yashsingh1/xdaforums huggingface dataset:
[Magisk] Oceanik:
May be... Seems so... You know better. :)

Attached it to this post.

[RR5.7.4 clean install, some patches, kernel, Magisk-v12.0.zip, NanoMod-microG-9.1.20170607.zip (all defaults)]

> [boot system, MagiskManager-v4.3.3.apk, XposedInstaller_by_dvdandroid_29_04_17.apk]

> [reboot > adb debugging on, logcat started]

> [reboot recovery, NanoMod-patcher-9.1.20170607.zip, xposed-v87.1-sdk23-topjohnwu.zip]

> [boot system, start Xposed Installer (Xposed Framework version 87.0 (Systemless by topjohnwu) is installed, but not active), logcat stopped]

If you need smth. else or some tests, I'm at your service.
[Magisk] totalcmdext:
Is it possible to install Naono-MicroG with Yelp store instead of Play store?

In the initial script the nanomod.play=1. So, if i put nanomod.play=0 will it install Yelp?
[Magisk] Oswald Boelcke:
Negative!

From the Github Alter Installation
[Magisk] Setialpha:
Just in case someone missed it: the latest Magisk v13 beta fixes the issue of modules not working in parallel. NanoMod 9.3 onwards will no longer bundle Magisk Manager, as it's bundled with Magisk now.

In case you're annoyed by Play Store updating itself, you'll find my modified version 7.9.53.Q here. Also the changed I made to Play Store (more precisly the diff) is now at github, too.
[Magisk] DJ aliasz3d:
Thank you for this playstore update :good:

I'll have to thank you once I get some back.

Edit: working well :good:

I should add when I updated playstore manually (before your Phonesky apk) to a newer playstore 7.9.2.53Q the same as yours is when I checked system/priv/app it would crash upon doing a IAP just like you mentioned in the github page. It is now working again with your Phonesky.apk. don't know if it's worth mentioning.
[Magisk] RobotPhone:
How should we install the apk? Just overwrite the old one in /system/priv-app/Phonesky/ ?
[Magisk] Setialpha:
install normally by tapping on the apk from file manager on device (easier).
[Magisk] Calvin.manneson:
has anyone used the dex patcher on s7 tw?
[Magisk] Setialpha:
It works on S6 TW, so it should on S7, too, IF the ROM is deodexed.
[Magisk] Calvin.manneson:
thanx for replying..used your s6 hybrid rom.

I tried on one(nougat) ended with error...will try another.

I don't have access to a pc atm
[Magisk] Setialpha:
9.3 beta1

Version 9.3 beta1 is now available. Changes since 9.2:

* Internal Changes
* Full, F-Droid, microG packages: fix installation in system mode
* remove bundled Magisk Manager (now bundled with Magisk itself)
* Updates
* microG Gms Core (0.2.4-103)
* Substratum (782)
* Yalp Store (0.16)
* Simple Calendar (2.5.2)
* Simple Gallery (2.10.10)
* Termux (0.51)
* Twidere (3.6.18)
* VLC (2.1.11~beta)
* Play Store (7.9.52.Q)

Download from AFH, beta builds for Full, F-Droid and microG packages available.

Feel free to test and report any occurring issues. When testing with Magisk either use v12 or latest official v13 beta.
[Magisk] Wo11ven:
[MENTION=4187311]Setialpha[/MENTION], could you possibly provide a few steps to what one would need to do in order to port NanoMod to x86, using your GitHub repo as base?
[Magisk] Torrify:
Has there been any progress with this?

I am still encountering game-breaking bugs, despite switching to XPosed and using the FakeGapps patcher as suggested

It seems the background/fused location service is not working. Even with all the MicroG self checks passed and app permissions granted, Google Maps will not acquire a location unless left to sit for some time, AND then manually closed re-opened. Even then, it will lose it shortly thereafter and not regain until restarted.

Other apps requiring the background location function either crash on opening or are unable to resolve maps, location, or both. Additionally, installing some these apps often results in spontaneous hard reboot, usually within 30s of first start.

There also seems to be problems with Cloud messaging but I'll leave that to later..

Rolling back to either official GApps or even the Nougat Lineage+MicroG ROM largely restores normal functionality, so it's not the apps, and it's not the hardware. I suspect it is a problem with the MicroG package itself, though I'm unsure what.

I would like to provide the logs you suggest but I am still unsure of the best way to do this i.e. when do I flash the zip? After first boot? After trying to use one of the problematic apps? After trying all of them? After a spontaneous reboot?
[Magisk] Setialpha:
All Magisk Modules can be installed from TWRP and Magisk Manager, that's neither new, nor should it be confusing, except you confuse the terms Magisk Manager and Magisk Module.

NanoDroid is the only Module diving deep into the system, thus it's safer not to flash from running system.
[Magisk] Setialpha:
Yes, a few posts back I uploaded a test buuld for the Patcher,

The installation logs in /data/adb are created after installation ends (either successful or not), so you post them directly after flashing.

Again, the SysTest zip has no prerequisites, just flash and post the log.

The Maps issue was already largely discussed here, it's currently not working with microG, except using and old Maps 9.x version. Not related whether unlp works or not.

GCM is fixed with the current release of microG, make sure mtalk.google.com is not blocked by your adblocker (if any), also, as always with microG: first install and setup microG, then tbe apps, else they'll never register.
[Magisk] Vavun:
Is anyone has problem with viber and instagram push messages with microg ?

All new viber builds are registered, but do not receive push messages in microg. And every new buil re-register itself in microg after every update.

Instagram correctly receives all push messages, but the phone does not go out of sleep.

I see new messages only after opening Instagram or after some time

For example Telegram has no such problems for me.

Sorry for bad english
[Magisk] Torrify:
Thanks. Unfortunately:

-The new patcher is producing no different results, I am still getting major lag in touch response and menu switching.

-The latest version of GoogleMaps (dowloaded fresh from yalp) DOES work flawlessly with MicroG, as a part of the current "lineage+MicroG" builds, as does background location provider for other apps like weather, fuel map ett. So it can't be a broader microG issue as you say - it is something specific with these builds and however they are interacting with the rest of the system. L

- I am flashing MicroG prior to any app installation, and I have no adblockers, firewalls, or hooking modules (ie XPrivacy). Whatever is causing this, it's MicroG.

-I understand the SysTest zip has no pre-requisites, my question is at what point should it be run in the order of setup, in order to capture logs with useful information? Immediately after first flash? After installing Maps and trying to get a location lock? After installing apps that crash out or bootloop? Both? What is most useful to you from a diagnostic perspective?

Thankyou
[Magisk] friedCELLS:
I've been running these modules/microg from this thread for over a month without issues on my stock rooted LG V30. But for the last few days, I'll see Google services library updating on it's own, then I'll see an update notification for Google services core in F-Droid, the update will fail, then again Google services library shows again downloading on its own in download manager, then F-Droid again will show an update for the same and fail again, and over and over. It looks like something automatically updated from Google, and F-Droid microg can't override it. Everything still works fine, but I'm constantly bugged by the notification from F-Droid about an update that fails every time. Previous updates always worked. How could I fix this?
[Magisk] lucastracq:
just tested again stable nanodroid full package, this time without mpv. installation fails at installing zelda sounds.

also tested new systest zip, working 100%.
[Magisk] raptorddd:
https://xdaforums.com/showpost.php?p=78197828&postcount=4760

i did it yesterday i updated both playstore and microG from his repository in Fdroid.

i still need to use playstore and see if problem is gone..
[Magisk] lucastracq:
[MENTION=4187311]Setialpha[/MENTION]

i've done more testing, each time disabling what failed before. in the end, nanodroid installs fine without:

- mpv

- zelda sounds

- twidere

- xda labs

- gnu bash

- shell utilities

- nintendo fonts

in the zip file attached there are logs for each failed installation (named after what didn't install).

a few more questions:

- first time i opened termux it tried to install something and then crashed, now it doesn't start anymore. is it related to nanodroid and/or the fact that gnu bash and shell utilities weren't installed?

- amaze file manager crashes when opening settings. for sure it's not nanodroid's fault, right? is it happening to you too? fixed in next version

- in microg self check there is one voice "Play Store (Phonesky) installed" unticked. i'm using just yalp store, do i need also fake store?

ok, i've finished :) sorry for the long post and let me point out that i'm not complaining nor pushing you to fix things, i just hope all this can be useful in some way to you and your project.

thanks a lot again for all your time and hard work!
[Magisk] DoR3M3:
[MENTION=4187311]Setialpha[/MENTION] in my rom when using microG this section;

System supports location provider

Your system does not support this UnifiedNlp package.

Either install a matching package or a compatibility Xposed module.

Can the Nanodroid-patcher be made to take care of this support? My understanding to inject/patch the framework.jar?

I just did a SuperR's Kitchen Deodex and then applied Tingle, thinking this would work, but Tingle doesn't take care of this either...

It would be really great if you can make the Nanodroid-patcher using the Deodeox methods you have listed, I use VDEX.

Oh how I don't want to use XposedGmsCoreUnifiedNlP... :(

Thanks

P.S. If you remember Nanodroid-microG doesn't work on my device, so I have to manually do this.
[Magisk] guest4711:
Did you move unified-nlp (or com.google.android.gms) to /system/app (after installing it via f-droid to /data/app)?
[Magisk] DoR3M3:
That's GmsCore and I have a copy of it in /priv-app and that does nothing...
[Magisk] raptorddd:
ok used today playstore several times today and the self update have stopped since i updated from fdroid using setialpha repository..
[Magisk] NotesOfReality:
I suggest you to try to install termux with gnu bash and shell utilities and to read the full documentation, you may need Fake Store on the basis of how much well-coded are the apps you use because some can FC if Play Store isn't installed which actually is just sick.
[Magisk] lucastracq:
thank you for the answer. termux wiki is all the documentation i've found, is it the one you are saying?
[Magisk] Tomatot-:
Hey, browsing reddit I found this post: https://www.reddit.com/r/LineageOS/comments/8sh2nt/why_is_bacons_shiny_new_151_build_odexd_all_of_a/

So it looks like my issue is because LOS doesn't "like" to be deodexed. So it would have nothing to do with your module. That's good news I guess.
[Magisk] Setialpha:
The crash issues for some apps (like Termux) will be fixed with 20.2.

Dunno, but you may post the log from SysTest package, on a clean installation of your ROM (only ROM, nothing else).

Let's see whether we can make it work.
[Magisk] friedCELLS:
Unfortunately the update for services always fails and play store shows already at the latest version. If I try to update the services, it fails, then play store starts updating services again on it's own.
[Magisk] Setialpha:
20.2.20181122 Cardenas

Hi all,

version 20.2 Codename: Cardenas is now available.

What's new?

SystTest package which collects information to aid debugging and error search

improved Patcher package

you can now choose between official microG GmsCore and NanoDroid custom microG GmsCore (default)

switched to stable Amaze build, switch from Simple Gallery to Simple Gallery Pro

squashed bugs in CommonInstaller and Uninstaller

Installers now print where they store the logfiles

Full ChangeLog

## 20.2.20181122 "Cardenas"

### Notes

* (Simple) Gallery is now replaced by Simple Gallery Pro. While the app is still Open Source, code available on github and free on F-Droid, the Play Store release is now paid ([see this post by the developer](https://medium.com/@tibbi/some-simple-mobile-tools-apps-are-becoming-paid-d053268f0fb2)), thus the change. NanoDroid-wise the transistion is done in-place, but you will have to re-setup the application.

### Bug Fixes

* CommonInstaller
* fix installing APK libraries for non-multilib APKs

* Uninstaller
* fixed Uninstaller failing if no overlayed apps from System Mode exist
* fixed Uninstaller failing to remove Patcher artifacts and restore original services.jar

### General Changes

* SysTest package
* new package for providing several ROM informations
* device profile (ROM, manufacturer, device, ABI, builddate, security patch date)
* detected LD_LIBRARY_PATH
* DalvikVM binary and it's architecture
* mounted partitions, whether device is A/B
* list of installed GApps
* file list of /system/app and /system/priv-app
* log is created in /sdcard/NanoDroid-SysTest.log

* Full, microG packages
* new setup variable `nanodroid_gmscore`, selects which microG GmsCore to install
* 0 = install NanoDroid's [custom microG GmsCore](https://github.com/Nanolx/android_packages_apps_GmsCore)
* 1 = install [official microG GmsCore](https://github.com/microg/android_packages_apps_GmsCore)

* CommonInstaller
* NanoDroid installation log now contains whether install was successful or not
* Installer now prints a message where it stored the logs

* Patcher package
* drop unlp patch, not required on most ROMs and is suspected to cause issues on some ROMs
* improve DalvikVM architecture detection
* improve calling DalvikVM to prevent using patch2oat
* (which may have a different bitness (32 vs. 64 bit) as DalvikVM itself)

* Uninstaller
* now also uninstalls the BromiteWebView package

* SetupWizard
* add new `nanodroid_gmscore` variable

* build-package Script
* move to stable Amaze build

* Documentation
* more detailed information about custom APKs

### Updates

* automatic
* Bromite WebView (70.0.3538.107)
* Odyssey (1.1.16)
* Amaze (3.3.0)
* Simple Gallery Pro (6.0.0)

* manual
* microG GmsCore (0.2.6.14796-dirty-112)
* Play Store (12.6.11)

Download links

Download from Nanolx or AFH.

Bug reporting

In case of errors, please provide

/data/adb/MODID_log_INSTALLDATE

/data/adb/MODID_twrp_INSTALLDATE (TWRP Installation)

log from SysTest package

logcat (if applicable)
[Magisk] kmem:
Funny, I had to disable these same options before nanoDroid would install on crDroid. Never had this issue before with previous builds.
[Magisk] raptorddd:
new build code cardenas has option to choose setialpha playstore or microG one.. so you shouldnt have that problem anymore.
[Magisk] Torrify:
...none of the issues I raised, nearly a week ago, have been fixed with this update.

The sig spoofing patcher still results in horrible lag.

The location service is completely nonfunctional. Apps needing the Maps API and/or background location at best can't get a lock, and at worst crash out entirely.

GCM is also unpredictable and unreliable, and the system randomly reboots of its own accord

For the fourth time - can you PLEASE provide some clear instruction as to WHEN to provide the described logs, in order to accurately to diagnose and resolve these problems. They remain game-breaking.
[Magisk] Wo11ven:
Patching is failing on a new unique ROM for my device (Zenfone 2 - Borets Zenfone 4 Edition). I have attached the logs.
[Magisk] zae857:
How to swithced to microg official cause microg which ur mod keep update itself ???

---------- Post added at 05:52 AM ---------- Previous post was at 05:50 AM ----------

Which have patched , cause im using microg default , but ps keep updating:confused:???
[Magisk] Setialpha:
I already told you to post the installation logs and systest log. I also said *no* prerquisites for those logs, I honestly don't understand what's not clear by that.

For the random reboot issue, a similar issue has been reported upstream on microG github, likely related to unlp not working.

Since the lag persists, a logcat would be helpful, for at least 15 Minutes in ROM.
[Magisk] zae857:
Which version???

---------- Post added at 05:55 AM ---------- Previous post was at 05:54 AM ----------

So which is stable now???

---------- Post added at 05:56 AM ---------- Previous post was at 05:55 AM ----------

Which is stable now?
[Magisk] Setialpha:
Not Play Store, but microG.

I'll have a look, thanks.

No, it's not my mod updating itself, it's the Play Store itself that updates itself and also tries to update Play Services, though we use microG instead, thus it obviously fails.

As a microG user using the Play Store you'll never completely elimiate that issue, check this thread or the microG thread: this hiccup is a reliable vagabound.
[Magisk] zae857:
So microg official has this issue too, if yes better i will disable gplay, and use when i need it:cool:

---------- Post added at 06:04 AM ---------- Previous post was at 06:02 AM ----------

What is difference between gms core ur mod and by official?:confused:
[Magisk] Setialpha:
See

https://github.com/Nanolx/android_packages_apps_GmsCore#changes
[Magisk] Torrify:
What's not clear, as I've already stated, it whether you want me to get these logs after I install microg, ie before installing any apps, or after I install one, or all of the apps causing various problems, or after install the apps and then provoke a problem, and then in that case which app and which problem? It's not about pre-requisites, it's about timing.

And theres no way I can get a 15 minute log, the rom reboots withing 60 seconds of boot, tops... Any solution there, or just passing the buck to MicroG?

I don't buy that personally - Micrgo and UNlp is work just fine in the combined Lingeage-MicroG build. This is only occurring in Nanodroid.
[Magisk] Apex Predator:
The way you word your posts sounds like you don't feel as though you're getting your money's worth.
[Magisk] raptorddd:
use tingle to patch...

use GAPPS if it doesnt work out for you.
[Magisk] Torrify:
Explain?

---------- Post added at 08:21 AM ---------- Previous post was at 08:20 AM ----------

No, I'll likely just roll back to Nougat with the fully functional and bug-free Lineage+MicroG builds.
[Magisk] NotesOfReality:
Nope I was referring to the wiki of NanoDroid https://gitlab.com/Nanolx/NanoDroid/blob/master/README.md , it's very informative and reading it should be almost mandatory under my point of view.
[Magisk] h_maharaj:
I'm testing out NanoDroid on one of my old devices - Galaxy Note 2 running AICP 12.1 (Nougat 7.1.2). Everything works well except when querying SafetyNet. It seems like DroidGuard Helper is crashing when SafetyNet is queried resulting in SafetyNet API error in Magisk. I've tested out patching the ROM with both Tingle and NanoDroid patcher but both methods result in the same problem unfortunately.

NB. This isn't an issue for me since I don't use anything that relies on SafetyNet. Just thought to report it in case anyone else is experiencing a similar problem.
[Magisk] h_maharaj:
Apologies for double posting. For some reason XDA Labs only uploaded one of the log files.
[Magisk] lucastracq:
oh sorry, didn't understand.

yeah, i have already read that a few times even before getting started with nanodroid. totally agree with you and thanks again.
[Magisk] Setialpha:
That's already listed in the issues section.
[Magisk] Setialpha:
Nougat is something completely different. Oreo and Pie introduced new hurdles. Also comparing microG ready ROMs with ROMs that don't support it, is like comparing cherries with strawberrys.
[Magisk] Torrify:
Good to see you're at least reading my posts....

Can you now at least answer my question regarding the logs? I'm trying to help fix these problems but right now, you're being the biggest obstacle.
[Magisk] Setialpha:
Given you tested NanoDroid on a non-microG ready, deodexed post-Nougat ROM it's not "only in NanoDroid", but the combibation of all three.

Well the "just" in "just post them" actually is a timing, or more precisely the absence of it. It doesn't matter as installation logs can only be posted after installation amd the systest log collects generic information.

For the logcat, connect phone to PC while booting and collect the logcat from PC, that logcat would also contain the reason for the sudden reboot.
[Magisk] Setialpha:
Thanks, but I think actually the word "just" is the biggest obstacle right now.

Also you've answered the users' question yourself right now.
[Magisk] Torrify:
Righto, now we're on target. Thanks.

So youre saying the logs (fromd your zip file) DONT need to be collected after the actual occurrence of the bugs/crashes? Meaning I can in fact just take them right after a clean Nanodroid flash, BEFORE installing any of the apps provoking instability?

As for logcat - when you say 'connect to phone while booting' are we talking "adb -d logcat" and wait for device detection?

I'm going to have to do any of this on Monday anyway, I've waited up till 4am and now it's time for bed. Thanks
[Magisk] h_maharaj:
I've checked the issues section already and none of that applies in my case. I granted all permissions to GmsCore and Play Store and rebooted after setting up MicroG. DroidGuard Helper is installed as a user app as well.
[Magisk] agentXshadow:
Hello! Thank you for all your work on NanoDroid.

My phone has an existing installation of the upstream MicroG. What would be the process of moving over to NanoDroid from regular MicroG?
[Magisk] Setialpha:
Did you enable SafetyNet in microG settings and ensured it is set to use official server?
[Magisk] Setialpha:
In theory it should work in-place (some users reported it worked, but a TWRP backup is recommended), except you'd loose GCM registrations and microG settings, you'd likely also have to remove and re-add your Google Account.

That's because the installer can't differentiate whether the installed com.google.androud.gms is Google GmsCore or microG GmsCore, thus on new NanoDroid installation it gets rid of any pre-existing GmsCire and it's data; when updating NanoDroid this step is skipped of course,
[Magisk] Setialpha:
Yes, the installation and systest logs contain generic information about what happened during installation, respectively what ROM/Device characteristics exist on the target device. Theese information can be collected anytime (for the systest), respectively are auto generated (for the installation logs).

Yes, adb logcat, or adb -d logcat (though -d is usually not required when only one Android device is connected). It depends on the ROM. On most custom ROMs it will collect logs early during boot already, not so on stock ROMs, though.
[Magisk] Torrify:
Understood. Thanks, will do another fresh test install Monday and post logs.
[Magisk] h_maharaj:
I did. Google SafetyNet, Cloud Messaging and Device Registration are all enabled and SN is set to use the official server. SafetyNet Helper Sample app returns the following:

SafetyNet request: success

Response validation: fail

Error Msg: ApiException[14]

I tested out another ROM which has signature spoofing built in (ResurrectionRemix) on the same device and SN queries work without issue. It's only on this ROM that needs to be patched where DroidGuard Helper crashes while querying SN.
[Magisk] Setialpha:
What's the logcat during SN request?
[Magisk] h_maharaj:
I posted the logcat together with the other logs upthread but here it is again.
[Magisk] DoR3M3:
Hi Setialpha, ok I ran NanoDroid-systest-20.2.20181122 and I've attached the log.

Wiped, and clean install of OxygenOS 5.1.7.

Thanks
[Magisk] LSS4181:
Is there a way to prevent NanoDroid uninstaller from deleting configuration files?

At times I might consider uninstalling and reinstalling NanoDroid (in case the environment got messed up somehow) but this will cause issues as I might end up accidentally reinstalling it using default configuration which may not be what I wanted.