I'm using a UUID that I generated online...nothing special. Are there certain guidelines for creating UUIDs for certain types of tasks (like HID for example)? Even though I've coded up client/server pairs in Python and Java, I'm still at the 2% level of Bluetooth understanding. I have seen threads around that seem to indicate that if you are offering HID interaction then you want to start with a certain sequence in your UUID, perhaps a similar thing for OBEX related functionality. Any truth to that?
So far I've been very disappointed with Android bluetooth support. My current app idea requires the ability to be in permanent discovery mode to really take advantage of the system....when I found out that wasn't even possible on Android I almost threw my phone through a wall. Now there is this completely unnecessary and inexplicable need to manually unpair devices for success. Irritating!
By the way do you know any good introductory resources for Bluetooth? Especially as it pertains to Android? So far I've been googling one question/issue after another, trying to build up my knowledge that way....but thats a steep hill to climb. I would be especially interested to find out how to incorporate profiles like OBEX into my own application because had I figured out how to use OBEX inside my application, my work would have been reduced by 95%.