yashsingh1/xdaforums huggingface dataset:
[Magisk] super-drone:
Yeah weird, isn't it? My device is a moto g5 plus with Qualcomm snapdragon so I don't know, I am currently using viperOS nougat 7.1.2, already applied patcher and everything on microG is checked except by unifiedNLP, the most incredible thing is that I already tried 3 different ROMs, 4 if I include lineageOs 15 on android Oreo. It's really weird, I remember when I used microG unofficial installer by ale on aosp extended and location used to work fine, this problem is happening only after I installed nanomod, which is very strange. But thanks anyway [MENTION=5140997]MarcoBobolo[/MENTION]! Gonna do a nandroid backup and try installing some other ROMs
[Magisk] Setialpha:
Patcher 13.4-beta2.1

13.4 beta 2.1 for the patcher is attached to this post. What's new?

fix SecSettings.apk/SecSettings2.apk patching

fix SecSettings.apk/SecSettings2.apk backup

big internal code consolidation

other minor fixes and improvements

As usual feel free to test and report any ocuring issues.
[Magisk] Setialpha:
if you switched between ale5000's unofficial microG installer and NanoMod without wiping /data before, I suppose that's the cause. NanoMod has a re-signed microG GmsCore (which, together with a patched Play Store allows (in-)app-purchases using microG, which normally won't work), Android likely does not properly handle the transistion between theese twor microG packages.
[Magisk] super-drone:
Nope, I figured it wouldn't work, so I did a clean flash of the ROM.
[Magisk] Setialpha:
Then I'd need a logcat, to look into the issue.
[Magisk] kurtn:
Thank you for the hint. My NLP stopped working after gsmcore update. Re-flashing [MENTION=7126506]Shadow53[/MENTION]'s microg did repair NLP.
[Magisk] Shadow53:
Last time I tried, I'm pretty sure I was able to do a purchase with the official microG and the patched Play Store.

I don't make many purchases, though, so I don't quite remember if it actually worked. But I remember having issues with the official Play Store and flashing the patched one and I *think* it worked.
[Magisk] b4rgh3st:
I wasn't able to find a changelog. Do you know what was changed?

And can I just flash NanoMod-microG over my existent NanoMod installation or will this change my microG settings? Just downloading and installing the linked apk didn't work (it says that it conflicts with a package of the same name).

TIA!
[Magisk] Setialpha:
If you have the Full package installed you should also update the Full package. If you want the microG package instead, first uninstall the Full package and the install the microG package.

You won't not loose your settings, when you switch in one go (i. e. remove the Full package and without reboot install microG package, and

then

reboot).
[Magisk] c3p0u812:
I've read through this thread since yesterday. I hate to ask what might be a stupid couple of questions but...

I am wanting to install some of, but not all of, the apps in the 13.4 beta, but I don't understand what file or files I am supposed to edit. A quick walk through would do me some good if possible.
[Magisk] piet8stevens:
You can most easily do that with the setup wizard. It will generate the files for you through an aroma setup.
[Magisk] c3p0u812:
Do you just flash the setup file through twrp?
[Magisk] Setialpha:
Yes, though you actuall run the SetupWizard, rather than flashing anything.

Afterwards flash the package of choice.
[Magisk] piet8stevens:
Yes
[Magisk] c3p0u812:
The only setup file I have are zip files. Where do I find the setup wizard to run without flashing ?

---------- Post added at 10:56 PM ---------- Previous post was at 10:53 PM ----------

Oh. When I try to flash the nanomod setup wizard zip file through twrp it just freezes. Gotta remove the battery to turn the phone off...
[Magisk] Setialpha:
You *run* it by choosing*flash* zip.

Note the word 'actually' in my previous post.

Edit: AROMA only supports arm/arm64, if you're on x86/x86_64, you need to setup manually.
[Magisk] c3p0u812:
Im arm. Twrp is just freezing. I'll try flashfire. I appreciate the help

---------- Post added at 11:53 PM ---------- Previous post was at 11:01 PM ----------

No go...
[Magisk] Oswald Boelcke:
@setialpha: Thanks very much for the continuous work and improvements. Looking for to giving v14 a try within the next days. And copied - Magisk v14 is mandatory with Nanomod v14.

Please allow me to share an observation that might be interesting to others, too. I'm Gapps-free and using microG for more than two or three years, and in April about six months ago I discovered your great Nanomod modules. Since then, I'm using Nanomod-microG but always as a Magisk module; current on Nanomod v13.4-beta1 and Magisk v14.

Already a few weeks ago, I discovered that localisation via GSM cells or WiFi wasn't possible but I didn't mind as I'm usually using localisation via "sensors" i.e. GPS. Due to the very low priority to me I didn't dig into this issue but I knew that gms core and all backends were correctly installed and data bases downloaded and present. The microG self test just did not show the last bottom two tickmarks. Interestingly, it had worked sometimes in the past but I apologise I cannot recapture with which Magisk and/or Nanomod version the issue occured the first time. Just as a remark, the issue was persistent on both of our Samsung i9305.

Just monitoring the post in this thread over the last days and reading about NLP issues, I remembered my own one. First, I followed @kurtn advice here, and flashed @Shadow53's microg but this didn't solve the problem.

Next step was to completely uninstall Nanomod by use of the uninstaller. I used the setup-wizard to create the setup-file to my desire but I've chosen to install Nanomod-microG directly to /system and not as a Magisk module - actually the very first time not to have Nanomod as Magsik module. Rebooted into system and back into TWRP and patched the system.

Back in system, I made all required setups for microG (permissions, backends etc.) and no NLP issues anymore, all marks in self test or ticked, and localisation through GSM cells and WiFi is working!

Repeated above mentioned procedure on the second i9305; also on that device no issues anymore. Conclusion: For whatever reason, the issue occured because Nanomod was installed as Magsik module.

EDIT: I tried to reproduce the issue with one of the two devices. Flashed the uninstaller followed by the v13.4-beta1-setup.zip but did not select installation to /system. Flashed v13.4-beta1-mircoG. Successful installation as Magisk module. Booted into system, check if Nanomod was installed as Magisk module. Set location mode to "savings".

Check microG settings self test: All tickmarks available. Opened OSMand+: Positive and good location.

Obviously unable to reproduce (but I was ready to take a logcat). Somehow, by something I initially did this morning, I "removed" the issue.

NLP is working and good locations via GSM cell/WiFi are provided independent of the way Nanomod-microG is installed.
[Magisk] Setialpha:
So, what does the logcat say? I can't reproduce the issue on my devices...
[Magisk] Oswald Boelcke:
I apologise for not having taken a logcat. As stated I barely use it and most likely didn't capture one due to level of personal priority.

However, as soon as I've time I'm going to fall back and try to reproduce - and capturing the desired logcat. I'll keep you updated.

@setialpha: I tried to reproduce the issue with one of the two devices. Flashed the uninstaller followed by the v13.4-beta1-setup.zip but did not select installation to /system. Flashed v13.4-beta1-mircoG. Successful installation as Magisk module. Booted into system, check if Nanomod was installed as Magisk module. Set location mode to "savings".

Check microG settings self test: All tickmarks available. Opened OSMand+: Positive and good location.

Obviously unable to reproduce (but I was ready to take a logcat). Somehow, by something I initially did this morning, I "removed" the issue.

NLP is working and good locations via GSM cell/WiFi are provided independent of the way Nanomod-microG is installed

Post #1491 amended.
[Magisk] fiswany:
safetynet check Successfull

first thing first

i am on Samsung SM-G900F & RR 5.8.4 and ofc Magisk 14

i was on NanoMod-13 (only patcher+MicroG+F-Droid) and i was like all of you when i go for safetynet chk iget MicroG droid help had stopped .. :(

after releasing Nanomod-14 here is what i did :

before restart i disable internet connection then > twrp > flashing nanomod-13 uninstaller > restart normally (maybe some apps uses push notification will stop working press ok & we will get to that later ) to check that everything is ok (still offline)

>twrp>flash nanomod-14 patcher >flash nanmod-14 MicroG> flash nanomod-14 F-droid> reboot normally

go & check MicroG setting as in full documentation > log in to play store > go to magisk > safetynet check successfull :good:

few things to the dev.

1- all the application registered in google cloud messaging ofc is gone due to uninstallation of MicroG and ofc need to be uninstalled first then reinstalled to be attached to the service. cant we work around that ??

2- after rebooting MicroG core service asked to grant permission for phone, contacts, SMS, location. i granted the permission to the service but when i checked under privacy it used only location and the rest till now never used !! is that normal ?? shall i keep giving the permission or its ok to prevent ??

thanks for ur support, and keep the good work up
[Magisk] Setialpha:
As stated under 'Issues' microG needs to be installed before application, lse they won't register. Given you've rebooted between uninstallation and reinstallation, that's of course no longer the case.

Of course it needs the permissions, else several things won't work. It always had this permissions, but since a system apps was uninstalled and reinstalled Android no longer automatically grants them. It's the way Android handles permissions when system apps vanish.

You should also check if Play Store has all permisdions granted (if that's what you've installed).
[Magisk] fiswany:
play store doesn't have permission to anything but its working fine with me :rolleyes::rolleyes:
[Magisk] Setialpha:
Patcher 14.0a

Small hotfix release for the Patcher: it would aways install the patched files to /system.

* Bug Fixes
* Framework-Patcher package
* fix installation path detection

Download link at top of first post.
[Magisk] nakshb:
Getting error in Google play games any solution..?
[Magisk] Anarchy16:
lol, play games will never work (for now)
[Magisk] Setialpha:
To be more precise: it's not implemented in microG.
[Magisk] nakshb:
Thanks ?
[Magisk] ShapeShifter499:
I'm just curious, why was the keyboard changed?
[Magisk] Shadow53:
Not the Dev, but probably because Hackers Keyboard hasn't really been updated lately and has the same look as the Gingerbread days (or was it Ice Cream Sandwich?). BeHe keyboard is more recent in development and is trying to be a keyboard for programmers as well, iirc.

Also, maybe [MENTION=4187311]Setialpha[/MENTION] likes the keyboard better. I bundle AnySoftKeyboard into my own zip, personally, though I may try BeHe again.
[Magisk] Setialpha:
Actually, that's pretty much it, though NanoMod has both BeHe and Anysoft, as I prefer the latter for normal typing and the former for terminal stuff.
[Magisk] kirkirehani93:
[MENTION=4187311]Setialpha[/MENTION] , Patcher v14 doest works for me now. However its completely flashes in twrp . No errors nothing. On reboot...there is not signature spoof enabled. 13 beta 2 version just worked fines with the same setup.

Setup: NOS O Rom with Radon kernel 5.5
[Magisk] Setialpha:
14.0 or 14.0a? logcat?
[Magisk] kirkirehani93:
14.... Will get logcat...
[Magisk] Setialpha:
Errrr... it should be recovery.log, during flashing, my mistake.
[Magisk] kirkirehani93:
U saved me...i was about to flash to get log again....

There you go...http://cloud.tapatalk.com/s/59c15547f3cb9/last_log.zip
[Magisk] Retseem:
In version 13.2 I had Play Store working but couldn't get UnifiedNLP to be registered to system. Now I was hopefull since version 14.0a has the qualcom fix and indeed I got UnifiedNLP actually registered and all checkmarks enabled, but unfortunately now Play Store is not working [RH-01] error. Using Android 7.1.2, tried both Mokee 71.2 and RR 7.8.4. On Mokee I didn't even get the Playstore icon but just the green Android one. Seems I am not that lucky to get Micro G running since in the past the Galaxy S6 NanoROM didn't work on dual SIM :(
[Magisk] dirtyreturn:
Hello,

the framework-patcher - does that need to be flashed by its lonesome and manually install the apks to work??

For signature spoofing i mean.
[Magisk] demonoidmaster:
Run the setup wizard (flash it via twrp), select what you want (example if you want the sigspoof switch to appear in dev options in settings then tick it in setup wizard, also select if you want the additional apps stuff like fdroid, keyboard, music player etc etc, doesn't include microg or the other stuff because that's installed by default, if you need gsync for calendar & contacts then tick that, etc)

Once done flash the full nanomod zip
[Magisk] kirkirehani93:
Try disabling play store once from the settings and re-enable it. It will work.
[Magisk] dirtyreturn:
Thanks, man!

Just for the sake of understanding , -

the framework-patcher.zip - that does NOT need to be flashed at all?

In what circumstance does that work?
[Magisk] kurtn:
The patcher is one of many methods to get signature spoofing. Here is an overview https://xdaforums.com/android/general/index-list-custom-roms-offering-t3557047
[Magisk] Retseem:
Thanks a lot, that was the trick I needed.
[Magisk] Retseem:
After a reboot the settings cannot be used for about a minute. Seems to take a while for "extra settings" to be loaded. After that settings can be used as normal. I didn't have this issue before applying the nanomod patcher. Anyone elase having this issue? Also "extra settings" asked for root permissions which I granted, but is that really needed?

---------- Post added at 15:16 ---------- Previous post was at 15:09 ----------

I didn't select signature spoofing to be installed in developer options and I assumed that the spoofing would be enabled by default, this doesn't seem to be the case. Now I have patched signature spoofing but can't enable it. Time for another re-flash.
[Magisk] dirtyreturn:
So just custom roms with signature spoofing added work?

Even with the patcher??

Would anyone be willing to check on Unlegacy-Android for the grouper??
[Magisk] gimpy1:
I do what is recommended in the OP under the documentation link. Signature spoofing and safety net both are enabled on my rom (bhb's RR on droid turbo, also AEX rom works).

I do a clean wipe, flash rom, bhb's kernel, magisk, and nanomod, in that order. I then reboot. I then go back into Twrp and flash the patch and reboot again.

Seems to work fine.

I do have to use the Davdroid app to get my Google calendar and contacts loaded. I don't know how else to load them.
[Magisk] kurtn:
No. You need either a ROM with spoofing or nanomod patcher or one of the other methods provided in the link.
[Magisk] kurtn:
Looks like AOSP without microg support. There are nougat, marshmallow and other flavours. Nougat: nanomod

Marshmallow: nanomod or xposed
[Magisk] BootloopedMillennials:
Another case of this happening. It occurred with 14.0a patcher. No errors just signature spoofing wasn't enabled on bootup.

Setup- LineageOS 14.1 (9/22 Build), Magisk 14.0

Manually deleted the patcher files in /system and /system/add-on (i believe was the folder), flashed the 13 beta 2 patcher. That fixed it.
[Magisk] fastguy:
Yep v14a patcher also didn't work for me. I did a wipe on system, reinstalled and did patching with v13 and it was good.
[Magisk] super-drone:
Anyone here using Oreo? I'm using lineage 15 and everything is working fine except by sign spoofing after applying the 13.3v patcher, anyone facing same problem?
[Magisk] pokipokipxorn:
No need to use DavDroid at all

Flash nanomod, configure microg, reboot

Assign permissions to contacts, calendar, contact sync, calendar sync, plus everything microg or google. Reboot

Add new google account, go into account, 3 dot menu sync, u should see contacts & calendar inside. SYNC then Reboot

Launch contacts & calendar, all your contacts & calendar events should be intact.

When launching calendar, will be asked to sign in, just select cancel. It will work.

U can install google calendar or any other google apps later if u like the UI. Remember to assign permission, reboot, sync account, reboot before launching the app
[Magisk] demonoidmaster:
He needs to select gsync in the setup wizard for that to work, contacts/calendars are disabled by default

---------- Post added at 08:17 AM ---------- Previous post was at 08:16 AM ----------

You're using an outdated patcher, most recent is 14.0
[Magisk] gimpy1:
Thx, both. I will look at it in the morning. I have never used the set up wizard.
[Magisk] Setialpha:
14.1

Version 14.1 is now available.

It fixes an issue with the patcher (again) where System Mode installation of the services.jar does not work, Magisk Mode did work since 14.0a.

Also

nanomod-overlay

can add system properties to the Full/microG Magisk Modules, like

nanomod-overlay -A ro.build.type user

remove them using

-R

, or show all added ones using

-L

. That's basically just a front-end to

resetprop

, but it additonally stores your settings in NanoMod Module's own system.prop, so that they persist a reboot. The installers will backup and restore those settings upon update.

Full ChangeLog since 14.0

* Bug Fixes
* Framework-Patcher package, addon.d:
* Fix installation into `/system`
* General Changes
* nanmod-overlay Script:
* add `-C, --cast` parameter, fixes cast not working on some custom ROMs
* uses Magisk to enable `persist.debug.wfd.enable` both on-the-fly and permanently
* on-the-fly setting may not work, in that case, simply reboot
* add `-A, --add-prop` parameter, add system property
* both on-the-fly and permanently
* add `-R, --remove-prop` parameter, remove a property previously added through `-A, --add-prop`
* requires reboot to take effect
* add `-L, --list-props` parameter, list alls properties added through `-A, --add-prop`
* Full, microG packages:
* backup and restore `system.prop` generated by `nanomod-overlay`, if any, during update
* Full package:
* remove `permissions` init script
* Updates (manual)
* Play Store (8.2.40.T)
* Updates (automatic)
* MPV (2017-09-20)

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] Ex_FallenSkyTear:
for update, i only flash new version on the old version, or i need unistall old version befor?

[sorry for my bad english]
[Magisk] dirtyreturn:
[MENTION=4187311]Setialpha[/MENTION]

Arm 32bit

7.1

system mode

asus 2012 nexus 7--- unlegacy-android

Just wondering.

Ive tried to patch and ive not seen signature spoofing appear in dev options.

Any idea i guess?
[Magisk] Setialpha:
Just flash the new version.

Only added, if you've selected that option in the NanoMid SetupWizard, respectively added 'nanomod_sigspoofui=1' in your setup file.
[Magisk] gimpy1:
I've clean installed to most current updates of rom and Magisk and nanomod. Micro g (signature spoofing is enabled), as is magisk safety net (green, passes).

But, when I open up the magisk settings to view "superuser", the magisk app force closes. Otherwise, it seems to be working perfectly. Any idea what I have done to cause that?. Rebooting does not help.
[Magisk] Setialpha:
Known Magisk issue, clear Magisk Manager app data.
[Magisk] Setialpha:
On a side-note: I've updated Apktool to 2.3.1 on my PC. As you may already know NanoMod contains a modified Play Store that allows (in-)app-purchases with microG, which normally don't work. Since Apktool for a longer time did not support Oreo and InstantApps I had to patch that out since NanoMod shipped Play Store 8.x. So from now on InstantApps and KeyboardNavigationCluster (Oreo-exclusive, but what's that?) is no longer patched out, as Apktool can now handle that properly.

Link to my modified Play Store 8.2.55.T (since it was released after NanoMod 14.1)..

You may need to wipe Play Store app data (and if so, re-grant Signature Spoofing permission (on pre-patched ROMs)).
[Magisk] piet8stevens:
Nanomod + Magisk on stock ROM - debload Gapps?

Hi, I have been using nanomod for quite a while on Axon 7 custom roms. [MENTION=4187311]Setialpha[/MENTION]: thank you for all the work and the unbelievably fast support.

I am considering going back to stock rom as I have too many issues on the custom ones (data not working, GPS slow, requiring almost daily reboot, call issue, camera not as good as stock). But I want to remain gappless.

Is it possible to use nanomod to debloat Gapps and Google Play Services, Google Play Store and then use the microG full package just as if I were on a custom rom?

EDIT: sorry for typo in title
[Magisk] Setialpha:
Uff, if the ROM you wanna use is deodexed, it's likely possible (required for patching sigspoof support), though needs some more work.

For example you need to pseudo-debloat anything GApps related, by adding to .nanomod-overlay file (auto-applied during installation, but you can later apply changes using 'nanomod-overlay --update').

If not using Magisk, use the force-debloat Script from the repo (run from adb shell in TWRP), which will also debloat the system accordingly to the file, but obviously it's permanent in that case (until re-flashing the ROM, also asks whether to really do anything, or do test mode, which will only show what would be removed).

I don't know what exactly needs to be debloated, as I don't know whatms included in the desired ROM.
[Magisk] gimpy1:
Thx, that worked (I had already tried a dirty flash of ROM, magisk and nanomod and also just reinstall magisk 14 from magisk manager-nothing worked). Didn't think of just wiping data.

But, although that did work, I also cleared data in a couple of other apps (don't remember which ones). As I was typing this answer in xda labs, it force closed on me in mid sentence. Other apps that I tried to open (such as lightning and amaze, etc.) Also force closed on me. This forced me to go back into TWRP and redo a clean install of everything. As of right now, everything seems to be working fine, safety net, spoofing, contacts and calendar:svetius::).

Thx, for all your help.
[Magisk] shnapsx:
Hi.

Which setting i should enable to make in-app purchase possible? NanoMod 14.1.20170923, safetynet works, singature spuffing enabled, Playmarket installed.
[Magisk] Setialpha:
Nothing, it's already fine, if you've choosen PlayStore.
[Magisk] shnapsx:
Seems like it doesn't work. Tried multiple apps - they all want to pay with my card. Did i do i anything wrong?
[Magisk] Setialpha:
Huh? So, what's wrong with that? Who's card do you expect to be charged instead?

You can instead add you PayPal account to your Google Account, or other payment methods, depending on your country.
[Magisk] shnapsx:
I don't expect any cards. I just want to purchase some things inside app with in-app purchases for free. Otherwise this doesn't work. When i tap on something to buy, playmarket show me standart popup that wants real money to do that. And it wants my real card to pay with it.

So i've decided that in-app purchases don't work.
[Magisk] Didgeridoohan:
For real!? :eek:

What kind of warez do you think this is? I believe you've misunderstood something... Or I hope I'm completely misunderstanding what you're writing.

If you want something that costs real money, you should pay for it with real money. Anything else is theft.
[Magisk] Bludwurst:
I'll give them the benefit of the doubt and assume they want to do an in-app purchase that is being offered for free as one of those cutesy limited time offers.

But it'll still ask for credit card information even if it costs 0$ with 0¢ because reasons.
[Magisk] Setialpha:
Ah, that's true, ask Google, why it is like that.