1. Run the attached file on bluecove-emu, no OBEX PUSH service will be
discovered;
2. Change Bluecove ServiceRecordImpl for the attached one and the service will
be discovered.
The "dirty fix" in ServiceRecordImpl enables an OBEX PUSH server to be
discovered.
It seems that in BluetoothConsts there is a map of unused OBEX UUIDs, which
should be used at this point of ServiceRecordImpl.
I've discussed this on the following thread:
http://groups.google.com/group/bluecove-users/browse_thread/thread/36352fac7c18f
115
Thanks,
Rodolpho
Original issue reported on code.google.com by rodolpho...@gmail.com on 8 Aug 2010 at 3:42
Original issue reported on code.google.com by
rodolpho...@gmail.com
on 8 Aug 2010 at 3:42Attachments: