Change the minimum brightness level from usual 10 to 1. It doesn't modify the autobrightness level map so automatic brightness won't be lowered (though it can be easily adjusted on CM11).
This is so far exactly the same as GravityBox offers (modifying 'config_screenBrightnessSettingMinimum').
But Minimum Brightness offers one unique feature - it also modifies the lower brightness levels in MX Player (free/paid). Because no matter whatever you use manual or auto brightness, MX Player always uses minimum brightness of 0.05 (12/255, 19/255, 27/255, 36/255...). To actually lower the brightness, you would have to turn off brightness control in MX Player or use one of many 'overlay filter brightness app'.
So Minimum Brightness module retains the same quadratic function for brightness levels but includes lower values (1/255, 4/255, 9/255, 16/255, 25/255...).
Minimum Brightness uses value 1/255 which might not be suitable for every display (meaning LCD) but it suits perfectly my Super AMOLED screens (Galaxy S5 / Galaxy Tab S 8.4) and watching videos at night is still enjoyable.
There are many excellent auto brightness apps (Lux, Darker etc) that can use overlay filters to lower brightness even more so it's up to everyone to try and decide.
This module has been merged into new module http://forum.xda-developers.com/xposed/modules/mod-xposed-tweaks-cm-t3279109. Please check that module for any future updates.
Hello! Thanks for the mod, I will test
Works very nice on Xperia Z2, however minimum brightness is absolute darkness Could you please add an option to define minimum brightness value?
_mysiak_ said:
Works very nice on Xperia Z2, however minimum brightness is absolute darkness Could you please add an option to define minimum brightness value?
Click to expand...
Click to collapse
The situation is the same on my Xperia SP. When I set the brightness to miniumum the screen is totally black, also when the backlight decreases after 10 seconds screen gets black.
Hi! Tried min brightness but when screen is set to the lowest level, I get a white screen after locking the phone.
Sent from my DIAMOND D1 using XDA Free mobile app
Really great tweak!! I'm noobie in Android enviroment with my new Elephone P3000S and the lowest screen brightness is to high for me so your tweak is very usefull.
I also have the issue that the lowest brightness level sets the screen completly black and I have been scared for 1 hour truing to solve a completely black, touching all buttons but the phone didn't "wake up". Finally, pressing power buttom + volumen up + home soft key it has worked :angel:
So it would be very important to prevent black screen by allowing the user to set the minimun level.
Thanks!
Hey, I know making GUI is a pain in the ass so can you please make alternative version with minimum brightness set to 2? That will satisfy most of people complaining here. Your app is currently the only dimmer working on lollipop.
Dri0m said:
Hey, I know making GUI is a pain in the ass so can you please make alternative version with minimum brightness set to 2? That will satisfy most of people complaining here. Your app is currently the only dimmer working on lollipop.
Click to expand...
Click to collapse
I will have a new device soon so that could make me change my mind about lowest value and UI.
@Dri0m
In the first post you can find archive containing multiple versions of module with different low values.
How to disable this module...?
I installed this module last night, enabled it in Xposed Framework, but did nothing with it. Then this afternoon I opened the Settings menu, went to Display, and before I could do anything else I received a phone call. As I terminated the call, the screen flashed, the phone rebooted--and after restarting it is completely, or almost completely blank. If I repeatedly tap the power button I get a fraction-of-a-second glimpse of the SIM PIN screen at normal brightness. This leads me to the suspicion that, by some weird combination of bad luck and an accidental touch of a finger after terminating the phone call, that the Minimum Brightness somehow got set--although why the phone then rebooted I don't know.
Anyway, by luck and good judgement I finally managed to enter the correct SIM PIN and then the phone unlock PIN. However, I can do nothing else. The screen is still blank, and as the phone is currently unlocked I don't want to touch the power button. Before sending the phone back to the manufacturer or anything drastic like that, I would like to try disabling the Xposed Framework. Whilst trying to find something useful in Windows Explorer I found Xposed-Disabler-Recovery.zip in the Internal storage\Android\data\de.robv.android.xposed.installer\files folder on my phone. I assume that this should be what I need. However, as I cannot see anything on the screen I would need to know the exact buttons to press, in which order and how many times etc, in order to enter the Recovery menu and do what is needed. According to the phone manufacturer the OS is unmodified Android 4.4.2., although strangely they will not even tell me which keys to press to enter the Recovery menu (long story, the upshot is, they flat out refuse to help apart from suggesting returning the phone).
Note that I only suspect it is the Minimum Brightness module that is causing the problem, however the problem did not exist before yesterday (when I installed the module), and as I was about to do something with the brightness when the phone rebooted itself, it seems too much of a coincidence to be anything else. If I cannot disable the module/framework, the only other thing I can think of is a factory reset--but again I would need to know exactly which buttons to press, in which order etc. Unfortunately at the moment USB debugging is not enabled, and again without the screen I cannot access it to turn it on.
Any help or suggestions hugely appreciated.
PL
@Papalazzzaru
Xposed now sports a safemode which allows you to disable Xposed during bootloops. To disable Xposed, you'll have to repeatedly tap one of the hardware buttons (Power, Volume, or Home) on your device during startup.
During boot, your device will vibrate twice when it detects the first key press. You'll then have five seconds to press that same button four more times, with each keystroke producing a short single vibration. After ending with a long vibration, your device will disable and prevent most of Xposed's actions, allowing you to easily troubleshoot problematic modules.
Sorted
Outstanding, thanks.
Papalazzzaru said:
I installed thi............. gely appreciated.
PL
Click to expand...
Click to collapse
Device model please?
Caterpillar S50, on Android 4.4.2, baseband version LTE_S0201121.0_S50_0.017.00.
it is compatible with lollipop?
imam88 said:
it is compatible with lollipop?
Click to expand...
Click to collapse
The MX Player part still works. I don't know about the lowest value of brightness in general but at least with CM12 & Samsung the brightness goes to the hardware minimum by default.
Thanks, this is exactly what I want.
Could you make it for LP ?
I want my phone be absolute zero brightness for driving navigation.
Tested it on CM12.1 Nightly on the Nexus 6. It works here, but on 0 the screen is a bit purple. However, I guess this is the screen's fault
Gesendet von meinem Nexus 6 mit Tapatalk
moneytoo said:
The MX Player part still works. I don't know about the lowest value of brightness in general but at least with CM12 & Samsung the brightness goes to the hardware minimum by default.
Click to expand...
Click to collapse
Yes it works
This module seems to be working well on the Moto X Pure Edition (Motorola xt1095) running Lollipop 5.1. It's an AMOLED screen, and I personally find the minimum brightness on 5.1 too bright, so this has helped solve that.
I'm using Motorola Moto E(condor), I had automatic restart problem in my stock ROM, later I unlocked the bootloader and installed custom ROM, I had been using custom ROM for months, Now suddenly when I changed the ROM My mobile's brightness has become low, Even bootloader brightness is low, and now if i enable auto brightness and move the brightness slider to 25% its becoming darken(unable to view anything). So I changed to Stock ROM, but the problem still exists.
Help me out please......
:crying::crying::crying::crying:
Same problem here. Any luck finding a solution?
Flash this maybe your brightness will increase.
http://forum.xda-developers.com/android/software/mod-xtremevideo-media-youve-seen-t3174158
Though I think it might be a hardware related problem.
Hi guys!
I have a strange thing on my Dell Venue 8 (3830/T02D).
While the auto brightness is off, the brightness is still changing, depending on the type of content. For example, if I scroll o long page with white background in browser, and suddenly some dark object or picture will appear in the window, the brightness of the screen will change. It happens constantly when I use my tab with low brightness settings.
In other words the brightness constantly jumps, when something happens on the screen, so it's really very annoying.
For the first time I thought, that it is hardware issue, but later I google the problem and find out some similar questions, where people say, that it is not a hardware, but Android 4.4 problem/bug or Intel compatibility issue (it was written, that many Asus tabs and even Nexus have the same problem and it is called dynamic contrast, that is stupid function exclusively in Android 4.4).
Is it true?
Will the downgrade to 4.3 help to get rid of this random brightness jumps?
Is there any fix/hack to override this problem without flashing/downgrading?
Yumioki said:
Hi guys!
I have a strange thing on my Dell Venue 8 (3830/T02D).
While the auto brightness is off, the brightness is still changing, depending on the type of content. For example, if I scroll o long page with white background in browser, and suddenly some dark object or picture will appear in the window, the brightness of the screen will change. It happens constantly when I use my tab with low brightness settings.
In other words the brightness constantly jumps, when something happens on the screen, so it's really very annoying.
For the first time I thought, that it is hardware issue, but later I google the problem and find out some similar questions, where people say, that it is not a hardware, but Android 4.4 problem/bug or Intel compatibility issue (it was written, that many Asus tabs and even Nexus have the same problem and it is called dynamic contrast, that is stupid function exclusively in Android 4.4).
Is it true?
Will the downgrade to 4.3 help to get rid of this random brightness jumps?
Is there any fix/hack to override this problem without flashing/downgrading?
Click to expand...
Click to collapse
I never noticed this problem but if other devices have it, and no fix was provided would be no fix for this device either.
I'm currently on 2019 june security patch, stock rom v10.3.3.0. Not planning to upgraded anytime soon bcos there is no bug i,ve encounter while using this version and battery life is great. But the lowest brightness is too bright and to blinding during the night. If i'm upgrade to the newest android 9 stock rom using fastboot, does this lowest brightness is fix? How about in android 10? Is it better? Need a quick answer cause this phone is going to make me go blind!!...
Search Google play store for "super dim screen" and try one of the apps, there were at least 2 which worked with this phone, but don't recall which ones exactly.
Or install this testing build of VAB and use super-dim option - https://forum.xda-developers.com/showpost.php?p=83909269&postcount=2224
The recent FunTouch OS 12 has a lot of features missing. It feels like IQOO has rolled up the updates in a hurry.
1. No Android 12 Clock widget.
2. No Quick Panel tiles like Android 12.
3. Dark mode not getting applied on App Drawer.
4. Etc etc
Bloody hell, when will we get Origin OS for Indian market.
This device has so much potential if they just unlock the bootloader for installating custom roms
Disabled animations in Developer menu doesn't get applied either
Also, home screen is not coming from many widgets like the one we get by swipimg right from left edge
This seems like an Alpha version without much testing and stitching with animations quite annoying like dark mode not applying to app drawer
This is almost the the first few versions when we bought the device during launch. Only after one June or July upgrade things became like a release version. Established that IQOO OS team for IQOO 7 releases updates without proper testing and going through beta testing as such issues were never encountered in IQOO 3 with IQOO OS which people for some reason criticize
Witnessing huge flashes of brightness fluctuations at night even when automatic brightness is turned off.
Still can't find a way to switch off Accessibility button
Prankey said:
Witnessing huge flashes of brightness fluctuations at night even when automatic brightness is turned off.
Still can't find a way to switch off Accessibility button
Click to expand...
Click to collapse
Same here. Gets blindingly bright in the middle of the night. My phone also keeps crashing atleast 3 times a day. Waiting for a fix update.
abnormalindian said:
Same here. Gets blindingly bright in the middle of the night. My phone also keeps crashing atleast 3 times a day. Waiting for a fix update.
Click to expand...
Click to collapse
Yup, same here as well. Plus sometimes when I enable battery saver the brightness also increases even if auto brightness is turned off and manual bright is set to lowest possible value.
I still have similar issues on my Vivo X80 Pro and many familiar features like the new Control Center are still missing! What shoud that? OriginOS would be so much better, why do you have to develop such a bad operating system internationally. I don't get it and I'm actually very, very excited about the X80 Pro but the software totally ruins the experience!