Related
These steps are intended for use on the stock Droid X2. I'm sure they will be close to the same on other phones, but if your phone is not a stock Droid X2, know that the steps may be different or you may get unfavorable results. Always backup anything you don't want to lose.
Before even considering this, READ ALL THE STEPS. Then READ IT AGAIN.
There are two tweaks recommended here: V6_Supercharger and SD Speed Increase.
Requirements for V6_Supercharger:
1. Rooted Phone (Gingerbreak 1.20)
2. Script Manager (free on Market)
3. BusyBox 1.18.2 or earlier
NOTE: I haven't confirmed the script works on 2.3.4... You may want to use the latest version of the script if you have 2.3.4
Installing/Using the script:
1. Install BusyBox. There are a number of ways to get this... it comes as part of Titanium Backup, for example. If you're not sure if you have it, or not, you can use BusyBox Installer (free on Market) to detect whether or not you have it and install it if you don't.
- Note: BusyBox Installer tells you which version you have installed on the main screen after it loads... it should be in a list that starts with "Your device is Rooted"
- Note: Make sure you don't install BusyBox 1.19 or anything newer than 1.18.2
2. Download the script. Save it in a place where you'll be able to find it.
3. Launch Script Manager and find the downloaded file (usually in /mnt/sdcard/download). Long-press no it and select rename, then delete the .txt from the end. You should have a file named "V6_SuperCharger_for_Android-update8.sh"... Press once on the script file to load it into Script Manager, check the 'Run as Root' box (DO NOT select "Run at Boot") and push "Run" to execute the script.
4. The script will run and ask for a speed. Touch anywhere on the screen to open your keyboard. Type 1 if this is your first time running the script, 0 if you're a fast reader or you are in a hurry. Next, it lists 17 options and gives an input prompt. Type 8 and push Enter. (This selects the called MegaRAM 1 preset, but feel free to try others, if you're so inclined)
5. Once script finishes, type 17 and push enter to end the script. Push the phone's Menu button and select 'exit' to return to the list of scripts.
6. Pushing the phone's Back button should bring you to a file browser. Push the '..' line (second from top) until the top line reads '/'.
7. Push the phone's Menu button, push 'More' and then 'Config'. Check the box 'Browse as root'. Push the phone's Back button to return to the file browser.
8. Browse to /data and select '99SuperCharger.sh' (This script was created by the first script and makes sure the settings from the first script are re-applied on boot)
9. Select both 'Run as root' and 'Run at boot'. Push 'Save' and then 'Run'. If it says "Exit code 0" at the top of the screen, the script ran successfully. Any other Exit codes should be reported.
10. Almost all the settings are now in place... but reboot your phone to get the last ones implemented.
11. After reboot, launch Script Manager and run V6_SuperCharger_for_Android-update8.sh (the first script). Select 0 at the first prompt, look for the current minfrees values... it should say "Launcher is HARD TO KILL!" and "Current minfrees = 6, 12, 40, 60, 80, 100". If the settings are correct, type 17 to exit and you are done. If not, re-read steps because you missed something.
Credit goes to Zeppelinrox, see this thread for more info on this script.
Requirements for SD Speed Increase:
1. Rooted Phone (Gingerbreak 1.20)
2. SD Speed Increase (free on Market)
Configuring SD Speed Increase:
1. Open the app and adjust the memory slider to 2048
2. Check 'Set on every reboot'
3. Push the red button
4. Reboot the phone
Advanced: 3G TurboCharge
- I'll post full step-by-step instructions soon, but for now, here are two more scripts from Zepplinrox that will boost 3G performance... (Forum Post) Run 3GTurboChargerInstaller.sh and 98KickAssKernelTweaksInstaller.sh once each (Hint: Don't forget to remove the .txt extension). The second script creates this boot script: /system/etc/init.d/98kickasskernel, so you will have use this thread to get init.d created (Side note: I haven't been able to get it to actually run the scripts that are placed in init.d... we're stuck with Script Manager for now). Run all scripts as root, obviously.
Questions, Comments & Corrections are welcome!
To Do:
Update SuperCharger to update7 (need to test it myself first)
Test and implement AutoStart script
Edit:
06/27/2011 - Removed ro.Home_app_adj tweak. It's handled by the SuperCharger script.
06/27/2011 - Updated SuperCharger script instructions to use v4 of the script.
07/14/2011 - Updated SuperCharger script instructions to use v5 of the script.
07/25/2011 - Added BusyBox requirement to the SuperCharger script.
07/25/2011 - Updated SuperCharger script instructions to use v8 of the script. Rewrote most steps for improved clarity.
08/19/2011 - Updated 3G and Kernel links.
Using it now... Cant see a major difference but I can tell some things are faster... and havent had any reason to kill any apps because the phone starts to get sluggish so IMO thats a major plus and a sign that it is working...
Oh yeah... use option 9! Megamemory device....
Sent from my DROID X2 using XDA App
alright so I did all the steps... but when i re-open it (step 10) it goes back to the original 1-3 menu. what did i do wrong?
falconfan101 said:
alright so I did all the steps... but when i re-open it (step 10) it goes back to the original 1-3 menu. what did i do wrong?
Click to expand...
Click to collapse
What does the script say those numbers mean?
The 1-3 settings are just setting the scroll speed of the text when the script runs. I personally like to set it to 1 (fastest) but it really doesn't matter. 3rd gives you a chance to read everything.
Works, like a charm, now if i wanted to get rid of it would it just be going back through the steps and undoing what i did?
slowz3r said:
Works, like a charm, now if i wanted to get rid of it would it just be going back through the steps and undoing what i did?
Click to expand...
Click to collapse
No, all you have to do is uninstall script manager and reboot. Deleting the scripts is optional.
Sent from my DROID X2 using XDA App
This script really made a big difference.
Great work, and there is no battery drain...
Sent from my DROID X2 using XDA Premium App
vvildcard said:
Before even considering this, READ ALL THE STEPS. Then READ IT AGAIN.
Requirements for V6_Supercharger:
1. Rooted Phone (Gingerbreak 1.20)
2. Script Manager (free on Market)
Installing/Using the script:
1. Download this ZIP and extract the script to your sdcard.
2. Load the V6_SuperCharger_for_Android-update4.sh script into Script Manager and check the 'Run as Root' box (DO NOT select "Run at Boot"). Push "Run" to execute the script.
3. The script will run and display a list of 16 options and a prompt. Touch anywhere on the screen to open your keyboard. Type 9 and push Enter. (This selects the option called MegaMemory Device)
4. Once script finishes, type 16 and push enter to end the script. Push the phone's Menu button and select 'exit' to return to the list of scripts.
5. Pushing the phone's Back button should bring you to a file browser. Push the '..' line (second from top) until the top line is '/'.
6. Push the phone's Menu button, push 'More' and then 'Config'. Check the box 'Browse as root'. Push the phone's Back button to return to the file browser.
7. Browse to /data and select '99SuperCharger.sh' (This script makes sure the other script runs on boot. Otherwise you would have to do steps 2-5 everytime you boot your phone)
8. Select both 'Run as root' and 'Run at boot'. Push 'Save' and then 'Run'. You will most likely see 2 errors at the end of the 99SuperCharger script... this is expected.
9. Reboot your phone, but you might already notice a significant difference in speed and zero redraws from your launcher.
10. After reboot, launch Script Manager and run the V6_SuperCharger_for_Android.sh script, but this time don't select any options just look at your current settings and make sure they are the same as the Step values you put in. Right under the list of options, it should say: 'NOTE: Current minfrees =' If they are correct, type 16 to exit and you are done. If not re-read steps because you missed something.
Credit goes to Zeppelinrox, see this thread for more info on this script.
These steps were posted a while ago on droidforums.net... you might run through the comments on that forum if you have any trouble and don't want to wait for a reply.
Click to expand...
Click to collapse
What are the values that it sets? I currently am running the V6 script and unless this is a newer version my option 9 is called "Gaming settings". At any rate I did option 10 and set values at 6,12,75,125,150,175. What does this set them to?
disregard my previous post. I ran it and found they are the same settings I have been using. Thanks for the updated script though.
is their a script dev thread where updated scripts are posted
THANK YOU!
I was about 10 mins away from calling VZW and telling them to take this back and send me my original X back... I wasn't able to get ANY Ver. of Pandora to play or even Slacker half the time. The complete phone would freeze ALL the time to the point I could not do anything unless I performed a Battery Pull to hard reset.
This fixed ALL my issues. I don't even have the 1-3 second wake delay I was experiencing before. So far so GREAT!! As I type I even realize that while Pandora is playing and the phone is charging it is not getting nearly as hot as it was before? I don't care why it's working better now, but I'm glad it is!
I can't wait until we can get a decent rom with these fixes already in place! I loved Liberty on my old X. I miss it!
A+++\
slowz3r said:
is their a script dev thread where updated scripts are posted
Click to expand...
Click to collapse
The end of the OP has the link.
This's pretty slick. While I haven't noticed huge gains in most areas, due to having cleaned and optimized my phone, the whole thing just seems to run with extra smoothness. Also, there's no more delay when waking the phone.
Sent from my DROID X2 using XDA App
I ran this script on my phone and couldn't be happier. Stock I'd get about 115mb ram free on ATK. After root and de-bloat I topped out at 170. After this script, 220+!!!
Sent from my DROID X2 using XDA App
This is a godsend!
Thanks for creating this thread and providing the most excellent script for memory mgmt. I've just installed it on my DX2 and boy, does it fly! I now see 130m+ memory free whereas before it would bounce between 50M-90M. Many thanks! I will run the remainder of this week and see if there are other impacts.
I do have one question, however, since I'm a newbie to all this: can I now remove the ATK application and disable the native Task Manager application with this script now in place? Or should I keep these as add'l failsafes?? Please advise and thanks for all the great info on this forum!
droid4ever said:
I do have one question, however, since I'm a newbie to all this: can I now remove the ATK application and disable the native Task Manager application with this script now in place? Or should I keep these as add'l failsafes?? Please advise and thanks for all the great info on this forum!
Click to expand...
Click to collapse
Try using Titanium Backup Pro to freeze these programs. I have both apps frozen, and my phone is fine
Sent from my rooted, supercharged Droid X² using XDA App
Does this increase benchmark scores at all? I know they don't mean anything but I think we can all agree, they're fun.
Also does this JUST manage memory or does it do other things as well?
Sent from my SCH-I500 using XDA Premium App
In my limited and completely amateur testing, there was no noticeable improvement in benchmarks... but I'm sure mileage will vary. You should seek out Zepplinrocks (the scripts writer) for a better answer.
I am sure this is a stupid question, but I'm a droid Newb. Is it nessicary to have the script manager app constantly running once you have already ran the script? Or is it good to go once I have exited it the last time? And after rooting, and running this script my weather widget keeps on saying i am in rockport il. And I'm not.... any suggestions?
When I click the Zip to download V6 on my phone it say "download unsuccessful"
And I have done these:
Requirements for V6_Supercharger:
1. Rooted Phone (Gingerbreak 1.20)
2. Script Manager (free on Market)
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've read through the threads in the dev section about running linux on our Atrix either off of the sd card or chroot but didn't get a clear picture of what is possible with this technique using our phones on the laptop dock.
I'm about to give this one a go where it walks you through installing Ubuntu on our phones.
how-to-install-ubuntu-on-android
Does it work well? Does the touchpad and keyboard work without issues? Do the usb ports function correctly? And finally, does it play nice with Webtop if you have Webtop installed and enabled?
Thanks in advance for any info.
Update: The install script for this method failed when ran. It appears it is looking for a specific kernel version. The error I received was "FATAL: Could not load /lib/modules/2.6.32.9/modules.dep: No such file or directory". When I looked in the /lib/modules directory on the phone I only found a 2.6.29-arm2 directory.
you can just use WebTopScripts and Webtop2SD.
You can see how it works on my video [Polish language on video only]
http://www.youtube.com/watch?v=MGfZe4jOdfo
ovitz said:
you can just use WebTopScripts and Webtop2SD.
You can see how it works on my video [Polish language on video only]
http://www.youtube.com/watch?v=MGfZe4jOdfo
Click to expand...
Click to collapse
I checked out your video and I wish I could understand Polish.
Anyway, I just installed webtop2sd and when I launch it I get a force close error popup saying...
"Sorry! The application webtop2sd (process net.toreishi.webtop2sd) has stopped unexpectedly. Please try again."
I'm running stock 4.5.141 build with root and unlocked bootloader. Any idea on why I'm getting this error?
I can translate this video if you want to
yes, you have to instal bussybox installer form Google Play Store, then you need to change permissions of busybox in/system/bin/
Open permissions and uncheck "Set GID" permission, save changes.
ovitz said:
I can translate this video if you want to
yes, you have to instal bussybox installer form Google Play Store, then you need to change permissions of busybox in/system/bin/
Open permissions and uncheck "Set GID" permission, save changes.
Click to expand...
Click to collapse
Thanks for reminding me about Busybox. I didn't bother to install it since when I updated my Superuser binary it said it was installing a custom Busybox so I thought that would be all I would need. I guess I was wrong and had to install Busybox anyway.
I'm running the WebTopScripts at the moment. It seems to be going well.
Thanks for your help.
help please
Ok first off let me say that I am very new to android so I am a noob. Lately I have received my Atrix 4G lapdock and I have been scouring over these forums attempting to install ubuntu or some other desktop linux distro on my device for the past week.
I have installed Webtop2sd 1.1.2 (I was getting force close with 2.0 version so I downgraded :/ ) I want to partition my sdcard but it is not being recognized by webtop2sd. I have changed permissions to uncheck set GID in busybox which is installed in systym\bin ...\xbin. Still no recognition.
I have attempted to ext3 partition my sdcard with Windows Mini Tool Partition Wizard but I get and error during processing and the partition cannot be created. Currently sdcard is fat32 format.
Can anyone please provide some assistance in this it would be most helpful!
Thank you!
Device stats:
unlocked BL, rooted, and ROM Nottachtrix 4G and faux 1.3 Ghz Kernal installed
Fixed!!!
For some reason the partition tool was acting up so I used another software which did the trick.
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.
I have tried following these directions to temporarily get the Advanced menu back for the CM10.2 nightlies so I can enable dock audio. I keep getting the following error:
Error type 3
Error: Activity class {com.cyanogenmod.device/com.cyanogenmod.device.DeviceSettings} does not exist
It seems to work on other VZW Note 2 Android 4.3 based roms, but I cannot get it to work on our nightlies.
Is there an additional file or entry missing somewhere?
Thank you for any assistance.
Hopper8 said:
Ok, for anyone who is missing the 'Device settings' or 'Advanced Settings' menu (since it was left out of CM10.2. See here for more details.) These settings include mDNIE screen settings and backlight control. I for one use them.
Anyway: To get these settings back, follow these steps.
1. Download attached apk (I took it from Rootbox 4.2.2, but it works just the same on 4.3).
2. Paste it into /system/app, set permissions to rw-r--r-- and reboot.
3. Enter terminal Emulator, and type:
Code:
su [enter]
am start -n com.cyanogenmod.settings.device/.DeviceSettings [enter]
(obviously don't type [enter], press the enter key....)
4. Device Settings will open up, set whatever you desire
Note: to re-open the app, you will have to do it throught Terminal Emulator again. There's no other way of launching it that I could find, even Titanium Backup doesn't recognise it as able to run.
Big thanks to Unisexist6969 and Markox89 for helping figure this out
Edit: most users of a launcher such as nova or similar should be able to add a homescreen shortcut using nova activities shortcut. Personally this doesn't work for me, I'm not sure why. The method above will work regardless of using a different launcher, or if someone (like myself) doesn't have the option to add a shortcut, or if they plain don't want a homescreen shortcut (also like myself).
Click to expand...
Click to collapse
mising said:
I have tried following these directions to temporarily get the Advanced menu back for the CM10.2 nightlies so I can enable dock audio. I keep getting the following error:
Error type 3
Error: Activity class {com.cyanogenmod.device/com.cyanogenmod.device.DeviceSettings} does not exist
It seems to work on other VZW Note 2 Android 4.3 based roms, but I cannot get it to work on our nightlies.
Is there an additional file or entry missing somewhere?
Thank you for any assistance.
Click to expand...
Click to collapse
I'm running the Eclipse ROM (which I believe is based off of CM 10.2), and I had this issue before I restarted the phone. After restarting, it fixed the problem. If this issue persists after restarting your phone, maybe someone else can chime in?
Sorry I couldn't be of more assistance.
SonOfUncleSam said:
I'm running the Eclipse ROM (which I believe is based off of CM 10.2), and I had this issue before I restarted the phone. After restarting, it fixed the problem. If this issue persists after restarting your phone, maybe someone else can chime in?
Sorry I couldn't be of more assistance.
Click to expand...
Click to collapse
Rebooting didn't help, I am back on a TW ROM for the moment since I use my dock everyday, but plan on trying Eclipse or PAC this weekend.
Sbrissen said he is going to put the option back in the settings once they figure out where they want to put it, so I just keep flashing the nightlies every few days to check.
Thank you for your input though.