Active Topics
-
[HOWTO] Comprehensive Firmware Flashing Guide for N9 (1,580)
to Nokia N9 / N950 by aspergerguy - 1 hr, 31 mins ago -
Nokia N9-00 Prototype Build S1.12 (RM-680 codename "Dali") (250)
to Nokia N9 / N950 by en0s - 2 days, 21 hrs ago -
[Announce] Maebble - Pebble support for Maemo (118)
to Applications by glo-worm - 3 days, 10 hrs ago -
Possible to flash Leste to eMMC? (6)
to Maemo 7 / Leste by Eri - 4 days ago - more...
Jqwon |
2012-11-30
, 22:44
|
|
Posts: 6 |
Thanked: 1 time |
Joined on Mar 2011
|
#1
|
Hi...been having problems with my Bluetooth...it does not detect active Bluetooth devices and it's not detectable...I've searched the forum and tried every solution suggested I.e deleting the Bluetooth folder in var/lib/bluetooth...it still won't come on...any suggestions...Will appreciate your help..
|
|
2012-12-01
, 00:39
|
|
Posts: 198 |
Thanked: 76 times |
Joined on Mar 2010
|
#2
|
rule of thumb: the more effort it takes to get at least an idea how to solve, the more trivial the problem is ...
therefore: did you enable BT and set it to "visible"?
edit:
what do you get for
(make sure to anonymize the MAC/BD Address before posting the output! that's the XX:XX:XX:XX:XX:XX string)
Last edited by arne.anka; 2012-12-01 at 00:45.
therefore: did you enable BT and set it to "visible"?
edit:
what do you get for
Code:
ps ax | grep bluetoothd
Code:
hciconfig
Code:
hcitool dev
(make sure to anonymize the MAC/BD Address before posting the output! that's the XX:XX:XX:XX:XX:XX string)
Last edited by arne.anka; 2012-12-01 at 00:45.
| The Following 2 Users Say Thank You to arne.anka For This Useful Post: | ||
|
|
2012-12-01
, 06:31
|
|
Posts: 6 |
Thanked: 1 time |
Joined on Mar 2011
|
#3
|
yes I switched on the visibility.
For the first command it gives me
/home/user # ps ax | grep bluetoohd
2178 root 2088 S grep bluetoohd
the second command gives me
/home/user # hciconfig
hci0: Type: UART
BD Address: XX:XX:XX:XX:XX:XX ACL MTU: 1017:4 SCO MTU: 64:1
DOWN
RX bytes:4054 acl:0 sco:0 events:105 errors:0
TX bytes:31592 acl:0 sco:0 commands:102 errors:0
and the third command gives me
/home/user # hcitool dev
Devices:
For the first command it gives me
/home/user # ps ax | grep bluetoohd
2178 root 2088 S grep bluetoohd
the second command gives me
/home/user # hciconfig
hci0: Type: UART
BD Address: XX:XX:XX:XX:XX:XX ACL MTU: 1017:4 SCO MTU: 64:1
DOWN
RX bytes:4054 acl:0 sco:0 events:105 errors:0
TX bytes:31592 acl:0 sco:0 commands:102 errors:0
and the third command gives me
/home/user # hcitool dev
Devices:
| The Following User Says Thank You to Jqwon For This Useful Post: | ||
|
|
2012-12-01
, 11:17
|
|
Posts: 560 |
Thanked: 422 times |
Joined on Mar 2011
|
#4
|
OK. so, next step is to ensure the partner devices are working. Do you have another phone or something that claims it can see your N900? It's much eaier trying to pair something else with a screen (for feedback), which KBs and headsets etc. don't have.
|
|
2012-12-01
, 12:04
|
|
Posts: 6 |
Thanked: 1 time |
Joined on Mar 2011
|
#5
|
i have a galaxy tab and blackberry...both are not recognising the device.Visibility is set to on and when searching on the galaxy tab its able to recognise the blackberry.The N900 isnt able to recognise any devices too.
|
|
2012-12-01
, 12:07
|
|
Posts: 33 |
Thanked: 22 times |
Joined on May 2012
@ ja_JP.UTF-8
|
#6
|
try
and then
check if your device "hci0" were UP or not.
then copy&paste&post messages to this thread.
I often use these commands when powering on my BT manually.
they're written on other maemo talk threads.it's worth to try them.
then
hciconfig hci0 up
hciconfig hci0
dmesg | tail
I often use these commands when powering on my BT manually.
they're written on other maemo talk threads.it's worth to try them.
modprobe hci_h4p;
echo "00:11:22:33:44:55" > /sys/devices/platform/hci_h4p/bdaddr;
modprobe -r hci_h4p;
modprobe hci_h4p;
bluetoothd;
hciconfig hci0 up;
hcitool scan
|
|
2012-12-01
, 15:36
|
|
Posts: 6 |
Thanked: 1 time |
Joined on Mar 2011
|
#7
|
for the first command it switches on the bluetooth
for the second command i recieve
home/user # hciconfig hci0
hci0: Type: UART
BD Address: XX:XX:XX:XX:XX:XX ACL MTU: 1017:4 SCO MTU: 64:1
UP RUNNING PSCAN ISCAN
RX bytes:9844 acl:0 sco:0 events:253 errors:0
TX bytes:75030 acl:0 sco:0 commands:246 errors:0
and for the final command
home/user # dmesg |tail
[62649.183044] wl1251: 151 tx blocks at 0x3b788, 35 rx blocks at 0x3a780
[62649.198699] wl1251: firmware booted (Rev 4.0.4.3.7)
[62649.316406] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[62650.035827] wl1251: down
[62775.589263] slide (GPIO 71) is now closed
[62786.878234] slide (GPIO 71) is now open
[62808.745574] slide (GPIO 71) is now closed
[62808.995513] cam_focus (GPIO 68) is now active
[62809.011108] cam_focus (GPIO 68) is now inactive
[62817.182922] slide (GPIO 71) is now open
for the other process...
when i each the command modprobe -r hci_h4p i recieve
home/user # modprobe -r hci_h4P
FATAL: Module hci_h4P not found.
neither does it recognise other devices nor is it recognised by other devices.
Last edited by Jqwon; 2012-12-01 at 15:41.
for the second command i recieve
home/user # hciconfig hci0
hci0: Type: UART
BD Address: XX:XX:XX:XX:XX:XX ACL MTU: 1017:4 SCO MTU: 64:1
UP RUNNING PSCAN ISCAN
RX bytes:9844 acl:0 sco:0 events:253 errors:0
TX bytes:75030 acl:0 sco:0 commands:246 errors:0
and for the final command
home/user # dmesg |tail
[62649.183044] wl1251: 151 tx blocks at 0x3b788, 35 rx blocks at 0x3a780
[62649.198699] wl1251: firmware booted (Rev 4.0.4.3.7)
[62649.316406] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[62650.035827] wl1251: down
[62775.589263] slide (GPIO 71) is now closed
[62786.878234] slide (GPIO 71) is now open
[62808.745574] slide (GPIO 71) is now closed
[62808.995513] cam_focus (GPIO 68) is now active
[62809.011108] cam_focus (GPIO 68) is now inactive
[62817.182922] slide (GPIO 71) is now open
for the other process...
when i each the command modprobe -r hci_h4p i recieve
home/user # modprobe -r hci_h4P
FATAL: Module hci_h4P not found.
neither does it recognise other devices nor is it recognised by other devices.
Last edited by Jqwon; 2012-12-01 at 15:41.
|
|
2012-12-01
, 15:59
|
|
Posts: 198 |
Thanked: 76 times |
Joined on Mar 2010
|
#8
|
Originally Posted by Jqwon
typo -- must be "bluetoothd"
/home/user # ps ax | grep bluetoohd
2178 root 2088 S grep bluetoohd
you should see at least two lines of output -- one of bluetoothd itself and the second of your request.
something like this:
Code:
Nokia-N900-51-1:~# ps ax | grep bluetoothd 940 root 3408 S /usr/sbin/bluetoothd -n 3357 root 4064 S grep bluetoothd Nokia-N900-51-1:~#
Originally Posted by Jqwon
adapter not up
/home/user # hcitool dev
Devices:
Last edited by arne.anka; 2012-12-01 at 16:02.
|
|
2012-12-01
, 16:06
|
|
Posts: 198 |
Thanked: 76 times |
Joined on Mar 2010
|
#9
|
Originally Posted by Jqwon
what do you get now for
for the first command it switches on the bluetooth
Code:
hcitool dev
when i each the command modprobe -r hci_h4p i recieve
Originally Posted by Jqwon
case-sensitive: ist's "hci_h4p".
home/user # modprobe -r hci_h4P
FATAL: Module hci_h4P not found.
what do you get for
Code:
lsmod | grep hci
|
|
2012-12-01
, 16:12
|
|
Posts: 198 |
Thanked: 76 times |
Joined on Mar 2010
|
#10
|
btw: enabling bt shows here in dmegs:
hci_h4p information:
please, check if the module exists on your device and the firmware file:
Code:
[58807.462219] hci_h4p hci_h4p: firmware: requesting bcmfw.bin
Code:
Nokia-N900-51-1:~# modinfo hci_h4p filename: /lib/modules/2.6.28-omap1/hci_h4p.ko author: Ville Tervo license: GPL description: h4 driver with nokia extensions srcversion: AE9629CC2B10806108936C0 depends: bluetooth vermagic: 2.6.28-omap1 preempt mod_unload modversions ARMv7 Nokia-N900-51-1:~# dir /lib/modules/2.6.28-omap1/hci_h4p.ko -rw-r--r-- 1 root root 24388 2010-08-06 10:53 /lib/modules/2.6.28-omap1/hci_h4p.ko Nokia-N900-51-1:~#
Code:
Nokia-N900-51-1:~# dir /lib/firmware/bcmfw.bin -rw-r--r-- 1 root root 9560 2009-10-22 14:26 /lib/firmware/bcmfw.bin