~wtay/bluez - Bluez hacking

Age	Commit message (Collapse)	Author	Files	Lines
2012-06-28	doc: Fix typo	Michal Labedzki	1	-1/+1
	This patch fix simple typo in documentation of API.
2012-01-23	proximity-api: Add Link Loss Alert for Proximity Reporter API	Claudio Takahasi	1	-0/+6
	PropertyChanged signal for LinkLossAlertLevel property is emitted when a given remote device writes a new value for the Alert Level characteristic in the local Link Loss service. Each platform is free to define the actions for the detected signal.
2012-01-23	proximity-api: Add Proximity Reporter API	Claudio Takahasi	1	-2/+32
	Adds API for Immediate Alert Service(IAS) abstraction. IAS is used by Proximity Monitors and Find Me Locators to notify the user that reporter/target has been found. This new interface combines Proximity Reporter and Find Me Target in the same API providing the flexibility to implement external applications to control alerts(including per device alerts). This abstraction allows the development of platform specific applications to control Immediate Alert coming from Proximity Monitor and Find Me Locator. This provides flexibility to define different level and tone for each device. Use case: watch finding a mobile phone.
2011-08-02	Proximity API simplification	Claudio Takahasi	1	-30/+6
	Delegates the Immediate Alert Level control to the caller(client). Immediate Alert Service is shared between Path Loss and Find Me. Three signal level states are defined: "good", "regular" and "weak". Meaning that at least two thresholds are necessary to implement a proper state transition. "unknown" will be returned if the link is not active. For Path Loss, the logic to trigger the writting operation of the Immediate Alert Level characteristic needs to be implemented in the client. SignalLevel can be only one of the inputs to define when and which value to write in the characteristic.
2011-07-09	Add Proximity API	Claudio Takahasi	1	-0/+78
	Covers the Proximity Monitor 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. 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 characteristic.