I'm using my dad's Note 10.1 (2014) and I've been experiencing some problems. The screen would randomly just turn off (but it doesn't shut down) when I looked away. I thought it was the smart eye detection feature thingy but when I checked, it was already turned off. Another problem is that the home button and/or the capacitive just randomly stops working. Had to reboot the device in order to get it working again. At first I thought it was some hardware problem but I'm pretty sure it isn't. So yeah. Does anyone face the same problems? I've heard this device have some software issues that causes this but after some searching I got no answers.
Hi
I have your problem too. i have thiss issue on Stock rom. i use for one day Resurrection Remix ROM. i havn't see this issue.
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.
I am wondering if anyone ever encountered these kind of problems,
First of all i've been running cm10.2rc for the past month or so and was having no problem whatsoever. Then out of the blue last night, my screen started flicking on and off, then it'd reboot off for no reason. It goes into apps of widget for no apparent reason either. Even in recovery mode (recovery touch) it clicks options without me touching anything.
I've flashed a dirty/clean, Cm11 (don't like it came back to cm10).
It's as if my power button gets stuck.
I'm wondering if this is a common hardware issue that i could solve by changing a part myself off ebay or any kind of solution for this insane phone?
Thanks
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.
I have had my Moto 360 for just over a week. For the second time the touchscreen stopped functioning. First time I resolved by turning it off (very long press hardware button) then left overnight and it was fine in the morning. Turning it off and back on again didn't help. Couldn't factory reset because no touchscreen.
Second time is now.
Does anyone else have this problem? Any clues how to resolve?
Thanks.
Edit: After left off for a while (instant off and on doesn't work) it is fine now. Anyone have any clues or better suggestions how to fix?
spanielhead said:
I have had my Moto 360 for just over a week. For the second time the touchscreen stopped functioning. First time I resolved by turning it off (very long press hardware button) then left overnight and it was fine in the morning. Turning it off and back on again didn't help. Couldn't factory reset because no touchscreen.
Second time is now.
Does anyone else have this problem? Any clues how to resolve?
Thanks.
Edit: After left off for a while (instant off and on doesn't work) it is fine now. Anyone have any clues or better suggestions how to fix?
Click to expand...
Click to collapse
Yes mine has done it two or three times since the last OTA update, nothing I did to the screen had an effect, had to reboot the watch to recover.
teslabe said:
Yes mine has done it two or three times since the last OTA update, nothing I did to the screen had an effect, had to reboot the watch to recover.
Click to expand...
Click to collapse
Mine doesn't recover immediately on a reboot but it is nice to know I'm not alone in the problem. It's better to know that you've only had this problem since the OTA. That means it can be fixed in software. Thanks.
Same here
Lost "touch" today on mine. Had the 360 for about 4 weeks and not seen the problem until now. Wasn't even sure how to turn it off until I saw "very long press" - thanks!
Turning mine back on straight away was fine so it was just a turn it off and back on thing. Frustrating, but I'm glad it's a software bug rather a touch screen fault, that would be a real pain. Hopefully, if it's a bug it will be fixed.
i think.....
I think this happens when the moto 360 is not set on your wrist
Ddoes anyone solve this issue ? My new moto 360 touch screen doesnt work at all. So i can choose any language in initial setup
This problem Occurs when no static energy is given to the case of the moto360. As soo'n as You touch The Iron ring The touch Will work. Release it and it Will stop working. Ik think The touch screen works rather like a conductive layer between the back of the watch and the screen it self in which the skin gives the energy needed to control the screen. When the back of the watch isn't connected to skin the touchscreen completely stops working.
In video you see what happens
https://youtu.be/KpQ-dqWYO6s
Mine did this too, however I broke my screen ordered a replacement and haven't had the issue since. When mine quite working if I triple pressed the power button it lock the screen then pressing the power button it would turn on and work though. Sometimes it wouldn't come right back on like it froze or something.
Sent from my Nexus 6 using Tapatalk
I've been having this problem too, it's more like my weekend watch but last week i noticed that it wasn't responding and i thought it could be a RAM issue. I've done multiple reboots and it doesn't work.
There was only an occasion where i left it overnight till it almost drained completely and it worked again, and then it started freezing again.
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.