I got a few people over PM and WhatsApp asking me how to enable Ambient Display on the Lava Pixel v1, so I decided to do some research on this.
I tried DVDAndroid's Enable Ambient Notifications Xposed module but it didn't work, so instead of bothering him for that, I started looking for a non-root, non-xposed way of achieving this since one of my daily use apps enforces Xposed checks and doesn't start if it detects Xposed installed. Trawling through the PlayStore I discover AcDisplay, which solves this problem in a fantastic and easy way. Look for it on the play store and rejoice in the beauty of Ambient Display!
Related
This is for CM 11S 4.4.4 Kitkat version - no need to do this on COS 13.1 6.0.1...
Short story on why I need it:
Coming from the SGS4, I got used to my habits and the functionality of the led notification that is being able to continue pulsating, even if my screen was on or I was using my phone.
The necessity derives from the fact I sometimes use my phone in silent mode and while messaging in one app, I receive notifications in another. Without pulsating led notification, I would need to finish w/e I was doing and see the notification above the app icon that received notification. Also cause I have set personalized led colors based on my contacts too, aside per app so it's rather useful to know the person A sent me whatsapp message and not person B etc...
Other times, I would just need it so it stays there for, let's say 5 minutes. Other times, I was simply asking - WTH, if it can work for the battery (without pulsating when charging), why it can not work for whatever app I need it to work?
Seen the One+1 std. functionality is not doing that, aside battery charging, but with fixed light... I searched a bit and found a workaround. Maybe there is a small tiny bit of impact on the the battery, but I could care less.
Disclaimer:
I can not be held responsible in any way for your actions in setting your phone. If you chose to follow this guide, it's your responsibility of what you're doing and of what might happen to your phone.
Requisites:
So to make the notification led working even your screen is lit, and so to continue pulsating when you turn on your screen (within the set timespan) you will need:
1. A rooted One+1 phone
2. CM11S 4.4.4 ANdroid version - xposed is working as it should, is stable and without glitches.
3. xPosed framework - lastest official and stable version (for the moment, consider KK stable ver.) - Be sure to make a system wide nandroid backup before installing xPosed framework.
4. XLED module - download from the modules repository inside xPosed app.
5. Lightflow (maybe other similar apps can fit all the the same, but I use Lightflow) - download from the Play Store, Pro version can set vast majority of apps that has and supports notifications.
Howto:
Assuming you know how to root your phone and what xPosed is and how to manage it (if not, do read some in the dedicated sections or use google)...
1. Install the xLed module, activate it in the xPosed Install app and reboot your phone.
2. Install Lightflow, open it and go to Device Settings and Root, set it up to work in the root mode only, no other settings are needed. Set your per app or per contact notifications as you're pleased.
3. Open the XLED app, check Enable XLED and Screen on LED and close it.
4. Go to your phone settings and turn off battery notification light, turn off custom values under Notification light while leaving the checkmark on Notification light option.
5. Test your notification pulsating from Lightflow app or wait to receive some notification or put your phone on the charger.
Enjoy. :victory:
Note:
I have not touched any other XLED options or set other functionality but what I already wrote, seen how both Lightflow and XLED have some similarities in what they do - I don't want them conflicting by setting the same stuff twice. You are free to try this all out even without Lightflow by setting the XLED only, but my goal was to make custom Lighflow notifications to stick while the screen is lit as I use Lightflow. I achived that and that's how far it goes for me.
Proof:
Sorry for the crappy quality and the pause followed by the cut, my net was lazy...
Hi guys, I noticed that Galaxy S6 doesn't have DOZE (lollipop's ambient display) feature.
I searched on google but the only ambient display feature is for AOSP ROMs with Xposed only (module not working on TouchWiz).
So I was wondering if someone will be able to make this feature for TouchWiz too (Xposed or not).
Thanks in advance
I have noticed once or twice if i get a notification from someone on my edge contacts it acts like a ambient display when i picked it up. Dont know if the screen was still on from it coming in or it turned on when i picked it up. But it definately reminded me of my nexus 6 ambient display with the clock lit at a low light state and the notification on the screen
So thats a good sign of it being possible
Sent from my SM-G928P using XDA Free mobile app
TENN3R said:
Hi guys, I noticed that Galaxy S6 doesn't have DOZE (lollipop's ambient display) feature.
I searched on google but the only ambient display feature is for AOSP ROMs with Xposed only (module not working on TouchWiz).
So I was wondering if someone will be able to make this feature for TouchWiz too (Xposed or not).
Thanks in advance
Click to expand...
Click to collapse
Lollipop's Ambient Display is not present in Touchwiz. You can download an app from the Play Store called Active Notifications (and one other app by a similar name with similar function) that basically does that exact same thing - and it should work without root.
(Also, side note "Doze" (not DOZE, an acronym) is not part of Lollipop, nor is it related to the Ambient Display feature. Doze is a new feature in Marshmallow that puts the phone into a high power saving mode when it's not being used.)
Anyone else have issues with Lightflow making the phone screen turn on randomly when sitting on a table? The colors for the notifications are correct, but becausue of the screen coming on alot randomly this is going to kill the battery life. I even enabled a setting to reduce this in light flow but nothing works. Does anyone have lightflow working correctly?
Thanks!!
At the moment the only option is to switch off the ambient display. If there's an outstanding notification or one is getting updated it'll trigger ambient display and lightflow always has an active outstanding notification.
I've put a feature request in to Google to allow some control of when it triggers.
Can you star the issue here*
https://code.google.com/p/android/issues/detail?id=191786
I don't seem to have this problem. Ambient display only lights up on new notifications, even with the latest Light Flow with persistent notification. I do have issues with light flow losing control on a regular basis and then I just see the standard very slow white led blink regardless of notifications. Activating lock screen promptly fixes and then I see the appropriate color and blink rare from light flow.
andrewpmoore said:
At the moment the only option is to switch off the ambient display. If there's an outstanding notification or one is getting updated it'll trigger ambient display and lightflow always has an active outstanding notification.
I've put a feature request in to Google to allow some control of when it triggers.
Can you star the issue here*
https://code.google.com/p/android/issues/detail?id=191786
Click to expand...
Click to collapse
Thanks for the explanation. Hopefully u guys find a workaround
I also have had probles with the ambient display turning on seeminly randomly all the time, I didn't know it was light flow..
On another note, I miss the feature were my screen would turn on when I get a text messge (but not dismiss the lightflow) so in case the LED wasn't attention grabbing enough the screen turning on would be. Nexus doesn't seem to do that, can lightflow do this? (turn on the screen for 2-3 seconds right after a new specific notification, say text message?)
andrewpmoore said:
At the moment the only option is to switch off the ambient display. If there's an outstanding notification or one is getting updated it'll trigger ambient display and lightflow always has an active outstanding notification.
I've put a feature request in to Google to allow some control of when it triggers.
Can you star the issue here*
https://code.google.com/p/android/issues/detail?id=191786
Click to expand...
Click to collapse
Out of curiosity is building the app with the new api's what triggers the need for the notification? Reason I ask is the previous (lollipop api???) version was working fine without the persistent notification on Marshmallow.
AndrasLOHF said:
Out of curiosity is building the app with the new api's what triggers the need for the notification? Reason I ask is the previous (lollipop api???) version was working fine without the persistent notification on Marshmallow.
Click to expand...
Click to collapse
Yes that's exactly it.
I'm bringing out a new play store version later today which will be targeting lollipop's API for people who don't mind loosing android 6 specific features (ie runtime permissions, camera flash control) but don't want the notification related issues of apps targeting android 6.
a fine trade off for me. Had to stop using the app because of that for the time being.
Absolutely fine with me as well. Thanks for the great work as always Andrew.:good::highfive:
Coming from a Droid Turbo, Moto's AOD was awesome. Always showed me the time and icons for any notifications - if I wanted more info, I tapthe notification and get a peek (still on AOD) at the info, then could open my phone directly to that app by dragging up.
In contrast, I find Samsung's AOD fairly useless - even the time is often NOT on or bright enough when I really need it. And if you choose the AOD with notifications, they only work for a couple of stock Samsung apps if you happen to use those apps.
Has Samsung opened up the AOD API to third parties to create their own AOD apps? If so, anybody know of any good ones? Or perhaps turn Samsung AOD off and a third party Android app can emulate it? Right now, as is, the Samsung one seems pretty useless to me. And the 3rd party themes they offer for AOD don't change or add to the functionality - just allow optional looks of the same basic function.
Check out these:
https://play.google.com/store/apps/details?id=com.greatbytes.activenotifications&hl=en
https://play.google.com/store/apps/details?id=com.achep.acdisplay&hl=en
https://play.google.com/store/apps/details?id=com.anandbibek.notifyfree&hl=en
The last one seems to me to be the most effective.
Edit: You'll want to turn AOD off to use these.
The stock Samsung AOD enables some more optimizations for the display controller, including reducing the number of colours and the refresh rate.
How do I know whether those apps do the same? Is it known how to access the display controller this way, is there an API for that? How could I write an app that uses this?
hollywoodfrodo said:
Coming from a Droid Turbo, Moto's AOD was awesome.
Click to expand...
Click to collapse
My previous device was a Moto X and like you I miss some Moto AOD features too.
Anyway, there are ways to tweak a bit Samsung AOD , check this thread: Mod for Always ON Display to Double tap to Unlock possible?? (Nougat)
Hey XDA,
Does anyone know if it's possible to enable the android ambient display on a rooted style (I much prefer it to Moto's Active Display). I've been trying to get it working for a few days now. I disabled the moto display task, and can select ambient display in settings, but no go. I've installed the Ambient Display xposed module, and have all the options, but still doesn't turn on when I get a notification or when I reach for it.
I've also tried setting up a tasker profile to make use of the sensors, but can't figure out how to switch on Ambient display, not the entire screen.
Any ideas?
Yes, running into the same issue with stock OTA 7.0 and ambient display on XT1575.
Was anyone ever able to get stock ambient display (not Moto Active Display) working?
No... As most developers of ROMs for this device who have ever tried to get Moto Display working on a custom ROM will tell you, Ambient Display and Moto Display cannot co-exist in the same device. If Moto Display is installed (as in on stock), then Moto removed or otherwise permanently the default Android Ambient Display functionality, likewise if Ambient Display is working, Moto Display cannot even be installed, because of how this works it likely has hooks into the kernel as well.
TLDR answer... If you want Ambient Display go to a custom ROM, otherwise live with Moto Display if you want to stay stock.
acejavelin said:
No... As most developers of ROMs for this device who have ever tried to get Moto Display working on a custom ROM will tell you, Ambient Display and Moto Display cannot co-exist in the same device..
Click to expand...
Click to collapse
Nope, the truth is that lenevo intentionally removed some ambient display code from 7.0 for some unknown reasons. On previous 6.0 android you could enable it just by disabling moto display app in the settings.
iks8 said:
Nope, the truth is that lenevo intentionally removed some ambient display code from 7.0 for some unknown reasons. On previous 6.0 android you could enable it just by disabling moto display app in the settings.
Click to expand...
Click to collapse
Hmm... Then why can't we add Moto Display to a third party ROM? (I only refer to Nougat, Marshmallow is legacy in my book)