The last couple ROMs I've flashed for my GSIII (Cyanogen 10.1 M1 & Carbon 1.4 JB 4.2.2) both work pretty well, I'm on Carbon at the moment because the video seems a little more stable.
However I've had a recurring issue on both ROMs. Ocassionally, the hardware Home Button will act as though it is always being long pressed.
So when you quickly tap it, the task switcher comes up instead of taking you to your home screen. The only fix seems to be to reboot the phone.
It didn't do this on the Cyanogen 10 final release so I'm guessing it has something to do with 4.2.2. Has anyone else experienced this issue? I tried searching around but couldn't find anything about it.
Thanks for any help.
Hexidecimal said:
The last couple ROMs I've flashed for my GSIII (Cyanogen 10.1 M1 & Carbon 1.4 JB 4.2.2) both work pretty well, I'm on Carbon at the moment because the video seems a little more stable.
However I've had a recurring issue on both ROMs. Ocassionally, the hardware Home Button will act as though it is always being long pressed.
So when you quickly tap it, the task switcher comes up instead of taking you to your home screen. The only fix seems to be to reboot the phone.
It didn't do this on the Cyanogen 10 final release so I'm guessing it has something to do with 4.2.2. Has anyone else experienced this issue? I tried searching around but couldn't find anything about it.
Thanks for any help.
Click to expand...
Click to collapse
This has been a known issue with CarbonRom. Here is a post that talks a little (very little) about it. It's a known bug and is basically when the three front hardware buttons automatically do long presses. No solution has been found yet.
topherk said:
This has been a known issue with CarbonRom. Here is a post that talks a little (very little) about it. It's a known bug and is basically when the three front hardware buttons automatically do long presses. No solution has been found yet.
Click to expand...
Click to collapse
Thanks for the reply, hope that once the GSIII gets official 4.2.2 it can be resolved, if not sooner.
Related
Hi guys,
Long time lurker, first time poster. I've been using CM7 RC2 without any issues, and recently updated to RC4. As soon as I did, my touchscreen lost a lot of responsiveness. Sliding open the drawer was no longer a simple swipe, I had to baby it along to get it to open, same thing applies to any other functions. Typing was a nightmare, because I had to press longer and harder on the screen to get it to recognize each of my keystrokes.
As soon as I switched back to my nandroid backup of RC2, everything's fine again. Any ideas? I've searched everywhere and can't find any mention of this problem, and didn't see it in the known bug list. I am using LauncherPro on top of CM7, might this be causing the issue?
Hardware 004, stock CM7 with default kernel if it matters.
THANKS!
Well I would recommend upgrading to the latest stable version, clean install, and see if that takes care of it first, along with the latest gapps.
beenyweenies said:
Hi guys,
Long time lurker, first time poster. I've been using CM7 RC2 without any issues, and recently updated to RC4. As soon as I did, my touchscreen lost a lot of responsiveness. Sliding open the drawer was no longer a simple swipe, I had to baby it along to get it to open, same thing applies to any other functions. Typing was a nightmare, because I had to press longer and harder on the screen to get it to recognize each of my keystrokes.
As soon as I switched back to my nandroid backup of RC2, everything's fine again. Any ideas? I've searched everywhere and can't find any mention of this problem, and didn't see it in the known bug list. I am using LauncherPro on top of CM7, might this be causing the issue?
Hardware 004, stock CM7 with default kernel if it matters.
THANKS!
Click to expand...
Click to collapse
Definitely would go with the stable release and you should be good to go.
PLEASE SEE BOTTOM OF OP FOR UPDATES
-----
Greetings all,
[Backstory]
I've been flashing ROMs for about a year now. I started off with Virtuous Team Gingerbread and the Sense 3.x ROMS. I had no issues.
Then I moved to CM7, and MIUI, also on Gingerbread. No problems.
I've been using the CM9/CM10 ROMs since they appeared for the Incredible 2, from AOKP and Aeroevan, respectively.
Here is where the problems start.
[Problem]
On ICS and JB ROMs, I get what I have dubbed (there is probably a better name for it) "Phantom Touch Input".
At first I thought this was caused by normal bugs and glitches in the ROM. I did my best to deal with it. Usually a simple lock/unlock would solve the issue, temporarily.
So what would happen? Without touching the screen, I would get the long press menu to show up, and then the screen and capacitive buttons would freeze. Or the screen would start to slowly half scroll to the side, and again, freeze.
The most annoying part is when I am typing on the phone. I have tried other keyboards, be it from the MIUIv4, or the default keyboards of 4.0.x, 4.1, or 4.2. All the sudden random keys are pressed, and continue to be pressed, even when my fingers are nowhere near the screen.
However, no one else seems to have this issue, so it looks like I am the lone wolf here with this problem.
Can anyone provide insight? A possible fix? Or am I forced to deal with this on all 4.x ROMs?
---
UPDATE 1: Issues also occurred on CM7.2, so I may be facing a hardware issue.
UPDATE 2: Issues occurred in 4ext Touch. Looking around on YouTube, others (Incredible S users) have similar issues.
Nearly confirmed as a hardware issue.
Check Page 2 for video links.
[::AP::] said:
Greetings all,
[Backstory]
I've been flashing ROMs for about a year now. I started off with Virtuous Team Gingerbread and the Sense 3.x ROMS. I had no issues.
Then I moved to CM7, and MIUI, also on Gingerbread. No problems.
I've been using the CM9/CM10 ROMs since they appeared for the Incredible 2, from AOKP and Aeroevan, respectively.
Here is where the problems start.
[Problem]
On ICS and JB ROMs, I get what I have dubbed (there is probably a better name for it) "Phantom Touch Input".
At first I thought this was caused by normal bugs and glitches in the ROM. I did my best to deal with it. Usually a simple lock/unlock would solve the issue, temporarily.
So what would happen? Without touching the screen, I would get the long press menu to show up, and then the screen and capacitive buttons would freeze. Or the screen would start to slowly half scroll to the side, and again, freeze.
The most annoying part is when I am typing on the phone. I have tried other keyboards, be it from the MIUIv4, or the default keyboards of 4.0.x, 4.1, or 4.2. All the sudden random keys are pressed, and continue to be pressed, even when my fingers are nowhere near the screen.
However, no one else seems to have this issue, so it looks like I am the lone wolf here with this problem.
Can anyone provide insight? A possible fix? Or am I forced to deal with this on all 4.x ROMs?
Click to expand...
Click to collapse
Not exactly sure, I would say its hardware if it happens on all the roms. Have you went back to CM7 or MIUI since this problem started? I would revert back to one of them and test for a couple of days to see if the problem continues. If the problem is only active in ICS or JB then someone else will have to give you a hand on a resolution.
ThePhantom97 said:
Not exactly sure, I would say its hardware if it happens on all the roms. Have you went back to CM7 or MIUI since this problem started? I would revert back to one of them and test for a couple of days to see if the problem continues. If the problem is only active in ICS or JB then someone else will have to give you a hand on a resolution.
Click to expand...
Click to collapse
Ok will do when I have the chance.
Thanks for the speedy reply.
But let's say it is a hardware issue...
Do I unroot/restore/whatever and bring it back to Verizon?
Thanks.
[::AP::] said:
Ok will do when I have the chance.
Thanks for the speedy reply.
But let's say it is a hardware issue...
Do I unroot/restore/whatever and bring it back to Verizon?
Thanks.
Click to expand...
Click to collapse
Yes if the phone is still under warranty
I'm so fresh you can suck my nits...
Flashed CM 7.2
My home button didn't work, but that doesn't really matter.
I still experienced the same issues.
On a side note, wow CM7.2/Gingerbread is smooth....damn kernel. But stock 2.3.x is so ugly
Anyways, it seems like I should just "start clean".
I'm not sure what that entails - not just a full wipe...something more...tips?
[::AP::] said:
Flashed CM 7.2
My home button didn't work, but that doesn't really matter.
I still experienced the same issues.
On a side note, wow CM7.2/Gingerbread is smooth....damn kernel. But stock 2.3.x is so ugly
Anyways, it seems like I should just "start clean".
I'm not sure what that entails - not just a full wipe...something more...tips?
Click to expand...
Click to collapse
I use 4ext recovery myself, and I do a "full wipe" by format all partitions/factory data reset, then I see a lot of people also say wipe cache and dalvik so I throw that in as well, it don't take long but just in case a factory reset don't get them I just do it...lol. Hope that helps, and that may clear up some bugs with ICS and JB roms if you weren't doing that before. Just make sure you do a backup before wiping everything. Wouldn't want you to be without a phone if some process hiccups.
Thanks for the info.
Should I do anything with my SD card? It shouldn't affect ROM performance, but a wipe wouldn't be a bad idea, yes?
[::AP::] said:
Thanks for the info.
Should I do anything with my SD card? It shouldn't affect ROM performance, but a wipe wouldn't be a bad idea, yes?
Click to expand...
Click to collapse
I doubt that the SD card would affect the performance, but as long as you have backups of everything you can do as you please, backup backup backup. You don't want to lose everything, trust me I have seen bad things happen to guys that don't backup, and I have learned from experience as well.
Right right I know.
I'll try 4ext on a fresh ROM and see how things go.
Not a good idea to flash the touch version of 4ext in light of my issues.
Did a Nandroid, hit back, then screen input froze. The on-screen time is updating, but are the capacitive buttons are lit up but do not respond/give haptic feedback, let alone the touch screen itself. Power button just moves to the power menu, where I again cannot select anything.
Pulling battery :/
This is why I will never (want to) purchase a phone without a removable battery.
So looks like my issue isn't software related. (This issue can in no way be software related [or even caused by], right?)
I've had the phone for over a year...but I guess I'll try with Verizon.
*sigh*
What a pain.
Looks like I am certainly not alone.
(Better video) http://www.youtube.com/watch?v=25CaiveQoQg
(Similar) http://www.youtube.com/watch?v=kANVkc-Sk74&feature=related
I'm just really pissed off. And there isn't a phone in the market that I want.
That looks like possibly a bad digitizer, you can replace that fairly cheaply if you are out of warranty. That would be my best guess, and keep in mind I am no expert. Here is a link so you can see the process:
http://www.youtube.com/watch?v=LQL9gakQyuI
ThePhantom97 said:
That looks like possibly a bad digitizer, you can replace that fairly cheaply if you are out of warranty. That would be my best guess, and keep in mind I am no expert. Here is a link so you can see the process:
http://www.youtube.com/watch?v=LQL9gakQyuI
Click to expand...
Click to collapse
That is what I was thinking.
I'll also see if I can milk anything out of Verizon. I'm already an unhappy customer, given the lack of ICS, especially when promised.
Yep, digitizer.
http://forum.xda-developers.com/showthread.php?t=1399085
Good luck with Big Red, and let us know if you get it resolved.
ThePhantom97 said:
Good luck with Big Red, and let us know if you get it resolved.
Click to expand...
Click to collapse
Thanks, I'll keep everyone updated.
I'm sure I'm not the only one who has had issues. Hopefully word spreads, especially to those still under warranty who are suffering from a faulty digitizer.
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
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
Hi all,
I'm unable to post my question in the development thread for this rom (http://forum.xda-developers.com/showthread.php?t=2085828), but hopefully some of you are running the Stable 4.2.1 version of Slim's rom and can help address my question.
First off, this rom is pretty much flawless and battery life is excellent (once I found the right Kernel). The only problem I'm experiencing is with the use of my Home Button. Often times when I go to hit the Home button it pulls up the Recent Apps, as if I'm "long pressing", instead of taking me to my home default screen. I also noticed that when this happens, if I hit the Menu Button it launches Google Search, as if I were "long pressing" it.
So it's as if the Rom/Phone thinks I'm "long pressing" when not. Typically a reboot fixes it for part of the day and then the issue returns. I've used the Halo Launcher that is included in the rom as well as my preferred NOVA Launcher and the problem persists with both. I've also tried full wiping and re-flashing but the problem always turns up.
I searched the thread as well and novone has mentioned it as an issue, I'm wondering if it's a hardware problem with my actual phone? For now, Ive enabled the on-screen nav keys as a work around.
Any thoughts or help on this would be much appreciated.
-Ryan
imryanthompson said:
Hi all,
I'm unable to post my question in the development thread for this rom (http://forum.xda-developers.com/showthread.php?t=2085828), but hopefully some of you are running the Stable 4.2.1 version of Slim's rom and can help address my question.
First off, this rom is pretty much flawless and battery life is excellent (once I found the right Kernel). The only problem I'm experiencing is with the use of my Home Button. Often times when I go to hit the Home button it pulls up the Recent Apps, as if I'm "long pressing", instead of taking me to my home default screen. I also noticed that when this happens, if I hit the Menu Button it launches Google Search, as if I were "long pressing" it.
So it's as if the Rom/Phone thinks I'm "long pressing" when not. Typically a reboot fixes it for part of the day and then the issue returns. I've used the Halo Launcher that is included in the rom as well as my preferred NOVA Launcher and the problem persists with both. I've also tried full wiping and re-flashing but the problem always turns up.
I searched the thread as well and novone has mentioned it as an issue, I'm wondering if it's a hardware problem with my actual phone? For now, Ive enabled the on-screen nav keys as a work around.
Any thoughts or help on this would be much appreciated.
-Ryan
Click to expand...
Click to collapse
This seems to be a common issue with 4.2.x ROMs. As far as I've heard the exact cause is unknown and there is no known permanent fix as of yet. For what it's worth, I'm running LiquidSmooth RC2 (4.2.2) and have the same issue periodically, as do many others. As you've noticed, a reboot is the only current fix. I'm sure it's something they will eventually work out, but for now it's a minor intermittent annoyance.
melocil ate
fingolfin14 said:
This seems to be a common issue with 4.2.x ROMs. As far as I've heard the exact cause is unknown and there is no known permanent fix as of yet. For what it's worth, I'm running LiquidSmooth RC2 (4.2.2) and have the same issue periodically, as do many others. As you've noticed, a reboot is the only current fix. I'm sure it's something they will eventually work out, but for now it's a minor intermittent annoyance.
Click to expand...
Click to collapse
Ahh, gotcha. I hadn't searched through any of the other 4.2 Rom threads. Thanks.
Something just got submitted to fix it I believe. http://review.cyanogenmod.org/#/c/33383/
Sent from my SGH-T999 using xda premium