yashsingh1/xdaforums huggingface dataset:
[Moto G 2015 Android Development] :
I really thank U Mse for your response, rom is freaking great but i have big issue, i check this on 3 roms for now, Oreo AOSP, this rom ANd official Lineage microG - i use greenify and only on oryginal no microG LOS is working properly wakening all GCM apps - this optioon is always on on grennify so hibernate apps like Whatsapp could be awaken with incoming messages, but this is not working on those 3 roms, only on LOS with gapps, very strange, i dont know why those roms behave like this
[Moto G 2015 Android Development] MSe1969:
Why do you use Greenify at all? LineageOS has got the privacy guard, and in N, there is an AppOp to disallow background execution per app. So I wouldn't even bother with Greenify.

Further, there is the battery optimization feature in android. Apps, which are supposed to wake up, should not be "battery optimized".

I am no expert on Greenify, but to my knowledge, it hibernates apps when not in foreground and explicitly urges its users NOT to hibernate alarm clock and/or instant messaging apps! That is still today stated in the app info on play store.

So I am not aware of a functionality to wake up e.g. a hibernated WhatsApp... But I haven't used Greenify since years.

If such a feature exists, then I am sure it only works with " original" play services, as those always are beyond any rules of android (that's the way they are designed, and if the Greenify app would even attempt to restrict them, it would immediately be banned from at store - Google's store, Goggle's law ;) )
[Moto G 2015 Android Development] :
i use grennify to save battery?:) so u don t use any app like this? and whata about ram and battery life? i just wanna understand what is happening there on those roms why oreo with gapps why gappless roms, this is confusing for me - and i get used to it to use grennify always for better battery life and ram
[Moto G 2015 Android Development] MSe1969:
Don't get me wrong, Greenify is a great app for stock ROMs, but since you can - at least in LineageOS - restrict background execution via privacy guard, I personally don't see added value for it in LineageOS. However, if you like it, nothing wrong with it - but don't hibernate WA.

As you mentioned RAM: "RAM optimization" apps (I mean BS like "CleanMaster" and friends) are at best completely useless, in reality those apps just spy on you and tell you BS stories how they have cleaned your system. Ever heard of the term "Snake Oil"? :)
[Moto G 2015 Android Development] :
i agree with U 100% percent, my knowledge about how greenify works is small, but still on LOS14.1 works flawlessly whatsapp badoo even sms app wake up immediately when GCM push is incoming but this in not working on microG roms... im very curious;) why... and maybe like u sad i even delete grenify when is useless on Nougat
[Moto G 2015 Android Development] Carnage_mafia:
Greenify is useful only till marshmallow..
[Moto G 2015 Android Development] MSe1969:
Let me try to summarize:

1. Greenify "hibernates" apps not in foreground to prevent background execution.

2. That feature is implemented by default in a technically different way by LineageOS 14.1 via privacy guard, where you can simply block background execution per app, so in general, there is no need any more for Greenify.

3. Despite the clear recommendation given by Greenify NOT to hibernate messaging apps, there seems to be a Greenify feature to wake up hibernated apps based on push messages. Without a doubt a useful feature, however seems to only work with "original" play services. Can't comment and definitely can't "fix" that in microG.

4. So assuming your observation is correct, this indeed would be an argument to still use Greenify and also an argument to stick to the "real" Gapps... 5. However, it of course depends on your own priorities:

Google play services itself is a huge battery consumer (different from microG), so not sure whether hibernating WA and other apps receiving push messages compensates the battery drain caused by play services

6. Further, it depends on the importance for you of the reasons, why you want to get away from Google.

7.And finally, microG allows you to carefully choose, which apps can receive push messages (original Gapps not, this is then a voluntary setting in each app, if even available; but on app level, the app always receives the push in background and decides whether to shoot a notification or not) - whilst some apps really need push messages, it is "nice to have" or even annoying to receive them for others, personal taste of everybody. So simply disallow push for some apps (like newspaper apps) and restrict background for them might be more battery efficient eventually.

So depends on your preference, what you want - and on the apps you use, which are important to you...
[Moto G 2015 Android Development] :
Again thx man, i decide to open a thread on greenify and 1 response is: MicroG does not use standard GCM interfaces; likely need regular gapps.

So i think problem is solved, but still i dont kno why GCM push dont work on Oreo roms, but this is for differnet day and thread...

EDIT : So what is GCM setting in micorG settings? cuz i just enable it and my GCM apps like whatsapp r now waking up from greenify, so i discover a way :)

Conclusion: microG roms support GCM interface regardless :)

Thx everyone cheers
[Moto G 2015 Android Development] :
can U check guys if latest Tinder is working for u ?:) cuz on this and official microG LOS Tinder lateets stop working for me, thx
[Moto G 2015 Android Development] MSe1969:
I am not using Tinder at all (and I won't even install it for testing purposes).

As already mentioned, some apps require the original play services and won't work with microG.

This may have in fact two reasons, which often are correlated to each other:

microG does not attempt to fully replace all functions of the original play services, especially not the privacy-intrusive ones or the advertizing stuff. People, who are looking for a replacement of the original play services, use microG mostly because of improved privacy. So apps requiring such specific functions not covered by microG yet, won't fully work with microG - or even not at all.

Depending on how an app is coded, the app either works normally, until a non-supported function (e.g. in-app purchases) is called (and somebody using microG would not attempt to do that). "Privacy-intrusive" apps however, where the real intention of the originators is to collect data about their users, often put some additional efforts to refuse to work, if they can't be as nosy as intended.
[Moto G 2015 Android Development] MSe1969:
New builds with November ASB available

Hi all,

new builds are up with November 2018 ASB patches:

A. Regular LineageOS 14.1 with OMS and microG patch

https://www.androidfilehost.com/?fid=11410963190603843472

B. Hardened build with pre-installed microG (w/o OMS)

https://www.androidfilehost.com/?fid=11410963190603843470

C. Hardened microG-build with OMS patch

https://www.androidfilehost.com/?fid=11410963190603843471

Features for all 3 builds:

Security String 2018-11-05

V8 Java Script engine has been finally back-ported within LineageOS, this has been incorporated here as well

Regards, M.
[Moto G 2015 Android Development] positivetourettes:
guys anyone using different provider for geolocalization tham Mozzila and nominatim? Im asking cuz on my Osprey gps indorrs works fine but for a few seconds my localization is about 500m wrong - and now is GONE for good, sudennly localosation just disapeard, i even reinstal rom and checked all micorG option and now i don have localization so again go back to gapps omg
[Moto G 2015 Android Development] MSe1969:
Hi, assuming you are not faking the location to the app requesting the location through XprivacyLua etc., the following needs to be considered:

We need to clearly distinguish GPS (device) from coarse location (application).

Normally, if you set location to "device only", the GPS should find a fix, although this *may* take some minutes, especially if it needs to completely identify satellites from scratch. If that part does not work, even after a clean install, something is wrong with hardware.

The coarse location provider (e.g. Mozilla) submits the cell tower ids and the WiFi ssids, which it sees, to the Mozilla (or in case of Gapps to Google) server and the server returns, based on that, some coordinates. Coarse location can help the GPS chip to get a fix faster, as an approximate location requires less calculations and there is no need to wait for the complete so-called 'almanach' from the satellites. However, if for whatever reason coarse location delivers a significantly wrong location, this can have a bad influence to GPS fix process.

I personally use DejaVu and GPS location provider and have deactivated Mozilla, because I don't want to send my data to a server. I am however not aware of any issues with Mozilla, Mozilla normally works well out of the box.
[Moto G 2015 Android Development] positivetourettes:
This is why its strange, i flash your rom latest, out of the box sets up all setiings in microG, download maps and gps works in door in a seconds... and after reboot just stopped, on clean flash rom every settings enabled... so i did another flash rom, and another, and i never saw working in door gps like for the first time again - so this was a dream:) heheh, im not understanding what just happened with my phone and this very good rom - i go back to LOS 14.1 with gaps and gps working in doors like always so this is not hardware issue imo - PLS help cuz i wana use microG instead of gapps
[Moto G 2015 Android Development] matymador:
First off, thank you for this ROM. It's very stable and it's my daily driver. Tbh the fact that is degoogled is a plus.

The one issue I have is that GMaps is not working very well. The name of the streets don't show and it seems like it can't connect to the google servers, because it doesn't do any route calculation when I ask for directions.

Do you have any suggestions I could try to fix it?
[Moto G 2015 Android Development] MSe1969:
Hi, sorry for the late reply.

I have not been able to reproduce the issue described by you. SatStat shows also in "device only" mode a very fast and accurate GPS fix.

Have to admit however, that I did not find the time for a really comprehensive test (i.e. use e.g. OsmAnd~ app in the car to navigate to a destination).

Nevertheless, there haven't been any changes regarding location functionality in the last months - cm-14.1 anyhow is in "legacy mode", so besides security patches, there is no real development ongoing here. . . And my adaptations, which are described in the OP, also do not concern location functionality. So I don't know right now, how I can help you - is there any possibility that you could try to produce a log? Thanks, M.
[Moto G 2015 Android Development] MSe1969:
"GMaps" means 'Google Maps', right? As this is a Google product, I am not really sure to what extent GMaps would try to make use of the "original play services". I think it does not make sense trying to avoid Google on the one hand side for good reasons and on the other hand trying to use a certain Google product, whilst not knowing in detail, how it really interacts with Google.

Whilst I see the point that one doesn't want the original Google play services (with root access!!) spy on you and "phone home" all day, but still wanting to take advantage of the nice features, which Google offers: This is a contradiction, which you cannot solve in my opinion. 'microG' helps to use 3rd party apps with Google dependencies to work, but not apps built by Google themselves. I use e.g. Open Streetmaps instead of Google Maps (the app is called OsmAnd~ in F-Droid) - so that would be my recommendation.

In fact, part of Google's business model is

not

to let you "cherry-pick" - you get all their nice and useful stuff only in combination with their "spy services" on an Android device :)

Regards, M.
[Moto G 2015 Android Development] matymador:
Thank you for your response and I will look into OsmAnd.

As for the usage of Google Apps, I don't see the problem if you're not logged into them. Will Google match the IMEI or other identifying data from the phone to some Google Account? I wouldn't put it past them but in my case the trade off is justified. Google gets to know where I go and I get to know how to get there. I also created dummy google accounts to use with the phone, but I guess it wouldn't be so hard to match them with my real accounts.

Of course, none of that matters since I can't use the Google Apps with them not working correctly :p
[Moto G 2015 Android Development] MSe1969:
New builds with December ASB available

Hi all,

new builds are up with December 2018 ASB patches.

Besides, the fix for the 'adb root' bug, as explained here, is also included.

A. Regular LineageOS 14.1 with OMS and microG patch

https://www.androidfilehost.com/?fid=11410963190603869933

B. Hardened build with pre-installed microG (w/o OMS)

https://www.androidfilehost.com/?fid=11410963190603869935

C. Hardened microG-build with OMS patch

https://www.androidfilehost.com/?fid=11410963190603869934

Regards, M.
[Moto G 2015 Android Development] jemail:
I notice with this build that I am constantly seeing the following notification:

Updating Play support libraries

which then downloads the support libraries I guess.

This constant downloading killed my data allowance in the space of 3 days.

I have installed the Google Play Store from Shadow53's website.

Anyone any ideas?
[Moto G 2015 Android Development] MSe1969:
Hi jemail,

I have had a quick look to Shadow53's web site and would like to give a couple of items as feedback from my point of view:

The microG binaries/apps haven't changed compared to November; further, the applied patches from LineageOS cover areas, which I am pretty sure about, have nothing to do with your described issue (unless you tell me that going back to the last build solves your issue)

I know and I also successfully tested that about one and a half year back or so: In general, you can run the original play store on top of microG, but only in /system/priv-app - this is also explained on Shadow53's web site

However, there are some things you have to know - and I guess

that

is the issue you may be suffering from: The original play store has one very specific behavior. It

silently

self-updates, if a new version is available, and it silently updates the Google Play Services, if an update of Google's Spy services is available. The silent self-update of Google "core" apps is something, you cannot switch off in any settings, different from the feature to auto-update other apps. In case of microG, a specific version string is normally spoofed to apps asking for play services version to ensure a certain 'minimum' level is reported, so apps don't start complaining. But the original Google Play Store app of course always attempts to download the latest and gratest release of the Google spy services apk from Google's play store. So I guess it downloads the apk, but then fails to "update" (or even worse, if it would succeed. . .), repeats its attempt and so on. Google does not publish a new version of their spy services on a daily schedule, there may also be days or weeks between two versions. But when it tries to update the spy services, I am at least not surprised that this leads to "unexpected" results in conjunction with microG (especially when considering, that Google does not care at all when it comes to microG)

That is why I personally don't really recommend this approach. If you ask me, simply use Yalp (or Aurora, if you like it colorful) to download stuff from the play store. Folks wanting to access their purchased apps can continue doing so, if they use their original credentials with Yalp instead of the "default" logon. But you can't buy new stuff, obviously . . .

In short: I think this is an expected issue when using the "original" Play store app on top of microG, unfortunately. I don't know, whether the "patched" play store app mentioned on that site is any better in that regard . . .

Regards, M.
[Moto G 2015 Android Development] jemail:
Thanks for the informative response ?. As this is a recently observed behaviour I agree with you that Google is most likely the cause of the problem. I may try yalp or Aurora although for the moment I can firewall Google Play Store so it can only download stuff over Wi-Fi.

Once again many thanks for keeping this build up to date with security patches.

This is still the best ROM to use as a Dailly Driver.
[Moto G 2015 Android Development] Carnage_mafia:
Can I flash gapps on this rom?
[Moto G 2015 Android Development] MSe1969:
Yes, but only on the build variant A (see OP)
[Moto G 2015 Android Development] Carnage_mafia:
Gotcha.. Thanks.
[Moto G 2015 Android Development] hovnonium:
After months of usage of this rom..today I came late to the work because time on the phone was late about 47 minutes....same time is in the recovery

Odd thing is that i havent done anything with the phone (in settings, or recovery, or flashing anything)

Any guesses what went wrong?
[Moto G 2015 Android Development] MSe1969:
No idea, really...
[Moto G 2015 Android Development] jemail:
Are you still providing monthly security builds/updating LineageOS for the Moto G osprey?

I think you are the only dev building an up to date nougat ROM for osprey and falcon at the moment.

Many thanks for your good work on the osprey and falcon phones.
[Moto G 2015 Android Development] MSe1969:
Yes, I do. Most probably I'll upload tomorrow.
[Moto G 2015 Android Development] MSe1969:
New builds with January 2019 ASB patches available

Hi,

new builds with January 2019 ASB patches are available for download:

A. Regular LineageOS 14.1 with OMS and microG patch

https://www.androidfilehost.com/?fid=11410963190603903268

B. Hardened build with pre-installed microG (w/o OMS)

https://www.androidfilehost.com/?fid=11410963190603903267

C. Hardened microG-build with OMS patch

https://www.androidfilehost.com/?fid=11410963190603903266

Features of the new builds:

Security string 2019-01-05

System Webview updated to M71 (variant A.) / Privacy-enhanced Bromite SystemWebView M71 (variants B. and C.)

Additional 'spectre v1' mitigations in kernel

Update of Timezone data

No submission of IMSI/phone number to Google when GPS is in use (only applies to build variants B. and C.)

Package usage stats switched off by default (also see comment below - only applies to build variants B. and C.)

Package usage stats

Under Settings > Security > Apps with usage access, all installed apps are listed, which have the PACKAGE_USAGE_STATS permission.

Android's default behavior is to have them switched on for their tracking and the user can opt-out (if he/she is aware of this option).

The implemented change causes each installed app with the above permission to have the tracking disabled and the user explicitly needs to opt-in to allow the app to do the tracking. This is more privacy-friendly, as the user anyhow did not have any advantage of this (yes, I know: The app manufacturers "only want to improve the user experience" . . .)

Happy flashing!

M.
[Moto G 2015 Android Development] jemail:
Just flashed the latest build with no problems and everything is working well.

Would you consider making builds for the nvidia shield tablet? There are builds available for the nvidia shield tablet available on https://lineage.microg.org/ but they are not patched for oms and hardened like your builds. I think they provide a docker for those that would like to build there own microg LineageOS builds.

I would certainly test any nvidia shield tablet ROM you felt you could build.

Once again many thanks for your excellent work on providing up to date nougat ROMs for the community.
[Moto G 2015 Android Development] MSe1969:
Glad to read, that you are happy with the build.

Regarding Shield Tablet: As this is OT in this thread, I suggest continuing this topic via PM.

In general, making a build without having the device to at least see, whether it boots, is very difficult . . .
[Moto G 2015 Android Development] hovnonium:
Latest build is pretty good, but batery drains a little bit faster than on previous builds.
[Moto G 2015 Android Development] MSe1969:
February builds

Hi,

new builds with February 2019 ASB patches are available for download:

A. Regular LineageOS 14.1 with OMS and microG patch

https://www.androidfilehost.com/?fid=1395089523397887706

B. Hardened build with pre-installed microG (w/o OMS)

https://www.androidfilehost.com/?fid=1395089523397887690

C. Hardened microG-build with OMS patch

https://www.androidfilehost.com/?fid=1395089523397887691

Happy flashing!

M.
[Moto G 2015 Android Development] MSe1969:
Do you have the same impression also with the new Feb. build? If yes, is it possible to 'narrow down' your observation?
[Moto G 2015 Android Development] hovnonium:
It is better, but i think my battery is dying.
[Moto G 2015 Android Development] MSe1969:
As announced here, LineageOS has discontinued to deliver official 14.1 builds in the course of providing LineageOS 16.0 builds.

The 14.1 tree however will continue to be maintained for security patches by the community (I am one of these contibutors, btw).

So this build will normally continue.
[Moto G 2015 Android Development] ajaysingh23:
Thanks !
[Moto G 2015 Android Development] matymador:
Thanks for your work. It is appreciated.
[Moto G 2015 Android Development] MSe1969:
March builds

Hi,

new builds with March 2019 ASB patches are available for download:

A. Regular LineageOS 14.1 with OMS and microG patch

https://www.androidfilehost.com/?fid=1395089523397913596

B. Hardened build with pre-installed microG (w/o OMS)

https://www.androidfilehost.com/?fid=1395089523397913611

C. Hardened microG-build with OMS patch

https://www.androidfilehost.com/?fid=1395089523397913595

Features:

Security string 2019-03-05

SystemWebView updated (includes CVE-2019-5786): M72 (build variant A) / M73-Bromite (build variants B and C)

Various patches merged from Squid kernel

Happy flashing!

M.
[Moto G 2015 Android Development] MSe1969:
April builds

Hi,

new builds with April 2019 ASB patches are available for download:

A. Regular LineageOS 14.1 with OMS and microG patch

https://www.androidfilehost.com/?fid=1395089523397936736

B. Hardened build with pre-installed microG (w/o OMS)

https://www.androidfilehost.com/?fid=1395089523397936737

C. Hardened microG-build with OMS patch

https://www.androidfilehost.com/?fid=1395089523397936735

Regards, M.
[Moto G 2015 Android Development] MSe1969:
LineageOS 15.1

Hi all,

I am working on LineageOS 15.1 for the Osprey device - I have made a test build for the "hardened microG" variant, which is based on the Osprey device-dependent sources/blobs from here - The former and current Osprey maintainers for LineageOS own this github organization and as far as I can see, this is the device-dependent base waiting to become "official" for LineageOS 15.1.

I definitely will further provide at least another set of cm-14.1 builds as before for the May ASB (most probably also still for June), but I would like to switch to LineageOS 15.1 for the Osprey device eventually. Therefore, I would like to ask you for feedback on my LineageOS 15.1 test build, whether it runs smoothly and you would consider it ready to be a daily driver.

Important:

This build is signed, so for those of you willing to test, please make a backup of your current installation first and clean-flash.

(The brave of you may also want to try dirty-flashing and using the key migration script following the instructions here (Section "Dealing with signed builds") - make a backup first!)

Thanks in advance for any feedback.

M.