Database Develop

Auto Memory Mangager

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.

[Q] Final word on task killers?

So I have heard that using a task killer app could do more harm then good. Is this true? If not, whats a highly recommend task killer app?

Why you shouldn't use them.

a.n said:
Why you shouldn't use them.
Click to expand...
Click to collapse
I read this article via a link from gizmodo and it was very informative. I was using ATK for some time and thought it was doing well. I had no idea that many of the issues I was running into were actually coming from the task killer nixing items I needed running. I realized this after I removed the task killer and installed watchdog.
I am not going to say watchdog was streamlining power house for my phone but, it did allow me to see what was really going on in a much more efficient manner. The information it provides is useful and gives a much better idea of what is consuming all those battery eating clock cycles. I feel more comfortable now knowing what is actually active and whether I need it to be.
Since the change over I have been consuming more battery power but I just changed to Cognition and I have significantly less FCs. This is on top of my recent full time GPS usage and frequent music streaming.

[Q] Disable auto-closing apps

Well i searched around XDA a bit and found many threads related to this bt all for WM and not android.
Multi-tasking is getting a bit tough. Apps get auto-closed after sometime.
Samsung Galaxy SL i9003
Stock firmware and everything stock, nothing chngd much. Only apps installed from the Market.
Say m surfing the opera, and even if a small app like messaging is open and aftr some roaming around when i return of opera, it has closed.
PS - Above is jus an example so dnt claim Opera is a power-hogger so it wil b to open up ram for other apps and all......
So any way of disabling the auto-closure of apps?
Love XDA

@ mod who moved it...
Its related to i9003 nt i9000.
Anyways tnx for moving. Wil get more views here....

Any dev der? Help!
Sent from my GT-I9003 using XDA App

Personally, I cannot believe that this doesn't get complained about a lot more vocally and a lot more often, especially as it is common across ALL Android devices running 2.2 or beyond, not just the Galaxy S. It is a MAJOR usability issue in the operating system and one that is a complete dealbreaker for me.
Since 2.2 any application left running in the background is automatically closed by the system after a few minutes of inactivity, regardless of memory availability/needs or power consumption. This approach is far from acceptable for things such as EBuddy or any other msn-style instant messaging client which the user may want to leave open in order to stay logged in, so as to remain constantly available and reachable by other parties using the same service. This is just one example of a type of application I might want to leabe open and running in the background, but there are plenty of others.
The fact that the entire Android platform has essentially removed multi-tasking as a feature of the OS as of version 2.2 is astounding and appalling to me, and it's very surprising not to find more people just as offended by this on a more regular basis. What's worse, no matter how rooted or custom-ROM'd your device might be, there seems to be absolutely no way to override or disable this behavior as it is hard-coded into the OS kernel at a fundamental level. We basically have a first generation iPhone on our hands now, thanks to this latest innovation.
Closing apps when memory and system resources are low is one thing, but closing them just because the user hasn't attended to them in the last five minutes or so? Ridicullous. If you wouldn't want your desktop computer shutting down all your open/background applications every time you go for a coffee break or take a 10-minute phone call, what makes the Android developers think users want this done on their smartphones???

Exactly.
There's an app on the market, Spare Parts, in it ders a option on hw android handles suc apps.
There r two options. Normal and aggressive. Keep it normal and try and c if it helps.
paleozord said:
Personally, I cannot believe that this doesn't get complained about a lot more vocally and a lot more often, especially as it is common across ALL Android devices running 2.2 or beyond, not just the Galaxy S. It is a MAJOR usability issue in the operating system and one that is a complete dealbreaker for me.
Since 2.2 any application left running in the background is automatically closed by the system after a few minutes of inactivity, regardless of memory availability/needs or power consumption. This approach is far from acceptable for things such as EBuddy or any other msn-style instant messaging client which the user may want to leave open in order to stay logged in, so as to remain constantly available and reachable by other parties using the same service. This is just one example of a type of application I might want to leabe open and running in the background, but there are plenty of others.
The fact that the entire Android platform has essentially removed multi-tasking as a feature of the OS as of version 2.2 is astounding and appalling to me, and it's very surprising not to find more people just as offended by this on a more regular basis. What's worse, no matter how rooted or custom-ROM'd your device might be, there seems to be absolutely no way to override or disable this behavior as it is hard-coded into the OS kernel at a fundamental level. We basically have a first generation iPhone on our hands now, thanks to this latest innovation.
Closing apps when memory and system resources are low is one thing, but closing them just because the user hasn't attended to them in the last five minutes or so? Ridicullous. If you wouldn't want your desktop computer shutting down all your open/background applications every time you go for a coffee break or take a 10-minute phone call, what makes the Android developers think users want this done on their smartphones???
Click to expand...
Click to collapse
Sent from my GT-I9003 using XDA App

Exactly.
I hv migrated frm Symbian, and m a hard multi-tasker, and disappointd with Android jus cos of tis...
paleozord said:
Personally, I cannot believe that this doesn't get complained about a lot more vocally and a lot more often, especially as it is common across ALL Android devices running 2.2 or beyond, not just the Galaxy S. It is a MAJOR usability issue in the operating system and one that is a complete dealbreaker for me.
Since 2.2 any application left running in the background is automatically closed by the system after a few minutes of inactivity, regardless of memory availability/needs or power consumption. This approach is far from acceptable for things such as EBuddy or any other msn-style instant messaging client which the user may want to leave open in order to stay logged in, so as to remain constantly available and reachable by other parties using the same service. This is just one example of a type of application I might want to leabe open and running in the background, but there are plenty of others.
The fact that the entire Android platform has essentially removed multi-tasking as a feature of the OS as of version 2.2 is astounding and appalling to me, and it's very surprising not to find more people just as offended by this on a more regular basis. What's worse, no matter how rooted or custom-ROM'd your device might be, there seems to be absolutely no way to override or disable this behavior as it is hard-coded into the OS kernel at a fundamental level. We basically have a first generation iPhone on our hands now, thanks to this latest innovation.
Closing apps when memory and system resources are low is one thing, but closing them just because the user hasn't attended to them in the last five minutes or so? Ridicullous. If you wouldn't want your desktop computer shutting down all your open/background applications every time you go for a coffee break or take a 10-minute phone call, what makes the Android developers think users want this done on their smartphones???
Click to expand...
Click to collapse
Sent from my GT-I9003 using XDA App

Is this the reason why I have to constantly log back into Evernote, and Tweetdeck every time i wanna have a look at them?
The whole concept of syncing periodically doesn't work anymore because they are constantly logging out on me.

Unfortunately neither Spare Parts nor any such custom tweaking app seems have any effect on this berhaviour under Froyo or Gingerbread. And yes, the system auto-close is the reason that re-logging into connectivity apps every time you open them is necessary. Since they have been shut down and are no longer running, you are essentially re-launcing them anew each and every time. Hardly ideal.
Previous "old school" smartphone platforms like Symbian and Windows Mobile 5/6 had multi-tasking incorporated into their basic functionality. It's really a shame that shiny new operating systems like Android/iPhone make it such a struggle. Up until and including Eclair (2.1) leaving apps open in the background was completely possible, but as of the present moment WebOS is the only "new age" smartphone OS that still allows it, and unfortunately it hasn't moved along in other development areas very quickly at all.

I wonder y others @xda & @google dnt feel tis....
paleozord said:
Unfortunately neither Spare Parts nor any such custom tweaking app seems have any effect on this berhaviour under Froyo or Gingerbread. And yes, the system auto-close is the reason that re-logging into connectivity apps every time you open them is necessary. Since they have been shut down and are no longer running, you are essentially re-launcing them anew each and every time. Hardly ideal.
Previous "old school" smartphone platforms like Symbian and Windows Mobile 5/6 had multi-tasking incorporated into their basic functionality. It's really a shame that shiny new operating systems like Android/iPhone make it such a struggle. Up until and including Eclair (2.1) leaving apps open in the background was completely possible, but as of the present moment WebOS is the only "new age" smartphone OS that still allows it, and unfortunately it hasn't moved along in other development areas very quickly at all.
Click to expand...
Click to collapse
Sent from my GT-I9003 using XDA App

Erm....why do you think people flash custom roms?!
GTi9000 insanitycm010/insaneglitch

slaphead20 said:
Erm....why do you think people flash custom roms?!GTi9000 insanitycm010/insaneglitch
Click to expand...
Click to collapse
Custom ROMs do not change or affect this system auto-close functionality in any way. At least I've never seen any that did so successfully. It seems to be coded too deeply into the OS to be changed, from what I can tell. That is, I'm sure theoretically it *could* be changed, but most custom roms I've seen tackle far more surface-level interface issues and not the way the kernel manages processes in the background.

I didn't realise this happened after 2.1... I already was thinking why all apps were getting closed so fast after I updated my i9000 to froyo and then to 2.3. I just bought i9100 mainly because of the 1gb ram and still, with 400mb free ram, apps getting closed after couple of hours. (Not minutes, or even seconds like i9000, thankgod).
Autokiller lets you manually change some value of a running app, so it won't get killed... unfortunately this isn't automated so it's no use.

The time before auto-closure can sometimes vary from device to device.. I've tested on two Froyo devices other than the Galaxy S, each from different manufacturers as well, and apps rarely make it past ten minutes before being shut down on any of them. I've never seen anything make it a couple of hours so that's a new one.
I've actually gone back to my Motorola Defy running 2.1 for now, specifically to be able to multi-task again. Sadly there is a 2.2 update available over-the-air for it, but I keep declining because I just don't want to lose the ability to multi-task. Unless some future version like Ice Cream Sandwich restores control to the user, Eclair may very well be the last edition of Android I ever use.
Or should I say AndroIPhone, since that is what it has become.

Eclair actually allows u to multi-task normally?
No issues lik froyo?
Working lik "old-school" OSes's multi tasking?
paleozord said:
The time before auto-closure can sometimes vary from device to device.. I've tested on two Froyo devices other than the Galaxy S, each from different manufacturers as well, and apps rarely make it past ten minutes before being shut down on any of them. I've never seen anything make it a couple of hours so that's a new one.
I've actually gone back to my Motorola Defy running 2.1 for now, specifically to be able to multi-task again. Sadly there is a 2.2 update available over-the-air for it, but I keep declining because I just don't want to lose the ability to multi-task. Unless some future version like Ice Cream Sandwich restores control to the user, Eclair may very well be the last edition of Android I ever use.
Or should I say AndroIPhone, since that is what it has become.
Click to expand...
Click to collapse
Sent from my GT-I9003 using XDA App

ggclanlord said:
Eclair actually allows u to multi-task normally?
No issues lik froyo?
Working lik "old-school" OSes's multi tasking?
Click to expand...
Click to collapse
Correct, applications are left open and running in the background indefinitely until the user chooses to close them. Using a good multitasking app like TaskSwitcher or Smart Taskbar you can switch back and forth between open apps as much and as often as you like, or go away for hours without anything ever closing on you. I'm doing it presently on my Defy with no issues at all, just like older operating systems allow(ed).

Tats really Awesome!
paleozord said:
Correct, applications are left open and running in the background indefinitely until the user chooses to close them. Using a good multitasking app like TaskSwitcher or Smart Taskbar you can switch back and forth between open apps as much and as often as you like, or go away for hours without anything ever closing on you. I'm doing it presently on my Defy with no issues at all, just like older operating systems allow(ed).
Click to expand...
Click to collapse
Sent from my GT-I9003 using XDA App

ggclanlord said:
Tats really Awesome!
Click to expand...
Click to collapse
It's certainly a saving grace for Android that Eclair devices still provide multi-tasking functionality for those who insist upon it, though at the same time it sucks to see all these super powerful, souped up Froyo and Gingerbread devices being released monthly and having to snub them because of the deficiency in the newer OS.
Please, please fix this in Ice Cream Sandwich or Chocolate Souffle or Lemon Tart or whatever desserty moniker the 2.4 flavour of Android takes on. Or at the very least give the user the option to select an operational mode (auto-close or manual manage) just like many devices offer for battery management, with performance mode versus smart-saver mode etc..
It's hardly a smart phone without multi-tasking!!

I guess so it'd b more effective if tis is wrttn to Google...
paleozord said:
It's certainly a saving grace for Android that Eclair devices still provide multi-tasking functionality for those who insist upon it, though at the same time it sucks to see all these super powerful, souped up Froyo and Gingerbread devices being released monthly and having to snub them because of the deficiency in the newer OS.
Please, please fix this in Ice Cream Sandwich or Chocolate Souffle or Lemon Tart or whatever desserty moniker the 2.4 flavour of Android takes on. Or at the very least give the user the option to select an operational mode (auto-close or manual manage) just like many devices offer for battery management, with performance mode versus smart-saver mode etc..
It's hardly a smart phone without multi-tasking!!
Click to expand...
Click to collapse
Sent from my GT-I9003 using XDA App

Cn any1 tel me whthr tis issue is der @GB o nt?
M on Froyo cos GB nt yet released for my device (only a Dev update yet)

I can't say with 100% certainty but I'm reasonably confident it's the same under Gingerbread (2.3). Google considers this "feature" of the Android operating system to be a significant improvement and benefit, so they're not likely to remove it on their own anytime soon unless they get a massive influx of complaints about it.
The best we can hope for is probably a user-controllable setting of some sort that determines the degree of system aggressiveness in auto-closing background applications. There are already plenty of third party root-based utilities available in the market with similar settings, but they only affect their OWN auto-closing tendencies and do not override the system itself's default auto-close behaviour. I know this because I have tried them all at the lowest possible setting levels, and everything still gets closed in the background just the same.

Battery Monitor App, is it possible on this OS?

I had Android for a while, and I remember there was an App that broke down Battery/Cpu usage. It would even keep track of how long the screen was on, what was being used most that could potentially be using the battery more.
Ive yet to see an App like this for WP7, let alone 8. Is it even possible? Or is it just yet another thing impossible due to MS lock down on some aspects of the phone OS?
I really do like this OS, but it seems more and more, MS's lock down really hurts development, preventing Devs from really bringing out the most of the OS and prevents functions and abilities youd normally think would exist.

I can understand the want for an app like this (I had it on android myself), but since switching over to WP8 I don't see the need.
All the apps on here run very well and nothing is going crazy like it does with android. Locking down the OS is a good thing sometimes, devs have a much harder tune creating system level apps that run way out of control or have memory leaks that cause battery to run dry in an hour. The only thing I have done is gone to the background apps in settings and stopped what I didn't want running in there.
Sent from my RM-820_nam_att_100 using Board Express

LudoGris said:
I can understand the want for an app like this (I had it on android myself), but since switching over to WP8 I don't see the need.
All the apps on here run very well and nothing is going crazy like it does with android. Locking down the OS is a good thing sometimes, devs have a much harder tune creating system level apps that run way out of control or have memory leaks that cause battery to run dry in an hour. The only thing I have done is gone to the background apps in settings and stopped what I didn't want running in there.
Sent from my RM-820_nam_att_100 using Board Express
Click to expand...
Click to collapse
I initially thought this when I had WP7 and a Trophy. Now that I have the 920, I would love to have this. Partially just to prove out that using my phone (screen on) and games and other things just eats up the battery like crazy. Others over at WPCentral have also posted issues with the battery. Many people have in fact. It would be very useful to some of us who are experiencing issues.
I know some claim to get over a day or more use out of their 920. I, among many others, could only dream of such a thing, or perhaps achieve it if we just didnt do much with our phones.
I disagree on the lock down. While I get your point, having used Android also, I enjoyed many great apps that just wont ever be possible on WP's. No other email clients, no true 3rd party browser not built on IE, no new keyboards to name a few. Some of these apps I had used on Android really were superior to what Ive seen MS do with WP. Which is why I think sometimes 3rd party Devs or home Devs sometimes can just do things better as well as think outside the box and give us real options. You dont get real options for many thing on WP. Everyone is stuck with the same keyboard, browser, mail, messaging client, etc.

True...but remember, there was a time when nothing like that was available for Android either.
Devs have made things more than possible - granted an open system helps - but don't discount what may become available in the future.

Yes there are battery monitor apps for Windows Phone 8. Battery Level for Windows Phone 8 seems to be the most popular. The nice part is that it will autoupdate the live tile with the battery level and you can add it to the lockscreen to show it there as well. It's not quite as in depth as Android with regards to telling you what is pulling the most power but as others have mentioned on WP8 it's a slightly different mechanic than Android as the background processes are a lot more regulated with regards to how they can do that (as are the developers when making their apps). It would be kind of interesting to see something like Android's built-in battery stats but I honestly haven't really haven't had any problems (not that I was really having problems on Android either).

Battery Measure is similar, and has a free version with ads - live tile, graph over time. etc.

and can you tell us where we can get the battery monitor for th WP 8? I want one...

Battery App
inconceivable said:
Yes there are battery monitor apps for Windows Phone 8. Battery Level for Windows Phone 8 seems to be the most popular. The nice part is that it will autoupdate the live tile with the battery level and you can add it to the lockscreen to show it there as well. It's not quite as in depth as Android with regards to telling you what is pulling the most power but as others have mentioned on WP8 it's a slightly different mechanic than Android as the background processes are a lot more regulated with regards to how they can do that (as are the developers when making their apps). It would be kind of interesting to see something like Android's built-in battery stats but I honestly haven't really haven't had any problems (not that I was really having problems on Android either).
Click to expand...
Click to collapse
That sound very good but where can I get the apps Battery Level?

I want to see what's consuming my ram.

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.