yashsingh1/xdaforums huggingface dataset:
[Magisk] inVain_theGenuine:
ahh....

restoring the apps could be the culprit.

I remember the days when my WhatApps always failed me before I did the proper google account setup.

back then, I was even still with the open Gapps.

those had led me to this thread, to be frank.

I then read Setialpha's post about the importance of how to install the GCM based apps after we did the proper setup of our google account.

now I always install my WhatsApp after I did proper setup of microG /NanoDroid on this thread.

after everything got checkmarked on the microG self-check, I do register my google account and reboot afterward.

install the instant push notification tester via the playstore, and see if I can get the push notification correctly.

then it's time to populate my phone with apps :LOL

only with microG I was able to see what apps were registered with GCM, to my surprise... it were lots of them... more than what I expected, probably they were connected to GCM to receive their ads?

in your case, maybe it was worth to try to save your WhatsApp chat locally, uninstall your current WhatsApp....

then re-installed it again, log in to your WhatsApp account and see if it was registered on the microG's GCM.

it should be better than do the full wipe of your phone and start all over again.

best of luck :)
[Magisk] kurtn:
[MENTION=8862070]Rorschach1010[/MENTION]

You have an Oreo ROM. I don't think WhatsApp will work correctly with microG. I had my best results by installing WhatsApp without microG and disabling battery optimisation for WhatsApp.
[Magisk] :
Thank you both for all the tips. I'll try installing some apps from scratch but Oreo might be an issue too, that's true.
[Magisk] jenslody:
I did not receive messages for slack and threema on oreo with microG.

After downloading and installing old apks (2016 and early 2017) and allowing the automatically registering of push notofications, I updated both apps and push notifications seem to work.
[Magisk] SilentEYE:
I don't think that Threema will work. I tried nearly every method and there is no solid workaround.

It looks like the app is registered, but it's not working correctly.

Maybe you can post your findings later?
[Magisk] Mynacol:
Strange. I have Threema successfully installed and GCM seems to work fine and additionally is quite responsive (I mean if new messages are available, I get sooner than later a notification for them)

Unfortunately, I can't say what I have done to get it to work, it somehow worked without messing around with it...

Hope you get GCM to work!
[Magisk] tom.android:
I used 3 custom setup files (.nanomod-apps,.nanomod-overlay,.nanomod-setup)

with NanoDroid-16.4.20180328.zip but can't install the apps.

How can I fix it?

nanomod_microg=1

nanomod_fdroid=1

nanomod_apps=0

nanomod_play=1

nanomod_overlay=1

nanomod_zelda=0

nanomod_mapsv1=1

nanomod_init=1

nanomod_gsync=0

nanomod_swipe=0

nanomod_forcesystem=0

nanomod_sigspoofui=0

nanomod_nlpbackend=2
[Magisk] SilentEYE:
Which device are you using?

Can you check the gcm settings page, where Threema is listed. I got the problem that there wasn't any update.

EBay didn't work as well.

I tried several methods with user fructify from microG telegram group. Unfortunately we weren't successful.
[Magisk] sahil_anas:
Newbie here

Can any one helpme out with the confusion. Is this an alternative to Google play service, i mean if i install microg then i don't need to install gapps.
[Magisk] Mynacol:
I have a Samsung Galaxy S4 (i9505) running LOS 14.1, Magisk 16, and NanoDroid 15.1.

Since months I haven't touched my configuration and MicroG. Threema was installed in an early version (2.x) and only upgraded since then.

Do you know already that there is an option inside the Threema settings -> "error correction" (translated from German) -> reset push-token

This resets the Threema GCM registration and maybe helps you.

If you haven't tried already, install the latest 1.x Threema version, test push notifications and if successful, upgrade Threema to the latest and greatest version.

I assume all (maybe except the ones regarding UnifiedNLP) checkmarks in the MicroG self-test are checked and push notifications work with other apps (e.g. a push notification tester)
[Magisk] SilentEYE:
[MENTION=7718878]Mynacol[/MENTION]

The push token reset function is broken on oreo custom ROMs.

I got an error message. Tried at least 6 ROMs. Device is Xiaomi redmi note 4.

It is said that there is a problem with new push method changes on Oreo.

The Threema support replied me, that the new oreo push (firebase cloud messaging) is the same as GCM.

Where did you get a legal Threema v1 from?
[Magisk] guest4711:
Yes, MicroG is an alternate for some functions provided by the google framework. It is for those people caring about privacy. But for those loving to have bloatware like google now, alexa or cortana it is not meant...
[Magisk] tdsystems:
Dos it work with LeEco Le Pro 3 Elite (X722 or ZL0)?
[Magisk] guest4711:
It should work with all devices. Signature spoofing depends on the ROM (either it is supported while the ROM's developer included the necessary patches or you can patch it yourself. But be warned that patching odexed ROMs is a little bit tricky). And it will only work if no g-apps are installed.
[Magisk] Mynacol:
Then I'm afraid I cannot help you. I were never on an Oreo android version and have no experience there.

And as I have no need for it, I cannot help you with a v1 version either. My only idea is using Yalp Store and going to "manual download"
[Magisk] kurtn:
I'm just reading into this. Threema has a poll function to use when gcm is not available. Could be similar to WhatsApp that works best in Oreo without microg and not battery optimised.
[Magisk] SilentEYE:
Now the problem is "solved". I was talking to an user who had problems with oreo and gcm.

Afterwards you quoted me and trying to show a workaround.

Maybe you have missed that the problem was on oreo builds.
[Magisk] inVain_theGenuine:
so, how did you solved the problem?
[Magisk] SilentEYE:
Sorry it was a typo.

I meant the problem of wrong communication.

The bug is still there. But there is a tiny update for microG. If I find the time I will check the new version with an oreo build.
[Magisk] jenslody:
It does not fix the push issue with some apps.
[Magisk] Setialpha:
But it fixes the issue that in some cases, if the user can't login to Google, no message is shown, also it bumps the spoofed GService Version, fixing apps to refuse to work due to outdated Play Services.
[Magisk] Setialpha:
that needs to be '1' if you wanna install apps.
[Magisk] Setialpha:
1) I may add an option to only install Fake Store.

2) Yes, you're right, the GApps removal feature does not work 100% in system mode, thus you end up without GsfProxy. Will be fixed in next release.
[Magisk] Setialpha:
You simply flash a new release, without removing the previous. But many apps switch from GCM to FireBase and microG does not (yet?) support that.
[Magisk] Setialpha:
This explains the contents of each package: https://gitlab.com/Nanolx/NanoDroid#packages
[Magisk] Setialpha:
I may have a look.
[Magisk] Setialpha:
This is completely unrelated to Signature Spoofing, which is required for microG to disguise itself as GService.

My modified Play Store requires it aswell, because I altered the Play Store so (new) purchases work with microG, which otherwise isn't the case.

About certification, see the attached screenshot (NanoDroid 16.4 + Magisk 16.3 out-of-the-box, experience may vary, though).
[Magisk] abacate123:
Just pass the ctsProfile and it'll show certified there. As simples as that.
[Magisk] Setialpha:
Yup.
[Magisk] reohufsdn2@gmail.com:
Hi,

Sorry if this is a noob question, but I have a problem flashing the patcher .zip. Each time the process gets to services.jar it fails. Help would be appreciated.

Device: Oneplus One

Nanodroid ver.: NanoDroid-patcher-16.4.20180328.zip

OS version: lineage-14.1-20180328-nightly-bacon-signed.zip

Recovery: TWRP 3.2.1-0

And if it matters I've tried flashing the patcher both before and after flashing magisk 16.3. I've also only tried to clean flash.
[Magisk] d1n0x:
Why don't you just download LineageOS bundled with MicroG?

https://download.lineage.microg.org/bacon/

No need to patch and everything built-in ready to go.
[Magisk] guest4711:
Probably your ROM is odexed. If unsure check on the system/framework folder of your LineageOS.

If you can find "oat" folder, then you have an odex-ed ROM.

In this case you need to de-odex the ROM (or IMO, at least the services.jar) to make the NanoDroid patcher gets its job done.
Search in this thread for "odex" to find more help.

If this problem does not belong to you, post your errormessage please...
[Magisk] reohufsdn2@gmail.com:
Because I really want a working play store.

I don't know which file under system/framework I was supposed to be looking for. Is it okay for you to check for me? I took screenshots of all the files under that directory.

---------- Post added at 04:12 AM ---------- Previous post was at 04:08 AM ----------

Whoopsie[IMG="1"]https://i.imgur.com/tkcwQi9.png[/IMG][IMG="2"]https://i.imgur.com/pduncSy.png[/IMG][IMG="3"]https://i.imgur.com/NLjlFdG.png[/IMG][IMG="4"]https://i.imgur.com/2oBAeV5.png[/IMG]
[Magisk] Shadow53:
You can use the Lineage for microG and flash a Play Store zip from my site at https://shadow53.com/android/downloads/microg/. There is a version that uses the official Play Store and one that uses the patched NanoDroid version. If you are only using NanoDroid for microG with a Play Store, you might try that.

P.S. it would be a good idea to use a Play Store only zip and not one bundled with microG so you can receive updates to microG when you update the ROM.
[Magisk] jenslody:
[MENTION=899471]SilentEYE[/MENTION]for some (unknown) reasosn it works now.

I did not try to reset the push-token with the actual Threema, because everything is fine at the moment and it never worked in oreo, but I did it with my temporarily installed 2.84 and it works immediately.

At the moment I get messages in the same seconds they were send and Threema was last opened more then twelve hours ago.
[Magisk] Setialpha:
16.5

Version 16.5 is now available. Highlights since 16.4:

improved GApps removal mechanism

fix microG GsfProxy installation in System Mode

option to only install Fake Store

usual updates

Full ChangeLog since 16.4

### Bug Fixes

* CommonInstaller
* fix microG GsfProxy not installed in System Mode

### General Changes

* CommonInstaller
* Full, microG packages
* improve GApps removal mechanism
* improve some installer messages
* new value 3 for nanodroid_play variable will install Fake Store only
* Full, microG packages
* move microG GsfProxy from /system/priv-app to /system/app
* Full package
* download Orbot and Orfox from Guardian Project F-Droid repo instead from the release mirror
* SetupWizard
* update for nanodroid_play value 3

### Updates

* Automatic
* GNU Nano 2.9.5
* F-Droid (1.2-alpha0)
* (Simple) Calendar (3.4.1)
* (Simple) Gallery (3.6.3)
* KeePass DX (2.5.0.0-beta7)
* QKSMS (3.0-beta8)
* microG GmsCore (0.2.4-111)

* Manual
* Play Store (9.4.18)
* MPV (20180402+merges)

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] iacchi:
[MENTION=4187311]Setialpha[/MENTION]: In the download links I only see the f-droid version - what about the other two versions (the full one, for what concerns me)?
[Magisk] Setialpha:
I was just made aware of a bug when upgrading from Magisk Manager (upgrading from TWRP was not affected) - so I re-uploaded microG and Full packages with the following, additional change:

### Bug Fixes

* CommonInstaller
* fix restoration tasks during NanoDroid update when upgrading from Magisk Manager
* restore NanoDroid-Font settings
* restore NanoDroid-Prop settings
* restore patched `services.jar` (if applicable)

Original 16.5 announcment post

--- Edit: [MENTION=4719100]iacchi[/MENTION] you've been ninja'd
[Magisk] :
Since 16.4 was my first version, I'm not sure how to update. Do we just install the full package via magisk or is it necessary to first use the wizard again so it won't install apps I haven't installed the first time?

Also, is it possible to install or uninstall things like Zelda sounds or Nintendo fonts afterwards?
[Magisk] Setialpha:
You simply flash a new version (either from TWRP or Magisk Manager), the configuration files persist until you format the storage, remove them or run the Uninstaller.

If you want to remove a feature, re-run the SetupWizard or modify the configuration file accordingly and then update.
[Magisk] :
Gotcha, thanks.

BTW, a heads-up about gcm. You can install greenify to see which of your apps are using gcm. This makes it easier to know which apps to reinstall without titanium backup.
[Magisk] inVain_theGenuine:
"oat" is a name of a folder inside the "framework" folder.

another way to distinguish if you have an odexed rom is by checking the system/app or system/priv-app folder.

if you can find "oat" folder inside your installed apps, chances are you've an odexed rom.

now, assuming you've an de-odexed rom......

did you patch it straight after your flash your rom?

if you did, you need to reboot to your system once; to let it build the ".dex" file inside the dalvik-cache folder.

then, you need to reboot to the twrp and apply the patch.

don't wipe anything yet, since the NanoDroid Patcher will be patching the ".dex" file inside the dalvik-chache.

something worth to mention here is; if you intend to flash the NanoDroid as a magisk module, you need to patch the framework after you install magisk.

else, flash magisk after after you apply the patch and install NanoDroid.
[Magisk] kurtn:
I think this goes into a totally wrong direction. LOS 14.1 is normally not odexed. Nanodroid patcher builds its own dex files, so no boot into system necessary. Nanomod normally tells you in twrp terminal wat went wrong. In doubt you can go advanced and copy logfile to internal storage. From there you can post it (after boot into system).

And [MENTION=9060100]reohufsdn2@gmail.com[/MENTION] microG with play store is not an optimal solution. Try microG with yalp or GApps with afwall or xprivacyLua.
[Magisk] :
[MENTION=8546761]inVain_theGenuine[/MENTION] What's the purpuse of the patcher and is my understanding correct?

1. If you have a rom that supports signature spoofing then just flash the full package

2. If it doesn't you can use the patcher to patch a de-odexed rom

3. If you have an odexed rom without signature spoofing you have to de-odex it first
[Magisk] kurtn:
Correct.

To 3: you can also use xposed fakegapps.
[Magisk] inVain_theGenuine:
my bad.

I thought he's on LOS 15.1

that's what I did prior to 16.2 up to I now (after reading your post)

and yes, on the 16.5 apparently the patcher can patch the rom without the existence of dalvik-cache, so I think we can patch the rom straigh after flashing the rom :-bd

1. in brief; yes!

microG & the patched Playstore /fakestore are the ones which need the signature spoofing,

so if you have a rom which supports signature spoofing, you can just go ahead and install Nanodroid MicroG or the whole package.

2. yes

3. yes
[Magisk] deedeeceleb:
Where did you find 2.84?

Gesendet von meinem ONE A2003 mit Tapatalk
[Magisk] jenslody:
Direct download in Yalpstore, buildnumber is 284.
[Magisk] J4jks:
I've installed NanoDroid microG module magisk mode but it seems not working fine

Self check is fine, given all permissions

But status is disconnected ,no apps are showing in gcm using apps

I'm using odexed ROM (los 15.1 kenzo by Abhishek) + xposed+fakegapps
[Magisk] kurtn:
Doesn't work as good as in nougat.
[Magisk] iacchi:
The beta version of QKSMS seems to have some issues. For starter, it doesn't open the context menu when I hold on a message. Might be worth going back to the stable version?
[Magisk] Setialpha:
This is not a NanoDroid issue, but microG and is already plenty discussed in this thread, search for GCM in here.
[Magisk] Setialpha:
I already re-uploaded with QKSMS 2.7.3, but I forgot to inform the people.
[Magisk] iacchi:
Good to know, I'll re-download then.

EDIT: [MENTION=4187311]Setialpha[/MENTION] I've just re-downloaded and re-flashed NanoDroid, but the QKSMS app has not changed, still v. 3.0b8.
[Magisk] Setialpha:
You may have to uninstall app updates.

Edit: From where did you download?

It seems something went wrong when exchanging files. I'm currently re-uploading again, just to ensure it includes QKSMS 2.7.3.

QKSMS 3.0 beta9/10 include many fixes, so I'll see if it can make it into 17.0 beta again.
[Magisk] iacchi:
I downloaded the file a few minutes before I wrote the message from nanolx. I don't think it got updated on its own after re-flashing nanodroid.
[Magisk] deedeeceleb:
Nvm I got it. Thank you very much :)

Gesendet von meinem ONE A2003 mit Tapatalk
[Magisk] jenslody:
What did you do exactly ?

Steps are:

open Yalp-store,

search for Threema,

on the Threema-site ttap on the three dots at the bottom-right,

in the opening menu tap on manual download,

put in the build-number (284),

wait untilthe button changes from checking to download,

tap on download,

after download, install
[Magisk] Setialpha:
Uploaded NanoDroid Play Store 9.5.09, use 'nupd ps' as root to update.
[Magisk] :
Seems Like you need busybox for this command. Either this or I needed to install bash.
[Magisk] Setialpha:
Busybox is required, yes.
[Magisk] inVain_theGenuine:
thanks to your post #2923 I've re-read the documentation again.

apparently quite a few things have changed.

and yes, the patcher works flawlessly on a fresh installed rom. Sublime works by Setialpha! :good:

this time, I just manually copied the contents of Nanodroid's microG (with microG's fakestore) + FDroid (without the xbin).

I flashed NanoDroid with only the overlay and scripts features to debloat the Slimroms.

everything run exceptionally well, eversince.

whatsapp led notification has never failed on me again even though I run my phone behind orBot.

I don't know if this is what made the difference; that I've switched my messaging app from Silence to QKSMS.

I did this because I found out that Silence use the same extra library file as whatsapp (libcurve25519.so), their sha-1 & md5 are exactly the same value... so I thought they might had conflict with each other.

[MENTION=4187311]Setialpha[/MENTION], you've made an excellent choice of apps to be installed alongside with Nanodroid! :good:
[Magisk] Setialpha:
'only ... with Magisk', so there's more with Magisk.
[Magisk] DEVILOPS 007:
Am I still able to use the Google app with this? I use the Google integration feed with Nova launcher.
[Magisk] marcdw:
Not sure but I doubt it. Google App probably most definitely needs the actual Play Services to function properly.

If you have microG already, test and report back.

LG G3 D851, PAC-MAN LP ROM, MultiROM, Tapatalk 4.9.5
[Magisk] :
Since microG pretends it's the official Play Services, it might actually work, since other Google apps work just fine. But I'd like to know for sure too, so yeah, please report back ;)
[Magisk] inVain_theGenuine:
please excuse me for the OOT, but what is this Google app actualy doing?

I'm an oldschool, I use browser for most of my internet need... that includes youtube and downloading most of my apps via the apkmirror.

currently I'm using ms launcher and disable its feed feature just because I don't have a single clue of it (I swear I don't).

I believe ms launcher's feed is something similar with Google app, CMIIW :D
[Magisk] Nonononoki:
Any way to get Nanodroid working on unofficial Magisk? Because the official version does not support Treble supported Android yet
[Magisk] :
It should work with any version, but you'll have to test yourself. If it doesn't, just flash it in TWRP.
[Magisk] Nonononoki:
When flashing in TWRP it either says it requires Magisk 15.0 or up (unofficial version says "Magisk 16.3-UNOFFICIAL", I guess it's a simple String check?) and aborts the process. I'm using the MicroG version, am I missing something? I've read that Magisk was not needed for Nanodroid.
[Magisk] Setialpha:
It checks against the version string in util_functions.sh, dunno what it is for that version? Link?

No, it's not needed, but if it detects magisk.img it will try to install in Magisk Mode. Use nanodroid_forcesystem=1 in the setup file to force System Mode installation.
[Magisk] Nonononoki:
Thanks for the help, wiping system was the solution for the problem. Custom Magisk I use: https://xdaforums.com/showpost.php?p=76103355&postcount=8505
[Magisk] Setialpha:
The first beta for 17.0 will land this weekend. What's to expect: OTA survival/addon.d for System Mode installation (Full, microG, F-Droid packages).

The l33t h4x0rs can create a package from GitLab repository to try it out right now.
[Magisk] guest4711:
It's working for me (Magisk 16.3 (180408)).
[Magisk] marcdw:
Google App is also known by different names. Google Search, Google Now, and Velvet. You've probably used it on stock ROMs as it's one of the main tools in Google's catalog. Provided OK Google (voice) searches.

Gapps packages of Nano and higher (Open GApps f.i) include it.

Google Now Launcher and Nexus/Pixel Launchers include swipe-right-to-view out of the box. Nova, Flick, and Lawnchair support that via add-ons.

ZTE Axon 7 A2017U, Stock B32, Tapatalk 4.9.5
[Magisk] :
Yalp store got an update. Is it possible to update it if you installed it as a system app similar like the nupd ps command or do we have to uninstall it and reinstall the new version as a system app?
[Magisk] :
You can update it if it's got the same signature, which it should, since it's downloaded from F-Droid.

By that I mean, you'll have to update it from F-Droid.
[Magisk] :
I see, so the signature is from f-droid. We will have to wait a week then.
[Magisk] :
I guess so
[Magisk] Setialpha:
NanoDroid PlayStore 9.6.11 uploaded, use 'nupd ps' (as root, on device) to update.
[Magisk] abacate123:
Wew, thanks for the fast updates fellow :)
[Magisk] YiPing_Huang:
Is it normal that my phone vibrate like crazy after issuing "nupd ps"?
[Magisk] Wo11ven:
Same here, but a lot of weird text and symbols appear like crazy and it fails to update at the end. Will edit with video soon.

Edit:

[youtube]ms2VvoG3F0w[/youtube]

Running Lineage 7.1.2, same happens with last the 3 versions of NanoDroid that I tested, haven't tried older versions. System mode.
[Magisk] Setialpha:
Hmm... what busybox do you have installed? It seems it's 'wget' applet is broken and outputting the apk to stdout instead of the destined path. The vibration and stuff is then the to be expected shell 'bell' triggered by the output.

If you don't I strongly suggest using [MENTION=4544860]osm0sis[/MENTION] busybox in the latest version, which is known to work™.
[Magisk] kecodoc:
[MENTION=4187311]Setialpha[/MENTION]

Please help me me I try install NanoDroid-microG-16.5.20180402 to my devices use lineages os 15.1 android 8.1 error google play has top working.

I try enable Google device registration setting and install fake gap module from xposed I can't fix.
[Magisk] Setialpha:
Does Play Store have required permissions? Did you reboot after setting up microG? Where's the logcat?
[Magisk] YiPing_Huang:
I installed osm0sis' busybox from Magisk. No more random symbols and vibration.

But it throws me a line of error. I am not sure if the update is successful or not.
[Magisk] Setialpha:
It's some Termux issue, not related to nupd.

The word 'Success' comes from the package manager, so it did work.