Search results

Did you try flashing from Magisk?

23.1.2, the issue you're experiencing is now something completely different.

The issue has been discussed and fixed.

Nothing at all, settings reside in /data

You'd need to modify the build-package.database and build-package.update files in data/ directory in the git repo accordingly. Take an app like MPV as example and add the entries for your desired app accordingly.

I'm not sure I understand your goal, but that would require modifying build-package to actually bundle said app with ND.

Yes. And yes, the fancy new XDA app shows notification in realtime, woohoo.

Remove it from /data/adb/modules/NanoDroid/system/app and reboot. Ensure to adjust your setup to prevent reinstalling said app. Or flash NanoDroid again, after adjusting setup, but that's likely overkill.

Hi everyone, version 23.1.2 is now available. This release fixes critical bugs that only occur on TWRP which uses busybox instead of toolbox. Feel free to give it at try. Thanks @TALUAtXDA who pointed out the things that have been so obvious, I didn't see them for way too long. ChangeLog...

This very likely depends on the Phone/Contacts app included in the ROM. I've experienced both behaviours, irregardless of microG version was used. It may be that some Phone/Contacts expect some certain API to present, which microG maybe does not include, but I haven't checked into that...

Yes, fixed, I completely missed that.

https://gitlab.com/Nanolx/NanoDroid/-/commit/a05fdf8e7133eb3f9aa57050649a283eefd574b1

I figured that out meanwhile, I'll change the checks so they work with both toolbox and busybox. I didn't know TWRP comes with different "flavours".

Actually, no. There's something complety wrong on your Samsung device trying to setup busybox, basically the whole installer fails. I'll investigate.

Hi everyone, a new bugfix release 23.1.1, Codname Zora is now availabe! ChangeLog ## 23.1.1.20210116 "[Zora](https://memory-alpha.fandom.com/wiki/Zora_(artificial_intelligence))" ## Bug Fixes * Installer, Uninstaller, SysTest, Patcher * fix bugs regarding mounting `/system` from TWRP *...

Hi all, NanoDroid 23.1 Codename Ni'Var is now available. This release includes many internal improvements, aswell as several bugfixes. Not all issues in regards of device compatibility have yet been resolved. I do now have a secondary device again so more intense Android 11 testing will be...

You still need some way of installing something to /system directly, so if you have TWRP installed or did install Magisk before the bootloader was re-locked (if it was re-locked), it should be possible. If you have root access to the device at all, you can also install it manually to /system...

You can simply adjust the setup, flash again (throgh MM) and reboot.

For all custom build in NanoDroid (GNU Bash, MPV, SQLite 3*, Play Store*), I've setup a new git repository as central starting point to check what's up or to create your own builds: https://gitlab.com/Nanolx/nanodroid-patches * just linked, reside in their own repos, for reasons Feel free to...

I may have a look

Long time no see, I've been busy with work and other stuff, I'll get back on here slowly the next weeks.

If you think it's a microG issue, please open a report over at github.com/microg

What's the log? Does fpashing through Magisk work?

NanoDroid 23.0.1 Hi everyone, version 23.0, codename All Aboard, was shadow-dropped last week, I totally forgot to make an announcement here. Anyway, version 23.0.1, codename FCK 2020, is now available containing two bug fixes. Highlights Fixes for Android 11 support in the Installer Alot of...

apktool can't properly process Android 11 apks, so it's not possible to do it currently.

Please provide a logcat.

Android requires BSW to be in /system and /data (as update) installed. That's mentioned in BSW documentation and in NanoDroid documentation. If you just removed the Magisk Module, you only removed the one in /system. Remove /data/app/com.android.webview* and reboot, that should solve the issue...

You can check out old versions on git, that's the installer and stuff required to build NanoDroid packages. Afterwards use build-package as documented to download the apks. There's no archive for built packages. If you want an issue to be fixed, I need the TWRP log. Alternatively you can...

There's always /tmp/recovery.log Did you try flashing from Magisk instead?

By flashing a new zip. If you want to not update the whole module, but only microG, add the microG repo to AuraDroid and then you'll be able to update ut.

See: https://gitlab.com/Nanolx/NanoDroid/-/blob/master/ChangeLog.md#important-note tl;dr you need to re-patch your device. The SysTest log is created by running/flashing the NanoDroid-SysTest package, but it's not required in your case.

23.0-beta2 "All Aboard" Hi everyone, the second beta for 23.0, internal version 22.91, is now available for testing. Changes since 22.90 (23.0-beta1) Fix mounting /system from TWRP in several occasions Fix a regression in nanodroid-overlay which would leave you with no overlays when...

Go to Settings > Device Settings > Audio Enhancement and ensure it is not fully down, else no sound at all.

OK, now I know, why it's not read, /external_sd is not a direct link to /storage/$UUID - this isdifferent in TWRP, thus it works there. For now move the configuration to the internal storage (/sdcard) I'll provide a fix, soon

I made another change, sorry for the trouble...

There's always /tmp/recovery.log aswell

For those having issues with /system mounting from TWRP, I've updated the CommonInstaller in git repo, you can test using the new version by removing the one from the zipfile and adding the one from the git repo instead. gitlab.com/Nanolx/NanoDroid Or wait for a new beta build soon.

What's the mount path for your external sd when in ROM?

Dunno, on A11 the linker setup currently doesn't work.

Unlikely, pressing on Installation will lead to the docs where the first topic is Installation Setup. https://gitlab.com/Nanolx/NanoDroid#installation

NanoDroid 23.0-beta1 "All Aboard" Hi all, a new, shiny, beta release is ready for testing: 22.90 (23.0-beta1), codename "All Aboard". First of all this release includes rewrite, rework and fixes in several parts of the code, so I'd like to invite you to test it - as always with major beta...

For those with issues regarding Play Store app purchases, see: https://gitlab.com/Nanolx/NanoDroid/-/blob/master/doc/Issues.md#play-store-does-not-show-bought-apps-as-bought

Whether LOS4uG is an option depends not just on your uG usage or availability. AICP has several features/settings I've grown qccustomed to, so I'm not going to throw them away. It is, of course, the easiest option.

Did you try the proposed fixed?

Stock ROMs often hard rely on the SetupWizard, meaning installing microG before the first ROM boot fails, this was seen on OxygenOS starting with Android 10 for example, but of course isn't limited to it. AOSP or LOS don't have that requirement. Also most devices now are A/B meaning...

That's only the report, does not affect the zip file. I haven't updared that feature yet, so that's expected.

Thanks, it should work now, with the latest commit.

ubuntiger the switch to ZStandard was freshly made yesterday, so it's likely only tested on my machine (works). What's the output of: touch test.txt zstd test.txt file -b --mime-type test.txt.zst ?

Don't! remove GooglePackageInstaller! Then there will be no package installer left and your device can't install/update apk. Also GoogleExtServices is often a hard requirement for a working device. Both packages don't conflict with microG.

Ah, yes, if you use Xposed modules instead of native support or manual patching, you won't have to priv-app uG.