maemo.org Bugzilla – Bug 7843
BH-103 - Annoying Beeps when calling or receiving a phone call or SMS
Last modified: 2010-03-15 20:52:50 UTC
You need to
before you can comment on or make changes to this bug.
(Settings > General > About product)
EXACT STEPS LEADING TO PROBLEM:
(Explain in detail what you do (e.g. tap on OK) and what you see (e.g. message
Connection Failed appears))
1. Connect the Bluetooth headset
2. Try making a phone call
3. Annoying beeps (4-5 beeps) are heard
4. Disconnect the call
5. Make a call to this device from another mobile
6. Not that when the ringing starts, the beeps are heard again.
7. Pick up the call, notice that when the call is picked up, the 4-5 beeps are
The beeps should be 1-2 only and not 4-5 beeps, which is very annoying and
takes more time too.
The beeps are heard at specified time and the number of beeps are 4-5 beeps
(always, less than 1/10, 5/10, 9/10)
EXTRA SOFTWARE INSTALLED:
Some softwares from Maemo-Extras, nothing pertaining to bluetooth. Happens even
when no 3rd party software is installed.
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US)
AppleWebKit/532.0 (KHTML, like Gecko) Chrome/220.127.116.11 Safari/532.0
Also reproducible on BH-604 stereo headset
Thanks for reporting this.
Does this happen again / is this still an issue in version 2.2009.51-1?
verified to be happening on 2.2009.51-1
also the beeps happen when:
1. when i start dialing a call
2. and again when the call is picked up at the other end... eventually because
of the beeps, i end up talking only after 4-5 seconds after the call is
this issue is making bluetooth unusable as it is way to annoying...
This was most probably fixed in package
which is part of the internal build version
(Note: 2009/2010 is the year, and the number after is the week.)
It is definitely not reproducable in the internal version 2010.04-4 with the BT
stereo headset BH-103.
A future public update released with the year/week later than this internal
build version will include the fix. (This is not always already the next public
Please verify that this new version fixes the bug by marking this bug report as
VERIFIED after the public update has been released and if you have some time.
To answer popular followup questions:
* Nokia does not announce release dates of public updates in advance.
* There is currently no access to these internal, non-public build versions.
A Brainstorm proposal to change this exists at
*** Bug 8319 has been marked as a duplicate of this bug. ***
Created an attachment (id=2152) [details]
Logging made with hcidump
I jinxed it again - bug got so scared when I made dumpfiles it became fixed.
Uploading the log files anyway, just in case they will be needed sometime.
Created an attachment (id=2153) [details]
Logging made with hcidump
Tomas: Thanks for the logs, but as written this is already fixed internally...
@ Andre Klapper:
Thanks for confirming that it is fixed internally and may be available in next
However, can you confirm what the new behavior after it being fixed is? Is it 1
or 2 beeps, no beeps at all, or how?
verified to be not fixed on 3.2010.02-8
Still the same issue is seen, specially when receiving a call !
Please read comment 4 again:
"This is not always already the next public update."
Also, please never set the Priority. Thanks.
Setting explicit PR1.2 milestone (so it's clearer in which public release the
fix will be available to users).
Sorry for the bugmail noise (you can filter on this message).