Hi Tim, > I am putting a JSR82 implementation on an Android device that uses > BlueZ, accessing BlueZ via the dbus api. > > JSR82 has an API where you can set service class bits for a particular > service you have registered. So the JSR82 implementation needs to be > able to set the class of device in some way. I would like to add a dbus > method to do this, and I'd like to know the opinion of BlueZ developers > on this: I did mention before that JSR82 is the most stupid Bluetooth API that I have seen so far, didn't I? Personally I wouldn't even bother with JSR82 and give up right away. It is really a pointless API. In BlueZ the services bits of the class of device settings are modified dynamically based on the registered SDP service records. So you don't have to do anything. Just register the right SDP service record with the proper UUID and it will take care of this automatically. Regards Marcel -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
