Travisdroidx2 originally asked this in the Eclipse 2.0.2 thread, and rather than clutter that thread up any more. I decided to post his question here and answer it as well.
Travisdroidx2 said:
Moon Shadow - NM said:
If you are boot looping right now, there is no way besides a nandroid restore or an SBF. BTW, ZepplinRox's V6_SuperCharger_Script does work on Eclipse 2.0.2. However, there are a few things that you have to do to get it to run.
First, edit your /system/etc/init.d/99tweaks file and remove all oom and adj references. If you need more information on this, let me know.
Second, you are going to use build.prop and NOT init.rc.
Third, I recommend using Nitro's nullifier (I don't remember what option it is).
I use setting 6 for most of my work, and will drop to 5 or raise to 7 as the situation demands.
Ciao!
Click to expand...
Click to collapse
Moon Shadow thanks for your help. Last night after yo ureplied to my question on v6 I tried to edit and remove the lines you were talking about. What do you use to remove them? Root explorer or script manager? On root explorer I did not see the oom and adj script in there. I ran it in script manager and it just showed that things were failing.
Also on second step are you using mash up build prop and deleting any init.rc? Or am I way off? Sorry for the noob questions. I am still learning and appreciate all the support and help that I get from others on here. If I am way off then maybe I will just stick with the Stock Eclipse since it is so freat already
{
"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"
}
Click to expand...
Click to collapse
Actually, I use ADB to pull the files and edit them with GVIM or Notepad ++. Do not use regular Windows Notepad as it does not terminate lines correctly for Linux/Android. If you use Linux as your ADB machine, you are good to go. Use GVIM or nano or gedit or... (You get the idea.)
The lines I remove from 99tweak are:
Code:
# aggressive memory management
echo "0,3,5,7,14,15" > /sys/module/lowmemorykiller/parameters/adj
echo "2560,4096,6144,17408,19456,23552" > /sys/module/lowmemorykiller/parameters/minfree
As for the build.prop and init.rc. No, DO NOT remove either file. Just make the selection in V6_SuperCharger_Script. (By the way, I'm using v9 RC 4 of the script.)
Run the script as root in ScriptManager, or terminal, or adb, what ever you feel most comforatable doing. Now select the following:
Choose option 26. Driver Options, then select 0 as your speed setting, Then select Y for build.prop, select N for init.rc integration, select Y to disable the "animation".
Next choose option 20. Nitro Lag Nulifier, then select 1 to install it. (Don't reboot yet.)
Now, choose option 6. to Supercharge.
Now, choose option 30. to restart.
Hope that helps!
Ciao!
I have been using Script Manager from the Market, however, I would prefer to use ADB, under Windows 7. Can you post steps to connect? I already have the necessary drivers installed.
The problem I am having with U9 RC4 is that the options do not display for me (1-31), so I choose 6 and let it go from there...thanks for the quick steps above.
If I choose to edit the script using Root Explorer, am I editing the 99tweak in init.d or is it located elsewhere? Can I edit it after I run V6 before I reboot?
The options do display , when it asks which option just scroll back up a little bit and there they are. I thought the same thing
Sent from my DROID X2 using XDA App
y0himba said:
If I choose to edit the script using Root Explorer, am I editing the 99tweak in init.d or is it located elsewhere? Can I edit it after I run V6 before I reboot?
Click to expand...
Click to collapse
I always edit it before running v6 that way after running v6 u can just reboot from there and be good to go.
Make sure u delete the .bak that root explorer creates of the original 99tweaks script.
Where do I find V9? The threads I are updated to V8. I know V9 is a RC so its probably not in an official thread yet.
EDIT: Nevermind, I found it.
ashclepdia said:
I always edit it before running v6 that way after running v6 u can just reboot from there and be good to go.
Make sure u delete the .bak that root explorer creates of the original 99tweaks script.
Click to expand...
Click to collapse
I thought I had to run the V6 script in order for it to create the 99tweaks file? Hopefully I can run the V6, not reboot, edit 99tweaks then reboot.
Also, the script creates copies of the 999tweaks file in multiple places. There is a 99tweaks, then another files that has a .sh (script) extension, and there are multiple copies in multiple locations.
Which one do I edit? (Filename and location)
y0himba said:
I thought I had to run the V6 script in order for it to create the 99tweaks file? Hopefully I can run the V6, not reboot, edit 99tweaks then reboot.
Also, the script creates copies of the 999tweaks file in multiple places. There is a 99tweaks, then another files that has a .sh (script) extension, and there are multiple copies in multiple locations.
Which one do I edit? (Filename and location)
Click to expand...
Click to collapse
99tweaks is the ECLIPSE scripts.
99supercharger is the v6 scripts.
U r editing 99tweaks if u haven't deleted it at all already
system/etc/init.d/99tweaks.
Are u running eclipse? Lol
The reason u are editing those lines out of 99tweaks is because those lines will "conflict" with the 99supercharger script. Don't worry about editing 99supercharger. U need to edit 99tweaks bcuz those lines change the "minfrees and oom grouping " which is what u are using v6supercharger for.
Have I confused u yet? lol j/k
Moon Shadow and Ash thank you very much for the help!! I was able to follow your steps and deleted the files from the 99 tweeks and run v6 v9 rc4 and set it up just like moon shadow said. Great instructions thanks again for your patients
Actually no, that was the exact answer I was looking for. I never really dug into the script itself until this issue arose, so did not realize that Eclipse (Yes, I am running it) had it's own Supercharge, so to speak. What are the advantages of V6 over Eclipse's built-in scripts? Do I need V6?
I was using V6 with the stock for battery. Example: Stock, 2 hours of listening to music over Bluetooth, 20 minutes talk time, GPS, WiFi, data running, when I would return I was at 67% battery. With V6 that number changed to 80% and it was much faster.
y0himba said:
Actually no, that was the exact answer I was looking for. I never really dug into the script itself until this issue arose, so did not realize that Eclipse (Yes, I am running it) had it's own Supercharge, so to speak. What are the advantages of V6 over Eclipse's built-in scripts? Do I need V6?
I was using V6 with the stock for battery. Example: Stock, 2 hours of listening to music over Bluetooth, 20 minutes talk time, GPS, WiFi, data running, when I would return I was at 67% battery. With V6 that number changed to 80% and it was much faster.
Click to expand...
Click to collapse
All I know is my phone performs better when using v6supercharger lol
I go wit what works. And I know this setup works for me
I love the tutorial at the top, original post. This should be a sticky.
Anyone want to post a tutorial for accessing your Droid X2 via ADB on Windows 7?
y0himba said:
Anyone want to post a tutorial for accessing your Droid X2 via ADB on Windows 7?
Click to expand...
Click to collapse
I guess I'll start working on an adb tutorial for the DX2. I see enough "How do I do that?" questions that I think it is warranted at this time. I'll post it in the General section with my other tutorials.
[EDIT]
Actually, I ran across an EXCELLENT adb tutorial... I'm not going to re-write the wheel on this one. This guy did a knock out job of it. Here is his tutorial: http://forum.xda-developers.com/showthread.php?t=1241935
[/EDIT[
Ciao!
I installed the supercharger script V9 RC4 and used the options you listed. After rebooting, my wifi didnt work anymore. I unsupercharged with the scripts built in option and wifi worked again. So I know it was the script. If we run this script do we HAVE to delete those lines you were talking about? If not, I dont know why it ruined my wifi connection.
EDIT: Im still on Eclipse 1.3 BTW.
Moon Shadow - NM said:
I guess I'll start working on an adb tutorial for the DX2. I see enough "How do I do that?" questions that I think it is warranted at this time. I'll post it in the General section with my other tutorials.
Ciao!
Click to expand...
Click to collapse
This is awesome.
I can't wait to read it.
I have been curious about adb for a while also...and ur tutorials are always easy to follow and very well written. Thanks!
jsgraphicart said:
I installed the supercharger script V9 RC4 and used the options you listed. After rebooting, my wifi didnt work anymore. I unsupercharged with the scripts built in option and wifi worked again. So I know it was the script. If we run this script do we HAVE to delete those lines you were talking about? If not, I dont know why it ruined my wifi connection.
EDIT: Im still on Eclipse 1.3 BTW.
Click to expand...
Click to collapse
That is a known issue with the 3G_TurboCharger Script, but not with V6_SuperCharger. Zep has implemented a potential fix for the WIFI problem with the 3G_TurboCharger, and it MIGHT fix your WIFI issue, however, I'm not sure. In fact, there are several things you can do to troubleshoot the issue.
Here is the link to the thread that has the 3G_TurboCharger: http://forum.xda-developers.com/showpost.php?p=18703418&postcount=5021. You will want to select option 8, the Wi-Fixer.
I don't think this is the issue, though. A few troubleshooting things to try:
1. Are you on GB 2.3.5? There was another member that was having huge WIFI issues on 2.3.5. He finally solved the issue by turning off QoS (Quality of Service).
2. Are you on Eclipse 2.0.1? If so, that version has a known problem with WIFI. Update to 2.0.2.
3. Have you tried resetting (power cycling) your wireless router? There have been reported problem with some routers holding invalid information regarding an android device, thus causing issues with the wireless connection.
Try these and let us know how it goes.
Ciao!
Moon shadow thanks again for your tutorial. It allowed me to set up v6 supercharge properly as well as helpfull hints from Ash like deleting the. BAK file root explorer makes. I also realized before i was using version 7 and not version 9. Now when i run the script everything stuck and phone is running great. I will read your latest tutorial on adb as this is something new to me and i really appreciate all the help and support!
Moon Shadow - NM said:
That is a known issue with the 3G_TurboCharger Script, but not with V6_SuperCharger. Zep has implemented a potential fix for the WIFI problem with the 3G_TurboCharger, and it MIGHT fix your WIFI issue, however, I'm not sure. In fact, there are several things you can do to troubleshoot the issue.
Here is the link to the thread that has the 3G_TurboCharger: http://forum.xda-developers.com/showpost.php?p=18703418&postcount=5021. You will want to select option 8, the Wi-Fixer.
I don't think this is the issue, though. A few troubleshooting things to try:
1. Are you on GB 2.3.5? There was another member that was having huge WIFI issues on 2.3.5. He finally solved the issue by turning off QoS (Quality of Service).
2. Are you on Eclipse 2.0.1? If so, that version has a known problem with WIFI. Update to 2.0.2.
3. Have you tried resetting (power cycling) your wireless router? There have been reported problem with some routers holding invalid information regarding an android device, thus causing issues with the wireless connection.
Try these and let us know how it goes.
Ciao!
Click to expand...
Click to collapse
1. I am On 2.3.4 still. I havent updated to 2.3.5 yet
2. Im running Eclipse 1.3 still
3. Its not my router because after uninstalling the script, my wifi worked again.
I am using a couple other scripts. The speedy script and the build.prop mash-up script. They might be conflicting with the wifi but I wouldnt know what to change.
After a day of running stock 2.02 i flashed v7 and also mash up and my performance of my phone dropped. I confirmed this with benchmark 2011 and must have ran it 30 times. I got way better numbers running stock rather than with both of the other scripts. I restored back to stock and percormance was back up. I was happy with the stock eclipse but have to say so far moon shadow set up seems to be running great i am very pleased with the performance right now and my benchmark 2011 scores went up even higher.
jsgraphicart said:
1. I am On 2.3.4 still. I havent updated to 2.3.5 yet
2. Im running Eclipse 1.3 still
3. Its not my router because after uninstalling the script, my wifi worked again.
I am using a couple other scripts. The speedy script and the build.prop mash-up script. They might be conflicting with the wifi but I wouldnt know what to change.
Click to expand...
Click to collapse
Did u try "forgetting" the network in wifi settings and setting up a connection again?
ashclepdia said:
Did u try "forgetting" the network in wifi settings and setting up a connection again?
Click to expand...
Click to collapse
No, I didnt. I'll try that when Im at home and run the script again. Thanks.
Related
Well, I'm not much of a guide person, but there's a great tool that's been out for a long time that has proven to be quite useful to me. THIS IS NOT A REPLACEMENT FOR FREEZA'S GUIDE. That's an excellent guide, and he deserves full credit for it. This guide is for those of you who want to trim/debloat after you flash. It also serves many other handy uses, which I shall explain in a few.
Also keep in mind, this will work on damn near ANY rooted Android phone. In fact, I used to use it QUITE a lot on my old Sprint Hero. This is essentially ADB without the need to know how to use the command line.
~~ This guide is a constant WIP ~~
What is Android Commander?
It's an all-in-one tool that was designed using adb. It provides the following:
[*]Complete root-based file manager
[*]Applications Manager
[*]Rebooting/Powerdown Abilities
[*]Storage Monitor
[*]All around awesome tool
It's completely free to use and is written by a talented XDA developer.
Requirements:
Windows XP or higher: As if I'm going to give you link to this
My little ADB Package: http://dl.dropbox.com/u/345001/Images/AC Guide/ADB.rar (For anyone wondering why I'm giving this seperate, it's to save you the trouble of having to download the entire android sdk and going through the convoluted method of using the SDK manager to grab adb)
Android Commander written by our very own XDA user PanPiotr: http://androidcommander.com/
1. Download my ADB package, and extract is somewhere. Inside is a folder called ADB, with two dlls and the adb executable. Remember where you put it.
2. Download and install Android Commander.
3. Right click and run Android Commander as administrator. It will ask you to set the ADB path near the bottom. Select the ADB folder that contains the 3 files above, which you downloaded already.
4. If it doesn't automatically start the app after selecting the folder, simply press exit, and run it again as administrator. This time, the app will start up
And this is what you see!
{
"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"
}
Now for starters, you'll notice a plethora of information. Try not to get overwhelemd. Android Commander is a ridiculously comprehensive utility. And the best part is that it's based entirely on ADB. Now, by default, you'll see your Windows files on the left pane, and the Android files on the right.
Let's begin with the debloating. Start by finding the "System" folder first.
From here, head on over to the "app" folder.
So this should be pretty self explanatory. Start selecting checkboxes for apps and bloatware that you don't want/need. Then, just click the "delete" button. It will delete them all in one shot.
I know this seems a bit anticlimactic, but that's more or less it for the debloating guide, because that's only one of the many uses AC has. Read on to the next few posts for a few scenarios/possibilities that you may encounter while using custom ROMs.
Basic Scenarios/Uses
This post covers basic scenarios and uses for Android Commander.
[If you've been directly linked to this post, please see the post above for information on installing and getting Android Commander up and running]
Remember, AC can start functioning as quickly as just moments after you see the white HTC screen. It doesn't have to be fully on for you to use AC and all its features. Android Commander can also be used from recovery as well.
Help! I used SetCPU, checked "Set On Boot", overclocked too high, and now my device is in a boot loop
Not a problem! I've done this too many damn times to count. The solution comes down to two options; one, be super fast when booting up and try and clock down SetCPU when you get in (very frustrating), or use AC! Remember, Android Commander can be used either in recovery or even during boot! So what we're going to do is start it up, and uninstall SetCPU. Let's open up Android Commander, and select "Applications Manager". It will ask you if you would like to update the list of applications, click yes.
From this point on, you can now see all of your applications. Simply click on one of the applications, and either uninstall it using the buttons above, choosing to delete its data or not.
By the time your device finishes rebooting, or when you boot out of recovery, you'll find SetCPU gone and your device no longer locking up and bootlooping! Easy, huh?
Did you know you can reboot the device from Android Commander?
Yes, you can . Simply click on the "Phone" menu up top:
Pick what you want to boot in. Also, yes, you see "screenshot" in there, but it currently doesn't work for the EVO 3D. It should for older devices though.
Did you know you can flash a recovery image through AC?
Indeed, you can.
More to come!
Advanced Uses - For Devs/Themers
This section is intended for both budding and veteran ROM cooks, modders, and themers.
Did you know that you can set file permissions with Android Commander? You can do what root explorer does, just fine. If you choose to use the 7.9.9.9 beta and up, you can easily set file permissions of any file, as shown below
MORE TO COME
First part of the guide is up
Thanks for this, I look forwards to seeing what more comes to this guide. Well done man.
empiire said:
Thanks for this, I look forwards to seeing what more comes to this guide. Well done man.
Click to expand...
Click to collapse
Glad you find it useful. It's got a ton of potential for devs such as yourself, I'd highly recommend you experiment with it, there's stuff I still don't even know about yet.
It even has it's own pre-"su"'d command line built into it.
Updated the "basic use" post to include more awesome little details
This is a nice tool! im definitively gonna be using this! thanks!!
steal25 said:
This is a nice tool! im definitively gonna be using this! thanks!!
Click to expand...
Click to collapse
Let me know what other cool features you end up finding, I'm sure you'll run into plenty of stuff I haven't found yet.
This will be loaded before the sun sets. Thanks for sharing - great utility.
Sent from here using this. Black. Slab.
Thats a pretty slick app.
I did everything stated in the first post, and for some reason it doesn't say I am rooted. so I don't have the application manager. to be clear I don't need the SDK installed, just your file? I extracted it into a new directory and then set that as the path when I started up AC, it starts up, finds my phone, can explore it, reboot it, but it still says I am not rooted in the lower left corner of AC. I am not a noob when it comes to doing stuff with android, but am noobish with adb, never used it before, so i thought this would be a great tool for me to learn...if I can get it to work.
jbermi said:
I did everything stated in the first post, and for some reason it doesn't say I am rooted. so I don't have the application manager. to be clear I don't need the SDK installed, just your file? I extracted it into a new directory and then set that as the path when I started up AC, it starts up, finds my phone, can explore it, reboot it, but it still says I am not rooted in the lower left corner of AC. I am not a noob when it comes to doing stuff with android, but am noobish with adb, never used it before, so i thought this would be a great tool for me to learn...if I can get it to work.
Click to expand...
Click to collapse
Hmm. Did you run AC as admin?
LiquidSolstice said:
Hmm. Did you run AC as admin?
Click to expand...
Click to collapse
yep, followed everything in the first post...and yes, the phone is rooted. LOL. I am going to uninstall AC and try again, and see if that works...
problem - phones rooted - viper rom 1.2.1 stock kernal - downloaded the two files you have, installed your AC, and unzipped the ADB - start up, point it to that folder, then it has the little window that says DEVICE: NOT FOUND. have debug on, charge, i am the admin on the pc.
-----sorry------ now it runs only after i posted.... sometimes thats all it takes - now to test it out, looks very useful, and easy.... thank you
Thanks, Liquid. Way faster then using Root Explorer or manual adb. Wish I'd known about this ages ago.
Very usefull...but We realy need a UI manager to change icons ect....
Thanks Liquid - I used your LiquidSense ROMs over on the Hero side, and now that I've got my E3D, it's great to see you devving over here. I used Android Commander a lot on the Hero, so good to see it will still work for the E3D! Thanks for the Guide!
-mb
when i use the sign .zip file tool, i put a file on my desktop, then run the tool and cannot figure out where is put the new signed file at? Any help?
i changed the output folder to desktop, and nothing, it doesn't sign the file and ouput it....hmm...
Great guide! I use Android Commander for just about everything. Nice point on using it to get out of a boot loop. I discovered that when I had my Hero, and it saved me many times.
Sent from my s-off Shooter!
Attached Are The 3 Latest Updates For The 3GTurboCharger, V6 Supercharger, And 98KickassKernelTweaks.
General Instructions:
1. Place All Scripts On Root Of SD Card.
2. Rename The Scripts Removing .txt
3. You Must Create The "init.d" Folder Inside /system/etc Prior To Running The 98KickassKernelTweaks Script.
4. Use Script Manager To Load The Scripts.
5. All Scripts Need To Have "RUN AS ROOT" Checked First.
6. Then Select "RUN" And Follow The Instructions On The Screen.
7. Proceed To Next Set Of Instructions If Your Script(s) Warrant It.
Advanced Instructions For V6 Supercharger And 98KickassKernelTweaks:
1. Menu>More>Advanced Options>Config Check "BROWSE AS ROOT
2. /data 99Supercharger.sh Check Off Both "RUN AS ROOT And RUN AT BOOT"
3. /system/etc/init.d 98KickassKernel Check Off Both "RUN AS ROOT And RUN AT BOOT"
4. ***Possible Your Device Will Also Create 99Supercharger If The "init.d" Folder Exists.
More Info On It Go Here:
3GTurbocharger And KickassKernelTweaks
http://forum.xda-developers.com/showpost.php?p=15948434&postcount=1127
V6Supercharger:
http://forum.xda-developers.com/showthread.php?t=991276
As A Reminder This Was Created By Zeppelinrox And All Credit Goes To Him.
Files Are Now Attached For Easy Download.
I was under initial impression these werent needed after the GB update? I guess i was mistaken?
SuBDivisions said:
I was under initial impression these werent needed after the GB update? I guess i was mistaken?
Click to expand...
Click to collapse
This Post Doesn't Specify For Froyo Or Gingerbread Users. It's Up To The User, And I'm On Gingerbread And I Find All 3 Beneficial.
Now that we have the init.d hack will the kickasskernal with the IO tweaks work? Or should I just use the IO tweaks that come with navenedrob's script?
I Vote You Should Try It And See If It Works. Make A Backup First.
It boot looped...........
Do I have to sbf? Or could I just use the nandroid?
Throw The Phone Out Now. You Royally Messed Up. Geez Leave You Alone For One Minute And Look What You've Done. Nandroid Is Just Fine, No SBF Necessary.
WAAAAHHHHH no fair.... oh look it rebooted.....
So yea I am gonna try to use the IO tweaks from navenedrob's script as well as the cpu tweak from his script oh on top of the SD read ahead one. Those should work well with supercharger and kickasskernal I think. Those do not touch the cpu freq right?
I Don't Have Any Reason To Believe It Would.
Awesome, everything is working great.
My cpu is set to 1000 min and max. Sd read ahead is working but umm how do I know if the IO tweaks are working?
Sent from my DROID X2 using Tapatalk
Anyhow... now that I have my cpu at 1000 min/max I want to separate the cpu freq tweak and have different freq scripts for battery saving.
Sent from my DROID X2 using Tapatalk
How are these scripts running for X2 owners? Any major issues so far?
triton302 said:
How are these scripts running for X2 owners? Any major issues so far?
Click to expand...
Click to collapse
I Think They Work Fantastic, Personal Opinion. No Issues At All.
Mods like this one should also go to the Droid X2 Dev forum.
navenedrob said:
Mods like this one should also go to the Droid X2 Dev forum.
Click to expand...
Click to collapse
This Was Actually A Toss Up, Because Zep Started A Thread In The General.
i tried the scripts on p3 and it actually made it use marginally more ram and it was glitchy. i dont remember what numbers i used but i got them from this forum somewhere. either way when i tried to undo it i got a reboot loop so i sbfed and went back to p3. after looking into it some more ive read some places that you dont need this if you arent running froyo. any truth to this?
I Don't Think It's Been "Proven" But Rather A Preference. I'm Using All 3 On P3's Along With Various Other Tweaks I've Taken From Others. I Have 40 Running Apps With 100Mb Of Ram And My Phone Is Still Lightning Fast. So My Conclusion Of "Truth" Is These Help Tremendously. On The Other Hand A User Like Yourself Claims It's Worse. I Hope That Helps In Understanding What You're Asking.
so what you are saying is that its personal preference and doesnt really matter that much?
how many people here use the V6 Supercharger Script with their Streak?
I'm having trouble with it and was hoping other more adept streakers know what the hell is going on with mine...
so I've run probably every script since the first one, but, it turns out the instructions I got weren't as complete as they could have been, and inadvertantly, I ran the scripts as the .txt and .pdf file formats that they came in.
I also saw a tutroial that involved changing a file name using root explorer, which I also never did.
i also did this for the 3G and kernelizer tweaks aswell
so now I have the latest script version and I notice that it's not working, I have no idea how long ago it stopped...
what I would like to know is:
A: how to totally clean all of it from my system, in order to start a totally fresh install.
B: how to properly install all three of the the scripts on the streak.
anybody nice enough to help me?
I use it...since version 8.
I use the latest version, along with the 3g & kick ass kernal tweak.
I use option 6, multitasking, 512 leaded.
Drop in here>> http://forum.xda-developers.com/showthread.php?t=991276 I'll bet someone can help you.
I've tried following all the instructions, even some from other tutorials, I've un supercharged and started from scratch.
how did you make yours stick?
bugmenotacc said:
how many people here use the V6 Supercharger Script with their Streak?
I'm having trouble with it and was hoping other more adept streakers know what the hell is going on with mine...
so I've run probably every script since the first one, but, it turns out the instructions I got weren't as complete as they could have been, and inadvertantly, I ran the scripts as the .txt and .pdf file formats that they came in.
I also saw a tutroial that involved changing a file name using root explorer, which I also never did.
i also did this for the 3G and kernelizer tweaks aswell
so now I have the latest script version and I notice that it's not working, I have no idea how long ago it stopped...
what I would like to know is:
A: how to totally clean all of it from my system, in order to start a totally fresh install.
B: how to properly install all three of the the scripts on the streak.
anybody nice enough to help me?
Click to expand...
Click to collapse
It has been made very clear by some of the senior developers here that V6 does not work on the Streaks because of some type of conflict with how the memory is allocated or configured or something, that's one of the reasons that it isn't implemented into the ROMs... so it's just snake oil, a placebo for a Streak owner. I'm not saying it doesn't work on other devices, but it DOES NOT work on the Streak
Is there a post by a dev anywhere that explains it?
Will AutoKiller Memory Optimizer work? It must this device that it doesn't work on... the minfree file disappears or something
zeppelinrox said:
Is there a post by a dev anywhere that explains it?
Will AutoKiller Memory Optimizer work? It must this device that it doesn't work on... the minfree file disappears or something
Click to expand...
Click to collapse
Yeah, but for the life of me I can't remember exactly where but what I wanna lean towards it being in fards' GingerStreak thread
I'll try and find it...
BUT the newest version does put ALL the supercharging in init.rc...
A dev just has to put it in their boot.img
zeppelinrox said:
Is there a post by a dev anywhere that explains it?
Will AutoKiller Memory Optimizer work? It must this device that it doesn't work on... the minfree file disappears or something
Click to expand...
Click to collapse
I used to have it installed but I couldn't see where it was ahving any effect or benefits so I uninstalled
I'm wanting to see what the V6 Scripts will do for CM7 but I cannot for the life of me get them to stick upon reboot.
I have them setup via Script Manger to run as root. I've gone in, did option 6 (0,4,10,12,14,15) and option 20.
Upon reboot, the settings in /sys/module/lowmemorykiller/parameters/adj are set back to the default CM7 settings
I've tried setting the properties in both local.prop and build.prop, but nothing seems to stick.
I've tried integrating the settings of the init.rc into the ROM and not doing that.
None of these options seems to make the low memory killer settings I set in V6 stick and it ALWAYS reverts back to the stock CM7 settings.
I know I can just rerun the script after it's done booting, but I never had to do this with other ROMs as it would integrate fine in /etc/init.d and run.
I see in the /etc/init.d a S99SuperCharger script with the correct permissions set. I can run it via sh and it sets the properties correctly.
It just seems that CM7 is overwriting the low memory settings somewhere and I don't know where. I don't see it occurring in any of the supplied scripts from CM7 in the /etc/init.d and I don't see it in the build.prop file.
Any ideas? I know I could just tell Script Manager to run the script on boot, but that's usually not recommended except as a last resort.
I guess the real reason I would like to get this working the way it normally does (via the init.d scripts) is just to understand what CM7 is really doing.
Thanks!
Perhaps CM7 has some sort of memory management of it's own that sets things back to the defaults on boot????????
I know, not much of an answer but it's the best I can come up with.
robocuff said:
Perhaps CM7 has some sort of memory management of it's own that sets things back to the defaults on boot????????
I know, not much of an answer but it's the best I can come up with.
Click to expand...
Click to collapse
That's what I figured is happening. I just have to determine where it's happening at.
I see that the V6 scripts are running, but something is setting it AFTER the init.d process is done.
I also checked the /data/SuperChargerRan log file and this is what I saw:
02-16-2012 09:20:53: Applied Settings from /system/etc/init.d/S99SuperCharger!
02-16-2012 09:20:54: DIDN'T Apply Settings from /data/99SuperCharger.sh!
Not sure why the second one isn't working.
Looking at the /sys/module/lowmemorykiller/parameters/adj file, it's back to the original settings that CM7 has: 0,1,2,4,7,15
iBolski said:
I'm wanting to see what the V6 Scripts will do for CM7 but I cannot for the life of me get them to stick upon reboot.
I have them setup via Script Manger to run as root. I've gone in, did option 6 (0,4,10,12,14,15) and option 20.
Upon reboot, the settings in /sys/module/lowmemorykiller/parameters/adj are set back to the default CM7 settings
I've tried setting the properties in both local.prop and build.prop, but nothing seems to stick.
I've tried integrating the settings of the init.rc into the ROM and not doing that.
None of these options seems to make the low memory killer settings I set in V6 stick and it ALWAYS reverts back to the stock CM7 settings.
I know I can just rerun the script after it's done booting, but I never had to do this with other ROMs as it would integrate fine in /etc/init.d and run.
I see in the /etc/init.d a S99SuperCharger script with the correct permissions set. I can run it via sh and it sets the properties correctly.
It just seems that CM7 is overwriting the low memory settings somewhere and I don't know where. I don't see it occurring in any of the supplied scripts from CM7 in the /etc/init.d and I don't see it in the build.prop file.
Any ideas? I know I could just tell Script Manager to run the script on boot, but that's usually not recommended except as a last resort.
I guess the real reason I would like to get this working the way it normally does (via the init.d scripts) is just to understand what CM7 is really doing.
Thanks!
Click to expand...
Click to collapse
Hehehehe... Me thinks you should search the forums a little bit. When I was testing cm7 for DZK, I tried EVERYTHING I used on previous ROMs, to include V6_SuperCharger. V6_SuperCharger DOES NOT WORK with CM7! The BIGGEST reason is the mapping for the memory slots are different with CM7, so fudging with them tends to cause massive issues and slowdowns. The reason it does not stick is most likely (speculation here) due to CM7 settings things back to it's optimized default settings.
Keep in mind that CM7 is an "optimized" AOSP based ROM... That means NO BLOATWARE! I am running with roughly 315 apps, most of which I use on a WEEKLY basis. Some, only monthly.
There are a few issues that I have noticed, root/su issues, sometimes system crashes on boot, sometime bluetooth crashes on boot, sometimes the dialer crashes... But with non-root apps, this thing SCREAMS!
Also, CM7 incorporates it's own memory management system that works better than the Moto Blur based ROMs. Just my two cents.
Ciao!
Moonshadow, thanks for the explanation. I did do a search and for some reason, your post didn't come up. Now that I search, I find it. I'll attribute it to an ID-10T or PEBKAC error.
iBolski said:
I'll attribute it to an ID-10T or PEBKAC error.
Click to expand...
Click to collapse
Are you REALLY sure about that??? It could be that Google just hiccuped during that nanosecond that your search on XDA was running... And didn't affect anyone elses searches...
You can be like Apple and blame/sue everyone else... (Just joking!)
Ciao!
Besides cm 7 does not need any script runs good as it is.
I know there are a couple posts out there on how to fix this, but this is one of the most legitimate ways to fix the multitasking issue we have all come to know and hate on Android devices running Sense. If you don't want to install a whole new ROM, such as MEANROM, you don't have to! This is a small guide to using the V6 SuperCharger script by Zeppelinrox. I know the amount of steps seems like a lot, but it's really not that many. Most of the steps will be followed by just reading what you see on the screen and accepting the recommended option!
Zeppelinrox said:
What's it do?
It makes your phone FAST... super snappy with better multitasking!
It rearranges and fixes the OOM Groupings and Priorites and lowmemorykiller values.
So basically, it's a COMPLETE MEMORY MANAGEMENT FIX!
It's the ONLY one of it's kind
NO LAUNCHER REDRAWS, faster than ever, multitasking is better... why?
Because it works with the lowmemorykiller and letting it work the way it's meant to work.
Also, because of the rearrangement, it works the same on all roms!
The problem with using minfree tweakers like AMM or AKMO is that it doesn't work the same on all roms.
Secondary apps may be in slot 3 on some roms but in slot 5 in others!
That's why you hear people comment "I tried AKMO but it didn't do anything..."
Most likely it didn't do anything because the apps weren't sitting where they were expected to be.
So fasten your seat belts and enjoy the ride!
Click to expand...
Click to collapse
So, everything you need to know or want to know can be found at Zep's original thread here. There is a lot of information, and because he is so technical, I think that sometimes his instructions can be hard to read for some, so I thought I would put together a VERY SIMPLE GUIDE to give you guys a hand. You can find the best instructions from him under Installing/Using.
http://forum.xda-developers.com/showthread.php?t=991276
On to the instructions...
How To Use Supercharger
Please only proceed if you are rooted and have busybox
Download script manager from the market: https://play.google.com/store/apps/details?id=os.tools.scriptmanager&hl=en
Download zep's latest V6 Script (V6_SuperCharger_for_Android-Update9_RC11_Test_6.sh.pdf): http://forum.xda-developers.com/showpost.php?p=18703418&postcount=5021
remove the .pdf extension (should now end in .sh) and place on your phone /sdcard (you can use rom tool box or estrongs to rename the file)
At this point, I highly recommend you make a nandroid through TWRP or CWM. The script has a built-in undo feature, which works well, but I still think we all know this is best.
Open up Script manager on your phone. Make sure to check 'Browse as Root' Option
Navigate to the location wher you placed the V6 .sh script
Click the Skull/Crossbones to run as root. This should turn green. NOTE: DON'T USE THE BOOT OPTION
Hit Run
At this point, get ready for an onslaught of text. Don't be afraid and try your best to read even though much of it may not make sense!
You may be asked about your launcher. Answer the question correctly for your setup.
Any time you are asked to press Enter, go ahead and proceed. This is the last time I will tell you to hit Enter for most occasions.
Pick your scrolling speed. I recommend slow or normal the first time you do this, so you can keep up.
On the kernel panic screen, I recommend choosing the Rock(H)ard Option, so hit H and then enter
Accept the Misc and 3G tweaks by hitting Y
Feel free to keep or disable the annoying animation (the scrolling V6 at the beginning of the script)
Hit Y(es) for SuperMinFree Calculator settings. This is an automatic calculation. You can change this later when you get more confident. Many will choose the 1000HP option for our phone (based on available memory)
It will now backup your build.prop and some other system files.
ICS and newer Android services store a lot of the memory tweaks in services.jar. This script will now take you through an ICS patcher. Accept the Automatic Transmission. This will upload services.jar, and download the patched one.
It will eventually tell you that it needs to wipe your caches and restart. You will definitely want to do this. You will need to wait 4-5 minutes while it rebuilds your Dalvik Cache
Almost done! After your phone boots up and stabilizes, go back into Script Manager. Navigate to /data/99Supercharger script. Check the SU (skull/crossbones) and check the boot option.
Zepelinrox said:
- Stock ROMs - It also creates /data/99SuperCharger.sh which you can load up on boot (run as root) with Script Manager. The OOM groupings work as well since it happens on boot in local.prop or build.prop (18 entries added)
Click to expand...
Click to collapse
Reboot your phone and now your phone will run the supercharger script on startup. If you ever want to verify that your script is working, or if you want to mess with any of the extra options (including removal), run the original V6 shell script you downloaded as root, just like we did at the beginning. This will tell you if you are 100% optimized and give you a whole menu of options to play with!
I can actually open multiple apps now and go back to the first one without it having to reload. Waze is the best example. If I ever switched out and then back, it always had to reload...not anymore! Again, this all seems like a lot, but it's really pretty easy once you give it a shot!
Let me know if anything is unclear so that I can adjust this OP to help others.
Make sure to give Zep a 5 Star Rating in his OP and also give him thanks, he is the man!
Reserved just in case.
ok i need to correct you on one of your steps...DO NOT SELECT THE BOOT OPTION FOR THE SCRIPT. IT COULD CAUSE YOUR PHONE TO BOOT LOOP. only select run as root. it even tells you that on the guide that zeppelinx put in his thread.
edit: sorry for caps but i wanted to point this out before someone made this mistake
bog3nator said:
ok i need to correct you on one of your steps...DO NOT SELECT THE BOOT OPTION FOR THE SCRIPT. IT COULD CAUSE YOUR PHONE TO BOOT LOOP. only select run as root. it even tells you that on the guide that zeppelinx put in his thread.
edit: sorry for caps but i wanted to point this out before someone made this mistake
Click to expand...
Click to collapse
You have to run /data/99Supercharger as root and give it boot option or it won't be applied at boot. But you are right, if you are worried, you could just run it as root the first few times. I personally always set this one to boot as well. If you had to, you could always adb in recovery, and remove /data/Supercharger if you are having problems.
*EDIT
This is mostly a concern for ROMS/Kernels that utilize /etc/init.d but I will add this caveat to the OP
adma84 said:
You have to run /data/99Supercharger as root and give it boot option or it won't be applied at boot. But you are right, if you are worried, you could just run it as root the first few times. I personally always set this one to boot as well. If you had to, you could always adb in recovery, and remove /data/Supercharger if you are having problems.
*EDIT
This is mostly a concern for ROMS/Kernels that utilize /etc/init.d but I will add this caveat to the OP
Click to expand...
Click to collapse
if the rom uses init.d then the script will install a service to the init folder and it will auto load when then phone is restarted, no need to try and force it to run. also if it is a stock rom (with the script manager program) you can set the 99supercharger to run after boot as a task.
bog3nator said:
if the rom uses init.d then the script will install a service to the init folder and it will auto load when then phone is restarted, no need to try and force it to run. also if it is a stock rom (with the script manager program) you can set the 99supercharger to run after boot as a task.
Click to expand...
Click to collapse
What you are saying is exactly the point I made in the OP. Is this unclear? You should only ever run 99Supercharger on boot, not the original V6Supercharge Script. And yes, this is geared mostly towards stock users, who do not have init.d support and therefore need SManager to run the boot script for them.
adma84 said:
What you are saying is exactly the point I made in the OP. Is this unclear? You should only ever run 99Supercharger on boot, not the original V6Supercharge Script. And yes, this is geared mostly towards stock users, who do not have init.d support and therefore need SManager to run the boot script for them.
Click to expand...
Click to collapse
i understand what you are saying but the boot symbol next to the run ass root symbol in the script should not be checked. if you need it to run at boot the script manager program can do that for you, by setting up a scheduler when you reboot. after boot it will run the script but not during
p.s. let me re-read what you put so i am just not looking stupid lol. i think i need a nap
edit: yea if you need it to run at boot do it through the script manager program and set it up to schedule it to load the script after your phone is already booted to avoid any potential boot loops (but dont check the boot logo at the top left hang corner of the actual script itself
bog3nator said:
i understand what you are saying but the boot symbol next to the run ass root symbol in the script should not be checked. if you need it to run at boot the script manager program can do that for you, by setting up a scheduler when you reboot. after boot it will run the script but not during
p.s. let me re-read what you put so i am just not looking stupid lol. i think i need a nap
edit: yea if you need it to run at boot do it through the script manager program and set it up to schedule it to load the script after your phone is already booted to avoid any potential boot loops (but dont check the boot logo at the top left hang corner of the actual script itself
Click to expand...
Click to collapse
Can you post the steps to describe how you personally do boot scripts with SManager?
After Android starts up, it will send a boot intent to all apps registered to receive such an intent. This is where SManager is allowed to execute any scripts you have marked with the boot option. This happens much later than a traditional /etc/init.d start script, but is no less effective. Please let me know how you mark scripts as bootable and I can add that recommendation as well. Thanks.
adma84 said:
Can you post the steps to describe how you personally do boot scripts with SManager?
After Android starts up, it will send a boot intent to all apps registered to receive such an intent. This is where SManager is allowed to execute any scripts you have marked with the boot option. This happens much later than a traditional /etc/init.d start script, but is no less effective. Please let me know how you mark scripts as bootable and I can add that recommendation as well. Thanks.
Click to expand...
Click to collapse
1. open script manager
2. click menu
3. click more
4. click advanced options
5. click scheduler
6. click add new task
7. click select file
8. navigate to 99supercarger file the script created and click on it
9.you can from there click on boot (inside the file you just clicked on)
10. click save
it will boot the script after the phone is done booting, to prevent the possibility of boot looping. you can also create an event to do an engine flush however often you want (i do one at midnight everyday)
This gets executed at the same time during system boot as the method I mentioned. Both are valid. Thanks for the feedback!
Sent from my Nexus 7 using xda app-developers app
adma84 said:
This gets executed at the same time during system boot as the method I mentioned. Both are valid. Thanks for the feedback!
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
i thought you were saying click the boot thing during install ....i am sorry haha i got really tired all of a sudden and stuff wass getting jumbled together...
v6 works awesome though i have been using it for about 1 year now on this phone and my old evo
Also, for anyone that gives this a shot, please post back with your results!
Not to be "that guy" buuuut the effects of v6 at least from my experience with this phone (again fresh frombcustoms preorder release) the day i got it i was rooted and installed v6 because ive used it on all my prior evos since i found it probably right around when zep released lol...anyways on this phone its a strictly placebo effect and actually created more lag and launcher reloads...i was running the 1000hp option and tried the i believe 750hp whatever the one down from 1000 is anyways both of them gave me same results and once i removed the script all was good in the hood as they say lol...but if its working for yall then maybe zep fixed some ish for this problem and i didnt know about it...well this epic runon sentence is finished sorry for the length and useless points
Sent from the depths of hell
yea i also used it on my og evo and i just put it on last night again on this one, tried the 750 option and 1000 option. today at school my memory got so low it locked my phone, that never happened with mean rom and the tweaks he puts in. undoing the supercharge now.
Sorry everyone.
Sent from my Nexus 7 using xda app-developers app
adma84 said:
Sorry everyone.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
no thanks man for helping out, i just think this phone doesnt do well with it, and that may be because of how HTC changed the multitasking settings themselves. it may conflict with v6
Theres something up with it because its def just this phone because nothing solves it at all
Sent from the depths of hell
wileout said:
Theres something up with it because its def just this phone because nothing solves it at all
Sent from the depths of hell
Click to expand...
Click to collapse
I wonder if it's hard coded into sense somewhere
Sent from my EVO using xda app-developers app
bog3nator said:
I wonder if it's hard coded into sense somewhere
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
Im thinking its sonething stupid like a character in the code is supposed to be one way and its mirrored the other way lol
Sent from the depths of hell
It's definitely helps with multitasking. I can keep apps open in the background much easier. Problem is that it chokes out the available ram for running apps, so it can make it feel sluggish. I think it's overtweaking the mem settings.