Related
I don't whether i'm hallucinating or what, but i noticed that when i change the autobrightness levels in ViperX ROM/Faux 10u, the levels are not consistent.
for example i turn on the screen(in the dark) and the brightness should be at its lowest (20) then when I turn the brightness manually to lowest it gets a little darker.
I think my default brightness are overriding the custom levels whenever i turn off the screen, Can anyone with similar ROM/Kernel confirm this ? or someone noticed this on any other ROM ? (check my signature for more details about my Phone)
CM brightness control doesn't work!
Hi,
First of all i would like to thank the developers of Android Viper X for creating the best Android OS in history It's amazing!! :good: I’am using this OS now for 1 week, and I’am stunned by the amazing performance!! The only problem i have is that my CM brightness control function does not work anymore after upgrading from OS: 2.7.1 to >>>>>,>> 3.2.3. So i hope someone can tell me what causes this problem.
Cyanogenmod has a feature called LiveDisplay which automatically adjusts LCD color temperature according to time of day. Has anyone gotten this to work on the builds provided by Transi1? I'm in love with this old tablet after installing crdroid and am interested in figuring out how to get live display or color calibration working. I get some flickering and temporary display corruption when i try to adjust color calibration in the same display menu as LiveDisplay.
It Iooks like support may have been added in a pacman ROM a few years back, I wonder if that change was ever incorporated into Transi1's builds
cyobane said:
Cyanogenmod has a feature called LiveDisplay which automatically adjusts LCD color temperature according to time of day. Has anyone gotten this to work on the builds provided by Transi1? I'm in love with this old tablet after installing crdroid and am interested in figuring out how to get live display or color calibration working. I get some flickering and temporary display corruption when i try to adjust color calibration in the same display menu as LiveDisplay.
It Iooks like support may have been added in a pacman ROM a few years back, I wonder if that change was ever incorporated into Transi1's builds
Click to expand...
Click to collapse
In my experience, do not use this feature on the Kindle 8.9. If I would make a guess, I'd say the tablet doesn't support this feature and on any of the 4 or 5 ROMs I have tried, will either severely pixilate the screen, or throw the tablet into reboot. I was having a lot of trouble figuring out what was causing the issues until I turned the options off. I only figured it out because after the event happened, usually on first boot of the newly installed ROM, a notice would appear in status bar asking if I want to configure LiveDisplay. This option could very well damage the device if enabled.
cyobane said:
Cyanogenmod has a feature called LiveDisplay which automatically adjusts LCD color temperature according to time of day. Has anyone gotten this to work on the builds provided by Transi1? I'm in love with this old tablet after installing crdroid and am interested in figuring out how to get live display or color calibration working. I get some flickering and temporary display corruption when i try to adjust color calibration in the same display menu as LiveDisplay.
It Iooks like support may have been added in a pacman ROM a few years back, I wonder if that change was ever incorporated into Transi1's builds
Click to expand...
Click to collapse
I have done some experimenting with this feature. The 8.9 doesn't have the ability to adapt the display. So turn that off. Set the live display mode to 'night only'. Surprisingly this works pretty well.
DragonFire1024 said:
I have done some experimenting with this feature. The 8.9 doesn't have the ability to adapt the display. So turn that off. Set the live display mode to 'night only'. Surprisingly this works pretty well.
Click to expand...
Click to collapse
Interesting, I wish it worked for me, all I get is some flickering garbage on screen when i set to 'night only'. Are you also using transi1's latest crdroid build from December? Maybe there's another setting I have that is interfering
cyobane said:
Interesting, I wish it worked for me, all I get is some flickering garbage on screen when i set to 'night only'. Are you also using transi1's latest crdroid build from December? Maybe there's another setting I have that is interfering
Click to expand...
Click to collapse
Temaseks build. CM 13.
Sent from my Samsung Galaxy S7 using XDA Labs
Title says it all. I have been on Oreo for a month, and the lack of a useful ambient display is just such a fail I am actually considering rolling back to an older os version.
I wish not and to remain on Oreo, but do you know of any rom or hack to bring back Nougat ambient display? I was a daily user of "wave to trigger ambient display". New options dont work for me. ("pick up to trigger useless ambient display")
Many thanks,
Didier
I'm not sure what exactly is wrong with Oreo's ambient display, as I'm mostly still on Lineage 14.1 as my daily driver. However, if it's just the wave gesture: For a few days I tried DirtyUnicorns 12 release candidate and it definitely had the "wave to display" feature working. But note that this rom is still in RC and has not yet reached stable status.
I'm using the latest version of omnirom, which has the wave gesture available. You can also interact with notifications while still in ambient mode, which is really nice.
Naudiz said:
I'm not sure what exactly is wrong with Oreo's ambient display, as I'm mostly still on Lineage 14.1 as my daily driver. However, if it's just the wave gesture: For a few days I tried DirtyUnicorns 12 release candidate and it definitely had the "wave to display" feature working. But note that this rom is still in RC and has not yet reached stable status.
Click to expand...
Click to collapse
I tried Oreo for OOS and AOSP - basically the ambient screen does not display notifications anymore, just icons - so you cannot see what these are (as opposed to Nougat Ambient display, which shows full notifications, like email title, etc.). The notification displays only when you receive it - and when you do, you cannot interact with it. You have first to get out of the Ambient display and fully wake the screen. Maybe I'll keep an eye on the rom see if they follow Google's new design or go their own way.
lobotomize said:
I'm using the latest version of omnirom, which has the wave gesture available. You can also interact with notifications while still in ambient mode, which is really nice.
Click to expand...
Click to collapse
I Tried Omni with Oreo, and was not able to get the old ambient display, although the wave gesture was working... Maybe will give it another try, thanks
I upgraded to Android Q DP1 yesterday through OTA and noticed the double-tap-to-check-phone feature now always displays the full lockscreen including wallpaper. Same thing for lift-to-check-phone. In Pie, it used to show ambient display first when double tapped. I have the Always On Display disabled. Is this a bug?
Settings
Display
Advanced
Lock screen display
It's there
Mr Patchy Patch said:
Settings
Display
Advanced
Lock screen display
It's there
Click to expand...
Click to collapse
Yes, the "Double-tap to check phone" and "Lift to check phone" options are still there, and when enabled those actions still wake the screen, but the wake behaviour has changed, which is what I'm wondering about. When woken, it now shows the full lock screen rather than the ambient display (black background and dark theme) that used to show up in Pie.
Shimakaze said:
Yes, the "Double-tap to check phone" and "Lift to check phone" options are still there, and when enabled those actions still wake the screen, but the wake behaviour has changed, which is what I'm wondering about. When woken, it now shows the full lock screen rather than the ambient display (black background and dark theme) that used to show up in Pie.
Click to expand...
Click to collapse
Ohhh...ok I know what you mean now. Personally, I like it the way it is now in Q.
Mr Patchy Patch said:
Ohhh...ok I know what you mean now. Personally, I like it the way it is now in Q.
Click to expand...
Click to collapse
It's down to personal preference for sure. I wish they would've made that wake behaviour configurable if it's not a bug.
I wish the same too even in full 10 release they didn't change this behaviour
It's better to wake the ambient display than to wale the whole phone in case you need to check nots.
:good:
Hey all!
I am glad too see somebody else also noticed it. I absolutely adore the clean design and funcionality of Pixel's AOD, but the changed funcionality of double-tap to wake (from waking AOD to waking the whole screen) annoys me. I even rolled back from Q beta to Pie hoping they would not implement this change in stable release. Now in order to see AOD you need to have it on constantly, which actually drains some 1% battery per hour (that actually makes it some 15-20 over a working day's period and is actually quite substantial.), also during the night. I also don't stare at the phone all the time to need AOD all that time - a gentle tap to peek the time, weather and notifications is just enough - I see some of you would agree.
Is there any way we can appeal to Google similar to OnePlus's feedback section?
Hey, has it also become iOS like?
I hate whole iOS lock screen turning on. What a shame
I spent time factory resetting my phone thinking that the missing ambient display settings were a bug, I never thought Google would remove that functionality. The language under the "Lock Screen Settings" sounds similar, but they don't do the same thing since now it just wakes the entire screen. Real bummer that Google keeps removing features.
Yeah, it seem they went almost full iOS on this And it was so good: tap twice - AOD shows, tap twice again on that AOD - the lock screen shows. Why Google, why! At least give us an option to schedule when the AOD can be turned off automatically (like at some hours at night).
And to think I bought the Pixel just a week ago to finally taste the stock Android. It is good, no doubt here (and the phone size and general style is very refreshing from thos behemoths I used from Sammy, OP or Huawei), but OnePlus seems much more thoughtful and practicality-oriented. And what is the more important the pledges from the OnePlus community actually work quite often which I don't expect with Google somehow.
I'm fine with it. Not a big deal.
Sent from my Pixel 2 XL using Tapatalk
Always On Display Enabler
Here's a Substratum overlay I made that enables AOD on Stock Android 10, along with Burn-In protection and AOD Wallpapers.
I created this as I wasn't happy with the one available in the PlayStore as it also modifies system theme colors and that wasn't a desired feature.
Compatible with Substratum Lite.
Tested working on Pixel XL.
Features:
- AOD Wallpapers: seems to not be working
- Burn-In protection: seems to be working ok.
- Doze: seems to not be working (Device does not enter DeepSleep).
Version: 1.2
DOWNLOAD
Source code: https://github.com/blckbearx/AOD-Enabler
AhReLocazo said:
Always On Display Enabler
Here's a Substratum overlay I made that enables AOD on Stock Android 10, along with Burn-In protection and AOD Wallpapers.
I created this as I wasn't happy with the one available in the PlayStore as it also modifies system theme colors and that wasn't a desired feature.
Compatible with Substratum Lite.
Tested working on Pixel XL.
Version: 1.2
DOWNLOAD
Source code: https://github.com/blckbearx/AOD-Enabler
Click to expand...
Click to collapse
Tested and it seems to be working.
Questions :
1. IIRC the Pixel LWP had notification animations right ? It seems these aren't working. Also the LWP specific AOD images vanish after a while.
2. Does this prevent deep sleep ?
daedric said:
Tested and it seems to be working.
Questions :
1. IIRC the Pixel LWP had notification animations right ? It seems these aren't working. Also the LWP specific AOD images vanish after a while.
2. Does this prevent deep sleep ?
Click to expand...
Click to collapse
I couldn't get AOD wallpapers to show, they're enabled by the overlay but they don't seem to show, I couldn't get any wallpapers package to work with this feature.
Regarding deep sleep, this should be working, I've never noticed any background battery drainage while using AOD.
@daedric So after a bit of testing I got the animation to work, what I did was disable every Magisk module that I had (except for Substratum's module) and rebooted, then animations started working.
Edit: this may also be a way to use the Magisk module instead of Substratum. I'll try this and report back
Works on Pixel with LOS 17.1 and substratum lite. Thanks!
Animation works too I think. There's a smooth transition and screen doesn't flash at all. Have quickswitch, modprops, and fontchanger too and it's all working together.
Edited my post as I was thinking about the older substratum overlay. Sorry! I'm going to try this one. If it nails deep sleep I'm gonna donate to you OP. I've been waiting for deep sleep with AOD for two years.
---------- Post added at 11:56 AM ---------- Previous post was at 11:08 AM ----------
Update: deep sleep doesn't work according to EX manager, everything else works great!
Flipz77 said:
Edited my post as I was thinking about the older substratum overlay. Sorry! I'm going to try this one. If it nails deep sleep I'm gonna donate to you OP. I've been waiting for deep sleep with AOD for two years.
---------- Post added at 11:56 AM ---------- Previous post was at 11:08 AM ----------
Update: deep sleep doesn't work according to EX manager, everything else works great!
Click to expand...
Click to collapse
Let me change some things and I'll upload another version for you to try
Edit: I think enabling deep sleep will break dt2w, we'll see that if the next version works
@Flipz77 try the attached APK and please test if Deep Sleep works. I compared with the Magisk module and I had a modification that it didn't have regarding Doze so I removed it. Now it's basically identical to the Magisk module except for the Burn-In protection and AOD Wallpapers lines.
Thanks, I really appreciate your dedication! I've been testing it but it looks like deep sleep still doesn't work, sadly
I made a version that only includes the Magisk module's settings and still Deep Sleep isnt working
I guess it has to do with using Substratum or that the device doesn't go into Doze with the screen on, even though I enabled a line that makes Doze independant of the screen's state.
I just wanted to say thanks. I'm using this with an essential ph1 and substratum lite
I've installed this on a LG V40 running RR 8.6.8 GSI. Here the AOD/ambient display didn't work too good out of the box, possibly because of missing overlays. With this overlay, i can at least get AOD active fulltime or have the device wake when picked up/tilted (albeit a bit wonky/insensitive).
Still, double tap to wake from a black screen does not work here (when the system is in doze), only triggers from sensors will wake the device to show ambient display. Most likely a vendor/hw overlay/kernel issue.
Doze/Deep sleep works as long as i don't enable full always-on display.
On full always-on, dt2w works, but the cpus won't go into deep-sleep.
And i haven't seen much of a movement for burn-in protection. If it's there, it's too small to effectively shift out a majority of the pixels in use.
I guess it depends on the device, I made the module based on what the Pixel XL lacks on stock ROM.
On the Pixel XL the DeepSleep issue is also present, I forgot to correct that on the OP, thanks for the reminder.
The burn-in protection I tested it and it seems to shift too little, pretty much unnoticeable so it may be kinda useless.
I guess most of this is related to what is already baked in the ROM.
Anyways, custom ROMs for ther Pixel XL that have AOD available still face this issues, son in the Pixel XL case it may be Device/Kernel related.
Hey! Thanks for making this, still works on Android 11 pixel experience GSI.