Related
i noticed battery level feedback in my x1 is just in 10% steps. (shown with homescreen). is this normal? other htc devices are more precise...
DocMAX said:
i noticed battery level feedback in my x1 is just in 10% steps. (shown with homescreen). is this normal? other htc devices are more precise...
Click to expand...
Click to collapse
Yes, I notice that also after putting in the percentage icons for the battery meter.
Probably SE purposely design it to be like that.
is there a registry hack?
Would like to have precise indicator too, 10% steps are bit ugly. With 1% steps you can figure actual consumption and extimated battery time quite well...
No hack yet?
X1 can only show battery life with 10% precision? even 3rd party Battery meters display in 10% steps. Can not think of any advantage of such a primitive feature design. Hack or a workaround would be much appreciated.
would be happy to be proven wrong, but the source that provides the status of the battery life is an OEM driver that is device-specific, Microsoft only provides the API to access the source. So there's no way you can hack unless you write a new power management driver for X1.
The thing with LiPo batteries is, that the nominal voltage is 3.6 [V] and the minimum voltage is 2.5 [V] (below this, the battery will be damaged).
So the usable voltage range are 1.1 [V]. The device has to measure the voltage to show the battery level. Due to the tolerances and mesurement deviations it is hard, if not impossible, to measure more exact than 1/10th [V].
SonyEricsson therefore shows a realistic value of the battery level whereas devices that show more exact values simply lie.
I was just wondering about the whole deal with wiping the battery stats. To me it seems as if the point of this is strictly to get the OS to report and understand the battery more so than anything to do with the battery itself. I mean, the OS can't actually change the physics of the battery, right?
But the OS needs to understand what a full charge is and what an empty charge is, so that it knows when to shut down and when to stop charging and all that sort of stuff.
What I'm thinking is that if you wipe the stats and it's not at 100%, it will think that the discharge from that point to an actual low level is the full breadth of charging and adjust accordingly.
Is any of this remotely accurate? Or am I just making wild assertions?
Actually...it's the software that can make or break battery life...take for example background notifications. Wifi uses battery power and if you have different programs all polling for updates at x amount of times per hour..even when asleep..it will eat up battery juice...another example is the cm bug that kept the speaker on all the time and the nook never really went to sleep...it used tremendous amount of juice for not doing anything...another example..screen brightness..does not the software control how dim or bright you want it...and say you could not adjust the settings..your right..a battery is just a battery but how the kernel, drivers and loaded programs determine how fast or slow the battery power is to be used. Clearing the stats gives more accurate measurements for the kernel and hence will power down(power saver mode ) or other items for the kernel depending on what type of governor is on the nook..software wise.
I think you misunderstood what I was saying. What I'm trying to say is that the OS can't change the physics of the battery. Drain is drain, no matter what software is running. In other words, say you have two perfectly identical systems, both running the exact same software. The battery capacity is exactly the same on both and they both have the same drain. The battery doesn't actually drain faster on one vs the other, but the OS can *think* it's draining faster. That's why we have all these battery stats and such...right? Or am I wrong?
Oh Ok...you are right in the fact that it cannot and the software..depending on what it's state(charge level) is will determine how to run..it just makes it more accurate.
Wiping the Battery Stats tells the OS to start learning what the new High and Low are.
It doesn't matter what level of charge the battery has when you do this....
- As the battery gets lower the stat keeps updating the level as the new low.
- As you charge the battery it continuously updates the stat as the new High.
Once you have taken the battery to both of these extremes then, in theory, the OS will have accurate info on your battery.
At a certain point in time the battery stats stop updating which is exactly why it is important to do this.
So I have this terrible drops from X -> 50% and X-> 20% (yes, I am aware of "battery drops explained" topic) and I was thinking if I could get around this false battery percentage display like this:
Let's say I will charge battery to 100%, turn on airplane mode, turn off every data/wifi etc. and just leave it for day or two until it is almost decharged. Then I will take a screenshot of battery usage graph and I make a straight diagonal line through it and see how I would like the percentage to be displayed instead of the real one.
I am not sure if I explained it good enough, but here's the example screenshot for you:
i(dot)imgur(dot)com/QEwJPeA.png
If we could someone force the phone (through apk or some kind of script) to show us te percentage like in the screen above we could AT LEAST have some better battery charge representation and some better knowledge about how much charge is really left. Even with 10% steps.
So to sum up:
1) Realize how your battery is behaving, dropping etc., take your version of battery graph
2) Create 'checkpoints' like in screenshot above and tell some application or script to show you the percentage like described in the screenshot as well
3) We can't get rid of drops on old batteries, so maybe at least we could earn some better % representation
PS.
I found a script that could be useful in my idea:
tutorialforandroid(dot)com/2009/01/getting-battery-information-on-android.html
I thought this was important enough to move out of the Volume Control--USB Audio thread as it contains some information which runs counter to prevailing beliefs and suggests a way to test these beliefs.
This report is the result of my struggles to figure out the power drain issue with Phone.apk since I discovered that enabling it restores the volume "button" control over Media volume. Be prepared to be surprised. I was.
If you search online for issues with the generic "phone.apk" and battery consumption you will see the same drum beat over and over. Nearly everyone is convinced that the app is eating up their battery (even when they don't actually have a phone). They cite the battery usage stats which show the "cell standby" process (whatever that is) eating up huge percentages of the battery life. They also (mostly) cite a marked increase in battery life (and a disappearance of the "cell standby") when the app is deleted or disabled. Some also claim that simply changing to "airplane mode" kills the "cell standby" process.
It's difficult to argue with someone's personal experience, but there are a few voices amidst the clamor which say something more or less like this:
The problem is that the statusbar in the systemUI process actually reports the status of cellular radio to the battery stats service. It apparently does know that there isn't a *connected* radio, and then incorrectly assumes there is an *unconnected* radio which would be consuming battery searching for a signal (if it existed!). So it is just reporting time to the service, and it is sending that number through some formula that computes battery usage and displays it.
I assure you (as someone who is a programmer, but more relevantly has common sense) that a nonexistent cellular radio is NOT consuming your tablet's battery. It is simply a stat reporting error.
Click to expand...
Click to collapse
But, you know, it is a well-established fact that disabling Phone.apk improves battery life. I don't claim to know very much about the Android operating system but as I've delved into this issue one thing has occurred to me that seems completely illogical. I don't understand all of what happens when a device is rooted, but I doubt that a whole bunch of system apps that were somehow disabled before rooting are suddenly enabled during rooting. So before the NST is rooted, surely the underlying Android 2.1 system is chugging along and none of the apps present is actually disabled. Why then, does Phone.apk suddenly become a current hog only when the device is rooted?
So my quest took me down the rabbit hole in an attempt to disable all functions of Phone.apk except the desired ability to control the media volume. This led me to track down obscure settings menus (for the curious geek: AnyCut in the PlayStore--be careful, some settings will cause a reboot), alter the settings.db file (the only place that seems to have any say about "airplane mode"). Would you have imagined that Phone.apk has data roaming set as default "on"? Ever wonder why Phone.apk never appears when enabled? Turns out it has a dependency on Contacts.apk which is absent from the NST. Anyway it was all for naught. By the time I was finished my NST was leaking power like a sieve even without Phone.apk re-enabled.
Fortunately I had an old backup from December and didn't have to restore too much. Back to square one and more reading. It eventually occurred to me that the Nook Color had been the source of some of the audio work, so I visited that forum. Didn't find anything. Of course the Nook Color has native audio capabilities. But I did find a long thread in which proponents and opponents "discussed" Phone.apk and its possible effect on battery drain. That and member @HotShotAzn (his research is here) led me to SystemPanel. The paid version allows you to monitor the system for as long as a week at a time and follow things like CPU usage, power consumption, what's running, etc. If you're interested in SystemPanel for yourself, there's an extensive overview of it here.
Lies, D*mned Lies, and Statistics
Before I lay out the data from my experiments, let me just disclaim the whole thing right now so that anyone with a different experience can still feel validated. I don't claim this study is definitive. To do it right, I should have restored my NST to stock, rooted and then compared power consumption with and without Phone.apk. I judged that as too tiresome although the backup capability of NookManager really would have made it rather easy.
My system: I am running rooted stock 1.21 with the most recently amended kernal that includes gussied up audio but I note here that the audio implementation in that kernal is not quite complete, being a few details shy of enabling full mic capabilities. I filled those in myself. I use NoFrills CPU governor to regulate the CPU between 300 MHz and 1 GHz, on demand. I run Tasker in the background for a number of things, principally to autostart/stop WiFi for those apps that need it, and to control/lock rotation on some apps. There's a lot of little stuff that fritters away a little CPU time in the background, like the BBC News, TuneIn Radio, etc. I also have all the B&N stuff going except for NookCommunity and Social, both of which I consider nagware.
Day 1-2: No Phone.apk
I fully charged my NST before retiring and let it do its thing overnight. It was down to 99% the next morning. I read lightly during that day and the next, but did nothing else with the device. You can see the power drop-off in section 1 of the first image below. Pretty good.
These are the basic stats from those two days:
Remaining charge: 92%
Active:
ADW
Home
Library
Reader
SystemPanel
Service-only processes
CloudService
com.bn.nook.affileddownloadservice
DeviceManagerService
Market
News and Weather
Settings
Tasker
TestCenterService
USB Audio
USB Host
WaveformDownloaderService
Inactive (cached) apps
AdAway
Email
Maps
Pandora
Shop
thumbnailservice
TuneInRadio
Internal System Processes
Android keyboard
android.process.acore
android.process.media
com.bn.cloud.svc:svc
com.google.process.gapps
system
Top apps
System Processes
system
SystemPanel
Days 3-4: Volume control "kludge"
I fully charged the NST before retiring and also briefly ran the USB Audio toggle app so I could use ES Task Manager to wake up the volume control as described here. Then I left the NST to sleep.
The next two days I read lightly as before, nothing more. I was shocked at the power drop-off as seen in section 2 of the first image below.
These are the basic stats from those two days:
Remaining charge: 50%
Active:
ADW
Home
Library
Reader
SystemPanel
Service-only processes
CloudService
com.bn.nook.affileddownloadservice
DeviceManagerService
Market
News and Weather
Settings
Tasker
TestCenterService
USB Host
WaveformDownloaderService
Inactive (cached) apps
AdAway
Email
Maps
Pandora
Screenshot Easy
Internal System Processes
Android keyboard
android.process.media
com.bn.cloud.svc:svc
com.google.process.gapps
system
Top apps
system
TestCenterService
SystemPanel
You can see from the plot that the discharge rate and CPU usage are both elevated for that two-day period. The Top Apps have also changed. "system" has moved up and TestCenterService has made the top three (the list is much longer). I more deeply investigated both of these and, sure enough, the increased CPU activity comes mainly from "system" (which I believe is the underlying Linux, as opposed to "System") and to a smaller extent, TestCenterService (com.bn.serviceone). What exactly is going on when the volume control kludge has been executed is anyone's guess, but it's clear that the result and any side effects continue to propagate through the CPU until a reboot, even when USB Audio is not in use.
I couldn't believe this result so after wrapping up all my tests today I disabled Phone.apk again, rebooted and set up the volume control kludge using ES Task Manager. Immediately the undercurrent of increased CPU usage showed up in the real-time stats from SystemPanel. So whatever volume control strategy you choose, it probably should not be this one.
Days 5-6: Phone.apk enabled
After enabling Phone.apk I rebooted (cancels effect of kludge), fully charged, and left the NST to sleep overnight. The next morning, I was down to 98% battery. So far so good.
I read for the next two days, as before, although perhaps a little more heavily since I got into a good mystery You can see the power drop-off in section 3 of the first image below. It's very similar to the first two days without Phone.apk enabled, and certainly MUCH better than that of days 3 & 4.
These are the basic stats from those two days:
Remaining charge: 91%
Active:
ADW
Home
Library
Reader
SystemPanel
Service-only processes
com.bn.nook.affileddownloadservice
DeviceManagerService
Market
News and Weather
Set Cover
Settings
Tasker
TestCenterService
USB Audio
USB Host
WaveformDownloaderService
Inactive (cached) apps
AdAway
Email
ES Task Manager
Google Partner Setup
Maps
No Frills CPU Control
Pandora
TuneIn Radio
WiFi File Transfer
Internal System Processes
Android keyboard
android.process.acore
android.process.media
com.bn.cloud.svc:svc
com.google.process.gapps
Dialer
system
Top apps
system
System Processes
SystemPanel
There's some jockeying for place among the various apps and services, but the bottom line (or rather the top one in this case) is that the remaining charge after two days is essentially the same as without Phone.apk running.
Of course there is no mention of the mysterious "cell standby" in all of these stats. You'll notice that the Dialer shows up low on the list of Internal System Processes. For the curious I called up the details on that. They are in the second image below. Clearly, enabling Phone.apk has nothing to do with battery life on my NST. But it does give me full volume control without any silly kludge that can't be explained and actually consumes even more juice. And now that I'm done with my experiments I don't need the SystemPanel monitor on so that will save a little more juice
YMMV.
I've found that the free GSam Battery monitor is very useful for tracking down apps that drain the nook. http://bit.ly/1Xclacj . I found two apps that I had installed that were trying to call home and draining my battery.
After upgrading to Oxygen 11 i do feel there's battery drain.
Tried to factory reset + Cache Wipe but still same.
Put display on 60Hz & FHD+ but no go..
GUARDIANBD said:
After upgrading to Oxygen 11 i do feel there's battery drain.
Tried to factory reset + Cache Wipe but still same.
Put display on 60Hz & FHD+ but no go..
Click to expand...
Click to collapse
what are the top drainers when you go to :
1) settings
2) battery
3) press on the ellipse ( three vertical dots ) in the upper right corner and choose 'battery usage'.
. . . for me, my largest app usage is aodNodify at a whopping 20 percent, followed by messages.
4) press on the ellipse again and choose 'Show full device usage'.
. . . for me it's Screen at 20 percent, and then Wi-Fi at 11 percent.
(hth)
GUARDIANBD said:
After upgrading to Oxygen 11 i do feel there's battery drain.
Tried to factory reset + Cache Wipe but still same.
Put display on 60Hz & FHD+ but no go..
Click to expand...
Click to collapse
I get 10 hours with 120hz and FHD so no need to disable that.
Tbh besides what @old_fart said the main killers are
5G
Facebook
Not wiping after a major system upgrade ie; 10 to 11
Poor kernel
Misbehaving Google play services
AOD (looks great, kills battery)
Charging overnight (eventually this will murder your battery)
Gaming
Video calling
Misbehaving rogue app.
Misbehaving launcher.
Ads ( block them all)
You get the picture, I've compiled a large list of problems and suggested alternatives in the review section of this forum, can't remember which one but a lot of good tips are in there, give them a look.
Attached Battery status.
The Os was cleaned after the upgrade to Os 11.
AOD - is switched off.
5G - Not working anyway.. disabled.
GUARDIANBD said:
Attached Battery status.
The Os was cleaned after the upgrade to Os 11.
AOD - is switched off.
5G - Not working anyway.. disabled.
Click to expand...
Click to collapse
Good to all that.
Are you on stock OS or any kernels installed? Magisk ROMs?
It's possible if your phones just been set up that it may be backing up/ syncing Google photos.
Go through your apps and make sure that there set up optimise instead of intelligent control.
Facebook is always a killer, maybe use the browser version it's not much different, personally I'd delete the account and every bit of info in it, hate Facebook
I would say OOS11 drains more battery than OOS10. I game a lot and my battery lasted longer on OOS10.
firephoenixctk said:
I would say OOS11 drains more battery than OOS10. I game a lot and my battery lasted longer on OOS10.
Click to expand...
Click to collapse
Depends on the game for me.
Emulation is a good test and it runs about the same for me.
I have tweaked my CPU thresholds though.
So there is no difference in up or down actions or peak speeds, all of which i reduce
Im using stock rom my SOT is about 5-6hrs tops and i keep seeing people with 10+ SOT with stock rom..
Might be faulty phone? what's you're settings and configs?
dladz said:
I get 10 hours with 120hz and FHD so no need to disable that.
Tbh besides what @old_fart said the main killers are
5G
Facebook
Not wiping after a major system upgrade ie; 10 to 11
Poor kernel
Misbehaving Google play services
AOD (looks great, kills battery)
Charging overnight (eventually this will murder your battery)
Gaming
Video calling
Misbehaving rogue app.
Misbehaving launcher.
Ads ( block them all)
You get the picture, I've compiled a large list of problems and suggested alternatives in the review section of this forum, can't remember which one but a lot of good tips are in there, give them a look.
Click to expand...
Click to collapse
Are you using stock rom? or custom one?
GUARDIANBD said:
Are you using stock rom? or custom one?
Click to expand...
Click to collapse
Stock mate.
I've used some magisk ROMs then I realised I can actually make the changes I want to myself.
I've used CRDroid and PE but I missed the OOS camera, battery was very similar to what i have in OOS but gaming does burn the candle a lot faster
Here's that list I made in the standby drain the in the review section, I made it a while back so some may no longer apply
"Change 5G to 4G
Remove Facebook use web based
Remove Facebook messenger use web based
Remove Twitter use web based
Remove any ad based apps pay for the pro version
Turn off gestures like lift to wake
Change from QHD to FHD (No difference)
Allow auto brightness
Turn off WiFi overnight
Turn all updates to manual not auto (play store)
Remove any so you don't use
Change back up to once a month (WhatsApp)
Turn off location history (Google)
Use titanium to remove any system apps you don't need
Don't allow anonymous usage statistics for any app ever.
Don't allow tracking cookies on any website
Use adaway (root needed)
Don't open web pages in Google app (I use Samsung browser)
Don't use xposed.
If you game you will not get high SOT scores, period.
Don't bother with battery saving apps or monitoring apps.
Streamline your apps, if you don't use it, remove it.
Don't allow WiFi scanning (as in letting other apps use it when it's not on)
Never allow personalised ads.
Never allow notifications from websites
Always decline cookies unless your absolutely have to allow some tracking (common sense prevails here)
Optimise as many apps as possible unless it affects performance.
Don't allow apps to remain open in the notification area.
Change your launcher, my preferred launcher is lawn chair and this did actually burn up some battery when compared to the OnePlus launcher.
Don't use live widgets (yes they look cool, but they annihilate your battery)
Live wallpaper, again very cool, but battery burners.
Again! Don't charge overnight, make a note of your percentage then see what it is in the morning, you shouldn't be losing more than 5% really, if you've done well then it'll be reflected here, the good SOT results will follow.
Turn off live read outs of network speed, RAM usage in the status bar.
Turn off NFC unless in use.
Leave location on in quick settings.
Don't overcharge your phone, IE: overnight
Don't allow your phone to fully deplete the battery.
Whatever anyone says, this does 100% damage batteries, there is no argument here and I won't entertain anyone who says otherwise, Ive seen through real life tests what this results in, bloated, inefficient, possibly dangerous lithium batteries.
Keep your phone out the sun.
Keep it out of extreme cold.
Keep your device clean dust free.
Snapchat, Viber, house party, apps like that tends to use more battery as they don't have great dormancy periods.
Apps like speed test by Ookla tend to have location tracking, similarly they tend to turn themselves on and off when they feel like it, my advice, install test and uninstall.
Allow a couple of battery cycles between tweaking sets, to give you an idea of how much of a difference you've made.
Use BBS to see what is being used, once you've removed problems, remove BBS.
I've just written this from the top of my head so o probably missed some things, the general idea is to keep your device clean and fresh, remove files you don't need any more.
Keep an eye on apps that misbehave or aren't wanted, index your folders so they aren't a mess
The more good things you do means the more potentially bad apps you can have on your phone, eg if you really need Facebook, you could keep it so long as you clean up other areas of your phone"
Good luck
Based on some years of experience i would add to this amazing and great list:
- Only use either wi-fi or 3g/4G/5g at a time. Alternate between them. ( ex. leave home - off wifi - on 4G, arrive home - off 4G - on Wi-Fi ) Don't use both on all day long. Battery will drain.
- Use sync off ( Playstore (mentioned above) and "sync app data" ). Only turn on when you want the phone to update and shut if off after.
Disabled some weird facebook management apps and it looks a bit better, currently 25hr's with no charge, 68% battery left and 1:48hr's of SOT.
Will test it for few days and update.
Not the most apps used today but still heading for 10 hours.
Lot of painful lost bets today.
Well, my battery now lasts longer on idle, but SOT while using it is still 6hrs
Some other guys from Facebook groups shows about 10hr's of SOT with QHD + 120HZ..
GUARDIANBD said:
Well, my battery now lasts longer on idle, but SOT while using it is still 6hrs
Some other guys from Facebook groups shows about 10hr's of SOT with QHD + 120HZ..
Click to expand...
Click to collapse
Not sure I can believe that tbh, QHD just kills the battery
GUARDIANBD said:
After upgrading to Oxygen 11 i do feel there's battery drain.
Tried to factory reset + Cache Wipe but still same.
Put display on 60Hz & FHD+ but no go..
Click to expand...
Click to collapse
drain oneplus 8 pro
for thoose who have drain battery issues this can be the problem
forum.xda-developers.com