yashsingh1/xdaforums huggingface dataset:
[Moto G 2015 Android Development] MSe1969:
New August 2019 builds available

Hi,

new builds are available for download:

A. Default LineageOS 14.1 with substratum and microG patch

https://androidfilehost.com/?fid=6006931924117934977

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

https://androidfilehost.com/?fid=6006931924117934978

C. Above hardened microG build with substratum patch

https://androidfilehost.com/?fid=6006931924117934979

ASB August 2019, security string 2019-08-01

July Kernel patches included in this build

Additional patches from AOSP branch 'nougat-mr2-security-release'

OTA Support (see below)

variants B,C only: Bromite Webview on 76.0.3809.100

variants B,C only: Aurorastore 3.0.9 with AuroraServices install method (see below)

OTA support

This build update brings back the LineageOS Updater app. Any further updates of this build will appear in the updater app and you can download them within your phone, i.e. no need to manually flash.

Please note:

- Of course, you are free to continue to flash the build manually as before, it is an additional option.

- You still have to flash this update manually, as before, otherwise you won't find the Updater (Settings - System - about phone - LineageOS Updates)

- The updater will propose newer builds, it will obviously not propose this update, so "no new updates found" is the expected result, if you call the updater after flashing.

AuroraStore update (variants B,C only)

Aurorastore in version 3.0.9 now brings a new app installation method called "AuroraServices". Please perform the following steps after updating:

- Launch the "AuroraServices" app, which you'll find in the app overview and grant the storage permission, afterwards, you may close the app

- Launch AuroraStore, go to Settings - Installations - Installation method and choose "AuroraServices"

Happy flashing,

Regards M.
[Moto G 2015 Android Development] MSe1969:
Situation unchanged - can't really test (that is also the reason, why I only publish the -01 patch level, as kernel patches will always be with one month delay; e.g. this month's update has last months kernel patches, which justifies only the 2019-08-01 patch level) therefore, until further notice, no progress with LineageOS 15.1 - the last test build e.g. had a non-working Camera / missing camera app, was e.g. reported as feedback. I can't really work on any reported feedback, as I don't have the device right now . . .
[Moto G 2015 Android Development] NewUser012345:
Hi

I have Installed lineage-14.1-20190810-UNOFFICIAL-oms-osprey.zip over the older version with twrp without any problems! :) Even Magisk still works. :good:

THX
[Moto G 2015 Android Development] sponk0:
I also recently installed the August 10 version (clean install). Everything seems to be working great so far.

Note: my osprey is currently running as wifi-only device (no sim-card installed), as I switched to another phone as primary device a while ago, so I can't tell if calls and mobile data are working.

Thank you very much!
[Moto G 2015 Android Development] alanthelinuxguy:
I was looking for a Custom ROM for the Moto G3 that would offer regular security patches and yours seems to be one of the very such ROM's to do so. The ROM installed fine and, although I have only been using it for a few days, it seems to work extremely well. So, many thanks for your past - and future - work on this ROM.

However, I had one bizarre (to me) occurrence when I used the Clock app's timer. This used the Rooster Alarm by default and, while I could tell it to change the sound file, the **** continued to crow whatever the setting! My solution was to install Google's current Clock app from the Play Store. This app worked as expected, such that I could change the alarm sound, and so resolve my problem.

However, one thing I don't understand and, no doubt, you can set me straight. Your instructions seem to suggest that the ROM comes with microG enabled, but micro-Gapps are not installed by default, and require flashing separately from the Custom ROM. In my case, I flashed pico-Gapps as I wanted to minimize the amount of internal memory used. But, while the Gapps wiki suggests that the clock app isn't included with pico-Gapps (but is a part of micro-Gapps), my resulting system did have a Google clock app installed. It turned out to be Version 4.5.0 (with the "defective" rooster) while the updated version in the Play Store was Version 6.2.

So, where does the Clock app come from - "your" microG, or OpenGapps (pico-Gapps)?

Note, that I'm not complaining. This is just a question to further my understanding of custom ROM's and their associated software.

Alan
[Moto G 2015 Android Development] XDrive10:
Dude, microG isn't an GApps package, it's just a patch for those who don't want to use any Google App or Service

About the alarm, i don't have an osprey to replicate that issue, but try to change default alarm sound through Settings>Sounds or moving a custom sound file to Internal Storage/Alarms and try to test if it works

Hope it helped :D
[Moto G 2015 Android Development] MSe1969:
As already outlined by [MENTION=9083491]XDrive10[/MENTION] , the variant A is only patched for the use of microG, you have three choices, which you can't combine obviously:

a. Flash Gapps (from opengapps.org) - in that case, the microG patch has no meaning or effect (you did that already)

b. Install microG as regular user apps (see microg.org for more info)

c. None of the above

The clock app is pre-installed from LineageOS. Can't really reproduce your issue, however - as you can see, when you scroll through this thread, I don't have the device around anymore all the time. However, when it used to be my daily driver until June 2018, I could use whatever sound I wanted. And the clock app didn't have any recent changes (except for language translations).
[Moto G 2015 Android Development] alanthelinuxguy:
Thanks to you and [MENTION=9083491]XDrive10[/MENTION] for clarifying for me the nature of microG.

With regard to the clock/timer issue, I went back and installed just your LineageOS 14.1 file without pico-Gapps. The timer in the clock app says (in Settings) that it is using the Hassium alarm by default but it is the Rooster Alarm that actually sounds. And, as I noted previously, I was unable to change the alarm to use a different sound file. Whatever sound I choose, it's the rooster that is played. This isn't really a problem since, having flashed pico-Gapps, I can install an updated clock app which does allow the alarm sound to be modified. I merely mention this as an oddity that I came across with your custom ROM.

Otherwise, your ROM is working just fine, and I'm looking forward to the September security patches.

Alan
[Moto G 2015 Android Development] MSe1969:
New builds with September ASB

Hi all, new builds with September 2019 ASB available for download (sec. string 2019-09-01).

They will later today (or tomorrow) also be available through the OTA Updater app.

A. Standard build flavor with substratum patch

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

B. hardened microG build flavor

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

C. hardened microG build flavor with Substratum patch

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

Happy flashing - regards, M.
[Moto G 2015 Android Development] alanthelinuxguy:
M:

I received the September 9, 2019 OTA update today. The installation process worked flawlessly and all systems (that I have used so far, including E-mail, browser and camera) are working normally. Many thanks for the prompt security patch.

Alan
[Moto G 2015 Android Development] sponk0:
same here. Installed fine, so far no problems found. Thanks a lot :)
[Moto G 2015 Android Development] liliki:
I started using this great ROM about a week ago. Amazing! Seamless and no bugs so far! Thanks so much for your work.

I use Exchange Services to access my work email and calendar. Unfortunately Exchange Services forces me to grant my work (a large university) Device Administrator access to my phone.

Among other nasties this allows them to remotely wipe it. Obviously as someone using a hardened ROM with microG I don't like this!

Would you consider adding these two patches to the hardened build?

https://github.com/Rawi666/android_...mmit/fe78d598bb74c76512e21bdbc6f58e43fffdf411

https://github.com/Rawi666/android_...mmit/7d7a8c067982e8b336208fd52c3f655a42b139f7

They come from here, where other people have been bypassing this somewhat ridiculous security risk: https://xdaforums.com/showpost.php?p=75687333&postcount=1315

Thanks again for the great ROM!
[Moto G 2015 Android Development] MSe1969:
Thanks for the positive feedback.

In regards to modifying the e-mail and exchange app, I am not sure whether to follow that approach, yet.

You have those modified apps ready to flash and you can also easily put a "survival script" into /system/addon.d to automatically re-flash them in each update, which will provide a workable solution for you.
[Moto G 2015 Android Development] KamiOh:
Hi.

I installed this rom.

lineage-14.1-20190908-UNOFFICIAL-microG-osprey.zip

Use magisk to do the safetynet test

At first I couldn't do it, a message appeared:

"Safetynet error api".

Look for information and solve it.

settings migroG > google safety>enable> advanced> use official server.

I'll do the test again in the magisk

ctsProfile: false

basicIntegrity: false

Then I went back to look for info on the internet.

I installed modules for magisk.

MicroG Installer. not work

I installed microG DroidGuard helper. not work

I try his video tutorial. not work

https://www.youtube.com/watch?v=xY3GiTv3CV8

Any solution to pass "safetynet" or it is not possible using rom with "microg"? :confused:

Sorry for my English, I'm using translator.
[Moto G 2015 Android Development] MSe1969:
Hi, after an update of the safety net binary by Google around four months ago, safety net fails right now in conjunction with microG, see here:

https://github.com/microg/android_packages_apps_RemoteDroidGuard/issues/24

Let's hope the microG folks find a solution eventually. For what do you need SN?

Regards, M.
[Moto G 2015 Android Development] KamiOh:
Thank you very much for your answer.

I understand, we will have to wait for a solution.

I want to play and I understand that some applications ask you for safetynet.

As well as bank applications to make transfers.

In itself, it is not a priority for me, but I would have liked it to pass safetynet.

Thanks again for responding.

Good day.
[Moto G 2015 Android Development] MSe1969:
New builds available with October 2019 ASB

Hi all,

new builds area available for download with ASB Security string 2019-10-01.

Soon, the updater app will also offer OTA updates (if you are on the August or September build).

A. Default LineageOS 14.1 with substratum and microG patch

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

- System Webview on 77.0.3865.116

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

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

- Bromite Webview on 77.0.3865.104

- Aurorastore 3.1.3 with AuroraServices 1.0.4

C. Hardened microG build with substratum patch

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

- Bromite Webview on 77.0.3865.104

- Aurorastore 3.1.3 with AuroraServices 1.0.4

Happy flashing, regards M.
[Moto G 2015 Android Development] alanthelinuxguy:
October Update

[/COLOR]

This month's update was downloaded this morning. The installation was straightforward. The system seems to be working as usual. Many thanks for keeping this package up to date! :o

Alan
[Moto G 2015 Android Development] sponk0:
Same here, update installed via OTA, went smoothly, everything is looking good.

Thanks very much!
[Moto G 2015 Android Development] MSe1969:
New releases with November ASB patches

Hi all,

new builds with November ASB is available for download:

A. Default LineageOS 14.1 with substratum and microG patch

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

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

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

C. Above hardened microG build with substratum patch

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

(They will soon be also shown in the Updater app for OTA update, if you have the August, September or October build installed.)

ASB Security string 2019-11-01 (as usual, kernel updated from previous month are included)

microG GMS core updated to 0.2.9.x (a patch-release containing the fix of the location provider issue, which occurred to the 1st 0.2.9.x release) - Variants B and C only

Bromite Webview on 78.0.3904.72 - Variants B and C only

In regards to Aurorastore: Right now, the anonymous logins don't work, see the respective support thread.

(This is however not directly related to this build, but simply a heads-up, because I include this app in my builds, variants B and C)

Happy flashing - regards, M.
[Moto G 2015 Android Development] sponk0:
Just installed via OTA. Everything went smoothly, so far all good. Thank you very much for keeping this ROM alive
[Moto G 2015 Android Development] frenchiveruti:
No signal on SIM Card in argentina.

A. Default LineageOS 14.1 with substratum and microG patch

I've downloaded this version, as soon as everything worked, I installed my SIM card into the phone, and the thing doesn't recognize any antenna, nor signal of any kind. I'm from argentina and I'm using a Claro SIM card.

This phone was in use with AOSPextended 7.1.2 until i flashed into your rom, and I just simply installed your ROM using TWRP, and then flashed "OpenGApps nano" package, again using TWRP.

The phone now is not a phone but a rather nice smart brick, the OS boots up fine and everything but it doesn't recognize the SIM card.

Anything I've done wrong?
[Moto G 2015 Android Development] MSe1969:
First question: Since you came from a different ROM, did you clean flash? I.e. you have performed a wipe? Or did you simply flash this ROM over your existing ROM without factory reset / purging data? If the latter, please boot into TWRP and perform a wipe of /system, /data and cache and then flash the ROM again.

2nd question: Did you flash any other things on top? Like custom kernel or firmware?

3rd question: Assuming question #1's answer is "clean flash", and #2 is " no", what exactly is the technical name of your device? (XT number from Motorola)?

EDIT: Oh, last but not least - I hope you did not wipe too much using TWRP, like the modem? I don't remember right now what options TWRP offers to wipe, but if you did also wipe the modem, then that is the result...

Sorry if my questions seem to imply you may have done something stupid, but when looking for the solution, all those things need to be considered.
[Moto G 2015 Android Development] frenchiveruti:
Hello, thanks for the quick reply, I did a clean flash using solely TWRP, which offers Dalvik, data, system, and another one that right now I can't remember.

The phone was not picking up cellular data, and I didn't tamper with modem or anything, but I do recall something coming up in the TWRP screen when the ROM zip was flashing.

But, to keep you at ease and not to worry, I did the process again, installing the ROM and the phone picks up cellular data with the same SIM that was in it.

The only thing I did different this time was wiping the Dalvik cache twice or thrice I don't remmeber, but it was for good measure, and the phone decided to recognize the SIM.

Thanks! Sorry for the worries haha.

I like that you keep this ROM updated.
[Moto G 2015 Android Development] frenchiveruti:
Hello I come again to tell you that as soon as the phone drops off a cellular network, it never picks up signal again, making it quite a hassle because where I live we don't really have good mobile companies and the signal is awful in half of the places where I move around.

Is there any "fixes" I can do without necessarily switching ROMS or anything?

I still don't know the specific "XT1542" model of the phone because I can't find that information anywhere, you changed the default name of the bluetooth so it also doesn't show on there.

Anyways, I hope I can still use yours because the newer version of ROMs that are around here are quite heavier and this phone in particular is an 8GB version.

EDIT: decided to check inside the phone and there it was, XT1542

Now, I'm going to try to revert to stock ROM, and then installing yours again, and we'll see.

Well, everything failed horribly: https://xdaforums.com/2015-moto-g/help/help-phone-pick-cellular-signal-phone-t4009665
[Moto G 2015 Android Development] alanthelinuxguy:
Have been away for a few days but have now downloaded and installed the November update. Works just fine. Many thanks once again.

Alan
[Moto G 2015 Android Development] MSe1969:
Not sure what to suggest... Maybe find XT1542 modem/baseband image file and try flashing via fastboot (be careful! This may completely brick the device, if you use wrong file - never had such issue before) - or hardware issue?
[Moto G 2015 Android Development] Jhoner:
Youtube Vanced doesn't work in this rpm

---------- Post added at 05:18 PM ---------- Previous post was at 05:18 PM ----------

Youtube Vanced doesn't work in this ROM
[Moto G 2015 Android Development] MSe1969:
YT vanced is a "patched" genuine Google YT app. As such, it needs - as far as I know - the genuine Google spy services. Hence, as long as you use build flavors B or C, it won't work most probably. You most probably need then flavor/build variant A with Gapps flashed.

If you use already A, I don't have a solution.

In general, I recommend e.g. NewPipe as YT app, it does not need any G* spyware to run and offers more than the genuine YT app.
[Moto G 2015 Android Development] MSe1969:
New builds with December 2019 ASB patches

New builds with December ASB are available for download:

A. Default LineageOS 14.1 with substratum and microG patch

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

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

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

C. Above hardened microG build with substratum patch

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

ASB Security string 2019-12-01

System Webview on 78.0.3904.108 (Build Variant A)

Bromite Webview on 78.0.3904.119 (Build variants B and C)

Updated AuroraStore 3.1.5 (Build variants B and C)

It will also be shown soon in the Updater app for OTA update, if you have at least August 2019 build installed.

Regards, M.
[Moto G 2015 Android Development] alanthelinuxguy:
Update downloaded and installed. No issues. Many thanks. Alan
[Moto G 2015 Android Development] UtkKing:
Why should we not wipe Internal?

Because I always used to wipe internal storage as well everytime while flashing a new rom.. :confused:
[Moto G 2015 Android Development] MSe1969:
If you wipe Internal, all individual files (e.g. pictures, photos, music files, etc.), which you have stored on your device, will be deleted.

This is not necessary, when you want to flash a ROM and basically, this advice is to prevent people from doing that by accident. Further, if you have no SD card, Internal is the only place to store the ZIP file, which you are going to flash.

If you are aware of this, know what you are doing, and don't care to loose those files (or have made a backup before, to restore some of them later), and put the ZIP to flash on the external SD, by all means: go ahead and wipe Internal, if you prefer doing so.
[Moto G 2015 Android Development] Dr4k05:
Hi.

First, I wanted to thank you for keeping our devices up to date with the latest security patches, keep up with the good work!

Second, I have a question: does encryption work properly? Sorry if its a dumb or obvious question, but yesterday I tried to encrypt my device (variant C, December 2019), and it kept showing the LineageOS logo for approximately four hours. At the end I decided to shut it down, and obviously when I turned it back on my data was corrupted and I got the "Decryption unsuccessful" message. I had to wipe and flash everything again. I'm using variant B at the moment.

Thanks.
[Moto G 2015 Android Development] MSe1969:
Hi, I am not aware of any encryption problems. When the osprey used to be my daily driver, it was encrypted. Right now (as mentioned earlier in this thread), my son uses this device (still encrypted).

Hence I can't format its data partition and retry to encrypt (to test).

Which version of TWRP do you use?
[Moto G 2015 Android Development] Dr4k05:
I'm using TWRP 3.2.1-r1 from squid2. I searched a bit and found that there are newer versions, do you think it has anything to do with that?
[Moto G 2015 Android Development] rori1977:
Bluetooth name resolution not working

Hi and thanks for this usefull piece of software, which works great for me with only one exception:

Bluetooth only displays the MAC adresses of neighbor-devices. The human readable names of the devices discovered do not appear for me when scanning for new Bluetooth devices.

This makes it difficult to identify the correct device to connect to.

Anyone else having this issue as well?
[Moto G 2015 Android Development] MSe1969:
Should be fine (sometimes the newest TWRP aren't good for old Android versions, 3.2 should be fine though) - in my falcon thread, one encryption issue was reported "solved" after downgrading TWRP from 3.3 to 3.2, but that does not apply here.

Have you maybe formatted the data partition with a "non-default" format?

Maybe anyhow try another TWRP?
[Moto G 2015 Android Development] TheForce:
In the november version of the A-rom-version the names are readable.
[Moto G 2015 Android Development] MSe1969:
New builds with January 2020 ASB patches

Hi all,

new builds are ready for download - as usual, they will soon be offered also in the updater app:

A. Default LineageOS 14.1 with substratum and microG patch

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

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

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

C. Above hardened microG build with substratum patch

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

ASB Security string 2020-01-01

System Webview on 79.0.3945.116 (Build Variant A)

Bromite Webview on 79.0.3945.107 (Build variants B and C)

Updated AuroraStore 3.1.7 (Build variants B and C)

Updated AuroraServices 1.0.5 (Build variants B and C)

Regards, M.
[Moto G 2015 Android Development] alanthelinuxguy:
Latest release (January, 2020) installs flawlessly - as usual! Many thanks. Alan
[Moto G 2015 Android Development] Lefl:
Thank you so much! You're keeping this great phone going!
[Moto G 2015 Android Development] Néocray:
Hello. Thanks for MSe1969's steady support for this device, it's always nice!

For the story, my daily phone is a Samsung S5 4G+, and it runs great with a RR build with great support from one of your fellow countrywomen. So I'm happy to find an other steady developper here.

I'm looking for a new ROM for an Osprey, having troubles with latest RR 16.0 build, and have a few questions.

Are they plans to move to newer Android version? Is there any reason to stick with LOS 14.1 on Osprey? From my experience, I didn't get better stability and battery life with Nougat than Pie, but I could be wrong…
[Moto G 2015 Android Development] kirans:
First of all thanks for keeping the MotoG alive. I happened to stumble upon this thread, which helps breathe life again to my trusty MotoG. I have used the latest version to install , no issues seen during installation, but I am unable to play any MP3 files. Have I missed anything, or do I need to do anything to enable MP3 playback.

Thank you so much for your work!
[Moto G 2015 Android Development] sponk0:
Thanks to [MENTION=7929484]MSe1969[/MENTION] as well for keeping this device alive. Installation went smoothly as usual (OTA; version A). So far, no bugs or regressions found :good:

mp3-playback seems to work fine on my device (XT1541; tested with "AIMP" player), so it might be a problem specific to your installation.
[Moto G 2015 Android Development] Néocray:
Well, I tried to clean install (prior wipe system, data, cache and dalvik) either version A or C, resulting in no boot. The phone stays on boot animation…