yashsingh1/xdaforums huggingface dataset:
[Magisk] Oswald Boelcke:
@Setialpha: Just a brief feedback. Installed today v20.0-beta1 (i.e. more precisely NanoDroid-microG-19.90.20181110 and NanoDroid-BromiteWebView-19.90.20181110) on two Samsung devices, an i9305 and a SM-G901F). Running perfectly.

Android Webview was already replaced by Bromite on the G901F prior to installation of NanoDroid-BromiteWebView. Both zips were flashed through TWRP; no issues at all. Nothing special to report from the G901F.

On the i9305, Android Webview was still available. Installed both zips via Magisk Manager (Magisk v17.3) and rebooted uneventfully. Tried to launch Magisk Manager to check the modules; Magisk Manager opened but was stuck on the logo. Meanwhile, toast messages appeared that Google Play Store crashed. AFWall was unable to configure; most likely root missing. Titanium Backup didn't open.

Rebooted the i9305 into TWRP, reflashed Magisk v17.3, directly followed by NanoDroid-microG and last but not least NanoDroid-BromiteWebView; rebooted. Now, all running extremely fine and without issues; Android Webview was replaced by Bromite as system app. Nothing special to report besides the issue when trying to install through Magisk Manager (actually no issue for me personally as I usually flash NanoDroid through TWRP). However, I didn't expect that issue therefore I wasn't running a logcat. If it's benefial and of interest I'm able to reset the i9305 to status quo ante and try to reproduce the problem while Matlog is recording and extracting the TWRP log.
[Magisk] marcdw:
Ah, for a second I was gonna face-palm, thinking how could I miss that. But I didn't. The ROM running NanoDroid is PureFusion Nougat. That setting is in Oreo and above I believe.

Since the ROM I'm composing on now is Nougat I installed Amaze 3.3.0RC10. No problems with grayed out install button. Must be a ROM thing. Thanks.

ZTE Axon 7 A2017U, /e/ v0.1 ROM, microG (NoGapps), Multiboot, XDA Legacy
[Magisk] DeebWeb:
Installed NanoDroid microG all perfectly without errors . But now broken Xposed installed, activation error, how to fix please tell me ?
[Magisk] Setialpha:
I don't know? I don't use Xposed, but several users reported no conflicts occured from NanoDroid + Xposed.

What's the logcat?
[Magisk] Setialpha:
Version 20.0 will no longer support flashing through Magisk Manager. While it worked in most cases, it wrecked havoc, if it failed.

Already required TWRP flash before:

- Uninstaller

- SetupWizard

Requiring TWRP flash with next release:

- Full package

- microG package

- F-Droid package

- Bromite WebView package

Still flashable through Magisk Manager:

- Patcher

Installation as Magisk Module of course still is supported (and default and recommended), but you're now forced to do it from TWRP.
[Magisk] DeebWeb:
installed Magisk, systemless Xposed

I try to reactivate Xposed, error

ERROR: Could not access Xposed jar '/system/framework/XposedBridge.jar'
[Magisk] Koont:
Anybody else get an error 7 when updating play store through fdroid? Got this on v 19 and 20 beta.

LG V20

Resurrection Remix 6.2.1

Magisk 17.3

Any kernel SS v40

313 GPU
[Magisk] marcdw:
Interesting. Same behavior on my PureFusion but I haven't checked thoroughly as to why. Will see if I have same error you found. Xposed will activate on soft reboot though.

Moto G5S Plus XT1806, OmniROM, microG (NoGapps), MultiROM, XDA Legacy
[Magisk] DeebWeb:
Xposed is activated. Thanks for your advice
[Magisk] Playe:
I twrp flashed only the bromite webview package, which shows up in my app list but is not available in developer options (only chrome). Android system webview is disabled. Any ideas to get bromite webview to work? Stock pie on Google pixel 1 rooted with magisk.
[Magisk] Marc0601:
Same problem here, in developer options i got aosp webview only, i am on /e/ rom nougat rooted with magisk on galaxy note 2
[Magisk] Setialpha:
You need to remove updates from previous WebView, aswell, if there are any. Otherwise it worked on all devices I've tested.

If you search through the logcat for 'webview' you can check which one is actually used (the apk path).
[Magisk] Marc0601:
Can u explain??
[Magisk] dhacke:
Hey guys i heard that MicroG on Android 9 isn't possible anymore because of the signature certification.

So my question:

Does anyone tried NanoDroid on Pie? Is it really not possible on Pie to use MicroG?
[Magisk] guest4711:
Because Bromite and webview share the same package id you should not disable webview if you like to use Bromite...
[Magisk] Setialpha:
Well, the first post lists Pie as supported, so, yes, it works.
[Magisk] American_Jesus:
Unable to install thought TWRP

Have the same issue with 19.1 and 20.0

...
/tmp/updater[11]: unzip: not found
!! failed to load Common Installer
Updater process ended with ERROR: 1
...

Have no issues installing ROMs (zip) or Magisk

recovery_Magisk.log and recovery_NanoDroid.log attached

TWRP:

https://android.jenslody.de/BootleggersROM/j5ltechn/TWRP/TWRP_3.2.3_j5ltechn_20181013_jenslody.img
[Magisk] marcdw:
Wait, you have Google Chrome installed? If I'm not mistaken Chrome takes precedence as the webview provider and disables system webview. If memory serves.

ZTE Axon 7 A2017U, /e/ v0.1 ROM, microG (NoGapps), Multiboot, XDA Legacy

---------- Post added at 22:59 ---------- Previous post was at 22:49 ----------

No, it's not a problem. Both the Bromite and Chromium webviews are seen by the system as AOSP Webview in developer options. At least on Nougat. I use the webviews on all of my ROMs. Manually placed after flashing and before first boot so I know there's nothing else in the way.

ZTE Axon 7 A2017U, /e/ v0.1 ROM, microG (NoGapps), Multiboot, XDA Legacy
[Magisk] zae857:
Please remove gsync default cause it never works, i flash again use different addon, not built in nanodroid

Version 19 and 20 are same both
[Magisk] Setialpha:
It's not enabled by default.
[Magisk] zae857:
Then why both apps built in default, and how to enable???
[Magisk] Setialpha:
Huh? I thought you want to disable them? You're confusing me.

In your NanoDroid configuration file you have an entry

nanodroid_gsync=1

change it to

nanodroid_gsync=0
[Magisk] fink.nottle:
To any of you using microg with chromium (or bromite) webview, are you able to use location services reliably in chromium for *google.com websites ? For eg., if you go to maps.google.com and spend some time on the site, does it remain stable ? Chromium crashes for me in this scenario. It only happens for *google.com websites. This is on an AOSP 9 build with the latest upstream microg. Not sure if this fork's microg has any changes that affect his specific issue.
[Magisk] vatsal_chandan:
i got same error even if i've enabled sync adapters , but not such error in 19.x version
[Magisk] zae857:
cannot found that, which one?

---------- Post added at 10:50 AM ---------- Previous post was at 10:16 AM ----------

Edit i find it, but didnt work at all,
[Magisk] Setialpha:
GSync Adapter installation will be fixed with 20.0.1 later today. Or grab the latest CommonInstaller from gitlab and replace the one from the zip.

I'm not at home right now, lunch break, so it'll take a few hours, but I made the required change right now.
[Magisk] LovepreetSinghGill:
Unable to install
[Magisk] Setialpha:
TWRP log? Works here.
[Magisk] LovepreetSinghGill:
How to take log of twrp ?
[Magisk] Oswald Boelcke:
TWRP "automatically" records a log while you're using TWRP. Just grab the log when your transaction is down. The TWRP log is saved at /tmp/recovery.log but TWRP also allows you to copy the log to your (if I correctly remember) internal storage. Just search for this functionality; if I remember my TWRP correctly (currently just to lazy to boot into TWRP to look it up) at Advanced and then at the top left.
[Magisk] LovepreetSinghGill:
Ok
[Magisk] LovepreetSinghGill:
Log
[Magisk] Setialpha:
Huh? Your magisk.img is resized to no less than 4334 MB and yet it complains about no free space available. What's the actual size of magisk.img content?
[Magisk] LovepreetSinghGill:
Fixed by installing latest magisk
[Magisk] Playe:
I disabled chrome, but now it's just using the default Android webview v66 (which is the factory version, not updated). Bromite webview is v70. Bromite still isn't an option to select. Not sure if relevant, but the pixel default webview location is /system/app/webviewstub/webviewstub.apk where as the bromite location is /system/app/webview/webview.apk

Any logs that would be helpful?
[Magisk] Cookie Ninja:
Try using the instructions from the bromite webview page https://github.com/bromite/bromite/wiki/Installing-SystemWebView
[Magisk] Setialpha:
Aha, thanks for the heads up! I didn't know about webviewstub. Will add this to the installer, aswell.
[Magisk] LovepreetSinghGill:
Why Bromtie is not showing
[Magisk] Setialpha:
20.1.20181112 "Miranda"

Version 20.1 Codename "Miranda" is now available.

What's new

fix GSync Adapter installation

improve BromiteWebView package ROM compatibility

improve Uninstaller (System Mode)

Notes

See Version 20.0 announcement for additional informations

If you have issues with BromiteWebView not being shown by your ROM, first uninstall the old Module from Magisk Manager, reboot, once it's gone, flash the new module version from TWRP

Full ChangeLog

## 20.1.20181112 "Miranda"

### Bug Fixes

* CommonInstaller
* fix GSync Adapters installation

### General Changes

* Bromite WebView package
* change apk path from /system/app/webview to /system/app/BromiteWebView
* disable /system/app/webviewstub (some ROMs use that instead of /system/app/webview)
* get rid of webview updates, aswell, if it's a fresh NanoDroid installation

* Uninstaller
* in System Mode restore all debloated apps upon uninstallation, not just GApps

Download links

Download from Nanolx or AFH.

Bug reporting

In case of errors, please provide

/data/adb/MODID_log_INSTALLDATE

/data/adb/MODID_twrp_INSTALLDATE

logcat (if applicable)
[Magisk] DoR3M3:
I actually thought this Miranda;

https://www.bbc.co.uk/programmes/b00w7dv9

LOL ;)

Keep up the great work!

P.S. If you've never watched Miranda, I highly recommend it!
[Magisk] AuxNips:
Patcher crashes TWRP and Magisk (when installing as module).

[MENTION=4187311]Setialpha[/MENTION]

8.1.0 Lineage OS.

TWRP 3.2.3-4

Magisk 17.4 (17.1, 17.3 as well)

Patcher* versions tested: NanoDroid 20.1.20181112, 20.1.20181111, 19.0.20181027, 19.1.20181102, and 19.1.20181103.
[Magisk] marcdw:
Page 465. Page 466. You should really check first about an issue. These past few pages have pretty much been about Bromite.

Moto G5S Plus XT1806, OmniROM, microG (NoGapps), MultiROM, XDA Legacy
[Magisk] zae857:
How to fix update plau support libaries, this one always come after reboot
[Magisk] Setialpha:
This issue was both stated here and in microG github previously.

tl;dr: wait until today evening (CET), when a new unofficial microG build pops up in my F-Droid repository,
[Magisk] rayman95:
Is there a method to flash LOS or can I just flash ROM and patch + nanomod kernel magisk and reboot???

Thanks for advice
[Magisk] guest4711:
If you want nanomod to be installed systemless you should flash Magisk first.

1. Usual wiping

2. Flash ROM

3. Reboot to recovery

4. Flash Magisk

5. Flash Nanomod + Patch

6. Reboot and enjoy.
[Magisk] kurtn:
For official lineageOS there is a microG variant. For unofficial the "method" is to clean flash ROM and patcher.
[Magisk] rayman95:
It's unofficial but should I flash rom and nanodroid magisk reboot and patch reboot or rom patch and the rest or it doesn't matter????
[Magisk] kurtn:
Doesn't matter. Magisk is not necessary.
[Magisk] zae857:
Can i install nanodroid microg v20.1 as magisk???

botloop when i want to upgrade microg with twrp
[Magisk] kurtn:
I'm a little bit disappointed. I installed the microG version and meant to get the absolute minimum version. But I got PLAYSTORE! OK. There is an uninstaller. Could you please have a look at the log from uninstaller? There was a red message in twrp and I fear there are leftovers.
[Magisk] NamitNayan:
as you didn't check the documentation to know the defaults beforehand.
[Magisk] :
Hello !

I'm using NanoDroid microG and I wondered why I needed to flash the zip directly in TWRP instead of Magisk, as the latter said no ?

Just curious :)
[Magisk] zae857:
Maybe new one doesnt suooort magisk
[Magisk] razorfancy:
[MENTION=4187311]Setialpha[/MENTION]

I am using Nanodroid MicroG v19 to update to v20 do I need to flash the NanoDroid-patcher-20.1.20181112.zip and the NanoDroid-microG-20.1.20181112.zip or just need to flash the NanoDroid microG zip file?
[Magisk] :
Not when you directly flash from Magisk, but on TWRP it works and say Magisk stuff so ... I guess.
[Magisk] Setialpha:
Guys, read the announcements. It is clearly stated that FLASHING through Magisk Manager is no longer supported. Magisk Mode installation is still supported and default.
[Magisk] Setialpha:
The patched services.jar is kept during upgrade, so just flash the upgrade.
[Magisk] Setialpha:
A bit harsh, but I guess that one thing causing confusion is that Play Store choice is not bound to microG choice, because those are two different settings.

Besides I'll fix the bug in the Uninstaller soon. Or use version 20.0 instead.
[Magisk] Setialpha:
Uploaded a new microG GmsCore build to my F-Droid repo which spoofs Play Services version 14.7.92.
[Magisk] razorfancy:
So just to make sure, I only need to flash the NanoDroid-microG-20.1.20181112.zip right?
[Magisk] rayman95:
just added your repo but i'm still on V12.2.12 and there is no update...Do I have to unistall and install the new one???

thank's

EDIT : I answer myself, I uninstall actual version and in fdroid I find only V12.5.15...How can I get the good version???or maybe V14.. is the true google play store????
[Magisk] AuxNips:
[MENTION=4187311]Setialpha[/MENTION]

Why won't you help me? I provided log, version, and rom information, what else am I missing? Your patcher won't install through TWRP or Magisk.
[Magisk] zae857:
I cant install trough magisk, it says not magisk module
[Magisk] Devagya:
discord not working, gateway timout, possibly due to microg
[Magisk] jenslody:
The answer is in the post you quoted: to make it more clear (hopefully):

no installation through Magisk(-Manager) possible, but it detects Magisk in TWRP and installs in Magisk mode then.
[Magisk] mobilism:
Dose anyone notice that if installed MicroG patcher and updated Android System Webview to latest ,via browser loads web pages very slow.
[Magisk] Setialpha:
You are confusing Play Store with Play Services. Play Store is 12.5.15, Play Services (= microG GmsCore) is 0.2.6.14792-dirty-105 (where 14792 is the spoofed version). For some reason (bug) in F-Droid it sometimes appears as UnifiedNlp (NoGapps), see screenshot.
[Magisk] Setialpha:
Nope, it doesn't. It says can't be installed from Magisk Manager.

this
[Magisk] Setialpha:
Wait. I suppose I can come up with a test build, soon™.
[Magisk] Shobit Joura:
I installed nanofroid microg on oreo 8.1 roms , it works like a charm, but when i install the same on android pie and after setting up location backends in self check , following bozlxes are unchecked and location services arent working fine!!

Box 1 - no known location

Box 2- geocoder cant test location no location is provided !!!

Plzz help !

I have tested it in 3 to 4 pie roms it didnt work !!!!

Or tell me any alterneative for accessing location !!!!!

---------- Post added at 08:59 AM ---------- Previous post was at 08:54 AM ----------

The same is happening with me on pie , buton orea its working fine , plzz help how to get those boxes checked ,/!/

I have given them permissions tried same on 3 to 4 roms but no luck help plzzzz!!!!
[Magisk] ashwini215:
Check if providing the following permissions through a terminal app help your cause :-

pm grant com.google.android.gms android.permission.ACCESS_FINE_LOCATION

pm grant com.google.android.gms android.permission.ACCESS_COARSE_LOCATION
[Magisk] Shobit Joura:
Tried but doesnt worked

---------- Post added at 09:26 AM ---------- Previous post was at 09:26 AM ----------

I rebooted also but no luck!!!
[Magisk] Setialpha:
Rule of thumb don't !!!!!! it's generally seen as impolite.

To answer your question: as always, not all ROMs are compatible or contain conflicting packages and only a logcat can sched light.
[Magisk] Koont:
Any idea how to update Playstore through f droid on the latest release? Clean install, Resurrection Remix 8.1, and Magisk flashed after Nanodroid.
[Magisk] SH1M4BD3:
Is everyone has same situations with me, how to make googlephotos working : syncing , backup did not work its stuck on getting ready, is there any chances to make this work, as all my photos already on google photo..
[Magisk] Setialpha:
Because

a) you have Fake Store installed, then this is the desired result

b) you have a different Play Store as mine installed currently
[Magisk] Koont:
A.. I thought we needed both for in app purchases.
[Magisk] Setialpha:
Nope. You need Play Store for purchases, Fake Store only if you don't want Play Store, you can't install both at the same time. That's why NanoDroid doesn't offer an option to do so.
[Magisk] AuxNips:
Thank your for responding, even if (it looks like) you're being condescending. :good: :good:
[Magisk] DoR3M3:
Since Nanodroid-microG doesn't support my device I have to follow your OP and do this manually, also adding in some changes you make like which help. :)

So for the moment I am using the microG F-Droid repo to install;

microG Services Core

microG Services Framework Proxy

FakeStore microG Store

microG DroidGuard Helper

So there's a problem with GmsCore v0.2.6.13280 and have you created/patched this version of microG?

I also see listed on your repo there's DroidGuard Helper, what changes have been made to this?

http://nanolx.org/fdroid/repo/

When you have a little time, can you PLEASE put down some information on this repo site, telling us what changes to GmsCore & DroidGuard Helper have been done? That way someone like myself that does this manually, doesn't have to look around for changelogs somewhere else, it would be GREATLY APPRECIATED!

https://nanolx.org/fdroid/repo/ seems to work just fine, you might want to mention it besides the QR Code, newbies might get confused.

I also put up a microG guide to do this manually and I'd greatly appreciate it when you have some free time to read it over and give me some of your thoughts input, if there might be some better ways to do anything? Especially since you have this repo, I want to know if I should be adding that to my guide for other people to be sure to use this version of GmsCore & DroidGuard Helper.

https://xdaforums.com/oneplus-5t/how-to/guide-microg-deodex-signature-spoofing-t3862961

I'm assuming for now to continue installing microG Services Framework Proxy & FakeStore microG Store from the microG repo and install

microG Services Core & microG DroidGuard Helper from the Nanodroid Repo, even if doing this manually? I'm also assuming that all these versions are in the Nanodroid-microG?

Thanks

P.S. Bromite SystemWebView is just a replacement of Android System WebView?

Download Bromite SystemWebView

https://www.bromite.org/system_web_view

I don't like or want Chromium, but a webview replacement that is more secure and Google free sounds nice... ;)
[Magisk] Shobit Joura:
I am attaching a logcat. Plzz see and help if possible.
[Magisk] zae857:
How to fix gojek feature cannot load with microg map api v1?
[Magisk] Shobit Joura:
Hey i am providing one more log after entering the following commands and rebooting ,

su

pm grant com.google.android.gms android.permission.ACCESS_FINE_LOCATION

pm grant com.google.android.gms android.permission.ACCESS_COARSE_LOCATION
[Magisk] LovepreetSinghGill:
Error
[Magisk] marcdw:
You really need to specify what it is that you are doing or trying to do. It appears you are trying to install the standalone unifiedNlp but I'm not sure. If you are, don't, as it is already a part of the microG core.

Please provide more info than just "Error".

LG G3 D851, LiquidRemix v9.1.3 Oreo ROM, microG (NoGapps), MultiROM, XDA Legacy
[Magisk] LovepreetSinghGill:
There is an update for unified NLP(no gapps) but when I try to upgrade the error is showing .
[Magisk] Oswald Boelcke:
I haven't see an update of UnifiedNlp (nogapps) for quite a while.https://github.com/microg/android_packages_apps_UnifiedNlp/releases

And the f-droid repo shows for all three different UnifiedNlp January 2017 as last update date:

https://f-droid.org/en/packages/com.google.android.gms/

https://f-droid.org/en/packages/org.microg.nlp/

https://f-droid.org/en/packages/com.google.android.location/

The Xposed modules are even older:

https://repo.xposed.info/module/de.r3w6.xposedunifiednlp

https://repo.xposed.info/module/be.r3w6.intika.xposedunifiednlp

What has been updated were different backends. There's also a thread available dedicated to UnifiedNlp (https://xdaforums.com/android/apps-games/app-g-unifiednlp-floss-wi-fi-cell-tower-t2991544), which is regularly monitored by @n76 who actively works on these projects.
[Magisk] h_maharaj:
The update is actually for Microg GmsCore (to version 0.2.6.14792-dirty-105). I updated yesterday but for some reason it shows up as UnifiedNlp (no gapps) in Fdroid (Nanolx repo).
[Magisk] Oswald Boelcke:
Thanks for the info; I know. I updated two days ago and in my F-droid/nanolx repo it's shown as what it is (refer to screenshot). Anyhow, that wasn't that what we're talking about but probably a good guess (or assumption) taken the little or better none information into consideration the initial poster provided.
[Magisk] LovepreetSinghGill:
How can I update it
[Magisk] yakaaithiri:
Users from India? Any way to get apps like Ola Cabs and UTS work with MicroG ? ..

Ola says turn on location while UTS is not even logging in . Uber is working fine though. Please guide me.
[Magisk] kurtn:
F-droid
[Magisk] Setialpha:
In regards to unifiednlp I'll just quote myself. On one of my devices microG GmsCore is shown as unified nlp aswell, wrongly.

And in regards to ANY future bug report without detailed information and/or logs: I'll keep the right to silently ignore them.

Currently I'm spending more time arguing about that I need logs, rather than digging into them and do something useful
[Magisk] Setialpha:
This weekend I'll post a testing zip that will collect ROM infos, so I can check what could be done to improve compatibility. Not just for the Patcher, but also for the GApps removal script.
[Magisk] Setialpha:
I'll dig into this, this weekend.

http://nanolx.org/fdroid/repo/ is also a webpage with information about the packages.

microG GmsCore has the source linked, which shows the differences in it's README, DroidGuard Helper contains the fix required for it to work on non 32bit arm devices.
[Magisk] Setialpha:
I'll have a look at it the next days.
[Magisk] DoR3M3:
Hi Setialpha

I forgot to mention, since I'm doing this manually and using the official microG, is there any problems with sticking to official? I'm just trying to figure if doing this manually, what advantage I'd have using the Nanodroid-microG GmsCore version, as well as the DroidGuard Helper?

At least from what I see, you're more active... :)

I did dig through the README, this is all I found;

* Play Store (reason: re-signed and modified to support (in-)app-purchases with microG GmsCore)

* microG GmsCore (reason: built with additions) - additions?

* microG DroidGuard Helper (reason: built with fix for non 32bit arm devices failing SafetyNet attestation)

Anything else about GmsCore you can tell/explain?

Thanks
[Magisk] Shobit Joura:
Ohkk sir waiting for your response..
[Magisk] LovepreetSinghGill:
But it showing error while updating
[Magisk] Oswald Boelcke:
You can always flash the NanoDroid microG module through TWRP just on top of the existing installation. the µG module also contains UnifiedNlp.