yashsingh1/xdaforums huggingface dataset:
[Magisk] shnapsx:
So, all navigation should work normally?

I'm asking this because last time i used microg my apps had crushed.:silly:
[Magisk] piet8stevens:
I can confirm osmand, maps.me, google maps and uber work.
[Magisk] shnapsx:
Nice one. Okey, i'l install it later and will check how it works
[Magisk] super-drone:
How exactly do I get a logcat for this problem? I mean, I barely know how to get a log and I don't know where exactly, could you mention some guide threads?
[Magisk] Setialpha:
14.2

Version 14.2 is now here. Highlights since 14.1:

Framework-Patcher addon.d working again

Framework-Patcher improved and faster

InstantApps no longer patched out from Play Store

Full ChangeLog

* Bug Fixes
* Framework-Patcher addon.d:
* Fix error when trying to mount magisk.img
* Use /dev/tmp for custom dalvik-cache to ensure it works in all cases
* General Changes
* Framework-Patcher package, addon.d:
* drop odex check (dexpatcher fails on odexed ROMs anyway)
* drop separate dalvik-cache creation (decreases required time)
* apply patches in parallel (majorly decreases required time)
* no longer support `nanomod_forcesystem` setting
* other minor internal improvements
* Update dexpatcher to 1.4.0
* Updates (manual)
* Play Store (8.2.55.T)
* built with Apktool 2.3.1 for full Oreo/InstantApps support
* Updates (automatic)
* Substratum (853)
* New Pipe (0.10.0)
* (Simple) Gallery (2.14.4)
* Yalp Store (0.26)
* F-Droid Privileged Extension (0.2.7)

Download from AFH.

In case of errors, please provide

your device's architecture

your device's Android version (not ROM version)

whether installed as Magisk Module or in System Mode

used Magisk version

recovery.log or logcat or both (whatever is applicable)
[Magisk] dirtyreturn:
Geez! Finally figured out how, i mean, steps to take for this to work.

_________

Could anyone give an opinion here?

I decided to use the yalp + fake store option.

The warning about violation of playstore terms came up.

Which option is the 'safer' one to choose?

I guess the actual playstore option, right?
[Magisk] Kjivar:
Use Playstore if you want to install apps you have purchased. Otherwise you'll be fine with yalp+fake. Just sign in with the option fake yalp store account
[Magisk] organite:
Thank you for this nanomod.

You made my transition from windows phone to android in peace.

I'm on LOS (honor 5x kiw-l21) without Magisk.

The LOS rom is well patched for signature spoofing and Nanomod works but when I update LOS OTA I lose Nanomod apps.

The updated rom is still patched but I've to reflash nanomod.zip.

Is it normal?
[Magisk] Setialpha:
Of course, when you install in system mode. That's the drawback in comparison to Magisk mode.

addon.d *would* be possible but I never looked into it, as it's not straight forward, given you can customize NanoMod setup.
[Magisk] organite:
Ok, thank you. I will take a look at Magisk then.
[Magisk] shnapsx:
Setialpha, can you help me?

I downloaded 6 packages: nanomod, nm-fdroid, nm-microG, nm-patcher, nm-setupwizard, nm-uninstaller.

So i read op-post and saw that nanomod have fdroid, microG and patcher included. But when i install just nanomod i have only debloated apps. Am i right?

Or for all nanomod abilities i should install in this sequence:

1. setup wizard

2. nanomod

3. microg

4. fdroid

5. patcher
[Magisk] Mynacol:
The Nanomod package includes everything mentioned in the OP. The fdroid and microg packages only include some of the tools. The setup wizard is an AROMA configurator you run inside of the custom recovery and writes a configuration file. If the nanomod package finds this configuration file, it installs only the selected things.

The uninstaller tries to uninstall everything nanomod has done. The patcher tries to patch your ROM to support signature spoofing, which is a requirement for MicroG.
[Magisk] Setialpha:
No. The big package contains *everything*. Steps 3 + 4 are redundant.
[Magisk] shnapsx:
Okey, one more question: in which way can i get situation when i have configured nanomod to install contact sync but it doesn't work? Contacts have all permissions, i entered my gmail acc, chrome got all my bookmarks. But i don't have any contacts.
[Magisk] gimpy1:
I had that problem yesterday myself (contacts not loading, although the calendar did). What I finally did to get my contacts was to use shadow 53's explanation with the davdroid app.
[Magisk] xerves78:
microg module makes often freezes on lineage oreo :(

someone this problem too ?
[Magisk] Bludwurst:
Someone had said it caused bootloops on Oreo.
[Magisk] xerves78:
i tested it:

lineage oreo without microg = freezes too
[Magisk] rohitdave:
Hi

A noob question sorry.

Is the following sequence correct to install microg with the Setup wizard -

Install Rom

Reboot to Recovery

Install Setup Wizard

Install MicroG

Install Patcher.

I am on Official RR Cancro rom.

I am sorry if this has already been answered, can someone please help.
[Magisk] Setialpha:
No reboot between ROM and NanoMod installation required, else: yes.
[Magisk] Setialpha:
Moto X Play does not yet have an Oreo ROM, so I can't test myself, but this issue seems to be a microG issue, 'xause also reported by non-NanoMod users.
[Magisk] rohitdave:
Thanks for the reply sir will try shortly
[Magisk] super-drone:
Actually I tested microG in an Oreo ROM and it worked perfectly fine, (with exception of unifiedNLP because for some reason that I don't know it won't work in any ROM for me but should work for you people) the only thing its bothering it's that patcher takes a long time to apply, like 5-10 minutes.
[Magisk] kurtn:
I've seen this slow patcher issue with version 13.1. New version is said to be faster. Which did you use?
[Magisk] Bludwurst:
Is MicroG Services Core a system app and location doesn't work anyway? :v

(Just asking because you've made me interested in trying MicroG in some Oreo ROMs for my device, teehee)
[Magisk] Setialpha:
There are packages like the qualcomm one mentioned in 14.1/14.2 that conflict with unifiedNlp. If I can itendtify them I can adjust NanoMod accordingly.
[Magisk] rohitdave:
I tried Microg V14.2, after installing ROM I tried to install the Setup Wizard thru TWRP halfway thru install the phone reboots to the rom

Should I try an earlier version say 13 if so what version of Magisk should I use

My phone is RR Official Cancro MI4 W

Thanks
[Magisk] Setialpha:
I've never heard of such an issue, recovery.log?
[Magisk] kirkirehani93:
[MENTION=4187311]Setialpha[/MENTION] , 14.2 build is superfast ...patches within 6 mins . Thanks for your work:)
[Magisk] super-drone:
I used 14.1 version and was still slow, haven't tried 14.2 tho

---------- Post added at 05:37 AM ---------- Previous post was at 05:32 AM ----------

Well not exactly, apparently location it does works for everyone except me, so you can update to Oreo with no problems (I hope...)

---------- Post added at 05:39 AM ---------- Previous post was at 05:37 AM ----------

So how can I help you to identify them? I'm all yours if you need
[Magisk] rohitdave:
In the GitLab Nanomod thread https://gitlab.com/Nanolx/NanoMod#nanomod Under Installation Process I am under the impression it says to install the Setup Wizard first and then flash rom.

I dont know I am confused

I am sorry but is there any guide on getting a recovery log.

Edit

I think i got it how to get the log in TWRP let me try it.

Thank You
[Magisk] Setialpha:
It doesn't matter when you flash the setupwizard, as long you do it before NanoMod. It just creates configuration files.

In TWRP go to Advanced > Copy log to SD. You'll then find the recovery.log file in /sdcard.
[Magisk] hungvip2001:
I try to install the full pack, but every time it error. Try to save the config file to data, sdcard, but can't fix.
[Magisk] Setialpha:
What error?
[Magisk] hungvip2001:
[MENTION=2613559]satia[/MENTION]lpha

Sorry i forgot the screenshot.
[Magisk] slothdabski:
I don't not get the wakelock with microg
[Magisk] rignfool:
So...

I know this is tough to quantify... But is your battery life "better" running microg?
[Magisk] Sivakkumar7:
[MENTION=4187311]Setialpha[/MENTION],

I got the same error message mentioned in earlier posts while installing DU & AOSP Extended roms in my mobiles ( Moto-E,Redmi Note3 & OP3T). I tried both the test flashable zip files for on-device-framework patcher.both are working great.Successfully patched signature spoofing on DU and AOSP Extended.

Thanks for this awesome mod and on-device-framework patcher.Now people like me who is having limited software knowledge can try different roms without waiting for signature spoofing support.

Great work.:good:
[Magisk] Oswald Boelcke:
No, my battery duration has not increased or drainage decreased, however you'd like to call it.

But this wasn't my initial intention by going GApps free. If interested you find my objectives here.

Actually, while I still was using microG on Resurrection Remix (RR)-MM-v5.7.4 with custom AGNi-kernel v4.5.5 and Xposed my drainage was about 1.5% per hour, what suited me fine. That setup is still my fallback as daily driver if I'm getting annoyed by Nougat.

A few days ago when I read first about this fantastic module, I decided to go for RR-N-v5.8.3 with its ROM inherent kernel (not too many custom kernel for Nougat and my device available) and to make it GApps-free by support of Magisk and NanoMod. My wife's and my sister-in-law's i9305, both on RR-N-v5.8.3 but with GApps-Pico, drain acceptably around 1.5 - 1.7% per hour.

I started with the "full" NanoMod and Magisk v12 but experienced an unexpected drainage of 15.9% and during the second logging period 16.8% per hour i.e. my battery was nearly dead (down to 3%) within about six hours, what was unacceptable to me. I uninstalled the full NanoMod module, and I'm on the NanoMod microG module since this morning i.e. actually I finished the setup of my device late noon. Since about 1400 hrs, I'm letting it idle to take an idle BBS dump later. I'm going to report the result in the above link thread as soon as I've finished.
[Magisk] Setialpha:
That's strange, I never experienced any drain. I suppose some app went amok. In case it ever happens again a logcat would be nice, to check which app and why. My device (Moto X Play wit RR and Squid Kernel), uses ~2% over-night, 1 - 2 days of battery overall, depending on usage.
[Magisk] Setialpha:
Depends, on which Google Services were previously in use/installed. In general microG is more battery friendly, since most GApps ROMs feature the whole buttload. Though, if you used something minimal like Open GApps pico/nano, there might be no difference.
[Magisk] toji12:
how can i uninstall the app i dont need after flashing NanoMod
[Magisk] Setialpha:
Maps v1 API is part of NanoMod, too. You need to set

nanomod.mapsv1=1

in the setup file. See Alter Installation in the first post/README. Supported by both full and microG-only package.
[Magisk] Setialpha:
Either setup desired applications before installation (see the first post/README) or remove them from /magisk/NanoMod/system/app.
[Magisk] Setialpha:
7.0

Version 7.0 is now available, Highlights since 6.1:

on-device framework-patcher now works on ROMs that don't have zip installed

fixed (in-)app-purchases (worked in 6.0, but accidently broken in 6.1)

bugfixes

Notes: due to the fix of the (in-)app-purchases you might need to remove your Google Account and re-add it (if you get error 925 when trying to install or update an app, you will need to do so).

To remove the Google Account go to

System > Accounts > Google > click on the email adress > ... (three-dot menu) > delete

To re-add the Google Account simple go

Play Store

or System > Accounts > add > Google

Sorry for that.

If you

never manually

created NanoMod configuration files, it is recommended that you remove the default ones. In TWRP mount /data and go to Advanced > Terminal and type in:

rm -f /data/.nanomod*

press Enter to execute. That's it (of course you can also use a file manager with root support (like the provided Amaze) and go to /data and remove the files in a graphical fashion).

Full ChangeLog since 6.1:

7.0.20140725
* Internal Changes
* some ROMs don't have a `zip` binary which is required for the on-device `framework-patcher` to work
* it now provides arm and arm64 `zip` binaries as fallback
* all packages: let the installers fails if device has x86/x86_64 architecture (NanoMod only supports arm/arm64)
* full and microG-only packages: if the installers create default configuration files because no user-defined exist, those files get removed after installation
* this is to ensure the users who don't care about them always get the default configuration
* obvioulsy, if you opt-in to create your own setup, it won't be affected by this
* full and microG-only package: if the setup file is incomplete, add the missing properties with default values
* microG-only package: set default value of `nanomod.overlay` to `0`
* microG-only package: create the application overrides if `nanomod.overlay` is `1`
* Fixes
* fix regression from 6.1 which prevented (in-)app-purchases
* fix the microG only package by default installs no app store
* now defaults to Play Store
* Updates
* GNU Nano (2.8.1)
* GNU Bash (4.4)
* F-Droid (0.103-alpha3)
* F-Droid Privileged Extension (0.2.4)
* NewPipe (0.9.3)
* Twidere (3.5.25)
* Substratum (703)
* VLC (2.1.6~beta)
* New
* Application
* (Simple) Calendar (2.3.3)
* Override
* Calendar

Have Fun.

In case if issues: post here or over at github including information what you installed and a logcat. Thanks.
[Magisk] Wo11ven:
Hey dev, what features make this module not work with x86 devices?
[Magisk] Setialpha:
The patcher is not setup for x86/x86_64, many apps won't work as their x86/x86_64 libs are not exposed by this module, some apps don't even properly support x86/x86_64.

In fact it could support x86/x86_64 but I don't have a device to test. No device = No support.

if someone else wants to do the necessary changes, they are free to provide a pull request over at github.
[Magisk] Oswald Boelcke:
Thanks very much. Realised a little bit late, too. However, as soon as some of my apk's could be restored by Titanium Backup, I knew I was lacking the Maps v1 API as it happens to me before your great module was born. Therefore, my immediate action.

My nanomod-settings are already changed.

I've no doubt that you didn't experience this issue. I'm convinced you hadn't realised the module in that case. Anyhow, I was pretty surprised, too; and therefore I apologise that I didn't initiate a Catlog recording. I simply didn't expect that but I attached the two BBS dump I took more or less in the middle of the night as I woke up by red flashing low battery LED indications.

As my wife is currently hospitalised my priorities are on a running system, and if I realise later on that the "microG-only-module-system" is at low power after I watch the football game at home and my wife in the clinic, I'm going to revert first to my former RR v5.7.4 GApps-free system; and I'm convinced to have your consent.

As soon as possible, I'm going to clean setup a configuration with the full NanoMod module, and I promise to take a logcat from the very beginning. It's very much in my own interest that you receive the best information available.

BTW: Realised that v7 is released. Thanks very much for your great efforts to all of us!
[Magisk] culiacanazo:
I'd say it's definitely better, but I have alternatives for everything Google
[Magisk] Draygon:
What version of play store is used in your latest version?

Thanks!
[Magisk] Setialpha:
7.7.31.O
[Magisk] Aaren11:
Trying to use the on device patcher with my V20, running deodexed Not So Stock ROM v6.5, still getting Error 1 in TWRP, even with the latest patcher zip. Not entirely sure what's going on, but running Haystack on my PC seems to indicate the script is having trouble finding all the /framework files for patching.
[Magisk] Draygon:
Are automatic play store updates disabled by default, or will my play store update automatically and break the inapp functionality?

Thanks!
[Magisk] Setialpha:
Please provide /tmp/recovery.log

Provided Play Store has a different package signature, so it's impossible to install official release without removing my modified one beforehand (or using some alternative installation method).
[Magisk] Aaren11:
Please find the recovery log attached. Let me know if there is any further info you require.
[Magisk] Setialpha:
I need the recovery.log.
[Magisk] rohitdave:
Hi

Recovery file attached, one more thing my TWRP is 3.0.2.0 not the latest.

Hope this is what you need

Thanks

Sorry for troubling you over the weekend Setialpha have you had time to check my log sir
[Magisk] hungvip2001:
here is it. any ideal ?

Edit: Next update, can you add an F-droid 's Rss Reader like Flym (still update in Play store) and a contact app?
[Magisk] rohitdave:
Patcher v 14.2 installs in around 3 minutes on Nougat
[Magisk] super-drone:
Yeah on nougat is pretty fast, I was referring to 14.1 on Oreo, which took a long time to apply, idk about 14.2 haven't tested yet and I went back to nougat because Oreo is not stable enough to use my phone as a daily driver
[Magisk] TahirZX:
Im trying out few. Modules.

Can anyone explain to me what this module does? I can't understand from. OP. Thanks I'll highly appreciate it.
[Magisk] rohitdave:
If you are refering to MicroG it basically lets you run your phone without GAPPS.

Without GAPPS you get lower Wakelocks and Alarms on your phone, more disc space, battery life is better, your phone is cleaner and faster without GAPPS.

In NanoMod you have 3 options to select what you want to install, I basically install MicroG which is around 32 MB, other are MicroG + Fdroid around 5 MB or NanoMod around 180 MB.

You can install Magisk v14 with Nanomod v 14.2

You should also read what Shadow has written about MicroG also read the Gitlab repo carefully.

My 2 cents hope it has helped, feel free to ask someones out there to help
[Magisk] kurtn:
Made a comparison: 14.2 is significantly faster than 14.1 on Oreo. But it seems still slow compared to the 13ers on Nougat. Log of 14.2 attached.
[Magisk] hungvip2001:
Edit 2: try with magisk and get the same error, magisk manager crash
[Magisk] rohitdave:
Edit
[Magisk] demonoidmaster:
I don't understand how you don't comprehend those simple instructions..

Flash the setup wizard (rom already installed)

Select what you want / don't want

Then flash either the full nanomod package or just microg

Then flash the patcher
[Magisk] zputnyq:
Hi guys,

I'm new to nano mod.

I have a few questions

Does the patcher works on kitkat stock 4.4.2?

Which package that only contain patcher?
[Magisk] rohitdave:
I have followed every thing as you mentioned. Clean Flashed rom

Thank you for your suggestion, in my post 1572 and 1576, 1582 I have mentioned -

During the setup wizard install thru TWRP, recovery freezes half way thru and phone subsequently reboots by itself.

I have attached a recovery log in post 1582

I am already using MicroG without the setup wizard and every thing works fine.

I am a quite a noob and at times find certain points difficult to understand may be due to age:)

All help is appreciated
[Magisk] kurtn:
I think, that's no good idea. Stock typically including gapps and being odexed. Preferred method to get rid of gapps: flash a custom ROM. In case that ROM has no signature spoofing (microg support) you can flash the patcher. Its an extra zip not included in any package.
[Magisk] demonoidmaster:
I see
[Magisk] husseinaltaaf:
Getting Problem with NanoMod, i have followed all insttuction

Flashed SetupWizard

Flashed rom

Flashed Patcher

Flashed Magisk

Flashed NanoMod

Reboot

But that happens. When the first start setup appeared also it infinitetely checks for connection!!! I had to turn off wifi to finish setup.

I have also setup MicroG Account!

But this always appear and play store not working and when pressing Home Button it goes to Account setUp Google Account as you last Reset.... but click setup does Nothing

Help pleasee
[Magisk] Setialpha:
I assume you didn't setup microG, as in the instructions. Also flash patcher last.

At everyone else: I'll be looking into the provided logs very soon™.
[Magisk] husseinaltaaf:
Thx. Sorry My rom has GApp in IT! I suppose thats Whats Causing This problem, Right?
[Magisk] demonoidmaster:
You flashed these way out of order holy sh..

---------- Post added at 10:21 PM ---------- Previous post was at 10:17 PM ----------

Also yes, nanomod (microg) is basically what people can use instead of gapps, so if your rom has gapps, after you flash it go to /system/app and /system/priv-app and find any gapps related folders and delete em (assuming you know which ones are google apps and which are folders you shouldn't touch, if you don't know what you're doing then DON'T TOUCH ANYTHING and move on to using another rom that doesn't have gapps preinstalled)
[Magisk] paed808:
Thanks, it works on Lineage OS 14.1 on my Moto G 2014 (titan) Though I had to use the "NanoMod-patcher-13.2.20170906.zip" instead of the newest patcher or it wouldn't work.

Also, the systemless install of the Zelda sounds didn't work so I installed them manually.

---------- Post added at 11:40 PM ---------- Previous post was at 11:17 PM ----------

One problem: Google Play Store crashes when I select "install" on an application, I checked the logcat, something about being unable to start AppsPermissionsActivity.
[Magisk] kurtn:
Patcher 14.2 is really fast. But it has a problem when it comes to dirty flashing.
[Magisk] Ex_FallenSkyTear:
for update os, lineage, i can just flash patcher after rom?

i only use nano-microG.
[Magisk] kirkirehani93:
+1
[Magisk] kurtn:
Patcher 13.1 survive dirty update. No need to flash. Survival of microG depends on magisk. Ale5000 and shadow53 have microg zips that survive without magisk.
[Magisk] piet8stevens:
nanomod-overlay

Sorry - it is not clear to me where I should specify the build.prop I want to modify. Is this only via script on a PC or can I also specify props in the .nanomod-overlay file? Or anywhere else on my phone? Note: I also do not know how to use resetprop for Magisk directly. Either solution would work for me, but so far, I have been doing everything via nanomod on my phone, which is a very convenient way of getting the changes I want. Thx for that.
[Magisk] husseinaltaaf:
HMM Thx but i have tried that but Getting BootLoop. And yes i know what i deleted! But anyway thx again. I don't use NanoMod anymore! :)
[Magisk] demonoidmaster:
If it bootloops then your device/rom isn't compatible or could be something else unrelated to nanomod
[Magisk] Ex_FallenSkyTear:
my playstore don't work:

i have magisk 14.0, with nano-microG + patcher.

os is lineage.

my problem is download: tap on "update" or "install", agree the permission's app, but download don't start.

and two apps say device is incompatible, but i had installed.
[Magisk] Setialpha:
You run theese commands on a terminal on your phone, eg. the supplied Termux, as root. To become root issue the following command in Termux (and grant permission):

su
[Magisk] Setialpha:
Did you follow the full setup instructions for microG? Did you reboot your device?

Else I need a logcat to investigate (various tutorials on how to get it here on XDA).
[Magisk] Setialpha:
The installation of the sounds works for me, the next time you try to install/update, you may provide the recovery.log, so I may check what's wrong on your end.

So, where's the logcat?
[Magisk] Ex_FallenSkyTear:
yes, i followed install guide, i also tried to reset and reinstall playstore and microG...

an custom kernel can influence it?

and for a logcat, i found only this, i hope is correct.