I have replaced my panel with an aftermarket ips lcd (not amoled). While the display is perfectly acceptable oxygen os doesnt seem to be able to handle the brightness on the new replacement screen. It often freezes on a setting if i keep it at that particular brightness level for too long and requires a reboot to start working again.
These issues don't happen with Lineage, and while i could run lineage, i would like to run oxygen as i like it.
What is it about the brightness settings that lineage does differently from oxygen, and can that be somehow patched back into oxygen?
It's baked on the op system i dont think there is a way... Custom rom is the only way
Related
I've looked at past threads, but found no resolution to this.
I'm running voodoo colour with deep black settings and everything looks great, except right before the screen times out it will dim to its lowest setting and force the amoled panel to turn a sickly yellow/green hue.
I would like to disable the dim aspect and just let the screen time out by shutting off completely. Is there anyway to do this? I'm running the latest version of Pixel Rom with Air Kernel 4.2. I don't have auto-brightness enabled.
i am having the same issu i dont have to yellow tint in low light
but still i whould like to disable the dim it is disturbing my daily use of the device
i too dont see any point for this time out before the screen turns of
and i cant understand why when plying a game i need to touch the screen every 25 sec to get rid of the dim
thanks
I remember seeing something about auto-brightness light sensor tweaking back when I was using NV rom last year but I don't know if that would apply or not.
Does anyone know if the custom apps on the market avoid this?
edit: Tried Tasker for a full screen-off solution, and a bunch of other apps. Wasn't able to get the results I wanted :I
I have a Samsung Captivate and I am running a kernel with voodoo color support with this same issue.
The first post of this thread shows a possible solution - http://forum.xda-developers.com/showthread.php?t=1002090
I flashed the pixel os android 10 in my redmi note 7 and now i am facing screen lock issue my phone does not accept any screen lock that i am trying to apply on it plzz help me
Hi
I recently upgrade my SAGA from CM 7.1 to 7.2, it seems CM team did a great work, less defect, smooth animation and so on. If the Auto Brightness can be as good as which on 7.1, it will be a perfect Rom.
Basically, I use the default setting, except enabled "Allow light decrease" on both version, I found on 7.1, if you move phone from a bright place to a darker place, the screen will get darker gradually, even just from one level to another, it doesn't make you feel flicker. However, on 7.2, it just change the backlight from one level to anther without any transition. I even tried the latest night version built on July 29, same reaction.
Does anyone have the same problem and know why?
Thanks.
As the title says, which one do you guys think is better? For example battery life, features, etc. I tinkered with Havoc OS the other day, but after realising half the custom Havoc settings that were in 2.9 like custom doze were not present, I reflashed 2.9. I was expecting all that was in 2.9 plus more.
Now that OOS 10.0.1 has dropped, I wanted to see what that was like, but didn't want to flash, be disappointed and then have to reflash Havoc and set up each app all over again. I've had issues restoring stable TWRP backups, so I have given up and just start from scratch each time I reflash.
What features from each stand out to you and what SOT and standby drain %/h are you getting from both?
havoc 3.0 is better because new maintainer is skulshady he trying best to provides new updates in every 1/2 week there are some less tweak for now but getting added in new updates you can wait till the base os changes to oos 10 (dont know when)
if you dont want to install app from scratch try migrate app by baltiapps
i didnt check sot & idle drain so i cant say anything about it
siddhrsh said:
havoc 3.0 is better because new maintainer is skulshady he trying best to provides new updates in every 1/2 week there are some less tweak for now but getting added in new updates you can wait till the base os changes to oos 10 (dont know when)
if you dont want to install app from scratch try migrate app by baltiapps
i didnt check sot & idle drain so i cant say anything about it
Click to expand...
Click to collapse
How do you install it? I tried and it borked my phone.
Try to install 3.1 latest on 20-01-2020. Seems to be fine Rom. But OTG provision is not seen.
Does havoc os have working, smooth OOS gestures? Only thing stopping me from changing in the past was bad gestures. Main issues for me on 10.3.0 are Bluetooth connectivity, internet disconnects, and poor battery life.
rickesh1 said:
Does havoc os have working, smooth OOS gestures? Only thing stopping me from changing in the past was bad gestures. Main issues for me on 10.3.0 are Bluetooth connectivity, internet disconnects, and poor battery life.
Click to expand...
Click to collapse
No oos gesture yet but full screen gestures are there currently some minor bug otg doesn't work & display profile changes after every reboot
battery working great but deep sleep is 0% switching to other kernel like blu spark fix this
Just had to switch to OOS 10.3.0 from Havoc OS due to freezing/crashing with Android Auto. Tried all the fixes on the internet, but no luck. Was going to go back to 9.0.6, but decided to try stock and it has been working fine. Too bad, as I really like Havoc with some of the AOSP touches, and the capability to separately adjust notification sounds. Can't understand why OnePlus can't add this feature.
wrench588 said:
Just had to switch to OOS 10.3.0 from Havoc OS due to freezing/crashing with Android Auto. Tried all the fixes on the internet, but no luck. Was going to go back to 9.0.6, but decided to try stock and it has been working fine. Too bad, as I really like Havoc with some of the AOSP touches, and the capability to separately adjust notification sounds. Can't understand why OnePlus can't add this feature.
Click to expand...
Click to collapse
To be honest, other ROMs do have these options, you could try something else
Hello,
I've been using LineageOS 18.1 on my OP7 Pro for about 2 weeks, and I would like to share some of my issues with it and hope an educated person can send me in the right direction.
Issues I have with LOS so far:
1. Random crashes where my phone will reboot, probably once every day/every other day
2. Physical notification slider doesn't mute media volume when set to silent
3. Battery life seems worse than stock OOS on A11
4. Forced 90Hz refresh rate instead of stock adaptive potentially meaning worse battery
5. Vibration intensity way too strong and no option to change it
Probably forgetting some others but that's the gist of it. Ifbyou think there's a ROM for me including stock then please lmk. I briefly used HavocOS but it felt too Google-ly to me. Still open to try it if y'all recommend it though. Thanks
My concern is adaptive brightness not working on GSI ROM (not even one)
I have LineageOS 19.1 and adaptive brightness ain't working (had Pixel Experience and AOSP, but doesn't work either).
I have also tried "force alternative backlight scale" - that only enables brightness to be changed
I have read and found the one way about overlays' /vendor/overlay stuff, but overlay is already there, folder permissions are 755 and APK permissions are 644. And mo matter how much reboots or termux commands still nothing... Also found treble-overlay-samsung-galaxy-a53.apk in root files but that one also doesn't seem to solve the problem.
Night Light works perfectly, still don't get why adaptive ain't working.
I've seen people on GSI roms on this forum, so help would mean a lot.
Same problem here. I heard that overlay require root so I didn't try it since I dont want to root my device.
Any help would be appreciated
If its the same as my other Samsung phone and if I remember correctly then its due to the adaptive brightness being custom implemented for Samsung's official rom that isn't compatible with unofficial roms. Something like that.
Either way, its just how it seems to be with custom roms. You can set low brightness if you want it and less battery usage and if low brightness is offered.
Since I'm not working on the rom, I could be wrong for this phone. But, since you bring up its not working here, it seems like its probably it.