missing checked signature boxes since 0.36

[RobertoWa]

since latest microg [0.36] i have unchecked boxes signatur system, gmscore and phonesky. was working well till [0.35]. after update it is missing.

as it seems, everything is still working as expected.

System
Android Version: 10, stock rom, patched by nanodroid

[Spp595]

I had exactly the same problem on crdroid, but after installing fakegapps it was solved

[Rheydskey]

I got the same problem.
Could it be b9b7278 the cause ? #2680 (comment)

This means that all signature spoofing patches need to be updated to address the change of API usage by - in addition to the PackageInfo.signatures also spoofing the PackageInfo.signingInfo. There's unfortunately nothing we can do in microG itself.

[mar-v-in]

microG 0.3.6 got updated to check for the signature spoofing to be compatible with the latest version of Play Services. If you're using an old version of signature spoofing, it will now say that signature spoofing does not work correctly in Self-Check. There is no immediate issue through this: If you have apps that use microG and you don't update them, they will continue to work. However you should be aware that any updates to apps might cause them to no longer consider microG a valid implementation of Play Services and will show errors and/or ask you to update Play Services.

[BurhanBudak]

microG 0.3.6 got updated to check for the signature spoofing to be compatible with the latest version of Play Services. If you're using an old version of signature spoofing, it will now say that signature spoofing does not work correctly in Self-Check. There is no immediate issue through this: If you have apps that use microG and you don't update them, they will continue to work. However you should be aware that any updates to apps might cause them to no longer consider microG a valid implementation of Play Services and will show errors and/or ask you to update Play Services.

Still, thanks for adding the support for the API, but what now? There are a lot of factors we need to think about, like, should I update my custom room to December build? Should I use Play Integrity Fix or Play Integrity Fork, etc. Some apps show good response to the API. Some still abuse the API for no reason, like RCS and free coupon McDonalds.

To be frank, this is just a catch-up for us, but now MicroG is more superior than Graphene-Sandbox.

[HanabishiRecca]

should I update my custom room to December build?

LineageOS already updated signature spoofing patches and it's already out in nightly build.
LOS derivatives like GrapheneOS would follow in some amount time, I guess.

[mar-v-in]

@BurhanBudak I guess your comment is related to Play Integrity which is not relevant in this thread at all. The change in signature spoofing is for Play Services not Play Integrity, which after many years decided to change to a new OS API to check signatures that some signature spoofing patches did not consider. You can read about the details and how many ROMs did the upgrade in #2680.

You should always update to the latest operating system version available, as they often include critical security updates.

There is really no competition between microG and GrapheneOS GmsCompat. They are different approaches with different goals.

[Hruehle]

Sorry how is the case with LOS microG? I use it on my Fairphone3 and after the update via Fdroid of microG services I have the same problem.

[mar-v-in]

@Hruehle You don't have to do anything right now. Make sure you install the next version of LOS4microG once it becomes available (probably mid January for Fairphone 3). After that update, the checks will turn positive automatically. Until then it's best to not update any apps that make use of microG as the update of these apps might render them unusable.

[BurhanBudak]

should I update my custom room to December build?

LineageOS already updated signature spoofing patches and it's already out in nightly build. LOS derivatives like GrapheneOS would follow in some amount time, I guess.

Not that fast but i can wait, I thought there would be fuse as of PI API was added. But it wouldn't matter as we will be forced to do some hacking to pass verdict. The most important point is to stay at a specific security patch before the hardened PI is added.

[ale5000-git]

@mar-v-in
In the self check can we say Yes/No/Partial instead of just Yes/No for signature spoofing?
It will reduce the confusion.

[Vavun]

In the self check can we say Yes/No/Partial instead of just Yes/No for signature spoofing?

Or something like
Signature spoofing (0/2 methods) 🔲
Signature spoofing (1/2 methods) 🔲
Signature spoofing (2/2 methods) ✅

For non-huawei builds

[ale5000-git]

The summary of the patch situation is explained here: #2680 (comment)

[mar-v-in]

A lot about self-check is confusing at this point. It should probably be replaced entirely.

[ale5000-git]

I think it is always good to have a global overall of things that need to be done to have everything working but maybe a lot of the text can be changed to be more clear.

[RobertoWa]

I'll summarize for my understanding: in the foreseeable future, old signature spoofing patches will no longer work and microg will focus on what Google has changed - hence the unchecked boxes. In my case with Android 10 patched via nanodroid, I will have to switch to a different patch or another OS.

[ale5000-git]

Plain LineageOS already have signature spoofing built-in; and most ROM nowadays already include it.
There is also the FakeGApps Xposed module.

[kolAflash]

I guess for "LineageOS for microG" users new ROM builds are needed then, as described here:
lineageos4microg/docker-lineage-cicd#716

At least the current build for the FP3 (2024-12-11) seems to still use the old signature spoofing. It comes with "microG Services" 0.2.27.223616 (quite outdated!?) and it says signature spoofing is working fine. But the preinstalled F-Droid offers an update to "microG Services" 0.3.6 after which the signature spoofing is shown as non working. So for the moment I'll only apply the 0.3.5 microG updates (Services and Companion) from F-Droid, because they are still working fine.

[HanabishiRecca]

"LineageOS for microG"

This thing is kinda obsolete for the past year.
Just use regular LineageOS and install microG apks as regular apps. It just works.

[kolAflash]

"LineageOS for microG"

This thing is kinda obsolete for the past year. Just use regular LineageOS and install microG apks as regular apps. It just works.

Interesting! The microG wiki says nothing about spoofing support in the official LineageOS.
https://github.com/microg/GmsCore/wiki/Signature-Spoofing

---

Update:

Added LineageOS spoofing support is mentioned here (2024-02-25):
https://www.reddit.com/r/LineageOS/comments/1b11zex/los_has_added_internal_microg_support/
https://review.lineageos.org/c/LineageOS/android_frameworks_base/+/383574
https://review.lineageos.org/q/topic:microg-eval

So I guess the microG/GmsCore/wiki and also the "LineageOS for microG" website should be updated.
https://lineage.microg.org/#faq6
"MicroG requires a patch called "signature spoofing", which allows the microG's apps to spoof themselves as Google Apps. LineageOS' developers refused (multiple times) to include the patch, forcing us to fork their project."

Just tested lineage-21.0-20250102-nightly-FP3-signed.zip on my spare FP3 and signature spoofing is reported as working after installing microG-0.3.6 :-)

[HanabishiRecca]

The microG wiki says nothing about spoofing support in the official LineageOS.

It's simply outdated, the last edit in May 5, 2022.
Official LineageOS introduced the signature spoofing patch in Feb 25, 2024.

[ale5000-git]

I guess for "LineageOS for microG" users new ROM builds are needed then, as described here: lineageos4microg/docker-lineage-cicd#716

At least the current build for the FP3 (2024-12-11) seems to still use the old signature spoofing. It comes with "microG Services" 0.2.27.223616 (quite outdated!?) and it says signature spoofing is working fine. But the preinstalled F-Droid offers an update to "microG Services" 0.3.6 after which the signature spoofing is shown as non working. So for the moment I'll only apply the 0.3.5 microG updates (Services and Companion) from F-Droid, because they are still working fine.

LineageOS for microG can still be used, but you have to use builds after 2024/12/17 to have the new signature spoofing patch.
They have also updated the included microG recently but propably new builds aren't up yet (you can still update it through F-Droid).

[ale5000-git]

It is wrong to think that apps will works or not depending of the tick in microG self-check.

Nothing will change, old apps will still works and new apps will NOT work indipendently if you have 0.3.5 with spoof checked or 0.3.6 with spoof unchecked.

[FarhanMS123]

Hi, if I may add... this means Huawei HarmonyOS 2.0.0 (HUAWEI MatePad) would also not works... right? I download these

• com.google.android.gms-hw
• com.android.vending-hw
• com.google.android.gsf

And also using FakeGApps (following #2680 (comment) ) is still not working.

Who should fix this? Is this issue on HarmonyOS side or one of companions?

[ale5000-git]

Hi, if I may add... this means Huawei HarmonyOS 2.0.0 (HUAWEI MatePad) would also not works... right? I download these

• com.google.android.gms-hw
• com.android.vending-hw
• com.google.android.gsf

And also using FakeGApps (following #2680 (comment) ) is still not working.

Who should fix this? Is this issue on HarmonyOS side or one of companions?

Your comment doesn't make sense, the main difference from normal microG and hw microG is how it get signature spoofing.

If you use FakeGApps you should use the normal microG builds.
Instead if you have a supported Huawei phone you should use the hw microG (withOUT FakeGApps).

Also if you use FakeGApps make sure the version is 6.5 or higher.

[gprn]

Must I understand I need to upgrade the LOS with microG version that run my phone to have signature spoofing working again?
19-20230415-microG-beyondOlte here and never be interested to upgrade to 20 nor 21 cause this old version suits very well my old phone, the recent one have worst battery life e.a.
So am I stuck now?

[HanabishiRecca]

Must I understand I need to upgrade

Read the discussion. You are not forced to upgrade, if all your apps are working fine.
But if you want to use latest versions of Google's apps (and presumably more would follow), you will need to upgrade your signature spoofing patch in one way or another.

[BadTrucker99]

[ildar]

Or something Signature spoofing (0/2 methods) 🔲 Signature spoofing (1/2 methods) 🔲 Signature spoofing (2/2 methods) ✅

No. Better: - Signature spoofing 🔲 - Deprecated signature spoofing method 🔲 And, yes, the BIG FAT WARNING in the release notes would lower the repetitive questions here.

[BadTrucker99]

Broken

[litoj]

My current experience is that after updating from 0.32 on CorvusOS (dead, but supports the old spoofing), I suddenly cannot use an app that I haven't even updated. As if there was a check to use the newer api if available.

Also, something about the microg apk signatures caused me to have to uninstall them all first before I could install the new versions.

Edit: updating the app solved the issue.