On Thu, 2011-06-30 at 15:24 -0300, Claudio Takahasi wrote: > Covers the Proximity Reporter for Link Loss, Tx Power and Immediate > Alert services. This first proposal considers that the connections > will be managed by the bluetoothd core based on the registered > connection callbacks. Any examples of possible uses, or hardware implementing those? Is this good enough to implement both sides of the profile, or just one side of it? Is this something that could require UI being written? > Only one instance of Immediate Alert service is allowed, "Alert Level" > characteristic of this service is used by Find Me and Path Loss. Note > that "Alert Level" for Path Loss is a LOCAL property written in the > Immediate Alert service when the threshold is reached. For Find Me > the user/application needs to actively enable the alert in the Immediate > Alert service. Link Loss has it's own instance of Alert Level its. > characteristic. Cheers -- 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
