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

[Setialpha]

I mean this View attachment 4654586

Sent from my Poco F1 using XDA-Developers Legacy app

Nope, I don't know, but it has been reported upstream, aswell. See: https://github.com/microg/android_packages_apps_GmsCore/issues/666 You may post a logcat there.

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.

Inside each zip is the fallback configuration file, you can extract it and modify it, then save it in either

a) /sdcard/
b) /data
c) the same directory as the zip file

As mentioned in the 20.3 beta announcement post the syntax for two variables changed with the beta, so for further advice I need to know which one you use (stable or beta).

Also if the doc say: nanodroid_something=[0|1] then it means you have the following choices

a) nanodroid_something=0
b) nanodroid_something=1

for on-off variables 0 = disabled, 1 = enabled, else the meaning is further described in the docs. If the docs (for the beta) say: nanodroid_something=[0|1][0|1] then it means you have the following choices

a) nanodroid_something=00
b) nanodroid_something=10
c) nanodroid_something=01
d) nanodroid_something=11

where each element (digit) as it's own meaning, which is further described in the docs, so what you posted nanodroid_something=2 1 will be nanodroid_something=2 (everything past be space is ditched).

Again depends on whether you're going to use the beta or stable.

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?

No problem here downloading from Nanolx, AFH recently often has slow mirrors.

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 ?

Works here as system/app + user-app (udpate), but fails for some as priv-app.

 

[Tomatot-]

Nope, I don't know, but it has been reported upstream, aswell. See: https://github.com/microg/android_packages_apps_GmsCore/issues/666 You may post a logcat there.



Inside each zip is the fallback configuration file, you can extract it and modify it, then save it in either

a) /sdcard/
b) /data
c) the same directory as the zip file

As mentioned in the 20.3 beta announcement post the syntax for two variables changed with the beta, so for further advice I need to know which one you use (stable or beta).

Also if the doc say: nanodroid_something=[0|1] then it means you have the following choices

a) nanodroid_something=0
b) nanodroid_something=1

for on-off variables 0 = disabled, 1 = enabled, else the meaning is further described in the docs. If the docs (for the beta) say: nanodroid_something=[0|1][0|1] then it means you have the following choices

a) nanodroid_something=00
b) nanodroid_something=10
c) nanodroid_something=01
d) nanodroid_something=11

where each element (digit) as it's own meaning, which is further described in the docs, so what you posted nanodroid_something=2 1 will be nanodroid_something=2 (everything past be space is ditched).

Again depends on whether you're going to use the beta or stable.



No problem here downloading from Nanolx, AFH recently often has slow mirrors.



Works here as system/app + user-app (udpate), but fails for some as priv-app.

Thank you so much for your detailed explanation.

 

[Tomatot-]

So I'm using this installer: NanoDroid-microG-20.2a.20181122.zip

Here is my config:

nanodroid_gmscore=1
nanodroid_play=21
nanodroid_overlay=0
nanodroid_mapsv1=1
nanodroid_gsync=0
nanodroid_swipe=0
nanodroid_forcesystem=0
nanodroid_nlpbackend=110

Is there something wrong in it?
I've run the uninstaller, then the installer with this config, and it seems to ignore the lines where I put two numbers:
-I don't have a store nor YALP
-I don't have any of the nanodroid_nlpbackend

Is there something I'm doing wrong? Or does the template work for the beta now?

Thank you for your time...

 

[NamitNayan]

So I'm using this installer: NanoDroid-microG-20.2a.20181122.zip

Here is my config:



Is there something I'm doing wrong? Or does the template work for the beta now?

Thank you for your time...

that config is for beta version.
stable will use older way I guess.

 

[Tomatot-]

that config is for beta version.
stable will use older way I guess.

Yeah I figured this out. But then what's the old syntax way?

Also, I tried the same config with beta but it makes my phone bootloop. :/


EDIT : ok I managed to find the history of the file and so now I should have the right syntax. Thanks anyway.

 

[silkshadow]

Just wanted to report a possible bug/incompatibility with this and Lastpass. To note I don't use Lastpass as my password manager (untrustworthy and garbage company since it got bought) but one of my clients uses it so I have to.

On Note 9 LineageOS 15.1, I flashed Magisk, Nanodroid, and Xposed. Set it up and played with it for 2 days and discovered that Lastpass crashes ( "Lastpass has stopped" error) right after opening. Besides having to force stop and wipe the Play store every couple times it gets opened, Nanodroid was performing great (love it).

Tried AICP (android 8.1), flashed Magik, Nanodroid, and Xposed. Setup quickly, went online downloaded Lastpass first thing and it also crashes right after opening, same as on LOS.

I've now tried both LOS and ACIP but flashed ROM, Magisk, Opengapps and Xposed instead just to see if that was the issue. Lastpass works fine with both ROMs in this scenario. Far from conclusive, but it does point to a possible incompatibility. I'm, sticking with Nanodroid and just using Lastpass in Firefox for now.

 

[Tomatot-]

It's weird
That's my current setup with the last stable:

0) Wipe data.
1) Flash ROM
2) Flash recovery (normal A/B procedure)
3) Reboot recovery
4) Flash NanoDroid-microG-20.2a.20181122

nanodroid_gmscore=0
nanodroid_play=4
nanodroid_overlay=0
nanodroid_mapsv1=1
nanodroid_gsync=0
nanodroid_swipe=0
nanodroid_forcesystem=0
nanodroid_nlpbackend=3
nanodroid_nlpbackend=3

I've also tried

nanodroid_forcesystem=1

and it seems the script doesn't work well with Magisk. If Magisk is installed, my device boots. If the nanodroid is installed, my phone boots. But if I install both I get a bootloop. Any idea?

EDIT: more information:
So I've tried this setup:

nanodroid_gmscore=0
nanodroid_play=4
nanodroid_overlay=1
nanodroid_mapsv1=1
nanodroid_gsync=0
nanodroid_swipe=0
nanodroid_forcesystem=1
nanodroid_nlpbackend=3

Here is what shows on my screen: https://i.imgur.com/rvpR8U0.png

See in attachemnt the logs.

If I open the setup file again, that's how it looks:

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

When I reboot, sometimes i just go back to TWRP (like at the time I'm writing), sometimes I have a bootloop, and once I booted but I didn't have any of the apps installed.

EDIT 2: using the beta nanodroid leads to the same result: I just boot to TWRP.

I don't even know how I managed in the first place to make it work, when it wasn't even written properly lol.

 

[thoiloidainhan]

Have u had a chance to look into the discord issue, sir @Setialpha ?

 

[the.D]

Have u had a chance to look into the discord issue, sir @Setialpha ?

Discord works fine here. If you're using NetGuard that's what's causing the issue.

 

[LovepreetSinghGill]

Have u had a chance to look into the discord issue, sir @Setialpha ?

Mine also does not work

 

[bege10]

a beta release for 20.3 (internal version number 20.2.90) is now available.

• move DroidGuard Helper from priv-app to app

Can this version be flashed over 20.1 or do I need to uninstall first?

With the F-Droid repo active and no apps from the NanoDroid package installed, do I need to install every full NanoDroid version or is updating via F-Droid enough?

 

[Apex Predator]

Can this version be flashed over 20.1 or do I need to uninstall first?

With the F-Droid repo active and no apps from the NanoDroid package installed, do I need to install every full NanoDroid version or is updating via F-Droid enough?

You can flash over old versions, no need to uninstall.

Technically you can just keep using F-Droid for package updates (microG etc), that's what I've been doing. I do use apps from NanoDroid, but they also update via F-Droid.

The change in your quote for example wouldn't be applied with an F-Droid update though. You'd have to move it manually, probably easier to just flash the whole package, less messy.

When there's a big update/something new/flashing a ROM update, I'll get the full package, as was the case last week.

 

[bege10]

You can flash over old versions, no need to uninstall.

Thank you for answer. DroidGard Helper is moved by flashing the new version over the old one?

 

[demonoidmaster]

Thank you for answer. DroidGard Helper is moved by flashing the new version over the old one?

If the only thing changing is that app moving from priv-app to app, flash it and see if it's present in the new folder, then go look in priv-app and if it's still there too just delete the droidguardhelper folder

Or, manually move the droidguard helper folder from /system/priv-app to /system/app first then flash the zip

 

[thoiloidainhan]

Discord works fine here. If you're using NetGuard that's what's causing the issue.

Is netguard an adblocker? Im not using it. Been with adaway for a long time. I disabled adaway just in case too and discord still wouldnt connect, keep spinning

 

[Tomatot-]

Is netguard an adblocker? Im not using it. Been with adaway for a long time. I disabled adaway just in case too and discord still wouldnt connect, keep spinning

No it's a firewall.

 

[thoiloidainhan]

No it's a firewall.

Nope. Its definitely microg fault. But in trying to pinpoint the issue i found a partial solution. Disable microg, restart discord then enable microg again. Discord will work from that point on but i will have connection issue again if i restart discord

 

[Tomatot-]

Nope. Its definitely microg fault. But in trying to pinpoint the issue i found a partial solution. Disable microg, restart discord then enable microg again. Discord will work from that point on but i will have connection issue again if i restart discord

I meant netguard is not a adblocker, it's a firewall, that's all. :good:

 

[LSS4181]

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)

I'm having this issue as well with XZ Premium (CarbonROM 6.1), TWRP 3.2.3, NanoDroid 20.2, just recently (it never happened before). It seems to be some filesystem-related issue.

After instaling Magisk, when I first install NanoDroid full package will succeed. However, the subsequent installs (such as Bromite WebView) would fail because for some reason after flashing NanoDroid resize2fs would see magisk.img as damaged, telling me "Please run e2fsck -f magisk.img first."

However, at this point the img file has been expanded, but the actual file system is not. Also, trying to do "e2fsck -f magisk.img" as instructed would not find any error, and does not fix the error message.

Manually forcing a resize (e.g. resize2fs -f magisk.img 600M) would allow it to install. After resizing, occasionally there would be an inode error when running e2fsck -f magisk.img.
Shrinking would fail again, with the same aforementioned message, so I ended up having to manually shrink the partition using "resize2fs -f" as well (and of course, run e2fsck -f magisk.img just in case).

On the other hand, it seems the Bromite package is not be stable enough on a "user" ROM. Some apps would crash whenever it tries to access WebView related functions. On "user" ROM it might also be checking the WebView APK's signature. On my Pixel C running a Lineage OS 16.0 "userdebug" ROM it's working fine.

And DANGER: Trying to update Bromite WebView from F-Droid could result in bootloop. On my XZ Premium with CarbonROM ("user" ROM) I learned this lesson the hard way. At first it tried to update and failed, and second time, it seemed to succeed, a dialog popped up for a very brief moment that I really didn't see what was written on it, then it went into a bootloop for a few seconds then rebooted to TWRP. I couldn't do anything at this point, so I ended up restoring a backup I did a few days ago when I tried to update from NanoDroid 19 to NanoDroid 20 (and before trying Bromite WebView).

EDIT: It seems manually reinstalling the Bromite System WebView package as user app on top of the Bromite WebView module fixed the issues I've been encountering on my phone. The apps don't crash anymore, so it's probably that by installing the System WebView as user app, other apps would be able to load the libraries directly from APK.

It doesn't appear to be related to whether the ROM is "user" or "userdebug". Some ROMs do require such a step to make other apps properly detect the substituted WebView, while on other ROMs it works out-of-box.

 

[Setialpha]

@LSS4181 are you using Magisk 17.3 it's a bug several users already have suffered, including myself but the recent versions seem to have fixed it for me. At least on the ROMs I've tested Bromite WebView works in all cases, but yes, compatibilty can't be garanteed.

*snip*

Also, I don't get all theese questions, if you have you to use the UNINSTALLER before an UPDATE. Of course not, else it would be called Updater, not Uninstaller *sigh*. Or do you remove your ROM/WhatsApp/Firefox/Whatever before an update? No.

Also given on a fresh installation - as opposed to updates - the GApps removal mechanism is triggered. As you all know microG packages have the same package names as GApps packages. Thus logically you're going to kill your microG setup, most noticeably GCM registrations, when using the UNINSTALLER before an "update"; as it then of course is NO update, but a FRESH installation, obviously, as you removed anything that could have been updated...

I don't understand this question in first place, honestly.