yashsingh1/xdaforums huggingface dataset:
[Magisk] Setialpha:
Nope, I don't know, but it has been reported upstream, aswell. See: https://github.com/microg/android_packages_apps_GmsCore/issues/666 You may post a logcat there.

Inside each zip is the fallback configuration file, you can extract it and modify it, then save it in either

a) /sdcard/

b) /data

c) the same directory as the zip file

As mentioned in the 20.3 beta announcement post the syntax for two variables changed with the beta, so for further advice I need to know which one you use (stable or beta).

Also if the doc say: nanodroid_something=[0|1] then it means you have the following choices

a) nanodroid_something=0

b) nanodroid_something=1

for on-off variables 0 = disabled, 1 = enabled, else the meaning is further described in the docs. If the docs (for the beta) say: nanodroid_something=[0|1][0|1] then it means you have the following choices

a) nanodroid_something=00

b) nanodroid_something=10

c) nanodroid_something=01

d) nanodroid_something=11

where each element (digit) as it's own meaning, which is further described in the docs, so what you posted nanodroid_something=2 1 will be nanodroid_something=2 (everything past be space is ditched).

Again depends on whether you're going to use the beta or stable.

No problem here downloading from Nanolx, AFH recently often has slow mirrors.

Works here as system/app + user-app (udpate), but fails for some as priv-app.
[Magisk] Tomatot-:
Thank you so much for your detailed explanation.
[Magisk] Tomatot-:
So I'm using this installer: NanoDroid-microG-20.2a.20181122.zip

Here is my config:

nanodroid_gmscore=1
nanodroid_play=21
nanodroid_overlay=0
nanodroid_mapsv1=1
nanodroid_gsync=0
nanodroid_swipe=0
nanodroid_forcesystem=0
nanodroid_nlpbackend=110

Is there something wrong in it?

I've run the uninstaller, then the installer with this config, and it seems to ignore the lines where I put two numbers:

-I don't have a store nor YALP

-I don't have any of the nanodroid_nlpbackend

Is there something I'm doing wrong? Or does the template work for the beta now?

Thank you for your time...
[Magisk] NamitNayan:
that config is for beta version.

stable will use older way I guess.
[Magisk] Tomatot-:
Yeah I figured this out. But then what's the old syntax way?

Also, I tried the same config with beta but it makes my phone bootloop. :/

EDIT : ok I managed to find the history of the file and so now I should have the right syntax. Thanks anyway.
[Magisk] silkshadow:
Just wanted to report a possible bug/incompatibility with this and Lastpass. To note I don't use Lastpass as my password manager (untrustworthy and garbage company since it got bought) but one of my clients uses it so I have to.

On Note 9 LineageOS 15.1, I flashed Magisk, Nanodroid, and Xposed. Set it up and played with it for 2 days and discovered that Lastpass crashes ( "Lastpass has stopped" error) right after opening. Besides having to force stop and wipe the Play store every couple times it gets opened, Nanodroid was performing great (love it).

Tried AICP (android 8.1), flashed Magik, Nanodroid, and Xposed. Setup quickly, went online downloaded Lastpass first thing and it also crashes right after opening, same as on LOS.

I've now tried both LOS and ACIP but flashed ROM, Magisk, Opengapps and Xposed instead just to see if that was the issue. Lastpass works fine with both ROMs in this scenario. Far from conclusive, but it does point to a possible incompatibility. I'm, sticking with Nanodroid and just using Lastpass in Firefox for now.
[Magisk] Tomatot-:
It's weird

That's my current setup with the last stable:

0) Wipe data.

1) Flash ROM

2) Flash recovery (normal A/B procedure)

3) Reboot recovery

4) Flash NanoDroid-microG-20.2a.20181122

nanodroid_gmscore=0
nanodroid_play=4
nanodroid_overlay=0
nanodroid_mapsv1=1
nanodroid_gsync=0
nanodroid_swipe=0
nanodroid_forcesystem=0
nanodroid_nlpbackend=3
nanodroid_nlpbackend=3

I've also tried

nanodroid_forcesystem=1

and it seems the script doesn't work well with Magisk. If Magisk is installed, my device boots. If the nanodroid is installed, my phone boots. But if I install both I get a bootloop. Any idea?

EDIT: more information:

So I've tried this setup:

nanodroid_gmscore=0
nanodroid_play=4
nanodroid_overlay=1
nanodroid_mapsv1=1
nanodroid_gsync=0
nanodroid_swipe=0
nanodroid_forcesystem=1
nanodroid_nlpbackend=3

Here is what shows on my screen: https://i.imgur.com/rvpR8U0.png

See in attachemnt the logs.

If I open the setup file again, that's how it looks:

nanodroid_gmscore=0
nanodroid_play=4
nanodroid_overlay=1
nanodroid_mapsv1=1
nanodroid_gsync=0
nanodroid_swipe=0
nanodroid_forcesystem=1
nanodroid_nlpbackend=3nanodroid_fdroid=1
nanodroid_microg=1
nanodroid_apps=1
nanodroid_zelda=1
nanodroid_init=1
nanodroid_bash=1
nanodroid_nano=1
nanodroid_utils=1
nanodroid_fonts=1
nanodroid_override=0

When I reboot, sometimes i just go back to TWRP (like at the time I'm writing), sometimes I have a bootloop, and once I booted but I didn't have any of the apps installed.

EDIT 2: using the beta nanodroid leads to the same result: I just boot to TWRP.

I don't even know how I managed in the first place to make it work, when it wasn't even written properly lol.
[Magisk] thoiloidainhan:
Have u had a chance to look into the discord issue, sir [MENTION=4187311]Setialpha[/MENTION] ?
[Magisk] the.D:
Discord works fine here. If you're using NetGuard that's what's causing the issue.
[Magisk] LovepreetSinghGill:
Mine also does not work
[Magisk] bege10:
Can this version be flashed over 20.1 or do I need to uninstall first?

With the F-Droid repo active and no apps from the NanoDroid package installed, do I need to install every full NanoDroid version or is updating via F-Droid enough?
[Magisk] Apex Predator:
You can flash over old versions, no need to uninstall.

Technically you can just keep using F-Droid for package updates (microG etc), that's what I've been doing. I do use apps from NanoDroid, but they also update via F-Droid.

The change in your quote for example wouldn't be applied with an F-Droid update though. You'd have to move it manually, probably easier to just flash the whole package, less messy.

When there's a big update/something new/flashing a ROM update, I'll get the full package, as was the case last week.
[Magisk] bege10:
Thank you for answer. DroidGard Helper is moved by flashing the new version over the old one?
[Magisk] demonoidmaster:
If the only thing changing is that app moving from priv-app to app, flash it and see if it's present in the new folder, then go look in priv-app and if it's still there too just delete the droidguardhelper folder

Or, manually move the droidguard helper folder from /system/priv-app to /system/app first then flash the zip
[Magisk] thoiloidainhan:
Is netguard an adblocker? Im not using it. Been with adaway for a long time. I disabled adaway just in case too and discord still wouldnt connect, keep spinning
[Magisk] Tomatot-:
No it's a firewall.
[Magisk] thoiloidainhan:
Nope. Its definitely microg fault. But in trying to pinpoint the issue i found a partial solution. Disable microg, restart discord then enable microg again. Discord will work from that point on but i will have connection issue again if i restart discord
[Magisk] Tomatot-:
I meant netguard is not a adblocker, it's a firewall, that's all. :good:
[Magisk] LSS4181:
I'm having this issue as well with XZ Premium (CarbonROM 6.1), TWRP 3.2.3, NanoDroid 20.2, just recently (it never happened before). It seems to be some filesystem-related issue.

After instaling Magisk, when I first install NanoDroid full package will succeed. However, the subsequent installs (such as Bromite WebView) would fail because for some reason after flashing NanoDroid resize2fs would see magisk.img as damaged, telling me "Please run e2fsck -f magisk.img first."

However, at this point the img file has been expanded, but the actual file system is not. Also, trying to do "e2fsck -f magisk.img" as instructed would not find any error, and does not fix the error message.

Manually forcing a resize (e.g. resize2fs -f magisk.img 600M) would allow it to install. After resizing, occasionally there would be an inode error when running e2fsck -f magisk.img.

Shrinking would fail again, with the same aforementioned message, so I ended up having to manually shrink the partition using "resize2fs -f" as well (and of course, run e2fsck -f magisk.img just in case).

On the other hand, it seems the Bromite package is not be stable enough on a "user" ROM. Some apps would crash whenever it tries to access WebView related functions. On "user" ROM it might also be checking the WebView APK's signature. On my Pixel C running a Lineage OS 16.0 "userdebug" ROM it's working fine.

And DANGER: Trying to update Bromite WebView from F-Droid could result in bootloop. On my XZ Premium with CarbonROM ("user" ROM) I learned this lesson the hard way. At first it tried to update and failed, and second time, it seemed to succeed, a dialog popped up for a very brief moment that I really didn't see what was written on it, then it went into a bootloop for a few seconds then rebooted to TWRP. I couldn't do anything at this point, so I ended up restoring a backup I did a few days ago when I tried to update from NanoDroid 19 to NanoDroid 20 (and before trying Bromite WebView).

EDIT: It seems manually reinstalling the Bromite System WebView package as user app on top of the Bromite WebView module fixed the issues I've been encountering on my phone. The apps don't crash anymore, so it's probably that by installing the System WebView as user app, other apps would be able to load the libraries directly from APK.

It doesn't appear to be related to whether the ROM is "user" or "userdebug". Some ROMs do require such a step to make other apps properly detect the substituted WebView, while on other ROMs it works out-of-box.
[Magisk] Setialpha:
[MENTION=4542513]LSS4181[/MENTION] are you using Magisk 17.3 it's a bug several users already have suffered, including myself but the recent versions seem to have fixed it for me. At least on the ROMs I've tested Bromite WebView works in all cases, but yes, compatibilty can't be garanteed.

*snip*

Also, I don't get all theese questions, if you have you to use the UNINSTALLER before an UPDATE. Of course not, else it would be called Updater, not Uninstaller *sigh*. Or do you remove your ROM/WhatsApp/Firefox/Whatever before an update? No.

Also given on a fresh installation - as opposed to updates - the GApps removal mechanism is triggered. As you all know microG packages have the same package names as GApps packages. Thus logically you're going to kill your microG setup, most noticeably GCM registrations, when using the UNINSTALLER before an "update"; as it then of course is NO update, but a FRESH installation, obviously, as you removed anything that could have been updated...

I don't understand this question in first place, honestly.
[Magisk] SH1M4BD3:
I'm on latest beta 2018-11-28, how to check and enable the last location options on self-check??does it improves the locations accuracy?

On the last beta i'm sure that i've checked the all 3 option on setupwizzard DeJa-vu,Mozilla,and new Apple things..but there's only DeJa-Vu inside the UnifiedNLP backend, is that normal??
[Magisk] guest4711:
Probably a problem with the installer. You may install these backends from f-droid without problems. After that you can select them in the backend. No reboot needed.
[Magisk] DoR3M3:
Network-based location enabled is typically unchecked when you have Location OFF in the phone settings, make sure it's on "High Accuracy'" too...

[MENTION=4187311]Setialpha[/MENTION] any progress on this?

---> https://xdaforums.com/showpost.php?p=78244782&postcount=4839

Thanks
[Magisk] LSS4181:
Yeah I'm using Magisk 17.3. It seems to happen to me mainly on the Bromite package, not the full package.

Also, as for having to use the Uninstaller before an update... well, back then I had some strange issues when upgrading from one major version to another (v19 to v20), that some apps force close, mainly involved the Simple series tools which went Pro. The system appeared as if it was remembering the old (no longer maintained non-Pro) version of the Simple Gallery/Calendar and would still show that version, although it'd simply force close. I can always install the Pro version from F-Droid. Besides that, Termux force closed as well. On the other hand, it seems OTA survival on custom ROMs doesn't work quite well, so maybe that can be the reason why that happened as my phone had went through several OTAs (technically dirty flashes of updated versions), although back then trying to uninstall then reinstall NanoDroid v20 did not fix the issues.

Eventually as the old system broke down thanks to an attempted Bromite Webview update (which I marked as DANGER previously), I clean flashed the ROM and everything else and now everything's working as

intended.

I don't use NanoDroid for microG, only for F-Droid and open source app alternatives, as Wear OS (Android Wear) is still not supported (planned 0.3 milestone with a $35 bounty, which is still far away) and I need it for my Huawei Watch 2.
[Magisk] alecthenice:
Can this be flashed with flashfire?

I have dm-verity enabled. Can someone advise me on how to install this .zip using flashfire? There is no twrp available for my device.
[Magisk] Klizi:
What would happen if I flash f-droid zip followed by microg zip? is it ok to flash both zip files?

Can I use Magisk to flash patcher zip file? so I dont have to keep flashing the patcher each time I update OS?

After the latest update, Magisk doesn't support at all? Do we have to flash all zips through the recovery?
[Magisk] demonoidmaster:
*sigh* people are still trying to use bromite? It doesn't work, why go through that much of a hassle over a modified webview, just use the browser instead

---------- Post added at 04:39 AM ---------- Previous post was at 04:31 AM ----------

All that just to use F-droid? Why not just install it as a user app and install the magisk module for it...
[Magisk] da49155192b8caf2250f5e:
Uninstall third party apps

Hi,

First off, thank you so much for your work. It's really awesome.

My question: I installed some third party applications provided by NanoDroid (like Amaze, OpenLauncher, etc.) through Magisk. I would like to uninstall one or two finally. But because they are installed in /system/app or /system/priv-app/ I cannot uninstall them with the common way. And because they are installed through Magisk, I cannot use a regular debloating tools (like the nanodroid-overlay script for example) neither because apps are not really in /system/app and /system/priv-app.

So, how can I uninstall this apps without uninstalling all NanoDroid? Can I find a config file somewhere that I could edit?

Thanks!
[Magisk] Klizi:
Bromite web view has a bug and it broke the login page of turtl private note taking app (turtlapp.com) which is extremely important to me and now it's not allowing me to get into any of my notes and I got my life stuck.

I need to uninstall Bromite web view which I installed using F-Droid + Priority extension (nanolx)

I don't see the uninstall button. I can only uninstall Bromite browser
[Magisk] Portgas D. Ace:
[MENTION=4187311]Setialpha[/MENTION]:

would it be possible to have the ringtones as a standalone module? So basically without the need to download the whole >200mb NanoDroid module.
[Magisk] knpk13:
I'd be interested in this too since I'm not ready to use microG on my main device yet. But I love Zelda xD
[Magisk] LSS4181:
Provided the Bromite WebView works (which is the case on my Pixel C using a Lineage 16.0 userdebug), it helps keeping WebView up to date without having to use Google's version on Play Store. It seems to be less compatible on a user ROM as there might be signature-related checks involved.

And for F-Droid, I meant to use the Privileged Extensions which allows updates to proceed without my confirmation (which didn't work when I installed it as user app with Magisk module). On top of that, I use it to replace certain apps with open source counterparts as well as systemlessly debloat several apps that I don't use (such as SIM Toolkit, Email, Exchange Services, etc.).
[Magisk] Setialpha:
You can gran individual audio files from gitlab: https://gitlab.com/Nanolx/NanoDroid/tree/master/Full/system/media/audio
[Magisk] Setialpha:
Bromite WebView works here, so it also depends on your ROM.

See Alter Installation in the documentation. tl;dr if you used the Setup Wizard it did create a configuration file you can edit and re-flash it without those unwanted apps.

I may add a feature to nanodroid-overlay for that.

Uninstall the Bromite WebView module from Magisk Manager. Your ROM's original WebView is backed up at /sdcard/nanodroid_backups.
[Magisk] Setialpha:
A) the minor packages can be installed alongsinde, so it's ok.

B) You don't have to flash it everytime, it has a addon.d which is autorun on each ROM update. Flashing through Magisk won't change that. That's because services.jar changes in the ROM update are otherwise not be included, obviously.

C) You are mixing two different things. NanoDroid is an ordinary Magisk Module, but needs to be flashed through TWRP. All Magisk modules can be flashed through TWRP, but NanoDroid is the only one, that must be.
[Magisk] demonoidmaster:
i don't use it, tried out the browser once , it's good but what killed it for me is it can't sync my bookmarks etc
[Magisk] Setialpha:
I don't find anything why it shouldn't work, with the latest GApps removal stuff, just from the log.

Wait for the next beta and give it a try again, if you feel like.
[Magisk] Portgas D. Ace:
I tried to install microG on my OnePlus 5 with AOSP Extended (Pie) and most of the things work out of the box, only GCM push doesn't work. It always shows the status "not connected". What can I do to get it working? All apps have been registered properly.
[Magisk] Setialpha:
If you use any adblocker whitelist mtalk.google.com
[Magisk] Portgas D. Ace:
I already did that and rebooted. Same issue. Will try again tomorrow. Maybe some settings of AFWall+ were interferring with it.
[Magisk] jenslody:
I had this on my workprofile, private profile worked fine. I fixed it by temporary adding my gmail-account to the profile and after gcm was connected, I removed it.

Since then it works on both profiles.
[Magisk] DoR3M3:
I was more concerned with possibly figuring out why the microG UnifiedNlP wasn't working with OxygenOS, but I'm assuming it has to do with the framework.jar needing to be changed...

Hmm and thanks
[Magisk] evilvoice:
[MODULE/SYSTEM] NanoDroid 20.2a/20.3-beta1 (microG, pseudo-debloat, F-Droid + apps)

Bromite works here after I changed my framework, so I don't know what issues others are having. I am noticing some ad redirects that I didn't have before, but I'm still testing. Haven't updated yet to the newest version.

To those having issues with Bromite, are you installing the app a second time? Not only do you need to flash the zip (or place the file in system), but you also need to install the app through the package manager.
[Magisk] Klizi:
Yes, I tried flashing nanodroid through magisk and it got interrupted the process by itself, and I had to flash it through Recovery, not as a magisk module, So now it's impossible to uninstall right?

Would uninstaller zip work all the time? I had to flash f-droid zip through twrp and installed microg core using f-droid, then again, I flashed bromite web view too, and installed it through f-droid and now I can't uninstall bromite web view (it conflicts with some other apps so I wanna remove it so badly). How do I remove MicroG completely? I flashed uninstaller zip but nothing has removed, I can still see bromite web view and microg.

And again: snapchat and signal private messenger doesn't work with MicroG too, even reinstalling after flashing microG doesn't work. App doesn't register with push.

I don't see bromite webview module in magisk manager because, I flashed it through recovery :silly: :(

Is it possible to restore files manually from /sdcard/nanodroid_backups ?
[Magisk] LSS4181:
I don't think the problem is with whether or not to install the app a second time... Maybe it's needed if you're running it on a "user" ROM (on which I'm having problems with). On my Pixel C running Lineage 16.0 "userdebug" ROM Bromite worked without requiring to do anything, probably because substituting WebView is permitted under such environments. On "user" ROMs, replacing WebView with anything other than Google's versions (on Play Store) is considered a security bug and intentionally prohibited.

On my phone running a "user" ROM (CarbonROM) I even ended up soft-bricking it when I attempted to upgrade Bromite WebView from F-Droid. I was not able to figure out the exact cause as there was some message popped up for a very brief moment then it bootlooped (and rebooted itself to TWRP after a few minutes), and my USB debugging was off at that time (because some games would outright refuse to start if USB debugging was on). I don't know where F-Droid attempted to install the update, but it was clear that attempting to install an updated Bromite WebView package (either as user app or system/systemless app) on a "user" ROM broke something very important.

The best way would be to let Bromite WebView be somehow accepted by the custom ROM community (AOSP, Lineage, etc.) so it can be installed on top of the system WebView as an alternative in custom ROMs. But unfortunately, given the current situation with WebView implementations, this is very unlikely to happen. (Off-topic, better discuss such in Bromite's own thread)

EDIT: Turned out you were right all along. On some ROMs, installing the a second time fixed all the crashes I used to have, as by reinstalling, its presence is now properly covered in the system.

EDIT 2: I just found this. Someone has put up a repo that could be used to ship Bromite WebView when building custom ROMs. I haven't tested it, as it appeared new and should be considered experimental. Still, thanks to the one who made it possible to do so.
[Magisk] evilvoice:
While you may not have had to install a second time, you may want to read their wiki on installing their webview through any means.
[Magisk] demonoidmaster:
Or yknow, have bromite not have the same package name as default webview that all roms come with, that's what the bromite dev should do
[Magisk] Klizi:
Somebody tell me how can I get rid of this two bromite webview apps. They are really buggy
[Magisk] evilvoice:
I'm pretty sure it has to have a name that replaces another package or it wouldn't get used. I think webview for all devices is set in framework
[Magisk] oseiasrodrigues0:
Someone knows how to resolve this problem because when I try to update the microg by the F-Droid Nanodroid repository of this error "Pre-installed package with the same name has a different signature of the new package and the old package data have not been removed" someone knows how to solve?
[Magisk] LSS4181:
Aside from the default system WebView (which Bromite WebView tries to replace), the only other ones permitted to be used are Google's WebView (Play Store) and Chrome (Stable/Beta/Canary).

By the way, it seemed possible to configure to build a ROM without any WebView implementations built-in (which was the case for a very brief while for AOSP on Pixel C). On such ROMs, Bromite WebView might be useful and would just work since there were nothing needed to be replaced, and normally you'd need to install at least "stock" opengapps (which contains Chrome) in order to get things that rely on WebView working on such ROMs.
[Magisk] alecthenice:
Ok with dm-verify?

Can I use flashfire.apk to install nanodroid without triggering dm-verity? I am on android 5.1 api 22
[Magisk] DoR3M3:
Look up at Klizi's post above your head, see how small his/her image is?

There is an Attachement section, look down when making a reply --> Attach Files

Please edit and attach your image, now and in the future...

Thanks

P.S. Where's [MENTION=7408621]Oswald Boelcke[/MENTION] when you need him? LOL ;)