Related
This is now android works. The way I see this, this is very much similar to "pre-fetch" concept in windows 7.
I have a 6 GB RAM laptop. Base OS uses less than 1.5 GB of RAM. But like an hour or so when I see my RAM usage, its to the tune of 3-4 GB. What I have noticed is that my most frequently/recently used apps are loaded to RAM and kept there idle. Some amount of RAM is always kept free instead of using up all RAM. This way apps start faster. When I load a different memory heavy program, it pushes the existing one out and loads this.
More or less the same in android too. When u go to any task manager app n see the running apps, u'll notice that many of the apps loaded are the ones u use frequently.
These apps do NOT use any CPU. They are just loaded to memory and kept there for quick access.
When I boot up my phone I have like 190+ MB free RAM. Though left in standy mode, within an hour, I see my free RAM fall to 80-120 MB range. I never saw it go less than 80 MB. And the apps in memory are the ones I used the last time, and the ones I use all the time.
Even if u use a task killer to kill these "inactive" apps at intervals, they would be loaded again sooner or later. That's the principle of android. So by using task killers, though u feel u r freeing up memory, in fact, u r only draining ur battery. What's the use of memory if u r not using it effectively.
Don't worry abt free RAM amount. Let android manage it. Systems are intelligent enough these days.
Hope this helps. Below is more about the same in detail.
Android Memory Management
Android is a Linux based OS with 2.6.x kernel, stripped down to handle most tasks pretty well. It uses native open source C libraries that have powered Linux machines for years. All the basic OS operations like I/O, memory management, and so on, are handled by the native stripped-down Linux kernel.
How to use memory for each application
Android’s process and memory management is a little unusual. Like Java and .NET, Android uses its own run time and virtual machine to manage application memory. Unlike either of these frameworks, the Android run time also manages the process lifetimes. Android ensures application responsiveness by stopping and killing processes as necessary to free resources for higher-priority applications.
Each Android application runs in a separate process within its own Dalvik instance, relinquishing all responsibility for memory and process management to the Android run time, which stops and kills processes as necessary to manage resources.
Dalvik and the Android run time sit on top of a Linux kernel that handles low-level hardware interaction including drivers and memory management, while a set of APIs provides access to all of the under- lying services, features, and hardware.
Dalvik Virtual Machine Dalvik is a register-based virtual machine that’s been optimized to ensure that a device can run multiple instances efficiently. It relies on the Linux kernel for threading and low-level memory management.
The Dalvik Virtual Machine
One of the key elements of Android is the Dalvik virtual machine. Rather than use a traditional Java virtual machine (VM) such as Java ME (Java Mobile Edition), Android uses its own custom VM designed to ensure that multiple instances run efficiently on a single device.
The Dalvik VM uses the device’s underlying Linux kernel to handle low-level functionality including security, threading, and process and memory management.
All Android hardware and system service access is managed using Dalvik as a middle tier. By using a VM to host application execution, developers have an abstraction layer that ensures they never have to worry about a particular hardware implementation.
The Dalvik VM executes Dalvik executable files, a format optimized to ensure minimal memory foot- print. The .dex executables are created by transforming Java language compiled classes using the tools supplied within the SDK.
Understanding Application Priority and Process States
The order in which processes are killed to reclaim resources is determined by the priority of the hosted applications. An application’s priority is equal to its highest-priority component.
Where two applications have the same priority, the process that has been at a lower priority longest will be killed first. Process priority is also affected by interprocess dependencies; if an application has a dependency on a Service or Content Provider supplied by a second application, the secondary application will have at least as high a priority as the application it supports.
All Android applications will remain running and in memory until the system needs its resources for other applications.
It’s important to structure your application correctly to ensure that its priority is appropriate for the work it’s doing. If you don’t, your application could be killed while it’s in the middle of something important.
The following list details each of the application states shown in Figure (see the attached image) explaining how the state is determined by the application components comprising it:
Active Processes Active (foreground) processes are those hosting applications with components currently interacting with the user. These are the processes Android is trying to keep responsive by reclaiming resources. There are generally very few of these processes, and they will be killed only as a last resort.
Active processes include:
* Activities in an “active” state; that is, they are in the foreground and responding to user events. You will explore Activity states in greater detail later in this chapter.
* Activities, Services, or Broadcast Receivers that are currently executing an onReceive event handler.
* Services that are executing an onStart, onCreate, or onDestroy event handler.
Visible Processes Visible, but inactive processes are those hosting “visible” Activities. As the name suggests, visible Activities are visible, but they aren’t in the foreground or responding to user events. This happens when an Activity is only partially obscured (by a non-full-screen or transparent Activity). There are generally very few visible processes, and they’ll only be killed in extreme circumstances to allow active processes to continue.
Started Service Processes Processes hosting Services that have been started. Services support ongoing processing that should continue without a visible interface. Because Services don’t interact directly with the user, they receive a slightly lower priority than visible Activities. They are still considered to be foreground processes and won’t be killed unless resources are needed for active or visible processes.
Background Processes Processes hosting Activities that aren’t visible and that don’t have any Services that have been started are considered background processes. There will generally be a large number of background processes that Android will kill using a last-seen-first-killed pat- tern to obtain resources for foreground processes.
Empty Processes To improve overall system performance, Android often retains applications in memory after they have reached the end of their lifetimes. Android maintains this cache to improve the start-up time of applications when they’re re-launched. These processes are rou- tinely killed as required.
How to use memory efficiently
Android manages opened applications which are running in the background, so officially you shouldn’t care about that. This means that it closes the applications when the system needs more memory. However, most android users are not very satisfied with how it does its things because sometimes it leaves too many processes running which causes sluggishness’ in everyday performance. We can use advanced task killer/task manager and it does its job very well.
Source:
Code:
http://mobworld.wordpress.com/2010/07/05/memory-management-in-android/
NICE!!
diablo009 said:
This is now android works. The way I see this, this is very much similar to "pre-fetch" concept in windows 7.
I have a 6 GB RAM laptop. Base OS uses less than 1.5 GB of RAM. But like an hour or so when I see my RAM usage, its to the tune of 3-4 GB. What I have noticed is that my most frequently/recently used apps are loaded to RAM and kept there idle. Some amount of RAM is always kept free instead of using up all RAM. This way apps start faster. When I load a different memory heavy program, it pushes the existing one out and loads this.
More or less the same in android too. When u go to any task manager app n see the running apps, u'll notice that many of the apps loaded are the ones u use frequently.
These apps do NOT use any CPU. They are just loaded to memory and kept there for quick access.
When I boot up my phone I have like 190+ MB free RAM. Though left in standy mode, within an hour, I see my free RAM fall to 80-120 MB range. I never saw it go less than 80 MB. And the apps in memory are the ones I used the last time, and the ones I use all the time.
Even if u use a task killer to kill these "inactive" apps at intervals, they would be loaded again sooner or later. That's the principle of android. So by using task killers, though u feel u r freeing up memory, in fact, u r only draining ur battery. What's the use of memory if u r not using it effectively.
Don't worry abt free RAM amount. Let android manage it. Systems are intelligent enough these days.
Hope this helps. Below is more about the same in detail.
Android Memory Management
Android is a Linux based OS with 2.6.x kernel, stripped down to handle most tasks pretty well. It uses native open source C libraries that have powered Linux machines for years. All the basic OS operations like I/O, memory management, and so on, are handled by the native stripped-down Linux kernel.
How to use memory for each application
Android’s process and memory management is a little unusual. Like Java and .NET, Android uses its own run time and virtual machine to manage application memory. Unlike either of these frameworks, the Android run time also manages the process lifetimes. Android ensures application responsiveness by stopping and killing processes as necessary to free resources for higher-priority applications.
Each Android application runs in a separate process within its own Dalvik instance, relinquishing all responsibility for memory and process management to the Android run time, which stops and kills processes as necessary to manage resources.
Dalvik and the Android run time sit on top of a Linux kernel that handles low-level hardware interaction including drivers and memory management, while a set of APIs provides access to all of the under- lying services, features, and hardware.
Dalvik Virtual Machine Dalvik is a register-based virtual machine that’s been optimized to ensure that a device can run multiple instances efficiently. It relies on the Linux kernel for threading and low-level memory management.
The Dalvik Virtual Machine
One of the key elements of Android is the Dalvik virtual machine. Rather than use a traditional Java virtual machine (VM) such as Java ME (Java Mobile Edition), Android uses its own custom VM designed to ensure that multiple instances run efficiently on a single device.
The Dalvik VM uses the device’s underlying Linux kernel to handle low-level functionality including security, threading, and process and memory management.
All Android hardware and system service access is managed using Dalvik as a middle tier. By using a VM to host application execution, developers have an abstraction layer that ensures they never have to worry about a particular hardware implementation.
The Dalvik VM executes Dalvik executable files, a format optimized to ensure minimal memory foot- print. The .dex executables are created by transforming Java language compiled classes using the tools supplied within the SDK.
Understanding Application Priority and Process States
The order in which processes are killed to reclaim resources is determined by the priority of the hosted applications. An application’s priority is equal to its highest-priority component.
Where two applications have the same priority, the process that has been at a lower priority longest will be killed first. Process priority is also affected by interprocess dependencies; if an application has a dependency on a Service or Content Provider supplied by a second application, the secondary application will have at least as high a priority as the application it supports.
All Android applications will remain running and in memory until the system needs its resources for other applications.
It’s important to structure your application correctly to ensure that its priority is appropriate for the work it’s doing. If you don’t, your application could be killed while it’s in the middle of something important.
The following list details each of the application states shown in Figure (see the attached image) explaining how the state is determined by the application components comprising it:
Active Processes Active (foreground) processes are those hosting applications with components currently interacting with the user. These are the processes Android is trying to keep responsive by reclaiming resources. There are generally very few of these processes, and they will be killed only as a last resort.
Active processes include:
* Activities in an “active” state; that is, they are in the foreground and responding to user events. You will explore Activity states in greater detail later in this chapter.
* Activities, Services, or Broadcast Receivers that are currently executing an onReceive event handler.
* Services that are executing an onStart, onCreate, or onDestroy event handler.
Visible Processes Visible, but inactive processes are those hosting “visible” Activities. As the name suggests, visible Activities are visible, but they aren’t in the foreground or responding to user events. This happens when an Activity is only partially obscured (by a non-full-screen or transparent Activity). There are generally very few visible processes, and they’ll only be killed in extreme circumstances to allow active processes to continue.
Started Service Processes Processes hosting Services that have been started. Services support ongoing processing that should continue without a visible interface. Because Services don’t interact directly with the user, they receive a slightly lower priority than visible Activities. They are still considered to be foreground processes and won’t be killed unless resources are needed for active or visible processes.
Background Processes Processes hosting Activities that aren’t visible and that don’t have any Services that have been started are considered background processes. There will generally be a large number of background processes that Android will kill using a last-seen-first-killed pat- tern to obtain resources for foreground processes.
Empty Processes To improve overall system performance, Android often retains applications in memory after they have reached the end of their lifetimes. Android maintains this cache to improve the start-up time of applications when they’re re-launched. These processes are rou- tinely killed as required.
How to use memory efficiently
Android manages opened applications which are running in the background, so officially you shouldn’t care about that. This means that it closes the applications when the system needs more memory. However, most android users are not very satisfied with how it does its things because sometimes it leaves too many processes running which causes sluggishness’ in everyday performance. We can use advanced task killer/task manager and it does its job very well.
Source:
Code:
http://mobworld.wordpress.com/2010/07/05/memory-management-in-android/
Click to expand...
Click to collapse
Sweet!! Good Info.. But wrong Section. You should port this in the General Section to help all!
rickysa2000 said:
Sweet!! Good Info.. But wrong Section. You should port this in the General Section to help all!
Click to expand...
Click to collapse
Oh. I thought this belongs to Q&A.
Any mods here who can move this to "General" please.
This would be why when you open the built in task manager nothing or only your launcher shows up but when you open ATK multiple other programs are shown open, correct?
I found similar information while researching battery saver programs. I keep ATK when I have stubborn apps that are stuck because it is easier to get through than Android Task Manager but the auto-kill feature is always disabled. Good coverage of this info.
bclark said:
This would be why when you open the built in task manager nothing or only your launcher shows up but when you open ATK multiple other programs are shown open, correct?
Click to expand...
Click to collapse
Exactly! If all programs/processes show up, like they do in ATK, it could cause instabilities in the system when the user kills any important process knowingly/unknowingly.
trekie86 said:
I found similar information while researching battery saver programs. I keep ATK when I have stubborn apps that are stuck because it is easier to get through than Android Task Manager but the auto-kill feature is always disabled. Good coverage of this info.
Click to expand...
Click to collapse
Thanks you. Saw too many threads/posts with questions about ATK and killing tasks. So compiled this so they could all be directed to this thread.
I don't mean to go digging up old threads, but I just wanted to post my opinion here on this memory clearing ordeal.
After reading the entire thread, I am even MORE inclined to want to use ATK or something similar...
At the very bottom of the post, last paragraph, it reads -
How to use memory efficiently
Android manages opened applications which are running in the background, so officially you shouldn’t care about that. This means that it closes the applications when the system needs more memory. However, most android users are not very satisfied with how it does its things because sometimes it leaves too many processes running which causes sluggishness’ in everyday performance. We can use advanced task killer/task manager and it does its job very well.
Click to expand...
Click to collapse
Here's my take -
While there is no way to override Dalviks operations for application retention, at least while you're operating the device you can keep the memory clear by monitoring and assisting in clearing it out, manually; Which will in fact yield a performance boost for a duration of time. Based on the description of how Dalvik operates, this is true.
Exactly how long of a duration I don't know. But it is as obvious as it gets that while Dalvik memory management is indeed cool, it is far from perfect and definitely induces low memory situations that CAN in fact cause sluggish performance. That much is already known.
So, in my opinion, if you enjoy the absolute maximum performance out of your device, ATK or something similar is definitely NOT a bad idea. Though it has to be done manually and after a period of time applications are brought back into memory, clearing the memory before opening an application allows full memory access to that application and also inevitably reduces CPU load as it removes the requirement for Dalvik to "shove" other applications on idle off the memory to make room for the active applications.
Personally, I just use Task Manager. It seems much more effective at clearing the memory.
Well, there are times when my phone is on for abt a week or so without turning off or rebooting (the times when I resist flashing roms or kernels or modems) and still I hardly feel any sluggishness. And I do NOT use any task killers. I let android handle everything its way.
And there is a difference between cleaning up memory say once every couple days, and having ATK set up to free up memory every hour or two. The first one could be helpful while the second is a battery killer.
rickysa2000 said:
Sweet!! Good Info.. But wrong Section. You should port this in the General Section to help all!
Click to expand...
Click to collapse
why quote such a big post to tell this
come on
regards
strategist99 said:
why quote such a big post to tell this
come on
regards
Click to expand...
Click to collapse
^
Why necropost ?!? Come on !
(just messin with ya)
Sent from my SGH-I897 using xda premium
how about file expert's memory management options?
ok - i get what's being written at the top of this. however, i do wonder about being able to tweak things some, mainly because on file expert's memory manager there's several memory config options: gamer, multi-tasker, light user, whatnot.
i got a phone to fit in my pants pocket, so it doesn't come with tons of RAM. and it freezes quite a bit when swapping between apps. of course there could be many other reasons, but still...
file expert's options don't seem to be persistent, so it's hard to get a handle on which setting would work best. now - would there be a way of making persistent memory optimization changes? if, how?
what is an amount of free memory that would need to be there for things to be smooth? by ATK, i get south of 50Mb quite often, which seems low.
i don't really like ATK's auto-kill - don't know what it will kill, and it seems that a free memory kill-threshold would be better than one based on time.
zdoe said:
ok - i get what's being written at the top of this. however, i do wonder about being able to tweak things some, mainly because on file expert's memory manager there's several memory config options: gamer, multi-tasker, light user, whatnot.
i got a phone to fit in my pants pocket, so it doesn't come with tons of RAM. and it freezes quite a bit when swapping between apps. of course there could be many other reasons, but still...
file expert's options don't seem to be persistent, so it's hard to get a handle on which setting would work best. now - would there be a way of making persistent memory optimization changes? if, how?
what is an amount of free memory that would need to be there for things to be smooth? by ATK, i get south of 50Mb quite often, which seems low.
i don't really like ATK's auto-kill - don't know what it will kill, and it seems that a free memory kill-threshold would be better than one based on time.
Click to expand...
Click to collapse
Auto-kill is quite bad as the it kills processes that always reset.
As for your ram, you could run a Bigmem kernel. 50ram is fairly normal with regular processes and a couple extras. It all depends on what you use/run.
I would need your phone's setup to help you more towards it though.
xperia ray, snapdragon, 512Mb of RAM
don't know what bigmem kernel is or would do. i'm a noob.
the phone as above. list of installed apps courtesy titanium attached - except i've since killed ATK and now trying autokiller, which is good at least for the SD-card parameter tweaks it gives. not sure about its memory management aspects, but at least they're persistent.
list of apps
here's the list - the forum didn't take .htm
and i'm on CM7.2.
EDIT/UPDATE: unrelated to killer apps, but for those of you who came to this thread to find remedies for RAM shortage - my observation currently is that the best thing you can do to yourself is to enable swap. that, and taking out the "play store" took me from 5 crashes a day to 1 - and after half a day of multi-tasking apps i can see up to 80Mb of swap in use, with 60Mb of RAM free, and the phone still running smoothly.
How to detect if an app is in background
In the above article it is said that the memory management is completely under control of Dalvik VM and Android runtime.
Is it not possible for a device driver to intelligently check if any app in background and release memory (allocated inside driver).
onStop(): All the rendering is stopped.
Is it possible to check some app state value to see if app in background or minimized?
This is not the explanation of memory management but process management
Suggestions
Gamer Mode
New Taks Manager
Game Mode
Description: When putting your phone into Game mode it will automaticly stop all the running background applications, freeing as many RAM as possible.
- You won't be able to recieve text messages
- All background application sync will be stopped
- All unnecessary applications will be stopped
- Still able to recieve calls
- All required system applications will still be running
More Functionality
Give the user the ability to add their own blacklist or whitelist, so if users choose that their application must remain active, it will.
New Taks Application
Description: When it comes to memory or RAM the galaxy doesn't actually narrow it down. It doesn't have much RAM space and when you run too much services in the back, it will drain your battery as the preformance of your phone.
New Options
- Add a checkbox so users can choose if the app must run or be excluded from start up.
- Add an option that when you close the application, all the running background services will close with it
Possible system structure
Active Processes (Apps) | System Processes | Downloaded | All Applications
All other ideas or suggestion are all welcome
Intensity007 said:
Suggestions
Gamer Mode
New Taks Manager
Game Mode
Description: When putting your phone into Game mode it will automaticly stop all the running background applications, freeing as many RAM as possible.
- You won't be able to recieve text messages
- All background application sync will be stopped
- All unnecessary applications will be stopped
- Still able to recieve calls
- All required system applications will still be running
More Functionality
Give the user the ability to add their own blacklist or whitelist, so if users choose that their application must remain active, it will.
New Taks Application
Description: When it comes to memory or RAM the galaxy doesn't actually narrow it down. It doesn't have much RAM space and when you run too much services in the back, it will drain your battery as the preformance of your phone.
New Options
- Add a checkbox so users can choose if the app must run or be excluded from start up.
- Add an option that when you close the application, all the running background services will close with it
Possible system structure
Active Processes (Apps) | System Processes | Downloaded | All Applications
All other ideas or suggestion are all welcome
Click to expand...
Click to collapse
Both of those are already avaiable, the first is the Gamerzrom (although not perfect), the second is avaiable as many system manager app, search for it.
I have a few apps running in the background all the time. Facebook and blood and glory mainly. Is there a way to delete them for good? On Facebook I set it that no notifications and never refresh, and its still using up 12mb. Same with blood and glory. Any way to kill them for good? Is there an app maybe? Thanks.
Well, mainly in android apps have 4 components.
Two of those are Activities and Services.
The activities have UI, you can activate and use it. The services doesn't have UI since they are hidden. You can't Activate them manually and their purpse is to open the app fast. Deleting the app is the best way you can use a task manager to close them.
Advanced Task Killer, for example, has the ability to set timer for RAM clearing, you can set it to whenever you lock your screen.
if i helped you, hit the thanks button
Another way for ram.
I think of the amount of memory (ram) have effected to play game or run any application smoothly.
So If you use kernel Semaphore 2.7.4(GB) or 1.2.0 (ICS) there are choices for big memory to run application smoothly.
I want to kill an app like Facebook, and then I don't want it to run in the background after I close the app. When I kill the process , after aboit 10 seconds it goes on again!
Anyone!?
Anyone 2x?
use advanced task manager.or delete the facebook app and install fbm.it does not run in the background
I've found an useful article about Task killer apps:
Being a new member, I cannot post outside link.
Search for: Task killer apps What they do, and why you shouldn't use them ->
Autostarts
There is an app on android market called Autostarts, it's an amazing app i've used it for over a year now and never had any problems. what it does it stops apps like facebook from starting up automaticly and keeps the app fully closed until you choose to launch it. Same goes for any other app which you choose to disable from auto-starting by itself. This is why Autostarts is so much better than say a normal task killer because apps closed by task killers restart themselves a few minutes later so your just running round in circles trying to keep the app closed probably eating up more battery trying to close it every 5 minutes than if you just left the app alone, where as with autostarts you dissable the app once then thats it it wont start until you tell it to, perfect!
Autostart sounds quite good
I'd also recommend using titanium backup to freeze the app, unfreeze when you want it and then freeze when you dont.
Autostart probably sounds like the easier option, no need to keep freezing and unfreezing, but knowing about titanium backup and freezing apps doesn't hurt
UPDATE: Check post #2 for the updated information!
Hey guys, first off I know many are going to say "Another battery thread.." but I wanted to share what I have been doing to my Galaxy S5 and see what you guys are doing.
Device:
-Samsung Galaxy S5 (AT&T)
-Rooted (towelroot)
-Running The Extreme Debloated ROM below
-Stock battery
ROM: Being that we don't have any custom roms yet, less is more. You of course could use titanium backup or the like to freeze many of the apps, uninstall many of the bloat apps yourself or you could install the Extreme Debloated ROM from the link below.
[NCE}{SafeStrap]DeOdexed/Extreme Debloat/Stock/Android L Features/Under 400mb!
Screen: We all know the more dim the screen the better the battery life, I don't use auto brightness but some do.
Greenify: If you aren't using this yet, you should! Rooted or not, this app works!
Auto-Sync: If you can function without this, turn it off. All apps, change to sync less frequently.
CPU: If you are only using your device for simple tasks, underclock it. I have mine running at 300 MHz-1.498 GHz interactive cfq. Of course you can set the Governor to be on demand etc for when you need it. I use No-frills CPU Control
Llama: There are many apps that you can use but Llama is free and is easy to get going, check it out here. Below is what I have my events set to, of course there is a bit more to it (advanced settings, aka delays etc). I have the Llama events that I use attached below, just install Llama and then place the text file in the Llama folder (stored on the local sd, internal). Go to events and press the menu button, then import and select it.
Explanation Of Events For Llama:
1-When screen turns off, but is not in a call and music is not playing. Delay for 1 minute and then disable mobile data, disable wifi, run the shortcut (from greenify) "Hibernate Now", disable account sync. The delay can be customized, but I like it at 1 minute. I have read from Intelli3G that turning the signals on and off can effect battery life, so previously I had it with no delay. This is fine if you don't turn your phone on and off too often.
2-When screen turns on, enable mobile data, enable wifi, enable account sync (but don't update). This is straight forward, turn it all back on. You can select the account sync to update if you want.
3-Wifi off if not connected when screen turns on. Delay for 40 seconds and then disable wifi if not connected. Since event #2 turns on the wifi by default, this will turn it off if it is not connected to a network.
4-Mobile data off if on wifi. When the phone connects to wifi, delay for 45 seconds and then disable mobile data. You will still get texts/calls etc, but not use data of the network.
5-Mobile data on when wifi off. Just as event #4 but the reverse, since we turned off mobile data while the wifi was on we need to turn it on. No delay, because we want it back right away.
6-Phone powered on. When the phone turns on, delay for 30 seconds and then run the greenify hibernate now shortcut. You can increase the delay if you have any processes starting up on boot.
AFWall+: Any firewall app will do just fine, but if you want to specify the IPv6 support (4G) then this one works great! Just realize it is default to selecting apps allowed to use the network (aka white list), which for me is just the browser/messaging/swiftkey. I have a toggle widget set on my screen that I turn on/off depending if I need anything special (use the market/youtube etc). This keeps them from using the network, thus saving your battery.
Autostart Processes: You can use many apps to change this, but I used SD Maid. Turn off anything you don't need running in the background (facebook etc).
Ads: Might not save much, but blocking ads will help on your data usage at least. I like Adaway. I also like to patch the apps from using ads (paranoid much?), I would think that covering two bases is better than one. Use Luckpatcher for this.
Apps: Back on my first smart phone (Palm Pre), we didn't have specific apps at first for normal things like facebook so we used the browser for the majority of our needs. You can use instagram/facebook/email etc all via the browser, thus reducing app usage in the background (data use, push notifications etc). I have tried fast for facebook and many small email clients, but you are sacrificing lots. The mobile pages work close to the app, better than a clone app. If you are like me I like the style and functionality of facebook/gmail/instagram, but I have not found any apps that pull this off very well outside of the official ones. Being you can block the apps via firewall and force stop them with greenify it does help, but apps like facebook/gmail they keep checking for updates and keep running causing wakelocks. Some apps like AquaMail seem to do the trick for me.
Xposed Framework: I LOVE the functionality that it provides, as it reminds me of the modding that we had back on WebOS but with these frameworks running in the background it causes some battery lose.
Closing Notes: There are many other options and possibilities depending on how you use your phone, and of course your mileage may vary. These are from my own testing and readings, some things may not even help or be very effective but this is why I am posting this. Let us share what works best for our device! Being I don't run XPosed I can't use Intelli3G, but since I am cutting off data where I can it helps. I would be interested in putting my phone in 2G/3G/4GLTE with a button click, might be possible with Llama but I haven't tried.
Credits:
[email protected] for the towelroot!
[email protected] and @raynan for their awesome work on debloating the stock ROM!
[email protected] for his suggestions on tasker/Llama!
[email protected] for greenify!
[email protected] for No-frills CPU Control!
[email protected] for Llama, the reason my battery lasts longer!
[email protected] for AFWall+!
-dominik for adaway!
-ChelpuS for LuckPatcher!
If you have found ANY of this useful, have any suggestions, comments etc please post below. Click Thanks if you want to show appreciation if this did help you. Thanks!
Update #1:
-Coming soon!
Test #1:
Using the above information in post #1 I was able to get 32 Hours 15 Min (1 d 8 h 14 m 54 s) with 6 Hours Screen On Time! Check screen shots below for the proof, and comment below to the awesomeness! I will be doing a new test with the updates coming to the OP!
Test Subject:
-Check the attached BetterBatteryStats log for complete info!
-Samsung Galaxy S5 (AT&T)
-Rooted (towelroot)
-Running The Extreme Debloated ROM below
-Stock battery
-ROM: [NCE}{SafeStrap]DeOdexed/Extreme Debloat/Stock/Android L Features/Under 400mb!
can you post up some screen shots of your battery life / stats?
I'm on stock, rooted, bloat is frozen. I'm using grernify for games and other apps I don't use regularly or don't rely on for push notifications. I use adaway for ad blocking.
with just those steps taken, and using the phone as a smartphone, I can easily get 20+ hours off charger and a screen use of 5 hours.
I understand what you're trying to do here but what is the point of diminishing returns?
I have gotten around the 18 hour mark, but out of the box I was only getting around 12. I will try getting an accurate screenshot and try out a few other settings. Our batteries may vary slightly I'm sure, and at some point I bet there are diminishing returns like with underclocking. I will test it out and report back
Thanks for the input @Russ77
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
Updated! I was able to get 32h 15m battery life with 6h of screen on time! @Russ77 @GDofWR420 @UnhoIy
kalans said:
Updated! I was able to get 32h 15m battery life with 6h of screen on time! @Russ77 @GDofWR420 @UnhoIy
Click to expand...
Click to collapse
Can't put this thing down. Battery is great, I'm always on it and get almost 7 hours screen time before I throw it on the charger. For me I keep the screen on the lower setting with auto turned off and screen set to dynamic for that deep, bold color.
Sent from my SAMSUNG-SM-G870A using XDA Premium 4 mobile app
GDofWR420 said:
Can't put this thing down. Battery is great, I'm always on it and get almost 7 hours screen time before I throw it on the charger. For me I keep the screen on the lower setting with auto turned off and screen set to dynamic for that deep, bold color.
Sent from my SAMSUNG-SM-G870A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
+1
I'm at 4 hours 17 minutes screen use and have 42% battery remaining. I'll easily surpass 7 hours of screen use and probably 20 hours total battery.
when idle on mobile signal my phone consumes about 1%/hr. if I wasn't playing couch potato today (its 107 outside) and was doing stuff I'd use around 6 hours of screen time and could go 30 hours total battery time.
this is all with no battery saving measures taken other than greenifying all banking and game apps.
Hey guys, first off I know many are going to say "Another battery thread.."
Click to expand...
Click to collapse
Yes, to play devil's advocate here:
The apps and tweaks are going to make some difference, but it's more about how you use your phone, rather than doing a bunch of tweaks and modifications, which many of us have done at some point or another (the same tweaks but maybe with different apps and Roms).
I've seen posts around here talking about getting 3 and 4 days average, and sometimes 5 days of battery, and I always say that's because you all don't use your phone that much.
It's all about how you use your phone. I only get up to 48 hours with moderate use; that's terrible battery life by the standards around here; and with heavy use, with my brightness cranked up because I like my colors pretty and bright, and with consistently playing games all day, I'm only getting about 4 and a half hours screen on time. That battery life might be 7 hours or 2 full days, depending on how much else I'm doing with the phone.
I love how I posted this thread to help others but instead it is just getting people to post about the opposite.. I just got 54+ hours out of the OEM battery, but I am sure nothing I did helped.. Insert sarcasm here.
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
kalans said:
I love how I posted this thread to help others but instead it is just getting people to post about the opposite.. I just got 54+ hours out of the OEM battery, but I am sure nothing I did helped.. Insert sarcasm here.
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
Click to expand...
Click to collapse
Oh, I don't doubt the 54 hours battery life. Like I said, the apps and tweaks are going to make some difference. But it all depends on how you use your phone. I'm not going to get 54 hours battery, even if I use your phone because of what I do. I'm playing games, or streaming radio, or watching movies or Youtube, and that's not all day, and with my screen bright.
Just me personally, I don't like to worry too much about how much battery life I'm getting. When I start doing that, then I find myself going out my way and doing things different (such as frequently checking the battery stats and stretching the phone's downtime) like I would not normally do, trying to see how much battery that I can actually get, instead of just enjoying the phone as I would normally use it.
When I had my old HTC Evo a few years back, I was doing everything that you're doing, and then some (as you can find several of these threads for every phone), trying to get every little ounce of juice that I could out that miserable battery. Same type apps and Roms, just different names. I had apps that turned off Wifi, data, bluetooth, and even crashed the phone once in a while. I actually got used to turning my screen brightness all the way down so that I could barely see anything. And it was great having a Rom so de-bloated, that I got a chance to find out what was missing when I got lost driving and needed directions. Yeah, it made a difference in the battery all right.
kalans said:
UPDATE: Check post #2 for the updated information!
Hey guys, first off I know many are going to say "Another battery thread.." but I wanted to share what I have been doing to my Galaxy S5 and see what you guys are doing.
Device:
-Samsung Galaxy S5 (AT&T)
-Rooted (towelroot)
-Running The Extreme Debloated ROM below
-Stock battery
ROM: Being that we don't have any custom roms yet, less is more. You of course could use titanium backup or the like to freeze many of the apps, uninstall many of the bloat apps yourself or you could install the Extreme Debloated ROM from the link below.
[NCE}{SafeStrap]DeOdexed/Extreme Debloat/Stock/Android L Features/Under 400mb!
Screen: We all know the more dim the screen the better the battery life, I don't use auto brightness but some do.
Greenify: If you aren't using this yet, you should! Rooted or not, this app works!
Auto-Sync: If you can function without this, turn it off. All apps, change to sync less frequently.
CPU: If you are only using your device for simple tasks, underclock it. I have mine running at 300 MHz-1.498 GHz interactive cfq. Of course you can set the Governor to be on demand etc for when you need it. I use No-frills CPU Control
Llama: There are many apps that you can use but Llama is free and is easy to get going, check it out here. Below is what I have my events set to, of course there is a bit more to it (advanced settings, aka delays etc). I have the Llama events that I use attached below, just install Llama and then place the text file in the Llama folder (stored on the local sd, internal). Go to events and press the menu button, then import and select it.
Explanation Of Events For Llama:
1-When screen turns off, but is not in a call and music is not playing. Delay for 1 minute and then disable mobile data, disable wifi, run the shortcut (from greenify) "Hibernate Now", disable account sync. The delay can be customized, but I like it at 1 minute. I have read from Intelli3G that turning the signals on and off can effect battery life, so previously I had it with no delay. This is fine if you don't turn your phone on and off too often.
2-When screen turns on, enable mobile data, enable wifi, enable account sync (but don't update). This is straight forward, turn it all back on. You can select the account sync to update if you want.
3-Wifi off if not connected when screen turns on. Delay for 40 seconds and then disable wifi if not connected. Since event #2 turns on the wifi by default, this will turn it off if it is not connected to a network.
4-Mobile data off if on wifi. When the phone connects to wifi, delay for 45 seconds and then disable mobile data. You will still get texts/calls etc, but not use data of the network.
5-Mobile data on when wifi off. Just as event #4 but the reverse, since we turned off mobile data while the wifi was on we need to turn it on. No delay, because we want it back right away.
6-Phone powered on. When the phone turns on, delay for 30 seconds and then run the greenify hibernate now shortcut. You can increase the delay if you have any processes starting up on boot.
AFWall+: Any firewall app will do just fine, but if you want to specify the IPv6 support (4G) then this one works great! Just realize it is default to selecting apps allowed to use the network (aka white list), which for me is just the browser/messaging/swiftkey. I have a toggle widget set on my screen that I turn on/off depending if I need anything special (use the market/youtube etc). This keeps them from using the network, thus saving your battery.
Autostart Processes: You can use many apps to change this, but I used SD Maid. Turn off anything you don't need running in the background (facebook etc).
Ads: Might not save much, but blocking ads will help on your data usage at least. I like Adaway. I also like to patch the apps from using ads (paranoid much?), I would think that covering two bases is better than one. Use Luckpatcher for this.
Apps: Back on my first smart phone (Palm Pre), we didn't have specific apps at first for normal things like facebook so we used the browser for the majority of our needs. You can use instagram/facebook/email etc all via the browser, thus reducing app usage in the background (data use, push notifications etc). I have tried fast for facebook and many small email clients, but you are sacrificing lots. The mobile pages work close to the app, better than a clone app. If you are like me I like the style and functionality of facebook/gmail/instagram, but I have not found any apps that pull this off very well outside of the official ones. Being you can block the apps via firewall and force stop them with greenify it does help, but apps like facebook/gmail they keep checking for updates and keep running causing wakelocks. Some apps like AquaMail seem to do the trick for me.
Xposed Framework: I LOVE the functionality that it provides, as it reminds me of the modding that we had back on WebOS but with these frameworks running in the background it causes some battery lose.
Closing Notes: There are many other options and possibilities depending on how you use your phone, and of course your mileage may vary. These are from my own testing and readings, some things may not even help or be very effective but this is why I am posting this. Let us share what works best for our device! Being I don't run XPosed I can't use Intelli3G, but since I am cutting off data where I can it helps. I would be interested in putting my phone in 2G/3G/4GLTE with a button click, might be possible with Llama but I haven't tried.
Credits:
[email protected] for the towelroot!
[email protected] and @raynan for their awesome work on debloating the stock ROM!
[email protected] for his suggestions on tasker/Llama!
[email protected] for greenify!
[email protected] for No-frills CPU Control!
[email protected] for Llama, the reason my battery lasts longer!
[email protected] for AFWall+!
-dominik for adaway!
-ChelpuS for LuckPatcher!
If you have found ANY of this useful, have any suggestions, comments etc please post below. Click Thanks if you want to show appreciation if this did help you. Thanks!
Click to expand...
Click to collapse
I would Recommend you to use Hibernate App no need of root
Hibernate App
Running @cstayton bo3 Kool kit active rom and have phenomenal battery life. No spare apps here. Turned on power save mode at 18%.
Watched two episodes of dexter, a little over half an hour on dead space, 4 short phone calls, a hand full of text and a few hours on the Web and using the xda app.
kalans said:
UPDATE: Check post #2 for the updated information!
Hey guys, first off I know many are going to say "Another battery thread.." but I wanted to share what I have been doing to my Galaxy S5 and see what you guys are doing.
Device:
-Samsung Galaxy S5 (AT&T)
-Rooted (towelroot)
-Running The Extreme Debloated ROM below
-Stock battery
ROM: Being that we don't have any custom roms yet, less is more. You of course could use titanium backup or the like to freeze many of the apps, uninstall many of the bloat apps yourself or you could install the Extreme Debloated ROM from the link below.
[NCE}{SafeStrap]DeOdexed/Extreme Debloat/Stock/Android L Features/Under 400mb!
Screen: We all know the more dim the screen the better the battery life, I don't use auto brightness but some do.
Greenify: If you aren't using this yet, you should! Rooted or not, this app works!
Auto-Sync: If you can function without this, turn it off. All apps, change to sync less frequently.
CPU: If you are only using your device for simple tasks, underclock it. I have mine running at 300 MHz-1.498 GHz interactive cfq. Of course you can set the Governor to be on demand etc for when you need it. I use No-frills CPU Control
Llama: There are many apps that you can use but Llama is free and is easy to get going, check it out here. Below is what I have my events set to, of course there is a bit more to it (advanced settings, aka delays etc). I have the Llama events that I use attached below, just install Llama and then place the text file in the Llama folder (stored on the local sd, internal). Go to events and press the menu button, then import and select it.
Explanation Of Events For Llama:
1-When screen turns off, but is not in a call and music is not playing. Delay for 1 minute and then disable mobile data, disable wifi, run the shortcut (from greenify) "Hibernate Now", disable account sync. The delay can be customized, but I like it at 1 minute. I have read from Intelli3G that turning the signals on and off can effect battery life, so previously I had it with no delay. This is fine if you don't turn your phone on and off too often.
2-When screen turns on, enable mobile data, enable wifi, enable account sync (but don't update). This is straight forward, turn it all back on. You can select the account sync to update if you want.
3-Wifi off if not connected when screen turns on. Delay for 40 seconds and then disable wifi if not connected. Since event #2 turns on the wifi by default, this will turn it off if it is not connected to a network.
4-Mobile data off if on wifi. When the phone connects to wifi, delay for 45 seconds and then disable mobile data. You will still get texts/calls etc, but not use data of the network.
5-Mobile data on when wifi off. Just as event #4 but the reverse, since we turned off mobile data while the wifi was on we need to turn it on. No delay, because we want it back right away.
6-Phone powered on. When the phone turns on, delay for 30 seconds and then run the greenify hibernate now shortcut. You can increase the delay if you have any processes starting up on boot.
AFWall+: Any firewall app will do just fine, but if you want to specify the IPv6 support (4G) then this one works great! Just realize it is default to selecting apps allowed to use the network (aka white list), which for me is just the browser/messaging/swiftkey. I have a toggle widget set on my screen that I turn on/off depending if I need anything special (use the market/youtube etc). This keeps them from using the network, thus saving your battery.
Autostart Processes: You can use many apps to change this, but I used SD Maid. Turn off anything you don't need running in the background (facebook etc).
Ads: Might not save much, but blocking ads will help on your data usage at least. I like Adaway. I also like to patch the apps from using ads (paranoid much?), I would think that covering two bases is better than one. Use Luckpatcher for this.
Apps: Back on my first smart phone (Palm Pre), we didn't have specific apps at first for normal things like facebook so we used the browser for the majority of our needs. You can use instagram/facebook/email etc all via the browser, thus reducing app usage in the background (data use, push notifications etc). I have tried fast for facebook and many small email clients, but you are sacrificing lots. The mobile pages work close to the app, better than a clone app. If you are like me I like the style and functionality of facebook/gmail/instagram, but I have not found any apps that pull this off very well outside of the official ones. Being you can block the apps via firewall and force stop them with greenify it does help, but apps like facebook/gmail they keep checking for updates and keep running causing wakelocks. Some apps like AquaMail seem to do the trick for me.
Xposed Framework: I LOVE the functionality that it provides, as it reminds me of the modding that we had back on WebOS but with these frameworks running in the background it causes some battery lose.
Closing Notes: There are many other options and possibilities depending on how you use your phone, and of course your mileage may vary. These are from my own testing and readings, some things may not even help or be very effective but this is why I am posting this. Let us share what works best for our device! Being I don't run XPosed I can't use Intelli3G, but since I am cutting off data where I can it helps. I would be interested in putting my phone in 2G/3G/4GLTE with a button click, might be possible with Llama but I haven't tried.
Credits:
[email protected] for the towelroot!
[email protected] and @raynan for their awesome work on debloating the stock ROM!
[email protected] for his suggestions on tasker/Llama!
[email protected] for greenify!
[email protected] for No-frills CPU Control!
[email protected] for Llama, the reason my battery lasts longer!
[email protected] for AFWall+!
-dominik for adaway!
-ChelpuS for LuckPatcher!
If you have found ANY of this useful, have any suggestions, comments etc please post below. Click Thanks if you want to show appreciation if this did help you. Thanks!
Click to expand...
Click to collapse
I was/am having some issue importing the events for Llama I was wondering if I am doing something wrong or...? Is there a specific way of importing it?
Hey guys quick question I'm an avid user of power saving mode (not UPSM) but I feel it could do better so I've been working on my own profile in tasker to better extend my battery. My question is what's the CPU underclocked to in power saving mode
daltonhrrll said:
Hey guys quick question I'm an avid user of power saving mode (not UPSM) but I feel it could do better so I've been working on my own profile in tasker to better extend my battery. My question is what's the CPU underclocked to in power saving mode
Click to expand...
Click to collapse
1728 MHz, or 1.7 GHz on mine.
shortydoggg said:
1728 MHz, or 1.7 GHz on mine.
Click to expand...
Click to collapse
How many cores does it under clock
Hi Friends !
We have doze enabled in developer option setting.Now there is aggressive doze option which is by default enabled.
My doubt is weather using Greenify it helps further or it kills more battery.
Weather Greenify is useful in Nougat as this app is not updated since long.
What I have noticed that my Whatsapp is always in top or 2nd for battery eating with Doze/A.doze applied.
However when I uses Greenify it is able to hibernate WA and battery consumption with WA becomes less
in that case.
Someone suggest that without A.Doze battery stats is better.
Lately I have started to use Naptime also but didn't find any good on it for battery.
Anyone could put more light on optimized setting.
And Naptime/A.Doze was unable to hibernate Social APPS/Cloud apps/system apps only Greenify was able to do that.
Whatsapp still has it's place imo because the dumbest feature ever doze on the go exists, if your phone moves doze doesn't work as well as it should. Greenify isn't affected by that so if you greenify an app it will remain in hibernation no matter what until it is opened or called on.
the only thing i suggest that is useful is Wakelock detector. While by itself it is just for monitoring, if found when apps were misbehaving. E.g., i had an incorrectly configured Tasker profile that just drained my battery, and would have never caught it if not for this app.
But i would like someone (with a lot of free time) to re-flash their rom to stock, then use it for 1 week with Greenify, Naptime, G+N, neither. and report back battery stats.
I have a question regarding battery life, I am using magisk + Super SU. will it drain more battery ? To attain root in system I am having to use super su.
I used to be a greenify user but now not anymore ..the aggressive doze feature is awesome ..as for preventing WhatsApp to launch in background..you can switch off auto launch in background and also restrict background data in whatsapp and that extends my battery life dramatically
Sent from my ONEPLUS A3010 using XDA-Developers Legacy app
As I always say when it comes to computers and computing. Your system knows whats best for it. Use the system's doze over any third party app. Your system is always tailored to itself, whereas any third party app needs to be as inclusive as possible to apply to every phone out there.