I had a day or two where I was unable to get my phone to change orientation from portrait to landscape. Mainly for watching netflix or Youtube. I found a work around for youtube, I had to flip the orientation of the device and press the full screen button. But then my phone was locked in landscape and wouldn't go back to portrait unless I shut the screen off and unlocked the phone again.
I dealt with this for two days, I checked settings to make sure that "auto rotate" was enabled, I disabled it and re-enabeld it just to be certain.
I'm not sure what really fixed it, I started tapping it lightly against the table while the phone was in landscape mode. After about 3 light taps the phone started responding to the changes in orientation again.
Now my question is... What happened, and Why?
I assume that the accelerometer got stuck, but has any one else experienced any issues like this?
So far this is the first issue that I have had out of the device and it has been an awesome 3 weeks
I have an Otterbox Commuter installed on the phone, in case that helps.
Happened here too.
Sent from my LG-H815 using Tapatalk
Mine is currently stuck as well. My girlfriend turned rotation off and since turning it back on it won't work. Turning the phone off didn't help.
I've seen multiple users here and on Reddit have fixed the stuck accelerometer by lightly banging against a table.. I find it quite amusing
They get stuck sometimes, especially if the phone has had an impact from dropping. It's a small miracle that they work at all.
If yours gets stuck all the time it could be a bad chip. I'd replace the phone while it's under warranty.
Same problem
After accidentally turning off auto rotate several months ago it stopped working. A light smack on the back of phone fixed it and haven't had a problem since.
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 just recently got a T217S from Sprint, had it about 2 weeks, running all stock, 4.42 Android. Ran fine the first week, then I noticed that the screen would start to flicker. Doesn't change colors, just flickers. Playing with the brightness can sometimes cause it to stop temporarily, but it starts again almost immediately. The level of brightness doesn't make a difference, neither does any applications I'm running. I've rebooted it into safe mode and without even touching it, it started flickering less than 30 seconds after booting. I've google the heck out of this and it doesn't seem to be a hardware issue, but an Android problem. I would like to avoid a factor reset if I can, especially until I get solid proof that it would FIX the problem. So far, no one can even tell me WHY it's doing it.
HELP???
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.
So it seems theres something wrong with my sensor.. trying to tap the screen to wake the device doesnt always work and when the screen is on, gesturing through cards the screen will just shut off. I suspected it might have to do with the sensor so i just tested by keeping ambient mode turned on and now everything works fine.. But as soon as ambient mode is turned off it starts acting buggy.
It happened to me a few weeks back and i thought a reboot solved it but yesterday the problem returned and even after a factory reset the problem persists. Not sure if its related to the last update.. could the Android Wear app cause issues?
At this point im not sure what to do except for keeping it in ambient mode..which i really dont want to have to do. Im hoping its software related.. the watch itself is in great shape..never been dropped or anything..the only other thing i can think of is it started happening again last night after i finished running and the watch back and band was pretty sweaty. This watch should be able to withstand some sweat though no? ..it is water resistant after all.
Hi all,
I've recently got this tablet from Google store (and out of stock now).
After installed all things needed, a serious problem has appeared during in use. Its screen unexpectly trembles, pops notification out, runs and closes apps randomly then unable touchscreen at all. These make me crazy even in screen saver, and power button doesn't work sometimes to stop those happenings.
The device hasn't rooted and staying as 'pure' with only afew apps, so I've done erasing system cache partition on recovery mode and factory reset twice to solve this problem.
Nothing happened so far since reset the device but is still unsettling.. and now I just supposed touching screen badly (with sweaty fingers for example) or the screen protect film I affixed since unboxing might cause the problem.
Does anyone faces a problem like this?
Regards,
Allen
If it was greasy fingers my tablet would be completely unusable. Luckily a quick clean sorts any issues that causes.
My first suspicion would be the screen protector, as mine has done similar when there was something touching the screen. Maybe try taking it off and seeing how it goes? You can also turn on show taps in the Developer Options to be able to see what touches the tablet is detecting when it goes mad.
Better than before
The Real Dannilion said:
If it was greasy fingers my tablet would be completely unusable. Luckily a quick clean sorts any issues that causes.
My first suspicion would be the screen protector, as mine has done similar when there was something touching the screen. Maybe try taking it off and seeing how it goes? You can also turn on show taps in the Developer Options to be able to see what touches the tablet is detecting when it goes mad.
Click to expand...
Click to collapse
Thanks for your reply. Now I've used a BT mouse to match with mine and less touch on the screen apparently. Nothing happened so far.
It's not a problem of hardware I supposed and pretty sure that the screen protector interferes a certain touch as you commented. Still my eyes are keeping on what caused the problem.