yashsingh1/xdaforums huggingface dataset:
[Moto G 4G Android Development] MSe1969:
New builds with November 2019 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=4349826312261626203

B. Hardened build with pre-installed microG and F-Droid, patched for substratum

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

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

ASB Security string 2019-11-05

Bromite Webview on 78.0.3904.72 (variant B only)

microG GMS core updated to 0.2.9 (variant B 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 build variant B)

Happy flashing - regards, M.
[Moto G 4G Android Development] ChrisRM:
The Peregrine just keeps on going...

Another smooth update OTA, many thanks....
[Moto G 4G Android Development] ChrisRM:
Aurora store?

The Aurorastore app seems to be bogged down at the moment, with the Dev focussing on other matters. Are there any thoughts on alternatives for the B variant?
[Moto G 4G Android Development] MSe1969:
For me, AuroraStore 3.1.3 works fine under the following options with the following settings and options on SEVERAL devices (including my office Samsung phone with Stock ROM, where I have at least limited the Google spyware and deactivated the Google playstore to avoid the silent software updates and other silent actions happening in the background without my knowledge and control):

1. Use a gmail fake account, which you create for yourself (via web browser, you probably don't want to do that with a phone having Gapps, but that's up to you)

2. Make sure the chosen password has less than 12 characters

3. In settings, network in Aurorastore, use http://auroraoss.in:8080 as custom token dispenser

I have found this in the respective support thread on XDA, but in fact, this is the extract from the few useful posts there in-between the "spam-like" posts about the app not working together with all the connected "me too" posts.

Btw, I think that the dev IS working on a solution...
[Moto G 4G Android Development] ChrisRM:
That seems to work well, apps are now updating happily. Thanks for dredging this out of the dross on that thread; I did dip in and out of it but couldn't face reading my way through it...
[Moto G 4G Android Development] MSe1969:
New builds with December ASB are available for download:

A. Default LineageOS 14.1 with substratum and microG patch

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

B. Hardened build with pre-installed microG and F-Droid, patched for substratum

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

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

ASB Security string 2019-12-05

System Webview on 78.0.3904.96 (variant A only)

AuroraStore updated to 3.1.5 (variant B only)

Regards, M.
[Moto G 4G Android Development] ChrisRM:
Variant B just OTA'd, almost without noticing. How things should be...
[Moto G 4G Android Development] MSe1969:
New builds with January 2020 ASB patches

Hi all,

new builds ready for download - they will soon also be offered via OTA update:

A. Default LineageOS 14.1 with substratum and microG patch

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

B. Hardened build with pre-installed microG and F-Droid, patched for substratum

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

ASB Security string 2020-01-05

Standard flavor only: System Webview on 79.0.3945.116

microG flavor only: Bromite Webview on 79.0.3945.107

microG flavor only: AuroraStore updated to 3.1.5

microG flavor only: AuroraServices updated to 1.0.5

Regards, M.
[Moto G 4G Android Development] ChrisRM:
As Ryan Reynolds said in 'The Hitman's Bodyguard', "Boring is best.". OTA variant B just dropped in as usual.
[Moto G 4G Android Development] MSe1969:
New builds with February 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...0200207-UNOFFICIAL-oms-peregrine.zip/download

B. Hardened build with pre-installed microG and F-Droid, patched for substratum

https://sourceforge.net/projects/li...0206-UNOFFICIAL-mG-oms-peregrine.zip/download

ASB Security string 2020-02-01

Standard flavor only: System Webview on 79.0.3945.136

microG flavor only: Bromite Webview on 79.0.3945.139

microG flavor only: AuroraStore updated to 3.1.8

Cheers, M.
[Moto G 4G Android Development] MSe1969:
New builds with March 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...0200306-UNOFFICIAL-oms-peregrine.zip/download

ASB Security string 2020-03-05 (with kernel fixes)

System Webview on 80.0.3987.117

B. Hardened build with pre-installed microG and F-Droid, patched for substratum

https://sourceforge.net/projects/li...0305-UNOFFICIAL-mG-oms-peregrine.zip/download

ASB Security string 2020-03-05 (with kernel fixes)

Bromite Webview on 80.0.3987.117

AuroraStore updated to 3.2.0

Added Netguard app (F-Droid version!) to SELinux domain allowing to access /proc/net

Cheers, M.
[Moto G 4G Android Development] MSe1969:
New builds with April 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...0200410-UNOFFICIAL-oms-peregrine.zip/download

ASB Security string 2020-04-05

Fix for CVE-2020-8597 (external/ppp)

Kernel: CVE-2019-10638 siphash 128bit for IP generation *

System Webview on 80.0.3987.132

B. Hardened build with pre-installed microG and F-Droid, patched for substratum

https://sourceforge.net/projects/li...0409-UNOFFICIAL-mG-oms-peregrine.zip/download

ASB Security string 2020-04-05

Fix for CVE-2020-8597 (external/ppp)

Kernel: CVE-2019-10638 siphash 128bit for IP generation *

Bromite Webview on 81.0.4044.76

AuroraStore updated to 3.2.4

Cheers, M.

________________________________________

* Kernel is frequently updated every month, but this one I found worth mentioning
[Moto G 4G 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...0200507-UNOFFICIAL-oms-peregrine.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, patched for substratum

https://sourceforge.net/projects/li...0507-UNOFFICIAL-mG-oms-peregrine.zip/download

ASB Security string 2020-05-05

Bromite Webview on 81.0.4044.127

AuroraStore updated to 3.2.8

Cheers, M.
[Moto G 4G Android Development] phoenixmet:
Thaks for the updates :):good:
[Moto G 4G Android Development] Vuche:
Hello MSe1969,

Thank you so much for keeping our moto G alive!

I had some (a lot of, actually!) time available during the confinement that I used to play (aka update) with my old phones. I had your ROM installed on my G LTE for a few weeks now, using it as a hotspot and a home device. It's so nice to see that a 6 years old phone can still be used and updated nowadays, it's what the makers should do themselves, of course without getting the money from the new phones they could sell instead ;)

The only "issue" I have, not related to the ROM at all, is the lack of space with only 8GB of internal storage. I use the paid version of Link2SD to use storage space of the second partition of the SD card, but I think it's not maintained anymore and I get mounting errors at start up. I remember I used a starting script on my xperia ray a few years back that would switch the internal stogage with the external storage, very usefull when you had only less than 2GB internal storage!

If anyone knows of something similar working on our moto G, I would be very thankful for sharing it here, as I'm sure there are other people than me wanting to expend the memory a little.

Thanks again for you great work!
[Moto G 4G Android Development] jemail:
Look for a magisk module named fbind by developer VR25. Check the XDA magisk forum thread for fbind as I think it only installs with magisk 20.1, but you can then update magisk after fbind is installed.
[Moto G 4G Android Development] Vuche:
Ok, thanks a lot, I'll try this module. I didn't really understand all the instructions for setting things up, but I guess I'll get it when I'll be so far. I had my SD card second partition formated in ext3 for link2sd, but as I read in fbind thread, it has to be in ext4, right?
[Moto G 4G Android Development] jemail:
I have my sd card formatted as vfat by twrp and fbind works fine.

But I think if the read me says ext4 best to go with that.
[Moto G 4G Android Development] MSe1969:
New builds with June 2020 ASB

Hi all,

new builds are ready for download and also already offered for OTA update through the updater app:

A. Default LineageOS 14.1 with substratum and microG patch

https://sourceforge.net/projects/li...0200607-UNOFFICIAL-oms-peregrine.zip/download

Sec. string 2020-06-05

System Webview on 81.0.4044.138

B. Hardened build with pre-installed microG and F-Droid, patched for substratum

https://sourceforge.net/projects/li...0605-UNOFFICIAL-mG-oms-peregrine.zip/download

Sec. string 2020-06-05

Bromite Webview on 83.0.4103.76

Note:

This time, there haven't been any platform patches, as all published patches were already pushed by Google in a previous tag upstream and already back ported.
[Moto G 4G Android Development] xenox001:
Bootloop

[MENTION=7929484]MSe1969[/MENTION] Thank you for providing still updates for this old device. I used this ROM for half a year now whit minimal issues, like some random restarts of the phone. But yesterday it restarted it self and got stuck in a bootloop. And is not working any more. Is there anything that I can do to get it back to normal? I wiped already cache and dalvik, but the bootloop is still present.

Thanks in advance, xenox001
[Moto G 4G Android Development] MSe1969:
Well, difficult to "remotely diagnose". I know, difficult when having a boot loop, but are you still able to obtain a log?

If that's an option, the log could indicate the issue and thus there may be an option to fix the situation.

Another try could be to dirty flash the last ROM version again (worth a try, but almost sure it won't help).

Do you remember, what was happening / you were doing before the sudden restart (which indicates some sort of crash)?

What should work for sure, but you may not want that, is a factory reset. If you could live with that, this for sure is the easiest approach. And to be honest, also my recommendation: There are too many potential f*ups within the stored data in your /data partition after a crash leading to a reboot, and when my son had such an issue two and a half years back with his falcon device and end of last year with his osprey device, we eventually ended up doing so both times.

You could e.g. also first make a nandroid backup of your device in TWRP and then do a factory reset, just to confirm, that there is no hardware issue and then restore your backup to be again, where you are now...
[Moto G 4G Android Development] xenox001:
Are these the log files that are needed? I got them through TWRP.

dmesg.log (I omitted all the mtp release and open events)

<6>[ 8950.680261,0] Report pwrkey press event
<6>[ 8951.155007,0] Report pwrkey release event
<6>[ 8951.164667,0] mdss_dsi_on+: ctrl=e14b1010 ndx=0
<6>[ 8951.191265,0] mdss_dsi_on-:
<6>[ 8951.191310,0] mdss_dsi_panel_on+: ctrl=e14b1010 ndx=0
<6>[ 8951.389973,0] synaptics_dsx_sensor_state: state change SUSPEND -> ACTIVE
<6>[ 8951.390738,0] mdss_dsi_panel_on-. Pwr_mode(0x0A) = 0x9c
<6>[ 8951.508304,0] qcom,leds-qpnp leds-qpnp-e1e35400: backlight on
<5>[ 9038.737455,0] type=1400 audit(1594478063.724:172): avc: denied { write } for uid=0 pid=149 comm="recovery" name="0" dev="dm-0" ino=25 scontext=u:r:recovery:s0 tcontext=u:object_r:media_rw_data_file:s0 tclass=dir permissive=1
<5>[ 9038.737839,0] type=1400 audit(1594478063.724:173): avc: denied { add_name } for uid=0 pid=149 comm="recovery" name="recovery.log" scontext=u:r:recovery:s0 tcontext=u:object_r:media_rw_data_file:s0 tclass=dir permissive=1
<5>[ 9038.738221,0] type=1400 audit(1594478063.724:174): avc: denied { create } for uid=0 pid=149 comm="recovery" name="recovery.log" scontext=u:r:recovery:s0 tcontext=u:object_r:media_rw_data_file:s0 tclass=file permissive=1
<5>[ 9038.738866,0] type=1400 audit(1594478063.724:175): avc: denied { write } for uid=0 pid=149 comm="recovery" name="recovery.log" dev="dm-0" ino=38031 scontext=u:r:recovery:s0 tcontext=u:object_r:media_rw_data_file:s0 tclass=file permissive=1
<5>[ 9038.795954,0] type=1400 audit(1594478063.784:176): avc: denied { setattr } for uid=0 pid=149 comm="recovery" name="recovery.log" dev="dm-0" ino=38031 scontext=u:r:recovery:s0 tcontext=u:object_r:media_rw_data_file:s0 tclass=file permissive=1
<5>[ 9038.796394,0] type=1400 audit(1594478063.784:177): avc: denied { relabelfrom } for uid=0 pid=149 comm="recovery" name="recovery.log" dev="dm-0" ino=38031 scontext=u:r:recovery:s0 tcontext=u:object_r:media_rw_data_file:s0 tclass=file permissive=1
<5>[ 9038.796773,0] type=1400 audit(1594478063.784:178): avc: denied { relabelto } for uid=0 pid=149 comm="recovery" name="recovery.log" dev="dm-0" ino=38031 scontext=u:r:recovery:s0 tcontext=u:object_r:media_rw_data_file:s0 tclass=file permissive=1

I also had to shorten the recovery.log to post it. Because I am a new user I cant post the link directly. It is pastebin[dot]com[slash]bn3Caai6
[Moto G 4G Android Development] ensltr:
Hello MSe1969,

I've been using your room for almost a year now and it is the best but a few weeks ago I noticed the cell radio is turning off by itself and it refuses to come back on neither by the airplane mode toggle or by power cycling the device, it is only after many power cycles that it comes back on (so far it has been random), how can I help to debug this? When this condition happens the phone is not displaying "airplane mode" but whenever I try to make a call a pop up message tells me that I need to turn airplane mode off to make a call, if I try to scan for networks in network operator I instantaneously get "error while searching for networks" and also if I get in the testing menu (*#*#4636#*#*) I can read data from my SIM card and there is a IMEI and phone number listed but the Voice Service field is marked as Radio Off, also in the same testing menu the cellular radio power toggle is off and activating it makes no difference, same goes when cycling airplane mode, by the way the airplane mode switch in the power off menu sometimes shows a discrepancy (it is enabled but the system menu airplane mode toggle is disabled) and sometimes is grayed out. What is consistent is that whenever I power cycle the device the airplane mode switch in the power off menu is enabled but the phone is "not in airplane mode"
[Moto G 4G Android Development] MSe1969:
New builds with July 2020 ASB patches

Hi all, new builds are up with Sec. string 2020-07-12 - they will soon be offered as OTA, too:

A. Default LineageOS 14.1 with substratum and microG patch

https://sourceforge.net/projects/li...0200712-UNOFFICIAL-oms-peregrine.zip/download

B. Hardened build with pre-installed microG and F-Droid, patched for substratum

https://sourceforge.net/projects/li...0712-UNOFFICIAL-mG-oms-peregrine.zip/download

This build variant has in addition the following changes:

updated prebuilt microG GmsCore fom /e/ project to fix FCM registration issues

F-Droid updated to 1.8 / F-Droid privileged extension updated to 0.2.11

Aurorastore updated to 3.2.9 / AuroraServices updated to 1.0.6

Happy flashing!
[Moto G 4G Android Development] ChrisRM:
Smooth

Again, very smooth OTA for variant B with TWRP 3.3.0.0; many thanks!
[Moto G 4G Android Development] MSe1969:
Hi, sorry for my late reply - too busy with work related stuff and wanted to give priority to ship my build updates. Unfortunately, Pastebin now tells me "This page has been removed!" The snippet of the log, which you have pasted in your post seems to be from TWRP itself, rather than from the bootloop of the ROM. The SELinux denials deal with the recovery itself not being able to write the file "recovery.log" to the /sdcard (aka /storage/emulated/0/ ) directory, which is weird.

Question: Can you access the internal memory of your phone properly, when you have connected it via USB to your PC in TWRP ?

Maybe executing the option "Fix contexts" from TWRP's "Advanced" options is worth a try?
[Moto G 4G Android Development] MSe1969:
Hi, same as expressed in my previous post - sorry for delayed answer.

The most common reason for what you describe would be that the contacts to the SIM card are "worn" and there is a temporary loss of physical contact. But you confirmed that the contact and recognition of the SIM card is given. I have no good idea on how to debug - except for trying to grab a log, when that happens.

I have in fact two proposals (next to trying to grab a log, of course):

- Try it with a different SIM, so exclude (or confirm) some issue with the SIM (is your SIM worn or scratched a lot?) or also try to force the grip by using a piece of paper together with the SIM (but be careful!)

- Or there is a hardware issue with the modem . . .
[Moto G 4G Android Development] ensltr:
Thank you very much for the response,

Unfortunately the SIM port on that device past away after an empty SIM adapter got stuck in there and did some damage to the pins so no further test (that is worth the effort) is possible.
[Moto G 4G Android Development] MSe1969:
Yeah, that perfectly explains . . .
[Moto G 4G Android Development] ensltr:
The SIM port malfunction happened after the before-mentioned issues and it was an unrelated accident. I'm inclined to believe that the original problem was a modem ("hardware") issue.
[Moto G 4G Android Development] MSe1969:
OK, pitty your device is now scrapped...
[Moto G 4G Android Development] axde9:
Hello [MENTION=7929484]MSe1969[/MENTION], I have been using the variant b from past few weeks and recently it crashed. It boots to fastboot with message "Failed to Initialize partition..". I can access the device via fastboot but fastboot getvar cid shows "0XDEAD". After searching on forums, it is likely the device is hardbricked. I cannot also boot to twrp directly. Will it be possible to a host side boot like fastboot boot <kernel> <ramdisk>.
[Moto G 4G Android Development] MSe1969:
If the boot loader can't even access any partition, this doesn't look good... Booting the kernel via fastboot boot <boot.IMG> will probably result in the same error.

I am not really familiar with the 0xDEAD value, but as you searched already and it indicates a brick, I could think of the following:

- Try to flash the last official stock ROM by making use of the specific Moto flash tool for the respective ROM (search the net)

- If your hardware did not say "goodbye" to lead to the crash, this should normally also "low-level" repair your partitions

- Afterwards, flash LineageOS again

This approach is worth a try - but maybe you meanwhile found more info?

But as said, if this is because your hardware (e.g. flash memory) simply gave up, I am afraid there isn't much, which can be done.
[Moto G 4G Android Development] axde9:
Hi, I tried to flash last stock firmware but they it fails with mostly "Failed (remote error)" or "permission denied" messages. Since it only shows as fastboot device, I cant use adb shell either. I will check check on this as it would be interesting to know why it crashed other than hardware failure.
[Moto G 4G Android Development] MSe1969:
If the device always gets back to the boot loader, to which you can only talk through fastboot, there isn't really a lot of options. You can flash or wipe partitions (if the BL recognizes them, which seems not the case, as you describe), you can update the BL (if that fails, you have really irreversibly hard bricked your device), and you can also perform some "special" write operations. I don't remember, whether I had the very special issue some years back with my falcon or amami device, but I vaguely remember having had a similar issue like you, but with a very specific error. I found a weird command when looking for it, which made my device work again, and I think it was a fastboot command.

Maybe I have noted it somewhere... Will get back to you on that, but could be also something completely different...
[Moto G 4G Android Development] axde9:
this will be useful, thanks! I yesterday drained the battery and started charging using a wall charger. The device booted with lineageos like nothing happened. :confused: One thing I forgot to mention is that on fastboot it was showing "Device LOCKED STATUS: 0" even though I have unlocked the bootloader. I am not aware of the boot sequence after unlocking it so this could be some low level partition corruption as you mentioned. Since the device is back, should I try to do a clean install by flashing stock image first ?
[Moto G 4G Android Development] MSe1969:
If your device is back and you can do everything (I.e. no "funny" things, which weren't there before), I'd simply leave it and consider it a case of "weird sh*t happens sometimes".
[Moto G 4G Android Development] MSe1969:
New builds with August 2020 ASB patches

Hi all,

new builds are up with Sec. string 2020-08-05 and updated webviews to M84 - they will soon be offered as OTA, too:

A. Default LineageOS 14.1 with substratum and microG patch

https://sourceforge.net/projects/li...0200808-UNOFFICIAL-oms-peregrine.zip/download

B. Hardened build with pre-installed microG and F-Droid, patched for substratum

https://sourceforge.net/projects/li...0807-UNOFFICIAL-mG-oms-peregrine.zip/download

Happy flashing!

Regards, M.
[Moto G 4G Android Development] galoneta:
Dear MSe1969, thanks for your updated ROM!
[Moto G 4G Android Development] MSe1969:
New builds with September 2020 ASB patches

Hi all,

new builds are up with Sec. string 2020-09-05 and updated webviews to M85 - they will soon be offered as OTA, too:

A. Default LineageOS 14.1 with substratum and microG patch

https://sourceforge.net/projects/li...0200913-UNOFFICIAL-oms-peregrine.zip/download

B. Hardened build with pre-installed microG and F-Droid, patched for substratum

https://sourceforge.net/projects/li...0912-UNOFFICIAL-mG-oms-peregrine.zip/download

Happy flashing!

Regards, M.
[Moto G 4G Android Development] MSe1969:
microG: Exposure Notification API for "Corona apps"

Hi all,

below is applicable for the "microG" build variant (B):

microG has published an implementation of the "Exposure Notification API" in tag v0.2.12.203315.

So it should now be possible to run "Corona apps", which are designed to make use of Google's Exposure Notification API, with this build, too.

I have created a test build containing this version, the test build can be downloaded and (dirty-)flashed manually here, for interested people:

https://sourceforge.net/projects/li...0918-UNOFFICIAL-mG-oms-peregrine.zip/download

This will become part of the next regular build onwards. Feedback welcome (I obviously can't help with any EN API issues, that would find its way into microG through the microG project, but a general feedback and also feedback concerning the overall microG functionality is welcome, there may be e.g. some useful patches in the e.OS fork, which haven't yet found their way into the mainline...)

Regards, M.