yashsingh1/xdaforums huggingface dataset:
[Magisk] Setialpha:
9.1 beta1

Version 9.1 beta1 is now available. Changes since 9.0:

* Internal Changes
* move init script execution from `post-fs-data` to `late-start`
* fixup init scripts possibly not finding `Busybox` when installed as Magisk Module
* as a side-effect Magisk Log is now properly recorded and no longer imcomplete
* save init scripts logs in `/magisk/NanoMod/.logs/${script}.log`
* on boot existing logs will get `.old` appended, you alway have the current boot's logs and the previous'
* add `external_sd` init script which will symlink your external SD Card's mount directory to `/external_sd`
* known path from TWRP, makes it easier to `adb push` files to the SD Card
* SD Card needs to be inserted upon boot, else `/external_sd` won't be created
* it might take 30 - 90 seconds after boot up until `/external_sd` becomes available
* make `nanomod-overlay` script use `grep` and `sed` instead of `awk`
* makes `nanomod-overlay` script work in case `Busybox` is not installed
* add `nanomod.init` setup variable to make it possible to not install the init scripts
* Updates
* F-Droid (0.103.1)
* VLC (2.1.9~beta)
* Simple Gallery (2.10.7)
* Play Store (7.9.30.Q)

Only the full module has a beta build available. Download from AFH.

I think I've found the issue why NanoMod does not work with Magisk v13 snapshots, I have to test more, but as far as I tested as of now it's a bug in Magisk. I'll write more on that once I've done more testing.
[Magisk] zacharias.maladroit:
well, what was it ?

rebooting afterwards ?
[Magisk] J4jks:
I have installed NanoMod 9.0 with magisk on PureNexus ROM it just struck on boot animation

But on crDroid 3.3 it was fine

Thanks [MENTION=4187311]Setialpha[/MENTION]
[Magisk] Setialpha:
As mentioned in first post: run as root, so the 'su' command first.

Logcat please.
[Magisk] J4jks:
Logcat please.[/QUOTE]

Now tried without Magisk root and its booted with SuperSU
[Magisk] zacharias.maladroit:
yeah, well that was a bit hard to achieve because of circular dependency

phh superuser and MagiskManager needed to enable root / MagiskManager

thus I first had to download magiskmanager + phh.superuser from apkmirror, push it via adb and then install it (allow "unknown sources")

Also nanomod-overlay --permission didn't work , nanomod-overlay --pm did

Can you please add that for the Magisk-based approach ?

(I mean the instructions)

I'm sure this will make the installation a whole lot more possible for folks that didn't think of adding those two apks before using it

Thanks for the answer and these packages ! :)
[Magisk] d1n0x:
I clean flashed ROM and NanoDroid and now I get a lot more apps registered in Cloud Messaging. What is this sorcery?
[Magisk] Setialpha:
No sorcery, but marvin doing more work on GCM issues. NanoDroid includes a snapshot build of microG, not the last release.
[Magisk] Setialpha:
That issue has already been discussed here, it's a microG bug, which should be forwarded to the microG issue tracker.
[Magisk] Setialpha:
I suppose it's because your using Stock ROMs? Keep in mind there's no garantuee that the automatic GApps removal always works. I'll try to improve it, though.
[Magisk] Setialpha:
Dunno, what doesn't work? Is there a log to check?

Personally I don't use official YT app, but New Pipe works fine.
[Magisk] Setialpha:
I'll check this.
[Magisk] Setialpha:
AROMA is old, and abandoned by it's developer, so until the bug in TWRP isn't fixed, you'll have to create or edit the configuration yourself.
[Magisk] Setialpha:
What's a yellow shield? I never used inbox.

Log?
[Magisk] Setialpha:
Dunno if OP6 has any special location provider or not, that needs to get out of the way, but yes, Pie seems to cause issues for unlp.

On OP3T also issues on Pie, but fine on Oreo. If I find some time I'll give it another shot and see if I can collect any meaningful logs for microG/unlp dev.
[Magisk] Setialpha:
It does, unless there's a package with the same id installed. And that's the problem. If GApps update themselves, theese updates might prevent microG to properly work and vice versa.

Some package ids like GsfProxy or GmsCore are equal between both. So data never gets deleted and causesheavy issues, as microG GmsCore can't use GApps GmsCore data and vice versa, will cause crashes and thus will render them useless.

As I said not as easy as you might think.
[Magisk] mdl054:
Thank you again, your work is appreciated! :highfive:
[Magisk] DoR3M3:
NanoDroid-microG-18.3.20180920 & NanoDroid-microG-18.2.20180916 worked for me on the Essential with A/B partitions running Stock Oreo. The OnePlus 5T doesn't have the A/B scheme and both of these versions don't work for it.

I hope you can please get this working on a single partition device like the OnePlus 5T.

Not sure if you had a chance to look at the logs, do they show you anything?

Please let me know when you've got something for me to test.

Thanks

P.S. You might want to check the latest vdexExtractor, because for me on two different devices it is creating services_classes.dex not services.apk_classes.dex as listed on the tutorial for VDEX;

https://gitlab.com/Nanolx/NanoDroid/blob/master/doc/DeodexServices.md

P.S. I'm trying this all manually using the Debloater Terminal Emulator to uninstall Gapps and Play Store is not getting properly removed. So this doesn't just appear to be a NanoDroid-microg issue, but I don't understand why it's not getting uninstalled. I'm working with the Debloater DEV on this, I'll let you know what I find...
[Magisk] isaactsg:
I have the same issue with google maps on crDroid 8.1 on a Xiaomi Mi A1 with Nanodroid 18.3.1. Google maps opens and recongnizes my account but can't load tiles or find routes. This might be an upstream issue with microg, as a similar issue was brought up a year ago: https://github.com/microg/android_packages_apps_GmsCore/issues/455.
[Magisk] elraffa:
The same happens to me, do you know any workaround for maps and YouTube vanced? google maps from any browser is too slow for 360 view, what is for what I use it.

From your link, it seems to be the solution "The problem is the line break on the http header. Changing the line break from \n to \r\n and it worked again" but I don't know how to do it.
[Magisk] psychem:
INOX movies app.

The playstore icon turns into a yellow shield for some reason in the new build. Playstore gives a rh01 error clearing app cache doesnt work.
[Magisk] HemanthJabalpuri:
Sir..I just posted issue in microG github issues...

With 0.2.4 I can able to login but it cant correctly spoofs google play services..

I think you are modifying a bit to work right...?

If yes can you please modify 0.2.4 microG gmscore to work with your Nanodroid ...please..

Edit:- In github they said to use 0.2.4 to login and update after logging in... from this https://github.com/microg/android_packages_apps_GmsCore/issues/619

Thanks..
[Magisk] zsoltsandor:
I've started using LineageOS for microG, and flashed NanoDroid straight away on top of it. So far, I like the results, apart from some delays (or lost communication) with GMC, and the glitches with Maps API.

My observations so far:

Your patched microG components conflict with the packages from the official microG F-Droid repo, so update is not possible from there. An F-Droid repo could be useful, if your resources allow.

LineageOS updater will eventually find ROM updates, I guess keeping NanoDroid updated as well is a good idea. A helper app, something similar to the GApps updater, could also be useful. Also, if your resources allow.

Other than that I quite like the whole concept, my phone and tablet are definitely more responsive and have better battery life with microG and NanoDroid (I'm going with the full zip, because I want it all, though replacing some apps).

My devices are: Samsung Galaxy Tab S 10.5, Samsung Galaxy S7 edge.
[Magisk] vvilq:
Sorry for my stupid questions! Recently I flashed latest NanoDroid-18.3.1.20180921.zip (release of 21-September), but today the newest microg was released by Marvin (ver 0.2.6.13280 of 28-September,

microg.org/download.html ). Should I now update my phone from nanodroid's version of microg to the newer Marvin's version? Is it recommended? If yes, how can I update it? What is the safest way for such update? (clear step-by-step procedure is highly appreciated. Nanodroid on my phone was installed as Magisk module. Android is 8.1)

Or should I wait when this Marvin's microg release will be somehow integrated into the future Nanodroid release? What is ETA for that? 1 week, 2 weeks, month?

Also, what is the right way to update nanodroid from its previous version to the next nanodroid ver. ? Thanks!
[Magisk] iacchi:
It's not that easy to switch from nanodroid's version of microg to the official one. The best thing is to wait for an update from setialpha, which usually only takes a couple of days maximum anyway.
[Magisk] DoR3M3:
[MENTION=4187311]Setialpha[/MENTION], do you still have a copy of NanoDroid-microG-18.0.3.20180908? This was the last version that worked for the Essential, maybe it will work for the OnePlus 5T.

The OnePlus 5T is a pain in the butt, even if I manually debloat with the Debloat (Terminal Emulator) I can't manually install microg, it won't go.

Also in F-Droid if I add the microg repo and try to install it in F-Droid I get a popup saying;

A previously installed package of the same name has a different signature then the new package and the old package's data was not removed.

After doing the debloat I ran; find /system /data/{app,data,misc*,system*} > /sdcard/find.txt

I'm attaching this find.txt maybe you can see a problem?

Hey isn't it time to upgrade your OnePlus 3T to a 5T? LOL ;)

This 5T is a Royal Pain In The Butt, I don't know what OnePlus did to Oxygen OS, but it's not debloating like other Stock Oreo... :eek:

THANKS

P.S. Going either the Debloater (Terminal Emulator) method or NanoDroid-microg, I think I may of found the problem;

./adb uninstall com.google.android.gms
[Magisk] jenslody:
You have a lot of data below '/data/data/com.google.android.gms'.

This is most likely causing your problem.
[Magisk] American_Jesus:
Stable Archive https://androidfilehost.com/?w=files&flid=156387
[Magisk] DoR3M3:
I saw all this, and I've been ripping through, taking out heaps, but still not getting at it. But, if I have to manually remove now, the entire point of trying to do this "Systemlessly" with the Debloater (Terminal Emulator) isn't working. I'm still trying to figure out if the Debloater (Terminal Emulator) is suppose to be able to do this, because I had it working just fine on other devices, but now on the OnePlus it doesn't. So maybe it's one of those things were it might work and might not, I'm still trying to figure it out.

Also I wonder if any libraries of gms can effect this, where I might need to rip out libs too?

Also in /system/priv-app there's GmsCore directory, but it's empty from the Debloater, but I wonder, if even having an empty named directory as such could also throw this off, and I should remove it?

hmm

NanoDroid-microG-18.0.3.20180908 is not there, that's why I asked... ;)
[Magisk] Setialpha:
The latest release is already included. It has a lower version number, because it's a snapshot build, but marvin has not made any changes since the snapshot build, except bumping the version number and making a new release.
[Magisk] lovepreetsg:
Do anyone have Gsync zip file I am unable to download it form shadow53 website
[Magisk] Apex Predator:
That makes sense. Now I know why some apps magically wanted to register out of the blue last week.
[Magisk] d1n0x:
Select to install it in the Aroma installer and use the full nanodroid zip
[Magisk] Setialpha:
I'm testing a few things, including:

- FDroid repo for my custom apks instead of nupd

- improved GApps removal for Stock ROMS (keep in mind: I can't garantuee that it'll work on all ROMs)

- replacing AdAway with Blockada

- Lightning snapshot build or replacement

- OpenLauncher snapshot build

- Oandbackup has been updated recently, I'm gonna test how good the new release is

No ETA.
[Magisk] Setialpha:
That's likely the problem. microG GmsCore is /system/priv-app/GmsCore aswell. So you debloated both GApps GmsCore AND microG GmsCore. Don't do this, microG GmsCore will replace GApps GmsCore.
[Magisk] Namnodorel:
Note about Blokada: Although it looks prettier, it is also unfortunately incompatible with any VPN application or rootless firewall like NetGuard.
[Magisk] Setialpha:
It's not just prettier, it has several features Adaway lacks

- rootless

- DNS changer

- variety of block lists

- app white listing

Yes, it conflicts with VPNs, but as you know NanoDroid is configurable, so you can safely opt-out.
[Magisk] DoR3M3:
I was doing this all manually debloating and installing microg. I wasn't using NanoDroid-microg at the moment, first testing out by hand... ;)

I did however need to go with an Xposed UnifidedNLP module for the Location, it seems to be an issue with Stock Android over Custom ROMS, at least it's my understanding.

Now that I've got the manual method figured out, time for NanoDroid! ;)

I posted some screen shots of the manual method of success, but I still used the NanoDroid VDEX Deodex method and the NanoDroid-patcher...

===========================

P.S. [MENTION=4187311]Setialpha[/MENTION], after making this post I went back and did these steps for OnePlus 5T Oxygen OS Stock Oreo 8.1.0 - (This is not a Dual Slot A/B device, one partition scheme)...

1. Fresh clean install Oxygen OS

2. Patched VDEX method

3. Booted into System

4. Booted into TWRP flashed Magisk

5. Booted into System and ran these cmds; adb shell >> su >> cd /data/data >> rm -rf com.google.android.gms

6. Booted into TWRP and placed .nanodroid-setup > /sdcard/.nanodroid-setup

Contents of .nanodroid-setup

nanodroid_microg=1

nanodroid_fdroid=0

nanodroid_apps=0

nanodroid_overlay=1

nanodroid_zelda=0

nanodroid_mapsv1=1

nanodroid_init=0

nanodroid_gsync=0

nanodroid_swipe=0

nanodroid_forcesystem=0

nanodroid_bash=0

nanodroid_nano=0

nanodroid_utils=0

nanodroid_fonts=0

nanodroid_override=0

nanodroid_play=4

nanodroid_nlpbackend=0

7. Flashed NanoDroid-microG-18.3.1.20180921

8. Booted into system and microg was not installed... :(

I ran find /system /data/{app,data,misc*,system*} > /sdcard/find.txt please have a look, hopefully it will help you, because I don't know what's going on...

>

>
[Magisk] Setialpha:
First step to NanoDroid 19 done. Took me a while to handle F-Droid expected APK signatures for signature spoofing APK, but:

The NanoDroid F-Droid repo is now live. With updated versions of microG GmsCore, Play Store and MPV.

This build of microG GmsCore includes the GoogleSuiteLogin fix from jimbo1qaz and Wellbeing added to known Google Packages.

OpenLauncher aswell, but you first need to uninstall the old one due to signature mismatch.

https://www.nanolx.org/fdroid/repo
[Magisk] [Alien]:
Thanks for your job. NanoDroid is awesome, works flawlessly for me with LineageOS microg on my Xiaomi Redmi Note 3 Pro
[Magisk] HemanthJabalpuri:
What is above fix?

Is it is login issue i.e., unable to tap login or cancel?
[Magisk] Setialpha:
Nope.

https://github.com/microg/android_packages_apps_GmsCore/pull/624
[Magisk] HemanthJabalpuri:
Sir with microG installer in 4.4.2 rom..

The lib files for arm are storing in /system/lib/arm/ not in just /system/lib/...

Any issues will arise from above thing?
[Magisk] Setialpha:
I don't think so.
[Magisk] castrum_doloris:
Perhaps you could include both, so the User can deicide which app he wants to use. In my case VPN is used by Orbot, so Blockada isn't an option for me.

Maybe you could also include the updated AdAway Version 4.0.9:

https://androidfilehost.com/?w=files&flid=249276

Link is coming from this thread, as the official thread hasn't been updated yet

https://xdaforums.com/apps/magisk/magisk-unified-hosts-adblocker-t3559019

As I'm writing of Orbot (and TorFox): installed within NanoDroid package they don't work and are force closing on Android 8.1.

I guess this has already been reported somewehere, I'll do my reasearch now. So most likely you can ignore this last part ^_^
[Magisk] greenjongreenjon:
This worked for me!

Using Linage-for-microg on a Nexus 6 (Verizon).

-Factory reset

-installed the latest linage-for-microg

-installed latest patched play store

-(I didn't have any account to delete)

-turned sync off

-cleared play store data

-signed in to play store, got the error

-closed play store

-opened play store AND IT WORKS.

-Thank you.
[Magisk] guest4711:
4.0.9 is not as stable as 3.3: It crashes when using file:// protocol (to include local files), seems to have problems when you delete sources, use whitelists etc.

So I would not recommend to switch to the current beta.
[Magisk] williamlaw:
Since Nanodroid is 0.25 only, may I know how to update MicroG to 0.26 ?

Thanks
[Magisk] Oswald Boelcke:
Personally, I search a thread and read a few days back before I post but that's simply my best practise.

Please see this post by Setialpha from 29 SEP to answer your question.

Alternatively, download the GmsCore from the µG website. (usually I rename the downloaded file to GmsCore.apk). By use of a root explorer, move the downloaded file to /system/prov-app/GmsCore replacing the current GmsCore.apk in that target location. Confirm that the file has "644" permissions. Reboot.
[Magisk] iacchi:
Setialpha, I've tried to enable your fdroid repository by pasting the link in the add new repo page, but of course there is no fingerprint and the repo doesn't really load. I see from your screenshot that you enabled it with fingerprint and everything, may I ask you how did you do it? Maybe you can post a screenshot of the full QR code?
[Magisk] guest4711:
Just tried it with the url https://www.nanolx.org/fdroid/repo/ on f-droid 1.4. About 3' after adding the url to the list of repos f-droid shows the fingerprint.

To make you happy I attach the screenshot you requested...
[Magisk] Adolamin:
Hello all,

Currently using latest NanoDroid MicroG and I'm getting error 495 when trying to download or update apps in Playstore. I've reinstalled NanoDroid MicroG and still no change. Not sure if this is MicroG or not. Any help here would be appreciated

Also a side note, when I try to nupd ps it won't connect to nanolx.org: error 404 not found.
[Magisk] mongo0:
same here, also whatsapp keep crashing ( havent updated it for some weeks though)
[Magisk] Setialpha:
Error 495 is a non-microG/NanoDroid related issue and fixes are noted over the web very often. tl;dr try clearing all cache and/or re-installation of Play Store.

nupd was deprecated in favor of a F-Droid Repository, official announcement a few posts back
[Magisk] Setialpha:
The above URL now is a proper, though very plain, web page showing the full link and the qrcode.

Docs updated, aswell.
[Magisk] bertino:
Could you make the link clickable?
[Magisk] marcdw:
I take it you mean the qrcode? The link itself is clickable. Just clicked it a few minutes ago. Default browser came up then "open with" dialog where I chose F-Droid. Repository was added and updated. All good.

What's not clickable?

LG G3 D851, AOSPA-L ROM, Nebula Rev9.3 Kernel, microG (NoGapps), MultiROM, XDA Legacy
[Magisk] vhick:
Hi [MENTION=4187311]Setialpha[/MENTION]

I have a problem with the nanodroid apps. I have a problem with Amaze, it keeps fc while tapping settings. I also have a problem with tor for Android. It keeps fc. I also have a problem with some of my apps.

Thank you for your awesome microG
[Magisk] Setialpha:
If something fails you should provide a logcat, so I can look at the issue, Tor is an early preview, so issues are to be expected.

microG is not mine, but [MENTION=3999488]MaR-V-iN[/MENTION] work.
[Magisk] Setialpha:
It is now.
[Magisk] vhick:
Hi [MENTION=4187311]Setialpha[/MENTION]

I provide the logcat for the two apps. I hope it helps.

Thank you...
[Magisk] ashwini215:
I want to install these new repositories.

But after uninstalling the old verison of gmscore, when i update gmscore from fdroid the apk gets installed at /data/app and not at /system/priv-app.

the same goes with play and droidguard apks.

I think I am not doing it the right way. plz guide me guys.
[Magisk] clewis.it:
You shouldn't need to uninstall if you already added the new repo.
[Magisk] ashwini215:
After adding the repo, when trying to upgrade the apks, I being asked to uninstall the previous version because of the different signature both versions have.
[Magisk] Setialpha:
I suppose you've been using the official apks previously? Then of course you can't just update. In this case you need to install NanoDroid first. Or install the apks into /system manually.
[Magisk] Setialpha:
A small step for me, a big one for the user: the documentation on GitLab (or GitHub for terran mirror-universe people) now has a proper introduction and a full Table of Contents, for easier navigation.

If you want to contribute suggestions or provide improvements to the docs, it's very welcome.
[Magisk] :
Hi, i have currently using nanodroid v18.0.2 microg module and im trying to update my gmscore

I added your repo on f droid and when pressing install it says error install microg services core /data/user/0/org.froid.fdroid/cache/apks/nanolx.org-1/repo failed to verify. what should i do ?
[Magisk] Setialpha:
Provide a logcat, it maybe contains a hint. I suppose you're on the latest F-Droid release?

You may also update NanoDroid and see what happens then. If unsure, make a TWRP backup beforehand.

It's working fine here.
[Magisk] :
I updatet latest, here is log

edit:

i reinstall froid and now it says the extension has not been granted privileged access to create an error report

EDIT2: I managed it to work now! played around fdroid and it didint had unknow sources enabled so i think that was the problem, all good now
[Magisk] jenslody:
Or simply use the new repo and systemize gmscore and droidguard-helper with the terminal-systemizer magisk-module by [MENTION=7296895]veez21[/MENTION].

Just need to do it once, updates work without that (system-app updates go into /data anyway).
[Magisk] iacchi:
Thanks to guest4711 for the inital screenshot and to setialpha for creating a proper web page. I have used the qr code to add the repo and now everything works fine.

---------- Post added at 09:49 PM ---------- Previous post was at 09:20 PM ----------

Ok, so, short report. I usually install nanodroid with yalp and fakestore, but after enabling the fdroid repository and letting it update the apps, I found myself with play store installed as well, which I didn't really want. Is there a glitch somewhere?
[Magisk] Setialpha:
No. Fake Store and Play Store have the same package ID, thus F-Droid thinks Play Store is installled, when Fake Store is installed.

But... since both Fake Store and Play Store are signed by me, you might have 'updated' Fake Store to Play Store (lol, sorry).

This will no longer be possible with 19.0. But I'll upload a 18.3.2 tomorrow to kill this issue beforehand.

For now uninstall the 'update' and in F-Droid ignore Fake/Play Store updates from 3dot menu in the F-Droid app page.
[Magisk] Setialpha:
Patcher 19.0-test1

Hi all, a new test build for the patcher is now available. Please test and report whether it works.

It should improve ROM compatibility, most linker related issues should be gone.

SHA256 for this file: ebf576ed1e8808d044deac1adb14d130fb3f1751bb28184064a42fcba571aa0e
[Magisk] iacchi:
Right, I didn't think about the same package ID issue. I can't really uninstall the update, it's a system app and I don't have that option (afaik). I can wait for nanodroid updates, that's not a problem. Mostly, when the update comes (I usually update via TWRP), will play store go away?
[Magisk] Setialpha:
Just make it go away. Settings > Apps > Play Store > 3dot menu > uninstall updates. Updates are user apps, always.

Then block updates for Fake Store in F-Droid until the next update of NanoDroid.
[Magisk] iacchi:
I didn't know that, good to know. Update removed and future updates ignored, all good now.
[Magisk] psychem:
--deleted--
[Magisk] zsoltsandor:
Thanks for the F-Droid repo, it makes life significantly easier.

Do you think you could add a script to the full package that changes the DNS to Cloudflare?