yashsingh1/xdaforums huggingface dataset:
[Magisk] Apex Predator:
I finally updated from v18.3.1 to v20.2. On the earlier version if you had Fakestore only installed, it would be automatically overwritten by the full play store in f-droid unless you manually flagged it to ignore all updates.

Thus was supposedly fixed with newer versions of NanoDroid but now that I've updated, I unticked ignore updates for Fakestore in F-Droid and it tried to update to full playstore again.

Any ideas? How often is Fakestore updated anyway? I guess leaving ignore updates ticked is probably no big deal.

Edit: I found this post by [MENTION=4187311]Setialpha[/MENTION] that I remembered from when the issue first occurred -
[Magisk] iacchi:
I was in your same situation at the beginning, but after I installed 18.3.2 the problem disappeared, and I never had to flag anything in F-Droid. Now I'm on 20.1 and the issue is still fixed for me.
[Magisk] Apex Predator:
Hmmm... I wonder why the fix hasn't worked for me. I mean I know I made a big version jump, but I had hoped the fix would propagate across.

Let's see what Setialpha has to say.
[Magisk] iacchi:
Wait a minute, I double checked and I take back what I just said. You have to keep play store updates disabled in f-droid. What the fix in 18.3.2 did was to restore fakestore over play store without any further action on my part. I guess if you disable play store updates and just reinstall the latest version of nanodroid you will find yourself with fakestore again.
[Magisk] h_maharaj:
[MENTION=4187311]Setialpha[/MENTION]

I managed to solve the SafetyNet issue. It seems that the problem on this ROM was having DroidGuard Helper in priv-app.

I uninstalled updates for DroidGuard Helper and then moved the DroidGuard folder from /sbin/.core/img/NanoDroid_microG/system/priv-app over to sd card and rebooted.

I installed DroidGuard Helper from Fdroid. As a user app only, it was no longer crashing but only Basic Integrity was passing. I then moved the DroidGuard folder from sd card to /sbin/.core/img/NanoDroid_microG/system/app and rebooted.

SafetyNet can be queried now without any crashing and both Basic Integrity and CTS pass. However as soon as DroidGuard Helper is placed in priv-app, it starts to crash again but works perfectly in /system/app.
[Magisk] Apex Predator:
Ah OK. No need for me to do any reinstalling as I stopped the play store update before it could complete so Fakestore is still intact. Then I flagged it to ignore updates straight away.
[Magisk] Lithesis:
I was considering whether should I post it since I don't have any log (no more) but maybe it'll be useful.

So I was trying to install NanoDroid past ~5 hours and sadly no luck.

The is something wrong with UnifiedNIp since I kept having two problems with regardless of how I was installing. It says it doesn't has last known location therefore some apps which use location might have a problem and it doesn't have Location for Geotester, please check location backend. Of course Google Maps didn't work properly.

What I did:

Device is Poco F1 and was on MIUI Oreo (8. something)

- wiped cache, dalvik, system, data and internal

- flashed LOS latest build for Poco

- flashed Magisk

- flashed Kernel

while still in TWRP I deodexed services.jar according to https://gitlab.com/Nanolx/NanoDroid/blob/master/doc/DeodexServices.md with http://vdex2dex.com (services.vdex with checkbox checked), installed in on device and set required permissions

- flashed NanoDroid Patcher

- flashed NanoDroid Full with custom .nanodroid-apps and .nanodroid-setup (most of the apps didn't install cause of '<NameOfApp>[] missing' - the '[]' might be missing character, maybe array symbol dunno)

- rebooted

As in the opening of this post location wasn't working. In MicroG self check everywhere I had green checkboxes. Location was on, permissions were there, backends were set but no dice.

Repeated that sequence many times - also with default .nanodroid-apps and .nanodroid-setup but still location wasn't working. I might try with new version again but no promises.

.nanodroid-setup

nanodroid_microg=1
nanodroid_gmscore=0
nanodroid_fdroid=1
nanodroid_apps=1
nanodroid_play=1
nanodroid_overlay=1
nanodroid_zelda=0
nanodroid_mapsv1=1
nanodroid_init=1
nanodroid_gsync=1
nanodroid_swipe=1
nanodroid_forcesystem=0
nanodroid_nlpbackend=3
nanodroid_nano=1
nanodroid_bash=1
nanodroid_utils=1
nanodroid_fonts=0
nanodroid_override=0

.nanodroid-apps

AnySoftKeyboard
Blokada
OmniClock
OmniJAWS
OpenCamera
OpenKeyChain
OpenLauncher
OpenWeatherMapProvider
OpenVPN
Orbot
QKSMS
Substratum
Termux
YahooWeatherProvider
[Magisk] HyperCriSiS:
Since some versions Playstore does not install amymore. If I install it manually and update Nanodroid later it even gets deinstalled. What clould I done wrong?
[Magisk] friedCELLS:
1. I keep getting the error seen in screenshot when trying to update gms core. Would deleting gms core in root explorer, then installing updated version in F-Droid solve this?

2. I keep seeing people updating from 1 version of Nanodroid to another. Why would this be necessary? Don't most components of Nanodroid update anyways in F-Droid? It took me about a week of working on this to get it working on stock rooted Rom, so I'm totally paranoid of flashing anything and screwing it up. I know that I can just do a TWRP backup before flashing anything but I've even had those restores fail to restore boot partition correctly and not boot. So I never feel completely safe with changing things.
[Magisk] Lithesis:
Again wiped everything

- flashed NanoDriod-microG

- trying to flash Bromite

******************************
Powered by Magisk (@topjohnwu)
******************************

> setup Magisk environment
- Found /data/adb/magisk.img
e2fsck 1.43.3 (04-Sep-2016)
I:Found no matching fstab entry for uevent device '/devices/virtual/block/loop7' - change
- Resizing /data/adb/magisk.img to 320M
I:Found no matching fstab entry for uevent device '/devices/virtual/block/loop7' - change
e2fsck 1.43.3 (04-Sep-2016)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/data/adb/magisk.img: 88/28672 files (1.1% non-contiguous), 10354/16384 blocks
resize2fs 1.43.3 (04-Sep-2016)
Please run 'e2fsck -f /data/adb/magisk.img' first.

Resize /data/adb/magisk.img to 320M
e2fsck 1.43.3 (04-Sep-2016)
I:Found no matching fstab entry for uevent device '/devices/virtual/block/loop7' - change
- Mount /data/adb/magisk.img to /dev/tmp/magisk_img
<< with Bromite WebView
creating overlay for webview
installing app: BromiteWebView_arm64
cp: write error: No space left on device
!!
failed to install /dev/tmp/install/system/app/BromiteWebView_arm64/BromiteWebView_arm64.apk to /dev/tmp/magisk_img/NanoDroid_BromiteWebView/system/app/BromiteWebView
!!
- Unmounting partitions
I:Found no matching fstab entry for uevent device '/devices/virtual/block/loop7' - change
__bionic_open_tzdata: couldn't find any tzdata when looking for CST6CDT,M3.2.0,M11.1.0!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
cat: can't open '/dev/tmp/install/.nanodroid-overlay': No such file or directory

cp: write error: No space left on device

like, really?

Edit:

Reinstalled everything (aka full wipe and flash again) 5 times, everytime Bromite fails to install, location is not working and can't open play store cause it crashes... (microG package, bromite, fdroid)
[Magisk] ydd0ras:
I have a p0c0 too. With Multirom. My primary ROM is LOS as well. I have the NanoDroid microG and the patcher 20.1 flashed. My location, GPS is perfect. Also I had a complete debloated MIUI 10 (Xiaomi.eu) as secondary. Have installed the same NanoDroid combo. Location has been working perfectly as well.
[Magisk] Lithesis:
How did you deodex services.jar for the patcher? I tried MSM Extended ROM which has spoofing enabled by default but same issues there.

Edit: Wait you flashed 20.1, I was using 20.2 - maybe that's the problem :confused:
[Magisk] HyperCriSiS:
I found the issue. Somehow phonesky and location backends got appended to overlay config. I did not add it... Location backends still were installed.

But I have another issue. When installing new Nanodroid version all set app permissions are reset.
[Magisk] Lithesis:
So I flashed 20.1 patcher, microG and fdriod packages. Playstore doesn't crash, everything is configured properly but still location doesn't work. Google Maps and AndOsm~ can't find my position and Maps doesn't even load street map, only shows terrain map if I zoom out far enough. It looks like Pie issue according to posts https://github.com/microg/android_packages_apps_UnifiedNlp/issues/164 and https://github.com/microg/android_packages_apps_UnifiedNlp/issues/167 but why for some it does work :confused:?

Anyway attached logs from installation and logcat.
[Magisk] tom.android:
update fail "microG Services Core" please advice.....

from Nanodroid 20.2

------

I'v founded the solution. by disable ----Fdroid--->expert mode--->check out privileged Extension.
[Magisk] kurtn:
Add nanodroid repo
[Magisk] bege10:
Play Store updates automatically

For a week or two now Play Store updates apps automatically without notice (sometimes all new updates, sometimes just one or two leaving the rest) although I have not altered the settings to not update automatically and to notify about updates.

Nanodroid 20.2.20181122, current updates via F-Droid (Play Store 12.6.13)

Samsung Galaxy S5 Plus (SM-G901F), LineageOS 15.1 (Android 8.1)

Edit:

I found a solution:

First version of Nanodroid I had installed was 18. In self check it said that the ROM doesn't support spoofing but spoofing was enabled. Everything worked fine.

Meanwhile I have installed Nanodroid 20. Now I saw that self check has changed. Now it says that ROM supports spoofing, spoofing is enabled but a permission is missing. As I clicked on that new entry I was asked to permit spoofing, now all boxes in self check are checked and Play Store notified me about a new update without installing it automatically. Everything seems to be back as it shall be.
[Magisk] Setialpha:
Ask Google.
[Magisk] Setialpha:
Will be changed in 20.3
[Magisk] Setialpha:
Does location work with patcher 20.1? The space refers to magisk.img, which is a loop back device, not your physucal device.

For the crashes obviously logs are required.
[Magisk] Lithesis:
https://xdaforums.com/showpost.php?p=78253842&postcount=4854
[Magisk] Setialpha:
Dunno where the [] is coming from, but likely due to your configuration file being badly formatted, remove it and re-create it.
[Magisk] Setialpha:
Play Store and Fake Store have the same package name, but different signatures, thus an update is not possible.

F-Droid will detect the mismatching signature and won't allow updating (which would fail anyway). If it still does, it's a bug in F-Droid.

What I fixed, was that both had the same signature, so users with Fake Store ended up with Play Store unintendetly.
[Magisk] Setialpha:
Will be changed with 20.3
[Magisk] Setialpha:
You don't use the uninstaller before flashing a new version, do you?

Else I don't know why app permissions are reset, as the only code that does so, is the GApps removal mechanism, that's only triggered on fresh installations, but not on updates.

Using the uninstaller first obviously results in a fresh install, not an update.

Ah, sorry, I see you already tried with 20.1, ignore my previous post.

Did you try the possible solution in issue 164 linked in your post? Else you may try a different ROM to check whether it's not a ROM issue.

I'll check the logs soon.
[Magisk] Setialpha:
Will check, thanks.
[Magisk] Lithesis:
Yes, few time after reflashing via Termux and adb but that didn't change anything. I've actually tried it on other ROM - MSM Extented which supports sig spoofing by default, but that again didn't help.

I've switched to GAPPS for now as I need maps to work but i'll probably try new version if it comes out next weekend.

Thanks for checking logs, let me know if you find anything :)
[Magisk] Setialpha:
Maps is known to currently not properly work, regardless of unlp, but normally OsmAnd should work - when unlp does.
[Magisk] Apex Predator:
Must be an F-Droid bug then because after the install when I opened F-Droid and refreshed the repositories I saw play store start downloading an update of something like 26MB. I clicked the X to stop it immediately so I can't be sure if it would've completed successfully and put full PS in place.

In fine with leaving Fakestore flagged to ignore updates. How often do you update it anyway? It has no real functionality except to "pretend" so i gather it doesn't need much development. Any new versions will go into the full package anyway so I guess it's no big deal to not get them OTA.

The only thing I'd suggest is to add a note to your documentation about the F-Droid bug and tell users that install Fakestore that they will have to manually flag it to ignore updates or risk having it replaced by the full play store.
[Magisk] Klizi:
Finally it started working again with havoc after flashing with recovery.

Thanks to the Dev for fixing havoc incompatible bugs.

I really miss flashing this as a Magisk module

Edit: after latest update snapchat stopped working
[Magisk] Klizi:
Installed this after flashing fdroid zip and upgraded microg through fdroid

Anyone spot the problem?
[Magisk] kurtn:
I think, I have seen some permissions missing after update from nanodroid repo.
[Magisk] xaruseus:
I installed Unofficial LineageOS 15.1 on my SM-J530F(J5 2017), nanoDroid(microG) and Magisk thru TWRP. Phone works fine and I don't even need/use Play services, but microG tells me in Self-Check that it does not pass sig spoofing for system, play services and play store. Do I need to fix those three sigs to pass because of security reasons or is it ok without? I know I should deodex services.jar as it says on nanoDroid Gitlab DeodoxServices(can't post outside links) before installing Magisk and nanoDroid if I understand correctly.

What is the "best" way to deodex services.jar?

1. Do a fresh installation of the LineageOS and first manually deodex services.jar and than install Magisk and NanoDroid or,

2. install on a current system Xposed framework as a Magisk module and see if sig spoofing will work?

Has anyone tried anyting like that?

Thank you and I'm sorry if this was already answered.
[Magisk] kurtn:
If you don't need play services you most probably do not need microG. Have you tried pure lineageOS with f-droid?

If some apps refuses to work because play services are missing: flash nanodroid patcher. Deodexing Oreo is done by patcher.
[Magisk] xaruseus:
I did not try pure LineageOS without microG/Gapps(I tought of it), because I did not know till what extend I need play services on a smart phone. I'm very newbie about customizing anything on my phone(my first install of a custom ROM, ever). I'm learning fast, but still overwhelming and alot to learn... I see it is mainly of try and error thing with custom ROMs, etc.
[Magisk] bege10:
I just had to run the separate NanoDroid patcher on LineageOS 15.1 after installing NanoDroid to have both, services.jar patched and spoofing enabled in selfcheck.
[Magisk] elraffa:
I can't update microg through f-droid, it shows screen shoot error, Does anyone know a workaround to update microg? I have installed nanodroid 20.2. Also in magisk I always get "safetynet API error" even if I have a good WiFi signal.

Enviado desde mi ALE-L23 mediante Tapatalk
[Magisk] tom.android:
Fdroid--Setting---Expert mode----->Enable it and then disable---> privileged Extension
[Magisk] elraffa:
thanks for response. I tried your steps but when is installing trough system package installer, it shows "fail to install, unknown error". what could I do?

Enviado desde mi ALE-L23 mediante Tapatalk
[Magisk] DoR3M3:
Thanks, keep up the great work, looks busy around here too...
[Magisk] OrcaXS:
My GCM registered app list got wiped after updating from 20181112 to 20181122, is it normal?

Do I have to re-register apps to GCM every time after updating?
[Magisk] Apex Predator:
It's not normal after a dirty flash and usually you don't have to re-register them. However, since this has occurred, you will need to uninstall then reinstall them in order for them to re-register. If they have data associated you can back them up in Titanium backup then after reinstallation just restore the data component.
[Magisk] Shobit Joura:
Any solution yet ????

I have been waiting for so long , devs plzz help....
[Magisk] Setialpha:
Nope, some ROMs currently cause issues and users already reported similar issues upstream.
[Magisk] elraffa:
[MENTION=4187311]Setialpha[/MENTION] could you help me to update microg?

Enviado desde mi ALE-L23 mediante Tapatalk
[Magisk] tom.android:
Try to install nanodroid with system mode if magisk mode not working for you.
[Magisk] elraffa:
nanodroid magisk mode works fine, the only problem is that I can't update microg trough f-droid and in magisk I get safetynet API error. thanks for your help :)

Enviado desde mi ALE-L23 mediante Tapatalk
[Magisk] guest4711:
Did you add NanoDroid repo to f-droid (https://nanolx.org/fdroid/repo/)?

Otherwise f-droid offers versions signed using another key (so you cannot use them for updating).
[Magisk] elraffa:
I have these repo in f-droid (screenshot), Do I have to add something else?

Enviado desde mi ALE-L23 mediante Tapatalk
[Magisk] guest4711:
No, that should be enough.
[Magisk] evilvoice:
[MENTION=4187311]Setialpha[/MENTION] I posted earlier about BromiteWebView not working (I think, or I meant to and ended up asking a different question about it). I finally figured everything out about the issue. This will pertain to others who've done the same thing as me. I've taken a stock Samsung ROM and hand removed everything Google (apps, framework, libs) that didn't break the phone. Removing them gives you a sense of not having Google installed, even though some things have been hard-coded by the manufacturer. I don't know if you're going to be able to do this, but this is what I did.

First, your package only searches for Android webview (which it should since it's going to be tough to replace Google webview as listed below). Google's webview obviously uses Google in the name (WebViewGoogle, com.google.android.webview). Maybe update the package to search for both?

Second, the app that tells the system what webview to use is framework-res.apk. I don't know if it can be changed without editing the strings and repackaging the app, or if there is a sql database edit that can be done. I changed mine to com.android.webview and Bromite works.

Side note: is it possible to build Bromite so it's package name is com.google.android.webview? I know they talk about changing the package name in the wiki but don't remember if there was a reason unless their webview heavily relies on it having the default package name.

I'm probably the only one asking for the update to cover this, so you may not want to worry about it. I've made my changes and done what needed to be done for me. Now that I realize things like that are hard-coded, I need to look deeper into removing things than just deleting the files.
[Magisk] Setialpha:
The next release will look for that packages aswell, though I'm not 100 % sure whether it'll work out, as you already pointed out it may be hard-coded in framework-res.apk. It would be possible to change the package name for Bromite WebView, but only with a new build, though I don't know how much the source recycles the package name for API calls.
[Magisk] Setialpha:
20.2a

Hi all,

the Full and microG packages have been re-uploaded as 20.2a, fixing the missing nanodroid_gmscore value in the fallback setup, causing to install official microG GmsCore instead of NanoDroid's custom version,

for users that don't have their own setup file.
[Magisk] fink.nottle:
Did something change in droid guard ? Last time I had tried droid-guard, I had to make it a priv-app in an AOSP build. What needs to be done to make it work without priv-app ?
[Magisk] lukasss_98:
hi, for some reason i cant download this module, after 5 seconds the speed starts to fall down quickly to a full stop, i've tried downloading it with jdownloader, and from the opera and chrome browsers with or without a vpn and still not able to finish a download, does anyone have a mirror for the NanoDroid-20.2a.20181122.zip file?
[Magisk] Tomatot-:
Hi, I'm interested in your NanoDroid-microG module.

My TWRP doesn't support AROMA installer. Is that alright? What files should I modify if I want to choose a few options, like the store I want for example, or location provider backend?

Also, do you know if there's a way to know what apps use GCM? Because I'm using Titanium Backup and I guess for these apps using GCM it's either to clean install them.

EDIT: with greenify it's possible to see what apps use GCM. There are actually so many, even when they shouldn't use it. But for most of them I don't need to have instant notifications.
[Magisk] ydd0ras:
Hello guys, I am using NanoDroid on all devices for a long time. Today I have installed a new P ROM on my cancro, but can't connect to Google Servers. This is not a NanoDroid, but a ROM issue. Thus maybe someone have an idea, where I can find the issue? Maybe someone had the same issue. Thx!
[Magisk] ydd0ras:
I mean this
[Magisk] Oswald Boelcke:
The OP provides a link to the full documentation in bold letters that eventually leads you to this: https://gitlab.com/Nanolx/NanoDroid/blob/master/doc/AlterInstallation.md
[Magisk] Tomatot-:
Thank you. Sorry I got confused, I checked all this file: https://gitlab.com/Nanolx/NanoDroid/blob/master/README.md#microg-1 but couldn't find what I wanted. Doesn't matter anyway. :)

---------- Post added at 00:46 ---------- Previous post was at 00:32 ----------

Do you have any idea what is the origin of this error? "twrp updater process ended with error 2"

https://i.imgur.com/JGhSaKO.png

Info:

OnePlus 6

Omnirom official Pie

Magisk installed

.nanodroid-setup

nanodroid_gmscore=1

nanodroid_play=(2 1)

nanodroid_overlay=0

nanodroid_mapsv1=1

nanodroid_gsync=0

nanodroid_swipe=0

nanodroid_forcesystem=0

nanodroid_nlpbackend=(1 1 0)

Could I be doing something wrong?
[Magisk] Oswald Boelcke:
The link you provided was regarding signature spoofing and not about the setup wizard and the file .nanodroid-setup and its modifications.

Anyhow, I#ve no experiences with Pie and don't know if the issue is related to the ROM but I doubt. After a glance into your TWRP log I believe it's a bad .nanodroid-setup file. If the file contains the values you posted above then the lines about "play" and "nlpbackend" are corrupted; only one digit is allowed behind the "=" and must be iaw. here.

Just as an example I added "my" setup file (please note that I added the suffix to the file name to allow for upload to XDA).
[Magisk] Tomatot-:
Yeah, I meant this link: https://gitlab.com/Nanolx/NanoDroid/blob/master/doc/AlterInstallation.md#detailed-description . It doesn't matter.

Thank you for your help, again. I get what you mean however it seems for these two lines you can put several numbers, like it's explained here for example: https://i.imgur.com/15yqcs8.png

But maybe I should write it this way:

nanodroid_play=2 1

insteaf of:

nanodroid_play=[2][1]

I will try and let you know.

EDIT: yep it worked like that! Great, thanks again.