yashsingh1/xdaforums huggingface dataset:
[Magisk] guest4711:
No. Both are working. When you are inside you get the location from network location (blue marked) (depends on your drivers whether thid is from WLAN or mobile cells), when outside from GPS (red marked, WLAN may be not available there).
[Magisk] PriteshChauhan:
How to get gmail app working like in ale5000 mod?
[Magisk] JACC (THE FLASH):
A question, which are more advisable to use? The OpenGapps or NanoMod??
[Magisk] Setialpha:
Dunno, I don't use that.

I guess you mean OpenGApps or microG, 'cause NanoDroid can be installed without microG and thus is compatible with OpenGApps, too.

While the GApps Vs. microG discussion was held already a quadzillion times the tl;dr is: microG if you care about privacy, if you don't, or if you're forced (by work or whatever) to use apps not working with microG, then use OpenGApps.

Further discussion on this topic should go into the microG thread.
[Magisk] TevW:
Hi, I'm currently follow the guide you linked to deodex my S8, however extracting my services.vdex results in 2 files called services_classes.dex and services_classes2.dex. I tried continuing the rest of the guide using the first file as it had a larger size, but the zip -d command resulted in it saying nothing to be done, and the phone doesn't boot after pushing it.

Any advice would be appreciated. :)
[Magisk] ale5000:
For me it works as is.
[Magisk] cmonty14:
PlayStore error: Error retrieving information from server RH-01

Hi,

I have installed latest NanoDroid over version 17.

I didn't face any issues with 17, but with 18.2.20180916 I get this error with PlayStore:

Error retrieving information from server RH-01

I have ensured that Self-Check reports no errors (see attachments).

How Can I fix this error?

THX
[Magisk] cmonty14:
Hi,

I want to use function "Smart Lock", however this is only available with Gapps.

Or is there any other option to get this function? Or is there a fork of "Smart Lock" available?

Would it make sense to install Gapps and then install NanoDroid incl. MicroG?

THX
[Magisk] temporarium:
Should we wait? Or is the current release stable?
[Magisk] Setialpha:
You can't use GApps and microG together.
[Magisk] Setialpha:
Force-Close it once and start ut again. This issue occurs since forever, not new, but not all users are affected.
[Magisk] cmonty14:
I tried this already, but it's not working.
[Magisk] Setialpha:
I can't reproduce that. What's the log?
[Magisk] Setialpha:
18.3.20180920

Hi all, verson 18.3 is now available.

ChangeLog since 18.2:

## 18.3.20180920

### Bug Fixes

* Patcher
* during installation get rid of old addon.d

* CommonInstaller
* switch back mode detection to 17.x behaviour

### General Changes

* On-PC framework-patcher
* removed for now, broken beyond Oreo and does not work on odexed ROMs
* a better implemenation will follow

* Force-Debloat script
* removed as NanoDroid-Overlay works in System Mode, aswell now

* Patcher
* add unifiednlp patch by Tom Vincent

### Updates

* automatic
* Substratum (1006)

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] Setialpha:
it doesn't matter whether 'zip -d' fails or not, but I forgot a '*' in the 'zip -j' command, so I suppose you haven't added classes2.dex. I updated the doc.

Just for the record: if you're below Android Pie, the Patcher will de-odex on it's own. Manual de-odexing is only required when the Patcher fails.
[Magisk] TevW:
Well that brings me on to another glitch I found :eek:

When running the patcher, it crashes and forces my phone to restart.

It reaches

++ services.jar status: VDEX

Then it slows my S8 quite considerably, and restarts. I can launch my ROM fine after it, but it isn't deodexed, or patched.

I originally thought it might've been because it was VDEX as I'd never seen it before, but I guess not. I'll retry the manual method as you've updated, and update. Thanks for your help btw!

UPDATE: Manually deodexing did not work. Phone still crashed.
[Magisk] DoR3M3:
[MENTION=4187311]Setialpha[/MENTION] hi, I wiped the phone all over, started from a fresh install. I installed NanoDroid-microG-18.3.20180920 and nupd mg still fails, same message and I attached the find log for you before on another post, not sure if you saw it...

I attached a screen shot of the message, and I attached the find log.

By the way, I just got a OnePlus 5T. Not sure if having a find log helps for support, but I've attached it, find_op5t.txt

The find.txt is from the Essential.

Thanks
[Magisk] smigima:
Thanks for such detailed answer! :)

I've managed to get it work. I've updated DejaVu, and turn on wi-fi and it started working, so I guess it needed to download some data about hotspots.

Now it's working with wi-fi turn off ass well.

Thanks again, you're the man!
[Magisk] immelman3:
Hi, I've always used your amazing work on TWRP and I really wanna thank you for this amazing work.

Today I tried the magisk module installation on a new phone and I noticed it is not able to patch my lineage os 15.1.

Is the "patcher" zip supposed to work on magisk too or is it a recovery flashable zip only?

In any case thank you from the bottom of my heart
[Magisk] guest4711:
DejaVu stores the locations you have visited. So it will know more and more places if kept enabled. It can -per design- not work on places you visit for the 1st time.
[Magisk] lokalkey:
RH-01

have the same error too - my solution:

disable playstore - delete all data and cache - delete your google acc - (i made newstart, not sure if needed) - login to your acc - this solution works for me
[Magisk] smigima:
But it needs enabled wi-fi to be worknig? I was under the impression, that it collect data from mobile internet, not wi-fi. If so, I'll enable wifi to help it collect data.
[Magisk] iacchi:
It actually uses both.
[Magisk] lambroslnk:
In my case all I have to do is delete data and cache on the Store app, then it opens normally. After an hour or so it stop working and shows the error.

So since I do not use it often, just to install an app that I have purchased, I keep it frozen and everytime I wanna use it I just delete data/cache and it works flawlessly.
[Magisk] d1n0x:
I would suggest you also download local GSM backend from F-Droid and download cell database for your country.
[Magisk] Setialpha:
I'll check it out later today, been busy, sorry.

I suppose it's because you're using a Stock ROM, let's see how much the GApps removal mechanism can be improved further.
[Magisk] Setialpha:
About RH-01 error some are facing.

Luckily I have a Nexus 6 as backup phone, addtionally to my daily driver OnePlus 3T, so I could finally reproduce that error it seems. For some reason or another it seems to depend on whether Data Sync is active prior adding Google Account or not? At least it seems so from my observations. All facing RH-01 issue do the following:

System > Accounts > Remove Google Account

System > Accounts > Disable Account Data Syncronization

System > Apps > Play Store > Clear Data

System > Apps > Play Store > Grant all permissions (also check if signature spoofing is granted)

After all is set in microG self-test after doing the above steps, open Play Store and re-add your account.

You may have to close (recent apps > swipe it away) the Play Store once - et voila, it works properly again.

Please test if this works for your all aswell.

<<<>>>

on a side-note: This commit by github user sualk-27o solves SafetyNet imcompatibilities with some apps since API 1 was deprecated. It does

not

change your attestation result, it fixes that several apps failed to get any result at all.

I'll roll-out a new release with that microG GmsCore bundled very soon. The majority of you, for which 'nupd' works, can already update to a new build including this fix and enjoy all their apps again, which failed to attest recently, using 'nupd mg' as always.
[Magisk] Setialpha:
It's only TWRP-flashable for now. For Magisk Manager support more work would need to be done. It's on the agenda and likely fixes some incompatibilities I'm/we're currently facing, but no ETA.

Thanks for those kind words.
[Magisk] Setialpha:
18.3.1

Hi all, version 18.3.1 is now available.

What's new?

moved GsfProxy from app to priv-app, which may resolve issues with stock ROMs

merged latest upstream microG GmsCore changes, including working SafetyNet API 2 attestation

Full ChangeLog

## 18.3.1.20180921

### General Changes

* Full, microG package
* move GsfProxy from /system/app to /system/priv-app

### Updates

* automatic
* QKSMS (3.5.4)
* Amaze (3.3RC5)

* manual
* microG GmsCore (0.2.5.13280-dirty)
* Play Store (11.8.09)

Download links

Download from Nanolx (AFH will follow tomorrow).

Bug reporting

In case of errors, please provide

/data/adb/MODID_log_INSTALLDATE

/data/adb/MODID_twrp_INSTALLDATE (TWRP Installation)

logcat (if applicable)
[Magisk] the-her0:
hey, how do i, if i may ask, include nanodroid in my rom? i'm wondering what i have to do in order to include this into a rom i'm working on, please redirect me to the previous answer if you have already answered the question
[Magisk] sxml2015:
NanoDroid-microG-18.3.1

No installation package？
[Magisk] DoR3M3:
[MENTION=4187311]Setialpha[/MENTION], I know you're busy, don't mean to be a bother, you're awesome dedication is greatly appreciated! :)

By the way NanoDroid-microG-18.3.1 is not installing, I flash it, but when I boot into the phone it doesn't appear.

I wiped and did all this on a fresh install of Oreo too, by the way, no updating...

I've attached TWRP /tmp/recovery.log and logcat.

Thanks
[Magisk] Voldemort13:
GSyn Adapters ?

What are the GSyn Adapters?
[Magisk] Oswald Boelcke:
GSyn Adapters = Google Sync Adapters!

For more information on them search XDA and the web; such a search might leed you to e.g. this page: https://shadow53.com/android/downloads/google-sync-adapters/
[Magisk] YamiYukiSenpai:
Is there a way to fix the error where microG couldn't connect to Google's servers? I got an email from Google that seems to have confirmed that my Google account successfully logged in, even though that error showed up afterwards.
[Magisk] Voldemort13:
THANKs

Oh they are just Google calendar and contacts sync. Thats great that they are not working! I dont want them I use my nextcloud with davdroid for it. Just wish xposed and selinux enforced wouldbe already on Pie roms :crying:
[Magisk] 7root:
Hello,

I'm having difficulties with patching my ROM.

I'm running NitrogenOS based on Android 9.0 Pie on my OP3 and Signature Spoofing seems to be broken/not implemented right now. ROM is deodexed.

When I flash the NanoDroid patcher, the script gets stuck on "patching services.jar" forever. I tried waiting a couple of minutes, but eventually I have to force reboot. Is it supposed to take that long or is something broken?

Edit: nvm. Apparently patching really takes 10+ minutes
[Magisk] Setialpha:
They are not installed by default, I suppose that's why they don't work.

I don't see the point in them either, but some seem to want them.
[Magisk] Setialpha:
If you mean rh-01 error in Play Store, see a few posts back. If not, I'd need a more precise description what doesn't work.
[Magisk] Setialpha:
TWRP log shows installation is fine. Maybe it is bacuse A/B? I'll check the logcat later.

Did you try installing Magisk first and then NanoDroid? I'm just wondering whether that works.

I don't own any A/B device, thus I'm fixing bugs blind.
[Magisk] Setialpha:
What exactly do you mean? Apps? Scripts? microG?
[Magisk] YamiYukiSenpai:
This happened to me before. I re-flashed Magisk, which worked for me

---------- Post added at 04:22 PM ---------- Previous post was at 04:04 PM ----------

This didn't work. Data sync is currently disabled, cleared out data on the Play Store as well, and granted all permissions. However, there was no need to remove my Google account because it was gone after the update. I had to reinstall Magisk in order for microG, YouTube Vanced and other modules to show up, which deleted the data in those apps.
[Magisk] Peter1212:
NanoDroid with MicroG and Gapps

Since Nanodroid with MicroG requires a clean ROM without any previous installation of Gapps, is it possible to install Gapps after setting MicroG up through Magisk? There's MagicGapps that installs Gapps system-less all that'd be required of the mod would be to use Gapps whenever required, even if both can't be activated at the same time would it be possible for that setup to work if one of them is used at a time? Either MicroG or Gapps? That'd solve many a lot of problems that come with MicroG without Gapps and would give an advantage over having Gapps without MicroG. Whenever there's any actual app that doesn't work or support the MicroG GMScore services we can just switch to the Gapps and when that's done and we need to switch back to MicroG for battery drain we can just switch back to it and restart. All it'd need would be a simple restart, but I think that's far easily manageable then to lost functionality or lose battery.

I would love to try it out tomorrow but if anyone seems to want to try it now feel free to do so and pose the results. If anyone has already done so please share their experiences too and if the dev already knows it won't work or would pose far too many other problems please share the facts if possible, I'd love to know if there are more chances of failure than being successful at it before trying it out. I'd still post my results tomorrow.

Thanks.
[Magisk] Setialpha:
You can't have both at once. Switching is in theory possible, BUT app data for basic components conflicts betwern microG and GApps, you you'd need a init script that backups data for the disabled modules and restores it for the enabled. May sound simple, but might not be as much in reality.

I doubt it would be worth it in the long run.
[Magisk] DoR3M3:
Hi Setialpha, well if you think back, we had this problem before, and now it started again. So all I can say is you did fix it before. The last two versions worked...

These are the steps I am doing each time you bring out a new version, because I want to do this all on a clean rom to test, I'm not updating/upgrading.

1. Wipe both slots in twrp

2. fastboot -w

3. Flash Stock Oreo 8.1.0

4. Deodex the rom

5. Flash NanoDroid-Patcher

6. Boot to bootloader

7. Boot back to TWRP and flash Magisk

8. Boot up System

9. Boot to TWRP and flash MicroG

10. Boot up System
[Magisk] Peter1212:
Turning the module off doesn't delete the app data or does it? Last time I tried it left the apps that were not related with GMScore services and everything else was removed. I know switching does sound simple in theory that's why I was asking if anyone has tried it or not before. And the same goes for MagicGapps which says that it removes/stops the GMS services if any of them starts crashing. So I think it doesn't delete anything but normally since they are installed in and through magisk it just ignores those files and when the module is enabled again it starts using those files once more.
[Magisk] Voldemort13:
Good to hear

Good to hear that they are not installed by default. Thats one of the biggest reason for installing MicroG and NanoDroid to get rid of them :laugh:
[Magisk] immelman3:
Hi, I am trying to use the On-Pc framework patcher you mention in the reading since I am not able to use TWRP on my current magisk rooted device.

Yet I am unable to find it in ur gitlab. Would you help me? Is on-pc patcher still a thing or is it deprecated?

EDIT: I've seen you removed it.
[Magisk] psychem:
i'm getting a yellow shield Playstore icon in latest 21st september Nanodroid Microg. so using the previous stable. inox app is not working !
[Magisk] mosolicious:
I'm gonna ask here, as there's a larger change for feedback than other forums, and this is related.

I'm having a really hard time getting a GPS fix using microG. It often takes 10 minutes or more, and even then it can sometimes stop working.

Everything looks fine in microG Settings, I have enabled all location backends, I've been outside, etc.

The problem persists cross-ROMs, as I've tried with the microG LineageOS-fork and OmniROM. It has worked before though, and everything else, ROM-wise, works perfectly. So this is kinda annoying as I rely on navigation on my phone.

Thanks!
[Magisk] d1n0x:
GPS has nothing to do with MicroG.
[Magisk] Apex Predator:
Yeah this is OT for this thread but anyway.... Have you checked your gpsconf file? It's possible you have the wrong NTP server for your region.

You can edit it manually or use an app like Faster GPS, it's on F-Droid.
[Magisk] 1plus:
[MENTION=4187311]Setialpha[/MENTION]

a minor bug report -- a few days ago I was installing LOS 15.1 + Magisk + Nanodroid on one device for a guy, i.e. I don't have immediate access to it, so troubleshooting would be a bit tricky. Anyway Nanodroid itself installs, patcher works, uninstaller works. However setupwizard did not work, so I ended up creating files myself. Basically it seems that aroma installer does not work on that device under most latest official TWRP. That phone was Galaxy S5, international model i.e. with snapdragon 801.

Basically when during flash of NanoDroid-setupwizard-18.3.1.20180921.zip in TWRP when starting aroma installer it actually freezes for a while, then TWRP itself reboots again into recovery.

Update: tried on another device with early 800 series snapdragon (i.e. ARM) -- same problem, setupwizard's aroma installer does not start, causes TWRP reboot.
[Magisk] elraffa:
Hi, I installed microg last version 18.3.1 in viperOS 7.1.2 android, superSU, self check is all ticked, GPS location works fine in any app, all is working great except for google maps. The map pane is visible along with a location marker but with no map content, the app can see my Google's account but don't let me download offline maps. I tried delete data, grant all permissions, terminal nanodroid-perm, install, uninstall, with no success, map content is not showing at all. could anyone help me please. In YouTube vanced I can't log in, it shows "you didn't install the microg as instructed", do you know how to solve this? Thanks for your great work [MENTION=4187311]Setialpha[/MENTION].
[Magisk] hertzschi:
It's a bug in latest twrp.

Just flash twrp 3.1.0.1 and aroma installer runs just fine.

Works on my S5:good:
[Magisk] d1n0x:
Small bug:

I installed Lineage for MicroG on my device and flashed NanoDroid over it using the setup wizard, forced system mode and enabled app override. Didn't select any apps to install, neither to debloat.

Now a ROM update came out. I flash it in TWRP, the NanoDroid backup/restore does its thing and I successfully boot back into the new version, however now some apps like Clock and Eleven are missing. I never selected those apps for debloating.

Had to delete the .nanodroid-x files from my internal storage and reflash the ROM for it to work normally again.
[Magisk] 1plus:
in my experience it does. Getting approximate location apparently helps to get a cold fix. I.e. when location is not known, it takes longer to get a fix.

---------- Post added at 01:37 PM ---------- Previous post was at 01:30 PM ----------

I see. But I would rather not downgrade TWRP. Loads of issues with encryption etc on lesser versions. E.g. I had issues with official twrp builds on oneplus1 (which is pretty much same age as S5).

I'm actually using an unofficial build for it due to concerns with Oreo encryption schemes. I would not recommend to use anything below 3.2.2 for LOS15.1.
[Magisk] mdl054:
I'm having an issue with certain apps not getting GPS location. Apps like Pokemon Go all say location not found but others such as Waze, Satstat, etc all have no issue and find me immediately. I'm done multiple clean full reinstalls and can replicate the issue every time. With gapps it works, without gapps it doesn't. I opened a terminal and typed "su" and "nanodroid-perm" as mentioned in a previous comment and both are registered properly. This makes no change. The apps in question all have permission granted for location. I'm happy to provide anything needed to troubleshoot this if needed. I'm on 9.0 Liquid Remix but the same issue happens on Lineage and Omnirom. Oneplus 6. Thanks for all the hard work!
[Magisk] Fauzi Hamzah:
Any idea use microg to run YouTube ?
[Magisk] DoR3M3:
[MENTION=4187311]Setialpha[/MENTION] I also have a OnePlus 5T I just received, and it doesn't have A/B partitions, only one.

I am also getting the same problem on the OnePlus 5T running stock Oreo, rather the Oxygen OS 5.1.5

1. I installed Magisk, then rebooted the System.

2. Then I booted into TWRP and patched it Deodex with the VDEX tutorial

3. Then I installed NanoDroid-patcher

4. Then I installed NanoDroid-microg

Now when I booted into the system, same problem, microg is not installed.

I'm attaching /tmp/recovery.log and find log for the OnePlus 5T.

I mentioned in a previous post that this worked in the last two versions. If you recall, it started out like this, then you fixed it, now it's back to the way it was when you started.
[Magisk] HemanthJabalpuri:
[MENTION=4187311]Setialpha[/MENTION]

I am running stock touchwiz 4.4.2 rom...

I successfully flashed microG ...

but I am not able to tap signin or cancel in microG login setup wizard.....

Below is logcat taken with SysLog app...
[Magisk] :
Yes, that worked the trick! Clean flash of ROM, reboot then twrp flash of patcher zip (took just over 20 mins) and then I installed nanomod fdroid zip after another reboot. Running smoothly on Nexus 5x RR 5.8.3 #nogapps

https://Telegram.me/NoGapps
[Magisk] Mar-cel:
What does the patcher zip do?
[Magisk] :
It enables signature spoofing without having it integrating in the ROM by default or without needing a pc
[Magisk] droika:
Works fine now on A300FU - thanks a lot!
[Magisk] Indha Lezzio:
Patched RR ROM and installed microg in my S4 i9505.

Fast, easy and amazing!!!!

Thanks a lot, subscribed to the thread and waiting for further staff!!!!
[Magisk] knpk13:
Is the patcher also a magisk module like the other zips,? I'm not sure how to get started.
[Magisk] Setialpha:
No. It patches the services.jar. The patched file is either installed into one of the NanoMid Magisk Modules, or directly into /system if they aren't installed.
[Magisk] JERW28:
[MENTION=4187311]Setialpha[/MENTION] and everyone who uses Magisk Snapshot builds

NanoMod microG 8.0 and 9.0 do not work with the latest Snapshot builds of Magisk. Installing the mod causes a bootloop at the splash screen. Tested with Magisk 5.0-170529 and 5.0-170530 and Magisk Manager 5.0-170529 from XDA member kanjer's github ["here"]https://github.com/kantjer/MagiskFiles[/URL]

Steps:

1. Make nandroid backup of ROM

2. Full wipe

3. Flash rom with built-in Magisk deleted

4. Flash kernel (optional)

5. Flash Magisk zip mentioned above

6. Flash my own private magisk debloat mod to uninstall Magisk Manager 4.3.3 system app

7. Flash Magisk Manager 5.0-170529.apk Magisk mod

8. Wipe delvik/ cache and reboot system

9. Successfully boot phone and Magisk Manager shows everything installed correctly.

10. Reboot to recovery

11. Flash nanomod microG 8.0 or 9.0 no errors in twrp log

12. Reboot system

13. Stuck at the beginning of boot at the splash screen animation

Phone info in signature and I do not know how to capture a log so early in the boot process. Please advise. [MENTION=4187311]Setialpha[/MENTION] I realise you may want to wait to for the next stable magisk release to update nanomod microG. This is just an FYI.
[Magisk] Setialpha:
I already noticed that, but Magisk v13 is not ready for daily use yet, so I'll wait until atleast an official beta.
[Magisk] Mar-cel:
[MENTION=4187311]Setialpha[/MENTION] I got this error in TWRP after flashing 28.05. Patcher zip.
[Magisk] Setialpha:
So where's your /tmp/recovery.log?
[Magisk] pbeckmann:
Next time, please attach the log as an File or use the

tags.

Thanks
[Magisk] Setialpha:
[MENTION=5314891]ELoTRIX[/MENTION]

Hmmm, I see where it fails, but I dunno why for sure. ...

What gives you the following command from 'adb shell', /system must be mounted:

ls -l /system/bin/dalvikvm*

? Did you boot into the ROM once?