[GH-ISSUE #23135] issue: Transription not working reliably #19892

Closed
opened 2026-04-20 02:25:44 -05:00 by GiteaMirror · 13 comments
Owner

Originally created by @tilllt on GitHub (Mar 27, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/23135

Check Existing Issues

  • I have searched for any existing and/or related issues.
  • I have searched for any existing and/or related discussions.
  • I have also searched in the CLOSED issues AND CLOSED discussions and found no related items (your issue might already be addressed on the development branch!).
  • I am using the latest version of Open WebUI.

Installation Method

Docker

Open WebUI Version

0.8.11

Ollama Version (if applicable)

0.18.3

Operating System

Debian

Browser (if applicable)

Android / Chrome 146.0.7680.164 (Play Store Version)

Confirmation

  • I have read and followed all instructions in README.md.
  • I am using the latest version of both Open WebUI and Ollama.
  • I have included the browser console logs.
  • I have included the Docker container logs.
  • I have provided every relevant configuration, setting, and environment variable used in my setup.
  • I have clearly listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc).
  • I have documented step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation. My steps:
  • Start with the initial platform/version/OS and dependencies used,
  • Specify exact install/launch/configure commands,
  • List URLs visited, user input (incl. example values/emails/passwords if needed),
  • Describe all options and toggles enabled or changed,
  • Include any files or environmental changes,
  • Identify the expected and actual result at each stage,
  • Ensure any reasonably skilled user can follow and hit the same issue.

Expected Behavior

When using the Transcription functionality within Open-Webui, it is possible to record an unlimited amount of text in the Dialog which opens. This recording should be processed entirely and accurately be transcribed into the prompt window of Open-WebUI

Actual Behavior

I just recorded a ~4min dictation into OpenWebUI, using my Android Phone Xiaomi 12x with a Bluetooth Headset. During the recording i put the phone in my pocket, so lock-screen turns on at some point, but when unlocking, it suggests the recording had been continuing.

When stopping the recording and transcribing, only the first sentence of the recording was transcribed, the rest was omitted and lost.

Steps to Reproduce

  1. Start long recording on Android phone (phone has to activate lock screen in the meanwhile)
  2. unlock Phone
  3. stop Recording, wait for Transcription
  4. check results

Logs & Screenshots

I can not reproduce the behaviour on the desktop browser and dont have access to the logs on the phone

Additional Information

I assume this is a Android Phone related problem. i successfully did longer subscriptions on the desktop browser.
I think there should be an option to store the recording, in case the transcription fails.

Originally created by @tilllt on GitHub (Mar 27, 2026). Original GitHub issue: https://github.com/open-webui/open-webui/issues/23135 ### Check Existing Issues - [x] I have searched for any existing and/or related issues. - [x] I have searched for any existing and/or related discussions. - [x] I have also searched in the CLOSED issues AND CLOSED discussions and found no related items (your issue might already be addressed on the development branch!). - [x] I am using the latest version of Open WebUI. ### Installation Method Docker ### Open WebUI Version 0.8.11 ### Ollama Version (if applicable) 0.18.3 ### Operating System Debian ### Browser (if applicable) Android / Chrome 146.0.7680.164 (Play Store Version) ### Confirmation - [x] I have read and followed all instructions in `README.md`. - [x] I am using the latest version of **both** Open WebUI and Ollama. - [x] I have included the browser console logs. - [x] I have included the Docker container logs. - [x] I have **provided every relevant configuration, setting, and environment variable used in my setup.** - [x] I have clearly **listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup** (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc). - [x] I have documented **step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation**. My steps: - Start with the initial platform/version/OS and dependencies used, - Specify exact install/launch/configure commands, - List URLs visited, user input (incl. example values/emails/passwords if needed), - Describe all options and toggles enabled or changed, - Include any files or environmental changes, - Identify the expected and actual result at each stage, - Ensure any reasonably skilled user can follow and hit the same issue. ### Expected Behavior When using the Transcription functionality within Open-Webui, it is possible to record an unlimited amount of text in the Dialog which opens. This recording should be processed entirely and accurately be transcribed into the prompt window of Open-WebUI ### Actual Behavior I just recorded a ~4min dictation into OpenWebUI, using my Android Phone Xiaomi 12x with a Bluetooth Headset. During the recording i put the phone in my pocket, so lock-screen turns on at some point, but when unlocking, it suggests the recording had been continuing. When stopping the recording and transcribing, only the first sentence of the recording was transcribed, the rest was omitted and lost. ### Steps to Reproduce 1. Start long recording on Android phone (phone has to activate lock screen in the meanwhile) 2. unlock Phone 3. stop Recording, wait for Transcription 4. check results ### Logs & Screenshots I can not reproduce the behaviour on the desktop browser and dont have access to the logs on the phone ### Additional Information I assume this is a Android Phone related problem. i successfully did longer subscriptions on the desktop browser. I think there should be an option to store the recording, in case the transcription fails.
GiteaMirror added the bug label 2026-04-20 02:25:44 -05:00
Author
Owner

@Classic298 commented on GitHub (Mar 27, 2026):

might be a security topic, that background mic access to websites gets disabled when the phone is locked

<!-- gh-comment-id:4141115245 --> @Classic298 commented on GitHub (Mar 27, 2026): might be a security topic, that background mic access to websites gets disabled when the phone is locked
Author
Owner

@Classic298 commented on GitHub (Mar 27, 2026):

This isn't something Open WebUI can easily fix on the web side. Browsers enforce these restrictions at the OS/engine level for privacy and battery reasons, and there's no reliable workaround from a PWA or standard web app. A native Android app could request a foreground service with microphone permission to keep recording, but a browser tab simply can't do that.

<!-- gh-comment-id:4141120582 --> @Classic298 commented on GitHub (Mar 27, 2026): This isn't something Open WebUI can easily fix on the web side. Browsers enforce these restrictions at the OS/engine level for privacy and battery reasons, and there's no reliable workaround from a PWA or standard web app. A native Android app could request a foreground service with microphone permission to keep recording, but a browser tab simply can't do that.
Author
Owner

@tilllt commented on GitHub (Mar 27, 2026):

Just my opinion, but a feature that doesnt reliably work should not be offered on that respective platform, or at least cause a warning. If transcription doesnt work on mobile, the option should be hidden. So, i disagree, there is definitely something OpenWebUI can and should do.

<!-- gh-comment-id:4141141026 --> @tilllt commented on GitHub (Mar 27, 2026): Just my opinion, but a feature that doesnt reliably work should not be offered on that respective platform, or at least cause a warning. If transcription doesnt work on mobile, the option should be hidden. So, i disagree, there is definitely something OpenWebUI can and should do.
Author
Owner

@Classic298 commented on GitHub (Mar 27, 2026):

When you switch apps while recording a voice message, the recording will stop for messaging apps (e.g. Signal)

When you lock your phone while youtube is running in the browser, the playback will stop

When you lock your phone while your browser is trying to run python code (e.g. in a pydodide sandbox) for battery and security reasons, it is also not run when you move away!

In none of these cases, a warning exists. This is a natural limitation of the browser and the OS.
You can't have a background browser tab permanently access the microphone. That would be a security problem (i.e. a website opening antoher tab in the background that then permanently listens in on you without you ever noticing - even when your phone is locked) and it also drains your battery.

Transcription DOES WORK on mobile - but if your phone locks itself during voice recording on messaging apps, recording is also paused/stopped there. Open WebUI behaves the SAME WAY like Signal, WhatsApp etc.
And these don't display a warning. So why should Open WebUI?

<!-- gh-comment-id:4141289635 --> @Classic298 commented on GitHub (Mar 27, 2026): When you switch apps while recording a voice message, the recording will stop for messaging apps (e.g. Signal) When you lock your phone while youtube is running in the browser, the playback will stop When you lock your phone while your browser is trying to run python code (e.g. in a pydodide sandbox) for battery and security reasons, it is also not run when you move away! In none of these cases, a warning exists. This is a natural limitation of the browser and the OS. You can't have a background browser tab permanently access the microphone. That would be a security problem (i.e. a website opening antoher tab in the background that then permanently listens in on you without you ever noticing - even when your phone is locked) and it also drains your battery. <ins>Transcription DOES WORK on mobile - **but if your phone locks itself during voice recording on messaging apps, recording is also paused/stopped there.** Open WebUI behaves the SAME WAY like Signal, WhatsApp etc. And these don't display a warning. So why should Open WebUI?</ins>
Author
Owner

@tilllt commented on GitHub (Mar 27, 2026):

I am not switching apps or locking my phone intentionally, the phone locks itself after recording length X. I think there's a difference, isn't there?

<!-- gh-comment-id:4141314392 --> @tilllt commented on GitHub (Mar 27, 2026): I am not switching apps or locking my phone intentionally, the phone locks itself after recording length X. I think there's a difference, isn't there?
Author
Owner

@Classic298 commented on GitHub (Mar 27, 2026):

That said, this really is a browser-level constraint, not an Open WebUI bug. The browser revokes microphone access when the screen locks, we don't get a say in that. And as I mentioned, apps like Signal and WhatsApp behave the same way (recording stops when you lock).

Where your experience did differ is that it may have appeared like the recording was still going after you unlocked. That's a fair UX concern if the browser silently killed the mic stream. If you'd like to open a feature request for something like that (e.g., detecting a lost mic stream and STOPPING the recording outright instead - like Signal and WhatsApp do), that would be a constructive next step and I'd be happy to look at it. But reporting it is a bug when its not an Open WebUI bug is the wrong approach here

But as a bug, the current behavior is consistent with how browsers enforce mic access, so I'll keep this one closed.

<!-- gh-comment-id:4141316841 --> @Classic298 commented on GitHub (Mar 27, 2026): That said, this really is a browser-level constraint, not an Open WebUI bug. The browser revokes microphone access when the screen locks, we don't get a say in that. And as I mentioned, apps like Signal and WhatsApp behave the same way (recording stops when you lock). Where your experience did differ is that it may have appeared like the recording was still going after you unlocked. That's a fair UX concern if the browser silently killed the mic stream. If you'd like to open **a feature request** for something like that (e.g., detecting a lost mic stream and STOPPING the recording outright instead - like Signal and WhatsApp do), that would be a constructive next step and I'd be happy to look at it. But reporting it is a bug when its not an Open WebUI bug is the wrong approach here But as a bug, the current behavior is consistent with how browsers enforce mic access, so I'll keep this one closed.
Author
Owner

@Classic298 commented on GitHub (Mar 27, 2026):

I am not switching apps or locking my phone intentionally, the phone locks itself after recording length X. I think there's a difference, isn't it?

it doesn't matter who or what locked your phone.

Locking the phone kills mic access

If your phone accidentally locks while Signal is recording, same outcome.

<!-- gh-comment-id:4141326795 --> @Classic298 commented on GitHub (Mar 27, 2026): > I am not switching apps or locking my phone intentionally, the phone locks itself after recording length X. I think there's a difference, isn't it? it doesn't matter who or what locked your phone. Locking the phone kills mic access If your phone accidentally locks while Signal is recording, same outcome.
Author
Owner

@tilllt commented on GitHub (Mar 27, 2026):

In signal you have to continously hold the record button while recording, probably for the same reason. so recording a 4min text from which only the first sentence gets recorded: can't happen in signal. UI is one approach to handle "the problem". Saying "there is nothing that wen can do" is simply not true, you get that, right?

<!-- gh-comment-id:4141368232 --> @tilllt commented on GitHub (Mar 27, 2026): In signal you have to continously hold the record button while recording, probably for the same reason. so recording a 4min text from which only the first sentence gets recorded: can't happen in signal. UI is one approach to handle "the problem". Saying "there is nothing that wen can do" is simply not true, you get that, right?
Author
Owner

@Classic298 commented on GitHub (Mar 27, 2026):

@tilllt you can press and hold the record button - and pull it UP, which locks the recording in place.

You can then let go of your finger.

And i didn't say there is nothing open webui can do.
Read my response from above.

Where your experience did differ is that it may have appeared like the recording was still going after you unlocked. That's a fair UX concern if the browser silently killed the mic stream. If you'd like to open a feature request for something like that (e.g., detecting a lost mic stream and STOPPING the recording outright instead - like Signal and WhatsApp do)

But that would rather be a UI feature then, than a bug. Because it's not a bug.

<!-- gh-comment-id:4141415970 --> @Classic298 commented on GitHub (Mar 27, 2026): @tilllt you can press and hold the record button - and pull it UP, which locks the recording in place. You can then let go of your finger. And i didn't say there is nothing open webui can do. Read my response from above. > Where your experience did differ is that it may have appeared like the recording was still going after you unlocked. That's a fair UX concern if the browser silently killed the mic stream. If you'd like to open a feature request for something like that (e.g., detecting a lost mic stream and STOPPING the recording outright instead - like Signal and WhatsApp do) But that would rather be a UI feature then, than a bug. Because it's not a bug.
Author
Owner

@tilllt commented on GitHub (Mar 27, 2026):

For completeness sake, as per your signal comparison: signal doesn't let the phone go to sleep when recording.

<!-- gh-comment-id:4141459606 --> @tilllt commented on GitHub (Mar 27, 2026): For completeness sake, as per your signal comparison: signal doesn't let the phone go to sleep when recording.
Author
Owner

@Classic298 commented on GitHub (Mar 27, 2026):

My comparison with Signal was to illustrate that the behavior is the same when the phone is locked: the mic stream gets killed by the OS regardless of the app. That part is identical.

You're right that Signal can prevent the phone from going to sleep during recording, but Signal is a native app. Native apps CAN acquire wake locks and foreground service permissions to keep the screen on and the microphone active.

A website cannot do this. Browsers do not give web apps the ability to reliably prevent the device from sleeping or to keep the microphone open through a screen lock. This is an intentional security and privacy boundary enforced by the OS and browser engine, not something Open WebUI chose to ignore.

This remains not a bug in Open WebUI


Therefore my comparison with signal, as it has a recording feature. If the phone locks, your recording stops.
Same behaviour

Only difference is that Signal is an app and can try to prevent automatic locks, but accidental or user-triggered phone locks also will still cause the recording to stop

But a website can't even prevent the phone from locking in this scenario.


As I said, now for the third time - this is not a bug. For sure you can open a feature request to STOP recording, if this is technically possible that is, when Mic access is revoked due to phone locking, but other than that there's nothing Open WebUI can do

<!-- gh-comment-id:4141512935 --> @Classic298 commented on GitHub (Mar 27, 2026): My comparison with Signal was to illustrate that <ins>**the behavior is the same when the phone is locked**</ins>: the mic stream gets killed by the OS regardless of the app. That part is identical. You're right that Signal can prevent the phone from going to sleep during recording, but Signal is a native app. Native apps CAN acquire wake locks and foreground service permissions to keep the screen on and the microphone active. A website cannot do this. Browsers do not give web apps the ability to reliably prevent the device from sleeping or to keep the microphone open through a screen lock. This is an intentional security and privacy boundary enforced by the OS and browser engine, not something Open WebUI chose to ignore. This remains not a bug in Open WebUI --- Therefore my comparison with signal, as it has a recording feature. If the phone locks, your recording stops. Same behaviour Only difference is that Signal is an app and can try to prevent automatic locks, but accidental or user-triggered phone locks also will still cause the recording to stop But a website can't even prevent the phone from locking in this scenario. --- As I said, now for the third time - this is not a bug. For sure you can open a feature request to STOP recording, if this is technically possible that is, when Mic access is revoked due to phone locking, but other than that there's nothing Open WebUI can do
Author
Owner

@tilllt commented on GitHub (Mar 27, 2026):

Fyi

https://developer.mozilla.org/en-US/docs/Web/API/Screen_Wake_Lock_API

<!-- gh-comment-id:4141557842 --> @tilllt commented on GitHub (Mar 27, 2026): Fyi https://developer.mozilla.org/en-US/docs/Web/API/Screen_Wake_Lock_API
Author
Owner

@Classic298 commented on GitHub (Mar 27, 2026):

Fair point on the Wake Lock API I wasn't aware of this API. Navigator.wakeLock.request('screen') could prevent auto-lock during recording and is supported across all major mobile browsers at this point. Wouldn't help with manual locks, but would cover your specific scenario.

If you want to open a feature request covering wake lock acquisition during recording + mic stream loss detection, go for it.

<!-- gh-comment-id:4141591780 --> @Classic298 commented on GitHub (Mar 27, 2026): Fair point on the Wake Lock API I wasn't aware of this API. Navigator.wakeLock.request('screen') could prevent auto-lock during recording and is supported across all major mobile browsers at this point. Wouldn't help with manual locks, but would cover your specific scenario. If you want to open a feature request covering wake lock acquisition during recording + mic stream loss detection, go for it.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#19892