Wear OS: fix Enter not sending in WhatsApp and dictation not landing in Browser (#294)

[m5991]

Fixes #294.

Hi! I really enjoy your apps. I paid for Dictate Wear and it was such a bummer when it
didn't work on my watch, I really was looking forward to have something like this. I know my way around adb tooling and had a feeling the fix might be simple,
so I vibed my way through it, and this is what I ended up with.

What was wrong

Two problems I described earlier turned out to be the same story.

Enter (from the numpad) didn't submit. performEnter committed a literal "\n". Most fields never treat that as a
submit — they declare an editor action in imeOptions and act on that instead. So in WhatsApp the
transcript landed in the box and just sat there, and in the Browser the search never ran.

Something that surprised me, and that may not be obvious without a Galaxy Watch (and logcat) in hand: the field
Dictate binds to is usually not the app's own. On Wear OS 6 / One UI 8 Watch, WhatsApp and Keep Notes
both go through Samsung's RemoteInput text-entry activity, so the IME sees

onStartInputView: pkg=com.samsung.android.honeyboard action=DONE imeOptions=0x6 inputType=0xc041

and the app's own window only returns (with inputType=0x0, not an editor) once that DONE action
fires. That's why Keep Notes seemed to work while WhatsApp didn't. Samsung Browser is the exception —
a directly bound field declaring IME_ACTION_SEARCH.

Dictated text disappeared in the Browser. After a transcription the service commits the text and
immediately calls requestHideSelf(0). Over the browser's search field that teardown races the commit
and the text is dropped — the same field accepts keypad input fine, where no hide is involved. And even
where the text survived, hiding took away the ⏎ needed to send it.

What I changed

1. ⏎ fires the field's declared action (SEND / SEARCH / GO / DONE …), falls back to a real
   KEYCODE_ENTER when there is none, and commits a newline only for multi-line editors.
   IME_FLAG_NO_ENTER_ACTION is respected.
2. The post-dictation auto-hide now only happens when the field has no pending action — unchanged for
   notes-style fields — and the keyboard hides once the action has actually fired, so it isn't left
   sitting opaque over the result.

44 added lines in one file, no UI changes.

How I tested

Galaxy Watch8 (SM-L330), Wear OS 6.0 / One UI 8.0 Watch, tethered to Dictate on a Galaxy S26 Ultra
(Android 16).

	before	after
WhatsApp	text lands, Enter does nothing	Enter fires DONE, message sends
Browser	dictated text never appears	text lands, Enter runs the search
Keep Notes	works	still works, still auto-hides

Important to say, the way to send a transcripted is with the Enter button of the numpad, it is usable but maybe not ideal.

The part I can't check

I only have my own watch, so I'm blind to how this behaves elsewhere. The risk I'd flag: a field that
declares an action but expects a newline anyway would now submit instead of adding a line. I tried to
guard that with the multi-line and IME_FLAG_NO_ENTER_ACTION checks, but a device reporting things
differently could behave differently. If you'd rather shape this another way, I'm happy to re run checks in my watch.

This is my first time contributing to an open source project like this. Hope it helps.

🤖 Generated with Claude Code

https://claude.ai/code/session_01EBBqERL2Akg9cYDXRaaK7D

[DevEmperor]

Hi @m5991, thank you, and sorry this sat for so long. Your diagnosis was spot on. By the time I got to it, the file had changed underneath it (the #363 rework), so #294 is now fixed in 6872eeb instead:

• ⏎ fires the field's action.
• After a dictation into a send/search/done field, the keyboard stays open and shows the recognized text with a button shaped like the action, so you no longer need the numpad to send.
• A new watch setting, "Auto-send" (off by default), fires the action right away.

Two things from your PR made it in as a follow-up in e0a18db:

• Your finding that WhatsApp and Keep reach the keyboard through Samsung's RemoteInput screen with DONE, which my watch never showed me. Auto-send now covers DONE too, or it would have done nothing in WhatsApp.
• Closing the keyboard after ⏎ has fired an action.

Both ship with the next watch release, and I'd be glad to hear how WhatsApp behaves on your Watch8 then. Thanks for a first contribution this careful. Closing in favour of those two commits.