Repository navigation
Conversation
webOS 10 and later ship a flutter-type screensaver app with no qml/ dir, so the historical bind-over-qml/main.qml has no target and apply.sh exits with 'Could not detect screensaver QML target' (webosbrew#14). - detect both generations: legacy qml keeps the old bind, flutter firmware get a staged qml app (stock appinfo retyped to qml + screensaver-main.qml) bind-mounted over the app directory - add 'apply.sh remove' plus a Restore-stock button so the overlay can be undone without a reboot (webosbrew#13) - best-effort sam block/release after staging Verified on OLED77B2PUA, webOS 10.3.1 (fw 33.31.61): apply/remove round-trip clean, sam accepts the staged qml appinfo after a sam reload. Fixes webosbrew#14, helps webosbrew#13.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #14, helps #13.
Problem
On webOS 10+ firmware (verified on an OLED77B2PUA, webOS 10.3.1 / 33.31.61) the
stock screensaver app is a flutter bundle:
type: flutter,mainpointingat the app directory, and no
qml/at all. The historicalbind-over-
qml/main.qmlhas no target, so apply exits withCould not detect screensaver QML target(#14), and the same gap breaks everyworkaround built on top of it.
Change
assets/apply.shnow detects both generations:qml/main.qml)/var/lib/webosbrew/custom-screensaver/: the stock appinfo retyped toqmlwithmain: qml/main.qml, plus this app'sscreensaver-main.qml,then bind-mount the whole staged directory over
/usr/palm/applications/com.webos.app.screensaver. sam accepts theqml-typed copy of the flutter appinfo on 10.3.1.
Also:
apply.sh remove(+ a Restore stock screensaver button) unmounts theoverlay immediately — no reboot needed (Cannot restore original screen saver! #13)
Validation
(
getAppInforeportstype: qmlafter a sam reload)the type change up from block/release alone — a
systemctl restart sam.service(or reboot) settles it if the screensaver misbehaves aftertoggling. Happy to iterate on making the transition smoother if you'd
prefer the restart be automatic.
The screensaver QML itself is unchanged; this only fixes the apply/remove
machinery so the existing aerial qml runs on new firmware.