Database Info

Raphael is brutally closing programs!

Raphael is brutally closing programs!
I really dunno why is this happening... I have 50% of RAM free and it lets me run just 3-4 programs together. When I run one more... it occasionally selects one thats previously ran and kills it silently... I really wouldn't like to "Clear Storage" from settings

I also had this problem when I first got my TP. It's a simple fix - you need to disable AutoKill. With a registry editor, go to HKCU\Software\HTC\TaskManager, and change the value of “EnableAutoKill” to “0".

^ yes this a good fix. I remember I couldnt switch between opera and replying to a text message, I felt like I was back to a feature phone, with one thing at a time capability.
There is also a registry tweak that instead of killing apps you can change the threshold at which the system starts auto-killing, same registry path.

You guys are amazing! THANK YOU! BUT... I still have the problem
Any other ideas?

You can refer to this thread:
http://forum.xda-developers.com/showthread.php?t=426585
In the section of "Tips", there is a tweak which solved the problem perfectly

Thank you. Tried that caches tweak, it made whole system run much faster. But still - i cannot seem to get 4 proggies to run at the same time. Always the first dies... flip flop

This thread is turning into a copy of few others around here. Only this is new and alive.
Please help me out.
I've tried:
1) The HTC Task Manager registry tweaks
2) The cache sizes maximizing
and...
3)?
Maybe the ugly 32MB/32Process limit (http://msmobiles.com/F/viewtopic.php?p=36334&highlight=&sid=c6b5982e059ec35ce19fd3cd952bd683) is still present in WinMo6.1?

Hello!
OMFG! After disabling autokill my TP started to act almost like desktop in case of multitasking
I was able to run around 12 programs at a time, but i've also made changes to memorytreshold, the value i set was 173015040 (1.5 times the default value).
The funny thing was that TP was still responsive to commands and even opera ran smoothly when surfing throu light web pages.
First app closed after memory usage peeked around 65%, but the rest was still responsive.
Hope this helps
BHole

Thats my point. Same limit like 65% because I have customized my device with launchers, hardkey remapper, Wktask etc. Now I can have (only) five apps running at a time... Is there a sort of free RAM threshold inside the WM6 or HTC-s stock (1.9) ROM. Maybe it is still the 32 process limit from the old times?

Hello!
It looks like there is some kind of limit to number of proceses or memory used by them but if you customized your pda maybe you should disable some of the oryginal programs that are runing in the background. I saw some registry entries in taks manager that hid some of the runing aps maybe not all of them are nesesery for you and can be disabled to lower proces count.
BHole

Yeah.. but I would like to USE the RAM the device has.... I'd like to run manymany programs so the RAM load would be for example 95%. Why is not that possible?

[Q] Some newbe questions

I have a few questions and thought I'd post them for you Android Ninjas to laugh at. Once you get though recognizing my ignorance though, I'd love some education.
Why does my phone give me errors that it can't move apps to my SD card (says it is full) when I have 7GB free on it?
I tried installing an app and it told me that there wasn't enough room in SYS to unpack the files. Is this related to #1? How can I give more space to SYS?
Do widgets or live wallpaper consume CPU or battery when the screen is off or the phone is locked? In other words, will a sleeping phone with lots of widgets use more power than one with just static shortcuts on the screen?
Is the Android memory management good enough that you don't need to reboot the device every day or so in order to clear everything out and get optimum performance?
I've played with the rooted stock ROM for the Inspire, Revolution 4, and now CM7. I see the differences between the UI interface. But what is the purpose/benefit in changing kernals?
Every evening at 7pm, I get a blank SMS message notification with no content and no sender name/number. When I click to open it, it launches GO SMS, but there is no corresponding message in my list of messages. What is this and how do I get it to stop?

3. yes, the more, the more resources and cpu used. livewallpaper uses more than static wallpaper. more widgets, especially ones that update and use data, use resource more than no widgets, etc.
4. android OS is rock solid. i go weeks without reboot. i just went 540 hours on one boot, and that's just the best one that i paid attention to. it goes longer but after 22 days it loses its fun of keeping track.
5. differetn kernels are for different purposes. some are over clocked for performance. some are under volted for longer battery life. its just ways to tweak the phone to get what you want out of it.

RAM Script and Delvik Heap size anyone?

Has anyone tried this on the Infuse ?
[SCRIPT][19.9.2011] The Best RAM Optimization - Updated!
I also did the following.
Used Root Explorer, and Open & edit /system/build.prop, change dalvik.vm.heapsize= to 80m
Any one confirms this is great ?

Have not tried, might muck around with it later today after i finish my essay. Do you think his script will run on top of DynamicRAM's 99 tweaks? I know the supercharger script didn't play nice with it if you have both installed at the same time.

Didn't notice anything
hey ya'll watch this!!

If this is what I think it is then it is what dynamic rams script is based off of. If it is an init.d script then most likely the parameters that each changes that ate the same will new set to the last commands that runs setting it. Though both may run together it is gonna be mostly redundant. One script will mostly not be applied. Changing the name of the script will determine what runs first. I know the letter s and I think e are used for this but I don't know which is set to run first. Then the number sets the order after that.

[Q] Is there a way to permanently set lower oom values for processes?

I'm using Autokiller to keep my phone a bit snappier since I have a low amount of memory. However, at times it kills processes that should stay open (namely: the phone and messages apps, which I have to open several times in a row because it closes them right after I open them). I have found that setting the oom value of these processes low (-17, foreground, ignored) in Autokiller helps, but the problem is that these values always keep reverting back to original after some time. Is there a way to permanently set lower oom values for processes either using Autokiller or some other way?

have you found a fix?
I'm wondering the same thing. Have you figured out a way to do it? Autokiller keeps killing Dr web on me.

neverlost7 said:
I'm using Autokiller to keep my phone a bit snappier since I have a low amount of memory. However, at times it kills processes that should stay open (namely: the phone and messages apps, which I have to open several times in a row because it closes them right after I open them). I have found that setting the oom value of these processes low (-17, foreground, ignored) in Autokiller helps, but the problem is that these values always keep reverting back to original after some time. Is there a way to permanently set lower oom values for processes either using Autokiller or some other way?
Click to expand...
Click to collapse
As long as your device is rooted you can use Auto Memory Manager from the market.
Its a free app and can set OOM values and priority for programs
But a weird of warning, never set a large program like HTC Sense or whatever to -17 unless you have lots of RAM.
Sent from my HTC HD2 using xda premium

Supercharger is the way to go if you ask me. Memory manager apps I've seen seem to act more like task killers, does more harm than good. Supercharger allows you to change the oom settings, and the priority settings that certain apps get. I think it requires root, but then again ANY app that is going to actually do what you want is going to require root. I would give it a try, every single person I have recommended it to has thanked me after.

Silentbtdeadly said:
Supercharger is the way to go if you ask me. Memory manager apps I've seen seem to act more like task killers, does more harm than good. Supercharger allows you to change the oom settings, and the priority settings that certain apps get. I think it requires root, but then again ANY app that is going to actually do what you want is going to require root. I would give it a try, every single person I have recommended it to has thanked me after.
Click to expand...
Click to collapse
I have used this too, but it isn't very n00b friendly, it works extremely well however but I would like to add, you shouldn't use the highest settings in supercharger unless you have a high end phone, the OOMs on the top settings are ridiculously high...

Tigermoto said:
I have used this too, but it isn't very n00b friendly, it works extremely well however but I would like to add, you shouldn't use the highest settings in supercharger unless you have a high end phone, the OOMs on the top settings are ridiculously high...
Click to expand...
Click to collapse
Yea, my amaze has over 800mb of ram, and the highest setting ate that up real quick.. but the lower values were pretty good for my old vibrant which only had 343mb of ram.
I thought the instructions weren't too complicated, thought the length of the post should scare off anyone who isn't too sure of themselves.. the main thing someone could do wrong is set it as run at boot in script manager. As long as they just follow the prompts once they run the script, they should be able to experiment without risking any damage to their phone.
If anyone has any problems, that thread has most of the answers in it, the people are willing to give advice, and worst case scenario I could try to help if anyone has any issues. If you are capable of rooting your phone(outside one click root solutions), you are more than likely safe following the instructions in that thread.

I use system tuner pro for my Xperia arc s, check it out in Google play

(Guide) A complete maintenance guide to pretty much any android phone

INTRODUCTION
This is a guide made ​​to with help from Xperia X10 users and developers for Xperia X10 users enjoyment but most of the tips contained here are suitable for any phone running Android. The tips contained here focus on WHAT to do to improve the performance of your phone and not HOW to do it, after all, once you know what must be done is to find simple tutorials on how to take these actions.
For some of the tips contained in this guide I assumed that you have just installed a new ROM or formatted / bought your phone recently and have root access but even without these prerequisites this guide can still be useful to most users.
It’s important to say that although most of the tips some are quite basic, some require a little more work and deal with the more delicate parts of your phone, they should be made ​​at your own risk. These more advanced tips often use very specific terminology which you can find more about on XDA Developers or even Google.
Finally I would like to remind that even machines that are made ​​within a few standards can operate in different ways: some phones take better advantage of certain adjustments and settings and not others so it’s impossible to guarantee one hundred percent efficiency for all of you but still I that you make good use of this guide.
Sincerely,
Guilherme "XOT" Oliveira
- Install a good ROM and a good Kernel
Official ROMs are good but custom ROMs are usually faster and in many cases as stable as official ROMs. This is because ROMs are released and thereafter rarely change, custom ROMs are already made by developers who are constantly improving their job to get the most out of your phone. It's very important to research before installing a new ROM, searching always for the one that meets your expectations and relates well with your device since the same ROM can work very well on my x10 but not as well on x10 my brother’s for example.
The same goes for Kernels, but with Kernels take extra care to make sure that the Kernel is compatible with your desired ROM and your phone.
- Keep clean your caches
Caches are good to keep certain information and have access to these faster but with these files and information some "garbage" is stored .
The solutions to this can be pretty basic or advanced, the most basic way is to enter your Application Manager (Settings> Applications> Manage Applications) and clear the cache for each application. It is important to clear the cache only and not application data as these may be important such as the files that resemble your progress in a game. Already the most advanced solution is to clear the Dalvik Cache and Cache Partition through your recovery.
Both solutions don’t need to be made ​​with daily frequency, for example I usually clean my caches every 45 days or when I feel that the phone is getting slow.
- Make a full, but clean, backup
Full backups (full system backup) like those made ​​by recovery or nandroid are great to store complete setups but when they are done with “dirty” files in the the phone’s memory restoring these files may worsen rather than help the situation of your device .
Ideally, do a full backup after completely configure your phone (configure your account, set your homescreens, install the required applications, etc.) but before using it for real.
That way if your phone starts getting slow and nothing works to reverse the situation you can easily go back to your “original” settings without the hassle of customizing everything in its way again.
- Do not touch the CPU / GPU the first day
Like people, phones also take a while to adapt to a new environment, or in our case new ROMs, so during the first 24 hours of use is important to use the settings of CPU and GPU that came with the ROM, no overclock, undervolt and things like that.
Another important step in the process of adaptation to the new ROM is really using and exploring the device in this very first day so it "get used" to the change. Do not mind the battery consumption, that should stabilize after a few days.
It’s also iimportant to remember that some ROMs already comes with overclock, undervolt and improvements in battery usage. In this case there is no problem in using these settings from the first minute because if they are there since the installation of the ROM, it is because they are part of the default settings already programmed and develop on this particular ROM and it will work better this way.
- Use the maximum your battery
Batteries seem to last less and less as time goes on, in part this is because your battery is uncalibrated and there are ways to fix it.
I will not talk much on this subject because it is very easy to find guides that teach you how to calibrate your battery so I’ll just recommend that you take a look at them.
- Applications: less is more
Having millions of apps is the glory and the doom of smartphones, the glory because you can do everything on your device and doom because of the following reasons:
As a computer your phone also slows down the as it becomes full and in most cases you can blame it on the number of apps that you have installed on it. So try to leave installed only the applications you actually use and uninstall the ones that you no longer use so you can have more free memory and consequently a faster device.
Some applications can not be uninstalled because they are system applications; in order to remove those apps you are going to need uninstallers that have root access (ex: RootUninstaller) which are capable of removing these applications but before taking such a measure is necessary to look for a safelist (a list of applications that can be removed without causing system problems).
Keeping a low number of applications but doing so by installing and uninstalling new apps every day also usually let the machine slower so if you find an application for a specific function that fits your needs you should stay with it instead of testing another 10 before returning to it.
PS: A good way to avoid testing several applications before finding the right one is reading reviews and comments before making your choice.
- Repair defective applications
Often the phone is working fine but a certain application or function is not, which can cause slowdowns and FCs (force close); depending on the situation there is not much to do but some of these solutions may take care of the problem:
The first thing to do is to uninstall and reinstall the apps via Play Store to make sure that the problem was not caused by a corrupted file when you downloaded the application, if the problem persists there are some more advanced alternatives: in the advanced settings of your recovery select fix permissions, this function should make sure that every application has the necessary permissions to work properly.
- Keep some free space
Full memory is often a problem on any device, especially in older phones like ours, after all the more files the longer it takes read all these files if it is necessary, so the tip is this: the more free space the better.
This step seems a little redundant since we already talked about having the smallest possible number of applications but this time we are also talking about other files. Anything occupying space on your phone is "bad"; too many photos, songs, text documents, etc.. can make the phone slower and lets be honest, you do not need to carry 150 photos of your last weekend with you all the time.
A solution to this problem is simple, try to keep the memory of your phone as free as possible by eliminating caches, unused files and moving applications to the SD card (Settings> Applications> Manage Applications> choose the application and select Move to SD card or use apps like Link2SD); your SD card should also be kept clean by eliminating unused files and traces left by already uninstalled applications, such traces are sometimes hard to find and applications like SD Maid can help you eliminate much of this "junk".
- Avoid keeping some applications running all the time
It’s very common to close an application and assume that it stopped running on the system but this is not always the case because it actually still cached in the memory of the device, Android makes it to be faster on reopening it later and often the system itself definitively closes the application automatically but that’s not always the case.
Firstly it is important to prevent certain applications from even opening and to do this we use apps known as Startup Managers, there are several options in the Play Store but I particularly like Autostarts. Once inside your Startup Manager you can choose which applications will be opened as the system is started or any action is taken (for example changing the state of your Wi-Fi); the ideal is to minimize the number of self-starting applications, leaving only the truly necessary ones without forgetting to be very careful to avoid stopping system applications because if they are unable to open themselves it can cause instability. Another way to prevent applications from opening or stay on cache all the time is to disable automatic updates of apps such as email clients and social networks but this is a more personal matter that varies from user to user, just remember that the more constant the updates are, the more time these applications will be running in the background and more power (CPU and battery) will be consumed.
Now that we’ve already took care of the self opening apps it’s time to find out when you really need an app to be closed for sure.
It's easy to know when to quit an application completely but it is necessary to first understand a basic concept about the system: applications and processes cached in memory are not always a bad thing, in fact as stated at the beginning of the topic they are a good thing because the application should open faster when launched again (hence the use of Task Killers usually worsens more than help if not done properly) but if you use an application to view the weather every morning and will only use it again the next morning this application can be closed without problems.
In our current official version of Android (2.3) already have a task manager that can be used to do this action (Settings> Applications> Running services > select the desired process and press Stop) but if you want a more advanced option there are several Task Managers that monitor processes and can be used to close them too.
PS: Again about the Task Killers: although its use is discouraged for the day-to-day because of the reasons already explained, if you plan on haevy gaming they can be the great saviors since these games need a lot of free memory to run without lags.
- SMS: clean your inbox
Message apps, both native and third-party tend to take quite some time to open if you have many messages on your mobile because everytime you run your message app it needs to load a large list of conversations, so cleaning your inbox periodically helps performance, the same goes for call log.
A tip for those who want to clear the messages inbox and call log without losing your information is backing up with applications like SMS BackUp + that emails you both your conversations and call logs, all within a specific marker so they won’t end up messing the inbox of your email or if your intention is to save only one or two most important message the native client and most ones available at Play Store have the option of forwarding SMS, simply by holding your finger over until the action menu opens up.
- Give your device a break
Like conventional systems for computers, Android also collects information in its memory and despite the “dumping information system” some of it is left in cache , which ends up requiring more processing on your device.
To end this there is a very simple solution: give a rest to the phone. Once a day or when you feel like the machine is running slow give it a reboot or shut down and leave it off for a minute or two before restarting, it should get rid of the cache and it can boost the speed of the phone, but attention: restart the machine and making it open up various apps on boot has no point so keep your boot clean (see related topic).
- About some specific applications:
Task killers (that goes for any app of this kind) are good for a heavy gaming experience (eg: GTA, Dead Space, Asphalt...) because those games need a lot of free RAM but for everyday use is preferable to don't use task killers and keep some of the apps in the cache so they open faster when they are requested again.
Deep sleep is an important part of the ROM performance when it comes to battery usage, applications like CPU Spy can check if this function is working correctly or No-frills CPU Control which in addition to monitoring provides the ability to adjust the frequencies and governors you want to use in your phone.
Chainfire3D is an useful app to change the way your GPU will work and customize it to gain performance or quality , notice that these values ​​tend to be inversely proportional.
Try always to use the lightest possible applications, it helps in memory. I for one think the galleries and music players of almost all default ROMs are too heavy and prefer apps like QuikPic and UberMusic.
Finally I would like to thank: XDA Users: Oodie, x10forevers, Vasishta Reddy, DiKeJ, 9Lukas5, FeraVolt, alzbac, Websites: lifehacker.com, limitlessdroid.com , doctor-android.com, androidcentral.com for helping with the tips on this guide and say that if you have a tip that is not in this guide feel free to share with us!
PS: I'm sorry if I made some grammar mistakes, English is not my first language and this is a pretty big article.

thanks...nice one..

Dude I screwed my music thing on x10 . Please help . Tried flashing xperia s music player . Now music icon has dissapeared . N power button seem to reboot all the time . Will updating binary files of xrec n then flashing again help ?
Please tel . Desperately.
Rooted x10 2.3.3 stock Rom
Sent from my X10i using xda premium

theMoiz94 said:
Dude I screwed my music thing on x10 . Please help . Tried flashing xperia s music player . Now music icon has dissapeared . N power button seem to reboot all the time . Will updating binary files of xrec n then flashing again help ?
Please tel . Desperately.
Rooted x10 2.3.3 stock Rom
Sent from my X10i using xda premium
Click to expand...
Click to collapse
Hey dude, I don't really know how to help you because I haven't had any similar problems but I'm pretty sure that you should try the basics: clear caches (dalvik included) and fix permissions.
Since I'm not a developer I can't really help you with the binary files but try reaching your ROM's developer and he might help you
I hope you get your phone fixed

Dude u sure that I should clear off dalvik cache ? I tried fixing permission but still nothing . The power button rebooting the phone is more irritating than not having a default music PLAYER . Im asking in this forum but havent got the solution yet :'(
Sent from my X10i using xda premium

Excellent post Buddy . Hope you update the thread with other power users opinions & Tips .
Thanks.
Oodie.

theMoiz94 said:
Dude u sure that I should clear off dalvik cache ? I tried fixing permission but still nothing . The power button rebooting the phone is more irritating than not having a default music PLAYER . Im asking in this forum but havent got the solution yet :'(
Sent from my X10i using xda premium
Click to expand...
Click to collapse
I think that the only people that can help you are the ones on your device's specific forum man, try creating a topic there
Sorry but I really don't know what to do to fix your phone

Some of the tips are a complete waste of time and utter crap (mostly those related to keeping RAM usage low and task killers [EDIT: actually, you contradict yourself on these points], giving the device time to "adapt" to the environment -seriously?- and going for the lighter apps -this obviously applies if you have an outdated device, but it's not a rule).
EDIT: Forgot to say that the rest is good.

GermainZ said:
Some of the tips are a complete waste of time and utter crap (mostly those related to keeping RAM usage low and task killers [EDIT: actually, you contradict yourself on these points], giving the device time to "adapt" to the environment -seriously?- and going for the lighter apps -this obviously applies if you have an outdated device, but it's not a rule).
EDIT: Forgot to say that the rest is good.
Click to expand...
Click to collapse
As I said the guide was wrote based on Xperia X10 user experience so it is kind of an old device.
About the RAM management you won't have any issues with a top device with a lot of free RAM but in our case (old device users) we have about 256mb or less RAM to work with so keeping it well managed is essential if you want your device to run smooth.
The adaptation thing seems like BS but it's not, because your device need to create/edit some files as its being used and that's what this part of the article really means. For example your battery writes a log about its own capacities (making a long story short by recalibrating your battery all you do basically is reset this log)
Thanks for the feedback, hope you found something usefull

GuilhermeXOT said:
As I said the guide was wrote based on Xperia X10 user experience so it is kind of an old device.
About the RAM management you won't have any issues with a top device with a lot of free RAM but in our case (old device users) we have about 256mb or less RAM to work with so keeping it well managed is essential if you want your device to run smooth.
Click to expand...
Click to collapse
No, it's not essential. It's actually bad.
The lifehacker website seems to be down, so I'm giving you a link to this article instead (the article itself links to three more detailed articles; one of them is the lifehacker article I wanted to link; do read them): http://androidandme.com/2011/11/app...lers-still-dont-give-you-better-battery-life/
EDIT: Regarding the battery, draining the battery (to 0% or close) is actually bad for lithium based batteries and should be avoided. A discharge to 15% is usually enough.

GermainZ said:
No, it's not essential. It's actually bad.
The lifehacker website seems to be down, so I'm giving you a link to this article instead (the article itself links to three more detailed articles; one of them is the lifehacker article I wanted to link; do read them): http://androidandme.com/2011/11/app...lers-still-dont-give-you-better-battery-life/
EDIT: Regarding the battery, draining the battery (to 0% or close) is actually bad for lithium based batteries and should be avoided. A discharge to 15% is usually enough.
Click to expand...
Click to collapse
I get your point and I also talk about the same thing as the article in the guide: "the use of Task Killers usually worsens more than help if not done properly" , I just didn't elaborated on this very much.
Now, what I'm saying is that if you are a day-to-day user you don't need a task killer and it's recommended ONLY for a gaming experience, aka heavy games like GTA, Dead Space, etc...
"Task killers (that goes for any app of this kind) are good for a gaming experience but for everyday use is preferable to keep some of the apps in the cache so they open faster when they are requested again."
I'm not a task killer fan myself but if you check any gaming rom (DikeJ's for x10 is a good example) you can see that the developers try to maximize the free RAM because those heavy games use a lot of it.
So in order to avoid this kind of confusion I'll edit the article to solve this misunderstanding thx for the heads up

GuilhermeXOT said:
I get your point and I also talk about the same thing as the article in the guide: "the use of Task Killers usually worsens more than help if not done properly" , I just didn't elaborated on this very much.
Now, what I'm saying is that if you are a day-to-day user you don't need a task killer and it's recommended ONLY for a gaming experience, aka heavy games like GTA, Dead Space, etc...
"Task killers (that goes for any app of this kind) are good for a gaming experience but for everyday use is preferable to keep some of the apps in the cache so they open faster when they are requested again."
I'm not a task killer fan myself but if you check any gaming rom (DikeJ's for x10 is a good example) you can see that the developers try to maximize the free RAM because those heavy games use a lot of it.
So in order to avoid this kind of confusion I'll edit the article to solve this misunderstanding thx for the heads up
Click to expand...
Click to collapse
Cool, thanks for that

Buddy, that guide is awesome written, excellent work. And big thanks for credits - I'm very proud that I could help in that "project" ^^. It's should hit XDA Blog . Cheers .

DiKeJ said:
Buddy, that guide is awesome written, excellent work. And big thanks for credits - I'm very proud that I could help in that "project" ^^. It's should hit XDA Blog . Cheers .
Click to expand...
Click to collapse
I'm the one who have to thank you
People please share your ideas so we can make this guide better!