Develop Bugs

Mango users, watch out for unresponsive touchscreen

Title says all. I was just chillin' listening to some music (Let's Get It to be exact) and when I pressed my power button to check and see how fast the WiFi reconnects, I swiped up and nothing happened. It was like that for about a minute or two, the volume rocker worked and I could hold down the camera button and go to the camera, but the touch screen just wouldn't work. I popped off the back and was about to remove the battery and thats when everything went back to normal...pretty odd...just a heads up.
Wifi now reconnects instantly. I am pleased

strange... not had any problems like this at all on mine yet...
Seems VERY responsive, been using it all lastnight over and over and this morning.
what phone you have? im using the mozart

Keefo said:
strange... not had any problems like this at all on mine yet...
Seems VERY responsive, been using it all lastnight over and over and this morning.
what phone you have? im using the mozart
Click to expand...
Click to collapse
Dammit, I thought I said what phone I was using...I'm on the HTC Arrive. It hasn't done it since I've posted..I highly doubt it'll happen all the time (probably won't ever happen again)..just wanted to mention it.

This happened to my arrive right as it was done updating on the screen that says the update is done...the close button wouldn't work, but I remember reading this thread so I waited it out and it started to work after like 2 min

I am having the exact problem on my HD7, only seems to occur if I am listening to music. The lock screen appears, but I cannot swipe.
Mine doesn't always come back and I have to remove the battery.

I have the same issue every once in a while. I'm not on Mango though, I'm running NoDo on a HTC Surround.
It's happened about 5 times in the last six months.

I've had the same issue since before NoDo. The quickest fix is to try turning the screen off and then on again, sometimes it takes a few attempts but it normally works.

haven't noticed on dvp or anything I wonder if its a htc thing...

I haven't noticed it, though I did get the red screen associated with changing the reg entries to get 32 bit color one.
Interesting side not, when I was updating to Mango, on one of the reboots I got the red screen and thought I was screwed, but the update process continued and on the next reboot it was normal again...

ms79723 said:
Title says all. I was just chillin' listening to some music (Let's Get It to be exact) and when I pressed my power button to check and see how fast the WiFi reconnects, I swiped up and nothing happened. It was like that for about a minute or two, the volume rocker worked and I could hold down the camera button and go to the camera, but the touch screen just wouldn't work. I popped off the back and was about to remove the battery and thats when everything went back to normal...pretty odd...just a heads up.
Wifi now reconnects instantly. I am pleased
Click to expand...
Click to collapse
nope havnt come across this yet on my Samsung Focus. The only issue seems to be the increased boot up time(phone stays on d Samsung logo screenfor a long time) but I am quite sure its due to Samsungs crappy bootloader and besides I hardly have to reboot WP7 ever anyway

Hey, has anyone else noticed that weird icon where your signal and data icon should be?
Idk if its the new icon for no signal or what...but when I unlocked my phone, I saw an icon that looked like the copy and paste icon where my signal and data icon should be.

I must say I'm noticing this on third party apps a lot, I don't know whether it's because they are downloading data from the Internet or what but it's happening quite a bit at the moment. LG Optimus 7 btw.

[Q] Sometimes my touchscreen stops working

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.

HTC M8 screen randomly turning off

Dear Friends,
After updating my htc one m8 to Android 5.0.2 and resetting the phone as needed, i am facing the problem of switching off the screen randomly while i am using it. can anyone help me.
appreciate the support.
thnx

hogrsq said:
Dear Friends,
After updating my htc one m8 to Android 5.0.2 and resetting the phone as needed, i am facing the problem of switching off the screen randomly while i am using it. can anyone help me.
appreciate the support.
thnx
Click to expand...
Click to collapse
Have you checked the screen timeout settings in settings/display & gestures? That's the most likely possibility.

It's not a timeout problem for me.
My timeout settings are at one minute or more and the screen will blank on me in the middle of active use. If I tap the power button repeatedly (the number of times required varies, but it takes fewer if the taps are spaced by a second or so), the screen will come back on, but more often than not, the screen will black again immediately (i.e. in the middle of the unlock process). The screen blacks, but remains responsive to touch. If I tap where a button was before pressing the power button, when I can see again, the app (or launcher screen) has changed accordingly. The problem has gotten more frequent, to the point that my phone is almost unusable as of yesterday afternoon.
I have tried a factory reset as of this morning, which didn't remove the problem. My battery seems to be OK. I'm still getting roughly the same battery life I've always had. I'm stuck, and I'm not finding abundant references to it anywhere, so any help would be appreciated.
A brief history of my interaction with this problem: I bought the phone used about 3 months ago. about 3 weeks in, the blanking problem started to appear, but only in landscape mode apps (games). This was not frequent until about a month ago, when it started becoming more frequent and affecting everyday activity, not just games. About 3 weeks ago, I started having problems with image persistence (which may not be relevant, but I'm not sure either way). Yesterday afternoon it started blanking repeatedly. Restarting the phone had helped in the past, but not this time. Leaving the phone shut down for 2-3 hours also failed.
I am getting very frustrated, and I really like this phone.
Please help, if anyone can.
Thanks very much.

Pixel not waking up from sleep

Anyone else having issues with the Pixel not waking up from sleep. This happens to me seemingly randomly, at least I have not been able to pinpoint what is causing it. I have to use the power button and volume rocker to hard reboot it. This is my second unit that has done this, and Google just wants to replace it again.
I made a quick video of it:
https://www.youtube.com/watch?v=97iho4sHAlc

I have exactly the same problem ...
to boot, I press 10 seconds repeatedly on the power button.
I already had the problem of keyboard update ...

I thought this was solved but sadly it's still around. Suffered from it a few days ago after doing a factory reset about a week ago.

Ves said:
I thought this was solved but sadly it's still around. Suffered from it a few days ago after doing a factory reset about a week ago.
Click to expand...
Click to collapse
Same here, I finally received the Feb update on my replacement Pixel and thought it was solved... nope.
I bought the Pixel for quick work trips so I did not have to bring my laptop. I take allot of flights in the morning and return that afternoon/evening. The Pixel was going to be used for Presentations, and notes. It is super frustrating when I have the tablet all setup to present and I have to mess with it to get it to turn back on. This thing has way to many problems for a premium tab, and seems like Google has not dedicated the appropriate resources to supporting it (support/dev).

Ah the old "Sleep of Death" it seems to have plagued (mostly) tablets for years. I've had it happen on my Asus Transformer T101 years ago and it also happened on my Samsung Galaxy Tab S 10.5". I haven't had it happen yet in the months I've owned the Pixel, but I have had some odd issues where I press the power button to turn it on and it shows the unlocked boot warning for literally a second and then turns off/reboots, when it does that I have to hold the power button for like 10 seconds to force a reboot and then it boots up fine.
Sent from my Pixel C using Tapatalk

I use the pattern to unlock my device. For years on my Asus TF201 (which had occasional severe performance problems), I would occasionally turn it on, get nothing for several seconds, and then get the pattern unlock screen for a fraction of a second, and then it would sleep. Sometimes if I drew the pattern really fast it would unlock it. Othertimes, I think I just rebooted it.
With the Google Pixel C, I (perhaps foolishly) continued the pattern unlock approach. It usually works fine. But occasionally, I will get the pattern unlock screen soon enough, enter the pattern, and it will do nothing for several seconds (just frozen on the pattern screen with my drawn pattern) and then go to sleep. If I try this repeatedly, sometimes once it will actually let me in. Otherwise I reboot and try again.

buurmas said:
I use the pattern to unlock my device. For years on my Asus TF201 (which had occasional severe performance problems), I would occasionally turn it on, get nothing for several seconds, and then get the pattern unlock screen for a fraction of a second, and then it would sleep. Sometimes if I drew the pattern really fast it would unlock it. Othertimes, I think I just rebooted it.
With the Google Pixel C, I (perhaps foolishly) continued the pattern unlock approach. It usually works fine. But occasionally, I will get the pattern unlock screen soon enough, enter the pattern, and it will do nothing for several seconds (just frozen on the pattern screen with my drawn pattern) and then go to sleep. If I try this repeatedly, sometimes once it will actually let me in. Otherwise I reboot and try again.
Click to expand...
Click to collapse
I do not use the pattern lock, I do secure it with a passcode though. My issue does not seem to be related to the security though as it does it at random times and never display the login prompt.

still having both random reboots and screen blackouts. This is a shame google will not acknowledge the problem and say they're fixing it. It only makes me believe that they know about it yet CANT fix it. Like its a hardware issue more than a software one. At least if they would say "we are aware of the issue and working on a fix" or "we were working on a fix but now working just a big OS update instead" Id feel like I wasnt ripped off by them. I mean I have EVERY nexus device box still displayed in my hobby room at my house. Im a huge fan but this is really bad.

Joined beta N program, hopefully this issue is resolved on the Pixel C.

Screen flicker when manually locking screen

I sideloaded the July patch 2 days ago and now out of the blue, my screen has decided to start flickering if I manually press the power button to lock the phone. I turned on AOD when the June patch came out because of the horrible lag that was introduced but now I've gotten used to the AOD and don't really want to turn it off now. When I tested it by turning off the AOD, the flicker doesn't occur. Did Google just revert back to pre-June patch with that setting? I thought they said they found a solution that both takes care of the lag and the flicker? Furthermore, why was it working fine for 2 days and now just randomly decided to start flickering?? I have also noticed that I am getting a little higher battery drain. It may be time for a wipe to see if that clears these items up but other feedback and experiences are appreciated to determine if I'm the only one or if it's wide spread.

Side note: I turned off AOD and then forced a restart by holding the power button for 10-12 seconds. Once the phone came back on, I turned AOD back on and it hasn't had the issue but for how long will this last, I don't know.

Well that lasted about 30 minutes and the flicker came back. I may try a wipe soon to see what happens but I'd hate to do it for nothing.

I've experienced this multiple times, doesn't matter what update I was on, but it went away after some time. Haven't experienced it in some time.
Never knew what the cause was or what the fix was either. p:

This used to be a major issue and it disappeared for most with the first beta. Weird that you're suddenly experiencing it. Google were/are aware.

It seems to be coming and going with AOD on. I haven't done a wipe yet but if it keeps coming back over the next day or 2, I will.