yashsingh1/xdaforums huggingface dataset:
[Magisk] sexler:
Hey guys,

I got a basic question. I searched the thread for it but couldn't find an answer, but maybe I used the wrong word. So, sorry if I didn't find it.

What is the right way to update NanoDroid microG?

I used TWRP and installed NanoDroid microG first. After that I installed the NanoDroid patcher, also using TWRP.

Now, when I want to update to the latest version do I have to use the uninstaller first and install both packages again (mircoG and patcher) or can I just install microG again?

Thank you!
[Magisk] kurtn:
Just reinstall microG. There is no benefit in re-patching as long as the self check says "system spoofs signature"
[Magisk] sexler:
Thank you for your help! :good:

Is it possible to use F-Droid for updating microG, too?
[Magisk] kurtn:
Go to microg.org/downloads to get the f-droid repo and switch f-droid to unstable updates
[Magisk] utg1:
Hi mate, thanks for beta 3.

I forgot to tell you that if I keeping Playstore Daily Hygiene service disabled, my microG settings don't dissappear and I have no RH01 issue...so....I hope I've solved it.

Thanks a lot for your support. ;)
[Magisk] Spazturtle:
Found a bug.

If you flash Magisk and then NanoDroid and NanoDroid-Patcher then NanoDroid and the patched files get written to the Magisk image.

But the NanoDroid addon.d is alphabetically before the Magisk addon.d, so after a system update NanoDroid-Patcher will run first and it will write the patched files to /system instead of the magisk image.

To fix this the NanoDroid addon.d should be renamed to be alphabetically after the Magisk addon.d.
[Magisk] :
Now that's interesting, I'll test it the next time I get the chance. This command is for the android terminal or do I have to connect my phone to my PC?
[Magisk] Mynacol:
You can use the commands either with a terminal emulator with root privileges or

You can use your PC and get an adb shell with "adb shell" and enter there the commands.
[Magisk] guest4711:
You may run it on terminal after switching to root (by running "su" or prefixing the pm command by "su -c", e.g. "su -c pm grant ...")
[Magisk] Setialpha:
Did you wipe /data? addon.d does not rely on Magisk, only on magisk.img being available.

I'll have a look. Could you provide a recovery.log from addon.d/ROM update?
[Magisk] hungvip2001:
A bad new: Google blocked uncertified device to use GApps

https://www.xda-developers.com/google-blocks-gapps-uncertified-devices-custom-rom-whitelist/

Is this a problem for microG ?
[Magisk] kurtn:
It is for sure no problem for microG. Most problems will be with play store. If you really need that it is maybe better to use GApps. With some privacy enhancement.
[Magisk] Setialpha:
I doubt, it's related to Android ID and CTS (you pass with Magisk and DroidGuardHelper, meaning Play Stoe sees itself as certified), plus you can unlock yourself, a free Google Service for Custom ROM users, may be that a change in microG ciuld be required for that, but I dunno.
[Magisk] cristihan:
[MENTION=4187311]Setialpha[/MENTION] First of all, thank you for your great work !

I installed LineageOS 15.1 on my serranoveltexx device. (galaxy s4 mini - i9195i). I tried to flash the NanoDroid patcher stable version and last beta version and every time get the same error (attached). On the same device I had installed LineageOS 14.1 and I did not have any errors with NanoDroid patcher. Am I doing something wrong ?
[Magisk] inVain_theGenuine:
I'm on NanoDroid (of course with microG),

according to Google's Playstore; I have a certified device ;)

you can check on the system/framework folder of your LineageOS 15.1.

if you can find "oat" folder, then you have an odex-ed ROM.

you need to de-odex the ROM (or IMO, at least the services.jar) to make the NanoDroid patcher gets its job done.

afaik, most oreo based ROMs are odexed
[Magisk] utg1:
[MENTION=4187311]Setialpha[/MENTION] I'm testing new beta 3 and all is OK! ? Even with Magisk 16.2

Thanks mate
[Magisk] Predatorhaze:
What files we need to download and flash?beta 3 zip got all included(225mb)?
[Magisk] :
[MENTION=4187311]Setialpha[/MENTION]

Can I use this module just to have some apps up-to date if I choose not to install MicroG and NLP Provider in setup wizard or will it still mess with gapps in any way?
[Magisk] Mynacol:
https://gitlab.com/Nanolx/NanoDroid/blob/master/README.md

The given link should answer your questions. If there are any left, let us know
[Magisk] sparkster666:
I installed [ROM][OFFICIAL][8.1.0]FireHound-v4.3.1 For Google Pixel XL [Marlin] on my Pixelxl

I install Nanodroid as a Magisk module but every time I try to run the F-droid or Yalp store I get this error.

Any help would be appriciated
[Magisk] Anarchy16:
hello, long time no see,

i have an issues here which i never faced before, AFAIK, microg is google-less, but somehow in the new build, its ask me to update google play services (see screenshot) but after finished downloading, it cant install the update (obviously)

device : hero2lte (s7 edge)

rom : AEX

nanodroid : latest beta

method : clean flash
[Magisk] marcdw:
[MENTION=7162809]Anarchy16[/MENTION], just because it says you need to update play services that doesn't mean you were supposed to do so. You are using microG after all, not Google.

The issue is with Telegram. I'm using 4.8.4 from TeamBlackOut on my microG (0.2.4-108) ROMs with no issues.

If your Telegram is from the Play Store maybe try another one like from F-Droid or TBO.

LG G3 D851, PAC-MAN LP ROM, MultiROM, Tapatalk 4.9.5
[Magisk] Anarchy16:
i see, tq for info :svetius:
[Magisk] cristihan:
I received this error in Oreo 15.1 on my galaxy i9195i after trying to update via Fdroid an application installed with Yalp Store. I solved this error as follows:

- Cleared cache for Yalp Store

- Uninstalled f-droid.

- Reinstalled f-droid (zip file from NanoDroid via TWRP).

- Update repository Fdroid after install.

- Installed org.fdroid.fdroid.ota_1000013 from Fdroid repository.

- F-droid installed applications only update them with Fdroid!

I hope this will help you. :confused:
[Magisk] Setialpha:
Some apps are now expecting a higher Play Services version Number, more precisly version 12.x, while microG spoofs version 11.x. Wait for an microG update to solve this issue (or use Telegram from F-Droid, which does not rely on Play Services, as already suggested).
[Magisk] amakuramio:
Wish it contained googlebackuptransport, googlecalendarsync and googlecontactsync. Extracting them from opengapps, putting them in system, setting permissions everytime is annoying. Made update.zip with titaniumbackup.

But yeah fck google, always 4 to 5 hr sot and drains, when removing gapps now 7 hr sot without a sweat.
[Magisk] Setialpha:
It does, you have to enable it. Read the docs, or use the SetupWizard before flashing.
[Magisk] Anarchy16:
read the alter installation details, make .nanodroid-setup file or use setupwizard
[Magisk] kurtn:
Haha verhext
[Magisk] cristihan:
"Telegram" is no longer what is said to be in the matter of encryption.

Look here: https://gizmodo.com/why-you-should-stop-using-telegram-right-now-1782557415

and here: https://medium.com/@thegrugq/operational-telegram-cbbaadb9013a

"Signal" is for those who care about their private life !

:cool:
[Magisk] Setialpha:
Version 16.3 contains a broken MPV build (effects x86_64 and arm64 devices). Use the following command as root to update to a fixed build:

nupd mpv

I'll re-upload 16.3 with the fixed apk, soon.
[Magisk] amakuramio:
Thanks will flash nanog microg plus setupwiz
[Magisk] amakuramio:
Btw how to set unifiednlp?
[Magisk] guest4711:
The basics are included by default. You may add backends at any time, e.g. from f-droid.

The GitLab repository contains the full documentation with infos about

more detailed info what's included

detailed installation instructions

setup instructions for microG

list of known Issues (and fixes/workarounds)

more

>> Full Documentation
[Magisk] cristihan:
[MENTION=4187311]Setialpha[/MENTION] Thank you for your great work !

I've tried the framework patcher from "NanoDroid-patcher-16.3.20180327.zip" today via TWRP, on my device (android 8.1) but it has caused error. (Attached)
[Magisk] guest4711:
The errormessage (on your screenshot) tells you that odexed ROMs are not supported.

If you don't know what that means (you are not alone) search this thread for "odexed" or see https://xdaforums.com/apps/magisk/module-nanomod-5-0-20170405-microg-t3584928/post75693780[/url
[Magisk] Setialpha:
16.4

What's better than just re-uploading version 16.3 with a fixed MPV.apk? Right, uploading version 16.4 with a few more changes.

Full 16.3 announcement post

Full ChangeLog for 16.4

### Bug Fixes

* CommonInstaller
* fix magisk.img handling when an installation error occurs
* fix storing recovery.log in /data/adb/ after installation
* Full Package
* MPV build from 16.3 crashed on x86_64 and arm64, fixed build included

### General Changes

* CommonInstaller
* programmatic /system/xbin handling
* if /system/xbin exists in ROM use it for installing utilities and scripts
* if /system/xbin does not exist in ROM, use /system/bin instead
* progressbar functions
* stuff taken from osm0sis' busybox installer
* Full, F-Droid, microG packages
* don't unmount /system at the beginning of the installation process, just to re-mount it later during mount_partitions()
* utilize CommonInstaller progressbar functions for proper progressbar display

### Software Updates

* Automatic
* GNU Nano (2.9.4)

Download links

Download from AFH or Nanolx.

Bug reporting

In case of errors, please provide

/data/adb/.nanodroid_MODID

/data/adb/.recovery_MODID

logcat (if applicable)
[Magisk] lmvuong1997:
Please check the nanodroid-microg-16.4 archive, there's only system folder so can't flash
[Magisk] guest4711:
[MENTION=4187311]Setialpha[/MENTION] Same here. No scripts etc. included...
[Magisk] Setialpha:
Thanks for informing me. 16.4 microG and F-Droid packages re-uploaded.
[Magisk] guest4711:
NanoDroid-microG installs OK now. Thanks a lot.
[Magisk] d0s1s:
Hi,

[MENTION=4187311]Setialpha[/MENTION] I have one question: Why is GsfProxy in /system/priv-app? Due to MicroG documentation it is not needed to run like a priv app.

github.com/microg/android_packages_apps_GsfProxy/blob/master/services-framework-proxy/src/main/AndroidManifest.xml#L9-L10

github.com/microg/android_packages_apps_GmsCore/blob/master/play-services-core/src/main/AndroidManifest.xml#L21-L29

Thanks!
[Magisk] :
[MENTION=4187311]Setialpha[/MENTION] The newest version of Lawnchair from Github works great without Lawnfeed, if you want you can try to include it instead of OpenLauncher: https://github.com/LawnchairLauncher/Lawnchair

For now it's only available on Github.
[Magisk] Setialpha:
Because it's been like this forever™ (read: for no particular reason).

Well, I may have a look, though I'm not making any promise on switching.

-----8x-----

modified Play Store 9.4.18 uploaded, run, as root:

nupd ps

to update.
[Magisk] d0s1s:
O.K. Seems GsfProxy doesn't require any privileged permission, so it doesn't have to be put under priv-app.

Best Regards!
[Magisk] inVain_theGenuine:
is it possible to install NanoDroid without any Playstore or Yalp?

I did tried to configure the setup wizard without any store (nanodroid_play=0) and manually copied the "fakestore" to priv-app, but the MicroG's Self-Check was complaining about phonesky wasn't installed.

maybe I should rename the "fakestore" to "phonesky" to get it done?

I'm currently running 16.4 with Playstore, but apparently google's always giving me the x86 version of FireFox which lead me to search on APK Mirror for downloading my apps.

thought I might be save some resources by ditching the Playstore, but doesn't like to reinstall my whole rom without knowing if this might be achieved.... so I just ask here first :)
[Magisk] inVain_theGenuine:
hi....

I was wondering if this is a typo, kindly see the following attachment (in the blue circle)
[Magisk] :
Thank you for the great app :)

I have a question: I have to allow all app permissions again after each update of nanodroid. Is it normal, a bug or I have to change the way of install/update process?

Normally I update LineageOS first and then install nanodroid with TWRP (After the last step, I have to set the app permissions again)

Hardware:

LineageOS 14.1

Bq aquaris M5
[Magisk] cristihan:
- Edit these files ".nanomod-setup", ".nanomod-apps" , ".nanomod-overlay" with NP ++ as you wish .

(Explanations and my custom setup files in attached zip).

- Copy edited files and "NanoDroid-16.4.zip" on your extenal sd card. (do not delete the "dot" from files names !)

- Flash via TWRP.
[Magisk] Predatorhaze:
i thought yes,but really..there is no clear explanation.Here https://gitlab.com/Nanolx/NanoDroid/blob/master/README.md ,it says use setupwizard and after that it says do a clean wipe..

How the f*** i install this gapps package? can someone just tell the right order.I just wnt to use it,dont wanna know all the ins and outs

Do i need to flash setupwizard and thats it?!
[Magisk] demonoidmaster:
Ffs, flash rom

Flash setup wizard, select what you want

Flash microg

Nowhere does it say to wipe after using setupwizard
[Magisk] Predatorhaze:
flash microG or Nanodroid package?

This is the readme.

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

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

either pre-patched with signature spoofing support or deoxeded so you can patch yourself (instructions follow)

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)

install NanoDroid

reboot into ROM
[Magisk] guest4711:
If you need the basic functionality NanoDroid-microG is sufficient. If you want more, take the full package (and deselect all you don't like in setup wizard).
[Magisk] Predatorhaze:
i think i get it now.Ive found out AEX rom is odex rom..spoofing is not support out of the box
[Magisk] Draygon:
Hello,

can someone tell me how to update Nanodroid correctly?

Whenever I do this, GCM push notifications of my apps are not working anymore. I need to reinstall affected apps completely, which is a time consuming process (Need to backup app data of many apps).

I really want to switch completely to Nanodroid, but this forces me to stick with GAPPS.
[Magisk] jenslody:
Do you reboot without NanoDroid installed in the process ?

I use microG from their repo instead of NanoDroid, because I sometimes boot with disabled Magisk (or broken Magisk, because I use internal test-builds) and the reinstall process is annoying.

But I thought, that if you do not reboot without microG it should work.

Maybe it's related to the fact, that NanoDroid installs it as system-app (just a wild guess).

I systemized the droidguard-helper, because it's needed to pass safetynet (even if I can not pass it at the moment with my rom).
[Magisk] rnadomuc:
will Play Store Visa make it possible to use Play Store without signature spoofing or fakegapps?

https://xdaforums.com/apps/magisk/play-store-visa-device-certified-custom-t3769069
[Magisk] :
I installed Nanodroid now on a rom with signature spoofing support. Selfcheck is showing everything activated except for signature for phonesky. I'm sure that I let the wizard install the fakestore (Yalp and fakestore I think) but for some reason I can't find the store to give any permissions at all (there is also no phonesky on /system/priv-app/). The Yalp store is installed. Is there a possibility to install phonesky manually and if yes, how do I have to proceed (should it be installed as system or user app?).

Also Yalp is always showing updates for Device Health Services and MicroG Services Core. I'm guessing that I definitely shouldn't update them but can I remove these messages somehow or is it only possible to set them on the blacklist for Yalp?
[Magisk] jenslody:
pm grant com.google.android.gms android.permission.FAKE_PACKAGE_SIGNATURE

as root or in adb shell should do the trick to enable signature-spoofing for fake-store.

And in yalpstore, there is an option in the settings to blacklist apps, so it does not check for updates.
[Magisk] marcdw:
AEX has had signature spoofing support for awhile now. At least on Nougat.

You're on the Axon 7, right? NFound's AEX O ROM is odexed? Hmm, didn't know that. But are you sure spoofing is not included? There's no setting for it so after flashing/installing microG you'll see if support is there under App Permissions.

I think I'll flash AEX O on a Moto and see if it has sigspoofing.

EDIT: Yep, it's there.

ZTE Axon 7 A2017U, DarkROM_SimpleMobileTools, microG (NoGapps), Multiboot, Tapatalk 4.9.5
[Magisk] :
I tried it with Termux 2 times now but its not working. Haven't tried it with ADB via my PC but I'll try this too.

I know about Yalp and blacklisted apps but I had hoped that there is a way to get rid of it permanently but I guess due to Yalp thinking MicroG is Android Play Services, it can't be helped. I guess, there is no workaround for blacklisting it.
[Magisk] guest4711:
Did you switch to a root shell before by typing

su
pm grant ...

or

su -c pm grant ...

? What errormessage do you get?
[Magisk] :
Yes, I tried both of these commands. There is no error message. It just opens a new line in the terminal without message at all (no positive nor negative).
[Magisk] kurtn:
Why donty you use the settings GUI? App permissions spoof... Threedotmenu
[Magisk] kurtn:
Why don't you use the settings GUI? App permissions spoof... Threedotmenu
[Magisk] :
[MENTION=4187311]Setialpha[/MENTION], sorry for so many requests, but there is a YalpStore alternative with a material design interface called Galaxy. It also has some updated libraries and it's available from Github and XDA Labs. If you decide to do so, you can include it as an option next to Yalp and Google Play. You can see the github page here: https://github.com/whyorean/Galaxy
[Magisk] perrsona1234:
From what I know, Galaxy is just a fork of Yalp Store. So it's basically the same but with material design. Same bugs, etc. Current 1.0 Galaxy ver is based on 0.35 Yalp Store ver. :)
[Magisk] :
The dev said something about removing old libraries and updating others, since Yalp store keeps old ones for backwards-compatibility. But essentially yes, you're right.
[Magisk] inVain_theGenuine:
thanks a ton for going into trouble to upload those file for me :)

your "custom-setup-read!!!.txt" is a genuine savior!

I used to think that those value is a binary switch; 0 & 1 only (got stuck in those avr world for quite some time before :LOL)

guess I'll tweak my phone on this week end as well....

thank you :)
[Magisk] :
I can't believe that this was actually what I needed to do. Thanks a bunch.

BTW: microg shows only 2apps which registered with gcm but I'm sure some others should have to. I registered gcm before installing any apps, only phonesky signature wasn't active thought that has nothing to do with gcm. Is there a way to manually register apps for gcm. Signal for example is reported to work.
[Magisk] marcdw:
Right. There is no confirmation in the terminal. Once you issue the command then that's it. Go to the microG Settings self-check page to confirm it worked.

EDIT: Oops, too late. I see you got it.

I was thinking FakeStore anyway which had to be done via terminal. Sorry.

LG G3 D851, CyanogenMod CM12.1 ROM, Fechda R7 Kernel, MultiROM, Tapatalk 4.9.5
[Magisk] Shadow53:
Some apps use Firebase instead for notifications, which microG doesn't (yet) support. To make these apps register, you'll need to install an old version that uses GCM, have it register, and then update it to the newest version. That's been reported to work with some apps, at least.
[Magisk] Predatorhaze:
Yeah I discovered later when I read it on a forum. MicroG works good on aex o! Thanks. But play games are not working(cloud save), whatsapp(drive cloud) does work. Is there a way to make play cloud save work?
[Magisk] kurtn:
I think it's not worth the trouble, when you end up in a GApps like setting with massive proprietary software and all your personal data on Google servers. Then you better stay with original GApps.

And play games is not implemented.
[Magisk] deedeeceleb:
I've got the same problem after doing a clean flash on carbon. Everything was working nice on 16.2 and below.

My apps also tell me that Google play services aren't installed and refuse to run.

16.4 is also giving me several different error 1 like failed to install npem.

Gesendet von meinem ONE A2003 mit Tapatalk
[Magisk] inVain_theGenuine:
I just finished re-installing 16.4 my phone on the morning (now it's dusk, where I'm living).

this time I went without Playstore (nanodroid_play=0),

the only difference I made with my previous attempt was; I manually download the "fakestore" app from the microG web site.

rename it to "Phonesky.apk" and place it inside "Phonesky" folder.

copy it into /system/priv-app folder;

I'm on Android 7.12, and have NanoDroid installed as part of my system (nanodroid_forcesystem=1).

now I have everything works flawlessly.

maybe you can do the same with the bundled "fakestore".

[MENTION=4187311]Setialpha[/MENTION]

on my 2nd attempt installing NanoDroid 16.4 (with the full NanoDroid package + setupwizard), I constantly missing GsfProxy in my priv-app.

wasn't a big deal, since I can manually copy it to the appropriate folder.... but I thought I might inform you anyway ;)
[Magisk] :
It seems like I get notifications from signal, just WhatsApp not (I think). All the other apps like TripAdvisor and airbnb aren't that important anyway so it's not worth the trouble. I have no clue which version uses firebase and which gcm or even how I would get such old versions.

---------- Post added at 01:58 PM ---------- Previous post was at 01:54 PM ----------

I get that play services not installed message on a few apps like TripAdvisor but as far as I can see it still works but I can't really test it so I'm not completely sure.

No error 1 messages though.

I hope that firebase will work in near future. Its mostly not important but still, it would give you a better feeling of "completeness" :laugh:.
[Magisk] inVain_theGenuine:
my WhatsApp is okay with NanoDroid, it was registered on microG's GCM; I got notified for every single messages I received, and quite instant as well.

I believe I'm using the latest stable version of WhatsApp (2.18.92).

are you using orBot as well?

when I'm using orBot, my WhatsApp seems a little clumsy for triggering the sounds /led notifications.

now I'm trying to register the WhatsApp on orBot's vpn and it behaves better (at least for these 2 days since I started to use orBot's vpn).

you can try the:

https://play.google.com/store/apps/details?id=com.firstrowria.pushnotificationtester&hl=en

to check your GCM notification functionality.
[Magisk] :
I installed all my apps via titanium backup with data. Is this somehow a problem to restore work data? I restored them definitely after registering with with gcm in the microg settings. The only thing that didn't work at that time was phonesky signature but m pretty sure this has nothing to do with gcm and push notifications?

To be precise, it doesn't seem like push notifications don't work for me. I get them for XDA for example. Its just some apps and for some reason, only 3 apps are registered with gcm, according to microg settings, even though much more are definitely working.

I haven't used orbot since I switched to Oreo as for some reason the VPN rooting for different apps didn't work. It worked on nougat. Orbot itself worked but I don't use orfox so without VPN routing, I have no reason to use orbot. Though, to be fair, some apps (like fdroid and lightning browser) can natively proxy with orbot in the settings.

Thanks for this push testing app. I tested it and all works fine so maybe titanium with data restoring is the problem? I think I will have to all this in the microg thread instead of spamming this one. Nanodroid itself worked flawlessly :)