11 replies to this topic

[Adgeek]

Hi all

my home button didn't work anymore in CM7 RC2. It's a very annoying problem. Please fix it thanks.

Or maybe somebody have a solution?

Regards.

[yassinej]

Hi!

I'm using HTC Desire GSM and i have the same issue after flashing CM7 RC2.
The home and search button are not working.

I have done full wipe before flashing.

Thank you for your time.

Adgeek, on 08 March 2011 - 03:35 PM, said:

Hi all

my home button didn't work anymore in CM7 RC2. It's a very annoying problem. Please fix it thanks.

Or maybe somebody have a solution?

Regards.

[timothe]

try nightly build 14

[mtbsoft]

I'm suffering from the same problem of the Home & Search buttons not working - I can almost produce this on demand.

Telstra Desire, hboot cm7r2, radio 5.17.05.23, 32Gb - 512M ext4, remainder FAT32.

I can restore an early nandroid backup and everything is fine, restore a number of apps via Titanium, reboot and everything is still fine, leave the device for a while and the buttons stop working.

I've checked for the data row in the sql table "secure" referred to in post 8 of the thread http://forum.cyanoge...ns-not-working/ and the row of data is there.  I'm really at a loss what else to try - I've spent the last two odd days doing litlle more than backsups, resets and restores, trying different install sequences, different start points all resulting in the same final result - Home and Search stop working (the screen just blinks).

Any thoughts or suggestions (please, I'm getting desperate!).  I've got a logcat which may have the "button-disconnect" event in it but can't identify it myself, if anyone can suggest what I need to look for I'm happy to try.

Cheers.

Edited by mtbsoft, 02 January 2012 - 09:31 AM.

[bassmadrigal]

Are you ever restoring system data with Titanium Backup? You should only restore apps and app data when using Titanium Backup. And I don't know what CM7r2 is... can you fill me in? And why are you restoring a nandroid and restoring backups from Titanium rather than just installing the latest version of CM through recovery?

[mtbsoft]

Thanks for replying mate. Ok...

Never restoring any system data with Titanium (I know that one!).  I basically started with a fresh install of CM 7.1.0 (updated hboot through fastboot, then installed CM7, gapps and radio through recovery), went through and did all the configuration (wifi, etc) and did a nandroid which I can restore as a configured base.

hboot CM7r2 from http://alpharev.nl/ (145Mb/5Mb/287Mb)

I then restore a variety of apps through Titanium because they have data included which I don't want to lose.

Make sense (I hope so).

More info to add. Pressing the Home button which running aLogCat showed the following in red/orange...

"WResourceType( 182): Invalid package identifier when getting bag for resource number 0x00000000"

I'm wondering if it might be worth updating ADW from the market, thoughts?  I haven't tried any nightly builds yet and can't find a full builds for earlier 7.X to try, only updates.

[mtbsoft]

Oh damn, just realised this isn't a Desire forum - want me to restart this in the Desire forum?

[bassmadrigal]

The N1 and the Desire have very similar innards, but it could be possible this is a Desire only issue (as I haven't seen this issue other than the issues in that other thread you posted in). So posting in there might yield other responders.

Have you tried without restoring any apps to see if the problem still happens? I am thinking it could be related to an app.

[mtbsoft]

Trying that approach as we speak, loading half a dozen apps at a time straight from the market (doco'ing as I go) then leaving it for an hour or so.

Noted that there were a couple of Widget related entries in the logcat shortly afterwards so I'm going to skip widgets for now (sigh!) and see if that makes any difference too.

Will post to the Desire forum and link the threads.

Cheers mate, will let you know how I go.

Edited by mtbsoft, 02 January 2012 - 12:59 PM.

[mtbsoft]

Well, it has been a long effort but... the final culprit seems to be the data associated with Tasker that I was restoring using Titanium.

It's been a long effort of nandroid backup, install a few apps, reboot, put some data in, watch for bad behaviour, restore some data with Titanium, rinse and repeat. (Stats:  7 nandroids, 10 cycles (3 failures), 90 apps)

Technically the jury is still out... it's working for now, only in about 24 hours will I be truly satisfied that I've nailed it but it shows that not even non-systems apps' data is absolutely safe to restore.

[mtbsoft]

Bingo!  Got it!

It was the Tasker data, as I thought, but... I tried exporting it from Tasker, reset device, restore previous backup, import into Tasker... and it broke again.

So I tried disabling different profiles within Tasker and discovered that it was those which were driven by an application running (specifically, enabling GPS on Maps or Navigation running).  By recreating the specific profiles from scratch, rather than restoring them, the problem went away, so I guess the app. id. changed across roms (or something like that).

Why it should manifest as broken Home and Search I'll leave for someone else to discover.

So, if you are having trouble with your Home and Search buttons stopping... and have just come from a different rom... and are using something like Tasker ... and have restored data which identifies specific applications running on the new rom... (sharp intake of breath) DON"T!  Don't restore that data but instead recreate it and hopefully you won't waste three days of your Christmas holidays trying to get to the bottom of the problem!

Hope this helps someone!

Edited by mtbsoft, 03 January 2012 - 01:11 PM.

[bassmadrigal]

Thanks for filling us in, and I am glad you finally got it figured out.