yashsingh1/xdaforums huggingface dataset:
[Magisk] dhacke:
No. It's a complete replacement as in the past.
[Magisk] garylawwd:
I just use an older version of flightradar as I need this app. I work on aircraft so need to know what times they are arriving/departing.

The version I currently use is 7.5.0 which you can get on apkmirror. Still has its bugs but it works not too bad
[Magisk] marcdw:
Howdy,

Anyone have any ideas on what probably happened here at https://xdaforums.com/showthread.php?p=79665153

More curious than anything else.

ZTE Axon 7 A2017U, AospExtended v4.6 ROM, Radioactive v2.4 Kernel, microG (NoGapps), Multiboot, XDA Legacy
[Magisk] 73sydney:
The single reason i gave up on MicroG was that the maps/navigation never work on the apps i need it to....

As much as it sounds like fun to go "google free", the reality is you have to give up too much functionailty.

Its not worth it to feel like youre somehow beating google, because youre not, youre making your life harder...
[Magisk] Oswald Boelcke:
Negative, you don't. But you have to walk the whole way and probably look for alternatives to Google-contaminated applications.

I'm convinced we can win...:good::)
[Magisk] Setialpha:
Fixed in development version.
[Magisk] Setialpha:
That's your point of view. I'm using OSM and I'm happy. The only remaining non-AOSP Google app I'm using is Play Store and I don't miss anything.

If that's not how it turned out for you, that's OK, but don't tell me, that I'm making my life hard, when I don't lol.
[Magisk] guest4711:
Never had a device with google services on it, so I don't miss them (or any apps requiring it). And most apps telling me they need GMS are running fine even without.

So I don't know why it should be worth to invite ABC corp. into my phone...
[Magisk] Valdrio:
And that's why monopoly and conflict of interest are bad. And that's why it is important to stay away from such situation such as Google, Facebook, Apple, Microsoft and Amazon.

Unfortunately too much apps require gms and Google is trying to make ever more mandatory. Sad.

---------- Post added at 07:35 PM ---------- Previous post was at 07:33 PM ----------

Probably, but only good politics can solve definitely this situation, we can do only so much about it.
[Magisk] Setialpha:
I've updated and improved the #Issues section of the documentation. Most known issues and their fixes can be found there (as always): https://gitlab.com/Nanolx/NanoDroid#issues

Be sure to check it, before posting here, your issue may already be listed. ;)
[Magisk] Setialpha:
The next release will drop 1 application, switch 1 from alpha to stable channel, replace 3 applications.

See: https://gitlab.com/Nanolx/NanoDroid/blob/master/ChangeLog.md for more infos.

Feel free to grab your pitch forks. ;)

Ah, and the SysTest will be executable from Magisk Manager aswell, along with SetupWizard and Uninstaller fixes.

Now, that magisk.img is dead, I'll be testing support flashing through Magisk Manager again. Let's see.
[Magisk] Setialpha:
Yes, NanoDroid now behaves like all other Magisk modules on frsh Magisk installation: first flash Magisk, then boot into ROM once, afterwards flash NanoDroid.

Previous NanoDroid versions had custom code to get around tgat restriction, but that could cause other issues, so it was dropped.
[Magisk] DrUnknownEMC:
You can't assume it making our life harder. You can only say it making your own life harder.

If you really need address's number search try magic earth. If not osm is a good option.

It was kinda fun setting up my own nextcloud which essentially break a need for Google sync options.
[Magisk] gardiol:
Two are the things I find hard to do without Google:

1. Voice dictation. I use it a lot, in the car, and it would be too dangerous to type and too time consuming each time to stop and text

2. Commercial directory and opening times on Google maps, unreplaceable and critical to me. Searching on the web is pointless, since I need to find out places which are near to me in places I don't know well.

For everything else I already use next cloud and davdroid and such... The day the two point will be replaceable, I will fully switch. For now, I keep looking here and try once in a while to check how it's going

It's a great work and very important. Keep it up!
[Magisk] d1n0x:
1. Wait until you can safely text outside of your car. Nothing can be that important that you need to immediately respond.

2. Contribute to OSM by adding opening times to businesses. You can take gmaps as an example and just copy the times.
[Magisk] gardiol:
This is what I think it's a very stupid reply. sorry if I say so but your option is not an option at all for me and you are quite obnoxious to suggest it.

It's clear that I would wait until I stop my car to text. But the point is Google give me an amazing option which is quite useful when you drive hours per day and you have to reply to text for work.

As for your second reply, I agree with you and I would happily do it but still I need access to Google Maps to do such thing on the move.... Or better I will start to doing it today I never thought of it... I thought that kind of metadata could not be added to openstreetmap in a reliable manner due to the way openstreetmap databese is organised .

anyway for voice dictation it seems that at least one option is opening up a believe it will still require a long time before it's viable. It has been posted here a few days ago I checked and it's still not usable but I'm confident we get there in the long run.
[Magisk] temporarium:
This is a very civil reply, [MENTION=3705972]gardiol[/MENTION].

To everyone else: please respect others' opinions, folks. Suggestions should be practical, not critical.
[Magisk] Oswald Boelcke:
StreetComplete is an easily to handle tool to support improvement of OpenStreetMaps: https://f-droid.org/en/packages/de.westnordost.streetcomplete/
[Magisk] githyanki:
I installed the Google app for voice dictation. Set it up as only voice input, not as assistant. Best I could do without better alternative.

As for gmaps, you can access it through a web interface. Look up all the info you need there and use omsand for the navigation.
[Magisk] gardiol:
Thank you, next time I need to reflash my ROM I will try!
[Magisk] DrUnknownEMC:
1. True, I usually just call or the person will know call if it urgent information. They will learn eventually calling is probs quickest method to get reply lmao.

2. Yeah kinda missing searching for new restaurants. Now is mostly based off suggestion from others or usual places. I usually call ahead now as I got played by opening hours for some smaller business.
[Magisk] TeLow:
Hi SetiAlpha,

find attached the recovery.log and dmesg.log, i hope those are the right ones and help. Do i have to flash Magisk before or after the Nanodroid packages?

//edit: So after flashing the lates omnirom for op6t OTA the first time it would not boot but would reboot to bootloader. I then reflashed everything a second time (omni, twrp, microg, bromite, fdroid and magisk) it woudl boot into system but the Nanodroid packages weren't fully installed (fdroid missing, microG settings were there but GSM Core was missing according to the settings.

I then rebooted a third time into TWRP and flashed everything besides the omnirom itself, then rebooted into system and did the npem and nutl -r command as su, that worked. All Apps stayed registered and push services are working.

Cheers
[Magisk] Bracher:
Sorry for coming back to my old problem, but unfortunately it got worse:

My mobile is a Samsung Note 3 (hlte) it's an old Mobil but it works still fine. I got in trouble after Nanodroid microG 20.7.92.20190424. I can't use the setup Whizard - get bootloops but my .nanodroid-setup file does not work with all new versions after 20.7.92. I had no chance to install the Play store, only Aurora and Fake Store have been installed (and I have for the installation of stores 'nanodroid_play=100' and the file is stored in data, data/media/0 and on the external sd-card).

OK I gave up and used until now the old version of Nanodroid, but with a clean update of my ROM (RR-P-v7.0.2-20190605-hlte-Official) and Magisk 19.3 the playstore of Nanodroid microG 20.7.92 does not work anymore. So I'm afraid I'll have to go for the new version of Nanodroid MicroG. But I have no idea what I'm doing wrong.

So what should I deliver so that somebody could perhaps identify my problem. As I have fortunately two Note 3 - one not updated until now and still working fine I can wait a bit before I make a new effort to get on with the installation of the new ROM.
[Magisk] Valdrio:
Is Google the only solution for voice dictation? No alternative apps?
[Magisk] clewis.it:
Not that I know of. However you can minimize google usage by downloading the offline voice files, a and using another assistant app like Saiy.
[Magisk] marcdw:
Heh, no pitchforks here. I really like OmniClock but Alarmio is just as cool. Lightning hasn't been updated in two years so removing it makes sense. Never could warm up to BeHeKeyboard.

Gotta do whatcha gotta do.

LG G3 D851, Candy7 v6.0 ROM, Google free - no microG, MultiROM, XDA Legacy
[Magisk] the_Pan:
:svetius: I agree, it's really cool!

The only thing I miss so far, are those selfchanging backgrounds from omniclock.
[Magisk] Bracher:
I tried ones more to get the Play-Store installed - without success, still Aurora and Fake Store

Now I have attached my logfiles as well as the nanodroid-setup.text which was stored on the external SD-Card as well as in 'data' and 'data/media/0'

The log files says 'nanodroid_play=31' whereas I have in my setup file (nanodroid-setup.text) 'nanodroid_play=10'. I have no idea why the Nanodroid-microG package is not able to work with my setup-file. I will now install Nanodroid Systest and provide that log as well
[Magisk] Bracher:
This is the log file of the systest
[Magisk] githyanki:
I liked the look of alarmio too, until this morning. The snooze timer on the alarm updates with a countdown. It seems pie ROM's treat updates to the notification differently and there's a chime for each update. At least on my ROM this happens. Very annoying. Couldn't find a way in the settings to turn that off.
[Magisk] Kjivar:
Hi, I'm having trouble with GPS.

Running CARBON-CR-7.0-OPAL-WEEKLY-dumpling-20190605-0232.zip, 9.0.5 firmware, Magisk 19.2 andNanoDroid.

Turning on GPS and opening SatStat or Osmand to check position. Can't get a fix on position (tried both

gps only and high accuracy).

Any advice or solution for this problem?

Can't really find anything in this tread other than perhaps installing xposed.

Could have a another go with Omni, but I can't verify that unified nlp works. Dev says it does, but Idk how to test. GPS on Omni is either on or off. No other toggle as I recall.
[Magisk] d1n0x:
GPS has nothing to do with MicroG. It must be your network location backends that aren't properly configured
[Magisk] Kjivar:
Thought it might be ROM related actually. Carbon has had some known issues concerning unified nlp. My set up has worked on Omni. Forgot the log, but posting it now. Maybe this can pin point what's wrong.
[Magisk] d1n0x:
Negative, I use carbon ROM and UnifiedNLP works fine (although I do use a standalone version since I don't use MicroG, but that shouldn't make a difference)
[Magisk] Kjivar:
Sooo, now it works. Not sure why it didn't in the first place.

Went through the Nominatim set up again: went back to OSM API server, rebooted and them back to Mapquest API. Location worked with both.

Also had a looksy on my VPN. Now location in battery saving mode also works. Which confirms, in my understanding, that the unified nlp works yes?
[Magisk] guest4711:
Yes. To make very sure have a look onto selftest in unified nlp (or in pie+ in location settings: unlp should be listed as provider).
[Magisk] ParanoidVisitor:
Hi guys, i still have the problem with installing NanoDroid over Magisk 19.2, it says that Magisk version 15.0 or newer is required.

Here, i'm posting logs....

https://www.mediafire.com/file/271i....0.20190601_log_19700101_03.26.37[2].log/file

https://www.mediafire.com/file/18qg...0.20190601_twrp_19700101_03.26.37[1].log/file
[Magisk] :
Just reboot. Nanodroid has been updated to function as a magisk module, and therefor you must reboot between flashing magisk, and nanodroid
[Magisk] castrum_doloris:
As you're allready replacing apps; Maybe I have a further suggestion for an app replacement ^_^ (if you didn't already consider this):

Smart Pack Kernel Manager instead of Kernel Adiutor.

I experienced it as a very nice fork of Adiutor.

https://xdaforums.com/android/apps-games/app-smartpack-kernel-manager-t3854717

https://github.com/SmartPack/SmartPack-Kernel-Manager
[Magisk] aCIDsLAM:
I had this problem too. As a workarround i installed nanodroid to system, even if i am using magisk. Then the settings stayed after a reboot.
[Magisk] PoochyX:
These Android systems truly be puzzled what works for one end user won't work for the next cause all of are configurations are different
[Magisk] castrum_doloris:
Which version of EdXposed do you have installed? beta/alpha, SandHook/YAHFA?

Try to switch between them (YAHFA is more stable)

Which Modules for EdXposed do you have installed?

What happens If you remove EdXposed completely? Are the nanodroid/µG settings staying?

It seems like a very strange interaction/bug for me
[Magisk] PoochyX:
YAHFA is the preferable Sandhook?
[Magisk] razr96:
I recently got the same problem and fixed it by also installing microg as a user. This with EdXposed on AospExtended.
[Magisk] castrum_doloris:
Sorry, I'm not sure if I get your question right ^_^

But in general, YAHFA is an older and more tested, and so more stable hooking method.

Sandhook is newer, not very stable and tested yet, but should be faster than YAHF. (Whatever 'faster' means in this context. I didn't experience any differences)

So if you're using Sandhook and are running into problems, it's worth a try switching to YAHFA. (Vice versa also recommended)

What you prefer in the end, is your choice. I'm going with YAHFA (0.4.1.2 beta) and I'm happy
[Magisk] farfromrefuge:
I am facing a crash with the play store. It keeps on crashing.

So here is what i have done:

- install los

- run nanodroid patcher

-install modified play store from nanodroidx f-droid repo

Now it keeps on crashing.

In the logcat i see this

:

06-13 17:29:05.390 31522 31522 E AndroidRuntime: Process: com.android.vending, PID: 31522
06-13 17:29:05.390 31522 31522 E AndroidRuntime: java.lang.SecurityException: You either need MANAGE_USERS or CREATE_USERS permission to: query users
06-13 17:29:05.390 31522 31522 E AndroidRuntime:	at android.os.Parcel.createException(Parcel.java:1950)
06-13 17:29:05.390 31522 31522 E AndroidRuntime:	at android.os.Parcel.readException(Parcel.java:1918)
06-13 17:29:05.390 31522 31522 E AndroidRuntime:	at android.os.Parcel.readException(Parcel.java:1868)
06-13 17:29:05.390 31522 31522 E AndroidRuntime:	at android.os.IUserManager$Stub$Proxy.getUsers(IUserManager.java:1092)
06-13 17:29:05.390 31522 31522 E AndroidRuntime:	at android.os.UserManager.getSerialNumbersOfUsers(UserManager.java:2183)
06-13 17:29:05.390 31522 31522 E AndroidRuntime:	at uja.c(SourceFile:12)
06-13 17:29:05.390 31522 31522 E AndroidRuntime:	at uiz.d(Unknown Source:2)
06-13 17:29:05.390 31522 31522 E AndroidRuntime:	at kjq.a(SourceFile:159)
06-13 17:29:05.390 31522 31522 E AndroidRuntime:	at kkk.a(SourceFile:11)
06-13 17:29:05.390 31522 31522 E AndroidRuntime:	at afvo.run(SourceFile:2)
06-13 17:29:05.390 31522 31522 E AndroidRuntime:	at android.os.Handler.handleCallback(Handler.java:873)
06-13 17:29:05.390 31522 31522 E AndroidRuntime:	at android.os.Handler.dispatchMessage(Handler.java:99)
06-13 17:29:05.390 31522 31522 E AndroidRuntime:	at android.os.Looper.loop(Looper.java:193)
06-13 17:29:05.390 31522 31522 E AndroidRuntime:	at android.app.ActivityThread.main(ActivityThread.java:6718)
06-13 17:29:05.390 31522 31522 E AndroidRuntime:	at java.lang.reflect.Method.invoke(Native Method)
06-13 17:29:05.390 31522 31522 E AndroidRuntime:	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493)
06-13 17:29:05.390 31522 31522 E AndroidRuntime:	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:858)
06-13 17:29:05.407 3130 3166 I ActivityManager: Showing crash dialog for package com.android.vending u0

I already faced that issue once and fixed it but i cant remember how. I think i fixed by running nanodroid-perm. But i can't find how to install it again on my phone.

Any help would be appreciated
[Magisk] Setialpha:
No, you need to install patched Play Store as System app.
[Magisk] farfromrefuge:
And how can i do that after installing from f-droid? Not sure why it was working before. I was also updating it through f-droid
[Magisk] Setialpha:
Updates don't matter, the initial installation does.

Well, since Play Store needs privapp permission whitelist, only a ibstaller like NanoDroid will help in this regard. Ther are other ways to systemize apps, but since they are not meant for priviledged apps and don't create their whitelists, you nay get stuck in a boot loop.
[Magisk] TeLow:
[MENTION=4187311]Setialpha[/MENTION] did you have the time to look at my logs? i hope they are the right ones now.
[Magisk] DoR3M3:
[MENTION=4187311]Setialpha[/MENTION] in the latest NanoDroid-microG-21.0.20190601, what happened to the /etc/permissions, I no longer see anything for 'com.android.vending.xml', and 'privapp-permissions-google.xml'?

No more <permission name="android.permission.FAKE_PACKAGE_SIGNATURE" />?

hmm
[Magisk] Setialpha:
Not yet.

Auto generated during installation.
[Magisk] Tisckkytt:
It's sed for me that Playstore has been removed from the microG package, now I need to download the whole nanodroid 300+ mb package just to get the Playstore.

I know I can manually set up the Playstore from the repo but it's just too much effort compared to what it used to be just flashing the microG package & no need to worry about anything else.

If it's possible to add back the Playstore as an option in the microG package, maybe an aroma selection menu while installing would be really appreciated. Thanks. :)
[Magisk] daywalk3r666:
flash the setupwizard and select playstore instead of aurora store.than flash the microg package
[Magisk] Oswald Boelcke:
Exactly this is available in the setup-wizard.
[Magisk] Tisckkytt:
Does setup wizard work that way? I thought it's for the full Nanodroid package only.
[Magisk] daywalk3r666:
yes it works.
[Magisk] TevW:
No, the setup wizard just generates a file used by the main Nanodroid package to install what you chose to in the setup wizard.
[Magisk] Oswald Boelcke:
Not totally correct. The generated setup-file is also used if only the µG sub-module is flashed.
[Magisk] farfromrefuge:
Ok so i tried :

- uninstalling the playstore

- running the setup wizard to choose play store

- install Nanodroid MicroG (21.0)

- restart

Now the issue is that i can't update the Playstore Through your F-droid repo. It tells me that the apk signature have changed (from the included 15.1.24 to the repo 15.3.17)

Is that normal. Shouldn't they have the same signature?
[Magisk] Setialpha:
Did you enable signature spoofing for Play Store and reboot afterwards?
[Magisk] farfromrefuge:
Oh it needs signature spoofing to update itself through f-droid? It might be it.

I had an issue with the patcher putting in boot loop so i was trying without having the patcher applied. So signature spoofing might not have been working.

I am trying to go around the bootloop right now, i think it has to do with incompatible los/patcher versions
[Magisk] farfromrefuge:
Tried everything you said. Now here is my working setup (except for Playstore update):

- Los 16 build from May (build from June bootloop with NanoDroid, did you know?) with MicroG

- NanoDroid 20.8.91

- PLay Store 15.0.13

- Everything is checked in MicroG setup

- Playstore has Signature Spoofing permission and is working.

Now if i go in F-droid and try to update the Play Store using your repo it tells me "the new version is signer with a different key to the old one ..."

Actually have the same issue with all microG apps.

Any idea?
[Magisk] Tisckkytt:
Thanks. I just checked & yes Phonesky app is there in the microG package, so the setup wizard should install that if chosen to.

I had this misconception that setup wizard is only for the full package, that's why never tried with the microG package.
[Magisk] Setialpha:
You rebooted after granting signature spoofing permission?
[Magisk] farfromrefuge:
Yes i did multiple times. BTW i dont think F-droid is a system app and i use the privilege extension. If that can help...
[Magisk] garylawwd:
I had the same issue and it was because fdroid didnt have 'install from unknown source' permission.

What I did is disable privelaged extension and manually installed the update and that will give you the permission prompt.

Once unknown sources is enabled it installs apps with privelaged extension
[Magisk] farfromrefuge:
Sadly not my issue, F-droid already have that permission :s
[Magisk] Oswald Boelcke:
The way it is written, I assume you're using "LineageOS for microG" and you used the "full" NanoDroid package to get the additional applications/add-ons.

Which PlayStore are you using, and from where did you get it? The one modified by Setalphia? Unless you use that you won't be able to update it via F-Droid as it's differently signed.
[Magisk] farfromrefuge:
Indeed i use a custom build made for my phone (a3 2017) with microg in. After that i use the Nanodroid MicroG to install MicroG + Playstore (setup through the setup wizard)

So the Playstore is supposed to be signed by Setalphia
[Magisk] Oswald Boelcke:
Affirmative, it is... (or should be). Did you already give shadow53's standalone Play Store a try? The patched version is Setalphia's.
[Magisk] farfromrefuge:
Thanks it worked! What i did was :

- install "MicroG as System App Patched": was able to update the play store through F-droid but could not update MicroG

- installed the "unofficial verison" : could update microG!

So now all is good. But to me it says that the signatures from 20.x are not the same as the one from F-droid?

Thanks
[Magisk] Setialpha:
20.8.91 is a beta release you should use 21.0 instead, it should fix the bootloop issue with June ROM.
[Magisk] Bogdans29:
Enyone have link of magisk module?
[Magisk] garylawwd:
The download is the magisk module also.

It needs to be flashed in recovery but it installs as a magisk module if magisk is detected
[Magisk] Bogdans29:
Well i was do just that but magisk dont show like its magisk module in apk-modules...
[Magisk] PoochyX:
Magisk repo just downloaded the apk for you with some audio effects you install the apk it transfered to your storage in the viper folder and when it's installed it will install the driver and the app Willl detect your a magisk user and install the viper driver as a magisk module alot of convolers don't work as system apps so they went about the installation like this

([emoji3590]9/[emoji725]/9[emoji3590])
[Magisk] garylawwd:
What are you talking about? Wrong place I think?

We are talking about nanodroid not viper
[Magisk] PoochyX:
That conment was for another op my bad [emoji24][emoji24][emoji24][emoji24]

([emoji3590]9/[emoji725]/9[emoji3590])