Database Info

Advanced Tricks for Saving Battery (it Works)

EDIT: Last Update: 10th Sep 2011 with New INfo (trick no.7)
Advanced Tricks for Saving Battery
The following tweaks can greatly save battery if you done it right. But bear in mind that risk are relatively higher since its involve those deep system components.
If you know what you're doing, there is not much to worry about.
Note: I will not responsible for the any damage of your device
My Result:
Before: After moderate usage of 20 hours, Battery Left 30% - 35%
After : After moderate usage of 20 hours, Battery left 70% - 75%
Note: Battery Usage is very subjective matter. The numbers here is not trying to give you an exact calculation, it just trying to give you a feel of how the battery saving. But i have try my best to be consistent on the usage pattern, cpu loads and temperature to do this comparison. Of cause, you might discover different result on your device. With different ROM, kernel, radio, usage, screen brightness, all the other factors come into play, the result would varied.
Kindly please post a feedback on how it works on your device>
1. Use Undervolted Kernel / ROM
- Undervolted means that your device will use relatively less battery to give the same CPU frequency
- (e.g. normally CPU run at 1.61ghz @1350mv, after undervolted it may require only 1275mv at the same frequency)
- Tested on my device, it is the most effective tweak to increase battery life (I reduced -100mv at most of the CPU frequency (except 1), give me about 30-35% more battery)
- Because the undervolting value is varied depend on the ROM and kernel, so no point i post all the numbers here. (PM me if you need the list)
- Ask at your respective ROM thread for the availability of undervolted tweak
- If you wanted to try to change the undervolting value, i recommended to use OC/UV beater2 http://forum.xda-developers.com/showthread.php?t=1207546
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
- Because the tool have ease-to-use interface (no need use terminal emulator), just few taps will do.
- Most importantly, we can test new UV value with "Temp Activate", if the device freeze, just restart and it will go back to the last good state (last best config for you, instead of kernel's default value), and no need to flash the vddreset.zip / other reset.zip
2. Use "GSM auto (PRL) to save more juice while still connecting through 3G
- in the phone setting>wireless and network>MobileNetwork>NetworkMode
we are only allow to choose GSM only/ WCDMA / Auto between two
- but if you use type "*#*#4636#*#*" to phone Information, you can choose more type of networkmode. It is claimed that choose "GSM auto (PRL)" allow you to save more battery (cell standby) while allow you to connect to 3G network.
- This might somehow depend on your carrier / provider
- Please provide feedback on this. THanks
3. Try out different CPU Governor
- nowadays a lot of ROM have advanced CPU governor like Smoothass, Smartass, Interactive, etc.
- Try different combination during wake up and screen off to look for the best setting that let u save more juice
- This are my settings:
Governor during awake = On Demand
Max Wake = 998mhz​ Min Wake = 122mhz​ Governor during Screenoff = PowerSave
Max Sleep = 307mhz​ Min Sleep = 122mhz​ - NOTE: if you put min sleep too low, there is a chance that you device might freeze and won't wake up!
- I personally recommended "DaemonController" from Sybregunne for controlling the CPU governors and frequencies. It is a ease-to-use, yet sophisticated enough for the purpose of OC/UC. It is my favourite OC/UC controller since it released.
- DaemonController is a smart tool that it will bypass virtous daemon, and use direct frequency if we choose governors that is incompatible with the virtuous o/c. Hence, only 1 deamon is run which is more efficiency.
- Refer to the original thread here for more details: http://forum.xda-developers.com/showpost.php?p=16726715&postcount=2
- Quoted from original thread: "It is a Graphical tool that allows users to change andrev_oc/virtuous_oc frequencies and governors without having to reboot their device. Confirmed to work on Android Revolution HD 6.1.0 and a lot more ROMS.
4. Use AutoKiller Memory Optimizer
- This tool is different from other app killer
- It fine tunes android systems inner memory manager to keep your device fast over time.
- As a side effect it also lowers battery consumption.
- At certain free memory level (e.g. 250mb), the android os will automatically close those apps not in use (according to original android os logic)
- The lowMemoryKill level can be modified to suit your style of usage. It is to find a balance point between "not killing the apps you're need" and "sufficient free RAM to avoid sudden out of RAM / Laggy ".
- What i experience before is that these values are set to be too low. It keep most of the apps opened in background. So we can use the apps much faster and consump less cpu. Result: we have lower free RAM. The tradeoff: When I open heavy game, I experienced run out of RAM (it tell me not sufficient RAM to run).
- When the values set too high. It will kill the apps in background faster. So we will spend more cpu, and slower to reopen it. Tradeoff: you will have alot of free RAM back there. But for what?
- Therefore, it is to find the middle point that satisfy both ends. Generally, users with more apps better off with lower lowmemorykill value. Users with less apps (always switch between fews app only), are better off with higher lowmemorykill value.
- MY case: I only have 25+ apps installed. and Only use few apps (other rarely use). THis is my setting (in Pages): 3072, 8192, 16384, 50688, 58368, 76288. I have experimented with many values for 3 months. Just 1 month ago, i found these value suit me very much. It keep balance between the two tradeoff mentioned. Maybe you can try to figure out your own.
- Generally, we play with the last 3 numbers only. The first 3 numbers is related to:
(Foreground app)
(Visible app)
(Secondary server)
Which offer no significant benefits if we kill them.
5. Use Autostart
- Instead of closing them, it would be better if we don't let the app start from the begining
- You can choose to disable those app that u feel unnessary, so that they will not run during your phone startup
5. Check your Battery Consumption
- Download "Current Widget" or "battery monitoring widget" from market
- these apps will monitor your battery usage and recoded in a log file
- This is the normal consumption rate (varied across ROM, kernel and CPUI frequency and other factors)
Sleep/ScreenOff Consumption: 2mv - 8mv
WakeUp Consumption (no wifi, just use local apps, no gaming): 150mv - 250mv
Gaming consumption: about 300 - 400 mv (varied across diff games)
- To be comparable, it is suggest that you try to compare the consumption rate with your friends with same ROM, kernel, radio)
- With the monitoring log, you will able to notice adnormal peak / adnormal high drainage easily
6. Use "Battery History for GingerBreak" to check what running in background (Especially thanks for Saluco for this useful way to check battery drainage )
- this is a free tool can be download from xds forum http://forum.xda-developers.com/showthread.php?p=13328125
- Go to "Partial Wake Usage" to see what apps running when your device is sleeping
- Please "thanks" the developers of the apps for creating and letting us use his useful tool
- Give the screenshot of "Battery History for Gingerbreak" to the community of your ROM, this will give them more clues for them to help you
- For consistency, please monitor your usage for at least 3 hours (@ frequency 1 - 5 minutes) in order to have sufficient data and reliable readings.
7. Disable "Receiver" of application using AutoRun Manager (Really for Advanced User ONLY)
- Receivers are the "condition" where if it is fulfilled, the app will be executed
- For stance, Google Map has 8 receivers. Either 1 of these 8 conditions is met, google map will be open and run automatically.
- Now we actually try to disable this autoRUN by disable the "receiver" = means that even if the condition is met, the app won't run
- TO do this we need donated version of AutoRun Manager (available in market) to do this, go setting enable advanced mode
- Go second tap of the menu (advanced menu) to disable the receiver of particular app
- It is HIGHLY recommended to disable 1 receiver at 1 time, so that you can know the impact and trace back to the receiver
- you might get confused if you disable too many receivers at 1 time
- WARNING: ONLY disable those receiver that you know. DIsable system's receiver will make your system instable. So better only disable the user app.
- WHY IT IS USEFUL? Example: i used "Battery History for Gingerbreak (tip 6) to found out that "Facebook for android" is locking my device from being deep sleep (as it shown as high minute usage in the "partial wake menu"). Then i wanted to disable the feature of the that keep my device awake. THen i disable the "awake service" receive of it. Then it will help to save more battery by preventing those app that run automatically when certain conditions are met (example: Wifi-on, location changed..etc_
<More humble sharing is coming>
<<< Please click on "Thanks" if you found this post helpful, your thanks are very much appreciated >>>
------------------------------------------------------------------------------------------------------------------------------------------------------------
(The content is talking about HTC Desire HD, but the tricks can generally apply to any other smartphones, Hope it help you~)
Well it’s been 7½ days since I reviewed the Desire HD in which I said I didn’t want to comment on battery life until I’ve used it for 10 days. Tomorrow morning at 10am will be the 10th day, but I’m ready 14 hours early!
I’ve seen a lot of talk on the internet about terrible battery life, I’ve even experienced it myself (10% per hour on standby) but not wanting to give it a bad name without being sure, I’ve waited. I can now declare – the Desire HD does not have a battery life issue!
Read on after the break for how you can make yours last 24 hours on one charge!
Let me explain first of all, why I don’t think there is an issue. My Desire HD, last night and today, has shown better battery life than my Samsung Galaxy S and Nexus One ever did. It will probably continue to improve for the next week too.
Yesterday, after 10 hours of medium to light use (screen on was 40 minutes), I was still at 59% battery.
Today, I’ve been off for 12 hours and I’m still at 48%. The screen has been on for 50 minutes, 30 minutes of streaming music via bluetooth, 1 hour of podcasts playing through my earphones and a few text messages. Generally, on standby (and not being used) on 3G while at work, it was only using 2% an hour! I’m not [/B]sure any Android phone has ever managed that low consumption for me.
I don’t know how HTC have managed it from a 1230mAh battery, but if anyone manages to produce an ‘extended’ battery that fits, this thing could last a very long time. As for what the Desire Z might be able to do, wow!
So, what have I done to get this? As well as the usual tips I’ve given, here’s a few more for your Desire HD -
Remove apps you don’t use. You’ll need to root your device with VISIONary and then remove system apps like Flickr, Twitter, Stocks, Peep, Gmail and Friend Stream using Titanium Backup.
Syncing kills! Go to Settings -> Accounts & sync and see what apps are set to sync. For me, a big improvement came from turning off syncing my Facebook ‘Live Feed’ (this seems to turn back on at reboot). Also, only have one of the two Facebook apps syncing at all. For me, I stopped HTC Sense, News and Weather from syncing. If you really want these, maybe just drop their frequency an extra hour or two.
Lower e-mail checks. I have 4 e-mail accounts that K9 Mail checks for me. Like the other syncs, I dropped them from 15 minutes, to 1 or 2 hours, 4 for the less important one. Definitely don’t use the push e-mail setting on K9.
Try different connections. Go to Settings -> Wireless & networks -> Mobile networks and change Network Mode. For me, for some reason on Orange in London ‘WCDMA only’ works the best for me.
Calibrate. After 7 to 10 days use, calibrate your battery and you should be good to go, simple as that!
**ADDITION** Once in a while (if not always) try charging via USB rather than mains. It has been reported this is better for the battery and will actually provide better life from one charge. I can’t necessarily say this claim is true, but I have often seemingly got better life from a USB charge. Try it!
Bear in mind, there are people reporting much better life than I get. Some say they can last over 40 hours on one charge.
Also, make use of the ‘Power Saver’ in Settings. I’ve put mine at 30%. When this kicks in I tend to find battery consumption might even drop to 1% per hour, which means it may be possible you could last for 3 days on one charge! I can’t wait to see what happens when we get proper root and can use custom ROM’s!
(source:http://hemorrdroids.net/htc-desire-hd-battery-life/)
<<< Please click on "Thanks" if you found this post helpful, your thanks are very much appreciated >>>​
Looking for general guideline for your Lithium Ion Battery?
Have a look at this http://forum.xda-developers.com/showthread.php?p=15631703#post15631703

i might have to try this on my fassy

Is it necessary to have one of these threads every other day?
Sent from my HTC Sensation 4G

Turn off your phone. Battery life will be awesome.
Otherwise carry spare chargers and/or batteries. Simples.

DirkGently1 said:
Turn off your phone. Battery life will be awesome.
Otherwise carry spare chargers and/or batteries. Simples.
Click to expand...
Click to collapse
Lol. I have 3 spare batteries, girlfriend has 2. Still chew through em in a day
ADR6300

Not really sure anything here is new information...

Cheers, I'll try a couple of these.

How about putting your phone into Flight mode while at work.
I, for my part, get my mails to my desktop machine anyways and i like the fact, no one can distract me while I'm hacking in a gazzillion lines of code.
If it's important my lazy colleagues can use their legs and walk into my office.

flight mode is as good as switching off your phone

My battery already goes down like 1% every hour when the screen is off. So it's fine to me. It's only when I'm actively using WhatsApp, Facebook and Twitter that it goes down faster.
Main killer of the battery is the screen. The screen with high backlight burns through it. While idle it hardly drains.

thanks for this

servellia said:
How about putting your phone into Flight mode while at work.
Click to expand...
Click to collapse
I would get fired if I do that

I think you just made s regular phone from your smartphone
Sent from my Desire HD using XDA Premium App

Good reminders - thanks.

cooooll thanksss

DirkGently1 said:
Turn off your phone. Battery life will be awesome.
Otherwise carry spare chargers and/or batteries. Simples.
Click to expand...
Click to collapse
niceeeeeeeeeee

Thanks for the tips, although if Google just closed maps instead of having it open all the time!
Bet that would save some battery!

Good one to see... thanks for the post

I´ll try this...
Thanks!

I use Juice defender beta with ultimate features and i did calibrate my battery. It's 1:26 AM and through moderate to heavy usage i'm still at 41%. It still has a lot to do with your CPU speed (over/under clocked), ROM, Radio and kernel. I'm CM7 Lordmod's CFS kernel and the latest Radio from AT&T Stock (I have the Inspire the Desire HD's identical cousin.) and a RIL to match. Oh and I'm Overclocked to ~1.2 GHz using the ondemand governor.

[APP/OPEN SOURCE]Screen Standby ♯ Root [2.0]-Screen off while keeping device active

[APP/OPEN SOURCE]Screen Standby ♯ Root [2.0]-Screen off while keeping device active
SCREEN STANDBY ♯ ROOT 2.0
TURN OFF SCREEN AND AVOID OVERHEATING PROBLEM FROM PROLONGED STREAMING/GAMING OVER HDMI / MHL | DOWNLOADING DATA OVER WIFI
SAVE YOUR SCREEN AND BATTERY WHILE PHONE IS STILL RUNNING!
OPEN SOURCE!
AUTO SCREEN OFF / ON WITH HDMI CONNECTION / DISCONNECTION
Git Repo: https://github.com/nkahoang/screenstandby
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Remote Controller Feature - Public Review
Setting Wizard
Search Plugin
Selectable UI
Outgoing call automator
​
TURN YOUR SCREEN INTO TOUCHPAD, NO NEED FOR BUYING AN EXTERNAL MOUSE!​REMOTE CONTROLLER FEATURE!​SCREEN STANDBY IS NOW LIVE ON GOOGLE PLAY STORE!
The app is published under the name "Screen Standby ♯ Root"
VIDEO CLIPS SHOWCASING THE APPS:
SEE NEW FEATURES IN ACTION!
SEE APP IN ACTION! (thanks Doctor.Krouch so much for the awesome clips)
All About Android - Episode 86 with a short review of Screen Standby
XDA TV Review of Screen Standby!
CooLoserTech·Top 10 Best Apps of the week # 171
Click to expand...
Click to collapse
INTRODUCTION
Hi everyone,
This is originally for HTC One X, however, I have ported it to the Galaxy Nexus and now it could work on all devices! (Galaxy S3 / Moto Razr / etc). "Screen Standby" will completely turn off the backlight while keeping the phone running for MHL / HDMI streaming|gaming. That means you can now watch movie / play games on big screen and can still turn off the screen (touch screen still works!).
Click to expand...
Click to collapse
ROOT REQUIRED (Non-root method also available but not as effective & battery saving as root)
FEATURES
- Switch off the screen temporarily without actually putting the phone into 'sleep mode'. The phone is still running! It saves your battery, avoids heating to prolong battery life
- Since 1.96, screen can be optionally turned into touchpad!
- It has a nice little widget that let you quickly turn the screen off from your homescreen
- Since version 1.5 beta 2, shaking your device will temporarily toggle between complete screen off and lowest brightness level (so that you can perform quick action without playing a blind guessing game)
- Non-root method now available with 1.98 Beta 7
- One two dimmer: Turn off screen automatically after an idling time (no user interaction)
- Simple interface
Click to expand...
Click to collapse
WHY?
This little app will temporarily turn off screen backlight, however, unlike putting the phone to sleep, the phone is kept running. It is perfect for keeping the phone from heating from prolonged HDMI streaming over Medialink HD or MHL connection (the screen is off yet image/movie/games continue to be streamed) / or wifi data downloading, etc.
HOW DOES IT WORK?
It attempts to perform various actions (cutting screen voltage / brightness / light switch / writing a blank image to frame buffer, etc)
(Since 1.5, the voltage method is temporarily disabled)
For some devices, the screen may shutter a bit if Automatic Brightness is turned on. However, the app will automatically detect it and put the backlight into sleep again. So if you want to avoid the problem, set Automatic Brightness to false.. Since 1.7, enable auto brightness handling in app setting helps preventing this flickering
HOW TO TURN ON THE SCREEN AGAIN?
+ Click on the app notification on your status bar (since version 1.3) or
+ Simply put the phone into true sleep (short press power button) then turn it on (power button again)
+ Temporarily lid the light a bit by shaking the device (since 1.5b2, enable it in Menu -> Settings)
+ If you can't turn on using any of the above methods, press emergency button (in main app interface) to turn on / or use 2 by 1 widget
Click to expand...
Click to collapse
SCREENSHOTS (Updated for version v1.97)
Installation
Install as normal apk No big deal
Remember, install and use as your own risk, even though I can't think of any damage this little app can cause to your phone
Click to expand...
Click to collapse
Changelogs:
ßeta 2 Changelog:
Add toggable UI: Metro and Android Dark Holo (in Settings -> Extra)
New feature: Outgoing call automator !
First ßeta Changelog:
- New! Setting Wizard to help user quickly and easily set up Screen Standby. Simply select your known-supported device (the list is expanding!
Please help me) and your use-case (Streaming movie / Playing ingress / Playing Youtube etc) and the wizard will automatically select the optimised preset for you!
- New! Screen Standby Search Plugin to help automate Screen Standby from Search key (long press search hardware-key or softkey) or Google Now gesture (swipe up from Home softkey on Jellybean device). The plugin can now open Screen Standby interface, activate / deactivate / toggle screen off or launch Remote Controller
- Added better Root & BusyBox checker and helper
- Added new Tasker intent to control screen standby:
com.nkahoang.screenstandby.action.TOGGLE : to toggle screen on and off automatically
com.nkahoang.screenstandby.action.REMOTE_CONTROL: to launch Remote Control from tasker
- Added new option to broadcast an intent to Tasker when HDMI is detected (go to my app's settings -> HDMI Detection -> Enable broadcast on HDMI Connection/Disconnection. Specify intent action (case-sensitive) for each case. Go to tasker, add New System Event -> Intent Received, type exactly the action intent you provided in Screen Standby). The best part is, HDMI Intent can also be broadcast without activating Screen Standby (yeah, so you can use SS as a HDMI sensor for tasker)
- Added ability to use Remote Controller with Wifi-Direct (if a warning message is shown, just click 'Continue Anyway')
Optimizations:
- Continued optimisation for Nexus 4
- Added wake-lock to One Two Dimmer
- Slightly tuned sensors
From user report:
Normally, with the same amount of time watching movie, battery drain drops from 30% down to just 2%!!!!!!!!!!!
Click to expand...
Click to collapse
Please report bugs / feedbacks / suggestions.
To help me solving your issue faster, since version 1.31, you may want to open the app, hit "Menu" key -> Print debug info. It will then generates a log file containing the required information. Please send that file over pm to me. Thank you
Click to expand...
Click to collapse
Special thanks to:
- ppmeis (helps with S2, now S3 / Transformer and lots of other stuffs)
- winsettr (helps with Galaxy Nexus compatibility and constant reports)
- mnsk (helps with his Sony and Iconia)
- cocatriz (helps with S2)
- TheDarkLux (helps with Galaxy S3)
- evilmtv (helps with problems on GB devices)
Coffee buyers:
Styles Vancleave
- agronick from AppRadio / ARLiberator forum
- jjwatmyself (and also thanks for his mention of my app on his thread)
- jdbaldi
- jhanson
- MichaelMotes
Youtube clip:
- Doctor.Krouch
Click to expand...
Click to collapse
Tutorial: Setup app to work with tasker / Llama
Follow the instruction of this post:
http://forum.xda-developers.com/showpost.php?p=33073452&postcount=92 (Tasker)
http://forum.xda-developers.com/showpost.php?p=33073452&postcount=565 (Llama, thank Buzzthebuzzsaw)
DOWNLOAD
Stable version of app can be downloaded in attachments section on through Google Play Store. In addition, this thread will receive beta / experimental build in the future.
Archived build (1.1 to 1.96) can be downloaded from here
Click to expand...
Click to collapse

I like this great idea
Sent from my SPH-L710 using xda premium

Good idea finally something like this
Sent from my SGH-T989 with Darthstalker

Awesome app. I don't know if this makes sense, but on my Galaxy Nexus the previous version was much quicker to turn the screen off...
Sent from my Galaxy Nexus using Tapatalk 2

OCT 14 2012. App updated.
UI rework + Add notification to quickly turn off screen without put phone into sleep (see screenshot)
winsettr said:
Awesome app. I don't know if this makes sense, but on my Galaxy Nexus the previous version was much quicker to turn the screen off...
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
It should be slower the first time you use it only (since now it will manually find screen device for every phone, not hardcoded like before)

Working on TF300T almost perfect. The only "issue" is that when I turn off display, keyboard dock doesn't work (touchpad and usb works but not keyboard).
It doesn't work on my sgs2...I'll try at home with mhl connected and I'll report again. Nice work man. A must have app!
Confirmed it doesn't work on SGS2. It turns brightness at lowest level without standby screen.
Device Info:
Samsung Galaxy S II GT-9100 International
OS Version: 4.0.4 ICS (tested on GB 2.3.6 too)

Awesome app, one thing is that is a bit of a guessing game when trying to select apps and actions inside apps. Could be a tiny bit higher, so we can see at least barely what we are tapping on?

ppmeis said:
Working on TF300T almost perfect. The only "issue" is that when I turn off display, keyboard dock doesn't work (touchpad and usb works but not keyboard).
It doesn't work on my sgs2...I'll try at home with mhl connected and I'll report again. Nice work man. A must have app!
Confirmed it doesn't work on SGS2. It turns brightness at lowest level without standby screen.
Device Info:
Samsung Galaxy S II GT-9100 International
OS Version: 4.0.4 ICS (tested on GB 2.3.6 too)
Click to expand...
Click to collapse
Please download the latest version (1.31) which have print debug info ("Menu" -> "Print debug info") and sends the file it generates over to me. I don't have either of your devices so this may be the only way I can fix that bug.
jgaf said:
Awesome app, one thing is that is a bit of a guessing game when trying to select apps and actions inside apps. Could be a tiny bit higher, so we can see at least barely what we are tapping on?
Click to expand...
Click to collapse
Ugh, i'm not sure what you mean. Can you explain it a bit clearer? If it is possible then I shall implement that.

I think he's asking if you can make it have a little bit of light so he can barely see the screen. When you are using the phone with a TV, you have to guess where to touch the screen.
Perhaps an adjustable brightness setting or just a barely on setting would be helpful for some.

That really defeats the purpose of this app... If you need that functionality, look into Screen Filter or something similar that will lower the brightness but keep the screen on.
Sent from my Galaxy Nexus using Tapatalk 2

How about this:
Pressing the button will now toggle(circle) between three modes:
- Brightness On (app not functioning)
- Lowest brightness possible (but not completely off) and
- Zero brightness (completely turn off screen)

I HAVE BEEN LOOKING FOR THIS.!!!!! THANK U.! LOL
Sent from my PG86100 using xda app-developers app

nightwinn said:
I think he's asking if you can make it have a little bit of light so he can barely see the screen. When you are using the phone with a TV, you have to guess where to touch the screen.
Perhaps an adjustable brightness setting or just a barely on setting would be helpful for some.
Click to expand...
Click to collapse
Yeah this what I meant. Specially when playing games it is very hard, for stuff that can't be mapped into a gamepad
winsettr said:
That really defeats the purpose of this app... If you need that functionality, look into Screen Filter or something similar that will lower the brightness but keep the screen on.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
The thing with screenfilter is that it lowers the brightness on the TV too.
I just had another idea, don't know how complicated it would be to implement though. Would it be possible to add "an always on top or floating button" that would toggle the screen on and off. For example there's an app for exploiting games called Game Guardian, this app has a very small, semi transparent and movable icon that lets you access it from anywhere. This way when we need to open mxplayer and select a movie from our library we can easily turn the lights back on and then turn them off after selecting the video.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2

nkahoang said:
Please download the latest version (1.31) which have print debug info ("Menu" -> "Print debug info") and sends the file it generates over to me. I don't have either of your devices so this may be the only way I can fix that bug.
Click to expand...
Click to collapse
Here's the log. I hope it'll help to find the issue.

Hi, i have a I9300 SGS3 and i doenst work.
Here's the debug log.

TheDarkLux said:
Hi, i have a I9300 SGS3 and i doenst work.
Here's the debug log.
Click to expand...
Click to collapse
Your log has nothing inside! Is it because you didn't grant root access to my app? Try uninstall / reinstall and answer "Allow" when superuser/supersu asks you.
ppmeis said:
Here's the log. I hope it'll help to find the issue.
Click to expand...
Click to collapse
Sent you a pm for beta version.

nkahoang said:
Your log has nothing inside! Is it because you didn't grant root access to my app? Try uninstall / reinstall and answer "Allow" when superuser/supersu asks you.
Click to expand...
Click to collapse
It has, i tried uninstall/reinstall now, with same result. Log is empty
It is in my SuperSU app an has root access.
Here the log of SuperSU, because the app is writing anything in the log.
first log:
find /sys/devices -name 'brightness'
exit
sh: <stdin>(1): find: not found
second log:
find /sys/devices
sh: <stdin>(1): find: not found

BIG UPDATE: VERSION 1.4 BETA
+ Now have another way to turn off screen: SET SCREEN VOLTAGE TO ZERO VOLT. With this we have some bonus advantages:
- Much faster turn off time
- No more shuttering with auto brightness!
- Should work with AMOLED Devices (Galaxy S2 / S3 owners, please report!)
However, you should upgrade only if previous version does not work for your devices since this method is still a bit unstable.

Thanks a lot mate, now it works
Confirm working on SGS3.
Bug Report (1):
I have the app VirtualSat.eu to watch tv. When i'm in the app menu, display is off/black (tv still on) when i then select to watch something, the display powers on again.
Bug (2):
after the first operation, i pushed the home button (display powers off again), then scrolled down the notification bar to disable screenOff, it disappears from the notification bar. But display is still off. So i pushed the power button to get to the lock screen (this method is working).
Edit(1)
Tested a bit more, (for bug 2): If i reopen the app an repush on the screen off button (to get the app back in the notification bar), and then tried to reactivate the display, the display powers on for about 2-3 seconds and then again powers off.
For Bug(1): Tried another TV app (Zattoo) there the display stays off if i select a station to watch. So i think it's the app who uses a command that gets the display back on.
But in anyway thanks for your work. Will test with some other apps.

TheDarkLux said:
Yeah thanks a lot mate, now it works Big up
Click to expand...
Click to collapse
Can you test your S3 with MHL as well? I want to make sure that my method guarantees MHL and HDMI works

[APP][4.1+] Save your battery power with Pixel Battery Saver (Pixel Overlay App)

Hi!
At the beggining - I'm sorry if you won't understand something. English isn't my main language, I still learn.
In some smartphones with AMOLED screen (such as Samsung Galaxy S4) black pixel = turned off pixel.
I've always been irritated because of the fact that our batteries aren't too great, but phone producers still produce their phones with hiper-resolution, which practically we cannot even see.
I have invented something, that later I turned to real app.
I call it Pixel Battery Saver, because it displays some kind of totally black mesh on the screen (you can change its density), so at least half of the pixels (or more) are turned off (so the screen consumes less energy!), while you are still able to read anything on your screen.
If you still don't understand, just take a look at the screenshots.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've already created this app.
You may download and test it for free,
but if you really appreciate my work - I would be grateful for every donation (every single dollar would be helpful).
Let me know if you found any annoying bug or misspelling. This is my very first app - I still learn
FAQ:
What do I need this for?
- Imagine this situation - your battery level is really low, but you have to search for something important on the Internet. Making the brightness lower often isn't enough. That's when you would need my app - to turn off some count of pixels.
There are lots of apps that dim the screen...?
- This app works different. It doesn't overlay your screen with transparent image (but there is such option in premium version if you need it too). It overlays your screen with totally black screen, which makes some count of pixels off, to prevent them from consuming battery.
Do I really need AMOLED screen?
- The best results you can get right with AMOLED screen, where black pixel means turned off pixel. However, even in other type screens black pixels are saving some battery, so it's just worth to check.
In battery stats I can see that this app consumes a lot of energy. Why?
- Don't look at the stats, look at the real battery consumption. Probably, Android Battery Stats app "thinks", that this app display an image on the screen all the time, because of what it shows an information about consuming energy. In fact, this app turns OFF the pixels (in AMOLED screens with this function), so it SAVES that energy, not consumes.
When the mesh is on, I am unable to install apps (Install button is disabled). WTH?
- That's because of the Android Security. In premium version of Pixel Battery Saver I added an option to bypass this protection. In this free version you can simply turn off the app (by clicking "Turn off" button in Settings window) before installing any app and then turn on it again.
Density of the mesh that I recommend is "High".
Changelog in post #2.
Download: Google Play

Always use the latest version with fixed bugs and new options.
[CHANGELOG]
v1.3 (coming next month):
- new option to automatically start service at specific battery level
- hidden notification icon
- option to detect package installer to prevent its bug (stops mesh activity when you're installing new app and starts it again when it's done)
- new option to dim the screen (useful at night)
- small fixes
v1.2.1:
- fixed doubled mesh after reboot (black screen)
- fixed unnecessary scrolling to the bottom ad
v1.2:
- quickly show/hide the mesh with notification action
- Ads. Sorry =)
v1.1.1:
- shortcut to the donation page
v1.1:
- new option to automatically start service on boot
- small bugfixes
[TO DO]
- Widget
- Overlay bottom navigation bar too
[KNOWN BUGS]
- I can't install any app (unable to tap Install button)
> This bug is fixed in version 1.3 (added new option to prevent this)
- The bottom navigation bar (with back, home and recent apps buttons) isn't overlayed
> I know about this, I will fix it in the future

disip said:
So, the question is - is anyone able to create an app like this?
Click to expand...
Click to collapse
There are a couple of issues with the concept as you've outlined it.
1) Turning off 50% of the screen you make small text unreadable. Even in your example the not so tiny temperature values are illegible.
2) While this would definitely conserve power in terms of physically lighting the screen, it might not be by as much as you'd think. The screen has multiple power sucking components. The first is the light producing LED's. Turning half of them off saves half the power. Simple math
. But the GPU that processes the screen imaging still runs at full speed even if the screen is blank. While the LED pixels aren't working, the GPU is still working to render a black image. So turning off half the pixels doesn't reduce the power draw required to run the entire display to 50% in total.
3) The app that overlays the black mesh will require the GPU to work overtime. It's got to render the image that's supposed to be in the screen plus it's got to render the black mesh over the native image. That could potentially use up more energy rendering the black than the black saves by not lighting the pixels.
4) The already built in option is to just turn the screen brightness down 50%. It accomplishes the same goal, requires no additional image rendering, and preserves the original image design without loss.

Skipjacks said:
There are a couple of issues with the concept as you've outlined it.
1) Turning off 50% of the screen you make small text unreadable. Even in your example the not so tiny temperature values are illegible.
2) While this would definitely conserve power in terms of physically lighting the screen, it might not be by as much as you'd think. The screen has multiple power sucking components. The first is the light producing LED's. Turning half of them off saves half the power. Simple math
. But the GPU that processes the screen imaging still runs at full speed even if the screen is blank. While the LED pixels aren't working, the GPU is still working to render a black image. So turning off half the pixels doesn't reduce the power draw required to run the entire display to 50% in total.
3) The app that overlays the black mesh will require the GPU to work overtime. It's got to render the image that's supposed to be in the screen plus it's got to render the black mesh over the native image. That could potentially use up more energy rendering the black than the black saves by not lighting the pixels.
4) The already built in option is to just turn the screen brightness down 50%. It accomplishes the same goal, requires no additional image rendering, and preserves the original image design without loss.
Click to expand...
Click to collapse
1) Why do you think so? As you can see on my image, it doesn't make the text unreadable (if the "mesh" is pixel-by-pixel)
2) Right, but everyone know that black-layout apps are muc better for our battery than colorful or white, right because black screen isn't that "hungry" of power
3) Ok, but there are lots of apps that creates a full-screen black (transparent) overlay to make the screen more "shade" (dim?) to save the power. It works, even thou all the thing you described in #3
4) Oh, right, but when my energy power is really low, I turn the screen brightness to the lowest level, but it still consumes a LOT of energy.
Anyway! This discussion isn't even important, maybe we should just CHECK if this may work, or if not?
But, as I said, I am just asking someone to create a simple app like this.
Thanks anyway for reply.

Really? No one?

disip said:
Really? No one?
Click to expand...
Click to collapse
it's not worth in my opinion, while rendering half of the screen black would help save some battery, the saving wouldn't be so great, yes the screen is what burns the most battery on android but, its not just having it on, its having the phone out of deep sleep, having the touch sensor activated and registering touches, etc, not to mention it would just kill the great viewing experience that the phone offers.

-Ric- said:
it's not worth in my opinion, while rendering half of the screen black would help save some battery, the saving wouldn't be so great, yes the screen is what burns the most battery on android but, its not just having it on, its having the phone out of deep sleep, having the touch sensor activated and registering touches, etc, not to mention it would just kill the great viewing experience that the phone offers.
Click to expand...
Click to collapse
Though when we are using our phones it has to render the whole screen anyway, so I think rendering a half of it would be better?
I am not thinking about this app making our screen always on. I just mean to display this mesh when we are using our phones and the battery level is low.
And, of course, it would kill the viewing experience, but when your battery level is 5% and you have to do some important research on the internet - you don't care about the viewing experience.
If you think turning the pixels on is not the thing that consumes the most of the battery, then turn the brightness to the highest level and then to the lowest and see how much it consumes... (changing the brightness doesn't change anything with the touch sensor and other thing you described though)
I thought my idea is really simple to develop for any Android developer and to see if it really works...

I think that if you do some comprehensive tests, you could bring some attention.
Create one image with this pattern, put on your phone and open it with any image viewer, put the bright on max. Let it run for some time.... Measure how much battery was sucked.... Test again with the same image, but without the pattern, do some statistics with the results.
Are you rooted? You could invert screen color or make it grayscale.

That's exactly what I was thinking about. I will do this tomorrow.

I'll post my quick opinion. It really depends on how the phone handles the screen, but my experience is from my old Galaxy S2 with NoLED running over night. I think NoLED program was essentially accomplishing what you are proposing (i.e. rest of screen is "off" or black) and on portion of the screen is on for the LED to hop around. However, even though the screen was black the screen was still draining at a quite high rate (~6%/hr on average). The screen needs to be "off" not just black in order to save more power.
But having stated the above, I am looking forward to your test results to compare and determine if it can save more battery.

liquidzyklon said:
I'll post my quick opinion. It really depends on how the phone handles the screen, but my experience is from my old Galaxy S2 with NoLED running over night. I think NoLED program was essentially accomplishing what you are proposing (i.e. rest of screen is "off" or black) and on portion of the screen is on for the LED to hop around. However, even though the screen was black the screen was still draining at a quite high rate (~6%/hr on average). The screen needs to be "off" not just black in order to save more power.
But having stated the above, I am looking forward to your test results to compare and determine if it can save more battery.
Click to expand...
Click to collapse
Thanks for your opinion, but the screen in s2 is way different than on s4. The screen in s2 doesn't turn off the black pixels. The one in s4 does.
II am looking forward to do this test tomorrow

I think this would be like a filter app, such as the found in Play Store.

Exactly. I was talking about it but I forgot the name. I next hour I will do some tests.

Ok, thread can be closed - I've created this app by my own. I mean, I used many of tutorials and examples, and finally got it. Thanks anyway.

Could you share your findings?

This would be pretty hard, as I have read dozens of sites and forums to understand everything. There wasn't any quick or simple solution.

Did it work and save as much battery as you expected?

leodfs said:
Did it work and save as much battery as you expected?
Click to expand...
Click to collapse
I still do not know, I have to test it multiple times to be sure.

Ok. I think it really works, but I'm still not sure. Give me few days to share the alpha version of my app (I just want to add some extra functions).
By the way, does anyone know where should I look for a list of phones with screens like in S4? I mean where the black pixel means it's off.

disip said:
Ok. I think it really works, but I'm still not sure. Give me few days to share the alpha version of my app (I just want to add some extra functions).
By the way, does anyone know where should I look for a list of phones with screens like in S4? I mean where the black pixel means it's off.
Click to expand...
Click to collapse
Here's a list of some recent ones. Pretty sure the Moto X has one as well.
http://www.oled-info.com/oled_devices/mobile_phones

Some battery test results

Today did some basic tests to see how the batter compared to a Sony Z Ultra.
Be advised this is not a fair test, the ZU is 2 years old. While the device has been properly maintained and not stressed a lot, its still with a two year old battery.
Screen on ( ZU: 45%, X2: 50% ( brighter then ZU to compensate the battery somewhat )), no activity.
ZU: Lost about 11% in 75 minutes.
X2: Lost about 4% in 75 minutes.
At that rate the devices will last:
ZU: 11h15 minutes
X2: 31h10 minutes
Now this matches up with a review i read where they state that the X2 will last 35 hours with screen on.
The double to triple battery life seems to match up with the reviews i read before. Its powering a bigger screen, higher resolution, has more memory ( 3GB vs 2GB ), and still triple the ( 2 year old ) ZU, despite given a extra handicap with a high screen usage.
Some benches:
AnTuTu:
ZU: 39.900
X2: 49.200
About 25% better benchmark performance. Memory had clearly more bandwidth, faster internal flash, CPU score was a bit of a head breaker. Faster on multithread and float ( probably because of the 64 bit ) but slower in the single core ( pure ) integer performance.
Screens:
If both devices are put next to each other, the ZU its color looks more washed ( grayish ) out compared to the X2. The X2's color are more stronger.
So far its a great ZU replacement.
Things i do not like: The screen has a higher output for everything ( everything looks bigger on the screen ) compared to the ZU where they reduced the rendering size for the font/etc, giving more content on the screen.
This needs a fix somehow ( do not know if this can be changed with a setting or needs a custom rom ).
That is it. Not a lot of time right now.

change dpi in build.prop if you are rooted.
If you are not rooted. run following command inside any terminal app :
- wm density xxx
- reboot device
where xxx is 170 to 400. keep changing it until you find are happy with resolution.

What is the standard DPI on the X2?

400
Flavio said:
What is the standard DPI on the X2?
Click to expand...
Click to collapse

bark1234 said:
change dpi in build.prop if you are rooted.
If you are not rooted. run following command inside any terminal app :
- wm density xxx
- reboot device
where xxx is 170 to 400. keep changing it until you find are happy with resolution.
Click to expand...
Click to collapse
Good advice, thanks.
Will changing the DPI affect all parts of the UI? For example, will the web browser show more content because the viewport will have been lengthened due to the smaller dot pitch?
I ask because I have installed third party launchers on my device that "simulate" a lower DPI by shrinking the size of text and icons on the home screen, but the magnification of all other apps is left unchanged.

Yes
aniym said:
Good advice, thanks.
Will changing the DPI affect all parts of the UI? For example, will the web browser show more content because the viewport will have been widened due to the smaller dot pitch?
Click to expand...
Click to collapse

bark1234 said:
change dpi in build.prop if you are rooted.
If you are not rooted. run following command inside any terminal app :
- wm density xxx
- reboot device
where xxx is 170 to 400. keep changing it until you find are happy with resolution.
Click to expand...
Click to collapse
Thanks for the tip Bark...
It did involve a bit more work then what was written above... You need to do a bunch of steps to conclude things to a good end. I made a little mini-guide to help people along:
http://forum.xda-developers.com/mediapad-x2/general/mini-guide-adb-installation-usage-t3183906
Hope it helps. Btw: 280 rocks for this device... makes a lot of websites run into desktop made, and Chrome shows tabs. Turns it into more of a mini-pc... and with the big screen its still very readable!

Can you tell us which standard apps are incompatible with the 280DPI setting?
Do the dialer and contacts work? And settings?

Flavio said:
Can you tell us which standard apps are incompatible with the 280DPI setting?
Do the dialer and contacts work? And settings?
Click to expand...
Click to collapse
So far there seems to be a bug with the navigation bar and landscape. In the sense that the navigation bar shows up but none of the icons show up ( and nothing reacts on the bar ). Not sure if its related to the 280dpi or not.
Some more battery numbers:
3h36min playing Fallout Shelter ( big battery eating game )
4.20min total screen time.
Battery loss: 44%

[/COLOR]
Benjiro said:
So far there seems to be a bug with the navigation bar and landscape. In the sense that the navigation bar shows up but none of the icons show up ( and nothing reacts on the bar ). Not sure if its related to the 280dpi or not.
Some more battery numbers:
3h36min playing Fallout Shelter ( big battery eating game )
4.20min total screen time.
Battery loss: 44%
Click to expand...
Click to collapse
Great info thanks. Would you be able to post some screenshots of the UI and web browser so we can see the difference 280 DPI makes in terms of screen real estate? Thanks!

Flavio said:
Can you tell us which standard apps are incompatible with the 280DPI setting?
Do the dialer and contacts work? And settings?
Click to expand...
Click to collapse
I have no problems at all with anything running the density at 280

aniym said:
[/COLOR]
Great info thanks. Would you be able to post some screenshots of the UI and web browser so we can see the difference 280 DPI makes in terms of screen real estate? Thanks!
Click to expand...
Click to collapse
Here are some apps running at 280 DPI.

bark1234 said:
If you are not rooted. run following command inside any terminal app :
- wm density xxx
- reboot device
where xxx is 170 to 400. keep changing it until you find are happy with resolution.
Click to expand...
Click to collapse
Seems to ask for writting permission:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
http://www.hostingpics.net/viewer.php?id=566688Screenshot20150822213331.png
So to be rooted, isn't it?

Try to run from adb shell.
Djiban said:
Seems to ask for writting permission:
http://www.hostingpics.net/viewer.php?id=566688Screenshot20150822213331.png
So to be rooted, isn't it?
Click to expand...
Click to collapse

Djiban said:
Seems to ask for writting permission:
http://www.hostingpics.net/viewer.php?id=566688Screenshot20150822213331.png
So to be rooted, isn't it?
Click to expand...
Click to collapse
Do this:
http://forum.xda-developers.com/mediapad-x2/general/mini-guide-adb-installation-usage-t3183906
Works perfect. Took me a hour to figure out those steps ( especially the missing driver! ). *lol*

Today finally did a full charge ( up to 90% ), with still 13% left. So in total been using the X2 from last week Thursday ( full charge to 97% on Thursday night at 20.30, with a small 10% extra charge-up on Saturday when it was connected to my USB for configuring ).
Did some navigation tests:
GPS: Fast lock-on even without A-GPS. Inside 3 meters from the window it found 4 sat's but no lock-on. Closer to the window got 12 sats with 10 in usage.
Cold start outside was done within several seconds, where it took my old HTC HD2 at times 3 or 4 minutes ( Hamburg = big building everywhere blocking the signal too much for my old HD2 its cold start )...
28 min driving with Sygic navigation, with 4G/Phone/GPS on had a battery drop of about 4% ( from 18 to 14% ).
Inside at my work, had GPS + 4G + Phone active during "sleep", drains the battery about 1 a 2% per hour. Probably the GPS trying to get the location while inside, what was draining the battery faster.
Biggest battery eater: Fallout Shelter... this eats battery like candy. I estimate that playing the game for 8 hours will drain the battery from 95% to 5% ... So that is good survivability. If all you do is comic book readying, i estimate that you can easily get 20h+ out of it.

Here are some power usage number over the last 6 days and half.
25/08 21.30: 100%
- Installing some software
- Wifi + Cell on all night
26/08 9.50: 93%
- Call 15 min
- Daily WeChat checks & talks
- Wifi ( useless, no connection ) + 2G + Cell on all day
26/08 17.44: 88%
- Some playing around
- Wifi + Cell on all night
27/08 9.22: 83%
- Call 15 min
- Lots of WeChat chatting
- Wifi ( useless, no connection ) + 2G + Cell on all day
27/08 17.23: 74%
- Wifi or 2G + Cell on all day, forgot to write down. Based upon the drop, i probably had 2G and no Wifi on.
28/08 9.22: 71%
- Some WeChat chatting & checking but low activity day
- 2G + Cell on all day
28/08 17.50: 69% << no joke .. only 2% that day??
... big gap, weekend. Forgot to write down numbers.
- Some software installing, playing round, internet usage, ... a bunch of things
- Wifi + Cell on all the time.
31/08: 08:00 ( Forgot to write down but it was in the 40% somewhere )
- GPS navigation for about 30 minutes in the car
- Wifi + 2G + Cell
31/08: 11.47 36%
- Chatting, etc ... you know the routine by now *lol*
- 2G + Cell all day
31/08 18.19: 31%
- 2G + Cell all night
01/08 9.50: 28%
...
In total my screen was on for about 5 hours according to the battery app but i have my doubts about the reporting. Sygic ( car navigation ) had run for a pure minimum of 30 minutes ( longer because i tested some things at home ), and this usage is not reported at all. And Sygic + GPS are medium/high power drainers.
My 4G/2G + Cell account for 24% of the power usage. Wifi accounts for 4%. My 5 hour screen time supposedly account for 4%...
Its not easy to get a perfect power profile because activities switch, or i forget to turn off the Wifi at work ( so its constantly wasting energy looking for a connection ), with then 4G/2G also active. Or forgetting to turn of the GPS after using the navigation.
In comparrison, my 2 year old Sony Z Ultra, this same type of activity ( minus any GPS usage because i tried to save the Sony Z Ultra from heavy work to extend its life ), resulted in about 2 days of work, before the battery started hitting close to 30 a 40% mark. At that moment i always charged up because it made me unconfortable.
On new battery, the Sony Z Ultra's life was closer to 2.5 days of activity. What is really not bad for a phone that big. Especially if we compare the battery life of most other smaller smartphone's from that time / era.
But the X2 so far is really trumping it massivly. If this was my ZU, showing 27% ( now ), i will have been like "o god, o god, need to charge it up" because its going to drain ( even doing nothing ). I do not have the same feeling with the X2.
And to be honest, i wasted a bunch of power because of the missing ability to automatically turn Wifi off, when your not near your home Wifi connection. So you end up with Wifi + xG active all the time outside. Love to install Trigger or any of the Xposed modules the moment it becomes available.
My estimate for tonight, when i officially hit day 7 ( 168 hours ), is that the phone will have 20% left. Hell, i can probably do another day and half with that. But i think that 20% is a good charge mark. Lower then that will damage the battery more easily ( if you keep low charging over time ).

Benjiro said:
Here are some power usage number over the last 6 days and half.
25/08 21.30: 100%
- Installing some software
- Wifi + Cell on all night
26/08 9.50: 93%
- Call 15 min
- Daily WeChat checks & talks
- Wifi ( useless, no connection ) + 2G + Cell on all day
26/08 17.44: 88%
- Some playing around
- Wifi + Cell on all night
27/08 9.22: 83%
- Call 15 min
- Lots of WeChat chatting
- Wifi ( useless, no connection ) + 2G + Cell on all day
27/08 17.23: 74%
- Wifi or 2G + Cell on all day, forgot to write down. Based upon the drop, i probably had 2G and no Wifi on.
28/08 9.22: 71%
- Some WeChat chatting & checking but low activity day
- 2G + Cell on all day
28/08 17.50: 69% << no joke .. only 2% that day??
... big gap, weekend. Forgot to write down numbers.
- Some software installing, playing round, internet usage, ... a bunch of things
- Wifi + Cell on all the time.
31/08: 08:00 ( Forgot to write down but it was in the 40% somewhere )
- GPS navigation for about 30 minutes in the car
- Wifi + 2G + Cell
31/08: 11.47 36%
- Chatting, etc ... you know the routine by now *lol*
- 2G + Cell all day
31/08 18.19: 31%
- 2G + Cell all night
01/08 9.50: 28%
...
In total my screen was on for about 5 hours according to the battery app but i have my doubts about the reporting. Sygic ( car navigation ) had run for a pure minimum of 30 minutes ( longer because i tested some things at home ), and this usage is not reported at all. And Sygic + GPS are medium/high power drainers.
My 4G/2G + Cell account for 24% of the power usage. Wifi accounts for 4%. My 5 hour screen time supposedly account for 4%...
Its not easy to get a perfect power profile because activities switch, or i forget to turn off the Wifi at work ( so its constantly wasting energy looking for a connection ), with then 4G/2G also active. Or forgetting to turn of the GPS after using the navigation.
In comparrison, my 2 year old Sony Z Ultra, this same type of activity ( minus any GPS usage because i tried to save the Sony Z Ultra from heavy work to extend its life ), resulted in about 2 days of work, before the battery started hitting close to 30 a 40% mark. At that moment i always charged up because it made me unconfortable.
On new battery, the Sony Z Ultra's life was closer to 2.5 days of activity. What is really not bad for a phone that big. Especially if we compare the battery life of most other smaller smartphone's from that time / era.
But the X2 so far is really trumping it massivly. If this was my ZU, showing 27% ( now ), i will have been like "o god, o god, need to charge it up" because its going to drain ( even doing nothing ). I do not have the same feeling with the X2.
And to be honest, i wasted a bunch of power because of the missing ability to automatically turn Wifi off, when your not near your home Wifi connection. So you end up with Wifi + xG active all the time outside. Love to install Trigger or any of the Xposed modules the moment it becomes available.
My estimate for tonight, when i officially hit day 7 ( 168 hours ), is that the phone will have 20% left. Hell, i can probably do another day and half with that. But i think that 20% is a good charge mark. Lower then that will damage the battery more easily ( if you keep low charging over time ).
Click to expand...
Click to collapse
That's awesome! I'm the opposite of you. I leave the screen brightness all the way up all day, use an hour or more of Navi, do about an hour of phone calls and Facebook, an hour or Web browsing, a half hour of Teamviewer, a half hour of texting, and maybe sneak in a game of Spades. The battery still lasts almost two days. This is amazing in a phone this size. No other phone I've had went this long on one charge with everything turned up. So far I really love this phone and plan on buying another soon.

ajsmsg78 said:
That's awesome! I'm the opposite of you. I leave the screen brightness all the way up all day, use an hour or more of Navi, do about an hour of phone calls and Facebook, an hour or Web browsing, a half hour of Teamviewer, a half hour of texting, and maybe sneak in a game of Spades. The battery still lasts almost two days. This is amazing in a phone this size. No other phone I've had went this long on one charge with everything turned up. So far I really love this phone and plan on buying another soon.
Click to expand...
Click to collapse
I know the feeling. Its one of those devices where you do not feel like your limited to x time on it, before you need to run to the charger.
Yesterday did about 30 min car ( 2 * 15 min ) navi with the car usb charger connected. The battery was at 62% before ( did some charging at work using the pc's usb port ) and it was 71% after i arrived home. The problem i have is, was it connected to the 2Amp port or the 1Amp ( its one of those Chinese dual usb ports mini chargers with no description: "what is what" *lol* ).
So still need to figure out if it was charging up on 1 Amps or 2 Amps ( to give me a idea of the power consumption while navigating ). The fact that it charged up while navigating is always a plus.
My old HTC HD2 had the habit of slowly draining while driving with the usb charger connected. Do not remember what my ZU did ( did not used it much for nav, mostly because of the limited battery life ).
So, my X2 is going to retire my ZU & HTC HD2 at the same time.

Benjiro said:
I know the feeling. Its one of those devices where you do not feel like your limited to x time on it, before you need to run to the charger.
Yesterday did about 30 min car ( 2 * 15 min ) navi with the car usb charger connected. The battery was at 62% before ( did some charging at work using the pc's usb port ) and it was 71% after i arrived home. The problem i have is, was it connected to the 2Amp port or the 1Amp ( its one of those Chinese dual usb ports mini chargers with no description: "what is what" *lol* ).
So still need to figure out if it was charging up on 1 Amps or 2 Amps ( to give me a idea of the power consumption while navigating ). The fact that it charged up while navigating is always a plus.
My old HTC HD2 had the habit of slowly draining while driving with the usb charger connected. Do not remember what my ZU did ( did not used it much for nav, mostly because of the limited battery life ).
So, my X2 is going to retire my ZU & HTC HD2 at the same time.
Click to expand...
Click to collapse
My X2 retired every phone I had including the Note 4 and Nexus 6. A seller on ebay is selling our Gold 32gb X2 for $409.99. I may pick up another one to have an extra.

AMOLED burn-in solution and question

OLED displays gets burn-in almost exclusively in places where there are a lot of elements that stay completely white all the time. Most notoriously, status bar and navbar. For some people who text a lot, I have seen burn-in for the call and video call buttons, as well as individual keyboard letters.
My question is, is there an app, or a theming engine to be precise, that would allow the user to set a time interval, during which those high persistence elements of the picture could be dimmed over time? For example, user unlocks the phone and starts typing a message - navbar, statusbar, keyboard letters are all 100% white. They remain white, then after 60 seconds they start to dim, and after 120 seconds they are at 30% brightness. So when you're having long texting sessions, keys would be dim enough so you can make them out, but since they are not leaving your muscle memory you can type just as well as if it was at 100% brightness - but you save a lot of energy and thus substantially reduce the potential for burn-in. And if you're outdoors and can't make out what the time is after those 180 seconds, you gently pull down the notification bar and it resets to 100%. Something like that.
I can't be the first person to think of this. Moreover, I think AOSP devs realized this at around version 9 and dropped the overall brightness of the status/navbar to 80%, but it remains like that the whole time. What I am proposing would be infinitely more efficient. Anyone here knows something that's able to do that?

Avoid use in direct sunlight. Seconds not minutes if you do. Use manual brightness control and keep below 50%. Typically I comfortable use 30-40% indoors. Excessive brightness prematurely kills AMOLED displays needlessly. Excessive heat with the display on ie again direct sunlight should be avoided.
Use dark mode. The red pixels are longest live, blue the shortest; heavy blue or white usage will degrade the display the fastest.
Use icon packs and layouts that support pixel conservation. Rotate widgets and icons periodically.
This heavily use N10+ has over 8k hours on its display. There is no detectable fading, failed pixels, color inaccuracies, nothing; it remains perfect. It's a mirror image next to my new N10+ with less then 50 hours on it.
AMOLED displays can be very long lived. Everything on this homepage gets rotated slightly from time to time, even the page number icons ie 3 instead of 2.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

johnnyboy041 said:
OLED displays gets burn-in almost exclusively in places where there are a lot of elements that stay completely white all the time. Most notoriously, status bar and navbar. For some people who text a lot, I have seen burn-in for the call and video call buttons, as well as individual keyboard letters.
My question is, is there an app, or a theming engine to be precise, that would allow the user to set a time interval, during which those high persistence elements of the picture could be dimmed over time? For example, user unlocks the phone and starts typing a message - navbar, statusbar, keyboard letters are all 100% white. They remain white, then after 60 seconds they start to dim, and after 120 seconds they are at 30% brightness. So when you're having long texting sessions, keys would be dim enough so you can make them out, but since they are not leaving your muscle memory you can type just as well as if it was at 100% brightness - but you save a lot of energy and thus substantially reduce the potential for burn-in. And if you're outdoors and can't make out what the time is after those 180 seconds, you gently pull down the notification bar and it resets to 100%. Something like that.
I can't be the first person to think of this. Moreover, I think AOSP devs realized this at around version 9 and dropped the overall brightness of the status/navbar to 80%, but it remains like that the whole time. What I am proposing would be infinitely more efficient. Anyone here knows something that's able to do tha
blackhawk said:
Avoid use in direct sunlight. Seconds not minutes if you do. Use manual brightness control and keep below 50%. Typically I comfortable use 30-40% indoors. Excessive brightness prematurely kills AMOLED displays needlessly. Excessive heat with the display on ie again direct sunlight should be avoided.
Use dark mode. The red pixels are longest live, blue the shortest; heavy blue or white usage will degrade the display the fastest.
Use icon packs and layouts that support pixel conservation. Rotate widgets and icons periodically.
This heavily use N10+ has over 8k hours on its display. There is no detectable fading, failed pixels, color inaccuracies, nothing; it remains perfect. It's a mirror image next to my new N10+ with less then 50 hours on it.
AMOLED displays can be very long lived. Everything on this homepage gets rotated slightly from time to time, even the page number icons ie 3 instead of 2.
View attachment 5721937
Click to expand...
Click to collapse
johnnyboy041 said:
OLED displays gets burn-in almost exclusively in places where there are a lot of elements that stay completely white all the time. Most notoriously, status bar and navbar. For some people who text a lot, I have seen burn-in for the call and video call buttons, as well as individual keyboard letters.
My question is, is there an app, or a theming engine to be precise, that would allow the user to set a time interval, during which those high persistence elements of the picture could be dimmed over time? For example, user unlocks the phone and starts typing a message - navbar, statusbar, keyboard letters are all 100% white. They remain white, then after 60 seconds they start to dim, and after 120 seconds they are at 30% brightness. So when you're having long texting sessions, keys would be dim enough so you can make them out, but since they are not leaving your muscle memory you can type just as well as if it was at 100% brightness - but you save a lot of energy and thus substantially reduce the potential for burn-in. And if you're outdoors and can't make out what the time is after those 180 seconds, you gently pull down the notification bar and it resets to 100%. Something like that.
I can't be the first person to think of this. Moreover, I think AOSP devs realized this at around version 9 and dropped the overall brightness of the status/navbar to 80%, but it remains like that the whole time. What I am proposing would be infinitely more efficient. Anyone here knows something that's able to do that?
Click to expand...
Click to collapse
I think you could look into immersive mode, It has many different names Another option talk in developer forums fr your phone , otherwise its hidden somwhere in your settings
Click to expand...
Click to collapse

Galaxy store>Good Lock family of apps>Quickstar

Is there a way to prevent burn in when using the phone in a bright environment? My job requires a bright environment.

Fytdyh said:
Is there a way to prevent burn in when using the phone in a bright environment? My job requires a bright environment.
Click to expand...
Click to collapse
No other than the mods I already mentioned. AMOLEDs have a finite lifespan that's proportionately shorter or longer dependant on brightness level. The brightest stars burn the fastest...
All you can do in that case is use at minimum needed viewing brightness and try to use in shaded areas.
Maybe use a work phone so you don't burn up your personal phone.

I am under the impression that none of you even read what I asked in full. I asked a very precise question regarding a particular way to mitigate burn in, nothing on HOW to to mitigate it, as I hinted in the name of this thread.
1. "Avoid use in direct sunlight." Excuse me? Phones are meant to be used outdoors, and they have been since the birth of the idea of a mobile phone.
2. I don't have a Samsung phone. What I meant was something more universal, like a Magisk module, or a root theme engine.
3. With due respect sir, everything you mentioned is more of a paranoid hassle than an automated instant-fix. What I proposed, on the other hand, is.

johnnyboy041 said:
I am under the impression that none of you even read what I asked in full. I asked a very precise question regarding a particular way to mitigate burn in, nothing on HOW to to mitigate it, as I hinted in the name of this thread.
1. "Avoid use in direct sunlight." Excuse me? Phones are meant to be used outdoors, and they have been since the birth of the idea of a mobile phone.
2. I don't have a Samsung phone. What I meant was something more universal, like a Magisk module, or a root theme engine.
3. With due respect sir, everything you mentioned is more of a paranoid hassle than an automated instant-fix. What I proposed, on the other hand, is.
Click to expand...
Click to collapse
Welcome to the planet. The more you run it in direct sunlight the higher the risks including outright failure. That sound better?
This isn't a backlight LCD* or a LED display. OLEDs are less robust than LEDs.
Due respect my mass... prudence isn't paranoia.
8+k hours here and no detectable damage of any kind.
* direct sunlight can fry LCDs too.

blackhawk said:
Welcome to the planet. The more you run it in direct sunlight the higher the risks including outright failure. That sound better?
This isn't a backlight LCD* or a LED display. OLEDs are less robust than LEDs.
Due respect my mass... prudence isn't paranoia.
8+k hours here and no detectable damage of any kind.
* direct sunlight can fry LCDs too.
Click to expand...
Click to collapse
Dude, nobody sets their phones to sunbathe for no reason. If the situation requires me, I'm using it the open sun. That hasn't damaged any OLED screen I used in the past 10 years. You ain't gonna convince anyone to rearrange widgets every week giving a meteor strike argument, especially with that attitude. Now please, are we over useless internet forum fights? I'm not negating any technical point you made, and what you did is certainly a way to deal with the issue, but it is objectively not practical for 99% of users.