yashsingh1/xdaforums huggingface dataset:
[Moto G 2015 Android Development] alanthelinuxguy:
M

New build downloaded, installed, and working fine. Many thanks.

Couldn't download the 17.1 trial but I believe that this was only available to users of Variant B. I'm using Variant A, but I look forward to switching once you have a final product ready to go for "mere mortals"! {grin}

Alan
[Moto G 2015 Android Development] MSe1969:
Hi - in fact, this is something, what can be even observed in the "official" LineageOS 17.1 builds for the Osprey device. So this is not related to my build in particular. Anyhow, I'll try to have a deeper look - I have observed already, that the LineageOS 16.0 build (as mentioned, this is mainly chil360's work) uses the TimeService.apk (Qualcomm time service) from the Motorola blobs, whilst LineageOS 17.1 (both, chil360's unofficial builds as well as the LineageOS official build) uses 'Sony Timekeep' - don't know why, but I may want to try in my builds with the Qualcomm TimeService (although I suspect, that there must be a reason for this...)

Regards, M.
[Moto G 2015 Android Development] MSe1969:
Switching from LineageOS 16.0, build variant A, to official LineageOS 17.1 builds for the Osprey device

Hi all,

here comes a tutorial how to switch from my current LineageOS 16.0 build

variant A

to official LineageOS 17.1 build without having to do a clean install (e.g. to keep your data):

Download my migration build from below URL and place it into the internal memory or SD card of your Osprey device:

https://sourceforge.net/projects/lin17-microg/files/MIGRATION/lineage-17.1-20201218-MIGRATION-osprey.zip/download

Download the latest official build from LineageOS and also place it into the internal memory of SD card of your device:

LineageOS Downloads

download.lineageos.org

Download any further flashable ZIPs, you may need for your specific setup, such as Gapps (remember: arm and Android 10, flavor of your choice), Magisk, etc. and also place it to your phone

Reboot to recovery

Make a nandroid backup, to be able to restore the current LineageOS 16.0 Setup

Wipe the /system partition

Flash my migration build, afterwards - without rebooting - Gapps (if applicable) and afterwards (also only, if applicable) Magisk and any other additional stuff - but DON'T flash the official build yet!

Wipe cache & dalvik and reboot into LineageOS 17.1

You are now with my Migration build - remember, that this build is not secure - simply verify, that the system seems to work as expected and that you can re-setup, what might be missing. However, don't install new stuff and only have the migration build active for a short time.

Reboot to recovery and flash/install now the official LineageOS 17.1 build and reboot - DONE.

This does not have to happen immediately, but I wanted to provide this information - feedback welcome.

Regards, M.
[Moto G 2015 Android Development] sponk0:
Thank you very much for providing these instructions and the migration build. I followed the instructions 1 by 1, and everything went smoothly and looks fine so far.

I started from the 16.0, Variant A build from Dec. 18

Test device is a XT1541 (16GB/2GB)

I installed opengapps from 2020-12-09, arm / android10 / "nano" version and official lineageos-nightly from 2020-12-18

The phone is operated without a SIM at the moment, so I only tried WiFi (can't comment on calls and mobile data), and I haven't done real-life testing over a longer period of time yet (just installed a few minutes ago). If anything comes up that is looking odd, I'll let you know.
[Moto G 2015 Android Development] sponk0:
Just for the sake of completeness: phone is still running fine with no hiccups
[Moto G 2015 Android Development] alanthelinuxguy:
M:

Following the above instructions (Dec 19, 2020 at 7:38 PM), I have now installed LineageOS 17.1. The flashing process worked exactly as advertised. I have yet to try out Android 10 to any great extent, but I do have two questions for you regarding the new build:

(1) Are you switching to LineageOS 17.1 builds going forward, such that there will be future updates of this new variant and, presumably, if this is the case, the recent 16.0 series will be abandoned at some point?

(2) I ran into some storage issue with 16.0 where the free storage dropped precipitously to about 300 MB and Google Play refused to download and install any new apps or updates (see: https://linuxnorth.wordpress.com/2020/12/19/tracking-down-android-storage-space-hogs/).

Initially, I thought that this was the K-9 E-mail client grabbing almost 1 GB of storage in app_view/BrowserMetrics. I cleaned out this folder, checked the web for references to BrowserMetrics and found a bug report on GitHub:

Webview’s BrowserMetrics should be regularly cleaned by K-9 #5061

Webview's BrowserMetrics should be regularly cleaned by K-9 · Issue #5061 · thunderbird/thunderbird-android

Describe the bug I noticed that K-9 Mail occupies 800MB of internal storage and decided to check what eats so much space. Running du -h /data/data/com.fsck.k9 revealed the WebView's BrowserMetrics ...

github.com

The OP indicated that "we (the group of people maintaining legacy LineageOS including MSE1969) resolved the problem by switching system webview to Bromite."

However, before I could research Bromite, I found that free space was still being eaten up and it turned out that many apps were using considerable amounts of storage in the same manner. A post on GitLab noted the same issue.

WebView produces a lot of garbage in cache

WebView produces a lot of garbage in cache (#2820) · Issues · LineageOS / issues / android · GitLab

Apps using WebView (e.g.Jelly) are collecting a lot of garbage in their app_webview/BrowserMetrics directory, which never gets deleted. I just manually deleted several hundred MB in seveal apps....

gitlab.com

A recent post on this forum noted that "This will be resolved by any builds dated 20201227 or later..."

Can you confirm that this is indeed the case for your build of LineageOS 17.1 ?

As usual, many thanks for all your work on these custom ROM's and Happy New Year!

Alan
[Moto G 2015 Android Development] MSe1969:
Hello Alan,

yes, my plan is to open a new thread for the LineageOS 17.1 "microG" build variant and to stop the LineageOS 16.0 builds eventually. I won't provide a "default" LineageOS 17.1 build any longer, that is why I have published the instructions to help people, who have so far used the build variant A of my 16.0 builds to take advantage of the official LineageOS 17.1 builds. I have provided the build variant A for LineageOS 16.0, as there hasn't been any official 16.0 build for the Osprey device, but providing a build variant with almost no difference to the official builds does not really add any value - that's why.

Just to be sure, that things don't get mixed up or confused:

The build variant B ("microG build") of my builds uses Bromite Webview instead of the default System Webview, hence those builds aren't affected that much, as Bromite seems to clean up this directory frequently. There is however an issue opened for Bromite to entirely remove that feature - one of the next releases of Bromite will include it.

The build variant A (Standard build) makes use of the default Webview shipped by LineageOS, that is why those builds were affected. LineageOS has now patched their Webview, so any new official builds including that patch will stop wasting that much space (you may however still have to manually do some cleaning)

As indicated above, I will stop providing the build variant A for LineageOS 17.1 - people who were using my build variant A for LineageOS 16.0 should switch to the official builds of 17.1.

Regards, M.
[Moto G 2015 Android Development] alanthelinuxguy:
M:

I was surprised to see that LineageOS are once again supporting the Moto G3 as they dropped this model some time ago. Are you creating their official build, or has someone else at XDA recently acquired this phone?

When LineageOS dropped the Moto G3, I picked up your custom ROM but went with Variant A since I didn't think I needed the added features of Variant B and so I opted for "simplicity". However, now that you are standardizing on the microG build, I'm thinking that maybe I should simply switch to this version, and stay the course with the tried and tested, rather than go back to LineageOS and have them drop support at some point.

I realize that developers move on from time to time, and that some phones will inevitably lose support at some point. It's just that I'm happy to keep my Moto G3 alive for as long as possible and I have found your builds to be very efficient in this regard.

Alan
[Moto G 2015 Android Development] MSe1969:
Hi Alan,

I use the official LineageOS device config, kernel and blobs of 17.1 for my Osprey "microG" build. This means, that if I did also a "build variant A", it would be identical (except for the build signature) with the official 17.1 build of LineageOS, and that does not really make a lot of sense.

I *may* (not sure, yet) consider working on an own kernel fork to apply additional patches - but even that would not really justify to publish an own build variant A. (In that case, I could e.g. consider to simply offer a boot.img to be flashed via TWRP or similar, if there was a real interest).

If however - for whatever reason (which I don't believe for the moment) - LineageOS decides to drop the official Osprey support in the future, I will be happy to step in again.

Regards, M.
[Moto G 2015 Android Development] MSe1969:
LineageOS 17.1 thread created

Hi all,

I have just posted a new thread for my hardened 17.1 microG buld for the Osprey device:

https://xdaforums.com/t/rom-unoffic...ineageos-17-1-for-motorola-g3-opsrey.4218515/

It contains a 17.1 hardened microG build with the January 2021 ASB patches included.

As explained in this thread before, I would like to summarize the below information:

I will stop providing 16.0 builds in this thread

The hardened 17.1 microG build from the referred thread can simply be "dirty-flashed" over the latest version of the build variant B from this thread - this is what I recommend to do in the near future

People having used the 16.0 build variant A so far should switch to the official LineageOS 17.1 Osprey ROM. I have explained here the details.

People already using my 17.1 test build should be offered an OTA update via the Updater app

I would like to use the opportunity to thank you for your interest in these builds and look forward to seeing you in my new 17.1 thread.

In the meantime, I will keep this thread open for a while to answer further topics to my LineageOS 16.0 builds and/or to help migrating to 17.1, if needed.

Cheers, all the best

M.
[Moto G 2015 Android Development] nodens76:
Thank you very much @MSe1969 for your hard work on this builds. Your builds are always high quality one !

I would like to thank you with a few beers/coffees (what's your preferred way of transfert) !?
[Moto G 2015 Android Development] MSe1969:
Many thanks for the positive feedback and for considering making a donation, much appreciated - but don't worry.

I am referring you to an answer, which I have given in another thread about that topic; it outlines my point of view:

https://xdaforums.com/t/rom-lineage...r-moto-g-falcon.3808428/page-17#post-81839953

Cheers, M.
[Moto G 2015 Android Development] nodens76:
Thanks for your reply, I'm very inline with your perspective of privacy and community sharing !
[Moto G 2015 Android Development] MSe1969:
Heading towards EOL

Hi all,

as announced already before, there is now a LineageOS 17.1 successor thread for the "microG" build variant B. Btw, an update with February '21 ASB patches has been published there. Also, a "howto" for folks using the 16.0 build variant A to migrate to the "official" LineageOS 17.1 builds has been provided. Further, no additional questions and/or comments to the 16.0 builds have been posted here.

So I think it's time to declare the EOL of this thread. I will soon ask the forum admins to close this thread - if you have any questions on how to migrate, please feel free to ask them in my successor thread.

A last time here, thanks for your interest and hope to see you in my LineageOS 17.1 thread.

Cheers, M.
[Moto G 2015 Android Development] MSe1969:
Back again

As explained in the updated and reworked OP, this thread has been re-activated. I will again provide hardened LineageOS 16.0 "microG" builds for the Osprey device. Please read through the updated OP to get the full picture.

You can download the build from here:

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

ASB Security string 2021-12-05

Bromite Webview 96.0.4664.54

microG 0.22.214516-21

F-Droid 1.13

Many kernel sec. patches

Updated DRM blobs

Happy flashing!

Regards, M.
[Moto G 2015 Android Development] MSe1969:
Quote from my 17.1 thread about this 16.0 build from @Tiki Thorsen :

(y)

I have some good news for you - please have a look at this test build here (will become part of this build from next month onwards - feedback welcome):

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

"Music Player GO" seems to work on my latest test build, please check again and let me know.
[Moto G 2015 Android Development] Tiki Thorsen:
I performed a clean install and tested it for a couple of days.

The audio channel balance under Settings>Accessibility works just as it did on Android 10.

Music Player Go works correctly now.

In case someone is interested in getting a full dark mode;

For Substratum Theme Engine to work, you must have root access

Install this via recovery and then enabled "developer options" and enable "Root Access", afterwards install this.

(I prefer this method over having Magisk installed just to get root)

EDIT: I found a small glitch, entering the wallpapers "app" and scrolling down, is very laggy/delayed and slow.
[Moto G 2015 Android Development] Tiki Thorsen:
@MSe1969 What are your thouts on the Simple Mobile Tools suite?

I am currently testing them, so far they are lightweight and bloatware free. (The gallery, calendar, contacts and phone for now)

Getting them from F-Droid (including Simple Thank You) allows you to have all the PRO versions.
[Moto G 2015 Android Development] MSe1969:
Looks like a good alternative to bloatware stock apps, so for sure worth to consider for folks with Stock ROM on their phones. I haven't tested so far, but makes a really good impression.

In case your thoughts point into suggesting to ship them in my build:

The respective apps provided by default LineageOS are also either based on AOSP or known opensource projects. So I don't see any point in shipping them instead of the LineageOS ones, especially, as everybody can simply install them and decide to use instead of the shipped ones, or install things not shipped by LineageOS (like Draw or the notepad) Or do you see any particular app of them doing things better than the LineageOS ones?
[Moto G 2015 Android Development] MSe1969:
New build with January 2022 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-20220121-UNOFFICIAL-microG-signed-osprey.zip/download

ASB Security string 2022-01-05

Some kernel patches

Backported Audio balance (accessibility settings) from Android 10

Happy flashing!

Regards, M.
[Moto G 2015 Android Development] Tiki Thorsen:
I was looking for an SMS app and calendar replacement; since the stock calendar is not usable without an account, and personally I don't like the stock SMS app. The Simple Camera has a very nice feature to remove the metadata from the pictures.

But I do agree with you that it is not necessary to include them in the build.
[Moto G 2015 Android Development] Tiki Thorsen:
Which version of TWRP do you recommend? (To avoid using/errors when installing via OTP)

The OTA updated failed to install, it went to TWRP;

Error opening: '/data/system/dropbox/system_app_strictmode@1642588679065.txt' (I/O error)

I did a manual installation of the update and it installed correctly, but it gave me the same error at the end.

I can attach the whole .log file from TWRP if you want/need.
[Moto G 2015 Android Development] MSe1969:
I just made a test on my 2nd osprey device, and all went smoothly without any issue - using TWRP 3.3.1
[Moto G 2015 Android Development] TheLabCoat:
Hi i found a bug yesterday this all happened because i forced the cpu (i did nothing to the cpu only i tried to play this) trying to play clash of clans the device couldn't handle and it happened something that always happened to me on havoc os or cr droid to reprudece the bug you have to use the rom some time and it comes at a hard reset(holding power button to simulate taking off the battery) the notification bar dosn't show anymore and don't get any push notifications only sound you cant expand notifications or the bar plugin usb don't show the phone folder on the pc. So i was on linage 16 and updating everyday manually with ota this happened so i wiped out internal memory and factory reset and installed this rom (clean flash) in the rom and solved. I got another error that i posted here but it was my fault i forgot to mount data. To reproduce the bug i mentioned before i was using the rom like for 1 month and for this to happen on havoc i was on 3 months or 6 but on that try i didnt forced the cpu just happened and one day woke up turn on my phone and found that i cant use notification bar maybe the customizations of the rom forced

appart from this the rom works great and it is so stable, im going to purchase a battery latter to expand the vital life this is an incredible phone dispite the olderness. Thanks for you effort is really appreciated.
[Moto G 2015 Android Development] TheLabCoat:
solved forgot to mount data after deleting data and reboot to recovery
[Moto G 2015 Android Development] Ritik99:
https://xdaforums.com/t/rom-unoffic...neageos-16-0-for-osprey.4095453/post-83301927

Try this next time.
[Moto G 2015 Android Development] MSe1969:
New build with February 2022 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-20220219-UNOFFICIAL-microG-signed-osprey.zip/download

Custom build release 2022-02-01

F-Droid updated to 1.14, F-Droid privileged extension to 0.2.13

Bromite System Webview updated to 97.0.4692.106

microG updated to 0.2.24.214816-2

The AOSP project has stopped to officially provide security patches for Android 9 (Pie), hence the patches have been backported from Android 10 by the LineageOS team. This means, that the official security string will not get updated any longer and remains on the value 2022-01-05. In order to still show the status and security backports on a "best effort basis", the ROM now shows in addition a "Custom build release" to indicate this.

Happy flashing!

Regards, M.
[Moto G 2015 Android Development] Esteban Android:
the audio channels are inverted in the jack:(
[Moto G 2015 Android Development] p10s:
The February build includes an old version of Aurora Store which no longer supports anonymous logins. I tried to update the app with F-Droid (after enabling the option to show incompatible versions), but that didn't work. F-Droid complained about a different key and advised to remove the old app. But that didn't work either. I finally managed to install the new version of Aurora Store manually by using ADB with root access.
[Moto G 2015 Android Development] MSe1969:
F-Droid uses an own signature key, whilst I take the apk from the original place: https://gitlab.com/AuroraOSS/AuroraStore/-/releases#4.1.1

If you want to upgrade AuroraStore in future, go there, then you don't need to work with adb etc.

BTW, my next build will ship the updated AuroraStore
[Moto G 2015 Android Development] MSe1969:
New build with March 2022 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-20220317-UNOFFICIAL-microG-signed-osprey.zip/download

Custom build release 2022-03-01

Bromite System Webview updated to 99.0.4844.58

microG 0.2.24.214816-2

AuroraStore 4.1.1

Happy flashing!

Regards, M.
[Moto G 2015 Android Development] Matiasx:
man! so happy to have found this thread, I recently recovered an osprey and I hope this could give it wings
[Moto G 2015 Android Development] Matiasx:
& it works perfectly indeed.

Thx you very much !!
[Moto G 2015 Android Development] ensltr:
Is VoLTE functional in this ROM? or does anyone know how to make it work with this ROM? I had enabled the enhanced 4G LTE mode switch to no avail.
[Moto G 2015 Android Development] MSe1969:
New build with April 2022 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-20220415-UNOFFICIAL-microG-signed-osprey.zip/download

Custom build release 2022-04-01

Bromite System Webview updated to 100.0.4896.57

Happy flashing!

Regards, M.
[Moto G 2015 Android Development] MSe1969:
New build with May 2022 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-20220509-UNOFFICIAL-microG-signed-osprey.zip/download

Custom build release 2022-05-01

Some kernel patches

Bromite Webview on 101.0.4951.53

microG updated to 0.2.24.214816-10

Mozilla Location provider on 1.5.0

F-Droid 1.15

Happy flashing!

Regards, M.
[Moto G 2015 Android Development] MSe1969:
Sorry for my late reply.

VoLTE is tricky, especially with older devices. I am not an expert with that, I simply took over the device config.

As far as I know, it seems to work only "partly" for the osprey - there are countries and operators, where it seems to work, and others, where it will never work (I e.g. never got it working in Germany). That's all I can say - if you try and it works, be happy, if not - tough luck...
[Moto G 2015 Android Development] ensltr:
No worries.

In my case (Mint, a T-mobile US MVNO) the phone stats indicate that VoLTE is active (voice in LTE network while in standby) but it has never been able to actually pick up a call in LTE, The ultimate test will come this July when they shutdown 3G networks, I'm almost sure I will loose telephony but we will see. Anyway, thank you so much for your work maintaining this devices (I have a few peregrines too that still see plenty of use).
[Moto G 2015 Android Development] Matiasx:
Data not working for me :(
[Moto G 2015 Android Development] MSe1969:
All fine with my own device. A log and a more detailed description of your issue would definitely help...
[Moto G 2015 Android Development] Matiasx:
Sorry man, I had not configured correctly the APN (my bad). Now it's all working fine, thx again for your work! my phone flies
[Moto G 2015 Android Development] :
Thanks for this excellent ROM as well as for the Moto G falcon one.

I ran into a small Problem with the latest OTA update, it didn’t work with the latest TWRP (twrp-3.6.1_9-0-osprey): “failed to map file @ ...”.

Unfortunately I cannot debug this further, because the device is somewhere else. Flashing manually in TWRP works.

A first search suggests this is a TWRP problem. Is twrp-3.3.1-0-osprey still the version the updates are tested with? In case the next update fails, I think it would be probably easier to downgrade TWRP.

Much obliged.
[Moto G 2015 Android Development] MSe1969:
I am using 3.4.0-0, but 3.3.1-0 should also be OK, I think.

Yes, as a rule of thumb, "never touch a running system" - and more modern TWRP versions are basically created and developped to cope with the respectve latest Android version. As TWRP largely depends on

device config

, the most advanced TWRP versions are created with device configs aiming at latest Android versions - hence it can (but does not have to) be indeed a reason to "roughly" stick with the TWRP versions, which were optimized for the Android release in use, especially for OTA functionality.