Related
Not sure if you all are familiar with this app, I haven't seen anyone speak upon it on XDA yet, so just thought I'd share my experience with it.
http://www.androlib.com/android.application.com-lim-android-automemman-wBjq.aspx
IMO, this app is pretty cool. Very simple and easy to use, although it doesn't come with detailed instructions on how to use, so I felt the need to explain a little bit about it:
Tired of lags to and from Dialer/Contacts/Call Log?
Have you ever pressed the call button to dial a number/contact and nothing happens for 10 to 15 seconds then finally the call goes through and starts to ring?
Ever went back to home screen after fooling around with an app, or web surfing the browser only to find that a widget or two is missing or is not loading/refreshing properly?
Gmail not syncing daily as it usually does?
Market taking forever to load up the downloads page or lagging connection with G-talk to promptly start the download/updates you started?
Well these are the memory/background/content provider situations that need to stay snappy if nothing else does, agree?
Then this app may or may not be the answer to all of your problems.
For me it was. First and foremost, it is a FREE app, yay! (at least to my current knowledge, unless developer has changed it)
*FYI* This app does require root permissions, so if you are not rooted this will be of no use to you.
After installing, when first opening the app, super permissions should pop up, just check the always box and press allow for root access. Close the app, then re-open.
Now, there are 4 options you may choose, DEFAULT< CUSTOM< MILD< AGGRESSIVE
Default settings will be what you see on first use, those are the default Android memory settings for your G1
Custom- self explanatory, you move the bars of each memory category according to how you prefer- *Note* the amount shown is not exact memory, it is a threshold, basically a set amount not to exceed, Your phone will automatically choose how much to use according to how much it needs, but its limitations will be set by the threshold you choose. Go ahead and make your adjustments, then click the custom button, this will save these settings. So the next time you want to re-enter those settings, just hit the custom button, and it will restore.
Mild- Simply a preset application setting
Aggressive- Another preset app setting
You choose what works best for you, I would suggest playing around with different settings until you have achieved a memory usage that gives you the most improvement, *Note* Do note mistake this as a speed app, it only controls memory, so don't expect some super fast change, but if you set it up properly, and memory is being managed to the best case scenario of your usage, speed will increase, believe me.
Start with the presets, see how they work throughout the day, if you notice no difference, or worst than it already was, change it to something else.
Personally, my best experience has been with the Aggressive preset. Its been the most effective for my phone, however; this won't be the case for everyone. Aggressive basically raises the threshold for background data(widgets,home, cache, etc.) And content provider (google apps, settings, G-talk and stuff) And Empty application- this means, IMO, the amount of free memory sitting around available, for soon to come data or apps that you might open later, I.E.- multi-tasking, Call screen, new mms or sms
It also lowers the threshold of the foreground and running apps, so that they don't suck up so much memory the phone lags before it can open other things in memory. Get it? But as I stated, different people will have different preferences.
If you haven't already, try it out! If you don't like it, or don't need it...maybe results won't change things enough for you to have any use for it, you can always uninstall, and it won't harm any memory or data on your phone.
Also, regardless of threshold settings, if you open or use more memory than threshold limits, it will not break or crash you phone causing reboots or anything like that. So don't worry. The app does not prevent you from doing anything on your phone, it simply manages it according to your use.
I hope this comes in handy for someone, as it has been more than useful for me on a daily basis. You can find more information via market or the link above.
Don't take offence to this, but any "speedup" you think you are getting from it is entirely a function of the placebo effect.
There is no advantage to forcing memory to remain "free", and in fact, doing something like this will actually make the phone SLOWER than it would otherwise be.
Android has a VERY well thought out memory management system. It keeps a record of processes running and their priorities. In the event that more memory is required for a higher priority application, it will automatically select some other application to kill off in order to get that.
What this does is it ensures that you ALWAYS have the memory FULLY utilized, which means optimal performance under every circumstance.
An unfortunate trap that you are falling into is the traditional view of memory -- for example on a DESKTOP system, you don't have anything killing off unused processes, which means that every program you open will use up more memory, so the more FREE memory you have, the more new programs you can open before it starts swapping, and therefore you aim to always have a big chunk of free memory because more free memory means more applications can be open.
Android doesn't work like this!!!
What you are doing is forcing a memory utilization threshold on the thing. This has the same effect as simply reducing the total memory available on the device. That means that important applications are *MORE LIKELY TO GET KILLED OFF*.... which has exactly the OPPOSITE effect from what you seem to be after, which is to ensure that these important applications are NOT killed off.
I could be wrong, but I believe the intent of this is to allow the Android internal memory manager to be tweaked so that certain applications/processes have a higher priority and remain in memory and those that you deem as "less important" are removed first.
Here is a thread on the Hero forum about it:
http://forum.xda-developers.com/showthread.php?t=622666
Also, here is another App that does the same thing... only it will allow the settings to persist through a reboot...
http://www.androlib.com/android.application.com-rs-autokiller-wEwp.aspx
With this App, I do not notice an increase in free (meaning useless) memory... I do notice that key processes that I deem important are still running on CM 4.2.14.1... Even after running many of the ~160 apps I have, including games...
Individual results may vary... Nobody runs the same exact configuration and apps on their G1...
L8r
@Ibcoder
That means that important applications are *MORE LIKELY TO GET KILLED OFF*.... which has exactly the OPPOSITE effect from what you seem to be after, which is to ensure that these important applications are NOT killed off.
Click to expand...
Click to collapse
But it doesn't do that, the threshold simply states a measurable amount of reserve...but not a limitation. Theres a difference. Limits and thresholds are not the same, So what you are saying is not how the app works. All apps open in memory remain in memory, of course you still have to use kill switches and task managers to control unwanted memory hogs, but the app basically controls the memory in use, thats all Im saying, so if that memory is being divided properly, responsive times will increase, I know android had its own setting of doing this, hence the word *DEFAULT*...that is what the app is for, if you don't want to let Android control your memory usage, the app gives you the option to customize it
Also, here is another App that does the same thing... only it will allow the settings to persist through a reboot...
http://www.androlib.com/android.application.com-rs-autokiller-wEwp.aspx
Click to expand...
Click to collapse
Cool app! Thanks for the link, never seen this one.
But wouldn't auto kill be the same as all the other task managers and explorer apps? Its made to kill off unwanted apps, processes, and background services to free memory right? Well, I have plenty of those, and they all work quite fine.
The app I am discussing above is not a killer, its only a manager, it just gives the proper amount of memory to the category you specify to be more important memory users, thus for saving wasted memory. It doesn't specifically kill off or make memory, just manages it.
thanx though, I will try that out.
I recently saw this new app in the Market, but was unsure what advantage it will have on performance, if any. I'll pay attention to this thread to see where the discussion leads on it's usefulness (or potential lack thereof).
TeeJay3800 said:
I recently saw this new app in the Market, but was unsure what advantage it will have on performance, if any. I'll pay attention to this thread to see where the discussion leads on it's usefulness (or potential lack thereof).
Click to expand...
Click to collapse
Ok, and I don't blame ya, that's how I test everything on xda, roms,apps, hacks, you name it....but only after I review enough good responses (preferably 3)
But on the contrary, there have been times that something was reviewed poorly, but after my own experience turned out to be great! You'll see that a lot in the android market as well, great apps with two star/3 star ratings all because some asshole didn't know how to use it, LoL
Try it dude, you got nothing to lose...won't break ya phone, but if ya want to play safe nandroid your current stuff first.
Klyentel said:
Cool app! Thanks for the link, never seen this one.
But wouldn't auto kill be the same as all the other task managers and explorer apps? Its made to kill off unwanted apps, processes, and background services to free memory right? Well, I have plenty of those, and they all work quite fine.
The app I am discussing above is not a killer, its only a manager, it just gives the proper amount of memory to the category you specify to be more important memory users, thus for saving wasted memory. It doesn't specifically kill off or make memory, just manages it.
thanx though, I will try that out.
Click to expand...
Click to collapse
As far as I know, they are pretty much the same... The XDA thread I mentioned above has both the Dev of the App you posted and the Dev of the App I posted... They both created one at around the same time... One with sliders and one with fields... The only difference I think is that AutoKiller uses a service to write the settings on a reboot...
Still playing with this to see if it makes any real difference... I know if I set the values too aggressive, then the browser reloads every time I come back to it...
I know if I set the values too aggressive, then the browser reloads every time I come back to it
Click to expand...
Click to collapse
yeah that has happened to me too.
The linux kernel keeps a buffer cache of recently used files in RAM. So whenever an application wants to access something on the flash, instead of going to the flash file system, it can just get it from the file buffer cache in RAM, a significant speed increase.
If the RAM is currently being taken up by unused android apps, then that leaves less room for the buffer cache, so in theory, by killing off unused android apps more quickly, that will allow the linux kernel to allocate more space for the buffer cache and thus speeding up the system.
Am I way off here?
Dave
lbcoder said:
Don't take offence to this, but any "speedup" you think you are getting from it is entirely a function of the placebo effect.
There is no advantage to forcing memory to remain "free", and in fact, doing something like this will actually make the phone SLOWER than it would otherwise be.
Android has a VERY well thought out memory management system. It keeps a record of processes running and their priorities. In the event that more memory is required for a higher priority application, it will automatically select some other application to kill off in order to get that.
What this does is it ensures that you ALWAYS have the memory FULLY utilized, which means optimal performance under every circumstance.
An unfortunate trap that you are falling into is the traditional view of memory -- for example on a DESKTOP system, you don't have anything killing off unused processes, which means that every program you open will use up more memory, so the more FREE memory you have, the more new programs you can open before it starts swapping, and therefore you aim to always have a big chunk of free memory because more free memory means more applications can be open.
Android doesn't work like this!!!
What you are doing is forcing a memory utilization threshold on the thing. This has the same effect as simply reducing the total memory available on the device. That means that important applications are *MORE LIKELY TO GET KILLED OFF*.... which has exactly the OPPOSITE effect from what you seem to be after, which is to ensure that these important applications are NOT killed off.
Click to expand...
Click to collapse
@dwang-agreed, as I stated @lbcoder, what he is saying is that the app holds everything in memory which slows down system, but it does not do that, and he implied that I stated it limited use of apps, which is incorrect, it does not operate as a limiter, or a kill switch, only a manager. Sort of like, organizing processes by priority based upon setting of threshold tolerance. Of course killing off unwanted apps and processes have to be done manually, via kill widgets or file explorers, When I first posted about this app I assumed that concept to be in mind of the reader....sadly I was wrong. I guess everything around here has to be put in perspective as if the reader knows nothing...sort of like an "101 handbook for Dummies" type thing.
What you are suggesting is incorrect, contrary to the product description, and quite frankly, impossible.
And you can't read.
There is no "I" in lbcoder.
Klyentel said:
@Ibcoder
But it doesn't do that, the threshold simply states a measurable amount of reserve...but not a limitation. Theres a difference. Limits and thresholds are not the same, So what you are saying is not how the app works. All apps open in memory remain in memory, of course you still have to use kill switches and task managers to control unwanted memory hogs, but the app basically controls the memory in use, thats all Im saying, so if that memory is being divided properly, responsive times will increase, I know android had its own setting of doing this, hence the word *DEFAULT*...that is what the app is for, if you don't want to let Android control your memory usage, the app gives you the option to customize it
Click to expand...
Click to collapse
lbcoder said:
What you are suggesting is incorrect, contrary to the product description, and quite frankly, impossible.
And you can't read.
There is no "I" in lbcoder.
Click to expand...
Click to collapse
First and foremost buddy, I quite frankly don't give a dam how you spell your name with an "I" or an "L"
Secondly, what I am stating is not incorrect, and is possible, because I have the app, use it everyday, and does exactly what I said it does via OP. Thank you very much. If you disagree, then don't download the app. Simple as that.
or heres a better idea create one of your own. I will be more than happy to try it if you feel you can do better, but don't downsize the quality of this one, straying other users away from trying it, as it may be as useful to them as it is me. Got it?
Now get ya DREAM on...(with android that is )
and leave me alone.
I've downloaded to my LG Optimus Black 30 apps til' now, I'm on Zeus V2.1
When I had the stock rom I had 100 apps!!
Does installing many apps necessarily slow down the phone? or It doesn't have to affect on the phone memory and speed?
On the one hand, I know that the phone is a lot faster when It has only few apps, and on the other hand, I have an Android Phone, Why not to have funny apps like lighter and games. What's your opinion?
Short answer: Mostly less is more...
Means: A lot of apps stay in memory and slow down ur phone, as u alread answered to urself, some even keep running in background and can keep the cpu from going to deep sleep mode, if they are not programmed well.
So yes, many apps slow down ur phone
Well, to describe it correctly, i would like you to explain that it's not the "numbers" of applications that matters.... I mean, we have a whole one GB of internal space, so we can easily afford 100+ applications.
So, it's actually the "type" of applications that give you a considerable effect on your device's performance.
# Example : i have installed TorrentFreak reader application. When i open it to read TF articles, it opens... when i exit it, it exits... shuts down completely. Now, i have installed UNO game from glu, which even if i don't open, it brings me advertisement notification.
So, the moral of story is, if i have installed hundreds of applications like TFreader, they won't cost me any RAM or any battery usage if i don't use it. But if i install just 10-15 apps like UNOgame of glu, they will use my data connection, RAM etc. in background even if i hardly use them.
So, always choose the application wisely, that's the point. Check their permissions, see if they add any "services" that may keep consuming your cpu cycles..... and you are good to go.
Am running PA 3.60 which is great. I've now run some additional script that culls out and slims down the ROM and gapps. Again, everything runs great. I probably have a lot more memory free now than before. But I'm not sure what good that is.
Traditionally, we want to free up memory so we can install more apps - a2d and other methods help to keep things clear.
I don't want to do that - I want to be able to run more than one or two apps at the same time. But I don't know which memory types to clear up to do that.
The ROM is in, well, ROM, so making it smaller may not help free up memory if there's fixed 512MB used for it.
I know Android is actually running a lot of processes at once. What I mean is that if I load an app, say Candy Crush, then run another app, say Grindr, I can switch back and forth pretty much ok and each app resumes where it left off without any noticable reloading/refreshing. But if I then run another app, say Scruff, then as soon as I try to switch back to one of the others, it has to reload/refresh/restart. So clearly, there wasn't enough memory available to keep all 3 resident and it swapped some out or simply released it.
Logically, if I have more of a certain type of memory free, this will not happen as often. I know it depends on how much memory and other resources an app requires, but I don't need to get into that level of analysis yet. First and foremost, what sort of memory should I try to make as much of as possible to let me swtich between apps without so much reloading?
douginoz said:
Am running PA 3.60 which is great. I've now run some additional script that culls out and slims down the ROM and gapps. Again, everything runs great. I probably have a lot more memory free now than before. But I'm not sure what good that is.
Traditionally, we want to free up memory so we can install more apps - a2d and other methods help to keep things clear.
I don't want to do that - I want to be able to run more than one or two apps at the same time. But I don't know which memory types to clear up to do that.
The ROM is in, well, ROM, so making it smaller may not help free up memory if there's fixed 512MB used for it.
I know Android is actually running a lot of processes at once. What I mean is that if I load an app, say Candy Crush, then run another app, say Grindr, I can switch back and forth pretty much ok and each app resumes where it left off without any noticable reloading/refreshing. But if I then run another app, say Scruff, then as soon as I try to switch back to one of the others, it has to reload/refresh/restart. So clearly, there wasn't enough memory available to keep all 3 resident and it swapped some out or simply released it.
Logically, if I have more of a certain type of memory free, this will not happen as often. I know it depends on how much memory and other resources an app requires, but I don't need to get into that level of analysis yet. First and foremost, what sort of memory should I try to make as much of as possible to let me swtich between apps without so much reloading?
Click to expand...
Click to collapse
Try enabling zram, I haven't tried it personally but its supposed to allow for more multitasking.
Sent from my Nexus One using xda app-developers app
Moved To Q&A
You may of considered it dev based, but its a question so belongs in the Q&A section.
I've tried ZRAM now for a couple of days but makes no difference. I also have the problem on another Android device. I'm convinced its some sort of design limitation of the opsys or something. When I start up Grindr, it takes a long time to load all the images, make connections, etc. Then I start of Gruff, and it does the same. As long as I don't try to go to another app, I can flip between the two of them without them restarting/reloading/reinitialising themselves. That is clearly because their pages didn't get swapped out of memory or flagged for deletion and deleted.
But if I do something else, or even try to use additional functions within either app, its too much and the next time I try to flip to the other app, it has to reload and reestablish connections etc.
Its not just those apps either. The same with a game like Candy Crush. Or many many apps.
So either my devices don't have enough memory of some form to allow many concurrent apps to run without being swapped out, or Android can't handle it and unnecessarily swaps out or deletes a process's memory pages to make room for the next process, >>> even if the device has plenty of memory<<<.
I don't know which type of memory the opsys needs if this is the case. I'd like to know so that i can make sure there's ample available so that this constant restarting doesn't keep happening. It seems stupid to me that Android does this if the device has got "heaps" of available memory (no pun intended). Newer devices will continually have more and more built in memory, so if Android is doing this arbitrarily and not because of space issues then its, well, stupid.
I have to assume its my devices that are the problem. They're both old (Nook Color, Nexus One). But with the NC, I'd assume we can partition some of that 5GB for use as main memory to run lots of processes concurrently, without this annoying swapping/page deletion/forcing re-inits all the time.
I'm also having problems figuring out where in XDA to post this question - its not NC specific, or dev specific, but I need answers from people that know the Android architecture so I can work out if its possible to stop this from happening.
Hi, i'm thinking of buying an HTC one and i can't wait for it and i wonder how much of a difference does closing apps make in terms of battery life because it is obvious that having apps running in the background makes the OS feel a lot faster and if it's a minor downside than i'd rather have the upside of having those running in the background.
Hahaahahahahahahahahaahaha. Closing them neither increases battery nor makes the system feel faster... Have you come from an iPhone? (It doesn't make a difference on iPhones either)
nope im coning from glaxy nexus and it does make a difference in it though
According to what I've read, the newer android systems freeze the apps while in the background. I don't know what apps you'd keep open in the background, though. The only one I have keep running is my browser.
Im asking that if im surfing on net and then have to go somewhere, do i have to close apps and then put the phone in my pocket or is just locking your phone and putting it in your pocket is fine.
battle1 said:
Im asking that if im surfing on net and then have to go somewhere, do i have to close apps and then put the phone in my pocket or is just locking your phone and putting it in your pocket is fine.
Click to expand...
Click to collapse
I just lock the phone and put it in my pocket. Does fine for me. I get awesome battery life. Usually your screen is what eats up your battery anyways, again I say usually ;p (always an exception somewhere). Out of all the android phones I've had, this one has the best battery life. Not saying there aren't better, but I can go a whole day with moderate use and still have a little juice at the end of the day. Now granted, if you were playing music, you may want to stop that first, but I figured that was common sense...
battle1 said:
Im asking that if im surfing on net and then have to go somewhere, do i have to close apps and then put the phone in my pocket or is just locking your phone and putting it in your pocket is fine.
Click to expand...
Click to collapse
Just minimize it to the recent apps tray, you can just restore the app where you left off ... Android manages apps extremely efficiently so you don't need to close them, force stop them in settings, use a task manager or any of the above. It actually drains your battery more to kill apps and have them start again, especially system apps that constantly run, than it does to just leave them running.
when you pause an activity (hit the home button, rather than the back button - or venture off to a different activity)
The app does not continue running, however it does preserve the application state (as long as dalvik doesn't kill it, due to higher priority memory allocation requests)
Apps can launch background services, which are NOT paused in the same way (depending on how they are created, of course). In order to force kill all services associated with an app, you'll have to use the app manager.
---
As far as performance/battery impact:
- You'd think "Oh, if i pause 50 apps then i'm going to run out of memory?" NO - the dalvik will kill them in the order it deems necessary to ensure a certain amount of memory is always free.
- This also means you cannot count on a paused app ALWAYS being where you left it off. In the middle of writing an important email? pause the app, go look something up in chrome, and come back to the email it MAY or MAY NOT BE where you left it off. (The dalvik could have killed it)
- Paused apps do not account for any CPU time, therefore there is no battery impact.
Services MAY account for cpu time depending on what they're doing - and they will run even when the app is killed depending on how they were registered.
So even in my Galaxy Nexus it's actually better if i don't swipe all the recent apps?
Hello everyone.
Even after hibernating all the apps, still 2GB of my ram is used. I want to look at all the processes that are using the ram. How can I do that?
Cheers!
Until someone comes up with a better answer...
Settings/Apps. Under each app there are stats for used storage and memory used in the past few hours. Might give you a clue.
xhamadeex said:
Hello everyone.
Even after hibernating all the apps, still 2GB of my ram is used. I want to look at all the processes that are using the ram. How can I do that?
Cheers!
Click to expand...
Click to collapse
Because ANDROID KNOWS that UNUSED RAM is WASTED RAM.
It ***preloads*** all of the things, in order of what it believes is the likelihood of you using those particular things.
This way when you actually DO use one of those things, it is ***already loaded*** (and starts fast).
Stop "hibernating" things. You are breaking Android.
doitright said:
Because ANDROID KNOWS that UNUSED RAM is WASTED RAM.
It ***preloads*** all of the things, in order of what it believes is the likelihood of you using those particular things.
This way when you actually DO use one of those things, it is ***already loaded*** (and starts fast).
Stop "hibernating" things. You are breaking Android.
Click to expand...
Click to collapse
Hmm.. You have a point..
So, is using Greenify a bad Idea?
xhamadeex said:
Hmm.. You have a point..
So, is using Greenify a bad Idea?
Click to expand...
Click to collapse
Bad idea.
yea there's two built-in ways to view running processes. One is directly Settings. Scroll down to where it says Memory. Open and check it out. I know. Google might as well not even wasted their time making that activity since it's next to useless. The other one is located in Developer Options. It's labeled "Running Services" and gives you stats on what apps are running, how long, etc. Yea, not very helpful either since there isn't much you can do besides uninstall some things or do the root and ransack thing. It's intentionally made like that, just like the way android battery stats are completely useless for nailing down offensive background services. Google likes it that way. They make money by tracking your location and serving you up with as many ads as possible. While it's true what dude said about the way Android preloads and makes a lot of stuff ready in RAM, hibernating, and using task killers is basically like working against your system resources, don't listen to people who yell things at you because they've been brainwashed by companies and developers who want their services installed, front-and-center, autostarting, and running 24/7 in your device's memory. Why else you think every website has a banner talkin' bout "oooh ooh install our app" and grant as many permissions as possible while some even go as far as sabotaging their own services via their website so users feel forced to install the app. They don't care about you, your cpu, or your experience as long as it's filled with ads and periodically uploading analytics and usage stats and the best way to do that is to have background and persistent services to silently restart their location polling or pointless notification systems designed solely around getting you to interact with the app. I'm not talking about things like email, messaging, or whatever other app you depend on or feel is important enough to keep close at a tap of finger. My suggestion is to analyze those settings activities I named earlier or a 3rd party one like BBS and make some decisions about what you are willing to delete. Compromises can be made depending on what's important to you and also with root. Half (or more) of the apps in your phone that have boot receivers and other various event listeners up the wazoo have no business knowing your phone is even on until you tap it's little icon. This is opinion of course because others will tell you you're breaking android and a bunch of other nonsense they've been fed by google to address the people, like me, who are tired of seeing google and other apps (usually ones my by behemoth corporations) that run constantly in the background even though I open up and use whatever particular app maybe once a week. If you're rooted, there is a lot you can do to take control of apps that like to stay nudged up as close as possible in the queue and keep open connections. It all depends on you and how you use your device. Don't listen to know-it-alls who yell at you IN ALL CAPS. Either accept the fact that google, facebook, admob (and whoever else app you have that thinks it's the most important) own your phone, or do a little research for yourself because regardless of what homeboy said, it's easy to see that available RAM feels way smoother than ram that has to wait for android to move pokey balls out of the way...just sayin
ElwOOd_CbGp said:
yea there's two built-in ways to view running processes. One is directly Settings. Scroll down to where it says Memory. Open and check it out. I know. Google might as well not even wasted their time making that activity since it's next to useless. The other one is located in Developer Options. It's labeled "Running Services" and gives you stats on what apps are running, how long, etc. Yea, not very helpful either since there isn't much you can do besides uninstall some things or do the root and ransack thing. It's intentionally made like that, just like the way android battery stats are completely useless for nailing down offensive background services. Google likes it that way. They make money by tracking your location and serving you up with as many ads as possible. While it's true what dude said about the way Android preloads and makes a lot of stuff ready in RAM, hibernating, and using task killers is basically like working against your system resources, don't listen to people who yell things at you because they've been brainwashed by companies and developers who want their services installed, autostarting, and running 24/7 in your device. Why else you think every website has a banner talkin' bout "oooh ooh install our app" and grant as many permissions as possible while some even go as far as sabotaging their own services via their website so users feel forced to install the app. They don't care about you, your cpu, or your experience as long as it's filled with ads and periodically uploading analytics and usage stats and the best way to do that is to have background and persistent services to silently restart their location polling or pointless notification systems designed solely around getting you to interact with the app. I'm not talking about things like email, messaging, or whatever other app you depend on or feel is important enough to keep close at a tap of finger. My suggestion is to analyze those settings activities I named earlier or a 3rd party one like BBS and make some decisions about what you are willing to delete. Compromises can be made depending on what's important to you and also with root. Half (or more) of the apps in your phone that have boot receivers and other various event listeners up the wazoo have no business knowing your phone is even on until you tap it's little icon. This is opinion of course because others will tell you you're breaking android and a bunch of other nonsense they've been fed by google to address the people, like me, who are tired of seeing google and other apps (usually ones my by behemoth corporations) that run constantly in the background even though I open up and use whatever particular app maybe once a week. If you're rooted, there is a lot you can do to take control of apps that like to stay nudged up as close as possible in the queue and keep open connections. It all depends on you and how you use your device. Don't listen to know-it-alls who yell at you IN ALL CAPS. Either accept the fact that google, facebook, admob (and whoever else app you have that thinks it's the most important) own your phone, or do a little research for yourself because regardless of what homeboy said, it's easy to see that available RAM feels way smoother than ram that has to wait for android to move pokey balls out of the way...just sayin
Click to expand...
Click to collapse
Holy wall of text Batman!
You've got a couple of points hidden inside that rambling, but dude... If you want anyone to read that, try that little thing called paragraphs.
Didgeridoohan said:
Holy wall of text Batman!
You've got a couple of points hidden inside that rambling, but dude... If you want anyone to read that, try that little thing called paragraphs.
Click to expand...
Click to collapse
Ah...apologies. I may have been a little bit hopped up last night on the leftover holiday spirits but how else to explain what I see as google's all-over-the-place ridiculous approach at making it as god awful experience as possible for people interested in granular control over their devices' /system. I just got done flashing, setting up, and going thru the motions on a new phone so I may have been a little annoyed as well. lolz hope it helps someone.