yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab S Android Development] Bigdrago:
Wow. Nice. This tablet (sm-t805) still lives on I see!

My tablet have started losing battery even if turned off :/ any known hardware fix? Battery is new.

Anyway...will the drm ever work so we can watch netflix in hd?

I currently have LineageOS-14.1-Deathly with gapps nano. Could you implement deathly on this build so we could adjust cpu&gpu voltage etc?
[Galaxy Tab S Android Development] bluess57:
No, it won't
[Galaxy Tab S Android Development] kickinazz:
Was anyone able to get mindthegapps working on this? I keep getting an error 1 trying to sideload it through TWRP.
[Galaxy Tab S Android Development] toscha42:
Never tried MindtheGapps since NikGapps work perfectly with the ROM.

Cheers

Toscha
[Galaxy Tab S Android Development] Zakaria2328:
runs way faster without gapps so that's the route I went, you could give nikgapps a shot
[Galaxy Tab S Android Development] kickinazz:
That's what I ended up doing. Nikgapps worked.
[Galaxy Tab S Android Development] tids2k:
@ROM_gamer987 @bluess57 , any update on a Lineage OS 21 build ?
[Galaxy Tab S Android Development] amisprokillaz:
tried them aswell. Got error 1. BiTGapps do work tho. Even the ROAR variant.
[Galaxy Tab S Android Development] Arktos_moi:
everything work fine for me except the automatic sleep mode

when the tablet is off it wake up by itself 10 seconds later

when I use the On/Off button the tablet don't wake up.

If I made a macro for screen off with macrodroid the tablet don't wake up too

Very good rom anywhere (with a little boost by using 3C_CPU)
[Galaxy Tab S Android Development] avdimdv:
I am still on original samsung rom but want to try something new. Can you tell how good color accuracy of display is on this rom? Samsung have different profiles - "Basic" is quite accurate SRGB emulation, "AMOLED photo" is more or less Adobe RGB. I mostly use "Basic" as tablet lacks HDR so we an consume only SDR content.
[Galaxy Tab S Android Development] 212th:
How do i root this ROM? I tried flashing Magisk but it broke everything
[Galaxy Tab S Android Development] 212th:
Actually the ROM breaks itself after the first reboot... SM-T800
[Galaxy Tab S Android Development] Zakaria2328:
Works fine for me? T800, no Gapps, rooted with Magisk by flashing it in recovery.
[Galaxy Tab S Android Development] 212th:
Latest Magisk? Flashed it right after flashing ROM?
[Galaxy Tab S Android Development] Zakaria2328:
booted into rom before flashing, just did the magisk .apk to .zip thing
[Galaxy Tab S Android Development] Bigdrago:
Rom works fine, it is fast. Flashed rom and magisk with twrp.

But I cant enter recovery through twrp, magisk or lineageos power button (enter recovery).

I have to shut if off and hold home+volume up+power button.

And it doesnt work to flash Nikgapps:

Updater process ended with ERROR : 1

Error installing zip file

Any ideas? Sm-t805
[Galaxy Tab S Android Development] toscha42:
Looks like wrong package, here NikGapps are working perfectly fine.

Cheers

Toscha
[Galaxy Tab S Android Development] Bigdrago:
Nikgapps-T for android 13 arm64?

Downloaded nikgapps-core-arm64-13-20240127-signed.bin.zip
[Galaxy Tab S Android Development] toscha42:
Why is it …signed.bin.zip? Should be …signed.zip only. Did you download from Sourceforge, official NikGapps repository?

Cheers

Toscha
[Galaxy Tab S Android Development] Bigdrago:
Yes I did download from official. I downloaded again and got the same:

Maybe MindtheGapps is better.
[Galaxy Tab S Android Development] Bigdrago:
Flashed lineageos20 again. Tried mindthegapps with no luck. So strange.

I deleted everything. Flashed lineage. Flashed mindthegapps and nikgapps with error.

Flashed magisk with no error.
[Galaxy Tab S Android Development] toscha42:
And you're sure your LineageOS is version 20 / Android 13?

Cheers

Toscha
[Galaxy Tab S Android Development] Bigdrago:
99.99% sure.

Using this:

[ROM][UNOFFICIAL][13] LineageOS 20 for Samsung Galaxy Tab S 10.5 (SM-T805/SM-T800 - chagalllte/chagallwifi ) - Alpha

LineageOS 20 UNOFFICIAL for 2014 Samsung Galaxy Tab S 10.5 LTE/Wifi Model: SM-T805 (LTE) - chagalllte - 10.5" screen, Exynos 5420 SoC, LTE Model: SM-T800 (Wifi) - chagallwifi - 10.5" screen, Exynos 5420 SoC, Wifi These are the ONLY models that...

xdaforums.com

Downloaded from:

Release LineageOS 20 (Chagalllte) · davigamer987/releases

Broken Gps, RIL and fingerprint Selinux Enforcing

github.com
[Galaxy Tab S Android Development] toscha42:
Yes. But is that also the ROM running right now? IoW was flashing LOS 20 successful? Reason for asking is that the error code suggests that it's the wrong Gapps package for the installed ROM. If LOS 20 is running fine you might like to download Gapps package again in case the one you're trying to install is corrupted.

Cheers

Toscha
[Galaxy Tab S Android Development] Bigdrago:
Yes I am running this los in this thread.

I flashed stock firmware and bootloader.

Flashed twrp.

Flashed this rom.

Still the same.

Error code: Could not mount /mnt/system! Aborting. See file.
[Galaxy Tab S Android Development] jlreynolds:
I've got a Samsung Galaxy Tab S 10.5 WiFi that I bought years ago.

It's usually in the top of my roll-away toolbox in my shop as I haven't used it other than for some pdf motorcycle manuals in years.

I would like to give it the latest ROM update that is available.

I'm not up to date on the process as the vast majority of forum members are.

Years ago I updated the ROM on my Motorola Xoom and don't recall any real issues but frankly, in reading most of the posts the process is way beyond my current understanding.

Is there somewhere a step-by-step guide to the process?

I would appreciate any direction.

Thanks

James
[Galaxy Tab S Android Development] Bigdrago:
Download usb drivers and newest odin:

Odinflash

Samsung Odin,Odin download,Download Odin 3.3.14 , Download Odin 3.07,Odin 3.09, Odin 1.85,Samsung ROM Flashing Tool

www.odinflash.com

Flash bootloaderwith TWRP (tar file). Uncheck "auto reboot". Reboot into recocery yourself.

Download TWRP for chagallwifi

Download TWRP Open Recovery for chagallwifi

eu.dl.twrp.me

Download this lineageos 20, flash it with twrp.
[Galaxy Tab S Android Development] toscha42:
Weird, wasn't necessary in my case. Anyhow if it works for you, perfect. :)

Cheers

Toscha
[Galaxy Tab S Android Development] Bigdrago:
Edit: I see now this is a common problem after searching the www.

I flashed los20 again and selected "update lineage recovery alongside os" during install.

It seems TWRP may be out of date for los20 and modern apps like gapps for android 13.

Even if I checked "update recovery alongside" I still have TWRP.

How do I change twrp to los recovery?

No updated pending inside los.
[Galaxy Tab S Android Development] Bigdrago:
Sorry, deleted my last lines. Typo.

Searching for a way to install los recovery. Any ideas?
[Galaxy Tab S Android Development] Zakaria2328:
did you try microg
[Galaxy Tab S Android Development] toscha42:
No idea. I'm perfectly happy with TWRP. :)

Cheers

Toscha
[Galaxy Tab S Android Development] Bigdrago:
Haha.

Bug report sent to twrp team. Hope they can fix it.
[Galaxy Tab S Android Development] Bigdrago:
Solved. Had to download a nikgapps package from 2022 for android 13 to make it install.
[Galaxy Tab S Android Development] mmaazzaa:
What version/release were you successful with?
[Galaxy Tab S Android Development] Bigdrago:
Started to try with the oldest and that worked:

NikGapps-core-arm64-13-20220828-signed.zip
[Galaxy Tab S Android Development] MuffinTechTips:
Hey there!

First, thank you for this build!

Are there some performance tweaks available for this Rom? Every Rom I try feels kinda sluggish and there are apps like navigation apps that really lagging and aren't really useable. It might be the device resources, but the deathly Version of 14.1 with the thermal mod mentioned here runs perfect. Android 7 is just too old.

Thanks

Erik
[Galaxy Tab S Android Development] Bigdrago:
Deathly 14.1 was nice.

Trying to get the deathly app for los20 but I dont think it work.
[Galaxy Tab S Android Development] gugi2000:
Which version of GAPPS should I install?
[Galaxy Tab S Android Development] Hazou:
Nope, it won't. Needs kernel changes. If the kernel patches arent applied, the app won't do anything. Just a fancy app, then.
[Galaxy Tab S Android Development] semihyazar:
Hi i have samsung tab s 10.5 t807 lte turkey version can ı use this rom for my lte tablet
[Galaxy Tab S Android Development] :
Regarding aggressive OOM-Killer and unstable Mali Graphics drivers ...

Why is that? I'm currently using an unofficial LineageOS 17.1 / Android 10 on my SM-T800. Runs smooth and fast. Has no issues.

I recently tested your LOS 18.1 build. It was very nice, but Browser, Google Earth, OSMAND for example crashing so frequently, that it's almost unusable.

I think it's a combination of both (OOM, Graphics): Browser or Google Earth crashing might be due to Mali driver issues (i've been developing embedded stuff using these proprietary drivers for Mali devices... and I know, it got lots of bugs, crashes, undefined behaviour). But I also tried to let OSMAND do a map download in the background. It gets killed almost every time after, e.g. a minute or two in the background (as a foreground service)... So this might look like OOM killing it (i tweaked OOM-settings to the least aggressive settings possible, it didnt help).

So I want to ask (comparing this to LOS 17.1, which doesn't have these issues at all):

- Are there any changes to Mali drivers since LOS 17.1? I mean... it's a kernel driver and a proprietary, compiled user space library we can't change much...

- Why is the OOM-Killer so aggressive. Did the OS footprint get so big, that it more frequently runs on low RAM compared to LOS 17.1 or why is this not fixable?

I'm asking this because I really like the ROM and appreciate work of all involved people here and would love to use it (if stable). (...And to have the same Android version, appearance, etc. on all of my devices.)

My SM-T800 might be 11 years old. But it's still good... Nice display (even compared to some recent tablets), battery still lasts about ~5..8 hours of use.

Sometimes a bit slow but still OK for Browsing, Youtube, etc.

Thank you for your replies :-)
[Galaxy Tab S Android Development] Hazou:
The problem lies within the newer mali userspace driver and kernel driver. This WAS a problem until I fixed this last Juli. The newer driver is needed for newer android versions. If the older drivers are used, some apps won't work properly. But with the newer driver, you get OOM fast, because the device won't ditch old buffers in the mali driver.

The problem with the newer driver is that our device doesn't cope with it to well. Even the older standard ARM Mali driver needed a change from Samsung to get it working well with our device.

This is the main patch that is needed: https://github.com/HazouPH/android_...mmit/db107380d0390986f4c22d78496e97cf96ee2c90
[Galaxy Tab S Android Development] :
@Hazou: Thanks! That's a very interesting insight!

I got one more question: Is there any chance to get this ROM up and running with microG?

I tried this with Magisk + microG installer revived and LSposed modules. Each module can be installed individually without any problems. After having installed both modules, the device would get stuck at the boot logo.

Do you have any idea or could point me to something?

Or, alternatively... Would it be possible to get a version of your ROM which includes the appropriate signature spoofing patch? A solution without LSposed would be perfectly fine for me anyways.

Thanks!

zw.
[Galaxy Tab S Android Development] Hazou:
Could be possible. The ROM needs some changes I believe to support this. Maybe the ROM builder will have a go at it again?
[Galaxy Tab S Android Development] :
I believe it should be possible by "just" adding the appropriate patch for Android 13 from one of the microG-Repos and build the ROM. I would like to give it a try. Right now I do not (yet) have any experience with Android build systems at all.

In another thread, there was some great news too, regarding this: LineageOS today added the commits to enable microG signature spoofing. So, in the future, this should be supported out of the box without the need to patch in signature spoofing (in source or by decompiling some .jar files) or the use of Magisk + LSposed + FakeGApps.

(Information was found here)
[Galaxy Tab S Android Development] Mrodfr:
Hello

I use the ROM on my ST800 since one month or two. At first, I was satisfacted but now the tablet crash verry often, often around google task like :

gmail: read a mail and jump to chrome for seing the link.

Play store: update an application, crash at the beginning of download update.

crash also when navigate of settings. settings crash.

Crash is tablet reboot untill samsung galaxy tabs and lineageOS sequence and crash again 2-3 or 4 time untill a complete boot of the tablet.

I use this tablet and this rom for basic task as reading mail and chrome but not possible now.

Look like update google stuff apps and play service untill now destroy the usability of the tablet.

just 10-12 apps installed like some google apps, weather, etc... really simple task.

I will surely revert to ANDROID 10 ROM soon but I'm also ready for test is someone explain how to do.

For me, the actual version of the ROM need update(s) urgently.
[Galaxy Tab S Android Development] :
Hi,

thanks for this information.

I switched back to Android 10 as well because I couldn't get Signature spoofing to work (which one should be able to setup by using Magisk + LSPosed + some "FakeGApps" LSPosed module). This should be no longer neccessary, if somebody would do a rebuild of this ROM from up-to-date LineageOS-sources as LineageOS now includes the neccessary patches.

But I really asked myself if this ROM suffers from the same problems like the Android 11 ROM, also available for the tablet. As you described, apps keep crashing all the time, rendering it basically useless for any type of usage.

@Hazou explained the root cause a few posts earlier in this thread:

Perhaps, the driver patch could be included in an up-to-date build of this ROM too :-) and we could give it a try again. Otherwise I think, it might be better to stay with Android 10 which works absolutely fine and stable (except encryption) on my device.

zw.
[Galaxy Tab S Android Development] ROM_gamer987:
Yet another android version for chagall
[Galaxy Tab S Android Development] ROM_gamer987:
Hi, i tried building LOS21 with your Lineage 17.1-deathly kernel but it bootloops, i'll attach last_kmsg

Edit: Got it work just had to enable xz
[Galaxy Tab S Android Development] ROM_gamer987:
So far the things that are broken:

Camera (says camera is in use)

Lineage Touch HAL (Won't boot with it added)

SELinux Enforcing
[Galaxy Tab S Android Development] ROM_gamer987:
Camera seems to die with the following errors:

03-08 16:37:24.225 3200 3621 E CameraService: initializeShimMetadata: Error initializing shim metadata: Status(-8, EX_SERVICE_SPECIFIC): '10: connectHelper:1886: Failed to initialize camera "0": Function not implemented (-38)'
]03-08 17:16:31.499 3085 3143 I ExynosCameraHWInterface: [INFO] (HAL_camera_device_open:772):camera(0) in
03-08 17:16:31.499 3085 3143 D ExynosCameraHWInterface: DEBUG(check_camera_state):camera(0) state(1) checking...
03-08 17:16:31.499 3085 3143 E ExynosCameraHWInterface: ERR(check_camera_state):camera(0) state(1:OPENED->1:OPENED) is INVALID
03-08 17:16:31.499 3085 3143 E ExynosCameraHWInterface: ERR(HAL_camera_device_open):camera(0) state(1) is INVALID

Maybe @bluess57 knows something about these errors? Github search didn't help this time
[Galaxy Tab S Android Development] glennza:
Can I suggest that if you want to use Deathly kernel that you make sure that you use a generic name (uname). "Deathly" has been blacklisted on Play Integrity
[Galaxy Tab S Android Development] ROM_gamer987:
Sure, I'll do that if I every get this into a release able state, currently camera is broken and a few other things too
[Galaxy Tab S Android Development] glennza:
When I installed Nikapps, I had the same problem as others have reported. All downloads just sit on "pending" forever.

I fixed this by going into settings/apps, opening Google Play Store, Mobile Data and Wi-Fi. In mine, all data options (Allow Network Access / Wifi Data) were set to off! I turned them on and downloads now work.
[Galaxy Tab S Android Development] Dj Kaïra:
Hello, which gapps should I choose for sm-t800? THANKS

because it tells me updater process ended with ERROR: 1
[Galaxy Tab S Android Development] hdcine:
Hi, you can try BitGApps, the Core version with minimal Google Apps : BiTGApps-arm-13.0.0-v3.3-CORE.zip
[Galaxy Tab S Android Development] Dj Kaïra:
thanks =)
[Galaxy Tab S Android Development] Mrodfr:
Hello

I have this ROM installed and I don't really use my tablet because of the verry often crash, caused by the MALI GFX problem.

I just put in charge the tablet and wait after new release of this ROM for further tests and cross finger to see a better update (but difficult for the developper as we all can read).

Some months later (now), the tablet don't launch an application and crash even with just try to see battery status with 3ctoolbox. Crash now here arrive less than a minut and allways and need 4-5 reboot to see android again.

The application update (and goole stuff application) now crash the tablet pratically immediately.

Surely different apps code on all the aps and crash even more the GFX MALI outdated driver.

Don't waste your time with the actual version and wait for a new one. I will rever to android 10 during july-August for my summer vacancy (I need the tablet for that).
[Galaxy Tab S Android Development] luigi.lineageos:
Hello, thanks for your support to everyone. I have a problem: most of the applications crash (ex.:Firefox). From what I understood it's a matter of RAM that is not well managed by the ROM. Do you know how to fix that?
[Galaxy Tab S Android Development] glennza:
In the end I fixed it by buying a Tab S4. I tried many roms for the Tab S and they all had issues. Probably not the answer you were looking for but it was just too frustrating.

S4 is a great tablet. Smooth and fast.
[Galaxy Tab S Android Development] runekock:
Well, this rom is described as Alpha, so major problems are to be expected. As far as I can tell, @Hazou's lineage 17.1 rom has the best reputation for stability.
[Galaxy Tab S Android Development] xAmidox:
This tablet arrived for me and although it charges, it doesn't open the USB for data. Is there any way to flash the original ROM without Odin and put this custom one there?

it opens TWRP, I even managed to update it to the most current one, as it has TWRP, I'm sure they've already installed some custom rom on it, but it no longer boots and stays endlessly on the Lineage logo

Anyway, is there any original ROM that can be flashed via TWRP?
[Galaxy Tab S Android Development] Bigdrago:
I have the original rom. But think I had to flash it with Odin. Then I flashed lineage with twrp.
[Galaxy Tab S Android Development] xAmidox:
I just need some way to install stock with TWRP :/
[Galaxy Tab S Android Development] toscha42:
There is no way. Odin is the only chance for end users to install a stock ROM.

Cheers

Toscha
[Galaxy Tab S Android Development] xAmidox:
So can I consider this equipment lost? since there is no way to disable his USB for data, there is no driver that can do it, there is no occurrence of the PC when connecting any cable to it
[Galaxy Tab S Android Development] toscha42:
You can search for EDL mode. I've never used it and hence have no experience with it. But might be worth looking into it.

Ciao

Toscha
[Galaxy Tab S Android Development] Zakaria2328:
Reboot to download, hold power, vol down and home button and flash stock with Odin and samfw.
[Galaxy Tab S Android Development] Zakaria2328:
You sure it doesn't get recognized after going into download mode and installing the samsung driver on your pc?
[Galaxy Tab S Android Development] xAmidox:
yes, possibly the data track on the USB can be corrupted, since it only charges the battery, but I managed to flash it with the /e/ OS rom and it works, except for the data via USB within the Android itself!
[Galaxy Tab S Android Development] ROM_gamer987:
@Akhil99 Can you explain how to use the oss FP Hal? I got it in dt with all the changes needed (used https://github.com/VDavid003/androi...mmit/7c2644255ad3fd1b33410e047eee29edbf509c08 as reference) but idk how to do the service part, i tried looking at some commits such as https://github.com/RahulPalXDA/andr...mmit/85cdc0550902745ba8194a5ce94a4390bd8d1087 but i can't figure out how to make the service work with the HAL, even looking at other samsung devices using this oss hal (even some on los 18.1) They don't have services or anything that i could find
[Galaxy Tab S Android Development] ROM_gamer987:
Also here's a los 20 build in case someone wants to try it out: https://realmeme.realmemecloud.workers.dev/0:/lineage-20.0-20230419-UNOFFICIAL-chagalllte.zip_XNaVlJ

Has same issues as los 19.1 but with no encryption as FDE got removed in android 13, I'll properly update the post to android 13 later
[Galaxy Tab S Android Development] Akhil99:
klte-common: Build fingerprint 2.1-service · LineageOS/android_device_samsung_klte-common@7ea4ffa

Change-Id: Ifffe781deef90d861a0ad68f8649c265c249d0c5

github.com

klte-common: fingerprint: Bump version to 2.1 · LineageOS/android_device_samsung_klte-common@09e4b79

Change-Id: Id355acaf78387917252c56476da0ff8d3828f5d0

github.com

klte-common: fingerprint: Resolve compilation warnings · LineageOS/android_device_samsung_klte-common@7a56477

* fingerprint_enumerate had an incorrect signature * Quit partially initializing fingerprint_msg_t instances Change-Id: I09a05f3656c5bdc1e17fa76b5e68c56e0b7277de

github.com

These made FP (the service I was mentioning) work on android oreo LOS 15.1 on Galaxy S5 3G.

Sorry, I'm super busy rn, will try helping out whenever I can.
[Galaxy Tab S Android Development] ROM_gamer987:
Hm, must be that something changed since Oreo that makes it no longer work because I have all that added and yet the device does not see a fp sensor

Edit: I was able to get it to work now! It boots and sees the fp sensor, But the add fingerprint button is greyed out and see no obvious errors in logs
[Galaxy Tab S Android Development] bluess57:
Your previous log file had this error message

3786 E Fingerprint21: Unable to set callback

did you resolve it ?
[Galaxy Tab S Android Development] ROM_gamer987:
That error no longer appears with the oss fp hal, The Fingerprint hal is giving no obvious errors

Logs: https://realmeme.realmemecloud.workers.dev/0:/fpltest
[Galaxy Tab S Android Development] bluess57:
Check kernel messages for anything related.

Btw,Are you still selinux permissive?

Gpsd didn't start

E [B0: init: 1] init: Could not start service 'gpsd' as part of class 'main': File /vendor/bin/gpsd (labeled "u:object_r:vendor_file:s0") has incorrect label or no domain transition from u:r:init:s0 to another SELinux domain defined. Have you configured your service correctly?
[Galaxy Tab S Android Development] ROM_gamer987:
I did try permissive and fp didn't work either, I'll fix this gpsd error (Although it doesn't work anyway)
[Galaxy Tab S Android Development] bluess57:
Theres an ion error with process 3172

Which is fingerprint related

04-20 04:53:50.994 3172 3172 E ion : ioctl c0144900 failed with code -1: Out of memory
[Galaxy Tab S Android Development] ROM_gamer987:
Thanks I'll try to figure it out
[Galaxy Tab S Android Development] tolga1461:
How can I run this rom (or lineage 20) on chagallwifi version?
[Galaxy Tab S Android Development] bluess57:
The ioctl can be figured out by reading this:

Decoding an IOCTL Magic Number — The Linux Kernel documentation
[Galaxy Tab S Android Development] bluess57:
Don't, its still in development and see the posts about what's not working
[Galaxy Tab S Android Development] ROM_gamer987:
Yeah, sometimes system UI crashes out of nowhere, definitely not stable yet (still trying to figure out fp too)
[Galaxy Tab S Android Development] Akhil99:
Send logs, I think it's related to SELinux rules.