THE PROBLEM
To save battery while playing video Tegra intelligently decreases the backlight while increasing color brightness and contrast. Because it monitors on a frame by frame basis the changes are often unnoticable. You basically end up with the same displayed image using less backlight.
Unfortunately it seems to get stuck even after you leave the video and the changes are very noticeable as the changes were specific to the video frame you just left and not your homescreen.
This also may be the cause of some ghosting issues and for some it seems to eliminate any ghosting problems for them.
MANUAL FIX
(will reset at each reboot)
In terminal -
(You may need to type "su" and press enter before entering these commands)
To turn it off
echo "0" > /sys/devices/tegradc.0/smartdimmer/enable
To change how aggressive it is (untested)
echo "#" > /sys/devices/tegradc.0/smartdimmer/aggressiveness
Note: battery life while watching videos WILL decrease if you turn it off or decrease the aggresiveness
AUTOMATIC FIX
Trickster Mod
- has the ability to disable PRISM and set it to disable on boot.
N7scripts.rar
- A collection of scripts compiled by hamdir which, in conjunction with Script Manager (available in the market) will allow you to toggle smartdimmer/PRISM on and off at will.
- You can also use script manager to toggle it at boot if you want.
- Also includes a script to disable 3D scaling which may improve 3D gaming performance (untested)
Thanks to hamdir for his pack of scripts and for convincing me to make a new post for these fixes.
I may use this for other sysfs tweaks... mine for now.
Thanks. Easier to save and flash then manually entering in these values each time I crackflash.
If the T3 can increase the color saturation and gamma while decreasing backlight, wonder if we can increase the colors while leaving the backlight alone. All of the N7s I've played with have a dull washed out look with a warm tone for whites.
Sent from my Nexus 7 using xda premium
does flashing the .zip just delete the PRISM file? cuz when I manually enter the command after flashing it via CWM it doesn't allow me to any more.
"
ROM may flash stock recovery on boot? Fix?
No
.
.
.
.
.
Yes - Disable Recovery flash
.
.
.
+++ Go back +++
which reboots if you "go back" what is this?
-------------------------------------------------------------------------
How do you set up the script? I have script manager and the Scrip.rar saved onto my SD card. Thanks in advance!
player911 said:
Thanks. Easier to save and flash then manually entering in these values each time I crackflash.
If the T3 can increase the color saturation and gamma while decreasing backlight, wonder if we can increase the colors while leaving the backlight alone. All of the N7s I've played with have a dull washed out look with a warm tone for whites.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Messing with the kernel I haven't had any luck. You could ask Morfic. He might be able to make something happen.
Also prism increase color BRIGHTNESS for the most part (you said saturation). That's why the homescreen ends up looking washed out and bright and not oversaturated when PRISM fails to shut off.
Sent from my Nexus 7 using xda premium
sharp2G said:
does flashing the .zip just delete the PRISM file? cuz when I manually enter the command after flashing it via CWM it doesn't allow me to any more.
"
ROM may flash stock recovery on boot? Fix?
No
.
.
.
.
.
Yes - Disable Recovery flash
.
.
.
+++ Go back +++
which reboots if you "go back" what is this?
-------------------------------------------------------------------------
How do you set up the script? I have script manager and the Scrip.rar saved onto my SD card. Thanks in advance!
Click to expand...
Click to collapse
There's no prism file. These tweaks are changing a sysfs value. There's no file. The flashable zip adds an init.d file that runs the manual command at every boot.
In your case CWM is complaining about a file that flashes stock recovery on boot and overwrites CWM. These are completely different things. Let CWM "disable recovery flash" and you'll be good to go.
Sent from my Nexus 7 using xda premium
This is awesome. It definitely needs to be implemented in a ton of ROMs
so does flashing this decrease battery life when watching videos? im confused by op..
awesome post, thx!
yes this fix, completely get rid of the grey levels washout issues!!! and greatly improves the quality of the display, it will cost some battery life, but any boost to this average screen is welcome
now about ghosting it did reduce it a lot but sadly it didn't kill it, i still get the very random occasion of faint LCD ghosting
finally we really need to find out a way to fix the stupid low saturation, in particularly the greens are very low
google....these screen issues, lack of tablet UI and launcher rotation issues, makes want to smash it through the wall
Nice find. Hopefully Google/Nvidia/Asus will fix this in an update.
Thank you very much for this! While I don't own a Nexus 7, I *do* own an Asus TF700T and this problem also exists on it. On the TF700, this "mode" is active all of the time, no matter what you are doing and it is *very* noticeable and distracting, especially when watching videos (but it *is* noticeable everywhere else as well).
Disabling this "Feature" makes the problem go away. At the very least, you can enable/disable as needed now.
Thanks again!
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Hello from Germany,
my Nexus is unlocked and rooted
Terminal:
su
cd /sys/devices/tegradc.0/smartdimmer
./enable
"Permission denied"
change user rights:
chmod 744 enable
(old settings are 644)
./enable
./enable[1]: 1: not found
so where is my fault?
ever since i disabled this gamma destroying feature and my screen keeps getting better and better
starting to fall in love with it really
Riquelme10 said:
Hello from Germany,
my Nexus is unlocked and rooted
Terminal:
su
cd /sys/devices/tegradc.0/smartdimmer
./enable
"Permission denied"
change user rights:
chmod 744 enable
(old settings are 644)
./enable
./enable[1]: 1: not found
so where is my fault?
Click to expand...
Click to collapse
you didn't even enter the command line properly...
Sent from my Nexus 7
sharp2G said:
you didn't even enter the command line properly...
Sent from my Nexus 7
Click to expand...
Click to collapse
Care to post how it should be done then? Might be a little bit more helpful
Also, does this affect battery life overall? Or just while watching movies?
Riquelme10 said:
Hello from Germany,
my Nexus is unlocked and rooted
Terminal:
su
cd /sys/devices/tegradc.0/smartdimmer
./enable
"Permission denied"
change user rights:
chmod 744 enable
(old settings are 644)
./enable
./enable[1]: 1: not found
so where is my fault?
Click to expand...
Click to collapse
You do not "run" the "enable" file. You need to do this:
echo "0" > /sys/devices/tegradc.0/smartdimmer/enable
or
echo "0" > enable (if you are already in that dir).
That will disable the SMartDimmer "feature". Echoing a "1" will re-enable it. I have not noticed any battery life difference....
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
espionage724 said:
Care to post how it should be done then? Might be a little bit more helpful
Also, does this affect battery life overall? Or just while watching movies?
Click to expand...
Click to collapse
yes its an LCD battery saving feature and so disabling it will definitely reduce battery life
choose between battery life or quality display
hamdir said:
yes its an LCD battery saving feature and so disabling it will definitely reduce battery life
choose between battery life or quality display
Click to expand...
Click to collapse
Yes as said in the OP smart dimmer analyzes the video frames and determines whether it can lower the backlight while increasing the color brightness and maintain almost the same image. Lower backlight = better battery life.
Sent from my Nexus 7 using xda premium
After I turned off the dimmer, the screen got a little brighter, so I manually turned down my normal 40% brightness to 30% brightness. So in the end I don't think I'm losing any battery life at all.
Ravynmagi said:
After I turned off the dimmer, the screen got a little brighter, so I manually turned down my normal 40% brightness to 30% brightness. So in the end I don't think I'm losing any battery life at all.
Click to expand...
Click to collapse
I agree - I think any battery life reduction will be *very* minor for most people... I certainly haven't noticed any difference...
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Related
050820121030:
I have use the search button to see how i can lower screen brightness on galaxy note.
i found everywhere mentioning screen filter, it is not i don't like screen filter, but when i take screenshot it will be tinted gray.
so i decide to go to a more elegant way like what atrix 4g user did.
http://forum.xda-developers.com/showthread.php?t=1245332
i tried with my note, i cant find sys/bus/i2c/drivers/lm3532, i decided to check folder with the nearest name, but i can't find it.
so i decided to download linux, mind you i have no idea how to use linux.
i downloaded samsung ics opensource update 4, inside i can't find leds-lm3532.c,leds-lm3532.h,board-mot-lights.c.
so futhur dig found leds-lm3530c, the file structure is different with leds-lm3532.c, but i think it works the same.
any good suggestion from experts?
edit1 050820121203:
I decided to check what AdjBrightness do.
it is modifying the following files
/sys/class/leds/lcd-backlight/brightness
/sys/class/leds/amber/blink
/sys/class/leds/amber/brightness
/sys/class/leds/green/blink
/sys/class/leds/green/brightness
all return errors in note.
further investigation leads to Rootdim:
/sys/class/leds/leds-sec/trigger
/sys/class/leds/leds-sec/brightness
/sys/class/leds/leds-sec/mmc1::/trigger
/sys/class/leds/leds-sec/mmc1::/brightness
/sys/class/leds/leds-sec/mmc2::/trigger
/sys/class/leds/leds-sec/mmc2::/brightness
here all the triggers return error.
next thing i check /sys/class/
i see backlight/panel in it.
i also see lcd, leds and lightsensor.
have no idea, keep digging.
100820120935:
Found s6*aa*.c files inside driver folder.
There will be some info about 5.3inch screen.
Deeper search found that it only suplort 24 stages of brightness
From 0,1 to 30 is 0
Conclusion minimum brightness for galaxy note is 1(more than 30)
Keep digging.
100820121808:
s3cfb_s6e39a0.c contain brightness level from 1 to 24.
100820121815:
AMS529HA01 is samsung 5.3 inch galaxy note panel
s3cfb_s6e8aa0 -- the one we are using.
the following files also related to the above file.
s3cfb_s6e39a0
s3cfb_s6e63m0
s6d6aa1
s6dr171
s6e8aa1
smart_dimming
midas-lcd
setup-fb-s5p
the whole thing means samsung have tried other lcd before hd super amoled 5.3 inch?
keep digging for the brightness
150820121820:
End of research, the brightness for amoled devices only have 24 levels.
lower than that you will need to adjust contrast for better battery consumption.
if you use filter it wont decrease battery consumption, and it will affect your screenshot images clarity.
1609120512:
https://sites.google.com/site/androidnothize/no-dock/input-device-and-backlight
this shows you minimum brightness level is 30
http://forum.xda-developers.com/showthread.php?t=1709686
search for min_bl
http://forum.xda-developers.com/showthread.php?t=1154278&page=617
curve?
http://forum.xda-developers.com/showthread.php?t=1576355&page=222
N.E.A.K
So, what's the verdict? Are we stuck with "too bright in the dark" screens on our Note's?
d210 said:
So, what's the verdict? Are we stuck with "too bright in the dark" screens on our Note's?
Click to expand...
Click to collapse
For that purpose a screen filter works just fine for me.
Frankly it's not doing it for me, it looks like I'm looking through a grey plastic bag.
Andrew0811 said:
150820121820:
End of research, the brightness for amoled devices only have 24 levels.
lower than that you will need to adjust contrast for better battery consumption.
if you use filter it wont decrease battery consumption, and it will affect your screenshot images clarity.
Click to expand...
Click to collapse
So what is conclusion bro?
We can't use brightness below the SYSTEM-MINIMUM?
I also want more battery by reducing brightness to below 10.
AND yes you did well.
Good research.
Sorry for my english..
when I switch from an app with black screen (notification bar xda app etc etc) to a bright one.. Like whatsapp I see a strange thing... There is less contrast for 0.5sec then contrast is perfect and all is normal...
I don't know if you understand what I mean...
Is this normal? Or is a fault display?
Happens with stock and cyano... Full brightness and at lowest brightness...
thx for the replay
drigerott said:
Sorry for my english..
when I switch from an app with black screen (notification bar xda app etc etc) to a bright one.. Like whatsapp I see a strange thing... There is less contrast for 0.5sec then contrast is perfect and all is normal...
I don't know if you understand what I mean...
Is this normal? Or is a fault display?
Happens with stock and cyano... Full brightness and at lowest brightness...
thx for the replay
Click to expand...
Click to collapse
Thermal throttling is normally given as the answer to this.
Thanks for the fast replay... Then I must change my device? Or it'snormal
drigerott said:
Thanks for the fast replay... Then I must change my device? Or it'snormal
Click to expand...
Click to collapse
Its normal, but there are ways to change the way it does it, I am not an expert but if you root you can start to cange values. Search for thermal throttling values and you will hit a good thread about.
Yes I have root.. But I didn't understand.. For thermal throttle you mean cpu? Or even the display?
cause I don't have problem with multitask or other.. Only this strange problem that image quality is not perfect when switching to dark image to bright one.. But for less then a second.. But is frustrating and strange
drigerott said:
Yes I have root.. But I didn't understand.. For thermal throttle you mean cpu? Or even the display?
cause I don't have problem with multitask or other.. Only this strange problem that image quality is not perfect when switching to dark image to bright one.. But for less then a second.. But is frustrating and strange
Click to expand...
Click to collapse
as i said i am not an expert, but if you search in this forum you will find other threads that will give you information on which files to modify and how to do it...
gregbradley said:
as i said i am not an expert, but if you search in this forum you will find other threads that will give you information on which files to modify and how to do it...
Click to expand...
Click to collapse
ok i found some 3d about termal throttle and is not my problem.. i tried different mod but nothig...
i uploaded a video to show my problem ...
see the contrast change?
is not brightness...it's contrast that changes...
Yes, a have this effect too. I`ve changed brightness values at system/etc/sysmon.cfg, to a maximum values, after that screen doesn`t changing brightness when device is more hot, but this effect like in this video, is still exists! This contrast shading are not a termal throttling, this is something else, i don`t know exactly what it is.
i'm not alone then...
with cyanogenmod is so more evident...
tomorrow i'll turn on another one in my shop and see if is all xperia t like this...
anyway if some other has this strange problem, plz post here ^^ (maybe is a software fault)
Maybe a refresh issue?
when i scroll a page on black background with white txt.. the txt becomes greysh... if you scroll slowly remains white... happens to you too?
drigerott said:
Maybe a refresh issue?
when i scroll a page on black background with white txt.. the txt becomes greysh... if you scroll slowly remains white... happens to you too?
Click to expand...
Click to collapse
I don`t think it`s a refresh rate, but maybe i`n wrong.
And, yes, i have the same issues, and the screen is shading and becomes bright again all the time. Especially this happening when i try to open something or to enter at one of the bookmarks of phone menu, and when the phone "thinking", screen is shading, but then it becomes brighter again. I`m reaaly don`t know what it ies, but it`s not because of a thermal, 100%! I already changed the values of a brightness. I`m sure that all Xperia T phones are with the same issues, it`s bacause of a something in soft.
It has nothing to do with gpu.
Here is data sheet for AS3676 - www1.futureelectronics.com/doc/AUSTRIAMICROSYSTEMS/AS3676.pdf
And here is what DLS is from the data sheet -
8.4.9 DLS - Dynamic Luminance Scaling Input
The pin GPIO1/DLS can be used for dynamic backlight scaling input. Dynamic backlight scaling is used to reduce the power of the backlight especially when showing dark picture contents on the display. The control unit to operate DLS is the display processor sending a PWM signal to the AS3676 and in parallel changing the display content to compen- sate for a reduced brightness backlight.
DLS can be turned off in /system/etc/pre_hw_config.sh -
echo 0 > /sys/class/leds/led_1-lcd/use_dls
echo 0 > /sys/class/leds/led_2-lcd/use_dls
Is it save to turn DLS off ?
Sent from my LT30p using xda app-developers app
peetr_ said:
It has nothing to do with gpu.
Here is data sheet for AS3676 - www1.futureelectronics.com/doc/AUSTRIAMICROSYSTEMS/AS3676.pdf
And here is what DLS is from the data sheet -
8.4.9 DLS - Dynamic Luminance Scaling Input
The pin GPIO1/DLS can be used for dynamic backlight scaling input. Dynamic backlight scaling is used to reduce the power of the backlight especially when showing dark picture contents on the display. The control unit to operate DLS is the display processor sending a PWM signal to the AS3676 and in parallel changing the display content to compen- sate for a reduced brightness backlight.
DLS can be turned off in /system/etc/pre_hw_config.sh -
echo 0 > /sys/class/leds/led_1-lcd/use_dls
echo 0 > /sys/class/leds/led_2-lcd/use_dls
Click to expand...
Click to collapse
great find.. any way yesterday i turned on 5 new xperia t in my shop and all do like mine... that is DSL like peetr say..
but the annoying thing is that on cm10 (that all the ui is gray/dark) DSL is too much visible...) now i'll try to disable it.. i'll report if works
EDIT: still the same..
I don't get how to turn DLS off, what value should i change to turn it off ?
Sent from my LT30p using xda app-developers app
you must edit the file in /system/etc/pre_hw_config.sh
with root explorer or similar and change thise line: (0 instead of 1)
echo 0 > /sys/class/leds/led_1-lcd/use_dls
echo 0 > /sys/class/leds/led_2-lcd/use_dls
0 instead of 1 , and what should i set instead of 2 ? 0 too ?
And, is this save ???
Sent from my LT30p using xda app-developers app
Finally, this will have effect or no?
Because maybe we all have this issue.
Sent from my LT30p using xda premium
all xperia t works like i posted in the video (infact i tried 5 new xperia t all the same)
but that mod is not working.. for me is still the same..
DennisDD78 said:
0 instead of 1 , and what should i set instead of 2 ? 0 too ?
And, is this save ???
Sent from my LT30p using xda app-developers app
Click to expand...
Click to collapse
this is stock
echo 1 > /sys/class/leds/led_1-lcd/use_dls
echo 1 > /sys/class/leds/led_2-lcd/use_dls
change in to this:
echo 0 > /sys/class/leds/led_1-lcd/use_dls
echo 0 > /sys/class/leds/led_2-lcd/use_dls
but i see no difference..
Hey Guys,
So i got my nexus 7 about a week ago and had noticed a touch response delay and it made scrolling through the homescreen and webpages a pain. I searched around last night and this morning and found these build prop tweaks.
#Response
debug.performance.tuning=1 - Increases touch responsiveness.
video.accelerate.hw=1 - Increases touch responsiveness.
windowsmgr.max_events_per_sec=150 - Increases scrolling responsiveness.
I aslo have fauxclock 123 installed from the play store and disabled the tegra 3 smart dimmer. After doing both i see a substantial increase in responsiveness. let me know if anyone else gets the same result.
Do you add these to the build prop yourself, or are these supposed to be in there already with a different value?
Did you update to 4.2.1? It fixed all my issues.
Sent from my Nexus 7 using xda premium
Im on stock rooted 4.2.2 and still have slow scrolling and bounce back issues, i have just added these lines to my build prop and am giving it a go, i will report back with result, thanks for this! I hope it makes it better!
leonclement said:
Im on stock rooted 4.2.2 and still have slow scrolling and bounce back issues, i have just added these lines to my build prop and am giving it a go, i will report back with result, thanks for this! I hope it makes it better!
Click to expand...
Click to collapse
I am running Glazed build 4.1.2. How do I apply these fixes? Is this something I can do by myself or should I rely on a dev?
Edit: Upon further research, it seems that these values should be applied to /system/build.prop right? I don't see those headings anywhere, do I just copy and paste those 3 lines anywhere into the file?
Worked perfectly on my 8GB Nexus 7 running Paranoid Android 3.15. You rock!
Atrix2destroyer said:
I aslo have fauxclock 123 installed from the play store and disabled the tegra 3 smart dimmer. After doing both i see a substantial increase in responsiveness. let me know if anyone else gets the same result.
Click to expand...
Click to collapse
there are cheaper options to disable smart dimmer than spending $4.
in terminal:
echo "0" > /sys/devices/tegradc.0>smartdimmer/enable
if you have rom toolbox, you can go into the scripter app, create a new script with that command and set it run at boot.
if you want purchase an app to do it for you: https://play.google.com/store/apps/details?id=com.widgets.big.tegra.prism.toggle
cnstarz said:
there are cheaper options to disable smart dimmer than spending $4.
in terminal:
echo "0" > /sys/devices/tegradc.0>smartdimmer/enable
if you have rom toolbox, you can go into the scripter app, create a new script with that command and set it run at boot.
if you want purchase an app to do it for you: https://play.google.com/store/apps/details?id=com.widgets.big.tegra.prism.toggle
Click to expand...
Click to collapse
Thanks for the heads up... Definitely kind of a waste to spend $4 just to disable that file. But fauxclock is a great app definitely worth the money
The nexus 6 gets pretty dim, but you can make it dimmer than the slider allows.
Attached is an APK which will do it when opened. All it does is run the following command:
Code:
echo 1 > /sys/devices/fd900000.qcom,mdss_mdp/qcom,mdss_fb_primary.164/leds/lcd-backlight/brightness
I'm unsure how to get it to persist through turning the screen off and back on (it goes back to the default min brightness if you do this).
Full Source is available here:
https://github.com/chrisj951/MinBrightness
ChrisJ951 said:
The nexus 6 gets pretty dim, but you can make it dimmer than the slider allows.
Attached is an APK which will do it when opened. All it does is run the following command:
Code:
echo 1 > /sys/devices/fd900000.qcom,mdss_mdp/qcom,mdss_fb_primary.164/leds/lcd-backlight/brightness
I'm unsure how to get it to persist through turning the screen off and back on (it goes back to the default min brightness if you do this).
Full Source is available here:
https://github.com/chrisj951/MinBrightness
Click to expand...
Click to collapse
That's awesome, thanks. Is there any was to make the maximum brightness higher?
SeanPlunk said:
That's awesome, thanks. Is there any was to make the maximum brightness higher?
Click to expand...
Click to collapse
Still been trying to figure that out. It seems as that making it brighter may require building the OS or kernel from source to do.
You can also download Screen Filter ( no root required).... I use this at night when I'm in my car and don't want that bright glow on my face
irock1985 said:
You can also download Screen Filter ( no root required).... I use this at night when I'm in my car and don't want that bright glow on my face
Click to expand...
Click to collapse
Great app. Thanks for the tip.
Oneplus 7 Pro
Force 90hz Refresh Rate in almost every App (and Games)
*also uncaps FPS (since Vsync is on by default for Android)
Requirements:
1. A Windows PC (Windows 10 64 Bit is preferred)
2. Oneplus Drivers
3. A USB Type-C Cable
4. Your Oneplus 7 Pro
Steps:
1. Plug in your Oneplus device and select File Transfer mode in your phone's notification selection, then open My Computer and you will see the drive for Oneplus Drivers.
2. Install Oneplus Drivers (you may be prompted to reboot afterwards). You may need to plug and unplug the device to finish driver recognition. Unplug your phone once it is finished.
3. In your phone, go to Settings > About Phone, and tap Build Number multiple times in fast succession until the message "you are now a developer" appears.
4. Go to Settings > System > Developer Options, and turn on USB-debugging.
5. Go to Playstore and download jOnePlus Tools
6. Plug your device in your PC.
7. Anywhere on the empty desktop of your PC, press shift + right click, and select "Open Powershell window here"
8. Wait for Powershell to load
9. Type "adb shell" without the quotes
10. A permission prompt will appear in your Oneplus 7 Pro's screen, allow it.
11. Type "adb shell" once again and press Enter, and you should see your device like this "Oneplus7Pro:/ $"
12. Type or copy-paste the text below without the quotes:
"pm grant net.jroot3d.joneplustools android.permission.WRITE_SECURE_SETTINGS", and press Enter.
13. Once you've entered that, it should repeat what you've typed in the next line.
14. Unplug your device, and open jOnePlus Tools app.
15. Tap Screen Refresh Rate and select Force 90Hz
16. Congratulations, you are done! To confirm, you can go to Settings > Display > Screen Refresh Rate and you should see it as 60Hz from the outside, but when you tap it, you will see that nothing from the 2 choices is selected. It means you are using the 3rd Hidden Setting.
Tip: You may need to reselect Force 90 Hz from the jOnePlus Tools if you have selected 90hz or 60hz from the settings.
Note: This will enable 90hz (and up to 90 fps) for apps and games, unless the app itself has an even stronger FPS-controller then it will tone-down the FPS to the standard set by that game. But for most games without an FPS controller or 30-FPS-locked games without an in-game FPS-controller, it will work 100%.
Credits:
C3C076 (XDA Developer, Dev of GravityBox)
JRoot3D.dev (jOnePlus Tools Developer)
Guide Maker: Ares (Freyelis - XDA Senior Member)
RIP Battery Life?
stanley08 said:
RIP Battery Life?
Click to expand...
Click to collapse
No, try it. The brightness and resolution actually kills more battery than the refresh rate, so set the reso to dynamic, and the brightness to less than 50% always.
Freyelis said:
No, try it. The brightness and resolution actually kills more battery than the refresh rate, so set the reso to dynamic, and the brightness to less than 50% always.
Click to expand...
Click to collapse
Maybe I will
stanley08 said:
Maybe I will
Click to expand...
Click to collapse
Enjoy better gaming man. Try it on Assassin's Creed: Identity too, that game has awesome graphics but was locked at 30 FPS... Not anymore
Freyelis said:
No, try it. The brightness and resolution actually kills more battery than the refresh rate, so set the reso to dynamic, and the brightness to less than 50% always.
Click to expand...
Click to collapse
Anyway to set auto brightness but less than 50% always ??
Or you could simply use Smurf kernel which already has this in the config and stays set through reboots. Or just use the original method from C3C076 which sets it permanently no need for this extra stuff or to have joneplus tools constantly in background for no reason...
9 hrs SOT? @op do you have qhd or fhd?
Stock kernel? Any mods?
if i restart my phone will the settings i made gone?
se7ensde said:
Or you could simply use Smurf kernel which already has this in the config and stays set through reboots. Or just use the original method from C3C076 which sets it permanently no need for this extra stuff or to have joneplus tools constantly in background for no reason...
Click to expand...
Click to collapse
Adb method from C3C076 resets after every reboot, that's why I made this tutorial for those unrooted people who wants to make the setting stick.
bubu23 said:
if i restart my phone will the settings i made gone?
Click to expand...
Click to collapse
No
Xalph92 said:
Anyway to set auto brightness but less than 50% always ??
Click to expand...
Click to collapse
Either set it manually, or use YAAB app as a replacement for auto brightness, which you can set the maximum ang minimum brightness.
virtyx said:
9 hrs SOT? @op do you have qhd or fhd?
Stock kernel? Any mods?
Click to expand...
Click to collapse
Dynamic, stock kernel.
No mods, I just control every background app using built-in background restriction, deepclear, and deep battery optimization.
Just for information, my kernel config has a switch to apply 90Hz, auto or 60 HZ.
Gesendet von meinem xXx_NoLimits_7.1 on GM1913 mit Tapatalk
Freyelis said:
Adb method from C3C076 resets after every reboot, that's why I made this tutorial for those unrooted people who wants to make the setting stick.
Click to expand...
Click to collapse
Did you actually test it? "ADB shell settings global put" command changes user settings that are stored in the filesystem and are thus persisted across reboots until explicitly changed by the user.
Freyelis said:
Dynamic, stock kernel.
No mods, I just control every background app using built-in background restriction, deepclear, and deep battery optimization.
Click to expand...
Click to collapse
Have you restricted system apps too? Did you do this for each app one by one?
Do you have a list of what you've restricted
thanks!
thanks!!!so after doing this im rooted already?because jtools need root right?
Freyelis said:
Adb method from C3C076 resets after every reboot, that's why I made this tutorial for those unrooted people who wants to make the setting stick.
Click to expand...
Click to collapse
Stays through reboots for me... And like I said there are easier simpler and faster ways to achieve this without need of all this extra stuff. Smurf kernel already implemented this in his config so it stays like that too. And C3C076 had made qs tiles for this. I've been using his method for over a week now through several reboots no issues.
C3C076 said:
Did you actually test it? "ADB shell settings global put" command changes user settings that are stored in the filesystem and are thus persisted across reboots until explicitly changed by the user.
Click to expand...
Click to collapse
Sorry, thanks for the clarification sir, great work as always, will revise this one
virtyx said:
Have you restricted system apps too? Did you do this for each app one by one?
Do you have a list of what you've restricted
Click to expand...
Click to collapse
I did not restrict system apps, only the apps that I installed. Apps that I need notifications from such as Telegram, is not included in the restriction. All other apps are, like games, editors, etc..