yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Hexrotor:
Nope, I tried this way but no help. I flashed marshmallow firmware then Crdroid6.9 without clean, it was no display but heated up at boot. I waited for about 10min but it didn't boot complete. Edit: I tried again just now, it booted successfully but still no backlight. Now I'm using official marshmallow.

I don't know why this ROM works with spiramedia's BOE device. I have some friends who have T350/P350 BOE devices and all they have backlight problem with 3-part ROMs, that’s why I am sure that the backlight problem is related to BOE.

For Los 17 and Crdroid, my device has no backlight after the "Samsung Galaxy Tab A", but official marshmallow works fine.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
The above makes sense to me. I believe the aboot partition does the initial boot and shows the Samsung Galaxy Tab A logo with backlight. Then it loads boot.img which contains the kernel. If the kernel isn't properly configured for the BOE panel, then it probably disables the backlight for some reason.

Let's see if spiramedia reconfirms that my 17.1 build works on his BOE panel.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] spiramedia:
flash any marshmallow rom. install this recovery twrp 3.3.1 before system boot. and it will work just fine. https://yadi.sk/d/0PyIqtmNDZSeUA
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Hexrotor:
Bro are you sure your device is BOE panel? I tried to flash latest marshmallow firmware and this twrp again but still no backlight(include twrp). If you are really using BOE device, the backlight problem may be not caused by BOE.

I want to ask you some necessary questions:

1) Are your device really using BOE panel? If allowed, I want you to reconfirm it in DEVCHECK app, just in Hardware>Graphics>Panel.

2) Have you ever had a backlight problem? If so, which Android(twrp) version you used? (PS. Twrp 3.2+ has backlight problem in my device, )

:)If you can provide more information, it would be more helpful for us.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] spiramedia:
here my screenshots and pictures of my tablet. and it is boe panel.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
Definitely BOE. Thanks for the pics.

[MENTION=4052504]spiramedia[/MENTION], did you get a chance to get some of the answers I asked about for your shutdown problem?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Hexrotor:
Thx! :crying:Maybe I the firmware I use is different from yours.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Hexrotor:
?Actually I tested several ROMs yesterday, and now my tablet cannot boot up. I tried to flash firmware but useless, it turns to recovery when first boot, and always stays on the boot animation when boot to system. I don't know what to do.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
[MENTION=4052504]spiramedia[/MENTION], can you adb shell into your tablet and do the following command

cat /proc/device-tree/chosen/bootargs

On mine, near the end of the text output I see

lcd_id=0x5d8810 mdss_mdp.panel=1:dsi:0:ss_dsi_panel_S6D7AA0_LSL080AL03_WXGA:1:none

I'm just curious if yours shows the BOE in the ouput?

Thanks.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] spiramedia:
[MENTION=8726605]retiredtab[/MENTION]

tablet works fine. no shut downs.

here is what i gor in adb shell

sched_enable_hmp=1 console=null androidboot.hardware=qcom user_debug=23 msm_rtb.filter=0x3F ehci-hcd.park=3 androidboot.bootdevice=7824900.sdhci androidboot.selinux=permissive buildvariant=userdebug androidboot.sec_atd.tty=/dev/ttyHSL0 loglevel=4 sec_log=0x100000@0xafe00008 sec_dbg=0x80000@0xaff00008 androidboot.revision=4 androidboot.warranty_bit=1 androidboot.bootloader=T350XXU1BPI2 lpm_levels.sleep_disabled=1 fg_reset=0 androidboot.boot_recovery=0 sec_debug.reset_reason=0x0 pmic_info=4 androidboot.debug_level=0x4f4c sec_debug.enable=0 sec_debug.enable_user=0 androidboot.cp_debug_level=0x55FF sec_debug.enable_cp_debug=0 vmalloc=340M cordon=5f04934d4ba4827dae1b753264762dcf connie=SM-T350_OPEN_EUR_0a84495e5d4aeff737133a16083ac125 androidboot.security_mode=1526595584 androidboot.emmc=true androidboot.serialno=0b37ead1210a9b57 androidboot.baseband=apq lcd_id=0x5db810 mdss_mdp.panel=1:dsi:0:ss_dsi_panel_S6D7AA0_LSL080AL03_BOE_WXGA:1:none gt58wifi:/

---------- Post added at 06:23 AM ---------- Previous post was at 06:14 AM ----------

[MENTION=11154257]Hexrotor[/MENTION]

flash this rom https://drive.google.com/file/d/1gjoodMD09sAZJIWM8fVKrBT3cwmqTTSP/view

flash twrp recovery that i gave upper. and if it will work. flash lineageos. this is what i did.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
There's a number of reported fixes for failed to mount /efs. You can try them as per below

https://www.digitalreborn.com/fix-samsung-galaxy-unable-mount-efs/

You definitely want a backup of your existing efs before trying to make a new partition. And you will likely need twrp 3.3.1 to execute the adb commands. I'm not sure if the Samsung recovery works with adb or not.

On my tablet, I see "efs -> /dev/block/mmcblk0p13" because apnhlos starts at 1.

gt58wifi:/dev/block/platform/soc.0/7824900.sdhci/by-name # ls -al

lrwxrwxrwx 1 root root 20 1971-07-20 06:53 apnhlos -> /dev/block/mmcblk0p1

lrwxrwxrwx 1 root root 20 1971-07-20 06:53 sbl1 -> /dev/block/mmcblk0p3

lrwxrwxrwx 1 root root 21 1971-07-20 06:53 efs -> /dev/block/mmcblk0p13

Using heimdall print-pit (it's entry 12, but still identifier 13 because heimdall starts at 0).

--- Entry #0 ---

Binary Type: 0 (AP)

Device Type: 2 (MMC)

Identifier: 1

Attributes: 5 (Read/Write)

Update Attributes: 1 (FOTA)

Partition Block Size/Offset: 8192

Partition Block Count: 30720

File Offset (Obsolete): 0

File Size (Obsolete): 0

Partition Name: APNHLOS

Flash Filename: NON-HLOS.bin

FOTA Filename:

--- Entry #12 ---

Binary Type: 0 (AP)

Device Type: 2 (MMC)

Identifier: 13

Attributes: 5 (Read/Write)

Update Attributes: 5 (FOTA)

Partition Block Size/Offset: 212992

Partition Block Count: 28672

File Offset (Obsolete): 0

File Size (Obsolete): 0

Partition Name: EFS

Flash Filename: efs.img.ext4

FOTA Filename:
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
Nov 8 build uploaded with Nov 5 security patches. Also, I added code for s-pen support for the SM-P350, but I have no way of testing it. See

https://xdaforums.com/galaxy-tab-a/development/sm-p350-rom-s-pen-support-beta-testers-t4187731

for details. Please note there will be NO HELP and NO SUPPORT for any bricked SM-P350 as a result of using the Nov 8 build. There will be NO HELP and NO SUPPORT in reverting the SM-P350 back to stock. I do not have the SM-P350 so I cannot test it.

I test all my builds for the functionality as stated in post #1 and the Nov 8 build works on my SM-T350. I just don't have the SM-P350.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Rahul.raj:
This may be a stupid question but how different are the SM-T350 (WiFi) and SM-T355Y (LTE-DO) ROM-wise? Is it very complicated to modify this ROM to work with SM-T355Y/gt58ltedo?

I can do a little bit of scripting, if needed, but not very tech savvy.

Cheers.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
Your questions is FAQ 1. It's answered there.

Try it at your own risk. I have no T355Y to test it on.

If you want to try the T350 rom on the T355Y, you won't get any LTE for sure. You can modify the rom zip file to install on the T355Y by removing the assert command from

META-INF/com/android/google/android/updater-script

or you can add gt58ltedo and T355 to the assert statement. Either should work.

The assert command is there to ensure you don't flash the rom on the wrong tablet.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Rahul.raj:
Thanks for the reply!

Sorry, I should have mentioned that I had read it and was asking specifically because other than the LTE, the two devices seemed to be identical. ALso, search for T355Y or gt58ltedo did not turn up any results on the thread.

My bad - let me phrase my question better: If I am willing to do some reading and some building, how can I try and add LTE support using this ROM as the base? Or if you could guide me to a resource which I can follow.

I am actually looking for some way to de-bloat the OS. I found resources for rooting and recovery, but no custom ROM for gt58ltedo.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
Okay, now that you have clarified, your best best to building a custom rom is to look at

https://github.com/Galaxy-MSM8916/android_device_samsung_gt58ltetmo/tree/lineage-17.1

Yes, I know the above is a "t" and not a "d". I don't know what the two letters mean. It could be country code specific or tied to a specific carrier or telecommunications band like

lte, 3G, 4G, etc.

With the above device tree, you can try building your custom rom and using my files from post #2 to help you build a roomservice.xml file, see what bugs you will run into with my fixes txt file and using my repo diffs to make the changes.

If this is your first time building, I suggest you read what I had to write about it in this thread

https://xdaforums.com/galaxy-tab-a/how-to/help-device-tree-sm-t380-t4187749

As for me adding LTE to my build, it's not a possibility. I have no T355 to test it on and I have no LTE sim devices in the house or contracts with carriers. And I don't want the invariable headaches that come with helping people who complain the volume is too low, too high, too distorted, dropped calls, poor reception, etc, etc.

According to

https://www.gsmarena.com/samsung_galaxy_tab_a_8_0_(2015)-7121.php

the 350 and 355 should share almost identical hardware, but you should download devcheck

https://play.google.com/store/apps/details?id=flar2.devcheck

to make sure its a Qualcomm CPU. Also see if you have a BOE sourced panel. You can compare the output with the pictures at

https://xdaforums.com/showpost.php?p=83782137&postcount=24
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
BOE panel fix

See post #1 for BOE panel fix.

The above tells you why the problem exists and how flashing a 1MB aboot.mbn fixes it.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
[MENTION=11154257]Hexrotor[/MENTION], new information and fix for BOE panel. It's flashing a 1MB file aboot.mbn file.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Rahul.raj:
Many thanks! This was exactly what I was looking for.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
timekeep implemented - qualcomm RTC is readonly

Continued from

https://xdaforums.com/showpost.php?p=83899345&postcount=617

I will never say "It shouldn't be too difficult" again publicly.

After struggling with getting timekeep compiled, I finally found a repo where I could see how timekeep was implemented properly via

https://gitlab.com/LineageOS/issues/android/-/issues/1411

https://xdaforums.com/showpost.php?p=82725973&postcount=363

https://github.com/YumeMichi/device_oneplus_onyx

Thanks to [MENTION=7093179]YumeMichi[/MENTION] for the open source repos where I could see the code.

I tested the timekeep functionality in Lineageos 17.1 and in TWRP 3.3.1 by turning off network time (NTP) and manually setting the time. In both cases, the time was kept correctly.

So my instincts were correct initially about using timekeep in post #18

https://xdaforums.com/showpost.php?p=83776003&postcount=18

but it just took a while to actually implement it.

Anyway, the changes will be incorporated into the Dec security patch. The build I'm using with the timekeep functionality will given to those who just want to test the functionality themselves to help verify that it works.

=== recovery log from TWRP 3.3.1 with timekeep build ===

I:TWFunc::Fixup_Time: Pre-fix date and time: 1971-08-11--22-36-06

I:TWFunc::Fixup_Time: Setting time offset from file /sys/class/rtc/rtc0/since_epoch

I:TWFunc::Fixup_Time: will attempt to use the ats files now.

I:TWFunc::Fixup_Time: Setting time offset from file /data/vendor/time/ats_2, offset 1554355087000

I:TWFunc::Fixup_Time: Date and time corrected: 2020-11-12--03-54-13

Code to implement is attached.

PS. I could not get

on boot /system/bin/timekeep restore

as suggested by

https://github.com/sonyxperiadev/timekeep

to work at all. Compiler kept complaining

Invalid keyword '/system/vendor/bin/timekeep'

so I moved it to a .sh (shell file) instead of a .rc file.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] spiramedia:
new update! thats a good news!!!
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Hexrotor:
:)Oh thank you for your works! This backlight problem has existed for a long time and finally it was solved. I just have no non-BOE P350 now so I cannot test it. I'll test it on BOE P350 in the future as much as possible. Hope it works on P350.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
New build called lineage-17.1-20201214-UNOFFICIAL-gt58wifi.zip

Release notes for Dec 14, 2020

1. Dec 5 security patches.

2. Changed some error messages to verbose to stop spamming log files.

3. Whatever LineageOS changed since last Nov update.

4. Add timekeep functionality since SM-T350 has no real time clock. This allows the tablet to keep time when not used with a NTP (network time protocol) server. It works in Android OS and TWRP.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Zinnath Ara:
Can anyone please give me the twrp 3.3.1 file for SM-T350? I found the .img file but I need the .tar file so that I can flash it with odin.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
Make your own .tar file or use heimdall. Heimdall is what I use on linux.

Convert IMG to TAR (zip to tar.md5) - Odin Flashable Files

How to Convert IMG to TAR Odin Flashable files. Zip into tar.md5 using BAT Tool. Image files into Odin files. .img to .tar.md5 Converter Online.

www.droidthunder.com

Heimdall | Glass Echidna
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
New January 2021 build at new download location.

retiredtab - Browse /SM-T350/17.1 at SourceForge.net

sourceforge.net

I'm moving to sourceforge for all 2021 uploads. The main reason is that I would like to see the stats of where this rom is being downloaded from worldwide. All 2020 builds will remain on androidfilehost.

Release notes for Jan 14, 2021

1. Jan 5 security patches.

2. Changed some error messages to verbose to stop spamming log files.

3. Whatever LineageOS changed since last Dec 2020 update.

4. For some reason after flashing the rom, TWRP 3.3.1 now says "unable to mount storage". I had never seen that before. Nevertheless, if you reboot, the rom will work fine. I test all my builds before uploading.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] krazyvladimir:
I've installed the latest version from Jan 14th, everything works fine except for when I connect a bluetooth speaker and select for the audio to be routed to that speaker, everything still goes through the tablet's speakers. I'm wondering if others have a similar problem and if there's a fix for it.

Thank you
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
Yes, I just discovered that problem with audio not working over bluetooth a few of days ago. All the "A/E" class roms that I build, SM-P550, SM-T550, SM-T350 and SM-T560NU 17.1 have the same problem. However, the 16.0 builds all work fine with this feature. I will update post #1 to reflect that it's not working until I find what is wrong.

Something changed in 17.1 and so far, I haven't found root cause. If you need that feature immediately, use crDroid for T350 as it works on that rom.

https://xdaforums.com/t/rom-sm-t350...-0-v6-14-android-10-galaxy-tab-a-8-0.4158163/
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
BTW, audio over bluetooth is something I never use and I didn't even know it worked in 16.0 and was broken in 17.1. So another alternative is to use my 16.0 build.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] krazyvladimir:
No rush, take your time and thank you for your effort.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
New build called lineage-17.1-20210210-UNOFFICIAL-gt58wifi.zip.

Release notes for Feb 10, 2021

1. Feb 5 security patches.

2. fixed audio over bluetooth. Huge thanks to @nubianprince for helping with suggestions and his repos. The problem was that some of the audio xml files weren't being copied over in 17.1 because of some directory changes to hardware/qcom.

3. Whatever LineageOS changed since last Jan 2021 update.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
@krazyvladimir, audio for BT works now in Feb 10 build.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] ahmadbilal505050:
Is this stable enough to use it as a daily driver? Should I use this ROM or CrDroid?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
New build called lineage-17.1-20210307-UNOFFICIAL-gt58wifi.zip

March 7, 2021 release notes

1. Mar 5 security patches.

2. Whatever LiineageOS changed since last February release.

3. Stock camera does not save picture on front facing camera. Use open camera instead. I don't know when stock camera was broken, but when I tested the March 7, 2021 build, it doesn't work. I never use the camera or video recording on the tablets.

Open Camera | F-Droid - Free and Open Source Android App Repository

Camera App

f-droid.org
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] ahmadbilal505050:
Thanks alot for updating. I've installed the previous version. Can I update it or I have to do the whole process of flashing again?

I also wanted to request will you please make an Android 11 based ROM or GS-I support ROM( that gives GS-I compatibility) this device so that we can flash GS-I even if you discontinue support for this device. Please reply😍
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] ahmadbilal505050:
Man, the chrome and YouTube keeps stopping every five minutes. The Bluetooth also doesn't work
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] racerxgt91:
Thanks for the hard work. Hope to see 18.1 o n this old thing see if it could handle it lol.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] ahmadbilal505050:
😍😍😍😍I would be very happy then
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
New build called lineage-17.1-20210412-UNOFFICIAL-gt58wifi.zip

April 12, 2021 release notes

1. April 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/307454

2. Whatever LiineageOS changed since last March release. Nearly 59,000 out of the 70,000 files had to be recompiled due to the last set of changes.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] yxo 6o6uka:
I maybe missing something obvious, yet... what is the utility of enabling the on-screen nav bar with buttons next to the h/w buttons of this tab?

The build is very nice, appreciate it, thx!
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
I use the tablet in the semi-dark/dark sometimes and since the hardware keys are not lit up, having the on screen nav bar helps.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lpedia:
I use the on-screen nav bar on my Pixel 3 because it's so much easier to see than the Pixel's standard (very understated) on-screen nav keys.

It's also a way to swap the keys to where most other devices have them, because those of us who routinely use both Samsung and non-Samsung devices tend to keep hitting the wrong key on both ... ;)
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
Yes, I can't make everybody happy with the defaults, but at least you can turn on screen nav off or invert the keys settings to your liking.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
New build called lineage-17.1-20210510-UNOFFICIAL-gt58wifi.zip

May 10, 2021 release notes

1. May 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/309564

2. Whatever LiineageOS changed since last April release.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
New build called lineage-17.1-20210615-UNOFFICIAL-gt58wifi.zip

June 15, 2021 release notes

1. June 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/312240

2. Whatever LiineageOS changed since last May release (about 5400 files had to be recompiled).
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] btnhan:
Thank you for everything you have done. I'm planning to flash this ROM on my SM-P355, I know a little bit about flashing but I don't know how to flash it on my device because it doesn't match the digital sign I think? I've search how to change the digital signing but it doesn't work, may be it's because of other command line I think, and this is out of my reach. Can you please spare some time tell me how to edit it, and yeah I'm ready to take risk LOL. Thank you.

P/s: I also want to mention that I have done what you told at #33. I unzipped the file and deleted assert and rezipped the file but TWRP still said this "invalid file zip file format". Am I missing something? Like do I have to adjust something when I re-zip the file? Or by unzipping the file, I have damaged the boot img?

Oh and when I'm checking other file META-INF\com\android\metadata and there are some T350 device code, do I need to change this too?

Edit: I've successfully edited the file, and change everything related to device's code and finished installing, but it won't boot into the OS, so i can say it won't work on SM-P355. So SM-P355 users, don't try it. Thank you @retiredlab btw
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
New build called lineage-17.1-20210713-UNOFFICIAL-gt58wifi.zip

July 12, 2021 release notes

1. July 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/313448

2. Whatever LiineageOS changed since last June release (about 4500 files had to be recompiled).
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
For those who want to try 18.1 ALPHA, see

https://xdaforums.com/t/unofficial-...or-galaxy-tab-a-sm-t350-july-10-2021.4305903/
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] user655362020:
Hello, I want to build LineageOS 17.1 for T355Y (LTE variant of T350). What is the difference between evervolv kernel and msm8916 kernel ? I noticed evervolv kernel overclocks by default. Is there a way to disable overclock ?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
The last time I tried evervolv's 11.0 kernel it was stock clock speeds (1.2CPU/Soc and 400Mhz). Overclock is 1.6Ghz and 650Mhz for CPU/Soc and GPU respectively.

The commits for this were pointed out at

https://xdaforums.com/t/rom-officia...b-a-8-0-sm-t350.3411150/page-12#post-84773289

As for the differences between evervolv and msm8916 kernel, you can look at the commits to see what the differences are.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] user655362020:
Thanks
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] ovalseven:
Is there any way to enable touch sound for the back button?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
If you have onscreen nav enabled (on by default), touching the back button on the screen generates a sound (verified on my 18.1 build, but probably the same on 17.1). This also assumes you have settings, sound, advanced, touch sounds enabled.

If you want sound when touching the hardware back button, then I don't know. You may have to search for an app or magisk module to do that?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] ovalseven:
Yes. I was referring to the hardware back button. Stock rom had a sound as does crDroid. Your Lineage rom seems to run better though. Maybe I can get used to it being silent.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
New build called lineage-17.1-20210807-UNOFFICIAL-gt58wifi.zip

Aug 7, 2021 release notes

1. August 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/314572

2. Whatever LiineageOS changed since last July release (about 4500 files had to be recompiled).