Announcement

**bay1902** · 04 July 2012, 05:44

Bob,

My utmost respect and congrats, you flippin genius!

I'm out all day at a meeting in London but will d/l and run the beta tonight. Will post back any issues, but so looking forward to this!

Many thanks from 7g2 users!

bay

**patalao** · 04 July 2012, 10:36

hi bob
just tried your rom and the touch doesn`t respond as he should
an example: if i press the back button it will assume that i`m pressing the google search bar
resuming all the touch functions are switched(i press one thing and it does another)

i have erased IDB and flash the loader
and in the ClockWork recovery the touch works fine but with a little lag(when i press down or up it takes a wile to responde but nothing dramatic)

by the way sorry for my english and i hope this will help you solving the problem
don`t know if its only me but this is what happened

hope you can reply as soon as possible and good work by the way
i admire your will in doing such things
thank`s

**kevin** · 04 July 2012, 12:36

thanks you Bob for your great job, I'll donate some money because your job is... the best

**bay1902** · 04 July 2012, 16:48

Bob,

Confirmed - the touch on the ROM has issues. I can't even get onto play to install alogcat. Essentially the touch icons & where they physically respond appear to be on opposite corners.

For example, for the notification bar on the bottom right you need to touch the top right corner. Touching the Google search opens the apps (if you can actually find the right point on the screen). To activate the bottom left buttons you have to touch just about the time on the bottom right - again its tricky to find.

So basically, the rom seems speedy, however you are unable to navigate due to the touchscreen being all over the place. I have even tried using the accelerometer to see if different ways round makes the button active - it doesn't.

So hope this helps - would provide more but just unable to get a logcat for you. Also unable to do system checks in terms of software use as you simply cannot get there with the touchscreen.

Hope this is an easy adjustment for you.

Great stuff so far, a few little tweaks I think & we're there!

Cheers

bay

Edit - also got issues with the touch on the lockscreen - trying to find the right spot to swipe it unlocked is a task! lol

**bay1902** · 04 July 2012, 16:55

ok, apologies for a double post - but this is relevant. Couldn't switch the 7G2 off due to the touchscreen issue so did a reboot via the reset button, let it re-start & suddenly all touchscreen icons worming perfectly!

No idea what this is about but connecting to my wifi & play in a moment. Will get a logcat if I can & will monitor if this stays stable.

Great work bob!

Edit - one more update / something noticed Bob, we seem to have the same battery icon bug as in previous morkamod roms. The question mark is over the icon & it only appears to update when rebooted. I'm not sure if this is something that can be fixed or not?

**patalao** · 04 July 2012, 17:03

Strange
Just turn the Tab on now and as magic it works ok now
this is some freaking mystery

**bay1902** · 04 July 2012, 17:08

Additional findings - signing into Google Play doesn't want to work. gapps force closes on me, followed by google framework - meaning i've not been able to set an account. Just using using app injector & then will reboot & see if this makes any difference.

**Finless** · 04 July 2012, 17:14

Originally posted by patalao View Post

Strange
Just turn the Tab on now and as magic it works ok now
this is some freaking mystery

You guys. Read the readme. You HAVE to reboot after first load up of the OS or the touch screen will act wierd and you will probably have no sound.
Flash the ROM, CWM menu shows up, select reboot now. When desktop comes up reboot again.
All should be working fine after that.

patalao, this is why it worked after you powered off and back on!

Yes you need to use APP Injector and at least put back the stock browser and an email client (at least one of them) or Gplay will not work.

Bob

**patalao** · 04 July 2012, 17:23

Originally posted by Finless View Post

You guys. Read the readme. You HAVE to reboot after first load up of the OS or the touch screen will act wierd and you will probably have no sound.
Flash the ROM, CWM menu shows up, select reboot now. When desktop comes up reboot again.
All should be working fine after that.

patalao, this is why it worked after you powered off and back on!

Yes you need to use APP Injector and at least put back the stock browser and an email client (at least one of them) or Gplay will not work.

Bob

Bob when i installed the rom for the first time this morning i reeboot the device several times
that`s why i`ve posted the problem...
now i have force closes in several things just as said in post above by bay1902
will try to reinstall once more to see if it works

**kevin** · 04 July 2012, 17:31

When I flash the rom and I push reboot now, the tablet boot very well, reboot and all is beautiful, fatest and complete but when I install app injector and install all the aplications and reboot, all the app cause FC.

Sorry for my English.

**bay1902** · 04 July 2012, 17:42

Bob,

Appreciate this - ok bit of a 'doh' moment on the rebooting. Apologies for that, should have read readme. But the issue with the battery notification & also the removal of notifications on the 'taskbar' - these are occurring. Still only have a ? on the battery icon.

Used app injector to install maps - force closes each time. Have both stock & gmail email apps in - still get force closes on Gplay & when trying to sign in with my account. Unable to sign into gmail or use gapps google sign-in at all.

Edit - additional testing. Most of the apps within the injector force close or just stop altogther. This includes Google Earth, Eurosport, Angry Birds.

Working: Camera, Gallery, Music, Reader, YouTube, Play Music, Calc,

Not working - calendar, GPlay, Gmail, Battery indicator (not updating at all) - basically any application that requires gapps

I'm also getting Superuser keeps on quitting & force closing - meaning that Button Saviour stops, etc. Strange.

**Finless** · 04 July 2012, 19:27

Hmmmm OK...

I will have to look into this with APP Injector and the force close. Sounds like the same problem I had with the first BETA of the 9G2. I must have missed something.

As for the messages staying on the task bar. THIS IS how Honeycomb works. Unfortunatly you have to close them by clicking on the message, a little box will pop up, click the little X on the right side of the box. This is how you close those messages. There is nothing I can do to fix this as again this is how honeycomb works!

As for the battery icon. I can look inot that but it is not a problem on the 10G2 or the 9G2. So makes me wonder if this is not a kernel issue with the 7G2. Maybe thats also why Morka never fixed it.
I will look into it.

Thanks for BETA testing guys. I am sure I can solve these force close issues. I already think I know what the problem is.

Bob

**bay1902** · 04 July 2012, 19:29

Cheers Bob,

Trying to get a logcat out but no dice so far - only get a blank, can see red and amber errors with alogcat but just can't get an output.

With the message on how Honeycomb works, I know. My point is that there isn't actually an X to close these, well not on my 7g2, maybe i'm missing something here?

Originally posted by Finless View Post

Hmmmm OK...

I will have to look into this with APP Injector and the force close. Sounds like the same problem I had with the first BETA of the 9G2. I must have missed something.

As for the messages staying on the task bar. THIS IS how Honeycomb works. Unfortunatly you have to close them by clicking on the message, a little box will pop up, click the little X on the right side of the box. This is how you close those messages. There is nothing I can do to fix this as again this is how honeycomb works!

As for the battery icon. I can look inot that but it is not a problem on the 10G2 or the 9G2. So makes me wonder if this is not a kernel issue with the 7G2. Maybe thats also why Morka never fixed it.
I will look into it.

Thanks for BETA testing guys. I am sure I can solve these force close issues. I already think I know what the problem is.

Bob

**Finless** · 04 July 2012, 19:37

DAMN IT!

I am an idiot! I cannot believe I made the same mistake twice! The mistake I made with the 9G2 I did exactly the same mistake with the 7G2.

OK so please do this:
Here is a new boot.img. This is all you need to fix ALL of the force close and the google sign in issues.

1) Download this boot.zip
2) Unzip it and it will leave a boot.img
3) In the ROM kit delete the boot.img in the /image folder
4) Put this new boot.img back into the ROM kit /image folder
5) Reflash the ROM. Yes please erase IDB again so we get a clean start.

Here is the new boot.img download:

http://video.freaktab.com/?subpath=f...ename=boot.zip

Let me know and if it works I will update the entire ROM download for others. Until then I have taken it offline.

Bob

Announcement

Announcement

ENDED - Arnova 7G2 Finless Bob's "GingerComb" Custom ROM Version 2.1 BETA 2

ENDED - Arnova 7G2 Finless Bob's "GingerComb" Custom ROM Version 2.1 BETA 2

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

What's Going On