We have a fix
Please read this post (and Thanks Milaq for the fix!!) and follow the instructions.
[*]Also, can someone test custom auto brightness levels too please?
I have made a ClockWorkMod flashable version of the fix in this post. This should cover almost all ROMs, irrespective of how the device is named in build.prop (leo, htcleo, bravo, qsd8k).
Original Post:
UPDATE: Thanks to Looki75, we have a workaround using Tasker to have custom auto-brightness levels with the flashing LED libraries here. Please go through his post and give your feedback!
I am rewriting the whole post, based on what I realized/ learnt today
We currently two lights libraries for to our phone:
lights.htcleo.so - this file has working auto-brightness and flashing LED notifications - but custom auto-brightness settings do not work (more on this a bit later)
lights.qsd8k.s0 - this file has working auto-brightness and custom auto-brightness levels, but LED notifications do not flash
Custom auto-brightness settings
What is it?
This is a setting/ feature in CM7 ROMs, not sure if MIUI has it or not (Users, please confirm if you have custom auto-brightness settings in non-CM7 based ROMs)
In a pitch dark room, the screen's brightness chosen by auto-brightness setting may be higher than required. With custom auto-brightness, the level of brightness the phone uses for a specific amount of light can be configured - the biggest benefit being higher battery life. Please read this post by @Dorimanx for custom auto-brightness levels.
How do I know if I have it or not?
You do not have the lights library that is compatible with custom auto-brightness levels if:
Your LED Notifications work (Except HeirOS kernels)
If you have something similar to this in your logcat:
20:50:43.090 Error lights 180 ***: value=90 (Mode=1)
20:50:43.090 Error lights 180 ***: value=91 (Mode=1)
20:50:43.090 Error lights 180 ***: value=92 (Mode=1)
20:50:43.090 Error lights 180 ***: value=94 (Mode=1)
Click to expand...
Click to collapse
On the other hand, you have it if
Your LED does not flash
Your screen will dim for several seconds (5~10seconds) before timing out
You do not see the errors I had quoted above in your logcat
So what is the point of this thread?
I had tried several Kernel combinations (and libaudio.so, but that does not matter in this issue) while trying to figure out the No Sound/ BT Voice Command/ libaudio.so issues, and found out that even if I have lights.qsd8k.so, which enables custom auto-brightness levels, LED Notifications flash with HeirOS 1.7.5 Kernel - they flash in amber and green alternatively. This gave me a hope that
This is something to do with the kernel (I used Tytung's initrd.gz, so it is not from there...)
This could be fixed easily with all our kernels, because HeirOS has already done it!
So What Next?
Anyone using any of the HeirOS kernels see what library you have (/system/lib/hw), and please use the lights.qsd8k.so if it is not there, deleting lights.htcleo.so while at it (it is available in the Mirrors used by @Dorimanx), and confirm if you concur with my observations - please mention the kernel version and the name of the lights library in your feedback.
Once we have that confirmed, we can request HeirOS to let us know the secret ingredient (or someone intelligent enough to look through the source codes can find it and post the diff/ findings).
This is not a critical/ experience-affecting issue, but rather something that is now "broken" and can be fixed without much ado!! I am sorry for not being clear earlier, a little bit of Rum cleared things up for me
Lets now restart this discussion!!!
It is people like you that are going to make our phone as if it came with android when we bought it! I know you are not the one doing the coding but with all your support, your don't give up attitude, and your connections you get the job done. Thank you for all your determination.
Sent from my HTC HD2 using XDA App
hopefully the next thread for collaboration work that will become one of it's kind in hd2 android history. thx for your dedication and all the testing that you do! thanks to all the devs making our hd2 improving everyday.
I have posted a request in HeirOS' kernel thread, meanwhile can those who use earlier versions (1.7.2 or so) confirm if they have working LED Notifications when you use a working auto-brightness configuration please?
If so, I think we can trawl the source code posted on the first post of HeirOS kernel thread...
ph03n!x said:
We currently have to choose between a working auto-brightness setting, or a working flashing LED notification in most configurations/ kernals....
Click to expand...
Click to collapse
Had never problems with auto brightness and my last kernel with a non working LED notification is older than around a half year. But I tried only MDJ, Tytungs and Raf's kernel. Green and orange LED are working perfect with these.
What problems do you have with auto brightness? Not working or the false brightness for the actual light?
Only outdoor at sunshine the auto brightness sometimes didn't choose the maximum brightness, than I set manual to max.
Nixda99 said:
Had never problems with auto brightness and my last kernel with a non working LED notification is older than around a half year. But I tried only MDJ, Tytungs and Raf's kernel. Green and orange LED are working perfect with these.
What problems do you have with auto brightness? Not working or the false brightness for the actual light?
Only outdoor at sunshine the auto brightness sometimes didn't choose the maximum brightness, than I set manual to max.
Click to expand...
Click to collapse
The auto-brightness / LED notifications are from /system/lib/hw/lights.htcleo.so (or lights.qsd8k.so).
In our case if your ROM's chef chose to have a working LED Notification configuration, auto-brightness will not work - the display will have a fixed brightness irrespective of the surroundings, and will not dim before fading out.
If you choose working Auto Brightness, the screen will maintain ambient lighting, but when have a missed call or SMS or email or chat, the LED stays on and does not flash.
That said, what kernel are you using? And can you check your logcat right from system boot (using QtADB?) and let us know if you see any errors?
ph03n!x said:
The auto-brightness / LED notifications are from /system/lib/hw/lights.htcleo.so (or lights.qsd8k.so).
In our case if your ROM's chef chose to have a working LED Notification configuration, auto-brightness will not work - the display will have a fixed brightness irrespective of the surroundings, and will not dim before fading out.
Click to expand...
Click to collapse
Yeah...
Typhoon included Led blinking, i always replace it with lights.qsd8k.so with auto-brightness, i dont care about Led blinking too much, more interesting good working auto-brightness
Install led me know from the market and you will have both working fine.That is what i do in dorimanx rom which has auto brightness enabled by default.
eseregin said:
Yeah...
Typhoon included Led blinking, i always replace it with lights.qsd8k.so with auto-brightness, i dont care about Led blinking too much, more interesting good working auto-brightness
Click to expand...
Click to collapse
Sent from my HD2 using XDA App
ph03n!x said:
The auto-brightness / LED notifications are from /system/lib/hw/lights.htcleo.so (or lights.qsd8k.so).
In our case if your ROM's chef chose to have a working LED Notification configuration, auto-brightness will not work - the display will have a fixed brightness irrespective of the surroundings, and will not dim before fading out.
If you choose working Auto Brightness, the screen will maintain ambient lighting, but when have a missed call or SMS or email or chat, the LED stays on and does not flash.
That said, what kernel are you using? And can you check your logcat right from system boot (using QtADB?) and let us know if you see any errors?
Click to expand...
Click to collapse
If I remember it correctly, the working LED Notification (i.e. No fading out feature) of lights.htcleo.so in my GB ROM is from Gpc.
Moreover I think that the developer of LedMeKnow app, which is free by the way, may point out to the developers what to change in order to have both auto brightness and led blinking working out of the box for hd2s
karapialis said:
Install led me know from the market and you will have both working fine.That is what i do in dorimanx rom which has auto brightness enabled by default.
Sent from my HD2 using XDA App
Click to expand...
Click to collapse
Sent from my HD2 using XDA App
leds and auto brightness work perfectley if you use the lights file from iamgpc. So I dont see the problem. Secondly this problem is hard to catch I can remember that Letama and gauner1986 tried to solve this problem but at the end they gave up.
jan-willem3 said:
leds and auto brightness work perfectley if you use the lights file from iamgpc. So I dont see the problem. Secondly this problem is hard to catch I can remember that Letama and gauner1986 tried to solve this problem but at the end they gave up.
Click to expand...
Click to collapse
Yes, manual brightness works in GPC's lights.htcleo.so, but auto-brightness does not.
I found the HeirOS has fixed this (though not documented) in 1.7.5 (not tested earlier versions)...
ph03n!x said:
We currently have to choose between a working auto-brightness setting, or a working flashing LED notification in most configurations/ kernals.
I am saying "most" because in my quest to fix the No Sound/ BT Voice Command/ libaudio.so issues, I tested various kernels and configurations, and found that with HeirOS 1.7.5 kernel, I have a working auto-brightness WITH flashing LED notifications. The notifications actually flash amber and green.
So looks like this is something that we can fix easier than the close to 5 weeks spent on the No Sound bug
HeirOS, please share your thoughts/ inputs for the benefit of all of us!!
This is not a critical/ experience-affecting issue, but rather something that is now "broken" and can be fixed without much ado!!
My explanation / understanding of the LED Notification vs. Auto Brightness issue- correct me if required
Click to expand...
Click to collapse
Here is a well-known solution for auto-brightness + flashing LED:
karapialis said:
Install led me know from the market and you will have both working fine
Click to expand...
Click to collapse
Like I said earlier, while fixing it natively is a good-to-have solution, and not a deal breaker for almost all of us. But still having it fixed surely feels good, doesn't it?!!
karapialis said:
Install led me know from the market and you will have both working fine
Click to expand...
Click to collapse
Updated the first post
karapialis said:
Moreover I think that the developer of LedMeKnow app, which is free by the way, may point out to the developers what to change in order to have both auto brightness and led blinking working out of the box for hd2s
Sent from my HD2 using XDA App
Click to expand...
Click to collapse
LED Me Know eats up battery while flashing notification. When its flashing LED, the battery drain is more than 100mAh. Though I haven't used the application in a long time, but I remember previously it used to do that...I wonder if its changed now..
I actually prefer a static LED with working auto brightness.
Its very obvious without staring at my phone whether I have a new text, missed call, or otherwise. I tend to miss the blinking since its 8 seconds apart.
(know it can be configured to 3 seconds, but still)
Sent from my HTC HD2 using Tapatalk
ph03n!x said:
Yes, manual brightness works in GPC's lights.htcleo.so, but auto-brightness does not.
I found the HeirOS has fixed this (though not documented) in 1.7.5 (not tested earlier versions)...
Click to expand...
Click to collapse
Auto brightness works fine here.
In HeirOS 1.8 kernel i have led working and i do notice that when its really dark the screen will get bright and when its super sunny it gets darker so i believe auto brightness + led works fine in his new test kernel btw i am on sense gb rom.
Vice versa
In HeirOS 1.8 kernel i have led working and i do notice that when its really dark the screen will get bright and when its super sunny it gets darker so i believe auto brightness + led works fine in his new test kernel btw i am on sense gb rom.
Click to expand...
Click to collapse
Sent from my HD2 using XDA App
Auto brightness with flashing LED notification works perfectly in Tytung's rom and kernel.
Related
Based on this thread. I've done some digging and think that it is possible to make an app to control the backlight. I've came out with a quick app just to show the prove of concept how it works but since I'm not familiar writing android apps and APIs, I leave it for you experience peeps to do it
I believed with some coding, you should be able to:
1) enable BLN with notifications - SMS, MMS, Gmail, missed calls and what not
2) Pulse BLN
3) Allow user to control pulse duration
4) Control when to stop BLN after N times or whatever
How the app works:
The apk is in the bin directory so after install, run the app and click on the toggle button. Turn power off or wait for screen off, you will see the BLN light up for 2 sec then goes off.
Pre-requisites
1) Use my kernel here (b4.2) or
2) Use neldar's kernel but you will need to restore back the modded lib that he replaced back to stock.
I've attached the source code showing how it can be done including binary compiled that I did using Eclipse. I would hope if you take up this project, please open source it so I can incorporate any changes with kernel support.
Does 'pulse' effect require wakelock?
xan said:
Does 'pulse' effect require wakelock?
Click to expand...
Click to collapse
afaik, yes but i dont know the API enough to know if there is any workaround
would be great if someone could get this thing to work on our sgs!
Currently i'm using the great BackLightNotification v0.9.8 RC3 mod, but a pulsing backlight would even be greater!
xan, are you working on this?
Nope, I'm not (not convinced about it yet...)
I'm using BLN + missed call and I'm completely happy with it.
It seems only improvement over neldar's notification is "pulse" (or better referred as "blink"?) effect, which with my little knowledge about APIs would definitely be triggered during wakelock, which is dealbreaker for me. I dont see any good sacrificing battery life during wakeups for blinking a diode.
Hi all.
I have problem in android with display brightness.
When i boot from winmob to android brightness on maximum like in windows mobile. But when he sleep first time or i press power button and then wake him up by pressing power button brightness become lower. In settings brightness on maximum. I try move from max to min and move back to maximum but brightness don't become to normal maximum like in first after booting.
I tried different kernels but it don't solve my problem.
Any body have same problem?
viber.ua said:
Hi all.
I have problem in android with display brightness.
When i boot from winmob to android brightness on maximum like in windows mobile. But when he sleep first time or i press power button and then wake him up by pressing power button brightness become lower. In settings brightness on maximum. I try move from max to min and move back to maximum but brightness don't become to normal maximum like in first after booting.
I tried different kernels but it don't solve my problem.
Any body have same problem?
Click to expand...
Click to collapse
First, wrong section. This should go in the Android section, preferrably in the build thread for whichever build you're using.
Second, if you had tried that little search button you would've found that yes, this is a bug. I believe it's even on the tracker... Again, if you had searched you also would've found some workarounds. Good luck.
Thank you for reply.
In android section i don't have rights to create thread.
This bug in every cwm builds which i used with any kernel. Exclude last kernels from october. I used search before but don't find workarounds with touch pro 2 brightness bug. If you found something can you give me link.
Thanks.
viber.ua said:
Thank you for reply.
In android section i don't have rights to create thread.
This bug in every cwm builds which i used with any kernel. Exclude last kernels from october. I used search before but don't find workarounds with touch pro 2 brightness bug. If you found something can you give me link.
Thanks.
Click to expand...
Click to collapse
XDAndroid doesn't use CWM.
arrrghhh said:
XDAndroid doesn't use CWM.
Click to expand...
Click to collapse
Thanks for reply, arrrghhh.
I install XDAndroid FRX07.1 not CWM.
And is not solve problem. On Rhod100 brightness after first display shut off lower around on 25%. Autobrightness also after first display off not working.
If any body have same bug can you give link where this problem solving?
Thread moved.
At least try to search, OP... FFS.
Search FRX07.1 thread for "brightness".
Amazing.
For people that want to save some battery juice and think that the autobrighntess values are too high...I got the right mod for you.
I lowered the autobrighntess values in framework-res:
old:
Code:
<integer-array name="config_autoBrightnessLcdBacklightValues">
<item>63</item>
<item>63</item>
<item>63</item>
<item>96</item>
<item>130</item>
<item>143</item>
<item>171</item>
<item>199</item>
<item>227</item>
<item>255</item>
</integer-array>
new:
Code:
<integer-array name="config_autoBrightnessLcdBacklightValues">
<item>1</item>
<item>11</item>
<item>23</item>
<item>35</item>
<item>48</item>
<item>55</item>
<item>80</item>
<item>150</item>
<item>200</item>
<item>255</item>
</integer-array>
People who dont know what this mod is doing, a small explanation.
When you got your brighntess on "automatic" your screen brighntess will be set regarding the value of you brighntess sensor.
So if its dark outside = low screen brighntess,
if its bright outside = high screen brighntess.
But in my opinion the brighntess states of the automatic screen brighntess are far too high and wastes battery.
When you also compare both first values in the two arrays you see that the minimum autobrighntess value was at 63 as default.
So when its completly dark in your room/outside your screen brighntness is brighter then it has to be.
...so you have maybe already noticed that the manual brighntess you can yet is far lower then the minimum autobrighntess value.
Its a flashable zip and compatible with Leedroid Tweaks.
In the next version of Leedroid Tweaks there will be a toggle to choose different autobrighntess arrays:
normal, low, lowest.
But for now you can use this zip with my prefered values.
hf:
Pls make a backup, before flashing this zip.
http://d-h.st/JWk
Thank you to bring this amazing mod
Works great. It's not as over powering with the brightness now.
Sent from my HTC One X using Tapatalk 2
Evil-Dragon said:
Works great. It's not as over powering with the brightness now.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Yeah, but still need to test if that values are okay for daily use.
Could be that a few steps are too low, so wou wouldlnt see the screen as good when its bright outside.
Just tested it my office..will seeover teh next two days if that values are okay (-:
Will keep you posted, weather here is awful atm, so can't test in sunny conditions but inside is fine.
Sent from my HTC One X using Tapatalk 2
Thanks..I'll try it later..
This mod seems a good idea.
Have only been using my phone for a day or so, but the screen does seems to drain the battery somewhat. Am hopeful that your mod will help.
It's a good idea to have different profile with LeeDroid tweaks.
Already liking this mod, many thanks
Sent from my HTC One X using Tapatalk 2
Mod working great. Now to reap the rewards of better battery life
Sent from my HTC One X using XDA
great job, there would be possibility of a zip to restore the original values?, thank you very much.
great mod, i like your new settings. i tried your new setings today afternoon in my car, the display was bright enough for me.
more outdoor usage this weekend, i will tell you if the brighness is too low.
it's working perfect in low/no light, just the right brightness for me
however, during the bright day light this afternoon it was constantly changing brightness, one second very bright, 2nd second very dark, third second somewhere in between then start the cycle again one second very bright, 2nd second....
but seeing that no one else has mentioned about this then i conclude it must be something that i've done wrong... again... hehe (i'm gonna keep using tomorrow and see how it behaves)
keep up the good work matey and take ur sweet time before getting married, as someone once said 'Marry in haste, repent at leisure'
Thanks.
Did you perhaps find a solution for the backlight of the menu buttons.
I get the feeling they are not lighting up correctly.
When iam in my backyard in the dark the buttons don't light up, till you cover the sensor complete.
Others are having the same problem?
Can you tweak those values too?
Sent from my HTC One X using xda premium
Whiskey103 said:
Thanks.
Did you perhaps find a solution for the backlight of the menu buttons.
I get the feeling they are not lighting up correctly.
When iam in my backyard in the dark the buttons don't light up, till you cover the sensor complete.
Others are having the same problem?
Can you tweak those values too?
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
They are also in framework-res (-:
Whiskey103 said:
Thanks.
Did you perhaps find a solution for the backlight of the menu buttons.
I get the feeling they are not lighting up correctly.
When iam in my backyard in the dark the buttons don't light up, till you cover the sensor complete.
Others are having the same problem?
Can you tweak those values too?
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
+1 ... same problem here
hey buddy,
do you have stock value zip in case want to back to it?
Thanks
Onepagebook said:
hey buddy,
do you have stock value zip in case want to back to it?
Thanks
Click to expand...
Click to collapse
you could just replace the framework-res with the one of your preferred rom in the flashable zip. or when your use leedroid tweaks use the framework-res of that.
At work at, can provide two flashable zips after work.
hi,
is it possible for a rooted phone without any mods to flash this in?
since ur 1st post stated leedroid tweaks which i assumed meant mainly for leedroid mods
qw_zzz said:
hi,
is it possible for a rooted phone without any mods to flash this in?
since ur 1st post stated leedroid tweaks which i assumed meant mainly for leedroid mods
Click to expand...
Click to collapse
it will work on each rom, which is rooted and deodexed.
...not really sure about the deoxed one..make a cwm backup and try it (-:
it's a bright sunny afternoon here and your auto brightness settings are working perfect today, must have been the gremlins yesterday
i've made a bunch of transition effects including ics, bounce, flip etc using your zip to flash them, if you want to test them and use them you are more than welcome (i've downloaded to my dropbox, so pm me if you're interested)
Today is the very first time ever for me to root an android device and thank God it run perfectly.
Now i am using AIC kernel for V500 4.4.2 stock ROM. (http://forum.xda-developers.com/showthread.php?t=2741405)
Gamma correction in it really improved screen and picture quality. (plus 8000 antutu point increase bonus)
Before, i can barely see anything in Bloodborne trailer video. (http://www.youtube.com/watch?v=G203e1HhixY)
Since i cant post in development thread, i hope i can find answers to the followings:
Is it possible to further improve gamma in the future?
Even though currently gamma is improved, but the brightness level issue still persist. Is it hardware or software issue?
Is there any possibility for brightness level improvement in the near future (kernel) update?
All in all, i really like my G Pad and really hope for the possibility to receive screen improvement update in the near future.
uchihamonkey said:
Today is the very first time ever for me to root an android device and thank God it run perfectly.
Now i am using AIC kernel for V500 4.4.2 stock ROM. (http://forum.xda-developers.com/showthread.php?t=2741405)
Gamma correction in it really improved screen and picture quality. (plus 8000 antutu point increase bonus)
Before, i can barely see anything in Bloodborne trailer video. (http://www.youtube.com/watch?v=G203e1HhixY)
Since i cant post in development thread, i hope i can find answers to the followings:
Is it possible to further improve gamma in the future?
Even though currently gamma is improved, but the brightness level issue still persist. Is it hardware or software issue?
Is there any possibility for brightness level improvement in the near future (kernel) update?
All in all, i really like my G Pad and really hope for the possibility to receive screen improvement update in the near future.
Click to expand...
Click to collapse
I heard a week or so ago through the grapevine of a version 20d coming out pretty soon. I have held off making any other changes to the AIC kernel until I see what LG did(no sense reinventing the wheel).
What brightness issue would you like changed? I know in general people think the Gpad screen is dark, but some of the AIC kernel users think the lowest brightness is too bright as well.
I think the screen is pretty bright at 100%, so for me it's a software issue. That's in 2 places, the kernel backlight driver, and the ROM brightness(think brightness slider).
aicjofs said:
I heard a week or so ago through the grapevine of a version 20d coming out pretty soon. I have held off making any other changes to the AIC kernel until I see what LG did(no sense reinventing the wheel).
What brightness issue would you like changed? I know in general people think the Gpad screen is dark, but some of the AIC kernel users think the lowest brightness is too bright as well.
I think the screen is pretty bright at 100%, so for me it's a software issue. That's in 2 places, the kernel backlight driver, and the ROM brightness(think brightness slider).
Click to expand...
Click to collapse
Tks for the reply and also thank you very much for the kernel, it really is helping a lot!
Rather than issue, i should have worded it as G Pad having a relatively low brightness level/dim display.
Compare to my nexus 7 1st gen, G Pad at 70% brightness level still not as bright as nexus at 30%.
Actually i dont really mind it, 70-80% G Pad brightness level is my sweet spot.
However, it would be great if the number is 30% rather than 70% (i am just feeling paranoid of having big number for a display setting).
I also realized that colours (might be) a bit off, especially red that looks orange-ish.
In general display seems lean toward yellow (yellowish-white).
Wonder if this is a common thing for all unit?
Hopefully it is just a matter of colours calibration that can be solved through software update not a hardware characteristic.
I tried Screen Adjuster and added more blue and red, but i just cant seems to find the proper setting to create a whiter white or redder red...
All in all, it is nice to hear version 20d may be coming soon.
Hopefully LG will address all these screen related things.
Also, really look forward to your another great work, especially when LG get it all wrong again this time
aicjofs said:
I heard a week or so ago through the grapevine of a version 20d coming out pretty soon. I have held off making any other changes to the AIC kernel until I see what LG did(no sense reinventing the wheel).
What brightness issue would you like changed? I know in general people think the Gpad screen is dark, but some of the AIC kernel users think the lowest brightness is too bright as well.
I think the screen is pretty bright at 100%, so for me it's a software issue. That's in 2 places, the kernel backlight driver, and the ROM brightness(think brightness slider).
Click to expand...
Click to collapse
It would be great if you could add row scheduler when you next update your kernel.
Thanks in advance rich ?
Sent from my LG-V500 using XDA Premium HD app
uchihamonkey said:
Tks for the reply and also thank you very much for the kernel, it really is helping a lot!
Rather than issue, i should have worded it as G Pad having a relatively low brightness level/dim display.
Compare to my nexus 7 1st gen, G Pad at 70% brightness level still not as bright as nexus at 30%.
Actually i dont really mind it, 70-80% G Pad brightness level is my sweet spot.
However, it would be great if the number is 30% rather than 70% (i am just feeling paranoid of having big number for a display setting).
I also realized that colours (might be) a bit off, especially red that looks orange-ish.
In general display seems lean toward yellow (yellowish-white).
Wonder if this is a common thing for all unit?
Hopefully it is just a matter of colours calibration that can be solved through software update not a hardware characteristic.
I tried Screen Adjuster and added more blue and red, but i just cant seems to find the proper setting to create a whiter white or redder red...
All in all, it is nice to hear version 20d may be coming soon.
Hopefully LG will address all these screen related things.
Also, really look forward to your another great work, especially when LG get it all wrong again this time
Click to expand...
Click to collapse
You can use Faux Clock or System Tuner to adjust the color temp and gamma.
meanoc said:
You can use Faux Clock or System Tuner to adjust the color temp and gamma.
Click to expand...
Click to collapse
Really...?
In that Kernel thread it states....
Add Faux Display interface (gamma control seems broken)
so does the Faux app control the gamma, even though aicjofs had noted that it seemed to be broken...?
vimesUK said:
Really...?
In that Kernel thread it states....
Add Faux Display interface (gamma control seems broken)
so does the Faux app control the gamma, even though aicjofs had noted that it seemed to be broken...?
Click to expand...
Click to collapse
It works for me?
meanoc said:
You can use Faux Clock or System Tuner to adjust the color temp and gamma.
Click to expand...
Click to collapse
Pardon me but where can i find this Faux Clock and System Tuner?
Do you have any preferred setting for optimum screen (colour) performance?
uchihamonkey said:
Pardon me but where can i find this Faux Clock and System Tuner?
Do you have any preferred setting for optimum screen (colour) performance?
Click to expand...
Click to collapse
You can find them here https://play.google.com/store/apps/details?id=com.teamkang.fauxclock and https://play.google.com/store/apps/details?id=ccc71.pmw.pro . Your best bet is to either use a calibration tool or just adjust it to your eyes.
Hi i have been looking for a module for ed xposed which hopefully can control lowest brightness level. I am on Asop rom on the poco f3 and development is in early stages which means in darker areas the low brightness goes to low. It would be useful if there were a module which can set the lowest brightness to a certain value which the system cannot got lower than e.g 12% I hope this is understood and perhaps ther is already a module available for this but i cant find it.
sam00561 said:
Hi i have been looking for a module for ed xposed which hopefully can control lowest brightness level. I am on Asop rom on the poco f3 and development is in early stages which means in darker areas the low brightness goes to low. It would be useful if there were a module which can set the lowest brightness to a certain value which the system cannot got lower than e.g 12% I hope this is understood and perhaps ther is already a module available for this but i cant find it.
Click to expand...
Click to collapse
RootDim [root] - Apps on Google Play
Dim many rooted device's screens below factory settings.
play.google.com
loopypalm said:
RootDim [root] - Apps on Google Play
Dim many rooted device's screens below factory settings.
play.google.com
Click to expand...
Click to collapse
Thankyou so much its working perfectly just what i needed.
I spoke to soon left the phone overnight and in the morning brightness very minimal again. I guess it stopped working.