(Temp. fix:root reqd.) High CPU usage and battery drain due to Google Play Services.

Search This thread

Huebabbel

Member
Aug 12, 2015
13
6
The solution from this thread also helped me with com.google.android.gms eating CPU time on my RealMe 7 Pro with AospExtended ROM.
The logs look a bit different, thus I'm leaving this here so that others may find it.

This solved it: "pm disable com.google.android.gms/.chimera.GmsIntentOperationService"
Lots of other "pm disable" commands for related issues did not change anything.

I had already added the ota-update adblock entries mentioned earlier in this thread to solve a previous issue with gms battery consumption.

Using "Kernel Toolkit" to set the CPU scheduler to Conservative and changing the frequency up/down thresholds to 35/90 already mitigated the battery drain a bit, but it was still draining way too fast while in use.

"top -H" revealed that the .INSTALL_UPDATE thread of com.google.android.gms was using a full core.

"adb logcat" gave some more info on what was happening. There was the InstallationIntentOperation along with a CertPathValidatorException in an endless loop.
08-13 10:22:34.072 2604 2666 I SystemUpdate: [Control,InstallationControl] Installation progress updated to (0x116, -1.000).
08-13 10:22:34.190 2604 2666 I SystemUpdate: [Control,InstallationControl] Resume on reboot feature enabled: true.
08-13 10:22:34.377 2604 2666 I SystemUpdate: [Execution,ExecutionManager] Action pre-download-validate executed for 1.68 seconds.
08-13 10:22:34.401 2604 2666 I SystemUpdate: [Execution,ExecutionManager] Action exponential-backoff-delay-execution executed for 0.01 seconds.
08-13 10:22:34.442 2604 2666 I SystemUpdate: [Control,InstallationControl] Installation progress updated to (0x017, -1.000).
08-13 10:22:34.617 2604 2666 I SystemUpdate: [Control,InstallationControl] Resume on reboot feature enabled: true.
08-13 10:22:35.012 2604 2666 E SystemUpdate: [Execution,PreDownloadValidateAction] Failed to download.
08-13 10:22:35.012 2604 2666 E SystemUpdate: bmhu: Unknown download exception.
08-13 10:22:35.012 2604 2666 E SystemUpdate: at bmia.f:)[email protected][email protected] (150400-461192076):19)
08-13 10:22:35.012 2604 2666 E SystemUpdate: at bmia.e:)[email protected][email protected] (150400-461192076):3)
08-13 10:22:35.012 2604 2666 E SystemUpdate: at bmfv.a:)[email protected][email protected] (150400-461192076):42)
08-13 10:22:35.012 2604 2666 E SystemUpdate: at com.google.android.gms.update.execution.InstallationIntentOperation.onHandleIntent:)[email protected][email protected] (150400-461192076):14)
08-13 10:22:35.012 2604 2666 E SystemUpdate: at com.google.android.chimera.IntentOperation.onHandleIntent:)[email protected][email protected] (150400-461192076):2)
08-13 10:22:35.012 2604 2666 E SystemUpdate: at uzc.onHandleIntent:)[email protected][email protected] (150400-461192076):4)
08-13 10:22:35.012 2604 2666 E SystemUpdate: at ffs.run:)[email protected][email protected] (150400-461192076):3)
08-13 10:22:35.012 2604 2666 E SystemUpdate: at ffr.run:)[email protected][email protected] (150400-461192076):11)
08-13 10:22:35.012 2604 2666 E SystemUpdate: at cfnu.run:)[email protected][email protected] (150400-461192076):2)
08-13 10:22:35.012 2604 2666 E SystemUpdate: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
08-13 10:22:35.012 2604 2666 E SystemUpdate: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
08-13 10:22:35.012 2604 2666 E SystemUpdate: at java.lang.Thread.run(Thread.java:923)
08-13 10:22:35.012 2604 2666 E SystemUpdate: Caused by: java.util.concurrent.ExecutionException: java.lang.RuntimeException: Execution exception
08-13 10:22:35.012 2604 2666 E SystemUpdate: at java.util.concurrent.FutureTask.report(FutureTask.java:123)
08-13 10:22:35.012 2604 2666 E SystemUpdate: at java.util.concurrent.FutureTask.get(FutureTask.java:207)
08-13 10:22:35.012 2604 2666 E SystemUpdate: at bmia.f:)[email protected][email protected] (150400-461192076):16)
08-13 10:22:35.012 2604 2666 E SystemUpdate: ... 11 more
08-13 10:22:35.012 2604 2666 E SystemUpdate: Caused by: java.lang.RuntimeException: Execution exception
08-13 10:22:35.012 2604 2666 E SystemUpdate: at bmhy.run:)[email protected][email protected] (150400-461192076):5)
08-13 10:22:35.012 2604 2666 E SystemUpdate: at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:462)
08-13 10:22:35.012 2604 2666 E SystemUpdate: at java.util.concurrent.FutureTask.run(FutureTask.java:266)
08-13 10:22:35.012 2604 2666 E SystemUpdate: at xoc.c:)[email protected][email protected] (150400-461192076):6)
08-13 10:22:35.012 2604 2666 E SystemUpdate: at xoc.run:)[email protected][email protected] (150400-461192076):7)
08-13 10:22:35.012 2604 2666 E SystemUpdate: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
08-13 10:22:35.012 2604 2666 E SystemUpdate: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
08-13 10:22:35.012 2604 2666 E SystemUpdate: at xth.run:)[email protected][email protected] (150400-461192076):0)
08-13 10:22:35.012 2604 2666 E SystemUpdate: ... 1 more
08-13 10:22:35.012 2604 2666 E SystemUpdate: Caused by: bmhu: Unable to get response code.
08-13 10:22:35.012 2604 2666 E SystemUpdate: ... 9 more
08-13 10:22:35.012 2604 2666 E SystemUpdate: Caused by: javax.net.ssl.SSLHandshakeException: java.security.cert.CertPathValidatorException: Trust anchor for certification path not found.
08-13 10:22:35.012 2604 2666 E SystemUpdate: at com.google.android.gms.org.conscrypt.ConscryptFileDescriptorSocket.startHandshake:)[email protected][email protected] (150400-461192076):25)
08-13 10:22:35.012 2604 2666 E SystemUpdate: at bffn.b:)[email protected][email protected] (150400-461192076):2)
08-13 10:22:35.012 2604 2666 E SystemUpdate: at bffn.createSocket:)[email protected][email protected] (150400-461192076):9)
08-13 10:22:35.012 2604 2666 E SystemUpdate: at com.android.okhttp.internal.io.RealConnection.connectTls(RealConnection.java:185)
08-13 10:22:35.012 2604 2666 E SystemUpdate: at com.android.okhttp.internal.io.RealConnection.connectSocket(RealConnection.java:153)
08-13 10:22:35.012 2604 2666 E SystemUpdate: at com.android.okhttp.internal.io.RealConnection.connect(RealConnection.java:116)
08-13 10:22:35.012 2604 2666 E SystemUpdate: at com.android.okhttp.internal.http.StreamAllocation.findConnection(StreamAllocation.java:186)
08-13 10:22:35.012 2604 2666 E SystemUpdate: at com.android.okhttp.internal.http.StreamAllocation.findHealthyConnection(StreamAllocation.java:128)
08-13 10:22:35.012 2604 2666 E SystemUpdate: at com.android.okhttp.internal.http.StreamAllocation.newStream(StreamAllocation.java:97)
08-13 10:22:35.012 2604 2666 E SystemUpdate: at com.android.okhttp.internal.http.HttpEngine.connect(HttpEngine.java:289)
08-13 10:22:35.012 2604 2666 E SystemUpdate: at com.android.okhttp.internal.http.HttpEngine.sendRequest(HttpEngine.java:232)
08-13 10:22:35.012 2604 2666 E SystemUpdate: at com.android.okhttp.internal.huc.HttpURLConnectionImpl.execute(HttpURLConnectionImpl.java:465)
08-13 10:22:35.012 2604 2666 E SystemUpdate: at com.android.okhttp.internal.huc.HttpURLConnectionImpl.getResponse(HttpURLConnectionImpl.java:411)
08-13 10:22:35.012 2604 2666 E SystemUpdate: at com.android.okhttp.internal.huc.HttpURLConnectionImpl.getResponseCode(HttpURLConnectionImpl.java:542)
08-13 10:22:35.012 2604 2666 E SystemUpdate: at com.android.okhttp.internal.huc.DelegatingHttpsURLConnection.getResponseCode(DelegatingHttpsURLConnection.java:106)
08-13 10:22:35.012 2604 2666 E SystemUpdate: at com.android.okhttp.internal.huc.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:30)
08-13 10:22:35.012 2604 2666 E SystemUpdate: at bmhy.run:)[email protected][email protected] (150400-461192076):2)
08-13 10:22:35.012 2604 2666 E SystemUpdate: ... 8 more

"dumpsys activity broadcasts" also showed a lot of gms update spam:

#162: act=com.google.android.finsky.downloadservice.intent.action.WAKING_STATE_UPDATE_BROADCAST_ACTION flg=0x10000010 pkg=com.android.vending (has extras)
0 dispatch +17ms finish
enq=2022-08-13 10:12:02.195 disp=2022-08-13 10:12:02.195 fin=2022-08-13 10:12:02.212
extras: Bundle[{STRIPPED=1}]
#163: act=com.google.android.finsky.downloadservice.intent.action.STATE_UPDATE_BROADCAST_ACTION flg=0x10000010 pkg=com.android.vending (has extras)
0 dispatch 0 finish
enq=2022-08-13 10:12:02.188 disp=2022-08-13 10:12:02.188 fin=2022-08-13 10:12:02.188
extras: Bundle[{STRIPPED=1}]
#164: act=com.google.android.finsky.downloadservice.intent.action.WAKING_STATE_UPDATE_BROADCAST_ACTION flg=0x10000010 pkg=com.android.vending (has extras)
0 dispatch +22ms finish
enq=2022-08-13 10:12:02.117 disp=2022-08-13 10:12:02.117 fin=2022-08-13 10:12:02.139
extras: Bundle[{STRIPPED=1}]
#165: act=com.google.android.finsky.downloadservice.intent.action.STATE_UPDATE_BROADCAST_ACTION flg=0x10000010 pkg=com.android.vending (has extras)
0 dispatch 0 finish
enq=2022-08-13 10:12:02.125 disp=2022-08-13 10:12:02.125 fin=2022-08-13 10:12:02.125
extras: Bundle[{STRIPPED=1}]


Historical broadcasts [background]:
Historical Broadcast background #0:
BroadcastRecord{5fd6fba u0 com.google.android.gms.update.STATUS_CHANGED} to user 0
Intent { act=com.google.android.gms.update.STATUS_CHANGED flg=0x10 pkg=com.google.android.gms (has extras) }
extras: Bundle[{STRIPPED=1}]
caller=com.google.android.gms 2604:com.google.android.gms/u0a206 pid=2604 uid=10206
enqueueClockTime=2022-08-13 11:51:32.283 dispatchClockTime=2022-08-13 11:51:32.283
dispatchTime=-790ms (0 since enq) finishTime=-761ms (+29ms since disp)
resultTo=null resultCode=0 resultData=null
nextReceiver=1 receiver=null
Deliver +21ms #0: (manifest)
priority=0 preferredOrder=0 match=0x108000 specificIndex=-1 isDefault=false
ActivityInfo:
name=com.google.android.gms.chimera.GmsIntentOperationService$PersistentInternalReceiver
packageName=com.google.android.gms
processName=com.google.android.gms.persistent
enabled=true exported=false directBootAware=true
resizeMode=RESIZE_MODE_RESIZEABLE
Historical Broadcast background #1:
BroadcastRecord{8cf6e6b u0 com.google.android.gms.update.STATUS_CHANGED} to user 0
Intent { act=com.google.android.gms.update.STATUS_CHANGED flg=0x10 pkg=com.google.android.gms (has extras) }
extras: Bundle[{STRIPPED=1}]
caller=com.google.android.gms 2604:com.google.android.gms/u0a206 pid=2604 uid=10206
enqueueClockTime=2022-08-13 11:51:31.722 dispatchClockTime=2022-08-13 11:51:31.723
dispatchTime=-1s353ms (+1ms since enq) finishTime=-1s336ms (+17ms since disp)
resultTo=null resultCode=0 resultData=null
nextReceiver=1 receiver=null
Deliver +16ms #0: (manifest)
priority=0 preferredOrder=0 match=0x108000 specificIndex=-1 isDefault=false
ActivityInfo:
name=com.google.android.gms.chimera.GmsIntentOperationService$PersistentInternalReceiver
packageName=com.google.android.gms
processName=com.google.android.gms.persistent
enabled=true exported=false directBootAware=true
resizeMode=RESIZE_MODE_RESIZEABLE


#0: act=com.google.android.gms.update.STATUS_CHANGED flg=0x10 pkg=com.google.android.gms (has extras)
0 dispatch +29ms finish
enq=2022-08-13 11:51:32.283 disp=2022-08-13 11:51:32.283 fin=2022-08-13 11:51:32.312
extras: Bundle[{STRIPPED=1}]
#1: act=com.google.android.gms.update.STATUS_CHANGED flg=0x10 pkg=com.google.android.gms (has extras)
+1ms dispatch +17ms finish
enq=2022-08-13 11:51:31.722 disp=2022-08-13 11:51:31.723 fin=2022-08-13 11:51:31.740
extras: Bundle[{STRIPPED=1}]

This finally revaled com.google.android.gms.chimera.GmsIntentOperationService$PersistentInternalReceiver
I wonder if there's any way one would've arrived that this fix from just the logcat above.
 

PilotSoldier

New member
Aug 16, 2022
2
0
Xiaomi Poco X3 Pro
I have the same problem, It happened last week, so i have been seeing this task "com.google.android.gsm" taking 10~15% CPU Usage, I found a way to maybe just not burn the phone CPU + Battery

Go to Settings > All Apps > Scroll down till you find Google Play Services

Clear Data
+ Cache

Go to Permissions > Disallow "Body Sensors" + unnecessary permissions

Hope this helps
 

rocker00

Senior Member
Jun 23, 2012
494
492
I hadn't updated from the July build and today the issue was back. Will update after September build drops. Pixel Spoof is included in the ROM.
And I've the latest security patch (Aug) and the issue is back two days a go even after the modified spoofing, Lol, arrowos team has completely removed PixelPropsUtils, hope to see the same behavior on all the ROMs.
 

amn1987

Senior Member
Interestingly crDroid has an option "Unlimited Photos Storage" which I have disabled. Yet this issue cropped up after 2 months on the same build. Google still detects the device as Pixel 6 Pro though for ex. in the notification while logging into my Google account from another device.
 

mmortal03

Senior Member
Apr 15, 2014
332
54
Interestingly crDroid has an option "Unlimited Photos Storage" which I have disabled. Yet this issue cropped up after 2 months on the same build. Google still detects the device as Pixel 6 Pro though for ex. in the notification while logging into my Google account from another device.
I wish devs for these ROMs would just remove the spoofing code completely unless there is some absolute necessity, until a real fix comes along. It's inevitable that various phones will lose dev support and then it becomes a poison pill/ticking time bomb to have left it in.
 

rocker00

Senior Member
Jun 23, 2012
494
492
I wish devs for these ROMs would just remove the spoofing code completely unless there is some absolute necessity, until a real fix comes along. It's inevitable that various phones will lose dev support and then it becomes a poison pill/ticking time bomb to have left it in.
What seems strange to me that this issue makes the ROM unusable and the fix breaks many important functions, we identified the cause & the fix and no any response from the devs!!! and for what? the unlimited photos storage? there are many magisk modules to achieve that, messing with the framework to remove the spoofing isn't an easy job for the majority of users, why this stubbornness? that's really odd!!!

amn1987 That toggle has nothing to the with the issue, it's just to spoof the photos app,a small part of the spoofing, the cause of this issue is spoofing GMS.​

 
Last edited:

R4Ck

Senior Member
Aug 14, 2011
142
21
The solution from this thread also helped me with com.google.android.gms eating CPU time on my RealMe 7 Pro with AospExtended ROM.
The logs look a bit different, thus I'm leaving this here so that others may find it.

This solved it: "pm disable com.google.android.gms/.chimera.GmsIntentOperationService"
Lots of other "pm disable" commands for related issues did not change anything.

I had already added the ota-update adblock entries mentioned earlier in this thread to solve a previous issue with gms battery consumption.

Using "Kernel Toolkit" to set the CPU scheduler to Conservative and changing the frequency up/down thresholds to 35/90 already mitigated the battery drain a bit, but it was still draining way too fast while in use.

"top -H" revealed that the .INSTALL_UPDATE thread of com.google.android.gms was using a full core.

"adb logcat" gave some more info on what was happening. There was the InstallationIntentOperation along with a CertPathValidatorException in an endless loop.


"dumpsys activity broadcasts" also showed a lot of gms update spam:



This finally revaled com.google.android.gms.chimera.GmsIntentOperationService$PersistentInternalReceiver
I wonder if there's any way one would've arrived that this fix from just the logcat above.

This fixed the problem for me too.
Poco x3 pro crdroid 8.6

You can root, apply the pm command directly from adb shell and unroot, it sticks after reboots and unroots.
 
  • Like
Reactions: amn1987

X3User

Member
Jun 24, 2022
9
1
Is this issue only because of the spoofing as pixel? I'm currently on miui based rom (without unlimited photo storage or 90fps unlocked on games) for 2 weeks now and the issue has been fixed. Is miui based rom without spoofing safe from this issue? Thanks in advanced for the reply!
 

amn1987

Senior Member
Is this issue only because of the spoofing as pixel? I'm currently on miui based rom (without unlimited photo storage or 90fps unlocked on games) for 2 weeks now and the issue has been fixed. Is miui based rom without spoofing safe from this issue? Thanks in advanced for the reply!
Yes. Manufacturers for obvious reasons can never include Pixel spoof in their ROMs.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    The solution from this thread also helped me with com.google.android.gms eating CPU time on my RealMe 7 Pro with AospExtended ROM.
    The logs look a bit different, thus I'm leaving this here so that others may find it.

    This solved it: "pm disable com.google.android.gms/.chimera.GmsIntentOperationService"
    Lots of other "pm disable" commands for related issues did not change anything.

    I had already added the ota-update adblock entries mentioned earlier in this thread to solve a previous issue with gms battery consumption.

    Using "Kernel Toolkit" to set the CPU scheduler to Conservative and changing the frequency up/down thresholds to 35/90 already mitigated the battery drain a bit, but it was still draining way too fast while in use.

    "top -H" revealed that the .INSTALL_UPDATE thread of com.google.android.gms was using a full core.

    "adb logcat" gave some more info on what was happening. There was the InstallationIntentOperation along with a CertPathValidatorException in an endless loop.


    "dumpsys activity broadcasts" also showed a lot of gms update spam:



    This finally revaled com.google.android.gms.chimera.GmsIntentOperationService$PersistentInternalReceiver
    I wonder if there's any way one would've arrived that this fix from just the logcat above.

    This fixed the problem for me too.
    Poco x3 pro crdroid 8.6

    You can root, apply the pm command directly from adb shell and unroot, it sticks after reboots and unroots.
  • 7
    Google Play Services is causing high CPU usage and massive battery drain( >25%/h) continuously. Battery temps. cross 40°C in no time. The issue persisted upon rebooting the device. Had to finally freeze it.
    In FKM, I/O section shows constant 20-25MB/s writes. "com.google.android.gms" and "com.google.android.gms.persistent" are the two processes causing consistently high CPU usage. There's also "jbd2/sda1-8".
    After booting into Safe Mode the issue didn't persist. But still no idea what exactly is causing this issue.
    Poco F1 running crDroid 7.14. This issue cropped up the first time ever in build 7.7. Only resolved after dirty flashing 7.13. NikGApps Core version.

    Temp. fix : type the following in any Terminal emulator of your choice with the recommendation being Termux
    su
    pm disable com.google.android.gms/.chimera.GmsIntentOperationService

    If not rooted maybe try via ADB.

    Issue arises due to spoofing Pixels for the unlimited Google Photos backup hack. Real solution is either removal of the PixelPropsUtils framework or it's suitable modification. It's all in the hands of the ROM devs.
    7
    If the problem is "system update" of Google play services, perhaps we need to do a clean flash of a Rom with an updated Gapps package.
    Try this command:
    su
    pm disable com.google.android.gms/.chimera.GmsIntentOperationService
    After using it immediately the logcat spam stopped. It's been a few hours and it hasn't recurred. Got this from another user also suffering from this issue and he confirmed that it's been over a day since the issue last occurred.
    5
    The solution from this thread also helped me with com.google.android.gms eating CPU time on my RealMe 7 Pro with AospExtended ROM.
    The logs look a bit different, thus I'm leaving this here so that others may find it.

    This solved it: "pm disable com.google.android.gms/.chimera.GmsIntentOperationService"
    Lots of other "pm disable" commands for related issues did not change anything.

    I had already added the ota-update adblock entries mentioned earlier in this thread to solve a previous issue with gms battery consumption.

    Using "Kernel Toolkit" to set the CPU scheduler to Conservative and changing the frequency up/down thresholds to 35/90 already mitigated the battery drain a bit, but it was still draining way too fast while in use.

    "top -H" revealed that the .INSTALL_UPDATE thread of com.google.android.gms was using a full core.

    "adb logcat" gave some more info on what was happening. There was the InstallationIntentOperation along with a CertPathValidatorException in an endless loop.
    08-13 10:22:34.072 2604 2666 I SystemUpdate: [Control,InstallationControl] Installation progress updated to (0x116, -1.000).
    08-13 10:22:34.190 2604 2666 I SystemUpdate: [Control,InstallationControl] Resume on reboot feature enabled: true.
    08-13 10:22:34.377 2604 2666 I SystemUpdate: [Execution,ExecutionManager] Action pre-download-validate executed for 1.68 seconds.
    08-13 10:22:34.401 2604 2666 I SystemUpdate: [Execution,ExecutionManager] Action exponential-backoff-delay-execution executed for 0.01 seconds.
    08-13 10:22:34.442 2604 2666 I SystemUpdate: [Control,InstallationControl] Installation progress updated to (0x017, -1.000).
    08-13 10:22:34.617 2604 2666 I SystemUpdate: [Control,InstallationControl] Resume on reboot feature enabled: true.
    08-13 10:22:35.012 2604 2666 E SystemUpdate: [Execution,PreDownloadValidateAction] Failed to download.
    08-13 10:22:35.012 2604 2666 E SystemUpdate: bmhu: Unknown download exception.
    08-13 10:22:35.012 2604 2666 E SystemUpdate: at bmia.f:)[email protected][email protected] (150400-461192076):19)
    08-13 10:22:35.012 2604 2666 E SystemUpdate: at bmia.e:)[email protected][email protected] (150400-461192076):3)
    08-13 10:22:35.012 2604 2666 E SystemUpdate: at bmfv.a:)[email protected][email protected] (150400-461192076):42)
    08-13 10:22:35.012 2604 2666 E SystemUpdate: at com.google.android.gms.update.execution.InstallationIntentOperation.onHandleIntent:)[email protected][email protected] (150400-461192076):14)
    08-13 10:22:35.012 2604 2666 E SystemUpdate: at com.google.android.chimera.IntentOperation.onHandleIntent:)[email protected][email protected] (150400-461192076):2)
    08-13 10:22:35.012 2604 2666 E SystemUpdate: at uzc.onHandleIntent:)[email protected][email protected] (150400-461192076):4)
    08-13 10:22:35.012 2604 2666 E SystemUpdate: at ffs.run:)[email protected][email protected] (150400-461192076):3)
    08-13 10:22:35.012 2604 2666 E SystemUpdate: at ffr.run:)[email protected][email protected] (150400-461192076):11)
    08-13 10:22:35.012 2604 2666 E SystemUpdate: at cfnu.run:)[email protected][email protected] (150400-461192076):2)
    08-13 10:22:35.012 2604 2666 E SystemUpdate: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
    08-13 10:22:35.012 2604 2666 E SystemUpdate: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
    08-13 10:22:35.012 2604 2666 E SystemUpdate: at java.lang.Thread.run(Thread.java:923)
    08-13 10:22:35.012 2604 2666 E SystemUpdate: Caused by: java.util.concurrent.ExecutionException: java.lang.RuntimeException: Execution exception
    08-13 10:22:35.012 2604 2666 E SystemUpdate: at java.util.concurrent.FutureTask.report(FutureTask.java:123)
    08-13 10:22:35.012 2604 2666 E SystemUpdate: at java.util.concurrent.FutureTask.get(FutureTask.java:207)
    08-13 10:22:35.012 2604 2666 E SystemUpdate: at bmia.f:)[email protected][email protected] (150400-461192076):16)
    08-13 10:22:35.012 2604 2666 E SystemUpdate: ... 11 more
    08-13 10:22:35.012 2604 2666 E SystemUpdate: Caused by: java.lang.RuntimeException: Execution exception
    08-13 10:22:35.012 2604 2666 E SystemUpdate: at bmhy.run:)[email protected][email protected] (150400-461192076):5)
    08-13 10:22:35.012 2604 2666 E SystemUpdate: at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:462)
    08-13 10:22:35.012 2604 2666 E SystemUpdate: at java.util.concurrent.FutureTask.run(FutureTask.java:266)
    08-13 10:22:35.012 2604 2666 E SystemUpdate: at xoc.c:)[email protected][email protected] (150400-461192076):6)
    08-13 10:22:35.012 2604 2666 E SystemUpdate: at xoc.run:)[email protected][email protected] (150400-461192076):7)
    08-13 10:22:35.012 2604 2666 E SystemUpdate: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
    08-13 10:22:35.012 2604 2666 E SystemUpdate: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
    08-13 10:22:35.012 2604 2666 E SystemUpdate: at xth.run:)[email protected][email protected] (150400-461192076):0)
    08-13 10:22:35.012 2604 2666 E SystemUpdate: ... 1 more
    08-13 10:22:35.012 2604 2666 E SystemUpdate: Caused by: bmhu: Unable to get response code.
    08-13 10:22:35.012 2604 2666 E SystemUpdate: ... 9 more
    08-13 10:22:35.012 2604 2666 E SystemUpdate: Caused by: javax.net.ssl.SSLHandshakeException: java.security.cert.CertPathValidatorException: Trust anchor for certification path not found.
    08-13 10:22:35.012 2604 2666 E SystemUpdate: at com.google.android.gms.org.conscrypt.ConscryptFileDescriptorSocket.startHandshake:)[email protected][email protected] (150400-461192076):25)
    08-13 10:22:35.012 2604 2666 E SystemUpdate: at bffn.b:)[email protected][email protected] (150400-461192076):2)
    08-13 10:22:35.012 2604 2666 E SystemUpdate: at bffn.createSocket:)[email protected][email protected] (150400-461192076):9)
    08-13 10:22:35.012 2604 2666 E SystemUpdate: at com.android.okhttp.internal.io.RealConnection.connectTls(RealConnection.java:185)
    08-13 10:22:35.012 2604 2666 E SystemUpdate: at com.android.okhttp.internal.io.RealConnection.connectSocket(RealConnection.java:153)
    08-13 10:22:35.012 2604 2666 E SystemUpdate: at com.android.okhttp.internal.io.RealConnection.connect(RealConnection.java:116)
    08-13 10:22:35.012 2604 2666 E SystemUpdate: at com.android.okhttp.internal.http.StreamAllocation.findConnection(StreamAllocation.java:186)
    08-13 10:22:35.012 2604 2666 E SystemUpdate: at com.android.okhttp.internal.http.StreamAllocation.findHealthyConnection(StreamAllocation.java:128)
    08-13 10:22:35.012 2604 2666 E SystemUpdate: at com.android.okhttp.internal.http.StreamAllocation.newStream(StreamAllocation.java:97)
    08-13 10:22:35.012 2604 2666 E SystemUpdate: at com.android.okhttp.internal.http.HttpEngine.connect(HttpEngine.java:289)
    08-13 10:22:35.012 2604 2666 E SystemUpdate: at com.android.okhttp.internal.http.HttpEngine.sendRequest(HttpEngine.java:232)
    08-13 10:22:35.012 2604 2666 E SystemUpdate: at com.android.okhttp.internal.huc.HttpURLConnectionImpl.execute(HttpURLConnectionImpl.java:465)
    08-13 10:22:35.012 2604 2666 E SystemUpdate: at com.android.okhttp.internal.huc.HttpURLConnectionImpl.getResponse(HttpURLConnectionImpl.java:411)
    08-13 10:22:35.012 2604 2666 E SystemUpdate: at com.android.okhttp.internal.huc.HttpURLConnectionImpl.getResponseCode(HttpURLConnectionImpl.java:542)
    08-13 10:22:35.012 2604 2666 E SystemUpdate: at com.android.okhttp.internal.huc.DelegatingHttpsURLConnection.getResponseCode(DelegatingHttpsURLConnection.java:106)
    08-13 10:22:35.012 2604 2666 E SystemUpdate: at com.android.okhttp.internal.huc.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:30)
    08-13 10:22:35.012 2604 2666 E SystemUpdate: at bmhy.run:)com.google.androi[email protected][email protected] (150400-461192076):2)
    08-13 10:22:35.012 2604 2666 E SystemUpdate: ... 8 more

    "dumpsys activity broadcasts" also showed a lot of gms update spam:

    #162: act=com.google.android.finsky.downloadservice.intent.action.WAKING_STATE_UPDATE_BROADCAST_ACTION flg=0x10000010 pkg=com.android.vending (has extras)
    0 dispatch +17ms finish
    enq=2022-08-13 10:12:02.195 disp=2022-08-13 10:12:02.195 fin=2022-08-13 10:12:02.212
    extras: Bundle[{STRIPPED=1}]
    #163: act=com.google.android.finsky.downloadservice.intent.action.STATE_UPDATE_BROADCAST_ACTION flg=0x10000010 pkg=com.android.vending (has extras)
    0 dispatch 0 finish
    enq=2022-08-13 10:12:02.188 disp=2022-08-13 10:12:02.188 fin=2022-08-13 10:12:02.188
    extras: Bundle[{STRIPPED=1}]
    #164: act=com.google.android.finsky.downloadservice.intent.action.WAKING_STATE_UPDATE_BROADCAST_ACTION flg=0x10000010 pkg=com.android.vending (has extras)
    0 dispatch +22ms finish
    enq=2022-08-13 10:12:02.117 disp=2022-08-13 10:12:02.117 fin=2022-08-13 10:12:02.139
    extras: Bundle[{STRIPPED=1}]
    #165: act=com.google.android.finsky.downloadservice.intent.action.STATE_UPDATE_BROADCAST_ACTION flg=0x10000010 pkg=com.android.vending (has extras)
    0 dispatch 0 finish
    enq=2022-08-13 10:12:02.125 disp=2022-08-13 10:12:02.125 fin=2022-08-13 10:12:02.125
    extras: Bundle[{STRIPPED=1}]


    Historical broadcasts [background]:
    Historical Broadcast background #0:
    BroadcastRecord{5fd6fba u0 com.google.android.gms.update.STATUS_CHANGED} to user 0
    Intent { act=com.google.android.gms.update.STATUS_CHANGED flg=0x10 pkg=com.google.android.gms (has extras) }
    extras: Bundle[{STRIPPED=1}]
    caller=com.google.android.gms 2604:com.google.android.gms/u0a206 pid=2604 uid=10206
    enqueueClockTime=2022-08-13 11:51:32.283 dispatchClockTime=2022-08-13 11:51:32.283
    dispatchTime=-790ms (0 since enq) finishTime=-761ms (+29ms since disp)
    resultTo=null resultCode=0 resultData=null
    nextReceiver=1 receiver=null
    Deliver +21ms #0: (manifest)
    priority=0 preferredOrder=0 match=0x108000 specificIndex=-1 isDefault=false
    ActivityInfo:
    name=com.google.android.gms.chimera.GmsIntentOperationService$PersistentInternalReceiver
    packageName=com.google.android.gms
    processName=com.google.android.gms.persistent
    enabled=true exported=false directBootAware=true
    resizeMode=RESIZE_MODE_RESIZEABLE
    Historical Broadcast background #1:
    BroadcastRecord{8cf6e6b u0 com.google.android.gms.update.STATUS_CHANGED} to user 0
    Intent { act=com.google.android.gms.update.STATUS_CHANGED flg=0x10 pkg=com.google.android.gms (has extras) }
    extras: Bundle[{STRIPPED=1}]
    caller=com.google.android.gms 2604:com.google.android.gms/u0a206 pid=2604 uid=10206
    enqueueClockTime=2022-08-13 11:51:31.722 dispatchClockTime=2022-08-13 11:51:31.723
    dispatchTime=-1s353ms (+1ms since enq) finishTime=-1s336ms (+17ms since disp)
    resultTo=null resultCode=0 resultData=null
    nextReceiver=1 receiver=null
    Deliver +16ms #0: (manifest)
    priority=0 preferredOrder=0 match=0x108000 specificIndex=-1 isDefault=false
    ActivityInfo:
    name=com.google.android.gms.chimera.GmsIntentOperationService$PersistentInternalReceiver
    packageName=com.google.android.gms
    processName=com.google.android.gms.persistent
    enabled=true exported=false directBootAware=true
    resizeMode=RESIZE_MODE_RESIZEABLE


    #0: act=com.google.android.gms.update.STATUS_CHANGED flg=0x10 pkg=com.google.android.gms (has extras)
    0 dispatch +29ms finish
    enq=2022-08-13 11:51:32.283 disp=2022-08-13 11:51:32.283 fin=2022-08-13 11:51:32.312
    extras: Bundle[{STRIPPED=1}]
    #1: act=com.google.android.gms.update.STATUS_CHANGED flg=0x10 pkg=com.google.android.gms (has extras)
    +1ms dispatch +17ms finish
    enq=2022-08-13 11:51:31.722 disp=2022-08-13 11:51:31.723 fin=2022-08-13 11:51:31.740
    extras: Bundle[{STRIPPED=1}]

    This finally revaled com.google.android.gms.chimera.GmsIntentOperationService$PersistentInternalReceiver
    I wonder if there's any way one would've arrived that this fix from just the logcat above.
    2
    So, my question is... has anyone figured out WHAT EXACTLY has been screwed up by disabling GmsIntentOperationService, because it's rather important, as I understand it? No problem not having notifications on Google Keep, since I am not using it. Are push messages still ok, for say... Whatsapp, Telegram? What did disablint that service screw up?

    Any other possible fix found? It's unbelievable that most devs don't acknowledge the issue on custom roms and fix it...

    It's definitely rather important, and I'd ideally like to know, too. But as far as any other possible fix, I can report to you that Moto G5 Plus users like me just received an updated CrDroid ROM yesterday, and whatever the dev did -- whether it was building in the hosts file blocking, or something with incorporating the latest Android bug fixes -- but it fixed our constant barrage of SystemUpdate logcat messages. I believe, as per the above posts by rocker00, that if a dev sought to remove some of the Pixel spoofing code it could also deal with it. Ideally, I'd love to know why or how the spoofing code specifically causes it.
    2
    `pm disable com.google.android.gms/.chimera.GmsIntentOperationService` works but this command breaks google keep notifications :(