Hey, I'm curious to see whether there is something that I could do to my BUZZ to gain more battery it's currently got SPLASHMOD rom, and clockwork mod... I'm just unsure because it was fine for ages with the CyanogenMod but then deteriorated for some strange reason I hadn't downloaded something I shouldn't neither use something that would drain the battery so I'm pretty confused I'd be grateful if there was an explanation I'm pretty much a noob at this type of stuff so go easy on me.
Thank you for your time
Just decrease the CPU frequency.. If u dint set the CPU, then go for "Atutu battery saver" App.., it helps you to get battery life for whole day with experiencing all the stuff, For me normally batter drains in 9 or 10 hours normally, but after installing this app, it helps me to withstand 40+ hours for my normal use.. It just sets your CPU frequency low and optimises your mobile phone so that no resource will be using battery.... have a try..
try decrease the cpu and set sheduler on powersave
Like the guy above me try decrease your cpu and set your sheduler on powersaver. It works good for me. And you can also try to use other roms. Some roms just use more and really I have no idea why
I will yell you why.......
Cos some roms have so much sh#t running in the background that most users are unaware of,also app after app to do this and to do that will not help in the slightest.
Turn your screen brightness down,stop overclocking,manage your lmk and ooms,sort your syncing out,stop adding placebo scripts etc etc I'm bored now so I hope you get my point.
UTID
i am using splashmod v1.8 and im getting very good battery life after calibration
i used to use CM7 and get 20 hours battery life on moderate use..
with splashmod it goes upto 40 hours....with 2g networks, wifi sometimes and music ... + splashmod v1.8 is very fast!
Just got some questions
How are you guys overclocking?
How fast is your top speed?
Is it stable?
Is battery life affected? If so, how?
Anything else you noticed after overclocking?
ultimatebuster said:
Just got some questions
How are you guys overclocking?
How fast is your top speed?
Is it stable?
Is battery life affected? If so, how?
Anything else you noticed after overclocking?
Click to expand...
Click to collapse
all phones overclock different.
so to answer your questions (in order)
1. i use system tuner to overclock to 1.19ghz
2. 1.26ghz but my old evo toped at 1.19
3. it is stable for me at 1.19
4. battery life isn't affected all to much from the stock speed it drains about the same rate. (998mhz)
5. all i noticed was stuff was a little faster/smoother on sense roms.
to find your top speed just get system tuner and set the governor to performance (this pins your cpu at the top speed) then just keep increasing the max speed up 1 increment at a time until it freezes and reboots (you may have to pull the battery) so if it freezes at 1.22ghz then your top is 1.19 (1 step below the crashing point) and for stability i would stay at 1.15ghz (step below top) because when you near the threshold where it freezes/reboots it tends to get a little laggy and jumpy.
then when you find your stable point take your governor off of performance and instead put it to something else like interactive or smartass or whatever your governor of choice is on the kernel you are using at the time.
hope this helped
I AM NOT RESPONSIBLE FOR ANY NEGATIVE IMPACTS OR CONSEQUENCES ON YOUR PHONE IF YOU SO CHOOSE TO USE THESE TIPS.
I've created a couple threads on the ZTE U950 and LG G2, and one problem is the battery life. The battery cannot come out of these devices and thus we cannot combat this with a bulkier, beefier replacement for heavy usage. Charging constantly is something I try to avoid, so these are a few simple tips that can help optimize your battery life (and that APPLY to ANY PHONE):
TIPS
BATTERY
1a) Buy and download CPU Sleeper (root required). There are two versions, one for dual-cores, and the other for quad-cores. Essentially, when a phone is "sleeping", it is actually still running all its cores, helping drain battery faster. This app turns off all but one core when it is "sleeping" so that your battery is not drained nearly as fast.
BATTERY
1b) To take this step a bit further you can download a free app called Multicore CPU Control. In this app you can control your other cores. You can setup profiles to turn on or off cores, and setup each core with different governors. On my LG G2, I setup a profile to only have one core running at 960MHz (2.2GHz originally) after using the steps from below. If you plan to only run one core, then you do not need to buy CPU Sleeper.
NOTES ON 1b: Multicore CPU Control is the name when installed, it is called CPU Performance Control Free on the Google Play Store (either name will work on Google Play). The program needs to be turned on after each boot. When first setting up a profile save it and edit it in order to manipulate the other cores available. The app does not always apply a profile even if it has already been selected. To turn on a profile, click on the profile desired and go to the CPU Monitor tab to check if it has been applied. If not, repeat the process until it does (it usually takes me about 3 times at most).
BATTERY/RAM
2) Download Greenify (root required), a great free app! Sometimes a user does not have a ROM with a kill all button, so pesky apps just stay on without consent. This app allows a user to turn off any app that may want to run in your background, and even shows you which apps are currently running. Apps like Facebook, Talkatone, etc. can all be stopped even if your "task killer" supposedly took care of them.
BATTERY
3a) Wakelock Detector-Save Battery is a free app that checks for apps that continue to work while the phone is "asleep". While Greenify will display the most troublesome apps, this app will help discover any other apps that are running without consent.
BATTERY/RAM
3b) If Greenify does not show the apps discovered in Wakelock Detector-Save Battery, then download Disable Services (root required). This free app allows a user to disable an entire service, or just parts of a service that are bothersome. Click on a service/app to find out what other services accompany it. Read the accompanying services and discern whether or not the service is needed. A good place to start in this app is to check any service/app that has a blue number next to it.
EXAMPLE 3b: I use the Outlook app a lot, but sometimes it gets annoying with updates for insignificant email. I can open Wakelock Detector-Save Battery and click the Outlook app. I turn off "AppWidgetUpdateService" to disable Outlook email updates. Not all services have obvious names, so be careful on system apps if performing trial-and-error.
BATTERY/RAM
3) Buy and download BetterBatteryStats (CPU Spy Reborn/Plus is FREE and only shows CPU states). This app tells me what CPU States are used the most often and is what I download first before my next step. A user can also determine battery-draining apps and turn those off. If turning off those apps is not possible through Settings>Apps just Greenify them!
BATTERY
4) Underclocking. This is an amazing step for saving battery! If you have ran BetterBatteryStats for at least a day, this will come in handy and is highly recommended. You can use numerous programs like SetCPU or Voltage Control to set the clock of the CPU. The key is to find a point that will still be responsive, yet lower than the maximum.
EXAMPLE 4: For this example I will be using my ZTE U950 and Voltage Control. According to BetterBatteryStats, my most used clock was at 1.2GHz and 860MHz. I left my minimum clock at the lowest possible setting, while my maximum clock I changed to 860MHz. I ran this for a few days and saw a noticeable difference in battery life. Another important part to this if choosing the right I/O Scheduler and CPU Governor. I found the default I/O Schedule ("cfq") to perform the best, despite "noop" being good for sluggish memory. "Powersave" is a good Governor at stock CPU speeds, but it will not get a user the savings of power that a step like this will. I tested with this Governor with this step and got horrible reaction times and would often need to restart the phone. The best results I have are with "ondemand" and "interactive". I am currently using "interactive" with a maximum clock of 475MHz! I arrived at that number after checking my BetterBatteryStats while running at 860MHz and found that to be the next most used clock. Now my battery is lasting about twice as long as it normally did! My phone's response time is a bit slower at this low clock speed, but that can combated...
BATTERY/RAM/SPEED
4b) (IF YOU HAVE INIT.D SKIP TO STEP 4c) My LG G2 is underclocked to 960MHz, as noted in step 1b. I am saving quite a bit of battery, but the UI response can lag a lot at times. The use of boot scripts can be helpful to compensate for this. However, my LG G2 does not have init.d support. There are numerous threads that explain how to get init.d support for a lacking Android phone. The simplest method is to install an app from Google Play. I use one called Init.d-Installer just because it forces the phone to reboot once it has installed; others do not seem to do anything to inform a user if they have received init.d support
BATTERY/RAM/SPEED
4c) Download a script called V6 SuperCharger. The thread may seem daunting, but it is fairly easy to install. Download the newest PDF and change it to TXT. Ensure you have init.d support, BusyBox installed (also in the thread if needed), and SuperSU. Run the script in a free app like SManager with SU permissions and follow the instructions. This script gives the ability to enhance speed and power. I install this in order to ensure my UI stays responsive, and LG G2 runs almost at stock speeds (alongside all my other enhancements)!
BATTERY
5) Undervolting (root required/custom kernel required). This is also a great way to save battery. I decrease the voltage in steps of 25 and test from there. If I find no quirks, I leave it. If I find sluggishness or have random phone reboots, I increase by increments of 25 (or 12.5) until I find something stable.
Most phones will not allow undervolting without a custom kernel. To see whether a phone can undervolt or not download, Sytem Tuner. There is a free and paid (Pro) version of this app, but the free one should be sufficient for what we want to do. After installing, open the app and click on the Voltage settings tile on the left-lower side of the screen. All the phone's CPU MHz steps and the amount of voltage applied to each step can be viewed. At the bottom of the screen are buttons to increase or decrease voltage in 12.5 increments (which will apply to all steps). If the -12.5 button is clicked and the values of all the steps drop, then a phone can undervolt. Additionally, System Tuner allows a phone to manually apply undervolting to each step if wanted.
To test undervolting, just push the decrease button until the phone freezes up. There is no harm to your phone or CPU as neither are being overpowered (just the opposite), and a reboot after freezing will reset the phone to default voltage settings. A - 75MHz drop is normal for a phone while remaining stable; and in a lot of cases -100MHz is achievable.
NOTE: Tips #4 & #5 also can be applied to GPUs.
NOTE 2: One thing that should be mentioned is to be careful about putting more than one app that controls CPU clocks. They can read differently and trump the other when used in combination. Instead, install and use one at a time to get more accurate readings. The same should apply to undervolting apps.
BATTERY/RAM
6) A user can change the Dalvik cache a bit to see if that helps optimize RAM, and possibly battery. I did quite a few tests for these to see how they performed. I think the only reason I noticed any changes immediately is because of how far underclocked my CPU is. Anyways, the best results I was able to get with my ZTE U950 was as follows:
124m - dalvik.vm.heapsize (2nd one, not 1st)
8m - dalvik.vm.heapstartsize
For other phones, these are the items to trial-and-error with:
davilk.vm.heapsize (may be more than one at different values)
davilk.vm.heapstartsize
davilk.vm.heapgrowthlimit (may be more than one at different values)
A user can change these settings by downloading an app like Build.Prop from Google Play. I did notice my battery seemed to drain slower with these changed. The RAM was the best optimized for the self-made tests I performed and was nearly the best in all the tests I had ran. A user may or may not notice any differences unless they multitask a lot.
BATTERY/RAM/SPEED
7) All other well-known methods apply as well:
A. Battery Saver apps/settings
B. Battery Calibration apps
C. Refrain from the use of widgets
D. Automatic Brightness apps/settings
E. Small Screen Times before Screen Sleep
F. Turn Off WiFi and/or Data when not needed
G. Task Killers apps/settings
I'm trying to find out whether enabling Force GPU Rendering in the Dev Options is worth doing to improve battery?
I've read everywhere mixed opinions, that it works or it doesn't work or it 'should' work in theory but am unsure - mainly because it's set to off by default..
Currently running Resurrection Remix Marshmallow and the battery life is randomly good and [email protected]
It will increase usage, the stress of graphics is being handled by both CPU and GPU to save battery. Turning that setting on will put a big burden the GPU itself cant handle too well. Results will be faster performance yet glitches and stuff like overheat and battery drain may happen.
*I no longer have this phone so these values and builds will not be updated if you would like to add new values for this phone or add tweaks to existing builds then feel free to post them on this thread.
*This requires root
I decided to make this thread to share with you guys a tweak that I found that really helped my battery life. I was never able to get more than 3hrs of screen on time on my phone or get decent standby times on lollipop like I did when I was on marshmallow but I may have found a solution. I stumbled on this thread: http://forum.xda-developers.com/nexus-5x/general/guide-advanced-interactive-governor-t3269557 by soniCron give the guy a thanks while you're over there. This guide is for CPU settings to increase battery life and performance. I saw that it was for the Nexus 5x and because the g4 and 5x have the same CPU I decided to give it a shot. I never noticed much performance improvements but I did notice a big battery improvement like I said before. There are many different flavors of tweaks to try and I ended up going with GhostPepper and then tweaking it to my liking.
Here are my settings for the G4 based on GhostPepper
https://docs.google.com/spreadsheets/d/1Yn-qtExspkzINkhtjHBhQyrbtSdMLH9ls4booeqsfh4/edit?usp=sharing
* 8/14/16 If you used the settings from the beta build Turtle or modded GhostPepper check to make sure your settings are up to date. I just changed some target load numbers slightly and fixed an error with the values for above_hispeed_delay. I also fixed an error with a value for the modded GhostPepper settings.
*8/15/16 Slight changes to beta settings to increase smoothness and battery life slightly
*8/17/16 Small change to beta settings to increase smoothness more and changed development status of Turtle to stable beta meaning you can probably use it without worrying about battery drain or slow downs though it does need more testing to move it to daily use
After changing these values with some type of kernel tweaking app I used kernel adiutor, make sure all CPU boosting settings like touch boost or input interval are off or at 0
After applying these settings you should see noticeable improvements in battery life
If you find any better settings add them to the thread.
*I am not responsible if your phone dies, bootloops, bricks, or causes the world to explode.
Unfortunately, this requires root, so no-go on MM.
konradsa said:
Unfortunately, this requires root, so no-go on MM.
Click to expand...
Click to collapse
I meant to put that in the post updating it now.
I found simply changing my governor to interactive greatly increased my battery life. I am going to try this and see what I get. I'll post results.
trxrider31 said:
I found simply changing my governor to interactive greatly increased my battery life. I am going to try this and see what I get. I'll post results.
Click to expand...
Click to collapse
OK great this uses the interactive governor.
New Beta Settings
I have updated the main post with a link to a list of settings one of them is the one that was on there before and the other is one I am working on. The beta I just added seems fairly decent from my testing though this is my first time trying to make my own The small core settings are ones that I did and the Big core settings are slightly tweaked GhostPepper settings. This one seems smooth from my testing maybe not as smooth as the first one I added but it does seem to have a little better battery life when doing light gaming. If your adventurous go for it and report any issues and the battery life you are getting. I also turned all thermal settings off like Core control, VDD, and Temp throttle. It didn't have any affect on my temps if anything they went down a little maybe 1 or 2 degrees but did seem to help smoothness and making sure the governor settings acted right on both profiles.
*I am not responsible if your phone dies, bootloops, bricks, or causes the world to explode.
*If you used the settings from the beta build Turtle or modded GhostPepper check to make sure your settings are up to date. I just changed some target load numbers slightly and fixed an error with the values for above_hispeed_delay. I also fixed an error with a value for the modded GhostPepper settings.
Just wanted to post an update on the battery life I am getting with the beta settings. I managed to get almost 5hrs of screen on time with the Turtle settings beating my previous longest screen on time from the images in the first post. I managed to do this with even more demanding tasks. In the first post the battery times are with mainly web browsing this time I was mainly watching Netflix and YouTube for about 3hrs worth of my screen on time. My brightness was also 10% higher than the first time. I also did a standby test and managed to only drain 3% overnight and it said I would get 139 hrs of standby time which I think is insanely good.
Battery life test
I just ran the Geekbench 3 battery test and managed to get 5 hrs 45 min and a score of 3456 on the beta settings. I managed to beat the G4 battery time by 50min and this was with 30% brightness and Bluetooth, WiFi, and Cell on no airplane mode. I also managed to beat the G3 and almost got the same battery time as the OnePlus One.
*Comparisons where made from the battery times here:https://browser.primatelabs.com/battery-benchmarks
Shorty88jr said:
I just ran the Geekbench 3 battery test and managed to get 5 hrs 45 min and a score of 3456 on the beta settings. I managed to beat the G4 battery time by 50min and this was with 30% brightness and Bluetooth, WiFi, and Cell on no airplane mode. I also managed to beat the G3 and almost got the same battery time as the OnePlus One.
*Comparisons where made from the battery times here:https://browser.primatelabs.com/battery-benchmarks
Click to expand...
Click to collapse
Hi, dude. I'm very interested in tweaking my G4 to get better battery life as at the moment I need to charge it twice a day. I just have a noob question, could you please tell me how you disabled touchboost using Kernel Adiutor?
IvanN8458 said:
Hi, dude. I'm very interested in tweaking my G4 to get better battery life as at the moment I need to charge it twice a day. I just have a noob question, could you please tell me how you disabled touchboost using Kernel Adiutor?
Click to expand...
Click to collapse
Go to the CPU section then scroll all the way down till you get to a section that says CPU Boost. Set the Interval to 0 Sync Threshold disabled and Input Interval to 0. The input boost frequency will never disable for me but with the above settings it shouldn't matter because it will never run anyway.
Shorty88jr said:
Go to the CPU section then scroll all the way down till you get to a section that says CPU Boost. Set the Interval to 0 Sync Threshold disabled and Input Interval to 0. The input boost frequency will never disable for me but with the above settings it shouldn't matter because it will never run anyway.
Click to expand...
Click to collapse
Ok. I really thank you. Just entered the values, I will give it a try and report back on how it goes. Those numbers you got look really good.
IvanN8458 said:
Ok. I really thank you. Just entered the values, I will give it a try and report back on how it goes. Those numbers you got look really good.
Click to expand...
Click to collapse
I would try the GhostPepper settings first. The beta settings seem to give me better battery but they are still a work in progress and not as smooth as the other settings but you can use them if you want any feedback on those settings would be appreciated. I was also surprised how much those settings did for my battery life.
I decided to do a benchmark on how much of a difference there was between stock and the custom settings and to show I wasn't making stuff up by saying that I used these settings and magically got almost double battery life With the stock settings I got just a hair over 3hrs vs almost 6hrs on the tweaked CPU settings. You can see the results from stock in the IMG. The results for the tweaked settings are near the bottom of the first page.
IvanN8458 said:
Ok. I really thank you. Just entered the values, I will give it a try and report back on how it goes. Those numbers you got look really good.
Click to expand...
Click to collapse
How is your battery life after trying the settings out for a few days?
hey man i just tried yours and let we see the performance in next day. anyway the tweak that youve done is only on the CPU? no GPU or whatsoever? what if i implemented from others, let say other G4 users that tweak the GPU and i combined with your CPU tweak. any problem?
Hey man, how could I get the tweak for this setting? Thank you
I didn't think you could tweak the kernel without an unlocked bootloader for the Verizon G4 (vs98613b)?
elrosid said:
hey man i just tried yours and let we see the performance in next day. anyway the tweak that youve done is only on the CPU? no GPU or whatsoever? what if i implemented from others, let say other G4 users that tweak the GPU and i combined with your CPU tweak. any problem?
Click to expand...
Click to collapse
Yes just CPU and yes you can use GPU tweaked combined with the CPU tweaks just be aware it may affect stability.
glees.shin said:
Hey man, how could I get the tweak for this setting? Thank you
Click to expand...
Click to collapse
You need to be rooted then use the app kernel adiutor and change the values in the app.