App installations are causing FpsCentralContr (FpsCentralControl service) to kick up CPU usage to 95%, and it stays there, doesn't come down. Even after screen is off it stays there, eating 95% cpu time.
Remember, even manual apk installation from file manager is triggering this behaviour, so not completely dependent on Google Play Services, IMO at least.
Due to this, cpu is kept clocking at 2.96 continuously, which intimately reduces battery life and causes device heating.
And these high temps in turn result in slower charging speed even on 30w charger.
Ps: following observations were made using ADB tool and armoury crate for temp reading, device was not rooted, and @FiREPLAY guided key stuff.
I doubt highly, as per my findings, issue is triggered by the app installations not the armory crate, people are thinking clearing data and restarting solves problem, is partially wrong.
See after reboot, FpsCentralContr won't trigger, (atleast it will not Hogg like 95%cpu), so whenever you install app, manually or via app store, Then it will trigger FpsCentralContr and you start noticing this heating and battery drain.
So clearing AC's data and won't do anything, its just That, reboot will itself temporarily stop the issue.
you can still do the installation, but after install apps(APK or playstore), trigger FOTAService(check for system updtae) then kill that process again from developer options -> running process
Comments
Some latest fundings:
App installations are causing FpsCentralContr (FpsCentralControl service) to kick up CPU usage to 95%, and it stays there, doesn't come down. Even after screen is off it stays there, eating 95% cpu time.
Remember, even manual apk installation from file manager is triggering this behaviour, so not completely dependent on Google Play Services, IMO at least.
Due to this, cpu is kept clocking at 2.96 continuously, which intimately reduces battery life and causes device heating.
And these high temps in turn result in slower charging speed even on 30w charger.
Ps: following observations were made using ADB tool and armoury crate for temp reading, device was not rooted, and @FiREPLAY guided key stuff.
Why is not allowed to disable Armoury Crate?
Can we downgrade Armory Crate to try to fix?
https://www.apkmirror.com/apk/zenui-asus-computer-inc/armoury-crate/armoury-crate-3-3-0-49_200720-release/armoury-crate-3-3-0-49_200720-android-apk-download/
You wont be able to go back to the previous firmware I am afraid.
There are some suggestions here to minimise the problem while we wait for an update.
Downgrading to Android 9 and updating to 10 again. (Will lost data)
That too I guess.
I assumed it meant from A10 to another A10 firmware.
https://www.asus.com/Phone/ROG-Phone-II/HelpDesk_Download/
I doubt highly, as per my findings, issue is triggered by the app installations not the armory crate, people are thinking clearing data and restarting solves problem, is partially wrong.
See after reboot, FpsCentralContr won't trigger, (atleast it will not Hogg like 95%cpu), so whenever you install app, manually or via app store, Then it will trigger FpsCentralContr and you start noticing this heating and battery drain.
So clearing AC's data and won't do anything, its just That, reboot will itself temporarily stop the issue.
FpsCentralContr is a service part of Armory Crate?
I haven't updated to 2009.47,yet but there is an update notification for me in the settings, do you guys want me to update or not,any suggestions
Nope its part of HardwareStub (com.asus.hardwarestub)
I've shared some more detail on the 4th page you can check it out. :)
I suggest you wait till the next one with a fix
@Gustav_ASUS
nice catch, I can confirm that installing a standalone APK also make CPU spike at 2.96Ghz. So it's not totally Google play store issue.
Mods, may need Devs to switch a bit the focus
But again, if I turn On FOTAService, then kill the process, CPU goes down again
Please quick fix this
Okay thanks for the suggestion, did you get the charge limit to 80 % and 10 W charge speed options in the latest update?
So, disable Play Store and not installing an app "solve" temporarilly the issue!
you can still do the installation, but after install apps(APK or playstore), trigger FOTAService(check for system updtae) then kill that process again from developer options -> running process
The problem is "Google Play Services" and "Google Play" auto install themselves.
The problem is that "Google Play Services" and "Google Play" install themselves.
didi APK install also go through Google play service? or just apps from google play store?
if google play service is the matter, will this help?