Database Develop

[MOD][DEPRECATED] Overclock support

Content deprecated and removed to avoid confusion.

Note 31/07/2011: Updated for Nova Script
Note 10/08/2011: The method is a bit different but you get the overall idea after reading this
II. How to overclock (applies to Nova)
So, you just want to overclock eh?
Ok, you have several ways to do this:
a) Using Nova built-in overclock script
b) Typing commands by hand (terminal, adb, etc)
(No, SetCPU does not work on OMAP devices, only for choosing governors)
I will also cover how you get your Optimus Black to auto-overclock (at least in Nova).
But first of all, very very important, please open this spreadsheet - it has a listing of values of clocks and the corresponding voltages which can be: stock ones, low ones, ultra low ones and high ones. For speed & battery compromise, I suggest low ones. However, if you're a gamer, you better stick with stock for instance.
Print that.
Done? let's move on.
a) Using Nova built-in overclock script
Now, I made a hilariously simple script for you to use on Nova to facilitate your overclock.
You just have to open the terminal application and:
Type "su" (without ""), press enter, click allow if it asks - very important step (needs root).
Type "nova" (without ""), press enter and congratulations, you've just entered the nova (overclock) script!
There just choose "overclock!". Remember, first the voltage, then the clock.
For example:
Type "su" (without "") on terminal, press enter. Click allow if it asks.
Type "nova" (without "") on terminal, press enter.
Type "1" (without "") and press enter.
Type "62" (without "") and press enter.
Type "1100000" (without ""; this is 1.1 Ghz) and press enter.
Enjoy your overclocked and undervolted phone.
Oh, terminal emulator has some kinks:
- If your keyboard disappears hit menu button and click 'toggle soft keyboard'.
- If you exit and it stays on the statusbar, re-enter terminal, hit menu button and click 'reset'.
P.S. You can also run this via ADB.
But how to auto-overclock on boot?
Now in latest Nova Script it will ask you if you want to set them on boot!
If by some reason you didn't test and found out that your device is stable with those settings and you can't boot your device or if it does it's all laggy and craps, you can just power it off, remove microSD card, use an adapter and put it on your PC or laptop and remove the file, then insert the microSD card back and reboot the phone. I chose a file in the microSD card especially because of this safeguard.
b) Typing commands by hand
If you're feeling too pro for the overclock script, you can just type them by hand:
- echo "xx" > /proc/overclock/max_vsel
- echo "xxxxxxx" > /proc/overclock/max_rate
If you want to auto-overclock, use the same method as above.
This is it. Simple.
A few reminders:
Voltage first; then frequency.
Check the table in the beginning of the post for frequencies and recommended voltages
Frequency has to be for example 1200000, not 1.2. It's in Mhz, not Ghz.
Test the **** out of your device with a frequency/voltage before setting it at boot.
Most Optimus Black won't be stable beyond 1.2 Ghz.
If you can't boot or are having problems because of auto-overclock, just delete the file.
Done.

Sorry for the delay, I'm finished now.
Time to go upload Nova v1.7.27.

Instructions updated; I forgot the "su" part.

Thanks for the detailed tutoring!

Thanks! I really appreciate this

Interesting...
From where have you obtained the recommended voltaje/freq?
Thanks!

From a reference of Droid X which uses the same chipset as us.

my first thing is to set the min freq to about 100Mhz XD

Is not working...
After boot, cat /proc/overclock/max_rate says 550000
Changing auto_ocuv in /sdcard/nova/overclock/ has no effect. After reboot, the same 550000...
Changing manually with oc script works, after that the report is correct.
Anyway, is not much difference between the two cases... It seems a little bit increased speed, but maybe is just me...
I used 62 and 1150000...
Untill now it is OK.
How the setting must be arranged in auto_ocuv? Mine is 621150000.. Is this correct?

rgabi88 said:
Is not working...
After boot, cat /proc/overclock/max_rate says 550000
Changing auto_ocuv in /sdcard/nova/overclock/ has no effect. After reboot, the same 550000...
Changing manually with oc script works, after that the report is correct.
Anyway, is not much difference between the two cases... It seems a little bit increased speed, but maybe is just me...
I used 62 and 1150000...
Untill now it is OK.
How the setting must be arranged in auto_ocuv? Mine is 621150000.. Is this correct?
Click to expand...
Click to collapse
That's because you have vold/179:16.
It works for 179:17.
Today I will get it working for everyone. I suppose you can't also use App Inj.
But no worries, just wait for today's version.

Noejn said:
From a reference of Droid X which uses the same chipset as us.
Click to expand...
Click to collapse
That's why quadrant advanced bar results precentage is very similar. Both suck in cpu processing very nice in I/O hhahaha.
Sent from my LG-P970 using Tapatalk

Noob question, could optimus black get more overclock potential with Android 2.3 ? Or always unstable with 1.2 ghz+ ?

Thanks! Using your overclock, I could overclock my Optimus Big (Only for Korea)!
I used 1200/64... However I tried to overclock my phone more than 1.2GHz, but I can't do that. It's so hard to find right voltage for 1.3GHz or 1.25GHz

Hi I'm new to this. What is the different between overlocking and unlocking a the phone? Thanks.

[GUIDE][FIX] Nvidia PRISM/smartdimmer - fix screen washout after watching videos

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

[GUIDE] Force 90Hz for almost every App/Game (Uncaps FPS)

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..

[KERNEL][11] Placebo Kernel - LOS 18.1 Undervolting

Changelog:
2021-06-06
-Merge to 54ffccbf053b5b6ca4f6e45094b942fab92a25fc
Disclaimer: I have no idea what I'm doing, I just copy pasted some stuff together and compiled the kernel. This kernel was only momentarily tested on an SM-G900T (klte). If there's a compatibility problem you will probably boot loop until you fix it. Undervolting can cause issues. You have been warned!
This is the LOS 18.1 kernel from https://github.com/LineageOS/android_kernel_samsung_msm8974/ with the KTOONSEZ undervolting control mods from https://github.com/alaskalinuxuser/...mmit/37664e51977ccd27563458526463f53c6be0490a
The gcc version is a 4.9 I got from this GitHub page:
https://github.com/Duhjoker/arm-linux-androideabi-4.9
Intro:
This kernel allows tweaking CPU voltages. We're interested in undervolting the CPU so it uses less voltage to operate. The extent you can undervolt your CPU is based on luck. While your CPU will run more efficiently with an undervolt, real-world benefits are sometimes hard to tell. For example, your phone may compensate for cooler operation by running at a higher speed more often. Any battery life benefits to undervolting this one part of the phone are ambiguous, it's really hard to test.
Prerequisites:
You will need root on your phone! If you don't have root you can get it by installing Magisk. First install Magisk's apk file in Android. Then rename the apk so it has a .zip file extension and leave it in your phone's storage.
Releases · topjohnwu/Magisk
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
Instructions:
0. Keep a copy of Magisk's .zip on your phone!
1. Download the latest *boot.img and place it in your phone's storage
2. Boot to TWRP recovery or the recovery you use
3. Tap Install -> Tap "Install Image" to toggle the button
4. Select boot.img and FLASH TO YOUR BOOT PARTITION
4a. If you use Magisk it's broken now. Tap "Install Zip" to toggle the button and flash Magisk's zip
5. Reboot
6. Install SmartPack Kernel Manager OR Kernel Adiutor and grant it root privileges. You may now tweak your CPU voltage in the app. Once you are happy with your settings use the "Apply on Boot" to make the settings permanent.
https://f-droid.org/en/packages/com.smartpack.kernelmanager/
https://f-droid.org/en/packages/com.nhellfire.kerneladiutor/
Note: The kernel does not persist. You will need to reinstall it after every LOS update.
(Not) Optional: Consider making a TWRP backup of your phone. Unstable undervolting can result in data loss.
Help, I'm boot looping/can't boot because of unstable undervolt:
Download your phone's particular LineageOS zip from https://download.lineageos.org/ and unzip it. Put the boot.img file on your phone and flash it to the BOOT partition in recovery.
Undervolting guide:
Not all two phones are the same. Look at your stock voltages or old forum posts for reference. The S5's SoC is the MSM8974PRO/MSM8974AC, marketed as the Snapdragon 801. Also see the binning info at the bottom of this guide to learn your phone's binning.
Open SmartPack and go to CPU Voltage in the menu. It will display a big list of CPU clock speeds and voltages. These are your stock voltages. Your goal is to lower them some amount without your phone crashing. On the top part of the app you can scroll to "Global Offset" and enter one number to lower all the voltages at once.
I recommend trying a -30 mV or -40 mV global offset first, it seems like most phones can handle this. After you set your undervolt you should test for stability before making it permanent. Here are some ideas:
-Use your phone as you normally would.
-Keep playing videos on your phone
-Try the stress test in the bottom of this guide
Do not daily drive your phone for work until you're reasonably sure your undervolt is stable. You don't want it to crash when doing something important.
Once you have a good global offset you can start tweaking individual CPU states to lower voltages even more. This can get really annoying since there are so many. If you want to fine-tune I recommend only giving special attention to the top speed (2457), the middle speeds (1574 in particular, but include everything up to 1267 if you have to), and the lowest speed (300.)
The average phone tends to spend the most time in those states so focusing on those will help save your sanity.
To set your undervolt permanently enable "Apply on Boot" and SmartPack will set the values when your phone starts.
Spotting an unstable undervolt:
If one or more CPU states are unstable your phone will suddenly hang, hard reboot, fast reboot or other anomalies. You will probably also see CPU problems in the logs. Do "su; dmesg" in a Terminal or "su;logcat" to see. The cure for a bad undervolt is not undervolting so much. It can be hard to tell which CPU states are unstable unfortunately, you may have to adjust all of them to be sure,
Tips:
-Undervolts can be hard to test for stability, so try to leave some overhead if you don't have all day. SmartPack/Kernel Adiutor lets you set a global offset if you only want a small UV!
-You can set unusually low voltages for 300 MHz. Its stock voltage is about 750-800 mV but it will usually work on 650 mV and go as low as 600 mV if you're lucky.
-Low freqs are usually better at getting undervolted than the top freqs
-Not all cores will run at the same freqs/voltages. Disabling most of your cores is a good way to prevent your phone from heating up during stress tests but may lead to instability when you reactivate all of your cores.
-Your phone's battery draining may spontaneously cause your undervolt to become unstable. Unfortunately you just have to make the UV less aggressive if this happens.
-Try not switch the governor. To change CPU behavior go to Settings > Battery >Battery Saver and Performance > Performance Profile and toggle the slider as you see fit.
I recommend using Balanced and switching to Quick when you need your phone to be faster.
Performance is very energy inefficient. It prevents all cores from parking and tries to peg at least some of them to top speed. One core performance can be better than quick but multi-core makes it very easy for the phone to throttle.
LOS uses Qualcomm's MPDecision hotplugger. Switching governors causes glitches MPDecision and prevent CPU cores from parking. If you really want to try out governor tweaks, you should disable MPDecision in SmartPack first. Disabling MPDecision will incur a battery life penalty since your CPU will no longer park.
Synthetic stress test:
Install Termux and run this one-liner to stress one core:
Code:
while true; do openssl speed -evp aes-256-gcm; sleep 15s; done
For 4 cores:
Code:
while true; do openssl speed -multi 4 -evp aes-256-gcm; sleep 15s; done
You can also use this test to compare performance or to observe thermal throttling. OpenSSL will return a performance score after each run.
Sample stock/undervolt values from my speed3-pvs9-bin-v1 SM-G900T:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Very minor LOS power saving tweaks that don't help very much but they're funny:
-Search "Backlight" in the settings and turn off the backlight for the Menu and Back keys.
-The battery/notification LED can be adjusted down to about 7% brightness
-LOS has several settings for turning off haptic feedback/vibrations. I turned them off for the touch keyboard and the Menu/Back keys.
SoC Binning Information:
Your phone's SoC is tested for quality and assigned a PVS number at the factory. For S5, it ranges from PVS0 (low quality) to PVS15 (high quality). Higher quality have lower stock voltages. Check by running these in a terminal:
Code:
su
cat /sys/module/clock_krait_8974/parameters/table_name
You can compare the bins here

boot loop

vlad3647 said:
boot loop
Click to expand...
Click to collapse
Which device do you use?
I left some default undervolts in the PVS tables because they didn't work for me, maybe it's causing the problem. I'll remove them and compile it again later.

Klte

I don't mind boot loop,I reinstall everything

vlad3647 said:
I don't mind boot loop,I reinstall everything
Click to expand...
Click to collapse
You can always fix the boot loop by flashing boot.img from the lineageos zip.
I compiled build PlaceboKernel05072021V2.img without modified PVS tables in the first post. Still works on my phone.
I uploaded a V3 as boot.img, I don't know if this makes a difference. Works on my phone.

I didn't know thanks

Thanks, is working great

Flashed the `boot.img` file itself; verified working on my G900P!

Merged changes (includes the sdcard related ones.)

can't change the values on the voltage. phone keeps on rebooting. using g900t
update: got it to work. testing in progress

Boatshow said:
Changelog:
2021-06-06
-Merge to 54ffccbf053b5b6ca4f6e45094b942fab92a25fc
Disclaimer: I have no idea what I'm doing, I just copy pasted some stuff together and compiled the kernel. This kernel was only momentarily tested on an SM-G900T (klte). If there's a compatibility problem you will probably boot loop until you fix it. Undervolting can cause issues. You have been warned!
This is the LOS 18.1 kernel from https://github.com/LineageOS/android_kernel_samsung_msm8974/ with the KTOONSEZ undervolting control mods from https://github.com/alaskalinuxuser/...mmit/37664e51977ccd27563458526463f53c6be0490a
The gcc version is a 4.9 I got from this GitHub page:
https://github.com/Duhjoker/arm-linux-androideabi-4.9
Intro:
This kernel allows tweaking CPU voltages. We're interested in undervolting the CPU so it uses less voltage to operate. The extent you can undervolt your CPU is based on luck. While your CPU will run more efficiently with an undervolt, real-world benefits are sometimes hard to tell. For example, your phone may compensate for cooler operation by running at a higher speed more often. Any battery life benefits to undervolting this one part of the phone are ambiguous, it's really hard to test.
Prerequisites:
You will need root on your phone! If you don't have root you can get it by installing Magisk. First install Magisk's apk file in Android. Then rename the apk so it has a .zip file extension and leave it in your phone's storage.
Releases · topjohnwu/Magisk
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
Instructions:
0. Keep a copy of Magisk's .zip on your phone!
1. Download the latest *boot.img and place it in your phone's storage
2. Boot to TWRP recovery or the recovery you use
3. Tap Install -> Tap "Install Image" to toggle the button
4. Select boot.img and FLASH TO YOUR BOOT PARTITION
4a. If you use Magisk it's broken now. Tap "Install Zip" to toggle the button and flash Magisk's zip
5. Reboot
6. Install SmartPack Kernel Manager OR Kernel Adiutor and grant it root privileges. You may now tweak your CPU voltage in the app. Once you are happy with your settings use the "Apply on Boot" to make the settings permanent.
https://f-droid.org/en/packages/com.smartpack.kernelmanager/
https://f-droid.org/en/packages/com.nhellfire.kerneladiutor/
(Not) Optional: Consider making a TWRP backup of your phone. Unstable undervolting can result in data loss.
Help, I'm boot looping/can't boot because of unstable undervolt:
Download your phone's particular LineageOS zip from https://download.lineageos.org/ and unzip it. Put the boot.img file on your phone and flash it to the BOOT partition in recovery.
Undervolting guide:
Not all two phones are the same. Look at your stock voltages or old forum posts for reference. The S5's SoC is the MSM8974PRO/MSM8974AC, marketed as the Snapdragon 801. Also see the binning info at the bottom of this guide to learn your phone's binning.
Open SmartPack and go to CPU Voltage in the menu. It will display a big list of CPU clock speeds and voltages. These are your stock voltages. Your goal is to lower them some amount without your phone crashing. On the top part of the app you can scroll to "Global Offset" and enter one number to lower all the voltages at once.
I recommend trying a -30 mV or -40 mV global offset first, it seems like most phones can handle this. After you set your undervolt you should test for stability before making it permanent. Here are some ideas:
-Use your phone as you normally would.
-Keep playing videos on your phone
-Try the stress test in the bottom of this guide
Do not daily drive your phone for work until you're reasonably sure your undervolt is stable. You don't want it to crash when doing something important.
Once you have a good global offset you can start tweaking individual CPU states to lower voltages even more. This can get really annoying since there are so many. If you want to fine-tune I recommend only giving special attention to the top speed (2457), the middle speeds (1574 in particular, but include everything up to 1267 if you have to), and the lowest speed (300.)
The average phone tends to spend the most time in those states so focusing on those will help save your sanity.
To set your undervolt permanently enable "Apply on Boot" and SmartPack will set the values when your phone starts.
Spotting an unstable undervolt:
If one or more CPU states are unstable your phone will suddenly hang, hard reboot, fast reboot or other anomalies. You will probably also see CPU problems in the logs. Do "su; dmesg" in a Terminal or "su;logcat" to see. The cure for a bad undervolt is not undervolting so much. It can be hard to tell which CPU states are unstable unfortunately, you may have to adjust all of them to be sure,
Tips:
-Undervolts can be hard to test for stability, so try to leave some overhead if you don't have all day. SmartPack/Kernel Adiutor lets you set a global offset if you only want a small UV!
-You can set unusually low voltages for 300 MHz. Its stock voltage is about 750-800 mV but it will usually work on 650 mV and go as low as 600 mV if you're lucky.
-Low freqs are usually better at getting undervolted than the top freqs
-Not all cores will run at the same freqs/voltages. Disabling most of your cores is a good way to prevent your phone from heating up during stress tests but may lead to instability when you reactivate all of your cores.
-Your phone's battery draining may spontaneously cause your undervolt to become unstable. Unfortunately you just have to make the UV less aggressive if this happens.
-Try not switch the governor. LOS uses Qualcomm's MPDecision hotplugger. Switching governors will glitch MPDecision and prevent CPU cores from parking. If you really want to try out governor tweaks, you should disable MPDecision in SmartPack first. Disabling MPDecision will incur a battery life penalty since your CPU will no longer park.
Synthetic stress test:
Install Termux and run this one-liner to stress one core:
Code:
while true; do openssl speed -evp aes-256-gcm; sleep 15s; done
For 4 cores:
Code:
while true; do openssl speed -multi 4 -evp aes-256-gcm; sleep 15s; done
You can also use this test to compare performance or to observe thermal throttling. OpenSSL will return a performance score after each run.
Sample stock/undervolt values from my speed3-pvs9-bin-v1 SM-G900T:
View attachment 5302815View attachment 5302817
Very minor LOS power saving tweaks that don't help very much but they're funny:
-Search "Backlight" in the settings and turn off the backlight for the Menu and Back keys.
-The battery/notification LED can be adjusted down to about 7% brightness
-LOS has several settings for turning off haptic feedback/vibrations. I turned them off for the touch keyboard and the Menu/Back keys.
SoC Binning Information:
Your phone's SoC is tested for quality and assigned a PVS number at the factory. For S5, it ranges from PVS0 (low quality) to PVS15 (high quality). Higher quality have lower stock voltages. Check by running these in a terminal:
Code:
su
cat /sys/module/clock_krait_8974/parameters/table_name
You can compare the bins here
Click to expand...
Click to collapse
LMAO imagine undervolting a 7 year old device...

ralovesoc said:
LMAO imagine undervolting a 7 year old device...
Click to expand...
Click to collapse
Are you here just to make a fun of something? That's rude.
Yes, it's a 7 years old 28nm CPU, which is obviously isn't as power efficient as modern ones. 28nm is huge by today's standards.
7 years ago, this phone came in a box with additional battery and a battery charger, because it was an issue even then. What's the problem in undervolting or underclocking the device when performance isn't a priority, to make it last longer?

To change CPU behavior go to Settings > Battery >Battery Saver and Performance > Performance Profile and toggle the slider as you see fit. I think this is how you're supposed to do it because changing governor settings directly causes glitches. Performance preset pegs most cores to top speed.
Garry58 said:
7 years ago, this phone came in a box with additional battery
Click to expand...
Click to collapse
Maybe in some markets but I don't think that was true. Have an ad that didn't age well.

Boatshow said:
Maybe in some markets but I don't think that was true. Have an ad that didn't age well.
Click to expand...
Click to collapse
Maybe only in EU? I don't know. I have 900F model. That ad is just typical Samsung ad. They're openly laughing at iPhone, but literally next year do the same thing with Galaxy S6. At this point, I don't think marketing team has any communication with development team.

Boatshow said:
You can always fix the boot loop by flashing boot.img from the lineageos zip.
I compiled build PlaceboKernel05072021V2.img without modified PVS tables in the first post. Still works on my phone.
I uploaded a V3 as boot.img, I don't know if this makes a difference. Works on my phone.
Click to expand...
Click to collapse
what do you mean V3?

@vlad3647 That was an old post, there is no V3 anymore. Now I name by date. Currently the latest is 06-06-2021_boot.img.

@Boatshow
Are you able to add some hotplug options to the kernel? Without all cpu cores stay online all the time, what of course means unnecessary energy wasting.

@v00d007 Not sure what you mean, the default hotplugger MPDecision still works with the modified kernel. If the cores stop parking it's probably because MPDecision is disabled or a CPU settings change caused it to glitch.
If you're talking about an alternative hotplugger fbs wrote one here. Nobody can compare it to MPDecision because that is closed source. I read several years ago that hotpluggers only save small percents over a few hours so I don't know if testing differences is worth trying.
tuned-kernel-S5/drivers/staging/tuned at ten · bemerguy/tuned-kernel-S5
Contribute to bemerguy/tuned-kernel-S5 development by creating an account on GitHub.
github.com
Maybe a hackjob you can do is compile the tuned plugger (or get the binary from the zip) and swap it out with the MPDecision binary. It should be at /system/bin/mpdecision or somewhere similar.

Boatshow said:
Not sure what you mean, the default hotplugger MPDecision still works with the modified kernel. ...
Click to expand...
Click to collapse
Well, the problem for me is that in kernel adiutor the category "hotplug" doesn't show up. And category "cpu" shows that no core goes offline at any time. If MPDecision was active, 1 or 2 cores should go offline from time to time if there's no load. Normally I use Intelliglug and for me it makes a noticable difference in battery cycles (~10-15%).

How To Guide [GUIDE] How to *actually* force peak refresh rate. (Snapchat, GCam, Insta, etc) (Does not work on Android 14)

[Re-posting this here after I confirmed it work with the Pixel 7 as well]
To be clear, this is not the same as the developer option.
Enter the following ADB commands (you can also modify these values using the app SetEdit in the Play Store, no root required):
adb shell settings put system peak_refresh_rate 24.0
adb shell settings put system min_refresh_rate 24.0
The reason this works is because by assigning it a random and unsupported value, we are [kind of] breaking the refresh rate. As a result of which, the OS won’t be able to adjust this rate, and hence stick with the maximum available rate.

You can also enable the "Force Refresh Rate" in Developer Options. I tried it, but don't really care to keep DO enabled. Also you can enable "Show Refresh Rate" in DO. I did that also, and realized that with keeping it at 60(normal), and keeping "Smooth Display" on, the phone kicks it into 90 the moment you touch the screen. So forcing 90 100% of the time is a waste of battery in my opinion. Only when the phone is not touched for three seconds does it drop back to 60. Otherwise any use of the phone it stays at 90 normally.

bobbyphoenix said:
You can also enable the "Force Refresh Rate" in Developer Options. I tried it, but don't really care to keep DO enabled. Also you can enable "Show Refresh Rate" in DO. I did that also, and realized that with keeping it at 60(normal), and keeping "Smooth Display" on, the phone kicks it into 90 the moment you touch the screen. So forcing 90 100% of the time is a waste of battery in my opinion. Only when the phone is not touched for three seconds does it drop back to 60. Otherwise any use of the phone it stays at 90 normally.
Click to expand...
Click to collapse
Started my day today at 100% 7AM and am at 52% 11PM so I am happy. I can't stand Snapchat being 60.

Update on my observation. It may be a placebo effect, but knowing that it changes makes me see a slight stutter. Forcing 90 at all times "seems" much smoother, so I'm leaving it on also. Cheers!

this trick is irrelevant, you can do it in developer tool....

Vio281 said:
this trick is irrelevant, you can do it in developer tool....
Click to expand...
Click to collapse
The developer option does not force in many cases. In Snapchat when you swipe to the left and the camera is still initialized it stays at 60hz. Once the camera is not initialized it goes to 90hz. I believe it is the same in Instagram.

Jonnyswboy said:
The developer option does not force in many cases. In Snapchat when you swipe to the left and the camera is still initialized it stays at 60hz. Once the camera is not initialized it goes to 90hz. I believe it is the same in Instagram.
Click to expand...
Click to collapse
Jonnyswboy said:
The developer option does not force in many cases. In Snapchat when you swipe to the left and the camera is still initialized it stays at 60hz. Once the camera is not initialized it goes to 90hz. I believe it is the same in Instagram.
Click to expand...
Click to collapse
Has a fix been found for this cause I found this doesn't seem to be an issue at all on iPhone but incredibly frustrating on Android especially Snapchat.

lukeah02 said:
Has a fix been found for this cause I found this doesn't seem to be an issue at all on iPhone but incredibly frustrating on Android especially Snapchat.
Click to expand...
Click to collapse
My fix is in the original post. Has been working great for me.

Been using this for a while, but let's saym hypothetically if I wanted to restore it to default settings, which values do I need to put on the adb commands?

If I do those ADB commands and decide I want to not have them anymore, how would I revert?

To get your default values before doing the change, use:
Code:
adb shell settings get system peak_refresh_rate
and
Code:
adb shell settings get system min_refresh_rate
For me on stock firmware unrooted, peak_refresh_rate = null, and min_refresh_rate = 0.
Thanks for your fix! I was wondering why some apps were low hz.

heisenberg17 said:
Been using this for a while, but let's saym hypothetically if I wanted to restore it to default settings, which values do I need to put on the adb commands?
Click to expand...
Click to collapse
Get default values before doing the change:
adb shell settings get system peak_refresh_rate
adb shell settings get system min_refresh_rate
Default values (stock unrooted):
peak_refresh_rate = null
min_refresh_rate = 0
Thanks for your fix! I was wondering why some apps were low hz.

I've just got a Pixel 7 and thought I'd try this.
Observations, stock not rooted etc
Peak refresh rate = 90
min refresh rate = null
Applied the settings in post 1
and both come back as 24 when 'getting' peak/min rates from adb.
However, turning on show refresh rate in developer options show 90 when using the screen, but drops back to 60 if you leave it for a few seconds.
it only stays at 90 if you turn on Force peak refresh rate in Developer options.
This is only so far when messing about on the home screen, not tested in any apps etc, but it looks like these settings can't be fixed by setting a random number as post 1 implies

As a quick follow up, setting both peak and min to 90 does fix them, but seems a bit pointless as you can turn it on/off within developer settings.
This is not a bash at the OP, but maybe recent update have taken this 'feature' out

Does this survive a reboot?

xduox said:
Get default values before doing the change:
adb shell settings get system peak_refresh_rate
adb shell settings get system min_refresh_rate
Default values (stock unrooted):
peak_refresh_rate = null
min_refresh_rate = 0
Thanks for your fix! I was wondering why some apps were low hz.
Click to expand...
Click to collapse
Though the above might be a possible solution, here is the proper way to revert using ADB:
adb shell settings reset system peak_refresh_rate
To dig further into the possible System settings (amazing topic ^^)
adb shell settings list system

MrPeaski said:
seems a bit pointless as you can turn it on/off within developer settings.
This is not a bash at the OP, but maybe recent update have taken this 'feature' out
Click to expand...
Click to collapse
You can't force peak refresh rate in developer settings. It will still drop at times, like in Snapchat when the camera is accessed, on Google Maps, etc. It still automatically drops to 60hz despite the developer option being enabled.
And after updating to the Android 14 beta this workaround does not work anymore, and I am very frustrated that I am unable to truly force 90hz anymore.