v0.6.5 — safer logs and a sandbox repair

This release stops IPv6 addresses appearing in new event-log lines and adds an opt-in repair for one confirmed native-video sandbox failure on affected 2019 LG sets. The repair remains hardware-specific and needs a rooted Homebrew Channel; an experimental non-root Developer Mode procedure is documented separately.

If you shared event logs from v0.6.4: review or remove them

Event logs from v0.6.4 could contain a server's IPv6 address in plain text. Earlier releases may also be affected, but their exact scope has not been established.

What to do: If you shared an earlier event log, review where you shared it and remove or replace that copy where appropriate. The exposed values were network addresses.

What is fixed, and what is not: v0.6.5 redacts compressed and expanded IPv6 literals, bracketed addresses and ports, and IPv4-mapped tails from newly written event-log lines. Existing log files and copies already shared are not changed retroactively.

What's new

• Affected sandbox failures now offer a Repair button. On the known k5lp/k3lp failure, PlxNative explains the root requirement and asks for confirmation with Cancel selected by default. Confirming makes one attempt through the rooted Homebrew Channel service; no repair runs at startup or during ordinary playback. A timeout leaves the outcome unknown, and after success the app must be fully closed and reopened.
• A non-root Developer Mode procedure is available for testing. It uses LG's signed, version-matched configuration pair and webOS Dev Manager, with backup and rollback steps. The firmware mechanism and downloaded 4.10.0 pair were checked, but the complete procedure and write permissions have not yet been verified on an affected non-rooted TV. Read the experimental non-root guide before trying it.

Fixed

• IPv6 addresses no longer remain visible in new event logs. The local and report redaction paths now cover the literal forms emitted by connection diagnostics. This is a log-privacy fix, not an IPv6 connectivity change.
• The k5lp/k3lp sandbox error no longer ends at a dead-end instruction. Rooted users can request the same repair operation that restored playback for the issue reporter; the rooted-TV guide explains its limits and recovery path.

Compatibility

• Starts and renders the repair UI, verified on the dev set — 2019 LG set. An LG 49SM9000PLA reports platform release 4.10.2 (LG markets this generation as webOS 4.5). The confirmation, cancellation, unsupported-device behavior, and app-to-root-Homebrew identity probe were checked in a development build before release preparation. This set is not affected, and these checks did not run playback or the repair command.
• Repair and playback reported by someone else — one 2019 LG set. Robert confirmed that the equivalent root-shell command restored playback on a k5lp set running v0.6.3 in issue #74. That confirms the operation, not the new in-app button.
• Prior playback baseline — one 2021 set. mariotaku ran v0.2.1 on an LG 65UP7560AUD at platform release 6.5.2 and got a picture in issue #22. That remains prior-version evidence.
• Starts, and nothing further is known — every other firmware from webOS 4.0 up. The established loader boundary is unchanged. Static startup evidence says nothing about whether video plays; the matrix belongs in the technical audit.
• Does not start — webOS 3.9.2 and older. Symbols the app needs are missing from those firmwares, so the process is killed before anything appears.

Known issues

• The new Repair button has not been run on an affected set. Its command, confirmation, privilege probe, and fail-closed response handling were checked separately, while the affected reporter used a root shell. Success, timeout behavior, and persistence after relaunch or reboot still need an affected-device run.
• The non-root guide remains experimental. App-directory write permission, acceptance of the LG-signed pair, and playback have not been tested end to end on an affected non-rooted TV.
• Every other known issue in v0.6.4's audit remains unless superseded above, including the unconfirmed real-keymanager3 recovery path and the previously recorded one-off libmali crash.

Help test this release

If PlxNative identifies the missing-rtkmem sandbox on your k5lp/k3lp set, try the rooted Repair button or the experimental non-root procedure that matches your installation. Tell us whether the app reopened and the same video played in issue #74; a photo of the support line is useful and contains the app version, TV firmware/hardware label, and failure code. It working is as useful a report as it failing.

Installing

Download com.beb.plxnative_0.6.5_arm.ipk and install it with the Homebrew Channel or dev-manager-desktop. Normal installation does not require root; only the in-app sandbox repair requires a rooted, elevated Homebrew Channel.

Nothing in this distribution chain is signed, so this sha256 is what tells you the file you have is the file published here:

2c11a1e5cc38a2734b5e29779aae52612ddf3ae02555771a052a80469981e54f  com.beb.plxnative_0.6.5_arm.ipk

Installing and checking a download covers the other assets, how to check the hash on each platform, and the Developer Mode expiry that uninstalls your apps. This package bundles FFmpeg under LGPL-2.1-or-later and its complete corresponding source is attached to this release. Exactly what was built, verified and shipped is in the technical audit for v0.6.5.

What's Changed

• Backport IPv6 event-log redaction to v0.6 by @GLinnik21 in #83

Full Changelog: v0.6.4...v0.6.5