I have done searches on boot times and other than reading the article about the guy who propsed to his fiance on the boot screen of her phone I did not see a real answer to my question/concern.
I have noted that after having installed about 60 apps my tablets boot time is now double. It went from 37 seconds to about 75 seconds.
I have run several "startup manager" apps but mostly they find that many apps have added items that run post boot. I have disabled those and it makes no difference.
What other than the fact that the apps occupy space in memory causes this kind of change in my startup time?
I am not thinking so much that I want/need fast bootups, rather that if these apps are causing slow boot times, what else are they doing to my tablet? Such as lesser performance overall due to running processes etc...
Constructive input would be appreciated, Thanks!
Related
I suspect there is a memory leak somewhere in the Sense UI or or in Android. When I boot my phone and kill all the apps I don't want running, I see 96MB of free ram. But after a day, with the same apps running, I am down to 46MB. This has the result (or so I assume) of making my phone feel more sluggish even though I'm running the same apps. Rebooting fixes all the sluggishness, and the Hero flies. Is anyone seeing the same thing?
I've been using it since launch and haven't had much lag.
You can always try a hard reset if its that bad.
Test it while using regular home and kill sense UI, see if there's a difference.
Well, I only get a lag from time to time. It's just that I noticed this increase in memory usage for no particular reason. I'll try to track down the offending apps if I can. I might try a hard reset though. Can't hurt.
I notice that the browser and my exchange "mail" process freeing up the most memory when I use Advanced Task Killer to "Auto-End" all non-excluded apps every hour.
Once, the mail app was taking up 30mb of RAM. It's not uncommon for the browser to take up 20 or more either. After a while, I also see what you mean, in that when I first start my phone with the same 6-9 system processes I have anywhere from 90-100MB free, and after a while when killing them, I can only get to 75-80 free.
Since I had the Mogul a while back, I tend to watch RAM closely since that phone only had a measly 20 free after boot.
Same Here
I'm seeing the same thing as well. I use TaskPanel X to track memory usage and apps. Likewise the memory seems to slowly decline over time. Additionally even if I kill all the non-critical apps so it is like it was when it booted, I'm still about 30-40MB less than after a fresh boot.
I have been experiencing some strange behavior, but I am a backup whore, so this is more curiosity than anything else...
Whenever I read up on VC, ti seems that a best practice is to test setting for at least a day to ensure that you are stable with them before saving as boot settings.
I do this - on the regular. The weird thing is that I will test settings for days on end with no issue, but as soon as I save as boot settings, teh next boot chugs me into FC hell and/or boot loops.
I *think* I may have noted the issue lying in the fact that the app was on teh SD card, and I a *hoping* that that is where the issue lies. I mean, until the media scanner is complete (and I have the scripts that speed that up [running the 3072 version at present]) most, if not all apps that are on the SD card are not listed in the app drawer, and it seems to populate as they are scanned... So it would make sense in my noob-mind that the settings cannot be made at boot per se until teh scan is past voltage control... Does this make sense?
I have moved it back to the internal memory and am ready to give it a try, but thought I'd toss the thought out there and see what others think...
TIA.
i would think you'll have better results this way. just like you said it couldn't possibly get the information as it boots if it hasn't scanned the card yet. or at least i wouldn't think it could.
post your results, im curious.
Well it was a sound presumption. Went ahead and set boot settings, rebooted and it did the trick.
Very pleased.
Swyped on my Fascinate - please excuse any swypo's...
Hi all.
After switching around from ROM to ROM, the main issue I seem to be facing all the time is that the ROM's start out pretty fast and stable, but after I load up all my stuff, they all start bogging down. Now this is to be expected. I have quite a few apps that run in the background and some widgets that also get loaded, etc... But checking my memory manager, I can also see that lots of apps I don't need at the moment and even some games are also hogging memory, despite the fact I haven't launched them since booting or have since killed them with a mem manager. This gets frustrating as at the moment I can identify anywhere from 75 to 125 megs being used for apps and games that load something when I don't need them to do anything right now.
My question is, how do I prevent them from loading or reloading automatically? I have a boot manager, but they aren't in there. Also set memory manager to auto kill every x mins, but this is just a temporary patch since after killing them they tend to reload very fast.
Anyone have a solution? I'd be most appreciative.
Thanks in advance!
Dear all,
I've got a problem that I hear a lot about for different phones but haven't found a useful solution yet (yes, I searched xda as best as I could).
While my phone Android phone (Desire Z, stock 2.3.3, not rooted) used to be pretty swift after I got it, it significantly slowed down over time.
What's bothering me most is that, after using a couple of applications, it takes a couple of seconds to load the launcher, even after having exchanged HTC Sense for LauncherPro which helped for a while.
I'm not a developer but it seems logic to me that that once powerful phone is still there and is only crammed up with useless processes/background operations by useless/inefficient apps.
So here are my questions:
How can I clearly identify apps which slow my phone down? Is there a way to limit their damage?
How much internal memory or RAM needs to be available before memory becomes a performance issue? Right now, I have 220MB internal storage and 71MB RAM available.
Can I selectively and completely turn off apps while I don't use them without uninstalling them?
Can I switch background operations on and off (e.g. I will definitely survive without some rarely used social apps checking for messages)
Can I change how often an app is active while I'm not using it actively (e.g. have whatsapp check for new messages only every 5 minutes)
I'd appreciate any answer!
Best regards & Thanks in advance
Not sure if it is wrong, just would like to get some explanation of this. Phone has bit less than 1GB ram available for apps and default behavior of Androuid should be to use it all for caching recently run proceses, because there is no difference if memory is free or taken - it uses same power.
I have Viper ROM 1.06 and using Nik3r kernel, tested with and without dataswap mod (128MB). Even tried to tweak Viper settings for minfree setting, using Multitasking ultimate profile. And still the same behavior. When I check available memory, it always sits around 750 used out of 980MB. Regardless what and how many apps I run.
Problem is, that when phone is not used for some time I see almost every time apps starting instead of fast switching from memory. Its mainly visible for me on FBReader, which I use to read ebooks every time I have little spare time. I pull phone from pocket, start FBReader and voila, it is starting from scratch loading book. Its 2-3s, but still. its relatively small app, shouldnt be killed most of the time thanks to system policies on free ram.
When I try to play with phone and run as many apps (start FBReader, home and run Chrome+load 2 tabs, run Camera, run Viber, run Tapatalk and back to FBReader) to force it to close my FBreader from memory, everything works fine and it swaps back in immediately. Even though checking Apps tab in settings shows memory usage about 750-800/980, not fully stuffed with cached apps (think its not showing correct numbers? Or not showing memory taken by apps in empty state?). But anyway. I give up, turn off my phone and let it be for some time. Then I check for example for SMS and would like to continue reading my book. And FBReader is loading as if it was closed. Why?
Seems to me like phone does cleaning of cached stuff in memory after some time when it is not used? Cant say precise when it happens, it just annoys me to see that system shows all the time around 750/980MB used and still is unable to keep my app in memory for longer period when it works fine if I test it directly.
Any ideas/tips/explanation?
Hi, I have the same issue with the fb messenger (chat heads)
I
Android still shut down and it doesn't restart...
Any idea ?
Sent from my ARCHOS 80 COBALT using xda app-developers app