Hello,
When the phone locks after the timeout, Always on Display is not working, it appears for 5 seconds and then it fades.
When I manually lock the phone it does works ok.
RMX2202_11_A.13.
I didn't receive update for A.16.
Thanks
Personalizations -> AOD -> Display options -> All Day
I already did that. The problem is with "all day" selected.
I have the same problem, it worked good since few days ago, now it does the same!
Related
Hello,
After the last update (touch screen related bugfixing), my tablet do a strange thing,
With normal usage the screen suddenly started to turn to black, many random pixel turned to black, and in about 5 second the screen is turned completly black (like in some old screen saver)..
I switch off the display, then switch it on and the tablet display is still black, I have to hold power botton for 10 second and reboot the tablet and then it worked perfectly.
A second time the same problem, then i switch off the display, then switch it on and the tablet working perfectly.
I hope it's not hardware related issue (maybe video card related), anyone else have the same issue?
Maybe the option Force GPU Rendering in Developer Option is the cause, I try to disable it (with the previous firmware version no problem with this option enabled in 3 months)..
PS: the upper half of the back of the tablet where the Qualcomm 810 is located isn't hot when the problem showed itself..
PS2: in Developer option I have enabled
- Debug usb
- verify usb app
- Force GPU Rendering
- Use Nuplayer
Did you find out anything more about this?
Have you continued to experience this problem?
I have a problem which is not exactly the same, but since your thread didn't get any answers I thought I would share my problem here in case it may be relevant to yours...
My Z4 (LTE) suddenly doesn't respond to finger inputs on the screen. It has happened three times over the last 5 days.
I did buy a sleeve from aliexpress a few weeks ago, and this has a magnet closing lock that wakes up the screen.
Can it be that this magnet disturbs the digitizer, or is it more likely to be software/OS related?
In dev options I have NOT "Force GPU rendering" or anything else beside "Allow mock locations" and "Stay awake while charging".
BR,
Christopher
I have an S6 Edge, model SCV31, currently running android 7 (updated last night).
Due to my work, I've been in the habit of always having my phone in silent/vibration mode. This has been the case, with this same phone, for around two years. Maybe two or three days ago there was a notification on my lock screen telling me that my phone was on silent and that I may miss calls. I was given the option to take my phone off silent, or say "it is okay". I have never had this notification before. Normally if I receive a notification I don't care for, I long press on it and turn off notifications for whatever is causing it. I could not long press on the notification, and touching the screen to unlock my phone caused the notification to disappear. This was while running android 6. Around the same time these notifications started I was emailed by my service provider that I would soon be able to download android 7. I received the notification a few times before updating, both while charging and not. I was hoping the update would reset/fix whatever triggering the notification, but have still been receiving it since.
I have not been able to force the notification to reappear. I have tried turning on sounds and turning them off again, restarting my phone, and leaving my phone charging for a few minutes (I initially noticed it while charging) to no avail. Until now, I haven't thought of taking a screen shot, but if necessary I will try to remember when next it occurs.
Does anyone know what is causing this notification and how to turn it off?
Thank you in advance,
JB
After recent Android Pie update, (9.0.0.232(C636E10R3P), I cannot set a screen timeout any longer than 10 minutes. Prior to this Android update, there was a "NEVER" option at the bottom of the list.
Without this option, streaming is constantly being interrupted. How can this option be reinstated?
Thanks.
Hello,
I currently have 2 problems on my redmi note 5.
The first is that I no longer receive notification of receipt of a message. I have to go into the application to notice that I have received a new message. No data in the circle above the application or on the lock screen when everything is set up and everything worked before.
I have exactly the same problem with the Facebook app.
My second problem is having a lot of little bugs:
- screen that remains on the wallpaper with no applications usable for several seconds
- phone vibrating, which lights up on the lock screen but nothing appears on the screen. I have to scroll up and down, phone unlocked, to get the notification
- camera that borders on and does not save the photo
- Etc
Could you tell me how to resolve all of these problems?
Thank you
Mobile: Redmi note 5
Firmware: 11.0.3
I've been documenting my struggles with my lock screen in another thread. But I just had a major breakthrough and didn't want this to get buried.
To recap, my lockscreen has been a buggy mess from day one. The fingerprint sensor barely works, the fingerprint icon randomly disappears, and the gray border that's supposed to appear around the fingerprint icon simply doesn't show up. The lockscreen doesn't light up when I pick up the phone either (it stays dimmed). Also, wallpapers don't show up on the lock screen, and the big ugly clock sometimes disappears or moves itself to the top-left.
I've tried just about everything to fix this. As a last-ditch effort, I added a new user profile only to find that the lockscreen works perfectly well for this new profile (but still not for my main one).
Here's my main profile with the unusable lockscreen:
broken lockscreen of main profile
Watch "broken lockscreen of main profile" on Streamable.
streamable.com
And here's what it looks like when using the other profile:
working lockscreen on new profile
Watch "working lockscreen on new profile" on Streamable.
streamable.com
So there's clearly some obscure bug that most people aren't experiencing here. I'd love to just figure it out so I can move on.
When I didn't have the "always on display" turned on, the phone was very consistant about turning on properly when I picked it up. I ran it this way for 3-4 days without any issues.
After reading some articles on the P6, I realized that it has an AOD and that it was turned off. So I turned the AOD on while leaving all the other settings set the same. At first, the finger print icon wouldn't appear consistantly, but that is because I had adjusted the animation scale settings in the Developer settings. Changing that back to stock fixed the issue with the finger print icon not showing up.
That beings said, I have experienced the same "unresponsive" screen many times over the last couple of days that I have had the AOD turned on. The screen stays dimmed (or even turned off if I pull the phone out of my pocket) and the finger print reader is inactive (even though the icon is displayed). The screen is suppose to turn on when I lift the phone up, but it doesn't always do it. When this happens, I have to either manually turn the screen on using the power button, or double tap the screen to wake it. This is clearly a bug in the system somewhere. I probably need to report it to Google, but hopefully it is fixed soon.
After spending way too long on this, I've determined that the bug occurs consistently with these specific settings (although it may also occur for similar ones):
Lock after screen timeout: 30 minutes (or anything high enough to prevent it from locking between tests)
Power button instantly locks: disabled
Lift to check phone: disabled
Tap to check phone: disabled
Always show time and info: enabled
Replication steps:
1) Enter the above settings
2) Press the Power button to go to the lockscreen
3) Set your phone down for a couple seconds
4) Pick your phone back up and try to use the fingerprint sensor
Result: The fingerprint sensor won't work the first time.
I think all the other issues I had were actually stemming from this one issue.