hey, thanks! (i knew that much but it’s nice to have it here for future readers )
@paulakreuzer: i now additionally set up the Openbmap backend and both this and the GMS one use offline databases. (edit) And yes, I rebooted after setting them up. (/edit) They obviously work, as I get an instant rough fix in osmand and a bit later the gps localizes me more accurately. also UnifiedNlp says that location backends are set up.
I just realize: I did not do the step with the signature spoofing, since on the µG website they do not mention this (and everything installed fine without it). But could this be the problem afer all? Or was this a step that was formerly required to get µG installed?
edit2: just to be clear. there’s 2 issues here. the first one is that the self-check of UnifiedNlp does not see any location (although satstat and osmand do) and the second one is that i cannot use signal (it complains at the point where you register your phone number).
For microG to impersonate Google Services, it needs signature spoofing. Just use Tingle.
To know more about the Android security model, or why this is needed, check other posts of mine like this one quoted below:
Sadly, Signal and other bunch of free apps depend on crappy proprietary GMS to work.
About your update concerns, Tingle patch (i.e. modifies) the system, so when you update the system to a newer, pristine version of FP Open, you’ll need to patch it again. But so far, you won’t have any other problem with the Fairphone Updater.
Nop, you can update without reverting your modifications, but you lose them.
As of now (current Android state), you can install any app on the ecosystem (this wasn’t true some years ago). On runtime, those apps check if you have Google services, or a reimplementation like microG, and they use them if available. If not, then can occur two things:
The app crashes, when initializing or at some step (Signal’s registration)
The app shows an avoidable message of "lack of GMS” and can’t use some functions (usually push messages, so you don’t get notifications on Slack or Signal)
You can patch the system with Tingle, install microG, register on Signal, and update the system eventually. Then you can use Signal because you are already logged in, but you won’t receive push notifications.
Privacy note: microG still contact the Google Push Messaging servers and Google receive a bunch of metadata of your communications. However, with microG you can control that with the relatively new push messaging settings and by inspecting the code, which is completely open source.
hey @Roboe, thanks for all your replies and info again!
so i will need to keep signature spoofing even after the signal registration :\
I just tried to use tingle and I am getting “ERROR: No device detected! Please connect your device first.” after selecting option 1 (after running “python3 main.py”).
I already tried to change the “connected as”-option of the phone (MTP, PTP, mount sd card) but nothing worked. usb debugging is enabled and i allowed root access for adb.
– does anybody have an idea what could be the problem? (@ale5000?)
i installed microG from fdroid according to the abovementioned guide (5.5).
there it says
Install the latest
*microG Services Core
may be called “µg UnifiedNlp (no GAPPS)” instead, but make sure it displays “microg” and not “F-Droid” as the repository.
*microG Services Framework Proxy
and at least one Unified NLP backend (from F-Droid repository).
I did all of this. Do I still need to install the apk from their website? (i.e. your link)
If yes, then our guide should be updated.