yashsingh1/xdaforums huggingface dataset:
[Magisk] Shadow53:
Note on those adapters, from the linked page:

"After installation, you may need to enable certain permissions for the sync adapters to work. Go to Settings -> Apps, tap the three-dot button in the top-right, and tap “Show system.” Then search the list of apps for “Google Calendar Sync” and make sure it has the “Calendar” permission enabled. Do the same for “Google Contacts Sync” and the “Contacts” permission. These permissions should be automatically enabled in a future update. See this post for more details."

The sync adapters don't always work the way they should after install. It's possible [MENTION=5627087]ale5000[/MENTION] figured it out in their install zip - I haven't checked (yet). But in order to work, the adapters may need to have permissions manually enabled. I'm not sure that's good enough to have them included in Nanomod, personally.

For people looking to sync contacts, there is another method involving using DAVDroid: https://shadow53.com/no-gapps/setup-guide/3/#option-3-1-2-using-davdroid
[Magisk] inestion:
I get error: 1 and the end on nanomod installation, also it seems that I can't write to /dev/block/mmcblk0p9 but dunno if they are related
[Magisk] Setialpha:
Already fixed in 9.3 (currently in beta).
[Magisk] inestion:
Thanks you, installed the beta without the error.

I've just discovered NanoMod so I'm a bit confused but if I don't plan on using Magisk why it is installed with NanoMod? Sorry if the question has already been asked but the search doesn't seem to work atm.
[Magisk] Oswald Boelcke:
Magisk doesn't get installed with NanoMod. Magisk either comes with the (your) ROM or has to be flashed individually.
[Magisk] inestion:
I was referring to the .apk sorry. Anyway it's not present in the beta so not a problem anymore
[Magisk] Setialpha:
9.3 beta4

Version 9.3 beta4 is now available. Highlights

Optional Google Sync Adapters

nanomod-overlay -p revamped

permissions init script that calls nanomod-overlay -p

Detailed Changes

* fix that VLC was always installed, even if user requested not to
* also greatly simplify VLC installation code in installer
* Full package: remove app libraries not required for device architecture
* example: on ARM the libraries for ARM64, x86 and x86_64 are removed
* microG package: don't install terminfo files as GNU Nano is not included
* microG package: bundle `aapt` (required for `nanomod-overlay`)
* on-pc framework-patcher: only do actual work if in TWRP
* added force-debloat script (for system mode!)
* script that can be run from recovery to debloat the system
* the list of applications resides in the script itself
* the default settings equal to the pseudo-debloat settings of `nanomod-overlay` script
* needs to be run from TWRP, requires explicit user acceptance
* add `Jelly` to the list of pseudo-debloated apps by default
* `nanomod-overlay -p` now checks for proper permissions of system apps
* FAKE_PACKAGE_SIGNATURE for microG Gms Core and Play Store
* READ_CALENDAR and WRITE_CALENDAR For Google Calendar Sync
* READ_CONTACT, WRITE_CONTACTS and GET_ACCOUNTS for Google Contacts Sync
* add `permissions` init script that runs `nanomod-overlay -p`
* Full package only
* for microG package manully run `nanomod-overlay -p` as before
* add optional Google Calendar Sync and Google Contacts Sync
* not installed by default
* bundled with Full and microG package
* add `nanomod.gsync=[0|1]` setup variable
* defines whether to install Google Sync Adapters
* Updates
* Simple Calendar (2.5.3)
* Kernel Adiutor (0.9.70.3)

Download from AFH

x86/x86_64 support is still in-progress, it seems to work in System Mode, but not (yet) in Magisk Mode. Feel free to test.

Provide recovery.log / logcat in case of issues.
[Magisk] Setialpha:
Quick heads up: beta 5 will replace VLC with MPV, this reduces the size for the full zip to 148 MB. MPV is still early for Android, but playing stuff so far.

Also updated YahooWeatherProvider and added OpenWaetherMapProvider.
[Magisk] Wo11ven:
Not yet, Magisk has to be signed to work with my phone cause Asus made it so. I'm still waiting for someone in the Zenfone 2 forum to sign the v13.

For now I'm running non-magisk version and it's great.
[Magisk] digitman xxx:
[MENTION=4187311]Setialpha[/MENTION]

great work bro, everything working great but notice that NanoMod-patcher take about 45 min to be flashed but it working good at the end. is it NORMAL?

also play store not working properly as i should delete it's cash everytime before open it otherwise give me empty white window.!

i guess maybe i miss something

clean flash Lineage 13.1 flash magisk 13 latest beta(96f8efc) flash NanoMod-microG-9.2.20170610 then flash NanoMod-patcher -9.2.20170610

SM-G7102
[Magisk] DJ aliasz3d:
I had to clear playstore app data and cache and now its working for me kept giving server error, patcher only took about 1 to 2 minutes on my s3LTE I9305.

Edit: on nanomod microg with 10/6 patcher on RR 5.8.3 magisk 12
[Magisk] digitman xxx:
thanks for the hint, of course will clear both cash&data next time and feedback

as i said 45 min, So i think there is really something got wrong
[Magisk] DJ aliasz3d:
No problem :good:

45 minutes is quite long indeed.
[Magisk] Bearthquake:
I think I noticed in the nanomod thread that it isn't fully compatible with v13 yet, so you should flash it as system (before flashing magisk)
[Magisk] Setialpha:
That issue with Play Store is known to me, but I don't know why. All I know is: since the upgrade to Nougat it disappeared for me completely, on Marshmallow some ROMs have it, some not.

Did you boot jnto the ROM once before patching? For reference on my Moto X Play it takes less then 5 minutes. But Magisk v13 has a sinilar issue, so maybe I can resolve it the same way some beta testers of Magisk did.

It is, because the bugs in Magisk v13 preventing NanoMod are mostly fixed, 9.2 on the other hand can't be properly installed into /system, which is fixed in 9.3.

Also the patcher has nothing to do with Magisk (other than installing the modified file to it).
[Magisk] Anarchy16:
how to enable sync ? using command or another flashable zip ?

i read instruction on github, but i cant find any tutorial/step to enable it
[Magisk] -Happy Feet-:
okay, this solves the sending error?
[Magisk] -Happy Feet-:
Have this problem also.
[Magisk] Setialpha:
I suppose you have version 20.4 installed, as this issue was fixed with that release (and explained in the 20.4 release post)?
[Magisk] Setialpha:
Have added this under the new "G-Crap"-topic to the Issues list.
[Magisk] Setialpha:
What ROM? I suppose you're using version 20.4 of NanoDroid?

For LineageOS this issue has been fixed with 20.4, but some other ROMs have an additional "master switch" in their own Settings which enables Signature Spoofing or not.
[Magisk] Setialpha:
The installation logs are not too big to upload here, it's /data/adb/MODID_log_INSTALLDATE and /data/adb/MODID_twrp_INSTALLDATE, where MODID is the Package you've flashed and INSTALLDATE the time and date you installed it.

But: nothing changed in the installer compared to the previous version in that regard, so it should work just as before. Are you using the latest (official) version of TWRP for your device?
[Magisk] Setialpha:
Ah, I see. I'm refering to the self-test.
[Magisk] Koont:
Havoc ROM for OnePlus 6t. And, your right I'm on 20.4. I'll search around. My bad. Been fondling my new phone since black Friday and hadn't been keeping up with development. Thanks
[Magisk] oF2pks:
Hi [MENTION=4187311]Setialpha[/MENTION] , thx for advanced DroidGuardHelper & gmscore14.7.99 on repo : https://www.nanolx.org/fdroid/repo

Can you upload non-debug flavor: debug is not supposed to be battery friendly for "dynamic non static" apps (?).

For info, apks can be "null"-signed: void first 6x asking [What?] + 1 "y" for latest [Is?] for keytool... , and after zipalign 4...,you can use "

android

" as generic password with apksigner sign --ks debug.keystore *.apk

[SIZE="1"]$ keytool -genkey -v -keystore debug.keystore -storepass android -alias androiddebugkey -keypass android -keyalg RSA -keysize 2048 -validity 10000
What is your first and last name?
[Unknown]:
What is the name of your organizational unit?
[Unknown]:
What is the name of your organization?
[Unknown]:
What is the name of your City or Locality?
[Unknown]:
What is the name of your State or Province?
[Unknown]:
What is the two-letter country code for this unit?
[Unknown]:
Is CN=Unknown, OU=Unknown, O=Unknown, L=Unknown, ST=Unknown, C=Unknown correct?
[no]: y

Generating 2,048 bit RSA key pair and self-signed certificate (SHA256withRSA) with a validity of 10,000 days
for: CN=Unknown, OU=Unknown, O=Unknown, L=Unknown, ST=Unknown, C=Unknown
[Storing debug.keystore]

Warning:
The JKS keystore uses a proprietary format. It is recommended to migrate to PKCS12 which is an industry standard format using "keytool -importkeystore -srckeystore debug.keystore -destkeystore debug.keystore -deststoretype pkcs12".[/SIZE]

Also, do you change MAX_REFERENCE_VERSION in https://github.com/microg/android_e...bc04e0b#diff-064598cbf8b67520465b27cbc3c9f458 ? edit : indeed.

Finally , ( [MENTION=5627087]ale5000[/MENTION] ) GoogleContactsSyncAdapter should be moved to privileged /priv-app, due to INTERACT_ACROSS_USERS privapp-permissions needed (?).

For the record, latest compatible is 9.84.2 uploaded here https://androidfilehost.com/?fid=11410963190603886579

If it makes sense to some, I noticed (with apktool) that Maps9.84.2 includes a /com/google/android/apps/gmm/shared/net/v2/grpc/CAcert.pem (attached) , which appears in gmscore14.3.66 only /com/google/android/libraries/micore/learning/testing/grpctestchannel/CAcert.pem

btw , for users who don't want trackers, you can scan your apks (keyboard...) with ClassyShark3xodus/fdroid
[Magisk] masterxxxxxl:
the nanodroid setupwizard freezes my LG G7's TWRP. The last thing that gets printed out before is "(c) 2013 by amarullz xda-developers".

Are logs already generated at this point? Where do I get them?
[Magisk] Setialpha:
If it doesn't work, you'll need to generate the files manually. AROMA isn't supported by it's developer anymore.
[Magisk] Setialpha:
The debug build is required for signature spoofing through Xposed. I'll have a look regarding Sync Adapters (don't use them personally).
[Magisk] DoR3M3:
I've never noticed/seen anything called self-test?
[Magisk] jenslody:
In microG-settings (gmsCore-app) it's called Self-Check, I guess that what he is referring to.
[Magisk] DoR3M3:
Look at my Avatar, I know Self-Check... ;)

I was only saying, I didn't see any thing referring to a test, and then I thought, HOLY BLEEP am I loosing my mind and not seeing some feature here... LOL

Cheers
[Magisk] AlreadyFree:
Ok. the 13.05 files are from my attempt to install the new version and the 13.09 files are from when I tried to reinstall the previous version. the last file is from the data/adb/logcat folder so assuming that's the logcat you're always asking for :) Just have to change the extensions back to .txt
[Magisk] Shobit Joura:
Hello devs i just flashed the patcher on vdex rom and then fter rebooting the rom sytem started lagging very much ....is there any fix?????

Its rr oreo 8.1.0
[Magisk] -Happy Feet-:
With Lineage it works but have no playstore. And safteynet fails.
[Magisk] Setialpha:
I've looked into OxygenOS on OP+5T and it's not possible to fully fix it automatically.

Steps required:

- flash OOS

- optional: flash Magisk

- boot into ROM (if never booted into before)

- flash NanoDroid

- boot into ROM

- issue the following commands, as root, on-device to make NanoDroid/microG work with OOS:

pm install -r /system/priv-app/GsfProxy/GsfProxy.apk
pm install -r /system/priv-app/Phonesky/Phonesky.apk
pm install -r /system/priv-app/GmsCore/GmsCore.apk

Now everything works, including unified nlp.
[Magisk] Setialpha:
Is this the pre-patched version of RR or the official? Normally the lagging is caused by patching an already patched ROM. Otherwise there's no fix.

I'll have a look, thanks.

Did you choose to install the Play Store? Regarding SafetyNet see the Issues list in the documentation.
[Magisk] -Happy Feet-:
I read that i must manually install manually, after installing Fakestore. Right?

I read the Dokumentation to the safetynet issues.
[Magisk] Setialpha:
Nope, you can't install Fake Store and Play Store, you can only install one of them.
[Magisk] DoR3M3:
[MENTION=4187311]Setialpha[/MENTION] hi

The off white background for microG, I guess you could say Optical Illusion, because it makes the icon appear smaller.

I made the background white and it now appears larger, what do you think?

Maybe just my eyes...

Personally I like the whiter brighter background...

hmm
[Magisk] Shobit Joura:
Theres an option to grant system spoofing permission coloumn in apps permissions , but that does not works , even after granting permission to microg in microg it says plz check ur rom documentation.....now what should i do?

in microg self check it says plzz check ur rom documentation system dont spoofs sign ...

I think built in system spoofing sign dont work, i asked the dev he said rom doesnt come with sign spoofing...

Now what should i do???
[Magisk] jenslody:
In addition you might still need to grant permission manually via terminal or probably from Settings -> apps-> miscellaneous (or advanced or similar) -> app.permissions, if it does not ask for it.

Or allow spoofing in general (often in developer options).
[Magisk] Shobit Joura:
I gramted it from app permission but in self check still system doeant spoof sign , plzz check rom documentation.

Plzzz tell me the terminal command , and will check if it works?
[Magisk] kmem:
Thanks, it's crashing for me when hidden as well. I'll have to try this. Hopefully future NanoDroid versions will rectify this issue.
[Magisk] mad1mystic:
If I change the values in nanodroid-setup play =0 the installer will still not install fake store. I don't want to install playstore. I tried different values in setup like play=0, 2, 10 but fake store doesn't install on the other hand play =1 will install play store which I don't want. Thanks
[Magisk] marcdw:
So it's not present at all? No /system/priv-app/FakeStore/FakeStore.apk or entry in Settings -> Apps? Hmm, what does the installation log or recovery log show?

Moto G5S Plus XT1806, Validus 8.1.0, microG-NanoDroid, MultiROM, XDA Legacy
[Magisk] Setialpha:
Fake Store is the second digit, so: 01 is the correct one.
[Magisk] -Happy Feet-:
Okay thanks for your Information, but have tried this only with fakestore and can't access the playstore
[Magisk] Setialpha:
a bit easier, as less issues may follow up:

Steps required:

flash OOS

optional: flash Magisk

mount /system read-write and remove the following folders:

system/priv-app/GmsCore

/system/priv-app/GsfProxy

/system/priv-app/Phonesky

boot into ROM (ignore all those complaints that Play Services are missing)

go back to TWRP

flash NanoDroid

boot into ROM - benefit

I won't go into details, but you can't switch from GApps GmsCore to microG GmsCore in-place on

Stock ROMs/GApps

, thus bootin into ROM once without it is required (when GApps are coming from OpenGApps in-place switching works, only Stock GApps ***** around). All other conflicts are solved by the Installer.
[Magisk] mad1mystic:
thank you sir.
[Magisk] jaymoker:
Hello,

[MENTION=4187311]Setialpha[/MENTION]

Please see these few posts before.

I flashed NanoDroid-patcher-20.4.20181230 and it ran successfully (see attached recovery.log).

What I don't understand is that the code (made by [MENTION=5627087]ale5000[/MENTION]) used in NanoDroid-patcher-20.4.20181230 to detect if the ROM has native sigspoof is the same used in NanoDroid-systest-20.4.20181230 and while, the first one doesn't detect native sigspoof support, the last one does (see attached Systest.log).
[Magisk] Setialpha:
I'm currently on a bug hunt and will add this to the list to check, thanks.

I'll also test Havoc OS on my OnePlus 3T. I suspect it may be related to clean flash of ROM and NanoDroid Vs. dirty flash or additional work required.

Will post something once I'm done testing.
[Magisk] Blackcrown:
The point of installing Fake Store is to fake the appearance of Google Play Store, nothing more. If you want to access the Play Store, install Yalp from Fdroid, it gives you anonymous access to the Play Store.

Gesendet von meinem SM-T813 mit Tapatalk
[Magisk] d1n0x:
[MENTION=4187311]Setialpha[/MENTION] I am currently trying out OmniROM 9 on my OnePlus 5.

It has native signature spoofing support and everything works fine except for location. In self-check it says "UnifiedNLP is registered" is unchecked.

I tried to tell my maintainer and he said it's because NanoDroid removes com.qualcomm.location from system/priv-app as it is apparently needed for uNLP to work correctly. I highly doubt this, as it works fine on any other ROM I've tried.

Could you shed some light on this?

Thank you
[Magisk] Setialpha:
Fixed. See git repository, will ship with 20.5.

uNlp doesn't work with com.qualcomm.location, thus it has to be removed.

As [MENTION=5627087]ale5000[/MENTION] pointed out, in reply to a similar user report, in his thread, some custom ROMs decided to drop com.google.android.gms from searched location providers. I guess that's what OmniROM did, I haven't checked their code, though, yet.

This can only be solved by the OmniROM team. On OmniROM up to 8.1 the exact same setup works perfect, by the way.

To restore com.qualcomm.location, you may issue the following command, as root, on the device:

novl -r com.qualcomm.location

if you wanna try with that package, as suggested by the OmniROM developers.
[Magisk] Shobit Joura:
Will that new update fixes location issue since for me now microg never worked on any android pie rom ,, so i am still on los 15.1:crying:
[Magisk] LovepreetSinghGill:
[MENTION=4187311]Setialpha[/MENTION]

Hey plz fix the problem of discord with microg
[Magisk] d1n0x:
I tried the command as su, but only get "read-only file system" as a response. I am on LOS 16 now and everything is working fine.

---------- Post added at 09:49 AM ---------- Previous post was at 09:47 AM ----------

It's not just something you can fix easily, it is a Discord problem. If you absolutely depend on it, use the mobile site, your PC or even Gapps. And please be more polite when asking for things.
[Magisk] guest4711:
It looks as if you installed NanoDroid in system mode. So try a remount rw before trying to restore qualcom nlp, e.g.

su
mount -w -o remount /system
novl....
mount -r -o remount /system
[Magisk] -Happy Feet-:
Hello I would install nandroid on this lineage 16 ROM for my Pixel Sailfish Phone. But I always get an bootloop.

https://xdaforums.com/pixel-xl/development/rom-lineage-16-0-pixels-sailfish-marlin-t3830083/page71

My steps:

- install lineage on partition A

- install TWRP on Partition A

- switch to partition B and reboot Recovery

- install nanodroid

-reboot

The steps are wrong or is nandroid incompatible with lineage?
[Magisk] d1n0x:
Lineage needs to be patched first.

Flash ROM

Boot into ROM

Reboot to recovery

Flash patcher and nanodroid
[Magisk] -Happy Feet-:
Okay thanks I try it.
[Magisk] razr96:
Well this is strange, I removed the overlay of com.qualcomm.location and now network location finally works. Isn't UnifiedNlp supposed to be incompatible with com.qualcomm.location?
[Magisk] Koont:
You don't install root? Flash magisk after Nanodroid.
[Magisk] -Happy Feet-:
Direct after nanodroid?
[Magisk] Setialpha:
Before is usually better, so NanoDroid is a Maisk Module and you don't have to care about A/B.
[Magisk] Setialpha:
Maybe the new(er) version isn't? Old versions at least caused a lot of trouble.
[Magisk] Shobit Joura:
Bro can u explain plzz , what steps u followed .....
[Magisk] razr96:
Enter `novl -r com.qualcomm.location` in a root shell and reboot. Setup the location backends and make sure location mode is not set to 'device only' (it has to be one of the other two).
[Magisk] Setialpha:
I'm not the microG developer, report the issue to [MENTION=3999488]MaR-V-iN[/MENTION] in the microG thread.
[Magisk] Setialpha:
... damn. Will be fixed with 20.5.
[Magisk] Setialpha:
If your ROM has com.qualcomm.location, it get's debloated by default, because some/old versions of it are incompatible with uNlp. Newer versions of com.qualcomm.location seem to be (the other way round) to be required for uNlp to work. Try re-enabling uNlp with the following command, as root, on-device:

Magisk Module installation:

novl -r com.qualcomm.location

System Mode installation:

mount -orw,remount /system
novl -r com.qualcomm.location
mount -oro,remount /system

the extra steps for System Mode installation will not be required anymore with NanoDroid 20.5.
[Magisk] Setialpha:
Hi all,

a quick information about the upcoming version 20.5:

Still open issues to check:

bootloops with crDroid (strangely only crDroid users are reporting them)

Fake Package Signature not working though natively built-in on Havoc OS

Fixed issues:

drop com.qualcomm.location from auto-removed applications as some versions no longer conflict with unified Nlp

Patcher now properly detects whether ROM is pre-patched natively

SetupWizard falls back to /sdcard if user has choosen /external_sd for storing configuration, but it doesn't exist

updated AROMA build for SetupWizard and many other (minor) improvements to the SetupWizard

fix installing microG DroidGuard Helper / Bromite WebView as user apps for Magisk Modules

nanodroid-overlay script in System Mode now properly re-mounts /system read-write to be able to perform actions

many other improvements, see ChangeLog

I expect version 20.5 to be released this weekend.
[Magisk] NotesOfReality:
A (little) two lines summary is possible on smartphones

I'm using a Xiaomi Redmi 4 Prime (5 inches screen, ro.sf.lcd_density=440) on Oreo 8.1(AICP 13.1) and in the worst of the most common/possible of the cases I see a two lines summary.

I've set "OnePlus Slate" as the default font, since it's quite big for my standards I've set the "Display Size" to "Smallest" and I see a little two lines summary.

If I set "Roboto" Font (Default Oreo 8.1 font) with "Default" "Display Size" (which may be a case more similar to yours) I see a two lines a bit bigger summary.

Here I append three screenshot:

1) "Display size" menu in "Display" section of "Settings" app , with "OnePlus Slate" Font

2)"System" section of "Settings" app (with MicroG Dashboard menu summary) with "OnePlus Slate" Font and "Display Size" set to "Smallest"

3)"System" section of "Settings" app (with MicroG Dashboard menu summary) with "Roboto" Font (Default Oreo 8.1 font) and "Display Size" set to "Default"

Honestly I still don't see any point in having a two lines summary, since it's quite precise.

Don't want to make a war because of this, be it clear, if [MENTION=4187311]Setialpha[/MENTION] too likes it that way, it's ok.

Hoping that my will of clarfying and calmly discussing is clear.
[Magisk] Bracher:
Sorry but I have a strange interference:

today FDroid Nanomod repo offered an update of Playstore, Bromite SystemWebView and microG Service core, after the updates all my newspaper apps crashed- it looks as if the BromiteSystemWebView version 71.0.3578.120 does not work properly.

Has somebody else had this problem? OK now I found the following: https://github.com/bromite/bromite/issues/216. Is there any possibility to get rid of this update? Unfortunately I made no update of the original SystemWebView before flashing Nanodroid-BromiteWebView - now I can not reinstall that, perhaps there should be added a warning
[Magisk] guest4711:
You can always install older versions from f-droid. But you have to uninstall the newest version first --> settings -- apps -- bromite webviev -- disable -- yes ... -- enable. Then you can install a working version from f-droid (...115 seems to be ok). 120 crashes on all my devices (arm with android 6,7,8,9) too.
[Magisk] jenslody:
Bromite 120 (browser not webview) blocks all my other browsers from cinnecting to internet and it also blocks the Magisk grant-root-access-dialog from opening.
[Magisk] Bracher:
Thanks a lot, its a system app so you can only deactivate but this enables you as well to install an earlier version!!!:o