Skip to content

Android: add hardware keyboard commands and BrailleSense 7 alternatives - #33

Open
edenkizerccr-coder wants to merge 13 commits into
masonasons:mainfrom
edenkizerccr-coder:android-braillesense-keyboard
Open

edenkizerccr-coder wants to merge 13 commits into
masonasons:mainfrom
edenkizerccr-coder:android-braillesense-keyboard

Conversation

@edenkizerccr-coder

Copy link
Copy Markdown

Android users can operate timeline and post actions with Control shortcuts, including layered alternatives for devices that do not deliver Control+Shift reliably. This contributes the keyboard and reading improvements developed and tried in a separate private FastSMRW 0.6.1 copy, adapted to the official app's existing identity and services.

BrailleSense 7 testing reported by the contributor

  • I have not found a layered command that fails in my use so far.
  • Reply works reliably across repeated uses, including after the first use.
  • Only a couple of the Control+Shift commands have worked on my BrailleSense 7, and those have been less reliable.
  • I do not know how the Control+Shift commands behave on other Android devices; I have not tested them there.
  • I am seeing less timeline jumping now.

Both the Control+Shift commands and their layered alternatives are retained. These are the contributor's physical-device reports from the private build, separate from automated checks; they do not claim exhaustive testing of every function or acceptance of the adapted official-app build on every device.

Changes

  • Add a single 47-command catalog, a complete help reference and a keyboard-delivery test. Control+V, release, then Control+letter supplies the corresponding Shift command. Control+G sends only from the focused main writing field; editing keys keep their normal behavior.
  • Accept complete key press/release streams and the release-only Android events observed on BrailleSense 7, without duplicating actions or submissions. Cancelled, duplicate and held inputs are covered, as is recovery after a lost release.
  • Track actual accessibility or keyboard focus on posts, reject stale or ambiguous post targets, and restore the original accessibility delegate when leaving timeline reading. Ordinary typing avoids command lookups and hierarchy scanning.
  • Remember local post/viewport positions separately for each account and timeline, prevent retained UI requests from replaying, and keep cached rows associated with timeline identities when tabs move or close. Refresh and opening Home keep place; Control+Z or Go to top requests top explicitly.
  • Make Mentions and Mastodon Messages easier to reach. Announce pending original-text retrieval for Edit, deduplicate pending editor requests and discard cancelled delayed editors.
  • Add the separate keyboard reference to the Android guide, include a native Word shortcut guide, and add user-facing changelog entries under 0.6.1.

The official package, app name, version, signing configuration, update checks and Firebase notification route remain in place. No private-fork package/signing material, credentials, background polling dependency or APK is included. The shared C++ core and other platform front ends are unchanged; this is an Android input/accessibility binding for existing actions. BuildConfig generation is enabled for the diagnostic version label. The existing notification permission guard now explicitly catches SecurityException instead of runCatching so Android lint recognizes its handling; delivery semantics are retained.

Validation

  • 95 Android unit tests pass: 92 keyboard/focus/position/request tests and the 3 existing push-crypto tests.
  • Android Kotlin compilation and APK packaging pass using the unchanged, previously verified official native libraries. Android lint reports 0 errors and 5 existing warnings. A clean native NDK build was not rerun because that toolchain is not installed in this environment; the local validation accommodation is outside the submitted checkout.
  • All 47 catalog commands are checked with complete and release-only input, every layered Shift alternative is checked, and all five send forms are checked with both event forms.
  • The four-page native Word guide was opened/rendered with Microsoft Word and every page reviewed. Native text and all 47 catalog entries match; personal document properties are blank.

Maintainer review points

Local position preservation intentionally takes priority over unsolicited core/server cursor selections after a local viewport exists. The current native select_row event has no reason field; an explicit synchronous jump-to-parent is allowed through a two-second same-timeline intent window. A shared event reason would allow a cleaner distinction between deliberate navigation and server-marker restores. This behavior needs maintainer review, especially with home position synchronization enabled.

The saved anchor must still be available for exact restoration, and this does not restore a particular word or braille cursor within a post. Editor source fetching still depends on the existing server/worker request; cancelling ignores the delayed editor rather than aborting that request. Testing with other Android keyboards and screen readers remains welcome.

edenkizerccr-coder and others added 13 commits November 3, 2026 01:31
Retain Control+Shift commands alongside layered alternatives and document the contributor’s reported BrailleSense 7 results.

Co-Authored-By: OpenAI Codex <noreply@openai.com>
Accept full and release-only input, preserve writer editing and post focus, and provide both Control+Shift and layered alternatives.

Co-Authored-By: OpenAI Codex <noreply@openai.com>
Part of the Android hardware keyboard and BrailleSense 7 contribution.

Co-Authored-By: OpenAI Codex <noreply@openai.com>
Part of the Android hardware keyboard and BrailleSense 7 contribution.

Co-Authored-By: OpenAI Codex <noreply@openai.com>
Part of the Android hardware keyboard and BrailleSense 7 contribution.

Co-Authored-By: OpenAI Codex <noreply@openai.com>
Part of the Android hardware keyboard and BrailleSense 7 contribution.

Co-Authored-By: OpenAI Codex <noreply@openai.com>
Part of the Android hardware keyboard and BrailleSense 7 contribution.

Co-Authored-By: OpenAI Codex <noreply@openai.com>
Part of the Android hardware keyboard and BrailleSense 7 contribution.

Co-Authored-By: OpenAI Codex <noreply@openai.com>
Part of the Android hardware keyboard and BrailleSense 7 contribution.

Co-Authored-By: OpenAI Codex <noreply@openai.com>
Part of the Android hardware keyboard and BrailleSense 7 contribution.

Co-Authored-By: OpenAI Codex <noreply@openai.com>
Part of the Android hardware keyboard and BrailleSense 7 contribution.

Co-Authored-By: OpenAI Codex <noreply@openai.com>
Part of the Android hardware keyboard and BrailleSense 7 contribution.

Co-Authored-By: OpenAI Codex <noreply@openai.com>
Part of the Android hardware keyboard and BrailleSense 7 contribution.

Co-Authored-By: OpenAI Codex <noreply@openai.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant