yashsingh1/xdaforums huggingface dataset:
[Magisk] Draygon:
Thanks a lot for the answer, just found out that my TWRP version doesn't support Aroma.

I created the file manually like mentioned in the setup. It worked at my first try! :)

Could someone tell me what these packages are for?

- nanodroid_overlay

- nanodroid_mapsv1

- nanodroid_swipe

Thanks a lot so far, I hope Nanodroid will replace my Google Play Services for a long time.
[Magisk] Oswald Boelcke:
All covered in the excellent full documention/Wiki that is linked in the OP. Pease check this part regarding your specific question:

https://gitlab.com/Nanolx/NanoDroid/blob/master/doc/AlterInstallation.md
[Magisk] Setialpha:
Could someone with bootloop issues on LOS 16 upload the /system/framework/framework-res.apk? Thanks.
[Magisk] lindroidux:
I am unable to upload here. Any other option?

I usually uninstall nanolx b4 update & reinstall after flashing lineage update.
[Magisk] garylawwd:
Upload it to mega and leave the link here
[Magisk] andy356:
Firefox Send would be a better suggestion, no?
[Magisk] garylawwd:
Whatever he wants I suppose. He can even upload to gdrive or Dropbox of he wanted to.

It was more just suggesting he upload to a cloud drive and share the link.

He can use whatever he wants but I know where you are coming from, in the spirit of open source and privacy Firefox send is an option
[Magisk] lindroidux:
[MENTION=4187311]Setialpha[/MENTION]

[send.firefox.com/download/4702d9802b41543b/#nW7yj-jbpZnlYgaWmrq_0g]
[Magisk] garylawwd:
[MENTION=4187311]Setialpha[/MENTION]
[Magisk] starbright_:
satellite (sipgate app)

No it is not - but this is not end of the world.

There is a workaround. Just log in at a "normal" (not microG) device. Than create a backup via oandbackup and restore it at your micro-G device. Don't forget to anounce it to microG by "nutl -r" (in adb shell with root permissions).

It is recognised as GCM app. Seems ringing works after disable battery optimization for this app.

There is a entry here:

https://github.com/microg/android_packages_apps_GmsCore/issues/809
[Magisk] malefient:
I have encountered an issue after installing latest - 15.1-20190628-NIGHTLY-santoni - update on my Xiaomi Redmi 4X device.

Lineage OS was installed Feb 2019 having following components:

- Lineage OS build number lineage-15.1-20190224-nightly-santoni flashed with twrp-3.2.3-1-santoni;

- signature spoofing enabled using NanoDroid-patcher-20.6.20190126;

- root permissions patch flashed;

- microg apps installed and launched successfully;

No system updates were installed until today. After update had been installed I noticed absence of microg apps accompanying disabled both signature spoofing and root permissions.

I tried to reenable signature spoofing with flashing NanoDroid-patcher-21.0.20190601 but it didn't help.

Is this issue related to NanoDroid patcher? This is incorrect behaviour given that "flashing the on-device Patcher zip it also installs an addon.d script that auto re-patches the ROM upon update".
[Magisk] amg314:
You should be rooted to install microG.

So, install magisk.zip thru TWRP or Magisk Manager and then try Nano Droid or any other tool.
[Magisk] malefient:
The problem is not how to install microg apps but why the already installed microg apps are deleted after system update. Together with root permissions deactivated and signature spoofing disabled.
[Magisk] amg314:
If your OS update changes boot.img, you will lose Magisk root.

If your OS update change the system.img, you will get unpatched framework.jar, stock gms core, etc.
[Magisk] Setialpha:
Only if addon.d isn't supported or not working. Else both will stay intact.
[Magisk] malefient:
Then what information do you need to find out that?
[Magisk] Setialpha:
Flash the update manually and post the log. Normally the addon.d prints messages to the user that it's doing stuff.
[Magisk] eigerzoom:
another lost soul tryin to pass safetynet

thanks for any help

device is LG-US998/LS998 V30+ Thinq on H930 Havoc 2.5 rom

(i've also tried liquid remix rom)

bootloader unlocked

with microg safetynet set to on - magisk check fails both cts and integrity

safetynet off - magisk check returns api error

i've performed this command

pm install -r /system/app/DroidGuard/DroidGuard.apk

have tried with/without droidguard magisk hide

have tried default gmscore and nano

have tried full install and the setup method followed with microg.zip/bromite.zip

magisk is installed and i've tried with v18.1 as well as v19.3

twrp version is 3.2.3.7 however i have 3 different versions available and wondering if this might be the issue

TWRP-3.2.3-7-DataIMG

TWRP-3.2.3-7-default

TWRP-3.2.3-7-IntSD

here's the system test

https://privatebin.net/?d706d9b83482cfa4#RBXZyTePghcEbb4Nqd9xcQ/qRWmiUccN0dLgmnZArE8=
[Magisk] temporarium:
Just curious why you're moving away from the custom to the official microG implementation?
[Magisk] eigerzoom:
oops i see you were responding to the new release ... haha
[Magisk] Setialpha:
As stazted in the issues section of the documentation: you can't currently pass SafetyNet with microG.

Because all changes by 3rd parties are now upstream, half of those from me or Vavun aswell, the other half is currently under review. With the changes merged into upstream, the fork becomes redundant, simple as that.
[Magisk] andy356:
You plan on releasing stable after these get merged, right?
[Magisk] Setialpha:
Nope, NanoDroid's development is not related to microG, so the stable release will come when ready.

Once the microG changes are merged and mar-v-in rolled out a official release including them, I'll no longer create custom microG builds
[Magisk] andy356:
Will custom microG users be automatically migrated to the official one then?
[Magisk] lindroidux:
Bootloop in latest beta version too (same issue since previous 2 releases). Reboots into recovery after flashing nanodroid.

Unable to upload logs due to error "bad request".

After the issue cropped up, I usually flash LOS,/reboot, flash nanodroidr, boot and then apply sig spoofing patcher. Problem is logging into play store & permission requests from apps everytime after LOS updates.
[Magisk] Setialpha:
Upload the log somewhere, please. Also: don't uninstall NanoDroid before the update, that's the reason for the permission/login issue. System Mode or Magisk Module installation?
[Magisk] Setialpha:
Yes, as I said.
[Magisk] lindroidux:
Logs are here:

https://send.firefox.com/download/54fb0d06e19007b8/#RvuW6-mAQytdHy39Zt0Bbw

After flashing LOS update, it boots to LOS logo/bootscreen & then reboots to recovery after a vy long display of LOS boot logo. Then I uninstall nanodroid, reboot to LOS.

Afterwards, flashing patcher & nanodroid gives no issues till next LOS update

It is magisk 19.3 installation.
[Magisk] andy356:
[MENTION=4187311]Setialpha[/MENTION] The documentation mentions that there are differences between the official and custom microG cores, and then links to your microG fork on GitHub. I can't find where the changes are listed, though. Help?
[Magisk] Setialpha:
https://github.com/microg/android_packages_apps_GmsCore/pulls/Nanolx
[Magisk] andy356:
Thanks! I hope they get merged soon.
[Magisk] Setialpha:
Huh? What makes you think that I'd stop?
[Magisk] Kajuru:
He will drop the custom gmscore, not nanodroid
[Magisk] oseiasrodrigues0:
If I install the nanodroid on my ROM that has Gapps, the nanodroid uninstall the Gapps?
[Magisk] Valdrio:
Hi I'm actually on revenge os on Dipper, air only installled microg, and f-droid module but apps purchased from playstore can't check the validity of the license. I want to provide a log about that. How do i do it? Thank. You very much.
[Magisk] dhacke:
Install a logcat app (for example Matlog) or use the log function of adb.

Then trigger the error while the log function is active and upload the log here.
[Magisk] marcdw:
There is no log to provide. Apps that do license checking or use in-app purchasing require the Play Store to handle that. It's not a bug or issue, just the reality of things. Install the Play Store or don't use such apps.

If you decide to install the Store you can flash Shadow53's patched Play Store zip instead of reconfiguring & reflashing NanoDroid. It can then be updated via F-Droid if you have the nanolx repo added (which you probably do since you're using NanoDroid).

https://shadow53.com/android/downloads/microg/

ZTE Axon 7 A2017U, /e/OS 0.7-n ROM, microG (NoGapps), XDA Legacy
[Magisk] rayman95:
Just want to know how to upgrade an already patched rom??? From viper 3.6 patched to 3.7????

Thanks...
[Magisk] DrUnknownEMC:
Clean flash
[Magisk] Setialpha:
FYI: the custom microG GmsCore and DroidGuard Helper build were removed from the repo yesterday. Starting with 22.0 stable, users will be migrated to official builds.

Releases will only contain official builds, obviously.
[Magisk] Setialpha:
Another heads up: there will be a second beta for 22.0 soon, with APKs shipped BZip2 compressed. This should fix the issue that the full package requires atleast 512 mb usable space in TWRP. But of course needs to be tested for it's performance impact.
[Magisk] eerovil:
When switching from the custom microG to the official one a complete uninstall is needed (I used Titaniumbackup to uninstall after clearing data)

This will unregister the phone from Google cloud messaging, so when microG is reinstalled the FCM key will not match in any apps and thus FCM will not work.

I didn't want to reinstall all my FCM apps, so I deleted the keys by running

cd /data/data; find -type f -name '*gms.appid*.xml'

with the

-delete

flag. After that all apps were showing as registered in microg settings.

FWIW just clearing the cache should also work, but it did not for me. For anyone else struggling with this that command is worth a shot.
[Magisk] Setialpha:
There's

nutl -r

for this purpose.
[Magisk] Setialpha:
Development update:

- compressed apk installation works well (saving about 120 MB space in TWRP for full package)

- several bugfixes in Uninstaller for System Mode

- fixed bootloops with LineageOS 16

- massively inproved build-package script
[Magisk] eigerzoom:
Google maps doesn't work very well.

I've tried a few different angles of attack without much success.

maps go with chromium installed + auto updater and also regular google maps, and just using a mobile browser (but navigation doesn't work)

I've seen some of the talk about the api version changes, but i dont really understand whats going on under the hood.

can i simply run an older version of google maps for full compatibility?

any idea what version of maps the major changes took place if this will work.

i have a really old version (5.3.1) i keep for just these scenarios, which doesn't seem to work on pie unfortunately

when i load google maps, it will only download a local tile, if at all, and cannot pan or load nearby areas at all.

just trying to understand if anyone with some knowledge feels like passing it on....no obligation haha....

I
[Magisk] kostas gp:
9.84.2 is the latest version that can work
[Magisk] eigerzoom:
thanks

i found the proper arm64 high dpi version on apkmirror

if you use titanium backup you can unlink it from the market so it doesn't auto update
[Magisk] Kajuru:
That fixed the issue on beta 1 where Osmand and fdroid would refuse install. Now all is good.
[Magisk] Setialpha:
20:41 CEST: currently re-uploading beta2 with an additional compatibility fix for LineageOS 16 for microG.

20:50 CEST: re-upload finished.
[Magisk] :
No issues upgrading to beta2.

All functions work correctly.

OnePlus6

Omni 9-20190707

MicroG package.
[Magisk] vjdennis77:
Hi guys , after flashed nanodroid microg (latest beta2 july09) , chrome crash and didn't open , what I need to do pls ? I'm op6 with superior custom ROM ( signature spoofing support )
[Magisk] lindroidux:
Installed without any bootloop or other issues. Thank u vy much :good::good::)
[Magisk] Setialpha:
Wait for next release of microG, it's a known bug.
[Magisk] ewong3:
crdroid update... sharing

just tried dirty flashing latest 0709 nanodroid over 0708 crdroid on op5, and had 'phone is starting' error reported by many in that thread. Then tried clean flash (ie format data) from scratch. the PIS issue still there, but after a couple of restarts and long waits (up to 10mins I think) the system is finally up and running.

just thought this may help those out there despairing on the PIS problem...
[Magisk] Setialpha:
Dunno what error that is. Anybody provided logs?
[Magisk] ewong3:
this is a widely reported bug, but not fixed despite many attempts, some put it to livedisplay issues, see discussions in crdroid thread: https://xdaforums.com/oneplus-5/development/rom-crdroid-android-5-0-t3836886

even more heavily talked about in its tg group so won't repeat it here...
[Magisk] orawnnd:
Do these Modules work on any ROM? In my case Xiaomi.eu on Mi9. And when installing microG, do I have to uninstall all google services?
[Magisk] PoochyX:
Yes all of it.... Just keep contact and Callander sync adapters else won't have access to your calender events and contacts

([emoji813]9/[emoji725]/9[emoji813])
[Magisk] vjdennis77:
OK thanks
[Magisk] d1n0x:
No, you need a ROM that supports signature spoofing or you need a deodexed ROM that you can patch to support signature spoofing.
[Magisk] Bracher:
Sorry for asking but searched and found nothing: after a new Installation with Magisk 19.3, Nanodroid microG and F-Droid 21.0 official F-Droid is complaind installation of microG Service Core failed Error -7: a previously installed package of the same name has a different signature than the new package, when I searched for the logs I found only logs about the f-Droid installation - strange, but everything works well: playstore, gps..., Osmand
[Magisk] Setialpha:
Already been asked and answered in this thread a few times.
[Magisk] kostas gp:
Does anyone else has issue with titanium backup? It stays on preview page and I can't do anything
[Magisk] githyanki:
It's probably requesting root at that point. Check Magisk install to make sure all is ok.
[Magisk] kostas gp:
Root, busybox etc are all ok. Addon is also installed. I've reinstalled everything many times but it doesn't get to work. I thought that micro g could be the issue. I don't know if it works for other users
[Magisk] raptorddd:
how do i install bromite webview.? does gcam work with it.?
[Magisk] :
Flash bromite zip. Yes, atleast it works at my end, on op6 with syberia
[Magisk] raptorddd:
do i need to delete google webview.?
[Magisk] Setialpha:
No.
[Magisk] Setialpha:
Official nightly build with post-release fixes by [MENTION=3999488]MaR-V-iN[/MENTION]

https://microg.org/dl/GmsCore-v0.2.8.17785-4-06c8b76.apk
[Magisk] tsky7:
On the new NanoDroid Version 22.0.20190713 i get Error 1 in TWRP
[Magisk] :
Does your nanodroid fdroid repo include now on official builds or is it harm to add official build fdroid and update that way ?
[Magisk] Setialpha:
No, official build = official repo.
[Magisk] Setialpha:
Re-uploaded with a fix.
[Magisk] tsky7:
Thanks!
[Magisk] :
Did anyone else loose their contacts ans caller log after flashing 22.0? I did for some strange reason.. luckily i had it backed up though..

Got no errors in twrp
[Magisk] Keule-Tm:
Luckily not at all. My contacts are served via DavX5, but my call history stayed intact as well.

BQ X5+, LOS14.1 custom build.
[Magisk] kostas gp:
Does this have a different signature? I can't install it as an update
[Magisk] PoochyX:
Good to see this forum still very active

([emoji813]9/[emoji725]/9[emoji813])
[Magisk] ewong3:
Environment set up advice?

been on this rom for several weeks but not been using it as main driver due to need to familiarise with entirely different set up from google based ecosystem. Still some questions surrounding the utility, and hoped someone could point out the best config going forward:

1) what is the best foss backup app to install for restoring most if not all the nanodroid data/apps? currently every nanodroid/rom upgrade means complete individual installation/set up and it is a bit tedious...

2) is it possible to go for non-google based account management completely, and if so what is the replacement set up in:

a) microg (currently i just enable all items in the microg settings);

b) credentials / acc apk;

c) calendar/contact/mail/whatsapp (if not already in the current full package);

3) if still opting for google based management (as opposed to 2 above), what are the settings in microg/magisk/etc that give you progressive level of privacy (vs loss of functionality)?

If there is a link to some discussion on this that would be perfect... I am sure this set of questions is common amongst all non-programmer users out there.
[Magisk] PoochyX:
You need Google more then you know

([emoji813]9/[emoji725]/9[emoji813])
[Magisk] :
I had no issues with it. Flashed the update in twrp, and stumbled upon it. Are you running something else than the official one perhaps?
[Magisk] PoochyX:
How about you go back to stock

([emoji813]9/[emoji725]/9[emoji813])
[Magisk] kostas gp:
Damn, after clean flashing rom it installed normally. I don't know why my phone acts weird. Now I can't get play store to work no matter what I do. What the hell, it always gives server error even if I clean storage, reinstall it etc. Oof

---------- Post added at 04:37 AM ---------- Previous post was at 04:36 AM ----------

Yee it's good
[Magisk] hengkidermawan:
thank you for the latest nanoBromite
[Magisk] Draygon:
EDIT: Used search and recognized that Safetynet is broken right now with Nanomod.

Would be great if it will get fixed in future.
[Magisk] Setialpha:
It's an official nightly build, so it's signed with official key.
[Magisk] PoochyX:
That's because Droid helper hasn't been updated [emoji24]

([emoji813]9/[emoji725]/9[emoji813])
[Magisk] Draygon:
Hi,

my push messages for GCM registered apps are not working. When I send a message from my 2nd Smartphone via Signal / Whatsapp, the message arrives when I turn on my display.

Battery optimization is disabled for Signal, Whatsapp and microG Service Core. The messenger apps were installed after GCM was enabled inside microG.

Can someone please tell me what is wrong? Thanks!
[Magisk] kostas gp:
You're right, it seems that I couldn't update it because I had first install 22.0 beta 1. But another issue came up. I clean installed 22.0 stable and there was no way I could get play store to work. It always showed server error. But if I first install an older build and then update to 22.0 stable then it works. Was latest stable tested on a clean installation?
[Magisk] vjdennis77:
Guys , after installed latest stable on my op6 and most of g apps are lag , is that normal ? Especially chrome app
[Magisk] PoochyX:
On newest beta 2 how can I use the Google play store instead of aurora before nanodroid came with play store and now it comes with aurora also fake my gps now works with micro G only thing is I haven't been able to get the last box checked [emoji24]

([emoji813]9/[emoji725]/9[emoji813])
[Magisk] garylawwd:
You need an aroma supported recovery and flash the setup wizard to configure installation and then flash nanodroid
[Magisk] PoochyX:
Im using twrp isn't that an aroma supported recovery also i got the last box checked but I'm not receiving notifications for tapatalk and is this normal

([emoji813]9/[emoji725]/9[emoji813])
[Magisk] guest4711:
Create a config file for Nanodroid by hand. See the following description:

nanodroid_play=[0|1|2|3][0|1]

what app store to use:

1st item
0 = No App Store
1 = Play Store
2 = Yalp Store
3 = Aurora Store
2nd item
0 = without Fake Store
1 = with Fake Store

So use nanodroid_play=10 in your setup file.
[Magisk] alfadyn:
after a clean install i cant see the apps provided by nanodroid. only app that appears with it is aurora store. I think the GNU zip change has something to do with this.

Im using TWRP 3.2.3 on Z5 Compact
[Magisk] Setialpha:
Not related, it's working fine.
[Magisk] alfadyn:
what can cause to this problem mate. i really appreciate your work on this. let me tell you the steps i follow.

1. Wipe data, system, dalvik, cache.

2. install "LineageOS for microG" for Z5 Compact

3. installed Magisk

4. boot up the system

5. again in TWRP

6. install latest Nanodroid

7. install latest BromiteSystemWebView

8. reboot

before i begin i even reflashed the latest recovery
[Magisk] Setialpha:
Dunno, I can't see anything without the installation logs.
[Magisk] PoochyX:
How do I make this config file and where do I place it so it gets read by twrp when I flash the microG zip file and are notifications broken for up to date apps cause tapatalk isn't sending me notifications nor is Messenger only one I'm getting notifcatons for is telegram and it haven't even registered with Google cloud messaging

([emoji813]9/[emoji725]/9[emoji813])
[Magisk] :
[MENTION=4187311]Setialpha[/MENTION] any info what might cousing my droidguard stops/crash when trying open some apps or trying safetynet test? here some log

or is this normal behavior for now ?
[Magisk] guest4711:
Reading the fine manual (or using the search function in this thread) you'll get the answer:

Put the options one per line and save the contents as .nanodroid-setup (dot nanodroid-setup) into the root of internal storage (usually /sdcard) or in root of /data
[Magisk] marcdw:
See post #3.

Moto G5S Plus XT1806, balanceOS 2.0, MultiROM, XDA Legacy
[Magisk] PoochyX:
I did the file like this and it still installed the aurora store is there something I'm doing wrong

([emoji813]9/[emoji725]/9[emoji813])
[Magisk] :
No, create a .txt file thats named ".nanodroid-setup"

I've put mine in /data. I wanted fakestore instead of playstore, and I like aurora, though Ive installed yalp also.

Mine looks like this, but you should use "nanodroid_play=10" instead

nanodroid_microg=1
nanodroid_fdroid=1
nanodroid_apps=1
nanodroid_play=31
nanodroid_overlay=1
nanodroid_zelda=0
nanodroid_mapsv1=1
nanodroid_init=1
nanodroid_gsync=0
nanodroid_swipe=0
nanodroid_forcesystem=0
nanodroid_nlpbackend=1100
nanodroid_bash=1
nanodroid_nano=1
nanodroid_utils=1
nanodroid_fonts=0
[Magisk] PoochyX:
Apps are not registering for push notifications

([emoji813]9/[emoji725]/9[emoji813])
[Magisk] :
Are you using an adblocker of some kind? Whitelist mtalk.google.com.

You can also try to dial *#*#2432546#*#* (*#*#Checkin#*#*, if thats easier to remember) to manually register

Also, try using the nutl -r command, followed by the apps actual name. Youll find it in app settings.

Heres an example

nutl -r com.snapchat.android

Must run as root, so enter "su" first to run as root
[Magisk] PoochyX:
I should whitelist that on my energized host file and minminguard is okay right

([emoji813]9/[emoji725]/9[emoji813])
[Magisk] Oswald Boelcke:
If you're using e.g. Adaway I suggest not to manipulate "your energised host file" but to simply add mtalk.google.com to your whitelist in Adaway (please refer to third screenshot). Here's the respective section in the excellent NanoDroid readme that is worth to be studied.

Also my personal best practise: The apps I want to be registered for pushes I always manually install them

after

the installation of µG and I don't restore these apps by Titanium Backup (TB). After the "manual" installation, I only restore their data from TB. By this method I always achieve the desired result, and I don't use any of the alternative methods described in readme.

I assume you already got a "functionable" .nanodroid-setup file. I added two screenshots of mine just for completeness (location and content). Please observe that the filename starts with a dot and that it doesn't bear a suffix.
[Magisk] PoochyX:
Oswald always good to hear from you

.. You always give the best help

([emoji813]9/[emoji725]/9[emoji813])
[Magisk] guest4711:
I told you to put one option per line into a file called ".nanodroid-setup" on the root of /data or /sdcard. As far as I can see you did create one file per option (btw: don't miss the leading dot!)
[Magisk] PoochyX:
That setup file is a text file right

([emoji813]9/[emoji725]/9[emoji813])
[Magisk] Oswald Boelcke:
Negative; as I stated here it doesn't bear a suffix i.e. it is NOT .nanodroid-setup.txt but only .nanodroid-setup