yashsingh1/xdaforums huggingface dataset:
[Magisk] Liflo:
Hello, I'm new to magisk and curious about nanodroid/microg

I came from cusrom crdroid Android 9 for Samsung Galaxy A5 2017

I installed full nanodroid through twrp

I read about the installation instruction, didn't know maybe I missed something

1. Already turn on crdroid spoofs signature in miscellaneous setting and apps permission in advance setting

2. Self-check showing system spoofs signature unchecked & couldn't do anything (tapping every where) it said read the instruction again.

3. Trying to connect XDA with google it said google play service error & opening play store fail to load (just blank)

Just wanna know maybe the cusrom couldn't using microg

Thanks :)
[Magisk] Estebanium:
Thank you for the feedback guys. I was not sure if Battery related issues are a cause of NanoDroid, because why wouldn't a Core Service drain the battery? I know that LineageOS 16 has a common battery drain of up to 4 %/h, but I wasn't sure where to look at. BetterBatteryStats just showed a lot of alarms of Android. I switched from LKT to FDE.AI and with Appops I double checked the permissions for waking the device or run in the background. It seems to settle down now.
[Magisk] castrum_doloris:
Did you install GApps before µG/nanodroid?

Did you alter the nanidroid setup files? If yes, what is your setup?

If no, maybe you should read the documentation about it and set up nanodroid after your needs.

Always a possibility (and recommended) is to do a clean install of your Rom (without GApps) and install µG/nanodroid straight away

---------- Post added at 01:55 PM ---------- Previous post was at 01:46 PM ----------

Did you ever try to remove these "AiO kernel tweakers" and observe your battery stats?

These things often bring more harm than good, and are rarely useful at all. It's way better to look for custom kernels dedicated to your device.

For me these Alarm Wakelocks are an additional hint for this.

And with AppOps you can't block these kinds of wakelocks. You need a kernel, a kernel editor (like ExKernelmanager) and/or Custom Rom which are supporting to block wakelocks.

To conclude: µG should not drain battery. And is not responsible for alarm wakelocks. As far as I know
[Magisk] Liflo:
Here's how I installed the cusrom and nanodroid

1. Wipe data, system & dalvik/cache

2. Flash the cusrom - magisk - nanodroid

3. Wipe dalvik/cache

No GApps at all.

Did I miss something?

No, I didn't do anything to nanodroid file since I downloaded it.

I'm lost, don't know what I missed.

Maybe this cusrom didn't support microg

Thanks.
[Magisk] castrum_doloris:
Hmm... should be working in theory. And crDroid should work with µG too.

Which Magisk and Nanodroid version do you use?

You could try to install the official µG (PlayStore won't work with this, but for testing you could try)

You can use the Setup Wizard for this or create the setup file by yourself (if your TWRP doesn't support AROMA)

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

(Change lines:

nanodroid_gmscore=1

nanodroid_play=00 or 20)

Else, You could try to start over again with crDroid and/or try a different Rom.

(I don't own your device, so I'm not able to help you very well. Sorry)
[Magisk] garylawwd:
I have official MicroG with working playstore
[Magisk] DoR3M3:
Actually it was Dirty-227 my bad...

If I see this again, I'll be sure to post a logcat...

Thanks
[Magisk] Oswald Boelcke:
I'm still on Nougat and have no own experiences with crDroid. So I apologise in advance if my post isn't really useful.

Although Setialpha stated here on 2019-02-11

your issue may still rest with signature spoofing on crDroid. Has it really been fixed? I don't know? Any comments from other crDroid Pie users are appreciated.
[Magisk] asymcon:
No, I haven't yet installed Magisk and getting DF error even on a vanilla system.

---------- Post added at 09:54 AM ---------- Previous post was at 09:38 AM ----------

There's no such setting in my release of microG (0.2.6.15090-dirty-167)
[Magisk] Oswald Boelcke:
I'm using µG 0.2.6.15180-dirty-241 but have always also had that setting in earlier versions. Personally, I actually refrain from bug reports connected to outdated versions.
[Magisk] azakosath:
I was using crDroid by that time and the signature spoofing hadn't been fixed no matter what the changelog said, I had to run the NanoDroid patcher 20.4 to get it working.
[Magisk] asymcon:
Yes I saw in your earlier screenshot.

0.2.6.15090-dirty-167 is

not outdated

, it's supplied with Nanodroid stable

0.2.6.15180-dirty-241 is supplied with beta package.

Anyway I tried with the beta package, and still getting stuck on DF-DFERH-01 without Magisk, and with clear data/cache for Play Store.
[Magisk] garylawwd:
What worked for me was open your browser and search for an app and then when prompted open using play store and it should work
[Magisk] Oswald Boelcke:
I don't want to argue but by my definition, NanoDroid 20.7.20190310 (stable) is not outdated but if installed a month after its release, the contained µG Services Core require a update.

NanoDroid 20.7.91 (20.8-beta2) comes with 0.2.6.15180-dirty-227 in accordance with the changelog in the release post as of 2019-04-03 but also according to the readme in the zip-file. If installed later, the contained µG Services Core require a update via the Nanolx fdroid repo, in which 0.2.6.15180-dirty-241 is the latest available version.

But back to your issue. To force stop Google PS and to clear data and cache is always a good idea. Did you also try to remove your Google account, reboot, and to create a new Google account?
[Magisk] asymcon:
Ok, thanks for clarification. :)

I've cleared data, system and dalvik cache and added the account on a vanilla system.

Not yet, in fact I haven't tried any other account beside this one. Let's see...

---------- Post added at 12:37 PM ---------- Previous post was at 11:56 AM ----------

This works!

Thanks a ton.

EDIT: Two paid apps authorized fine so far.
[Magisk] marcdw:
You're right it shouldn't but there have been times when it has. I had a couple/few ROMs where some service went wild and kept the phones awake. Had to block the service. This was late last year and hasn't happened again with microG installations since. I never did check if it was a known issue or not at the time.

LG G3 D851, Paranoid Android 7.3.1, NanoDroid, MultiROM, XDA Legacy
[Magisk] asymcon:
In microG under 'more' settings, there's "Allow connecting to Google servers" and "Connect to Google via Tor network", both greyed out.

I take it those features are not yet implemented?
[Magisk] Oswald Boelcke:
Affirmative.
[Magisk] Liflo:
I download the latest file.

I'm on crdroid + gapps + magisk now

I download signature spoofing checker

It said, signature spoofing : disabled

Did it prove that the cusrom doesn't support microg?
[Magisk] azakosath:
No, you should go to:

Apps & notifications/ App permissions/ Spoof package signature

And grand the permission manually. Then you can check the spoofing checker.

Edit: I'm not sure if crDroid has an option for enabling signature spoofing in crDroid extra settings. You should check this.

And it's better to ask this in crDroid telegram group, it's off-topic here.
[Magisk] Liflo:
Already enabled signature spoof setting in miscellaneous setting on crdroid & granted spoof package signature in advance permission by enabling the apps.

Like the instruction said.
[Magisk] PoochyX:
Micro G is spying on us I have discovered it in the source code...
[Magisk] azakosath:
And? Didn't it work? Anyway, just read my post in the previous page.
[Magisk] Liflo:
Didn't work, thanks.
[Magisk] Oswald Boelcke:
My very personal opinion: Such a statement requires evidence and proof when it's made, probably best in the µG thread. I think the µG developer should have a chance to reply.
[Magisk] guest4711:
What did you discover? Please clarify.
[Magisk] Bracher:
Dear all, I can't activate Playstore on my Note 3 with ResurrectionRemix v.7.0.2 (Android Pie), but I have no problem with the unofficial version of LinageOS 16.0. Both have been installed clean, Signature Spoofing enabled, MicroG working ok with both versions but if I try to log in playstore the first two steps are ok (Name and password) but afterwards it is stuck (the page accept the conditions of Google). I have Magisk up to date, working ok, I have magisk-riru-core and magisk-Ed Xposed, everything works well, but the problem with playstore is a bit annoying as ResurrectionRemix is updated more regularly than LinageOS, so I would prefer RR. One thing LinageOs has to be patched and the Patcher works fine, RR is already patched so the Patcher won't work,m ight thie be the reason. I asked as well in the RR thread if somebody had the same problem but so far with no outcome. It's not a big problem as I can go back to LA 16.0 (LA Nougat is no longer mainained)

Happy easter to all of you
[Magisk] rayman95:
Each month [MENTION=2693412]haggertk[/MENTION] update LA16.0....last is one week old....did you tried beta version of nano???? And without xposed
[Magisk] n76:
Please indicate the place in the source code you've found this issue.

I haven't come across anything that worried me so I am curious about what I've missed.
[Magisk] temporarium:
I think he's unhappy that his calls to abandon microG go unheeded, so he's trying to scare users away.
[Magisk] tsky7:
I'm having the same problem on my Galaxy S5 with Bootleggers 4.1 and sigspoofing enabled tried different roms so far and nothing works, a week ago everything was working fine

Edit: I always use force system mode, but with magisk (18.1) I get the same problem
[Magisk] Bilge656:
Has anyone had problems with a bootloop after installing the big nanodroid package? I installed unofficial lineageos 16 on my Pixel 2 XL, then the sig spoof patcher, then magisk, then nanodroid.
[Magisk] Bracher:
Yes I tried in meantime without Xposed and with the beta version of nano, but I had the same problem - so I'll go back to LA. Unfortunately with my tablet SM-P600 there is only RR no unofficial version of LA, but let's see perhaps it works there. But I'll wait a bit.

Thanks for all replies and a restfull eastern
[Magisk] Setialpha:
No, but what's the logcat?
[Magisk] Cyberavater:
Not installing

Log provided in the attachment.
[Magisk] Bilge656:
Logcat is attached.

My steps this time were install rom, flash twrp, reboot recovery, install patcher, install magisk, install nanodroid -> it shows lineage boot animation for a second and then boots into twrp

I rebooted recovery to switch A/B partition because the patcher wouldnt work otherwise.

I guess even though the patcher said it succeeded, it failed?

Edit: I tried installing NanoDroid on an unofficial rom of CarbonRom, since it has support for signature spoof. I installed the rom, twrp. Rebooted recovery to switch partition, then installed magisk then nanodroid. It reboots directly back into twrp.

I uploaded the second logcat too.
[Magisk] starbright_:
In manual there is mentioned a re-registering via "nutl -r <appname>.

I tested this bit found - there is no option "-r". Do I have wrong version? How can I get this working?

I have in selfcheck all green but the I don't see a registered app for push notification.

Also the app "push notification tester" fails with registering. What am I doing wrong?
[Magisk] PoochyX:
You probably using up to date apps that are using fire cloud messaging

[emoji3436]I Willl Scarfice For Those That I Love [emoji3434]
[Magisk] starbright_:
So can you tell me an app that are for sure works, jut to test this?

And if I understand this right - FCM is supported.

https://github.com/microg/android_packages_apps_GmsCore/issues/439
[Magisk] TiTiB:
New behavior. For no apparent reason (no system changes, nor apps that should effect this, self-check is Okay) the gms core (Play Store) stopped connecting. At each stage, Signin/Password/I agree, there is data going up and down, but there is never an apparent connection made to Play Store. No error, just never connects.

I'm baffled, and have tried reflashing NanoDroid-microG (even the 20.7.91.99999999 version) but am getting "updater process ended with error 1".

I have read that the "error 1" issue will be fixed in next release, but am eager to get things working now. Any help will be much appreciated.

Huawei Mediapad M5 [8.4]

Rooted w/Magisk

SHT-W09 (C567)

LOS 15.1 [unofficial]
[Magisk] marcdw:
[MENTION=4721947]Bilge656[/MENTION], you have a lot of access denied messages in your TWRP log. Stuff like this...

libc: Access denied finding property "ro.vndk.lite"
libc: Access denied finding property "ro.vndk.version"
libc: Access denied finding property "libc.debug.malloc.options"
libc: Access denied finding property "libc.debug.hooks.enable"

I'm ignorant in those matters so I'm sure the Dev will have a clue if those are the reasons for the reboot into TWRP thing.

LG G3 D851, Paranoid Android 7.3.1, NanoDroid, MultiROM, XDA Legacy

---------- Post added at 05:45 ---------- Previous post was at 05:39 ----------

For some reason the mpv libs fail to install according to your logs. Everything before that seemed fine. For the time being see what happens installing without mpv. Once again, the Dev or others will know more.

LG G3 D851, Paranoid Android 7.3.1, NanoDroid, MultiROM, XDA Legacy
[Magisk] Cyberavater:
When I use aroma, the install finishes successfully but without installing the thing. :silly:

After the reboot Nanodroid *the whole module* is absent.
[Magisk] PoochyX:
What version of magisk are you using

[emoji3436]I Willl Scarfice For Those That I Love [emoji3434]
[Magisk] Cyberavater:
Latest/None result is the same.
[Magisk] PoochyX:
Sometimes you got to downgrade magisk versións to get certain results every phone is different with every combination of magisk

[emoji3436]I Willl Scarfice For Those That I Love [emoji3434]
[Magisk] Cyberavater:
That's what I said, sometimes I tried even without Magisk.

---------- Post added at 04:47 PM ---------- Previous post was at 04:44 PM ----------

These problem doesn't occur with the v20.6 tho.
[Magisk] Oswald Boelcke:
Sir, I've requested you here to provide evidence of your accusation towards @MaR-V-iN, for me personally a highly recognised developer who's allowed me independence from Google. As far as I see you've never accused him directly in the µG thread or raised a respective issue on Github. As I don't use Telegram, I don't know if you were active on the respective Telegram channel.

I'm only able to assume why you raised your accusation here; please accept that I don't publish assumptions publicly.

May I politely ask you again to prove your accusation! And if you're unable for whatever reason, I think it be simply appropriate to modify your post or get it deleted.

As far as I see there're also other users waiting for your response:

P.S. I definitely recognised that you're trying to help and support a lot of users with NanoDroid but personally I fear such a post discredits you, which would be a pity!

****************************

@Setialpha, I apologise for being (again) off-topic in your thread but I couldn't let this statements rest as it is.
[Magisk] PoochyX:
It could just be analytics traffic and I took it over board I do apologize about my actions

[emoji3436]I Willl Scarfice For Those That I Love [emoji3434]
[Magisk] guest4711:
You told you did find it in the sources. Where do the connections go to? Which data is send? Even analytic data needs approval by the user here in Europe and nobody asked whether we agree with collection of data...

So please clarify.
[Magisk] jenslody:
Just point to the sources, where you find the suspicious code.
[Magisk] Oswald Boelcke:
I concur that µG contains a Google analytics module (refer to screenshot) but even if activated I'd personally refrain that from calling it spying. Even I was easily able to disable that service.

Even if such a module is implemented (and although activated by Google as default) is it activated? It can easily be deactivated by a developer in the Android manifest. Such a deactivation might look like this (taking Signal as a specimen). Did you check the µG code against that?

But from my point of view even better, developers can easily remove all those classes as it was e.g. done for Conversations: https://github.com/siacs/Conversations/commit/c2067e3b56364317bc384b55e320b72326fb1de6

Why didn't you just raise such a request/issue on the µG Github. I'm convinced you'd have got an open ear...
[Magisk] budbay:
[MENTION=4187311]Setialpha[/MENTION] trying to download, it seems nanolx.org is down. I tried on and off VPN so I don't think its my connection. Can anyone confirm?
[Magisk] Setialpha:
It should be working again now.
[Magisk] Cyberavater:
Please check it [MENTION=4187311]Setialpha[/MENTION]
[Magisk] guest4711:
Do you know there are holidays? And that setialpha is working for free in his free time on this project?

It's less than one day passed after you did post the logs. No need to remind anybody to look at it...
[Magisk] PoochyX:
Thats what I was Goin to show that screenshot Oswald however my phone had died and just now got it back on... I believe an open ear is warranted because we shyed away from Google to not be tracked and not have are privacy compromised and now again are usage access as for certain is being monitored now where is this analytics being transfered to and what exactly is being monitored with the permissons we giving Micro G at runtime it is a device administrator before even modules like xprivacy Lua are doing thier jobs

[emoji3436]I Willl Scarfice For Those That I Love [emoji3434]
[Magisk] Vavun:
I'll just leave it here

AnalyticsService.java

That is everything that the analytics service does

Log.d(TAG, "onBind: " + intent);
return null;
[Magisk] starbright_:
How can I check that push notification/GCM works?

I have 2 phones here - both LOS, Magisk, Nanodroid - all selfcheck green (or better blue), and also enabled Google registration and GCM. So what am I missing to get this working? Is "push notification tester" an app that should trigger that? I get for step 1 all green except "register for push notification failed".

Don't have firewall or adblocker ... Please help!

Either I missed something or none of the apps support this. If someone have registered apps, please let me know the name and whether there is something that I might have overseen. Thanks.
[Magisk] Cyberavater:
Yes, and Setialpha can say it him/herself. No need to be one's unproductive lackey. Don't just quote if it's no helps your providing! Stop wasting others/your time.
[Magisk] oF2pks:
All you need to know is explained here https://en.m.wikipedia.org/wiki/Method_stub

Basicaly, if you want to setup a working spoof, you need good stubs...

( [MENTION=4187311]Setialpha[/MENTION] , thx for github synced back.)
[Magisk] temporarium:
I'm on Oreo.
[Magisk] temporarium:
One more...
[Magisk] D4ND310:
If I remember from either the main Documentation, or possibly a reply in this thread, apps you want to receive Push Notifications for need to be installed after you install MicroG/NanoDroid to be correctly registered. Otherwise, they will just continually try to refresh with no result.

Back up the app'/ app' Data which you would like to receive Notifications from, uninstall/reinstall the app'/Data with NanoDroid already installed. Then, I believe, your app' should get fully registered for GCM.
[Magisk] starbright_:
I know that, so I deinstalled and re-installed it few times. Even with reboot inbetween. Nothing happened. I even did it on LOS15.1 and 16. Same at different devices. So I miss something. Permissions? Something that not automatically set by nanodroid ....

I do need an expert.:confused:
[Magisk] starbright_:
Look. What I don't have is a google account or something like that. But I guess that's not needed - as device is enabled for registration....
[Magisk] Setialpha:
Working here. Log?
[Magisk] Setialpha:
I'll have a look soon™
[Magisk] Cyberavater:
Thanks, will be waiting.
[Magisk] Oswald Boelcke:
Are you convinced this is true. As far as I know Xposed and its modules (i.e. also XPrivacyLua) are running even before the OS is booting. And again: Did you check that the module you're complaining about is activated.

But anyway, I'm leaving this discussion now as it's off-topic to me in this thread.

Just this morning, updated Bromite Webview, µG Services Core and Google PS via the Nanolx F-droid repo. A few minutes later I submitted a invoice to my health insurance via their application and received the "turn-in" notification. Additionally, after I just noticed your post, I positively tested the notifications with "Push Notification Tester" (please refer to attached screenshots). BTW: Using both, AFWall+ and Adaway.

:good:
[Magisk] Tomatot-:
Try to open your dialer and copypaste this:

*#*#42678278#*#*

Then try again

It might fix it.

You can also try to reboot after trying this.
[Magisk] starbright_:
I did this. Not working.

Is halting the app and clear all the memory of it sufficient or do I really need to deinstall.

Of course I tried both ways. But downloading Push notification tester again and again is kind of boring.

microG is the only module in Magisk (microG sub module v20.7.20190310) and it is checked (active)

Please also look here to screenshots:

https://xdaforums.com/showpost.php?p=79385862&postcount=6129

If you have other ideas, please let me know.

My only hope is that [MENTION=4187311]Setialpha[/MENTION] can found something in log ....

---------- Post added at 04:55 PM ---------- Previous post was at 04:44 PM ----------

I added repo an got message to uodate microG core and Playstore. Playstore couldn't be updated, got error.

" aufgrund eines unbekannten Fehlers fehlgeschlagen"

Is it because I installed Yalp+Fake store? Is that the reason?

Installed Version: 0.0.2 recommended 14.6.56 ?!?
[Magisk] Oswald Boelcke:
Most likely. I'm using only Yalp and Setialpha modified Google Play Store (mGPS). Yalp is my main tool but mGPS I only use for two reason (without precedence): 1. To be able to make (in)app puchases. 2. To participate in beta programmes on GPS; I'm currently registered for 16 of those including e.g. SD Maid, OpenVPN for Android, ConnectBot, Greenify, BetterBatteryStats, Kernel Adiutor.

I don't have fake store installed.

My personal suggestion if you also want to use Google Play Store: Uninstall current fake store and Yalp. Re-run the NanoDroid Setup Wizard to only install Google Play Store (it will be the modified one) or manually alter your current setup file. Flash the NanoDroid microG submodule again. Download and install Yalp from F-Droid and also check if there're any updates via the Nanolx repo (should be most likely as I just updated this morning). Finally to reietrate: Forget about Fake Store.
[Magisk] starbright_:
Mh, I did so but for the google play store I need an account - they even want to have my phone number. That wasn't the idea behind using microG (for me). Is there no way around that?

In microG I see some "..." setting, next to Safety net (which is not activated for me).

"Allow connection to Google servers" is greyed out, can't be enabled.

I do now have PlayStore, but it seems I can't install Yalp now.