In the following settings, is the battery use equal?
CPU set to 200 MHz @ 900mV
CPU set to 100 MHz @ 900mV
Does this then mean that the first option below uses less battery?
CPU set to 200 MHz @ 900mV
CPU set to 100 MHz @ 950mV
Or is there some other aspect of the 200MHz vs 100 MHz that affects the battery outside of the mV?
Hello Everyone!
I have a question regarding undervolting and overclocking.
I flashed ARHD 7. I am using stock Daemon Controller for virtuous_oc. I have very bad battery life atm so I tried to undervolt it a bit more. (Clocks are 122-1152MHz).
My VDD table is like this:
clock - voltage
122000 875
230400 900
307200 900
384000 925
460800 950
537600 975
614400 975
691200 1000
768000 1000
844800 1025
921600 1025
998400 1025
1075200 1025
1152000 1000
The reason I gave 1152000 only 1v is because my cpu were 75% at that clock, thatt is too much for me. Logically..i thought.. lower voltage would lover the time spent on that clock. Results: 35% at 122mhz and 50% at 1152mhz, other % are in between. But the battery life aint better.
BTW my system is superfast and stable.. no reboots or freezes nor anything.
Can someone suggests me what to do in this case? What are your VDD levels?
Thank you for your time
miHah
* *
jr0324 said:
I have very aggressive undervolt settings that work great for franco kernel m4
Stable CPU:
1344 (untouched - 1380 mV(don't use))
1228 (1250 mV)
1036 (1125 mV)
729 (975 mV)
384 (850 mV)
192 (725 mV)
Default CORE & IVA
Battery life is strong with these for me. I can forget to charge before I go to sleep with and moderate use throughout the day, wake up to ~35%.
Screen off: 384 max
Min CPU: 192
Max CPU: 1228
Governor: ondemand
Click to expand...
Click to collapse
(。_。) slowly backs away from this thread.
* *
....
pointless.
oh and op, that's not an agressive uv..
Sent from my i9250
I have searched around and couldn't find anyone talking about undervolt the voltage of CPU for our CPU, anyone can post their values as a guideline.
=================================================================
So far I have undervolt 384Mhz to 775 from 825, and tested stability for whole night burn test, it's stable and it gives me more than an hour standby time now.
Looking forward to test other frequency including 1.7GHz, so even overclocking the phone doesn't drain extra battery
P.S. my phone stands by at 384MHz according to CPU Spy Plus
Stock
MHz Vol
192 800
310 825
384 825
432 850
486 850
540 875
594 875
648 900
702 900
756 925
810 975
864 975
918 1000
972 1025
1026 1025
1080 1050
1134 1075
1188 1100
1242 1125
1296 1150
1350 1150
1404 1175
1458 1200
1512 1225
1566 1225
1620 1250
1674 1275
1728 1300
No body care about undervolting on Xperia S?
its at most by -100
Trust me, it helps with heating issued just that tiny bit
Envious_Data said:
its at most by -100
Trust me, it helps with heating issued just that tiny bit
Click to expand...
Click to collapse
Sorry, in details please. Thank you,
NoMoreAres said:
Sorry, in details please. Thank you,
Click to expand...
Click to collapse
All default voltages can be reduced by 100mv
Any lower and your cpu will reboot because of a saftey feature
Too high, and your cpu will burn out (also reboot)
Undervolting - giving a cpu les voltage per clock
Can save battery, can keep cpu cooler, can save cpu life
Over volting - does the oposite
Dont neccicarily know if this helped but i explained in more detail?
Sent from my LT26i using XDA Premium 4 mobile app
Hi
I have been working on google pixel 2xl in my research and I wanna understand the contents of the thermal-engine.conf file (I mean what each subroutine written there is doing)
many phones start throttling when the temperature of the cores exceeds some threshold, although in google pixel 2xl and according to what I understood from thermal-engine.conf file
it is rather based on a sensor called bd_therm2 as shown in the first subroutine in the thermal-engine.conf file
"[SKIN-MID-FLOOR2]
algo_type ss
sampling 2000
sensor bd_therm2
device cluster1
set_point 38000
set_point_clr 37000
device_max_limit 1804800
time_constant 0"
but this is not the only subroutine there and there are others and I do not understand what each subroutine is doing
although based on my experiments when bd_therm2 sensor exceeds 38 throttling starts
I appreciate if somebody directs me to some reference that explains these contents
The file contents are as follows (sorry my first time on that forum and I did not know how to attach it)
[SKIN-MID-FLOOR2]
algo_type ss
sampling 2000
sensor bd_therm2
device cluster1
set_point 38000
set_point_clr 37000
device_max_limit 1804800
time_constant 0
[SKIN-MID-LOW-FLOOR2]
algo_type ss
sampling 2000
sensor bd_therm2
device cluster1
set_point 40000
set_point_clr 39000
device_max_limit 1497600
time_constant 0
[SKIN-LOW-FLOOR2]
algo_type ss
sampling 2000
sensor bd_therm2
device cluster1
set_point 45000
set_point_clr 44000
device_max_limit 1190400
time_constant 0
[HOT-SKIN-VIRTUAL2]
algo_type virtual
trip_sensor bd_therm2
sensors tsens_tz_sensor13 tsens_tz_sensor0
list_cnt 2
weights 1 -1
set_point 39000
set_point_clr 36000
sampling 1000
math 0
[VIRTUAL-SS-GPU-SKIN2]
algo_type ss
sensor HOT-SKIN-VIRTUAL2
device gpu
sampling 2000
set_point 7000
set_point_clr 2000
device_max_limit 414000000
[SKIN-MONITOR2]
algo_type monitor
sampling 2000
sensor bd_therm2
thresholds 48000 50000 52000
thresholds_clr 47000 49000 51000
actions cluster0+cluster1+gpu cluster0+cluster1+gpu cluster0+cluster1+gpu
action_info 1094400+1190400+414000000 883200+902400+342000000 300000+300000+257000000
[BATTERY-MONITOR2]
algo_type monitor
sampling 2000
sensor bd_therm2
thresholds 50000
thresholds_clr 48000
actions battery
action_info 3
[SKIN-SHUTDOWN2]
algo_type monitor
sampling 1000
sensor bd_therm2
thresholds 54000
thresholds_clr 53000
actions shutdown
action_info 1
[SKIN-MID-FLOOR]
algo_type ss
sampling 2000
sensor bd_therm
device cluster1
set_point 49000
set_point_clr 48000
device_max_limit 1804800
time_constant 0
[SKIN-LOW-FLOOR]
algo_type ss
sampling 2000
sensor bd_therm
device cluster1
set_point 51000
set_point_clr 50000
device_max_limit 1190400
time_constant 0
[HOT-SKIN-VIRTUAL]
algo_type virtual
trip_sensor bd_therm
sensors tsens_tz_sensor13 tsens_tz_sensor0
list_cnt 2
weights 1 -1
set_point 39000
set_point_clr 36000
sampling 1000
math 0
[VIRTUAL-SS-GPU-SKIN]
algo_type ss
sensor HOT-SKIN-VIRTUAL
device gpu
sampling 2000
set_point 7000
set_point_clr 2000
device_max_limit 414000000
[SKIN-MONITOR]
algo_type monitor
sampling 2000
sensor bd_therm
thresholds 58000 60000 64000
thresholds_clr 57000 59000 63000
actions cluster0+cluster1+gpu cluster0+cluster1+gpu cluster0+cluster1+gpu
action_info 1094400+1190400+414000000 883200+902400+342000000 300000+300000+257000000
[SKIN-SHUTDOWN]
algo_type monitor
sampling 1000
sensor bd_therm
thresholds 66000
thresholds_clr 65000
actions shutdown
action_info 1