yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab S Android Development] Hazou:
Here you go.:

Release LOS-17.1: [AV] Stop bad scaling of video playback · HazouPH/android_device_samsung_universal5420-common

Using patches from CM-14.1 Change-Id: Ife9b033e8b09a63f1b8d1573926c33982685df01

github.com

Changelog (only T800):

Kernel with UV/OC capabilities (Code from Deathly kernel) (DANGEROUS!)

Fixes to scaling while playing video in web browser

IR Blaster firing with right timing

Deathly Adiutor APK preinstalled. (Needs root to work)

Fixes some selinux denials (still in permissive mode)
[Galaxy Tab S Android Development] steso90:
Thank you so much!

Now LOS 17.1 is as fast as LOS 14.1 :)

Fast charging and everything else work perfectly!

Thank you again for porting this to LOS 17.1 !
[Galaxy Tab S Android Development] glennza:
Could we have a T805 version please?
[Galaxy Tab S Android Development] pzduz:
would you mind building for sm-t705 (klimtlte) if it from Deathly kernel I really like to try it
[Galaxy Tab S Android Development] Hazou:
New release:

LineageOS 17.1 for Samsung Galaxy Tab S 8.3/10.1 Wifi/LTE (T700/T705/T800/T805) version:

Updated:

Kernel with UV/OC capabilities (Code from Deathly kernel) (DANGEROUS!)

Fixes to scaling while playing video in web browser

IR Blaster firing with right timing

Deathly Adiutor APK preinstalled. (Needs root to work)

Fixes some selinux denials (still in permissive mode)

Media upstream changes from Exynos5420 repo

zram/zcache kernel enabled from Exynos5420 repo

Keep in mind: T700/T705/T805 not tested! Flash at your own risk.

I don´t think there is much more to do. My tab is running fine, only the Lineage camcorder is not working.

Release LOS-17.1-19-06-23: universal5420: Enable BOARD_USE_CSC_HW · HazouPH/android_device_samsung_universal5420-common

Change-Id: If664112cb3da387b8fb38406c1e361b93b781531

github.com
[Galaxy Tab S Android Development] glennza:
Installed and testing now. The one problem I have found common to all of the LineageOS versions is corruption of embedded video. I was hoping that Hazou's release might have sorted it out but it hasn't.

I worked out a way to "fix" it (or at least improve it), which is by installing an older version of Android System Webview.

The best way to experience the problem is to install Google News and attempt to read a few articles. It was the first thing I tried with this new release. Bang, instant reboot!

This is my goto webview. Installed and all now works okay.

Webview v.75

Also: thanks to Hazou for working fingerprint too. Didn't work for me in glitcher's release
[Galaxy Tab S Android Development] djase:
I hope this version will solve the reboot and freeze problem I have with the previous version.🤞
[Galaxy Tab S Android Development] Hazou:
So this problem can be found in Los 14.1 too?
[Galaxy Tab S Android Development] theparkdude:
Does anyone know if the release from Hazou fixed the microphone not working issue on the SM-T700?
[Galaxy Tab S Android Development] glennza:
Yes
[Galaxy Tab S Android Development] Hazou:
Okey, is there a rom where it is not present, excluding stock? Or does it only work with the old v75 version of webview.
[Galaxy Tab S Android Development] glennza:
I haven't found any ROM without this issue. I had a conversation about it with Bluess57...

https://xdaforums.com/t/rom-unoffic...sm-t805-chagalllte-beta.4512951/post-88235975

Could also be a hardware problem only affecting my tablet?
[Galaxy Tab S Android Development] steso90:
Do you have any plans to add nethunter support for your kernel?

Here are some info about it.

Porting NetHunter to New Devices manually | Kali Linux Documentation

In order to port NetHunter to a new device, it’s important to understand how NetHunter is separated. NetHunter is divided by the rootfs (also known as the chroot but will be referred to here as rootfs) and the kernel. For the most part, the rootfs is not important to your Android device as it...

www.kali.org
[Galaxy Tab S Android Development] Hazou:
Okey. I can open every page with webview until i start a video. Then it gets displaced, the page stutters and the app dies or just doesn't function. Not my tablet. It stays on. I can stop the app and move on. It seems to me from logcat and dmesg that the OMX video decoder gets information it cant proces. But what I dunno.

Just for my information. The v76 webview also has this problem? And did u install the version and changes the webview version in Developers Settings?

Nope, not at this moment.
[Galaxy Tab S Android Development] glennza:
I removed the embedded webview through TWRP then installed v75 so it is the only version installed .

In the past I have tried Bromite too.also doesn't work.

Not sure about v76. I experimented with quite a few versions and had to go back a long way until I found one that worked. It's possible that you could go a bit further forward. I don't think v75 "fixes" the problem ,it's just a bit more stable.
[Galaxy Tab S Android Development] steso90:
i have noticed one thing with this kernel and its locked att 1400mhz minimum and i cant lower it @Hazou
[Galaxy Tab S Android Development] Hazou:
Untill version 89, there are no problems. From 90 till latest it doesn't work right. Except when u force hardware rendering in webview. Then it works as it should on the tab.

Hmm, only when online or also with screen off? Does it change when changing cpu gorvernor
[Galaxy Tab S Android Development] glennza:
Is this useful?

https://xdaforums.com/t/disable-hw-overlays-force-gpu-rendering.2227089/
[Galaxy Tab S Android Development] steso90:
I've tried different governors, maybe it's some app that forces my device to be awake
[Galaxy Tab S Android Development] djase:
T800 here, with the latest rom charging time is very very slow, almost 8hrs for 100%.
[Galaxy Tab S Android Development] steso90:
You can charge charging rate in "power and battery" in deathly adiutor app
[Galaxy Tab S Android Development] Joshuagabriel524:
Hi @Hazou , i've taken a look at the source code from github, and i want to try and fix the mobile data, text and calls of this device myself given my experience flashing other ROM's so far,

(i will try and flash your specific rom later and try to see if the problem still persists, but i thought why not look at the source while i'm at it)

this is my first time diving deep into modifying these and i want to take a shot at it , LOL :'D
[Galaxy Tab S Android Development] Hazou:
If the other 17.1 roms didn't have a working Rill. This one will not have it. I can only try to repair stuff I can test.

The source code can be a bit overwhelming. Start by just building the rom and try out small changes. Unfortunately the image you send will not fix anything. The image allows Rill to do something in an restricted "enforced" selinux kernel. The kernels for 17.1 and 18.1 are all permissive.
[Galaxy Tab S Android Development] Joshuagabriel524:
So i got to test out your ROM on the SM-T705 variant, it tends to lock up completely for some reason whenever i watch YouTube for about 20 minutes into the video,not sure why it keeps happening, there also some scenarios when i scroll through the settings and try to activate "Developer Options" and instantly restarts before i could finish the last few taps. :D

but i'll keep observing it in the meantime
[Galaxy Tab S Android Development] djase:
even after a complete wipe, I have too many freezes, and have to hard reboot the tablet.
[Galaxy Tab S Android Development] Joshuagabriel524:
Apparently the ROM is a bit unstable , the crashes and hardlocks can happen at anytime , i'll be reverting back to a previous stable build of "crDroid" that i backed up

Speaking of crDroid, does anyone have an archive of the last latest build ?? mine is only on January 2022 based on the date while im flashing it
[Galaxy Tab S Android Development] djase:
So far so good with this one : lineage-17.1-20230625-UNOFFICIAL-chagallwifi.zip
[Galaxy Tab S Android Development] FalenDemon:
Is anyone successful boot this build: lineage-17.1-20230625-UNOFFICIAL-klimtwifi.zip ?
[Galaxy Tab S Android Development] glennza:
Where are you getting these new ROMs?
[Galaxy Tab S Android Development] glitchers:
Judging by the filename, looks like one of mine.
[Galaxy Tab S Android Development] FalenDemon:
Link was above: https://lineageos.glitchy.net
[Galaxy Tab S Android Development] glennza:
Thanks guys! Don't know how I missed it
[Galaxy Tab S Android Development] Joshuagabriel524:
Thats the one i just tested just last saturday, random lockups can happen anytime.
[Galaxy Tab S Android Development] glitchers:
You sure about that? The impression I got from reading the thread was that you were using Hazou's Deathly kernel fork built 0619, not mine from 0625.
[Galaxy Tab S Android Development] Joshuagabriel524:
Sorry, i meant to say i came across a similar build , but to someone named "blues557" i think.
[Galaxy Tab S Android Development] Hazou:
Didn't know this one existed. Cool
[Galaxy Tab S Android Development] jassus:
How about wideline on this rom? Can you still watch netflix in FullHD on sm t800?
[Galaxy Tab S Android Development] Tomd000:
I can confirm that Hazou's Lineage 17.1 works on the T700 Klimtwifi, thank you.
[Galaxy Tab S Android Development] Bushcrafter:
Wow,i can not believe how many people are still using this tablet. I still have my T-800 and use it almost everyday.Its good to see a few people are still trying to give it some love. One of these days I guess I will have to retire it,but it just keeps on working.😁👍
[Galaxy Tab S Android Development] Hazou:
For those who want:

New release:

Release LOS-17.1: [AV] Stop bad scaling of video playback · HazouPH/android_device_samsung_universal5420-common

Using patches from CM-14.1 Change-Id: Ife9b033e8b09a63f1b8d1573926c33982685df01

github.com

Changelog:

Updating libGLES_mali to r15p0..10.6.

This should fix newer Android Webview implementation

This could fix OOM problems with graphic heavy applications
[Galaxy Tab S Android Development] Klaus20:
For some time now I have not been able to connect to WLAN in the home network.

I set up a guest, but that doesn't work either.

--> "Network connection could not be established" <--

A connection can be established immediately with the Personal Hotspot.

All other devices connect to the WLAN without any problems (Fritz Box 6690)

Does anyone have an idea how I can fix it?

Regards Klaus
[Galaxy Tab S Android Development] Hazou:
If you can connect to networks outside your home. the problem most likely lies within your home network.
[Galaxy Tab S Android Development] Klaus20:
That's what I thought too, but no idea where to start?

Turning off the Windows Firewall was unfortunately unsuccessful.
[Galaxy Tab S Android Development] Hazou:
The Windows Firewall does nothing for your tablet or even a wireless connection in general. It can only stop data from going out or in over a connection from the windows device, but not the connection itself.

I assume your fritsbox sends out the wireless signal,without any other repeaters or accespoints in your home.

Then try:

- Forget the wireless connection in your WiFi section of the tablet and try again from scratch.

- kill the power (not restarting, I mean make it dead) of the fritsbox and reconnect it after about 10seconds. Then retry my first point.
[Galaxy Tab S Android Development] Klaus20:
I did the update to lineage-17.1-20230715-UNOFFICIAL-chagalllte.zip via the recovery menu, but after the restart I ended up in the recovery menu again. Even if I turn off the tablet, I go back to the recovery menu when I turn it on.

Now I've tried to restore the backup but now I'm stuck in an endless boot loop.

With Home + Quiet + Power I can get into download mode but not into recovery.

I was hoping that the new version would solve my WLAN problem. But now nothing works.
[Galaxy Tab S Android Development] Klaus20:
Now I can manage to get into download mode, but in recovery I only see the writing briefly and then I'm back in the boot loop. Maybe someone has an idea how I can solve the problem?

Regards Klaus
[Galaxy Tab S Android Development] Hazou:
Reflash the recovery through Download Mode? Than boot into Recovery Mode? Just make sure u are using latest TWRP Recovery.

Maybe if that doesn't work, flash full stock package (and test) so everything becomes stock again and then flash Recovery to get a custom rom working. But i don't know if this even works.
[Galaxy Tab S Android Development] Klaus20:
First of all thanks - I will try it tomorrow.

How can I flash the recovery in the Download Mod Odin?

If so, where in Odin?

Regards Klaus
[Galaxy Tab S Android Development] Hazou:
There are plenty of guides for flashing recovery through Odin, I think. Haven't done that for a long time.
[Galaxy Tab S Android Development] Klaus20:
So far I haven't found a way to recover my backup created with TWRP.

Unfortunately, I can't access the TWRP interface either, only in download mode or boot loop.

Is there another way so I can use the tablet again?
[Galaxy Tab S Android Development] Hazou:
Full stock flash with official software? Never needed it, so don't know. And after that go back to a working twrp and even restoring the backup.
[Galaxy Tab S Android Development] Klaus20:
I flashed the stockrom and TWRP and afterwards I was able to restore my recovery.

Thank you for your help !!
[Galaxy Tab S Android Development] shaglord:
Hey guys. Can any of these LineageOS versions receive a cast? I want to use the beautiful oled as a simple display for other devices. Thanks!
[Galaxy Tab S Android Development] rvmphoenix:
Hey guys, do you have any LOS 18.1 stable ROM for a SM-T700 KLIMTWIFI?
[Galaxy Tab S Android Development] Dunkwho:
I'm also struggling with wifi failing to connect. I'm using a SM-T700, I found that 14.1 works fine but 17.1 will see the networks, accept the wifi key, but fail to authenticate. No such problem with 14.1 which goes right through the process just fine.

Sticking with 17.1 I went a little deeper

* hotspot from my S10 phone - connects

* wifi to my deco m4 network - fails to connect

* turn on the wifi on my router (normally off, deco is plugged into the LAN on my router) - connects!

So some weirdness with my deco mesh network that isn't behaving the same as my router's wifi. Note that the deco is handing out dhcp for its network on a different subnet to the router. 14.1 (and everything else in my house) is happy with the deco config, 17.1 is not happy with the decos :(

The builds that I've been using are:

Hazou builds from your github repo:

- lineage-17.1-20230619-UNOFFICIAL-klimtwifi

- lineage-17.1-20230715-UNOFFICIAL-klimtwifi

download.exynos5420.com:

- lineage-14.1-20211225-UNOFFICIAL-klimtwifi

If there's anything that I can do to get the wifi connecting to my decos I'd love to hear/try it. I don't want my router wifi, the signal isn't consistent through my house (hence the decos) ... plus I want to know that I can rely on the wifi on my tablet when I travel. Thanks!
[Galaxy Tab S Android Development] Hazou:
Do you have any Dmesg and Logcats from then? I can't reproduce it, so walking blind in it. Maybe there are already fixes around, but I can't search for them without seeing the problem.
[Galaxy Tab S Android Development] orizonnoziro:
had the same problem. the solution was to turn off fast roaming in the deco settings.
[Galaxy Tab S Android Development] Dunkwho:
Logcat attached

Thanks for all of your efforts with these builds!

Fast roaming - yes thanks for that suggestion! Turning that off allows the tablet to connect with 17.1. Weird that 14.1 connected with fast roaming enabled.

If you make a build to test with fast roaming enabled Hazou I'd be happy to try it

Edit - Hmm ... my logcat doesn't appear to be attaching :(

Edit2 - all good when zipped :)
[Galaxy Tab S Android Development] dennisv9:
For some reason this doesn't work for me (klimtwifi). i get stuck in a reboot loop and return to trwp. Tried with and without gapp packages, but stuck in reboot loop. Can someone point me to a website where i can download the stock firmware so to get the device running again.
[Galaxy Tab S Android Development] toscha42:
Here you go:

Latest Samsung GALAXY Tab S firmware

Download the latest Samsung firmware for GALAXY Tab S with model code SM-T800. Check out our free download or super fast premium options.

www.sammobile.com

Cheers

Toscha
[Galaxy Tab S Android Development] rvmphoenix:
Thanks for the update. Unfortunately, in my case, it didn't work. When updating, and after loading, the screen sends me back to TWRP. I used the following: lineage-17.1-20230625-UNOFFICIAL-klimtwifi.zip, and had the previous version installed: lineage-17.1-20230528-UNOFFICIAL-klimtwifi.zip.

Later, I updated with the Hazou ROM (thanks also to you for your effort, friend), using its latest update: lineage-17.1-20230715-UNOFFICIAL-klimtwifi.zip, and with this one I had no problems when booting, but at the moment after watching videos, after about 20 minutes, the tablet got stuck and didn't react with anything, so I had to restart it in an emergency. I decided to go back to the version that was most stable for me: lineage-17.1-20230528-UNOFFICIAL-klimtwifi.zip.

This was my experience.

Thanks to both glitchers and Hazou for keeping up with updates for our tablets.
[Galaxy Tab S Android Development] Hazou:
Ha, i can test this myself now. I had fast-roaming disabled in my unifi network. With it enabled, my device doesn't connect to the network. The device is missing the 802.r11 implementation. I have a feeling that this can be resolved.

-- Small update

Problem lies within WP_SUPPLICANT. It contains some kind of bug. In lineageOS 18 en 20 I dont see the error happening
[Galaxy Tab S Android Development] glitchers:
Thanks for reporting your results.

That's the first I've heard of lineage-17.1-20230625-UNOFFICIAL-klimtwifi.zip not working entirely. Unfortunately I only have chagallwifi hardware for testing. I build for that, verify on my tablet, and then build for the other 3 models using the same general technique.

I realize you might be tired of troubleshooting, but are you able to verify that the checksum of your zip matches the one listed on the website? Any of these should match:

md5sum:

634d919a5016e9f5c2cae996f47e6636 lineage-17.1-20230625-UNOFFICIAL-klimtwifi.zip

sha1sum:

42a3dbdf223908f4567f1be0db21f082f1e4e94d lineage-17.1-20230625-UNOFFICIAL-klimtwifi.zip

sha256sum:

556c32c12ea0686eef616f9bfdd4a85c3b6ea09778aacc2c01120f6c12526622 lineage-17.1-20230625-UNOFFICIAL-klimtwifi.zip
[Galaxy Tab S Android Development] Hazou:
I got your fix. Took a while to find it. If i didn't mess up one small character I would have found it sooner. Will implement it in the next build allong side some security updates untill June (or July if they are available).
[Galaxy Tab S Android Development] Dunkwho:
I had exactly the same issue with lineage-17.1-20230625-UNOFFICIAL-klimtwifi.zip failing to start - it would show the lineage logo but then drop back to TWRP.

I confirmed the md5sum for my download:

634d919a5016e9f5c2cae996f47e6636 lineage-17.1-20230625-UNOFFICIAL-klimtwifi.zip

I switched to Hazou's builds and they boot fine 👍
[Galaxy Tab S Android Development] Hazou:
New release:

https://github.com/HazouPH/android_device_samsung_universal5420-common/releases/tag/1.2

Changelog:

Fix 802.11r (Use compatible authentication methode)

Update System Security Patches to ASB 2023-07

Some minor changes
[Galaxy Tab S Android Development] teohub:
Thanks for keeping up development on this devices.

Is Mic working on T700 klimtwifi on Hazous or glitschers ROMs?
[Galaxy Tab S Android Development] glennza:
I just wanted to let people know that after trying many many ROMS for my T805, it is my opinion that Hazou's is the best. This is mainly because he has manage to fix the problems with the Mali driver that affects all of the LOS ROMs I've tried and his inclusion of Deathly Kernel

Also, Android 10 seems to be the sweet spot. I have installed LOS 18.1 and 20 and they are still too buggy (app crashes mainly and the Mali bug). Hopefully they will improve. @Hazou did tell me he might work on newer versions!

If you are not aware of it, check out the Thermal Mod thread. It's not 100% necessary to do the hardware mod but the video shows good settings for Deathly Adiutor.

Thermal Mod

I was also curious about changing the Data and Cache partitions from ext4 to f2fs. I wasn't sure if LOS supported it but I did it anyway. I am pleased to report that it does! Just back up the Data partition to the external drive, convert Data and Cache in TWRP and restore data. Working fine for me so far. Is there any speed improvement? Dunno! But it's not any slower :)

So there you go! Hazou's ROM. Kernel tweaks. F2fs partitions. Fast, smooth and stable.

Hazou's ROM Repository
[Galaxy Tab S Android Development] smileysxt:
I am trying the latest of Hazou offerings on both my Chagallwifi and Klimtwifi models. I love the install, once up all my apps work but Clash of Clans and Boom Beach just crash before even showing "supercel". Before the last update of Boom Beach about a week ago, Boom Beach would work. Now they both crash.

Is there a setting like windows has where you can say run as if you are in an older version of the OS?

14 .1 of lineage works for both games.
[Galaxy Tab S Android Development] smileysxt:
I went to appmirror and loaded the previous versions of Boom Beach 48.134 and Clash of Clans 15.352.6 on 17.1 and they worked. The current versions Boom Beach 48.136 and Clash of Clans 15.352.8 never start to launch and crash before anything shows.

The newest versions Boom Beach 48.136 and Clash of Clans 15.352.8 work perfectly fine on 14.1 firmware.
[Galaxy Tab S Android Development] Hazou:
Ye, indeed. It just quits. No error message, nothing. Does it also quit when using: https://github.com/HazouPH/android_device_samsung_universal5420-common/releases/tag/1.0
[Galaxy Tab S Android Development] smileysxt:
Just tried lineage-17.1-20230619-UNOFFICIAL-chagallwifi.zip and it has the same result.

Installed Clash of Clans 15.352.8 from the apk, does not launch.

Removed Clash of Clans 15.352.8.

Installed Clash of Clans 15.352.6 from the apk, works just fine.

Upgraded Clash of Clans 15.352.6 to 15.352.8, does not launch.

Now if it did not work on 14.1, I would understand it more.

It also works on the original Samsung firmware still 6.01.
[Galaxy Tab S Android Development] Hazou:
Oke, then the problem is not GPU driver related. The 20230619 has the same driver as stock. It is in the last update. Maybe they can fix it or hopefully more have this problem on other devices. And there is some kind of fix. The bad thing about this,it just crashes. So an internal apk error. No logcat or kernel log says anything.
[Galaxy Tab S Android Development] Cryple:
Hey,

what TWRP version are you using to change to F2FS format?

Thanks
[Galaxy Tab S Android Development] smileysxt:
I am using twrp-3.7.0_9-0 for my T800 and T700. I always wipe everything under advanced wipe when I try an image to be sure there is nothing in the way of success.
[Galaxy Tab S Android Development] xtrme:
@Hazou many thnx for continuing the development for this device

Running and using it as a last resort for my kid :p in the car

And as home assistant display at home

After running it for a week with the lastest release

I notice it "crashes "after running video (you tube downloaded videos)

The device is unresponsive but the sound does continue (home power down vol is the only cure)

Maybe a driver issue. Do you have a compilation with a different driver that I could test
[Galaxy Tab S Android Development] glennza:
I used twrp-3.6.0_9-0 (didn't know there was a newer version)
[Galaxy Tab S Android Development] Hazou:
I do have 3 different flavors:

- Version 1.0 with the original GPU kernel and Userspace driver

- Version 1.1 with the original GPU kernel driver and the updated r15p0 Userspace driver

- Version 1.3 (soon) with the r15p0 GPU and kernel driver.

If in any of the 3 it crashes it could be the that the decoder gives the problem. I see that a lot of other exynos roms are using there prebuilt OMX decoders (we are not). So it could be that. Someone need to test :P