Database Users

We can now overclock our phones!

Couldn't really see any discussion on this yet, and personally it's in a location on the forum that I rarely visit but I've found an overclock tool that is slowly becoming very good indeed for our processors. Link to thread is here. I'm soo far up from 528Mhz to 748Mhz (been stable for the past 6 hours no problem). Just make sure to follow the thread (instructions are linked to ensure overclock remains applied through scripts and 3rd party apps). Should take no longer than 30mins for a well versed user to set up. Please don't try this if you haven't got a clue what you are doing as there is soo much scope for error and dead phones! You may also need to customise any scripts to your specific phone/software build. CDMA phones as usual are different from what I've heard. But anyway good luck, I'm gonna keep trying to push the Mhz up (aiming for 850Mhz ).

Not sure its a good idea to go past 700 mhz,our phones run hot as it is under capacity,as with gaming rigs heat is your Enemy,the cooler you keep it the faster.

It's actually remained pretty cool, and when it's in my pocket it's only running at stock clocks anyway. Only when I'm using it does it get to the full 748Mhz. Running wifi router and charger and temps are not noticeably hotter than usual...

um... ive been clocked up to 787 highly stable for the last like 2 weeks. No heat problems, no battery problems, just insane speed.
recommendations: Download v1, not v2. ESP if you dont know what you're doing. Then download the zip im attaching, there's 2 mortscripts in there and a registry addition, THESE MUST BE IN THE STORAGE CARD ROOT. use the regisitry addition FIRST (just associate w/e regedit software you use, then run the .reg file in total commander), then go back to total commander, edit the .mscr "Toggle_boost" and adjust the value boost = "x" to whatever value you want the phone to OC at, eg boost = 41 is 787mhz which is stable for me, test yours out.
THEN, open and install rhodiumkbdcontrol (attached), reboot, go to settings>system>keyboard config> add key
1st pick which key you want to be the OC boost swtich, I have it mapped to my PTT button. click the plus sign, drop down menu, run program, then highlight "run program" in the list then click "..." then type in
Program: \windows\mortscript.exe
Arguments: "\storage card\toggle_boost.mscr"
This time you wanna use the power key.
same general instructions except
Program: \windows\mortscript.exe
Arguments: "\storage card\boost_off.mscr"
then plus sign again, drop down menu, default key action, and click extended emulation. THEN hit update config. should work like a charm, also autoover clocks to 610, the boost button with send you up the w/e the boost = "x" is set to, and then back again, most find 710mhz to be the stable point, and feel free to ask questions

sorry, heres the zips

wouldnt overclocking also gives you a higher chance of frying your CPU chip? cuz ive seen it happened in PCs i just idk about PPCs

I agree that there are virtually no ill effects to this. When unlocked, I have my phone running at 787 mhz. While it is locked or sleeping it throttles down to 604 and eventually 528 mhz. I have noticed no extra heat nor extra drain on the battery. Just blazing fast speed! Sense 2.5 is virually not laggy at all! CHT 1.8.5 is so smooth and quick even with the aminations enabled!
If anyone is interested in the automated clocking process, I can help by giving my set-up that is working flawlessly on the ROM in my signature!

miked79928 said:
I agree that there are virtually no ill effects to this. When unlocked, I have my phone running at 787 mhz. While it is locked or sleeping it throttles down to 604 and eventually 528 mhz. I have noticed no extra heat nor extra drain on the battery. Just blazing fast speed! Sense 2.5 is virually not laggy at all! CHT 1.8.5 is so smooth and quick even with the aminations enabled!
If anyone is interested in the automated clocking process, I can help by giving my set-up that is working flawlessly on the ROM in my signature!
Click to expand...
Click to collapse
Yeah could you hook that up? I think posting it here would be best but pm'ing works just as well
Edit:
I just read threw the above links and guides and was wondering if there is a more automated way of setting this up rather than having to link it to a button press. I'm guessing this has not been figured out yet (or the guides would have mention of it ). Just curious.

dantegl36 said:
Yeah could you hook that up? I think posting it here would be best but pm'ing works just as well
Click to expand...
Click to collapse
Here is the best way I have found to do it. I take absolutely no credit for this:
http://forum.xda-developers.com/showpost.php?p=7354283&postcount=627

Check it!
Outlaw78a said:
Not sure its a good idea to go past 700 mhz,our phones run hot as it is under capacity,as with gaming rigs heat is your Enemy,the cooler you keep it the faster.
Click to expand...
Click to collapse
I have used this, NRG also does. I have NEVER had any problems and mine is as high as 787 as long as I'm running it which is constantly.
XITruthiX said:
um... ive been clocked up to 787 highly stable for the last like 2 weeks. No heat problems, no battery problems, just insane speed.
Click to expand...
Click to collapse
100% agreed. Been running at the highest speeds with NO problems, no batt drain, no heat probs, nothing.
XERO_Racer said:
wouldnt overclocking also gives you a higher chance of frying your CPU chip? cuz ive seen it happened in PCs i just idk about PPCs
Click to expand...
Click to collapse
Not unless you are having excessive heat problems. Since there are basically no people reporting these problems, I wouldn't worry.
miked79928 said:
I agree that there are virtually no ill effects to this. When unlocked, I have my phone running at 787 mhz. While it is locked or sleeping it throttles down to 604 and eventually 528 mhz. I have noticed no extra heat nor extra drain on the battery. Just blazing fast speed! Sense 2.5 is virually not laggy at all! CHT 1.8.5 is so smooth and quick even with the aminations enabled!
If anyone is interested in the automated clocking process, I can help by giving my set-up that is working flawlessly on the ROM in my signature!
Click to expand...
Click to collapse
Once again as stated earlier, 100% agreed.

Do I have to keep plugged in?

miked79928 said:
Here is the best way I have found to do it. I take absolutely no credit for this:
http://forum.xda-developers.com/showpost.php?p=7354283&postcount=627
Click to expand...
Click to collapse
I thank you for this, but I'm not sure how to implement it. I have installed Mortscript, I've copied the code into a file I called overclock.mscr and modified the code reflect the reg values on my Tilt 2. and I've placed the script on the root on my SD card. I've installed MSM7kCpuSpeed on to my SD card. How do I make the script run automatically?
Thank you!

I take no responsibility for w/e happens to your phone with this advice.
Try putting a pointer in your start up to the over clocking script. Its highly unstable and could brick your phone or require a hard reset... thats why I do it with a toggle switch, i dont mind manually applying the OC with a hard key knowing its safe, esp because the situations where I actually NEED 787mhz are less common than needing to just wake the phone to answer a call or make a txt message.

I just want to say that I have been running android on my tilt 2 overclocked at around 750 for a few months now with various builds and i know a lot of other users who have as well with no problems, i am going to try this out, thats what i pay for insurance for hehe
..and after reading more i may have spoken too soon because i missed the posts where i saw that you can brick your phone with OC in WinMo easily enough if you are not careful, so tread with caution

dirtypiratehooker said:
I just want to say that I have been running android on my tilt 2 overclocked at around 750 for a few months now with various builds and i know a lot of other users who have as well with no problems, i am going to try this out, thats what i pay for insurance for hehe
..and after reading more i may have spoken too soon because i missed the posts where i saw that you can brick your phone with OC in WinMo easily enough if you are not careful, so tread with caution
Click to expand...
Click to collapse
Just a note, I'm not sure the insurance would cover burning a custom ROM into the phone, or overclocking the CPU. And if the chip is fried you can't burn the stock ROM back in. But then, they probably couldn't figure out it was updated without in stalling a new CPU. Umm, it would probably work.

Would a .cab for this ever be conceivable?

At this point, we have finally got a script that will work for most Rhodiums, Topaz (Diamond 2), and a few guys with other phones seem to be having good luck.
The device has to have Mortscript installed, and nettrip's MSM7 v2.
It is a single script solution that requires no pre checks in the registry, no key/button assignment, and you can change the speed settings from the script instead of the registry.
It throttles the OC up and down for calls, lock, and sleep, to avoid freezing on wake up and in a call. Some problems that still need to worked out by nettrip in the script. I don't envy him the work as the script(s) were bad enough. Four of us have hit that original script (by jpc) from about page 13.
You copy the script to the SD or the device root, create a shortcut to the file, copy the shortcut to Windows\Startup directory, reset/reboot the device and you are off.
You can use the MSM7 app to read the OC, but you should make sure to exit the app before sleep, lock, or power off, as it will error on reboot if left open.
To be honest, you never have to open the MSM7 app, as the script controls it in the background.
I believe the script is set for a low over clock. 691. My experience has been a 710 average, but a lot get a stable OC at 750+. I am running 748 and I think I will stop there. A 200MHz overclock will just have to do.The phone does not get hot, though with intense use, it does get warmer. Never warmer than when the battery is charging, tho.
I am running the nrg Sense Reference ROM, 23xxx based on Sense 2.5. I added the CHT 1.8x and the editor to save a few MHz, no biggy.
The overclock allows the Sense to work MUCH smoother, actually noticeable as even the weather animation is smooth.
And all the vid players seem to work better.
I have noticed NO extra battery drain than usual.
The script is only a stop gap measure until nettrip finishes his app, but it does work well with little effort. WAAAAY better now than even last week.
However, use the script at your own risk, as you can get too Medieval on the OC. Some guys are running 800+, more nerve than I have.
Anyway, if interested in the script or want to read some more about the app, you can start here
http://forum.xda-developers.com/showthread.php?t=725290&page=89
post #882 has the script.
Plenty of instructions on how to use (and make changes to the settings) in the last 30-40 pages.

Sorry if this is already explained, but can someone tell me in simple details how to keep my overclock at 729mhz even after screen lock or sleep mode? I've tried to follow previous posts but it keeps reverting back to 528mhz after locking and sleep.

Ok so this seems legitamite,everyones checking in with no problems.
other than the increased risk factor that always accompanys speed,
it seems our ppc's cpu was underclocked beforehand ?
i will try this and see if i get a gpu boost as well.
but ivr already experienced my phone overheating to the point
of shutting itself down,and the god-damned orange light is permenantly on...

need help verifying cpu speed

Hi Everyone
I have OC Widget installed on my phone (htc hero sprint) and I was wondering is there a way to confirm that the speed being reported by OC widget is in fact the actual cpu speed. My reasons for doubting this are that
1) even with a setting 710mhz the phone seems kind of sluggish at times
2) I get notifications of cpu settings changes when turning my screen off to on but I do not see a change in the number displayed in the widget (it is always set at the on screen speed)

adb shell cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq
*edit*
I would be interested in knowing where you read CPU temperature information, though.

Doward said:
adb shell cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq
*edit*
I would be interested in knowing where you read CPU temperature information, though.
Click to expand...
Click to collapse
CPU temp huh...i have no idea lol
Since you brought it up I do have a question for you that is somewhat related, can access heat (from either the battery or cpu) cause a reboot (either a complete reboot going through all the load screens or just a reboot to boot back into the home screen).
I was experiencing quite frequent reboots (the later of the two I described above) and had initially thought maybe they were app related but could never determine if that was the cause.
I was over clocking and underclocking so was wondering if maybe that could have lead to some instability issues.

dsMA said:
CPU temp huh...i have no idea lol
Since you brought it up I do have a question for you that is somewhat related, can excess heat (from either the battery or cpu) cause a reboot (either a complete reboot going through all the load screens or just a reboot to boot back into the home screen).
I was experiencing quite frequent reboots (the later of the two I described above) and had initially thought maybe they were app related but could never determine if that was the cause.
I was over clocking and underclocking so was wondering if maybe that could have lead to some instability issues.
Click to expand...
Click to collapse
Clock speed and voltage go hand in hand - if you are adjusting one without the other, yes, you will affect stability. Heat also plays a part - now, specifically can a hot battery cause a CPU malfunction? Yes, but unlikely. More likely, the heat will affect the voltage from the battery and case CPU instability via that path.

KNOWN issues with KT-SGS4 Sprint KitKat 4.4 TouchWiz kernel

SO... in regards to the KT-SGS4 KitKat 4.4 TouchWiz kernel, the vast majority of users seem to have no problems with it, but there ARE KNOWN issues that appear to be caused by this kernel for some users, with varying degrees of rarity. WHY certain users have these issues when others do not is not currently known, but it would be great if we could figure this out. I am HOPING this thread (and it will only be a THREAD with input from others) will help us find cures for the issues we face with this kernel.
KNOWN ISSUES:
#1. Sound skipping - This seems to be the most common issue experienced with the kernel and I actually would not call it rare. Some possible fixes for this are to: A) increase the Media/Music Min Mhz and Bluetooth Profile Mhz to around 702 Mhz or so, B) try using a different I/O Scheduler and try adjusting the Internal and External Read Ahead Buffers, C) change disable_hotplug_media from a 0 to 1.
#2. Phone freezes/locks up while charging
#3. Screen flickers when a window is open over the desktop
#4. Mobile connection/data (and possibly also GPS) loss a while after booting phone - this may be the rarest issue, but it is OBVIOUSLY the most serious. I have suffered from it personally. I contacted Ktoonsez regarding this and he denies it being a known issue since many thousands of users use his kernels and don't have this issue... I have confirmed multiple other users who DO have this issue and the only thing I see we have in common is the KT-SGS4 kernel. It appears that this issue MAY be fixable by using the "right" choice of governor and settings. The problem is that what the "right" choice of governor and settings are MAY be determined by your ROM. On stock rooted NAE with MF9 bootloader, using largely the kernel default settings, including the interactive governor, APPEARS to have cured this issue for me (as well as the freeze while charging), while using the ktoonserativeq governor or the pegasuq governor appear to have caused this issue (I am still in the process of investigating this...).
This is not meant to be in any way negative towards Ktoonsez and I certainly appreciate all the work he does to provide us kernels, but there ARE issues that some of experience and I hope this thread can help us work TOGETHER to solve them! If there are any other issue that you believe should be listed, please post them. If you have any possible cures, please post them. If you need any help, please ask. If you have any input, please post! :highfive:

I can't get his kernel to run on my phone for the life of me so I stuck with Negalite NAE Stock Kernel, but I use his kernel religiously on my wife's s3. Even using basically the same setup I still get skipping on music, phone goes unresponsive after charging a few hours. And a few others.

Is music skipping only for users who are also trying to do ViPER4Android (probably with Convolver turned on)? I think the governor and adjustments are also critical in solving this problem. I've been using ondemand and somebody said interactive is also helpful. The other thing here is that it could be an issue of I/o scheduler. I've been using sio. I'm getting minimal skipping at this point. You're right that ktoonservativeq caused MAJOR skipping, even with tons of governor tweaks.
After switching to ondemand, my phone hasn't locked up while charging, but it has randomly locked up at other times. Weird.
On issue #4, I've lost data less with ondemand but it hasn't completely solved the problem. Sometimes I can toggle Airplane Mode on and off and get going again, but mostly that toggle won't even work and I have to reboot.

JesseAaronSafir said:
Is music skipping only for users who are also trying to do ViPER4Android (probably with Convolver turned on)?
Click to expand...
Click to collapse
That is an interesting question, now that you mention it. I had been using ViPER4Android, probably while I was having the skipping issue, but I stopped using it in the long process of attempting to cure my mobile connection issue (I read something that made me think it could be related) and I'm actually not sure if I ever had the skipping issue without it.
Of all the issues though, this one is very common in the KT-SGS4 kernel thread, so I DOUBT (but don't know) that everyone experiencing it is using
ViPER4Android.
(Also, I THINK it skipped for me without Convolver turned on).

I haven't used v4a since I was on Negalites

elwood said:
I haven't used v4a since I was on Negalites
Click to expand...
Click to collapse
Yeah, I think the skipping has to do with the kernel generally allowing the governor in default settings to throttle down too low when music is playing...

rsngfrce said:
Yeah, I think the skipping has to do with the kernel generally allowing the governor in default settings to throttle down too low when music is playing...
Click to expand...
Click to collapse
Don't forget the issue where the phone will not power up while charging if it's charging while off.
I don't. Mine even skips while the screen is on and I don't use V4A and have tried other than stock music players as well. I have no such problems with Nega but I've tried different modem firmwares too. These don't seem to affect this problem.
If anybody wants, though, they could chime in on my Wifi tethering problem. Nobody seems to wanna tackle it.
http://forum.xda-developers.com/galaxy-s4-sprint/help/wifi-tether-disappeared-t2877341

arikdahn said:
Don't forget the issue where the phone will not power up while charging if it's charging while off.
I don't. Mine even skips while the screen is on and I don't use V4A and have tried other than stock music players as well. I have no such problems with Nega but I've tried different modem firmwares too. These don't seem to affect this problem.
If anybody wants, though, they could chime in on my Wifi tethering problem. Nobody seems to wanna tackle it.
http://forum.xda-developers.com/galaxy-s4-sprint/help/wifi-tether-disappeared-t2877341
Click to expand...
Click to collapse
I didn't forget it, it is issue #2!
#2. Phone freezes/locks up while charging
In my experience, the phone does NOT have to be off while it is charging to have this issue, it would happen to me when I was charging my phone with it on. Fortunately, on NAE stock rooted with MF9 bootloader, using the mostly default kernel settings with the interactive governor seems to have fixed this issue for me, as well as the mobile connection/GPS issue (knock on wood still...). I mainly just adjusted the I/0 Sceduler to noop and the Media/Music and Bluetooth Min Mhz to 702 Mhz from the stock settings. The only issue I am personally left with now is the screen flicker.
I don't think the screen being on or off relates THAT much to the music skipping issue, it skipped for me too with the screen on. Definitely I would say, using the ktoonservativeq governor with Ktoonsez' settings WILL result in music skipping... BUT, IMO, this MUST BE TAKEN INTO ACCOUNT, Ktoonsez DOES NOT HAVE OUR PHONE... how can his settings POSSIBLY be OPTIMAL for our phone? Think about that!
As far as your WiFi tethering issue, I am well aware of it personally, having read your other posts, but I don't know much about this (don't use it myself) and in another thread I was going to direct you to a link you are already aware of that didn't help. If anyone can help arikdahn with this, please jump in! :good:

I definitely had more problems with music skipping when the screen would turn off. Using ondemand or interactive with sio and 2048 read ahead caches seems to have almost completely resolved the issue for me. I'm still not sure which I/o scheduler is best.

I would think that the governor throttles down MORE when the screen is off, which is why I consider the Media/Music and Bluetooth Min Mhz settings important to be set above the default, which I believe is Min and should override that throtte down when music playing (ay the expense of battery time, but the battery is meant to be USED when needed) and I can't see how that CAN'T cause skipping in most setups. But it does occur for some even with the screen on.

rsngfrce said:
I would think that the governor throttles down MORE when the screen is off, which is why I consider the Media/Music and Bluetooth Min Mhz settings important to be set above the default, which I believe is Min and should override that throtte down when music playing (ay the expense of battery time, but the battery is meant to be USED when needed) and I can't see how that CAN'T cause skipping in most setups. But it does occur for some even with the screen on.
Click to expand...
Click to collapse
Well, all I have to go off of is my own expertise with MY equipment only. My thoughts based on this is that it's not a limited-resources type issue, like if the CPU's throttling down or not buffering ahead enough or whatever. I had skipping problems all the time and I tried it with uTorrent running in the background, items downloading/moving, and these processes didn't slow down or cause any problems themselves. That's why I think what I think. Anyway, what this means to me is that I do not believe that in my situation, anything I can do with the kernel's configurable options will change anything. Then again, i think my phone's possessed anyway. It won't run the dialer on AOSP/CM roms and might just be one of the most finnicky high tech devices I've ever owned.

arikdahn said:
Well, all I have to go off of is my own expertise with MY equipment only. My thoughts based on this is that it's not a limited-resources type issue, like if the CPU's throttling down or not buffering ahead enough or whatever. I had skipping problems all the time and I tried it with uTorrent running in the background, items downloading/moving, and these processes didn't slow down or cause any problems themselves. That's why I think what I think. Anyway, what this means to me is that I do not believe that in my situation, anything I can do with the kernel's configurable options will change anything. Then again, i think my phone's possessed anyway. It won't run the dialer on AOSP/CM roms and might just be one of the most finnicky high tech devices I've ever owned.
Click to expand...
Click to collapse
Hey, I'm not in any way disputing what you are saying, the point of this thread is to figure these things out! I'm certainly not presenting myself as the expert on these issues! I'm just a lucky one who seems to have mostly resolved the issues on MY phone. (BUT... I AM NO ANDROID EXPERT EITHER and will never claim to be, but I am not saying it is a limited-resources issues, what I am saying is that I believe the default settings will allow the governor to throttle down to below the level necessary to play music without skipping... I could be wrong, but that it what it looks like to me.)
Because SO MANY people APPARENTLY don't have MOST of the issues mentioned, I personally think this is highly related to which ROM you are using... though I don't know what ROM those other people are using...

[HELP] Overheating issues

Hi everyone,
Thanks for reading this . As specified above, my phone has a rather serious problem of overheating. To try and reslove the issue I tried modifying the CPU frequency, to set it low enough. And a very bizarre thing just happend.
Opening Kernel Adiutor, I saw that 4 out of my 8 cores (the 2.5 ones) were running normally. No overclock, stock settings, stock governor and so on. The issue seems to be in the other 4 (the 2.3 ones). Both the minimum and highest frequency allowed is set up to the same parameter (1556 mHz), forcing it to stay at maximum clock all the time. I tried modyfing via Kernel Adiutor the settings, lowering the minimum frequency allowed to stock one (which should be around 300 or something), but it had no effects: it immediatly comes back to 1556 and just won't come down.
All of this started happening after i removed Franco Kernel from my system, flashing another ROM (Chroma) with a different kernel altogether. I'm currently on Cataclysm ROM and after doing a clean install, formatting internal storage as well as every other partition, i couldn't resolve the issue. Moreover, Kernel Adiutor sometimes won't even show my CPU settings, stuck on an infinite loading. If anyone could help me, it would be much appreciated. It's really important. I'm by no means Android expert but i do have a rather basic understanding of ADB and so on.
Thanks a lot for your time.
-LVBNR5

I used to own a n7 and that allowed me to set min and max freq. with apps fine but i am also seeing this on my 6p, i don't notice any "overheating" although it may be due to me being used to it always running hot since i run a lot of heavier programs and also you know... SD810 but i guess it does the frequency thing as a way that frequency is actually controlled on this platform or something, because it sticks fine to the limits you set while flashing a kernel but no app can get it to stick. Then again this is just me sharing my experience with it as it is my first phone with this platform, so maybe someone who knows more about this could offer some help.

ml11ML said:
I used to own a n7 and that allowed me to set min and max freq. with apps fine but i am also seeing this on my 6p, i don't notice any "overheating" although it may be due to me being used to it always running hot since i run a lot of heavier programs and also you know... SD810 but i guess it does the frequency thing as a way that frequency is actually controlled on this platform or something, because it sticks fine to the limits you set while flashing a kernel but no app can get it to stick. Then again this is just me sharing my experience with it as it is my first phone with this platform, so maybe someone who knows more about this could offer some help.
Click to expand...
Click to collapse
Thanks anyway, i really appreciate it!

Battery, thermal performance and general cpu optimization

Just confirming that this post from the Z5 forum: here does indeed work on the z3 single sim(probably dual sim as well, can't see why not).
These tweaks are based on the Heimdall governor used in this post
Tweaks reduces heat, optimizes the performance and increase the battery life.
Check them out!
Edit
I think i have to clear something up with these scripts
my intention of using these scripts is to be able to use my phone longer. To have better battery life in general. I also wanted to be able to use my phone without always compromising the performance of the device. why only use 50% of a handsets performance right? so i wanted to increase the amount of time i could use the deice before it got to hot and starts the thermal throttling. the throtteling for this phone is verry agressive and i wanted to change this. Im using a cover for my phone so i dont care if i gets hot, if that means that i have better performance.
so without any thermal configurations this phone gets laggy or starts thermal throttling around 60 degrees. I have increased this limit to around 70 degress where you will start to feel the reduce in performance. Thats 10 degrees where i get extra performance. there are often use scenarios where you just use your phone for 10 minutes at a time right? well, i can do that now without getting the thermal throttling being in the way.
This thermal files are intended to make the device perform better and allow cpu to get warmer. This is optional!
i configures the scripts a bit, since i only use the Heimdal governor, i combined the three scripts, and made some minor improvements.
-Disabled two of the little and big cores.
-Set max speed of big cores to 1248, eg underclock
-Set gpu governor to simple_ondemand
In the thermal config file i have, ive also made some changes. since the thottling is to aggressive for me, the little cores throttling does not go under 960mhz, ever no matter how hot.
This means that scrolling menues and browsing internet does not lagg. Sven if the cpu is 75 degrees.
This does not happen to the big cores, which means that games using big cores, will lagg when exeding 75 degrees. They will be throttled down to 384mhz to not brake the device.
Warning! im not responsible for any melted devices! The thermal config is for people who does not care how hot their phones get. they just want performance.!
Installation
-For battery, thermal improvement, and cpu optimization:
1. Rename the file to: BearPower.sh ,
2. Make a mew folder in /etc/"folderName" and place the script file there.
3. Set it to apply on boot of the device with SManager. Mark the "Boot" "SU" buttons, then "save" and then "run".
-Install the thermal configs:
1. Rename the "init.qcom.post_boot.txt" file to xxx.sh
2. Rename the "thermal-engine.bearpowerv1.0.txt" file to xxx.conf
3. Make /etc folder writable
4. Place both of them in the /etc folder
5. check permission, set it to 644 or -rw -r -r
6. restart your device

Already tried but didn't find any noticeable change.

waseemakhtar said:
Already tried but didn't find any noticeable change.
Click to expand...
Click to collapse
well it increaded my SoT with 1 hour, ill take it

Did you fix the overheating issue ??

nex_t said:
Did you fix the overheating issue ??
Click to expand...
Click to collapse
I tweaked the three scripts in the z5 forum even further, so my my phone does notbget hot when doing light to medium use, but it still gets got when playing games ?
Phone also gets hotter when plugged in charger... My phone is a lot better than what it was as well

I never play games on the mobile phone
As i said, i use it for web browsing and Youtube, most of the time
bjowol, please help me one more time.
Which files do i have to flash ? Do i need another kernel now, for doing this ?
Thank you so much