lightblue-devel — Discussion about developing with LightBlue.

[LightBlue-devel] Lightblue on Ubuntu 11.04 or Python 2.7

[Santosh v. <vat...@gm...>]

Hello all,

I am a student at University of Pennsylvania and we are using
lightblue for a project. We have suddenly started encountering a
problem with lightblue socket.accept() method. We used this method
before for without any problems on Ubuntu 10.10 and Python 2.6.

The problem is as follows:

We have a bluetooth server that essentially runs the following code:

import lightblue

ss = lightblue.socket()
ss.bind(( "", 1 ))
ss.listen(1)
lightblue.advertise("BluetoothServer", ss, lightblue.RFCOMM)
sock, addr = ss.accept()

and a client that runs:

import lightblue

ss = lightblue.socket()
err = ss.connect_ex(("BluetoothAddress", BluetoothPort))

When we run the server and then the client, the client's connect_ex()
method returns with a 0 error code indicating that the connection was
successfully established. However the server ss.accept() method is
still blocked and does not return. We see that this problem exists
when the server is running on Ubuntu 11.04 and Python 2.7. We ran the
server code on Ubuntu 10.04 and Python 2.6 and it seems work just
fine. I just needed to know if this is a problem that someone has
encountered and if so does anyone know the solution or a workaround
for this problem. Thanks in advance.

-- 
Regards
Santosh G Vattam

Re: [LightBlue-devel] Use of lightblue in multithreaded applications

[Lukas H. <Lu...@gm...>]

Hello,

as multithreading isn't possible I tried to switch to a asynchronous 
behaviour. 

Is it possible to speficy a callback that gets called when there is new data 
availabe?

Should rfcommChannelData:rfcommChannel:data:length not be called when there is 
new data available? I added a NSLog output in this function, but it is only 
shown after I call the recv method of the socket. Does anybody know why?

Lukas

[LightBlue-devel] Use of lightblue in multithreaded applications

[Lukas H. <Lu...@gm...>]

Hello,

I wanted to port my application to Mac OS X.
This application uses PyQt4 for the user interface and has a seperate thread 
to manage a bluetooth socket (using pybluez on Windows/Linux and now I want to 
port this to OS X too).
The seperate thread is required, because otherwise the user interface will get 
blocked.

Here is a simple example of the thing I want to make:
from PyQt4.QtCore import *
from PyQt4.QtGui import *
import lightblue

class Thread(QThread):
    def run(self):
        sock = lightblue.socket()
        print "connecting"
        sock.connect(('00:1B:AF:84:FF:E2', 18))
        print "connected"
        
class Button(QPushButton):
    def __init__(self):
        QPushButton.__init__(self,  "Start thread")
        self.connect(self,  SIGNAL("clicked()"),  self.start) 
    
    def start(self):
        self.thread = Thread()
        self.thread.start()
        
app = QApplication([])
button = Button()
button.show()
app.exec_()


This didn't work, I get many of these error messages:
2010-01-30 11:25:35.909 Python[217:4c2f] *** __NSAutoreleaseNoPool(): Object 
0x105b30b80 of class NSConcreteMutableData autoreleased with no pool in place 
- just leaking
2010-01-30 11:25:35.912 Python[217:4c2f] *** __NSAutoreleaseNoPool(): Object 
0x105b25cd0 of class NSConcreteMutableData autoreleased with no pool in place 
- just leaking
2010-01-30 11:25:35.915 Python[217:4c2f] *** __NSAutoreleaseNoPool(): Object 
0x102df2010 of class NSConcreteMutableData autoreleased with no pool in place 
- just leaking
2010-01-30 11:25:35.917 Python[217:4c2f] *** __NSAutoreleaseNoPool(): Object 
0x105b080c0 of class NSConcreteMutableData autoreleased with no pool in place 
- just leaking

So i thought adding a seperate NSAutoreleasePool in my thread would solve the 
problem:
from PyQt4.QtCore import *
from PyQt4.QtGui import *
import lightblue
import Foundation

class Thread(QThread):
    def run(self):
        pool = Foundation.NSAutoreleasePool.alloc().init()
        
        sock = lightblue.socket()
        print "connecting"
        sock.connect(('00:1B:AF:84:FF:E2', 18))
        print "connected"
        
        pool.release()

class Button(QPushButton):
    def __init__(self):
        QPushButton.__init__(self,  "Start thread")
        self.connect(self,  SIGNAL("clicked()"),  self.start) 
    
    def start(self):
        self.thread = Thread()
        self.thread.start()
        

app = QApplication([])
button = Button()
button.show()
app.exec_()

But now the sock.connect hangs forever:
lukass-Mac:~ Lukas$ python test.py 
/Library/Python/2.6/site-packages/lightblue/_bluetoothsockets.py:42: 
DeprecationWarning: the sets module is deprecated
  import sets     # python 2.3
connecting


I know that the IOBluetooth framework isn't multithreadable, but is there no 
workaround for this (like using the bluetooth socket in only one thread)?
Is there any example for this task?
Is it really not possible to make an application using lightblue which has a 
non-blocking user interface?

I'm using Mac OS X 10.6 Snow Leopard.
Python: 2.6.1
lightblue: 0.4 with OS X 10.6 patch
PyQt4: 4.7

Thank you for any help,
Lukas Hetzenecker

[LightBlue-devel] hciconfig to change my bluetooth device

[Alexandre G. <al...@ri...>]

Hi!

I have a very bad bluetooth device in my laptop and I need a external
bluetooth device to send/receive files with lightblue. I use hciconfig to
down the embeded device, but I think that isn't working:

alex@little:~$ sudo hciconfig
[sudo] password for alex:
hci0:    Type: USB
    BD Address: 00:24:7E:98:4B:BE ACL MTU: 1021:8 SCO MTU: 64:1
    UP RUNNING PSCAN INQUIRY
    RX bytes:103399 acl:803 sco:0 events:1520 errors:0
    TX bytes:21180 acl:584 sco:0 commands:499 errors:0

hci1:    Type: USB
    BD Address: 00:22:F7:17:04:8F ACL MTU: 310:10 SCO MTU: 64:8
    UP RUNNING PSCAN
    RX bytes:1043 acl:0 sco:0 events:35 errors:0
    TX bytes:1342 acl:0 sco:0 commands:33 errors:0

alex@little:~$ sudo hciconfig hci0 down
alex@little:~$ sudo hciconfig
hci0:    Type: USB
    BD Address: 00:24:7E:98:4B:BE ACL MTU: 1021:8 SCO MTU: 64:1
    DOWN
    RX bytes:104734 acl:813 sco:0 events:1540 errors:0
    TX bytes:21399 acl:592 sco:0 commands:505 errors:0

hci1:    Type: USB
    BD Address: 00:22:F7:17:04:8F ACL MTU: 310:10 SCO MTU: 64:8
    UP RUNNING PSCAN INQUIRY
    RX bytes:5024 acl:21 sco:0 events:162 errors:0
    TX bytes:1830 acl:16 sco:0 commands:50 errors:0

I see here all ok, but when I try to send files in parallel (it works with
other computer, same device), but when I plug the device in my laptop and
deactive the embeded device doesn't work.

Any help?

Thanks,
Álex González

-- 
Please, don't send me files with extensions: .doc, .docx, .xls, .xlsx, .ppt
and/or .pptx
http://mirblu.com

[LightBlue-devel] Several bluetooth devices at time with lightblue

[Alexandre G. <al...@ri...>]

Hi!

I'm trying to do a bluetooth "spammer" and like to have more than one local
bluetooth devices, so I could send more than 7 files at time... anyway to do
this? I was searching info but I didn't find anything, anywhere to start
reading?

Bye and thanks!
Álex González

-- 
Please, don't send me files with extensions: .doc, .docx, .xls, .xlsx, .ppt
and/or .pptx
http://mirblu.com

[LightBlue-devel] LightBlue 0.3.2 released

[Bea L. <bl...@gm...>]

LightBlue 0.3.2 has been released!

This releases contains some major bug fixes. It fixes
lightblue.obex.recvfile()  on Linux (which was often refusing Put
requests), stops NSInconsistencyException from being raised on Mac OS
X during event processing, and makes 'from lightblue import *' work
again.

[LightBlue-devel] LightBlue 0.3 released

[Bea L. <bl...@gm...>]

LightBlue 0.3 has been released!

The main feature of this release is a new OBEXClient class for the Mac
OS X and Linux platforms. The library also now works on Mac OS 10.5,
and the BTUtil framework has been renamed to "LightAquaBlue" and has
been completely rewritten. The internals of the Linux OBEX client and
server implementations have also been completely rewritten to be more
flexible and more easily customised. Various unicode-related bugs have
also been fixed.

Downloads available from
http://lightblue.sourceforge.net

[LightBlue-devel] LightBlue 0.2.3 released

[Bea L. <bl...@gm...>]

LightBlue 0.2.3 has been released. This fixes the bug in the linux
version which stopped it from working with the newer versions of
PyBluez.

[LightBlue-devel] LightBlue 0.2.2 has been released

[Bea L. <bl...@gm...>]

LightBlue 0.2.2 has been released. These are the changes:

+ The PyS60 3rd Edition binaries have (really) been fixed, and
gethostaddr() and gethostclass() should also be fixed for PyS60 2nd
Edition FP2 and FP3.

+ Since it's getting more difficult to build for PyS60 1st Edition,
this build has been dropped for this version -- which isn't an issue
for this release since there are no new features -- but there won't be
any further builds for this edition. If you need to compile LightBlue
for 1st Edition, feel free to email me with any issues.

+ Fixed functions on Mac OS X build that wait (e.g. finddevices(),
recv() for sockets) so that they don't busy-wait and hog the CPU.


Downloads are available at http://lightblue.sourceforge.net and
http://sourceforge.net/project/showfiles.php?group_id=173752

[LightBlue-devel] LightBlue 0.2.1 released

[Bea L. <bl...@gm...>]

LightBlue 0.2.1 has been released. Hopefully it fixes several
installation issues with the Python For Series 60 3rd Edition .sisx
binary.

This version also adds an unsigned .sis for PyS60 3rd Edition with the
maximum free dev cert capabilities. To use this, you'll need to get a
free dev cert from Symbian Signed and install it to your phone. Then,
use the cert to sign the LightBlue .sis file, and install it to your
phone.

This thread has some more information about signing and certificates for PyS60:
http://discussion.forum.nokia.com/forum/showthread.php?t=95141

Since there are no other changes to the library for this release, I
haven't uploaded any new sis files for the PyS60 1st edition and 2nd
editions.