yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] chaoscreater:
Could you share what you've disabled in Google Play Services? I've seen a lot of threads over the years and tried them, but they always either cause more battery drain or don't make much of a difference.
[Android Q&A, Help & Troubleshooting] amn1987:
Those fixes might work only because the ROM build actually doesn't incorporate the Pixel Spoof hack. Otherwise there's no other way to counter this issue save for the terminal command.
[Android Q&A, Help & Troubleshooting] chaoscreater:
Sorry, I'm lost here.

I saw a bunch of wakelocks related to chimera.GmsIntentOperationService on my device and after a bit of Googling, I found this thread. I have no context about whatever ROM build or Pixel Spoof hack you're referring to.

I know how to disable the chimera.GmsIntentOperationService (which I'm assuming is what you were referring to when you mentioned terminal command).

The question I asked luxsam5 was more about how he was able to stop Google Play Services from updating automatically. I know how to prevent apps from updating or even being detected by the Play Store, but I've never heard of how to stop Play Services itself from updating. Or perhaps I'm reading it wrong and that he used App Manager to disable chimera.GmsIntentOperationService service, which is just the same as you would do using the ADB command in the first post.
[Android Q&A, Help & Troubleshooting] ImDooMLoRD:
Sry i was wrong the Tasker thing didn't helped at all in any case.

But, i did a dirty flash and it's working fine for now.👍
[Android Q&A, Help & Troubleshooting] arunsai123:
Latest stable. the one without magisk hide support and uses zygisk.
[Android Q&A, Help & Troubleshooting] amn1987:
The issue is back today. Gonna have to dirty flash the ROM again.
[Android Q&A, Help & Troubleshooting] joke19:
Test this

GitHub - gloeyisk/universal-gms-doze: Patches Google Play services app and certain processes/services to be able to use battery optimization

Patches Google Play services app and certain processes/services to be able to use battery optimization - gloeyisk/universal-gms-doze

github.com
[Android Q&A, Help & Troubleshooting] amn1987:
Thanks but this isn't related to battery optimization for Google Play Services. It's anyway built into NikGApps. In fact idle drain isn't affected (probably because Tasker enables Battery Saver after screen off) only active drain is massively increased, around 25%/h. System Updates spams the logcat continuously.
[Android Q&A, Help & Troubleshooting] o0vampire0o:
hi guys, i have a redmi note 7 with lineage os. same bug. i haven't found a solution

EDIT: my logcat is letterally FULL of this

[Execution,ExecutionManager] Unable to create the action. Restart the execution from the scratch.

java.lang.IllegalStateException

at vus.j:)com.google.android.gms@221213044@22.12.13 (190400-437850846):0)

at binz.f:)com.google.android.gms@221213044@22.12.13 (190400-437850846):0)

at bims.a:)com.google.android.gms@221213044@22.12.13 (190400-437850846):10)

at com.google.android.gms.update.execution.InstallationIntentOperation.onHandleIntent:)com.google.android.gms@221213044@22.12.13 (190400-437850846):12)

at com.google.android.chimera.IntentOperation.onHandleIntent:)com.google.android.gms@221213044@22.12.13 (190400-437850846):2)

at ttn.onHandleIntent:)com.google.android.gms@221213044@22.12.13 (190400-437850846):4)

at eqt.run:)com.google.android.gms@221213044@22.12.13 (190400-437850846):3)

at eqs.run:)com.google.android.gms@221213044@22.12.13 (190400-437850846):11)

at cbhi.run:)com.google.android.gms@221213044@22.12.13 (190400-437850846):2)

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)

at java.lang.Thread.run(Thread.java:920)
[Android Q&A, Help & Troubleshooting] ares93:
I have the same issue on a Poco X3 Pro running Pixel experience 12.

Its has something to do with play services going into an update loop. A dirty flash has not fixed the issue.

I can temporarily fix it by using Servicely in rooted mode, and manually enable a bunch of play store services that are disabled. I'm not sure if this is purposeful in the rom or part of the issue. But enabling them makes it normal for a few hours.

I use my phone heavily at work so downtime to reflash and restore a backup is unfeasible until the weekend. Got it pretty much plugged in the entire day right now.

I'll reflash on friday evening.
[Android Q&A, Help & Troubleshooting] amn1987:
It's surprising that this thread couldn't attract the attention of even one person with the requisite knowledge to analyse the logs. I had created a thread on Reddit as well but it fared no better.

Previously dirty flashing a new build would fix this issue for about a month until it would recur. A11 builds were deprecated last month and dirty flashing the current build again could not temporarily fix the issue. Clean flash could probably fix it for good. I plan to do so in a couple of weeks time. Meanwhile I am forced to keep Play Services frozen which is highly inconvenient.
[Android Q&A, Help & Troubleshooting] amn1987:
I had reinstalled Servicely after a long gap some months ago which could have coincided when this issue first reappeared. Just as you mentioned a bunch of services related to Play Services were blocked. My first thought was maybe I had blocked them myself so re-enabled everything, uninstalled Servicely and rebooted. But just after an hour this issue was back. Reinstalled Servicely and now I just re-enable those services whenever they become disabled. I have disabled AdAway and battery optimization for Play Services. Also a bunch of apps like App Ops, Shizuku which could potentially have an impact. But ultimately a clean flash is necessary it seems. I will probably reinstall all apps from scratch as well instead of restoring with Swift Backup.
[Android Q&A, Help & Troubleshooting] o0vampire0o:
Nothing. I used Servicely but it's the same. Tomorrow I'll wipe the phone.

It's strange because if I have the screen on or bt on there is the battery drain, but if the bt is off the phone go in deep sleep without problems. Do you know is the play services has something connected to the bt?
[Android Q&A, Help & Troubleshooting] amn1987:
After freezing Play Services I re-enable the 2 services related to Play Services that are shown in Servicely as being disabled then defrost Play Services and the issue doesn't recurr for around 2 hours. This doesn't impact idle drain in my case probably because battery optimization is enabled for Play Services. I have disabled optimization so let's see how it goes.

After the temporary fix in the logcat I found this :W/azfh (32309): java.lang.SecurityException: Permission denial: com.google.android.gms writing to settings requires:android.permission.WRITE_DEVICE_CONFIG

This seemed similar to the issue referenced here https://gitlab.opengapps.org/opengapps/all/-/issues/3

I added the fix to the default-permissions file. I could change its file attributes but dunno if it will stick after a reboot or not. Hopefully this will do the trick.
[Android Q&A, Help & Troubleshooting] o0vampire0o:
Can you tell me where can i find default-permission? So I can try the trick
[Android Q&A, Help & Troubleshooting] amn1987:
It's mentioned in the link. Anyway etc/default-permissions/opengapps-permissions-q.xml I am using BitGApps currently and in the default-permissions folder there was only the default-permissions.xml file. In it I added the following:

<exception package="com.google.android.gms.persistent">

<permission name="android.permission.WRITE_DEVICE_CONFIG" fixed="false"/>

</exception>

I don't know if a reboot is necessary or not. Anyway I haven't and so far the issue hasn't recurred. Too early to tell though.
[Android Q&A, Help & Troubleshooting] o0vampire0o:
I have the pixel experience and practically every Google services is in the rom... So i suppose i have to check in the system root. Ok
[Android Q&A, Help & Troubleshooting] amn1987:
As of now the issue hasn't recurred. By far the longest stretch yet.

Edit: It's back with a vengeance. Can't seem to control it via Servicely anymore. Back to freezing Play Services.
[Android Q&A, Help & Troubleshooting] amn1987:
I am not gonna waste any more time in this until I am ready to do a clean flash. XDA seems to be a pale shadow of it's former self sadly.
[Android Q&A, Help & Troubleshooting] ares93:
As expected a clean flash fixed the issue. Didn't find another solution so i bit the bullet
[Android Q&A, Help & Troubleshooting] bl4ckest:
clean flash not help - problem return for a few days
[Android Q&A, Help & Troubleshooting] amn1987:
SystemUpdate entries are continuously spamming the logcat?
[Android Q&A, Help & Troubleshooting] o0vampire0o:
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.
[Android Q&A, Help & Troubleshooting] amn1987:
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.
[Android Q&A, Help & Troubleshooting] o0vampire0o:
Thx it works I'll check every day. Anyway tomorrow I'll update the phone at android 12 with a new Gapps package. If even the new has the bug I'll write here

Edit: today the logcat continues to be free from the spam. Anyway, yesterday i updated the play services at the last beta version available, the 22.12.13 (190400-437850846) no DPI from apkmirror
[Android Q&A, Help & Troubleshooting] amn1987:
Yes it's the same in my case. It's such a relief. Now I can clean flash according to my convenience. Also Play Services RAM usage seems to have halved to 170-oddB from 350-400MB on average earlier.

I had also flashed 22.13 while searching for a fix. Then went back to December 2021 build from NikGApps. But despite a dirty flash the Play Services version continues to be 22.13!
[Android Q&A, Help & Troubleshooting] amn1987:
If the fix continues to hold for some more days I will edit the thread title as Solved and post it in the OP.
[Android Q&A, Help & Troubleshooting] rocker00:
I can confirm that this solution is 100% working , since yesterday everything seems to be fine, my log is exact same like yours, SystemUpdate is the key of this issue, and I'm not able to identify what is the reason of this issue cuz it suddenly appeared without modifying anything! tried a clean flash, tried the base apk from Pixel 6 pro as a system app, tried to use the updated version from play store as a base apk on the system but nothing helped, my only doubt now is about spoofing the device which is used on most (if not all) the ROMs now, maybe google has changed something to detect that spoofing same like vanced manager which is detected now as a harmful app by Google Play Protect, maybe that spoofing has to be modified or even removed from the framework, have to wait for the next update of the ROM to see. Thanks for sharing the solution.
[Android Q&A, Help & Troubleshooting] amn1987:
I thought since Play Services would only be trying to download OTA updates on Pixel devices maybe it was something to do with the Pixel spoof for unlimited backup of photos. So I changed it to the original fingerprint of F1 but to no avail.
[Android Q&A, Help & Troubleshooting] amn1987:
https://developer.android.com/work/dpc/system-updates This could be a possible explanation for the issue. In my case the issue would popup at roughly 30 day intervals which conicides with the OTA update intervals. Dirty flashing a new version would postpone it for another 30 days. Since 7.15 was the last A11 build Google is now exacting vengeance.
[Android Q&A, Help & Troubleshooting] amn1987:
Another user had reported for a few months that System was downloading gigabytes of data every month. Maybe in his case the issue was the same only it was data wastage instead of battery drain.
[Android Q&A, Help & Troubleshooting] rocker00:
Changing the fingerprint is not enough at all or even useless, see the attachment, this is from Ancient Rom A12, spoofing is deeply integrated in the framework, they make a specefic apps like gms (which is the case here), photos, google app and more to be spoofed.
[Android Q&A, Help & Troubleshooting] amn1987:
I wonder why more users haven't reported this issue. Granted most of them might have moved to A12 builds already but in my case this appeared at least 4 months ago and in case of crDroid at least there was no A12 build back then.
[Android Q&A, Help & Troubleshooting] amn1987:
Has anyone experienced apps especially Google apps like Gmail, Calendar even GCam crashing after deploying the fix and not performing a clean flash? After a dirty flash the permissions had been reset. But the issue persists even after allowing all necessary permissions.
[Android Q&A, Help & Troubleshooting] o0vampire0o:
Another good day with the fix. We will wait the "next ota". Question: and if the rom devs will fix the bug before the compilation of the rom? Is it possible?
[Android Q&A, Help & Troubleshooting] amn1987:
No idea. In my case A11 builds are EOL. I haven't come across anyone running A12 with this issue.
[Android Q&A, Help & Troubleshooting] amn1987:
After almost a week's passing the fix continues to hold.
[Android Q&A, Help & Troubleshooting] laviniu_c:
another victim here, cmd worked for me too.

such a stupid error...

for anyone unsure, you can also temp fix it by killing the gms process 4-5 times, eventually it gives up for up to 1day
[Android Q&A, Help & Troubleshooting] ruruoli:
`pm disable com.google.android.gms/.chimera.GmsIntentOperationService` works but this command breaks google keep notifications :(
[Android Q&A, Help & Troubleshooting] laviniu_c:
that's interesting, might be worth leaving the intent enabled and disabling notifications on keep the normal way. in case that's what's actually causing the initial spin/lock.

L.E. didnt even know google keep has notifications.
[Android Q&A, Help & Troubleshooting] amn1987:
Only in case of Google Keep? I don't use it but no issues in case of the several other Google apps I use.
[Android Q&A, Help & Troubleshooting] tmstaedt:
can confirm that. But I took another approach and as root, killed the installd process. log SPAM and high CPU usage are gone and no other strange side effects so far.

Device: oneplus3, android 11 msm-xtended custom ROM

Thomas Mittelstaedt in Xtended Official Community

Tried the following: As root, open a terminal or via adb shell and kill process installd. Looks good so far, Google play store works normally, also those calendar and Google keep notifications work. Will observe a little more...😉

t.me
[Android Q&A, Help & Troubleshooting] ruruoli:
I've tried disabling this installd service, it doesn't helped in A12L
[Android Q&A, Help & Troubleshooting] castaway1:
any way to fix it but dont brake google keep?
[Android Q&A, Help & Troubleshooting] ruruoli:
1) upgrade your rom every month

2) find a rom which supports "google play system update" (there are few of them), maybe system update will actually work on them
[Android Q&A, Help & Troubleshooting] amn1987:
After an irrecoverable bootloop( probably due to LSPosed plus the necessity to freeze the Magisk Manager app to get a few banking apps working) I finally decided to move to an A12 and as expected this issue didn't occur.
[Android Q&A, Help & Troubleshooting] ruruoli:
If your rom is new enough (may/june patch) there will be no system update for you, wait a month or two (maybe three) and it will start to occur.
[Android Q&A, Help & Troubleshooting] amn1987:
A12 builds are updated monthly so there shouldn't be any issue.
[Android Q&A, Help & Troubleshooting] livingbeing:
hi, did you find any solution to solve this without root?

when I check my log file from adb, I am quite sure that the problem will occur once a day at every "SystemUpdate" service from play store,

without root, i can only kill the play service at that time from developer settings
[Android Q&A, Help & Troubleshooting] amn1987:
Try the command in ADB. Otherwise the real fix is to switch to an upto date ROM.
[Android Q&A, Help & Troubleshooting] amn1987:
What's the current status?
[Android Q&A, Help & Troubleshooting] mmortal03:
I believe it's still an issue on some A12.1 builds (see below). Also, someone in the Telegram chat told me that disabling com.google.android.gms/.chimera.GmsIntentOperationService broke more than just Google Keep -- it broke sync in various ways. For those of us without good A12 builds available, such as Moto G5 Plus, this is really frustrating.

https://xdaforums.com/t/rom-12-1-po...aosp-2022-07-13.4038949/page-81#post-87043581
[Android Q&A, Help & Troubleshooting] amn1987:
In A11, Contacts sync had stopped working and some reminders from Calendar were missing most of the time. Probably due to this issue. I had read somewhere of a Magisk module to disable Google Play System Update but couldn't find it anywhere. In my case after updating to A12 fortunately it's not an issue.
[Android Q&A, Help & Troubleshooting] amn1987:
Maybe microG is worth a shot if this issue persists in case of upto date builds as well. I suspect this issue could be related to spoofing devices as Pixels for the unlimited Google Photos backup hack.
[Android Q&A, Help & Troubleshooting] mmortal03:
That's a good idea. I just did a bit of searching and it didn't bring up much as far as recent potter support for microG, though, and I'm really not interested in trying to compile my own right now. What's frustrating is that I have no need for the unlimited Google Photos hack!

It was just suggested to me that, if a backport can be made from a fix in 12.1, that we look at commits in PixelPropsUtil (frameworks/base/core/java/com/android/internal/util/custom/PixelPropsUtils.java)

https://xdaforums.com/t/rom-12-1-po...aosp-2022-07-13.4038949/page-83#post-87166011
[Android Q&A, Help & Troubleshooting] amn1987:
MicroG isn't device dependent AFAIK. Just flash the module or the zip as the case might be.

It will be good to have a proper fix for this frustrating issue as at some point ROM development will stop for most devices.
[Android Q&A, Help & Troubleshooting] mmortal03:
I haven't installed MicroG before, but I understand the basic concept, and I've been reading up on it since you mentioned it. I read that it needs signature spoofing support in the OS, which CrDroid supposedly has, but, in this particular case, if my purpose is simply to get around a bug in Google Play services, then the goal would be to *not* go down the rabbit hole of full-on MicroG, right? I could be misunderstanding it, so correct me if I'm wrong, but I don't believe there's some way to just swap out the gapps version of com.google.android.gms with the MicroG version of it and keep everything else the same (i.e. the regular Play Store and the common Google apps included with opengapps or whatever)?
[Android Q&A, Help & Troubleshooting] amn1987:
No it doesn't work that way. I couldn't stick to microG for very long even in a years old entry-level device where it's super low resource usage would have been very handy due to app incompatibilities. Some apps that worked fine without Play Services would just crash with microG. As a stopgap solution it should be OK while waiting for a proper fix.
[Android Q&A, Help & Troubleshooting] mmortal03:
I guess I'll take the opportunity to at least tinker with microG, and see what I learn.
[Android Q&A, Help & Troubleshooting] mmortal03:
Are there any other such commands that might have an effect here? I found a very old thread referring to the following, but none of these have an effect on this issue:

adb shell su -c pm disable com.google.android.gms/.update.SystemUpdateActivity
adb shell su -c pm disable com.google.android.gms/.update.SystemUpdateService
adb shell su -c pm disable com.google.android.gms/.update.SystemUpdateService$ActiveReceiver
adb shell su -c pm disable com.google.android.gms/.update.SystemUpdateService$Receiver
adb shell su -c pm disable com.google.android.gms/.update.SystemUpdateService$SecretCodeReceiver

Trying to think outside the box, the following guy blocked OTA updates by write-protecting the ota_package folder on boot! That doesn't seem to apply here, but I wonder if something along those lines could work.

Section in tutorial on disabling OTA updates outdated · Issue #2463 · topjohnwu/Magisk

The section describing how to disable automatic OTA updates no longer works. The toggle has no effect and some updates (not all, presumably only those marked as "mandatory") are downloaded and inst...

github.com
[Android Q&A, Help & Troubleshooting] amn1987:
I had tried the first but it didn't work IIRC.
[Android Q&A, Help & Troubleshooting] rocker00:
All A12L ROMs that I've tried are affected by this issue, derpfest, ricedroid, sparkos and cherishos, so it doesn't really matter about the android version or the ROM is outdated or so, as i mentioned before, seems like that spoofing has to be modified or even completely removed from the framework, I've tried to mess with build.prop by modifying many things but nothing helped, for example, why Miui stock ROMs are not affected? simply, no spoofing!

I hope that the developers pay more attention to this cuz this is really annoying and the solution brings more issues!
[Android Q&A, Help & Troubleshooting] mmortal03:
@rocker00 , even if that's true, maybe on the affected ROMs the devs can find a way to spoof things even further, lol, to get around this particular issue -- rather than remove all the spoofing. :) I don't care which way they do it, as long as we can find a fix.
[Android Q&A, Help & Troubleshooting] rocker00:
@mmortal03 I'm not saying that the spoofing is completely useless, but in this situation at least Google stuff has to be removed, they can keep the spoofing for the games to get a higher fps and every stuff but Google, for example, who cares about having an unlimited photos storage and in return you get overheating, bad performance and battery drain?
[Android Q&A, Help & Troubleshooting] amn1987:
I have tried 2 different A12 ROMs so far and in both the issue isn't present despite the hack to get unlimited backup in Google Photos. Maybe it will be back if I stay on a build for a month or more...
[Android Q&A, Help & Troubleshooting] rocker00:
YES! it's the spoofing :D

I'm on MSM-Xtended A11 right now, completely removed the spoofing stuff from the framework, did a clean flash (just to start from the beginning) followed by the modified framework, restored my apps and updated everything and as expected, THE ISSUE IS COMPLETELY GONE, BUT, safetynet isn't passing now (CTS fails) :p .

Now the reason is 100% known, it's the devs time to modify the spoofing.

I'll keep updating if i solved the safetynet, according to my experience, I'll try to change the fingerprint or the security patch level, otherwise I've no idea cuz the safetynet was passing before removing the spoofing.

Edit: Successfully passed the safetynet by changing the security patch date level to the one that matching the fingerprint I'm using, i always use the original fingerprint for my device, this might not be an issue for all since not everyone changing the fingerprint, but in case if anyone is doing the same make sure to change the security patch level to the one that matching the fingerprint your are using and don't get scared that the device is showing and old security patch level, it's just a number.

Google is becoming more & more aggressive and who knows what is next?!
[Android Q&A, Help & Troubleshooting] mmortal03:
@rocker00 , what did it take to remove the spoofing? I came across the following, but I don't know how relevant it is to all these different ROMs with this problem: https://github.com/Sushrut1101-ROMs/PixelPropsUtils/blob/crDroid/PixelPropsUtils.java