yashsingh1/xdaforums huggingface dataset:
[Magisk] guest4711:
Yes, use an app like aLogcat ROOT (View system and app log) - https://f-droid.org/app/rs.pedjaapps.alogcatroot.app or OS Monitor (Monitor the Operating System) - https://f-droid.org/app/com.eolwral.osmonitor
[Magisk] HemanthJabalpuri:
Sir we use this where we have issue is going on right?
[Magisk] guest4711:
Yes.
[Magisk] Hb20032003:
But when I flash patcher it says unable to patch services.jar
[Magisk] HemanthJabalpuri:
Sir [MENTION=4187311]Setialpha[/MENTION] this is the log taken by OS-MONITOR. ..

I dont know if it is correctly taken or not...

since it is first logcat.....

The issue is i cant able to tap on signin or cancel in microG setup wizard.....

I flashed microG.....
[Magisk] Setialpha:
So, where's the log, so I can actually check what's the issue?

Hmm... it shows errors in microG itself, you're better off providing a more complete logcat over at microG, seems to be related to android support library.
[Magisk] DoR3M3:
[MENTION=4187311]Setialpha[/MENTION]

I replied back to you that I copied the services.jar into /system/framework, did you see my recovery.log, does it show/help?

https://xdaforums.com/showpost.php?p=77487212&postcount=3858

In the link above, would you please be so kind as to look over the steps I am doing, if they look correct?

The only thing I didn't do is connect phone with PC while in TWRP, mount /system read-write.

We are suppose to run adb while the phone is in TWRP mounted /system read-write?

Sorry if you mentioned this before, I said in the past I had vdex and odex files on my phone and you said to follow the VDEX method on the tutorial, but I forgot when I asked you if said this work on Stock Oreo 8.1.0?

I also can't update nupd mg on Stock Oreo 8.1.0, please see the attached screen shot I used NanoDroid-microG-17.9.20180818 with nanodroid_overlay=1 but I have Xposed with FakeGapps, would that mess it up?

Thanks
[Magisk] vloli:
First sorry for my bad english. and thx for you apps

my rom is nitrogen 7.1.2 with signature spoofing. and magisk

it work fine with ale5000'version( microG unofficial installer) untill 1.0.31 beta.

so i want try this magisk version

i del all thing ale5000'version then drity flash NanoDroid-microG-18.0~beta2.zip with twrp.

after reboot i can see it in magisk

i open it can get permission from signature spoofing. ( it seem i dont need to flash the NanoDroid-patcher?)

and i can login google account

But,other apps cant detection microg.

when i run some apps need gapps it ask me for the gapps (sorry my english)

and i run google photo and google drive it dont login auto. cant login.

why?

i will clean flash but i dont think it will work. i trhy it before.
[Magisk] Apex Predator:
Some potentially a stupid questions incoming, if so please forgive me. I've been using Nanodroid for a while now and everything has worked for the most part. I keep up with this thread out of interest and to stay across latest developments. However, the last week or so has seen a flurry of activity that has left me quite confused.

It started with all this talk of vdex patching and whatnot else going on with the v18 betas. I have been fine up until now and currently on v17.9. My ROM is AICP v13.1, an Oreo ROM that is pre-patched for signature spoofing. That being the case, do I need to worry about all this talk of patching, deodexing and other stuff that is slightly out of my current knowledge base?

If things work for me as is, is it better to wait for a stable version before updating or can I go ahead and flash a beta and continue to have things function. I usually flash the full package with microG, F-Droid, some apps and some system debloating. Will I have to do any of this patching stuff or is that only for people whose ROMs are not pre-patched?

Bonus question that's been on my mind for ages: initially I tried to use fakestore only as I have no need for proper play store. However I found I could not achieve an error free environment without PS installed. For example, some substratum themes wouldn't work, Protonmail would moan about it and wouldn't do push messages. So if it's Gmscore that's so critical, why does Protonmail only complain until PS is present?

I would really like to not have PS installed but having fakestore only, with or without Yalp/Aurora just doesn't seem to let everything function. Btw I don't sign into it or anything and I allow it no permissions, it just sits there doing nothing but making me resent it's presence yet also being glad it keeps the errors away.
[Magisk] clewis.it:
Regarding NanoDroid Patcher, it only applies to ROMs that don't have built in support for signature spoofing. AICP has signature spoofing built in, so you don't have to worry about that.

The issue regarding fakestore is different. I noticed that when the patcher or xposed+fakegapps is used, fakestore gets spoofing permissions. However, on AICP and crDroid, you need to grant signature spoofing in the app permissions. This works with Play Store, but fakestore does not request permissions. I'm thinking fakestore needs to be modified to request that permission, unless somebody knows how to force that permission to be granted?
[Magisk] Namnodorel:
Depends on the implementation. If the permission is a priv-app/system one, then it needs to be declared in system/etc/permissions/ for the app to have it.
[Magisk] tom.android:
1.Sometime microG services core has stopped. when changes screen-view to horizontal.

2.Can't use nanodroid-overlay --update

NanoDroid 18.0 beta 2
[Magisk] iacchi:
I may have missed this in previous conversations, but in any case I will post this information in case others have my same problem. I always had nanodroid configured to install F-Droid and Yalp store only. After upgrading from 17.2 to 17.9, apps started complaining that Google Play Services was not installed and the related option was unticked in microG self-checks. I had to modify .nanodroid-setup option nanodroid_play from 2 to 4 to install FakeStore as well to make everything work properly again.

I wonder: what's the point in letting people install Yalp store only if it throws errors in the system afterwards?
[Magisk] inVain_theGenuine:
I think I'm having a similar issue regarding to the overlay feat on the miui 9.5.8.0 for RN4, I'm using NanoDroid 17.9.

On my other phone (miui 9.5.7.0 on mi 6x) I had no issue with the NanoDroid overlay feat.

I've suspicion that magisk is preventing me messing with the system partition since I have both the advanced settings option thicked on the RN4.

the attached, is my settings on my wayne (without any gapps /uG); I was forced to restart everything on my RN4 since I bricked it :D

would you confirm your advanced magisk settings for me?
[Magisk] clewis.it:
That seems simple enough. It looks like NanoDroid already puts fakestore in /system/priv-app. So, all we should have to do is add a file that tells it to enable the SIG spoof permission? I will double check that next time I install AICP.
[Magisk] Setialpha:
We can't assume everyone wants both, so both opportunitys are given. This change was advertised, btw.

Theese settings are device related and auto detected if they are required. Theese checkboxes are to give users the possibility to force them.

NanoDroid already contains the permissions file required. Though it may not apply in all cases, if you flashed NanoDroid on a non-clean ROM. You can use the 'npem' command as root, on device, to grant permissions.

Sometimes an old Play Store installation may interfere. Try deleting /data/app/com.androud.vending* and /data/data/com.android.vending to be sure and reboot.
[Magisk] Setialpha:
Can't reproduce. What's the log/output?
[Magisk] iacchi:
Thank you for the reply, Setialpha. I will find the relevant part in the thread and re-read it.
[Magisk] inVain_theGenuine:
if I set "nanodroid_apps=0", should I place the ".nanodroid-apps" on SDcard as well?

kindly see the log (it was taken with the NanoDroid 17.9)

so, I was still keeping my setup files from the previous installation (without .nanodroid-apps being present on the SDcard) and revert back to the NanoDroid 17.8.

and to my surprise, the overlay manager is doing fine, but sadly I don't save any log since I was on despair :D

oh,

could you give an option to exclude the f-droid apps from the installation of NanoDroid's f-droid?

the miui doesn't allow me to directly install anything from f-droid or yalp if any of these were installed as a system app.

I can still install any app without issue if I have the f-droid or yalp installed as a regular app, though.

edit: renaming .log to .txt
[Magisk] lee.wp14:
Unfortunately my device is kind of an old one, thus i'm stuck at twrp 3.1.0 Anyway the latest beta2 works fine. Thanks.
[Magisk] raptorddd:
worked on miui 10 8.1

used NanoDroid-patcher-18.0~beta2
[Magisk] HyperCriSiS:
Does MicroG drop analytics and app measurements?

I wonder if I can stop blocking this in xprivacy, as it makes apps unstable.
[Magisk] Dezqo:
MicroG doesn't change anything about the apps you install...

I have the latest XPrivacyLua and I do not experience any inconveniences and everything runs stable. I don't believe XPrivacyLua should affect your apps in such a way actually.

Are you sure you're not using anything else that changes your apps, MinMinGuard for example?

What exactly do you mean with 'unstable'? Does anything crash? How is the experience different?

I think if you want a *stable* experience then microG might not be the right choice. :)

(Edit: Completely missed that you are using XPrivacy and not the newer XPrivacyLua, in that case I suggest switching to XPrivacyLua as it is stable and lightweight!)
[Magisk] raptorddd:
i use myandroidtools for that. never had problems.. only firebase some apps FC. so i re enable the app.
[Magisk] HyperCriSiS:
I am also using XPrivacyLua.

Especially at boot about 20 Apps crash. Also many apps need to be startet several times before they start properly. I have to recheck if maybe MinMinGuard is the culprit.

My Question was what happens with the analytics of the apps which normally use the Google framework. Do they just get dropped by MicroG?
[Magisk] Namnodorel:
XPL by itself should never make an app crash, much less that many.

microG does not include any proper analytics implementation, so in that way it "drops" them - but that doesn't mean you should stop restricting with XPL, since most analytics (even the Google ones) work on their own as well.
[Magisk] Setialpha:
No. 2 has been fixed today in git.
[Magisk] Setialpha:
If you don't want F-Droid use nanodroid_fdroid=0. Though the F-Droid privileged extension should allow installs? Is it known to F-Droid devs that FDE is broken on Miui ROMs?

When nanodroid_apps=0 it's irrelevant whether nanodroid-apps cfg exists, as it's not used anyway.

The overlay script had a bug in beta2, which I fixed today.
[Magisk] Setialpha:
Great, now I only need to fix addon.d creation, which is broken in current beta.
[Magisk] DoR3M3:
Hi [MENTION=4187311]Setialpha[/MENTION] I replied to you, but didn't hear back?

https://xdaforums.com/showpost.php?p=77503527&postcount=3887

Summary

1. I have odex and vdex on phone, so I'm doing the VDEX tutorial

2. Not working on Stock Oreo 8.1.0

3. I didn't mount phone in TWRP system rw, maybe the problem and we do adb in TWRP?

There's a link above, and a link also in that, showing everything I'm doing.

I'd love to be able to deodex the stock oreo, but NanoDroid-patcher-18.0~beta1+vdex_9 doesn't seem to be doing anything, and I attached a recovery.log in the links above.

Thanks! :)
[Magisk] basem_ym:
From now on, Let's not pollute this thread with large logs PLEASE!!

You can paste your log on pastebin and post its url, very simple.

or at least save your log as text, compress it and upload it as attachement.

(first one is prefered!)
[Magisk] DoR3M3:
Manual deodex hasn't been working for me, following the manual steps and then using the latest beta patcher, but I realized I didn't mount the system rw in TWRP, going to try that now, and run the adb cmds in TWRP, I hope this works...
[Magisk] Setialpha:
Stay tuned. I still have a few things on my todo list.
[Magisk] DoR3M3:
Hi Setialpha, I was starting to think I am becoming a bother! LOL

Thanks for your kindness and understanding...

By the way, this time I mounted the system rw in TWRP, then ran the cmds and then used the NanoDroid-patcher-18.0~beta2.zip and the install completed! WoOt...

But running the cmds for me on an Essential in TWRP were instead;

adb pull /system/system/framework framework

adb push framework/services.jar /system/system/framework

Also the latest vdexExtractor created framework/oat/arm64/services_classes.dex.

Well I finally FLIPPIN got it! YEAH! Either it was doing it all in TWRP which I didn't do before, or the latest NanoDroid-patcher-18.0~beta2 was the trick, and I assume running in TWRP adb cmds was what I needed.

Anyhow in microG System spoofs signature is checked! ;)

By the way, in the Apps permissions there is no Signature Spoofing listed, is this ok now, or should I still have it to enable for GMSCore & FakeStore?

Cheers

P.S. Is there anyway to keep Google Contacts working? After installing NanoDroid-microG with nanodroid_overlay=1 Google Contacts won't work. hmm
[Magisk] clewis.it:
Thanks. I will have to remember the npem command next time. This was a clean install, so no leftover play store files. I took another look at AICP and found out there's a "Show System" option that was hiding fakestore in the SIG spoofing permissions. Once i hit show system and granted the permission to fakestore, everything worked. Still not sure why the permission didn't show up when I went into the fakestore app info, though. Guess I still need to get used to this ROM.
[Magisk] bertino:
Are instructions for cdex on that list too? Cause vdexextractor is supposed to convert that into dex now, but I haven't been able to get it to work. Thanks for the support BTW
[Magisk] Apex Predator:
This is good news. I will try it out soon. Reinstall ND with fakestore only then get sig spoofing permission locked in. I'm keen to see if it will have the same effect as the mere presence of PS.

Out of interest, do you get the "system process" error when you boot into AICP? It's dismissible and doesn't seen to affect anything but it's an annoyance and I'd love to figure out what's causing it. I got it when i was on crDroid too. Not sure if it's from ND, Magisk, ROM(s) or an app.
[Magisk] kurtn:
Tried on moto e surnia unofficial lineageOS. Pie has a problem with detecting wrong android version. Oreo seems to successfully deodex, but patching fails. Log attached.
[Magisk] clewis.it:
I don't get the system process error on the latest AICP on my Verizon note 4, unless I flash an older boot.IMG. it has other weird issues though.
[Magisk] Setialpha:
Yes, you have to do it from TWRP, because A/B partition scheme may else give unexpected results, say you pushed your patched services.jar into slot A, but TWRP accesses slot B instead.

And that's another reason to use Magisk, because having services.jar in a NanoMod module will ensure having the patched services.jar on any slot.

And yes it's /system/system by default on that scheme. I'll update the docs during the next days.

On self-patched ROMs sigspoof is not part of the permission model, thus not listed in the permissions list ir AppsOps, that's expected behaviour. It's different on pre-patched ROMs.

You have to configure nanodroid-overlay in orxer for it to work properly. Though I dunno whether I handled the case someone uses both novl and gsync oroperly... need to check.

Both of you seem to have linking issues maybe caused by vendor libs not being found... when you execute the following commands (best run from ROM, not TWRP) as root, post the generated file /sdcard/nd.txt:

mount >> /sdcard/nd.txt
ls -l /system >> /sdcard/nd.txt
find / -type f -name '*.so' >> /sdcard/nd.txt
[Magisk] Setialpha:
I haven't tried that yet, it'll only work on GNU/Linux or macOS as of now, neither on Windows (who needs that anyway?) or on-device. Though, I'll have a look.
[Magisk] Setialpha:
That's actually how I know it from all pre-patched ROMs, none show sigspoof under the app permissions, but in the overall permission settings.

Though the 'show system apps' is kinda new to me.
[Magisk] Setialpha:
The next version will be installable into Magisk again, even if you've never booted into ROM, Magisk 17 broke that on a factory clean /data partition.

Also if /data can't be mounted (likely due failed decryption), the installer will error-out.
[Magisk] DoR3M3:
[MENTION=4187311]Setialpha[/MENTION], well I'm finally getting there, at least now I've got Oreo 8.1.0 deodex, and the NanoDroid-patcher-18.0~beta2 working.

This is the contents of my .nanodroid-setup;

nanodroid_microg=1

nanodroid_fdroid=0

nanodroid_apps=0

nanodroid_overlay=1

nanodroid_zelda=0

nanodroid_mapsv1=1

nanodroid_init=0

nanodroid_gsync=0

nanodroid_swipe=0

nanodroid_forcesystem=0

nanodroid_bash=0

nanodroid_nano=0

nanodroid_utils=0

nanodroid_fonts=0

nanodroid_override=0

nanodroid_play=4

nanodroid_nlpbackend=0

So there's only 3 issues now I'm trying to resolve.

1. I thought that nanodroid_overlay=1 is all that's needed to debloat?

2. Google Contacts won't run, it runs for a second, I get a popup saying it's stopped and closes. I thought GMSCore is suppose to allow it to work?

3. I can't update microg with nupd mg. I have Busybox installed from Magisk 17.1

I've attached a screen shot trying to update microg that fails.

Thank you very much for all your time, help and effort you put into this project, it's greatly appreciated! :)
[Magisk] kurtn:
I hope it helps
[Magisk] Tisckkytt:
Documentation says, Android 9.0 is currently not supported by vdexExtractor or smali/baksmali.

How to deodex then?
[Magisk] ydd0ras:
I have deodexed the services.jar successfully on for devices with AOSP 9.0.O or LOS 16, by following the manual way:

https://gitlab.com/Nanolx/NanoDroid/issues/9#note_96859941
[Magisk] you_man:
Guys, does the viber get a push message now or is not it?:rolleyes:
[Magisk] Klizi:
Does telegram messenger get push notifications? after latest magisk update, it started getting crashed
[Magisk] Setialpha:
Theese are outdated instructions, the newest are in the docs. If it works on Pie then the ROM you use either

a) is already deodexed

b) does not use VDEX 019 or ODEX 039 file formats

the latter is pretty assumable, as early LOS 15/Oreo builds also used the 'old' file format from Nougat for a certain time.

Either way VDEX 019 or ODEX 039 are not supported by baksmali, as it fails to load boot.oat (there are issues on smali github open regarding Pie support), vdexExtractor creates cdex instead of dex for VDEX 019, which are not easy to convert to dex.

tl;dr if it works for you LOS Pie still uses Oreo file formats, but that's going to change.
[Magisk] Setialpha:
1) you need to tell it, what to get rid of, see: gitlab.com/Nanolx/NanoDroid/blob/master/doc/NanoDroidOverlay.md (I've checked, there's nothing by default that interferes with GSync).

2) Contacts App works here, no sync though, but what's the log?

3) try again, I've re-uploaded the GmsCore.apk
[Magisk] Setialpha:
Patcher 18.0~beta2+env_test1

Hi all, a new test build for the Patcher is available, which hopefully increases ROM compatibility further.

NanoDroid-patcher-18.0~beta2+env_test1.zip

Feel free to test.

[MENTION=8031265]kurtn[/MENTION] this /should/ fix your posted issue.
[Magisk] Setialpha:
Uploaded modified Play Store 11.6.15. As always updating using

nupd ps

on-device, as root.
[Magisk] Setialpha:
[MENTION=7586138]tom.android[/MENTION] Hurray!
[Magisk] DoR3M3:
Hi Setialpha, you originally showed me this link for the .nanodroid-setup;

https://gitlab.com/Nanolx/NanoDroid/blob/master/doc/AlterInstallation.md

I'm now not sure what you're trying to show me with that other link, that I now have to further change the .nanodroid-setup? I thought you told me before that nanodroid_overlay=1 is the option for NanoDroid-microg to debloat, so that microg is installed properly?

I also don't understand most everything on that page, it reads more like Unix Man Pages, I hope in time you can change the documentation to better explain, rather then look like Man. I hate man in Linux... :(

Man are Reference pages, not a Tutorial, please consider that when writing documentation, that you create them as Tutorials to teach us how to do things step by step, not a reference to look over. I hope you understand? ;)

That link you posted just confuses me further to now understand the differences of .nanodroid-overlay and .nanodroid-setup, meaning, I was under the assumption that .nanodroid-setup handled everything.

So now I'm assuming this?

1). .nanodroid-setup - is just the basic setup/install for microg?

2). Now to debloat we use- .nanodroid-overlay? - (But this is debloating beyond the .nanodroid-setup if we want further debloat?)

3). Where .nanodroid-setup is placed we also place .nanodroid-overlay in the same /path?

In regards to the debloating .nanodroid-setup seems to do the Google debloating needed for microg to install and work, and that's good enough for me. For any other debloat, I then use the Debloat (Terminal Emulator) Magisk Module to remove anything else I don't want.

I'm attaching a logcat, hopefully it will tell you why Contacts is not working?

The re-uploaded the GmsCore.apk, this should now help with updating, nupd mg?

One logcat was to big, so I had to split it into 2...

By the way I am also trying this with the NanoDroid-microG-18.0~beta2.zip

Thanks

P.S. NanoDroid-patcher-18.0~beta2 says; services.jar status: ODEX & NanoDroid-patcher-18.0~beta2+env_test1 says services.jar status: VDEX, and I'm assuming VDEX is correct, because on the Essential it has odex and vdex files. For now NanoDroid-patcher-18.0~beta2 is working for me and patching, but with NanoDroid-patcher-18.0~beta2+env_test1, after about 40 seconds the screen goes blank and flickers blank, and it fails. I've attached a recovery.log for NanoDroid-patcher-18.0~beta2+env_test1, hope it helps.
[Magisk] sxml2015:
How to update

nupd ps command Where to enter?

I only install these two

Magisk installs NanoDroid - microg

TRWP installation NanoDroid - patcher
[Magisk] DoR3M3:
If you have Magisk installed for Root, it has a Magisk Module for it, you need to install BusyBox, you can read about it here;

https://busybox.net/about.html

Then you need a terminal and the simplest one is "Terminal Emulator";

Without Google Play Store

http://jackpal.github.io/Android-Terminal-Emulator/

Google Play Store

https://play.google.com/store/apps/details?id=jackpal.androidterm

Open Terminal Emulator and type su to have root access, if you get a popup, grant it, then type in nupd ps

Profit! ;)
[Magisk] kurtn:
Works. Patcher needs only 5 minutes
[Magisk] tom.android:
nanodroid-overlay --update ......now working
[Magisk] sxml2015:
thank you very much!！！
[Magisk] Oswald Boelcke:
Instead of posting a "thank you" without any further helpful information I guess most of the XDA user rather prefer if you simply hit the "Thanks"-button in the lower right corner of the respective post (or the :good:-icon on XDA Labs), in this case for the advice by @DoR3M3.

Another terminal that is quite often used and available on F-Droid (especially for all those who refrain from using Google) is "Termux". A screenshot from Termux is available in the post by @tom.android directly above yours.
[Magisk] guest4711:
F-Droid has three good terminal applications, which are available using f-droid app, but also using standard browser:

Terminal Emulator for Android (Access Android's built-in Linux command line shell. Unleash your inner geek!) is an enhanced version of the standard terminal (which can be enablef in developers options of some ROMs) - https://f-droid.org/app/jackpal.androidterm

NeoTerm (terminal emulator for the 21st century) offers " terminal here" functionality and script execution from desktop - https://f-droid.org/app/io.neoterm

Termux (Terminal emulator with packages) is modular expandable - https://f-droid.org/app/com.termux