I have a Galaxy S5 but I think this is a general question. I've modded and tweaked my cell phones for several years, but I know next to nothing about what I'm doing. That's why I do a LOT of research BEFORE doing anything. There's a lot of bloatware and unnecessary stuff floating around in the android system. I'm trying to reduce battery drain and speed up boot and processing speed.
The first problem I run into is trying to find anything about different software, components, and processes. I don't want to remove something and brick my phone or make it worse.
I'm running ROM Toolbox Lite using the Auto Start Manager.
Question: What is the relationship of app receivers and processing speed and battery life?
I'm considering turning off all receivers that start with bootup on programs I seldom use and don't want active until I start them.
1. Will those receivers ALL turn on when I decide to start a specific app? (That's what I'm hoping for)
2. How will this affect my speed, memory usage, and boot time?
From others experiences is it worth getting the PRO version?
Related
So here is an interesting one. So I still have me trusty X10 that I used for testing and backup. I also have a sim that floats from the X10 for testing to a Streak7 for play, with all my other off contract old school priced ATT services. With all of the extra devices traveling with the family, I am thinking of using the X10 as a dedicated hotspot of sorts, being that it would be significantly cheaper than a dedicated one, has unlimited data, and won't trip off the must have tethering features if I used a unlocked novatel.
SO my question you ask? Any suggestions on maybe optimizing a build for more specialized use? It would be interesting to even build a HotspotOS that would consist of the core Android with zero services other than those needed for the hostspot to run. Let it run fullscreen autostart, and you have yourself an Android Hotspot Appliance...
I will settle for some safe to remove that may eat battery hints. I believe hard throttling the cpu very low with setcpu would gain a good bit, but may impact throughput.
Hey guys... I feel like I cannot keep the phone on for more that 72 hours continuously.
I'm using Galaxy SII, G version (I9100G). Currently everything original (no custom rom/kernel)
I believe that most of Android phones have the same problem.
After 50 hours++ of up time of the phone (I mean the phone keeps on for 50 hours), The phone will become noticeable lag, but just a bit, not too much. One of the best evidence is in the game Fruit Ninja. I will feel the lag everytime I slash the fruit.
I'm sure that most apps is closed (except background apps like samsung keypad) and my battery usage graph is in straight horizontal line (without any optimize software, only with BetterBatteryStats). Only 500 - 600MB of RAM is used and I think this is normal.
After I restart the phone, the phone will become smooth and the RAM will be 300 - 400MB used only. Others do not show any difference.
And sure, the phone will repeat the same problem after some hours.
I wish I can keep the phone on continuously and no need to restart it frequently just like normal phones.
Can someone share some experience about this?
Is there any solution for this?
Or this is the nature of Android?
Can Custom ROM solve this?
Your best bet is to use an app killer program so you can close anything and everything running in the background.
Holy... If you mean task killers, I can tell you that it will not work, but will make the situation far worse for Android 2.3 and up...
I use one that's built in to the ROM that I use and my phone runs great for days on end.
I'm using Memory Booster (RAM Optimizer) as my first experiment to solve this problem...
I've had my suspicions about this since I first got the Droid X2. I think it may be possible for much of the lag many (most/all?) people experience at some time or another.
As a test, I can check free RAM in Advanced Task Killer when I first boot up the phone, and it will hover somewhere 150 megs with all user processes killed.
Then, when I check after 24 hours of constant use (with intermittent charging periods) I will struggle to get 100 megs with all user processes killed.
Finally, if I reboot the phone, I will be able to obtain a decent amount of freed-up RAM again.
Anyone experiencing anything similar?
Now, I must mention, I'm operating under the assumption that the X2 does not cache apps or files in the RAM. I suspect there is too little RAM at such a minimal speed to be able to clear RAM fast enough in the event that something non-cached is called on. I mean, even Microsoft was slow to use this cache method, as they first introduced it in Windows 7. A good example of this in Windows 7 is if you check the Task Manager, you will see that roughly only a quarter of your RAM is ever actually labeled as "free", even if you currently have no programs open or are using minimal amounts of RAM.
And it certainly doesn't feel as if the cache is working as intended if Motorola did infact implement it on our phones.
I have contimplated over this for quite some time and have also came to the same conclusion. But the real question is: What can we do about it?
Most likely nothing.
Not sure of this is actually the case but when V6 is ran for instance it does talk about cached apps and gives an "actual" free ram reading. I would guess that zepplinrox would not have worded it that way if it was not the case but I have no real evidence either way.
Sent from my DROID X2 using xda premium
This did happen to me when I ran Advanced Task Killer on cm7. I'd start with a very good 190 free ram (insane I know) and after a few hours I'd struggle to brake 110
Sent from my DROID X2 using Tapatalk 2
This is the nature of Android and Linux in general. When you start an app (or a process), it will remain in memory until it is cleared by the OS. The problem with task killers and Android 2.3.x and above is this: Android 2.3.x and above RESPAWN the killed task since the OS did not kill it. Plus, there is no way to FORCE to OS to kill an app that is in the background. What Android does is renice the process until it is a positive number, greater than 1, then it kills the process. Android 2.3.x was designed to "auto manage" those tasks. If you run htop from an ADB session and launch apps and use the back button to back out of them, you will notice that the amount of free memory diminishes. Then, after sitting for a time, the amount of free memory slowly begins to increase. When an app that requires a bunch of memory is launched, the Android will kill those background apps to free up more memory. In theory, it is a great way to manage the memory. In this respect, apps that have been launched in that past will start up faster. Personally, I like having control over things. You could possibly write a script that will renice a process to something like +20 and then Android will kill it automatically, but that would be a very risky prospect as it might kill RUNNING foreground apps as well.
Hope this little explanation helps!
Ciao!
DX2 Version History lesion / Android Process Cache
theredvendetta said:
I've had my suspicions about this since I first got the Droid X2. I think it may be possible for much of the lag many (most/all?) people experience at some time or another.
As a test, I can check free RAM in Advanced Task Killer when I first boot up the phone, and it will hover somewhere 150 megs with all user processes killed.
Then, when I check after 24 hours of constant use (with intermittent charging periods) I will struggle to get 100 megs with all user processes killed.
Finally, if I reboot the phone, I will be able to obtain a decent amount of freed-up RAM again.
Anyone experiencing anything similar?
Now, I must mention, I'm operating under the assumption that the X2 does not cache apps or files in the RAM. I suspect there is too little RAM at such a minimal speed to be able to clear RAM fast enough in the event that something non-cached is called on. I mean, even Microsoft was slow to use this cache method, as they first introduced it in Windows 7. A good example of this in Windows 7 is if you check the Task Manager, you will see that roughly only a quarter of your RAM is ever actually labeled as "free", even if you currently have no programs open or are using minimal amounts of RAM.
And it certainly doesn't feel as if the cache is working as intended if Motorola did infact implement it on our phones.
Click to expand...
Click to collapse
Your question is a bit complex. See back when Droid X2 first was released it had 2.2.3 for most users, and didn't have very good application memory management. This was the start of many applications such as "Advanced Task Killer" that you mentioned. These apps were supposed to help in closing apps that were running all the time.
Things changed a bit with the Gingerbread (2.3.3) release. This initial release made the Droid X2 useable. In my opinion the DX2 prior to Gingerbread was nearly a brick! I had many reboot issues, FC, connection issues, GPS issues, etc. With 2.3.3 many issues were eliminated, while others were reduced enough that they didn't bother me TO bad.
2.3.4 came out to fix battery issues largely...
Now I realize you weren't asking for a history lesion, but it is useful to know these things to know where things were and where things are today. I am currently running 2.3.5/412 and have been for months. I can say from experience, Android DOES cache background processes. I thought it did back in 2.3.4, but i can't remember... I don't think it did back in 2.2.x or at least the OS didnt' inform the users via GUI.
Your question about performance though? Yeah the DX2 is crap! I love the physical layout, but it has MANY issues with performance... some have been reduced by doing build.prop edits, yet I have realized that many who post these edits have posted wrong.... for example, they are increasing the buffer sizes thinking this will help internet speeds. This is super complex, but Google "Buffer Bloat" and you'll see how larger buffers often mean greater throughput, but MUCH greater latency....
simply put... big buffer == faster download of individual files.... smaller buffer == slightly slower download but MUCH more responsive
I'm not sure if that answered your question or not... let me know how I did or if I just rambled perhaps =P
hello everybody
the question is simple..... i have a E790 and i want a Rom, kernel, mod or configuration for best battery life... any suggestions?
Slick V3 plus MEs kernel. Lower min clock speed and use badass governor. I've never had anything better. I'm currently using MEs EG8 ROM, which I like better, but battery life is slightly less then when I used Slick.
Sent from my LG-E970 using XDA Premium 4 mobile app
x-geo said:
hello everybody
the question is simple..... i have a E790 and i want a Rom, kernel, mod or configuration for best battery life... any suggestions?
Click to expand...
Click to collapse
Best configuration for extended battery life = power off when not in active use.
Not trying to be a jerk here, but while stating that question is simple, the answer most certainly isn't. There are a huge number of factors that play into battery life, and you haven't provided any info at all to us to provide good answer.
The answer depends on how you use the device. Do you need extended idle time but not high performance? underclock, undervolt, freeze all your background apps. Do you have lots of stuff running in the background? Try greenify paid with xposed features. Do you want the most possible screen on time? drop your brightness as low as you can stand it. Run in Airplane mode. Are you in a crappy service area? Turn off cell radio and use Wifi only.
We don't know what you need for connectivity, or how you use the device, or what apps you run, or anything else. We need tons more info to try to chase battery life. We don't know what will constitute "acceptable" performance, to you, when down-tuning processor speeds and brightness and things. These are all things you need to experiment with to find what works best for you.
In general, I've found that for my use-case, the new 4.3 ROMs are marginally better on battery life than prior versions. I typically get about 4 hours screen on time, with around 20 hours up-time, and minimal phone calls (15min per day or so) and end up having 15-20% battery left when I put the phone on the charger. In moderate use, I look for wakelocks to be roughly twice my screen on time. I don't run much processor intensive stuff, the majority of my awake time is spent at minimum clock speed.
Min screen brightness
x-geo said:
hello everybody
the question is simple..... i have a E790 and i want a Rom, kernel, mod or configuration for best battery life... any suggestions?
Click to expand...
Click to collapse
Min screen brightness, lower timeout, eco mode, task killer, data off and airplane mode at the office (or school or whenever you use "silent mode" instead)
endeavor2908 said:
Min screen brightness, lower timeout, eco mode, task killer, data off and airplane mode at the office (or school or whenever you use "silent mode" instead)
Click to expand...
Click to collapse
Be very careful with task killers. If you try to kill stuff that auto restarts, you will end up causing battery draining start / kill loops. In general task killers haven't been necessary since gingerbread.
Sent from my Optimus G using Tapatalk 4
dandrumheller said:
Be very careful with task killers. If you try to kill stuff that auto restarts, you will end up causing battery draining start / kill loops. In general task killers haven't been necessary since gingerbread.
Sent from my Optimus G using Tapatalk 4
Click to expand...
Click to collapse
As stated before, the 4.3 roms seem to have better battery life then the previous versions.
Certain apps can help with battery life as well. "Tasker" can be setup to disable functions when not needed.
"SetCPU" can be used to setup profiles to change min/max frequencies and change governors when certain conditions are met... this can also be done with Tasker but requires a good understanding of Tasker functions.
"Greenify" is also a good app. It will hibernate apps that you choose. This can prevent certain apps from running in the backround until you actually use them.
Turn off animations
Turn off animations and transitions, keep the minimum amount of widgets and location services from social apps
Kernel Confusion
Dear Concern,
m using AT&T LG Optimus G (e970), i just rooted my phone and unlocked my bootloader. the confusion m having ritenow is
m about to install the new custom rom in my phone but m confused about the kernel thing that ppl used to talk here .. my current software information is
Android Version :: 4.1.2
Kernel Version ::: 3.4.0
Software Version : E97020J
Can anyone guide me if i need to flash kernel while installing the custom roms *4.4.2*, and what are the risks?
is it necessary to flash kernel or not ??
Regards.
Moiz
Its not necessary to flash separate kernel..custom ROMs come with embedded kernels sometimes modified from existing kernels,such as mizry's AK kernel...flashing separate kernels are optional
Sent from my LG Optimus G using XDA Premium 4 mobile app
Our device isn't considered to be powerful anymore. It's became an complete underdog. Thanks to Android's flexibility, you can force to make your phone pretty much fly with several tweaks.
1. Delete as much bloatware as possible.
This is regarded as an easiest, noobiest option to improve your phone's performance. Many OEM apps stays hibernated in the RAM, thus limiting free RAM available to the user and sometimes even stressing NAND too much. In the end, it's the best to keep your phone as clean and deleting useless apps on the fly.
2. Don't install too much apps into NAND memory
Benchmarks shown, that our phone's NAND chip is considered to be rather slow. Since many apps access small amounts of random data pretty much constantly, it's better to have less apps installed on your phone.
3. Avoid using app killers
This is a placebo effect, since Android's memory management is inferior to what app killers are doing. Many apps stays in such state, where they are ready to be launched almost instantly. App killers, however, pretty much screw all the mandatory functions and stresses the phone even more than before. Launcher redraws are rather common occasion when app killer is being used.
4. Use custom kernel
Custom kernels often offer more features and are more optimized to make the use of available hardware. OEMs never seem to mess around with kernels much, since they want to have their product as stable as possible. Devs, however, mess around with kernels and extract almost double the real-time performance.
5. Never fill up your storage completely
The more data is available on the storage, the harder is getting to find it. Since data is laid randomly, it searches for the information location. When there are too much data, it gets harder to find the data needed. Often slower cards, like Class 2 or Class 4, are considered to be the better choice, since those cards are much faster at writing and reading marginal data randomly.
6. Select the I/O scheduler, CPU governor wisely
These things manipulate with the main hardware. The better optimized the governors are, the better the phone will run and won't drain the battery as much. Though keep in mind, that many governors have their own drawbacks.
sioplus is one of the better I/O schedulers. It allows access to random data pretty quickly, which ensures smooth and snappy performance in the system.
ondemand is the most common and is the stapple and the base of many custom governors available today. It's method is pretty simple - whenever phone registers a touch input, it automatically raises the CPU speed to the max. In retrospect, it should give great performance, but it usually suffers from poor response.
7. Play around with Dalvik VM settings
My optimized settings (feel free to use them):
dalvik.vm.heapstartsize=6m (size when first launched)
dalvik.vm.heapgrowthlimit=64m (limit of standard app)
dalvik.vm.heapsize=192m (heap for large app)
These settings pretty much controls our multitasking. Each phone has it's own specified settings, so it could run better.
Lowering these settings could majorly improve performance, but it could slow down around, when there too much heavy apps running in the background.
Raising these settings could improve multitasking, since less CPU power is required to extract certain data to the RAM. Scrolling a heavy webpage, for instance - raising these settings could improve scrolling smoothness and loading times, since there isn't a need to clean the heapsize as frequently as it was before.
More suggestions are coming later. If you found this article useful, please leave THANKS!
Good day.