Related
anybody working on or considering making notification light using the capacitive buttons on the bottom? is it possible to use those leds as a notification?
That would be an awesome solution...
To use as notifications OnLY the capasitive buttons and not all Screen as "NoLED" app...
+1 from me...
+1 I also agree
and maybe a stretch and maybe you guys dont agree but you could also have each button be a different notification, ie:
text message the back button would light up, email the menu button so on and so fourth
+2 for this idea
It's already been done for the galaxy s's, BLN requires a custom kernel though.
I prefer NoLed, in the market, works great for notifications. NoLed
Im thinking about getting a Nexus S.
The only thing stopping me is the lack of notification LED.
It would be pretty good if this could work.
And being able to tell if its sms or email etc from which button lights would be very cool. But i would think the backlight is just one big light.
I've had a look at NoLed, but it doesnt seem ideal. If i get a notification while im asleep, the screens going to stay on for up to 8 hours non stop? That doesnt sound good.
Also it seems to mess with the lock screen and wake up of the phone.
So i just noticed today when pressing the capacitive button, it turns off. that likely means each one is lit independently from a separate LED correct? so if thats the case, theoretically each led should be able to flash independently?
terryhau said:
Im thinking about getting a Nexus S.
The only thing stopping me is the lack of notification LED.
It would be pretty good if this could work.
And being able to tell if its sms or email etc from which button lights would be very cool. But i would think the backlight is just one big light.
I've had a look at NoLed, but it doesnt seem ideal. If i get a notification while im asleep, the screens going to stay on for up to 8 hours non stop? That doesnt sound good.
Also it seems to mess with the lock screen and wake up of the phone.
Click to expand...
Click to collapse
From what I read... the NOLED app works well with the AMOLED screens because blacks dont use power. It basically turns on for that single notification or something like that.
You should read more about it from the vibrant sub forum.... with both having AMOLED screens.
azn2050 said:
From what I read... the NOLED app works well with the AMOLED screens because blacks dont use power. It basically turns on for that single notification or something like that.
You should read more about it from the vibrant sub forum.... with both having AMOLED screens.
Click to expand...
Click to collapse
Correct, in amoled screens the only pixels drawing power are the ones that are being lit for the notification. You can also set the notifications to timeout after a certain amount of minutes, and can also set a "sleep time" so there no notification while you're sleeping at night. Another awesome feature is the use of the proximity sensor, so that if the phone is in your pocket it doesn't turn on the notification but once you take your phone out of your pocket the notification shows up on the screen.
Check the devs thread for more info:
integra891 said:
So i just noticed today when pressing the capacitive button, it turns off. that likely means each one is lit independently from a separate LED correct? so if thats the case, theoretically each led should be able to flash independently?
Click to expand...
Click to collapse
This is EXACTLY what I hoped was going to be possible.
integra891 said:
So i just noticed today when pressing the capacitive button, it turns off. that likely means each one is lit independently from a separate LED correct? so if thats the case, theoretically each led should be able to flash independently?
Click to expand...
Click to collapse
You would think this would've the case but not exactly. The galaxy s does this also but it is not possible to activate the leds separately
Sent from my Nexus S using XDA App
matt_stang said:
You would think this would've the case but not exactly. The galaxy s does this also but it is not possible to activate the leds separately
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Yes, I was also thinking this too but could there be some sort of app written making it believe all other buttons were "pressed" so their lights were off once a notification came in? I strongly believe ANYTHING can be changed with a few smart edits I mean people here on XDA bring multi-touch and FM radio's to devices that shouldn't have those features!
Even if you could have each notification have a different light dimmed as if it were being "pressed"
As in: Text message= all lights lit BUT the home
Voicemail=all lights lit BUT the back button ETC...
If they could be seperate that would be great but honestly even if it's all of them it's good enough for me, I just wanna see SOMETHING if my phone is just sitting there
ikon8 said:
It's already been done for the galaxy s's, BLN requires a custom kernel though.
I prefer NoLed, in the market, works great for notifications. NoLed
Click to expand...
Click to collapse
NoLED is ok except for 2 things for me.
1 - I don't like the dots/icons hopping around the screen. I would rather they were just lined up across the top or the side.
2 - It plays around a bit much with turning the screen on and off.
Looking at NoLED there is NO reason why he couldn't make it act exactly like the Notification LED for the Ball on the Nexus One. Just have different colors for different notifications and rotate them on the same cluster of 4 LEDS on the top right of the phone.
Boom you have rotating colored notifications simple and effective
I wish I was better at coding stuff...haha
I'm glad there is a thread going about this!
Sent from my Nexus S using XDA App
You couldn't be anymore on point man. The jumping about is slightly unprofessional.
hopefully well see some work towards this once some custom roms start coming out
The reason the notifications move around the screen is so that it doesn't burn out those pixels.
dudeimgeorge said:
You couldn't be anymore on point man. The jumping about is slightly unprofessional.
Click to expand...
Click to collapse
Yes I agree, it would be amazing if they just slid around your screen or drifted all over. OR a pulsing light pops up on the screen just like a virtual trackball like the nexus one!
sassyness77 said:
Yes I agree, it would be amazing if they just slid around your screen or drifted all over. OR a pulsing light pops up on the screen just like a virtual trackball like the nexus one!
Click to expand...
Click to collapse
clearly you guys do not understand why it jumps around so unprofessionally
do you want burned out pixel?
After playing with the Lollipop build for a while on the Moto X 14, I think for me the biggest thing that will take the most getting used to on the N6 is not having Moto display. Sure Googles implementation is OK, but no where near as useful ad Moto's.
Cant beat picking up the phone and having your messages show up. Or better yet waiving your hand over the display to light it up.
This and moto assist are the only reason I may hang on to my Moto X 14. I use the hand wave feature frequently. Way more than i thought i would. Moto assist for driving and at home is so convenient. It's like having Amazon's echo wherever you are. Sure the N6 has always listening but I don't think you can answer phone calls and reply to messages hands free.
If the moto apps can be hacked to work on the N6 I may go for it.
jmill75 said:
Cant beat picking up the phone and having your messages show up.
Click to expand...
Click to collapse
That's how it works on the N6.
Try agent app. That's a good replacement for talking and replying back to texts while driving. Dynamic notifications is almost exactly like moto display
Sent from my XT1053 using Tapatalk
I need to get a new phone, and the only thing keeping me from the Nexus 6 is the lack of Moto Display/Moto Suite/Moto Voice, etc. I've yet to hear from a 2014 Moto X user who says that they wouldn't miss it.
The way it works on the nexus is when you pick up the phone the active display turns on. The same as the moto
magestic1995 said:
The way it works on the nexus is when you pick up the phone the active display turns on. The same as the moto
Click to expand...
Click to collapse
The Moto X's active display also pulses like a notification LED, and you can also just wave your hand over it to get it to turn on.
_MetalHead_ said:
The Moto X's active display also pulses like a notification LED, and you can also just wave your hand over it to get it to turn on.
Click to expand...
Click to collapse
The N6 version pulses as well, so it's only missing the wave function.
Credit & Thanks to biggiestuff for the following:
"Ambient display looks similar but in no way is close to moto display. Moto display uses the low power contextual processor in order to save battery. Ambient display uses the amoled ability to fire up specific pixels in order not to waste battery. The minute you interact with ambient display the screen fires up 100 percent. Moto display let's you interact without ever using the primary processor until you unlock. It's a step in the right direction but not there just yet."
Battery impact will be substantially greater.
l_stevens said:
Credit & Thanks to biggiestuff for the following:
"Ambient display looks similar but in no way is close to moto display. Moto display uses the low power contextual processor in order to save battery. Ambient display uses the amoled ability to fire up specific pixels in order not to waste battery. The minute you interact with ambient display the screen fires up 100 percent. Moto display let's you interact without ever using the primary processor until you unlock. It's a step in the right direction but not there just yet."
Battery impact will be substantially greater.
Click to expand...
Click to collapse
Uuhm... i'm sorry.... but i'd personally be questioning biggiestuff's basis for his comment. Watch video's of "Moto Display", and then watch the video of Ambient Display. There is physically no difference as to how one functions compared to the other. In Lollipop's Ambient Display, you get the typical Lollipop notification look, with the notifications showing up under the clock, also saying what the notification is, what was said in the text message, etc... When you interact with a particular notification, yes, the display turns on completely. Then look at "Moto Display". Yes, you can touch the screen to "interact" with them... but with either system, the display has to be turned on to do anything more than that. Only difference i can see is that Moto Display uses less pixels, since it only lights up up to 3 circles with the app icon in the middle, unless you have more than 3 notifications.... at which point you get a menu-like notification as the 3rd one.
Long story short...
Ambient Display = notifications are displayed on screen, and interacting with them (to see your list of e-mails/texts received, or opening the app directly from the notification) powers the display on completely.
Moto Display = Notification icons are displayed on screen. Interacting with those allows you to see what the notification says. Interacting FURTHER powers the display on completely to open the app so you can do what you need to do.
No difference at all power requirement wise (except for the minuscule amount of power needed for the couple extra pixels in Ambient Display) that i can see.
elementaldragon said:
Uuhm... i'm sorry.... but i'd personally be questioning biggiestuff's basis for his comment. Watch video's of "Moto Display", and then watch the video of Ambient Display. There is physically no difference as to how one functions compared to the other. In Lollipop's Ambient Display, you get the typical Lollipop notification look, with the notifications showing up under the clock, also saying what the notification is, what was said in the text message, etc... When you interact with a particular notification, yes, the display turns on completely. Then look at "Moto Display". Yes, you can touch the screen to "interact" with them... but with either system, the display has to be turned on to do anything more than that. Only difference i can see is that Moto Display uses less pixels, since it only lights up up to 3 circles with the app icon in the middle, unless you have more than 3 notifications.... at which point you get a menu-like notification as the 3rd one.
Long story short...
Ambient Display = notifications are displayed on screen, and interacting with them (to see your list of e-mails/texts received, or opening the app directly from the notification) powers the display on completely.
Moto Display = Notification icons are displayed on screen. Interacting with those allows you to see what the notification says. Interacting FURTHER powers the display on completely to open the app so you can do what you need to do.
No difference at all power requirement wise (except for the minuscule amount of power needed for the couple extra pixels in Ambient Display) that i can see.
Click to expand...
Click to collapse
No, it's different. With the Moto X, you can interact with the screen and view the notification without the phone actually turning on, whilst still only using the low power contextual processor. You can't respond to it, but you can view it. And again, unless you physically unlock the device, it is all done with the low power contextual processor while the phone is technically still asleep. With the N6 and Ambient Display, the moment you touch the screen it wakes up the phone, lights up in full color and uses the full power processor. There is a reason why when you use Ambient Display the standby battery life gets chopped by about 25%. Check out the specs sheet for the N6- Standby time is 330hrs with Ambient Display off, and 250hrs with it on. http://www.google.com/nexus/6/
_MetalHead_ said:
No, it's different. With the Moto X, you can interact with the screen and view the notification without the phone actually turning on, whilst still only using the low power contextual processor. You can't respond to it, but you can view it. And again, unless you physically unlock the device, it is all done with the low power contextual processor while the phone is technically still asleep. With the N6 and Ambient Display, the moment you touch the screen it wakes up the phone, lights up in full color and uses the full power processor. There is a reason why when you use Ambient Display the standby battery life gets chopped by about 25%. Check out the specs sheet for the N6- Standby time is 330hrs with Ambient Display off, and 250hrs with it on. http://www.google.com/nexus/6/
Click to expand...
Click to collapse
Yes..... but on the other hand.... they've actually gone ahead and POSTED their estimated battery life with it on and off. Looking at the Moto X, all you get is "24 hours mixed usage". Nothing saying what to expect with Moto Display on or off. I'd assume it probably kills the battery just as much... but i couldn't find a review that tested battery life with it on and off.
Again.... with Moto Display, you get notification circles.... only showing the app icon. You touch the icon, and you get what the text message says and who it's from, or what the e-mail you received was about. You can then slide your finger up to the app icon again to unlock the device, turning the screen on fully, and opening up to that message.
With Ambient Display, it's no different from the standard lock screen with the notifications showing, aside from it using only the required pixels. The ONLY difference between it and Moto Display is that for Moto Display, you have to touch the notification icon on the screen to see what the notification says, whereas with Ambient Display, when it turns on, whatever you'd really need to see is already there. Moto Display just adds one extra step to the process.
l_stevens said:
Moto display uses the low power contextual processor in order to save battery. Ambient display uses the amoled ability to fire up specific pixels in order not to waste battery..
Click to expand...
Click to collapse
This doesn't make any sense to me. Those two things are not mutually exclusive. Both Moto Display and Ambient Display take advantage of AMOLED's ability to only light up select pixels to conserve battery when displaying notifications. As for the use of a low power processor to save battery when displaying notifications, the Snapdragon 805 SoC has a Hexagon DSP built-in, so it's possible that the Nexus 6's Ambient Display is also using a low power processor to display notifications. It's simply too early to say that this difference exists between Ambient Display and Moto Display.
elementaldragon said:
Yes..... but on the other hand.... they've actually gone ahead and POSTED their estimated battery life with it on and off. Looking at the Moto X, all you get is "24 hours mixed usage". Nothing saying what to expect with Moto Display on or off. I'd assume it probably kills the battery just as much... but i couldn't find a review that tested battery life with it on and off.
Again.... with Moto Display, you get notification circles.... only showing the app icon. You touch the icon, and you get what the text message says and who it's from, or what the e-mail you received was about. You can then slide your finger up to the app icon again to unlock the device, turning the screen on fully, and opening up to that message.
With Ambient Display, it's no different from the standard lock screen with the notifications showing, aside from it using only the required pixels. The ONLY difference between it and Moto Display is that for Moto Display, you have to touch the notification icon on the screen to see what the notification says, whereas with Ambient Display, when it turns on, whatever you'd really need to see is already there. Moto Display just adds one extra step to the process.
Click to expand...
Click to collapse
I haven't really tested it on my 2014 Moto X yet, but I can tell you from personal experience with my 2013 Moto X that Active Display has pretty much zero effect on standby battery life. My 2013 loses about 1% overnight, and maybe 3-4% a day if I just let it sit. That's with or without Active Display being on. That's the whole point of the low power contextual processor, it can do these things (Active Display, Moto Voice) with negligible effect on battery life. It was designed that way. Judging from the stated specs of the Nexus 6, it doesn't seem like they had Ambient Display in mind when designing the hardware. I mean, an 80 hour hit to standby battery life is pretty substantial.
As far as the information that's displayed is concerned, I can't really comment on it because I have no experience with the N6. But it does seem that you are correct in that it displays the same or similar information, albeit with one less step. In my point of view, that's actually a bad thing because it brings up some privacy concerns. The Moto X just pulses the type of notification for all to see- if you want to see the contents of it, you need to physically interact with the display. The N6 with Ambient Display, actually pulses the content of the notification which I'm not so keen on.
In the same boat. The Moto features truly change how one uses a phone. Am worried by getting the N6, that I'd miss these features a great deal.
Waste of a click
Anyone have the screen shot of the moto x2014 lollipop updates before they took it down? Even Motorola somewhat acknowledge that ambient display drains more than moto display. Moto x 2014 will have ability to use both.
Sent from my XT1053 using Tapatalk
What are the odds of the moto features becoming available for the N6, either from porting or moto directly making them available?
johnchad14 said:
What are the odds of the moto features becoming available for the N6, either from porting or moto directly making them available?
Click to expand...
Click to collapse
If they haven't been done by now, I'd say the chances are slim. What features are you looking for. There are solid alternatives but I agree with most that Motorola's implementation has much tighter and cleaner integration. I actually gave up on my nexus 5 for a moto x. I probably would have ended up with the new moto x if it wasn't for that tiny battery.
Sent from my XT1053 using Tapatalk
You think some build prop. editing would allow moto suite to work? That is the main advantage of Nexus devices. Tinkering ?
ok so i got the Moto X 2014 ,Droid turbo and others Motorola.
the Active display works like that: when u got a notification the screen lights untill u read or dismiss the notification.
on Moto X play the phone acts in another way: lights one time ,then nothing untill u take the phone in ur hands. then the phone lights up and make u see that u got new notification.
why? why the screen doesn lights up more times like on Moto X 2014?
thanks
sorry for bad english
moto x 2014 have proximity sensors. I was just going to hand over the phone to read notifications. play moto x uses the gyroscope to capture action, and turn on the screen when you take the pocket phone.
Enviado de meu XT1563 usando Tapatalk
riewe said:
moto x 2014 have proximity sensors. I was just going to hand over the phone to read notifications. play moto x uses the gyroscope to capture action, and turn on the screen when you take the pocket phone.
Enviado de meu XT1563 usando Tapatalk
Click to expand...
Click to collapse
Moto x play doesn t have gyroscope...
danger2u said:
ok so i got the Moto X 2014 ,Droid turbo and others Motorola.
the Active display works like that: when u got a notification the screen lights untill u read or dismiss the notification.
on Moto X play the phone acts in another way: lights one time ,then nothing untill u take the phone in ur hands. then the phone lights up and make u see that u got new notification.
why? why the screen doesn lights up more times like on Moto X 2014?
thanks
sorry for bad english
Click to expand...
Click to collapse
Because the play uses an LCD vs AMOLED on the 2014. This would drain a lot more battery if it kept powering the entire screen for repeat notifications.
But the Moto X Style which has a larger LCD screen and a smaller battery does repeat notifications, this must be either a bug of the Moto X Play or just ****...
Hi got a moto x play yesterday and I dont like the notification ''active screen''.. I need to toutch my phone to see the notification...wtf Is it possible to have something flashing??
Josh2123 said:
Hi got a moto x play yesterday and I dont like the notification ''active screen''.. I need to toutch my phone to see the notification...wtf Is it possible to have something flashing??
Click to expand...
Click to collapse
It has a hidden led light, we're just waiting for squid2 to update his kernel for marshmallow. You can try cm13 as well. We definitely don't want the lcd screen to keep flashing, like dictionary said, it would murder our battery life.
Any update about the LED notification light, how to activate it. I am running the unrooted Marshmallow OTA update.
Thanks in advance.
edy.xda said:
Any update about the LED notification light, how to activate it. I am running the unrooted Marshmallow OTA update.
Thanks in advance.
Click to expand...
Click to collapse
Only with root devices...
How to deactivate the proximity sensor? Because earlier i did turn it off and now i have factory reset the phone but not able to find the settings for the same. Please help
My biggest source of frustration right now is how inconsistent Ambient Display is. I suppose I was spoiled with the Moto X because it worked without fail all the time. On stock android Ambient Display just sort of comes on when it feels like it, but it's even more inconsistent on this phone than it was on my Nexus 6. It's to the point that I don't even rely on it, I just go straight for the fingerprint reader or power button because otherwise, I end up just looking at a black screen 98% of the time.
This applies both to when I have notifications and don't. Sometimes, I'll pick it up and it'll show me the time. Other times, nothing. I pull it out of my pocket with a notification, notification light blinking and everything and the screen never comes on until I hit the power button or scan my finger.
That is frustrating. I was hoping to notification on the home screen "light up" like they do on the iPhone. I find this feature useful when I'm driving. Are you saying you have the feature enabled and it works intermittently?
Mine hardly ever works like it should...
Sent from my Nexus 6P using Tapatalk
Hopefully a software update will fix the issue.
Same here. Coming from a Turbo I miss it...I wish we could use the proximity sensor to activate it...
Same here. I hope some custom rom may bring moto x like active display.
Ambient Display is totally fubar on my 6P; no notifications whatsoever, the phone is sitting on my desk, and it just lights on and on and on wihout any reason.
That's bizarre...mine works 90% of the time as expected.
wewewi999 said:
Ambient Display is totally fubar on my 6P; no notifications whatsoever, the phone is sitting on my desk, and it just lights on and on and on wihout any reason.
Click to expand...
Click to collapse
Have a feeling you have an app installed that controls the led, ex lightflow or light manager. If so disable said app and this will stop happening.
At least that was the problem in my case..
richport29 said:
Have a feeling you have an app installed that controls the led, ex lightflow or light manager. If so disable said app and this will stop happening.
At least that was the problem in my case..
Click to expand...
Click to collapse
I dont have any LED control apps installed and mine does exactly what wewewi999 is saying. I will hear it and look, nothing happens. If I pick it up, it ONLY activates Ambient Display with it is completely vertical. If it goes away and I want Ambient Display to activate again, forget it. I basically have to do the twisting motion that I used to do to activate the camera on the Moto phones to get the Active Display to turn on.
Currently, I have an unread notification. Ambient Display activated instantly, then pulsed once after about 5 seconds. Then pulsed again after about 10 seconds. Still unread, it has stopped pulsing altogether? The next notification, it didnt pulse at all. Random.
tluley51 said:
Currently, I have an unread notification. Ambient Display activated instantly, then pulsed once after about 5 seconds. Then pulsed again after about 10 seconds. Still unread, it has stopped pulsing altogether? The next notification, it didnt pulse at all. Random.
Click to expand...
Click to collapse
Mine does exactly this. It's been irritating me. I've tried uninstalling apps, clearing cache and still it occurs.
Shame because I like the ambient display feature. Hopefully a software update can fix this.
If you find a solution do let me know.
Sent from my Nexus 6P using Tapatalk
+1
Coming from a Droid Maxx I am so used to just pulling my phone out off my pocket or lightly nudging it when it's sitting on the desk and having the time (and any recent notifications) show up without having to do anything else. With the Nexus 6p, just as others have said, it's so random that I can't even figure out how it's supposed to work. Surely this is not what they intended. I really hope they can and will fix it.
Seriously missing Moto!
Mine seems a little better with the notification led off. Can't say its perfect as I'm used to Moto's awesome implementation, but its definitely better without the notification led on for me.
I think it's Doze. My Nexus 6 was very sensitive until I updated to Marshmallow. It still responds reliably when I pick it up, but it is less sensitive to nudging and of course notifications are delayed because of how Doze works.
Poser said:
That's bizarre...mine works 90% of the time as expected.
Click to expand...
Click to collapse
Mine has been working at least 90% of the time too. I was worried after seeing all these posts but it's been working great.
jamespat93 said:
Mine has been working at least 90% of the time too. I was worried after seeing all these posts but it's been working great.
Click to expand...
Click to collapse
Mine wasn't working well, so I installed AcDisplay. It now works much better. Not sure if it is the app or the setting that is making it work, but it is now working well enough to make me feel like compares to my old Droid Maxx.
I realised that the tempered glass screen protector I was using (which had no cutout for proximity sensor) was the trouble maker. I knew the protector was already causing trouble while receiving/disconnecting calls but had it for the time being until I got a correct one. Now that I removed the screen protector the ambient display works flawlessly!
cynicist said:
I think it's Doze. My Nexus 6 was very sensitive until I updated to Marshmallow. It still responds reliably when I pick it up, but it is less sensitive to nudging and of course notifications are delayed because of how Doze works.
Click to expand...
Click to collapse
I wonder if we can turn off battery optimization for the app or service which controls ambient display? Anyone know what it is called?
---------- Post added at 11:41 AM ---------- Previous post was at 11:40 AM ----------
jmaclean62 said:
Mine wasn't working well, so I installed AcDisplay. It now works much better. Not sure if it is the app or the setting that is making it work, but it is now working well enough to make me feel like compares to my old Droid Maxx.
Click to expand...
Click to collapse
Any noticeable effect on battery life?
jmaclean62 said:
Mine wasn't working well, so I installed AcDisplay. It now works much better. Not sure if it is the app or the setting that is making it work, but it is now working well enough to make me feel like compares to my old Droid Maxx.
Click to expand...
Click to collapse
so your using AcDisplay instead? Or AcDisplay improved your ambient display somehow?
manas.neo said:
I realised that the tempered glass screen protector I was using (which had no cutout for proximity sensor) was the trouble maker. I knew the protector was already causing trouble while receiving/disconnecting calls but had it for the time being until I got a correct one. Now that I removed the screen protector the ambient display works flawlessly!
Click to expand...
Click to collapse
Yeah my screen protector has the cut out too and I've never really had a problem with ambient display. Tried a Moto x Pure before and it pretty much works just as good.
jamespat93 said:
so your using AcDisplay instead? Or AcDisplay improved your ambient display somehow?
Yeah my screen protector has the cut out too and I've never really had a problem with ambient display. Tried a Moto x Pure before and it pretty much works just as good.
Click to expand...
Click to collapse
I tried AcDisplay yesterday and its useless if you use the fingerprint scanner to unlock. AcDisplay is just another loop to jump thru to unlocking the phone. I will admit though, it DOES work MUCH better than Ambient Display. Much more sensitive.
Hi,
I use moto display without gesture detection. When i receive a notification (mail, text message, ...) the screen turns on and slowly turns off which is the expected behaviour. But then the screen keep turning on/off indefinitely until i open the notification or dismiss it.
Do you have the same behaviour ?
Moreover this behaviour is not linked to any phone mouvement as it is just laid on the table without any vibration that could wake it up.
It seems to me that this new bahaviour appeared with MM.
Either you disable Moto display for notifications or slide the unlock icon to the right so it will dismiss the notification on moto display but not on the notifications bar.
Yes, but do you confirm that this is the expected behaviour ?
I thought it was supposed to turn the screen on just one time and not to turn my screen into a christmas tree. Moto display is supposed to save our battery life, not sure it is going to reach that target with this behaviour, especially with a screen that is not an amoled...
MyGoul said:
Yes, but do you confirm that this is the expected behaviour ?
I thought it was supposed to turn the screen on just one time and not to turn my screen into a christmas tree. Moto display is supposed to save our battery life, not sure it is going to reach that target with this behaviour, especially with a screen that is not an amoled...
Click to expand...
Click to collapse
It's gonna pulse every minute or so for about 10 minutes I believe. Then it stops. If your phone is face down, it won't pulse at all.
Thanks for your feedback, too bad that we can't configure it, it's way too long by default imo.
I had a problem with the Lollipop and now the MM versions of the Moto Display. You can dismiss the notification, but it will start pulsing again for the same notification a little while later, with nothing new happening. Wasn't too bad with Lollipop, because I just switched to Ambient display which worked perfect. Now Ambient is gone for some reason.
mvmorr01 said:
I had a problem with the Lollipop and now the MM versions of the Moto Display. You can dismiss the notification, but it will start pulsing again for the same notification a little while later, with nothing new happening. Wasn't too bad with Lollipop, because I just switched to Ambient display which worked perfect. Now Ambient is gone for some reason.
Click to expand...
Click to collapse
I've checked, i don't have this behaviour on my side, once the notification is dismissed it stops pulsing... i don't understand how it can be different from one phone to another.
Edit : How did you switch to Ambient display btw ?
I haven't found a way to switch to Ambient on MM, you can only turn off Moto Display which gives you no notifications at all! It was easy with Lollipop, just go to the Moto settings and choose which display version you want.
Well it could be acceptable to turn it off with a notification led...
mvmorr01 said:
I haven't found a way to switch to Ambient on MM, you can only turn off Moto Display which gives you no notifications at all! It was easy with Lollipop, just go to the Moto settings and choose which display version you want.
Click to expand...
Click to collapse
Maybe unfortunately for some, Motorola got rid of Ambient Display in MM.
https://motorola-global-portal.custhelp.com/app/answers/prod_answer_detail/a_id/108823