yashsingh1/xdaforums huggingface dataset:
[Magisk] Primokorn:
I'll include the patched Play Store app into my flashable zip and grant the signature spoofing permission.

Thanks for the feedback.

Did you have to prevent Google Play from updating itself?
[Magisk] espionage724:
I'm not seeing an option to enable Signature Spoofing. Here's what I did:

Wiped everything from TWRP

Flashed LineageOS ROM (lineage-14.1-20171020-nightly-shamu-signed)

Reboot to Recovery

Wiped all but System and set Data and Cache to F2FS

Reboot to Recovery

Flashed Kernel

Flashed Magisk (14.0)

Reboot to Recovery

Copied .nanomod-setup to /sdcard

Flashed NanoMod-patcher (14.5.20171022)

Flashed NanoMod-microG (14.5.20171022)

Flashed NanoMod-fdroid (14.5.20171022)

Reboot to System

.nanomod-setup contains the following:

nanomod_play=2
nanomod_overlay=0
nanomod_mapsv1=0
nanomod_gsync=0
nanomod_swipe=1
nanomod_forcesystem=0
nanomod_sigspoofui=1

microG self-check doesn't see Signature Spoofing support, and I don't see an option for it in Apps -> Settings -> App permissions. Did I miss something? All 3 NanoMod packages flashed without error.

Edit: Got it; I noticed a commit that mentioned to look under Developer options. I then did a clean install and flashed only LineageOS, the patcher, microG, and F-Droid packages. I looked under developer options though and didn't see an option, but microG self-check said it was supported. So I re-did the installation I did above (with Magisk and everything) and then went to Developer options and saw the option to allow spoofing at the very bottom. Toggled it on, went back to self-check, and all was reported well :)

I have to say, NanoMod is pretty amazing :D
[Magisk] Primokorn:
OK so I tried to use the patched Play Store during a clean flash and the Play Store force closes due to a missing librairy. Any idea? I didn't find such a librairy into your zip.

java.lang.UnsatisfiedLinkError: dalvik.system.PathClassLoader[DexPathList[[zip file "/system/priv-app/Phonesky.apk"],nativeLibraryDirectories=[/system/lib/Phonesky, /system/priv-app/Phonesky.apk!/lib/armeabi-v7a, /system/lib, /vendor/lib, /system/lib, /vendor/lib]]] couldn't find "libcronet.61.0.3163.81.so"
at java.lang.Runtime.loadLibrary0(Runtime.java:984)
at java.lang.System.loadLibrary(System.java:1562)
at org.chromium.net.impl.CronetLibraryLoader.a(SourceFile:21)
at org.chromium.net.impl.CronetUrlRequestContext.<init>(SourceFile:17)
at org.chromium.net.impl.br.a(SourceFile:9)
at org.chromium.net.f.a(SourceFile:15)
at com.google.android.finsky.utils.b.a.<init>(SourceFile:8)
at com.google.android.finsky.application.d.cm(SourceFile:126)
at com.google.android.finsky.application.d.aW(SourceFile:184)
at com.google.android.finsky.application.FinskyApplication.onCreate(SourceFile:195)
at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1025)
at android.app.ActivityThread.handleBindApplication(ActivityThread.java:5499)
at de.robv.android.xposed.XposedBridge.invokeOriginalMethodNative(Native Method)
at de.robv.android.xposed.XposedBridge.handleHookedMethod(XposedBridge.java:339)
at android.app.ActivityThread.handleBindApplication(<Xposed>)
at android.app.ActivityThread.-wrap2(ActivityThread.java)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1576)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:154)
at android.app.ActivityThread.main(ActivityThread.java:6239)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:891)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:781)
at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:103)
[Magisk] Setialpha:
The library is in the apk. My installer extracts it during installation. Open the apk as zip file and you'll find lib/arm/libcronetxxxxxx.so insude.
[Magisk] Primokorn:
Where do you copy the file? In /system/lib and /vendor/lib?
[Magisk] totalcmdext:
The problem for rebooting of device is the FakeStore.apk.

I don't have find the reason but it is creating the rebooting when the Location Service is on
[Magisk] Setialpha:
Should both work, or use /system/priv-app/PhoneSky/lib/arm/libcronetxxxxx.so
[Magisk] Setialpha:
You might grab a logcat then and file a bug report over at github.com/microg
[Magisk] Primokorn:
I had another FC (for a different reason) so I decided to use your full mod (for the first time. Sorry if I missed something).

1. Clean flash of my custom ROM (Unofficial RR - 7.1.2_r29 - built-in signature spoofing) + Magisk + NanoMod-microG stable

2. Everything was checked in microG self-check screen

3. I downloaded an icon pack then tried an in-app purchase and the app force closed

10-26 14:56:28.457 4593 4593 D AndroidRuntime: Shutting down VM
10-26 14:56:28.459 4593 4593 E AndroidRuntime: FATAL EXCEPTION: main
10-26 14:56:28.459 4593 4593 E AndroidRuntime: Process: com.android.vending, PID: 4593
10-26 14:56:28.459 4593 4593 E AndroidRuntime: java.lang.RuntimeException: Unable to instantiate service com.google.android.gms.measurement.AppMeasurementService: java.lang.ClassNotFoundException: Didn't find class "com.google.android.gms.measurement.AppMeasurementService" on path: DexPathList[[zip file "/system/priv-app/Phonesky/Phonesky.apk"],nativeLibraryDirectories=[/system/priv-app/Phonesky/lib/arm, /system/priv-app/Phonesky/Phonesky.apk!/lib/armeabi-v7a, /system/lib, /vendor/lib, /system/lib, /vendor/lib]]
10-26 14:56:28.459 4593 4593 E AndroidRuntime:	at android.app.ActivityThread.handleCreateService(ActivityThread.java:3217)
10-26 14:56:28.459 4593 4593 E AndroidRuntime:	at android.app.ActivityThread.-wrap5(ActivityThread.java)
10-26 14:56:28.459 4593 4593 E AndroidRuntime:	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1598)
10-26 14:56:28.459 4593 4593 E AndroidRuntime:	at android.os.Handler.dispatchMessage(Handler.java:102)
10-26 14:56:28.459 4593 4593 E AndroidRuntime:	at android.os.Looper.loop(Looper.java:154)
10-26 14:56:28.459 4593 4593 E AndroidRuntime:	at android.app.ActivityThread.main(ActivityThread.java:6239)
10-26 14:56:28.459 4593 4593 E AndroidRuntime:	at java.lang.reflect.Method.invoke(Native Method)
10-26 14:56:28.459 4593 4593 E AndroidRuntime:	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:891)
10-26 14:56:28.459 4593 4593 E AndroidRuntime:	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:781)
10-26 14:56:28.459 4593 4593 E AndroidRuntime: Caused by: java.lang.ClassNotFoundException: Didn't find class "com.google.android.gms.measurement.AppMeasurementService" on path: DexPathList[[zip file "/system/priv-app/Phonesky/Phonesky.apk"],nativeLibraryDirectories=[/system/priv-app/Phonesky/lib/arm, /system/priv-app/Phonesky/Phonesky.apk!/lib/armeabi-v7a, /system/lib, /vendor/lib, /system/lib, /vendor/lib]]
10-26 14:56:28.459 4593 4593 E AndroidRuntime:	at dalvik.system.BaseDexClassLoader.findClass(BaseDexClassLoader.java:56)
10-26 14:56:28.459 4593 4593 E AndroidRuntime:	at java.lang.ClassLoader.loadClass(ClassLoader.java:380)
10-26 14:56:28.459 4593 4593 E AndroidRuntime:	at java.lang.ClassLoader.loadClass(ClassLoader.java:312)
10-26 14:56:28.459 4593 4593 E AndroidRuntime:	at android.app.ActivityThread.handleCreateService(ActivityThread.java:3214)
10-26 14:56:28.459 4593 4593 E AndroidRuntime:	... 8 more

Full log
[Magisk] Texas_Ace:
I have been running into a strange issue on several phones over the last few days, had the same issue with a note 4 and S5 running lineageOS 14.1 (trying it on another S5 now).

Everything will go great, the rom flashes, Magisk works fine, passes safetynet, ect.

Until I try to shut down the phone. The phone will appear to shut down but the indicator lights on the buttons will never go out as it seems to hang just before shutdown. The only way to fix it is to pull the battery, holding the power button seems to have no effect.

After a reboot it once again works fine until I shutdown.

I have tried every combo of installing that I can think of, it seems to be the microG part of nanomod that causes the problem as if I only flash that it will lockup on shutdown. I have not tried fdroid alone though.

If I install it without Magisk and then install magisk after, the problem seems to go away and it shuts down fine. So it would seem to be the magisk integration that is causing the issue.

What do I loose by having it installed aa system instead of magisk?

I have also tried both magisk 14.0 and 14.3 beta with the same results.
[Magisk] :
I seem to lurk this forum. Nanomod is my lifesaver, I've been flashing every version for nearly 6 months now and haven't had any issues at all. Thanks OP, figured I'd pop out from the shadows to say I appreciate it. (:
[Magisk] Bludwurst:
(Eighty-four years late, but whatever.)

Passing SafetyNet, I think.

And obviously, without Magisk, you can't have any other •°~totally radical~°• Magisk modules, which is a total bummer.
[Magisk] Texas_Ace:
lol, NP.

Thats the strange part, if I install it as a /system and then install Magisk after (I suppose it could be before but easier to make sure it installs as system if I do nanomod first), everything works perfect. It passes safteynet, magisk works perfect and it shuts down properly.

Only if I install it as a magisk install does the shut down break.
[Magisk] Bludwurst:
How mysterious...
[Magisk] mongo0:
I have the same problem;

I don't know what to do with these solutions... which service should I disable?

Can I switch to user app ? Phonesky is fake playstore right?

I only see this notifications from today on.. I updated to NanoMod-microG-14.5.20171022 but it did not help.
[Magisk] Setialpha:
Phonesky = Play Store, FakeStore = Fake Play Store.

Download 'Disable Services' from Play Store and use it to disable 'DailyHygieneService' of Play Store, you'll then get rid of the notification.
[Magisk] Setialpha:
14.6.20171031

Version 14.6 is now available. Highlights since 14.5

switch to official build for microG GmsCore

several new features for nanomod-overlay/novl script

Full ChangeLog since 14.5:

* General Changes
* Full, microG packages:
* switch to official microG GmsCore build, modifying Play Store alone is enough for (in-)app purchases to work
* remove unused variables and aliases from Bash configuration file
* make bash, nano, less wrappers not throw a message if `resize` command is not available
* in case your OS does not have a `resize` command, install osm0sis' Busybox
* nano, less wrappers only set TERMINFO if it actually exists
* add crDroidFilemanager to list of apps pseudo-debloated by default
* crDroidFilemanger = Amaze
* add crDroidMusic to list of apps pseudo-debloated by default
* if `com.qualcomm.location` is found, only add it to the list of pseudo-debloated applications, if it isn't already
* Full package:
* some ROMs call Adaway AdAway instead (not the capital A)
* let the installer handle that case, so the user does not get a double-installation of Adaway
* if an application provided by NanoMod is already part of the ROM don't install it
* nanomod-overlay Script:
* added `-f`, `--fix-update` parameter, fixes navbar, lockscreen, statusbar issues after OTA update
* see: https://www.xda-developers.com/broken-navigation-bar-lock-screen-ota-update/
* added `-P`, `--airplane-mode` parameter, allows to choose which radios are disabled in Airplane Mode
* those will not be activatable, until Airplane Mode is deactivated
* user is given instructions when this parameter is called
* added `-b`, `--boot-count` parameter, show how often the device was booted
* required Android 7.0 or newer
* added `-F`, `--audio-focus` parameter, prevent given application from stealing audio focus
* pass application name as parameter, example: `novl -F com.test.application`
* added `-B`, `--read-clipboard` parameter, prevent given application from reading the clipboard
* pass application name as parameter, example: `novl -B com.test.application`
* `-b|B|f|F|P` paramters are available in both Magisk and System Mode
* Updates (automatic)
* OpenCamera (1.41.1)
* (Simple) Calendar (2.9.1)
* F-Droid (1.0.1)
* NewPipe (0.10.1)
* (Simple) Gallery (2.17.2)
* Orbot (15.5.0.RC1)
* Termux (0.54)

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] Texas_Ace:
I am curious, is it possible to add apps to nanomod so that it could be used to flash all the apps I want on the phone from the start?

It would be really cool if the script could look in a user directory such as "Nanomod Apps" on the SD/extSD card where I could simply put the APK files I wanted installed. It would then scan the folder and install all the APK's during the script. This would save me a ton of time downloading and flashing all the apps individually and would allow people to customize the install without having to edit nanomod itself.

You could even allow for a "system and priv-app" subfolder that would place the APK's accordingly.
[Magisk] Shadow53:
I'm pretty sure that the docs give instructions for how to add/remove apps to the build process of the NanoMod zip. You probably want to do that versus the developer building in a check for apk files.

<shameless-plug>

I've developed a zip-building process of my own that aims at making it easy to build zip files for installing apps/files to your device. It's similar to NanoMod in that regard, and the two projects have shared a couple ideas back and forth. You may be interested in checking out my project for installing your apps, if you decide not to use NanoMod.

https://xdaforums.com/android/development/dev-shadow53s-flashable-zip-builder-t3671119

</shameless-plug>
[Magisk] Texas_Ace:
I figured I could hack my way into the scripts and add my own APK's but it is then very hard to update it with each new nanomod version that comes out and with new apps / changes to apps that I make over time. By simply installing all APK's found in a folder my thinking was that it would be very simple to stay up to date and would transfer through updates and changes.

It was simply a suggestion, no harm done if it is ignored but would sure make things nice for the end user and would basically make my install process a 3 file affair with the rom, magisk and nanomod. Boot and enjoy.

I will check out your thread tomorrow, looks interesting. I knew that something like this had to exist but could never find it while googling.
[Magisk] Oswald Boelcke:
Probably it isn't that you're looking for; however Titanium Backup Pro provides the capability to create so called "update.zip" from your already installed application repository. You just have to decide what ought to be included.

I use this functionality all the time when I know a clean flash is required i.e. I use "a 7 file/zip affair": ROM, Magisk, kernel, Magisk microG, F-Droid and patcher, update.zip.
[Magisk] justmix4:
Hello. It happens every time I try to check the SafetyNet in Magisk Manager.

Nexus 4, LineageOS 02170420, Quanta kernel, latest NanoMod patcher and microG 7.0.20170425, Magisk 12
[Magisk] Setialpha:
Listed in 1st post under 'Issues', check that out.
[Magisk] SketchyStunts:
That's because this is designed for los/aosp ROM's
[Magisk] Aaren11:
Thanks, somehow managed to totally overlook that line.
[Magisk] Oswald Boelcke:
My Samsung GT-i9305 with RR-N-v5.8.3 is GApps free due to your great module. Thanks very much again.

I used the NanoMod microG module, and the device is running just superb. Battery drainage is at about 1.8% per hour, which is very decent to me as I have e.g. Conversations and R2Mail2 neither battery-optimised nor greenified.

Anyhow, as indicated in my post here, I tried to replicate the battery drainage issue with the "full" NanoMod module, and it occured again. I charged the device up to 100% and let it idle. After 3 hours, I had a quick glance for about 2 seconds on the battery indicator showing the battery already being down to 50%! I decided to let it further idle and intended to take a BBS idle dump after 6 hours; however, when I tried to wake up the device after six hours to take the dump file I'd to realise the phone was already dead due to an empty battery. For this reason, I'm unable to attach a BBS dump, and I apologise. For whatever reason, the device never went to deep sleep.

But as requested, I had Catlog running all the time, and the logcat is attached. I hope it supports some analysis.
[Magisk] Setialpha:
Well, you need TWRP and a deodexed ROM, stock ROMs are all odexed, modders usually deodex or mix-odex-deodex their ROMs. All LineageOS/AOSP ROMs users have custom recovery and deodexed ROM. So, a modified, deodexed stock ROM should work.

I'll have a look, though this issue has been reported in RR 5.8.3 thread for Lux (Moto X Play), with Open GApps, too. So likely a ROM/Kernel issue, but we'll see.
[Magisk] Aaren11:
As I depend on Microg, I only ever run deodexed ROMs be they stock or AOSP based.
[Magisk] slothdabski:
[MENTION=4187311]Setialpha[/MENTION]

I've been using your patcher on RRemix and it's been working fine. But today I tried on AOSiP for oneplus3 and it failed. Here's the log from TWRP

https://drive.google.com/file/d/0B1My3ELWb01vWHEtVzc3RkJVWFk/view?usp=drivesdk

Thanks in advance!!!
[Magisk] Setialpha:
Isn't AOSiP pre-patched? According to https://xdaforums.com/android/general/index-list-custom-roms-offering-t3557047 it is.
[Magisk] marcdw:
It depends on the builds. From what I've seen there's no signature spoofing on the G3 AOSiP builds. Same for Tipsy. Certain builds have it but not on my device.

So even if a ROM is on the list that doesn't mean/guarantee that sig spoofing will be present. Best to confirm with one's device maintainer.

LG G3 D851, PAC-MAN LP ROM, MultiROM, Tapatalk 4.9.5
[Magisk] Setialpha:
OK, but if it fails patching, it likely is for the device of the given user.
[Magisk] slothdabski:
FYI I tried using a different unofficial build of AOSiP for op3. It didn't have maybe spoofing, but the patcher worked. There must be something different about the official build and maintainer
[Magisk] :
I can not connect to Google API and because of that i can not pass Safetynet.

I followed your steps like a mad man.

My rom is ZenityRR for the Oneplus3/3T which has support for microg.

And yes, Magisk hide is enabled.

What am i doing wrong?
[Magisk] :
The question is, did YOU read the first post? Please show me where my issue is resolved in the first post.

Otherwise i wouldnt have posted ofc.
[Magisk] SketchyStunts:
Play Store lacks fake sign permission

Its the 2nd issue in OP. Solution is listed. My clipboard is removed so I can't paste it here
[Magisk] :
My bad, that actually helped.

Its really difficult for me as a semi-noob to think that my issue was correlated with the issues posted, that could be clearer. Thanks though. My journey goes onward.

The only thing i have not been able to work out is:

"Network-based location enabled:", the box is not ticked for me and i cant get it to work. Any suggestions?
[Magisk] Bludwurst:
Is your location setting turned on? :p

If it is and it doesn't work, it might be that NanoMod doesn't include the appropriate location patch?

(I haven't gotten around using NanoMod; OmniROM comes with full microG support out of the box).
[Magisk] :
Ofc its turned on. I just cant figure it out.
[Magisk] Brandon9231:
Pretty sure it has to be set to high accuracy too. If that doesn't work try using Mozilla stumbler(?)...it's kind of like an extension to Mozilla's location service that gives the system more detailed location info. Just run it once and you should be fine. Make sure to give location permissions to the back end, stumbler, and mgs core.
[Magisk] Texas_Ace:
Interesting, I have had a lot of issues restoring apps from titanium to different roms so I don't really use it for that anymore unless I have no other options.

I assume that the zip file is just the raw APK files? Have you had any issues with corruption or crashing when doing this? I will have to look into that. Not as convenient as just keeping the APK's in a folder but a lot easier then what I have been doing.
[Magisk] Setialpha:
[MENTION=4573886]Texas_Ace[/MENTION] I don't plan on adding support for external applications, but you could create your own flashable zip, like [MENTION=7126506]Shadow53[/MENTION] said.

----

14.6 introduced new features for the nanomod-overlay Script, they are now fully documented.
[Magisk] Sander9847:
Any idea why the microG module doesn't work with the dissabled signature from the Smali patcher module (https://xdaforums.com/apps/magisk/module-smali-patcher-0-7-t3680053).

The checkboxes all say signature spoofing isn't enabled but I know it does work.
[Magisk] Setialpha:
Because that's something different. It only disables the signature checks locally, but does no spoofing externally.

That's why the smali module says 'signature *verification*', not signature spoofing.
[Magisk] Ex_FallenSkyTear:
attempt to flash nano-microG in magisk.

device: Moto E LTE (surnia).

architecture: arm.

sdk: 25.

magisk 14.
[Magisk] hungvip2001:
In some ROM, the mod works perfectly. But in some other, I can't add any Google account because the sign in button is blur. Please help
[Magisk] r0tati0n:
Hi, I have a question regarding the apps...

If an app was installed before microG, the app fails to register to microG and causes battery drain.

The app should be uninstalled and reinstalled then.

If I backup the app with Titaniumbackup, then restore it without uninstalling the app, does this count as a reinstall and the App registers properly?
[Magisk] jackulus:
Hi guys. I'm a pretty new user of Nano Mode - thanks to it I managed to successfully setup microG on my mobile. I'm somewhere in the middle of checking/testing procedures and I encountered one meaningful inconvenience so far.

I find the voice typing functionality provided by Google app quite productive (making lots of short notes in my profession) on gappsed Android. At present, using microG framework I can use Google app but VoiceTyping input method becomes inactive immediately afer invoking it.

Any of You used/tried this functionality successfully or have a clue for me? Any help very appreciated.. :)
[Magisk] Shadow53:
No, that does not count. You'll have to actually uninstall and reinstall, then do whatever you need to with the newly installed app for it to register (some do it on first launch, some when you sign in, etc.). Then you should be able to restore the backed up data from TiBu.

It also occurred to me that you may get the same reset effect if you delete all of the app's data without reinstalling...
[Magisk] uli_p:
I use the Swype keyboard that offers the same function. Speech recognition works very well.
[Magisk] r0tati0n:
Thank you :)

I just noticed, TiBu has an option to uninstall all backed-up apps.

Backup all apps, uninstall all backed-up apps, restoring them again, does not count either then, right?
[Magisk] jackulus:
Sure! It works. I used to use it years ago. Now I'm accustomed to Swiftkey and after a few minutes of testing Swype it's hard time to use it ?. And it uses huge amount of RAM comparing to Swiftkey..

Nevertheless, speech recognition works great, seems to be better then google's. It is a great circumvention for me.

Thanks a lot ! :good: :)
[Magisk] uli_p:
You're welcome. Even though my reminder seemed hardly necessary. :)
[Magisk] mongo0:
Thanks a lot for your help! I have another issue:

I cannot use any app that uses Google navigation. It either crashes or just won't work.... How can I fix this? I have the microG package. Can I add maps apis for these apps to work?!
[Magisk] maybeme2:
In the list of supported Android versions 6.0 is mentioned but not 6.0.1.

Is 6.0.1 supported?

Also I'm a little confused about its installation because I'm new at this. I currently have 6.0.1 with xposed on my nexus 5. After I download the latest version of nanomod do I just use my twrp recovery to flash nanomod on top of everything?