This is a very powerful mod that changes the brightness of the Xperia flashlight / torch.
This can cause damage if left on for extended periods of time. It is advised you install the medium version.
Source
Pre-Caution:
I take no responsibility to any burnt hands, burnt phones, or bricked phones. The chances of getting into a brick or bootloop is very low and I will aid you as much as possible, but will take no responsibility for this happening.
CAUTION:
The extreme version sets the torch to 1,000,000 Ua - in other words, its basically an industrial flashlight now, meaning it will get very hot, very quickly. Please take caution with using the extreme version.
DOWNLOAD:
Medium
Extreme
Uninstaller
SmarTemperature (To increase the temperature limit)
Installation:
1. Have a rooted device with /system access (So not the temp root method)
2. Download and move one of the zips to your SD Card
3. Enter recovery and backup your phone (Incase you want to revert back to default values)
4. Flash the Torch ZIP, and then flash the SmarTemperature ZIP
5. Enjoy!
Code:
# LED If setting for Indicator(uA)
if_indicator_level = 4125
# LED If setting for Torch or video recording (uA).
if_torch_vr = 500000
# Vf measured at factory (mV).
vf_factory = 2869
# Min voltage for VBat (mV)
v_batt_min = 3500
This mod works by modifying /etc/flashled_calc_parameters.cfg with custom values
NOTE:Take caution if you plan to modify this config file yourself.
XDA:DevDB Information
Xperia Brighter Torch Mod, Tool/Utility for the Sony Xperia Z5 Compact
Contributors
nzzane
Version Information
Status: Stable
Current Stable Version: V2
Stable Release Date: 2016-10-04
Created 2016-10-03
Last Updated 2016-11-22
Reserved:
My device shutdown when turning on the LED on medium, could you provide the initial value please?
raphoun said:
My device shutdown when turning on the LED on medium, could you provide the initial value please?
Click to expand...
Click to collapse
What firmware are you on & what Kernel are you using?
I have updated the OP with the first few lines of code for the medium version - as well as adding an uninstaller zip
nzzane said:
What firmware are you on & what Kernel are you using?
I have updated the OP with the first few lines of code for the medium version - as well as adding an uninstaller zip
Click to expand...
Click to collapse
The last firmware with OM5Z kernel. Thanks for the uninstaller
raphoun said:
The last firmware with OM5Z kernel. Thanks for the uninstaller
Click to expand...
Click to collapse
Very weird, do you still have "Allow OEM Unlock" enabled?
I am having the same issue here...
I am on Xpower 5.0 androplus kernel and it also happened on previous kernel... what could be the problem?
mine shutting down to , last stock rooted rom
If someone can find where the temp warning config file is, I will update this mod with that in.
i have tried to increase the temp warning temp but it has failed..
nzzane said:
If someone can find where the temp warning config file is, I will update this mod with that in.
i have tried to increase the temp warning temp but it has failed..
Click to expand...
Click to collapse
i dont think its the temp warning because my device doesnt over heat at all it just turns off...
if it was temp warning then it should get hot first then shut down am I right or ?
hey every one I just found this :
http://forum.xda-developers.com/xpe...-smartemperaturex-best-balanced-s810-t3438890
smartemp mod fixed my issue! had the extreme mod installed and turned on for couple of minutes , no shut down no warnings and also device doesnt even heat after the first couple of minutes on EXTREME TORCH
hope it works for you guys
@Gewiz told me about this so credit for him
madshark2009 said:
i dont think its the temp warning because my device doesnt over heat at all it just turns off...
if it was temp warning then it should get hot first then shut down am I right or ?
Click to expand...
Click to collapse
From what I have seen. The device, for Some reason, detects that it is heating quickly even thought it's not. This prompts the over heating warning.
It could be that the phone has a procedure in place to stop modification of the flashlight, but I have not seen this yet
madshark2009 said:
hey every one I just found this :
http://forum.xda-developers.com/xpe...-smartemperaturex-best-balanced-s810-t3438890
smartemp mod fixed my issue! had the extreme mod installed and turned on for couple of minutes , no shut down no warnings and also device doesnt even heat after the first couple of minutes on EXTREME TORCH
hope it works for you guys
@Gewiz told me about this so credit for him
Click to expand...
Click to collapse
Thanks, will add this to the OP
Hi, first of all, sorry in advance if it is a stupid post, I am no developer. Is it possible that everybody is running an extreme version and getting thermal problems because of a typo? I ve tried this mod (the medium version), and read the thread.
I opened the default configuration file, and compared it to the same file in the zip.
Two values change:
___________________default_____Medium________Extreme
if_indicator_level = _____3125_______4125___________5125
if_torch_vr = _________25000_____500000_________1000000
Isn't that strange? In the medium and the extreme versions, the indicator current is increased by 30% and 60% respectively, but the flash led's current goes from 25k to 500k and 1 million
The values seem to be in μA, that makes the default value of 25.000μA equal to 25mA, which seems about right for a led.
I ve modified the medium vetsion to the value "if_torch_vr =50.000 instead of 500.000. No shutdown, but I cannot judge how bright it is right now.
argotera said:
Hi, first of all, sorry in advance if it is a stupid post, I am no developer. Is it possible that everybody is running an extreme version and getting thermal problems because of a typo? I ve tried this mod (the medium version), and read the thread.
I opened the default configuration file, and compared it to the same file in the zip.
Two values change:
___________________default_____Medium________Extreme
if_indicator_level = _____3125_______4125___________5125
if_torch_vr = _________25000_____500000_________1000000
Isn't that strange? In the medium and the extreme versions, the indicator current is increased by 30% and 60% respectively, but the flash led's current goes from 25k to 500k and 1 million
The values seem to be in μA, that makes the default value of 25.000μA equal to 25mA, which seems about right for a led.
I ve modified the medium vetsion to the value "if_torch_vr =50.000 instead of 500.000. No shutdown, but I cannot judge how bright it is right now.
Click to expand...
Click to collapse
Hey, not a stupid post - So with the Z5 series they have a pretty low thermal limit, so thats why it is so retarded and shuts down, unless you have flashed the thermal limit raiser. (created for the purpose of the z5 thermal limit being so low)
Let me know if you notice a change in brightness, as the I may have miss-typed some of the code
Hi, I haven't looked it since.
I did not want to try that thermal mod. The posts on its thread weren't very encouraging. Decided to leave it set at if_torch_vr =50000
I can test again with other values but it won't be in the next days. Probably when I decide to jump to nougat
The Medium mod send my phone in temperature protection, if someone have Xposed try this module to increase the temperature limit
http://repo.xposed.info/module/michele2.thermal.disabler
Edit:
The module does not solve the problem, after a minute with the LED on the Z5c turns off after a temperature warning message.
cioce said:
The Medium mod send my phone in temperature protection, if someone have Xposed try this module to increase the temperature limit
http://repo.xposed.info/module/michele2.thermal.disabler
Edit:
The module does not solve the problem, after a minute with the LED on the Z5c turns off after a temperature warning message.
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=69743947&postcount=11
Did you tried that? I recommend v1.6.1
EDIT
WORKING FOR FEW SEC AND SHUTTING DOWN!
on my 1.54
im using green kernel for stock rom
Links dead, reupload? Thanks
Related
I have just downloaded ASTRO file manager and started browsing through system files, then Ive found a file called calibration in /etc/wifi . In order to try to have a better wifi signal, i have opened that file with text editor and found a line where i can read pa0maxpwr=70 i guess it can be possibly by putting a higher level, make the wifi signal stronger, but I dont have enough time to try this, so please try to confirm this by yourself and write here obtained results....
This file has been found in firmware .042 in R800i device with stock kernel/rom
Ive found another line that says: pa0itssit=62 , but i dont know for what is used this value....
I don't think changing the number will make you have a stronger signal.
Maybe it's like if the power signal is 70 or more, show the wifi signal at max (the little dot and 3 waves on top of it).
bamsbamx said:
I have just downloaded ASTRO file manager and started browsing through system files, then Ive found a file called calibration in /etc/wifi . In order to try to have a better wifi signal, i have opened that file with text editor and found a line where i can read pa0maxpwr=70 i guess it can be possibly by putting a higher level, make the wifi signal stronger, but I dont have enough time to try this, so please try to confirm this by yourself and write here obtained results....
This file has been found in firmware .042 in R800i device with stock kernel/rom
Ive found another line that says: pa0itssit=62 , but i dont know for what is used this value....
Click to expand...
Click to collapse
In the cheapo Chinese tablets from 2010 there were similar mods to increase the Wifi signal though they made the device (and more specifically the wifi antenna) extremely hot. So I wouldn't fancy doing it on a proper device.
pa0maxpwr determines the max power that is given to the wifi antenna, increasing it will just give you a hot phone and short battery
i have tried it (increased to 90) , but the wifi antenna hasnt increase its temperature and the battery works as always....
And have you increased your Wifi strength?
Logseman said:
And have you increased your Wifi strength?
Click to expand...
Click to collapse
i dont fell any increase in the wifi signal.....
Txpower=100?
I tired changing the value, but it seems to revert back to its default (doesn't save). I'm rooted with the zergrush method.
If someone is playing with this, try 255 for a value and see if it makes a difference. 255 is max for an int (1byte)
Njord0 said:
I tired changing the value, but it seems to revert back to its default (doesn't save). I'm rooted with the zergrush method.
If someone is playing with this, try 255 for a value and see if it makes a difference. 255 is max for an int (1byte)
Click to expand...
Click to collapse
I think you have to mount the system as R/W. If it doesnt work try setting the correct properties/permissions of the file....
I found that file in other folders inside phone memory, maybe have to change all the same files....
AndroHero said:
pa0maxpwr determines the max power that is given to the wifi antenna, increasing it will just give you a hot phone and short battery
Click to expand...
Click to collapse
Isnt this phone hot already?
Pretty sure this is a dead end, even if pa0maxpwr is set to 0, wifi works the same as always
Well, it worked with three other testers, some friends of mine that found the same problem. If you're facing this, try and feedback me. Just want to make sure that I've helped someone.
This guide is for those who have the 0% battery issue, found the fix by Bazoocaze (thanks a lot !!!) and are experiencing some quick battery drain. If you're not, then you can go read something else In two or three weeks of testing, I believe that this does not have something related to the ROM that we're using. The processes on background and the use of CPU is relative, but maybe a process is using too much energy, and if we keep the energy level on a low status, I think this process won't have so much energy to use. And maybe the kernel, or the kernel's governors are affecting something, not sure of this last one. I've also concluded that this don't have anything to do with the Wi-Fi modules, because I've already tried that fix, and it drains pretty quick anyway, some believe that there is a bug affecting the Wi-Fi, and it doesn't turn off, even if we turn it off on the menu.
First of all, if you haven't find the fix, read this: http://forum.xda-developers.com/showthread.php?t=1312398
You can also use the DooMKerneL ICS v4 that DooMLorD developed, and it already has the patch built-in (I recommend for this guide): http://forum.xda-developers.com/showthread.php?t=1520654
1 - Flash the kernel, the one of Bazoocaze or the DooM Kernel
2 - Turn on your phone, normally, make all your configs, and do a little test, BEFORE following this guide. See how many time your battery can hold on. If you feel that it's going out too fast, keep going on the guide.
3 - For this operation, I suggest you buy or download the free version of SETCPU, never forget that name. NoFrills didn't work very well to me..
4 - Overclock, if you want and if you're using DooMKerneL. Keep the MHz min on 364 (will explain later)
5 - Go to the profiles tab and press the ''plus'' button. Change the MHz max to 768 and keep the min at 364. In profile, select Screen Off, and change the governor to powersave or smartass and set priority to 100%
6 - Save it, and press Enable and Notifications on the bottom of the screen.
7 - Now test it for some time. Try not to keep your screen always on, as it ''cancel'' the effect of this guide.
Explanations:
a) The reason to keep the min MHz at 364 is that you won't face stuttering in the screen on/off, because the app will only change the max value, and not the min value, which makes the system still work fine (I believe, if some dev could correct me..). It behave better in AOSP alike roms.
b) NoFrills didn't give me the same results as SetCPU, that's why I'm recommending SetCPU. Make some effort to buy the Pro app.
c) The main trick is to reduce the power usage and capacity when the screen is off, because you don't use your phone 100% of the day, and because the process that may exist (mentioned above) would not use the whole capacity of the energy and the CPU as well. That's why it works. At least worked for me.
d) There is absolutely no hardware of software issue if you try this guide, you can uninstall the SetCPU app and use kernel other than DooM's. It's safe and quick, if it doesn't work, you can always revert everything.
Please, if you want to try this guide, give me the feedback. As I've said, I just want to confirm that theory and make sure that I've helped someone.
Thanks Bazoocaze and DooMLorD for being life savers!!!!!!!!
Bye
Thanks for your help
Sent from my LT18i using xda premium
Hi all, I know there are threads already created for questions etc but I've an extensive list of them and I don't think its appropriate to spam them in someone else's thread. And I'll update the first post of the answers and replies I've received for the questions I've posted!
My phone's information: will5's MIUI ROM 2.5.25 GB 2.3.7
My list of questions
Android OS
::Hard rebinding hard keys::
Is that possible? My power button recently got damaged and its really tough to press the power button now which is quite a problem, is there any way to rebind the power button to say the camera button? (specifically the 2nd-click of the camera button, not the first click (focus)) MS2Toolbox is able to wake screen with the camera button but thats just soft-sided and I need to hard bind for turning on the phone and using the recovery etc... :crying:
::Allow app to stay active when screen-off and when not in foreground:: http://forum.xda-developers.com/showpost.php?p=29658020&postcount=95
I want to let my app, specifically Opera Mobile, to be constantly active as I run a script (user javascript) on it which repeats its function periodically. Is there a way to keep it active throughout deep-sleep, or when in the background? Currently its working well when I switch the screen off as long the app was in the foreground. The script and Opera Mobile still runs perfectly and I do not experience battery drain (weird). I have been doing so for the past few months and it takes probably only 30% of my battery overnight when I sleep despite the periodic data connection. However, this didn't happen on the MIUIv4 ROM when I tested it. The app is 'frozen' or suspended, it seems, the moment I switch the screen off. Tried apps which disabled deep sleep etc but didn't work. Any ideas?
Overclocking
::What are the default VSELs for the respective frequency for MS2?::
I know there's one here http://forum.xda-developers.com/showpost.php?p=11620994&postcount=1 by santiemanuel, but it gives VSELs WAY above those I'm using or the defaults from MS2Toolbox. Say, for 300MHz, the stock vsel is 33 and 30 is considered unstable. How ever the default in MS2Toolbox for that frequency is 17 if I'm not wrong. I'm using that at the moment and it seems to be running fine (used powersave governor to enforce 300MHz to test it out). Just to confirm, should I really follow that table?
WiFi
::Changing Milestone 2's WiFi MAC address::
Hi guys, I've been trying to look for a way to change my M2's MAC address but have not been able to get it to work.
I've googled up for methods but the common ones do not work.
Tried so far:
- The nvram.txt file
Can't find it in the usual folders stated.
- busybox ifconfig tiwlan0 hw ether <MAC>
- busybox ip link set dev tiwlan0 addr <MAC>
Tried these two commands but didn't work either in terminal emulator. Even did the off-on-immediately spam commands but no luck.
Unsorted
Code:
http://forum.xda-developers.com/showpost.php?p=29675172&postcount=905
::SOLVED::
Overclocking
::How do I check the current VSEL and frequency at any point in time?::
I'm trying to underclock and ultra-undervolt to save as much battery as possible and want to know how's the selected governor working in order to manually optimize the settings to my preferences.
::How do I know its an unstable VSEL?::
Q: Quite vague a question but... as said in the first question, I'm running 300MHz at a VSEL of 17 instead of 33, nearly half of the stock. How would I be able to tell if its unstable? When I'm running in powersave governor, it shows that the 'system' process stopped responding at boot and I've the wait/close option, but after selecting wait the dialog disappears and the phone still works as per usual. However its very sluggish, clearly because of the underclock. Regardless, does the system process being unresponsive at the start shows it is unstable?
A: djlooka via PM
djlooka said:
...My suggestion is: try with that setvsel app for defy (see my answer in the CM9 thread) which comes with a useful mini-stress tester app (you can install it from within the main OC app). It can stress test every single freq step, so you can find its 'sweet-spot-vsel'.
One could also think that there's some advantage in fine tuning the middle steps. IMHO it's wasted time
After some days of tweaking, I realized that our phone will stay in the two the middle steps (combined) for less than 5% of the time. So even if you could save some % of the power by losing 1 or 2 vsel points (let's say 10% of the original vsel), the "on the road" gain would be infinitesimal (10% x 5% = 0.5%).
Anyway it's fine to OCD a bit even about those 2 steps
My final word is: find the lowest possible vsel for both the top and bottom freqs by stress testing. To be extra careful, raise them by one point for rock solid.
E.g.: 300-22 is the best combo for my lowest step -> I put 300-23, and so on.
Click to expand...
Click to collapse
::3 steps shown in the bootloader but 4 shown in MS2Toolbox::
Q: This has been bugging me recently. I've read recently that the M2 has 4 steps for its CPU. So the CPU actually follows the 4 steps shown in MS2Toolbox or the 3 in the bootloader? Note: When I change the values in the bootloader, the values changes respectively in MS2Toolbox for the 2nd,3rd,4th rows (did not tick auto apply in M2T to prevent overlaps with bootloader settings). But the 1st row shows values lower than the one in the 2nd row automatically.
A: djlooka @ http://forum.xda-developers.com/showpost.php?p=29806494&postcount=908
djlooka said:
...Our phone, instead has 4 steps (300, 600, 800, 1000 MHz - the same as the Defy+).
AFAIK, when you set a configuration which allows only 3 steps (in the bootmenu), the hw internally adjusts to have the last 2 steps equal (e.g. 300, 600, 800, 800 MHz).....
Click to expand...
Click to collapse
Applications
MX Player - Does not require codecs. If it requests for ARMv7 NEON codec, get the NEON version of the player instead.
Hey guys, my ZenFone always has a red cellular network after flashing any custom rom. Only on stock rom it's fine. It's always red no matter where I go, and it's draining a lot of battery.
So on another day, I turned on airplane mode and left it overnight. And then when I checked my phone in the evening, it drained a lot. But towards the end it was shown to be awake, which caused a huge sudden drain.
I have Greenify which prevents background processes, but I doubt Greenify itself takes up much battery.
Anyway to figure out what's causing this problem?
try delete batery cache using app, you can download it from play store
kihope12 said:
try delete batery cache using app, you can download it from play store
Click to expand...
Click to collapse
Which app? Couldn't find... Does wiping cache partition help?
ShinraTensei04 said:
Which app? Couldn't find... Does wiping cache partition help?
Click to expand...
Click to collapse
battery calibration app, you can find it on play store
ShinraTensei04 said:
Which app? Couldn't find... Does wiping cache partition help?
Click to expand...
Click to collapse
Calibrate your battery . (Simply use any app from play store that can do it )
For red bars : put on 2 sims it will solve the problem .
For wake : use wakelock detector or any similar app and see which app is keeping ur device awake . Force stop that or uninstall it .
Greenify : you can check ur battery stats for Greenify to see how much it consumes (use xposed based feature , its feature rich )
Also try to change your governor it will help you extend few mins of usage . (Use kernel aduitor)
Thank you.
Boomshiva said:
Calibrate your battery . (Simply use any app from play store that can do it )
For red bars : put on 2 sims it will solve the problem .
For wake : use wakelock detector or any similar app and see which app is keeping ur device awake . Force stop that or uninstall it .
Greenify : you can check ur battery stats for Greenify to see how much it consumes (use xposed based feature , its feature rich )
Also try to change your governor it will help you extend few mins of usage . (Use kernel aduitor)
Thank you.
Click to expand...
Click to collapse
Thank you for replying.
-I'm charging my phone to 100%, will update results after calibrating.
-So even after removing second sim card the red bass won't come back?
-I think I found what caused my device to be awake: Kernel Adiutor. I switch off 2 cores of my CPU using this, to temporarily fix the freeze issue(unlocked bl), but after about 20 minutes I'm unable to switch those cores back on without a hard reboot. Leaving then switched off overnight caused a huge drain, as shown below.
- Greenify doesn't use much at all.
- Governor changing is something I feel will lead to the same result as switching off cpu cores.
EDIT: The pic shows Wi-Fi was on the entire time, but in fact it was switched off the whole time... wonder why
EDIT 2: wakelock detector doesn't work, says 'failed to perform task at the moment, try again later' as soon as i open it.
ShinraTensei04 said:
Thank you for replying.
-I'm charging my phone to 100%, will update results after calibrating.
-So even after removing second sim card the red bass won't come back?
-I think I found what caused my device to be awake: Kernel Adiutor. I switch off 2 cores of my CPU using this, to temporarily fix the freeze issue(unlocked bl), but after about 20 minutes I'm unable to switch those cores back on without a hard reboot. Leaving then switched off overnight caused a huge drain, as shown below.
- Greenify doesn't use much at all.
- Governor changing is something I feel will lead to the same result as switching off cpu cores.
EDIT: The pic shows Wi-Fi was on the entire time, but in fact it was switched off the whole time... wonder why
EDIT 2: wakelock detector doesn't work, says 'failed to perform task at the moment, try again later' as soon as i open it.
Click to expand...
Click to collapse
1: if you remove SIM then yes red bars will come .
So insert both the sims that's the fix .
2:read about different governors ,it will help you understand them , as you mentioned about turning off cores that was simply HOTPLUG governor (my guess ), yes it causes huge battery drain in ZenFone . Try other governor ( yankactive,wheatley, conservative x ........)
3:I think your Wi-Fi is in scanning mode always , so suggest you turn that off .
To turn that off simply get into location setting , tap on the 3 vertical dot (options ) , there would be scanning option set according to ur preference .
Hope this would help you .
Boomshiva said:
1: if you remove SIM then yes red bars will come .
So insert both the sims that's the fix .
2:read about different governors ,it will help you understand them , as you mentioned about turning off cores that was simply HOTPLUG governor (my guess ), yes it causes huge battery drain in ZenFone . Try other governor ( yankactive,wheatley, conservative x ........)
3:I think your Wi-Fi is in scanning mode always , so suggest you turn that off .
To turn that off simply get into location setting , tap on the 3 vertical dot (options ) , there would be scanning option set according to ur preference .
Hope this would help you .
Click to expand...
Click to collapse
-Is there no way to deactivate 2nd sim?
-I'm not using any governor, as shown below.
-My Wi-Fi scanning is switched off, as shown below.
ShinraTensei04 said:
-Is there no way to deactivate 2nd sim?
-I'm not using any governor, as shown below.
-My Wi-Fi scanning is switched off, as shown below.
Click to expand...
Click to collapse
1: In cm based roms second sim cannot be deactivated (known bug )
2: Suggest you to turn on all the cores .and use the default governor .
3: Try turning on and then off the Wi-Fi scanning option .
4: Also you can perform a clean install of the Rom (if nothing helps and send a logcat to the Rom developer)
Boomshiva said:
1: In cm based roms second sim cannot be deactivated (known bug )
2: Suggest you to turn on all the cores .and use the default governor .
3: Try turning on and then off the Wi-Fi scanning option .
4: Also you can perform a clean install of the Rom (if nothing helps and send a logcat to the Rom developer)
Click to expand...
Click to collapse
right, and i want add
@ShinraTensei04
5: You use MM rom so your batery will work (keep) less time then LL (MM is higher obout two version of android then stock LL)
kihope12 said:
right, and i want add
@ShinraTensei04
5: You use MM rom so your batery will work (keep) less time then LL (MM is higher obout two version of android then stock LL)
Click to expand...
Click to collapse
That wasn't the problem, the problem was that my battery suddenly drained due to my phone being awake with screen still off, but thanks for replying anyway.
So battery calibration did nothing. And it seems the cellular signal strength being red is something of a bug for RR for the Zen5, but the person said it doesn't impact battery at all. But in my case it does, it causes over 300 mAh drain in a day.
Update
Lenovo fixed the issue in the latest update with my initial method which was switching off the CABC in the backlight controller which gives us a brightness boost. So obviously it is not dangerous.
Old Message:
So having achieved root, I was looking into the easiest of the issues. Some call it flickering. The "feature" is called CABC and is supposed to save battery. But obviously this comes at a cost of the display constantly adapting the brightness to the content which can cause flickering depending on what you have on the screen.
With root this can be switched off. Alternatively a new kernel could solve this without root. In both cases an unlocked bootloader is still required.
Instructions:
Use a build.prop editor form the Playstore
Edit the variable "ro.qualcomm.cabl=2" and set it to 0. CAUTION this modifies the system partition. If you want to receive OTAs in the future you will have to flash the system partition with an original image or backup.
Reboot
Technical details:
There are three places where CABC can be switched off:
In the build.prop
In the device tree blob in the boot image/kernel. Specifically the DSI switch on commands in the LCD panel description contain the enabling of CABC
In the LCD backlight driver /sys/devices/soc.0/78b6000.i2c/i2c-2/2-002c -> could be dangerous because it increases brightness and the voltages in the backlight controller
matshias said:
So having achieved root, I was looking into the easiest of the issues. Some call it flickering. The "feature" is called CABC and is supposed to save battery. But obviously this comes at a cost of the display constantly adapting the brightness to the content which can cause flickering depending on what you have on the screen.
With root this can be switched off. Alternatively a new kernel could solve this without root. In both cases an unlocked bootloader is still required.
I attached an Automate flow which disables CABC and guess what we get a brightness bump of about 20%. Now the maximum brightness of the display is even a bit brighter than my old Yoga Tab 2 and should be on par with the 3 pro
Make sure that Automate runs on system startup and has root enabled.
Technical details:
There are two places where CABC can be switched off:
In the device tree blob in the boot image/kernel. Specifically the DSI switch on commands in the LCD panel description contain the enabling of CABC
In the LCD backlight driver /sys/devices/soc.0/78b6000.i2c/i2c-2/2-002c
It turns out that if you disable the latter CABC is off even without modifying the former. Of course this requires ROOT to change. This could also be done in the kernel, but would need either a recompile or modifying the init.rd
Click to expand...
Click to collapse
Thanks Now only audio sync issues left for me and tablet will be perfect.
Have you compared the battery performance with and without CABC disabled?
Ashili said:
Have you compared the battery performance with and without CABC disabled?
Click to expand...
Click to collapse
No, these battery life tests take a long time, which I don't have Time is better spent looking into the other issues. It shouldn't be too much of a difference.
matshias said:
No, these battery life tests take a long time, which I don't have Time is better spent looking into the other issues. It shouldn't be too much of a difference.
Click to expand...
Click to collapse
Yap, I think so. The battery life is long enough. Thank you.
I would think as long as you manually adjust brightness to match your content, you'd get similar results.
I modified the thread to use a less invasive method. I am having issues with my tablet. I am not sure it was caused by this mod but just to be safe I recommend everyone not to use it any longer.
what kind of problem?
chuwq1038 said:
what kind of problem?
Click to expand...
Click to collapse
Everything works (also the display) but the battery drains and the back of the tablet gets warm even when the tablet is switched off. Could be completely unrelated to the mod, but who knows.
With latest official update I have a battery drain issue too. 15% down overnight...