Related
Hey there fellow modifiers!
I have gathered the best tips and tricks to get the best battery life on our loved LG G6.
All this methods were made on a H870S non rooted phone so anyone can do it.
Post gets constantly updated with more tricks, so keep coming!
Reduce resolution to 1080p and adjust DPI for comfortable view: (AOD gets messy so you are better off disabling it)
1) Connect phone via adb and activate debugging.
2) Execute this command and select the resolution you want.
"adb shell wm size 1080x2160" THIS MAKES YOUR PHONE RUN IN 1080 NATIVE RESOLUTION.(tested and works wonders)
"adb shell wm size 720x1440" HAVEN'T TESTED THIS ONE, IF YOU DO COMMENT.
If you need the original resolution just run:
"adb shell wm size 1440x2880"
3) Run this command to adjust DPI(screen scaling).
"adb shell wm density 500" SLIGHTLY SMALLER.
"adb shell wm density 400" EVEN SMALLER. THE ONE I LIKE WHILE USING 1080P
"adb shell wm density 300" COULD WORK GOOD WITH 720P.
If you need the original resolution just run:
"adb shell wm density 640" THE ORIGINAL WITH 1440P.(or the three options on "app scaling are 544/640/720)
DON'T TOUCH APP SCALING BECAUSE IT WILL MODIFY THIS.
4) Reboot if needed.
Deactivate/Debloat the phone as much as possible.
Just go to settings > Apps and start searching for deactivable system apps.
Secret menu
Disabling LDB
1) Open Dialer and type "*#546368#*870#" where "870" is your model number.
A "secret menu" should appear, if not search for your secret code.
2) Go to "SVC Menu"
3) Go to "LDB"
4) Untick the "enable". It should then say below it "MLT will not run after booting.
DON'T CLOSE THE MENU STILL.
Disabling Log Service.
1) Go back from the previous menu.
2) Go to "Log Service"
3) Tap 2 times on "Log enable". It should enable and then disable again all logs, cleaning them in the process.
4) Exit menu.
Disable Always on Display.
Settings > Display > Always on Display.
Disable Wifi/Bluetooth scanning while off.
Go to Settings > location> three dots > scanning > Bluetooth scanning and Wifi scanning.
Disable "Find my Device" under Phone Administrators if you don't use it.
Settings > Fingerprints & Security > Phone Administrators
Disable Excess "Trust Agents".
Settings > Fingerprints & Security > Trust Agents. (I personally never use nor "LG Face recognition" or "Smart Lock (google) so i disable them)
Disable Alarming Flash if On.
Settings> Accessibility> listening> Alarming flash
Use Greenify to "Doze" the Battery-Hog Apps.
Just download "Greenify" from play store and follow instructions given on app.
Turn on Battery Saver.
AOD doesn't seem to work at 1080p
Sent from my LG-H870DS using Tapatalk
I don't really know, i disabled ir.
Screen-on drain at 1080p is 22.7%/hr, about 3% improvement over the original resolution. I can't upload my screenshot for some reason
Sent from my LG-H870DS using Tapatalk
Is the guide for changing 1080 resolution also works for unrooted phone
penglengpung said:
Is the guide for changing 1080 resolution also works for unrooted phone
Click to expand...
Click to collapse
Yeh, i did it on mine and is not rooted.
I am getting easily close to 7hs SOT and 0% drain during 13hr night.
monose1 said:
Yeh, i did it on mine and is not rooted.
I am getting easily close to 7hs SOT and 0% drain during 13hr night.
Click to expand...
Click to collapse
Interesting... 2% during night with flight mode ON (about 8h). With AOD INm flight mode ON it takes during 8h 4%.
Do you have stock software and stock launcher (with or without dock?).
Can I run these commands in a terminal with root?
Thank you for this! lowering the resolution also seems to make the phone that little bit snappier. Any ideas how to fix recent apps list? it shows zoomed in previews (likely ignoring the set density). This also applies to AOD and boot up animation in my experience.
RimvydasT said:
Thank you for this! lowering the resolution also seems to make the phone that little bit snappier. Any ideas how to fix recent apps list? it shows zoomed in previews (likely ignoring the set density). This also applies to AOD and boot up animation in my experience.
Click to expand...
Click to collapse
Yees, makes phone snappier. Have you tried rebooting? I set mt density to 400. I didnt even noticed multitask being ablittle zoomed in, i think it wont have a solution. Boot animation always happens, i remember my old lg g2 had that, nothing tondo with that. But in my opinion is worth.
basicreece said:
Can I run these commands in a terminal with root?
Click to expand...
Click to collapse
Yes, just search for the desire commands and run the in terminal. With root you could do it with some apps also.
monose1 said:
Yeh, i did it on mine and is not rooted.
I am getting easily close to 7hs SOT and 0% drain during 13hr night.
Click to expand...
Click to collapse
I wish you could make a tutorial video on how to do it..??
penglengpung said:
I wish you could make a tutorial video on how to do it..
Click to expand...
Click to collapse
If you follow this guide you can get that battery life.
What did tou have some issues? The commands? I could look into a tutorial.
monose1 said:
If you follow this guide you can get that battery life.
What did tou have some issues? The commands? I could look into a tutorial.[/QUOTE
I don't know how to set up adb initially, but Googled it and found some instructions... All ok now..??
Click to expand...
Click to collapse
penglengpung said:
monose1 said:
If you follow this guide you can get that battery life.
What did tou have some issues? The commands? I could look into a tutorial.[/QUOTE
I don't know how to set up adb initially, but Googled it and found some instructions... All ok now..
Click to expand...
Click to collapse
Awesome man, if you have any doubts just PM me.
Click to expand...
Click to collapse
the caller dialer appears narrow and long
Does someone know what LDB is good for? I tried googling it but found no real answer. I don't like disabling things I don't know the purpose of. Thanks for your guide btw!
Thanks. I will try it
Thought i'd add to this too:
Enable 'conserve memory'
Settings > Smart Doctor > Memory > 3 dots > Conserve memory
Select the apps you don't want running in the background.
This works so well. I usually get only 2-3 hrs of SOT with normal settings, but now i strongly believe i can easily reach around 5-6hrs with this method. Screen on avg used to be around 20%/hr, now its around 10%/hr which is astonishing. Thank you!
So, moving from s8+ then note8 (obviously 7.1) i used to use an apk of black nav bar, once installed then a solid black color shows up as a color option..
So now with s9+ in my hands, i installed it and it didn't work, am assuming because its oreo, any idea if there is any solution (other than substratum) to black the navbar..
+1 It's annoying.
im using navbar apps and it works fine on the s8 running oreo so should work on s9+ as well, still havent got mine so cant test it.
Code:
https://play.google.com/store/apps/details?id=pl.damianpiwowarski.navbarapps&hl=en
You can also just use an adb command:
https://www.google.de/amp/s/www.xda-developers.com/change-galaxy-s8-navigation-bar-color/amp/
corwin_amber said:
You can also just use an adb command:
https://www.google.de/amp/s/www.xda-developers.com/change-galaxy-s8-navigation-bar-color/amp/
Click to expand...
Click to collapse
That's exactly what i was looking for, thank you, will give it a try tomorrow..
I tried this and am unable to inject black as an option. Possibly that Oreo is prohibiting this (for now).
I used an adb command I saved from earlier (S8+ Times) and it worked just fine:
adb shell settings put global navigationbar_color -16777216
adb shell settings put global navigationbar_current_color -16777216
adb shell settings put global navigationbar_use_theme_default 0
corwin_amber said:
I used an adb command I saved from earlier (S8+ Times) and it worked just fine:
adb shell settings put global navigationbar_color -16777216
adb shell settings put global navigationbar_current_color -16777216
adb shell settings put global navigationbar_use_theme_default 0
Click to expand...
Click to collapse
I will try this one later today.
corwin_amber said:
I used an adb command I saved from earlier (S8+ Times) and it worked just fine:
adb shell settings put global navigationbar_color -16777216
adb shell settings put global navigationbar_current_color -16777216
adb shell settings put global navigationbar_use_theme_default 0
Click to expand...
Click to collapse
Isn't this the same as the link above has, except explains different color values? I still can't figure out why Samsung thinks the users don't want black or be able to choose whatever he/she wants.
It is probably the same, nevertheless it worked for me.
corwin_amber said:
I used an adb command I saved from earlier (S8+ Times) and it worked just fine:
adb shell settings put global navigationbar_color -16777216
adb shell settings put global navigationbar_current_color -16777216
adb shell settings put global navigationbar_use_theme_default 0
Click to expand...
Click to collapse
These 3 commands worked. It shows as an "off white" in the Nav Bar settings but the bar itself is black as expected. Thank you!! Bring on the burn-in!
WorldIRC said:
These 3 commands worked. It shows as an "off white" in the Nav Bar settings but the bar itself is black as expected. Thank you!! Bring on the burn-in!
Click to expand...
Click to collapse
Sell!
I wanted to do this but was then warned off it as it can cause bad burn-in. Is this true?
The adb commands worked perfectly with me, so far..
CuBz90 said:
I wanted to do this but was then warned off it as it can cause bad burn-in. Is this true?
Click to expand...
Click to collapse
Black means the pixels are off, so there is no burn in.
Ramer said:
Black means the pixels are off, so there is no burn in.
Click to expand...
Click to collapse
But whilst the background is black, the button symbols themselves are white/grey making them pixels lit. If those pixels are lit all the time whilst the pixels around it are off, it's more likely to burn into the screen as those pixels are being used more.
CuBz90 said:
But whilst the background is black, the button symbols themselves are white/grey making them pixels lit. If those pixels are lit all the time whilst the pixels around it are off, it's more likely to burn into the screen as those pixels are being used more.
Click to expand...
Click to collapse
True, but isn't every phone like that?
Ramer said:
True, but isn't every phone like that?
Click to expand...
Click to collapse
All phones with oled screens yes.
Not working for me, still all my colors are the stock Samsung ones and nothing closely resembling black
I read somewhere, I really can't seem to find the article that Samsung did this on purpose. To help prevent burning And to keep screen degradation uniform. I assume it's because the black bar is essentially no pixels meaning they're not on. Meaning they're not being used as much as the rest of the phone's display thus they will degrade slower and eventually give the appearance of burn in. Makes sense to me I guess
I have the amazfit stratos 2. I installed a custom watchface.
The problem that i'm facing is that the watchface is different when locked and when unlocked. I would like it to be like on the photo from the unlocked screen. You can see a green shade on the unlocked state. When it's locked it's only a sort of green line without any shade.
Usually most watchfaces go into 8 colours mode when screen is locked, it was meant to save battery (?) and increase contrast, but I think it was also some limitation of the initial API used to display watchfaces. Every custom WFZ that is available on SAWFB site will display this behaviour. Some built-in ones won't look as bad if the background is only black or white. To avoid this, without keeping the screen on all the time and killing battery, you can personalise the WFZ by copying the same background to the 8c folder (WFZ is actually a zipped folder) or use a Java (APK) watchface.
lfom said:
Usually most watchfaces go into 8 colours mode when screen is locked, it was meant to save battery (?) and increase contrast, but I think it was also some limitation of the initial API used to display watchfaces. Every custom WFZ that is available on SAWFB site will display this behaviour. Some built-in ones won't look as bad if the background is only black or white. To avoid this, without keeping the screen on all the time and killing battery, you can personalise the WFZ by copying the same background to the 8c folder (WFZ is actually a zipped folder) or use a Java (APK) watchface.
Click to expand...
Click to collapse
Thanks for your answer. I've checked what you suggested. But like you can see in the pictures it was already like this. The weird thing is that the first time i installed this watchface everything was fine. Than i modified it to display the temp instead of the total km. When i installed it , i notified this behavior. So i installed the original one again and still the same weird behavior.
Try using these command on adb, with the watch connected to the computer, this will reset the launcher and watchfaces cache (root not needed):
Code:
adb wait-for-device
adb shell rm -rf /sdcard/.watchfacethumb
adb shell pm clear com.huami.watch.launcher
lfom said:
Try using these command on adb, with the watch connected to the computer, this will reset the launcher and watchfaces cache (root not needed):
Code:
adb wait-for-device
adb shell rm -rf /sdcard/.watchfacethumb
adb shell pm clear com.huami.watch.launcher
Click to expand...
Click to collapse
Sadly that didn't work. I've shared the original file maybe you or someone else can check it out to see if the same thing happens on there watch?
Same thing... And now I realize that I missed one thing: you are using Stratos, that comes with WOS2 (Watch OS 2.0), and it doesn't use the "8c" folder anymore, but some kind of color mapping/dithering in another folder named "26w". Even using a black & white PNG in 8c folder, WOS2 removes the dithering in my tests.
If you are into graphics and want to try to figure out how it works, I am attaching one of the stock WFZ for Stratos, so you can see what I meant above.
This kind of dithering from another stock WFZ seems to work better, but I don't know how to make them.
lfom said:
Same thing... And now I realize that I missed one thing: you are using Stratos, that comes with WOS2 (Watch OS 2.0), and it doesn't use the "8c" folder anymore, but some kind of color mapping/dithering in another folder named "26w". Even using a black & white PNG in 8c folder, WOS2 removes the dithering in my tests.
If you are into graphics and want to try to figure out how it works, I am attaching one of the stock WFZ for Stratos, so you can see what I meant above.
Click to expand...
Click to collapse
Thanks , i'll try this one out. I wish there was an easy programme that we could use to make or edit existing wachtfaces. The one i've send you looks very nice but only when not in locked mode sadly. I would be happy if someone gets this working.
Hi OP, me too interested in this topic... Got Stratos yesterday and cant really understand why they impact screen awesomeness in this way...
Also interested in this topic. If.we can get the lock/standby mode watchfaces look better would be a great win for this cool watch.
Sent from my Redmi 5 Plus using Tapatalk
It can't be done.
The watch in standby switches the display to the 8 color mode and you can't do anything about it.
It is one of the reasons why it used so little energy
fzelle said:
It can't be done.
The watch in standby switches the display to the 8 color mode and you can't do anything about it.
It is one of the reasons why it used so little energy
Click to expand...
Click to collapse
8bit mode is OK - but dont shut off antialiasing....
My Garmin FR935 screen is 240x240, has ****ty colors (64) but looks WAY BETTER due antialiasing constantly on and has 3weeks batt life if connections are off (I just upload stats over wifi when I am home)
So technically 8bit mode is OK but dont shut off antialiasing - as screen really turns crap (until you move your hand to turn antialiasing on)...
phnikola said:
8bit mode is OK - but dont shut off antialiasing....
My Garmin FR935 screen is 240x240, has ****ty colors (64) but looks WAY BETTER due antialiasing constantly on and has 3weeks batt life if connections are off (I just upload stats over wifi when I am home)
So technically 8bit mode is OK but dont shut off antialiasing - as screen really turns crap (until you move your hand to turn antialiasing on)...
Click to expand...
Click to collapse
I wrote 8 color mode, not 8 bit.
So apparently the 1 III suffers from the same issues as its Sony Predecessors... The Flashlight is very bright when you use it as camera flash, but when you turn on the flashlight, its artifically throttled to idk, prevent overheating?
So for the older Xperias there were ways to modify flashlight configs and librarys. However, I havent found a way to edit the current parameter for the flashlight on the 1 III. For the 5 II the GodlyTorch App seemed to work, according to a report in https://forum.xda-developers.com/t/...ness-fix-torch-light-not-photo-flash.4203293/, but that doesnt want to work on my 1 III (I have Root)
Now the question: Can someone find the parameters to increase Flashlight LED Current via Magisk Module, XPosed/LSPosed Module or manual edit? I'd be even willing to donate to a kind developer who builds a usable flashlight mod for the 1 III.
Thanks in advance.
When flashlight is on and your device is rooted, you can change the value of
Code:
/sys/class/leds/led:torch_0/brightness
/sys/class/leds/led:torch_3/brightness
(There are two flash LEDs)
The max value you can set is given by the max_brightness file in the same directory.
I didn't find a way (yet) to apply this by default, you have to have the flashlight running in order to change its brightness that way.
However, I do warn you that I am not responsible in any way if using your LED at full power causes damage to your device.
MK73DS said:
When flashlight is on and your device is rooted, you can change the value of
Code:
/sys/class/leds/led:torch_0/brightness
/sys/class/leds/led:torch_3/brightness
(There are two flash LEDs)
The max value you can set is given by the max_brightness file in the same directory.
I didn't find a way (yet) to apply this by default, you have to have the flashlight running in order to change its brightness that way.
However, I do warn you that I am not responsible in any way if using your LED at full power causes damage to your device.
Click to expand...
Click to collapse
Thanks for this info, working fine for me!
I played a bit around with this and tested the brightness values with 150; working fine in terms of short term heat development.
Edit 2: After a few days I start to notice a very slight discoloration of the diffusor with a value of 150. Its not affecting anything and barely visible, but I'd recommend to go lower than 150, because I suspect the LED may get too warm for the diffusor. I changed the guide to use 30 for now (which equals double the brightness compared to stock), please test your values for yourself, its probably better to not exaggerate it.
Make sure you type in the values right! Too high values and the LED Diffusor may melt, or the LED might die. Do this modification at your own risk, no matter at which brightness you target! I am not responsible for side effects resulting from the mod.
With Terminal Shortcut Pro and assigned Root Priviliges I made myself a Home Screen Icon that will boost the values for me in the current "Torch session" once the LED is turned on before. Other terminal emulator apps will work too.
In the Shortcut I set Run with Root and used the following command
Code:
echo 30 >> /sys/class/leds/led:torch_0/brightness && echo 30 >> /sys/class/leds/led:torch_3/brightness
Basically just a command that writes the 30 brightness value to the 2 files.
If someone can find a terminal command that turns on the flash in the first place, we could combine the commands to potentially make a simple but working replacement quick settings for the torch.
Edit: Thanks to the XDA Community and a Tool I was able to recreate the Torch experience with a Quick setting
You need https://play.google.com/store/apps/details?id=com.quinny898.app.customquicksettings
You have to buy the premium in app purchase for 1,29€ to unlock Root Command Running. Then you configure your quick setting (choose the Advanced -> Root Command under Preset) and paste the following script (credits to https://forum.xda-developers.com/t/increasing-torch-power-with-root.3637773/post-73098701, modified by me for 1 III)
Code:
#!/system/bin/sh
toggle=$(cat /sys/class/leds/led:switch_0/brightness)
if [ "$toggle" = "0" ];then
echo 30 > /sys/class/leds/led:torch_0/brightness
echo 30 > /sys/class/leds/led:torch_3/brightness
echo 1 > /sys/class/leds/led:switch_0/brightness
echo "on"
else
echo 0 > /sys/class/leds/led:torch_0/brightness
echo 0 > /sys/class/leds/led:torch_3/brightness
echo 0 > /sys/class/leds/led:switch_0/brightness
echo "off"
fi
Once again, make sure you type in the values right! Too high values and the LED Diffusor may melt, or the LED might die. Do this modification at your own risk, no matter at which brightness you target! I am not responsible side effects resulting from the mod.
Then you get rename the toggle, give it a nice Torch Icon and set the color to grey. It will function like the normal quick setting: Tap once, it turns on, Tap again, turns off. Even works locked.
Good luck and best regards.
If you want to use the Google Assistant Button as a torch toggle and also have Quick Settings Toggle (sadly its always toggled on) i found an app that can do both.
You need:
LSposed/Xposed
Root Shell access (adb shell)
Xposed Edge pro
Busybox for Android NDK (Magisk Module)
XperiaGAButtonRemap (Magisk Module)
Open a cmd or powershell
execute adb shell
execute su
accept root permissions on your phone
execute vi /bin/torch
press the key i
paste the script:
einhuman197 said:
Code:
#!/system/bin/sh
toggle=$(cat /sys/class/leds/led:switch_0/brightness)
if [ "$toggle" = "0" ];then
echo 150 > /sys/class/leds/led:torch_0/brightness
echo 150 > /sys/class/leds/led:torch_3/brightness
echo 1 > /sys/class/leds/led:switch_0/brightness
echo "on"
else
echo 0 > /sys/class/leds/led:torch_0/brightness
echo 0 > /sys/class/leds/led:torch_3/brightness
echo 0 > /sys/class/leds/led:switch_0/brightness
echo "off"
fi
Click to expand...
Click to collapse
press ESC
type :wq and press ENTER
execute chmod +x /bin/torch
Now you can execute /bin/torch as root and it will toggle the torch with higher brightness values.
In Xposed Edge enable "Keys" toggle and open it. Tap on "+ Add" at the bottom, press the Google Assistant Button, it should be recognized as "KEYCODE_PROG_BLUE", then set the action of either click/double click/long press (whatever you prefer as the torch toggle) to execute a Shell command, enter /bin/torch in the input field and enable the "Root access" toggle.
If you want, you can also set other custom things to the Google Assistant button for the other 2 states.
For the quicksettings menu tap on "Quick settings tiles" in the main menu of Xposed Edge and enable the first tile and open the settings for that tile. Set the action, again, to a shell command, input /bin/torch and enable Root Access. You can set the label to "Torch" and choose the Torch icon found in "Built-in icons". As i already said, the toggle will always be turned on for some reason. It just executes a shell command after all.
Good luck
Amazing, thank you everyone.
However, please let me insist that this may damage your phone if you put values too high... trust me. I accidentally put a brightness of 350 instead of 150 while trying the script in a terminal, and a few seconds were enough for the plastic underneath the glass to melt... Thankfully, it is still transparent so I can still use my flashlight, but no doubt it could have done a lot more damage if I let it run for longer. So please, use this with a lot of care (and double check what you write).
That's why in lots of countries, rooting voids your (hardware) warranty, you can do physical damage to your device so again, please be careful. Thankfully, this plastic bit and even the LED underneath are easily replaceable (the plastic bit is separated from the rear glass and the LED is on a separate ribbon cable). However, there don't seem to be a lot of OEM replacement parts for this phone yet.
Seems like a lot of work for little return and added threat of damage to an expensive phone. I agree that the brightness is dimmer than other phones I have had...but I did a test in a completely dark room and it actually is bright enough to find "whatever" you may be looking for. So I can live with it. Maybe Sony will do something to improve it a little?
jaseman said:
Seems like a lot of work for little return and added threat of damage to an expensive phone. I agree that the brightness is dimmer than other phones I have had...but I did a test in a completely dark room and it actually is bright enough to find "whatever" you may be looking for. So I can live with it. Maybe Sony will do something to improve it a little?
Click to expand...
Click to collapse
Sony could definitely improve it. But it seems like they had a history for compareably dim Flashlights.
I edited my explanation post to adapt lower brightness, because 150 as value starts to slightly discolor my diffusor, so I suspect we should run it lower.
MK73DS said:
太棒了，谢谢大家。
但是，请让我坚持，如果您将值设置为高，这可能会损坏您的。......我相信在终端中尝试手机时，我不小心将恢复设置为 350 而不是 150 ，几秒钟就可以让玻璃下面的恢复正常……幸好还是可以的，所以我可以使用我的手电筒，但有疑问，如果我能运行更长时间，它会请小心使用它（并仔细检查你写的内容）。
这就是为什么在国家/地区，root 导致您的许多（硬件）故障，您可能会再次对您的设备造成物理损坏，请小心。值得庆幸的是，塑料钻头甚至下面的 LED 都可以轻松更换（塑料钻头与后玻璃分离，LED 还位于单独的带状电缆上）。
Click to expand...
Click to collapse
darken5404 said:
Click to expand...
Click to collapse
You can't say I didn't warn you!
Indeed flashlight in mark 3 and older xperias is very bad.
I compared it to an iPhone and it's like day and night. Many aspects xperia brand is suffering like front camera, flashlight, no 21:9 pics, missing 4k 60fps recording in main app with stabilization, poor screen brightness, insufficient battery capacity, no any cooling system (especially at this price there should be vapor chamber or any other advanced cooling and not throttling cpu as a solution...), Not to mention regular software apps like Album, email and others :/
MK73DS said:
You can't say I didn't warn you!
Click to expand...
Click to collapse
I got it fixed through sony aftermarket and has ip68,fixed the screen for me by the way
On android 12 after rebooting the function stops working.
So I got to the area of the phone you guys specified, but as of today, the default values are WAY different that what yall found. Let me take a few screen shots
Here is the systems default peramitors. Any idea why they are so different?
Edit- Okay, so extra piece to the puzzle. When torch is off, the brightness file is 0, but when it is on the file is set to 15.
editing the file while the torch is on does nothing.
Edit 2 - Just wanted to note that for those who just want a demonstration of the changes possible, the fallowing app will do just that
Release v1.4.6 · BRoy98/GodlyTorch
Merge pull request #2 from TheDorkKnightRises/patch Fix LED file path for OnePlus One (bacon), proper device names for OP Merge pull request #3 from TheDorkKnightRises/patch Fix default double-...
github.com
this app needs root. Run it as a HTC 10 and it works just fine. However, I would like to recommend NOT going over the half way point. its VERY bright and will probably kill your LED if you do. You have manual control over the brightness. You can add it as a shortcut in the drop down menu of your phone. simply use the standard torch button, and then click the godly torch button to activate whatever preset you gave it.
Edit 3 - setting the brightness in Godly Torch to 50% Intensity sets the brightness to 135. Given that we know damage starts to happen at 150, I set the brightness in Godly to 15% (under the "toggle Intensity" shown in the screen shot), which brings the brightness to a value of 45. Its easily double as bright. I would not recommend going past this point.
I would say by using godly torch as a HTC 10 worked...mind you I double checked the brightness by just hitting the quick toggle and then messing with godly torch. The lower setting is matching just turning on the quick toggle the higher setting is what I'm comfortable with, but idk how long I'm comfortable running it at that brightness.
BlazingKahn35 said:
On android 12 after rebooting the function stops working.
Click to expand...
Click to collapse
For those on stock who use the assistant button :
If it stops working after reboot, copy the binary file to somewhere safe on your sd card, then using XPosed edge just add a long press gesture to your assistant button that recopys the file from your sd card, then sets the permissions again (make sure to check run as root)
cp /sdcard/torch /bin/ | chmod +x /bin/torch
Just checking in on the status of forcing 90hz. Was disappointed to find there was no way to do it when I purchased the phone.
Is there any way to actually force 90hz at this point? I find that it goes to 60hz about 30-40% of the time depending on type of use despite enabling "force peak refresh rate" in developer options, it's quite annoying.
Thanks
Try this one
Cheers
Tom
Jonnyswboy said:
Just checking in on the status of forcing 90hz. Was disappointed to find there was no way to do it when I purchased the phone.
Is there any way to actually force 90hz at this point? I find that it goes to 60hz about 30-40% of the time depending on type of use despite enabling "force peak refresh rate" in developer options, it's quite annoying.
Thanks
Click to expand...
Click to collapse
Not sure if other reply was an error but forcing 90Hz all the time is simple.
In Developer Options, scroll down to "Force peak refresh rate" & switch it on.
Probably good idea to also go to Settings|Display and turn off "Smooth display".
mannikon said:
Not sure if other reply was an error but forcing 90Hz all the time is simple.
In Developer Options, scroll down to "Force peak refresh rate" & switch it on.
Probably good idea to also go to Settings|Display and turn off "Smooth display".
Click to expand...
Click to collapse
It still drops to 60hz in Maps and any app that uses the Camera. I don't think having smooth display disabled makes a difference when you use the developer option.
Not sure but you can try to set using
adb shell settings put system peak_refresh_rate 90.0
adb shell settings put system min_refresh_rate 90.0
Click to expand...
Click to collapse
That's why I linked to the Optimization topic. The command you mentioned is written there, except use 120.0 (Pixel 6 Pro). On the Pixel 6 it will change to 90Hz or replace the 120.0 with 90.0
But the OP didn't even gave a feedback.
Cheers
Tom
tom1807 said:
That's why I linked to the Optimization topic. The command you mentioned is written there, except use 120.0 (Pixel 6 Pro). On the Pixel 6 it will change to 90Hz or replace the 120.0 with 90.0
But the OP didn't even gave a feedback.
Cheers
Tom
Click to expand...
Click to collapse
I have tried that. That is what I did with my OP7T but it doesn't work on the P6.
This issue is directly related to the Camera being used and Google Maps. I can't believe I am the only one talking about this. It drives me mad. I will literally pay someone to come up with a solution to this problem.
EDIT: I FIGURED IT OUT!!
adb shell settings put system peak_refresh_rate 24.0
adb shell settings put system min_refresh_rate 24.0
Enable 120Hz Refresh Rate in Snapchat, Instagram, GCam Camera
In this guide, we will show you the steps to enable the 120Hz refresh rate in third-party camera apps such as Instagram, Snapchat, and GCam.
www.droidwin.com