yashsingh1/xdaforums huggingface dataset:
[Magisk] den5o:
Yes all my installations are with overlay disabled. I had no issues with omni 9. It's very peculiar why this issue is present with 10
[Magisk] AnonVendetta:
I'm having an issue with NanoDroid-patcher-22.5.1.20200102.zip. My steps:

Wipe and clean flash ResurrectionRemix-M-v5.7.4-20161126-trltexx.zip (Marshmallow) from TWRP (latest recovery IMG from twrp.me is installed). No other zips are flashed.

Reboot into ROM, let it sit idle for 5 mins

Reboot into recovery, make a backup of services.jar, try to flash the patcher zip. After a few mins I get patching failed, error 1 (I think that was the error code). I noticed /data/adb is empty (the patcher didn't place any files there, and Magisk is not installed).

The previous stable patcher worked fine. Maybe I should use that for now?

I did make a copy of recovery.log, I'm attaching it to this post. Thanks for any help!
[Magisk] atirage21:
After install last nanodroid from january 2020, i have troubles with updating of apps in Google Play, wich always crash. Android 9, Xiaomi Whyred with last firmware v11.0.3 and with nanodroid from october was not problem.
[Magisk] Diresh:
From your log

Signature|privileged permissions not in privapp-permissions whitelist: {com.android.vending: android.permission.START_ACTIVITIES_FROM_BACKGROUND}

You can try adding the missing permission, or maybe try installing nanodroid without play store
[Magisk] den5o:
Thanks for the reply. How do I go about adding the missing permission?

I didn't try without play store, however it is not useful for me to do so.
[Magisk] Setialpha:
Could you upload your framework-res.apk from /system/framework? So I can fix the installer in that regard.
[Magisk] den5o:
View attachment framework-res.zip
[Magisk] ParanoidVisitor:
Is it possible to update Aurora Store to new build 3.1.7 ? Nanodroid microG make the app built-in ...
[Magisk] Andhika24kd:
In case you have root access, you can rename it to 'AuroraStore.apk' and move it to 'system/app/AuroraStore' (or priv-app), replacing an existing file. Otherwise, you need to make a flashable zip file (which I won't make it for you).
[Magisk] m_reyna_16:
Is it possible to use Samsung watch with a phone running nanomod? If so, what will work and what won't?
[Magisk] AnonVendetta:
Can I get a little help with the NanoDroid patcher issue I posted about in https://xdaforums.com/showpost.php?p=81381845&postcount=7696? I already attached the relevant logs, this is all the info I have.

Thanks!
[Magisk] :
Its different signatures from f-droid (the one from nanodroid) and the dev. You either have to wait for f-droid to verify the update, which takes roughly about a week or remove it, and install the apk from xda. Though using the apk from elsewhere bit f-droid will no longer allow you to update through f-droid.
[Magisk] imska:
I think ResurrectionRemix has native signature spoofing support. That means you should not need the patcher at all. The nanodroid systest did not seem to notice though...

When I flash it onto RR, it just does nothing and outputs to the log that the rom already supports signature spoofing.

The only way I can explain the stacktrace in your log is that is possibly has something to do with the (un)installation of magisk. Maybe a reboot after uninstallation would have prevented that?

Anyway, with RR, no need for the patcher. But you could check when RR started to include the microg patch that lineage refused to include (without valid reason). Maybe your rom version is older
[Magisk] m_reyna_16:
Anyone?
[Magisk] AnonVendetta:
[MENTION=6872152]imska[/MENTION]: No, you're wrong,and I'll explain:

Yes, RR does have native signature spoofing support...but not the Marshmallow versions. RR M is based on CyanogenMod, but RR Nougat and higher are based on Lineage.

I installed Lanchon's Signature Spoofing Checker app from F-Droid,it reports no spoofing support. I also tried installing the MicroG GMS APK from the project's official website, again no spoofing support present. And, just to be sure, I also exhaustively checked my ROM's Settings app, no mention of spoofing anywhere and no option to enable it. So, in my case, manual patching is necessary.

To clarify, I did not install Magisk while flashing the ROM, and after rebooting into TWRP I only flashed the patcher zip. However, I did flash Magisk and Xposed after patching failed (so I could temporarily use the FakeGApps module to enable spoofing). And when I said that /data/adb was empty, I mean that the folder was present but empty (before flashing the patcher zip and before Magisk). This folder is generated during the first boot of the ROM, but the Magisk zip can manually create it if not present. I assure you that, stacktrace or not, Magisk has nothing to do with my issue.

And, as I've already stated,the old patcher zip from October 2019 works fine, but the new one doesn't. The issue is clearly with the patcher zip itself. I would like to formally report this issue so that [MENTION=4187311]Setialpha[/MENTION] can investigate it, but I'm not sure where, so I'm posting here instead.
[Magisk] x8LHiiIB:
Try using the beta version
[Magisk] ghoppa:
Hi x8LHiiIB!

Thank you, it actually worked! I didn't think about that, the simplest solutions are always the best! :D :highfive:
[Magisk] Setialpha:
Version 22.5.2 with some bugfixes will drop this weekend. The curious can check the ChangeLog https://gitlab.com/Nanolx/NanoDroid/blob/master/ChangeLog.md

Also version 18.3.13 of the patched Play Store now in the repo.
[Magisk] SH1M4BD3:
Anyone has alternatives way to make your contact synced, at least displaying whole stored contacts on Q

As now on gsyncstuff not supportedyet??
[Magisk] azakosath:
You can extract sync adapters from a gapps package and make your own magisk module.
[Magisk] d1n0x:
Why don't you just manage your contacts offline? You don't need to give these personal details to Google
[Magisk] hertzschi:
Or one can use DAVx5 with a trustworthy carddav provider.

That's what I do.

Same result more privacy,more security
[Magisk] piet8stevens:
Agree. DAVx5 works really well. Also for calendar.
[Magisk] wee2000:
I'm a first user of MicroG. My aim is to install my preferred apps(Whatsapp/Youtube/banking apps) with minimal resources used, thus i planned to ditch gapps.

Installed magisk, then NanoDroid-microG-22.5.1.20200102.zip on my sony XZ2 running a freshly installed Omnirom 9.0.. After successful installation, i found the microG in my apps tray, with Aurora store.

Downloaded all apps using aurora store, but when i run it(ie : whatsapp/youtube), it has error 'google services not supported by my device'. So i assume i don't have google play services installed. May i know to get thru this? In the MicroG self-check, all of the other boxes is ticked, but there's one grayed out checkbox(the 7th one) stating 'Either the installed Play Store(Phonesky) is not compatible....'

I don't see an app called Phonesky in my menu.
[Magisk] kurtn:
[MENTION=1179365]wee2000[/MENTION] install fake store
[Magisk] dhacke:
Or Play Store.
[Magisk] wee2000:
Yes, but how do i go about installing fakestore or playstore? is it by :

- installing apk?

- flashing from twrp?

- or flash from some other apps like magisk?
[Magisk] bigsatan:
Google Play Store for microG is available in f-droid repo
[Magisk] dhacke:
I reply here now to avoid even more off topic in OmniROM thread from MartinX3.

Regarding your question: Both can be installed with Nanodroid which means twrp.

It has the possibility to install the modified play store but not by default.

In the NanoDroid packages is a file named 'nanodroid-setup'. And in this file you can find the mentioned line.

I would be glad to know what stands after '=' in this line.

Edit: Ups i believe i have a little typo in my last answers. The line is named as 'nanodroid_play' not 'nanodroid-play'.

At least after that page:

https://github.com/Nanolx/NanoDroid/blob/master/doc/AlterInstallation.md

Sry when i confuse you.
[Magisk] x8LHiiIB:
When installing nanodroid, did you select "install aurora + fake store"?
[Magisk] dhacke:
As far as i know only FakeStore or the patched Play Store is called 'Phonesky' in the microG selfcheck.

Whether Aurora Store is installed or not isn't from interest for microG.

Or am i wrong with that?
[Magisk] x8LHiiIB:
OP installed aurora store so I'm gonna go out on the limb here and say he still wants it. Now, try to follow me here, the OP also wants the phonesky check to pass. So if you carry the one and add it to the...jesus. It doesn't take a rocket surgeon to connect the dots here...
[Magisk] dhacke:
Take a breath and keep calm.

It wasn't my attention to get anybody angry here. If i done it in your case sry.
[Magisk] ParanoidVisitor:
This is how to make Phonesky Play Store correct signature in microG Self-Check:

https://shadow53.com/android/no-gapps/faq/playstore-incorrect-signature/
[Magisk] x8LHiiIB:
Its all good man, didnt mean to come off so harsh. This forum is filled with self-proclaimed "experts", realing at the chance to correct any little factoid to inflate their little ego. It gets super annoying and frankly I can't stand it.
[Magisk] dhacke:
Don't worry. I didn't take it personally. I was just very wondered because i didn't understand the reason for your well let's say emotional answer yesterday.

Lets just carry on and forget about it:cowboy:
[Magisk] I5WsRcGXFSPHLBFtjNxBXkd2:
Nanodroid`s last stable patcher shows error and wont work when using it with this ROM: https://xdaforums.com/redmi-note-5-pro/development/rom-t3913242

I dont know if its patcher or ROM`s fault but I tried with two clean flashes to ensure that Im not doing anything wrong.
[Magisk] keyshooter:
Hi, I am unable to flash nanodroid patcher on Official Lineage OS 16.0 (trying on ROM from 2020-01-13) on Moto G7 (river). The zip fails just after trying to mount /system even if is already mounted, I have try multiple things, I don't know if is because of the way the ROM is installed or something I'm doing wrong. I install the ROM by sideloading it with adb sideload, after that I install Magisk 20.3 also by sideloading it, according to Magisk installer the package is install, and after installing Magisk Manager the Manager says is in fact installed, I have try sideloading the package, I have try flashing with Lineage Recovery and with TWRP, I have try patcher and the full package and they all fail just after trying to mount /system. The phone also has an AB partition system (don't know if that helps) I have try reinstalling the ROM multiple times, nothing of that has work, even the log folder that Nanodroid (full package) says it makes is nowhere to be found (says /data/media/0/nanodroid_logs but there is no nanodroid_logs folder when I enter there)

I hope somehow this can help and you can ask me to try different methods or stuff if you want to

---------- Post added at 03:26 AM ---------- Previous post was at 03:26 AM ----------
[Magisk] Noru29:
You can't use Nanodroid on official LOS, you need to install LineageOS for microG

But there's also another new way to test on Official LOS with Magisk: microG Revived (You can download it on official Magisk's repository)
[Magisk] keyshooter:
I see, thanks, I will flash LOS with MicroG then, I hope a ROM able to support nanodroid gets release, in the meanwhile this will work.

Sad I can't install those TLOZ sounds :'c, I know I can add them manually but is not the same
[Magisk] githyanki:
You can flash nanodroid after installation, just choose not to install MicroG, or fake store in setup.
[Magisk] Setialpha:
Since when? If you want to use microG on official LOS you need to patch the framework. Up to Oreo the NanoDroid-Patcher can deodex and patch, on Pie you need to manually deodex services.jar and can patch using the NanoDroid Patcher. Android 10 is not yet supported.

That other microG installer doesn't make any difference, as your framework still isn't be patched.
[Magisk] d1n0x:
Patching works for LOS Pie without any prior modifications, at least on OP5.
[Magisk] keyshooter:
Then how do you do that? I'm using Lineage 16 (Pie) and I didn't knew about the services step,you mean that if I do this step i can install Nanodroid Patcher and after that microg, bromite, etc etc etc?
[Magisk] Oswald Boelcke:
My device is a Samsung S8+/SM-G955F with LOS16 (not LOS for µG) with microG powered by Nanodroid. As stated above LOS16 / Pie cannot be patched by the Nanodroid patcher. I use the Smali Patcher for this; works easily and perfectly.
[Magisk] d1n0x:
Yes it can. LOS is deodexed by default. I don't know if this applies to all official builds, but it is for my device.
[Magisk] Setialpha:
Official builds are odexed.
[Magisk] d1n0x:
Not for OP5 apparently
[Magisk] jackson_c:
Is it possible to install microg on the system and then disable root / magisk?
[Magisk] :
You can choose to install as magisk module or into /system, with a config file. You do not need magisk to install migroG zip. If magisk isnt present, it will automaticly install into /system.
[Magisk] J-Lindo:
Here's a question. Lineage for MicroG installs with MicroG preinstalled. First, I installed Magisk. I've flashed the Nanodroid uninstaller, uninstalled MicroG Core, then flashed Nanodroid MicroG, which correctly installed as a Magisk module instead of going to /system.

My question: will updating LOS for MicroG keep MicroG systemless, or will it try to install it to system, giving me both system and systemless?
[Magisk] :
Aslong as you flash magisk after updating, I belive you should be fine.

But why do you insist on having microG as a magisk module? Its already in the rom. Why bother with the extra steps?
[Magisk] J-Lindo:
My Galaxy S5 isn't passing SafetyNet, so I was experimenting to see if changing MicroG to systemless had any effect. It didn't.
[Magisk] :
This is a known issue, after google redid how safetynet works.
[Magisk] J-Lindo:
Ohhhhhhhh. Thank you.
[Magisk] Setialpha:
I know I've promised a new bugfix build last week, instead a new beta will drop tomorrow. ChangeLog: https://gitlab.com/Nanolx/NanoDroid/blob/master/ChangeLog.md
[Magisk] d1n0x:
Thank you. Will "add more permission to privapp whitelist automatically (0xc212)" fix the location permission issue on Android 10? (Permission isn't granted unless MicroG Settings is opened)
[Magisk] keyshooter:
Any particular reason for the Zelda removal?
[Magisk] Setialpha:
Nope.

I've decided it's out of scope for this project. I may upload them separately.
[Magisk] keyshooter:
Agree ? yet, yes, please and thank you about the separately package. Hope so.
[Magisk] keyshooter:
So I try to deodex services.jar on Lineage OS 16 (Pie) and for whatever reason it doesn't get deodexed? Patcher fails on services.jar which is weird, I follow all the steps, was using vdex and I use the Compact Dex Converter instructions with the tools/deodex/run.sh script to get the dex file and zip it in the services.jar and I did the chmod chown thing (on the phone, yes) but nothing, when I try to flash patcher it fails on services.jar.

Also this Lineage version is constantly getting updated because is pretty new for my phone so probably it will have tons of bugs, does the updates kills the deodexed services,jar?
[Magisk] Setialpha:
NanoDroid 22.6-beta1 (22.5.90)

Hi everyone,

version 22.5.90 (= 22.6-beta1) is now available for testing.

Highlights

Zelda Ringtones have been dropped, a few shell utilities aswell (will upload the ringtones separately)

Google Sync Adapters and Swipe Libraries have been moved into new NanoDroid-Google package

microG package reduced from 64 MB => 42 MB

Full package size reduced from 406 MB => 364 MB

fix dexpatcher crashing

fix bootloop on Android 10 (related to privapp-permission whitelisting)

prevent installation of Bromite System WebView on Android 10 (not yet supported)

Full ChangeLog

## 22.6 beta-1

### Bugfixes

* Installer
* add more permission to privapp whitelist automatically (0xc212)
* fix bootloops on Android 10

* Patcher
* fix dexpatcher crashing

* Bromite System WebView
* Bromite System WebView will support Android 10 starting with version 80
* disable installation of Bromite System WebView on Android 10 for now

### General Changes

* Full Package
* replace Face Slim with Frost
* users will be auto migrated
* no longer ship Substratum
* no longer ship Orbot
* no longer ship GNU Nano Editor
* use 0smosis' GNU Nano flashable zip
* drop the following shel utilities:
* col
* colcrt
* colrm
* look
* setterm
* no longer ship Zelda ringtones
* break-out Google Sync Adapters and Swipe libraries into NanoDroid-Google package

* microG package
* break-out Google Sync Adapters and Swipe libraries into NanoDroid-Google package

* Google package
* new package which includes Google Sync and Swipe libraries

* Patcher
* for SDK 19 - 25 use dexpatcher 1.6.3
* for SDK 26 and newer user dexpatcher 1.8.0-alpha4

* SetupWizard
* remove Nintendo Fonts entry (no longer available)
* set Aurora Droid as default F-Droid client
* update for recent changes

### Updates

* automatic
* Aurora Store (3.1.7)
* Bromite System WebView (79.0.3945.123)
* F-Droid (1.8-alpha1)
* Privacy Browser (3.3)
* Simple Calendar Pro (6.8.3)
* Tor Browser (68.4.1)

* manual
* Google Play (18.4.45)

* tools
* dexpatcher (1.8.0-alpha4-snapshot)

Download links

Download from Nanolx.

Bug reporting

In case of errors, please provide

/data/media/0/MODID_log_INSTALLDATE

/data/media/0/MODID_twrp_INSTALLDATE

SysTest package logfile

logcat (if applicable)
[Magisk] keyshooter:
Trying to flash patcher fails trying to backup the services.jar file

<< backing up services.jar to: /data/media/0/nanodroid_backups

!! failed to backup services,jar

I check if data was mount and it was, I try to look for logs in the suggested folders but non of those folder were found.

I don't know if is something on my ROM or some mismatch on folders
[Magisk] den5o:
Just installed the beta and there is no boot loop this time on my oneplus 6 running the latest build of omni rom.

There is however a different issue that I'm not sure if nanodroid or the ROM is at fault.

In microg settings I can allow signature spoofing for microg. When I check the spoof signature permission in the settings app it says "0 of 0 apps allowed" and I am unable to allow spoofing for play store.

Heading back to microg self check it registers as allowing spoofing for microg.

Very confusing as to what is actually going on. How do I go about manually allowing spoofing for play store?
[Magisk] NamitNayan:
su

pm grant com.android.vending android.permission.FAKE_PACKAGE_SIGNATURE

(In a terminal app)
[Magisk] J-Lindo:
Thank you! Will this install as a Magisk Module?
[Magisk] lordsolrac2:
I'm having trouble with Signature Patching. I'm on LOS17, one which is hoping to become official, so no sig spoof support. I've tried a few options, Haysack and Smali Patcher, and neither support Android Q, sadly neither does the current beta (20200119). So, with that said, instead of asking for an ETA, is there anything we could do to help with a possible porting? Be it APEX or Dex?

Or is it already implemented in a commit that might not have a build?
[Magisk] d1n0x:
[MENTION=4187311]Setialpha[/MENTION] is your NanoDroid repo down? I can't find Google Play Store in F-Droid anymore after a clean install.
[Magisk] Setialpha:
No. But F-Droid no longer auto-adds it. You'll have to add it manually.
[Magisk] atirage21:
So i understooded more this problem. Google Play 17.9.17-all from nanodroid is OK, but after update through F-droid to version 18.3.13 was started problem with google api.

---------- Post added at 07:41 AM ---------- Previous post was at 07:39 AM ----------

Maybe it is associated with big changes in google api about process of updating. https://www.gsmarena.com/google_pla...notifications_for_updated_apps-news-41053.php
[Magisk] TeLow:
Hi,

I cannot grant signature spoofing for the fake store in the work profile.

What I tried is:

Run the npem command in a root shell in the work profile.

Setting the system app privilege in the app permission manager.

Problem is that in the permission manager's signature spoofing tab, its the only tab that does not have the three dots to show system processes, so I can't get the fake store to show up. In android 9 the option was there and you could set the permission for the normal and the cloned work profile fake store.

Is there a third way?

Cheers!
[Magisk] :
Try this one. Perhaps this one works.

Su
pm grant com.android.vending android.permission.FAKE_PACKAGE_SIGNATURE
[Magisk] TeLow:
Hi,

tried that, no change...
[Magisk] den5o:
Performing microG self-check results with UnifiedNlp not registered in system.

nanodroid beta on oneplus 6 with latest omni 10 build
[Magisk] :
Aslong as it works, dont mind it. Its like that on op6 and other devices, but works none the less.
[Magisk] d1n0x:
I guess it's a problem with Omnirom, it was the same on Pie. They never bothered to fix it
[Magisk] :
No, its not an omni problem, its like that on all roms on op6, and other devices aswell. Im my vague memory, its something related to qualcom location service. I dont remember the specifics, but tbh, it doesnt matter, 'cause location works despite unifiednlp not checking in self- check list..
[Magisk] FriendlyNeighborhoodShane:
Hello! Does the NanoDroid FDroid repo seem to be down?
[Magisk] Oswald Boelcke:
One page/two days/10 posts back: https://xdaforums.com/showpost.php?p=81548589&postcount=7764
[Magisk] wackendf:
Hi

I am running a Poccophone with LOS 16. (Android 9). And I don't know how to deodex it manually.

This tutorial

https://gitlab.com/Nanolx/NanoDroid/blob/master/doc/DeodexServices.md

is to complicated for me. Are there any tutorial videos or a tutorials with pictures out there?

Thanks.
[Magisk] d1n0x:
Why don't you just use Lineage for MicroG? No need to fiddle around with deodexing
[Magisk] urgali:
Maybe personal preference, I wouldn't like to be forced to use a rom instead of my favorite one, don't you agree?
[Magisk] d1n0x:
It's literally the same as LineageOS, just with MicroG
[Magisk] wackendf:
I didn't knew that there is a ROM available.

Is it possible to dirty flash the microG ROM on the existing ROM with the nanodroid package already installed?
[Magisk] d1n0x:
No. Coming from a different ROM you must always clean flash
[Magisk] wackendf:
Then I would prefer the deodex solution.
[Magisk] githyanki:
You can try smali patcher. I think that's the easiest way to patch in signature spoofing using an application.

I chose the clean flash to LOS with microg as I didn't want to re-do the patch for every update.
[Magisk] urgali:
You're right, I actually misread rom name, sorry for that
[Magisk] wackendf:
It looks like i have to install magisk. Is that correct? If so, is there an other easy way to deodex the device?
[Magisk] MajorBoobage:
I have a Rapahel device (Redmi K20 pro premium), running MSM-X custom rom Android 10, with magisk.

The rom supports signature spoofing, and doesn't come with gapps included (I have installed opengapps pico).

I tried using Nanodroid when I flashed the rom and couldn't get it to work no matter which guide I followed, and spent few days pulling my hairs out and flashing and reflashing.

Now my device is already configured to my liking and I use it as a daily driver and cannot afford down time of more than 12 hours.

Is there a way for me to reliably remove gapps and install MicroG on my existing rom without losing my data/settings?

Thanks.
[Magisk] FriendlyNeighborhoodShane:
Hello!

I have a question, not related to NanoDroid, but MicroG.

I'm trying to push a couple APKs and the related permission files to system by hand (well technically by script), and my current set of files work perfectly on Quack, but not Pie.

The apps I'm pushing are pretty basic: MicroG and components, Play Store, Aurora suite and backends.

On Pie's logcat obtained during bootloop I get zygote shutting down due to fatal error "permission ACCESS_WIFI_STATE is not a changeable permission type" and then it reboots to recovery.

I feel like the permission must be put somewhere in all priv-app's exception xml, but that didn't work either. Anybody has any ideas what's going on?
[Magisk] LovepreetSinghGill:
Fixed