yashsingh1/xdaforums huggingface dataset:
[Magisk] raptorddd:
inwaw about to ask samething. latest and it keeps updating. check in fdroid and all its uptodate. why is this happening.?

i remember staying on this build cause i had ps update constantly..

NanoDroid-microG-18.0.1.20180907.zip have not used this in a while but it was not present in that build..

setialpha
[Magisk] Setialpha:
Uploaded new Play Store and microG builds.
[Magisk] NotesOfReality:
Excuse me I've installed the stable build of NanoDroid 20.3.20181208 on bacon(armv7-a Snap 801 device) Candy Rom based on Android 8.1 Oreo with November Security Patch and I've all the green positive flags in the "Self-Check" menu of the "Micro-G Settings" app, unfortunately I've no sync options in the sync menu of my google account in the "Settings" app. I've enabled the "System Mode Installation" and "Google Sync" (or something like that) flags in the "setupwizard" AROMA zip. "GoogleContactsSync" and "GoogleCalendarSync" folders are correctly placed in /system/app and "GoogleBackupTransport" is correctly placed in /system/priv-app and their permissions(folders and apk files) are correct, moreover I've tried to clear their data and reboot but that didn't fix a thing. Could anybody please help me or tell me what am I missing? I've searched in the README.md for "sync" and "contact" keywords without finding anything helpful.
[Magisk] TiTiB:
Tried search but didn't find this mentioned.

Getting "ERROR: 1" when trying to flash from TWRP [3.2.2-1 Unofficial]. Is it caused by SELinux Enforcing in my ROM [LOS 15.1 Unofficial]?

TWRP Log extract is:

Installing zip file '/sdcard/Download/NanoDroid-20.3.20181208.zip'

Checking for Digest file...

Skipping Digest check: no Digest file found

I:Update binary zip

Verifying package compatibility...

Package doesn't contain compatibility.zip entry

I:Zip does not contain SELinux file_contexts file in its root.

I:Legacy property environment not used in updater.

/tmp/updater[11]: unzip: not found

!! failed to load Common Installer

Updater process ended with ERROR: 1

I:Install took 0 second(s).

Error installing zip file '/sdcard/Download/NanoDroid-20.3.20181208.zip'

Huawei Mediapad M5 [8.4]

SuperSU Rooted w/xposed

SHT-W09 (C567)

LOS 15.1 [unofficial]

Any help appreciated

>>>>>>>>>> EDIT: Able to flash in TWRP after Mount->System <<<<<<<<<<<<

Still not able to use G**gl-dependant apps though.

Getting "java.lang.SecurityException: Not allowed to bind to service Intent { act=com.google.android.c2dm.intent.REGISTER pkg=com.google.android.gms }" error

>>>>>>>>>> EDIT 2: Okay, works fine. Had to un/reinstall problem apps. <<<<<<<<<<<<
[Magisk] Kelvino9:
In curious if the microG Builds are signed with different signatures each time. I'm on build dirty-113 now and would like to update to dirty-115, but F-Droid refuses to update with a potential signature mismatch notification.

I'm having this issue for the past few versions. None would update over its predecessor. As of now I always have to push the APKs manually to /system/priv-app to update to the latest Snapshot build provided by the Nanolx F-Droid Repo. Any ideas?
[Magisk] elraffa:
hi, I have latest 20.3 nanodroid version, latest magisk 18.1r4 version, ROM viperOs nougat 7.1.2, in nanodroid settings/Google safetynet enabled/official server... but in magisk manager I get safetynet API error and root checker app I get"can't access Google play services".. how can I pass safetynet?

Enviado desde mi ALE-L23 mediante Tapatalk
[Magisk] epsilon_0:
I'm having problems installing NanoDroid on a clean OmniRom installation.

I've installed OmniRom, then installed TWRP, then Magisk, and nothing else.

When I boot into recovery and install NanoDroid (full version) I get the error:

failed to install /dev/tmp/install/system/app/Amaze/Amaze.apk to
/dev/tmp/magisk_img/NanoDroid/system/app/Amaze
!!
- Unmounting Patitions ....

Can you please help me? I really want to be able to use this!

It looks like a really awesome module!

PS: When I didn't have magisk, it was able to install it to system and worked OK but needed more permissions which I couldn't without magisk.
[Magisk] jenslody:
I don't use Nanodroid as flashable zip, just the Nanodroid F-Droid repo and never had any issues updating the apps.
[Magisk] Setialpha:
Read the Issues section. Issue already listed and happens with Magisk 18.0 or newer.
[Magisk] Setialpha:
There's the log?
[Magisk] Setialpha:
Of course not, they ate all signed with the same key. Some Stock ROMs don't like the F-Droid Priviledged extension, maybe disabling it helps?
[Magisk] elraffa:
I have enabled magisk hide for microg droidguard, restarted phone, deleted magisk data, WiFi is working fine and fast but safetynet API error still occurs

Enviado desde mi ALE-L23 mediante Tapatalk
[Magisk] epsilon_0:
Very sorry about that.

The two logs are on pastebin over here:

NanoDroid_twrp_19700608_17.15.20: pastebin.com/yJK0bxV2

NanoDroid_log_19700608_17.15.20: pastebin.com/57cNSG3M

Seems like for some reason the installer thinks there is no more space available...

Might this be because of the encrypted file system?

But this error did not occur when trying to install without Magisk.
[Magisk] elraffa:
sorry I don't know how to do it..Does it should be terminal logcat or magisk logcat?

Enviado desde mi ALE-L23 mediante Tapatalk
[Magisk] :
After updating to microg to dirty-115 getting many safetynet fails, need enable/disable droidguard many times to get it pass, anyone same ?
[Magisk] Kelvino9:
Disabling Privileged Extensions seem to do the trick. I tried it several times upgrading from different versions to another and it always worked. Thanks for the hint!
[Magisk] DoR3M3:
[MENTION=4187311]Setialpha[/MENTION] did you get a chance to look at my post?

https://xdaforums.com/showpost.php?p=78384344&postcount=5001

I'd like to be able to use NanoDroid-patcher in SuperR's Kitchen but it doesn't work.

My understanding is maybe the way you have the update-binary and updater-script, that this is backwards, what is in the update-binary is suppose to be in the updater-script.

The DEV mentions Magisk and SuperSU are good examples to follow...

In the meantime, on a rom I used the patch, I then coiped out the services.jar and added into a rom I'm building in Kitchen and it worked to apply sig spoofing.

Do you know how to apply Native Signature Spoofing to a ROM, and DOCS on how to do this?

Thanks
[Magisk] American_Jesus:
[MENTION=4187311]Setialpha[/MENTION] [MENTION=8340552]jenslody[/MENTION]

I'm unable to install NanoDroid since v19

Installing zip file '/external_sd/CustomROM/Magisk/Modules/NanoDroid-microG-20.3.20181208.zip'
Checking for Digest file...
Skipping Digest check: no Digest file found
I:Update binary zip
Verifying package compatibility...
Package doesn't contain compatibility.zip entry
I:Zip does not contain SELinux file_contexts file in its root.
I:Legacy property environment not used in updater.
/tmp/updater[11]: unzip: not found
!! failed to load Common Installer
Updater process ended with ERROR: 1

Full recovery.log attached
[Magisk] guest4711:
Your recovery lacks support fur unzip. Did you try to mount /system r/o before flashing (so the unzip binary from /system can be used)?
[Magisk] American_Jesus:
NanoDroid is the only zip that fails, other zip packages install without issues.

Thanks that helped, weird other magisk and non magisk zip packages install with no issues, this is the only one with that issue.
[Magisk] tom.android:
Manual Deodex & Signature spoofing patch Android Pie (Cdex)

1. Download TOAD - v3.0.0.1.exe from https://xdaforums.com/android/general/toad-source-android-deodexer-t3848307

2.Install by run exe

3.Copy your rom (framework folder and build.prop) into Your_Files folder. ****build.prop is important

4.Run TOAD.exe

5.Result is (deodex) services.jar ----TOAD_deodex_xxxx-xxxx.zip

------------Step 2

Patch file from step 5 with SmaliPatcher-0.0.2.9 from https://xdaforums.com/apps/magisk/module-smali-patcher-0-7-t3680053
[Magisk] mongo0:
As listed in the issues section, with magisk v. 18.0 SafetyNet check fails both ctsprofile and basicIntegrity.

However the proposed workaround (apply Magisk Hide for microG DroidGuard Helper) does not help here since it messes up microG ('microG DroidGuard Helper keeps stopping', when I press checking safetynet status and hide is active)
[Magisk] clewis.it:
Just install droidguard again as a user app.
[Magisk] darkvadd7:
Hi, I'm trying to flash nanodroid-patcher after a deodex, but it' stuck on >> patching services.jar, what can I do?
[Magisk] Setialpha:
I'll check it, the next days. Native? You'll have to grab the source, apply the patch from the microG repo and build the whole ROM.

I'll have a look.

That's actually what the command from the issues section does. I tested it on several ROMs, no issues here. I suppose SafetyNet is enabled from microG settings?
[Magisk] kurtn:
Wait 10 more minutes. The patcher is really slow on Oreo. Not tested on pie yet.
[Magisk] DoR3M3:
Ok, well for now, I just ran the NanoDroid-patch on a backup, then I kept a copy of the patched services.jar, and copied that into the new rom I built in SuperR's Kitchen, then flashed it in TWRP and when it booted and I checked with microG, it showed the signature spoof support was checked. So for now this works ok.

Just wasn't sure how invloved it was to turn a rom into native if possible, can it be done on a Stock Rom, with just some tweaking to the files, or it has to be when you compile/patch a rom?

Thanks
[Magisk] mongo0:
Yes, it is enabled in microG (official server), is this correct?

It still keeps crashing when checking for SN...

(In microG Settings self check everything is ticked off)

Thanks for your reply.
[Magisk] Setialpha:
'

Then you need to set it up properly. It can't work that way.
[Magisk] mongo0:
thanks for your response... Maybe "ticked off" was the wrong term. I meant that everything looks fine under Self-Check (is checked) and I can download from PS.
[Magisk] darkvadd7:
Thanks, it took almost 20 minutes to flash.
[Magisk] raptorddd:
used ot on lg g4 and it took more then 15 minutes.
[Magisk] mdl054:
Everything seems to be working well with latest release after I made the safetynet workaround change (pm install -r /system/app/DroidGuard/DroidGuard.apk)

This solved the safetynet issue but I have a problem with certain apps getting location now. Is it possible this change is related or am I following the wrong lead?
[Magisk] Setialpha:
Nope, DroidGuard Helper only is for SafetyNet and nothing else. If using Magisk, add those apps to MagiskHide.
[Magisk] Setialpha:
A new microG GmsCore build now up. On Android 6 and later you should no longer see microG in the Launcher, but in the System Settings instead. Thanks to vavun; also light theme by cbviva.
[Magisk] geoff-codes:
When would I wan't to use direct-install?

I'm sorry, but I'm a bit of a newb, and no, I haven't read all 500 previous pages of this thread (sorry: ( ), so it might have been already asked, but:

What would be the use case for wanting to use something like NanoDroid without Magisk (direct install)? Because, I mean, this is a modification that necessarily requires root regardless, right?

I guess I just don't quite understand why so many things are now offered both as a nice, clean systemless Magisk module AND also through these older frameworks/hacks that (especially these days) can be really harmful. So I guess, like, is there some tradeoff from using the Magisk approach with NanoDroid, that some people just don't want to make? Some downside to it that I'm not aware of?
[Magisk] honeyoil:
got stunned a little after microg shortcut disappearence:rolleyes:

integration looks great
[Magisk] guest4711:
First, there are some devices like my Samsung i9100 where magisk is not available.

Second, you don't need root for flashing nanodroid. You need a custom recovery like TWRP which you can boot (either by installing it or by adb fastboot method).

This way you don't need root or root access during normal operation. And your device is protected if you make a mistake...
[Magisk] geoff-codes:
Oh! For some reason I thought microG (because it impersonates parts of Google suite, required root (like for the signature impersonation and such). Thanks for the info!
[Magisk] kurtn:
Nice. Would be perfect, if microG settings would adapt to the general settings color scheme.
[Magisk] Setialpha:
cbviva said it's on the agenda, see: https://github.com/microg/android_external_MicroGUiTools/pull/13

If the Settings integration is working as intended, I'll send vavun's and my commits upstream, let's see whether it'll get merged.
[Magisk] Shobit Joura:
Hello devs may i ask when will microg be stable for android 9,, any plans soon???

I and many user and my friend found that unified nlp location just dont work, i wrote to their thread too , but no response sadly:(
[Magisk] Setialpha:
Dunno, ask [MENTION=3999488]MaR-V-iN[/MENTION], he's the microG developer. All I know is, that some ROMs have their location provider hardcoded or provide a conflicting one. On the Custom Pie ROMs I've tested so far, it's working as expected.
[Magisk] Klizi:
I use havoc os, with microg (fdroid)

Why snapchat never work with this?
[Magisk] Klizi:
No Google play services.
[Magisk] dhacke:
Did you try to install snapchat new? On my phone some apps need a new install before they recognize MicroG as Play Services.
[Magisk] Oswald Boelcke:
Maybe a search by @Klizi in @MaR-V-iN's µG thread is succesful? I realised that Klizi posted this "snapchat issue" already several times within the last month in this thread but I doubt it's NanoDroid related and that @Setialpha is able to fix it - or in other words: off-topic here.

However, regarding Snapchat I believe to remember that somebody posted following as a solution about one year ago (I'm aware that µG and most likely Snapchat have changed since then and inconveniently):

Flash GApps (whatever that requires? ROM clean flash?) - Install Snapchat - Take a backup of Snapchat by Titanium Backup (TB) - Remove GApps (whatever that requires?) - Flash µG - Restore TB backup of Snapchat.

As I'm not a user of Snapchat I'm not aware if it depends on or provides GCM push notifications. If this is the case I assume these are broken when applying the mentioned procedure.
[Magisk] Klizi:
Yes i installed after flashing fdroid and updating microg.

They never appear in registered apps list in microg settings

---------- Post added at 04:00 PM ---------- Previous post was at 03:53 PM ----------

Yes i posted this once. Its in 488 page in this thread and I don't see a solution through
[Magisk] Oswald Boelcke:
I don't want to be nitpicking, it was twice; here on page 488 and here on page 495. And the question remains why didn't receive you a solution or support in this thread? My best guess: It is not a NanoDroid issue!
[Magisk] dhacke:
[MENTION=9055513]Klizi[/MENTION]

Please correct me when i'm wrong but i am i right that you installed this bromite, parts of nanodroid and/or MicroG from f-droid?

I know probably you don't want to do this but i would make a full Wipe in this situation and install only nanodroid over the recovery and test snapchat and signal then.

It seems to me that you mixed many things.
[Magisk] Shobit Joura:
I am also talking about custom pie roms , i have tested havoc, aex , los, etc but none of them worked?
[Magisk] Setialpha:
I've tested NitrogenOS and Havoc and it worked on both. Maybe they include something conflicting?

You may run the SysTest zip and post the generated log.
[Magisk] Shobit Joura:
Ohhhk , is will do it later

---------- Post added at 06:50 PM ---------- Previous post was at 06:48 PM ----------

Did u gotsome time , then plzz see my logs i previously attached , in previous chats of our on this thread....plzx

---------- Post added at 06:52 PM ---------- Previous post was at 06:50 PM ----------

See those are here
[Magisk] Setialpha:
That's a logcat, but I'd like to see the SysTest log this time.
[Magisk] agentXshadow:
F-Droid stated there was an update to the microG Core from the Nanolx repo this morning. After installing, the microG settings app has disappeared from my launcher. However, it appears to still be functioning as expected.

Is this intended?

I'm on OmniRom 9.0
[Magisk] Setialpha:
You can use the patches with Haystack on-pc. Creating a new on-pc patcher Script has been on my agenda for a while now, since I'm in holidays for two weeks now, I'll get into it after christmas.

You can then patch the services.jar on-pc. Dunno about automatic Kitchen integration, though.
[Magisk] Setialpha:
Yes, see a few posts back, on Marshmallow and up it's shown in the System Settings now.
[Magisk] jenslody:
But it must be installed as system-(priv?)app, at least on my system.

Before it also worked as user-app.
[Magisk] TheUndertaker21:
hey guys

does patcher allow application with different signature to install on top of each other ? i installed it through twrp but it's not showing on magsik

idk if i did something wrong ? or i don't know how to test it
[Magisk] agentXshadow:
Thank you for clearing that up for me! It is indeed where it should be in that case.

With that, I'll add OmniRom 9 to the evidence of NanoDroid working on Android Pie.

Edit: I'll add that SafetyNet passes with the workaround (`pm install -r /path/to/DroidGuardHelper.aim`)
[Magisk] Setialpha:
Hmm, yes, I'd never expected someone to manually install it. But we may have both, so one can opt in to hide the launcher icon.

No, the patcher does not allow for such a thing, also it's not intended to show up in Magisk. It installs the patched services.jar into the NanoDroud module (or, if not installed, directly into /system).
[Magisk] TheUndertaker21:
what exactly does it do though? is that the same as smalipatcher ?

seems like it's impossible to disable signature verification without xposed which is a dead application
[Magisk] Setialpha:
It patches for signature spoofing which is required for microG GmsCore to disguise as GApps GmsCore. It does not allow to bypass signature verfication.
[Magisk] DoR3M3:
Ok on what you said...

Well running Nanodroid-patcher on a ROM, then keeping a backup of the services.jar, then dumping that into the /framework and build a new ROM with this in Kitchen, and then flash the new ROM in twrp and run it, this works... ;)

Cheers
[Magisk] LovepreetSinghGill:
I my case it is showing in launcher and in setting both
[Magisk] Klizi:
Same thing happened to me. [pie]Havoc OS
[Magisk] marcdw:
Read the previous page again where that is discussed.

ZTE Axon 7 A2017U, /e/ v0.1 ROM, microG (NoGapps), Multiboot, XDA Legacy
[Magisk] Klizi:
I made a nandroid backup and did this.

Wiped all.

Flashed clean havoc OS.

flashed the microg zip via recovery.

Installed snapchat, same result. Installed signal same result.

Then again,

Wiped, flashed clean Arrow OS, flashed microg. Installed snapchat and signal. Same result.

---------- Post added at 05:43 AM ---------- Previous post was at 05:34 AM ----------

Well, that's nice but this update made microg settings disappeared from everywhere in havoc OS. Even in system settings.

https://imgur.com/a/zRG2pxp
[Magisk] kmem:
Showing both places in AEX too.
[Magisk] Shobit Joura:
systest performed on aex 6.1 pie .

hello dev , i just clean installed aex , and ran systest latest stable zip as told by u , and i also checked that unified location isnt working , always the status is no known location.

hope this sytestlog helps:)

i also wanted tto ask, thatt my rom supports signature spoofing , and microg get granted signature spoofing , but playstore signature spoofing box remains unchecked but after flashing syspatcher , then play store also get signature spoofing .

cant we grant signature spoofing to play store without flashing syspatcher????
[Magisk] Setialpha:
DON'T flash the patcher on pre-patched ROMs, it can cause heavy issues. On pre-patched ROMs go to Settings> Apps > Permissions > Signature Spoofing and enable it for Play Store.

I'll check the logs later today, currently not at home.
[Magisk] Shobit Joura:
Ohhhk , waiting for the response for the logs ....later....
[Magisk] dhacke:
For signal you can use this version:

https://signal.org/android/apk/

Then you can avoid the problematic with microG because this version don't need as far as i know Google Play Services and GCM.

The notifications goes over websocket. It needs a little bit more Batterie power but then the notifications would work again.

Regarding Snapchat i don't know. Mayby they change something in the app and use something which MicroG doesn't cover.

I never used Snapchat so i can't help you really with this thing.
[Magisk] Klizi:
Yeah I'm already using the signal with the background processes. You can still download it via play store or yalp store, current version activates the background process if it can't detect the play services. Yes, it eats up the battery like a devil and also turns on some wake locks.

Anyway thank you for trying to help. I appreciate it
[Magisk] Setialpha:
OK. Your ROM does include com.qualcomm.location, but that should be disabled by NanoDroid automatically. You can test whether that's the case by running the following command, as root, on-device:

novl -l

the list should include com.qualcomm.location. If NOT, then run the following command, as root, on-device:

novl -a com.qualcomm.location

and reboot. If it still doesn't work afterwards, I don't know what going on for sure, your SysTest Log shows no other conflicting location provider (don't remove FusedLocation!) and your logcat shows that uNlp is started and both backends loaded. You may then create the file /data/media/0/microG.log like (again as root, on-device):

dumpsys package com.google.android.gms > /data/media/0/microG.log

and post that file, maybe something will show up there. Also, if your ROM allows it, try the different GPS modes and see whether they make a difference and whether the location backends have location access granted.
[Magisk] Shobit Joura:
Nopethis didn't worked,

I am attaching the log u asked....
[Magisk] Shobit Joura:
Nope this didn't worked and I am attaching the log.
[Magisk] Muzzammil Mehboob:
Microg isn't updating using nupd

Is there any other way to do it?
[Magisk] kurtn:
https://nanolx.org/fdroid/repo?fing...86FE93D14596B381D75BE83A1D616E2D44A12654AD015
[Magisk] Oswald Boelcke:
Search this thread (actually best practise prior to posting): @Setialpha already stated that "nupd" has been disabled and updates need to be done through the nanolx.org f-droid repo. @kurtn gratefully provided you with the link.

By the way: Same applies to the Google Play Store respectively "nups".
[Magisk] Shobit Joura:
Hello dev , sorry for boring u ,

But i wasymt able to download any apk of update , but instead the page forwarded me too source page and there i dont found any available link.... Plz help....

And my micg setting are still shown in app drawer but i heard it got moved to settings in latest update , can plz send me the kink of the page where apks can be downloaded of latest update ??
[Magisk] Muzzammil Mehboob:
Actually I didn't had enough time and I was away for a time being so I couldn't read previous posts.
[Magisk] Shobit Joura:
Bro i make it work in a way , try that , firstly download an old apk around 9.7.x.x.x

Then open it and let it load once , then u update it and woaah ur latest maps start working!!!

---------- Post added at 06:46 PM ---------- Previous post was at 06:33 PM ----------

Hello devs can soneone helo me in running my gps , since i am not able to run it , i searched in tgread but wasnt able to find a way , i also read faqs

My gps isnt working and deja vu provider isnt working too but after installing mozilla , location was working bu it is very inacurrate , can someone help me how to solve this , sorry for asking this if its already discussed....

I am on RR oreo 8.1...