Hi guys, I'm currently on on the last Existent MM rom, and I find the led brightness too low for me, so that I can barely notice it when it is not night time.
I remember that on some KK roms or Aosp based roms the brightness was far more efficient.
Is it kernel related? Or is there a way to tweak some files to make it brighter?
Thanks
TheLonelyCyborg said:
Hi guys, I'm currently on on the last Existent MM rom, and I find the led brightness too low for me, so that I can barely notice it when it is not night time.
I remember that on some KK roms or Aosp based roms the brightness was far more efficient.
Is it kernel related? Or is there a way to tweak some files to make it brighter?
Thanks
Click to expand...
Click to collapse
IDK for me it is bright enough also am on latest existenz rom
Try cleaning the speaker grills
Related
I'm starting to see a correlation between absolute crap-for-crap batter life and having the ambient light detector enabled. I'll do a test tomorrow, but I'm pretty sure if I just left my screen on full brightness all day, that I wouldn't get as bad of battery life as I do with the ambient light detector turned on.
Is there a problem with the fascinate's polling period? or possibly how much power is being sent TO the sensor? This might explain the problems on hacked roms where people are noticing a buzzing/hissing noise coming from the phone right around the area of the ambient light sensor when in the middle of a call (and the screen is on).
Has anybody seen where in the code the ambient light sensor is handled? (is it in the kernel, or somewhere in the drivers?).
*EDIT*
Thanks for moving my post. I was pretty annoyed with myself for posting in the wrong section.
*edit* Now that the thread has been moved, This post could probably be deleted.
--------------
Well, since nobody has moved this to the other forum yet and it's received a few views, Has anybody else noticed this before?
My personal experience had been full brightness ate battery fast and low brightness was a combination of hard to read and similar drain to auto. Then again my phone has never hissed at me except for godawful noises using skype wifi sometimes, and I have never messed with brightness under froyo.
My only observation with froyo roms is that "stock" eb01 was awful but superclean and AOSP were pretty good, particularly under EB+ kernels.
Also, I lose more battery than I would like to from signal loss overnight, but turning off 3G seems to help with that.
Swyped grumpily from my advertised as "can be upgraded to Android 2.2" device.
i noticed that the automatic brightness setting is absolutely terrible at choosing the correct brightness.
the froyo roms added the ability to hold down on the status bar and move left and right to adjust the brightness, so i just use this to adjust it on the fly when necessary.
this doesn't really answer your question, but i figured i'd add my 2 cents
lane32x said:
This might explain the problems on hacked roms where people are noticing a buzzing/hissing noise coming from the phone right around the area of the ambient light sensor when in the middle of a call (and the screen is on).
Click to expand...
Click to collapse
The noise comes from having the key backlights on during a call.
If you are referring to the softkeys, there were some assumptions that this was the case, but I have tested this out and have heard the noise even when those lights were turned off.
Also, I ran my phone at about half brightness today all day. I've had it off the charger for 15 hours, made 3 hours worth of phone calls, and it's still at 41% battery life.
2 days ago when I just had my phone in the pocket, not doing anything and leaving the screen off (with auto brightness enabled) my battery was dropping significantly after only 6 hours and no phone calls or Internet usage.
Why is on every CM10 ROM i have tried screen so damn dark? On highest settings, it not even on half of brightness of stock ROM. And when its sun outside, black turns to purple so i have to lower brightness to half... Why is screen brightness so low on every CM10 and is there any fix for that...? And overall screen quality just seems low comparing to my old LG P500. And especialy that this phone should have bravia engine that makes its screen better than most other similar phones.
I am currently using ParanoidAndroid 2.37 http://forum.xda-developers.com/showthread.php?t=1963556 with Lupus kernel.
Also phone is LWW.
Echelonex said:
Why is on every CM10 ROM i have tried screen so damn dark? On highest settings, it not even on half of brightness of stock ROM. And when its sun outside, black turns to purple so i have to lower brightness to half... Why is screen brightness so low on every CM10 and is there any fix for that...? And overall screen quality just seems low comparing to my old LG P500. And especialy that this phone should have bravia engine that makes its screen better than most other similar phones.
I am currently using ParanoidAndroid 2.37 http://forum.xda-developers.com/showthread.php?t=1963556 with Lupus kernel.
Also phone is LWW.
Click to expand...
Click to collapse
Bravia Engine works properly only on stock based ROMs... we can get it via Pimp My ROM to work on CM but it doesn't make a difference...
And I don't know about PA... but the brightness in CM is much greater than stock ROM
This module aims to fix Nexus 5 ambient light sensor issues leading to random auto-brightness spikes under certain lighting.
The issue
Sometimes the light sensor goes crazy and reports 30000 lux even in a dim light because of what auto-brightness attempts to blind you in a moment. These random spikes happen when you hold a phone at certain angles and depend on light bulbs used in a room.
The solution
The fix is implemented as an Xposed module.
Basically, it is a filter inserted near a point where native HAL communicates to Android framework. It intercepts all sensor readings and replaces abnormal 30000 lux (and 0 lux following 30000) with an averaged value from a sliding window. This affects any process that use Android sensors API including system_process, so that default Android auto-brightness works fine too (no need to use apps like Lux Dash to workaround the issue).
Installation
Download and install Xposed framework
Then install Nexus 5 Light Sensor fix module and activate it
Reboot
Usage
The module provides no user interface, nor it runs any services in a background. It only injects a proxy method to the implementation of Android sensors API. You won't be able to notice it in the main menu or in a task manager. Think of it as a patch that can be turned on and off through Xposed installer.
Source
The mod is open source (with permissive MIT licence), the source code is available on my GitHub.
Thanks
@rovo89 for his Xposed framework
@n3ocort3x and @wantabe for the initial attention and for kicking me up to finally create a new thread
and you (the community) for your feedback
More on the issue
Two major issues with the Nexus 5 ambient light sensor (original module announcement)
Palmadores said:
1. The sensor reading often jumps to 30000lx momentarily, (measured using Lux Dash in Debug mode), and so the phone blinds you for while. This happens in a repeatable fashion when you hold the phone at certain angles. Try it yourself.
2. The N5 reads zero lux even in moderate/dim light, while my old N4 still reads around 10 lux.
Click to expand...
Click to collapse
exorz said:
Using the Lux app debug mode I rotated the phone while in a room lit with incandescent bulbs and one lit with daylight. When rotating the phone I sometimes see a spike of 30000 lx but more importantly the sensor drops to 0 even though there is plenty of ambient light. During daylight I don't see the 30000 lx spikes but I still see the sensor dropping to 0 when there's plenty of ambient light.
Click to expand...
Click to collapse
Is the Auto-Brightness Functionality wonky on the Nexus5?
Aria807 said:
I think it may be bugged with Halogen lighting (correct me if I'm wrong). My home is ~ 18 years old, and we have some bulbs that have not been changed yet (yellow). Sometimes when I use my N5 under those lighting, the sensors go whack and don't register properly picking up 0lx, then spike up to 30000lx. Once I move to areas in the house with newer bulbs, the sensors work normal, picking up the right readings.
Click to expand...
Click to collapse
Well done! Auto-brightness accuracy is much improved indoors! Appreciate your work on this!
Do I need to disable the modules if I dirty flash a new Carbon nightly? Or is that not necessary
augoza said:
Do I need to disable the modules if I dirty flash a new Carbon nightly? Or is that not necessary
Click to expand...
Click to collapse
I'm not sure, cause I use stock ROM, but I guess there is no need to disable it. As I can see from Carbon sources, related parts of code was not modified at all. To be sure, please ask ROM developers or other Xposed guys.
1.1 update won't install on nexus 5 signature mismatch
Sent from my Nexus 5 using Tapatalk
ddloco said:
1.1 update won't install on nexus 5 signature mismatch
Click to expand...
Click to collapse
I know, this is my fault and this is actually stated in the module description. Please remove version 1.0 and install 1.1 from scratch.
Still coming up very bright compared to Lux. Battery drain WILL be an issue.
mcnob said:
Still coming up very bright compared to Lux. Battery drain WILL be an issue.
Click to expand...
Click to collapse
The mod only removes random spikes reported by sensors. It does not affect an algo used by stock auto-brightness (any auto-broghtness is basically a function that maps a given input value from the sensors to the screen brightness; the mod just removes some trash from the input).
AFAIK the stock auto-brightness is configured through framework-res (google: config_autoBrightnessLcdBacklightValues, e.g. http://forum.xda-developers.com/showthread.php?t=2616914). Probably there is some app/mod for tweaking these options.
Wonder if custom ROMs like Omni and CM already have the fix baked in?
Anyone tries this on something other than an N5?
Motorola perhaps?
Sent from my DROID RAZR M using Tapatalk
FirePsych said:
Anyone tries this on something other than an N5?
Motorola perhaps?
Click to expand...
Click to collapse
I'm pretty sure this wouldn't make any sense, at least with current implementation, which compares each input value against hardcoded 30000 lux.
bland.life said:
Wonder if custom ROMs like Omni and CM already have the fix baked in?
Click to expand...
Click to collapse
The problem is that a code to be patched is located in a device-independent part of Android, but only Nexus 5 build should be modified. However, I didn't research well whether there is a way to build some piece of base framework only for a particular device. Probably Omni/CM guys know better.
mcnob said:
Still coming up very bright compared to Lux. Battery drain WILL be an issue.
Click to expand...
Click to collapse
Must be a variance between different devices because on my N5 auto-brightness indoors at night looks just a little on the dim side. In brighter light it looks good to me but I can't tell you what percentages it's using. I would probably like it 2 or 3 percentage points higher indoors but I'm fine with the way it is now. At least on my device I haven't seen any noticeable effect on battery life with auto-brightness on most of the time. Still getting 5-9 hrs of screen on time with my use. I made a comment in a previous post about auto-brightness being more accurate, I was referring to the way it would constantly adjust the brightness level and the changes would be big ones. Personally I think auto-brightness is much better with the module installed and in my case useable now. No, it's not as accurate as the auto-brightness is on my One X, which is amazingly accurate, for that kind of accuracy I would use something like Lux, maybe in conjunction with the module. I would give it a shot myself but I've purchased enough apps to modify the display brightness as it is. Running stock 4.4.2.
Edit:
Forgot to mention I'm using the dimmer backlight setting in the config file for the ElementalX kernel. I don't think that makes much of a difference in accuracy, if any, just how dark the display can potentially go. I also completely forgot that the dimmer backlight and auto-brightness levels are options available in the GravityBox module. As effing long as I've used GB I've never used those two options!
abusalimov said:
I'm pretty sure this wouldn't make any sense, at least with current implementation, which compares each input value against hardcoded 30000 lux.
Click to expand...
Click to collapse
Yup. Didn't work on my Razr M.
Sent from my DROID RAZR M using Tapatalk
I don't know what the issue is lol, but I have Franco kernel so I assume I'm immune to this right?
Sent from my Nexus 5 using Tapatalk
Deeco7 said:
I don't know what the issue is lol, but I have Franco kernel so I assume I'm immune to this right?
Click to expand...
Click to collapse
It doesn't matter, which kernel do you run, ALS is a user space driver. BTW I use franco kernel too.
10000 lux
My N5 reports 10000 lux instead of 30000, very annoying
Running CM11.0 m5
zbloh said:
My N5 reports 10000 lux instead of 30000, very annoying
Running CM11.0 m5
Click to expand...
Click to collapse
Thanks for reporting. Is it reproduced on CM11.0 M5 only, did you try other ROMs? Does it show exactly 10000.0 lux? If so, I could catch this value as well.
New version 1.2 is available now:
- Always replace 0 lux with 1 lux to prevent auto-brightness changing hither and thither in a very low light environment
- Do not feed replaced values back to EMA filter (makes it more responsive to newly coming proper readings)
- Filter out 10000 lux as well (reported by zbloh)
Hi guys hope someone can help. This is the first time I've rooted and flashed a custom ROM bootloader is unlocked and I'm running CyanogenMod 12-20150201 nightly all seems well except a few issues and as I'm new to this I'm not exactly sure what to do the Led light is extremely dim and I've noticed incredible battery drain are these issues just me or is it the nightly ROM cheers
Anyone else having problems with automatic brightness changes?
Every evening when it gets dark the brightness level goes to the lowest level, which is much to dark to read anything. Every evening I have to adjust the ''automatic'' level to halfway the level-slider, multiple times.
Do you have night mode enabled ?
I have this feature enabled from 9pm to 7am and indeed the auto brightness goes lower than normal value during this time slot .
Pouic said:
Do you have night mode enabled ?
I have this feature enabled from 9pm to 7am and indeed the auto brightness goes lower than normal value during this time slot .
Click to expand...
Click to collapse
No eye comfort modus
No Adaptive sleep modus
Only 'dark modus' enabled day and night
The same is happening to me. The brightness of the screen in darker lights is too low. Every time I move the slider to upper brightness but next time I open the screen is lower again.
marselcj said:
The same is happening to me. The brightness of the screen in darker lights is too low. Every time I move the slider to upper brightness but next time I open the screen is lower again.
Click to expand...
Click to collapse
I tried to wipe the system settings but the problem persists. I hope they can fix this in an update
BartKey said:
I tried to wipe the system settings but the problem persists. I hope they can fix this in an update
Click to expand...
Click to collapse
I might state the obvious, but the sensor is a bit high up on the device and it might be covered by your phone case, u sure it's not just a goof with an off brand cover?
The sensor is not covered. I use an original OnePlus cover.
Strange thing ... Everybody or at least majority of Oneplus Nord 2 owners had complained about automatic brightness . It's true in my case as well but now problem is solved with a 3-d party apk . Velis Auto Brightness from G.Play . Calibrating autobrightness is very accurate but the app remain active in background all the time and I didn't know how this affect battery drain . I read all OnePlus latest phones have this annoying bug and it's pitty none of latest updates solved it , worst here on XDA or OnePlus forum no one offer any solutions to calibrate automatic brightness .
Some smart guys said there is not "automatic brightness" but "adaptive brightness" so we had to learn phone AI how to adjust brightness a few days and then restart the phone . This are childish thoughts of those which are nothing to do else .
So , what do you think about this ? There are solutions to calibrate or fix this issue ?
I noticed that when the phone is on below 15% or lower and the battery saver is on ( for me it's 10%) the phone brightness goes to automatic mode and it becomes even less bright. I think it has to be a certain feature which is connected to battery saving IMO.
I'm using Velis for 3 months as well. This solves the problem. But OnePlus definitely should solve this.
Even latest update v11.3 EU, doesn't solve it. I even did a factory reset. 3 hours work to reset everything back as is was, for nothing...
Look at a possible solution (for me didn't work) :
"
stevendumondCupcake
stevendumond , Sep 25, 2021 :
stevendumond said: ↑
FYI: I did this a few minutes ago. I think that may be it. Before I did this, the screen brightness did not work at all. I could slide that slider up and down and nothing ever changed on screen brightness, auto or manual. Now it works! On auto and manual!
Hopefully this is the "fix"! But disabling a feature is NOT a fix, it's a workaround. Luckily I don't need that feature
Click to expand...
Click to collapse
So far the screen brightness has not faded into darkness. Phone is working fine now. This is a workaround that works.
Settings> Battery> Battery Optimization> Advanced Optimization (3 dots in upper right)> Sleep Standby Optimization: OFF
Click to expand...
Click to collapse
Since A.14 OTA , Adaptive Brightness is better but not entirely satisfying . It seems they solve bugs by little steps ... which is quite annoying !
muppetz said:
Since A.14 OTA , Adaptive Brightness is better but not entirely satisfying . It seems they solve bugs by little steps ... which quite annoying !
Click to expand...
Click to collapse
Not better here with a.14. Same problem as before... Indeed very annoying
BartKey said:
Not better here with a.14. Same problem as before... Indeed very annoying
Click to expand...
Click to collapse
Minimum level (especially in low light) is a little bit higher , sensitivity is more accurate and transition between levels is also a little bit faster . I'm pretty sure there are some improvements , that's a fact not a feeling .
muppetz said:
Minimum level (especially in low light) is a little bit higher , sensitivity is more accurate and transition between levels is also a little bit faster . I'm pretty sure there are some improvements , that's a fact not a feeling .
Click to expand...
Click to collapse
Let's hope it improves a lot more. My previous devices, Moto g, Moto G5 plus, never had such problem, even on any custom ROM...
BartKey said:
Let's hope it improves a lot more. My previous devices, Moto g, Moto G5 plus, never had such problem, even on any custom ROM...
Click to expand...
Click to collapse
Oh , yes I still have Motorola One Vision and automatic brightness is flawless ...