yashsingh1/xdaforums huggingface dataset:
[Magisk] Loader009:
Sadly I have now an untypical problem.

People at the telegram Group for microG (NO GAPPS) couldn't help me...

The PlayStore doesn't show any installed apps and is searching for updates constantly. I know that I can solve it with a full wipe, I did that once.

I already tried to remove any overlay, but that didn't help.

I use the NanoDroid-microG submodule.

Permissions and PrivacyGuard settings should be alright.

First I had installed it in system-mode but because of more tests I decided to switch to magisk-mode.

Afair it was after that, that some apps began to say they were not paid, so I checked PlayStore and noticed that problem (again).

If you have any idea to test before I wipe, please tell me.

griffin:/ # novl -l
Overlays exist for following applications in /system/app:

* BasicDreams
* Email
* messaging
* PhotoTable
* Stk
* WallpaperBackup

Overlays exist for following applications in /system/priv-app:

* com.qualcomm.location
* Eleven
* Gallery2
* Recorder
* Snap

griffin:/ # novl -c
removing Overlays from /sbin/.core/img/NanoDroid_microG
removing override: BasicDreams
removing override: Email
removing override: messaging
removing override: PhotoTable
removing override: Stk
removing override: WallpaperBackup
removing override: com.qualcomm.location
removing override: Eleven
removing override: Gallery2
removing override: Recorder
removing override: Snap
griffin:/ # novl -l
Overlays exist for following applications in /system/app:

*

Overlays exist for following applications in /system/priv-app:

*
[Magisk] Setialpha:
Did you disable any service of Play Store? Did you ensure it has sigspoof enabled (check from microG selfcheck if it reports correct signature)? Else only a logcat may help.
[Magisk] Loader009:
I disabled the Daily Hygiene service.

Thanks to you I remembered something like "it has to run at least once before disabling it" and reenabled the service.

The issue is gone now, all installed apps are visible and it finds updates, thank you :)

PS: If you still want a logcat, look at the attached zip in my previous post.
[Magisk] rnadomuc:
Pro-tip on getting playstore to work: Make sure you go to the 'Advanced' section of Google SafetyNet in MicroG settings and make sure the official server option is selected (nothing is selected by default, for some reason)

Also after you set up your google account, you might still get RH-01, close out the app and try again, sometimes it doesn't work the first time even if everything is set up correctly for some reason.
[Magisk] Punkiderma:
For me play store works well without having to enable safetynet
[Magisk] rnadomuc:
Did you install F-Droid? I think it might have something to do with the Droid Helper or whatever. I could never get it to work without enabling it.

It's not really SafetyNet though, just an emulator that only works as far as communicating with remote servers. Still won't let you pass SafetyNet checks.
[Magisk] Punkiderma:
Yes, I have nanodroid microG and nanodroid fdroid modules installed
[Magisk] andrepgaspar:
no mather what i choose in setupwizard just deja vu is installed, cant install mozilla

if you need logs, just say where they are and i will upload them
[Magisk] iacchi:
Have you tried to install Mozilla backend through f-ddroid? It doesn't necessarily need to be installed with nanodroid.
[Magisk] Setialpha:
Are you sure you dob't have any old setup files in the way? NanoDroid looks in various places and uses the first ones found.

Remove any hidden .nanodroid-* files from /data, /sdcard (internal storage from inside Android), /external_sd (external storage from inside Android) and/or the directory the zips are saved in. The rerun the SetupWizard and try again.
[Magisk] andrepgaspar:
Fully wiped first so no
[Magisk] RobotPhone:
Last time I ran the setupwizard after a full phone wipe (going to oreo) I selected both backends too but only deja installed. Not a big deal because I installed mozilla through fdroid, but I can confirm something might need to be tweaked with the nanodroid install scripts.
[Magisk] jenslody:
Also external memory (sd-card) ?
[Magisk] andrepgaspar:
Yes!! In the final screen of the setup wizard where we can see how the config looks like, it just doesn't appear the mozilla one, just deja vu
[Magisk] Setialpha:
Ok, I guess I've found the issue, you can't see it, if you look in the wrong place.

All code that is doing anything regarding nlp in both SetupWizard and CommonInstaller is fine... but in the beginning of the setup script the definition of the variable nlp_prop was non existent... OMG.

It did thus not create the nanodroid_nlpbackend variable at all, leading the CommonInstaller to install DéjaVu.

New beta tomorrow (with more changes, than just that).
[Magisk] :
Is it possible to move between stable and beta nanodroid?
[Magisk] andrepgaspar:
good and quick job mate!!
[Magisk] D4ND310:
Great, thanks! I wiped and fresh-started my phone last night and have been fighting with Google Play all day due to my entire uninstalled purchase history requiring payment again.

Any items that were previously bought, if not installed at the time, were requesting I bought them again. I eventually gave up and restored my TWRP backup from just before I wiped after multiple retries at NanoDroid and various Magisk configurations and un/installations.

Previous to my wiping I'd also backed up my more important user apk/data files. One of these was My Android Tools Pro, which I had restored. Its data files, indeed, was set to disable DailyHygeineService, so as soon as Play Store ran, it was in effect.

I did not know that I had to let Play Store run the service at least once before manually disabling it. Thank you! :)
[Magisk] utg1:
I'm trying new beta (16.3b2) and, at least for now, Playstore and microG settings work well: no error RH01 and settings don't dissappear.

Just one thing: when I flash ND_patcher beta2, it detects Android 7.0 - 8.1 SDK but I have Marshmallows, so install fails. I used a previous version.

Cheers
[Magisk] :
OK, now that there was a new update for my rom, I tried it again. It's definitely not working. The patcher says that odexed ROMs are not supported. Self check says that spoofing isn't active. I don't want to deodex it manually and I definitely don't want to use exposed so for now I can't use nanodroid/microg. Don't know how much work it is or if it is even possible but future request fur nanodroid is to deodex ROMs ;)
[Magisk] utg1:
[MENTION=4187311]Setialpha[/MENTION]: it's better that I do not speak :/

Same issue with beta2: when I get Playstore error RH01, my microG settings dissappear, all off. :(
[Magisk] Setialpha:
I'll have a look at the logcat you provided, didn't have the time yet.

---8x---

16.3 will get two more additions: Fonts and KeePass DX instead of KeePassDroid.

The fonts are the one you'll find in several Nintendo Games like Splatoon 2 or Super Mario Maker, there's a new setup variable (nanodroid_fonts) and a new script (nanodroid-font), for this feature. Currently the installer can't restore upon upgrade of NanoDroid, in case anyone uses the git version to build packages themselves; also it's currently Magisk-only. Both will change/be fixed before the final release of 16.3, so there might be a third beta.

If you've choosen to install KeePassDroid, the CommonInstaller will auto-migrate to KeePass DX, so nothing to do on user's end in this regard. KeePass DX has a nicer UI, full Fingerprint support and Oreo Autofill service, thus the transistion.
[Magisk] :
Thanks for the change, much appreciated. Can you change QKSMS for Silence or something though, it hasn't been updated in a year. Also I know you switched VLC for MPV, but VLC is still a lot better, even with a little extra size.

And one last thing (I know it's annoying if people request stuff), OpenLauncher is pretty outdated as well, LawnChair is a much better alternative.
[Magisk] inVain_theGenuine:
I'm also plead for Silence + VLC! :highfive:

thanks for the fix regarding the nlp backends :)
[Magisk] inVain_theGenuine:
[MENTION=4187311]Setialpha[/MENTION]

I have a tad bit question,

whenever I installed NanoDroid on Slimroms 7 I always have Playstore registered on Google Cloud Messaging.

but on Omniroms (Oreo 8.1), I can't have Playstore registered on GCM.

is this an expected behaviour, I mean for the Playstore to be unregistered on android 8.1?

and uh...

I'd like to report that on the version 16.2 (stable), I have zero issue for syncing to my google account on both Slims7 & Omni 8.1.

It went straight syncing without me need to put any additional effort.

sweet!! :thup
[Magisk] Shadow53:
If you are talking specifically about the F-Droid edition of Lawnchair, it gets fussy if LawnFeed isn't installed, even if you aren't using the Google Now integration. They're currently putting together support for F-Droid, here's the open pull request: https://github.com/LawnchairLauncher/Lawnchair/pull/1157 In the meantime, apparently beta builds of Lawnchair don't depend on Lawnfeed.

I've also had issues with it randomly reporting it has stopped when I hit the home button, followed by it working just fine. I believe this was with Lawnfeed installed, though I could be wrong.

My own zips currently use Hayai launcher, due to the above Lawnchair issues and an issue with OpenLauncher that causes it to crash if I open the app drawer. The fix has been committed but apparently not yet put into a release.

Regarding QKSMS, the adventurous can install beta versions of the rewrite from the GitHub releases section.
[Magisk] :
I guess you're right, I too have experienced some force closes in Lawnchair. And I'll test the Hayai launcher and the QKSMS beta.
[Magisk] Setialpha:
OpenLauncher 0.5.9 includes the fixes for AppDrawer crashes AFAIK and it's included in NanoDroid. 0.5.10 is released on GitHub, will be included in next NanoDroid version. I don't see a reason to switch, OpenLauncher is very flexible and all.

Also QKSMS 3.0-beta6 is included in the latest NanoDroid beta, it's working stable enough already, tested several devices. For SMS that is, I don't use MMS.
[Magisk] Setialpha:
I don't have Play Store registered either, it's not required it seems, 'cause notifications and stuff properly works.
[Magisk] FriendlyNeighborhoodShane:
[MENTION=4187311]Setialpha[/MENTION]

Actually, bash isn't the only thing that doesn't work on older kernels, Column doesn't work either. So novl -s (show_overrides) doesn't work.

I just tried to removed the pipeline from that function, and it ... This is beyond me.... The alignment is weird. I've attached the output. For both app and priv-app, there is first a proper output then a second one, where the badgings are correct, but the folder names are all replaced by WeatherProvider

show () {

echo " >> processing /system/app"

for app in /system/app/*/*.apk; do

sysname=$(basename "${app}" .apk)

if [[ ! -f ${OVERLAY_PATH}/system/app/${sysname}/.replace ]]; then

humname=$(show_app_name "${app}")

S_APPS="${S_APPS}

* ${sysname}	|(${humname})"

fi

done

echo " >> processing /system/priv-app"

for app in /system/priv-app/*/*.apk; do

sysname=$(basename "${app}" .apk)

if [[ ! -f ${OVERLAY_PATH}/system/priv-app/${sysname}/.replace ]]; then

humname=$(show_app_name "${app}")

S_PRIV_APPS="${S_PRIV_APPS}

* ${sysname}	|(${humname})"

fi

done

echo "Non-Overlayed applications in /system/app:

$(printf '* %s\n' "${S_APPS[@]}" )

Non-Overlayed applications in /system/priv-app:

$(printf '* %s\n' "${S_PRIV_APPS[@]}" )

"

}

I've seen somewhere that paste might be an alternative, and it's in busybox.

AAPT work perfectly, atleast as far back as my device. So that pretty much settles it for binaries.

Good luck.

EDIT: Wow.... now I've properly formatted the function and the first output just shows filder names, and the second both folder names and badging.
[Magisk] Shadow53:
Hmm, the F-Droid build is still on 0.5.8... Didn't realize they'd made new releases. Thought I'd set up notifications for that.
[Magisk] utg1:
No problem mate! :good:

Just to report: ATM I'm using NanoDroid-microG-16.1.20180209 and seems that this version does not have those issues like the new versions 16.2 and 16.3beta....
[Magisk] Setialpha:
What ROM are you using? It complains about something I can't fix. Likely the older Play Store in 16.1 doesn't utilize that feature.

Also did you block any service of Play Store? What happens, when you update it (https://www.nanolx.org/apk/Phonesky.apk)?

What happens a full clean flash? Because it also complains about a UID change of microG, I don't know what causes it, but that erases the microG settings.

I can't reproduce theese errors myself, though.
[Magisk] demonoidmaster:
Lean Launcher is better than Lawnchair
[Magisk] Setialpha:
They just pushed 0.5.10 to F-Droid (finally).
[Magisk] utg1:
BIG EDIT:

Same issue with 16.1 :(...

EDIT 2: I'm trying Playstore version 9.2.11 with Daily Hygiene disabled and microG 16.3beta2... After few hours no issues... Fingers crossed ×××

I have a RedMi 4 Prime with Miui 9 based on Android 6.0.1 (+ Magisk 16.0 before and now 16.1)

I only have two disabled services (but by default, I didn't touch anything):

com.android.vending/com.squareup.leakcanary.DisplayLeakService

and

com.android.vending/com.squareup.leakcanary.internal.HeapAnalyzerService

Also I tried without luck to disable/enable "DailyHygiene".

I already tried to update Playstore when I used MicroG 16.2 and 16.3 beta (1 and 2), same issues.

I have to test playstore update with uG version 16.1!

Give me a few hours to test it.

I tried to, in order:

1) wipe cache and davilk cache

2) re-flash the rom with a wipe /data and restore apps with Titanium backup (without MicroG)

3) restore smartphone ID via Titanium Backup

No luck.

I just have to try to update Playstore and test it with uG 16.2 and/or 16.3..

Anyway thank you very much for your incredible work and for the time that you dedicate (and have dedicated ^^) to me.
[Magisk] :
[MENTION=4187311]Setialpha[/MENTION] How did you download VLC, before switching to MPV? I always get a wrong SHA256 cache, while downloading either from F-Droid or ApkMirror.
[Magisk] piet8stevens:
See attached - it was very long and I selected some lines that I thought were important (E). Seems droidguard issue.

I copied droidguard from system and installed it, but not see any app call droidguard.
[Magisk] slothdabski:
I'm still able to pass safetynet with droidguard installed as user app
[Magisk] piet8stevens:
Thank you. I installed droidguard as a user app (I copied from /system to /sdcard/Download and installed from there), but I do not know how to check that it was correctly installed. Do you have a DroidGuard app in your app list?
[Magisk] piet8stevens:
[MENTION=4187311]Setialpha[/MENTION] Here is a better logcat with *:E.
[Magisk] slothdabski:
No I dont
[Magisk] Setialpha:
It's called microG DroidGuard Helper in Settings > Apps.

I'll have a look at all theese logcats, soon™.
[Magisk] slothdabski:
Thanks I was looking for D, didn't realise the pckg started with M
[Magisk] SirSoviet:
It looks like dexpatcher only works after the first boot.
[Magisk] JERW28:
[MENTION=1835735]piet8stevens[/MENTION] [MENTION=4187311]Setialpha[/MENTION] for microG droidgaurd helper to work, Google SafetyNet needs to be enabled in microG settings. By default it is disabled and Magisk Manager thinks you have no internet because it cannot detect safetynet.

To enable it:

1. Click on microG Settings

2. Click on Google SafetyNet

3. Toggle on

4. Click on 3 dot menu in upper right-hand corner >advanced

5. Click use official server (first option)

6. Go back to microG main screen. Under Google SafetyNet it should now say "Enabled"

7. Go to Magisk Manager and enable MagiskHide in settings (no need to hide microG ect..)

8. Reboot

9. Check if you pass SafetyNet in Magisk Manager.

If you loose root after doing this, simply disable magiskhide and reboot, to gain root again.

This is a known problem with Magisk and we have to wait for topjohnwu to figure it out and hopefully fix it.
[Magisk] piet8stevens:
Thank you so much. I had SafetyNet enabled, but not the advanced check of the official server. Once I did that, it worked.

Your help is much appreciated.
[Magisk] Setialpha:
Actually the README states to "set to use official servers" in regard of SafetyNet ;)

Either way. I've changed the way the framework-patcher detects the required architecture for LD_LIBRARY_PATH. Please test.
[Magisk] piet8stevens:
Sorry - reading precisely is difficult.

What exactly do you want me to test? Just run it and see what happens?
[Magisk] gh0st85:
Still not working but I think the problem is an odexed rom.
[Magisk] Setialpha:
It won't ever work on odexed ROMs, but I may add a check for that...
[Magisk] Setialpha:
Yep.
[Magisk] gh0st85:
Yeah, that's what I thought but since it isn't mentioned anywhere...

Edit: off topic, can you recommend a simple way to deodex a rom?
[Magisk] Setialpha:
Version 7.2 now available. Highlights since 7.1: many improvements in framework-patcher.

Full ChangeLog

* Internal Changes
* full package: replace `spaces` with `underscores` in Zelda ringtone names
* full package: minor fix in installer
* framework-patcher package: grow and shrink `magisk.img` if required
* fixes issue where patched `services.jar` could not be installed, because not enough space was left in `magisk.img`
* framework-patcher package: show error message to user if `/system` fails to re-mount read-write
* framework-patcher package: unmount `/system` and `/data` after work is done
* framework-patcher package: less verbose output from `dexpatcher` and `zip`
* framework-patcher package: note the user to post `/tmp/recovery.log` if something fails
* framework-patcher package: use static `zip` binary, fixes possbile `zip` failure older ROMs
* framework-patcher package: change the way `LD_LIBRARY_PATH` is determined
* framework-patcher package: check if ROM is `odexed` and exit if so
* framework-patcher package: code clean-up
* framework-patcher script: grow and shrink `magisk.img` if required
* fixes issue where patched `services.jar` could not be installed, because not enough space was left in `magisk.img`
* framework-patcher script: fix installation path for patched `services.jar` when NanoMod is not installed
* Updates:
* GNU Bash (4.4[012])
* Substratum (721)
* OpenKeyChain (4.4.1)
* OpenLauncher (0.3.2.1)
* Twidere (3.5.36)
* F-Droid (0.103)
* Play Store (7.7.40.N)
* Kernel Adiutor (0.9.7.1beta)

Have Fun.

In case of errors: provide logcat or /tmp/recovery.log
[Magisk] piet8stevens:
OK, I installed a new version of the BlissRom, re-installed Magisk, rebooted, installed NanoMod and used your latest patcher. Apart from changed comments in the output window, it succeeds just like the previous version. Only thing that was a bit confusing was that your last two versions have the same name - both are called NanoMod-patcher-7.2.20171231.zip. I must admit I ran both - one from sdcard and one from a usb stick over USG.
[Magisk] Setialpha:
XXXX1231 is the test version (as New Years Eve is still more than 7 months ahead), sorry for the confusion. And thanks for testing.
[Magisk] justbfree:
Hi, i'm having this issue, could you please let me know how did you fix it? thanks.

Edit: Nevermind I found it.
[Magisk] pandavova:
Btw, i get the RH-01 message in the Play Store too, even with NanoDroid-microG-16.1.20180209.

Im using a S5Neo 6.0.1.

I hope for a fix, because its curently not useable.
[Magisk] abacate123:
Try these methods below:

Source (you can find other answers there as well): https://www.quora.com/How-do-I-fix-Google-play-store-error-rh-01/
[Magisk] Ramakrishnan ?:
Thnx for the wonderfull work !
[Magisk] Setialpha:
modified Play Store 9.3.14 uploaded. Use

novl -U

on 16.2 to update, or

nupd ps

on 16.3 beta to update.
[Magisk] Setialpha:
I didn't automatically, back then I did it manually. I guess it does not work because VLC has different apks for different architectures, that's not supported by build-package.
[Magisk] :
Apparently it's the same with Firefox. Thanks for the answer though :)
[Magisk] jenslody:
I had the same problem on my Samsung J5 running self-build validus oreo, based on lineage 15.1.

I manually granted the FAKE_PACKAGE_SIGNATURE permission to the two apps needing it.

In adb-shell:

pm grant lanchon.sigspoof.checker android.permission.FAKE_PACKAGE_SIGNATURE
pm grant com.google.android.gms android.permission.FAKE_PACKAGE_SIGNATURE

The first is only for testing purposes, the second is for the fake-gms of microg.

You might need to run this as root, even if it works this way on my device. Probably depends on your adb-rights.

This makes the self-test pass, but unfortunately some apps (like Threema) do not register with microG anyway, but that's another story (as discussed already).
[Magisk] psychem:
Thanks for this alternative. Unable to use olacabs with this. It is a must app for me. Please fix the issue with olacabs app.
[Magisk] piet8stevens:
It is kind of difficult to fix anything when

a) no description whatsoever of what does not work

b) no logs.

The OP clearly states what you need to do for [MENTION=4187311]Setialpha[/MENTION] to have a chance to 1) reproduce and 2) fix your issue.
[Magisk] psychem:
sorry about that.

a) the app is for booking taxis like uber. problem is the google maps do not show in the app.

b) i will try to get the log and post soon but it happens in all phones i have tried with microg so you can install this app in your phone and see if maps work or not.

thanks.
[Magisk] psychem:
Log for olacabs attached
[Magisk] jenslody:
Did you try it with "normal" microG ?

If that does work, it is a NanoDroid issue, otherwise it is a microG problem and should be reported on their site.
[Magisk] psychem:
i dont know what "normal" microG is. Please provide a download link.

what is the link to report this issue ?
[Magisk] Mynacol:
So, [MENTION=4187311]Setialpha[/MENTION] has done this flashable package (either Magisk or directly to system) to automatically install MicroG and other stuff in a great form (e.g. with the setupwizard it is selectable what to install).

MicroG is only part of this Package and doesn't get developed in this project. The XDA thread for MicroG is: https://xdaforums.com/android/apps-games/app-microg-gmscore-floss-play-services-t3217616/page447

And their website (including a link to the GmsCore, the main part of MicroG, github page): https://microg.org/

Directly regarding your problem:

How did you install NanoDroid? What have you selected? I am specifically pointing to to the so-called "MapsAPIv1", which could be used (or wanted to be used) by your problematic app. There were already some Google Maps issues, which were solved with the named software.

Some Background: The Maps API v2 is baked into MicroG, the Maps API v1 is realized with the named software and I believe there is already a Maps API v3, but idk.

Write if you need further assistance. Regards, Mynacol:highfive:
[Magisk] psychem:
Thanks for those links.

The way i installed Nanodroid was through 2 packages flashed via TWRP - NanoDroid-fdroid-16.2.20180302.zip and NanoDroid-microG-16.2.20180302.zip and also flashed Xposed along with the Fakegapps module.

Playstore and others gapps work fine and update fine as well.

Should i flash Patcher or Setup Wizard?
[Magisk] kurtn:
You still have GApps? MicroG is meant to replace GApps. Do you want to go noGApps?
[Magisk] psychem:
no i dont have flashable opengapps i just downloaded the google apps from playstore after flashing nanodroid.
[Magisk] :
You don't need the patcher if everything works. The setup wizard won't help you either, since it only makes the files required for customisation (you need these before flashing NanoDroid).
[Magisk] kurtn:
That's not worth the trouble. Flash GApps or get noGApps.