Hi folks, running CM7 with Faux's kernel and the entire front of the phone becomes unresponsive at times, seemingly randomly. Side buttons still work, turning the screen off and then back on fixes the issues. Capacitive buttons stop responding too.
Is there any reason for this to happen? It seems to occur on every nightly I've ever used, and I believe on several kernels.
Updated with logcat taken from right after I turned the screen back on.
Old bump, but still looking for help on this matter.
I've narrowed it down to being a hardware issue. Before cutting out, the touchscreen will often make seemingly random presses (hitting random keys onscreen, for example) for a second, and then crap out.
Applying higher than comfortable force to the top third of the screen restores touch temporarily, but hitting the power button on and off is the only way to reliably fix it (if only for a minute or 2). I'm ready to shell out $40 for a new digitizer, but can anyone else suggest what might be up or alternate methods of fixing it?
If it's still under warranty then try to get a warranty replacement.
Волк said:
If it's still under warranty then try to get a warranty replacement.
Click to expand...
Click to collapse
Alas, I'm using a T-Mobile USA phone in Canada, so no warranty for me.
What are your frequency settings via setcpu? Maybe your min to max is too high of a jump causing instability.
dylyxcore said:
What are your frequency settings via setcpu? Maybe your min to max is too high of a jump causing instability.
Click to expand...
Click to collapse
816 - 216 on Faux's kernel. Happens on stock and UV.
I still think it's the touch module itself since physically squeezing the phone gets a response.
Sent from my LG-P999 using XDA App
Bring it up to 389(or 4-whatever, whatever's next) and see how that works.
Or try another kernel?
Although I'm sure these were things you've tried. I give basic possible solutions.
SefEXE said:
Bring it up to 389(or 4-whatever, whatever's next) and see how that works.
Or try another kernel?
Although I'm sure these were things you've tried. I give basic possible solutions.
Click to expand...
Click to collapse
Thanks, but I've already covered those bases :-(
Sent from my LG-P999 using XDA App
You need a new digitizer. Mine would do something similar. After replacing it, everything worked fine.
buru898 said:
You need a new digitizer. Mine would do something similar. After replacing it, everything worked fine.
Click to expand...
Click to collapse
Thank you. Will this do the job?
Related
Okay for a good month and a half I have been having an odd problem. Sometimes randomly my phone will start glitching and viberating randomly like I'm pressing the soft buttons below the sreen and sometimes that menu comes up like I pressed the menu button. Not the launcher. Ans also I can be in gallery and select a photo and it will viberate like I hit the back button and it will go back and I have to select it a few times before it stops. What could it be? It even done it on froyo
Sent from my SCH-I500 using XDA App
That happens to me every once in a while, the whole system will just hang and the menu will come up or the recent apps thing will come up multiple times and the phone will vibrate, then it just goes back to normal.
Sent from my SCH-I500 using Tapatalk
Yea. What's causing it
Sent from my SCH-I500 using XDA App
Could be a bad flash, or some app has created a conflict, seems to me I read there are a couple of apps that caused this. You could just reflash a different rom, see if that fixes it.
oka1 said:
Could be a bad flash, or some app has created a conflict, seems to me I read there are a couple of apps that caused this. You could just reflash a different rom, see if that fixes it.
Click to expand...
Click to collapse
I have FLASHED several times with several different things! And I use stock so its not the rom
How often do you pull your battery?
WankAttack said:
How often do you pull your battery?
Click to expand...
Click to collapse
once every few days why? I think its hardware not software. cause No matter what rom I have had even 2.2 and stock it still does it
hyelton said:
once every few days why? I think its hardware not software. cause No matter what rom I have had even 2.2 and stock it still does it
Click to expand...
Click to collapse
From my experience you can get some oddities such as this as a result of a bad flash (which re flashing would correct as stated above) so I'd say your assumption is probably correct and your problem may be with the hardware.
I don't want to ask the obvious question but no one has. Have you dropped it any? Or has it been exposed to any kind of water. I had a phone freak-out on me when usb port got a little wet from some rain.
Just when you think you have it idiot proof, they come out with a better idiot.
not been wet and its not a bad flash. Right now I'm trying out froyo again and it done it again last night. I'm a uscellular agent. And I have yet to have anyone else come I. With the same problem
Sent from my SCH-I500 using XDA App
hyelton said:
not been wet and its not a bad flash. Right now I'm trying out froyo again and it done it again last night. I'm a uscellular agent. And I have yet to have anyone else come I. With the same problem
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
I believe this happens on an undervolted kernel un areas of extremely low signal. Recently, it seems to be happening on any kernel. I hope this get's addressed in our real froyo release.
not been wet and its not a bad flash. Right now I'm trying out froyo again and it done it again last night. I'm a uscellular agent. And I have yet to have anyone else come I. With the same problem
Click to expand...
Click to collapse
It happened when I was on 2.1 as well, Usually only when I had a bunch of things running. Im an agent too! xD
OK my phone stopped for a few days I haven't had a case on it. Then today I pit my case back on it and it started doing it earlier for the first time in days. The case doesn't over the front of the phone at all
Sent from my SCH-I500 using XDA App
Yea, that sounds like it may be the case :s I've had it happen a couple times, but I thought it might just be like my fingerprint is over the button and keeps presseing it. I just wipe my finger over the bottom of the phone and it stops. Don't know if its the same thing.
Sent from my Froyo Mesmerize
I think you are right I've had the same issue and if youlook at the soft keys when it happens you'll see that one of the buttons thinks it's being pressed I think it's just a hardware issue cause like you said when you run your finger over the keys it stops.
Also, similar problem every once in a while when I'm trying to swype during a swype it acts as if my finger lost contact with the screen but I definitely didn't lift my finger abd it happens several times in a row until I lock the screen turning the touch screen off it seems to reset the touch sensors.
Swyped using USCC Mesmerize
cpfeifer said:
I think you are right I've had the same issue and if youlook at the soft keys when it happens you'll see that one of the buttons thinks it's being pressed I think it's just a hardware issue cause like you said when you run your finger over the keys it stops.
Also, similar problem every once in a while when I'm trying to swype during a swype it acts as if my finger lost contact with the screen but I definitely didn't lift my finger abd it happens several times in a row until I lock the screen turning the touch screen off it seems to reset the touch sensors.
Swyped using USCC Mesmerize
Click to expand...
Click to collapse
or it's a ghost, woooooooo!
I've experienced this issue before, although very rarely. Every time it has been the menu button and it always seemed to be in colder weather. I use a thin screen protector I picked up at a USCC store. Happens even more rare with EA11 leak however my screen brightness changes (occasionally) when I end phone calls and am in the middle of an app
Sent from my SCH-I500
I recently rooted my Inspire (2 days ago) and just today ive noticed that im getting dead spots on my touch screen. Its most noticeable when im typing something and one of the keys will hardly register. I will have to push multiple times, harder than I would normally have to for it to register. Rebooting the phone fixes the dead spot for a while, and then a new spot will have the same issue a little later. If anyone has any suggestions or and ideas on what could possibly be causing this I would really appreciate it.
What rom/kernel are you using? A lot of people were having that problem, including myself, and to my understanding it had something to do with the drivers. I believe Lee's latest kernel addresses this problem.
Sent from my Desire HD using XDA App
I've noticed this while using the CoreDroid ROM and the Gingerbread keyboard. I switched back to the HTC keyboard and deadspot is gone. So my guess is, its something with the GB keyboard.
Well I am using LeeDroid Rom. Does the regular rom itself not update the Kernel aswell?? Sorry if this is a dumb question, this was my first time rooting.
It's a well documented bug. It's hardware problems with inspires
Sent from my Inspire 4G using XDA Premium App
same here, using Coredroid V7(even before v7) and Lee Kernel 3.1.7 BFS.
same here.. its always the A and the O with almost every rom..
@OP:
This is a known touch screen drivers issue. Only way out is to press power for screen off, and then press again for screen on. I don't think any of our devs here can do anything about it (atleast I assume so, with no doubts about the abilities of our devs).
diablo009 said:
@OP:
This is a known touch screen drivers issue. Only way out is to press power for screen off, and then press again for screen on. I don't think any of our devs here can do anything about it (atleast I assume so, with no doubts about the abilities of our devs).
Click to expand...
Click to collapse
I have found that doing a screen rotation works too
chicobrown726 said:
I have found that doing a screen rotation works too
Click to expand...
Click to collapse
Great! I generally (close to 95%) have my screen rotation turned off, so didn't notice it. Thanks for the idea though.
Since yesterday, my screen has been flickering randomly, sometimes till the whole screen turns black. To resolve this, I have to do a battery pull and restart.
How can I go about checking if this is hardware or software? It doesn't happen on any specific app. But, if it's hardware then it wouldnt be good after a battery pull right?
Any advice or help is greatly appreciated. Thanks!
have you tried a different rom?
ranteo said:
How can I go about checking if this is hardware or software? It doesn't happen on any specific app. But, if it's hardware then it wouldnt be good after a battery pull right?
Click to expand...
Click to collapse
You could always do a full reset and see if that cures the issue.
However, just because a battery pull fixes it, that doesn't rule out hardware. The act of taking the cover off (assuming you're doing that), removing/replacing the battery, and putting the cover back on does jar the device a bit. If you've got a loose connection or cable going bad, that could be enough to coax it into working for a bit.
xmc wildchild22 said:
have you tried a different rom?
Click to expand...
Click to collapse
Yea, switched a different rom but still the screen flickers.
jonnycat26 said:
You could always do a full reset and see if that cures the issue.
However, just because a battery pull fixes it, that doesn't rule out hardware. The act of taking the cover off (assuming you're doing that), removing/replacing the battery, and putting the cover back on does jar the device a bit. If you've got a loose connection or cable going bad, that could be enough to coax it into working for a bit.
Click to expand...
Click to collapse
what do you mean by a full reset? Restore to stock rom?
After trial and error, I realize the screen flickering stops when the keyboard slides out. No screen flickers happen when the keyboard is slide out. Does this most definitely mean it is a hardware problem?
My screen was doing this yesterday as well. I'm thinking about going back to stock and getting it replaced since I also have a few dead pixels.
Sent from my HTC myTouch_4G_Slide using xda premium
2G1J said:
My screen was doing this yesterday as well. I'm thinking about going back to stock and getting it replaced since I also have a few dead pixels.
Sent from my HTC myTouch_4G_Slide using xda premium
Click to expand...
Click to collapse
Actually, how do you go back to stock? I did factory reset in settings, but after reboot, my software version still shows virtuous inquisition under the build number. How actually do I go back to stock?
ranteo said:
Actually, how do you go back to stock? I did factory reset in settings, but after reboot, my software version still shows virtuous inquisition under the build number. How actually do I go back to stock?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=17424340&postcount=24
2G1J said:
http://forum.xda-developers.com/showpost.php?p=17424340&postcount=24
Click to expand...
Click to collapse
any one have a fix yet for this ???
If it's any similar to the HTC mytouch 3g slide, it sounds like your flex cable is about to go out. If you have a warranty, back it up and get it replaced. If not, back it up and upgrade or try to replace the flex cable. Good luck.
Sent from my XT1053 using xda app-developers app
So what happens every so often when I hit the unlock button is that my phone screen won't come on. Everything else works fine but the screen isn't on so obviously I can't see what's happening. Is this happening to anyone else or is this a possible hardware malfunction? It's been happening with several CM10 based roms over the last month and a half. It's gotten progressively more frequent.
Sounds like you're getting what they refer to as SOD. Its buggy software in CM10 that will hopefully be sorted out soon.
I agree, likely SOD. If your kernel allows control of CPU voltages, I would bump them up for the lower clock speeds. Seemed to help for me.
Sent from my SCH-I535 using xda app-developers app
Which "unlock button" are you hitting. It's a common issue with the CM10 ROMs that if you hit the home button when the phone is locked and the screen is off that it doesn't bring the phone to life as it should. I have it happen all the time and just have to hit the home button several times or hit the power button to unlock it. I haven't tried seeing if the phone worked with the screen off like you mentioned I've always just tapped the home button till it lit up finally.
Slacker101 said:
So what happens every so often when I hit the unlock button is that my phone screen won't come on. Everything else works fine but the screen isn't on so obviously I can't see what's happening. Is this happening to anyone else or is this a possible hardware malfunction? It's been happening with several CM10 based roms over the last month and a half. It's gotten progressively more frequent.
Click to expand...
Click to collapse
This drives me crazy and it has me considering using another ROM. Is it fair to call this "stable" release so if this keeps happening? Just food for thought.
brando7010 said:
I agree, likely SOD. If your kernel allows control of CPU voltages, I would bump them up for the lower clock speeds. Seemed to help for me.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Realize this post is over a year old but it helped me fix my issue. I used Benchmark and Tuning (available for free on play store) which allows you to choose a few types of governors one of which was on demand. hasn't black screened since. Thank you guys.
Hi!
For past two-three days I am experiencing this problem. Touch sensor just randomly stops working. Top side of the screen is very very difficult to control, sometimes even impossible. Sometimes it feels like sensor recognizes multiple touches at the same time which results random pages or menus opening and closing.
After short usage with screen up or after long downtime (like when I go to sleep) I'm not able to use sensor at all. I cannot shut down the alarm clock, I cannot answer the calls. I still can use the power button tho.
Now what is the most retarded is that nearly all that vanishes after phone reboot. The only thing that remains is that top side of the screen is still quite difficult to control. For example I cannot open that top slide-bar comfortably. I have to slowly move my finger over the screen in order to do so.
Phone specifications:
Custom ROM: Cyanogen 11-20140702-nightly
sdcard partition type: FAT32
bootloader version: 2.14
Security-OFF
CID: 11111
Custom recovery: TWRP 2.7.0.8
P.S.: tried to re-insall ROM did not help. Phone havent been damaged by any means recently.
Did u over or under clock..flash a mod to control kernel? That's what it sounds like
I'm assuming you're using the stock kernel? What you're describing is an ongoing issue with the CM kernel, flash a custom kernel (Torched or Bubba) and your problem should cease.
Sent from my Evita
Wow. I never knew there was an issue with stock kernel...what's causing that anyways?
Damn it..
I'm a newbie with all that kernel flashes. Any How-To for noobs? Guide or something? I have found Tourched Kernel for KK thread (I suppose it stands for Kit-Kat?), but it's quite puzzling for me with all that voltages.
P.S.: What caused such random issue all of the sudden? Have been using CM for quite a bit of time already. Got that issue just 2-3 days ago
Look under Tims sig
marknoll said:
Wow. I never knew there was an issue with stock kernel...what's causing that anyways?
Click to expand...
Click to collapse
I have no idea what's causing it, I do know that using a custom kernel always fixes it for me though.
SoulSurvivors said:
Damn it..
I'm a newbie with all that kernel flashes. Any How-To for noobs? Guide or something? I have found Tourched Kernel for KK thread (I suppose it stands for Kit-Kat?), but it's quite puzzling for me with all that voltages.
P.S.: What caused such random issue all of the sudden? Have been using CM for quite a bit of time already. Got that issue just 2-3 days ago
Click to expand...
Click to collapse
Flashing a kernel is similar to flashing a ROM, if you want instructions just check the How-To Guide For Beginners thread in my signature.
Sent from my Evita
timmaaa said:
I have no idea what's causing it, I do know that using a custom kernel always fixes it for me though.
Flashing a kernel is similar to flashing a ROM, if you want instructions just check the How-To Guide For Beginners thread in my signature.
Sent from my Evita
Click to expand...
Click to collapse
Meh, I have updated kernel to 3.4.86-Torched-KK.B4.3+
Problem is still here.
Still cant open top slide menu properly. It is just weird, it really seems like some sort of damage to very top side of the screen. But i didnt hit it or anything like that. Screen itself without any visible damage or even scratches, cuz im using screen protector. Gonna see if I can at least answer the calls properly without sensor goin full nuts.
update:
That's definitely a software issue. If i turn the phone around so screen would get rotated that "damaged" area works just fine. What the **** is going on? It started so randomly
You can try flashing a different ROM, or rolling back to the last build of CM that you remember being ok.
Sent from my Evita
SoulSurvivors said:
Meh, I have updated kernel to 3.4.86-Torched-KK.B4.3+
Problem is still here.
Still cant open top slide menu properly. It is just weird, it really seems like some sort of damage to very top side of the screen. But i didnt hit it or anything like that. Screen itself without any visible damage or even scratches, cuz im using screen protector. Gonna see if I can at least answer the calls properly without sensor goin full nuts.
update:
That's definitely a software issue. If i turn the phone around so screen would get rotated that "damaged" area works just fine. What the **** is going on? It started so randomly
Click to expand...
Click to collapse
Maybe reflashing the ROM and the kernel would be a good idea. I've had to do that too. Its annoying,but sometimes I had to do that. Good luck.
Nop..
I've done the factory reset. Installer fresh ROM, Gapps and kernel.
Same ****. I Guess That is indeed hardware damage to sensor.
/sadpanda
There's a way to diagnose it. Download an app called sensor on play store