yashsingh1/xdaforums huggingface dataset:
[Magisk] DoR3M3:
[MENTION=4187311]Setialpha[/MENTION] well you changed the way things work from NanoDroid-microG-17.9.20180818 to NanoDroid-microG-18.0.1.20180907 so just as I got comfortable with one method, I'm now trying to wrap my head around the new changes...

With 17.9.20180818 and .nanodroid-setup, this worked just fine for me in the past, it removed the various Google Services/Framework/Play Store and whatever else, only to install and have microg running, now this is not the situation with NanoDroid-microG-18.0.1.20180907, and now I'm trying to understand, why change this basic function of simply installing microg? I'm not talking about Gapps debloating, I'm only talking about the debloat needed for microg to install and work, nothing else...

To me to say Gapps means most of the basic Google Apps; Calendar, Phone, messege, Gmail, Maps, etc... To me microg is about removing the framework/system of Google that microg needs...

Anyhow, now it's confusing, now you're saying I also need to configure .nanodroid-overlay to have NanoDroid-microG-18.0.1.20180907 to install properly?

Because when I look at https://gitlab.com/Nanolx/NanoDroid/blob/master/doc/NanoDroidOverlay.md I'm not seeing anything related to having microg installed and working properly.

But when I look at this page; https://gitlab.com/Nanolx/NanoDroid/blob/master/doc/GAppsRemoval.md this makes more sense for microg, but reading that page, to me this is happening automatically?

Again, I see, or understand nothing about the documentation as it relates to .nanodroid-overlay and having microg install properly... :eek:

getprop | grep ro.build.

[ro.build.ab_update]: [true]
[ro.build.characteristics]: [nosdcard]
[ro.build.date]: [Mon Jun 25 08:05:06 PDT 2018]
[ro.build.date.utc]: [1529939106]
[ro.build.description]: [mata-user 8.1.0 OPM1.180104.267 399 release-keys]
[ro.build.display.id]: [OPM1.180104.267]
[ro.build.fingerprint]: [essential/mata/mata:8.1.0/OPM1.180104.267/399:user/release-keys]
[ro.build.flavor]: [mata-user]
[ro.build.host]: [02389ad3b031]
[ro.build.id]: [OPM1.180104.267]
[ro.build.product]: [mata]
[ro.build.shutdown_timeout]: [0]
[ro.build.system_root_image]: [true]
[ro.build.tags]: [release-keys]
[ro.build.type]: [user]
[ro.build.user]: [jenkins]
[ro.build.version.all_codenames]: [REL]
[ro.build.version.base_os]: []
[ro.build.version.codename]: [REL]
[ro.build.version.incremental]: [399]
[ro.build.version.preview_sdk]: [0]
[ro.build.version.release]: [8.1.0]
[ro.build.version.sdk]: [27]
[ro.build.version.security_patch]: [2018-07-05]
[Magisk] Setialpha:
GApps removal list is hardcoded, for everything else the file .nanodroid-overlay is used, it will only debloat what's inside that file. See the docs.
[Magisk] Setialpha:
OK, looks like I can safely distinguish Stock and Custom ROM, let's see whether 18.0.2 fixes the issue (in a way it does not break Custom ROMs).

No, nothing changed regarding microG installation at all.

Well you asked me about nanodroid-overlay and I answered., but now I come to the conclusion that you're mixing up two complete different features, or you want to connect them, when there's no connection.

1) microG installation has it's own hard-coded GApps removal list, which is NOT connected to the debloat feature

2) The debloat feature utilizes the .nanodroid-overlay file to know what to debloat

2a) if you only want microG installation you don't need the debloat feature

2b) if you want the debloat feature, you may need to create nanodroid-overlay file, unless you're happy with the defaults
[Magisk] DoR3M3:
Sorry I was only confused by what you said before, thinking I needed the .nanodroid-overlay...

Ok I understand now that it's the same way as before...

So when using the .nanodroid-setup below that I used in the past for 17.9.20180818, now with 18.0.1.20180907 it does not work.

I'll go back and install it all over and flash it again, and post a /tmp/recovery.log

nanodroid_microg=1
nanodroid_fdroid=0
nanodroid_apps=0
nanodroid_overlay=1
nanodroid_zelda=0
nanodroid_mapsv1=1
nanodroid_init=0
nanodroid_gsync=0
nanodroid_swipe=0
nanodroid_forcesystem=0
nanodroid_bash=0
nanodroid_nano=0
nanodroid_utils=0
nanodroid_fonts=0
nanodroid_override=0
nanodroid_play=4
nanodroid_nlpbackend=0
[Magisk] Setialpha:
18.0.2 hotfix release

Hi all, another hotfix release.

Notes

Version 18.0 contains many changes, so I recommend you read first:

18.0 announcement post

18.0.1 hotfix release post

What's new?

## 18.0.2.20180908

### Bug Fixes

* Full, microG packages
* improve microg-permissions.xml to fix bootloops on some Pie ROMs

* CommonPatcher
* try to detect whether we are on a Custom or Stock ROM
* should fix linking issues on Stock ROMs

### Updates

* manual
* Play Store (11.6.18)

Download links

Download from Nanolx (AFH link will follow later).

Bug reporting

In case of errors, please provide

/data/adb/MODID_log_INSTALLDATE

/data/adb/MODID_twrp_INSTALLDATE (TWRP Installation)

logcat (if applicable)
[Magisk] DoR3M3:
WOW that was fast, I wasn't expecting it so soon... ;)

I'm quick too, LOL, I just wiped it, and flashed back Stock Oreo 8.1.0 and patched it with the /doc/DeodexServices.md for VDEX and installed Magisk, and I was only seconds away to flash NanoDroid-microG-18.0.1.20180907...

Ok I'll try now instead NanoDroid-microG-18.0.2.20180908 and I also placed in this /path;

/data/media/0/.nanodroid-setup...

BRB ;)
[Magisk] DoR3M3:
It's still not working microg is not being installed using NanoDroid-microG-18.0.2.20180908.

Again this is my .nanodroid-setup options below, placed in /data/media/0/.nanodroid-setup

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

I've attached the /tmp/recovery.log

P.S. I have a screen shot to show you how the app drawer looks with no microg. I also thought Gmail, Maps, and Photos was suppose to be removed? At least I thought these were removed with 17.9.20180818, now I forget?...
[Magisk] Setialpha:
The installer log is fine, but I going logically through everything I guess I know what's wrong. Try the following:

a) remove /data/adb/NanoDroid_FileList

b) go into TWRP and flash again

tell me whether it solved your issue.
[Magisk] DoR3M3:
Ok I'll do that, and in the meantime I noticed you were asking to post these, so here they are too...
[Magisk] DoR3M3:
[MENTION=4187311]Setialpha[/MENTION]

a) remove /data/adb/NanoDroid_FileList - Yes I did it!

b) go into TWRP and flash again - Yes I did it!

No it's not working, still no microg appears in the app drawer... :(

The App Drawer looks the same as the screen shot I attached before...
[Magisk] Setialpha:
I'm currently uploading 18.0.3, if that doesn't work for you, I need a logcat.
[Magisk] Setialpha:
18.0.3 hotfix release

Hi all, another hotfix release. This is the last one I hope, please don't hate me (lol).

While the patcher got much love from beta testers, the packages haven't, so we stumbled across several issues that never appeared on my limited tests. But it should be fine now, or at least on par with 17.9. Coming to my mind it would be much easier to drop System Mode support at all.

Notes

Version 18.0 contains many changes, so I recommend you read first:

18.0 announcement post

18.0.1 hotfix release post

18.0.2 hotfix release

What's new?

## 18.0.3.20180908

### Bug Fixes

* CommonPatcher
* don't register services.jar in uninstaller information for System Mode installation
* fixes logical interferences with CommonInstaller

* CommonInstaller
* migrate /data/adb/.nanodroid-list to /data/adb/NanoDroid_FileList

### General Changes

* CommonInstaller, Uninstaller
* update for CommonPatcher changes

Download links

Download from Nanolx (AFH link will follow later).

Bug reporting

In case of errors, please provide

/data/adb/MODID_log_INSTALLDATE

/data/adb/MODID_twrp_INSTALLDATE (TWRP Installation)

logcat (if applicable)
[Magisk] DoR3M3:
Ok, time to wipe and flash it all over BRB in just a few, I'm speedy... ;)

BIG THANKS!

P.S. I'll try NanoDroid-patcher-18.0.3.20180908.zip too, I hope it works also...
[Magisk] :
[MENTION=4187311]Setialpha[/MENTION] I noticed when i upgraded to 18.0.2 via magisk microg settins loses , via twrp all settings are ok
[Magisk] DoR3M3:
SUCCESS! WoOT! ;)

Essential PH-1 (Stock Oreo 8.1.0)

/doc/DeodexServices.md - VDEX Method

NanoDroid-patcher-18.0.3.20180908 - successful

NanoDroid-microG-18.0.3.20180908 - successful

One question, look at the attached screen shot, the Gapps that are still installed, should these of also been removed?

Calendar?

Chrome?

Gmail?

Maps?

Photos?

As I mentioned before, I thought NanoDroid-microG-17.9.20180818 removed these, or some of them?

BIG THANKS, I'll HIT that thanks button... ;)

P.S So what was wrong with the previous patcher versions, that it was causing TWRP to go blank screen, and what was wrong with microg before not installing?
[Magisk] tom.android:
18.0.3 hotfix release

test with update ROM. (installed patch and nanodroid-full with magisk manager.)

it working great on official rom. ( manual deodexed services.jar )

finally the hard work for using nanodroid is now on stock or official ROM not Custom ROM. ( only for me)

Tha last quation = how to automatically restore nanodroid-patcher after OTA update ROM.?
[Magisk] Setialpha:
Theese GApps don't interfere with microG, so they are not removed by default. 17.9 behaved the same.

If you want to get rid of them, you can either deactivate them or use the debloat feature.

For the patcher: it went crazy when we set LD_LIBRARY_PATH manually, which on custom ROMs in most cases is required. So we now try to detect whether it's a stock or custom ROM and do the magic accordingly.

For microG: it did not get rid of the old GApps app data and possibly GApps updates which are stored in /data/app under certain circustances. This was fixed in 18.0.3.
[Magisk] DoR3M3:
Only for me?

Not sure I understand that reply, look up at my last reply, it's working for me on Stock Oreo. ;)
[Magisk] Setialpha:
I'll have a look at this. Thanks for reporting.
[Magisk] DoR3M3:
Ok, sounds great, glad you got it worked out, I hope I was able to help out, and glad to help!

For debloating I always use the Magisk Module Debloater (Terminal Emulator)

THANKS for all the great work, keep it up! ;)
[Magisk] tom.android:
How to use nanodroid on MIUI-10 China rom by pass all self-check.? no xposed.
[Magisk] guest4711:
When using Nanodroid Overlay for this purpose there is no need to do it again by hand when upgrading your ROM or even if you have uninstalled magisk cause your decisions are stored in /sdcard/.nanodroid-overlay. They will be used if you reinstall NanoDroid.
[Magisk] DoR3M3:
In /system/framework does it have both odex and vdex files?

Debloter (Terminal Emulator) is so easy to remove and install back if you want. The reinstalling part if you wanted to, I'm not sure with Nanodroid Overlay.

Anyhow Debloater is very simple and works great! Systemless too... ;)
[Magisk] HemanthJabalpuri:
Sir in 4.4.2 when a friend given a patched framework.jar .... I replaced that....

Then checked with signature spoof checker...

It shows enabled....

My question is why services.jar patch? Insted of framework.jar patch in 4.4.2....
[Magisk] guest4711:
Both work the same way: They mount an "empty" folder into /system/app/%app-name% rsp. /system/priv-app/%app-name%

But this is a little bit OT here, so eod and have a good day.
[Magisk] Setialpha:
Design choice. Needle/Tingle patches apply against framework.jar, while Haystack patches applies to services.jar. I'm using Haystack patches.
[Magisk] Setialpha:
That only works, if your ROM has addon.d support, which Stock ROMs don't, NanoDroid already provides an addon.d for that purpose.
[Magisk] kurtn:
This patcher generates an addon.d script. Reflashing the ROM looks like nothing gets patched.
[Magisk] Setialpha:
It tries to, but fails. DalvikVM crashes. I'll see what I can do.
[Magisk] HyperCriSiS:
After update unifiednlp is missing the second to last checkmark. What can I do to fix that?
[Magisk] guest4711:
Did you try a reboot? After doing that open SatStat (GPS, sensor and network status) - https://f-droid.org/app/com.vonglasow.michael.satstat - to test the function. After that all checkmarks should be there... If not, check the permissions of the unified nlp sources.
[Magisk] Setialpha:
The second checkmark indicates whether backends are set-up, it seems they aren't. Please check whether the location backends are active.
[Magisk] Setialpha:
Patcher 18.1~addond_test1

I'm throwing in a new beta build for the patcher with several fixes for the addon.d, re-patching services.jar after ROM update (given ROM supports addon.d) should work again with this build.

Download: NanoDroid-patcher-18.1~addond_test1.zip

Full ChangeLog (patcher only) for this build, compared to 18.0.3:

## 18.1 in-dev

### Bug Fixes

* PatcherAddon
* fix printing messages

* PatcherAddon
* fix DalvikVM crash

### General Changes

* CommonPatcher
* tell DalvikVM to be more verbose
* remove ancient, unused files from addon.d
* for binary files only install the current-arch ones into addon.d
* clean-up addon.d environment every time addon.d is fired up

* CommonPatcher
* ROMs with build-type userdebug are treated as Custom ROMs

Please test, in case you need that feature.

[MENTION=8031265]kurtn[/MENTION] my Nexus 6 (backup phone) went glowing hot just for this, haha, so I hope it does it's job, for you aswell.

Luckily for you the Xenoblade Chronicles 2 DLC release next friday, so you won't see me annoying you with hotfixes and beta builds for a while. :P
[Magisk] kurtn:
My moto e surnia CPU has only 37°C. Patch after dirty update running. Thanks. No hotfix is good news. Means no major bugs :)
[Magisk] ll_L0neW0lf_ll:
Can I restore apps via Titanium Backup after installing microG? Would that break anything? I'm specifically worried about WhatsApp as I don't use their official app from playstore, I use a modded version (GBWhatsApp). Thanks in advance! :)
[Magisk] abacate123:
AFAIK, microG has nothing to do with Titanium, so it should make no difference. As long as you're rooted (and busybox too) it should be fine.
[Magisk] DoR3M3:
[MENTION=4187311]Setialpha[/MENTION], F-Droid seems to be pretty simple and straight forward, just to install the .apk and Magisk has a Privleged Extension module. What is the benefit of doing it instead with NanoDroid-fdroid?

Thanks
[Magisk] d1n0x:
No difference
[Magisk] Setialpha:
Uploaded microG GmsCore build 0.2.5.12878-152 with a fix for microG issues #444 and #598 by voidstarstar.

As root, on-device, use

nupd mg

to update. I've successfully tested updating on my devices btw.
[Magisk] Oswald Boelcke:
Affirmative, you certainly can without any negative effects. However, if we're now talking about a new/fresh installation of µG and not an update and if you restore applications via TiBu that you want to receive GCM push notifications then this doesn't work. Those applications must be clean installed (i.e. if installed, uninstalled first and then re-installed) after the installation of µG but afterwards it's possible to restore just its data from TiBu. If you "only" update/upgrade µG no need for the before mentioned procedure.

As I'm privacy paranoic I don't use WhatsApp, Facebook and all the other **** thus unable to provide any own experiences in that respect.
[Magisk] ll_L0neW0lf_ll:
Thanks! everyone for their help! Finally installed microG on AEX and it's working flawlessly. Faced some issues with WhatsApp after installation ( it was asking me to restore data even after restoring data via Titanium Backup after every reboot) a quick search in this thread solved it, all I had to do was to disable battery optimisation for whatsapp and it started to work properly. But I'm unable to get YouTube Vanced to work (installed from Magisk v 17.1), it says "YouTube won't work without play services (- and something) " and closes on me! Any possible fixes?

Some other apps like Authy and Todoist give me a notification that they cant work without google play services but they are still functional.

Thanks in Advance
[Magisk] iacchi:
This has happened to me with Telegram before. In happened when Google updated some version of their API and microG had not caught up with the change yet. Just wait until microG gets updated.
[Magisk] Setialpha:
microG currently is up to date. This error message also appears when Play Store is missing. See if installing either Fake Stor or Play Store solves your issue.
[Magisk] ll_L0neW0lf_ll:
Yes, I have play store installed but I still get that error message. It's not a big problem as the app works just fine after dismissing that message. Anyways is Vanced YouTube (via magisk v 17.1) working?
[Magisk] kurtn:
I'm just planning a new setup for my daily driver. One main aspect is easy updates. I think, I will install most apps from f-droid. Only patcher and gms-core from nanodroid. Procedure for ROM update will be dirty flashing followed by a 'nupd mg'. I think the addon.d scripts do a good job, but they will revert all updates made after first flashing?
[Magisk] Setialpha:
Nope, that's been a bug in the installer, that's been fixed for both TWRP installation and addon.d with 18.0.2. For Magisk Manager installation this bug will be fixed with 18.1.

Though the other improvements for addon.d will arrive with 18.1 officially. If you want it earlier, repace the file CommonAddon from the zip with the one from the gitlab repo. For the patcher use the previously posted beta build.
[Magisk] Setialpha:
18.1

Hi all, version 18.1 is now available.

What's new?

fixes for flashing through Magisk Manager (GApps removal, Overlay creation and microG data loss fixed)

many improvements for Patcher addon.d and Package addon.d

other minor changes

Full ChangeLog

## 18.1.20180909

### Bug Fixes

* CommonInstaller
* fix installer not detecting upgrade when flashing through Magisk Manager

* CommonAddon
* fix crashes during addon.d post-restore action
* fix printing messages

* PatcherAddon
* fix DalvikVM crash
* fix printing messages

* NanoDroid-Overlay
* fix (re-)creating overlays when flashing through Magisk Manager

* Uninstaller
* fix error in error-printing (sic!)

### General Changes

* CommonInstaller
* code simplifications
* ROMs with build-type userdebug are treated as Custom ROMs

* CommonAddon
* during post-restore action create NanoDroid-Overlay

* CommonPatcher
* tell DalvikVM to be more verbose
* remove ancient, unused files from addon.d
* for binary files only install the current-arch ones into addon.d
* ROMs with build-type userdebug are treated as Custom ROMs
* remove duplicated '!!' in error messages

* PatcherAddon
* clean-up addon.d environment every time addon.d is fired up

* Uninstaller
* remove duplicated '!!' in error messages

### Updates

* automatic
* New Pipe (0.14.0)
* QKSMS (3.5.1)

* manual
* microG GmsCore (0.2.5.12879-152-custom)

Download links

Download from AFH or Nanolx.

Bug reporting

In case of errors, please provide

/data/adb/MODID_log_INSTALLDATE

/data/adb/MODID_twrp_INSTALLDATE (TWRP Installation)

logcat (if applicable)
[Magisk] FusuyevO:
First time using microg.Flashed nano microg but play store is blank.Worked only on first reboot.Android pie.
[Magisk] kurtn:
There are lineageOS weather providers included in full package. These seem to be the official ones. For Oreo we need https://androidfilehost.com/?w=files&flid=243785
[Magisk] Setialpha:
Dunno, on OmniROM Oreo and NitrogenOS Oreo the included ones work. But I'll check what's different.
[Magisk] raptorddd:
guys i been using superSU for a while then now on magisk. and i noticed that theres a module in magisk that its enabled. but after that i cant rename,delete anything in explorer.. if i disable module then i can edit rename delete anything with file explorer. but microg and playstore dissappears then if i check module it appears but microG and playstore set up are also deleted and i have to set it up again.. is that normal? :confused:
[Magisk] :
Sorry i'am noob here,why there is separate microg zip file there in download section,i thought microg already included in nanodroid zip
[Magisk] Setialpha:
There's a full package with everything, and separate, small modules which only contain microG or F-Droid, read here what every package contains.

In order to know how to customize your setup read this.
[Magisk] Setialpha:
Magisk mounts NanoDroid (or any other module) on top of the original /system, thus old, or non-updated, file managers don't properly work, Amaze for example works as expected.
[Magisk] :
What settings do you have for pokemon go? I installed the latest Nanodroid microg, non rooted ROM so no magisk, and using mozilla unifiedNLP. It still says my OS is not compatible. Also running it through island if it matters, but it doesn't run regularly either.

The game runs but eventually I get the "OS is not compatible" screen and locks the game until I relog.
[Magisk] DoR3M3:
I'm still not understanding the reason to use NanoDroid-fdroid, unless you just said Setialpha that there's a bug in the F-Droid.apk installer?

Also [MENTION=4187311]Setialpha[/MENTION], I just used NanoDroid-microG-18.0.3.20180908, so when there's a new release like NanoDroid-microG-18.1.20180909.zip, should we flash that over top of the previous version in TWRP, or Magisk, or this is only needed on a new install?

Thanks
[Magisk] Apex Predator:
Finally got around to installing v18.1. Did it after flashing Magisk v17.1. Didn't go as well as I'd hoped but wasnt total disaster.

Issue #1: debloat did not work at all. It's never failed in the past. All relevant apps marked were still there on boot. Ended up having to use the Debloater terminal emulator module in Magisk. No big deal.

Issue #2: In the past when I've updated, apps that may have been installed prior but were not marked for install on the update would be gone, this time they were still there. For eg I chose not to install Newpipe because the F-Droid version is broken and I wanted to install the latest from their github but the old version is still there, along with playstore (I opted for fakestore only this time).

Tried a second time, this time I ran the uninstaller, which I usually don't. Playstore was gone but all else remained as detailed above... no debloat, old apps not removed.

Thoughts?

BTW if I knew exactly which log to post and where to find it I will gladly do so.

---------- Post added at 03:43 AM ---------- Previous post was at 02:57 AM ----------

Well third time's a charm I guess. Installed again without running uninstaller but with running the wizard again and debloat worked. Very strange. Play store still gone but Newpipe still there. Other apps needed reconfiguring (as they usually do after an update) which makes me wonder why they didn't the first couple of tries.

Still waiting for microG to pop up with it's request to register Protonmail for push messages. As usual I had to uninstall/reinstall because of the microG update. Usually pops up not long after I sign in.

One big victory though - looks like I definitely DO NOT need to have play store installed! As per prior discussion in this thread, all I had to do was go into spoofing permissions, hit the 3 dot menu, allow system apps and voila.
[Magisk] Apex Predator:
Okay, scratch everything I wrote above, phone started bootlooping. Post is still relevant I guess (and insight would be good) but now I have no idea what's causing the problem. Had to restore the backup I made before commencing.

On reflection, it was a bad idea to update both Magisk and NanoDroid but I figured that's what I would do for a fresh install so what's the harm?

I'm going to sit tight for a while then maybe just install Magisk update and reboot, leave that for a while, THEN if all seems okay will try NanoDroid again.

[MENTION=4187311]Setialpha[/MENTION] - can you please advise on best practise for this operation? It's a simple update from v17.9 to v18.1. My usual method is to just run the wizard, step through it then flash the full package and reboot. Should I be uninstalling first? I've never had to before.