yashsingh1/xdaforums huggingface dataset:
[Magisk] Setialpha:
I suppose he means to install something different than PS. Well, use the SetupWizard or read 'Alter Installation' in the docs.
[Magisk] hungvip2001:
Hello. I try to install via magisk but error.

How to fix that? My phone is xz1 running stock sony rom
[Magisk] guest4711:
As I see, your ROM does not have /system/xbin: + ROM has no /system/xbin, using /system/bin instead

So a special handling should be performed. All parts extracted to /tmp/system/xbin must be moved to /system/bin, but imho the script tries to move from /top/system/bin (and does not find the files).

Either you modify the install script yourself or you wait for developers update...
[Magisk] Setialpha:
Actually I tried to cover that case, but made a mistake. Fix incoming soon™.
[Magisk] Setialpha:
17.1

Version 17.1 is now available. Besides the usual updates it fixes installation on ROMs that don't have /system/xbin.

Full ChangeLog

## 17.1.20180507

### Bug Fixes

* CommonInstaller
* fix installation on ROMs that don't have /system/xbin

### Updates

* automatic
* OpenKeychain (5.0.1)
* NewPipe (0.13.3)
* KeePassDX (2.5.0.0beta9-libre)
* QKSMS (3.1.1)
* Yalp Store (0.40)
* F-Droid Privileged Extension (0.2.8)
* Bucket (0.2.1-beta-1253)

* manual
* Play Store (9.9.21)

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] Gr0m03eka:
Many apps keep asking to update Google Play Services even after the 17.1 Nanodroid update. Should I update something manually via terminal?
[Magisk] abacate123:
You must wait MicroG update itself. This should have nothing to do with NanoDroid.
[Magisk] hungvip2001:
Thanks for very fast fixes. Now I installed successfully. But Google play crashing, every Google apps crashing. How to fix this:confused:

I am on stock sony rom
[Magisk] Setialpha:
Dunno? What's the log? Does the ROM have sigspoofing? What GApps were previously installed?

Stock ROMs are more difficult to support.
[Magisk] hungvip2001:
The room has pre- install gapp.

Maybe it is rom 's fault
[Magisk] Dobsgw:
Remove all gapps

Wipe data (or user installed updates of gapps remain and go crazy since system apk is missing.)

You won't be able to just switch from gapps to microg seamlessly
[Magisk] Setialpha:
NanoDroid tries to debloat several GApps, but I dunno which ones are installed on theese ROMs.
[Magisk] Dobsgw:
From my Sony days I remember they renamed most of the gapps and it was really annoying for debloating roms
[Magisk] Setialpha:
They do? They should be punished.
[Magisk] Setialpha:
There might be an issue with Play Store from 17.1, I'll report, soon™.
[Magisk] Setialpha:
I uploaded a fixed Play Store build, I'll upload new zips tomorrow. Meanwhile update Play Store using 'nupd ps' as root, on-device.
[Magisk] FriendlyNeighborhoodShane:
Hi [MENTION=4187311]Setialpha[/MENTION]

Would you be considering some o the changes i suggested here?

https://xdaforums.com/apps/magisk/module-nanomod-5-0-20170405-microg-t3584928/post76445060
[Magisk] PetaByteBoy:
I'm still having the issues I described earlier, but that's not what you intended to fix, right?
[Magisk] Setialpha:
Nope, but a logcat might be helpful.
[Magisk] raptorddd:
i asked before how should i update nanodroid. migrog and playstore.

do i just dirty flash over previous nanodroid. i had NanoDroid-microG-16.5.20180402

but playstore would start updating everytime i opened playstore. so i downloaded NanoDroid-microG-17.1.20180507

dirty flash. but playstore would FC when i hit update app or install. sorry no logs. i hope the new build you have fixes playstore problem.

thanks
[Magisk] PetaByteBoy:
https://zerobin.net/?3d99532161a145e1#kCXW6qZRXfPrg3RK871Oe4bJjSjTr1sdTrtzaN2rF98=
[Magisk] drigg:
MicroG DroidGuard Helper keeps crashing. This is on clean flash of crDroid ROM and Magisk stable. Didn't have this issue back in March. Will try to reflash everything and report back. The Magisk SafetyNet check doesn't work and this error frequently pops up.
[Magisk] :
https://github.com/microg/android_packages_apps_GmsCore/issues/521#issuecomment-381926017
[Magisk] ydd0ras:
Have exactly the same on my crDroid 8.1.0 on my Xiaomi Mi A1. Also on other devices with 8.1.0. Working nice on a Redmi Note with dotOS 7.1.2 and NanoMod 16.4
[Magisk] kurtn:
Google has changed safetynet again. In the long term we have the choice: safetynet on stock ROM or custom ROM without or iOS.
[Magisk] Dobsgw:
Or just wait for a microg droid guard helper update...

Safetynet passes fine on custom ROMs with gapps and magisk (and sometimes without magisk if no system root detected)

So its really just about keeping droid guard helper in line with safetynet updates. Same as the great "google play services is out of date" messages on older versions of microg.

It really falls down to keeping it maintained which is difficult. It seems microg core is getting more attention as it is the main function of the project.

Or hopefully google stops messing with safetynet but the banks and entertainment companies won't like that :/
[Magisk] Setialpha:
Google has updated DroidGuard Helper, as long as microG / microG DroidGuard Helper aren't updated accordingly, there's nothing I can do. But the microG maintainer knows about the issue, just wait.
[Magisk] Setialpha:
17.1a

I re-uploaded 17.1 with fixed Play Store, labelled 17.1a.
[Magisk] rum0s:
Since I'm using NanoDroid-17.1a.20180507 the map functionality in many apps is no longer working. Though Maps v1 library is selected in the installer.

Does anyone have version 16 - there it worked ? :)
[Magisk] Setialpha:
Modified Play Store 10.0.07 uploaded. Issue 'nupd ps' as root, on-device to update.
[Magisk] Setialpha:
The first post contains links to the old versions, too.

But I doubt it will fix your issue, nothing changed regarding microG/Maps in the new version. Also Maps uses API v2 (built into microG), not v1 (which is for legacy apps).

Google is enforcing GApps, by making less Google Apps work on uncertified devices and microG is not yet updated accordingly, so that might also be the cause.

Or you have updated Maps and the new version uses APIs not yet provided by microG.
[Magisk] rum0s:
Many thanks for your answer!

Until now I assumed, that apps using a bulitin display of gmaps use API v1. Thinking that v2 should work flawlessly. :laugh:

As you wrote whether I updated gmaps. I think I do not completely understand how it is working.

The API uses functions to get contents from gmaps online? Is it a problem when googlemaps is installed on my device?

It would be great if you could explain me more.

Besides I couldn't find the older versions (16?) on the mirrors or the server.
[Magisk] AngryLady:
Flashing: Nanodroid MicroG v17.1.a

Rom: OmniROM 8.1 Non-Treble

Root: Magisk 16.4

Phone Encryption: ENCRYPTED

Result: no module detected (not installed)
[Magisk] AngryLady:
Is there a link to download the init.d .zip (nanodroid's version)? Because nanodroid won't installed.
[Magisk] Setialpha:
No logs?

No, it's only available in full package.
[Magisk] iqbal_mahmuda:
I can't open play store. And google, Gboard seems can't work properly. I'm also can't sync contacts. What should I do?

EDIT : I figured out about play store and gboard, but still I can't get google, Gmail, and contact sync to work.
[Magisk] d1n0x:
Why would you want to use tons of Google products still? Look for alternatives or use normal gapps if you can't live without Google.
[Magisk] inVain_theGenuine:
hi, I'm currently on NanoDroid stable 17.0....

when I tried to remove an overlayed app with "novl -r xxx", I have the "remove_overrides: not found" message:

I believe I didn't have this issue when I was on NanoDroid 17.0 beta 1,

or am I missing something?

right now I just delete the "K9Mail" folder on the NanoDroid's magisk partition and delete the K9Mail on the ".nanodroid-overlay" to get the app back...... (in case you're curious, I installed the K9Mail as a "genuine" system app)

I also notice some functions on the xbin folder of the NanoDroid is sharing the same filename as can be found on the busybox (unzip is a thing I can vividly remember).

now I've change the "unzip" on the busybox to "busybox_unzip" and I can see more free ram on my device.

previously, I feel the f-droid 1.3 alpha0 is very laggy so I need to roll back to 1.2.2 (my network might be the culprit at the time), but after renaming all the duplicate on the busybox functions and keeping the ones from NanoDroid...... I have nothing to complain with the f-droid 1.3 alpha0.
[Magisk] cetoo:
how to update tihs perfect module? im using v17.0.201804. but ı search for update methods ı cant find anything. how can ı do?
[Magisk] d1n0x:
Whats that Keyboard you are using?
[Magisk] guest4711:
Simply flash the new one...
[Magisk] inVain_theGenuine:
AnysoftKeyboard, ICS theme.

the keyboard was already there with the NanoDroid, as for the theme I can only find it on Playstore (but I got lost quite easily on the F-Droid :LOL)
[Magisk] iqbal_mahmuda:
Yeah I want to, but I don't want install any google services from them, which is impossible. Of course, I can live without it. Btw, it seems that location didn't work because whenever I open the maps from browser, location icon didn't come out if it sets in high accuracy mode.
[Magisk] :
Tried flashing NanoDroid-17.1a.20180507.zip, but it's stuck at "Found Magisk image". No logs because it didn't install or give out errors. Anyone else with the same problem?

Edit: tried with the latest beta and it didn't work either, I guess it's a problem on my end.
[Magisk] Setialpha:
If you're on Magisk 16.4 it may just be extremely slow. I experienced this once, too.
[Magisk] :
Oh, I actually am. Thanks :)

Approximately how long did it take for you?
[Magisk] Setialpha:
3 - 4 Mins. in TWRP on my Nexus 6, can't reproduce on 1+3T, though.
[Magisk] :
Ok, thx. On my Redmi Note 3 it took more than 15 min, so I tried with 16.0 and if worked.
[Magisk] PokemonTotalWar:
Would it be possible for you to upload the template you use for this? I'm in need of a system/less installer and the one that used to be on XDA is discontinued. It would be greatly appreciated if you could provide a new one :)
[Magisk] Setialpha:
Everything you'd need is in the git repo (Full/META-INF + CommonAddon + CommonInstaller), but it's specialized, thus the same installer for different modules and configuration file support. I currently don't have the time for a generalized and monolithic template.
[Magisk] Setialpha:
Uploaded modified Play Store 10.0.32, use 'nupd ps' to update on-device, as root.
[Magisk] AmirKar:
unfortunaltey it while trying to install it , via magisk i didnt see anything ( it is showed that the module installed) but nothing else,the only thing i saw is "microg helper"

i installed the packaages also, only the patcher always failed.

and i tried via custom recovery while wiping everyhing, but my phone got brick so i used the back up,

i did every step via the guide, but nothing work, i may miss something i think...

help someone ? :)
[Magisk] anunaym14:
I have flashed two modules - MicroG and FDroid!

2 issues I have faced with MicroG is that in TWRP it showed Maps API not installed, and the second thing is that whenever I install a google app, and try to sign in, it says account already exists and I can not processed without adding another account!

If you want I will provide you the logs!

Thanks in advance!
[Magisk] Setialpha:
You have to tell the installer to install Maps API v1, else only v2 is installed. See 'alter installation' in first post.

You need to grant Google App phone/contact permission in Settings > Apps > (APP) > Permissions. That's normal with microG, not related to this module.
[Magisk] American_Jesus:
Having so issues with battery drain!

With gapps the battery drain over night was about 2%~5%, with NanoMod ~50%+ .

Knowing some other users with microG installed, they no experiencing the same issues, but i didn't test microG "natively" installed on the system.

I've only installed NanoMod-microG and NanoMod-fdroid (both 7.2.20170508)

This a report to try to figure out what or why is draining so much battery, people who tracks battery usage see the wakelocks and background usage.
[Magisk] Setialpha:
I don't have that issue, so please provide additional infos like logcat and battery statistics.
[Magisk] American_Jesus:
I'm going to try on next full charge.

I'll install microG and use it on next 24h to compare it, then re-enable the mod and make some more testing and try to create some logs.

Don't know if it is microG fault or some other app causing the problem.

Here's some battery stats with NanoMod-microG

Battery usage

Wakelocks
[Magisk] culiacanazo:
It certainly would be another app, try this, really simple solution https://xdaforums.com/showthread.php?t=2179651

Edit: the thing with your last post is it shows you ALL usage.

With the solution i provided, you charge it fully before going to sleep, unplug it, and don't touch it again until the morning. Then, first thing go check out the app and see what really kept your phone awake.

Far more accurate ;)
[Magisk] American_Jesus:
Thanks, ill try that app

I've attached a logcat

adb logcat -b all > logcat.log

PS: was too big, needed to compress it, use zcat or extract it.

Edit:

After searching some posts, [MENTION=7408621]noc.jfcbs[/MENTION] also reported having a similar issue here

I'm using a similar ROM but with Nougat (7.1.2), don't think that's the cause.

Can't find similar issues with microG installed in system (not saying the problem is it with NamoMod)
[Magisk] Oswald Boelcke:
Different to your issue, I only experienced the problem with the "full" NanoMod package. No battery issue at all with NanoMod-microG; however, I don't used NanoMod-FDroid due to no need.

BTW: I'm on Resurrection Remix N-v5.8.3 i.e. somehow Nougat 7.1.2, too.
[Magisk] westkone:
Hi,

I'm running ZeNiTy-RR-Evolution ROM (android 7.1.2_r8) on my OnePlus 3T.

I have Magisk v12 installed with Viper4Android, iYTBP and Nanomod modules enabled.

I need to pass SafetyNet check in order to install some applications.

So, I've enabled Magisk Hide and microG SafetyNet option (with officials servers option ticked in advanced tab).

But everytime I check SafetyNet status with Magisk, it fails.

I also have some random microG DroidGuard Helper FC.

Other than that, microG services are working fine.

I'm using Youtube and Play Store without any problems.

Edit : SELinux is in enforcing state.

Edit2 : added 'logcat -b all' output
[Magisk] Oswald Boelcke:
I'm also on a (different) RR version with SELinux to strict; however, despite Magisk in the hide mode I fail the CTS check. I don't mind as I don't need SafetyNet. My personal guess: My ROM and kernel (probably yours too) reveal details of our systems that aren't good for Google.
[Magisk] anunaym14:
Yes, by deleting the app and giving permissions did the job!

But....I downloaded google app so as to use google now cards with pixel launcher and the assistant but whenever i try for the assistant i get into the now cards window which apparently loads forever and i not getting the now cards screen by swiping left on home screen!

Thanks in advance!
[Magisk] westkone:
Thanks for the quick answer.

So, I will repost on the ROM thread as it seems to be ROM/kernel related.
[Magisk] pbeckmann:
Hey,

just a small PSA: There is an updates Version for the Privileged Extension of FDroid.

And a small bug: Play Store shows me permanently a banner with "Looking for security updates" does somebody else have that too?

Greetings
[Magisk] schorsch.funke:
Yes with RR from Zenith I have it to. But no battery drain or so with it. I disabled notifications for play store
[Magisk] anunaym14:
Also one thing..The XDA Labs app is showing an update to the Play Store...shall I do that.?
[Magisk] skdubg:
you cant update it
[Magisk] Setialpha:
Nope, you can't. Also I can't update my modified version to 7.8 yet, as apktool does not yet properly support InstantApps.

1. Updated

2. I don't know the cause of that. It happened for me once on crDroid but went away on clean install, never experienced on RR.

See 'Issues' in first post for the fix, the microG DroidGuard Helper FC is known.

On a general Note: Users of RR 5.8.3 that experience battery drain should try a different kernel (or try different settings), the issue is ROM related and reported across multiple devices, independently of this module or microG or whatever. I will still have a look at the logs, though.

On Moto X Play I'm using RR 5.8.3 with PhoenixKernel, no drain or anything.
[Magisk] anunaym14:
Setiaplha, You missed this I guess..
[Magisk] Setialpha:
I never used that, so I don't know what this actually is or whether the issue is caused my microG or NanoMod or whatever. But you may provide a logcat and I'll check.
[Magisk] anunaym14:
I will install it again..will share the logcats in some time!
[Magisk] kurtn:
You are on stock ROM. MicroG will not solve your "banned for in app purchase" problem.
[Magisk] Setialpha:
Log?
[Magisk] Setialpha:
Yes, blocked accounts won't magically unban.
[Magisk] AmirKar:
hey.

nope it is not a ban, just an error.

but anyway i wanna use nanodroid.

i installed it via magisk, and it is applied as module, but for some reason i dont see anything.
[Magisk] EREVtov:
thanks!

thanks so much, it is works.

but however while trying to play so online game , it is tells me it is wont work cause there is not google service working.

is that may be a conflict? or it is could be fixed and i just did something wrong?

thanks for the help :)
[Magisk] kurtn:
Google play games is not implemented in microG
[Magisk] Setialpha:
10.1.08 uploaded.
[Magisk] raptorddd:
i always have this problem. playstore works okey but when i want to download app or update app it crashes. am using latest stable

but if i delete phonesky and flash myself a flashable old playstore v 9.1.24 i think then i can download and update apps.? it just the plasytore inside your zip that causes crash

log attached.
[Magisk] evilvoice:
Is that a built in command? I've never heard of that being used to update Google play. Any info on it? Thanks
[Magisk] Setialpha:
https://gitlab.com/Nanolx/NanoDroid#nanodroid-upd
[Magisk] abacate123:
Yes, it's. Remember that the play store apk included within this module is modified to allow in-app purchases with microg. That being said, that's why you need to update it manually, either updating the whole module when an update it out or through this built-in terminal command said above.

:)
[Magisk] LSS4181:
I've been using the latest Nanodroid for a few days (on my Zenfone 2 Z00A, with latest GA ROM), and am having a few questions:

1. The DroidGuard helper is crashing (with latest Magisk 16.3), so I couldn't get Safety Net working (despite having enabled it in microG settings). The Safety Net check in Magisk will simply say "The response is invalid."

2. The Play Store is still able to attempt to download the latest update to update itself (of course it couldn't), I don't know if the auto-update mechanism could be patched, at least disabled, to avoid wasting unwanted battery or data in the background.

3. If I need to add/modify/remove features provided by the full Nanodroid package in the future (such as adding or removing provided apps), what procedures are needed? Could I just modify the specific configuration files then reflash the full Nanodroid package, or do I have to start the ROM over (clean flash)? (EDIT: As for provided apps, I've installed a few manually before, from F-Droid, do I need to remove them first to avoid conflicts, if I try to let Nanodroid package include the ones already installed?)

4. Had anyone here with success using Wear OS (formerly Android Wear)? I want to use Nanodroid while still be able to get the functionalities on my AW 2.0 powered smartwatch working.

5. It seems the detailed list of debloated apps page isn't there anymore (the link on the OP is now 404). Is there an updated link about it, as I need to know which stock apps got debloated that I might need to get myself an alternative to get the functionalities working. (EDIT: It's now called nanodroid-overlay.)

EDIT: Guess for question 4 the answer is no for the time being. I even went as far as factory resetting the watch so I can start the procedures over, but it turned out a disaster. The phone cannot go past the "Getting your watch details..." phase. If I force close the Wear OS app on the phone, the next time I run it I'll be greeted by the main menu, but Wear OS won't be able to connect nor continue the configuration.
[Magisk] sexler:
Hey guys,

When using Android 8.1 with a ROM that supports signature spoofing do you need the Nanodroid-Patcher?

So far I used LOS 14.1 (deodexed) but I want to try a different Oreo ROM. But there you have the problem of the odexed system.

I just want to know if you use Magisk and install Nanodroid microG and enable signature spoofing for it, is it working correctly?

Thank you for your help.
[Magisk] guest4711:
If your ROM supports signature spoofing there is no need to patch it. Simply install microG and perform its self test.
[Magisk] jenslody:
On some roms you need to grant signature-spoofing rights manually for microG it would be

pm grant com.google.android.gms android.permission.FAKE_PACKAGE_SIGNATURE
[Magisk] psychem:
im on redmi note 5 running lineage OS 15.1 20th may 2018 build. after i enter username password and hit accept microG login page crashes. i get notification saying calendar is requesting access to my google account which i just entered. the account is now present in settings--> accounts. when i tap on playstore it brings up the login page again and when i enter username again it says account already exists. when i delete that account from settings the whole process repeats and loops.

when flashing the nanodroid microG package it says shrinking /data/adb/magisk.img to 4160M and TWRP UI gets laggy but completes successfully.

What could be the way out here?
[Magisk] d1n0x:
Use Magisk 16.0 and flash sync adapters
[Magisk] psychem:
im using magisk 16.4 and need access to playstore.
[Magisk] d1n0x:
The "shrinking /data/" thing is because of Magisk 16.4. Uninstall and install 16.0.

Play Store access has nothing to do with Magisk.
[Magisk] psychem:
attaching log for the event
[Magisk] psychem:
playstore opening the microg google login page over and over again is because of syncadapters? that is the main problem
[Magisk] Setialpha:
Nope. More likely because of lacking permissions or a bug. I'll check the log.
[Magisk] guest4711:
Version 0.41 of Yalp Store (Download apks from Google Play Store) is out: https://f-droid.org/app/com.github.yeriomin.yalpstore Connection error to google is history ;)
[Magisk] YamiYukiSenpai:
Why does microG's official site have different version numbers for their apps compared to the ones found on F-Droid and bundled with NanoDroid?

For example, microG's FakeStore's version number is 0.0.2 on their official website, while FakeStore on F-Droid (and NanoDroid) is 10.1.08-all?

And is there a difference if I were to just sideload microG apps instead of flashing NanoDroid?
[Magisk] jenslody:
microG is not on f-droid, but on microG's own f-droid repo, so it should always be the last available version. And what you see in thef-droid app, depends on your settings ( advanced -> show unstable versions or something like that).
[Magisk] Mynacol:
Android apps are uniquely identified by their package name. For Play Store/Fake Store this is identical, because Fake Store tries to spoof the existence of the Play Store.

On the MicroG Website, you only find Fake Store versions (the newest is 0.0.2)

F-Droid sees the installed apps on your device and the apps available in the repositories you enabled.

Now we have the following construct: By the version number of the *Store, you probably have installed the Play Store, which is now at version 10.x...

On the MicroG website are only FakeStore versions with 0.x as version.

But F-Droid sees the Play Store and connects it to the Fake Store, because only the Fake Store is available on the repositories.

For you, it seems that F-Droid has a Fake Store version 10.x, but it is the Play Store with wrong name and description in F-Droid