User manual

FCC ID: 2AB8ZND5

Users Manual

Download: PDF
FCCID_2641811

Lois/Clark Device Behavior April 28, 2015 New Business Group UX Document Owner: Anna Mansour anna.mansour@intel.com Intel Confidential — Do Not Forward

Contents 3 CURRENT JEWELRY (DEVICE) BEHAVIOR 10 SPECIAL SITUATIONS FOR THE R/GA APP 22 PLANNED JEWELRY (DEVICE) BEHAVIOR Intel Confidential — Do Not Forward | 2

Current Jewelry Behavior Intel Confidential — Do Not Forward | 3

Summary of Device Behaviors (Completed) Exact LED Colors TBD pending testing. Inactive = no movement/no alerts received from paired phone. Intel Confidential — Do Not Forward | 4

Summary of Device Behaviors (Planned) [By Beta. App must guide user to do FW update] Exact LED Colors TBD pending testing. Inactive = no movement/no alerts received from paired phone. Intel Confidential — Do Not Forward | 5

Bluetooth Advertising Events that will make the Device advertise itself (30 seconds): If the Device has not been paired with a phone § The device is turned on § The bluetooth pairing information is removed (via an 8-second button press) § [Planned] The button is pressed once when the device is already turned on If the Device has been paired with a phone § The device is turned on § A button press § A recognized double or triple tap § The BLE connection is interrupted § The bluetooth pairing information is removed (via an 8-second button press) § Periodically (~every 1s) to maintain a constant connection § [Planned] When movement (accelerometer) occurs after device hasn’t moved in a given time TBD More details in Clark/Lois BLE Behaviors document. Intel Confidential — Do Not Forward | 6

Button Overview Note: Currently, on release of the device button the haptic response is played. This will be fixed so that the haptics play after the button is held for the specified time. Turn on / BLE Advertise Note: If device is already powered on, pressing Power On Button the button will trigger BLE to advertise Vibra Device turns off Power Off Button User releases button in response to vibra Device wipes Vibra Vibra pairing info Wipe Pairing Info Button User releases button in response to vibra Device goes to recover mode Vibra Vibra HW Reset Vibra Recovery Mode Button User releases button in response to vibra (used rarely) 0 Sec 3 Sec 8 Sec 12 Sec Hold button for 12s for recovery mode/hw reset until light feedback (exact pattern TBD) Intel Confidential — Do Not Forward | 7

Debug Notifications – Extra Lights You’re Experiencing These occur along with the normal behaviors. They are temporary debugging codes and will be removed before the Beta Field Trial. Please see Device Release Notes for the most up to date debug notifications. Intel Confidential — Do Not Forward | 8

Tap Input Pattern Error: Feedback if a tap not successfully sent to phone. Buzz: 250ms LED: Red 5 Flicker (100ms On, 100ms Off) Pattern Gestures: Blink feedback for two and 3 taps. Intel Confidential — Do Not Forward | 9

Special Situations for the R/GA App to handle Intel Confidential — Do Not Forward | 10

[Planned] Recovery Mode Recovery Mode is needed for 3 situations 1. Device is non-functioning and no other fixes work (User-Initiated) 2. If BLE link is cut during FOTA (Automatic) 3. If too many critical problems have been detected (Automatic) There should be: • In-App detection of Recovery Mode and guidance for getting the user out of it (a firmware update). • FAQ/Support for putting the device into Recovery Mode when nothing else works, and getting the device out of Recovery Mode. • FAQ/Support for what to do when the device goes into Recovery Mode by itself. Intel Confidential — Do Not Forward | 11

Unpairing a Device – Potential Issues Unpairing should be done on both the jewelry and the phone to prevent future pairing issues. The user needs to be instructed to unpair from both the phone and the jewelry. Two potential sticky situations: Jewelry is still paired, Phone has no pairing info/is new Jewelry is wiped, Phone is still paired Scenario 1: Kate is lending her watch to Julie Scenario 3: Kate gets her watch back from Julie Julie can’t pair until she wipes watch BT settings. Kate’s phone will have old pairing info, even though it recognizes the watch. She won’t be Scenario 2: Olivia got a new phone able to pair until she removes the device from Olivia can’t pair until she wipes the ? her BT menu. watch BT settings. ? Intel Confidential — Do Not Forward | 12

Pairing, Wiping, Reconnecting Intel Confidential — Do Not Forward | 13

Pairing New Jewelry – Never Been Paired Put Device on Charger Begin Pairing Flow In App Confirmation of Pairing on Jewelry and plug in User follows App instructions to trigger Bluetooth advertising 1 Blink (500 ms) 1 Buzz (250 ms) Paired & Connected PAIR Brand new devices arrive in a shipping mode. They must be put on the charger to get out of shipping We recommend requiring the user to mode and be able to pair. press the button (an intentional act). It will power on automatically Note: A firmware update might be and advertise. necessary right after pairing. Intel Confidential — Do Not Forward | 14

Pairing New Jewelry – Never Been Paired A Potential Flow User views Device out of instruction card Plug in shipping mode Download Start Pairing Open Box Jewelry/ App Flow in App Charger and advertises Jewelry “Press Button Continue App Found & on Jewelry” Setup Flow Paired If Jewelry still A Firmware Update advertising, skip may be required Intel Confidential — Do Not Forward | 15

Pairing New Jewelry – Previously Paired (ex. sharing/selling) Remove previous pairing Begin Pairing Flow In App Confirmation of Pairing on Jewelry This will cause the device to Follow App instructions to broadcast for 30 seconds trigger Bluetooth advertising 1 Blink (500 ms) 1 Buzz (250 ms) Paired & Connected *Press* PAIR We recommend requiring the user to press the button (an intentional act). Intel Confidential — Do Not Forward | 16

Pairing New Jewelry – Previously Paired A Potential Flow Device still paired, not found App shows Receive Attempt to Wipe pairing help Jewelry Pair in App on Device (or FAQ link) Jewelry Attempt to “Press Button Continue App Found & Pair in App on Jewelry” Setup Flow Paired If Jewelry still A Firmware Update advertising, skip may be required Intel Confidential — Do Not Forward | 17

Wipe the Pairing for the Jewelry Remove Previous Pairing At 8 seconds, a notification Remove the Jewelry from the phone’s Press Jewelry button for 8s to reset it confirmation is played followed by the Bluetooth menu. This prevents issues if the (Jewelry must be on) Power On pattern user tries to pair the same Jewelry again. 1 Buzz (1.5 seconds) *Very Long Press* Forget this device * Press button for 8 seconds until haptic feedback, then release Intel Confidential — Do Not Forward | 18

Connecting Jewelry (previously paired) from the Device A. One Device Trigger Bluetooth Advertising Jewelry Finds Phone it is Paired to Jewelry Connects to Phone (if available) Found Connected Each time the connection does not exist and there is a paired phone, the device will advertise when: • Powered on • A tap is detected • 30 minutes have elapsed without connection since the last advertising event. • [Planned] The button is pressed • [Planned] Device is moved after not moving for a period of time Intel Confidential — Do Not Forward | 19

POR Connecting Jewelry (previously paired) from the Device B. Multiple Devices – no devices are already connected The first jewelry that has a Bluetooth Advertising condition triggered connects to the phone Connected Intel Confidential — Do Not Forward | 20

POR Connecting Jewelry (previously paired) from the Device C. Multiple Devices – one is already connected Jewelry A is connected and the user wants Option 1: Connect from the app Option 2: Once the user walks far enough, Jewelry B to connect Jewelry A will disconnect and Jewelry B will eventually connect Jewelry A Jewelry B Jewelry B Connected Connected CONNECT Intel Confidential — Do Not Forward | 21

Planned Jewelry Behavior Intel Confidential — Do Not Forward | 22

Planned Behaviors First Time Use – Shipping Mode • When receiving a brand new device, it needs to be put on the Qi charger first to get out of shipping mode. It will turn on and advertise (BT) for 30s. Charging Behavior • See page 26-27. • Charger LED displays 2 states: “charging” and “full” (if no alignment of coils, light turns off). Notification Interrupt • Differentiate “local” from “incoming” notification. • Allow some notifications to interrupt others. Device needs to queue notifications and play them out serially. • Incoming Notifications (SMS, email, call etc.) should have the ability to queue and play one after the other. Device Connect/Disconnect Alert • Add as a configuration, off by default. Recovery Mode & Alert • Press button for 12 seconds to trigger Recovery Mode. • Feedback that the device is in Recovery Mode (an LED pattern). • The app will need to walk the user through getting the device out of Recovery Mode (a firmware update). • API update to detect when the device is in Recovery Mode. Firmware Update Success • Buzz: 2 short buzzes (250ms On, 250ms Off). • There is an open bug – currently there is no feedback for FW update success. Intel Confidential — Do Not Forward | 23

Battery Behavior Intel Confidential — Do Not Forward | 24

CR [Planned] Status Alert: Low Battery Device is Inactive Device is inactive for 10 minutes or more. Once moved, Device indicates its low battery status. (and sends to the phone, if appropriate) Intel Confidential — Do Not Forward | 25

[Planned] Charging the Device Lois Charging (Red, or Amber Empty Charger pending tuning ability) Charged (Blue) Clark Intel Confidential — Do Not Forward | 26

CR [Planned] Charging Behavior / Taking off of the charger if Power is On Display Status Alert: Normal sequence if battery is greater than low. Display Status Alert: Low Battery sequence if device battery is low. Additionally, if battery is not empty, BLE advertises and if Jewelry is in range, connects to paired phone. If the battery is dead, the Device will power on automatically on the charger as soon as it has enough charge. Intel Confidential — Do Not Forward | 27

Intel Confidential — Do Not Forward |


Document Created: 3600-06-23 00:00:00
Document Modified: 3600-06-23 00:00:00
© 2025 FCC.report
This site is not affiliated with or endorsed by the FCC