yashsingh1/xdaforums huggingface dataset:
[Magisk] Setialpha:
Nope, the last time I checked it did not feature much more than a nice UI, so I decided to stick with Yalp Store.
[Magisk] Setialpha:
Open the NanoDroid zip file of your choice and navigate to the folder (inside the zip):

system / etc / permissions

you'll find a file called

privapp-permissions-google.xml

; replace it with the attached one and re-install NanoDroid from that updated zip file.

Your ROM should boot now (unless you stumble accross another issue).
[Magisk] Setialpha:
hmm... do you have any adblocker active? if so, please manually whitelist the following domain:

mtalk.google.com
[Magisk] R+Z:
Getting an nginx error when trying to download the file. Anyhow thanks for the fast reply.
[Magisk] Setialpha:
You can also download it from gitlab if XDA gives you an error.
[Magisk] friedCELLS:
Just letting you know that I use protonmail and it works fine for me. Not sure what I did to get it to work. I'm on Lineage OS, Oreo 8.1, microg all updated to latest. I found somewhere that somebody suggested installing protonmail v191 (search on apkmirror). I actually installed this first but couldn't login even though the password was correct. I gave up and installed the latest version from microg Playstore, enabled Google cloud msging in MicroG settings, and I get push notifications when new emails arrive without issue. Maybe something happened in the install of the old version even though it wouldn't login?! No idea.
[Magisk] Nosepull:
Can anybody explain why location is so unreliable with MicroG / NanoMod? I have some Tasker profiles based on network location, and they work very unreliable without GApps. Using original Google Apps on the same device, everything is fine.

I tried the Mozilla location service as included with NanoMod and the Local GSM backend from FDroid. The last one seems to be a bit better, but not good enough to be reliable. Most of the time the location context is only activated when turning the screen on, or not at all. Some battery saving problem, maybe?
[Magisk] Oswald Boelcke:
I'm extremely happy with the preciseness and reliability of network location in conjunction with µG! This means I absolutely disagree to the statement that location is unreliable with MicroG / NanoMod. However, I don't use Tasker and though unable to try to reproduce any possible location implications in this respect.

If interested in the backends I use and their settings, please refer to this post in @MaR-V-iN's thread:

UnifiedNlp - FLOSS Wi-Fi- and cell-tower-based geolocation.
[Magisk] devrruti:
I see a few improvements in aurora over yalp:

Aurora by default doesn't ask to update the fdroid apps that have newer versions in play store (causing signature mismatch error)

You can spoof location to get apps not available in some territory
[Magisk] Setialpha:
So it must have seen some love since then, I'll test it again.
[Magisk] Setialpha:
Same here. DejaVu is a learning backend which connects your GPS location to cell tower location. It improves as more data it can combine.

Ichnaea (Mozilla) is pretty good, it uses data provided by Mozilla. Here in Nuremberg Ichnaea is almost equal to GPS. But it data coverage may be less good in non-urban areas. There's Mozilla Stumblr in F-Droid, which you can use to srnd data to Mozilla, to improve the database, if you wish.

Indoors vs. outdoors is indeed a little bit worse compared to GApps, it's about 10 - 15 m off indoors sometimes, but that result will heavily vary depending on the device and the materials outwhere and how much cell signal they block.
[Magisk] Setialpha:
[MENTION=8483166]R+Z[/MENTION] is your issue solved with the new file?
[Magisk] temporarium:
I got curious and installed the latest 2.0.3b Aurora Store and had trouble logging in anonymously. This version on F-Droid is from June, so maybe it needs an update...
[Magisk] Nosepull:
I use Tasker and network location to switch between work- and home-profiles. With GoogleApps, this works flawlessly. On the same phone, with MicroG, Tasker often seems to get stuck in one profile. E.g. I'm at home and for hours the phone stays in work profile. I also noticed that SatStat does not always show the blue pin for network location.
[Magisk] mobilism:
Thanks!Problem salved! It caused by application Brevent enabling Dynamic Disable.
[Magisk] ydd0ras:
Thx for the tip. It works withe the 9.80.0!
[Magisk] R+Z:
Yes.

Someone mentioned that I would have to whitelist permissions to get microg to work, but I though I had to modify the rom and not the microg zip.
[Magisk] Setialpha:
Great. So I may make an official release this weekend.
[Magisk] devrruti:
It's not been updated in fdroid

https://gitlab.com/fdroid/fdroiddata/merge_requests/3772

You can get v2.0.5-β here:

[APP][5.0+] Aurora Store - an opensource App Store [Oct 13] - https://xdaforums.com/android/apps-games/galaxy-playstore-alternative-t3739733
[Magisk] aaron74:
Awesome! Finally got time to experiment. Can't believe this worked on stock rom (emui8). Everything working as should be.

1 correction for directions. The patcher needed installed through magisk.

Thanks for all your work on this.
[Magisk] temporarium:
DELETED
[Magisk] Klizi:
I have flashed NanoDroid-microG-19.0.20181027.zip on Magisk.

After the reboot, I can see this.

Is it safe? Is it installing original Google play services which would eat battery a lot? Will it overwrite the microG play store with the original store?
[Magisk] Klizi:
Then again It started displaying the play store as 'Leaks' and it crashed when I open it. What is happening?
[Magisk] abacate123:
Try this. Delete the module. Reboot. Go to TWRP and install it through there (not through the Manager). Login again. Check if you face such issues later on. These weird af issues are rare, but sometimes it used to happen with me when I updated the module through the Manager... Dunno why.
[Magisk] Klizi:
Here what I tried:

Deleted magisk module and rebooted, Flashed "NanoDroid-microG-19.0.20181027.zip" once again with magisk. - Didn't fix. Still seeing the play store as "Leaks"

Deleted magisk module and rebooted again, Then rebooted once again to Recovery and flashed "NanoDroid-uninstaller-19.0.20181027.zip" via recovery, then rebooted to system, and flashed Flashed "NanoDroid-microG-19.0.20181027.zip" once again with magisk - Didn't fix. Still seeing the play store as "Leaks"

Deleted magisk module and rebooted again, Then rebooted once again to Recovery and flashed "NanoDroid-uninstaller-19.0.20181027.zip" via recovery, then rebooted to system, and rebooted to recovery again and flashed "NanoDroid-microG-19.0.20181027.zip" again with the recovery, as your directions. - Bootloop occurred

Got back to the recovery by holding Power+Volume up keys, Flashed "NanoDroid-uninstaller-19.0.20181027.zip" via recovery, then rebooted" - Still bootloop

Got back to the recovery by holding Power+Volume up keys, Wiped Dalvik/Cache and Cache, then rebooted" - Still bootloop

Got back to the recovery by holding Power+Volume up keys, flashed "NanoDroid-uninstaller-19.0.20181027.zip" via recovery, Wiped Dalvik/Cache and Cache, then rebooted" - Still bootloop

Got back to the recovery by holding Power+Volume up keys, Restored the nandroid backup (System, Vendor, Data, Boot), Wipe Dalvk/Cache, Cache, then rebooted - Booted to the system, and it has previous version of microG, which is working fine.

Deleted magisk module, which was the previous version of NanoDroid-MicroG, Rebooted to system, then rebooted to recovery. Flashed the latest MicroG with recovery (again "NanoDroid-microG-19.0.20181027.zip"), Wiped Dalvk/ Cache , Cache , Rebooted to system. - - Bootloop occurred

Got back to the recovery by holding Power+Volume up keys, Restored the nandroid backup once again, rebooted to system, Deleted Magisk module which was the previous version of microG, Rebooted, Flashed Latest NanoDroid-microG-19.0.20181027.zip with magisk - Didn't fix. Still seeing the play store as "Leaks"

Restored the nandroid backup again and gave up on the latest microG version

Running Havoc OS with stock kernel. Seems like there is a problem with the latest stable version of microG.
[Magisk] Oswald Boelcke:
You certainly have good reasons to trigger tasker by network location and not by your home WiFi. I just assume that you e.g. arrive at home with disabled WiFi and that you enable WiFi via your home profile. However, I still doubt that the issue is really µG (or then in turn NanoDroid) related but that there are issues with your backend(s) or even the middleware.

If my above assumption is correct then Déjà Vu by @n76 might be the right backend for exactly your purpose as it not only uses locally acquired WLAN/Wi-Fi AP but also mobile/cellular tower data to resolve user location.. Personally, I'm very satisfied with Déjà Vu as it provides a very accurate position as long as it was at least once allowed to correlate a GPS position with a network. At home indoor with even poor GPS reception and location mode set to energy saving, I get a position nearly as accurate as GPS. Please consider to give Déjà Vu a try.

With the MozillaNlpBackend I personally always had some issues therefore I don't use this backend any longer but I know that other people like e.g. Setialpha made different experiences. I use the LocalGsmNlpBackend also by n76 with great satisfaction. To create my database, I'm using the data provided by Mozilla Location Services and not the ones of OpenCellId as I also experineced trouble with the latter ones. In order to create my database, I've filtered the data by country, and I only download/update via WiFi due to the amount of data.

µG already comes with UnifiedNlp but if your issues persist when even using other bankends you might want to consider to try the middleware (depending on your system) available on F-droid (https://f-droid.org/en/packages/com.google.android.gms/, https://f-droid.org/en/packages/com.google.android.location/, https://f-droid.org/en/packages/org.microg.nlp/) or to use the respective Xposed module.

​
[Magisk] SH1M4BD3:
Sir , really love this decelopement, one serious problem for me seems the googlephoto won't sync(backing up) ..while pulling some old photos seems work good, even on wolifi seems unable to auto backup the pictures here..anyone have solution on this??
[Magisk] HyperCriSiS:
Could be Tasker related. I get very good location results. You could add more location services. There are some more available on F-droid. Just search for " nlp".
[Magisk] Nosepull:
I know that there are more location services available. Of those, for me Mozilla seems to be the most unreliable and LocalGSM the best alternative. However, even this one seems flakey for me. I haven't tried DejaVu yet.

Looking at the circles which SatStat gives for location accuracy, they seem alternatively absurdly big or are not there at all, making me believe that Google's location services have some clever algorithms behind.
[Magisk] mobilism:
Any help is appreciate . Can I install Microg without installing any location backdends ？The stock one works better .Search all posts can't find out what should I do .
[Magisk] kurtn:
As you are on stock ROM or custom with GApps. You still can disable all Google apps, except play services and install f-droid.
[Magisk] Setialpha:
Should be fixed with the next release. Given you've choosen to install swipe libs.
[Magisk] mobilism:
My rom is a modified Sony's stock Rom without GApps. Stock's COM.QUALCOMMM.LOCATION works better than Microg's location backdends. When I installed Microg , it would delect COM.QUALCOMMM.LOCATION ，which makes GPS signal worse than stock one .
[Magisk] Setialpha:
com.qualcomm.location is incompatible with unlp, you won't get any network location without removing it.
[Magisk] mobilism:
So it's possible to Flash Microg with uninstalling Microg's location backends. I

In setupWizard that is no selectbox to chose dosen' install location backdends .
[Magisk] Setialpha:
Technically yes, but again: it will very likely break network location, as unlp is builtin into microG, only the backends can be removed, not unlp itself.

You can restore com.qualcomm.location by issueing the following command, as root, on device:

novl -d com.qualcomm.location

The reboot and see what happens.

Given basically no one can reproduce your issue (or not that heavy off result), I suppose your suffering from a bug or ROM incompatibility and reporting it with a logcat might help more than punching unlp with a hammer in the long run.
[Magisk] mobilism:
In MicroG settings self-check shows my system does not suppor tUnifiedNlp. I think that is why gps works better before installing MicroG.

Thanks for your help.
[Magisk] weissgarnichts:
Nice to hear!

I did check swipe libs in the setup wizard, but i even mentioned that the box was unchecked when i upgraded to the new nandroid version.

Regards
[Magisk] Jungfred:
The nanodroid-microG.zip includes

"on-device framework-patcher for microG support (signature spoofing)"

So its redundant to flash the patcher after the nanodroid package?

Or is this not the same "patch"?
[Magisk] Setialpha:
The SetupWizard does not need to be run on updates again, as your choices already are saved. And yes, it does not read previous choices, but that's an AROMA limitation.

You're mixing up the project summary 'Nanodroid') you've read, with the module summary ('Modules' > 'NanoDroid-microG') following up below that.

tl;dr no, the Patcher is the on-device framework-patcher.
[Magisk] SH1M4BD3:
[MENTION=4187311]Setialpha[/MENTION], i'm on pie with microg support ..how do i fix the playstore error, at the first setup playstore works but not even opened after reboot, and about google photo sync does it needs some option too on setup wizard same as contact&callender part, as all of my photos already backed up on cloud and with 32GB storage i have..i won't lie i really need the google photos works flawlesly auto backup, and freeing up the space when i needed, as for now its still buugy, sometimes work, but many time stuck on backing up process, look forward on this...thanks
[Magisk] J4jks:
Hey, setialpha , I've installed Nanodroid microg and frdroid 18.x beta and upgraded to 19.

For me , mostly all apps installed are registered in microg but only few apps are receiving notifications.

You can see in the ss attached.

Tried old version of the app and didn't get any notifications.
[Magisk] Setialpha:
Well it's straight there: Play Store does not have signature spoofing granted. Go to Settings / Apps / Permissions / Signature Spoofing and grant it.

Dunno, works here, but that's not a NanoDroid issue, but a microG, grab a logcat and report it upstream.

As stated seversl times, ensure you have no adblocker blocking mtalk.google.com it us required for GCM to work.
[Magisk] Setialpha:
I updated the issues section of the documentation, see:

https://gitlab.com/Nanolx/NanoDroid#issues

Also instructions for checking package SHA256 checksum and GPG signature, if desired, have been added:

https://gitlab.com/Nanolx/NanoDroid#sha256-checksum-and-gpg-signature
[Magisk] ashwini215:
I am using samsung galaxy A5 2016, nougat.

Uptill NanoDroid-microG-18.90.20181011 everything works fine.

From v19 (both betas), I am getting bootloop ( the screen's stuck on samsung logo).

Logcat is attached (this one's v19 beta2).

Kindly advice :good:
[Magisk] psychem:
i had this issue too, data partition got corrupted. clean flash solves the problem.
[Magisk] ashwini215:
If you mean installing stock rom via odin and then repeating the process of installing MicroG, I must tell you that I, frustratingly, have tried this several times & ended up with the same issue :(

I should also tell u my process :-

flashing latest stock rom (nougat in my case) via odin--->

deodexing it ---> flashing nanodroid patcher, reboot---> in twrp flashing setupwizard & flashing nanodroid simultaneously...

Please tell how you are doing it. which device and android version are you using.
[Magisk] razorfancy:
[MENTION=4187311]Setialpha[/MENTION]

Can you please help me? I am using RR N 5.8.5 but I cant sign-in to my google account using Nanodroid Micro G.

I install it like this:

1º Reboot to Recovery.

2º Wipe Cache, Data and System

3º Flash RR N 5.8.5 ROM

4º Flash Magisk

5º Flash NanoDroid-patcher-19.0.20181027.zip

6º Flash NanoDroid-microG-19.0.20181027.zip

7º Flash NanoDroid-fdroid-19.0.20181027.zip

8º Reboot

After the system start I have go to the MicroG Settings:

enable Google device registration

enable Google Cloud Messaging

enable Google SafetyNet

In UnifiedNlp Settings I choose:

Déjà Vu as Geolocation backend

Nominatim as Address lockup backend

After this I reboot the system and I have go to the PlayStore and try to sign-in to my google account but it keeps crashing when I try to insert my google account password.
[Magisk] Oswald Boelcke:
You're flashing/installation procedure sounds very reasonable to me. Did you check if all permissions are granted to Google Play Store. Occasionally, it happened to me (don't ask when precisely) that I had to grant them for the initial setup but could afterwards withdraw them again. Sometimes a wipe of play store data and cache is also useful.

If interested how I first went for NanoDroid about one and a half year ago, it's contained somewhere in this thread.
[Magisk] psychem:
im using oneplus x oreo rom LOS 15.1.

i backed up the apps using titanium backup and the did a clean flash meaning wipe system data dalvic and cache before flashing LOS 15.1 and nanodroid from twrp.
[Magisk] Setialpha:
For the Play Store issue all known solutions are in the documentation under "Issues". About Google Photos, I don't know, I don't use it. If anything, a logcat would help.
[Magisk] Setialpha:
What's the logcat?
[Magisk] Setialpha:
19.1.20181102 "Bonaventure"

Hi all,

version 19.1 Codename "Bonaventure" is now available.

What's new?

fixed issues with too "brutal" GApps removal causing issues in some cases

fixed bootloops caused by missing READ_RUNTIME_PROFILES permission for Play Store on some ROMs

improved Swipe library installation / provide SDK specific versions

documentation: add section "SHA256 Checksum and GPG Signature", improve section "Issues", minor changes to section "microG Setup"

usual updates

Full ChangeLog

## 19.1.20181102 "Bonaventure"

### Bug Fixes

* Full, microG packages
* add READ_RUNTIME_PROFILES to Play Store priv-app permissions

* Commoninstaller
* improve microG DroidGuard Helper installation
* fix swipe feature by providing SDK-specific libraries

### General Changes

* Full, microG packages
* split privapp-permissions-google.xml into
* privapp-permissions-microg.xml for microG GmsCore permissions
* privapp-permissions-phonesky.xml for Play Store permissions
* split microg-permissions.xml into
* microg-permissions.xml for microG GmsCore and uNlp permissions
* phonesky-permissions.xml for Play Store permissions
* add privapp-permissions-gsync.xml for BackupTransport permissions

* CommonInstaller
* make GApps removal mechanism less brutal

### Updates

* automatic
* New Pipe (0.14.2)
* Blokada (3.6.101900)
* OpenVPN (0.7.6)
* (Simple) Gallery (5.1.2)

* manual
* MPV (20181102-nightly)
* OpenLauncher (20181029-nightly)
* Play Store (12.4.14)
* microG GmsCore (0.2.6.14369-dirty-103)

Download links

Download from Nanolx or AFH.

Bug reporting

In case of errors, please provide

/data/adb/MODID_log_INSTALLDATE

/data/adb/MODID_twrp_INSTALLDATE (TWRP Installation)

logcat (if applicable)
[Magisk] adolfo2000:
i cant connect to discord app on 27-10 nanodroid, can this be related to microg or is a rom issue?
[Magisk] mobilism:
After updating to "Bonaventure"，google play store crash, even clear play store data and cahce.
[Magisk] Nosepull:
Newest version causes all apps loosing most of the granted permissions. Even worse, MicroG starts with (bad) default settings: No location providers, no device registration for push services activated. I.e. all apps relying on push would have to be reinstalled. S7 with LOS15.1. What am I doing wrong here?
[Magisk] Setialpha:
19.1.1 "Bonaventure Refit"

Hi all,

I've uploaded version 19.1.1, which should fix issues from 19.1 caused by privapp-permissions.

I hate that some ROMs behave different than others. I'm also considering disabling flashing through Magisk Manager, and only support flashing through TWRP.

Download links

Download from Nanolx or AFH.

Bug reporting

In case of errors, please provide

/data/adb/MODID_log_INSTALLDATE

/data/adb/MODID_twrp_INSTALLDATE (TWRP Installation)

logcat (if applicable)
[Magisk] Nosepull:
Seems to have fixed my problems, thanks. I always flash with TWRP.
[Magisk] mobilism:
Play store still crash.Falsh via TWRP.
[Magisk] mobilism:
Log
[Magisk] Nosepull:
I used the setup wizard to force system installation mode. Otherwise even TWRP always uses Magisk installation mode if it was selected before.

One observation with the new ZIP: It seems that it has force-debloated my rom, though I never configured that...
[Magisk] gensec:
F-droid? I don't see it there yet.
[Magisk] abacate123:
That'd be better.
[Magisk] Setialpha:
? NanoDroid is not in F-Droid. I guess you mean custom microG GmsCore build, but that's not what was updated.
[Magisk] adolfo2000:
After a lot of testing i realised nanodroid microg is blocking discord gateway. I tried an older nanodroid version (21-09) and it worked so it is a recent bug

I used an older discord version (6.9.3) and the latest version to test.
[Magisk] :
nice to hear, my discord also not working so now we know there is something wrong
[Magisk] Setialpha:
NanoDroid does NOT block anything. Either it is Blokada set up too strict or something else, I may investigate,
[Magisk] psychem:
can u plz add swipe libs to nanodroid?
[Magisk] Setialpha:
It already is included. You need to enable it.
[Magisk] gensec:
Same here
[Magisk] mobilism:
My temporary workroud is exteact Play Store from microg.zip and normally install it again.
[Magisk] gensec:
I came back to 19.0 because cloud messaging also didn't work, now with 19.0 all ok
[Magisk] friedCELLS:
Just want to report that this is working flawlessly now on my H932 LG V30 stock rooted Rom! Couldn't be happier. I worked on this for at least a full weeks worth of hours. I tried everything that I could think of but either wouldn't boot or everything would look good but Playstore would crash when opening. I tried extreme Google removing before flash, just basic Google removing before flash, with patcher, then try FakeGapps, trying to figure out if it was one single file that I was removing that was breaking the install, flashing thru magisk, then twrp, you name it, I tried it. I'm not sure exactly which thing got it to work. But I will say that what cost me this week of frustration was reading a lot of people saying to remove all traces of Google before flashing this. Or at least Playstore, Core, Framework. I tried every combination of light removal to heavy. But when I was finally about to give up for good. Really thought there was no hope, then I said, f*ck it, one last prayerful attempt. And I simply flashed the Rom clean, Magisk, booted, got through setup, rebooted and flashed lastest Nanomod Microg and Fdroid WITHOUT REMOVING ANY GOOGLE stuff first. Installed FakeGapps through Xposed, battery optimizations disabled as usual, etc, rebooted, opened Play Store and literally could not believe my eyes when it actually opened. Went back in to see if somehow the original Play Store hadn't been removed because all I had seen probably 100 times in a row from different flashing sequences was a crash of Playstore at that point. I literally did not believe that it worked. I was shocked that removing nothing and simply flashing the file did it! God, if only I tried this 2 weeks ago, I would have saved hours and hours and hours of frustration and irritation. So I have no idea if it's the new Zip (11/02) that did it or the method. But I'm super grateful and going to send a donation your way. Thanks for everything!
[Magisk] d1n0x:
In the meantime you could have just flashed a custom ROM and NanoDroid.