Database Users

Get aospCmod 2.3 to boot on your Hero

EDIT: thread no longer needed - ROM boots at 691 now
This is for the limited heroes which cannot function at 768mhx, like mine. First let me say you need to go to the GB thread and read the wiki for rom install intructions FIRST. I have added a section on that wiki page about kernels and clockspeeds near the bottom. Ok, the stock aospGB kernel or deca's uncapped #589 both scale to 768 freely, and some heroes can't handle that high of a frequecy but CAN handle speeds over 691.
I have FINALLY figured out how to get the kernel to BOOT less than 768 reliably, and it was super easy. I have tested it on deca's uncapped #589 so far. I have updated the main page of the wiki AGAIN about freezes/bootloops with this info if people need it later. The GB wiki is "readme" in the OP of the aospGB thread.
Instructions: First I assume you are on 01/28 GB already, running a capped 691 kernel or deca's #43 scaled to your max. Go into your root explorer app, navigate to system/ etc/ init.d/ and open the "30cpumem" file with the text editor, change the max frequency to whatever your phone can handle,i.e. 710xxx,729xxx,748xxx (mine is 729600). Then reboot into recovery and flash the #589 uncapped 768mhz kernel, and the reboot the phone. This worked for me with no hiccups. Since I used root explorer, I can't tell you the adb codes, so if you know them feel free to make the same file edit that way - and update the wiki if it works. Happy trails.
CREDITS:
aosp and the CM7 team for the rom
decad3nce for the overclocked kernels

The stock kernel should only boot at 691. 30cpumem already reads that for me, and I have never touched that file. Also, whenever I flash the newest update and use No-Frills, the max is always already set @ 691 as well.

stayclean said:
The stock kernel should only boot at 691. 30cpumem already reads that for me, and I have never touched that file. Also, whenever I flash the newest update and use No-Frills, the max is always already set @ 691 as well.
Click to expand...
Click to collapse
hmm, well, guess I'm a little past due then. lmao. Well, the info still works if you want to go OVER 691 at boot, like me with 729. Thanks for thr info though.

Thread closed by OP's request.

[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

[Q] Running CM7.2 (MiRaGe-KANG build) - How do you know V6 is working? Wi-Fi Question

Hi All,
I'm new here but have been reading the threads since I got a Nook Color last month.
I'm booting from a 16GB microSD card: [CM7.2-RC0] MiRaGe - KANG build of CyanogenMod ("encore_CM72-MiRaGe-12122011") and also installed "gapps-gb-20110828-signed"
I ran the Battery Calibration tool just yesterday when it was plugged in and at 100%
I installed the Nook Color USB Mass Storage utility so that I could access the SD card from my computer
I also followed the thread's advice on installing V6 Supercharger (http://forum.xda-developers.com/showthread.php?t=1344873):
Nook Color with its large kernel with many features consumes the RAM rapidly and low memory becomes an issue where V6 Supercharger becomes useful.
Here is how I install, it takes only one minute.
- Download update 8 to sdcard root directory.
- Start Terminal Emulator and do the followings
- su
- cd /sdcard
- sh V6*
- choose option 0 (fastest scroll)
- choose 9
- choose option 16 to reboot ​
I have a couple questions that I can't ask in the dev threads since I just registered here.
How do you check if V6 Supercharger is working? I didn't install BusyBox or Script Manager like the original V6 Supercharger thread suggested...so is there a way to do this through the Terminal Emulator?
What do you recommend overclocking your CPU settings in CyanogenMod settings to? I have mine currently set to Conservative, Min: 300 MHz, Max: 1100 MHz, and Set on boot. Would 1200 MHz be pushing it too much?
I've read some questions and threads on here regarding the Wi-Fi turning off when it goes to sleep. When you press the side power button to turn off the screen, is that also putting the device to sleep? Is there a solution to the problem of the Wi-Fi turning off on its own when the screen is off?
Thanks in advance to any advice or answers! And of course, if you have any suggestions on other things I should be installing/uninstalling I'd greatly appreciate it!

AngelWings8 said:
I have a couple questions that I can't ask in the dev threads since I just registered here.
How do you check if V6 Supercharger is working? I didn't install BusyBox or Script Manager like the original V6 Supercharger thread suggested...so is there a way to do this through the Terminal Emulator?
What do you recommend overclocking your CPU settings in CyanogenMod settings to? I have mine currently set to Conservative, Min: 300 MHz, Max: 1100 MHz, and Set on boot. Would 1200 MHz be pushing it too much?
I've read some questions and threads on here regarding the Wi-Fi turning off when it goes to sleep. When you press the side power button to turn off the screen, is that also putting the device to sleep? Is there a solution to the problem of the Wi-Fi turning off on its own when the screen is off?
Click to expand...
Click to collapse
1. Open your app drawer, flick the screen, if it scrolls instead of stuttering then V6 is working.
2. OC as much or as little as you want. 1200 is safe but some people say that the increased battery drain isn't worth the slight increase in speed. You have to decide for yourself.
3. Yes, that is putting the device to sleep, yes, that will turn off your wifi. Most people prefer sleep to just screen off because it saves your battery. The old CM7.0.3 and earlier didn't have sleep mode and you lost 1-3% of battery per hour of standby. If you're ok with that then:
wireless & network settings > wi-fi settings > menu > advanced > wi-fi sleep policy>never

Thanks a bunch! I was wondering why there wasn't an "Advanced" option when I went to Wi-Fi settings...didn't even think to press the menu button! I chose to set the sleep policy to "Never when plugged in" and we'll see if that works for me. Is the default "When screen turns off"?

yup, it's been the default on every android device i've used. It allows you to put your device to sleep and then turn it back on when you need it without having to wait for android to boot. I can tell when an app kept my nook from sleeping because my battery is dead.

I installed the Nook Color USB Mass Storage utility so that I could access the SD card from my computer
Click to expand...
Click to collapse
I don't think you (we) need this step since I believe the feature has been integrated into the latest CM7 builds, assuming MiRaGe the same.
1. Open your app drawer, flick the screen, if it scrolls instead of stuttering then V6 is working.
Click to expand...
Click to collapse
Without even installing V6 Supercharger, I don't believe that I ever experience the stuttering. If that's the case, how do I know the V6 script is working/running/better performance?

votinh said:
Without even installing V6 Supercharger, I don't believe that I ever experience the stuttering. If that's the case, how do I know the V6 script is working/running/better performance?
Click to expand...
Click to collapse
You can tell it's installed Ok by running it again and using option 1 to show the status.
Not so easy to tell its immediate benefit as its real job is trying to ensure that the memory is kept free, so you have to compare operation over time as more apps get used / loaded.

You know, I'm not sure if I ever experienced the stuttering either. I'll have to check later today.
If I just used the Terminal Emulator, would I essentially do these steps?
- su
- cd /sdcard
- sh V6*
- choose option 0 (fastest scroll)
- choose 1 (to show status)
- choose option 16 to reboot
Also, just want to confirm that you need to keep the V6 file in the sdcard root directory right? I'm assuming if you ever delete or move the V6 file, V6 Supercharger would stop working?

By definition, "root directory" of the bootable CM7 uSD card is the one that has 117MB where ROM/GApp zip files used to be. If that, I don't believe that we (or NC) can access that partition. If it does, I want to know too.
With CM7 runs off eMMC, root directory of "normal" uSD card is ......... ehh, not in any sub-folder.
Can someone who actually do run V6 script chip in for some info?
Big thanks

Oh I'm sorry, when I wrote "sdcard root directory", I mean the root directory of what you can access when you plug it in via USB and not the partition where you're booting CM7 from. It's essentially where I save all my folders of wallpapers/music/videos/etc.

AngelWings8 said:
Oh I'm sorry, when I wrote "sdcard root directory", I mean the root directory of what you can access when you plug it in via USB and not the partition where you're booting CM7 from. It's essentially where I save all my folders of wallpapers/music/videos/etc.
Click to expand...
Click to collapse
Oh, ok.
Did you run the script yet? How was it?

No offense to the person that suggested checking V6 by flicking the app drawer, but there are a couple more reliable options.
I am no expert, by any means, but from looking over the program, it looks like all it really does is prioritize your apps by whether they are foreground or back, a launcher or hidden and so on, then allocate memory to the apps following that priority. I think any response check would wholly depend on how many apps you have running (or being killed by the V6 task killer)
Either way, even if it turns out that I wholly misunderstood the program, I can tell you how to see if it is installed and running for sure.
This will work if you have already installed the V6 or not. the following are directions for terminals, if you are running the dev's Scripter app, I would imagine it is similar, if not automatic.
Open a terminal.
su
cd sdcard/
sh V6*
the menu then scrolls. option 0 is often recommended here, but that is just a value for the scrolling speed of theV6 script itself. you can increase this number if you errant to spend a little time looking over what you're running.
f you think you have already ran the V6 look below the 17 options to current minfrees. If you want option 9 (Mirage Kang's recommendation) the current minfrees should read 6, 12, 75,100,125,150 mb. if it does, then you are supercharged. if not, go ahead and select option 9.
Now before you reboot, I would recommend that you run option 15 if you are not using Scripter. that will run V6 through the terminal emulator. That way, should you ever want to check your values or mess with the options, you can open terminal, su, then bash V6, and it will run.
Even if you don't think you will ever want to readjust the supercharger again, it had the added benefit of yelling you your "installation was INCREDIBLY SUCCESSFUL" which is bound to make you feel supercharged.
Run option 16 to reboot and now you can feel secure, without relying on a subjective flick of the app drawer.

Thanks everyone! I'm going to try uninstalling the USB Mass Storage app I downloaded then, if I don't actually need it with the CM7.2 version.
I did run Terminal Emulator to see what the minfrees were and it was the same as option 9. I didn't even think of running option 15, but I've done so now. After I rebooted, I opened up the Terminal Emulator again and typed "su" and then "bash V6" and it says "bash: V6: No such file or directory". Am I doing something incredibly stupid or wrong?
Also, do I have to leave the V6 txt file on the sdcard or can you delete it after you've run it?

I would bet it was a problem with case. bash v6 and bash V6 are two different things. Capital V should fix the issue.
Save the txt file, it is the actual script that is being ran. Without it, nothing happens.

I used bash V6 (and tried bash v6 just to see if anything would happen) and I got the same message. I thought maybe I just didn't do it right first time around, so I went back in, checked the minfrees and entered option 15 and then 16 to reboot, but when it did, it booted to the stock Nook Color OS. I just shut down and turned it back on and it went into Cyanogenmod with no problem...but is that strange that it didn't boot into CM? And once I got into CM again, I checked the overclock settings and it was back down to 800 GHz (even though I set it on boot at 1200 GHz).

votinh said:
By definition, "root directory" of the bootable CM7 uSD card is the one that has 117MB where ROM/GApp zip files used to be. If that, I don't believe that we (or NC) can access that partition. If it does, I want to know too.
With CM7 runs off eMMC, root directory of "normal" uSD card is ......... ehh, not in any sub-folder.
Can someone who actually do run V6 script chip in for some info?
Big thanks
Click to expand...
Click to collapse
That's a partition, not a directory. Every partition has a separate root directory.
With emmc, it's simpler because there's only one partition on the sd card so there's only one root directory. You can copy it over using usb or a sd card reader and it'll end up in the same place.
If you are running off the uSD, transferring files via USB places them on the "SDcard" partition on the uSD. That way, CF3D can find the files.
**I have a ton of apps, which may be the cause of my app drawer stuttering on flick (where you try to swipe to the bottom of your app list in one flick).

Thanks for all the useful replies! I uninstalled Nook Color USB Mass Storage app, and it seems to be working fine!
I saw that there is a new build for [CM7.2-RC0] MiRaGe - KANG and was wondering if you guys could kind of walk me through doing my first update. I downloaded both of these files listed in his first post:
- ROM - 01132012 build: MD5sum: 41676325569e773340378ba886dd6bf6
- transparency theme with circular battery indicator for 01132012 build. MD5sum: 9fb6a03e91f01c162a2f8f37cfe8ac77 Flash this theme after booting once with the new ROM. Do not use this theme with earlier or later builds.​
For installation, it says "Just follow the official CM7.1 installation via recovery guide (stable or nightly). The removed components will be retained on your NC from the previous ROM if you do not uninstall those (Titanium recommended) or do a clean wipe."
I do have Titanium and I backed up using the "all user apps and system data" option. Is that adequate or is there a different option I should be using? Also, since he mentions that the removed components will be retained on the NC if you don't uninstall those...how do you know which ones and how do you go about uninstalling those? I never actually used the uNooter or ROM Manager...so I'm trying to figure out how to make it work with the method I used the first time around (VeryGreen's: http://forum.xda-developers.com/showthread.php?t=1000957) What I've done is just renamed "encore_CM72-MiRaGe-01132012" with "update-" in the beginning, put it on the boot partition, and rebooted into recovery.

wrong button click, LOL
Anyway, that should be it.

Yeah, my NC seems to be working fine after just renaming it to "update-" in the beginning of the files and booting it into recovery, but the transparent battery indicator theme didn't seem to do anything
Also, this is a random question, but do your NCs' volume rocker thing seem kind of loose? I was just wondering if that's normal because mine you can move left and right (you can kind of wiggle the button itself).

AngelWings8 said:
Yeah, my NC seems to be working fine after just renaming it to "update-" in the beginning of the files and booting it into recovery, but the transparent battery indicator theme didn't seem to do anything
Also, this is a random question, but do your NCs' volume rocker thing seem kind of loose? I was just wondering if that's normal because mine you can move left and right (you can kind of wiggle the button itself).
Click to expand...
Click to collapse
My volume button does that too.

Oh good, I was hoping it wasn't some sort of issue with the button being broken or something.
Also, I asked this earlier, but could someone explain to me what to do since after updating a new [CM7.2-RC0] MiRaGe - KANG build, he says "The removed components will be retained on your NC from the previous ROM if you do not uninstall those (Titanium recommended) or do a clean wipe. If you don't need a clean wipe, i.e. current ROM is CM7.1, instead of step 5 in the guide, do wipe dalvik-cache only."
Is that what I should be doing? How do I go about it using VeryGreen's method (without using ROM Manager or ClockworkMod Recovery?)
I'm sorry if I just sound like a complete noob, but I'm trying to learn!

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.