Page 3 of 5 12 3 45
Reply
Thread Tools
ndi's Avatar
ndi is offline ndi
2010-01-13 , 19:21
Posts: 2,050 | Thanked: 1,425 times | Joined on Dec 2009 @ Bucharest
#21
Interesting, skipped that.

Also, what version of PC Suite?
__________________
N900 dead and Nokia no longer replaces them. Thanks for all the fish.

Keep the forums clean: use "Thanks" button instead of the thank you post.
 
kesh is offline kesh
2010-01-13 , 19:44
Posts: 4 | Thanked: 0 times | Joined on Nov 2009 @ DE
#22
The last one... 7.1.40.1
 
ikerrg is offline ikerrg
2010-01-14 , 16:28
Posts: 181 | Thanked: 82 times | Joined on Jan 2010
#23
The problem has not been solved in firmware 2.2009.51-1, at least in my device. The class is still 0x580000. Maybe I need to reflash, but I'm afraid PCSuite will ruin it again when I connect the device.
 
ikerrg is offline ikerrg
2010-01-14 , 17:56
Posts: 181 | Thanked: 82 times | Joined on Jan 2010
#24
Finally fixed!!! See the two latest posts in https://bugs.maemo.org/show_bug.cgi?id=7849

Thank to all of you for your collaboration.

Cheers!
 
filbert is offline filbert
2010-01-14 , 22:08
Posts: 55 | Thanked: 14 times | Joined on Mar 2009 @ UK
#25
Originally Posted by Alan_Peery View Post
The fact that the N900 failed to identify itself as a "phone" isn't the problem, as its capabilities exceed that of a phone. I *like* my N900 showing up as a "computer" in Windows 7. The problem lies in PC Suite, and it expecting the device on the other end to always name itself as a "phone", rather than supporting a collection of bluetooth functions. .
It is a problem for me as it stops TomTom connecting to it and using it for handsfree (and possibly other features). I issued the hci command to change the class and it immediately saw it as a phone and connected. A reboot has changed the class back to 0x5a0100 .

(I am on the new firmware update PR1.1)

Rgrds

Peter
 
ikerrg is offline ikerrg
2010-01-15 , 07:42
Posts: 181 | Thanked: 82 times | Joined on Jan 2010
#26
Did you try the following commands in console root mode, as indicated in the bug report?

stop bluetoothd
rm /var/lib/bluetooth/*/config
start bluetoothd
 
filbert is offline filbert
2010-01-21 , 21:56
Posts: 55 | Thanked: 14 times | Joined on Mar 2009 @ UK
#27
Originally Posted by ikerrg View Post
Did you try the following commands in console root mode, as indicated in the bug report?

stop bluetoothd
rm /var/lib/bluetooth/*/config
start bluetoothd
Yes, I have done that. I found that the start command doesn't seem to fully start bluetooth. I get the following:

Nokia-N900-42-11:~# hciconfig hci0 class
Can't read class of device on hci0: Connection timed out (110)

If I run start bluetoothd again, it says

Nokia-N900-42-11:~# start bluetoothd
start: Job not changed: bluetoothd

If I start bluetooth from the desktop, I still get the wrong class:
hci0: Type: UART
BD Address: 00:BD:3A:AC:A0:6C ACL MTU: 1017:4 SCO MTU: 64:1
Class: 0x5a0100
Service Classes: Networking, Capturing, Object Transfer, Telephony
Device Class: Computer, Uncategorized

By the way, the prompt is odd and the output from uname is:

Nokia-N900-42-11:~# uname -a
Linux Nokia-N900-42-11 2.6.28-omap1 #1 PREEMPT Thu Dec 17 09:40:52 EET 2009 armv7l unknown

which implies the old firware version but I *have* updated and the about screen says "2.2009.51-1.203.2" - is there a definitive way of getting the firmware version from the command line?

Rgrds

Peter
Last edited by filbert; 2010-01-21 at 22:07.
 
fpp's Avatar
fpp is offline fpp
2010-02-08 , 11:51
Posts: 2,853 | Thanked: 968 times | Joined on Nov 2005
#28
Thanks Heavens for this thread ! My N900, which had been happily working as a "Phone" since december, suddenly disappeared from PC Suite, although my PC's BT stack still saw it as a "Desktop".

Using the hciconfig command got it back into PC Suite and the Calendar sync running again (until next time :-).

If I recall correctly, it was connecting *to* the PC *from* the N900 (to send a picture from the image viewer via BT) that triggered the change. I must have picked up something from extras* that messed with the BT device classs at some point...
__________________
maemo blog
 
ofels is offline ofels
2010-02-11 , 09:19
Posts: 138 | Thanked: 103 times | Joined on Jan 2010 @ Southern Germany
#29
Originally Posted by fpp View Post
If I recall correctly, it was connecting *to* the PC *from* the N900 (to send a picture from the image viewer via BT) that triggered the change. I must have picked up something from extras* that messed with the BT device classs at some point...
The question is: What could that be? I am suffering from the same problem and it is a little bit tedious to manually change the class after reboot.
I suspect it could be from the FMRadio applications and widgets. The bluetooth module is the one providing fm radio support so it might be located in that area. At least this is the only thing related to bluetooth which I have installed as far as I can see.
Last edited by ofels; 2010-02-11 at 09:25.
 
fpp's Avatar
fpp is offline fpp
2010-02-11 , 10:51
Posts: 2,853 | Thanked: 968 times | Joined on Nov 2005
#30
I don't have (and never had) the FMRadio applications and widgets installed. The only thing I can think of that is BT-related and I got from extras-* is the Bluetooh DUN package for tethering the N900.
 

The Following User Says Thank You to fpp For This Useful Post:
Reply
Page 3 of 5 12 3 45

« Previous Thread | Next Thread »
Thread Tools

 
Forum Jump


All times are GMT. The time now is 18:05.

Contact Us - Home - Archive - Top