Database Users

*UPDATED* HTC EVO Best Practices for Battery Management on AOSP ROMs

Last Edited 4/25/2011 @ 1:00PM EST
*** I’ve updated on my previous post on HTC EVO Best Practices for Battery Management that I’ve put together. There were certain steps that were fine tuned and others that were either added or removed. I just wanted to share with everyone in order to save the time I spent researching, applying and testing these fixes on my EVO and a couple of other EVO’s I’ve tested. ***
*** Just an FYI, I didn’t write any of the apps/codes listed below. I just spent a lot of hours researching methods to improve the battery life on my EVO on several different sites. I’ve linked the sites where I got the information and giving ALL credit to the original posters. If I missed any names and If there are anybody that needs credit to be added for any of the steps below, please let me know and I’ll add them right away. ***
*** These steps have been ONLY tested to work on AOSP ROMs like Destroyer v2, CyanogenMod and MIUI. ***
*** Finally, this is meant to just be a guide for Best Practices for Battery Management. I’ve tested these steps on several HTC EVO’s which had Destroyer v2, CyanogenMod 7 or MIUI and had no issues. If you decide to try these steps in the guide, I take no responsibility for any items that might go wrong with your phones . ***
All that said, let’s get started. I’m looking to keep this as a “Living Document”, so I will continue to update and edit this original post with any new info that is shared by others or get discovered over the next few weeks. For anyone that’s new to rooting and flashing ROMS, I’ve added the first two steps. Most 99% of everyone else on this site, please move onto Step 3.
Step One, Root Your Phone.
Easiest way to do that is to go to http://unrevoked.com/ and select your phone. Then select Unrevoked3 “Painless root and flash”. If you’re a MAC or Linux user, just download the software. If you’re on a Windows computer, download and install the HBoot Drivers by clicking on “More Info?” Once you launch the software, just follow the onscreen prompts and your phone should be rooted within 5-10 minutes.
Step Two, Backup and then Flash a ROM.
Easiest way to do that, is after you’ve rooted the phone, go to the market and download the app ROM Manager by ClockworkMod. Once you access the app, it's very important to first backup the ROM that came prepackaged with your phone in case you ever need to flash back to it. Click on "Backup Current ROM", I even saved a copy of that backup on my computer incase I need to copy it back to my phone.
To flash a new ROM, click on click on “Download ROM” and you’ll be able to install CyanogenMod 7.0.0 Stable Release. Or you can go to their site and download the ROM from them at http://www.cyanogenmod.com/ Another ROM that this works well with the steps below is MIUI and you can download that ROM from http://www.miuiandroid.com/
Step Three, Upgrade the Kernel.
I’ve found that every person’s phones are setup differently. Also different kernels work better on certain phones then others. The two best kernels are SavagedZen and Tiamat. Personally, just my opinion, I got better performance from SavagedZen kernels, so that’s what I go in detail below. Although test for yourself, as Tiamat 3.3.7 has gotten great reviews also.
There are also different type of kernels as CFS, BFS or SBC and no-SBC. What are the differences?
SBC is Super Battery Charge. Basically, it enables a trickle charging effect on the charger. It fills the battery up to 100% so when you pull it off of the charger, it's absolutely full. The noSBC kernels use the stock battery driver and charge differently. Some users are not comfortable with SBC and prefer not to use it. They do not trust it and believe it may cause failure although there has been no evidence that it will actually do so. Again, this is a user preference and why both builds are created at this time.
As for CFS or BFS, they are schedulers. CFS is the default Android scheduler that all stock kernels use. Its called the Completely Fair Scheduler and schedules the CPU fairly. BFS, or Brain F*** Scheduler, gives the present task a higher priority and background tasks less CPU. Which one to use is more or less on the user.
Most people wouldn't notice any difference. In theory, watching videos, playing games, and listening to music should be smoother with BFS, because it emphasizes the foreground task. CFS should be better for running background tasks, because it gives equal priority to everything. And some peoples' phones don't play nicely with BFS, so CFS is generally the reliable fall-back option.
Above is just a summary, although if you want to read more in detail about kernels, I got all the info above from this link http://www.cs.unm.edu/~eschulte/data/bfs-v-cfs_groves-knockel-schulte.pdf
Finally, once you’ve installed CM7 or MIUI, next step is to upgrade the kernel to Savaged-Zen. Go to this link http://mirror.savaged-zen.com/ and download the kernel from April 7th named “SavagedZen-1.1.0-CFS-HAVS-WiMAX-GB-signed.zip” and copy it to your SD card. Then turn off the EVO and turn it back on in recovery mode (Holding down the down volume button then then pressing power). Once ClockworkMod Recovery loads up, scroll down and select “Install zip from sdcard”, then scroll down and select “choose zip from sdcard”. After that, just scroll down to where you’ve saved the Savaged-Zen kernel and install it. Once the phone reboots, check to see if the kernel has been applied properly by going into Settings\System\About Phone (from MIUI menu) and then click on More Information. Kernel version should now have SavagedZen listed.
Step Four, Lower voltages on AOSP kernels.
–viperboy- had a great post on this topic, below is the link for his instructions http://forum.xda-developers.com/showthread.php?t=1028322 . I usually start off first by flashing the 50mV.zip and if it’s stable for a day or two, then I upgrade to 75mV.zip. On one EVO, I went up to 100mV and it started rebooting until I lowerd it back to 75mV. Haven’t had any issues with it since. On another EVO, I had to lower it from 75mV to 50mV to resolve freezing issues and haven’t had any issues with it since. Point is, you have to find the best voltage level that works best for your phones.
Step Five, change the Heap levels.
After updating the kernel and voltage levels, download VM Heap Tool from the Market. That tool will let you adjust the heap size on your phone, which Heap is the amount of memory each application can use. By default, your phone is set to 32m, which has issues with force closers of the launders and files. After you download the app, adjust the heap level to 40+. I've gone with 44m and haven't had any force closers, where before I would get 1 or 2 a day.
People running the latest build of MIUI release 1.4.22 Beta 7, stiffspliff changed the default MIUI Heap level to 64. So any MIUI users on the new release do not need to install\use this tool anymore.
Step Six, download BatteryCalibration app from the Market.
Useful tool especially if you like to keep switching\testing new ROMs on your phone. Calibration needs to be done after flashing a new ROM, since the program will remove the batterystats.bin system file. The OS generates a new clean batterystats file soon, thus any fake information from the previous ROM is removed.
Step Seven, manually setup the display settings.
When checking the Battery Settings\Battery Use, the Display is usually the biggest battery drain. To help offset this a little bit, go to Display Settings and turn automatic brightness off. Then manually setup the display at 25-30% brightness. Usually just take it down as far possible that you feel you’re comfortable seeing the screen properly.
Step Eight, condition the battery
Below are the steps to follow from a XDA member HipKat that have worked nicely to condition the battery.
1 - The "HTC Method w/10 Time Unplug"
Charge to full, unplug, turn off the phone, charge while off for another hour. Unplug, turn the phone on for 2 minutes, turn it off again, charge for another hour.
Unplug til the light goes off, plug back in til it turns green.
Do that 10 times.
Boot to Recovery, while plugged in. Clear battery stats, boot to system. And wait 2 mins, THEN unplug.
Also, I keep my GPS, mobile data and WiFi off unless I need it. You don't need either of those to make phone calls or texts.
Step Nine, what to AVOID
This step isn’t anything to install or update on your phone, it’s more meant for what type of apps to avoid.
First is Juice Defender, who with more research I’ve found could either help or drain your battery life. If you have JD on all day when you're not really using your phone much, in an area where your phone would normally be searching for data all day, wasting power, the battery savings are HUGE.
Although, if you're constantly using your phone, the battery savings are negligible at best, and negative at worst, since it would be constantly turning your data service on and off. So depending on each person’s definition of how they use the phone, JD might be an application to avoid, especially if you’re a mid to heavy user of your phone.
Next is any type of Task Killers. XDA poster Justin.G11 has a in detail blog on this topic and below is the link for anyone interested.
http://egotoobigtovirtualize.blogspot.com/2011/03/android-battery-goodies.html
In a quick summary, using a Task Killer puts a little program in memory that will routinely scan your phone for running applications and forcefully close them, returning that memory to your phone. The problem is that this is a bad idea and the result of people assuming that multi-tasking in android is the same thing as multi-tasking in a desktop OS.
In it’s best moment, a task killer does absolutely nothing for your phone. It kills apps in memory that the process lifecycle service would have freed the moment it was needed anyway. The power consumed by your memory is constant weather it’s storing a 0 or a 1. So that doesn’t save you in battery at all. Instead, it nearly costs you battery because you just added a regular 15min scheduled task to monitor your apps. Which gives your android system more to do. Not only that but remember normally android stores the “activities” before it kills the app. Something the force close of a task killer will skip. This why you often have to re-login to apps that were force closed by a task killer, as opposed to that illusion of always running when android does the job. What’s funnier is because it registers background tasks with android, they will simply re-launch anyway. Meaning task killer will constantly find itself shutting down the same process over and over again, making the whole thing extra pointless.
Short of it is: 100% of any battery gains are placebo, and better battery gains could be easily achieved by changing the polling cycle of your apps so the android service doesn’t have to launch so many things so regularly. Forcefully closing apps with a task killer does not go to the root of your battery problem, does nothing to help, and simply impacts the user experience by skipping the storage of activities.
Step Ten, Control the polling of e-mail
Again another great write up by Justin.G11 in his blog linked above is Control the polling of e-mail. What we need to do is ratchet down on the polling and and background syncing our phones do to keep our battery life up. Most times, our #1 offender is e-mail, and more times than that, it’s POP3 or IMAP.
Let’s just throw it out there: POP3 is terrible for battery life. We are basically telling our phones to launch an email app every x minutes and sync/download. This means I have to choose between fast polling intervals to get mail instantly (5 minutes or faster) which will drain my battery with regular processes, or save battery with slower polling but mean that I may not get important emails for 30 minutes or more (in the land of instant gratification and IT support … this could be a deal breaker).
Thankfully ActiveSync provides us with an easy way out (ditto for Google Gmail, but that’s not my focus at them moment.)
Systems like Gmail and ActiveSync use a clever mechanism known as long-lived http to do their mail polling. What happens is a client will log into the target server, check for mail, then say “if any mail comes in the next 30 minutes, ping me at this IP” then stop. The actual time is a variable, that the phone cranks up slowly until it’s too long to make through the firewalls in the path of communication, but 30mintues is not uncommon. So after the initial poll the mail program can stop, be removed from memory/CPU, and a simple listener trigger is left on android for 30minutes incase the Exchange Server decides to “wake up” the mail client in order to deliver a new message.
This is really nice because it means I can have a slow 30minutes polling interval and save battery while having the email delivery time of a constant poll. But it means I have to stop using POP3… and start using ActiveSync for work, and perhaps Gmail for home use.
So how do I do that? Well you have Gmail if you have an android phone, and in the Accounts and Imports section of your mail settings you can setup Google to poll your various POP3 services for you. Bingo: best of both worlds. As a final “but I like keeping my messages separate”, you can label each message as it gets delivered to your gmail inbox so you can keep your messages sorted by POP3 account, and even register multiple smtp names for sending. A full solution.
By doing this I can now bring my battery down _significantly_ without sacrificing the ability to get emails at all. Major win in that department. Once I have all my personal POP sources tunneled through Gmail, I can simply rely on ActiveSync for work!
That’s it guys! Hope this post has been helpful in extending your phones battery life.
Here are my phones specs at the time of the testing...
HTC EVO
Model Number: PC36100
Build Number: MIUI-EVO-1.4.15-ENG
Kernel version: 2.6.38.2-SavagedZen-1.1.0-CFS-HAVS-WiMAX-GB+
Battery type: Stock battery that came with device (prior shelf life 4-6 hours of heavy use)
After following all 10 steps I get the following performance from my battery
Heavy Use - 15+ Hours
Only about 4-5 hours phone is idle
30-60 minutes on the phone
Using WiFi at home and work, 3G while in my car or out on the town
20+ text messages
Download 5-10 apps per day
Play games 2-3 hours, maybe more if stuck in a meeting
Listen to music to and from work, about an hour per day.
On the internet most of the day, especially since I like to access facebook and twitter via my phones browser instead of their apps.
Watch 2-3 hours of videos\Youtube
Spend about 1 hour customizing my themes and\or downloading new themes
Finally, did a movie test on Sunday. After a 100% full charge, disconnected and played two movies on the phone. After about 4 hours when the movies were done, battery was still at 52%.
On Average, battery would drain 8-12% per hour of constant continual use when playing games, watching videos or listening to music.
As I said earlier in this post, I want this Best Practices for Battery Management to be a Living Document and I’ll be constantly updating\editing it once new or better practices\apps have been discoved for improving the battery life.
CREDITS
unrevoked.com for the “Painless root and flash”
ClockworkMod for “Rom Manager”
Guys at CyanogenMod for a great ROM
Guys at MIUI for a great ROM
Guys at Savaged-Zen for a great kernel
Taylor Groves, Jeff Knockel and Eric Schulte on their indetail info on kernel differences
-viperboy- for his instruction on how to lower voltages on AOSP kernels
Martino for “VM Heap Tool”
stiffspliff for increasing the MIUI default Heap level to 64
HipKat for the battery conditioning method
NeMa for “Battery Calibration”
Justin.G11 for his blog about Task Killers and Control the polling of e-mail

Define 15+ hours of heavy use. If the phone is on for most of that time and using data, then JD is not going to be doing much is it?
Your tips are well written - a good starting point for someone new.

What bothers me is people say "I got X hours on Y type of usage." Without specifying what battery they're using.
Good read though.

goodboynyc said:
What bothers me is people say "I got X hours on Y type of usage." Without specifying what battery they're using.
Click to expand...
Click to collapse
Obviously, you should that someone is talking about the stock battery unless otherwise noted.

you should reset the title for HTC EVO Best Practices for Battery Management on AOSP ROM's.
instructions are a little biased.

jalai said:
you should reset the title for HTC EVO Best Practices for Battery Management on AOSP ROM's.
instructions are a little biased.
Click to expand...
Click to collapse
maybe he didn't think sense users deserved attention?
Definitely I good starting point. I would recommend tasker over jd, but that's just me
Swyped from my cyanogenized and gingerbreaded EVO

Step 11. Get a kernel with SBC for maximum battery life!
Sent from my EVO using Tapatalk

I found this useful. I knew everything else but it introduced me to the battery calibration app and lowering my voltages.

goodboynyc said:
What bothers me is people say "I got X hours on Y type of usage." Without specifying what battery they're using.
Good read though.
Click to expand...
Click to collapse
would these instructions be applicable to someone using an extended battery? If so, should the battery life be extended in that scenario?

ECrispy said:
Define 15+ hours of heavy use. If the phone is on for most of that time and using data, then JD is not going to be doing much is it?
Click to expand...
Click to collapse
Sorry, I just signed up to this site and this was my first post. I've edited my original post above to reflect what my definition of 15+ hours of heavy use was and give a detailed breakdown.
goodboynyc said:
What bothers me is people say "I got X hours on Y type of usage." Without specifying what battery they're using.
Click to expand...
Click to collapse
I edited my original post to detail that I'm using just the stock battery that came with the phone. I also added the specs of my phone for those that were interested in what ROM and Kernel I was running during these tests after I did all 10 steps.
jalai said:
you should reset the title for HTC EVO Best Practices for Battery Management on AOSP ROM's.
Click to expand...
Click to collapse
Good ideal, I just edited the subject.
twiz0r said:
maybe he didn't think sense users deserved attention?
Click to expand...
Click to collapse
Meant no disrespect to any sense ROM users.
I'll be testing a few sense ROMs next weekend, I'll do a similar post once I've tweaked these steps to fit sense ROMs I'll upload and do some more battery tests.

twiz0r said:
Definitely I good starting point. I would recommend tasker over jd, but that's just me
Click to expand...
Click to collapse
Thanks for the feedback, that's exactly what I'm looking for. As I want to best tweak these Best Practices for Battery Management on AOSP ROMs as much as possible. I'll test out tasker compared to juice defender to see if it'll help my battery life.

another good tip would be to spell AOSP correctly. What the hell is ASOP? a fable?
if you can't remember how to spell it, here's a tip:
Android Open Source Project

deathsled said:
another good tip would be to spell AOSP correctly. What the hell is ASOP? a fable?
if you can't remember how to spell it, here's a tip:
Android Open Source Project
Click to expand...
Click to collapse
LOL.....great tip, that's what I get for trying to edit my posts quickly.

Madvillebuck said:
would these instructions be applicable to someone using an extended battery? If so, should the battery life be extended in that scenario?
Click to expand...
Click to collapse
As long as your running an AOSP ROM like CM7 or MIUI, these instructions would be applicable to anyone, including those using an extended battery.
Since I don't have an extended battery, I'd love to hear feedback on performance from anyone who tried all these steps on an extended battery.

NYG27 said:
Thanks for the feedback, that's exactly what I'm looking for. As I want to best tweak these Best Practices for Battery Management on AOSP ROMs as much as possible. I'll test out tasker compared to juice defender and will try a kernel with SBC to see if they help my battery life.
Click to expand...
Click to collapse
Are you sure you're not already using an SBC kernel? SZ are SBC unless you specifically download the non SBC version. Also, kernel performance is phone dependent. Some people may see better battery life on the stock kernel or Tiamat (AOSP).

Which kernal should i get for improved battery performance? Im on Destroyer v2 mod & battery drains fast...Link would help to kernal!

Maybe I think too logically, but wouldn't all those apps you say to d/l be using battery to run in the background??
No offense, but I get excellent battery life just by keeping data off when I'm not using it.

jstalford said:
Are you sure you're not already using an SBC kernel? SZ are SBC unless you specifically download the non SBC version. Also, kernel performance is phone dependent. Some people may see better battery life on the stock kernel or Tiamat (AOSP).
Click to expand...
Click to collapse
Reason I mentioned “SavagedZen-1.1.0-CFS-HAVS-WiMAX-GB-signed.zip” as the kernel to download, is that I've read about and tested that kernel to be more stable. (Maybe just my personal preference).
By all means test out the BFS kernel and see if you get better performance. There are also none non-SBC kernel but I haven't tested them out yet.
I try to flash a different ROM and kernel each week and test them out. As I do, I'm going to update my original post as much as possible to try to get a true Best Practices for Battery Management for both AOSP and Sense ROMs. So far I've only tested these steps with CM7 and MIUI, which is why I only caution people to test these steps with those ROMs or other aosp roms. The more testing I do with sense roms, I'll update my original post on this thread to be compatible with both aosp and sense roms.

HipKat said:
Maybe I think too logically, but wouldn't all those apps you say to d/l be using battery to run in the background??
Click to expand...
Click to collapse
If you look at Battery Settings\Battery Use, those apps hardly take up 1-2% of my battery running in the background. That's a trade off I'll take for having them improve the overall performance of my battery.
HipKat said:
No offense, but I get excellent battery life just by keeping data off when I'm not using it.
Click to expand...
Click to collapse
No offense taken. Although truth be told about your comment, you have listed in your sig that you use the Sedio Extended battery 3500 mAh. If I had an extended battery and kept data off when I'm not using it, I'd have great battery life also. Although I don't like the look and the bulkier feel of the extended battery (no offense, just my personal preference).
That's why I created this thread to help people extend the life of their stock battery that came with the EVO.

Tiamat>SZ for battery life.

[INVESTIGATION] Battery drain bug in 2.3.4 (JVP build for now)

It seems that our beloved Samsung did it again!
Now we can enjoy a fully functional, long waited, Gingerbread 2.3.4.
Although some sources say that it is only a leak, the JVP build seems to behave really well, according to the reports of many users.
Gingerbread 2.3.4 was build in order to fix some Android bugs and make the interface even faster. We have seen that the second task is a success, the user experience and crazy Quadrant scores being the best witnesses. But what about the first task, are there any android bugs in this build? Maybe we could find out together.
The key purpose of this thread is to find out if that Android OS bug, which made Gingerbread users a hard life, is still present.
You can help this investigation by keeping an eye on the battery stats and reporting the consumption (in percents, of course) of the Android OS. It is even better if you can add some screenshots.
Please don't forget to mention:
- The ROM and kernel you are using.
- Some apps or games you are using (known to fire this bug on previous builds).
- Whether you have autorotation on or off (some users reported they had no drain if kept off on 2.3.3 builds).
- What type of usage you applied to the phone (not really necessary, only you are kind enough).
If you have any kind of suggestion regarding some modifications for this thread you are welcomed to post them. It will helps us become more efficient.
Thank you very much for your effort!
EARLY CONCLUSIONS*:
- Battery life is indeed an improvement on JVP 2.3.4
- The Android OS bug is less aggressive. The reports show a maximum consumption of approx. 20%. We can't say for sure if we can talk about a bug anymore. Anyway, the drainage is not so bad, comparing to 2.3.3 versions.
- The Android System consumption is a bit scary (15-20%) especially after a flash. However, it tends to stabilize in time.
- A clean flash, factory resets, avoiding apps restoration with Titanium or similar, reducing consumers when you don't need them always helps. With or without battery draining bugs.
- JVP is a better alternative for previous versions due to improvements for battery life, speed and stability, even if it's a beta release. So you should go for it, it really is an upgrade!
*The statements above are based on reports and poll results collected until now and they may change. I take no responsibility if you will find those informations incorrect or incomplete. Flash JVP at your own risk, you could loose data or brick your phone, although there aren't reports that say that. Follow the instructions and you should be ok!

is this a new craze insted of train spotting or stamp colecting ....battery watching ....most of us have got a life and have better things to do then watch how much a battery uses ...do what i do charge the phone and enjoy these phones do use loads of battery

Updated with 2.3.4 I9000XXJVP,CSC = I9000OXAJVP and kept it on without sim and without even touching but fully charged. The battery life was just for one and half days.

Android OS running at 3%
using Damian's GTO Alpha kernel for JVP and Brotuck's gingerMod ROM.
Autorotation off.
Consistent q scores in the 2600 range, phone running very smoothly and very fast in daily use (internet, twitter, pics, camera, messaging, phone), 130+ apps installed, no issues. Seems a much better base firmware than any of the 2.3.3 variants.

It's a bit early to investigate this stuff.
Wait for Samsung to release 2.3.4 sources and devs to make some stable kernels based on this.
Until this time many stuff can be broken (well, you're free to beta test though ).

batery is much beter in 2.3.4

no since i flash JVP 2days ago!

anukilimanoor said:
Updated with 2.3.4 I9000XXJVP,CSC = I9000OXAJVP and kept it on without sim and without even touching but fully charged. The battery life was just for one and half days.
Click to expand...
Click to collapse
Keep in mind that after a reflash the battery life will stabilize after a while.
In my opinion, the cell standby may be the cause. If left without SIM, Airplane mode off, your phone will continue to search for signal and this really drains the battery.
If you can make a test again, check the battery usage and post your conclusion.
Thanks for your contribution!

got-petrol said:
is this a new craze insted of train spotting or stamp colecting ....battery watching ....most of us have got a life and have better things to do then watch how much a battery uses ...do what i do charge the phone and enjoy these phones do use loads of battery
Click to expand...
Click to collapse
This kind of activity is normal in community, especially here in XDA.
It will be useful for those kind of people who don't like to experiment in order to find some answers.
We could do like you but, what if we need to charge it again, after 8 hours, without using the phone?
That's why this "new craze" exists, because we want to avoid that kind of problems.

Tatsuya79 said:
It's a bit early to investigate this stuff.
Wait for Samsung to release 2.3.4 sources and devs to make some stable kernels based on this.
Until this time many stuff can be broken (well, you're free to beta test though ).
Click to expand...
Click to collapse
You're right but the 2.3.4 concentrates on fixing bugs, so even in beta stage we should see some changes.
Anyway, the thread is intended to test the firmware regarding this problem, so it can become an indicator for people asking weather they will experience this problem of they can enjoy using their phone without even thinking about this.

lgsshedden said:
Android OS running at 3%
using Damian's GTO Alpha kernel for JVP and Brotuck's gingerMod ROM.
Autorotation off.
Consistent q scores in the 2600 range, phone running very smoothly and very fast in daily use (internet, twitter, pics, camera, messaging, phone), 130+ apps installed, no issues. Seems a much better base firmware than any of the 2.3.3 variants.
Click to expand...
Click to collapse
Thanks for your feedback, happy user!

I must say that 2.3.4 battery is performing better than 2.3.3 so far.
After 11 hours with gps and auto rotate on, battery still have 30% of juice left.
EDT: Attached screenshots
Sent from my GT-I9000 using XDA App

Comming from Froyo JPY to stock deodexed JVP, I have noticed a higher battery drain.
I lost 13% overnight, I had 21% battery use on cell standby (6hours of use). and I noticed something very strange, android system has a 18% battery use with only 5 minutes running, WTF???
I'm using stock deodexed rom from ramad, Dark core kernel and screen off animation. that's all I've changed to this rom, no games, and a few apps like titanium backup and atk.
When I tapped on the android system there was a huge list of included packages, I will list them here, maybe one of them (or all together) is causing that huge battery use:
com.samsung.InputEventApp
Service mode
Software update
Google Backup Transport (actually, I turned off google backup, idk why this is here)
Settings Storage
Mobile tracker
Account and Sync Settings
EncryptApp
Task manager
Error
Perso
com.sec.android.app.lcdtest
VPN Services
Factory Test
wssyncmlnps
PopupuiReceiver
Preconfig
BluetoothTest
Self Test Mode
WlanTest
Status Bar
Settings
Mobile tracker settings
Android System
DRM content
MTP Application
PhoneSetupWizard
Security Storage
Licence Settings
PhoneUtil
Those are all......

gtluis said:
Comming from Froyo JPY to stock deodexed JVP, I have noticed a higher battery drain.
I lost 13% overnight, I had 21% battery use on cell standby (6hours of use). and I noticed something very strange, android system has a 18% battery use with only 5 minutes running, WTF???
I'm using stock deodexed rom from ramad, Dark core kernel and battery off animation. that's all I've changed to this rom, no games, and a few apps like titanium backup and atk.
When I tapped on the android system there was a huge list of included packages, I will list them here, maybe one of them is causing that huge battery use:
com.samsung.InputEventApp
Service mode
Software update
Google Backup Transport (actually, I turned off google backup, idk why this is here)
Settings Storage
Mobile tracker
Account and Sync Settings
EncryptApp
Task manager
Error
Perso
com.sec.android.app.lcdtest
VPN Services
Factory Test
wssyncmlnps
PopupuiReceiver
Preconfig
BluetoothTest
Self Test Mode
WlanTest
Status Bar
Settings
Mobile tracker settings
Android System
DRM content
MTP Application
PhoneSetupWizard
Security Storage
Licence Settings
PhoneUtil
Those are all......
Click to expand...
Click to collapse
It seems that you have a normal consumption on Android System. Also that app list is present on every ROM which has all system apps. On lite ROMs you can get a smaller list, because some of those apps are removed by the chefs.
Maybe your network coverage is not that good
After a flash, the battery needs stabilization, until then it can drain fast. Try to recalibrate it. Please tell me if you need a good guide.
Try a lite ROM. Maybe you will experience a good Android System consumption.
Thanks for the feedback!

Look at the poll results so far 72% say they have no battery issue, so it must be the apps on your phone that are at fault for any unusual battery drain.
Look at your own apps first before you blame the rom, mostly it's not the rom that's at fault.

gtluis said:
I lost 13% overnight, I had 21% battery use on cell standby (6hours of use). and I noticed something very strange, android system has a 18% battery use with only 5 minutes running, WTF???
Click to expand...
Click to collapse
When you're not really using your phone, Android System will have a higher battery use percentage, because nothing else is using battery.
Long periods of idle, you will see higher Cell Stanby and Android System percentages.
The more you use the phone, those percentages will lower.

mammenj said:
I must say that 2.3.4 battery is performing better than 2.3.3 so far.
After 11 hours with gps and auto rotate on, battery still have 30% of juice left.
EDT: Attached screenshots
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Good job! Enjoy your phone!

turn off data connection or wifi when youre not using them
and it will least even longer...

This is what i had with the previous JVO (2.3.3) and not using any task killer anymore. I moderately used the phone, made some calls, wrote some SMS, had blutooth on in the car, listening mp3. Ah, and i set display brightness to "auto" always, i don't use the manual setting with lowest brightness value anymore.
But i also can get the battery down in less than a day...
I'll give the new 2.3.4 a try.

It's funny to see that there is always somebody who needs to torture the board with reinventing the battery wheel. Strange battery behavior usually shows up (and is often dependent on them) in threads with special roms or kernels. The only thing this thread will brings us is more of the same on how to save juice if you don't want to fork for a larger/extra battery.

[Q] Note 4: Performance Issue

Hi Guys,
I am a new Note 4 user, I've had note 2 before. Recently I have used Z3, OneplusOne and S5, which in my opinion other than the S5, the phones were smooth and laggieness was non existence. I have since changed to the Note 4 and immediately I have realised that even in the kitkat (currently running lollipop) that the phone lags when changing between the programs, turning on the camera, or even after a picture has been taken it takes a while to get to respond. Hardwar-wise I believe the Note 4 is very respective and I can only blame this on the software. I have since upgraded to lollipop and I must say the performance is no different than before. Could anyone tell me without rooting and installing a modified rom, is there a way to increase the smoothness of the phone? it is because of the bloatware? how to de-bloat? or is it just how it is?
Thanks
Patrick

the better is a clean installation and after that come back and report any issue's

Thanks vagenrider but this issue was already apparent when I first used the phone right out of the box and noticed the lag.

pplwu said:
Thanks vagenrider but this issue was already apparent when I first used the phone right out of the box and noticed the lag.
Click to expand...
Click to collapse
hi,
I can say this,
that i had my Note4 (N910F rooted, stock Rom.) since October 2014 till now.
Overall i had little or no "lag" of note. (apart from Recent button plus an setting issue.. minor )
Over this period of time, if i found/noticed a bit of "lag" and i found culprit, causing the problem, I would uninstall app,
i also noticed, so far that it has always been a 3rd party (badly coded.. or on lollipop the app was not "playing" nicely.. etc etc)
So overall.... when i was on Android v 4.4.4 or now on Lollipop my device has been working fine.. battery use, been good, very, very smooth
So all i can say, if you have issues it is either you have a faulty device or an app/combination of apps causing lag.or setting issue
I have stated this, in many of my post that i have following devices.. on hand
Note 4, Note 3,Note 8.0 (tab) Note 2 and they all running fine..( 100% satisfaction)
Bottom line
is that i think i am in a good position to state that my Note 4 compares 100%plus, with my Note3(which is a very very, good device, smooth no lag, etc etc)
Above is just my opinion and i hope that you can sort out your device
Good luck

pplwu said:
Hi Guys,
I am a new Note 4 user, I've had note 2 before. Recently I have used Z3, OneplusOne and S5, which in my opinion other than the S5, the phones were smooth and laggieness was non existence. I have since changed to the Note 4 and immediately I have realised that even in the kitkat (currently running lollipop) that the phone lags when changing between the programs, turning on the camera, or even after a picture has been taken it takes a while to get to respond. Hardwar-wise I believe the Note 4 is very respective and I can only blame this on the software. I have since upgraded to lollipop and I must say the performance is no different than before. Could anyone tell me without rooting and installing a modified rom, is there a way to increase the smoothness of the phone? it is because of the bloatware? how to de-bloat? or is it just how it is?
Thanks
Patrick
Click to expand...
Click to collapse
I am having the same issues with my device. I've had it with both lollipop and KK. I've had multiple ROMS (all stock). I've done fresh installs, cleaned cache, disabled apps, and completely run with none of my apps installed. All the same issues, as you've mentioned. I'm thinking of returning my note 4 if they don't fix it by 5.1.1 or August. This device cost way too much for these kinds of issues... :-\

zkyevolved said:
I am having the same issues with my device. I've had it with both lollipop and KK. I've had multiple ROMS (all stock). I've done fresh installs, cleaned cache, disabled apps, and completely run with none of my apps installed. All the same issues, as you've mentioned. I'm thinking of returning my note 4 if they don't fix it by 5.1.1 or August. This device cost way too much for these kinds of issues... :-\
Click to expand...
Click to collapse
pplwu said:
Hi Guys,
I am a new Note 4 user, I've had note 2 before. Recently I have used Z3, OneplusOne and S5, which in my opinion other than the S5, the phones were smooth and laggieness was non existence. I have since changed to the Note 4 and immediately I have realised that even in the kitkat (currently running lollipop) that the phone lags when changing between the programs, turning on the camera, or even after a picture has been taken it takes a while to get to respond. Hardwar-wise I believe the Note 4 is very respective and I can only blame this on the software. I have since upgraded to lollipop and I must say the performance is no different than before. Could anyone tell me without rooting and installing a modified rom, is there a way to increase the smoothness of the phone? it is because of the bloatware? how to de-bloat? or is it just how it is?
Thanks
Patrick
Click to expand...
Click to collapse
About debloating:
Without root you cannot really debloat the rom. You can only try to holding every app you don't need and drag&drop on touch wiz launcher and drag&drop it to "app details". New window with details will be prompted and you can delete or deactivate the app. This is everything you can do on stock to debloat.
About the main problem:
Also here without root and custom rom I could only suggest to try following:
Go to Settings app.
Scroll down to device information.
Tap few times (I think 5 times shoul it be) on build number to activate developer options.
Go back to main screen of settings, scroll down to developer options and open them.
So from here you can try to change following values:
- Force GPU rendering
- Turn off hardware overlays
- lower values for animations (all three) or just set them to zero if you don't need them. That gives really bounce speed (but mainly just for eyes, it doesn't really chages overall performance of device, just little bit maybe)
The nagtive thing of GPU and harware overlay is little bit higher the battery drain then usual.

vbaschen said:
About debloating:
Without root you cannot really debloat the rom. You can only try to holding every app you don't need and drag&drop on touch wiz launcher and drag&drop it to "app details". New window with details will be prompted and you can delete or deactivate the app. This is everything you can do on stock to debloat.
About the main problem:
Also here without root and custom rom I could only suggest to try following:
Go to Settings app.
Scroll down to device information.
Tap few times (I think 5 times shoul it be) on build number to activate developer options.
Go back to main screen of settings, scroll down to developer options and open them.
So from here you can try to change following values:
- Force GPU rendering
- Turn off hardware overlays
- lower values for animations (all three) or just set them to zero if you don't need them. That gives really bounce speed (but mainly just for eyes, it doesn't really chages overall performance of device, just little bit maybe)
The nagtive thing of GPU and harware overlay is little bit higher the battery drain then usual.
Click to expand...
Click to collapse
Thanks for that!! I've just done the above, will use this setting for a while and see how it goes.

Hi Guys, after applying vbaschen's suggestion I believe the phone has improved in terms of window changing and smoothness in operation. Battery discharge hasn't affected me that much given the battery has always lasted an entire day of heavy use and I plug it in everynight. I would recommend this quick mod. Thanks again vbaschen.

vbaschen said:
About debloating:
Without root you cannot really debloat the rom. You can only try to holding every app you don't need and drag&drop on touch wiz launcher and drag&drop it to "app details". New window with details will be prompted and you can delete or deactivate the app. This is everything you can do on stock to debloat.
About the main problem:
Also here without root and custom rom I could only suggest to try following:
Go to Settings app.
Scroll down to device information.
Tap few times (I think 5 times shoul it be) on build number to activate developer options.
Go back to main screen of settings, scroll down to developer options and open them.
So from here you can try to change following values:
- Force GPU rendering
- Turn off hardware overlays
- lower values for animations (all three) or just set them to zero if you don't need them. That gives really bounce speed (but mainly just for eyes, it doesn't really chages overall performance of device, just little bit maybe)
The nagtive thing of GPU and harware overlay is little bit higher the battery drain then usual.
Click to expand...
Click to collapse
Right on. I was going to recommend reducing the animation values as well as that is usually the case. Hope it helped!

Androidious said:
Right on. I was going to recommend reducing the animation values as well as that is usually the case. Hope it helped!
Click to expand...
Click to collapse
I went for a completely different solution: the Note 4's Snapdragon cpu has the bad habit of heating up very quickly. Two or three minutes of heavy usage (gaming/emulation, or worst: piles of file operations, e.g. media scanner) make it shoot up to 85° C. To prevent serious damage, the cpu is then automatically scaled down to extremely low values, which results in abysmal performance. When I first unboxed my N910F and inserted my old sdcard, the media scanner went haywire because my sdcard was faulty (works alright in my old Note 2, but the Note 4 is picky). The phone quickly got too hot to even touch, ran sluggish as hell (AnTuTu scores between 24000 and 29000), then shut itself down. :crying:
After I had replaced the sdcard, things got better, but only when I didn't put too much load on the phone: 52000 AnTuTu points in the morning (first thing to do with the cold phone), but getting worse steadily until I couldn't score more than 43000 points.
Now, after a lot of fiddling and tweaking (Kitkat, Lollipop, Stock, Custom, CM 12.1), I finally settled for (Lollipop) Emotion Revolution R8 ROM along with the Emotion nightly kernel (r17) and (most important) Synapse kernel tweaker. Instead of overclocking the blasted thing even more, I actually downclocked it one step (2572,8 MHz). The result: a rock stable phone that actually runs way better than with the higher (stock) clock rate. The cpu hardly ever scratches 70° C, and usually stays around 65° C even when I run demanding apps like PPSSPP, Dosbox, or Real Racing 3 (don't like that one, but it beats the s**t out of the cpu - 85° with stock cpu clock!). AnTuTu scores reach about 51500 - almost as much as with stock clock rate - but several times in a row now, with no performance hit. So, even though the peak performance may be one or two percent lower, I can run my phone for hours without any performance drops. Oh, and it's good for battery life, of course. :good:
So, if you're rooted, you may want to give it a shot. :fingers-crossed:

[HOW-TO][NEWBIE GUIDE] Optimize & proper set up your Galaxy S6 Edge (stock firmware)

[HOW-TO][NEWBIE GUIDE] Optimize & proper set up your Galaxy S6 Edge (stock firmware)
As I've read across this forum and on several specific threads related to usage, battery life and so on, as well as discussing with some of my friends having a S6 or S6 Edge, I realized that most of the people don't really know how to properly set up their phones or how to use them efficiently.
OK, I get it, this is a fancy phone, not every owner is a developer or tech guy so it might be that many choose it based on the looks and don't really know how to optimize it...then they start complaining about different things like lag or battery drain not knowing that most of the problems are caused by miss-usage or improper setup. Of course there are bugs too, nothing is perfect. Of course there are many firmwares available and some are market or carrier dependent so some features or settings might be missing from some of them or even work differently.
What I will try here is to provide some guidelines and tips for setting up various things on the phone in order to maximize it's battery life and for a better usage. I will also make some recommendations based on my experience, tests and usage that might not apply to everyone. Use common sense and logic to apply similar settings in your particular case. Don't come screaming that you made that or that and now something is not working.
And YES, I know there are similar guides like this posted over the Internet and I'll probably make similar recommendations here too but I couldn't find such a guide here on XDA that is particular to this phone (if there is a better one than you might as well ignore mine).
All these things I'll describe below are applicable to any STOCK, NON-ROOTED 5.1.1 firmware and won't break warranty or your phone.
Now that was a long (and maybe unneeded introduction) but I thought to write this for everyone...let's start.
Model No.: SM-G925F
Android: 5.1.1 r2 (LMY47X)
Baseband: G925FXXU2QOI7
Kernel: 3.10.61-5672012
Build date: Fri Sept 4 2015
Carrier: Orange RO
DISPLAY
First I would like to say some words about the display. We have a great display, high resolution and it is most likely the biggest battery drain factor. There are two major things about it that you should keep in mind and will help you to get a better battery:
1. It's AMOLED...that means that the black pixels on it will consume no power because are not lit. Studies showed that even if not completely black, AMOLED displays use less energy if the displayed picture is darker compared to a lighter one.
2. The brightness level. Most people use it on "auto" or high level settings and this will be a major drain factor.
You can drastically lower the battery drain caused by your screen by selecting as much as possible dark (black) backgrounds and/or themes. There are some nice ones available in the Theme Store (my favorite is the Dalkomm Coffee Theme), that make most screens and menus dark/black. Also choosing a dark wallpaper for lockscreen/homescreens will help.
Don't use screen brightness at maximum...never. You don't need that in 99% of the cases. Also you won't probably need the automatic setting either since most of the people are spending most of the time indoors (either at work or home). A low manual setting will be fine most of the time, I have it set up at about 20% and only need a brighter one when going out. At that time I just tap on "auto" and it'll increase based on ambient light level. So you don't even need to tweak it alot every time. Find a low manual setting that's fine for your eyes and just tap on "auto" when you go out in sunlight.
CONNECTIVITY
Another battery drain factor is your multiple connection/radios features. In most cases you use just several: Mobile Data, WiFi, GPS/location and BT (when applicable). That means you should turn off all the others you don't use...NFC or BT (when not connected to a headset or car-kit or not listening to music). I don't listen to music and don't have a BT headset so I mostly not using BT (just when I'm in my car) and almost never use NFC so I have both disabled and I enable them only when needed via the Quick Settings.
WiFi
WiFi should also be properly setup otherwise it'll have impact on battery. It was incorrectly assumed or considered that keeping WiFi on all the time will drain battery faster. That was proven in different tests that's not true and in fact keeping WiFi on all the time won't make a big difference and in some cases was even better than to turn it off/on. I think is something similar with the car engines that suck more fuel when started that when running at idle. The major power drain is not when WiFi is running while is not connected to any network, but when the WiFi radio is powered up. When is on and not connected, it's going into a lower power state so the battery consumption is negligible.
I had a case with one of my friends that had WiFi setup to turn off when display was off...wrong choice, he got about 30% battery drain overnight because instead of having it connected to his home WiFi, the phone was using his 4G/LTE connection to make all the background sync/updates. That was eating his battery and also his data plan. After setting WiFi to "always" his overnight drain lowered to as little as 2-3%.
In some regions/carriers there are 2 other settings that were proven to help battery life: WiFi calling and VoLTE. I don't have either of them but based on different articles and what people say, they surely help with that so don't forget to turn them off if you don't use these features.
You might also want to try turning off "Always allows scanning" and "Smart network switch". I have the second turned off but I keep on the first one. Basically the first option tell the Location service to use WiFi for locating the device even if WiFi is switched off (by the on/off switch) so that means the radio is active. Second option should make you switch faster from WiFi to mobile data in case the WiFi signal is not strong enough or fluctuating. In my country there are plenty of WiFi hot-spots and they have mostly good connections so I don't use this feature.
GPS
Well here the opinions are split but I am currently having it ON all the time and Location Service is set to "high accuracy". I personally haven't noticed such a major difference with or without it so I preferred to let it on as it is used by many apps or services. You can try to set Location to "wifi and cell only" but don't think that will bring you a major benefit.
RUNNING APPS/PROCESSES
Well this is an important one. I've initially started to turn off/disable/uninstall everything I don't need or use. This can be done mostly from the Settings - Applications - Application Manager or if you want to go further, you can install Package Disabler Pro from PlayStore, about which I'll detail later.
Now why we should do that? There are lots of apps, processes and background services running on our devices that take care about all the things we do on the device. The problem is that ALL are using resources: processor time, memory, space and so on. In the end these are translated for a user in LAG or battery drain. Of course we cannot kill everything and I learned long time ago that installing Task or memory managers on Android it's the worst thing you can do. Android it's smart enough to take care better about it's resources and processes (at least to a certain point) and keep killing a certain process won't give you more battery life but will eat more of it in the end,
What I wanted to say is you shouldn't start disabling, killing or blocking everything cause you might end up with an unstable or not properly working phone (case in which only a factory reset might help). First of all look at the ALL tab in Application Manager and try to identify what you don't need or use. For example I'm certainly not using some things like: music, books, news feeds, Samsung's keyboard (I use SwiftKey), the TouchWiz launcher (I use Nova), health services or whatever, S-Voice, S-Health, S-Finder, I don't have any smartwatches so I don't use any Gear processes, fancy device wake-up functions (like wave gestures) or animated wallpapers either.
So after all considerations above, you decided that you can safely disable some apps/processes. All good but you'll quickly learn that some of them cannot be disabled via Application Manager (the "disable" button is grayed out). Now what? Well here comes handy that Package Disabler Pro that I've told you about in the beginning. That app is able to disable ANY apps/processes on your phone, including those that are protected and cannot be disabled via the normal way (and yes it can do that without being rooted). The downside of it is that you must be careful what you choose to disable not to have something that is needed for the normal functionality or the apps you're currently using. The app has also a backup/restore function (via an xml file) for saving the list with apps you have disabled and easily import them back after a factory reset for ex. I've added to this thread my list of disabled apps as it is exported by the application (just unzip and copy the file on the root of your internal memory and it can then be imported in the Package Disabler app)
Another important thing is WHAT apps you're using. I know that socializing and social networking are some of today's most trendy things but keep in mind that some of the apps used for that are not so well made. An example could be the Facebook app/messenger which are reported to drain alot of battery. RSS feeds, news feeds, multiple weather apps or widgets, all contribute to battery drain and lag. Don't install several apps/widgets for the same purpose (like several calendar apps or weather apps). Each will take resources and won't have an added value. Want to use another weather app/widget than the one coming with the phone? Fine, install it...but don't forget to uninstall/disable the built in one or others that do the same thing. Same goes for keyboard for ex; I use SwiftKey for years and got used with it. For me it's better than any keyboard that Samsung might put on the device, therefore I've disabled the standard Samsung keyboard. I also don't like TouchWiz launcher and use Nova that offers me much more flexibility so...I've disabled both the "easy" and "regular" TouchWiz launchers. I went to the point that I've even disabled the different embedded font types, you have 5 of them and I doubt someone uses more than one at a time.
So as you all can see it's not only a matter of setup but also a matter of usage. When you have a device you have to use it properly otherwise it'll not perform as you expect. Imagine a car that has a manufacturer fuel consumption value of 5.5 liters/100 Km....that's under certain conditions not on ANY type of driving. Fly with 200+ km/hr on a highway and I'll guarantee you won't have 5.5 liters/100 km consumption. That doesn't mean the manufacturer has lied or mislead you. Same goes with a phone, if you don't know how to use it and optimize it, you'll have a bad experience.
I work in the IT industry for years and I mostly laugh when I hear someone advising somebody to reinstall the operating system to solve a problem. Same goes for "factory reset" for a phone. Yes, this method works some times but that won't solve the root cause of an issues if you're using it the same way. After several days it'll perform as bad as before and you'll just say that "factory reset" did nothing. Of course it didn't...YOU have to do something different, not the phone.
Now I apologize for the long post and I do hope that at least some will learn to better manage their devices and to understand what they're doing not just running certain commands or procedures blind. Both S6 and S6e are great devices but we should learn how to properly use them in order to benefit the most from them...otherwise we just come here asking for help or mumbling about what crap devices they are.

Thank you, I will check to see if I get an improvement on the standby battery drain.

Your part about not setting the screen to Auto is flawed. You mention that we are mostly indoors, and you don't need a brighter screen for that. Auto mode also knows that and sets the brightness lower. It already does automatically what you do manually.

Tnx. And yes....keeping screen at 20% brightness and just switching to auto when in outdoors works great for the battery life.

ArmedandDangerous said:
Your part about not setting the screen to Auto is flawed. You mention that we are mostly indoors, and you don't need a brighter screen for that. Auto mode also knows that and sets the brightness lower. It already does automatically what you do manually.
Click to expand...
Click to collapse
Not quite, I've tested it. If you're on "auto" and use a lower setting on the slidebar, in a dark room the screen is too dark, you'll have to turn off "auto" and the manual brighteness set on the same level will be much higher than on auto.
Now if you have such good eyes and you're able to use "auto" in all cases with the slider at 20% that's good for you...unfortunately I am not so that's why I use it as I've described. The point is that "auto" mode consumes MORE battery regardless of how it's set, than a lower 'manual' mode. So I preffer to have it like this than to use auto all the time.

Thanks for the awesome guide. I'll start disabling some useless processes and see how my battery life is working. Anyway without much editing the battery of S6Edge is pretty good. I can use it a whole day and still 19% remaining. As a comparison I wasn't able to do it with my S3 having to recharge it 2 or even 3 times at day.
Again, thanks for the guide!
Enviado desde mi SGS6e mediante Tapatalk

G2 D800 Lagging, running absurdly slow?

Hi, so I've had my G2 D800 model for a while (about a year or two), and for the most part, it's been an excellent phone despite being 3 years old now. Never had any slowdown problems, and it's always performed well in games and in general.
But just recently, about a week ago, it just started lagging out and being very, very slow.
For example, if I'm watching a YT video through the app, if I rotate the screen, it takes maybe 5-8 seconds to actually rotate. Also, in a lot of circumstances where the keyboard has to pop up, it just freezes the app until the keyboard pops up maybe 10 seconds later.
It's also just laggier in general in most apps, scrolling through FB or Twitter freezes nearly every second when I'm scrolling. It's generally unresponsive and sometimes just freezes outright. It also acts this way on the homescreen, and in most everything else.
The most annoying part, however, is that sometimes the devices just doesn't turn on for sometimes up to 15 seconds after pushing the power button (and it usually just refuses to turn on when using my knock code).
The odd part, however, is that once it's actually in something like a game, it performs perfectly fine.
I've played a number of Cardboard games, as well as games like Nova 3, and it performs perfectly.
I've also ran multiple benchmarks (Geekbench, 3DMark, etc), and it scores around where it should.
Info about the device:
LG G2 D800
Stock Lollipop 5.0.2
Software Ver. D80030f
Kernel Ver. 3.4.0
Rooted
TWRP Recovery installed
XPosed Lollipop installed
G3 Tweaks installed, a number of tweaks applied
Everything else is stock (homescreen, etc)
What I've tried/checked:
Checked memory usage during "lag sessions", rarely dips below 300mb free
Changing minfree values through Rom Toolbox (tried every preset, as well as setting everything to the max to free as much as possible)
Rebooting (affects nothing)
Checked CPU speed with Rom Toolbox (is at max, and does achieve the max speed of 2265 MHz. Setting it to performance mode/setting the min speed to be 2265 MHz has no effect, but reduces battery time)
Changed default cache sizr (tried every preset from 128kb to 4096kb. With multiple benchmarks, the optimal value for r/w bounced between 512kb and 4096kb, currently on 4096)
Things I have not tried (that I am aware would possibly have an affect):
Changing anything in the kernel tweaks/build.prop
Completely wiping, reformatting, and reinstalling (I really would rather avoid this if possible, as it would take a while to get everything back to what it is now, and it was a pain to upgrade to Lollipop in the first place)
I am unaware of anything else I could try to fix it, which is why I'm here
So, does anyone know of any other solutions or things to try? This has made my phone very unreliable, even for phone calls and messages, which is a problem.
Thank you for your time and help!

Jtpetch said:
Hi, so I've had my G2 D800 model for a while (about a year or two), and for the most part, it's been an excellent phone despite being 3 years old now. Never had any slowdown problems, and it's always performed well in games and in general.
Click to expand...
Click to collapse
Hi,
First thing i need you to try out is this custom kernel : http://forum.xda-developers.com/lg-g2/development/lp-5-0-2-kernel-3-4-107-dorimanx-1-0-lg-t3102512
Then install greenify, and hibernate all the unnecessary apps.
This should solve the issue.

iubjaved said:
Hi,
First thing i need you to try out is this custom kernel : http://forum.xda-developers.com/lg-g2/development/lp-5-0-2-kernel-3-4-107-dorimanx-1-0-lg-t3102512
Then install greenify, and hibernate all the unnecessary apps.
This should solve the issue.
Click to expand...
Click to collapse
Thanks for the quick reply!
I'll try out greenify, though there aren't many unnecessary apps running (i uninstalled all the bloatware first thing, when I rooted).
And about the custom kernel, it's something I've never tried, so I have a couple questions.
Will it wipe my device, or break TWRP, root, or Xposed? (Sorry, didn't see the answer on that forum)
Will a TWRP backup I make be able to fully restore my device to it's current condition?
Is everything that is supported on my device be supported with that kernel? (Apps, etc. Don't know a whole lot about how kernels work, so I don't know)
Thank you!

Jtpetch said:
Thanks for the quick reply!
I'll try out greenify, though there aren't many unnecessary apps running (i uninstalled all the bloatware first thing, when I rooted).
And about the custom kernel, it's something I've never tried, so I have a couple questions.
Will it wipe my device, or break TWRP, root, or Xposed? (Sorry, didn't see the answer on that forum)
Will a TWRP backup I make be able to fully restore my device to it's current condition?
Is everything that is supported on my device be supported with that kernel? (Apps, etc. Don't know a whole lot about how kernels work, so I don't know)
Thank you!
Click to expand...
Click to collapse
Hi,
Even you uninstalled bloatware, the apps you use daily could be running in background and taking all those rams. So whenever you play a game or dont use a certain app, just go to greenify and hibernate. Since you have xposed installed, you can do more than that such as u can stop sync , etc.
About the kernel, it has a ram management settings and cron task.
Ram management dont need to be altered. It has some preset profile so if you seek performance, just choose performance or if u need battery , select battery profile etc.
Cron task is useful because it will do alot of things automatically. For example, it will release ram at certain amount of time from the apps , it will restart google play service since that could be an issue , etc.
All you need to do is take a nandroid backup just to be safe. Then download Dorimanx Ota from playstore and it will detect ur device and show u which version of kernel is available. Then download that, go to recovery, flash it, and you will see three app installed : Synapse -- will give you all the details of ur setup including cpu speed, temp etc for monitoring purposes
Dorimanx settings - this is the main settings of the kernel. You will see a P icon on top, tap it and choose your desired profile.
Color management : It is as the title says, just leave it be.
Then use your device, check your ram and report back. Hopefully it will resolve your issue.

Wow. Dorimanx did a lot more than I was expecting.
Downloaded the app, downloaded the kernel, flashed it no problem, went through and checked out synapse.
Went into the Dorimanx settings, and set it to the "Performance" profile.
Immediate improvement.
The whole phone seems a lot more snappy, and I switched back and forth between a 1080p60 YT video, facebook, and twitter with absolutely no problem.
Free memory when idle (no apps open) stays around 1gb; it used to be about 500mb before.
Tested a few games for the heck of it, and it actually seems to have improved game performance somehow. (It seems to have overclocked my CPU to 2.5ghz, though, so that makes sense.)
Temps stayed at around 58-60c while running a few Cardboard apps, so it seems fine.
Thanks for the help iubjaved! This has fixed my issue and then some! Ah, the wonders of the Android dev community.

Jtpetch said:
Wow. Dorimanx did a lot more than I was expecting.
Downloaded the app, downloaded the kernel, flashed it no problem, went through and checked out synapse.
Went into the Dorimanx settings, and set it to the "Performance" profile.
Immediate improvement.
The whole phone seems a lot more snappy, and I switched back and forth between a 1080p60 YT video, facebook, and twitter with absolutely no problem.
Free memory when idle (no apps open) stays around 1gb; it used to be about 500mb before.
Tested a few games for the heck of it, and it actually seems to have improved game performance somehow. (It seems to have overclocked my CPU to 2.5ghz, though, so that makes sense.)
Temps stayed at around 58-60c while running a few Cardboard apps, so it seems fine.
Thanks for the help iubjaved! This has fixed my issue and then some! Ah, the wonders of the Android dev community.
Click to expand...
Click to collapse
No worries, happy to help. I gave you advice based upon my experience using all those .
Feel free to post in XDA if you need any sort of help, you will find many that will give you insights and stuff to solve your issue.
GL :good: