lineageos4microg / android_vendor_partner_gms Goto Github PK

Currently included GmsCore is version 0.2.27.223616 (around one year old).

https://github.com/microg/GmsCore/releases

I'd like to use the new location stack (and plenty of bug fixes).
So updating GmsCore requires other changes (e.g. removing the location backend apks).

Wonder if it's the cause of fast battery draining
[lineage-20.0-20230310-microG-merlinx]

Hey team,

I recently updated from LineageOS for microG 19.1 to 20. Doing this caused F-Droid to lose all apps and ability to update.

After debugging with the rest of the F-Droid team, we figured out that this is a bug introduced in F-Droid 1.16, where a major Android version upgrade will put the database into an incorrect state: https://gitlab.com/fdroid/fdroidclient/-/merge_requests/1210. We tagged a new release (1.16.3) which fixes this bug.

While we don't know if your ROM updates F-Droid installations on OS upgrades, but if it does, it would be great if you could include 1.16.3 as soon as it is available (I will notify you when that is, we're currently busy with the build and signing process). We believe that, if 1.16.3 is installed before the first time F-Droid is launched after a major Android version update it should no longer put its database into an incorrect state, therefore allowing users to upgrade from LineageOS 19.1 to 20 without breaking F-Droid.

Kind regards,
Sylvia van Os
(F-Droid Contributor)

Unfortunately UnifiedNlp is not working for me on coral (Pixel 4 XL). There is even no UnifiedNlp section in MicroG Self-Check — last position on that list is "Battery optimizations ignored" under "System". What can I provide you with to help diagnose this issue?

Latest release of microG (0.2.25.223616) crash when adding an account with SafetyNet disabled, this is already fixed in the latest nightly.

Hi, do you plan to add microg patch mentioned in https://calyxos.org/news/2022/03/03/microg-android-12/ ?

thank you

Building 19.0 including GmsCore returns an error:
FAILED: out/target/common/obj/APPS/GmsCore_intermediates/enforce_uses_libraries.status /bin/bash -c "(rm -f out/target/common/obj/APPS/GmsCore_intermediates/enforce_uses_libraries.status ) && (build/soong/scripts/manifest_check.py --enforce-uses-libraries --enforce-uses-libraries-status out/target/common/obj/APPS/GmsCore_intermediates/enforce_uses_libraries.status --aapt out/host/linux-x86/bin/aapt prebuilts/prebuiltapks/GmsCore/com.google.android.gms-212658044.apk )" error: mismatch in the <uses-library> tags between the build system and the manifest: - required libraries in build system: [] vs. in the manifest: [com.android.location.provider] - optional libraries in build system: [] vs. in the manifest: [] - tags in the manifest (prebuilts/prebuiltapks/GmsCore/com.google.android.gms-212658044.apk): uses-library:'com.android.location.provider' note: the following options are available: - to temporarily disable the check on command line, rebuild with RELAX_USES_LIBRARY_CHECK=true (this will set compiler filter "verify" and disable AOT-compilation in dexpreopt) - to temporarily disable the check for the whole product, set PRODUCT_BROKEN_VERIFY_USES_LIBRARIES := true in the product makefiles - to fix the check, make build system properties coherent with the manifest - see build/make/Changes.md for details

This is due to enforcing consistency between build-system and manifest in Android 12 (https://source.android.com/devices/tech/dalvik/art-class-loader-context)

Hello,
just a quick reminder, microG was updated: https://microg.org/fdroid/repo/com.google.android.gms-214816046.apk
Can you please update the included apk.
Thanks!

Hello!

So I have a strange issue - I'm trying to integrate your microG implementation as a build option for VoltageOS because folks have asked for it.

It builds just fine and integrates nicely but the problem is the GmsCore APK specifically ends up being left unsigned:

05-18 21:46:36.843  2433  4784 E PackageExtInit: unable to parse SigningDetails for com.google.android.gms; code -103; msg Failed to collect certificates from /system/product/priv-app/GmsCore/GmsCore.apk
05-18 21:46:36.843  2433  4784 E PackageExtInit: java.lang.SecurityException: META-INF/CERT.SF indicates /system/product/priv-app/GmsCore/GmsCore.apk is signed using APK Signature Scheme v2, but no such signature was found. Signature stripped?
05-18 21:46:36.843  2433  4784 E ParseTypeImpl: Cannot set to success after set to error, was Failed to collect certificates from /system/product/priv-app/GmsCore/GmsCore.apk
05-18 21:46:36.843  2433  4784 E ParseTypeImpl: java.lang.SecurityException: META-INF/CERT.SF indicates /system/product/priv-app/GmsCore/GmsCore.apk is signed using APK Signature Scheme v2, but no such signature was found. Signature stripped?
05-18 21:46:36.846  2433  2433 W PackageManager: Failed to parse /system/product/priv-app/GmsCore: Failed to collect certificates from /system/product/priv-app/GmsCore/GmsCore.apk

This then results in that APK being completely ignored. It's very strange because I see nobody else reporting this issue and Voltage is based on LineageOS so I'm a bit mystified.

I believe what's happening is that the APK is getting its libs unpacked but then being repacked and not signed. I have attempted to remedy this by adding the following to each APK definition:

LOCAL_SDK_VERSION := current

This should, in theory, skip modifying the APK but then we fail to actually build the ROM at all because then I get errors like this:

out/target/product/tdgsi_arm64_ab/obj/APPS/IchnaeaNlpBackend_intermediates/package.apk: error: Contains compressed JNI libraries and/or dex files 

So it seems like I'm in a catch 22 with this - any guidance would be greatly appreciated. :)

Hello

I've made a little web app with a frontend where you can subscribe to web push notifications, subscription is then sent to a nodejs server that send notifications back to the client device.

It's working great using Chrome or Brave on regular Samsung OS with Google Apps and Google Services Framework.

My phone is using the last version of microG Lineage OS 18.1 on a LG G5 (h850).
I can receive push notifications from my nodejs server using Firefox.

But using any Chromium based browser, when i subscribe on the frontend the notification sent by my nodejs server is never displayed.

if i go to microG settings > Cloud Messaging > Brave i can see that last message is received when my nodejs server is sending it.
So it's seems that the connection between my nodejs server and Brave browser is working, but client side PushEvent is never triggered.

To make web push notification work, you have to use the Push Service of the browser, so on Chromium based browsers it use an endpoint like https://fcm.googleapis.com/fcm/send/<random-string>, note sure if this is related to my problem as far as i understand microG purpose is to enable FCM Cloud Messaging on Lineage OS.

Thanks if you can help me ;)

I tried to build lineageos4microg for lineage-19.0 (lineageos4microg/docker-lineage-cicd#243), and it fails with the following output:

FAILED:
build/make/core/artifact_path_requirements.mk:26: warning:  device/google/bramble/lineage_bramble.mk produces files inside build/make/target/product/generic_system.mks artifact path requirement.
Offending entries:
system/app/FDroid/FDroid.apk
system/app/GsfProxy/GsfProxy.apk
system/app/IchnaeaNlpBackend/IchnaeaNlpBackend.apk
system/app/NominatimGeocoderBackend/NominatimGeocoderBackend.apk
system/etc/org.fdroid.fdroid/additional_repos.xml
system/etc/permissions/privapp-permissions-com.android.vending.xml
system/etc/permissions/privapp-permissions-com.aurora.services.xml
system/etc/permissions/privapp-permissions-com.google.android.gms.xml
system/etc/permissions/privapp-permissions-org.fdroid.fdroid.privileged.xml
system/etc/sysconfig/sysconfig-com.google.android.gms.xml
system/priv-app/FDroidPrivilegedExtension/FDroidPrivilegedExtension.apk
system/priv-app/FakeStore/FakeStore.apk
system/priv-app/GmsCore/GmsCore.apk
In file included from build/make/core/main.mk:1346:
build/make/core/artifact_path_requirements.mk:26: error: Build failed.
08:08:48 ckati failed with: exit status 1

This leads me to believe PRODUCT_ENFORCE_ARTIFACT_PATH_REQUIREMENTS was switched on in LineageOS for 19.0 and this repository conflicts with that. I'm not exactly sure if a Product Partition is created when building LineageOS.

One proposed solution I found was to set LOCAL_PRODUCT_MODULE := true in the module definitions. I tried it for another personal repository and it seems like the error line regarding this Apk goes away.

Unsure about the implications of potentially moving our apps from system to product partitions and if that actually would apply.

So far, this is just me noting down what I found out. Any further hints are appreciated.

Building 18.1 using the master branch of this repo fails with the following error

FAILED: ninja: 'out/target/common/obj/JAVA_LIBRARIES/androidx.window.extensions_intermediates/javalib.jar', needed by 'out/target/product/avicii/obj/APPS/GmsCore_intermediates/dexpreopt.zip', missing and no known rule to make it I'm using the same prebuilts for both build attempts: <project name="lineageos4microg/android_vendor_partner_gms" path="vendor/partner_gms" remote="github" revision="master" />

Originally posted by @petefoth in #13 (comment)

Two lines were A line was added to GmsCore/Android.mk in this commit and this commit to fix the issue with building 19.1

LOCAL_USES_LIBRARIES := com.android.location.provider
LOCAL_OPTIONAL_USES_LIBRARIES := androidx.window.extensions androidx.window.sidecar

If I remove these two lines this line, then my 18.1 builds succeed.

Is it possible make the inclusion of those lines conditional on the Lineage OS version or Android version?

Could it be the case, that due to the way the signature-spoofing works, when the "fake" com.android.vending (Fake Store) with the real one (plain Play Store), it is recognized as "unverified"?

See:
FriendlyNeighborhoodShane/MinMicroG#68
nift4/microg_installer_revived#141

LineageOS now support restricted signature spoofing for GmsCore only, so the steps outlined in Note 2 are no longer required

So I figured out my problem. I have never used docker, therefore I never read the docker readme. (My main system can't even run docker, I have been compiling in a Ubuntu VM in VMware with snapshots) It mentions needing a signature spoofing patch, something missing from the readme here.

At the bottom of this I found the mention of the patches and applied the one for Android Q.
https://github.com/microg/GmsCore/wiki/Signature-Spoofing
At first building failed because there were two .old files the compiler complained about, but deleting them allowed me to compile the build, and it isn't bootlooping or being weird in my limited testing so far. This is with the XZ1C too, will try to main it again and see if I encounter any weirdness.

Not sure if this is also required after applying the patch, but I ran export SIGNATURE_SPOOFING=restricted as well before compiling.