yashsingh1/xdaforums huggingface dataset:
[Magisk] Setialpha:
17.2~beta2

The second beta for 17.2 is now available.

Highlights since beta1

improved A/B partition scheme taken from Magisk [MENTION=4470081]topjohnwu[/MENTION]

I don't have a A/B device, so please report back

improved GApps removal mechanism

custom microG build with two more additional changes [MENTION=5627087]ale5000[/MENTION]

Fix for microG issue #560

temporarily whitelist app upon high-priority GCM messages

by default install both Deja Vu and Ichnaea nlp backends

switch from stable Amaze build to official beta

usual updates

for reference: 17.2~beta1 announcement post.

Full ChangeLog since 17.1

### General Changes

* Full package
* switch from Bucket/LibreSubstratum to Substratum App
* Bucket was abandoned
* if the user had Bucket in the lists of applications to install, NanoDroid will auto-migrate to Substratum
* add OmniClock and pseudo/debloat DeskClock by default
* OmniClock allows to disable that brain-dead pre-alerts
* switch from stable Amaze build to official beta build
* Full, microG packages
* custom builds for microG GmsCore and microG DroidGuard Helper
* fix Safety Net attestation, Play-Services update-nag
* more information below
* by default install Déjà Vu and Mozilla nlp Backends
* improve GApps uninstallation routine
* CommonInstaller, CommonPatcher, Uninstaller
* improved A/B device support code taken from Magisk 16.6

### Updates

* automatic
* Orbot (16.0.2-RC1)
* (Simple) Calendar (4.1.0)
* (Simple) Gallery (4.3.1)
* OpenKeychain (5.1.4)
* QKSMS (3.3.3)
* Yalp Store (0.42)
* AnySoftKeyboard (1.9.1944)
* NewPipe (0.13.5)
* KeePassDX (2.5.0.0beta11-libre)
* Substratum (997)
* OmniClock (2.0.14)
* K9-Mail (5.503)
* nlpBackend Déjá Vu (1.1.8)
* FDroid (1.3-alpha3)
* Termux (0.64)
* nlpBackendIchnaea (1.4.0)
* Kernel Adiutor (0.9.11.1)
* AnySoftKeyboard (1.9.2055)
* Amaze (3.3.0RC1)

* manual
* Play Store (10.7.19)
* microG GmsCore (0.2.4-126_custom)
* bumped spoofed Play Services version
* fixes 'update your Play Services' nag
* built as priviledged module
* including 'null check for issue 560', see [this pull request](https://github.com/microg/android_packages_apps_GmsCore/pull/561)
* including 'temporarly whitelist app upon high-priority GCM messages', see [this repo](https://github.com/ale5000-git/android_packages_apps_GmsCore/commits/master)
* microG DroidGuard Helper (0.1.0-17_custom)
* fixes SafetyNet attestation with microG
* see [this pull request](https://github.com/microg/android_packages_apps_RemoteDroidGuard/pull/19)
* MPV (20180627_custom)
* latest upstream snapshot (with additional pull requests)

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] shnapsx:
Is Google maps related apps works? Or microg still have problem with maps api? Can anyone post screenshot of Uber and Google maps app for me?
[Magisk] :
I've just installed this on my device, how do you properly update microG incase an update comes out?
[Magisk] d1n0x:
Just flash the new version. Setialpha is very quick regarding updates
[Magisk] :
Will my apps update while moving from beta1 (system mode) to beta2 systemless?
[Magisk] iacchi:
yes
[Magisk] kelgd12:
Play Store update

Up to beta3 pls.
[Magisk] abacate123:
Beta 2 already has the latest play store (until now when I'm posting this), which is 10.7.19, you can check here in the changelog.

Also, you can check the apkmirror site to see that it's the latest version available now.
[Magisk] xiaoming94:
Calendar sync doesn't appear to be working for me. Contact sync is working just fine.

Any idea on how to fix the calendar sync?
[Magisk] garylawwd:
Go into a terminal emulator and enter

Su
nanodroid-perm

Reboot and it should work
[Magisk] Setialpha:
Uploaded modified Play Store 10.8.21. Use 'nupd ps' as root, on device, to update.
[Magisk] Setialpha:
I noticed that installation through Magisk Manager is broken (once again), will be fixed, soon™.
[Magisk] _Kosmas_:
Just disable this Playstore service:

com.android.vending/com.google.android.finsky.services.ForegroundCoordinator$ForegroundCoordinatorService
[Magisk] piet8stevens:
TiBu

I can no longer run Titanium Backup without it crashing. I have re-installed it to no avail. I do get a warning that with Magisk SU, I may run into problems. Does anyone else have this? Any solutions?
[Magisk] slothdabski:
Working for me. Just clean flashed a room with nanomod and magisk this morning
[Magisk] Oswald Boelcke:
I had a similar issue but was able to drag it down not to be related to NanoMod but to substratum and a theme I'd installed - TiB was no longer FC-ing after I uninstalled the overlays. My solution was that I first uninstalled TiB, second compiled and activazed the overlays again, and re-installed TiB. Since then working fine.
[Magisk] Primokorn:
last attempt: did you dirty flash your ROM and had to install microG again?
[Magisk] HaoZeke:
This is the best, most underrated module EVER.

I'm surprised it's not available from magisk manager yet...
[Magisk] MaurixMystic:
Totally agree

Enviado desde mi A0001 mediante Tapatalk
[Magisk] kurtn:
Off (backup) topic: As you know, I'm searching for a way to receive lineage updates with microg surviving. Dirty flash is the way lineage updates from within settings, i think. That doesn't work well with nanomod module?
[Magisk] American_Jesus:
if you don't wipe /data no, probably only need to patch again (NanoMod-patcher).

Check your microG settings and see if the Signature Spoofing if checked (passed), if not flash NanoMod-patcher again and it should be fine.

Last time i dirty flash my rom (Resurrection Remix), i wiped system, dalvik and cache, and didn't need to patch again. But needed to flash other stuff like Magisk or other kernel mods.
[Magisk] piet8stevens:
Actually, I took me a while to notice the problem - I have now checked my backups and they have not been correctly made probably since I installed Nanomod. So, not sure what created the problem. I will do a clean install of a ROM, magisk and nanomod and watch more carefully whether TiBu works. One remaining thing that might have created it: I have TiBu Pro for which I had to install Play Store. I did that and then disabled Play Store after having run TiBu once (without Play Store, TiBu would not even start with TiBu Pro installed). I will try reenabling Play Store and report back.

Good idea, I tried it, but it did not fix the problem.

Thank you all for the replies.

EDIT: Now, this is confusing. TiBu works again. Not sure which of the changes over the last 2 days has made the difference and why it did not work last night. I did disable the substratum themes, I reinstalled TiBu from zip and when I went to check the Play Store, it was enabled (I had forgotten to disable it when I reinstalled the ROM) and I disabled it again. I am not going to experiment now to find out what exactly made the difference. Thank you again for the replies.
[Magisk] marcdw:
[MENTION=1835735]piet8stevens[/MENTION], which ROM are you using this time with NanoMod on the Axon. I'd like to see if I experience the same behavior. Plus giving me something to play with.

LG G3 D851, PAC-MAN LP ROM, MultiROM, Tapatalk 4.9.5
[Magisk] HaoZeke:
By the way has anyone gotten hangouts working? It's the only thing I can't get to work
[Magisk] piet8stevens:
This is on Blissrom, the penultimate version (0708 if I remember correctly) as I cannot switch to the last one as I have a A2017G. I am now trying to switch to AOKP but having some issues (TiBu: backups unreliable + TWRP restore does not always work) - so takes a lot of time and is risky to switch roms. I never had this on my HTC One (m7) and still have not figured out how to reliably restore a TWRP backup.
[Magisk] Setialpha:
Titanium is written to make use of SuperSU's features. It is unreliable with any other su implementation, that's not an issue of this module, nor of Magisk, but rather TiBu itself assuming everyone uses SuperSU (in their defense: it's been the defacto standard long enough).

Another note: verification of paid apps and substratum themes only work with PlayStore. Just saying, as I read that a few posts back.

TWRP backups were unreliable in early Nougat stages, but since a few months it works perfectly on my devices.
[Magisk] HaoZeke:
My paid apps are ok though.. Titanium works well too.. Though I use a mod.
[Magisk] marcdw:
I updated my bootstack on the A2017U so I could try the latest Bliss. None of the outstanding issues have been fixed so you're okay on that front. As you may have seen I also had to go back to the previous bootstack.

My TiBu backup and restores have been working okay with Magisk. I also use a module that makes the su binary available in /system/xbin (for compatibility) and I have busybox (osm0sis). Magisk's busybox is always off.

Been backing up and restoring in TWRP without issue so far. As you know restores only work if you make /system read/write. Once restore is finished put it back to read only.

I forget, are you encrypted?

I've got Bliss backed up and have restored it a time or two. Not using NanoMod on that one though.

LG G3 D851, PAC-MAN LP ROM, MultiROM, Tapatalk 4.9.5

---------- Post added at 09:07 AM ---------- Previous post was at 08:59 AM ----------

Hangouts still doesn't work with microG.

It can be accessed via the web though.

https://hangouts.google.com/

I think. It will take you to the Play Store by default but if you switch to desktop site it'll change to the Hangouts web frontend. Only downside is everything is so tiny since it's not a mobile friendly site.

That's the only way I know of accessing Hangouts.

LG G3 D851, PAC-MAN LP ROM, MultiROM, Tapatalk 4.9.5
[Magisk] HaoZeke:
I also managed to install and open it with an older apk.

http://www.apkmirror.com/apk/google-inc/hangouts/hangouts-8-1-121732641-release/
[Magisk] piet8stevens:
Thank you. So if I understand correctly, you have su as a module in Magisk on top of NanoMod? Did you make it yourself? Where can I get that? And then you disable the magisk su? And same question for busybox: as a magisk module?
[Magisk] marcdw:
The su module is just a little thing to make Magisk's su available to apps that might look for su in certain locations like /system/xbin. According to the module's OP it breaks safetynet if that's a concern. I now usually flash it right after Magisk.

https://xdaforums.com/apps/magisk/magisk-suxinbind-t3564673

osm0sis' BusyBox. I pretty much flash it with every ROM, from KK to Nougat. The flashable installer knows what to do depending on what it finds. With Magisk it installs as a module. With SuperSU systemless it goes to /su. For all else it goes to the standard location, /system/xbin. If one prefers the latter location you could flash BusyBox before Magisk or SU.

https://xdaforums.com/showthread.php?t=2239421

Not yet using NanoMod on the ZTE. Tonight I'll try with both Bliss and AOKP and see how things go.

ZTE Axon 7 A2017U, PureNexus ROM, Tapatalk 4.9.5
[Magisk] marcdw:
Thanks, but does it work? I've tried that before but all it does is churn and churn. Won't show conversations.

I've even tested ancient versions on my other setups.

When we say it doesn't work with microG we mean it doesn't function. Launching/running has not been a problem. Well, not normally.

Plus I'm not sure it would work even if it were "working". Meaning Google has a habit of disabling older versions. I used to use the DarkMTRL Hangouts (v8 I think) but after awhile Google throws up that " you're version is outdated" thing. Then no longer allowed to use. Forced to update.

LG G3 D851, crDroidAndroid v3.2 ROM, microG (NoGapps), MultiROM, Tapatalk 4.9.5
[Magisk] Setialpha:
OK. Magisk Manager installation was "just" partially broken, only for Full package regarding extra apps, microG and F-Droid have been fine. Fixed in git repo. New beta build will follow tomorrow.

Also I've re-build MPV with proper arm64 support, use 'nupd mpv', on-device, as root to update.
[Magisk] DoR3M3:
[MENTION=4187311]Setialpha[/MENTION] I seem to be in the same situation as ydd0ras;

https://xdaforums.com/showpost.php?p=75582976&postcount=2454

I am also using a Mi A1, running Stock Oreo, and when I flash NanoDroid-microG-17.1a.20180507.zip the only things I see installed are; Deja Vu Location Service - microG DroidGuard Helper - microG Services Framework Proxy

Maybe the A/B partitions?

I hope you'll get this working for the Mi A1 with A/B

.nanodroid_NanoDroid_microG & .recovery_NanoDroid_microG added to Logs.zip

Thanks
[Magisk] Setialpha:
Did you try 17.2~beta2? Also I can't open the zip file it seems to be broken.
[Magisk] guest4711:
There is a problem with xda website: The zipfile contains a httpd-errormsg (403 - forbidden) only...
[Magisk] JDC2389:
I already have beta2 installed, can I flash beta3 over the top or how should I proceed, also thanks for your work.
[Magisk] DoR3M3:
I see you just released 17.3...

As far as this word Try, goes, does this support A/B and should work, so try like this, or you don't know, and just give it a try? ;)
[Magisk] guest4711:
Yes, simply flash the new beta (using MagiskManager or TWRP).
[Magisk] Oswald Boelcke:
Since Wednesday, XDA was under a DDOS attack; a lot of links just led to this error message. I hope the admin's and mod's have been able to defeat the attackers. Currently, it looks to me as pretty normal again.
[Magisk] d1n0x:
I installed the stable over the latest beta and now I'm getting errors about missing Play Services..

Edit: also, it seems to have messed up all my app's permissions. I had to grant them all manually again. After flashing the NanoDroid uninstaller and reflashing NanoDroid, everything works fine now.
[Magisk] YamiYukiSenpai:
Was I supposed to be able to use the Play Store as normal? If it is, is it normal for it to automatically update? The Play services almost updated automatically (just before I disabled it).

Also, I can't use Chromecast on Netflix
[Magisk] bertino:
Cast api is not implemented in microg
[Magisk] YamiYukiSenpai:
Oh. I thought it was since I was able to use it with YouTube
[Magisk] bertino:
Yeah Youtube is the only app that works. I don't know why either.
[Magisk] Setialpha:
Do you have all permissions granted? Including sigspoof for Play Store?

I'll check the logs, soon.
[Magisk] d1n0x:
In my edited post I explained that everything is working now. I set all permissions and uninstalled/reinstalled NanoDroid. No problems anymore :)

It might also have sufficed to just enable all permissions again, now that I think about it :D
[Magisk] Nightshadowxd:
Hi everyone, I have few problems with NanoDroid on HTC 10 Leedroid v5.2.1 (149) Oreo.

First of all, I can't install it via Magisk or flash it through twrp.

After process MicroG does not appears in app drawer. Only crashes from gms and play store.

I can only install them manually by using apks from Setialpha's webside.

After some crashes when I tried to open google play store I figure out that Android WebView is required to login in on Google account.

After installing it, everything seems working great, besides location.

It's small problem, maybe not even related with MicroG or Nanodroid but apps like Google maps or Pokemon Go dosn't recognize my current location. In SatStat I haven't that problem. I tried changing backends and nominatim api server from OSM to MapQuest but that don't work.

Sorry for my poor english :/
[Magisk] Setialpha:
Did you fully setup microG as described in the documentation?
[Magisk] hireshnaik:
Hi

I am facing issue a issue with hangout chat. New Notification are not showing unless I open app manually pls help.
[Magisk] sxml2015:
NanoDroid-patcher

Can't Magisk Manager be installed? failure

inflating: ChangeLog.md

Android 7.0 - 8.1 (SDK 24) detected

device architecture: arm64 ! !

odexed ROMs are not supportedFailed !!

Installation failed
[Magisk] iacchi:
As the message says, you can't install the patcher on an odexed rom. Either you deodex it yourself (not for the beginners), or you find a rom which is either deodexed or with signature spoofing support built in.
[Magisk] Oswald Boelcke:
From my personal point of view much too little information. I'd appreciated if you'd at least mentioned your used ROM and posted the recovery.log (actually in your case as you can't yet attach files to your post, a link to the log e.g. at hastebin):

https://xdaforums.com/general/help/issue-rom-kernel-application-to-consider-t3619338

https://xdaforums.com/galaxy-s3/help-i9305/how-to-how-to-best-phrase-request-to-t3404880

However, just as an assumption due to your brief quotation of the recovery notification your ROM is odexed. @iacchi already provided the right suggestions. Additional information available on Gitlab/NanoDroid.
[Magisk] hireshnaik:
help pls
[Magisk] acestars:
the on-device patcher is failed, attached the logs from twrp and magisk manager. Then i installed xposed FakeGapps, the self check show the spoof signature is checked but the play store is force closed everytime i run it. the logcat just show it killed.

update:

xiaomi redmi note 2, miui 8.0.2.0, android 5.0
[Magisk] d1n0x:
Hangouts nost likely uses FCM, which is not yet supported by MicroG.
[Magisk] hireshnaik:
Thanks. Got it now
[Magisk] Nightshadowxd:
Yesterday, I tried to reinstall rom (few times) and flash magisk, patcher (on first attempt - nanodroid-patcher, in second - tingle), nanodroid with microG via twrp again. Maybe in first try I accidentally missed something in documentation or remove some important app from system, but this time everything seems to be normal. I had microG settings app in drawer. Every permissions was granted, GCM, Safety Net, location were set and phone was rebooted. Unfortunatly, after that I stuck in bootloop. I decided to downgrade rom to nougat 7.0 and everything working well now.

About su nanodroid-perm:

htc_pmeuhl:/ $ su

htc_pmeuhl:/ # nanodroid-perm

package com.google.android.gms found

failed to grant permission android.permission.FAKE_PACKAGE_SIGNATURE

package com.android.vending found

failed to grant permission android.permission.FAKE_PACKAGE_SIGNATURE

htc_pmeuhl:/ #
[Magisk] Setialpha:
if you patched yourself, that's the expected output.

Well, the bootloop needs to be investigated, what's the logcat, dmesg, Magisk log during the boot loop?
[Magisk] abacate123:
[MENTION=4187311]Setialpha[/MENTION], how can I disable the Google Play Protect scan without the Play Services app? It's enabled here and Play Store says "No problems found/Apps scanned at ----" in My apps & games. I couldn't find an option to disable it. I'm on latest NanoDroid stable.
[Magisk] demonoidmaster:
Settings, security & privacy, select play protect
[Magisk] AlreadyFree:
Updated from the latest Beta1 to the newest Stable release and am having some issues now. The Play store can't seem to pull up my list of installed apps to update, it just continuously tries to load without ever resolving it, and all my paid apps are behaving like they are unlicenced. Also, and this might be an fdroid issue, fdroid keeps automatically installing Orbot on my phone without permission. The first time i updated i just overwrote the beta, then to try to resolve the above problems i did an uninstall of nanodroid & magisk, then clean install of system, magisk, nanodroid, patcher. Same problem. All permissions are checked in microg settings. Can't figure it out.
[Magisk] D4ND310:
Have you previously disabled any Play Store updates?

DailyHygeineService, for instance, that most people disable to stop the bkground updater, should be restored and then re-enabled after reinstalling Nanodroid. Just an idea, as I had the same problem before.
[Magisk] AlreadyFree:
Ahh, yeah. That was the recommended solution a few builds back to stop the modified playstore from continuously trying to update itself. I forgot that i had done that. I believe that problem has been fixed in the newest build so that service doesn't need to be disabled anymore?? Nice suggestion though. That fixed my problem. Thanks. Now i just have to figure out why fdroid is insisting on installing orbot.
[Magisk] Nightshadowxd:
This time I tried to flash full package of NanoDroid. Luckily or not, the same bootloop happened after reflashing. I cannot find magisk log in /data/adb.

In order, what I installed:

- TWRP 5.2.2.1 (lastest)

- Leedroid 5.2.1 (r149)

(I removed some applications that appeared in https://gitlab.com/Nanolx/NanoDroid/blob/master/doc/GAppsRemoval.md )

- ElementalX kernel for HTC 10 (3.03)

- For signature spoofing I use Tingle

- Magisk 16.0

- NanoDroid (stable)

Maybe I should try use different kernel, Magisk 16.6 and patch rom by using NanoDroid patcher?
[Magisk] Setialpha:
I'll have a look, thanks. Any particular reason, you're not using the latest Magisk (16.7), it contains many bug fixes since 16.0?
[Magisk] Nightshadowxd:
I just noticed that there is a newer version of Magisk. :D I uninstalled NanoDroid, upgraded Magisk to beta, and see if MicroG will work this time. :)
[Magisk] iacchi:
Isn't Magisk 16.7 a beta version?
[Magisk] guest4711:
Yes, it is. But sometimes a new beta solves some older problems without introduction of (too many) new ones. You can wait til the next release (some days? weeks?) or give the beta a try...
[Magisk] Apex Predator:
Has anyone else had issues getting OmniClock to install? I've tried many times, making sure that box is ticked every time but it never installs. I checked inside the full package and the apk is there but the installer shows no mention of it despite ticking the box. Is there perhaps something missing in a script? Not exactly sure how the magic happens. ?

Running crDroid v4.5 Oreo with Magisk v16.7 and current Nanodroid on a Note 4.
[Magisk] Apex Predator:
So I now have new problem... Trying to do a clean install of my entire system to fix a problem I've been having. When I flash Nanodroid, it no longer detects Magisk and installs to the system. No idea why, I've changed nothing and have done many flashes in recent weeks. Here are my usual steps:

1. Full wipe - system, data, dalvik/art and cache

2. Flash ROM crDroid 4.5 Oreo 8.1.0

3. Flash addonsu remove zip

4. Flash Magisk 16.7 (1671), the hotfix one

4. Flash Nanodroid 17.2 set up wizard step through the aroma installer

5. Flash Nanodroid 17.2

6. Wipe cache & dalvik

7. Reboot system

Until today, that process worked fine and Nanodroid always detected Magisk, although both were earlier versions. Today is the first time I've tried this specific version combo on a clean install.

As an experiment I ran uninstallers for both then flashed previous Magisk 16.6 followed by Nanodroid full package but without the set up wizard (I was impatient) ... and it detected Magisk. So after uninstalling both and starting over I did the usual steps only this time using the set up wizard... And it failed to detect Magisk. Grrrrr.

I've tried all steps again several times with latest versions of everything and Nanodroid just won't detect Magisk and insists on a system install.

So what now? Would stopping after Magisk install and booting into system once then rebooting recovery and then trying the Nanodroid install be a good idea? I remember reading somewhere, possibly this very thread, that booting before microG is installed is ill advised as it can cause issues. That may have only been in relation to installed apps that need the framework though, which would not be as much of a concern on a clean install.

Any ideas?
[Magisk] clewis.it:
Reboot after installing magisk. Then go back to recovery and flash nanodroid.
[Magisk] Apex Predator:
Yep, my gut feeling was correct, as was your response. Reboot after Magisk did the trick.
[Magisk] Setialpha:
Uploaded modified Play Store 10.8.32, use 'nupd ps' as root, to update.
[Magisk] Luigi7744:
Hello, i was having problems with apps registering to GCM. Specifically the Mega cloud server app. I get no notifications.

I reverted back to nanodroid 16.1 and the app registration is working fine now... all apps are registering to the GCM service.
[Magisk] Apex Predator:
When I try to update PS I get this:

Updating: Phonesky

wget: bad address 'www.nanolx.org'

!! failed to download Phonesky

Termux has internet access.