From: newskrawl@krawl.org   
      
   On Tue, 18 Nov 2025 07:58:19 -0000 (UTC), NewsKrawler wrote:   
      
   >  only Whisper Keyboard (which   
   > doesn't rely on Android's RecognitionService at all) worked on the first   
   > tap with Copilot (without being logged into Microsoft).   
      
   When you press the mic button on your default keyboard while you're in   
   Copilot, does it work the first time, every time?   
      
   Of the integrated on-IME ASR's I tested, SendRight crashed every time so I   
   moved to the other IMEs that run automatic speech recognition inside the   
   input method process to insert text via the IME API.   
      
   Transcribo worked slightly differently than Whisper C++ in that Transcribo   
   doesn't require holding down the microphone button to convert speech to   
   text offline. You still have to tap its mic button though, even after I set   
   Transcribo to recognize speech automatically (so I have to work that minor   
   issue out later).   
      
   What's happening is that when a tap is performed in any app's text field,   
   Android hands focus to an IME. That IME pulled up is whatever keyboard is   
   set to the default (or the last-used, in the case of Whisper/Transcribo   
   settings). The problem with Copilot is the next step.   
      
   When you press the mic button on the delegation ASR's such as   
   AnysoftKeyboard, FlorisBoard, GBoard, Google Voice typing, HeliBoard,   
   OpenBoard, Samsung Keyboard, etc., the IME starts the platform recognizer   
   (either by SpeechRecognizer.startListening or by launching a   
   RecognitionService/voice-typing intent) which takes exclusive mic access   
   and runs ASR locally (or on the cloud if enabled).   
      
   The Android system recognizer posts results back to on the   
   Speechrecognizer.Listener (or intent) which the IME forwards to   
   InputConnection.commitText.   
      
   At this point, any app, including Copilot must still have a valid   
   InputConnection and focus at the time the IME forwards the text. That the   
   the step which seems to be failing since I can see flashes at times as the   
   ASR tries to communicate with the Copilot text focus and fails more often   
   than not.   
      
   Whisper C++ and Transcribo (and Sayboard when set up as an integrated   
   on-IME ASR) run ASR inside the IME pricess and call   
   Inputconnection.commitText directly, eliminating intermediate handoffs by   
   inserting text synchronously from the IME itself.   
      
   Of the three working on-IME ASRs, I'm leaning toward Transcribo but what I   
   need to test is accuracy (where Sayboard with the small English model is   
   the worst) and speed (where Whisper.cpp seems to be slow, and anything else   
   that might matter which I'll learn during testing, such as all of them seem   
   to be a bit flaky with Copilot).   
      
   Still, I need to know from someone who can run a quick test of Copilot.   
   1. Install Copilot on Android   
   2. Do not log into a Microsoft Account   
   3. Do not press the Copilot microphone button   
      
   If you do press the Copilot mic button, it "appears" to work without   
   needing an account but it's crippleware as it only works for a short time.   
   Then it requires the account for the Copilot mic button to work.   
      
   When you press the mic button on your default keyboard while you're in   
   Copilot, does it work the first time, every time?   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)