[Q] Glitch where capacitive screen becomes oversensitive/non-responsive - Verizon Droid Incredible 2

I've started noticing recently that my Incredible 2 touchscreen occasionally goes berserk. All of a sudden it will stop properly responding to my finger and instead whatever is on the screen will start flailing about e.g. a webpage will move around more or less uncontrollably or a list will move up and down in short spurts and sporadically. I almost feel like the movement can be influenced by hovering a finger over the screen without actually touching, almost as if the capacitive screen can sense the electricity from that far. The four capacitive buttons stop doing anything and produce no haptic feedback when touched.
I've found that the surefire way to resolve this is to press the power button to turn off the screen, and then press it back to get to the lockscreen. At that point, everything starts working normally again.
I have been messing around with ROMs, but this problem has occurred on CM7, Mikrunny, and a newly flashed stock.
Any ideas?

Do you happen to be charging the phone when this happens?

I am not. I've read up a bit about that, but my touchscreen craziness starts when it is in my hand, not connected to the charger.

Do you have a custom rom running? If so which one? Did you do a full wipe before flashing?

Currently, Mikrunny. Before flashing a Rom, I would always wipe data, wipe cache, and wipe dalvik cache.

Maybe static electricity? It would explain the hypersensitivity but not really the capacitive buttons not responding.
Sent from my Incredible 2 using XDA App

Do you all think this has to do with flashing different ROMs, or was this type of problem gonna come up regardless of that?

LeoBloom. said:
Do you all think this has to do with flashing different ROMs, or was this type of problem gonna come up regardless of that?
Click to expand...
Click to collapse
Based on the fact that it is happening with different roms it seems to me like it is not related to flashing roms.
Sent from my Incredible 2 using XDA App

Good news. I figured that since most of these issues regarding crazy touchscreens was due to a 3rd party charger being used, then it was likely that it had something to do with the power the phone was receiving, specifically from my battery. For the last 2 or 3 days, I've tried using my phone with the old standard battery (as opposed to my extended), and I haven't run into the problem since. Eventually, I will move back to the extended, but I'm liking the thinness of my phone way too much to switch

Related

[Q] Screen won't stay off.

Has anybody had an issue where when they press the power button, the screen will turn off for a moment, then come right back on? And if so, does anyone know a solution? I've looked around on the forums a bit, and its a problem on other phones where the screen has to be at at least 40% brightness, but it happens to me no matter how high or low the brightness setting is. Running ACS 1.0.2, but it has happened on other ROMS before, so i doubt it is a ROM issue.
I have had this happen too, but only in CM 7. And just figured it was because that rom is in the alpha stage right now. I have not had it happen in any other rom so far. When it was happening it was only some of the time. Was never able to figure out what the differences were when it would and wouldn't happen. Seemed like it was just random.
Sent from my SPH-D700 using XDA App
I've since found this happens very often when the brightness is up all the way, and the lower the brightness, the less it happens. Could this be a software problem?
I had this happen a few months ago. I wasn't sure what was causing it. At first it was turning on the lock sound, and the sound would play after the screen shuts off. Then the sound would kick the screen back on. I believe I changed ROM later and it never happened again. If you are on a custom ROM, maybe try reflashing?
I have had the exact same thing happen on 2 different Roms. Just wipe and flash and it fixes the problem.
BloodThirstyEmu said:
I have had the exact same thing happen on 2 different Roms. Just wipe and flash and it fixes the problem.
Click to expand...
Click to collapse
Unfortunately that only lessened it, not fixed it. It still happens enough that I leave the brightness down. Tried multiple times. :/
This still happens on a fresh stock install of EC05. Could this be a hardware issue that I should get checked out?

[Q] G2 touchscreen delayed or unresponsive after CM7 update. Solutions?

This is my first time posting. I know how annoying reposts are, so I tried to find if anyone else had the same problems I have. Unable to find an answer, I seek a solution to my strange problem...
I flashed CM7 three days ago. Before flashing, I did a full factory reset, wiped cache, etc. I also performed a backup of rom, which was at the time CM6. Everything worked without a hitch for these past three days. I installed new programs, really enjoyed the new features. However, today, the screen suddenly became unresponsive.
It acts as though I am long-pressing something when I am not. It will not register even hard taps and when I try to hit the home key it brings up the most recent apps list as though I long-pressed. I have reset, but it keeps doing this. When I try to use an app where scrolling is required, it bounces back to the spot I started scrolling. Very frustrating. Any solutions?
At first I thought it was from installing swype beta, but after removing it completely, resetting, and reflashing, the screen continues to act up.
Flash your backup and see if you still have the same problem
Sent from my HTC Vision using XDA Premium App
Spastic909 said:
Flash your backup and see if you still have the same problem
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
Hey thanks for your suggestion. I've tried it but the screen problem continues. I even tried going back to the stock rom. Do you think it's a hardware issue?
Having the same problem using MexDroid for the G2...have to resort to the trackball half the time because the touchscreen doesn't work right or at all.
I reinstalled the ROM twice already and it keeps acting up at some random point after installing a few apps (none of which affect the touchscreen as far as I know). Tried clearing cache, dalvik cache, and fixing permissions...nothing. Happens regardless of overclock settings too.
magus57 said:
Having the same problem using MexDroid for the G2...have to resort to the trackball half the time because the touchscreen doesn't work right or at all.
I reinstalled the ROM twice already and it keeps acting up at some random point after installing a few apps (none of which affect the touchscreen as far as I know). Tried clearing cache, dalvik cache, and fixing permissions...nothing. Happens regardless of overclock settings too.
Click to expand...
Click to collapse
It's nice to know I'm not the only one with this problem... i.e. misery likes company... but I'm also sorry to hear that you have the problem, as well. There seems to be nothing that I can do at the moment. Since the phone is still under warranty, I guess I could just flash the original rom, factory reset, and send it back for a new one. I'd rather find a solution, though, in case it happens again.
wronskishin said:
It's nice to know I'm not the only one with this problem... i.e. misery likes company... but I'm also sorry to hear that you have the problem, as well. There seems to be nothing that I can do at the moment. Since the phone is still under warranty, I guess I could just flash the original rom, factory reset, and send it back for a new one. I'd rather find a solution, though, in case it happens again.
Click to expand...
Click to collapse
The weird thing is that it only happens sometimes...like, sometimes I'll get 100% accurate/responsive touchscreen use, while other times I can pinch all I want and never zoom in. I think it might have something to do with my lowering the screen density - right now I have it at 140, and earlier at 190, and it seems that when I have the stock 240 or the 190, I have better luck with the touchscreen than with at 140...but the usefulness of the lower screen density outweighs the better touchscreen for me.
magus57 said:
The weird thing is that it only happens sometimes...like, sometimes I'll get 100% accurate/responsive touchscreen use, while other times I can pinch all I want and never zoom in. I think it might have something to do with my lowering the screen density - right now I have it at 140, and earlier at 190, and it seems that when I have the stock 240 or the 190, I have better luck with the touchscreen than with at 140...but the usefulness of the lower screen density outweighs the better touchscreen for me.
Click to expand...
Click to collapse
How do you change the screen density?

[Q] Forced Reboot when Screen Times out - All ICS roms

Hi All,
I've been able to successfully install many of the ICS roms that are out there. However my problem isn't with the home button, search, data or echos. Whenever my screen times the phone just reboots itself and continues to do so. If I lock the screen myself the same situation happens. I've properly wiped before installing data>cache>delvik>superwipe>kernel cleanse>install>fix permissions>reboot>10min wait and reboot. If tried going back in and fixing permissions too, but nothing seems to fix this issue. The only solution around is keeping the screen on full time or if I leave it plugged in, then the screen can lock without rebooting.
Any suggestions? Currently running IML74K_Ics_Perfection
Did you try under clocking or undervolting
?
Sent from my SGH-T989 using Tapatalk
I have not. Though i thought it might get too low during idle causing it to power down
If it does get too low then bump it up a bit and see what happens. If not then I'm stumped. In all honesty I would simply go back to gb. ICS has just to many bugs for me to bare. Really you're not missing out on much besides multitasking and chrome perhaps.
Sent from my SGH-T989 using Tapatalk

Random Reboots - FF18

I'm running the stock ICS FF18, rooted. All seemed reasonably well for the first couple weeks, now the damn thing wants to randomly reboot.
I tried wiping, reinstalling the stock ICS, but the problem returned. Reboots happen maybe upwards of a dozen times a day. I've tried isolating the problem but unable to find a common variable...sometimes it happens when I'm in the middle of something, like web surfing or texting. Sometimes it happens when I press the power button, sometimes it happens when it's just sitting there not being touched, sometimes it happens when plugged it, sometimes when not plugged in.
I can't think I have a bad install twice and I'm not finding much on the forums here about others with a similar problem with the stock ICS. So I'm thinking either an app is being a b1tch and causing problems or perhaps something related to the battery? If there was one common theme, it does always happen later in the day or at night after the battery is down below 50%.
Does anyone have thoughts, ideas, suggestions on the likelihood of a bad battery or perhaps someone experienced something similar?
waltcoleman said:
I'm running the stock ICS FF18, rooted. All seemed reasonably well for the first couple weeks, now the damn thing wants to randomly reboot.
I tried wiping, reinstalling the stock ICS, but the problem returned. Reboots happen maybe upwards of a dozen times a day. I've tried isolating the problem but unable to find a common variable...sometimes it happens when I'm in the middle of something, like web surfing or texting. Sometimes it happens when I press the power button, sometimes it happens when it's just sitting there not being touched, sometimes it happens when plugged it, sometimes when not plugged in.
I can't think I have a bad install twice and I'm not finding much on the forums here about others with a similar problem with the stock ICS. So I'm thinking either an app is being a b1tch and causing problems or perhaps something related to the battery? If there was one common theme, it does always happen later in the day or at night after the battery is down below 50%.
Does anyone have thoughts, ideas, suggestions on the likelihood of a bad battery or perhaps someone experienced something similar?
Click to expand...
Click to collapse
Any special wi-fi config? (That's the culprit in my case.)
garwynn said:
Any special wi-fi config? (That's the culprit in my case.)
Click to expand...
Click to collapse
No...never installed the hotspot hack, did have foxfi installed, but did not reinstall after reloading ff18.
im also having the same problem as well, and the problem has became worse and worse,what started off as once or twice a day,is now at least occurring every 10 min.I think im about to downgrade right now to stock gingerbread and see what happens
My phone has always had some amount of random "poweroffs" (not really reboots, I pick up the phone expecting it to be on and it boots from scratch instead). However its much more frequent on ICS (FF18/FH13).
rocket321 said:
My phone has always had some amount of random "poweroffs" (not really reboots, I pick up the phone expecting it to be on and it boots from scratch instead). However its much more frequent on ICS (FF18/FH13).
Click to expand...
Click to collapse
U can always unroot back to el29(gingerbread)i was having the same problems and now i can enjoy my phone
Sent from my SPH-D710 using xda premium
I had that issue on AOKP M6, then realized my power button was actually broken. It would reboot the phone because it was actually stuck down internally. Had to get a new phone.
Sent from my SPH-D710 using xda app-developers app
R0CKSTAR3N3RGY said:
I had that issue on AOKP M6, then realized my power button was actually broken. It would reboot the phone because it was actually stuck down internally. Had to get a new phone.
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
The power button seems to be a common cause of random reboots and that's what I'm leaning towards now as no other software fix has resolved the problem. Supposedly Sprint ordered me a replacement to swap out phones. I'd definitely recommend trying a different Kernel if on FF18 and if that doesn't fix it, try rolling back to EL29.

[Q] Galaxy Nexus Sleep of Death

Problem: Cannot turn on the screen by pressing the power button sometimes. The screen is black or very dim, I cannot tell. One can see nothing on the screen, and it doesn’t accept any touch input, either. The phone still rings if there’s an incoming call. If this happens, the following several presses (about 10 - 20) on the power button will probably lead to a reboot. The “screen auto-rotate” and the proximity sensor may fail after the reboot, but will recover after a manual reboot.
Frequency: Fewer with higher Rom version. About once per day for 4.3.
Other description:
 The problem frequently happens when I just take the phone outside my house/office, and seldom happens when the phone just stays somewhere.
 The problem seems to be irrelevant to the remaining battery capacity or the uptime, but it never happens when charging.
 The problem seems to be irrelevant to the Apps installed.
 The problem seldom happens in the first 3-4 days after flashing a Rom, but happens more and more frequently as time goes by. My guess is some cache is stuffed by some trash, which causes the problem. The phone may be fine as long as the trash can be cleaned up on a regular basis.
 I manually reboot my phone at most every two days.
Solutions tried, but don’t work
 Flashing official ROMs 4.0.4, 4.1.1, 4.1.2, 4.2.2 and 4.3 following the procedure “adb reboot bootloader; fastboot oem unlock; flash-all; fastboot oem lock”, without google wallet, not rooted.
 Turning off the auto-brightness control, as suggested by some post on the Internet.
Does it look like it goes to standby normally or does the screen show gibberish and then turns off?
Sent from my Galaxy Nexus using XDA Free mobile app
Thymo said:
Does it look like it goes to standby normally or does the screen show gibberish and then turns off?
Sent from my Galaxy Nexus using XDA Free mobile app
Click to expand...
Click to collapse
Thank you very much.
I think it's standing-by normally even through the screen is black (or very dim, I cannot tell), since it rings if there's an incoming call. I can see nothing from the screen, and I don't think the screen accepts any touch input, either.
Does this answer your question? Thank you.
Bobby_yan said:
Thank you very much.
I think it's standing-by normally even through the screen is black (or very dim, I cannot tell), since it rings if there's an incoming call. I can see nothing from the screen, and I don't think the screen accepts any touch input, either.
Does this answer your question? Thank you.
Click to expand...
Click to collapse
Thanks.
Was just asking if you had gibberish yes or no. In that case i've got a different issue than you (Suspecting f*cked GPU).
Have you tried a different ROM/Kernel combination maybe it's related to that.
Thymo said:
Thanks.
Was just asking if you had gibberish yes or no. In that case i've got a different issue than you (Suspecting f*cked GPU).
Have you tried a different ROM/Kernel combination maybe it's related to that.
Click to expand...
Click to collapse
No.
No, I just tried the official ROMs. Any suggestion?
Perhaps it's just busy in the background and running low on RAM. Give LagFix a try. Sorry can't link atm as I am on mobile...
eKeith said:
Perhaps it's just busy in the background and running low on RAM. Give LagFix a try. Sorry can't link atm as I am on mobile...
Click to expand...
Click to collapse
Thanks a lot. I'm trying it.
Bobby_yan said:
Thanks a lot. I'm trying it.
Click to expand...
Click to collapse
LagFix does NOT help in my case. Any other suggestions? Thanks.
I've also had this blank screen with calls still ring issue for as long as I can remember, nearly 2.5 yrs.
I've always suspected it's my ROM and so I'd try out another ROM'S, BUT no other ROM works like how I'd like, so I always come back to my ROM.
It doesn't happen every single day, but it does happen very often.
I've tried using apps that auto reboot daily, but eventually this blank screen issue will return.
Unfortunately I can't seem to find any solution, so I just put up with it, it's like the 1 only flaw with my ROM.
&
Not to be at all rude, but I'm really glad op has had this issue from testing other versions of Android, cause then at least I know I don't need to give up my great tablet mode ROM.
LOL
I think I've finally found a work around for this screen of death.
Using Exposed, download/install this module/extension:
Disable Proximity
http://repo.xposed.info/module/com.mrchandler.disableprox
It does exactly what it's name is and ever since then I've not once had to remove my GN battery to work again because the screen went completely dead.
NVM
Screen still goes dead.
Anyone find an actual fix to this?
isajoo,
I had pretty much the same problems with my Galaxy Nexus running CyanogenMod 11 M12.
It got better by doing the following :
Blowing dry air in the earpiece… though the proximity sensor is clearly beside it. Can't do any harm though, I guess.
Settings/Applications/All/menu/Reset applications preferences (or whatever that's called in english) : that seemed to do a lot of good to my phone ! However, it's a very unsatisfactory answer on a technical point of view, as I still don't know WHAT was precisely needed. It's a "magic wand" solution for which I can't give an explanation.
Not specifically related, but greatly helped my phone in the responsiveness area : Trimmer (fstrim) (https://play.google.com/store/apps/details?id=com.fifthelement.trimmer), an updated version of LagFix that you may already know
Hope that helped !
(I wanted to try http://www.androidlegend.com/how-to-perform-proximity-sensor-calibration-on-any-samsung-phone/ as well, but apparently, /sys/class/sensors/proximity_sensor/prox_cal does not exist on my phone…)

Categories

Resources