yashsingh1/xdaforums huggingface dataset:
[Magisk] DoR3M3:
Ahh it looks nicer on your device, on mine it's one long line and it gets cut off, so I can't read all the text.

Anyhow he changed it a few posts back, it now says; "Setup and test microG"...
[Magisk] -Happy Feet-:
Not working for me. Get an bootloop
[Magisk] BootloopedMillennials:
Device- Nexus 6

Codename- Shamu

TWRP Version- Official 3.2.3.0

ROM- LineageOS 15.1 Nightly

Service.jar Status- VDEX (both odex and vdex in system path)

NanoDroid Patcher Version- 20.4

Is it correct in assuming that I have to use a VDEXEXTRACTOR to deodex the rom then flash the NanoDroid patcher?

Because just flashing NanoDroid patcher, it hangs at patching services.jar. At least I let it go 10mins before force rebooting, as device was heating up.
[Magisk] bege10:
See here https://gitlab.com/Nanolx/NanoDroid/issues/31

It is not solved yet.

Edit: I changed to installing LineageOS for microG and only add Play Store from NanoDroid. That needs no additional patching and works on my device. (If you do so, too, thoroughly read instructions on LineageOS for microG home page to migrate from original LineageOS to LineageOS for microG. I first did not and had to flash several times until everything worked.)
[Magisk] SHA_NDY:
MicroG without TWRP?

Is there any chance to get MicroG working without TWRP? For my HTC U11 Life (Android One, running 9.0 Pie) there isn't TWRP available yet (or never will be). Flashing in Magisk without TWRP is not possible right?

Thanks.
[Magisk] Shobit Joura:
I also got bootlooped on crdroid oreo 8.1.....
[Magisk] Nosepull:
My phone (S7 Edge) with current Nanodroid has changed identities - it suddenly starts to identify itself as Huawei device to Google?! Causing all kinds of weird security warnings. What has gone wrong here?
[Magisk] -Happy Feet-:
Not possible.
[Magisk] khnoizer:
Since I'm using nanodroid patcher now, do I need to flash it everytime I dirty flash my rom, even though I'm on magisk mode?
[Magisk] kurtn:
It's not dependent on magisk. After dirty flashing the patcher automatically stars doing the work. If you flash pie ROM, make sure it is deodexed.
[Magisk] marcdw:
By any chance are you using Bromite Webview? If so that may be the reason as it "masks" some things as part of its privacy-oriented feature set. Depending on the ROM I'm on Google sees Samsung mostly on my devices (none are Samsung).

If you don't have the Webview then I don't know. Nothing I know of in microG or NanoDroid that would cause that device change.

LG G3 D851, PAC-ROM 6.0.1, MultiROM, XDA Legacy
[Magisk] Nosepull:
Ah! That's the reason, thanks for the hint.
[Magisk] NotesOfReality:
It may be a bug in your OS font rendering(?) engine.
[Magisk] DoR3M3:
[MENTION=4187311]Setialpha[/MENTION]

I have microG from NanoDroid-microG-20.4.20181230, and the first time I start F-Droid version 1.5.1 it shows in the overhead notification saying there's an update for "microG Services Core" but when you look at the update, it's showing "UnifiedNlP (no Gapps)" instead.

Then if I close and reopen F-Droid the microG update is no longer listed.

I've attached a screen shot running F-Droid for first time showing "UnifiedNlP (no Gapps)" instead of microG Services Core.
[Magisk] guest4711:
That's an old "problem" caused by unified nlp and full micro-G (and Google Play Service) using the same pkg name.
[Magisk] ale5000:
I have never tried but it may work:

- Enable Developer options

- In the developer settings, enable Android debugging (ADB)

- Restart in the stock recovery and flash my OTA zip

My OTA zip is signed with the test keys so it may work (but I cannot grant it).

About NanoDroid I don't know.
[Magisk] AlreadyFree:
Oh, never did mention too that I am using the latest TWRP.

Tried doing a fresh install of my rom but I'm still getting the same results. Tried installing another, newer rom with same results there. Rolled back to NanoDroid 20.2a and that installs fine on both roms. Now makes me wonder if I really did get 20.3 installed that first time and if so, how?
[Magisk] Setialpha:
I added the multiArch and geo.API_KEY now, too, thanks. Yes, libconscrypt_jni.so it's needed for the ProviderInstallerImpl by voidstarstar (see the pull request in the upstream microG repo).

Maybe Maps issue it's related to changes to SafeParcel / GmsPeopleSvc needed? Log contains:

01-10 20:20:56.195 13073 13160 D SafeParcel: Unknown field num 10 in com.google.android.gms.common.internal.GetServiceRequest, skipping.
01-10 20:20:56.195 13073 13160 D SafeParcel: Unknown field num 11 in com.google.android.gms.common.internal.GetServiceRequest, skipping.
01-10 20:20:56.195 13073 13160 D SafeParcel: Unknown field num 12 in com.google.android.gms.common.internal.GetServiceRequest, skipping.
01-10 20:20:56.195 13073 13160 D GmsPeopleSvc: bound by: GetServiceRequest{serviceId=PEOPLE, gmsVersion=15068000, packageName='com.google.android.apps.maps', extras=Bundle[{support_new_image_callback=true, social_client_application_id=80, real_client_package_name=com.google.android.apps.maps}]}
[Magisk] DoR3M3:
I've never seen this before using microG...

I downloaded Lineage microG and had a look through it to see what it was doing in regards to microG and flashed it, and didn't see this issue in LOS microG.

The only thing I noticed different in LOS microG was a lack of permissions added in, and no additional_repos.xml.

So I went back to test this on a ROM I am working on, I didn't want to remove any of the permissions xml files, so I removed the additional_repos.xml and put in the ROM F-Droid 1.4. I then flashed the ROM, started it up, ran F-Droid and manually added in the Repo and microG Services Core showed the name correct. Then I updated F-Droid to 1.5.1 and restared it and the name was still correct.

Next I went back to my ROM and replaced F-Droid in /system/app with version 1.5.1 and flashed the ROM to my device to test it now with the latest F-Droid version. I started my phone, started up F-Droid and manually added in the repo and the name was correct again; microG Services Core.

So for my final test I went back and added in /system/etc/org.fdroid.fdroid/additional_repos.xml flashed this ROM and the problem returned.

I'm at a loss to understand how having the additional_repos.xml added into the ROM is causing this problem, but I have tested this several times, and everytime I have it in my ROM the name for microG always shows up as UnifiedNlP instead.

Hmm odd... :eek:

P.S. [MENTION=4187311]Setialpha[/MENTION], seems to be some odd problem using the additional_repos.xml
[Magisk] Tomatot-:
Hi, I own a OnePlus 6 and I run Pie. I've used Nanodroid-MicroG on a few ROMs and it has never failed, however, on one ROM, it makes the ROM bootloop (Omni).

According to the ROM's dev, it's a problem regarding permissions. That's his words : "every privileged app must declare its permissions in an xml and installed on system."

Do you know what he's referring too? And do you know how you/I could edit your installer compatible with the ROM? I've tried to look up for solutions but it's beyond my knowledge... Thanks. :)
[Magisk] Setialpha:
I'd need a logcat from bootloop to check which ones are missing.
[Magisk] Setialpha:
About the non-working signature spoofing on Havoc OS: it should pretty simple. Go to Settings > Havoc Settings > System > Allow signature spoofing must be ticked. Should be, because it doesn't work. Regardless whether enabled or not, Havoc OS doesn't spoof the signature. In the settings I can see that the property 'allow_signature_fake' is properly set to '1' (enabled). I'd say this is a bug in Havoc OS.

I can't reproduce the bootloop on crDroid 5 (Pie) under no constellation with NanoDroid 20.5 development version. Either the bug was fixed with 20.5, fixed in a new crDroid build or is simply not reproducible by me.

Last on the list is OmniROM...
[Magisk] Shobit Joura:
Yeah no issue in crdroid v5 ...but bootloop occurs in crdroind v4.7
[Magisk] Setialpha:
Ah, I see.
[Magisk] Shobit Joura:
And it occours after enabling device registration..etc etc ...if everything is left unchecked / unenabled then rom boots fine but once they are enabled the rom doesnt boot and is stuck in bootloop.....
[Magisk] TechTiks:
Sorry for the stupid question, but how is the NanoDroid version of microg different to the official version? I couldn't quite get it from the first post. Is it the modified Play Store or is there more?
[Magisk] Setialpha:
There's a link to source on the f-droid repo info page, also in the documentation. tl;dr https://github.com/Nanolx/android_packages_apps_GmsCore/blob/master/README.md

Of course not Play Store, microG is microG,Play Store is Play Store.
[Magisk] HyperCriSiS:
What's the reason that there's a MicroG Nanodroid Version? Why aren't those fixes made in the official version?
[Magisk] bagoes.s:
I've got a suggest from other to make my Nexus 7 more free RAM for using microG on AOSP 7.1, I've installed Gapps pico before.

How to use this? Only flash the NanoDroid microG or what? Can someone guide me ?
[Magisk] marcdw:
Before considering flashing microG, ask yourself how do you use your phone. Are you a big fan of Google apps? Some work, some work but not so well, some not at all. Are you open to alternatives?

You're ROM must support signature spoofing. If it does not then it'll need to be patched. Lastly there's an Xposed module to help if the first two don't apply or work, respectively. Obviously for Oreo and below.

Read the OP and associated links where applicable. Check out Shadow53's site for some good reading.

https://shadow53.com/android/no-gapps/

Peruse this thread as well as those of the main microG and ale5000's installer (sorry, no links at the moment).

The free RAM thing is not really important here. Android uses the Linux kernel. Memory management is more important than free RAM (like in Windows). The old saying, free RAM is wasted RAM.

That's it (my lunch break is over. [emoji16] ).

ZTE Axon 7 A2017U, AospExtended v4.6 ROM, LlamaSweet 0.5 Kernel, microG (NoGapps), Multiboot, XDA Legacy
[Magisk] Setialpha:
Most changes are already sent upstream, but they aren't merged yet, as it should be known mar-v-in is very busy. Some other changes need further testing and will be sent upstream at given time.
[Magisk] Setialpha:
Double Post.
[Magisk] Lithesis:
[MENTION=4187311]Setialpha[/MENTION]

Asking for some clarification regarding deodexing from your doc https://gitlab.com/Nanolx/NanoDroid/blob/master/doc/DeodexServices.md

If I have vdex and odex files should I use both methods? vdexExtractor works fine, but sadly baksmali is throwing bad utf-8 byte on pie.
[Magisk] bege10:
F-Droid shows Fake Store installed instead of Play Store

As long as I had installed LineageOS and full NanoDroid F-Droid correctly showed the Play Store installed and provided updates (NanoDroid repository).

Since the patcher does not work with LineageOS any more I have LineageOS for microG and the Play Store from NanoDroid installed. That works well but F-Droid shows Fake Store instead of Play Store as installed and it does not provide updates any more.

(How) can I fix this?
[Magisk] Setialpha:
Either, or, not both. As both instructions go until the end creating classes.dex, you'd be doing the same thing twice.

It's a very old issue in F-Droid, discussed one page back. You can't do anything about it. The issue needs to be fixed in F-Droid.
[Magisk] bege10:
I understood the discussed issue the other way round, that users complained about updates of Play Store although they had installed only Fake Store. Is it the same issue, no matter which way round?

If it is an old issue, why did it work correctly until I changed to LineageOS for microG and Play Store from NanoDroid?

If there is nothing to do about it, how can I update Play Store from NanoDroid repository or any other way?
[Magisk] mobilism:
Does GCM works need play store or fake store?

When I install full nanodroid Microg and Aurora ,application can't registration .

Full nanodroid Microg and official play store .After application registrated ,uninstall play store ,Microg can't receive messages .
[Magisk] Setialpha:
It's the same issue, it doesn't occur for everyone, so it's just a coincidence.

Simply go to the app, tap on the version you want and press upgrade.
[Magisk] Tomatot-:
All right thanks, I'll try to do take one soon and let you know.
[Magisk] Shobit Joura:
Is v20.5 releasing today???? As in earlier chats it was said that eta was this weekend.
[Magisk] d1n0x:
It'll be released when it's ready, stop being rude
[Magisk] Shobit Joura:
I am sorry if i acted as being rude:crying:
[Magisk] bege10:
OK, now I understand. I thought manually updating would install Fake Store instead of Play Store. It is a pity that updates don't work automatically this way, but that's something I can well live with. Thank you very much.
[Magisk] mobilism:
In nanodroid-microg lacks radiocell backend .
[Magisk] the_Pan:
May be a stupid question, but can I install 20.5 directly over 20.4?
[Magisk] Setialpha:
Ah, yes, will re-upload. Edit: done.

Yes.
[Magisk] TanByv:
Hello having isssues with flashing full package. I ran setup wizard and created config file.

Device & ROM: Samsung SIII Mini (GT-I8190), LineageOS 14.1 (Android 7.1.2)

Signature Spoofing: Natively Supported

Nanodroid Version: 20.4.20181230

TWRP: 2.8.7.3 (Tried with 3.2.2 too)

Root: SuperSU (SYSTEM Mode)

Issue: unzip: write: No space left on device

I clearly have enough space. +6GB should be enough right?

I can flash individual module zips like MicroG only, FDroid only, BromiteWebView and OsmAnd+

Log file attached. Thanks!
[Magisk] guest4711:
You ran out of space on your magisk image. You should increase its size before installing NanoDroid. "Magisk Manager for Recovery Mode" module (mm) is your friend...
[Magisk] TanByv:
Sorry about not writing the root method I totally forgot about it. I use SuperSU since Magisk isn't compatible with my ROM.

Also, using SYSTEM mode.

Now added those in my post.
[Magisk] Tomatot-:
Thank you so much!! Since I'm among the ones that reported issues with Omni, I will try asap and let you know with a log if it doesn't work. :)
[Magisk] marcdw:
The no space left refers to your /system partition no doubt, not your internal storage size. Depending on your device that partition may be small. If it's something like 512MB there might not be enough space for ROM and a lot of extras.

Check whatever logs were generated as well as recovery log to verify what exactly ran out of space.

Moto G5s Plus XT1806, MultiROM, XDA Legacy
[Magisk] Libre111:
Installation failed on Lineage 16 Unofficial Poco F1 ROM.

Then I tried installing the patcher zip first, the patch installed no problem, but again Nanodroid installation failed.

Am I missing something?
[Magisk] guest4711:
Without a proper description how you tried it and without logs (save recovery log in TWRP after failed installation and attach it here) it's near impossible to tell.
[Magisk] Koont:
Got this baby running on OmniRom for OnePlus 6t. Thanks
[Magisk] Libre111:
I tried by rebooting into TWRP and flashing the latest Nanodroid zip. I will try and find the log files. Error message is:
[Magisk] TanByv:
Thanks for the response, yes my phone only has 8GB of storage and system partition is probably 512MB or 1024MB...

I'm currently repacking the full zip with all the "open source apps" resized to 1 byte to create a "lite" package that weights 88MB (308MB before, 400MB when extracted).

Hopefully it will work. I'll edit this when I get the chance to test it. (Today)

Edit: Installation works perfectly. Everything installed correctly and working. Maybe we should get a lite package that doesn't have apps in them to further support older devices with low storage.
[Magisk] Shobit Joura:
Yeaaah , from this update location strted working android pie roms!!!!!

Thanks all the devs for your time and all things which u do for us !:good:
[Magisk] Setialpha:
Why? Just don't install what you don't need. NanoDroid is configurable, see 'Alter Installation' in the documentation. The microG package does not include any additional apps, so you should be good to go already, btw.
[Magisk] Setialpha:
Ah, I see it's a Yalp Store issue. Will look into it, thanks!
[Magisk] Setialpha:
Could you please test this package, whether it works with OmniROM + Yalp Store (or Aurora Store)? Works fine here on NitrogenOS.

NanoDroid-microg_20.5_PrivAppTest.zip
[Magisk] Lithesis:
Hi [MENTION=4187311]Setialpha[/MENTION]

Installed ~2h ago full package of NanoDroid, setup everything, installed some stuff and well location is not working ._. In microG self check everything is checked beside network-based location.

PocoF1 on AICP (https://xdaforums.com/poco-f1/development/rom-aicp-14-0-p-9-0-beryllium-t3888617), has native sig spoofing. Attached logs from installation and logcat while using Osm and google maps via firefox.

It was clean install btw.
[Magisk] Setialpha:
Did you read Issues > unified Nlp?
[Magisk] Lithesis:
Ah yes should have added that. Executed all three commands, rebooted few times, still no dice. No Blokada installed, I have pihole on local network but https://location.services.mozilla.com is whitelisted.
[Magisk] Setialpha:
Looks like OmniROM? In my tests on my OnePlus 5T I also noticed that on OnePlus 5T OmniROM only GPS works, but no Network Location. Haven't found a fix yet, but using OxygenOS anyway.

Does doing it the over way round fix at least GPS (run as root)?

novl -r com.qualcomm.location

and reboot.
[Magisk] Lithesis:
Can't say if looks like Omnirom. Never used it. I've tried to flash it before AICP but 2 latest version were bootlooping even without Nano so I gave up :)

I've tried the command already dunno if it helped. Maybe to be precise, geolocation is not working. It finds my general location.

Here some stuff from logcat which is wierd:

01-14 20:14:58.957 1121 1121 W LocationManagerService: no network location provider found
01-14 20:14:58.958 1121 1121 E LocationManagerService: no geocoder provider found
01-14 20:14:58.959 1121 1121 D LocationManagerService: Unable to bind FLP Geofence proxy.
01-14 20:14:58.960 1121 1121 D LocationManagerService: Hardware Activity-Recognition not supported.
01-14 20:14:58.961 1121 1121 D LocationManagerService: Unable to bind ActivityRecognitionProxy.
[Magisk] Setialpha:
I've seen that aswell. Ah yes, I've overlooked the "AICP" part. Is it AICP Oreo or Pie? I've noticed that some ROMs (including OmniROM Pie) seem to no longer allow to bind microG's bundled uNlp, though I don't know whether by accident or by purpose - though the maintainer for OnePlus 5T didn't react to my post in this regard...

The Issue was also reported over at [MENTION=5627087]ale5000[/MENTION] thread, see: this post. Could you upload the file /system/framework/framework-res.apk, so I can check? Thanks.

If that's the case the ROM developers could fix it easily in a new ROM build.
[Magisk] TanByv:
I meant the full zip little typing mistake there sorry and I also just figured you can configure the standalone packages, my bad. Should've read the readme better...
[Magisk] Lithesis:
There you go https://www24.zippyshare.com/v/FeNApF6o/file.html. It's a pie rom.

If it's the ROM issue I'll ask the devs.
[Magisk] Setialpha:
Hmm... framework-res looks fine for this ROM. I'm not sure what's the issue.

Could you post the log from the SysTest package, please?
[Magisk] Lithesis:
Here.
[Magisk] Setialpha:
I'm sorry I don't know what's causing the issue, except it may be a ROM bug.

* Log says no location provider is installed, but it is

* framework-res is looking for the right package

* SysTest doesn't report any conflicting location provider

Edit: maybe try the following 'novl -a FusedLocation' as last instance. And reboot.
[Magisk] Lithesis:
Did not work :(
[Magisk] Tomatot-:
That's exactly the same installer as the one you share except it has fixed permissions right? Just to make sure I can use the normal .nanodroid-setup file as well as the uninstaller if something gets wrong.

So right now I'm running Omni with Nanodroid (but with the 0 value regarding stores, so I don't have any stores installed), can I just edit the nanodroid-setup file and flash the file you shared like an update?

EDIT: it worked!!! Amazing man, what a legend! Thank you so much for your support. May I share the file with other people using Omni on OP6 or should I just wait for next release to officially state that your installer full works with Omni now?
[Magisk] DoR3M3:
Yeah patched Play Store, good job!

By the way I still like;

<string name="gms_settings_name">microG</string>

<string name="gms_settings_summary">Setup microG</string>

LOL ;)

What are all the new permissions added to com.android.vending used for, why the change?

Also for users that don't use the Play Store and have FakeStore installed, is there something that can be done to either FakeStore or the Play Store, so that FakeStore is not recognized by F-Droid as Play Store? Otherwise it's always telling you there's a Play Store update, also not sure if someone by accident trys to update it, if it would cause problems. Maybe it's just more of an annoyance constantly seeing the update there, but it would be nice if this could be changed.

Keep up the great work!

Thanks
[Magisk] Setialpha:
Ask Google what the permissions are used for in particular.

You can't update Fake Store to Play Store, different signature, so you can disable the update notification for Fake Store.
[Magisk] -Happy Feet-:
I don't know if this is an microg Bug. But sometimes, after an update my background shows the last installation screen of an app. I must restart the device..
[Magisk] oF2pks:
Pie uses new Power/StandBy per app : https://developer.android.com/about/versions/pie/power ; on my microG Treble/GSi, I noticed location was sometimes failing , but was working fine when com.android.location.fused was exempted from BatteryOptimisation (like gmscore is).

My (fdroid) app_PackagesInfo shows inactive apps in green (plus many more infos: read_logs, ...)

So [MENTION=5166752]Lithesis[/MENTION] [MENTION=6754189]Shobit Joura[/MENTION] can you toggle FusedLocation to NotOptimized and reboot to check location efficiency ; I believe GoogleGmsCore has a specific wake for that when location is turn on (?). Also FusedLocation doesn't seem to consume battery https://android.googlesource.com/pl...+/master/include/hardware/fused_location.h#26

After reading https://android.googlesource.com/pl...ore/java/com/android/server/SystemConfig.java plus opengapps example, I decided to use attached /sysconfig/xxx.xml (good battery & deep_sleep)

Finally com.google.android.gms should be added to <string-array name="config_locationProviderPackageNames" (& <string name="config_defaultDndAccessPackages") by devs ; this way location permission of MicroG is directly toggled by LocationSettings central on/off (?)

Can someone point an app using explicitly com.google.android.maps.jar ( [MENTION=6204913]n76[/MENTION] ? FlightRadar24 v6.6.0) .
[Magisk] Setialpha:
Again what learned. I'll test this with Omni on OP5T.

Edit: getting closer on OmniROM, unified Nlp now registers, but is not yet fully working. log still says

W LocationProviderProxy-network: Odd, no component found for service com.android.location.service.v3.NetworkLocationProvider
W Odd, no component found for service com.android.location.service.FusedLocationProvider

which is odd, as both microG / uNlp provides 'com.android.location.service.v3.NetworkLocationProvider' and 'com.google.android.gms' is part of 'config_locationProviderPackageNames'.
[Magisk] n76:
An app that uses the Maps v2 API? I wrote Spawn of Acastus to do a couple of things. First to give me a replacement for Address2GPS, second to allow me to enter arbitrary addresses into microG's geocoder. But it does a map display of the results, so it is using the Google Maps v2 API as implemented by microG to do that.

microG's Maps API implementation is far from complete and bug free. While it works for my simple app, and it seems to be used by the Toyota Entune app successfully, it fails horribly on CalTran's QuickMap.