yashsingh1/xdaforums huggingface dataset:
[Magisk] bertino:
Ok, so I tried on pie again and it didnt work. I have both vdex and odex, so i used the latest vdexextractor to convert the vdex to cdex and compact-dex-extractor (from the vdexextracror github issue) to convert that to services_classes.cdex.new, which I renamed to classes.dex and put into services.jar. Then i flashed the nanodroid patcher and got the log. Hope this helps!
[Magisk] gadgetguy08:
I have tried to update Gmscore and still get this:

mata:/ # nupd mg

Updating: GmsCore

Connecting to www.nanolx.org (87.118.73.2:443)

wget: note: TLS certificate validation not implemented

GmsCore.apk 100% 4466k 0:00:00 ETA

Failure [INSTALL_FAILED_DUPLICATE_PERMISSION: Package com.google.android.gms attempting to redeclare permission com.google.android.googleapps.permission.GOOGLE_AUTH already owned by com.google.android.gsf]

!! failed to install GmsCore

What would you suggest?
[Magisk] tom.android:
Wooo!!! Great job now I don't deleted any conflict apps myself. Nanodroid make it for me.
[Magisk] Setialpha:
It doesn't work as dexpatcher 1.6.0 does not support ODEX 039 format from Pie and .6.1 crashes on-device. You'd need to baksmali and re-smali classes.dex to get an older format, or does the cdex script allow for an older API?

Haven't checked yet.

Edit: OMG, I just fixed running dexpatcher 1.6.1 on-device! I hate Java, such derp error messages, so simple fix (once you got it). That means: *deodexed* Pie is supported with the next beta build.
[Magisk] Setialpha:
It complains about missing WebView, so I guess you can fix this by installing either Android System WebView or Chrome from Play/Yalp Store.
[Magisk] Setialpha:
I suppose you didn't have GApps installed previously?

You can wait for the next stable build which contains the new GmsCore, use 18.0~beta2, which already has the latest apk bundled or manually place the apk inside the Magisk module.
[Magisk] tom.android:
Great Man .Now I don't deleted some conflict apps myself before install your NanoDroid. its debloate automatically.
[Magisk] Setialpha:
Neither of them two are on the default debloat lists of NanoDroid. You can confirm this by opening the zip and checkin the files CommonInstaller (GOOGLE_APPS variable) and the .nanodroid-overlay file.

Edit: [MENTION=7586138]tom.android[/MENTION]: I remember some Magisk versions conflicted with some WebView implementations. Are you using Magisk?
[Magisk] Setialpha:
NanoDroid-patcher-18.0~beta2+env_test1+pie1.zip

Hi all, a new patcher beta build is now available. Unless something went wrong big time, this is the last beta before this weekend's final 18.0 release.

What's new compared to yesterday's build?

dexpatcher 1.6.1 now finally runs on-device. This dexpatcher release supports O/DEX 039 format, so an

already

de-odexed Pie ROM is now supported. The patcher will still exit upon vdexed or odexed Pie ROMs (which you still need to manually de-odex).

further fixes following env_test, including fixes for some Pie ROMs and a fix for 32bit devices

minor internal changes

What ROMs was this tested?

On my Nexus 6 with:

Resurrection 5.8.5 (Nougat)

LineageOS 15.1 (Oreo)

NitrogenOS P (Pie)

I strongly encourage you to test this release and report any occurring issues.

Download: NanoDroid-patcher-18.0~beta2+env_test1+pie1.zip
[Magisk] bertino:
It works on my OP3 running Nitrogen OS P, manually deodexed.
[Magisk] Setialpha:
AFAIK NitrogenOS P already is de-odexed, so it's services.jar already contains classes.dex, so you could skip deoxing and go straight to patching. At least the last build I tested (I also own a OP3) was like that and the build for my Nexus 6, aswell.
[Magisk] bertino:
Well thanks for the tip! I'll try it on the next build. I just assumed I needed to do it anyway, even though the deodex checker app said I'm deodexed.
[Magisk] gadgetguy08:
Is there a way to turn off logging in /data/adb/logcat? Or do we need to just manually clean up from time to time?
[Magisk] tom.android:
I don't known this before. Yes I'have WebView Trouble.
[Magisk] DoR3M3:
I see I'm not the only one with this... hmm

[MENTION=4187311]Setialpha[/MENTION] did you get a chance to see my logcat for Contacts not working?

Thanks Setialpha! :)
[Magisk] Setialpha:
Actually alles files older than 7 days should get deleted, else you'd need to disable init scripts installation at all.
[Magisk] iacchi:
I am running latest stable Magisk (17.1) and nanodroid (17.9) on LineageOS Nougat and:

For me it works only about 30% of the time.

For me it always works properly.
[Magisk] Setialpha:
I guess you suffer from this issue: https://github.com/microg/android_packages_apps_GmsCore/issues/606

I'll provide a new microG GmsCore build with that added known package, soon™, you can then test whether it fixes the issue.
[Magisk] Setialpha:
Telegram has an PlayStore and F-Droid version. For microG the F-Droid version should be used, as it does not rely on GCM/FCM.
[Magisk] iacchi:
Right, I forgot to mention it: I use the PlayStore version.
[Magisk] Setialpha:
I've uploaded a new microG GmsCore build, labelled 0.2.5.12879-149-477b244. As always use

nupd mg

to update on-device, as root. Compared to the previous build it contains the following changes:

added Google Contacts to KNOWN_GOOGLE_PACKAGES

fix build failing due missing com.vividsolutions:jts

fix build issues [merged from FreeMobileOS]

set package of intent prior to broadcasting [merged from voidstarstar]

The full list of differences compared to upstream microG can be read here.
[Magisk] :
Hi, im getting this error:

Updating: GmsCore

Connecting to www.nanolx.org (87.118.73.2:443)

wget: note: TLS certificate validation not implemented

GmsCore.apk 100% |********| 4466k 0:00:00 ETA

Failure [INSTALL_FAILED_VERSION_DOWNGRADE]

!! failed to install GmsCore

Can i download that apk manual and place it system/priv app ?
[Magisk] Setialpha:
Does the following, as root, work:

pm install -rd /sdcard/nanodroid_apks/GmsCore.apk

? The previous build somehow miscalculated the versionstring and thus had VERSION-141-dirty while this build has it correct VERSION-30-dirty, but obviously 30 is less than 141 thus Android believes it's a downgrade.
[Magisk] :
same Failure [INSTALL_FAILED_VERSION_DOWNGRADE]

i have not download any apk just put that command on termux
[Magisk] Apex Predator:
Also getting the install failed version downgrade error.

Might hold off on the mg and PS updates and just wait for v18 stable.

Sorry Setialpha, usually I would beta test but after the Magisk v17 update debacle last week I have spent to much time getting things back to normal. I decided not to yet again with v17.1 (supposed hotfix) until you release v18, then I can do a full backup and flash both in twrp.
[Magisk] Setialpha:
OK, I've found the issue in the build scripts and worked-around them. Re-Run 'nupd mg' it will now work.
[Magisk] :
thanks worked!:good:
[Magisk] tom.android:
error log v.18.0
[Magisk] Setialpha:
Did you use the Patcher to install services.jar into /system? If so NanoDroid will install itself into /system, aswell (because the Patcher created /data/adb/NanoDroid_FileList, which contains the installer information for System Mode installation). Which conflicts with installation through Magisk Manager. You would need to install through TWRP.

Edit: I'll re-upload Full, microG and F-Droid packages which will exit in this constellation with a proper error message, instead of going crazy.

Edit 2: re-uploaded Full, microG and F-Droid packages.

Edit 3: just for clearification: if NanoDroid is installed as Magisk Module, then the Patcher will install the services.jar into that module. If there's no NanoDroid Magisk Module, the Patcher will install into /system. Programatically what comes first 'takes the lead'.
[Magisk] heisenmark:
Hi guys I have updated nanodroid to 18.0 from 17.9 (last stable). I noticed that I lost GCM registration for alla apps. How can i restore them? I'm on RR 7.1.2 with magisk 17.1 and nanodroid (full) updated from recovery. Thanks!

Edit: Also I can't enter play store (error RH-01) even if I gave again fake signature permission through terminal
[Magisk] iacchi:
I can confirm this. After update GCM is set to OFF and after re-enabling it I also had to grant microG core service all permissions to work properly. Location backends also got de-activated. I guess I have to re-install apps to enable them again?
[Magisk] tom.android:
(microG-settings ---->Self check)

This error occured when i changed from vertical to horizontal view 4-5 time. After that unifieNLP will not registerd in system till restart mobile againt.
[Magisk] Setialpha:
Dang, yes, I'll upload 18.0.1 hotfix soon, with a fix for the settings loss.

Regarding PlayStore RH-01:

a) you need to grant *all* permissions it asks for

b) a reboot after re-setup of microG is required.

Please report microG bugs to github.com/microg/android_packages_apps_GmsCore

Edit: or, if you have a Substratum theme that themes the Play Services, disable that overlay, as it would not be compatible with microG.
[Magisk] iacchi:
Do you think that after you release the hotfix, all GCM registrations will be back, or are they lost now at least for me and heisenmark?
[Magisk] Setialpha:
18.0.1 hotfix release

Hi all, the hotfix release 18.0.1 is now available. Sorry for the trouble, upgrading NanoDroid is safe again.

First of all: 18.0 has

many

changes, so be sure to read the original announcement post..

Second this is the list of Changes in the 18.0.1 hotfix relase, compared to 18.0:

## 18.0.1.20180907

### Bug Fixes

* CommonInstaller
* fix microG GmsCore, PlayStore and microG Services Framework Proxy loosing data and permissions after upgrade
* if System Mode installation is detected, exit the installer if run from Magisk Manager

### General Changes

* CommonInstaller
* minor code improvements
* fix doubled "!!" in error strings

Download links

Download from Nanolx (AFH link will follow tomorrow).

Bug reporting

In case of errors, please provide

/data/adb/MODID_log_INSTALLDATE

/data/adb/MODID_twrp_INSTALLDATE (TWRP Installation)

logcat (if applicable)
[Magisk] Setialpha:
lost, sadly, unless you have a recent /data backup, sorry.
[Magisk] iacchi:
No, but it's ok. It seems that apps are re-registering themselves without needing to reinstall them. I will update anyway.

EDIT: scratch that, I made a backup of /data before upgrading. Should I update to 18.0.1 before restoring it?
[Magisk] Setialpha:
When you restore /data from TWRP, the magisk.img will also be reset, so first restore then upgrade.

If you just restore the app data alone, the order shouldn't matter.
[Magisk] iacchi:
Ok, data restored and everything seems to work. Thank you very much again for the help and especially for all your work.
[Magisk] pavanjadhaw:
I am pretty impressed by your work. This is what I ever wanted.

But can you make a custom zip which will remove /permanently uninstall all the psuedo freezed apps and add all the apps to the system that nanomod adds?
[Magisk] Setialpha:
Ah, crDroid... did you explicitely grant signature spoofing permission to Play Store? It's not auto-granted afaik.
[Magisk] Setialpha:
That sould be easily automizable thing to do. I'll have a look.
[Magisk] purval6300:
can you guide me how to patch framework for signature spoof
[Magisk] pavanjadhaw:
Cool, I am fan of FOSS apps very much and to my surprise I use mostly all the apps included in your nanomod so its nice thing to have.

I don't know if other users will benefited but I would be.
[Magisk] Setialpha:
If you're on Linux use framework-patcher.sh in the github repository (link in first post), if you're on something else, klick on the Haystack link in first post and read the instructions.
[Magisk] LilBlinx:
Works well on Xperia M2 with Omni. With ResurrectionRemix I had to run the framework patch
[Magisk] Setialpha:
Yup, afaik OmniROM and crDroid are the only pre-patched ROMs broadly available.
[Magisk] slothdabski:
Working well on oneplus3 with AEX ROM!! Using micro g and my Google apps login just fine and play store 100% functions
[Magisk] f41lbl0g:
I got it to work as a user app, but not through nanomod.

Do you know how I can grant play store spoofing permission manually? For microG I had to click on the tick and it brought up a spoofing popup, but I don't know how to get that popup for Phonesky.
[Magisk] Setialpha:
I guees you installed my modified version as user app? Else IAP won't be possible, because the original version does not have signature spoofing (obviously), only mine.

If you did not install mine as user app, uninstall play store and install the apk from /system/priv-app/Phonesky/Phonesky.apk.

Signature spoofing permission should be auto-granted. I was wrong before, but after installing crDroid on my tablet I saw the permission was indeed auto-granted.
[Magisk] Setialpha:
I've updated the Issues paragraph in first post. Currently there's a bug in Magisk (#155 in the github issue tracker of the Magisk project) that on some devices affects either Play Store or microG Droid Guard Helper (they crash).

I re-worded that paragraph and made the instructions on how to fix that issue locally more clear. If you don't have any issues with microG DroidGuard Helper or Play Store crashing, you can safely ignore this.

I provided topjohnwu with logcats, boot image and stuff, so let's wait and see.
[Magisk] :
So just to clear things up, if I dirty flash my rom to update, will I only have to patch it via framework-patcher.sh (as this rom doesn't have signature spoofing by itself) and nothing else or it has to be clean flash with everything again?
[Magisk] Setialpha:
Yes, only re-run framework-patcher.sh, that's enough.
[Magisk] Jonyjack:
Hi, the link to microG homepage is not working. I get a 404 error.

Thanks ;)
[Magisk] Kungencortes:
Getting google play store service error, in microg settings signature spoof not active for phoneksy?

im on lastest omnirom.
[Magisk] Setialpha:
Can you grant permission for fakesign in Settings > Apps > Google Play Store ?

Else I'd need a logcat to see more.
[Magisk] Kungencortes:
Wheres the fakesign option?

http://imgur.com/YZXfDE8
[Magisk] topyli:
Am I mistaken, or are all the apps you mention also installed? I'd prefer not to have a preconfigured list of apps. Is there a way to customize what apps are installed? Even better, to install F-Droid only here?
[Magisk] Kungencortes:
Cant find a logcat apk for noguat..
[Magisk] Setialpha:
That's not a bug, it's a feature. See Alter Installation in first post.

Though it should not be active for the microG module by default, I'll correct the default parameters, as expected to be.

They are not uninstalled, just disabled. See 'nanomod-overlay --help' for possible options regarding those overrides.
[Magisk] xaaaj:
does google drive and gmail works with microG? just want to confirm cause i want to try this to get more battery life.

thanks in advance.
[Magisk] Oswald Boelcke:
I use microG for nearly 18 months now but mainly in order not to be condemned with Google. However, I didn't experienced less battery drainage through the use of microG.
[Magisk] Setialpha:
9.0 beta4

The fourth beta of version 9.0 is now available, that's also likely the last one, except any major issue occurs. Changes since 9.0 beta3:

disable pseudo-debloat feature for microG package by default

update Play Store to 7.8.74.P 1) 2)

add an uninstaller package 3)

change the way permissions are set in installer

Download from AFH , for beta4 all 5 zips are available.

Please test and report any occurring bugs with the following information provided

logcat

recovery log

whether using default or custom setup

1) I managed to make it work by removing InstantApps from AndroidManifest, so that feature won't work, though I never seen it (yet) in real life.

2) this will obviously stop Play Store from trying to update itself endlessly (and crashing 'cause that fails)

3) only works for the Magisk Modules, when flashing in System mode the uninstaller won't work and there won't ever be an uninstaller for System mode, just re-flash your ROM and that's it.
[Magisk] anunaym14:
Okay! Thanks for the info!

But, whhat about that play store crash and update thing?

It crashes every 5-10 mins and updates itself each time after the crash!

Any idea of why it is happening?
[Magisk] Setialpha:
See one post above yours.
[Magisk] marcdw:
Couple of tests of v9.0 beta 4, microG package.

Device: ZTE Axon 7 A2017U, 64bit.

ROM: crDroid v3.2.

Test 1, /system: Play Store still not installed. Getting Yalp Store instead.

Recovery log: https://mega.nz/#!6ZAzADYT!rLg93xhElysH8TUsg5DwG7ur0elj6pW0X0Fxqmy0cok

Test 2, Magisk: Default launcher still being disabled.

crDroid Home or com.cyanogenmod.trebuchet.

Recovery log: https://mega.nz/#!iQAAkSRT!wa27ryntNzIvPL6jxWvx9NYlLwO54jx1WlVLo2RqY0M

ZTE Axon 7 A2017U, AospExtended v4.2 ROM, microG (NoGapps), Tapatalk 4.9.5
[Magisk] schorsch.funke:
Installed beta4 microgG variant and everything works fine, as it should. My rom is RR unofficial from Zenith

Thank you for work and time.
[Magisk] Setialpha:
For 1 I need logcat while system running

For 2 make sure you don't have an old configuration file left over
[Magisk] pbeckmann:
Herr too! TugaPower with integrated signature spoofing and LinOS Base 14.1
[Magisk] anunaym14:
Yes, did that already!

I asked just because I am using stable version!
[Magisk] Setialpha:
9.0 stable

So version 9.0 stable now available. Changes since version 9.0 beta4:

Fix Play Store crashes on fresh installation

Several fixes regarding nanomod-overlay script

Let the installer make the nanomod-overlay script remember the zip directory

Let the uninstaller also remove configuration files

Let the uninstaller also remove /system/.nanomod-patcher file

Update Simple Calendar and Simple Gallery

Complete ChangeLog since version 8.0.20170521

* Internal Changes
* shiny new installer
* cleaner and easier maintainable code
* several improvements to `/system` mode installation
* for microG, F-Droid and full packages
* fix **GNU Bash** installation in microG package
* drop Launchers from list of pseudo-debloated applications in microG package
* disable pseudo-debloat feature in the microG package by default
* NanoMod installers for full and microG package support configuration files located in the same directory as the zip, make the `nanomod-overlay` script remember that path
* also fixes bug that `nanomod-overlay` does not work outside of the installer
* better error message in `nanomod-overlay` script if configuration file does not exist
* install Maps API version 1 by default
* add an **uninstaller** zip which will uninstall any NanoMod Magisk Module
* checks for all three (full, F-Droid and microG) packages and removes them if found
* does not work for system mode installation (and there won't be an uninstaller for that)
* Updates
* Simple Calendar (2.5.1)
* Simple Gallery (2.10.6)
* NewPipe (0.9.7)
* Nominatim Nlp Backend (1.2.2)
* Termux (0.50)
* PlayStore (7.8.74.P)
* VLC (2.1.8~beta)
* Yalp Store (0.15)
* Twidere (3.6.15)
* OpenLauncher (0.5.1)
* Open Camera (1.38.1)

Download from AFH.

When upgrading the microG package from 8.0 to 9.0 first flash the uninstaller to ensure no outdated configuration files exist. Then install the microG package. This is also recommended when switching between the microG and full package.

While the uninstaller does not remove NanoMod when installed in system mode, it does remove the configuration nevertheless.

Doing so is not required when upgrading the full package as the default configuration files have not changed for it.

This is now also mentioned in the README.
[Magisk] Phil_Smith:
This is just awesome! Flashed nanomod-microg and -patcher over slim7 on the mi5. Works perfectly! Thanks a lot!
[Magisk] :
Hi guys. I'm having some difficulties with the patcher zip and wondered if you can help. So I flashed RR on Nexus 5x, wiped cache and dalvik, flashed my kernel, wiped cache and dalvik, flashed patcher zip, waited 20 mins, worked but when it boots I get a 'android is starting' message after boot that seems to be stuck. At least 10 mins. I tried booting into twrp and wiping cache and dalvik but same message. Any ideas?
[Magisk] Oswald Boelcke:
I experienced something similar on Samsung i9305 with RR v5.8.3 when I tried using NanoMod v8. For that reason, I reverted to v7, which worked for me perfectly.
[Magisk] :
Was this with the patcher zip?
[Magisk] Oswald Boelcke:
Please don't take me for granted but I think so if I correctly remember. It's already a few days ago (actually when v8 was released), and in my age I forget what I don't write down.

I'm always only using the microG portion and the patcher as I had real severe battery drainage with the full NanoMod when I tried it the very first time.
[Magisk] lucastracq:
as mentioned in the OP
[Magisk] :
I tried to follow the OP installation instructions. I didn't however boot the ROM before the patcher zip and magisk flash. I'll try that. Thanks :svetius:
[Magisk] lucastracq:
no problem, but report back if it works or not.
[Magisk] Adzkii:
please add support for google play game
[Magisk] Setialpha:
I'm not the author of microG, that's [MENTION=3999488]MaR-V-iN[/MENTION]
[Magisk] Setialpha:
I'll see what I can do.
[Magisk] Setialpha:
.nanodroid-setup file contains the installer variables, while .nanodroid-overlay filecontains all apps you want to debloat. What's the log from the installer?

When you're in your stock ROM, run the following command and post the output:

getprop | grep ro.build.

Edit: regarding failed installation from Magisk Manager, see the message it prints:

!!
System Mode installation detected, but device in BOOTMODE
!!

check a few posts back my reply to tom.android.

tl;dr you used the Patcher in system mode, thus the installer will follow and install NanoDroid in system mode aswell. If you want Magisk Mode, flash the module furst then the patcher.
[Magisk] tom.android:
Can i edit debloat files list.