[APP] Msm7kCpuSpeed - Overclock Raphael/Diamond/Topaz/Rhodium/Blackstone/Whitestone

[APP] Msm7kCpuSpeed - Overclock Raphael/Diamond/Topaz/Rhodium/Blackstone/Whitestone - Windows Mobile Apps and Games

After LeoCpuSpeed to overclock the HD2, I've been working on overclocking the MSM7k SoC on the Raphael, with success. The same processor is present on the Diamond, Rhodium and the Topaz, so it should work on all of these devices. I've been able to underclock to 57MHz and overclock up to 710MHz, using small 19.2MHz steps. It can clock even further, but it depends on the quality of the processor in your device where the limit for you lies.
Supported devices
- Raphael
- Diamond
- Rhodium (check out this post for a nice guide and this app by oruam57 to prevent SOD)
- Topaz
- Blackstone
- Whitestone
- More?
Features
- The CPU speed is calculated from the actual clock registers, not via some dll or shady method.
- CPU speed is updated every 250ms (I haven't seen it auto-scale to other frequencies yet, but kept this feature from LeoCpuSpeed).
- A small dot blinks on each update so that you can see if your device hangs or not.
- Under- or overclock by moving the slider
- Automatically apply setting at boot
- While waiting for version 3 of this app, oruam57 made a little app that automatically scales down when the screen is off and overclocks again when exiting standby, effectively preventing SOD.
Notes on overclocking
1) AT YOUR OWN RISK
2) Only works while connected to AC power (depending on device)
3) The "604MHz" OC frequency is a special one. Only with this frequency set, you can remove AC power without having a lockup. So: after you overclock and want to remove your USB cable, set it to 604MHz first! You'll see it go back to the default 528MHz a second after you remove the cable. That's something the device does, not my app.
4) Overclocking while on battery gives insta-hang (for me). It seems this depends on the device.
5) Use "Apply at boot" wisely! If you use a setting that is unstable, your device may not boot up anymore! You'd need a hard-reset (factory settings).
When using TCPMP to benchmark the overclock, be aware that this tool overclocks the CPU, not the GPU.
Battery
I have not done any tests regarding battery life. The voltage to the processor is the same as when it is on 528MHz. It seems it cannot be increased. However, more speed will result in more heat, which means energy from your battery.
(And before you ask, I haven't performed any temperature tests either).
Screenshots
{
"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"
}
Versions
v2
- Enabled apply at boot option (Choose wisely, if your device hangs on boot, you'll need a hard reset)
- Fix app crash (trackbar exception) when going into standby
- Increased max freq to 902.4MHz for those fortunate enough
- SoD/hang on battery/etc not fixed yet
v1
- Initial release
Known issues
Q: My device hangs when unplugging from AC power
A: Read the overclock notes.
Q: When on battery and I press the "604MHz" button, it shows 604MHz for a brief second, and then goes back to "528MHz".
A: Some driver, module, or whatever in Windows Mobile enforces CPU speed every second, overriding the overclock. This is a known issue.
Q: My device hangs after standby (Sleep Of Death)
A: This is a known problem. Until fixed, only solution is to clock to "604" (the special frequency) before putting your phone away.
Q: Msm7kCpuSpeed crashes. When it does, and I click "details", it says something about System.Windows.Forms.Trackbar.set_Value.
A: This is a known problem. The app calculates frequency every 250ms. When the device goes into standby, there's a small window where the CPU is set to 19.2MHz, but my app isn't put to sleep by Windows Mobile yet. When in this small window, it calculates the frequency and updates the app, it crashes. This is because the lowest frequency in my app is 57.6MHz, and it can't find 19.2MHz (or 38MHz). Fixed in v2.
Credits
Thanks to phhusson and bzo for their overclock in the Linux kernel for MSM7k devices, where I could lend some code from.
And thanks to BASSMANBOB for letting me know such a tool is in demand.
Download
v2 HERE
v1 HERE

reserved space

Sweet...testing!

Hi NetRipper,
i hope that's real . I have installed the app without any issue on my phone (signature).
After starting the app the 528 MHz was shown.
A max from 787 MHz was possible to set.
>>The "604MHz" OC frequency is a special one. Only with this frequency set, you can remove AC power without having a lockup
I was able to set the 787 MHz and disconnect the AC power and no hangup.
I have to test now the BatterLifeTime. But this is at the moment not so important.

I confirm that there is no lockup after disconnecting from USB.

Working on Blackstone
Hi NetRipper,
I can confirm your tool works on the Touch HD (Blackstone). Made a short benchmark using SKTools Integer Test:
Result:
Default 528Mhz: ~295
710Mhz: ~425
It really boosts CPU performance! Any chance to get this working in Battery Mode? As you wrote the device crashes when trying to set a higher Value in Battery Mode.
Thank you very much!

Works for me, both plugged in and unplugged.
@ stock speed interger test gives about 310,
@710 gives about 440,
tested unplugged @710 ~440,
tested unplugged, program exited @710 ~440.
THANKS!
ps. haven't tested lock screen.
ROM is JACKOS S2 full version with recommended radio

waiting long time

bennib. said:
Hi NetRipper,
I can confirm your tool works on the Touch HD (Blackstone). Made a short benchmark using SKTools Integer Test:
Result:
Default 528Mhz: ~295
710Mhz: ~425
It really boosts CPU performance! Any chance to get this working in Battery Mode? As you wrote the device crashes when trying to set a higher Value in Battery Mode.
Thank you very much!
Click to expand...
Click to collapse
Thanks for letting me know it works on blackstone. Added that to the list.
I'm hoping I can get it to work in battery mode, but I still need to find the cause. I have the same issue on Leo also still, same cause probably. Will probably involve more disassembling and runtime patching to get this to work :s it's a pain.

Awesome... 750Mhz = 465
On battery working fine but I started in on AC though.
PS, unfortunately it is not quite stable at that speed but it looks cool anyway lol

Works on battery mode on Sprint Touch Pro 2. Max overclock of 768 without hangup. Exactly as when running Android!
Thank you for this wonderful app!

demonlordoftheround said:
Works on battery mode on Sprint Touch Pro 2. Max overclock of 768 without hangup. Exactly as when running Android!
Thank you for this wonderful app!
Click to expand...
Click to collapse
How are you testing stability...do you run it then exit and send the phone to sleep or standby for a few minutes?
Mine can go to standby (manually) but if I leave it there a few minutes then it wont come back.

Are you going to add "auto-apply at startup"?
Is it ok to cook this app into a rom?

shaolin95 said:
How are you testing stability...do you run it then exit and send the phone to sleep or standby for a few minutes?
Mine can go to standby (manually) but if I leave it there a few minutes then it wont come back.
Click to expand...
Click to collapse
Just happened to me as well. Going to set to 710 MHz and continue testing.

Sure you may cook it into your rom.
The reason "auto-apply at startup" is not enabled, is because it doesn't work on battery yet. Even for the guys where the phone doesn't hang, the overclock will be undone when on battery.
Or does the overclock stay active for some people on battery? I'd think it at least goes back to 528MHz.

NetRipper said:
Sure you may cook it into your rom.
The reason "auto-apply at startup" is not enabled, is because it doesn't work on battery yet. Even for the guys where the phone doesn't hang, the overclock will be undone when on battery.
Click to expand...
Click to collapse
OK, great job anyway! That's a big step in overclocking Rhodium.

shaolin95 said:
How are you testing stability...do you run it then exit and send the phone to sleep or standby for a few minutes?
Mine can go to standby (manually) but if I leave it there a few minutes then it wont come back.
Click to expand...
Click to collapse
That might be the same issue as when on battery. When it comes out of standby, it will try to set the clock speed again, causing the device to lock up. If you go to standby and go out of it right away, the device doesn't actually go into full-standby yet (it takes at least a few seconds before it does).
You can test stability by using SPB benchmark or something similar that does lots of calculations. I.e. I can clock it at 750MHz, but when I run a benchmark tool, it will hang. At 710MHz I'm stable.

NetRipper said:
That might be the same issue as when on battery. When it comes out of standby, it will try to set the clock speed again, causing the device to lock up. If you go to standby and go out of it right away, the device doesn't actually go into full-standby yet (it takes at least a few seconds before it does).
You can test stability by using SPB benchmark or something similar that does lots of calculations. I.e. I can clock it at 750MHz, but when I run a benchmark tool, it will hang. At 710MHz I'm stable.
Click to expand...
Click to collapse
I get the very same results on Rhodium (TP2) Verizon with MR2 rom in Battery mode.
If I do the quick standby (in and out) it works.
Letting the device go to sleep on its own locks the device and you have to do a battery pull to get it back.
Nice to see it come this far.

I set it to 710MHz and worked fine, unplugged the power cable and it stayed at 710MHz, but came back to check it about an hour later and it reverted to 528MHz as NetRipper said.
This is some great work NetRipper, hopefully you can figure out what in WinMo is reseting it on battery power.
Thanks again NetRipper.

Epsilion said:
I set it to 710MHz and worked fine, unplugged the power cable and it stayed at 710MHz, but came back to check it about an hour later and it reverted to 528MHz as NetRipper said.
This is some great work NetRipper, hopefully you can figure out what in WinMo is reseting it on battery power.
Thanks again NetRipper.
Click to expand...
Click to collapse
Did the device go to standby at all?

Related

[KERNEL][JetStream] DooMKernel [Rel:v01][Dt:04/Jan]

hello everyone,
i present to u the first custom kernel for the HTC JetStream!
i have developed kernels for Xperia X10, Xperia ARC, Xperia PLAY, Huawei Ideos X6, Samsung Galaxy SL, Kindle Fire, HTC Flyer and now i bring u my kernel for HTC JetStream!!! this is my first kernel for a MSM8x60 (Snapdragon S3 device)..
i dont have this device with me and so it was a pain getting this kernel working without device in hand but thanks to the testers it was possible!!!
special thanks to: bmw-boy, nmyseteroious & Russ741 for testing it out on their tablets!
[ disclaimer ]
OVERCLOCKING CAN BE DANGEROUS! U RISK THE HARDWARE GETTING DAMAGED!
PROCEED WITH CAUTION!
U HAVE BEEN WARNED!
I AM NOT TO BE HELD RESPONSIBLE IF U DAMAGE UR PHONE / SPILL UR COFFEE / MISS UR ALARMS / ANY OTHER CALAMITY/MISHAP
[ features ]
CPU overclocked to 2.052 Ghz
CPU underclocked to 192 Mhz
GPU overclocked to 320 Mhz
for safe booting CPU is capped at bootup to 1.536GHz/384MHz (max/min)
slightly undervolted (atleast for stock frequencies)
uses LZMA compression
added lots of fixing/patches (including CPU HOTPLUG notifications/CPU unaligned access) thanks to faux132
VDD CPU voltage control (@ /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels)
compiled using Snapdragon optimizations
PERFLOCK disabled
SWAP enabled
enabled few file systems support:
NTFS
NFS
CIFS
insecure kernel (ro.secure=0 & USB debugging enabled by default)
/system mounted as RW
[ credits for features ]
most of the stuff in this kernel is based on the work by faux132 and showp1984 on their HTC Sensation kernel!
thank you all for ur work!
[ requirements ]
stock HTC JetStream ROM (or ROMs based on it)
bootloader unlocked
working recovery
android app for overclocking like SetCPU (paid) or NoFrills CPU Control (free)
VDD control app: IncrediControl
[OPTIONAL] CIFS Manager (free)
[OPTIONAL] Swapper 2 (free)
[ how to install my kernel ]
download the provided kernel image & wifi module (zip file)
save the wifi module (zip file) to external sdcard
reboot device into fastboot mode (adb reboot bootloader)
flash my kernel using (fastboot flash boot kernelname.img)
reboot device (fastboot reboot)
enter recovery (adb reboot recovery)
flash the wifi module (zip file) via recovery (install zip from sdcard)
reboot phone and enjoy the kernel
FOR OVERCLOCKING
start SetCPU/NoFrills CPU Control app on ur device (or any other app which supports overclocking) (u may get a popup asking for SuperUser permissions, click ok/yes/allow)
now slowly increase the MAX slider to the right (one notch at a time) to increase the maximum frequency limit
DO NOT JUMP TO THE LAST POSSIBLE FREQUENCY
SLOWLY increase the frequency one notch at a time and do stability/testing for few hours
during testing never set "SET ON BOOT" option of these apps... u might get stuck in bootloops...
[ my kernel sources ]
https://github.com/DooMLoRD/HTC-JetStream-HC-Kernel
[ donations ]
if u feel that this work has helped u OR u think that the work i put into making this is worthy of donations, then click on the following link for buying me some coffee/beer/etc
PAYPAL DONATION LINK
[ downloads ]
[JetStream] DooMKernel v01 (mirror)
MD5HASH: dc8093f0b349f14580515e52be7f1fff
Wifi Module (mirror)
{
"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"
}
ENJOY!!!

reserved for later

what's the wifi module?
and also, i have no intention of OCing or UCing..will this kernel make a difference for me?

guru_shastri said:
what's the wifi module?
and also, i have no intention of OCing or UCing..will this kernel make a difference for me?
Click to expand...
Click to collapse
custom kernels need the corresponding wifi module for wifi to work correctly... else u will get error...
if u are not planning to OC then dont worry... the kernel will always boot at 384mhz/1536Mhz (similar to stock speeds)... so if u dont overclock using apps then kernel will never be run at those high clocks
though u might be interested in undervolting... CPU Voltage control interface is provided!!!

Interesting.
I have flashed many roms and mods but never delved into kernels much.
I don't plan on OC or UC either. Saying that, is SetCPU and VDD Control app still required to use the kernel for proper control?
I'm sorry if I ask basic questions. Like I said, not dealt with Kernels much before.

So what's the next to make our tablet flying

will it make the tablet quicker? without OCing that is...
and if something goes wrong - are the kernels at bmw-boy the stock ones? in case i'd need them
and i think all that is left is a proper ROM.
and than - just waiting for ICS.

I"m unsure if this is related to this kernel, but... after flashing, when i switch from Disk drive to charge only the jetstream freezes for quite a long while. Does anyone else experience this?

UC/OC
I have seen several posts making statements about "I have no intention to overclock...." etc. Why? One of the great benefits of using a custom Kernel/ROM is the ability to over/under clock the device (JetStream or whatever). Do you drive your car at exactly 45MPH and 2500RPM everywhere you go and park it on a treadmill at night so it can continue to turn the tires at 45MPH and 2500RPM? No you drive slow when needed and fast when needed. When you come to a traffic light you car idles and uses less fuel. This is what UC/OC is about. By using a dynamic CPU control (SetCPU or NoFrills) the CPU clock will increase/decrease as needed. SAVING you battery and giving you a performance boost when needed. Can you damage your processor? Sure you can, but you can damage it just as much by dropping it on the floor. Set the CPU controls properly (DooMLord tells you how above) and you wont have any negative affects. I have been UC/OC my several devices for years.
I tested this Kernel and have it running flat out at 2+GHz with no issues.
Enjoy the battery life extension, the better usability and DooMLord's hard work. He was up till about 5am his time yesterday testing.
Just my 2C.
Russ741

Russ741 said:
I have seen several posts making statements about "I have no intention to overclock...." etc. Why? One of the great benefits of using a custom Kernel/ROM is the ability to over/under clock the device (JetStream or whatever). Do you drive your car at exactly 45MPH and 2500RPM everywhere you go and park it on a treadmill at night so it can continue to turn the tires at 45MPH and 2500RPM? No you drive slow when needed and fast when needed. When you come to a traffic light you car idles and uses less fuel. This is what UC/OC is about. By using a dynamic CPU control (SetCPU or NoFrills) the CPU clock will increase/decrease as needed. SAVING you battery and giving you a performance boost when needed. Can you damage your processor? Sure you can, but you can damage it just as much by dropping it on the floor. Set the CPU controls properly (DooMLord tells you how above) and you wont have any negative affects. I have been UC/OC my several devices for years.
I tested this Kernel and have it running flat out at 2+GHz with no issues.
Enjoy the battery life extension, the better usability and DooMLord's hard work. He was up till about 5am his time yesterday testing.
Just my 2C.
Russ741
Click to expand...
Click to collapse
I actually take back what I said!
I am clocked at about 500/1800 min/max.
Though after I reboot, SetCPU forcecloses two or three times without me even opening the app. (And it is not set to boot)
I see this as an opportunity to learn more about kernels and UC/OC. I appreciate all of Doom's efforts and am happy to donate to him for it!

its not personal, and i have great appretiation for the work Doomlord put in it.
and i will flash it as soon as i could.
that being sayd, i don't think OC a device is a good thing. i'm happy with what i get right now, and i think there's a reason the CPU is clocked the way it is.
i've tried OCing in some of my past devices and never felt the difference besides having another app grinding my memory.
that's my opinion for now. it might change someday..

guru_shastri said:
its not personal, and i have great appretiation for the work Doomlord put in it.
and i will flash it as soon as i could.
that being sayd, i don't think OC a device is a good thing. i'm happy with what i get right now, and i think there's a reason the CPU is clocked the way it is.
i've tried OCing in some of my past devices and never felt the difference besides having another app grinding my memory.
that's my opinion for now. it might change someday..
Click to expand...
Click to collapse
as i told u earlier:
>>>
the kernel will always boot at 384mhz/1536Mhz (similar to stock speeds)... so if u dont overclock using apps then kernel will never be run at those high clocks
<<<

flashed it. everything seems fine so far...
let's see how it goes for the upcoming days.
should anything happen and i'd like to restore he original kernel - is it posted here somewhere? maybe it should be?

Battery Life
@DoomLord
Question, just by having the Kernel will I have a better battery life or should I do some configurations?
Thanks

sikorski said:
@DoomLord
Question, just by having the Kernel will I have a better battery life or should I do some configurations?
Thanks
Click to expand...
Click to collapse
There are already some optimizations to improve battery life... I will tell u later how to undervolt further to get even better battery life..
Sent from my HTC Flyer P510e using XDA App

EXCELLENT kernel!
prolly one of the best kernels I've EVER flashed and used with regard to battery life, speed, stability, etc. been runnin this kernel since it's first moment of release at 192mhz min/2.05ghz max/ondemand... absolutely NO crashes, NO reboots, NO heating issues (matter fact it runs cooler than stock pre rooting!). VERY GOOD job!!!! can/will u help us out in the Rezound community as well??

when I open the incredicontrol app, the app says that I need a Rom that supports the apps configuration methods.... ?

since i dont have the device with me i cant test but the CPU voltage VDD control interface will provide u with following features:
get the current CPU frequency/voltage table
Code:
cat /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
lower voltages for all frequencies
e.g.: lower voltage by 25mV
Code:
echo '-25000' > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
increase voltages for all frequencies
e.g.: increase voltage by 25mV
Code:
echo '+25000' > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
specify voltages for a particular frequency
e.g.: say u want to set voltage for 1536 MHz frequency to 1225 mV then:
Code:
echo '1536000 1225000' > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
here is a useful app:
http://rootzwiki.com/topic/4550-app09-beta-snapdragon-dual-core-oc-control/
may be someone can test it?
the current frequency/voltage table is as follows:
https://github.com/DooMLoRD/HTC-Jet...ernel/arch/arm/mach-msm/acpuclock-8x60.c#L220
all this can be made into simple init.d script
i will later post a update.zip to enable init.d support...

After flashing kernel and opening incredicontrol, this is what I get.
Advice?
Should I reflash the kernel? It flashed properly...

i reflashed. Still the same error message...?

[SCRIPTS][TWEAKS] Init.Doh | Battery & Performance | 0.4.6b | 3/16/12

{
"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"
}
Credits: Pikachu01, geko95gek, crypted, droidphile, User FeedbackFeatures:
Pikachu01's ThunderBolt! scripts (v2.6.1). (Also extracts the bolt_scripts onto the SDCARD)
80MB LMK Tweaks (v6 SuperCharger Memory Tweaks)
Crypted's GPS.conf for Quick Fixes
Ad Blocking Hosts file (5 of the best merged together)
Undervolted - Safe -50mV on most
Easy to tweak with ExTweaks
GPU Rendered UI Enabled
AFTR enabled, Sched_mc disabled. Siyah logger disabled. Custom Brightness, Touch Sensitivity Parameters, Static Bus Frequencies, Custom Deepsleep Levels, Dynamic hotplug, Logging disabled, Phone / Memory / SDCard / WIFI/3G/4G Tweaks, Hot Plug Thresholds, Sampling Interval & Frequency, Gtalk Wifi Only = False.
CPU set to: [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected]
Battery Version:
In this version you will be sacrificing some cpu & gpu performance for a decent amount of battery. Hotplugging checks at a slower rate for battery, Ondemand is tweaked for battery instead of speed. Minimum brightness levels are set lower, our #1 Battery Drainer.
100-1000Mhz
Ondemand/sio
GPU set to: 100/160/200Mhz | 800/850/900mV
Hotplug/Governor Tweaked for Battery
Performance Version:
This version you should be noticing a difference in benchmarks/responsiveness. The battery drain should be a little more than stock because of the overclocking. Hotplugging is set to Siyah Defaults, and lulzactive is tweaked for performance/battery.
100-1400Mhz
lulzactive/sio
GPU set to: 100/200/400Mhz | 800/900/1150mV
Hotplug/Governor Mostly at Stock/ThunderBolt!
Requirements:
Most of the Features will not work in ICS - Backup First
SiyahKernel v2.6.13+
ExTweaks Installed - If you wish to tweak init.doh
Files installed:
/system/etc/init.d/
S01logger - Disables Android Logging
S02sysctl
S70darky_zipalign - Zipalign
S91SuperCharger - Memory Tweaks
S98CFS - ThunderBolt! Kernel Tweaks
S98system_tweak - Most ThunderBolt! Tweaks
S92init_doh - CPU/Misc Tweaks
/system/etc/
gps.conf - GPS Tweaks
hosts - AdBlocking
SuperChargerAdj - LMK Memory Tweaks
SuperChargerMinfree - LMK Memory Tweaks
SuplRootCert - GPS Cert.
/system/
default.prop - LMK Memory Tweaks
/data/.siyah/
default.profile - Most of CPU/GPU Tweaks (ExTweak Profile)
Init.d scripts deleted each install:
Files Listed Above (Overwritten)
S98gekoh
s91voltctrl
Installation:
Download the latest zip below
Do a Backup in Recovery Mode
Flash Init.Doh in CWM (Recovery)
Reboot
The following steps are not required
If you now have 2 zipaligns scripts, please delete one of them (Keeping the one listed above)
Download Script Manager
Open Script Manager, Scroll down to the "bolt_scripts" on your sdcard
Open "sqlite_optimize", press the Skull/Bones icon "Su" and "Save"
Press Run, this will take a minute or two. Ignore the Errors.
It is finished when you see "Exit code 0", Click Close.
Run this script once once in a while (Whenever you have installed a few apps)
Updating/Changing Version: Just flash the latest zip and all the files are overwritten.
Uninstall: Download the file (uninstall_doh.zip) and flash it in CWM.
Note:
If you have any issues, try clearing your cache/dalvik
Give this script some time to work. At least one full batteries worth.
Some people give up after one SoD, just adjust the voltages up a little. Could also be kernel related (Read your kernels thread for latest issues)
This script changes at least once a week, so let me know if you run into any issues.
General Battery Saving Tips: - Thanks AndroidGX
Never use Tasks killer things or related.
Settings > Display > Touch key light duration : "OFF"
Settings > Display > Auto adjust screen power : [TICK]
Settings > Applications > Samsung Apps > "OFF"
Settings > Privacy > Back up my data > [UNTICK]
Settings > Location and security > Use wireless networks : [UNTICK]
Settings > Wireless and network > Wi-Fi settings > (press Menu button) > Advanced > Wi-Fi sleep policy > "Never" or "When screen turns off"
Deactivate auto sync for accounts
Deactivate GPS (and wifi gps)
Set brightness level to automatic/low
Disable motion
Changelog:
v0.4.6b: Upped Hotplugging a little. Disabled Static Bus. Changed back/updated to Crypted GPS v3.1 No-SSL. Smooth Scaling Enabled 2/2/2. GPU Thresholds changed to 90/50/90/50. Wifi/Phone Experiments added to bottom of S92init_doh. Should be a faster release without hopefully any additional battery drain.
[*]v0.4.5b: Lowered Hotplugging values. They were fairly ridiculous. Disabled sched_mc, redundant with hotplugging on. Freq_cpu1on back at 600hz. GPU Thresholds changed to 85/70/85/65 (Thanks droidphile). GPUSTAYCOUNT=2 on all. Upped ondemand/down_differential to 10.
[*]v0.4.4b: Changed freq_cpu1on to 800Mhz. Changed GPS Quick Fix to H3llstorm's. Updated Ad Blocking Hosts file. Uncommented Wifi/Phone Experiments in s92init_doh.
[*]v0.4.3: 2.6.13 Siyah Required. Moved most of the tweaks in init_doh to default.profile for the new 2.6.13 SiyahKernel. This will allow you to edit most of this in ExTweaks app. Added 80MB LMK v6 SuperCharger memory tweaks by zepp & Pika. Cleaned out most commented lines in system_tweak, and a couple AOSP issues. Updated ThunderBolt! scripts. Changed hotplug values / GPU steps for hopefully better battery. Changed scheduler to SIO. Choosing a lower minimum brightness for better battery. Commented out Experimental Tweaks in init_doh script.
[*]v0.4.2b: Few build.prop tweaks again, these from ICScrewD. You will see them at the bottom of init_doh under "Latest Experiments". Could cause AOSP issues. Also extracting bolt_scripts to both /emmc/ and /sdcard/, hopefully fixing some peoples complaints about it missing. Overall, just a small update.
[*]v0.4.1b: Deep Sleep Freq set back to 100-800 @ 400mhz bus. If .4.0 is working fine for you, no need to update.
[*]v0.4.0b: Deep Sleep Freq set to 100-500Mhz and bus @ 133Mhz (This could cause SoD's, let me know). Set Governor to Ondemand (Good Battery Life with Moderate Use), tweaked ondemand towards Battery Saving. Fixed 100Mhz mV to 925 (Instead of 920). Changed GPS fix to Crypted's patch (experiment). Back to 3 step GPU (100/160/[email protected]/850/900mV). 1000Mhz bus set back to 266Mhz.
Q: Where is my init.d folder? A: On your main storage. "/system/etc/init.d/". Find it with File Manager
Q: I want to change stuff like voltages/governor, but how? A: Browse to the init.d folder, open s99init_doh with a text editor such as Jota Text Editor. Trial and error from here.
Q: Cool story bro, but I can't edit/save the file. Wth? A: Calm down. The directory is read only. In file manager go to the directory, then open your menu -> more -> settings, scroll to the bottom and check root and mount. When u are finished, unchecked those two.
Q: How do I boot into recovery (CWM) mode? A: Through your power menu, through the CWM app on your phone, or: With the phone off, Vol-Up,Vol-Down, Power Button - Hold down at same time till your in recovery
Q: I tried hitting my power button recently, but the screen never came on (SOD). Whats up? A: Hard to say exactly, but lets start pumping the CPU voltages up. 25mV at a time. If it continues even at stock voltages, long-press power to reset the phone and then pull /proc/last_kmsg and let me know!A lot of people can push their voltages lower, I can too. Trying to make this script universal for us siyah people. Don't be afraid to increase/decrease your CPU voltages 25mV at a time, never go higher than stock in my opinion.
Undervolting is pretty much a placebo with your screen on. At most people save is 5% more battery with extreme undervolting. If you get one reboot, you may have drained more power than you have saved. If you want to save battery, turn your brightness low and choose a governor that stays away from the max freq the most. Your phone will also save a little more juice if you can handle 100Mhz as lowest state.
Stock CPU Voltages: [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected]
Stock GPU Voltages: [email protected] [email protected]
Backup your init.d folder if you want to be safe, this will overwrite all the files listed above. Also if you have a voltage control service, odds are that this won't work (at least the cpu/gpu/voltage tweaks).Go give thanks to: (Click on their names below)
Pikachu01 - 99% of the scripts
geko95gek - CPU/GPU/Voltage Settings, Tons of user feedback
Armisael - Misc Tweaks, User Feedback
stevehkim - Misc Tweaks, User Feedback
GadgetCheck - CheckROM, Misc Tweaks
droidphile - Amazing reference/guide
bedalus - Another Amazing Reference
crypted - GPS Quick Fix
H3llstorm - GPS Quick Fix
I9100 & SGH-I777 Community
To anyone I forgot: Thank you for all your hard workSiyahKernel Only: Download: Battery 0.4.6b | Performance 0.4.3p

Does it work on ICS?

Konstantinos said:
Does it work on ICS?
Click to expand...
Click to collapse
Doubt it. Parts of it would, so you could dissect certain things like the gps/hosts file. Thanks for bringing that up though, I have to remember you i9100 folks are currently in love with ICS. Us i777 have it way to buggy.
Update: I will check back later today to see if anyone has any issues.

love the name

Lets try it. Thanks!
Will give feedback after a day or so. Installed battery version
Sent from my GT-I9100 using xda premium

No harm in having something new to play with i guess. Great thread mate.

Just installed the performance version and it's working great coupled with Checkrom and Siyah. Thanks!
EDIT: Hmm, my SGS2 seems to be having issues with the three GPU frequency steps, as ShadowGun isn't running smooth anymore.

Toss3 said:
Just installed the performance version and it's working great coupled with Checkrom and Siyah. Thanks!
EDIT: Hmm, my SGS2 seems to be having issues with the three GPU frequency steps, as ShadowGun isn't running smooth anymore.
Click to expand...
Click to collapse
This is where I need your help. If you could, go into ExTweaks. In the gpu tab could you increase the first step to 160 2nd to 267. First step mV 850. 950mV for 2nd. Let me know how that runs.

cwc3 said:
This is where I need your help. If you could, go into ExTweaks. In the gpu tab could you increase the first step to 160 2nd to 267. First step mV 850. 950mV for 2nd. Let me know how that runs.
Click to expand...
Click to collapse
Tried changing the settings, but it seems it wasn't related to the settings of your script, but the kernel. Running stock now and everything is working as it should. Would definitely recommend this script for anyone wanting a little boost in performance!

Just checking in. Curious if anyone has any issues/recommendations. This script has over 1500 installs since last month in the i777 community. I am looking for ways to improve it, and your feedback is much appreciated.
Thanks again folks.

will try soon, after reflashing back to 100% stock KI4 on my S2
and this thread has the best appearance that i've ever seen on xda, really

Hi cwc3,
After recharge and your scripts it last 22 hours before my battery is empty with normal use.
It runs very smooth, where I expected some lags as its the battery version.
I have the feeling longer usage is possible if the voltage is set a bit lower. What do you think?
Sent from my GT-I9100 using xda premium
Checkrom v6

kart_man_21 said:
Hi cwc3,
After recharge and your scripts it last 22 hours before my battery is empty with normal use.
It runs very smooth, where I expected some lags as its the battery version.
I have the feeling longer usage is possible if the voltage is set a bit lower. What do you think?
Sent from my GT-I9100 using xda premium
Checkrom v6
Click to expand...
Click to collapse
Worth a try. I'm my tests, lowering voltages was more of a placebo. The voltages are found in the s92initdoh init.d script.
Did you notice any increase in battery? Typically you should notice a little lag when switching between things. The main battery saving from this script is going to be from the underclocking on both CPU and gpu.
Anyways, thanks a bunch for the feedback.

Hi,
I noticed big difference compared to stock, as that would empty my battery within 18 hours.
Sent from my GT-I9100 using xda premium

kart_man_21 said:
Hi,
I noticed big difference compared to stock, as that would empty my battery within 18 hours.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Glad to hear! I know I'm not thank button shy, but I also appreciate the feedback. If choose to continue using the script, be sure to let me know how things are going. Thanks kart man.

New Update
v0.4.5b: Lowered Hotplugging values. They were fairly ridiculous. Disabled sched_mc, redundant with hotplugging on. Freq_cpu1on back at 600hz. GPU Thresholds changed to 85/70/85/65 (Thanks droidphile). GPUSTAYCOUNT=2 on all. Upped ondemand/down_differential to 10.
Still experimenting with these values based off of peoples feedback/droidphile's thread. Be sure to let me know if you run into any issues, always looking for feedback.

cwc3 said:
v0.4.5b: Lowered Hotplugging values. They were fairly ridiculous. Disabled sched_mc, redundant with hotplugging on. Freq_cpu1on back at 600hz. GPU Thresholds changed to 85/70/85/65 (Thanks droidphile). GPUSTAYCOUNT=2 on all. Upped ondemand/down_differential to 10.
Still experimenting with these values based off of peoples feedback/droidphile's thread. Be sure to let me know if you run into any issues, always looking for feedback.
Click to expand...
Click to collapse
Mate nice to see this in the original android development thread..great stuff and some great tweaks you have going here..if there is anything i can do to help out feel free to PM me my friend.
Great job again..we should get this lot working for cm9 which i am currently using

Hi mate. Just flashed this, will give u feedback very soon. But so far after 2 hours its sweet! . Using the battery version.
Sent from my GT-I9100 using xda premium

I'm very Curious to try this on my ICS SGSII... lol is this working on ICS?
_____________________
Sent From OFFICIAL CM9 BUILD using SAMSUNG GALAXY S II

sam razzy said:
I'm very Curious to try this on my ICS SGSII... lol is this working on ICS?
_____________________
Sent From OFFICIAL CM9 BUILD using SAMSUNG GALAXY S II
Click to expand...
Click to collapse
Some of the features. Could you possibly backup and let me know? I can't touch ics for a few more days, and owning a sgh-i777 doesn't help either.

(DISCONTINUED)[KERNEL][JB] JellyKernel for Optimus L7 II (Single SIM)

DOWNLOADS:
BE AWARE, THAT DATA COULD GET CORRUPTED!!! ALWAYS MAKE NANDROID BACKUP BEFORE FLASHING MY NEWEST KERNEL BUILDS! I WON'T BE RESPONSIBLE FOR THE DAMAGE YOUR DATA GOT!!!! IT'S HIGHLY RECOMMENDED TO MAKE FULL DATA WIPE AND REFLASH SYSTEM, BECAUSE KERNEL IS ABSOLUTELY DIFFERENT FROM NOW ON!!!
Build 20150517-015 (STABLE)
HTML:
Fixed camera
Some more cpufreq driver updates
Build 20150516-012 (TESTING)
HTML:
Updated fat filesystem drivers, fixed some bugs
CPU usage dropped at idle
Heavy SLUB optimizations and fixes
Build 20150516-006
HTML:
Fixed some bugs regarding CPU access
Much better hotplug functionality (now you can leave mpdecision enabled)
CPU scaling optimizations
ext4 fix (one weird thing: after installing this kernel, startup wizard will appear - turn off wifi and go through all the procedure, otherwise you will be stuck at google login)
Fixes from LG G2 kernel
Build 20150515-001
HTML:
Tons of improvements
KGSL fixes, stability fixes, working scaling governor
Dynamic FSYNC
Made scaling drivers to work more efficiently
Lessened up chances of QDSP5 to crash in low memory situations, improved decoding
Stabilized wakeup/sleep switching
Several quirks for better interconnect between MDP and GPU
TONS of camera fixes, now it should work marginally better, provide better framerate when recording
Improved ZRAM efficiency
Introduced optimized percpu variable access, which improves performance a little bit
added optimized AES and SHA1 routines
Optimized Adreno drivers, reverted back to stock ones
AND TONS MORE OF STUFF!!!!
DOWNLOAD LINK:
https://www.mediafire.com/folder/78e7p85s3fc9p/KERNELS
Link for the source code:
GITHUB:
https://github.com/airidosas252/android_jellykernel_vee7

thanks for you work,i will definitely try this one.

This is definetly awesome news, I'd like to give a link from my rom to this kernel-can't implement it now, but I'd like to make new versions with your kernel, credits given. Great job, thank you!

Good thing I haven't posted this kernel yesterday. You would have gotten into a real mess: networking would stop working after some use of it.
It was a problem related to compilation. I've fixed it now and testing.
I will upload it to you a little bit later today. Sorry for waiting.
Sent from my LG-P710 using XDA Free mobile app

Please add swap support in next version of this kernel

Doing nandroid backup then im gonna test it,thanks. :good:

Ilyazzzz said:
Please add swap support in next version of this kernel
Click to expand...
Click to collapse
It is there.

i tested the kernel a couple of hours,maybe i made something wrong cause the phone was heating and everytime i exit an app i had redraws on the home screen,some apps just close after using them,without the warning of a FC,like testing the kernel with antutu qhen it reaches 80% the app just closes. And it made the phone slower.
When i made the backup restore i lost a few apps none of them are important,i can download them again.
I used no frills cpu with smartassH3 and vr,with the kernel in max OC and min UC values,and i did not touch the gpu frequency,because i dont know hot to do that.
So basically im not saying the kernel its bad,is that maybe i neded to use another app in order to have better perfomance
So,yes i need help or just point me into the right direction so i can search about it.
I've been using modified kernels,since xperia x10,but this its the first time i have these problems.
And thanks again for your work and effort.

As I mentioned in the thread, avoid using 500 MHz GPU clock. This is the most obvious thing, that makes phone unstable. Set it off using Trickster MOD.
Don't know, why mine is rock stable for like 3 days now (there is something wrong with deep sleep, though. I think different toolchain is responsible for such issue).
I even broke into 10000 (10420 points) mark in Antutu, so yeah... Definitely something's wrong on your phone.
With stock kernel my phone was very laggy, always redrawing no matter which launcher, stutter in almost every game (now even Hungry Shark doesn't lag anymore).
Sent from my LG-P710 using XDA Free mobile app

airidosas252 said:
As I mentioned in the thread, avoid using 500 MHz GPU clock. This is the most obvious thing, that makes phone unstable. Set it off using Trickster MOD.
Don't know, why mine is rock stable for like 3 days now (there is something wrong with deep sleep, though. I think different toolchain is responsible for such issue).
I even broke into 10000 (10420 points) mark in Antutu, so yeah... Definitely something's wrong on your phone.
With stock kernel my phone was very laggy, always redrawing no matter which launcher, stutter in almost every game (now even Hungry Shark doesn't lag anymore).
Sent from my LG-P710 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for the response,but mate,as i mentioned ,i never touched the GPU frequencies.because i was using only no frills cpu in order to use the max oc and the min oc for the cpu.
I will check that app (trickster mod) asap, right now im at the work,also,if you can ,can you tell me your settings please?
And thanks again.

kalel29 said:
Thanks for the response,but mate,as i mentioned ,i never touched the GPU frequencies.because i was using only no frills cpu in order to use the max oc and the min oc for the cpu.
I will check that app (trickster mod) asap, right now im at the work,also,if you can ,can you tell me your settings please?
And thanks again.
Click to expand...
Click to collapse
Regarding GPU frequencies, it's the same deal as the CPU frequencies, although changing it could either improve performance or make it worse more drastically.
There's nothing so special about my settings: Using 1024 Kb of sd cache, sio i/o governor, smartassv2 cpu governor, leaving both cores online all the time (deleted mpdecision binary from /system/bin folder, because it's too poor for keeping optimal on and off switching of second CPU core). From OS side I've deleted every possible LG app (left nearly at AOSP level), disabled logcat (because I don't need such right now), using Class 10 microSD card, because it won't bottleneck the phone too much. So that's about it.

airidosas252 said:
Regarding GPU frequencies, it's the same deal as the CPU frequencies, although changing it could either improve performance or make it worse more drastically.
There's nothing so special about my settings: Using 1024 Kb of sd cache, sio i/o governor, smartassv2 cpu governor, leaving both cores online all the time (deleted mpdecision binary from /system/bin folder, because it's too poor for keeping optimal on and off switching of second CPU core). From OS side I've deleted every possible LG app (left nearly at AOSP level), disabled logcat (because I don't need such right now), using Class 10 microSD card, because it won't bottleneck the phone too much. So that's about it.
Click to expand...
Click to collapse
ok then,thanks i will try the same settings,also i have a 16gb,class 10 microsd card,and deleted all the lg apps that i dont use. :V
thanks for the reply.

Any possibility of USB OTG being implemented anytime soon?

CrashBandicootX said:
Any possibility of USB OTG being implemented anytime soon?
Click to expand...
Click to collapse
I don't know. It's in the same position as it was in Kitkat - drivers are included but it just doesn't work.
I'll try talking to other developers.

RAM
Hello! :cyclops:
Is there any form to optimize the RAM usage? Any application or something? Greenify works?

Im using v2,everything runs better,and its feels smoother,the only thing that i noticed is that i lost data in some apps,had to disable superSU,and Xposed,and open all the apps that requiere root,in order to regain access to the apps that use superSU again,and finally when im using antutu in order to see how is the perfomance it just closes when its about to finish the benchmark,always,besides that minor thing,the kernel its solid,im using no frills cpu with max freq in 1037mhz,min in 245 mhz, sioplus and smartassh3,(im not touching GPU freq),but every time i restart the phone,the values doesnt stay,y have to manually change the governor and scheduler.

Sorry dude,thanks for your effort but i think my phone doesnt like your kernel,i used trickstermod,no frills,set cpu,and the antutu one,and everytime y reboot the phone the kernel has the default settings again,min freq in 245,max freq in 1,036,and it returns also to ondemand and sio.
:/
I made a backup of my kernel,what partition do i need to restore in order to have the old kernel back?????
and again,thanks.
P.S. a friend is using same kernel in his phone,he is using stock firmware,odexed and im using a custom rom,deodexed. And its the same result in both phones.

@kalel29
To restore old kernel in CWN go to advanced restore and choose boot

sasa g said:
@kalel29
To restore old kernel in CWN go to advanced restore and choose boot
Click to expand...
Click to collapse
Yeah, now I'm encountered certain problems and I was testing backported Kitkat kernel for some time now.
That one is miles better than Jellybean's one (it is too buggy, because simply compiling breaks certain things)
Kitkat kernel, at least, puts phone to sleep state properly (now my phone stays cold throughout whole day, if I don't use it at all, while with Jelly Bean's one, it was always warm, sometimes even hot)
And yeah, sorry, who feels, that posted kernel causes some problems. It is addressed now and fixed.
I'm not an expert in C code, so some specific programming issues are unsolvable for me.
And the feedback is always welcome for me.

[UPDATED][TUTORIAL] Have better Battery Life on TW 5.1.1

I have lose root after flash of kernel

Marco2701 said:
I have lose root after flash of kernel
Click to expand...
Click to collapse
That happens if you flash the kernel. But to get the root access again, simply flash this.
And btw, thank you for reporting that bug that I known but I forgot. Anyway, that information was added in the thread, so if anyone experience that bug too, they'll have the solution in the thread
But again, thank you

The Forgotten said:
That happens if you flash the kernel. But to get the root access again, simply flash this.
And btw, thank you for reporting that bug that I known but I forgot. Anyway, that information was added in the thread, so if anyone experience that bug too, they'll have the solution in the thread
But again, thank you
Click to expand...
Click to collapse
Thank you so much

"Disable any kind of synchronzation
Disable WiFi, Mobile Data, GPS and etc when you're not using them
Keep Power Saving Mode always on
Keep the phone's brightness at the minimum possible
Uninstall any app related to Facebook, like Facebook itself and Messenger.".....
Hahaha...its easyer to simply Power off the phone��
For ME ,skype,FB,viber,email was minimum to alltime runs on device.
Some tips to battery save:
automatic brightness off...change it manualy because sensor drains batt.
If not bánt fast drain simply disable mobile data ....wifi on 24h US aproximately 8-10mah...useless to disable if not connected at any Network...
With thats, with factory batt u rease circa 4-4.5h of screen on time ,at 75%wifi and 25%mibile data use.
Cpu settings not significantly influent the battery drain.Just overclock or power draining governor mode was result fast drain.
My suggestion is: ondemand or factory...
io: @tw use factory settings... @CM bfq 512M or 256M.
GPS was not significantly results draining.
Extra sized battery not recommended because kernels not able to correct use of it... just with replace it and restart the phone was resulting longer using time... my 7200mah anker after 3 replace and restart, results circa 3.5days and 10-12 h ours of screen time... of course with higher mobile data using this times was shorter.
I hope thats helps anybody ��

needforszpit said:
"Disable any kind of synchronzation
Disable WiFi, Mobile Data, GPS and etc when you're not using them
Keep Power Saving Mode always on
Keep the phone's brightness at the minimum possible
Uninstall any app related to Facebook, like Facebook itself and Messenger.".....
Hahaha...its easyer to simply Power off the phone��
For ME ,skype,FB,viber,email was minimum to alltime runs on device.
Some tips to battery save:
automatic brightness off...change it manualy because sensor drains batt.
If not bánt fast drain simply disable mobile data ....wifi on 24h US aproximately 8-10mah...useless to disable if not connected at any Network...
With thats, with factory batt u rease circa 4-4.5h of screen on time ,at 75%wifi and 25%mibile data use.
Cpu settings not significantly influent the battery drain.Just overclock or power draining governor mode was result fast drain.
My suggestion is: ondemand or factory...
io: @tw use factory settings... @CM bfq 512M or 256M.
GPS was not significantly results draining.
Extra sized battery not recommended because kernels not able to correct use of it... just with replace it and restart the phone was resulting longer using time... my 7200mah anker after 3 replace and restart, results circa 3.5days and 10-12 h ours of screen time... of course with higher mobile data using this times was shorter.
I hope thats helps anybody ��
Click to expand...
Click to collapse
Bro, if you simply turn off your phone, you won't receive calls.
Thank you for reminding me of the automatic brightness one, I really forgot about it
And yes, CPU Settings will influenciate the battery a lot. You really don't know how governors work, right? And with those instructions, I disabled the CPU Boost, a function that's not needed in most of the cases. And yes, overclocks and the "power draining" governor aka performance governor drains more, but every bit of battery is precious.
And btw, bro, OnDemand is the factory CPU Governor. Please do some research before posting.
But, anyway, thank you ^^

Nice thread

SoUnd001 said:
Nice thread
Click to expand...
Click to collapse
Thank you ^^

Nice work bro.

Themes / Apps / Mods [ROOT] Thermal engine mod ver 1.1

If you are annoyed by your device switching refresh rate to 60FPS or that you are unable to record a video for more than 2 minutes say no more! According to my findings
Sony maxed out all the frequencies without any throttling during camera usage and applied kill switch at 55C.
As for any other use case scenarios, there is an aggressive throttling and forcing screen back to 60FPS, with an exception of using Xperia Stream or Endurance modes. As you may have guessed that these limitation are not to protect the device, but avoid any law suits from people who burned their hands.
Behold!
I present you thermal config mod that will make your device usable and keep your hands warm.
Of course at your own risk, I do not take any responsibility for broken devices, burned hands, radiation sickness or any other catastrophic events.
Description:
During your normal usage (not gaming or camera) the throttling will remain the same, BUT your screen won't switch back to 60FPS.
If you add your game/app to the game enhancer and select "performance profile" it will throttle way less aggressively. Max temperature is changed from 56C to 61C, screen refresh rate will only drop if the display itself will reach 45C.
In "balanced" profile the temperature limit is set to 58C, frequencies are limited to 1574Mhz (Little)+1651Mhz (Big)+2054Mhz(Prime)+545Mhz(GPU).
"Battery mode preferred" is set to 57C with the following limits: 1267Mhz+1325Mhz+1728Mhz+492Mhz.
{
"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"
}
Camera related profiles are set to 63C.
Video recording profile is set to endurance mode (66C temp limit) with a little bit of throttling to cool device down
During recording device will show warning, but won't disable camera functionality. However if the camera module itself will reach the limit temperature (untouched by me), the recording will stop. Additionally modem might be temporary switched off to cool device down.
Is this safe?
As safe as using endurance mode.
I took thermal profile for Xperia Stream dock thermal limits from endurance mode, so it is relatively safe for the device, but may not be as safe for you, if you have sensitive skin.
I strongly recommend using stick/stand when recording high quality videos for a longer periods of time.
Instructions:
You need root and magisk.
Install this module
GitHub - HuskyDG/magic_overlayfs: Make system partition become read-write (it is also possible without Magisk)
Make system partition become read-write (it is also possible without Magisk) - GitHub - HuskyDG/magic_overlayfs: Make system partition become read-write (it is also possible without Magisk)
github.com
After rebooting go to oem/etc with any root file manager, enable R/W and replace the thermal-engine.conf and change.cfg for newer versions.
Make sure to set the same permissions and backup original files.
In the end you may want to go to /data/adb/modules/magisk_overlayfs and modify mode.sh to lock partition again (mode 2), this is done to avoid some apps detecting traces of modified system with Momo app.
Additionally I recommend undervolting GPU.
Thanks to @ragu24 for pointing at the right direction.
To do so:
Install konabess and select your GPU (should be in the middle).
Backup old image.
Then go to import/export.
Export your config (backup).
Import config txt that I shared.
Save GPU freq table.
And then repack and flash image.
After rebooting check the frequency table if the UV applied correctly.
Have fun!
Changelog
0.1 initial release:
Kill switch disabled
Applied Xperia Stream profile to Game Performance and camera
0.2 version:
Slightly raised screen temperature limit (it was lower in gaming mode)
Modified general camera profile (non stock app?)
0.3 version:
Disabled screen fps drop for other game profiles (unless screen itself is hot)
Returned kill switch (previous version will not stop unless other sensors show high temp)
Raised temperature till 64C for camera and game performance profile
0.4 version:
Less aggressive throttling for best performance (Game performance and camera profiles)
Raised temp to 66C for video recording and game performance profiles (endurance mode)
For other camera related profiles I limited temp to 63C
Switched modem to endurance mode on a game performance profile, however during long video recording modem may be temporary disabled to reduce device temperature
1.0 version:
Introducing modified "battery life preferred" and "balanced" profiles for Game Enhancer (Also thermal limit in custom settings should do the trick)
"Battery life preferred" temp limit: 57C, Max frequencies: 1267Mhz(Little)+1325Mhz (Big)+1728 (Prime)+492Mhz (GPU)
"Balanced" temp limit: 59.5C, Max frequencies: 1574Mhz+1651Mhz+2054Mhz+545Mhz
1.1 version:
Reworked game enhancer profiles to have dynamic frequency adjustment instead of aggressive throttling
Restricted limit for performance profile to 61C
Restricted limit for balanced profile to 58C
Disabled modem endurance mode for performance profile, since device doesn't heat that much anymore (back to stock change.cfg)
Made sure that underclocking kicks in instantly on balanced and battery safe profiles
Minor bug fixes

Also for xperia 1 iii with A13 ?

Pandemic said:
Also for xperia 1 iii with A13 ?
Click to expand...
Click to collapse
You have different frequencies and no Xperia Stream support, but we can use profile for endurance mode.
Share your config I will take a look.

V 0.2 Update
Slightly raised screen temperature limit (it was lower in gaming mode) and modified general camera profile (non stock app?)

0.3 Update
Disabled screen fps drop for other game profiles (unless screen itself is hot)
Returned kill switch (previous version will not stop unless other sensors show high temp)
Raised temperature till 64C for camera and game performance profile (same as endurance mode)
P.S.
Seems like Sony maxed out all the frequencies without any throttling and then just shut it it off after it reaches 55C during video recording. No wonder why it overheats lol

Thank you! just installed v0.3, you actually made me root my phone AGAIN just to enjoy this. wow.
i was wondering if i should keep stock and buy a stick for endurance mode or just root for free, and i chose the free and comfortable option.
ps. i also tried seeing what will happen if i flash different region firmware (54 on 72) - it seemed to work, and i could scan barcodes for e-sim cards, but unfortunately reception wasn't working with the different region firmware. now when i am rooted, i will see if it is possible to flash different MBN files to get VOWIFI working (LET+5G works)

Orof said:
Thank you! just installed v0.3, you actually made me root my phone AGAIN just to enjoy this. wow.
i was wondering if i should keep stock and buy a stick for endurance mode or just root for free, and i chose the free and comfortable option.
ps. i also tried seeing what will happen if i flash different region firmware (54 on 72) - it seemed to work, and i could scan barcodes for e-sim cards, but unfortunately reception wasn't working with the different region firmware. now when i am rooted, i will see if it is possible to flash different MBN files to get VOWIFI working (LET+5G works)
Click to expand...
Click to collapse
Haha, I rooted just to see if it will be possible to implement this mod and pure black background in apps.
Unfortunately you can't just buy any stick and enable endurance mode, device needs to be connected to some external device via usb/hdmi. It almost seems like a way to encourage people to buy compatible accessories.
As for different regions I don't think you can enable e-sim on the device that doesn't has the module. Also if you flash Japanese firmware you will have voice recording for calls, but nfc module will break, because they use different technology.
As for enabling VOWIFI it might be possible. You newer know if the difference is in hardware or just limited by software. For example I converted my XZ premium to dual sim by flashing firmware and replacing sim tray.
You can either experiment with newsflasher or manually.
With overlayFS you can "write" to system partitions(unless it's root folder like system or oem), I think I saw something related to connectivity in /product partition.
Just use unsin tool to unpack part of firmware in open it with 7zip.
In case a failure it's nice to have a bootploop protector module, or you can boot in safe mode to disable magisk and start over. However my mod will need reinstallation too.

Suggestion - a couple of changes to the throttle behavior.
this is how phone throttles after 20 mins of CPU test with a fan on the case. as you can see - no dips, very high performance.
however, this is how the phone behaves when there is no fan attached to the phone (and the phone is without a case):
this suggest that some throttling adjustment is in order, as playing games with this amount of throttle will surely be noticeable.
for reference, this is how the phone throttles on stock profile:
if we can make the temp more consistent and less frame drops - it will be great (not needing to use a fan as well)
EDIT - Throttling behavior from stock is from the original firmware. it should be possible to extract the thermal engine from the initial catches of the Xperia 1 IV and apply them to the current software (currently the phone throttles more than it did in the past, to around 170k points)
app is CPU Throttling Test

@Orof , thank you for your tests! Frame drops are unavoidable, that's the "kill-switch". Without it temperature will keep rising and rising, CPU needs to cool down somehow.
How many threads do you use in CPU Throttling test? I don't think default is enough, as with Burnout Benchmark I was able to trigger modem overheat warning when I disabled kill-switch.
I am working on the new version based on endurance mode with throttling at 57C and kill switch at 66C( max for endurance). It may restrict modem when the temperature will be high enough (Happened during 30 minutes recording [email protected]). Gonna do couple of tests and upload it.

New version is up!
There are two files inside archive now, same logic applies with replacing and setting permissions.

Annnd still hitting the kill switch for some reason (using the new files)
I wonder why. I wish the throttling was more aggressive so that the kill switch wouldn't be met, while still gaining more performance than stock (215,000 according to gsmarena)
*EDIT -changed the threads amount from the default value (20) to 60, still the same.

Orof said:
Annnd still hitting the kill switch for some reason
View attachment 5916741
I wonder why. I wish the throttling was more aggressive so that the kill switch wouldn't be met, while still gaining more performance than stock (215,000 according to gsmarena)
*EDIT -remembered yo change the threads amount.was testing the default value (20). How many did you test?
Click to expand...
Click to collapse
I used 20 threads.
Maybe you have higher ambient temp?
Also it seems that every device is different for some reason. Some people can film for 15 minutes 4k120fps, others see the thermal warning while just taking photos.
Did you try limiting frequencies with FKM?

Doom Slayer said:
I used 20 threads.
Maybe you have higher ambient temp?
Also it seems that every device is different for some reason. Some people can film for 15 minutes 4k120fps, others see the thermal warning while just taking photos.
Did you try limiting frequencies with FKM?
Click to expand...
Click to collapse
I reckon that the higher ambient temp is the issue here, though it doesn't mean that it throttling cannot be initiated sooner or harder to avoid the kill switch, for those who live in a higher temp locations
Will try limiting via FKM. Can already confirm that via the default perf setting (without the mod), score stabilize at around 170-180k with no sudden jumps, so it is something we should be able to do with a bit more tinkering.
Thanks for all the work! I really appreciate it.

Orof said:
I reckon that the higher ambient temp is the issue here, though it doesn't mean that it throttling cannot be initiated sooner or harder to avoid the kill switch, for those who live in a higher temp locations
Will try limiting via FKM. Can already confirm that via the default perf setting (without the mod), score stabilize at around 170-180k with no sudden jumps, so it is something we should be able to do with a bit more tinkering.
Thanks for all the work! I really appreciate it.
Click to expand...
Click to collapse
With aggressive throttling it will be very similar to kill switch. It will lower frequencies until device will slightly cool down and will do it again after it will heat. On stock it just happens very soon a major performance cuts that's why it's stable on the benchmark. Same can be achieved by locking frequencies with FKM for a specific app/game.

Doom Slayer said:
With aggressive throttling it will be very similar to kill switch. It will lower frequencies until device will slightly cool down and will do it again after it will heat. On stock it just happens very soon a major performance cuts that's why it's stable on the benchmark. Same can be achieved by locking frequencies with FKM for a specific app/game.
Click to expand...
Click to collapse
Thanks for the explanation, I understand now why it behaves this way on stock
I wonder if I can fine-tune the frequencies by editing the thermal-engine.conf (and maybe the change file as well) without needing to use FKM. already tried to make some changes to version 0.3 with no meaningful success. will have to dig deeper
Cheers!

Orof said:
Thanks for the explanation, I understand now why it behaves this way on stock
I wonder if I can fine-tune the frequencies by editing the thermal-engine.conf (and maybe the change file as well) without needing to use FKM. already tried to make some changes to version 0.3 with no meaningful success. will have to dig deeper
Cheers!
Click to expand...
Click to collapse
Try the uperf mod in combination with the modified thermal config file!
It's dynamically able to adjust the frequencies on the fly - just like FKM but dynamic! Combined with the higher thermal limits it should allow for a smoother experience

ragu24 said:
Try the uperf mod in combination with the modified thermal config file!
It's dynamically able to adjust the frequencies on the fly - just like FKM but dynamic! Combined with the higher thermal limits it should allow for a smoother experience
Click to expand...
Click to collapse
Thanks for the suggestion, but when trying to install it on the Xperia using Magisk, installation failed because "Taro is not supported". will try different versions of it ans report back

Orof said:
Thanks for the explanation, I understand now why it behaves this way on stock
I wonder if I can fine-tune the frequencies by editing the thermal-engine.conf (and maybe the change file as well) without needing to use FKM. already tried to make some changes to version 0.3 with no meaningful success. will have to dig deeper
Cheers!
Click to expand...
Click to collapse
You can try, just make sure to reuse the frequencies from the config like from game save profile.
Basically we have a choice either to have a higher performance with a little bit of drops or lower performance, but more stable.
On default profiles CPU just cust performance in half when it reaches 53C. Which happens like after 1 minute of CPU Throttling Test.
Anything below that reduction will not prevent CPU from building up the heat, but will slow it down. Without external cooling best you can do is to prolong that performance drop moment or castrate your CPU and "enjoy" stability.
Drops are necessary to keep device from going above maximum temperature (when I completely disabled thermal engine it easily went above 70C) because device sucks at getting rid of heat passively.
Main motivation to create this mod was to prolong video recording time, get rid of annoying screen refresh rate switch, as it causing flickering and squeeze a bit more fps out of emulators with prolonging the moment when the CPU gets castrated.
These synthetic tests do not reflect normal usage. If any game or app behaving like that it means poor optimization with an exception of emulators. It's up to users to configure each game to find a balance between stability and better graphics/more fps.
I'am planning to eventually edit balanced and battery safe profiles inside game enhancer, but don't expect miracles.
Meanwhile if anyone wanna contribute, you may lock frequencies with FKM and run the thermal throttling test on each, to find the one which is more stable, so I can use this data in modified balanced game profile.

Orof said:
Thanks for the suggestion, but when trying to install it on the Xperia using Magisk, installation failed because "Taro is not supported". will try different versions of it ans report back
Click to expand...
Click to collapse
I use this one - one of the latest

New version is up!
Basically it eliminates the need to have FKM, as balanced and battery life profiles in game enhancer will castrate frequencies as soon as possible , which will slow down heating (what the point of having maximum performance for a minute anyways? ) and result more stability.
Frame drops may appear sooner or later, depending on your ambient temperature, if you are using my undervolting profile, phone case (all my tests run in aramid carbon fiber case) and in general it seems that it's random for each device.
Battery safe profile
Balanced profile

Better Mobile App

welcome