yashsingh1/xdaforums huggingface dataset:
[Magisk] iacchi:
[MENTION=4187311]Setialpha[/MENTION] it's been a while since I asked the question (I moved to a new apartment so it took me a while to find the time to do this) but I have uninstalled Magisk 18.1 and tried to downgrade to 17.3, then reinstalled NanoDroid as you said, all from the same recovery session. After doing this, a problem that manifested itself when I first installed NanoDroid on this rom (official latest ZUI for ZUK Z2 pro, Oreo 8.0 based) presented itself again, but this time I could not fix it.

The problem: when I install NanoDroid, DroidGuard Helper and the Services Framework Proxy get installed, but GmsCore doesn't. Or at least, the apk is in /system/priv-app, but apart from that everything looks like it's not installed (microG settings app not installed, GmsCore doesn't appear in the list of installed apps). Last time this happened I found the GmsCore app on F-Droid (from your repo), I installed it from there and all was fine. This time instead the app was not in there, so this workaround didn't work (please note that even the last time, after installing it, it disappeared from F-Droid). This failing, I tried to go to /system/priv-app/GmsCore and click on the apk from there to install it, but install failed. I'm attaching a logcat of the failed install with this method. I'm happy to provide other logcats, if you tell me what you need.

First of all, there is the need to figure out why GmsCore doesn't get installed during NanoDroid installation. Second, there is the problem of installing it in some way in the current system, so that I can use it. Thanks in advance for all your help!
[Magisk] marcdw:
Your ROM is Marshmallow. So is the one I'm on now, a debloated stock. Had the same issue. First I went with the adapters included with the ROM. No contacts sync.

Next round of ROM flashing I removed the adapters and flashed a Shadow53 zip. Same results. Zip from ale5000 wouldn't install (forgot it doesn't support MM).

When I went with using NanoDroid I used the adapters therein. Syncing is good. Suggest you try again with NanoDroid. Not sure why your ROM didn't recognize the adapters.

I mentioned DAVx5 (formerly DAVdroid) earlier. I usually use that on my setups. You could consider that if the adapters just don't work out .

LG G3 D851, Clean ROM v3.2, NanoDroid (microG), MultiROM, XDA Legacy
[Magisk] DoR3M3:
I don't mean to go Off-Topic here, but hopefully a lot of people, myself included will appreciate understanding the differences, reasons, or needs for using Haystack over NanoDroid-patcher, if you could give a brief explanation?

With no disrepect at all to you, I looked over the GitHub repo in the past, when I was trying to decide back then, which method to use, Haystack, Tingle, NanoDroid-patcher and thought, why go to all this trouble with Haystack or Tingle, when the NanoDroid-patcher seems to do the job just fine, and is very simple, just flash it in TWRP...

Anyhow, I'd really love to know any reasons as to why someone should choose Haystack over NanoDroid-patcher?

Thanks
[Magisk] PoochyX:
Haystack leaves a option in developer options to turn on or off signature spoofing as the nano patcher patches the framework directly and to remove signature spoofing you have to replace the jar file with the unpatched one that gets backed up when you use the nanidroid patcher

PoochyXXX
[Magisk] Setialpha:
Nope. To put it simple: [MENTION=4141005]Lanchon[/MENTION] is the developer of dexpatcher, a tool to modify dex files. Haystack is a 'frontend' to dexpatcher and provides the patches for signature spoofing and UI; it is run on PC. NanoDroid-Patcher is another 'frontend' to dexpatcher, which uses Haystack patches; it is run on device.

tl;dr that's just been a patch update notification.

The UI patch isn't included in NanoDroid-Patcher, but may make a return, who knows.
[Magisk] djuka007:
There's a HUGE difference between the adapters included in the latest beta and the latest stable. The ones in the latest beta seem like mock files, while the ones in the stable release are the actual apks.

Right now I have both adapters syncing but I don't get any syncing done.

Will try to clear cashe/data for all the apps and see what happens, if not I'll uninstall the microG and try again.
[Magisk] djuka007:
Everything works now. I hope those adapters will be fixed in the new stable version.
[Magisk] Setialpha:
The issue is already resolved in the build-package script on gitlab, so yes.
[Magisk] Setialpha:
It's likely the magisk.img issue fixed with the current beta. So yes, others had it aswell and fix is currently in the beta channel, coming to stable, soon™.
[Magisk] Setialpha:
20.7.20190310 "749 Mark 148"

Hi all,

version 20.7 is now available, Codename for this release is "749 Mark 148".

This release features a few bug fixes and improvements, aswell as the usual updates, aswell as updated patches for signature spoofing.

ChangeLog

## 20.7.20190310 "749 Mark 148"

### Bug Fixes

* nanodroid-perm
* fix typo prevent some permissions to be set

* Installer
* fix resizing magisk.img failing due it being dirty
* fix GApps removal in certain cases
* fix compatibility with LineageOS for microG
* certain components now only get removed if NanoDroid's replacements are actually going to be installed
* fix storing library installation information in System Mode installation for APKs installed to an alias path
* fixes addon.d being unable to restore libraries after ROM update
* affects microG GmsCore and Bromite WebView

### General

* Installer
* re-use already unpacked framework-res when checking for native sigspoof more than once
* more verbose GApps removal logging
* make `unzip` less noisy to prevent twrp.log pollution

* Patcher
* update Haystack patches to 20190308 by @Lanchon
* improved patches
* official Android Pie support

* build-package Script
* update to new OpenGApps host URL

### Updates

* automatic
* Simple Gallery (6.5.5)
* Simple Calendar (6.3.2)
* Bromite System WebView (73.0.3683.61)
* Odyssey (1.1.17)
* NewPipe (0.16.0)
* Termux (0.66)
* Blokada (3.7.022000)
* AnySoftKeyboard (1.9.2629)
* Open Camera (1.45.2)
* QKSMS (3.6.3)

* manual
* microG GmsCore (0.2.6.15090-167-dirty)
* Play Store (13.8.16)

Download links

Download from Nanolx.

Bug reporting

In case of errors, please provide

/data/adb/MODID_log_INSTALLDATE

/data/adb/MODID_twrp_INSTALLDATE

SysTest package logfile

logcat (if applicable)
[Magisk] Lanchon:
NanoDroid-patcher *is* haystack. but haystack is intended to run on a PC. NanoDroid-patcher is essentially some parts of haystack packaged to run in recovery.

most of haystack deals with generating tailored patches for, compiling them against, and test-applying them over, each android version from 1.5 through 9.0. it is also the project that provides the source of the patches. NanoDroid-patcher bundles only the binary patches produced by haystack and the tool that applies them.

said tool, called dexpatcher, happens to also be developed by me, and haystack is just a use-case for it. a pretty boring one at that: in fact, the only reason i maintain haystack at all (and not that often, unfortunately) is because nanolx uses it and he has a user base.

the dexpatcher tool is a portable "common-subset java" project, runnable on both java's and android's VMs.

but as any java bytecode, it requires a VM to run. nanolx' original work on NanoDroid-patcher is essentially setting up the stage to run java bytecode within recovery at all, which is no small feat. when we discussed how to do this, i was leaning on bundling a "small" VM implementation in the zipfile. but he ended up creating this solution in which he builds a proper runtime environment, and then mounts /system and uses the ART (android's VM) that is installed there instead. (one must be; otherwise... what are you patching?) a lot of work in FLOSS is packaging, adapting and extending other people's work. nobody creates anything from scratch. i wouldn't be able to use linux at all if it wasn't for the work of projects like the debian or ubuntu distros.

anyway... running android's VM outside of android is a very interesting development. dexpatcher is interesting too. haystack is boring.

fin
[Magisk] DoR3M3:
As mentioned by PoochyXXX, Haystack leaving an option in developer options to turn on or off signature spoofing, which I always assumed was an option added to the "Application Permissions" section...

Can the NanoDroid-patcher be made so that Signature Spoof support is incorporated "Natively" into the framework? So a ROM that doesn't have Native Sig Spooof Support can now have it with the NanoDroid-pathcer? With this "Signature Spoofing" option now in the "Application Permissions"?

Thanks for keeping up this boring project as you put it... LOL ;) It's HIGHLY APPRECIATED!

Cheers
[Magisk] PoochyX:
Is Java needed to run the front end for the dexpatcher.

PoochyXXX
[Magisk] djuka007:
Good! Thx!

One more thing.

The location is working up to a point but it's very variable.

It doesn't work "out of the box", had to install Mozilla backend and set permissions for fine and coarse location in the terminal, but settings don't stick after a reboot (put a script in init.d to fix this).

Also, even though mock location works with Google Maps (installed without a problem) it doesn't seem to work with Tinder.

Wonder how to troubleshoot that.
[Magisk] daywalk3r666:
its not a bug but maybe for future develoment interesting.the canary builds of magisk has no longer magisk.img

modules are stored now in /data/adb/modules
[Magisk] Setialpha:
It's still not 'native' as in 'full fledged part of permission model'. I already said some words about the UI patch.
[Magisk] Danko Jones:
I have a (probably) stupid question. A year ago I switched from GApps to microG/nanodroid to avoid google collecting my data and draining my battery. Actually I'm using yalp store to get apps from play store which is working more or less.

To my question: Is it also save to use the patched play store version regarding privacy? Is the app also collecting data like google services app or is it not comparable?

Thanks in advance for any infos about that.
[Magisk] d1n0x:
Even with MicroG, Google is collecting data. It's not as much as with Gapps though. And if you log in to yalp with your account, your app installs will be connected to your account.
[Magisk] Danko Jones:
Thanks for reply.

Actually I'm using yalp store with fake yalp account. So the question would be if google can collect anything more then my installed apps when I use my google account to load and update apps (besides the data collections you already mentioned).
[Magisk] Oswald Boelcke:
By my experience, the modified play store collects (or is trying to collect) the same data as the original Google Play Store. In order to work the play store obviously requires access to the list of installed applications (same as Yalp does) and to my Google account (Remark: I personally never run Yalp with my Google credentials). The modified play store is the one and only Google application on my device running µG powered by NanoDroid.

The attached screenshots show my personal settings to limit/avoid data collection and/or transmission by Google Play Store. A very important part plays the fake of information through XPrivacyLua (however, this requires Xposed, which definitely breaks SafetyNet and might not be suitable for some people).

EDIT: Off-topic for @user2k10 - AppOpsXposed v1.30.3 as of 2016-02-21 (Xposed repo); running perfectly on my RR-N-v5.8.5

And off-topic for @djuka007 - MyAndroidTools Pro.
[Magisk] PoochyX:
Ad listener should be declined also as it collects information to use to dispense ads just saying

PoochyXXX
[Magisk] Oswald Boelcke:
Oh, that's the AD ID listener, and I don't care about this service being enabled as I rather fake the ID as the last screenshot shows. But you're right, who doesn't fake should disable the service.
[Magisk] Oswald Boelcke:
https://xdaforums.com/showpost.php?p=79089537&postcount=5824
[Magisk] djuka007:
I have Xposed and XPrivacyLua installed and SafetyNet seems to work.

Just wanted to ask you which is the app beside Appops and XPrivacy that you put in the screenshots, I don't recognize it
[Magisk] afridi.shahriar:
hey, thanks [MENTION=4187311]Setialpha[/MENTION] for keeping microG updated and usable with latest android versions.

but, it doesn't support FCM, so, many apps' notifications are not showing, till the apps r being opened.

can u kindly do something?
[Magisk] iacchi:
In short: no. NanoDroid is just (a bit of an understatement) of microG, which is developed mainly by mar-v-in. Anyway, FCM support in microG is non-existant, and there's nothing setialpha can do about it (short of implementing it single-handed).
[Magisk] afridi.shahriar:
but, microG is opensource, so, cant he try to add FCM support?
[Magisk] iacchi:
Of course he can, as I said. I think you just don't realise the amount of work that this is (keep in mind that I think this basically involves reverse-engineering Google code).
[Magisk] PoochyX:
So soon micro G is going to be depracated due to the fact that newly updated apps will be using firebase cloud messaging instead of Google cloud messaging and since the op is just porting this to magisk there is nothing he can do to implement FCM cause he isn't the maintainer of micro G and the maintainer of Micro G Marvin hasn't added any new commits to Micro G in a while and the last commits have nothing about changing methods to the newest form of cloud messaging its always a cat and mouse game between Google and developers...

Like Chainfire says Google has a team of competent engineers behind them

PoochyXXX
[Magisk] dhacke:
Just my opinion to that topic: I think the most devs there make themselfes to easy with that FCM.

All apps which i have use polling instead of FCM/GCM and that works.

Yes the developers need to support this alternative but mayby a e-mail to them could help. I don't know. Probably the most developers don't even know about this option.

Then it wouldn't matter whether MicroG supports FCM or not.
[Magisk] DoR3M3:
Is there anyway you think in the future to have this native/full fledged for ROMs that don't have this support, and NanoDroid can provide it?

Not sure about these words you are talking about in regards to the UI patch?

Thanks
[Magisk] starbright_:
Is there a good reason to offer OSMand as a module? Is there any advantage over installing it via FDroid? Some remapping google maps to OSMand? Or is it just because installation is more conveniant?

For FDroid I can imagine the advantage of a deeper integration to the system in terms of permissions. But for OSMand?

Instead of Mozilla location service (or optional): Can you add GSM location service (that can work offline with a downloaded database - I like it)
[Magisk] Oswald Boelcke:
OSMand has been definitely worth to be incorporated into the full NanoDroid app portfolio; however, from my understanding (and I bet a saerch within this thread will lead to a post by Setialpha that confirms this) OSMand was too large, and hence Setialpha provided it as an own module (btw: same applies to Bromite Webview).

Regarding the location service: I use one that works offline witha downloaded database). All available via F-droid. I think, Setialpha had to very selectively decide, which FOSS to include into the full NanoDroid package. He cannot incorporate everything due to size limitations. Even if you make it optional (to install) it must be in the package.
[Magisk] starbright_:
I like that too, but why should this be installed like that and not in the classical way via FDroid? Is there a benefit over the standard installation? That is my question.
[Magisk] Oswald Boelcke:
None of the applications provided in the full package (including OSMand as single sub-module) as replacements for the pseudo-debloated applications require to be installed via NanoDroid. It's simply convenience but you can just use the "standard" installation e.g. via F-Droid. Even the F-Droid sub-module isn't required if you prefer to install F-Droid "normally" and then flash the Magisk module for the F-Droid privileged extension.

TL;DR: No benefit.
[Magisk] oF2pks:
Are you sure your Pie rom is correctly patched (deodex...); I build a phh-treble microg specific, with patch and every thing working/included here : https://xdaforums.com/project-trebl...arm64aosp-9-0-0r21-microg-ufofficial-t3878115

(indeed)

It "often" starts to work after few "hours" (when doze throttling stops (?)).

[MENTION=4187311]Setialpha[/MENTION] , on Pie with new doze/alarm system, depending if device is plugged or not, all backends appear to be throttled, and thus first location always failed; so not only location.fused has to be unlocked for <allow-in-power-save...> but all known backends need <allow-unthrottled-location...>.

Conversely microG gmscore seems to work fine without <allow-in-power-save...> & <allow-in-data-usage-save...> and the built-in warning for GCM & push notifications is pretty well designed (end user is free to choose for battery...)

[MENTION=5627087]ale5000[/MENTION] attached /etc/sysconfig/microg-a5k.xml seems to solve all microG defects on Pie (compare to "simplified" oreo and previous), I believed this (and location.fused specifics) should be notified in latest Pie patches: it can be done straight in aosp deep source or through aosp/device source setup before build, or with a "live" Magisk.

Also confirm working, on Pie: target sdk28, buildTools 28.0.3 and manifest/multiArch for GmsCore GoogleServicesFramework and DroidGuard (safetyNet ok when /system fingerprint paired with /vendor). [MENTION=8949533]DoR3M3[/MENTION] if you need them for Pie, they are attached here : https://xdaforums.com/project-trebl...ufofficial-t3878115/post78401533#post78401533 ; gmscore is anticipated to 16.9.99 (official beta is already to 16.0.86)
[Magisk] Cyberavater:
What about adding youtube vanced? https://xdaforums.com/android/apps-games/app-youtube-vanced-edition-t3758757
[Magisk] garylawwd:
What about adding a Google app to modules that promote ditching Google altogether?

Kinda sounds counter productive even if its vanced version
[Magisk] Cyberavater:
Well this module already has modded Playstore, then what's wrong with having modded Youtube as well?

BTW, Youtube Vanced doesn't use google services it uses MicroG
[Magisk] Shobit Joura:
I think microg will die when fushcia os will come

What u think?
[Magisk] marcdw:
Oops, went off on a tangent. LOL. Deleted.
[Magisk] Setialpha:
Because there's no actual alternative for paid applications.

NanoDroid already includes NewPipe as YouTube client.

We don't even know all details what Fuchsia will turn out, so I'm not thinking about it. Also given Androids market share, I do have doubts it will be something available soon, if they ditch Android and people/OEMs don't like Fuchsia, they'll loose their market. I suppose it's safer to assume Fuchsia to replace ChromeOS, or enter a new niche, rather than replacing Androing in the next few years. But don't give too much on my opionion.
[Magisk] Cyberavater:
I know, I use Nanodroid. But original Youtube seems cooler to me. ( I don't know, maybe I'm just being biased about it?)

Anyway, I use Youtube Vanced additionally as default Youtube app thought it might be a good idea to suggest it here. If it's against this module's policy it's totally understandable.
[Magisk] Tomatot-:
HI [MENTION=4187311]Setialpha[/MENTION] , some users who wanted to flash Omnirom on OnePlus 6 reported me that their phone wouldn't boot with 20.7, whereas 20.6 was working fine.

I've seen in the changelog you've changed permissions stuff. Is it possible you broke again permissions for stores? If you remember there was an issue before with this specific device/ROM but you fixed it after I sent you a log. Do you need a new log or do you already have an idea of what's the issue? I can personally try to reproduce the issue if you don't know where the issue comes from and I can try a fix if you have one to share.

Thanks for your time.
[Magisk] Setialpha:
*sigh* I added a new perm to uG whitelist, in order to fix Geocoder compat with an other ROM, as per user report/logcat, but OmniROM *****es now. The fix already is in the git repo.
[Magisk] Tomatot-:
Ah feels bad man. Well, thank you for the quick fix.
[Magisk] cRaZy-bisCuiT:
Thanks for NanoDroid!

I got a few questions:

1. If I just want MicroG + Location provider to work, no additional apps and bloat, what package do I need?

2. If I upgrade my ROM (let's say using ArrowOS which comes with weekly updates which you dirty flash): Do I need to re-install NanoDroid after every single update? How could I try to avoid that?
[Magisk] dhacke:
Then you need the zip with 'microG' in the name and must edit the setup file in the zip file. Otherwise the zip installs the patched play store version, too.

I can look later at home what exactly you must change to avoid the Installation of the play store (if you want).

By dirty flash no. You must only make the microG setup again.
[Magisk] kurtn:
Never had to setup anything after dirty/ota updates.
[Magisk] dhacke:
Ok mayby i had a wrong memory about that. Sry.
[Magisk] guest4711:
If you installed it systemless (as a MagiskModule) there's no need to reinstall anything after OTA / flashing your ROM as long as you don't wipe /data/adb.
[Magisk] b4rgh3st:
Hi,

How does LineageOS for MicroG interact with nanodroid? I know that I don't need to patch it but what about the other stuff like privileged f-droid, the patched PlayStore, location backend and so on? Can I just use Nanodroid to add this stuff and use the debloater/installer and use the "override function"?
[Magisk] kurtn:
Lineage4microG has privileged f-droid. Patched playstore is ok to take from nanodroid. Location back ends are up-to-date in f-droid. MicroG is different in nanodroid. I would use that if apps urge me to update google play services. I would never flash the full nanodroid, but use the aroma installer to select the things I really need.
[Magisk] Setialpha:
Hi all,

as you've surely seen mar-v-in is active again, dedicating about 20 hours a week to microG. He already merged a few changes by various contributors (gudenau, voidstarstar, porygonzrocks, armills, vavun, jimbo1qaz, lockdis, ale5000 and me) upstream and a few more pull requests are still open. You should have received a new unofficial microG build by me two days ago. I'd like to encourage you to report any occuring issues, as it includes the updated versions of some earlier merged pull requests which are now upstream, aswell as the pending pull requests.

Especially the effect of this one should be tested: Temporary whitelist support for Doze by voidstarstar, even more so if anyone uses manged/work profiles.

Thanks in advance.
[Magisk] jemail:
I installed the patched Google Play Store from the F-Droid repo. I get error DF DFERH-01 whenever I try to launch the Google Play Store. I've tried clearing caches, data and removing the Google account and re adding it but I cannot get past this error.

Any ideas?
[Magisk] daywalk3r666:
grant signature spoofing

https://gitlab.com/Nanolx/NanoDroid#issues
[Magisk] jemail:
Thanks for the link ?:)

All Signature spoofing functionality is already checked in microG self check and is integrated into the custom ROM I'm using.

I can use the unpatched version of Google Play Store with no problems, it's just the patched version which throws the error and it's a different error than the one mentioned in the issues link.
[Magisk] DrUnknownEMC:
Usually a reboot fixes for me.
[Magisk] Oswald Boelcke:
First: Negative, you do not need to upgrade to v20.7 from v20.6 in order to be able to receive updates via F-droid.

However, it looks to me that you have only added the µG F-droid repo. I suggest to also add the "NanoDroid companion F-Droid repository" that provides you with the updates as indicated in the OP:
[Magisk] jenslody:
If you already have microG from their repo and want to switch to the nanodroid-repo, you have to unistall microG first, because both apps are signed with different keys and you can not upgrade from the one to the other.