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.
Related
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.
Hello everyone, I just recently got a G3 and it was working fine for the 1st 2 days, no issues. I was sending a text to a friend earlier today and after it sent, it completely froze. After doing a soft reset it took forever to boot up. Once it booted up, it seemed to be fine. about an hour of operation, the screen looked as if it was freezing because it wasn't recognizing any of my touches. i decide to flip the phone sideways to see if it was actually frozen but it changed to landscape just fine. Sometimes it comes back to life then goes off again shortly after, and other times, i have to soft reset. I've tried the following to no avail.
Took the phone apart and cleaned both connectors.
Re-flashing the rom.
Trying 4 other roms.
Returned to lollipop stock.
I can't figure this out for the life to me and worked my ass of to be able to buy this phone. Any help would be appreciated as I can't afford to spend any more money on it!
I also have this issue, it's been ongoing for a few weeks. There will be short periods where it can work just fine, then it just freezes up and does not register any inputs. The content on the screen continues to run as if nothing happened (videos and games keep playing). Turning the screen off, waiting a couple minutes, then turning it on can sometimes give me another minute of use until it freezes up again. Also of note, when the screen is unresponsive and I press the power, it will dim to very low levels for a few seconds before going fully black. When the screen is being responsive and I press the power, it goes straight to black, as is normal and expected. From my testing, I've concluded:
1. This issue is not app dependent. It can occur at any time, and is not caused by alarms or overlays, such as blue light filters.
2. The issue is not from the specific battery I use. I've switched out between multiple batteries and used different chargers, none seem to affect the frequency of freezes.
3. Temperature may have something to do with this. When waking the phone after it's been sitting out in the cold, there seems to be a higher likelihood that it will be unresponsive. This is not always the case, which makes concluding that the issue is hardware related difficult, but some correlation seems to exist.
4. This issue started occurring shortly before I began having the popular "SIM Card Removed" issue, which I've yet to resolve (though can sometimes get the SIM card to work)
I am running stock 6.0 D85030p AT&T. I will post here again if I figure something out, but I have been trying for weeks without much success.
Hi all,
Bit of an odd problem my S9+ seems to have developed. Since I got the September update a few days a go, my Exynos S9+ on Three (but unlocked/unbranded) in the UK keeps on turning the Always on Display on.
I have it turned off by default, but on occasion when I plug it in it'll reactivate it. It doesn't happen all the time, only occasionally, but it does happen often enough for it to be annoying. I had a to add the AOD short cut to the pull down menu to be able to quickly turn it off, so it definitely wasn't something I was accidentally pressing (at least not until I added that button, but it is on the second page of shortcuts).
Anyone else having this problem since the update? Or have I just got a weird phone with a mind of its own?!
Thanks
Always on Display
Hi, I got my Samsung Galaxy S9 2 days ago and it is sort if driving me nuts!
The minute I get a mail or notification from the many groups I'm in- the screen flashes- I guess it's the lock-screen.
I turned off the "Always On Display" but it still flashes...
Is there any way to stop this... I'm a little ADD and it's really annoying.
At he moment I'm just turning it upside down so as not to see it!
Thanks in advance- Robin
kingdave82 said:
Hi all,
Bit of an odd problem my S9+ seems to have developed. Since I got the September update a few days a go, my Exynos S9+ on Three (but unlocked/unbranded) in the UK keeps on turning the Always on Display on.
I have it turned off by default, but on occasion when I plug it in it'll reactivate it. It doesn't happen all the time, only occasionally, but it does happen often enough for it to be annoying. I had a to add the AOD short cut to the pull down menu to be able to quickly turn it off, so it definitely wasn't something I was accidentally pressing (at least not until I added that button, but it is on the second page of shortcuts).
Anyone else having this problem since the update? Or have I just got a weird phone with a mind of its own?!
Thanks
Click to expand...
Click to collapse
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!