Since flashing CM 10.1 I have had this happen twice... when i press the home button, it acts like i'm doing a long press (it even vibrates).
Rebooting the phone fixes it. Not sure what "triggers" this fault, but wondering if anyone else has had the same issue?
Thanks
dcipher said:
Since flashing CM 10.1 I have had this happen twice... when i press the home button, it acts like i'm doing a long press (it even vibrates).
Rebooting the phone fixes it. Not sure what "triggers" this fault, but wondering if anyone else has had the same issue?
Thanks
Click to expand...
Click to collapse
On last CM10.1 build?
It could be that you're pressing it hard and it gets stuck or that there's dirt under.
I get this randomly as well. I'm on the 1/27 nightly
Sent from my SAMSUNG-SGH-I747 using xda premium
According to this thread http://forum.xda-developers.com/showthread.php?t=2085171(10.1 it is an issue with cm10.1. Though the thread hasn't been updated in a week.
It is a known issue. A reboot is the only solution to the problem though (until it starts acting up again).
I've also experienced this issue, reboot fixes it. Almost like a memory leak, but I'm not sure. Irritating, but I'm glad the home button wake issue was finally fixed in 10.1.
Yupp, known issue. I personally have dealt with it since 10.1 release, and finally got tired of it and switched to Tasks AOKP.
Sent from my SGH-I747 using xda app-developers app
Related
Hi everyone, I am new here but not new to rooting phones. I've followed the instructions for installing |ROM| Jedi Mind Trick |V9| 9|19 completely and thoroughly and I've waited the 10 mins (sometimes more) before I rebooted the phone. Every time after the reboot, I start messing with the phone and checking out the features, my capacitive buttons just completely stop working, they are unresponsive and they don't even light up. Also, the lockscreen doesn't work unless I press the power button once and then I can go into the phone and everything else is working except for the capacitive buttons. So that leaves me stuck in the last app that I was in and I cannot go back home since the capacitive buttons are functioning.
I have tried reflashing the ROM 3 times and the same exact thing happened each time. I also tried rebooting the phone and turning the phone completely off and the capacitive buttons will function only for about a minute and then completely stop working again. I was wondering if someone knows how to fix this or if anyone was experiencing the same issue and found a way to fix it. Please let me know, I'm not sure what I did wrong for this happen since the ROM seems to be working for everyone else.
I found I had far less problems and quirks after installing teamwin touch recovery. Then flash.
Sent from my aokp_tenderloin using xda app-developers app
ctrlaltdeln said:
I found I had far less problems and quirks after installing teamwin touch recovery. Then flash.
Sent from my aokp_tenderloin using xda app-developers app
Click to expand...
Click to collapse
Ok, thank you, I will try using TWRP and see if it fixes the issue. Will reply back soon!
myst3ry23 said:
Ok, thank you, I will try using TWRP and see if it fixes the issue. Will reply back soon!
Click to expand...
Click to collapse
i had exactly the same problem. I second the advise above. In the nutshell, it seems, that the flashing sequence didn't clean something.
Running 11-15 nightly of CM10
Does anybody have any trouble waking their device from time to time?
Sometimes the device doesn't wake when I press the power button or it takes a couple of presses.
Same thing with the Home button.
Just wondering if this was a hardware issue or software issue.
khoikn said:
Running 11-15 nightly of CM10
Does anybody have any trouble waking their device from time to time?
Sometimes the device doesn't wake when I press the power button or it takes a couple of presses.
Same thing with the Home button.
Just wondering if this was a hardware issue or software issue.
Click to expand...
Click to collapse
I've experienced that when on CM10. So it definitely ain't hardware. Test It out by using TW.
SiNJiN76 said:
I've experienced that when on CM10. So it definitely ain't hardware. Test It out by using TW.
Click to expand...
Click to collapse
same thing. i only had that issue on cm ROMs... running the official jelly bean release and the issue went away immediately.
Ok so I've been using a few different versions of the CM10 ROM and I've noticed a new problem. On occasion, when I go to wake the device, it will not wake. The keys light up, but thats it, the screen doesn't come on. The only way to get it working again is to hold down the power button and wait till it restarts. It's happened twice so far, not too frequently but annoying none-the-less.
Is there something I can do to fix this?
screwregi said:
Ok so I've been using a few different versions of the CM10 ROM and I've noticed a new problem. On occasion, when I go to wake the device, it will not wake. The keys light up, but thats it, the screen doesn't come on. The only way to get it working again is to hold down the power button and wait till it restarts. It's happened twice so far, not too frequently but annoying none-the-less.
Is there something I can do to fix this?
Click to expand...
Click to collapse
I thought you said you noticed a new problem...
Sent from my LG-P930 using xda premium
lordcheeto03 said:
I thought you said you noticed a new problem...
Sent from my LG-P930 using xda premium
Click to expand...
Click to collapse
I meant new to me! Though I looked around like crazy, cant find anything on this problem so I figured it was unique to my device.
screwregi said:
I meant new to me! Though I looked around like crazy, cant find anything on this problem so I figured it was unique to my device.
Click to expand...
Click to collapse
Nah, I'm mostly just giving you a hard time The CM10 nightly thread has gotten to be a beast to look through; seriously though... that problem is pretty old, and like you said; the only way to get around it is to hold power or do a battery pull. Just wait until you have an alarm go off in the morning and you can't turn it off!
Try the 2013 nightly, it does not appear to have this issue
Nz
notzippy said:
Try the 2013 nightly, it does not appear to have this issue
Nz
Click to expand...
Click to collapse
Maybe not, but it probably has other issues instead!
I can confirm that these issues still exist in the NIGHTLY (1/20) version. Just had it happen. Doesn't appear to be quite as frequent, but definitely still happening. I think it MAY have something to do with notifications, not sure though. Seems to often happen when I get a notification, I'll go turn it on and it wont wake from sleep.
screwregi said:
I can confirm that these issues still exist in the NIGHTLY (1/20) version. Just had it happen. Doesn't appear to be quite as frequent, but definitely still happening. I think it MAY have something to do with notifications, not sure though. Seems to often happen when I get a notification, I'll go turn it on and it wont wake from sleep.
Click to expand...
Click to collapse
Just saying; but there's already a thread for discussing CM10...
Hey all. So the past few days I noticed that my Menu button on my S3 ATT has been showing the Google Now search. Additionally when pressing home often time it goes to the Multi Task window. These are settings I set for the 'long press'. I should note Im running CM 10.1 latest nightly and Nova Launcher (if it matters).
I figured this was a CM issue so I went to a 1 week old nightly but the same. Im not worried this may be something to do with the hardware buttons themselves. Really hoping its a software thing
Anyhow I appreciate any help on the subject or things I can try
Thanks!
Its worth adding that when I upgrade the nightly, then the buttons seem to work for at least a few hours. Im not sure if a simple reboot would also have this effect however I plan to monitor that when it starts acting up again and let you all know
Seems very odd to me that it works fine for awhile then gets worse and worse throughout the day
Thanks
I think what you're experiencing is a long button press bug. CM10.1 has a known issue of registering a long press (especially for hardware keys) even when you quickly tap.
So if I had to guess I'd say your phone is fine and it is CM10.1,
I should add this happens on my menu button too. It hasnt happened on my back button but I also have nothing on my Long Press for the back button.
RoachForLife said:
I should add this happens on my menu button too. It hasnt happened on my back button but I also have nothing on my Long Press for the back button.
Click to expand...
Click to collapse
do you know if this is something that affects everyone on a galaxy s3, just some phones or all phones on cm10.1? i've been running cm10.1 on my d2vzw and generally stay on top of all the development related postings but see hardly any mentions of the topic. i realize it's not a huge bug as a simple restart will fix it but it certainly is annoying.
first post, btw :cyclops:
I havent seen mention of this before but I am not on the forums all that much.
Quick update - after flashing to latest nightly, its been nearly 24hrs without issue. Hope it stays this way
RoachForLife said:
I havent seen mention of this before but I am not on the forums all that much.
Quick update - after flashing to latest nightly, its been nearly 24hrs without issue. Hope it stays this way
Click to expand...
Click to collapse
Update 2 - Yes, rebooting the phone does fix this. Last time I went 3 days before it began to act up. Rebooted and good as new. Kinda annoying but not the end of the world
Ive noticed that when my screen goes off and I hit the home button to wake it back up sometimes when it turns back on it shows me the recent apps list as if I held the home button down. Only started happening since latest update. Confirmed happening on stock and frosty jelly bean latest build.. has anyone else noticed this? Btw I have pattern lock as lock screen
Sent from my SGH-T889 using xda app-developers app
Yep - and if you disable the lockscreen it happens pretty much every time. How the home button is handled changed from 4.1.1 to 4.1.2, which is where the issue stems from I believe. It takes a little smali hacking to fix it (though to be fair I would consider the fix that I am trying as being in testing still).
Can you share how to resolve this issue. I don't think T-Mobile has fixed the issue and it is driving me nuts. I don't want a lock screen so that is not a good solution for me. I also prefer not to root at this point.
Thanks for any help!
It requires root unfortunately... though I suppose I could try to throw it into an ODINable tar similar to the prerooted tar thats out there...