Database Develop

[CLOSED][EOL] Osprey LineageOS 13 with microG patch - Moto G 2015 Android Development

Hi,
this thread aims at keeping the LineageOS 13.0 version alive for the Moto G 2015 (osprey) device with current security patches from LineageOS (branch 'cm-13.0'). The build here has already a history in this thread on XDA - it may be worth to scroll through it to find additional information.
The build has got the following features:
LineageOS 13 with current security patches
Patched for microG (see https://microg.org, signature spoofing as switchable permission)
Squid kernel for the Osprey device (own fork)
LineageOS Jelly Browser
Current Android System Webview
CMUpdater is not part of this build
Renewed CA-certificates from AOSP master branch
VoLTE (may not work in all cases!)
Current build data
Download here
AOSP tag android-6.0.1_r81
Security string 2018-06-01
Android System Webview on M66 (stable, taken from LineageOS 14.1)
Contains the fix for the KRACK attack against WPA2
Root access included (can be switched on/off in developer settings)
Unofficial microG-build as 2nd build variant
Download here
Hardened build with pre-installed microG apps. For more information, see https://lineage.microg.org/
(This is an unofficial build for LineageOS 13 f. osprey based on the work described on the project page)
Different from the 1st build, the following features apply, everything else is the same:
No root available (can be flashed separately)
Pre-installed microG apps (see lineage.microg.org page)
SQLite 'secure delete' feature enabled
Access to /proc/net blocked for user apps
Enhanced Privacy Guard (1): Switches for motion sensors and other sensors available
Enhanced Privacy Guard (2): Switches for read phone state and storage (read/write) available
Oreo backport: SET_TIME_ZONE permission restricted to system apps
Oreo backport: Access to timers in /proc restricted
Cloudflare DNS (1.1.1.1) as default fallback
Privacy-preferring default settings
Source Code links
LineageOS: https://github.com/LineageOS
Kernel: https://github.com/MSe1969/android_kernel_motorola_msm8916/tree/mse_cm13
microG patch: https://github.com/microg/android_p...aster/patches/android_frameworks_base-M.patch
microG-Build: https://github.com/lineageos4microg
local manifest: https://github.com/cm13-microG/local_manifests
hardening features: see reserved post further below
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 2015 (osprey) 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 key to the reboot recovery option and select with power 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 or SD card
If you wish to install Google apps (GApps), please refer to the GApps section further below
An unlocked bootloader (read the warnings carefully and backup your data!
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 linked here. 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 spefify "Dalvik", "System", "Cache" and "Data" to be wiped.
Make sure NOT to wipe "Internal memory" or "SD Card". Swipe to confirm the deletion and get back into the main menu.
GApps
The following instructions only apply for the 1st variant, do not flash Gapps over the "microG build":
You do not need to install GApps, but you may wish to do so. In that case, download GApps from here and put the .ZIP also to the SD card or Internal memory of your device.
Choose ARM as platform, Android 6.0 and the flavor of your choice. I recommend "pico", as this leaves you the most freedom to only install, what you really need; you can later still install all the Google products you want and do not need to live with pre-installed Google applications 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) or your SD card (path /external_sd).
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 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.
(Note: If you wish to get rid of 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)
If you come from a different ROM (or stock firmware), make sure that you have performed the Wipe steps above.
If you wish to install GApps, select the respective .ZIP file directly afterwards, do not boot into Android before having flashed GApps. When finished flashing, return to the main menu, choose "Reboot" and then "System", which will cause your phone to boot into Lineage OS 13.0 - be patient, the first boot after flashing a new ROM takes quite long!
microG Installation
These instructions apply to the 1st 'default' variant, not the 'microG build' (which has already microG installed)
The ROM is patched for the use of microG, but it does not contain the microG system components.
The best way to obtain them is to include the microG repository into the F-Droid store 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 'unstable' Gms Core version 0.2.4-105-... 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
Credits
Android Open Source project (AOSP)
LineageOS project
squid2 (Kernel)
microG project
XDA:DevDB Information
Osprey LineageOS 13 with microG patch, ROM for the Moto G 2015
Contributors
MSe1969
Source Code: https://github.com/cm13-microG/local_manifests
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
Based On: LineageOS
Version Information
Status: Testing
Created 2017-10-23
Last Updated 2018-07-24

Change Log
June 20th, 2018
Announcement to discontinue the cm-13.0 builds - please visit my Lineage OS 14.1 microG thread, which continues with LineageOS 14.1
June 10th, 2018
Security string 2018-06-01
May 22nd, 2018
Security string 2018-05-01
Android System Webview M66
Cloudflare DNS as default (instead of Google)
Privacy-preferred default settings
Kernel fix for in-call sound issue
April 11th/12th, 2018
Security string 2018-04-01
Android System Webview M65
March 16th/17th, 2018
Security string 2018-03-01
Squid Kernel r22c (Oreo)
Renewed CA certificates from AOSP master branch
Bugfix of date/time reset on reboot, when no carrier sync
Bugfix in microG build: Always skip GMS page in SetupWizard
February 19th, 2018
Update after ASB merge in LineageOS 13.0
Webview now on stable M64
February 10th, 2018
Security string 2018-02-01
Squid Kernel r22c (Oreo)
Privacy Guard enhancements
Further security hardening in 2nd "microG build" variant
January 16th, 2018
Security string 2018-01-01
Squid Kernel r22 (Oreo)
System Webview switched back to M63-stable
2nd build variant "unofficial microG build"
December 21st, 2017
Security string 2017-12-01
Squid Kernel r21 (Oreo) forked
Recent Jelly build
Android System Webview 64.0.3282.30 (beta)
November 24th, 2017
Security string 2017-11-01
Squid Kernel (Nougat) forked and merged 3.10.108 updates from kernel.org
October 23rd, 2017
Fix of KRACK attacks
Security string 2017-10-01
AOSP tag 6.0.1_r81
Android System Webview updated to M64
Squid Kernel (Nougat)
- - - - - - - - - - - - - - - - - - - - - - - - - - - -
Historical entries from this thread:
September 21st, 2017
Security string 2017-09-01
AOSP tag 6.0.1_r80
Jelly updates
Fix of 'Blueborne' attack (part of Sept. security patches)
September 2nd, 2017
Security string 2017-08-01
Android System Webview updated to M60
July 14th, 2017
Security string 2017-07-01
June 14th, 2017
Security string 2017-06-01
Android System Webview updated to M59
May 28th, 2017
Replaced Gello with new LineageOS Jelly Browser
Android System Webview updated to M58
May 26th, 2017
Security string 2017-05-01
April 17th, 2017
Security string 2017-04-01
AOSP tag 6.0.1_r79
March 24th, 2017
Security string 2017-03-01
Included Kernel from cm-14.1 branch to regularly receive sec. patches
March 13th, 2017
Security string 2017-02-01
February 21st, 2017
Security string 2017-01-01
Rebranded LineageOS

Security Hardening (microG build)
Details about additional security hardening in the "microG build"
1. SQLite 'Secure Delete' feature
This sanitizes deleted data by overwriting it with zeroes, rather than having it persist within SQLite's free list.
Backport from Oreo, see https://android-review.googlesource.com/q/topic:"secure_delete"
2. Restrict SET_TIME_ZONE permission to system apps
Backport from Oreo, see here
3. Enhanced Privacy Guard (1) - Sensor permission switches
An own sensor template to control access to motion sensors (ask mode) and all other sensors (allowed by default, but can be restricted) has been implemented into the Privacy Guard. Commits: (1), (2), (3)
4. Enhanced Privacy Guard (2) - Switches for 'Read phone state' and 'Storage'
The existing AppOps to read the phone's IMEI and to control access to the SD card have been made accessible.
This is a cherry-pick of the proposed LineageOS change here
5. Restrict access to /proc/net for user apps
An adapted SELinux policy prevents user apps from accessing the /proc/net pseudo file system, which can be misused to monitor and track the phone's internet traffic. For technical backgrounds, see here. This is the main commit. For the legitimate use case of the smart phone owner him/herself monitoring the network traffic to see, what the installed apps do, the app Privacy-Friendly Network Monitorhas been bundled
6. Access to timing information in /proc restricted
To prevent side-channel attacks as described here, the respective Oreo patch has been back-ported.
7. Cloudflare (instead of Google) default DNS
Cloudflare DNS has a better privacy policy than Google Public DNS and has DNS-over-TLS and DNS-over-HTTPS. In the deafult DNS settings (as fallback) and network diagnostics, the Cloudflare DNS adresses 1.1.1.1 and 1.0.0.1 are specified as defaults (instead of Google's 8.8.8.8 and 8.8.4.4)
8. Privacy-preferred default settings
When newly installed, the below settings are defaulted, different from standard LineageOS 14.1 (all setting can be changed at any time later):
Privacy Guard is enabled on install (proposal during Setup)
Anonymous LineageOS statistics disabled (proposal during Setup)
The standard browsing app does not get the location runtime permission automatically assigned

Sweet..

Nice. Good to see this as separate post.

Every time the ambient display lights up the screen, it is in on a high brightness mode. And the moment I tap, it gets back to normal brightness. I know this could be a cm13 issue but, any way to resolve this ?

shadowbone said:
Every time the ambient display lights up the screen, it is in on a high brightness mode. And the moment I tap, it gets back to normal brightness. I know this could be a cm13 issue but, any way to resolve this ?
Click to expand...
Click to collapse
I haven't observed this behavior on my device, can you provide some more details?

MSe1969 said:
I haven't observed this behavior on my device, can you provide some more details?
Click to expand...
Click to collapse
It isn't that big a difference but perhaps I could provide you a log, if that could help.

shadowbone said:
It isn't that big a difference but perhaps I could provide you a log, if that could help.
Click to expand...
Click to collapse
Thanks - will have a look later

MSe1969 said:
Thanks - will have a look later
Click to expand...
Click to collapse
Sure thing.
Also, is this volte supported or should I flash the volte patch ? Because I can't seem to get it work. I am on the latest build.

VoLTE
As you can see in the old thread, there have been some discussions about VoLTE support (and also some attempts from my side to get it running).
Let me quickly summarize:
I have tried the VoLTE patch(es) from XDA - VoLTE menu was there but no VoLTE calls on my phone
I have tried to create a test build with the contents of those patches and also looked at what was done in cm-14.1 - same result: menu there, but no VoLTE calls (LTE symbol disappears when calling)
Got mixed feedbacks from people using the test build - works well for the ones and does not work or stops working after reboot for others . . .
LineageOS 14.1 is supposed to have VoLTE support f. osprey - same story, not on my phone (menu entry there, but *#*#4636#*#* menu and IMS status there tells VoLTE not available - tested with SIM cards from different carriers)
So I'm having trouble to get it working on my device (XT1541 16GB) at all. On my repo's at github, the msm8916 device and vendor tree have two volte branches for testing.
Any insight, advice and/or build suggestions welcome

shadowbone said:
It isn't that big a difference but perhaps I could provide you a log, if that could help.
Click to expand...
Click to collapse
dear user, could you tell me what application I can get this file (
File Type: txt 2017-10-25-14-38-27.txt), since I have some errors in the rom, thanks.

MSe1969 said:
As you can see in the old thread, there have been some discussions about VoLTE support (and also some attempts from my side to get it running).
Let me quickly summarize:
I have tried the VoLTE patch(es) from XDA - VoLTE menu was there but no VoLTE calls on my phone
I have tried to create a test build with the contents of those patches and also looked at what was done in cm-14.1 - same result: menu there, but no VoLTE calls (LTE symbol disappears when calling)
Got mixed feedbacks from people using the test build - works well for the ones and does not work or stops working after reboot for others . . .
LineageOS 14.1 is supposed to have VoLTE support f. osprey - same story, not on my phone (menu entry there, but *#*#4636#*#* menu and IMS status there tells VoLTE not available - tested with SIM cards from different carriers)
So I'm having trouble to get it working on my device (XT1541 16GB) at all. On my repo's at github, the msm8916 device and vendor tree have two volte branches for testing.
Any insight, advice and/or build suggestions welcome
Click to expand...
Click to collapse
You could get some help from this post.. check by integrating this patch. https://forum.xda-developers.com/2015-moto-g/themes-apps/osprey-volte-patch-android-n-roms-t3527635
Edit - post added

Erick_Summer said:
dear user, could you tell me what application I can get this file (
File Type: txt 2017-10-25-14-38-27.txt), since I have some errors in the rom, thanks.
Click to expand...
Click to collapse
Well, if you meant taking a log, there are plenty. The one I used is 'matlog'. You can get it from playstore.

rahul9999 said:
You could get some help from this post.. check by integrating this patch. https://forum.xda-developers.com/2015-moto-g/themes-apps/osprey-volte-patch-android-n-roms-t3527635
Edit - post added
Click to expand...
Click to collapse
I used this post and its patches always as a base for my test builds. Tried now the most current MM patch , which was uploaded in October - same result, does not work on my device.

shadowbone said:
It isn't that big a difference but perhaps I could provide you a log, if that could help.
Click to expand...
Click to collapse
Hi, haven't really noticed anything unusual in the log, I also use afwall and Xprivacy. Only noticed you use a battery app, but log does not indicate any issues... So I am afraid I can't really help, as I can't reproduce this behavior on my device.

MSe1969 said:
Hi, haven't really noticed anything unusual in the log, I also use afwall and Xprivacy. Only noticed you use a battery app, but log does not indicate any issues... So I am afraid I can't really help, as I can't reproduce this behavior on my device.
Click to expand...
Click to collapse
Yeah, I use the betterbatterystats from xda. I guess I will try and do a dalvik cache clear and if possible do a clean rom flash in the near future and try again. Else, it must be some device specific issue.
Anyway thanks a lot for your time. I appreciate it.

My daily ROM, please update.
The best ROM tk!

kurapika7 said:
My daily ROM, please update.
The best ROM tk!
Click to expand...
Click to collapse
This is marshmallow, correct. Why is it better than
Nugget?
Thanks for sharing!
Also, your experience with no Google services.

melp57 said:
This is marshmallow, correct. Why is it better than
Nugget?
Thanks for sharing!
Also, your experience with no Google services.
Click to expand...
Click to collapse
have a better use of ram

Related

Welcome back!
This thread is dedicated to provide Lineage-OS 16.0 builds for the Motorola Moto G 2015 (Osprey) with current security patches.
You can consider this thread as kind of a successor of my LineageOS 14.1 Osprey thread
Well, and as well also a 'successor' of my LineageOS 17.1 Osprey thread !
Sounds weird? Well, here comes the explanation:
In May 2020, I have created this thread as a successor of my LineageOS 14.1 builds. Until December 2020, I used to provide two build flavors, one for Standard LineageOS and one with my hardened microG build. From January 2021 onwards, I have provided my hardened microG build flavor with LineageOS 17.1 in above linked thread, whilst I had asked the users of the "Standard" flavor to simply switch to the official LineageOS 17.1 builds. It has turned out, that indeed Android 10 is the boundary, of what can be done with this old device. Especially the hardening measures ask for a stronger hardware, so the builds were "still okay", but not really as agile as the 16.0 builds (especially on an 8GB device). Based on own experience and user feedback in my 17.1 thread, I have finally decided to go back to Android 9 / LineageOS 16.0 - so here we are.
I have decided to re-enable this thread instead of creating a new one, to allow you to better search for any answers and issues.
Until December 2020, There were two build flavors available, both signed (see further below). Both builds have aimed at providing stable and reliable "daily-driver" builds. The last "Standard LineageOS 16.0" build can still be downloaded here - I will however not offer this build flavor any more.
The build flavor, which I offer now again in this thread is my
Security hardened microG build
The latest build can be downloaded here.
It is mainly based on the work of chil360 and the main features are:
Fork of Hybrid-X kernel with frequently applied security patches
Encryption fully functional
Enforcing SE Policy
OTA support
Pre-installed microG and F-Droid like the LineageOS for microG project (own fork)
Pre-installed AuroraStore
eSpeak TTS engine (FOSS TTS solution)
Backported Audio balance (accessibility settings) from Android 10
Additional security hardening features listed below
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
Cloudflare as default DNS (instead of Google)
Privacy-preferred default settings
Optional blocking of Facebook- and Google-Tracking
Optional disable captive portal detection
Firewall UI
Increased max. password length of 64
No submission of IMSI/phone number to Google/Sony when GPS is in use
Default hosts file with many blocked ad/tracking sites
Privacy-enhanced Bromite SystemWebView Mulch Webview
Additional restriction options for secondary users
Constified JNI method tables
Current release levels
Custom build release: 2023-06-01
Security string: 2022-01-05
AOSP tag: 9.0.0_r46
Mulch Webview: M114
Source-code and build instructions
Kernel: https://github.com/lin16-microg/android_kernel_motorola_msm8916/tree/mse_v1
Build manifest: https://github.com/lin16-microg/local_manifests
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 2015 (osprey) 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 key to the reboot recovery option and select with power key)
Activate the Developer options (Settings, about phone: tap 7 times on the build number), get into the new menu Developer options and activate, if available, the option "OEM unlocking")
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 or SD card
Only valid for the "standard build flavor": If you wish to install Google apps (GApps), please refer to the GApps section further below
An unlocked bootloader (read the warnings carefully and backup your data!)
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 official TWRP recovery from the TWRP site. 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, connect the phone via USB to your PC, get it into 'fastboot mode' and enter the following command on your PC:
Code:
fastboot flash recovery TWRP.img
Afterwards, directly boot into 'recovery mode' (enter fastboot reboot on your PC and use the right hardware keys to get into recovery mode) - 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 spefify "Dalvik", "System", "Cache" and "Data" to be wiped. Make sure NOT to wipe "Internal memory" or "SD Card". Swipe to confirm the deletion and get back into the main menu.
GApps
DO NOT attempt to flash GApps on the "microG" build variant!
For the "Standard" variant (if you really want to flash the "historic" build from December 2020), the following applies:
You do not need to install GApps, but you may wish to do so. In that case, download GApps from here and put the .ZIP also to the SD card or Internal memory of your device. Choose ARM as platform, Android 9.0 and the flavor of your choice. I recommend "pico", as this leaves you the most freedom to only install, what you really need; you can later still install all the Google products you want and do not need to live with pre-installed Google applications you have no use for.
(To be more precise, I EXPLICITLY DO NOT RECOMMEND any Gapps variant larger than "nano"!)
Install the ROM
In the TWRP main menu, choose "Install". A file manager appears to let you navigate to your internal memory (path /sdcard) or your SD card (path /external_sd). Choose the .ZIP file of the ROM and swipe to flash.
If you update from a previous version of the ROM, you don't need to perform a wipe. If 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. (Note: If you wish to get rid of 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)
If you come from a different ROM (or stock firmware), make sure that you have performed the Wipe steps above. If you wish to install GApps, select the respective .ZIP file directly afterwards, do not boot into Android before having flashed GApps.
When finished flashing, return to the main menu, choose "Reboot" and then "System", which will cause your phone to boot into our Lineage OS 16.0 - be patient, the first boot after flashing a new ROM takes quite long!
microG
Only valid for the "microG" build variant: After the first installation of this ROM, you need to setup microG.
Please read the instructions given on the LineageOS for microG site, section "Post Install - UnifiedNlp"
Dealing with signed builds
Please note, that my builds are signed with an own key. When you come from a different build, you cannot directly "dirty-flash" this build. You either have to perform a "clean flash" (recommended), or flash "interim-wise" one of my migration builds.
If you don't want to perform a "clean flash" (which means, you will loose your data), you can work with my prepared "Migration Builds". Simply flash the respective Migration Build flavor (A or B) over your existing build. If you had Gapps before, make sure to also flash the respective Gapps (correct android version!) on top before rebooting and wipe cache and dalvik.
A migration build resets the package signatures during each boot and thus supports "dirty-flashing" from a different build.
If you choose to go that path, make sure to immediately perform the OTA update, which will be offered by the Updater app - stay on the migration build as short as possible and UNDER NO CIRCUMSTANCES install or update any app! (if you e.g. had Gapps installed before, deactivate auto-updates).
The migration builds are foreseen to support the following scenarios only:
My Lineage 14.1 (Nougat) Osprey build variant A => my LineageOS 16.0 standard build >> use migration build A
Any Lineage 15.1 (Oreo) LineageOS build => my LineageOS 16.0 standard build >> use migration build A
Any Lineage 16.0 (Pie) LineageOS build => my LineageOS 16.0 standard build >> use migration build A
My Lineage 14.1 (Nougat) Osprey build variant B or C => my LineageOS 16.0 microG build >> use migration build B
One of my previous LineageOS 16.0 microG test builds => my LineageOS 16.0 microG build >> use migration build B
In case you come from my LineageOS 14.1 Osprey builds, please read the detail migration instructions in this thread.
Download sources:
Migration Build A
Migration Build B
Bug reports:
If you have a problem please create a post with these information:
Original Kernel shipped with this rom:
Build Date:
And try to get log as described here
Credits
Android Open Source project (AOSP)
LineageOS project
chil360
squid2
microG project
csagan5 (Bromite)
Whyorean (AuroraStore)
XDA:DevDB Information
[ROM][Unofficial][9.0.0][signed]LineageOS 16.0 for Osprey, ROM for the Moto G 2015
Contributors
MSe1969
Source Code: https://github.com/lin16-microg/local_manifests
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.10.x
Based On: LineageOS
Version Information
Status: Stable
Stable Release Date: 2023-06-24
Created 2020-05-06
Last Updated 2023-06-25

Change Log
June 20th, 2023
Custom build release 2023-06-01
Mulch Webview 114.0.5735.131
microG 0.2.28.231657
AuroraStore 4.2.3
May 12th, 2023
Custom build release 2023-05-01
Mulch Webview 113.0.5672.77
April 21st, 2023
Custom build release 2023-04-01
Mulch Webview 112.0.5615.101
March 22nd, 2023
Custom build release 2023-03-01
Bromite Webview replaced by Mulch Webview 111.0.5563.58
February 21st, 2023
Custom build release 2023-02-01
microG on 0.2.27.223616-3
Spoof apps installed by G*PlayStore
January 8th, 2023
Custom build release 2023-01-01
microG 0.2.26.223616-16
December 12th, 2022
Custom build release 2022-12-01
Bromite Webview 108.0.5359.106
microG 0.2.26.223616-2
November 14th, 2022
Custom build release 2022-11-01
Bromite Webview 106.0.5249.163
microG 0.2.25.223616-10
F-Droid 1.15.3
Timezone data updated to 2022f
October 13th, 2022
Custom build release 2022-10-01
Bromite Webview 105.0.5195.147
microG 0.2.24.223616-61
APN configurations updated
September 11th, 2022
Custom build release 2022-09-01
Many kernel patches
Bromite Webview updated to 104.0.5112.91
microG 0.2.24.214816-30
Contacts app slightly 'de-Googled'
August 12th, 2022
Custom build release 2022-08-01
Bromite Webview updated to 103.0.5060.140
July 16th, 2022
Custom build release 2022-07-01
June 16th, 2022
Custom build release 2022-06-01
Some kernel patches
Bromite Webview on 102.0.5005.96
microG updated to 0.2.24.214816-11
F-Droid 1.15.2
May 9th, 2022
Custom build release 2022-05-01
Some kernel patches
Bromite Webview on 101.0.4951.53
microG updated to 0.2.24.214816-10
Mozilla Location provider on 1.5.0
F-Droid 1.15
April 15th, 2022
Custom build release 2022-04-01
Bromite System Webview updated to 100.0.4896.57
March 17th, 2022
Custom build release 2022-03-01
Bromite System Webview updated to 99.0.4844.58
microG 0.2.24.214816-2
AuroraStore 4.1.1
February 19th, 2022
Custom build release 2022-02-01
F-Droid updated to 1.14, F-Droid privileged extension to 0.2.13
Bromite System Webview updated to 97.0.4692.106
microG updated to 0.2.24.214816-2
January 22nd, 2022
ASB Security string 2022-01-05
Some kernel patches
Backported Audio balance (accessibility settings) from Android 10
December 26th, 2021
Relaunch of LineageOS 16.0 microG builds
ASB Security string 2021-12-05
Bromite Webview 96.0.4664.54
microG 0.22.214516-21
F-Droid 1.13
Many kernel sec. patches
Updated DRM blobs
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
December 18th, 2020
ASB Security string 2020-12-05
System Webview 87.0.4280.101 (Standard variant)
Bromite Webview 87.0.4280.106 (microG build variant)
Updated microG from upstream to 0.2.14.204215-15 (picked until 720b089)
F-Droid updated to 1.10-alpha1-114 (microG build variant)
November 14th, 2020
ASB Security string 2020-11-05
Additional Fix for CVE-2020-15999
Fix of AOSP E-Mail widget
System Webview 86.0.4240.185 (Standard variant)
Bromite Webview 86.0.4240.181 (microG build variant)
Updated microG with fixes in GCM and EN API (microG build variant)
Replaced weak F-Droid signatures with ROM's V2 signatures (microG build variant)
October 13th, 2020
ASB Security string 2020-10-05
Bromite Webview 86.0.4240.73 (microG build variant)
microG 0.2.12.203315 - including "Exposure notification API" for use of Covid tracing apps (microG build variant)
Additional hardening: bionic and constified JNI method tables (microG build variant)
September 13th, 2020
ASB Security string 2020-09-05
Kernel: Wireguard tag v1.0.20200908
System Webview 85.0.4183.101 (Standard build variant)
Bromite Webview 85.0.4183.86 (microG build variant)
Added eSpeak TTS engine (microG build variant)
August 10th, 2020
ASB Security string 2020-08-05
Kernel: Wireguard tag v1.0.20200729
System Webview 84.0.4147.89 (Standard build variant)
Bromite Webview 84.0.4147.113 (microG build variant)
Location of the firewall functionality moved to Network > Data usage in Settings (microG build variant)
July 12th, 2020
ASB Security string 2020-07-05
Kernel: Wireguard tag v1.0.20200623
microG: updated prebuilt GmsCore fom /e/ project to fix FCM registration issues (microG build variant)
F-Droid updated to 1.8 / F-Droid privileged extension updated to 0.2.11 (microG build variant)
Aurorastore updated to 3.2.9 / AuroraServices updated to 1.0.6 (microG build variant)
June 10th, 2020
ASB Security string 2020-06-05
Kernel: Wireguard tag v1.0.20200520
Disabled NearbyMessagingService and DiscoveryService (only relevant, if genuine Gapps are used) to improve WiFi performance, when BT is used
System Webview on 81.0.4044.138 (Standard build variant)
Bromite Webview on 83.0.4103.101 (microG build variant)
Sepolicy: Netmonitor exception f. "Tracker Control" app (microG build variant)
May 6th, 2020
Initial feature list:
OTA Support
Enforcing SELinux
Forked Hybrid-X kernel with native Wireguard support and current sec. patches
System Webview on 81.0.4044.117 (Standard Build)
Below listed initial features apply to the "microG" build variant:
Pre-installed microG and F-Droid same as the LineageOS for microG project
Pre-installed AuroraStore (Version 3.2.8) with AuroraServices 1.0.5
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
Cloudflare as default DNS (instead of Google)
Privacy-preferred default settings
Optional blocking of Facebook- and Google-Tracking
Optional disable captive portal detection
Firewall UI
No submission of IMSI/IMEI to Google when GPS is in use
Default hosts file with many blocked ad/tracking sites
Privacy-enhanced Bromite SystemWebView 81.0.4044.127
Additional restrictions for secondary users
Increased password length

Detail features of "microG" build flavor
1. Pre-installed microG and F-Droid
same as the LineageOS for microG project
2. Pre-installed AuroraStore
works w/o having to enable the "unknown sources feature"
3. Restrict access to /proc/net for user apps
An adapted SELinux policy prevents user apps from accessing the /proc/net pseudo file system, which can be misused to monitor and track the phone's internet traffic. For technical backgrounds, see here. For the legitimate use case of the smart phone owner him/herself monitoring the network traffic to see, what the installed apps do, the app Privacy-Friendly Network Monitor has been bundled.
4. Enhanced Privacy Guard - Sensor permission switches
An own sensor template to control access to motion sensors ('ask' mode) and all other sensors (allowed by default, but can be restricted) has been implemented into the Privacy Guard.
5. Cloudflare (instead of Google) default DNS
Cloudflare DNS has a better privacy policy than Google Public DNS and has DNS-over-TLS and DNS-over-HTTPS. In the deafult DNS settings (as fallback) and network diagnostics, the Cloudflare DNS adresses 1.1.1.1 and 1.0.0.1 are specified as defaults (instead of Google's 8.8.8.8 and 8.8.4.4)
6. Privacy-preferred default settings
When newly installed, the below settings are defaulted, different from standard LineageOS 16.0 (all settings can be changed at any time later):
Privacy Guard is enabled on install (proposal during Setup)
Anonymous LineageOS statistics disabled (proposal during Setup)
The standard browsing app does not get the location runtime permission automatically assigned
Sensitive information is hidden on the lock screen
Camera app: Location tagging disabled by default
Further, when a lock screen protection is set (PIN, pattern, password), the Nfc, Hotspot and airplane mode tiles require authentication and cannot be set without
7. Optional blocking of Facebook- and Google-Tracking
Settings => Network & Internet (scroll down)
When activated, all outgoing connection attempts to Facebook servers will be suppressed.
Same applies to Google, but certain apps on an internal exception list will still be able to connect (AuroraStore, microG, or e.g. NewPipe, if installed)
8. Optional disable captive portal detection
Settings => Network & Internet (scroll down)
When activated, the system will not ping a specific Google server any longer when establishing a WiFi connection to determine, whether a captive portal is being used.
9. No submission of IMSI or phone number to Google/Sony when GPS is in use
GPS also works fine, if no SIM card is present, so there obviously is no benefit for the phone holder (different from other involved parties ) to provide this data . . .
10. Default hosts file with many blocked ad/tracking sites
The system's hosts file redirects a comprehensive list of URLs known to be adware, tracking, etc. to 127.0.0.1 (ipv4) and ::1 (ipv6)
11. Privacy-enhanced Bromite SystemWebView
Instead of the default Chromium System Webview component, the Bromite SystemWebView is used offering more privacy, more ad blocking and less Google tracking.
12. Firewall UI
Settings => Security & Location - Firewall
Lists all apps and allows to restrict Internet access per app in regards to WiFi, mobile network or VPN
This per-app feature is a standard feature in LineageOS, but the UI to show all apps is an Extra (taken from a topic in LineageOS's Gerrit - it may, or may not, become part of the official LineageOS one day)
13. Maximum password length increased to 64
14. Additional restriction options for secondary users
- Disallow app installation option
- Disallow audio recording option
15. Miscellaneous hardening
- hardened bionic lib
- constified JNI method tables

Further Tips & Tricks
Root
The ROM does not come with root baked in. A couple of features in this ROM even reduces the usual need for root.
Nevertheless, if you need/want to grant root permissions to some of your apps, the most popular options are:
Official LineageOS su addon (use 'addonsu-16.0-arm-signed.zip')
Magisk (please search XDA on your own)
Note that I cannot and will not support any issues related to Magisk
microG initial configuration after 1st install
After the first installation of this ROM, you need to setup microG.
Please read the instructions given on the LineageOS for microG site, section "Post Install - UnifiedNlp"
OTA Updates on an encrypted device
In case your device in encrypted and you have flashed apps creating "survival scripts" in /system/addon.d (e.g. Magisk), there *may* be a dependency to files in the data partition.
An OTA update until current TWRP 3.3.1 does not decrypt the data partition, as this is usually not needed - under specific circumstances however, this may lead to unwanted effects (up to a non-booting device!) during an OTA update, if such scripts aim at modifying files located in the data partition. If unsure, rather perform the update manually as dirty-flash in TWRP or - which in general is a good practice - regularly perform backups in TWRP. If you haven't flashed anything on top of my build (except for the LineageOS root addon or Gapps f. variant A, which both is no problem), there shouldn't be any issue.
(This commit in TWRP indicates, that this potential issue will be solved in future TWRP releases).

Hello MSE1969.
When installing external applications or installing applications through the My APK application, the system interface freezes.

LogCat lineage-16.0-20200506-UNOFFICIAL-signed-osprey
LogCat lineage-16.0-20200506-UNOFFICIAL-signed-osprey

johnatanlhm said:
Hello MSE1969.
When installing external applications or installing applications through the My APK application, the system interface freezes.
Click to expand...
Click to collapse
Thanks for the log. First of all, I can't reproduce any issue in regards to installing apk files "from unknown sources". I'll only have time tomorrow to look into the log in detail, but I have some general questions:
My build is signed, as explained in the OP. So you can't just "dirty flash" it over an existing build. Further, if you attempt to "upgrade" a system app, which you previously have extracted from another build via "My APK", this will also cause issues.
So could you please provide some details on your installation? (Clean flash, dirty flash and if DF, what you did? What did you try to "restore" with My APK?)
Thanks

Hello. Mse1969.
answering your questions. I did a clean install and started installing my apps through my apk. There came a time when the system screen froze and returned to normal only when the device was restarted. As I continued the application installation process, the system screen was frozen again.
detail. the system screen freezes during the transition from the my apk screen to the apk installation screen. doing this in sequence, the screen freezes.

johnatanlhm said:
Hello. Mse1969.
answering your questions. I did a clean install and started installing my apps through my apk. There came a time when the system screen froze and returned to normal only when the device was restarted. As I continued the application installation process, the system screen was frozen again.
detail. the system screen freezes during the transition from the my apk screen to the apk installation screen. doing this in sequence, the screen freezes.
Click to expand...
Click to collapse
The log is somehow "ambiguous".
Code:
05-08 16:43:07.029 5814 5991 E tsoft.myapk.fw: Invalid ID 0x00000000.
. . .
05-08 16:43:15.101 433 2216 E : Couldn't opendir /data/app/vmdl921819599.tmp: No such file or directory
05-08 16:43:15.101 433 2216 E installd: Failed to delete /data/app/vmdl921819599.tmp: No such file or directory
. . .
05-08 16:43:28.490 5814 5814 E xxx : onError [email protected]
Not sure how to interpret this - the myapk app seems to talk to Facebook (for me a reason not to use an app at all, but that is not topic of this conversation) and there seems to be an issue with accessing the /data partition by the package manager, but I also see other read errors.
Could you please describe in detail, what you did?
- You said clean flash (good), so you wiped /data and /system, and flashed the ROM - which build variant of my ROM?
- What else did you flash?
- Did you attempt to re-format the /data partition with a different than default file format (maybe you did that way before flashing this ROM)?
- Was it a specific app, which you attempted to install through "my apk", when the issue has occurred? (As indicated before: DO NOT restore system apps)
A general advice: As you started with a clean flash - I recommend to simply try the following, just to make sure:
- make sure to use the most recent official TWRP
- Boot to TWRP
- Wipe the system partition and FORMAT(!) the /data partition
- Reboot TWRP and flash the ROM again
(I had, in different threads and different contexts, this approach finally solve some similarly weird issues)
Regards, M.

Hello MSe1969.
- clean installation. I cleaned Dalvik / ART Cache, System, Data, Cache and installed the ROM.
- I also installed the gapps and the lineageos root along with the ROM.
- I did not try to reformat the / Data partition with a file format other than the standard one.
- The free apps that I have that can be downloaded from the Play Store are installed normally, because I install from the Play Store. But I have other paid apps that were saved by my apk to be installed by my apk.
Detail. I don't use Facebook on osprey. Osprey is now my secondary device.

Hello, first of all thank you very much MSE for the very high quality build you provide us ! I was a long time user of your lineage 14 hardened build (variant b) and I switched lately on the present build (still variant b, ie no gapps).
I made a clean flash, had no problem, all is very functionnal.
Maybe one force close when I try to access the gps property in the menu. I can switch it with the quick tile but whenever I try to access it in pref, it force close.
Edit : Add some log
Code:
05-12 17:42:48.145 D/LocationSettings( 9725): NO dashboard tiles for LocationSettings
05-12 17:42:48.149 D/SettingsActivity( 9725): Executed frag manager pendingTransactions
05-12 17:42:48.174 I/system_server( 1332): NativeAlloc concurrent copying GC freed 130303(5MB) AllocSpace objects, 40(1564KB) LOS objects, 50% free, 11MB/22MB, paused 174us total 214.919ms
05-12 17:42:48.214 I/DeviceIndex( 9725): Skipping: device index is not enabled
05-12 17:42:48.216 W/TileUtils( 9725): Found com.android.settings.Settings$NotificationAppListActivity for intent Intent { act=com.android.settings.action.SETTINGS pkg=com.android.settings } missing metadata com.android.settings.category
05-12 17:42:48.218 I/LocationEnabler( 9725): Location mode has been changed
05-12 17:42:48.219 I/LocationEnabler( 9725): Location mode has been changed
05-12 17:42:48.220 W/TileUtils( 9725): Found org.lineageos.lineageparts.trust.TrustPreferences for intent Intent { act=org.lineageos.lineageparts.action.SETTINGS pkg=org.lineageos.lineageparts } missing metadata
05-12 17:42:48.220 W/TileUtils( 9725): Found org.lineageos.lineageparts.firewall.FirewallPreferences for intent Intent { act=org.lineageos.lineageparts.action.SETTINGS pkg=org.lineageos.lineageparts } missing metadata
05-12 17:42:48.222 I/LocationEnabler( 9725): Location mode has been changed
05-12 17:42:48.226 I/chatty ( 9725): uid=1000(system) com.android.settings identical 2 lines
05-12 17:42:48.228 I/LocationEnabler( 9725): Location mode has been changed
05-12 17:42:48.243 D/SettingsActivity( 9725): No enabled state changed, skipping updateCategory call
05-12 17:42:48.320 W/ActivityManager( 1332): Background start not allowed: service Intent { cmp=com.google.android.gms/org.microg.nlp.ui.SettingInjectorService (has extras) } to com.google.android.gms/org.microg.nlp.ui.SettingInjectorService from pid=9725 uid=1000 pkg=com.android.settings startFg?=false
05-12 17:42:48.321 D/AndroidRuntime( 9725): Shutting down VM
05-12 17:42:48.322 E/AndroidRuntime( 9725): FATAL EXCEPTION: main
05-12 17:42:48.322 E/AndroidRuntime( 9725): Process: com.android.settings, PID: 9725
05-12 17:42:48.322 E/AndroidRuntime( 9725): java.lang.IllegalStateException: Not allowed to start service Intent { cmp=com.google.android.gms/org.microg.nlp.ui.SettingInjectorService (has extras) }: app is in background uid UidRecord{ce13ab6 u0a30 TRNB bg:+1h1m42s346ms idle change:idle procs:1 seq(0,0,0)}
05-12 17:42:48.322 E/AndroidRuntime( 9725): at android.app.ContextImpl.startServiceCommon(ContextImpl.java:1577)
05-12 17:42:48.322 E/AndroidRuntime( 9725): at android.app.ContextImpl.startServiceAsUser(ContextImpl.java:1549)
05-12 17:42:48.322 E/AndroidRuntime( 9725): at android.content.ContextWrapper.startServiceAsUser(ContextWrapper.java:680)
05-12 17:42:48.322 E/AndroidRuntime( 9725): at com.android.settings.location.SettingsInjector$Setting.startService(SettingsInjector.java:561)
05-12 17:42:48.322 E/AndroidRuntime( 9725): at com.android.settings.location.SettingsInjector$StatusLoadingHandler.handleMessage(SettingsInjector.java:457)
05-12 17:42:48.322 E/AndroidRuntime( 9725): at android.os.Handler.dispatchMessage(Handler.java:106)
05-12 17:42:48.322 E/AndroidRuntime( 9725): at android.os.Looper.loop(Looper.java:193)
05-12 17:42:48.322 E/AndroidRuntime( 9725): at android.app.ActivityThread.main(ActivityThread.java:6718)
05-12 17:42:48.322 E/AndroidRuntime( 9725): at java.lang.reflect.Method.invoke(Native Method)
05-12 17:42:48.322 E/AndroidRuntime( 9725): at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:491)
05-12 17:42:48.322 E/AndroidRuntime( 9725): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:858)
05-12 17:42:48.326 W/ActivityManager( 1332): Force finishing activity com.android.settings/.Settings$LocationSettingsActivity
05-12 17:42:48.345 W/BroadcastQueue( 1332): Permission Denial: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to ProcessRecord{2575a2a 4777:com.amazon.venezia/u0a107} (pid=4777, uid=10107) requires android.permission.READ_LOGS due to sender android (uid 1000)
05-12 17:42:48.345 I/Process ( 9725): Sending signal. PID: 9725 SIG: 9
05-12 17:42:48.393 I/ActivityManager( 1332): Process com.android.settings (pid 9725) has died: fore TOP
05-12 17:42:48.393 I/WindowManager( 1332): WIN DEATH: Window{faddc05 u0 com.android.settings/com.android.settings.Settings$LocationSettingsActivity}
05-12 17:42:48.394 W/libprocessgroup( 1332): kill(-9725, 9) failed: No such process
05-12 17:42:48.396 I/Zygote ( 294): Process 9725 exited due to signal (9)
05-12 17:42:48.433 W/SurfaceFlinger( 256): Attempting to destroy on removed layer: AppWindowToken{51b5fb7 token=Token{e6066b6 ActivityRecord{44f3e51 u0 com.android.settings/.Settings$LocationSettingsActivity t231}}}#0
05-12 17:42:48.442 W/libprocessgroup( 1332): kill(-9725, 9) failed: No such process
05-12 17:42:48.442 I/libprocessgroup( 1332): Successfully killed process cgroup uid 1000 pid 9725 in 48ms

nodens76 said:
Hello, first of all thank you very much MSE for the very high quality build you provide us ! I was a long time user of your lineage 14 hardened build (variant b) and I switched lately on the present build (still variant b, ie no gapps).
I made a clean flash, had no problem, all is very functionnal.
Maybe one force close when I try to access the gps property in the menu. I can switch it with the quick tile but whenever I try to access it in pref, it force close.
Edit : Add some log
Click to expand...
Click to collapse
Thanks for the log - on my device, I cannot reproduce the issue, it works fine either way: tile and settings pref.
I can't directly interpret the error based on the log entries - but just to make sure: Have you configured the microG stuff already? (configured location providers, granted permissions, disabled battery optimization etc.)?
I know that if microG isn't fully configured in regards to location providers, some weird things sometimes happen, if location functionality is involved . . .

Hello,
I have an other issue in the microg-version here...
Push-messages (Signal, Whatsapp) are delayed when device sleeps.
Microg is set up correctly and announces an incoming message, but Signal doesn't do anything "due to app idle"
For both Signal and microG Services Core background activity is not restricted and battery usage not optimized.
Any idea?
logfile:
https://www.file-upload.net/download-14074950/logfile.html

maxwell80 said:
Hello,
I have an other issue in the microg-version here...
Push-messages (Signal, Whatsapp) are delayed when device sleeps.
Microg is set up correctly and announces an incoming message, but Signal doesn't do anything "due to app idle"
For both Signal and microG Services Core background activity is not restricted and battery usage not optimized.
Any idea?
logfile:
https://www.file-upload.net/download-14074950/logfile.html
Click to expand...
Click to collapse
Hi, the log confirms your observation, but I don't see any indication, why.
The Osprey isn't my primary device, so I don't want to move Signal to it away from my primary device. I don't have a good idea right now. The open issues in the microG GMS core repo also do not lead me anywhere...
Anybody else in the forum having such an issue?
EDIT: I confirm that this build seems to have difficulties with push messages (test app), but still need to find out why...

MSe1969 said:
EDIT: I confirm that this build seems to have difficulties with push messages (test app), but still need to find out why...
Click to expand...
Click to collapse
Hi!
Push Notification Tester worked for me when I disabled Iptable Block-Script.
The script blocks the connection to the (PNT) server...
High priority notifications after 30 minutes doze were no problem.
But.... it does not change anything with Signal.
I noticed I receive messages in time when the device is charging and in doze, but with delay when unplugged.
And I found this:
https://github.com/signalapp/Signal-Android/issues/8604
https://github.com/signalapp/Signal-Android/issues/8692
It MIGHT be a problem Signal has with Android's power management which changed with Version 9:
https://developer.android.com/about/versions/pie/power
But on the other hand the battery settings of your rom still look more like Lineageos than stock Pie, so I don't know ....
Regards

Hello MSe1969.
I did a new installation, everything went well and the problem did not appear. I leave a LogCat of the installation of the application (s), through My APK and also through the Play Store. I leave this LogCat also for you to look for other errors.

maxwell80 said:
Hi!
Push Notification Tester worked for me when I disabled Iptable Block-Script.
The script blocks the connection to the (PNT) server...
High priority notifications after 30 minutes doze were no problem.
Click to expand...
Click to collapse
First of all, thanks for your feedback. Indeed, I was also doing tests with Push notification tester.
Yes, PNT contacts google, so the block script would need to be disabled. I consider however adding PNT to my exception list
What you write is interesting, because - different from my other LineageOS 16.0 microG builds (one treble GSI and my OP3T build), where PNT works flawlessly, I have an issue with PNT on the Osprey build:
It first does not seem to receive any push message (test screen waiting forever), but they arrive with a delay of several hours! Same happens with the test feature of the Slack app (ok on my other LineageOS 16.0 builds, but hours of delay with the Osprey build). So I consider something to be fixed related to the device-specific parts (kernel?, device-config?, blobs). Same results even after factory-reset and first tests undoing some aggressive power-saving tweaks. So you say, that on your device, PNT works normally and you only have issues with Signal? Or are you saying that the specific case of a high prio message after several minutes of doze works?
To everybody: Any hints and feedback welcome.
maxwell80 said:
But.... it does not change anything with Signal.
I noticed I receive messages in time when the device is charging and in doze, but with delay when unplugged.
And I found this:
https://github.com/signalapp/Signal-Android/issues/8604
https://github.com/signalapp/Signal-Android/issues/8692
It MIGHT be a problem Signal has with Android's power management which changed with Version 9:
https://developer.android.com/about/versions/pie/power
But on the other hand the battery settings of your rom still look more like Lineageos than stock Pie, so I don't know ....
Regards
Click to expand...
Click to collapse
Next to the assumed issue with this ROM, there indeed also seems some issue with Signal itself - I also sometimes (but not really reproducible) had the impression of delays with Signal on my OP3T device . . .
EDIT: Interestingly, the Signal issue #8692 also mentions in one comment an Osprey device, where such issues even occur in older Android versions . . . - does not necessarily mean anything, but who knows . . .?

MSe1969 said:
Yes, PNT contacts google, so the block script would need to be disabled. I consider however adding PNT to my exception list
Click to expand...
Click to collapse
With the block script on it's not possible to download received videos in Whatsapp so maybe you could think about adding another exception as well...?
Regarding the included adblocker - could it make sense to have the option to turn it off? I don't know how a mobile ab works, but I know they can cause trouble on PCs.
MSe1969 said:
So you say, that on your device, PNT works normally and you only have issues with Signal? Or are you saying that the specific case of a high prio message after several minutes of doze works?
Click to expand...
Click to collapse
I checked again:
PNT notifications arrive in time, both normal and high priority.
Whatsapp seems to work too, after I turned battery optimization off.
Signal messages are always delayed (~2 - 20 minutes) when device is in doze and always in time when awake.

maxwell80 said:
With the block script on it's not possible to download received videos in Whatsapp so maybe you could think about adding another exception as well...?
Click to expand...
Click to collapse
No.
Whilst I see your point, this is technically not possible. WA is Facebook and FB is a large pool of IP addresses which are dynamically assigned, redirected and balanced, so you block FB as a whole or you haven't blocked it at all (same with Google).
EDIT: I think I may have misunderstood you. It would be possible to allow only the WA app to connect to FB. Need to think about that...
maxwell80 said:
Regarding the included adblocker - could it make sense to have the option to turn it off? I don't know how a mobile ab works, but I know they can cause trouble on PCs.
Click to expand...
Click to collapse
The AB is a pre-delivered, frequently updated hosts file, which translates known ad hosts into 127.0.0.1 (IPv4) and ::1 (IPv6). You can set an option in the Dev. Options to keep/restore the hosts file on your device and ignore the updates and then use a hosts file root app or simply replace the hosts file with a dummy file.
maxwell80 said:
I checked again:
PNT notifications arrive in time, both normal and high priority.
Whatsapp seems to work too, after I turned battery optimization off.
Signal messages are always delayed (~2 - 20 minutes) when device is in doze and always in time when awake.
Click to expand...
Click to collapse
Thanks for the confirmation; odd, that it's doing this weird stuff on my device, even after a factory reset...

Push notifications - update
maxwell80 said:
I checked again:
PNT notifications arrive in time, both normal and high priority.
Whatsapp seems to work too, after I turned battery optimization off.
Signal messages are always delayed (~2 - 20 minutes) when device is in doze and always in time when awake.
Click to expand...
Click to collapse
Thanks again for your feedback, yes, I can confirm that push notifications as such work perfectly well!
The issue with my phone was very specific:
- I didn't realize, that I had some days back connected my Osprey phone to the Guest WiFi and not the regular WiFi
- The guest WiFi however has a netfilter active to only allow http / https (and as such no other tcp port, which means also no GCM)
- Therefore, push messages did not work at all
- At night, the WiFi is automatically switched off, and via the mobile data connection, the push messages finally arrived - that explains the weird delay of several hours
I am glad, that there is no issue with the ROM (only my own "special" WiFi setup).

This thread is discontinued - LineageOS 17.1 (Android 10) definitely has reached the boundary, of what an old medium range device can handle. Therefore, I have decided to go back to LineageOS 16.0 (see below - I have re-opened the linked LineageOS 16.0 thread).
This thread is dedicated to provide hardened Lineage-OS 17.1 builds with microG included for the Motorola Moto G 2015 (Osprey) with current security patches.
You can consider this thread as a successor of my LineageOS 16.0 Osprey thread
Different from my 16.0 thread, I do not offer a "standard variant", as there is an official LineageOS 17.1 version available for the Osprey device.
Security hardened microG build
Download here
Build is signed
Pre-installed microG and F-Droid like the LineageOS for microG project (own fork)
Pre-installed AuroraStore
Bromite as default browser
eSpeak TTS engine (FOSS TTS solution)
Additional security hardening features listed below
Cloudflare as default DNS (instead of Google)
Privacy-preferred default settings
Optional blocking of Facebook- and Google-Tracking (Settings - Network & Internet)
Optional disable captive portal detection or choose from various providers (default is GrapheneOS and not Google; Settings - Network & Internet)
Firewall UI (under Trust)
Increased max. password length of 64
No submission of IMSI/phone number to Google when GPS is in use
Default hosts file with many blocked ad/tracking sites
Privacy-enhanced Bromite SystemWebView
Extra control of sensor access for additionally installed user apps (Special access under app permissions)
Constified JNI method tables
Current release levels
Security string: 2021-12-05
AOSP tag: 10.0.0_r41
Bromite Webview: M96
Source-code and build instructions
Kernel: https://github.com/LineageOS/android_kernel_motorola_msm8916/tree/lineage-17.1 (official LineageOS)
Build manifest: https://github.com/lin17-microG/local_manifests/tree/lin-17.1-microG
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 2015 (osprey) 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 key to the reboot recovery option and select with power key)
Activate the Developer options (Settings, about phone: tap 7 times on the build number), get into the new menu Developer options and activate, if available, the option "OEM unlocking")
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 or SD card
An unlocked bootloader (read the warnings carefully and backup your data!)
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 official TWRP recovery from the TWRP site. 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, connect the phone via USB to your PC, get it into 'fastboot mode' and enter the following command on your PC:
Code:
fastboot flash recovery TWRP.img
Afterwards, directly boot into 'recovery mode' (enter fastboot reboot on your PC and use the right hardware keys to get into recovery mode) - 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 spefify "Dalvik", "System", "Cache" and "Data" to be wiped. Make sure NOT to wipe "Internal memory" or "SD Card". Swipe to confirm the deletion and get back into the main menu.
NO GApps!
DO NOT attempt to flash GApps on this build! This build is "Google-free" comes with pre-installed AuroraStore and microG.
If you absolutely want Gapps, download and flash the official LineageOS build for this device instead.
Install the ROM
In the TWRP main menu, choose "Install". A file manager appears to let you navigate to your internal memory (path /sdcard) or your SD card (path /external_sd). Choose the .ZIP file of the ROM and swipe to flash. If you update from a previous version of the ROM, you don't need to perform a wipe. If you come from a different ROM (or stock firmware), make sure that you have performed the Wipe steps above. When finished flashing, return to the main menu, choose "Reboot" and then "System", which will cause your phone to boot into our Lineage OS 17.1 - be patient, the first boot after flashing a new ROM takes quite long!
microG
After the first installation of this ROM, you need to setup microG.
Please read the instructions given on the LineageOS for microG site, section "Post Install - UnifiedNlp"
Dealing with signed builds
Please note, that my build is signed with an own key. When you come from a different build, you cannot directly "dirty-flash" this build. You have to perform a "clean flash".
Bug reports:
If you have a problem please create a post with these information:
Original Kernel shipped with this rom:
Build Date:
And try to get log as described here
Credits
Android Open Source project (AOSP)
LineageOS project
althafvly
chil360
microG project
csagan5 (Bromite)
Whyorean (AuroraStore)

Change log
2021-12-18
ASB Security String 2021-12-01
Bromite System Webview and Browser updated to 96.0.4664.54
microG 0.22.214516-21
2021-11-13
ASB Security string 2021-11-05
Bromite System Webview and Browser updated to 94.0.4606.109
2021-10-11
ASB Security string 2021-10-05
Bromite System Webview and Browser updated to 93.0.4577.83
2021-09-12
ASB Security string 2021-09-05
microG 0.2.22.212658-2
2021-08-07
ASB Security string 2021-08-05
Bromite System Webview and Browser updated to 92.0.4515.134
F-Droid updated to 1.13
Fix in WiFi randomization
2021-07-10
ASB Security string 2021-07-05
Bromite System Webview and Browser updated to 91.0.4472.146
microG 0.2.21.212158-2
AuroraStore 4.0.7
2021-06-14
ASB Security string 2021-06-05
Bromite System Webview and Browser updated to 91.0.4472.102
microG 0.2.19211515-9
2021-05-11
ASB Security string 2021-05-05
Bromite System Webview and Browser updated to 90.0.4430.204
microG upstreamed (no version upgrade)
Update: AuroraServices 1.1.1
2021-04-13
ASB Security string 2021-04-01
Bromite System Webview and Browser updated to 90.0.4430.59
F-Droid updated to 1.12
Update: AuroraStore 4.0.4 with AuroraServices 1.1.0
2021-03-08
Security string 2021-03-05
Bromite System webview updated to 88.0.4324.207
Bromite Browser updated to 88.0.4324.207
F-Droid 1.11
microG 0.2.18.204714
2021-02-15
Security string 2021-02-05
Bromite System webview updated to 88.0.4324.141
Bromite Browser updated to 88.0.4324.141
F-Droid 1.10-alpha-234
microG 0.2.17.204714-5
2021-01-15 - Initial build
Pre-installed microG (0.2.16.204713-10) and F-Droid like the LineageOS for microG project (own fork)
Pre-installed AuroraStore
Bromite as default browser (87.0.4280.131)
eSpeak TTS engine (FOSS TTS solution)
Additional security hardening features listed below
Cloudflare as default DNS (instead of Google)
Privacy-preferred default settings
Optional blocking of Facebook- and Google-Tracking (Settings - Network & Internet)
Optional disable captive portal detection or choose from various providers (default is GrapheneOS and not Google; Settings - Network & Internet)
Firewall UI (under Trust)
Increased max. password length of 64
No submission of IMSI/phone number to Google when GPS is in use
Default hosts file with many blocked ad/tracking sites
Privacy-enhanced Bromite SystemWebView (87.0.4280.131)
Extra control of sensor access for additionally installed user apps (Special access under app permissions)
Constified JNI method tables

Hello, I dirty flashed and for now everything seems fine ! Even maybe a little snappier.
I will report any problem.
Thank you for your work !

I did a clean flash (just to be on the safe side) and every works correctly. Thanks!

I would like to discuss an observation I made feeling wise since your previous version based on lineage 16.
First, some context, I started with your ROM on lineage os 14, then 16 and now 17.
In my opinion the 14 had the best feeling. Fast, reactive, even with a load of apps.
Since 16, I have no bug (and thats great !) but the device seems slow, often unresponsive.
I don't have many app running maybe firefox which is RAM eater but if I check this when it's slow it show no more than 1.4go in use on 2.
I was searching what may be the reason and I realize that the 14 had a custom kernel by Squid, one I happily used on other roms too.
Could this be an idea ? Others people feeling the same ?

nodens76 said:
I would like to discuss an observation I made feeling wise since your previous version based on lineage 16.
First, some context, I started with your ROM on lineage os 14, then 16 and now 17.
In my opinion the 14 had the best feeling. Fast, reactive, even with a load of apps.
Since 16, I have no bug (and thats great !) but the device seems slow, often unresponsive.
I don't have many app running maybe firefox which is RAM eater but if I check this when it's slow it show no more than 1.4go in use on 2.
I was searching what may be the reason and I realize that the 14 had a custom kernel by Squid, one I happily used on other roms too.
Could this be an idea ? Others people feeling the same ?
Click to expand...
Click to collapse
Admitting, that the Osprey isn't my primary device, I didn't feel like 16.0 was slow - I was heavily testing 16.0 beginning of the year (as at that time, a couple of things weren't yet working properly) and I had a good impression. As the move to 17.1 wasn't too difficult (I mainly worked with an emulator first to bring up my 17.1 hardened build, which itself indeed was a lot of work), I did not really create "heavy load" on my Osprey for 17.1 - I however don't have a bad impression about the phone's behavior.
Yes, 14.1 had the Squid kernel (which doesn't work on higher releases), which was an excellent piece of work. The 16.0 build also had a Custom kernel (Hybrid-X fork), whilst 17.1 uses the "regular" LineageOS kernel, but I have the impression, that it is still maintained.
I am however no "kernel tuner" and also not good at that. I usually try to apply sec. patches (for which many others do not seem to have the necessary patience), if I maintain the kernel fork myself, but I am neither good at adapting a kernel to a device, nor at general kernel tuning.
If you can point me to a nice Custom kernel for the Osprey, which I can fork and where I would simply have to pick sec. patches, I can give it a try - I could also try chil360's Hybrid-X kernel used for android 10.0 as a base and pick the sec. patches from my 16.0 kernel to see and have you guys judge as well, whether this leads to a better result. However - this is not my highest priority, especially not when I am short on spare time.
But curious to see other people's opinions first.

Yeah may be slow wasn't appropriate, but it feels sometimes a little sluggish. This is my primary device and I tend to have dozen of firefox tabs open so this could be my fault !
My question wasn't to ask you more work, it was more an open question to request reports or advices.
I had a look on the kernel available on osprey and it seems that there're not plenty. I saw that Squid's one hasn't been updated. Thanks for the Hybrid-X, pointer, I will look into that.
I discovered also android GO which should be helpful on low memory devices. With 2go, osprey is not really in this category but who knows. I had a rapid look and found somes scripts which required a flag enabled during compilation. Are you aware of this ? Would this be interesting to dig ?

Nothing related to development, but Ospery in title has a typo error. Just noticed so pointed out

nodens76 said:
First, some context, I started with your ROM on lineage os 14, then 16 and now 17.
In my opinion the 14 had the best feeling. Fast, reactive, even with a load of apps.
Click to expand...
Click to collapse
Official LOS17 has always been laggy for me on osprey. Some people still build LOS14 with monthly security patches for osprey last I checked. They said the hardware can't really handle newer versions of android that well so they stick to nougat. I tested both for like half an hour and I think 14 is better, but I still stuck to 17 because of the automatic LOS updater.

Ritik99 said:
Nothing related to development, but Ospery in title has a typo error. Just noticed so pointed out
Click to expand...
Click to collapse
Thanks for the hint - fixed

knpk13 said:
Official LOS17 has always been laggy for me on osprey. Some people still build LOS14 with monthly security patches for osprey last I checked. They said the hardware can't really handle newer versions of android that well so they stick to nougat. I tested both for like half an hour and I think 14 is better, but I still stuck to 17 because of the automatic LOS updater.
Click to expand...
Click to collapse
@nodens76 @knpk13 (and whoever volunteers as well) - would you like to test something?
I have currently no access to my Osprey device (again next Sunday only) to test myself, but I have created a boot.img based on chil360's Android 10 Osprey kernel (https://github.com/chil360/android_kernel_motorola_msm8916) here:
https://sourceforge.net/projects/lin17-microg/files/MIGRATION/osprey_chil360_10_boot.img/download
The image does not contain the latest patches, but it should give an impression, whether the device is maybe more reactive than using the "official" LineageOS kernel.
To test, please proceed as follows:
Step 1:
Test, whether it boots at all (as indicated, I have currently no access to my Osprey device) - reboot to bootloader and enter the command fastboot boot osprey_chil360_10_boot.img
Step 2:
If step 1 works, reboot to recovery and flash the boot.img via TWRP or from fastboot via the command
fastboot flash boot osprey_chil360_10_boot.img
To get back to the shipped kernel, extract the boot.img from the ROM zip and flash it as described above.
Please let me know, whether you see any difference. If the chil360 kernel is considered "better", I'll apply the latest patches and will ship my build with this kernel in future.
Looking forward to your feedbacks.

Thanks @MSe1969 , I will try and report back.
I also tried on my side some apps cleaning and more agrssive ram managment which were successful to some points.
Edit :
Step 1 : Ok for me ;
Step 2 : Ok, I will use it for the week-end and make a report on monday.

I used the custom kernel for the lasts 3 days and everything works fine. I played a little with the governors of cpu and gpu and I think that the ui seems a litlle less laggy althought there is still some case where It feel very slow (opening spotify and switching on the bluetooth for example).
It's not a revolution but I think that's a little improvment and some fine tuning in the kernel can save a little battery too. I would say "Keep it"

nodens76 said:
I used the custom kernel for the lasts 3 days and everything works fine. I played a little with the governors of cpu and gpu and I think that the ui seems a litlle less laggy althought there is still some case where It feel very slow (opening spotify and switching on the bluetooth for example).
It's not a revolution but I think that's a little improvment and some fine tuning in the kernel can save a little battery too. I would say "Keep it"
Click to expand...
Click to collapse
Thanks a lot for testing. Then I'll patch it and make it part of the next build. Do you have some advice which settings to tweak?

I found lionfish governor has a very good ratio reactivity/battery consumption.
For gpu, I'm not sure, I tried powersave as I don't play but anyway it add lags so ...
I switched i/o schedulers to zen but it's hard to quantify the gain.
Do you have a github to the kernel ? I should try to disect squid's one ...

nodens76 said:
I found lionfish governor has a very good ratio reactivity/battery consumption.
For gpu, I'm not sure, I tried powersave as I don't play but anyway it add lags so ...
I switched i/o schedulers to zen but it's hard to quantify the gain.
Do you have a github to the kernel ? I should try to disect squid's one ...
Click to expand...
Click to collapse
I directly fetched chil360's kernel, but I will fork it and pick all the patches from the 16.0 one, so you could the create some PR's or I could even grant you access if you want...

Thanks for the offer, I first need to build my first kernel ... I'm not new in linux things but never done an android build so I need some practice and first some tooling !

MSe1969 said:
@nodens76 @knpk13 (and whoever volunteers as well) - would you like to test something?
I have currently no access to my Osprey device (again next Sunday only) to test myself
Click to expand...
Click to collapse
Sorry, I currently don't have access to my osprey either. I've lent it to my grandmother.

Quick question: I'm coming from the stock rom, do I have to install Android 6 before I can install your ROM?

r3dd0t said:
Quick question: I'm coming from the stock rom, do I have to install Android 6 before I can install your ROM?
Click to expand...
Click to collapse
Shouldn't there be a Stock Android 6 version available? Does your Stock ROM offer you an update?
I am not 100% sure whether you would have to upgrade to Android 6 first, I had on my Ospreys already Android 6 Stock, when I first flashed LineageOS on them. But in general, it is always a good thing to update, if possible, to the latest offered Stock ROM version.

This is the support thread of PixelFlasher
(PixelFlasher is an open-source self contained GUI tool to facilitate Pixel phone device flashing/rooting/updating with extra features).
Note: This thread is meant for issues and problems faced in Google Pixel 5 devices, generic issues that are device agnostic should be discussed in the main thread.
For full details on where to download / usage and feature set of the tool, visit the main thread at XDA or the project's Github page.
Troubleshooting:
If you need support or assistance, the best way to get is by generating a support file from within PixelFlasher.
You can hit that big Support button on the main screen, or select it from the Help menu.
The generated support.zip file is sanitized (redacted) to keep your sensitive information (username device id ...) private.

Placeholder

Placeholder

Placeholder

just asking if it will work on 4a5g too due to similarities with Pixel5 or not?

creezalird said:
just asking if it will work on 4a5g too due to similarities with Pixel5 or not?
Click to expand...
Click to collapse
Yes it should, although I don't have one and hence I have not tested it, but the program should work for all Pixel phones, and possibly all Google made phones. There is no difference in the process amongst these phones.

New Release: (See full details here on xda or here at github)
April 03, 2022 v2.0.0.0-pre release.
Major refactoring
Added Advanced (Expert) mode UI.
Basic mode keeps UI simple and hides expert features.
Support for setting active slot.
Reboot options (recovery, system, bootloader)
Moved custom ROM options to expert mode.
Added custom flashing to expert mode, can now flash to live (temporary root), or custom flash any image to any partition.
Moved flashing to both slots, disabling verity / verification to expert mode.
Many other improvements, validations and checks.
Updated documentation.

Update:
Version 2.0.1 which includes a hotfix for issue reported here.

New Release:
April 06, 2022 v2.1.0 release
Setup dedicated profile directory.
Put logs in the profile directory and maintain log history.
Plumbing for Linux support (just the flashing part is left to do).
Plumbing for new workflow.
Bugfix to handle name conflict in ROM filename.
Various minor improvements.
Update documentation.

New release:
April 10, 2022 v2.2.0 release
Linux support.
Remember last window position.
List Magisk modules, when Magisk is detected.
Added fastboot verbose option.
Added more checks and validations.
Added more details when errors are encountered.
Cleaner message box (better formatting).
Notice to the user in case fastboot drivers are not setup properly.
More plumbing work for the new upcoming workflow.
Add notes on how to build the Linux version.

New release:
April 11, 2022 v2.2.2 release
Linux Improvements, warn user if selected SDK is old.

New Release:
April 19, 2022 v2.4.0 release
Magisk modules management, enable / disable modules selectively, this comes in handy to disable suspect modules before an upgrade.
Autoscroll the console.
Code cleanup.
April 17, 2022 v2.3.0 release
Optional automatic check for updates feature.
Added help menu links to:
- Report an issue
- Feature Request
- PixelFlasher Project Page
- PixelFlasher Community (Forum)
- Homeboy76's Guide
- V0latyle's Guide
- Open Configuration Folder
- Check for New Version
Icons for menu items.
Link to download Pixel Firmware.
Link to download Android Platform Tools.
Unlock Bootloader.
Lock Bootloader.
SOS (experimental) - disable Magisk modules to get out of bootloop.
Additional flashing options:
- product
- system
- system_ext
- system_other
- vbmeta_system
- vbmeta_vendor
Added sideload flashing option.
Updated documentation.
Further improved console messages for troubleshooting.
Linux build using Github Actions.
Manual build for Kali Linux.

Bug fix release:
April 20, 2022 v2.4.1 release
Bug Fixes: Error message during flashing, introduced by code reshuffle.
It turns out that some Magisk Modules don't set the id, which was expected to be present, which caused Magisk module management screen not to display.

New Release:
April 30, 2022 v3.0.0 release
New workflow, no more package preparation, select options and flash all dynamic.
boot.img caching and management UI with details about the state of boot.img files.
Faster as there is no more need to zip a package.
Other optimizations and improvements.
Update documentation.
Check the main thread or the Github page for details about the new workflow, hope you find it useful.

New Release
May 02, 2022 v3.1.0 release
Fixed a missing step in the final flashing of boot.img
Decoupled Firmware / ROM processing from selecting the files, now we have a separate button to process, makes it clearer and does not give the impression that selecting the file is hanging.
Added splash screen (v3.0.1), the GUI refresh hiccup is gone.
Made the boot.img management delete function more extensive.
I flashed my phone with the May drop using this version.

badabing2003 said:
New Release
May 02, 2022 v3.1.0 release
Fixed a missing step in the final flashing of boot.img
Decoupled Firmware / ROM processing from selecting the files, now we have a separate button to process, makes it clearer and does not give the impression that selecting the file is hanging.
Added splash screen (v3.0.1), the GUI refresh hiccup is gone.
Made the boot.img management delete function more extensive.
I flashed my phone with the May drop using this version.
Click to expand...
Click to collapse
I would like to make a request for your tool if that's ok could you give the option to open up diag for the Pixel 5?

elong7681 said:
I would like to make a request for your tool if that's ok could you give the option to open up diag for the Pixel 5?
Click to expand...
Click to collapse
what is diag?
what Am I going to open?

badabing2003 said:
what is diag?
what Am I going to open?
Click to expand...
Click to collapse
Diag port for using QPST from Qualcomm

elong7681 said:
Diag port for using QPST from Qualcomm
Click to expand...
Click to collapse
Is this what you want?
Code:
adb shell "su -c 'setprop sys.usb.config diag,adb'"
just type this and see if it works, if it does, very easy to add.
I don't have a Qualcomm device to test with

badabing2003 said:
Is this what you want?
Code:
adb shell "su -c 'setprop sys.usb.config diag,adb'"
just type this and see if it works, if it does, very easy to add.
I don't have a Qualcomm device to test with
Click to expand...
Click to collapse
Code:
adb shell
su
resetprop ro.bootmode usbradio
resetprop ro.build.type userdebug
setprop sys.usb.config diag,diag_mdm,adb
diag_mdlog
cancel (ctrl+c) once it starts to "hang" at failed to open diag socket
change usb config (file transfer, no file transfer)
This is how it is done for the Pixel 5

LineageOS 18.1 UNOFFICIAL for 2015 Samsung Galaxy Tab S2 SM-T710 ONLY​Model: SM-T710 (wifi) - gts28wifi - 8" screen, Exynos 5433 SoC, no LTE
This is the ONLY model that the ROM will work on.​
There is NO ROM for the T715 or T815 in this thread. Questions about T715 or T815 will be completely IGNORED.
You MUST READ posts 1-4 (about 10 minute read) before deciding to install this rom. If you think this is an unreasonable request, then stop reading now and find another rom. Thank you.
DISCLAIMER
I am not responsible for lost data, identity theft, lost money, security vulnerabilities, bricked devices or any other hardware or software malfunctions that comes as a result of flashing this rom.
All involved in bringing this build to you are working voluntarily on it in very limited spare time, and their other life commitments have much higher priority. Don't expect a prompt, or even any, response to questions and bug reports.
Before attempting to install this ROM
1. Ask yourself: would bricking your device be a disaster for you? If yes, don't try this ROM! It can't be guaranteed stable and reliable enough to depend on for daily use.
2. BACKUP YOUR DATA AND EXISTING ROM. Be prepared for a complete restore if anything goes wrong.
3. RESEARCH adb, fastboot, Odin/heimdall, and TWRP and how to use them, if not already familiar with these.
What works
1. bluetooth
2. wifi
3. brightness
4. external audio
5. GPS
6. audio through headphone jack
7. audio over bluetooth
8. selinux enforcing
9. DRM level 3 (SD definition)
10. deep sleep
What doesn't work
1. fingerprint. As I wrote in post 1891 at
https://forum.xda-developers.com/t/...t810-t815-t815y.3879302/page-95#post-85533725
I will not spend anymore time looking at fingerprint. If you need fingerpint to work, stay with stock Samsung rom.
2. DRM level 1 (no HD definition). There's more detail in post 1891 above. I will not be trying to achieve level 1 for HD definition. If you need HD definition for your $treaming media, stay with stock Samsung rom.
3. If you charge the device while it's powered off and then want to power it on, you MUST wait at least 30 seconds AFTER disconnecting the charger cable before pressing the power button otherwise you might run into strange boot problems such as the touch screen not working.
4. Possibly other features that I haven't tested or do not use.
Source Code
See FAQ 1 for links in post #2.
Thanks
1. LineageOS team for source code.
2. @retiredtab, @ananjaser1211, @lpedia, @Yogi555 and @CuckooPenguin for spending nearing 1 month fixing the 2 most biggest bugs in 17.1 that plagued users for nearly 10 months: the wifi instability and random reboots. These are discussed in detail at
https://forum.xda-developers.com/t/...rs-running-any-version-of-android-10.4308193/
https://forum.xda-developers.com/t/...rs-running-any-version-of-android-10.4308203/
3. All past contributors of the exynos5433 code.
4. @rINanDO for his lmkd spam fix in 18.1.
5. beta testers: lpedia, Yogi555 and CuckooPenguin
6. lpedia for building the public T710 monthly roms starting April 2022
7. lpedia for suggestions, proof reading and FAQ table format in post #2.

Frequently Asked Questions. You MUST READ this before posting any questions. Thank you.
QuestionAnswerQ1. Can I build this ROM for myself? Where are the source and kernel source files?A1. Yes, you can. The source files are listed below.
Kernel
https://github.com/retiredtab/android_kernel_samsung_universal5433-selinux
Device Tree
https://github.com/retiredtab/android_device_samsung_gts2-common-selinux
https://github.com/retiredtab/android_device_samsung_gts28wifi
Vendor
https://github.com/retiredtab/proprietary_vendor_samsung-selinux
In addition, there is a repo diff file for device-specific tweaks needed to work and a roomservice.xml (local manifest file) file so you can build this rom yourself. The other patch required for tcp/ip is at https://github.com/DerpFest-11/pack...mmit/22fd53a977eeaf4e36be7bf6358ecf2c2737fa5eQ2. Is this ROM suitable as a daily driver?A2. It might be, depending on your requirements. You would need to try it yourself, with your preferred apps, to see if suits your purposes. I've been using it myself since mid August 2021 with no major issues.Q3. What do I do if my app xyz doesn't work?A3. I can't help diagnose problems with random apps I know nothing about. If the app is critically important to you and it doesn't work on this ROM, go back to a ROM where it did work.Q4. Why is this ROM laggy and/or buggy?A4. The device will be noticeably slower if you're using any Gapps package. Consider going gapps-free. A lot of apps will work without Google's services, or there exist alternatives that will. Check out F-Droid, Aurora Store, NewPipe, etc.Q5. What TWRP should I use?A5. You MUST use my unofficial TWRP 3.5.2_9. Get it from
https://sourceforge.net/projects/retiredtab/files/SM-T710/TWRP/Q6. Why should I use this ROM?A6. You don't have to! If you don't like it, go back to your old ROM.Q7. Will you offer monthly updates with security patches?A7. We plan to do so. lpedia will try to update the ROM with the monthly security patches after LineageOS has released them, free time permitting. Each monthly build will be tested to make sure all the "What's working" functionality listed in post #1 still works, before it's made available (which might in some cases delay the release).Q8. I'm a newbie. Can you provide step by step instructions?A8. We simply don't have the time to do this, but there are lots of tutorials, videos, etc online showing how to flash custom ROMs and how to deal with common problems. Newbie questions are also accepted in the XDA General Questions and Answers forum. Having said that, @pflyaz has kindly make a guide in post #37.Q9. Can I report a bug with respect to the ROM?A9. Yes, but you need to supply the following information. If you don't, I won't look at it.
Provide an adb logcat of the problem, and if possible describe how to reproduce it. Note that I can't help if it involves downloading any app I don't already use that requires payment or creating a userid/password.
To get a logcat, open a terminal window on your PC, connect your device to it via USB, and do this:
Bash:
# clear the logcat first
adb logcat -c
# start logcat trace
adb logcat > problem.txt
# reproduce problem
# wait until problem has occurred,
# then stop trace by hitting ctrl-c then zip the problem.txt file
# before uploading it.
Q10. How long will you build 18.1 for this device?A10. For now, 18.1 will be built for all of 2022. After that, we will make a decision depending on a number of factors.Q11. Do I need to erase everything and format my data before installing this ROM for the first time?A11. Under most circumstances, yes.
If you're coming from stock Samsung Android, or an earlier version of LineageOS, or a different custom ROM, you MUST 'clean flash': boot to TWRP recovery, wipe system, data, dalvik/art cache, and cache partitions, then Format Data, then install this ROM.
If you don't do this you're likely to run into problems, such as getting stuck at the boot animation for more than 5 minutes.
The ONLY exception is that if you are coming from LOS 18.1 with the April 5 2022 security patch or later, you can dirty flash the latest security patch build.Q12. What Gapps should I use?A12. Your choice! There are several well-known Gapps packages, such as NikGapps, BiTGapps, OpenGapps, and MindTheGapps. OpenGapps is being removed as per post #11. Do your own research as to what is the most reliable gapps option for you.
I recommend installing the SMALLEST version of any of these, preferably with just the minimum Google services needed to access the Play Store and run apps that depend on Google services.
You could also consider Google alternatives, such as Aurora Store, which mirrors the Google Play Store apps but doesn't need any Google services itself. Many Play Store apps do not actually depend on Google services.
If you are going to install any Gapps package, follow the installation instructions given for that particular package.Q13. I'm having problems with Gapps. Can you tell me why it's not working?A13. I can't answer any questions about Gapps, because I don't use them. Ask your questions on the XDA thread for the Gapps package you're using.Q14. Why isn't my post answered?A14. There are several possible reasons: the question is answered in the FAQ (in which case it will be ignored completely); or it involves apps or operating systems that I don't use; or it's about Gapps, which I don't use; or I simply have not had time to answer any questions.Q15. What speed up/optimization tips do you suggest?A15. These steps can make a big difference to performance:
Turn off animations. Go to Settings > System > Developer options, scroll down to the Drawing section, and set Window, Transition and Animator scale all to "Animation off".
Don't install Gapps unless you depend on something that only Google is providing. Use Aurora Store to get your preferred Play Store apps - they will all be available on Aurora Store. You can choose to access this anonymously or use a Google account.
Don't run more than two apps at the same time. You can probably listen to music in the background and use a web browser at the same time.
Use a web browser with built-in adblock and privacy features, such as Brave.
Use NewPipe to watch your streaming content. It has built in adblock so you don't have to watch forced ads.
Look for apps that are open source, ad-free and lightweight.
Q16. Does this ROM support Magisk so I can root my device?A16. Magisk works with this ROM as reported by beta testsers, but that could change with any revision and changes by Google. However I don't use it myself and can't help with any related issues. Direct any questions about Magisk to the XDA Magisk forum.Q17. Will this ROM ever become official?A17. Never. Official maintainers have onerous responsibilities, and I know my device trees, code organization and git commits will NOT meet LineageOS standards. I'm not able or willing to take on the responsibilities and commit the extra time to supporting an official build.Q18. What is the difference between this ROM and others?A18. This ROM tries to be pure LineageOS with little or no modification. Other ROMs may come with a different UI, different bundled apps, etc.Q19. Will there be any major 18.1 code modifications in the future?A19. I don't anticipate any major modifications. There may be some slight tweaking to the SEpolicy, small bug fixes and minor code cleanup, but all the hard work - getting the rom up and running, and fixing all the major bugs - has been done. This doesn't mean the code is perfect or well organized, but I won't be making any major changes.Q20. Why did you fork the trees?A20. I wanted my own private branch where I could make changes that would only affect my own personal builds.Q21. Can you build a variant of this device? For example, a LTE or S-pen version?A21. I cannot and will not try to build for a variant device if I don't physically have that device. I have to be able to boot and test it myself, and there's no guarantee that I can get those variant features working. So I will NEVER build T715, T810 and T815.Q22. Can I load this ROM on a variant device like LTE or S-pen version?A22. This ROM is for the device explicitly listed and will only work on that device. Do not try to install it on any other device.
ONLY if you are an advanced user and understand TWRP, adb, odin, heimdall, etc, you could try loading it on a LTE or S-pen variant by modifying the updater-script, but be warned: there are likely to be problems, including a bricked device, bootloops, or the ROM not being able to support the functionality of LTE/S-pen.Q23. Does this ROM have any wifi connection issues?A23. This ROM's wifi has been stable on the specified device ever since lpedia and I determined the root cause of the wifi problems back in July 2021 and re-installed the original S2 network 'blobs' with LOS 17.1.Q24. Is this ROM secure so I can do financial transactions?A24. Although Android monthly security patches do improve general security, this ROM's outdated kernel and old proprietary vendor blobs/drivers will NEVER get updates of any kind, and could have significant security holes.
In addition, although the ROM is SElinux enforcing, there's a good chance that the rules written (about 800+ lines of code) have some errors.
If the device is rooted, this would further weaken the security.
With this information, it's up to you to make an informed decision about whether you trust this ROM to be secure enough for your financial transactions.Q25. Okay, I understand the consequences and willing to take the risks outlined, now where can I find the BETA rom?A25. Downloads are at
https://sourceforge.net/projects/lpedia-sf/files/gts28wifi/

Monthly release notes
June 10, 2023 release notes
1. Incorporates June 5 as per https://review.lineageos.org/q/topic:R_asb_2023-06
May 8, 2023 release notes
1. Incorporates May 5 as per https://review.lineageos.org/q/topic:R_asb_2023-05
Apr 18, 2023 release notes
1. Incorporates Apr 5 as per https://review.lineageos.org/q/topic:R_asb_2023-04
March 19, 2023 release notes
1. Incorporates Feb 5 and Mar 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2023-02 and https://review.lineageos.org/q/topic:R_asb_2023-03
Jan 8, 2023 release notes
1. Incorporates Jan 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2023-01
Dec 12 release notes
1. Incorporates Dec 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-12
Nov 12 release notes
1. Incorporates Nov 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-11
Oct 9 release notes
1. Incorporates Oct 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-10
Sept 11 release notes
1. Incorporates Sept 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-09
2. Fixes non working touchscreen and hardware buttons when powering up with power cable plugged in and device turned off. However, the recommendation is still to unplug your charger, wait 30 seconds before pressing power button when your device is turned off.
https://github.com/retiredtab/andro...mmit/7e0657629efedc7f06f6f6fb57199fca0b4e8ea6
https://github.com/retiredtab/andro...mmit/e17c44d2e282d67b243a1c99ce62127e83052c4f
3. Removed settings menu option for fast charging. S2 tablet devices do not support this.
https://github.com/retiredtab/andro...mmit/6db8e690141a98e5cf9e6952c3572c127c0cf8ea
Aug 10 release notes
1. Incorporates Aug 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-08
2. Fixes saving of color profile in live display during a reboot/shutdown.
https://github.com/retiredtab/andro...mmit/01b1ed6ba8c268a19762031415fde1b4e45d4ac3
3. Fixes offline battery charging by writing rules to allow charger to access certain files. This removes the previous workaround. Thanks to @simon-edwards for providing an adb logcat that showed the denials.
https://github.com/retiredtab/andro...mmit/041ae45960170e68410b059f4f709e9c14b79a99
July 23, 2022
1. Added argosd to improve wifi throughput as per https://github.com/retiredtab/andro...mmit/c181aa0c5192e46a5a03d4451e2648481a520c0f
2. Incorporates July 5th security patches as per https://review.lineageos.org/q/topic:R_asb_2022-07
3. Incorporates a workaround for offline charging.
https://github.com/retiredtab/andro...mmit/9d019f0a3be789850a9add18d042990631f05b44
Previously, if the device was off and you plugged in a charger, it would show a battery icon and this would display indefinitely giving no sign of charging animation. With this workaround, the battery icon is displayed for a few seconds and then a white circle with a charge symbol inside it is shown to indicate it's charging.
After a few seconds, the screen will go blank and continue charging. The side effect of this workaround is that in order to turn on the device, you first must unplug the charger and then turn on your device. If you try to turn on the device with the charger cable plugged in, it won't turn on.
June 12, 2022
1. Removed vibrator code from gts2-common as wifi only models don't have vibrator motor (only LTE models).
https://github.com/retiredtab/andro...mmit/e54aee73a98e3cef6e74f96c1815cec9c82ff10d
https://github.com/retiredtab/andro...mmit/dd846b06378182398c55b57b2edc2537369bd509
2. Incorporates June 5th security patches as per https://review.lineageos.org/q/topic:R_asb_2022-06
May 12, 2022
1. Added overlay for led capacitive led buttons as per https://github.com/retiredtab/andro...mmit/83551570e4627a0e353e358787f83aa65484b528
2. Incorporates May 5th security patches as per https://review.lineageos.org/q/topic:R_asb_2022-05
April 11, 2022
1. YOU MUST read posts 1-4 if you haven't already
2. First public BETA release of selinux enforcing T710 build.
3. Incorporates April 5th security patches as per https://review.lineageos.org/q/topic:R_asb_2022-04
4. BACKUP your data because YOU MUST wipe dalvik/cache, cache, system, data and internal storage partitions in TWRP and FORMAT DATA after as this is the first release of this build. You cannot dirty flash at all. See FAQ.

Reserved.

Initial public build called lineage-18.1-20220411-UNOFFICIAL-gts28wifi.zip. The sha256sum file is provided as well to ensure integrity of download.
lpedia has tested all the functionality as to what works as per post #1 before uploading the build. Having said that, there's still a chance it won't work on your device due to human error, your configuration, your apps, etc. If it won't boot, always start with a complete wipe of everything and format your data. This is known has a clean install. Backup your data before a clean install.
April 11, 2022
1. YOU MUST read posts 1-4 if you haven't already
2. First public BETA release of selinux enforcing T710 build.
3. Incorporates April 5th security patches as per https://review.lineageos.org/q/topic:R_asb_2022-04
4. BACKUP your data because YOU MUST wipe dalvik/cache, cache, system, data and internal storage partitions in TWRP and FORMAT DATA after as this is the first release of this build. You cannot dirty flash at all. See FAQ Q11.

Congratulations on the awesome release!

New build called lineage-18.1-20220512-UNOFFICIAL-gts28wifi.zip
lpedia has tested all the functionality as to what works as per post #1 before uploading the build. Having said that, there's still a chance it won't work on your device due to human error, your configuration, your apps, etc. If it won't boot, always start with a complete wipe of everything and format your data. This is known has a clean install. Backup your data before a clean install.
May 12, 2022 release notes
1. YOU MUST read posts 1-4 if you haven't already
2. Added overlay for led capacitive led buttons as per https://github.com/retiredtab/andro...mmit/83551570e4627a0e353e358787f83aa65484b528
3. Incorporates May 5th security patches as per https://review.lineageos.org/q/topic:R_asb_2022-05
4. If you are upgrading from the April 11 build, you may dirty flash the May 10 build. If you are NOT coming from the April 11th, 2022 build, you MUST BACKUP your data because YOU MUST wipe dalvik/cache, cache, system, data and internal storage partitions in TWRP and FORMAT DATA. You cannot dirty flash at all. See FAQ Q11.

Hi there, thanks for your ROM. I would like to report a bug with using it.
May 12, 2022 release "lineage-18.1-20220512-UNOFFICIAL-gts28wifi" with "open_gapps-arm-11.0-pico-20220503".
All factory resetted through TWRP, after flashing and booting the device it is stuck on "Just a sec..." when selecting set up offlie. If you try to set it up over wifi it is stuck on "Getting your tablet ready."
I've included my logcat, if you need more info or another reproduction please let me know.
Thanks!
Kim

kimrosebush said:
Hi there, thanks for your ROM. I would like to report a bug with using it.
May 12, 2022 release "lineage-18.1-20220512-UNOFFICIAL-gts28wifi" with "open_gapps-arm-11.0-pico-20220503".
All factory resetted through TWRP, after flashing and booting the device it is stuck on "Just a sec..." when selecting set up offlie. If you try to set it up over wifi it is stuck on "Getting your tablet ready."
I've included my logcat, if you need more info or another reproduction please let me know.
Thanks!
Kim
Click to expand...
Click to collapse
Hi, @kimrosebush. Thank you for sending a logcat.
This kind of problem is often because the gapps package isn't quite right for some reason. Google Setup needs the underlying Google Play services to be present and working properly. This line from your logcat suggests they are not:
Code:
05-12 22:29:54.077 4147 4225 W GooglePlayServicesUtil: com.google.android.setupwizard requires Google Play services, but they are missing.
A few questions about the process you followed:
1. What OS was on the T710 before you began? If it was stock Android, was it the latest version available?
2. Did you install the correct version of TWRP (see Q5 in the FAQ)?
3. When you say "All factory resetted through TWRP", what did you actually do?
4. When did you install the gapps package? Just after the ROM, before first boot?
Have you checked whether everything else is working? In particular, is wifi connecting and working properly? [Pressing the Home button should get you out of the stuck Google Setup.]

lpedia said:
Hi, @kimrosebush. Thank you for sending a logcat.
This kind of problem is often because the gapps package isn't quite right for some reason. Google Setup needs the underlying Google Play services to be present and working properly. This line from your logcat suggests they are not:
Code:
05-12 22:29:54.077 4147 4225 W GooglePlayServicesUtil: com.google.android.setupwizard requires Google Play services, but they are missing.
A few questions about the process you followed:
1. What OS was on the T710 before you began? If it was stock Android, was it the latest version available?
2. Did you install the correct version of TWRP (see Q5 in the FAQ)?
3. When you say "All factory resetted through TWRP", what did you actually do?
4. When did you install the gapps package? Just after the ROM, before first boot?
Have you checked whether everything else is working? In particular, is wifi connecting and working properly? [Pressing the Home button should get you out of the stuck Google Setup.]
Click to expand...
Click to collapse
Hey @lpedia thanks for the reply.
1. LineageOS 17.1 I believe was the build.
2. Yes I installed the provided version.
3. I formatted all partitions except SD, flashed the images and then formatted the SD to ensure a completely wiped device.
4. Just after the ROM.
I tried a few times further, then I decided to go for the 'full' OpenGApps package; once I used this one and attempted the offline setup again I was able to proceed further in configuring the tablet.
Thanks for the hint in the right direction. Am glad to be on Android 11 now.
Kind Regards,
Kim

I will be removing opengapps from the FAQ because for several months now (starting around Oct 2021), the opengapps project has been releasing UNTESTED builds that results in bootloops or non working gapps services. Despite numerous requests/posts from the community to slow down the releases and actually TEST THEM BEFORE release, the latest May 3, 2022 shows there is still room for improvement.
This thread in the opengapps forum is just the latest example. Details of UNTESTED builds are also in the same megathread below.
https://forum.xda-developers.com/t/...rsions-devices.3098071/page-367#post-86885091
It's also shown up in other roms like
https://forum.xda-developers.com/t/...7-1-04-30-2022.3937956/page-100#post-86885353
This would be a good time for user to do their own research on which gapps is best for them or use NONE at all. I use Aurora Store myself.
Just a reminder that the builds we release are TESTED and verified to have all the functionality as listed in post #1.

kimrosebush said:
Hey @lpedia thanks for the reply.
1. LineageOS 17.1 I believe was the build.
2. Yes I installed the provided version.
3. I formatted all partitions except SD, flashed the images and then formatted the SD to ensure a completely wiped device.
4. Just after the ROM.
I tried a few times further, then I decided to go for the 'full' OpenGApps package; once I used this one and attempted the offline setup again I was able to proceed further in configuring the tablet.
Thanks for the hint in the right direction. Am glad to be on Android 11 now.
Kind Regards,
Kim
Click to expand...
Click to collapse
Good to hear!
Note that you don't have to be quite so brutal about wiping absolutely everything for a 'clean' flash. I manually wipe Dalvik / ART Cache, Cache, and System, and then Format Data. I have never reformatted the SD.
If you have any further trouble, I suggest you try starting again with a clean flash and a different gapps package, or try doing without any gapps, as @retiredtab has recommended in the post above.
In my experience, some gapps packages, or sometimes just a particular version of a gapps package, don't work with some ROMs. I have not tried opengapps, but I can confirm that BiTGApps-arm-11.0.0-R45_signed.zip does work on my T710 with this particular ROM version.
I personally like BiTGapps because it installs only the bare minimum needed (Google services and Play Store; doesn't even automatically run Google Setup) and doesn't have to be installed before first boot. So it's possible to install LOS, boot the system, make sure everything's working, then go back into TWRP and install gapps. If any problems turn up, this approach also makes it easier to tell whether it's something to do with LOS or with gapps.
You could also try running LOS without any gapps, and if you decide you want gapps after all, install BiTGapps without having to clean-flash and start again.

I just installed this rom two days ago. It has been working great. Today, however, I noticed that Trust gave me a message about the build having public keys. Yesterday, I don't recall getting that message. Also, root checker says "root access is not properly installed." The last time I checked, it was not rooted. Finally, my CRAVE (a Canadian streaming service) app won't play videos but gives a "device is rooted" message. Netflix works however.
Would you have any idea what is going on or how I should deal with this?
Thanks,
MC

Dr_MC said:
Today, however, I noticed that Trust gave me a message about the build having public keys. Yesterday, I don't recall getting that message.
Click to expand...
Click to collapse
On April 6, @lpedia and I had a PM discussion about signing builds.
lpedia wrote
Code:
"About signing builds ... an issue with just using the default test-keys signature is that someone can easily create
their own builds and pass them off as someone else's, possibly adding malicious or just plain bad code, and their
package would look just like the original."
I replied
Code:
"For our purposes, maybe we should just include the sha256sum and recommend that the users verify
them to ensure the file downloaded correctly and it wasn't modified?"
To get stop seeing that trust message, goto settings, privacy, trust, turn off build signature.
Dr_MC said:
Also, root checker says "root access is not properly installed." The last time I checked, it was not rooted. Finally, my CRAVE (a Canadian streaming service) app won't play videos but gives a "device is rooted" message. Netflix works however.
Click to expand...
Click to collapse
I can't see the Crave app in Aurora Store. I use the app devcheck to check for root access and the screenshot clearly shows it's not rooted.
There's nothing in my code to enable root. In fact, I don't even want root on my devices.
For Crave, you can try using Magisk and it's hide root function to see if that will fool Crave into thinking the device is not rooted.

Dr_MC said:
Also, root checker says "root access is not properly installed." The last time I checked, it was not rooted.
Click to expand...
Click to collapse
I did installed the above root checker app and got the same message. That is, the T710 rom, by default is NOT rooted. I don't know why Crave would say it's rooted.
I believe root checker's main function is to verify that your rom is "rooted" so when it says "root access is not properly installed.", it's trying to tell you that your attempt to use Magisk or similar type app to root the rom was unsuccessful.
BTW, you are better off using devcheck as it's an excellent ad-free utility that I use on a regular basis to help develop this rom vs the ad-infested root checker app. While devcheck isn't open source, it's written by flar2 who is a xda member here.

Dr_MC said:
Also, root checker says "root access is not properly installed." The last time I checked, it was not rooted.
Click to expand...
Click to collapse
Root Checker Basic says "Sorry! Root access is not properly installed on this device" when asked to confirm root status on an unrooted device. So as far as that app's concerned, it just means "I can't confirm it's rooted". Which is to be expected if it isn't rooted and you haven't even tried to root it.
If that isn't the app you're using, see if you can find out what it means to your particular root-checker app.
Dr_MC said:
Finally, my CRAVE (a Canadian streaming service) app won't play videos but gives a "device is rooted" message. Netflix works however.
Click to expand...
Click to collapse
Did the CRAVE app work on this device when it had the stock Samsung ROM? Do you have to register devices to receive this service? If so, might it need to be re-registered? Because its device ID will have changed.

Thanks for suggesting devcheck. It says I'm unrooted. Perhaps Crave noticed the unlocked bootloader or the custom ROM.

It did work with stock. It was registered, twice in fact. I deleted both, registered it again. The ap still says I'm rooted. Oh well, that's ok, I can use crave through a browser.
BTW do you know where I can find the stock keyboard?
Thanks

Dr_MC said:
BTW do you know where I can find the stock keyboard?
Click to expand...
Click to collapse
If you mean the Samsung keyboard - sorry, no, I don't. I switched to a different keyboard years ago. Google's GBoard has similar functionality, I think. MS SwiftKey is OK, too - has the best (most relevant) suggested text of any of the keyboards I've tried.

ROM working fine for me after trial and error with various gapps. FWIW I ran into the "just a sec " with opengapps. I finally had some joy by flashing the rom, but not gapps. Boot the ROM and completely setup it up Lineage. Then I restarted and flashed open gapps. When I rebooted everything came uo fine and has been solid eversince. Kudos your you gentlemen for fixing the Wifi ! Its been nice to have it work stably.

LineageOS 18.1 UNOFFICIAL for 2015 Samsung Galaxy Tab S2 SM-T810 ONLY​Model: SM-T810 (wifi) - gts210wifi - 9.7" screen, Exynos 5433 SoC, no LTE
This is the ONLY model that the ROM will work on.​
There is NO ROM for the T715 or T815 in this thread. Questions about T715 or T815 will be completely IGNORED.
You MUST READ posts 1-4 (about 10 minute read) before deciding to install this rom. If you think this is an unreasonable request, then stop reading now and find another rom. Thank you.
DISCLAIMER
I am not responsible for lost data, identity theft, lost money, security vulnerabilities, bricked devices or any other hardware or software malfunctions that comes as a result of flashing this rom.
All involved in bringing this build to you are working voluntarily on it in very limited spare time, and their other life commitments have much higher priority. Don't expect a prompt, or even any, response to questions and bug reports.
Before attempting to install this ROM
1. Ask yourself: would bricking your device be a disaster for you? If yes, don't try this ROM! It can't be guaranteed stable and reliable enough to depend on for daily use.
2. BACKUP YOUR DATA AND EXISTING ROM. Be prepared for a complete restore if anything goes wrong.
3. RESEARCH adb, fastboot, Odin/heimdall, and TWRP and how to use them, if not already familiar with these.
What works
1. bluetooth
2. wifi
3. brightness
4. external audio
5. GPS
6. audio through headphone jack
7. audio over bluetooth
8. selinux enforcing
9. DRM level 3 (SD definition)
10. deep sleep
What doesn't work
1. fingerprint. As I wrote in post 1891 at
https://forum.xda-developers.com/t/...t810-t815-t815y.3879302/page-95#post-85533725
I will not spend anymore time looking at fingerprint. If you need fingerpint to work, stay with stock Samsung rom.
2. DRM level 1 (no HD definition). There's more detail in post 1891 above. I will not be trying to achieve level 1 for HD definition. If you need HD definition for your $treaming media, stay with stock Samsung rom.
3. If you charge the device while it's powered off and then want to power it on, you MUST wait at least 30 seconds AFTER disconnecting the charger cable before pressing the power button otherwise you might run into strange boot problems such as the touch screen not working.
4. Possibly other features that I haven't tested or do not use.
Source Code
See FAQ 1 for links in post #2.
Thanks
1. LineageOS team for source code.
2. @retiredtab, @ananjaser1211, @lpedia, @Yogi555 and @CuckooPenguin for spending nearing 1 month fixing the 2 most biggest bugs in 17.1 that plagued users for nearly 10 months: the wifi instability and random reboots. These are discussed in detail at
https://forum.xda-developers.com/t/...rs-running-any-version-of-android-10.4308193/
https://forum.xda-developers.com/t/...rs-running-any-version-of-android-10.4308203/
3. All past contributors of the exynos5433 code.
4. @rINanDO for his lmkd spam fix in 18.1.
5. beta testers: lpedia, Yogi555 and CuckooPenguin
6. Yogi555 for building the public T810 monthly roms starting April 2022
7. lpedia for suggestions, proof reading and FAQ table format in post #2.

Frequently Asked Questions. You MUST READ this before posting any questions. Thank you.
QuestionAnswerQ1. Can I build this ROM for myself? Where are the source and kernel source files?A1. Yes, you can. The source files are listed below.
Kernel
https://github.com/retiredtab/android_kernel_samsung_universal5433-selinux
Device Tree
https://github.com/retiredtab/android_device_samsung_gts2-common-selinux
https://github.com/retiredtab/android_device_samsung_gts210wifi
Vendor
https://github.com/retiredtab/proprietary_vendor_samsung-selinux
In addition, there is a repo diff file for device-specific tweaks needed to work and a roomservice.xml (local manifest file) file so you can build this rom yourself. The other patch required for tcp/ip is at https://github.com/DerpFest-11/pack...mmit/22fd53a977eeaf4e36be7bf6358ecf2c2737fa5eQ2. Is this ROM suitable as a daily driver?A2. It might be, depending on your requirements. You would need to try it yourself, with your preferred apps, to see if suits your purposes. I've been using it myself since mid August 2021 with no major issues.Q3. What do I do if my app xyz doesn't work?A3. I can't help diagnose problems with random apps I know nothing about. If the app is critically important to you and it doesn't work on this ROM, go back to a ROM where it did work.Q4. Why is this ROM laggy and/or buggy?A4. The device will be noticeably slower if you're using any Gapps package. Consider going gapps-free. A lot of apps will work without Google's services, or there exist alternatives that will. Check out F-Droid, Aurora Store, NewPipe, etc.Q5. What TWRP should I use?A5. You MUST use TWRP 3.5.2_9. Get it from
https://dl.twrp.me/gts210wifi/Q6. Why should I use this ROM?A6. You don't have to! If you don't like it, go back to your old ROM.Q7. Will you offer monthly updates with security patches?A7. We plan to do so. Yogi555 will try to update the ROM with the monthly security patches after LineageOS has released them, free time permitting. Each monthly build will be tested to make sure all the "What works" functionality listed in post #1 still works, before it's made available (which might in some cases delay the release).Q8. I'm a newbie. Can you provide step by step instructions?A8. We simply don't have the time to do this, but there are lots of tutorials, videos, etc online showing how to flash custom ROMs and how to deal with common problems. Newbie questions are also accepted in the XDA General Questions and Answers forum. Having said that, @pflyaz has kindly make a guide in in post #16.Q9. Can I report a bug with respect to the ROM?A9. Yes, but you need to supply the following information. If you don't, I won't look at it.
Provide an adb logcat of the problem, and if possible describe how to reproduce it. Note that I can't help if it involves downloading any app I don't already use that requires payment or creating a userid/password.
To get a logcat, open a terminal window on your PC, connect your device to it via USB, and do this:
Bash:
# clear the logcat first
adb logcat -c
# start logcat trace
adb logcat > problem.txt
# reproduce problem
# wait until problem has occurred,
# then stop trace by hitting ctrl-c then zip the problem.txt file
# before uploading it.
Q10. How long will you build 18.1 for this device?A10. For now, 18.1 will be built for all of 2022. After that, we will make a decision depending on a number of factors.Q11. Do I need to erase everything and format my data before installing this ROM for the first time?A11. Under most circumstances, yes.
If you're coming from stock Samsung Android, or an earlier version of LineageOS, or a different custom ROM, you MUST 'clean flash': boot to TWRP recovery, wipe system, data, dalvik/art cache, and cache partitions, then Format Data, then install this ROM.
If you don't do this you're likely to run into problems, such as getting stuck at the boot animation for more than 5 minutes.
The ONLY exception is that if you are coming from LOS 18.1 with the April 5 2022 security patch or later, you can dirty flash the latest security patch build.Q12. What Gapps should I use?A12. Your choice! There are several well-known Gapps packages, such as NikGapps, BiTGapps, OpenGapps, and MindTheGapps. OpenGapps is being removed as per post #14. Do your own research as to what is the most reliable gapps option for you.
I recommend installing the SMALLEST version of any of these, preferably with just the minimum Google services needed to access the Play Store and run apps that depend on Google services.
You could also consider Google alternatives, such as Aurora Store, which mirrors the Google Play Store apps but doesn't need any Google services itself. Many Play Store apps do not actually depend on Google services.
If you are going to install any Gapps package, follow the installation instructions given for that particular package.Q13. I'm having problems with Gapps. Can you tell me why it's not working?A13. I can't answer any questions about Gapps, because I don't use them. Ask your questions on the XDA thread for the Gapps package you're using.Q14. Why isn't my post answered?A14. There are several possible reasons: the question is answered in the FAQ (in which case it will be ignored completely); or it involves apps or operating systems that I don't use; or it's about Gapps, which I don't use; or I simply have not had time to answer any questions.Q15. What speed up/optimization tips do you suggest?A15. These steps can make a big difference to performance:
Turn off animations. Go to Settings > System > Developer options, scroll down to the Drawing section, and set Window, Transition and Animator scale all to "Animation off".
Don't install Gapps unless you depend on something that only Google is providing. Use Aurora Store to get your preferred Play Store apps - they will all be available on Aurora Store. You can choose to access this anonymously or use a Google account.
Don't run more than two apps at the same time. You can probably listen to music in the background and use a web browser at the same time.
Use a web browser with built-in adblock and privacy features, such as Brave.
Use NewPipe to watch your streaming content. It has built in adblock so you don't have to watch forced ads.
Look for apps that are open source, ad-free and lightweight.
Q16. Does this ROM support Magisk so I can root my device?A16. Magisk works with this ROM as reported by beta testsers, but that could change with any revision and changes by Google. However I don't use it myself and can't help with any related issues. Direct any questions about Magisk to the XDA Magisk forum.Q17. Will this ROM ever become official?A17. Never. Official maintainers have onerous responsibilities, and I know my device trees, code organization and git commits will NOT meet LineageOS standards. I'm not able or willing to take on the responsibilities and commit the extra time to supporting an official build.Q18. What is the difference between this ROM and others?A18. This ROM tries to be pure LineageOS with little or no modification. Other ROMs may come with a different UI, different bundled apps, etc.Q19. Will there be any major 18.1 code modifications in the future?A19. I don't anticipate any major modifications. There may be some slight tweaking to the SEpolicy, small bug fixes and minor code cleanup, but all the hard work - getting the rom up and running, and fixing all the major bugs - has been done. This doesn't mean the code is perfect or well organized, but I won't be making any major changes.Q20. Why did you fork the trees?A20. I wanted my own private branch where I could make changes that would only affect my own personal builds.Q21. Can you build a variant of this device? For example, a LTE or S-pen version?A21. I cannot and will not try to build for a variant device if I don't physically have that device. I have to be able to boot and test it myself, and there's no guarantee that I can get those variant features working. So I will NEVER build T715, T810 and T815.Q22. Can I load this ROM on a variant device like LTE or S-pen version?A22. This ROM is for the device explicitly listed and will only work on that device. Do not try to install it on any other device.
ONLY if you are an advanced user and understand TWRP, adb, odin, heimdall, etc, you could try loading it on a LTE or S-pen variant by modifying the updater-script, but be warned: there are likely to be problems, including a bricked device, bootloops, or the ROM not being able to support the functionality of LTE/S-pen.Q23. Does this ROM have any wifi connection issues?A23. This ROM's wifi has been stable on the specified device ever since lpedia and I determined the root cause of the wifi problems back in July 2021 and re-installed the original S2 network 'blobs' with LOS 17.1.Q24. Is this ROM secure so I can do financial transactions?A24. Although Android monthly security patches do improve general security, this ROM's outdated kernel and old proprietary vendor blobs/drivers will NEVER get updates of any kind, and could have significant security holes.
In addition, although the ROM is SElinux enforcing, there's a good chance that the rules written (about 800+ lines of code) have some errors.
If the device is rooted, this would further weaken the security.
With this information, it's up to you to make an informed decision about whether you trust this ROM to be secure enough for your financial transactions.Q25. Okay, I understand the consequences and willing to take the risks outlined, now where can I find the BETA rom?A25. Downloads are at
https://sourceforge.net/projects/retiredtab/files/SM-T810/18.1/

Monthly release notes
June 9, 2023 release notes
1. Incorporates June 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2023-06
May 9 release notes
1. Incorporates May 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2023-05
Apr 18 release notes
1. Incorporates Apr 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2023-04
Mar 19 release notes
1. Incorporates Mar 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2023-03
Feb 17 release notes
1. Incorporates Feb 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2023-02
Jan 11. 2023 release notes
1. Incorporates Jan 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2023-01
Dec 12 release notes
1. Incorporates Dec 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-12
Nov 21 release notes
1. Incorporates Nov 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-11
Oct 9 release notes
1. Incorporates Oct 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-10
Sept 11 release notes
1. Incorporates Sept 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-09
2. Fixes non working touchscreen and hardware buttons when powering up with power cable plugged in and device turned off. However, the recommendation is still to unplug your charger, wait 30 seconds before pressing power button when your device is turned off.
https://github.com/retiredtab/andro...mmit/7e0657629efedc7f06f6f6fb57199fca0b4e8ea6
https://github.com/retiredtab/andro...mmit/e17c44d2e282d67b243a1c99ce62127e83052c4f
3. Removed settings menu option for fast charging. S2 tablet devices do not support this.
https://github.com/retiredtab/andro...mmit/6db8e690141a98e5cf9e6952c3572c127c0cf8ea
Aug 10 release notes
1. Incorporates Aug 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-08
2. Fixes saving of color profile in live display during a reboot/shutdown.
https://github.com/retiredtab/andro...mmit/01b1ed6ba8c268a19762031415fde1b4e45d4ac3
3. Fixes offline battery charging by writing rules to allow charger to access certain files. This removes the previous workaround. Thanks to @simon-edwards for providing an adb logcat that showed the denials.
https://github.com/retiredtab/andro...mmit/041ae45960170e68410b059f4f709e9c14b79a99
July 13, 2022
1. Added argosd to improve wifi throughput as per https://github.com/retiredtab/andro...mmit/c181aa0c5192e46a5a03d4451e2648481a520c0f
2. Incorporates July 5th security patches as per https://review.lineageos.org/q/topic:R_asb_2022-07
June 11, 2022
1. Removed vibrator code from gts2-common as wifi only models don't have vibrator motor (only LTE models).
https://github.com/retiredtab/andro...mmit/e54aee73a98e3cef6e74f96c1815cec9c82ff10d
https://github.com/retiredtab/andro...mmit/dd846b06378182398c55b57b2edc2537369bd509
2. Incorporates June 5th security patches as per https://review.lineageos.org/q/topic:R_asb_2022-06
May 10, 2022
1. Added overlay for led capacitive led buttons as per https://github.com/retiredtab/andro...mmit/83551570e4627a0e353e358787f83aa65484b528
2. Incorporates May 5th security patches as per https://review.lineageos.org/q/topic:R_asb_2022-05
April 10, 2022
1. YOU MUST read posts 1-4 if you haven't already
2. First public BETA release of selinux enforcing T810 build.
3. Incorporates April 5th security patches as per https://review.lineageos.org/q/topic:R_asb_2022-04
4. BACKUP your data because YOU MUST wipe dalvik/cache, cache, system, data and internal storage partitions in TWRP and FORMAT DATA after as this is the first release of this build. You cannot dirty flash at all. See FAQ.

Reserved.

Initial public build called lineage-18.1-20220410-UNOFFICIAL-gts210wifi.zip. The sha256sum file is provided as well to ensure integrity of download.
Yogi555 has tested all the functionality as to what works as per post #1 before uploading the build. Having said that, there's still a chance it won't work on your device due to human error, your configuration, your apps, etc. If it won't boot, always start with a complete wipe of everything and format your data. This is known has a clean install. Backup your data before a clean install.
April 10, 2022
1. YOU MUST read posts 1-4 if you haven't already
2. First public BETA release of selinux enforcing T810 build.
3. Incorporates April 5th security patches as per https://review.lineageos.org/q/topic:R_asb_2022-04
4. BACKUP your data because YOU MUST wipe dalvik/cache, cache, system, data and internal storage partitions in TWRP and FORMAT DATA after as this is the first release of this build. You cannot dirty flash at all. See FAQ Q11.

Tried the beta build and everything seems to be working. I'll observe once it goes into deep sleep and see if WiFi will lose connection (usually 24 hours) on the other 18.1 build. Loaded all my paid apps without issues. Only gripe is the Netflix with DRM L3. Will look into another thread where they spoofed it.

I'll give it a try. Other LOS 18.1 roms wifi not working.

@retiredtab, @ananjaser1211, @lpedia, @Yogi555 and @CuckooPenguin thx very much for your work.
Until yesterday mine was on ripees build from 20211103 which was stable and working but didn't seem to get any further updates than 20211208.
Clean installation went well although I didn't follow "Q5" and used latest TWRP which is 3.6.1_9-0.
Flashed it with Magisk 23. (wanted to make sure that Gapps didn't interfere)
1st boot was fast, setting it all up.
Looking in settings for button backlight duration but didn't find it (using it in the night and want them to light up as short as possible).
Wifi connection there as soon as it wakes up.
So I gave BitGapps a go and flashed ARM64 which worked (isn't specified in "Q12" and as far as I remember only ARM worked on ripees build).
Fiddling around a bit installing paid apps and others.
Everything seems to be fine especially for a beta version.
For others who want to change from ripees version to this one:
On mine it worked to restore "Data" via TWRP (partition got wiped again before) what makes it much easier to switch.
Each app I use seems to be working under the new ROM without problems.
Fun fact: button backlight after restoring is as short as it was set in the prior ROM.

bmwdroid said:
Clean installation went well although I didn't follow "Q5" and used latest TWRP which is 3.6.1_9-0.
Click to expand...
Click to collapse
The reason I write MUST is that not all TWRP from the official TWRP site work properly. For example, when I was initially building the 18.1 tree back in July/Aug 2021, I needed mtp and adbd to work in TWRP T710 for debugging purposes.
Despite the change log claiming both were fixed, not a single version worked wrt mtp and adbd. I knew this way back in Dec 2020 and you may have even seen my post #124 since you were post #122 and #126 in the same thread.
So in order to get 18.1 up and running, I fixed TWRP T710 myself as I explain at
https://forum.xda-developers.com/t/recovery-unofficial-twrp-3-5-2_9-for-samsung-sm-t710.4430335/
So for T710 users, I know my TWRP build is rock solid as I have easily used it more than 150 times when making the 18.1 rom.
Another example. During the summer of 2020, I upgraded the OS on a Samsung S4 phone for my friend. I went to official TWRP website, downloaded the latest and much to my surprise, the touchscreen didn't work at all. I used an older TWRP version and it worked fine.
Bottom line: even though it's on the official TWRP website does not mean it's tested or working properly. In the case of the S4 TWRP with the non working touchscreen, it's obvious there was zero testing done.
That's why we will test ALL our 18.1 builds for the "what works" functionality in post #1 before uploading to the general public.
bmwdroid said:
Looking in settings for button backlight duration but didn't find it (using it in the night and want them to light up as short as possible).
Click to expand...
Click to collapse
By sheer coincidence, I already had the above in my private build on March 27 as I wanted to test it to make sure it works before adding it into github. Yes, I test even 1 line of code change myself no matter how trivial.
The 1 line of code needed is documented at
https://review.lineageos.org/c/LineageOS/android_device_samsung_s3ve3g-common/+/292889
I will put this change into my github so that it gets built with the May 5 security patches.
bmwdroid said:
Wifi connection there as soon as it wakes up.
Click to expand...
Click to collapse
My github repo has always had the S2 wifi blobs after @lpedia and I fixed it on Aug 7, 2021 as per
https://github.com/retiredtab/propr...mmit/3984c2ef6852794a939b8eda689fc477705d5c86
As you can see in my github history, that reversion back to S2 wifi has never changed since Aug 7, 2021.
bmwdroid said:
Fun fact: button backlight after restoring is as short as it was set in the prior ROM.
Click to expand...
Click to collapse
Without looking through the 1000's lines of code or more, the above functionality exists probably in the hardware/samsung repo
https://github.com/LineageOS/android_hardware_samsung/tree/lineage-18.1/hidl/light
and the settings are probably saved in some directory, but the display menu for the button backlights isn't shown until I put in that one commit above. That is, the OS knows to use the saved settings, but without the menu overlay, it doesn't show the menu itself.

retiredtab said:
The reason I write MUST is that not all TWRP from the official TWRP site work properly. For example, when I was initially building the 18.1 tree back in July/Aug 2021, I needed mtp and adbd to work in TWRP T710 for debugging purposes...
Despite the change log claiming both were fixed, not a single version worked wrt mtp and adbd. I knew this way back in Dec 2020 and you may have even seen my post #124 since you were post #122 and #126 in the same thread....
Click to expand...
Click to collapse
Well I gotta admit I didn't check adb and mtp in that TWRP.
I probably saw your post but might not have paid attention as they referred to T710 and as I own T810 I judged them as not relevant for me.
retiredtab said:
...
Bottom line: even though it's on the official TWRP website does not mean it's tested or working properly. ...
Click to expand...
Click to collapse
That's what I've noticed as well for T325.
retiredtab said:
..My github repo has always had the S2 wifi blobs after @lpedia and I fixed it on Aug 7, 2021 as per
https://github.com/retiredtab/propr...mmit/3984c2ef6852794a939b8eda689fc477705d5c86
As you can see in my github history, that reversion back to S2 wifi has never changed since Aug 7, 2021....
Click to expand...
Click to collapse
I just mentioned wifi functionallty for those users of T810 having problems with ripees ROM after version 20211103 and looking for a stable version regarding that feature.

retiredtab said:
......Without looking through the 1000's lines of code or more, the above functionality exists probably in the hardware/samsung repo
https://github.com/LineageOS/android_hardware_samsung/tree/lineage-18.1/hidl/light
and the settings are probably saved in some directory, but the display menu for the button backlights isn't shown until I put in that one commit above. That is, the OS knows to use the saved settings, but without the menu overlay, it doesn't show the menu itself.
Click to expand...
Click to collapse
The settings seem to be in the file /data_mirror/data_de/null/0/org.lineageos.lineagesettings/databases/lineagesettings.db
When opening in DB Browser I found:
In table "secure" the lines
46 "button_backlight_timeout" (value 1000 [probaly for milliseconds as I set it to 1s in ripees ROM]) and
47 "button_brightness" (value 1.0).
In table "system" the line
47 "button_backlight_only_when_pressed" (value 1).
Never worked with .db files myself before but for the knowing it might be interesting if they want to fiddle around a bit.

New build called lineage-18.1-20220510-UNOFFICIAL-gts210wifi.zip
Yogi555 has tested all the functionality as to what works as per post #1 before uploading the build. Having said that, there's still a chance it won't work on your device due to human error, your configuration, your apps, etc. If it won't boot, always start with a complete wipe of everything and format your data. This is known has a clean install. Backup your data before a clean install.
May 10, 2022 release notes
1. YOU MUST read posts 1-4 if you haven't already
2. Added overlay for led capacitive led buttons as per https://github.com/retiredtab/andro...mmit/83551570e4627a0e353e358787f83aa65484b528
3. Incorporates May 5th security patches as per https://review.lineageos.org/q/topic:R_asb_2022-05
4. If you are upgrading from the April 10 build, you may dirty flash the May 10 build. If you are NOT coming from the April 10th, 2022 build, you MUST BACKUP your data because YOU MUST wipe dalvik/cache, cache, system, data and internal storage partitions in TWRP and FORMAT DATA. You cannot dirty flash at all. See FAQ Q11.

@retiredtab just flashed it onto 20220410.
1st try very dirty (not wiping anything) resulting in bootloop.
2nd flash (after wiping system+caches) of ROM, Bitgapps28-arm, Magisk23 made it start.
Magisk had of course to patch boot.img again.
Thx very much.

Due to a post in the T710 regarding gapps, I will be removing opengapps from the FAQ because for several months now (starting around Oct 2021), the opengapps project has been releasing UNTESTED builds that results in bootloops or non working gapps services. Despite numerous requests/posts from the community to slow down the releases and actually TEST THEM BEFORE release, the latest May 3, 2022 shows there is still room for improvement.
This thread in the opengapps forum is just the latest example. Details of UNTESTED builds are also in the same megathread below.
https://forum.xda-developers.com/t/...rsions-devices.3098071/page-367#post-86885091
It's also shown up in other roms like
https://forum.xda-developers.com/t/...7-1-04-30-2022.3937956/page-100#post-86885353
This would be a good time for user to do their own research on which gapps is best for them or use NONE at all. I use Aurora Store myself.
Just a reminder that the builds we release are TESTED and verified to have all the functionality as listed in post #1.
T710 thread post #8, #9 and #10.
https://forum.xda-developers.com/t/...neageos-18-1-for-sm-t710-may-12-2022.4430339/

I wanted to express my sincere thanks to @retiredtab and @Ipedia for your work on the ROMs for the T710 and T810. I have both devices and had previously used the @ripee versions in thread (2) [ROM][UNOFFICIAL][11] LineageOS 18.1 [T710][T715][T715Y][T810][T815][T815Y] | XDA Forums (xda-developers.com). But that 18.1 version had some noticeable bugs and wasn’t being maintained.
Thanks to @bmwdroid ’s April 15 post directing us to this forum, I have been experimenting with this ROM since then on both the T710 and the T810. Based on my pretty heavy usage, I can declare both to be excellent. Most notably, the WiFi is rock solid. The T810 and the T710 (especially) are outstanding hardware, and being able to run Android 11 is a huge boost in the device’s intrinsic value.
I have experienced a couple of random BSOD-equivalent crashes over the past month, but the tablet always immediately restarted. I am going to try and learn how to provide the necessary to the developers so, if it happens again, they can have the necessary evidence. Since I am a decent techie, but not a developer, I decided to write up the complete upgrade procedure I followed so others who come to this forum may benefit. See my next post.
PS: I put this post on both the T710 and the T810 threads since I have both devices.

Tab S2 T710 and T810 Upgrade Procedure Using LineageOS 18.1 ROM by retiredtab
These installation instructions work for both Tab S2 T710 and T810. I have both devices and have tested on both. I am a Windows guy, so these instructions assume a Windows PC. I am a lifelong techie guy and an Android enthusiast. But I am not developer, so these instructions should work for any competent newbie who is a decent techie, but I realize there may be alternative approaches for those who have deeper tech knowledge than me.
Step 1 – Preparation
Update your Tab S2 to the latest stock software.
Install a micro-SD card into your Tab S2.
Enable Developer Options – tap Build Number seven times.
In Developer Options, turn on USB debugging.
Connect your TGab S2 to your PC via USB and download onto the micro-SD card three files:
Retiredtab’s latest Lineage 18.1 ROM from lpedia-sf - Browse /gts28wifi at SourceForge.net (T710) or retiredtab - Browse /SM-T810/18.1 at SourceForge.net (T810)
open_gapps-arm-11.0-pico-20220215.zip from The Open GApps Project
Magisk-v24.3.apk from Release Magisk v24.3 · topjohnwu/Magisk · GitHub
Download to your PC TWRP_3.5.2_9_SM-T710_20210719_Unofficial.tar from retiredtab - Browse /SM-T710/TWRP at SourceForge.net (T710) or twrp-3.5.2_9-0-gts210wifi.img.tar from Download TWRP for gts210wifi (T810)
Download to your PC Odin, from https://technastic.com/wp-content/uploads/2020/02/Odin3_v3.14.4.zip, and extract the zip.
Comments:
I saw retiredtab’s comments about OpenGApps quality. However, this version works well for me. I had previously tried the latest MindTheGapps (which hung) and BiTGapps (which doesn’t include the Google restore functionality that I use.)
Magisk is optional if you want/like root. I do!
Step 2 – Install TWRP Recovery
Power off your Tab S2.
Launch Odin on your PC and press OK.
Power up your Tab S2 into Download mode by holding down Home+VolDown+Power.
Then at the Warning screen hit VolUp.
Connect your Tab S2 via USB to your PC, and you should see Added!! in Odin.
Click AP in Odin and select the downloaded TWRP.
In Odin Options, uncheck Auto Reboot.
Click Log tab again.
Click Start in Odin.
Installed TWRP only takes a couple of seconds.
You will see progress in the Log, and Pass at the top of Odin when done.
Step 3 – First boot into TWRP.
This part is tricky!
Power down your Tab S2 by holding down VolDown+VolUp+Power.
IMMEDIATELY the screen goes blank, hold down Home+VolUp+Power.
Keep holding down until you see the TWRP home page.
If you end up booting into Android rather than TWRP then you will have to repeat steps 2 and 3 again.
Step 4 – Backup your stock ROM
In TWRP, select Backup, Select Storage to choose your micro-SD card, check all the boxes, and then swipe Backup.
Step 5 – Install ROM and GApps.
In TWRP, select Wipe, then Advanced Wipe.
Select all partitions except Micro SD Card.
Swipe to Wipe.
Back, Back again, then Format Data
Type yes, and hit check.
Back, Back, Back, and select Install.
Select your micro-SD storage.
Select the Lineage-18.1 ROM.
Add more Zips, and select open_gapps.
Swipe to confirm Flash.
Installation took about 3 minutes.
Wipe Cache/Dalvik, and Swipe to Wipe
Reboot System
Step 6 – Build your Android 11 Tab S2
First boot into Lineage was less than a minute, and then the Lineage boot animation took less than 2 minutes before “Hello” appeared.
On each build I’ve done I see “Speech services by Google keeps stopping” error once Hello appeared.
I assume this is one of the known OpenGApps bugs.
Clicking Close App makes it go away, and later Google replaces the module anyway.
Set up your Android device per your preference. I have loads of Apps so it takes me a long time. If you are less of a pack-rat, it shouldn’t take long!
At the end of the initialization process, be sure not to choose the Replace Lineage recovery option, otherwise TWRP goes away.
I have found that, by not installing Magisk initially, Google restores all my Apps, including the sensitive ones such as Peacock, Netflix, Disney+, etc. And when I check Google Play/Settings and scroll to the bottom, I see “Device is certified”.
I recommend leaving tablet completely alone until Google has finished its “Copy Apps and Data” from my other tablet. When I get impatient and fiddle around as it’s copying I’ve seen crashes.
Once all copying is done, do your unique Android setup. My go-to Android settings are:
Nova Prime Launcher (actually, gets selected during the copy process, but I load my layout from backup at this time)
Microsoft Swiftkey
Default USB = File Transfer
Window/Transition/Animator Scale all set to Animation Off
Screen timeout 30 minutes, and screen saver Clock
Battery %age next to icon
FX File Explorer
Microsoft Edge as default browser (with AdBlock enabled and Google as search and sync to my PC)
Raindrop, for all my bookmarks
Advanced restart menu (to allow reboot into TWRP).
Step 7 – Make Root
Restart Tab S2 into TWRP.
In TWRP, Install Magisk-v24.3.apk.
Reboot System
In Android install Magisk-v24.3.apk.
Open Magisk and select zygisk in settings.
Restart again.
You now have root. I test by enabling root in FX File Explorer and granting root.
Step 8 – All done!
I do a final and full TWRP backup once the device is solid.
Note:
I found the fingerprint reader sometimes works to unlock the Tab S2. Per other discussions on this thread, looks like I got lucky!

pflyaz said:
Tab S2 T710 and T810 Upgrade Procedure Using LineageOS 18.1 ROM by retiredtab
Click to expand...
Click to collapse
Thanks. I updated FAQ to point to post #16 for newbies.

Hi just a question regarding Q5
A5. You MUST use TWRP 3.5.2_9.
Is there a reason for this! I'm only asking because I have 3.6.0.9-0 installed so just wondered why its a must.
Edit - ignore the message above I didn't see post 9 when reading this on my tablet but do now I am on PC.

Had this running now for the last 5 hours, everything seems to be fine but I'm seeing very slow WiFi speeds. Coming straight from (lineage-18.1-20211103-UNOFFICIAL-gts210wifi) where I was getting a constant speed over 330mb I'm now only getting 110 dropping down to 70 at best.

lojelo said:
Had this running now for the last 5 hours, everything seems to be fine but I'm seeing very slow WiFi speeds. Coming straight from (lineage-18.1-20211103-UNOFFICIAL-gts210wifi) where I was getting a constant speed over 330mb I'm now only getting 110 dropping down to 70 at best.
Click to expand...
Click to collapse
@retiredtab Maybe just a wild guess, but might this commit be related? In my understanding argosd is a daemon that controls the CPU governor so that CPU performance can be adopted to network bandwith requirements. Shouldn't that be activated for Wifi models as well?