How to set Permanent Background process limit ? - Sony Ericsson Xperia Neo, Pro

Hi guys,
just one question, search for it but didnt found a solution jet.
I set Under Settings -> Developer options -> Background process limit there is some options to choose. I´m unsig etc."At most, 3 processes". But, after rebooting the device, the option reset itself to "standard limit".
Is it possible to set any command as an startup file in the init folder, that after every restart it will be "4 processes" instead of "standart" ???
I hope to get some help, thanks !!!

Did you try SystemTuner Pro?
It have option to add int.d scripts at boot.Im using it and i'm almost sure that it have
and option to set and this you need or someting simmilar to that.

gencho81 said:
Did you try SystemTuner Pro?
It have option to add int.d scripts at boot.Im using it and i'm almost sure that it have
and option to set and this you need or someting simmilar to that.
Click to expand...
Click to collapse
I do not think it's on there, I need only script

gencho81 said:
Did you try SystemTuner Pro?
It have option to add int.d scripts at boot.Im using it and i'm almost sure that it have
and option to set and this you need or someting simmilar to that.
Click to expand...
Click to collapse
Hi! I'm loocking for this Script, but I don't find it.
Someone can Post it? Thanks in advance.

https://play.google.com/store/apps/details?id=ccc71.pmw

gencho81 said:
https://play.google.com/store/apps/details?id=ccc71.pmw
Click to expand...
Click to collapse
Thanks, but the App is understandable. Too much unnecessary settings for me.
I'm looking for a simple script to insert in init.d.
Inviato dal mio GT-I9000

Finally figured this out, man was it annoying.
I need it for my 2012 Nexus 7 running Android 5.1.1
It was running slower than molasseses until I changed the data partition to f2fs (make sure you have a kernel and ramdisk that support f2fs!) and enabled this tweak.
It can be done with root access with a single command.
service call activity 51 i32 x
Where x is the number of background processes you want.
If the API changes in the future, it's easy to look it up again.
http://grepcode.com/file/repository...4.4_r1/android/app/IActivityManager.java?av=f
Look for the line with SET_PROCESS_LIMIT_TRANSACTION
Then just extrapolate that info to http://grepcode.com/file/repository...ERSION/android/app/IActivityManager.java?av=f
Replacing DESIRED_ANDROID_VERSION with the version you're interested in.

Any solution you found?

I used to have this script,But now I do not have but him and I'm looking again, in case I remember him I'll share it here. I'm just here to warn you that it is possible and use the settings command, but I only remember that.

Related

V6+SuperCharger! script.

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

[Discussion]CM 7 - Optimal Configuration Thread - MINICM 7 - UPDATED 22/09/2011

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-TO]Make Live Wallpapers Smoother!

So I was searching around the Internet to find a way to make live wallpapers smoother. And I found a tutorial on another forum, tried it, and it worked like a charm, so I decided to post the tutorial on XDA Developers. Credits for this go to boimkun, a member of the Symbianize forum.
If you don't make to waste time on making the script, I have uploaded mine for you. Download the script
Requirements:
-Root access
-An application for making scripts (in this tutorial we are using GScript)
-Live wallpapers
Tutorial:
1. Open GScript
2. Click Menu, and then click "Add script"
3. Tick "Needs SU" if it's not ticked
4. Set the script name, and type in the text box below:
Code:
renice -15 `pgrep android.process.acore'
Note: "android.process.acore" stands for your launcher process name. You can use android.process.acore for ADW Launcher and Launcher Pro
5. Save the script and execute it
You must run the script on every boot.
Optional (I haven't tried this, but works very smooth without this as well):
boimkun said:
Maybe you want to try to renice the live wallpaper too (this may slow it down, I would not suggest to do it). To do this
- launch the terminal
- write 'ps' then press enter
- will appear a list of processes. here you should find one that has a name similar to the LWP you're using (for example, I'm using Pixel Zombies Infection and the process name is haydenTheAndroid.liveWallpaper.pixelZombies)
now you can renice it either from terminal or from GScript.
To renice from terminal:
- check the number *** which the process has in the PID row. You have to remember this number
- write 'su' then press enter. now you have root privileges
- write 'renice N ***' where N is the nice number you want (20=minimum priority ; -20=maximum priority, which you obviously don't want). You can set it to 20 to give the LWP the minimum priority
To renice from GScript go in the script you already created and add a similar line, by substituting "-15" with "20" and the process name with your LWP's process name.
You should now see an increased smoothness when scrolling homescreens and app drawer
Click to expand...
Click to collapse
That was all for this tutorial. Please post a comment, whether this script works for you or not.
It won't work alongside the loop smoothness tweak right?
Sent from my GT540
gonna try it out soon!!
yeah will this work along with the loopy and supercharger??
andreas__ said:
It won't work alongside the loop smoothness tweak right?
Sent from my GT540
Click to expand...
Click to collapse
I don't know about that, because I don't use that tweak. But you can try.
androidboss7 said:
gonna try it out soon!!
yeah will this work along with the loopy and supercharger??
Click to expand...
Click to collapse
It should, but I'm not sure. Try it, and you'll see.
despotovski01 said:
It should, but I'm not sure. Try it, and you'll see.
Click to expand...
Click to collapse
ok i will just for the fun of it!!
cause i dont really use live wallpapers!
i wanna try this utility it's easy to use??
Nirvanico said:
i wanna try this utility it's easy to use??
Click to expand...
Click to collapse
Yes, it's as easy as pie.
despotovski01 said:
Yes, it's as easy as pie.
Click to expand...
Click to collapse
hmmmm pie
just so u know. i put the command line in etc/init.d and give proper permission and the live wallpaper works really well.
though i only use multipicture live wallpaper but it loads automatically now after reboot and it scroll smoother.

[Q] Fix Permissions

I would like to think I am very familiar with GNU/Linux/UN*X permissions, but I don't have the foggiest idea as to what "fix permissions" does in Android recoveries and apps.
Is anyone willing to give an accurate overview of what's happening? If so, please do. Finally, can anyone point me towards some opensource code that implements such a task? That would be most appreciated.
Thanks in advance.
exiquio said:
I would like to think I am very familiar with GNU/Linux/UN*X permissions, but I don't have the foggiest idea as to what "fix permissions" does in Android recoveries and apps.
Is anyone willing to give an accurate overview of what's happening? If so, please do. Finally, can anyone point me towards some opensource code that implements such a task? That would be most appreciated.
Thanks in advance.
Click to expand...
Click to collapse
In order not to have applications to affect others, Android creates a new user/group to store data for each app and the permission information is keep in packages.xml. fix_permissions is to ensure permission integrity.
ROM Manager bundles fix_permissions shell script (I am sure others too):
/data/data/com.koushikdutta.rommanager/files/fix_permissions
Tingtan already explained the process of fix permissions and suggested ROM Manager as the shell commander but you can also fix permissions in CWM recovery by going to advanced/fix permissions/yes
Sent from my PC36100 using XDA App
hmmm, not realy clear for newbie like me, can you explain what problem will happen if fix permision ( in CMW ) is needed but i don't do it ?
When I flashed a rom, I always fix permissions at the end, then reboot.. That's how I learned to flash. :thumbup:
You can also fix permissions in rom toolbox under the "manage apps. " Its on bottom, just slide bottom bar to left and you will see it.
Codename FC18
taitrandht said:
hmmm, not realy clear for newbie like me, can you explain what problem will happen if fix permision ( in CMW ) is needed but i don't do it ?
Click to expand...
Click to collapse
http://wiki.cyanogenmod.com/wiki/Fix_permissions
Just found that. Sounds like what tingtan was saying.
Thanks I did not know that I could fix my permissions in Rom Tool Box.
Hello.
I suspect that fixing permissions implementation differs between tools. I suspect some of them doing worse to the system by performing this.
I'd appreciate a suggestion of tool doing this best (ie. no bad impact on system performance)
I just ran this from ROM Manager and thought... oh what have I done now...
I didn't really need to do it or anything. At least it didn't appear to have created issues
But, is it more or less secure now?
problem starting all aps after fix permission
just trying fix permission after flash rom and now my andriod cann't execute launcher and android system.
Nav bar and notification bar still show up, so the only thing i can use is setting menu.
Clear data on apps cann't do either due to, in active button (keep computing size all time)
Any idea how to fix this?
darkfader said:
I just ran this from ROM Manager and thought... oh what have I done now...
I didn't really need to do it or anything. At least it didn't appear to have created issues
But, is it more or less secure now?
Click to expand...
Click to collapse
More secure - tingtan answered that a couple of posts up now hit his thanks button
I am using Phil Touch recovery and for some reason I don't have the option "fix permissions" in the advanced section. Any theories for why?
mafra staue
H0LT3R said:
I am using Phil Touch recovery and for some reason I don't have the option "fix permissions" in the advanced section. Any theories for why?
Click to expand...
Click to collapse
its been removed with 5.10.0 version i think
wyklocnik said:
its been removed with 5.10.0 version i think
Click to expand...
Click to collapse
Guess it's a background process.
Stock Recovery Permission Fix?
How do you 'fix permissions' if you have only stock recovery?
I thought I needed to do this with my Titanium backup file.
I read that you must move the file into the system directory (off of SD Card or EXT SD Card) to do this, however this can be a problem and an inconvenience for such a large file, is there another recommended way of doing this if your Rooted but pure stock?
(Ideally this would alleviate the need to move the file, or at least would take care of the manual process if it's not possible to rectify in place.)
Fix permission?
Guys i have a note 3 sm n9005 and i am running cm12.1 ever since it came out. Well the rom is pretty good and stable but its missing some features on my device like the( on screen nav bar, ambient display , themer for cm themes) and im kinda frustrated cuz they are some nice features to be missing. Anyhow i tried liquidsmooth 4.1 and i did get the nav bar and the other settings, but now im back to cm cuz ls 4.1 has some bugs and again im without these features on cm12.1. Will this fix permissions thing solve the problem?? And if any one knows the fix for it please share it with me. Thanks.
I would like to invite you guys to test my new app Parasol which can solve the permission problem in Android M~
http://forum.xda-developers.com/android/apps-games/app-parasol-alpha-t3190615
Hi there,
Parasol is a new app to solve the permission problem in Android M. Here is the link: http://forum.xda-developers.com/android/apps-games/app-parasol-alpha-t3190615
Just try it and give me some expert feedback. Thanks a lot~
shell script to fix permissions
This is my first shell script but it fixed the permissions on an app that started crashing after I upgraded to android M
it takes the /data/data/XXX folder name as its only parameter
This script only repairs the owner:group of the data files
Please send comments - this script can be used by anyone in any way
Code:
#!/bin/sh
if [ "$1" != "" ]; then
#The folders in /data/data each have a different owner. The next line gets the owner and the strips the whitespace
appusername=$(stat -c "%U" /data/data/$1 | xargs)
#The next line constructs the chown command to repair the permissions for all the files in the target folder
fixperm="chown -R $appusername:$appusername /data/data/$1/*"
#Display the command to the user
echo "$fixperm"
#Uncomment the next line if you would like the script to fix the permission
#eval $fixperm
else
echo "Missing target folder parameter"
fi

Fix Multitasking and Reduce Lag

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.

Categories

Resources