[ROM][LineageOS 14.1][substratum] for Moto G LTE [peregrine]

[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.

 

[galoneta]

Dear MSe1969, thanks for your updated ROM!

 

[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.

 

[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.

 

[admkx]

Hey M, I clean flashed the latest build of this ROM a few weeks ago and didn't touch the phone since. Last week, I took a bunch of important photos with the default camera app to internal storage, put the phone away (connected to Wifi) and now went to transfer them to my PC and they're all gone. There's 1 JPG file of ~150 left and it's corrupted. Do you have any idea what could have happened?

 

[MSe1969]

Hey M, I clean flashed the latest build of this ROM a few weeks ago and didn't touch the phone since. Last week, I took a bunch of important photos with the default camera app to internal storage, put the phone away (connected to Wifi) and now went to transfer them to my PC and they're all gone. There's 1 JPG file of ~150 left and it's corrupted. Do you have any idea what could have happened?

No idea, that sounds weird.
Spontaneously, the only things I could think of are:
- Have you tried rebooting, just to be sure?
- If you reboot to recovery and use the internal file manager of TWRP, is it the same or can you see the files then?
- Your hardware / internal storage (hence your device) is damaged (can you normally access? Store files, edit files etc)
- Maybe you have some rogue app on your phone?

 

[admkx]

No idea, that sounds weird.
Spontaneously, the only things I could think of are:
- Have you tried rebooting, just to be sure?
- If you reboot to recovery and use the internal file manager of TWRP, is it the same or can you see the files then?
- Your hardware / internal storage (hence your device) is damaged (can you normally access? Store files, edit files etc)
- Maybe you have some rogue app on your phone?

Hey M, yes I rebooted and tried with TWRP - no luck. It was a clean install of this ROM (actually version 20200712), so any rogue apps must have been included. I can only hope something was damaged?

 

[MSe1969]

Hey M, yes I rebooted and tried with TWRP - no luck. It was a clean install of this ROM (actually version 20200712), so any rogue apps must have been included. I can only hope something was damaged?

Then I am afraid it could be your hardware - but as said, this is really weird...

 

[ChrisRM]

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.

This is looking good but Google Maps is protesting about needing Play Services updated; I should find a different mapping tool, perhaps?

 

[MSe1969]

This is looking good but Google Maps is protesting about needing Play Services updated; I should find a different mapping tool, perhaps?

A good alternative would be OsmAnd~
In regards to Maps, same as with other apps directly coming from Google, it is unfortunately not guaranteed that they always run fine with microG . . .
Did you recently upgrade the Maps app ?

 

[admkx]

Then I am afraid it could be your hardware - but as said, this is really weird...

They were sensitive document photos with a lot of PII, as my regular phone had a broken camera. I used the default camera app and internal memory. Before taking the photos, I accidentally dropped the phone from about 1m, and after kept it in my pocket. It's still weird though.

My theory is, if there was nefarious activity from sketchy code (Aurora, F-Droid, ???), the culprit would leave the files so as not to arouse suspicion?

So, hopefully it was just some kind of bug with the camera app or a hardware error or something. It's not the first time people have lost photos. I guess I learned my lesson to use a traditional camera for such things.

Regardless, thank you for your work on this ROM. It's been great otherwise apart from this weird issue. I wonder if anyone else brings it up.

 

[ChrisRM]

A good alternative would be OsmAnd~
In regards to Maps, same as with other apps directly coming from Google, it is unfortunately not guaranteed that they always run fine with microG . . .
Did you recently upgrade the Maps app ?

No, due to my falcon becoming less predictable, I moved over to a spare peregrine I was bequeathed and am facing bringing that up to the same usefulness as the falcon. That's why the question, not that G Maps has been updated or changed, simply installed and found not to work...

 

[MSe1969]

No, due to my falcon becoming less predictable, I moved over to a spare peregrine I was bequeathed and am facing bringing that up to the same usefulness as the falcon. That's why the question, not that G Maps has been updated or changed, simply installed and found not to work...

In fact, background of my update question was, whether it was the newest maps version and it is, because you've freshly installed - maybe the version on your falcon wasn't the (meanwhile) newest, and that one still worked with microG...

 

[MSe1969]

They were sensitive document photos with a lot of PII, as my regular phone had a broken camera. I used the default camera app and internal memory. Before taking the photos, I accidentally dropped the phone from about 1m, and after kept it in my pocket. It's still weird though.

My theory is, if there was nefarious activity from sketchy code (Aurora, F-Droid, ???), the culprit would leave the files so as not to arouse suspicion?

So, hopefully it was just some kind of bug with the camera app or a hardware error or something. It's not the first time people have lost photos. I guess I learned my lesson to use a traditional camera for such things.

Regardless, thank you for your work on this ROM. It's been great otherwise apart from this weird issue. I wonder if anyone else brings it up.

If it was a fresh install, as you tell, there are no "questionable" apps shipped along with my build!
So far, nobody has brought up such an issue - the only thing, I am investigating right now, is, that rarely, WiFi drops after a while (falcon and peregrine) and requires a restart.
So if we also leave out the theoretical possibility of any "targeted" attack to YOUR individual device (let's not develop any paranoia, usually there always is a simple explanation for anything ), and we also leave out the possibility of anybody having physically accessed your device, while it was unattended, the remaining option would be a HW defect...

 

[admkx]

If it was a fresh install, as you tell, there are no "questionable" apps shipped along with my build!
So far, nobody has brought up such an issue - the only thing, I am investigating right now, is, that rarely, WiFi drops after a while (falcon and peregrine) and requires a restart.
So if we also leave out the theoretical possibility of any "targeted" attack to YOUR individual device (let's not develop any paranoia, usually there always is a simple explanation for anything ), and we also leave out the possibility of anybody having physically accessed your device, while it was unattended, the remaining option would be a HW defect...

Thanks for following up M.

You seem legit I'm not interesting enough to be targeted, I think, and if I was, the attacker would have left the files so as not to arouse suspicion. The device was physically secured the entire time, so we can probably just chalk it up to a hardware fault - which is rare but not unheard of - likely due to mechanical abuse (dropping it, pocketing it, etc.) around the time of shooting the photos, or it just being old.

Thanks again for your great work and communication

 

[Irish_Dude]

Absolutely brilliant ROM.

Running flawlessly on my Moto G

Is there anyway to root this ROM?

Would love to install AFwall+ but it requires root

Thank you so much Dev

 

[MSe1969]

Absolutely brilliant ROM.

Running flawlessly on my Moto G

Is there anyway to root this ROM?

Would love to install AFwall+ but it requires root

Thank you so much Dev

Thanks for the positive feedback - regarding root, see post #3 in this thread.

 

[MSe1969]

New builds with October ASB

Hi all,
new builds are available for download and will soon be offered as well via OTA update:

A. Default LineageOS 14.1 with substratum and microG patch
https://sourceforge.net/projects/li...0201010-UNOFFICIAL-oms-peregrine.zip/download

• ASB Security string 2020-10-05
• Updated TimeService.apk (explanation below)

B. Hardened build with pre-installed microG and F-Droid, patched for substratum
https://sourceforge.net/projects/li...1009-UNOFFICIAL-mG-oms-peregrine.zip/download

• ASB Security string 2020-10-05
• Updated TimeService.apk (explanation below)
• Bromite Webview on 86.0.4240.73
• updated microG with included Exposure notification API (for Covid tracing apps - see below)

Updated TimeService.apk
System time is now also synchronized via WiFi network (if no SIM card is present).
This helps also to improve the situation, if idle WiFi connections drop after a while

microG with included Exposure notification API
microG now contains an open-source implementation of Google's Exposure notification API, which is used by many Covid tracing apps.
Please make sure to re-enable your configured coarse location providers in the microG settings as a one-time activity after the upgrade.

Happy flashing!
Regards, M.

 

[MSe1969]

Update of EMail app (fix widget issue)

Hi all,

for those of you interested, who do not want for the next build :
I have created a flashable zip with the update of the AOSP E-Mail app to fix the widget issue described in this post

Happy flashing - regards, M.

 

[MSe1969]

microG interim update

Hi all,

the below applies only to users of the build variant B:

An interim update of microG GmsCore is available for download here as flashable ZIP:
https://sourceforge.net/projects/li...s/microG-Update-20201017-testkey.zip/download

The apk has been built from the microG source.
Please only use for the build variant B of this ROM (peregrine) or the falcon ROM from this thread


This update contains the following fixes:

• GCM sign-in issues
• Mapbox issues
• Various improvements of the exposure notification API

There is currently no official new version of microG, but due to some issues, which I have experienced myself in regards to the Covid tracing app and GCM sign-in and which were fully solved after applying the update, I wanted to offer it for those of you, who are interested. To update, simply download the linked ZIP file and flash via TWRP (disable ZIP signature verification).

Important hints:

1. One of the possible issues with the EN API is an incredible growth of the database and thus, the space used by the microG app (the respective Covid tracing app may also start to behave weird due to that). If you get the system message, that memory is becoming short, don't delete the app data of microG - the EN-DB will properly reorganize after flashing the update
2. The UI has been re-shaped internally. If you start the microG UI and what you see looks "weird" (e.g. Exposure notifications API now shown, or device registration and GCM looking "disabled"), don't panic and DON'T change any settings. Instead, please go to Settings - apps, pick the microG GMS Core app and purge the app's cache (only the cache, and not the app data!) - Afterwards, all will be fine.

Regards, M.