yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab S Android Development] shaglord:
This might not change any of that but I noticed something interesting today.

Default governor is "interactive" but if you look at the clocks even at light loads it rarely goes down, if at all. I always thought that was strange.

Today I noticed that after turning on "battery save mode" in the status menu, the clocks look a looot better. It's still the same governor and same peak clock, but instead of hovering around max it's now around 1000MHz. Much better.
[Galaxy Tab S Android Development] teohub:
@ Hazou

I wanted to push the issue again. Apparently only T700 is affected. Is it possible to match this with T705 if the error can be fixed this way.

Thanks in advance.
[Galaxy Tab S Android Development] Hazou:
Hi,

There are at the moment a couple of problems I know of. And they are all not very easy to fix. Most of the time, because I cant reproduce them.

- T700 with mic problem. I don't own one, so i can't test anything. Is there any moment in time in another LOS version where it did work?

- Supercell games dont start. The problem most likely lies within the firmware. Lineage 17.1 for our device and multiple others are missing something. On 14.1 they do work, so there has been a change. But where?

- The device won't go to sleep. I hoped I got something, but that isn't it. And again, I cant reproduce it, so it is most of the time hoping for someone to see a fix.

- The device in interactive schedular mode (CPU) has high frequency. But this has something to do with the powerhal. It should be fixable, I or others just dont have spend time on it.

I hope offcourse that all those problems will eventually be fixed. Even maybe in higher LineageOS versions. But as I said, they are all not that easy to do.
[Galaxy Tab S Android Development] teohub:
Hi,

Whatever you can do is appreciated.

All versions of Lineage or Crdroid before 17.1 had no Mic problem on T700. T700 seems to be the only device with this problem on 17.1.
[Galaxy Tab S Android Development] Hazou:
Okey, so you can confirm that lineage 16.0 has a working mic.

Does a logcat/dmesg gives anything? When trying the mic?

Could be forgotten path/implementation or even denials from selinux. I believe that from 17.1 and on, even in permissive mode, selinux will stop processes from doing something
[Galaxy Tab S Android Development] @meone:
I'm testing Hazou's latest on my T705 (lineage-17.1-20230915-UNOFFICIAL-klimtlte.zip with "latest" Opengapps pico from February '22) & must say I'm surprised how snappily it runs after booting. Too bad I'm having similar video crashing issues, not with Youtube but with VLC SMB-streaming in my home network.

I can't reproduce it perfectly but after x minutes rather than hours watching video, the tab hangs with sound endlessly repeating one tone and only a forced reboot will cure it. I've tried grabbing last_kmsg via adb but the tab doesn't respond post-crash. With Lineage installed the HOME/PWR/VOL-UP key combo for TWRP/recovery no longer seems to work, I had the idea that maybe I might adb-pull logfiles booted into TWRP -?

last_kmsg reset after the last crash ("no errors detected"), but here's a earlier one, saved on Windows with special chars muddled. Almost every line says "zcache: zcache compress error ret -22". ( pastebin, seems I'm not allowed to post attachments)

The tab is not rooted but root adb is enabled in developer settings.
[Galaxy Tab S Android Development] Hazou:
Ha oke. I will add it to the list. Good find. Hopefully that gets us somewhere.
[Galaxy Tab S Android Development] @meone:
@Hazou: I admire your cool but I know the chances we'll get anywhere with such limited logs are not quite zero. ;)

Same crash in Total Commander media player with system default codecs... new last_kmsg (pastebin), but nothing helpful ("No errors detected").

I managed to boot into TWRP right after the crash this time, any chance to get logs from /system that would be overwritten on reboot? Or are all the relevant ones kept in memory only?

I'll try to capture the logcat on PC and make it crash again...
[Galaxy Tab S Android Development] shaglord:
Is it possible the sleeping problem is that the testing app is being battery optimized when the screen turns off?

It's just a theory because I'm getting quite good battery life. I do use battery saver though because it allows the clocks to come down under low load. Default they don't.
[Galaxy Tab S Android Development] glennza:
I wouldn't think so but it's a good point and worth investigating.

Is it doing the same on yours?
[Galaxy Tab S Android Development] shaglord:
I can confirm that the mic isn't working on T700.
[Galaxy Tab S Android Development] Hazou:
As of yesterday. @retiredtab has made a patch for it. And it has been succesfully tested for working of the MIC. If you all don't mind. It will be implemented in the security updates off Oktober.
[Galaxy Tab S Android Development] teohub:
Thank you very much. Will test it as soon as available. 😁👍
[Galaxy Tab S Android Development] @meone:
@Hazou: I just PMed you (I think, in a "conversation") the logs for two BSODs, one streaming from local network and another one playing back from internal storage. The second one took more than 4 hours and I thought maybe my issue was network-related, but I just needed to turn my back and poof.

dmesg and logcat cuts out two seconds or so before the BSOD, so the thing to go on is last_kmsg.

Unable to handle kernel NULL pointer dereference at virtual address 00000190
Internal error: Oops: 5 [#1] PREEMPT SMP ARM

So far this is the error I've seen after every crash, also in a pastebin I linked to earlier but overlooked.

Maybe the one tombstone in the bugreport from a VLC crash is also useful, but it's from earlier. VLC often stops playing when streaming (over SMB) after a couple of minutes, but the connection doesn't drop, it just begins playing the next file, and it doesn't crash.

Steps to reproduce:

1. start logging (as root; I used "adb logcat -v time > logcat.log" in Windows CMD window #1 and

adb shell
while true; do dmesg -c; sleep 1; done

in another, it gives a nice colorful output that can be copypasted into a text file)

2. play 2-5 TV episodes files in a row (in fullscreen), either from nas (quicker) or local storage

3. wait for the sound of one endlessly repeating tone ;)

4. do "adb shell "cat /proc/last_kmsg" > last_kmsg.txt" as quickly after reboot as possible
[Galaxy Tab S Android Development] ctoph0:
Where is the latest available? the link in the first post is dead
[Galaxy Tab S Android Development] shaglord:
Click on the github link in Hazou's signature. The repository is called something like "5420 common". In it go to the "Releases" section.

Hazou isn't the OP but he has newly compiled builds for t70x/t80x tablets.
[Galaxy Tab S Android Development] teohub:
Releases · HazouPH/android_device_samsung_universal5420-common

Contribute to HazouPH/android_device_samsung_universal5420-common development by creating an account on GitHub.

github.com

;)
[Galaxy Tab S Android Development] bnjroos:
My SM-T705 is running on latest official firmware, can someone recommend a step by step guide on how to flash lineage os 17.1 (never flashed an android device before but I am computer literate) ? So many different guides on the internet with slightly different info that I do not want to take the chance to brick my device that is damn slow but still working.
[Galaxy Tab S Android Development] toscha42:
It's not rocket science. Basically the description from #1 in this thread still is valid. You need:

Odin - a software to install a custom recovery on a Samsung device.

TWRP - a custom recovery to install a custom ROM on an Android device.

Cheers

Toscha
[Galaxy Tab S Android Development] bnjroos:
Thanks, indeed followed and managed, damn my tab is back to normal speed and netflix is working.
[Galaxy Tab S Android Development] shaglord:
I thought first running CF-Autoroot was required to flash custom files in Odin. Like for unlocking the bootloader.
[Galaxy Tab S Android Development] DonChino:
Thank you for the wonderful port, because this tablet has been mothballed for 3+ years; so this is a good stable point in case Android 11, 12, 13 do not work., haha...

I did not test everything; but one thing that irked me is that my tablet will not connect to my WiFi if the SSID is hidden, although I do not know if that is the tablet or LineageOS. I also ran into the LineageOS rebooting into TWRP after install; so you MUST wipe all partitions, except SD Card and OTG.

(y)
[Galaxy Tab S Android Development] bnjroos:
I did not need it, only booting in download mode then flashing TWRP with Odin.

Lineage OS 17.1 was working like a charm however I decided to install GApps and now it has become significantly slower and has random reboots.

What is the process to make a clean re-install of the OS only ?

I basically only need netflix and youtube (this is why I added GApps but it seems to make troubles). Netflix installed from apk worked great.
[Galaxy Tab S Android Development] shaglord:
Wipe the system and data partition in twrp before sending the zips over via usb. That's as clean as it'll get.

If you want to tweak the pad with the supplied Deathly Auditor app/kernel you need root. So while you're in twrp you could flash a magisk patched image of boot.img.
[Galaxy Tab S Android Development] jeff862:
Lineage 20 update for Samsung T700
[Galaxy Tab S Android Development] aelfinn:
Cool, when will you have that ready?
[Galaxy Tab S Android Development] draentor:
Great job @Hazou , I flashed my SM T-800 a few days back and the battery life is great without gapps. Thanks for your work :)

Does everyone have a good Deathly Adiutor profile for a daily usage ?
[Galaxy Tab S Android Development] shaglord:
I suggest this.

1 global undervolt (i was able to do -100mV)

2 enable battery saver in notifications menu (otherwise the cpu never downclocks)

3 set a cpu temp throttle profile in deathly to 1600/1700/1800 (same number in all fields except the last(600), depending on what you can sustain. With a cooling mod you can sustain 1700 or 1800. If no mod 1400-1600.
[Galaxy Tab S Android Development] glennza:
Can't seem to find the battery saver. Where is the notifications menu you mention? Thanks
[Galaxy Tab S Android Development] shaglord:
This.

When turning it on you still get proper max frequencies but on low cpu load with this on it downclocks to 800-1000MHz which is normal behavior. Without thia enabled the "interactive" governor appears to work like "performance".

(on the device i photographed I don't need it because it's plugged in all the time, but my portable T700 it works better with battery saver on)
[Galaxy Tab S Android Development] glennza:
Ahhh, nice. I'll give it a try
[Galaxy Tab S Android Development] Hazou:
Ye, the powerhall does this ramp up. It has 3 options.

Go to settings -> Battery -> Energysaving and performance (I think this is the translation to English from dutch)

Chose profile Battery saving. This will only change the Interactive governor ramp up. And will not enable any additional battery saving features that button does.

We can change the powerhall profiles. Energysaving is at this moment the same as the one in 14.1. Balanced does ramp down, but much less. Performance is always up.
[Galaxy Tab S Android Development] Hazou:
LineageOS 17.1 for Samsung Galaxy Tab S 8.3/10.1 Wifi/LTE (T700/T705/T800/T805)

Changelog:

Update System Security Patches to ASB 2023-10

Update Powerhall

Fix T700/5 microfoon (@retiredtab)

HACK: Stop 5 Powercell games from crashing

Update kernel

Release Samsung T700/5 T800/5 LineageOS-17.1-15-10-2023 · HazouPH/android_device_samsung_universal5420-common

LineageOS 17.1 for Samsung Galaxy Tab S 8.3/10.1 Wifi/LTE (T700/T705/T800/T805) Changelog: Update System Security Patches to ASB 2023-10 Update Powerhall Fix T700/5 microfoon HACK: Stop 5 Powercel...

github.com
[Galaxy Tab S Android Development] prodj77:
Thanks for your hard work!!, your ROM is the most stable for my chagallwifi 👍🏼. The only thing I would like is the possibility of a "certified device" in future ROMs. Thanks again Hazou 🙂.
[Galaxy Tab S Android Development] Hazou:
You mean SafertyNet? I don't know if it is possible,but we can try.
[Galaxy Tab S Android Development] prodj77:
Yes my friend, SafertyNet pass. Thank you.
[Galaxy Tab S Android Development] teohub:
@Hazou

Can confirm Mic on T700 is now working.

Rom is working fine and smooth.

Battery life is good using CPU Govenor conservativex.

Great Job!

Thank you very much for fixing Mic Issue.
[Galaxy Tab S Android Development] shaglord:
I noticed the clocks on Hazou 1.5 look good with the default interactive governor but with the slider in Power Saver settings turned down from Balanced (middle) to Power Save (left). The rom appears more fluid than on 1.4 while still downclocking.

This is just my observation. I'm not a pro or anything.
[Galaxy Tab S Android Development] H421:
I'm a newbe, where should I flash it, boot or system image
[Galaxy Tab S Android Development] ISoreo:
boot, btw low memory killer seems bug i will patch and upload on this thread
[Galaxy Tab S Android Development] ISoreo:
Update for klimtlte (i have this device only) : Swappiness 60 -> 160, LMK should be fixed (i tested it with open both firefox and youtube)
[Galaxy Tab S Android Development] ISoreo:
Update for klimtlte : update GPU value should be more smooth, undervoltage the CPU should be help about reduce the high temperature
[Galaxy Tab S Android Development] knosso:
Hello there. With deathly it is possible to undervolt as well. I with -45mV and a piece of scrap metal in top of the soc with thermal paste I can run at 1800MHz on LOS 14. I'm still reading through the various pages of the thread to see if deadly is available for this rom before installing. Also kudos for enabling the fingerprint because it has always been disabled in custom roms.
[Galaxy Tab S Android Development] knosso:
I was wondering wether it was possible to enable all 8 cores at the same time for this device. It is possible on other devices with the same SOC but discouraged on Tab S (both 8.4 and 10.5) due to poor cooling. Now I am planning to hard mod the battery to have double or triple capacity, at that point since i need to cut open the back anyway I might just as well improve the cooling system and push the SOC to the limit.
[Galaxy Tab S Android Development] pzduz:
I'm using klimtlte lineage 14.1 just upgrade to this ROM using twrp twrp-3.5.2_9-0 it seem the Bluetooth is not working i install both lineages and crdroid but still facing same problem does anyone else having this problem or I'm installing it wrong
[Galaxy Tab S Android Development] ISoreo:
after i searching a lot, our cpu 5420 is b.L which is big.LITTLE 4 cores 2 clusters so me or our dev can't enable that for 8 cores in the same time but it can switch the cpu task for heavy jobs between big and LITTLE
[Galaxy Tab S Android Development] xthakila:
Great work been away. Will give it a full try tonight. So far causes the tablet to slow down significantly also the display flickers.
[Galaxy Tab S Android Development] ISoreo:
I will try to patch RAM, LMK and ZRAM, anyway please try this first update for klimtlte temporaly with GPU and CPU patched
[Galaxy Tab S Android Development] xthakila:
This one is much better tablet is much snappier.

What are the GPU and CPU limits that you have patched in? I think maybe you undervolted the CPU too much in the last patch.

Also the patch killed root. Will have to re-root it. But that's not a big deal.
[Galaxy Tab S Android Development] ISoreo:
I adjust min max value and change some parameter of GPU make more smooth, from LOS 14.1 I can undervoltage upto -37.5 mV so I'm adapted to 17.1 too, that's make my tab S good in CPU temp, for about root you can patch it with magisk before flash by TWRP
[Galaxy Tab S Android Development] xthakila:
So far the boot patch seems to be running smoothly. Battery drain seems to be okay.

Magisk cannot be applied because flashing the boot image over magisk makes it un-rooted
[Galaxy Tab S Android Development] ISoreo:
I mean after you download my boot image you can patched the boot image by magisk before you reboot to recovery and flash it. mine work fine
[Galaxy Tab S Android Development] xthakila:
If I do this

1. Flash your image file

2. Flash magisk

Won't magisk just overwrite the boot?
[Galaxy Tab S Android Development] ISoreo:
Magisk will patch my image file instead
[Galaxy Tab S Android Development] xthakila:
Okay patched magisk over your boot image. Cheers. Will have to check if it works after a few games of warzone

Edit 1 seems to be fine. Battery drain seems to be within a tolerable range.
[Galaxy Tab S Android Development] kyddox:
Do anyone knows if Zoom app works correctly with this ROM? I have tried several ROMs but the Zoom's app audio doesn't work and i need it for my daughter's online classes.
[Galaxy Tab S Android Development] xthakila:
There are some people that reported microphone problems. Mine works fine on the sm-t705. Haven't tried zoom.
[Galaxy Tab S Android Development] teohub:
Can this bootimage be used with T700 klimtwifi ?
[Galaxy Tab S Android Development] glennza:
Can you have a look in Deathly Adiutor under Usage Statistics. Does yours show as being "Awake" all the time and does the Deep Sleep show zero or some actual time? Thanks
[Galaxy Tab S Android Development] shaglord:
Sure. This is my T700 on Hazou 1.5 + power saver and -88mV global offset.

I'll leave it on for a few hours and post another screenshot afterwards.
[Galaxy Tab S Android Development] shaglord:
And a couple of hours later.
[Galaxy Tab S Android Development] glennza:
That's useful to know. Your T700 is going into deep sleep but mine - even with just a clean install - won't. Yet it does with LOS 14.1. There doesn't seem to be any logic to it??
[Galaxy Tab S Android Development] shaglord:
Try pulling the slider to Power Save (left) clear open apps then wait for a while with the screen off. Also, don't charge it.

My tablet only slept for 3h out of 5h uptime. I did not use it for 2h. I just used it for maybe 5 min total. So screen off doesn't automatically mean sleep.
[Galaxy Tab S Android Development] glennza:
I've had it on powersave for the past couple of days. It never sleeps, doesn't matter what I do. If I leave it with the screen off for 24 hours, then it's awake for 24 hours!.

I was sure it was something I'd done that's why I did a full wipe, reinstalled Hazou's rom + Magisk and did nothing else. Problem still there. Do the same with the Deathly 14.1, all works fine.
[Galaxy Tab S Android Development] glennza:
Just took this screenshot right now, see what I mean? Tried using a wakelock detector but it didn't tell me anything useful
[Galaxy Tab S Android Development] shaglord:
Has Deathly got root permission?

Is it possible you're on the snapdragon version?
[Galaxy Tab S Android Development] Hazou:
Hmm. Your GPU is also stuck at 350. Do you have a screen protector? Is it always charging or off?

In one of your logcat/dmesg it stated that de displaydriver is always active.
[Galaxy Tab S Android Development] doctrin:
Hey @Hazou ...though using my Tab S since 2014, your ROM completely renews my SM-T800.

But I have serious crashes while playing videos. Even in playing the videos in background hangups accure frequently.

How can I assist in fixing this issue?
[Galaxy Tab S Android Development] Hazou:
A dmesg/logcat could help. But if you have a sample video? I can test myself.
[Galaxy Tab S Android Development] glennza:
I think I've fixed it. It seems to be related to the CPU Minimum speed in DA. I had it set to 800MHz. When I dropped it back to 100MHz it started sleeping normally. Now have it at 350MHz and it's still sleeping normally.

I really don't know how that survived a full wipe because it was not sleeping and I hadn't made any changes to DA. I wouldn't think that it writes any changes into hardware?

Anyway, I'm glad I've got it running normally so I don't have to keep it on the charger all the time.

Thanks for your help guys!
[Galaxy Tab S Android Development] Hazou:
That is good to hear. Still a bit weard. Maybe the kernel cpufreq governor doesnt let is deep sleep when the min clock is set to high.
[Galaxy Tab S Android Development] glennza:
When I sent you the logs, it was after a full wipe and fresh install. I had not changed any of the DA settings. My understanding is that none of the kernel settings survive a reboot. DA sets them every time you start the tablet?

I do have another problem though... Nothing major just an annoyance,

The other 17.1 ROMs that I had previously used got stuck at the PIN login screen. You put your PIN in and it would sit there and then go blank. you could try this many times and get the same thing. After a few minutes it would let you log in.

Now, when I installed the Hazou ROM, it didn't do this. It logged in straight away. It was the first 17.1 ROM where this worked properly. Except now it has started having the same problem!!! It's as if the "security driver" isn't loading until very late in the boot procedure and PIN login isn't available.

Anyway, I don't reboot very often so it's not a big issue.
[Galaxy Tab S Android Development] shaglord:
Sleep or not, are you seeing actual improvement in battery life?
[Galaxy Tab S Android Development] glennza:
Too early to say. It's always been on the charger when I wasn't using it. Now it's sleeping I can leave it unplugged and see how long the battery lasts.
[Galaxy Tab S Android Development] Hazou:
I have the issue too when the PIN in the first stage at startup doesn't always login. Seems the Keystore or something is loaded a bit late in the process.
[Galaxy Tab S Android Development] glennza:
I'm sure it wasn't doing it when I first installed your rom a couple of versions ago. I was impressed that you had fixed it! I don't know why it would start doing it again. Not a big deal though.
[Galaxy Tab S Android Development] Hazou:
I can think of one thing. Between 1.2 and 1.3 there has been a change in using the fingerprint. Maybe that has something to do with it.
[Galaxy Tab S Android Development] stsz1954:
Hello.

I have installed this rom on my SM-T700. The speaker volume is low even at maximum volume. I turned off AudioFX which helped a bit. Do I have to make changes to mixer_paths.xml file to change this? Where is this file on this device?

Thanks for any help.
[Galaxy Tab S Android Development] glennza:
You can increase the volume in Deathly Adiutor. I set mine 3db higher and it's much better. Be careful not to set it too high or it will distort.
[Galaxy Tab S Android Development] shaglord:
Deathly app (root) can increase volume.

On both my tablets I do it but I didn't experience a volume drop compared to stock rom. It was simply low before too. Thankfully we have Deathly to fix it.

It will introduce some distortion. You don't want to overdo it.

Woops, glennza already replied. My bad.
[Galaxy Tab S Android Development] stsz1954:
Hello.

Thanks for the tip about fixing the sound using Deathly Adiutor. I raised the gain by 3db. The sound is much better, but I still have to turn AudioFX off and I have to set the sound to maximum volume. Are there any other modifications to further improve sound?
[Galaxy Tab S Android Development] binhminhluc9h:
Hello,

These links are not working, can someone help me to re-upload again, many tks
[Galaxy Tab S Android Development] shaglord:
Hazou in this thread has recently uploaded newer builds for this tablet on his github. Check out the link in his signature.

I believe it's a continuation of the work by the OP.
[Galaxy Tab S Android Development] dmitry1986:
Hi all! I have a sm-t807 and sm-t800 tablet in my hands, I flashed them with the latest October firmware. After installing the firmware, I installed Google services - everything worked great. But after a while I noticed that the 807 was discharged very quickly, literally before our eyes. It’s definitely not a matter of the battery; with the stock firmware the battery holds its charge many times longer. I didn’t install the software, only what was built into Google services. Has anyone already encountered this problem? Is there a solution to this problem? Perhaps I can provide some logs from my tablets?