-
Hi,
I assume you mean "connecting client" rather than "connecting server". In the lightblue.obex.OBEXClient class you can specify the exact headers to use when sending files.
However, you'd need to control the code on the phone to actually be able to read this information, since phones normally just use the bluetooth name of the connecting device when showing "x is trying to send a file"...
2009-11-11 07:47:23 UTC in LightBlue
-
If it works from obexftp but not LightBlue, it could be that the file is being sent to an OBEX FTP server rather than an OBEX Push server on the device. The lightblue.obex.sendfile() function doesn't use the FTP protocol when connecting, which would be a problem if it is connecting to an FTP server.
2009-08-20 08:32:43 UTC in LightBlue
-
blammit made 5 file-release changes.
2009-08-13 09:38:01 UTC in LightBlue
-
blammit made 2 file-release changes.
2009-08-13 09:37:01 UTC in LightBlue
-
Hi Álex,
Are you sure it's sending to the correct channel for the OBEX Push service? Do you have any logs to indicate what the problem might be?
The PIN handling is done at a lower level than lightblue, so you'd have to use a different library to handle that. If you're on linux, try using the python dbus bindings for bluez.
2009-08-13 09:35:26 UTC in LightBlue
-
blammit made 4 file-release changes.
2009-07-28 06:18:01 UTC in LightBlue
-
blammit made 2 file-release changes.
2009-07-28 06:16:01 UTC in LightBlue
-
blammit made 2 file-release changes.
2009-07-28 06:09:02 UTC in LightBlue
-
blammit committed revision 28 to the LightBlue SVN repository, changing 10 files.
2009-07-16 09:45:27 UTC in LightBlue
-
blammit committed revision 27 to the LightBlue SVN repository, changing 10 files.
2009-07-16 07:54:14 UTC in LightBlue
