It only happens when my phone is plugged into the charger. Sometimes, when I plug in the phone and continue to use it, I'll get random touch actions on the screen during intentional touch actions. Or I'll hit the back button and feel multiple vibrations followed by it acting like I swiped up from the back button. Unplugging the phone from the charger causes the issue to immediately disappear.
I think it's related to the firmware, as I don't recall it happening before I updated to the latest T-Mobile firmware. And it's done it across multiple ROM's and kernels, so it's not that either.
Has anybody else noticed this issue?
The fact that I'm the only person this is happening to, kinda worries me... lol.
I have faced that issue
Hello there,
I've just posted the same issue yesterday with no answer either.
Are you using the dot case? If I use the phone with no case it works just fine while plugged.
http://forum.xda-developers.com/htc-one-m8/help/viper-one-screen-failing-charging-t2906474
Hope somebody can give some light on this.
Cheers.
Related
anyone had problem with the screen not responding after waking up?
There's no way to turn off the phone / make it respond unless to unplug the battery and plug it in again. Had this problem on the first GN and my second replacement GN.
Yep, happened to me the other day as well. There was a crash right before which made the phone reboot. Once it came back, the hardware buttons responded fine but the touchscreen was dead until a battery pull.
Hasn't happened since though.
Had this at lunch today also had it a few days ago.
When returning from sleep the touch input seems to be completely unresponsive.
I left mine for a while to see if it recovered, it did, it came up with the crash report for "System Process" The screen was then responding fine.
Weird. This is indeed different to the sleep of death, because the screen comes on.
Although maybe it's related in some way?
This just happened to me, and so I googled to find an answer. It thankfully led me here. It's like you guys described: I just tried unlocking my phone, but the screen was completely unresponsive. Not a single touch would register, even when trying to touch the Power Off option.
I read robaldred's comment, so I decided to try the waiting game. Thankfully, after a few minutes the screen just came on and the device was ready to use. I don't believe I saw a crash report though.
I hope this won't become a serious issue. I'd hate to be stranded at a point when I need to use my phone.
I had this problem too. have you guys used custom notification sounds?
Sent from my Galaxy Nexus using XDA App
I had this exact problem and I found it was due to Juice Defender (I have the Ultimate version as well). It kept happening after I installed and but since removing it over a week ago no problems.
Just had it happen here, had to pull batt. Using BatteryXL but will keep it on and see if it happens again.
Hello,
For the last few days now my phone keeps randomly pushing the menu bottom for no reason!? I've tried several roms and I'm having the same issue. I have one of those expensive screen protectors on, but I don't think that is the issue. Sometimes all of the compasitive buttons lock up and I have to lock the screen and then unlock it for them to get back to working?
androidguy1991 said:
Hello,
For the last few days now my phone keeps randomly pushing the menu bottom for no reason!? I've tried several roms and I'm having the same issue. I have one of those expensive screen protectors on, but I don't think that is the issue. Sometimes all of the compasitive buttons lock up and I have to lock the screen and then unlock it for them to get back to working?
Click to expand...
Click to collapse
I have this same issue. I've done some research and it appears to be a hardware glitch that happens when you have low signal. I've seen some reports of people bringing up the issue with Sprint/Samsung and they will replace the phone. I haven't taken the time to try that yet, since it only happens very infrequently for me.
lol awesome, this started happening to me maybe 2-3 weeks ago and i had thought i sat down too hard on my phone and messing up the menu button. originally i thought i was able to replicate the problem just by holding the phone vertically and rocking it back and forth. i'm glad to see others are having this same issue (well not really glad, just relieved its not a hardware issue).
i am experiencing the same issues the OP is.. menu button randomly pressing itself and all buttons being locked up requiring a lock screen then unlock to get things back to working.
andermic said:
I have this same issue. I've done some research and it appears to be a hardware glitch that happens when you have low signal. I've seen some reports of people bringing up the issue with Sprint/Samsung and they will replace the phone. I haven't taken the time to try that yet, since it only happens very infrequently for me.
Click to expand...
Click to collapse
can you point me to the other reports of this issue?
Thanks guys. I just don't have the time to take in my phone in. I normally have about 3 or more bars of service and it was still locking up on me. it's getting really annoying. Maybe I can just call it in? Who knows? They always give me a hard time! If anyone finds a better solution please let me know. Thanks!
Hi,
I have:
Sony Xperia Z1 Compact
Rooted
CyanogenMod version 11-20141112-SNAPSHOT-M12-amami
Android version 4.4.4
Kernel version 3.4.0cyanogenmod-g1b20e398 [email protected] #1
Build number cm_amami-userdebug 4.4.4 KTU84Q a265284510 test-keys
My phone's screen has the annoying problem of sometimes not waking when I press the power button (while the phone is turned on). The phone is still on, but doesn't respond to input. I can call it, but nothing happens. I can connect the charger, but it doesn't respond.
I did not experience the issue before rooting. After rooting and installing CyanogenMod, the problem occurred perhaps 1-2 a week.
Recently I encrypted my phone. After that the problem has become much more frequent. The screen is now unwakable roughly 2-3 times a day, some times even more!
The only solution I have found, it to either turn the phone off via the red off button next to the SIM card, or by rebooting it by holding the power button in for so long.
The issue is extremely annoying, especially after it started occurring 2-3 times a day.
I have tried searching for similar issues, but haven't found any solutions.
I have tried changing the brightness levels so the max level is 99% instead of 100%, as someone had suggested, but that hasn't made any difference. Unscrewing the phone and cleaning the proximity sensor, as someone else had suggested, is something I haven't tried yet, as I don't feel competent enough to unscrew the phone.
The phone used to have the protection plastic provided from the fabric, but I tore that off not too long ago. No change in behaviour.
I have not managed to find one special event that triggers this behaviour or reproduce the issue on demand.
Hopefully someone will have some tips as to what I can do to solve this issue. Thanks in advance.
Any modifications on the kernel? Like special governors or under/overclocking?
As you are using a custom ROM the clear advise here is: try out with stock ROM and see if the problem is still there.
If not, it is a problem with the ROM.
I'm having the exact same problem. I flashed cm11 snapshot two days ago, and today my screen wouldn't wake no matter what.not even a restart would solve the issue, cause the moment the phone goes to sleep after a boot, that was the last time the screen was on. I'm following this thread in case somebody comes up with a solution.
hi there, my phone is acting the same way as yours described. Mine is rooted on stock lolipop and it never happened before although i had a replacement unit and the one before that acting the same way. Pressed the power button and nothing happend regardless screen on or off. Had to do hard reset and it worked for like 1 or 2 days. I went to sony talk forum and ppl seems to say it a bug since the phone released. If anyone got anything would be great help. Thanks
Hey there guys , I've been searching through the forum topics about my issue but so far I've found nothing close to my scenario.
A few months ago I bought my first HTC phone (M8). Its a great device for sure , despite the fact that I had to return it back twice.
First time it was a faulty microphone , so they sent me back a brand new device. Great isn't it ?
However recently I've noticed a few .... let me call them 'glitches' .
Let me give you some details on what I've experienced with the device:
Despite the issues that i'm going through ... the phone works great, but...
Sometimes the screen wont turn on when I'm receiving incoming calls (same goes for the alarm clock) but the phone is able to recognize touches - i've managed to pick up the call when I swiped the screen in the area where the "green" answer button appears .
The above issue doesnt happen so often but the thing that bothers me is the unlocking issue.
At first I thought that it was stuck or faulty power button.
When the phone is idle for some time and I pick it up and press the unlock button ... nothing seems to happen I've tried pressing it hard ... i've tried pressing it gently ... i've tried pressing it multiple times until the screen wakes up .
Same goes for motion launch unlocking .
When I use motion launch to unlock it the phone only gives me a vibration feedback ... and thats it until I try harder to bring the screen back to ''life'' .
(I can also press my security pattern buttons while the screen is dead and feel the phone vibrating , BUT NOT ALWAYS , sometimes is just .. dead )
I already sent the phone back describing the same problems and they just flashed the firmware , which did not fix any of the issues.
Stock Rom android 5.0.1 , not rooted
Soo what do you guys think? What can I do next .. is it android bug or a faulty unit ?
is it possible to be a sensor problem (proximity , accelerometer)
Already tried factory reset and dalvik cache wipe.
Any advice would be useful.
Thanks for taking your time .
Cheerz
I have the same issue. There are times it takes me hitting the power button 20 times for it to finally light up but I can press buttons with it black. The weird thing is it does it on every single ROM but I havent noticed it on Stock...maybe I'm not using stock enough to see. I'll probably throw stock on there today and take it into sprint and let them replace it.
I have the same problem whether it's on stock or custom ROM (KK or L). I am pretty sure this is a hardware problem. Unfortunately, my m8 is out of warranty so HTC won't fix it for free. I read it some where that it could be a faulty proximity switch so shining a light beam to the top part of the phone may wake up the screen. I haven't tried it yet because every time it happens, I don't have a flash light handy. It is an annoying problem to say the least.
When this happens, I pushed the power button, the volume up button, and swiping the screens. Eventually the screen would wake up and every thing works fine... until the next time.
Its a ****ing pain in the ass.
however none of the sensor reading apps report a faulty/stuck sensor.
the wors thing... I've already sent my phone for repair, describing the problems in details. .. and it took them a whole f*cking month to bring it back to me with no results.
I don't think they will replace it because its a problem that takes time to be experienced...and no one is going to wait for it to happen. ...
Any other ideas?
Should I wait for android 6.0 or should I try a custom rom too see if these problems presist.
Fml I love the phone but this is frustrating.
I have the same problem I think. I just bought an M8 on Ebay. I am S-off, unlocked and rooted, using the Viper Rom currently. I have also tried AICP, the stock Tmobile Rom and a few others. Same issue.
If I double tap, I feel the screen vibrate, but nothing comes on. Then, I keep pushing power button a few times. Sometimes it comes on and sometimes I am too impatient to wait, so I just hold power and volume up.
I also know that the phone internals come on, because after that vibration, I swipe up and push the screen a few times. Then, when I am fiddling with the power button and it does come on, I do see that there is an app already on the screen.
I think this is a rare issue, as I haven't even been able to find many posts regarding this. I may have to get a new one if this keeps going on so bad.
Ozger said:
I have the same problem I think. I just bought an M8 on Ebay. I am S-off, unlocked and rooted, using the Viper Rom currently. I have also tried AICP, the stock Tmobile Rom and a few others. Same issue.
If I double tap, I feel the screen vibrate, but nothing comes on. Then, I keep pushing power button a few times. Sometimes it comes on and sometimes I am too impatient to wait, so I just hold power and volume up.
I also know that the phone internals come on, because after that vibration, I swipe up and push the screen a few times. Then, when I am fiddling with the power button and it does come on, I do see that there is an app already on the screen.
I think this is a rare issue, as I haven't even been able to find many posts regarding this. I may have to get a new one if this keeps going on so bad.
Click to expand...
Click to collapse
I am experiencing the exact same issue with my M8. I have seen a lot of people stating it may be a hardware fault related to heat and internals but something about how it reacts seems software related.
I really hope someone who has fixed or uncovered the reason comes forward. At this rate I may be switching back to a S4 LTE-A.
Soulink said:
I am experiencing the exact same issue with my M8. I have seen a lot of people stating it may be a hardware fault related to heat and internals but something about how it reacts seems software related.
I really hope someone who has fixed or uncovered the reason comes forward. At this rate I may be switching back to a S4 LTE-A.
Click to expand...
Click to collapse
I think it IS hardware related. I was able to return that one and got another M8. No problems at all.
Hey hey,
I'm experiencing the follow issue with my Pixel 3a XL. I put it onto charge at bedtime, and when I got up in the morning after the alarm went off the screen got black and unresponsive. I believe the phone is still working at this point because I can hear vibrations when I try to turn it off or boot into fastboot mode, but the screen is totally dead.
Anyone experiencing anything similar? Any ideas or suggestion on this one?
I experienced the same thing last week. Happened two days in a row and in addition to what you stated it seemed that my default home launcher had been unset in default apps, My phone seemed to bounce between launchers while navigating.
I'm running lineage and at 1st I thought maybe it was something in the update, but I don't think that was actually anything to do with it. If you're not running lineage then it for sure wasn't. Maybe a rogue app update, google services? I don't know.
I also don't know what cleared the problem up. Like I said the only thing I noticed was my default home launcher had become unset, and I set it back in default apps. Maybe something relating to that caused the phone to act seemingly dead?
Either way, if you just hold your power button for 15 sec or so it'll reset, and check your default home app. I don't really know the cause or solution, but it seems to have cleared up since then and everything is back to normal.
Hi,
I am experiencing the same thing with my pixel 3xl. I plugged it in before going to bed and in the morning it was unresponsive and black screen. I tried changing chargers and plug but nothing changed. When i plug it in a PC it shows QUSB_BULK_CID and then the serial number but nothing else. I have found many people in the google support forums that have the same issue (https://support.google.com/pixelpho...-pixel-3xl-black-screen?hl=en&msgid=121361292) but no one has replied with a fix or even an update.
Have you resolved your issue?
This is an annoying problem that I've been suffering from my pixel 3a xl for a long time. This would sometimes happen to me when just using my phone regularly but happened a lot more often when charging my phone overnight. When it first started happening to me, I noticed that I could resolve the problem by not having any magisk modules enabled.
However, this didn't seem to be a permanent solution. Nowadays my phone occasionally locks up in the way you describe, but if I leave it alone it usually comes back to a working state in about 4-8 minutes. It's very annoying and motivating me to get a new phone.
It might be worth taking a look at this issue thread on the magisk GitHub that describes the same error: https://github.com/topjohnwu/Magisk/issues/3171
My phone did this yesterday. I woke up and it was unresponsive, seemed dead. I just held the power button, restarted, and back to normal. I know had a bunch of google apps update the day before and even that morning. If I remember right, I had google apps update the last time it happened. I think there something there that's causing the problem, and once the phone is restarted it's good.
I can't say that's it for sure, but it's something I noticed. It is kind of odd that when it happen to one person here, there's usually another in about the same time frame.
Yeah mines still dead and unresponsive. I lost hope like two days ago. There was nothing out of the ordinary when it happened and no weird updates. Just plugged it in like every night and then it bricked during the night.
vagelisot said:
Hi,
I am experiencing the same thing with my pixel 3xl. I plugged it in before going to bed and in the morning it was unresponsive and black screen. I tried changing chargers and plug but nothing changed. When i plug it in a PC it shows QUSB_BULK_CID and then the serial number but nothing else. I have found many people in the google support forums that have the same issue (https://support.google.com/pixelpho...-pixel-3xl-black-screen?hl=en&msgid=121361292) but no one has replied with a fix or even an update.
Have you resolved your issue?
Click to expand...
Click to collapse
Hi!
It turned out that there was an issue with the screen (I completely don't understand why). I had it replaced and everything is back to normal.
Hope you will have your issue resolved!