[MODULE/SYSTEM] NanoDroid 23.1.2.20210117 (microG, pseudo-debloat, F-Droid + apps)

[Setialpha]

I'vd uploaded version 20.3a of the Setup Wizard. Fixes selcetion for uNlp Backends not properly created.

 

[d0s1s]

Oh, I see, haven't yet tested anything, so it's safe to update, yay! Edit: DroidGuard Helper alone is enough, GmsCore is always on the hide list. Will add this to the issues list.

In my case, I fixed this situation with two steps:

1 - Using Magisk Hide for DroidGuard (this causes DroidGuard crash).
2 - To fix the crash... running like root --> pm install -r /system/app/DroidGuard/DroidGuard.apk`

SaffetyNet passes on latest nanodroid-microg build on OmniRom for OnePlus 6 and Magisk v18.0.

Regards

 

[NamitNayan]

In my case, I fixed this situation with two steps:

1 - Using Magisk Hide for DroidGuard (this causes DroidGuard crash).
2 - To fix the crash... running like root --> pm install -r /system/app/DroidGuard/DroidGuard.apk`

You can simply install apk like any other app in case 2.
It fixed for me.

 

[Apex Predator]

I'vd uploaded version 20.3a of the Setup Wizard. Fixes selcetion for uNlp Backends not properly created.

I was just coming into the thread to post about the Mozilla back end not being installed despite being selected in the installer. Glad to see you've fixed it.

 

[alecthenice]

Will this work on a device that has both android 5.1 sdk and an aditional moverio sdk? I want to install the magisk module so that i can use the backend of the google play enviroment. Is deoxing the rom all that is needed for compatability of devices among all devices within the specified supported sdks? I ask because my thread of like 6 on this device only includes amateurs. I have magisk and a twrp that is modified to suit my device I havent flashed it yet though because it requires a mouse to use. It should probably be flashed?

 

[iacchi]

It's the same path, because the system app has been replaced with the new one. You can simply remove the old one, as it's normally a user app (update).

Hi Setialpha, that's the point: I can't. Both the old Simple Gallery and Yalp (I've switched to Aurora) are still considered system apps and the uninstall option is not there. The same thing didn't happen with Simple Calendar (I just decided that I didn't need it anymore, so I removed it from .nanodroid-apps), where after the update it was switched to a user app and so I was able to remove it.

 

[forjustin]

Hi Setialpha, that's the point: I can't. Both the old Simple Gallery and Yalp (I've switched to Aurora) are still considered system apps and the uninstall option is not there. The same thing didn't happen with Simple Calendar (I just decided that I didn't need it anymore, so I removed it from .nanodroid-apps), where after the update it was switched to a user app and so I was able to remove it.

Use root Toolcase app from xda.

 

[derders]

@Setialpha

google play support libraries updates often a day at the moment... isn`t the fix to update microg version number to a higher one?

I am on latest updates of your microg that comes via fdroid (repo)
0.2.6.14797-dirty-113

 

[Oswald Boelcke]

@Setialpha: Unable to confirm @derders observation. Also on µG Services Core v0.2.6.14797-dirty-113 (via F-Droid) and zero attempts of updates of the Google Play Support libs. Maybe it differs from device to device and/or overall system setup and configuration?

 

[raptorddd]

@Setialpha

google play support libraries updates often a day at the moment... isn`t the fix to update microg version number to a higher one?

I am on latest updates of your microg that comes via fdroid (repo)
0.2.6.14797-dirty-113

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

 

[Setialpha]

Uploaded new Play Store and microG builds.

 

[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.

 

[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

Sent from my SHT-W09 using XDA Labs

>>>>>>>>>> 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. <<<<<<<<<<<<

 

[Kelvino9]

Uploaded new Play Store and microG builds.

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?

 

[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

 

[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.

 

[jenslody]

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?

I don't use Nanodroid as flashable zip, just the Nanodroid F-Droid repo and never had any issues updating the apps.

 

[Setialpha]

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

Read the Issues section. Issue already listed and happens with Magisk 18.0 or newer.

 

[Setialpha]

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:


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.

There's the log?

 

[Setialpha]

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?

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?