http://forum.xda-developers.com/showthread.php?t=991276&highlight=http://forum.xda-developers.com/+V6+SuperCharger!
http://forum.xda-developers.com/showthread.php?t=991276&highlight=[Script]+V6+SuperCharger!+HTK+%26amp%3B+BulletProof+Launchers!
I know quite a few roms that use this script.. That run awesome!!
I was hoping that more roms here would make use of it.
OmegaRED^ said:
http://forum.xda-developers.com/showthread.php?t=991276&highlight=http://forum.xda-developers.com/+V6+SuperCharger!
http://forum.xda-developers.com/showthread.php?t=991276&highlight=[Script]+V6+SuperCharger!+HTK+%26amp%3B+BulletProof+Launchers!
I know quite a few roms that use this script.. That run awesome!!
I was hoping that more roms here would make use of it.
Click to expand...
Click to collapse
I do use this script, and I can say that it is a success!
1.0.2 Using the MiniCM6 Nobodyatall!
One of the best roms in Big X10 xda land "Wolfbreaks" uses this.
I hope the roms here start using it... It rapes!
I must say.. this is works very well on my mini with MiniCM 2.0.5 GingerBread
Before: Active launcher and Zeam launcher is redraw everytime I finish to play NFS Shift or even after I open Application manager
After: No redraw (Active Launcher and Zeam) when finished playing Angry Birds, NFS Shift and other RAM eater games
Great ..
So I tried this script, and now my launcher is hard to kill / supercharged
but then after reboot it still says my launcher is hard to kill, but also that my prior minfrees don't match my current minfrees.
it then shows my curent minfrees as the default minfrees and the prior as what i selected. is that supposed to happen?
I mean exactly as the screenshot moedjs posted
like isn't it supposed to set current minfrees to what i selected, and not to default?
moedjs said:
I must say.. this is works very well on my mini with MiniCM 2.0.5 GingerBread
Before: Active launcher and Zeam launcher is redraw everytime I finish to play NFS Shift or even after I open Application manager
After: No redraw (Active Launcher and Zeam) when finished playing Angry Birds, NFS Shift and other RAM eater games
Great ..
Click to expand...
Click to collapse
Exactly.. makes multi tasking rock.. keeps the memory free, locks in the home app.
It works badass!
I did not understand the installation
ops , I did find a help, sorry
hey guys, does this works in SE android firmware 2.1?
Another question, in a tutorial it says :
P.S. When Installing Programs, MAKE SURE Script Manager are installed on PHONE and NOT in the MicroSD Card!
I have app2sd installed already , how can I do this? thanks
can someone who tried this give his values and his results?
sounds like a great tool
thnx in advance
I have the same problem as Carpe-Dimi above regarding new minfrees not sticking after reboot, although the Launcher is "Hard to kill".
I used option 6 in the script set up.
I followed help file advice to have Script Manager run /system/etc/init.d/99SuperCharger "at boot" and "as root" but problem persists.
Otherwise seems to work fine at keeping launcher in memory. I don't see any boost in Quadrant Score... or any other noticeable improvements to be honest.
MiniCM 7 is pretty good as it is
Any advice on settings or getting minfrees to stick?
Anyone know if it works on mini pro?
That number 1-17 is best for my phone?
alanllew said:
I have the same problem as Carpe-Dimi above regarding new minfrees not sticking after reboot, although the Launcher is "Hard to kill".
I used option 6 in the script set up.
I followed help file advice to have Script Manager run /system/etc/init.d/99SuperCharger "at boot" and "as root" but problem persists.
Otherwise seems to work fine at keeping launcher in memory. I don't see any boost in Quadrant Score... or any other noticeable improvements to be honest.
MiniCM 7 is pretty good as it is
Any advice on settings or getting minfrees to stick?
Click to expand...
Click to collapse
there are config files in the ramdisk.tar (can't remember name atm, but they are init.rc files) that have lines regarding the setting of ram optimizations.
however. these are definatley meant to do the same as the script, but the values in them don't correspond to the ones the script readsout, so I'm thinking another script runs on top of that which overrides those values again.
that's just a theory tho, since I can't edit the ramdisk file as I dunno how to set the permissions back when unpacking and repacking ramdisk.tar but I'll get back when I find out.
as for the launcher being bulletproof, that definately makes the home button respond a lot faster ^^
Carpe-Dimi said:
there are config files in the ramdisk.tar (can't remember name atm, but they are init.rc files) that have lines regarding the setting of ram optimizations.
however. these are definatley meant to do the same as the script, but the values in them don't correspond to the ones the script readsout, so I'm thinking another script runs on top of that which overrides those values again.
that's just a theory tho, since I can't edit the ramdisk file as I dunno how to set the permissions back when unpacking and repacking ramdisk.tar but I'll get back when I find out.
as for the launcher being bulletproof, that definately makes the home button respond a lot faster ^^
Click to expand...
Click to collapse
Somewhere in the original post it says that in some Custom Roms the minfrees won't stay after reboot so you HAVE TO select 'run at boot' for it to stay.
edit: From original post:
Note: For some reason, the minfree levels do not stick on some Custom ROMs. I don't know why this is. Maybe a bug in GingerBread?
........ You can check /res/user.log to see if it ran...
........ If this happens to you, use Script Manager to load /system/etc/init.d/99SuperCharger "on boot" and "run as root"
And I also have a question(just like the one 2 above)
What is the best one to choose (1-17)?
ThankYou
I tried:
'........ If this happens to you, use Script Manager to load /system/etc/init.d/99SuperCharger "on boot" and "run as root"'
and still could not get values to stick
Has anyone else tried this and had more luck?
how do you install this.. i could not understand
Carpe-Dimi said:
there are config files in the ramdisk.tar (can't remember name atm, but they are init.rc files) that have lines regarding the setting of ram optimizations.
however. these are definatley meant to do the same as the script, but the values in them don't correspond to the ones the script readsout, so I'm thinking another script runs on top of that which overrides those values again.
Click to expand...
Click to collapse
u r correct...the memory free settings are modified by some file not located in ram disk...i have examined the init.rc files and ramdisk settings are quiet different form the one that is set in the roms during runtime
now only if v knew what that file was!!!
The values are not equal with me, but I noticed a big improvement!
I am using the following values in the original 6,8,16,20,22,60 MiniCM6 Froyo!
It must have some kind of file it impossible values are equal, but it works it works!
I have done for mine and is awesome...
DareDan said:
I have done for mine and is awesome...
Click to expand...
Click to collapse
which values did you use?
please delete this post sorry
Related
Hi,
I think in making this thread to discuss what is the optimal configuration for our beloved x10 minis/pros/x8
Best configuration, in my opinion, is when you can use the phone with maximum free memory(so, no lag), the maximun batery duration(so, no overclock and yes undervolt).
These options are completly harm free, if you dont like them you may just undo and be happy, no system files are harmed.
THESE WORKS ALSO WITH X8 and X10 mini pro. These three is the very same phone specs with diferente body shape.
The
Here is goes my configurations:
Cyanogenmod menu/ Performance.
CPU Configuration:
Governor Interactive X(it scales a lot the processor power, keepin it as mutch as possible in low frequencies without performance loss)
Undervolt Ticked
set on boot Ticked
Jit Ticked
allow purging of assets Ticked
Spare Parts program
Windows Animations FAST
Transition Animations FAST
Font Size EXTREMILY LARGE(im a bit blind, )
Programs That eat resources continuously
The is some of them bundled in rom.
I delete all, prefering programs that dont restart itself and eat the few phone resources.
Deleted:
DSP Manager
Gmail
Google Maps
Latitude
FOTA KILL (gOOGLE OVER THE AIR UPDATES)
Pico TTS (text to speech program/interface - if ypu arent blind u dont need it)
Voice Dial
Voice Search
Update:
Supercharger v8 Memory optimize script.
1 Download SCRIPT MANAGER FROM MARKET
2 Go to this thread and download SuPERCHARGER SCRIPT
3 Open program, load the script, Tick option run as ROOT.
4 in program dialog, type "1(fast)" and "enter"
5 In main Dialog, type "2" agressive one" and "enter"
6 Hit back button, click in run in background.
7DONE
Now i get a very Stable phone, fast as hell, with regulary 59mb free ram resources, no lag, batery lasting 1 day of heavy use and one day and a half of mediun use. BENCHMARK with ATUTU: 1608. As it should be.
link added to my FAQ, thx for this
any tests are welcome
what are these? Alow Resource Free Ticked, Set up in iniciation ticked ? i can't seem to find them.
Great tweak bdw
emmanuelcassar said:
what are these? Alow Resource Free Ticked, Set up in iniciation ticked ? i can't seem to find them.
Great tweak bdw
Click to expand...
Click to collapse
--> allow purging of assets
--> set on boot
pedrocel85 said:
Update:
Supercharger v8 Memory optimize script.
1 Download SCRIPT MANAGER FROM MARKET
2 Go to this thread and download SuPERCHARGER SCRIPT
3 Open program, load the script, Tick option set on boot. there's a problem here, in the original thread it is written run as root but DO NOT run this script at boot!!!
4 in program dialog, type "1(fast)" and "enter"
5 In main Dialog, type "2" agressive one" and "enter"
6 Hit back button, click in run in background.
7DONE
Click to expand...
Click to collapse
trying now... tests results tomorrow
please man, correct that and it will be fine
matmutant said:
trying now... tests results tomorrow
please man, correct that and it will be fine
Click to expand...
Click to collapse
I can not change the version of busybox!
Every time I make the change, it always returns the old value!
Is there a secret to it, or is it impossible?
Gustavo RD78 said:
I can not change the version of busybox!
Every time I make the change, it always returns the old value!
Is there a secret to it, or is it impossible?
Click to expand...
Click to collapse
I just did not try
everything worked ^^
matmutant said:
I just did not try
everything worked ^^
Click to expand...
Click to collapse
Sorry but my English is very bad! : s
Let's get this straight ...
... you also failed to change the busybox?
The description says the supercharger need busybox 1.18.2 or lower, because there may be errors, which are not errors.
I'll try to run the script with the version you have (1.19.1-static CM71)
Gustavo RD78 said:
Sorry but my English is very bad! : s
Let's get this straight ...
... you also failed to change the busybox?
The description says the supercharger need busybox 1.18.2 or lower, because there may be errors, which are not errors.
I'll try to run the script with the version you have (1.19.1-static CM71)
Click to expand...
Click to collapse
i'm using embedded busybox of CM7 2.1.1 by nAa and his kernel
(don't know which one but i don't care since it worked without any problem ^^)
matmutant said:
i'm using embedded busybox of CM7 2.1.1 by nAa and his kernel
(don't know which one but i don't care since it worked without any problem ^^)
Click to expand...
Click to collapse
worked! ! Thank's
Sent from my X10mini using Tapatalk
pedrocel85 said:
Update:
Supercharger v8 Memory optimize script.
1 Download SCRIPT MANAGER FROM MARKET
2 Go to this thread and download SuPERCHARGER SCRIPT
3 Open program, load the script, Tick option run as ROOT.
4 in program dialog, type "1(fast)" and "enter"
5 In main Dialog, type "2" agressive one" and "enter"
6 Hit back button, click in run in background.
7DONE
Click to expand...
Click to collapse
now your tut is great
something i do in a different way you did :
1 Download SCRIPT MANAGER FROM MARKET
2 Go to this thread and download SuPERCHARGER SCRIPT
3 Open program, load the script, Tick option run as ROOT.
4 in program dialog, type "1(fast)" and "enter"
5 In main Dialog, type "2" agressive one" and "enter"
6 type 17 (exit) and then "enter" -->at the top you see: running becoming exit code0
7 press "close" (it was "kill" while the script was running)
8 reboot
9 now your phone uses supercharger, you don't need to run it again
if you want to undo this :
1 run the cript
2 choose 1 (fast)
3 choose 14 (UnSuperCharger)
5 wait
6 type 17 (exit) and then "enter" -->at the top you see: running becoming exit code0
7 press "close" (it was "kill" while the script was running)
8 reboot
9 now your phone uses no more supercharger.
i don't know if it is a better way, but it's mine
[email protected]
the supercharge stick after reboot or did u use 98kernel?
ChavitoArg said:
the supercharge stick after reboot or did u use 98kernel?
Click to expand...
Click to collapse
It sticks after reboot. It will only go away if you undo or instal new rom.
ChavitoArg said:
the supercharge stick after reboot or did u use 98kernel?
Click to expand...
Click to collapse
here is the answer
matmutant said:
9 now your phone uses supercharger, you don't need to run it again
if you want to undo :
1 run the cript
2 choose 1 (fast)
3 choose 14 (UnSuperCharger)
5 wait
6 type 17 (exit) and then "enter" -->at the top you see: running becoming exit code0
7 press "close" (it was "kill" while the script was running)
8 reboot
9 now your phone uses no more supercharger.
Click to expand...
Click to collapse
maybe it wasn't so clear :S
matmutant said:
here is the answer
maybe it wasn't so clear :S
Click to expand...
Click to collapse
thanks for the sarcasm, lol. but before whit the old versions of MiniCM those values doesnt stick after the reboot-
ChavitoArg said:
thanks for the sarcasm, lol. but before whit the old versions of MiniCM those values doesnt stick after the reboot-
Click to expand...
Click to collapse
sorry
i didn't try with miniCM6 or with miniCM7 2.0.8 and before ^^
i didn't know that didn't stay after reboot
that wasn't really a sarcasm,
i know my english isn't so good, you could have not understood
ChavitoArg said:
thanks for the sarcasm, lol. but before whit the old versions of MiniCM those values doesnt stick after the reboot-
Click to expand...
Click to collapse
They do sticky.
Do a litle test over there.
Open script manager, aply agressive settings, wait, close program, reboot.
After a reboot, open program again.
You will see the OOM values you set will still be there.
best,
pedro
matmutant said:
sorry
i didn't try with miniCM6 or with miniCM7 2.0.8 and before ^^
i didn't know that didn't stay after reboot
that wasn't really a sarcasm,
i know my english isn't so good, you could have not understood
Click to expand...
Click to collapse
No problem men, i speak spanish btw
with te previous versions of MiniCM7 the values doesnt stick after reboot, you have to use 98kickasskernel script to make it work. Now works just running the V6 script, and the values stick
is it best to enable compache? what's the effect on the device?
emmanuelcassar said:
is it best to enable compache? what's the effect on the device?
Click to expand...
Click to collapse
compcache works only if you have nAa04 and miniCM7-2.1.2
it will increase RAM (virtually) but uses CPU to "zip-unzip" the data in the compcached RAM part
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
This is a compilation, some of my own thoughts combined with ideas from others scattered throughout this forum... I really can't credit anyone other than who has already been credited above because it's just standard ideas.
Please feel free to add legitimate tips and tweaks to this thread so everyone can have a better TP experience! If it's noteworthy and people say it's helpful, I will add it to this OP!
1. Download the proper GAPPS and GAPPS fix to get Calendar working (thanks Stroid01, I borrowed your links from the original install thread)
2. Download the Charging and SystemUI fix from Dalingrin
3. Download Chainfire3D and install the Beta EGL drivers. Why? They fixed a lot of visual glitches that came with the stock ones.
4. Download and install the latest Adobe Flash 11.1 from the Market to enable Flash video, otherwise it won't work right out of the gate.
5. Enable USB transfer: Settings -> Storage -> Advanced (the 3 little dots in the top right corner) -> USB computer connection, then check the box next to "Media Device (MTP)"
6. It was in my best interest to change the DPI of the LCD, it'll look much better and the icons won't be so huge, my favorite has been 132 (though others have reported 145 to be good as well): Edit the build.prop in Root Explorer (mount R/W first) and change the line "ro.sf.lcd_density = 160" to "ro.sf.lcd_density = 132"
7. Install the cracked Market to fix any issues with your new DPI settings (Thanks, marios96)
8. To run Gamelot games edit your build.prop (it's located in your /system directory) to say this (I changed mine to XOOM instead of DROIDX but the idea is the same, thanks ssconceptziew):
ro.product.model=DROIDX
manufacturer=motorola
I guess this could be moved to the Development forum, I just thought this would be appropriate here since it's not actually involving developing something, just tweaks.
thanks, guess i will try the chainfire thing
How did you install chainfire. Tells me my device isnt compatible. And where do i find the drivers. Thanks in advance
Tapatalkin in from my ICS equipped Touchpad
When I try to install an app in the market, it gets stuck at the downloading stage. Is there a way to fix this? I've tried doing a fresh wipe and install of CM9 but nothing has worked! Also, I'm having problems downloading the UI fix. The countdown keeps on repeating.
Thanks. Looks much better now.
On WinXP I could not get MTP to work until I disabled debugging. Once I did that it showed up on my computer as a media device.
http://rootzwiki.com/topic/15568-rel-market-fix-dpi-compatibility/
Also install the cracked market from above to fix any compability issues with the new DPI.
wizegui said:
When I try to install an app in the market, it gets stuck at the downloading stage. Is there a way to fix this? I've tried doing a fresh wipe and install of CM9 but nothing has worked! Also, I'm having problems downloading the UI fix. The countdown keeps on repeating.
Click to expand...
Click to collapse
I have the same problem. If I figure it out I'll post it here as well.
jok3sta said:
How did you install chainfire. Tells me my device isnt compatible. And where do i find the drivers. Thanks in advance
Tapatalkin in from my ICS equipped Touchpad
Click to expand...
Click to collapse
Find an APK online. I'm not telling you to go get warez and download the pro version, I'm saying go get a free version.
And Chainfire is a driver program. That's what it's for, installing new drivers
I already got the pro version . The free version dosnt have the driver
Tapatalkin it from my Epic 3g Touch
You can also mention changing the kernel so you can get voltage control.
Samsung Galaxy S Captivate ICS CM9, Glitch Kernel | HP TouchPad CM9
iamsamsamiam said:
You can also mention changing the kernel so you can get voltage control.
Samsung Galaxy S Captivate ICS CM9, Glitch Kernel | HP TouchPad CM9
Click to expand...
Click to collapse
Flashing the new kernel didn't give me any voltage control in SetCPU.
treehumper said:
Flashing the new kernel didn't give me any voltage control in SetCPU.
Click to expand...
Click to collapse
Yeah, there's no voltage control in SetCPU even though he states it in his change logs. It does work in System Tuner though.
Tried, and you're right. The different kernel is a bit more unstable at this point in time, however. I am using it, but it's not for those that don't mind more frequent reboots (what's funny is that this is also my primary work device.... lol).
I have a tweak.
To run Gameloft Games edit your build.prop to say this:
ro.product.model=DROIDX
manufacturer=motorola
ssconceptz said:
I have a tweak.
To run Gameloft Games edit your build.prop to say this:
ro.product.model=DROIDX
manufacturer=motorola
Click to expand...
Click to collapse
Doesn't work for me. I still cant play modern combat 3
Tapatalkin in from my ICS equipped Touchpad
Did you copy the build.prop to your internal, edit then replace and restart. You can't edit it in place.
Sent from my SPH-D710 using xda premium
ssconceptz said:
Did you copy the build.prop to your internal, edit then replace and restart. You can't edit it in place.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
I used root explorer to edit it.. changing it dis something because before I did I couldn't even download the game from the market. But now I can't download the data file
Tapatalkin it from my Epic 3g Touch
Use the method I described
Sent from my SPH-D710 using xda premium
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.