search

microg / GmsCore

Free implementation of Play Services
https://microg.org
Apache License 2.0
8.51k stars 1.71k forks source link

app "microg services core" not visible in f-droid #424

Open fvoncken opened 7 years ago

fvoncken commented 7 years ago

Using the QR code in https://microg.org/download.html resulted in F-Droid the following apps "FakeStore", "microG DroidGuard Helper" and "microG Services Framework Proxy". However, the app "microG Services Core" does not occur in F-Droid.

Because of the location issue of my device with LineageOS I'd like to use the location service "UnifiedNlp (no GAPPS)" within LineageOS following the instructions on XDA. However, microG Services Core is an essential part of the instructions. And I cannot proceed without that missing app in F-Droid. What can I do? Can I flash Services Core separately besides the QR-method?

I have Nexus 5 with LineageOS 14.1 and TWRP.

mar-v-in commented 7 years ago
  1. Sometimes F-Droid shows microG Services Core under "UnifiedNlp (no GAPPS)". You can see if this is the case by looking at the version numbers: UnifiedNlp is at version 1.6.8 and Services Core is at version 0.2.4
  2. On original LineageOS 14.1 the location provider (UnifiedNlp standalone or included with Services Core) must be on /system partition. There are root tools to move the apk if you feel uncomfortable on doing it yourself. You also need to ensure the package persists across updates.
  3. if you are only interested in the UnifiedNlp functionality, you don't need the other parts of microG and only the "UnifiedNlp (no GAPPS)" standalone package (assuming you don't have GAPPS installed. However this will not allow usage of official Google apps.
Ronkn commented 6 years ago

I have a similar question my yalp store app wants to update "microG services core" but it fails to install. I assume it's bc fdroid handles this?

I'm using the MicroG version of lineageos. Does this microG core services just get updated with their release of the microg-lineageos update?

rakshazi commented 5 years ago

Hello from 2019. Could you split MicroG (which uses com.google.android.gms) with UnifiedNlp (which uses the same app code) and publish them as separate apps, please? It's very hard to find out how to use UnifiedNlp without MicroG. To be honest, it took about 2-3 hours of parsing the web, to find that comment on separate non-microg community with link to this issue.

Thank you!

ArchangeGabriel commented 5 years ago

@rakshazi Both apps are already present in F-Droid. They are different builds depending on whether you want to have it alongside Google Apps or not, and that also defines the appcode. Using the same as μG Services Core is necessary in one of the cases.

RalfJung commented 4 years ago

The recommendation by the F-Droid developers for this problem is to put "UnifiedNlp" and "microG services core" into distinct repositories to avoid the name confusing. Would that be possible?

mar-v-in commented 4 years ago

@RalfJung that means removing UnifiedNlp from F-Droid main repository and create a new repository for unifiednlp only. Yes that would work, but doesn't sound like a good solution either.

ale5000-git commented 4 years ago

I think a better solution would be exclude F-Droid and Yalp Store from spoofing in the signature spoofing patch.

mar-v-in commented 4 years ago

@ale5000-git This doesn't solve the issue with F-Droid. The UnifiedNlp package already has a different signature from microG Services Core no matter if signature spoofing happens or not.

The problem is that F-Droid can't handle two packages with same package name but different signature as two different apps, they are handled as the same app. IIRC, F-Droid won't suggest updates if the signature doesn't match.

ale5000-git commented 4 years ago

I may be wrong but if I remember correctly F-Droid added support for signing a single app with 2 different signatures, so it should be able to pick the update with the matching signature if signature spoofing isn't enabled.

So while both apps will still appears as one, it should be able to pick the correct file.

LuccoJ commented 3 years ago

@mar-v-in this is a continuing problem especially for users of LineageOS for microG, who often assume they always have to upgrade the whole ROM because they don't see the microG update show up in F-Droid. I assume it's a minority that ever gets to ask about it and receives an answer on the lines of "temporarily disable the main F-Droid repository" or "pretend to be updating UnifiedNlp (no GAPPS)".

Since "UnifiedNlp (no GAPPS)" in the main repo has long been an obsolete version, could you maybe ask the F-Droid team to remove (archive) it so that this stops being an issue for the majority of users? I once asked if this was possible, but apparently they weren't inclined to do it without the author specifically asking.

bananer commented 2 years ago

For those of you still here in 2022, I've written up all I know in this issue: https://github.com/lineageos4microg/docker-lineage-cicd/issues/266