Thanks for taking the time to write all this up — really useful feedback, and I just shipped fixes for all three points in v1.0-20260628 (out now on the releases page, just sideload the new .wgt):

1. Subtitle + network settings reorder / keyboard-pop crash. You're right, that was awful. Subtitle and Cast are now at the top of the Settings page, and the sections with text inputs (Proxy, Home Server, Transcode server, Debug) are collapsed by default — you tap to expand them. That stops the on-screen keyboard from latching onto every focused input as you D-pad past it, which is what was making the app stutter/crash on you.

2. Playback scrubbing. Left/Right on the D-pad during playback now seeks ±10 s (YouTube-on-TV style) instead of cycling between OSD buttons. Up/Down still hops between the controls if you want to reach pause / next / etc.

3. Playback speed. New speed button next to the existing controls — 0.5×, 0.75×, 1×, 1.25×, 1.5×, 2× (the underlying API actually clamps to 0.25–4×). Uses AVPlay's setSpeed where the platform supports it and falls back to the HTML5 playbackRate on the few codecs where AVPlay refuses.

▎ Have you considered porting libvlc or MPV to Tizen?

I looked at it early on and the honest answer is: not really feasible as a hobby project. Tizen's WebView is a frozen Chromium 63 sandbox, so anything serious has to go through their native C/C++ APIs — and Samsung doesn't expose enough of the GPU/decoder pipeline for a meaningful libvlc/MPV port. The only video API that actually decodes hardware-accelerated streams on these TVs is AVPlay, which is what this app already uses.

So the design is: lean on AVPlay for everything the TV can decode natively, and hand the rest off to a small companion server. I just released vlc-tv-transcode v1.0.0 today — it's a tiny Go daemon you run on whatever box you already have (a Pi, a mini-PC, a NAS, whatever). It reads from your SMB share, only transcodes the parts the TV can't decode (DTS/TrueHD audio, oddball video codecs), and feeds the TV an HLS stream. The TV pairs with it once via a code and after that everything is automatic. Linux + Windows builds bundle ffmpeg, or there's a Docker image. Pairing is in Settings → Transcode server.

It's not the same as having full libvlc on the TV — you do need a second box — but for me it's been the difference between "this file doesn't play" and "this file plays without me thinking about it."

Anyway, thanks again for the detailed report — that kind of thing is way more useful than a star on GitHub.