Possible simple fix to Multitasking and battery life help - worked a charm on my D3 - HTC One X

This may be of great use - it was to me on my Droid 3 and I noticed weird settings posted on here in HTC's default Build.prop that explain IMO the memory Issues people are perceiving.
Multitasking can easily be fixed in build prop by editing the corresponding values (I assume, not tried it yet but I've seen the values in the prop.). Some of the default HTC settings baffle me. Or use RomToolbox by JRummy - its easy and works on Boot. You can also edit lowmemorykiller using this app, I always start on mild and take off about 6 megabytes on the bottom 3 categories.
Ive not rooted yet but on my D3 (512mb ram) I used dirty ratio 70% (HOX default is 0%....!) Dirty background 90% (Hox default is 30%) and vfs cache pressure 10. Hox default is 100. This makes android flush the cache less often, saving battery and eliminating stutter (uses CPU time and I/O to flush the cache), keeps apps in background ram leaving you where you left off and doesn't negatively impact on battery life or degrade performance over time (reboots every couple of days can't harm though). I've no idea why the HOX's default settings are so aggressive - unless they thought users might get an errant app, leave it running and complain when they dont know why the battery is draining... oh and kill OOM allocating task was also a yes (can't remember if you set that to 1 or true in build.prop but there's a checkbox on Romtoolbox for it).
On my Droid 3 with the above settings, I could infinitely multitask (VM Heap of 48mb - but on HOX you could easily double that for more tabs in browser etc) and my battery gained a perceived time of about an hour at least - maybe more, due to the apps always remaining open and CPU time not having to be used reopening them and redrawing the past state they were in because theyve been pushed out of RAM.
I researched the above for ages looking for and testing the best combinations online when I had my D3 (even with 512mb ram Moto's settings were way less aggressive than HTC's are at default) and made sure they wouldn't cause lag over time, or loss of performance over time - as well as providing optimal battery life.

Related

[Q] resent Reboots and freezes without any system changes

Ok, I must say that I have not had any reason to complain regarding the ROM's that I'm using, I will make this thread a bash of them either, but Ineed to understand a few things....
Ok so I have been running CM6.1.0 stable for a few weeks (since it was made available) and really have not had many issues. As a matter of fact it runs very smooth. I have since installed Pershoot's kernel and it much improved my battery....and here lies the issue I have tried to run many scenarios to improve my battery duration (about 8 hrs on ChiChis 1800 mAh).
So I have installed the following apps:
- Advanced task Killer - set on agressive
- Juice Defender - set to turn off all connections while screen is off
- Juice Tracker - Plots battery consumption (very nice!!!)
And while my battery performance has increased greatly...I'm getting anywhere between 13 to 17 hrs depending on use and gaming.
The other thing that I found rather odd was the fact that I no longer have the 5 different options on SetCPU. I am limited to:
- Performance
- On Demand
- User space (recommended not to be used by dev).
I am missing:
- Conservative
- ???? I forgot what what the other level
Nayone having or had anything like this?
As I'm typing this I'm downloading the Pershoot Kernel, but I am still hesitant about the CM 6.1.1.
Thanks!!!

[How to] Improve battery life

I'm new here & making this thread in order to share my own experience plus what I've learned from others since there're a lot of concerns regarding battery life.
Followings are what identified as the most power consumption sources and we'll fix them 1 by 1:
1. HD screen: I usually set the display brightness manually to about 15-20%. It is quite acceptable as I almost stay indoor at day time (surely this will make your screen nearly blind at this level if you try it outdoor under sunset)
2. Duo core 1.5GHz CPU: Having your CPU at this speed makes your phone soooo hot for heavy tasks. I use SetCPU to set the speed to 1188Mhz max and 192MHz min and also use SetCPU to enable the Screen Off profile where the max & min speed both set to 192MHz (there're no reasons to run it at high speed when the screen is off, right?).
3. The stock home launcher: I found the stock launcher (called LG Home) always takes a high portion of battery so I replace it with Go Launcher. This app also has a nice feature where you can see and close all running programs so you won't have to install another task killer.
4. Bloatware: Firstly, install Titanium Backup and "Freeze" whatever bloatware you found in this list (thanks youngv408) including the LG Home but only after you install & use Go Launcher. Secondly, install Gemini App Manager, at its home screen you will see running apps, for each of them that you don't want them to autorun (no more running in background & no more auto restart if you kill it), tap on the app name > choose More Operation > Config "Autorun" (root) > disable all of its autorun options (don't ever disable or freeze the Go Launcher if you are using it!)
Above tips keep my boy easily survive 1 day with 50% battery left (with 5,6 phone calls, some SMS, some 3G for web & downloading and little gaming). Hope they help.
All good tips, thanks!
Some good suggestions except for maybe #2. Personally, I found SetCPU had a dramatic negative effect on my battery life. Uninstalling it netted me several more hours with average usage immediately. Also, don't use task killers other than the built-in features of Gingerbread to kill a misbehaving app. The OS already does a good job managing running apps. Turn off GPS because some apps like to ping your current location occasionally and GPS uses a lot of juice. Finally, make sure apps like Facebook, Twitter, Google Plus, Google Currents, Gmail, etc. aren't set to sync too frequently.
Malnilion said:
Some good suggestions except for maybe #2. Personally, I found SetCPU had a dramatic negative effect on my battery life.
Click to expand...
Click to collapse
+1
According to battery use info smaller cpu clock resulted in more cpu total time usage
This battery gets better everyday... never had this experience with another phone.
Weird is, that after i no-bloated and did some tweaking in the beginning, the batterylife was still very disappointing. It seems that it is growing with the user...
we can turn off wifi or 3g if we don't use them,so we can extend the time

How to increase HTC One X battery life

There is no doubt that HTC One X is the most powerful phone on the market yet, despite it's stock of amazing hardware features it also has a few lacks. And on of the biggest perhaps is the short battery life, but with a few tricks and modifications it is possible to overcome that and so increase the battery life of the best phone yet.
Well I found 6 tricks and extras that can really increase your battery life up to 20%:
1. KILL APPS USING TASK MANAGER
Notice or not but there are a lot of apps and services running in the background of your phone that suck a lot of battery and most of them are apps that you wouldn't need so killing those processes can increase your battery life.
To kill apps you have to access the task manager:
Press home icon>all apps>search for task manager and launch it.
Now you have the option of killing separate apps (press X on the process you want to end) or just ending the all by touching the stop all button.
2. Closing open Apps
A great feature in htc one x is also that you switch between open apps but it can also take a lot of battery depending on how many Apps you =have open.
How to close open Apps:
Touch the recent app button (in right to the home button)> now swipe the open Apps (the ones you want to close) to the top.
3.Disable Transition Animation
Transition Animation also take a lot of batter since the require more ram and disabling them can also increase your ram therewith your overall system performance.
How to Disable Transition Animation:
Go Settings>Display & gestures> uncheck the Animation bar
4. External Battery
Well there is always an option of getting an external portable battery which is quit inexpensive and can double your battery life.
5.System directory Modification
Just a few weeks ago a member (mike1986) posted about a file or directory displacement made by HTC that caused the short battery life. And now you can correct it and you could boost you battery life by up to 20%.
LINK TO mike1986 POST
6.Battery Save App
A battery save app could also be a life save as you can monitor exactly how much on what you're spending and then configure power save modes using apps such as Easy Battery Saver.
You can also turn off services such as 3g/WiFi/GPS to save battery consumption advanced users can also scale the CPU and more system operation with such brilliant app as JuiceDefender - battery saver.
RECOMMENDED BATTERY SAVER APPS:
*JuiceDefender - battery saver* Free
JuiceDefender Ultimate Cost Money
Easy Battery Saver Free
Conclusion:
Following those six step should improve your battery life a lot and should therewith resolve the major issue with the HTC One X.
:goodlease Comment and Thank if you think that this post was helpful.:laugh:​
Hi
HRandev said:
There is no doubt that HTC One X is the most powerful phone on the market yet, despite it's stock of amazing hardware features it also has a few lacks. And on of the biggest perhaps is the short battery life, but with a few tricks and modifications it is possible to overcome that and so increase the battery life of the best phone yet.
Well I found 5 tricks and extras that can really increase your battery life up to 20%:
1. KILL APPS USING TASK MANAGER
Notice or not but there are a lot of apps and services running in the background of your phone that suck a lot of battery and most of them are apps that you wouldn't need so killing those processes can increase your battery life.
To kill apps you have to access the task manager:
Press home icon>all apps>search for task manager and launch it.
Now you have the option of killing separate apps (press X on the process you want to end) or just ending the all by touching the stop all button.
2. Closing open Apps
A great feature in htc one x is also that you switch between open apps but it can also take a lot of battery depending on how many Apps you =have open.
How to close open Apps:
Touch the recent app button (in right to the home button)> now swipe the open Apps (the ones you want to close) to the top.
3.Disable Transition Animation
Transition Animation also take a lot of batter since the require more ram and disabling them can also increase your ram therewith your overall system performance.
How to Disable Transition Animation:
Go Settings>Display & gestures> uncheck the Animation bar
4. External Battery
Well there is always an option of getting an external portable battery which is quit inexpensive and can double your battery life.
5.System directory Modification
Just a few weeks ago a member (mike1986) posted about a file or directory displacement made by HTC that caused the short battery life. And now you can correct it and you could boost you battery life by up to 20%.
LINK TO mike1986 POST
Conclusion:
Following those five step should improve your battery life a lot and should therewith resolve the major issue with the HTC One X.
:goodlease Comment and Thank if you think that this post was helpful.:laugh:​
Click to expand...
Click to collapse
The biggest drain is the screen, so turn down the brightness.
Those other tips are probably more a placebo, and killing tasks is a bad idea on Android. Most of the apps are just loaded into memory but not actively running so not using power, and when your phone screen is off, nothing is running (unless you have a badly behaved application that is). Even if you have most of your memory empty of applications, those memory chips are still drawing the same power regardless, so it makes sense to keep applications in memory. Why? Because when you want to use the app again, the phone doesn't have to waste CPU cycles and power loading the application from the flash memory, then loading the applications saved state, so power is saved. If you never use the app again, and memory is short, it gets unloaded.
There is also the school of thought that if you shut down all background applications and so you lose functionality (background status updates, location services, push mail services, animations, weather displays etc), you then haven't got much of a smart phone!
The system directory modification related to an old version of the firmware, I doubt anyone is effect by that issue now.
Regards
Phil
It wouldn't effect your internal system apps
PhilipL said:
Hi
The biggest drain is the screen, so turn down the brightness.
Those other tips are probably more a placebo, and killing tasks is a bad idea on Android. Most of the apps are just loaded into memory but not actively running so not using power, and when your phone screen is off, nothing is running (unless you have a badly behaved application that is). Even if you have most of your memory empty of applications, those memory chips are still drawing the same power regardless, so it makes sense to keep applications in memory. Why? Because when you want to use the app again, the phone doesn't have to waste CPU cycles and power loading the application from the flash memory, then loading the applications saved state, so power is saved. If you never use the app again, and memory is short, it gets unloaded.
There is also the school of thought that if you shut down all background applications and so you lose functionality (background status updates, location services, push mail services, animations, weather displays etc), you then haven't got much of a smart phone!
The system directory modification related to an old version of the firmware, I doubt anyone is effect by that issue now.
Regards
Phil
Click to expand...
Click to collapse
I do appreciate your replay but it only shows you those task that are running separately (not internal system apps) and if you kill them it does make a difference in the overall performance. And some operations like navigation running in the background continuously uses GPS and even Data constantly, so if you end it, it does make a difference.
You are right with the screen brightness, I thought about it and came to a conclusion to just leave it at auto because no one would like a dim display.
So it wouldn't completely turn off your data or calls or corrupt your system since you wouldn't terminate any internal system apps
regards,
HRanDev
PhilipL said:
Hi
The biggest drain is the screen, so turn down the brightness.
Those other tips are probably more a placebo, and killing tasks is a bad idea on Android.
Click to expand...
Click to collapse
+1
And also control 3G/WiFi/BT radios as and when needed , there are battery saver apps like Juice defender that intelligently turn off 3G and data connections.
Advanced users can also play around with custom kernels, CPU speed settings and Kernel governors, etc.. (can help with custom ROMs)
Thanks for the tip, I added it to it.
Actually agree with PhilipL.
Killing or managing tasks in Android is a placebo - and is likely to do more harm (in terms of battery life) than good. Plenty of articles if you google saying task managers are a bad idea.
However, managing screen brightness and background services will help enormously.
Sent from my HTC One X using xda app-developers app

Battery/RAM/Speed Optimization Tips for Android Phones

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

[Q] Dat memory usage, yo...[VZW Gnex] (SOLVED-ISH)

I have tried almost every rom/kernel combination available and cannot seem to sustain an acceptable amount of RAM usage. I constantly have over 60-70% memory usage and there is NOTHING installed on the phone yet! It's causing massive slowdowns that make the phone nearly unusable. I cant seem to find the problem.
Currently using PA 4.3 beta with ASKP 4/2 build. Same issue. I've tried 4.2.2 roms, 4.3 roms, and every available 4.4.2 rom + kernels.
Is there any way to cut down the RAM usage? An app, a mod, a kernel/rom combo that will help me out here? Or is it just my device? I had one before and do not remember it being this awful before
since nobody seems to have any insight, id like to update with a note or two...
PA 4.3-Beta2/Dirty-V 20140422 is BADASS. Memory management is MUCH better. only about 40-50% RAM usage anymore. here are the settings im using (with TricksterMod for PERFORMANCE...battery is...meh):
General Tab:
I/O - 1280/fiops
CPU -
Min 350000
Max 1650000
Max Scr. Off 525000
Min Scr. On 350000
Governor - interacivex/smartassv2/ondemand (i switch between them for no reason at all really, just to test the difference. none really noticed. dyninteracive causes bootloop)
Specific Tab:
Content Adaptive Brightness - ON
Force Fast Charge - ON
Multicore Power Saving - 2 (just because...dont really know what impact it has)
High Performance Sound - ON
Headphone Volume Boost - 1
Vibrator Strenght - 127
Dynamic FSYNC - ON (havent noticed an impact either way...maybe battery life?)
Temperature Limit - 80
Temperature Throttle - ON
GPU OC - 384MHz (512 on my device causes garbage/lag in alot of games)
ZRAM - OFF (dont really understand its purpose...)
Voltages are untouched (suggestions?)
Phone does get pretty hot playing games like Asphalt 8/Real Racing 3/CoD: BOZ/CoD: Strike Team/anything graphically intense, but they all run exceptionally well. Apps that arent intense on resources are super snappy and much more responsive than they used to be on any other kernel/rom combo i tried.
These are just MY settings (again...for PERFORMANCE) Battery life is great depending on what im doing and how long im doing it for. Left alone with moderate internet usage i can get about 3/4 day with it. Gaming...forget it lol.
Any tips on better performance without the heat?

Categories

Resources