3 ms·

I'm currently in a similar spot, but am very surprised you did not mention MicroG, which is an open reimplementation of the Google APIs. There seem to be some i

I'm currently in a similar spot, but am very surprised you did not mention MicroG, which is an open reimplementation of the Google APIs. There seem to be some issues with GCM (or, more precisely, the newer replacement - uhm, FCM?), but imho it's worth a try. If you already have a LineageOS-supported device, you can grab a prebuilt LineageOS+MicroG image from the MicroG site. Disclaimer: That's pure theory. I'm still figuring out how to do a custom build of LOS16+MicroG for my device, since it's only on LOS14.

kop316 8y ago
Have you looked here? They do builds of lineageos with mircog already installed https://lineage.microg.org/ https://lineage.microg.org/
- archi42 8y ago
  Thanks :), but as I said: > If you already have a LineageOS-supported device, you can grab a prebuilt LineageOS+MicroG image from the MicroG site. I redacted a lengthy part of my comment since I felt it wouldn't add anything to the discussion; but it went like this: Sadly, my device (HTC 10 aka pme) is officially only on LineageOS 14.x, which is Android 7. Since I am coming from Android 8 stock ROM, I'd like to stay on Android 8 or even get Android 9. There are unofficial LineageOS builds for this (from a guy who just doesn't merge the back to LOS; which I can understand considering the additional effort - on top of all the work is already doing). But of course they lack the necessary patches for MicroG. And the MicroG only pre-builts are based on the official LineageOS build process and thus the official images. So I can only get Android 7 + MicroG with the comfortable "grab image and flash"-method. I gave building a custom MicroG+LOS{15.1,16.0} a shot using the official MicroG docker image (just a single docker run command) and adding the unofficial builds local_manifest.xml, but those two builds failed for me and I didn't bother messing around with that docker c*. Accidentally, I did that the day before this was posted to HN, no changes since then. But I suppose I'll try a docker-less build on my machine once I feel like it. Eventually I can just put MicroG on the unofficial build from xda-devs, since that doesn't contain GApps; but I am not sure how great the experience is when not having the MicroG/F-Droid patches. I will see. EDIT: Regarding signature spoofing, the MicroG github wiki says: > You can also patch your already-install ROM by flashing NanoDroid-patcher, without any computer interaction. It will auto-patch every updated ROM. So maybe that works.
  - kop316 8y ago
    Ahh sorry, I missed that. What may be easiest for you is actually to use Xposed. I think that can allow the signature spoofing needed for MicroG.
    - archi42 8y ago
      I used NanoDroid - worked quite well :) I'd still prefer to build a LOS with MicroG integrated, but it's difficult to get the required information from the folks at xda-dev...

kop316 8y ago

Have you looked here? They do builds of lineageos with mircog already installed https://lineage.microg.org/ https://lineage.microg.org/

archi42 8y ago
Thanks :), but as I said: > If you already have a LineageOS-supported device, you can grab a prebuilt LineageOS+MicroG image from the MicroG site. I redacted a lengthy part of my comment since I felt it wouldn't add anything to the discussion; but it went like this: Sadly, my device (HTC 10 aka pme) is officially only on LineageOS 14.x, which is Android 7. Since I am coming from Android 8 stock ROM, I'd like to stay on Android 8 or even get Android 9. There are unofficial LineageOS builds for this (from a guy who just doesn't merge the back to LOS; which I can understand considering the additional effort - on top of all the work is already doing). But of course they lack the necessary patches for MicroG. And the MicroG only pre-builts are based on the official LineageOS build process and thus the official images. So I can only get Android 7 + MicroG with the comfortable "grab image and flash"-method. I gave building a custom MicroG+LOS{15.1,16.0} a shot using the official MicroG docker image (just a single docker run command) and adding the unofficial builds local_manifest.xml, but those two builds failed for me and I didn't bother messing around with that docker c*. Accidentally, I did that the day before this was posted to HN, no changes since then. But I suppose I'll try a docker-less build on my machine once I feel like it. Eventually I can just put MicroG on the unofficial build from xda-devs, since that doesn't contain GApps; but I am not sure how great the experience is when not having the MicroG/F-Droid patches. I will see. EDIT: Regarding signature spoofing, the MicroG github wiki says: > You can also patch your already-install ROM by flashing NanoDroid-patcher, without any computer interaction. It will auto-patch every updated ROM. So maybe that works.
- kop316 8y ago
  Ahh sorry, I missed that. What may be easiest for you is actually to use Xposed. I think that can allow the signature spoofing needed for MicroG.
  - archi42 8y ago
    I used NanoDroid - worked quite well :) I'd still prefer to build a LOS with MicroG integrated, but it's difficult to get the required information from the folks at xda-dev...