Bluetooth On The Sl-3000?

[tumnus]

Have a look at /etc/apm.d/bluetooth . That is the script that does the business. I was told that the Socket Rev G card can be brought back simply by running 'cardctl resume'

[gerenb]

Have a look at /etc/apm.d/bluetooth . That is the script that does the business. I was told that the Socket Rev G card can be brought back simply by running 'cardctl resume'
[div align=\"right\"][a href=\"index.php?act=findpost&pid=68877\"][{POST_SNAPBACK}][/a][/div]

I modified the bluetooth script with the following line at the end of the "resume" section:

/etc/rc.d/init.d/bluetooth restart

The card now works after a resume - sometimes brute force is the way to go.  

Thanks for your help!

[Bombur]

Have a look at /etc/apm.d/bluetooth . That is the script that does the business. I was told that the Socket Rev G card can be brought back simply by running 'cardctl resume'
[div align=\"right\"][a href=\"index.php?act=findpost&pid=68877\"][{POST_SNAPBACK}][/a][/div]

I modified the bluetooth script with the following line at the end of the "resume" section:

/etc/rc.d/init.d/bluetooth restart

The card now works after a resume - sometimes brute force is the way to go.  

Thanks for your help!
[div align=\"right\"][a href=\"index.php?act=findpost&pid=68906\"][{POST_SNAPBACK}][/a][/div]

Oi!  That's done it for me as well.

J.

[gerenb]

None of the overclocking kernels appear to work with my Socket rev. H. Upon resume, my Zaurus reboots. The problem disappears when I switch back to the stock kernel.

Are any overclocking kernels available that do not have this problem?

[iamasmith]

It may be worth mentioning the suspend-resume architecture IPK renames /usr/local/bin/apm to /usr/local/bin/apm.rom then creates it's own as a script.

If you are having problems with your Z not suspending then this is the issue. When you hit the power button the command 'apm -s' is run as the Zaurus user which doesn't have rights to suspend the box. To fix you must edit /usr/local/bin/apm and prefix the commands with 'sudo' i.e.

Code: [Select]

#!/bin/bash

# Replacement apm script that eventually
# calls the real apm with all arguments
# passed to it.
# Before that, however, it calls a script
# that will run all suspend commands in
# /etc/apm.d/suspend.d and then kicks off
# a resume script that carries on running
# when we resume and runs all commands in
# /etc/apm.d/resume.d

if [ "$1" = "--suspend" -o "$1" = "-s" ]; then
   sudo /usr/local/bin/susp.sh
   sudo /usr/local/bin/resume &
fi

sudo /usr/local/bin/apm.rom $@

the IPK that is being mentioned on this thread doesn't have this.

[tumnus]

Actually I think you must have got the pre SL-5500 3.1 ROM version of the ipk from ELSI where everything ran as root. If you go to the home page of the susp-resume ipk, you'll find the version that has had the sudo lines in it since the 3.10 ROM came out.

I didn't realise ELSI had only grabbed the old version of the ipk. I have added a link to the current ipk. Sorry about that.

[byland3]

Would it be possible for someone to make an overall summary of setup instructions for this topic? Eg. SL-C3000 + Socket BT card + Nokia 6630 (or other Symbian series 60 model) phone?

I have tried all of the tricks and tips on this and other sites, but I still cannot get it to work. Previously, I had an SL-C760 + Nokia 7600 that paired and connected successfully with the Socket BT card, but I am utterly confused with the new Zaurus.

Current ZUG Howto document ( under SL-Cxxx) on this topic is outdated....

Thanks in advance.

[byland3]

Would it be possible for someone to make an overall summary of setup instructions for this topic? Eg. SL-C3000 + Socket BT card + Nokia 6630 (or other Symbian series 60 model) phone?
------------------------------------

Here is a first try at the proper sequence of actions. But I failed after trying this, so additional steps are probably required.... Please feel free to add on you own knowledge. Please!!!
----

1) download--> bluez_zaurus_2.12_2.4.20_alpha4_arm.ipk ( 211.87k )
[https://www.oesf.org/forums/index.php?act=Attach&type=post&id=279]
- Remember to rename the download and change some of those underscores (_) to bluez-zaurus_2.12-2.4.20-alpha4_arm.ipk


2) alpha4 (plus additional packages) installation:
- Removed the csr package and the alpha2 package.
- Installed alpha4 package.
-Install additional packages (not part of alpha4):
   -Install bluez libs??
   -Install bluez utils??
   -Install qtopia-bluetoothnetworkapplet (*Java installation required first)
-reboot.

3) Settings in Zaurus SL-C3000
-eject and reinsert BT card
#cardctl ident (check that card is recognized by zaurus)
#hciconfig (get BT mac address of zaurus side--> xx:xx:xx:xx:xx:xx)
    not necessary --> #sdptool browse (scan to find mac id)
# hcitool scan (scan for BT mac address of phone side--> xx:xx:xx:xx:xx:xx)
   -Service name : dial-up network ==> channel 1.


- re-entered settings in /etc/bluetooth/rfcomm.conf
- initial insertion of the Socket rev H card did not register with hcitool dev
- tried /etc/rc.d/init.d/bluetooth start --> didn't work either
- re-inserted the card. hcitool dev finally found the card.


vi /home/zaurus/Applications/Network/modules/IRDA.conf
find IRDA code --> IRDAxxxxxxxxxxx
vi /etc/ppp/peers/IRDAxxxxxxxxxxx
   -add '/dev/rfcomm0' at top line

4) Phone side settings (Vodafone in Japan, using Nokia 6630 phone with BT)
-Connect your phone via USB or BT and put setting to the phone:
   Access point: vodafone (Tools->Settings->Connection->
     Packet data->Access point)

5) Pairing between Zaurus and phone (use common pin numbers such as 1234 and then set for auto-pairing...)

6) Zaurus dial-up network settings (for Vodafone network in Japan)
User name: ai@vodafone
Pass word:vodafone
Dial: *99#

[pdogn]

I am using a Anycom BTCF card in a SL-C3000 with the following packages installed:

sudo 0.1
susp-resume 0.9-3.1
bluez-zaurus 2.12-2.4.20-alpha4
susp-resume-bluez 0.9.2
qtopia-pannetworkapplet 1.0.1

The Anycom card is recognized by cardctl ident, but the card address is all zeroes when queried with hciconfig hci0.  Dmesg shows thw following driver error messages when the card is ejected and then inserted:

bluecard_cs:  Unknown HCI packet with type 0x28 received.
bluecard_cs:  Unknown HCI packet with type 0x20 received.
bluecard_cs:  Unknown HCI packet with type 0xfc  received.

Any ideas for  resolving the problem appeciated.

[tumnus]

Would that be the Anycom CF-300? If it is, it requires a kernel patch backported from kernel 2.6, which means replacing your Sharp kernel with a custom one.

The packages I have put together only support the stock Sharp kernel.

[pdogn]

Tumnus,

Thanks for the quick response.  My card is the Anycom CF-300, so I'd appeciate you recommendations as to a compatible CF format BT card.  I'd like to avoid the custom kernel if possible.

[tumnus]

Here's a list of cards and their compatibility with the Zaurus drivers:

https://www.oesf.org/index.php?title=Bluetooth_Card_Support

[byland3]

Can anyone please give corrections/comments/advice about why the steps below have not worked for me? Or should this configuration work?

SL-C3000 + Socket BT card (Version F) + Nokia 702NK/6630  phone?
----------------------------------------------------------------------------------------------------------------

1) download--> bluez_zaurus_2.12_2.4.20_alpha4_arm.ipk ( 211.87k )
[https://www.oesf.org/forums/index.php?act=Attach&type=post&id=279]
- Remember to rename the download and change some of those underscores (_) to bluez-zaurus_2.12-2.4.20-alpha4_arm.ipk


2) alpha4 (plus additional packages) installation:
- Removed the csr package and the alpha2 package.
- Installed alpha4 package.
-Install additional packages (not part of alpha4):
   -Install bluez libs??
   -Install bluez utils??
   -Install qtopia-bluetoothnetworkapplet (*Java installation required first)
-reboot.

3) Settings in Zaurus SL-C3000
-eject and reinsert BT card
#cardctl ident (check that card is recognized by zaurus)
#hciconfig (get BT mac address of zaurus side--> xx:xx:xx:xx:xx:xx)
    not necessary --> #sdptool browse (scan to find mac id)
# hcitool scan (scan for BT mac address of phone side--> xx:xx:xx:xx:xx:xx)
   -Service name : dial-up network ==> channel 1.


- re-entered settings in /etc/bluetooth/rfcomm.conf
- initial insertion of the Socket rev H card did not register with hcitool dev
- tried /etc/rc.d/init.d/bluetooth start --> didn't work either
- re-inserted the card. hcitool dev finally found the card.


vi /home/zaurus/Applications/Network/modules/IRDA.conf
find IRDA code --> IRDAxxxxxxxxxxx
vi /etc/ppp/peers/IRDAxxxxxxxxxxx
   -add '/dev/rfcomm0' at top line

4) Phone side settings (Vodafone in Japan, using Nokia 6630 phone with BT)
-Connect your phone via USB or BT and put setting to the phone:
   Access point: vodafone (Tools->Settings->Connection->
     Packet data->Access point)

5) Pairing between Zaurus and phone (use common pin numbers such as 1234 and then set for auto-pairing...)

6) Zaurus dial-up network settings (for Vodafone network in Japan)
User name: ai@vodafone
Pass word:vodafone
Dial: *99#
[div align=\"right\"][a href=\"index.php?act=findpost&pid=73446\"][{POST_SNAPBACK}][/a][/div]
[/quote]

[tumnus]

Well which bit hasn't worked?

Has your phone paired?

Did the GPRS connection fail? If it did fail, please post the contents of /tmp/qpe-ppp-log .

You don't need any extra packages to get basic Bluetooth working. The qtopia--bluetoothnetworkapplet package doesn't need Java.

You do need to to a 'sdptool browse' to find the actual channel of the DUN profile of your phone as this can differ from model to model.

[baliv]

Hi,
I have two SL-C3000 with Socket Rev H bt card.
I established "manually" a PAN connection:
  C3000#1: pand --listen --role GN
  C3000#2: pand –connect MACaddrC3000#1
                 ifconfig bnep0 192.168.0.101
  C3000#1: ifconfig bnep0 192.168.0.100

The problem is a communication performance / freezing after a while:
    C3000#1: ping -s 1024 192.168.0.101
          1032 bytes from 192.168.0.101: icmp_seq=0 ttl=64 time=4464.8 ms
          1032 bytes from 192.168.0.101: icmp_seq=1 ttl=64 time=4285.7 ms
          1032 bytes from 192.168.0.101: icmp_seq=2 ttl=64 time=5131.8 ms
          1032 bytes from 192.168.0.101: icmp_seq=3 ttl=64 time=6461.1 ms
          ping: sendto: Network is unreachable
   
However C3000#2 still show the connection:
     C3000#2: pand -l
            bnep0 MACaddrC3000#1

When I tried to have more input with hcidump, syslog, I notice that ping response time decreased, meaning that with  a takeCPUBusy.sh script I was able to reduce the response time below 100ms:
     C3000#2: cat files of a directory in loop
     C3000#1: ping -s 1024 192.168.0.101
           PING 192.168.0.101 (192.168.0.101): 1024 data bytes
           1032 bytes from 192.168.0.101: icmp_seq=0 ttl=64 time=129.2 ms
           1032 bytes from 192.168.0.101: icmp_seq=1 ttl=64 time=75.5 ms
           1032 bytes from 192.168.0.101: icmp_seq=2 ttl=64 time=74.5 ms
           1032 bytes from 192.168.0.101: icmp_seq=3 ttl=64 time=67.7 ms
           1032 bytes from 192.168.0.101: icmp_seq=4 ttl=64 time=65.2 ms
           1032 bytes from 192.168.0.101: icmp_seq=5 ttl=64 time=70.2 ms
           ...

I tried to reduce the speed rate from 230400 to 115200 on /etc/bluetooth/uart, without success (i.e. hciattach failed with BCSP timout error).

what else can I change try?

Any explanation, tip or any kind of help is welcome!


Following is dump of log that may be interessting:
# hciconfig -a
hci0:   Type: UART
        BD Address: 00:02:C7:42:B0:22 ACL MTU: 340:4  SCO MTU: 64:10
        UP RUNNING PSCAN ISCAN
        RX bytes:5828 acl:29 sco:0 events:55 errors:0
        TX bytes:10399 acl:44 sco:0 commands:15 errors:0
        Features: 0xff 0xff 0x0f 0x00 0x00 0x00 0x00 0x00
        Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
        Link policy: HOLD SNIFF PARK
        Link mode: SLAVE ACCEPT
        Name: 'zaurus'
        Class: 0x120114
        Service Classes: Networking
        Device Class: Computer, Palm
        HCI Ver: 1.1 (0x1) HCI Rev: 0x1bb LMP Ver: 1.1 (0x1) LMP Subver: 0x1bb
        Manufacturer: Cambridge Silicon Radio (10)


syslog:
Feb  2 12:45:31 localhost kernel: bcsp_recv: Error in BCSP hdr checksum
Feb  2 12:45:32 localhost kernel: bcsp_recv: Short BCSP packet
Feb  2 12:45:32 localhost kernel: bcsp_recv: Error in BCSP hdr checksum
Feb  2 12:45:32 localhost kernel: bcsp_recv: Short BCSP packet
Feb  2 12:45:33 localhost kernel: bcsp_recv: Short BCSP packet
Feb  2 12:45:33 localhost kernel: bcsp_recv: Error in BCSP hdr checksum
Feb  2 12:45:34 localhost last message repeated 7 times
Feb  2 12:45:34 localhost kernel: bcsp_recv: Out-of-order packet arrived, got 7 expected 6
Feb  2 12:45:34 localhost kernel: bcsp_recv: Out-of-order packet arrived, got 0 expected 6
Feb  2 12:45:34 localhost kernel: bcsp_recv: Out-of-order packet arrived, got 1 expected 6
Feb  2 12:45:35 localhost kernel: bcsp_recv: Error in BCSP hdr checksum
Feb  2 12:45:36 localhost last message repeated 7 times
Feb  2 12:45:36 localhost kernel: bcsp_recv: Out-of-order packet arrived, got 7 expected 6
Feb  2 12:45:36 localhost kernel: bcsp_recv: Out-of-order packet arrived, got 0 expected 6
Feb  2 12:45:36 localhost kernel: bcsp_recv: Out-of-order packet arrived, got 1 expected 6
Feb  2 12:45:37 localhost kernel: bcsp_recv: Error in BCSP hdr checksum
Feb  2 12:45:37 localhost last message repeated 2 times