Page 2 of 2 FirstFirst 12
Results 21 to 26 of 26
Like Tree4Likes
  1. #21  
    hrm well i did some poking around using novaterm and with the help of the WebOS Internals site particularly the New Bluetooth Page.

    Wasn't able to get far though. Here's what I was able to come up with:

    First off it seems the known Palm Bluetooth related files in /usr/bin are
    PmBtEngine
    PmBtStack
    PmBtStart

    PmBtStart being the bash script that seems to start Bluetooth.
    here is the code for those interested:
    Code:
    #!/bin/sh                                                                      
          
    # don't use highspeed UART                                                     
    NOHU=/var/log/NOHU                                                             
                                                                                   
    # Startup script to load CSR stack and start Bluetooth Engine                  
                                                                                   
    # Use BTid ROM token if available, otherwise btconfig.  If no btconfig,        
    # append 2 randomly generated bytes to 'ID' below, and update btconfig.        
    ID="00:02:5b:12"                                                               
    btid=`cat /dev/tokens/BToADDR`                                                 
    if test -z $btid; then                                                         
       btid=`cat /var/log/btconfig`                                                
       if test -z $btid; then                                                      
          # get two random bytes in the right format                               
          btid="$ID:`dd if=/dev/urandom bs=2 count=1 | hexdump -e '1/1 \"%02x:\"'`"
          btid=`expr substr "$btid" 1 17`                                          
          echo $btid > /var/log/btconfig                                           
       fi                                               
    fi                                                  
                                                        
    STACK_NAME=PmBtStack                                
    ENGINE_NAME=PmBtEngine                                       
    CONTACTS_NAME=PmBtContacts                                   
    STACK_PATH=/usr/bin/$STACK_NAME                              
     
    btck=26000      # 26MHz clock                                                  
    btbaud=115200 # default 115200 baud rate                                       
    PS_PORT=16888                                                                  
                                                                                   
    # initialize default non-highspeed UART port                                   
    DEV=/dev/ttyS2                                                                 
                                                                                   
    # load CSR stack                                                               
    if test -e $STACK_PATH; then                                                   
       echo $PS_PORT > /var/log/btport                                             
                                                                                   
       # load and use highspeed UART driver if available                           
       if test -e /dev/bt_uart && ! test -e $NOHU; then                            
          DEV=/dev/bt_uart                                                         
              btbaud=3686400                                                       
       fi                                                                          
                                                        
       killall -w $ENGINE_NAME                          
       killall -w $STACK_NAME                           
       killall -w $CONTACTS_NAME                        
       echo exec $STACK_PATH -C $DEV -X $btid -F $btck -U $btbaud
       exec $STACK_PATH -C $DEV -X $btid -F $btck -U $btbaud     
    else                                                         
       logger -t $0 '*** BT stack failed to start.'              
    fi
    The BT device itself seems to be located at /dev/bt_uart

    also it looks like bsl0 is the bluetooth interface in network config(ifconfig -a) as it corresponds to the MAC address of the TouchPads own bluetooth chip.
    I'm not sure what the other interfaces are for besides eth0(wifi) and lo(local loopback). There also is a dummy0, gre0, and rmnet0 through rmnet7. I also noticed none of the interfaces correspond to the MAC address of my Blackberry Phone.

    That's about as far as I got though. I wasn't able to figure out how to get PmBtStack to run in debug mode or output it either to the shell or logs to see if the PAN profile is actually found and initialized in 3.0.4. I've seen debugging outputs from others showing PAN being registered and initialized assuming those were WebOS 2.x or older though since I couldn't figure out debugging. Killing the two Bluetooth engine related processes and restarting them normally would result in errors or cause it to hang at the shell for myself in 3.0.4.

    checking for Palm Bluetooth running processes reveals as follows:
    Code:
    ps aux | grep PmBt 
    root      2191  0.0  0.3  65780  3280 ?        S<Ll 04:22   0:00 /usr/bin/PmBtStack -C /dev/bt_uart -X **:**:**:**:**:** -F 26000 -U 3686400
    root      2392  0.0  0.4  58528  4020 ?        SLl  04:22   0:00 /usr/bin/PmBtEngine {"list":["hfp/hsp","hf","a2dp","avrcp","opp","opps","spp","mapc","hid"]}
    from there it doesn't look like it PAN is loading and it seems like the Bluetooth Profiles are loaded from within PmBtEngine itself(second line). However maybe its not loading because my Blackberry only supports DUN?

    I'm wondering if it may be possible to insert a profile for DUN/PAN into the end of the PmBTStart script? If not it sounds like it needs to be within PmBTEngine itself. The problem with that is its compiled code thus unreadable and Palm hasn't released the source for it. I doubt they will since their Bluetooth engine is supposedly proprietary as well although it cant hurt to bug them by constantly requesting it

    Otherwise the only options for getting DUN/PAN support on the TP is to find a way to install a different Bluetooth Engine like that WebOS Internals article talked about, beg HP to add support(again not looking likely), or move to using Android on the TP instead of WebOS(a thought that will probably make many here cringe ).
  2. #22  
    anyone know If the plan on Implementing support for this in the next update
  3. #23  
    Would be nice but considering webOS has never supported it as a client combined with a move towards just using wifi instead with newer smartphones for tethering I doubt it will ever happen.

    I suppose constantly asking HP support for it couldn't hurt though. Just not sure we'd get enough people interested in doing so.
  4. #24  
    Even if you were able to setup the connection (not a problem because you are _connecting_ to a DUN service which is basically a RFCOMM port, not exposing one), I've always found it hard to confuse WebOS into thinking it has a network connection active.
  5. mauro1's Avatar
    Posts
    205 Posts
    Global Posts
    213 Global Posts
    #25  
    for my money, I have setup tethering between my thinkpad and my pre phone via all three methods (WiFi,BT,USB), and they work reliably. I find myself using the BT transport very seldomly due to bandwidth limitations of the transport. So I only use BT when a) the WiFi spectrum is really crowded and b) I do not have a USB cable handy.
    Palm Pilot -> IBM WorkPad -> Handspring Visor -> Palm VIIx -> Palm T|X -> Palm Pre -> US GSM Palm Pre 2 [shelved] and 16GB HP TouchPad [died] -> (Samsung GNex and 32GB HP Touchpad with CM9)
  6. #26  
Page 2 of 2 FirstFirst 12

Tags for this Thread

Posting Permissions