yashsingh1/xdaforums huggingface dataset:
[Magisk] starbright_:
I applied nanodroid (latest stable) to a stock Rom and failed. So nanodroid itself reports success. Nevertheless after booting I don't see the microG settings-app.

So I take again a closer look to the manual (apply this to stock is rather new to me).

I removed as described /system/priv-app/GmsCore, GoogleServicesFramework and Phonesky. I also did the boot to system (Question here - what is the reboot important for?). In next TWRP-session microG-nanodroid gets installed. I also can see that files are in proper location. So what else might be the reason? For this test I used version without Magisk.

Another question: what happens if installation is done with out Magisk and later Magisk will be installed.

[MENTION=4187311]Setialpha[/MENTION]: Could you find with the log why the patcher failed on a Stock 8.0 ROM?

https://xdaforums.com/apps/magisk/m...405-microg-t3584928/post83537141#post83537141
[Magisk] ubuntiger:
It does work now, thanks!

To be more precise: ./build-package pull works, and

./build-package all works as well, except for create_report which reports missing templates:

$ ./build-package all
NanoDroid correctly populated
Creating Package
Type Full
Name NanoDroid-23.0.20201012.zip
Directory /home/ubuntiger/git/NanoDroid
Done
[...]
creating NanoDroid report:
| NanoDroid Version: 23.0.20201012
| NanoDroid Type: Snapshot Release
| NanoDroid Report: NanoDroid-Report-23.0.20201012
No report template for file: /home/ubuntiger/git/NanoDroid/BromiteWebView/system/app/BromiteWebView_arm64/BromiteWebView_arm64.apk.zst
No report template for file: /home/ubuntiger/git/NanoDroid/BromiteWebView/system/app/BromiteWebView_arm/BromiteWebView_arm.apk.zst
[...]
No report template for file: /home/ubuntiger/git/NanoDroid/OsmAnd/zstd.x86
Done
$

Looks like being in the context of the change to zst as well. If you need input, just let me know how I can help.
[Magisk] Setialpha:
That's only the report, does not affect the zip file. I haven't updared that feature yet, so that's expected.
[Magisk] Setialpha:
Stock ROMs often hard rely on the SetupWizard, meaning installing microG before the first ROM boot fails, this was seen on OxygenOS starting with Android 10 for example, but of course isn't limited to it.

AOSP or LOS don't have that requirement.

Also most devices now are A/B meaning, flashing ND durectly after the ROM in System Mode will result in ND being installed into the wrong slot. Rebooting either into the ROM or rebooting TWRP updates the active slot. When you check custom ROM threads you'll often see reboot TWRP as installation step for that reason.

Nothing happens when you install ND to /system and Magisk afterwards. What were you expecting?

I'll have a look at the Patcher issue, but currently busy with other tasks. Feel free to check out the git log or ChangeLog og the in-development version 23.0 for more infos.

https://gitlab.com/Nanolx/NanoDroid/-/blob/master/ChangeLog.md

A new beta likely arrives this weekend.
[Magisk] Tomatot-:
Thanks for the news. Do you know if anything changed in Android 11 patcher wise?
[Magisk] andy356:
Why Warden and not App Manager, [MENTION=4187311]Setialpha[/MENTION]?
[Magisk] starbright_:
It is a simple old style non-treble-ROM. And I have bootet into it before my attemps with nanodroid. I repeat the installation now with Magisk installed before. I could find all the parts in /data/adb/modules/NanoDroid_microG/system. So it seems it uses the inherent debloat of ConfigUpdater, GoogleFeedback, GoogleOneTimeInitializer, Velvet ... - they are empty.

And my ROM complains a lot about missing Google Play Services and some apps stop - so far fine.

In Settings/Apps I see microG Droid Guard Helper but not the GmsCore, and so not the microG setting-app. Looking at the setup I am pretty sure this is not your fault.

But what the hell prevents the ROM from starting this? I checked the setting but couldn't find something like that.
[Magisk] rasputin_g:
Did you deodex your rom? I doubt that your stock was already deodexed
[Magisk] starbright_:
No, I didn't. Sorry - using stock ROM is new to me, before I used LOS (but for my device it is to buggy for me).

I go for this manual https://github.com/Nanolx/NanoDroid/blob/master/doc/Installation.md

There wasn't mentioned that (just for spoofing).

Can you give me a hint why this is need and how to do that best? Only few files need to deodex or complete ROM?
[Magisk] rasputin_g:
The patcher is to enable spoofing, and for spoofing to work you need to be deodexed. Although I think the patcher tries to deodex on some older versions, but I don't remember which ones. The manual on the gitlab has instructions
[Magisk] starbright_:
Spoofing is not my first problem. This I solved by smali patcher atm. But what do to to get GmsCore/Fakestore running?

I mean looking at the orginal Samsung apps this are also just normal apks? Arn't odex files haven't a different suffix? Sorry for this questions .... all new to me.

A closer look show me that in some folders is an oat/arm folder, containing a odex and a vdex file. This is for GmsCore and Phonesky, but not for GoogleServicesFramework. And .. this apk can't be decompressed with my archive tools !?! So what do I have to do?
[Magisk] rasputin_g:
OK then Idk when the issue is. doesn't look like you still need to deodex after all
[Magisk] starbright_:
What is for sure is - the original Samsung apps GmsCore.apk und Phonesky.apk are different in it's structure and have an oat folder - which that in NanoDroid doesn't have. It sound like to be the reason why the microG files are not really visible in the system after installation. But doesn't I have to change the microG-files into the Samsung way instead of converting the unwanted orginal files that will be deleted/debloated anyhow? How?
[Magisk] starbright_:
I am runnning a Stock Samsung ROM Android 8 with Orangefox as Recovery.

Today I applied nanodroid after installing Magisk + SmaliPatcher.zip for spoofing and don't do any debloating at all. So did'nt delete anything manually. It seems to work :)

Magisk Selfcheck gets all green. So good so far.

After disabling the NanoDroid module in Magisk and reboot I would expect to see the original system, but this is not the case. Either this is a bug or something I don't understand. Can someone enlighten me?

What is happen: I see the icons for Google and Playstore again, but a message "3 is continously stop". In /setting/apps I found that app "3", it has version 0.2.12 ... so this is the microG-GmsCore, which seems to be still active. Also original Playstore has FC.

Also I still can see in Apps DroidGuardHelper which I don't would expect there.

On settings there exist a new entry "3" where usually are the Google settings.

After re-enabling in Magisk the NanoDroid Module it seem to work again. Selfcheck all green and in /settings I get the MicroG Settings as an item (where before it was the "3").
[Magisk] rasputin_g:
You need to install the uninstaller as a magisk module to fully remove it.
[Magisk] starbright_:
What is still not understand: Why installation of Nanodroid works if ROM has not been debloated (so Velvet, GmsCorem ...) still in ROM - but not if it has been removed. before That is weird.
[Magisk] raptorddd:
please help using stablr build. using this

nanodroid_microg=1

nanodroid_fdroid=1

nanodroid_apps=1

nanodroid_play=10

nanodroid_overlay=0

nanodroid_mapsv1=1

nanodroid_init=10

nanodroid_gsync=0

nanodroid_swipe=0

nanodroid_forcesystem=0

nanodroid_nlpbackend=1000

nanodroid_bash=1

nanodroid_utils="findfs findmnt hexdump lessecho lesskey lsblk lscpu lsipc lslocks lsns ncal whereis"

my playstore dont show installed apps or any updates available to my apps.?
[Magisk] zkoz:
Unfortunately for me too. in addition, I cannot download previously purchased applications. Aqua mail cannot see the purchased license.

Is mentioned in the documentation about playstore issues in Android 10
[Magisk] Setialpha:
Did you try the proposed fixed?
[Magisk] raptorddd:
for me purchased apps works.

just theres no apps in installed tab and on update tab i press refresh and doesnt do anything.

yes am on a10
[Magisk] raptorddd:
ok ive read full documentation.

am on miui12 a10 playstore doesnt have a way to allow permissons. like says needs phone and storage

theres no permissons tab on playstore but other user apps have it. i dont know if its rom or a10 related.

my problem is no apps onstalled or new updates available.
[Magisk] zkoz:
Me? I think yes I did. I ran script to delete runtime-permissions.xml.

But this didn't fix playstore paid app.

Surprisingly, there is no more dferh01 error :)
[Magisk] starbright_:
Is there an example to workaround the missing setting-wizard?

I just used the microG edition and it installed Aurora too. In general no problem, but versions above 3.2.4 doesn't work for me and removing that manually is challenging as it seems to be non-deinstallable system app.. At least if you want to install an older version afterwards. As for me I would include just that what can't be simply added with FDroid and microG-repo.

Just my 5 cent, but thumbs up to the work of [MENTION=4187311]Setialpha[/MENTION]!
[Magisk] tek3195:
Edit installation file to not install aurora, then install version you want later.
[Magisk] cHECKjAM:
the big difference between nanodroid and lineage4microg is that you get to choose your packages more or less with nanodroid?

I also wonder if there is a good list of what all the packages do.. Like the "google" package etc.. Cant seem to find the details about that
[Magisk] zelleb:
https://gitlab.com/Nanolx/NanoDroid/-/blob/master/doc/Packages.md
[Magisk] cHECKjAM:
perfect, thank you.. I was looking in the website only.. Not a pro in this..

So do you know the difference between using this and the lineage4microg ?

My end goal is to use Lineage 17 on my phone, with only f-droid and a few packages from aurastore for banking apps and important apps only.

Not planning to use any google features or google play store purchases or anything.. I just want that these apps that require Google play services etc.. actually runs and works.

What is the minimal things needed then? Patcher only? Or I need the microG packages as well for this?

Also patcher says "when Magisk is installed it creates the NanoDroid_Patcher module and install the patched services.jar there", Does this mean I should flash magisk first and then patcher?
[Magisk] tek3195:
I've used both NanoDroid and Lineage4micro-g and a mixture at one point to install patched play store on Lineage4micro-g. It seems to me that if you want to install Lineage and your device has official support you should go with Lineage4micro-g. Makes more sense to install with it built-in rather than install ROM then try to patch and install to get same results. I would do it in one shot and permissions are pretty much handled. Smoother experience.
[Magisk] Setialpha:
Whether LOS4uG is an option depends not just on your uG usage or availability. AICP has several features/settings I've grown qccustomed to, so I'm not going to throw them away. It is, of course, the easiest option.
[Magisk] Setialpha:
For those with issues regarding Play Store app purchases, see:

https://gitlab.com/Nanolx/NanoDroid...lay-store-does-not-show-bought-apps-as-bought
[Magisk] starbright_:
Does Radiocell backend works for you? In MatLog I see: "JSON data was null" - both online and offline. I don't get position, while it works with "Local GSM location" backend. Mh.... I am on Oreo.
[Magisk] SkyeNymph:
So I mentioned a problem with getting microg to notice my location, as well as a issue with microg not getting permission to get location in the background on 10. I ended up deleting /data/system/users/0/runtime_permissions.XML using TWRP's file manager (after an attempt to edit it to manually add it the missing permission that resulted in a bootloop) and after a reboot both issues were resolved. I have not noticed any issues aside from having to grant several apps permissions again. I doubt this is a good solution but I thought I would post it, in case it helps.
[Magisk] ubuntiger:
That's what I did. In detail like this:

Install official 17.1, start and do basic setup

Install Magisk and start LOS again.

Install patcher. Patcher will automatically be installed as a Magisk module, as it detects Magisk. (Don't recall if I restarted LOS before the next step, but is does not hurt.)

Install NanoDroid. Unless you apply a special config (see the NanoDroid Readme), it will also be installed as a Magisk Module.

Make sure to grant Signature Spoofing Permissions to MicroG Services Core in Settings > Apps & Notifications > microG Services Core > Permissions > Additional Permissions > Signature spoofing > Allow

After installation of MicroG (as part of the installation of NanoDroid)

This most likely can only be answered in detail by the initiator of this thread.

However, if you installed Magisk before, the patcher installs itselves as a module of Magisk, and at least the formal aspects are different. Whether the core algorithm is the same as for LineageMicroG - no clue.

The Magisk method has the advantage that you can uninstall it easily, Magisk as well as modules inside Magisk, as Magisk acts as a layer between your LineageOS and the modules.

And Magisk acts as a provider of root rights (checkbox inside it to activate / deactivate).

There is close to no good chance any more to have root rights otherwise in LOS 17.1, because the addonsu of LOS16 doese not work any more, see the LOS docu.

You should read the Magisk doku on the "root" topic anyhow. It explains many things and problems of "normal" rooting.

The modules are installed "in the layer".

If you remove the "layer", i.e. Magisk, you remove the modules as well and you are back to your plane LineageOS.

But you can also leave the layer and just remove the modules.

Actually I would not bother too much about this aspect, have read numerous articles on this, and my conclusion is: There are many more severe risks around in your computer / mobile / online world than this one. One of them is your router at home. So I do not bother on that comparably small SigSpoofing risk.

But with the solution to install the patcher and NanoDroid both as modules of Magisk you can easily uninstall the modules, i.e. you have your own choice and can take you own decisions.

Not sure if I understand your question correctly, but I think: No.

Install 1. NanoDroid_patcher, 2. NanoDroid, both after installing Magisk, then you automatically will find these two as Modules in Magisk if you do not manipulate the default settings of Nanodroid.

Just curious: Your mobile is a Samsung Galaxy S5 which just got 17.1 newly? Or something different?
[Magisk] Stogie87:
Hi there,

would it be possible to provide the previous beta of Nanodroid MicroG?

It was the best working version for me...
[Magisk] rasputin_g:
When will the signature spoofing patcher support android 11?
[Magisk] Pac-Man:
Since the Aroma installer is not available anymore, how can I select what I want to install or not from the NanoDroid package?
[Magisk] d1n0x:
By first reading the documentation
[Magisk] Pac-Man:
If I asked is because I didn't find anything in the documentation.

But thank you, I'll look again to see the same as yesterday :good:
[Magisk] Setialpha:
Unlikely, pressing on Installation will lead to the docs where the first topic is Installation Setup.

https://gitlab.com/Nanolx/NanoDroid#installation
[Magisk] Setialpha:
Dunno, on A11 the linker setup currently doesn't work.
[Magisk] hraisins:
Installation through TWRP failed (logs attached), installation with Magisk Manager did succeed, but didn't pick up configuration (on external SD), so installation is somewhat bloated now.
[Magisk] Setialpha:
What's the mount path for your external sd when in ROM?
[Magisk] Setialpha:
A dirty flash for updating is OK, only upon the first time a full clean flash is recommended. Everything that's inside .nanomod-overlay will be pseudo-debloated. So remove everything you want to keep.

The file handling inside the installer has been changed, nothing that should bother you. More detailed info in the next, separate post.

If the old patcher works for you, you don't need to update it, but I've fixed several bugs meanwhile. Though when in System Mode the uninstaller only correctly restores services.jar if at least patcher 10.0 is used. If you don't install in System Mode or don't plan to uninstall NanoMod that does not matter.

Did you follow the setup instructions for microG? I guess not, because it's working normally after microG is setup. The 'No Google Play Services available' message is a huge indidcator that miroG is not setup. Check the docs.

I've never had insta-lock with UnifiedNlp (which is part of microG), so I suppose that's normal-ish.
[Magisk] kurtn:
Yes. Location mode "battery saving" 6 seconds from tapping the maps icon to correct location with 100 m radius.
[Magisk] Setialpha:
For the next beta the handling of the file

/system/.nanomod-patcher

by the full and microG package installers will change. This file is created by both NanoMod's on-pc and on-device framework patchers after successful patching of services.jar. When installing NanoMod in System Mode everything was fine, but in Magisk Mode the state of the file was not always correct. This is fixed in todays commits. So now let's get into detail:

Flash ROM

Flash Magisk

Flash NanoMod (initial run)

Reboot ROM; back into TWRP

Flash NanoMod-Patcher / Use framework-patcher.sh

services.jar patched and /system/.nanomod-patcher is created

So far so good, nothing different as before, but now.

a) ROM Update

ROM Update will remove /system/.nanomod-patcher

NanoMod installer now sees that the Magisk Module has services.jar, but /system/.nanomod-patcher is missing => tells user to re-run NanoMod-Patcher, drops previous services.jar to prevent (rare but possible) boot-loops because of incompatibilities between the two services.jar versions

b) NanoMod Update

if Magisk Module has services.jar and /system/.nanomod-patcher exists the patched services.jar will be backed up and restored during installation, no need to re-run Patcher after NanoMod Update anymore

if Magisk Module has services.jar but no /system/.nanomod-patcher exists, assum ROM Update and proceed as mentioned in a)

c) wiping dalvik-cache

no effect on patched services.jar

d) updating Magisk

no effect on patched services.jar

So the new behaviour should now be what everything (well, or at least: most) users expected right from the start. The setup variable nanomod_reinstall has been dropped, because it's no longer required.

I also revised mod.sh, which is now called build-package (a script that allows you to create snapshot builds from the git repository).

I plan on revising the documentation, too, but my time is limited, so if something feels like helping out, you're welcome.

The next beta will possible be released on thursday. If you want to test right now, checkout the git repo and use build-package to create a snapshot build.
[Magisk] finalista:
Unfortunately I did not find the .nanomod-overlay file. l installed the nanomod microg package as magisk module and looked in the directories stated in documentation /sdcard /persistent and /data but no luck. Maybe someone can point me to the right direction ;)
[Magisk] Setialpha:
It's not there, if you didn't create it. You'll find the example file in the docs, modify it and copy it to your device.

https://gitlab.com/Nanolx/NanoMod/blob/master/doc/.nanomod-overlay

In fact running nanomod-overlay script on the device would create the file, based on what was done during installation, if no config is found, but that's broken until 11.2-beta1.
[Magisk] kurtn:
Did the build-pakckage full. Wiped everything, flashed AEX, Magisk, Nanomod. Most things look reasonable, but I don't get a checkmark at microG Self-Check "Playstore has correct signature" and "UnifiedNlp is registered in system". Starting Playstore makes "microG Services Core has stopped". Lightning has FC at start.
[Magisk] demonoidmaster:
Tried the new beta, disabled the zelda sounds, enabled sync and disabled fdroid in the config file, booted up fine except i can't find wherever microg settings is to set up the other stuff

Skipped using the patcher because it doesn't work, as for signature spoofing i don't think Resurrection Remix has such a thing in it so anyways for me it seems this module won't work no matter what i do
[Magisk] abacate123:
Have you flashed the framework patcher (after boot once in the rom)? The signature failure is usually because of that.

About the UnifiedNlp, have you configured/selected the UnifiedNlp at microG settings and rebooted? If you did those steps then I don't know what could it be, maybe a beta bug.
[Magisk] demonoidmaster:
Update, flashed 11.1

Ok

Still no microg settings app

Flashed the patcher though, works now, so that's good atleast, though i don't see no 'spoofing signature" in Settings -> Apps -> gear icon ->

Opened YouTube, works fine, gmail too

Playstore though just won't budge
[Magisk] Setialpha:
PlayStore: go to Settings > Apps > Gear Icon > App Permissions > Signature Spoofing > Enable for Play Store

Lightning: that's a bug not related to NanoMod, it happened to me, too in AOSPEX builds before they switched to new WebView.

UNlP: that's an issue a handful users across all ROMs have, not NanoMod related. Still, can't say anything without a logcat.

microG Settings are found in the Launcher, not the System Settings.

The permission is only visible for pre-patched ROMs, nkt self-patched.
[Magisk] ShiShTuBaBu:
I am getting this error. I clean flashed ROM and everything did by the instructions of the doc.

But in the setting I wasn't able to check this.
[Magisk] Shadow53:
You'll need to manually grant the signature spoofing permission to the Play Store. Look back a few messages for how to do that.
[Magisk] ShiShTuBaBu:
thanks, that solved my issue :)
[Magisk] demonoidmaster:
That's what i meant by microg settings, was nowhere to be found either in the launcher or homescreen, just wasn't there

Also everything worked ok except the Play Store refusing to connect, tried removing my google accounts and then adding them back, that's when even that would fail to connect, so idk why but I've given up on this, gone back to opengapps pico because either ways it doesn't have much battery drain so, biggest culprits are Facebook (replaced it with Simple Pro) , Messenger (Facebook messenger) and snapchat

Js but for this you should maybe split the full zip, microg only zip, fdroid zip into 2 zips, one for system, one for Magisk only module (v4 template)
[Magisk] Setialpha:
There's no reason to split. If it does not work, I need logs. From recovery and logcat. I can't help you with nothing to look at.
[Magisk] demonoidmaster:
Already did that awhile ago, but eh rn I'm back on opengapps so i can't post newer logs sorry
[Magisk] Setialpha:
Ah yes, sorry, currently digging through everything. Will post back soon™.
[Magisk] demonoidmaster:
Disregard my logs from a few pages back as i don't think they'll be of any help ..
[Magisk] vladniko:
So my google inbox and Reddit app will not deliver notifications right away. Is this because gcm is set to 300s?
[Magisk] Setialpha:
Yes, that means it checks every 5 Minutes for new notifications.
[Magisk] Setialpha:
For those having issues with /system mounting from TWRP, I've updated the CommonInstaller in git repo, you can test using the new version by removing the one from the zipfile and adding the one from the git repo instead.

gitlab.com/Nanolx/NanoDroid

Or wait for a new beta build soon.