Related
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.
Hey,
I was using swiftdroid last two days and it appears to be killing all apps almost as soon as I quit it. I checked with Advanced Task Killer and it appears swiftdroid is trying to keep at least 45MB free even after I enabled 32MB swap with built-in VRAM.
This is very annoying. It keeps quitting facebook chat and IMO chat as soon as I switch to another app. I'm aware GT540 has very low memory but the thing is in stock, I didn't have any problem even though I didn't have VRAM/swap. I usually get around 25MB RAM free all the time and most apps stay in memory. I'm usually like able to launch the IM app, facebook app and still be able to use the browser or file expert or messaging app.
So, is there's a workaround? It's really annoying when it keeps quitting the IM app just like that!
Sorry for saying it's annoying. I know we get this for free and I shouldn't be complaining at all. It's just that it pissed me by quitting IM app, the only app I want to stay in the memory.
What version of Swiftdroid are you using
The latest one (M5), has improved RAM management a lot
And comes with better battery life, too
I got the same thing. Always 40-45mb free and apps being killed quickly. I'm on M5. Someone said that Joestone's AOSP is better in this aspect, but I didn't test it yet.
Mitalca:
I'm on M4. I downloaded M5 only today. I don't think it lacks good RAM management. It's just that its memory management settings have been tweaked to keep maximum possible amount of RAM free so that any new app will launch faster. Am sure there must be a switch to change it.
EazyLuke:
I don't really have any problems with stock 2.1. I checked out Joe's AOSP and swiftdroid. The only real advantage apart from speed is voice input. In Joe's AOSP, I couldn't get voice to work. In swiftdroid, it worked.
that's what I meant with RAM management
Maurik changed the settings on M5
mhoangtr said:
In M4 rom, lowmemorykiller setting is 6,8,16,20,32,40 MB so apps killed too fast.
If you want to keep apps longer, try set to 6,8,16,20,22,24 MB (this is default value of android).
Click to expand...
Click to collapse
But I don't know how can you change that setting in M4
Try M5, if it ain't working for you, go to Joe's
Mitalca said:
that's what I meant with RAM management
Maurik changed the settings on M5
But I don't know how can you change that setting in M4
Try M5, if it ain't working for you, go to Joe's
Click to expand...
Click to collapse
@Mitalca: That's the whole purpose of the post. I couldn't find the option where I can change 6,8,16,20,32,40 MB to 6,8,16,20,22,24 MB.
How do I change it?
You can change these values with e.g. this application https://market.android.com/details?id=com.lim.android.automemman&feature=search_result
I installed this app: https://market.android.com/details?id=com.rs.autokiller
It does the same thing.
I set the values to 6-8-12-18-20-20. Now I'll have to see if that brings an improvement.
EDIT: Tested it for a few minutes. And it seems to be an awesome improvement! I can switch from Facebook, Twitter and Browser, and everything is kept in memory, meaning these apps don't have to reload everything!
And it seems to be stable. I also use some of the "advanced system tweaks settings".
Thanks you guys.
XDA memebers. Useful as ever.
I'm gonna try both the apps and keep the app with slicker interface.
M5 isn't working.
Says assert failed when trying to flash via recovery.
Trys v6 SuperCharger!
http://forum.xda-developers.com/showthread.php?t=991276
It Works Perfectly on our GT540!
I found this problematic, too.
I installed M5 yesterday. Everything is great except this (and I don't like oversensitive accelerometer, but it's not urgent problem ).
Last night I listened Music player, and surfed via Miren. After two opened tabs, Music player shut down . After four opened tabs, phone rebooted. Factory widgets' widgets are useless with this agressive RAM menagment.
hash87 said:
You can change these values with e.g. this application https://market.android.com/details?id=com.lim.android.automemman&feature=search_result
Click to expand...
Click to collapse
Thanks man.
Works excellent .
EazyLuke said:
I installed this app: https://market.android.com/details?id=com.rs.autokiller
It does the same thing.
I set the values to 6-8-12-18-20-20. Now I'll have to see if that brings an improvement.
Click to expand...
Click to collapse
To bad - it want access to too much permissions.
Access to too much permissions? Use LBE Privacy Guard!
What permissions?
And by the way, I wrote a PM to Mur4ik and asked him to try this app out. Maybe he'll change the numbers for RAM-management in his next release if he thinks it's an improvement.
EazyLuke said:
What permissions?
And by the way, I wrote a PM to Mur4ik and asked him to try this app out. Maybe he'll change the numbers for RAM-management in his next release if he thinks it's an improvement.
Click to expand...
Click to collapse
There are plenty of custom ROMs that use Mur4ik's config. It boils down to personal preference. Do you want newer apps to launch really fast or do you want certain apps to stay in memory all the time?
Multi-taskers would prefer to have all apps in memory while people who like doing one thing at a time or who use phone for gaming mainly would prefer Mur4ik's config which launches apps faster.
The best thing for Mur4ik is to include an option to change the memory management config depending on user.
After changing the numbers my apps don't really seem to open slower.
In my opinion Mur4ik could lower the numbers a little bit, to allow better multitasking, but still let new apps open fast (just my personal opinion).
But I don't say he HAS TO do that, just a suggestion, if he doesn't like it it isn't a problem at all, because everyone can simply adjust the numbers easily .
That's true. xD
If I were to suggest, I'd suggest to add the option to change these settings. Apps opening fast depends on what individual apps are in the memory and what new app you are opening.
For example, if you open Angry Birds while your memory is at 16MB, you certainly can't expect it to open fast.
On the other hand, if you open messaging app while memory is at 16MB, it certainly will open faster.
But, I really disliked the apps Swiftdroid had in the latest release. I had to get rid of the whole GO suit with Uninstaller for Root.
nibras_reeza said:
But, I really disliked the apps Swiftdroid had in the latest release. I had to get rid of the whole GO suit with Uninstaller for Root.
Click to expand...
Click to collapse
Try M6, was released yesterday, it's completely clean! Only Tonepicker and QuickSettings are added.
SWEETTTTTTTT!!!!!!!!!!!!! xD
you could also try to put mur4ik rom in the kitchen and play with autokiller settings ...
this is michalak8 from android.com.pl (mike's froYo dev) looking for that magic 10 posts to post my rom) Could someone close the rom thread in development section - I would like to post it my self without google-translate bugs
mikegapinski
I just want to know if anyone else is running this script. I refused to believe my Nexus S was not behaving, after all, it's a Nexus S! But, eventually even I had to get real. Truth is, lately, no matter what ROM I'm running after a few days things would slow down way too much. Lag, Launcher redraws, FCs due to lag. Things were too slow.
Anyway, I used the V6 SuperCharger script and it really has changed things. I used the MegaRAM option for 512 MB phones and I swear it has been a revelation. Even overclocking couldn't bring about this change. Currently, I'm on MIUI which most people consider to be a bit heavy and clunky. However, after supercharging with the MegaRAM option and Bulletproofing the launcher it's unstoppable! Highly recommended for those of you experiencing phone lag. Make sure to follow the Dev's instructions for using his script. All credit to user: zeppelinrox. Amazing stuff!
Which MegaRAM option did you select? I picked the second option, but I don't know which is better for Nexus S. So far I noticed browser is much much smoother now, other things has always been smooth for me, so I can't really tell the difference.
I used the 2nd MegaRAM option as well. But, I'm going to test out the first option. As I understand it, the more memory you want free in the 3rd slot the less multi tasking you can do (as this is where the secondary apps will be places)...I THINK!
As per that thread if 25 MB is good enough on a Milestone, a Nexus S should do well with 40 MB.
THIS from the thread:
zeppelinrox said:
Additional Info: You can find each app's priority and OOM.
....................... In AMM, Press Menu > Running Processes > Group by OOM grouping.
....................... Expand each group and see what apps are included and each app's priority level. (Higher numbers get killed first!)
....................... If you tap on an app, you can get additional info. Tip: Check and see what's included with android.process.acore
The default minfree values ("kill thresholds") for each OOM group are, as far as I can tell: 6, 8, 16, 20, 22 and 24 mb. (CyanogenMod 6.1.2)
This means that: when free memory lowers to 24 mb, EMPTY_APPS get killed; at 22 mb free ram, CONTENT_PROVIDER apps get killed; and so on...
Now, because the Milestone has only 256 mb of memory, I found these numbers too low, especially the 3rd one.
Basically, with those settings, you will usually be sitting with only 20 - 25 mb of ram.
Possibly less. Basically, it's the 3rd number (16) + 5. That's your free memory.
And my phone just chokes when it has that little ram available. Lag, home screen redrawing, the launcher getting killed.... ugh....
After extensive fiddling around, I've come to the conclusion that setting the third slot to about 25mb works great.
No home screen redraws while not being too aggressive on secondary/background apps while having about 30-35mb free all the time
BTW, free ram is not wasted. Android will use that memory to cache the file system and this speeds things up. See this informative post.
Click to expand...
Click to collapse
Si_NZ said:
Which MegaRAM option did you select? I picked the second option, but I don't know which is better for Nexus S. So far I noticed browser is much much smoother now, other things has always been smooth for me, so I can't really tell the difference.
Click to expand...
Click to collapse
Just tested the 1st MegaRAM option and things are quite smooth. Launcher is not as buttery as with the 2nd option but, it's still great. The browser does quite well too, pinch to zoom is smooth but, scrolling is a little stuttery on a heavy page like Engadget's.
Just wanted to tell - if you are on my MIUI ROM, don't use it because I have my own RAM Optimization script integrated.
never heard of this till this morning, thanks for bringing it up
trying it out now
brainmaster said:
Just wanted to tell - if you are on my MIUI ROM, don't use it because I have my own RAM Optimization script integrated.
Click to expand...
Click to collapse
I love it when a tweaker tells tweakers not to tweak.
Really!
zeppelinrox said:
I love it when a tweaker tells tweakers not to tweak.
Really!
Click to expand...
Click to collapse
you should know that two scripts running can cause issues......
zeppelinrox said:
I love it when a tweaker tells tweakers not to tweak.
Really!
Click to expand...
Click to collapse
I didn't said anything against your script, just told the users to not use it on my custom ROM. A think that as maker of your script you should know - two RAM scripts on same ROM are doing only damage.
They don't stay running.
They execute and end.
Whichever one runs last is the one that sticks.
Many people were using juwe's script with the V6 script and things ran fine so it's not a big deal.
Of course, if somebody wanted to, they can delete the minfrees in any of their custom roms and plug them into supercharger...
Why do you guys like scaring the crap out of people for nothing? lol
brainmaster said:
Just wanted to tell - if you are on my MIUI ROM, don't use it because I have my own RAM Optimization script integrated.
Click to expand...
Click to collapse
Great to hear from you. Haha. Just about to ask you
does it work well with cm7?
mohsin125 said:
does it work well with cm7?
Click to expand...
Click to collapse
I'm running it on cm7, and my phone seemed to be a bit snappier
time will tell though
Can someone put this in a stock rom? Sounds too complicated
. Interested in more speed but stock on matrix rom is pretty fast
rican408 said:
Can someone put this in a stock rom? Sounds too complicated
. Interested in more speed but stock on matrix rom is pretty fast
Click to expand...
Click to collapse
use this guide, and it will be easier than you could imagine
http://forum.xda-developers.com/showthread.php?t=1126940
I tried this and for some reason it derped my sim card, said it was locked (couldnt unlock it when booted as it just went passed the pin screen and onto home screen) and the home button wouldnt work. Anyone got any ideas?
Haizum74 said:
I tried this and for some reason it derped my sim card, said it was locked (couldnt unlock it when booted as it just went passed the pin screen and onto home screen) and the home button wouldnt work. Anyone got any ideas?
Click to expand...
Click to collapse
I've seen this problem with the SIM/PIN lock on other ROMs. You might want to try disabling and re-enabling the SIM/PIN lock from settings. It should immediately ask for the PIN and reenable you Home key. What settings did you apply? Maybe they killed off your system guard.
Sent from my Google Nexus S using XDA App
Just an update on my settings. The MegaRAM seem to really speed everything up but, I find that they weren't being nice to my Whatsapp (I was missing messages now and then) I think Whatsapp would receive the message but get immediately killed before it could broadcast the notification. Once it even seemed to exit in app for no reason at all. So I switched to Balanced Settings 3 and so far Whatsapp as well as the launcher and phone in general has been very responsive.
Sent from my Google Nexus S using XDA App
deejaylobo said:
I've seen this problem with the SIM/PIN lock on other ROMs. You might want to try disabling and re-enabling the SIM/PIN lock from settings. It should immediately ask for the PIN and reenable you Home key. What settings did you apply? Maybe they killed off your system guard.
Sent from my Google Nexus S using XDA App
Click to expand...
Click to collapse
I went for Megaram option 1 (I think). I disabled password and it then worked but by this time I had uninstalled the script. Any particular option you suggest? Cheers for the reply too.
It depends on your usage. I would suggest starting out with Balanced settings 3 and moving up or down the menu depending on whether you want more(down) or less speed(up). I've found that the trade off is speed vs multitasking. Though, I think zeppelinrox could confirm whether I'm right.
I was wondering if i could minimize applications on my phone and make them run as there are running normally . So that when i return to them they do not have to reload or anything . Something like the backgroundr application on iphone . Is something like that available on android ?
Sent from my HTC Vision using XDA App
hah are you kidding me? You're about to start a flame war lol.
Android has proper multitasking. When you hit the home button in an app, the app continues to run. Effectively "minimizing" the app. The only reason why it would close is to open up memory for a newer app that demands it. Switching between apps is as easy as holding down the 'home' button to see a recent apps list, and selecting which you want.
The iPhone is the one that actually doesn't do true multitasking. For most apps on iOS, they freeze the app rather than letting it continue to run. Things like streaming music, etc. will continue to play, but minimizing an app like a game etc. something will freeze the app till you return to it.
Some light reading on the subject that may give you a little insight: http://android-developers.blogspot.com/2010/04/multitasking-android-way.html
After you understand that, I find this video explains it as well: http://developer.android.com/videos/index.html#v=fL6gSd4ugSI (from a developer POV, but still shows how it works).
+1, home button to "minimize" the app, and longpress home to return to it.
Well I was gonna say, just hit home and it stays running but his post is epic lol.
Okay thanks and sorry for the dumb question but i still have a few inquisitions .. if i am browsing the web and i go to the messaging app to send a text then when i go back to the internet browser the web page reloads . As i have a slow mobile internet connection that annoys me . Secondly if i am watching a video and again have to send a text when i go back to the video it starts from the beginning . Is tht how its suppose to be or am i doing something wrong ?
Sent from my HTC Vision using XDA App
talha92 said:
Okay thanks and sorry for the dumb question but i still have a few inquisitions .. if i am browsing the web and i go to the messaging app to send a text then when i go back to the internet browser the web page reloads . As i have a slow mobile internet connection that annoys me . Secondly if i am watching a video and again have to send a text when i go back to the video it starts from the beginning . Is tht how its suppose to be or am i doing something wrong ?
Click to expand...
Click to collapse
it more than likely means there wasn't enough free RAM available to run both applications (along with all other background applications) so it closes the previous app so that the current one can operate freely.
So what I'm expressing is that Android isn't closing the app because you switched apps, its closing in order to keep the other apps running properly when the system is low on RAM, rather than the phone freezing up.
Are you running stock HTC Sense? Because on MIUI I just loaded a page, then read a text, followed a link to the youtube app, watched a video, then toggled back to the browser and the page was still there...
If you're on stock HTC Sense I'm assuming thats why you're having RAM problems.
I like the htc sense look on my phone so i am using virtuous unity v1.31 that has sense 3.0 ..And i have the task manager application installed i have never seen my phones free ram lower then 65 mb . Its usually around 70-75.. so i wonder why my phone is closing apps by itself . :s
Sent from my HTC Vision using XDA App
I just checked 'running services' in the phone settings under applications . There the free ram.is ranging from 185mb to 165mb . :s
Sent from my HTC Vision using XDA App
Do you have a ''how-to'' to disable or uninstall services that we dont need?
In the same way as msconfig on windows.
talha92 said:
I like the htc sense look on my phone so i am using virtuous unity v1.31 that has sense 3.0 ..And i have the task manager application installed i have never seen my phones free ram lower then 65 mb . Its usually around 70-75.. so i wonder why my phone is closing apps by itself . :s
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
This "Task Manager" you have running. Is it some app that kills other apps? If so, uninstall it. It is causing your problems and making your phone run poorly.
If you search around (maybe even on the Unity thread, if my memory serves me correctly . . . which it often doesn't!) there are some tweaks posted that are claimed to help memory management by slightly adjusting the parameters by which Android kills processes. I haven't personally tried them, so make a nandroid before changing anything, just in case.
talha92 said:
I like the htc sense look on my phone so i am using virtuous unity v1.31 that has sense 3.0 ..And i have the task manager application installed i have never seen my phones free ram lower then 65 mb . Its usually around 70-75.. so i wonder why my phone is closing apps by itself . :s
Click to expand...
Click to collapse
What 'task manager application' do you have running? If its killing processes prematurely then that can be a problem...
GinoAMelone said:
This "Task Manager" you have running. Is it some app that kills other apps? If so, uninstall it. It is causing your problems and making your phone run poorly.
Click to expand...
Click to collapse
the task manager app is the app already installed in the virtuous unity rom .. and i cant seem to uninstall it . and i dont think it would cause problems as it is packaged in the rom. would it ? .
---------- Post added at 08:53 PM ---------- Previous post was at 08:50 PM ----------
redpoint73 said:
If you search around (maybe even on the Unity thread, if my memory serves me correctly . . . which it often doesn't!) there are some tweaks posted that are claimed to help memory management by slightly adjusting the parameters by which Android kills processes. I haven't personally tried them, so make a nandroid before changing anything, just in case.
Click to expand...
Click to collapse
thanks i am going to search for it in the virtuous unity thread and see if i am able to solve the problem .recently i noticed if i am playing music in the background and i open the messaging app or a big site like the desktop version of facebook on my browser the music application crashes so there is definately an issue with memory management in my phone
The main issue is that Sense 3.0 is not really meant to run on our phone, due to lack of memory. Sense 3.0 takes a huge chunk of memory, so it doesn't take much more to push the system over the edge. The tweaks I've read about won't be a huge change in memory management. But people on here swear they are helpful.
redpoint73 said:
The main issue is that Sense 3.0 is not really meant to run on our phone, due to lack of memory. Sense 3.0 takes a huge chunk of memory, so it doesn't take much more to push the system over the edge. The tweaks I've read about won't be a huge change in memory management. But people on here swear they are helpful.
Click to expand...
Click to collapse
With the new virtuous unity 2.37.0 (sense 3.0) I have an average of 130 mb of free memory. I use temp+cpu widget to monitoring.
Is it not enough?
I read an article about memory managing (auto killer apps) on GB roms, an apparently it wont give a faster speed or better battery life.
oVeRdOsE. said:
With the new virtuous unity 2.37.0 (sense 3.0) I have an average of 130 mb of free memory. I use temp+cpu widget to monitoring.
Is it not enough?
I read an article about memory managing (auto killer apps) on GB roms, an apparently it wont give a faster speed or better battery life.
Click to expand...
Click to collapse
If the latest version of Unity uses less memory, updating to that version might help the OP with his particular issue. I'm personally on 1.29. I tried every version after that (with the exception of 2.37), and they all resulted in my battery life being cut in half, so I'm back on 1.29.
The memory management tweaks I spoke of are simply adjustments to the parameters by which Android's built-in task manager kills tasks when memory is needed, not a separate auto killer app. Android inherently kills idle tasks when memory gets low. The adjustment I've seen, if I remember properly, actually raises the threshold for how full memory is before it starts killing tasks.
I agree that 3rd party auto killer apps will not increase performance, except in pretty isolated cases (like a rogue app, badly coded app with a memory leak).
Yes i was thinking of updating to v 2.37 nd see if tht solves my problem . And i was wondering if there was a simple way to stop android automatically closing applications till its down to more like 20-25mbs . But it will never go tht low will it ?
Sent from my HTC Vision using XDA App
I use the mobile phone in the process, feel the speed is very slow, does there have a app, can run a memory more than 90% in the use of the process ,It can automatically clean up? I use sgI9500
wufang640 said:
I use the mobile phone in the process, feel the speed is very slow, does there have a app, can run a memory more than 90% in the use of the process ,It can automatically clean up? I use sgI9500
Click to expand...
Click to collapse
There's a few things you can try. First have you changed the animation/transition speeds in developer settings, it definitely makes things feel a bit snappier.
If you're rooted you can try greenify to hibernate apps running in the background.
https://play.google.com/store/apps/details?id=com.oasisfeng.greenify
You can remove unneeded Samsung/bloatware apps installed on the /system directory, this frees up some RAM. If you're not rooted you can disable unneeded apps in applications.
Or another option is to install a custom ROM that has performance tweaks and bloat removed.
Sent from my GT-I9505 using xda app-developers app
gsmyth said:
There's a few things you can try. First have you changed the animation/transition speeds in developer settings, it definitely makes things feel a bit snappier.
If you're rooted you can try greenify to hibernate apps running in the background.
https://play.google.com/store/apps/details?id=com.oasisfeng.greenify
You can remove unneeded Samsung/bloatware apps installed on the /system directory, this frees up some RAM. If you're not rooted you can disable unneeded apps in applications.
Or another option is to install a custom ROM that has performance tweaks and bloat removed.
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
thanks guys, greenify is good.
wufang640 said:
I use the mobile phone in the process, feel the speed is very slow, does there have a app, can run a memory more than 90% in the use of the process ,It can automatically clean up? I use sgI9500
Click to expand...
Click to collapse
I found that the best thing was to just play around with the settings. I uploaded a quick tips video on how to speed up your Galaxy S4 using my i9500, but any variant will work. The link to the video is here: http://goo.gl/7Y71w0. It actually makes a huge difference (you can notice the changes straight away) and its really simple to do even if you are a new user.
Another good thing to do was to get rid of Samsung's bloatware which helps free up lots of memory and the whole UI feels a bit less bogged down. To do this you can either individually disable each app you don't want in settings > more > application manager > and choose and force stop or uninstall the app you wish to remove. While this doesn't get rid of the app from your actual device, it will stop it from eating all your RAM. A better way to do this (but it is more difficult) is to run the "Truly Clean" script on your device. I made a tutorial of it on my website here: http://goo.gl/dgk67P and the original thread is here: http://goo.gl/63SmWI.
Hope that helps you out
Clean Master is a greate application, all in one, it do a well job. it's free on google play stor :