mirror of
https://github.com/Droid-Deck/DroidDeck.git
synced 2026-11-20 05:16:01 +00:00
Unify configurable control surfaces and profile management
This commit is contained in:
1 parent
aa3757eff1
commit
63004567fd
73 files changed
+5237
-5015
No files matched your search
@@ -6,12 +6,13 @@ a functional configuration UI and hardware validation on AYN Thor. The related
|
||||
maintainer discussions motivate this work; they are not approval of this
|
||||
implementation.
|
||||
|
||||
The configuration UI is intentionally basic. If maintainers accept the
|
||||
architecture, I am happy to refine the UX/UI in the same PR before merge, or in a
|
||||
follow-up PR, whichever they prefer. Navigation, binding discovery, layout
|
||||
editing, accessibility and localization need further attention. The current UI
|
||||
makes the architecture usable and testable rather than establishing its final
|
||||
interaction design.
|
||||
The configuration UI keeps the existing Setup tabs. Controller contains mode
|
||||
defaults, one profile list and device settings. Reusable layouts and actions are
|
||||
stored separately but are managed within each profile source. Direct editing on
|
||||
the target display has been exercised on AYN Thor, including editing above a live
|
||||
Steam session and keeping the secondary canvas separate from the main-screen
|
||||
tools. Revision-specific checks and remaining limits are recorded in the
|
||||
validation report.
|
||||
|
||||
## Why a shared system
|
||||
|
||||
@@ -26,11 +27,14 @@ The model separates three concerns:
|
||||
- **Source role:** physical controller, game overlay (primary) or auxiliary panel
|
||||
(secondary). Swapping the game and auxiliary panel between displays preserves
|
||||
the panel's role and bindings.
|
||||
- **Profile:** the actions assigned to controls in each role. Game and Desktop are
|
||||
the two editable built-in profiles. Auto selects by session mode; explicit
|
||||
selection supports a game running inside a desktop session.
|
||||
- **Surface layout:** the placement and size of local screen controls. The custom
|
||||
second-screen layout is stored independently for each built-in profile.
|
||||
- **Profile:** references to a physical binding preset and a layout/binding pair
|
||||
for each touch role. Game and Desktop are editable bases; named profiles can
|
||||
share parts. Auto has separate Steam and Desktop assignments. Opening a profile
|
||||
for editing does not activate it.
|
||||
- **Surface layout:** stable element IDs, types, names, positions and sizes.
|
||||
Named custom layouts can be used on either touch role. Actions belong to a
|
||||
separate binding preset associated with that layout. Two desktop profiles can
|
||||
share their physical bindings and layout while using different touch actions.
|
||||
|
||||
A binding selects native controller output, a DroidDeck action, or disabled.
|
||||
Native output continues through the existing game/Steam path, optionally with a
|
||||
@@ -44,7 +48,8 @@ flowchart TD
|
||||
Secondary[Secondary custom controls] --> PadBridge
|
||||
Deck[Deck pads and grips] --> DeckControls
|
||||
BLE[Steam Controller BLE reports] --> TritonInputRouter
|
||||
Profiles[Game / Desktop profile by source role] --> Router[InputRouter]
|
||||
Library[Saved profiles, layouts and binding presets] --> Profiles[Resolved active profile by source role]
|
||||
Profiles --> Router[InputRouter]
|
||||
PadBridge --> Router
|
||||
DeckControls --> Router
|
||||
TritonInputRouter --> Router
|
||||
@@ -55,7 +60,8 @@ flowchart TD
|
||||
Motion --> Held
|
||||
Held --> Guest[Existing guest keyboard and mouse output]
|
||||
Native --> Steam[Steam Input or guest controller consumer]
|
||||
Layout[Independent surface geometry] --> Secondary
|
||||
Layout[Independent surface geometry and element IDs] --> Secondary
|
||||
Layout --> Primary
|
||||
```
|
||||
|
||||
These are routing relationships, not additional asynchronous queues. Native
|
||||
@@ -66,8 +72,10 @@ publication is performed by the existing source adapters and writers.
|
||||
| Component | Responsibility |
|
||||
| --- | --- |
|
||||
| `InputProfile` | Logical controls, source roles and supported actions |
|
||||
| `InputProfiles` | Versioned persistence, selection, validation and migration |
|
||||
| `InputSurfaceLayout` | Bounded custom lower-screen geometry, separate from actions |
|
||||
| `InputLibraries` / `InputLibrary` | Versioned reusable parts, validated references, selection and migration |
|
||||
| `InputProfiles` | Compatibility API for the compiled active profile and legacy migration |
|
||||
| `InputSurfaceLayout` | Bounded normalized touch geometry and legacy layout migration |
|
||||
| `InputSurfaceSource` | Independently owned per-element routing through existing pad/Deck publishers |
|
||||
| `InputRouter` | Resolve channels on profile changes, route events, track held outputs |
|
||||
| `PadBridge` | Existing player slots plus independently owned local touch sources |
|
||||
| `DeckControls` | Source ownership for Deck grips, contacts, coordinates and clicks |
|
||||
@@ -88,12 +96,103 @@ captured keys match a device identity plus Android keycode/scancode, rather than
|
||||
persisting a transient Android device ID. System-reserved keys remain with
|
||||
Android. This is not a per-device calibration system.
|
||||
|
||||
### Controller navigation
|
||||
|
||||
Setup keeps its existing top-level tabs. Controller starts with Desktop and Game
|
||||
mode defaults, followed by one profile list and inline device settings. Opening
|
||||
or editing a profile does not activate it; the session menu owns the active
|
||||
profile override. Quick-menu overrides are called out beside the default selectors.
|
||||
|
||||
Each profile opens Physical controller, Main screen or Second screen. Control
|
||||
cards and touch element rows open the same large properties editor. Layout
|
||||
editing uses the full-size canvas and one draggable, expandable Tools palette. Back
|
||||
returns to the source and profile being edited, rather than the library root.
|
||||
Saved layouts and reuse commands live inside the relevant source editor; there
|
||||
are no parallel top-level layout, binding and profile catalogs.
|
||||
|
||||
New profiles copy actions and custom geometry independently by default. Users
|
||||
can explicitly keep physical controls shared at creation, or copy/link a source
|
||||
from another profile later. Reusing a saved layout can link geometry without
|
||||
linking actions. Make independent copies both geometry and actions for that
|
||||
source. Reset actions affects only the selected profile, preserving its layouts
|
||||
and detaching shared actions before resetting them.
|
||||
|
||||
Main-screen visibility remains a global device setting. Color and opacity belong
|
||||
to each saved touch layout. The standard gamepad is an ordinary editable layout:
|
||||
its legacy positions, appearance and stick options are migrated into elements.
|
||||
Other saved resolutions remain selectable layouts. The previous fixed gamepad
|
||||
renderer and its separate editor are removed; only its placement calculation is
|
||||
retained for migration. Vibration, radial stick dead zone, Joy-Con VR, global
|
||||
shortcuts and timing diagnostics are inline below the profile list. This adds no
|
||||
settings reads or queues to input dispatch.
|
||||
|
||||
### Session profile composition
|
||||
|
||||
Both the session drawer and launcher controls sheet expose Profile, Physical
|
||||
controller, Main screen and Second screen. Choosing a profile loads its three
|
||||
saved parts; choosing one part creates a mode-specific override without editing
|
||||
the source profile. Game and Desktop remember their choices separately. Auto
|
||||
resolves the corresponding default profile. Selecting a complete profile clears
|
||||
part overrides. Save as new profile creates independent copies of all three
|
||||
parts, including geometry, appearance and actions.
|
||||
|
||||
Fixed lower-screen tabs, side selectors and click bars are removed. Deck pads
|
||||
and grips, one or two Deck pads, grips alone, the mouse trackpad with keyboard,
|
||||
and a compact gamepad are ordinary editable layout/binding presets. Their menu,
|
||||
keyboard and click buttons are ordinary elements too. The compact gamepad reuses
|
||||
the previous panel geometry calculation. Existing fixed-panel selections migrate
|
||||
to profile controls on first use. Schema 4 also preserves version-3 custom
|
||||
layouts and converts legacy fixed layout references without changing physical
|
||||
mappings. Active quick-menu parts cannot be deleted.
|
||||
|
||||
Mouse touchpad gestures reuse `TouchpadGestures` for relative movement, tap,
|
||||
hold-drag, two-finger scrolling and secondary clicks. A tap uses the element's
|
||||
configured click action; it does not reposition the pointer. Gesture outputs use
|
||||
owned router channels and are suppressed while input is suspended or until a
|
||||
held contact returns to neutral after a profile change. Native Deck pad mode
|
||||
retains contact/position reporting and click behavior for Steam Input.
|
||||
|
||||
### Reuse and migration
|
||||
|
||||
Existing `FakeInputWriter` transports, player assignment, guest keyboard/mouse
|
||||
output, `KeyboardHost`, second-screen presentation and `DeckControlsPanel` are
|
||||
reused. The custom lower-screen editor arranges the existing buttons, sticks,
|
||||
trackpads and grips; it does not create another emulated controller.
|
||||
output, `KeyboardHost` and second-screen presentation are reused. The existing
|
||||
button, stick, d-pad and trackpad views now live in `InputSurfaceView`; there is
|
||||
no parallel fixed controller panel. The custom editor arranges the existing button, stick, d-pad and trackpad
|
||||
views; it does not create another emulated controller. Trigger elements provide
|
||||
press/release input. A new element is unassigned until an action is explicitly
|
||||
saved. Native sticks and pads retain their existing click gestures.
|
||||
Movement/contact and click are separate assignments for sticks and trackpads.
|
||||
Both use the same properties editor and router ownership rules; migrated click
|
||||
bindings remain editable, and a custom mouse pad can assign its click separately.
|
||||
|
||||
The editor uses the target display at actual size. On a dual-screen device,
|
||||
Add, Undo, Snap, Save and element properties stay on the activity display; the
|
||||
auxiliary display is a full-size canvas with no toolbar inset. On one display,
|
||||
a draggable Tools bubble expands into those same tools, including element
|
||||
properties, and collapses to leave the canvas accessible. Properties replace the
|
||||
canvas and return to the same draft. Snapping aligns centers and edges with
|
||||
other elements and the display, including during resize. Done persists geometry and actions together; Cancel discards the
|
||||
draft after confirmation. The preview has no input sources and cannot send
|
||||
input to the running session.
|
||||
|
||||
Primary custom layouts follow the existing on-screen-controls visibility setting;
|
||||
Steam's touch-controller mode retains priority. Secondary layouts use Profile controls mode. Terminal, desktop and dashboard
|
||||
remain separate panel modes. Steam-managed touch controls keep their own editor; a new editable layout
|
||||
can start empty or copy a saved custom layout.
|
||||
|
||||
Legacy Game/Desktop mappings, key captures, active selection and lower-screen
|
||||
geometry migrate to the library together. Legacy element IDs preserve their
|
||||
existing logical bindings. New elements use stable independent IDs, so two
|
||||
buttons can have different actions or hold the same output without releasing
|
||||
one another. Referenced parts cannot be deleted, and editing an unsupported
|
||||
library version cannot overwrite it. Shared edits show their scope; copying a
|
||||
binding preset from a profile relinks only that profile's selected role.
|
||||
|
||||
Library decoding, validation and preset resolution happen during configuration
|
||||
or profile activation. Dispatch uses preconfigured router channels, with no
|
||||
preference reads, profile lookups or new asynchronous queues. The physical native
|
||||
identity path and frame-based stick motion remain in place. These properties do
|
||||
not substitute for a fresh latency comparison on hardware.
|
||||
|
||||
The old touch-only mapping and Select-as-Steam settings migrate once into Game's
|
||||
primary-screen and physical bindings respectively. Their redundant UI is removed.
|
||||
@@ -193,13 +292,15 @@ Steam Mobile Touch retains its own Steam-managed layout and protocol. Its widget
|
||||
do not pass through this local remapper. The VR-specific input path also remains
|
||||
separate. Existing gestures retain their recognizers and share output ownership.
|
||||
|
||||
The two built-in profiles and the bounded custom lower-screen editor are the
|
||||
implemented scope. Named profile libraries, import/export, per-app selection,
|
||||
macros, tap/hold behavior, multi-button activation chords and a complete freeform
|
||||
multi-display editor are deferred. One button emitting Ctrl+F is supported;
|
||||
pressing multiple buttons to activate a new binding is not implemented.
|
||||
The local UI revision includes named profiles, reusable binding presets and
|
||||
custom layouts edited on either display. Import/export, automatic per-app
|
||||
selection, macros, configurable tap/hold behavior and multi-button activation
|
||||
chords remain deferred. One button emitting Ctrl+F is supported; pressing
|
||||
multiple buttons to activate a new binding is not implemented. Built-in Steam
|
||||
touch layouts retain their separate Steam-managed editor.
|
||||
|
||||
Native remaps stay within compatible report families. Additional hardware
|
||||
Physical native remaps stay within compatible report families. Generic custom
|
||||
buttons choose a supported button output explicitly. Additional hardware
|
||||
adapters must join before publishing consumed controls; an Activity-only
|
||||
interceptor cannot cover every raw device. Future adapters should use this
|
||||
contract without replacing device-specific calibration or protocol handling.
|
||||
@@ -240,3 +341,53 @@ project's direction, whether adapters join at the right point, and whether the
|
||||
shared ownership/lifecycle contract is suitable for future input sources. The
|
||||
validation document distinguishes device-tested behavior, host regressions and
|
||||
remaining coverage. UX/UI refinement can follow agreement on those decisions.
|
||||
|
||||
### Settings polish and display targeting
|
||||
|
||||
The session Profile row expands to show the three saved parts and the editor.
|
||||
Choosing the profile remains a separate selector. Session editing opens its
|
||||
settings on the spare display, when available; element properties and editor
|
||||
commands stay on the activity display. Main-screen placement over a running
|
||||
session uses a transparent canvas so controls can be arranged around game UI.
|
||||
Existing visible controls are suspended while editing.
|
||||
|
||||
Schema 5 adds an explicit main/secondary/both target to saved layouts. Migration
|
||||
infers the target from existing profile and quick-menu references, preserving
|
||||
layouts already used on both screens. Layout rows render a miniature with the
|
||||
same `InputSurfaceView` renderer; unused legacy copies are retained under Other
|
||||
saved layouts. Newly created layouts belong to the source being edited.
|
||||
|
||||
Action editing retains a draft for each route and action type. Sticks assigned
|
||||
to a digital action press above 55% on either axis and release below 35%; a
|
||||
trackpad holds a digital action during contact. These semantics are explained
|
||||
next to the action. Horizontal scroll uses the same router and existing evdev
|
||||
REL_HWHEEL / Wayland axis transport, with independent fractional accumulation.
|
||||
No additional event thread or queue is introduced.
|
||||
|
||||
### Screen-key consolidation
|
||||
|
||||
Schema 6 imports the retired screen-key overlay into normal saved profiles,
|
||||
layouts and element bindings. The active old set and each named saved set become
|
||||
separate imported profiles. Current Game/Desktop defaults and quick selections
|
||||
remain unchanged; the settings page explains where to find the imported profiles.
|
||||
The old editor, overlay View, guest-key dispatch path and session-menu entries
|
||||
are removed. Only a one-time reader of the old preferences remains.
|
||||
|
||||
Migration converts normalized centers and density-based sizes into the shared
|
||||
layout geometry. Key chords, four-way directions, separate eight-way stick
|
||||
bindings, toggle buttons, built-in symbols, custom image references, shape and
|
||||
opacity are retained. Blank stick diagonals keep their previous behavior of
|
||||
pressing neighboring cardinal directions. Imported images are decoded once per
|
||||
view, sampled to at most 512 pixels, and read only from the app's existing image
|
||||
directory. New buttons can choose text or an existing built-in key symbol.
|
||||
|
||||
A converted library and the original raw preferences are committed together
|
||||
before old preference entries are removed. Invalid data or capacity failures do
|
||||
not erase the old library or keys, and settings show a pending-import notice.
|
||||
The backup is recovery data, not a second runtime input configuration.
|
||||
|
||||
Toggle buttons use `InputSurfaceSource` and the same router ownership as every
|
||||
other element. Releasing one owner cannot release another owner's held key.
|
||||
Menu suspension, profile changes, cancellation and detach release latched output.
|
||||
Physical native input continues through its existing fast path; no queue, timer
|
||||
or additional event thread is introduced for these features.
|
||||
@@ -4,6 +4,264 @@ Recorded on 2026-10-24. These results distinguish the device-tested candidate fr
|
||||
the later upstream rebase and host regression fixes. They do not establish zero
|
||||
latency or complete coverage of every controller and session mode.
|
||||
|
||||
## UI publication candidate, 2026-11-06
|
||||
|
||||
The implementation was updated through upstream `a1bc8467f` (merge `aa3757eff`).
|
||||
The generic action selector now says **Scroll**; binding summaries still state
|
||||
the configured direction. Closing the docked session drawer now invokes its
|
||||
ordinary close action instead of disabling the second-screen presentation.
|
||||
The global-reset regression compares against a pristine compiled library, which
|
||||
includes the editable gamepad's keyboard element.
|
||||
|
||||
- All **944 input/UI tests in 125 suites passed**. The final full JVM run completed
|
||||
**3,598 tests in 493 suites: 3,573 passed, 25 failed, no errors or skips**.
|
||||
The failures are the same unchanged upstream log-export tests (24) and
|
||||
case-sensitive WoW add-on import test (1) described below. Input/UI and global
|
||||
settings reset passed in this full run.
|
||||
- Initial full runs exhausted this Mac's free disk and produced secondary native
|
||||
runtime/idle failures. Obsolete local test APKs were removed. The completed run
|
||||
used a local Gradle init script with one worker and a fresh test JVM every 25
|
||||
classes to bound temporary-file use. No repository test configuration was
|
||||
weakened and no tests were excluded from the completed run.
|
||||
- The APK passed runtime-input, session-asset, native dependency, alignment and
|
||||
v1/v2/v3 signature checks. SHA-256:
|
||||
`611814f11cbac4bab7f97dac5c0b0657d85d8dfbd6b40b741bda1fc13efa6f83`.
|
||||
It was installed over the separate Input Test app with its environment intact;
|
||||
as with earlier local candidates, Rust store engines were omitted.
|
||||
- On AYN Thor, closing the lower-screen menu with its X restored the existing
|
||||
controls instead of revealing Android. The live Steam editor, separate lower
|
||||
canvas and upper tools/properties, profile previews, saved layouts, and action
|
||||
pages were exercised. A single Trigger selection added a centered, selected
|
||||
element; the reported occasional extra tap was not reproduced. The temporary
|
||||
editor change was discarded.
|
||||
- The user also verified native controls, profile switching, trackpad/pointer
|
||||
and scrolling behavior on the immediately preceding UI candidate. This is
|
||||
distinct from automated UI navigation and the historical latency measurements.
|
||||
|
||||
Actual display captures and test reports are retained locally under
|
||||
`app/build/reports/input-publish/`. Screenshot publication is subject to the
|
||||
user's review. No new latency measurement was made for this UI revision.
|
||||
|
||||
## Input settings polish, 2026-11-06
|
||||
|
||||
The final input/UI host run passed **941 tests in 124 suites, zero failures**.
|
||||
New coverage includes retained route/action drafts, centered element creation
|
||||
without a placement tap, collapsed quick-profile settings, schema-4 migration
|
||||
with a layout shared across both screens, target/scroll serialization, and
|
||||
horizontal scrolling through both guest mouse backends. Existing physical native
|
||||
fast-path and ownership tests remain green.
|
||||
|
||||
The settings use stable DroidDeck Input labels, contextual axis/contact hints,
|
||||
color swatches, opacity sliders and rendered layout thumbnails. Diagnostics now
|
||||
open a result dialog and explain how to record a sample and what it measures.
|
||||
Shortcut rows show the actual assignment and offer Restore to default.
|
||||
|
||||
No new latency comparison was taken for this UI revision. The normal native
|
||||
controller path is unchanged. New horizontal wheel work happens only for a local
|
||||
scroll action. The user's environment installation is retained. Device verification is recorded below.
|
||||
|
||||
### Screen-key removal and Thor verification
|
||||
|
||||
The old screen-key overlay, standalone editor, layout panel and separate runtime
|
||||
key sender are removed. Schema 6 imports the old active set and every named set
|
||||
as editable profiles. Current defaults and selections are kept. Tests cover
|
||||
idempotent import, chords, normalized geometry, per-element opacity, shapes,
|
||||
image references, symbols, custom diagonals, and retaining the original data
|
||||
when migration cannot complete. A backup and the converted library are committed
|
||||
together before the old preferences are removed.
|
||||
|
||||
New shared element tests exercise latched keyboard and native controller buttons,
|
||||
shared ownership, cancellation, menu suspension and profile replacement. Separate
|
||||
diagonal bindings release previous keys and preserve neighboring-direction
|
||||
fallbacks. No additional input queue or thread is used.
|
||||
|
||||
Final APK installed over `com.droiddeck.launcher.inputtest` on AYN Thor:
|
||||
`6618be55c28a52746b6504656a480845d25d8a34114daa1829aad5dbb5b5e729`.
|
||||
Packaging checked runtime inputs, session assets, native library dependencies and
|
||||
v1/v2/v3 signatures. As with the earlier test packages, Rust store engines are
|
||||
omitted; the Steam/Desktop environment is retained.
|
||||
|
||||
On-device checks:
|
||||
|
||||
- The expanded Profile has readable text and one visibly grouped block.
|
||||
- Profile source rows and saved-layout rows show bounded thumbnails. The previous
|
||||
black rectangle overflowing the list no longer appears.
|
||||
- The original anchored color menu shows its color swatches.
|
||||
- Steam → Controller → Edit opens settings on the spare display.
|
||||
- Main-screen editing opens on the activity display over live Steam. A second
|
||||
on-device crash was found and fixed: returning from lower-display settings must
|
||||
use the existing activity dialog, not a Presentation on the default display.
|
||||
- Adding a button immediately centers and selects it. Its properties and symbol
|
||||
picker open on the main display.
|
||||
- Secondary-screen editing leaves only the canvas below and tools above. Adding
|
||||
a trackpad centers and selects it without requiring another placement touch.
|
||||
- Temporary edits were discarded. Comparing the before/after saved libraries,
|
||||
excluding new default schema fields, found no changes to the user's profiles,
|
||||
geometry, bindings or selections. Schema changed from 5 to 6.
|
||||
- Steam remained READY after closing the editors; the final device log contained
|
||||
no new fatal exception.
|
||||
|
||||
The test device had no old screen-key sets to import. Legacy content migration
|
||||
and toggle ownership were verified by host regression tests, not by a new
|
||||
physical-input latency or end-to-end game test. Evidence is under
|
||||
`app/build/reports/input-polish/`; the final installable copy is
|
||||
`app/build/input-ui/DroidDeck-Input-Test-unified-screenkeys-2026-11-06.apk`.
|
||||
|
||||
## Unified editor and session profile composition, 2026-11-06
|
||||
|
||||
The fixed gamepad and its separate editor are replaced with a saved editable
|
||||
layout rendered by `InputSurfaceView` on either display. The old fixed lower
|
||||
panel, tab switches and separate mouse trackpad view are removed. Deck pads,
|
||||
grips, single pads, the mouse trackpad and a compact gamepad are editable presets;
|
||||
their menu, keyboard and click buttons are normal elements. The compact preset
|
||||
reuses the previous panel geometry calculation.
|
||||
|
||||
Schema 4 migrates version-2 overlay references, mappings, saved positions,
|
||||
appearance and stick-click preferences, and version-3 fixed lower layouts.
|
||||
Other resolution-specific positions remain saved layouts. Future or invalid
|
||||
libraries are not overwritten. Physical mappings retain their identities and
|
||||
assignments. Existing custom layouts remain intact.
|
||||
|
||||
On two displays, the activity hosts Add, Undo, Snap, Done and full-size properties;
|
||||
the other display contains only the canvas, without a reserved toolbar strip.
|
||||
On the main display a draggable Tools bubble expands into the same tools,
|
||||
including Properties. The editor snaps centers and edges while moving and
|
||||
resizing. Both source pages list their actual elements. Device settings are
|
||||
inline below the profiles.
|
||||
|
||||
The quick menu selects a whole profile or overrides Physical controller, Main
|
||||
screen and Second screen independently. Game and Desktop selections are separate.
|
||||
Changes do not mutate the source profiles; saving a combination creates independent
|
||||
copies. Returning to Auto clears the overrides. Tests cover serialization,
|
||||
reference validation, deletion protection and preservation of source profiles.
|
||||
|
||||
The complete input/UI host run passed **931 tests in 124 suites, zero failures**.
|
||||
Coverage includes full-size shared editing, floating tools, display removal,
|
||||
geometry migration, source ownership during detach/layout replacement, quick-menu
|
||||
composition and saving, native Deck clicks and mouse gestures. Tap and hold use
|
||||
the configured element click; ordinary taps do not reposition the cursor. Profile
|
||||
changes and menu suspension suppress delayed gesture presses until neutral.
|
||||
The neutral-stick/physical-input regression remains covered.
|
||||
|
||||
No new end-to-end latency measurement was performed for this revision. The
|
||||
physical controller path remains unchanged. Touch output uses the existing
|
||||
owned router and guest transports without an additional event queue. Mouse
|
||||
movement is delivered synchronously; tap/hold recognition reuses the existing
|
||||
`TouchpadGestures` timings. The local APK omits the Rust store engines and uses
|
||||
the separate Input Test application ID.
|
||||
|
||||
Device verification on AYN Thor confirmed the four quick selectors and saved
|
||||
second-screen presets, draggable/expandable tools, full-screen properties and a
|
||||
canvas-only secondary display. WindowManager reports the main editor at
|
||||
`[0,0][1920,1080]`; the secondary canvas uses the full `1240×1080` display.
|
||||
The installed library migrated to schema 4 with existing profile references,
|
||||
bindings and custom layouts preserved. A previous test migration's unchanged
|
||||
main overlay geometry was corrected from its window-size copy to its saved
|
||||
1920×1080 version. No user-edited geometry was replaced.
|
||||
|
||||
Final APK SHA-256: `c13326d11f5e8de3b878d83b296ba2f77495baf5c35d1d00dbb0327333c0277d`.
|
||||
Runtime assets, native library dependencies and v1/v2/v3 APK signatures passed
|
||||
verification. Focused editor/input checks passed again after fixing Compose 1.6
|
||||
fullscreen dialog sizing. Live game/desktop input and perceived latency with this
|
||||
final build still need user testing; the device checks above cover UI and migration.
|
||||
|
||||
## Controller integration and upstream update, 2026-11-06
|
||||
|
||||
Merged upstream `bf693d7f7` into the working branch as `ba5876bf6` before the UI
|
||||
integration. This includes 90 upstream commits, including radial stick dead zones
|
||||
and mouse-button handling. The merge keeps routed source ownership and the new
|
||||
upstream raw-stick behavior; the targeted input merge checks passed.
|
||||
|
||||
Controller now contains two default-profile selectors, one profile list and a
|
||||
Device settings entry. Source-specific action editing and saved layouts are
|
||||
inside each profile. New profiles are independent by default, with an explicit
|
||||
option to share physical controls. Direct editing and Hide tools / Show tools
|
||||
are retained. No input-event queue or preference lookup was added by this UI
|
||||
reorganization.
|
||||
|
||||
The first full host run executed 3,580 tests in 490 suites: 3,555 passed and 25
|
||||
failed, with no skips. All 926 input and UI tests in that run passed. The failures
|
||||
are in unchanged upstream log-export tests (24) and WoW add-on import tests (1).
|
||||
The log fixtures require `SecureDirectoryStream`, unavailable in this macOS JDK;
|
||||
the WoW test assumes `Foo` and `foo` refer to different paths, while this host
|
||||
filesystem is case insensitive. A direct Java filesystem probe confirmed both
|
||||
conditions. The log-export failures also reproduce when run separately. The
|
||||
affected production and test sources match `origin/main`. These host limitations
|
||||
have not been hidden by disabling tests or changing production code.
|
||||
|
||||
The final input/UI-only run passed all 927 tests in 122 suites.
|
||||
|
||||
Additional final checks cover integration in the existing Setup tabs, the lack
|
||||
of duplicate Layout/Configure entries, back navigation, independent creation,
|
||||
explicit physical sharing, and preserving elements while hiding editor tools.
|
||||
Rendered UI checks cover 360×800, 640×360 and 960×600 dp. Earlier latency results
|
||||
below are not a fresh measurement of this revision.
|
||||
|
||||
The final 26 profile/library/editor checks passed again after the source-specific
|
||||
control lists and sharing labels were finalized. The APK passed session-asset
|
||||
matching, runtime-input attestation, native dependency/export checks, alignment
|
||||
and signing validation. It uses the same local HTTPS/direct-release download
|
||||
adaptations as the previous build and still omits the store Rust engines.
|
||||
|
||||
Installed the update over `com.droiddeck.launcher.inputtest` on AYN Thor without
|
||||
clearing data. Verified Setup → Controller → Desktop → Second screen → Edit on
|
||||
screen; the canvas opened on the lower display, Hide tools / Show tools worked,
|
||||
and selecting the right trackpad opened large properties on the main display.
|
||||
Returned without saving; the stored input-profile preferences matched the backup
|
||||
exactly. Device settings had no persisted overrides before or after this check.
|
||||
No fresh gameplay or latency measurement was performed in this UI pass.
|
||||
|
||||
Final APK SHA-256:
|
||||
`f1d16a503661055a0abe8cc954d3fc94f6b9a1c1c626ac38b6c88dba478810d1`.
|
||||
|
||||
## Local UI revision, 2026-11-05
|
||||
|
||||
This revision adds the Profiles / Layouts / Bindings libraries, migration of the
|
||||
previous settings, independently identified touch elements, and a direct editor
|
||||
on either display with properties on the activity display.
|
||||
|
||||
- The complete JVM/Compose run passed 3,306 tests across 467 suites, with no
|
||||
failures, errors or skipped tests. The native identity fast-path checks remain
|
||||
in that suite. After the final editor-window adjustment, all nine editor and
|
||||
adaptive-layout UI tests passed again.
|
||||
- New coverage includes legacy mapping/geometry/selection migration, shared
|
||||
physical presets with separate touch actions, explicit private copies, safe
|
||||
deletion/reset, unsupported schema preservation, independent element actions,
|
||||
overlapping held outputs, suppression across profile/menu changes, and inert
|
||||
editor previews, independent stick/trackpad click bindings, same-view
|
||||
detach/reattach, and saving a draft after the auxiliary display disappears.
|
||||
- Both Steam and Desktop quick settings expose the same input library entry.
|
||||
- Compose navigation was exercised at 360×800, 640×360 and 960×600 dp. Rendered
|
||||
images are generated under `app/build/reports/input-ui/`. The properties Save
|
||||
control stays outside the scrollable content on the short landscape screen.
|
||||
- Updated the existing `com.droiddeck.launcher.inputtest` installation on AYN
|
||||
Thor from 0.6.0 to the local 0.6.9 build without clearing its data. The official
|
||||
package was not replaced. A local backup of the two input preference files was
|
||||
taken before migration; all 61 saved Desktop bindings matched after migration.
|
||||
- On Thor, exercised the quick-settings entry, library navigation, full-size
|
||||
editing on both displays, selection on the lower display with properties on
|
||||
the main display, moving an element, Undo and Done. After undoing the move and
|
||||
saving, the complete stored library matched the pre-edit data.
|
||||
- The earlier Thor latency measurements below apply to the earlier candidate,
|
||||
not to this library/editor revision. No new end-to-end or dispatch latency
|
||||
claim is made.
|
||||
|
||||
The complete local runtime build passed session-asset matching, runtime-input
|
||||
attestation, native export/dependency validation, alignment and signature checks.
|
||||
The local build-script copy used HTTPS for the Debian archive and direct GitHub
|
||||
release downloads when the unauthenticated API was rate limited; checksum and
|
||||
revocation checks remained enabled. No build-script changes are included in the
|
||||
source diff. As before, the test APK excludes the Epic/GOG/Amazon Rust engines.
|
||||
The installed APK SHA-256 is
|
||||
`3e3f41589d45b70294f2d59404f591ae76f2ceba8488657e8821aab1bca224b3`.
|
||||
|
||||
Before publishing, also test on Thor: create two Desktop profiles sharing physical
|
||||
bindings; give them different touch actions; edit and resize on the actual lower
|
||||
display; open properties on the top display; save/cancel; swap screens; return
|
||||
from Android Home; disconnect/reconnect the auxiliary display; and repeat the
|
||||
paired physical-button latency measurement. Verify primary custom overlays with
|
||||
on-screen controls enabled and secondary layouts in Custom controls mode.
|
||||
|
||||
## Revisions and environment
|
||||
|
||||
The Thor candidate was `5021e7ac` on base `ac0909ea`, with the local temporary-file,
|
||||
|
||||
Reference in new issue
Block a user