Hello XDAers, although I'm a new member I have been digging this community for quite a while
Anyway, I have searched for this but couldn't find a relevant thread..
Can anybody please add a feature which forcefully enables the brightness control bar in notification panel of samsung phones when battery drops below 5%? As by default after 5% brightness cannot be controlled in sammy ROMs.
Probably an Xposed Module can fix this.
The feature is only present in the GS3..and there must be a simple file requiring editing to remove/edit the code for brightness control below 5% battery. If anybody has any info for which file is responsible for this effect, please let me know so I can create a fix for this and post a module myself.
Come on..No replies to such a primitive problem?
Sent from my GT-I9100
Maybe send a p.m to all developers telling them how important it is.
Same problem on a Note 3 SM 9005. Solution needed
Hi guys - I have the same problem - on a Note 3 SM9005 running Android 4.4.2.
It's really an annoyance - we need a tweak to enable setting the brightness with battery below 5%!
Many TIA
Gail
Related
does anyone know of a way i can get the international version -5 or +5 auto-brightness adjustment? i want to extend my screen on time a little bit without having to adjust it manually all the time.
many thanks
Nobody knows of any way to get this one little tweak?
sent from my galaxy s4
a brightness app I like a lot
fade2green514 said:
Nobody knows of any way to get this one little tweak?
sent from my galaxy s4
Click to expand...
Click to collapse
I know this isn't what you're looking for - but - if you can't find it, take a look on the playstore for an app called Display Brightness - it has the icon of a yellow lightbulb. You can place a fine line along any edge of your screen and simply move it up or down to adjust the brightness. You don't have to leave what you're doing and I find it wonderful when I suddenly go out in the middle of the day and can't see a thing - at least I know where the control is.
How can I disable or avoid the android setting that makes the brightness go down to minimun when the phone goes to 5% battery?
I have an extended battery and it is very annoying. Maybe I can override the effect with a tasker profile or something?
I'm no expert so I don't know where to start to find any solution...
Anyone?
I tried with a tasker profile but it does not work when battery is under 5%... is there a script to stablish any brightness level?
I am interested too, I didn't have this problem on 4.1.2, but after I flashed 4.3 I encontered this issue.
Very annoying if it happens on sunlight, it makes impossible to use the phone!
I could partially fix it with the app "rootdim" on the Play store, with it I can force it but when the screen goes off it resets again
As far as Internet resources go, this is impossible on Android and is a limit imposed by the kernel.
My thoughts: maybe this is changeable with a build.prop tweak, or a custom kernel. There isn't even an Xposed mod available for this, nor is it included in Gravitybox, Wanam Xposed, or any other collection. I hate this limitation too, especially in the sunlight like @dabyd64 said. You can possibly try using an android shell something like "print 1 > /sys/class/display/brightness" or something like that. Depends on device! I will look into it.
All the best,
aarongillion63 said:
As far as Internet resources go, this is impossible on Android and is a limit imposed by the kernel.
My thoughts: maybe this is changeable with a build.prop tweak, or a custom kernel. There isn't even an Xposed mod available for this, nor is it included in Gravitybox, Wanam Xposed, or any other collection. I hate this limitation too, especially in the sunlight like @dabyd64 said. You can possibly try using an android shell something like "print 1 > /sys/class/display/brightness" or something like that. Depends on device! I will look into it.
All the best,
Click to expand...
Click to collapse
That is what rootdim does, at least you can use the phone, but you have to force the brightness each time you unlock the screen
It has a nice preset widget, so its almost fixed. Single touch and brightness restored.
I think the low brighness is forced because in old roms the screen would flicker if the battery was very low and the brightness set high.
So Samsung fixed it in the hard way
I have a mt6572 phone and I'm facing a problem related to brightness of my phone.
My screen brightness is always high and it burns my eyes at night.
I cant find any brightness option in my build.prop.
So I added this line to appropriate section of build.prop--
Code:
ro.lcd.min_brightness=blah(low as possible)
I rebooted my phone and nothing changed.
Still high brightness.
So,I tried this--
Code:
ro.init.screen_brightness=blah(as low as possible)
It didn't make any difference too.
I tried changing roms.
But every kk rom has the same issue(But ported from different phones).
It dont happen in LP roms.
I know about CF lumen,Darker and etc. screen controller app.I know those are great but I don't wanna use them.
I just want to get rid of it without using an app.
I will be glad if someone post a solution for me.
Regards
BatDroid
bump
Dear all,
I have an issue related to the Developer Options and the Background Processes Limitations (On Android 4.4.2 - Note 2 rooted):
Once I limit the background processes to 1 in order to save some battery I see that I have a side effect, the battery starts to became hot and discharges quickly, It's a very strange situation to face.
Someone knows a workaround for this situation ?
Thanks to all !
Belfast82 said:
Dear all,
I have an issue related to the Developer Options and the Background Processes Limitations (On Android 4.4.2 - Note 2 rooted):
Once I limit the background processes to 1 in order to save some battery I see that I have a side effect, the battery starts to became hot and discharges quickly, It's a very strange situation to face.
Someone knows a workaround for this situation ?
Thanks to all !
Click to expand...
Click to collapse
It is not a battery saving feature. Don't touch settings that you don't know anything about. Just increase it to default units otherwise you might make things worse. Use the default power saving features by samsung if you want to save battery.
Sent from my SM-G900H using Tapatalk
redhotiron2004 said:
It is not a battery saving feature. Don't touch settings that you don't know anything about. Just increase it to default units otherwise you might make things worse. Use the default power saving features by samsung if you want to save battery.
Sent from my SM-G900H using Tapatalk
Click to expand...
Click to collapse
Hello redhotiron2004,
perfect, thank you for the information.
Hello guys,
I am looking for help regarding an issue I have had since I swicthed to LineageOS.
The brightness setting is incorrect and the indicated brightness value is not the real brightness value (eg : 100% is not real 100%, 20% is the real 0%)
Here's the video
https://youtu.be/g4B8RAM0GHU
I have no idea where it could come from, I didn't have any specific issue with the installation of the ROM itself or anything related (Magisk daemon dies from time to tome but a reboot fix it, I don't think it is related)
Do you have any idea what could be the issue ?
Thank you.
Benben42 said:
Hello guys,
I am looking for help regarding an issue I have had since I swicthed to LineageOS.
The brightness setting is incorrect and the indicated brightness value is not the real brightness value (eg : 100% is not real 100%, 20% is the real 0%)
Here's the video
https://youtu.be/g4B8RAM0GHU
I have no idea where it could come from, I didn't have any specific issue with the installation of the ROM itself or anything related (Magisk daemon dies from time to tome but a reboot fix it, I don't think it is related)
Do you have any idea what could be the issue ?
Thank you.
Click to expand...
Click to collapse
Shouldn't you rather be asking this question in the ROM thread instead of here? The LOS users are concentrated there and anyone with a similar issue is likely to respond quickly there. Further if the issue is really ROM related, the devs have an opportunity to know about it and rectify it.