Hi, I recently rooted my friends Hero (CDMA).
We flashed CM7 and the latest GAPPS.
After everything got set up we noticed the Home Button on the phone doesn't work, Long Press and short press does absolutely nothing.
I know it is operational and works on the stock rom. ClockWork Recovery also detects when the home key is pressed.
Updating to the latest nightly(58) does not help either.
The Home Key just will not work in CM7.
How can I fix it and make the home button work again?
Thanks in advance.
Do the flash process start to finish again, it works.
il Duce said:
Do the flash process start to finish again, it works.
Click to expand...
Click to collapse
Thanks, that fixed the home button problem!
Usually I do this...
- Reboot recovery
- Wipe Cache
- Format Cache (Just to be safe_
- Wipe Dalvik
- Key Test
- Press Home Button 20x
- Wipe Cache
- Format Cache (Just to be safe_
- Wipe Dalvik
- Reboot into system
All done and working again on my freshly flashed rom It's a bit quicker than re-flashing and setting up all over again
FIXED!
I had this same problem I found out that I installed the wrong version of GAPPS. I installed Gapps for ICS cm9 instead of the correction version for CM7
good luck!
shadmaster said:
I had this same problem I found out that I installed the wrong version of GAPPS. I installed Gapps for ICS cm9 instead of the correction version for CM7
good luck!
Click to expand...
Click to collapse
Cm9 wasn't even out when this was posted. :/
Sent from my HERO200 using XDA
Yes it was! It was the build before build prototype prototype Alpha!
It was hard to come by. Top secret. G 14 Classified.......very hush hush.
Related
Since the upgrade to FRF91, my AT&T nexus one has been somewhat laggy, and I even got an "App is not responding, force close?" dialog, which I believe is the first of those I have gotten on the Nexus One. Animations between programs almost always stutter now, while on the original Froyo release, this was not an issue.
MatthewDS said:
Since the upgrade to FRF91, my AT&T nexus one has been somewhat laggy, and I even got an "App is not responding, force close?" dialog, which I believe is the first of those I have gotten on the Nexus One. Animations between programs almost always stutter now, while on the original Froyo release, this was not an issue.
Click to expand...
Click to collapse
I would try the following (assuming you are STOCK):
Turn your phone off
Mail it to me (kidding)
Hold Volume Down and power back on (puts you into Stock Recovery)
Press the Volume Up and Power at same time (brings up the Recovery Menu)
Select Wipe Cache Partition (or similar)
Reboot
Hope this helps!
After download FRF91 on my stock N1 the apps run really smooth and in
FRF85B I had alot of force close pop-ups.
I did a wipe cache and wipe cache devik and installed the FRF91 and my N1 is running silky smooth and fast with all apps.
Ok, tried that. Seems better, but it might just be that fresh feeling after a reboot. Thanks for your help.
Sent from my Nexus One using XDA App
Damn good tip Talderon. Worked for me.
Thanks!
Talderon said:
I would try the following (assuming you are STOCK):
Turn your phone off
Mail it to me (kidding)
Hold Volume Down and power back on (puts you into Stock Recovery)
Press the Volume Up and Power at same time (brings up the Recovery Menu)
Select Wipe Cache Partition (or similar)
Reboot
Hope this helps!
Click to expand...
Click to collapse
Sent from my Nexus One using XDA App
Talderon said:
I would try the following (assuming you are STOCK):
Turn your phone off
Mail it to me (kidding)
Hold Volume Down and power back on (puts you into Stock Recovery)
Press the Volume Up and Power at same time (brings up the Recovery Menu)
Select Wipe Cache Partition (or similar)
Reboot
Hope this helps!
Click to expand...
Click to collapse
Does this process have any undesirable effects? By this I mean, does it erase anything one would likely want to keep?
what if you have RA recovery? how do you wipe cache?
logger said:
Does this process have any undesirable effects? By this I mean, does it erase anything one would likely want to keep?
Click to expand...
Click to collapse
No side effects at all. The first boot after wipe may take longer cause the dalvik cache has to be recreated. No necessary data and no settings get lost.
For amon ra select wipe -- cache and wipe -- dalvik cache
You should do this after every rom update and kernel update. I am flashing kernels nearly every day and wipe helps 99% when facing problems!
i was updating my touchpad CM9 to V2 from aplha .06 and i just downloaded it stright to the touchpad with wifi and went to update it. I wiped the cach and all that but right before i went to install the CM9 i accidently hit the fix permissions button, it was like 5 am had just woken up and was in a hurry. Now that i try to boot to CM it wont do it at all it just reboots. I was wondering if anyone had an insight on it and could help me let me know.
Thanks in advance
plada2315 said:
i was updating my touchpad CM9 to V2 from aplha .06 and i just downloaded it stright to the touchpad with wifi and went to update it. I wiped the cach and all that but right before i went to install the CM9 i accidently hit the fix permissions button, it was like 5 am had just woken up and was in a hurry. Now that i try to boot to CM it wont do it at all it just reboots. I was wondering if anyone had an insight on it and could help me let me know.
Thanks in advance
Click to expand...
Click to collapse
Try flashing over.
Wipe data, cache and Dalvik and start fresh. It sounds like you had a bad flash...
plada2315 said:
i was updating my touchpad CM9 to V2 from aplha .06 and i just downloaded it stright to the touchpad with wifi and went to update it. I wiped the cach and all that but right before i went to install the CM9 i accidently hit the fix permissions button, it was like 5 am had just woken up and was in a hurry. Now that i try to boot to CM it wont do it at all it just reboots. I was wondering if anyone had an insight on it and could help me let me know.
Thanks in advance
Click to expand...
Click to collapse
I did the exact same thing and thought I had screwed things up. Luckily I had backed up prior so I simply restored it and it appears to have been fixed. There might be another way to remedy this in case you don't have back up though.
Good luck with finding a solution.
Sent from my MIUI Evo 3D
[SOLVED]
Sorry I keep posting things to myself and solving it on my own after hours -__-.. I already struggled hours beforehand and was frustrated..
Anyways, I went to CMW recovery mod, deleted the back up that I backed earlier. And then format/reset to factory mod / wipe partition / cache / Dalv. Then I went to boot my device but after 10 minutes, it'd still be loading cyanogen.... so I reinstalled the CyanogenMod9. Wiped all the things I mentioned above again and when it loaded to OS, it worked..
I have no idea what was causing it.. probably the back up file interfering somehow? Because that's the only thing I got rid of and everything went back to normal.
_________________
Hey guys, I successfully installed CyanogenMod 9 on my Gingerbread 2.3.5.
Everything is great and slick. I used to use CyanogenMod 7.
Funny thing is, I enabled the lock screen (pattern) and it seems to be not working? I don't know if I'm missing something but after leaving my phone for good 20 minutes, I came back to turn on (from sleep) and it wasn't asking for lock screen pattern. I tried slide too, same.
Also, from my previous versions, whenever I was in setting or any app, if I were to press on Home Button it would bring my back to main screen. My Home button no longer does this. I have no idea what it does now, I press it and the phone vibrates (indicates that its been pressed) but no effect. I have to literately press Back like 5 times just to return to Main menu.
Is there something I'm suppose to enable or something?
Let me know, thank you
-Dan
danroh said:
[SOLVED]
Sorry I keep posting things to myself and solving it on my own after hours -__-..
Click to expand...
Click to collapse
lol, hate when that happens
Hey danroh,
I had same issue with home button and lockscreen and this steps fixed problem:
1) I accidentally downloaded Jelly Bean gapps instead of ICS version
2) Reinstalled CM9
3) Downloaded experimental build and flashed that over stable one
4) Flashed with proper ICS gapps
5) Factory reset/Data wipe, Clear Dalvik cache
6) Reboot
-----
Hit thanks if that worked for you
HElp ME
hard2play said:
Hey danroh,
I had same issue with home button and lockscreen and this steps fixed problem:
1) I accidentally downloaded Jelly Bean gapps instead of ICS version
2) Reinstalled CM9
3) Downloaded experimental build and flashed that over stable one
4) Flashed with proper ICS gapps
5) Factory reset/Data wipe, Clear Dalvik cache
6) Reboot
-----
Hit thanks if that worked for you
Click to expand...
Click to collapse
IT didnt wok, maybe because i dont have the needed gapps. Do you have a link?
danroh said:
[SOLVED]
Sorry I keep posting things to myself and solving it on my own after hours -__-.. I already struggled hours beforehand and was frustrated..
Anyways, I went to CMW recovery mod, deleted the back up that I backed earlier. And then format/reset to factory mod / wipe partition / cache / Dalv. Then I went to boot my device but after 10 minutes, it'd still be loading cyanogen.... so I reinstalled the CyanogenMod9. Wiped all the things I mentioned above again and when it loaded to OS, it worked..
I have no idea what was causing it.. probably the back up file interfering somehow? Because that's the only thing I got rid of and everything went back to normal.
Click to expand...
Click to collapse
Weirdly, my brother's Galaxy S had the same thing. Home button just would not work after installing CM9. Tried a few things, failed.
Then, I found this thread and I remembered that I'd backed up his old CM7 a while before. Deleted that backup in CWM Recovery, factory wiped/cache wipe, reinstalled CM9 and Gapps for 9 and boom, everything was fine.
EDIT:
Another thing to note is that when the home button wouldn't work, there was no Lockscreen either, just like you had. On first boot it didn't prompt me for a google account either, which it did do after I deleted the backup.
hard2play said:
Hey danroh,
I had same issue with home button and lockscreen and this steps fixed problem:
1) I accidentally downloaded Jelly Bean gapps instead of ICS version
2) Reinstalled CM9
3) Downloaded experimental build and flashed that over stable one
4) Flashed with proper ICS gapps
5) Factory reset/Data wipe, Clear Dalvik cache
6) Reboot
-----
Hit thanks if that worked for you
Click to expand...
Click to collapse
hey man!!..thnx for your guide...i w as actually in great trouble coz of this error..nd now its fixed!!...thnx a lot!!...
Hello people o/
I've downloaded a CM11 rom for my galaxy ace and i'm having some problems with it.
As soon as I installed everything(gapps, cmlogin) the phone turned on normally, but now I can't use neither the volume button or the back/options button, and just to add up there's no keyboard installed on my phone anymore.
Can someone please help me with it? It's really frustrating
picles said:
Hello people o/
I've downloaded a CM11 rom for my galaxy ace and i'm having some problems with it.
As soon as I installed everything(gapps, cmlogin) the phone turned on normally, but now I can't use neither the volume button or the back/options button, and just to add up there's no keyboard installed on my phone anymore.
Can someone please help me with it? It's really frustrating
Click to expand...
Click to collapse
Boot into recovery and restore a backuped rom , you can also use Odin to flash a fresh stock rom
Here there's a usefull q&a thread, have a look
http://forum.xda-developers.com/showthread.php?t=2313363
Sorry to resurrect an old thread but the same thing is happening to me. Clean install, wipe data, format system and it's still there. It seems that this problem only pops up after installing Gapps. But as far as I know, it's Gapps for 4.4.4. using this particular CM11 build. http://download.androidarmv6.org/_builds/cooper/stable/ RC10.
key board and menu, back buttons not working inmy ace after flasing with rc14
CMAceS5830 said:
key board and menu, back buttons not working inmy ace after flasing with rc14
Click to expand...
Click to collapse
You need to install correctly the ROM... which procedure have you followed to flash the ROM?
i have used the CWM-6.0.5.3_1-cooper to flash the rc 14 after clearing the cache dalvik and data.factory reset. and after flashingi have installed the minigoogle apps. i have tried the rc13 ,14 nd the stable release released today. all of them behave the same. Please let me know how i have to enable the keyboard. i am unable to connect to wifi also as unable to type the password in the prompt.
let me know if there is any other process to be followed while flashing the files.
i have used the CWM-6.0.5.3_1-cooper to flash the rc 14 after clearing the cache dalvik and data.factory reset. and after flashingi have installed the minigoogle apps. i have tried the rc13 ,14 nd the stable release released today. all of them behave the same. Please let me know how i have to enable the keyboard. i am unable to connect to wifi also as unable to type the password in the prompt.
let me know if there is any other process to be followed while flashing the files.
can you please post the complete process , that you think would flash the rom normally..
picles said:
Hello people o/
I've downloaded a CM11 rom for my galaxy ace and i'm having some problems with it.
As soon as I installed everything(gapps, cmlogin) the phone turned on normally, but now I can't use neither the volume button or the back/options button, and just to add up there's no keyboard installed on my phone anymore.
Can someone please help me with it? It's really frustrating
Click to expand...
Click to collapse
The solution for my my problem was:
Wipe data/factory reset AND
Clear cache and Dalvik cache AND
Format system partition
This can be done using ClockworkMod using various menus.
share
improve this answer
edited Oct 10 '14 at 13:34
Valerio Bozz
1032
answered Mar 19 '14 at 14:21
TaronAM
22113
Set as solution. Maybe you want to add the software you used for these steps. – davidbaumann May 20 '14 at 4:42
1
There is no additional software involved, other than booting into Recovery. – Matthias Urlichs Sep 13 '15 at 10:16
1
I also had to install CM again after these steps, but maybe because I said "No" to rooting the phone again on a reboot, and perhaps CM does that anyway (yes this is not the most intellectual comment) – Matthias Nov 25 '16 at 16:44
I installed CM11 last monday from this thread: http://forum.xda-developers.com/showthread.php?t=2658534
Since then I got the issue, that after the phone is in standby for a while, I can't unlock the lockscreen. There is no input possible, just reacts like I'm not touching the screen. If I press the power button again it locks again (screen off), but then it's not possible to even see the lockscreen again, powerbutton not working anymore. The only way to use the phone again is to hold the powerbutton for 10 seconds and reboot then.
I tried to wipe all and flash again, but no change. I tried "cm-11-20140503-UNOFFICIAL-jactiveltexx.zip" from spegelius first, and then "cm-11-20140508-UNOFFICIAL-jactiveltexx.zip" from allram. Wiped everything before flashing, but no luck, still getting that bug.
Sadly I can't post directly into that topic, because I'm new here
:DDDDDDDD said:
I installed CM11 last monday from this thread: http://forum.xda-developers.com/showthread.php?t=2658534
Since then I got the issue, that after the phone is in standby for a while, I can't unlock the lockscreen. There is no input possible, just reacts like I'm not touching the screen. If I press the power button again it locks again (screen off), but then it's not possible to even see the lockscreen again, powerbutton not working anymore. The only way to use the phone again is to hold the powerbutton for 10 seconds and reboot then.
I tried to wipe all and flash again, but no change. I tried "cm-11-20140503-UNOFFICIAL-jactiveltexx.zip" from spegelius first, and then "cm-11-20140508-UNOFFICIAL-jactiveltexx.zip" from allram. Wiped everything before flashing, but no luck, still getting that bug.
Sadly I can't post directly into that topic, because I'm new here
Click to expand...
Click to collapse
I suppose you have Gt-I9295 not US version of the phone?
When you flashed the zip. did u do a factory reset? and format /system /cache?
allram said:
I suppose you have Gt-I9295 not US version of the phone?
When you flashed the zip. did u do a factory reset? and format /system /cache?
Click to expand...
Click to collapse
Yes I got the european version. Before I flashed CM11 I did a "factory reset", wiped cache and dalvik cache. I did that before flashing another rom again. I will try to flash the newest (13th may) version from your gdrive later.
:DDDDDDDD said:
I installed CM11 last monday from this thread: http://forum.xda-developers.com/showthread.php?t=2658534
Since then I got the issue, that after the phone is in standby for a while, I can't unlock the lockscreen. There is no input possible, just reacts like I'm not touching the screen. If I press the power button again it locks again (screen off), but then it's not possible to even see the lockscreen again, powerbutton not working anymore. The only way to use the phone again is to hold the powerbutton for 10 seconds and reboot then.
I tried to wipe all and flash again, but no change. I tried "cm-11-20140503-UNOFFICIAL-jactiveltexx.zip" from spegelius first, and then "cm-11-20140508-UNOFFICIAL-jactiveltexx.zip" from allram. Wiped everything before flashing, but no luck, still getting that bug.
Sadly I can't post directly into that topic, because I'm new here
Click to expand...
Click to collapse
You should also use CWM 6.0.4.7...?