# Bluetooth in-ear start of speech chopped off

**URL:** <https://forum.kurviger.com/t/bluetooth-inear-sprachanfang-abgehackt/27631>\
**Category:** Navigation\
**Created:** [September 28, 2026, 8:21am UTC](https://forum.kurviger.com/t/bluetooth-inear-sprachanfang-abgehackt/27631 "2026-09-28T08:21:59Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ekmi](https://forum.kurviger.com/letter_avatar_proxy/v4/letter/e/b9bd4f/32.png) [@Ekmi](https://forum.kurviger.com/u/Ekmi)\
**Post date:** [September 28, 2026, 8:21am UTC](https://forum.kurviger.com/t/bluetooth-inear-sprachanfang-abgehackt/27631/1 "2026-09-28T08:21:59Z")

</div>

Hello,  
this topic has already been discussed in the thread [Bluetooth earbud - #15 by fstelt](https://forum.kurviger.com/t/bluetooth-earbud/5618/15), but there doesn’t seem to be a real solution yet.  
I navigate exclusively via voice guidance, and this works very well until the Bluetooth connection goes into power-saving mode. When the instruction „turn left“ is then spoken, you only hear „turn“, with „left“ getting swallowed because of the Bluetooth connection switching over.  
The only workaround that works for me is playing a continuous 10 Hz tone in an endless loop via VLC. Nothing else works for me. Then I can hear „left“ again.  
My request to the developers would be to implement an option for a start delay in the audio output. The delay also varies slightly depending on the hardware used, so a flexible setting in milliseconds would be a great solution.

---

<div class="post-metadata">

**Author:** ![Toffel](https://forum.kurviger.com/letter_avatar_proxy/v4/letter/t/9dc877/32.png) [@Toffel](https://forum.kurviger.com/u/Toffel)\
**Post date:** [September 28, 2026, 12:18pm UTC](https://forum.kurviger.com/t/bluetooth-inear-sprachanfang-abgehackt/27631/2 "2026-09-28T12:18:26Z")

</div>

There is a “solution” here.

> [@Headset verschluckt bei Ansagen die ersten Silben](https://forum.kurviger.com/t/headset-verschluckt-bei-ansagen-die-ersten-silben/11131/20?u=toffel):
>
> Ja, gehe ich mit. Es gibt ja viele Geräte, die nicht unedingt “standardmäßig” eingerichtet sind, und dann wird der support schwer. Ich möchte hier ergänzen, dass ich mittlerweile ein weiteres in-ear-bud erworben habe, welches den letzten oder vorletzten Bluetooth-Standard erfüllt. Und tatsächlich werden bei diesem bud keine Silben der TTS-Ansagen merh abgeschnitten, da der bud deutlich schneller aus dem “Ruhemodus” (zwischen längeren Ansagepausen) aufwacht (\< 100 ms, laut BT-Spezifikationsinfo)…

---

<div class="post-metadata">

**Author:** ![Ekmi](https://forum.kurviger.com/letter_avatar_proxy/v4/letter/e/b9bd4f/32.png) [@Ekmi](https://forum.kurviger.com/u/Ekmi)\
**Post date:** [September 28, 2026, 1:08pm UTC](https://forum.kurviger.com/t/bluetooth-inear-sprachanfang-abgehackt/27631/3 "2026-09-28T13:08:34Z")

</div>

Addendum: I’m using Kurviger version 3.6.6 on Android 13. I’ve already tested 3 different in-ears. With the first in-ear (which is broken), it still worked quite well. With the two newer ones (bought this year), the problem is present.

---

<div class="post-metadata">

**Author:** ![t00thl355](https://forum.kurviger.com/user_avatar/forum.kurviger.com/t00thl355/32/27045_2.png) [@t00thl355](https://forum.kurviger.com/u/t00thl355)\
**Post date:** [September 28, 2026, 1:16pm UTC](https://forum.kurviger.com/t/bluetooth-inear-sprachanfang-abgehackt/27631/4 "2026-09-28T13:16:15Z")

</div>

“In-ear” is a general term for me…

Which brand/model is it?

Which phone is it?

Maybe someone has experience with similar devices.

Can you share a route where you can reproduce the error in simulation mode?

Then we could try to recreate the issue and the developers could test different solutions.

---

<div class="post-metadata">

**Author:** ![zaphod\_42](https://forum.kurviger.com/user_avatar/forum.kurviger.com/zaphod_42/32/499_2.png) [@zaphod\_42](https://forum.kurviger.com/u/zaphod_42)\
**Post date:** [September 28, 2026, 1:22pm UTC](https://forum.kurviger.com/t/bluetooth-inear-sprachanfang-abgehackt/27631/5 "2026-09-28T13:22:50Z")

</div>

It’s very simple — as the OP already mentioned:

 ![20260928_103141210](https://forum.kurviger.com/uploads/default/original/3X/6/9/694e2d12b677174546e56f1fa2ebe8b8206a2681.jpeg)  
(Screenshot from K1)

---

<div class="post-metadata">

**Author:** ![Ekmi](https://forum.kurviger.com/letter_avatar_proxy/v4/letter/e/b9bd4f/32.png) [@Ekmi](https://forum.kurviger.com/u/Ekmi)\
**Post date:** [September 28, 2026, 1:27pm UTC](https://forum.kurviger.com/t/bluetooth-inear-sprachanfang-abgehackt/27631/6 "2026-09-28T13:27:39Z")

</div>

sorry, apparently I don’t know the app well enough. When you write about K1 and K3, do you mean the Kuviger versions? I couldn’t find anything in the menu like the one described here.

 ![image](https://forum.kurviger.com/uploads/default/original/3X/4/0/400809305180ecdb4ea2e77e39268e792d347f46.jpeg)

---

<div class="post-metadata">

**Author:** ![t00thl355](https://forum.kurviger.com/user_avatar/forum.kurviger.com/t00thl355/32/27045_2.png) [@t00thl355](https://forum.kurviger.com/u/t00thl355)\
**Post date:** [September 28, 2026, 4:11pm UTC](https://forum.kurviger.com/t/bluetooth-inear-sprachanfang-abgehackt/27631/7 "2026-09-28T16:11:41Z")

</div>

> [@Ekmi](#):
>
> When you write about K1 and K3, do you mean the Kurviger versions?

Correct. The numbers “1” and “3” refer to the first digit in the version number.  
Anything with version v3.x.x (currently v3.6.6) is informally referred to on the forum as “K3”.

“K3” is the app as you get it in the Play Store today. K3 is not a direct continuation of K1, which is why some features from K1 are no longer available in K3.

Kurviger has discontinued the further development of “K1” and the version is not available to new users.

---

<div class="post-metadata">

**Author:** ![Ekmi](https://forum.kurviger.com/letter_avatar_proxy/v4/letter/e/b9bd4f/32.png) [@Ekmi](https://forum.kurviger.com/u/Ekmi)\
**Post date:** [September 28, 2026, 4:22pm UTC](https://forum.kurviger.com/t/bluetooth-inear-sprachanfang-abgehackt/27631/8 "2026-09-28T16:22:49Z")

</div>

ok, thanks. That means it would be great if the developers of Kurviger could also provide the “Prepare audio connection” feature in K3. Then we could enter a delay time again and the announcement would be heard in full.  
@Developers: What do you think about this? Will you implement it? Thanks in advance.

---

<div class="post-metadata">

**Author:** ![t00thl355](https://forum.kurviger.com/user_avatar/forum.kurviger.com/t00thl355/32/27045_2.png) [@t00thl355](https://forum.kurviger.com/u/t00thl355)\
**Post date:** [September 28, 2026, 6:22pm UTC](https://forum.kurviger.com/t/bluetooth-inear-sprachanfang-abgehackt/27631/9 "2026-09-28T18:22:33Z")

</div>

I don’t usually have this problem since I generally have music playing in the background.

With my headphones, Bluetooth cuts off the very first sound:

„\*\*os geht`s“, „\*usfahrt 1 nehmen“, „\*\*inks abbiegen“…

A bit of a delay would actually be nice, although other navigation apps have the same issue for me…
