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
Related
Hey guys,
Seems there's a lot of ways you can improve the speed of Android in general. Some seem to be snakeoil... others, work quite well and there's proof to back it up.
I'm only interested in discussing the latter .
A lot of people have helped me gather a better understanding of Android (hyc, stinebd to name a few) in addition to a lot of Google searching. I am going to compile a list of what I have done, I would like to hear what you guys have done! Most app killer apps / app control will already be addressed, so those tools need not apply... I'm looking for real, permanent fixes here without adding more apps!
I am also trying to have topics that are easy working up to advanced. Obviously the more advanced topics are going to be harder to do. You've been warned.
So here's the disclaimer.
****DISCLAIMER****
Speed is as always relative. That basically means I don't want arguments about which build is faster. I want to argue about how to make every build faster .
Also, these tips should apply to any build, any device... they are pretty generic tips, but are obviously specific to Android, with some idiosyncrasies that apply to our port that wouldn't apply to native Android devices. Some is common sense, others are real ways to tear into the system. Hope you enjoy it!
Topic 1
Difficulty Easy - Apps/Widgets
I've noticed the number of widgets i have on my screens, or the number of apps that I have installed/are running in the background to greatly effect performance, in an obviously negative way.
Once I removed all the widgets (I only have the basic analog clock widget & the Google search widget on one desktop...) this seemed to improve general speed. One minor thing to check is if apps are set to auto/background sync. Only enable the ones you really want syncing, others just check manually.
On this same topic, replacing the launcher (the stock launcher in Android, Launcher2 is quite slow) can help immensely. I like ADW, but I've used LauncherPro in the past and it is good. Zeam also seems like a good launcher. I haven't used Go Launcher EX, I've heard good and bad things about it. Use what works best for you, try 'em all!
The last thing on this topic I would like to mention is animations. Settings -> Display -> Animation -> No animations can make the phone feel quite a bit snappier, obviously at the expense of the look/feel of the OS.
Topic 2
Difficulty Easy - Controlling app 'net Access
This leads me into the next topic, DroidWall. I've noticed that blocking apps from accessing the internet has been a very good thing - it's not so much a performance booster (although it probably does provide a little bump) it's mostly about battery life. Just be warned, if you block an app that is set to background sync, it will probably have very negative effects. Only disable an app's access to the internet with DroidWall after you've checked that app's background sync feature is disabled. I have a few apps allowed in DroidWall, and the rest are blocked. You can "whitelist" everything and check apps you want to block, or "blacklist" everything and check the apps you want to allow. It's a little annoying to remember to enable/disable DroidWall (I use the DroidWall widget to enable/disable it globally) but if you do, it is much better - you have complete control over how apps access the 'net on your device. It is available on the Market.
Topic 3
Difficulty Moderate - SD cache/readahead tweaking
The only reason I'm calling this one 'moderate' is the number of choices you have for settings for this... It's basically telling the SD card how much to hold on to or... read "ahead" if you will . This was turned way up in FRX07, (from 256kb to 2048kb or 2mb...) and I think this might be the source of a lot of the complaints of 'mini-resets' if you will where the boot animation is suddenly seen after a long system hang...
So some cards will work better with a larger setting - I've heard some with spankin new C6 cards that said 3072kb or 3mb was a good setting. Others have found a sweet spot at 256kb or 1024kb (1mb).
There are two ways of doing this - you can hack the init in the rootfs and adjust the setting manually, or be lazy like me and use SD Booster (from the Market). Adjusts the same settings, and they are applied immediately!
I would like to find a "sweet spot" - a good default if you will. Can folks test out 512kb and 1024kb, see if you have any more mini-resets within Android or any other slowness, etc... Obviously this isn't a cure-all for the slowness or the mini-resets, what we're looking to do is mitigate the effects. So let's focus on that, thanks!
Topic 4
Difficulty Moderate - Overclocking
Overclocking is obviously one relatively easy way to improve the speed of Android. In your startup.txt, add a line
Code:
acpuclock.oc_freq_khz=710400
for example to overclock to 710.4mhz. How did I find this value? I actually put in 714000, but if you look at dmesg near the beginning you'll see "ACPU running at ..." - that's what clock is the actual maximum. It goes in 19.2khz increments.
Feel free to experiment with how high your phone can go, just be warned that the higher you go the potential for failure goes up as well . Phone shouldn't blow up, but it might not work correctly or at all. Rebooting and scaling it back will fix it.
Here's the full *example* startup.txt:
Code:
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2292
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=240 msmvkeyb_toggle=off gsensor_axis=2,1,3 pm.sleep_mode=1 physkeyboard=rhod400 acpuclock.oc_freq_khz=710400"
boot
You can put the command anywhere in the cmdline section, just make sure it's between the quotes and at least one space between each command.
Topic 5
Difficulty Advanced - How Android Manages Memory/apps
Ok, I'm going to take two approaches to this. The first, is the full explanation on how Android manages memory.
Please feel free to read the post I originally read that inspired me to start looking at this stuff - How to configure Android's *internal* taskkiller. It was very helpful for me to grasp how Android manages applications. This is the reason why application killers are not a good thing...
If you want to do it manually, Starfox suggests:
Code:
echo "1536,3072,8192,10240,12288,20480" > /sys/module/lowmemorykiller/parameters/minfree
To try to do these commands, adb is very useful. Once you get adb shell working, then you just need to "su" (provides 'super user' privileges (root)) and put in the echo command above ^^.
I had another user (thanks icevapor) suggest this script -
[Script] V6 SuperCharger! HTK & BulletProof Launchers! The ONLY Android MEMORY FIXER!
I tried it myself, and it works very well. This thread is a little overwhelming, but the jist of it is this:
Install Script Manager (on the Market)
Run the V6 SuperCharger script. I use "Aggressive 1 Settings" (#2) and then I use the OOM Grouping Fixes & "Hard to Kill" launcher (#17)
Point Script Manager to run /data/99SuperCharger.sh to run as root & on boot. This will ensure the tweaks are reapplied after a reboot.
Topic 6
Difficulty Advanced - Managing Apps that auto-start on boot
This is one of the most annoying things in Android. When you have no apps installed, it seems very fast. Then you install apps, and you never seem to get that original speed back... Now you can!
This is kind of difficult to do, I am still getting the hang of it... but here goes. All credit goes to hyc, his original post.
The basic idea here is you run a logcat (adb logcat is easiest here, or you can use GetLogs to pull logcat...) Look in this log for "for broadcast" and find apps that start on boot. For example,
Code:
Line 41: I/ActivityManager( 1394): Start proc nextapp.systempanel for broadcast nextapp.systempanel/.monitorservice.BootReceiver: pid=1752 uid=10060 gids={3003, 1015}
Notice there are two sides of the "for broadcast". The name of the package (nextapp.systempanel) and the name of the service, "nextapp.systempanel/.monitorservice.BootReceive". I made the mistake of disabling the app (the left side). Do not do this, you want to disable the right side!
So in the shell,
Code:
pm disable nextapp.systempanel/.monitorservice.BootReceive
This will be persistent across boots, it will go with your data.img.
Obviously this was just one example of an app to disable. So long as you disable the right side (after the 'for broadcast') you shouldn't disable anything that will cause a serious problem. The apps should still work, but for example if you disable Google Voice you won't get messages until you open the app. So think about that... You disable Titanium Backup schedules.BootReceiver, the schedules for Titanium Backup (if you have any) won't run. Stuff like that. Disable calendar, you won't get calendar events... Disable clock no alarms. Get it? Good. I have been rebooting several times, and I keep checking what is set to start on boot. I'm not quite happy with it yet, but there's some things I'm leery of disabling. Just be wary, if you do disable something and don't like it - just pm enable <whatever you disabled>.
Now experiment away! The one caveat is if you do break something with pm disable (and it's serious) you might get a failure to boot. It really depends on how bad you mess up. If you make a copy of your data.img before you start making these changes, you can revert to that data.img and start back there.
Alright guys. Going to use this thread as a way to brainstorm about ways to improve the speed. Read up what I've posted, let me know if I did anything wrong... Also let me know what you guys do to improve speed!
Don't care about what build you're running, this thread isn't about what build is fastest - this is a how do I make every build faster thread.
I also realize I posted this in the Rhodium section - I want to see if there's any BLAC-specific tweaks that others should be made aware of!
Thanks. Great posting. Will try some of the topics I never used (because I didn't know about them).
ThaiDai said:
Thanks. Great posting. Will try some of the topics I never used (because I didn't know about them).
Click to expand...
Click to collapse
I'm sure there are more as well... These are just the ones that I found made the most difference on my device.
I'm also curious about the minfree setting. I've only tried a few settings, they seem good. I haven't done any drastic number changing, it seems like changing these values should be done with a lot of caution and testing. There are definitely some values that should not be touched and others that can take some more fudging with numbers .
Added Topic 3 and Topic 4 to startup.txt and rootfs.img.
Just booting. Let's see if this is stable.
Software options I do not test now because I only test the new versions now. So specific app optimization only necessary when ThaiDai Android Loader and installation procedure reaches v2
Ok, boot ok, started Android (NeoFROYO build(, will tell tomorrow if stable.
If so I will use this options as standard for Blacky and I will add software like Droid firewall.
Thanks and good night
Update - I redid topic 4, feel free to re-read it.
Thanks
Enviado desde mi FROYO BLUE CWM1.9 usando Tapatalk
Hi Arrrghhh!
Can a squashfsed and odexed apk boost speed inside Android OS?
john_matrix said:
Hi Arrrghhh!
Can a squashfsed and odexed apk boost speed inside Android OS?
Click to expand...
Click to collapse
No clue. What does that have to do with the Speed Improvements thread?
I'm guessing you tried and it didn't work? What APK!?!
I guess I don't really follow your train of thought. Does sqshfs'ing and odexing an APK make it run faster...? I'm pretty new to Android in general. Never even used a native Android device .
http://www.addictivetips.com/mobile/what-is-odex-and-deodex-in-android-complete-guide/
http://forum.xda-developers.com/showthread.php?t=709630
farukb said:
http://www.addictivetips.com/mobile/what-is-odex-and-deodex-in-android-complete-guide/
http://forum.xda-developers.com/showthread.php?t=709630
Click to expand...
Click to collapse
I still don't get what that has to do with our builds. ODEX and DEODEX have nothing to do with our builds... That stuff only applies to native devices, or builds that are ported from native devices (I would think).
Perhaps I'm missing something here... please tell me if I am .
Maybe they mean something else like: oxidized or deoxidized (reduced) apps. With these modified apps you can speed up the transfer of electrons, resulting in more performance without overclocking your cpu. And more: it will not reduce your battery capacity measurable. I used it in some of the builds I tried. You will get a nice small benefit also: because of the electron transfers you will get a small induced massage in your fingers for free.
ThaiDai said:
Maybe they mean something else like: oxidized or deoxidized (reduced) apps. With these modified apps you can speed up the transfer of electrons, resulting in more performance without overclocking your cpu. And more: it will not reduce your battery capacity measurable. I used it in some of the builds I tried. You will get a nice small benefit also: because of the electron transfers you will get a small induced massage in your fingers for free.
Click to expand...
Click to collapse
LOL!
Epic.
OK. I cant get V6 SuperCharger script to work! I downloaded the script and run it but I cant find /data/99SuperCharger.sh after I run it
x12CHRIS18x said:
OK. I cant get V6 SuperCharger script to work! I downloaded the script and run it but I cant find /data/99SuperCharger.sh after I run it
Click to expand...
Click to collapse
Did you make the choices in the script, or did you just exit the script?
You have to make sure ScriptManager is running as root too. There's a setting for it. "Browse as root" - make sure that is enabled. You won't be able to see /data without browsing as root.
...You have a TouchHD? I always thought you had a RHOD, lol.
Hello all,
I am the owner of a rooted xperia play with stock rom.
I've installed link2sd so that I can save some ram and space: moved most of my apps on the SD card, and deleted some unwanted native apps (Bruce Lee, Fifa, etc...) and "freezed" the others I did not dare to delete.
But this is not enough for me to play games like GTA III and Dead Trigger smoothly, even with a task killer and airplane mode set on. I suffer from many lags while playing greedy games.
I've done some researches on this forum and found some potential solutions:
- Using boosting apps like: gamebooster, ram manager pro, chainfire 3D pro, etc...
- Overclock the processor up to 1,6ghz with setCPU or other apps.
-Increase SD card performance and optimize ram as explained below:
Increase SD card performance
1. Navigate to /sys/devices/virtual/bdi/179:0 folder in your Xperia Play
2. Press and hold on the read_ahead_kb file. This action will pop out a new menu.
3. Choose Open With Text Editor option
4. Change the current value to 1024
5. Save your changes and exit
Optimize RAM
1. Grab the Juwe_Update18082011_RAM_Script.zip
2. Extract the file and put it on your SD card
3. Launch the Root Explorer
4. Navigate to /system/etc/
5. Create a new folder, named it as init.d
6. Copy the S97ramscript file into that folder
7. Set the perms of S97ramscript file to rwxrwxrwx
What is your advice? Can I use safely one (or several) of those solutions? What are the risks? Which solution is really effective and will allow me to play demanding games?
My xperia play is still under warranty so I don't want to lose it. Which means I don't want to try custom roms or custom kernels... Until my warranty ends.
Thanks for your help!
Well, the biggest performance boost, overclocking, requires a custom kernel. Not much else really makes a huge difference
Also, I believe using the init.d directory requires a custom kernel as well
Why not just use v6 supercharger?
Sent from my R800x using xda premium
jgregoryj1 said:
Why not just use v6 supercharger?
Sent from my R800x using xda premium
Click to expand...
Click to collapse
Did not know about this one...
It has a lot of success judging from the number of pages in the official v6 Supercharger thread...
But seems a bit complicated to me. Does it really works? Have you noticed some improvements in your performances?
More importantly, does it preserve the phone's warranty? I've read somewhere that it can be uninstalled so I guess so, but I'd like a confimation first.
Thanks for your help.
Look, the amount of times I have seen this type of thread open is astounding I would like to point that you use gingerbread any version (2.3.7 Moded to look like rom) and a custom kernel such as Doomlords etc. Supercharge or use a rom like Dike's. You only get best performance with using less apps, rebooting the phone before playing a game, task killers, clean your cache, installing phone eco friendly apps and use a governer for your preference!
---------- Post added at 01:47 PM ---------- Previous post was at 01:45 PM ----------
cityhunter62 said:
Did not know about this one...
It has a lot of success judging from the number of pages in the official v6 Supercharger thread...
But seems a bit complicated to me. Does it really works? Have you noticed some improvements in your performances?
More importantly, does it preserve the phone's warranty? I've read somewhere that it can be uninstalled so I guess so, but I'd like a confimation first.
Thanks for your help.
Click to expand...
Click to collapse
No you wont because you have to root, rooting voids the warranty anyway but you can simply unroot after...
cityhunter62 said:
Did not know about this one...
It has a lot of success judging from the number of pages in the official v6 Supercharger thread...
But seems a bit complicated to me. Does it really works? Have you noticed some improvements in your performances?
More importantly, does it preserve the phone's warranty? I've read somewhere that it can be uninstalled so I guess so, but I'd like a confimation first.
Thanks for your help.
Click to expand...
Click to collapse
I saw a vast improvement in my phone with V6. Its really easy. Just place the scirpt on your SDcard. Download script manager, then select the V6 script, check run as root, and hit go. Follow the on screen selection.
I did the following
512 HP super unleaded (Bulletproof home)
Nitro Lag nullifier
Seriously.... BIG difference in my phone. I could b playing a game and hit the home button.. BAM... there instant no lag no redraw, nothing just all there ready to go. Seriously cannot praise it enough.
nice..
Just to share my experience.
I've bought Ram Manager Pro finally.
I know it's probably not as effective as an overclock or V6 Supercharger, but I do not want to mess with the kernel, custom roms or scripts.
I'm running on stock gingerbread rooted, I've removed the bloatwares and I think it's enough modifications already. I don't want any bugs or troubles with stability so I don't want to modify the OS too much.
Anyway, I'm using Advanced Task Killer along with Ram Manager Pro... And it works! Really.
I was not able to play GTA because it was too laggy, but with Ram Manger Pro set on "Hard Gaming", I was able to improve the graphics (max details, dynamic shadows, 75% clipping and 80% resolution) and it plays rather nicely. It's not really smooth (not like 60 FPS) but it's far enough to be playable and enjoyable.
It wasn't without Ram Pro Manager. SO it's worth trying. Don't expect miracles but some gain in performances, surely.
Maybe I should try an alternative launcher as I heard it can improve performances as well... Any suggestions for a light and modest one?
Also, is there anyway to prevent Maps, Facebook, Crash bandicoot or Super Monkey Ball to start automatically even with task killer? I can understand (to a certain extent) that Maps and Facebook needs to start and connect, but Crash Bandicoot and Monkey Ball??? Seriously? WTF?
cityhunter62 said:
Just to share my experience.
I've bought Ram Manager Pro finally.
I know it's probably not as effective as an overclock or V6 Supercharger, but I do not want to mess with the kernel, custom roms or scripts.
I'm running on stock gingerbread rooted, I've removed the bloatwares and I think it's enough modifications already. I don't want any bugs or troubles with stability so I don't want to modify the OS too much.
Anyway, I'm using Advanced Task Killer along with Ram Manager Pro... And it works! Really.
I was not able to play GTA because it was too laggy, but with Ram Manger Pro set on "Hard Gaming", I was able to improve the graphics (max details, dynamic shadows, 75% clipping and 80% resolution) and it plays rather nicely. It's not really smooth (not like 60 FPS) but it's far enough to be playable and enjoyable.
It wasn't without Ram Pro Manager. SO it's worth trying. Don't expect miracles but some gain in performances, surely.
Maybe I should try an alternative launcher as I heard it can improve performances as well... Any suggestions for a light and modest one?
Also, is there anyway to prevent Maps, Facebook, Crash bandicoot or Super Monkey Ball to start automatically even with task killer? I can understand (to a certain extent) that Maps and Facebook needs to start and connect, but Crash Bandicoot and Monkey Ball??? Seriously? WTF?
Click to expand...
Click to collapse
Try Autostarts to disable apps from running automatically
Sent from my Xperia Play!
Install custom ROM like Xperia NXT and get Bloatware remover by fma965 = SMALL SPEED BOOST
Sent from my R800i using xda app-developers app
Surprising to me, I have been PMd by a few people asking about how I resolved issues that I was having with my tablet. I could not give you a specific answer on why and how well my tablet runs so this is just how I do it. Results for you may vary, and what works for me may have been a problem for others. I am in no way a dev, nor do I take credit for their work.
I am posting this as possible tips for CM10 (9/2/12build) w/ godmachine kernel v2.0 & the latest gapps available from goo.im. If you are not to that point or do not understand what I am talking about, STOP, and go read pio_masaki's [Guide] All things Iconia A100 (guide to modding)
MY RECOMMENDED APPS
Apex Launcher (NOVA Launcher is a good alternative) since Trebuchet 2.0 freezes/crashes ALOT
SetCPU w/profiles enabled for my overclock needs
ESFileExplorer for root and normal file manipulation as well as streaming video from my home server.
Titanium BackupPRO i think is the best file backup/restore software. Market Doctor as well as bloat ware/unwanted system app melter ability to integrate apps into ROM, than create a backup in CWM and next time you flash, all your apps will be included.
ESTaskManager for boot up app disabling/enabling, as well as Task killer if I need to terminate a running app. Has many other useful functions such as power optimization.
STARTING FROM SCRATCH/BUILDING MY CM10 SETUP
INSIDE TEAMWIN RECOVERY PROJECT
I use TWRP. In this order I wipe cache, dalvik cache, factory reset, and internal storage. Then I flash CM10, kernel, and gapps. Power off via menu option. Power on and i do not touch for 10min. than reboot wait 5 min, fill in Google profile, reboot than I start installing the rest of my apps. This is more your customization stage. Although I recommend installing your custom launcher, such as Apex Launcher, and updating Superuser before doing anything else.
USING TITANIUM BACKUP FOR FREEZING/REMOVING APPS
At this time I usually will start changing all my settings and freezing/uninstalling apps. Doing this will free up RAM and stop unused apps from even loading into the system. You can "thaw" them out anytime.
I use Titanium Backup and I freeze these system apps (I don't uninstall in case freezing an app causes a conflict):
E-Mail 4.1
Exchange Services 5.0
Face Unlock 4.1-392829
Gallery 1.1.4000 (In this build there are two identical listed, so I freeze one)
Google Play Music 4.3.605.392829
Google+ 2.6.1.30454518
Movie Studio 1.1
News&Weather 1.3.11
ROM Manager 5.0.0.8
Trebuchet 2.0
Lucky Patcher 2.5.0 (if you use it, use it for your purpose than FREEZE it until next time you need it)
Dev Tools 1.0
com.android.smspush 4.1.1-eng.odin.20120903.000735 (Not a 3G tablet, not texting so I freeze it)
[VOICEMAIL] Mobile Data 4.1.1-eng.odin.20120903.000735 (not a 3G tablet, so service not needed)
[SMS/MMS/APN] Mobile Network Configuration 4.1.1-eng.odin.20120903.000735 (not a 3G tablet, service not needed)
Network Location 1.1.10
Setup Wizard 1.3
Spare Parts 4.1.1-eng.odin.20120903.000735
VpnDialogs 4.1.1-eng.odin.20120903.000735
Voice Dialer 4.1.1-eng.odin.20120903.000735
USING ESTASKMANAGER TO EDIT STARTUP APPS
Next, I use ESTaskManager and disable a lot of the boot up apps. A lot of the apps you can disable their startup because you can launch them manually. This reduces boot up time and saves us some precious RAM and CPU cycles. Depending on what apps you uninstall or freeze, these may or may not be available to you.
I Disable:
Any of my user apps that aren't system related. Example, I can disable NOVA 3 from the boot up list because it's just cached in memory, and wasting memory to display notifications. For free games, this can actually stop all those annoying ads you get on startup. But I wouldn't want to disable SetCPU on startup, as it is controlling my governor, I/O scheduler, and CPU frequency. I am not going to list all my user apps, you get the point.
Calendar Storage-disable if you don't use
Contacts
Download Manager
Email
Exchange Services
Gmail
Google Contacts Sync
Google Playstore
Google Search (safe if you do not have any GSearch widgets, and you disable the "persistent" search bar from you home screens in settings)
News&Weather (safe if you don't use the widget)
ROM Manager (it's just best not to use this stupid thing! will get you into more trouble than good!)
Voice Dialer
USING SETCPU W/PROFILES ENABLED FOR OVERCLOCKING
Now for SetCPU, and how I use it.
Several users state that SetCPU causes a lot of problems with our tablet, and this is true, if you don't follow a few guidelines. I do have profiles enabled. I have 4 profiles. One for regular use, on for per app basis overclocking, one for screen off, and one for screen off on a per app basis so I am not under clocking as low as when screen off profile is triggered, for when apps like ESFileExplorer or Titanium Backup are performing long tasks and the screen times out.
I find using True/False and the "Any of these are true..." triggering events works best.
{
"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"
}
The problem with our tablet is it does not like using profiles. I have pinpointed the issue of SODs and random reboots being associated with SetCPU. When building profiles, you have to make sure you use the same governor in all of your profiles. You can change the I/O Scheduler for each profile without any negative effects. I use my tablet almost solely for Android Gaming, so leaving all my profiles set with lulzactive or smartassV2 is not an issue for me.
If you ABSOLUTELY want to change your governor, you can change it manually at the SetCPU "Main" screen. Just remember when you’re done to change it back to the one used in your profiles. To stop SODs (Sleep of Death), in your Screen Off profile, raise the MHz slider from 216MHz to 312MHz for your minimal under clock speed.
You can also use other features of SetCPU to undervolt and edit governors like lulzactive.
MY SYSTEM SETTINGS OPTIONS
Under Performance tab make sure for Processor and I/O scheduler that the "Set on Boot" option is OFF/UNCHECKED!
Under Memory I do have allow purging of assets ON/CHECKED
For Surface Improvement I select the "disable dithering" option. Some games/apps I use would FC until I turned this off.
zRam
I also have zRam turned on, but you have to flash a special zRam .zip from godmachine/linuxsociety from TWRP/CWM to actually have it working. Just download the appropriate .zip file for the amount of RAM you want to use for zRam compression. I use just the 100MB .zip. All the zips and a good explanation by linuxsociety are in his kernel thread
Under the Developer Options tab:
Turn on Android Debugging
I disable the "USB debugging notify" option, we already know we turned it on.
I turn on "Force GPU rendering"
For Background Process Limit I have it changed from Standard Limit to At most 4 processes
I have Kill app back button option checked.
Under Profiles tab, I tick the slider and turn profiles off.
For Wi-Fi sleep policy, I have a 5m time out. I found that wireless really sucks the life out of the battery. So if I'm not using it, I manually disable it.
BUILD.PROP MODS
I have used these, and for my uses I find that it is not needed. They do have benefits. For testing purposes I keep a copy of the stock build.prop and a copy of the modded build prop both in the system directory. Put them both in there and rename them build.prop.reg.bak and build.prop.mod.bak. Than with ESFileExplorer, make sure you have root access enabled, see pic) you can just rename the file you want to use to build.prop. Boot into recovery and clear cache and dalvik cache, and make sure you let the tablet sit for 10mins anytime you clear caches. The only time I really use the build.prop is to make an app list for the A500 in the playstore so I can download/purchase it and have it marked as so in the playstore, than extract the APK with titanium backup and than go back to stock build.prop and side load the app. Some apps will install under the A500 mod, but will FC or not run properly until you return to the stock build.prop.
I really can't think of anything else that I may be doing that can help you guys out. A suggestion I stand by, is I don't bother with widgets. They take up memory and CPU cycles for information you can usually get to via a couple taps on the good ol' touchscreen. And I have no idea why, it may just be me thinking it improves battery life, but I turn airplane mode on, and when I need wireless access I leave airplane mode on and turn wireless itself on. For some odd reason I see improved battery life, and my assumption is that when airplane mode is on, there are system apps that are put to rest by seeing the tablet is in this state.
Anyways, I hope this info will be useful for people. Any questions, feel free to post or PM me. I am a full time college student so I may not respond right away!
Very nice! Thorough, clear, and I can find no faults in your advice that isn't personal choice.
Sent from my Galaxy Nexus using Tapatalk 2
pio_masaki said:
Very nice! Thorough, clear, and I can find no faults in your advice that isn't personal choice.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Thanks! Approval from you means a lot to me, cause you know what your doing more than I do!! lol
Good job, although it could better sectioning, make it easier to find stuff. Besides that, not bad!
Sent from my A100 using Tapatalk 2
das_webos_transformer said:
good job, although it could better sectioning, make it easier to find stuff. Besides that, not bad!
Sent from my a100 using tapatalk 2
i'm open to suggestions!
I wasn't quite sure how to break it down, like how to label a category and what would go into that category.
Sent via acer iconia a100 on cm10_build090212; godmachine v2.0 kernel, smooth, stable, fast
Click to expand...
Click to collapse
edit: Updated op organization
Nice tut. Should help out some to squeek out max performance.
A little more detail of how to freeze (paid version only), and disable startup apps, might help the novice.
Pretty much the way I run, with several different personal preferences.
Looks good. I especially like the list of apps that can be frozen. Just want to add that there are a few free apps (i.e..App Quarantine) that also freezes unwanted app.
Might be just me anal but the pictures attached shows up really big on the computer, taking up most of the screen and really distracting. I almost missed the blurp about setcpu profiles in between the pictures.
illego said:
Looks good. I especially like the list of apps that can be frozen. Just want to add that there are a few free apps (i.e..App Quarantine) that also freezes unwanted app.
Might be just me anal but the pictures attached shows up really big on the computer, taking up most of the screen and really distracting. I almost missed the blurp about setcpu profiles in between the pictures.
Click to expand...
Click to collapse
lol I KNOW!!!
I was wondering why they posted so big from my linked photobucket.
Maybe I should scale them down and re-upload.
[/u]Looking good!
Sent from my A100 using Tapatalk 2
das_webos_transformer said:
[/u]Looking good!
Sent from my A100 using Tapatalk 2
Click to expand...
Click to collapse
Thank you. Over the next few days I am going to add in a section about app compatibility and what runs on CM10. Games, media, tools, all of it.
If anyone wants to contribute information for this CM10 Tips guide, I will gladly fit it into the OP and credit your name.
Thanks for the support guys!
Bump
Sent via Acer Iconia A100 on CM10_Build090212; godmachine v2.0 kernel, Smooth, Stable, Fast
Tsk tsk
Sent from my A100 using xda premium
das_webos_transformer said:
Tsk tsk
Sent from my A100 using xda premium
Click to expand...
Click to collapse
Gotta give the thread some bump love for the noobs.
I keep having to bump pio's guide as well, if it goes to the bottom of the threads, its basically nonexistent as noobs don't know how to operate a basic search function. lol
justjackyl said:
Gotta give the thread some bump love for the noobs.
I keep having to bump pio's guide as well, if it goes to the bottom of the threads, its basically nonexistent as noobs don't know how to operate a basic search function. lol
Click to expand...
Click to collapse
hey im not a "noob" ,..(ok so maybe ) im thinnking of trying this on my backup (yes i have 2 a100s) ..the second one is the 16 gb version..is there anything i should be made aware of before i do this?..(and i have looked but where is the godmachine kernel)
mordeith said:
hey im not a "noob" ,..(ok so maybe ) im thinnking of trying this on my backup (yes i have 2 a100s) ..the second one is the 16 gb version..is there anything i should be made aware of before i do this?..(and i have looked but where is the godmachine kernel)
Click to expand...
Click to collapse
God machine aka linuxsociety. http://forum.xda-developers.com/showthread.php?t=1818924
Start here http://forum.xda-developers.com/showthread.php?t=1711125. Once you get cm10 loaded up follow this guide.
Romman0 said:
God machine aka linuxsociety. http://forum.xda-developers.com/showthread.php?t=1818924
Start here http://forum.xda-developers.com/showthread.php?t=1711125. Once you get cm10 loaded up follow this guide.
Click to expand...
Click to collapse
ahh you beat me to it
but I am going to add ROM and kernel links into the OP. Should have the first time.
I need to update this but I've been so busy with my stickied G2x Kernel thread! lol
I've all about abandoned SetCPU in favor of Antutu/No Frills (still testing) alongside with Android Tuner Pro <--- Which is flippin sweet on this tablet.
I may just be using it by itself as it can OC/UC/UV as well, than startup editing, build.prop modding, SysCtril modding somuch more. My tablet has been running smooth, and usually I just turn it off when not using as I could not get standby battery drain under control. I've just hit 18hours and still counting after using Android Tuner and I am still able to play all my HD games smoothly, meaning performance is not horribly hindered. I'll run a benchmark on it.
Great guide. used this on my desire s as well.
Hi jackyl, just wanted to say "great guide" I'm from the a500 forum and I feel guilty saying that i never knew you guys existed :shame: If it hadn't been for a 100 user posting his issues over our side I'd still be locked in ignorance!!!
I will link your guide and pio's in my flash guide if thats ok....there's some great info everyone should read imho
Keep up the fantastic work, happy tabbing
rgds dibb
dibb_nz said:
Hi jackyl, just wanted to say "great guide" I'm from the a500 forum and I feel guilty saying that i never knew you guys existed :shame: If it hadn't been for a 100 user posting his issues over our side I'd still be locked in ignorance!!!
I will link your guide and pio's in my flash guide if thats ok....there's some great info everyone should read imho
Keep up the fantastic work, happy tabbing
rgds dibb
Click to expand...
Click to collapse
Hey thanks for the support, feel free to link it.
:thumbup:
Sent from G2x, CM7 Weekly 1-1-13, Faux 054.
Just a note, added a link here in that guide thing I wrote as well.
This is not meant to be a complaining post, mostly I wanted to see if anyone else is having my problems.
I am currently running ParanoidAndroid 2.50 (CM10 based ROM) and I absolutely love how all AOSP ROMs look and feel. TouchWiz had some neat things, but it felt really bloated.
My problem is, multi-tasking on AOSP blows, really, really, really, BAD. I mean it's downright as bad as HTC One X's Sense UI multitasking. For whatever reason, I can never get my free RAM to dip below the 600 MB limit. Usually it hovers around 750 MB, and occasionally I can get it down to 650 MB.
I am not a huge multitasker, but I HATE HATE HATE app re-draws and reloads. This was the one nice thing about TouchWiz, it would keep my opened applications running until I was absolutely at the bottom of my free RAM (~150 MB). My frequently used applications almost never needed to be reloaded/redrawn. This is especially big for applications like Youtube and Browser/Firefox, as you lose everything that you had loaded otherwise.
I've tried spamming opening apps, and the most apps I seem to be able to have open at once is around 8-10 depending on the circumstances. As soon as I cross that threshold of open apps, my other opened apps start being force closed, and require a redraw/reload. This is an absolutely pitiful amount of apps, especially with the whopping 600-800 MB of free RAM that I usually have.
I also have the issue that sometimes even when I don't open a lot of apps, some of my apps like to force close for no reason after a few minutes of being idle. My MailDroid and Firefox apps seem to be extra susceptible to this random time based force close compared to GoSMS, which rarely closes after an inactive period of time.
I have tried multiple kernels, multiple ROMS, multiple governers and I/O schedulers, and I even tried zeppelinrox's V6 supercharger + multitask mods. Nothing I do seems to allow me to crack into that 600 MB of unused RAM. I am so flustered by this that I'm actually considering going back to TouchWiz.
Could anyone else provide me with some feedback with their multitasking app limits/free RAM? Is this a known CM10 issue?
TL : DR
-I can never get below around 600 MB (usually hovers around 700MB) of free RAM
-My running app limit seems to be 8-10 with about 6 widgets
-My apps seem to force close after short durations of inactivity
-I experienced NONE of these problems on TouchWiz
-Could someone post their numbers for some of these things, and is this a known problem for CM10?
Same problem here... I think most people like this problem though. Many like to see more free ram, but I prefer faster multitasking. My main concern is my downloads being closed and interrupted.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Yeah definitely a known issue on AOSP. Memory allocation issues I guess. I've never seen a dev comment on it, despite the fact it has been brought up several times. I suspect we won't get a fix until the JB sources are released for the d2.
Post your services.jar
If you used the windows tool to patch it, it may not have worked - I've made quite a few changes for greater compatibility since it's last update.
btw what are your minfree settings?
Did you do the aLogcat test?
zeppelinrox said:
Post your services.jar
If you used the windows tool to patch it, it may not have worked - I've made quite a few changes for greater compatibility since it's last update.
btw what are your minfree settings?
Did you do the aLogcat test?
Click to expand...
Click to collapse
Oh wow it's zeppelinrox! Hi
Yes, I used the Windows Jellyscream tool to patch my services.jar. The ICS Service Center in your script insists that it worked, but CM10 does not currently have a "Charge Only" or "No Action" mode when the cable is plugged in, I'm forced to mount the SD card(s). Your tool specifically says do not do that, but I don't really have a choice :/
My current MinFree values are:
8, 14, 40, 50, 60, 75
I have also tried the auto-calculated ones (which in my opinion leaves way too much free RAM theoretically):
8, 16, 325, 358, 390, 423
Both of them didn't seem to make a difference.
I have attached my services.jar to this post as well as requested.
As for aLogcat, I'm not sure what that is or how to do that
Hi
Well I can't open it up... is the file size correct?
Maybe it's an incomplete upload.
I assume that it's for ParanoidAndroid 2.50 so try upping it again since I haven't cracked one of those open yet lol
The service centre only looks at the supercharged launcher aspect and the windows exe isn't up to date for the multitasking mods.
I've actually just updated the ultimate jar script today... and also has an SGS3 specific edit
However it may be only for the stock rom.
The aLogcat test is described in the ultimate jar thread OP.
Weird, I'm also not able to open the one on my phone, that's kinda scary.
Ok, I'll give your new ultimate script a spin, and I'll look into the aLogcat thing as well and try to provide you some information.
Here's the services.jar file that was leftover in the Jellyscream directory (JellyScreamPatcherV6_0.9.0.6/framework/services.jar). I chose not to delete the temp files, so I'm guessing it's the same file.
WOOOOOOOOOOOOOOOOO!!!!
Wow you were right zeppelinrox, I tried out your Ultimate Jars script and BAM, my phone is hauling ass right now. Down to 234 MB of free RAM and none of my apps have force closed on me at the moment even after running ~20. Also, my list of cached apps is MASSIVE now, my RAM is finally being utilized!!!!
Time will tell if my apps auto-close after inactivity, but damn this is awesome, THANK YOU SO MUCH, you rock .
Hopefully the windows tool gets updated eventually so it's easier for people to do this, it was a bit tedious to figure it out haha xD
Edit:
My only question now is why oh why do the default AOSP settings suck so bad?
ChrisG683 said:
WOOOOOOOOOOOOOOOOO!!!!
Wow you were right zeppelinrox, I tried out your Ultimate Jars script and BAM, my phone is hauling ass right now. Down to 234 MB of free RAM and none of my apps have force closed on me at the moment even after running ~20. Also, my list of cached apps is MASSIVE now, my RAM is finally being utilized!!!!
Time will tell if my apps auto-close after inactivity, but damn this is awesome, THANK YOU SO MUCH, you rock .
Hopefully the windows tool gets updated eventually so it's easier for people to do this, it was a bit tedious to figure it out haha xD
Edit:
My only question now is why oh why do the default AOSP settings suck so bad?
Click to expand...
Click to collapse
I think that's to make me look good
I hope to have it automated somehow like the outdated ics webapp.
btw how did you decompile?
I'll try again when on the PC.
edit: ok that second one you posted opens up fine. I guess that's CM10?
It looks like CyanogenMod is following my lead... https://github.com/CyanogenMod/andr...mmit/9a8117c4f887c8b0df9cadb5d9aa7689a878752a
am: Allow more hidden apps on devices with lots of RAM
* If more than 1.5GB is present, allow up to 40 hidden apps. * Number is somewhat arbitrary, but was found to work well on D2. * Also look at the sys.mem.max_hidden_apps value if given.
Click to expand...
Click to collapse
Uh yeah... you get a 40 app limit only if you have 1.5GB of RAM - otherwise, you're STILL stuck at 15 hidden apps... lol
I had already seen the "sys.mem.max_hidden_apps" code in ProcessList.smali before the last script update - so that's already been bypassed to 70.
I just didn't know where that setting came from lol
So if you're on CM10, the Ultimate Jar Power Tools script that's currently available already fixes that.
Of course, "sys.mem.max_hidden_apps" was introduced after my mucking around
zeppelinrox said:
btw how did you decompile?
Click to expand...
Click to collapse
Hmm, I'm not sure what you are asking here, could you clarify?
zeppelinrox said:
I think that's to make me look good
I hope to have it automated somehow like the outdated ics webapp.
btw how did you decompile?
I'll try again when on the PC.
edit: ok that second one you posted opens up fine. I guess that's CM10?
It looks like CyanogenMod is following my lead... https://github.com/CyanogenMod/andr...mmit/9a8117c4f887c8b0df9cadb5d9aa7689a878752aUh yeah... you get a 40 app limit only if you have 1.5GB of RAM - otherwise, you're STILL stuck at 15 hidden apps... lol
I had already seen the "sys.mem.max_hidden_apps" code in ProcessList.smali before the last script update - so that's already been bypassed to 70.
I just didn't know where that setting came from lol
So if you're on CM10, the Ultimate Jar Power Tools script that's currently available already fixes that.
Of course, "sys.mem.max_hidden_apps" was introduced after my mucking around
Click to expand...
Click to collapse
hey zeppelinrox....
And to think, that I read some debates with users downplaying the usefulness of 2gb ram vs 1gb. When I was on my HD2 with Swap/Zram, I was using your script(s)...but at one point, I had OS AutoKilling disabled entirely (can't even remember how I did it) and was using a fairly complex Tasker profile(s) to Kill ALL if my memory ran down to a critical stage....all except apps that I put in an EXCEPTION list. So basically, I had MAX multitasking...and the use of all available memory unless I hit a critical threshold...and then, aside from those apps on the exception list, all other apps would get killed. To this day, I believe that Android should be built with an Exception list for power users similar to your Bullet Proof thing.
My Stock S3 rom and kernel seem to handle things pretty darn well. I use Go Launcher EX and experience zero redraws and my tests so far indicate that the OS has great multitasking behavior. I can open quite a few apps for a good amount of time. Eventually they get killed, but as you know, it's a bit unpredictable. When I last ran the memory down to about 250mb, which was very difficult to do even with large games, the OS hardly killed anything. It wasn't a scientific test but feel factor based. One of these days SOON, I need to play with your scripts again. Only reason I haven't with the s3...is because so far the stock setup is working really well.
ChrisG683 said:
Hmm, I'm not sure what you are asking here, could you clarify?
Click to expand...
Click to collapse
OH that's ok.
The second file you posted decompiled fine
themadproducer said:
hey zeppelinrox....
And to think, that I read some debates with users downplaying the usefulness of 2gb ram vs 1gb. When I was on my HD2 with Swap/Zram, I was using your script(s)...but at one point, I had OS AutoKilling disabled entirely (can't even remember how I did it) and was using a fairly complex Tasker profile(s) to Kill ALL if my memory ran down to a critical stage....all except apps that I put in an EXCEPTION list. So basically, I had MAX multitasking...and the use of all available memory unless I hit a critical threshold...and then, aside from those apps on the exception list, all other apps would get killed. To this day, I believe that Android should be built with an Exception list for power users similar to your Bullet Proof thing.
My Stock S3 rom and kernel seem to handle things pretty darn well. I use Go Launcher EX and experience zero redraws and my tests so far indicate that the OS has great multitasking behavior. I can open quite a few apps for a good amount of time. Eventually they get killed, but as you know, it's a bit unpredictable. When I last ran the memory down to about 250mb, which was very difficult to do even with large games, the OS hardly killed anything. It wasn't a scientific test but feel factor based. One of these days SOON, I need to play with your scripts again. Only reason I haven't with the s3...is because so far the stock setup is working really well.
Click to expand...
Click to collapse
Yes you were using dorimanx's trick to break the lowmemorykiller on HD2
He asked me to break it on ICS and above, which I did.
But that only lasted a day because I found another way to do it... boost number of running apps without breaking lowmemorykiller.
Needless to say, dorimanx got real happy lol.
See post 2 of the ultimate jar thread for more about that.
So yeah, you still have the app limit and lots of room for more multitasking since you can't get very low on ram.
I've added more mods to reduce the likelihood of apps closing on you. (Check the change log)
Sense users are ecstatic with the latest
Anyway, I'm sure that if you try it, you'll notice a difference - it's just a matter of you not knowing how much better it can be
What program are you using to put on the app kill exception list?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Deoxlar said:
What program are you using to put on the app kill exception list?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Deoxlar...are you asking me?
With the HD2, I had the OS rigged to NOT kill any apps EVER and used System Tuner Pro as my APP Killer with exceptions checked off. I used Tasker to determine the ram availability each time a window opened or changed, and Tasker would trigger STP when necessary.
But Zepplinrocks' V6 Supercharger as a very unique system for doing similar...but overall, it handles everything to do with ram management and better. Also, for some people's setup, it is a dramatic improvement...a FIX... a LIFE SAVER. (Basically the rom Devs are going to eventually slowly STEAL Zeps ideas. But we will not forget.
My old HD2 memory mngt system was an ALL or NOTHING workaround so it suffered in that regard.. The way my S3 with stock ICS is handling things right now is surprisingly good. I did a test last night opening as many apps as possible until I basically ran out of FREE ram. At that point, the OS was doing it's thing, killing another app or 2 so it could run the new app launched. Multitasking...or switching to newly launched apps and then returning to previously launched apps where they left off....worked near flawless and FAST on my i747m. When I woke up today, 3/4 of the apps were still in memory ready for resuming.
This is why I went from 2 years of OBSESSIVE flashing and tweaking....to using my new S3 with the Stock rom and about 1/100th of the tweaks. Super STABLE and not a slouch. I hope the upgrade to JB...well....is an UPGRADE. yadda yadda yadda...:good:
Hey, for shi.tz n giggles do that aLogcat test that I describe in the multitasking OP... I'd be interested to see what your max hidden app limit is
Install aLogcat, run as many apps as you can, run aLogcat and search for longer.
Most people get this before the mod...
{
"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"
}
The 16th hidden app gets killed because the limit is usually 15.
zeppelinrox said:
Hey, for shi.tz n giggles do that aLogcat test that I describe in the multitasking OP... I'd be interested to see what your max hidden app limit is
Install aLogcat, run as many apps as you can, run aLogcat and search for longer.
Most people get this before the mod...
The 16th hidden app gets killed because the limit is usually 15.
Click to expand...
Click to collapse
For you Zep, I do about any test you asked me to do! Respect! :good:
Stay tuned....possible depression, followed by possible "V6...light at the end of the tunnel".
themadproducer said:
For you Zep, I do about any test you asked me to do! Respect! :good:
Stay tuned....possible depression, followed by possible "V6...light at the end of the tunnel".
Click to expand...
Click to collapse
LOL thanks for the kind words man
zeppelinrox said:
LOL thanks for the kind words man
Click to expand...
Click to collapse
OK, I used System Tuner Pro's log and guess what....checked a dozen times....
hidden #51
Yup...and also using "free" in STP terminal, I have 115mb free close to 1.6gb used.
I cross referenced by reopening the apps and most of them were still in ram memory.
Actually, a few games I was testing almost 20hrs ago, were still in ram. That surprised me.
So these games/apps were not killed off by idle time auto killing.
This is why I haven't tried any CM or custom roms. This thing seems to be doing way better...then the forums would lead me to believe. I was FLASH happy with my HD2 and never quite satisfied but this thing is so much better...and mostly stock.
What do you think Zep...honestly, have you heard any similar reports?
UPDATE: now i am down to 83mb free...still rock solid smooth.
So, you're using the "ultimate jars" script in conjunction with which ROM? And did you use in conjunction with the supercharger script?
Just trying to understand exactly what is required to "fix" the multitasking issue.
themadproducer said:
OK, I used System Tuner Pro's log and guess what....checked a dozen times....
hidden #51
Yup...and also using "free" in STP terminal, I have 115mb free close to 1.6gb used.
I cross referenced by reopening the apps and most of them were still in ram memory.
Actually, a few games I was testing almost 20hrs ago, were still in ram. That surprised me.
So these games/apps were not killed off by idle time auto killing.
This is why I haven't tried any CM or custom roms. This thing seems to be doing way better...then the forums would lead me to believe. I was FLASH happy with my HD2 and never quite satisfied but this thing is so much better...and mostly stock.
What do you think Zep...honestly, have you heard any similar reports?
UPDATE: now i am down to 83mb free...still rock solid smooth.
Click to expand...
Click to collapse
Wow I've never heard of a stock rom having the app limit set to 50.
However when you type free in terminal, how much is system tuner reporting as free?
There is a difference because the free command in terminal is always very low whereas apps like system tuner/task managers always report free ram as "free ram + cached apps" which is a much bigger number.
Can you post a deodexed services.jar (it's probably odex tho since it's a stock rom) or at least the smali files?
The windows patcher should be able to decompile it.
If it's not sense I'd only have to look at ActivityManagerService.smali and ProcessList.smali.
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