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?
Related
:[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
In the power options, under processor power management, the maximum processor state on battery seems to always revert back to 100% after a reboot or changing power plans. Any ideas why the setting won't stick?
I noticed this as well
..very annoying
is that the only setting you noticed reverting? or are there more?
I assumed win8 handles processes differently requiring less battery consumption.
Sent from my EVO using xda premium
but that isn't the issue
if u go into settings and change the 100% to anything else
it always reverts back .....very annoying ....marked difference in battery life noticed
If you create a new power plan and use it, the settings will stay after a reboot. This is what I did.
Did anyone try 20% CPU so far ? And if so, how is the battery life?
I won't mind getting Surface Pro if I can throttle down its CPU when on battery to Surface RT's speed for a longer battery.
I currently have a RT version with me
Power consumption curve for CPUs is very non-linear. 90% from 100% will probably save you more power than 20% from 90% will. You'd just be wasting a ton of processing capability.
GoodDayToDie said:
Power consumption curve for CPUs is very non-linear. 90% from 100% will probably save you more power than 20% from 90% will. You'd just be wasting a ton of processing capability.
Click to expand...
Click to collapse
Not only that but the windows throttle percentage is not really as specific as a 0-100 range would suggest, so even if you set 20% it might limit the cpu to its minimum frequency.
If you use a tool such as this you can see what the current frequency is: http://www.cpuid.com/softwares/tmonitor.html
With my laptops (much slower) Core2Duo the minimum frequency was too slow, but about 50% of the max worked well and dramatically reduced the heat under load.
Some people reckon it is better to allow the cpu to use its full frequency so that it finishes the job faster and can move back to the lowest idle state. I am not sure that really applies to i5 (which doesn't support the ARM-style idle states that haswell will) and like you say the power consumption at lower cpu frequencies doesn't vary much. My experience with windows is that sometimes for no apparent reason at all programs such as word or chrome sit using 50+% of the cpu and you have to restart the process. It doesn't happen often at all but you might not realise until your battery is low. With the pro's i5 I expect you could get away with quite a low cpu frequency and would at least know you will always get roughly the same battery life.
This is the same problem that w700 has, an even earlier product. This situation made the biggest thread in the acer community because people are angry, some even took back their products and traded for the surface which made it the same than people realized it was not the w700 itself. Throttle stop didnt work because it seems to be more temp related.
Here are some interesting topics
http://community.acer.com/t5/Acer-T...rottling-Turbo-Boost-issues/td-p/6873/page/28
http://forum.tabletpcreview.com/acer-gateway/54122-w700-throttling.html
Walderstorn said:
This is the same problem that w700 has, an even earlier product. This situation made the biggest thread in the acer community because people are angry, some even took back their products and traded for the surface which made it the same than people realized it was not the w700 itself. Throttle stop didnt work because it seems to be more temp related.
Here are some interesting topics
http://community.acer.com/t5/Acer-T...rottling-Turbo-Boost-issues/td-p/6873/page/28
http://forum.tabletpcreview.com/acer-gateway/54122-w700-throttling.html
Click to expand...
Click to collapse
Actually, it is nothing like that problem. The OP is talking about manually limiting the max clock of the device using the Windows setting that has been there for a while now.
Hello. I'm new with the account here, but been reading this forum for years.
I'm creating this thread because my new Nexus 5 (which I have for 20 days now) is overheating more than a normal mobile device should.
When i bought it, it had 4.4.4 Kit kat android, and I had that one for about 5 days, and in that time, I didn't notice any overheating, or maybe didn't pay attention, can't remember really.
But after installing official Lollipop 5.0.1, the device is heating pretty good even when browsing internet for 5 minutes, at about 30-40% brightness.
**** Please tell me if some of your devices are acting the same, and is it worth a try to install back an older android to try if it will stop overheating, or my device may be faulty and should I take it back for another one (or maybe switch to LG G2) ?
Because I'm still unable to post image links, i will write it down:
- Ambient temperature: 23 degrees Celsius
- The temperature sensor is taped on the back side, at the side of camera, this is where it overheats most. (even if not using camera)
- Phone temp after staying on standby with screen off: 28 C (it's not warm but it is warmer than desk which it is sitting on)
- After staying idle on home screen with screen on for 10 minutes (50% brightness): 30.5 C
- After chatting on Messenger for 10 minutes: 34.3 C (feels warm)
- After recording video for 4 minutes: 41 Celsius!!! (almost uncomfortably hot in the whole upper half of the phone, both the back side and the screen)
- After 15 minutes letting it cool down, with screen off of course, it is 38 C (still hot to touch), and it stays like that untill I reboot the phone, then it cools down.
The test took about 50 minutes, and after that, battery was drained for about 25%.
-While charging, the phone does not overheat, just gets a little warm which is OK. (haven't tried wireless charging)
P.S. I don't play games on the phone...
Please act quick in case I should return the phone...
the only time my phone gets hot is when im intensively doing a lot of things..
for example.. im playing ingress, have tether ON, and my two sons are using their tablets connected to my phone playing ingress too..
but if i turn off the game and turn off tether, it cools down..
to me it sounds u have something intesively using your CPU and perhaps GPS and other radios.
hold power button.. when PWR OFF shows, long press it and reboot into SAFE MODE...
use the phone for a bit and see if it gets warm... this should tell you if its apps installed.
I only used wifi, no tethering, no GPS, 3G, NFC or any other radios, cell signal is good so phone is not searching for it.
- In safe mode, it still gets warm when using camera. When browsing internet and watching images in google search, also but just mild warm..
- But after sitting and thinking, I've found a problem! After recording with camera and leaving it to cool down, it didn't cool down because it had to make an effort to upload that 5 min video on Google drive via Auto backup!
After turning the Auto-backup off, it is now much cooler!
I will post tomorrow with the results, if something changes...
Anyway, thank you!
First of all, "warm" doesn't mean anything.
Battery temperature does not mean much either, as the CPU is what generates the most heat.
There is a battery temperature throttle that reduces the CPU frequency, but it is almost entirely pointless as the CPU will always reach it's own throttle temperatures MUCH, MUCH earlier than the battery will. The CPU starts throttling at 65C CPU temp (NOT battery temp), and shuts itself down at about 105C CPU temp. Unless your battery somehow reaches a batterytemp of 70C+ (nearly impossible because the CPU will always hit it's throttle first), then I would never even take it into any sort of consideration unless you have a physical battery defect.
Using the camera generates heat since it's CPU and power intensive.
Using the phone in general will generate heat.
Keep in mind that mobile devices are passively cooled, not actively cooled with a fan/liquid.
Not sure what you're so worried about.
Lower your brightness
Lethargy, thank you for a short physics lesson. I'm already into physics and cooling systems so all is clear. I was just worried a bit because all of my previous phones weren't getting this warm (hot), but also never had a multi-core processor in phone eather, maybe that's the reason why I never experienced this before.
Battery temp (measured with app) gets up to 40-42 degrees Celsius, while the phone case gets up to 41 when recording video. Of course that temp won't damage the device, I'm not worried about the processor, but that temp is degrading battery life, in long term.
And about the brightness, phone is not meant to be used at lowest brightness all the time, so that shouldn't be an excuse for high temps. Just sayin'...
Sent from my Nexus 5 using XDA Free mobile app
AlexSRB said:
Lethargy, thank you for a short physics lesson. I'm already into physics and cooling systems so all is clear. I was just worried a bit because all of my previous phones weren't getting this warm (hot), but also never had a multi-core processor in phone eather, maybe that's the reason why I never experienced this before.
Battery temp (measured with app) gets up to 40-42 degrees Celsius, while the phone case gets up to 41 when recording video. Of course that temp won't damage the device, I'm not worried about the processor, but that temp is degrading battery life, in long term.
And about the brightness, phone is not meant to be used at lowest brightness all the time, so that shouldn't be an excuse for high temps. Just sayin'...
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
The only thing that sounded odd was how it wasn't cooling down until you rebooted, but it sounds like you figured that out with the automatic upload setting.
41-42c battery temp can be normal after prolonged usage, though personally I usually see that after a short gaming session. My brightness is around 40% and high brightness will cause extra heat.
Otherwise the phone is very thin so you can feel the stacked SoC and RAM heat up through the skin fairly easily, right around the camera area as you mentioned.
I think each device and CPU is slightly different and can vary by a few degrees under load as well.
AlexSRB said:
Lethargy, thank you for a short physics lesson. I'm already into physics and cooling systems so all is clear. I was just worried a bit because all of my previous phones weren't getting this warm (hot), but also never had a multi-core processor in phone eather, maybe that's the reason why I never experienced this before.
Battery temp (measured with app) gets up to 40-42 degrees Celsius, while the phone case gets up to 41 when recording video. Of course that temp won't damage the device, I'm not worried about the processor, but that temp is degrading battery life, in long term.
And about the brightness, phone is not meant to be used at lowest brightness all the time, so that shouldn't be an excuse for high temps. Just sayin'...
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Your temperatures are fine and you shouldn't worry about it. It's average for a Nexus 5, and there are throttles/shutdown temps anyways, for both the battery and CPU. I've had mine for a year and there hasn't been any sort of issue, normal usage should be negligible to the condition of the battery.
Ok, everything seems to be ok then. Now I can go to sleep without worrying Thanks guys!
Sent from my Nexus 5 using XDA Free mobile app
Hello, I have been using HTC U 11 for a couple of days now. I find it really odd that the temperature is kinda little high at all times. here are my observations.
before I start im from chennai and the avg temperate here ranges from 28 to 35 on a normal day.
I first noticed heating when I was recording a FHD video at 60FPS for more than 3 min. The camera stopped taking video due to overheat. The phone was uncomfortably hot. But then I realized maybe its because I was riding as pillion in motorcycle while recording and it was 1 PM in the afternoon with Sun burning your eyes. So I thought maybe its because of that.
then taking any 4K, hyperlapse videos increased temperature. So i used CPU temp to analyze the temperature(with back case removed) I was in a AC Hall with room temperature of around 26 degrees C and the starting temperature was 36 degrees C in my phone. Then,
I took two 4K videos 1 and 2 minutes each and the temperature went from 36 to 47 and once the video is finished it settled back to 41. the CPU was at 1900 MHz while recording and throttled down to 300Mhz once its done.
then I ran 3D Mark tests. it gave me a score of some 2.7K with an average FPS of 25 but while performing this test my CPU went to a whooping 53 degrees C and settled back to 45 degree C once its done. Normal Phone operations like FB, reddit, discord etc gives me around 36 37C which still, i feel is too much and despite being a glass body I have never felt any form of chillness even after hours of being in AC room it was always pleasantly warm when normal use to uncomfortably warm on high use.
Do you guys think that I have a defective device? I still have 4 days on free return policy with the seller. should I replace my phone?
I'd say it's normal for a phone.
Video recording and running heavy games is the most difficult tasks for smartphone (maybe now it's VR & AR), I'm not surprised at all if the temperature raises at 42 degrees or more.
Benchmark apps like 3D marks take full power of computing capability, no wonder why it gets even hotter.
Smartphone is a smartphone, not a PC nor a GoPro.
Alpert3 said:
I'd say it's normal for a phone.
Video recording and running heavy games is the most difficult tasks for smartphone (maybe now it's VR & AR), I'm not surprised at all if the temperature raises at 42 degrees or more.
Benchmark apps like 3D marks take full power of computing capability, no wonder why it gets even hotter.
Smartphone is a smartphone, not a PC nor a GoPro.
Click to expand...
Click to collapse
yeah! i thought that too. actually i think for a processor like 835 normal temperature is 35 36. I do understand that Optical Image stabilization and image stitching are quite heavy tasks . maybe im paranoid. I just want to make sure it doesnt damage the phone in the long run. Also its kind of a pride thing . you see from where I am, There are tonnes of pun and memes about cheap MI phones and heating. So people around here were like you have a $700 phone(thanks to all the customs and import duties) and it heats like a $50 MI phone?. *smh*.
Do you think installing custom rom can increase performance? I really want to get rid of that HTC companion, news republic, facebook and messenger. FB sucks. it takes up almost 300MB of RAM at all times.
It would not damage your phone but as we speak of the "long-term", something you probably should know:
If you keep using your phone for heavy tasks and temperature of the device is always at 38°C or higher, it could decrease the battery life. Higher temperature would cause the loss of battery capacity. You probably should be careful.
As for MI phones, 50$ is hard to get one. And heating meme is because of Qualcomm S810 back in 2015, for HTC, Xiaomi, as well some other devices. Some people just couldn't get over it even we have S835 today.
For RAM consumption, I'd say leave it, because on the one hand, U11 has 4GB of RAM, 300MB does no harm. (the theory is, the free RAM is some sort of a waste, you don't need to be careful about the RAM usage as long as you don't experience serious lag) on the other hand, you can always disable the apps if you don't need them. Installing another ROM won't make these apps running with less RAM.
Hi, I want to buy the Rog 5 but I've heard that it has high temperatures even from light use (like when using YouTube it reaches 40degrees celcius). How are the overall thermals? I'm not talking about throttling I'm talking about general temperature when using the phone for light tasks. Any info would be highly appreciated. Also any info on battery life would be great too
From what I have heard from Youtube and reddit, It is a hot phone because it keeps internals in a good temperature, plus they achieved better temperature after update.
Oxydrix said:
From what I have heard from Youtube and reddit, It is a hot phone because it keeps internals in a good temperature, plus they achieved better temperature after update.
Click to expand...
Click to collapse
But having a warm phone isn't a good sign is it? I'm currently using a huawei p40 pro plus and it's super cool (probably because of the ceramic body). You mentioned an update, so is the rog 5 cooler after the update? On YouTube Technick ran a battery drain test and the Rog 5's peak temp was almost 60 degrees celcius
Thanos88 said:
But having a warm phone isn't a good sign is it? I'm currently using a huawei p40 pro plus and it's super cool (probably because of the ceramic body). You mentioned an update, so is the rog 5 cooler after the update? On YouTube Technick ran a battery drain test and the Rog 5's peak temp was almost 60 degrees celcius
Click to expand...
Click to collapse
I don't know about the reliability of this man, but look here
Oxydrix said:
I don't know about the reliability of this man, but look here
Click to expand...
Click to collapse
Thanks man. This really helped.
I got it a few days back, I can share some impressions. Yes, it's a hot phone. Yes CPU temp gets up to about 40 degrees sometimes when browsing or multitasking. Gaming also gets it to about 45 - 50 on CODM and Dead Cells and between 55 and upwards of 60 with Genshin Impact. A Peltier effect cooler like the FunCooler from black shark brings this down about 10 degrees. This temperature is mostly felt at the center of the display, while the sides on the back, where the batteries are, remain noticeably cooler. Perhaps their goal was to dissipate het through the display, idk.
I haven't been able to notice any drop in performance yet, even with the thermal limit set to low. What I don't know is how this affects the chip long term, but I hope it doesn't degrade for at least about 5 years. Either way I'm sticking with a cooler for Genshin impact just to make sure the device lasts longer.
cotov said:
I got it a few days back, I can share some impressions. Yes, it's a hot phone. Yes CPU temp gets up to about 40 degrees sometimes when browsing or multitasking. Gaming also gets it to about 45 - 50 on CODM and Dead Cells and between 55 and upwards of 60 with Genshin Impact. A Peltier effect cooler like the FunCooler from black shark brings this down about 10 degrees. This temperature is mostly felt at the center of the display, while the sides on the back, where the batteries are, remain noticeably cooler. Perhaps their goal was to dissipate het through the display, idk.
I haven't been able to notice any drop in performance yet, even with the thermal limit set to low. What I don't know is how this affects the chip long term, but I hope it doesn't degrade for at least about 5 years. Either way I'm sticking with a cooler for Genshin impact just to make sure the device lasts longer.
Click to expand...
Click to collapse
Thanks for the reply. 40 degrees from just web browsing is ridiculous. Rather dangerously high and will definitely degrade batteries. Think I'll give the rog 5 a miss
Thanos88 said:
Thanks for the reply. 40 degrees from just web browsing is ridiculous. Rather dangerously high and will definitely degrade batteries. Think I'll give the rog 5 a miss
Click to expand...
Click to collapse
40 is the CPU reading I get. Batteries stay about 5 degrees below the CPU for normal use generally according to my observations, just to make that clear. Not sure which battery temp it's actually reading though, since there are 2 batteries.
Thanos88 said:
Спасибо за ответ. 40 градусов от простого просмотра веб - страниц-это просто смешно.
Click to expand...
Click to collapse
120/144 Hz need more power
cotov said:
40 is the CPU reading I get. Batteries stay about 5 degrees below the CPU for normal use generally according to my observations, just to make that clear. Not sure which battery temp it's actually reading though, since there are 2 batteries
Click to expand...
Click to collapse
cotov said:
40 is the CPU reading I get. Batteries stay about 5 degrees below the CPU for normal use generally according to my observations, just to make that clear. Not sure which battery temp it's actually reading though, since there are 2 batteries.
Click to expand...
Click to collapse
40 is still too high though for normal usage. I've never heard of a phone go that warm. My huawei sits at 22 maximum.
Phone arrived 2 days ago, in my experience It Is not that hot, while browsing / YouTube / Instagram It Is cool (about 31/32 °c) and my ambient temperature Is around 20 °. I have played 1 hour call of duty and It reached 37 ° on the cpu, while the phone was hotter, especially in the middle. I think this Is how It works, getting hot outside to be colder inside. Also I updated to firmware 2102.81 which helped a lot.
Oxydrix said:
Phone arrived 2 days ago, in my experience It Is not that hot, while browsing / YouTube / Instagram It Is cool (about 21/22 °c) and my ambient temperature Is around 20 °. I have played 1 hour call of duty and It reached 37 ° on the cpu, while the phone was hotter, especially in the middle. I think this Is how It works, getting hot outside to be colder inside. Also I updated to firmware 2102.81 which helped a lot.
Click to expand...
Click to collapse
Thanks for this!! I'll probably buy one now