Hello guys,
since I did the update to Android N I noticed that the device is pretty slow. After checking CPU-Z I saw that all "big" cores are offline. They are not even active when I run geekbench, therefore the multi-core score is only a little bit higher than the single core one (about 1900). A reboot fixes this issue temporarily. The bug was also reported a few month back at the google bug tracker (http://ift.tt/2czsZsc) and was apparently fixed in a future release.
Does someone have the same problem?
since I did the update to Android N I noticed that the device is pretty slow. After checking CPU-Z I saw that all "big" cores are offline. They are not even active when I run geekbench, therefore the multi-core score is only a little bit higher than the single core one (about 1900). A reboot fixes this issue temporarily. The bug was also reported a few month back at the google bug tracker (http://ift.tt/2czsZsc) and was apparently fixed in a future release.
Does someone have the same problem?
from xda-developers http://ift.tt/2d4pEyE
via IFTTT
Hello guys,
since I did the update to Android N I noticed that the device is pretty slow. After checking CPU-Z I saw that all "big" cores are offline. They are not even active when I run geekbench, therefore the multi-core score is only a little bit higher than the single core one (about 1900). A reboot fixes this issue temporarily. The bug was also reported a few month back at the google bug tracker (http://ift.tt/2czsZsc) and was apparently fixed in a future release.
Does someone have the same problem?
since I did the update to Android N I noticed that the device is pretty slow. After checking CPU-Z I saw that all "big" cores are offline. They are not even active when I run geekbench, therefore the multi-core score is only a little bit higher than the single core one (about 1900). A reboot fixes this issue temporarily. The bug was also reported a few month back at the google bug tracker (http://ift.tt/2czsZsc) and was apparently fixed in a future release.
Does someone have the same problem?
from xda-developers http://ift.tt/2d4pEyE
via IFTTT
No comments:
Post a Comment