yashsingh1/xdaforums huggingface dataset:
[Magisk] demonoidmaster:
Well, there's your answer, apks for android future revisions (nougat or such) don't work with prior android versions, logically, but you can go and find a GBT apk that's made for your 6.0.1 version, apkmirror might have it

PS: [MENTION=4187311]Setialpha[/MENTION] sorry about my rant, bit drunk so ain't got no filter on what i say rn, no hard feelings, <3 sorry . you're awesome though, take a look at my logs if you can
[Magisk] abacate123:
I know that's my answer, but not the solution I was expecting. That's why I'm reporting the issue (or whatever you'd call it) here to the developer so he could add it to the issues/limitation documentation or something like that. And marshmallow still the most used Android version out there tho (according to Google's graphics).

Anyways, I'll try later changing manually the apks inside nanomod's zip and see if it works. Thanks for your time :)
[Magisk] demonoidmaster:
I don't see how him having made his zips be using the most uptodate apks for an android version you're not running an "issue", but it is a limitation because you're still running MM instead of nougat

Best bet is replacing the non compatible apks in the zip with some made for your current android revision
[Magisk] Setialpha:
So it's GBT that's not working on MM? I'll check that. You reported about the SyncAdapters, so I did nothing, cause Google marked them as compatible with SDK 23 (= MM).

I personally don't have MM anywhere, plus I don't use GoogleSync.
[Magisk] Oswald Boelcke:
@fhLan: Thanks very much for your PM; however, I'd rather reply in a thread instead of a PM.

No, you cannot. It's not implemented into microG. Please check the implementation status here.
[Magisk] AndroidEJ7:
Is there anything special I need to do to update? Or just install normally with the same config file?
[Magisk] Setialpha:
Just install the new version as usual.
[Magisk] razr96:
Thanks alot for this, I have a few questions though.

Is it normal for google setup not to show up when using nanomod? I flashed the rom (RR), magisk and then nanomod-microg and fdroid. When I booted no setup was shown, it went straight to the launcher. It could just be the rom. A setup was shown when I used OpenGapps though.

Is 17 min a normal length of time for patching a rom? I patched after booting into it once. This is on a Lenovo P2.

Can I re-use a patched services.jar for the same rom? i.e is a patched services.jar always compatible for that specific rom zip file? I tried simply copying the patched services.jar into another install and it seemed to work.
[Magisk] Setialpha:
There's no setup wizard for microG.

The time required to patch depends on the device power, on my Moto X Play or Galaxy Tab 4 it takes about 7 Minutes.

Patched services.jar can be re-used on the same ROM version, on the same device, anything else can't be safely said beforehand. May work, or may not.
[Magisk] abacate123:
Yeah, it seems to be gbt's fault. I sent the zip I made and used attached above, which worked. I personally use the sync because all of my contacts are saved there xD
[Magisk] Anarchy16:
yeah, me too . only for contact :p
[Magisk] finalista:
Anyone else having the problem that after doze kicks in WhatsApp messages are only received if WhatsApp is excluded from battery saving or after opening the app? I'm using latest nanomod as magisk (latest) module with Los 14.1 from sultanxda.
[Magisk] abacate123:
I don't use whatsapp anymore ('cos it sucks), but anyways I installed here again to test the gcm, and it worked fine over here with my usage since I installed. And I didn't remove it from the battery saving.

Is your Google Cloud Messaging panel for the app (microg settings) like that on my screenshot attached?
[Magisk] finalista:
It's the same

I also tested with signal messenger. Same behaviour
[Magisk] birleytweet:
Hi thanks so much again. I found my NanoDroid backup was broken or for some reason can't restore.

If anyone can help me I'm willing to send you $50 either via PayPal, bitcoin or what you prefer.

Just as have already spent 5 hours trying to get this working.

I tried that command and it said all those had rhe signature already. If someone helps me get it working we can pm and I'm happy to pay, as theres a couple of crucial apps I need.
[Magisk] d1n0x:
su

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

Reboot
[Magisk] birleytweet:
Hi thanks I have tried that. Tried clearing cache and data for the play store then running the pm grant com.android.vending android.permission.FAKE_PACKAGE_SIGNATURE again.

In microg every box is ticked except the bottom one unifiednlp provides location updates.

I'm running crdroid on a oneplus 5t. After running the grant permissions command the play store shows my email address, but fails with the error DF-DFEREH-01

I'd had this problem last time I tried to update 6 months ago, so just went back to the old rom.

The play store was flashed as part of thr NanoDroid.

I'd say this is a common issue, for some reason on my old rom never had this issue.

If anyone has any ideas please let me know. If can solve it I'll send $50 like I said
[Magisk] carlos974:
Delete your google account.

Recreate your google account.

If the error is present, close the play store and then force the play store stop in parameter -> applications.

Then launch play store that should be good!
[Magisk] d1n0x:
Force close usually solves this for me
[Magisk] zuhero:
in app purchases dont work, any fix or woraround?
[Magisk] Estebanium:
Which App?
[Magisk] zuhero:
I installed the patched play store but any in app purchase from any app using the play store doesn't work.
[Magisk] flieswithhawks:
For what it's worth, I tried running crDroid a while back on my Moto X4 and was unable to get the spoof package signature to show up in Android settings and even after manually running terminal commands to spoof was still unable to get NanoDroid to work with the ROM.

May I suggest switching over to HavocOS as I have done. There are no issues with NanoDroid and all the features (including more if I'm not mistaken) from crDroid are present and working great.:good:

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

Have you checked that the spoof package signature in Android settings are allowed for microG as well as patched Play Store?
[Magisk] birleytweet:
Hi I believe signature spoofing was working, just issues getting the play store working. Had issues with crdroid killing the battery like crazy, so was able to revert back to my old ROM. I might try Havoc instead
[Magisk] zuhero:
Yep, signature spoofing is enabled, it shows in self check
[Magisk] Cerealekillers:
Hi!

Is the patcher (beta) is really working for all devices, I've installed Lineage OS 17.1 (official) and follow every steps (Wipes/Magisk/NanoDroid...) and the Patcher ended with an error 1.

Thanks.
[Magisk] birleytweet:
Hi thanks I looked into Havoc OS and looks like a better option. Do you have a link for the Havoc forum? The one for the Oneplus 5t is from 2018. I can find the sourceforge download link, but not the forum anywhere.
[Magisk] Mafioso:
First time nanodroid user here. I installed nanodroid microG beta package (04/18) on an old phone running nougat. I'm not getting chromecast button on youtube. I wanted to know what I was doing wrong as I read microG does support chromecast via youtube? Is there something I'm missing?
[Magisk] TRexombo:
A peculiar/unique situation?

Hello to everyone. Hope you are all doing good.

Recently I flashed a custom rom that is odexed on my OP6T and if I understand correctly, nanodroid patcher only works if your rom is deodexed. Is that correct? I tried it on the odexed rom and it failed even though the rom has signature spoofing support.

Here's the unique/peculiar part of the whole thing. I went ahead and installed magisk and then in recovery tried flashing nanodroid latest beta and it worked! Isn't it supposed to fail on an odexed rom?
[Magisk] d1n0x:
Why would you patch a ROM that already supports signature spoofing? O.o
[Magisk] Oswald Boelcke:
Negative, Nanodroid's modules are not supposed to fail on an odexed ROM, it's only the Nanodroid patcher that fails. And the Nanodroid patcher is an on-device framework-patcher (i.e. provides the signature spoofing support for ROM's without this support). In turn a valid question by [MENTION=3019922]d1n0x[/MENTION] why to use the patcher on a ROM that inherently already carries signature spoofing support.

I'm not wondering that the patchers fails but the rest works.
[Magisk] TRexombo:
Yessir, I can see why it's puzzling :laugh:

I normally would not want to patch a rom that already has SIG spoofing support but the rom comes with preinstalled gapps and whereas I didn't need it patched for signature spoofing, I was hoping I could run the installer at system level to remove gapps and install MicroG and all the open source apps provided in nanodroid.
[Magisk] d1n0x:
So then just flash NanoDroid. There is absolutely no reason to use the patcher.
[Magisk] TRexombo:
Oh yes, I understand now. For some reason I thought the patcher was included in Nanodroid. Before I installed magisk, from recovery I flashed the latest Nanodroid beta and it failed. I thought it was because the rom is odexed. Then, after I flashed magisk and ran nanodroid it was successful. :confused:
[Magisk] Bracher:
I have the same problem Fairphone 2 with Lineage OS 17.1 (official) and the patcher ended with error 1
[Magisk] Cerealekillers:
I used this script to enable signature spoofing, but it needs to be done after each update of the rom

https://gist.github.com/CHEF-KOCH/510cdac327c0132e550554a33e25baf4 or https://del.dog/hulycobanu.sh
[Magisk] laserkater:
Run from Linux terminal, with phone attached via adb.
[Magisk] Cerealekillers:
One one the last sentences "cp: write error: No space left on device"
[Magisk] TomRon:
.... Device is plain, there should be more than 100GB of free space available :confused::confused:
[Magisk] past_k:
nanodroid-Google package doesn't install anything by default. One has to edit/add a .nanodroid-setup file with e.g. nanodroid_gsync=1 in it. Is it by design? I'd expect it to install stuff by default, because that is why people download that package for.

Also I got an AEX losetup fails error while trying to install latest beta NanoDroid-Google-22.6.90.20200418.zip.

So I had to fix missing permissions.xml file in the "stable" package manually - it installed successfully after that.

Logs are not very helpful unfortunately:

NanoDroid_Google_22.6.90.99999999_twrp_.log - empty.

NanoDroid_Google_22.6.90.99999999_log_.log:

Installation successful: FALSE

### VALUES ###
ZIP=/external_sd/NanoDroid-Google-22.6.90.20200418.zip
ZIPDIR=/external_sd
TMPDIR=/dev/tmp
TMP_LIBDIR=/dev/tmp/nanodroid-lib
INSTALLER=/dev/tmp/install
MODID=NanoDroid_Google
SDK_VERSION=
ARCH=
LIB_ARCHES=
MODPATH=
SWIPE_LIBDIR=
MODE=
MAGISK_VER_CODE=
ROM_NO_XBIN=
NANODROID_UPGRADE=0
NANODROID_BINDIR=
HAS_FAKESIGN=
HAS_WEBVIEW=

### MOUNTED PARTITIONS ###

### PARTITION INFORMATION ###

DEVICE_AB=FALSE
VENDOR_COMPAT=TRUE
SYSTEM_AS_ROOT=FALSE
SYSTEMBLOCK=
VENDORBLOCK=

### DISK USAGE ###

I hope that helps and thanks for your great work!
[Magisk] flieswithhawks:
Short way ~15 mins

Step 1 - download latest .iso of Ubuntu

Step 2 - burn image to USB using this -> www.etcher.io

Step 3 - reboot into Ubuntu and open terminal

Step 4 - plug in phone and execute commands:good:

Long way ~???

Look into WSSL and run a terminal from inside Windows.

---------- Post added at 08:32 AM ---------- Previous post was at 08:28 AM ----------

Have you used the copypartitions.zip before you flashed your ROM when coming from stock? What slot are you flashing from A/B?

Also, have you setup a config file before using NanoDroid as is mentioned in the OP? Use the AROMA setupwizard zip if not
[Magisk] bkuri:
Actually you need to move the /etc folder inside the ZIP to /gsync/etc in order for the installer to work. HTH
[Magisk] amn1987:
After having used microG which was pre-built into the ROM I decided to try installing it manually in a different ROM. Other than not knowing intially that Play Store needed additional permission despite being installed as system app it went rather well.
[Magisk] FriendlyNeighborhoodShane:
Aha, Classic chef-koch. Kanging other people's work without credits.

EDIT: It's mine, originally posted in the microg subreddit https://redd.it/fywiix
[Magisk] TomRon:
copypartitions.zip: no, I didn't because I didn't know that I had to!

just did that what the installation howto said:

Source: https://gitlab.com/Nanolx/NanoDroid/blob/master/README.md#installation

NanoDroid

Use Setup Wizard to create configuration files (if you've got an arm/arm64 device), or create manually (see above)
Download pre-built zip or create one from this repository

Installing from scratch
This is the recommended way.

Stock ROM without GApps, custom ROM with/without OpenGApps
OpenGApps and GApps-less ROMs don't need further measurements, the Installer takes care of required steps.

perform full wipe (/system, /data, /cache, Dalvik/ART cache)

recommended, but not required

install desired ROM

make sure it does not include GApps if you want to use microG

NanoDroid tries to get rid of GApps on it's own, but it may not always work, try without any warranty

install Magisk

recommended, but not required
if Magisk is installed, NanoDroid will be installed as Magisk-Module, else it will install into /system directly

install desired Kernel (if any)
boot into ROM (for Magisk module installation only)
boot into TWRP again (for Magisk module installation only)
install NanoDroid

if you want to use microG make sure the ROM is either pre-patched with signature spoofing support or deoxeded so you can patch yourself see here

you can use the Patcher package to de-odex (up to Android 8.1) and/or patch services.jar (up to Android 9.0)

reboot into ROM

until the point Install Nandroid everything went fine...

I'm flashin A/B Custom Rom

setup a config file: no, where can I find the "OP"? OP = Full Documentaion?

Use the AROMA setupwizard zip if not.... is there any documentation on how to use this or just flash it via TWRP?

Thanks for the support!
[Magisk] flieswithhawks:
If you use the setup wizard before you flash NanoDroid it will allow you to choose what you actually install when you flash it.
[Magisk] TomRon:
ok did the Setup Wizard (AROMA) which was successful!

afterwards flashing Nanodroid still fails.

TBH... why is this installations step - creating config files for installing Nanodroid - stated under the chapter "Extras" (first Post of this thread).... for me is "Extras" something I CAN do optional not that this step is MANDATORY!... that's the reason I am asking this stupid questions....

what about this "copypartitions.zip", where to find this file, and how to use it? .... nothing specified in the documentation --> https://gitlab.com/Nanolx/NanoDroid/blob/master/README.md

Thanks for your help!
[Magisk] flieswithhawks:
[MENTION=5802280]TomRon[/MENTION]

I think you may need to do some more reading/research about things to better understand what it is you're trying to go about doing to your phone...

What's your reason for wanting to use NanoDroid in the first place? What device and ROM are you using?
[Magisk] TomRon:
Hello,

no doubt about that, sure I am willing to read/research, that's not the problem... It would be rather more convenient - for both us, I requesting for help and anybody else who is able to help- if all these things you have told me would be documented in the first place. I'm kind of RTFM type guy but this topic looks for me like a puzzle where I have to find all bits and pieces on different places.... but lets stop beefing around on this topic, it is as it is :good:

Reason: some of my personal required apps need to have access to google Playstore, but I dont want to have GAPPS on my phone due to obvious reasons.

Device: Blackview BV9800 (ARM64, A/B)

ROM: Havoc OS 3.5 Android 10 - no GAPPS

TWRP, and Magisk installed and working.

I started 2 weeks ago with the topic, flashing a custom ROM, TWRP, Magisk and now I'm at microG so the learning curve is actually quite steep and I want to get things accomplished.

Before that, the last time I did such similar thing is 6 years ago and in the mean time mostly everything changed.

Thanks for your help!
[Magisk] flieswithhawks:
I'm not sure I can be of much help at this point as I've explained things to you the best I know how. Perhaps someone else could word things in a way that's helpful towards your goals.
[Magisk] past_k:
Do I understand correctly that its possible to switch between microG and google services by enabling/disabling nanodroid modules in magisk in the following setup?

I.e. flash custom rom with opengapps and magisk.

Flash microG nanodroid as magisk module - it should pseudo-debloat (hide) google services and gapps and replace them with microG implementation.

Then if I want to temporarily switch back to google services I can just disable nanodroid magisk modules and reboot? And to switch back to microG just re-enable the modules and reboot again?

Will it work this way?
[Magisk] TomRon:
would be helpful if you could say something about something you mentioned before: copypartitions.zip

where to find it and how to use it?

Thanks
[Magisk] flieswithhawks:
I'm not sure for the device you have if it's even required or not.
[Magisk] TomRon:
Just FYI

I found the issue, it was indeed to less space on the system partition.

Resizing the system partition via TWRP solved the problem!

Thanks!
[Magisk] aeioo:
I am trying the patcher on unofficial Lineage 17.1 for Asus Zenfone Max (Z010D) and have patcher ended with error 1.

Anyone have idea about the problem of "/tmp/updater: line 48: /system/bin/dalvikvm: not found"?

After several hours of struggling, I gave up using the Nanodroid patcher.

Instead I have managed signature spoofing to work simply by manually patching services.jar with sigspoof-hook-7.0-9.0 and sigspoof-core using DexPatcher on PC running cygwin.

I have finally got microG working.
[Magisk] derschnelle:
Worked perfectly for me, thanks :)
[Magisk] Cerealekillers:
There is a new version of the patcher (beta instead of alpha) https://github.com/DexPatcher/dexpatcher-tool/releases/tag/v1.8.0-beta1 so the script need to be modified now if you want the newer version of the patch.
[Magisk] carolinaray:
nanodroid download website is taking 8 hours to download 300mb :(

nvm was probably my internet
[Magisk] Retseem:
Is Nanomod NOT possible when /data is engrypted?
[Magisk] starbright_:
What might go wrong if I get (LOS17.1) in selfcheck: Location service is not supported, UnifiedNlp is not registered? Is it a known LOS problem or a problem of Vendor, ROM or microG? (installed via latest stable Nanodroid)
[Magisk] knpk13:
I haven't used nanodroid in a while but I'm pretty sure you still need to patch LOS for it (as it officially does not support signature spoofing). There should be instructions for patching in the OP or you can find an unofficial LOS (or another) rom that supports signature spoofing or has microg installed already.

Edit: the conversation on this page right above your post also talks about patching in support for signature spoofing
[Magisk] starbright_:
microG and LOS 17.1 ?!?

I patched it with SMALI patcher and micoG reports to be spoofed. What I am wondering: I installed Fakestore, but seems not to have proper signature. BUT: I used that one from nanodroid (all that works in LOS 16 for me). I couldn't check permissions (to be spoofed) for Fakestore, as there is in SETTINGS/APPS/FakeStore - no permissions at all to be set. Is this a LOS bug?

Also strange:

Checking (general) permissions and look for spoofing: No apps - neither accepted nor rejected.

On the other hand microG Service core shows : spoof package signature.

This is confusing ?!? How does it look like for someone else with LOS17.1 ? Anyone experience?
[Magisk] CommanderSozo:
Stock Samsung One UI, No Google, Full S-Pen with Nanodroid?!

I really enjoy using a Samsung Note for the S-Pen experience, however, I would like to remove GAPPS and Google Play Services from said experience. Being completely new to this and desiring a Privacy-centered scenario, is there anyway to use Nanodroid to disable Google Play Services/Apps while still being able to use Samsung’s One UI with full S-Pen support? If so, how is this accomplished? If this is not possible, is there a way to disable GAPPS and Google Play Services from Tracking? Can WiFi Triangulation, WiFi Scanning and Contact Tracing be turned off, scrambled or fed disinformation on a Note 9 SM-N960F/DS model using Nanodroid? If so, would this require Root and TWRP to accomplish? Thanks for your time and any help that may be sent my way.
[Magisk] xdaM:
Picking up on the recent discussion: can someone say if there is any way to patch LOS 17.1 for good without having to repatch it on every ROM update, and, if there isn't, then how practical it is to keep patching it everytime, provided that I'd want the quickest possible solution and not to mess with any apps?
[Magisk] clewis.it:
I would use Magisk, edXposed, and Fakegapps in this case. Once everything is setup, you will be able to install updates to your ROM and just make sure Magisk is installed before you reboot. That should happen automatically also.
[Magisk] PoochyX:
Can someone help me overcome this error have seen it twice with latest stable f droid module and the latest beta I'm on havoc 3.6 GSI Android 10
[Magisk] flieswithhawks:
You first have to install via recovery or root explorer method to /system/product/app/webview and check the permissions to make sure they are correct.
[Magisk] carlos974:
Root explorer or MiXplorer method for me !

Works fine
[Magisk] Bracher:
Does FakeGapps still work on LOS 17.1? I've tried, I first installed Magisk, edXposed and Nanodroid microG after that tried to enable GCM via FakeGApps - unfortunately without result.
[Magisk] clewis.it:
It worked for me, though I installed fakegapps before microg. I'm sure you verified that fakegapps was activated in edxposed manager, too.
[Magisk] Bracher:
THANK YOU!!! It worked!
[Magisk] tek3195:
Is there an alternative to setup wizard. It freezes my Samsung Tab S5e at starting aroma installer and have to use adb to reboot recovery. Can the wizards config files be done manually and then flash the Nanodroid micro-G zip? If so a short run down on how ? I use nightly builds of Aurora Store and wanted this for the patched Play Store. Thanks
[Magisk] Keule-Tm:
Sure, edit the corresponding files with any text editor. You can find the full documentation here: https://gitlab.com/Nanolx/NanoDroid/-/blob/master/doc/AlterInstallation.md
[Magisk] Retseem:
I finally have NanoDroid working on my S9 with Android 10 (Latest Beta 20200418)

I assume the UnifiedNLP problem is still not fixed for Android 10, since none of the weather apps can get a location, except for the stock Sasmung weather app. All Navigation/Maps apps I tried had no problems though.

I've read that you have to grant fake signature spoofing for the PlayStore. that option is not to be found anywhere in the settings on my phone and also the pm grant command results in an error that the permission doesn't exist. Since my PlayStore is working fine and I can see and install my purchased apps etc. I wonder if this granting is still needed?

Also I would like to encrypt /data again, but for some reason the installer can't install NanoDroid if it can't mount /data, is there setting in the configuration file that I can set so I can install NanoDroid with encryption enabled?

---------- Post added at 14:08 ---------- Previous post was at 13:59 ----------

Another question: Can you have multiple location backends active and if yes, does the order of installation of them has influence on how it works? So is it using the first one in the list first and then continues to the next if it can't get a location with the first backend, or do they work in parallel? Athe moment I have Mozilla first and Déjà Vu second.

---------- Post added at 15:07 ---------- Previous post was at 14:08 ----------

Deleted, wrong thread.