yashsingh1/xdaforums huggingface dataset:
[Magisk] K9100ii:
You're missing aarch64 (64-bit ARM). The binary for arm should be selected if it returns 'aarch64'.
[Magisk] Setialpha:
Yes, fixed, I completely missed that.
[Magisk] Sc4r3Crow:
@Setialpha I'm using Nandroid since a couple of months and I love it (y)

Some time ago I've realized that I can't save contacts to my device anymore, that means I can't select my device as standard account for new contacts. I only have the opportunity to use either a Google account or one of my email accounts for saving them.

Is that related to the latest build of NanoDroid/MicroG or to the custom rom I'm using?

I'm not 100% sure but I think when I was using an older build of NanDroid with the same rom I'm using atm, I've been able to save contacts to device directly :unsure:
[Magisk] Setialpha:
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. Additonally if you grab a log that would hint at a microG issue, it should be posted as bugreport directly to the microG project.
[Magisk] Setialpha:
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

## 23.1.2.20210117 "BusyCompat"

## Bug Fixes

* Installer, Uninstaller, SysTest, Patcher
* fix critial bug when running from TWRP that comes with busybox instead of toolbox

* Patcher
* fix checking applicable debugging flags in TWRP that comes with busybox instead of toolbox

Download links

Download from Nanolx.

Bug reporting

In case of errors, please provide

when installing from TWRP

/data/media/0/nanodroid_logs/MODID_log_INSTALLDATE

/data/media/0/nanodroid_logs/MODID_twrp_INSTALLDATE

/tmp/recovery.log

when installing from Magisk Manager

/data/media/0/nanodroid_logs/MODID_log_INSTALLDATE

press the save icon and post the Magisk Manager created logfile aswell

SysTest package logfile

logcat (if applicable)
[Magisk] ubuntiger:
Hi everyone,

How can I selectively uninstall a single app installed via NanoDroid Full package as part of .nanodroid-apps?
[Magisk] Setialpha:
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.
[Magisk] ubuntiger:
Hi everyone,

would it be possible to

Thanks, that was fast. Would flashing NanoDroid again keep the personal settings done on the other apps?
[Magisk] Setialpha:
Yes. And yes, the fancy new XDA app shows notification in realtime, woohoo.
[Magisk] ubuntiger:
Yet another question:

Could I add my personally preferenced apps to the list of apps to install?

E.g. I like the RadioDroid App from F-Droid Repo.

Or could I manually move them to /data/adb/modules/NanoDroid/system/app once installed normally as user app from the repo?
[Magisk] Setialpha:
I'm not sure I understand your goal, but that would require modifying build-package to actually bundle said app with ND.
[Magisk] ubuntiger:
Yes, that's what I was targeting for. As I am typically building from git with ./build-package all at least this should be possible. But I would need precise hints, where to modify. (And maybe later how to keep the personal changes, as my git knowledge is elementary only, but this shall not be the main point.)
[Magisk] starbright_:
On a clean LOS installation I used the SimpleContact-APP (FDroid). It is not able to create an account - it can save data only on device-not visible to other apps. Only if the app on device creates initial entry than it can handled by this app too. Maybe this is what you experience too.
[Magisk] Setialpha:
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.
[Magisk] ubuntiger:
One last question for now: As I understand the apps are only installed with the Full package. When re-flashing, what happens to the other parts of the full package, e.g. to microg, where I most likely did some settings, gave some permissions, etc?
[Magisk] Setialpha:
Nothing at all, settings reside in /data
[Magisk] matke84:
@Setialpha Sorry what problem do I have with patcher? I left a log but got no response. Just to know what's going on. Is there a chance to sort it out?
[Magisk] Setialpha:
The issue has been discussed and fixed.
[Magisk] mahmoud ayman:
I was trying to install your module on A11 with magisk and my Rom supports sign.. spoofing. But it always eng up installing fake store and aurora without ask for choose for your mentioned play store,

Well I after installing I tried to force uninstall fake store then install play store and I did then moved it to system too. But it stuck on logo without any response BTY the Play store I installed was yours from fdroid. So. The bottom of this what I can do to fixx this problem?
[Magisk] kurtn:
NanoDroid/doc/AlterInstallation.md at master · Nanolx/NanoDroid

[MIRROR] See https://gitlab.com/Nanolx/NanoDroid for main repository - Nanolx/NanoDroid

github.com
[Magisk] mahmoud ayman:
Thanks
[Magisk] mahmoud ayman:
well i did as guide and i got Play store from nanodroid and signed in but it stuck at play logo without response.

any idea why that or a fix for this ??!
[Magisk] matke84:
@Setialpha Excuse me when it's fixed? I use the latest version and it doesn't work. The log is from the latest version.
[Magisk] Setialpha:
23.1.2, the issue you're experiencing is now something completely different.
[Magisk] matke84:
@Setialpha Sorry, but I think you replaced me with someone. I left the first log a couple of months ago and my problem has not been solved by any version, not even this last one. Anyway, is there a chance something can be done here?
[Magisk] Setialpha:
Did you try flashing from Magisk?
[Magisk] carlos974:
@Setialpha

The "rooted debugging" feature in settings -> options for developers no longer appears after installing MicroG

(attachments before and after)
[Magisk] mahmoud ayman:
Deleted
[Magisk] matke84:
@Setialpha It works but I would avoid using Magisk. Is there a chance you can set it to work through TWRP like before?
[Magisk] ubuntiger:
Seems not to be a general problem, I don't have this effect on a Mi8 dipper LOS with Magisk installation mode just newly done using an own build of 2021_01_17.
[Magisk] ubuntiger:
Thanks for your hint. Helped me get the problem fixed back in December, the solution was just a couple of lines down from your link - found it anyhow:

https://gitlab.com/harryhobo/NanoDr...sues.md#permissions-not-granted-on-android-10

With the latest NanoDroid version of 2021_01_17 the fix is no more needed for my Mi8 dipper with LOS 17.1 in MagiskMode.
[Magisk] ubuntiger:
Thanks for your hint, even though I did not follow it. I have a couple of different devices, and unfortunately not for all of them the original LOS and the microg.org version do exist, so I was targeting for something more generic.
[Magisk] flash713:
Just wanted to say thank you for all you do and have done op! I've used this installer on a few devices and always worked great!!

Currently on my tmobile converted to global OnePlus 6t im using crDroid 7.2 Android 11 rom with magisk 21.4 and Nanolx micro g & fdroid from stable section in op and ive been using this for 4 days now and its great! I hope micro g and Fdroid stay around for good. After all ive learned about spyware and malware, DRM and all i never want to use Play Store again. FDroid is soooooo much better in all ways imo. What Fdroid doesn't have i use privacy browser and vpn for and works well. Things like instagram and all... Anyway appreciate your work very much!! :)
[Magisk] carlos974:
For me on 2 devices (Galaxy mega and J5 2015) it's the same

(Android 11, magisk 21.4 et microG 2021_01_17)
[Magisk] flash713:
Latest Nanolx (stable) micro g and fdroid on crdroid 7.2 Android 11 on OnePlus 6t magisk 21.4 i cant get screen cast to work. Just tried and it just wont allow me to access cast at all. Log: https://mega.nz/file/rYIhCKrJ#_vnkLH2euBC8JPLZIdzUWIRZojgQY7wnRsETYxX5aK8
[Magisk] mobilism:
Android version: LineageOS18.1

When I install Patcher from Magisk ,I get this error:

- Copying zip to temp directory

- Installing NanoDroid-patcher-23.1.2.20210117.zip

********************************

NanoDroid

Framework Patcher

Powered by DexPatcher

23.1.2.20210117

********************************

> preparing environment

> Android 7.0 - 10.0 (SDK 30) detected

*** LD_CONFIG_FILE=/apex/com.android.art/etc/ld.config.txt

> device architecture: arm64

> installation mode: MAGISK

++

++ services.jar status: DEODEX

++

> patching signature spoofing support

>> patching services.jar

*** BOOTCLASSPATH=/apex/com.android.art/javalib/core-oj.jar:/apex/com.android.art/javalib/core-libart.jar:/apex/com.android.art/javalib/core-icu4j.jar:/apex/com.android.art/javalib/okhttp.jar:/apex/com.android.art/javalib/bouncycastle.jar:/apex/com.android.art/javalib/apache-xml.jar:/system/framework/framework.jar:/system/framework/ext.jar:/system/framework/telephony-common.jar:/system/framework/voip-common.jar:/system/framework/ims-common.jar:/system/framework/framework-atb-backward-compatibility.jar:/system/framework/ims-ext-common_system.jar:/system/framework/telephony-ext.jar:/system/framework/WfdCommon.jar:/apex/com.android.conscrypt/javalib/conscrypt.jar:/apex/com.android.media/javalib/updatable-media.jar:/apex/com.android.mediaprovider/javalib/framework-mediaprovider.jar:/apex/com.android.os.statsd/javalib/framework-statsd.jar:/apex/com.android.permission/javalib/framework-permission.jar:/apex/com.android.sdkext/javalib/framework-sdkextensions.jar:/apex/com.android.wifi/javalib/framework-wifi.jar:/apex/com.android.tethering/javalib/framework-tethering.jar

*** DALVIKVM_OPTS= -Xnoimage-dex2oat -verbose:class

Error preloading public library libandroid.so: dlopen failed: library "libstatssocket.so" not found: needed by /system/lib64/libandroid_runtime.so in namespace system

Aborted

!! failed to apply patches

! Installation failed
[Magisk] carlos974:
Known issue with Android 11!

See previous posts
[Magisk] ichmyselfandi:
I am also unable to patch Signature Spoofing on Lineage 18.1

I tried all patches and different methods regarding TWRP and Magisk.

I also was reading through the last pages of this thread.

So, basically it doesn't work at all? Or what is the solution?

Edit:

@Setialpha

I think it would be best to update the first post regarding Android 11 and Sig Spoofing. Because right now it says, that it works when done via Magisk.
[Magisk] kurtn:
EDIT: THIS PROCEDURE IS NO LONGER NEEDED. USE LSPosed.

From telegram

Signature Spoofing for Android 11

Guide by bluede-v Will

First of all Flash your ROM and Magisk (you need to download the latest version to get Magisk working on Android 11)

Click on Build number (7x) to enable Developer Options

After that enable ADB-Debugging and Root-ADB-Debugging in your ROM in case of LineageOS go to Setting -> System -> Developer Options

So Lets go this is the more complicated part. but also really easy if you done it once.

I'm using Debian Linux but it should be possible on every OS. In Windows use the Linux Subsystem.

You need to have ADB installed on your System tho.

ADB link: https://adbdownload.com

First of all you need to download this 2 Files:

spoof_AVDapi30.zip.ONLY'MAGISK&ANDROID-STUDIO · 11-attempt · oF2pks / Haystack · GitLab

GitLab.com

gitlab.com

https://github.com/microg/GmsCore/files/5652857/microG_AVDx86api30_magiskMaRViN.zip

Rename "spoof\_AVDapi30.zip.ONLY'MAGISK&ANDROID-STUDIO" to "spoof\_AVDapi30.zip"

Next Download this zip: https://gitlab.com/oF2pks/haystack/-/archive/11-attempt/haystack-11-attempt.zip

Also download this jar file: https://github.com/DexPatcher/dexpa...nload/v1.8.0-beta1/dexpatcher-1.8.0-beta1.jar

So now unzip the haystack-11-attempt.zip and put the dexpatcher.jar file into to Folder.

This part I use Bash shell in Linux.

Bash:

adb pull /system/framework/services.jar

java -jar dexpatcher-1.8.0-beta1.jar -a 11 -M -v -d -o ./ services.jar 11-hook-services.jar.dex 11core-services.jar.dex

(After that Command you should have 4 files all named classes*.dex)

Bash:

mkdir repack

zip -j repack/services.jar classes*.dex

After that you should have a new services.jar in your repack Folder.

Now You need to open the spoof\_AVDapi30.zip go in /system/framework/ and delete the old services.jar and put your own file in. that's in your repack Folder.

Don't ruin the zip-format of the file tho because otherwise Magisk will cry while install.

After that put your spoof-AVDapi30.zip and your microG\_AVDx86api30\_magiskMaRViN.zip on your Phone and Flash via Magisk.

Reboot and you hopefully have Signature spoofig working. If you run in any Problems check out the GitHub Links here. there will be comments that maybe will help.

#sigspoof #signature #spoofing #android11 #a11 #r
[Magisk] ozonevista:
Hello@Setialpha please help, the Nanodroid v23.1.2.20210117 does not allow me to get "MetaQuotes ID" in Metatrader 4 mobile app, i think it has something to do with microg, because when i use microg v0.2.14.204215029 it works and i get metaqoutes ID. Images of what i mean attached.
[Magisk] immi803:
@Setialpha

I'm on A11 arrow, rom with default signature spoofing, can you guide me how to pass safety net

Badly need for banking etc apps to work, self test all ticks, any help is highly appreciated

Thank you for your immense contributions
[Magisk] bertino:
Safetynet is broken in microg unfortunately, if you need it use gapps.

From the latest commit it seems that mar-v-in is working on this issue!
[Magisk] vladniko:
Even if those apps don't show up under gcm?
[Magisk] Setialpha:
Then not. Except I'm almist 99% sure GMail uses GCM.
[Magisk] vladniko:
It's super weird, when I had gapps the notifications for Reddit and inbox were instant. I just want to match that
[Magisk] Setialpha:
Did you do a clean flash of the ROM and everything before installing microg? If not, try if uninstalling and re-installing the apps fixes the issue.
[Magisk] vladniko:
I figured it out, it's because the accounts weren't syncing enough. The second I did sync now on my google account, it worked. Just need to find a way to get it to be instant now

---------- Post added at 10:15 AM ---------- Previous post was at 10:15 AM ----------

Yup, wiped cache dalvik data and system. Will trying reinstalling
[Magisk] :
Has anyone managed to get android wear to work with this module? Its the only app I have that refuses to work
[Magisk] Setialpha:
Dunno, but is Android Wear supported by microG?
[Magisk] Anarchy16:
so, i made some nanomod-patcher test with both my phone (mi4w & op3)

mi4w : latest aosip rom, patch only take 4-5min

op3 : latest CypherOS, damn patching for >30min :eek:

not a problem actually, but that makes me wonder, what causes the time gap between those 2 ? is it the phone or the rom :confused: ?
[Magisk] kurtn:
Granting spoofing permission to Playstore (and restarting) solved some of the Problems of the snapshot i made yesterday. But calling playstore still makes "microG Services Core has stopped". Afterwards NLP is broken. Should I try next snapshot or do a Test with a known good release?
[Magisk] Setialpha:
In this regard nothing was changed from the last stable release to the snapshot, so it won't change anything. I need a logcat to see what's going on when the Play Store crashes, also what ROM / ROM Version (not Android version) / Device?
[Magisk] Setialpha:
Progress Report

So far so good. The next release won't be 11.2, but 12.0 instead. So what happened so far since 11.2-beta?

configuration file format changes

the format for .nanomod-apps changed. Old

INSTALL_APPS="app1
app2
..."

New

app1
app2
...

the installer will auto-migrate existing files to the new format.

the format for .nanomod-overlay changed. Old:

APPS=(app1
app2
...)

PRIV_APPS=(app1
app2
...)

New:

app1
app2
...

the installer will auto-migrate existing files to the new format.

AROMA based setup wizard

Yes, it's here. Currently lacking app descriptions for pseudo-debloater setup, but who cares that will be added soon(tm).

It will create the configuration files in /data.

That means: if you have self-created setup files somewhere else than /data and want to use the Setup Wizard, remove them! Otherwise: if you don't want to use the Setup Wizard, do nothing(tm).

Why is the Setup Wizard a separate zip??? Because it's difficult to combine AROMA setup, Magisk Installer and System Mode installer (You can't just run shell commands normally in AROMA updater-script). Also this way you

a) don't have to re-setup everytime

b) can choose to not setup and choose default settings right away

c) can choose to self-create the setup and auto-install without distraction

So, no, Setup Wizard as part of the installer is not gonna happen.

When will it be available for testing?

Tomorrow for official beta, or checkout the git repo and use the build-package script (for the impatient).
[Magisk] RobotPhone:
Would you consider storing config files somewhere in 'internel memory' instead of /data ? Reason being is that people have to format /system and /data when flashing roms, which deletes nanomods config files.
[Magisk] American_Jesus:
See the docs https://gitlab.com/Nanolx/NanoMod/blob/master/doc/AlterInstallation.md

one of the following directories

/sdcard (internal storage)

/persist

/external_sd (TWRP path to SD Card (if any))

directory containing the zip file

/data (fallback)
[Magisk] demonoidmaster:
Who formats /data lol? If you update your rom there's no reasin to do such a thing
[Magisk] RobotPhone:
My suggestion is have the aroma setupwizard default to /sdcard instead of /data.

When switching roms it is encouraged to format /data as well as /system.
[Magisk] 1plus:
If you flash a different custom rom from your normal one that is usually a requirement (otherwise major problems are almost guaranteed to occur). Also it is a good idea to do so when your custom ROM upgrades to a next major version of android.

and of course the worst case scenario -- both /system and /data wipe when encryption fails.
[Magisk] demonoidmaster:
I said UPDATE, not migrating

As for let's say going from 7.1.2 based roms to then future Android O 8.0 custom roms (example Resurrection Remix will probably have builds of Android 8.0) then obviously it's always better to back up your stuff and wipe the slate clean

---------- Post added at 01:38 AM ---------- Previous post was at 01:35 AM ----------

I said update, not migrate...
[Magisk] vladniko:
Where is nanomod microg 12.0 beta? All the rest are there but microg.
[Magisk] Setialpha:
12.0-beta1

Version 12.0-beta1 is now available. Highlights:

.nanomod-patcher file handling changes

configuration file format changes and AROMA based setup wizard

improved Documentation

Full ChangeLog since 11.1

* Bug Fixes
* Full package:
* fixed that GNU Nano didn't work properly when ther terminal only had a few lines
* microG package:
* fixed that `column` was not bundled
* Full, microG packages:
* fixed that GNU Bash did not read `/etc/bashrc`
* fixed that the fallback `/data/.nanomod-overlay` did not get removed
* further fixes to `nanomod-overlay -g`
* remove `nanomod_reinstall` parameter for `.nanomod-setup` configuration file (Magisk-only)
* `services.jar` will now be auto backed up and restored during NanoMod Magisk Module update when `/system/.nanomod-patcher` exists
* `services.jar` will be removed from NanoMod Magisk Module (which indicates ROM update), print a message to the user accordingly
* General Changes
* Configuration Files:
* `.nanomod-apps` layout simplified, now only one app per line, nothing else
* existing configuration files will be migrated to new format
* `.nanomod-overlay` layout simplified, now only one app per line, nothing else
* existing configuration files will be migrated to new format
* Full package:
* provide more tools from `bsdmainutils`
* col, colcrt, colrm, hexdump, look, ncal
* provide more tools from `util-linux`
* findfs, findmnt, lsblk, lscpu, lsipc, lslocks, lsns, setterm, whereis
* provide `less` pager with `lessecho` and `lesskey` utils
* make `less` the default `PAGER` for GNU Bash
* make default `TERM` for GNU Nano `xterm`
* Setup Wizard (in-progress):
* AROMA based Setup Wizard to create all three configuration files in either
* `/sdcard`
* `/external_sd`
* `/data` (fallback)
* renamed `mod.sh` to `build-package`
* revised code, removed cruft
* add multi-param support, for example `build-package fdroid microg` will create those two package in one go
* Downgrades
* Google Backup Transport (7.1.1 > 6.0.1)
* Updates
* Substratum (811)
* Amaze (3.1.2-rc4)
* Yalp Store (0.19)
* Simple Gallery (2.12.2)
* OpenVPN (0.6.73)
* NewPipe (0.9.10)
* Lightning (4.5.1+snapshot20170718)

Download from AFH.

In case of errors, please provide

your device's architecture

your device's Android version (not ROM version)

whether installed as Magisk Module or in System Mode

used Magisk version

recovery.log or logcat or both (whatever is applicable)
[Magisk] cuberio1:
Thanx a lot :)

I tried both installation ways in order to update, the "classic" method and the aroma installer one.

Through the classic one (editing settings through laptop) everything went well.

Through the Aroma I thought it went well at first but realised it didn't install as an addition a few apps. No error message in TWRP, but it's like it did not do anything.

Here are my configuration and logs :

- Configuration :

• Device : oneplus 3T

• Android : 7.1.2 (RR ROM)

• Magisk module

• Magisk 13.3

- Logs :

AROMA Installer version 2.70RC2

(c) 2013 by amarullz xda-developers

ROM Name : NanoMod Setup Wizard

ROM Version : 12.0

ROM Author : Nanolx

Device : Generic (LOS/AOSP)

Start at : Thu Jul 20 21:57:54 2017

> NanoMod Setup Wizard 12.0.20171231

about to run program [/tmp/nanomod-setup] with 1 args

> Thanks for using NanoMod

script result was [1.0]
[Magisk] Zack316:
Hi, I am on Lineage OS based custom rom ( android 10 ). I installed the latest Nanodroid. Spoofing, playservices, phonesky not ticked.

Do I need to use xposed or something else to make it work ?

Pls help, thx.
[Magisk] kurtn:
Did you try to flash nanodroid patcher?
[Magisk] immi803:
Need some help before using microg

1. Where can i download configuration file ".nanodriod-setup" i can see raw file but couldn't find to download it, do i need to create file myself and copy everything to it"

2. In dynamic system partition, should i be good enough to place config file in /sdcard for MAGISK flashing, moreover I'm using orange fox recovery

3. Once successful in setting microg along with Google sync, would it be good enough for contacts backup & sync?

4. What about Gboard and chrome sync, like passwords, bookmarks etc?

5. What impact i should or someone find here on battery & system performance and resources?

6. Can i use latest play store app and signature spoof it for in app purchases or i have no option other than to opt for modified microg play store?

7. If few of my apps requiring magisk hide only to work should work fine as usual even when safety net doesn't pass?

8. Am i good enough with De Ja Vu location provider for Google maps etc or i need others like cell broadcast location providers etc?

I hope someone can help and guide me

Regards
[Magisk] kurtn:
Your questions sound like you really try to get a full Google setup with microG. Mainly for battery saving. That's not what microG is made for. There will be less trouble, if you stay GApps.

1 there is a .nanodroid-setup file for download.

8 navigation apps generally work best with satellite location (GPS and similar). The network location feature in GApps or MicroG is only to provide an estimated location till you get a first GPS fix. Déjà vu is self-learning and should be OK after some time of usage. I get best results from apple back end and best privacy from local gsm.