I need to setup an in-app OBEX server on an Android 2.3 device. Using the Bluetooth Chat Sample code I was able to setup an OBEX server. However, the server needs to use a custom UUID so the service is not registered as an ‘OBEX Server’
# sdptool browse local
...(snip)...
Service Name: OBEX Object Push
Service RecHandle: 0x10000
Service Class ID List:
UUID 128: ab123abc-1a2b-3c4d-5d7f-1234567890ab
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 18
So, when I receive data, it looks like I am receiving a raw OBEX connection request:
80 00 07 10 00 04 00 00 00 00 ...(snip)... 00 00 00 (1kb file)
Is there an OBEX implementation that I can use or do I have to implement the protocol myself?
I don’t want to use the inbuilt OBEX server – this has to be in app. I have tried BlueCove but I abandoned it when I had issues registering a service.
Yes, I did see this post and read the link in it, but by golly, there must be an easier way!
I ended up implementing the protocol myself. It wasn’t as hairy as I imagined. Since I was expecting only a specific client to connect and I knew that the client would only be pushing one file I was able to partially implement only the sections of the protocol that I needed.
Some documentation that helped with understanding the OBEX protocol were Obex13.pdf at: http://gitorious.org/gammu/gsm-docs/trees/e5161a75fb1e1c1608959b27ae3c3940bcf0911b/standards/obex
A quick snippet of how I parsed the sockets input stream:
(Note OBEXUtils and OBEXConstants are my classes.)
Snip of OBEXConstant: