About GPU Throttling - Nexus 4 Q&A, Help & Troubleshooting

Hello everyone,
My question is about Throttling. We know in stock Nexus 4 kernel, throttling starts when battery temperature hits 37C. CPU throttling is fine, but problem comes when it starts throttling GPU. Is there a way we can stop it from throttling GPU? Can we edit the stock thermald.conf file? Is it safe to edit it and remove GPU option from it and make it throttle when the battery temperature reaches 40C?

TheRebel said:
Hello everyone,
My question is about Throttling. We know in stock Nexus 4 kernel, throttling starts when battery temperature hits 37C. CPU throttling is fine, but problem comes when it starts throttling GPU. Is there a way we can stop it from throttling GPU? Can we edit the stock thermald.conf file? Is it safe to edit it and remove GPU option from it and make it throttle when the battery temperature reaches 40C?
Click to expand...
Click to collapse
should work and should be safe. why dont you try it?

vollmilch said:
should work and should be safe. why dont you try it?
Click to expand...
Click to collapse
Thank bro
Lol, I thought I might hard brick my phone. Do you know anyone else tried it?
I know we can get rid of this gpu throttling (which happens so early) by using some custom kernel, but i've tried many custom kernels, but they don't seem to have same smoothness as stock kernel.

TheRebel said:
Thank bro
Lol, I thought I might hard brick my phone. Do you know anyone else tried it?
I know we can get rid of this gpu throttling (which happens so early) by using some custom kernel, but i've tried many custom kernels, but they don't seem to have same smoothness as stock kernel.
Click to expand...
Click to collapse
trinity kernel has battery temp throttle disable, and its extremely smooth.

simms22 said:
trinity kernel has battery temp throttle disable, and its extremely smooth.
Click to expand...
Click to collapse
thanks!!!
does trinity kernel throttles on CPU temperature? thermal throttling?
And do you have any idea about my question in first post? Is it safe to edit the stock kernel's thermald.conf file?

TheRebel said:
thanks!!!
does trinity kernel throttles on CPU temperature? thermal throttling?
And do you have any idea about my question in first post? Is it safe the stock kernel's thermald.conf file?
Click to expand...
Click to collapse
it has its cpu throttle temp raised. but there is a simple script you can run in a terminal emulator app or go to tbe location with a root file explorer and exit manually. in a terminal emulator app..
su(press enter)
echo N > /sys/module/msm_thermal/parameters/enabled(press enter)
i always run with thermal throttle disabled. tbe cpu safty temp is still intact, if you hit it, youll automatically shut down to cool off. the only way that you will hit it is if you try to hit it.
about editing the thermald.conf file.. is it safe modding your phone in the first place?

i believe that faux's kernel uses a modded thermald file (cpu throttle temp raised, gpu throttle disabled). i used to keep a copy of the file on my dropbox and i would post it here for you but I deleted it some time ago. why dont you ask someone in his thread to share it with you so you can just replace yours.
but keep a backup of your original just in case

simms22 said:
it has its cpu throttle temp raised. but there is a simple script you can run in a terminal emulator app or go to tbe location with a root file explorer and exit manually. in a terminal emulator app..
su(press enter)
echo N > /sys/module/msm_thermal/parameters/enabled(press enter)
i always run with thermal throttle disabled. tbe cpu safty temp is still intact, if you hit it, youll automatically shut down to cool off. the only way that you will hit it is if you try to hit it.
about editing the thermald.conf file.. is it safe modding your phone in the first place?
Click to expand...
Click to collapse
Thanks for this! you're awesome
I know modding phone is not safe, that's why I was asking.
Anyway if I want to give try to trinity kernel, which one should I install? I'm currently on CM stable.
there are two links in trinity thread
one at the top (i'm not allowed to post links here of the OP) the link of homepage
Second says, stock/aosp + CM

vollmilch said:
i believe that faux's kernel uses a modded thermald file (cpu throttle temp raised, gpu throttle disabled). i used to keep a copy of the file on my dropbox and i would post it here for you but I deleted it some time ago. why dont you ask someone in his thread to share it with you so you can just replace yours.
but keep a backup of your original just in case
Click to expand...
Click to collapse
Thanks for the reply. I've faux123 thermald.conf file. But I dont' know whether I should replace stock thermald.conf with faux thermald.conf. Because faux has used Sampling 1500 (while in stock the sampling value is 5000). I don't know about sampling though , just the values were different so i didn't replace the file, thought it might hard brick the phone

TheRebel said:
Thanks for this! you're awesome
I know modding phone is not safe, that's why I was asking.
Anyway if I want to give try to trinity kernel, which one should I install? I'm currently on CM stable.
there are two links in trinity thread
one at the top (i'm not allowed to post links here of the OP) the link of homepage
Second says, stock/aosp + CM
Click to expand...
Click to collapse
go to http://www.derkernel.com/mako.php , click on "experimental" and download the first one (TF133).
if your rom doesnt use a modded ramdisk, just reboot into recovery, flash it, wipe cache and dalvik, reboot

TheRebel said:
Thanks for this! you're awesome
I know modding phone is not safe, that's why I was asking.
Anyway if I want to give try to trinity kernel, which one should I install? I'm currently on CM stable.
there are two links in trinity thread
one at the top (i'm not allowed to post links here of the OP) the link of homepage
Second says, stock/aosp + CM
Click to expand...
Click to collapse
theres only one link for downloads, tf133 is the latest http://derkernel.com/jb-mako.php

simms22 said:
theres only one link for downloads, tf133 is the latest http://derkernel.com/jb-mako.php
Click to expand...
Click to collapse
is there any difference in throttling based on battery temp and CPU temp? which one exactly are modifying using the echo command?
CPU temp threshold can be raised easily in faux app, so what about battery temp threshold? can we change it?

Related

SetCPU on Incredible?

Ok, i have a fully rooted incredible with SetCPU installed. I have profiles enabled and setup but when i change the main profile the current clockspeed is always higher. Also, the min/max at the top right never change from 998mhz max and 250 min. Do i need a special kernel or something to use setcpu? i have it under the nexus one/snapdragon profile btw. and its 1.5.4
mikerulez121 said:
Ok, i have a fully rooted incredible with SetCPU installed. I have profiles enabled and setup but when i change the main profile the current clockspeed is always higher. Also, the min/max at the top right never change from 998mhz max and 250 min. Do i need a special kernel or something to use setcpu? i have it under the nexus one/snapdragon profile btw. and its 1.5.4
Click to expand...
Click to collapse
Looks like only simple switches like "performance, userspace, etc" and for some reason advanced settings will make a difference. I believe persistent/kernel-level switches not provided for in the UI cannot work at present because we can't write to the build.prop, user.conf, or init.rc.
P.S., the DI's processor is upgraded from N1's. Same product line, newer model.
So im out of luck until a new kernel is out? Ok. But if i get a new kernel, will i be able to keep the default os or does that require a new rom?
Give 1.6 a try. Maybe it works for you.
larsdennert said:
Give 1.6 a try. Maybe it works for you.
Click to expand...
Click to collapse
Nope, even in 1.6 direct throttling still does/can not work, but seems like selecting userdata, performance, or ondemand has an effect on where the processor speed averages
You will need a overclocked kernal for SetCPU to work.
You DO NOT need an overclock kernel for it to work. The problem is the /system partition is not writable from within Android which is how SetCPU works. Once we get the nand unlock, it'll work.
from my understanding is you will need an unlocked kernel and RW NAND
Berzerker7 said:
You DO NOT need an overclock kernel for it to work. The problem is the /system partition is not writable from within Android which is how SetCPU works. Once we get the nand unlock, it'll work.
Click to expand...
Click to collapse
Now THAT makes sense. I'm not sure I want a Nand unlock; but I'd like an easier way to push stuff in recovery so I can make intentional tweaks and protect the OS the rest of the time.

[Q] SetCPU on Tattoo

Hi all
I recently installed SetCPU on my Tattoo with SPQRom 0.6 (Android 2.2) and actually it working in underclock (19MHz).
It seems that perflock can be disabled.
But on overclock I can't surpass the default freq 528MHz, even setting that manually (setcpu.txt)
Wich overclock frequency can I use? My kernel version is 2.6.29-fy-bfs
Thanks.
I had the same problem too... You have to flash a special OC kernel first. Check the Spqrom thread pages 68 to 70 (http://forum.xda-developers.com/showthread.php?t=767049&page=68), there you will find a download link and a step by step description.
Basically you flash the kernel and then edit one line in a system file to get Wifi back. It´s really not that difficult, even I managed it. After that you can use SetCPU, I went to 710 MHz, that seems to be the stable maximum.
eljanor said:
I had the same problem too... You have to flash a special OC kernel first. Check the Spqrom thread pages 68 to 70 (http://forum.xda-developers.com/showthread.php?t=767049&page=68), there you will find a download link and a step by step description.
Basically you flash the kernel and then edit one line in a system file to get Wifi back. It´s really not that difficult, even I managed it. After that you can use SetCPU, I went to 710 MHz, that seems to be the stable maximum.
Click to expand...
Click to collapse
I know, actually I'm using KiljackenROM 1.4 (only Android 2.1) and if I set to 768MHz the phone crashes and reboot. Without a voltage increment, I think 710MHz is the maximum stable (and it's ok as it is).
Now I'll check your link, thanks.
EDIT: GREAT! IT WORK PERFECTLY! Now it's only find the way to run at boot a script for activating wifi, but I think it's easy, with or without a program.
Thanks a lot
You´re welcome! Actually, you don´t need to write a script - just open the "/etc/init.d/02squashsf" file as a text file and put a # in front of the line "busybox losetup /dev/block/loop0 /system/squashfs/modules.sqf" to comment it out.
Try the "2nd Way" from the following quote I took from the official spqrom thread (Page 70):
x1l0n said:
How did you try to do it?
Anyway, there are a lot of ways to do it. Let's try first with adb (I'm writting this for a windows environment, because I'm too lazy to boot into linux, so sorry):
You plug in your tattoo through UsB on your PC. You start your command prompt and go to the folder where adb.exe is contained. The you write adb pull /etc/init.d/02squashsf c:\02squashsf <- this will save 02squashsf from your tattoo to your pc in the c:\ directory/partition. After that open the 02squashsf file with ... notepad/notepad++ and comment the line as described in my previous post. After you save the now modified 02squashsf file go to command prompt again and execute : adb push c:\02squashsf /etc/init.d/02squashsf <- this will copy 02squashsf from your c:\ to your tattoo. Pretty easy!
2nd Way:
Start RootExplorer on your tattoo and go to the folder /etc/init.d. Then click the small button in the upper right corner which says "Mount as R/W" (this will mount the system partition as Read/Write access). Find the 02squashsf file and long click it (until the menu pops up) and then choose edit as text file (or something similar). After it has been opened comment out the line as described in my previous post and save the file after the modification. That is all.
By the way, there is a 3rd way - unpacking the squash and editing its contents to be correct. But I don't really have the time...
And remember that a backup takes only a few minutes to make, but a mistake can cost you hours to fix if you have no backup
Click to expand...
Click to collapse
Takes 1 minute of your time, and you never ever have to think about it again, no matter how often you reboot. Not sure what the effect of outcommenting this line is though, but I didn´t run into any problems so far...
eljanor said:
You´re welcome! Actually, you don´t need to write a script - just open the "/etc/init.d/02squashsf" file as a text file and put a # in front of the line "busybox losetup /dev/block/loop0 /system/squashfs/modules.sqf" to comment it out.
Try the "2nd Way" from the following quote I took from the official spqrom thread (Page 70):
Takes 1 minute of your time, and you never ever have to think about it again, no matter how often you reboot. Not sure what the effect of outcommenting this line is though, but I didn´t run into any problems so far...
Click to expand...
Click to collapse
Eheheheheeh I'm using a safe "fourth way", that I thought.
A normal way (not that 3) is typing these commands on Terminal Emulator directly from the phone.
Well, so why don't insert them into "Preferences -> Initial command" and give to Terminal Emulator the superuser authorization (with flag "Remember")?
Now, every boot, I simply open Terminal Emulator with a link on the desktop, waiting few seconds and it work!
Sometimes the default power widget doesn't work, so I must enter in Settings -> WiFi and turn it on. But it work without typing nothing more or modify a system file
Baboo85 said:
I know, actually I'm using KiljackenROM 1.4 (only Android 2.1) and if I set to 768MHz the phone crashes and reboot. Without a voltage increment, I think 710MHz is the maximum stable (and it's ok as it is).
Click to expand...
Click to collapse
Talking about voltages, are they controllable in some accessible way? I'd give it a go any time if I could find any useful information on the subject. Any help?
Baboo85 said:
Hi all
I recently installed SetCPU on my Tattoo with SPQRom 0.6 (Android 2.2) and actually it working in underclock (19MHz).
It seems that perflock can be disabled.
But on overclock I can't surpass the default freq 528MHz, even setting that manually (setcpu.txt)
Wich overclock frequency can I use? My kernel version is 2.6.29-fy-bfs
Thanks.
Click to expand...
Click to collapse
Just a question of confirming something.
With the new SPQRom 0.7 room we still have to flash a new kernel like eljanor user advised?
[Q] SetCPU on Tattoo
I had the same problem too... You have to flash a special OC kernel first. Check the Spqrom thread pages 68 to 70 (http://forum.xda-developers.com/show...767049&page=68), there you will find a download link and a step by step description.
Basically you flash the kernel and then edit one line in a system file to get Wifi back. It´s really not that difficult, even I managed it. After that you can use SetCPU, I went to 710 MHz, that seems to be the stable maximum.
Click to expand...
Click to collapse
Or it's this new room already is ready to be Over-clocked?
Thanks in advance
So, how far have you guys have went? I've read that for some of you, 710 MHz is the stable max, but for me, my tattoo seems to crash occasionally on that clock speed. My stable max is one step lower, 691 MHz.
bladez said:
My stable max is one step lower, 691 MHz.
Click to expand...
Click to collapse
I agree. Most stable and powerful is 691MHz. I have tested tatto by System Benchmark from market and its shows max results on 619MHz, next 710MHz are got worst resulsts in Cpu and Graphics tests. 691MHz optimal.
I also experimented with System Benchmark, and I got the best results on 730, though it did reboot occasionally.
my is 680

[Q] x8 does not overclock

Hi everybody...
I know I'm not a dev, but I like to explore my android phone. So you are developing, and right after i'll be trying to do it... on my own
I believe I followed all the steps refered in x8 overclock module thread in devs section, but since I can't ask this there, i'll ask it here.
1st - Download and unzip x8oc.zip (the right version), then copy x8oc.ko to system/lib/modules (I'm sure the file is there, system is mounted rw).
2nd - Edit hw_config.sh on pc with notepad++ (my edited file is attached) and "glue it" back to system/etc after editing.
3rd - Reboot... and then what?! It reboots, but when I go to set cpu, I have same frequencies as before (122-600mhz). So, my x8 is not overclocked right?!
Beside this steps do I need to do something else?! In set cpu, do I select any device configuration or just auto detect frequencies?!
Do I need to set custom frequencies in any other files?!
I've just tried lot's of changes and nothing worked.
Please help me on this...
I'm using floyo 0.15 on my x8, rooted and with xrecovery on it...
Thank you all
the attachment is correct..and don't change the set cpu. i use the same roms like yours
Do you think that having baseband version 006 instead of the 015 could be the cause for this problem? I never updated it...
Because, I've done it again without touching set cpu and still no overclock... If you say it's correct, then I really don't know what else could it be...
Thank anyway for the reply
I think it is very influential on baseband cuz for the rom said that use xx15,...if yours non xx15 so try to change it ...what you've applied on the hw_config is same on mine so it's quitely correct.
Hi mate
So, I'll tell you what i've done.
Went to SE's site and repaired to the original 2.1 so restarted the phone, updated to baseband 015, then root, then xrecovery... and then, installed miniCM. As you know, miniCM has an update.zip to easily overclock it to 710MHz.
I tried it and it worked fine. BUT! I prefer Floyo 0.15 (the best till the moment for me) and so I tried to do something, when I restored back to Floyo.
Adding the code to the original hw_config.sh in floyo's file didn't work again. So I thougt... Let's trie to put MiniCM's hw_config (the file that comes in the update.zip) to floyo's system. And... It's working FINE!!! I'm currently running at 749(x27)Mhz and it doesn't go off... it's stable. Also handles 767(x28)Mhz but it's not so stable. Now I'm really satisfied with my overclocked x8.
But there is one reason that made me think of where was the mistake.
When I opened floyo's original hw_config and added the code, in notepad++ it was apparently correct and the visual configuration of the file was equal to miniCM's hw_config file (already with the code). But, when I opened the both in wordpad, the file I edited had the same format as in notepad++ and the file from MiniCM had all together and a different layout. So I thought that it was possible that android wasn't reading the file well, since the configuration of the code was different. And it worked so smoothly
So my question is, does notepad++ write in the language needed for this to work?! or is there anything needed to change in order to make it legible to android system?
Thanks again
Sorry for all this noob questions, but since you use the same rom as mine, it's a good chance to ask what I don't know. lol
Our rom comes out with app2sd pre installed right?
So it was suposed that I could move some programs to sd.
But, when I go to settings/apps manager There's the option to move apps to sd, but they all say "fail moving the app".
What do I have to do to make it work well?! Heard that the sd had to be partitioned. What program did you use to do that?!
That's the only thing left to make x8 perfect and full of memory lol
Thanks
I managed to OC it manually to 710 MHz in miniCM6, BUT no performance increase was detected. Quadrant score was consistently lower (~750) compared to no overclock (~850),
Any ideas?
I OCed it to 719MHZ with miniCM and i really felt an improvement. Switching menus and sliding on the home-screen (GO launcher) is really smoother.
Quadrant-Standard-Score:
@600MHz (ON DEMAND): ~520
@719MHz (PERFORMANCE): ~920
MaScXDA said:
I OCed it to 719MHZ with miniCM and i really felt an improvement. Switching menus and sliding on the home-screen (GO launcher) is really smoother.
Quadrant-Standard-Score:
@600MHz (ON DEMAND): ~520
@719MHz (PERFORMANCE): ~920
Click to expand...
Click to collapse
and about battery life, noticed any difference after OverClock your Phone?
biscoitu said:
and about battery life, noticed any difference after OverClock your Phone?
Click to expand...
Click to collapse
it drains a bit faster with the PERFORMANCE-govenor, but my phone is loaded every night anyway.
It is even less important to me, because when it reacts faster, i don't need to have it turned on as long as when it is laggy. And the display really needs most of the battery-power, so i may even save battery, when i can turn it off earlier.
Return to 600mhz
I can not use the overclock because when I reboot the phone it is on 691Mhz soon after he returns to 600mhz. I know that the CPU clock is dynamic, but he never returns to 691mhz. What did I do wrong? I used the XDA tutorial for overclocking.
Don't work yet
I just try full wipe and did not work. I think it's some parameter or file permission...

[Q] Some problems in XGin4.0 2.3.4

Hi guys! I have to post in this general section just because I have not reached 10posts yet in "android development".
So I upgraded shpit's ROM from XGin3.0 to XGin4.0 just one hour ago, and i discovered two (maybe stupid) problems: i can't install Facebook and Applanet!
But system seems to work fine just for now.
Anyone can help me?
Thanks in advance.
achill3r said:
Hi guys! I have to post in this general section just because I have not reached 10posts yet in "android development".
So I upgraded shpit's ROM from XGin3.0 to XGin4.0 just one hour ago, and i discovered two (maybe stupid) problems: i can't install Facebook and Applanet!
But system seems to work fine just for now.
Anyone can help me?
Thanks in advance.
Click to expand...
Click to collapse
Reboot to xrecovery, clear cache and delvik cache..
then try to download again...
Working!
malungkot said:
Reboot to xrecovery, clear cache and delvik cache..
then try to download again...
Click to expand...
Click to collapse
Thank you man! I solved!
Hi, ive just installed Xging 4.0 and its great Rom but i have some problems, i hope you can help me to solve them:
- I cant get the Overclock: i put the X8oc.ko module into system/lib/modules and edit the permissions but nothing happens, after reboot i cant modify the Max or Min Cpu fercuency...
- I cant see the Mddi lag fix in system/lib/modules, thats not usefull in this rom??
ive been looking for this module because i have some lags in games.
thanks and sorry for my bad english.
leonardv128 said:
Hi, ive just installed Xging 4.0 and its great Rom but i have some problems, i hope you can help me to solve them:
- I cant get the Overclock: i put the X8oc.ko module into system/lib/modules and edit the permissions but nothing happens, after reboot i cant modify the Max or Min Cpu fercuency...
- I cant see the Mddi lag fix in system/lib/modules, thats not usefull in this rom??
ive been looking for this module because i have some lags in games.
thanks and sorry for my bad english.
Click to expand...
Click to collapse
first try this
reboot to xrecovery and flash xgin4
factory reset ( full wipe )
exit and with root explorer just and only copy X8oc.ko in system/modules
don't edit hw_config it's already configured
go to settings and and choose cyanogenmod settings
then go to performance and select cpu settings
there should be max and minimum set maximum speed on whatever works just don't try to get it too much high the higher freq won't always make the system better sometimes it won't even reboot and works fine but the speed isn't better than lower freq
u can use quadrant to find it out and check your cpu score when you increase freq your score should be higher if you noticed that it's not increased or it just got lower on score ! revert it back to lower freq and see if your phone works without reboots and hangs
and second
mddi module is preinstalled it is present on modules and yes it is not configured in hw_config but i believe it is loaded and the run command must be somewhere in firmware and maybe in lib files
dragunov_lq said:
first try this
reboot to xrecovery and flash xgin4
factory reset ( full wipe )
exit and with root explorer just and only copy X8oc.ko in system/modules
don't edit hw_config it's already configured
go to settings and and choose cyanogenmod settings
then go to performance and select cpu settings
there should be max and minimum set maximum speed on whatever works just don't try to get it too much high the higher freq won't always make the system better sometimes it won't even reboot and works fine but the speed isn't better than lower freq
u can use quadrant to find it out and check your cpu score when you increase freq your score should be higher if you noticed that it's not increased or it just got lower on score ! revert it back to lower freq and see if your phone works without reboots and hangs
and second
mddi module is preinstalled it is present on modules and yes it is not configured in hw_config but i believe it is loaded and the run command must be somewhere in firmware and maybe in lib files
Click to expand...
Click to collapse
Ok thanks ill try again.
Wipe partition cache and full wipe.
Sent from my X8 using XDA Premium App

FEB-9-15 [] Post_boot tweaks - An *interactive* boost

Drop this file in your /system/etc folder, replacing the stock one. Cleaned up, and modified to work with a stock kernel or lean kernel.
Please open up the file, and read some of the notes I added, so you know what this does and how to change it if you so desire. It is very basic and straightforward.
Also, please remember one thing, if you want to go to the stock kernel, simply change any words in the scripts from "interactiveX" to "interactive".
Recommended lean kernel 3.16 with these scripts.
Designed to work with ALL Galaxy Note 3's running touch wiz 4.4.2 ROMs and running lean kernel or stock kernel. Other kernels are not guaranteed due to the voltages applied.
This will make a huge difference in performance and battery. Been using this (developed by me) for a long time now.
Summary:
*I/O optimization
*tuned interactive parameters
*fixed sysfs permissions for cpu's (root now has full control of sysfs tuneables)
*GPU sysfs identified for user to customize
*screen off frequency set to 1.2 GHz (can be changed by user)
*custom voltage set for bin 2 device. (Read instructions within file to adjust for others bins accordingly)
*custom mpdecision tuning and other relevant instruction regarding mpdecision binary
*general CPU tweaks for better performance, responsiveness and battery life (yes all 3 can be achieved, and are)
Again, open the file with a file explorer (or notepad+ in windows). Read it, understand it, adjust what you want, or leave it be. These settings are very much dialed in for the interactiveX governor of LK. It won't get much better. I'd say take a look at the voltage portion and mpdecision for now (found at the end).
Once more, drop file into the /system/etc directory... Replace the existing one, and reboot.
FILE DOWNLOAD
Updated today... many useful changes, and fixes (set up for stock kernel for now)
https://www.dropbox.com/s/tjlygujptls3lks/init.qcom.post_boot.sh?dl=0
Man that's one hell of a disclaimer.
Just giving you all a heads up.... I think there may have been a few errors in the stock init.qcom.post_boot file (they are human too, remember).
I am testing a few small changes to certain lines in the "factory" script to make sure. A brief explanation of it is that there are certain lines I removed from the one you all are using right now, and I did so because the file paths being called out did not exist!
However, I was going over this again tonight, getting ready for the official LP release and decided to review this odd discrepancy one more time. After doing some digging, I found that the file that some of those values were intended to be written to, were actually somewhere else!
Doh! - Sammy/QC. It is very possible that this location changed from a previous design or fs structure and somebody simply forgot to modify the script. Very interesting indeed.
Anyways, after I run this for a couple of days and do a little bit more investigating, I'll post the updated script for all of you.
Was wondering if anyone tried this, ill wait til after you update n test!
Updated dl link.. give it a go
I tried it didn't seem to have a noticeable difference in my opinion . I of course used the first script have yet to try the update.
Tried it
red_can_soda said:
Updated dl link.. give it a go
Click to expand...
Click to collapse
My phone started rebooting after 2 to 3 minutes....not sure what it is..perhaps low voltage or frequency...
red_can_soda said:
Updated dl link.. give it a go
Click to expand...
Click to collapse
Been running it all day no issues.
carl1961 said:
Been running it all day no issues.
Click to expand...
Click to collapse
Notice any improvement?
setfly95 said:
Notice any improvement?
Click to expand...
Click to collapse
I really haven't had time to notice, I will know in a few days.

Categories

Resources