Related
I could not find this on the Captivate Forum. I found this method on another forum referenced below. This has significantly increased the overall speed of my Captivate.
**REQUIRES ROOT**
**limits your App space to 130MB, which can possibly cause issues**
**Do NOT use with large number/size of apps**
**This should not be a permanent fix, but works until somethings else comes up**
**If you approach the size limit you will get errors and/or strange things**
Here is the original post. *READ THE THREADS!*
http://forum.xda-developers.com/showthread.php?t=727279 (Method 1 only)
-also-
http://android.modaco.com/content/s...298/got-the-stalling-problem-rooted-try-this/
Note: This method moves the app data from the SD space to the NAND space which significantly increased the speed of the phone , but PLEASE read the links and associated discussion. You are limited to 130MB app space on NAND, which can be limiting depending on which apps you use.
The following can be done using adb or using terminal emulator (available on the Market) without the adb commands
How to check how much app memory you are currently using:
Code:
adb shell
su
cd /data/data
busybox du -h|busybox grep M
How to apply Method 1:
Code:
adb shell
su
busybox cp -rp /data/data /dbdata
mv /data/data /data/data.bak
ln -s /dbdata/data /data/data
reboot
How to undo Method 1 (no loss):
Code:
adb shell
su
busybox cp -rp /dbdata/data /data/data.tmp
rm -r /data/data
mv /data/data.tmp /data/data
reboot
How to undo Method 1 (restore to point of application):
Code:
adb shell
su
rm /data/data
mv /data/data.bak /data/data
reboot
so are you working on the method 2? building a kernel to run app data on the ex-sd card method. this method is okay but has limitation.
for those who have alot of apps, i wouldn't bother. you phone will constantly have forceclose notification. however, if you do not have too many apps, it does make your phone smoother and faster. done the bench mark and brought it up about 100 points. not bad for a quick/temp fix.
but... still need a REAL fix. Mimocan who was the builder for the kernel for i9000 should be working on a kernel for us. Unless he is now into the new froyo bull crap. not worth my time right now. trying to run the 2.1 smoothest possible is the key for me.
does this method or method 2 fix the laggy issues in Dolphin HD browser and Touchdown Exchange?
I don't use Dolphin, but it made a MASSIVE difference in using Touchdown.
Running this currently on my Captivate flashed with the I9000 JM2 ROM w/ Captivate Kernel & SamSet 1.6 and I am getting a ~960 on quadrant. During the test you can see the I/O portion goes SIGNIFICANTLY faster. App load times also feel faster. Samset includes MCR Scripts to set this up for you.
Note: I tried to post links but since I am new to the forum I was blocked.
This worked wonders for Dolphin HD! Thanks!
Sent from my SAMSUNG-SGH-I897 using XDA App
I cannot get the Android SDK to install on my computer so can't use ADB. What Terminal emulation program do you recommend and how would I connect my phone to it?
Baldilocks said:
I cannot get the Android SDK to install on my computer so can't use ADB. What Terminal emulation program do you recommend and how would I connect my phone to it?
Click to expand...
Click to collapse
Terminal Emulator is available on the market
div3rg3nt said:
Running this currently on my Captivate flashed with the I9000 JM2 ROM w/ Captivate Kernel & SamSet 1.6 and I am getting a ~960 on quadrant. During the test you can see the I/O portion goes SIGNIFICANTLY faster. App load times also feel faster. Samset includes MCR Scripts to set this up for you.
Note: I tried to post links but since I am new to the forum I was blocked.
Click to expand...
Click to collapse
replace http with hxxp.
Do you have any downsides with flashing with the i9000 firmware? are you still limited to 130mb of app space?
If you read the modaco post Paul states that the 130 mb will take awhile to fill because the apps themselves are not stored but the data is.
"On the plus side, we're only moving data not the apps themselves, so filling up 130MB will take a while."
So that is good news I think I am going to try it. Thanks for the guy that posted how to check how much dbdata you have.
Works for me. Getting 980-1003 on Quadrant scores.
Just tried this. My captivate has been rather laggy and slow, specifically with apps such as twitter, facebook and pandora. I've been debating returning the phone and going back to iphone 4, but after the fix, it seems like a jump from an iphone 3g to a 4. Much snappier, but seeing that the custom kernel can yield 1500+ q scores, I'm actually not only hopeful, but excited about the future of the device.
Sent from my SAMSUNG-SGH-I897 using XDA App
too bad i cant apply the fix since i have 120 apps installed and they take up more than 130 MBs
As the previous poster said, its the application data space that is limited, not the space for actual apps. You can have a lot of apps installed, just not too many open and caching data.
Sent from my SAMSUNG-SGH-I897 using XDA App
I got a 973 running the stock Galaxy S I9000 and this fix. Not bad
Hmm I might have to give this a shot when I get home from work. Are most of you using this fix running stock Captivate rom?
Quadrant went from about 895 to 967. I can tell it's quicker. When I used to drag and drop apps and stuff there would be a lag, no lag now. I'm using a stock rom. This thing is going to be a monster once the modaco speed fix becomes available.
Ok before I did this I got a Quad score of 901. I checked my app data and I was at 120mb so just to make sure I deleted some apps I've never used and got down to 100mb. I did this (easy as pie BTW) and I got a Quad score of 951, but here's the deal. It booted completely from powered on to finishing "Scanning media" about x3 faster AND it was actually usable during "Scanning media", I don't know about anyone else but when it usually did that the phone was basically unusable during this period. So IMO even though it only gained like 50 points on Quad this thing is WAY faster with no lag that I can see zooming around between apps/launching them and such. Not a perma fix but this is a great band-aid till a real fix is found THANK YOU!!!!
Hmmm the more i read this thread the more i want to try this and according to the original poster its just as easy to undo as it is to set up so i guess there's nothing to loose.
Sent from my HTC Liberty using XDA App
well.. least we are takin steps in the right direction. i hear the kernal patch boosts your quadrant scores to about 1700.. so yeah. there's that to look forward to now.
NEW THREAD HERE
http://forum.xda-developers.com/showthread.php?t=765822
THIS IS NOW AVAILABLE IN EXT2, EXT3, AND EXT4 VARIATES(DOES NOT REQUIRE CUSTOM KERNEL!)
IF YOU ARE USING JH2/JH3 FIRMWARE, READ THIS POST, IT IS VERY VERY VERY IMPORTANT:
http://forum.xda-developers.com/showpost.php?p=7650658&postcount=312
The reason this step is important is that the JH2 firmware is a test build, and as a test build it has GPS logging enabled... this uses an absolutely ludicrous amount of storage space- and the real kicker? It uses the space OUTSIDE of this fix, meaning your phone will encounter low space warnings very quickly if not instantly upon applying the fix!
THIS NOTE IS FOR EVERYONE. THESE FIXES WORK BETTER FROM A FRESH FLASH. THEY *CAN* WORK WITHOUT A CLEAN FLASH BUT REALIZE THAT YOU ARE POTENTIALLY PUTTING YOUR DATA AT RISK!
What this does (Shamelessly stolen from RyanAZ's OP)
Creates a VIRTUAL EXT2 filesystem inside the stock RFS filesystem on the internal SD card, with a 4KB block size. This means that this lag fix creates a buffer between the real filesystem and the android system. This buffer should reduce the amount of disk I/O required for all operations by utilizing EXT2 buffering, as well as not writing file access times to disk, etc.
PROS
Doesn't rely on external SD
Easy to do
Reverse-able
Real, noticeable performance increases outside of Quadrant (Seriously don't pay attention to Quadrant, but if that's what you care about this will make your pants tighter)
CONS
Uses EXT2 file system which is non-journaled and CAN become corrupted, frequent backups are strongly recommended! (2.2 Implements error checking every 30 mounts)
It's also up for debate as to whether this adds extra strain on your internal memory.
1.0 SECTION WILL FOLLOW 2.0 STUFF
AS WITH ANY FIX: READ THE INFO, KNOW WHAT YOU'RE DOING, AND UNDERSTAND POTENTIAL CONSEQUENCES!
LINKS TO GET THE GOODS BELOW!!
The RyanZA version that does EXT2 is Available at the thread linked below
http://forum.xda-developers.com/showthread.php?t=751864
RyanZA has put out an APK version of the fix for people less comfortable doing the update.zip or batch file methods! (This is the V1 lagfix, so for people having issues with the newer fixes this one might work for you!)
TEMPORARILY DOWN UNTIL VERSION 2.3
http://forum.xda-developers.com/showthread.php?t=760571
There is also an update.zip version that does EXT2, EXT3 (1500 Quadrant), or EXT4 (1800 quadrant) versions thanks to Tayutama! I've tested this to work on JH2, and JM5 firmwares! There is also a special version for Captivate JH2 (It also works for JH3) that fixes the GPS Log issues so no need to edit the XML's yourself!
http://forum.xda-developers.com/showpost.php?p=7632258&postcount=208
praveer01 threw up a handy writeup for those of you running Unbuntu or any other Linux system:
http://forum.xda-developers.com/showpost.php?p=7671640&postcount=583
READ THE INSTRUCTIONS AND REMEMBER THIS IS *VERY* BETA, NEITHER RYANZA OR MYSELF WILL TAKE RESPONSIBILITY FOR MELTING YOUR DEVICES OR KILLING YOUR DOG IF THIS FAILS. That said, this thread has been very good about helping people who borked their Captivates with 1.0
Here's the reasons you'd want to do this:
Benefits over version 1
1.7GB of application data available, with no data loss. (Up from < 1GB)
e2fsck of the EXT2 partition on each boot. (To scan and fix corruption!)
Correct busybox version included! YES! (Because no one can get it right =P)
/app directory included in the fix for faster application installs.
Mounts instead of symlinks for extra performance as OS does less work (about 100 or so more quadrant).
2.3 Changelog
/dbdata has been removed. This fixes maps issues.
/app-private is now a symlink to /app/app-private. This fixes paid apps issues.
2.2 Changelog
/app-private is included
A second EXT2 partition is created in fast /dbdata storage. /dbdata/databases are moved inside here for increased speed in applications that use it. (System apps mostly, I think)
Proper parameters for e2fsck.
0% space reserved in the EXT2.
EXT2 partition reduced from 1.7GB to 1.5GB to allow more space for captivate users.
Running from a stock install of JH2 I'm currently getting 2300 quadrant scores with ALL AT&T BLOATWARE AND TW ENABLED!
IF YOU'RE NEW TO THIS KIND OF THING, OR ARE WORRIED ABOUT POSSIBLY HAVING TO REFLASH YOUR PHONE, YOU PROBABLY SHOULD WAIT A LITTLE WHILE FOR MORE PEOPLE TO TEST THIS!
___________________________________________________________________________
Found this over in the i9000 forums and tested it myself- I'm getting 2100+ quadrants scores with the stock Captivate kernel and it doesn't hang up on the I/O portion like all the other fixes... in addition you don't require an SDcard for this to work.
Original thread:
http://forum.xda-developers.com/showthread.php?t=748596
One of the folks over there created a one-click lagfixer and it DOES work for the Captivate:
http://forum.xda-developers.com/showthread.php?t=749495
FOR PEOPLE WHO DONT WANT TO READ THE ORIGINAL THREAD
This fix creates a 1GB file formatted in EXT2 and moves all of your apps, data, dbdata into it which DRASTICALLY improves I/O performance. One advisory SHUT YOUR PHONE DOWN PROPERLY, this means no yanking the battery out. Due to it being EXT2, non graceful shutdowns CAN cause corruption.
Edit: No wake up lag either- not sure if that's due to using a non-modded kernel or because the ext2 file is located on the internal memory.
Edit 2: Make *SURE* before attempting this that you have Busybox 1.17.1 or the boot animation script calls won't work!
Link to Busybox 1.17.1
http://forum.xda-developers.com/showpost.php?p=7574130&postcount=229
DO NOT UPGRADE BUSYBOX TO 1.18! 1.18 REMOVES MAKEFS WHICH IS NECESSARY FOR THIS PROCESS
Edit 3: I haven't used the stock Captivate ROM for a while, but this feels quite fast- Also worth noting that this SHOULD work with any ROM- including i9000, I might test that later but I'm enjoying having functioning haptic feedback. 2200 Quadrant with Shootme and market running! Since seeing is believing I've thrown in a screen cap.
Confirmed working with JM5 ROM
IF YOU USE A MAC OR JUST CAN'T GET ADB TO WORK THIS FIX CAN BE PERFORMED WITHOUT A PC- SEE THE POST BELOW:
http://forum.xda-developers.com/showpost.php?p=7583565&postcount=116
Ha! it worked thanks dude you should rename this thread with brackets. " [Fix][Lag] Alternative by {author name} - alpha " .. so it can gain more attention. Just we need two more fixes GPS and my attenna issues then i'm good with my captivate.
[edit]omg my phone is flying see this is how my phone should have been out the box it flies!
rebooting from this now. I should not that I had to run the shell script manually because it kept not prompting me for SU...? No biggy though.
Will test, can't post screen from work though.
Edit: running quadrant....
Edit: ... *thud* 1961, 2237 ( FB, gmail, etc were running & syncing in background last time!)
mykenyc said:
Ha! it worked thanks dude you should rename this thread with brackets. " [Fix][Lag] Alternative by {author name} - alpha " .. so it can gain more attention. Just we need two more fixes GPS and my attenna issues then i'm good with my captivate.
[edit]omg my phone is flying see this is how my phone should have been out the box it flies!
Click to expand...
Click to collapse
Title change done!
Glad this is working for you guys, I've tried every fix so far and this one is MILES ahead of the others in terms of real world improvement (At least for me).
Zilch25 said:
Title change done!
Glad this is working for you guys, I've tried every fix so far and this one is MILES ahead of the others in terms of real world improvement (At least for me).
Click to expand...
Click to collapse
I agree! waking up this morning in fear of being fired from my job, this made my day a little lol.
Besides downloading the .zip file, do i need anything else?
Also, i am assuming we install this by booting into recovery mode?
Thanks
Sent from my SAMSUNG-SGH-I897 using XDA App
LockeCPM4 said:
Besides downloading the .zip file, do i need anything else?
Also, i am assuming we install this by booting into recovery mode?
Thanks
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Nope just run lagfixme.bat this in the zip file, run and leave your phone screen on so you can see the root request permission.
LockeCPM4 said:
Besides downloading the .zip file, do i need anything else?
Also, i am assuming we install this by booting into recovery mode?
Thanks
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Nope, you don't need anything else. Also nope, no recovery mode shenanigans, just unzip the file, turn on debugging mode on your phone, plug her in, and run the batch file!
Also you MUST undo any prior lag fix
Sent from my SAMSUNG-SGH-I897 using XDA App
again, those high quadrant scores mean nothing unless you get no lag in real world testing. Such tests can be done in the following apps: Dolphin HD browser, facebook, twitter, touchdown, k-9 email
All common applications that have serious lag on the SGS. Assuming that this method does fix I/O problems (Especially the I/O quadrant tests), there should be no lag in those apps. Anyone try?
I noticed this in the original thread:
EDIT3 09 aug 0033HKT:
it's not for the benchmark only, instead, it has very good effects on ur phone's io
Click to expand...
Click to collapse
Sounds good, I'll give it a try
andy2na said:
again, those high quadrant scores mean nothing unless you get no lag in the following apps: Dolphin HD browser, facebook, twitter, touchdown, k-9 email
All common applications that have serious lag on the SGS. Assuming that this method does fix I/O problems (Especially the I/O quadrant tests), there should be no lag in those apps. Anyone try?
Click to expand...
Click to collapse
I know you have your reservations about these fixes, and you've been very vocal about your opinions on the matter. I happen to agree with you on most points, but as someone who has tried all of these, I can tell you this doesn't feel like the placebo effect. I'll install DolphinHD and toy with it, but everything I've messed with so far seems much snappier. Feel free to try it yourself, it literally takes less than 5 minutes to install, and is completely reverse able.
Edit: So far with dolphin HD things feel snappy, the only exception is pages absolutely laden with flash lite ads... but that's not really an I/O issue, if you've got any particular web site recommendations I'd be glad to check them out and let you know my mileage
So far so good, I recently erased my phone (130mb lag fix not big enough). And this is working wonderfully so far, dolphon browser HD(my favorite browser) works very fast. So far so good, I'll report back when I've tried it for the whole day.
Zilch25 said:
I know you have your reservations about these fixes, and you've been very vocal about your opinions on the matter. I happen to agree with you on most points, but as someone who has tried all of these, I can tell you this doesn't feel like the placebo effect. I'll install DolphinHD and toy with it, but everything I've messed with so far seems much snappier. Feel free to try it yourself, it literally takes less than 5 minutes to install, and is completely reverse able.
Edit: So far with dolphin HD things feel snappy, the only exception is pages absolutely laden with flash lite ads... but that's not really an I/O issue, if you've got any particular web site recommendations I'd be glad to check them out and let you know my mileage
Click to expand...
Click to collapse
Thanks! I'll give it a try as I don't like being tied down to 130mb for application storage using the NAND fix.
Basic usage should be snappy:
- opening\closing\switching tabs
- scrolling with the volume buttons
- pinch zooming
- loading multiple pages
On stock, and even mimocan's fix, it would lag horrible to the point of unusability.
The only way to make it run smoothly and quickly was to move all your /data/ to the /dbdata/ on the NAND (but limited to 130mb of app space)
I guess my install question wasnt answered. You said run the .BAT file, do i run it on my pc? And what software on the pc side must i have installed?
Thanks for helping a noob!
Sent from my SAMSUNG-SGH-I897 using XDA App
Zilch25 said:
I know you have your reservations about these fixes, and you've been very vocal about your opinions on the matter. I happen to agree with you on most points, but as someone who has tried all of these, I can tell you this doesn't feel like the placebo effect. I'll install DolphinHD and toy with it, but everything I've messed with so far seems much snappier. Feel free to try it yourself, it literally takes less than 5 minutes to install, and is completely reverse able.
Edit: So far with dolphin HD things feel snappy, the only exception is pages absolutely laden with flash lite ads... but that's not really an I/O issue, if you've got any particular web site recommendations I'd be glad to check them out and let you know my mileage
Click to expand...
Click to collapse
Tested:
Gmail, FB (official), GVoice, messaging, TWC, stock browser, andoku (yeah, I can SEE it faster. and thats a simple app!)
LockeCPM4 said:
I guess my install question wasnt answered. You said run the .BAT file, do i run it on my pc? And what software on the pc side must i have installed?
Thanks for helping a noob!
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Plug it into your pc making sure the USB debugging is on. Download the zip file, extract all of it. Run the Lagfixme.bat and make sure you leave the phone screen on (tap it if low time out) to accept the super user permission request. After that it will finish on it's own. Just reboot the phone by shutting it down. The zip file contains all the necessary files.
Edit: and make sure your phone is rooted / has the drivers installed!
LockeCPM4 said:
I guess my install question wasnt answered. You said run the .BAT file, do i run it on my pc? And what software on the pc side must i have installed?
Thanks for helping a noob!
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
The zip file actually contains a copy of the adb as needed, so other than the drivers to be able to connect via USB Debugging, nada.
All I can say is wow. Definitely not placebo. Certain apps used to take forever to initialize (i.e. Facebook, Market). They now start up almost instantly.
I have not tried any of the other "fixes" because to me they break more than they fix. I don't want to use my external SD in a way that makes it non-swappable and I don't want to be restricted to 130mb for apps. This fix is the best so far. I'm guessing it may not be necessary once we have Froyo (double the RAM) but it does the trick for now.
Seemingly didn't work for me, my Quadrant scores are still sitting at 948. I'm on the stock ROM, and undid the previous speed fix I had.
LockeCPM4 said:
I guess my install question wasnt answered. You said run the .BAT file, do i run it on my pc? And what software on the pc side must i have installed?
Thanks for helping a noob!
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
It was answered:
You need root
Download zip file- unzip it.
Put phone into debug mode and plug in USB
run the included .bat file from the zip file and it will do the rest for you.
It has it's own adb.exe but you might need to install the SDK if you haven't already. That's it though.
edit: Most devs have added this to their roms already so don't be surprised if you find it in the build.prop already.
So I saw this mentioned in a tweet by the dev for Launcher Pro:
To get really nice smooth scrolling on your Eris add the following line to your build.prop:
Code:
windowsmgr.max_events_per_sec=60
To add it into your build.prop follow these steps using your adb tool:
Code:
adb remount
adb pull /system/build.prop
(Go into your tools folder and open it with notepad. Add the line I posted and save.)
Code:
adb push build.prop /system/build.prop
Reboot into recovery, wipe dalvik cache, and start the phone up. This can a while to boot up right after because of the wiping dalvik cache. You should notice that scrolling on your phone is much smoother.
I AM NOT RESPONSIBLE FOR YOUR PHONE. IF YOU BREAK YOUR PHONE DOING THIS (it's unlikely!) I AM SORRY BUT I CAN'T HELP YOU.
I currently have mine set to 70 and it's not any noticeably smoother than 60 that I can tell but it is stable so if anyone wants to try bumping it up to 90 or 120 feel free.
Thanks for the advice last night on this Hungry Man. I did this and notice a definite difference in the scrolling. I moved my Launcher pro scrolling speed down now from 100 to 45 because I no longer need it high with this fix. I also didn't wipe Davlik after pushing, but the file is in there when looking with Estrong file manager and the scrolling is definitely better now..
Thanks again..
Glad I could help! Wiping the Dalvik cache isn't really necessary I suppose, I just find it's good practice after doing anything to your build.prop to avoid possible glitches.
any reason why this wouldnt work on other devices?
Where exactly do I add this line? Thanks.
dev/null/ said:
Where exactly do I add this line? Thanks.
Click to expand...
Click to collapse
Just add it to the end of build.prop file.
Worked, I thank you for the reply and to the OP for the info.
Twidroyd
Could I get someone to fire up Twidroyd after applying this patch? Seems to cause super-heavy lag+slowdown in scrolling, but it appears that Twidroyd is the main offender.
This seems to work just fine for me. I guess it seems smoother... I can't really tell. Definitely not laggier.
Wouldn't you be able to open the build prop in something like Root Explorer's text editor and get the same result? I'm just not around my regular computer with adb setup... Thanks.
es0tericcha0s said:
Wouldn't you be able to open the build prop in something like Root Explorer's text editor and get the same result? I'm just not around my regular computer with adb setup... Thanks.
Click to expand...
Click to collapse
yes you can do this also.
Sent from my FroyoEris using XDA App
Implemented this tweak in my latest ROM and it definitely makes a difference
Sent from my nonsensikal froyo
I tried obtaining access through Root Explorer and it says that build.prop is read only?
drtchocky said:
I tried obtaining access through Root Explorer and it says that build.prop is read only?
Click to expand...
Click to collapse
You have to remember to make the directory R/W at the top of the screen.
Can't really tell if it made a difference. Has anyone experimented with setting the number even higher?
EDIT: Upon further review, it seems to have made my scrolling slightly smoother but also more likely to 'hitch'
Yeah, I think this is what I was seeing in Twidroyd. Scrolling is smoother in a list you've already scrolled through, but will stutter as it loads new table cells (a guess on my part, but it seems to make sense.)
Izeltokatl said:
You have to remember to make the directory R/W at the top of the screen.
Click to expand...
Click to collapse
Thanks! Rebooting now....
I think it's likely that if you aren't overclocking your phone may not be able to handle the extra load. If you aren't overclocking your phone or you're usually on a low cpu setting try chaing to 50. Anything above 35 will increase the smoothness, though not to the same extent. I don't suggest passing 60, I'm at 70 and the differences are negligable.
As for the lag and stutters, I haven't experienced that.
I did it. Didn't break anything, but didn't really seem to change anything either.
I have seen a huge difference in smoothness in screen scrolling as well as app drawer. I have large amt of apps and app drawer flies. One thing though I do not have a space before or after the equal sign on my line. Some of you who aren't seeing a huge difference take the spaces out and see if anything changes.
Since Sony Xperia X10 is now running on 2.1, topics related to 1.6 is not mentioned here.
This thread are created based on compilation of other threads related to optimization, and meant as an entry point for user interested in optimization.
Understanding your Android
Just to put something short, so we can understand our Android and some points related to optimization better.
Android is an open source operating system owned by Google that is maintained by Android Open Source Project (AOSP). The operating system is based on modified Linux kernel, where most of the application is written in Java language and running on DalvikJVM.
Android do things differently than old generation OS like Symbian, and below is the explanation related to performance.
Unlike Symbian, Android designed to have as many as application loaded and running in the OS, it maintain list of least used application that will be unloaded when a requests for more memory is made when the free OS memory is already low.
These are the nature of JVM, where allocation and deallocation of memory is managed by garbage collector as doing things in bulk is faster then working with small chunks. So you don't have to be alarmed when you open a memory viewer application and see your Android is running on low memory. Freeing RAM with task killer is only momentarily, as you uses the phone again, the free memory will goes down again.
Android phones stores system application, data and files internally in NAND flash area and stores user data in internal memory storage or external storage such as SD cards. This memory is different than your operating sytem memory.
Operating system memory is memory allocated for the kernel, native application and most application you download from market. Installing a lot of application will not directly reduce free RAM, nor uninstalling or removing files will increase free RAM directly. Action such as removing ringtones, wallpaper and even Sony PC Companion ISO will not free your RAM
In general there are two type of android application. One is a standalone application that only run if you open the application, and the other one is running even you haven't open the application which called service.
By design, guideline and suggested practice, application should not continue to run lengthy processing when it get pushed to background via home button, back button or switching to other application; properly build application will just go idle. Which means you should be less paranoid about application eating you processing power.
But service is meant to run lengthy operation as they don't have user interface and runs in background. Some service meanth for pushing or pulling data from internet, reading your files and do processing like playing songs, or just doing something then update the widget just to make you happy. Unnecessary services are the things that you should be aiming if you want to optimize your Android.
General FAQ about Optimizing Sony Xperia X10 2.1
I just updated to 2.1 and my phone really feel slower than 1.6
Since you had been using 1.6 for quite some time, your SD card should have quite a lot of photo and media. Just after you updated to 2.1, and add your Google and maybe Facebook account, the new Face Recognition service is actually already starting to scans all your photo, then when your Google and Facebook contact arrived, it will try it best to match photo and contact. This new Face Recognition really kicks hard in your processor, then after a while your phone will be as fast and even better than old stock 1.6.
I still feel that the phone is slow, is there any simple and quick way to optimize
The simple and quick to optimize your phone instantly is by changing the 2.1 dalvikvm to JIT capable dalvikjvm. You can read and apply them by reading the thread referred below, but before you do that open the below link in background tab and please do read more first.
Android 2.1 OPTIMISER V002 by Jerpelea
2.1 Customizer v0.99.1 by ttxdragon
Both optimizer contains script that will erase your "junk/unused" application from your phone, be sure to read them first before executing. My suggestion is you apply JIT modification first, before going optimizing by remove your "junk/unused" application.
Please do remember that you have to Root your X10 first.
How to root the phone
You can root the phone using methods below.
OneClick z4root Android Application
SuperOneClick Windows Application
Is [INSERT APP NAME] here is save to remove?
By removing unused application, you will gain certain amount of performance gain. Below are the links with app list.
2.1 Customizer v0.99.1 by ttxdragon
Official List of Apps that Can be Removed from a 2.1 x10 by exekias
And still a lot more in other Sony Ericsson X10 forum section but those two is quite complete
And in case you forgot to make backup you can go to
2.1 System Apps - In Case You've Deleted Them by XperiaX10iUser
After doing all that my Quadrant Benchmark is still low
You should run Quadrant as least two or three time or until you get best score, the first one usually yield low score, because a lot of memory allocation process to Quadrant happening during the first run.
Tuning Utilities
Memory Usage - Application to see how much memory used by your application and services
Advanced Task Manager - Application to see is your application running on foreground, background or idle and its memory usage
Quadrant Standard - General benchmarking tools to see if your changes make improvement
Linpack - Processor benchmarking
Titanium Backup Pro - Back up application, the paid version can freeze your app rather then uninstalling it.
Fine Tuning Guide
About Widget, Application shortcut and Live Wallpaper
Even though widgets looks really good in your phone, some widgets required simple periodic process for updating its display, some have a full blown service running to support it. A very instant example that you can see in your phone is the Power Control widget and the new Status Switch widget.
Power Control widget update triggered by configuration change such as wifi on and off, while Status Switch widget which have a battery level is triggered by a running service. Just put Status Switch widget then go to Settings -> Application -> Running Services. Then you will see there a Status Switch Update service running in background to update the battery level.
By selectively put widgets on your home screen, you can gain extra processing and memory. Timescape widget is even worse, it have three service running to support it.
Application shortcuts also uses extra memory in your home screen app and your home screen app is usually system persistent, reducing number of shortcut will give extra RAM and reducing the required rendering process during scroll.
Live Wallpaper just as the name said looks really nice and require extra memory and process of course.
Tuning via build.prop
Some value can be added and modified into build to increase the performance of X10.
dalvik.vm.heapsize=32m
This will change the maximum memory size per application. If you decrease the value, smaller application starts faster, but big application like games will prone to crash, if you increase the value too much, smaller application takes longer to start, but big application will extra gain benefit from less garbage collecting.
Reference: Test: How changing the max amount of memory per VM Heap can effect your ROM (Cyanogen)
windowsmgr.max_events_per_sec=60
This will change the maximum number of touch screen gesture events per second, the bigger the value, the smoother the scrolling will be
There still some more build.prop tweaks that you can do, but not all of them will be processed by X10 as each device behave differently.
reservation for more article to go
Nice clean guide, should help newcomers. Good work!
synlar said:
Nice clean guide, should help newcomers. Good work!
Click to expand...
Click to collapse
Thanks, but i am quite depressed after reading it my self and found that i make a lot of typo. Had to revise and revise again.. lol.
Nice piece of work there Xeviro..
Can you post your build.prop please i cant find the windowsmgr.max_events_per_sec=60 one in mine.
Wolfbreak said:
Can you post your build.prop please i cant find the windowsmgr.max_events_per_sec=60 one in mine.
Click to expand...
Click to collapse
That one you add by your self to you build.prop. If you look further in google, there still a lot of other build properties that you can set to Android.
There is another way to add and test build.prop instantly by using adb shell command "setprop key value" and "getprop key". Some property will take effect immediately, some require you to reboot.
How do you prove that the windowsmgr.max_events_per_sec=60 actually works? After applying that I tried input benchmark and it still showed 33hz.
ooidort said:
How do you prove that the windowsmgr.max_events_per_sec=60 actually works? After applying that I tried input benchmark and it still showed 33hz.
Click to expand...
Click to collapse
Ok, i just checked, that for this build.prop property to take effect, you need to reboot the device first. I just test on my, giving 10 and 200 in value. With 10, the input benchmark showing less then 20hz most of the time, while with 200 it gives me 40hz+.
Also you can see if you scroll the app list with 10 and 200 value, you can see the difference.
xeviro said:
Ok, i just checked, that for this build.prop property to take effect, you need to reboot the device first. I just test on my, giving 10 and 200 in value. With 10, the input benchmark showing less then 20hz most of the time, while with 200 it gives me 40hz+.
Also you can see if you scroll the app list with 10 and 200 value, you can see the difference.
Click to expand...
Click to collapse
I definitely notice the difference between 10 and 200, but it still doesn't go above 33hz... Maybe it's the framerate cap doing it's thing?
xeviro said:
Thanks, but i am quite depressed after reading it my self and found that i make a lot of typo. Had to revise and revise again.. lol.
Click to expand...
Click to collapse
Good write up! I was actually going to say something about the typos/errors, because I'm a jerk, but, you noticed them too, so I feel satisfied.
I hope people will read your little intro about RAM and realize a task killer's real purpose is to kill rogue services that kill battery.
xeviro said:
That one you add by your self to you build.prop. If you look further in google, there still a lot of other build properties that you can set to Android.
There is another way to add and test build.prop instantly by using adb shell command "setprop key value" and "getprop key". Some property will take effect immediately, some require you to reboot.
Click to expand...
Click to collapse
But where do i need them to add? At Beginning or at End or Middle?
iead1 said:
Good write up! I was actually going to say something about the typos/errors, because I'm a jerk, but, you noticed them too, so I feel satisfied.
I hope people will read your little intro about RAM and realize a task killer's real purpose is to kill rogue services that kill battery.
Click to expand...
Click to collapse
Please forgive my typo and grammars, i life in country where people simplify their way of communication. I cannot talk proper now. hahaha
Wolfbreak said:
But where do i need them to add? At Beginning or at End or Middle?
Click to expand...
Click to collapse
Anywhere
xeviro said:
Please forgive my typo and grammars, i life in country where people simplify their way of communication. I cannot talk proper now. hahaha
Anywhere
Click to expand...
Click to collapse
If i add this to the end of my build.prop my phone does not accept SIM unlock code anymore .... ??
EDIT: Strange, second time it worked ... btw. what is the default value ?
Ive added dalvik.vm.heapsize=32m to see what diff it will make and well..
wow.. it killed my phone.
It will show sony ericsson on the screen when you turn it on and just stay there!
So yeah... how can i fix this?
It's bricked, you'll need to reflash the software!
:-(
OP- Great thread, thank you!
Post on my Rooted 2.1 X10i using Tapatalk Pro and Swype
Yeah i knida noticed...
fixed now but im not trying that heapsize thing again..
Anyone here have the original/untouched nordic build.prop? I'm really appreciate it if you share it here. ^_^
Sent from my Xperia X10i (2.1 and rooted) using XDA app
Seansmit17 said:
Ive added dalvik.vm.heapsize=32m to see what diff it will make and well..
wow.. it killed my phone.
It will show sony ericsson on the screen when you turn it on and just stay there!
So yeah... how can i fix this?
Click to expand...
Click to collapse
Seansmit17 said:
Yeah i knida noticed...
fixed now but im not trying that heapsize thing again..
Click to expand...
Click to collapse
Its working correctly in my phone, and this heapsize settings is the most common one in android modding. you go check google and see the results.
I also attached build.prop from my phone.
So the dev section here has been active recently with some high quality work, and I am looking to add to the fun
**SEE POST 2 FOR CHANGE LOG**
***VERY IMPORTANT IF YOU ARE GOING TO USE THIS MOD, you need to navigate to the /system/etc folder on your device, and rename the file "init.lge.zramswap.sh" to "init.lge.zramswap.sh.bak" so it does not run at boot.
This is a step by step instruction on how to replace the /system/etc/init.qcom.post_boot.sh file for the LG V10. Be it known, however, that this instruction (and file) can be used with any device running the Snapdragon 808 SoC combo.
What does this do?
Simple. It turns your device into an even more efficient powerhouse. Here are is a list of everything done:
-Interactive Governor tuning for performance and better battery life, a quick description of what I did...
-low load, quick response, low frequency
-high load, quick response, higher frequency
-modified input boost settings for Interactive
-Adjusted GPU target load values
-Switched IO scheduler to noop, and tuned accordingly
-Adjusted minfree values (RAM management, it is a little more multi-tasking friendly)
-Adjusted VM parameters - swappiness, dirty ratios, cache pressure, centisec values, etc (again to complement multi-tasking... your data will hang out a little bit more before being written to disk, but house cleaning won't happen all at once, so there is still good performance and your system won't bog down while it is flushing the toilet)
-DISABLED zRAM!!! - I have no idea why a device with 4 GB of RAM has zRAM enabled. This is purely a waste of CPU cycles and other system resources. You want physical memory, not compressed memory.
-Changed congestion algorithm to cubic (better network performance... assuming the network bandwidth is already there
-Cleaned up the shell file and fixed some errors.
-More to come!
How to do this, we'll just get right to it.
Download this app https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en
Download this file https://drive.google.com/open?id=0BzM9W6qUvx-gcm1SVDhsTDVWZ3M
And while you are here, check this out, decide which one you want.
http://forum.xda-developers.com/showpost.php?p=66792862&postcount=109
Very important you put the file on the root of your INTERNAL SDCARD!!!
Do not forget to do this.
After you do that, open terminal emulator, and type the following commands in the order they are presented (I would highly recommend just copying them from this post and switching back and forth between your browser and the terminal app):
Code:
su
Code:
cd /
Code:
mount -o remount,rw /system
Code:
cd /system/etc
Code:
rm init.qcom.post_boot.sh
Code:
cd /sdcard
Code:
mv init.qcom.post_boot.sh /system/etc
Code:
chmod 0644 /system/etc/init.qcom.post_boot.sh
Double check the file has been replaced with a file explorer of some sort, double check permissions, then reboot. Good to go.
Some of this stuff explained http://forum.xda-developers.com/tmo...nux-virtual-machine-explained-part-1-t3386956
CHANGE LOG***
May 1, 2017
-Pretty major overhaul of the file. I've done some stuff on the Axon 7 that has been pretty effective. Rolling those changes out to other devices. https://drive.google.com/open?id=0BzM9W6qUvx-gcm1SVDhsTDVWZ3M
May 31, 2016
-Replaced corrupted files. Good to go now!
Dangerously version (fixed) https://drive.google.com/open?id=0BzM9W6qUvx-gVHBGWEp3QkpURVE md5sum: a632c866e22114c0e18fa335f005293e
May 25, 2016
Quite a bit of changes here...
-VM completely readjusted. vfs_cache_pressure set back to default 100 to fairly reclaim memory pages that have been allocated to block specific data about file location, etc.. there are tons of write ups on this stuff if you guys want to investigate more into what this setting does, how it works. It's basically a fairness multiplier centered around a value 100. + or - that value increases or decreases the probability that the kernel will reclaim those certain memory pages relative to swap.
-Swappiness reduced drastically... from 80 to 40 (default is 60 depending on which kernel you are running)
-dirty ratio and dirty background ratios reduced drastically to avoid massive amounts of data being flushed and causing system hangups when that ceiling is hit. (lol this happened to me... system ran out of mem... *shrugs* I go hard bros)
-Increased the probably of the system to reclaim memory pages, and made a pretty big adjustment to writeback_centisecs and expire_centisecs
-Changed functional aspects of the interactive governor again - it is perfect. Nominal user experience. Same with touch input_boost. This system definitely has a sweet spot, and I'm pretty sure we've found it now.
-Decided to ditch the laptop mode idea and not mess with the RAM console outputs, the functional loss wasn't returning enough reward. So, here we are.
-Adjusted minfree once more, to
-It is important to note that the system will, admittedly, not multitask quite as aggressively. I had to do this, however, for myself mostly. As I was achieving OOM conditions and hitting the high ceilings set in other parameters like dirty_ratio and when it hits that wall, man it hits hard. Complete lock up for a good 40 seconds while everything is getting dumped from memory. I need a phone with more RAM lol. Didn't think that would ever happen on my mobile set up with 4 GB of it but here we are. I suppose I could re-enable zRAM for myself? But that would hardly help as compression ratios aren't going to yield me an extra gigabyte. Ok now I'm rambling. DOWNLOAD THE FILE!
Very interesting, I'll be trying this in the next hour or so! Thanks for posting.
Edit: Made changes as per the instructions and rebooted successfully. No issues so far, we'll see! Thanks again.
Nice...
Desde V10 (LG-H901)
For all variants? Is it compatible with H961N LP?
Looks promising and wanted to try.
How do I know it worked? I followed the steps
Sent from my LG-H901 using XDA-Developers mobile app
roosxter said:
How do I know it worked? I followed the steps
Sent from my LG-H901 using XDA-Developers mobile app
Click to expand...
Click to collapse
After every line he explains what it does, you would recognize the changes through your usage or maybe non-usage (as far as battery life and RAM management goes)
When I try to move the file it's giving me this error. I have BusyBox and pretty sure it's on read/write access. What am I doing wrong -_-
1|[email protected]:/ # mv init.qcom.post_boot.sh /system/etc
mv: init.qcom.post_boot.sh: remove: Read-only file system
1|[email protected]:/ #
iamtheon said:
When I try to move the file it's giving me this error. I have BusyBox and pretty sure it's on read/write access. What am I doing wrong -_-
1|[email protected]:/ # mv init.qcom.post_boot.sh /system/etc
mv: init.qcom.post_boot.sh: remove: Read-only file system
1|[email protected]:/ #
Click to expand...
Click to collapse
i got problem with the !!!!!!cd /sdcard , writing
i tried cd /storage/emulated/0
and worked for me
11868 said:
i got problem with the !!!!!!cd /sdcard , writing
i tried cd /storage/emulated/0
and worked for me
Click to expand...
Click to collapse
I tried that, but doesn't hurt trying again.
Edit: It worked. I did the same thing lol oh well thanks @11868
Can this be done with the root explorer instead of terminal emulator?
So this can be used on the G4? And does this overwrite settings within the kernel? If I push this file and I don't like the results can I flash a kernel to get rid of the changes?
iamtheon said:
When I try to move the file it's giving me this error. I have BusyBox and pretty sure it's on read/write access. What am I doing wrong -_-
1|[email protected]:/ # mv init.qcom.post_boot.sh /system/etc
mv: init.qcom.post_boot.sh: remove: Read-only file system
1|[email protected]:/ #
Click to expand...
Click to collapse
Your system wasn't mounted as rw when you executed the command
agrenwa said:
Can this be done with the root explorer instead of terminal emulator?
Click to expand...
Click to collapse
It can, yes, I just prefer the old school way. You can manually drop the file in the /etc folder after deleting the previous one. Just need to make sure the permissions are set appropriately.
klbjr said:
So this can be used on the G4? And does this overwrite settings within the kernel? If I push this file and I don't like the results can I flash a kernel to get rid of the changes?
Click to expand...
Click to collapse
Yes, this can be used on the G4 and any other device using the Snapdragon 808. Overwrite settings within the kernel? No, I wouldn't say that. sysfs is more of a userspace / virtual file system that allows you to interact with the hardware... but the parameters we are working with here are completely writable, not permanent, and more important, will reapply AFTER boot. So, no, flashing a kernel will not revert the changes. If you want to go back, you'll need the original file to replace mine with.
Hope this answers your questions.
Since the file is hosted on Dropbox, anyone who has a dropbox account please choose the login option, and transfer the file to your dropbox before downloading it from your own storage to avoid OP's dropbox being blocked for too many downloads in a row.
Good Job OP, nice to see Junior Members doing something great in the dev section
So I did it last night, and so far battery life seems to be much worse than before when nothing has changed but these tweaks. Any idea why? Battery stats is the same for me as usual with the exception of Android System being at 6% and Android OS at 6% use each.
So far so good, not sure what battery usage will be like. I had terrible lag in a game called Underworld Empire and that has disappeared! How badly was the kernel/system coded before?!
Question , how come your file is smaller than the original? Was there a lot of excess code that was useless?
Sent from my debloated rooted LG V10 using Tapatalk
rirozizo said:
Since the file is hosted on Dropbox, anyone who has a dropbox account please choose the login option, and transfer the file to your dropbox before downloading it from your own storage to avoid OP's dropbox being blocked for too many downloads in a row.
Good Job OP, nice to see Junior Members doing something great in the dev section
Click to expand...
Click to collapse
I'll try to upload the file elsewhere, didn't consider that. However, it is a very small file and dropbox might not notice/care. Good observation.
danstheman7 said:
So I did it last night, and so far battery life seems to be much worse than before when nothing has changed but these tweaks. Any idea why? Battery stats is the same for me as usual with the exception of Android System being at 6% and Android OS at 6% use each.
Click to expand...
Click to collapse
Coincidence maybe? Keep monitoring, report back.
Also, bear in mind: rebooting your system causes a little more activity within the OS the first day or so (particularly google services) and it does have an effect on battery drain.
amoot329 said:
So far so good, not sure what battery usage will be like. I had terrible lag in a game called Underworld Empire and that has disappeared! How badly was the kernel/system coded before?!
Question , how come your file is smaller than the original? Was there a lot of excess code that was useless?
Sent from my debloated rooted LG V10 using Tapatalk
Click to expand...
Click to collapse
Yes, it is smaller because I removed everything that was not relevant to the msm8992 SoC. Qualcomm uses common files for just about everything and anything they can - saves them time, hassle and consolidates work somewhat.
Most of the content removed from the stock file is for other platforms not relevant for us.
warBeard_actual said:
I'll try to upload the file elsewhere, didn't consider that. However, it is a very small file and dropbox might not notice/care. Good observation.
Click to expand...
Click to collapse
I recommend Google Drive or Box
@warBeard_actual
Great job buddy on this.... @freeza mad af!
To everyone else I've been using this for a while and am happy to report my buddy warBeard_actual has been killing it!
bencze, proof or it didn't happen