yashsingh1/xdaforums huggingface dataset:
[Magisk] bonbonboi:
I'm thinking to back to the previous version even most apps start to complain and giving error crashing reports, or maybe we really need to start over by a complete wipe then reflashing our devices.

java.lang.SecurityException: Not allowed to start service Intent { act=com.google.android.c2dm.intent.REGISTER pkg=com.google.android.gms (has extras) } without permission com.google.android.c2dm.permission.RECEIVE
at android.app.ContextImpl.startServiceCommon(ContextImpl.java:1381)
at android.app.ContextImpl.startService(ContextImpl.java:1358)
at android.content.ContextWrapper.startService(ContextWrapper.java:613)
at com.google.android.gms.gcm.GoogleCloudMessaging.zzah(Unknown Source)
at com.google.android.gms.gcm.GoogleCloudMessaging.register(Unknown Source)
at com.symantec.spoc.GCMRegistrar.a(SourceFile:87)
at com.symantec.spoc.q.run(SourceFile:548)
at android.os.Handler.handleCallback(Handler.java:751)
at android.os.Handler.dispatchMessage(Handler.java:95)
at android.os.Looper.loop(Looper.java:153)
at android.os.HandlerThread.run(HandlerThread.java:61)
[Magisk] CHEF-KOCH:
How is that possible? The patcher worked before till v14.93 or so and I didn't updated the from since tgen, really strange. I'm a killer bit confused and lost I dunno what to provide except my log file to fix this, I also checked the microg project for the s5 mini buts not supported.

I mean I could till back but I don't get it why it's not working anymore with the same LineageOs build the patch process is overall the same...
[Magisk] khnoizer:
Sorry, newbie here. Just want to ask simple questions.

1. If I update my rom through dirty flash, should I also flash nanomod again?

2. I installed nanomod to system, then flashed magisk. If I update nanomod, should I remove magisk first so nanomod will keep installed on system?

Thank you.
[Magisk] guest4711:
1. Yes. Reflashing a ROM wipes or destroys the contents of /system. As long as you install it to system you should reflash it afterwards. If you install it systemless, you are fine without reflashing.

2. If you want to keep it on system, you should use a configuration file (/sdcard/.nanomod-setup) -see post#1- to force installation to /system. But why not use it systemless?
[Magisk] khnoizer:
So, I create that config file, and flash the nanomod zip after that right? Thank you.

For the reason I chose system mode is, I was using the systemless mode last time, logged in my google account and all set up. For some reason I have to uninstall and reinstall magisk and therefore, nanomod also gone and I have to reinstall it. After that, I got stuck everytime I try to login into my google account. I checked the log, It says my google accout already exist. Then I wipe data and cache and reinstall all things but still stuck when login into my google account, and the log said the same thing, my account already exist.
[Magisk] guest4711:
Right. Create it and put "nanomod_forcesystem=1" into it. ;)
[Magisk] defi231:
OP3T

im using sultan LOS 14.1 with Nano Mod patcher 14.9, but i cant use NanoMod-patcher-15.0.20180113.zip, i get 1 error........... someone else:confused:
[Magisk] bonbonboi:
Just to be sure, today I did full wipe of my phone: system, data, cache, dalvik then flashed the OS (Viper sdk25) ... Magisk ...rebooted the phone many times till I quiet sure that Magisk is installed correctly. Then Magisk > Modules > added NonoMod microG v15.0.20180113 (and as usual with all nonoMod versions, the flash process doesn't scroll down till the end to show those buttons to Reboot Show log Close, but it seems the flash is completed even without them displayed in the end!?) ... Rebooted then phone ... Opened microG settings ... Give all permissions it asks for... UnifiedNlp Settings > Configure location backends > checked Deja Vu Location Service ... Got Daja Vu Location Service has stopped error message. Tap Open app .. the error message back again.

The logcat:

---- Jun 20, 1970 02:40:57 ----

06-20 02:40:26.233 1205 1295 I ActivityManager: Start proc 4447:org.fitchfamily.android.dejavu/u0a68 for service org.fitchfamily.android.dejavu/.BackendService

06-20 02:40:26.356 4447 4447 E AndroidRuntime: Process: org.fitchfamily.android.dejavu, PID: 4447

06-20 02:40:26.356 4447 4447 E AndroidRuntime: java.lang.RuntimeException: Unable to instantiate service org.fitchfamily.android.dejavu.BackendService: java.lang.ClassNotFoundException: Didn't find class "org.fitchfamily.android.dejavu.BackendService" on path: DexPathList[[zip file "/system/app/nlpBackendDejavu/nlpBackendDejavu.apk"],nativeLibraryDirectories=[/system/app/nlpBackendDejavu/lib/arm64, /system/lib64, /vendor/lib64, /system/lib64, /vendor/lib64]]

06-20 02:40:26.356 4447 4447 E AndroidRuntime: Caused by: java.lang.ClassNotFoundException: Didn't find class "org.fitchfamily.android.dejavu.BackendService" on path: DexPathList[[zip file "/system/app/nlpBackendDejavu/nlpBackendDejavu.apk"],nativeLibraryDirectories=[/system/app/nlpBackendDejavu/lib/arm64, /system/lib64, /vendor/lib64, /system/lib64, /vendor/lib64]]

06-20 02:40:28.471 1205 1696 I ActivityManager: Killing 4447:org.fitchfamily.android.dejavu/u0a68 (adj 0): crash

---- Jun 20, 1970 02:40:57 ----
[Magisk] Setialpha:
Hmm... what happens, when you flash it from TWRP?
[Magisk] utg1:
Hi all,

I have an issue with Nanomod-patcher version 15.0 (same with 14.92 and 14.93) I can't flash it via TWRP. Nanomod-MicroG 15.0 works fine.

I have to use patcher version 14.9.20171213.

I have a Redmi 4 prime with miui 9 android 6.0 based with TWRP version 2.1.1.-0.

Any ideas about it?
[Magisk] bonbonboi:
It will install, no problem at all, nanomod will detect the presence of magisk, if not then it will install itself to system.
[Magisk] Setialpha:
No, I mean, does it work, when you install from TWRP?
[Magisk] Setialpha:
What is the error message?
[Magisk] utg1:
"Failed to apply patches.

Updater process ends with error 1".
[Magisk] Setialpha:
The full message is in the recovery.log
[Magisk] utg1:
Log:

I:Found no matching fstab entry for uevent device '/devices/virtual/block/loop0' - change
>> patching services.jar
CANNOT LINK EXECUTABLE: "/system/lib/liblog.so" is 32-bit instead of 64-bit
page record for 0x7ad84b2010 was not found (block_size=64)
!! failed to apply patches
e2fsck 1.42.9 (28-Dec-2013)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/data/adb/magisk.img: 540/4096 files (0.6% non-contiguous), 12263/24576 blocks
I:Found no matching fstab entry for uevent device '/devices/virtual/block/loop0' - change
Il processo Updater è terminato con ERRORE: 1
I:Install took 1 second(s).
Errore durante l'installazione dello Zip '/external_sd/Download/MIUI/MicroG/NanoMod-patcher-15.0.20180113.zip'
Aggiornamento dei dettagli della partizione...
I:Data backup size is 5762MB, free: 8980MB.
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'auto'
...fatto
I:Set page: 'flash_done'
I:operation_end - status=1
I:Set page: 'reboot_system_routine'
I:Set page: 'rebootcheck'
I:Copying file /cache/recovery/log to /cache/recovery/last_log
Riavvio...
[Magisk] Setialpha:
I'll brew up some test build for the patcher during the next days.
[Magisk] bonbonboi:
I installed it through Magisk's modules tab. I'm not reporting an installation issue. It's about the new location service.
[Magisk] ccaappton:
I got the same error. The detect_arch() always return "arm" instead of "arm64". It looks like something is wrong here

After hardcode "arch=arm64", and change line 313, and "mount -o remount,rw /system" before patch, I succeed patching the rom.
[Magisk] matttbe:
Good catch! There is something wrong with this function: a `shift` is used at the first line without saving the variable that we need after. Maybe try this :

grep_prop() {
local PROP=$1
shift
FILES=$@
[ -z "$FILES" ] && FILES='/system/build.prop'
cat $FILES 2>/dev/null | sed -n "s/^${PROP}=//p" | head -n 1
}
[Magisk] jenslody:
"shift" is used correctly here, it just removes the first parameter of the function, so that "$@" contains the rest of the parameters.

On some systems "sed" does not work correctly.

Can you attach your "build.prop" and/or run

getprop ro.product.cpu.abi

and

getprop ro.product.cpu.abi2

and post the output ?
[Magisk] Setialpha:
It might still be an installation issue, that's why I'm asking whether installing from TWRP creates a working instance. Installation code for Bootmode (= Magisk Manager) is not exactly the same as for TWRP, so there MIGHT be differences, in fact before version 8 or 9 Magisk Manager installation wasn't supported at all because of the required changes to the installer.

Ha! The installer packages are correct, but the patcher is wrong. I attached a test build to this post, please report back.
[Magisk] cristihan:
Hi , and thank you for your great work. I have the same problem as "utg1". Nanomod-MicroG 15.0 works fine but I have to use patcher version 14.9.20171213 because Nanomod-patcher version 15.0 failed via TWRP 3.1.0-0 on my device. Please see attached screenshots .
[Magisk] Setialpha:
See one post above yours and test that build.
[Magisk] matttbe:
We need shift for $@ but we also need to save $1 before to use this variable in the sed command. After the shift, $1 is no longer the same. Or is this shell different on android?
[Magisk] jenslody:
If you look at the code in your former post, there is the line

locale PROP=$1

just before the "shift".
[Magisk] matttbe:
That's the line I added, you can look at the original code ;)
[Magisk] jenslody:
In this case you are right of course.

That's the problem with multi usable scripts (with Magisk and without), each function has to be doubled for each single flashable module, and this is of course errorprone, if you have to fix issues or modify this special function.

That's one of the major problems of John with Magisk modules. They can not be forced to use an api (because they use scripts) and many Magisk errors come from broken modules with their own scripts/fucntions. The original code from Magisk saves "$1" before the shift.
[Magisk] nero10:
android auto is not working with microg. any solution or idea to fix this issue?
[Magisk] Setialpha:
The modules are fine, only the patcher isn't. Also future NanoMod versions will share code through a common script file shared accross all of it's packages, which eases bug hunting and prevents errors lwft in a single package only.

AFAIK microG does not support AA.
[Magisk] tom.android:
UnifiedNlp not support -in chinese ROM

-How to use Nanomod-microG? Thank you.
[Magisk] fastguy:
Hi, due to Baidu Location Services embedded into the rom I think. Right?
[Magisk] tom.android:
How to check that?
[Magisk] kurtn:
Working in LOS 15.1
[Magisk] Setialpha:
Good!

+++++

The next release will split the installer functions into module specific and common code. It's already used for the Full package in the gitlab repo, if someone wants to have a look. microG and F-Droid packages follow soon.

Also the Uninstaller saw improvements and support for both old and new system mode istallations.

+++++

Here in the thread please refer to the gitlab repo, the one on github is knly a mirror and not always up to date.
[Magisk] utg1:
Patcher test build works fine here! Thanks mate!

Miui 9 (android 6.0), Magisk 15.3 and TWRP 3.2.1-1
[Magisk] cristihan:
Hi Setialpha, this NanoMod-patcher-15.0.99999999.zip is OK...thank you !
[Magisk] bonbonboi:
I already tried your new release, there is something strange, you know me I like to flash modules through Magisk's modules tab, so I removed the previous versions, rebooted the phone. Opened Magisk headed to modules tab, here is the strange part, I added NanoMod-microG-15.1.beta1.20180117.zip then rebooted the phone, it get installed, no issues so far, even the new location service provider didn't crash as before, I back to Magisk I installed NanoMod-fdroid-15.1.beta1.20180117.zip, rebooted the phone, I found out nanomod microg just gone, even not listed in Magisk, f-droid is there. So what I have found that I can't have them both, the last one of them get installed will stay and the other one will vanish.
[Magisk] guest4711:
Just tried. Installed latest nanomod-microG by [MENTION=4187311]Setialpha[/MENTION]. It installes to /magisk/NanoModfdroid/ instead of NanoModmicroG.

So when installing two variants only the last one would survive....
[Magisk] Setialpha:
Yes, will be fixed, soon.
[Magisk] locolyric:
Installing current stable version. Not booting up after flash the standard version.

Did I miss something?

I tried with magisk install and no magisk.

Both also no responses in boot logo

I tried install in magisk. Finally worked.

But unable to customize it. Cause install via twrp will definitely not booting in to home screen
[Magisk] guest4711:
You may customize it creating and population the configuration files, e.g. /sdcard/.nanomod-setup.

See the documentation linked in OP.

Your problem with TWRP is strange. But noone could help you without having more information. Which phone, which ROM, which TWRP version? Crypted or not? Best would be to post the recovery log (after flashing nanomod, before reboot) and the bootlog afterwards...

Hint: Use TWRP >= 3.0.1 for flashing.
[Magisk] Setialpha:
I've re-uploaded the microG beta package, fixes the issue it does not coexist with the F-Droid package. It is recommended to mark the old microG beta package for uninstallation in Magisk Manager and the reinstall it.
[Magisk] guest4711:
Thank you. Now it works for me again. :good:
[Magisk] Setialpha:
15.1

Version 15.1 is now available. See this post for more information about what 'Common Installer' is in case you're interessted.

The next release (16.0) will rename 'NanoMod' to 'NanoDroid'. The installers will take care of the transistion, while the Patcher and Uninstaller will support both old and new modules. The configuration files with the old names will be auto-migrated (= files and variable re-named). Of course there will be a beta release beforehand to give users the ability to test. No ETA, but no longer than a few weeks.

Why will the project be renamed? Well, the name NanoMod was poorly choosen right from the start, but I didn't have any better idea. The 'Mod' is, what actually is poor, as it isn't a mod (= modification) at all, or at least not what I interprete the word as. But since the project became much more popular than I ever expected I'm somewhat forced to retain the recognizability, so NanoDroid is my entry of choice.

Here's the full list of changes since 15.0:

* Bug Fixes:
* Patcher package, addon.d
* fix architecture detection
* mount /system read-write if required
* Uninstaller
* fix restoring Settings.apk backup (if any)
* General Changes:
* Full, microG, F-Droid packages
* split out common installer functions (~ 95 %) into separate file
* Common installer
* contains most installer functions (~ 95 %)
* code revision to do most stuff with least calls
* support all Full, microG, F-Droid packages without code duplications
* Full package
* provide custom OpenLauncher build from latest sources
* Uninstaller
* support both old (<15.0) and new (>=15.0) system mode installations
* only mount /system read-write if a system mode installation exists
* revise and simplify the code
* Updates (automatic):
* nlpBackendDéjàVu (1.0.8)
* (Simple) Gallery (3.2.3)
* NewPipe (0.11.4)
* Odyssey (0.1.11)
* (Simple) Calendar (3.1.0)
* Updates (manual):
* MPV (20180118)
* OpenLauncher (20180118)

Download from AFH.

In case of errors, please provide

/data/adb/.nanomod_MODID

/data/adb/.recovery_MODID

logcat (if applicable)

Additional Notes (shamelessly copied from 14.7 announcement post):

Play Store 8.4.*.V introduces internal apk changes, which are not (yet) supported by APK Tool, so I can't provide a newer version right now. To stop the Play Store from constantly trying to update itself (and drain both battery and mobile data), use an application like DisableService, Servicely or-the-like to disable Play Store's 'DailyHygieneService' *AFTER* you've initially setup the Play Store, else it won't sync your installed applications and won't provide you with updates, until you let that service atleast run once.
[Magisk] guest4711:
I like the old name. NanoMod is (for me) a small module I could add to my ROM... And on most devices I use I can disable and enable it using magisk in the section "modules". A logical name for Nanomod-microG would be microGmod....
[Magisk] HeinJanMaat:
Moin Setialpha

Both uninstallers (15.1beta1 and today's 15.1) give me Error: 2 with installed NanoMod 15.1beta

<<> removing /data/.nanomod-apps

/tmp/updater: line 237: syntax error: unexpected end of file (expecting "then")

<<> removing /data/.nanomod-overlay

Updater process ended with ERROR: 2

OnePlus 3T

Android 7.1.2

Resurrection Remix

Magisk v 15.3 (180113)

Going to test clean install.
[Magisk] Setialpha:
Will re-upload, soon.

Edit: done. Though you only need it, if you want to get rid of it, not for updates.
[Magisk] A00elbdawy:
i have s4 i9515 with lineage 14.1 and magisk installed (didnt flash gapps or anything else)

now i want to flash nanomod for microg and nanomod fdroid

so the steps are

1. flash patcher

2. flash microg then fdroid

all in one process without any rebooting in between?

i read the instructions on git lab but didnt know if i should flash setupwizard first before patcher or it is just for the whole nanomod.

thnx in advance and this project looks perfect for battery optimization and rapid preformance :good::D
[Magisk] abacate123:
Since the setup wizard zip is an aroma interface to let you create a script for choose whatever you'd like to install when you flash the desired nanomod zip (full, microg or any other), it should be flashed first. Then, after you select everything (or unselect everything, as you wish) on the setup wizard aroma interface, you flash the desired nanomod package.

Then you can flash the patcher after, if you need.
[Magisk] A00elbdawy:
i just flashed setupwizard and now i got several options to check or not

as i said i want to flash microg+f-droid which options i check:

1.microg

2.f-droid

3.apps

4.overlay

5.zelda tunes

6.maps

7.init scripts

8.maos api v1

9.google sync

10.swipe

11.force system (N.B: i got magisk installed)

12.sigsprrof ui
[Magisk] abacate123:
I don't wanna sound rude, but well, it's kinda obvious. What's written there on the setup wizard aroma, will only install what's within the main nanomod zips after the setup wizard is complete.

So if you've downloaded the nanomod-microg, or the nanomod-fdroid or another, for example, the setup wizard will create a script to install those things that are available on the main zip you've chosen, the other stuff that is not available inside it, will not install.

I see it's pretty much well explained on the gitlab documentation. I may ask you to read it more carefully again, phrase by phrase. C'ya.
[Magisk] A00elbdawy:
well ofc thanks for your help i appreciate it very much and it helped me alot.:good::highfive:

and those options werent included in the documentation or the aroma installation .only asked coz i dont want to face any problems(i guess this is what thread replies are opened for).

1.

NanoMod-setupwizard: includes

AROMA based Setup Wizard to create the configuration files

user can choose where to store the configuration files

/sdcard

/external_sd

/data (fallback)

NOTE: AROMA only works on arm and arm64, if your device is x86 or x86_64, it won't work

2. Installation Process

NanoMod:

Use Setup Wizard to create configuration files (if you've got an arm/arm64 device), or create manually (see above)

that's it when talking about setup wizard in the documentation.
[Magisk] nero10:
same problem and some apps get crashes, won't open(e.g. letgo, calciomercato). looks like a gps problem. 14.9 was the last working version without any problem.

7.1.2 RR
[Magisk] tom.android:
Me too.!!!

Chinese ROM + xposedGmsCoreUnifiedNlp
[Magisk] Livingsilver94:
I confirm the error with the uninstaller package. Plus, sync APKs are empty, they are not valid APKs. I tried to open and install them with Amaze after having noticed they don't have a proper icon.
[Magisk] guest4711:
Did you try the updated version (https://xdaforums.com/apps/magisk/module-nanomod-5-0-20170405-microg-t3584928/post75261964)?
[Magisk] Setialpha:
Logs!!!!111einself!!

(Sorry, but given the instructions for proper error reporting have been posted a quadzillion times, also simplified since version 15.0, I just had to do that)

Also it was posted multiple times that 14.9 and older use Mozilla backend by default, while 15.0 and newer use Deja Vu. So, ensure Deja Vu is enabled in microG settings, or opt-in to install Mozilla instead (or both).

Hmmm... they are auto-downloaded from OpenGApps, but I didn't receive any error message... I'll check it later today.

Also: why does everyone download the Uninstaller? It's not required for upgrades, downgrades or re-installations, only for ACTUAL uninstallations...
[Magisk] Livingsilver94:
Thank you. Both 15.1 and 15.0 lead to the same result.

I thought to use the uninstaller package to have a clean ROM back, since I had errors with the sync APKs in fact.

A question for you: When did you write that alert about Play Store 8.4? I just want to know how old is that issue.
[Magisk] Setialpha:
Since version 14.7, around late November/early December.
[Magisk] nero10:
i tried to disable deja vu or install mozilla but no success. i think you need to remove dejavu from package to fix this issue because you can't uninstall deja vu from f-droid.
[Magisk] Setialpha:
You don't need to remove anything, you can disable Deja Vu in microG, if you want to use mozilla, else: logcat.
[Magisk] nero10:
tried already, keeps crashing. how can i take a logcat?
[Magisk] guest4711:
Use an app like Logcat (Android Logcat without Root) - https://f-droid.org/app/com.tananaev.logcat or OS Monitor (Monitor the Operating System) - https://f-droid.org/app/com.eolwral.osmonitor to collect and copy the log if you don't like to use adb.
[Magisk] nero10:
attached log file but not sure if i did it right.

thanks.
[Magisk] Setialpha:
I'll upload new installers, soon.
[Magisk] Setialpha:
I'll have a look at it.
[Magisk] Setialpha:
New Full and microG packages uploaded (labelled 15.1.1), fixed Google Sync Adapter installation.
[Magisk] bonbonboi:
I'm wondering do we need to flash f-droid with every nanmod update?

Also yes nanodroid sounds better than nanomod.
[Magisk] Setialpha:
if nothing F-Droid related is mentioned, or no installer bug was fixed that affects you, not really, except you like high version numbers.
[Magisk] Deva Kaushik:
New MicroG supports Oreo?
[Magisk] kurtn:
Yes
[Magisk] trung335:
odexed rom not support :((

rom oreo 8.1

devices : XiaoMi Mi 4
[Magisk] Setialpha:
There's nothing I can do. You may deodex on your own (xda has tutorials on that) or use a deodexed ROM (if there's any).
[Magisk] jacomail95:
An alternative way to use MicroG (especially on odexed ROMs, this is the only solution I believe) is to use the new Xposed beta for Oreo and the FakeGapps module, then you can flash the NanoMod package of your choice, without need of patching

Inviato dal mio Nexus 5 con Tapatalk 2
[Magisk] ydd0ras:
Last night I have flashed the latest build of Nitrogen OS 8.1 on my Mi 4w. Then I have flashed Magisk 15.3 and finally NanoMod-microG 15.1. No need to flash the NanoMod Patcher. You can use the spoofing signature from the App Settings.
[Magisk] Setialpha:
Validus Oreo 8.1 also has built-in sigspoof again, FYI.

+++

Project rename to NanoDroid is progressing well, internally almost done, configuration file migration and auto-removal of old Modules works fine. SetupWizard, Patcher, Uninstaller currently untested. I expect a beta release this weekend.
[Magisk] psychem:
randomly sometimes i see "Google Play" downloading in notifications without asking for any permissions. Why does that happen? How can i stop it permanently from automatically downloading this ?
[Magisk] guest4711:
See a few posts back (https://xdaforums.com/apps/magisk/module-nanomod-5-0-20170405-microg-t3584928/post74439645 at the bottom). Stop the "daily hygiene service" /Service for PlayStore.