yashsingh1/xdaforums huggingface dataset:
[Android General] Oswald Boelcke:
Excellent and very glad to hear that it's working. Personally, I'm always happy when I recognise that somebody says fairwell and you won't see me back again to Google.:good:

As far as I know this "reboot" is required to more or less "create" dalvik/ART cache and cache; however, I might certainly be wrong. Additionally, since I believe Nanomod-patcher v14.x or so, Setialpha modified the patcher that it somehow creates the caches unless already available. I'm currently able to flash the patcher immediately after the microG module without issues, and I must flash the patcher also after a dirty update of RR.

Had the TB issue once, too. Used a different approach than you to positively solve it. Just completely uninstalled TB and the TB Pro key via SD Maid (incl. corpsefinder etc.), just maintained the backups on my external SD. Download TB from Google PS again, installed it, then downloaded and installed the Pro key. Working afterwards.

As you certainly know I'm intentionally not using Whatsapp and am therefore unable to support anyway (besides probably searching XDA and the web). Actually, I'm boycotting Whatsapp, Facebook & Co. from their very beginning and it was easy to build up my expression I even don't miss anything. There are better, open source, privacy concerned alternatives around; we just need to advertise them among our friends, companies etc. and to complain that official and governmental agencies, public media services paid by the community, politicians that usually pray the importance of strict privacy regulations in Germany and so on are using them. Worth to read and monitor for those with a German mother tongue: https://www.kuketz-blog.de/

As you correctly mentioned, all those applications requiring GCM pushes must be installed after the installation of microG; however, I noted that this is definitely not necessary after an upgrade of Nanomod i.e. when I simply flash a new release over the former one by TWRP. Afterwards, I certainly recheck all microG settings including those for GCM pushes.

Currently, I've a total of six applications in my portfolio but I granted only two (Nina, WarnWetter) the registration; for the other four I not only disabled the registration in the microG settings but also the corresponding services and broadcast receivers via MyAndroidToolsPro.

Last but not least, I recheck my Greenify settings regarding GCM pushes.
[Android General] ale5000:
Just for clarification, my installer use only original apk files.

There are reports that recently purchases with the original Google PS started working but I haven't tested it.
[Android General] Bracher:
Sorry for coming back, but I have a last question: I have read all posts in this forum and in the Nonomod forum and after carefully reading them I came to the conclusion that with Nanomod microG and Nanomod Patcher I'm no longer able to do a dirty flash of nightlies. That means I have to go for the whole procedure with every update - is this correct?

I don't complain, I'm happy with Nonomod and very thankful for all the help in this forum, everything works well but in consequence this means less updates because they trake a lot more energy and time, so I'll have to look for security patches and other important things in the changelogs in order to decide if I flash this nightly or better wait for the next one
[Android General] Oswald Boelcke:
I apologise I simply don't know. Since the very beginning when I got my i9305 I'm using RR that doesn't receive nightlies. No experiences with that at all. I suggest to ask in the microG/Nanomod threads if other guys using your ROM have experiences.
[Android General] Bracher:
Thanks a lot for your advice, I asked and was told as long as I installed Nanomod via Magisk no problem with dirty flashs of nightlies. In case somebody is interested: wipe Dalvik/cache, Cache and System, flash nightly, flash Magisk (flash xposed installer if not Magisk Module) reboot system - and everything worked well!!!
[Android General] Oswald Boelcke:
Thanks very much for this hint. Good to know for all who use nightlies.
[Android General] dawidd6:
Is google calendar and contacts sync working with microg?
[Android General] ale5000:
I use my "Google Sync Add-on" (it install the official Google sync apk to be used with microG) and they work perfectly without any effort but there are also completely open source alternatives.
[Android General] Oswald Boelcke:
Additionally to @ale5000's great advice, e.g. Nanomod also offers the capability with both, the "full" module and the microG-module. When and if running the Nanomod-setup-wizard, simply tick the respective box that you also want the sync adapters to be installed.
[Android General] maybeme2:
This thread is for the Samsung Galaxy.

My question:

Will this work for the LG Nexus 5?

Found the excellent tutorials

https://shadow53.com/android/no-gapps/setup-guide/1/
[Android General] Oswald Boelcke:
Obviously, I don't know the LG but I'm absolutely convinced that all mentioned here is working with LG.

And I certainly know shadow53's excellent guides and great website. I need to search this thread but I believe to remember I mentioned him quite often.
[Android General] ale5000:
I haven't tried every phone but I'm almost sure it works in any existing phone.
[Android General] stuckbootloader:
It should work on most devices out there; I own a Sony device myself.

I've installed and used microG just like in the first post before, and that worked; but I've recently made the switch to NanoMod, and it's amazing how easy it is to install. Give it a try, it should work just fine.
[Android General] Oswald Boelcke:
Absolutely true ...unless you've a stuck bootloader!;):D
[Android General] Bracher:
Sorrry for coming back but I have a serious problem since yesterday and perhaps somebody in this forum can help me: Nanomod worked well on all my devices (Samsung Note 3/hlte, Samsung Note 10.1/SM-P600), unfortunately I had to replace the last one. I replaced it with SM-P605 and for this device the official nightlies of LineageOS 14.1 are not able to detect my external SD-Card so I flashed the Unofficial LineageOS/CyanogenMod 14.1 for lt03lte (05.12.2017) by davidmueller13. But the Nanomodpatcher is not able to patch this ROM. I got the following remarks:

In red: 'Updater Process ended with ERROR: 1

Error installing zip file '/sdcard/MagiskManager/Nanomod-patcher - 14.8.20171130.zip'

As expected signature spoofing not ticked as well play service (GmsCore) and the play service (Phonesky) have not the correct signature.

ANY HELP WOULD BE VERY MUCH WELLCOMED!!!
[Android General] Oswald Boelcke:
I don't own any Samsung Note i.e. not familar with the available ROMs for these devices. Anyhow, the mentioned error makes me to assume that this unofficial LOS by davidmueller13 is odexed, and by my information the patcher only works with deodexed ROMs.

But I realised that you double-posted in the certainly better suited thread. That's good but please be aware double-posting isn't within the forum rules.
[Android General] Bracher:
Sorry, I'm a bit desolated in the moment, first I tried to flash TRWP 3.x.x.x and got a terrible bootloop took me a lot of time to come in download modus but I foolishly thought I made a mistake, so ones more original ROM and TRWP - bootloop finally I realised only 2.8.x.x is working and the unofficial TRWP 3.x.x.x that was all in all the whole evening. So and this morning (as my granddaughter is with her grandparents in China in the moment and I had time) I tried to go further with LineageOS Magisk and Nanomod, but yes I think you're right those unofficail ROMs from davidmueller (he has as well a Resurrection Remix developed) are deodexed. I have now tried with his Resurrection Remix but I could not even flash the Setup Wizzard of Nanomod, so probably it's the same.

Puh this is really bad as the official LineageOS is no alternative because this ROM is not able to deal with external SD-Cards. They don't show up for example in MiXplorer. So propably I have to forget this device and work with my old with the damaged screen....

THANK YOU VERY MUCH FOR THE REPLY!!!
[Android General] Oswald Boelcke:
Please find attached the dat-file of my personal backup of the disabled components of MyAndroidTools Pro. I had to zip the file as dat-files are not accepted for uploads.

To whom who's interested: Above quoted request is a reaction to my post here and quoted below:
[Android General] Oswald Boelcke:
I apologise that I'm replying slightly late. Just a few more ideas:

For signature spoofing, did you already try ale5000's Tingle or the Xposed framework with the FakeGApps module?

Instead of Nanomod, did you consider to e.g. use ale5000's microG unofficial installer?

Maybe Shadow53's tutorial is of any help: https://shadow53.com/android/downloads/microg/
[Android General] Oswald Boelcke:
New microG Services Core Available

A new microG Services Core version (0.2.4-111-gf1cdb48) is available. I usually download and install via F-droid; however, the download (https://microg.org/fdroid/repo/com.google.android.gms-12221403.apk) is also available on the microG Downlaod page.
[Android General] Bracher:
Hello,

I have a new question and hope you can help me ones more - the new microG playstore contains no longer the service "dailyhygieneservice" which had to be stopped in order to avoid self-updates of the playstore. Which service has replaced this or in other words which services should no be disabled?

Thanks a lot for every hint
[Android General] Oswald Boelcke:
That's affirmative. Actually, I doubt it's the new "µG-play store" but the one modified by Setialpha. I'm using the NanoDroid microG module i.e. I always get this modified store, respectively I update the store via terminal whenever Setialpha notifies about a new release. I think, also ale5000 is using that one in his microG unofficial installer. Shadow53 offers this modified store, too: https://shadow53.com/android/downloads/microg/

Anyhow, I didn't recognised that "dailyhygieneservice" was replaced by another one, I didn't change my setup of disabled service (except that "dailyhygieneservice" is simply not available anymore), and my Google Play Store hasn't tried once to auto-update. Don't know if this was useful to you?

EDIT (2018-11-01): @ale5000 is currently using the official unmodified version of Google Play Store; you find the content of his package here.Thanks to ale5000 for the update. Please refer to here for his original statement.
[Android General] Oswald Boelcke:
Just for completeness. Meanwhile a Samsung Galaxy S5 LTE+ (SM-G901F) has become my daily used device; however, if required I'm continuing to update this thread because I realised that there isn't any difference between the G901F and the i9305 in regard to GApps free. Even without having any knowledge about other devices, brands and types, I'm convinced this applies for most devices, certainly with some differences.

For these reasons, I decided to change the title of the thread and will most likely also request to move this thread into a different forum (maybe Android General under Android Development and Hacking).
[Android General] Oswald Boelcke:
It's quite a while that I started this thread, and meanwhile many things have changed but gratefully also improved with every step in development. The permanent readers of this thread know that about half way down the road, I started to use NanoDroid by Setialpha to flash/install microG, and even that changed its name. I'd like to update on my current settings of µG and its components; I assume the attached screenshots are self-explaining in this respect.

Still, the one and only NanoDroid module I use is the NanoDroid microG module (ok, if required I use the NanoDroid uninstall, patcher and installation wizard zips, too), and I always use NanoDroid as a Magisk module. For completeness, I attached my setup file. During a clean installation, I always flash the NanoDroid module through TWRP, but since the availability of Magisk v17.x I update my NanoDroid microG module via the Magisk Manager and haven't experienced any issues so far by this. Please be aware that a few people report some issue though when installing/flashing NanoDroid via Magisk Manager. And since the nanolx.org F-droid repo is available, all my updates of the microG GmsCore and the modified Google Play Store are conducted via F-droid. Just as a side remark: Just yesterday, I successfully made an in-app-purchase via Play Store i.e. I'm able to still confirm that Setialpha's modified Play Store is working in that respect.

My location backends are also updated via F-droid. Please be aware that the WiFi Location Service isn't actually anymore require if you use the fantastic Déjà Vu backend as @n76 also noted here. Some further information and screenshots, which I don't want to double-post here, are available in these two just 24 hours old posts: https://xdaforums.com/showpost.php?p=78013231&postcount=377 and https://xdaforums.com/showpost.php?p=78023597&postcount=4514

Please feel free to advice in case of any question.
[Android General] ale5000:
Currently it is the official unmodified version, you can see the content of the package here.
[Android General] Oswald Boelcke:
Thanks very much for the update. I really appreciate your support to maintain this thread as correct as possible. Original post amended!
[Android General] Bracher:
Dear Mr. Boelcke, can you help me one more time? Unfortunately I made a clean install of LOS on my Samsung Galaxy Note (lte03lte), now I'm no longer able to patch the ROM with the Nanodroid Patcher, it ends with 'failed to copy service.jar Updater process ended with ERROR: 1'. And as expected when checking with the Spoofing Checker, Spoofing is disabled. But this ROM is not odexed and my /system/framework.jar contains the file classes.dex, so the Patcher should work.

I'm a bit afraid the last two versions of my ROM have problems but the older versions have been deleted after the LineageOS team decided to no longer maitain lte03lte. I thought of sending my logs to Setialpha, perhaps he can help, but what exactly does he need, probably not a bugreport? Further I have a Nanodroid-Sys Test.log, logs of microG, FDroid and BomiteWebView but nothing on patcher have I to flash the whole Nanodroid package and enable Nanodroid_init? Or how else can I create a log? I saw you have installed MatLog but does this app catch logs when you're flashing in Recovery? and if has it to be installed before trying to flash the patcher? It's a busy time so take your time but if you could give me a hint in for example two weeks time this would ne great.

I wish a appy new year to everybody!!!

---------- Post added at 01:52 PM ---------- Previous post was at 01:42 PM ----------

I have as well a log created by my MiXPlorer MiX-Log
[Android General] Oswald Boelcke:
@Bracher: Which LOS version excatly? And no a logcat wouldn't help but certainly the TWRP recovery.log supported by screenshot(s). Are you using Xposed? If this is the case, you could try this Xposed module: "FakeGApps". But in any case, best is to ask Setialpha. And check this page - partially quoted:
[Android General] Bracher:
Thank you very much! As I have XPosed already installed for XPrivacyLua it was the easiest way to use FakeGApps, it worked very well even on my odexed ROM (I tested this with a new installation of the inofficial LOS which will kept updated by DavidMueller - the official unfortunately no longer). But the result is a bit strange: for example I have the full Playstore but asked in my configuration file for Aurora- and Fakestore "nanodroid_play=31", ...but the Playstore works very well despite my ROM having no signature spoofing - so I'll better ask Setialpha
[Android General] Oswald Boelcke:
First, I like to wish you all the best for 2019, especially health that is the most important thing. Currently out of thanks otherwise I'd shown my appreciation in that way.

Glad that signature spoofing worked out, and I'm convinced you're going to find solutions for your other issues in conjunction with Setialpha... Yeah, Xposed is extremely powerful, and gratefully the arguments, which prevent others from using it, don't apply to me and obviously not to you.

I'm only a very little bit confused as you said here above that your ROM wasn't odexed...
[Android General] Bracher:
Dear Mr. Boelcke I wish you as well a happy new year!

As for your question: realising that the last two versions of the official LOS had problems with the patcher, I decided to go for the inofficial LOS 14.1 which will be further updated by DavidMueller (many thanks!!!) this inofficial LOS is unfortunately odexed - the official LOS 14.1 wasn't odexed but will no longer be maintained.

I was hesitating to aks Setialpha for help as long as I had not tested the possibility with XPosed and FakeGApps so I went for this and was successfull everything works well and after I found out where to give microG Services Core the allowance for signature spoofing all boxes in microG settings are ticked (without having flashed the patcher). I suppose Google Play Store needs this allowance as well
[Android General] Oswald Boelcke:
Thanks very much for the wishes - and the explanation regarding the ROMs. All makes sense now.;)

And affirmative, Google PS also requires the permission (please refer to attached screenshot).
[Android General] Oswald Boelcke:
I well know that the modification I describe already occurred quite a while ago, and those who a interested in and familiar with NanoDroid know. However, I wanted to also mention it in this thread just for completeness.

NanoDroid now updates the following unofficial snapshot builds (that are partially modified by Setialpha) via its own F-Droid repo (https://nanolx.org/fdroid/repo/):

microG GmsCore

microG DroidGuard Helper

Google Play Store

MPV

OmniJAWS

OpenLauncher

In regard to Bromite SystemWebView, the URL to the F-Droid repo changed a few weeks ago to https://www.bromite.org/fdroid. Please be aware that at least that the version I require for my device's architecture is not always available on the F-Droid repo. However, I noted that as soon as (a) incompatible version(s) is/are indicated, the version for our devices is also available on the Bromite SystemWebView Releases page.
[Android General] Oswald Boelcke:
Post #84 updated!

Yesterday, I realised that I've forgotten to update this thread with the information that the Bromite WebView can easily be installed via a NanoDroid Bromite WebView sub-module since 2018-11-09 (NanoDroid v20.0 beta). For the release notifications of this version refer to here. Brief quotation from them:

Personal experiences: Simply excellent; works well and without any issues. And just to reiterate: The submodule only contains the WebView but not the browser. The submodule zip-file is flashed through TWRP, and when flashing the submodule the usually ROM-inherent Android WebView is automatically replaced by the Bromite WebView.
[Android General] mrhamed:
Hello, thank's to all people for trying to improve the privacy safety...

I'm on PIE with Elder-exposed (oneplus one) alse the Rom is: POSP v2.2 - bacon [OFFICIAL][WEEKLIES]

But after 2days. I couldn't pass the "System support location provider" check :crying:

I used the xposed's module XposedGmsCoreUnifiedNlp and UnifiedNlp.v1.6.8 but niether didn't work :crying:

Can you help me please?
[Android General] Oswald Boelcke:
For multiple reasons, I've decided to stay on Nougat (had just a very short journey to Oreo with the SM-G901F but reverted quickly).

This means no experiences with or knowledge about Pie; same applies to EdXposed. Thanks to Nougat, the official, stable and obviously no further developed Xposed is still available and usable to me. However, from my readings in other fora (e.g. XPrivacyLua) I remember posts that EdXposed isn't without bugs yet.

TL;DR: Negative, I apologise. Unable to assist.

Last but not least: For a few days already I'm playing with the idea to remove µG and to flash GApps again. I'm interested and to test if I've the capability and possibility to protect my privacy to my personal needs even on a device with GApps. Actually, I doubt but last time I'd a look XPrivacyLua wasn't available yet.
[Android General] mrhamed:
In my opinion, we should move forward in open-source world. so move to Pie and Elderxposed and ...

By my experience the xprivaxy or xprivacyLua can't safe our privacy alone and the google process(es) can access our privacy & drain the battery.

So we have to support the MicroG (like) project(s) with our feedback an contribute to stop spying our privacy.
[Android General] Portgas D. Ace:
The thing is: there will never be a completely tracking- and data collecting-free environment without an "open source" hardware. I have no doubt that any smart device has such hardware-related ways to track and collect data, no matter what software is involved. But yeah, basically, an open source operation system and an open source implementation like microG are essential components to maximize your own privacy, at least on the software side.

Unfortunately, microG seems not to work properly on Android Pie, tested it on various ROMs on one of my testing devices. I hope that this will change in the near future.
[Android General] Oswald Boelcke:
Thus far, I'd frozen CaptivePortalLogin and denied internet access by firewall to avoid "pings" to Google server. As of today, I'm using CaptivePortalLogin again i.e. unfrozen and internet access granted. For details refer to here.
[Android General] Oswald Boelcke:
The next reason to go GApps-free:

The Verge on 2019-05-14 "Google is about to have a lot more ads on phones"
[Android General] Oswald Boelcke:
Just thought it's time to bump myself.
[Android General] Oswald Boelcke:
Too many threads have been created on moderator's duty, so bumping this one to bring it up in my own profile stats.
[Android General] Oswald Boelcke:
Meanwhile, I always use Nanodroid as installer and to patch the ROM. Details at other locations in this thread.