Cyanogenmod RC4 - touchscreen responsiveness problem? - EVO 4G Q&A, Help & Troubleshooting

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.

Related

[Q] Moto Defy + Cm7RC1v2 camera flash always stays on

Hi this is my first post on xda, and I'm really hoping someone knows how to deal with this issue.
First of all let me just say that CM7 on the Moto Defy absolutely rocks! I do have one small quirk which I've yet to find any other Defy + CM7 user complain on.
Whenever I use the stock camera app and set my flash to "On", the flash turns on and STAYS on (like a flashlight). When I take a photo, the flash turns off though and works normally for succeeding photos but only until I close the camera app. Once I open up the camera app again, the LED flash stays on again until I take a photo.
I know it's kinda nitpicking but it's been annoying the heck out of me since I flashed CM7 (no other complaints really....wifi works alright and I even managed to get wireless tether to work in infrastructure mode with a WPA2 passkey). I even signed up on XDA just to know if somebody else is even experiencing the same issue.
Anyways, hoping someone out there's got an answer....
Are you just on CM7 RC1v2 or did you install a nightly on top?
I noticed the same in RC1 but some subsequent nightly fixed that. I'm currently on cm7-110813-2132-NIGHTLY btw.
Just RC1, still hesitant to flash a nightly build....Do you think extracting the the camera apk from that nightly and pushing it to the system/lib folder will solve the issue? I once extracted a camera apk from a nightly (not sure which) just to get touch to focus....it works alright but the flash issue is still there.
I don't know but you could try.
However, I've installed every other nightly and haven't had any issues. I'm currently on
cm7-110813-2132-NIGHTLY - but I've seen some commend on the CM7 main dev thread that people are also very happy with cm7-110808-0622-NIGHTLY-Jordan.
tried replacing the RC1 camera with the one from cm7-110813-2132-NIGHTLY....flash issue still there, although now touching the screen to focus will turn it off. However, on the camera's first start, the flash stays on again just the same. Oh well, guess I'll just have to live with this minor annoyance (on an otherwise excellent ROM) until RC2 or the Final build comes out Thanks for the reply twa_priv!

Issues w/ black screen....

I apologize if there is any easy fix for this or if there's already a thread, but I just recently started having this issue for about a week. Sometimes, when I turn on the screen it will quickly light up to the lock screen, but then turn blank right after; before I even get a chance to unlock the phone. The capacative buttons will completely stay light up and when I press them they vibrate so I assume the screen is still active.
Is this a common issue and is there an easy fix? I'm running the latest CM7 nightly build 258. I don't think that's the issue though because I just upgraded it today and before I hadn't upgraded the Nighly Build ROM in a couple weeks. I upgraded it today just to see if there was something wrong with that build.
Has anyone else experienced this?
Restore your previous ROM save
graymonkey44 said:
I apologize if there is any easy fix for this or if there's already a thread, but I just recently started having this issue for about a week. Sometimes, when I turn on the screen it will quickly light up to the lock screen, but then turn blank right after; before I even get a chance to unlock the phone. The capacative buttons will completely stay light up and when I press them they vibrate so I assume the screen is still active.
Is this a common issue and is there an easy fix? I'm running the latest CM7 nightly build 258. I don't think that's the issue though because I just upgraded it today and before I hadn't upgraded the Nighly Build ROM in a couple weeks. I upgraded it today just to see if there was something wrong with that build.
Has anyone else experienced this?
Click to expand...
Click to collapse
Are you using a custom kernel. If so are you under / overclocking or over / undervolting?
Nope. I'm running whatever kernel comes with the ROM and no undervolting or overclocking either.
Anyone....?
Have you done a restore?
I would try wiping dalvik-cache and the cache partition. If that dosent work i would wipe everything and do a fresh install of a different rom to determine weather it is rom related or hardware related.

hardware keys acting up all a sudden

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

[Q] GS III Home Button Issue

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.

[Q] Slim Rom Stable - Home button issues

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

Categories

Resources