yashsingh1/xdaforums huggingface dataset:
[Magisk] :
Hi everything seems to be working well,except play store it gives me an error message,I tried to reboot and clear data,cache but the problem still there,any solution ?
[Magisk] Setialpha:
You need to grant all permissions it asks for (yes, all), make sure sigspoof is enabled. On first start of it after clearing data, closing it (recent app screen, close Play Store) might help.
[Magisk] Setialpha:
Dunno what's wrong mit your ROM not liking microG, please post a logcat, maybe the PackageManager logs something useful.

About F-Droid, nope, the bleeding edge has proven to be almost as stable as the stable release for a long time now, plus new stuff accessible earlier. That's not gonna change from my side.
[Magisk] Setialpha:
Just flash for upgrade, for the bootloop please post a logcat (use 'adb logcat' while connected to PC).

A handful devices/ROMs seem to not like Magisk 17.

The logcat will help sched light, what's the cause, never ocurred during my tests.
[Magisk] Setialpha:
Dunno, with Magisk it works so far. It also scans your /sdcard and stuff for unallowed things, active developer settings, adb active and more. Seems it detects something, but it won't tell us what it detected.

Magisk basically hides everything from it.
[Magisk] Bracher:
Problem with UnifiedNlp and Nanodroid 18 beta and 18.1

Hi I have a problem with the two last ticket boxes, though I have 6 backends installed, updated and given the necessary permissions, which work fine and SatStats and OsMand have no problem to find my location still the two last ticket boxes are empty the message is: check your location provider services (bad english sorry), I made several restarts without any result. It's not yet a big problem as my location is still found with OsMand only the weather service does not work
[Magisk] [Alien]:
Any progress with FCM?
[Magisk] Oswald Boelcke:
What's your ROM (version)? Currently on NanoDroid microG 18.1.20180909, only 4 backends installed. When I used RR-O-6.0.1, the last two tick boxes always remained empty but localisation worked properly. Back on RR-N-v5.8.5, all boxes tick-marked. Personally, I'd point towards the ROM.
[Magisk] Bracher:
It's LOS 15.1 official version, unfortunately the 14.1 ROM for the Fairphone 2 is no longer maintained so I had to switch to ROM 15.1. Everything works well (ok I had to disable "hide" in Magisk otherwise I could not install any apk) Nanodroid microG, the patcher, xposed, xprivaxylua, the playstore, fdroid... Only the weather service does not work and I suppose it's caused by these two last tick boxes
[Magisk] d1n0x:
Why don't you just use LineageMicroG, if Lineage is officially supported?
[Magisk] Bracher:
I need the patched Playstore, that's the only app I use from Google but without I'll have no access to my paid apps like Süddeutsche Zeitung and other digital versions of Newspaper and there are as well some other apps I would missing. Besides I checked MicroG as well but even with MicroG there was one tick box (the last one unchecked) - and I had given all necessary permissions and the location provider full on (sorry my bad English). So this is unfortunately for me not a real alternative.
[Magisk] Setialpha:
The second last checkbox indicates whether the backends are activated, did you ensure you actually activated them?

Else only a logcat will sched light to the issue.
[Magisk] Setialpha:
Not yet, see the bounty or ask in the microG thread.
[Magisk] DoR3M3:
Ok on F-Droid, sounds good!

But with NanoDroid-microG-18.0.3.20180908 nupd mg was still failing on me with the same message as before, I've attached the screen shot from my last reply, not sure if you saw that or not, you didn't mention anything.

I've been playing with a lot of things, so I went back and wiped and flashed it all over and doing exactly the same steps, this second time in a row NanoDroid-microG-18.1.20180909 install failed.

So I have a logcat for you. I just don't get how one time I can flash it and it works and the next time it doesn't. Also I noticed in Debloater (Terminal Emulator) YouTube listed, which it shouldn't be there if it's been debloated with microg, because everything else doesn't show up. When I tried to remove it in Debloater, it said Failed, that YouTube was mounted.

In the past I've always done these steps.

1. Deodex Stock Oreo

2. Flashed NanoDroid-patcher

3. Flashed NanoDroid-microg
[Magisk] gadgetguy08:
I was getting the same failure msg for nupd mg and was trying lots of things to make it work. I think the last thing was to go to /system/app/gsfproxy.apk and click to install that again and the nupd started working. There was a reboot or two involved as well. Wish I had taken better notes.
[Magisk] DoR3M3:
No worries, let's see what Setialpha has up his sleeve... ;)
[Magisk] Setialpha:
Hmmm, may be an issue with with GSF from GApps Vs. GSF from microG. I'll see...
[Magisk] :
Any plans on switching from orfox with that new official tor browser relase?
[Magisk] the.D:
[MENTION=4187311]Setialpha[/MENTION] Any plans to update the patcher to include permission restrictions on signature spoofing? It's a security concern that any app can use signature spoofing and not just system apps.
[Magisk] Setialpha:
That's not possible in a universal patcher, use a pre-patched ROM for that, or ask the ROM dev to include the patch from microG repo. Plus, I'd say it's a virtual issue, because

a) you can check what apps request it (because it must be defined in the manifest)

b) microG users usually don't install any random apk

c) it does only spoof externally, not internally, thus the package manager can't be fooled

d) self patched ROMs are below 0,0x % of all users, no one wastes their time to exploit a minority like that
[Magisk] Setialpha:
Ok, the log contains hints of old GApps s**t still int way somehow. Please run the following commands, as roo, on-device:

find /system /data/{app,data,misc*,system*} > /sdcard/find.txt

and post the generated file find.txt from internal storage.
[Magisk] DoR3M3:
Well I wiped the phone to try over, and now it's working again. I then wiped and flashed it twice in a row and it still is working. So I'm not sure if a mistake on my end or what.

For the moment I can't reproduce it, if it happens again I'll post the find.txt

Thanks
[Magisk] sajjads24:
hi

can i install and use nanodroid on lineage 15.1 for i9100 with supersu ?(magisk not support i9100)
[Magisk] kurtn:
I recommend to stay with 14.1

https://download.lineage.microg.org/
[Magisk] Setialpha:
I suppose it has to do whether you booted into the ROM once and thus had data of GApps already populated, which the installer didn't delete.
[Magisk] guest4711:
Yes, you may. I'm using it with LOS addon-su (use TWRP to install NanoDroid in systemmode).
[Magisk] HyperCriSiS:
Is there a force parameter to override signature mismatch?
[Magisk] Setialpha:
Nope. That could easily be exploited, thus Android doesn't offer it. What do you need it for?
[Magisk] ichmyselfandi:
Does somebody uses NanoDroid with ArrowOS 9.x and can tell me if it works and if so do I need to deodex the ROM?
[Magisk] Apex Predator:
I've done multiple tests installing 18.1 (full package) and no matter what I try, debloat is 100% not working in any way. In addition, if I deselect the debloat option at the beginning of the wizard it still brings up the debloat selection page as you step through it. As mentioned in previous posts, other strange things are happening with apps.

I have even tried completely fresh installs, clean slates...full wipe including data. Reinstall ROM, Magisk then v18.1. Still can't get debloat to work. Also can't get apps to register for GCM on a clean install. I should note that this time I only installed Fakestore (and granted sig spoof permissions). Is it possible that play store not being present could cause that?

Where things are at now is I restored my backup, installed 18.1, THEN updated Magisk to 17.1 (16.7 was on already). This way round GCM remained functional for Protonmail and Push Notification Tester works as well. Couldn't get either to work on clean install.

Other strange things occur with apps being invisible and/or undeletable. Too much detail I can't be bothered to type right now...

Apologies for all the *****ing, it's just between Magisk and NanoDroid I'm getting tired of spending so much time just trying to make things work with a modicum of stability and predictability. There's a fine line between "I enjoy tinkering" and "I'm losing mind with this ****". I think I've crossed it.
[Magisk] DoR3M3:
These are the steps I am following.

1. Wipe in TWRP

2. Next boot to bootloader and fastboot -w, next flash stock Oreo

3. Boot in to phone and set up

4. Boot to bootloader, then flash twrp.img and boot into TWRP

5. Deodex rom and flash NanoDroid-patcher

6. Boot to bootloader, then back to TWRP and flash boot.img and Magisk

7. Boot into phone

8. Boot back to bootloader - flash twrp.img and boot into TWRP and flash microg

Yeah a lot of booting around, LOL, not sure what's wrong with these steps to muck it up, but this is what I do everytime...
[Magisk] HyperCriSiS:
I installed microG with your package but I get signature mismatch error when I try to update via nupd. I even have an xposed module installed which disables signature check but nupd seems to install apks differently.
[Magisk] Bracher:
Sorry I have another question:

Does anybody use Locus Maps? Obviously the new version of Locus Maps is no longer working with the patched Playstore. I can't access the Locus Store via Play Store so I'm not able to buy updates for my maps. I contacted the developper of Locus Maps and obviously there was an error from Google Play services library: API_NOT_CONNECTED. In the old version of Locus Map everything works well. I use Nanodroid-MicroG 18.1 - and all other apps work fine with the Playstore (I can't upload the logfile, sorry).

(my last question relating to Fairphone and LOS 15.1, which caused problems with Magisk and MicroG settings - last two tick boxes empty, it's a ROM Problem and I can live with, thanks for the offer to help Setialpha, but you have much on your plate and this is a ROM problem)

---------- Post added at 01:26 PM ---------- Previous post was at 12:50 PM ----------

I found a solution for the open last two tick boxes - so if somebody has the same problem: fortunately I copied the old files "org.fitchfamily.android.gsmlocation" and "org.openmap.unifiedNlp" before the update from LOS 14.1 to 15.1 on my PC. Today I found out that on my Fairphone those two files have been empty (in Internal storage/Android/data) obviously the download had not taken place. So I copied back the old files from my PC and voilà the last two tick boxes are now ok and I was able to update the Database
[Magisk] :
there is a possibility to use microg without the play stores?

Enviado desde mi K88 mediante Tapatalk
[Magisk] abacate123:
Yeah, you can. You can flash the setupwizard zip before the main nanodroid package(s), and select which one you want or you don't want.
[Magisk] :
But there should be a package.zip that does not include play store[emoji16]

Enviado desde mi K88 mediante Tapatalk
[Magisk] abacate123:
Nope. The installation is optional and configurable. But if you want something not related to microG or Play Store, try the F-Droid package then. It only includes the F-Droid app itself and it's own privileged extension (to allow background installation).

https://gitlab.com/Nanolx/NanoDroid/blob/master/README.md#packages
[Magisk] :
I did not mean that but thanks, I tried to explain as cool as possible

Enviado desde mi K88 mediante Tapatalk
[Magisk] abacate123:
And I answered you here.
[Magisk] bertino:
I installed an update to my ROM (nitrogen P), and now the patcher doesn't work anymore it flashes normally, but microg says I still don't have spoofing support.
[Magisk] DoR3M3:
[MENTION=4187311]Setialpha[/MENTION]

nupd mg is failing to udpate, please see the screen shot and attached logcat.

Also Notification Dots do not work after installing microg, please see logcat_2 & logcat_3, I had to split it up, to big...

Thanks
[Magisk] DoR3M3:
post error, forum acting up... :(
[Magisk] starbright_:
I've tried to install/run the patcher just in one shot with lineage and addsu. Not sure wether this should be possible or not - at least it doesn't work. It is same problem I've been faced of with previous patchers, seems that vendor is not available.

Is this a special LOS15.1 issue or one special of my ROM? Or do I have do reboot before? Or shall I still do in TWRP the "ln -s /system/vendor /vendor" .

Thank you.

NanoDroid 18.1.20180909
... > Android 7.0 - 9.0 (SDK 27) detected
> Custom ROM detected
> device architecture: arm

++
++ services.jar status: VDEX
++

> patching signature spoofing support

>> deodexing services.jar [VDEX]
[INFO] Processing 1 file(s) from /dev/tmp/install/dexpatcher/services.vdex
[DEBUG] [2484] 2018/09/15 03:10:21 (jni/../src/vdexExtractor.c:194 main) Processing '/dev/tmp/install/dexpatcher/services.vdex'
[DEBUG] [2484] 2018/09/15 03:10:21 (jni/../src/vdex_api.c:41 vdexApi_initEnv) Initializing environment for Vdex version '010'
------ Vdex Header Info ------
magic header & version : vdex-010
number of dex files : 1 (1)
dex size (overall) : 86c024 (8831012)
verifier dependencies size : 123f0 (74736)
verifier dependencies offset: 86c040 (8831040)
quickening info size : a54 (2644)
quickening info offset : 87e430 (8905776)
dex files info :
[0] location checksum : d085bb2c (3498425132)
---- EOF Vdex Header Info ----
[DEBUG] [2484] 2018/09/15 03:10:21 (jni/../src/vdex/vdex_010.c:75 vdex_010_GetNextDexFileData) Processing first Dex file at offset:0x1c
[DEBUG] [2484] 2018/09/15 03:10:21 (jni/../src/dex.c:351 dex_isValidDex) Dex version '037' detected
[DEBUG] [2484] 2018/09/15 03:10:21 (jni/../src/vdex/vdex_010.c:199 vdex_010_process) Took 331 ms to process Vdex file
[INFO] 1 out of 1 Vdex files have been processed
[INFO] 1 Dex files have been extracted in total
[INFO] Extracted Dex files are available in '/dev/tmp/install/dexpatcher'
adding: classes.dex (deflated 55%)
>> patching services.jar
Error preloading public library libandroid.so: dlopen failed: library "/vendor/lib/libcamera_client_shim.so" not found
libc: Fatal signal 6 (SIGABRT), code -6 in tid 2488 (main), pid 2488 (main)
Aborted

!! failed to apply patches
[Magisk] Setialpha:
18.2 should fix this, will be released Kaplan-Very-Soon™.

Wait for 18.2, it /may/ fix the issue.
[Magisk] Setialpha:
18.2.20180916

Hi all, version 18.2 is now availabe.

Important Update Notes

1. For those who are on Stock ROMs and having issues with microG, a clean flash of NanoDroid is recommended (read: Uninstall and Re-Install NanoDroid).

2. Before flashing 18.2 go to Settings > Apps > All Apps > microG GmsCore > Uninstall Updates

Theese steps are only required

this time

and when updating NanoDroid, new users or users having a factory clean ROM can skip them.

What's new?

fixed a bug in NanoDroid-Overlay

Patcher addon.d no longer conflicts with Magisk addon.d

Replaced Orfox with TorBrowser (auto-migrated)

more

Full ChangeLog since 18.1

## 18.2.20180916

### Bug Fixes

* NanoDroid-Overlay
* fixed a bug that caused GApps Removal and Overlay Creation to fail

### General Changes

* Full package, SetupWizard, CommonInstaller
* switch from Orfox to TorBrowser
* if user opted-in to install Orfox CommonInstaller will auto-migrate setup to TorBrowser

* Patcher
* move addon.d from 999 to 70 (fixes conflicts with Magisk addon.d)

* CommonInstaller
* improve custom Magisk migration code
* install microG DroidGard Helper as user app, aswell

* build-package
* dynamically check whether NanoDroid is correctly populated with APKs prior building packages
* when downloading APKs only updated the indices once per session instead for each individual APK
* drastically reduces time and bandwith required to populate NanoDroid with APKs

### Updates

* automatic
* F-Droid (1.4)
* (Simple) Calendar (4.2.0)
* (Simple) Gallery (4.6.2)
* NewPipe (0.14.1)
* nlpBackend Déjà Vu (1.1.9)
* QKSMS (3.5.3)
* Substratum (1004)

* manual
* microG GmsCore (0.2.5.12879-194-custom)
* Play Store (11.7.11)

* tools
* Dexpatcher (1.6.2)

Download links

Download from Nanolx or AFH.

Bug reporting

In case of errors, please provide

/data/adb/MODID_log_INSTALLDATE

/data/adb/MODID_twrp_INSTALLDATE (TWRP Installation)

logcat (if applicable)
[Magisk] bertino:
The patcher doesn't work for me anymore. After a ROM update, flashing the patcher as usual, takes as long as it usually does, but I don't have sigspoof.hoped the new update would work but it doesnt
[Magisk] Setialpha:
So, there's the log?
[Magisk] bertino:
So I flashed ROM and patcher again to get the log. This time the patcher still took a long time to flash but it gave an error.

https://ufile.io/ckffa
[Magisk] Setialpha:
Ah, it's the addon.d conflict. It's been fixed in 18.2, for new installations, but it does not remove the old addon.d during update.

rename the file /system/addon.d/999-nanodroidpatcher.sh

to /system/addon.d/70-nanodroidpatcher.sh

I'll release a 18.2.1 which gets rid of the 999 addon.d, tomorrow.
[Magisk] Apex Predator:
Flashed 18.2, it removed my GCM registration and I can't re-register it, same was happening on 18.1. Have uninstalled/reinstalled apps, flashed, reflashed ND, uninstalled and flashed. With Fake store only, with play store only. Nothing works. Even tried going back to 17.9 [when everything worked], Gave me constant micro G errors. I give up. Will have to go back to backup i made the other day [before i installed18.1] tomorrow when I have time.

Can I please get a definitive answer to the following, it would be extremely good to know once and for all:

Is it possible to register/use an app with GCM for push messaging with Fake store only installed?

Cheers.
[Magisk] kurtn:
Yes. I've some time manually installed apk s. They registered well.
[Magisk] abacate123:
Did you try to install it through magisk manager or twrp? I also had some similar problems, but while updating through magisk manager, once I tried through twrp again later, all fine.
[Magisk] Apex Predator:
So you definitely got push messages working with Fake store only? Good to know.

I have never tried installing through Magisk manager, only ever through TWRP because I run the install wizard. How does one control what gets installed when going through Magisk?
[Magisk] DoR3M3:
nupd mg still fails with the same message for NanoDroid-microG-18.2.20180916...

Hmm
[Magisk] khnoizer:
I'm going to update, but I have no option such as "uninstall updates" there, just "disable". So, am I good to go?
[Magisk] gadgetguy08:
I had the same error msg.. Reinstalled GsfProxy (went to /system/app and clicked on the apk and install) then did nupd mg again and it worked.
[Magisk] DoR3M3:
This works for me as well, so hopefully this will help Setialpha figure out the problem...

Thanks
[Magisk] bertino:
OK, so I looked in the addon.d folder and found no nanodroid scripts, so I flashed the ROM and the patcher and it looked good, forgot to grab the log and rebooted to the system. No signspoof. So I looked in add-on.d and the script was there with 70- in front so I flashed just the ROM, then the script flashed the patcher as expected, still no sigspoof. Here's the log.
[Magisk] guest4711:
Even when installing through MagiskManager the control file (/sdcard/.nanodroid-setup) is respected. So why not update through MM?

(For me it is easier to edit this file using my standard ASCII edit than to fiddle with Aroma or any other generator.)
[Magisk] Setialpha:
No, don't disable it, it's fine, nothing to do.
[Magisk] Setialpha:
Your setup is messed up somehow anyway, while the patcher targets Magisk, the microG package targets /system. Wait for 18.2.1.
[Magisk] Setialpha:
Did you follow the steps from the update notes of 18.2?
[Magisk] DoR3M3:
Hi, I wiped the phone and started all over from scratch, I didn't do this as an update.

1. Wiped

2. Flashed stock Oreo

3. Deodex

4. Flashed Patcher

4. Flashed microg

So I'm assuming from a clean start, this should of worked...

Hmm
[Magisk] Setialpha:
Hmm, dunno, working fine here, though I never used a Stock ROM. What's the find.log I requested a few pages back?
[Magisk] HemanthJabalpuri:
Sir I tested the latest version of microG in my device running on Stock 4.4.2 kitkat...

The problem from https://xdaforums.com/apps/magisk/module-nanomod-5-0-20170405-microg-t3584928/post77442795 is still there...

Can you please suggest a alternate working microG package....

when I flashed ale5000 's microG installer the problem is this https://xdaforums.com/android/development/microg-unofficial-installer-t3432360/post77518251
[Magisk] DoR3M3:
I'm assuming you meant this? find /system /data/{app,data,misc*,system*} > /sdcard/find.txt

The log is to big, I had to attach it.

Thanks
[Magisk] smigima:
unifiednlp do not have location to test geocoder

Hi, thanks for your work.

I've flashed NanoDroid-patcher-18.2.20180916.zip and then NanoDroid-microG-18.2.20180916.zip

On my LineageOS 16.0 (Android 9).

Signature spoofing is working! So thanks a lot, but the last checkbox (unifiednlp do not have location to test geocoder) is unchecked...

Do you have any solution for this problem? I've configured and grant perrsmissions to Apple and DejaVu I have unifiednlp and location enabled.

I would really appreciate any help.
[Magisk] Oswald Boelcke:
Besides the unchecked tick-mark, do your applications that use localisation provide a position in energy saving mode assuming they do in GPS mode.
[Magisk] smigima:
Unfortunately I can't turn on power-saving mode on GPS in Android 9 - it's only binary switch for location on or off.

But it doesn't really matters, because OsmAnd app doesn't work as well - it is saying that my location is not known :(

I was trying to override apps from nanodroid with these from F-Droid, but installlation failed, i assume due to missmacthed signature.

Any other thoughts? :)

edit: after ~10min it shows me my location, but I don;t know if it's from GPS or MicroG
[Magisk] Oswald Boelcke:
Try an application like SatStat (available on F-Droid); it'll show your both even on map to compare the retrieved locations. Additionally, you can update AGPS data.
[Magisk] smigima:
Thanks for reply! :)

Map shows nothing but light blue colour.

Under first - GPS - section I have "Satelites" with 0/19, which doesn't sounds good

And in this "cellural" section I have 2 LTE cells with some ID numbers.

Does it mean that my network location is working but GPS dosen't? That would be interesting twist :eek:

---------- Post added at 12:35 PM ---------- Previous post was at 12:05 PM ----------

So I was inside, when I went outside SatStat shows me location, but only from GPS.

In conclusion my GPS is working, microG with network location isn't
[Magisk] Oswald Boelcke:
I'm convinced your conclusion is correct that your GPS is working (as it also doesn't depend on µG) but network localisation isn't (yet).

We definitely have the problem of different ROMs - you're on Pie, I'm still on Nougat, and I don't know Pie at all and how µG collaborates with it i.e. I won't personally exclude a ROM issue. However, having been a very short period on Oreo before I reverted, the last two boxes in the µG self-check weren't ticked but localisation worked.

Just for completeness, I attached screenshots of my SatStat to show (at the last SS) how it differenciates between GPS and network locations. One of its useful features is also to update the AGPS data, which will speed up the position fixes.

Maybe an issue are the location backends you use. I remember pretty well that I'd always issues with Apple, and for a long while I'm using the ones as shown on the screenshot. Besides DéjàVu, the other two are also by @n76 and available on F-Droid. Please be aware that it takes quite a while to download the database for GSM Location Service (I personally use as database source the Mozilla Location Services filtered to my country), and I suggest to only download via WiFi. In case of issue with the backends, I know that n76 monitors this thread.