Related
I was almost 100% sold on the Polaris as my next device but battery life is very important to me. I currently have an HTC P3300 (well, O2 XDA Orbit) and with the increased battery capacity of the Polaris (1350mAh vs 1200mAh in my Orbit) plus the claimed better specs from HTC (GSM 7 hours talk/400 hours standby for the Touch Cruise vs 3.5-5 hours talk/150-200 hours standby for the P3300) I really hoped that HTC had dodged any battery life issues.
I just found this review however (http://www.mobile88.com/mobilegallery/phonereview.asp?phone=HTC_Touch_Cruise&pg=review&prodid=20785&cat=37) and it has me worried. The bit I'm worried about is right at the bottom of the page:
<Start of summary of review results>
The multimedia cycle tests in comparison to the results demonstrated by the original Touch and P3300 are given below:
Multimedia-cycle, video (AVI) Polaris=4:08 Artemis=5:20 Elf=5:38
Multimedia-cycle, audio (MP3) Polaris=13:49 Artemis=21:34 Elf=18:07
<End of summary>
You can see that for MP3 the Polaris is way worse than the Artemis (I'm assuming the numbers are <hours>:<minutes> of play time). With what I commented on in my first paragraph these results really suprise me.
Does anyone know the conditions/details of the video and audio multimedia-cycle tests above? I'm wondering if somehow the conditions for the Polaris test were less favourable than those for the Artemis. Maybe the MP3 decoder software was different between the Artemis and the Polaris and the latter was dramatically less efficient although I'm probably clutching at straws here. Any other thoughts, comments or real life results from owners?
- Julian
funny how the 2 wm6 devices have lower batt time then the wm5 device
would be intresting if a test with an aramis with wm6 was don
Rudegar said:
funny how the 2 wm6 devices have lower batt time then the wm5 device
would be intresting if a test with an aramis with wm6 was don
Click to expand...
Click to collapse
That's a really interesting point. I was considering upgrading my device to WM6 using one of the cooked ROMs from this site, or the official O2 Orbit one, but I decided not to after seeing quite a few posts here by people who had done it and reported that the battery life on their devices went down a lot after upgrading to WM6 so I do wonder if that is the issue.
- Julian
I already ordered a second battery. I always do regardless of the device. One less thing to worry about
I am impressed with the battery capacity of the Polaris compared to my MIO A201. Running Tomtom without charging on the MIO A201 about 2 hours, with the Polaris 4 hours.
---Alex--- said:
I am impressed with the battery capacity of the Polaris compared to my MIO A201. Running Tomtom without charging on the MIO A201 about 2 hours, with the Polaris 4 hours.
Click to expand...
Click to collapse
What screen brightness is that set at? I'm assuming that the MP3 test results I quoted are with the screen blanked because if not then almost 24 hours on an Artemis with the screen on is pretty amazing.
If the tests do involve the screen being on (and surely they must with the video tests?) then I do wonder if the brightness settings were the same between the Artemis and Polaris tests.
If you look at some pictures further up in the review that I linked to in the first post of this thread then you can pretty clearly see that, I assume with both set to maximum brightness, the Polaris screen is noticeably brighter than the Artemis, so it isn't really fair on the Polaris to run any <screen on maximum> tests with both having the backlight set to full; it would be much fairer to adjust the Polaris backlight to give as close to possible the same brightness as the Artemis screen on full. Just maybe this accounts for some of the difference.
Thanks a lot Alex for the info on the TomTom results but I'd love to hear some real-life results of people playing music in a loop with the screen blanked and also discharge rates with the device just left at idle but with the auto-off and backlight-off disabled so that the screen stays alive. How much does the battery drain after 2 hours of sitting idle like this?
The reason I ask my questions is because the things that burn the most "activity hours" on my device are playing music with the screen blanked (hence my first request) and reading ebooks, for which my second requested test is probably a fairly reasonable approximation.
- Julian
They're comparing it to two devices with OMAP processors. Power savings is one of the reasons the OMAP was used before. It's either power or battery, rarely both unless the device is large. You could probably underclock to increase battery life.
JwY said:
They're comparing it to two devices with OMAP processors. Power savings is one of the reasons the OMAP was used before. It's either power or battery, rarely both unless the device is large. You could probably underclock to increase battery life.
Click to expand...
Click to collapse
You hit the nail right on the head. I have not bothereed to check the source so I do not know the purpsoe of the test. In any case if you want 3 days of music you would be better of with an iP.... If you want processing power then you look for a device that will not make you fall asleep just waiting for a page to refresh
JwY said:
They're comparing it to two devices with OMAP processors. Power savings is one of the reasons the OMAP was used before. It's either power or battery, rarely both unless the device is large. You could probably underclock to increase battery life.
Click to expand...
Click to collapse
I was expecting someone to say this and I'm afraid that my hunch, which I am willing to admit could be wrong, makes me disagree with this. There is some reasoning to justify my hunch and it goes as follows.
Make the following assumptions (all numbers chosen for ease of arithmetic rather than accuracy since I am just trying to demonstrate a principle rather than derive results):
1) Yes, the CPU in the Polaris is more powerful than the one in the Artemis and lets assume that the Polaris CPU (PCPU for short) is exactly twice as powerful as the Artemis CPU (ACPU for short). By twice as powerful I mean that in any given second the PCPU will process twice as many instructions as the ACPU.
2) I am assuming that both CPUs have some sort of speed stepping technology such that, when they are not under load, the power consumption drops significantly to a fairly trivial value and I will assume that for both CPUs the idle power consumption is equivalent.
3) Assume that at full load the PCPU has twice the power consumption of the ACPU.
4) Assume that it takes a 100,000,000 instructions to decode and play 1 second of music (i.e. 100MIPS = 100 million instructions per second) and that the ACPU can only just manage this so when playing music the ACPU is at 100% load for 100% of the time.
With the above assumptions my point now is that a more powerful CPU won't create a serious decline in battery life when playing music because the 100 million instructions required to be executed for 1 second of music is constant so a 100MIPS processor will need to run flat out constantly to play music whereas a 200MIPS processor will only need to be at 100% load for 0.5 seconds in any given second and for the rest of the time it can be speed stepped right down. With the idealised assumptions above there would actually be no impact whatsoever on power consumption for any arbitrary processor power (for processors that have at least sufficient power to keep up with the music stream).
A further piece of real life evidence is, if it is solely or even predominantly down to the processor, then why is the Elf managing 18:07 on the MP3 test compared to the Artemis 13:49 (and that I believe this is with a smaller battery than the Artemis, 1100mAh vs 1250mAh; info taken from the specs on the HTC web site)?
Maybe assumption (2) is wrong which does hurt my argument somewhat, or maybe there are software differences, in the MP3 player and/or in WM6 itself, that stops the PCPU dropping its power consumption down as much when it's not actively decoding, but that Elf vs Artemis test result difference still makes me wonder what else is going on.
Honestly, I'm really hoping this is just due to a badly run test on the Polaris (not same conditions as Artemis test) and that the result is an Anomaly.
- Julian
I've had the xda Stellar (tytn II), which is very very similar to the polaris, for the last week, and the battery is, I'm sorry to say, the worse I've ever come across.
For the first few days, I was using it heavily and managed 1.5 days. Figured this would increase as I used it less. Took it off charge 5 hours ago, made a 20 minute phone call, sent 3 text messages, and used the word processor for 30 minutes. 75% battery left.
I'm sending it back and waiting for the Orbit 2 to be released. Fingers crossed the keyboard has some strange battery draining feature.
sonesh said:
I've had the xda Stellar (tytn II), which is very very similar to the polaris, for the last week, and the battery is, I'm sorry to say, the worse I've ever come across.
Click to expand...
Click to collapse
The Stellar only has an 1100mAh battery while the Polaris has 1350mAh. Sounds little but makkes a differece of 200 (yes, 200!) hours of StandBy time.
This means the Stellar specs say 250h whereas the Polais spec sheet says 450h.
sonesh said:
For the first few days, I was using it heavily and managed 1.5 days. Figured this would increase as I used it less. Took it off charge 5 hours ago, made a 20 minute phone call, sent 3 text messages, and used the word processor for 30 minutes. 75% battery left.
Click to expand...
Click to collapse
Yeah. That's very bad. I wonder if there's something wrong with your unit. According to the spec on the HTC web site you should be getting talk time of "Up to 264 minutes for UMTS - Up to 420 minutes for GSM". As far as I'm aware holding a call is by far the most battery-draining thing you can do on a device so if we count your 30 minutes of word processing as another 30 minutes of talk time we're probably grossly over-estimating but, on that assumption (and adding 5 minutes for the texts) that's only an equivalent of 55 minutes of talk time. Were you on 3G or GSM for all this? I suppose if it was 3G then maybe you could have expected the battery to be down to 79% but if it was GSM then the battery really shouldn't have been much below 87%.
Admittedly I think these talk time figures quoted by manufacturers are in very ideal conditions (i.e. very high signal strength from the mast) so what sort of reception area you were in when you made the call is an issue but I think that is probably counteracted by the fact that I probably vastly overestimated the power drain when word processing.
An interesting (free) utility is abcPowerMeter (http://www.acbpocketsoft.com/). It would be very interesting to compare the current consumption on the Artemis, the Polaris and the Tyan II.
If anyone is up for this then I suggest the state to test would be with the system sitting on the today screen, disable the auto-off but do allow the backlight to go off or manually disable it so that differing screen brightness isn't a factor. Also put the phone into flight mode so that all radios are off (to factor out any effects of different signal strengths) and then start abcPowerMeter and let it run for about 30 minutes during which time it should, in theory, settle to a pretty straight line showing the current drawn from the battery in this state.
I would most certainly do an Artemis (or rather O2 XDA Orbit) test but unfortunately the reason for my intense interest in all things Polaris is that my Orbit died on new year's eve (no, I didn't drop it or sit on it at a party!) so my device is totally dead.
- Julian
Could the Today plugins be making a difference? I'm thinking particularly the weather plugin. I've seen other discussions where people report battery life problems on various devices and one often-mentioned that people suggest to check is what Today plugins are running.
With the new devices now 3G, and 3G using a lot more power than 2/2.5G when active, I'm wondering if the weather plugin is causing 3G to be active and hurting power. How often does the weather plugin connect and can it be disabled? Not wanting to take the thread off topic but one thing I'd like to do if/when I get a Polaris is to disable the weather plugin on the Today screen, is this possible?
For my use, since I am concerned about battery life, I intend to keep my device in GSM mode and only switch to 3G when I want to connect to the internet and, when finished, I will immediately disable 3G again. I certainly don't want any plugins regularly polling the internet and turning stuff on without my permission.
- Julian
acbPowerMeter
I installed acbPowerMeter this afternoon, after noticing that my battery was draining extremely fast (~ 4 to 5 hours). The tool showed that the TC was using approx 320mA on average
I've been running the tool for some hours now, and after two hours the power consumption slowly lowered. I've been switching the screen off and on and have had the GSM radio on all the time. The avg value returned to ~20mA.
I'll keep an eye on power consumption, because now I don't trust the device anymore. I don't know what caused the huge change in power consumption in the first place.
Thanks for those test results Muyz. It's great to have some real data, but I'm sorry to hear that you're having battery problems too.
Regarding your results, did you start abcPowerMeter (APM for short) while your device was still plugged into the USB port? I noticed that when I had APM running when my device was charging then I got a very high mA reading (about 250mA on my 1200mAh O2 XDA Orbit) so I think the fact that there is charge current coming in confuses APM somewhat and, for the average, it could be that after you unplug it will take a while for the minutes or hours of false high readings to creep out of the statistics. I always made very sure that my device was fully unplugged before starting an APM session.
Regarding the 20mAh reading, that actually sounds very good to me. Unfortunately I'm recalling all this from memory because, as I said in an earlier post, my device is now totally dead, but I seem to remember about 29mA as as low as I saw. With the screen on the figure of 79mA sticks in my mind. As with you, these figures were all with GSM on. I had Bluetooth and WiFi disabled.
One thing that really suprised me with my tests was that, when I had a good GSM signal, I couldn't detect any difference in current drain between having GSM switched on or off (just registered to the network of course, not actually with a call active). The additional current drawn from having GSM on didn't even seem to be 1mA. The story is different in a no-signal area where the GSM keeps searching for a signal, that drained the battery really quickly.
- Julian
3G CONNECTION need more battery consumation(if you dont need disable), configure for normale use GSM, and the duration is guarantee...
New battery monitor tool
I've discovered a serious bug in the acbPowerMeter tool. The implementation of the tool does not use the proper types
This is why I've done a little programming myself last evening. The attachment to this tool contains a preliminary version of my own battery monitoring tool. It provides the correct battery readings for remaining power and current power consumption. One can adjust the polling frequency. I will complete the tool somewhere this or next week and put it on my website for download (freeware).
Muyz said:
I've discovered a serious bug in the acbPowerMeter tool. The implementation of the tool does not use the proper types
This is why I've done a little programming myself last evening. The attachment to this tool contains a preliminary version of my own battery monitoring tool. It provides the correct battery readings for remaining power and current power consumption. One can adjust the polling frequency. I will complete the tool somewhere this or next week and put it on my website for download (freeware).
Click to expand...
Click to collapse
Hi Muyz,
Not wanting to jinx this, but I'm cautiously optimistic that I just un-bricked my O2 XDA Orbit (Artemis) so, as long as it doesn't go bad on me again I might now be in a position to contribute Artemis (or re-branded Artemis) data for comparison.
In preperation for the tests I'm really interested in what are the problems you found with abcPowerMeter. You say above that it "does not use the proper types". What do you mean by this? As a (fairly old) computer scientist this immediately makes me think of types as in a typed computer language (e.g. it's declaring something as int instead of long or short instead of bool). Is this what you mean? Please excuse my ignorance, I know theory but have never been anywhere near any Windows, let alone Windows Mobile, programming environments; if you do mean language types then how did you detect this without the source code (or did you find that somehow or disassemble)?
If you don't mean variable typing then what do you mean?
In any event, many thanks for the work Muyz.
I un-bricked my device by re-flashing (twice) the official O2 WM6 ROM so when (assuming my device stays stable) I start running current consumption tests then I think it's probably quite good that I upgraded my device to WM6 because that removes one variable (is the current drain a WM5 -> WM6 issue?) so we can at least compare Artemis to Polaris on a fairly like-for-like basis regarding the OS version.
I'm really glad I started this thread, I think there's been some really interesting and useful discussion here and I certainly wasn't expecting to have people jumping in and posting fixed versions of the current-monitoring software, that was a really nice surprise (but I'm still really looking forward to hearing exactly what the issue was).
- Julian
Battery life in cooked ROMs - weather plugin
Hi guys,
in some cooked ROMs there seems to be a bug in the radio rom or simply in general. I've read several posts where people had the gsm units in their Artemis on full power most of the time causing the device to lose power very fast. This happened only with cooked ROMs, not with official versions. They noticed that when they had their phone close to speakers which caused the buzzing noise that you usually get when there is an incoming call or short message.
The other thing that consumes power is the weather plugin, but only when you have the auto-update activated! I disabled it and never had problems.
I think I'll buy this device anyways, haven't read any serious reasons not to buy it.
Thanks for your response, and I hope your device works properly now.
About the type issue: acdPowerMeter (obviously) uses the Windows API to retrieve battery information. It receives the information through a structure that contains signed integers. It seems as if acbPowerSoft managed to introduce a typing error by using unsigned integers instead of signed integers. The effect is that for negative values (e.g. when current is drawn from the battery), acbPowerMeter shows extremely large values. I discovered what is the most likely reason for this mistake: Microsoft shows an example on their website on how to retrieve battery status information. Their example shows the error clearly: the C# class use unsigned integers, whereas the native structure contains signed integers as you can see here. So I guess acbPocketSoft copied some code without checking the result
I do not have a clue on what caused the extreme battery drain I encountered a few days ago. I have not seen it since. Soon, my tool will include a warning mechanism. I first added a few other small things, such as battery temperature, as you can see in the new attachment
(Yes, I know, it contains a small glitch on exiting the application, but that will be fixed asap)
:[Disclaimer]:
Use this at your own risk!
:[Extra Disclaimer]:
This alters the way the Epic charges the battery.
Precaution has been taken to not exceed "normal" values, but when dealing with batteries (and their various sources and quality) there is always a chance something could go horribly wrong.
If you are in any way worried about this, then please move on, as this is not for you.
If you bought an extended battery off ebay and are worried your battery might explode, then please move on, as this is not for you.
This should be considered experimental, and only people who wish to experiment should use it.
There may come a time this will be incorporated into more (all?) kernels, but until then, you have been warned!
:[Requirements]:
Built for and tested on EB13 / EC05 EXT4.
:[Description]:
This is a tweak of the values that are used by the Epic to determine when the battery is at it's fully charged state, and when it should begin it's recharge state.
This is built on Bonsai 3.0.1
It includes the following: tun support, cifs support, 1.2GHz Overclock, autogroup scheduling, keyboard fix (thanks mkasick), video mode fix (thanks again mkasick), etc.
Thank you to all the devs who have contributed and I haven't listed (pm me).
I have also implemented nullghost's Idle timer from 2.6.34 thanks to ACS and nullghost.
[update]
I have also implemented the changes from the EC05 kernel, thanks to Rodderik.
And the scaling_available_frequencies sysfs interface thanks again to nullghost.
[update]
Attached source files for those who want them.
:[Features]:
Alters the "fully charged notification" to be more accurate.
Charges the battery to near full capacity.
Allows for less drain before the "recharge" kicks in.
Gives you a better chance at having a full charge when unplugging.
[update]
Provides over charge protection in the form of a max voltage cut-off.
Increased charge rates (mA) in both USB and AC modes.
There is a chance this change could cause fire or explosion!
Understand this is trial and error!
Even tho I've tested this for the past couple days, there is still a chance you will have a problem where I have not!
Especially if you use a charger other than a stock charger (rated at 0.7A)!
!!Again, you have been warned!!
Adjusted calculations for the fuel gauge (battery level percentage).
I have added a few kernel debug messages that can be seen using dmesg.
"OS Monitor" free in the market will allow you to view them (filter tag = [BATT).
:[What this does not do]:
This does not alter any of the following built in protections:
Max total charge time of 5 hours.
Max total recharge time of 2 hours.
Low battery voltage condition of 3400 (used for auto shutdown).
Low battery level condition of 0 (used for auto shutdown).This does not change the charge rate (current coming from the charger).
So no, it wont charge your phone faster (well technically it does, but only during the higher voltages where you would normally be "recharging" on a stock kernel).
:[Recommendations]:
Go download the free app "Battery Monitor Widget". Go into the settings and make sure that "Monitor without widget" is enabled (checked).
The app has a really nice history feature that I find useful, and can be used to help track things with this kernel.
:[Details]:
From the code (original and older values commented out)::
(Some line numbers might be a little off, as I have added some debug messages.)
[Full charge and Recharge adjustments]
Kernel/drivers/power/victory/s5pc110_battery.h: Line 166
Code:
#define BATT_RECHARGE_COUNT [COLOR="Blue"]15[/COLOR]//20
Kernel/drivers/power/victory/s5pc110_battery.h: Lines 170 ~ 173
Code:
#define OVER_CHARGE_COND_VOLTAGE [COLOR="Blue"]4210[/COLOR]// nubecoder
#define FULL_CHARGE_COND_VOLTAGE [COLOR="Blue"]4190[/COLOR]//4170//4000
#define RECHARGE_COND_VOLTAGE [COLOR="Blue"]4150[/COLOR]//4140//4110 // 2010.05.08.
#define RECHARGE_COND_VOLTAGE_BACKUP [COLOR="Blue"]4090[/COLOR]//4110//4000
Kernel/drivers/power/victory/s5pc110_battery.h: Lines 184 ~ 185
Code:
#define CURRENT_OF_FULL_CHG [COLOR="Blue"]60[/COLOR]//90//91 // 2010.05.08.
#define CHG_CURRENT_COUNT [COLOR="Blue"]15[/COLOR]//20
Which means:
When voltage is greater than or equal to 4190(mV) and current is less than or equal to 60(mA), full charge has been achieved.
When voltage is below 4150(mV) or 4090(mV), recharge activates (what determines if "backup" is used a Samsung mystery).
The current and recharge count values are also somewhat of a mystery, I decreased them to have a bit more consistent charge behavior.
[Over charge protection]
Kernel/drivers/power/victory/s5pc110_battery.c: Lines 438 ~ 444 and 458 ~ 464
Code:
if (s3c_bat_info.bat_info.batt_vol >= OVER_CHARGE_COND_VOLTAGE) {
s3c_set_chg_en(0);//Set charge off
s3c_bat_info.bat_info.batt_is_full = 1;
force_update = 1;
}
Which means:
If voltage is greater than or equal to 4210mV stop charging.
[Increased charge rate]
Kernel/drivers/regulator/victory/max9889_function.c: Line 3092
Code:
reg_buff[0] = (0x0 <<5) |(0x3 << 3) | /*(0x5<<0)*/ [COLOR="Blue"](0x6<<0)[/COLOR] ; // CHG_TOPOFF_TH=10%, CHG_RST_HYS=Disable, AC_FCGH=600mA // ???mA
Kernel/drivers/regulator/victory/max9889_function.c: Line 3106
Code:
reg_buff[0] = (0x0 <<5) |(0x3 << 3) |/*(0x1<<0)*/ [COLOR="Blue"](0x3<<0)[/COLOR] ; // CHG_TOPOFF_TH=10%, CHG_RST_HYS=Disable, AC_FCGH=380mA // ???mA
Based on some rudimentary calculations this translates to:
Code:
AC: @320mA which translates to @704mA
USB: @249mA which translates to @548mA
Note:: This was tested with a stock cable and charger for AC, and a stock cable and a direct laptop port for USB.
For more information read this post.
[Adjusted fuel gauge (battery level percentage)]
Kernel/drivers/power/victory/fuel_gauge.c: Line 159
Code:
adj_soc = (((data[0]*10) - 15) * 100) / (/*950*/ [COLOR="Blue"]980[/COLOR] - 15); // hanapark_Atlas
Which means:
Instead of rounding 95% up to 100% round 98% up to 100%.
:[WishList]:
Fixing the battery percentage output to be more accurate. (Partially done, we'll see how it goes.)
Adjusting the values to what I feel is the best charging experience (while still remaining "safe").
Possibly(?) increasing the charge rate to enable faster charging.
:[Testing]:
This has been tested on an Epic 4G running Bonsai 4.0.0b2 with a stock battery.
This build has not been tested on an extended battery (yet).
:[Feedback]:
Please post your feedback, I'd like to know some of the values reported when full charge occurs, when recharge starts / stops, if you've noticed your battery keeps charge longer / less, etc...
[Download HERE]
Download no longer available...
:[Special thanks]:
jaronow, for initial testing.
:[ChangeLog]:
Code:
v0.0.2 (03-22-2011)
Attached current source files to this post.
v0.0.2 (03-22-2011)
Added over charge protection cut-off of 4210mV.
Increased full charge voltage to 4190mV.
Increased recharge cond voltage to 4150mV.
Decreased recharge backup cond voltage to 4090mV.
Decreased full charge current condition to 60mA.
Decreased charge current count to 15.
Decreased recharge count to 15
Increased charge rate for AC from an estimated 600mA to @ 704mA.
Increased charge rate for USB from an estimated 380mA to @ 548mA.
Adjusted fuel gauge to be more accurate.
v0.0.1 (03-16-2011)
Initial Release
=]
Guinea Pig Number #1 reporting for duty!!! My phone booted up ok and did not explode!
I am using the Midnight Rom 4.2 Byor Edition so far my phone has booted up ok. I am charging my phone right now as we speak. I will do benchmark speeds when my phone is done charge up fully. I wiped my partination cache and the Dilvke cache too. I am trying to get a full charge.
Sweet Awesome work bro 8)
is this just a kernal flash? can't see what the file is from work. also, is it still the bonsai kernal? so smart ass governor still an option?
is it relatively simple to jack up the charge rate? my friends iphone charges in like an hour or less. mine takes at least 3 hours. annoying to say the least.
removed root for me
What makes the smartass governor special.
Can I keep my phone on 1.2 GHZ and the smartass governor will only use as much power it needs to complete the task at hand or would I save battery life by putting my phone on 800 MHz or it does not matter? Great Rom Kernal fast and efficient. The first time I flashed it I go slow benchmark scores but the score kept on improving and now they are pretty close to the score on the Bonsai Rom Kernal and this Rom gives you a fuller battery charge. I am loving this Kernal I highly recommend it. It is the best kernal I have tried so far and I have tried a lot of kernals in my day. This experimental kernal is the best kernal I have put in my phone this could be my daily driver. I have to give it a full day's test. So far so good not problems to report yet.
thank you! loved this kernels on my evo! will try today/tonight!
ms79723 said:
removed root for me
Click to expand...
Click to collapse
you running syndicate? i think i read the other day that root is in the kernel in syndicate. just run the 1 click root again
The other day I was looking at how to get a little more "umph" from the USB port charging. Do you think that we could tinker with this
Code:
static void s3c_set_chg_en(int enable)
{
int chg_en_val = maxim_chg_status();
if (enable) {
if (chg_en_val) {
if(curent_device_type==PM_CHARGER_TA)
maxim_charging_control(PM_CHARGER_TA, TRUE);
else if (curent_device_type==PM_CHARGER_USB_INSERT)
maxim_charging_control(PM_CHARGER_USB_INSERT, TRUE);
else{
maxim_charging_control(PM_CHARGER_DEFAULT, FALSE);
}
s3c_set_time_for_charging(1);
}
} else {
maxim_charging_control(PM_CHARGER_DEFAULT, FALSE);
s3c_set_time_for_charging(0);
s3c_bat_info.bat_info.batt_is_recharging = 0;
s3c_bat_info.bat_info.batt_current = 0; // hanapark_Victory
}
s3c_bat_info.bat_info.charging_enabled = enable;
}
Making it think that is never is plugged into anything but the wall charger would cause a little more current to be pushed through, and since we only pull like 600 mah from the wall, I think a could USB port/ Cord could handle it.
If none of that makes since, just tell me. I haven't spent more than a few minutes reading through the code that is there, and I really don't know too much about this stuff anyways.
Is this similar to the evo's sbc kernal where it will allow to fully (Trickle) charge an extended battery?
robl45 said:
is this just a kernal flash? can't see what the file is from work. also, is it still the bonsai kernal? so smart ass governor still an option?
is it relatively simple to jack up the charge rate? my friends iphone charges in like an hour or less. mine takes at least 3 hours. annoying to say the least.
Click to expand...
Click to collapse
Yes this is just a kernel, and yes this is based on the Bonsai kernel, anything that is included in the sources available here is included.
I've also added the 2.6.34 Idle timer that nullghost has given to us (taken from the ACS github, Thanks for your hard work guys!).
ms79723 said:
removed root for me
Click to expand...
Click to collapse
It seems that some Roms have root included in the kernel, which is not the case for Bonsai (and therefore this kernel as well).
ps- Thanks for your work on the SBC kernel for the Evo! This was definitely inspired by it.
vide infra said:
thank you! loved this kernels on my evo! will try today/tonight!
[snipped]
Click to expand...
Click to collapse
asj2583 said:
Is this similar to the evo's sbc kernal where it will allow to fully (Trickle) charge an extended battery?
Click to expand...
Click to collapse
This is not quite the same as the SBC kernel for the Evo (this does not trickle-charge).
It differs in that, the Epic already performs a "bump-charge" by default.
This kernel is a simple modification of the values used to determine when the bump charging occurs, etc.
So this is, more or less, just a modification of the stock charging behavior.
=]
Kcarpenter said:
The other day I was looking at how to get a little more "umph" from the USB port charging. Do you think that we could tinker with this
Code:
[snipped]
Making it think that is never is plugged into anything but the wall charger would cause a little more current to be pushed through, and since we only pull like 600 mah from the wall, I think a could USB port/ Cord could handle it.
If none of that makes since, just tell me. I haven't spent more than a few minutes reading through the code that is there, and I really don't know too much about this stuff anyways.
Click to expand...
Click to collapse
You sir, get a separate reply ;]
You are correct that you could change that code to force the USB into thinking it's being charged via AC, but I feel that would be a bad choice in implementation.
Rather check the code here:
/drivers/regulator/victory/max8998_function.c Lines: 3089 ~ 3118
Code:
else if(dev_type==PM_CHARGER_TA)
{
// hanapark_Victory (2010.05.12)
[COLOR="Blue"]reg_buff[0] = (0x0 <<5) |(0x3 << 3) |(0x5<<0) ; // CHG_TOPOFF_TH=10%, CHG_RST_HYS=Disable, AC_FCGH=600mA[/COLOR]
reg_buff[1] = (0x2<<6) |(0x3<<4) | (0x0<<3) | (0x0<<1) | (0x0<<0); //ESAFEOUT1,2= 10, FCHG_TMR=disable, MBAT_REG_TH=4.2V, MBATT_THERM_REG=105C
#ifdef CONFIG_KERNEL_DEBUG_SEC
kernel_sec_clear_upload_magic_number(); // hanapark_DF01
#endif
Set_MAX8998_PM_ADDR(CHGR1, reg_buff, 2);
//printk("%s TA charging enable \n",__func__);
}
else if(dev_type==PM_CHARGER_USB_INSERT)
{
value = FSA9480_PMIC_CP_USB();
// hanapark_Victory (2010.05.12)
[COLOR="Blue"]reg_buff[0] = (0x0 <<5) |(0x3 << 3) |(0x1<<0) ; // CHG_TOPOFF_TH=10%, CHG_RST_HYS=Disable, AC_FCGH=380mA[/COLOR]
if(value){
if (askonstatus)
reg_buff[1] = (0x1<<6) |(0x3<<4) | (0x0<<3) | (0x0<<1) | (0x0<<0); //ESAFEOUT1,2= 01, FCHG_TMR=disable, MBAT_REG_TH=4.2V, MBATT_THERM_REG=105C
else
reg_buff[1] = (0x3<<6) |(0x3<<4) | (0x0<<3) | (0x0<<1) | (0x0<<0); //ESAFEOUT1,2= 11, FCHG_TMR=disable, MBAT_REG_TH=4.2V, MBATT_THERM_REG=105C
}
else
reg_buff[1] = (0x2<<5) |(0x3<<4) | (0x0<<3) | (0x0<<1) | (0x0<<0); //ESAFEOUT1,2= 01, FCHG_TMR=disable, MBAT_REG_TH=4.2V, MBATT_THERM_REG=105C
#ifdef CONFIG_KERNEL_DEBUG_SEC
kernel_sec_clear_upload_magic_number(); // hanapark_DF01
#endif
Set_MAX8998_PM_ADDR(CHGR1, reg_buff, 2);
//printk("%s USB charging enable \n",__func__);
}
I believe it would be better to adjust the values marked above.
But I'm no good with bit shifting code, and I haven't yet figured out what to change the values to.
Of course we (you?) could simply change the value and see what happens, but I prefer to (at least somewhat) understand what I'm doing when I apply a change.
So that is why I haven't messed with it yet, more research needs to be done IMO.
If you do decide to try this, let me know how it goes.
And remember the USB spec says that it only gives out 500mA max.
=]
Well in that case ill be building tonight..... just needed a little refirmation from someone. Makes me sleep bettr at night.
Sent from my Samsung-SPH-D700 using XDA App
FWIW, we used something from no2chem called "Fast Charge" on WinMo, back when I used a Diamond.
It would charge around 900 maH(much less than Diamond's 1340 MaH battery) on USB and AC and drop down(trickle charge) once it reached 90 percent.
"A quick test from a usb2 port shows the following approx values:
At 50% charge, charges at 918mA
50 minutes later, battery is at 90% and charging at 462mA"
Batteries can accept up to their mA in charging, and since the batteries aren't usually spot on to their rated mA, I'd say we'd be safe up until about 1200 mA charging.
If all that makes sense, it's been a while since I've devved and had to learn all that good stuff.
EDIT: @Kcarp: I've got like 4 OEM batteries here, I'm willing to put at least one of them towards testing, assuming it's not going to harm the phone and would be a battery only affair.
mA and mAh are completely different units, one measures current and one measures capacity.
Sent from my Samsung-SPH-D700 using Tapatalk
My Battery has been charging for 4 hours and it is at 60%
My battery has been charging for 4 hours and it is only at 60% what gives? It is at taking a long time to recharge my battery.
intx said:
FWIW, we used something from no2chem called "Fast Charge" on WinMo, back when I used a Diamond.
It would charge around 900 maH(much less than Diamond's 1340 MaH battery) on USB and AC and drop down(trickle charge) once it reached 90 percent.
"A quick test from a usb2 port shows the following approx values:
At 50% charge, charges at 918mA
50 minutes later, battery is at 90% and charging at 462mA"
Batteries can accept up to their mA in charging, and since the batteries aren't usually spot on to their rated mA, I'd say we'd be safe up until about 1200 mA charging.
If all that makes sense, it's been a while since I've devved and had to learn all that good stuff.
EDIT: @Kcarp: I've got like 4 OEM batteries here, I'm willing to put at least one of them towards testing, assuming it's not going to harm the phone and would be a battery only affair.
Click to expand...
Click to collapse
Yep, I always loaded the fast charger drivers from no2chem on my TP1 and TP2. Enjoyed the increased charging rate from the car charger, usb, and other chargers.
That's the one thing I missed when I moved from the TP2 to the Epic...the Epic was god awful slow at charging!
Well, forgot that the hdd on my laptop has become "unstable" gotta go buy one, probably be tomorrow night before I can build I might try building anyways...it still boots, just locks up and makes god awful noises...we shall see I guess.
Sent from my Samsung-SPH-D700 using XDA App
jamice4u said:
My battery has been charging for 4 hours and it is only at 60% what gives? It is at taking a long time to recharge my battery.
Click to expand...
Click to collapse
What you have reported is not normal behavior.
Did you get the battery monitor widget? Could you post some of the history?
I would suggest you unplug from the charger, reboot into CWM, clear the battery stats, and reboot.
Sometimes the percentage readout behaves strangely, some people have reported that rebooting the phone drastically changes their reported percentages.
(Not on this kernel, but it's been mentioned at least a couple times in the Bonsai thread.)
Maybe you are experiencing this?
If you battery has been charging for 4hrs+ and isn't increasing it's percentage, then something is going wrong and needs to be investigated.
This is where the monitor widget comes in handy, what voltage is being reported, what current (mA) is being pumped into the phone, etc.
=]
i tried the kernal, took like 3 1/2 hours to charge up from 35% or so. but i dont know that we are really gaining much, what are we getting,another 2%?
if we could increase the charge rate, that would be something.
Here are 2 bugs I would like to report you loose root, the superuser icon is there, but you can't let special apps ask for permission. 2nd, the kernel is not supported for wirless tether, I am using the snydicate rom if that makes a difference.
Thanks for the kernel, I see great promise in it
Okay, needless to say, operating systems like iOS and Android are improving plus the new processors heading to dual core. However, battery technology is way behind I think. What improvements are needed in this field to get a smartphone working for a week on one charge (not realistic but ideal)?
Fuel cells?
New alloys?
What would work to help our battery technology which is falling behind?
Battery technology is far behind but it has been for over 100 years. For electric cars Toyota claims to have a new battery with 2-3x the power density of current batteries. Although for general purpose I believe Lithium Phosphate is still the current state of the art technology.
Fuel Cells are neat technology but not yet that practical just like 10year miniature nuclear cells.
The biggest problems in my opinion are
1. phone size (everything is getting so thin or small in general) leaving less room for a battery
2. screen size (huge touchscreen = big power draw), and other things too that impact battery life.
3. things that run in the background keeping the phone cpu in something other than its lowest power state
4. screen brightness. Seems trivial but can make a big difference and I think all phones should have ambient light sensors are change automatically.
5. internet connectivity. It goes along with #3 in that it wakes the cpu, but also the current wireless chipsets don't seem all that energy efficient. Using any connectivity cellular, wifi, or bluetooth really eats the battery. Many report turning off wifi, bluetooth, and using 2g when possible significantly improve battery life.
Personally I have the biggest battery I could get for my phone and my laptop too. My 17" laptop runs 4.5 hrs at lowest brightness and 3 hrs at the brightest setting. Most phones aren't much different.
Sorry long rant...... does that break down your question correctly?
landoftheeskimos said:
Battery technology is far behind but it has been for over 100 years. For electric cars Toyota claims to have a new battery with 2-3x the power density of current batteries. Although for general purpose I believe Lithium Phosphate is still the current state of the art technology.
Fuel Cells are neat technology but not yet that practical just like 10year miniature nuclear cells.
The biggest problems in my opinion are
1. phone size (everything is getting so thin or small in general) leaving less room for a battery
2. screen size (huge touchscreen = big power draw), and other things too that impact battery life.
3. things that run in the background keeping the phone cpu in something other than its lowest power state
4. screen brightness. Seems trivial but can make a big difference and I think all phones should have ambient light sensors are change automatically.
5. internet connectivity. It goes along with #3 in that it wakes the cpu, but also the current wireless chipsets don't seem all that energy efficient. Using any connectivity cellular, wifi, or bluetooth really eats the battery. Many report turning off wifi, bluetooth, and using 2g when possible significantly improve battery life.
Personally I have the biggest battery I could get for my phone and my laptop too. My 17" laptop runs 4.5 hrs at lowest brightness and 3 hrs at the brightest setting. Most phones aren't much different.
Sorry long rant...... does that break down your question correctly?
Click to expand...
Click to collapse
It sure does for me thanks
nova display and amoled plus is good for battery
li-po is more efficient than li-ion
dual core is more efficient about 40% than single core (in ginger bread)
Cycled 3 times now and the first day with moderate use I went about 8-9 hours. It was awesome. Now that I'm using it a little heavier and will actually be using it quite heavily with data, gps, browsing, phone calls etc. I am noticing maybe that really isn't enough... I need like 12 hours or more like I hear some people are getting...
So I ask you XDA, what is THE BEST way for me to achieve super long battery life with heavy use. I'm already using SetCPU (settings below)
2100 maH battery? (Will this even be a huge difference from our current battery? I don't know what our stock battery maH is..)
3800 maH battery? (If this ends up being the best solution...I need a good case to support it and these usually don't have those...)
A way to turn off LTE?
...any other way to get 12+ hours out of my phone with heavy usage? I'm never in the car long enough or at a desk long enough some days to be able to plug my phone in and charge...
Also, I've searched and searched and can't find anything other than "The LTE is still on even if you use X ROM, or turn X settings off, or install X kernel/radio." Is there any new update on how to turn off LTE on the Skyrocket when rooted?
My SetCPU settings:
Clock max 1350 MHz
Clock min 192 MHz
Profiles:
Screen OFF
Priority 60
Clock max 432 MHz
Clock min 192 MHz
Battery >=50*C
Priority 55
Clock max 756 MHz
Clock min 192 MHz
Battery <= 20%
Priority 50
Clock max 702MHz
Clock min 192 MHz
Battery <= 50%
Priority 45
Clock max 918MHz
Clock min 192 MHz
Battery <= 80%
Priority 40
Clock max 1188MHz
Clock min 192 MHz
Please help. I NEED to find a way to do this. I'm a network technician and having no access to phone calls and emails is tough. Also my family and loved ones after the work day and I'm still out doing errands for another 4 or so hours and my phone is 0% dead isn't a good thing.
*Note: If the 2100maH battery takes the stock back plate and it can give me what I'm asking for I would PREFER it. I have an Otterbox case I dropped $50 + SH on and I'd like to keep using it....
Phone specs:
SKY ICS 4.2F-7A
Kernel:
3.0.8-perf-1727RUXLF3-CL611724
syypher said:
Cycled 3 times now and the first day with moderate use I went about 8-9 hours. It was awesome. Now that I'm using it a little heavier and will actually be using it quite heavily with data, gps, browsing, phone calls etc. I am noticing maybe that really isn't enough... I need like 12 hours or more like I hear some people are getting...
So I ask you XDA, what is THE BEST way for me to achieve super long battery life with heavy use. I'm already using SetCPU (settings below)
2100 maH battery? (Will this even be a huge difference from our current battery? I don't know what our stock battery maH is..)
3800 maH battery? (If this ends up being the best solution...I need a good case to support it and these usually don't have those...)
A way to turn off LTE?
...any other way to get 12+ hours out of my phone with heavy usage? I'm never in the car long enough or at a desk long enough some days to be able to plug my phone in and charge...
Also, I've searched and searched and can't find anything other than "The LTE is still on even if you use X ROM, or turn X settings off, or install X kernel/radio." Is there any new update on how to turn off LTE on the Skyrocket when rooted?
My SetCPU settings:
Clock max 1350 MHz
Clock min 192 MHz
Profiles:
Screen OFF
Priority 60
Clock max 432 MHz
Clock min 192 MHz
Battery >=50*C
Priority 55
Clock max 756 MHz
Clock min 192 MHz
Battery <= 20%
Priority 50
Clock max 702MHz
Clock min 192 MHz
Battery <= 50%
Priority 45
Clock max 918MHz
Clock min 192 MHz
Battery <= 80%
Priority 40
Clock max 1188MHz
Clock min 192 MHz
Please help. I NEED to find a way to do this. I'm a network technician and having no access to phone calls and emails is tough. Also my family and loved ones after the work day and I'm still out doing errands for another 4 or so hours and my phone is 0% dead isn't a good thing.
*Note: If the 2100maH battery takes the stock back plate and it can give me what I'm asking for I would PREFER it. I have an Otterbox case I dropped $50 + SH on and I'd like to keep using it....
Phone specs:
SKY ICS 4.2F-7A
Kernel:
3.0.8-perf-1727RUXLF3-CL611724
Click to expand...
Click to collapse
I found a 2250maH Battery on ebay.. MFG is Andida. $13 shipped. Fits in the stock battery location with the stock cover. I have an OtterBox case. All is well! Worth the 7 day wait!
hemibat said:
I found a 2250maH Battery on ebay.. MFG is Andida. $13 shipped. Fits in the stock battery location with the stock cover. I have an OtterBox case. All is well! Worth the 7 day wait!
Click to expand...
Click to collapse
Thank you Hemi! Is Andida a good brand or something? Or are you just letting me know so I can find it? Just curious. How has the life been? I had an Atrix before the SkyRocket and I know a MAJOR issue with that phone was anything above stock that was breaking the 2000maH mark WOULD NOT register in the battery's true %. No matter what cycling, "fixes", battery stat resets etc. that you did. Does the battery on here show you the actual stats? Would this battery last long enough to meet my needs? 12 hour day with heavy usage?
Sorry for the question bombardment...but if this will really answer my needs which I really need answered ASAP, I will drop the $ for this immediately.
Buy an extended battery, then UC/UV like crazy
OFWGKTADGAF said:
Buy an extended battery, then UC/UV like crazy
Click to expand...
Click to collapse
How do you UV?
Also, what do you guys who've under clocked found as a good clock to keep it at? 1.5ghz is REALLY high IMO and I normally have it cap around 1.2ghz...anyone found a good clock to run around and it still be snappy and smooth?
Also..how do the guys with stock batteries get those 12 hour times? Is it just moderate usage? Will the 2100mah or 2200mah batteries give me what I want? 12 hours high usage? Or do I need to go with the 3800mah seidos I've been hearing a lot of good reviews on...?
syypher said:
How do you UV?
Also, what do you guys who've under clocked found as a good clock to keep it at? 1.5ghz is REALLY high IMO and I normally have it cap around 1.2ghz...anyone found a good clock to run around and it still be snappy and smooth?
Also..how do the guys with stock batteries get those 12 hour times? Is it just moderate usage? Will the 2100mah or 2200mah batteries give me what I want? 12 hours high usage? Or do I need to go with the 3800mah seidos I've been hearing a lot of good reviews on...?
Click to expand...
Click to collapse
Can't help with the battery, but I run 1080 max 192 min, battery is more or less same as 1500 max for me. I get 4hrs screen on time, maybe 3.5 if there's above average voice use. This is with data on the whole time. I've found my battery is just about completely dependent on screen time, minus some expected drain over the course of hours but that's very minimal.
Sent from my SGH-I727 using Tapatalk 2
hemibat said:
I found a 2250maH Battery on ebay.. MFG is Andida. $13 shipped. Fits in the stock battery location with the stock cover. I have an OtterBox case. All is well! Worth the 7 day wait!
Click to expand...
Click to collapse
In my experience the Extended Samsung Nexus battery is a better solution than the Andida.
syypher said:
Thank you Hemi! Is Andida a good brand or something? Or are you just letting me know so I can find it? Just curious. How has the life been? I had an Atrix before the SkyRocket and I know a MAJOR issue with that phone was anything above stock that was breaking the 2000maH mark WOULD NOT register in the battery's true %. No matter what cycling, "fixes", battery stat resets etc. that you did. Does the battery on here show you the actual stats? Would this battery last long enough to meet my needs? 12 hour day with heavy usage?
Sorry for the question bombardment...but if this will really answer my needs which I really need answered ASAP, I will drop the $ for this immediately.
Click to expand...
Click to collapse
The battery and mfg is the only one I found that was a 2500maH. It was the largest I found that kept everything I wanted (stock battery, cover, etc). There might be another CO that makes one, but this is what I've found. Two weeks and running. It charges the first 65% like a banshee, then slows down for the remainder.
It's worked well for me, extending my day and making life easier. It really doesn't take any longer to fully charge than the stock one did, just longer life throughout the day.
Hope this helps.
You thought about getting external mobile charger or just spare batteries? you charge everything when you got the time and then just swap around when needed.
have i got a solution for you my friend...
I'm testing a set of tweaks i made for my old phone which is working well. These tweaks provide excellent battery life and incredible performance gains.
Just to give you a quick snapshot, I'm at 22+ hours uptime @ 28% under moderate use. I'm not oc/uv either, and i am on official aokp Rom.
I plan to have it finalized by Sunday as long as my normal life duties don't interfere...
Sent from my SGH-I727 using xda app-developers app
I am the exact same way with my skyrocket, heavy use for work and need at least 12hrs+ battery. So after much research, Looking at extra batteries to carry around or the tweak/root/rom method, which is way more convenient then carrying around batteries all the time.
I rooted my device, put SKYICS on it, and tweaked the CPU and UV, and now I'm using my phone heavy and at hour 12 i'm at 39%, so happy now with this phone now. It does me. Give it a try, believe me you wont be disappointed.
thomas.raines said:
have i got a solution for you my friend...
I'm testing a set of tweaks i made for my old phone which is working well. These tweaks provide excellent battery life and incredible performance gains.
Just to give you a quick snapshot, I'm at 22+ hours uptime @ 28% under moderate use. I'm not oc/uv either, and i am on official aokp Rom.
I plan to have it finalized by Sunday as long as my normal life duties don't interfere...
Sent from my SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
Where will you posting it when it's done so i know where to find it?
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
once i get all the bugs ironed out, I'll post it on the dev section
Sent from my SGH-I727 using xda app-developers app
syypher said:
Cycled 3 times now and the first day with moderate use I went about 8-9 hours. It was awesome. Now that I'm using it a little heavier and will actually be using it quite heavily with data, gps, browsing, phone calls etc. I am noticing maybe that really isn't enough... I need like 12 hours or more like I hear some people are getting...
So I ask you XDA, what is THE BEST way for me to achieve super long battery life with heavy use. I'm already using SetCPU (settings below)
2100 maH battery? (Will this even be a huge difference from our current battery? I don't know what our stock battery maH is..)
3800 maH battery? (If this ends up being the best solution...I need a good case to support it and these usually don't have those...)
A way to turn off LTE?
...any other way to get 12+ hours out of my phone with heavy usage? I'm never in the car long enough or at a desk long enough some days to be able to plug my phone in and charge...
Also, I've searched and searched and can't find anything other than "The LTE is still on even if you use X ROM, or turn X settings off, or install X kernel/radio." Is there any new update on how to turn off LTE on the Skyrocket when rooted?
My SetCPU settings:
Clock max 1350 MHz
Clock min 192 MHz
Profiles:
Screen OFF
Priority 60
Clock max 432 MHz
Clock min 192 MHz
Battery >=50*C
Priority 55
Clock max 756 MHz
Clock min 192 MHz
Battery
Click to expand...
Click to collapse
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?