[Q] Battery Drain Causes? - Samsung Infuse 4G

[EDIT 7/31/12 - Changed the title of the thread, since qkster asked nicely. ]
Running CatyRom 2.0 (Android 2.3.6; KK4 modem).
Whenever I'm at home and connected to Wifi, battery life is pretty awesome.
As soon as I leave my house (and my wifi), battery drain increases substantially, and continues even after I return home and reconnect to Wifi. Aside from the display, the main cause of this battery drain is always "Android OS".
If I reboot the phone, battery drain goes back to its previously awesome state. (See Screenshots below)
Any tips to avoid the battery drain every time I leave my house? Or am I stuck rebooting my phone every time I get back home?
{
"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'd try another rom and see what happens.
Sent from my SAMSUNG-SGH-I997

tmease1 said:
I'd try another rom and see what happens.
Click to expand...
Click to collapse
Had the same problem with Infused. I guess I'll play around with different modems and see if things change.

Turn off your wifi when you leave the house...its not the rom ...I get amazing battery life away from the house
Sent from my SGH-I997 using xda premium

dman3285 said:
Turn off your wifi when you leave the house...its not the rom ...I get amazing battery life away from the house
Click to expand...
Click to collapse
I figured it was probably an Android thing, and not necessarily a CatyRom thing.
Flashed KL2 modem. Will see if that changes things at all without disabling Wifi while away from home (hoping for things to be as brain-dead & hassle-free as possible).
If not, I'll see what disabling Wifi does.
Will post battery graph screenshots over the next few days.

Modem does nothing for wifi, the wifi driver is in the kernel.
Use Shark for Root to capture wifi traffic. Load the pcap file in Wireshark.
If you see a bunch of things that look like this in the capture:
Code:
No. Time Source Destination Protocol Length Info
206 742.504839 06:46:65:da:c3:89 MurataMa_da:c3:89 0x886c 96 Ethernet II
207 742.528310 06:46:65:da:c3:89 MurataMa_da:c3:89 0x886c 74 Ethernet II
209 746.306143 06:46:65:da:c3:89 MurataMa_da:c3:89 0x886c 74 Ethernet II
210 746.313237 06:46:65:da:c3:89 MurataMa_da:c3:89 0x886c 74 Ethernet II
211 746.320438 06:46:65:da:c3:89 MurataMa_da:c3:89 0x886c 74 Ethernet II
212 746.327563 06:46:65:da:c3:89 MurataMa_da:c3:89 0x886c 74 Ethernet II
213 746.482617 06:46:65:da:c3:89 MurataMa_da:c3:89 0x886c 74 Ethernet II
214 746.488186 06:46:65:da:c3:89 MurataMa_da:c3:89 0x886c 96 Ethernet II
219 746.546120 06:46:65:da:c3:89 MurataMa_da:c3:89 0x886c 74 Ethernet II
220 746.547299 06:46:65:da:c3:89 MurataMa_da:c3:89 0x886c 79 Ethernet II
314 1624.841743 06:46:65:da:c3:89 MurataMa_da:c3:89 0x886c 76 Ethernet II
315 1624.849232 06:46:65:da:c3:89 MurataMa_da:c3:89 0x886c 74 Ethernet II
317 1628.634241 06:46:65:da:c3:89 MurataMa_da:c3:89 0x886c 74 Ethernet II
318 1628.638958 06:46:65:da:c3:89 MurataMa_da:c3:89 0x886c 74 Ethernet II
319 1628.644235 06:46:65:da:c3:89 MurataMa_da:c3:89 0x886c 74 Ethernet II
320 1628.648762 06:46:65:da:c3:89 MurataMa_da:c3:89 0x886c 74 Ethernet II
321 1628.783970 06:46:65:da:c3:89 MurataMa_da:c3:89 0x886c 74 Ethernet II
322 1628.789124 06:46:65:da:c3:89 MurataMa_da:c3:89 0x886c 96 Ethernet II
327 1628.829490 06:46:65:da:c3:89 MurataMa_da:c3:89 0x886c 74 Ethernet II
328 1628.829993 06:46:65:da:c3:89 MurataMa_da:c3:89 0x886c 79 Ethernet II
And by a "bunch" I mean once a second for minutes on end - try the latest Daily Driver kernel release. That will HOPEFULLY fix the issue.
It's some weird **** related to a wacky mostly undocumented Broadcom feature. **** Broadcom.

Hi mate interested in knowing your results, I got the same issue
Sent from my HTC Glacier using XDA App

Entropy512 said:
Modem does nothing for wifi, the wifi driver is in the kernel.
Use Shark for Root to capture wifi traffic. Load the pcap file in Wireshark.
If you see a bunch of things that look like this in the capture:
Code:
No. Time Source Destination Protocol Length Info
206 742.504839 06:46:65:da:c3:89 MurataMa_da:c3:89 0x886c 96 Ethernet II
207 742.528310 06:46:65:da:c3:89 MurataMa_da:c3:89 0x886c 74
And by a "bunch" I mean once a second for minutes on end - try the latest Daily Driver kernel release. That will HOPEFULLY fix the issue.
It's some weird **** related to a wacky mostly undocumented Broadcom feature. **** Broadcom.
Click to expand...
Click to collapse
Didn't see anything like that yesterday, but I had also disabled Wifi while away at my family's Christmas (which, by the way, did help battery life quite a bit).
Not sure if CatyRom 2.0 has the latest Daily Driver or not, so I flashed the 11/27 version.
Next time I go out, I'll toss together a pcap file and see if any of those MurataMa thingamabobs show up.
EDIT: Or is it the 0x886c Protocol I'm looking for (I didn't see any of those)? Sorry, I don't know diddly about network diagnostics...

FYI.. Here's the battery graph showing how disabling Wifi can help cut down on battery drain when outside of a Wifi area.
My family's Christmas was in a fairly rural area, so my phone was awake quite a bit more than usual, trying to sync on a mostly nonexistent data connection. So, I imagine disabling Wifi will have an even more pronounced effect if you have good cell coverage.
ADD: This is running CatyRom 2.0 after flashing the KL2 modem (theme is Matted Blue, if you were curious).

OK, entropy.. I think I see what you're talking about. Just got back from lunch, and my pcap was full of these...
Code:
21 17.410567 7a:d6:f0:97:50:71 SamsungE_97:50:71 0x886c 74 Ethernet II
22 18.435103 7a:d6:f0:97:50:71 SamsungE_97:50:71 0x886c 74 Ethernet II
23 19.458398 7a:d6:f0:97:50:71 SamsungE_97:50:71 0x886c 74 Ethernet II
24 20.481196 7a:d6:f0:97:50:71 SamsungE_97:50:71 0x886c 74 Ethernet II
25 21.504877 7a:d6:f0:97:50:71 SamsungE_97:50:71 0x886c 74 Ethernet II
26 22.564409 7a:d6:f0:97:50:71 SamsungE_97:50:71 0x886c 74 Ethernet II
27 23.554539 7a:d6:f0:97:50:71 SamsungE_97:50:71 0x886c 74 Ethernet II
I'm using your latest Daily Driver, so I'll keep an eye on what the battery does over the next few hours.

Well, the 11/27 Entropy Daily Driver kernel didn't appear to eliminate the Android OS battery drain.
I tried a few things, and it appears that the only thing to stop the battery level from plummeting is a reboot. Cycling Wifi off and back on seems to help a little, but not completely.
As far as the 0x886c packets go, they appeared roughly once every second in a pcap sample taken shortly after the first "Returned to Wifi".
A few minutes after "Rebooted Phone", I saw a flurry of about 10 of them in less than a second. Random 1-2 minutes samples during the next hour or two showed an occasional 0x886c packet -- maybe 1-2 per minute.
I didn't see any 0x886c packets in samples taken immediately after the second "Returned to Wifi", "Cycle Wifi", "Cycle Data Network Mode", or "Cycle Flight Mode".

fwiw:
I notice a big drain on batter by Google maps even when i don't use it.
idk if uninstalling for you may be an option or not..or opt out of location request
modem and data can also take up a bit a battery as well.
from previous posts, i have recommmed DL a dataswitch app that stops background data - it's a toggler.
this leaves phone and text intact.
do this when you dont need constant background data sync.
it is not for everyone but it can be useful if you are looking to conserve battery in a pinch.
you can go for several days on a single charge.
ymmv

I've used Juice Defender Ultimate in the past, but didn't really notice any improvement. In fact, it made battery life worse when on wifi.
With a constant wifi connection and sleep policy turned off, I can still have 100% battery 4hrs after unplugging from the charger(!).. Juice Defender disconnecting & reconnecting every 15 minutes killed a few percent every hour. Not to mention, I hate having to wait 10-15 seconds after turning on my phone to use the internet.
My only problem is when switching back and forth between wifi and cellular data.

****ING BROADCOM.
**** THEM TO HELL.
I thought removing BT-AMP support from the kernel would fix that wacked out **** but apparently it doesn't.
****ING BROADCOM.
**** THEM AND THEIR COMPLETELY UNCOMMENTED/UNDOCUMENTED CODE, ALONG WITH THEIR LACK OF DATASHEETS.
I'll see if I can duplicate this with the parents' phone. Interestingly enough, it only seems to happen with AT&T leak bases - I had it happen multiple times after getting my GS2 (which is when I started playing with UCKJ2) but never beforehand. (Edit: I'm wrong - it does also happen with UXKG3 base, such as Infused 2.x - but it seems to not happen on Hellraised ROMs to my knowledge, nor on CM7.)
This may possibly be related to the weird wifi issues (including battery drain) affecting UCKK6 for the Galaxy S II - It's some weird bug in /system and not the kernel.
Edit: To those having issues, do you own any other devices with Broadcom wifi chipsets? (Such as other Samsung phones, Samsung Tab 10.1s, etc)?
https://www.youtube.com/watch?v=eQBjQs07wbw - sing along with me! When they say "**** Martinez", I say "**** the Broadcom!" (Yes, I know that is a bit weird - but it has the correct syllable count and rhythm.)

PharmNerd said:
I've used Juice Defender Ultimate in the past, but didn't really notice any improvement. In fact, it made battery life worse when on wifi.
With a constant wifi connection and sleep policy turned off, I can still have 100% battery 4hrs after unplugging from the charger(!).. Juice Defender disconnecting & reconnecting every 15 minutes killed a few percent every hour. Not to mention, I hate having to wait 10-15 seconds after turning on my phone to use the internet.
My only problem is when switching back and forth between wifi and cellular data.
Click to expand...
Click to collapse
We are all set in our ways. If you're open to suggestion, unistall juice def.
download from market: dataswitch by tomatoX.
run it for a day and see what happens.
Entropy..I feel the anger of your rant, but it was way over my head to appreciate what it was about.

Entropy512 said:
...****ING BROADCOM.
**** THEM TO HELL......
Click to expand...
Click to collapse
Really necessary?

andrawer said:
Really necessary?
Click to expand...
Click to collapse
I think it is.

andrawer said:
Really necessary?
Click to expand...
Click to collapse
Yes, they are one of the least open source friendly and least developer-friendly companies out there.
They don't comment the code of their crappy kernel drivers (and this thread PROVES they are crappy) at all, and they don't provide ANY documentation on their chipsets.
So when their drivers flake out like they are here, there is no way to fix them.
The evidence is clear in the wireshark captures - some wacky proprietary feature of theirs (Bluetooth AMP) is flaking out and malfunctioning (despite this phone not even USING the BCM4330's BT features) and waking up the Infuse once a second in many cases. This kills battery life.
The feature misbehaves even when BTAMP is completely disabled in the kernel.
Sent from my GT-P7510 using Tapatalk

Entropy512 said:
Yes, they are one of the least open source friendly and least developer-friendly companies out there.
They don't comment the code of their crappy kernel drivers (and this thread PROVES they are crappy) at all, and they don't provide ANY documentation on their chipsets.
So when their drivers flake out like they are here, there is no way to fix them.
The evidence is clear in the wireshark captures - some wacky proprietary feature of theirs (Bluetooth AMP) is flaking out and malfunctioning (despite this phone not even USING the BCM4330's BT features) and waking up the Infuse once a second in many cases. This kills battery life.
The feature misbehaves even when BTAMP is completely disabled in the kernel.
Sent from my GT-P7510 using Tapatalk
Click to expand...
Click to collapse
I'm gonna give you the 1700th thank

I tried to reproduce this with my parents' phone (Infused 2.2.3, Daily Driver 11/27) - no luck, it's working fine.
Makes it a pain in the butt to debug.

Related

[Q] Wireless n limited to 65Mbps?

Has anyone been able to exceed wireless n speed of 65 Mbps on their Captivate?
My computer reaches speeds of 135 Mbps but with my captivate right next to the router, I don't see anything above 65 Mbps.
Edit: I'm just using the speed it tells you when you click settings->wireless and network->wifi then I just tap the SSID and look under speed.
Also I set my router to only use the 40mhz band. I just want to know if even 1 person has seen anything over 65 Mbps, so that I know whether it the phone or the router.
arababay said:
Has anyone been able to exceed wireless n speed of 65 Mbps on their Captivate?
My computer reaches speeds of 135 Mbps but with my captivate right next to the router, I don't see anything above 65 Mbps.
Click to expand...
Click to collapse
Dumb ? Is your computer using dual-band?
Edit: also, the Cap might be operating in 20mhz bands intead of 20/40... (nasty technical details)
How did you test this? ALso usiong no encryption helps....
Also I didn't know captivate have N band 2.4?
EDIT:
a/b/g/n dual spectrum capable.
My guess? driver.
http://www.broadcom.com/products/Bluetooth/Bluetooth-RF-Silicon-and-Software-Solutions/BCM4329
I am thinking the driver has some issues in general.
Random loss of connectivity and need to disable enable wireless to get connectivity back.
Slow 802.1x connection speeds (11mbps max from what I can tell)
N only connects on 2.4Ghz band and not 5Ghz.
So, yeah, my guess is driver is gimped a bit.
I have no issues with Wifi. BTW, iPhone 4 also uses only 2.4 Ghz band for "n". As I understand, 5 Ghz would require additional antenna.
Also get max of 65 Mbps
Was disappointed when I saw my Captivate which is advertised as having wireless N just barely connects above wireless G speeds. Both laptops easily gets 130Mbps from the same router.
N speeds on a 20MHz band will be 65Mbs. Your laptop and desktop most likely have a 40Mhz bandwidth antennae which allow you to get up to 135Mbs. The Captivate has an antennae that will only work on the 20MHz band which is why you only see a max of 65Mbs. I remember reading about why this is and I can't find the documentation any more.
Anyway, while this does seem "barely higher than G speeds" it's actually a big difference. The wireless N standard added the function of Multiple Input and Multiple Output (MIMO) antenna's which increases the signal throughput. The wireless G standard does not have MIMO function in it. The increased speeds and the addition of MIMO antenna's makes the Captivate's N wireless much faster than a G wireless even though the Mbs are close together.
---------- Post added at 09:59 PM ---------- Previous post was at 09:48 PM ----------
And, just to answer it in case someone is thinking it .....
Having your wireless on 5GHz vs 2.4GHz will not increase your Captivate speeds above 65Mbs. This refers to the frequency of the signal which is different from the signal bandwidth. The 5GHz range was added with wireless N to avoid interference from other 2.4 MHz devices such as wireless keyboards, wireless mice, home telephones (people still have these?), wireless gaming controllers, etc.
While 5GHz is nice, as it is a separate frequency to help avoid interference, it actually has a shorter broadcast distance since it's a higher frequency. It will also have a harder time broadcasting through walls and other solid objects since it's a higher frequency.
If I just made you think..."wow, thanks" please click the button below.
Good information
Thanks for the information. Am always much happier once I have been given an explanation to a question.
With some of the leaked GB 2.3.x builds, I have gotten 72 mbps when my router is set to N only mode, locked to 40 Mhz width, WMM enabled, WPA2 personal "AES only" encryption, with all options for "neighborly" radio turned off, and standing within 6ft of the router.
65 mbps was the highest I ever got on CM7 or Froyo and even the GB builds don't hold at 72 mbps for long.
My Captivate does connect to 2.4 Ghz with 40 Mhz width. 5 Ghz won't work though.
Ya my internet doesn't go over 2 mbs. 65 would be a dream.
Sent from my SGH-I897 using XDA App
ou812bkewl said:
With some of the leaked GB 2.3.x builds, I have gotten 72 mbps when my router is set to N only mode, locked to 40 Mhz width, WMM enabled, WPA2 personal "AES only" encryption, with all options for "neighborly" radio turned off, and standing within 6ft of the router.
65 mbps was the highest I ever got on CM7 or Froyo and even the GB builds don't hold at 72 mbps for long.
My Captivate does connect to 2.4 Ghz with 40 Mhz width. 5 Ghz won't work though.
Click to expand...
Click to collapse
Humm, I've never gotten anything higher than 65Mbps even on 5Ghz. However I've never tried it on 40Mhz width as I thought it wouldn't work. I'll have to test this out and see.
Sent from my SAMSUNG-SGH-I897 using XDA App

72 Mbps 802.11n wifi max speed on Inspire 4G?

Is anyone able to connect at higher than 72 Mbps? I Googled up an old forum post where they thought there might be a hardware limit? I just got a 802.11n router recently but I've yet to connect higher than 65 or 72.
Elbob10s said:
Is anyone able to connect at higher than 72 Mbps? I Googled up an old forum post where they thought there might be a hardware limit? I just got a 802.11n router recently but I've yet to connect higher than 65 or 72.
Click to expand...
Click to collapse
Try messing with the settings on your router. I spent nearly an hour one day on my wireless N router and was able to get further reception. Never messed with the speed as too its not really an issue. 65mbs is WAY more than enough for a mobile phone. But if its that important to you I think it really won't matter how much faster you make it because the speed at which the sdcard can write data can't keep up with the data speeds of a high speed home data connection of about 10-20m anyway. Already I'm able to download at about 1.2mbs on large files which is the same speed as my computer when downloading large files.
Point is... no matter what you do to increase the wifi speeds on your router or your phone won't make a difference
Sent from my MB855 using XDA
Computers connect to the router at 150+ so I'm pretty sure it's setup correctly.
I know it will only effect in-network activities, but I was just wondering if there was a reason I couldn't get it to go past 72.
The photon supports up to 150. You could try going into your router settings and change the rate from auto to 150 turn your wifi off then on after your router sets and see if you get the 150 connection. It may also have to do with the rom. The photon also supports 5ghz wifi connections but on cm9 we are stuck using 2.4 because the setting to change the frequency is missing
Sent from my MB855 using XDA
Lol oops forgot I'm on the inspire thread. I'm not sure If the inspire supports 5ghz frequencies. Go to wifi, then hit menu and go to advance settings. There might be an option to switch between the two settings. Also on your router mess with the channels. I have had better luck on 9 than 11 with getting over 72. Also make sure the channel width is 40mhz only. The 20mhz can support up to 150mps but if your phone don't need it it will not force it. The radio on nearly all smart phones are automatic which means it will do what it thinks is best for your phone. Some roms I have seen on other devices have forced settings for wifi which gives much more control over how the phone reads from the router.
Sent from my MB855 using XDA
It looks like a limitation of Android device since I have 2 devices max out only 72Mbps.
There are a number of limitations that stop extra fast speeds on 802.11n.
1) Antennas
1 antenna = max 150 Mbps
2) Congestion
If you are in a busy area (like suburbia, 2.4 Ghz is used by more than just WiFi too) you will not get the 40 Mhz bandwidth for 150 Mbps, it will drop back to 20 Mhz bandwidth which means 72.2 Mbps maximum.
3) Guard Interval
If the distinct transmissions between between both units are not making it through, the Guard Interval will be doubled from 400 nanoseconds to 800 nanoseconds. Maximum now possible is 65 Mbps.
Most people will never see more than 72 Mbps on one antenna.
More: Wikipedia: 802.11n, "Data rates"
I max out around 35mbps of real throughput
Sent from my Desire HD using xda premium

Slow Wifi speed on Nexus 5.

I am on stock ROM. With Franko Kernel 32
My router is Belkin N150
My Laptop is a W520 purchased over a year ago i7.
My laptop is able to connect at 150 Mb/sec
My Samsung S2 is able to connect at 150 MB/Sec.
My Nexus will only connect at 75 Mb/Sec.
The samsung with a stock rom and stock Kernel is able to pump data over wifi much much faster than my Nexus.
I get 600 Kb/Sec moving data from my laptop to the phone and phone to the laptop
On the nexus I am lucky to get 300 Kb/Sec.
I have tried all the TCP/IP options in Franko Kernel. Westwood / Bic etc.
Whats going on here.
Any tip much apprcated.
BTW I am using channel 7 cause it has the least traffic in my area.

WiFi Lan High Latency

I noticed lots of network jitter when connected to WiFi over 5ghz band in low congestion area with good signal strength. Pings to the router would vary between 4ms and 18, sometimes 22ms. Jitter to that degree is also evident when I ping out to the web.
I am wondering if this is responsible for my constant lag spikes in vainglory, paladin strike, and arena of valor.
I'd like to know how your guys' Android phones are performing when pinging your router address so I can compare. If you know how, you can download an app like "ping " from app store for easy testing.
Thank you.
systoxity said:
I noticed lots of network jitter when connected to WiFi over 5ghz band in low congestion area with good signal strength. Pings to the router would vary between 4ms and 18, sometimes 22ms. Jitter to that degree is also evident when I ping out to the web.
I am wondering if this is responsible for my constant lag spikes in vainglory, paladin strike, and arena of valor.
I'd like to know how your guys' Android phones are performing when pinging your router address so I can compare. If you know how, you can download an app like "ping " from app store for easy testing.
Thank you.
Click to expand...
Click to collapse
Could just be your network the ping is still in a good range j get about 10-15
That's very possible. Thank you for your time and contribution.
systoxity said:
That's very possible. Thank you for your time and contribution.
Click to expand...
Click to collapse
Test ping on other devices also connected over WiFi and share the results from them as well
I pinged my router 100 times and the ping times varied between 0. 916 and 4.98ms. But in average it's about 1ms.
Sent from my ONEPLUS A6003 using Tapatalk
TechOut said:
Test ping on other devices also connected over WiFi and share the results from them as well
Click to expand...
Click to collapse
Pinging via windows cubemix plus tablet on same 5ghz band gives me steady 2-3ms with infrequent outliers.
Will wait till more people are home and try some more devices. Thank you again everyone.
Tested an iPhone X, Nexus 6p, and re-ran the oneplus. The ping tests were done approximately 10 feet away from router with direct line of sight.
Tested consecutively with no other devices on network. Ping was directly to router. Bluetooth and cellular service disabled (I tested difference between cellular enabled and disabled, it was pretty much the same).
200 pings on 5Ghz band:
iPhone X: Avg 9.7 Standard deviation 2
Nexus 6p: Avg 10.2 Standard deviation 9
Oneplus 6: Avg 18.7 Standard deviation 5
200 pings 2.4Ghz band:
iPhone X: Avg 10.3 Standard Deviation 4
Nexus 6p: Avg 9.2 Standard Deviation 3.5
Oneplus 6: Avg 19.3 Standard Deviation 5.1
Realistically, a ping slowdown of about ~10ms on the oneplus 6 compared to iPhone X would probably not account for the jitter and frequent spikes I saw in those mobile games... Unless I put further strain by moving away from router. I noticed the signal notification indicator does not really reflect signal quality on iPhone and Oneplus; so who knows, more testing is needed. It is interesting though to see the difference in ping latency between the devices.

Haldi's Benchmark Thread for Testing&Fiddling with the Xperia XZ2

Howdy,
You might remember me from the Xperia Z2 or the Xperia Z. I've started playing around with Android on my old Sony Xperia X10i and i've always liked fiddling around with too much data and thoroughly testing what i own in order to fully understand it.
Lately i've been active in the HTC 10 Subforums but since the Battery started going bad i've become afraid of the phone dying on me and i got this really good deal on the XZ2. So here i am back at Sonys.
So... this thread is mainly for me to keep my findings sorted but you might also find some interesting things here.
If you take a look at my older threads you'll know what to expect
What's new with the Xperia XZ2?
Well.... Android 8.0 with SD845 and 4.9 Kernel... no more Interactive governor. We got EAS built in an use SchedUtil. While it is possible to modify the behaviour of SchedUtil via SchedTune it's nowhere nearly as complex as Interactive or different governors.
Trepn Profiler doesn't report Battery Power anymore... while Trepn Profiler has been partially broken since Android 6.0 it did work kinda fine on the SD820 devices even with Android 8.1 and custom Kernels. (except Load%) Even though it was limited one poll per 30sec. While on the XZ2 only estimated Power is available. Which does not work due to missing CPU load.
Benchmarking:
Powerdrain: Find out how much the Phone is using under specific circumstances.
Charging: How fast does the Device charge from 1% to 100%
Throttling: Analyzing Thermal and Powerlimit Throttling
Benchmarking Apps:
Repetitouch: To create custom Benchmarks that simulate normal everyday usage.
BatteryLog: For Charging Benchmark, Voltage and Battery% per Minute
GameBench: For FPS in games. (Make sure you deactivate Screenshot function for HTC10)
Benchmarking Hardware:
YZX Powermonitor: USB 3.0 QC3.0 4-13V 0-3A USB A Male-> USB A Female Powermonitor that measures Voltage and Current passing trough.
I'll update this Post when new infos are available...
Index:
Charging Stock ROM with Stock Charger Post NR3
Thermal Throttling and Taks Migration / Load Balancing Post NR6
Powerdrain & Thermal Throttling on GPU & CPU Post NR7
Thermal Throttling on Android P | 5% Battery Limit Post NR9
Charging Android P no Qnovo.... Post NR10
Charging Android 10 Post NR15
Aftermarket Batteries Tested Post NR16
OFFICIAL Battery Tested.... not better -.- Post NR19
Charging Sony Xperia XZ Stock ROM with Stock Charger
Qnovo in Action!
{
"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"
}
First thing we see is the max Voltage.... this phone is fully charged at 4,331V Okay? Guess that's the new kind of Battery. I'm used to see 4,4V
After 40 Minutes when the battery reached 40°C and 60% there is Thermal Throttling. If you take a look at the HTC10 Charging you can see the CCCV breaking point this does not happen here, it's simply reduced from 11W to 8W which does indicate throttling. It's only after 117 Minutes when the Battery reaches 4,33V that you can see the expected curve...
This has to do with the new Qnovo Charging Technology. Nice read on Qnovo Charging Technology...
In the far future when my phone found out when i charge it over night i'm also gonna measure the Battery Care in action i wonder how slow it charges if it has the time.
Oh, and i'll have to Try with Another QC3.0 Charger. While the UCH12 is QC3.0 and PD2.0 compatible even the Old Sony Chargers said 1.5A but only charged the phone with 1A....
just some ramblings to not forget....
H8216:/sys/devices/system/cpu/cpu0/cpufreq $ cat scaling_available_governors
conservative ondemand userspace powersave performance schedutil
H8216:/sys/devices/system/cpu/cpu0/cpufreq $ cat scaling_available_frequencies
300000 403200 480000 576000 652800 748800 825600 902400 979200 1056000 1132800 1228800 1324800 1420800 1516800 1612800 1689600 1766400
H8216:/sys/devices/system/cpu/cpu0/cpufreq/schedutil $ cat hispeed_freq
1209600
H8216:/sys/devices/system/cpu/cpu0/cpufreq/schedutil $ cat hispeed_load
90
H8216:/sys/devices/system/cpu/cpu0/cpufreq/schedutil $ cat pl
1
H8216:/sys/devices/system/cpu/cpu0/cpufreq/schedutil $ cat rate_limit_us
0
Click to expand...
Click to collapse
H8216:/sys/devices/system/cpu/cpu4/cpufreq $ cat scaling_available_governors
conservative ondemand userspace powersave performance schedutil
H8216:/sys/devices/system/cpu/cpu4/cpufreq $ cat scaling_available_frequencies
825600 902400 979200 1056000 1209600 1286400 1363200 1459200 1536000 1612800 1689600 1766400 1843200 1920000 1996800 2092800 2169600 2246400 2323200 2400000 2476800 2553600 2649600
H8216:/sys/devices/system/cpu/cpu4/cpufreq $ cat scaling_boost_frequencies
2803200
H8216:/sys/devices/system/cpu/cpu4/cpufreq/schedutil $ cat hispeed_freq
1574400
H8216:/sys/devices/system/cpu/cpu4/cpufreq/schedutil $ cat hispeed_load
90
H8216:/sys/devices/system/cpu/cpu4/cpufreq/schedutil $ cat pl
1
H8216:/sys/devices/system/cpu/cpu4/cpufreq/schedutil $ cat rate_limit_us
0
Click to expand...
Click to collapse
/dev/stune doesn't really show much.... schedtune.boost always seems to be 0.
Some Sensor paths... might need them later on.
H8216:/ $ for file in sys/class/thermal/thermal_zone*/type; do echo "$file"; cat "$file"; done
sys/class/thermal/thermal_zone0/type
aoss0-usr
sys/class/thermal/thermal_zone1/type
cpu0-silver-usr
sys/class/thermal/thermal_zone2/type
cpu1-silver-usr
sys/class/thermal/thermal_zone3/type
cpu2-silver-usr
sys/class/thermal/thermal_zone4/type
cpu3-silver-usr
sys/class/thermal/thermal_zone5/type
kryo-l3-0-usr
sys/class/thermal/thermal_zone6/type
kryo-l3-1-usr
sys/class/thermal/thermal_zone7/type
cpu0-gold-usr
sys/class/thermal/thermal_zone8/type
cpu1-gold-usr
sys/class/thermal/thermal_zone9/type
cpu2-gold-usr
sys/class/thermal/thermal_zone10/type
cpu3-gold-usr
sys/class/thermal/thermal_zone11/type
gpu0-usr
sys/class/thermal/thermal_zone12/type
gpu1-usr
sys/class/thermal/thermal_zone13/type
aoss1-usr
sys/class/thermal/thermal_zone14/type
mdm-dsp-usr
sys/class/thermal/thermal_zone15/type
ddr-usr
sys/class/thermal/thermal_zone16/type
wlan-usr
sys/class/thermal/thermal_zone17/type
compute-hvx-usr
sys/class/thermal/thermal_zone18/type
camera-usr
sys/class/thermal/thermal_zone19/type
mmss-usr
sys/class/thermal/thermal_zone20/type
mdm-core-usr
sys/class/thermal/thermal_zone21/type
gpu-virt-max-step
sys/class/thermal/thermal_zone22/type
silv-virt-max-step
sys/class/thermal/thermal_zone23/type
gold-virt-max-step
sys/class/thermal/thermal_zone24/type
pop-mem-step
sys/class/thermal/thermal_zone25/type
cpu0-silver-step
sys/class/thermal/thermal_zone26/type
cpu1-silver-step
sys/class/thermal/thermal_zone27/type
cpu2-silver-step
sys/class/thermal/thermal_zone28/type
cpu3-silver-step
sys/class/thermal/thermal_zone29/type
cpu0-gold-step
sys/class/thermal/thermal_zone30/type
cpu1-gold-step
sys/class/thermal/thermal_zone31/type
cpu2-gold-step
sys/class/thermal/thermal_zone32/type
cpu3-gold-step
sys/class/thermal/thermal_zone33/type
lmh-dcvs-01 Stuck at 75000 no matter what...
sys/class/thermal/thermal_zone34/type
lmh-dcvs-00 Stuck at 75000 no matter what...
sys/class/thermal/thermal_zone35/type
pm8998_tz 20° Colder than cores at load, idle is same
sys/class/thermal/thermal_zone36/type
aoss0-lowf
sys/class/thermal/thermal_zone37/type
cpu0-silver-lowf
sys/class/thermal/thermal_zone38/type
cpu1-silver-lowf
sys/class/thermal/thermal_zone39/type
cpu2-silver-lowf
sys/class/thermal/thermal_zone40/type
cpu3-silver-lowf
sys/class/thermal/thermal_zone41/type
kryo-l3-0-lowf
sys/class/thermal/thermal_zone42/type
kryo-l3-1-lowf
sys/class/thermal/thermal_zone43/type
cpu0-gold-lowf
sys/class/thermal/thermal_zone44/type
cpu1-gold-lowf
sys/class/thermal/thermal_zone45/type
cpu2-gold-lowf
sys/class/thermal/thermal_zone46/type
cpu3-gold-lowf
sys/class/thermal/thermal_zone47/type
gpu0-lowf
sys/class/thermal/thermal_zone48/type
gpu1-lowf
sys/class/thermal/thermal_zone49/type
aoss1-lowf
sys/class/thermal/thermal_zone50/type
mdm-dsp-lowf
sys/class/thermal/thermal_zone51/type
ddr-lowf
sys/class/thermal/thermal_zone52/type
wlan-lowf
sys/class/thermal/thermal_zone53/type
compute-hvx-lowf
sys/class/thermal/thermal_zone54/type
camera-lowf
sys/class/thermal/thermal_zone55/type
mmss-lowf
sys/class/thermal/thermal_zone56/type
mdm-core-lowf
sys/class/thermal/thermal_zone57/type
ibat-high from 500 idle to 2200 load, dropping with throttling to 1120
sys/class/thermal/thermal_zone58/type
ibat-vhigh same as above
sys/class/thermal/thermal_zone59/type
vbat 3744 at idle 3666 at load.... wtf is this voltage?
sys/class/thermal/thermal_zone60/type
vbat_low same as above
sys/class/thermal/thermal_zone61/type
vbat_too_low same as above
sys/class/thermal/thermal_zone62/type
soc idles at 44, drops to 42 and 42 at load...
sys/class/thermal/thermal_zone63/type
pmi8998_tz Broken "No Data available"
sys/class/thermal/thermal_zone64/type
xo-therm-adc
sys/class/thermal/thermal_zone65/type
msm-therm-adc
sys/class/thermal/thermal_zone66/type
pa-therm1-adc
sys/class/thermal/thermal_zone67/type
quiet-therm-adc
sys/class/thermal/thermal_zone68/type
ufs_therm idles at 37656 drops to 33672 at load
sys/class/thermal/thermal_zone69/type
pa_therm2
sys/class/thermal/thermal_zone70/type
flash_therm
sys/class/thermal/thermal_zone71/type
battery you guessed it... battery!
sys/class/thermal/thermal_zone72/type
wireless broken "no such device"
sys/class/thermal/thermal_zone73/type
bms same as battery at idle, 6°C colder at load. Shis should be interesting while charging
sys/class/thermal/thermal_zone74/type
sony_camera_0 broken "no such device"
sys/class/thermal/thermal_zone75/type
sony_camera_1 broken "no such device"
sys/class/thermal/thermal_zone76/type
wsatz.14 either around 34 to 55
sys/class/thermal/thermal_zone77/type
wsatz.13 idles at 38, goes to 53 at load
Edit: i did a test while Loaded and saw how the temperatures changed... Oh... and i also wrote a little script, to run on your phone, which writes all temperatures down as .csv
Yeah..... there is a lot of sensors... so let's try to cut some...
the normal difference between usr step and lowf is almost nonexistent... so one should be enough.
H8216:/ $ for file in sys/class/thermal/cooling_device*/type; do echo "$file"; cat "$file"; done
sys/class/thermal/cooling_device0/type
panel0-backlight
sys/class/thermal/cooling_device1/type
thermal-devfreq-0
sys/class/thermal/cooling_device2/type
thermal-cpufreq-0
sys/class/thermal/cooling_device3/type
thermal-cpufreq-1
sys/class/thermal/cooling_device4/type
thermal-cpufreq-2
sys/class/thermal/cooling_device5/type
thermal-cpufreq-3
sys/class/thermal/cooling_device6/type
thermal-cpufreq-4 #Throttling is happening here: shows value 10
sys/class/thermal/cooling_device7/type
thermal-cpufreq-5
sys/class/thermal/cooling_device8/type
thermal-cpufreq-6
sys/class/thermal/cooling_device9/type
thermal-cpufreq-7 #Throttling is happening here: shows value 24
sys/class/thermal/cooling_device10/type
ebi
sys/class/thermal/cooling_device11/type
cx
sys/class/thermal/cooling_device12/type
mx-cdev-lvl
sys/class/thermal/cooling_device13/type
cdsp_vdd
sys/class/thermal/cooling_device14/type
adsp_vdd
sys/class/thermal/cooling_device15/type
slpi_vdd
sys/class/thermal/cooling_device16/type
modem_pa
sys/class/thermal/cooling_device17/type
modem_proc
sys/class/thermal/cooling_device18/type
modem_vdd
sys/class/thermal/cooling_device19/type
modem_current
sys/class/thermal/cooling_device20/type
modem_skin
EDIT: P Dev Preview 2
oooh Fûck this shít they changed quite a bit in P dev Preview 2 -.-
C:\ADB>adb shell for file in sys/class/thermal/thermal_zone*/type; do echo "$file"; cat "$file"; done
sys/class/thermal/thermal_zone0/type
aoss0-usr
sys/class/thermal/thermal_zone1/type
cpu0-silver-usr
sys/class/thermal/thermal_zone10/type
cpu3-gold-usr
sys/class/thermal/thermal_zone11/type
gpu0-usr
sys/class/thermal/thermal_zone12/type
gpu1-usr
sys/class/thermal/thermal_zone13/type
aoss1-usr
sys/class/thermal/thermal_zone14/type
mdm-dsp-usr
sys/class/thermal/thermal_zone15/type
ddr-usr
sys/class/thermal/thermal_zone16/type
wlan-usr
sys/class/thermal/thermal_zone17/type
compute-hvx-usr
sys/class/thermal/thermal_zone18/type
camera-usr
sys/class/thermal/thermal_zone19/type
mmss-usr
sys/class/thermal/thermal_zone2/type
cpu1-silver-usr
sys/class/thermal/thermal_zone20/type
mdm-core-usr
sys/class/thermal/thermal_zone21/type
gpu-virt-max-step
sys/class/thermal/thermal_zone22/type
silv-virt-max-step
sys/class/thermal/thermal_zone23/type
gold-virt-max-step
sys/class/thermal/thermal_zone24/type
pop-mem-step
sys/class/thermal/thermal_zone25/type
cpu0-silver-step
sys/class/thermal/thermal_zone26/type
cpu1-silver-step
sys/class/thermal/thermal_zone27/type
cpu2-silver-step
sys/class/thermal/thermal_zone28/type
cpu3-silver-step
sys/class/thermal/thermal_zone29/type
cpu0-gold-step
sys/class/thermal/thermal_zone3/type
cpu2-silver-usr
sys/class/thermal/thermal_zone30/type
cpu1-gold-step
sys/class/thermal/thermal_zone31/type
cpu2-gold-step
sys/class/thermal/thermal_zone32/type
cpu3-gold-step
sys/class/thermal/thermal_zone33/type
lmh-dcvs-01
sys/class/thermal/thermal_zone34/type
lmh-dcvs-00
sys/class/thermal/thermal_zone35/type
pm8998_tz
sys/class/thermal/thermal_zone36/type
pm8005_tz
sys/class/thermal/thermal_zone37/type
aoss0-lowf
sys/class/thermal/thermal_zone38/type
cpu0-silver-lowf
sys/class/thermal/thermal_zone39/type
cpu1-silver-lowf
sys/class/thermal/thermal_zone4/type
cpu3-silver-usr
sys/class/thermal/thermal_zone40/type
cpu2-silver-lowf
sys/class/thermal/thermal_zone41/type
cpu3-silver-lowf
sys/class/thermal/thermal_zone42/type
kryo-l3-0-lowf
sys/class/thermal/thermal_zone43/type
kryo-l3-1-lowf
sys/class/thermal/thermal_zone44/type
cpu0-gold-lowf
sys/class/thermal/thermal_zone45/type
cpu1-gold-lowf
sys/class/thermal/thermal_zone46/type
cpu2-gold-lowf
sys/class/thermal/thermal_zone47/type
cpu3-gold-lowf
sys/class/thermal/thermal_zone48/type
gpu0-lowf
sys/class/thermal/thermal_zone49/type
gpu1-lowf
sys/class/thermal/thermal_zone5/type
kryo-l3-0-usr
sys/class/thermal/thermal_zone50/type
aoss1-lowf
sys/class/thermal/thermal_zone51/type
mdm-dsp-lowf
sys/class/thermal/thermal_zone52/type
ddr-lowf
sys/class/thermal/thermal_zone53/type
wlan-lowf
sys/class/thermal/thermal_zone54/type
compute-hvx-lowf
sys/class/thermal/thermal_zone55/type
camera-lowf
sys/class/thermal/thermal_zone56/type
mmss-lowf
sys/class/thermal/thermal_zone57/type
mdm-core-lowf
sys/class/thermal/thermal_zone58/type
ibat-high
sys/class/thermal/thermal_zone59/type
ibat-vhigh
sys/class/thermal/thermal_zone6/type
kryo-l3-1-usr
sys/class/thermal/thermal_zone60/type
vbat
sys/class/thermal/thermal_zone61/type
vbat_low
sys/class/thermal/thermal_zone62/type
vbat_too_low
sys/class/thermal/thermal_zone63/type
soc
sys/class/thermal/thermal_zone64/type
pmi8998_tz
sys/class/thermal/thermal_zone65/type
xo-therm-adc
sys/class/thermal/thermal_zone66/type
msm-therm-adc
sys/class/thermal/thermal_zone67/type
pa-therm1-adc
sys/class/thermal/thermal_zone68/type
quiet-therm-adc
sys/class/thermal/thermal_zone69/type
ufs_therm
sys/class/thermal/thermal_zone7/type
cpu0-gold-usr
sys/class/thermal/thermal_zone70/type
pa_therm2
sys/class/thermal/thermal_zone71/type
flash_therm
sys/class/thermal/thermal_zone72/type
battery
sys/class/thermal/thermal_zone73/type
wireless
sys/class/thermal/thermal_zone74/type
bms
sys/class/thermal/thermal_zone75/type
sony_camera_0
sys/class/thermal/thermal_zone76/type
sony_camera_1
sys/class/thermal/thermal_zone77/type
wsatz.14
sys/class/thermal/thermal_zone78/type
wsatz.13
sys/class/thermal/thermal_zone8/type
cpu1-gold-usr
sys/class/thermal/thermal_zone9/type
cpu2-gold-usr
Thermal/cooling_device is still the same...
akari:/ $ for file in sys/class/thermal/cooling_device*/type; do echo "$file"; cat "$file"; done |MAX|MIN|
sys/class/thermal/cooling_device0/type
panel0-backlight |4095|error|
sys/class/thermal/cooling_device1/type
thermal-devfreq-0 |6|6|
sys/class/thermal/cooling_device10/type
ebi |1|1|
sys/class/thermal/cooling_device11/type
cx |1|1|
sys/class/thermal/cooling_device12/type
mx-cdev-lvl |1|1|
sys/class/thermal/cooling_device13/type
cdsp_vdd |1|1|
sys/class/thermal/cooling_device14/type
slpi_vdd |1|1|
sys/class/thermal/cooling_device15/type
adsp_vdd |1|1|
sys/class/thermal/cooling_device16/type
modem_pa |3|0|
sys/class/thermal/cooling_device17/type
modem_proc |3|0|
sys/class/thermal/cooling_device18/type
modem_vdd |1|1|
sys/class/thermal/cooling_device19/type
modem_current |3|0|
sys/class/thermal/cooling_device2/type
thermal-cpufreq-0 |18|18|
sys/class/thermal/cooling_device20/type
modem_skin |3|0|
sys/class/thermal/cooling_device3/type
thermal-cpufreq-1 |18|18|
sys/class/thermal/cooling_device4/type
thermal-cpufreq-2 |18|18|
sys/class/thermal/cooling_device5/type
thermal-cpufreq-3 |18|18|
sys/class/thermal/cooling_device6/type
thermal-cpufreq-4 |24|24|
sys/class/thermal/cooling_device7/type
thermal-cpufreq-5 |24|24|
sys/class/thermal/cooling_device8/type
thermal-cpufreq-6 |24|24|
sys/class/thermal/cooling_device9/type
thermal-cpufreq-7 |24|24|
To Properly show these Values i've modified the adb reading scripts i've found somewhere else on XDA...
You simply start the .bat file when connected via ADB... either trough USB, or connect phone via USB type "ADB tcpip 5555" unplug, when in WiFi use adb connect 192.168.1.XX:5555
Welcome back! ^^
Thermal Throttling & Task Migration / Load Balancing
When i first used this phone i tought i'd have Endless power in my hands, so i couldn't resist using it ALL. Started CPU Load Generator app and saw that even with 8 Threads fully loaded the phone does not throttle down CPU....
Sound awesome huh? Even the Temperature wasn't getting that hot. Coooool... (pun intended)
But i was a tiny wee bit Skeptical. Could it really be? So i've decided to use my USB Powermeter and charge my phone to 100%. After a while the phone kept using the same current. 0.255W to be accurate. (With Screen Off and WiFi connected)
using a Full Load i could see all CPU cores staying at the max Frequency.
But.... the wallcharger did say something different!
Not even a Full Minute! While it does peak at 8W it falls down to a sustaineable 4W rapidly. (Even drops to 3.5W Later on...)
So What's going on here?
Using Snapdragon Profiler with ADB over WiFi i've tried different Load Scenarios, 1-9 threads and 16 threads.
1 Thread:
You can see the Thread jumping between core 5, 6 and 7
2 Threads:
With 2 Threads core 4 is also used this time
3 Threads:
with 3 Threads Core 7 is not being used anymore... throttling? The phone is trying to reach a sustaineable temperature of 60°C by limiting Big cores to 2.4ghz
4 Threads:
While core 7 stays offline we see the small cores being used, and a throttling to 2.4ghz on big cores.
5 Threads:
While it did cool down enough to go back to the big cores previously, now it stays on small cores. Also 2.17ghz on big cores.
6 Threads:
7 Threads:
Dropping to 1.84ghz on big cores
8 Threads:
Aaaannndd... here is the magic! 2.8ghz on big cores! Somehow the phone switched to another throttling method than frequency.
9 Threads:
While we did see some slight CPU frequency drops with 8 threads, they're all gone with 9.
16 Threads:
Exactly the same as with 9 threads.
Sadly Snapdragon Profiler does not show BatteryPower on the XZ2 So it seems plugging to the WallCharger is the only way to figure this out.
I'll have to redo tests when my phone is fully charged and see if i can get a consistent powerdrain.
Edit: Update: Android P Beta.... Dev Preview 2
Starting with 4 Threads...
Core 7 does NOT get turned off anymore.... But you do see a small task migration as soon as 68°C are hit. Small cores get more load.
Looking at the Performance you see a gradual degradation, and not big spikes like before.
With 7 Threads:
We can see Thermal Limit has been increased to 72°C
The Performance drops really fast to 85%-90% but manages to stay there for a long long time. i'm really impressed.
Edit:
Absolutly nothing new with Android 10 (Again 8 Threads)
Powerdrain & Thermal Throttling
Okay... here we go... Wallcharger + Snapdragon Profiler...
First i've charged my phone fully to check Idle drain. Around 0.3W check.
About GPU testing:
You see the Idle 1.2W Powerdrain at the beginning? That's because Snapdragon Profiler is connected via ADB over WiFi. Quite a lot compared to the 0.3W Idle...
The first few Peaks until 12 Minutes are a failure because i've accidently started the sublevel Benchmarks^^
The first real Peak to 5.4W is a CarChase OnScreen.
The 1.7G on Clocks/Second is a reading error, normal Max is 710Mhz.
You can see the Temperature reaching 66°C and throttling starts, GPU going to 600Mhz, also Big Cores limiting to 2.17ghz.
The 2nd Peak is CarChase OffScreen.
You can see the big cores dropping in Frequency pretty early. GPU maxed out at 710mhz, until the phone reaches 68°C. GPU throttles heavily, and Big cores are going Offline putting the Load on small cores.
Which caused a drop in Powerusage from 5W to 3.7W
The last Peak is Manhatten OffScreen.
When Throttling starts at 68°C GPU drops from 710mhz to 600mhz and task migration from big to small cores.
The Powerdrain is reduced from 4.4W to 3.9W
About CPU testing:
Well.... that didn't work as well as expected... In the Powermonitor graph you can see i've used CPU Load Generator started with 1 Thread, and added 1 more after 1 Minute, until i had 4 threads.
Admittely the phone was already 45°C when i started this test... therefore i've already had throttling before i even started.... But well.... i've expected more...
The same peaks that are visible in the Powermonitor graph are also clearly visible in the temperature graph on Snapdragon Profiler.
So even if the phone is throttling, it allows Burstpower/increased thermal limit for new tasks, to reduce lag. Pretty neat.
Edit: Here we go... on a cold device:
As always, until Minute 1.2 is pure IDLE, from 2-2.7 is whit ADB over WiFi and Snapdragon Profiler connected.
At Minute 3 you see the start of the first Task. Using around 3.3W
At 4.2 you see the 2nd Task starting, generating 4.4W load
At 5.2 the 3rd Task starts, using up to 6.3W but shortly after (timestamp 225s in the graph below) the phone reaches 68°C and starts throttling. Load drops to 5W. because the continous Load of 5W is not sustaineable the phone throttles down to 4.1W (timestamp 245s)
Tt 6.2 Minutes the 4th Task is started, which generates 5.2W, this causes the phone to get almost 68°C again (timestamp 275s) and drops powerdrain to 3.3W, the phone cools down to about 60°C (timestamp 295s) and stop throttling, therefore peaking to 6.1W and rising to 68°C again in 10 seconds. Trying to limit powerdrain to 5.2W for the next 5 seconds fails, and task migration kicks in turning core7 offline and pushing load onto little cores. Limiting Big cores to 2.4ghz and using 3.9W
(timestamp 0s equals 2 Minutes on the other graph)
Edit2:
So what does that mean for Performance?
I've used the App CPU Throttling Test to create a workload and also Display it's performance. Here you can see 3 threads at work. Full Performance 125.9GIPS
The 2 Minute run does not throttle, Snapdragon Profiler proofs that
Using the app with 7 Threads causes throttling twice. But again, all cores are shown at full frequency.
Using Snapdragon Profiler we can see the phone throttling at 64°C (timestamp 447s) and later on at 60°C (timestamp 490s)
The performance drops from 125.9Gips to 104.9Gips. Nothing in Snapdragon profiler would indicate that.... CPU frequency stays the same and Load is also equal.
These graphs are such a pain
I have no clue where the Thermal Limit is on the P Beta.... but it seems to be quite high!
(click on Image to get redirected to interactive Chart from Google Sheets)
(The Drops are when i stopped testing and changed from 8 to 7 to 6 threads)
panel0-backlight thermal-devfreq-0 thermal-cpufreq-0 thermal-cpufreq-1 thermal-cpufreq-2 thermal-cpufreq-3 thermal-cpufreq-4 thermal-cpufreq-5 thermal-cpufreq-6 thermal-cpufreq-7
0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0
There is NO throttling due to Task Migration, thats what Snapdragon profiler said, and the value in sys/class/thermal/cooling_device0/cur_state proofs this. As you can see in the example above, they stayed at 0 during the whole test.
Which is nice to know, since now we're certain Performance throttling does not happen due to a value in thermal/cooling_device*
Edit:
Oh.... not sure if this is a P feature or happens on Oreo too... gotta test...
But when you reach 5% Battery big cores shovel all Tasks to small cores, therefore frequency drops to 800mhz and performance takes a HUGE hit.
This time we see all 4 big cores reach a value of 24 on sys/class/thermal/cooling_device* for thermal-cpufreq-4, 5, 6 and 7.
Edit 2: Thermal Throttling on Android P (dev preview 2)
Yeah... i need way more patience.... Did another test, this time while charging, so we have power Measurement!
We already knew Thermal limit was WAY higher on P.....
(interactive Chart...)
Because this was using External Power from Wallcharger the battery did not heat up as fast because it was not used. Took 10 minutes for the battery to reach 43°C while the starting point was about 32°C
What we did not know... the PowerLimit is different too!
on Oreo it peaks at 8W and then rapidly drops to 6W and even lower to 4W when the Limit kicks in.
Thanks to the bigger Thermal Headroom we have in P it only peaks to 6.5W and drops to 5.8W in 1 minute but after that it continuously falls from 5.8W to 5W in 10 Minutes! Seems like it manages to stay at 5W. Oreo couldn't handle that.
You Remember Qnovo Charging on the XZ2 ?
Haldi4803 said:
Qnovo in Action!
Click to expand...
Click to collapse
Well... it's not present in Android P Dev Preview 2.
We still have the typical CCCV point
But instead QuickCharge 3.0 is doing a good job in scaling Voltage.
Charging is fast, 105 minutes to 130 Minutes... but with Qnovo you have 93% at 105 Minutes, who cares about 7% If you have way better battery live.
Sadly Bluetooth Broke down after 70 Minutes.... oh well you can probably imagine what happens from minutes 70 to 130 right? ^^
Haldi4803 said:
You Remember Qnovo Charging on the XZ2 ?
Well... it's not present in Android P Dev Preview 2.
We still have the typical CCCV point
But instead QuickCharge 3.0 is doing a good job in scaling Voltage.
Charging is fast, 105 minutes to 130 Minutes... but with Qnovo you have 93% at 105 Minutes, who cares about 7% If you have way better battery live.
Sadly Bluetooth Broke down after 70 Minutes.... oh well you can probably imagine what happens from minutes 70 to 130 right? ^^
Click to expand...
Click to collapse
Coming from OnePlus, I'm not impressed at all. My 5T could do 0-93% in only 60 mins. Almost twice as fast... Old OnePlus phones didn't seem to suffer from battery degradation after more than a year either.
davidletterboyz said:
Coming from OnePlus, I'm not impressed at all. My 5T could do 0-93% in only 60 mins. Almost twice as fast... Old OnePlus phones didn't seem to suffer from battery degradation after more than a year either.
Click to expand...
Click to collapse
Firstly Sony is limiting itself to QC 3.0. Secondly seeing as higher end phones all pack high quality batteries, they all suffer little degradation in the first place. Sony's method might make them last even longer. Come back in 2 to 3 years time and compare the battery health before saying you are not impressed. Not everyone is rich like you people to change phones every year or less. There are people who think about really long term usage and this should benefit them considering how batteries are non user replaceable nowadays.
hotcakes_shinku said:
Firstly Sony is limiting itself to QC 3.0. Secondly seeing as higher end phones all pack high quality batteries, they all suffer little degradation in the first place. Sony's method might make them last even longer. Come back in 2 to 3 years time and compare the battery health before saying you are not impressed. Not everyone is rich like you people to change phones every year or less. There are people who think about really long term usage and this should benefit them considering how batteries are non user replaceable nowadays.
Click to expand...
Click to collapse
I said that because my friend is still using his OP3 and it's been two years. His SOT is still largely similar and he use Dash charge all the time.
And no I am not rich. Rich people buy iPhone.
hotcakes_shinku said:
Firstly Sony is limiting itself to QC 3.0. Secondly seeing as higher end phones all pack high quality batteries, they all suffer little degradation in the first place. Sony's method might make them last even longer. Come back in 2 to 3 years time and compare the battery health before saying you are not impressed. Not everyone is rich like you people to change phones every year or less. There are people who think about really long term usage and this should benefit them considering how batteries are non user replaceable nowadays.
Click to expand...
Click to collapse
one thing worth noting when it comes to battery life
What killed my battery on my Z1 (I replaced it twice) was doing nandroid backups with TWRP, I believe part of the problem is that all the OS battery control and protection is not running when you boot into recovery and it causes extreme overheating, it is definitely something to be aware of and IMO destroys batteries
Charging Android 10
Nothing much changed For the good or the bad ^^
Aftermarket Battery Tests
Aftermarket Battery Tests
Because i was unhappy with the Batterylife of my XZ2, it was nowhere near where it has been 2 years before, i decided to open my phone and replace the battery!
Opening your phone seems kinda easy, so no big issue. In theory... in practice you need to be aware of 2 important details.
You need new Glue to close it again. Afaik Witrigs is the only seller of that.
Be verry carefull on the bottom part. If you go too dep you will cut your Display cable and need to buy a new LCD for 35$. I'm speaking from experience....
How to test the battery?
Because the connector of the battery is proprietary and extremely compact you can't plug the battery directly, so i had to make use of the USB Power Delivery function to draw 5V out of the phone.
The Phone was in Flight mode with screen off, to make sure no other services use the battery. Then i connected a Load Generator i bought from aliexpress. Drawing 5V 1A my 2.5 year old battery lasted 1h33 min and gave out 7.6Wh
Original Battery:
Which has been in use for more than 2 years.
7.6Wh - 7.8Wh Obviously i did 2-3 Tests to see if i get the same every time. And it was always around that.
Hsabat 4300mAh Battery:
Bought from Aliexpress for 13.- Looks pretty decent. Is utter crap. As one expects.
First charge gave 7.3Wh, Second charge gave 5.6Wh and third charge gave 6.5Wh Not something you want to put in your phone.
Witrigs Battery:
Since i bought the glue there anway, why not just get a battery for 9$ and test that!
It looks bland (black) but hey... who cares as long as it works.... right? it works?.... well yeah...
First charge gave 7.3Wh and the others were also around that. "New" Battery? i Don't think so...
Phonedepot
Because i was disapointed that my old 2.5years harshly used battery has better capacity than **** i bought online i went to a swiss shop which has quality batteries... well yeah... at least is supposed to: Phonedepot.ch
It's more expensive but has faster shipping (as its close by) and the quality of the battery looks way better from the ouside.
I managed to draw 7.4Wh - 7.5Wh
Conclusion
Well... it was obvious before i even started.... i just didn't want to believe it.
Aftermarket batteries sucks. All of them!
Simply replacing your battery to get better batterylife is a dream. If youre battery broke down completly a replacement can help out, yes. But not if the battery is ageing normally.
This is extremely useful info, thank you for the tests.
Yeah, so this is a problem. As I mentioned earlier, I didn't bought any of those "new" batteries or aftermarket ones. All of them are a low quality piece of garbage so unless your battery is dead, literally, I wouldn't really buy these. This isn't any help from me and I am aware of that. The problem is, you can't really buy any genuine battery from anywhere. LG has a lot of genuine replacement parts and you even can buy from them directly, or from samsung. I tried looking on aliexpress but there are "replacement" batteries that are obviously fake or "original" that have the same serial numbers printed on them.
Official Battery Test!​Because i really couldn't let it be i wen't and bought an official Sony Battery.
Where do you get a Official Battery you ask? There is an Official Sony Homepage that lists Repair Centers. Here in Switzerland Sertronics is the official Repair center. Mailed them with the Part number and Foto of my Battery and got a quick answer.
28.- is an extremely fair price. the 16.- shipping are somewhat annoying.
So i got an Official Battery which Looks WAY better than the other ones.
Looks pretty much the same as my Original one right?
So let's get into Testing...
As Before I've used my Discharging Tool via USB Type-C with 1A draw the 5V dropped to something like 4.85V so 4.85W draw was used. Phone in Flightmode with Screen off to have almost no internal power usage.
Sadly i had issues with some kinda power Saver which killed the USB Power drawing at 10% Battery sometimes....
Run:Time to 10%Wh at 10%Time to 0%Wh at 0%Stock Run 11h 28min7.1Wh--Stock Run 21h 29min-1h37min7.8WhStock Run 31h 29min7.2Wh--New Battery Run 11h 22min (16%)6.6Wh (16%)--New Battery Run 21h 27min-1h 38min7.9WhNew Battery Run 31h 29min-1h 38min7.9Wh
Works pretty much the same. You can see the Voltage Drop at the end is not THAT bad as with the Original Battery. (Yes, both of them we're used until the phone did an Emergency Shutdown due to low battery, shows 0% in the Log)
Because these Results aren't really that good (And Yes, i've plugged the new battery and used my phone for one week to let it acclimate, i also did two Full resets with the new battery, one with newflasher) i've checked the Battery test in the Service Menu.
It truly is no good. I've bought a "Typical 3180mAh" battery that has a minimum of 3060mAh and then it offers 2654. My old battery was showing something around 2700mAh the last time i checked.
So yeah... it is a fully working as intended Battery without any flaws... BUT the capacity is WAY to low.
I will contact the repair center from Sony and ask what the think of this.
Judging by the marked numbers on the replacement Sony battery, it was manufactured between April 4th and 10th 2020 (20W18 - year 2020, week 18). So you received a one year old battery. I also have some experiences with batteries manufactured around that date (20W32). Very poor results: 2200 mAh at first charge, then goes down to a consistent 2000 mAh for all other ones. XZ1 Compact here.
Haldi4803 said:
I will contact the repair center from Sony and ask what the think of this.
Click to expand...
Click to collapse
What did they say? Did they at least accept it back?

Categories

Resources