yashsingh1/xdaforums huggingface dataset:
[Magisk] Setialpha:
16.1

Version 16.1 is now available. Highlights since 16.0:

logcat init script (Full package): store logs in /data/adb/logcat

many improvements regarding GNU Bash shell

Full ChangeLog since 16.0:

16.1.20180209

* Bug Fixes:
* Full, microG packages
* when becoming su from GNU Bash the default sh instead of GNU Bash would become the active shell
* this is fixed now by always passing `--shell /system/xbin/bash.bin` to su when it is invoked from with a running GNU Bash instance
* fix ${TMPDIR} for GNU Bash is set to a non-writable directory
* create ${TMPDIR} for GNU Bash if it does not exist
* defaults to /sdcard/.bash_tmp
* fix ${HISTFILE} for GNU Bash not being set, thus history functionality not working
* defaults to /sdcard/.bash_history
* General Changes
* Full, microG packages
* when starting GNU Bash cd into /sdcard
* make /sdcard ${HOME} for non-root users in GNU Bash
* export ${SHELL} set to GNU Bash when it is invoked in interactive mode
* only clear and resize the buffer on start for interactive GNU Bash sessions
* nicer ${PS1} for interactive GNU Bash sessions
* ensure GNU Bash uses our version of the less pager, even if busybox' version is installed
* make ls use colors, if possible when in GNU Bash
* make grep use colors, if possible when in GNU Bash
* Full packages
* record logcat in /data/adb/logcat/${CURDATE}
* e.g.: /data/adb/logcat/20180208-07.05.18
* Updates (automatic)
* XDA Labs (1.1.4b)
* (Simple) Calendar (3.2.4)
* F-Droid (1.1~alpha2)
* (Simple) Gallery (3.4.0)
* Déjà Vu nlpBackend (1.1.1)
* Termux (0.60)
* Yalp Store (0.35)
* Odyssey (1.1.12)
* Updates (manual)
* PLay Store (8.9.23)
* GNU Nano (2.9.3)
* GNU Bash (4.4.18)

Download links

Download from AFH or Nanolx.

Bug reporting

In case of errors, please provide

/data/adb/.nanodroid_MODID

/data/adb/.recovery_MODID

logcat (if applicable)
[Magisk] godofsalt:
Ok answers that.

Tanx
[Magisk] daftect:
Which is better? LineageOS with built in microG or this version of microG provided with NanoDroid on straight LineageOS?
[Magisk] hungvip2001:
Built-in always is the best.

But no many ROM has it.

Now I am using nanodroid without a problem.

And nanodroid 's update is faster
[Magisk] kurtn:
No big difference. Nanodroid needs longer for ota update because patcher running after flashing. Nanodroid has more features. You will need longer learning it.
[Magisk] hertzschi:
Thanks for the update.

Did anyone experience proplems with the setupwizard.zip from 30.1.18?

For me the recovery always crashes hard and the device reboots back to the recovery.

Maybe something with aroma installer?

I have a klte with latest twrp recovery 3.2.1.

I don't know how to take a recovery log, because it gets overwritten at the immediate recovery reboot.

I'm new to nanodroid mod but not to microg.

Any help appreciated.

Thanks and have a nice weekend
[Magisk] kmem:
Forgive me, I tried to find this info in the op but perhaps I missed it.

Is the procedure for upgrading from nanoMod 14.9 to nanoDroid 16.1 as simple as flashing the new files over top of the old installation? Unfortunately my setup is fairly complex (multiROM) and I don't want to make a silly mistake.

During the initial installation it took me a while to figure out that nanoMod only works on the primary ROM. Is there any chance that this has changed in the latest rev?
[Magisk] mostevil94:
have you people included more features like support for youtube? could i get a fully functional youtube while using nanodroid? i still use gapps just for yt, if it is a way let me know thank you
[Magisk] Setialpha:
I never use(d) the official YT app, so I don't know. NanoDroid includes NewPipe instead, dunno if that fulfills your needs.
[Magisk] mostevil94:
there is ogyoutube but it does not work on your microg, requires a different version
[Magisk] dugi9991:
iYTBP works just fine with NanoDroid microG.
[Magisk] marcdw:
As dugi9991 mentioned, iYTBP works just fine. I use it on most of my microG setups. No problems with it.

LG G3 D851, CyanogenMod 12.1 ROM, Fechda Kernel R7, MultiROM, Tapatalk 4.9.5
[Magisk] Greek13:
I'm using a rom based on Los 15.1, the rom is odexed so I can't flash the patch. I have flashed only the microg and the Playstore or gmaps work fine, but I can't use the YouTube/iYTBP... Does anyone know how can I use YouTube? Thanks!

( In microg settings "phonesky has correct signature" is not checked)
[Magisk] kurtn:
Use xposed fakegapps
[Magisk] guest4711:
If you don't need subscriptions or upload of movies you could use NewPipe (Lightweight YouTube frontend) - https://f-droid.org/app/org.schabi.newpipe

I'm very satisfied with it...
[Magisk] ydd0ras:
Guys, it's me again. Must bother you again. Trying to flash NanoDroid microG on my Mi A1. But it won't work (check the ss). For signature spoofing I would use FakeGapps, because the ROM is odexed. Thx.
[Magisk] marcdw:
The error is right there in your screenshot. No build.prop file. A most important piece.

If it is truly not there, you need to find out why or contact your ROM dev.

If you're on stock then not sure. File should be there.

ZTE Axon 7 A2017U, AospExtended v4.6 ROM, microG (NoGapps), Multiboot, Tapatalk 4.9.5
[Magisk] ydd0ras:
I have a build.prop. I can also edit it. It is a stock ROM.
[Magisk] marcdw:
You'll have to forgive my ignorance when it comes to various devices but screenshot doesn't say /system/build.prop. It says /persist/speccfg/vendor_ro.prop. Are they linked in any way within the ROM?

Best bet is to go into TWRP, mount /system, and use TWRP's file manager to see if build.prop is physically present. Let us know.

If it is not there you could _probably_ copy that other prop file to /system and rename it build.prop. IF the file is of the same or similar as build.prop.

A second opinion would help in case I'm way off. Don't want you to mess anything up.

LG G3 D851, CyanogenMod 12.1 ROM, Fechda Kernel R7, MultiROM, Tapatalk 4.9.5
[Magisk] ydd0ras:
Many thanks mate, but sower at this point is maybe the problem. From the TWRP file manager I can't do anything
[Magisk] Setialpha:
What's the recovery.log after (failed) flashing? I can't look into this issue without.
[Magisk] ydd0ras:
1000 Dank, I mean thank you. Check the attached log please.

BTW, it is not easy to config the Xiaomi Mi A1 as any other device. Here is what I've tried before:

- debloated the ROM (odexed) and freed the device from any gapps (have left the Phonesky)

- flashed NanoDroid 16.0 from Magisk. Nothing happened

- installed the microG Services core, Services framework, Droidguard

- installed the Xposed Installer and the Framework and FakeGapps for signature spoofing. Also the XposedUnified....

All this will not work properly. For example I have flashed on my Xiaomi Mi4 with the latest Dirty Unicorns (also odexed) the NanoDroid 16 and the FakeGapps through the Xposed Installer; everything is working nicely.

Maybe you`ll find a way for the A1.
[Magisk] cristihan:
Hello [MENTION=4187311]Setialpha[/MENTION] ,

Thank you for your Great work !.

After a fresh install of a LineageOS 7.1.2 ROM on a Galaxy S4 mini (i9195i), I installed NanoDroid 16.1 . Everything worked fain after installation (microG, apps...) but Fdroid does not work properly. It updates repositories as the first startup very often and reports incorrectly the installed applications on the device. I have tried .. "clear cache and data" of Fdroid app but nothing has changed. (same behavior of Fdroid app in NanoDroid 16.0). I made another fresh install for ROM and I installed NanoDroid 15.0 and now everything is OK. I attached the video clip.
[Magisk] Garry050:
I have problem paid app install. but foday apply 16.1 update , it's solved. what the...
[Magisk] J4jks:
Again it's happening with nanodroid only

I've installed nanodroid via magisk , when I power of my device it won't shutdown, display is of and navigation key lights are glowing, of I connect charger, it doesn't show anything, nothing Is happening, just staying there.

I've reported same with my Titan,now on Kenzo.

After removing NanoDroid it's completely normal
[Magisk] jenslody:
This is an issue with f-droid 1.1-alpha2 and not related to nanodroid or magisk. A bug exists in their bugtracker on gitlab,
[Magisk] demonoidmaster:
That's not what the file manager looks like
[Magisk] cristihan:
Hi,

Thank you [MENTION=8340552]jenslody[/MENTION]. I did not know about an existing bug. In this case the solution is very simple ... f-droid 1.1-alpha2 app in archives must be replaced with the 1.1 alph0 version that works well.
[Magisk] psychem:
cant sign into my account get this screen permanently "just a sec" after entering password.

if i try some other gmail account it works. but that too stops after flashing rom a few times.
[Magisk] jenslody:
1.1-alpha1 works also.
[Magisk] marcdw:
Sorry for the late reply.

I am not sure why you are in a terminal or trying to mount a magisk image. I just wanted you to check for the existence of build.prop.

What do you mean you cannot do anything with the file manager?

1. Mount /system.

2a. Advanced -> File Manager. Go into system, scroll down and check for file.

or...

2b. Advanced -> Terminal. "ls /system/build.prop" or just "ls /system/" (no quotes). Check for file.

ZTE Axon 7 A2017U, AospExtended v4.6 ROM, microG (NoGapps), Multiboot, Tapatalk 4.9.5
[Magisk] ydd0ras:
Thanks mate for your support.

When I try to do something in the Terminal, then I get always some chaos. Wasn't so in the earlier N versions. Check the screenshot. The build.prop is not located in /system, but in /system/system. That's maybe the problem (A/B system??
[Magisk] psychem:
can't sign into my google account. gets stuck on "Just a sec" waiting screen after entering the password. using the latest lineage and microg.
[Magisk] Shadow53:
Do you have device check-in enabled? Pretty sure that is necessary for Google login. GCM may be necessary as well, depending. I usually make sure both are enabled.
[Magisk] psychem:
just did a clean flash for the rom and all is fine.:)
[Magisk] Setialpha:
Is the A1 an device with A/B system partition scheme? I never tested NanoDroid with one of them, as I don't have any. If not, it's a strange error, I'll check further.
[Magisk] Setialpha:
On a side-note: version 16.2 will allow updating NanoDroid custom apks using 'nanodroid-overlay -U', theese are Fake Store, Play Store, MPV andOpenLauncher as of now.
[Magisk] ydd0ras:
Yes, it is. You're fully right. That partition scheme causing sometimes lot of trouble and lot of efforts from the devs as well.

Thanks!
[Magisk] Setialpha:
Ok, I'll make A/B support a goal for 16.2.
[Magisk] Shadow53:
Any chance you'd be willing to share your findings for how to support A/B as you go or when you're done? I've done a little bit of research into it but haven't found much without a device to test on.
[Magisk] ydd0ras:
Ein Mann, ein Wort. Sounds nice mate. This is the last step, before having a great google-free device. Have already removed the Gapps systemless. Many thanks.

---------- Post added at 09:45 PM ---------- Previous post was at 09:43 PM ----------

If you're living here around the corner, I could borrow you my Mi A1. [emoji51]
[Magisk] Setialpha:
The first beta for 16.2 is now available. What's new?

adopt Magisk's mount code in order to support devices with A/B partition scheme

nanodroid-overlay -U parameter to allow updating custom apks

Full ChangeLog:

* General Changes:
* Full, microG, F-Droid packages
* use Magisk's mount code to support of devices with A/B partion scheme
* nanodroid-overlay Script
* add `-U`, `--update-apks` switch to nanodroid-overlay script, downloads and installs latest versions of custom NanoDroid apks, requires Busybox to be installed (for wget applet)
* Fake Store
* Play Store
* MPV
* OpenLauncher
* Updates (manual)
* Play Store (8.9.24)
* Kernel Adiutor (0.9.74.3)

Download links

Download from AFH or Nanolx.

Bug reporting

In case of errors, please provide

/data/adb/.nanodroid_MODID

/data/adb/.recovery_MODID

logcat (if applicable)

[MENTION=6282592]ydd0ras[/MENTION] please test
[MENTION=7126506]Shadow53[/MENTION] I was pretty sure Magisk had proper code readily available see scripts/util_functions.sh in Magisk repo or Full/nanodroid-functions in NanoDroid repo for the code
[Magisk] hungvip2001:
Nice gift for lunar new year:good:
[Magisk] Loader009:
[MENTION=4187311]Setialpha[/MENTION]

Sadly the patcher says:

!! odexed ROMs are not supported
Updater process ended with ERROR: 1

although, I build the ROM and I didn't knowingly odexed it.

I don't know how to enable odexed builds though -- if it is enabled by default, I have to find out how to disable that.

Please see the attachements... systemUI.apk is from /system/priv-app/SystemUI/

~ # find . -iname systemui.apk
./system/priv-app/SystemUI/SystemUI.apk
find: ./sys/kernel/slab/L2TP/IPv6: No such file or directory
find: ./sys/kernel/slab/L2TP/IP: No such file or directory

Any suggestions which I could do to make the ROM (RR oreo) compatible to NanoDroid?

PS: Please add a little guide on the first page for what you need to debug anything.

e.g. what logs, what if they are not available, which systemui.apk is needed and where to find it (maybe with "adb shell find / -iname systemui.apk")
[Magisk] Bogdan010:
You'll have to deodex RR or install xposed and fakegapps. Your choice
[Magisk] Loader009:
Checked Boardconfig.mk of my device, there it is set "WITH_DEXPREOPT := true", so it is indeed odexed...
[Magisk] Bogdan010:
Use xposed method
[Magisk] Shadow53:
People are suggesting deodexing or using Xposed, but if you're building the ROM yourself you can patch it to have native signature spoofing too.

https://github.com/microg/android_packages_apps_GmsCore/tree/master/patches

I believe people have had success applying the Nougat patch to Oreo ROMs, maybe with some slight changes.
[Magisk] guest4711:
Tested installation of NanoMod-mikroG from MagiskManager and from TWRP over 16.0. Works like a charm on my Sammy devices.

Edit: s/NanoMod/NanoDroid/g 666
[Magisk] Loader009:
[MENTION=4187311]Setialpha[/MENTION]

Rebuilt with different environment variables, with:

export DISABLE_DEXPREOPT=true

export WITH_DEXPREOPT=false

Now it begins to patch, but TWRP soon "crashes". (line 7078)

>> patching services.jar
CANNOT LINK EXECUTABLE "/system/bin/dex2oat": "/system/lib64/libart.so" is 64-bit instead of 32-bit
libc: CANNOT LINK EXECUTABLE "/system/bin/dex2oat": "/system/lib64/libart.so" is 64-bit instead of 32-bit
libc: Fatal signal 6 (SIGABRT), code -6 in tid 589 (dex2oat), pid 589 (dex2oat)

This happens for both, current stable and beta.

Still RR oreo.
[Magisk] Scottchy112:
Hello,

After i installed nanodroid via magisk on RR with the patcher, gps doesn't work. Tried to locate my position via gmaps but it doesn't work. Tried multiple other apps on the play store to check if it's because of google maps but they didn't work either.

I tried to get the logs via catlog when i spammed the location button in Google maps.I hope i did it right.
[Magisk] Bogdan010:
microG settings -> unifiednlp settings and check all available services
[Magisk] Scottchy112:
I do checked them. But i chose osm as nominatim api server. Do i have to choose map quest? If yes, what is the api key?

EDIT: Nvm, i had to choose map quest. Thought it wouldn't work because i dont have a api key but it do work.

Gps is fully funcionating now. Thanks
[Magisk] warface9991:
I accidentally clicked the "battery optimisation ignored" and it stuck and I can't revert it back. If it is enabled, does it drain battery?
[Magisk] Setialpha:
You mean for microG? No, it HAS to be disabled, else push notification and the-like won't properly work. No, it won't drain your battery (in this case).
[Magisk] warface9991:
Thanks for quick reply
[Magisk] _labello:
And now my device feels so slow even after I flashed the uninstall zip & reflashed my rom :(
[Magisk] Setialpha:
It doesn't do anything that could cause that. Also I'm sadly no claivkyant: no logs, no clue.

Either way, you may try wiping cache/dalvik-cache.
[Magisk] Setialpha:
Could you try flashing again and post the /tmp/recovery.log and also the output from

getprop >/tmp/getprop.log

which will be saved from /tmp/getprop.log, thanks in advance.
[Magisk] _labello:
Here is my logs, hope this shows the problem
[Magisk] ydd0ras:
hello mate, i have flashed it once again but i don't know if it's a problem because I have flashed the NanoDroid 16.2beta1 over microG stuff which I have installed manually (as apk). if yes, then I will make a fresh install and flash NanoDroid again and make then the logs.

you tell me!

many thx!

UPDATE!!!

strange things happen. I have debloated all of google apps and installed the microG services core/framework manually. now when I flash the NanoDroid from TWRP, after the reboot no microG appears but all the previously debloated google apps.

nix verstehen! silly!

UPDATE II: it seems that it screws the patched bootimg or similar. when I flash Magisk (15.3), after the reboot the gapps are gone, but still no microG.

i think, i will try that again but from the scratch!
[Magisk] apollo3x:
Someone please help me here! While flashing setupwizard in trwp, I check Google sync and flash nanomod beta! But upon booting, I can't find any contacts or calender data?

Also, micro g can't verify location,. I've given all the permissions and setup back ends too! Thanks in advance
[Magisk] Bogdan010:
Which version of Android do you use?
[Magisk] apollo3x:
I'm on oreo! Sync was lacking permission!

Now location is an issue! But the strange thing is, it was fine in beta 15!
[Magisk] Bogdan010:
Disable location, set it up in microG, restart and try again :)
[Magisk] apollo3x:
Thanks for your reply! I tried it but still stuck there, have a look
[Magisk] guest4711:
How about recovery log to see what happens when you try to flash? /data/adb/.nanodroid_* and /data/adb/.recovery_* are useful too...
[Magisk] apollo3x:
Thanks for replying, Google sync needed permissions! Please help me with locations!
[Magisk] Bogdan010:
Maybe
[Magisk] apollo3x:
Didn't help either :(
[Magisk] Bogdan010:
Reflash rom and microg. No idea
[Magisk] Setialpha:
In order for help, you should provude the requested files.
[Magisk] MonGoosY:
[MENTION=4187311]Setialpha[/MENTION] Just want to let you know that if DroidGuard Helper is installed as user app, SafetyNet fails because ctsProfile is false. So I edited nanodroid-functions to install DroidGuard Helper into priv-app and SafetyNet passes. I'm using OnePlus One with LineageOS 14.1 (Sultan's build)
[Magisk] SilentEYE:
I am a bit confused at the moment, so I try to figure out, if any Oreo ROM (in my case for Xiaomi Redmi note 4) is working with MicroG.

1. The Oreo ROMs (CrDroid, RR, Cardinal, etc) have signature spoofing implemented

After installing NanoDroid and requesting for spoofing permissions, I got a spoofing request dialog (like on nougat). All settings on MicroG Settings are checked and Playstore is working after [MENTION=7126506]Shadow53[/MENTION] tutorial.

2. Installing and setting up Ebay or Threema app, doesn't register into the MicroG's GCM, which I enabled before of course.

But some apps do register indeed.

I've tried ale5000's unofficial MicroG Zip too and I have the same problem.

Where is the problem now?

Not registering apps like here (postet by [MENTION=5627087]ale5000[/MENTION])?

Or aren't the ROMs deodexed ? (Why is there any signature spoofing then?)

Or is there a problem with latest MicroG v108?
[Magisk] kurtn:
Looks like apps find alternative messaging channels in Oreo so they not register to gcm.

The odex status is only relevant for ROMs without built in signature spoofing.
[Magisk] apollo3x:
Hi, I did not understand what are you asking for !
[Magisk] SilentEYE:
But I can't receive any messages. There is a gcm reset option in Threema app. And it gave me an error, everytime I try to force registering into gcm.
[Magisk] jenslody:
Good finding.

I use NanoDroid only for signature spoof (systemless) and have microG stuff installed from their fdroid-repo. But since some time (I think januaru) I could no longer pass cts.

After systemizing droidguardhelper (added systemless to /system/app) it works again.
[Magisk] mostevil94:
ive got a problem with yalp store, i have bought the premium version of ADW launcher 2 but yalp downloads the free version even tho i am using my own google account, could there be a resolve for this situation?
[Magisk] Shadow53:
Yalp cannot validate in-app purchases. If you purchased premium in the ADW Launcher 2 app, you'll need the Play Store installed to get premium.
[Magisk] piet8stevens:
Most of the time, using Play Store to activate the bought software is enough and then you can disable the Play Store to keep it from spying on you. That works for example for Titanium Backup Pro, for The Economist. But for the Financial Times, it does not work.
[Magisk] marcdw:
That last unchecked box will be so until you do something that uses that location provider. Then it should fill in.

Is the box always unchecked even after running something like a mapping or gps app?

LG G3 D851, CyanogenMod 12.1 ROM, Fechda Kernel R7, MultiROM, Tapatalk 4.9.5
[Magisk] apollo3x:
yes, its always unchecked! i open gmaps and i get acuurate location but after 10-20 secs, no more location! :( deja vu location crashes sometimes! i installed micro g without nanodroid, and it fine !
[Magisk] razorfancy:
Can someone please help me fix this problem?

I clean flash RR N 5.8.5 then flash magisk then flashed "NanoDroid-microG-16.1.20180209.zip" but when I reboot there isnt any contact sync or calendar sync apps, I check settings app(system apps) and using Es File Explorer but they arent installed.
[Magisk] Scottchy112:
Aha, i had the same issue and found a solution in the internet. You have to flash the sync apps separately. I upload the zip file to google drive. Just flash them and give them permissions in app settings. That worked for me.

https://drive.google.com/file/d/1VqU67WC_DuoWhk910IEwzzTdLpBApwZ_/view?usp=drivesdk
[Magisk] Setialpha:
They are included, but you need to enable them, see the project documentation.
[Magisk] Setialpha:
[MENTION=8010004]guest4711[/MENTION] already asked you to provide logs (logcat, recovery.log after flashing), I/we can't help you without.
[Magisk] Setialpha:
It's not that easy. DroidGuard crashes when installed as system app via Magisk. That's why it is installed as user app in first place. I may test things again, though as that's a bug that might be fixed in recent Magisk releases.

(Note: if it's installed as system app first, then as user app, both issues (crash+cts pass) are solved, but that's not an actual solution and given how android handles updates, it won't work without user interaction right from just flashing the zip (if a new system app and a new user app appear at the same system start and they are identical, Android drops one of them))
[Magisk] jenslody:
I have droidguard-helper installed as user app and use the terminal-systemizer module to put it into /system/app (it's done by creating a "org.microg.gms.droidguard"-folder and placing the base.apk into it and mount it on boot into /system/app).

I also tested updating the app from 0.1.0-4-xxx to 0.1.0-10-xxx through f-droid and it works without issues and crashes so far.
[Magisk] Thaymus:
Please

I'm a newbie to MicroG

Should I flash Nanodroid zip any time or just upon flashing a new ROM?

And shall I need any other files to flash or just the 200 MB zip file?
[Magisk] Bogdan010:
Flash nanodroid patcher, microg and google sync (optional)
[Magisk] Thaymus:
Appreciate your reply

So

I won't use Nanodroid(200MB zip file)

And where to find the Google sync(I just want to sync calendar)

And please the main question

Should I flash these with new ROM flash or not?
[Magisk] kurtn:
What ROM do you have? How do you update it? What functions of nanoDroid do you wish to use?
[Magisk] Bogdan010:
Sync apps here

(I forgot) flash zips before first boot otherwise microg will drain the battery
[Magisk] Thaymus:
I have Galaxy Grand Duos (GT-I9082)

Running Resurrection Remix Nougat

Each update I clean flash the new build

Functions I need:

1-Location services

2-Calendar sync

3-some applications don't start without checking the google account