Related
This article is about the Android Script.
For other uses, please search Placebo; Disambiguation
Op under construction,
Should become read-able soon.
Placebo 3.0 is here! Failed, 3.0.1 may work. lmao
View attachment Placebo3.0.1.zip
Placebo3.0.1-Dropbox
Placebo3.0.1-AmazonCloud
Now supports hotplug governor !
Now makes it's own tweak directory to cut down on overhead !
Now screenstate + CPU1_ON is working better than ever !
Now generates a list of kernel default settings for governors !
SHOULD now flash onto other phones without issue !
DOWNLOAD NOW AFTER READING MORE HERE
The setup I've been using lately uses two scripts; one script that has all of the tweaks and settings, and one small script for screenstate awareness.
Here are some details about installation and use.
1) Download the zip package you intend to install.
2) Boot into recovery with your preferred method. ( I personally just type "reboot recovery" into terminal. I hate holding the buttons...)
3) Navigate to the zip you downloaded and install it.
4) Assuming all went correctly, you will have the quickest flash you've seen, with the least "blahblahblah" possible.
This is normal.
TO VERIFY: Try switching gears. Open terminal emulator and type one of the following.
( you must first type "su" and hit enter )
ondemand
peqasus
conservative
interactive
smartass
lulzactive
If it installed correctly then this will effectively switch you to another governor with optimized settings.
Enjoy.
If this didn't switch you to a new governor, chances are there was a permission or mount failure on my part.
I will be posting additional tools to assist with this part, plus I'm getting a little better at preventing these issues.
To fix it yourself, try setting a governor after typing the following into terminal emulator. (these can be copy pasted if exact)
If it isn't working due to mount; the terminal emulator solution is
busybox mount -o remount,rw rootfs /
busybox mount -o remount,rw `busybox realpath /dev/block/platform/dw_mmc/by-name/FACTORYFS` /system
If if it was a permission related failure; the terminal emulator solution is
for i in ondemand conservative pegasus lulzactive interactive smartass;do
chmod 0755 /system/xbin/$i; done
If you have a problem that neither of these fix feel free to ask me or anyone else in this thread.
Latest scripts
Please read HERE before installing Beta3.1 (technically this NOT Placebo 3 )
PlaceboBeta3.1
Placebo(HEXEN)
(1-10-13 reposted with a couple minor issues fixed)
PegasusQ and dual cpu screenstate plus an SQL settings script
Here's a temp link to placebo2.0
http://db.tt/rsb7tAmY
Here's a sort of greatest hits type of link.
There isn't really any info on them ecxept buried in the thread but I tested to make sure they were all stable
http://db.tt/5KTUtews
A special thanks to:
Hakcenter:
This guy is extremely knowledgeable; willing to help improve others' understanding; has helped me on several occasions (although makes fun in the process ) despite my noobish questions, lack of attention span, and general stubbornness when I'm told I can't do something.... despite us meeting by me posting "Why is thread in the development section" in his apps thread LMAO (sorry, man...)..
For those of you who aren't familiar with Hakcenter, he has an application that applies tweak packages. I liked it when I gave it a lot. I changed some values... but that's not the point! TRY HIS APP. thanks...
Placebo Regulars; Dude, you guys... You guys are absolutely awesome. I honestly think that this is one of the most helpful (as in users helping other users) threads I've seen anywhere on XDA.
Zeppelinrox; His V6SuperCharger was my initial inspiration and his KickAssKernelizer was my initial template... way before Placebo was born.
Calkulin - Im sure I would know nothing if not for your easy to understand scripts having piqued my interest in the first place..
Thank you, sir.
(used nothing directly, but without his contributions....you get the picture..)
TDunham; Always friendly, always helpful, always has good and practical ideas.. never (publicly) judges me too harshly for my lack of ADHD medication...
Can't thank you enough for your kindness... but I can try.
Thank you, sir.
FreeCharlesManson; Your spit-balling and insight led me to a few realizations that altered the effectiveness of Placebo exponentially.
Thank you, sir.
Scarmon; also always helpful and friendly... and makes (at least one that I know of) badass roms that I would recommend to anybody (that I like..).
Thank you, sir.
BlackCanopy...
Two of the most willing-to-help people that I have the pleasure of knowing.. I can't thank you guys enough for keeping this place together.
MiguelHogue....
Team (all of them...) Seriously I still don't know why we aren't all on Teamusxdaguys.... Can't think of anybody in any crew that hasn't been helpful at one time or another.
A word for the wise.. Watch out for that Lickarock... sharp as a tack that one is.. as soon as he buckles down and puts to practice the knowledge slash resources that he already has..
I expect good things will come of it.
Problems?
I've got far more than 99 of em... IO aint one.
j/k
hit me up.... yue noe eye luuuhh yue.
Remember!
If you help one, you have helped us all.
+Good day, sirs+
+ENJOY Placebo+
Repos
..The Pharm..
Welcome. This is a repository with a few of the Placebo1 formats.
Be careful with them, I cannot guarantee them to be universal.
Obviously, of they say Univ then there have no reports of From specific issues. Similarly, if they say TW, don't bother trying on an AOSP build.
Here are some new items for your tool chests...
Format 12 & 7 and a persistent busybox
\\________//
Enjoy
Placebo-Black
Heres a little more info
http://forum.xda-developers.com/showthread.php?p=30348571
"This IS THE DROID you're looking for!!" Come to the black side...
Placebo Black was written on and for
BLACK ROM,
by Team Rejects!! AND Team Nocturnal!!
Works on every rom its been tested on, including JB builds.
PlaceboCmX-1
Placebo Pi. Nice and balanced build.
Nice and balanced. 8/09/12
Placeboπ
DietPill revision 1 (a big hit, simple, effective)
DietPillR1
DietWifiHERE
Placebo-FHV: 8/5 (balance)
http://db.tt/wFL0qtJy
So smooth.... that...
I should call it Santana or Thomas.. Eeer something
http://db.tt/XE2DWzst
Placebo set to Ondemand (performance)
PlaceboOnDmnd
Sugar Pill was an earlier one that was very well received. Stable, simple, gets work done, son!
Crazy Pill was around the same time as Sugar Pill. Can't remember much, except I think I was still adding transitions animations.
There's your warning.
View attachment dietpill-FHI.zip
View attachment SugarPill.zip
View attachment PlaceboFGXVII.zip
View attachment PlaceboFGXXII.zip
View attachment CrazyPill.zip
View attachment PlaceboFGXXVI.zip
View attachment PlaceboFGXX.zip
View attachment ServicesOptAOSKCMP9.zip
View attachment ServicesOptTouchWiz.zip
Check out my new JB compatible Odex Station
#
# RECOMMENDED: PHAKE_SETTINGS
#
dalvik.vm.heapstartsize=12m
dalvik.vm.heapgrowthlimit=96m
dalvik.vm.heapsize=192m
ril.hsxpa=2
ril.gprsclass=['dc 10 mul 4 sub 10';]
ril.hsdpa.category=['dc 8 mul 4 sub 8']
ril.hsupa.category=6\2
windowsmgr.max_events_per_sec=< >
debug.gr.swapinterval=0
RLIMIT_NICE 1
HOME_APP_ADJ -5
HOME_APP_MEM 5688
VISIBLE_APP_ADJ 1
VISIBLE_APP_MEM 11366
#
#
Thank you, you have clearly put allot of time into this... Im gonna check this out.
Sent from my SPH-D710 using xda premium
lolwut
Thank you ! 1st page.
What other scripts have you tested with this master piece?...Is it known to bump heads with any other scripts?
Sent from my SPH-D710
Placebo; Defined
A good reference for governors, definitions of their settings, extweaks, io schedulers, and a whole lot of other things.. can be found
Here, and thank OP of this thread if you like their info
Frequent Questions
My head hurts???
Click to expand...
Click to collapse
So, wait,... what does it do?
Click to expand...
Click to collapse
Here's a little info I prepared about the virtual memory aspect.. this is not complete.. and it's my half assed interpretation...
-------------------Virtual Memory------------------
dirty_background_ratio (threshold at which background data becomes 'dirtyable'
dirty_ratio (threshold at which data becomes 'dirtyable'
dirty_expire_centisecs (time, in hundredths of seconds, before dirty data expires
dirty_writeback_centisecs (time, in hundredths of seconds, before old data is allowed to be written by PDflush Daemons ( a value of ZERO disables flush, out of fear I haven't tried this.
drop_caches (self explained, but the values are | 1=PageCache; 2=InodeCache; 3=both
highmem_is_dirtyable (I don't fully understand this, but my take is it can prevent random/unnecessary I/O within known/mapped files
laptop_mode (determines the time, in seconds, between "disk" I/O and a flush of all dirty data
lowmem_reserve_ratio (ratio of total pages-to-free-pages for each memory zone
min_free_kbytes (this number is used to compute a pages_min value for each lowmem zone
How do I know which configuration is right for me???
Click to expand...
Click to collapse
- Well, that's the real point... you actually have to get your hands dirty here. No way around it.
Is it safe to flash this on ONEROM that is identical to ANOTHEROM?
Click to expand...
Click to collapse
Which one is the best one
Click to expand...
Click to collapse
Well,,, let's start from when you were 3. Go over in detail every decision you've ever made so I can graph what you will like best.
Have no idea how to use this but clearly you put in a lot of effort and it shows (look at the Quadrant! ). Thank you for your contribution and I believe this should go in the Development Section aswell
Lol i have no idea what im doing.. I unzipped it and put it in system bin folder n tried to run it in term emu and got log error so created a log in data log and it did something and log is full of garble but i know im doing it wrong. It was worth a try wish i had some instruction so i could get those scores! Mines under 3000
Sent from my SPH-D710 using XDA
Wish I could figure out how to use this lol, thanks for you hard work! :good:
Placebo:
It's hard to summarize Placebo quickly and in an easy to understand way.
Placebo is a script, or set of scripts, that changes Linux kernel settings in your Android.
It is hard to stay caught up, because the number of potential combinations is almost without limit,
and placebo is constantly changing as I learn/dabble with new/existing modifications.
Some will be for better battery (though all will probably help a little), some will be to make your phone
scream louder than Jenna J.
I would be more than willing to provide more technical information to anybody that requests it.
It's almost pointless to post specific values that are set, as no two Placebos make every adjustment the same,
but there are some constants, for example:
Every Placebo implements a sysctl.conf (or equiv.) which will adjust (at least some of) the following settings:
(The following is a brief breakdown of tunable virtual memory settings, as I understand them.
I do not claim to know a lot about Linux. If you notice something that I have misunderstood,
Please correct me. Flaming will not be responded to. Helpful knowledge will be appreciated.)
-------------------Virtual Memory------------------
dirty_background_ratio (threshold at which background data becomes 'dirtyable'
dirty_ratio (threshold at which data becomes 'dirtyable'
dirty_expire_centisecs (time, in hundredths of seconds, before dirty data expires
dirty_writeback_centisecs (time, in hundredths of seconds, before old data is allowed to be written by PDflush Daemons ( a value of ZERO disables flush, out of fear I haven't tried this.
drop_caches (self explained, but the values are | 1=PageCache; 2=InodeCache; 3=both
highmem_is_dirtyable (I don't fully understand this, but my take is it can prevent random/unnecessary I/O within known/mapped files
laptop_mode (determines the time, in seconds, between "disk" I/O and a flush of all dirty data
lowmem_reserve_ratio (ratio of total pages-to-free-pages for each memory zone
min_free_kbytes (this number is used to compute a pages_min value for each lowmem zone
PhAkEer said:
Honestly I dont see why you would have a problem trying a term.
Is your phone rooted? What commands did you attempt and what was the log output that it returned?
Curiosity; what Rom/kernel are you are using?
Click to expand...
Click to collapse
Not sure what to type lol and what to show you in the log but i am rooted on the universe rom with agats kernel.. I just typed in placebo. It has a ton of info in the log.. Also the universe does have kobridge tweaks which i see it in the logs lol
Sent from my SPH-D710 using XDA
Re: [TWEAK] placebo [$ETTINGS]
Just pm a copy of the log if yoy can... Im at work but will take a look.
Alright, I had hoped to wait until page 3..page 3 is always a safe place... Oh well....
This is a config Im currently working on. If it plays out well, its a big boost in a couple departments.
I cant very well get this thing universal with only one test phone...
Placebo: SugarPill
http://db.tt/in7LAmRN
This one almost effects the battery as much as a new ROM. It will probably take a short cycle before it balances itself out.
These settings are a little aggresive, but Im still taking it easy because I dont want anyone to break anything...
Come on guys, I thought we could all evolve this together =)
FREEBIE:
Ever gone into the supplicant scan's config file? Its pretty useful if you were to... say... Idk... Change the interface to uwbr0.
Your welcome.
(pictures unrelated to above tip)
Sent from my SPH-D710 using xda premium
Much better on the OP. Are you able to provide the download link to the file using the regular xda method (I added one below)? It is easier to see the link and it provides 2 very useful things: it has a built-in download counter (views) and you can remove or update it to new file(s) whenever you like.
Edit: Please put a brief note on the OP with what this script is known to work with (ROMs). And also do yourself a favor and put a disclaimer that you do not plan to support all the roms that are out at this time, try at your own risk stuff. That will save you a lot of headache there are so many different roms out there.
Is there a reason you're leaving /system writable?
Also, this seems to effectively replace kobridge's 41tweaks script, but doesn't address his ondemand scheduler, or build.prop or wifi sleep tweaks. Is that accurate? Can you see any potential conflicts if I kept those?
b1g.p0ppa said:
Is there a reason you're leaving /system writable?
Also, this seems to effectively replace kobridge's 41tweaks script, but doesn't address his ondemand scheduler, or build.prop or wifi sleep tweaks. Is that accurate? Can you see any potential conflicts if I kept those?
Click to expand...
Click to collapse
Actually it was by design to leave those alone, and since I have no scheduler in Placebo, no conflict there. (I smaaawt sah ntine) .
I didnt ask kobridge for permission to insert his work into placebo, so WifiSleepWait is left alone.
If you look for the "*tweaks" youll see what it is.. placebo will interact only with things having "tweak" in their name in its current config.
And about system, thats just a preference of mine. Feel free to add anything (including unmount) to it.
@ Tdun,
Forgive my XDA noobiness, but no actually, I dont know how to make that little tab. Lol
Thanks for all of your constructive criticism/advice. Its much appreciated.
(lol typos when noob=nofun)
Anyway this will work on GB?
Im on Calk's el29 and would love to see if this works on it.
PhAkEer said:
Actually it was by design to leave those alone, and since I have no scheduler in Placebo, no conflict there. (I smaaawt sah ntine) .
I didnt ask kobridge for permission to insert his work into placebo, so WifiSleepWait is left alone.
If you look for the "*tweaks" youll see what it is.. placebo will interact only with things having "tweak" in their name in its current config.
And about system, thats just a preference of mine. Feel free to add anything (including unmount) to it.
@ Tdun,
Forgive my XDA noobiness, but no actually, I dont know how to make that little tab. Lol
Thanks for all of your constructive criticism/advice. Its much appreciated.
(lol typos when noob=nofun)
Click to expand...
Click to collapse
Awesome! So awesome it inspired me to edit my sig. Here's how I'm incorporating your script into my rig:
Code:
echo "SugarPilling"
test -f /system/etc/init.d/41tweaks_kobridge && rm /system/etc/init.d/41tweaks_kobridge
cp /sdcard/gscript/SugarPill /system/etc/init.d/41SugarPill && chmod 755 /system/etc/init.d/41SugarPill
---------- Post added at 03:11 PM ---------- Previous post was at 03:10 PM ----------
apatcas said:
Anyway this will work on GB?
Im on Calk's el29 and would love to see if this works on it.
Click to expand...
Click to collapse
Sure it would. If nothing else, run it interactively and check the log. (I'm pretty sure) the tweaks get reset back to default when you reboot.
lol Im scatter-brained and trying to get out the door for work,
As for GB, I dont see why there would be any issues. I havent tried it, but these are the same things that were in scripts long before I was playing witb them so Id guess that its safe.
Sent from my SPH-D710 using xda premium
Is it possible to run this script from galaxy w? I have some ram issues and sometimes my phone lags.
In running services these applications are always open:
Facebook
hotmail
go launcher ex + go launcher notification + go locker
maps
swiftkey
I have read somewhere that this script is not very good with multitasking but it makes the phone run faster and smoother. These applications are considered in multitasking? Or in this case multitasking means for example to have messaging, browser etc running at the same time?
Thanks
Yes u can install v6 script in GW
Ur phone will be faster
But u should search the forum before posting
From My GWonder
Okay thank you!
Sent from my GT-I8150 using xda app-developers app
I've had some probless with supercharger, when closing apps with stock task manager, launcher would always close, and have to reload all the apps and widgets (stock touchwiz launcher). Can this be solved?
Sent from my bananaphone.
piefert said:
I've had some probless with supercharger, when closing apps with stock task manager, launcher would always close, and have to reload all the apps and widgets (stock touchwiz launcher). Can this be solved?
Sent from my bananaphone.
Click to expand...
Click to collapse
That is called "Launcher Redraw", technically, when you clear memory or run a resource-demanding apps, Launcher will be killed as well to give more memory.
To prevent this, set the "lock home in memory" option in V6Supercharger. Note that doing this will make your home launcher unkillable and thus your free memory will be lower.
My advice: If you do want to lock launcher in memory, use a low memory usage launcher, such as zeam, Go Launcher uses too much memory.
Hope this helps.
Reidzeibel
Sent from my Modded Stock DXLA2 (Didn't have the mood to update)
I installed Supercharger on my phone and now it works better altough some games runs slower and freezes on my device,
reidzeibel said:
That is called "Launcher Redraw", technically, when you clear memory or run a resource-demanding apps, Launcher will be killed as well to give more memory.
To prevent this, set the "lock home in memory" option in V6Supercharger. Note that doing this will make your home launcher unkillable and thus your free memory will be lower.
My advice: If you do want to lock launcher in memory, use a low memory usage launcher, such as zeam, Go Launcher uses too much memory.
Hope this helps.
Reidzeibel
Sent from my Modded Stock DXLA2 (Didn't have the mood to update)
Click to expand...
Click to collapse
Ehhh??
Lock home in memory is not in V6....actually, if it is enabled in Launcher or ROM, Zepp recommends not to do this!!!
From my memory, you got "Hard to Kill", "Die Hard" or "Bulletproof" depending on OOM and Minfree values you choose in the script....
Obviously, Bulletproof means Launcher will never be killed!!
But, the script expects that "lock home in memory" to be disabled, AFAIK.....if I am wrong, I apologise in advance!!!
BTW, if your not on ICS, can I recommend that old favorite Launcher Pro.....it may lack support from the Dev, but it runs silky smooth on GB and is lightweight with many options!!!
Sent either from my Sammy GT-i8150 or my Momo11 Bird Tablet!!
irishpancake said:
Ehhh??
Lock home in memory is not in V6....actually, if it is enabled in Launcher or ROM, Zepp recommends not to do this!!!
From my memory, you got "Hard to Kill", "Die Hard" or "Bulletproof" depending on OOM and Minfree values you choose in the script....
Obviously, Bulletproof means Launcher will never be killed!!
But, the script expects that "lock home in memory" to be disabled, AFAIK.....if I am wrong, I apologise in advance!!!
BTW, if your not on ICS, can I recommend that old favorite Launcher Pro.....it may lack support from the Dev, but it runs silky smooth on GB and is lightweight with many options!!!
Sent either from my Sammy GT-i8150 or my Momo11 Bird Tablet!!
Click to expand...
Click to collapse
Yes, Zepp advise not to enable the option IF you don't know what it is used for
Yes, If the launcher or ROM supports "Keep home in memory", do this instead of using supercharger script, I forgot to write this, thanks Irish for adding that part
Sent from my Modded Stock DXLA2 (Didn't have the mood to update)
reidzeibel said:
Yes, Zepp advise not to enable the option IF you don't know what it is used for
Yes, If the launcher or ROM supports "Keep home in memory", do this instead of using supercharger script, I forgot to write this, thanks Irish for adding that part
Sent from my Modded Stock DXLA2 (Didn't have the mood to update)
Click to expand...
Click to collapse
Well, I don't know friend.....
every tutorial I have seen or read including Zepp on the V6 Thread, says you should disable this setting if you have it, as it interferes with how V6 manages memory.....
and if you leave it enabled, it may cause lag on your device, the advice is to disable it, and Compcache [zRam]....If you don't have the option, it don't matter, so it's mainly aimed at CM7/9 ROMs.......
to achieve same result, V6 uses the Bullet Proof Launcher, but I think Zepp now advises to use the HTK option, as BPL breaks some other stuff in ICS.....
just to emphasise, it is important to read the outputs given in the script......
Zepp can be a hard taskmaster if you ask something covered there or in help files, etc.
Small example of his comments here:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
//EDIT2:
My original writing here was:
Forget the Supercharger. Instead take cear of the number of your apps and their intent-behavior.
Scripts like Supercharger are pure mess when targeting a solid daily driver system.
The number of people using this script is only high because there are a lot of folks with little knowledge about the underlying techniques.
Click to expand...
Click to collapse
These words might have been choosen to sharp for this given thread. See the further discussion for more details.
The essential core of my statement is to use the Supercharger with care, as you might run in more problems than before, if you do not know about your usage scenario and the side effects that come with every change in those parameters.
Tweaking settings like those of Supercharger is always a trade-off - but you can only adjust them if you know which flavor of system-behavior you prefer. Most users don't have a clue, so they have to believe magicians - Unlucky for them, because the provided magic potions are not more than nicely advertised placebo.
But at least, they got some great funky banners, so you can easily spread your unawareness in the whole xda forums via your signature through adding them.
// EDIT:
You can optimize memory management for either single task scenarios or multitasking scenarios. Logically, this is a classic trade-off.
To give an simplified example:
- Higher low-memory-killer-borders increase the chances of getting a smoother experience when running only one specific app most the time.
- On the other side, multitasking user experience will suffer, as activities get flushed out of memory earlier, when free memory decreases.
Other example: The VFS Cache Pressure parameter, which controls the weight between file system cache and application memory space.
- Lower values should give you better experience, wenn handling similar task scenarios most of the time, since their access patterns improve through caching
- On the other side, there is less memory space for applications, so this setup will give you slower task switching, as it is more likely now, that your desired new foreground application is not present in memory anymore.
XR-7 said:
Forget the Supercharger. Instead take cear of the number of your apps and their intent-behavior.
Scripts like Supercharger are pure mess when targeting a solid daily driver system.
The number of people using this script is only high because there are a lot of folks with little knowledge about the underlying techniques.
Tweaking settings like those of Supercharger is always a trade-off - but you can only adjust them if you know which flavor of system-behavior you prefer. Most users don't have a clue, so they have to believe magicians - Unlucky for them, because the provided magic potions are not more than nicely advertised placebo.
But at least, they got some great funky banners, so you can easily spread your unawareness in the whole xda forums via your signature through adding them.
// EDIT:
You can optimize memory management for either single task scenarios or multitasking scenarios. Logically, this is a classic trade-off.
To give an simplified example:
- Higher low-memory-killer-borders increase the chances of getting a smoother experience when running only one specific app most the time.
- On the other side, multitasking user experience will suffer, as activities get flushed out of memory earlier, when free memory decreases.
Other example: The VFS Cache Pressure parameter, which controls the weight between file system cache and application memory space.
- Lower values should give you better experience, wenn handling similar task scenarios most of the time, since their access patterns improve through caching
- On the other side, there is less memory space for applications, so this setup will give you slower task switching, as it is more likely now, that your desired new foreground application is not present in memory anymore.
Click to expand...
Click to collapse
Sounds like you've been reading my thread.
Thanks for confirming everything I've said LOL
Fact is, nobody can preach about android memory management and be right without confirming my findings.
So you're right.
And you confirm my findings.
Thanks and you're welcome.
PS. People know they hate launcher redraws and know they like it fixed.
But then again, you haven't read the thread or tried supercharger otherwise you'd know that it has different flavours for multitasking, aggressiveness and balanced.
And it's popular because it's for those that do know, and those that don't - not to mention that it works and does what it says.
If anybody thinks it's a placebo, it's in their head.
And you're wrong when you say "scripts like SuperCharger" because there is no such thing as a script like SuperCharger... silly.
edit: oh about VFS cache pressure, you can check that and all the other placebos in the Kick Ass Kernelizer script.
You fail to mention the importance of min_free_kbytes and dirty ratios and lease-break-time in your attempt to sound knowledgeable.
I guess you were too busy enjoying hearing yourself talk.
Man...
I woz goin to write that....but you just did it for me....
from the horses mouth, so to say!!!
Thanx....
hope you didn't mind the pic.....captures the essence of Zepp
EDIT....of course in XR's OP the EDIT bit was missing, so of course be had a quick look at the V6 thread....went Ohh Ohhhh!!!!
Code:
Edit:
I withdraw offending remarks about XR.....
as I have no knowledge as to his level of knowledge....
and in all humility I know phuck all myself....
OK??
Peace
Sent either from my Sammy GT-i8150 or my Momo11 Bird Tablet!!
irishpancake said:
Duplicate post!!! Sorry
Sent either from my Sammy GT-i8150 or my Momo11 Bird Tablet!!
Click to expand...
Click to collapse
irishpancake said:
Man...
EDIT....of course in XR's OP the EDIT bit was missing, so of course be had a quick look at the V6 thread....went Ohh Ohhhh!!!!
Click to expand...
Click to collapse
Sounds logic. I see that a am completely wrong at the V6-thread, so i go back, place a big EDIT-Label under my text, and add more text, so that every one can cen see it? Not.
Seriously, the examples i gave are there to line up the claim i did in the first part: V6 SuperCharger is no the glory fire-and-forget solution, most of those performance-increases come with some kind of accordant disadvantage. This should be mentioned.
irishpancake said:
Man...
but he is so "knowledgeable" or some kinda know-it-all know-nuttin
Click to expand...
Click to collapse
For some kind of stuff, one does not need >500 posts, but a solid technical comprehension, common sense and some research on the web.
---------- Post added at 03:47 PM ---------- Previous post was at 03:36 PM ----------
@zeppelinrox
What i wanted to express is: Those settings are trade-offs concerning the user experience. This stands in contrast to your explanations, which claim to bring both speed and multitasking to every phone. Forcing the home launcher to stay in memory is a good idea, but it was a one-liner until ICS came, so this can't be the reason for running hundreds LOCs at system startup.
The majority of users has a bunch of other problems, with their device configuration messed up, too much resource-intensive apps installed or a bad-performing ROM installed at some time.
And then there comes this shiny tool, it sounds like the good old american way of life (and is named like it): giving resources here, spending some more memory here - there's no limit, it makes your device blazing fast, it gives you all the things you dreamed of, on your old sluggish device.
Naturally, thats not the case: Yes, there might be useful scenarios, as it allows switching beetween LMK-profiles etc. But lets be honest: Normal users have no clue what they are doing there, playing around and getting more problems than before.
Actually, i like your idea of making those parameters accessible with more ease. As a advanced user, you can archive performance gains, because you know what to set for your specific usage scenario.
Its simply not the fire-and-forget-speedup for android, but people tend to believe this.
// Update:
I added a more diplomatic statement to my original post. Although my technical base argumenttion is the same as before, i guess its good for the discussion if there are less misleading emitotional expressions.
Just read post 3 in my thread.
It was never a one-liner. (well bulletproof launcher used to be at first)
Lock Home in Memory was a one-liner and it wasn't good enough.
All 3 launcher strengths are stronger than "lock home in memory" and there are 3 strengths precisely because there are trade offs...
Reading the script output would explain it anyway but suffice to say, you have said nothing that contradicts anything that I've said.
And very few users have problems with it and has a very good reputation.
Otherwise, this wouldn't happen:
http://goo.gl/qM6yR+
http://goo.gl/1JPl8+
Of course, that is only counting clicks on the goo.gl links... not all clicks.
But you get the idea: the sky's the limit.
And yep... it's like getting a brand new phone.
I've listened to you talk in circles so here's some advice: know what you're talking about before talking about it.
XR-7 said:
Sounds logic. I see that a am completely wrong at the V6-thread, so i go back, place a big EDIT-Label under my text, and add more text, so that every one can cen see it? Not.
Seriously, the examples i gave are there to line up the claim i did in the first part: V6 SuperCharger is no the glory fire-and-forget solution, most of those performance-increases come with some kind of accordant disadvantage. This should be mentioned.
For some kind of stuff, one does not need >500 posts, but a solid technical comprehension, common sense and some research on the web.
---------- Post added at 03:47 PM ---------- Previous post was at 03:36 PM ----------
@zeppelinrox
What i wanted to express is: Those settings are trade-offs concerning the user experience. This stands in contrast to your explanations, which claim to bring both speed and multitasking to every phone. Forcing the home launcher to stay in memory is a good idea, but it was a one-liner until ICS came, so this can't be the reason for running hundreds LOCs at system startup.
The majority of users has a bunch of other problems, with their device configuration messed up, too much resource-intensive apps installed or a bad-performing ROM installed at some time.
And then there comes this shiny tool, it sounds like the good old american way of life (and is named like it): giving resources here, spending some more memory here - there's no limit, it makes your device blazing fast, it gives you all the things you dreamed of, on your old sluggish device.
Naturally, thats not the case: Yes, there might be useful scenarios, as it allows switching beetween LMK-profiles etc. But lets be honest: Normal users have no clue what they are doing there, playing around and getting more problems than before.
Actually, i like your idea of making those parameters accessible with more ease. As a advanced user, you can archive performance gains, because you know what to set for your specific usage scenario.
Its simply not the fire-and-forget-speedup for android, but people tend to believe this.
// Update:
I added a more diplomatic statement to my original post. Although my technical base argumenttion is the same as before, i guess its good for the discussion if there are less misleading emitotional expressions.
Click to expand...
Click to collapse
OK man XR......I have removed my offensive comment about you, mainly becoz I don't know you and have no basis for the comment I made, and also becoz I think I cannot stand over it, so accept my apology please....
its not my usual form at all!!
You can check my posts!!
But, you were being provocative IMHO, and that is usually a good basis for discussion
OK!!
Sent either from my Sammy GT-i8150 or my Momo11 Bird Tablet!!
irishpancake said:
I have removed my offensive comment about you, mainly becoz I don't know you and have no basis for the comment I made, and also becoz I think I cannot stand over it, so accept my apology please....
its not my usual form at all!!
Click to expand...
Click to collapse
That's okay. As i mentioned above, i had also choosen sharp words, guess there might have been some more suitable writing style.
Nevertheless, i also guess that both sides - positive and negative - of the supercharger script should be discussed, as it is definitely note the magic silver bullet as it is sometimes perceived.
zeppelinrox said:
But you get the idea: the sky's the limit.
And yep... it's like getting a brand new phone.
Click to expand...
Click to collapse
Yes, it's remarkable. Not only one's device becomes at least a Galaxy Nexus, but it also increases display size, brigths up your teeth and pleasures your girlfriend.
You should get this for your girlfriend: https://play.google.com/store/apps/...GwsMSwxLDEsImF0dGljbGFiLkRyb2lkVmlicmF0b3IiXQ..
But if her device is SuperCharged, you're out of a job but mostly because you bore everybody to death.
i try v6 for a day, at night i realized that sms that i send in a day just keeping sending without being sent, i've tried to unsupercharged and reboot phone, but sms still sending, until i restore system to earlier setting than restart the phone, and check for the messages are sent
what is wrong with it?
what version of v6 that support stock rom?
is v6 increase free ram or is it does anything else? because i see no different on free ram that showed in ram booster
one more thing, when i run the script, i see text "it will not run on this rom, but you still can cook bla bla bla" is it normal?
Sent from my GT-I8150 using xda app-developers app
DISABLING CPU RENDERING
Credit goes to Leowaliet.
So what does this mod give to us?
What does this help us with?
•Speed √
•Smoothness √
•Sound √
•Less Battery Drain √
Works with any ROM
So, if you have Faux 11 kernel + this mod.
(In Algebraic Equation)
F+M=EpixNeshh
In technical terms, we are disabling CPU Rendering from the system so it force GPU to work on all Graphics.
So why not?
Would it hurt no?
Try it, YOU WONT REGRET IT :screwy:
*THIS WILL LET IMAGES IN XDA APPEAR*
*WILL NOT BREAK APPS*
First To Port MIUIv4 to T989
Isn't this already a toggle under Developer settings in ICS+ ROMs?
thehandi said:
Isn't this already a toggle under Developer settings in ICS+ ROMs?
Click to expand...
Click to collapse
This stops it for all ROMS. And doesn't brake some of the apps.
First To Port MIUIv4 to T989
Link won't work if you don't have an account on that site.
bobpantsspongesquare said:
Link won't work if you don't have an account on that site.
Click to expand...
Click to collapse
+1
here it is...havent tried it
alphadog32 said:
DISABLING CPU RENDERING
So what does this mod give to us?
What does this help us with?
•Speed √
•Smoothness √
•Sound √
So, if you have Faux 11 kernel + this mod.
(In Algebraic Equation)
F+M=EpixNeshh
In technical terms, we are disabling CPU Rendering from the system so it force GPU to work on all Graphics.
So why not?
Would it hurt no?
Try it, YOU WONT REGRET IT :screwy:
http://forums.androidcentral.com/at...uide-disable-cpu-rendering-vm670_eglpatch.zip
First To Port MIUIv4 to T989
Click to expand...
Click to collapse
This is already set by default in many custom ROMs but alsoeans you can't see pictures on apps like XDA
Sent from my SGH-T989 using xda premium
Try it, YOU WONT REGRET IT
Click to expand...
Click to collapse
Actually...I did regret it, as I can't see any pics in XDA and in
my Sopcast, the stream is very "choppy" and with worst
color quality. So......Sorry.
Even in custom Roms, the first thing I do is uncheck the "Force GPU..."
:crying:
This is not using the phone's Settings.
First To Port MIUIv4 to T989
alphadog32 said:
This is not using the phone's Settings.
First To Port MIUIv4 to T989
Click to expand...
Click to collapse
this mod is wrong!! dude! it will brake apps that need it to work, GPU only works wen need it, this mod desable 2D and 3D drawing
richardlibeau said:
you do not need this mod. just go to system/lib/egl and delete the first line android 0 0. this does the same thing as this mod. I did it on my phone and it works fine. No graphics problems . All hi tech games like asphalt,spiderman, avatar. cs portable, gta3 all play great. Videos do too. You can also add debug.composition.type=gpu to build prop and delete any other composition type that's in build prop to force gpu rendering for graphics
Click to expand...
Click to collapse
Thank you. Every one thinks it will break things. It is like saying I have a Land Rover with 4v4. Now, you're going up a hill and to run it up, you buy newer and better wheels. It still gets up, but slower. It would be a lot smarter to enable 4v4 so it can climb faster and more efficient. So GPU is supposed to run the Graphics Interface. Not the Processing Unit. Does it make sense? Of course not. Using GPU for its dedicated reason it is a way more reasonable thought. So why would you want it disabled?
First To Port MIUIv4 to T989
alphadog32 said:
Thank you. Every one thinks it will break things. It is like saying I have a Land Rover with 4v4. Now, you're going up a hill and to run it up, you buy newer and better wheels. It still gets up, but slower. It would be a lot smarter to enable 4v4 so it can climb faster and more efficient. So GPU is supposed to run the Graphics Interface. Not the Processing Unit. Does it make sense? Of course not. Using GPU for its dedicated reason it is a way more reasonable thought. So why would you want it disabled?
First To Port MIUIv4 to T989
Click to expand...
Click to collapse
The theory is all nice and logical, however, let me quote something:
Every one thinks it will break things.
Click to expand...
Click to collapse
I'm one of the "everyone" and I do not "think" it will break stuff, I know it does and I can reproduce it at a drop of my hat!
So why would you want it disabled?
Click to expand...
Click to collapse
Because of my above proof (proof for me)....that's why.
However, it's nice that people can have a choice. For others may work better.
:highfive:
Well it hasn't broken any apps for me.
First To Port MIUIv4 to T989
I'm not sure why everyone is jumping on the OP so hard.. he stated clearly in the second or third post that it Works without breaking anything .. I flashed it on my AOKP JB build with no problems and it didn't break anything like the option in development settings does... for example .. xda app loads pictures perfectly.
Maybe test it next time before flaming give it a test...
Sent from my SGH-T989 using xda app-developers app
All I know is the guy is trying to help the community and you guys all just bashed him.. I dont even think any of you even bothered to say thanks..
RushAOZ said:
Because you're probably not using any old apps that haven't been updated for ICS. Not jumping on the OP I'm simply stating this mod isn't needed because the GPU is already rendering everything. CPU will only render old apps so if you don't have any old apps then this mod is essentially useless. You're not forcing the GPU to do something it isn't already doing.
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
OK.. then riddle me this.. Using the option in development settings breaks my XDA and my FRF app, meaning they wont load pictures in the app.. However this mod has not caused this side effect..
RushAOZ said:
This mod isn't needed. The whole reason GPU rendering exists in ICS/JB is for apps that were written on GB. GB written apps didn't support GPU acceleration by default. With ICS and JB apps are written with GPU rendering on by default.
Basically these settings ONLY effect old apps that haven't been updated to ICS/GB. This is why disabling CPU rendering will break some apps as experienced by some of you above. GPU rendering is supposed.to force the GPU to render old apps and while it works most of the time there are apps that you can't force and you get errors and artifacts. So many misconceptions with this setting lol. Just leave it on. Problem solved.
Sent from my SGH-T989 using xda premium
---------- Post added at 10:46 PM ---------- Previous post was at 10:32 PM ----------
According to pocket now force gpu rendering is basically used to off load the graphical tasks given to the CPU in apps that aren't optimized for ICS. ICS has this option enabled by default when writing apps for it but with apps written on GB down to cupcake 1.6, gpu rendering when writing apps is off by default.
Basically, leave it on as its probably helping your CPU run older unoptimized apps more efficiently since it doesn't have to process the graphical UI for that app too.
http://pocketnow.com/2012/05/25/wha...-in-ice-cream-sandwich/?wpmp_switcher=desktop
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Its also pretty hilarious that you say this and are bending it to make your self correct..
YES newer applications that are based on the newer SDK have the ability to do this Nativity regardless of what you have checked or unchecked..
BUT it is not ONLY going to be beneficial for apps that are not.. it will force ALL rendering through your GPU and leaving the computation to the CPU giving your system an edge.. while be it a small one, but never the less an edge as far as CPU processing times and Graphics quality output ..
PJcastaldo said:
All I know is the guy is trying to help the community and you guys all just bashed him.. I dont even think any of you even bothered to say thanks..
OK.. then riddle me this.. Using the option in development settings breaks my XDA and my FRF app, meaning they wont load pictures in the app.. However this mod has not caused this side effect..
Its also pretty hilarious that you say this and are bending it to make your self correct..
YES newer applications that are based on the newer SDK have the ability to do this Nativity regardless of what you have checked or unchecked..
BUT it is not ONLY going to be beneficial for apps that are not.. it will force ALL rendering through your GPU and leaving the computation to the CPU giving your system an edge.. while be it a small one, but never the less an edge as far as CPU processing times and Graphics quality output ..
Click to expand...
Click to collapse
Thanks man. Felt it right in the heart.
First To Port MIUIv4 to T989
Ok enough arguing here, stay on topic and stop assuming that this or that will happen until you have tried the MOD. If you don't like or want to try it, stay out of the thread. Don't troll dev threads.
Noellenchris
XDA Forum MOD
alphadog32, thanks (I did hit the Thanks button), but one needs
more info in the OP, like, how to install it, does it work with default
kernel, or only with Faux, what Rom is compatible with....and so on.
Thanks for this.
:good:
I apologize I misread/ misunderstood what the OP was saying. Since the mod is actually configuring the egl libs, this WILL NOT break your pics as force gpu in setting will. Everybody thank the OP and move this thread forward
Sent from my SGH-T989 using xda premium
Flashed it a few hours ago, seems pretty solid so far. At least it certainly hasn't given me any problems with games or other apps. It's almost weird seeing pictures load on the XDA app btw, because it's been a long time since I've seen them work... lol. Running it on CM9.1.
I know, many people here want to have Android 4.x.x on their phones, but unfortunately, because of low-end processor as well as less RAM, these CM10/CM10.1 ROMs are laggy and slow. I am also one of them, but, after using these type of roms since 4 months, I have now got a perfect idea of using them. So, I am sharing the way I use these roms. Many people told that this also helps for CM7 users. So, now I have declared this thread as UNIVERSAL PERFORMANCE THREAD. This method can be used on - Stock | CM7/9/10/10.1.
NOTE : This thread is mainly from galaxy mini forums. But, I have posted it here also, so that Gio users also get its benefits.
NOTE : This method is same for PAC ROMS.. because they are based on CM. So, you can use this on PAC ROMs also.
♦ FINDING STABLE VERSION :
First of all, you will need to find a good stable version of any CM7\CM9\CM10\CM10.1 ROM. Find stable version by asking in general discussion thread of those particular ROM and then download that version. But, do not flash now.. Follow next step.
Note : For CM7 users - Official CM7 is best, but if you want you can try it on custom roms also. If you are using CM7 custom or stock based custom rom, then for scripts n tweaks to work, you must delete all the scripts from init.d so that scripts will not get overridden.
♦ SLIMMING THE ROM :
Slimming means making rom size less by removing unwanted and unnecessary applications from system/app. It reduces system memory use. Here is a chart of cm10.1 apps which are safe to remove - LINK
With reference to that chart you should remove following apps with adding alternatives to them.
Note: Left side apps are to be removed and right side apps are alternatives.
● LatinIME.apk - WP7 Keyboard App
● Browser.apk - Holo Web Browser
● CMFileManager.apk - Root Explorer File Manager
● Trebuchet.apk - Holo Launcher
NOTE: On CM7, default ADW is good, but you can also use Holo Launcher.
Other apps that can be removed without alternatives-
● CalendarProvider.apk - One of the big RAM consuming apps. This app start anytime, you do anything, so it will be a big save of memory removing this app. But, you will get problems with calendar sync..
● GoogleCalendarSyncAdapter.apk - Reomove this only if you do not sync calendar.
● Email.apk - If not in use.
● Gmail.apk - If not in use.
● Talk.apk - If not in use.
● GoogleBackupTransport.apk - It is used in google backups, remove on your own risk. (Not a risk, i always remove it.)
● ChromeBookmarkSyncAdapter - No use.
● HTMLViewer.apk - Never needed.
● UserDictionaryProvider.apk - It is useless without LatinIME.apk.
● VisualizationWallpapers.apk - Wallpapers app. Remove it always.
● CMWallpapers - Remove it always.
● VoiceDialer.apk - Do you really use it?
● LiveWallpapers.apk - Dont you care for your battery?
● QuickSearchBox.apk - If you dont use.
● PicoTTS.apk - Text to speech function.
NOTE: Alternative apps should always be installed in system/app only. For that, I recommend you to remove these apps drectly from rom's zip before flashing.
♦ USE OF SCRIPTS N TWEAKS :
Many people use hard scripts n many tweaks to get good performance. But, it is totally wrong.
Highly recommended to use Activo Speeder. It is the best script for performance. Dont use anyother thing with it- such as ram manager, seeder or anyother script.
(Note: If the above script doesnt work on your device then please find another good script and flash it.)
IT IS RECOMMENDED TO USE SUPERCHARGER ON ICS\JB :
After testing a lot, I found that SuperCharger is the best script which can be used with any ROM to get more performance and for perfect RAM Management. Here are some steps on how to use SuperCharger -
● Here is the original thread for SuperCharger script.
● Script can be downloaded from this download page.
● Download latest script as well as starter package if needed (Read Original Thread).
● Now, for 4.x.x ROMs, you do not need to do anything with services.jar. But, for below 4.x.x, services.jar needs to be patched to get SuperCharger Memory Management working.
● Now, copy script to SDcard and run it with Script Manager as root. For more detailed guide plz prefer the original supercharger thread.
● Now, you are running the script. You will find many options and info on screen. Read it all and choose what you want.
NEW DISCOVERY : SUPERCHARGER + CROSSBREEDER = ULTIMATE PERFORMANCE WITH MAX ENTROPY ! - by Dark Passenger
● LINK FOR THE POST.
Here are some tweaks-
In Build.prop -
●
Code:
ro.ril.disable.power.collapse=0
and change the value from 0 to 1. (Add the line with proper value if does not exist)
This one is for battery saving.
●
Code:
dalvik.vm.heapgrowthlimit=48m
If it already exists then just match the values.
This is a VM Heap management for RAM.
●
Code:
ro.ext4fs = 1
Improves EXT4 performance.
● IMP :
Add following lines below "# Other" in build.prop
Code:
ro.com.google.locationfeatures=0
ro.com.google.networklocation=0
(If exists, just change the values as above).
(Note: This one will remove location feature increasing performance freeing up more RAM. This frees up to 30mb of RAM)
And now remove NetworkLocation.apk from system/app as well as com.android.location.provider.jar from /system/framework.
For further build.prop tweaking, you can use this great guide -> Click Here. Thanks to Dark Passenger for some build.prop tweaks.
This much tweaking and scripting is enough. DONT USE TOO MUCH TWEAKS N SCRIPTS.
♦ BASIC APPS TO USE :
Your rom's performance also depends on the apps which you use. Always look for apps' memory usage and if the app consumes more ram then try to find an alternative app for it. Here are some basic apps which you should use (i always use them).
● Use Root Explorer as file manager, Holo Launcher as Launcher.
● Use Cache Cleaner App. It is must. Clean cache once a day.
● Use Root Cleaner App. A must have app. Do "Quick Cleaning" twice a day. It will regulate your performance.
You can also freeze the apps you are not using at that time, such as DSPManager (Unfreeze it only at the time of listening songs)
Freezing Google Apps will be a great way to reduce RAM consumption.
● Use this amazing app - Autostarts. This app controls the apps that start automatically in your phone. If you want settings which I use then PM me. I will tell you, how to use this app.
CLICK HERE FOR AUTOSTART APP SETTINGS
● ABOUT TASK KILLERS :
Using task killer is good but, it is also bad. Task killing is actually meaningless. Some apps never really get killed. They start again n again. So, use Autostarts instead task killers. But, here is a nice app for killing processes and freeing RAM. This is the original app. I have themed it to look good. Download it here.
Use it as a task killer, press menu button and include system processes and then start killing processes which are useless.
● Try to use apps as system apps.
● If you are using UC Browser then in its settings, check "Clear Data on Exit". If did, you will see UC will take less than 10mb but, if you wont do this, UC will take more than 15mb.
♦ IMPORTANT TIPS AND SETTINGS :
● Always flash rom with a clean wipe and proper flashing method.
● Do not flash gapps again if they are included in the rom.
● Do not flash internal memory scripts as they reduce performance.
● Use Adrenaline Boost. Boost once or twice a day. Boosting much will increase battery consumption.
● Use Root Cleaner app and freeze the apps which you are not using at that time. Freeze Google Play Store, Google Services Framework and other google apps which are always on. Unfreeze them when you want.
● The apps used for Backup purposes should not be installed always. Keep them in your sdcard and install them when you want and uninstall when done with them.
● Basic apps should always be in system/app.
● In Developer Options -
Set all animations scale to .5x
Set Background Process Limit to "Atmost 4 processes", if issues occur then set it back to "Standard Limit".
Enable "Kill App Back Button". Always use this feature to come out of the apps which do not really exit on pressing just back button.
● Do not expect much from our phone as it is not a high-end phone. Dont expect good battery life but, still to gain good battery life. Keep RAM free by using the ProcessKiller app as told above. I always get 170 mb RAM free.
● Do not charge battery until it gets discharged upto 10% or less. While charging do not remove it till it reaches 100% and 20 mins above that.
● Calibrate battery when needed.
● Avoid use of apps which are always running either in background or foreground.
● Press thanks. .
Thanks! I'm definetely going to try this out, even though I'm not running JB but ICS.
Deleting unneeded apps works on every Android version I think, and ActivoSpeeder works on ICS too, so I'm happy!
StiQuezNL said:
Thanks! I'm definetely going to try this out, even though I'm not running JB but ICS. Deleting unneeded apps works on every Android version I think, and ActivoSpeeder works on ICS too, so I'm happy!
Click to expand...
Click to collapse
As I hv mentioned in the title.. this method is for all ROMs.. It is not needed that you should be running JB only.. it is for all...
Noobwithdumbquestions said:
this made everything a lot more laggy and gmail stopped syncing... Also takes about 3 times as long to boot.
No offence, but this is pretty terrible. And after doing some actual research a lot of the "tweaks" you talk about here are never proven effective and frowned upon by actual experts. Even in the article you linked the writer says that something like dalvik heapsize is not something you should or have to change.
I would advice anyone to NOT waste any time on this.
ps: the last part (under tips and settings) is actually some good advice, although the background process limit is not saved in CM10 (and the max.mem tweak doesnt work), so you'll need to do that everytime at startup
Click to expand...
Click to collapse
please dude if you don't know how to tweak you can go i don't use this guide but it's a good one maybe you installed all those thing over a already tweaked rom, this guide if for clean stock, cm7/9/10/10.1
Nice guide...but I think you are wrong about the services.jar. You have to patch it when you use ICS or Jelly Bean, not on GB. And there is no Official CM7 on Gio.
Verstuurd van mijn GT-S5660
Verstuurd van mijn GT-S5660
tcris45 said:
please dude if you don't know how to tweak you can go i don't use this guide but it's a good one maybe you installed all those thing over a already tweaked rom, this guide if for clean stock, cm7/9/10/10.1
Click to expand...
Click to collapse
I applied it on a clean cm10.1 twice, had the same results, twice. I am not trying to talk down on someone elses work, but the fact is that some of the "tweaks" he talks about are never proven and often based on urban myths and the perception of people who applied them and saw improvement (placebo effect). fwiw, OP himself links to an article that busts some of the myths about tweaks, he tells people to apply...
So, maybe my device didnt start to lag more, in fact, it might have been more stable... however, setting the fs.file-max too big (as is one of the many things that activo script does) will make it less responsive, like there is a 100ms sleep between every action... I also experienced that with manual sysctl.
And some other tweaks that do work are still not great for everyone because they got other side effects that are not mentioned anywhere in this article. I got no idea why sync started giving errors and gmail stopped updating (twice) after these tweaks, but they did....
I am completely new to android, and should've done more research before blindly following some article that states to have some magical cure. But I am not new to linux and it seems this community suffers from the same kind of idiosyncrasies at the bottom end, where people constantly try to fix **** that isnt actually broken.
I'm talking about tweaks here obv, removing gapps. bloatware and lowering requirements for the OS is obv fine...
When someone's Gio lags, it's probably because they want to do stuff with it it's not made for, it's a slow device with minimal specs that does the pure core tasks as pda, phone, messenger and email, and as long as you do those it'll be fine. If you want more, buy a better phone. If it's that important to you and you dont have money, learn to appreciate what is actually important in life.
Nuff said.
Noobwithdumbquestions said:
I applied it on a clean cm10.1 twice, had the same results, twice. I am not trying to talk down on someone elses work, but the fact is that some of the "tweaks" he talks about are never proven and often based on urban myths and the perception of people who applied them and saw improvement (placebo effect). fwiw, OP himself links to an article that busts some of the myths about tweaks, he tells people to apply...
So, maybe my device didnt start to lag more, in fact, it might have been more stable... however, setting the fs.file-max too big (as is one of the many things that activo script does) will make it less responsive, like there is a 100ms sleep between every action... I also experienced that with manual sysctl.
And some other tweaks that do work are still not great for everyone because they got other side effects that are not mentioned anywhere in this article. I got no idea why sync started giving errors and gmail stopped updating (twice) after these tweaks, but they did....
I am completely new to android, and should've done more research before blindly following some article that states to have some magical cure. But I am not new to linux and it seems this community suffers from the same kind of idiosyncrasies at the bottom end, where people constantly try to fix **** that isnt actually broken.
I'm talking about tweaks here obv, removing gapps. bloatware and lowering requirements for the OS is obv fine...
When someone's Gio lags, it's probably because they want to do stuff with it it's not made for, it's a slow device with minimal specs that does the pure core tasks as pda, phone, messenger and email, and as long as you do those it'll be fine. If you want more, buy a better phone. If it's that important to you and you dont have money, learn to appreciate what is actually important in life.
Nuff said.
Click to expand...
Click to collapse
Look in signature, this thread is also there for Fit as well as Mini and is getting good response all over.. but you are the first one to complain on this. My advice to you- DO NOT USE THIS DO NOT POST HERE!
Some of your sayings are correct but, still this is the best way to increase performance. You might have did something wrong because this has been researched by me and some other people that this guide is perfect for low activity devices like ace, fit, mini, but if you dont want to use then dont use. I have NO PROBLEM.(I really dont get money or anything for this). lol..
FlemishDroid said:
Nice guide...but I think you are wrong about the services.jar. You have to patch it when you use ICS or Jelly Bean, not on GB. And there is no Official CM7 on Gio.
Verstuurd van mijn GT-S5660
Verstuurd van mijn GT-S5660
Click to expand...
Click to collapse
Yeah services.jar needs to be patched on ics and jellybean only. I didnt knew that official cm7 is not there for gio.. I dont own this device. sorry.
Noobwithdumbquestions said:
I applied it on a clean cm10.1 twice, had the same results, twice. I am not trying to talk down on someone elses work, but the fact is that some of the "tweaks" he talks about are never proven and often based on urban myths and the perception of people who applied them and saw improvement (placebo effect). fwiw, OP himself links to an article that busts some of the myths about tweaks, he tells people to apply...
So, maybe my device didnt start to lag more, in fact, it might have been more stable... however, setting the fs.file-max too big (as is one of the many things that activo script does) will make it less responsive, like there is a 100ms sleep between every action... I also experienced that with manual sysctl.
And some other tweaks that do work are still not great for everyone because they got other side effects that are not mentioned anywhere in this article. I got no idea why sync started giving errors and gmail stopped updating (twice) after these tweaks, but they did....
I am completely new to android, and should've done more research before blindly following some article that states to have some magical cure. But I am not new to linux and it seems this community suffers from the same kind of idiosyncrasies at the bottom end, where people constantly try to fix **** that isnt actually broken.
I'm talking about tweaks here obv, removing gapps. bloatware and lowering requirements for the OS is obv fine...
When someone's Gio lags, it's probably because they want to do stuff with it it's not made for, it's a slow device with minimal specs that does the pure core tasks as pda, phone, messenger and email, and as long as you do those it'll be fine. If you want more, buy a better phone. If it's that important to you and you dont have money, learn to appreciate what is actually important in life.
Nuff said.
Click to expand...
Click to collapse
okay go step by step and tell me what is it that is actually bothering you about the tweaking.(talk only about supercharger method not activ speedo).
yes most of the tweaks are utter bull**** The tweaks in the op(build prop ones are actually proven read the article again).As for dalvik size its recommended to keep a size around 48 so that you processes don't need to split their dalvik heaps into two separate piles thus reducing ram consumption.
Dark Passenger said:
okay go step by step and tell me what is it that is actually bothering you about the tweaking.(talk only about supercharger method not activ speedo).
yes most of the tweaks are utter bull**** The tweaks in the op(build prop ones are actually proven read the article again).As for dalvik size its recommended to keep a size around 48 so that you processes don't need to split their dalvik heaps into two separate piles thus reducing ram consumption.
Click to expand...
Click to collapse
I didnt use the supercharger method... The OP says the activo speedo is recommended, and the supercharger method is proposed as an alternative... I already said what problem I had with it (the response thing, and believe me or not, to me this difference is obvious and makes sense, I was able to reproduce it with just changing some of the same sysctl settings myself) but I wouldnt be surprised if there were more as it seems to do a buttload of things.
As far as the heapsize goes, I am not basing my conclusions on anything other than the OP's own link, which says things like:
dalvik.vm.heapgrowthlimit and dalvik.vm.heapsize - BUSTED,
Click to expand...
Click to collapse
This is one property that has cropped up recently in various build.prop recommendations for ICS. Typical suggested values range from “48m” all the way up to “256m”, likely motivated by the common misconception that more is better. The real purpose of this property is much less obvious than one might initially guess. It is also another one you should probably avoid changing.
Click to expand...
Click to collapse
Should you change this setting? Probably not.
Click to expand...
Click to collapse
Maybe you are right, I dont know all the technical implications, and I got no way to check it other than to test it and I see no difference in ram consumption if I change this property.
The ro.power.dissable thing might shut off wifi when in deep sleep and jumps back to mobile (I think, it happened after applying all tweaks and it seems the most likely thing to do that), but whatever causes that, you should warn people about that sort of thing as it can cost them money..
I didnt use it for long and I'm not an expert, i'm just sharing my findings, people can make up their own mind about it and share their experiences as well..
OJ said:
Look in signature, this thread is also there for Fit as well as Mini and is getting good response all over.. but you are the first one to complain on this. My advice to you- DO NOT USE THIS DO NOT POST HERE!
Some of your sayings are correct but, still this is the best way to increase performance. You might have did something wrong because this has been researched by me and some other people that this guide is perfect for low activity devices like ace, fit, mini, but if you dont want to use then dont use. I have NO PROBLEM.(I really dont get money or anything for this). lol..
Click to expand...
Click to collapse
Sorry, I didnt mean to offend you in any way and appreciate your effort... But telling me to stop posting just because I'm critical seems pretty backwards. If you only want people to say thanks and be greatful all the time, maybe you should start sharing horse pictures on a hello kitty forum...
I'm just sharing my experience and my problems might be related to my rom and it could very well work great on other phones or other roms... But I used a clean cm10.1, the CM10.1 rom almost everyone with a Gio uses, so I'd think it's still important to bring up my findings...
Noobwithdumbquestions said:
I didnt use the supercharger method... The OP says the activo speedo is recommended, and the supercharger method is proposed as an alternative... I already said what problem I had with it (the response thing, and believe me or not, to me this difference is obvious and makes sense, I was able to reproduce it with just changing some of the same sysctl settings myself) but I wouldnt be surprised if there were more as it seems to do a buttload of things.
As far as the heapsize goes, I am not basing my conclusions on anything other than the OP's own link, which says things like:
Maybe you are right, I dont know all the technical implications, and I got no way to check it other than to test it and I see no difference in ram consumption if I change this property.
The ro.power.dissable thing might shut off wifi when in deep sleep and jumps back to mobile (I think, it happened after applying all tweaks and it seems the most likely thing to do that), but whatever causes that, you should warn people about that sort of thing as it can cost them money..
I didnt use it for long and I'm not an expert, i'm just sharing my findings, people can make up their own mind about it and share their experiences as well..
Click to expand...
Click to collapse
the ro.power.disable.ril actually causes the phones radio to go to sleep so if your mobile data is off there is no reason to switch on rather the wifi might switch off(devs already stated so) and again switch back on once you get out of deep sleep.
its a good thing that you are coming back to provide a feedback and is appreciated(at least should be).
the change for dalvik.vm larger than 48 only allows the heap to grow to that value then split into a new heap since we can't/shouldn't/don't use apps with such a large memory footprint the chances of a split occurring post 48mb(gb and below) and 64mb(ics and above) is highly unlikely hence the changing the value to a larger quantity will make no difference.
PS personally even i dont like activo mainly cause i dont know how it works rather i use supercharger and its a much better option in my opinion.
Sorry, I didnt mean to offend you in any way and appreciate your effort... But telling me to stop posting just because I'm critical seems pretty backwards. If you only want people to say thanks and be greatful all the time, maybe you should start sharing horse pictures on a hello kitty forum...
I'm just sharing my experience and my problems might be related to my rom and it could very well work great on other phones or other roms... But I used a clean cm10.1, the CM10.1 rom almost everyone with a Gio uses, so I'd think it's still important to bring up my findings...
Click to expand...
Click to collapse
No, I already told you that many of your ideas are correct but, your way of expressing was not good.
Ex- You said that "Dont waste time on using this guide".
Now, if you think that was correct then please do not post again. If you are providing information then you can but, if you are telling people not to use this then dont post.
In fit's thread, Dark Passenger also wanted to express his ideas and wanted to help me. And I was happy about that. Because the way he helped me was like he really wanted to help. But, you was not polite as him.
You can ask Dark Passenger, there is a lot of information in the thread provided by him and I used that. And he never complained like you.
@Dark Passenger, please explain him.
OJ said:
No, I already told you that many of your ideas are correct but, your way of expressing was not good.
Ex- You said that "Dont waste time on using this guide".
Now, if you think that was correct then please do not post again. If you are providing information then you can but, if you are telling people not to use this then dont post.
Click to expand...
Click to collapse
Yeah, I was frustrated and my first response was not really fair. I agree.
Noobwithdumbquestions said:
Yeah, I was frustrated and my first response was not really fair. I agree.
Click to expand...
Click to collapse
When you use ics or jelly bean you need supercharger script and a patched services.jar (it's easy to do) because any other script don't works 100 % on it.
Sent from my GT-5660 using xda premium
Does this even need an explanation? Lollipop kills apps like it's his hobby.
Even with only a few light (on RAM) user apps running in the background you sometimes find yourself staring at your launcher home screen that, you could've sworn, was just showing a different app a second ago.
Or the times when, after multi-tasking a bit, your phone starts becoming painfully slow. Turns out that some apps are so stubborn that they go on strike (continuously restarting) when LP kills them.
I'm sure many have experienced this. And I have seen some devs address this issue here and there. I though it would be useful to gather the info into one thread, to ease our (or my?) frustration on this issue.
What I wanna know is, what causes it exactly (why didn't it happen on KK?), and is there a solution to this? Or at some way to calm LP down a bit with his killing of innocent apps.
Thanks.
Djalaal said:
Does this even need an explanation? Lollipop kills apps like it's his hobby.
Even with only a few light (on RAM) user apps running in the background you sometimes find yourself staring at your launcher home screen that, you could've sworn, was just showing a different app a second ago.
Or the times when, after multi-tasking a bit, your phone starts becoming painfully slow. Turns out that some apps are so stubborn that they go on strike (continuously restarting) when LP kills them.
I'm sure many have experienced this. And I have seen some devs address this issue here and there. I though it would be useful to gather the info into one thread, to ease our (or my?) frustration on this issue.
What I wanna know is, what causes it exactly (why didn't it happen on KK?), and is there a solution to this? Or at some way to calm LP down a bit with his killing of innocent apps.
Thanks.
Click to expand...
Click to collapse
Im running 1/8 FML with synapse injected R10 kernel on my toro and with ksm and laptop mode enabled in synapse, I haven't had a launcher redraw in days. I don't have anything whitelisted either. However, the trade-off I have at the moment is I cant seem to stream videos on my stock browser. Havent tried a different browser or anything. I just uncheck those two settings and reboot and all is well, but my phone certainly works much better now, and no redraws, with neph settings for LMK
Hope something helps someone!
Thanks
erk1725 said:
Im running 1/8 FML with synapse injected R10 kernel on my toro and with ksm and laptop mode enabled in synapse, I haven't had a launcher redraw in days. I don't have anything whitelisted either. However, the trade-off I have at the moment is I cant seem to stream videos on my stock browser. Havent tried a different browser or anything. I just uncheck those two settings and reboot and all is well, but my phone certainly works much better now, and no redraws, with neph settings for LMK
Hope something helps someone!
Thanks
Click to expand...
Click to collapse
Perhaps you can noobify that a bit, lol. I had to google almost everything you mentioned. As I understand it, this Synapse allows you to tweak the kernel? And this KSM settings can improve this RAM issue? Care to elaborate? And what is laptop mode?
I've read about adjusting the LMK values to calm LP down a little. Any idea though why this was so necessary in LP, but not in KK? Is stock LP 'naturally' more RAM hungry than KK?
Djalaal said:
Perhaps you can noobify that a bit, lol. I had to google almost everything you mentioned. As I understand it, this Synapse allows you to tweak the kernel? And this KSM settings can improve this RAM issue? Care to elaborate? And what is laptop mode?
I've read about adjusting the LMK values to calm LP down a little. Any idea though why this was so necessary in LP, but not in KK? Is stock LP 'naturally' more RAM hungry than KK?
Click to expand...
Click to collapse
I can try to elaborate little bit, as Ive been flashing things and researching xda a lot, but I am still noob in how/why things are the way they are. From what I gather lollipop just handles memory differently then kk did. I think that is some of the reason as to why the "recent apps" persist through reboots now. Remember, our device was not really supposed to run kk and certainly not meant to run lollipop. The developers here are without a doubt amazing in what they know and what they do for us users. A new kernel and driver was necessary to run lollipop on the aging gnex. Now, some of the issues we are experiencing is a google issue and will only seem to get fixed when they get around to it. I know my nexus 7 (old) has some memory issues and lag and redraws from time to time....not as much as I noticed with my gnex before the changes were made I stated in the above post. I recently helped my friend root and upgrade his oneplus one to lollipop and he has the same issues we all have, maybe not as bad, but they are noticeable
A lot of the questions you have, have been discussed recently in bsmitty83 kernel thread, since I asked them. There are links there as to what KSM and laptop mode are and what they do. KSM-kernel same page merging helps with RAM and I believe laptop mode helps to conserve power. A lot of these things are geared at devices with low ram like the aging gnex, but the developers have done a great job at making lollipop a daily driver. Most users I think use trickstermod from playstore to tune kernel settings, and that is ok, however, you must purchase the paid version to tweak low memory settings, which I did. However, synapse, also found on playstore can also be used to tweak kernel settings, but the kernel has to contain UCI support for the synapse app to work. Synapse has more settings available to tweak than trickster does, like KSM and laptop mode, which have helped me very much. The only kernel I'm aware of that has UCI support for synapse is bsmitty83 Full_Auto R10, because osmosis made it work
Hopefully this was rather accurate and helpful and not convoluted! ha.....im sure some more knowledgeable people will come and correct anything I said that may be incorrect, but in the meantime, read through the R10 kernel thread and see what you come up with
What ROM and kernel are you currently using?
Thank you
erk1725 said:
...
The only kernel I'm aware of that has UCI support for synapse is bsmitty83 Full_Auto R10, because osmosis made it work.
...
What ROM and kernel are you currently using?
Click to expand...
Click to collapse
I'm currently using AOSP rom (by freshgimmi) and the Full Auto R10 you mentioned. I'll try injecting the new ramdisk now and see how it goes.
I noticed this issue as well for the first several days . However once I installed the new bootanimation from arter97 the issue doesn't occur anymore. Not sure if it's related but all I did was mount /system as rw and copied into the new lollipop boot animation from here: http://forum.xda-developers.com/android/software/arm-arm64-android-5-0-lollipop-t3032247
Djalaal said:
Does this even need an explanation? Lollipop kills apps like it's his hobby.
Even with only a few light (on RAM) user apps running in the background you sometimes find yourself staring at your launcher home screen that, you could've sworn, was just showing a different app a second ago.
Or the times when, after multi-tasking a bit, your phone starts becoming painfully slow. Turns out that some apps are so stubborn that they go on strike (continuously restarting) when LP kills them.
I'm sure many have experienced this. And I have seen some devs address this issue here and there. I though it would be useful to gather the info into one thread, to ease our (or my?) frustration on this issue.
What I wanna know is, what causes it exactly (why didn't it happen on KK?), and is there a solution to this? Or at some way to calm LP down a bit with his killing of innocent apps.
Thanks.
Click to expand...
Click to collapse
SpideyTheMan said:
I noticed this issue as well for the first several days . However once I installed the new bootanimation from arter97 the issue doesn't occur anymore. Not sure if it's related but all I did was mount /system as rw and copied into the new lollipop boot animation from here: http://forum.xda-developers.com/android/software/arm-arm64-android-5-0-lollipop-t3032247
Click to expand...
Click to collapse
I know about this issue. It is a memory leak during boot. It is a good catch, though all you're changing is the bootanimation.zip. AFAIK, it should not affect your system's performance after boot, once your phone is up and running. My issue is a different thing entirely. I never got bootloops (that is, when not messing around with xposed).
Okay, you're right. As a test last night I switched from FML 5.0.2 to LiquidSmooth's LP ROM and I'm not seeing any aggressive app kills in LiquidSmooth.
Djalaal said:
I know about this issue. It is a memory leak during boot. It is a good catch, though all you're changing is the bootanimation.zip. AFAIK, it should not affect your system's performance after boot, once your phone is up and running. My issue is a different thing entirely. I never got bootloops (that is, when not messing around with xposed).
Click to expand...
Click to collapse
erk1725 said:
Im running 1/8 FML with synapse injected R10 kernel on my toro and with ksm and laptop mode enabled in synapse, I haven't had a launcher redraw in days. I don't have anything whitelisted either. However, the trade-off I have at the moment is I cant seem to stream videos on my stock browser. Havent tried a different browser or anything. I just uncheck those two settings and reboot and all is well, but my phone certainly works much better now, and no redraws, with neph settings for LMK
Hope something helps someone!
Thanks
Click to expand...
Click to collapse
I have got synapse up and running. I AM wondering though, what LMK settings are you using? Cause the neph settings I know of tell me to set empty app to 370, but synapse only allows max 320... If you're following different settings, could you link the post for me?
Djalaal said:
I have got synapse up and running. I AM wondering though, what LMK settings are you using? Cause the neph settings I know of tell me to set empty app to 370, but synapse only allows max 320... If you're following different settings, could you link the post for me?
Click to expand...
Click to collapse
Glad you got everything up and running.....Im using Neph's settings for LMK, and your correct the empty app only goes up to 320 in synapse. There was a post somewhere where Neph said he was still tweaking his LMK values and I believe he mentioned about lower empty app to 330 or something, so I just set it to 320 in synapse and call it a day