Is CPU frequency being throttled down to a max of 1.7GHz?

[mzsquared]

There is an ongoing discussion in S9+ thread https://forum.xda-developers.com/galaxy-s9-plus/help/cpu-feequency-doesnt-1-7-ghz-t3822630 about a possible problem regarding SD845 CPU performances level. I was there last week but since then I replaced my S9+ for OnePlus 6 and today I ran the Antutu Bench on it and found out that the CPU freq. results are exactly the same. I didn't save the screenshot today but it's identical to the graph I have from the S9+.(link below)
The bench score though, was outstanding at 287985. What could be the reason for not getting closer to the max. frequency?

 

[matze19999]

As far as I know, the op6 doesnt throtte the cpu, it only lower down the cpu voltage...

See here:

https://forum.xda-developers.com/oneplus-6/help/how-throttling-op6-t3799948

 

[nikhiltejagorantla]

It's for small cores dude.. Not A75.

 

[spartan268]

In that same thread you linked it said to use CPU-Z cause it's not being accurately reported. If you look at the clock speeds they all perfect match up to the LITTLE cores only.

Please do proper testing. If your Antutu score is translating typical scores expected from the OP6. That means nothing is wrong with the performance. There is no performance issue. Simply user misunderstanding. You made a Maserati reference. The reality is it's like giving a 8 cylinder Maserati to a new driver who doesn't know how to drive then blames the car.

 

[mzsquared]

In that same thread you linked it said to use CPU-Z cause it's not being accurately reported. If you look at the clock speeds they all perfect match up to the LITTLE cores only.

Please do proper testing. If your Antutu score is translating typical scores expected from the OP6. That means nothing is wrong with the performance. There is no performance issue. Simply user misunderstanding. You made a Maserati reference. The reality is it's like giving a 8 cylinder Maserati to a new driver who doesn't know how to drive then blames the car.

It was me who's made that reference to Maserati in the other thread.
I was only asking questions about that out of curiosity, hoping that someone can explain the discrepancy between the technical specs and CPU X readouts, I saw only a few sense making responses and I used what's available to me, antutu and CPU x. Since then I found some information on this subject: out of 8 cores only 4 are clocked @ 2.8Ghz and the first 4 @ 1.7. As for the the Maserati? It wold be a shame for any driver to lose 2 cylinders.

 

[spartan268]

It was me who's made that reference to Maserati in the other thread.
I was only asking questions about that out of curiosity, hoping that someone can explain the discrepancy between the technical specs and CPU X readouts, I saw only a few sense making responses and I used what's available to me, antutu and CPU x. Since then I found some information on this subject: out of 8 cores only 4 are clocked @ 2.8Ghz and the first 4 @ 1.7. As for the the Maserati? It wold be a shame for any driver to lose 2 cylinders.

I can assure you that the BIG cores are working as expected. Apps that can't properly read out the architecture only reflect the frequencies seen on the little cores only. This use to be a common problem earlier when the architecture was just freshly released.

With that being said. Do not worry your phone is working as is and the only thing wrong is the app being used to capture the data.

I attached a screenshot of my frequencies. You can see the big core is hitting the upper ranges and is not locked down. This is using elemental ex kernel manager.

 

[mzsquared]

I can assure you that the BIG cores are working as expected. Apps that can't properly read out the architecture only reflect the frequencies seen on the little cores only. This use to be a common problem earlier when the architecture was just freshly released.

With that being said. Do not worry your phone is working as is and the only thing wrong is the app being used to capture the data.

I attached a screenshot of my frequencies. You can see the big core is hitting the upper ranges and is not locked down. This is using elemental ex kernel manager.

Thanks! That's what I found baffling, not being able to see those numbers on available to me testing apps. I was suspecting that something was amiss though, when I saw the high bench score leaving all the competition way-way behind.