UnifiedNlp icon indicating copy to clipboard operation
UnifiedNlp copied to clipboard

Please Update readme.md

Open Mannshoch opened this issue 4 years ago • 8 comments
trafficstars

Describe the bug The current readme contain a link to releases with last Version is from 2017 Also the current readme miss information about Android newer than 7.

To Reproduce Steps to reproduce the behavior:

  1. Go to 'https://github.com/microg/UnifiedNlp
  2. Read the readme

Expected behavior

  • Some information about Android New er than 7
  • Is there may a Magisk module for that?
  • Link to newer release

System Android Version: 10 Custom ROM: LineageOS 17.1

Additional context After installing unified nlp from fdroid itry to find a way to register it in system and ended here.

Mannshoch avatar Jan 26 '21 17:01 Mannshoch

Here's a guide I wrote (with some information found here) on how to install UnifiedNLP on LineageOS 17.1: https://blog.eowyn.net/unifiednlp/

nobodywasishere avatar Apr 11 '21 18:04 nobodywasishere

For the record, @nobodywasishere your solution worked.

At moment, I'm wondering why there are so many old Issues without progress or get closed becasue not anymore relevant and why the readme.md is still on that old state.

Mannshoch avatar May 08 '21 06:05 Mannshoch

@nobodywasishere thank you for the clear guide, but may i suggest to add a hint, that Magisk must not be installed to get UnifiedNlp working. it took me hours to figure it out and sadly at least on LineageOS 17.1 it seems to be the case, that it also stops working if you install Magisk afterwards.

does anybody have an idea how to get UnifiedNlp working with a rooted LineageOS?

DJCrashdummy avatar Sep 05 '21 12:09 DJCrashdummy

By flashing microG? It's part of the core. Works for me, at least.

IzzySoft avatar Sep 05 '21 13:09 IzzySoft

yes i know his would be kind of a workaround... but i prefer a plain (rooted) LineageOS without any of the Google or microG shenanigans which i have to keep an eye on, that everything i don't like is deactivated.

...not to mention, that my device gets at LineageOS for microG an update once in ~4 months and the plain LineageOS once every ~2 weeks. and on top, for my device official LineageOS 18.1 builds are available for months now, but LineageOS for microG seems still stuck at 17.1. :unamused:

DJCrashdummy avatar Sep 05 '21 17:09 DJCrashdummy

OK, the update frequency is an argument. As for the shenanigans: I simply leave them disabled, which is the default anyway. But as you know of this, I'll shut up – mentioned it just in case :wink:

IzzySoft avatar Sep 05 '21 18:09 IzzySoft

As for the shenanigans: I simply leave them disabled, which is the default anyway.

@IzzySoft i hate it that i have to disagree with you, but at the last devices i flashed with "LineageOS for microG", the "Google device registration" at the "microG Settings" was on by default. i have to admit, that i have hardly an idea what it does... but i know that i don't need and don't want it!

DJCrashdummy avatar Mar 08 '22 20:03 DJCrashdummy

@DJCrashdummy to take away your hatred: there was a bug with that. Even after an update, on some devices it was turned on again. But that bug was fixed months ago, and I never saw it again after that. See: https://github.com/microg/GmsCore/issues/1554

IzzySoft avatar Mar 08 '22 21:03 IzzySoft