yashsingh1/xdaforums huggingface dataset:
[Moto G 2015 Android Development] maxwell80:
With the block script on it's not possible to download received videos in Whatsapp so maybe you could think about adding another exception as well...?

Regarding the included adblocker - could it make sense to have the option to turn it off? I don't know how a mobile ab works, but I know they can cause trouble on PCs.

I checked again:

PNT notifications arrive in time, both normal and high priority.

Whatsapp seems to work too, after I turned battery optimization off.

Signal messages are always delayed (~2 - 20 minutes) when device is in doze and always in time when awake.
[Moto G 2015 Android Development] MSe1969:
No.

Whilst I see your point, this is technically not possible. WA is Facebook and FB is a large pool of IP addresses which are dynamically assigned, redirected and balanced, so you block FB as a whole or you haven't blocked it at all (same with Google).

EDIT: I think I may have misunderstood you. It would be possible to allow only the WA app to connect to FB. Need to think about that...

The AB is a pre-delivered, frequently updated hosts file, which translates known ad hosts into 127.0.0.1 (IPv4) and ::1 (IPv6). You can set an option in the Dev. Options to keep/restore the hosts file on your device and ignore the updates and then use a hosts file root app or simply replace the hosts file with a dummy file.

Thanks for the confirmation; odd, that it's doing this weird stuff on my device, even after a factory reset...
[Moto G 2015 Android Development] MSe1969:
Push notifications - update

Thanks again for your feedback, yes, I can confirm that push notifications as such work perfectly well!

The issue with my phone was very specific:

- I didn't realize, that I had some days back connected my Osprey phone to the Guest WiFi and not the regular WiFi

- The guest WiFi however has a netfilter active to only allow http / https (and as such no other tcp port, which means also no GCM)

- Therefore, push messages did not work at all

- At night, the WiFi is automatically switched off, and via the mobile data connection, the push messages finally arrived - that explains the weird delay of several hours

I am glad, that there is no issue with the ROM (only my own "special" WiFi setup). :)
[Moto G 2015 Android Development] phool4XC:
Thank you!
[Moto G 2015 Android Development] Jackones:
Hey Folks,

I have a weird problem with this ROM (and other LOS-Versions, too).

The phone won't connect to cellular data with the standard-mode (GSM, WCMDA, LTE).

Workaround, for temporary functioning data:

1. Check GSM-only -> Connect to EDGE

2. Switch to LTE-only -> Connect to LTE

But when I restart the phone or toggle flight-mode, it won't connect again.

There are plenty of options, which connection-type should be preferred.

On another ROM (PixysOS 2.1) there are 3 options only (2G, 3G, LTE) and connection is rock solid.

Does anyone know a way for solid configuration?
[Moto G 2015 Android Development] XCore64:
I'm having this issue as well. However, I have no luck, especially with the stock OS (5.1.1 & 6.0). Even switching any options don't get a signal.

What carrier are you using? I'm using TextNow (under T-Mobile)
[Moto G 2015 Android Development] Jackones:
I‘m on T-Mobile (original) in Germany.

I switched to PixysOS again, maybe you want to try that.
[Moto G 2015 Android Development] MSe1969:
New build with February 2023 ASB patches

Hi all,

a new build is available for download and offered in the Updater app:

https://sourceforge.net/projects/lin16-microg/files/osprey/lineage-16.0-20230220-UNOFFICIAL-microG-signed-osprey.zip/download

Custom build release 2023-02-01

microG on 0.2.27.223616-3

Spoof apps installed by G*PlayStore *)

*) Apps installed by Aurora are now spoofed as "installed by Google PlayStore". This should fix such issues, where certain apps complain or refuse to run, when installed via Aurora - the internal string they expect is "com.android.vending", which translates in this build to the FakeStore app, so don't be worried, if the app info tells you "installed by FakeStore"

Happy flashing!

Regards, M.
[Moto G 2015 Android Development] zakk87:
@MSe1969 updater process ended with signal: 7

twrp-3.7.0_9-0-osprey.img
[Moto G 2015 Android Development] MSe1969:
Is it the 1st time with TWRP 3.7 ?

I am asking because I have made the experience - so far only for 14.1 builds I have to admit - that using the most recent twrp version on older android releases isn't always the best idea. The only true need to use the most recent twrp is the most recent android version to flash. On my osprey device, I still use TWRP 3.4.0
[Moto G 2015 Android Development] zakk87:
That's what I thought, that's why I provided the twrp version. I've had similar problems in the past, so I'll try the older version.

Edit: it works with TWRP 3.4.0.0 but only from internal memory. When I try to install from SD card recovery was restart. Nevermind.

Last question @MSe1969 how to install play store?

Rom is very smooth. Thank you!
[Moto G 2015 Android Development] MSe1969:
Interesting - not aware of this (however, in the last months, I've always installed from internal memory myself). Maybe a bug fixed in version 3.4.0-1 ? Anyhow, if you use in future the OTA feature, it'll anyhow use internal memory.

This ROM comes with pre-installed AuroraStore, which in fact acts as a "front-end" to G's play store with some options not available in the "original" (like downloading a specific older app version or anonymous use). So normally, you would not need the "original Google" playstore app. With the most recent build, it is even spoofed to installed apps, that they were installed by the "original" play store app.

Next to enhanced privacy and the absence of the infamous "Google kill switch", not using Gapps also makes your phone faster, using less network bandwidth and provide better battery behavior.

To make a long story short, there indeed

are

rare cases, where you really would need the original play store along with the genuine Google Play Services - if you indeed have such a case and you cannot work with any app alternative for the one specific app refusing to work on my ROM because of the missing play store or missing genuine G* spy services (but first search the net for app alternatives, you will be amazed - the alternatives often are even better), then I am afraid this ROM isn't for you and you should aim at any "default LineageOS" build allowing you to flash the regular Gapps...

Thanks for the positive feedback!
[Moto G 2015 Android Development] ragnaroknroll:
I just tried a clean install of the latest version (20230220) of the ROM on my MotoG using TWRP v3.7.0. I first flashed the ROM and then Open GApps pico arm 9.0 (20220215). Both flashes were successful. Upon first boot, I am asked to pick a language and it then starts "Checking for updates", but never finishes. It has successfully connected to my Wifi, but this checking of updates hasn't completed even after leaving it to check for them overnight. I'm not able to skip this step and move forward in the phone initialisation process. Any ideas what I may be doing wrong? Thanks!

EDIT: Not sure if it's relevant, but thought I'd note here that I'm flashing the ROM and Open GApps using the adb sideload feature.
[Moto G 2015 Android Development] MSe1969:
As explained in the OP, this ROM comes with pre-installed microG, so Gapps should NEVER-EVER be flashed over this ROM! So I'm afraid you need to boot TWRP again, wipe everything and then only flash the ROM - the idea of this ROM is to live without the Google Spy Services.

If you are convinced, that you can't live without Gapps, then this ROM isn't for you.
[Moto G 2015 Android Development] ragnaroknroll:
Gee yikes! I must have misread the instructions. Thanks a lot for pointing this out though. Had no idea what microG was. Have just read up about it and think it's a fantastic idea! Will give it a shot without GApps. Cheers!
[Moto G 2015 Android Development] MSe1969:
New build with March 2023 ASB patches

Hi all,

a new build is available for download and offered in the Updater app:

https://sourceforge.net/projects/lin16-microg/files/osprey/lineage-16.0-20230322-UNOFFICIAL-microG-signed-osprey.zip/download

Custom build release 2023-03-01

some kernel patches (as usual, not mentioning this everytime)

Bromite Webview replaced by Mulch Webview 111.0.5563.58 *)

*) Bromite hasn't received updates since end of last year. It is meanwhile 3 major versions behind Chromium upstream, so this becomes a security issue! So I have decided to bundle the Mulch Webview from the DivestOS project with my build, as it comes very close to my original motivation to bundle Bromite - it is mainly a Chromium webview with many patches applied from the GrapheneOS project.

Happy flashing!

Regards, M.
[Moto G 2015 Android Development] MSe1969:
New build with April 2023 ASB patches

Hi all,

a new build is available for download and offered in the Updater app:

https://sourceforge.net/projects/lin16-microg/files/osprey/lineage-16.0-20230420-UNOFFICIAL-microG-signed-osprey.zip/download

Custom build release 2023-04-01

some kernel patches

Mulch Webview 112.0.5615.101

Happy flashing!

Regards, M.
[Moto G 2015 Android Development] MSe1969:
New build with May 2023 ASB patches

Hi all,

a new build is available for download and offered in the Updater app:

https://sourceforge.net/projects/lin16-microg/files/osprey/lineage-16.0-20230512-UNOFFICIAL-microG-signed-osprey.zip/download

Custom build release 2023-05-01

some kernel patches

Mulch Webview 113.0.5672.77

Happy flashing!

Regards, M.
[Moto G 2015 Android Development] billyrich:
Hi @MSe1969 ,

I would like to know how you got the applications installed from Aurora to be faked as "installed from Google PlayStore".

I compile lineageos with microg and AuroraStore for some of my devices and would like apps installed from AuroraStore to display as installed from PlayStore.

Thanks
[Moto G 2015 Android Development] MSe1969:
Assuming you compile for lineage-16.0 (as you have asked in this thread), you would need to apply the below commit to frameworks/base :

PackageManager: Spoof Google Play Store as installer instead of Auror… · lin16-microg/android_frameworks_base@aa94e03

…aStore Some apps have a questionable "Integrity check" and refuse to run, if they think that they haven't been installed from the Google Play Store. In case of installations coming ...

github.com
[Moto G 2015 Android Development] MSe1969:
New build with June 2023 ASB patches

Hi all,

a new build is available for download and offered in the Updater app:

https://sourceforge.net/projects/lin16-microg/files/osprey/lineage-16.0-20230620-UNOFFICIAL-microG-signed-osprey.zip/download

Custom build release 2023-06-01

some kernel patches

Mulch Webview 114.0.5735.131

microG 0.2.28.231657

AuroraStore 4.2.3

The coarse location functionality of microG has been rewritten. microG no longer uses external "plugin" modules for location determination, but instead provides internally this functionality, currently only by fetching data from Mozilla. See here for further information.

Happy flashing!

Regards, M.
[Moto G 2015 Android Development] MSe1969:
Fixed build published

Hi all, I have published a fixed build, which is also offered by the updater app:

A further fix of the system tracing app (developer options) as part of the June ASB could be backported

A Fix in the kernel solves an issue with bad working USB-MTP connections (e.g. of you connect the device with your PC)
[Moto G 2015 Android Development] billyrich:
Thank you
[Moto G 2015 Android Development] MSe1969:
New build with July 2023 ASB patches

Hi all,

a new build is available for download and offered in the Updater app:

https://sourceforge.net/projects/li...-UNOFFICIAL-microG-signed-osprey.zip/download

Custom build release 2023-07-01

some kernel patches

Mulch Webview 114.0.5735.196

microG 0.2.28.231657 - "original" included (see comment)

I have started to rework my microG approach:

With the recent change to include the Mozilla Localtion services (MLS) directly into the microG code also comes the requirement to obtain an API key for MLS, which I don't have right now (I have requested one, but I am not sure

whether

and if yes, when I would get it). I have therefore included the original microG apk and use the now foreseen way to specify certain default settings, so one of the two reasons for me to build from source has gone.

Happy flashing!

Regards, M.
[Moto G 2015 Android Development] MSe1969:
New build with August 2023 ASB patches

Hi all,

a new build is available for download and offered in the Updater app:

https://sourceforge.net/projects/lin16-microg/files/osprey/lineage-16.0-20230816-UNOFFICIAL-microG-signed-osprey.zip/download

Custom build release 2023-08-01

some kernel patches

Mulch Webview 116.0.5845.92

Happy flashing!

Regards, M.
[Moto G 2015 Android Development] pmneo:
Thank you for your nice work!

But I can't get 4G / LTE getting to work.

I only can get EDGE to work relaible. Sometimes when switchen the different network types it has connected to LTE, but the most time it shows a cross on the bottom right corner of the signal strenth :(

Thanks
[Moto G 2015 Android Development] MSe1969:
As I don't have any issue with my own device, this seems to me not a general issue with this build. Based on similar experiences for another device, I recommend that you check the APN settings. Although I frequently backport the carrier-specific APN default settings from higher LineageOS releases, I think it makes sense to visit the homepage of your network carrier and search therein for the current to-be APN settings and configure them manually.
[Moto G 2015 Android Development] pmneo:
Thank you,

I have tried different APN Settings, different types of Network Types and I thought that it worked, but after the next Flight Mode or reboot the phone does not longer connect to LTE, until i try again the same things.

Very weired :(
[Moto G 2015 Android Development] MSe1969:
Indeed weird...

Can you produce a log? Maybe the log shows some hints...?
[Moto G 2015 Android Development] pmneo:
Nope sorry, but with PIxysOS 2.4 the LTE connection with the same APN settings work fine.
[Moto G 2015 Android Development] MSe1969:
I can only repeat, that I don't have those issues, which you describe, on my own device.

Have you really manually checked the exact APN details and fixed them accordingly, if you found any discrepancies?
[Moto G 2015 Android Development] MSe1969:
New build with September 2023 ASB patches

Hi all,

a new build is available for download and offered in the Updater app:

https://sourceforge.net/projects/lin16-microg/files/osprey/lineage-16.0-20230914-UNOFFICIAL-microG-signed-osprey.zip/download

Custom build release 2023-09-01

some kernel patches

Mulch Webview 117.0.5938.60

AuroraStore 4.3.1

Slightly hardened GPS configuration

Updated CA-Certificates

Happy flashing!

Regards, M.
[Moto G 2015 Android Development] MSe1969:
New build with October 2023 ASB patches

Hi all,

a new build is available for download and offered in the Updater app:

https://sourceforge.net/projects/lin16-microg/files/osprey/lineage-16.0-20231023-UNOFFICIAL-microG-signed-osprey.zip/download

Custom build release 2023-10-01

some kernel patches

Mulch Webview 118.0.5993.80

AuroraStore 4.3.5

FDroid 1.18.0

Fixes for CVE-2023-4863 and CVE-2023-5217

microG 0.2.29.233013

Happy flashing!

Regards, M.
[Moto G 2015 Android Development] ismarub:
Today I tested this rom and there are things I don't like. It came from the unofficial 8.1 lineup. The previous rom, despite being older, worked fine for me. I first installed a 17.1 lineage and it restarted randomly.

I don't like this rom because it takes up more space than others. When installing it, it only left me 3GB free to install apps on the 1/8GB Osprey. It weighs on your ass when you install things and Firefox stumbles. I think it's because of so many security patches, which ends up killing performance. I have other similar phones with other roms and they fly in comparison. I have seen something interesting and that is that certain apps that do not work with lineages because they detect custom rom (even with microg). Here they are validated and they work without problems.

But in my case I am not going to use this phone as my main phone. The one I use as the main one is a moto g5s that comes with Oreo with 2019 patches. Therefore I return to the unofficial Osprey 8.1 rom.

I thank the creator for his work. But I think that few people are going to use these phones as their main phones. I prefer to have a phone that is supposedly more insecure, but runs smoothly, than one that runs in fits and starts, but with patches from this year
[Moto G 2015 Android Development] MSe1969:
New build with November 2023 ASB backports

Hi all,

a new build is available for download and offered in the Updater app:

https://sourceforge.net/projects/li...-UNOFFICIAL-microG-signed-osprey.zip/download

Custom build release 2023-11-01

some kernel patches

Mulch Webview 119.0.6045.163

microG and companion (aka Fake>Store) 0.3.0.233515

Happy flashing!

Regards, M.
[Moto G 2015 Android Development] MSe1969:
New build with December 2023 ASB backports

Hi all,

a new build is available for download and offered in the Updater app:

https://sourceforge.net/projects/lin16-microg/files/osprey/lineage-16.0-20231220-UNOFFICIAL-microG-signed-osprey.zip/download

Custom build release 2023-12-01

some kernel patches

Mulch Webview 120.0.6099.115

Happy flashing!

Regards, M.
[Moto G 2015 Android Development] MSe1969:
New build with January 2024 ASB backports

Hi all,

a new build is available for download and offered in the Updater app:

https://sourceforge.net/projects/lin16-microg/files/osprey/lineage-16.0-20240113-UNOFFICIAL-microG-signed-osprey.zip/download

Custom build release 2024-01-01

some kernel patches

Timezone DB 2023 updates

Mulch Webview 120.0.6099.210

Happy flashing!

Regards, M.
[Moto G 2015 Android Development] shrots:
Glad to see osprey still being maintained. For little over a year I took pause from the device. Super happy to be back! The latest update with Android 9 is perfect, software feels very smooth!

Hats off to MR MSe1969!
[Moto G 2015 Android Development] MSe1969:
New build with February 2024 ASB backports

Hi all,

a new build is available for download and offered in the Updater app:

https://sourceforge.net/projects/lin16-microg/files/osprey/lineage-16.0-20240217-UNOFFICIAL-microG-signed-osprey.zip/download

Custom build release 2024-02-01

some kernel patches

AuroraStore 4.4.1

Mulch Webview 121.0.6167.178

Happy flashing!

Regards, M.
[Moto G 2015 Android Development] platypoid:
Thanks for the nice rom . Took me awhile of trying other roms that wouldn't load to find this one that works well on this phone someone gave me .
[Moto G 2015 Android Development] shrots:
Thank you for consistent updates! The rom is pure joy!

What might be the cause of the automatic update not functioning? In my case, after download is complete, device boots into TWRP without triggering the update. TWRP ver. 3.5.2_9-0. Phone is not encrypted.

Edit1: Updated TWRP to latest osprey release - 3.7.0-9.0, but again after reboot, stops in recovery.

Edit2: Via TWRP, managed to do update manually as following: copy file from /data/lineageos_updates to sdcard/Download, then perform Install Image. Before reboot wiped dalvik/cache. Update successful without loss of my data.
[Moto G 2015 Android Development] MSe1969:
Thanks for your positive feedback.

In general, I tend to give the advice to use the TWRP version, which was the most recent, when the used Android was the latest and gratest. Here, we talk about Android 9 and e.g. I use TWRP 3.4.0 for the Osprey device. Newer TWRP versions have been developed to cope with new Android versions, to e.g, support the new partition schemes, different ways for file encryption or different was to deal with OTA updates. For old devices not having such features, newer TWRP versions do not necessarily add value (in some cases however, they fix bugs, which may then be needed). What I can tell you is that TWRP 3.4.0 works fine for me for the Osprey device to run any Android 9 (or maybe 10) based builds. That would be my recommendation. (TWRP is supposed to be backwards compatible, and I would assume the TWRP core indeed is, but it depends, how the device maintainers cope with adapting the device configuration when building a newer TWRP...)
[Moto G 2015 Android Development] MSe1969:
New build with March 2024 ASB backports

Hi all,

a new build is available for download and offered in the Updater app:

https://sourceforge.net/projects/lin16-microg/files/osprey/lineage-16.0-20240310-UNOFFICIAL-microG-signed-osprey.zip/download

Custom build release 2024-03-01

some kernel patches

Mulch Webview 122.0.6261.105

Happy flashing!

Regards, M.
[Moto G 2015 Android Development] shrots:
Sweet! Thank you for commitment!

By the way, indeed, with downgraded TWRP (to version 3.4.0-0) update is now automatic!
[Moto G 2015 Android Development] MSe1969:
New build with April 2024 ASB backports

Hi all,

a new build is available for download and will soon be offered in the Updater app:

https://sourceforge.net/projects/lin16-microg/files/osprey/lineage-16.0-20240413-UNOFFICIAL-microG-signed-osprey.zip/download

Custom build release 2024-04-01

some kernel patches

Mulch Webview 124.0.6367.42

Happy flashing!

Regards, M.

EDIT: Sourceforge seems overloaded right now... - please be patient
[Moto G 2015 Android Development] MSe1969:
New build with May 2024 ASB backports

Hi all,

a new build is available for download and is already offered in the Updater app:

https://sourceforge.net/projects/lin16-microg/files/osprey/lineage-16.0-20240514-UNOFFICIAL-microG-signed-osprey.zip/download

Custom build release 2024-05-01

Some kernel patches

AuroraStore 4.4.4

Mulch Webview 125.0.6422.46

Happy flashing!

Regards, M.
[Moto G 2015 Android Development] MSe1969:
New build with June 2024 ASB backports

Hi all,

a new build is available for download and is already offered in the Updater app:

https://sourceforge.net/projects/lin16-microg/files/osprey/lineage-16.0-20240618-UNOFFICIAL-microG-signed-osprey.zip/download

Custom build release 2024-06-01

Some kernel patches

microG GmsCore & companion v0.3.2.240913

Mulch Webview 126.0.6478.71

Happy flashing!

Regards, M.
[Moto G 2015 Android Development] MSe1969:
New build with July 2024 ASB backports

Hi all,

a new build is available for download and will soon be offered in the Updater app:

https://sourceforge.net/projects/lin16-microg/files/osprey/lineage-16.0-20240717-UNOFFICIAL-microG-signed-osprey.zip/download

Custom build release 2024-07-01

Some kernel patches

AuroraStore 4.5.1

Mulch Webview 126.0.6478.186

Happy flashing!

Regards, M.
[Moto G 2015 Android Development] MSe1969:
OTA update has now been activated.

Please also consider below advices:

AuroraStore

It is advisable to delete memory and cache of AuroraStore (in Settings - apps) and go through initial steps again. (You need to select AuroraServices as install method AFTER initial setup)

microG

Quote from this issue: https://github.com/microg/GmsCore/issues/2237

"If you are using microG 0.3.2, you can configure https://api.positon.xyz/?key=74600654-2aec-11ef-aa95-3b7218da6865 as an API endpoint in microG Settings -> Location -> ⋮ -> Configure service URL."
[Moto G 2015 Android Development] MSe1969:
Messenger - Signal and Whatsapp

Hi [MENTION=10762195]maxwell80[/MENTION]

regarding Signal - did you try to download the Signal apk directly already?

I am not sure, whether this is a special "Google-free" version (using Websockets instead of GCM) or whether they simply provide the same APK as in Playstore for direct download only...

regarding Whatsapp - would you be willing to test this for me, when I add an exception to the iptables block script?

I can't test myself, as I would have to install WA (yikes!) on my device for that, which is for me an absolute No-Go...

Regards, M.