Database Users

[Q] Do you use auto brightness or set value?

Just curious to see what everyone does on their tablet. I stick to using auto brightness but turn it up every once in awhile when browsing the web. The screen is just very nice to look at IMO. So what do you guys do? If you don't use auto brightness, specify your brightness sweet spot.

I have auto brightness off and set to the lowest possible setting and only occasionally adjust the brightness higher.

I also use the lowest possible setting. When I need to change the brightness, I use an app "Display brightness".

k1silver said:
I also use the lowest possible setting. When I need to change the brightness, I use an app "Display brightness".
Click to expand...
Click to collapse
+1
Auto brightness in 4.2 is one big bug

I would love to go back to using auto-brightness but it's a buggy piece of **** on 4.2+, it's been over a month now and they still haven't fixed the ****ing screen flicker issue, completely disgraceful.
http://code.google.com/p/android/issues/detail?id=39841

I use set values from Extended Controls widget. I have it to like 7%/25%/36%/64%/100% and switch manualy according to what I need. Auto brightness never worked good for me on ANY android device

k1silver said:
I use an app "Display brightness".
Click to expand...
Click to collapse
Thank you for turning me onto Display Brightness! Now I don't have to depend on auto-brightness and how it drains the battery! I'll be upgrading to the Pro version to support the developer!
BTW... I'm so glad it doesn't black out the screen completely, otherwise I would probably have a Razr with a completely black display (I was testing it on my Razr before I installed it on the N7).

Screen dims when it shouldn't

I have set my S4 up so that it runs at 100% display illumination when charging. No autobrightness.
What is bothering me know is that the screen dims to about 50% very quickly after I stop touching the display and jumps up to 100% while I touch it.
Toggling smart stay doesn't change anything. Smart stay on doesn't help even when I look at the display (though it should just prevent it from going off .. not from dimming if I understand correctly.
I would like to display to stay at 100% when charging .. or at least set dimming to "after 15 secs" or so.
What needs to be done?

daniello8 said:
I have set my S4 up so that it runs at 100% display illumination when charging. No autobrightness.
What is bothering me know is that the screen dims to about 50% very quickly after I stop touching the display and jumps up to 100% while I touch it.
Smart stay toggling smart stay doesn't change anything. Smart stay on doesn't help even when I look at the display (though it should just prevent it from going off .. not from dimming if I understand correctly.
I would like to display to stay at 100% when charging.
What needs to be done?
Click to expand...
Click to collapse
I was reading about that and i found something about the chipset SnapDragon has an inside feature to adjust the screen brightness independently of the software (firmware on this case). Maybe you are watching that effect..

tomboymad said:
I was reading about that and i found something about the chipset SnapDragon has an inside feature to adjust the screen brightness independently of the software (firmware on this case). Maybe you are watching that effect..
Click to expand...
Click to collapse
There is a small tool that fixes it: "Caffeine" .. obviously
Intelliscreen also does the trick .. and there is a timeout you can set (not sure if it messes up the timeout for regular use when not charging though).

daniello8 said:
There is a small tool that fixes it: "Caffeine" .. obviously
Intelliscreen also does the trick .. and there is a timeout you can set (not sure if it messes up the timeout for regular use when not charging though).
Click to expand...
Click to collapse
Is not the solution because caffeine prevents from time up screen brightness but it doesn't prevent from cpu feature. Even if the screen is always wake up and the autobrightness is off, the brightness will be changed because the chipset.

tomboymad said:
Is not the solution because caffeine prevents from time up screen brightness but it doesn't prevent from cpu feature. Even if the screen is always wake up and the autobrightness is off, the brightness will be changed because the chipset.
Click to expand...
Click to collapse
Well .. it works for me.

daniello8 said:
I have set my S4 up so that it runs at 100% display illumination when charging. No autobrightness.
What is bothering me know is that the screen dims to about 50% very quickly after I stop touching the display and jumps up to 100% while I touch it.
Toggling smart stay doesn't change anything. Smart stay on doesn't help even when I look at the display (though it should just prevent it from going off .. not from dimming if I understand correctly.
I would like to display to stay at 100% when charging .. or at least set dimming to "after 15 secs" or so.
What needs to be done?
Click to expand...
Click to collapse
Could this be related to heat? With the screen on and charging + what ever other task you have the S4 doing it may be the S600 is governing the screen to reduce heat... just a theory like.

I'm having the same problem too.
If i unlock the phone the screens dims to about minimum brightness.
I can touch the brightness bar to make it brighter and it stays that way for as long as i don't lock the phone
If i lock the phone and unlock it again the screen dims again?
Tried all different settings bur nothing helps...
Very annoying....

Yesterday i bought and installed lightflow to control my led indicator.
Just a minute ago i removed the app and voila! No more screen dimming!
Damn, really love that app but rather no led control than having my screen dimmed to the lowest possible brightness.

[APP] Lux plugin for Nexus 5 - testers needed

UPDATE: The official Lux plugin for Nexus 5 is out now. Please use the official plugin instead. You can get it here: https://play.google.com/store/apps/details?id=com.vitocassisi.lux.plugin.nexus5
So what does this plugin offer?
Higher quality astronomer/night modes and subzero adjustment
On screen buttons are adjusted
Screenshots are no longer discoloured
Improved contrast
No more screen overlay means slightly less cpu usage
Instructions & important information
This plug-in can only be used on rooted Nexus 5 devices using Lux Auto Brightness v1.3 or higher!
You must enable plug-in support under the Advanced section of Lux preferences for it to work.
Should you decide to uninstall the plugin, it's strongly recommended that you reboot your device.
Notes
Astronomer/night modes require kernel RGB display calibration support (Franco Kernel R37 and newer and maybe other kernels. Check with your kernel developer). I have only tested this on Franco Kernel R37. Backup your ROM before installing.
Download:
Removed. Please use official plugin.

Nice plugin, testing it now.

Testing now
Sent from my Nexus 5

I've just read in the Franco kernel thread where you mention your plug in and a comment about working around KitKat limitations. I'm curious what the limitations are so please elaborate.
Thanks
Sent from my Nexus 10 using XDA Premium HD app

When my screen is close to timing out at 30, screen dims until screen turns off (which is normal). But the screen stays dimmed even after I tapped it before the timeout. Have to pull down notifications and either add or minus brightness to lux for it to go back to its supposed brightness.
Edit: not sure what happened, but its working normally now
Sent from my Nexus 5 using Tapatalk

My screen keeps flashing like the brightness goes to max for a split second then back down to where it should be. Weird. Running on Franco's r37
Sent from my Nexus 5 using Tapatalk
Edit: it seems to be connectet to screen dimming before it automatically turns off. If I interact with the screen during this time period the backlight turns on and stays on and I have to manually turn brightness down.

Jermehh said:
My screen keeps flashing like the brightness goes to max for a split second then back down to where it should be. Weird. Running on Franco's r37
Sent from my Nexus 5 using Tapatalk
Edit: it seems to be connectet to screen dimming before it automatically turns off. If I interact with the screen during this time period the backlight turns on and stays on and I have to manually turn brightness down.
Click to expand...
Click to collapse
Mine was completely the opposite but it's still tied to the screen dimmer. I'm sure this problem is fixable with a line of code.
Sent from my Nexus 5 using Tapatalk

DroneDoom said:
When my screen is close to timing out at 30, screen dims until screen turns off (which is normal). But the screen stays dimmed even after I tapped it before the timeout. Have to pull down notifications and either add or minus brightness to lux for it to go back to its supposed brightness.
Edit: not sure what happened, but its working normally now
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Same thing, fixed after a reboot.
However my night profile doesn't seem to work. It doesn't go to a sub-zero value.

I'm on r38. The color balance is a little different from before the plug in, probably due to switching to rgb. The colors seem cooler.
I too also have my screen turn suddenly bright when the phone does the auto brightness reduction when it is about to time out. Maybe that's a Franco kernel thing. I would love to use this plugin with r36 because I had much better battery life with that kernel compared to r37 or 38, but I guess the plugin doesn't work with the kernels that don't support rgb. I haven't tried it yet though.
Lux also has to often times before manually reset to adjust the brightness even if I have it set to auto and dynamic. In other words, I'll have to go to the notification panel and either hit the refresh button, or click on the percentage and once the pop up window appears on screen, the light sensor picks up the ambient light and adjusts as usual. maybe this is a sensitivity thing? maybe it wont trigger the change unless there has been a large enough change in lumens?
I have a tasker profile that turns off lux temporarily and sets brightness to 100% when using camera and gallery, and turns lux back on when closing the app. This is a little buggy with the n5 plugin installed I have seen. The phone sometimes can't decide to stay at full brightness or go back to almost illegible screen when the cam app is open. It seems to falter back and forth for some reason?
Once I close camera, lux kicks back in and it usually works at adjusting the brightness to respectable levels, but I wonder if that wonkiness inbetween is lux, or the kernel I'm using?
Sent from my Nexus 5 using xda app-developers app

anmar21 said:
Same thing, fixed after a reboot.
However my night profile doesn't seem to work. It doesn't go to a sub-zero value.
Click to expand...
Click to collapse
I think that's a bug of Lux. Basically when you tune your brightness to a sub-zero value lux adds a semi-transparent overlay to your screen to make it darker. However when Lux detects a plugin is installed, it removes the overlay and so sub-zero values won't work.
xybur said:
I'm on r38. The color balance is a little different from before the plug in, probably due to switching to rgb. The colors seem cooler.
I too also have my screen turn suddenly bright when the phone does the auto brightness reduction when it is about to time out. Maybe that's a Franco kernel thing. I would love to use this plugin with r36 because I had much better battery life with that kernel compared to r37 or 38, but I guess the plugin doesn't work with the kernels that don't support rgb. I haven't tried it yet though.
Lux also has to often times before manually reset to adjust the brightness even if I have it set to auto and dynamic. In other words, I'll have to go to the notification panel and either hit the refresh button, or click on the percentage and once the pop up window appears on screen, the light sensor picks up the ambient light and adjusts as usual. maybe this is a sensitivity thing? maybe it wont trigger the change unless there has been a large enough change in lumens?
I have a tasker profile that turns off lux temporarily and sets brightness to 100% when using camera and gallery, and turns lux back on when closing the app. This is a little buggy with the n5 plugin installed I have seen. The phone sometimes can't decide to stay at full brightness or go back to almost illegible screen when the cam app is open. It seems to falter back and forth for some reason?
Once I close camera, lux kicks back in and it usually works at adjusting the brightness to respectable levels, but I wonder if that wonkiness inbetween is lux, or the kernel I'm using?
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
I'm currently looking into this bug. It's caused by a work around to get the plugin to work with nexus 5. Otherwise your backlight stays on even after you turn your screen off, which is way worse than the fluctuation

anmar21 said:
However my night profile doesn't seem to work. It doesn't go to a sub-zero value.
Click to expand...
Click to collapse
I have this with the stock rom. No sub-zero values and no color temperature adjustment.

Awesome work! I wish I could help test but I'm stuck between a rock and a hard place in that I'm using the CM11 nightlies, which apparently don't work with the Franco kernel right now, but I really want the Lux root features! Anybody know if the CM kernel supports colour changes?
I think that's a bug of Lux. Basically when you tune your brightness to a sub-zero value lux adds a semi-transparent overlay to your screen to make it darker. However when Lux detects a plugin is installed, it removes the overlay and so sub-zero values won't work.
Click to expand...
Click to collapse
I'm not sure that is a bug of Lux. Up until a couple of days ago I was using a Galaxy Nexus with the Lux root plugin and that let me use sub-zero settings just fine.

The plug-in is in the playstore now. I use the carbon rom, with the kernel it comes with. Is 3.4.75-Slim4.4.2-kk-build4.1-beta a faux or Franco kernel?

augoza said:
The plug-in is in the playstore now. I use the carbon rom, with the kernel it comes with. Is 3.4.75-Slim4.4.2-kk-build4.1-beta a faux or Franco kernel?
Click to expand...
Click to collapse
Your question doesn't make sense. If you're asking what kernel to use try them both and see what you prefer.
Sent from my Nexus 5 using Tapatalk

Savant said:
Your question doesn't make sense. If you're asking what kernel to use try them both and see what you prefer.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Because I don't want to change my kernel. I want to stay stock carbon right now. Anyway I've just been using the new Nexus 5 light sensor fix module for xposed. Works great. You can use any kernel. Even stock N5 kernel
Edit: Actually the module is okay.

Please don't upload my apk's without permission. This plug-in was not written by the OP, it was written by myself. It might seem harmless, but you've diverted support from my official channels into here. That's not cool.

Cyb3rGlitch said:
Please don't upload my apk's without permission. This plug-in was not written by the OP, it was written by myself. It might seem harmless, but you've diverted support from my official channels into here. That's not cool.
Click to expand...
Click to collapse
Actually, I wrote this plugin using your source for Nexus 4 as a template. I decided to write it because at the time your plugin for Nexus 5 is not out yet. I can upload the source as proof if you want.
Either way I should probably link to your official plugin since it's out now

kevdliu said:
Actually, I wrote this plugin using your source for Nexus 4 as a template. I decided to write it because at the time your plugin for Nexus 5 is not out yet. I can upload the source as proof if you want.
Either way I should probably link to your official plugin since it's out now
Click to expand...
Click to collapse
Okay, well please don't use my market description and app icon, since it makes the distinction unclear. Thanks.

Ooops...
NEXUS 5

Screen flicker workaround

Hi everyone
I want to share a workaround to all of us who owns a defective S5
Symptom: You unlock your phone and it doesn't show anything. Actually, the phone is working. Capacitive buttons light up and you may heard some activity in the phone
Your phone has a defective screen. There are a lot S5 which have this problem, according to several forums. After several tries, unlock and lock over and over, the screen light up and you are able to use your phone. The problem is when you receive a call and you want to know who is calling you, the screen doesn't illuminate and you won’t be able to know who is.
Here's a workaround which makes your powerful S5 usable and take out from your drawer.
Solution:
The more effective way to fix it is: change defective screen! But sometimes it could cost as much as a new phone, or simply you can't afford it, and it's better to change your phone instead, and you put your S5 in a drawer.
The technical explanation of this problem is: Screen doesn't receive enough electrical current at low brightness levels (maybe the flex is defective, get old, etc)
Most probably the wake up problem exist together with screen flicker at low brightness levels
The wake up problem rises up more in dark environment, when light sensor make low bright screen
The lock screen light up screen, with a dim effect: when you lock the phone, it slowly turn screen off, and when you unlock, it make and effect of dim screen.
When you are is in dark environment, the effect is very slow, preventing the screen illuminate because the technical problem explained before.
When you are in very light environment, you lock screen and sensor light make the screen very brilliant and chances are you defective phone wakes up correctly.
We can use an app which give us complete control over brightness subsystem. I use an app called Velis AutoBrightness:
Once installed from Play Store, it shows a Setting Wizard. Follow the instructions. Below are some notes
• 1/7: Welcome Screen
• 2/7: How bright... Most probably is your phone always have flicker in low brightness. Choose "AMOLED" or "AMOLED bright". By the way choosing any one of those cure always minimum brightness failure!
• 3/7: Choose High sensitivity
• 4/7: On, if you want additional brightness when charging. Irrelevant for this thead. Choose your favorite setting
• 5/7: Same of 4/7
• 6/7: Choose enable: That enable the app
• 7/7: Some additional notes: Press Done
Now important settings: go to Menu > Settings > General: Settings Mode > Advanced
Service Activation settings:
• Disable system handler > ON: When you use Power saving mode, you surely noted screen flicker, which is very annoying, and make unusable power saving mode. By set this ON: Android doesn't set screen too dim; instead Velis have a minimum of brightness set by Wizard 2/7. (Surely you find out that you avoid screen flicker, by setting autobrightness off and slider in 8-10%)
Sensors settings:
• Screen-on sensor value override: Set this value to 30000. Read below this post if you want technical explanation of this setting
After you establish these settings, you'll be able to unlock your phone all the time!
This is the trick: When you unlock your phone, you'll note that the screen is very bright (because Screen-on to 30000) and quickly adjust to the environment light. The failure is that electrical current to screen is defective, and when exterior light is dark, the screen make a dim effect and doesn't light up.
Note to Marshmallow users:
• This app make use of Screen overlay permisions: And marshmallow is very restrict with this kind of app. This is specially true when you are installing an app. All you have to do is deactivate the app in notification screen: press "OFF" button, adjust system brightness upper enough to not flicker the screen, install your app, and activate Velis Autobrightness again
• Because of Doze mode, wake up from this mode may avoid your screen light up, the first time you use your phone. Let 10-15 seconds your phone wake up, lock again, and unlock again, and velis will make its work!
I hope this post make your smartphone usable. I barely apply this trick to two phones, but I think this is a good workaround!

I used this app & the flickering is still available

What worked for me is downgrading the firmware on my g900f all the way back to Android 4.0. My phone came with version 5.0 and I noticed the problem only after I kept installing samsung's system updates. Will report if the problem starts up again but I'm running rooted and running nougat just fine so I don't see a reason to keep upgrading the firmware.
Edit: nevermind, this didn't work

Reyse said:
The technical explanation of this problem is: Screen doesn't receive enough electrical current at low brightness levels (maybe the flex is defective, get old, etc)
Click to expand...
Click to collapse
Does anyone know for sure if it's the flex cable or some capacitors? I notice only the lower half of my screen flickers.. I bet there's a simple electrical fix for it instead of replacing the whoooole display

fbs said:
Does anyone know for sure if it's the flex cable or some capacitors? I notice only the lower half of my screen flickers.. I bet there's a simple electrical fix for it instead of replacing the whoooole display
Click to expand...
Click to collapse
Hello,
Have you change jour battery? If it s old it could cause some issues...
But try to buy a genuine one, I think that your battery must be old now.
Bye

cedouic said:
Hello,
Have you change jour battery? If it s old it could cause some issues...
But try to buy a genuine one, I think that your battery must be old now.
Bye
Click to expand...
Click to collapse
it doesn't make any sense. the lower half of the screen flickers in green even on charger

fbs said:
it doesn't make any sense. the lower half of the screen flickers in green even on charger
Click to expand...
Click to collapse
I noticed that screen only flickers at low brightness when using Boeffla kernel for LOS14 and others based on it.
No issue for the same device with LOS or Stock based kernels.

zlazaar said:
I noticed that screen only flickers at low brightness when using Boeffla kernel for LOS14 and others based on it.
No issue for the same device with LOS or Stock based kernels.
Click to expand...
Click to collapse
you're wrong
I was using los16 with stock kernel for months with flicker everyday

fbs said:
you're wrong
I was using los16 with stock kernel for months with flicker everyday
Click to expand...
Click to collapse
+1 to that , i even went back to stock and the screen flicker appeared and such issues are well known already with samsung amoled panels back in 2014-even some panels from 2018 . So def not kernel related.

I was using los 15.1 and this problem got worse. The phone was barely usable as mentioned by the op. In my case, the screen would start flickering below 60%. Then I switched back to stock marshmallow. I noticed that 100% brightness in los 15.1 is actually only about 70% in the stock rom.
I have been using the phone at 80% brightness for some weeks now and the problem has significantly reduced. But not completely gone, it's much much better. Also, you might want to avoid using dark wallpapers.

[Problem] Screen flashes bright on touch

Hello everybody,
I have this problem since few months:
Sometimes out of nowhere the screen starts flashing (like turning up brightness to 100%) for a split second when I touch it. After a while it stops. I have no idea where it comes from or how to replicate it. Sometimes restarting the device helps, sometimes not.
Automatic brightness is turned off.
Can anyone think of the origin of this problem or how to solve it?
It is a A2017G and on 7.1.1 with A2017GV1.2.0B05 but was the same with the last update (B04?).
Anything I could think of would be SystemUI Tuner, but I only use it to hide the NFC icon.
Thanks!

Try turning off assertive display under display settings

Tebor said:
Try turning off assertive display under display settings
Click to expand...
Click to collapse
Thanks! I turned it off now, hopefully it won't occure anymore.