yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] rocker00:
@mmortal03 Yes this is the main file but I've found some other related stuff, it's different from ROM to ROM, anyway, here are my steps:

* decompiled the framework.jar on the laptop

* used notepad++ and searched within the framework about everything regarding PixelPropsUtil

* copied the original framework on the phone and used MT Manger app to decompile and modify the framework and removed that file and some other lines I've found on other xmls (the apktool on the laptop gives a corrupted framework, at least for me)

* copied the modified framework and made a TWRP patch

* wiped everything and flashed the ROM followed by the modified framework (without rebooting, and this is very important) and that's it.

Surely, This is only for the advanced users, the real solution should comes by the devs.
[Android Q&A, Help & Troubleshooting] amn1987:
In my Redmi Note 3 running a nearly 2 years old build of Havoc (A10) I am observing similar signs. It doesn't seem to have the hack for enabling unlimited photos backup. I had disabled GMS Intent earlier but it seems to have been re-enabled somehow. Maybe after an update of Play Services?

Edit: It affected Redmi 3s as well running a 9+ months old build of Fork LOS 18.1. The issue wasn't temporarily fixed by freezing Play Services and the logcat spam wasn't there. After disabling Shamiko module the issue hasn't recurred so far. Maybe it coincided with the latest 0.51 update of the module as it wasn't present earlier from what I can tell.
[Android Q&A, Help & Troubleshooting] Tomo123:
Poco X3 Pro, running Arrow OS 11. After having battery drain issues multiple times, I solved it the usual way.

By adding OTA update links to blacklist in AdAway:

ota.googlezip.net

ota-cache.googlezip.net

ota-cache1.googlezip.net

ota-cache2.googlezip.net

Along with that, because Google Play Services still had their background fit trying to connect to the update servers, I disabled the following service:

com.google.android.gms/com.google.android.gms.chimera.GmsIntentOperationService

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...
[Android Q&A, Help & Troubleshooting] mmortal03:
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.
[Android Q&A, Help & Troubleshooting] amn1987:
TG, WA seemed to work fine. But many/most Google apps were affected.
[Android Q&A, Help & Troubleshooting] Tomo123:
Just tested, Whatsapp push notifications work without issues. Since I "have to have" Whatsapp in this day and age, that was my only concern... goody gumdrops!

For mail, I don't care, since installed Aqua Mail is set to automatically check mails every hour, Google Maps work, Youtube is replaced with Revanced/MicroG combo.

Found this:

Google Cloud Messaging, deprecated April 10 2018, has been deactivated and removed from Google's APIs. For equivalent functionality, use Firebase Cloud Messaging (FCM), which inherits the reliable and scalable GCM infrastructure, plus many new features.

So why, for hell sake, does update depend on GCM crap, when it seems it's not needed for anything else? Disabling it has no bad sides, at least in my usecase. Improved my battery life massively, since after disabling the service, alarms and partial wakelocks from Google Play Services are practically nonexistent.

Terefore, CPU is being much quieter and does not ramp up like an idiot in heat all the time. Faster doze time, less traffic on Wifi... a pure win.

If issues happen, I will update my post.

P.S. Must notify crDroid/Arrow dev for Poco X3 Pro about that fix, so he can implement the same in his ROM.
[Android Q&A, Help & Troubleshooting] amn1987:
I am using crDroid 8.6 in Poco F1 for a few weeks now and despite the hack still being present I haven't come across the issue so far. Ditto for Awaken ROM.
[Android Q&A, Help & Troubleshooting] Tomo123:
Awaken?

Oh, the ROM. Got it.
[Android Q&A, Help & Troubleshooting] nikapos:
thank you guys for this thread, i was driven crazy by the massive battery usage and overheating of the device.

i don t care what gets broken by disabling this service, i was afraid the phone was broken, the battery or the cooling system, and i was afraid it would brick soon, being the poco x3 pro.

i m still on crDroid 7.
[Android Q&A, Help & Troubleshooting] amn1987:
It looks like Shamiko and/or USNF is to blame for misbehaving Google and Android processes causing battery life to significantly worsen. Right now manually killing the processes in FKM. Every few minutes any of com.android.vending or com.android.gm, com.android.launcher or com.android.deskclock etc. start to use a lot of the CPU and the little cores max out at 100% until I manually kill them. In 3 different devices ranging from A10 to A12 (custom ROMs ). Official Magisk 25.2. Today clean flashed crDroid 8.7 in my Poco F1 and the issue cropped up after flashing the modules. Anyone else noticed the same? Freezing Play Services has no effect. Logcat spam is different and seems to reference some network issue.

Edit: USNF continues to block logging into Google accounts. Disabling USNF solves it everytime.

Edit2: Turned out to be it was a banking app to blame! ICICI Pockets. Could be because of hiding root. It's strange that it could spoof the names of various Android and Google processes.
[Android Q&A, Help & Troubleshooting] mmortal03:
How were you monitoring it? Was it just continuing to show up in the logcat output as the SystemUpdate messages, *after* you made your AdAway additions? I know you're on ArrowOS 11, Poco X3 Pro, but I'm interested because on the latest version of CrDroid (7.20), Moto G5 Plus (potter), the dev built the hosts file changes into the ROM to workaround the issue, and since then I haven't seen the constant barrage of SystemUpdate messages following this. I haven't had to disable GmsIntentOperationService.

But I also haven't yet done extensive testing with a *logged in* Goggle account, though. I'm concerned that I might run into issues with that, though I haven't heard anyone make this complaint yet. Your experience just makes me question whether there may have been other applicable fixes that may have gone into potter CrDroid 7.20 on top of the hosts file additions that aren't clear to us yet. I guess it's also possible that AdAway somehow isn't as thorough at blocking activity as modifying the hosts file directly?
[Android Q&A, Help & Troubleshooting] mmortal03:
You weren't seeing this issue prior to CrDroid 8.7? It sounds like it could be a different bug, technically separate from the Play Services/Pixel spoofing issue that this thread has been about?
[Android Q&A, Help & Troubleshooting] amn1987:
Not for the 2-3 of weeks I was on crDroid 8.6. Dirty flashed 8.7 and the issue cropped up. Yes it's a different issue. But Shamiko has had one or two updates since then. Due to issue with encryption internal storage got formatted. But even after a clean flash the problem didn't go away. After switching to Ad Guard DNS I had stopped using AdAway but no change even after disabling the former. One member in the crDroid group had mentioned banking or financial apps continue to work with Magisk v23 and he didn't come across this issue so far. That or Magisk Delta. LSPosed/Shamiko devs are reportedly quick to take offense and mute/ban so...

In the Zygisk thread Magisk Delta dev had mentioned Shamiko was having issues hiding Zygisk if any other Magisk module was also active. Will check after disabling other modules but it's not a viable solution as I simply must have Custom Fonts Installer module installed.
[Android Q&A, Help & Troubleshooting] amn1987:
It wasn't Shamiko or USNF. It was a banking app (ICICI Pockets) in my case! Probably the issue arose because of hiding root from it. I kept Processes tab in FKM and Matlog open in Split screen mode. Whenever a misbehaving process like com.android.gm or com.android.media etc was encountered upon killing it in the logcat the package name of Pockets was instead displayed with the same PID in both cases. Glad to finally have found the root cause. I now just stop the app after using it. Simply freezing it will trigger re-verification.

Edit: It's mind boggling that without root access an app can spoof various Android/Google processes. In the past whenever the app detected root it used to ask for Superuser rights which I always denied.
[Android Q&A, Help & Troubleshooting] castaway1:
so no fix yet? why some people have this problem and some not? im without gmail and keep notifications because of this :(
[Android Q&A, Help & Troubleshooting] mmortal03:
It was fixed on the latest CrDroid build for potter, but I don't know about any of the other affected ROMs.
[Android Q&A, Help & Troubleshooting] Huebabbel:
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.
[Android Q&A, Help & Troubleshooting] PilotSoldier:
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
[Android Q&A, Help & Troubleshooting] amn1987:
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.
[Android Q&A, Help & Troubleshooting] rocker00:
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.
[Android Q&A, Help & Troubleshooting] mmortal03:
But, unfortunately, no Moto G5 Plus build from them with this fix.
[Android Q&A, Help & Troubleshooting] JonasVFC:
what are the side effects?
[Android Q&A, Help & Troubleshooting] amn1987:
No notifications mostly. Gmail seems to work fine.
[Android Q&A, Help & Troubleshooting] JonasVFC:
do you happen to know if ms teams or slack are affected?
[Android Q&A, Help & Troubleshooting] amn1987:
I have not used them but third-party apps seem to be unaffected. Only Google apps are definitely impacted.
[Android Q&A, Help & Troubleshooting] JonasVFC:
Let's hope at least calendar sync doesn't break. I'll give it a go.
[Android Q&A, Help & Troubleshooting] amn1987:
Notifications from Calendar stop almost immediately after applying the fix unfortunately.
[Android Q&A, Help & Troubleshooting] amn1987:
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.
[Android Q&A, Help & Troubleshooting] mmortal03:
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.
[Android Q&A, Help & Troubleshooting] rocker00:
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.​
[Android Q&A, Help & Troubleshooting] flipeicl:
Thank you, it have worked for me.
[Android Q&A, Help & Troubleshooting] mmortal03:
@flipeicl , just keep in mind that disabling it breaks sync in various ways. It's a workaround, not a true fix.
[Android Q&A, Help & Troubleshooting] flipeicl:
I know that, but the battery drain...!
[Android Q&A, Help & Troubleshooting] R4Ck:
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.
[Android Q&A, Help & Troubleshooting] X3User:
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!
[Android Q&A, Help & Troubleshooting] amn1987:
Yes. Manufacturers for obvious reasons can never include Pixel spoof in their ROMs.
[Android Q&A, Help & Troubleshooting] X3User:
Thank you so much! I specifically used the one without the pixel spoof because there is pixel spoof on other miui based rom. I guess I have to stick with this one unless spoofing is completely removed on aosp roms.

Probably my Last Update LOL: It's been 5 months since I flashed miui based rom without the spoofing and it's still working fine. Maybe I'll switch to lineage os if a14 comes out as it doesn't have any spoofing.
[Android Q&A, Help & Troubleshooting] Elinx:
Thank you for this workaround.

I was very disappointed about the 5h max. SOT on my hot XRN10P - crDroid v7.16

I couldn't imagine that it was the crDroid, but already considering to install another rom.

After I found this relative easy fix I get at least 9h SOT and think that installing another rom still wil have this same problem, because I never thought about the Pixel spoofing.

I use K9-mail and AOSP calendar, so less problems with missing notifications.

Contacts, Calendar and Photo's sync does work, which is the most important part for me.

So next target is to find a similar rom without this spoofing or final fix. (maybe install an older version of Gapps?)

Edit: It runs now for several weeks and don't miss anything (besides the high battery drain ;))
[Android Q&A, Help & Troubleshooting] amn1987:
This is unrelated to the Pixel Spoof issue but in an old device (Redmi Note 3) running Q ROMs (Havoc 3.12 in particular and without the Pixel Spoof hack) everytime data is enabled Google services (com.google.android.gms.persistent ) peg the CPU0 at 100% for 40 minutes or so at a time. The "system_server" also uses lot of the CPU0 when this happens. Strangely while the other CPU cores are pretty much at idle the device still becomes very laggy for some minutes which is quite frustrating. Other users have reported the same as well but so far no solution. This issue isn't present in A11 ROMs but battery life is almost 50% worse in R vs Q so I am forced to put up with this issue. Plus A11 ROMs might include the Pixel Spoof which is much, much worse. Development of the device seems to have hit a dead end with the last update of A11 ROMs over a year ago. Only solution is to use microG but with BitGApps microG at least I just couldn't get any of the paid apps to work.
[Android Q&A, Help & Troubleshooting] gamersfan:
The solution with a root.

Solution №1

Add file-script GmsOff.sh at data/adb/service.d (its magisk folder to autostart scripts)

Write in file:

sleep 130

su -c pm disable com.google.android.gms/.chimera.GmsIntentOperationService

In the permissions of the script-file, put 3 checkboxes for execution.

Install app Terminal Shortcut Pro. you can create link there, and you must use it to turn service ON before you wanna restart or shutdown phone.

Write at link:

su -c pm enable com.google.android.gms/.chimera.GmsIntentOperationService

You also can just use terminal, if you dont like Shortcut program.

If you not turn service ON again BEFORE you reboot, there will be problems with receiving notifications AFTER your phone start.

Solution №2

Install Magisk Universal GMS Doze module (I use 1.8.8)

Create file 123.sh at data/adb/service.d

Write there:

sleep 130

cd /data/data ; su -c "find . -type f -name '*gms*' -delete"

In the permissions of the script-file, put 3 checkboxes for execution.

Also there is an option to create a script that will launch the service immediately after the system start, but before Google services fully load, and then disable it after a while.

It turned out like this for me, but your system startup time may be different, you need to select "sleep" values according to the situation.

sleep 20

su -c pm enable com.google.android.gms/.chimera.GmsIntentOperationService

sleep 80

su -c pm disable com.google.android.gms/.chimera.GmsIntentOperationService

For the future - install only ROMs without "Pixel Spoofing for unlimited Photos storage"

Check my Reddit Post about this problem.

There will be some enhancement to solutions.
[Android Q&A, Help & Troubleshooting] RRosh:
Thank you!

I have followed Solution №2 and it helped a Lot.

Do you know if I can uninstall Magisk afterwards though?
[Android Q&A, Help & Troubleshooting] gamersfan:
No, you can't :c
[Android Q&A, Help & Troubleshooting] HansKlopek:
January Pixel Experience Plus on a Redmi Note 10 Pro suffering from this badly. Battery just disappearing even after restarts, with Google play services way out on top of the battery drain leaderboard.

com.google.android.gms process constantly using CPU. No apps updating, sync not turned on. Device not plugged in.

I haven't applied any fixes yet but it's disappointing that I need to make this consideration!
[Android Q&A, Help & Troubleshooting] X3User:
Well I switched to arrowos since it doesn't have pixel spoof and memeui lag is killing me and so far so good. I'll update in few months

Ohh frick. On step-up it was rexognized as poco x3 nfc but now its pixel 2. I'm expecting that since pixel 2 doesn't have ota updates anymore it won't be a bug plzzz
[Android Q&A, Help & Troubleshooting] amn1987:
Shouldn't be an issue if new builds with the latest monthly security patches are released regularly and you update diligently. It's when the security patch is more than 2-3 months old that Play Services goes rogue.
[Android Q&A, Help & Troubleshooting] Nimda672:
got any solve?
[Android Q&A, Help & Troubleshooting] X3User:
So yeahhh. I came back to memeui 14 because I couldn't stomach the battery drain + heating issues, it didn't even lasted a week...

Tried termux comand + gms dose, didn't work. I tried to reflash with vanilla and manually flashing gapps but still no luck. I guess aosp isn't for me
[Android Q&A, Help & Troubleshooting] amn1987:
You can switch to LOS if it's available for your device. At least official builds shouldn't include the Pixel Spoof. I don't know why the terminal command didn't work in your case as no one else reported the same. Root is non-negotiable for the command to work.
[Android Q&A, Help & Troubleshooting] X3User:
Yeah thanks. Nightly build but it's still fluid af. Couldn't last for another day in memeui. Thank you so much, I finally have a daily driver rom!
[Android Q&A, Help & Troubleshooting] X3User:
So yeahhhhhh. Even if it doesn't have pixel spoof the error occurs and this is on the latest march security patch. Can I ask if you play games and you can log onto that with micro g?
[Android Q&A, Help & Troubleshooting] amn1987:
Check here if the issue is similar to what I had experienced in one of my devices.

I recently switched to A11 in the same device and the issue persisted only with the difference that one of the big cores was affected. Initially "iorap.cmd.compiler" also kept the CPU busy for quite a while but it seems to have gone away for now.

Edit: About 3 years ago I had used microG (Nanodroid) and with the modded Play Store app I could validate the license in case of all my paid apps but some months ago I had tried BitGApps microG and for some reason none of the paid apps would work. I don't play games in mobile...
[Android Q&A, Help & Troubleshooting] livingbeing:
Hi, is there any update about this? does changing fingerprint and remove spoofing help to prevent this gms drain?
[Android Q&A, Help & Troubleshooting] amn1987:
Restoring the original fingerprint had no bearing in this issue last time I tried it.
[Android Q&A, Help & Troubleshooting] st4ik:
With me Solution №2 works, but unfortunately after a few hours the process com.google.android.gms again uses a lot of cpu and drains the battery. Anyone also has this problem ? Rom CrDroid 8.13.
[Android Q&A, Help & Troubleshooting] daveryanoneza:
Using crdroid 7.13 (based on A11).

Been experiencing this with every rom I have installed but found a way to stop it from coming in and out of background processes. The solution may not be to everyone's liking though.

Since it's said "persistent", I thought maybe because it tries to revive google/play processes/services which I disabled or turned off.

So what I did was...

-Enabled every google services and allowed all permission from the Google app and Google Play Services.

-Turned on Usage and Diagnostics

-Turned on location and wifi and bluetooth scanning, then allowed location permission for all Google apps

-Turned on backup from photos and google one

-Set Google as defaut assistant and autofill service

In short, I basically allowed all google services.

The CPU and battery drain issue stopped for me. I mean, really. And yes, that's what Google wants from every user. It felt like I had no choice but to give up my privacy just to use their services.
[Android Q&A, Help & Troubleshooting] kamilchno:
A13 worked too
[Android Q&A, Help & Troubleshooting] laviniu_c:
this should still not work. the underlying problem is google tries to do the google play system update (the small update that does just the services/sytem patches updates) and it can't. not on anything custom since that's the nr1 thing devs turn off as they need to manually merge/check the services/patches into the rom.

please use it for a couple months, for me at least the problem seemed to popup after weeks of normal usage. the easiest is to just check the matlog from time to time and look for the continuous intent logs. but a sudden decrease in bat life and increase in temps is a good indicator too.