yashsingh1/xdaforums huggingface dataset:
[Magisk] SrJardel:
Will this ever support Play Games someday?

I've installed it on my kid's phone some weeks ago and everything went fine, no G, no bloatware, better battery usage, perfect.

But since he is a kid he mostly play games on his phone. At first I thought it could be a bug and said him I would look into it later. Now I realize microG has absolutely no support for Play Games. Going back to Gapps just because of it seems like a major hassle.
[Magisk] masta key:
I can't find 20.7-beta1.

I can't find 20.7-beta1. It is not in the provided link.
[Magisk] dhacke:
[MENTION=4187311]Setialpha[/MENTION]

I just test the nanodroid bromite webview from the beta link and with that zip i could install bromite webview.

So no error regarding the resizing of the magisk img anymore.

So i guess the NanoDroid 20.6 zips on the beta channel are the 20.7 version (it fits regarding the date, too). But they are named as 20.6.

Mayby you forgot to rename it?
[Magisk] Setialpha:
They are labelled 20.6.90 which technically equals to 20.7-beta1, so yes, those are the files.
[Magisk] DoR3M3:
[MENTION=4187311]Setialpha[/MENTION], Hi...

Are you familar with YouTube Vanced?

https://xdaforums.com/android/apps-games/app-youtube-vanced-edition-t3758757

Seems that you need a special version of microG to log into this version of YouTube.

Maybe you will consider the changes made in this micorG vanced version worthy to add into NanoDroid-microG for people that don't want to Root their device...

The YouTube Vanced project mentions this;

And non-root users need to check that they are not using a brand account due to MicroG bug.

What is this "Brand Account" and bug being mentioned?

Thanks

P.S. For people that don't want to Root their device. :)
[Magisk] d1n0x:
Use the magisk module and it will work
[Magisk] DoR3M3:
Yes that's good for Rooted, but if someone doesn't want to Root their device, then we have an issue... :(

Thanks
[Magisk] marcdw:
Brain cramp. Oops. Deleted. [emoji51]
[Magisk] Shobit Joura:
Unfnlp has no known location in syberia os pie tissot...tried 5 differnets location providers tried running enabling command of com.qualcomm.location( i know its already enabled ,but tried)

But still not working ......any idea how to fix?
[Magisk] bertino:
That is a separate, different microg, it can be installed alongside the normal microg :)
[Magisk] LovepreetSinghGill:
But still the location works even if shows no known location
[Magisk] Shobit Joura:
That is bcuz of gps , but unlp isnt working ....
[Magisk] Switch123456789:
Discord

I tested it on i9300 (LOS 14.1) and I get the same results with Discord. If I use ale5000's microG installer instead (http://tinyurl.com/zeuqjme), Discord is working perfectly fine with microG enabled. So yea, it is a NanoDroid issue for sure.

Edit: To be more precise, it's caused by the custom MicroG build of NanoDroid, thanks for clarifying [MENTION=4187311]Setialpha[/MENTION]. I will do some tests with NanoDroid + official MicroG build and report back.
[Magisk] Setialpha:
Nope, if anything it's a bug in my custom microG build. NanoDroid includes both official and custom microG.

The documentation goes into full details what's the difference and how to choose which microG build to use.
[Magisk] Setialpha:
A permission whitelist is missing, will be added with the next releade/beta.
[Magisk] mobilism:
I have found a xposed module can make GCM push more reliable and fast for wechat and telegram. And i want to know is Microg can do that without xposed in future？

The xposed module is open sourse:https://github.com/Tornaco/X-APM
[Magisk] DoR3M3:
It's still microG and you can't install it with another version of microG in the system, I tried just to test and it doesn't work.
[Magisk] Shadow53:
RE: spoof checker, L4M seems to limit signature spoofing permissions to privileged system apps, so it would make sense that the app claimed spoofing was not enabled. The important bit is if MicroG says it's available or not.
[Magisk] garylawwd:
No that shouldn't be the case. The vanced microG should definitely be able to be installed alongside the normal microG. Dunno why you have this issue but it shouldn't be like that
[Magisk] :
Does anyone have a problem with app registration for push messaging? It doesn't work for me for the past month or so, spoofing works fine as usual but apps just won't register no matter what, on signature spoofing checker app the only one that failed was gcm registration too. Apps don't complain for gcm missing.
[Magisk] Switch123456789:
Thank you! The documentation is a bit fragmented and overwhelming, so i decided to go with default MicroG package first and call it a day! :) Excuse my laziness.

However, today I figured it out and tried official MicroG aaaand yep, Discord is working now!
[Magisk] pinibo:
Just installed the pre-patxhed lineageos ROM on my nexus6. Same result. Spoof checker claims no support. Most of my apps work fine. Except npo radio 1 app. Anyone willing to try this app? It is a local app for the Netherlands.
[Magisk] minchutis:
I have aex pie with nanoDroid, all works well but some applications like Endomondo crashed. What I can do?? Thank you

Enviado desde mi Redmi Note 3 mediante Tapatalk
[Magisk] matttbe:
It seems you are not the first one. I also have issues and I am on Android 9 Pie with latest security updates. Could it be due to a recent change in the OS?

I don't see any error in the logs but maybe we should look there after the reinstallation of an app requiring GCM.
[Magisk] Setialpha:
It's already been mentioned: LOS for uG now (since December) only allows system applications acquire signature spoofing. Also the checker is kinda redundant on that ROM.
[Magisk] matttbe:
Thank you for your answer (and all the project!).

I had issues in January and February to have the signature spoofing working. Now it seems working because both MicroG settings and Signature Spoofing Checker say it is OK but do you mean that it is not the case? Or is it not enough to have GCM working?
[Magisk] kurtn:
GCM and signature spoofing are independent parts of microG. What's the symptom of GCM?
[Magisk] matttbe:
That was my impression too. GCM is enabled in MicroG settings like before but no more app can register. And I didn't ask to confirm these apps.

I just tried to use Push Notification Tester app (I am not sure it is testing what I want to test) but it crashes when registering for Push Notification. Here are the logs when testing that but I don't see anything interesting linked to microg: https://sebsauvage.net/paste/?a1949c6c136a7d67#GQP2+47Weasiul783C9oxepXPSBT7Xfp/UPtBpFupbY=
[Magisk] Setialpha:
That app uses FCM, not GCM AFAIK, so it's not reliable for our case. Unless I'm mistaken.
[Magisk] Oswald Boelcke:
I'm also occasionally using Push Notification Tester and just use it in order to check if I've the same issue as @matttbe.

And I can clearly state: Negative.

µG, NanoDroid and Push Notification Tester are all working perfectly as advertised (please refer to screenshots).
[Magisk] Setialpha:
You're right, I've just tested it myself.
[Magisk] :
Thanks! This fixed it for me.

For some reason DroidGuard doesn't work if installed via magisk module, it has to be installed in /system/.

Logfile (maybe can be useful):

time: 1551819906177
msg: java.lang.NullPointerException: Attempt to invoke virtual method 'android.content.res.Configuration android.content.res.Resources.getConfiguration()' on a null object reference
stacktrace: java.lang.NullPointerException: Attempt to invoke virtual method 'android.content.res.Configuration android.content.res.Resources.getConfiguration()' on a null object reference
at android.app.ActivityThread.updateLocaleListFromAppContext(ActivityThread.java:5576)
at android.app.ActivityThread.handleBindApplication(ActivityThread.java:5807)
at android.app.ActivityThread.access$1100(ActivityThread.java:202)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1658)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loop(Looper.java:193)
at android.app.ActivityThread.main(ActivityThread.java:6739)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:495)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:859)
[Magisk] matttbe:
Thank you to both of you for having tested that!

Would it mean there is an issue with my ROM? Or maybe more precisely due to the last security updates and some adaptations in microg might be needed?

I know that Google has deprecated GCM and they are going to remove it at some points. Could it be the start of this process?

EDIT: it seems they will remove it next month: https://developers.google.com/cloud-messaging/faq
[Magisk] Oswald Boelcke:
That Google is deprecating GCM in April is known for quite a few months and I believe already published in this thread.

And as stated by me: "µG, NanoDroid and Push Notification Tester are all working perfectly as advertised".

My personal conclusion: The issue rests with your device, where so ever. But I can't assess if µG requires adaptations, probably your ROM does?
[Magisk] SkilledAlpaca:
Yup, using Magisk Hide on Discord makes it work with the NanoDroid MicroG install. I was pulling my hair out over this for a day or so until I saw this message to hide Magisk from it.
[Magisk] PoochyX:
Glad I could help

PoochyXXX
[Magisk] Setialpha:
New patcher test zip with more debug info outputted.
[Magisk] inestion:
Log
[Magisk] Setialpha:
Uff, that's strange... the variable DALVIK_ARCH contains the string 32-bit, but on your device the evaluation

if [[ "${DALVIK_ARCH}" == *32-bit* ]]; then
action
elif [[ "${DALVIK_ARCH}" == *64-bit* ]]; then
action
else error
fi

fails, try the attached one and tell me if it now properly detects the architecture.
[Magisk] bhanuprasad1981:
Can i get just google sync as separate zip i dont want to install all included apps, i tried including Config file as mentioned in documentation but still all apps showed up in last final 9.3 version
[Magisk] Setialpha:
Nope, just download that two apks for that purpose, GoogleContactsSync, GoogleCalendarSync

https://github.com/Nanolx/NanoMod/tree/master/Overlay/system/app

Did you save the config file in the right directory? Also did you disable apps in the config file?
[Magisk] DJ aliasz3d:
Ok my error with the 9.2 patcher was the same saying wrong architecture, i'll try 9.4 and edit this post
[Magisk] DJ aliasz3d:
Ok this one worked :good:

Had an error at the end but i assume its no issue . Finally had a chance to setup .nanomod-setup too.

Next time i'll post a log now i've figured that out it would be more helpfull :good:

Sorry for the double post but i can't add attachments to an edited labs post.
[Magisk] bhanuprasad1981:
Yes i placed files in data directory and removed unwanted apps from config file
[Magisk] piet8stevens:
Patcher 9.4 + playstore error

Had a similar problem with dalvikvm error in patcher 9.3. 9.4 worked. With magisk 12. The error message at the end says "Error creating fstab" after thanking for using nanomod patcher.

I try to run playstore (version 7.9.80-Q-all [0][PR] 159305549) but receive an error "Error retrieving information from server [RH-01]". Any ideas? I have done a full wipe of the phone, installed a new rom, then light patch, magisk 12, nanomod. On my previous rom, everything worked. Both roms are 7.1.
[Magisk] DJ aliasz3d:
When I had that PS error I had to wipe PS app cache and data and then it worked, if I remember it was a 927 can't connect to server message followed by the code you quoted :good:
[Magisk] Setialpha:
I made more changes to the patcher, see the ChangeLog in the git repo. The fstab issue seems to only occur when installing to magisk, but not to ROM. I'll release a new beta, once it's fixed.
[Magisk] piet8stevens:
Thank you. I did that following your recommendation but the error is still there.

EDIT: one more issue I have: in Magisk manager, it says it cannot check SafetyNet, no internet? But I do have internet.
[Magisk] Setialpha:
See #Issues in the docs, how to solve that. tl;dr DroidGuard Helper needs to be a user app in some cases 'cause of a bug in Magisk. The error message is misleading.
[Magisk] piet8stevens:
Thank you for your reply and I must apologize: re. safety net, I had this problem before and the solution is in post #269 in this thread - I had not enabled Safetynet in microg.

I have now installed DroidGuard and PlayStore as user app (directly from priv-app as per your indications), but PlayStore still does not work - same error as before.

EDIT:

Found the solution here: https://shadow53.com/no-gapps/faq/playstore-not-loading/ - need to enable device registration, messaging and clean out data/cache.
[Magisk] Setialpha:
Of course. In the NanoMod docs you'll find detailed setup instructions, too.
[Magisk] piet8stevens:
Absolutely, but why do something the easy way when you can go through umpteen detours. Reading what is in front of my nose is difficult for me. ;)
[Magisk] 1plus:
I just tried Nanomod on the only android device of mine which does not have native signature spoof. Normal patcher fails with an error (cannot see dalvik), but 9.4 patcher apparently works almost fine. Although it does generate fstab error at the end. When I load the rom the UnifiedNLP works as it should (which is an obvious improvement compared to normal usage as the rom is gapps-free, plain LineageOS night build).

So what kind of error or functionality loss is expected due to fstab error?

P.S. I also use the most recent beta of Magisk13.
[Magisk] Setialpha:
The fstab error effects TWRP, not NanoMod. In worst case you need to restart TWRP before you can flash another zip, that's it.
[Magisk] Setialpha:
10.0-beta1

Version 10.0 beta1 is now available. Highlights since 9.3:

new installation mechanism

uninstaller can now also remove system mode NanoMod

if version 10.0 is installed

fixes to nanomod-overlay.genconfig and nanomod-overlay.permission

improved on-device framework-patcher

Full ChangeLog since 9.3

## 10.0 in-dev
* Bug Fixes
* Full, microG package
* fixup `nanomod-overlay.genconfig` syntax error
* fixup `nanomod-overlay.permission` not properly working
* install GoogleBackupTransport into `/system/priv-app`, not `/system/app`
* on-device framework-patcher
* stop process if `/system/.nanomod-patcher` file exists
* fixup missing function in on-device framework-patcher
* fixup architecture detection in on-device framework-patcher
* on-pc framework-patcher
* stop process if `/system/.nanomod-patcher` file exists
* force-debloat.sh remove Launchers from list of apps to remove
* PixelLauncher
* NexusLauncher
* Trebuchet
* zipalign microG Gms Core
* General Changes
* Full, microG, F-Droid package
* migrate to shiny new installation mechanism
* on-device framework-patcher
* code improvements
* better error messages when dalvikvm fails
* when installing patched `services.jar` to ROM back it up to `/sdcard`
* print somewhat more useful information
* on-pc framework-patcher
* when installing patched `services.jar` to ROM back it up to `/sdcard`
* uninstaller
* code improvements
* remove `/system/.nanomod-patcher` regardless wether Magisk is installed
* support uninstalling NanoMod when installed in system mode
* Updates
* Simple Gallery (2.11.1)
* XDA Labs (1.1.2.3)
* MPV (2017-06-25)
* Substratum (803)

Download from AFH.

In case of errors, please provide

your device's architecture

your device' Android version (not ROM version)

whether installed as Magisk Module or in System Mode

used Magisk version

recovery.log or logcat or both (whatever is applicable)
[Magisk] piet8stevens:
Titanium Backup no longer visible in launcher app drawer and unusable.

Have been going through many reinstalls to try and get my new ROM to work (had issues with external SDcard which I had adopted on my previous rom and somehow that stopped working). These are the steps I take: (after wiping dalvik, cache, data, system)

a. Flash ROM (AospExtended, Android 7.1) - this rom for Axon7 includes Magisk 12 install.

b. Magisk uninstall - not sure this is necessary but in step e below, Light Patch installs Magisk v13 so to be on the safe side, I uninstall 12.

c. Flash Titanium Backup.

d. Boot into Android. Can see Titanium Backup in launcher. When I launch, it complains of no root, as it should.

e. Flash Light Patch (to fix the no sound problem with calls that many roms have). This installs Magisk v13.

f. Flash nanomod 9.3.

g. Reboot into Android. Titanium Backup is no longer visible in the app launcher. It is visible in settings\apps and when I launch from there, it just closes.

h. Flash nanomod uninstaller 9.3

i. Reboot into Android. Titanium Backup is again visible in the app launcher. When I launch it from the app launcher, it just closes.

So, I am stuck as without TiBu, I cannot restore my apps. Any ideas? I have done this multiple times with slight variations in when I install TiBu but the final result after Nanomod in Magisk is that I lose TiBu.

Logcat has this error related to TiBu:

06-28 15:16:10.533 5376 5376 E ResourcesManager: failed to add asset path /data/app/com.keramidas.TitaniumBackup.apk
06-28 15:16:10.534 5376 5376 E AndroidRuntime: FATAL EXCEPTION: main
06-28 15:16:10.534 5376 5376 E AndroidRuntime: Process: com.keramidas.TitaniumBackup, PID: 5376
06-28 15:16:10.534 5376 5376 E AndroidRuntime: java.lang.NullPointerException: Attempt to invoke virtual method 'android.content.res.Configuration android.content.res.Resources.getConfiguration()' on a null object reference
06-28 15:16:10.534 5376 5376 E AndroidRuntime:	at android.app.ActivityThread.updateLocaleListFromAppContext(ActivityThread.java:5165)
[Magisk] SkilledAlpaca:
Is there any reason this works though? Discord worked fine without anything Google Related on the phone. No Push Notifications obviously, but no issues. Installing this variant of MicroG it stops working until you hide root from it? I'm really curious why this would be the case.
[Magisk] marcdw:
You could satisfy some of that curiosity by getting/capturing logs and seeing why. Maybe attach or link it here so logs can be examined.

LG G3 D851, Clean ROM v3.2, NanoDroid (microG), MultiROM, XDA Legacy
[Magisk] user822:
I have no luck with phh-treble

Update: figured it out

Instead of running "vdexExtractor" from the tutorial I needed to run /tool/deodex/run.sh to get the correct ".dex" and not ".cdex" file
[Magisk] temporarium:
If you're going to use Google, stay with gapps. What's your goal/reason for going with micgroG/NanoDroid?
[Magisk] PoochyX:
Probably the lower ram usage and battery savings

PoochyXXX
[Magisk] djuka007:
This is exactly right. S4 is an old phone, trying to extend its life a little bit longer.

Now, when we got that straight maybe we can get back to solving the problem ;)
[Magisk] d1n0x:
Have to agree with [MENTION=4645704]temporarium[/MENTION] here. There is no point using MicroG and still relying on Google services.

Did you get the permission of every single contact to have their details uploaded to some company's servers?

Maybe some people don't want to have anything to do with Google?

You not only jeopardize your own privacy, but that of others as well. Think about it.
[Magisk] marcdw:
Y'know what, all djuka said is that he's using the sync adapters and having issues. All the yick yack about goals/reasons of microG/NanoDroid is irrelevant. People have different reasons for using microG, not always about privacy.

The Google sync adapters are included as an option in NanoDroid so speechifying when someone uses them is silly. If you (collectively) feel they are against the goals/reasons for microG then you need to ask Setialpha to remove them and offer something else (like DAVx). Let's see how that goes. [emoji848]

ZTE Axon 7 A2017U, AospExtended v4.6 ROM, Radioactive v2.4 Kernel, microG (NoGapps), Multiboot, XDA Legacy
[Magisk] temporarium:
You are correct. One can hammer in a nail with a wrench.
[Magisk] Setialpha:
This. They are included, but not installed by default (I personally use old school vcf, no sync), because (for whatever reason) people demanded them.

At the end of the day it depends on what you want. I see a point in advising people, but I'd like to refrain from arguments.

If someone wants something else included as an alternative, just tell me, I'll see, what can be done.
[Magisk] user822:
I am on Pie (phh-treble) and getting this when tapping "last known location"

UnifiedNLP is not registered in the system

Any ideas :/ ?

Edit: After rebooting a few times it does seem to work, but still the same error occurs and it says unregistered in the self check
[Magisk] djuka007:
I really appreciate the enthusiasm present in this ideological discussion, but I'm still not any closer to actually solving my problem. :)
[Magisk] Oswald Boelcke:
Just a quick question for my better understanding: Why did you choose to use the sync adapters from OpenGapps and didn't use the ones that come with the NanoDroid-microG-submodule? Have you tried those before?

Remark: Personally, I don't use anything by Google.
[Magisk] MEKCHR:
Hello, I keep getting the error "Failed to install libs for Phonesky" when I try to install the full package although installing microg package separately causes no error. Is anyone facing this problem ?
[Magisk] djuka007:
I first tried using those provided in the microG package but system doesn't recognize them.

After I've copied them to /system/app (and set the permissions) they are not shown in the Settings - Apps - Show system
[Magisk] Lanchon:
[MENTION=4187311]Setialpha[/MENTION]

hi nanolx,

i published a couple of updates to the haystack signature spoofing patcher, including bugfixes, core and UI support for all androids from 4.0 to 9.0, and rewritten unified patches.

consider updating your signature spoofing patcher release to the latest version.

see: https://github.com/Lanchon/haystack/releases

---------

on patching performance:

as always, "dexpatcher --output out source.apk patch1.dex patch2.dex patch3.dex" produces exactly the same result but is roughly 3 times faster than applying the 3 patches serially in different tool runs. memory usage is mostly not affected. this invocation method should always be preferred.

when applying patches to frameworks of android versions that natively support multidex (ie: android 5 and beyond), dexpatcher's multidex mode MUST be enabled for robust operation. this is typically done with the --multi-dex option. (see: https://github.com/DexPatcher/dexpa...15e993d6d8af7/test/shell-test-ref.txt#L16-L19)

but there is an alternative: the --multi-dex-threaded option partitions the workload in small bundles and deliver them to simultaneous threads writing the different parts of a multidex output concurrently. the number of threads used by default match the number of processor cores available up to a maximum of 4 (but can be configured). my testing showed a 3.95 speed increase on a typical quad-core snapdragon 8xx processor using --multi-dex-threaded. (see: https://github.com/DexPatcher/dexpatcher-tool/releases/tag/v1.2.0-beta2)

these strategies combined can provide an 8x through 12x patching speed increase.

but keep in mind that enabling --multi-dex-threaded will result in:

- framework files with more classes<N>.dex parts than the bare minimum needed to hold their executable content.

- framework files that are different every time you patch the same source files because of the stochastic nature of work distribution across threads (and thus, across mulltidex parts).

however, ART does not care about which part of a multidex executable holds each type within the executable; it just loads all the types as needed. so these caveats do not result in any real functional disadvantage.

thanks!