yashsingh1/xdaforums huggingface dataset:
[Magisk] Torrify:
I appreciate the developers efforts on this. I had an earlier version from a year or so ago working pretty well on a Galaxy Note 3. But coming back to it now with newer phone (S7 Edge) its been disappointing to find this mod is now riddled with bugs. As it is, the phone barely runs with it, let alone is it a functional replacement for GApps. I've lost a solid week of my life trying to troubleshoot this, and got nowhere.

There's something seriously bugged with the signature spoofing patcher. On any given patch attempt, I'm getting anything from 1-5 "E:recv error on uevent" errors, with very unpredictable results as to whether it successfully enables spoofing. Even when it does say sig spoofing is enabled, often I still wind up with all sorts of bugs and crashes with anything trying to use the microg framework. Anything using the maps API is particular problematic, with various problems ranging from failure to load map layers to crash loops before the app even opens.

What even more frustrating is that if I install these apps first, and THEN run the patcher and flash microg, then they'll work ... sometimes. Wipe and reinstall the ROM and apps and try the process all over again and often they go back to crashing. Seems to be totally random, but proves the problem isn't the apps (that, and they work fine with Gapps) . And of course, even if the stars do line up and I get them working by installing the apps first, if I then update or reinstall them after flashing the patcher, they crash again.

The patcher also seems to be responsible for major performance problems. Even on a totally fresh ROM flash (plain ol Oreo Lineage after flashing the patcher zip (assuming it works) I'm getting awful lag (up to 1 second between touch and response) and appalling battery drain. No, it's not the ROM - without the patcher, or with Gapps, it runs fine.

Something also seems to be wrong with the MicroG package too. Constant MicroG crash/close messages, as well as any apps using their services, and apparently no functioning fused location/Nlp service. Totally random. Yes, I've set it up properly(at least, int eh same fashion that worked before).

The latest version of the uninstaller is bugged as well, and fails out saying it can't find the backup apps folder (when I never even asked it to delete or install any of the bundled bloatware anyway). Going back to v19 or 18, it does seem to work, except then any attempt to re-flash and of the zips also spits a variety of errors.

I've tested multiple versions of all the zips going back in the achrives and the results are more or less the same. Tried 4 different ROMs too. If I flash the bundled Lineage w. MicroG (nougat), or indeed anything else without NanoDriod, things are more or less fine. The problem is almost certainly nanodroid. I'd provide logs, but frankly the phone barely runs, the problems are entirely random an intermittent, and I have no idea where to start.

Oh but at least I get get Zelda sounds and Nintendo fonts...
[Magisk] forjustin:
Sorry to hear your problems. The latest nanodroid (full fackage) works perfect for me on the 2 devices I've tried it on. mido LOS 15. 1, and hermes viperOS.

I use xposed fakeGapps to patch.

nanodroid Uninstall fails.
[Magisk] Luigi7744:
I'm having text message delays and sometimes my phone fails to receive calls and doesn't register in my missed calls. All I get is a voicemail.

are my issues related to this module?
[Magisk] guest4711:
No, it should not. mikroG and related apps do not change anything regarding phone and message app. It's probably a problem of your phone service provider or a weak signal.

But test it yourself. Disable the module in MagiskManager, reboot and see what has changed...
[Magisk] grusta:
I also experienced a lot of performance problems with the patcher. Oneplus One, on LOS-based roms.

The solution was : using xposed to get signature spoofing. All the problems were gone. Did you try without the patcher?

Mind your language please, you're not very friendly with the dev. Even if I understand your frustration.
[Magisk] Torrify:
Yes, I have actually already tried the Xposed spoofing module to verify the problem is with the NanoMod Patcher. I omitted it as the post was too long already, but yes - no lag used Xposed spoofing, but I dont want to use Xposed long term however if I can avoid it

I'm not sure what you mean by 'mind my language'? I don't see any profanity or rudeness in what I wrote. Can you specify what parts exactly are not sufficiently 'freindly' or noncompliant with forum rules?
[Magisk] Klizi:
Can I flash the fdroid stable zip over beta zip?

Havoc OS has the signature spoof support but anyone tried the latest build with last update?
[Magisk] LovepreetSinghGill:
Yes
[Magisk] Setialpha:
NanoDroid SysTest

Hi all,

as promised, here's the SysTest package which will collect system information in order to help in improving ROM compatibility. Simply flash it through TWRP and it will create a file called /sdcard/NanoDroid-SysTest.log, post that file here.

Of course anybody is free to provide logs, but preferably those who encounter issues should do so.

What is collected?

device profile (ROM, manufacturer, device, ABI, builddate, security patch date)

pre-set and 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

nothing else

Thanks for your help!
[Magisk] Torrify:
Thanks, but you're not making it clear how to specifically employ this new zip, or how to get these 'logs' you suggest, or when to collect them. I would have provided them in the first instance, but I have no idea what you require or how to find it.

For errors that are occuring in TWRP, before the rom is even booted, how do we find these logs?

For ongoing lag once the ROM boots, which logs do you want then, and taken at what point? Immediately after boot? After 5 min?

For apps with intermittent maps crashes that fail after one trying one time, but then randomly work on another, do you want logs for the installations when they work, or when they fail, or both? And where would these log files be?

Or does this one zip get all of the above at once? If so, again - when is the appropriate time to do the flash?

Happy to do what I can do help diagnose/solve the problem, but I need to know whats required in order to do it.
[Magisk] Setialpha:
The new zip is simply flashed and the created log posted, no other prerequistes.

About the other issues I'll come back later today, currently busy. But there's one thing I suspect could at least be part of the problem.
[Magisk] Torrify:
Thankyou very much, greatly appreciated. Not need to rush, ill be away for a day or two.
[Magisk] D4ND310:
I can confirm these issues. They happen to me when using Nanodroid alongside Android 8.1 ROMS. The phone rings on incoming calls but no phone app appears on the gui to accept the call. The call also isn't recorded in the history logs.

Text messages also have a habit of not arriving, until the device is restarted.

This has happened repeatedly when I've used Nanodroid with Fakegapps Xposed module.

For this installation, on Danwood's most recent LOS-15.1 release, I've used Nanodroid Patcher and the issue is not occurring, for now.

I have a very interesting logcat from the last time it happened, I will attach the boot sequence section shortly...

*Edit: No I won't. This pathetic forum UI is making it impossible to attach anything. Again.
[Magisk] Setialpha:
So it might aswell be Xposed related, I never had such an issue on no ROM tested, plus NanoDroid does nothing that could possibly interfere with UI or calls. Atleast not in any intended matter. Does pastebin, github gists or whatever work for you, so you can post the logs?
[Magisk] D4ND310:
When this happens, no contacts are (obviously)viewable, Contacts app continually tries to refresh but doesn't display, it's settings do not open, either.

Already sent/received messages appear in the texting app but only as numbers, whether they are from a contact or not. New messages do not arrive.

The log here shows pretty much everything failing at boot, including User details, Contacts, Telephony, connections etc.

A restart sometimes resets the errors but not always. And, if it does reset it, the problem invariably arises again a while after the system has been running. As if all the aforementioned items are simply being killed.

As I mentioned, it hasn't happened since I've used your ND Patcher. It's been a few days now.
[Magisk] Oswald Boelcke:
Personally, I'd refrain from any action on a report that is based on on Oreo ROM with Xposed installed. Xposed for Oreo is clearly beta status but development seems to have halted for nearly half a year for whatever reason. Knowing the deep (and obviously by Xposed users intended) intrusion of Xposed you might dig into something that... I leave the rest open for the imagination of everybody who's concerned.
[Magisk] Setialpha:
There's a lot of errors from Google Connectivity Services and the MinMinGuard Xposed module.

I assume MinMinGuard does not properly work or is over-aggressively configured. Also Xposed for Oreo, as Oswald Boelcke said, never left Beta and development halted.

From your logs and your own experience using the Patcher, I'm 99 % sure Xposed or more precisely any module in use is at fault.

Just scratching on the surface to know what's causing the issue. But there's a reason the NanoDroid documentation doesn't mention Xposed. Development is stalled and thus many issues to be expected, I dropped Xposed after MM, as it was no longer reliably working or up to date for daily use.
[Magisk] D4ND310:
Thank you. Do you mind editing your post to remove the Pastebin link now that you have it, [MENTION=4187311]Setialpha[/MENTION]?
[Magisk] guest4711:
Messaging and phone app are usually part of g-apps, too. When no g-apos are installed no apps are selected as default app for phoning and messaging, probably. So try to select the installed phone app as defaukt app for phoning and the message app for messaging.

Please report back.
[Magisk] D4ND310:
Thanks, I've tried this with the default apps already as I've saw many almost similar posts relating to no phone app UI appearing on calls. However, my default app settings have always been set and appeared in Settings. I think it is, indeed Xposed for Oreo related.
[Magisk] Oswald Boelcke:
From my personal point of view, I can confirm that Xposed (and at least all of my very few modules) work as advertised on my Nougat ROMs (two different devices, all Resurrection Remix, all with µG powered by your superb tool - tanks in deed for this!).
[Magisk] D4ND310:
I can confirm this, too.
[Magisk] raptorddd:
been a while since i used nanodroid NanoDroid-microG-20.1.20181112 . am using miui 10 8.1 oreo and am getting constant update to either Gservices or playstore. how to stop this.??? see pics. thanks in advance.
[Magisk] Setialpha:
By either

a) not using Play Store

b) updating my unofficial microG build using my F-Droid Repository (see top of first post for link)
[Magisk] temporarium:
I'm using system-less (via Magisk) Xposed on Oreo with zero issues with NanoDroid. Maybe a particular module issue only...
[Magisk] Setialpha:
I'll post for the rest tomorrow, but I was talking about the webpage https://nanolx.org/fdroid/repo (open in browser, not with F-Droid), which contains a links to all used sources for the repo.

Which is https://github.com/Nanolx/android_packages_apps_GmsCore for microG, here everything is mentioned.

I'll add the links to NanoDroid docs, directly, aswell, likely more accesible.
[Magisk] DoR3M3:
I've run Xposed on a few different devices without issue, and still running it. Of course developement was/is Beta. Windows is a BIG BUG if you ask me, look how so called stable that is, and all the problems! LOL Bugs are everywhere....

Running microG manually, I can use the Official Play Store with no problems.... hmm

This makes me wonder, what advantage then would I have with the patched version, other then passing SafetyNet, but then I need to use Xposed, so that tosses that out.

For the less technical/geeky users, it would be great to get a simple breakdown too written up on the advantages of this patched version?

Thanks
[Magisk] Setialpha:
It is stated directly in the introduction, that the modification is that it allows for in-app-puchases with microG, which otherwise won't be possible on most ROMs. While some Stock ROMs don't need that, all AOSP/Lineage based ROMs do.

For SafetyNet you need the custom DroidGuard Helper, which fixes SafetyNet attestation not working on arches other than 32bit arm. Otherwuse it'll fail regardless if the result, as it's the attestation process itself that fails on latest upstream release.
[Magisk] DoR3M3:
Sorry for being blind, what Introduction, where?

I've looked both places; (Don't see any mention of app purchases for AOSP/Lineage based ROMs)

https://github.com/Nanolx/android_packages_apps_GmsCore

https://nanolx.org/fdroid/repo/ - Says; microG (in-)app-purchase support Patch - No mention AOSP/Lineage based...

For SafetyNet with Xposed, I don't see any solutions around this, I've even tried unloading modules in Xposed and Magisk and disabling Xposed, SafetyNet doesn't pass, unless all this can be done with this DroidGuard and Xposed?

Thanks
[Magisk] Setialpha:
No, Xposed never passes, but without Xposed and not on arm32 the modified DroidGuard Helper is required.

The introduction of NanoDroid, third paragraph:

"In order for full microG experience NanoDroid contains a modified Play Store which allows (in-)app-purchases with microG, which would normally not be possible."

also in the Summary

"modified Play Store to allow (in-)app-purchases with microG"

see https://gitlab.com/Nanolx/NanoDroid

There's no mention about which ROMs actually require it, because I don't wanna mention a list, but it is required for all custom ROMs I ever came accross, also many others confirmed making purchases won't work with official Play Store on custom ROMs.

Note: license checks always work, but purchases don't.
[Magisk] DoR3M3:
Ok on the ROMs!

One last question, do you know if Aurora Store or Yalp Store can be safely used for Paid Apps logged in with the real Google account, and not have Google ban the account? I've read online about Google banning account like this, not sure if it was just talk, or if it's actually happened.

Also, some apps I think you need to have the Play Store installed for License Checks, so that poses another issue, but I wouldn't mind testing it out again to see if you could get away with all License Checks without the Play Store.

I wonder too, in regards to privacy/security, how safe using a real Google Account on Aurora Store or Yalp Store would be?

Hmm

P.S. The Aurora Store OP;

https://xdaforums.com/android/apps-games/galaxy-playstore-alternative-t3739733

Disclaimer :

Using Aurora Store with your own Google account may cause your account

to be blacklisted, use at your own risk.
[Magisk] marcdw:
One of my ROMs is without Play Store. Aurora and/or Yalp uses Google account. Don't worry about the possibility of Google catching and banning. The disclaimer is there but the actuality is rare.

Using paid/pro versions has been fine so I'm not without my fave core apps. As you guessed, items that do license checking will fail. A real downer if you're a substratum themes fan.

LG G3 D851, LiquidRemix v9.1.3 Oreo ROM, microG (NoGapps), MultiROM, XDA Legacy
[Magisk] DoR3M3:
I know Aurora and Yalp can use the real Google account, the biggest problem as you mentioned is the license checking, but I wonder if that's true for all apps... hmm
[Magisk] Tomatot-:
Hi, I'm also having huge performance issues with Patcher. I've done A/B testing and I'm sur 100% the Nanodroit patcher is the problem. Thank you anyway for your solution and it does work for signature spoofing however I really don't get why it affects performance so much. Do you have any idea how it could be fixed? Let me know if you need some kind of information like logs or anything.
[Magisk] mdl054:
On a OP6? Are you trying this on OxygenOS? Is your rom fully Deodexed or just services.jar
[Magisk] Setialpha:
New SysTest + Patcher test release

Hi all,

1] NanoDroid-SysTest-20181119.zip

a new release of the SysTest is now available, with minor changes and much nicer formatted logfile. If you encounter issues you may flash this and post the generated log (/sdcard/NanoDroid-SysTest.log).

2] NanoDroid-Patcher-20.2~test1.zip

Also a new test release for the Patcher is now available. Anyone having issues actually executing the Patcher in first place or having other issues with the patched services.jar, are free to test this release. Ensure you start with a clean services.jar:

Flash the attached, fixed, Uninstaller (will uninstall everything), OR manually (only restoring origial services.jar, leaving everything else intact):

first step:

System Mode: copy services.jar backup from /sdcard/nanodroid_backups/services.jar to /system/framework/ (while in TWRP)

Magisk Mode: remove services.jar from /sbin/.core/img/NanoDroid*/system/etc/framework (while in ROM)

second step:

remove the file /data/adb/NanoDroid_Patched (either from TWRP or while in ROM)

Then flash the Patcher zip as usual and report your results.

3] NanoDroid-uninstaller-20.2~test1.zip

A fixed Uninstaller pre-release is attached, aswell.
[Magisk] DoR3M3:
I've been doing the VDEX method on a few devices, and never had issues with it. I also tried the so called full Deodex with SuperR Kitchen, and I found that to have lag on a VDEX device.

Maybe the ODEX method, something happening there with baksmali.jar and smali.jar. Using vdexExtractor for VDEX method has been great, not even sure how that can introduce lag... hmm
[Magisk] Tomatot-:
Oh sorry I didn't mention it but I was with LOS 16. I'm actually not sure if it's deodexed but usually LOS is.

Also, if it can help, I've noticed the device is very snappy when I boot, for like 10 seconds. It's as fast as without Droit Patcher. But then, it gets slower and slower, like if there was a background task which was taking more and more ressources to a certain extend (after maybe 30-40 seconds it stabilizes).
[Magisk] Oswald Boelcke:
I'm not using LOS 15 or above but I think I've read that the official LOS is coming odexed starting with Oreo.

And this TOAD - The Open-Source Android Deodexer by Ticklefish might be an alternative to deodex a ROM.
[Magisk] Tomatot-:
Thank you for your helpful answer and for the link. Do you think that would improve my experience to deodex LOS? To what extend?

A little off-topic but I'm a little disappointed with LOS decisions when I look at it. No signature spoofing, no deodexing, etc. They're taking weird directions for supposedly "safety" reasons...
[Magisk] kostas gp:
Only this and 18.3.1.20180921 patcher worked on my redmi note 5 pro. All the others didn't. The phone just turned off from recovery.
[Magisk] Oswald Boelcke:
Attached the log created by NanoDroid-SysTest-20181119.zip. I don't have or encounter any issues or problems i.e. only provided for completeness as suggested in the first quoted post.

I'm unable to answer those questions; I could only do for myself. From my perspective this includes the question if I want to use Oreo or Pie or whatever is coming afterwards at all. There are quite a few (certainly arguable) perspectives involved but my answers let me stay with Nougat. I'd personally not afraid to deodex a ROM or simply a specific file myself, and I'm convinced I'd learn a lot. Tools are gratefully available for that mission, and I constantly observe and really appreciate all efforts Setialpha is undertaking that those people who want to use NanoDroid µG achieve the required signature spoofing independent of the ROM they use.
[Magisk] evilvoice:
Setialpha, I've tried installing the webview zip, but for some reason it's not registering. I used the webview test app that the bromite site suggests and it shows none, but when I replace it with Google's webview, the test app correctly shows the info. Any ideas?

I'm using TouchWiz LP 5.0. Thanks
[Magisk] lucastracq:
i've flashed the nanodroid stable package (full version) on lineage 16.0 but it fails when installing the mpv codecs. after that i flashed the systest package and it failed as well (don't know if it's normal since it didn't complete the installation). how can i fix this?

EDIT: forgot to mention i'm installing nanodroid in system mode, because i don't have magisk at all. flashing procedure was: rom - patcher - nanodroid - systest.

also everything else is working, like microg, fdroid and all the rest. the applications installed before mpv are working while the others have benn skipped and stock apps weren't debloated.

please let me know if i can provide something useful for troubleshooting.
[Magisk] mdl054:
I believe if you are encountering lag with Oxygen, it's because of a leftover Google package. I can't remember which one, it's been a while, I recommend you go though and verify all the Google packages are gone. Worth a shot anyways.
[Magisk] Setialpha:
Your issue is listed in the issues list, it's supposedly the last one, see third post for link.

Please provide the installation logs from /data/adb/ they are named MODID_twrp_INSTALLDATE and MODID_log_INSTALLDATE. Where MODID is the name of the Package you flashed (NanoDroid, NanoDroid_microG, NanoDroid_FDroid or NanoDroid_BromiteWebView).

If you ran the SysTest, provide it's logfile, too,
[Magisk] Setialpha:
The next release will introduce a new setup variable: nanodroid_gmscore. 0 = install NanoDroids custom microG GmsCore (like now), 1 = install official microG GmsCore (new).
[Magisk] lucastracq:
well, when i first installed everything it didn't work and now i can't find anything related in /data/adb, but strangely now i tried to run it again and it worked, the log is attached with the other two (i added a .log extension because xda refused to upload them)

thanks a lot for your time.
[Magisk] Nex23:
Hello,

i am very confused.

I have:

- Costum ROM Resourrection Remix OS from OpenKirin Oreo 8.1

- Modified stock-recovery which adds Magisk / root (so no twrp)

- Gapps installed

- I don't have signature spoofing

So is this correct:

1) I install the nanoDroid-patcher.zip via magisk modules --> this allowes signature spoofing / deodex

2) I install nanoDroid-microG.zip via magisk modules --> deletes all Gapps, installs microG

(I never used Magisk to install something, can it install the .zips ?)

(I don't need setupwizard or fdroid or anything else)

Will this work ?

edit:

Well, well it says

but then
[Magisk] Setialpha:
--deleted--
[Magisk] Oceanik:
Setialpha, first of all, thank you for great promising mod!

Have some problems with systemless xposed compatibility... Wrote about it on github in the issues section. Do you need any more logs or addition info?
[Magisk] totalcmdext:
I have the similar problem!

After the installation of 9.2 MicroG i am loosing the Systemless Xposed.
[Magisk] lucastracq:
both 1777d9f and 1777d9f_v2?
[Magisk] Setialpha:
If anything it's related to the patcher, need full logcat.
[Magisk] Setialpha:
Both. NanoMod itself is fine, I've found out after testing, but another (private) module does not work in parallel.
[Magisk] Oceanik:
It's only NanoMod, patcher isn't related... Have tested several times and ways.
[Magisk] Setialpha:
That doesn't make sense. NanoMod does nothing else than mapping files to /system. Nothing that would interfere with Xposed at all.

Maybe it's a bug in Magisk, that's triggered by NanoMod?

Logcat and Xposed log should sched some light on this.