Related
Before I start credit belongs to eL_777 for posting this in the asus prime thread.
I read that enabling the "Force GPU Rendering " in the developer options would increase the speed of apps. I so I gave it a try and it has definitely increased the overall smoothness for me. I also what to add that it may cause some apps to force close but the only issue I noticed so far is launcher pro not displaying properly. I just switched to adw ex so that is no longer an issue. I opera, browser and tapatalk seem to be faster. It also seems to have an impact on the YouTube app. Hopefully this info helps some people out.
I didn't come across this yet in the xoom forum so I thought it I would share. Sorry if it is common knowledge.
Original post:
eL_777 said:
Hey guys I noticed earlier that my Netflix app was ALOT smoother than it used to be before the ICS update but several others disagreed with me so I was confused. Then I remembered that I enabled this setting in the developer options menu in the android settings, "Force GPU Rendering". Make sure you enable that, close Netflix and start it back up and it should be a million times smoother after you do that. Hope this helps.
Click to expand...
Click to collapse
runhopskipjump said:
Before I start credit belongs to eL_777 for posting this in the asus prime thread.
I read that enabling the "Force GPU Rendering " in the developer options would increase the speed of apps. I so I gave it a try and it has definitely increased the overall smoothness for me. I also what to add that it may cause some apps to force close but the only issue I noticed so far is launcher pro not displaying properly. I just switched to adw ex so that is no longer an issue. I opera, browser and tapatalk seem to be faster. It also seems to have an impact on the YouTube app. Hopefully this info helps some people out.
I didn't come across this yet in the xoom forum so I thought it I would share. Sorry if it is common knowledge.
Original post:
Click to expand...
Click to collapse
I had tried it and thought that there was an improvement in smoothness, but it seems that as you say, it can break some applications. But thanks for the reminder.
Enabling this preference in developer options offloads task of rendering window components like buttons, text and complex 2d graphics calculations to GPU. This often results in much faster UI rendering including animations.
On one side you will definitely achieve better frame rate (and hence smooth experience) throughout system, but you may end up using more battery. On certain devices, GPU consumes more power the CPU, hence you may observe 5-15% lower battery life with option enabled.
offloading UI rendering to GPU has obvious benefits so that CPU can work on other important tasks like database IO, data manipulation, layout calculations and responding to other user inputs.
I would recommend having this option enabled on devices with weaker CPUs e.g. You should seldom need to enable this on dual-core 1.4ghz ARM CPU.
Odp: Enabling "Force GPU Rendering " for more speed in some apps
taranfx said:
Enabling this preference in developer options offloads task of rendering window components like buttons, text and complex 2d graphics calculations to GPU. This often results in much faster UI rendering including animations.
On one side you will definitely achieve better frame rate (and hence smooth experience) throughout system, but you may end up using more battery. On certain devices, GPU consumes more power the CPU, hence you may observe 5-15% lower battery life with option enabled.
offloading UI rendering to GPU has obvious benefits so that CPU can work on other important tasks like database IO, data manipulation, layout calculations and responding to other user inputs.
I would recommend having this option enabled on devices with weaker CPUs e.g. You should seldom need to enable this on dual-core 1.4ghz ARM CPU.
Click to expand...
Click to collapse
I finally gave up GPU rendering as it crash the tab many times. Ie google maps hang the tab after 10-15 min time of usage to such extend that it bootlooped over and over till battery is dead. Also browsing web cause same crashes. If you face many random crashes-you know what to do.
Wysyłane z mojego XOOM 2 ME za pomocą Tapatalk 2
I noticed this juts few days ago and did this on all my family's Nexus S.
Install Chainfire3d
from the market and then open the app and tap to install the driver. I used the normal method not the advanced. Don't set any other settings after your phone reboots. You can if you want to but a lot of aps won't work with those settings.
What this app does is it installs an intermediate open GL driver between the apps and phone GPU driver to give you better performance.
Just figured I'll share it with everyone. It really made a difference for me on ICS speed. The way I see it it should be baked it to all ICS ROMs.
isnt this just used for games?
that's why its called chainfire3D
the whole point is to trick proprietary games "apps" into thinking you have GPU that you don't
so you are able to play tegra adreno..ect games on other devices
dont think its works on anything other than games so i don't se how its helping make overall ICS faster.
ICS is already using our sgx540 just fine
Well, it does and it makes a difference. Try it and see for your self. Chainfire3d is not just for games.
Thank you for pointing out this tweak. I too was under the impression that chainfire was just for games.
Both tapatalk and the browser feel much smoother.
Thanks
Sent from my Nexus S using Tapatalk
obsanity said:
Well, it does and it makes a difference. Try it and see for your self. Chainfire3d is not just for games.
Click to expand...
Click to collapse
im eating my words sorry i was under impression was games only
im trying now you're right things are even smoother now thanks for the tip
As advertised. Nice find obsanity, it does make things noticeably smoother on general.
Noticed speed improvements thank you man
Nexus S - CyberGR Hybrid ICS (5), Matrix Kernel (15)
Chainfire dev recommends disabling all driver settings unless being used by a specific applications, per his xda thread:
" I strongly advise that when you are NOT using Chainfire3D for something specific, you disable all the options. This is better for system performance."
Anyone know why? Is he talking about the non-default options?
I don't know exactly, but it seems like it is just to do with the specific settings (inside the default settings section). Using the driver is fine, but any of the options being ticked has the ability to make some applications go awry depending on the device. Those options, i assume, are only meant to be used when you want to use a specific app that requires or benefits from them.
Also, i've noticed great improvements in ES File Explorer scrolling. It would lag a fair bit scrolling through long folders, but now it's nice and smooth.
Harbb said:
I don't know exactly, but it seems like it is just to do with the specific settings (inside the default settings section). Using the driver is fine, but any of the options being ticked has the ability to make some applications go awry depending on the device. Those options, i assume, are only meant to be used when you want to use a specific app that requires or benefits from them.
Also, i've noticed great improvements in ES File Explorer scrolling. It would lag a fair bit scrolling through long folders, but now it's nice and smooth.
Click to expand...
Click to collapse
That's what I was thinking as well. Thanks.
I'm installing this now... Have you guys noticed any decline in battery life?
Hopefully not :3
Does anyone know if this has the same downside as forcing gpu acceleration in the developer setting? I remember reading the Googler's post on G+ on how it increased the memory overhead by 8mb per app, reducing the memory available for other apps and processes.
Sent from my Nexus S using Tapatalk
It doesn't force GPU rendering. Alot of the Android UI is already using GPU rendering, using this intermediate driver just somehow makes it more fluid.
Trying it now, though I don't notice much improvements in scrolling.
I use force GPU setting on my phone. With the live OC in Matr1x at 111% (max my phone can handle) it does make a bit of difference in UI. But this Chainfire3D driver makes the most difference for me.
Also, in case you are on a ROM which doesn't let you change min memory settings, I'm using MinFreeManager which is a small app that just does that. The default settings which it comes built in are for GB but you can just change them manually. I don't touch the top 3 and just tweak the bottom 3. I'm currently on:
14,19,24,32,64,128
Does it effect battery drain?
Will this eat more battery juice?
Highly doubt it, and so far havn't noticed anything particularly different on my end. You can uninstall it anyway if it does cause trouble (though might be wise to perform a nandroid backup while initially installing).
Thx man, now trying it!!
Greetzz Jojoost
Sent from my Nexus S using XDA App
What are the additional features in the pro version?
What are the additional features in the pro version?
They are not described in the market.
Anti-Aliasing features and per-app settings are the main features in the pro version. More info here.
Hello
Can someone kindly tell me what difference does enabling GPU UI rendering make? From the name I can understand that the UI will be rendered using the GPU and not the CPU. But what are the advantages/disadvantages of this? What changes can I expect upon enabling it? And how does it, if at all, affect battery life?
Thanks in advance =)
Most of the apps now use GPU rendering (app packages for ICS, etc). Some apps don't(old apps). Force GPU UI rendering switch forces those apps to use GPU.
Pro. much smoother UI in apps that don't enable GPU rendering by default.
Con. Some visual bug may appear on some apps.
and what about battery life?
gannjunior said:
and what about battery life?
Click to expand...
Click to collapse
Theory 1; since the GPU is having some work right next to CPU it is an additional burden to battery to feed them both
Theory 2; Since they share the load they both can run at lower clocks so this means less voltage needed. Less voltage means less energy consumed.
So I guess there is no exact way to measure but nowadays most of the apps are already using that option default so it must be a good thing. At least the device does not have to run the CPU at max speed and heat up.
'Disable hardware overlays' what does this mean and should I enable it
Sent from my GT-I9300 using xda app-developers app
mohnim said:
'Disable hardware overlays' what does this mean and should I enable it
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Read this:
Without a hardware overlay every application that is displaying things on the screen will share video memory and will have to constantly check for collision and clipping to render a proper image, this can cost a lot of processing power. With a hardware overlay each application gets its own portion of video memory, getting rid of the need to check for collision and clipping.
Basically, using hardware overlays can reduce CPU usage by quite a bit
Click to expand...
Click to collapse
Source: http://rootzwiki.com/topic/28977-disable-hardware-overlays/#entry778564
thanks for the explanation
gannjunior said:
thanks for the explanation
Click to expand...
Click to collapse
Not to be "that guy", but there's a button for that.
I know that many of us have noticed that our RAZR HD has less than perfect graphical performance...i.e. Lag on home screen, etc.
I just forced GPU rendering in developer settings and changed animations to 2x. Everything seems much smoother and more liquid. The GPU can definitely have it taken care of. I'd recommend doing this, makes a significant difference for the better.
Sent from my DROID RAZR HD using xda app-developers app
I too have enabled force GPU Rendering, and doing so increased my quadrant score upwards of 300 points. However, I think the smoothness you are experiencing is more due to your slowing down the transitions, thus making them easier to render and more fluid feeling. That being said, I took your advice, and it does indeed feel smoother on the 2x.
Sent from my DROID RAZR MAXX HD using xda app-developers app
Which animations are you changing to 2x? Window animation scale? Transition animation scale? Or animator scale?
I changed all 3. It is much more silky, but not as speedy in animations. A trade off
Sent from my DROID RAZR HD using xda app-developers app
changed my animation to .5 so its not slow, and its so fast I don't see lag. quadrant score went up to 5442
Verdnan said:
changed my animation to .5 so its not slow, and its so fast I don't see lag. quadrant score went up to 5442
Click to expand...
Click to collapse
If you put all three below 1 you'll lose your crt screen animation, just an fyi.
Swyped while swerving from my Droid Razr Maxx HD
Sorry for being a botard noob, but what is the "quadrant score" and how do I check it? I'm guessing the higher the number the better?
Thanks!
LifeAsADroid said:
Sorry for being a botard noob, but what is the "quadrant score" and how do I check it? I'm guessing the higher the number the better?
Thanks!
Click to expand...
Click to collapse
Quadrant is a benchmark software. It gives you a score based on some tests (graphical, memory, cpu etc...). Indead the higher is better but keep in mind that it's not representative of user experience. You can have a big score in quadrant and a slow phone.
Placing animations on .5x makes then appear faster and have less lag, but in reality all that is doing is hiding stutter and lag with superfast frame rates.
IPhone and windows phone could certainly have faster animations but that defeats the purpose...the purpose is for a silky smooth and quality set of transitions and animations. Moving animations and transitions to 1.5x helps a lot in this goal.
For example, if you take a look at the new animations in the app tray when opening an app in jelly bean, they aren't necessarily superfast...but they are generally fluid, smooth and appealing to the eye.
Sent from my DROID RAZR HD using xda app-developers app
krycek1984 said:
Placing animations on .5x makes then appear faster and have less lag, but in reality all that is doing is hiding stutter and lag with superfast frame rates.
IPhone and windows phone could certainly have faster animations but that defeats the purpose...the purpose is for a silky smooth and quality set of transitions and animations. Moving animations and transitions to 1.5x helps a lot in this goal.
For example, if you take a look at the new animations in the app tray when opening an app in jelly bean, they aren't necessarily superfast...but they are generally fluid, smooth and appealing to the eye.
Sent from my DROID RAZR HD using xda app-developers app
Click to expand...
Click to collapse
Changing animation speeds to 0.5 does speed them up. Open the phone or messaging at on 1.0x setting then do the same at 0.5. It doesn't simply appear faster, it IS faster. In fact, if you turn off the animations completely, these apps open instantly. No lag, no stutter.
kishin14 said:
Changing animation speeds to 0.5 does speed them up. Open the phone or messaging at on 1.0x setting then do the same at 0.5. It doesn't simply appear faster, it IS faster. In fact, if you turn off the animations completely, these apps open instantly. No lag, no stutter.
Click to expand...
Click to collapse
Exactly what we're going for, right? Speed and efficiency. Sure, the graphics of things moving when they open and close is neat to see, but if it looks like the graphic is moving through syrup, it kills speed and efficiency.
If 0.5x looks smooth, but really isn't, who cares? You don't notice it anyway, so it's a non-issue at this point (all while speeding up the graphic opening and closing).
Enabling this preference in developer options offloads task of rendering window components like buttons, text and complex 2d graphics calculations to GPU. This often results in much faster UI rendering including animations.
On one side you will definitely achieve better frame rate (and hence smooth experience) throughout system, but you may end up using more battery. On certain devices, GPU consumes more power the CPU, hence you may observe 5-15% lower battery life with option enabled.
I would recommend having this option enabled on devices with weaker CPUs e.g. You should seldom need to enable this on dual-core 1.4ghz ARM CPU.
offloading UI rendering to GPU has obvious benefits so that CPU can work on other important tasks like database IO, data manipulation, layout calculations and responding to other user inputs.
So I upgraded my X compact to official Nougat 7.0 a couple of days back and on first impressions I noticed some lag here and there mostly when scrolling
And I knew that Snapdragon 650 is almost clos to SD810 so what could be the problem because it was awesomely fluid and smooth on MM 6.0.1, so I started to dig up and here's what I noticed:
In CPUz app on MM it shows Qualcomm SD 650 @ 1.8 GHz but today I looked it up and in Nougat it shows Qualcomm SD 650 @ 1.4 GHz!!! And if you look at cpu cores, those 2 last core Cpu4 and cpu5 are stopped (i guess those two are [email protected] cores right?)
So conclusion is that A72 cores which are the main core to maintain smoothness are offline for some reason so Im asking developers to dig this up and help us out
Thank you
If there is no activity they should be stopped. My old Xperia M2 usually had only 1 core out of 4 active at the minimum clock. Then sure, if something was running in the background all 4 kicked at the hight clock.
I can't check right now with Nougat (my phone is currently updating to it. But it seems to take an awful lot of time. I think it has been updating for 20 minutes or more. Hopefully it's just updating all Dalvik caches or what they are now), but in Marshmallow all 6 cores were always active even with the CPU nearly idle. In my case I think that helped to cause the somehow high battery drain I had (that and plus wakelocks spamming all time).
But sure, if that means the phone will start lagging, screw it. I could deal with a day of battery life, I sure can't deal (again. And then again and again!) with a keyboard showing up after 1 or more seconds also missing the keys while swiping.
PS: it finally installed. You're right. Something definitively looks wrong with it. The cores 4 & 5 are disabled even with Google Play doing some apps updates. Unless it's because CPU Z isn't supporting Nougat yet. I'll have to investigate more via adb.
PPS: It might be the typical placebo effect but it actually feels even smoother now! So I am not sure what's going on.
Nah definitly not smoother!
I Check with qualcomm app and those 2 core are off all the time and it is lagging very bad in many places
If you wanna see the lag you can go scroll fast in call log or install an app like telegram messenger and scrol in chats
And also I played spiderman unlimited game on it and its lagging there no
There was No lag at all on android 6
Guys please report this issue
I used CPU-Z and CPU N°4 and 5 seems to be stop.
After few hours I am not sur that there are more lag than before.
I made a test with Antutu, I had arround 75000 before the update, and arround 80000 after the update.
I think I will make a fresh installation tomorrow.
I don't have those problems....
edit: I HAVE THIS PROBLEM.....
Guys are you serious?!
You actually dont see the lags here and there? Ieven see it lags when there are some notifications and i wanna scroll em fast
Come on guys!
Can someone on 7.0 with the Issue use CPU-Z (from google play) and click on "online validation" and share thr link to the CPU information page here, please?
Kianush said:
Guys are you serious?!
You actually dont see the lags here and there? Ieven see it lags when there are some notifications and i wanna scroll em fast
Come on guys!
Click to expand...
Click to collapse
you are too much dramatic...... there are some lag but not so much and not so drastic.....
and battery life is much much better on nougat
cingolat said:
you are too much dramatic...... there are some lag but not so much and not so drastic.....
and battery life is much much better on nougat
Click to expand...
Click to collapse
Maybe I am but smoothness in compact size was the one and only reason I went for this little guy
And whats the point of havin SD650 if there isnt any A72 cores to operate
And I really prefer a 100% fluid rom than a couple of hours more juice...
Kianush said:
Maybe I am but smoothness in compact size was the one and only reason I went for this little guy
And whats the point of havin SD650 if there isnt any A72 cores to operate
And I really prefer a 100% fluid rom than a couple of hours more juice...
Click to expand...
Click to collapse
I agree with you, and hope in a future update to solve this bug(because it is obviously a bug), but for now I can live with this.... maybe I'm lucky, but I don't have big lags, just a little bit here and there..... hope in future 7.1.1 to solve that....
another thing I notice is a louder speaker sound.....
dcro95 said:
I used CPU-Z and CPU N°4 and 5 seems to be stop.
After few hours I am not sur that there are more lag than before.
I made a test with Antutu, I had arround 75000 before the update, and arround 80000 after the update.
I think I will make a fresh installation tomorrow.
Click to expand...
Click to collapse
Wich rom did you update from to get nougat?
Kianush said:
Nah definitly not smoother!
I Check with qualcomm app and those 2 core are off all the time and it is lagging very bad in many places
If you wanna see the lag you can go scroll fast in call log or install an app like telegram messenger and scrol in chats
And also I played spiderman unlimited game on it and its lagging there no
There was No lag at all on android 6
Guys please report this issue
Click to expand...
Click to collapse
I confirm it doesn't lag for me. I checked scrolling through a long chat in Whatsapp and through the list of all my apps in Google Play (the latter has always been slow. Now it loads immediately, that's why I felt it was snappier). Then I tested with Antutu and I have got 74K (not sure why @dcro95 has got 80K, though).
Then if you look in Antutu/Info/CPU/More you see that for core 5&6 it says they are disabled. But at the same time it shows the percentage of their are activity (which, being the cores disabled, should be none). I didn't have time to check with adb, yet. But what I suspected and it seems to be confirmed by Antutu is that there might be a "bug" where the values for the cores active have the "read" flag cleared, like it happened with the minfree values in Lollipop with some Xperia (M2 for sure. It was "-w--w-----" instead of "rw-rw----".
Anyway, in case of your very noticeable lag I'd suggest to first check your stamina settings. If I enable the Stamina the phone lags immediately. Either with Nougat or Marshmallow.
Oh, and it mat not matter f you didn't enable the Stamina before upgrading. After the upgrade plenty of my configuration parameters simply went bananas. It changed my WiFi settings, removing the static address. And in the case of an app (but I imagine more of them at this point), it modified the login. I'm sure the login was correct because I had a widget for that app active (and working fine).
PS: my battery life still sucks, though. Actually it is even worse than before. I may have to backup, reset and restore the phone and see if it helps.
kwaille said:
Wich rom did you update from to get nougat?
Click to expand...
Click to collapse
I had a customized FR ROM 34.1.A.3.49, I had the Nougat update by OTA.
I made some test with ANTUTU with Nougat ROM, the results are :
- 80160
- 75600
- 74600
- 80780
Miche1asso said:
I confirm it doesn't lag for me. I checked scrolling through a long chat in Whatsapp and through the list of all my apps in Google Play (the latter has always been slow. Now it loads immediately, that's why I felt it was snappier). Then I tested with Antutu and I have got 74K (not sure why @dcro95 has got 80K, though).
Then if you look in Antutu/Info/CPU/More you see that for core 5&6 it says they are disabled. But at the same time it shows the percentage of their are activity (which, being the cores disabled, should be none). I didn't have time to check with adb, yet. But what I suspected and it seems to be confirmed by Antutu is that there might be a "bug" where the values for the cores active have the "read" flag cleared, like it happened with the minfree values in Lollipop with some Xperia (M2 for sure. It was "-w--w-----" instead of "rw-rw----".
Anyway, in case of your very noticeable lag I'd suggest to first check your stamina settings. If I enable the Stamina the phone lags immediately. Either with Nougat or Marshmallow.
Oh, and it mat not matter f you didn't enable the Stamina before upgrading. After the upgrade plenty of my configuration parameters simply went bananas. It changed my WiFi settings, removing the static address. And in the case of an app (but I imagine more of them at this point), it modified the login. I'm sure the login was correct because I had a widget for that app active (and working fine).
PS: my battery life still sucks, though. Actually it is even worse than before. I may have to backup, reset and restore the phone and see if it helps.
Click to expand...
Click to collapse
Thank you for you info man but let me explain it to you again
Firstly, what Im saying is on microscopic scale, I do feel even the smallest amount of lag
The laging that comes up after turning on Stamina is waaaay more than the lag that I talked about in OP, of course that is big enough to be seen by anyone!
On android 6.0.1 I didnt see even the smallest lag absolutly nothing! but after the upgrade to 7.0 I was starting to see small lags here and there(you might not even see it! Im very sensitive in this case) like for example when you have 3 notifications try to open notification bar with slow to normal finger swipe down, it lags a little there, and other examples that i said before.
At first i thought maybe the rom is not well optimized but after I saw cpuz I was sure that those cores are off!
On android MM telegram messenger had no lags, nothing! But now it lags a lot when scrolling but i say again this "a lot" is in compariaon to MM! not to Xperia tipo!!!
So I am 100% positive that A72 1.8Ghz cores are not functioning.
Lets go and try to fix that, or wait for an update to fix it.
I created a thread here quoting your first post. Maybe it will get more attention
http://talk.sonymobile.com/t5/Xperi...ock/td-p/1187152/jump-to/first-unread-message
Have reboot the phone and the core 5 & 6 were activated (up to 1,8)
Just after make it sleep, the core were stopped. Maybe an issue with doze ?
However I can"t say it lag. It maybe a little longer to charge game or big app but I use them to rarely to compare
crazy-gump said:
Have reboot the phone and the core 5 & 6 were activated (up to 1,8)
Just after make it sleep, the core were stopped. Maybe an issue with doze ?
Click to expand...
Click to collapse
Same for me, after reboot and used photos, th� where actived and cpu turn at 1.8ghz. 5min after they where disable. I think it depend cpu use. I ve no lag.
Kianush said:
Thank you for you info man but let me explain it to you again
Firstly, what Im saying is on microscopic scale, I do feel even the smallest amount of lag.
Click to expand...
Click to collapse
Hmmm.. Nope, my friend. You talked about a lot of lag: these are your very own words: "it is lagging very bad in many places"
Now if the problem is that you perceive a microlag that could be. With Lagdroid I learned how to ignore that for good.
.
So I am 100% positive that A72 1.8Ghz cores are not functioning.
Lets go and try to fix that, or wait for an update to fix it.
Click to expand...
Click to collapse
And I am quite sure that the cores are active, as Antutu benchmark shows in the info section. In the attached picture you can see how Antutu shows that the cores 5 & 6 have a CPU load (which I made it varying moving the notification panel), while at the same time they are shown as disabled. That simply isn't possible. If a core is disabled it can't have any load. So yes, there is a bug, but that seems to be in the CPU monitoring. I doubt we would get 74K or plus in Antutu if those two cores were off.
Miche1asso said:
Hmmm.. Nope, my friend. You talked about a lot of lag: these are your very own words: "it is lagging very bad in many places"
Now if the problem is that you perceive a microlag that could be. With Lagdroid I learned how to ignore that for good.
.
And I am quite sure that the cores are active, as Antutu benchmark shows in the info section. In the attached picture you can see how Antutu shows that the cores 5 & 6 have a CPU load (which I made it varying moving the notification panel), while at the same time they are shown as disabled. That simply isn't possible. If a core is disabled it can't have any load. So yes, there is a bug, but that seems to be in the CPU monitoring. I doubt we would get 74K or plus in Antutu if those two cores were off.
Click to expand...
Click to collapse
So what you say is that those cores are functioning normally but its juat showing them sleep right?!?
Then please tell me whats the reason on these even small lags?
Those dont matter actually, I need to know why I cant play spiderman unlimited and asphalt 8 on ultra setting like before
You could test them yourself
See 4 a53 1.4GHz are enough for daily usage but on heavy usage its obiouse that those a72 cores are missing
But there is one probibility, that those guys become active on very high usage like antutu! But I guess thats gonna be VERY HIGH!
Miche1asso said:
And I am quite sure that the cores are active, as Antutu benchmark shows in the info section. In the attached picture you can see how Antutu shows that the cores 5 & 6 have a CPU load (which I made it varying moving the notification panel), while at the same time they are shown as disabled. That simply isn't possible. If a core is disabled it can't have any load. So yes, there is a bug, but that seems to be in the CPU monitoring. I doubt we would get 74K or plus in Antutu if those two cores were off.
Click to expand...
Click to collapse
I have exactly the same on Antutu, and the max frequency is 1804 MHz.