yashsingh1/xdaforums huggingface dataset:
[Moto G 2015 Android Development] phool4XC:
Thank you again for the time you have spent providing useful free stuff! I have tried to give as much detail as possible, but please let me know if you need any more information. (You may also have to tell me how to extract it from the system, as I'm a relative noob.)

There are only two issues I've noticed with this build, and one of them has been present in the last two builds for 14.1 option B.

1. The first issue is the inability to install Magisk. This is because I'm a noob and don't know which file I'm supposed to select and patch using the Magisk Manager install dialogue. On other devices I have simply booted to recovery and used TWRP to install the .zip for Magisk, but that did not work with this ROM. After my initial failure, I tried reflashing the ROM and installing Magisk as part of the flash procedure. I also tried using the ADB Sideload facility in TWRP -- the output showed it installed successfully, but when I rebooted, Magisk 20.4 was still not detected by Magisk Manager 7.5.1 (276).

2. The second issue is a problem (or maybe multiple problems) with the Aurora Store. The first time it ran, it detected an update, but installing that update failed with an error message about "Insufficient storage space." I tried using F-Droid to update it, and got the following message:

When running the version provided by the ROM, it produced an error message near the bottom of the screen where "Building the Google Play API" initially appears saying "It is taking longer than expected" with a clickable option immediately below the Aurora Store logo, "Continue anyway ?" When I continue anyway, I'm left staring at a spinning wheel above "Loading." When I went to uninstall Aurora Store and then reinstall manually from F-Droid, I discovered that it's behaving like a system app which can only be disabled, not removed.

This second issue has shown up in the last two builds of the 14.1 ROM, as well.

Note that my primary use for the Moto G3 at this point is as an e-reader / GPS device. I don't know if there are any connection issues with mobile data as I'm using WiFi.

Tschüss!
[Moto G 2015 Android Development] MSe1969:
Hi, thanks for your feedback - appreciated.

Regarding Magisk, I unfortunately can't really help. In general, Magisk aims at patching the kernel to divert the access requests to the /system partition to it and from there either back to /system or to replaced parts located on the /data partition. The kernel I use is forked from chil360 and is a Hybrid-X custom kernel, compiled with a specific toolchain. Do the Magisk threads on XDA maybe provide a solution or more info?

I'll try it myself maybe, but can't promise anything.

EDIT - I just tested with my device and was able to flash Magisk without issues - all seems to work fine:

- Flashed Magisk-v20.4.zip from topjohnwu's Github via TWRP

- Booted into system and simply installed Magisk Manager v7.5.1.apk (also from topjohnwu's Github)

Regarding Aurora, the "building API took too long" issue has been discussed in the Aurora thread on XDA and should be fixed (or at least improved) in the latest version 3.2.8, which I'll bundle with my next build - there is however also a built-in option to update Aurora to the latest version. Usually logoff/logon with the anonymous account should fix it temporarily. I only bundle AuroraStore, but I am not its Dev.

Regarding your app update issue: F-Droid usually fetches the sources from the connected repositories, compiles from scratch and uses an own app signature (at least for its own app repositories, not for included 3rd party ones). This means, that you can only update apps via F-Droid, which have been originally installed from F-Droid.

Why Aurora had update issues first hand, I don't know - which app did you attempt to update and which install method did you specify? And did you grant the storage permission?

Regards, M.
[Moto G 2015 Android Development] phool4XC:
Thanks for pointing me in the right direction(s)! Clearly I hadn't bothered doing my own search for solutions.

I hate to see good tech discarded just because it's old, so I really appreciate the work you've done which allows me to have an up-to-date OS and security patches.

Looking forward to the next release!

- p
[Moto G 2015 Android Development] jemail:
I experienced this problem when I activated the custom tokenizer option in the network settings. Disabling the custom tokenizer option solved the 'taking longer' issue for me.
[Moto G 2015 Android Development] MSe1969:
Information

Hi all,

a couple of informations:

1. Three new builds with May 2020 ASB are on their way as usual, in a couple of hours they will be available and announced here, as well as via OTA update

2. Some of you may have already noticed, if not, I'll let you know with this post:

I have opened a separate Lineage 16.0 thread for the Osprey device.

You may have already guessed, what my previous test build posts were aiming at... ;)

My intention of providing builds focuses on stable, daily-driver enabled builds rather than "latest and greatest, but bleeding edge/beta".

Based on my own testing, my son meanwhile using Lineage 16.0 on his device and some of the feedbacks received, I am of the opinion that indeed, my LineageOS 16.0 builds fulfill this criterion.

I will provide two build flavors: LineageOS 16.0 "standard" and "hardened microG". I won't support "substratum themes" any longer, but LineageOS 16.0 also offers different themes (incl. dark mode).

The device config. work is mainly based on chil360's great work, but I managed to identify the crucial commit authored by squid2 to get the device encryption functional. The kernel contains latest sec. patches, I have added native Wireguard support (for whomever wishes to use WG) and the new series also offers OTA updates.

This having said, I am planning to stop the Nougat builds for the Osprey device. There is no immediate need to "convert", as indicated, there will be in a couple of hours again the known three 14.1 build variants A, B, C with the expected quality.

3. I will soon post some instructions on how to migrate from this build to the new LineageOS 16.0 builds without having to perform a "clean flash". This option may be of interest for you (if so, please wait for the post before "playing around" on your own).

Cheers, M.
[Moto G 2015 Android Development] MSe1969:
New builds with May 2020 ASB

Hi all,

new builds are ready

and are already offered through the updater app as OTA update

:

A. Default LineageOS 14.1 with substratum and microG patch

https://sourceforge.net/projects/li...1-20200507-UNOFFICIAL-oms-osprey.zip/download

ASB Security string 2020-05-05

System Webview on 81.0.4044.117

B. Hardened build with pre-installed microG and F-Droid

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

ASB Security string 2020-05-05

Bromite Webview on 81.0.4044.127

AuroraStore updated to 3.2.8

C. Above hardened microG build with substratum patch

https://sourceforge.net/projects/li...0200507-UNOFFICIAL-mG-oms-osprey.zip/download

ASB Security string 2020-05-05

Bromite Webview on 81.0.4044.127

AuroraStore updated to 3.2.8

Happy flashing - regards, M.
[Moto G 2015 Android Development] alanthelinuxguy:
May updates received through the Updater. Installed and working with no problems.

I note in your recent posts here that you have a 16.0 build available. Is this your recommendation for future builds for Osprey? If so, what are the main benefits/differences that will result from switching to the new release? Will you continue to maintain 14.1 in addition to 16.0 or is the plan to eventually move to 16.0?

Thanks again for all your work on the software.

Alan
[Moto G 2015 Android Development] alanthelinuxguy:
In your message detailing how to update to 16.0 there may be a problem with a link to "Android 9.0 (Pie)" in the above-noted sentence. If I'm not logged on to XDA, it gives me a link but takes me to an eBay web page. If I am logged in to XDA, there is no such link. Strange...

I believe that the link to GApps is: https://opengapps.org

Alan
[Moto G 2015 Android Development] MSe1969:
I haven't formatted any link around this section (and I myself don't see any) - the only link is to download the Migration build, variant A, from sourceforge.net

(I only wanted to express, that since you "dirty-flash" a pie build over a nougat build, that you obviously have to replace stuff you flash on top to fit accordingly, like Gapps.)
[Moto G 2015 Android Development] MSe1969:
As mentioned in my post, I am planning to stop the Nougat builds in favor of the Pie builds.

Differences for variant A are the same differences between LineageOS 16.0 (Android 9.0) vs. LineageOS 14.1 (Android 7.1).

Regarding the "microG" variant, in addition some more securing and other features (see OP).
[Moto G 2015 Android Development] alanthelinuxguy:
I followed the instructions and installed the migration package plus Gapps pico. The installation seemed to work fine. It stopped at a screen with just the date and time, and an icon which turned out to be some sort of indication of trust. I wasn't sure if the update was still running or how to proceed. There doesn't seem to be any support for swiping across the light sensor at the top of the screen, but pressing the power key brought the system to life. [It appears that the trick may be to tap the screen twice and then swipe up to unlock.]

The package retained my contacts, E-mail messages (K-9), and the reminders set in the Just Reminder app so it looks like all my data is still in place. I had to log back in to my Internet service but, once the connection was established, Updater offered me the LineageOS 16.0 May 6, 2020 update. This installed with no issues, other than my having to re-establish my set of custom icons on the home screen.

The user interface for Pie is somewhat different from that of Nougat, so there will be a bit of a learning curve going forward. However, since you will be moving to 16.0 at some point in the future, it's probably a good idea to start on this curve now. :)

As usual, thanks for all the work you put in to keep the Moto G3 alive - and for keeping our brains sharp with the challenge of figuring out new systems!

Alan
[Moto G 2015 Android Development] sponk0:
Just updated from 14.1 to 16.0 using the "migration" build method and the posted instruction. So far everything looks fine.

Only minor issues I experienced are:

had to re-enter Wifi password once

layout of start screen changed (but I was using a 3rd party launcher before)

Note for other users: During the 1st reboot after flashing the new build the screen remained just plain black for a little while (maybe a few minutes): Don't panic and just give it a little time, everything booted fine after a little wait.

Thank you very much, great build! It's really nice to see such great community support for a almost 5yr old device.
[Moto G 2015 Android Development] MSe1969:
Thanks for reporting your experience.

Yes, WiFi password is expected, as it's stored now in a different file (since Android 8 - I'll add a note in my instructions). I am myself amazed, that jumping from 7.1 to 9.0 (meaning to jump over 8.0 and 8.1) works that well...
[Moto G 2015 Android Development] Italord:
Is this rom stable for basic gaming? I tried LOS 16 and 17.1 but experienced worse performances trying to play Yu-Gi-Oh! Duel Links in those builds than in stock rom. Osprey is my secondary device, so I really don't care about using new android features on it, I just want to use it for basic gaming and would like to know what build is better for this.
[Moto G 2015 Android Development] MSe1969:
Honestly, no idea - I am not too much interested in this area. Give it a try and report back, I'd say...
[Moto G 2015 Android Development] sponk0:
I'm afraid I have to update my experience report. After running for a few minutes / hours I ran into a big issue: unlocking the lock screen did not work any more.

After entering the unlock pattern the screen quickly went black, then went back to the lock screen.

It felt like it sort of crashed during the unlock sequence and then went back to lock screen.

Reboot did not help: phone boots up fine until lock screen, but then can't be unlocked

I went back to 14.1, did the upgrade procedure once again, then same effect: initially all looks good, but then suddenly the phone won't unlock any more.

Before the problem occured, the phone was idle for quite a bit, so maybe it has something to do with doze mode (but this is pure speculation, I didn't do any debugging)

For the time being I reverted back to 14.1, which is running fine, so no big issue for me. Maybe I'll clean flash 16.0 at some later point if I find the time. Just felt like sharing the information.

Edit: additional information, for what it's worth: my osprey is running without a SIM card, it's WiFi only, in case that matters
[Moto G 2015 Android Development] MSe1969:
My own device does not show such behavior (but I haven't used a pattern) Question: Did you OTA update the migration build, as advised, or did you do all your testing with the migration build?

Also, a little trick: If you cannot get past the lock screen, boot to TWRP and delete the file /data/system/locksettings.db (ofc, this only works if you have decrypted the /data partition).
[Moto G 2015 Android Development] sponk0:
Yes, I did the OTA update. I did not do any tests with the migration build.

Thanks for the hint.
[Moto G 2015 Android Development] MSe1969:
As said, I have no issues with my osprey device (using PIN f. Lock screen and encryption).

I made however, on my Oneplus 3T device, the observation that when I was switching between Lineage 15.1 (my daily driver at that time) and 16.0 (test builds at that time) and back by restoring TWRP backups (I.e. before restoring, always made a current backup for later restore, so broken backup can be excluded), that the lock screen (password) did always not work any more: Means TWRP backup of perfectly working build, restoring backup of previously perfectly working higher build and vice versa, fail. I could always easily fix by deleting lock settings.db in TWRP before booting and then activating lock screen again, but that was weird. I took it as a one-off, and it only happened when switching. Maybe here sth. similar? No idea, especially as it worked at the beginning, if I understood you right...
[Moto G 2015 Android Development] sponk0:
Not sure if the issue I experienced is really comparable, I might have described it incompletely. Let me give it another try:

1. installed Migration build

phone boots, asks for pattern for decryption of data partition, accepts pattern, completes booting. Then I played around a little, locking/unlocking working fine

2. downloaded (via OTA) and installed regular 16.0 build

phone boots, asks for pattern for decryption of data partition, accepts pattern, completes booting. Then I can use it normally, locking/unlocking with pattern works fine

but: once I leave the phone lying around for a longer period of time (not too long, maybe max. 1 hour), then I suddenly can't unlock it anymore

if I enter incorrect pattern at lock screen: android complains about wrong pattern, let's me reenter another try (as expected/usual)

if I enter correct pattern: screen briefly changes to blackish, then jumps right back to lockscreen, but without any error message (once it has reached this point, even a reboot does not fix the issue, strangely)

but as this seems to be a singular case on my phone only, it's probably not worth putting a lot of effort into troubleshooting. I guess I'll just try a fresh install instead once I find the time. There's no hurry for me. I might also give it a try to remove screenlock and re-apply it later (as recommended).
[Moto G 2015 Android Development] sponk0:
Quick Update:

Tried the upgrade procedure from 14.1 to 16 once again, using the migration build method.

This time I removed the pattern lock once the migration build was booted.

Then OTA to the regular 16 build, and only then reapplied the pattern lock.

So far everything is looking great, now running for 2 days, my problem did not occur again.

Only thing I noticed: if I switch Bluetooth on (even ifnot connected to any device), the WiFi speed drops significantly. Anybody else seeing this?
[Moto G 2015 Android Development] MSe1969:
I don't see that, but I am using the microG build myself.

Are you using Gapps and the "Standard" build?

I am aware of two commits for another msm8916 device in LineageOS, where two not really necessary Google services (Discovery service and nearby messaging service) are switched off in the device configuration - and this is said to solve your described issue. I'll include this in my next build.

One general favor please:

Your postings all refer to my LineageOS 16.0 osprey builds. Please post any further feedback to those in my 16.0 thread! Thanks
[Moto G 2015 Android Development] MSe1969:
June 2020 information update

Hi all,

the June 2020 ASB published by Google show a "funny" (or better weird) situation:

Whilst there have been really a lot of patches for Android 10, the situation was different for the AOSP Pie and Oreo branches/tags, for which Google still provides updates.

In fact, Google had pushed in Oreo and Pie tags in May, which have been merged into the respective branches in LineageOS and consequently backported into Nougat (aka LineageOS 14.1).

The published AOSP tags representing the June ASB updates however contain exactly the same patches, so there is nothing new this month in regards to platform patches for any AOSP version below Android 10!

In other words, you can consider the patch level of last month's build being 2020-06-01 (and not 2020-05-05).

Therefore, I have decided not to publish new builds this month in this thread!

As announced already before, I want to continue with LineageOS 16.0 builds and stop providing LineageOS 14.1 builds for the Osprey.

I have just published the June updates in my LineageOS 16.0 thready for the Osprey device

As the May build can still be considered "secure", there is no urgency to migrate to LineageOS 16.0, but I recommend to concentrate on this activity and would be pleased if you continue using my builds now on LineageOS 16.0

In the previous posts, there has already been plenty of information how to migrate etc.

As the LineageOS 16.0 builds are stable, I think it is time now to come to an end in this thread.

I will of course continue answering posts in this thread, but I consider it pretty sure, that there won't be further LineageOS 14.1 builds for the Osprey device.

Hence, thanks a lot for your interest in this thread and looking forward to seeing you in my LineageOS 16.0 thread.

Cheers, M.
[Moto G 2015 Android Development] rori1977:
Short feedback after successful migration from LOS 14.1 to 16 Standard build "A"

All good, all data still there.

The only thing encountered was that

I also had to delete

data/system/locksettings.db
[Moto G 2015 Android Development] MSe1969:
Thanks for the feedback - I've updated the post with the migration steps accordingly.
[Moto G 2015 Android Development] MSe1969:
EOL

Hi all,

in my LineageOS 16.0 thread for the Osprey device, I have now published new builds, which contain the July 2020 ASB patches.

Well, having . . .

. . . done so,

. . . noticed that there haven't been any additional questions or comments to the last LineageOS 14.1 builds for the Osprey,

. . . announced already before, that this thread is eventually coming to an end due to focusing now on LineageOS 16.0,

. . . posted here already all the necessary information on how to migrate to my LineageOS 16.0 builds (scroll up and you'll find everything),

. . . it is time now, to declare the official EOL of this thread!

As far as I can see, this is probably my last post in this thread.

Once again, many thanks for your interest and participation here, and I am looking forward to hopefully seeing you in my LineageOS 16.0 thread for the Osprey device

Bye, M.
[Moto G 2015 Android Development] Ectatomma:
Big thanks!

Hi M.

Fair enough! Thanks a lot for your hard work. I managed to keep my phone working, updated, useful, that means more sustainable. So I guess is time to upgrade!
[Moto G 2015 Android Development] MSe1969:
New build with May security patches

New build available for download (regular 'microG' build):

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

Security string 2018-05-05

Squid kernel r22c with few addl. ASB patches

Android System Webview M66

Regarding 'Substratum' - I haven't received any feedback regarding my recent test build, so I did not (yet) make a substratum-enabled build...
[Moto G 2015 Android Development] jemail:
Finally downloaded your OMS build. I can confirm it it is working, tested with Spectrum substratum theme.

ROM is working as expected so far.

I will definitely be using your ROM as my daily driver. This ROM is the best microg ROM currently available.

Can you compile an OMS build with the latest security patches?

Many thanks for your work.
[Moto G 2015 Android Development] MSe1969:
Here we go: https://www.androidfilehost.com/?fid=746163614322267110

Once I get confirmation/feedback, that all is OK, I'll also link it in the OP.
[Moto G 2015 Android Development] jemail:
The only problem is that some apps notify me that they require Google Services and to function Google services must be updated.

This is a microg issue that has been solved by a microg fork called Nogoolag. It is available on github.

Are you aware of this issue? While I can use the nogoolag version of microg, I do not know if it has the same security hardening features that your version has.

Will download new version and report back tomorrow. ?
[Moto G 2015 Android Development] MSe1969:
Yes, I know that some apps cause such issues right now, this has already been reported in several issues in microg at github, so waiting for the developers to fix it.

I include the microG binaries and apk's as prebuilts, the other security hardening features are code changes in various AOSP/LineageOS based repositories, so independent from microG.

Therefore, if you would like to flash the Nogoolag stuff over my build, that should be okay (I however prefer to stick to the "original" microG stuff in my build)
[Moto G 2015 Android Development] stonny20:
Sorry for asking what's the difference between microg and oms build?
[Moto G 2015 Android Development] MSe1969:
Oms build is the microG build with additional patches to support substratum (taken over Form LineageOMS in github)
[Moto G 2015 Android Development] jemail:
I have dirty flashed the latest OMS build you provided and have not encountered any problems so far.

I will be using your OMS microg builds as my daily driver.

Many thanks for providing an OMS microg build with the latest security updates.
[Moto G 2015 Android Development] justindanielfox:
Awesome ROM. Been my daily driver for at least a month. Google free is the way to be
[Moto G 2015 Android Development] shadowbone:
Hey, great job with the rom.

I have been testing for the past two days and so far so good. The OMS support makes it even more functional.

The only issue I have been facing is the occurrence of ghost touches. But I'm yet to confirm the culprit. Could be the overlay issue or some rogue xposed module I use.

But overall its a great work.

Thank you so much.
[Moto G 2015 Android Development] jemail:
Wasn't aware there was a choice of theme install methods. So I guess I used the default choice whatever that was. I don't recall any errors in log char. As spectrum has been updated when I redo the theme installation I'll see if both methods install and report back.

This ROM is my daily driver as it is very stable and reliable, haven't experienced any ghost touch problems so far.