see my processor in geekbench 3?? ARM @ 1.14gHz.. pls help. I wanna know if this is normal. coz whenever my phone is 80% and above.. the scores ranges from:
single core score : 2500-2550
multi core score : 4400-4450
Also my iphone se is slow whenever I see that my processor’s low.
take note that I still have 33gb/64gb left.
Colin on 11 Sep, 2017 04:02 PM
I do not know of any part of Geekbench that would cause this kind of result pattern. It may be an issue with battery health on your device, so you may wish to take you phone to an Apple Store to get it checked out.
No, I’ve let an apple staff run diagnostic on my SE and he told me that the battery,software,hardware,etc has no issues. it may be due to ios 11 beta. I’ve hard reset my phone already and the issue’s gone.
I am having the same on my iPhone SE iOS 11.0.1. Performance cut in half when battery life is less than 70%. Prior to iOS 11, the scores were consistent no matter how much battery left unless low power mode was on.
This problem is not happening on my iPad Air 2. The same performance at 100% and 9%
Colin on 29 Sep, 2017 10:17 PM
Thank you to everyone for letting us know about this. We are investigating this issue, but so far have been unable to reproduce it at our office. I will let you know right away if we're able to provide any more insight into this battery-dependent performance.
For those experiencing this issue, if you could provide a link to your results for the iPhone SE in the Geekbench Browser along with the approximate battery percentage that the benchmark was run at, it would be a great help and may help us isolate this issue more quickly.
it would be great if ya'll guys find a solution or the cause to this problem. I'm really bothered. I saw in the tech reviews that even though they have 50% or below battery level, they can still get high results.
As far as I know, it’s happening on Samsung processors. 1800 & 3000 score at 32% battery life (sometimes even lower). Jumped to 2500 & 4400 at 100% battery. I didn’t have this problem in iOS 10. The same result no matter how much battery left unless low power mode was on.