Related
Ok, so there are task killer threads that lead me to believe that they a are a waste of time by and large, and that android automatically sorts things out. Those same posts also point out that task killers are an extra drain on the battery having to start applications over again uses more battery than leaving something dormant in the background. These posts are not the thoughts of one person but unanimous to those threads. All very well, but then there are the battery saving threads that say to close down all applications that aren't being used to save additional battery??? Again this is the view of everyone in those particular threads, so is there any chance of getting the two camps to FIGHT! And then I can decide which I shall choose to do!
For info I currently have task killer and use it all the time and get a full days use out of my battery which is good because I cane the hell out of it! But If I could improve it that would be good. I have however this afternoon decided to not use task killer for a few days and see how I get on. But an explanation would be good from both sides.
I never use a task killer and get 2 or 3 days use out of of my Desire. No point in a war just use your Desire for a week without a task killer and then a week with. I am pretty sure you will just find the task killer slows things down and doesn't improve battery life. You will not find any of the ROM chefs using a task killer either!
HI
I was reading one of those posts this morning and decided to uninstall task-killer.I have to say that after half day of heavy use my device started to be so laggy it took contacts or calendar 5 seconds to open!then I checked running processes and pretty much everything I was playing with was still running.memory dropped to 10MB and device became unusable.cannot say battery use has improved.I think it was the same.
But my task-killer is back up and running.
I must say that I am new to Android.I was using WM for long time.I can cook my own ROMs so I am not a noob but I know very little about Android.so if anyone knows what could be the reason of this huge slowdown I will be grateful for explanation.
And one more thing that needs to be said...
My device is rooted and I am using a2sd too.
polystirenman said:
HI
I was reading one of those posts this morning and decided to uninstall task-killer.I have to say that after half day of heavy use my device started to be so laggy it took contacts or calendar 5 seconds to open!then I checked running processes and pretty much everything I was playing with was still running.memory dropped to 10MB and device became unusable.cannot say battery use has improved.I think it was the same.
But my task-killer is back up and running.
I must say that I am new to Android.I was using WM for long time.I can cook my own ROMs so I am not a noob but I know very little about Android.so if anyone knows what could be the reason of this huge slowdown I will be grateful for explanation.
And one more thing that needs to be said...
My device is rooted and I am using a2sd too.
Click to expand...
Click to collapse
You may like to read this:
http://geekfor.me/faq/you-shouldnt-be-using-a-task-killer-with-android/
dhiral.v said:
You may like to read this:
http://geekfor.me/faq/you-shouldnt-be-using-a-task-killer-with-android/
Click to expand...
Click to collapse
well.i did read that before.that is why i do not understand why my phone was so slow.they are claiming that android should close apps by itself to reclaim memory.but in my case that wasn't true.everything was running and nothing was getting closed by system.
Here's another good read:
Google and Cyanogen comments imply task killer/manager apps are pointless
Both Dianne Hackborn and Cyanogen say Task Killers are useless, even developers of these apps concur. You should listen to them, I guess they understand juuust a little bit more than we do what Android is about.
pascanu said:
Here's another good read:
Google and Cyanogen comments imply task killer/manager apps are pointless
Both Dianne Hackborn and Cyanogen say Task Killers are useless, even developers of these apps concur. You should listen to them, I guess they understand juuust a little bit more than we do what Android is about.
Click to expand...
Click to collapse
i would like to believe it.i was so excited when i saw a post saying that i should get rid of task-killer.but as i wrote before after half day of heavy use(my phone is new so i play with it a lot :-D ) without task killer my phone was soooooo slow i couldn't use it anymore.today i had task-killer back on the phone and all day no slowdown what so ever.i don't understand that.i am starting to think it is related to A2SD and memory being relocated to SD card.
I also agree that taskkiller (the way it works for WM) is not good for android, because android has a better memory management...
but there is another flavour of taskkiller in the market... which are based on this:
How to configure Android's *internal* taskkiller
Unfortunately, your phone needs to be rooted before you can use that method.
If you worry about memory remember that the worst kind of memory is...free memory ! Because it's not being used. Obviously ram gets reclaimed and freed when it's needed.
As said in a couple more redundant threads, there might be a rogue app which you are better off closing because it stays in the background wrongly eating cpu cycles, but this is very very rare. Otherwise I think it's just the usual placebo effect...
andycted said:
If you worry about memory remember that the worst kind of memory is...free memory ! Because it's not being used. Obviously ram gets reclaimed and freed when it's needed.
As said in a couple more redundant threads, there might be a rogue app which you are better off closing because it stays in the background wrongly eating cpu cycles, but this is very very rare. Otherwise I think it's just the usual placebo effect...
Click to expand...
Click to collapse
Have you read the link in my previous post?
ANOTHER thread about this... There must be plenty of threads on this now, but I'll just once more give my impression.
Personally I have had HTC widgets like NEWS or MAIL or CALENDER hang or crash on me and I could not restart them unless I restarted the phone. In this case an app killer was ESSENTIAL. I don't believe you need to leave the app killer running always and kill every single task when your done, but its essential to have one installed so if a widget hangs (as has happened quite a few times on the Desire) you can kill the hung app without having to try a 5 hour shut down(another desire issue) and battery removal.
Also... after 2 days use of many apps and camera use and internet and youtube app etc, your internal RAM will be about 50mb available to programs. yes, android is supposed to kill stuff as it needs, and Im sure it does, but 50mb free memory compared to 150mb the lag is VERY obvious. So I do tend to kill tasks like camera and youtube etc if I have not used them in a day and my phone seem slaggy. the phone definetly runs faster then. Thats just a fact. So the internal android task killer is not as efficent as you'd like to think. Android 2.2 runs 450% faster than 2.1 so maybe then no lag will EVER be noticable. I'll still keep a task killer installed though in case widgets crash or hang.
I found my battery most efficient with this setup:
- Installed Advanced Task killer (free)
- Security level: High (it doesn't show system apps)
- I have put all frequently using apps on ignore list: ATK, Messages, BatteryTimeLite, Internet, Weather, Clock, Calendar (so Android manage with those apps)
- Auto kill Level: Safe
- Auto kill Frequency: 2 hours
With that setup battery lasts almost half time longer than without TK or with killing all apps when screen goes off. Also I don't have any force closes / lag.
Never experienced lag at 100 or 20 mb free.
mcgon1979 said:
but 50mb free memory compared to 150mb the lag is VERY obvious.
Click to expand...
Click to collapse
The amount of free memory doesn't necessarily have anything to do with lag.
As Android does not use virtual memory (unless you've hacked in swapper, which is a bad idea anyway), it will attempt to make best use of available memory which may mean keeping recently used items in memory, and thus "consuming" free memory. However, if those items are not actively processing, they should not be consuming CPU cycles and therefore consuming little to no power.
As far as a running system is concerned, having lots of free memory just means that it is being underutilized.
I don't kill tasks and my phone never lags - that's just a fact too!
Regards,
Dave
boge said:
I also agree that taskkiller (the way it works for WM) is not good for android, because android has a better memory management...
but there is another flavour of taskkiller in the market... which are based on this:
How to configure Android's *internal* taskkiller
Unfortunately, your phone needs to be rooted before you can use that method.
Click to expand...
Click to collapse
Using this method it is possible to make the native task killer a bit more aggresive. I did some experiments with this on the HTC Hero and it just might have improved speed slightly but at the expense of stability.
"Normal" task killers are completely pointless but if people want to use them why not? It they want to sacrifice both battery life and performance by using one surely that is their choice. Whatever the experts says will not convince them.
I suppose you could use one to kill the very occasional hung app. i.e. Once every few days, but most people seem to use them constantly and totally indiscriminately.
1. About Cpu: get a task manager with cpu monitoring and verify for yourself, frozen applications in background don't do anything.
2. About memory: If an application needs 10 MB it just uses 10 MB and couldn't care less if there are 11, 100, 1000 MB free. The only moment you COULD see a tiny slowdown is the instant it needs 20 and there are only 10 available, but the system is quite good in managing that, and freeing resources (there are six levels of memory cleaning which progressively remove unused applications from the background)
3. If you stop monitoring memory usage, stop worrying about the system, you'll find out it manages itself perfectly and you enjoy the phone a lot more.
Interesting article about installed apps and a battery.
http://blog.gsmarena.com/android-handsets-batteries-should-last-for-more-than-a-day-google-says/
"...Page accused the installed apps of causing the problems and claimed that software running in the background exhausts the battery quickly...."
Interesting article about installed apps and a battery.
http://blog.gsmarena.com/android-handsets-batteries-should-last-for-more-than-a-day-google-says/
"...Page accused the installed apps of causing the problems and claimed that software running in the background exhausts the battery quickly...."
Click to expand...
Click to collapse
as said in the post above, get a cpu monitoring task manager and see for yourself if you have something wrong. Personally I don't have any.
Also watch battery history which tells you if the phone doesn't manage to go properly to sleep (partial wake)
regarding that article, iphone users get way less battery time and they don't even have multitasking...
-------------------------------------
Ipad's dont have "Spell Check" thery have "Replace" built into Safarii adn it wokrs just fineq!!!
I personally installed auto memory manager, an app that configures android's internal task killer. Its not a task manager by itself, uses android's task manager. You can set the limits in MB for all the app categories android has.
I was using it in my hero as well and found it really useful. Before having it installed, after some time my free memory was ~50mb, thus my phone was sometimes lagging. Now its always above 100mb and no lag at all
I just installes arhd 2.1 rom and evrrything works fine.
I got most things installed.i need like twitter, fb, adv. task killer,
even auto startup killer, titanium, juice, setcpu and some more.
I disabled all notifications.
I prevent all startup apps i didnt want (all but 2,or 3)
I set sync to off. I checked all app settings twice.
Still there.are mostly like all apps running after i start my phone
And if i kill them it takes a while but they come back...
How to fix that ? Beside all my programms things like internet, mail, messages are also on.
My ram is down to like 210mb, when i kill its back to 480.
Thanks guys!
Android is nothing like windows.
Killing apps & processes to save memory is bad for your phone. Android handles its memory very well, and you killing apps interferes with that.
Apps are loaded into the RAM, for your convenience, if Android runs low on memory, it will decide what apps to kill.
I'm sure there is a guide that explains this.
andyharney said:
Android is nothing like windows.
Killing apps & processes to save memory is bad for your phone. Android handles its memory very well, and you killing apps interferes with that.
Apps are loaded into the RAM, for your convenience, if Android runs low on memory, it will decide what apps to kill.
I'm sure there is a guide that explains this.
Click to expand...
Click to collapse
So (Auto)-Taskkillers are Bull**** ?
Also Startup Prevention ? Everything like that ?
Or anything "good" ? I guess SetCpu is something useful which comes
into that area.
If someone has a guide, give me a "call"
Task killers should only be used to kill rogue apps, apps that are poorly coded. They shouldn't be used to manage your memory.
SetCPU is kinda different, all it does is allow you to alter the speed of your CPU.
mydanny said:
So (Auto)-Taskkillers are Bull**** ?
Also Startup Prevention ? Everything like that ?
Or anything "good" ? I guess SetCpu is something useful which comes
into that area.
If someone has a guide, give me a "call"
Click to expand...
Click to collapse
I find it very difficult to understand people who are using taskillers in their phone. The whole point, i guess, is to save some battery? But do you know that taskillers run constantly and consume even more battery? And you might end up messing up with your system and experiencing lags/problems.
The memory management of android system is different than what we are used to. You should let android manage the memory. If you still want to quit some of the apps which you think are using up your memory, you can do it manually via "manage applications" in applications.
I m also using ARHD. And i don't use any taskillers/ startup managers. I never experienced lags when playing gameloft games (i tell you they require lots of memory) or angry birds. I have my wifi-on, sync on all the time.
SetCpu is used to manage the cpu speed of your DHD. This can be used to create profiles (or comes already with some profiles like ondemand etc.) and the program itself understands the need for memory and adjusts your cpu speed according to that. It might give you some more bat. life.
Of course what kind of programs we want to use in our DHD is upto us. And people will have a divided opinion on whether to use taskillers or not. But if you ask me (and my almost 3 years of android experience), you are better off without any taskillers.
sphuyal said:
I find it very difficult to understand people who are using taskillers in their phone. The whole point, i guess, is to save some battery? But do you know that taskillers run constantly and consume even more battery? And you might end up messing up with your system and experiencing lags/problems.
The memory management of android system is different than what we are used to. You should let android manage the memory. If you still want to quit some of the apps which you think are using up your memory, you can do it manually via "manage applications" in applications.
I m also using ARHD. And i don't use any taskillers/ startup managers. I never experienced lags when playing gameloft games (i tell you they require lots of memory) or angry birds. I have my wifi-on, sync on all the time.
SetCpu is used to manage the cpu speed of your DHD. This can be used to create profiles (or comes already with some profiles like ondemand etc.) and the program itself understands the need for memory and adjusts your cpu speed according to that. It might give you some more bat. life.
Of course what kind of programs we want to use in our DHD is upto us. And people will have a divided opinion on whether to use taskillers or not. But if you ask me (and my almost 3 years of android experience), you are better off without any taskillers.
Click to expand...
Click to collapse
Word. Sounds convincing.
I will remove the **** from my phone - Task Killer and Startup Manager.
You also dislike Juice Defender ? I heard only positive things about battery.
Or is this 100% crap, too ?
mydanny said:
Word. Sounds convincing.
I will remove the **** from my phone - Task Killer and Startup Manager.
You also dislike Juice Defender ? I heard only positive things about battery.
Or is this 100% crap, too ?
Click to expand...
Click to collapse
I have never used Juice Defender but it is a OK app (it uses some bat. though). All i use i "currentwidget" to monitor what causes battery drain (if any). If i were you, i would see how the DHD goes along with/without juice defender for 48 hours. And then evaluate if i really need juice defender.
Killing apps is liking turning your car engine off on every street you go down. It's better to keep the engine running, it uses less petrol.
Same with memory management on Android, if you keep killing, it has to startup the app again each time you use it which actually uses more battery.
The only thing I use is setCPU on a smartass governor with a profile for when the screen goes off to reduce CPU usage to 450mhz. Mine idle's at 1-3ma.
What a bunch of rubbish. Task killers are an excellent easy to keep your phone running fast and smooth. They also save your battery by not letting tasks run in the background and eat battery unnecessarily.
I hope that wasn't too obvious a troll ...
Task killers suck. They are the Android equivalent of Windows registry cleaners. Sold to you to speed up your system but really they break it.
Sent from my super slick Android device.
dr.m0x said:
What a bunch of rubbish. Task killers are an excellent easy to keep your phone running fast and smooth. They also save your battery by not letting tasks run in the background and eat battery unnecessarily.
I hope that wasn't too obvious a troll ...
Task killers suck. They are the Android equivalent of Windows registry cleaners. Sold to you to speed up your system but really they break it.
Sent from my super slick Android device.
Click to expand...
Click to collapse
You had me for a minute there
hi, i wanna ask
i download an app manager to my phone,
Facebook,PS Pocket,Xperia Play,Maps is always there, even i close it on task manager, after a sec, it is there again and eating ram,
and one more thing, i got a problem,
theres no list on "More games" on xperia play,
thanks
Jahy420 said:
hi, i wanna ask
i download an app manager to my phone,
Facebook,PS Pocket,Xperia Play,Maps is always there, even i close it on task manager, after a sec, it is there again and eating ram,
and one more thing, i got a problem,
theres no list on "More games" on xperia play,
thanks
Click to expand...
Click to collapse
Ok first of all there is something you need to understand! NEVER USE A TASK MANAGER! They are useless. Android isnt like windows, having lots of free ram does not improve performance. Infact it hinders it. The following paragraph is taken from lifehacker.
"In Android, processes and Applications are two different things. An app can stay "running" in the background without any processes eating up your phone's resources. Android keeps the app in its memory so it launches more quickly and returns to its prior state. When your phone runs out of memory, Android will automatically start killing tasks on its own, starting with ones that you haven't used in awhile.
The problem is that Android uses RAM differently than, say, Windows. On Android, having your RAM nearly full is a good thing. It means that when you relaunch an app you've previously opened, the app launches quickly and returns to its previous state. So while Android actually uses RAM efficiently, most users see that their RAM is full and assume that's what's slowing down their phone. In reality, your CPU—which is only used by apps that are actually active—is almost always the bottleneck."
As for the more games option. If your using the .145 firmware. You need to reinstall "moregames.apk" if your using the latest firmware. You need to reinstall "fun&games.apk"
oh i see.
ummm more games is lost because of new update?? =.=
where can i get fun&games.apk ?
thankkss
hii, where can i get fun&games.apk?
AndroHero said:
Ok first of all there is something you need to understand! NEVER USE A TASK MANAGER! They are useless. Android isnt like windows, having lots of free ram does not improve performance. Infact it hinders it. The following paragraph is taken from lifehacker.
"In Android, processes and Applications are two different things. An app can stay "running" in the background without any processes eating up your phone's resources. Android keeps the app in its memory so it launches more quickly and returns to its prior state. When your phone runs out of memory, Android will automatically start killing tasks on its own, starting with ones that you haven't used in awhile.
The problem is that Android uses RAM differently than, say, Windows. On Android, having your RAM nearly full is a good thing. It means that when you relaunch an app you've previously opened, the app launches quickly and returns to its previous state. So while Android actually uses RAM efficiently, most users see that their RAM is full and assume that's what's slowing down their phone. In reality, your CPU—which is only used by apps that are actually active—is almost always the bottleneck."
As for the more games option. If your using the .145 firmware. You need to reinstall "moregames.apk" if your using the latest firmware. You need to reinstall "fun&games.apk"
Click to expand...
Click to collapse
See this is interesting. I just installed Task Panel and have it so it closes apps and opens up RAM every time I put the phone to sleep. I did it mostly to save battery. I consistently had my RAM at less than 50MB before the manager. Now it's usually above 120MB. My fear is battery life, and obviously performance in emulators and games like Minecraft.
El_Colombiano said:
See this is interesting. I just installed Task Panel and have it so it closes apps and opens up RAM every time I put the phone to sleep. I did it mostly to save battery. I consistently had my RAM at less than 50MB before the manager. Now it's usually above 120MB. My fear is battery life, and obviously performance in emulators and games like Minecraft.
Click to expand...
Click to collapse
If you learnt about android you would know that you device would function better when you had less than 50mb ram
Sent from my R800i using Tapatalk
I thought SGX540 that's superior than iphone4 would run new games without any lags but for new games such as 9mm and let's golf 3 i've face many stutter on those games. I'd like to ask others that you have problem like me or not ? or maybe next time i'd go back to ios or waiting ice cream sandwich. Those games are smooth in iphone4 but not in galaxy s that has superior GPU.
I didn't play to 9mm and I just tested Lets Golf3, but yeah... it's not strange to have some small lags sometimes.
If gaming on the phone is very important for you I suggest to use samsung roms and not cm7 or miui.
And yeah, maybe you should have buy an iPhone, Android still can beat iOS when it comes to games
im currently on JVT.firmware
Sent from my GT-I9000 using XDA App
I notice the lags too. I strongly believe that the lags are caused primarily by low ram. On Froyo, I never had lags in games, and they were all super smooth. But on gingerbread, after a few hours of usage, the ram drops below 100mb, and the games will lag. The games don't lag on a fresh boot. Hence, the problem is not with the gpu, but with the fact that 512mb of ram is just not enough for gingerbread. If you want to remove the lags in games as well as in the phone interface, I recommend that you flash a 2.2.1 rom. ZSJPK was one of the best roms I've ever used.
Yeah, sgx540 is better than the 535 use in iphone 4, but it's all about drivers and optimisations. And we can't deny that Apple is doing a wonderfull job with iOS.
Sent from my GT-I9000 using xda premium
disclaimernotice said:
I notice the lags too. I strongly believe that the lags are caused primarily by low ram. On Froyo, I never had lags in games, and they were all super smooth. But on gingerbread, after a few hours of usage, the ram drops below 100mb, and the games will lag. The games don't lag on a fresh boot. Hence, the problem is not with the gpu, but with the fact that 512mb of ram is just not enough for gingerbread. If you want to remove the lags in games as well as in the phone interface, I recommend that you flash a 2.2.1 rom. ZSJPK was one of the best roms I've ever used.
Click to expand...
Click to collapse
indeed, i also think the lags are caused by lack of ram...
when you move the camera around in the game it sometimes hangs and when the textures are in RAM, you can continue playing without fps drops or lag
a tip before you start playing:
- root your phone and install "autostarts" to disable all crap which boots up with android
- reboot phone
- after booting go to task manager and cleanup ram
- go to settings => applications => active services and kill unnecessary processes. (for example, when you close the facebook app, it still keeps running as a service, sometimes almost using 50MB ram)
i reduced lag in 9mm alot with the method above...
Is there a custom rom that has a very low ram consumption? that would fix this issues
Simplicitiy is very good!
alwo1303 said:
Simplicitiy is very good!
Click to expand...
Click to collapse
how many ram does system take with that rom?
For games playing, 2.2.1(JSD) is a Must!
titooo7 said:
I didn't play to 9mm and I just tested Lets Golf3, but yeah... it's not strange to have some small lags sometimes.
If gaming on the phone is very important for you I suggest to use samsung roms and not cm7 or miui.
And yeah, maybe you should have buy an iPhone, Android still can beat iOS when it comes to games
Click to expand...
Click to collapse
... what? You're suggesting Samsung over CM7/MIUI when you want more performance? Are you trying to troll or something?
_breez_ said:
indeed, i also think the lags are caused by lack of ram...
when you move the camera around in the game it sometimes hangs and when the textures are in RAM, you can continue playing without fps drops or lag
a tip before you start playing:
- root your phone and install "autostarts" to disable all crap which boots up with android
- reboot phone
- after booting go to task manager and cleanup ram
- go to settings => applications => active services and kill unnecessary processes. (for example, when you close the facebook app, it still keeps running as a service, sometimes almost using 50MB ram)
i reduced lag in 9mm alot with the method above...
Click to expand...
Click to collapse
Reboot my phone. Clear memory with task manager. Kill active services... just to game? Why not just close some apps? Common sense, people. It's a brilliant thing.
lpalvaro said:
Is there a custom rom that has a very low ram consumption? that would fix this issues
Click to expand...
Click to collapse
Yes, it's called V6 Supercharger Script. It's like a ROM, but it's actually just a script... and you can run that script on whatever ROM you want. What it does, is it lets you pick a number. That number decides how much free RAM you'll have. Then, like magic, you just have it.
There hasn't been a single piece of good advice in this thread...
upichie said:
Yes, it's called V6 Supercharger Script. It's like a ROM, but it's actually just a script... and you can run that script on whatever ROM you want. What it does, is it lets you pick a number. That number decides how much free RAM you'll have. Then, like magic, you just have it.
There hasn't been a single piece of good advice in this thread...
Click to expand...
Click to collapse
I can't use supercharger with semaphore kernel, and CF bigmem settings (98 mb) doesn't solve the performance issue.
lpalvaro said:
Is there a custom rom that has a very low ram consumption? that would fix this issues
Click to expand...
Click to collapse
No, custom roms, even so called simple and bare ones, use more ram than stock roms. I recommend ZSJPK 2.2.1, which has about 180mb of ram on boot, and an average of 120-140mb or ram after two days' usage.
lpalvaro said:
I can't use supercharger with semaphore kernel, and CF bigmem settings (98 mb) doesn't solve the performance issue.
Click to expand...
Click to collapse
Then you do it without the script. What's the problem here? I have over 2,000 games on my phone. And no, that wasn't a typo. None of them lag.
upichie said:
Reboot my phone. Clear memory with task manager. Kill active services... just to game? Why not just close some apps? Common sense, people. It's a brilliant thing.
Click to expand...
Click to collapse
because android automatically closes apps when RAM is low and services always keep running in the background, whether you need them or not.
why would you let a service use your ram when you don't even need it? THAT is common sense.
bigmem kernel may help? its what i use
upichie said:
... what? You're suggesting Samsung over CM7/MIUI when you want more performance? Are you trying to troll or something?
Reboot my phone. Clear memory with task manager. Kill active services... just to game? Why not just close some apps? Common sense, people. It's a brilliant thing.
Yes, it's called V6 Supercharger Script. It's like a ROM, but it's actually just a script... and you can run that script on whatever ROM you want. What it does, is it lets you pick a number. That number decides how much free RAM you'll have. Then, like magic, you just have it.
There hasn't been a single piece of good advice in this thread...
Click to expand...
Click to collapse
Learn some manners, people here are just trying to help. Have you actually tried the two games mentioned in op, you tell us you have 200 games installed is 9mm and lets golf included in these?
Sent from my GT-I9000 using XDA App
I've rolled back to froyo and now without apps in the background i0ve about 140mb of ram used, and now 9mm goes smooth. I'm not moving from froyo any more.
Also, now the battery lasts in 6 hours of screen usage, and with jvt only 4 hours
_breez_ said:
because android automatically closes apps when RAM is low and services always keep running in the background, whether you need them or not.
why would you let a service use your ram when you don't even need it? THAT is common sense.
Click to expand...
Click to collapse
Do you even use an Android phone?
leroys said:
Learn some manners, people here are just trying to help. Have you actually tried the two games mentioned in op, you tell us you have 200 games installed is 9mm and lets golf included in these?
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Are they though? When I help someone out, I tell them correct information. If I don't know the correct information, I don't tell them anything. Why? Because incorrect information is worse than not helping at all. Few people in this thread have given remotely acceptable advice. No one needs to do a 3-step process, including rebooting your phone, just to play games; likewise, no one needs to downgrade to Froyo in order to game either.
I have Let's Golf! 3D installed currently, but I don't have the most recent revision of 9MM—although I have played it in the past. I have my phone's CPU and GPU overclocked, like I'm sure many of us do here, and I can play both without noticeable lag. I didn't have to reboot my phone to play them. I didn't have to uninstall apps to play them. I didn't have to flash an entirely new ROM to play them. And I certainly didn't need to stand on one leg with the phone above my head to play them.
Bad advice is just bad.
upichie said:
Do you even use an Android phone?
Click to expand...
Click to collapse
I posted what helped reducing lag in 9mm on my phone.
if you don't need the help i posted, that's too ****ing bad. the fact this topic was started shows people are facing the same problem with lack of usable ram memory for 9mm.
looks like you have some sort of magic phone with unlimited amounts of ram memory that never lags
the reason why i told him to reboot his phone is because ram usage is much less in most cases, right after booting up.
and btw, next time do some more effort instead of posting one line if my information is not correct
The title is basically the question, im fed up of alot of programs auto opening on my android phone, it takes battery and is slightly annoying receiving notifications off apps i dont really care about such as the NFL game tells me about small things in the NFL, im in the UK, i dont care.
If you argue that it doesnt take alot of battery currently have 117mb free ram, (2 secs later) killed all my selected apps now have 201mb free so im using 80mb of ram on apps im not using. Ive made 2 or 3 phone calls today no more than 30 mins long altogether and ive lost 55% of my battery since about midday, which is when i unplugged the phone.
And I think all these apps are the problem so how can I stop them from auto opening, please help
Search the market for startup cleaner
Sent from my A101IT using xda premium
yusuo said:
If you argue that it doesnt take alot of battery currently have 117mb free ram
Click to expand...
Click to collapse
More free RAM doesn't really equate to longer battery life or lower power consumption.
Better search for auto starts, this asp shows you the conditions an asp can turn back on and you can bin it off, Facebook for example had like 8 conditions, from full to medium battery life, on charge and change in network....... Use it
Sent from my HTC Desire using xda premium
rootSU said:
More free RAM doesn't really equate to longer battery life or lower power consumption.
Click to expand...
Click to collapse
There's still no reason for most of this apps to use RAM. Apps like facebook and skype shouldn't be actice without user permission. Without login they are complete useless.
I'll try Startup Cleaner, thx.
It's how android works and what RAM is for. There is always a reason.
Sure if someone doesn't use Facebook, it should be uninstallable, but its not and its not causing any harm
Sent from my HTC Desire using Tapatalk
The problem isn't that apps start when I turn on the phone its that even after i use task manager to close they keep reopening and use over 100mb of ram, earlier I checked and only had 78mb ram available.
This must have an effect on battery to some degree i want to kinda ban certain apps from running in the background unless i specifically tell them to
RAM doesn't use more power, the more its used, no.
You don't need a task killer. You do not need to obsess about RAM. Forget about RAM and enjoy your phone
Sent from my HTC Desire using Tapatalk
rootSU said:
RAM doesn't use more power, the more its used, no.
You don't need a task killer. You do not need to obsess about RAM. Forget about RAM and enjoy your phone
Sent from my HTC Desire using Tapatalk
Click to expand...
Click to collapse
Thanks for you reply but its not really an answer its more of a contradiction, what I was asking is how to I stop apps from auto starting and eating up RAM, regardless of how long the phones been on
...and I'm telling you its a pointless, unecessary waste of time. Also it is not possible. Autostarts as already mentioned is the closest you'll get
Sent from my HTC Desire using Tapatalk
I also turned off the autorun permissions of a lot of apps, for 2 reasons: 1) a device that is smooth sooner after booting, using less cpu cycles/power. 2) preventing Sense from reloading due to RAM shortage and have smooth multitasking.
1) Android loads a bunch of apps to the RAM that have the autorun permission, until it thinks it is "enough" and useful to you. No matter how many apps you have installed, the amount of free RAM is always about the same, just the number of "unwanted" apps in the RAM differs. Removing the autorun on boot permissions prevents the loading of unnecessary apps that will immediately be removed from the RAM the moment you start the browser/a game, saving cpu cycles=power. So for me there is no point in loading them in the first place, because I am never going to use them (right away). I want the apps that don't to any syncing loaded on demand.
2) I hate slow multitasking and I hate it even more when Sense reloads because it got kicked out of the RAM after each time I press HOME.
I use 3G Watchdog (~12MB RAM), Unlock with Wifi (~8MB), Whatsapp (~15MB), Handcent SMS (~18MB), Droidstats (~13MB), Extended Controls (~12MB), Battery Monitor Widget Pro (~13MB). Okay, I maybe could delete some of them, but these app are "OK" to me, because I use them actively or just need a background service to operate normally.
With Gemini I disabled apps like Facebook, a screenshot tool (just load when I want to make a screenshot..), various public transport planning tools, etc from autostarting.
No joy moment: after using the Facebook app (market version), it may take up 50+ MB and it will not be closed when I start another RAM intensive app, because it is a high priority service. Result: Sense gets kicked out of the RAM. Or, when the situation is somewhat less critical: multitasking is as good as unusable: switching between apps makes them load over and over again, because app2 kicks app1 out of the RAM and vice versa, causing unnecessary lag. Therefore: when I am done with facebook, I close it, then STAY the hell closed It may only autostart when it receives a push message. In that case it is nice to have FB already in RAM when I tap the notification.
Why do even some games have background services, or the Engadget app, or .. , or... all eating precious RAM. And yes, I know, once IN the RAM they eat no battery, but they DO eat battery when the app loads itself back in the RAM when it thinks it needs to, after it got kicked the moment I decided to so something else.
Hmm, spent way too much time to try to explain my frustration Oh and by the way, I have a Legend, but the basics are the same of course.
Dwnload an app called internet commander from the market. It shuts off the internet when your screen turns off but still let's you get calls and texts. I've got my phone , rooted of course, clocked to 710 and my battery will last for days.
Sent from my Eris using xda premium
I just re read your post, that won't help with apps but it will help save battery. And when you turn your screen on the internet kicks right on instantly. Good luck
Sent from my Eris using xda premium
yusuo said:
The problem isn't that apps start when I turn on the phone its that even after i use task manager to close they keep reopening and use over 100mb of ram, earlier I checked and only had 78mb ram available.
This must have an effect on battery to some degree i want to kinda ban certain apps from running in the background unless i specifically tell them to
Click to expand...
Click to collapse
The guys here have already suggested you use a certain program from the Market. Have you tried it?
Regarding the whole RAM consumption issue, Android has its own built-in memory management system that ensures that there's always enough RAM for an app whenever it needs it, even if the memory manager shows like 40 MB free. Basically it "ejects" all background, unused apps, from memory making room for the foreground app which needs it most. If for some reason you need to fiddle with that, you can try using the V6 Supercharger script. I find it suitable for my needs but YMMV. It's completely reversible, so if you don't like it you can uninstall it just like that.
P.S. - I agree with rootSU, the ammount of free RAM has nothing to do with battery consumption. If you suspect that an app is draining your battery, check Android's battery statistics to find the culprit.
TVTV said:
Regarding the whole RAM consumption issue, Android has its own built-in memory management system that ensures that there's always enough RAM for an app whenever it needs it, even if the memory manager shows like 40 MB free. Basically it "ejects" all background, unused apps, from memory making room for the foreground app which needs it most. If for some reason you need to fiddle with that, you can try using the V6 Supercharger script. I find it suitable for my needs but YMMV. It's completely reversible, so if you don't like it you can uninstall it just like that.
P.S. - I agree with rootSU, the ammount of free RAM has nothing to do with battery consumption. If you suspect that an app is draining your battery, check Android's battery statistics to find the culprit.
Click to expand...
Click to collapse
I respectfuly disagree. Android built in ram management is just silly. If I open xda app for example (it could actually be any app for that matter), reply to a few posts, read a few more and close it, why does it need to stay in ram? It reloads anyway when I run it again after I've closed it (using the back button or the actual exit command in the app itself). Why does the camera app need to stay in the background after I just shot a few photos and closed it? Because I may or may not use it again in some time? It's rediculous. And the whole theory that ram management doesn't require any power/cpu usage, how do you guys think all those apps get killed? Android will power?! No, kernel scans all running apps and kills the ones based on built in heuristics so it also reads them first. So that doesn't require any power/battery? Awesome if it's true! Although I wouldn't bet on that. And all this fuss just because you may or may not launch the same app sometime during the next day/week/month/year or it'll eventually get killed? Now that's just plain stupid. I get apps that need services like widgets, push notifications etc. but random apps like root explorer, xda app, titanium, youtube etc. which are opened specificly by the user shouldn't be in ram just for the sake of it after they're closed. I closed it, meaning I don't need it anymore. And I don't need the kernel to scan all apps and running services every time I launch an app so it could provide the free ram that app needs. Consumes cpu time, battery, i/o ... every piece of hardware actually just to free some ram that shouldn't be occupied in the first place. Every app that I ever opened on my phone got loaded almost instantly and that's just after phone had been booted. So after that it should stay in ram so I could open it in a blink of an eye instead of instantly? That's just funny.
Anyway, I'm just thinking out loud so don't flame me immediately. There probably are apsects of it that I didn't mention here or am not aware of. And I'm not saying that I'm right and you guys are wrong, I'm just saying what I know and think about this subject.
-. typewrited .-
PlayPetepp, while it might be true that the OS allocates (thus use) some resources to memory maintenance, the impact on battery life is negligible. In the Android OS, apps in memory are ordered according to priority and state, so the OS always knows which apps to kill first if it needs to make room in RAM, without much of a hassle. The only bad consequence of this system seems to be the fact that once the memory fills up, the launcher may lag or even be evacuated from memory. But, as i've mentioned in my previous post, there are ways to prevent that, either via scripts or, if you know what you're doing, via editing system files.
So the OS doesn't need to scan anything as it keeps everything in memory again? Seems like an endless loop. Open, sort, kill if needed, reopen, sort again, kill ... to what end, constant unneccessary multitasking that user is unaware of? I really don't see any benefit of that system and am only seeing the downsides. I mean, who needs every app they ever run remain in ram even if they close them after using? And then opening another app and "waiting" for whatever needs to be closed to get it running. Sure you can mess with the scripts (init.d, init.rc, etc.) but the underlined conditions stay the same. I hope I'm making sense here. Or am I fighting against windmills.
I just figured out that I strayed from the topic of this thread so won't be continuing this discussion if it's considered offtopic.
-. typewrited .-
Stop looking for excuses for poor multitasking in Sense 3+ roms
erklat said:
Stop looking for excuses for poor multitasking in Sense 3+ roms
Click to expand...
Click to collapse
Hello again nice to see you here
Here's an interesting article on what I was talking about. Sense 3.5 doesn't need that many mbs of ram to work smoothly. After booting and setting everything up I have 150+ mb free. That should be enough for decent multitasking but all those apps not getting killed when you close them are eating too much. Can anyone explain in detail what hidden app, perceptible app, backup app and heavy_weight app means? I've been googling this for a week and can't find any decent explanation.
@PlayPetepp - I think i have already said (in my previous post) that the OS does indeed use some resources for managing the memory, but they are negligible in terms of their impact on battery life. IMHO, the only thing a 3'rd party memory manager (task killer) WILL do is improve lanuncher responsiveness (lag) as the lag does increase when free RAM drops under a certain limit. Thus used wisely, a task killer can improve responsiveness, but battery life... very little, in rare cases (it does the opposite, most of the time).
Regarding the so called "memory slots", here's an excerpt from this article:
FOREGROUND_APP: This is the application currently on the screen, and running
VISIBLE_APP: This is an application that is open, and running in the background because it's still doing something
SECONDARY_SERVER: This is a process (a service that an application needs) that is alive and ready in case it's needed to do something
HIDDEN_APP: This again is a process, that sits idle (but still alive) in case it's needed by an app that's alive and running
CONTENT_PROVIDER: This is apps that provide data (content) to the system. HTC Facebook Sync? That's a CONTENT_PROVIDER. So are things like the Android Market, or Fring. If they are alive, they can refresh and provide the content they are supposed to at the set interval. If you kill them, they can't of course.
EMPTY_APP: I call these "ghosts." They are apps that you have opened, but are done with them. Android uses a unique style of handling memory management. When an activity is ended, instead of killing it off Android keeps the application in memory so that opening them again is a faster process. Theses "ghost" apps use no battery or CPU time, they just fill RAM that would be otherwise empty. When this memory is needed by a different application or process, the RAM is flushed and made available for the new app. To satisfy the geekier people (like myself) Android does this by keeping a list of recently used apps, with the oldest apps in the list given the lowest priority -- they are killed first if RAM is needed elsewhere. This is a perfect way to handle 'ghost' processes, so there's no need to touch this part
Click to expand...
Click to collapse