Hi all, I started using my Pixel 2 XL yesterday and I got the first issue!
I set every settings into ambient display to off, anyway my pixel 2 xl yesterday decided to turns on the screen itself randomly for 4 times. Every time the screen turned on itself I could see the numeric pad of the lockscreen, the same use case you get when you have the fp scanner set and you just try to unlock the phone just swiping up on the lockscreen. The second and the third times were almost consecutive, while the first and the fourth times were quite far from the others.
As I wrote....I set the ambient display to off when I set up the phone the first time. I don't have any particular app installed dealing with screen nor battery management.
Today (second day of usage) I haven't got any spontaneous screen turned on yet...
Anyone else had a similar issue?
Thanks in advance
Aratheba said:
Hi all, I started using my Pixel 2 XL yesterday and I got the first issue!
I set every settings into ambient display to off, anyway my pixel 2 xl yesterday decided to turns on the screen itself randomly for 4 times. Every time the screen turned on itself I could see the numeric pad of the lockscreen, the same use case you get when you have the fp scanner set and you just try to unlock the phone just swiping up on the lockscreen. The second and the third times were almost consecutive, while the first and the fourth times were quite far from the others.
As I wrote....I set the ambient display to off when I set up the phone the first time. I don't have any particular app installed dealing with screen nor battery management.
Today (second day of usage) I haven't got any spontaneous screen turned on yet...
Anyone else had a similar issue?
Thanks in advance
Click to expand...
Click to collapse
Nope....it's just done it again!
The screen has just turned on itself few seconds ago...I had a Netatmo notification in the notification bar....but checking it I saw it was 6 minutes old....then I think it's not the cause of this issue! :/
Related
first i thought it was launcher pro's fault, but after changing launcher and rom release i'm pretty sure it's something else i haven't tracked down yet.
just after a reboot phone works as usual: screen lock runs after 30 seconds or by clicking the power button
after a while (days or even hours sometimes), the screen lock does not kick-in anymore: the screen just turns off and when you press the power button the phone is already unlocked.
i noticed that when the phone is in this "lock-bug" mode the notification led constantly shows a faint red light (you can barely notice it in the dark because it's really faint).
tested with:
launcher pro
go launcher
factory rom 2.21
blurless 2.34
I used to have the faint red light on after flashing a new rom.
It disapeared after I changed display setting to not automatic brightness.
It seems that the faint red light is the light sensor.
But I know nothing about your screen lock problem.
I have run into the same thing. I have not yet noticed the light, but I've had the screen lock stop working on my phone twice (I bought 3 phones 5 days ago for work). Like you, a simple reboot fixed the problem. I also tried toggling screen lock in the settings, and setting up a lock code, to see if the screen lock would start up. Both of my times, the first I noticed the issue was when I received a phone call and didn't have to swipe to answer, but that could have just been coincidence.
It isn't really a big deal for me or the employees, but it is a nuisance.
Happened to me as well, twice. First time it was just annoying that I had to reboot, second time it drained the s**t out of my battery in three hours.
So it's a bug allright.
Sent from my MB525 using Tapatalk
same here.. it just stops working.. any fixes yet?
Hello,
Yesterday when I was done working and got my phone from my locker, I opened an app and immediately
the screen went black and appearantly the phone had switched itself off. I turned it back on wondering why
it did this, but as soon as it had started up and the home screen appeared, it turned itself right back off.
I tried turning it back on about 7 or 8 times until the battery ran out and I could not try anymore.
When I got home I put it on the charger and fortunately the phone stayed on, however the top of the screen
seemed to be 'trembling' a bit and some pixels were changing from light red to dark red to light red etc. (my home screen is red)
I decided to leave it charging overnight and when I woke up, the trembling had disappeared. I took it off the
charger and after scrolling through my Facebook news feed, found that battery percentage was decreasing quite
quickly considering it's on power saver mode. I thought it might be that the screen brightness is too high, so I went
to settings and tried to adjust the screen brightness, however it is not responding? My screen brightness stays
exactly the same no matter whether I increase or decrease it, and when I was doing that the phone switched itself
off again. I put it back on charge now and turned it back on, but I am quite annoyed about this issue because I
do not know what it is and my phone is only 5 months old. I hope any of you can shed some light on the situation.
Summary of the issues:
- Phone switching itself off
- Screen trembled yesterday
- Battery decreasing quickly
- Brightness setting not working
Info about the phone:
- HTC One X 5 months old
- Android 4.2.2
- No adjustments made to the phone with rooting or any of that
Thanks!
Must be a hardware failure if you havent changed anything software-wise
Is it overheating?
Is it under warranty?
And other sensors are working? But like TTG TriCkSh0tZz said , use your warranty if you can.
Sent from my HTC One X using XDA Premium 4 mobile app
I seem to be having an issue with the screen turning on at random. I have Always-on screen set to ON and tilt-to-wake set to OFF, but the screen will turn on sometimes seemingly at random and multiple times in a row. I have done Factory Reset a couple of times and it does not help.
Is there anyone else with this occurance and is there a fix for it?
Sent from my VS980 4G using Tapatalk
I have this issue too. I've tried several configurations and it keeps doing it.
Sent from my SM-N910V using Tapatalk
Any apps that send a lot of notifications or any notifications that are automatically dismissed/very briefly show up? Can't think of anything else that would wake your watch.
No, not on mine.
Sent from my SM-N910V using Tapatalk
I have the exact same issue. At first I thought it was tilt-to-wake having poor gesture recognition so I turned it off. However I noticed without touching the screen it would turn on and then turn off after the stand-by time. To verify that was the case I left it sitting on my desk all day and observed that it would in fact randomly turn on and off. I also noticed that when the issue occurs the battery life decreases rapidly.
Also this issue will continue to occur even in theater mode.
Have you find a solution yet? My smartwatch 3 does the screen turn on randomly and then also touch screen issue occurs, and it makes random touches, swipes going into settings and so on, without touching the screen. I'am on the latest wear version mwd49b.
For more info search on youtube for my video about this problem: Sony SmartWatch 3 screen problem.
I recently began having the same problem. The screen does not turn off after it randomly turns on - I have to manually press the button to turn it off. Needless to say, this tend to run down the battery. I did a factory reset this morning, but the problem persists.
EDITING POST JULY 20:
After factory reset, I actually had the watch doubly connected to the phone, so I have corrected that now. However the problem with the random turn-ons began occurring well before the factory reset. I'm not sure what triggers it, or what stops it, but when it begins to happen, it drains the battery very quickly. The problem only began recently (within the past few weeks), so I'm not sure what changed to bring this on.
A bug in Android Alarm Clock keep the watch active after alarm ring. Just corrected yesterday by an update on Google Alarm/Clock app.
On the phone > android wear app > settings icon on top right > device settings (smartwatch 3) >tilt to wake set to off
Hey everyone!
As the title say i'm facing a issue with my always on display.
I'll try to make it as simple as possible:
When I set the always on display to be always active it works flawlessly.
When I set the always on display to activate on tap (and last for 10 seconds according to the settings) it appears for roughly 3 seconds and then disappears for 3-4 and reappears flickering for 2-3 times sometimes showing the desktop wallpaper between each flicker.
Did anyone experience the same issue?
What I did to try and fix it was:
- tested both on battery and while charging
- factory reseted and then restored backup (which was stupid, that lead me to the second point)
- start in safe mode (to check whether it was an app causing troubles) but no such luck, problem still occurs.
- uninstalled "nice lock" apps
- changed some settings under the always on display tab
- cleared cache of the always on app
What you should know:
- I'm running android 9, not rooted and have nova launcher as default home
- After I factory reseted the phone I wanted to stop always on display from updating to test whether it was a new version issue but I forgot and didn't make it in time so I'm currently running the latest version
Does anyone have any idea as of why it's behaving like this?
edit: just wanna be a little more clear, flickering is not meant like a lightbulb it's more something like it turns off and back on after a delay (I'm sorry english is not my native language I can't really explain it any better)
Frans1897 said:
Hey everyone!
As the title say i'm facing a issue with my always on display.
I'll try to make it as simple as possible:
When I set the always on display to be always active it works flawlessly.
When I set the always on display to activate on tap (and last for 10 seconds according to the settings) it appears for roughly 3 seconds and then disappears for 3-4 and reappears flickering for 2-3 times sometimes showing the desktop wallpaper between each flicker.
Did anyone experience the same issue?
What I did to try and fix it was:
- tested both on battery and while charging
- factory reseted and then restored backup (which was stupid, that lead me to the second point)
- start in safe mode (to check whether it was an app causing troubles) but no such luck, problem still occurs.
- uninstalled "nice lock" apps
- changed some settings under the always on display tab
- cleared cache of the always on app
What you should know:
- I'm running android 9, not rooted and have nova launcher as default home
- After I factory reseted the phone I wanted to stop always on display from updating to test whether it was a new version issue but I forgot and didn't make it in time so I'm currently running the latest version
Does anyone have any idea as of why it's behaving like this?
edit: just wanna be a little more clear, flickering is not meant like a lightbulb it's more something like it turns off and back on after a delay (I'm sorry english is not my native language I can't really explain it any better)
Click to expand...
Click to collapse
i also experience the same.
this phone has many strange bugs.
when i restart my A70, tap to show always on display works for me for 2-3 times.
after 2-3 times working correctly, the bug starts.
after i tap the screen, it shows AOD for 2 seconds. then turns the screen off and then at the end of the 10th second, screen just flashes itself for the last time and turns off completely.
i think it is related to the fingerprint scanner.
because after i registered my fingerprints and turned on unlocking the screen by the FP reader, this bug ends.
after i tap the screen it shows both the clock and fingerprint icon at the bottom of the screen.
after 2 seconds fingerprint icon disappears. and the clock is continued to be shown until the end of 10th second.
but there is a minor issue, when the fingerprint icon disappears, the AOD screen brightness changes. dims or brighter slightly.
can you please try tap to show AOD, by enabling the fingerprint unlocking?
samsung ?
xprzs said:
i also experience the same.
this phone has many strange bugs.
when i restart my A70, tap to show always on display works for me for 2-3 times.
after 2-3 times working correctly, the bug starts.
after i tap the screen, it shows AOD for 2 seconds. then turns the screen off and then at the end of the 10th second, screen just flashes itself for the last time and turns off completely.
i think it is related to the fingerprint scanner.
because after i registered my fingerprints and turned on unlocking the screen by the FP reader, this bug ends.
after i tap the screen it shows both the clock and fingerprint icon at the bottom of the screen.
after 2 seconds fingerprint icon disappears. and the clock is continued to be shown until the end of 10th second.
but there is a minor issue, when the fingerprint icon disappears, the AOD screen brightness changes. dims or brighter slightly.
can you please try tap to show AOD, by enabling the fingerprint unlocking?
samsung ?
Click to expand...
Click to collapse
Hey! Thanks for the answer, I can confirm we have the exact same issue. I also have the same brightness issue you described
Anyway, I have always used fingerprint unlock though so I don't know what to answer you.. I only recently noticed the weird behavior. I did a couple things to test and I found out that enabling the "fingerprint" icon showing in the always on display seems to "fix" the issue of the flicker but not the one of the brightness change (after enabling it i've yet to see the problem occur), you should try it and let me know if you see any improvement. It's probably on samsung's end though and hopefully we get it fixed with android 10 or earlier
I'll take this chance to ask you another question; two weeks ago I received a software update and ever since that day I noticed my battery to be lasting waaaay less than it used to, did you update your phone as well? Did you notice a battery drain?
I have the issue both of you talking about.
hello, I had this same issue and what I did was turn the phone off, and booting it up while pressing "Volume Up", after entering a black screen with many options, I selected wipe cache. It has worked without a flaw since then. There's lots of bugs with this phone. I recently had a problem where the USB port will detect a device and "plugged and unplugged" it, making my phone unable to dim. Thankfully I was helpful.
Why does my Android 10 Galaxy S9 keep going to lock screen randomly, even while I'm actively using it, like when I'm typing in a any like this? In the Settings I've got the Display time out set to 10 min and Lock Automatically is set for 30 min except when Smart Lock (No Body, Trusted Places) keeps it open.
kwhopson said:
Why does my Android 10 Galaxy S9 keep going to lock screen randomly, even while I'm actively using it, like when I'm typing in a any like this? In the Settings I've got the Display time out set to 10 min and Lock Automatically is set for 30 min except when Smart Lock (No Body, Trusted Places) keeps it open.
Click to expand...
Click to collapse
To further clarify,
I'm using the same Otterbox cover that I've been using for over a year, it does not cover the proximity sensor.
This only began a week ago. It happens completely randomly, a few times an hour at least. It has happened while actively pressing app controls, or reading, or just ended a call.
Found the answer on a Reddit post. Settings | Developers Options | Lock screen when trust is lost. < Disabling seems to have fixed the glitch