-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Question: upgrading microG in a no longer supported LineageOS for microG #904
Comments
The F-Droid repo is fine. For the other issue you should report it here: https://github.com/lineageos4microg/docker-lineage-cicd |
|
@ale5000-git , thanks, I'll use the F-Droid repo.
Thanks, moved: |
No, it's the same, after all, they are both build by microG |
Thanks for the answers :) |
The things that are in the default F-Droid repository may have a different signature but since microG GmsCore is in a custom repository provided by the author of microG himself then the signature is the same. |
Yea, sorry I forgot that microG maintains its own repo, so it's a non issue. |
Hi, I have LineageOS for microG 14.1
Support ended earlier this year, so my version of microG is v0.2.6.13280
After some reading I would like some confirmation to not risk breaking FCM/GCM registrations for example.
Should I just add the F-Droid repo and upgrade microG Services Core?
https://github.com/microg/android_packages_apps_GmsCore/wiki/Downloads
Will all the components be up to date? Or are there other steps to do when having a longer supported LineageOS for microG installation.
The text was updated successfully, but these errors were encountered: