I think there is a bug with the "Moto Display" feature in Moto E 2015 (3G version). I have ambient display turned off + Moto Display turned on. Even then, I am unable to see the time OR the notifications on the lock screen.
Anyone else facing the same bug?
I buy a Motorola X recently and till date not facing any problem but screen brightness is low.
liquiddeath said:
I think there is a bug with the "Moto Display" feature in Moto E 2015 (3G version). I have ambient display turned off + Moto Display turned on. Even then, I am unable to see the time OR the notifications on the lock screen.
Anyone else facing the same bug?
Click to expand...
Click to collapse
It will only show by moving the phone. It doesn't work like the Moto X. You have to physically move the phone, and it will only work if the phone's sensor detected movement from a still position for about five seconds. I have no issues with mine, so maybe try turning both off, and then back on again.
bobbyphoenix said:
It will only show by moving the phone. It doesn't work like the Moto X. You have to physically move the phone, and it will only work if the phone's sensor detected movement from a still position for about five seconds. I have no issues with mine, so maybe try turning both off, and then back on again.
Click to expand...
Click to collapse
I have tried moving the phone among other things - the Moto display feature just doesn't start. Maybe it's a bug with the Indian 3G version only?
I Also have the moto e 2015 3G version(India) but not face any problem with the moto e.
I think it's a software problem..
You can try the factory reset.
Sent from my MotoE2 using XDA Free mobile app
Its a software bug Dude i also have the same phone but haven't faced this problem. May be you should try factory reset.:good:
I had same problem
Then I turned off the moto app under settings and turned off the learning feature and the screen stays off
How do we turn off moto active display?
erapmicks said:
How do we turn off moto active display?
Click to expand...
Click to collapse
Open the Moto app. It's one of the setting in the app.
Related
Hello friends,
I am facing a weird problem these days. I own the GSM version of Razr and the screen randomly awakes from sleep without doing anything and it happens repeatedly.. i switch off the display using power button and it again becomes active in one or two seconds..This happens everyday once in a while..I would be grateful if you guys can help me about it as it is eating up my battery
no reply ?? :S
You might have something running in the background that's preventing sleep. Try checking what you have running when it comes on by itself. CPU spy is a great app to use to verify sleep.
Sent from my DROID RAZR using xda premium
manish.sanil said:
Hello friends,
I am facing a weird problem these days. I own the GSM version of Razr and the screen randomly awakes from sleep without doing anything and it happens repeatedly.. i switch off the display using power button and it again becomes active in one or two seconds..This happens everyday once in a while..I would be grateful if you guys can help me about it as it is eating up my battery
Click to expand...
Click to collapse
Something like this happened to me when i turned on the option "In-Pocket Detection" over Dislay Options, turning it off solved my problem.
I don't think In-pocket Detection is the culprit here, since that would cause the screen to go off when something approaches the sensor near the LED notification light. It likely would be a background process waking up the phone/screen. Are there any notifications that come up when the screen turns on? Check in your task list for suspicious items.
i used the application you suggested..However it doesnt show any unusual activity..thanks a lot
robertiv said:
I don't think In-pocket Detection is the culprit here, since that would cause the screen to go off when something approaches the sensor near the LED notification light. It likely would be a background process waking up the phone/screen. Are there any notifications that come up when the screen turns on? Check in your task list for suspicious items.
Click to expand...
Click to collapse
i dont see any weird applications running in the background.. can the signal drop cause this or changing from 2g to 3g n vice versa.. Will changing the sim-card help??
My moto e 2nd gen home button doesn't work or bring me to the home screen. Also, I can't enable the security settings on my phone, so when the phone screen goes black, enen though I've set a pin and selected that method of locking it, it doesn't look the screen. I've even set it to lock immediatly after the phone goes into sleep mode but it still doesn't lock my phone. Doe ls anyone have a solution to this. I have Android lollipop 5.0.2.
Passionchick said:
My moto e 2nd gen home button doesn't work or bring me to the home screen. Also, I can't enable the security settings on my phone, so when the phone screen goes black, enen though I've set a pin and selected that method of locking it, it doesn't look the screen. I've even set it to lock immediatly after the phone goes into sleep mode but it still doesn't lock my phone. Doe ls anyone have a solution to this. I have Android lollipop 5.0.2.
Click to expand...
Click to collapse
this section is of moto e 1st gen (2014). search for moto e 2015 on xda and ask your question there.
Hi everyone, I've had my Moto Z for a couple of days now and am pretty happy with the device - even with the battery life I have one small problem, however.
Sometimes, when the screen is turned off, the Moto Display approach action won't work. In these cases, I also notice that the bottom right IR sensor isn't lit up - which it usually is when the display is turned off. The approach action only starts working again when I pick the phone up. This is very inconvenient and not how it's meant to be.
Is anyone else experiencing this bug?
At first I thought it might be an issue with Doze putting the process responsible for the Moto Actions to sleep, but after whitelisting all Moto apps the issue still sometimes occurs. I have not yet found out under which circumstances this happens.
Any help would be greatly appreciated!
EDIT: It seems this issue only occurs immediately after turning off the screen, after which there is a slight delay (a couple of seconds) before the IR sensor is activated. I will observe if this is really the case, which of course would render it a non-issue.
Is anyone else having issues with AOD turning off even with slight darkness. For some reason my AOD keeps turning off even though there still some light in the room. It used to stay on when I wake up at 6am when there some sunlight but now it just turns off. I have to point the phone directly to the light sometimes to get it to turn on. Don't have any screen protector that is blocking the light sensor and seems to function correctly checking the debug mode (*#0*#). I have to reboot the phone to fix the issue but after a few days it goes back to being wonky.
yeah, i updated it via Samsung Galaxy App store, then did a data clear in the setting menu and now it works. But mine did the exact same thing.
clearing the data still causes me the problem.. Only fix for me is to reboot the phone =/
Do you have a screen protector?
Tidbits said:
Do you have a screen protector?
Click to expand...
Click to collapse
I have a screen protector but have all the cutouts that isn't blocking the proximity sensor. I've tested the sensor in debug mode and no issues at all.
what was updated or installed recently that had this started happening with. It may be an app that introduced a bug. Did you try and see if there is a AOD update?
Tidbits said:
what was updated or installed recently that had this started happening with. It may be an app that introduced a bug. Did you try and see if there is a AOD update?
Click to expand...
Click to collapse
what screwed it up was the AOD update (go figures ).. I reverted back to the original before the update but somehow it's broken now. As mention it works like it should after a reboot but after a few days it becomes all wonky.
I purchased my S21 about 5 weeks ago and I am not sure if I have been experiencing this issue since I bought it but in the last week, I have noticed this issue. When my phone is locked, the AOD will either show for a few seconds to a minute or just won't show. I've ensured it is set to always show, power-saving not set to turn it off, no Bixby routines and any updates are installed for phone/AOD. I've even factory reset my phone and removed the case and screen protector and the issues are still persisting. Does anyone else experience this issue?
Disable all power management... it screws up all kinds of things.
Does AOD show if you tap the screen?
I have disabled all power management that I am aware of and still experiencing issues. I've set it to show on tap and while it worked the first time, subsequent taps do not show the AOD
Video demonstrating AOD tap to show issue
Sounds like a firmware glitch or the flash was corrupted.
Double check all AOD and screen lock settings.
Try turning AOD always on.
Try disabling screen lock... a lock out is the last thing you want anyway.
Play with it... Android's wuv attention.
The case or screen protector won't do this more than likely.
blackhawk said:
Sounds like a firmware glitch or the flash was corrupted.
Double check all AOD and screen lock settings.
Try turning AOD always on.
Try disabling screen lock... a lock out is the last thing you want anyway.
Play with it... Android's wuv attention.
The case or screen protector won't do this more than likely.
Click to expand...
Click to collapse
I normally use AOD always on, I'd tried the tap on the option to test. Going to try flashing it today to see if that helps despite the factory reset not helping.
So I've flashed the stock firmware back onto my device and the issues are still persisting. I've contacted support through the Samsung Members app and it's been escalated to the Research and Development team and am just waiting to hear back.
Did you update any Samsung apps after the reload before testing it? Go with the factory app loads.
Try disabling the lock screen... they tend to end up locking out the intended user anyway, sooner or latter.
If no one else is having this issue it very well maybe a hardware issue.
Did you ever wonder what happens when one or two micro transistor junctions out of the millions in a phone fail? Yes, well...
Unfortunately I can't recall if Samsung apps updated before I tested. I've already factory reset a few times so I'd rather avoid that for now. I've noticed the issues occur when using auto-brightness on AOD in lower light settings. When I say lower light, I mean in my study during the day which I never experienced issues with on my S20 FE. I've sent a report to Samsung Members and am waiting on them to come back to me.
The you
brodieb321 said:
Unfortunately I can't recall if Samsung apps updated before I tested. I've already factory reset a few times so I'd rather avoid that for now. I've noticed the issues occur when using auto-brightness on AOD in lower light settings. When I say lower light, I mean in my study during the day which I never experienced issues with on my S20 FE. I've sent a report to Samsung Members and am waiting on them to come back to me.
Click to expand...
Click to collapse
Did you ever get this fixed. I have the exact same issue on my s20 ultra
Edit: Nevermind just fixed it after 3 days troubleshooting. Oddly it was the the disable AOD while in power saving mode that needed to be disabled even though I don't use power saving mode. Samsung never seem to amaze me with these dumb persistent bugs.
Glad to see you solved the issue. I'd already confirmed this setting was off for me. It's still happening. Looks like it's something to do with the level of light detection as the issue only happens when I have auto brightness set for the AOD. The problem is it's not even that dark when it's happening and never occurred with my S20 FE.