Related
So, for a long time reading the forum and asking a question along the way, why I have so quickly battery discharging on my phone, I came across an interesting thought: "and from what I actually compare?. someone wrote about 5% per night, someone love to confess on the tab "Journal of the battery and it shows that he is the difference between" running "and"phone on "0.5%. but what is a night (for me it's 8 hours for someone 5). which network who have (GSM or 3G)? Also, we are constantly being developed and modified ROMs and kernels, which also constantly featured the words "lowered energy consumption."
And how do you actually compared the energy consumption of the old firmware to new. usually it sounds like "on the old firmware, I charge the phone every day, and now I charge every 2 days." but we don’t know details of how actively you used options of your phone on the old version, and how use now "(for me, For example the first 3 weeks after buying the phone had lived only one days, but now 2-3 days. but not because the new firmware, but because I'm tired of constantly digging through the phone settings and install the different soft, thus discharging it).
So, our challenge is to develop an algorithm (and in the future opportunities programs), as can be correctly and objectively compare the power consumption of our devices. That at least from the transition to the firmware to the firmware, from one kernels to another to be sure that the phone will not live less than before. Search for programs of this kind I have not been successful, can someone tell me if he knows?
actually look to you for ideas, how best to develop an algorithm testing the phone, and simultaneously bring your own.
then everything will be set out with respect to the software part, because hardware is not subject to us
1. So, first of all we need to start with any initial data. Having read all the threads about power consumption, I have come to the conclusion that the original data should include the following:
- Do wipe battery stat. We fully discharge the phone till shutdown and charge it in off state. after the device is fully charged, unplug it from the charging device and do wipe batter stat from the recovery menu
- To make the calibration of the battery you need to discharge and completely charge in turned off state the device at least 3 times
Here is one of the toughest parts, considering the long battery charging our phones. charging off-state means 4 hours of losing connection. and we need to do it 4 times. One discharge-charge cycle for a complete calibration system, as I understood , is not enough.
all the widgets and programs that can perform any action to in background must be disabled.
well, and then discharges our apparatus up to 95% in quiet mode, to give the battery a little bit cool, and eliminate trouble with 99-98-97% and you can begin testing.
2. Measurement tool. I would have chosen for this purpose, program or Battery Monitor Widget (she effects on discharging battery, but it writes logs, which can be tracked over time the battery status in percentage and millivolts) or JuicePlotter (don’t have logs. We have to extract data from the graphs that it constructs). JuicePlotter showed the best result in power consumption while the CPU time drain more than BatteryMonitorWidget - here's the first interesting fact. Now I’m testing these programs repeatedly to confirm this effect
3. In order to reduce measurement error the device must be discharged at least 20% of one test. or better at 30%. then + / -1% in the testing will not be particularly significant. That why testing process will be long and tedious.
4. In order to understand the power consumption of device in general, you should at least try to understand and share the power consumption of its individual components:
5. power consumption of the screen. For this purpose you can use the widget to extend controls, where you can turn the screen on constantly. And choose any standard wallpaper with middle brightness. we need to measure how much battery discharging for 3 hours the screen on. for small, medium and very high brightness, respectively. you can check consumption on the automatic brightness too. is believed that the turning on an automatic brightness strongly discharge the device..
6. power consumption of the file system. In the good we ought to write a program that creates a file in a loop on the internal flash drive, and anything he writes and deletes the file. Repeat the loop few thousand times to the total time was about 2-3 hours. but until there is no such a program, you can simply copy the file size of 2-3 gigabytes of internal memory with a program such as ES Explorer. In this case, the screen must be enabled to minimum brightness (since we already know how much the phone is discharged from simply turn on the screen) to control the copy process and accordingly the percentage of discharge.
7. Estimation of consumption of the processor. To do this, too, we can write a program that would do any arithmetic operations within an hour of time. But here we get the maximum load, therefore the maximum power of the processor. and it is unlikely it will be different from the firmware to the firmware . But our processor is also able to reduce the frequency and consequently reduce power consumption. And here I think there is much to improve the software. Therefore, must be differences from firmware to firmware. And the best test for this, I think, show any video on device, it loads processor to 30% on average (better view a videoconcert, so there isn’t quite boring) for one hour and thus measure how much discharge our batteries from this view .
8. Estimation of Wi-fi. Then the test can serve up any file copy from PC (connected through wires to an access point, so this segment was not the brakes) to our unit. Since the maximum speed that I managed to squeeze out of the standard N on my Captivate is 0,8 MB / sec I think copying the file size of 2GB will be enough to discharge our device is not less than 20% battery. copy can be perform using the same ES Explorer
9. Rated power consumption in standby mode. here it must enable the network only GSM. turn off the wi-fi and bluetooth. the screen went off and did not touch the machine for 8 hours. Better course would be 24 hours, but I think hardly anyone will be able to perform such a test
Actually look to you for your suggestions and additions, as can be realized by comparing energy consumption of our devices.
from the general collective thoughts we can open thread with algorithm, where you can write your test results according to the algorithm ... and make any conclusions.
Hello,
my battery only lasts half a day max, before needing a recharge. I've already tried different custom roms, and currently I'm on Blisspop for android 5.1. The area I live in has good coverage, so that shouldn't be the culprit. I never play games on my device, but even basic web browsing drains my battery very rapidly. I do use android wear, but I don't think that is the reason I only get around 1 hour of screen on time.
Here are the things I've tried already:
- Turning off location reporting
- Disabling Google Now
- Removing Google Fit
- 'recalibrating' the battery by letting it discharge and then charge it fully without unplugging
- Using 3g instead of 4g
- Turning off location access
This is driving me nuts, and I don't know if it's my battery's fault or my phone's fault.
Thanks in advance.
Go to wifi, special, and disable scanning when the wifi is off. It helps A LOT. Also keep location reporting off, as setting it to network only creates tons of wakelocks even when mobile data and wifi are turned off.
I know some custom ROMS have had issues with Bluetooth battery drain in the past. Try turning it off and see what happens.
Turn down the brightness as well. There is significant difference in power usage between %50 and %100 brightness .
Hold power button and select power off. Helps
G'day,
I've had some odd issues with two consecutive Xiaomi phones, and I'm hoping someone here can shed some light on it for me.
With both my Mi Note 2, and now my current Mi Mix 3, after less than a year of owning each one (respectively), out of nowhere, the battery life drops through the floor, the phone gets really hot, and most oddly, I got wicked battery drop while the phone is off (e.g. I turned the phone completely off at 77%, and about an hour later, I turn the phone back on and it's at 43%).
On both phones, I've tried a factory reset, but it didn't work. It was, for all intents and purposes, fecked. At the moment, I'm waiting for the 15 day countdown for my Mi Mix 3 bootloader to be unlocked so I can try flashing the EU MiUI ROM and see if that helps, but that's still a hell of a long time to wait with a phone that idles at 50+° C and has a battery life of about 3 hours with minimal SoT.
I've installed BetterBatteryStats (using ADB to provide permissions), CPU-Z, CPU Monitor and Ampere to see if I could get some more information. I found a few things:
1. Somehow, with mobile data and WiFi enabled, the system was drawing SO MUCH power (reported by Ampere) that it literally wouldn't charge while plugged into a 2A wall port. It was drawing like 1300mA when it wasn't plugged in, and when it was, it was STILL drawing about 130mA, meaning no matter what, while the phone was on, I was losing battery.
2. BBS reported the biggest battery killer was under the 'Alarms' tab, caused by Android, which were "Intent: *job.delay*" and "Intent: *job.deadline*". I have literally no idea what these are, what's causing them, or how to stop it triggering.
3. I've done a full factory reset. The first hint that something was wrong was when I noticed that the phone wasn't charging when it was plugged in and turned on. I did the full factory reset, didn't help.
I'm currently running Global MiUI 11.0.4.0, Android 9.
Does anyone have any ideas? I haven't manually updated anything, I'm not particularly rough with the phone, but for two phones in a row, this has come straight out of nowhere. It's a shame, because the Mi Mix 3 has spoiled me with it's 100% screen real estate (no hole-punch, no teardrop for front camera), but I think my next phone is gonna go with something else.
Cheers.
Update: I've taken a squizz at the Google Battery Historian and basically, I have no feckin' idea.
The best I can get out of it is "Yep, something in the labyrinthine generic 'Android' system is causing it, but good luck narrowing it down or stopping it."
That being said, I've found that this Partial Wakelock is triggered fairly often (1-6 times per minute, give or take): IntentOp:.common.broadcast.BackgroundBroadcastReceiverSupport$GmsReceiverIntentOperation
I have no idea what the hell it is or does, and the only information I can find about it is from developers asking questions where it just happens to be part of their codebase, or a breakdown of how the WakeBlock app works.
It's getting woken up about every minute or so (usually more than once a minute). However, the wakelocks appear to be part of the core Google/Android systems that can't be individually disabled.
I'm still feckin' confused.
Overloke said:
Update: I've taken a squizz at the Google Battery Historian and basically, I have no feckin' idea.
The best I can get out of it is "Yep, something in the labyrinthine generic 'Android' system is causing it, but good luck narrowing it down or stopping it."
That being said, I've found that this Partial Wakelock is triggered fairly often (1-6 times per minute, give or take): IntentOp:.common.broadcast.BackgroundBroadcastReceiverSupport$GmsReceiverIntentOperation
I have no idea what the hell it is or does, and the only information I can find about it is from developers asking questions where it just happens to be part of their codebase, or a breakdown of how the WakeBlock app works.
It's getting woken up about every minute or so (usually more than once a minute). However, the wakelocks appear to be part of the core Google/Android systems that can't be individually disabled.
I'm still feckin' confused.
Click to expand...
Click to collapse
I think it's an issue with your network operator
XDRdaniel said:
I think it's an issue with your network operator
Click to expand...
Click to collapse
Any ideas as to how I'd further troubleshoot? I've gone into *#*#4636#*#* and changed the sort of signal it looks for, but it doesn't appear to have fixed anything.
In case anyone is interested, I've attached on of my Bugreports (from running adb bugreport), which can be viewed through Google Battery Historian.
I'm not saying there's a cash prize for anyone who can tell me what is happening and why, but I'm also not saying that there isn't.
So, I think we have our culprit (maybe).
I have attached several screenshots from a Battery Historian I took after having my phone on all day. The total phone on time was about 4-5 hours with, no joke, maybe 10 seconds of screen on time. Let's go through this absolute bullshittery together, shall we?
Battery - Full Time: The full length of time captured by the Battery Historian/bugreport command. It's in Zulu Time (GMT+0) and I'm in Australia (GMT+10), so the line starts going up at 5PM last night, which is more or less when I plugged it in to charge. You can see, while 'off', it took 16 hours to charge to 100%, and this was from a 'cold boot' (phone is completely dead), so it didn't have any information about what had been running, etc.
Battery - Discharge: The five or so hours time in which the entire battery discharged, starting from when I woke up in the morning and got ready for work. In the Screen row, you can see the small, three-to-four second windows throughout the day that I turned the phone on to check the battery. For almost the entirety of the time, the screen was off. You can see where the line next to Phone State goes from black to navy blue. This indicates that the phone has been put into Airplane Mode - you can see this is also where everything relating to network connectivity or mobile strength completely disappears. You can also see that App Processor Wakeup completely dies here - that means that actual installed apps (including GOOGLE_SERVICES and Xiaomi's preinstalled Facebook app stop sending commands to wake the CPU.
Battery - Cause: At least once a minute, usually more, two things fire that keep the CPU running - Abort:Wakeup IRQ detected during suspend: 999 msoc-delta and Abort:Wakeup IRQ detected during suspend: 663 qpnp_rtc_alarm. I have no feckin' idea what either of those are, and Googling results in either developer guides or threads that lead nowhere. If anyone knows what they are, for the love of God let me know.
Battery - Foreground Processes: While the phone was off, with every app closed, in Airplane Mode, we can see that there are still four apps that are somehow in the foreground: com.miui.mishare.connectivity (odd, since there's no connection), com.miui.securitycenter (which I tried disabling through ADB last night, and it stopped my phone from booting. Oops), com.miui.notification, and com.android.providers.contacts (which disappeared shortly after entering Airplane Mode).
Battery - Video: You can see here, for the ENTIRETY of the time that the phone was turned on, this odd Video row was enabled. There is no other information about it - what causes it, where it's coming from, what 'Video' means, anything.
Battery - 7 Second Slice: This is just a close-up of a seven-second period of time, wherein the above 999 msoc-delta and 663 qpnp_rtc_alarm kept the CPU running six times within 7 seconds. Not a lot on its own, perhaps, but over the course of hours, it clearly causes issues.
I've also attached the latest bugreport where I took these screenshots from if anyone wants to try and make sense of it.
--
This looks to me like an hardware issue more than anything, what is the idle state of the cpu?
Overloke said:
So, I think we have our culprit (maybe).
I have attached several screenshots from a Battery Historian I took after having my phone on all day. The total phone on time was about 4-5 hours with, no joke, maybe 10 seconds of screen on time. Let's go through this absolute bullshittery together, shall we?
Battery - Full Time: The full length of time captured by the Battery Historian/bugreport command. It's in Zulu Time (GMT+0) and I'm in Australia (GMT+10), so the line starts going up at 5PM last night, which is more or less when I plugged it in to charge. You can see, while 'off', it took 16 hours to charge to 100%, and this was from a 'cold boot' (phone is completely dead), so it didn't have any information about what had been running, etc.
Battery - Discharge: The five or so hours time in which the entire battery discharged, starting from when I woke up in the morning and got ready for work. In the Screen row, you can see the small, three-to-four second windows throughout the day that I turned the phone on to check the battery. For almost the entirety of the time, the screen was off. You can see where the line next to Phone State goes from black to navy blue. This indicates that the phone has been put into Airplane Mode - you can see this is also where everything relating to network connectivity or mobile strength completely disappears. You can also see that App Processor Wakeup completely dies here - that means that actual installed apps (including GOOGLE_SERVICES and Xiaomi's preinstalled Facebook app stop sending commands to wake the CPU.
Battery - Cause: At least once a minute, usually more, two things fire that keep the CPU running - Abort:Wakeup IRQ detected during suspend: 999 msoc-delta and Abort:Wakeup IRQ detected during suspend: 663 qpnp_rtc_alarm. I have no feckin' idea what either of those are, and Googling results in either developer guides or threads that lead nowhere. If anyone knows what they are, for the love of God let me know.
Battery - Foreground Processes: While the phone was off, with every app closed, in Airplane Mode, we can see that there are still four apps that are somehow in the foreground: com.miui.mishare.connectivity (odd, since there's no connection), com.miui.securitycenter (which I tried disabling through ADB last night, and it stopped my phone from booting. Oops), com.miui.notification, and com.android.providers.contacts (which disappeared shortly after entering Airplane Mode).
Battery - Video: You can see here, for the ENTIRETY of the time that the phone was turned on, this odd Video row was enabled. There is no other information about it - what causes it, where it's coming from, what 'Video' means, anything.
Battery - 7 Second Slice: This is just a close-up of a seven-second period of time, wherein the above 999 msoc-delta and 663 qpnp_rtc_alarm kept the CPU running six times within 7 seconds. Not a lot on its own, perhaps, but over the course of hours, it clearly causes issues.
I've also attached the latest bugreport where I took these screenshots from if anyone wants to try and make sense of it.
Click to expand...
Click to collapse
Same problem. Any solution?
I don't understand this feature at all. After reading this article http://www.xperiablog.net/2020/06/01/xperia-1-iis-hs-power-control-feature-bypasses-battery-charging-to-maximise-gaming-performance/ I thought it will allow me to play games for as long as I want without depleting the battery. I've tried charging with this feature turned on 2 times now, and both times the battery level was dropping., so where's that battery degradation reduction they write about?
Furthermore, H.S. power control supposedly prevents the battery from charging, but during both tests, Franko Kernel Manager was showing that the battery was charging, not in a usual way though. Speed was going back and forth between charging rapidly (as fast as 6000 mA) and charging slowly (as slow as 12 mA).
"Limits performance reduction and battery degradation caused by device overheating during charging. The battery doesn't get charged when this feature is on. Turn off this feature when charging". So you launch a game, go through the game enhancer's features, and see this confusing AF wording, which tells you the feature prevents overheating while charging and gaming, but at the same time tells you not to turn it on while charging and gaming.
I use this feature when navigating. I was happy that it's not only available for games. Worked well. At least battery level didn't changed after some hour drive. Didn't checked it with Franco kernel Manager.
You selected the App and the colored bar appeared when App was in use?
Undead_Son said:
I don't understand this feature at all. After reading this article http://www.xperiablog.net/2020/06/01/xperia-1-iis-hs-power-control-feature-bypasses-battery-charging-to-maximise-gaming-performance/ I thought it will allow me to play games for as long as I want without depleting the battery. I've tried charging with this feature turned on 2 times now, and both times the battery level was dropping., so where's that battery degradation reduction they write about?
Furthermore, H.S. power control supposedly prevents the battery from charging, but during both tests, Franko Kernel Manager was showing that the battery was charging, not in a usual way though. Speed was going back and forth between charging rapidly (as fast as 6000 mA) and charging slowly (as slow as 12 mA).
"Limits performance reduction and battery degradation caused by device overheating during charging. The battery doesn't get charged when this feature is on. Turn off this feature when charging". So you launch a game, go through the game enhancer's features, and see this confusing AF wording, which tells you the feature prevents overheating while charging and gaming, but at the same time tells you not to turn it on while charging and gaming.
Click to expand...
Click to collapse
Must be a bug, works fine on my phone though....try resetting the phone perhaps?
Phoost said:
I use this feature when navigating. I was happy that it's not only available for games. Worked well. At least battery level didn't changed after some hour drive. Didn't checked it with Franco kernel Manager.
You selected the App and the colored bar appeared when App was in use?
Click to expand...
Click to collapse
Yes, the enhancer works, just not exactly as advertised.
yekollu said:
Must be a bug, works fine on my phone though....try resetting the phone perhaps?
Click to expand...
Click to collapse
I've spent quite some time on customizing the phone, installing apps etc. so I'd rather not start all over again. Unless there won't be any custom ROMs for a very long time...
it is a bug. if you still have problem. or other people have a problem there a way to fix it without factory reset. if your phone running android 12 or android 11. BUT not lasted firmware(of the android version.). try to download lasted version of Game enhancer(i recommended version 7.x.x instead version 8.x.x, because it more stable on 7, but if you rooted or can install subsystem apk, you can go with lasted version and i more recommended to do so to get more feature), subsystem and monitor apk from apkmirror, dont worry all app have same Game enhancer logo. if you have android lasted android 11 or android 12 firmware, only download Game enhancer and monitor app, as subsystem has been set to persistent app. and cannot be updated. if you are rooted download all app i mention and install as system app then reset your phone. im using xperia 1 ii with version 7.0.A.1.20 game enchaner as my original version came with my firmware have bug and H.S does not work as intended. whoever updated it does fix the problem(you can see with most battery monitor app that charging switch from -x/+x to null or 0) whoever not installing subsystem and lasted monitoring app from cause :
1.powersaver or balance does not effect anymore(but switch to Power save allow phone to use 600-700mah more often, and performance while have same usage sometimes spike to 1000mah sadly the display stay at 60hz, this is not intended as using original app power are limitied to 400-650 while average around 480mah with 40hz display)
2.while congrats you can streaming from you phone now, unless subsystem installed you may only have 1 chance to screenshot thumbnail until you reset user data. as importing image or re screenshot not working without newer subsystem. but at least all stream function working fine as i test it for 1 hours nonstop(just make use you have atleast 20-30mbps UPLOAD as lower than that cause stuttering on youtube even on 480p stream)
3.it may or may not disable/bypass thermal throttling while gaming(cant confirm but on my phone using original apk will give me around 280gips max then down to around 160 or 180gips under 5 minutes while using update version will stay more than 300gips, on CPU Thrttling, same as 3d mark, while normal benchmark average, extended test will have better result than most xperia on same model with 99.5% stability and score around 1108 to 1106 from loop 1 to loop 4 with identical performance range from loop 1 to loop 20)
4.recording no longer work on sdcard as they change folder name and older subsystem still using older name, it just keep asking permission
5.on stream and record menu. there option for capture card. it does nothing, even installing another backend app. like audio app from G.E and other app, it still wont work, unless you are rooted and install all backend app as system app, whoever fearnot, you stil can stream your content via type c to hdmi like normal, but dont except you can get audio bypass or settings like xperia 1 IV have,
*again point 3 is unclear as for me performance from older bencmark are deference than now, but it is from era android 11, i can be sony fix thermal issue and performance from firmware and not this trick, but it does effect mine since i can just remove update and see instantly the deference and it may can on your xperia too
*i said both monitoring/monitor app and subsystem app. because it called that but apk file name uploaded as sony multitasking function and GE subsystem
here a proof for point number 3, and not it not with any mod(no fan cooler but no case either with H.S enabled)
Hello,
You can add custom apps to H.S. Power Control right?
Only supported apps or ALL apps installed?
Does that also work if you turn the screen off? or does the phone start charging as soon you you turn the screen off?
Android 9 on a Samsung SM-T290 tablet.
Had used my tablet, turned off screen (click Power once), and put it down. Some unknown time later, picked up tablet, clicked Power once, screen did not come on. After clicking Power a few times, held Power down thinking somehow tablet had shut itself off completely. Instead of booting, I got the choices "Power off / Shutdown" and "Reboot". Shutting down and rebooting worked. No sign of problems.
Some time ago I noticed my Uptime seemed large -- I think 400 to 600 hours.
What would cause Android to get itself into a state in which it is still running enough to offer a Power Off menu, but in which it refuses to light up the screen?
In particular, is there any problem with running too long without shutting down and rebooting?
J.Michael said:
...
What would cause Android to get itself into a state in which it is still running enough to offer a Power Off menu, but in which it refuses to light up the screen?
Click to expand...
Click to collapse
My guess is that in your Android the Doze mode is enabled.
FYI:
Starting with Android 6 Marshmallow, the Doze mode feature was introduced. This feature is designed to give a new breath of fresh air to battery consumption and in general battery life.
xXx yYy said:
My guess is that in your Android the Doze mode is enabled.
FYI:
Starting with Android 6 Marshmallow, the Doze mode feature was introduced. This feature is designed to give a new breath of fresh air to battery consumption and in general battery life.
Click to expand...
Click to collapse
No match when I Search Settings for "doze".
Under Battery -> Settings there is an
Optimize settingsSave battery by optimizing your settings when you are not using your tablet.It's a toggle, it is toggled OFF.
I think at the moment I turned off the sceeen, I was im a browser on an obnoxious web page. Maybe their clever Javascript tied something into a knot.
I'll try to notice when I pass 600 hours of Uptime.
J.Michael said:
No match when I Search Settings for "doze".
Under Battery -> Settings there is an
Optimize settingsSave battery by optimizing your settings when you are not using your tablet.It's a toggle, it is toggled OFF.
I think at the moment I turned off the sceeen, I was im a browser on an obnoxious web page. Maybe their clever Javascript tied something into a knot.
I'll try to notice when I pass 600 hours of Uptime.
Click to expand...
Click to collapse
If it has the doze feature, it would be a background process that you would see no controls or settings for. It is a feature in the kernel that runs at and below system level and you can't "see" it if you look for it.
Doze puts the device to sleep, it effectively freezes everything from the kernel level all the way up through system/user level and turns everything off without actually powering down and stays in that state until you "wake" it.
An example would be a Kindle Fire HD tablet that I had with doze, I forgot it was on and running a PSP emulator and I put it in a draw for many weeks, when I pulled it out of the draw and hit the power button, it woke right back up straight to the enulator and the game I had running and still had 60% battery.