Related
So I usually use CPUSpy to monitor my CPU usage. This comes in handy once the device is rooted and I can see how custom kernels and settings affect battery life and cpu cycles. My LG G4 is the tmobile variant and obviously not currently rooted. I notice through CPUSpy that my cpu speed literally never exceeds 1440mhz.
I don't have any problems with that per say, everything on the device still runs buttery smooth without anything more than the occasional hiccup or lag. I'm curious if anyone else has monitored their CPU speeds and noticed the same thing? I just find it a little interesting.
CPU spy can't even see the A57 cores so there's no way it can see what speed it's running at.
4 cores are limited to 1.44 the rest are 1.8
I have not used CPUSpy. But CPU-Z will show you the speed of each of the 6 cores. As mentioned, the last 2 are the only ones I've seen reach 1.8GHz, the first 4 seem to top out at 1.4 GHz.
Ok.. Using cpu-z..
That's how mine looks "at rest". When it's sitting quietly, saving the battery. Crank up some apps, and you should see those clock speeds rise.
But, trying to improve my battery life, and keep the temps down, I've been hoping to see those numbers stay low, not actually show how high they can go
I agree.. As ive stated, the device runs great i just found it odd. It even calls it a 1.44ghz cpu in the cpu profile and mostly no matter how hard i push the device i cant break that speed
Right as CPU-Z opens, the clock speeds spiked briefly. I was able to get a screenshot quickly.
Do yours also jump up for a second or two right as the app opens?
This has been discussed already. As the previous post shows, they do get to 1.8Ghz when required.
Hello,
I have a peculiar problem with my OnePlus Two
The faster A57 cores don't get activated, I have tried using Antutu, played Asphalt 8 And NFS NL for hours.
But the cores just won't get triggered
I'm using A1 CPU tool to monitor the same.
Even CPU Z wouldn't show me any activity on the other 4 cores while Antutu was running.
Any ideas? It's brand new can be returned
Oxygen OS - 2.1.1
A2003_14_151011
Sent from my C6602 using XDA Free mobile app
Denhot said:
Hello,
I have a peculiar problem with my OnePlus Two
The faster A57 cores don't get activated, I have tried using Antutu, played Asphalt 8 And NFS NL for hours.
But the cores just won't get triggered
I'm using A1 CPU tool to monitor the same.
Even CPU Z wouldn't show me any activity on the other 4 cores while Antutu was running.
Any ideas? It's brand new can be returned
Oxygen OS - 2.1.1
A2003_14_151011
Sent from my C6602 using XDA Free mobile app
Click to expand...
Click to collapse
I just installed A1 CPU to verify your issue.
It shows cores 0,1,2,3,4 are used at 1344ghz for me as well.
When i check with synapse (i'm on AK kernel) it shows all cores are used.
I guess it's a limitation with A1 CPU tool. Try with other tool that supports such architecure.
I was sceptical on the same but, out of the box I remembered seeing 1777 MHz frequencies.
Thanks a lot
I shall try more tools and get back.
Though I think if you're on a different kernel and had the A1 CPU tool been correct it would be redundant, Because core allocation would be done on kernel level (in my knowledge).
Sent from my iPad using Tapatalk
I know that it was already discussed but maybe someone has found a solution.
The problem is that performance of device gradually decreases proportionally to the level of the battery.
For example:
- battery is 90%, Real Racing 3 runs perfectly,
- battery is 45%, some lags appear during gameplay
- battery is 10%, heavily FPS drop, almost impossible to play
Battery saver is turned off, device is cold in all tests.
If I would like to save my battery level - I will turn on battery saver manually,
but I WANT to have good game experience not depending on battery level
This is really crazy.
Tested on stock OOS 2.1.1, with stock kernel, with Boeffla an AK, tested on Exodus ROM - everywhere I can see this weird behaviour.
May be some system files must be edited to overcame this issue?
jemcik said:
I know that it was already discussed but maybe someone has found a solution.
The problem is that performance of device gradually decreases proportionally to the level of the battery.
For example:
- battery is 90%, Real Racing 3 runs perfectly,
- battery is 45%, some lags appear during gameplay
- battery is 10%, heavily FPS drop, almost impossible to play
Battery saver is turned off, device is cold in all tests.
If I would like to save my battery level - I will turn on battery saver manually,
but I WANT to have good game experience not depending on battery level
This is really crazy.
Tested on stock OOS 2.1.1, with stock kernel, with Boeffla an AK, tested on Exodus ROM - everywhere I can see this weird behaviour.
May be some system files must be edited to overcame this issue?
Click to expand...
Click to collapse
Hi Jemcik, hi Denhot!
I'm facing the same issues on my new device and it's definately not normal!
With a battery level of 19% I was not able to get the 4 A57 cores online, which results in lower system performance. Have you found a solution?
@Denhot!
Maybe we should rename the thread into: IS OPT PERFORMANCE REALLY DEPENDENT ON BATTERY STATUS AND IS IT A ROM FEATURE OR AN ISSUE!?
I think, one of the kernel devs should be able to answer this question.
ollimi1 said:
With a battery level of 19% I was not able to get the 4 A57 cores online...
Click to expand...
Click to collapse
It looks like some system configuration files with kernels activation policy have to be edited,
but I haven't found yet which files exactly.
jemcik said:
It looks like some system configuration files with kernels activation policy have to be edited,
but I haven't found yet which files exactly.
Click to expand...
Click to collapse
I've never experienced such a function!
CPU power depending on battery voltage!? 62k with full battery, 49k with 20% battery both with same CPU temps!
Hopefully not a general problem on our side with the motherboard Voltage Regulator or something.
Have you been to a kernel thread and asked this question? If not, I will ask this in AK's kernel thread. Maybe he knows more about it!
The 4 high performance cores will only be activated when needed. What app are you using to check the core usage? Every now and then you should see 2 of the high performance cores sometimes coming to life every now and then, with the other 4 power efficent cores being more busy. Use CPU-Z to check.
Due to the way Oxygen OS's stock kernel works, only 2 of the high performance cores will ever be active, alternating between the 4 cores in an attempt to keep the phone cool and not throttle as often. If you want all 4 high performance cores to be active as well as overclocking it back to its original speeds, you'll need to flash a custom kernel.
jemcik said:
I know that it was already discussed but maybe someone has found a solution.
The problem is that performance of device gradually decreases proportionally to the level of the battery.
For example:
- battery is 90%, Real Racing 3 runs perfectly,
- battery is 45%, some lags appear during gameplay
- battery is 10%, heavily FPS drop, almost impossible to play
Battery saver is turned off, device is cold in all tests.
If I would like to save my battery level - I will turn on battery saver manually,
but I WANT to have good game experience not depending on battery level
This is really crazy.
Tested on stock OOS 2.1.1, with stock kernel, with Boeffla an AK, tested on Exodus ROM - everywhere I can see this weird behaviour.
May be some system files must be edited to overcame this issue?
Click to expand...
Click to collapse
Hi,
would like to share I don't have a similar experience, with NFS NL or Asphalt, phone was consistent with no lags even when it got unbearable to hold.
I as playing and simultaneously screen mirroring over to a TV.
Going from 65 to 25% over a long course.
I normally won't let my battery fall below 20%.
So the thing about Li-ion/pro is that as you go lower voltage decreases so to provide same power draw current increases.
Basically it would heat up faster.
That can be a reason combined with that their might be inbuilt measures to save battery like you said, nor as an engineer I would recommend you to stress your phone at those levels.
I can't explain the lag at 45%, didn't find it might try real racing 3 later to check.
Sent from my iPad using Tapatalk
trapistasajt said:
The 4 high performance cores will only be activated when needed. What app are you using to check the core usage? Every now and then you should see 2 of the high performance cores sometimes coming to life every now and then, with the other 4 power efficent cores being more busy. Use CPU-Z to check.
Due to the way Oxygen OS's stock kernel works, only 2 of the high performance cores will ever be active, alternating between the 4 cores in an attempt to keep the phone cool and not throttle as often. If you want all 4 high performance cores to be active as well as overclocking it back to its original speeds, you'll need to flash a custom kernel.
Click to expand...
Click to collapse
This is consistent with what I've noticed. The time It didn't, a simple reboot helped solve it and it hasn't occurred since.
Also these tools can't monitor the other cores, if you're rooted why not try synapse as helkat suggested
Sent from my iPad using Tapatalk
Denhot said:
This is consistent with what I've noticed. The time It didn't, a simple reboot helped solve it and it hasn't occurred since.
Also these tools can't monitor the other cores, if you're rooted why not try synapse as helkat suggested
Sent from my iPad using Tapatalk[/QUOTE
Thanks man!
I know how the S810 should work!
But I thought the performance issues have only to do with the temps. But now it seems it have also to do with the battery level.
It would be good if someone tries to reproduce the following to verify it:
1. One run Antutu benchmark with fully charged battery and room cool temps.
To be sure the conditions are the same, shut the display off for one or two minutes, than start display again, kill all recent apps and run Antutu test and note the results.
2. Than wait or do something until your battery is down to 20%, shut the display off for the same time, kill recent apps and start Antutu test run again and compare the results.
I've also tried the same after a reboot, with always the same results.
With 100% I get scores between 60 and 66k and with lower capacity (20%) I get only 48 till 50k!
I am not interested about the benchmark results, but I need to know if this only occurs on my side.
Click to expand...
Click to collapse
So, guys!
I have tested it the last few weeks and it is a fact that the performance in benchmarks is dependent by the battery level.
We have tested it with 3 devices and it is always the same.
But thank God, it seems on the devices perfomance themselves (in apps/ui) this has no effect!
But each one can replicate this behavior very easy!
ollimi1 said:
Hi Jemcik, hi Denhot!
I'm facing the same issues on my new device and it's definately not normal!
With a battery level of 19% I was not able to get the 4 A57 cores online, which results in lower system performance. Have you found a solution?
@Denhot!
Maybe we should rename the thread into: IS OPT PERFORMANCE REALLY DEPENDENT ON BATTERY STATUS AND IS IT A ROM FEATURE OR AN ISSUE!?
I think, one of the kernel devs should be able to answer this question.
Click to expand...
Click to collapse
I have the same issue! When battery level goes lower than 20%, my A57 kernels become offline. I checked this with CPU-Z and PerfMon. And this is the same on stock or custom kernel. Now I am using Boeffla kernel. The most frustrating is that my UI suffer from this. I have lot of lags in simple apps, such as calculator or some messengers.
Same issue here, there are threads in one plus forums.
I think the threashold level is at 40 % ?? They made this to keep the battery up. You can also see faster battery drop till the 40-30% mark then it is harder to kill the battery.
I am also dissapointed in this, maybe we can search the kernel sources ? Or is there a daemon app that triggers this?
I received the phone with 20%-30% battery, started an antutu knowing how powerfull 810 chip is, then boom 45k same as the previos phone i had with 801 chipset...i was like what the fxck....runing antutu again with full battery - 66k.
well i have run benchmark in back ground with few game and apps .. and checked with cpuz max that i have notice was around 50-60% cpu load still 2 off those a57 cores were off using this device for 2-3 days it always turns off 2 cores for me rest 6 is working most of the time :/ Even in battery saver mode .. i am not sure if this is a cpuz issue as i have not rooted my device yet so cant say properly ..
Also i face some freq. benchmark issue like in benchmark it scores around single core - 690 multicore - 2.6K .. and if i restarts device it scores normal - 1.1K and 4.5K .. i have no idea whats wrong with this :/
20% Battery Mark
The drop in performance at 20% Battery is standard behavior of the Rom and Stock Kernel. The Big Cluster (A57) is completly shut down to save Battery. If you dont want this you have to use a custom Kernel which is able to switch this Battery saving strategy off. Boeffla Kernel for example can do that.
Read http://www.anandtech.com/show/9828/the-oneplus-2-review/2.
They "optimized" the soc.....
No they just turned off some cores so there is no heat problem.
So I think this is my first and latest oneplus.
they've hit the mark! What the hell, i think they must be sued for false marketing. Its just like buying a car with 400 hp and those hp are only there when i'm parked or listen to music, if i'm on the highway or on the ridge the car has 100 hp...wtf :|
Killer2k8 said:
they've hit the mark! What the hell, i think they must be sued for false marketing. Its just like buying a car with 400 hp and those hp are only there when i'm parked or listen to music, if i'm on the highway or on the ridge the car has 100 hp...wtf :|
Click to expand...
Click to collapse
Calm down lol it's actually good on their part. Shutting down A57 cores on low battery is a good thing because the A53 cores use much lesser battery. If you're out on a trip and have 10% battery, with the A57 cores this will probably drain off within an hour of intermittent usage. When only the A53 cores are active, the battery life will increase greatly.
Companies design phones for average users, not just gamers. If you don't want this feature, root your phone, flash boeffla's kernel and disable the BCL Battery Driver. It's as simple as that
I can remember there was a similar issue happening on nexus 6, where cores were disabled at not that high temperatures.
If I can remember correctly, this was rectified by disabling the bcl driver.
Now, I found the correct path for the bcl driver (/sys/devices/soc.0/qcom,bcl.62/mode) on OPT, but I cannot edit the file, check the the screenshot below.
https://photos.google.com/share/AF1...?key=T2xkcU9mbGRON0dhVkFBTHdBaWs3Vi1Od1ZpOGN3
I even tried a init.d script, unfortunately, even this failed.
If someone can find a way to disable this, I reckon this will make our OPT way faster
hamdir said:
@Lord Boeffla
i just flashed your kernel after having problems with stock kernel, i think its similar to the bug you are tracking the stock kernel shuts down the big cluster at 40c or in low battery BUT also sometimes out of the blue it kills the big cluster never let it back on again another bug about usb charging where it stops charging over usb until reboot, i wrote about it extensively on the OP forums:
https://forums.oneplus.net/threads/to-oneplus-2-software-engineers-you-need-to-hear-this.399790/
you said that you are not sure about the s810 quality but i can assure you on the M9 latest v2.10 software it has killer performance full octa all the time (though the M9 has better thermal release as the s810 is connected to the metal unibody) but the quality of the OP2 stock kernel is really down mediocre, also from my M9 experience the high consume on the s810 is not related to a57 in specific, its the leakage in 20nm so even thee a53 cluster has high usage if its running on top clock, in fact on the M9 full octa LITTLE.big is better for battery as the a57s prevents the device from locking into the a53 full clocks, so really killing the big cluster for battery is counter productive to be honest, the easiest gain i found for battery is to underclock the a53 cluster to 1.2ghz and leave the a57 untouched in quad (which also help in keeping the SoC cold / improve sustainable performance)
i like you kernel because it tries to remain as stock as possible and whatever changes it does are noted, this is how i like custom kernels to be, its easier for the user to track what to change
but your hunt is making me think, is it possible that the users reporting the shut down are facing the exact same bug as stock kernel where the big cluster is killed for no reason? equally if the solution is disallowing min 0 why not make it optional?
finally i wanted to ask although we are setting 2:4 in a57 hot plug, the behaviour is exactly stock, ie: the device never requests more than 2 a57 cores so effectively its a hex configuration
Click to expand...
Click to collapse
Most people say that A57 cores are disabled on MM. But it isnt True. As you can see on screenshots, they are working. Please post screenshot from cpu-z on android N.
It's not disabled completely, they become active as needed when temp is under control for them to be active.
how is the temp and battery in N
read
pou_gh2 said:
how is the temp and battery in N
Click to expand...
Click to collapse
Very Good.
I hope so. I don't really wanna update if the A57 cores don't work.
They are not stop on Mm but Android N
It is true that the cpu changed Android N to Quad core???
They totally ruined Device by pushing such update ????
I'd rather belive it's cpu-z problem, because antutu score did not change after upgrading to 7.0.
S1gma said:
I'd rather belive it's cpu-z problem, because antutu score did not change after upgrading to 7.0.
Click to expand...
Click to collapse
Nope... It's Absolutely true.. 4 cores got disabled and working cores got underclocked to 1.5ghz
Don't belive the're underclocked. A53 cores runs at 1,5ghz as they should. We just don't have any app that can read actuall clock speed of A57 cores. But if they're disabled, I should not get any cpu usage on them. And I'm getting cpu usage on them!
What more, why we have the same benchmark scores as in Marshmallow?
Did anyone test this on lollipop? The cores themselves may not be disabled but I did notice their lack of use, no matter what game or app I use the 4 extra cores stay at 0 %.
Benchmarks such as atutu maybe specifically written to utilize all cores, but seeing their lack of use in general use is troubling.
As for the downclock the specification for this A57 is 2GHZ according to this.
http://m.gsmarena.com/sony_xperia_z3+-6878.php
And I do remember the clock speed being different in MM.
And there's also this.
https://forum.xda-developers.com/showpost.php?p=62151047&postcount=17
So some downclocking was made.
Edit.
Something worth a note, thou some people may know this already, "Stamina Mode" does seem to hae some effect on CPU usage.
After disabling "stamina mode" or setting it to start when battery is low i started to notice some usage from A57 in general use, where before it was not used at all.
I confirm on Android 7 they are disabled (last update). What the hell is this...
microlynz said:
I confirm on Android 7 they are disabled (last update). What the hell is this...
Click to expand...
Click to collapse
Care to give a prof of this claim?
foxsevent said:
Care to give a prof of this claim?
Click to expand...
Click to collapse
Look to this... Idiot phone
microlynz said:
Look to this... Idiot phone
Click to expand...
Click to collapse
I wouldn't say that's a proof, the cores may just not be in use atm, care to flash marshmallow or kittkat to test this?
foxsevent said:
I wouldn't say that's a proof, the cores may just not be in use atm, care to flash marshmallow or kittkat to test this?
Click to expand...
Click to collapse
When I flashed Android 6 MM the cores are working and the phone is very stable
microlynz said:
When I flashed Android 6 MM the cores are working and the phone is very stable
Click to expand...
Click to collapse
They are not disabled, just in an inactive state ... sleeping.
AttilaGolik said:
They are not disabled, just in an inactive state ... sleeping.
Click to expand...
Click to collapse
On Android 7 they never work. They keep on sleeping(or disabled it's the same thing)
microlynz said:
On Android 7 they never work. They keep on sleeping(or disabled it's the same thing)
Click to expand...
Click to collapse
Well to truly test you would have to flash all the way to KK, as supposedly the cores are disabled on both MM and N.
But you are correct it doesn't matter, as the A57 is down clocked to 1.56GHz to match the A53, and the A57 is in constant sleep state, may as well be disabled, even when running full HD games it does nothing, i wiuld mind this that much if it helped to keep the phone cooler but even without the A57 Z3+ is a bloody furnace, 60C degrees on a cold day, when in use just browsing the web.
Did you notice any difference when testing MM and N, lags, slowdowns etc?
How about any benchmarks? in antutu i get from 50k to 80k and i didn't notice all cores being uses when beniching, the only way i ever saw all cores in use is when using a CPU stress app.
If i had to guess i would say that the phone switches between A57 and A53 depending on what you do bu i never noticed CORES 5-7 ever being used.
Hi all,
I have cpu z installed and I'm not rooted. It generally uses all 8 cores but when I accidentally opened it I saw that it was only using 4 cores. I decided to restart and it is still using 4 cores. Is this normal because my g5 plus always uses all 8 cores.
Your in low power or battery saver mode... look at the battery symbol.. I can't remember if it kicks in at 5% or 15% battery automatically, then turns off when you connect the charger... It sometimes takes a few minutes for everything to kick back in. I would bet after getting a decent charge it was back to normal?
There is also a issue with Nougat at newer reporting CPU usage incorrectly even in rooted devices... been talked about a lot, something in the stock Moto firmware (or maybe that was a different Moto, I get them confused sometimes).
Ok thanks. Apparently cpu z was wrong.
the cores are reduced to 4 when u are on battery saver.
On thanks. The weird part was I didn't turn the battery saver.
DarthMaul14 said:
On thanks. The weird part was I didn't turn the battery saver.
Click to expand...
Click to collapse
It's automatic at a certain battery level by default.
Oh ok. Does the same thing apply for quad cores and hexacores.
DarthMaul14 said:
Oh ok. Does the same thing apply for quad cores and hexacores.
Click to expand...
Click to collapse
It will throttle them, although the exact implementation varies somewhat depending on the actual processor. littleBIG architecture tends to be that the BIG cores get shutdown, on more standard architecture like the SD625 they will get throttled to 50-75% of maximum speed, and others may just get a couple random cores disabled, it depends on the CPU and how Qualcomm/MediaTek/whoever engineered it.
Ok thanks!