Microphone kept open for a long period of time.

[g33khubber]

I have been using this app for the whole of today and I realized there's a bug where after a while when I come back to the app, it will show that it has recorded for 90 minutes plus and sometimes it's 10 minutes plus. So I think the recording did not stop.

[DevEmperor]

Thanks for the report! I haven't been able to reproduce this yet, so a few details would really help me pin down when it happens:

1. When you notice it — is the Dictate recording bar still visible on your keyboard, or do you open a text field and only then see that it's been "recording" for a long time?
2. What happened right before — did you switch to another app, lock the phone / let the screen turn off, get a phone call, or just leave the phone sitting with the keyboard open?
3. When it happens, does tapping the mic stop it normally (and transcribe the long audio), or does it feel stuck?
4. Settings — do you have "Instant recording" enabled? And "Keep screen awake while recording"?
5. Device + Android version, and does it correlate with anything specific (a particular app, split-screen, a call interrupting)?

Any pattern you've noticed — "it always happens after I do X" — would be the most useful clue. Thanks again for helping track this down!

[g33khubber]

1. The recording bar is not visible; however, once I open a new text field, I see that it has been recording for hours.
2. Switching to another app is probably the most common thing that I did. I also let the screen turn off before.
3. Yes, tapping the mic stopped it normally.
4. None of the above.
5. I am using the Vivo X200 Ultra on the latest Android version. There is nothing specific; I am just using WhatsApp most of the time with this app.

[g33khubber]

I just Recall that another scenario will be when I toggle between Swift Key keyboard and this keyboard. It's quite common for the mic to stay open when I toggle between the two.

[djdubd]

Thanks for all the work on 5.0. The app keeps getting better.

A request about this change (mic stopping when the screen turns off): could it be made an optional setting instead of always-on? I get the reasoning, but it's a real regression for a common workflow.

For example, I'll be doing a long recording (journaling), not looking at my phone, and the screen times out on its own. In 5.0 that silently ends the recording and I lose the last 30+ seconds. Before 5.0 I could keep talking right through the screen turning off, then unlock and it was still recording. Stopping then inserted everything.

I've already set the app to unrestricted battery and allowed it to run in the background, so this isn't a background-permission issue on my end. Looking at the attached commit, it seems like it was an intentional change.

For what it's worth, I did notice the keyboard keeps an "interrupted recording," but the floating button doesn't surface it at all, and even in the keyboard there's no practical way to know which word I was cut off on to resume. So a saved interrupted recording isn't really a substitute for not being interrupted in the first place.

Would you consider a toggle like "Keep recording when the screen turns off"? Default it to the new behavior if you prefer, and let those of us who relied on the old behavior opt back in. Happy to open a separate feature-request issue if that's more useful than a comment here.

[g33khubber]

Hi all, I was also thinking if it's possible to get the floating mic button without Accessibility? This is bad for security and many banking apps outrightly ban it.

…

On Sat, 11 Jul 2026 at 13:01, djdubd ***@***.***> wrote: *djdubd* left a comment (DevEmperor/DictateKeyboard#147) <#147 (comment)> Thanks for all the work on 5.0. The app keeps getting better. A request about this change (mic stopping when the screen turns off): could it be made an optional setting instead of always-on? I get the reasoning, but it's a real regression for a common workflow. For example, I'll be doing a long recording (journaling), not looking at my phone, and the screen times out on its own. In 5.0 that silently ends the recording and I lose the last 30+ seconds. Before 5.0 I could keep talking right through the screen turning off, then unlock and it was still recording. Stopping then inserted everything. I've already set the app to unrestricted battery and allowed it to run in the background, so this isn't a background-permission issue on my end. Looking at the attached commit, it seems like it was an intentional change. For what it's worth, I did notice the keyboard keeps an "interrupted recording," but the floating button doesn't surface it at all, and even in the keyboard there's no practical way to know which word I was cut off on to resume. So a saved interrupted recording isn't really a substitute for not being interrupted in the first place. Would you consider a toggle like "Keep recording when the screen turns off"? Default it to the new behavior if you prefer, and let those of us who relied on the old behavior opt back in. Happy to open a separate feature-request issue if that's more useful than a comment here. — Reply to this email directly, view it on GitHub <#147?email_source=notifications&email_token=ALU456ZLKO3JUETEUMMNYYL5EHCYVA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIOJUGI2TIMZVG43KM4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L#issuecomment-4942543576>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALU456ZTSHZ2TNZANOHY6TT5EHCYVAVCNFSNUABFKJSXA33TNF2G64TZHM4DANZWGA2TGOJSHNEXG43VMU5TINZZGMZTKNZZGAYKC5QC> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/ALU4563BZACUTZFSWPZTFI35EHCYVA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIOJUGI2TIMZVG43KM4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KUZTPN52GK4S7NFXXG> and Android <https://github.com/notifications/mobile/android/ALU456YSK4BJEX3ZQVQ6A3T5EHCYVA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIOJUGI2TIMZVG43KM4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2K4ZTPN52GK4S7MFXGI4TPNFSA>. Download it today! You are receiving this because you authored the thread.Message ID: ***@***.***>