Database Develop

Build G960FXXS1ARD1 has been released! (April security patch)

It seems a new build has been pushed to Germany, on April the 17th. Other unlocked phones should follow in the next days. The OTA update size is a little over 60MB.
https://www.sammobile.com/firmwares/SM-G960F/DBT/download/G960FXXS1ARD1/215642/
Model: SM-G960F
Changelist: 13138374
Build date: Tue, 10 Apr 2018 01:48:02 +0000
Security patch level: 2018-04-01
Product code: DBT
PDA: G960FXXS1ARD1
CSC: G960FOXM1ARCA
Click to expand...
Click to collapse
Only security patches this time around, according to Samsung, unlike the older builds which featured stability improvements (camera, call, face unlock): http://doc.samsungmobile.com/SM-G960F/DBT/doc.html
Build number: G960FXXS1ARD1
Android version: Oreo (Android 8.0.0)
Release date: 2018-04-17
· The security of your device has been improved.
Click to expand...
Click to collapse
I'll try to announce every new firmware version, as it becomes available, from now on.
:highfive:

Build G960FXXU2BRG6 has been released! (July security patches + general fixes)

This build was released today, July 18th, in India. The OTA size is around 250MB.
Links for the firmware release can be found here: https://www.sammobile.com/firmwares/galaxy-s9/SM-G960F/INS/download/G960FXXU2BRG6/225558/
Model name: SM-G960F
Changelist: 13951170
Build date: Thu, 12 Jul 2018 09:06:21 +0000
Security Patch Level: 2018-07-01
Product code: INS
PDA: G960FXXU2BRG6
CSC: G960FOXM2BRG4
Click to expand...
Click to collapse
The build features security patches + fixes related to AR Emoji and Super Slow Recording: http://doc.samsungmobile.com/SM-G960F/DBT/doc.html
Build Number: G960FXXU2BRG6
Android version: Oreo (Android 8.0.0)
Release Date: 2018-07-18
· The stability of AR EMOJI has been improved;
· The stability of Super slow has been improved;
· The stability of Device has been improved;
· The security of your device has been improved.
Click to expand...
Click to collapse

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

Hi,
this is my unofficial LineageOS 14.1 build for the Moto G LTE (peregrine) device with current security patches, microG patch and substratum support.
As announced here, LineageOS has discontinued to deliver official 14.1 builds in the course of providing LineageOS 16.0 builds, but the 14.1 tree will continue to be maintained for security patches by the community (I am one of these contibutors, btw). So this build will continue.
As the pregerine and the falcon device belong to the same device family and share the same kernel, the build is in fact very similar to my 'falcon' builds, so you may also want to browse in my XDA falcon thread to obtain further information.
The build has got the following features:
LineageOS 14.1 with current security patches (from official LineageOS repositories)
Security string 2021-06-05, AOSP tag 7.2.1_r36
May 2023 custom build release
Adapted LineageOS Jelly Browser (additionally having Startpage and Qwant as search engines)
Root is not included and would need to be flashed separately
Patched for the use of the substratum theme engine (the substratum app and the themes need to be downloaded separately)
System certificates taken from AOSP Oreo branch
Kernel forked from LineageOS and updated with many security patches
OTA Support
Enforcing SELinux
There are two build variants available:
A. Default LineageOS 14.1 with substratum and microG patch
Patched for the use of microG - you can either flash Gapps or manually install microG as apps (or use neither of those)
Android System Webview M114
Download here
B. Hardened build with pre-installed microG and F-Droid, patched for substratum
For the security/privacy focused. It has to be said that microG seems to run better if it is pre-installed.
Pre-installed microG same as the LineageOS for microG project
Pre-installed AuroraStore / AuroraServices
Additional security hardening features listed below
SQLite 'secure delete' feature enabled
Access to /proc/net blocked for user apps
Bundled netmonitor app to allow network monitoring
Enhanced Privacy Guard: Switches for motion sensors and other sensors available
Oreo backport: SET_TIME_ZONE permission restricted to system apps
Oreo backport: Access to timers in /proc restricted
Cloudflare as default DNS (instead of Google)
Privacy-preferred default settings
No submission of IMSI/phone number to Google when GPS is in use
Mulch System Webview M114
Download here
Source Code links
LineageOS: https://github.com/LineageOS
Kernel: https://github.com/lin14-mGoms/android_kernel_motorola_msm8226/tree/mse_v1
microG patches:
(1) https://github.com/microg/android_p...aster/patches/android_frameworks_base-N.patch
(2) https://github.com/microg/android_p...aster/patches/android_frameworks_base-N.patch
Patches for Substratum: https://github.com/LineageOMS
local manifest: https://github.com/lin14-mGoms/local_manifests/tree/cm-14.1-oms
Installation Instructions
YOU ARE RESPONSIBLE SOLELY YOURSELF FOR ANY ACTIONS YOU DO WITH YOUR DEVICE !!!
Please note - I won't explain any single aspect (e.g. how to install 'fastboot' on your PC or troubleshoot USB connectivity issues under Windows). Search the net and consult the search engine of your choice or look here in XDA, there is plenty information available.
Pre-Requisites
Get familiar with the hardware keys of the Motorola Moto G LTE (peregrine) device, especially how to enter fastboot mode (switch phone off hold power + volume down together for about 3 seconds) and recovery mode (in fastboot mode, switch with volume down key to the reboot recovery option and select with volume up key)
Have fastboot and adb installed on your PC and make sure, you can connect via USB to your device in fastboot mode and via adb
Download the most current .ZIP file of this ROM and place it to your phone's internal memory
An unlocked bootloader (read the warnings carefully and backup your data!)
Your bootloader must at least be on version 41.18 (find out via fastboot getvar version-bootloader) - if your bootloader is below that version, the ROM will refuse to install. In that case, you need to upgrade the BL first. See e.g. here for more info. (I currently do not find the link, which I have used some years back, but the provided link should be helpful, too)
Install TWRP recovery
If you come from stock ROM and have just unlocked your boot loader, this is the next thing to do. If you have already a working custom recovery on your device, there is no necessity to replace it.
However - I recommend to use the TWRP recovery. The following instructions are based on TWRP.
To install TWRP, download the TWRP.img file (Note: replace "TWRP.img" in the following instructions with the real file name) from this section to your PC, get it into 'fastboot mode', connect the device via USB to your PC and enter the following command on your PC:
Code:
fastboot flash recovery TWRP.img
Afterwards, directly boot into 'recovery mode' (see above) - I recommend not to boot the phone's Android system after having flashed TWRP. Once TWRP has been launched, you may decide to reboot your phone and install the ROM at any time later. But the first boot after flashing TWRP should be TWRP in recovery mode.
Advanced Wipe
ONLY perform the steps described here, if you come from Stock ROM or a different Custom ROM!
Boot into recovery mode. In TWRP, choose "Wipe", "Advanced" and specify "Dalvik", "System", "Cache" and "Data" to be wiped.
Make sure NOT to wipe "Internal memory" (or "SD Card", if shown). Swipe to confirm the deletion and get back into the main menu.
GApps (only for build variant A - do not flash on build variant B!)
You have the choice: a. Use microG - b. Flash GApps - c. Neither of those (obviously, you cannot combine those options!)
'microG' is installed simply by installing the respective apps, no flashing necessary. If you wish to have GApps, they need to be flashed together with the ROM. Download GApps in that case only from opengapps.org and put the .ZIP also to the Internal memory of your device. Choose ARM as platform, Android 7.1 and the flavor of your choice. I strongly recommend "pico" for two reasons:
1. The Moto G LTE has not much internal memory (8 GB) and GApps are notoriously known to waste a lot of space
2. It leaves you the most freedom to only install, what you really need; you can later download and still install all the Google products you want from the play store, so you do not need to live with pre-installed Google stuff you have no use for.
The 'microG patch' in this ROM has no negative impact on installing Gapps.
Install the ROM
In the TWRP main menu, choose "Install". A file manager appears to let you navigate to your internal memory (path /sdcard).
Choose the .ZIP file of this ROM and swipe to flash. If you update from a previous version of this ROM, you don't need to perform a wipe. If in that case, you had GApps already installed before the update, there is no need to flash them again. They will be automatically restored during the flash process.
If you come from a different ROM (or stock firmware), make sure that you have performed the Wipe steps above. If you want to install GApps, flash them directly after the ROM, do not reboot in between. (Note: If you wish to get rid of previously installed GApps, navigate to TWRP's file manager in the Advanced section of the main menu, go to path /system/addon.d and delete the file 70-gapps.sh, before flashing the ROM update)
When finished flashing, return to the main menu, choose "Reboot" and then "System", which will cause your phone to boot into Lineage OS 14.1 - be patient, the first boot after flashing a new ROM takes quite long!
Current / reported issues
WiFi hotspot needs to be toggled on/off/on after a reboot to work
WiFi hotspot enabled longer than 2 hours may cause a sudden reboot
Sometimes (root cause not clear), WiFi switches itself off after a couple of hours (fix by enabling/disabling flight mode)
It has been reported by some forum participants, that after messing with some Android-10 test builds for this device, WiFi wouldn't work any more: In this case, the solution can be found here:
[FIX] Cant turn WIFI on? You are missing this file
So after lots of flashing of different roms on my Moto G 2nd gen (XT1068) I ended up unable to turn WIFI on in any rom, including stock! Thing is, after days of breaking my head with this, I figured out I was missing the...
forum.xda-developers.com
Why still on Android 7.1 (Nougat) and not a higher Android version (like 10 or 11)?
The peregrine device is low on memory (RAM and storage flash memory), each newer Android release increases the resource demand and thus decreases performance and available memory - so higher versions won't really make sense for this device.
Further, I haven't seen any ROM for this device on a higher Android version than Nougat with enforcing SELinux (yes, coming there indeed is "slave work"; none of the devs, including me for above stated reasons, is willing to invest this time...) - which is a No-Go for any daily-driver use (in that case, your device simply is fully open many vulnerabilities and applying monthly ASB patches on a permissive SELinux is close to a complete waste of time).
Credits
Android Open Source project (AOSP)
LineageOS project
microG project
Substratum team
SkewedZeppelin (Kernel patches)
XDA:DevDB Information
[ROM][LineageOS 14.1][substratum] for Moto G LTE [peregrine], ROM for the Moto G
Contributors
MSe1969
Source Code: https://github.com/lin14-mGoms/local_manifests
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
Version Information
Status: Stable
Stable Release Date: 2023-06-20
Created 2019-09-12
Last Updated 2023-06-20

Change Log
June 2023
Custom build release 2023-06-01
Standard and Mulch Webview 114.0.5735.131
microG flavor only: microG 0.2.28.231657
microG flavor only: AuroraStore 4.2.3
May 2023
Custom build release 2023-05-01
Standard flavor only: System Webview 113.0.5672.77
microG flavor only: Mulch Webview 113.0.5672.77
April 2023
April 2023 Custom build release
Standard flavor only: System Webview 112.0.5615.136
microG flavor only: Mulch Webview 112.0.5615.136
March 2023
March 2023 Custom build release
Standard flavor only: System Webview 111.0.5563.58
microG flavor only: Mulch Webview 111.0.5563.58
February 2023
February 2023 Custom build release
Standard flavor only: System Webview 109.0.5414.118
microG flavor only: 0.2.27.223616-3
January 8th, 2023
January 2023 Custom build release
Standard flavor only: System Webview 108.0.5359.128
microG flavor only: 0.2.26.223616-16
December 14th, 2022
December 2022 Custom build release
Standard flavor only: System Webview 108.0.5359.79
microG flavor only: Bromite Webview updated to 108.0.5359.106
microG flavor only: 0.2.26.223616-2
November 14th, 2022
November 2022 Custom build release
Timezone DB 2022 updates
Standard flavor only: System Webview 107.0.5304.105
microG flavor only: Bromite Webview updated to 106.0.5249.163
microG flavor only: microG 0.2.25.223616-10
microG flavor only: F-Droid 1.15.3
October 17th, 2022
October 2022 Custom build release
Kernel: Some WiFi patches
Standard flavor only: System Webview 106.0.5249.79
microG flavor only: Bromite Webview updated to 105.0.5195.147
microG flavor only: microG 0.2.24.223616-61
September 11th, 2022
September 2022 Custom build release
Many kernel patches
Standard flavor only: System Webview 105.0.5195.79
microG flavor only: Bromite Webview updated to 104.0.5112.91
microG flavor only: microG 0.2.24.214816-30
August 9th, 2022
August 2022 custom build release
Standard flavor only: System Webview 103.0.5060.71
microG flavor only: Bromite Webview 103.0.5060.140
July 16th, 2022
July 2022 custom build release
June 16th, 2022
June 2022 custom build release
Standard flavor only: System Webview 102.0.5005.78
microG flavor only: Bromite Webview updated to 102.0.5005.96
microG flavor only: F-Droid 1.15.2
microG flavor only: microG 0.2.24.214816-11
May 11th, 2022
May 2022 custom build release
Standard flavor only: System Webview updated to 100.0.4896.127
microG flavor only: Bromite Webview updated to 101.0.4951.53
microG flavor only: F-Droid 1.15
microG flavor only: Mozilla Location provider 1.5.0
microG flavor only: microG 0.2.24.214816-10
April 16th, 2022
April 2022 custom build release
Standard flavor only: System Webview updated to 100.0.4896.58
microG flavor only: Bromite Webview updated to 100.0.4896.57
February 19th, 2022
February 2022 custom build release
Standard flavor only: System Webview updated to 98.0.4758.101
microG flavor only: F-Droid updated to 1.14, F-Droid privileged extension to 0.2.13
microG flavor only: Bromite Webview updated to 97.0.4692.106
microG flavor only: microG updated to 0.2.24.214816-2
December 20th, 2021
December 2021 custom build release
Standard flavor only: System Webview updated to 96.0.4664.104
microG flavor only: Bromite Webview 96.0.4664.54
microG flavor only: microG 0.22.214516-21
November 9th, 2021
Show again "official" Sec. string same as LineageOS (2021-06-05)
Additional Custom build release property to indicate backport status
Standard flavor only: System Webview updated to 95.0.4638.50
microG flavor only: Bromite Webview 94.0.4606.109
September 17th, 2021
UNOFFICIAL Security string 2021-09-05 *
Standard flavor only: System Webview updated to 92.0.4515.159
microG flavor only: microG upstreamed to 0.2.22.212658-2
___________________________
* CVE-2021-0514 and CVE-2021-0515 from July 2021 ASB are still missing!
August 10th, 2021
UNOFFICIAL Security string 2021-08-05 *
Standard flavor only: System Webview updated to 91.0.4472.164
microG flavor only: Bromite System Webview updated to 92.0.4515.134
microG flavor only: F-Droid 1.13
___________________________
* CVE-2021-0514 and CVE-2021-0515 from July 2021 ASB are still missing!
July 14th, 2021
UNOFFICIAL Security string 2021-07-05 *
Kernel: Many sec. patches applied (taken from Divest-OS)
microG flavor only: Bromite System Webview updated to 91.0.4472.146
microG flavor only: microG upstreamed to 0.2.21.212158-2
microG flavor only: AuroraStore 4.0.7
___________________________
* CVE-2021-0514 and CVE-2021-0515 from July 2021 ASB are still missing!
June 16th, 2021
Security string 2021-06-05
Standard flavor only: System Webview updated to 91.0.4472.101
microG flavor only: Bromite System Webview updated to 91.0.4472.102
microG flavor only: microG upstreamed to 0.2.19211515-9
May 09th, 2021
Security string 2021-05-05
Standard flavor only: System Webview on 90.0.4430.82
microG flavor only: Bromite System Webview on 90.0.4430.204
microG flavor only: microG upstreamed (no version upgrade)
microG flavor only: AuroraServices updated 1.1.1
April 11th, 2021
Security string 2021-04-05
Standard flavor only: System Webview on 89.0.4389.105
microG flavor only: Bromite System Webview on 90.0.4430.59
microG flavor only: F-Droid updated to 1.12
microG flavor only: AuroraStore updated to 4.0.4 with AuroraService 1.1.0
March 08th, 2021
Security string 2021-03-05
microG flavor only: Bromite System Webview on 88.0.4324.207
microG flavor only: F-Droid 1.11
microG flavor only: microG 0.2.18.204714
February 07th, 2021
ASB Security string 2021-02-05
microG flavor only: Bromite Webview on 88.0.4324.141
microG flavor only: Updated microG from upstream to 0.2.17.204714-5
microG flavor only: F-Droid updated to 1.10-alpha-234
January 17th, 2021
ASB Security string 2021-01-05
Standard flavor only: System Webview on 87.0.4280.101 & fix of persistent histograms eating disk space
microG flavor only: Bromite Webview on 87.0.4280.131
microG flavor only: Updated microG from upstream to 0.2.16.204713-10 (picked until 2f29b93)
microG flavor only: F-Droid updated to 1.10-alpha1-212
December 18th, 2020
ASB Security string 2020-12-05
Standard flavor only: System Webview on 86.0.4240.198
microG flavor only: Bromite Webview on 87.0.4280.68
microG flavor only: Updated microG from upstream to 0.2.14.204215-15 (picked until 720b089)
microG flavor only: F-Droid updated to 1.10-alpha1-114
November 08th, 2020
ASB Security string 2020-11-05
Fix of AOSP E-Mail widget
Fix for CVE-2020-15999
Standard flavor only: System Webview on 86.0.4240.185
microG flavor only: Bromite Webview on 86.0.4240.181
microG flavor only: Updated microG with fixes in GCM and EN API
microG flavor only: Replaced weak F-Droid signatures with ROM's V2 signatures
October 12th, 2020
ASB Security string 2020-10-05
Updated TimeService.apk
microG flavor only: Bromite Webview on 86.0.4240.73
microG flavor only: updated microG with included Exposure notification API (for Covid tracing apps)
September 14th, 2020
ASB Security string 2020-09-05
Standard flavor only: System Webview on 85.0.4183.101
microG flavor only: Bromite Webview on 85.0.4183.86
August 9th, 2020
ASB Security string 2020-08-05
Standard flavor only: System Webview on 84.0.4147.89
microG flavor only: Bromite Webview on 84.0.4147.113
July 12th, 2020
ASB Security string 2020-07-05
microG flavor only: updated prebuilt microG GmsCore fom /e/ project to fix FCM registration issues
microG flavor only: F-Droid updated to 1.8 / F-Droid privileged extension updated to 0.2.11
microG flavor only: Aurorastore updated to 3.2.9 / AuroraServices updated to 1.0.6
June 09th, 2020
ASB Security string 2020-06-05
Standard flavor only: System Webview on 81.0.4044.138
microG flavor only: Bromite Webview on 83.0.4103.76
May 07th, 2020
ASB Security string 2020-05-05
Standard flavor only: System Webview on 81.0.4044.117
microG flavor only: Bromite Webview on 81.0.4044.127
microG flavor only: AuroraStore updated to 3.2.8
April 10th, 2020
ASB Security string 2020-04-05
Fix for CVE-2020-8597 (external/ppp)
Kernel: CVE-2019-10638 siphash 128bit for IP generation
Standard flavor only: System Webview on 80.0.3987.132
microG flavor only: Bromite Webview on 81.0.4044.76
microG flavor only: AuroraStore updated to 3.2.4
March 07th, 2020
ASB Security string 2020-03-05
Standard flavor only: System Webview on 80.0.3987.117
microG flavor only: Bromite Webview on 80.0.3987.118
microG flavor only: AuroraStore updated to 3.2.0
microG flavor only: Added Netguard app (F-Droid version) to SELinux domain allowing to access /proc/net
February 07th, 2020
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
January 13th, 2020
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.7
microG flavor only: AuroraServices updated to 1.0.5
December 7th, 2019
ASB Security string 2019-12-05
Standard flavor only: System Webview on 78.0.3904.96
microG flavor only: AuroraStore updated to 3.1.5 (variant B only)
November 10th, 2019
ASB Security string 2019-11-05
microG flavor only: Bromite Webview on 78.0.3904.72
microG flavor only: microG GMS core updated to 0.2.9
October 15th, 2019
ASB Security string 2019-10-05
Standard flavor only: System Webview on 77.0.3865.92
microG flavor only: Bromite Webview on 77.0.3865.104
microG flavor only: AuroraStore updated to 3.1.3
September 12th, 2019
Initial creation - same approach like in my Moto G (falcon) thread
Security string 2019-09-05
AOSP tag 7.2.1_r36
System certificates from Oreo AOSP branch
Patched repositories according to LineageOMS project to support substratum
OTA Support
Build variant A - Standard LineageOS 14.1 with microG and substratum patches
Android System Webview M76
Build variant B - hardened microG build with substratum patches and additional security hardening
Bromite System Webview M76
Prebuilt microG and F-Droid
Prebuilt Aurora Store (with AuroraServices)

Tips and Tricks
microG installation on build variant A
The ROM (build variant A) is patched for the use of microG, but it does not contain the microG system components.
The best way to obtain them is to install the F-Droid store as app store and to include the microG repository as described on the microG Download page, where you will also find links for the direct download of the .apk files.
Please refer to the official installation instructions. However, there are three pieces of information, which are explained on the microG pages, but unfortunately not directly in the installation instructions, so I would like to point them out here:
Download the latest 'unstable' Gms Core version to avoid "outdated play services" warnings
The Location Provider functionality is included in Gms Core, but also available as separate application. I recommend Gms Core - however, the explanation is not included in Gms Core, but only here
To grant the signature spoofing permission, go to Settings - Apps - Advanced (the 'gear' icon) - App Permissions - Spoof package signature; it is not possible when you enter the individual app's permissions menu
Make sure to grant all permissions to the location and microG apps (best via running the self-test)
Install substratum
This ROM is patched to support the substratum theme engine, so no root required because of substratum (different from unpatched ROMs). Simply download and install the substratum theme engine from the play store (or look further down, if you don't use GApps) and also the theme(s), you wish to use. For any support with regards to substratum itself and the themes, please search on XDA in the respective forums. You may of course also ask here in this thread and I hope people participating here will answer, but I am no substratum expert, so please do not expect too much support from my side, when it comes to substratum details.
Btw, the ROM also works without substratum, so you can simply use it without, e.g. because of the microG patch.
Getting the substratum app without GApps
Without GApps, no official Play store . . . - but: When you search in XDA / the internet or simply install F-Droid (and for example search for "play store" in F-Droid), you will find a suitable alternative . . .
Root
Although not needed for substratum, there are many further valid reasons why root is needed (I myself also use it). The most popular options are:
Official LineageOS su addon (use 'addonsu-14.1-arm-signed.zip')
Magisk (please search XDA on your own)
SuperSU
Note that I cannot and will not support any issues related to Magisk and/or SuperSU
Details about the build variant B (hardened microG build)
The security hardening features of the 2nd build variant are described here

If you come from an official LineageOS 14.1 build and you would like to "dirty-flash" the 'Standard' build (variant A) - i.e. no wipe to keep your stuff (my recommendation is to do a clean install, see OP) - these instructions on the LineageOS Wiki are helpful. I will however not further explain this, you need to know, what you are doing (if you don't understand these instructions, it really is better and in your own interest, if you don't do it)
For build variant B, I really recommend a clean flash!

Have you tested the gyroscope? In previous los 14.1 builds there was the rotation issue...

MaCianz said:
Have you tested the gyroscope? In previous los 14.1 builds there was the rotation issue...
Click to expand...
Click to collapse
Not sure what you mean - Rotation seems to work normally. (Have to admit however that so far I have only built for falcon and the peregrine was only recently donated to me - but difference between falcon and peregrine in regards to building is only the device repo, rest including device-common and kernel is the same - and I've never noticed such an issue with falcon)

MSe1969 said:
Not sure what you mean - Rotation seems to work normally. (Have to admit however that so far I have only built for falcon and the peregrine was only recently donated to me - but difference between falcon and peregrine in regards to building is only the device repo, rest including device-common and kernel is the same - and I've never noticed such an issue with falcon)
Click to expand...
Click to collapse
I mean... Automatic rotation didn't worked for me in los 14.1...anyway, will test and report:good:

MaCianz said:
I mean... Automatic rotation didn't worked for me in los 14.1...anyway, will test and report:good:
Click to expand...
Click to collapse
I build and maintain an unofficial LOS 14.1 for Moto G LTE Peregrine that is based off the original official local manifest files with no added changes other than those reviewed, verified and committed by LineageOS Gerrit (e.g., latest security patches, etc.). I have no issues with the Gyroscope rotation, nor I have I had any reports of this issue by other members who have downloaded my build.
So ... I suspect the issue resides with your cell phone, either from installing a custom rom other than one based on Lineage, a corruption that has developed in your data, a conflict with another app or a hardware issue that would necessitate a replacement of that particular sensor. There are many apps on Play Store that can be used to re-calibrate the gyroscope sensor if you haven't tried that. As well, if you have not done a full clean flash: in TWRP wipe Cache, Dalvik cache, System and importantly, format data > Yes (i.e., not just a wipe in other words - making sure you back up your data and copy all your pictures, videos etc., over to your pc/laptop first), then try that. Then re-install the rom, open gapps etc.

sdembiske said:
I build and maintain an unofficial LOS 14.1 for Moto G LTE Peregrine that is based off the original official local manifest files with no added changes other than those reviewed, verified and committed by LineageOS Gerrit (e.g., latest security patches, etc.). I have no issues with the Gyroscope rotation, nor I have I had any reports of this issue by other members who have downloaded my build.
So ... I suspect the issue resides with your cell phone, either from installing a custom rom other than one based on Lineage, a corruption that has developed in your data, a conflict with another app or a hardware issue that would necessitate a replacement of that particular sensor. There are many apps on Play Store that can be used to re-calibrate the gyroscope sensor if you haven't tried that. As well, if you have not done a full clean flash: in TWRP wipe Cache, Dalvik cache, System and importantly, format data > Yes (i.e., not just a wipe in other words - making sure you back up your data and copy all your pictures, videos etc., over to your pc/laptop first), then try that. Then re-install the rom, open gapps etc.
Click to expand...
Click to collapse
I've done everything...and found out that it's something related to custom kernels.
los 14.1+gapps = rotation ok.
Los 14.1+gapps+any custom kernel(zer0 bye, kaminari, valkirye etc.) = no rotation working.
Anyway...it's not a big deal so i'll keep it like that.

MaCianz said:
I've done everything...and found out that it's something related to custom kernels.
los 14.1+gapps = rotation ok.
Los 14.1+gapps+any custom kernel(zer0 bye, kaminari, valkirye etc.) = no rotation working.
Anyway...it's not a big deal so i'll keep it like that.
Click to expand...
Click to collapse
Just as info: This ROM uses a Fork of the "original" LineageOS Moto msm8226 kernel - with further security patches only (as the LineageOS kernel hasn't been updated since longer time).
The feedback given in my parallel "falcon" thread was positive and also I do not have the impression that the device behavior indicates looking for an alternative kernel...
So if your motivation to use a 3rd party custom kernel is mainly driven by the security patching aspect, you may want to give this ROM's delivered kernel a try.

MaCianz said:
I've done everything...and found out that it's something related to custom kernels.
los 14.1+gapps = rotation ok.
Los 14.1+gapps+any custom kernel(zer0 bye, kaminari, valkirye etc.) = no rotation working.
Anyway...it's not a big deal so i'll keep it like that.
Click to expand...
Click to collapse
The kernel is just one aspect in the android sensor system, so yes it could be related to the kernel but not in all cases. You could see if a 'virtual' gyroscope app on Play Store could help in your case.
The diagram I've attached presents a great overview of the android sensor framework system (while it displays the
accelerometer sensor in the last frame, it is the same process for the gyroscope):

MSe1969 said:
Just as info: This ROM uses a Fork of the "original" LineageOS Moto msm8226 kernel - with further security patches only (as the LineageOS kernel hasn't been updated since longer time).
The feedback given in my parallel "falcon" thread was positive and also I do not have the impression that the device behavior indicates looking for an alternative kernel...
So if your motivation to use a 3rd party custom kernel is mainly driven by the security patching aspect, you may want to give this ROM's delivered kernel a try.
Click to expand...
Click to collapse
Nope...i use custom kernels for overclock and underclock:silly:
sdembiske said:
The kernel is just one aspect in the android sensor system, so yes it could be related to the kernel but not in all cases. You could see if a 'virtual' gyroscope app on Play Store could help in your case.
The diagram I've attached presents a great overview of the android sensor framework system (while it displays the
accelerometer sensor in the last frame, it is the same process for the gyroscope):
Click to expand...
Click to collapse
I used cpu-z for checking the sensor status, gyroscope was showing correctly x,y,z values.
With custom kernel values were fixed to 0.0.
Anyway, will check if there is some workaround(except flashing stock kernel )

Thank you MSe1969 for bringing this ROM to peregrine. I have both falcon and peregrine in the family and was using the falcon variant of your ROM, which is stable and smooth. Props to you my friend.

MaCianz said:
Nope...i use custom kernels for overclock and underclock:silly:
I used cpu-z for checking the sensor status, gyroscope was showing correctly x,y,z values.
With custom kernel values were fixed to 0.0.
Anyway, will check if there is some workaround(except flashing stock kernel )
Click to expand...
Click to collapse
Custom kernels for moto g lte are quite old, o would say stock forma the latest Roma have newer drivers that the Roms need

Pupet_Master said:
Custom kernels for moto g lte are quite old, o would say stock forma the latest Roma have newer drivers that the Roms need
Click to expand...
Click to collapse
I know...but i use this phone as a secondary phone for games and custom kernels with OC helps me to run heavier games.

MaCianz said:
I know...but i use this phone as a secondary phone for games and custom kernels with OC helps me to run heavier games.
Click to expand...
Click to collapse
Yea, trouble is that maybe you should use a older ROM for the time of the Kernel last update maybe, to avoid all issues

great work bro

Pupet_Master said:
Yea, trouble is that maybe you should use a older ROM for the time of the Kernel last update maybe, to avoid all issues
Click to expand...
Click to collapse
Maybe, but as long as it works...why not

Hi all,
new builds are available for download with ASB Security String 2019-10-05:
A. Default LineageOS 14.1 with substratum and microG patch
https://www.androidfilehost.com/?fid=1899786940962610093
- System Webview updated to 77.0.3865.92
B. Hardened build with pre-installed microG and F-Droid, patched for substratum
https://www.androidfilehost.com/?fid=1899786940962610092
- Bromite Webview updated to 77.0.3865.104
- AuroraStore updated to 3.1.3
If you are on the September build of this ROM, the updater app will also offer an OTA update.
Regards, M.

And the Peregrine just goes on; the hardened build OTA update works just as one would hope, and all is good.

[SHARE] Havoc OS A10 - POST IS UNOFFICIAL

=============================
Havoc-OS v3.8 Official Update
Android 10
=============================
Date: 21-08-2020
Device: OnePlus 5 (cheeseburger)
Maintainer: Tilaksid
Changelog: https://t.me/Havoc_OS/2494
Device Changelog:
• Bluetooth config update and clean up
• Telephony/Carrier config update from CAF
• Kernel cleanup and updates for better performance
Download Link:
• ROM (Vanilla): https://sourceforge.net/projects/ha...8-20200817-cheeseburger-Official.zip/download
• ROM (GApps): https://sourceforge.net/projects/ha...0817-cheeseburger-Official-GApps.zip/download
Note:
• Required firmware: 10.0.0-H1
This post is just for people who may wish to locate the A10 Havoc OS update, and since developer and their team is no longer concerned to update XDA, even after requesting several times by many..

For future use the SF files link to check for update. I will try to update here if possible to get the change logs and requirements.

Question How to avoid crash that happens when using ACTION_WIFI_ADD_NETWORKS intent in the android 11 devices

We are using ACTION_WIFI_ADD_NETWORKS intent to add our network into the Saved Networks. For reference, we are using this link https://developer.android.com/guide/topics/connectivity/wifi-save-network-passpoint-config
We noticed that the issue got fixed in the 5th Feb 2021 security patch release in Pixel devices. So in our codes, we implemented a workaround of checking if the Security Patch Level of the device is greater than the ValidPatch which is 2021-02-05 and then we proceeded with calling the intent. But this check failed in a Oneplus Nord CE 5G device with Android version 11 and Android Security update 2021-07-01
Please provide some information on when the Android security patch will be updated such that the crash will not happen anymore?