User's Guide
Table Of Contents
- 1 Document status
- 2 Introduction
- 3 Hardware requirements
- 4 Interactions Overview
- 5 Incoming events Overview
- 6 Gesture interactions - Example of partner possibilities
- 7 Detailed interaction and event states
- 8 Setting up
- 9 Disconnect and reconnect
- 10 Power ON A1ll
- 11 Turning OFF and Factory data reset
- 12 OTA and DFU mode
- 13 Automatic logging of physical activities - an overview
- 14 Remote mode
- 15 Control mode
- 16 Heart rate measurements
- 17 Alarm
- 18 Incoming call
- 19 Notifications
- 20 Charging battery TBD!!
- 21 Xperia at hand features
- 22 Document history
UXP X
2014-12-05 34 / 55
IxD BlueprintUXC
CONFIDENTIAL
14.3 Application mode - extension guidelines
Extensions can get raw accelerometer data from A1ll, this will enable extensions to use A1ll for e.g. gaming or guitar playing. A small protocol for tap interaction is
provided but counted steps and sleep data is not provided.
Extension developers can do the following:
- Create their own design pattern for how to interact with A1ll using the raw accelerometer data.
- Use the pre defined tapping protocol for interaction.
Extension developers are limited by the following:
- Extensions can not use keypresses
- Extensions can not use vibrations.
- For Extensions that want to use tapping to control media, we suggest that they will use the same pattern as defined for Media player (view next chapter).
- There will be no warning saying that the battery may run out very fast.
- It is up to Extension developers to define and explain their chosen interaction pattern to the user.
TBD
- Explore if the SmartBand should send data to other apps that are not identified as Control-apps. For instance Runtastic? No tap interactions may be necessary?
- There is no 15 seconds time out from AHA for extensions that use sensor data.
Open extension protocol descoped and
replaced by native remote mode