yashsingh1/xdaforums huggingface dataset:
[Magisk] Yoshi_523:
Hi,

Incase anyone is wondering my conclusion after I beleive a successfull install of NanoDroid & microG is that apps that use Google Play Services for location/maps like Uber Taxi app & WeatherZone app don't work any more. They each display an error regarding the Google Play Services after installing microG. Google Maps does work but with a significant delay which looks like it's requiring a GPS lock before displaying any location at all as opposed to when using the real Google Play Services it gets a location immidiately by using phone tower based location and Wi-Fi assisted GPS in the interium until adqueite GPS signal is achieved.

I installed latest NanoDroid-microG-23.1.2.20210117.zip in TWRP on my Samsung Galaxy S4 (Stock, Rooted, Debloated & Deodexed ROM). I then installed the latest microG Sevices Core apk (com.google.android.gms-212158042.apk).

I think I will just restore my previous TWRP backup and forget about microG that is unless someone has any fix?

So far the old tried and tested way I've been using Google Maps, Uber and WeatherZone without a google account is by only installing an old version of Google Play Services (v12.8.74 from 20-Jul-2018) and and old version of Google Maps (v9.55.1 from 17-Jun-2017). I found these on APKmirror.com. I'm not sure if newer verions of Uber work or not but I've just stuck to using the old version (v4.240.10001 from 4-Dec-2018).
[Magisk] kurtn:
You don't write a word about signature spoofing. Can you check that in microg self-check?
[Magisk] Bracher:
Unfortunately the method with RiruLSP and FakeGapps did not work for me. In case I did something wrong:

I have a fairphone 3 with a and b partition so I'm normally on LOS Recovery but can boot in twrp via bootloader

so my way:

fresh install of LOS (infact factory reset/wipe date in LOS recovery) and reboot, developperoptions USB Debugging,

Magisk - Busybox - Riru - Riru LSPosed activated (a bit strange was that LSP did not aks for root like EdXposed)

than I flashed Nanoroid microG via Magisk - stuck in boot

Rebooted in TWRP flashed Magisk Modul microG Installer revived

Rebooted sucessful. installed FakeGapps and activated it in LSP - reboot- dial *#*#CHECKIN#*#* reboot

But unfortunately this solved not my spoofing problem - no chanceto give spoofing allowance.

I would be very thankful if somebody could give me a hint
[Magisk] kurtn:
Did you give spoofing permission in fakegapps? Can you show microG self-check?
[Magisk] Bracher:
FakeGapps did not ask for any permission so how shoudl I give this permission and as for MicroG this is strange (it's German so I try to translate:

Box one: your system supports signature spoofing, but the box is not ticked and no app is asking for it and ther is no app Signature Spoofing Support.

The third boox issimilar Phonesky has the right signature but the box could not be ticked. all other boxes are ticked

No sorry the forthe box is similar to two
[Magisk] j0110:
Hello,

I experienced some issue while trying to install the patcher on LOS 18.1 from Magisk.

Here's the log :

- 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:/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

Thanks for your help !
[Magisk] kurtn:
Patcher does not work on android 11. Use LSPosed fakegapps
[Magisk] kurtn:
Open fakegapps app
[Magisk] j0110:
Thanks for tour reply.

I was questioning myself because on the gitlab, it is written :

11.0 / SDK 30 (R)

Patcher does not work from TWRP
Patcher works from Magisk if your ROM's services.jar already contains classes.dex

> Deodex Instructions

So I hoped that it would be possible as my services.jar contains classes.dex.
[Magisk] Bracher:
thank you for your help, but after installing FakeGapps (app-release.apk) from https://github.com/whew-inc/FakeGApps/releases and activating it in LSP and reboot - I can't open this app and in settings\apps I can't give permissions it's outgreyed.
[Magisk] wkn000:
@bracker

Open LSPosed app (Should be Activated), go to Modules (x modules enabled), click FakeGapps, switch Module activated and then click Apps to use (MicroG GSM and GSF for example)
[Magisk] jenslody:
One stupid question, just to be sure:

did you try to tick the boxes directly, or did you tap on the text?

The first approach does not work.
[Magisk] Bracher:
both, but doesn't matter anymore, there is a new LOS-MicroG Version for FP3 I flashed this and in combination with a modified MicroG Installer from FriendlyNeighborhoodShane it worked perfectly. But thank you all very much for your help!!!
[Magisk] sb56637:
Hi, a question about Android 11 ROMs and DroidPatcher: I understand that "Patcher does not work from TWRP". Is this just because Android 11 is always encrypted and TWRP can't access /data and /system ? Because I use the MoKee flavor of TWRP with MoKee, and it can access the encrypted data. The reason I don't want to use DroidPatcher through Magisk is because my device doesn't have A/B partitions and therefore Magisk would have to be re-installed after each update. Thanks for the help!
[Magisk] kurtn:
Patcher also fails on unencrypted android 11.
[Magisk] zedoc:
Hi, is it possible to flash LOS 18.1 MicroG version for my Lavender and flash Nanolx after that to bypass the Patcher problem on 11?
[Magisk] kurtn:
Lineage.microg.org has all necessary parts on board. Only nanolx part woth flashing is the webview. Everything else can be installed as user app.
[Magisk] Freepony:
Can I install the Nanodroid modified Play Market app?
[Magisk] kurtn:
Sure. I just don't know how. Maybe as user app.
[Magisk] zedoc:
I've just found this trick to install Playstore (phonesky) posted on github for LOS18.1 MicroG but did'nt try it yet...

Troubleshooting/Nanodroid with LOS 18-microG.md at main · los-legacy/Troubleshooting

Workarounds for LineageOS. Contribute to los-legacy/Troubleshooting development by creating an account on GitHub.

github.com
[Magisk] ChaosNicro:
So there is currently no way to get signature spoofing to work on android R without Magisk? Or is there a manual process?
[Magisk] kurtn:
https://xdaforums.com/t/signature-spoofing-on-unsuported-android-11-r-roms.4214143/
[Magisk] jackson_c:
Is there any way today to enable syncing contacts with Google on Android 11? Even manually.
[Magisk] kurtn:
There are synch adapters. My preferred method is to go theough google account settings with a web browser and download contacts as vcf file.
[Magisk] zkoz:
My prefered method is Davix app.
[Magisk] sn00x:
I've created a Masigk module for exactly that purpose. See this thread or on github
[Magisk] andy356:
@Setialpha Do you consider Android 11 support stable yet? I see there are still some bug fixes and changes queued up in the changelog for the next version.

I'm on LOS4microg 17.1 with Nanodroid, and would like to upgrade to 18.1, provided I can safely flash Nanodroid on it.
[Magisk] kurtn:
Main part missing for android 11 is a stable patcher. You don't need that for lineage.microg.org . What components of nanodroid do you use?
[Magisk] andy356:
Thanks for the info! I use the main zip (patched Play Store), plus Bromite, Google libs, and OSMAnd.

Sounds like I can upgrade just fine, then?
[Magisk] andy356:
@kurtn Sorry, I have to confirm. Is that a yes? I don't want to undertake a weekend-long process and end up having to rollback... :geek:
[Magisk] kurtn:
Each setup is different. You can get no guarantee. I always try to have a second phone setup. You can try to do a dirty upgrade.
[Magisk] andy356:
Oh, I'll definitely be doing a clean install. I don't want to compromise my daily driver by being lazy. Hence, a weekend-long process instead of an evening.
[Magisk] sn00x:
For me installing the patched PlayStore with NanoDroid on a freshly installed LOS 18.1 always ended with an unbootable system (the LOS boot animation never completed). However installing the playstore with nift4's microG Installer Revived did work. But it installs DroidGuard as a system app and furthermore renders OTA upgrades of GmsCore useless, because it overwrites the one which is already included in LOS for microG.

I ended up creating my own Magisk module fakestore2playstore, that simply replaces FakeStore with Nanolx's patched PlayStore.

@Setialpha I'm not sure what causes NanoDroid's the boot problem with LOS 18.1 for microG, but I assume it may be because of missing permissions. I guess after including these permissions, NanoDroid should work fine on LOS18.1 for microG.
[Magisk] jackson_c:
Any way to update Bromite WebView installed from NanoDroid with the official package?
[Magisk] ninevoltblock:
Wouldn't it be easier to enable the Bromite repo in F-Droid's settings, then F-Droid would offer any updates.

I am not sure if it is available in the default F-Droid, but it was in the F-Droid included in an older NanoDroid (that I had on my previous phone).
[Magisk] ninevoltblock:
I am struggling trying to install LineageOS 18.1 & NanoDroid on a OnePlus 8T (A/B slots, virtual partitions from Super partition, TWRP limited beta).

Neither TWRP nor LineageOS Recovery would install the NanoDroid zip. There is no OrangeFox for this device.

I succeeded to install LOS for microg, adb push the NanoDroid.zip and install from Magisk/"Install from storage". However, it ignored nanodroid-apps and nanodroid-setup from the same folder. Yet the config folders listed in Applications.md are read-only or do not even exist:

/data/media/0

/sdcard1

/external_sd

/data

/system/addon.d/

/tmp

Also, the permissions RECEIVE_SMS and ACCESS_BACKGROUND_LOCATION are unavailable, which may be the cause why some apps are stuck on startup (F-Droid) or crashing (including Magisk Manager). It's a known issue but the suggested fix does not work for me, as again the given paths are inaccessible or non-existing.

Do you know an easy way to get NanoDroid installed (controlled by nanodroid-setup and -apps files) on LOS18.1 on such a device?
[Magisk] kurtn:
How about not installing nanodroid on lineage.microg.org ? There is a magisk module for patched päaystore. Everything else can be installed as user app.
[Magisk] ninevoltblock:
I had been seeking NanoDroid's convenience of one-stop-shopping. But sure, I'll try that now. Thanks!
[Magisk] andy356:
Oh no! Thanks for the info. I'm not going to risk flashing until this problem gets solved... unless other people have been able to flash it successfully and it's a device specific problem?
[Magisk] Freepony:
I hope this will work with lineage microg. Thank you for your work.

But how to update the playstore app?
[Magisk] anly11:
Do i have to be rooted in order to deodex android 10 stock rom?
[Magisk] andy356:
No one?
[Magisk] kurtn:
Looks like you can avoid using play store. Stay with that. If not: there is a telegram group "microG user group" . People report success. Mainly with minmicrog installer.
[Magisk] andy356:
Unfortunately, I need the patched Play Store for a license-checking purchased app.
[Magisk] kurtn:
You already purchased the app? Is it piracy, if you now make the app usable without play store?
[Magisk] Roberto W.:
give https://github.com/nift4/microg_installer_revived or probably https://github.com/sn-00-x/fakestore2playstore a try
[Magisk] Psk.It:
I am using tipically those magisk module

(some additional notes)
[Magisk] ChaosNicro:
With the ROM images being filesystems packaged in a zip-file, could you not apply the modifications to the zip? Would that not get around the mounting/encryption problems of a running system. I'm trying to apply sigspoofing to an unofficial LOS build and would like to avoid root and Magisk.
[Magisk] einnarr:
Hello there,

as I installed LOS18 today on an Redmi 4x (santoni) together with Magisk (no GApps), I opted to install this Nanodroid-package via Magisk directly afterwards:

https://downloads.nanolx.org/NanoDroid/Stable/NanoDroid-23.1.2.20210117.zip

After reboot I found several apps being installed, which do not belong to LOS: e.g. Frost (Facebook Interface App)

As I do not use FB at all, I would like to uninstall Frost. However swiping the app symbol upwards to the top area the uninstall option does not appear.

Also in F-Droid - the app is listed as installed - no option for uninstall in the "managing apps section" is available.

What is the intended way to delete unwanted apps that come apparently with that NanoDroid package (now I also have 2 apps for: camera, calendar, SMS,...)?

Thanks.

cu,

einnarr
[Magisk] abacate123:
[MENTION=4187311]Setialpha[/MENTION] great work with the aroma (and the other changes as well), it's even faster/easier now, and much more user-friendly.

But, I'm still having trouble with the contactsSync BUT this time I've got some logs for the crashes, and I hope it helps you somehow. I'll attach (yeah I know this is getting annoying, sorry, last time I comment about it xD).

Edit: logs attached, I hope i got the crashes.
[Magisk] vladniko:
Have you tried this
[Magisk] Setialpha:
It's a setup wizard. It creates the setup files *only*. That's all documented in the announcement post (click the link that explains the setup wizard), ChangeLog and docs. ;)
[Magisk] abacate123:
Please, read the previous pages...
[Magisk] vladniko:
Was just asking, a simple yes would suffice
[Magisk] abacate123:
Lol why the drama, I was just answering, also, I explain better some pages ago, so that'd fit better your answer.
[Magisk] cuberio1:
I have to admit I read it before but only with your answer and a second time reading (!!) I think I get it now ... Sorry and thanks for all once again..
[Magisk] Shadow53:
I've updated my build scripts to build a sync adapter zip for the last three android versions. If I recall, your problem was that you were running marshmallow, so you should try using the zip for marshmallow systems now. Let me know if it works or not.
[Magisk] AlreadyFree:
I can't get swipe to work. I turned it on in the setup file. Is there some other steps involved to get it functional? Otherwise no problems. Thanks

Moto G osprey

GZR Tesla 7.1.2 Unofficial 4.3 Rom

NanoMod 11.1.20170714

Magisk 13.3

AOSP Keyboard
[Magisk] Blackcrown:
Nice - I was pointed to nanoMod last week and installed nanomod-microg and nanomod-fdroid as magisk modules after deodexing and patching my ROM .

Now - a few questions on updating nanoMod:

1. The way to update is: grab a new version of nanomod-microg and the patcher and flash again in TWRP - right?

2. No need to flash a new version of nanomod-fdroid, since fdroid should update itself - right?

3. Anything else to update/flash?
[Magisk] Trademark97:
I am having problems installing NanoMod on my device (Moto G4 [XT1625]).

The configuration I am using when I attempt to install is as follows:

TWRP 3.1.1 (Shreps)

AospExtended 4.4

Magisk v13.3

NanoMod 12.0-indev (commit ef0f6d7c)

NanoMod setup-wizard (also 12.0-indev)

I have tried to install using the following procedure (after full wipe):

------------------------------------------------------------------------------------------

1. Push all necessary files

2. Flash AospExtended ROM

3. Wipe cache and dalvik-cache

4. Flash Magisk v13.3

5. Wipe cache and dalvik-cache

6. Run setup-wizard, and make the following customizations:

a. Add SyncAdapters and SwipeLibs, and disable installation of Zelda sounds

b. Remove some applications from list of applications to install

c. Disable pseudo-debloat for some system applications

7. Confirm choices, and complete setup-wizard

8. Flash NanoMod full zip

-------------------------------------------------------------------------------------------

The installer seems to run just fine up to the part where applications are installed. Then, part way through, it fails.

The error I received is:

!! failed to install /dev/tmp/NanoMod/system/app/Oandbackup to /magisk/NanoMod/system/app/
Updater process ended with ERROR: 1

My recovery.log is attached.

Could you please help me figure out what the problem is when I am installing? Thank you very much for making such an awesome mod, and for being so responsive.
[Magisk] Setialpha:
[MENTION=8003791]Trademark97[/MENTION] you don't seem to use the released setup wizard: you've got a typo in your .nanomod-apps it says Oadnbackup instead of Oandbackup. The released version doesn't have that typo.
[Magisk] Trademark97:
Sorry, the Oadnbackup was a typo when I was writing my post; Oandbackup was the listed application name at the time of the failure. I apologize for any confusion that my typo may have caused.
[Magisk] Setialpha:
cp: xwrite: No space left on device

magisk.img seems to not be big enough, strange, the code for cgecking and growing magisk.img is the official one from module template v4...

The error logs about .nanomod-apps are irrelevant, just an old line if code left over (fixed just now).

I'll debug further. Or is not enough free space left in /data?
[Magisk] Trademark97:
Thank you for responding so quickly and for attempting to fix the problem as quickly as possible. I really appreciate your effort to help and I look forward to the problem being fixed so that I can update to the latest version of one of the most awesome Android mods I have ever found. :)
[Magisk] Setialpha:
1) for up to 11.1 yes. Starting with 12 the installer tells you whether you need to repatch (when ROM updated before), or whether it re-used the services.jar (when ROM not updated before).

2) all packages are always rebuilt for a new version, but for F-Droid that applies, yes. The microG/Full Packages also contain other stuff, so updating always recommended.

3) Nope.
[Magisk] Trademark97:
Is it possible to see how much space is assigned to /data, and if it is not sufficient, is there anything that I could do on my end to potentially free up enough room for the installation to successfully complete? If there is, I will do so and attempt to reinstall my system again, and see if it works.
[Magisk] Setialpha:
When you are in recovery, issue the following comnands (using 'adb shell' or Advanced > Terminal) and post the output please:

du -h /data/magisk.img
df -h | grep /data

It will tell you the size of magisk.img and space left of /data.
[Magisk] Trademark97:
Should I run these commands before I flash NanoMod, after I flash NanoMod, or both?
[Magisk] Setialpha:
Doesn't matter.
[Magisk] kurtn:
MicroG will not work correctly anyway with your method. You can uninstall the magisk module.

If you really want to learn about microG, try this:

santoni
[Magisk] Apex Predator:
You need to reinstall nanodroid and use (and edit) the config files. Please refer to the documentation.

If you don't want any apps at all, the best way is to edit the .nanodroid-setup file and make sure this line is correct: nanodroid_apps=0

If you do maybe want some apps, here is an example of the .nanodroid-apps file. Apps with # next to them will not be installed.

Please note, these will be installed as system apps. That is why you're having trouble removing them. Easiest way as I said is just to reinstall ND.

##########################################################################################

#

# NanoDroid-Apps configuration file

#

# All applications listed here will be installed

#

# Fileformat:

# - one app per line

# - name must be *exactly* (case sensitive!) like given in the NanoDroid documentation

# - see: https://gitlab.com/Nanolx/NanoDroid/-/blob/master/doc/Applications.md

# - commented out lines (starting with #) will be ignored

#

##########################################################################################

# Alarmio

# Amaze

# AnysoftKeyboard

# Blokada

# FreeOTPPlus

# Frost

# HackersKeyboard

K9Mail

# KeePassDX

# MPV

# NewPipe

# OAndBackupX

# Odyssey

OpenCamera

# OpenKeyChain

# OpenLauncher

# OpenVPN

# PrivacyBrowser

# QKSMS

SimpleCalendar

SimpleGallery

SmartPackKernelManager

# Termux

# TorBrowser

# Twidere

Warden

XDALabs
[Magisk] einnarr:
Hello Apex Predator,

thanks for the details. Clarified a lot for me :-)

cu,

einnarr
[Magisk] einnarr:
Hello kurtn,

knew about that link already, however there only LOS16 is available :-(

I prefer staying on the current LOS18 builds here:

Jabiyeff-build - Browse /LineageOS at SourceForge.net

sourceforge.net

To my understanding installing microG via NanoDroid through Magisk is the one way to get it actually working, as NanoDroid is "paving the way" for microG requirements.

What am I missing here?

cu,

einnarr
[Magisk] kurtn:
I don't know anything about the file you linked. But from the size i guess it is lineageOS without GApps. Thats good. Try to run it without GApps or microG first to see what's missing and how stable it is.

For microG you need signature spoofing. Is it built in?

Next you need some microG and companion apps. Here comes nanodroid or any other flashable installer. They are necessary, because for some features microG has to be a system app.
[Magisk] einnarr:
Hello kurtn,

those builds are pure LOS18 w/o GApps. No signature spoofing available therefore.

So far I flashed LOS18 with Magisk 23. Then running NanoDroid to get microG correctly in as system app. Guess this should be fine. Will test later.

My original post was just due to the additional apps turning up, which I did not expect (overlooked this fact) as I did not realize this regarding the info from NanoDroid website in the portion "summary" does not inform about these.

Will get back here when I can feedback whether microG it works or not.

cu,

einnarr
[Magisk] einnarr:
Ok, so I reinstalled LOS18, Magisk 23 and NanoDroid without apps an all went fine so far.

Now opening microG I see, that the LOS18-has no integrated support for signature spoofing. I thought this would be handled by the installation via NanoDroid? Where do I misunderstand the procedure?

As I only want to run some specific apps (electric car charging service: enbw mobility+ / wattfinder) dld via Aurora, I am not sure if I require sig-spoofing at all.

The apps install fine, but when opening up no map information is visible and both give the message, that "Required Google Play Services are not available on your phone".

Any hint on how I can proceed here?

Thx,

einnarr
[Magisk] kurtn:
Install lineage.microg.org . Official lineageOS has no signature spoofing and nanodroid can't patch android 11.

MicroG has the mapbox component. That is able to replace Google's map display in some apps. You have to try.

P.S.: you can try other methods to get signature spoofing on android 11 like patching services.jar or xposed module fakegapps or crDroid https://xdaforums.com/t/rom-official-10-0-11-0-crdroidandroid-6-x-7-x-santoni-stable.4176461/unread