Bug 8563 – Device ID reset to "BCM2048B0 Initialization Configuration"

Bug 8563 - (int-152120) Device ID reset to "BCM2048B0 Initialization Configuration"

(int-152120)
Summary:	Device ID reset to "BCM2048B0 Initialization Configuration"

Status:	NEW

Product:	Connectivity
Component:	Bluetooth
Version:	5.0/(2.2009.51-1)
Platform:	N900 Maemo

Importance:	Unspecified normal with 3 votes (vote)
Target Milestone:	---
Assigned To:	unassigned
QA Contact:	bluetooth-bugs

URL:	http://talk.maemo.org/showthread.php?...
Keywords:

Depends on:
Blocks:	9895
	Show dependency tree

Reported:	2010-01-27 02:52 UTC by timeless
Modified:	2011-04-14 15:20 UTC (History)
CC List:	6 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note

You need to log in before you can comment on or make changes to this bug.

Description timeless (reporter) 2010-01-27 02:52:27 UTC

SOFTWARE VERSION:
after 51-1

EXACT STEPS LEADING TO PROBLEM: 
1. unknown. for me bluetooth failed to work a few days ago
2. when bluetooth stopped working the name became empty and i couldn't change
it or turn it on.
3. my cellular phone stopped working sometime last night
4. my n900 ran out of power
5. when i turned it back on, the bluetooth item listed this id (i have
pictures)

EXPECTED OUTCOME:
my bluetooth device id was 'Green', it should not have changed

ACTUAL OUTCOME:
it was reset to "BCM2048B0 Initialization Configuration"

REPRODUCIBILITY:
twice, reported on tmo on dec 10, 2009 by "gidyn". My instance is the second

Comment 1 Lucas Maneos 2010-01-27 17:40:54 UTC

Make that 3, including <http://talk.maemo.org/showthread.php?t=38534>.  The USB
unplugging mentioned there may or may not be relevant.

Comment 2 Bill Wayson 2010-02-23 00:44:15 UTC

I've just discovered I had a similar issue with my N900.  I used the File
Manager today to navigate to a file, and when I did, the internal memory was
named "BCM2048B0 Initialization Configuration", where it had been "Nokia N900"
the last time I used File Manager.  I connected the N900, when it was powered
off, to a Windows XP computer via the USB cable.  In Windows, the "drive" was
still named "Nokia N900".  After reading this bug report, I checked the
Bluetooth configuration, and it too was named "BCM2048B0 Initialization
Configuration".  I did run a terminal command "tracker-processes -r" after
looking at Lucas Maneos' link, but it had no effect on this names.  I changed
the Bluetooth name back to "Nokia N900", and this appears to have worked.  Both
the Bluetooth and File Manager internal memory are now "Nokia N900".  I don't
know exactly when this happened nor how to reproduce it.  I am on the
3.2010.02-8.002 version of Maemo.

Comment 3 Nathan 2010-03-01 18:48:02 UTC

I am also affected by this. I do not regularly use bluetooth (haven't had it on
for weeks) but a while back I did change the name to "Nates N900" which also
renamed the drive as expected. A few days ago it got renamed to the same string
as above. I changed it back using the bluetooth settings dialog, and the
filemanager shows the change. However when I upload a file in the microb
browser the file choosr which pops up still shows the "BCM2048B9..." string.
Nothing else seems to be impacted, I can still upload files fine in the browser
and from what I've seen everything behaves as it should.

Comment 4 Seb 2011-04-14 15:20:24 UTC

I just encountered this bug too, no idea the steps that led up to it. Have been
having other problems too so it's a bit hard for me to recreate...