diff --git a/1+BREDR+++GFPS.md b/1+BREDR+++GFPS.md
new file mode 100644
index 0000000..a2cc2f6
--- /dev/null
+++ b/1+BREDR+++GFPS.md
@@ -0,0 +1,3 @@
+# 1 BREDR + GFPS
+
+该功能是通过GFPS 快速配对BREDR
diff --git a/1+Distance+测试失败.md b/1+Distance+测试失败.md
new file mode 100644
index 0000000..17ecf6b
--- /dev/null
+++ b/1+Distance+测试失败.md
@@ -0,0 +1,7 @@
+# 1 Distance 测试失败
+
+客户端测试1.2m不会有弹窗，认证实验室验证的时候1.2m却有弹窗：
+
+
+
+[BBPRO3BUG-28971] [BBPro3][RTL8773DFL+RTL8763EAU][GMI/WLT/JLAB_Daybreak][Gaming Stereo/Audio mixing]: GFPS pixel 7(android 13)没有弹窗 - Jira
diff --git a/1+Error+performing+GATT+operation_+.......md b/1+Error+performing+GATT+operation_+.......md
new file mode 100644
index 0000000..06249d5
--- /dev/null
+++ b/1+Error+performing+GATT+operation_+.......md
@@ -0,0 +1,13 @@
+# 1 Error performing GATT operation: ......
+
+
+
+耳机端不支援LEA， 手机端测试的时候好像setting界面开发者选项里面把 Bypass Bluetooth LE Audio Allowlist 打开了， 需要把Bypass Bluetooth LE Audio Allowlist 关掉并且重启手机再测试
+
+
+
+\
+
+https://partnerissuetracker.corp.google.com/u/0/issues/422213477
+
+\
diff --git a/1+Error+performing+GATT+operation_+fe2c1238-8366-......md b/1+Error+performing+GATT+operation_+fe2c1238-8366-......md
new file mode 100644
index 0000000..66c481e
--- /dev/null
+++ b/1+Error+performing+GATT+operation_+fe2c1238-8366-......md
@@ -0,0 +1,11 @@
+# 1 Error performing GATT operation: fe2c1238-8366-.....
+
+**测试手机支援LEA, 开发者选项中将 Bypass Bluetooth LE Audio 选项关掉，然后重启手机，再重新测试，好像就不会遇到上面截图对应的问题了**
+
+****
+
+
+
+\
+
+
diff --git a/1+Fast+Pair+Validator+FAQ.md b/1+Fast+Pair+Validator+FAQ.md
new file mode 100644
index 0000000..3e5cc86
--- /dev/null
+++ b/1+Fast+Pair+Validator+FAQ.md
@@ -0,0 +1 @@
+# 1 Fast Pair Validator FAQ
diff --git a/1+Firmware+Version+with+LE+audio+conn....md b/1+Firmware+Version+with+LE+audio+conn....md
new file mode 100644
index 0000000..18af3ca
--- /dev/null
+++ b/1+Firmware+Version+with+LE+audio+conn....md
@@ -0,0 +1,5 @@
+# 1 Firmware Version with LE audio conn...
+
+
+
+[BB2BUG-52827] [BB2][8763EWM][Tiger][GFPS][fast pair validator][fast pair測項][LE Audio] Firmware version 測試fail - Jira
diff --git a/1+GFPS+legacy+pair+搭配支援LEA手机不连+legacy+profile(A2DP_HFP).md b/1+GFPS+legacy+pair+搭配支援LEA手机不连+legacy+profile(A2DP_HFP).md
new file mode 100644
index 0000000..4599e95
--- /dev/null
+++ b/1+GFPS+legacy+pair+搭配支援LEA手机不连+legacy+profile(A2DP_HFP).md
@@ -0,0 +1,228 @@
+# 1 GFPS legacy pair 搭配支援LEA手机不连 legacy profile(A2DP/HFP)
+
+耳机端走的是GFPS legacy pair， 和支援LEA的手机做initial pair， 支援LEA的手机不连legacy profile,
+
+**测试发现：**
+
+**打开legacy CTKD LE 的功能之后 支援LEA的手机就会来连legacy profile**
+
+**关闭 legacy CTKD LE 功能之后， 支援LEA的手机就不会来连legacy profile**
+
+[BBPRO3BUG-24407] [BBPRO3][EVB][E Cut][3.15.0.5+TestBin][Single]配置Finder，耳机开机进配对，无法连接到Find Device - Jira
+
+https://partnerissuetracker.corp.google.com/u/0/issues/441653921
+
+\
+
+\
+
+https://partnerissuetracker.corp.google.com/u/0/issues/411582869
+
+
+
+
+// Device bonded
+04-18 14:30:36.473 1002 2508 2994 I BluetoothBondStateMachine: XX:XX:XX:XX:22:88 is bonded, wait for SDP complete to broadcast bonded intent
+// SDP
+04-18 14:30:36.606 1002 2508 2910 I bt_bta_dm: bta_dm_sdp_result: GATT services discovered using SDP
+04-18 14:30:36.606 1002 2508 2910 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:1798 - btif_dm_search_services_evt: SDP finished for xx:xx:xx:xx:22:88:
+04-18 14:30:36.606 1002 2508 2910 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:1807 - btif_dm_search_services_evt: New UUIDs for xx:xx:xx:xx:22:88:
+04-18 14:30:36.606 1002 2508 2910 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:1813 - btif_dm_search_services_evt: index:0 uuid:00001101-0000-1000-8000-00805f9b34fb
+// 1108 UUID_HEADSET
+04-18 14:30:36.606 1002 2508 2910 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:1813 - btif_dm_search_services_evt: index:1 uuid:00001108-0000-1000-8000-00805f9b34fb
+// 111E UUID_HANDSFREE
+04-18 14:30:36.607 1002 2508 2910 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:1813 - btif_dm_search_services_evt: index:2 uuid:0000111e-0000-1000-8000-00805f9b34fb
+//110B UUID_AUDIO_SINK
+04-18 14:30:36.607 1002 2508 2910 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:1813 - btif_dm_search_services_evt: index:3 uuid:0000110b-0000-1000-8000-00805f9b34fb
+04-18 14:30:36.607 1002 2508 2910 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:1813 - btif_dm_search_services_evt: index:4 uuid:0000110e-0000-1000-8000-00805f9b34fb
+04-18 14:30:36.607 1002 2508 2910 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:1813 - btif_dm_search_services_evt: index:7 uuid:6a24eeab-4b65-4693-986b-3c26c352264f
+04-18 14:30:36.607 1002 2508 2910 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:1813 - btif_dm_search_services_evt: index:8 uuid:df21fe2c-2515-4fdb-8886-f12c4d67927c
+04-18 14:30:36.607 1002 2508 2910 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:498 - get_cod: remote_cod=0x00244404
+04-18 14:30:36.607 1002 2508 2910 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:1863 - btif_dm_search_services_evt: SDP search done for xx:xx:xx:xx:22:88
+// Not sure if waiting for LE service discovery here
+04-18 14:30:36.607 1002 2508 2910 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:1917 - btif_dm_search_services_evt: Bonding LE Audio sink - must wait for le services discovery to pass all services to java xx:xx:xx:xx:22:88
+04-18 14:30:36.607 1002 2508 2910 I bt_bta_dm: bta_dm_search_cmpl: No BLE connection, processing classic results
+// Phone disconnected from provider.
+04-18 14:30:40.615 1002 2508 2910 I btm_acl : disconnect_acl: Disconnecting peer:xx:xx:xx:xx:22:88 reason:HCI_ERR_PEER_USER comment:stack::l2cap::l2c_link::l2c_link_timeout All channels closed
+32183 06:30:40.616070 host controller HCI_CMD 7 Sent Disconnect |
+
+
+
+
+
+
+
+// ACL LE connected
+04-18 14:30:32.132 1002 1048 2043 I bthal.activity: handle_ble_meta_event: LE Enhanced Connection Complete, conn_handle:041, conn_bda: XX:XX:44:44:22:88
+04-18 14:30:32.223 1002 2508 2910 I bt_bta_dm: bta_dm_acl_up: Acl connected peer:xx:xx:xx:xx:22:88 transport:BT_TRANSPORT_LE handle:65
+04-18 14:30:34.934 1002 2508 2910 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:586 - bond_state_changed: Bond state changed to state=1[0:none, 1:bonding, 2:bonded],prev_state=0, sdp_attempts=0
+04-18 14:30:34.934 1002 2508 2954 I BluetoothBondStateMachine: bondStateChangeCallback: Status: 0 Address: XX:XX:XX:XX:22:88 newState: 1 hciReason: 0
+04-18 14:30:34.944 1002 2508 2994 I BluetoothBondStateMachine: Bond State Change Intent:XX:XX:XX:XX:22:88 BOND_NONE => BOND_BONDING
+// ACL BR/EDR connected
+04-18 14:30:36.075 1002 2508 2910 I bt_bta_dm: bta_dm_acl_up: Acl connected peer:xx:xx:xx:xx:22:88 transport:BT_TRANSPORT_BR_EDR handle:11
+04-18 14:30:36.467 1002 2508 2910 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:586 - bond_state_changed: Bond state changed to state=2[0:none, 1:bonding, 2:bonded],prev_state=1, sdp_attempts=1
+04-18 14:30:36.467 1002 2508 2954 I BluetoothBondStateMachine: bondStateChangeCallback: Status: 0 Address: XX:XX:XX:XX:22:88 newState: 2 hciReason: 0
+04-18 14:30:36.473 1002 2508 2994 I BluetoothBondStateMachine: XX:XX:XX:XX:22:88 is bonded, wait for SDP complete to broadcast bonded intent
+04-18 14:30:36.473 1002 2508 2994 I BluetoothBondStateMachine: StableState(): Entering Off State
+04-18 14:30:36.607 1002 2508 2910 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:1917 - btif_dm_search_services_evt: Bonding LE Audio sink - must wait for le services discovery to pass all services to java xx:xx:xx:xx:22:88
+04-18 14:30:39.492 1002 2508 2994 I BluetoothBondStateMachine: Bond State Change Intent:XX:XX:XX:XX:22:88 BOND_BONDING => BOND_BONDED
+// BT_ACL_STATE_DISCONNECTED
+04-18 14:30:40.768 1002 2508 2910 I bt_shim_hci: packages/modules/Bluetooth/system/main/shim/hci_layer.cc:304 - operator(): ISO disconnection from GD, handle: 0x0b, reason: 0x13
+04-18 14:30:40.769 1002 2508 2910 D bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:2552 - btif_dm_acl_evt: Sent BT_ACL_STATE_DISCONNECTED upward as ACL link down event device:xx:xx:xx:xx:22:88 reason:HCI_ERR_PEER_USER
+04-18 14:30:51.134 1002 2508 2910 I bt_shim_hci: packages/modules/Bluetooth/system/main/shim/hci_layer.cc:304 - operator(): ISO disconnection from GD, handle: 0x41, reason: 0x16
+04-18 14:30:51.137 1002 2508 2910 D bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:2552 - btif_dm_acl_evt: Sent BT_ACL_STATE_DISCONNECTED upward as ACL link down event device:xx:xx:xx:xx:22:88 reason:HCI_ERR_CONN_CAUSE_LOCAL_HOST
+// Bonding Removed
+04-18 14:31:50.137 1002 2508 2910 I bt_btif_storage: packages/modules/Bluetooth/system/btif/src/btif_storage.cc:889 - btif_storage_remove_bonded_device: Removing bonded device addr=xx:xx:xx:xx:22:88
+04-18 14:31:50.137 1002 2508 2910 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:586 - bond_state_changed: Bond state changed to state=0[0:none, 1:bonding, 2:bonded],prev_state=2, sdp_attempts=0
+04-18 14:31:50.137 1002 2508 2910 I bt_btif_storage: packages/modules/Bluetooth/system/btif/src/btif_storage.cc:889 - btif_storage_remove_bonded_device: Removing bonded device addr=xx:xx:xx:xx:22:88
+04-18 14:31:50.137 1002 2508 2910 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:586 - bond_state_changed: Bond state changed to state=0[0:none, 1:bonding, 2:bonded],prev_state=0, sdp_attempts=0
+04-18 14:31:50.137 1002 2508 2910 E BluetoothMetricIdManager: packages/modules/Bluetooth/system/gd/common/metric_id_manager.cc:190 - ForgetDevice: Failed to remove device from paired_device_cache_
+04-18 14:31:50.140 1002 2508 2994 D AdapterProperties: Removing bonded device:XX:XX:XX:XX:22:88
+04-18 14:31:50.146 1002 2508 2994 I BluetoothBondStateMachine: Bond State Change Intent:XX:XX:XX:XX:22:88 BOND_BONDED => BOND_NONE
+04-18 14:31:50.147 1002 2508 2994 I BluetoothBondStateMachine: StableState(): Entering Off State |
+
+
+
+
+
+
+
+//Pairing starts
+04-18 14:30:32.100 I NearbyDiscovery: FastPairController: Validator: onValidatorConnectionRequested [CONTEXT service_id=265 ]
+04-18 14:30:32.100 I FastPair: FPDC: Starting to pair XX:XX:XX:XX:22:88: key[64], Preferences{gattOperationTimeoutSeconds=10, gattConnectionTimeoutSeconds=15, bluetoothToggleTimeoutSeconds=10, bluetoothToggleSleepSeconds=2,
+04-18 14:30:32.107 D FastPairUtils: FastPair: Pairing finished with intent action: com.google.android.gms.nearby.discovery.ACTION_VALIDATOR_PAIR_PROGRESS
+04-18 14:30:32.132 I bthal.activity: handle_ble_meta_event: LE Enhanced Connection Complete, conn_handle:041, conn_bda: XX:XX:44:44:22:88
+04-18 14:30:32.223 I bt_bta_dm: bta_dm_acl_up: Acl connected peer:xx:xx:xx:xx:22:88 transport:BT_TRANSPORT_LE handle:65
+04-18 14:30:32.224 D BluetoothDatabase: getProfileConnectionPolicy: device XX:XX:XX:XX:22:88 is not in cache
+04-18 14:30:33.870 D FastPairUtils: FastPair: Pairing finished with intent action: com.google.android.gms.nearby.discovery.ACTION_VALIDATOR_PAIR_PROGRESS
+04-18 14:30:34.922 D FastPairUtils: FastPair: Pairing finished with intent action: com.google.android.gms.nearby.discovery.ACTION_VALIDATOR_PAIR_PROGRESS
+04-18 14:30:34.944 I BluetoothBondStateMachine: Bond State Change Intent:XX:XX:XX:XX:22:88 BOND_NONE => BOND_BONDING
+04-18 14:30:36.075 I bt_bta_dm: bta_dm_acl_up: Acl connected peer:xx:xx:xx:xx:22:88 transport:BT_TRANSPORT_BR_EDR handle:11
+04-18 14:30:36.201 D CachedBluetoothDevice: Device name: JBL Tune 530BT
+04-18 14:30:36.467 I bt_bta_dm: bta_dm_search_sm_execute: state:BTA_DM_SEARCH_IDLE, event:BTA_DM_API_DISCOVER_EVT[0x202]
+//UUIDs discovered and device bonded
+04-18 14:30:36.606 D bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:1985 - btif_dm_search_services_evt: New GATT over SDP UUIDs for xx:xx:xx:xx:22:88:
+04-18 14:30:36.606 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:2002 - btif_dm_search_services_evt: No well known GATT services discovered
+04-18 14:30:36.606 I bt_bta_dm: bta_dm_search_sm_execute: state:BTA_DM_DISCOVER_ACTIVE, event:BTA_DM_DISCOVERY_RESULT_EVT[0x207]
+04-18 14:30:36.606 V bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:1777 - btif_dm_search_services_evt: result=0x0, services 0xc00c0062
+04-18 14:30:36.606 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:1798 - btif_dm_search_services_evt: SDP finished for xx:xx:xx:xx:22:88:
+04-18 14:30:36.606 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:1807 - btif_dm_search_services_evt: New UUIDs for xx:xx:xx:xx:22:88:
+04-18 14:30:36.606 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:1813 - btif_dm_search_services_evt: index:0 uuid:00001101-0000-1000-8000-00805f9b34fb
+04-18 14:30:36.606 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:1813 - btif_dm_search_services_evt: index:1 uuid:00001108-0000-1000-8000-00805f9b34fb
+04-18 14:30:36.607 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:1813 - btif_dm_search_services_evt: index:2 uuid:0000111e-0000-1000-8000-00805f9b34fb
+04-18 14:30:36.607 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:1813 - btif_dm_search_services_evt: index:3 uuid:0000110b-0000-1000-8000-00805f9b34fb
+04-18 14:30:36.607 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:1813 - btif_dm_search_services_evt: index:4 uuid:0000110e-0000-1000-8000-00805f9b34fb
+04-18 14:30:36.607 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:1813 - btif_dm_search_services_evt: index:7 uuid:6a24eeab-4b65-4693-986b-3c26c352264f
+04-18 14:30:36.607 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:1813 - btif_dm_search_services_evt: index:8 uuid:df21fe2c-2515-4fdb-8886-f12c4d67927c
+04-18 14:30:36.607 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:1863 - btif_dm_search_services_evt: SDP search done for xx:xx:xx:xx:22:88
+04-18 14:30:36.607 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:1917 - btif_dm_search_services_evt: Bonding LE Audio sink - must wait for le services discovery to pass all services to java xx:xx:xx:xx:22:88
+04-18 14:30:36.607 I bt_bta_dm: bta_dm_search_cmpl: No BLE connection, processing classic results
+04-18 14:30:39.492 I BluetoothBondStateMachine: Bond State Change Intent:XX:XX:XX:XX:22:88 BOND_BONDING => BOND_BONDED
+04-18 14:30:39.993 I FastPair: BluetoothAudioPairer: BondedReceiver: handleBondStateChanged: device=XX:XX:XX:XX:22:88, state=12, reason=-2147483648
+Connectionpolicy is -1 for all profiles
+04-18 14:30:40.018 D CachedBluetoothDevice: No profiles. Maybe we will connect later for device XX:XX:XX:XX:22:88
+04-18 14:30:40.615 I btm_acl : disconnect_acl: Disconnecting peer:xx:xx:xx:xx:22:88 reason:HCI_ERR_PEER_USER comment:stack::l2cap::l2c_link::l2c_link_timeout All channels closed
+04-18 14:30:40.768 I bt_shim_hci: packages/modules/Bluetooth/system/main/shim/hci_layer.cc:304 - operator(): ISO disconnection from GD, handle: 0x0b, reason: 0x13
+// connectionPolicy=-1 -1是指失败
+04-18 14:30:40.777 V BluetoothDatabase: getProfileConnectionPolicy: device XX:XX:XX:XX:22:88 profile=A2DP, connectionPolicy=-1
+04-18 14:30:40.777 V BluetoothDatabase: getProfileConnectionPolicy: device XX:XX:XX:XX:22:88 profile=HEADSET, connectionPolicy=-1
+04-18 14:30:40.777 V BluetoothDatabase: getProfileConnectionPolicy: device XX:XX:XX:XX:22:88 profile=HID_HOST, connectionPolicy=-1
+04-18 14:30:40.777 V BluetoothDatabase: getProfileConnectionPolicy: device XX:XX:XX:XX:22:88 profile=PAN, connectionPolicy=-1
+04-18 14:30:40.777 V BluetoothDatabase: getProfileConnectionPolicy: device XX:XX:XX:XX:22:88 profile=HEARING_AID, connectionPolicy=-1
+04-18 14:30:40.777 V BluetoothDatabase: getProfileConnectionPolicy: device XX:XX:XX:XX:22:88 profile=HAP_CLIENT, connectionPolicy=-1
+04-18 14:30:40.777 V BluetoothDatabase: getProfileConnectionPolicy: device XX:XX:XX:XX:22:88 profile=VOLUME_CONTROL, connectionPolicy=-1
+04-18 14:30:40.777 V BluetoothDatabase: getProfileConnectionPolicy: device XX:XX:XX:XX:22:88 profile=CSIP_SET_COORDINATOR, connectionPolicy=-1
+04-18 14:30:40.777 V BluetoothDatabase: getProfileConnectionPolicy: device XX:XX:XX:XX:22:88 profile=LE_AUDIO, connectionPolicy=-1
+//created bond but never received UUIDs
+04-18 14:30:49.941 W FastPair: BluetoothAudioPairer: pair: created bond but never received UUIDs, attempting to continue.
+Device disconnected
+04-18 14:30:50.083 I bluetooth: disconnect: Device: xx:xx:xx:xx:22:88, cid: 0xffff
+04-18 14:30:50.086 I FastPair: Gatt connection with XX:XX:XX:XX:22:88 closed.
+04-18 14:30:50.097 D FastPairUtils: FastPair: Pairing finished with intent action: com.google.android.gms.nearby.discovery.ACTION_VALIDATOR_PAIR_PROGRESS
+04-18 14:30:51.083 I btm_acl : disconnect_acl: Disconnecting peer:xx:xx:xx:xx:22:88 reason:HCI_ERR_PEER_USER comment:stack::l2cap::l2c_link::l2c_link_timeout All channels closed
+04-18 14:30:51.134 I bt_shim_hci: packages/modules/Bluetooth/system/main/shim/hci_layer.cc:304 - operator(): ISO disconnection from GD, handle: 0x41, reason: 0x16
+04-18 14:30:51.135 I bluetooth: disconnect: Device: xx:xx:xx:xx:22:88, cid: 0xffff
+04-18 14:31:50.101 I BaseModuleTask: event=ModuleEvent{message=Pairing process error. Reason: Is connected: false
+04-18 14:31:50.102 D FeatureTestActivity: ModuleEvent{message=Pairing process error. Reason: Is connected: false
+04-18 14:31:50.133 I FastPair: BluetoothAudioPairer: unpair: device=XX:XX:XX:XX:22:88, methodName=removeBond
+04-18 14:31:50.134 I BluetoothDevice: removeBond() for device XX:XX:XX:XX:22:88 called by pid: 19745 tid: 26174
+04-18 14:31:50.146 I BluetoothBondStateMachine: Bond State Change Intent:XX:XX:XX:XX:22:88 BOND_BONDED => BOND_NONE
+
+
+
+
+正常的流程
+//Pairing starts
+04-18 10:50:49.219 I NearbyDiscovery: FastPairController: Validator: onValidatorConnectionRequested [CONTEXT service_id=265 ]
+04-18 10:50:49.221 I FastPair: FPDC: Starting to pair XX:XX:XX:XX:94:09: key[16], Preferences{gattOperationTimeoutSeconds=10, gattConnectionTimeoutSeconds=15, bluetoothToggleTimeoutSeconds=10, bluetoothToggleSleepSeconds=2,
+04-18 10:50:49.288 I bthal.activity: handle_ble_meta_event: LE Enhanced Connection Complete, conn_handle:041, conn_bda: XX:XX:55:0b:94:09
+04-18 10:50:49.412 I bt_bta_dm: bta_dm_acl_up: Acl connected peer:xx:xx:xx:xx:94:09 transport:BT_TRANSPORT_LE handle:65
+04-18 10:50:49.416 D BluetoothDatabase: getProfileConnectionPolicy: device XX:XX:XX:XX:94:09 is not in cache
+04-18 10:50:51.779 I BluetoothBondStateMachine: Bond State Change Intent:XX:XX:XX:XX:94:09 BOND_NONE => BOND_BONDING
+04-18 10:50:53.322 I bt_bta_dm: bta_dm_search_sm_execute: state:BTA_DM_SEARCH_IDLE, event:BTA_DM_API_DISCOVER_EVT[0x202]
+04-18 10:50:53.826 I bt_bta_dm: bta_dm_search_sm_execute: state:BTA_DM_DISCOVER_ACTIVE, event:BTA_DM_API_DISCOVER_EVT[0x202]
+
+//UUIDs discovered
+04-18 10:50:54.679 I bt_bta_dm: bta_dm_execute_queued_request: Start pending discovery
+04-18 10:50:54.679 I bt_bta_dm: bta_dm_search_sm_execute: state:BTA_DM_SEARCH_IDLE, event:BTA_DM_API_DISCOVER_EVT[0x202]
+04-18 10:50:54.680 I bt_bta_dm: bta_dm_discover_device: bta_dm_discovery: starting GATT discovery on xx:xx:xx:xx:94:09
+04-18 10:50:54.680 I bt_bta_dm: bta_dm_search_sm_execute: state:BTA_DM_DISCOVER_ACTIVE, event:BTA_DM_DISCOVERY_RESULT_EVT[0x207]
+04-18 10:50:54.680 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:1952 - btif_dm_search_services_evt: New GATT over LE UUIDs for xx:xx:xx:xx:94:09:
+04-18 10:50:54.680 D bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:1963 - btif_dm_search_services_evt: clearing pairing_cb
+04-18 10:50:54.680 D bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:1971 - btif_dm_search_services_evt: Scheduling conn params unlock for xx:xx:xx:xx:94:09
+04-18 10:50:54.680 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:1996 - btif_dm_search_services_evt: index:0 uuid:0000180f-0000-1000-8000-00805f9b34fb
+04-18 10:50:54.680 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:1996 - btif_dm_search_services_evt: index:1 uuid:00001844-0000-1000-8000-00805f9b34fb
+04-18 10:50:54.680 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:1996 - btif_dm_search_services_evt: index:2 uuid:0000184e-0000-1000-8000-00805f9b34fb
+04-18 10:50:54.681 I BluetoothAdapterService: sendUuidsInternal: Received service discovery UUIDs for device XX:XX:XX:XX:94:09
+04-18 10:50:54.681 D BluetoothAdapterService: sendUuidsInternal: index=0 uuid=00001101-0000-1000-8000-00805f9b34fb
+04-18 10:50:54.681 D BluetoothAdapterService: sendUuidsInternal: index=1 uuid=00001108-0000-1000-8000-00805f9b34fb
+04-18 10:50:54.681 D BluetoothAdapterService: sendUuidsInternal: index=2 uuid=0000110b-0000-1000-8000-00805f9b34fb
+04-18 10:50:54.681 D BluetoothAdapterService: sendUuidsInternal: index=3 uuid=0000110e-0000-1000-8000-00805f9b34fb
+04-18 10:50:54.681 D BluetoothAdapterService: sendUuidsInternal: index=4 uuid=0000111e-0000-1000-8000-00805f9b34fb
+04-18 10:50:54.681 D BluetoothAdapterService: sendUuidsInternal: index=5 uuid=0000180f-0000-1000-8000-00805f9b34fb
+04-18 10:50:54.681 D BluetoothAdapterService: sendUuidsInternal: index=6 uuid=00001844-0000-1000-8000-00805f9b34fb
+04-18 10:50:54.681 D BluetoothAdapterService: sendUuidsInternal: index=7 uuid=0000184e-0000-1000-8000-00805f9b34fb
+04-18 10:50:54.681 D BluetoothAdapterService: sendUuidsInternal: index=8 uuid=6a24eeab-4b65-4693-986b-3c26c352264f
+04-18 10:50:54.681 D BluetoothAdapterService: sendUuidsInternal: index=9 uuid=df21fe2c-2515-4fdb-8886-f12c4d67927c
+//Bonded
+04-18 10:50:54.701 I BluetoothBondStateMachine: Bond State Change Intent:XX:XX:XX:XX:94:09 BOND_BONDING => BOND_BONDED
+// profile=A2DP, connectionPolicy=0 0 是指连线成功
+04-18 10:50:54.737 V BluetoothDatabase: getProfileConnectionPolicy: device XX:XX:XX:XX:94:09 profile=A2DP, connectionPolicy=0
+04-18 10:50:54.737 V BluetoothDatabase: getProfileConnectionPolicy: device XX:XX:XX:XX:94:09 profile=A2DP, connectionPolicy=0
+04-18 10:50:54.738 V BluetoothDatabase: getProfileConnectionPolicy: device XX:XX:XX:XX:94:09 profile=HEADSET, connectionPolicy=0
+04-18 10:50:54.738 V BluetoothDatabase: getProfileConnectionPolicy: device XX:XX:XX:XX:94:09 profile=VOLUME_CONTROL, connectionPolicy=100
+04-18 10:50:54.738 V BluetoothDatabase: getProfileConnectionPolicy: device XX:XX:XX:XX:94:09 profile=LE_AUDIO, connectionPolicy=100
+//action.UUID is received and profiles connected
+04-18 10:50:54.751 I FastPair: BluetoothAudioPairer: BondedReceiver: handleUuids: device=XX:XX:XX:XX:94:09, uuids=[00001101-0000-1000-8000-00805f9b34fb, 00001108-0000-1000-8000-00805f9b34fb, 0000110b-0000-1000-8000-00805f9b34fb, 0000110e-0000-1000-8000-00805f9b34fb, 0000111e-0000-1000-8000-00805f9b34fb, 0000180f-0000-1000-8000-00805f9b34fb, 00001844-0000-1000-8000-00805f9b34fb, 0000184e-0000-1000-8000-00805f9b34fb, 6a24eeab-4b65-4693-986b-3c26c352264f, df21fe2c-2515-4fdb-8886-f12c4d67927c]
+04-18 10:50:54.785 I FastPair: BluetoothAudioPairer: AdditionalBondedReceiver: onReceive: action=android.bluetooth.device.action.UUID, device=XX:XX:XX:XX:94:09
+04-18 10:50:56.829 I BluetoothPhonePolicy: processProfileStateChanged, device=XX:XX:XX:XX:94:09, profile=LE_AUDIO, 1 -> 2
+04-18 10:50:56.849 I BluetoothPhonePolicy: processProfileStateChanged, device=XX:XX:XX:XX:94:09, profile=VOLUME_CONTROL, 1 -> 2
+//Classic ACL disconnected due no available profiles
+04-18 10:50:58.705 I btm_acl : disconnect_acl: Disconnecting peer:xx:xx:xx:xx:19:19 reason:HCI_ERR_PEER_USER comment:stack::l2cap::l2c_link::l2c_link_timeout All channels closed
+04-18 10:50:58.847 I bt_shim_hci: packages/modules/Bluetooth/system/main/shim/hci_layer.cc:304 - operator(): ISO disconnection from GD, handle: 0x0b, reason: 0x13
+// Bond removed
+04-18 10:51:06.883 I FastPair: BluetoothAudioPairer: unpair: device=XX:XX:XX:XX:94:09, methodName=removeBond
+04-18 10:51:06.883 I BluetoothDevice: removeBond() for device XX:XX:XX:XX:94:09 called by pid: 5098 tid: 17729
+04-18 10:51:06.888 I btm_acl : disconnect_acl: Disconnecting peer:xx:xx:xx:xx:94:09 reason:HCI_ERR_PEER_USER comment:stack::acl::btm_acl::btm_remove_acl
+04-18 10:51:06.896 I btm_acl : disconnect_acl: Disconnecting peer:xx:xx:xx:xx:94:09 reason:HCI_ERR_PEER_USER comment:bta::le_audio::client disconnect
+04-18 10:51:06.896 I BluetoothPhonePolicy: processProfileStateChanged, device=XX:XX:XX:XX:94:09, profile=VOLUME_CONTROL, 2 -> 3
+04-18 10:51:06.897 I BluetoothPhonePolicy: processProfileStateChanged, device=XX:XX:XX:XX:94:09, profile=LE_AUDIO, 2 -> 3
+04-18 10:51:06.901 I BluetoothBondStateMachine: Bond State Change Intent:XX:XX:XX:XX:94:09 BOND_BONDED => BOND_NONE
+04-18 10:51:06.912 I bt_shim_hci: packages/modules/Bluetooth/system/main/shim/hci_layer.cc:304 - operator(): ISO disconnection from GD, handle: 0x41, reason: 0x16
+
+
+//Conclusion:
+The uuids are not passed to upper layer.
+The build seems to be old and there have been changes in this module, please check if it is repro in the latest build.
+If reproducible, please provide bug report along with issue timestamp/video.
+Steps to enable full bt_snoop logs:
+1.Enable Developer options on the device.
+2.In the Developer options menu, change the Enable Bluetooth HCI snoop log setting to Enabled.
+3.In the "Logger buffer sizes", change the buffer size to "16M"(or highest possible).
+4.Enable Verbose Logging from Developer Options (Developer Options -> Enable Bluetooth Stack log -> Select Verbose)
+5.In the "Store logger data persistently on device" to "All log buffers"
+6.Restart your phone for logging to take effect
+7.Try reproducing your issue again and take a new bugreport |
+
+
+
diff --git a/1+GFPS_Finder如何抓取手机log.md b/1+GFPS_Finder如何抓取手机log.md
new file mode 100644
index 0000000..368e0c3
--- /dev/null
+++ b/1+GFPS_Finder如何抓取手机log.md
@@ -0,0 +1,70 @@
+# 1 GFPS/Finder如何抓取手机log
+
+
+
+
+
+- [1.请务必详细描述测试步骤及对应时间点，比如：](#id-1GFPS/Finder如何抓取手机log-1.请务必详细描述测试步骤及对应时间点，比如：)
+- [2.要同步抓取手机端log，耳机端log 以及测试失败截图](#id-1GFPS/Finder如何抓取手机log-2.要同步抓取手机端log，耳机端log以及测试失败截图)
+- [3.手机端log抓取步骤：](#id-1GFPS/Finder如何抓取手机log-3.手机端log抓取步骤：)
+
+
+
+#### **1.请务必详细描述测试步骤及对应时间点，比如：**
+
+**什么时间点开机；**
+
+**什么时间点进Pairing mode；**
+
+**什么时间点点击手机端的GFPS弹窗；**
+
+**什么时间点失败，手机UI失败原因是什么；**
+
+**......**
+
+#### **2.要同步抓取手机端log，耳机端log 以及测试失败截图**
+
+#### **3.手机端log抓取步骤：**
+
+**3.1.手机setting界面开启 Bluetooth HCI snoop log**
+
+****
+
+****
+
+**3.2.开始复现问题之前，adb 输入以下cmd:**
+
+**`cmd1: `**`adb`` ``logcat`` ``-G`` ``16M`
+
+**`cmd2:`**` ``adb shell setprop log``.``tag``.``NearbyMessages`` VERBOSE`\
+**`cmd3`**`: adb shell setprop log``.``tag``.``NearbyDiscovery`` VERBOSE`\
+**`cmd4:`**` ``adb shell setprop log``.``tag``.``FastPair`` VERBOSE`\
+
+
+**`cmd5:`**` ``adb shell device_config set_sync_disabled_for_tests persistent `
+
+**`cmd6:`**` ``adb shell device_config put bluetooth INIT_logging_debug_enabled_for_all true`
+
+**`cmd7:`**` ``adb shell device_config put bluetooth INIT_default_log_level_str LOG_VERBOSE`
+
+cmd8: adb logcat \> FILENAME.log
+
+**3.3.开始复现问题**
+
+\
+**3.4.问题复现之后,**
+
+Terminate the logcat by “Ctrl + C”
+
+ **adb输入：** **`adb bugreport 获取log信息`**\
+
+**`请提供bugreport-XXX.zip 文件 和 FILENAME.log文件`**
+
+\
+
+\
diff --git a/1+Initialize+fast+pair+service+failed.md b/1+Initialize+fast+pair+service+failed.md
new file mode 100644
index 0000000..e6e1d03
--- /dev/null
+++ b/1+Initialize+fast+pair+service+failed.md
@@ -0,0 +1,70 @@
+# 1 Initialize fast pair service failed
+
+Google一开始的答复是我们的测试账号没有加入test group, 但是我们的测试账号是已经加入到test group的
+
+后面樊晨换个手机测试又复现不到了，
+
+但是后面再测试 GG09(pixel4xl), GG27(pixel6) 复现概率也还是很高的，并且复现之后很长一段时间不能测试
+
+不知道是不是和Google网络有关系
+
+Google最后给的答复是和网络有关系：
+
+\
+
+Hi Danni,
+
+According to Comment #7, this issue appears unrelated to the Validator itself, but rather to the synchronization process with the GMS server-side.
+
+This is the first time I've encountered this specific kind of issue.\
+I recall you mentioning that it started suddenly during your testing.\
+Therefore, it might not be related to the factory reset scenario as described in b/409388435#comment6.
+
+You've only encountered this issue recently, right?\
+Is it possible you've made any recent changes to your Wi-Fi connection settings?\
+For example, a firewall setting?\
+I suspect such a change could be affecting the synchronization with the GMS server.
+
+\
+
+**最终找到原因是因为QC实验室的Google网络开了防火墙：**
+
+
+
+\
+
+\
+
+**对比试验，测试过程中遇到该问题后，**
+
+**在google-》所有服务-》设备中关闭自动保存设备选项后，大概率可以测试通过， **
+
+**Fast pair validator 测试的时候可以关掉， 但是手动测试必须打开**
+
+\
+
+\
+
+
+
+https://partnerissuetracker.corp.google.com/u/0/issues/444061781
+
+\
+
+\
+
+
+
+\
+
+
+
+\
+
+\
+
+\
+
+
+
+\
diff --git a/1+Pairing+process+error,+Reason_+Not+receive+UUID,+Is+connected_false.md b/1+Pairing+process+error,+Reason_+Not+receive+UUID,+Is+connected_false.md
new file mode 100644
index 0000000..0d7700d
--- /dev/null
+++ b/1+Pairing+process+error,+Reason_+Not+receive+UUID,+Is+connected_false.md
@@ -0,0 +1,79 @@
+# 1 Pairing process error, Reason: Not receive UUID, Is connected:false
+
+目前遇到以下两个原因，可以逐一排查：
+
+
+
+
+
+- [原因1：可能是手机系统蓝牙出了问题，setting界面 system\>reset options\>reset Bluetooth & wifi , 然后重启手机试试看](#id-1Pairingprocesserror,Reason:NotreceiveUUID,Isconnected:false-原因1：可能是手机系统蓝牙出了问题，setting界面system%3Eresetoptions%3EresetBluetooth&wifi,然后重启手机试试看)
+- [原因2：如果设备端不支援LEA，和支援LEA的手机对测，发现手机不连legacy profile， 需要打开 legacy CTKD LE 的功能](#id-1Pairingprocesserror,Reason:NotreceiveUUID,Isconnected:false-原因2：如果设备端不支援LEA，和支援LEA的手机对测，发现手机不连legacyprofile，需要打开legacyCTKDLE的功能)
+- [原因3： 如果设备端支援LEA，和不支援LEA的手机对测，发现手机不连legacy profile， 需要关闭 legacy CTKD LE 的功能，这个是Google的bug，google 后续会给出修正](#id-1Pairingprocesserror,Reason:NotreceiveUUID,Isconnected:false-原因3：如果设备端支援LEA，和不支援LEA的手机对测，发现手机不连legacyprofile，需要关闭legacyCTKDLE的功能，这个是Google的bug，google后续会给出修正)
+- [原因4：测试账号连的设备太多了，需要定期清除](#id-1Pairingprocesserror,Reason:NotreceiveUUID,Isconnected:false-原因4：测试账号连的设备太多了，需要定期清除)
+ - [4.1 setting界面清掉所有的配对信息 1 gfps/finder 如何清除配对信息 - BT_Market - WIKI](#id-1Pairingprocesserror,Reason:NotreceiveUUID,Isconnected:false-4.1setting界面清掉所有的配对信息1gfps/finder如何清除配对信息-BT_Market-WIKI)
+ - [4.2 Go to Settings \> Google \> All services \> Devices \> Saved devices：](#id-1Pairingprocesserror,Reason:NotreceiveUUID,Isconnected:false-4.2GotoSettings%3EGoogle%3EAllservices%3EDevices%3ESaveddevices：)
+ - [4.2.1 Toggle off Automatically saved devices](#id-1Pairingprocesserror,Reason:NotreceiveUUID,Isconnected:false-4.2.1ToggleoffAutomaticallysaveddevices)
+ - [4.2.2 Wait for about 3 hours, toggling on again.](#id-1Pairingprocesserror,Reason:NotreceiveUUID,Isconnected:false-4.2.2Waitforabout3hours,togglingonagain.)
+ - [4.2.3 Try to do the test again and see if this issue still happens.](#id-1Pairingprocesserror,Reason:NotreceiveUUID,Isconnected:false-4.2.3Trytodothetestagainandseeifthisissuestillhappens.)
+
+
+
+#### 原因1：可能是手机系统蓝牙出了问题，setting界面 system\>reset options\>reset Bluetooth & wifi , 然后重启手机试试看
+
+
+
+\
+
+#### 原因2：如果设备端不支援LEA，和支援LEA的手机对测，发现手机不连legacy profile， 需要打开 legacy CTKD LE 的功能
+
+1 GFPS legacy pair 搭配支援LEA手机不连 legacy profile(A2DP/HFP) - BT_Market - WIKI
+
+#### 原因3： 如果设备端支援LEA，和不支援LEA的手机对测，发现手机不连legacy profile， 需要关闭 legacy CTKD LE 的功能，这个是Google的bug，google 后续会给出修正
+
+4 pixel6(android 12) 不连A2DP - BT_Market - WIKI
+
+\
+
+\
+
+https://partnerissuetracker.corp.google.com/u/0/issues/443202640
+
+https://partnerissuetracker.corp.google.com/u/0/issues/445592517
+
+
+
+\
+
+手机没有来连legacy profile：
+
+Line 32281: 0002123 09-05#11:00:37.169 194 0009843.085 \[APP\] !\*\*connected: b2s, bd_addr 88::54::1F::10::0C::5F, profs 0x00000000\
+Line 34379: 0004221 09-05#11:00:38.529 169 0011221.541 \[ENGAGE\] connected: b2s, bd_addr 88::54::1F::10::0C::5F, profs 0x00000000\
+Line 34741: 0004583 09-05#11:00:38.607 203 0011285.575 \[ENGAGE\] connected: b2s, bd_addr 88::54::1F::10::0C::5F, profs 0x00000000\
+Line 35042: 0004883 09-05#11:00:38.700 095 0011358.903 \[ENGAGE\] connected: b2s, bd_addr 88::54::1F::10::0C::5F, profs 0x00000000
+
+\
+
+[BB2BUG-52175] [BB2][D-CUT][8763EKH][Harman][T530][v3.13.2.20+Test bin] Fast pair Validator APP测试，Personalized Name Update Test Fail - Jira
+
+[BB2BUG-52173] [BB2][D-CUT][8763EKH][Harman][T530][v3.13.2.20+Test bin] Fast pair Validator APP测试，Ringing A Device with classic profile connection Test Fail - Jira
+
+[BB2BUG-52194] [BB2][D-CUT][8763EKH][Harman][T530][v3.13.2.20+Test bin] Fast pair Validator APP测试，Key Based Request Fiags Reserved Bit verification Test Fail - Jira
+
+\
+
+#### 原因4：测试账号连的设备太多了，需要定期清除
+
+##### 4.1 setting界面清掉所有的配对信息 1 gfps/finder 如何清除配对信息 - BT_Market - WIKI
+
+##### **4.2 Go to `Settings > Google > All services > Devices > Saved devices：`**
+
+###### ** 4.2.1 Toggle off `Automatically saved devices`**
+
+###### ** 4.2.2 Wait for about 3 hours, toggling on again.**
+
+###### ** 4.2.3 Try to do the test again and see if this issue still happens.**
diff --git a/1+Pairing+process+error_+Reason_+Is+connected+false.md b/1+Pairing+process+error_+Reason_+Is+connected+false.md
new file mode 100644
index 0000000..d439ed5
--- /dev/null
+++ b/1+Pairing+process+error_+Reason_+Is+connected+false.md
@@ -0,0 +1,60 @@
+# 1 Pairing process error: Reason: Is connected false
+
+目前遇到以下两个原因，可以逐一排查：
+
+
+
+
+
+- [原因1：可能是手机系统蓝牙出了问题，setting界面 system\>reset options\>reset Bluetooth & wifi , 然后重启手机试试看](#id-1Pairingprocesserror:Reason:Isconnectedfalse-原因1：可能是手机系统蓝牙出了问题，setting界面system%3Eresetoptions%3EresetBluetooth&wifi,然后重启手机试试看)
+- [原因2：如果设备端不支援LEA，和支援LEA的手机对测，发现手机不连legacy profile， 需要打开 legacy CTKD LE 的功能](#id-1Pairingprocesserror:Reason:Isconnectedfalse-原因2：如果设备端不支援LEA，和支援LEA的手机对测，发现手机不连legacyprofile，需要打开legacyCTKDLE的功能)
+- [原因3： 如果设备端支援LEA，和不支援LEA的手机对测，发现手机不连legacy profile， 需要关闭 legacy CTKD LE 的功能，这个是Google的bug，google 后续会给出修正](#id-1Pairingprocesserror:Reason:Isconnectedfalse-原因3：如果设备端支援LEA，和不支援LEA的手机对测，发现手机不连legacyprofile，需要关闭legacyCTKDLE的功能，这个是Google的bug，google后续会给出修正)
+- [原因4：测试账号连的设备太多了，需要定期清除](#id-1Pairingprocesserror:Reason:Isconnectedfalse-原因4：测试账号连的设备太多了，需要定期清除)
+ - [4.1 setting界面清掉所有的配对信息 1 gfps/finder 如何清除配对信息 - BT_Market - WIKI](#id-1Pairingprocesserror:Reason:Isconnectedfalse-4.1setting界面清掉所有的配对信息1gfps/finder如何清除配对信息-BT_Market-WIKI)
+ - [4.2 Go to Settings \> Google \> All services \> Devices \> Saved devices：](#id-1Pairingprocesserror:Reason:Isconnectedfalse-4.2GotoSettings%3EGoogle%3EAllservices%3EDevices%3ESaveddevices：)
+ - [4.2.1 Toggle off Automatically saved devices](#id-1Pairingprocesserror:Reason:Isconnectedfalse-4.2.1ToggleoffAutomaticallysaveddevices)
+ - [4.2.2 Wait for about 3 hours, toggling on again.](#id-1Pairingprocesserror:Reason:Isconnectedfalse-4.2.2Waitforabout3hours,togglingonagain.)
+ - [4.2.3 Try to do the test again and see if this issue still happens.](#id-1Pairingprocesserror:Reason:Isconnectedfalse-4.2.3Trytodothetestagainandseeifthisissuestillhappens.)
+
+
+
+#### 原因1：可能是手机系统蓝牙出了问题，setting界面 system\>reset options\>reset Bluetooth & wifi , 然后重启手机试试看
+
+
+
+\
+
+#### 原因2：如果设备端不支援LEA，和支援LEA的手机对测，发现手机不连legacy profile， 需要打开 legacy CTKD LE 的功能
+
+1 GFPS legacy pair 搭配支援LEA手机不连 legacy profile(A2DP/HFP) - BT_Market - WIKI
+
+\
+
+
+
+\
+
+#### 原因3： 如果设备端支援LEA，和不支援LEA的手机对测，发现手机不连legacy profile， 需要关闭 legacy CTKD LE 的功能，这个是Google的bug，google 后续会给出修正
+
+4 pixel6(android 12) 不连A2DP - BT_Market - WIKI
+
+\
+
+#### 原因4：测试账号连的设备太多了，需要定期清除
+
+##### 4.1 setting界面清掉所有的配对信息 1 gfps/finder 如何清除配对信息 - BT_Market - WIKI
+
+##### **4.2 Go to `Settings > Google > All services > Devices > Saved devices：`**
+
+###### ** 4.2.1 Toggle off `Automatically saved devices`**
+
+###### ** 4.2.2 Wait for about 3 hours, toggling on again.**
+
+###### ** 4.2.3 Try to do the test again and see if this issue still happens.**
+
+\
diff --git a/1+Reason_+could+not+connected.md b/1+Reason_+could+not+connected.md
new file mode 100644
index 0000000..77ce34b
--- /dev/null
+++ b/1+Reason_+could+not+connected.md
@@ -0,0 +1,85 @@
+# 1 Reason: could not connected
+
+
+
+如果测试遇到该问题，麻烦贴一下上面的截图，并且请帮忙指出上图红色框里面对应的信息：
+
+1.Found by EID at xxxxxx， xxxxx对应的地址是什么
+
+2.手机端显示connecting对应的时间点
+
+3.手机端显示Test finished对应的时间点
+
+\
+
+log分析：
+
+
+
+截图位置1：
+
+"Found by AK at 48:48:6A:60:5A:F7"
+
+截图位置2：
+
+"Scaning by EID"
+
+"Found by EID at 7B:F8:BE:9E:64:E0"
+
+截图位置3：
+
+手机尝试connecting 7B:F8:BE:9E:64:E0
+
+但是此时耳机端因为 48:48:6A:60:5A:F7 这条link还没有断掉
+
+手机再尝试连7B:F8:BE:9E:64:E0的时候
+
+耳机端会认为link已经存在，直接拒绝这次连线
+
+导致手机端测试显示 "Could not connect"
+
+这个问题不是必现的
+
+\
+
+想请问是不是可以先断开48:48:6A:60:5A:F7这条link，确保手机和耳机的link断开之后, 再尝试执行截图位置2以及之后的操作？
+
+不然的话，
+
+如果在48:48:6A:60:5A:F7这条link 断开之后， 再scan 到7B:F8:BE:9E:64:E0 并且尝试创建BLE link 是没有问题的。
+
+如果在48:48:6A:60:5A:F7这条link 尚未断开之前 ，就scan 到7B:F8:BE:9E:64:E0 并且尝试创建BLE link， 就会遇到上面描述的问题。
+
+\
+
+log:
+
+0006294 03-28#14:18:17.958 199 0034334.679 \[HCI\] hci_if_confirm: buf 0x0020de33\
+0006295 03-28#14:18:17.958 200 0034334.980 \[HCI\] !!!hci_le_conn_cmpl_evt: handle 0x0015, peer_addr 75 F2 05 93 E8 62 connection already exist\
+0006296 03-28#14:18:17.958 201 0034335.049 \[HCI\] !\*\*hci_cmd_disconnect: handle 0x0015, cause 0x13\
+0006297 03-28#14:18:17.958 202 0034335.183 \[HCI\] hci_if_write: buf 0x00407397, len 7\
+0006298 03-28#14:18:17.958 203 0034335.299 File\[011\], Line\[0239\] \[MODULE_LOWERSTACK\] \[clk:0x0001acd2\]--\>HCI_CMD:opcode:0406 len:3, 15001300-00407440-00130011-000d0004-00800000\
+0006299 03-28#14:18:17.958 204 0034335.343 File\[011\], Line\[0789\] \[MODULE_LOWERSTACK\] DISCONNECT OPCODE\
+0006300 03-28#14:18:17.958 205 0034335.390 File\[201\], Line\[2466\] \[MODULE_LOWERSTACK\] \[LL\] Disconnect Cmd: conn_handle 21 entry 10 reason 13
+
+COM3_btsnoop_2023-03-28_14-17-41.cfa
+
+COM3_2023-03-28_14-17-31.log
+
+air_log_could_not_connect.btt
+
+bugreport-taimen-RP1A.201005.004.A1-2023-03-28-14-19-27.zip
+
+这个问题需要咨询google：
+
+from google:
+
+Thanks for reporting. I found a race condition which can lead to this result. I'll prepare a fix, but since it does not reproduce on devices that we have, and to save some time, I would like to share an APK with the fix with you to verify it resolves the issue.
+
+Can you provide a Google account on which I can share the APK once it is ready?
+
+google 提供的新的apk: validator_realtek_diag.apk
+
+Alice Zhou(周丽) 麻烦用这个apk压测试试看，是否还能复现到这个问题
+
+\
diff --git a/1+gfps_finder+如何清除配对信息.md b/1+gfps_finder+如何清除配对信息.md
new file mode 100644
index 0000000..b41493e
--- /dev/null
+++ b/1+gfps_finder+如何清除配对信息.md
@@ -0,0 +1,33 @@
+# 1 gfps/finder 如何清除配对信息
+
+**耳机端：**
+
+需要做factory reset
+
+\
+
+**手机端：**
+
+1.查看手机setting-》connected devices 里面是否有配对信息，如果有请清掉对应的配对信息
+
+- Forget the connected device on Bluetooth setting.
+
+2.查看手机setting-》google-》Devices&sharing-\>Devices-\>Saved devices 里面是否有配对信息，如果有也请清掉
+
+- Go to **Settings \> Google \> Devices & sharing (or Device connections) \> Devices \> Saved devices**. Turn off the 'Automatically save devices' and back to the previous page then Turn On the 'Automatically save devices' again and you will see the below result appear 'No devices'.
+
+3.Find my device APP里面查看是否存在已经配对过的耳机设备，如果有请remove掉对应的耳机设备，可以参考[Test case4：Unprovisioning 测试视频](/pages/viewpage.action?pageId=387094681)
+
+4.重启手机
+
+ 
BEE3PLUSRD-231 - \[Bee3+\]\[GFPS\]initial pairing流程不正确问题 Closed
+
+\
+
+**Note：**
+
+测试手机归还QC之前务必先执行上面的操作，并且setting界面移除测试账号
+
+\
+
+\
diff --git a/1+legacy+CTKD+LE+功能打开之后+provision+fail.md b/1+legacy+CTKD+LE+功能打开之后+provision+fail.md
new file mode 100644
index 0000000..e97ba8e
--- /dev/null
+++ b/1+legacy+CTKD+LE+功能打开之后+provision+fail.md
@@ -0,0 +1,5 @@
+# 1 legacy CTKD LE 功能打开之后 provision fail
+
+[BB2BUG-50237] [BB2][RTL8763ESH/ROM][GMI][沃莱特][Harman][T530] [finder] 738：[Finder]Headphones cannot be added to the Finder APP - Jira
+
+
diff --git a/1+mcu+cfg+tool+设置的public+key+其实是没有起作用的，+后面会考虑隐藏起来.md b/1+mcu+cfg+tool+设置的public+key+其实是没有起作用的，+后面会考虑隐藏起来.md
new file mode 100644
index 0000000..9b3cc97
--- /dev/null
+++ b/1+mcu+cfg+tool+设置的public+key+其实是没有起作用的，+后面会考虑隐藏起来.md
@@ -0,0 +1,33 @@
+# 1 mcu cfg tool 设置的public key 其实是没有起作用的， 后面会考虑隐藏起来
+
+GFPS 加解密过程中， public key是手机端提供的， 每次配对 手机端提供的public key好像都是不一样的
+
+private key是我们mcu cfg tool里面设置的，每次配对private key是一样的
+
+
+
+
+//第一次配对
+[APP] !**gfps_gen_aes_key:public key F3 C9 0F CB A6 4B 12 A9 57 F8 C0 BA 39 2C E4 81 FF 13 E2 4D DA 88 BB 1E 02 31 AD 5F E2 A6 AD 7A 52 BE F8 89 A9 47 79 54 39 68 20 AA 6E CD 0C 83 4B 2E CF 57 86 18 FB 20 7D 92 21 09 AA 70 86 E4,
+ private key 69 02 DC F8 E1 00 E7 00 38 A2 7C A1 FF A8 AD 7C 17 2D 25 D2 B0 92 05 97 81 E7 34 FC A7 BF DB F8, ECDH key 98 2B 33 E0 5B 58 18 B9 90 BF BE A4 EC 1F 36 72 26 06 0F 00 1F FB 1C 8D 48 35 8A B9 B5 19 4B 61
+//第二次配对
+[APP] !**gfps_gen_aes_key:public key 78 6F 6D AE 59 A6 36 26 F5 B3 9C 42 11 16 09 AB 9C 43 8A F2 82 F7 0D 70 39 2A F0 81 61 17 40 FC C2 FA 2F F1 78 72 01 3A 3D F9 92 B5 D7 3C 23 FF 88 6A 48 F8 2A EF 62 A4 A1 04 D2 C6 E5 93 A2 63,
+ private key 69 02 DC F8 E1 00 E7 00 38 A2 7C A1 FF A8 AD 7C 17 2D 25 D2 B0 92 05 97 81 E7 34 FC A7 BF DB F8, ECDH key 82 A2 3A B7 E4 D3 14 17 94 23 B3 20 F0 58 FD AB 69 73 E1 C3 3A B2 DB 6B F3 8A 6E 86 35 5A 74 D4
+//第三次配对
+[APP] !**gfps_gen_aes_key:public key C1 44 1F 26 05 C5 85 6A 60 B1 D8 10 E5 0B A1 9F B4 2F 3E A2 AB 9F 81 D3 44 DA B2 EB 3A D3 D5 6E A2 9A BF B7 D1 93 18 81 B6 81 0E 4D FD 10 49 4C B7 14 3A F7 81 B9 80 5C 1E B1 73 E6 3F 58 6C 5D,
+ private key 69 02 DC F8 E1 00 E7 00 38 A2 7C A1 FF A8 AD 7C 17 2D 25 D2 B0 92 05 97 81 E7 34 FC A7 BF DB F8, ECDH key 33 86 25 F3 75 4A 59 3D B6 C6 42 3B DD 30 E9 96 F9 65 7B 40 6F 43 C4 92 BE A3 6E 16 8E FC BA 4D
+//第四次配对
+[APP] !**gfps_gen_aes_key:public key B4 8D B2 CD 73 E2 D4 2C 25 D8 9B 08 02 F0 86 5E 59 AF F3 86 29 B5 D3 84 9D AA 0E 94 AB CA 23 54 AB F1 BB 12 20 B8 3F B7 7D FA 02 9E B7 54 D4 52 FA 57 3D 50 49 35 A7 8D DE FB B3 58 AC EA E7 6B,
+ private key 69 02 DC F8 E1 00 E7 00 38 A2 7C A1 FF A8 AD 7C 17 2D 25 D2 B0 92 05 97 81 E7 34 FC A7 BF DB F8, ECDH key CF E1 AD F6 1A 7D CD 89 7D 0B C5 6F 7F CE 85 9B 2A 37 67 72 2E A6 C8 52 41 24 A3 A2 EC E8 71 B3
+
+//第五次配对
+[APP] !**gfps_gen_aes_key:public key 5B E7 FA B5 72 B1 0E 51 F3 A1 B9 90 63 27 3E E9 CC 59 9E 1C 45 7C 1A C0 91 EF 9F 05 06 48 E7 15 16 D1 FD 7F E9 8A E2 29 4B F1 A7 FA EF 83 11 C0 9C 85 91 FA 6E 53 20 FF 2F 4B 88 7B 42 08 11 3B,
+ private key 69 02 DC F8 E1 00 E7 00 38 A2 7C A1 FF A8 AD 7C 17 2D 25 D2 B0 92 05 97 81 E7 34 FC A7 BF DB F8, ECDH key E1 54 99 06 25 3E 0D D3 AC 05 1E 79 B9 E2 07 B6 BB A3 35 CA 3B FD 29 90 26 96 E5 02 20 E2 8C 1E
+
+
+//第六次配对
+[APP] !**gfps_gen_aes_key:public key 1F 6D EB 32 DE DC 1F 30 2E 2C 15 0C 99 62 67 B7 9D F4 12 48 B1 0A 8E 36 5E 5A FC F4 79 AF 19 F7 CC E6 72 55 F9 F2 8F 09 13 5F BA 87 C3 64 96 2D 54 D7 7A 00 55 4A FB 1F 0E 4C F4 25 82 97 F3 7C,
+ private key 69 02 DC F8 E1 00 E7 00 38 A2 7C A1 FF A8 AD 7C 17 2D 25 D2 B0 92 05 97 81 E7 34 FC A7 BF DB F8, ECDH key 96 83 AB B5 70 46 4C 21 EB 22 4D B4 86 73 23 3A B4 D2 54 73 C0 AD 29 59 A2 A7 22 2E 78 1C 12 89 |
+
+
+
diff --git a/1+客户使用GFPS流程.md b/1+客户使用GFPS流程.md
new file mode 100644
index 0000000..8a79424
--- /dev/null
+++ b/1+客户使用GFPS流程.md
@@ -0,0 +1,109 @@
+# 1 客户使用GFPS流程
+
+1\. 客户需要阅读GFPS spec 了解GFPS是什么以及有哪些features
+
+The Google Fast Pair Service | Google for Developers
+
+https://developers.google.com/nearby/fast-pair/specifications/introduction
+
+Partner Integration Guide for Google's Find Hub Network | Fast Pair | Google for Developers
+
+Find Hub Network Accessory Specification | Fast Pair | Google for Developers
+
+有關於 GFPS 的認證流程請參照: (此流程是 RTK協助客戶 註冊 Google project kickoff 以及 認證流程介紹)
+
+
+
+
+| Date |
+File |
+
+ |
+
+
+| 25/11/24 |
+ |
+
+ |
+
+
+| 25/12/18 |
+ |
+
+ |
+
+
+
+
+\
+
+\
+
+2\. 客户至少要注册三个google账号 xxx_test_account1@gmail.com，xxx_test_account2@gmail.com, xxx_test_account3@gmail.com, 如果是le only设备并且只需要find hub功能，可以只注册一个Google账号。
+
+ 另外建议客户注册一个专门的临时测试账号提供给Realtek qc 内部测试用，比如 xxx_customer_for_realtek_test@gmail.com 并且要在这个测试账号下注册一个临时的测试model id,
+
+ Realtek QC 会帮忙用这个临时测试账号和这个临时测试账号下的model id过完整的GFPS 认证相关的测项
+
+\
+
+3\. 客户需要自己注册model id https://developers.google.com/nearby/devices/, 注意model id是和Google账号绑定的。如果客户不清楚怎么注册，FAE可以参考这个wiki 协助客户注册 model_id 注册 - BT_Market - WIKI
+
+\
+
+4\. 客户需要将注册的model id 信息提供给 Realtek FAE， FAE需要请 YT(YingTsung (YT) Lin) 让google帮忙激活该model id 并且开案, 具体开案需要提供哪些信息，请咨询YT(YingTsung (YT) Lin) .
+
+ 另外客户需要将所有注册的Google账号提供给 Realtek FAE， Realtek FAE需要请YT(YingTsung (YT) Lin)联系Google， 让Google把客户的Google账号加入到Google GFPS/Finder/SASS 的 Test group
+
+ for example：
+
+ xxx_test_account1@gmail.com，model id: xxxxxx （这个账号由客户自己管理）
+
+xxx_test_account2@gmail.com, model id: xxxxxx （这个账号由客户自己管理）
+
+xxx_test_account3@gmail.com, model id: xxxxxx （这个账号由客户自己管理）
+
+xxx_customer_for_realtek_test@gmail.com, model id: xxxxxx（这个是客户注册的临时测试账号给Realtek QC内部测试用，请FAE提醒客户不要暴露私有信息, 产品量产之后，客户可以将这个账号注销）
+
+\
+
+5\. google 开案成功之后，YT(YingTsung (YT) Lin) 会通知Realtek FAE，Realtek FAE 通知客户可以使用注册的model id信息了
+
+\
+
+6\. Realtek FAE协助客户在mcu cfg tool 里面配置GFPS相关信息 [mcu cfg tool中 GFPS 各配置项的含义](/pages/viewpage.action?pageId=158870786)
+
+\
+
+7\. 请客户参考 https://developers.google.com/nearby/fast-pair/certification-process熟悉GFPS认证流程
+
+ Device Feature Requirements 请参考以下文档：
+
+ Hearable devcie 请参考： Fast Pair | Google for Developers
+
+ Locator tags 请参考：Fast Pair | Google for Developers
+
+\
+
+8\. 请客户参考GFPS认证spec 进行测试:
+
+ GFPS认证请参考：https://developers.google.com/nearby/fast-pair/fast-pair-certification-guideline，
+
+ SASS认证请参考：Audio Switch Certification Guidelines | Fast Pair | Google for Developers
+
+ Finder/Find Hub认证请参考：Find Hub Network Certification Guidelines | Fast Pair | Google for Developers
+
+\
+
+9\. 请Realtek FAE指导客户参考这个wiki 进行测试： 1 GFPS Test flow - BT_Market - WIKI
+
+\
+
+10\. 客户端所有的测试都PASS之后，需要过GFPS相关认证之前， 客户需要提交测试结果(即self test report)给 Realtek FAE， Realtek FAE 找 YT(YingTsung (YT) Lin) 讨论认证相关信息
+
+\
diff --git a/1+手机端显示+“Could+not+authenticate”.md b/1+手机端显示+“Could+not+authenticate”.md
new file mode 100644
index 0000000..d610e3c
--- /dev/null
+++ b/1+手机端显示+“Could+not+authenticate”.md
@@ -0,0 +1,9 @@
+# 1 手机端显示 “Could not authenticate”
+
+
+
+手机端setting 界面删掉配对信息，之后耳机端也要做factory reset 不然finder功能用不起来。
+
+每个测项测试之前手机端都会先清掉配对信息，所以每个测项测试之前耳机端都要主动做factory reset
+
+[8 手机端清掉配对信息之后，耳机端也要做factory reset，不然finder功能用不起来](/pages/viewpage.action?pageId=350190807)
diff --git a/1+认证实验室要求认证期间弹窗的图片和名字需要隐藏.md b/1+认证实验室要求认证期间弹窗的图片和名字需要隐藏.md
new file mode 100644
index 0000000..11f297c
--- /dev/null
+++ b/1+认证实验室要求认证期间弹窗的图片和名字需要隐藏.md
@@ -0,0 +1,25 @@
+# 1 认证实验室要求认证期间弹窗的图片和名字需要隐藏
+
+[BB2BUG-53293] [BB2][RTL8763ESE][Amazon/OSM][头戴立体声耳机][OSHA-67]Pegatron GFPS认证实验室反馈认证期间弹窗的图片和名字需要隐藏 - Jira
+
+和注册model id的时候填写的 Public Date有关系：
+
+
+
+\
+
+\
+
+如果UI信息和上面描述的不一样，手机可以尝试做以下绿色框里面的操作:
+
+
+
+\
+
+需要注意的是如果model id的Approval状态是 DRAFT, 在拿到认证之前需要开启debug mode：
+
+
+
+
+
+\
diff --git a/1-+SUT+A打开蓝牙关闭飞行模式后，SUT+B依然能搜索到设备.md b/1-+SUT+A打开蓝牙关闭飞行模式后，SUT+B依然能搜索到设备.md
new file mode 100644
index 0000000..df9bb15
--- /dev/null
+++ b/1-+SUT+A打开蓝牙关闭飞行模式后，SUT+B依然能搜索到设备.md
@@ -0,0 +1,9 @@
+# 1- SUT A打开蓝牙关闭飞行模式后，SUT B依然能搜索到设备
+
+[BB2BUG-47667] [BB2][RTL8763ESH/ROM][GMI][沃莱特][Harman][T135]Finder测试，SUT A中耳机打开Activate Unwanted Tracking mode，SUT B搜索到设备，SUT A打开蓝牙关闭飞行模式后，SUT B依然能搜索到设备 - Jira
+
+SUT A是owner phone
+
+SUT B是non owner phone
+
+
diff --git a/1.+Google+test+group.md b/1.+Google+test+group.md
new file mode 100644
index 0000000..ee1a9ba
--- /dev/null
+++ b/1.+Google+test+group.md
@@ -0,0 +1,32 @@
+# 1. Google test group
+
+客户需要关注的是以下红色框里面的test group：
+
+
+
+\
+
+\
+
+\
+
+Realtek全部test group 如下：
+
+
+
+\
+Fast Pair **launched** feature --\> should join the FastPairPartnerTest group\
+Fast Pair **un-released** feature --\> should join the Fast Pair external group
+
+Tony.YS Liu,\
+
+looks like there is a typo, correction is:\
+Fast Pair **un-launched** feature --\> should join the Fast Pair external group\
+So, for your customer and production users, they don't need to join Fast Pair external group for using GFPS legacy/le pairing feature.
+
+Tony.YS Liu,\
+
+However, IIUC, for Find Hub feature, before the Provider got certified, you and your customers need to join the FH test group to verify the Provider's Find Hub implementation.\
+Please work with the Find Hub team for this, thanks!
+
+\
diff --git a/1.+initial+pair+一直显示connecting.md b/1.+initial+pair+一直显示connecting.md
new file mode 100644
index 0000000..2e3f01a
--- /dev/null
+++ b/1.+initial+pair+一直显示connecting.md
@@ -0,0 +1,7 @@
+# 1. initial pair 一直显示connecting
+
+可能是Google 账号的问题， 可以尝试换个账号再试试看 realsilbt8888的账号没办法用来做手动测试
+
+
+
+\
diff --git a/1.+如何从手机+setting+界面判断+LEA_A2DP_HFP有connected.md b/1.+如何从手机+setting+界面判断+LEA_A2DP_HFP有connected.md
new file mode 100644
index 0000000..8bb0606
--- /dev/null
+++ b/1.+如何从手机+setting+界面判断+LEA_A2DP_HFP有connected.md
@@ -0,0 +1,11 @@
+# 1. 如何从手机 setting 界面判断 LEA/A2DP/HFP有connected
+
+from google:
+
+The LEA connected in the Settings UI when this "LE Audio" toggle on .
+
+
+
+if you turn off the "LE Audio" toggle off. you will see the options for A2DP/HFP , that means it connected to A2DP/HFP.
+
+
diff --git a/1.+手机端点击+ring+stop，耳机端并未停止响铃.md b/1.+手机端点击+ring+stop，耳机端并未停止响铃.md
new file mode 100644
index 0000000..e120e06
--- /dev/null
+++ b/1.+手机端点击+ring+stop，耳机端并未停止响铃.md
@@ -0,0 +1,73 @@
+# 1. 手机端点击 ring stop，耳机端并未停止响铃
+
+ BB2BUG-18476 - \[BB2\]\[8773ESL\]\[v3.13.0.7\]\[GFPS\]\[LE Audio\]Find device响铃时，有时候停止响铃失败 In Progress
+
+手机端点击 ring stop，耳机端并未停止响铃
+
+原因是：
+
+手机端有尝试发送停止响铃的cmd 给耳机端，
+
+但是因为我们耳机端没有发credit给手机，
+
+导致手机端认为耳机端没有剩余的credit了，
+
+进而手机端没办法发送停止响铃的cmd到耳机端，
+
+\
+
+From google：
+
+\
+hi tony:\
+11：27：45 pair\
+11：27：55 connect LE Audio\
+11：28：07 Ring Left，11：28：14 Mute Left，sucess\
+11：28：23 Ring Right，11：28：27 Mute Right，Mute Right fail
+
+Line 135172: 07-13 11:28:26.957 10166 8442 8442 I FastPair: FindDevice: Sending ring event, pre left false, pre right true
+
+\
+//it seems fast pair has already send mute right cmd\
+Line 135173: 07-13 11:28:26.957 10166 8442 8442 I FastPair: FindDevice: Sending ring event, left false, right false\
+Line 135174: 07-13 11:28:26.958 10166 2946 4749 I NearbyDiscovery: FastPair: send ring, device=XX:XX:XX:XX:65:0C \[CONTEXT service_id=265 \]
+
+however in phone's hci log, 11：28：27 we do not see mute right cmd
+
+it seems that after 11:28:22.960783, FP cannot send any message via L2CAP.
+
+LE L2cap channel is not disconnected in the log.
+
+Can you help to see why the PSM cannot be found? thanks
+
+\
+
+Hey Danni,
+
+I filter the HCI with btl2cap.psm == 0x0080, Seeker can receive the battery info from the L2cap event stream,
+
+but the problem here is Seeker cannot send message to the Provider.
+
+\
+It looks like a similar issue (google internal ticket: b/158958522#comment12) when we worked with realtek on ringing through RFCOMM.
+
+From wade_li@realsil.com.cn
on Jul 2020.
+
+> I check the differences with the HCI snoop log again. And find that phone has no RFC credits continue to send command.
+>
+> Actually, I will try to send credits after received RFC data.
+
+Could you help to see if the issue can be fixed when Provider handles the credit correctly?
+
+Thanks!
+
+\
+
+hi tony:\
+The reason is Provider do not send credit to seeker, we have already fix this issue and test sucess.\
+\
+we have another problem：some times seeker do not create LE L2CAP channel, I will create another jira, thanks
+
+\
+
+\
diff --git a/1.1+Project+工程enable对应功能.md b/1.1+Project+工程enable对应功能.md
new file mode 100644
index 0000000..4eefc74
--- /dev/null
+++ b/1.1+Project+工程enable对应功能.md
@@ -0,0 +1,43 @@
+# 1.1 Project 工程enable对应功能
+
+app_flags.h 里面找到 CONFIG_REALTEK_GFPS_XXX 相关的宏并按照以下信息配置：
+
+\#define CONFIG_REALTEK_GFPS_FEATURE_SUPPORT 1\
+\#define CONFIG_REALTEK_GFPS_LE_DEVICE_SUPPORT (0 && CONFIG_REALTEK_GFPS_FEATURE_SUPPORT)\
+\#define CONFIG_REALTEK_GFPS_SASS_SUPPORT (0 && CONFIG_REALTEK_GFPS_FEATURE_SUPPORT)\
+\#define CONFIG_REALTEK_GFPS_FINDER_SUPPORT (0 && CONFIG_REALTEK_GFPS_FEATURE_SUPPORT)
+
+GFPS依赖的其他的模块：
+
+\#if CONFIG_REALTEK_GFPS_FEATURE_SUPPORT\
+\#undef F_APP_RWS_BLE_USE_RPA_SUPPORT\
+\#define F_APP_RWS_BLE_USE_RPA_SUPPORT 1
+
+\#undef F_APP_SC_KEY_DERIVE_SUPPORT\
+\#define F_APP_SC_KEY_DERIVE_SUPPORT 1\
+\#endif
+
+\
+
+Note:
+
+有的IC宏的名字是GFPS_XXX, app_flags.h 里面找到 GFPS_XXX 相关的宏并按照以下信息配置：
+
+\#define GFPS_FEATURE_SUPPORT 1\
+\#define GFPS_LE_DEVICE_SUPPORT (0 && GFPS_FEATURE_SUPPORT)\
+\#define GFPS_SASS_SUPPORT (0 && GFPS_FEATURE_SUPPORT)\
+\#define GFPS_FINDER_SUPPORT (0 && GFPS_FEATURE_SUPPORT)
+
+GFPS依赖的其他的模块：
+
+\#if GFPS_FEATURE_SUPPORT\
+\#undef F_APP_RWS_BLE_USE_RPA_SUPPORT\
+\#define F_APP_RWS_BLE_USE_RPA_SUPPORT 1
+
+\#undef F_APP_SC_KEY_DERIVE_SUPPORT\
+\#define F_APP_SC_KEY_DERIVE_SUPPORT 1\
+\#endif
+
+\
+
+\
diff --git a/1.2+测试环境搭建.md b/1.2+测试环境搭建.md
index 3861e84..1ab1958 100644
--- a/1.2+测试环境搭建.md
+++ b/1.2+测试环境搭建.md
@@ -1,4 +1 @@
-# 1.2 测试环境搭建 {#测试环境搭建}
-
-::: {.Section1}
-:::
+# 1.2 测试环境搭建
diff --git a/1.2.1+设备端环境搭建.md b/1.2.1+设备端环境搭建.md
index 30f6b1f..c61cc87 100644
--- a/1.2.1+设备端环境搭建.md
+++ b/1.2.1+设备端环境搭建.md
@@ -1,14 +1,14 @@
-# 1.2.1 设备端环境搭建 {#设备端环境搭建}
+# 1.2.1 设备端环境搭建
-:::: {.Section1}
-``{=html}
+/**/
+
+
-::: {.toc-macro .rbtoc1777598888652}
- [1 MCUConfigTool 配置](#id-1.2.1设备端环境搭建-1MCUConfigTool配置)
- [1.1 General 页面 : 不勾选 Enable auto power off, 不勾选 Enable pairing timeout](#id-1.2.1设备端环境搭建-1.1General页面:不勾选Enableautopoweroff,不勾选Enablepairingtimeout)
- [1.2 General 页面 : Discoverable in standby mode 设置成disable。强制要求必须修改](#id-1.2.1设备端环境搭建-1.2General页面:Discoverableinstandbymode设置成disable。强制要求必须修改)
@@ -33,55 +33,56 @@ div.rbtoc1777598888652 li {margin-left: 0px;padding-left: 0px;}
- [2.3.1 开关盒操作步骤](#id-1.2.1设备端环境搭建-2.3.1开关盒操作步骤)
- [2.3.2 HUN显示测试](#id-1.2.1设备端环境搭建-2.3.2HUN显示测试)
- [2.3.3 demo rcfg， 里面有model id信息，不可以直接开给客户！！！](#id-1.2.1设备端环境搭建-2.3.3demorcfg，里面有modelid信息，不可以直接开给客户！！！)
-:::
-### 1 MCUConfigTool 配置 {#id-1.2.1设备端环境搭建-1MCUConfigTool配置}
+
-#### 1.1 General 页面 : 不勾选 Enable auto power off, 不勾选 Enable pairing timeout {#id-1.2.1设备端环境搭建-1.1General页面:不勾选Enableautopoweroff,不勾选Enablepairingtimeout}
+### 1 MCUConfigTool 配置
-**Note**:
+#### 1.1 General 页面 : 不勾选 Enable auto power off, 不勾选 Enable pairing timeout
-修改为了便于GFPS测试，GFPS 测试的时候或者是过认证的时候需要修改， **量产时可以考虑不修改。**
+**Note**:
-
+修改为了便于GFPS测试，GFPS 测试的时候或者是过认证的时候需要修改， **量产时可以考虑不修改。**
-#### 1.2 General 页面 : Discoverable in standby mode 设置成disable。**强制要求必须修改** {#id-1.2.1设备端环境搭建-1.2General页面:Discoverableinstandbymode设置成disable。强制要求必须修改}
+
-**Note**:
+#### 1.2 General 页面 : Discoverable in standby mode 设置成disable。**强制要求必须修改**
+
+**Note**:
GFPS 耳机第一次和一只手机配对成功之后(initial pairing 成功)，就会进入 subsequent pairing mode。
所以initial pairing 成功之后，不管耳机是进入idle mode 还是进入connectable mode(multilink 支持)，都不应该再设置成discoverable。
-
+
-#### 1.3 General 页面: 勾选 Non-discoverable when linkback **强制要求必须修改** {#id-1.2.1设备端环境搭建-1.3General页面:勾选Non-discoverablewhenlinkback强制要求必须修改}
+#### 1.3 General 页面: 勾选 Non-discoverable when linkback **强制要求必须修改**
-linkback模式下DUT不应该discoverable，不然手机端会一直弹配对窗口。
+linkback模式下DUT不应该discoverable，不然手机端会一直弹配对窗口。
\
-
+
-#### 1.4 勾选Multi-link support, 并且不要勾选 Enter pairing state while only available device is connected **强制要求必须修改** {#id-1.2.1设备端环境搭建-1.4勾选Multi-linksupport,并且不要勾选Enterpairingstatewhileonlyavailabledeviceisconnected强制要求必须修改}
+#### 1.4 勾选Multi-link support, 并且不要勾选 Enter pairing state while only available device is connected **强制要求必须修改**
-下面红框里的**不可以勾选 **不然battery HUN测试可能测不过， ** [[BBPRO2BUG-21515](https://jira.realtek.com/browse/BBPRO2BUG-21515){.jira-issue-key} - Getting issue details\... STATUS ]{.jira-issue jira-key="BBPRO2BUG-21515" client-id="SINGLE_2d885edc-676b-3349-9548-fe5648c9d8cd_948641792_2c9082e76519d09101657ff5cfb3003b"}**
+下面红框里的**不可以勾选 **不然battery HUN测试可能测不过， ** BBPRO2BUG-21515 - Getting issue details... STATUS **
-
+
-#### 1.5 Third Party页面配置GFPS参数 {#id-1.2.1设备端环境搭建-1.5ThirdParty页面配置GFPS参数}
+#### 1.5 Third Party页面配置GFPS参数
-在Third Party页面配置GFPS参数，详细信息参考 [mcu cfg tool中 GFPS 各配置项的含义 - BT_Market - WIKI](https://wiki.realtek.com/pages/viewpage.action?pageId=158870786){rel="nofollow"}
+在Third Party页面配置GFPS参数，详细信息参考 mcu cfg tool中 GFPS 各配置项的含义 - BT_Market - WIKI
-
+
下面是RTK已通过认证的Module ID
[认证结果及认证通过的model_id 和key](/pages/viewpage.action?pageId=204620689)
-#### 1.6 配置GFPS findme voice prompt tone {#id-1.2.1设备端环境搭建-1.6配置GFPSfindmevoiceprompttone}
+#### 1.6 配置GFPS findme voice prompt tone
-[gfps_findme.wav](#){.unresolved}
+gfps_findme.wav
自行选择wav文件作为findme vp tone，
@@ -91,7 +92,7 @@ wav文件名称可以自行修改，放入MCU config tool vp目录，
如下图所示：
-
+
打开MCU config tool开始配置findme tone，
@@ -101,84 +102,84 @@ wav文件名称可以自行修改，放入MCU config tool vp目录，
如下图所示：
-
+
-
+
-#### 1.7 保存新生成的 APP UI Parameter File 和 System Config File {#id-1.2.1设备端环境搭建-1.7保存新生成的APPUIParameterFile和SystemConfigFile}
+#### 1.7 保存新生成的 APP UI Parameter File 和 System Config File
-#### **1.8 Note** {#id-1.2.1设备端环境搭建-1.8Note}
+#### **1.8 Note**
-##### 1.建议把BD Address和Device Name也改一下 {#id-1.2.1设备端环境搭建-1.建议把BDAddress和DeviceName也改一下}
+##### 1.建议把BD Address和Device Name也改一下
-##### 2.建议Export 生成rcfg之前先导入正确的flash_map.ini {#id-1.2.1设备端环境搭建-2.建议Export生成rcfg之前先导入正确的flash_map.ini}
+##### 2.建议Export 生成rcfg之前先导入正确的flash_map.ini
-
+
-##### 3.因为设备不支援LEA， LEA相关的配置要务必关掉： {#id-1.2.1设备端环境搭建-3.因为设备不支援LEA，LEA相关的配置要务必关掉：}
+##### 3.因为设备不支援LEA， LEA相关的配置要务必关掉：
-
+
-
+
-
+
-### 2 TWS 耳机 GFPS battery feature测试环境搭建(只有TWS耳机需要做GFPS battery测试，single mode 不需要测试) {#id-1.2.1设备端环境搭建-2TWS耳机GFPSbatteryfeature测试环境搭建(只有TWS耳机需要做GFPSbattery测试，singlemode不需要测试)}
+### 2 TWS 耳机 GFPS battery feature测试环境搭建(只有TWS耳机需要做GFPS battery测试，single mode 不需要测试)
Note：
测试battery的时候需要搭配充电盒
-#### 2.1.mcu config tool 配置： {#id-1.2.1设备端环境搭建-2.1.mcuconfigtool配置：}
+#### 2.1.mcu config tool 配置：
-##### 2.1.1 HW Feature 模块 {#id-1.2.1设备端环境搭建-2.1.1HWFeature模块}
+##### 2.1.1 HW Feature 模块
勾选Charger功能：
-
+
-勾选支持充电盒功能，注意如果充电盒image烧录的是20ms,下面红色框中的40ms也要改成20ms,这个要和充电盒image匹配的。
+勾选支持充电盒功能，注意如果充电盒image烧录的是20ms,下面红色框中的40ms也要改成20ms,这个要和充电盒image匹配的。
-如果充电盒image 烧录的是40ms：
+如果充电盒image 烧录的是40ms：
-
+
如果充电盒image烧录的是20ms:\
-
+
勾选power off immediately when chose case和do not auto power off when case not close
-
+
-##### 2.1.2 charger 模块，勾选battery detection support {#id-1.2.1设备端环境搭建-2.1.2charger模块，勾选batterydetectionsupport}
+##### 2.1.2 charger 模块，勾选battery detection support
-
+
-
+
-
+
-##### 2.1.3 general 模块 {#id-1.2.1设备端环境搭建-2.1.3general模块}
+##### 2.1.3 general 模块
-
+
2.1.4 third party 模块 enable battery 功能
-
+
-#### 2.2.充电盒配置： {#id-1.2.1设备端环境搭建-2.2.充电盒配置：}
+#### 2.2.充电盒配置：
-##### 2.2.1 接线设置 {#id-1.2.1设备端环境搭建-2.2.1接线设置}
+##### 2.2.1 接线设置
-
+
-##### 2.2.2 充电盒操作 {#id-1.2.1设备端环境搭建-2.2.2充电盒操作}
+##### 2.2.2 充电盒操作
-
+
-#### **2.3 Note** {#id-1.2.1设备端环境搭建-2.3Note}
+#### **2.3 Note**
-##### 2.3.1 开关盒操作步骤 {#id-1.2.1设备端环境搭建-2.3.1开关盒操作步骤}
+##### 2.3.1 开关盒操作步骤
1.左右耳factory reset 之后，先按下出盒入盒按钮（确保两个按钮同时按下，代表左右耳机入盒），耳机入盒之后，再按下开盒关盒按钮(按键弹起是开盒)，耳机端可以听到power on的提示音，说明开盒成功。有时候开盒成功但是没有提示音，此时可以看一下log：
@@ -200,31 +201,30 @@ app_adp_handle_msg +++++ AD2B_CMD_POWER_OFF =4，如果有AD2B_CMD_POWER_OFF的l
关机之后，打开power off的提示音(目前没有打开，可以不需要修改，使用默认配置就好)
-
+
watch dog reset的时间改成6s,目前没有设置成6s,使用默认设置3s，目前测试看是ok的，所以这个也可以不用修改
-
+
-##### 2.3.2 HUN显示测试 {#id-1.2.1设备端环境搭建-2.3.2HUN显示测试}
+##### 2.3.2 HUN显示测试
HUN(Heads up notification)显示图如下：
-
+
一次HUN显示成功之后，需要先把上次的显示信息清掉,再执行下一次操作：
-
+
\
-##### 2.3.3 demo rcfg， 里面有model id信息，不可以直接开给客户！！！ {#id-1.2.1设备端环境搭建-2.3.3demorcfg，里面有modelid信息，不可以直接开给客户！！！}
+##### 2.3.3 demo rcfg， 里面有model id信息，不可以直接开给客户！！！
-[GFPS_Left.rcfg](/download/attachments/139180496/GFPS_Left.rcfg?version=1&modificationDate=1636711808317&api=v2){linked-resource-id="205658521" linked-resource-version="1" linked-resource-type="attachment" linked-resource-default-alias="GFPS_Left.rcfg" linked-resource-content-type="application/octet-stream" linked-resource-container-id="139180496" linked-resource-container-version="20"}
+GFPS_Left.rcfg
-[GFPS_Right.rcfg](/download/attachments/139180496/GFPS_Right.rcfg?version=1&modificationDate=1636711808877&api=v2){linked-resource-id="205658522" linked-resource-version="1" linked-resource-type="attachment" linked-resource-default-alias="GFPS_Right.rcfg" linked-resource-content-type="application/octet-stream" linked-resource-container-id="139180496" linked-resource-container-version="20"}
+GFPS_Right.rcfg
\
\
-::::
diff --git a/1.2.2+手机端环境搭建.md b/1.2.2+手机端环境搭建.md
index 276debf..91d6112 100644
--- a/1.2.2+手机端环境搭建.md
+++ b/1.2.2+手机端环境搭建.md
@@ -1,14 +1,14 @@
-# 1.2.2 手机端环境搭建 {#手机端环境搭建}
+# 1.2.2 手机端环境搭建
-:::: {.Section1}
-``{=html}
+/**/
+
+
-::: {.toc-macro .rbtoc1777598900336}
- [1.手机需要连接google网络](#id-1.2.2手机端环境搭建-1.手机需要连接google网络)
- [2.手机不可以打开勿扰模式，不然可能看不到弹窗](#id-1.2.2手机端环境搭建-2.手机不可以打开勿扰模式，不然可能看不到弹窗)
- [3.检查手机是否打开Google Play服务通知](#id-1.2.2手机端环境搭建-3.检查手机是否打开GooglePlay服务通知)
@@ -20,135 +20,135 @@ div.rbtoc1777598900336 li {margin-left: 0px;padding-left: 0px;}
- [9.Enable debug mode ID：](#id-1.2.2手机端环境搭建-9.EnabledebugmodeID：)
- [10.Check Google Play Service version](#id-1.2.2手机端环境搭建-10.CheckGooglePlayServiceversion)
- [11.注册成为google beta tester（内部测试账号已经注册过了，这一步不需要，如果是客户自己注册的Google账号，需要提醒客户check）](#id-1.2.2手机端环境搭建-11.注册成为googlebetatester（内部测试账号已经注册过了，这一步不需要，如果是客户自己注册的Google账号，需要提醒客户check）)
-:::
+
+
\
-该测试至少要准备两只手机。测试手机建议使用Google pixel手机， Pixel 5+ is recommended. 请**务必确保**手机端有打开开发者选项 [https://developer.android.com/studio/debug/dev-options?hl=zh-cn](https://developer.android.com/studio/debug/dev-options?hl=zh-cn){.external-link rel="nofollow"}
+该测试至少要准备两只手机。测试手机建议使用Google pixel手机， Pixel 5+ is recommended. 请**务必确保**手机端有打开开发者选项 https://developer.android.com/studio/debug/dev-options?hl=zh-cn
\
-#### 1.手机需要连接google网络 {#id-1.2.2手机端环境搭建-1.手机需要连接google网络}
+#### 1.手机需要连接google网络
-该网络必须可以登陆google的网站，在测试前请先测试一下是否可以登录google的网站(**建议试试能不能打开youtube之类的**）。
+该网络必须可以登陆google的网站，在测试前请先测试一下是否可以登录google的网站(**建议试试能不能打开youtube之类的**）。
-#### 2.手机不可以打开勿扰模式，不然可能看不到弹窗 {#id-1.2.2手机端环境搭建-2.手机不可以打开勿扰模式，不然可能看不到弹窗}
+#### 2.手机不可以打开勿扰模式，不然可能看不到弹窗
-
+
-#### 3.检查手机是否打开Google Play服务通知 {#id-1.2.2手机端环境搭建-3.检查手机是否打开GooglePlay服务通知}
+#### 3.检查手机是否打开Google Play服务通知
Setting-\>(Apps¬ification or Apps)应用和通知-\> See all apps -\>Google Play服务-\>通知-\>All Google Play services notifications, 开启(显示通知)
-
+
\
-#### 4.检查google play 服务是否更新到最新的版本 {#id-1.2.2手机端环境搭建-4.检查googleplay服务是否更新到最新的版本}
+#### 4.检查google play 服务是否更新到最新的版本
setting-\>(Apps¬ification or Apps)应用和通知-\>See all apps-\>Google Play 服务-\>高级-\>商店, 点击 App details or google play，界面会跳转到google play 商店，点击更新.
如果已经成为 beta tester, google play service可能会自动更新到最新的。
-
+
-
+
\
-#### 5.登陆google账号 {#id-1.2.2手机端环境搭建-5.登陆google账号}
+#### 5.登陆google账号
-Settings\>Accounts or Seetings-\>Google(内部账号(不可给客户)：
+Settings\>Accounts or Seetings-\>Google(内部账号(不可给客户)：
-[[[[[Fast Pair Validator 测试 请使用 ]{style="color: rgb(0,0,0);"}]{style="color: rgb(23,43,77);"}]{style="color: rgb(255,0,0);"}]{style="color: rgb(0,0,0);"}]{style="color: rgb(255,0,0);"}[realsilbt8888@gmail.com](mailto:realsilbt8888@gmail.com){.external-link rel="nofollow"}[ ]{style="color: rgb(255,0,0);"}
+Fast Pair Validator 测试 请使用 realsilbt8888@gmail.com
-[手动测试账号请参考 [[Google 账号 - BT_Market - WIKI (realtek.com)](https://wiki.realtek.com/pages/viewpage.action?pageId=394285307){rel="nofollow"} ]{style="color: rgb(23,43,77);"}]{style="color: rgb(255,0,0);"}
+手动测试账号请参考 Google 账号 - BT_Market - WIKI (realtek.com)
-#### 6 打开自动同步数据功能 {#id-1.2.2手机端环境搭建-6打开自动同步数据功能}
+#### 6 打开自动同步数据功能
由于GFPS的account key是存在google账号的云端的，所以必须要登陆google账号并且需要打开自动同步数据功能
Settings\>Accounts ：
-
+
or
Seetings→Google:
-
+
-#### 7.检查Show notification是否打开： {#id-1.2.2手机端环境搭建-7.检查Shownotification是否打开：}
+#### 7.检查Show notification是否打开：
Settings\>Google\>(Devices & sharing)\>Devices(设置\>Google\>设备连接\>设备\>)
pixel 2xl:
-
+
pixel 7:
-
+
\
-#### 8.Setting界面打开蓝牙，以及位置信息。 {#id-1.2.2手机端环境搭建-8.Setting界面打开蓝牙，以及位置信息。}
+#### 8.Setting界面打开蓝牙，以及位置信息。
\
-#### 9.Enable debug mode ID： {#id-1.2.2手机端环境搭建-9.EnabledebugmodeID：}
+#### 9.Enable debug mode ID：
-The model ID provided to you is a debug mode ID. To enable it, go to Settings \> Google \> Devices & sharing \> Devices \> top right 3 dot menu to enable "Include debug results".
+The model ID provided to you is a debug mode ID. To enable it, go to Settings \> Google \> Devices & sharing \> Devices \> top right 3 dot menu to enable “Include debug results”.
-If the option "Include debug results" is missing in this page, please ensure Developer options in the phone is enabled.
+If the option “Include debug results” is missing in this page, please ensure Developer options in the phone is enabled.
-or go to Settings \> Google \> Devices & sharing \> Devices \>"Include debug results"
+or go to Settings \> Google \> Devices & sharing \> Devices \>“Include debug results”
-Settings \> Google \> Devices & sharing \> Devices \> top right 3 dot menu to enable "Include debug results"
+Settings \> Google \> Devices & sharing \> Devices \> top right 3 dot menu to enable “Include debug results”
-
+
or
-Settings \> Google \> Devices & sharing \> Devices \>"Include debug results"
+Settings \> Google \> Devices & sharing \> Devices \>“Include debug results”
-
+
-[https://developer.android.com/studio/debug/dev-options?hl=zh-cn](https://developer.android.com/studio/debug/dev-options?hl=zh-cn){.external-link rel="nofollow"}
+https://developer.android.com/studio/debug/dev-options?hl=zh-cn
-#### 10.Check Google Play Service version {#id-1.2.2手机端环境搭建-10.CheckGooglePlayServiceversion}
+#### 10.Check Google Play Service version
Purpose: To confirm we use right version of Fast Pair module for testing
Go to Settings \> Apps¬ification or Apps\>google play services \> advanced, then check Google Play services version (It should be 20.XX.XX or higher).
-
+
\
\
-#### **11.注册成为google beta tester（内部测试账号已经注册过了，这一步不需要，如果是客户自己注册的Google账号，需要提醒客户check）** {#id-1.2.2手机端环境搭建-11.注册成为googlebetatester（内部测试账号已经注册过了，这一步不需要，如果是客户自己注册的Google账号，需要提醒客户check）}
+#### **11.注册成为google beta tester（内部测试账号已经注册过了，这一步不需要，如果是客户自己注册的Google账号，需要提醒客户check）**
-[1. Google test group - BT_Market - WIKI](https://wiki.realtek.com/display/BTMKT/1.+Google+test+group){rel="nofollow"}
+1. Google test group - BT_Market - WIKI
-Sign up for the Google Play services beta program [https://play.google.com/apps/testing/com.google.android.gms](https://play.google.com/apps/testing/com.google.android.gms){.external-link rel="nofollow"}
+Sign up for the Google Play services beta program https://play.google.com/apps/testing/com.google.android.gms
-join the Android Beta group at [https://www.google.com/android/beta](https://www.google.com/android/beta){.external-link rel="nofollow"} to get latest update via OTA
+join the Android Beta group at https://www.google.com/android/beta to get latest update via OTA
-Finder/Find Hub testing program please Navigate to [https://play.google.com/apps/testing/com.google.android.apps.adm](https://play.google.com/apps/testing/com.google.android.apps.adm){.external-link rel="nofollow"}
+Finder/Find Hub testing program please Navigate to https://play.google.com/apps/testing/com.google.android.apps.adm
\
-可以登陆Google账号之后在以下链接查看是否有添加成功：[我的群组](https://groups.google.com/my-groups){.external-link rel="nofollow"}
+可以登陆Google账号之后在以下链接查看是否有添加成功：我的群组
-
+
需要注意的是：
-
+
如果没有权限添加，FAE需要联系YingTsung (YT) Lin， 请他发邮件给Google， 让Google把客户注册的Google账号添加到Google的Test group。
\
-::::
diff --git a/1.2.3+Fast+Pair+Validator+环境搭建.md b/1.2.3+Fast+Pair+Validator+环境搭建.md
index ca616ba..698eb07 100644
--- a/1.2.3+Fast+Pair+Validator+环境搭建.md
+++ b/1.2.3+Fast+Pair+Validator+环境搭建.md
@@ -1,14 +1,14 @@
-# 1.2.3 Fast Pair Validator 环境搭建 {#fast-pair-validator-环境搭建}
+# 1.2.3 Fast Pair Validator 环境搭建
-:::: {.Section1}
-``{=html}
+/**/
+
+
-::: {.toc-macro .rbtoc1777598906641}
- [1 搭建手机端的测试环境](#id-1.2.3FastPairValidator环境搭建-1搭建手机端的测试环境)
- [1.1 手机需要连接google网络](#id-1.2.3FastPairValidator环境搭建-1.1手机需要连接google网络)
- [1.2 手机不可以打开勿扰模式，不然可能看不到弹窗](#id-1.2.3FastPairValidator环境搭建-1.2手机不可以打开勿扰模式，不然可能看不到弹窗)
@@ -28,151 +28,152 @@ div.rbtoc1777598906641 li {margin-left: 0px;padding-left: 0px;}
- [4 uninstall amazon 相关app](#id-1.2.3FastPairValidator环境搭建-4uninstallamazon相关app)
- [5 测试账号和MODEL ID](#id-1.2.3FastPairValidator环境搭建-5测试账号和MODELID)
- [6 测试准备](#id-1.2.3FastPairValidator环境搭建-6测试准备)
-:::
-### 1 搭建手机端的测试环境 {#id-1.2.3FastPairValidator环境搭建-1搭建手机端的测试环境}
+
-测试手机建议使用Google pixel手机，请**务必确保**手机端有打开开发者选项 [https://developer.android.com/studio/debug/dev-options?hl=zh-cn](https://developer.android.com/studio/debug/dev-options?hl=zh-cn){.external-link rel="nofollow"}
+### 1 搭建手机端的测试环境
+
+测试手机建议使用Google pixel手机，请**务必确保**手机端有打开开发者选项 https://developer.android.com/studio/debug/dev-options?hl=zh-cn
\
-#### 1.1 手机需要连接google网络 {#id-1.2.3FastPairValidator环境搭建-1.1手机需要连接google网络}
+#### 1.1 手机需要连接google网络
-该网络必须可以登陆google的网站，在测试前请先测试一下是否可以登录google的网站(**建议试试能不能打开youtube之类的**）。
+该网络必须可以登陆google的网站，在测试前请先测试一下是否可以登录google的网站(**建议试试能不能打开youtube之类的**）。
-#### 1.2 手机不可以打开勿扰模式，不然可能看不到弹窗 {#id-1.2.3FastPairValidator环境搭建-1.2手机不可以打开勿扰模式，不然可能看不到弹窗}
+#### 1.2 手机不可以打开勿扰模式，不然可能看不到弹窗
-
+
-#### 1.3 检查手机是否打开Google Play服务通知 {#id-1.2.3FastPairValidator环境搭建-1.3检查手机是否打开GooglePlay服务通知}
+#### 1.3 检查手机是否打开Google Play服务通知
Setting-\>(Apps¬ification or Apps)应用和通知-\> See all apps -\>Google Play服务-\>通知-\>All Google Play services notifications, 开启(显示通知)
-
+
-#### 1.4 检查google play 服务是否更新到最新的版本 {#id-1.2.3FastPairValidator环境搭建-1.4检查googleplay服务是否更新到最新的版本}
+#### 1.4 检查google play 服务是否更新到最新的版本
setting-\>(Apps¬ification or Apps)应用和通知-\>See all apps-\>Google Play 服务-\>高级-\>商店, 点击 App details or google play，界面会跳转到google play 商店，点击更新.
如果已经成为 beta tester, google play service可能会自动更新到最新的。
-
+
-
+
\
-#### 1.5 登陆google账号 {#id-1.2.3FastPairValidator环境搭建-1.5登陆google账号}
+#### 1.5 登陆google账号
-Settings\>Accounts or Seetings-\>Google(内部账号(不可给客户)：
+Settings\>Accounts or Seetings-\>Google(内部账号(不可给客户)：
-[[[[[Fast Pair Validator 测试 请使用 ]{style="color: rgb(0,0,0);"}]{style="color: rgb(23,43,77);"}]{style="color: rgb(255,0,0);"}]{style="color: rgb(0,0,0);"}]{style="color: rgb(255,0,0);"}[realsilbt8888@gmail.com](mailto:realsilbt8888@gmail.com){.external-link rel="nofollow"}[ ]{style="color: rgb(255,0,0);"}
+Fast Pair Validator 测试 请使用 realsilbt8888@gmail.com
-[手动测试账号请参考 [[Google 账号 - BT_Market - WIKI (realtek.com)](https://wiki.realtek.com/pages/viewpage.action?pageId=394285307){rel="nofollow"} ]{style="color: rgb(23,43,77);"}]{style="color: rgb(255,0,0);"}
+手动测试账号请参考 Google 账号 - BT_Market - WIKI (realtek.com)
-#### 1.6 打开自动同步数据功能 {#id-1.2.3FastPairValidator环境搭建-1.6打开自动同步数据功能}
+#### 1.6 打开自动同步数据功能
由于GFPS的account key是存在google账号的云端的，所以必须要登陆google账号并且需要打开自动同步数据功能
Settings\>Accounts ：
-
+
or
Seetings→Google:
-
+
-#### 1.7 检查Show notification是否打开： {#id-1.2.3FastPairValidator环境搭建-1.7检查Shownotification是否打开：}
+#### 1.7 检查Show notification是否打开：
Settings\>Google\>(Devices & sharing)\>Devices(设置\>Google\>设备连接\>设备\>)
pixel 2xl:
-
+
pixel 7:
-
+
\
跑 Fast pair validator 测试之前关掉 Automatically save devices
-**Note: 只有realsilbt8888的账号需要关掉 Automatically save devices， 其他手动测试的账号Automatically save devices需要打开**
+**Note: 只有realsilbt8888的账号需要关掉 Automatically save devices， 其他手动测试的账号Automatically save devices需要打开**
-
+
-#### 1.8 Setting界面打开蓝牙，以及位置信息。 {#id-1.2.3FastPairValidator环境搭建-1.8Setting界面打开蓝牙，以及位置信息。}
+#### 1.8 Setting界面打开蓝牙，以及位置信息。
\
-#### 1.9 Enable debug mode ID： {#id-1.2.3FastPairValidator环境搭建-1.9EnabledebugmodeID：}
+#### 1.9 Enable debug mode ID：
-The model ID provided to you is a debug mode ID. To enable it, go to Settings \> Google \> Devices & sharing \> Devices \> top right 3 dot menu to enable "Include debug results".
+The model ID provided to you is a debug mode ID. To enable it, go to Settings \> Google \> Devices & sharing \> Devices \> top right 3 dot menu to enable “Include debug results”.
-If the option "Include debug results" is missing in this page, please ensure Developer options in the phone is enabled.
+If the option “Include debug results” is missing in this page, please ensure Developer options in the phone is enabled.
-or go to Settings \> Google \> Devices & sharing \> Devices \>"Include debug results"
+or go to Settings \> Google \> Devices & sharing \> Devices \>“Include debug results”
-Settings \> Google \> Devices & sharing \> Devices \> top right 3 dot menu to enable "Include debug results"
+Settings \> Google \> Devices & sharing \> Devices \> top right 3 dot menu to enable “Include debug results”
-
+
or
-Settings \> Google \> Devices & sharing \> Devices \>"Include debug results"
+Settings \> Google \> Devices & sharing \> Devices \>“Include debug results”
-
+
-[https://developer.android.com/studio/debug/dev-options?hl=zh-cn](https://developer.android.com/studio/debug/dev-options?hl=zh-cn){.external-link rel="nofollow"}
+https://developer.android.com/studio/debug/dev-options?hl=zh-cn
-#### 1.10 Check Google Play Service version {#id-1.2.3FastPairValidator环境搭建-1.10CheckGooglePlayServiceversion}
+#### 1.10 Check Google Play Service version
Purpose: To confirm we use right version of Fast Pair module for testing
Go to Settings \> Apps¬ification or Apps\>google play services \> advanced, then check Google Play services version (It should be 20.XX.XX or higher).
-
+
\
\
-#### **1.11 注册成为google beta tester（内部测试账号已经注册过了，这一步不需要，如果是客户自己注册的Google账号，需要提醒客户check）** {#id-1.2.3FastPairValidator环境搭建-1.11注册成为googlebetatester（内部测试账号已经注册过了，这一步不需要，如果是客户自己注册的Google账号，需要提醒客户check）}
+#### **1.11 注册成为google beta tester（内部测试账号已经注册过了，这一步不需要，如果是客户自己注册的Google账号，需要提醒客户check）**
-Sign up for the Google Play services beta program [https://play.google.com/apps/testing/com.google.android.gms](https://play.google.com/apps/testing/com.google.android.gms){.external-link rel="nofollow"}
+Sign up for the Google Play services beta program https://play.google.com/apps/testing/com.google.android.gms
-join the Android Beta group at [https://www.google.com/android/beta](https://www.google.com/android/beta){.external-link rel="nofollow"} to get latest update via OTA
+join the Android Beta group at https://www.google.com/android/beta to get latest update via OTA
-Finder/Find Hub testing program please Navigate to [https://play.google.com/apps/testing/com.google.android.apps.adm](https://play.google.com/apps/testing/com.google.android.apps.adm){.external-link rel="nofollow"}
+Finder/Find Hub testing program please Navigate to https://play.google.com/apps/testing/com.google.android.apps.adm
\
-可以登陆Google账号之后在以下链接查看是否有添加成功：[我的群组](https://groups.google.com/my-groups){.external-link rel="nofollow"}
+可以登陆Google账号之后在以下链接查看是否有添加成功：我的群组
-
+
需要注意的是：
-
+
如果没有权限添加，FAE需要联系YingTsung (YT) Lin， 请他发邮件给Google， 让Google把客户注册的Google账号添加到Google的Test group。
\
-### **2 Fast Pair Validator APP安装** {#id-1.2.3FastPairValidator环境搭建-2FastPairValidatorAPP安装}
+### **2 Fast Pair Validator APP安装**
确认手机是否安装 Fast Pair Validator APP
-Fast pair validator app 图标如下图：
+Fast pair validator app 图标如下图：
-[]{style="color: rgb(153,51,0);"}
+
如果没有安装:
-去 Play Store/应用商店 下载 Fast Pair Validator APP并且安装。
+去 Play Store/应用商店 下载 Fast Pair Validator APP并且安装。
如果已经安装:
@@ -180,29 +181,29 @@ Fast pair validator app 图标如下图：
长按 Fast Pair Validator 图标，会看到App info
-
+
点击App info,会看到App details
-
+
点击App details,会看到以下页面，如果有新版本请手动更新到最新的版本。如果是beta版本则不需要更新，系统会自动帮忙更新。
-
+
-### 3 Enable fast pair validator app中的测项 {#id-1.2.3FastPairValidator环境搭建-3Enablefastpairvalidatorapp中的测项}
+### 3 Enable fast pair validator app中的测项
-#### [3.1 安装adb:]{style="color: rgb(32,33,36);"} {#id-1.2.3FastPairValidator环境搭建-3.1安装adb:}
+#### 3.1 安装adb:
-[[adb安装及使用方法](https://wiki.realtek.com/pages/viewpage.action?pageId=87464469){rel="nofollow"} 该wiki上提供的adb版本太旧，会出现device offline的问题，下载最新的[https://adbshell.com/downloads](https://adbshell.com/downloads){.external-link rel="nofollow"}]{style="color: rgb(32,33,36);"}
+adb安装及使用方法 该wiki上提供的adb版本太旧，会出现device offline的问题，下载最新的https://adbshell.com/downloads
-安装adb之后找到adb.exe所在的目录，在该目录下打开cmd命令行
+安装adb之后找到adb.exe所在的目录，在该目录下打开cmd命令行
-#### 3.2 输入如下命令： {#id-1.2.3FastPairValidator环境搭建-3.2输入如下命令：}
+#### 3.2 输入如下命令：
-adb shell am broadcast -a com.google.location.nearby.apps.fastpair.validator.FLAG_OVERRIDE \--es flag enable_features_for_v3 \--es value true \--es type boolean com.google.location.nearby.apps.fastpair.validator
+adb shell am broadcast -a com.google.location.nearby.apps.fastpair.validator.FLAG_OVERRIDE --es flag enable_features_for_v3 --es value true --es type boolean com.google.location.nearby.apps.fastpair.validator
-[]{.confluence-embedded-file-wrapper .confluence-embedded-manual-size}
+
按enter执行命令。
@@ -212,45 +213,44 @@ adb shell am broadcast -a com.google.location.nearby.apps.fastpair.validator.FLA
\
-### 4 uninstall amazon 相关app {#id-1.2.3FastPairValidator环境搭建-4uninstallamazon相关app}
+### 4 uninstall amazon 相关app
-Alexa (com.amazon.dee.app) 和com.amazon.wellness app， 会影响到Validator的测试，需要Uninstall。
+Alexa (com.amazon.dee.app) 和com.amazon.wellness app， 会影响到Validator的测试，需要Uninstall。
-The Alexa (com.amazon.dee.app) took too much time on handling the ACL_CONNECTED intent, which impacts the Validator\'s flow.
+The Alexa (com.amazon.dee.app) took too much time on handling the ACL_CONNECTED intent, which impacts the Validator's flow.
-There is still another **app,com.amazon.wellness** app, who handled ACL_CONNECTED for 20+ seconds.Please uninstall it as well.
+There is still another **app,com.amazon.wellness** app, who handled ACL_CONNECTED for 20+ seconds.Please uninstall it as well.
-现象： End-to-end integration测试，出现Pairing timeout
+现象： End-to-end integration测试，出现Pairing timeout
-操作方式：
+操作方式：
-adb uninstall com.amazon.wellness
+adb uninstall com.amazon.wellness
-adb uninstall com.amazon.dee.app
+adb uninstall com.amazon.dee.app
\
-### 5 测试账号和MODEL ID {#id-1.2.3FastPairValidator环境搭建-5测试账号和MODELID}
+### 5 测试账号和MODEL ID
使用Fast Pair Validator测试，需要先登陆Google账号，测试设备使用的Model ID,public key, private key 必须是该google账号注册的Device。
-场内测试账号：[realsilbt8888@gmail.com](mailto:realsilbt8888@gmail.com){.external-link rel="nofollow"}
+场内测试账号：realsilbt8888@gmail.com
-**Note：**
+**Note：**
fast pair validator app使用的model id 要和DUT开发板配置的model id一致。
-
+
-### **6 测试准备** {#id-1.2.3FastPairValidator环境搭建-6测试准备}
+### **6 测试准备**
测试过程中需要注意
-手机端弹出配对提示框时不要手动点击，fast pair validator app会自己触发配对.
+手机端弹出配对提示框时不要手动点击，fast pair validator app会自己触发配对.
开始测试前，需要确认是否已经和待测试耳机配对过，需要删除配对信息。 最后最好在开始测试前，开关一下飞行模式。
点击GOT IT开始测试时，耳机端一定要处于Pairable mode，否则会scan不到设备, scan 到设备后，点击Test开始测试。
-
-::::
+
diff --git a/1.3+测试.md b/1.3+测试.md
index 0ac4f00..96a63e3 100644
--- a/1.3+测试.md
+++ b/1.3+测试.md
@@ -1,11 +1,10 @@
-# 1.3 测试 {#测试}
+# 1.3 测试
-::: {.Section1}
测试完成之后要填写测试报告, 测试报告从以下位置获取：
-[Test Case of the Third Party - BT Test - WIKI](https://wiki.realtek.com/display/BT/Test+Case+of+the+Third+Party){rel="nofollow"}
+Test Case of the Third Party - BT Test - WIKI
-
+
\
@@ -13,11 +12,10 @@
Find My Device 那一页不需要测试：
-
+
\
Fast Pair Validator那一页 EDDYSTONE 下面的测项不需要测试：
-
-:::
+
diff --git a/1.3.1+Fast+Pair+Validator测试.md b/1.3.1+Fast+Pair+Validator测试.md
index 578acf2..ccdeb96 100644
--- a/1.3.1+Fast+Pair+Validator测试.md
+++ b/1.3.1+Fast+Pair+Validator测试.md
@@ -1,13 +1,11 @@
-# 1.3.1 Fast Pair Validator测试 {#fast-pair-validator测试}
+# 1.3.1 Fast Pair Validator测试
-::: {.Section1}
-[1.3.1.1 FAST PAIR](https://wiki.realtek.com/display/BTMKT/1.3.1.1+FAST+PAIR?src=contextnavpagetreemode){rel="nofollow"}
+1.3.1.1 FAST PAIR
-这个测项客户自测并且提交测试结果到Google云端，认证实验室暂时不会测试。
+这个测项客户自测并且提交测试结果到Google云端，认证实验室暂时不会测试。
-目前来看只要有一次测试成功，并且有提交成功的测试结果到Google云端就可以，即使偶尔失败了，如果确定不是我们设备端的bug, 也没关系的
+目前来看只要有一次测试成功，并且有提交成功的测试结果到Google云端就可以，即使偶尔失败了，如果确定不是我们设备端的bug, 也没关系的
-[https://partnerissuetracker.corp.google.com/u/0/issues/473688165](https://partnerissuetracker.corp.google.com/u/0/issues/473688165){.external-link rel="nofollow"}
+https://partnerissuetracker.corp.google.com/u/0/issues/473688165
-[]{.plugin_pagetree_children_span}
-:::
+
diff --git a/1.3.1.1+FAST+PAIR.md b/1.3.1.1+FAST+PAIR.md
index 7de9638..bf4d737 100644
--- a/1.3.1.1+FAST+PAIR.md
+++ b/1.3.1.1+FAST+PAIR.md
@@ -1,14 +1,13 @@
-# 1.3.1.1 FAST PAIR {#fast-pair}
+# 1.3.1.1 FAST PAIR
-:::: {.Section1}
-``{=html}
+/**/
-::: {.toc-macro .rbtoc1777599001982}
+
- [Note](#id-1.3.1.1FASTPAIR-Note)
- [1 以下关于mcu cfg tool 的修改仅仅是为了通过fast pair validator测试，待测试通过之后，需要将相应的修改恢复默认值。否则GFPS功能没法正常使用。](#id-1.3.1.1FASTPAIR-1以下关于mcucfgtool的修改仅仅是为了通过fastpairvalidator测试，待测试通过之后，需要将相应的修改恢复默认值。否则GFPS功能没法正常使用。)
@@ -48,51 +47,52 @@ div.rbtoc1777599001982 li {margin-left: 0px;padding-left: 0px;}
- [Firmware Version 测试](#id-1.3.1.1FASTPAIR-FirmwareVersion测试)
- [Dynamic Buffer Size测试](#id-1.3.1.1FASTPAIR-DynamicBufferSize测试)
- [10.测试结果上报](#id-1.3.1.1FASTPAIR-10.测试结果上报)
-:::
-### **Note** {#id-1.3.1.1FASTPAIR-Note}
+
-#### 1 以下关于mcu cfg tool 的修改仅仅是为了通过fast pair validator测试，待测试通过之后，需要将相应的修改恢复默认值。否则GFPS功能没法正常使用。 {#id-1.3.1.1FASTPAIR-1以下关于mcucfgtool的修改仅仅是为了通过fastpairvalidator测试，待测试通过之后，需要将相应的修改恢复默认值。否则GFPS功能没法正常使用。}
+### **Note**
- 也就是说以下修改只能搭配fast pair validator app使用，请不要将对应的修改提交到正式release版本。
+#### 1 以下关于mcu cfg tool 的修改仅仅是为了通过fast pair validator测试，待测试通过之后，需要将相应的修改恢复默认值。否则GFPS功能没法正常使用。
-#### 2 测试过程中GFPS 弹窗出来之后请不要点击弹窗！！！ {#id-1.3.1.1FASTPAIR-2测试过程中GFPS弹窗出来之后请不要点击弹窗！！！}
+ 也就是说以下修改只能搭配fast pair validator app使用，请不要将对应的修改提交到正式release版本。
-#### 3 GFPS Fast pair validator 测试走的Legacy flow, 通过gfps配对 legacy BREDR. {#id-1.3.1.1FASTPAIR-3GFPSFastpairvalidator测试走的Legacyflow,通过gfps配对legacyBREDR.}
+#### 2 测试过程中GFPS 弹窗出来之后请不要点击弹窗！！！
-#### 4 mcu cfg tool 中 可以配置按键key1进入legacy Pairing mode(MMI 0x6C)，有些测试会需要短按key1进入Pairing mode {#id-1.3.1.1FASTPAIR-4mcucfgtool中可以配置按键key1进入legacyPairingmode(MMI0x6C)，有些测试会需要短按key1进入Pairingmode}
+#### 3 GFPS Fast pair validator 测试走的Legacy flow, 通过gfps配对 legacy BREDR.
-
+#### 4 mcu cfg tool 中 可以配置按键key1进入legacy Pairing mode(MMI 0x6C)，有些测试会需要短按key1进入Pairing mode
-
+
+
+
\
-#### 5 手机提示信息解读： {#id-1.3.1.1FASTPAIR-5手机提示信息解读：}
+#### 5 手机提示信息解读：
-##### Upair the device：耳机做factory reset清掉配对信息 {#id-1.3.1.1FASTPAIR-Upairthedevice：耳机做factoryreset清掉配对信息}
+##### Upair the device：耳机做factory reset清掉配对信息
-##### place the device back into pairing mode：耳机进入pairing mode {#id-1.3.1.1FASTPAIR-placethedevicebackintopairingmode：耳机进入pairingmode}
+##### place the device back into pairing mode：耳机进入pairing mode
-#### 6 测试准备 {#id-1.3.1.1FASTPAIR-6测试准备}
+#### 6 测试准备
-##### 打开Fast Pair Validator app {#id-1.3.1.1FASTPAIR-打开FastPairValidatorapp}
+##### 打开Fast Pair Validator app
-[]{style="color: rgb(153,51,0);"}
+
-##### 通过model id找到待测试设备 {#id-1.3.1.1FASTPAIR-通过modelid找到待测试设备}
+##### 通过model id找到待测试设备
-[]{style="color: rgb(153,51,0);"}
+
-##### 选择FAST PAIR进行测试 {#id-1.3.1.1FASTPAIR-选择FASTPAIR进行测试}
+##### 选择FAST PAIR进行测试
-[]{style="color: rgb(153,51,0);"}
+
-##### 不要Enable LE spec test {#id-1.3.1.1FASTPAIR-不要EnableLEspectest}
+##### 不要Enable LE spec test
-[]{style="color: rgb(153,51,0);"}
+
-### Calibration 测试 {#id-1.3.1.1FASTPAIR-Calibration测试}
+### Calibration 测试
Note:
@@ -102,15 +102,15 @@ calibration 测试， discoverable adv interval需要足够小，spec 规定 dis
Note:
-GFPS 弹窗出来之后请**不要**点击弹窗！！！
+GFPS 弹窗出来之后请**不要**点击弹窗！！！
如果1m测项测试失败，Fast pair validator可以协助我们手动调整tx power值:
-
+
-详细文档可以参考：[tx power adjust user guide - BT_Market - WIKI](https://wiki.realtek.com/display/BTMKT/tx+power+adjust+user+guide){rel="nofollow"}
+详细文档可以参考：tx power adjust user guide - BT_Market - WIKI
-### End-to-end integration 测试 {#id-1.3.1.1FASTPAIR-End-to-endintegration测试}
+### End-to-end integration 测试
Note:
@@ -120,53 +120,53 @@ spec 规定not discoverable mode adv interval \<= 250ms，该测项中有verify
MCU cfg tool 配置：
-测试该测项的时候，手机清除配对信息(unpair device)，DUT断线需要进入non discoverable mode, 所以mcu config tool 中rws normal disconnect enter pairing mode需要设置成disable(不勾选)。
+测试该测项的时候，手机清除配对信息(unpair device)，DUT断线需要进入non discoverable mode, 所以mcu config tool 中rws normal disconnect enter pairing mode需要设置成disable(不勾选)。
-
+
-如果找不到 rws normal disconnect enter pairing mode 这个配置项 ，原因是这个配置项挪位置了，请参考jira [[BTSOCTOOL-2822](https://jira.realtek.com/browse/BTSOCTOOL-2822){.jira-issue-key} - Getting issue details\... STATUS ]{.jira-issue jira-key="BTSOCTOOL-2822" client-id="SINGLE_2d885edc-676b-3349-9548-fe5648c9d8cd_948641808_2c9082e76519d09101657ff5cfb3003b"} 进行配置，RWS normal disconnect enter pairing mode 改成Normal disconnect enter pairing mode
+如果找不到 rws normal disconnect enter pairing mode 这个配置项 ，原因是这个配置项挪位置了，请参考jira BTSOCTOOL-2822 - Getting issue details... STATUS 进行配置，RWS normal disconnect enter pairing mode 改成Normal disconnect enter pairing mode
-
+
\
-（1）手机提示 Next steps时，控制耳机进入配对模式，点击next，等待手机 prescan-\> pair device -\> check account key != null -\> unpair device-\>verify account key --\> verify 500ms frequency -\> Check subsequent pairing tx power level -\> repair device -\> un-repair device.。
+（1）手机提示 Next steps时，控制耳机进入配对模式，点击next，等待手机 prescan-\> pair device -\> check account key != null -\> unpair device-\>verify account key –\> verify 500ms frequency -\> Check subsequent pairing tx power level -\> repair device -\> un-repair device.。
-（2）点击next。 注意一定要在"10.Un-Repair device"显示"Unpairing finished!"后才能点NEXT。
+（2）点击next。 注意一定要在“10.Un-Repair device”显示“Unpairing finished!”后才能点NEXT。
如此反复5遍。
-
+
-
+
测试视频：
-[End To End test.mp4](/download/attachments/948641808/End%20To%20End%20test.mp4?version=1&modificationDate=1759129643533&api=v2){linked-resource-id="948642410" linked-resource-version="1" linked-resource-type="attachment" linked-resource-default-alias="End To End test.mp4" nice-type="Multimedia" linked-resource-content-type="video/mp4" linked-resource-container-id="948641808" linked-resource-container-version="19"}
+End To End test.mp4
-### Auto pairing 测试 {#id-1.3.1.1FASTPAIR-Autopairing测试}
+### Auto pairing 测试
-Mcu cfg tool配置：
+Mcu cfg tool配置：
-测试该测项的时候，手机清除配对信息(unpair device)，DUT断线需要进入discoverable mode, 所以mcu config tool 中 RWS页面下 rws normal disconnect enter pairing mode[需要设置成enable(勾选)。]{style="color: rgb(0,0,0);"}\
+测试该测项的时候，手机清除配对信息(unpair device)，DUT断线需要进入discoverable mode, 所以mcu config tool 中 RWS页面下 rws normal disconnect enter pairing mode需要设置成enable(勾选)。\
app_cfg_const.rws_disconnect_enter_pairing
-[]{style="color: rgb(0,0,0);"}
+
-如果找不到 rws normal disconnect enter pairing mode 这个配置项 ，原因是这个配置项挪位置了，请参考jira [[BTSOCTOOL-2822](https://jira.realtek.com/browse/BTSOCTOOL-2822){.jira-issue-key} - Getting issue details\... STATUS ]{.jira-issue jira-key="BTSOCTOOL-2822" client-id="SINGLE_2d885edc-676b-3349-9548-fe5648c9d8cd_948641808_2c9082e76519d09101657ff5cfb3003b"} 进行配置，RWS normal disconnect enter pairing mode 改成Normal disconnect enter pairing mode
+如果找不到 rws normal disconnect enter pairing mode 这个配置项 ，原因是这个配置项挪位置了，请参考jira BTSOCTOOL-2822 - Getting issue details... STATUS 进行配置，RWS normal disconnect enter pairing mode 改成Normal disconnect enter pairing mode
-
+
-[\
-]{style="color: rgb(0,0,0);"}
+\
+
-设置每一轮测试持续时间以及重复进行多少轮测试([推荐使用APP中提供的默认值进行测试（100次，一次120s)，然后点击test, ]{style="color: rgb(0,0,0);"}
+设置每一轮测试持续时间以及重复进行多少轮测试(推荐使用APP中提供的默认值进行测试（100次，一次120s)，然后点击test,
-测试时将手机setting-》显示-》屏幕超时设置成最大值。灭屏之后测试好像会stop，所以屏幕要保持常亮的状态。
+测试时将手机setting-》显示-》屏幕超时设置成最大值。灭屏之后测试好像会stop，所以屏幕要保持常亮的状态。
\
-**Note:**
+**Note:**
这个测试按照Google的测试spec是要求每轮测试之前都要强制进pairing mode的。
@@ -178,23 +178,23 @@ app_cfg_const.rws_disconnect_enter_pairing
\
-
+
-### Auto Subsequent Pairing 测试 {#id-1.3.1.1FASTPAIR-AutoSubsequentPairing测试}
+### Auto Subsequent Pairing 测试
MCU cfg tool 配置：
-测试该测项的时候，手机清除配对信息(unpair device)，DUT断线需要进入non discoverable mode, 所以mcu config tool 中rws normal disconnect enter pairing mode需要设置成disable(不勾选)。
+测试该测项的时候，手机清除配对信息(unpair device)，DUT断线需要进入non discoverable mode, 所以mcu config tool 中rws normal disconnect enter pairing mode需要设置成disable(不勾选)。
-
+
-如果找不到 rws normal disconnect enter pairing mode 这个配置项 ，原因是这个配置项挪位置了，请参考jira [[BTSOCTOOL-2822](https://jira.realtek.com/browse/BTSOCTOOL-2822){.jira-issue-key} - Getting issue details\... STATUS ]{.jira-issue jira-key="BTSOCTOOL-2822" client-id="SINGLE_2d885edc-676b-3349-9548-fe5648c9d8cd_948641808_2c9082e76519d09101657ff5cfb3003b"} 进行配置，RWS normal disconnect enter pairing mode 改成Normal disconnect enter pairing mode
+如果找不到 rws normal disconnect enter pairing mode 这个配置项 ，原因是这个配置项挪位置了，请参考jira BTSOCTOOL-2822 - Getting issue details... STATUS 进行配置，RWS normal disconnect enter pairing mode 改成Normal disconnect enter pairing mode
-
+
\
-**Note:**
+**Note:**
这个测试按照Google的测试spec是要求每轮测试之前都要打nondiscoverable 广播的。
@@ -206,19 +206,19 @@ MCU cfg tool 配置：
所以针对异常的情况，
-soc端是没办法做到所有的失败场景下都能保证下一轮测试一定会主动打nondiscoverable 广播(不在pairing mode才会打nondiscoverable 广播)， 因为手机端并不会告诉soc 什么时候测试开始。
+soc端是没办法做到所有的失败场景下都能保证下一轮测试一定会主动打nondiscoverable 广播(不在pairing mode才会打nondiscoverable 广播)， 因为手机端并不会告诉soc 什么时候测试开始。
所以如果跑自动化测试遇到失败的情况，建议手动测试：
-每一轮测试结束之后EVB按一下reset或者是关机再开机让设备端主动打nondiscoverable 广播(注意这个时候EVB一定不能做factory reset，也不能进pairing mode, 因为这个时候是期望打 nondiscoverable 广播)
+每一轮测试结束之后EVB按一下reset或者是关机再开机让设备端主动打nondiscoverable 广播(注意这个时候EVB一定不能做factory reset，也不能进pairing mode, 因为这个时候是期望打 nondiscoverable 广播)
-BLE advertisements don\'t contain fast pair account key while not in pairing mode 如果频繁遇到这个error， 可以尝试手动测试试试看
+BLE advertisements don't contain fast pair account key while not in pairing mode 如果频繁遇到这个error， 可以尝试手动测试试试看
\
测试信息设置：
-
+
手机端测试信息设置完成之后，
@@ -226,23 +226,23 @@ BLE advertisements don\'t contain fast pair account key while not in pairing mod
之后手机端点击test 开始测试
-
+
\
\
-### Cross Seekers Auto Subsequent Pairing Test 测试 {#id-1.3.1.1FASTPAIR-CrossSeekersAutoSubsequentPairingTest测试}
+### Cross Seekers Auto Subsequent Pairing Test 测试
MCU cfg tool 配置：
-测试该测项的时候，手机清除配对信息(unpair device)，DUT断线需要进入non discoverable mode, 所以mcu config tool 中rws normal disconnect enter pairing mode需要设置成disable(不勾选)。
+测试该测项的时候，手机清除配对信息(unpair device)，DUT断线需要进入non discoverable mode, 所以mcu config tool 中rws normal disconnect enter pairing mode需要设置成disable(不勾选)。
-
+
-如果找不到 rws normal disconnect enter pairing mode 这个配置项 ，原因是这个配置项挪位置了，请参考jira [[BTSOCTOOL-2822](https://jira.realtek.com/browse/BTSOCTOOL-2822){.jira-issue-key} - Getting issue details\... STATUS ]{.jira-issue jira-key="BTSOCTOOL-2822" client-id="SINGLE_2d885edc-676b-3349-9548-fe5648c9d8cd_948641808_2c9082e76519d09101657ff5cfb3003b"} 进行配置，RWS normal disconnect enter pairing mode 改成Normal disconnect enter pairing mode
+如果找不到 rws normal disconnect enter pairing mode 这个配置项 ，原因是这个配置项挪位置了，请参考jira BTSOCTOOL-2822 - Getting issue details... STATUS 进行配置，RWS normal disconnect enter pairing mode 改成Normal disconnect enter pairing mode
-
+
\
@@ -250,45 +250,45 @@ MCU cfg tool 配置：
测试信息设置：
-
+
\
-耳机先做factory reset，手机端清掉配对信息[1 gfps/finder 如何清除配对信息 - BT_Market - WIKI](https://wiki.realtek.com/pages/viewpage.action?pageId=401291585){rel="nofollow"}， 之后耳机开机进pairing mode，之后手机端点击test 开始测试
+耳机先做factory reset，手机端清掉配对信息1 gfps/finder 如何清除配对信息 - BT_Market - WIKI， 之后耳机开机进pairing mode，之后手机端点击test 开始测试
\
测试视频：
-[Cross Seekers Auto Subsequent Pairing Test.mp4](/download/attachments/948641808/Cross%20Seekers%20Auto%20Subsequent%20Pairing%20Test.mp4?version=1&modificationDate=1759224099177&api=v2){linked-resource-id="948651208" linked-resource-version="1" linked-resource-type="attachment" linked-resource-default-alias="Cross Seekers Auto Subsequent Pairing Test.mp4" nice-type="Multimedia" linked-resource-content-type="video/mp4" linked-resource-container-id="948641808" linked-resource-container-version="19"}
+Cross Seekers Auto Subsequent Pairing Test.mp4
测试log：
-[COM12_2025-09-30_16-56-51.log](/download/attachments/948641808/COM12_2025-09-30_16-56-51.log?version=1&modificationDate=1759223471600&api=v2){linked-resource-id="948651140" linked-resource-version="1" linked-resource-type="attachment" linked-resource-default-alias="COM12_2025-09-30_16-56-51.log" nice-type="Text File" linked-resource-content-type="text/plain" linked-resource-container-id="948641808" linked-resource-container-version="19"}
+COM12_2025-09-30_16-56-51.log
-[COM12_btsnoop_2025-09-30_16-51-45.cfa](/download/attachments/948641808/COM12_btsnoop_2025-09-30_16-51-45.cfa?version=1&modificationDate=1759223475897&api=v2){linked-resource-id="948651142" linked-resource-version="1" linked-resource-type="attachment" linked-resource-default-alias="COM12_btsnoop_2025-09-30_16-51-45.cfa" linked-resource-content-type="application/octet-stream" linked-resource-container-id="948641808" linked-resource-container-version="19"}
+COM12_btsnoop_2025-09-30_16-51-45.cfa
-[COM12_2025-09-30_16-51-39.log](/download/attachments/948641808/COM12_2025-09-30_16-51-39.log?version=1&modificationDate=1759223476397&api=v2){linked-resource-id="948651143" linked-resource-version="1" linked-resource-type="attachment" linked-resource-default-alias="COM12_2025-09-30_16-51-39.log" nice-type="Text File" linked-resource-content-type="text/plain" linked-resource-container-id="948641808" linked-resource-container-version="19"}
+COM12_2025-09-30_16-51-39.log
-[COM12_2025-09-26_14-19-00.log](/download/attachments/948641808/COM12_2025-09-26_14-19-00.log?version=1&modificationDate=1759223503080&api=v2){linked-resource-id="948651148" linked-resource-version="1" linked-resource-type="attachment" linked-resource-default-alias="COM12_2025-09-26_14-19-00.log" nice-type="Text File" linked-resource-content-type="text/plain" linked-resource-container-id="948641808" linked-resource-container-version="19"}
+COM12_2025-09-26_14-19-00.log
-
+
-
+
\
-### Public Key Based Pairing Request in Non Discoverable Mode 测试 {#id-1.3.1.1FASTPAIR-PublicKeyBasedPairingRequestinNonDiscoverableMode测试}
+### Public Key Based Pairing Request in Non Discoverable Mode 测试
MCU cfg tool 配置：
-测试该测项的时候，手机清除配对信息(unpair device)，DUT断线需要进入non discoverable mode, 所以mcu config tool 中rws normal disconnect enter pairing mode需要设置成disable(不勾选)。
+测试该测项的时候，手机清除配对信息(unpair device)，DUT断线需要进入non discoverable mode, 所以mcu config tool 中rws normal disconnect enter pairing mode需要设置成disable(不勾选)。
-
+
-如果找不到 rws normal disconnect enter pairing mode 这个配置项 ，原因是这个配置项挪位置了，请参考jira [[BTSOCTOOL-2822](https://jira.realtek.com/browse/BTSOCTOOL-2822){.jira-issue-key} - Getting issue details\... STATUS ]{.jira-issue jira-key="BTSOCTOOL-2822" client-id="SINGLE_2d885edc-676b-3349-9548-fe5648c9d8cd_948641808_2c9082e76519d09101657ff5cfb3003b"} 进行配置，RWS normal disconnect enter pairing mode 改成Normal disconnect enter pairing mode
+如果找不到 rws normal disconnect enter pairing mode 这个配置项 ，原因是这个配置项挪位置了，请参考jira BTSOCTOOL-2822 - Getting issue details... STATUS 进行配置，RWS normal disconnect enter pairing mode 改成Normal disconnect enter pairing mode
-
+
\
@@ -296,41 +296,41 @@ MCU cfg tool 配置：
测试信息设置：
-
+
\
-耳机先做factory reset，手机端清掉配对信息[1 gfps/finder 如何清除配对信息 - BT_Market - WIKI](https://wiki.realtek.com/pages/viewpage.action?pageId=401291585){rel="nofollow"}， 之后耳机开机进pairing mode，之后手机端点击test 开始测试
+耳机先做factory reset，手机端清掉配对信息1 gfps/finder 如何清除配对信息 - BT_Market - WIKI， 之后耳机开机进pairing mode，之后手机端点击test 开始测试
\
测试视频：
-[public key based request in non discoverable mode-Non LEA.mp4](/download/attachments/948641808/public%20key%20based%20request%20in%20non%20discoverable%20mode-Non%20LEA.mp4?version=1&modificationDate=1759225238333&api=v2){linked-resource-id="948651368" linked-resource-version="1" linked-resource-type="attachment" linked-resource-default-alias="public key based request in non discoverable mode-Non LEA.mp4" nice-type="Multimedia" linked-resource-content-type="video/mp4" linked-resource-container-id="948641808" linked-resource-container-version="19"}
+public key based request in non discoverable mode-Non LEA.mp4
测试log：
-[COM12_2025-09-30_17-33-58.log](/download/attachments/948641808/COM12_2025-09-30_17-33-58.log?version=1&modificationDate=1759225010223&api=v2){linked-resource-id="948651337" linked-resource-version="1" linked-resource-type="attachment" linked-resource-default-alias="COM12_2025-09-30_17-33-58.log" nice-type="Text File" linked-resource-content-type="text/plain" linked-resource-container-id="948641808" linked-resource-container-version="19"}
+COM12_2025-09-30_17-33-58.log
-[COM12_btsnoop_2025-09-30_17-29-41.cfa](/download/attachments/948641808/COM12_btsnoop_2025-09-30_17-29-41.cfa?version=1&modificationDate=1759225015190&api=v2){linked-resource-id="948651338" linked-resource-version="1" linked-resource-type="attachment" linked-resource-default-alias="COM12_btsnoop_2025-09-30_17-29-41.cfa" linked-resource-content-type="application/octet-stream" linked-resource-container-id="948641808" linked-resource-container-version="19"}
+COM12_btsnoop_2025-09-30_17-29-41.cfa
-[COM12_2025-09-30_17-29-39.log](/download/attachments/948641808/COM12_2025-09-30_17-29-39.log?version=1&modificationDate=1759225015860&api=v2){linked-resource-id="948651339" linked-resource-version="1" linked-resource-type="attachment" linked-resource-default-alias="COM12_2025-09-30_17-29-39.log" nice-type="Text File" linked-resource-content-type="text/plain" linked-resource-container-id="948641808" linked-resource-container-version="19"}
+COM12_2025-09-30_17-29-39.log
-
+
\
-### Public Key Based Pairing Request After Retroactive Pair 测试 {#id-1.3.1.1FASTPAIR-PublicKeyBasedPairingRequestAfterRetroactivePair测试}
+### Public Key Based Pairing Request After Retroactive Pair 测试
MCU cfg tool 配置：
-测试该测项的时候，手机清除配对信息(unpair device)，DUT断线需要进入non discoverable mode, 所以mcu config tool 中rws normal disconnect enter pairing mode需要设置成disable(不勾选)。
+测试该测项的时候，手机清除配对信息(unpair device)，DUT断线需要进入non discoverable mode, 所以mcu config tool 中rws normal disconnect enter pairing mode需要设置成disable(不勾选)。
-
+
-如果找不到 rws normal disconnect enter pairing mode 这个配置项 ，原因是这个配置项挪位置了，请参考jira [[BTSOCTOOL-2822](https://jira.realtek.com/browse/BTSOCTOOL-2822){.jira-issue-key} - Getting issue details\... STATUS ]{.jira-issue jira-key="BTSOCTOOL-2822" client-id="SINGLE_2d885edc-676b-3349-9548-fe5648c9d8cd_948641808_2c9082e76519d09101657ff5cfb3003b"} 进行配置，RWS normal disconnect enter pairing mode 改成Normal disconnect enter pairing mode
+如果找不到 rws normal disconnect enter pairing mode 这个配置项 ，原因是这个配置项挪位置了，请参考jira BTSOCTOOL-2822 - Getting issue details... STATUS 进行配置，RWS normal disconnect enter pairing mode 改成Normal disconnect enter pairing mode
-
+
\
@@ -338,7 +338,7 @@ MCU cfg tool 配置：
测试信息设置：
-耳机先做factory reset，手机端清掉配对信息[1 gfps/finder 如何清除配对信息 - BT_Market - WIKI](https://wiki.realtek.com/pages/viewpage.action?pageId=401291585){rel="nofollow"}， 之后耳机开机进pairing mode，之后手机端点击test 开始测试
+耳机先做factory reset，手机端清掉配对信息1 gfps/finder 如何清除配对信息 - BT_Market - WIKI， 之后耳机开机进pairing mode，之后手机端点击test 开始测试
\
@@ -346,39 +346,39 @@ MCU cfg tool 配置：
如果测试过程中遇到 Get account key fail, 参考以下视频：
-[Public key based pairing request after retroactive pair-nonLEA-Get account key fail.mp4](/download/attachments/948641808/Public%20key%20based%20pairing%20request%20after%20retroactive%20pair-nonLEA-Get%20account%20key%20fail.mp4?version=1&modificationDate=1759226451537&api=v2){linked-resource-id="948651473" linked-resource-version="1" linked-resource-type="attachment" linked-resource-default-alias="Public key based pairing request after retroactive pair-nonLEA-Get account key fail.mp4" nice-type="Multimedia" linked-resource-content-type="video/mp4" linked-resource-container-id="948641808" linked-resource-container-version="19"}
+Public key based pairing request after retroactive pair-nonLEA-Get account key fail.mp4
测试成功视频：
-[Public key based pairing request after retroactive pair-nonLEA.mp4](/download/attachments/948641808/Public%20key%20based%20pairing%20request%20after%20retroactive%20pair-nonLEA.mp4?version=1&modificationDate=1759226617723&api=v2){linked-resource-id="948651483" linked-resource-version="1" linked-resource-type="attachment" linked-resource-default-alias="Public key based pairing request after retroactive pair-nonLEA.mp4" nice-type="Multimedia" linked-resource-content-type="video/mp4" linked-resource-container-id="948641808" linked-resource-container-version="19"}
+Public key based pairing request after retroactive pair-nonLEA.mp4
\
测试log：
-
+
-
+
-[COM12_2025-10-13_13-47-37.log](/download/attachments/948641808/COM12_2025-10-13_13-47-37.log?version=1&modificationDate=1760336127463&api=v2){linked-resource-id="964439163" linked-resource-version="1" linked-resource-type="attachment" linked-resource-default-alias="COM12_2025-10-13_13-47-37.log" nice-type="Text File" linked-resource-content-type="text/plain" linked-resource-container-id="948641808" linked-resource-container-version="19"}
+COM12_2025-10-13_13-47-37.log
-[COM12_2025-10-13_13-51-37.log](/download/attachments/948641808/COM12_2025-10-13_13-51-37.log?version=1&modificationDate=1760336113757&api=v2){linked-resource-id="964439159" linked-resource-version="1" linked-resource-type="attachment" linked-resource-default-alias="COM12_2025-10-13_13-51-37.log" nice-type="Text File" linked-resource-content-type="text/plain" linked-resource-container-id="948641808" linked-resource-container-version="19"}
+COM12_2025-10-13_13-51-37.log
-[COM12_btsnoop_2025-10-13_13-48-53.cfa](/download/attachments/948641808/COM12_btsnoop_2025-10-13_13-48-53.cfa?version=1&modificationDate=1760336126687&api=v2){linked-resource-id="964439162" linked-resource-version="1" linked-resource-type="attachment" linked-resource-default-alias="COM12_btsnoop_2025-10-13_13-48-53.cfa" linked-resource-content-type="application/octet-stream" linked-resource-container-id="948641808" linked-resource-container-version="19"}
+COM12_btsnoop_2025-10-13_13-48-53.cfa
-[Public Key Based Pairing Request After Retroactive Pair测试pass.7z](/download/attachments/948641808/Public%20Key%20Based%20Pairing%20Request%20After%20Retroactive%20Pair%E6%B5%8B%E8%AF%95pass.7z?version=1&modificationDate=1763543863557&api=v2){linked-resource-id="998593044" linked-resource-version="1" linked-resource-type="attachment" linked-resource-default-alias="Public Key Based Pairing Request After Retroactive Pair测试pass.7z" linked-resource-content-type="application/octet-stream" linked-resource-container-id="948641808" linked-resource-container-version="19"}
+Public Key Based Pairing Request After Retroactive Pair测试pass.7z
-### Account key Broadcasting & Rotation of RPA测试 {#id-1.3.1.1FASTPAIR-AccountkeyBroadcasting&RotationofRPA测试}
+### Account key Broadcasting & Rotation of RPA测试
MCU cfg tool 配置：
-测试该测项的时候，手机清除配对信息(unpair device)，DUT断线需要进入non discoverable mode, 所以mcu config tool 中rws normal disconnect enter pairing mode需要设置成disable(不勾选)。
+测试该测项的时候，手机清除配对信息(unpair device)，DUT断线需要进入non discoverable mode, 所以mcu config tool 中rws normal disconnect enter pairing mode需要设置成disable(不勾选)。
-
+
-如果找不到 rws normal disconnect enter pairing mode 这个配置项 ，原因是这个配置项挪位置了，请参考jira [[BTSOCTOOL-2822](https://jira.realtek.com/browse/BTSOCTOOL-2822){.jira-issue-key} - Getting issue details\... STATUS ]{.jira-issue jira-key="BTSOCTOOL-2822" client-id="SINGLE_2d885edc-676b-3349-9548-fe5648c9d8cd_948641808_2c9082e76519d09101657ff5cfb3003b"} 进行配置，RWS normal disconnect enter pairing mode 改成Normal disconnect enter pairing mode
+如果找不到 rws normal disconnect enter pairing mode 这个配置项 ，原因是这个配置项挪位置了，请参考jira BTSOCTOOL-2822 - Getting issue details... STATUS 进行配置，RWS normal disconnect enter pairing mode 改成Normal disconnect enter pairing mode
-
+
\
@@ -388,69 +388,69 @@ MCU cfg tool 配置：
\
-### Key Based Request Flags Reserved Bit Verification 测试 {#id-1.3.1.1FASTPAIR-KeyBasedRequestFlagsReservedBitVerification测试}
+### Key Based Request Flags Reserved Bit Verification 测试
MCU cfg tool 配置：
-测试该测项的时候，手机清除配对信息(unpair device)，DUT断线需要进入non discoverable mode, 所以mcu config tool 中rws normal disconnect enter pairing mode需要设置成disable(不勾选)。
+测试该测项的时候，手机清除配对信息(unpair device)，DUT断线需要进入non discoverable mode, 所以mcu config tool 中rws normal disconnect enter pairing mode需要设置成disable(不勾选)。
-
+
-如果找不到 rws normal disconnect enter pairing mode 这个配置项 ，原因是这个配置项挪位置了，请参考jira [[BTSOCTOOL-2822](https://jira.realtek.com/browse/BTSOCTOOL-2822){.jira-issue-key} - Getting issue details\... STATUS ]{.jira-issue jira-key="BTSOCTOOL-2822" client-id="SINGLE_2d885edc-676b-3349-9548-fe5648c9d8cd_948641808_2c9082e76519d09101657ff5cfb3003b"} 进行配置，RWS normal disconnect enter pairing mode 改成Normal disconnect enter pairing mode
+如果找不到 rws normal disconnect enter pairing mode 这个配置项 ，原因是这个配置项挪位置了，请参考jira BTSOCTOOL-2822 - Getting issue details... STATUS 进行配置，RWS normal disconnect enter pairing mode 改成Normal disconnect enter pairing mode
-
+
\
板子做factory reset之后，开机进pairing mode，点击test开始测试
-测试过程中看到\"Please places the headset to pairing mode\"的时候，短按key1进入pairing mode， 测试过程中不可以做factory reset
+测试过程中看到"Please places the headset to pairing mode"的时候，短按key1进入pairing mode， 测试过程中不可以做factory reset
测试视频：
-[Key Based Request Flags Reserved Bit Verification.mp4](/download/attachments/948641808/Key%20Based%20Request%20Flags%20Reserved%20Bit%20Verification.mp4?version=1&modificationDate=1760339352253&api=v2){linked-resource-id="964439764" linked-resource-version="1" linked-resource-type="attachment" linked-resource-default-alias="Key Based Request Flags Reserved Bit Verification.mp4" nice-type="Multimedia" linked-resource-content-type="video/mp4" linked-resource-container-id="948641808" linked-resource-container-version="19"}
+Key Based Request Flags Reserved Bit Verification.mp4
\
-### Distance 0.3 Meter 测试 {#id-1.3.1.1FASTPAIR-Distance0.3Meter测试}
+### Distance 0.3 Meter 测试
-耳机开机，[按键key1进入GFPS LEA配对模式，然后开始测试，等待测试完成。]{style="color: rgb(153,51,0);"}
+耳机开机，按键key1进入GFPS LEA配对模式，然后开始测试，等待测试完成。
-Note:
+Note:
-GFPS 弹窗出来之后不要点；
+GFPS 弹窗出来之后不要点；
-如果该测项测不过，MCU cfg tool Thirdparty 页面需要适当减小tx power(比如从-10，减小到-12)；并重新跑 \"**Calibration 测试\"** 以及该测项
+如果该测项测不过，MCU cfg tool Thirdparty 页面需要适当减小tx power(比如从-10，减小到-12)；并重新跑 "**Calibration 测试"** 以及该测项
\
-### []{style="color: rgb(153,51,0);"} {#id-1.3.1.1FASTPAIR-}
+### 
\
-### Distance 1.2 Meter 测试 {#id-1.3.1.1FASTPAIR-Distance1.2Meter测试}
+### Distance 1.2 Meter 测试
-耳机开机，[按键key1进入GFPS LEA配对模式，然后开始测试，等待测试完成。]{style="color: rgb(153,51,0);"}
+耳机开机，按键key1进入GFPS LEA配对模式，然后开始测试，等待测试完成。
-Note:
+Note:
-GFPS 弹窗出来之后不要点；
+GFPS 弹窗出来之后不要点；
-如果该测项测不过，MCU cfg tool Thirdparty 页面需要适当增大tx power(比如从-12增大到-10）；并重新跑 \"**Calibration 测试\"** 以及该测项
+如果该测项测不过，MCU cfg tool Thirdparty 页面需要适当增大tx power(比如从-12增大到-10）；并重新跑 "**Calibration 测试"** 以及该测项
\
\
-### Distance 2 Meter 测试 {#id-1.3.1.1FASTPAIR-Distance2Meter测试}
+### Distance 2 Meter 测试
-耳机开机，[按键key1进入GFPS LEA配对模式，然后开始测试，等待测试完成。]{style="color: rgb(153,51,0);"}
+耳机开机，按键key1进入GFPS LEA配对模式，然后开始测试，等待测试完成。
-Note:
+Note:
-GFPS 弹窗出来之后不要点；
+GFPS 弹窗出来之后不要点；
-如果该测项测不过，MCU cfg tool Thirdparty 页面需要适当增大tx power(比如从-12增大到-10）；并重新跑 \"**Calibration 测试\"** 以及该测项
+如果该测项测不过，MCU cfg tool Thirdparty 页面需要适当增大tx power(比如从-12增大到-10）；并重新跑 "**Calibration 测试"** 以及该测项
@@ -460,21 +460,21 @@ GFPS 弹窗出来之后不要点；
\
-### Battery Notification Verification 测试 {#id-1.3.1.1FASTPAIR-BatteryNotificationVerification测试}
+### Battery Notification Verification 测试
-Note:
+Note:
-该测项测试的时候需要接充电盒
+该测项测试的时候需要接充电盒
MCU cfg tool 配置：
-测试该测项的时候，手机清除配对信息(unpair device)，DUT断线需要进入non discoverable mode, 所以mcu config tool 中rws normal disconnect enter pairing mode需要设置成disable(不勾选)。
+测试该测项的时候，手机清除配对信息(unpair device)，DUT断线需要进入non discoverable mode, 所以mcu config tool 中rws normal disconnect enter pairing mode需要设置成disable(不勾选)。
-
+
-如果找不到 rws normal disconnect enter pairing mode 这个配置项 ，原因是这个配置项挪位置了，请参考jira [[BTSOCTOOL-2822](https://jira.realtek.com/browse/BTSOCTOOL-2822){.jira-issue-key} - Getting issue details\... STATUS ]{.jira-issue jira-key="BTSOCTOOL-2822" client-id="SINGLE_2d885edc-676b-3349-9548-fe5648c9d8cd_948641808_2c9082e76519d09101657ff5cfb3003b"} 进行配置，RWS normal disconnect enter pairing mode 改成Normal disconnect enter pairing mode
+如果找不到 rws normal disconnect enter pairing mode 这个配置项 ，原因是这个配置项挪位置了，请参考jira BTSOCTOOL-2822 - Getting issue details... STATUS 进行配置，RWS normal disconnect enter pairing mode 改成Normal disconnect enter pairing mode
-
+
\
@@ -484,21 +484,21 @@ MCU cfg tool 配置：
\
-### Battery Suppress Notification Verification 测试 {#id-1.3.1.1FASTPAIR-BatterySuppressNotificationVerification测试}
+### Battery Suppress Notification Verification 测试
-Note:
+Note:
-该测项测试的时候需要接充电盒
+该测项测试的时候需要接充电盒
MCU cfg tool 配置：
-测试该测项的时候，手机清除配对信息(unpair device)，DUT断线需要进入non discoverable mode, 所以mcu config tool 中rws normal disconnect enter pairing mode需要设置成disable(不勾选)。
+测试该测项的时候，手机清除配对信息(unpair device)，DUT断线需要进入non discoverable mode, 所以mcu config tool 中rws normal disconnect enter pairing mode需要设置成disable(不勾选)。
-
+
-如果找不到 rws normal disconnect enter pairing mode 这个配置项 ，原因是这个配置项挪位置了，请参考jira [[BTSOCTOOL-2822](https://jira.realtek.com/browse/BTSOCTOOL-2822){.jira-issue-key} - Getting issue details\... STATUS ]{.jira-issue jira-key="BTSOCTOOL-2822" client-id="SINGLE_2d885edc-676b-3349-9548-fe5648c9d8cd_948641808_2c9082e76519d09101657ff5cfb3003b"} 进行配置，RWS normal disconnect enter pairing mode 改成Normal disconnect enter pairing mode
+如果找不到 rws normal disconnect enter pairing mode 这个配置项 ，原因是这个配置项挪位置了，请参考jira BTSOCTOOL-2822 - Getting issue details... STATUS 进行配置，RWS normal disconnect enter pairing mode 改成Normal disconnect enter pairing mode
-
+
\
@@ -506,21 +506,21 @@ MCU cfg tool 配置：
\
-### Battery Level Update Verification 测试 {#id-1.3.1.1FASTPAIR-BatteryLevelUpdateVerification测试}
+### Battery Level Update Verification 测试
-Note:
+Note:
-该测项测试的时候需要接充电盒
+该测项测试的时候需要接充电盒
MCU cfg tool 配置：
-测试该测项的时候，手机清除配对信息(unpair device)，DUT断线需要进入non discoverable mode, 所以mcu config tool 中rws normal disconnect enter pairing mode需要设置成disable(不勾选)。
+测试该测项的时候，手机清除配对信息(unpair device)，DUT断线需要进入non discoverable mode, 所以mcu config tool 中rws normal disconnect enter pairing mode需要设置成disable(不勾选)。
-
+
-如果找不到 rws normal disconnect enter pairing mode 这个配置项 ，原因是这个配置项挪位置了，请参考jira [[BTSOCTOOL-2822](https://jira.realtek.com/browse/BTSOCTOOL-2822){.jira-issue-key} - Getting issue details\... STATUS ]{.jira-issue jira-key="BTSOCTOOL-2822" client-id="SINGLE_2d885edc-676b-3349-9548-fe5648c9d8cd_948641808_2c9082e76519d09101657ff5cfb3003b"} 进行配置，RWS normal disconnect enter pairing mode 改成Normal disconnect enter pairing mode
+如果找不到 rws normal disconnect enter pairing mode 这个配置项 ，原因是这个配置项挪位置了，请参考jira BTSOCTOOL-2822 - Getting issue details... STATUS 进行配置，RWS normal disconnect enter pairing mode 改成Normal disconnect enter pairing mode
-
+
\
@@ -528,17 +528,17 @@ MCU cfg tool 配置：
\
-### Personalized Name Update 测试 {#id-1.3.1.1FASTPAIR-PersonalizedNameUpdate测试}
+### Personalized Name Update 测试
MCU cfg tool 配置：
-测试该测项的时候，手机清除配对信息(unpair device)，DUT断线需要进入non discoverable mode, 所以mcu config tool 中rws normal disconnect enter pairing mode需要设置成disable(不勾选)。
+测试该测项的时候，手机清除配对信息(unpair device)，DUT断线需要进入non discoverable mode, 所以mcu config tool 中rws normal disconnect enter pairing mode需要设置成disable(不勾选)。
-
+
-如果找不到 rws normal disconnect enter pairing mode 这个配置项 ，原因是这个配置项挪位置了，请参考jira [[BTSOCTOOL-2822](https://jira.realtek.com/browse/BTSOCTOOL-2822){.jira-issue-key} - Getting issue details\... STATUS ]{.jira-issue jira-key="BTSOCTOOL-2822" client-id="SINGLE_2d885edc-676b-3349-9548-fe5648c9d8cd_948641808_2c9082e76519d09101657ff5cfb3003b"} 进行配置，RWS normal disconnect enter pairing mode 改成Normal disconnect enter pairing mode
+如果找不到 rws normal disconnect enter pairing mode 这个配置项 ，原因是这个配置项挪位置了，请参考jira BTSOCTOOL-2822 - Getting issue details... STATUS 进行配置，RWS normal disconnect enter pairing mode 改成Normal disconnect enter pairing mode
-
+
\
@@ -546,11 +546,11 @@ MCU cfg tool 配置：
\
-测试注意事项：
+测试注意事项：
测试之前板子先做factory reset， 然后开机进pairing mode, 开始测试
-测试过程中看到\"Please places the headset to pairing mode\"的时候，短按key1进入pairing mode， 测试过程中不可以做factory reset
+测试过程中看到"Please places the headset to pairing mode"的时候，短按key1进入pairing mode， 测试过程中不可以做factory reset
@@ -562,19 +562,19 @@ MCU cfg tool 配置：
测试视频：
-[Personalized name update.mp4](/download/attachments/948641808/Personalized%20name%20update.mp4?version=1&modificationDate=1759129788767&api=v2){linked-resource-id="948642419" linked-resource-version="1" linked-resource-type="attachment" linked-resource-default-alias="Personalized name update.mp4" nice-type="Multimedia" linked-resource-content-type="video/mp4" linked-resource-container-id="948641808" linked-resource-container-version="19"}
+Personalized name update.mp4
-### Personalized Name with Provider First Time Pairing 测试 {#id-1.3.1.1FASTPAIR-PersonalizedNamewithProviderFirstTimePairing测试}
+### Personalized Name with Provider First Time Pairing 测试
MCU cfg tool 配置：
-测试该测项的时候，手机清除配对信息(unpair device)，DUT断线需要进入non discoverable mode, 所以mcu config tool 中rws normal disconnect enter pairing mode需要设置成disable(不勾选)。
+测试该测项的时候，手机清除配对信息(unpair device)，DUT断线需要进入non discoverable mode, 所以mcu config tool 中rws normal disconnect enter pairing mode需要设置成disable(不勾选)。
-
+
-如果找不到 rws normal disconnect enter pairing mode 这个配置项 ，原因是这个配置项挪位置了，请参考jira [[BTSOCTOOL-2822](https://jira.realtek.com/browse/BTSOCTOOL-2822){.jira-issue-key} - Getting issue details\... STATUS ]{.jira-issue jira-key="BTSOCTOOL-2822" client-id="SINGLE_2d885edc-676b-3349-9548-fe5648c9d8cd_948641808_2c9082e76519d09101657ff5cfb3003b"} 进行配置，RWS normal disconnect enter pairing mode 改成Normal disconnect enter pairing mode
+如果找不到 rws normal disconnect enter pairing mode 这个配置项 ，原因是这个配置项挪位置了，请参考jira BTSOCTOOL-2822 - Getting issue details... STATUS 进行配置，RWS normal disconnect enter pairing mode 改成Normal disconnect enter pairing mode
-
+
\
@@ -584,7 +584,7 @@ MCU cfg tool 配置：
测试之前板子做factory reset，然后再开机进pairing mode,然后开始测试
-看到\"Please places the headset to pairing mode\"的时候，短按key1让耳机进入 pairing mode
+看到"Please places the headset to pairing mode"的时候，短按key1让耳机进入 pairing mode
测试log:
@@ -594,17 +594,17 @@ MCU cfg tool 配置：
\
-### Ring a Device 测试 {#id-1.3.1.1FASTPAIR-RingaDevice测试}
+### Ring a Device 测试
MCU cfg tool 配置：
-测试该测项的时候，手机清除配对信息(unpair device)，DUT断线需要进入non discoverable mode, 所以mcu config tool 中rws normal disconnect enter pairing mode需要设置成disable(不勾选)。
+测试该测项的时候，手机清除配对信息(unpair device)，DUT断线需要进入non discoverable mode, 所以mcu config tool 中rws normal disconnect enter pairing mode需要设置成disable(不勾选)。
-
+
-如果找不到 rws normal disconnect enter pairing mode 这个配置项 ，原因是这个配置项挪位置了，请参考jira [[BTSOCTOOL-2822](https://jira.realtek.com/browse/BTSOCTOOL-2822){.jira-issue-key} - Getting issue details\... STATUS ]{.jira-issue jira-key="BTSOCTOOL-2822" client-id="SINGLE_2d885edc-676b-3349-9548-fe5648c9d8cd_948641808_2c9082e76519d09101657ff5cfb3003b"} 进行配置，RWS normal disconnect enter pairing mode 改成Normal disconnect enter pairing mode
+如果找不到 rws normal disconnect enter pairing mode 这个配置项 ，原因是这个配置项挪位置了，请参考jira BTSOCTOOL-2822 - Getting issue details... STATUS 进行配置，RWS normal disconnect enter pairing mode 改成Normal disconnect enter pairing mode
-
+
\
@@ -618,7 +618,7 @@ MCU cfg tool 配置：
测试之前板子做factory reset，然后再开机进pairing mode, 然后开始测试
-看到\"Please places the headset to pairing mode\"的时候，短按key1让耳机进入 pairing mode
+看到"Please places the headset to pairing mode"的时候，短按key1让耳机进入 pairing mode
测试log:
@@ -632,19 +632,19 @@ MCU cfg tool 配置：
测试视频：
-[Ring a Device.mp4](/download/attachments/948641808/Ring%20a%20Device.mp4?version=1&modificationDate=1759129874047&api=v2){linked-resource-id="948642430" linked-resource-version="1" linked-resource-type="attachment" linked-resource-default-alias="Ring a Device.mp4" nice-type="Multimedia" linked-resource-content-type="video/mp4" linked-resource-container-id="948641808" linked-resource-container-version="19"}
+Ring a Device.mp4
-### Retroactive Pair 测试 {#id-1.3.1.1FASTPAIR-RetroactivePair测试}
+### Retroactive Pair 测试
MCU cfg tool 配置：
-测试该测项的时候，手机清除配对信息(unpair device)，DUT断线需要进入non discoverable mode, 所以mcu config tool 中rws normal disconnect enter pairing mode需要设置成disable(不勾选)。
+测试该测项的时候，手机清除配对信息(unpair device)，DUT断线需要进入non discoverable mode, 所以mcu config tool 中rws normal disconnect enter pairing mode需要设置成disable(不勾选)。
-
+
-如果找不到 rws normal disconnect enter pairing mode 这个配置项 ，原因是这个配置项挪位置了，请参考jira [[BTSOCTOOL-2822](https://jira.realtek.com/browse/BTSOCTOOL-2822){.jira-issue-key} - Getting issue details\... STATUS ]{.jira-issue jira-key="BTSOCTOOL-2822" client-id="SINGLE_2d885edc-676b-3349-9548-fe5648c9d8cd_948641808_2c9082e76519d09101657ff5cfb3003b"} 进行配置，RWS normal disconnect enter pairing mode 改成Normal disconnect enter pairing mode
+如果找不到 rws normal disconnect enter pairing mode 这个配置项 ，原因是这个配置项挪位置了，请参考jira BTSOCTOOL-2822 - Getting issue details... STATUS 进行配置，RWS normal disconnect enter pairing mode 改成Normal disconnect enter pairing mode
-
+
\
@@ -656,43 +656,43 @@ MCU cfg tool 配置：
测试视频：
-[retroactive pair test.mp4](/download/attachments/948641808/retroactive%20pair%20test.mp4?version=1&modificationDate=1759129956680&api=v2){linked-resource-id="948642435" linked-resource-version="1" linked-resource-type="attachment" linked-resource-default-alias="retroactive pair test.mp4" nice-type="Multimedia" linked-resource-content-type="video/mp4" linked-resource-container-id="948641808" linked-resource-container-version="19"}
+retroactive pair test.mp4
测试log:
-[Retroactive Pair测试pass.7z](/download/attachments/948641808/Retroactive%20Pair%E6%B5%8B%E8%AF%95pass.7z?version=1&modificationDate=1763543586347&api=v2){linked-resource-id="998593012" linked-resource-version="1" linked-resource-type="attachment" linked-resource-default-alias="Retroactive Pair测试pass.7z" linked-resource-content-type="application/octet-stream" linked-resource-container-id="948641808" linked-resource-container-version="19"}
+Retroactive Pair测试pass.7z
-### Active Noise Control Verification 测试 {#id-1.3.1.1FASTPAIR-ActiveNoiseControlVerification测试}
+### Active Noise Control Verification 测试
-目前还不清楚怎么测试，如果不支援可以不测
+目前还不清楚怎么测试，如果不支援可以不测
-### Active Noise Control Disable 测试 {#id-1.3.1.1FASTPAIR-ActiveNoiseControlDisable测试}
+### Active Noise Control Disable 测试
-目前还不清楚怎么测试，如果不支援可以不测
+目前还不清楚怎么测试，如果不支援可以不测
-### Firmware Version 测试 {#id-1.3.1.1FASTPAIR-FirmwareVersion测试}
+### Firmware Version 测试
MCU cfg tool 配置：
-测试该测项的时候，手机清除配对信息(unpair device)，DUT断线需要进入non discoverable mode, 所以mcu config tool 中rws normal disconnect enter pairing mode需要设置成disable(不勾选)。
+测试该测项的时候，手机清除配对信息(unpair device)，DUT断线需要进入non discoverable mode, 所以mcu config tool 中rws normal disconnect enter pairing mode需要设置成disable(不勾选)。
-
+
-如果找不到 rws normal disconnect enter pairing mode 这个配置项 ，原因是这个配置项挪位置了，请参考jira [[BTSOCTOOL-2822](https://jira.realtek.com/browse/BTSOCTOOL-2822){.jira-issue-key} - Getting issue details\... STATUS ]{.jira-issue jira-key="BTSOCTOOL-2822" client-id="SINGLE_2d885edc-676b-3349-9548-fe5648c9d8cd_948641808_2c9082e76519d09101657ff5cfb3003b"} 进行配置，RWS normal disconnect enter pairing mode 改成Normal disconnect enter pairing mode
+如果找不到 rws normal disconnect enter pairing mode 这个配置项 ，原因是这个配置项挪位置了，请参考jira BTSOCTOOL-2822 - Getting issue details... STATUS 进行配置，RWS normal disconnect enter pairing mode 改成Normal disconnect enter pairing mode
-
+
\
-### Dynamic Buffer Size测试 {#id-1.3.1.1FASTPAIR-DynamicBufferSize测试}
+### Dynamic Buffer Size测试
-目前还不清楚怎么测试，如果不支援 可以不测
+目前还不清楚怎么测试，如果不支援 可以不测
\
-### 10.测试结果上报 {#id-1.3.1.1FASTPAIR-10.测试结果上报}
+### 10.测试结果上报
-测试成功后，除了 [目前还不清楚怎么测试 的测项之外的，其他所有的测试结果都为PASS，可以SUBMIT测试结果，否则请不要提交测试结果！！！]{style="color: rgb(255,0,0);"}
+测试成功后，除了 目前还不清楚怎么测试 的测项之外的，其他所有的测试结果都为PASS，可以SUBMIT测试结果，否则请不要提交测试结果！！！
\
@@ -701,4 +701,3 @@ MCU cfg tool 配置：
\
\
-::::
diff --git a/1.3.2+手动测试.md b/1.3.2+手动测试.md
index b4880f3..f7c90e7 100644
--- a/1.3.2+手动测试.md
+++ b/1.3.2+手动测试.md
@@ -1,7 +1,5 @@
-# 1.3.2 手动测试 {#手动测试}
+# 1.3.2 手动测试
-::: {.Section1}
手动测试完成之后需要提交self test report:
-Fast Pair self-tests report can be found in the [BlueTooth Classic](https://developers.google.com/static/nearby/fast-pair/downloads/self-test-reports/Bluetooth_Classic_-_Google_Fast_Pair_Self_Test_Report_10142020.zip){.external-link style="" rel="nofollow"}
-:::
+Fast Pair self-tests report can be found in the BlueTooth Classic
diff --git a/1.3.2.1+Initial+pair+and+subsequent+pair.md b/1.3.2.1+Initial+pair+and+subsequent+pair.md
index af306a1..381d727 100644
--- a/1.3.2.1+Initial+pair+and+subsequent+pair.md
+++ b/1.3.2.1+Initial+pair+and+subsequent+pair.md
@@ -1,17 +1,15 @@
-# 1.3.2.1 Initial pair and subsequent pair {#initial-pair-and-subsequent-pair}
+# 1.3.2.1 Initial pair and subsequent pair
-::: {.Section1}
google 官方测试文档：
-[Fast Pair 3.2 & 3.3 Certification Guidelines \| Google for Developers](https://developers.google.com/nearby/fast-pair/fast-pair-certification-guideline#22_notification_popup_for_initial_pairing){.external-link rel="nofollow"}
+Fast Pair 3.2 & 3.3 Certification Guidelines | Google for Developers
Realtek内部整理文档：
-[1 Initial Pairing and Subsequent Pairing Test Guideline(中文文档) - BT_Market - WIKI](https://wiki.realtek.com/pages/viewpage.action?pageId=288810503){rel="nofollow"}
+1 Initial Pairing and Subsequent Pairing Test Guideline(中文文档) - BT_Market - WIKI
测试视频：
-[initial_pairing.mp4](/download/attachments/948641817/initial_pairing.mp4?version=1&modificationDate=1759136017707&api=v2){linked-resource-id="948643166" linked-resource-version="1" linked-resource-type="attachment" linked-resource-default-alias="initial_pairing.mp4" nice-type="Multimedia" linked-resource-content-type="video/mp4" linked-resource-container-id="948641817" linked-resource-container-version="3"}
+initial_pairing.mp4
\
-:::
diff --git a/1.3.2.2+extended+feature.md b/1.3.2.2+extended+feature.md
index 84110a5..e874a9b 100644
--- a/1.3.2.2+extended+feature.md
+++ b/1.3.2.2+extended+feature.md
@@ -1,15 +1,13 @@
-# 1.3.2.2 extended feature {#extended-feature}
+# 1.3.2.2 extended feature
-::: {.Section1}
Google 官方文档：
-[https://developers.google.com/nearby/fast-pair/fast-pair-certification-guideline#4_feature_certification_criteria](https://developers.google.com/nearby/fast-pair/fast-pair-certification-guideline#4_feature_certification_criteria){.external-link rel="nofollow"}
+https://developers.google.com/nearby/fast-pair/fast-pair-certification-guideline#4_feature_certification_criteria
Realtek 内部整理文档：
-[1 Extension Feature Test Guideline(中文文档) - BT_Market - WIKI](https://wiki.realtek.com/pages/viewpage.action?pageId=374584696){rel="nofollow"}
+1 Extension Feature Test Guideline(中文文档) - BT_Market - WIKI
\
\
-:::
diff --git a/1.provider支援LE+audio+++Legacy+audio,不用单独过GFPS+Legacy的认证_.md b/1.provider支援LE+audio+++Legacy+audio,不用单独过GFPS+Legacy的认证_.md
new file mode 100644
index 0000000..42e7cba
--- /dev/null
+++ b/1.provider支援LE+audio+++Legacy+audio,不用单独过GFPS+Legacy的认证_.md
@@ -0,0 +1,5 @@
+# 1.provider支援LE audio + Legacy audio,不用单独过GFPS Legacy的认证?
+
+答案：是的
+
+
diff --git a/1.耳机支援LEA,手机也支援LEA,测试fail.md b/1.耳机支援LEA,手机也支援LEA,测试fail.md
new file mode 100644
index 0000000..de03dc2
--- /dev/null
+++ b/1.耳机支援LEA,手机也支援LEA,测试fail.md
@@ -0,0 +1,114 @@
+# 1.耳机支援LEA,手机也支援LEA,测试fail
+
+https://partnerissuetracker.corp.google.com/u/0/issues/419110816
+
+[BB2BUG-49617] [BB2][RTL8763ESH/ROM][GMI][沃莱特][Harman][T530] [finder] 455-[LEA][Finder]EIK rotation Automated test fail - Jira
+
+
+
+
+
+hi Mark:\
+\
+‘EIK Rotation’ test fail, can you help see the reason, thanks.\
+\
+test fail screen: Wed May 21 2025 10:06:37 GMT+0800 (中国标准时间).png\
+\
+20:01:31 phone rotating EIK and disconnect this ACL link,\
+when headsets receive disconnect command, The new EIK will take effect immediately after the BLE connection is terminated.\
+however headsets seems do not receive this disconnect command,\
+\
+we check logs in phone set:\
+//20:01:31.628 BluetoothGatt.disconnect\
+Line 23078: 05-20 20:01:31.628 10290 14358 31585 I GattClientImpl: BluetoothGatt.disconnect() - B8:17:43:1C:C6:CD \[CONTEXT service_id=284 \]\
+\
+however headsets seems do not receive this disconnect command,\
+we also check air log, At 20:01:31, there was no disconnection command in the air log.\
+\
+Is it because the cmd to terminate the connection on the mobile phone was not sent out?\
+\
+Add the following information:\
+The disconnection at 20:01:53 was received by both the air log and the headphone log.\
+Line 24568: 05-20 20:01:53.076 10290 14358 31594 I GattClientImpl: BluetoothGatt.disconnect() - B8:17:43:1C:C6:CD \[CONTEXT service_id=284 \]\
+thanks
+
+\
+
+add more information:\
+The headset supports LE audio.\
+When tested with a phone that does not support LE audio, EIK rotation test succeeds.\
+When tested with a phone that supports LE audio, EIK rotation test fails.
+
+\
+
+\
+
+Reassigned to tonyysliu@google.com.
+
+There seem to be another connection to the same device preventing the ACL from disconnecting. The connection is created a few seconds the Validator tests are run, perhaps during the pairing request which is the part of the test setup (logcat logs missing for that time)
+
+ 36659 20:01:05.523604 controller host HCI_EVT 34 Rcvd LE Meta (LE Extended Advertising Report) worldeliteel_1c:c6:cd 00 Common Audio
+ 36674 20:01:05.548200 host controller HCI_CMD 62 Sent LE Extended Create Connection [v1]
+ 36676 20:01:05.592129 controller host HCI_EVT 34 Rcvd LE Meta (LE Enhanced Connection Complete [v1]) worldeliteel_1c:c6:cd
+ Connection Handle: 0x0041
+
+LE Audio could be keeping this connection.
+
+ ::le_audio 2025-05-20 20:01:14.743 CONN_STATE GID -1 CONNECTING_BY_USER (0x05) -> : xx:xx:xx:xx:c6:cd ->CONNECTED_BY_USER_GETTING_READY (0x06)
+ ::le_audio 2025-05-20 20:01:17.869 CONN_STATE GID 1 CONNECTED_BY_USER_GETTING_READY (0x06) -> : xx:xx:xx:xx:c6:cd ->CONNECTED (0x01)
+ ::le_audio 2025-05-20 20:01:53.104 CONN_STATE GID -1 CONNECTED (0x01) -> : xx:xx:xx:xx:c6:cd ->DISCONNECTING (0x03)
+ ::le_audio 2025-05-20 20:01:53.104 CONN_STATE GID -1 DISCONNECTING (0x03) -> : xx:xx:xx:xx:c6:cd ->REMOVING (0x02)
+
+All GATT connect/disconnect request via API don't trigger actual ACL connects/disconnects on the controller till this one:
+
+ 05-20 20:01:31.628 I GattClientImpl: BluetoothGatt.disconnect() - B8:17:43:1C:C6:CD [CONTEXT service_id=284 ]
+ 42909 20:01:53.102405 host controller HCI_CMD 7 Sent Disconnect
+ Connection Handle: 0x0041
+
+------------------------------------------------------------------------
+
+@tonyysliu@google.com - do you know whether FP or LEA stack could be creating/holding this connection?
+
+‘
+
+’
+
+\
+
+#### gmark@google.com\google.com\> #9May 28, 2025 06:11PM
+
+Marked as fixed.
+
+Per logs it indeed seems that the initial connection is created by Fast Pair, then while the link is open, profiles are connected and this link is kept used throught the test till profiles are disconnected due to removing the bond. Forcibly removing the bond is expected to fix this.
+
+ [bugreport-tokay-BP1A.250505.005-2025-05-28-14-25-36.zip]
+
+ 05-28 14:22:32.091 I FastPair: FPDC: Starting to pair XX:XX:XX:XX:19:19: key[64], ...
+
+ // Device is being connected to.
+ 05-28 14:22:32.110 D BluetoothGatt: connect() - device: XX:XX:XX:XX:19:19, auto: false
+ 10535 14:22:32.155421 controller host HCI_EVT 34 Rcvd LE Meta (LE Enhanced Connection Complete [v1]) 19:22:77:19:19:19
+
+ 14:22:38.931 xx:xx:xx:xx:19:19 bond_state_changed BOND_STATE_BONDED
+
+ 05-28 14:22:40.198 D BluetoothAdapter: HEADSET connected
+ 05-28 14:22:40.201 D BluetoothAdapter: LE_AUDIO connected
+ 05-28 14:22:40.209 D CachedBluetoothDevice: onProfileStateChanged: profile LE_AUDIO, device XX:XX:XX:XX:19:19, newProfileState 1
+ 05-28 14:22:40.217 D CachedBluetoothDevice: onProfileStateChanged: profile VCP, device XX:XX:XX:XX:19:19, newProfileState 1
+ 05-28 14:22:40.261 D CachedBluetoothDevice: onProfileStateChanged: profile LE_AUDIO, device XX:XX:XX:XX:19:19, newProfileState 1
+ 05-28 14:22:40.275 D CachedBluetoothDevice: onProfileStateChanged: profile VCP, device XX:XX:XX:XX:19:19, newProfileState 1
+
+ // Does not disconnect due to connected profiles
+ 05-28 14:22:40.281 D BluetoothGatt: close()
+
+ // All following connect/close calls (skipped) do not affect the underlying connection, it's kept open.
+
+ // Validator closes the connection followed by unbonding, results in closing the underlying connection
+ 05-28 14:23:15.878 I GattClientImpl: gatt.close() [CONTEXT service_id=284 ]
+ 05-28 14:23:15.878 D BluetoothGatt: close()
+
+ 14:23:15.895 xx:xx:xx:xx:19:19 btif_dm_remove_bond BOND_STATE_NONE
+
+ 13261 14:23:15.909981 controller host HCI_EVT 7 Rcvd Disconnect Complete
+
+The potential fix is submitted and expected to be included in the next Validator's version.
diff --git a/10+battery+HUN弹窗一直不消失，或者是一直不显示.md b/10+battery+HUN弹窗一直不消失，或者是一直不显示.md
new file mode 100644
index 0000000..a7f9e64
--- /dev/null
+++ b/10+battery+HUN弹窗一直不消失，或者是一直不显示.md
@@ -0,0 +1,37 @@
+# 10 battery HUN弹窗一直不消失，或者是一直不显示
+
+**1. HUN的测试步骤如下：**
+
+1\) Test phone paired with the TWS headsets.(耳机和手机分别清掉配对信息，双耳在盒，开盖，耳机和手机做initial pair，initial pair成功之后，关盖，等待几秒确保耳机已经关机)\
+2) Open case.(双耳在盒，开盖)\
+3) when HUN shows, Close case.（HUN 出现之后立马关盖,等待几秒确保耳机已经关机）
+
+**NOTE：**
+
+**先执行步骤1， 步骤1 执行完成之后再执行步骤2 和 3， 之后步骤 2 和 3 可以重复多次。**
+
+关闭HUN弹窗的广播只打3s, 手机端看到HUN弹窗出现之后，就立刻执行关盒操作。
+
+
+
+\
+
+\
+
+**2.如果HUN 长时间不消失，应该是手机端没有扫到关闭HUN的广播信息，请尝试手机端主动清除HUN信息之后。再执行下一轮操作**
+
+
+
+\
+
+**3.如果HUN弹窗不显示，应该是手机端的状态没有恢复导致的，请先重启手机，然后再尝试。**
+
+\
+
+**4.手机一定要在亮屏的状态下测试，灭屏状态下手机不会开启 fast scan**
+
+\
+
+** BBPRO2BUG-21515 - \[BBPro2\]\[RTL8773CO SDK\]\[沃莱特/飞利浦\]\[RHA\]耳机入盒关盖与手机断连后，手机上依旧显示耳机电量信息 Closed **
+
+\
diff --git a/10+initial+pair成功,LE+ACL+link存在,耳机再次进入Pairing+mode,手机弹窗出来点击弹窗配对失败.md b/10+initial+pair成功,LE+ACL+link存在,耳机再次进入Pairing+mode,手机弹窗出来点击弹窗配对失败.md
new file mode 100644
index 0000000..afd5367
--- /dev/null
+++ b/10+initial+pair成功,LE+ACL+link存在,耳机再次进入Pairing+mode,手机弹窗出来点击弹窗配对失败.md
@@ -0,0 +1,11 @@
+# 10 initial pair成功,LE ACL link存在,耳机再次进入Pairing mode,手机弹窗出来点击弹窗配对失败
+
+[BB2BUG-50358] [BB2][RTL8763ESH/ROM][GMI][沃莱特][Harman][T530]759：After clicking the reappeared "fast pair" notification to connect, it prompts that the connection cannot be made（5/5） - Jira
+
+https://partnerissuetracker.corp.google.com/u/0/issues/424368416
+
+\
+
+
+
+\
diff --git a/11+Ringing+using+the+accessory+non-owner+service(dult)+fail.md b/11+Ringing+using+the+accessory+non-owner+service(dult)+fail.md
new file mode 100644
index 0000000..4024bab
--- /dev/null
+++ b/11+Ringing+using+the+accessory+non-owner+service(dult)+fail.md
@@ -0,0 +1,35 @@
+# 11 Ringing using the accessory non-owner service(dult) fail
+
++fail_6f086002.jpg)
+
+\
+
+测试失败的原因是：
+
+ 这个测项是要测试，
+
+1）手机下ring start cmd(0x300)给耳机
+
+2）耳机回复cmd rsp，响铃
+
+3）一段时间后，手机会下ring stop(0x301)
+
+4）耳机回复cmd rsp，停止响铃
+
+但是客户在步骤2之后，主动停止了响铃，导致第三步收到手机ring stop后，耳机没办法成功执行ring stop，因为ring已经被提前停止了，所以耳机会回复invalid state，导致测项失败。
+
++fail_69ce7f34.jpg)
+
+\
+
+请客户听到响铃后，不要操作设备。手机软件上只提示会有铃声响起，没有让用户去停这个铃声
+
++fail_0217de29.jpg)
+
+还有注意的一个点，如果客户配置的铃声很短，以这个测项为例，如果小于5秒，那收到stop之前就播完了，也就没办法被stop，那也会fail spec应该是有些这个铃声的时长要求的 好像是12s
+
+
+
+ BB2BUG-44729 - \[BB2\]\[RTL8763ESH/ROM\]\[GMI\]\[沃莱特\]\[Harman\]\[T135\] Google Finder (Ringing using the accessory non-owner service)项测试failed Closed
+
+修正： https://cn4soc.rtkbf.com/gerrit/c/HoneyComb/+/215092
diff --git a/11+non-LEA动态切换到LEA.md b/11+non-LEA动态切换到LEA.md
new file mode 100644
index 0000000..217af68
--- /dev/null
+++ b/11+non-LEA动态切换到LEA.md
@@ -0,0 +1,18 @@
+# 11 non-LEA动态切换到LEA
+
+Harman T530 non-LEA 和LEA支持动态切换
+
+non-LEA切换到LEA:
+
+不支援legacy CTKD LE的场景：\
+1.non-LEA耳机和手机通过GFPS成功配对leagcy
+
+2.JBL app不配对BLE，JBL app打开之后，点击LEA button 切换到LEA版本
+
+3.耳机重启进入Pairing mode，耳机端不需要清配对信息
+
+4.手机GFPS弹窗出来之后，点击弹窗，手机会先清除之前legacy的配对信息，然后配对BLE，然后LE CTKD legacy生成 legacy linkkey
+
+\
+
+\
diff --git a/12+Pairing+process+error,+Reason_+Not+receive+UUID,+Is+connected_false.md b/12+Pairing+process+error,+Reason_+Not+receive+UUID,+Is+connected_false.md
new file mode 100644
index 0000000..3bb325f
--- /dev/null
+++ b/12+Pairing+process+error,+Reason_+Not+receive+UUID,+Is+connected_false.md
@@ -0,0 +1,79 @@
+# 12 Pairing process error, Reason: Not receive UUID, Is connected:false
+
+目前遇到以下原因，可以逐一排查：
+
+
+
+
+
+- [原因1：可能是手机系统蓝牙出了问题，setting界面 system\>reset options\>reset Bluetooth & wifi , 然后重启手机试试看](#id-12Pairingprocesserror,Reason:NotreceiveUUID,Isconnected:false-原因1：可能是手机系统蓝牙出了问题，setting界面system%3Eresetoptions%3EresetBluetooth&wifi,然后重启手机试试看)
+- [原因2：如果设备端不支援LEA，和支援LEA的手机对测，发现手机不连legacy profile， 需要打开 legacy CTKD LE 的功能](#id-12Pairingprocesserror,Reason:NotreceiveUUID,Isconnected:false-原因2：如果设备端不支援LEA，和支援LEA的手机对测，发现手机不连legacyprofile，需要打开legacyCTKDLE的功能)
+- [原因3： 如果设备端支援LEA，和不支援LEA的手机对测，发现手机不连legacy profile， 需要关闭 legacy CTKD LE 的功能，这个是Google的bug，google 后续会给出修正](#id-12Pairingprocesserror,Reason:NotreceiveUUID,Isconnected:false-原因3：如果设备端支援LEA，和不支援LEA的手机对测，发现手机不连legacyprofile，需要关闭legacyCTKDLE的功能，这个是Google的bug，google后续会给出修正)
+- [原因4：测试账号连的设备太多了，需要定期清除](#id-12Pairingprocesserror,Reason:NotreceiveUUID,Isconnected:false-原因4：测试账号连的设备太多了，需要定期清除)
+ - [4.1 setting界面清掉所有的配对信息 1 gfps/finder 如何清除配对信息 - BT_Market - WIKI](#id-12Pairingprocesserror,Reason:NotreceiveUUID,Isconnected:false-4.1setting界面清掉所有的配对信息1gfps/finder如何清除配对信息-BT_Market-WIKI)
+ - [4.2 Go to Settings \> Google \> All services \> Devices \> Saved devices：](#id-12Pairingprocesserror,Reason:NotreceiveUUID,Isconnected:false-4.2GotoSettings%3EGoogle%3EAllservices%3EDevices%3ESaveddevices：)
+ - [4.2.1 Toggle off Automatically saved devices](#id-12Pairingprocesserror,Reason:NotreceiveUUID,Isconnected:false-4.2.1ToggleoffAutomaticallysaveddevices)
+ - [4.2.2 Wait for about 3 hours, toggling on again.](#id-12Pairingprocesserror,Reason:NotreceiveUUID,Isconnected:false-4.2.2Waitforabout3hours,togglingonagain.)
+ - [4.2.3 Try to do the test again and see if this issue still happens.](#id-12Pairingprocesserror,Reason:NotreceiveUUID,Isconnected:false-4.2.3Trytodothetestagainandseeifthisissuestillhappens.)
+
+
+
+#### 原因1：可能是手机系统蓝牙出了问题，setting界面 system\>reset options\>reset Bluetooth & wifi , 然后重启手机试试看
+
+
+
+\
+
+#### 原因2：如果设备端不支援LEA，和支援LEA的手机对测，发现手机不连legacy profile， 需要打开 legacy CTKD LE 的功能
+
+1 GFPS legacy pair 搭配支援LEA手机不连 legacy profile(A2DP/HFP) - BT_Market - WIKI
+
+#### 原因3： 如果设备端支援LEA，和不支援LEA的手机对测，发现手机不连legacy profile， 需要关闭 legacy CTKD LE 的功能，这个是Google的bug，google 后续会给出修正
+
+4 pixel6(android 12) 不连A2DP - BT_Market - WIKI
+
+\
+
+\
+
+https://partnerissuetracker.corp.google.com/u/0/issues/443202640
+
+https://partnerissuetracker.corp.google.com/u/0/issues/445592517
+
+
+
+\
+
+手机没有来连legacy profile：
+
+Line 32281: 0002123 09-05#11:00:37.169 194 0009843.085 \[APP\] !\*\*connected: b2s, bd_addr 88::54::1F::10::0C::5F, profs 0x00000000\
+Line 34379: 0004221 09-05#11:00:38.529 169 0011221.541 \[ENGAGE\] connected: b2s, bd_addr 88::54::1F::10::0C::5F, profs 0x00000000\
+Line 34741: 0004583 09-05#11:00:38.607 203 0011285.575 \[ENGAGE\] connected: b2s, bd_addr 88::54::1F::10::0C::5F, profs 0x00000000\
+Line 35042: 0004883 09-05#11:00:38.700 095 0011358.903 \[ENGAGE\] connected: b2s, bd_addr 88::54::1F::10::0C::5F, profs 0x00000000
+
+\
+
+[BB2BUG-52175] [BB2][D-CUT][8763EKH][Harman][T530][v3.13.2.20+Test bin] Fast pair Validator APP测试，Personalized Name Update Test Fail - Jira
+
+[BB2BUG-52173] [BB2][D-CUT][8763EKH][Harman][T530][v3.13.2.20+Test bin] Fast pair Validator APP测试，Ringing A Device with classic profile connection Test Fail - Jira
+
+[BB2BUG-52194] [BB2][D-CUT][8763EKH][Harman][T530][v3.13.2.20+Test bin] Fast pair Validator APP测试，Key Based Request Fiags Reserved Bit verification Test Fail - Jira
+
+\
+
+#### 原因4：测试账号连的设备太多了，需要定期清除
+
+##### 4.1 setting界面清掉所有的配对信息 1 gfps/finder 如何清除配对信息 - BT_Market - WIKI
+
+##### **4.2 Go to `Settings > Google > All services > Devices > Saved devices：`**
+
+###### ** 4.2.1 Toggle off `Automatically saved devices`**
+
+###### ** 4.2.2 Wait for about 3 hours, toggling on again.**
+
+###### ** 4.2.3 Try to do the test again and see if this issue still happens.**
diff --git a/12+Pairing+process+error.+Reason_+Only+receive+correct+UUID+from+1+address.md b/12+Pairing+process+error.+Reason_+Only+receive+correct+UUID+from+1+address.md
new file mode 100644
index 0000000..ab1acff
--- /dev/null
+++ b/12+Pairing+process+error.+Reason_+Only+receive+correct+UUID+from+1+address.md
@@ -0,0 +1,5 @@
+# 12 Pairing process error. Reason: Only receive correct UUID from 1 address
+
+
+
+[BBPRO3BUG-27045] [BBPRO3][EVB][E Cut][PEGA_HA_v1.0.4_20251106][24110 testbin][GFPS][FastPair][LEA phone]Personalized Name Update 测试 fail - Jira
diff --git a/12+Pairing+process+error_+Reason_+Is+connected+false.md b/12+Pairing+process+error_+Reason_+Is+connected+false.md
new file mode 100644
index 0000000..13e8bd2
--- /dev/null
+++ b/12+Pairing+process+error_+Reason_+Is+connected+false.md
@@ -0,0 +1,60 @@
+# 12 Pairing process error: Reason: Is connected false
+
+目前遇到以下原因，可以逐一排查：
+
+
+
+
+
+- [原因1：可能是手机系统蓝牙出了问题，setting界面 system\>reset options\>reset Bluetooth & wifi , 然后重启手机试试看](#id-12Pairingprocesserror:Reason:Isconnectedfalse-原因1：可能是手机系统蓝牙出了问题，setting界面system%3Eresetoptions%3EresetBluetooth&wifi,然后重启手机试试看)
+- [原因2：如果设备端不支援LEA，和支援LEA的手机对测，发现手机不连legacy profile， 需要打开 legacy CTKD LE 的功能](#id-12Pairingprocesserror:Reason:Isconnectedfalse-原因2：如果设备端不支援LEA，和支援LEA的手机对测，发现手机不连legacyprofile，需要打开legacyCTKDLE的功能)
+- [原因3： 如果设备端支援LEA，和不支援LEA的手机对测，发现手机不连legacy profile， 需要关闭 legacy CTKD LE 的功能，这个是Google的bug，google 后续会给出修正](#id-12Pairingprocesserror:Reason:Isconnectedfalse-原因3：如果设备端支援LEA，和不支援LEA的手机对测，发现手机不连legacyprofile，需要关闭legacyCTKDLE的功能，这个是Google的bug，google后续会给出修正)
+- [原因4：测试账号连的设备太多了，需要定期清除](#id-12Pairingprocesserror:Reason:Isconnectedfalse-原因4：测试账号连的设备太多了，需要定期清除)
+ - [4.1 setting界面清掉所有的配对信息 1 gfps/finder 如何清除配对信息 - BT_Market - WIKI](#id-12Pairingprocesserror:Reason:Isconnectedfalse-4.1setting界面清掉所有的配对信息1gfps/finder如何清除配对信息-BT_Market-WIKI)
+ - [4.2 Go to Settings \> Google \> All services \> Devices \> Saved devices：](#id-12Pairingprocesserror:Reason:Isconnectedfalse-4.2GotoSettings%3EGoogle%3EAllservices%3EDevices%3ESaveddevices：)
+ - [4.2.1 Toggle off Automatically saved devices](#id-12Pairingprocesserror:Reason:Isconnectedfalse-4.2.1ToggleoffAutomaticallysaveddevices)
+ - [4.2.2 Wait for about 3 hours, toggling on again.](#id-12Pairingprocesserror:Reason:Isconnectedfalse-4.2.2Waitforabout3hours,togglingonagain.)
+ - [4.2.3 Try to do the test again and see if this issue still happens.](#id-12Pairingprocesserror:Reason:Isconnectedfalse-4.2.3Trytodothetestagainandseeifthisissuestillhappens.)
+
+
+
+#### 原因1：可能是手机系统蓝牙出了问题，setting界面 system\>reset options\>reset Bluetooth & wifi , 然后重启手机试试看
+
+
+
+\
+
+#### 原因2：如果设备端不支援LEA，和支援LEA的手机对测，发现手机不连legacy profile， 需要打开 legacy CTKD LE 的功能
+
+1 GFPS legacy pair 搭配支援LEA手机不连 legacy profile(A2DP/HFP) - BT_Market - WIKI
+
+\
+
+
+
+\
+
+#### 原因3： 如果设备端支援LEA，和不支援LEA的手机对测，发现手机不连legacy profile， 需要关闭 legacy CTKD LE 的功能，这个是Google的bug，google 后续会给出修正
+
+4 pixel6(android 12) 不连A2DP - BT_Market - WIKI
+
+\
+
+#### 原因4：测试账号连的设备太多了，需要定期清除
+
+##### 4.1 setting界面清掉所有的配对信息 1 gfps/finder 如何清除配对信息 - BT_Market - WIKI
+
+##### **4.2 Go to `Settings > Google > All services > Devices > Saved devices：`**
+
+###### ** 4.2.1 Toggle off `Automatically saved devices`**
+
+###### ** 4.2.2 Wait for about 3 hours, toggling on again.**
+
+###### ** 4.2.3 Try to do the test again and see if this issue still happens.**
+
+\
diff --git a/13+手机端显示名字为乱码.md b/13+手机端显示名字为乱码.md
new file mode 100644
index 0000000..30a75df
--- /dev/null
+++ b/13+手机端显示名字为乱码.md
@@ -0,0 +1,9 @@
+# 13 手机端显示名字为乱码
+
+请先帮忙按照如下wiki验证加解密算法，如果加解密算法没有问题 那就很可能是手机的问题
+
+https://wiki.realtek.com/display/Bee1/gfps_lib_test
+
+ BUMBEEBUG-8940 - \[BBlite\]\[8773BFE\]\[1.8.3.4\]\[禾馳\]\[協宜\]\[帝品\]:GFPS连接后，蓝牙名处显示乱码 Closed
+
+ BBPRO3BUG-350 - \[BBPRO3\]\[EVB\]\[release_1220\]\[GFPS\]Naming测试之后，手机与RWS配对，RWS名字不对 Closed
diff --git a/14+Initial+Pair+with+(XX_XX_)+fail.md b/14+Initial+Pair+with+(XX_XX_)+fail.md
new file mode 100644
index 0000000..8f75288
--- /dev/null
+++ b/14+Initial+Pair+with+(XX_XX_)+fail.md
@@ -0,0 +1,7 @@
+# 14 Initial Pair with (XX:XX:) fail
+
++fail_77955b5d.jpg)
+
+\
+
+[BBPRO3BUG-27064] [BBPRO3][EVB][E Cut][PEGA_HA_v1.0.4_20251106][24110 testbin][GFPS][FastPair][LEA phone]Personalized Name with Provider First Time Pairing 测试fail - Jira
diff --git a/14+Initialize+fast+pair+service+failed.md b/14+Initialize+fast+pair+service+failed.md
new file mode 100644
index 0000000..176ebc8
--- /dev/null
+++ b/14+Initialize+fast+pair+service+failed.md
@@ -0,0 +1,70 @@
+# 14 Initialize fast pair service failed
+
+Google一开始的答复是我们的测试账号没有加入test group, 但是我们的测试账号是已经加入到test group的
+
+后面樊晨换个手机测试又复现不到了，
+
+但是后面再测试 GG09(pixel4xl), GG27(pixel6) 复现概率也还是很高的，并且复现之后很长一段时间不能测试
+
+不知道是不是和Google网络有关系
+
+Google最后给的答复是和网络有关系：
+
+\
+
+Hi Danni,
+
+According to Comment #7, this issue appears unrelated to the Validator itself, but rather to the synchronization process with the GMS server-side.
+
+This is the first time I've encountered this specific kind of issue.\
+I recall you mentioning that it started suddenly during your testing.\
+Therefore, it might not be related to the factory reset scenario as described in b/409388435#comment6.
+
+You've only encountered this issue recently, right?\
+Is it possible you've made any recent changes to your Wi-Fi connection settings?\
+For example, a firewall setting?\
+I suspect such a change could be affecting the synchronization with the GMS server.
+
+\
+
+**最终找到原因是因为QC实验室的Google网络开了防火墙：**
+
+
+
+\
+
+\
+
+**对比试验，测试过程中遇到该问题后，**
+
+**在google-》所有服务-》设备中关闭自动保存设备选项后，大概率可以测试通过， **
+
+**Fast pair validator 测试的时候可以关掉， 但是手动测试必须打开**
+
+\
+
+\
+
+
+
+https://partnerissuetracker.corp.google.com/u/0/issues/444061781
+
+\
+
+\
+
+
+
+\
+
+
+
+\
+
+\
+
+\
+
+
+
+\
diff --git a/14+subsequent+pairing手机提示+“无法连接，请尝试让设备进入配对模式”.md b/14+subsequent+pairing手机提示+“无法连接，请尝试让设备进入配对模式”.md
new file mode 100644
index 0000000..b8d2e54
--- /dev/null
+++ b/14+subsequent+pairing手机提示+“无法连接，请尝试让设备进入配对模式”.md
@@ -0,0 +1,7 @@
+# 14 subsequent pairing手机提示 “无法连接，请尝试让设备进入配对模式”
+
+原因很有可能是耳机不在connectable mode。
+
+jira:
+
+ BBPRO3BUG-390 - \[BBPRO3\]\[EVB\]\[release_1220\]\[GFPS\]Subsequent Pairing Failed Preview
diff --git a/15+GFPS+TWS+mode+测试ring功能的时候+++手机端只显示一个耳机设备.md b/15+GFPS+TWS+mode+测试ring功能的时候+++手机端只显示一个耳机设备.md
new file mode 100644
index 0000000..db00c6d
--- /dev/null
+++ b/15+GFPS+TWS+mode+测试ring功能的时候+++手机端只显示一个耳机设备.md
@@ -0,0 +1,55 @@
+# 15 GFPS TWS mode 测试ring功能的时候 手机端只显示一个耳机设备
+
+HIHI Danni
+
+請教下您知道這個 find me 設定TWS mode or 立体声 headset mode 的地方是在哪邊嗎？
+
+
+
+\[17:44\] Barry Chu
+
+AT 預期應該是要 TWS， 但是只顯示一个响铃设备
+
+\[17:44\] Barry Chu
+
+
+
+\[17:45\] Barry Chu
+
+看起來這段應該是沒甚麼問題 對嗎 ? 要請他們檢查 註冊時後填的資料嗎
+
+\[17:45\] 董丹丹
+
+手机端好像没有设置的地方，就是查我们的components
+
+\[17:45\] 董丹丹
+
+b2b是有连着的吗
+
+\[17:46\] Barry Chu
+
+應該是有連著的
+
+\[17:46\] 董丹丹
+
+是不是手机显示的问题呀
+
+\[17:46\] Barry Chu
+
+應該不是欸
+
+他們用 BBLite 量產的就有看到 TWS
+
+
+
+\[17:54\] 董丹丹
+
+注册model id的时候 是填写的TWS 耳机还是 立体声耳机呀
+
+\[17:54\] 董丹丹
+
+是这个model id 都会显示一个设备吗，很可能是注册model id 的时候填写的信息不对
+
+
+
+\
diff --git a/15+app_gfps_check_receive_pair_req_+receive_pair_req+0.md b/15+app_gfps_check_receive_pair_req_+receive_pair_req+0.md
new file mode 100644
index 0000000..09e91cb
--- /dev/null
+++ b/15+app_gfps_check_receive_pair_req_+receive_pair_req+0.md
@@ -0,0 +1,50 @@
+# 15 app_gfps_check_receive_pair_req: receive_pair_req 0
+
+**测试场景：**
+
+**手机和耳机之前配对过， 并且手机和耳机都不清除配对信息**
+
+当耳机打discoverable adv时(耳机重新进入pairing mode)，手机会回连耳机，BR/EDR link和 LE link 都会建立, 但是没有passkey信息的交互，BR/EDR不会重新走配对流程，但是会走加密流程。
+
+LE Link上面会交互 key based pairing characteristic ,personalized name characteristic, account key characteristic 信息，但是因为手机和耳机之前配过，所以LE link是不会交互pass key 信息的.
+
+而且此时交互的account key和配对时交互的account key是一样的，也就是说，当手机回连耳机时， LE Link上面交互的account key信息是不会改变的,和配对时交互的account key一样。
+
+\
+
+针对这种场景， 因为不会重新配对，所以gfps_db.receive_pair_req 始终是false， 耳机端就会触发timeout: 0004492 11-14#13:59:24.967 091 0050428.009 \[APP\] !\*\*app_gfps_check_receive_pair_req: receive_pair_req 0, p_le_link 0x2c0ac4//
+
+但其实这种场景属于回连的情况，所以我们会在收到account key之后设置 gfps_db.receive_pair_req为 true
+
+\
+
+APP-rws: modify gfps reconnect flow (267318) · Gerrit Code Review
+
+app_gfps_cb_handle_accountkey:
+
+
+
+
+
+
+ Line 29527: 0009420 11-17#13:56:53.591 048 0024690.632 [APP] !**app_gfps_cb_handle_kbp_write_req: provider bond 0, notify name 1, retroactively 1, pk exist 1, accountkey idx 0, provider addr 78::3F::8E::E0::84::67, seek addr C4::77::64::DE::EC::70
+ Line 29528: 0009421 11-17#13:56:53.591 049 0024690.853 [OS] !**create timer address:2072a8, name:app_gfps_timer_retroactively_check_accountkey, number:255
+ Line 29529: 0009422 11-17#13:56:53.591 050 0024691.000 [APP] !**app_gfps_cb_handle_kbp_write_req: p_curr_br_link 0x2c093c, p_curr_le_link 0x2c0ac4
+ Line 29530: 0009423 11-17#13:56:53.591 051 0024691.089 [OS] !**create timer address:207b18, name:app_gfps_timer_check_receive_pair_req, number:256
+ Line 29531: 0009424 11-17#13:56:53.591 052 0024691.293 [APP] app_gfps_personalized_name_read: personalized_name in ftl 小虎的JBL Tune 530BT, stored_personalized_name_len 23, is_valid 1
+ Line 29552: 0009445 11-17#13:56:53.591 073 0024702.862 [APP] !**gfps_ase_ctr_concat: input_data E5 B0 8F E8 99 8E E7 9A 84 4A 42 4C 20 54 75 6E 65 20 35 33 30 42 54
+ Line 29555: 0009448 11-17#13:56:53.591 076 0024703.056 [APP] !**gfps_ase_ctr_concat: output_data[23] 92 00 D0 F6 71 DA 51 A3 B9 35 9A 81 D9 3B DD AA 42 8B F9 D9 28 3A 78
+ Line 29556: 0009449 11-17#13:56:53.591 077 0024703.813 [APP] !**gfps_hmac_sha256: 75 5F 52 FC 8D 10 B9 A7
+ Line 29562: 0009455 11-17#13:56:53.591 084 0024705.560 [APP] gfps_send_personalized_name: success name 小虎的JBL Tune 530BT, input_nonce FD B6 C6 D3 7E D8 A8 D8, name_packet 75 5F 52 FC 8D 10 B9 A7 FD B6 C6 D3 7E D8 A8 D8 92 00 D0 F6 71 DA 51 A3 B9 35 9A 81 D9 3B DD AA 42 8B F9 D9 28 3A 78
+ Line 29563: 0009456 11-17#13:56:53.591 085 0024705.619 [APP] !** app_gfps_personalized_name_send: is_send = 1
+ Line 29564: 0009457 11-17#13:56:53.591 086 0024705.678 [APP] !**gfps_send_kbp_response_le: le_device_support 1, le_device_mode 1
+ Line 29574: 0009467 11-17#13:56:53.591 096 0024719.636 [APP] !**gfps_send_kbp_response_le: raw response 02 40 01 B8 17 43 1C C6 EF 11 AE 7B EE 85 2F C8, encrypt response 59 2E 9E 8A DD F6 E3 E6 C9 AC 49 61 8E 4F D7 38
+ Line 29651: 0009544 11-17#13:56:53.667 177 0024786.848 [APP] !**gfps_handle_char_account_key: encrypted key EF B3 B6 56 D5 C8 F8 47 D5 50 F6 DB D1 15 84 D7, decrypted key 04 F6 8F 7F 48 C9 3A 4E 34 19 2A 27 13 AB 6F 7D
+ Line 29652: 0009545 11-17#13:56:53.667 178 0024787.043 [APP] [Warning! Mismatched parameter type "BDAddr" and symbol "%b"] !**app_gfps_account_key_store: bd_addr C4::77::64::DE::EC::70 already exist, key update index i 0, key 04 3D 38 34 86 FB 35 6A 23 19 4E 83 70 05 66 90
+ Line 29653: 0009546 11-17#13:56:53.667 179 0024787.072 [APP] !**gfps_get_owner_key_valid: 1
+ Line 29654: 0009547 11-17#13:56:53.667 180 0024787.136 [APP] [Warning! Mismatched parameter type "BDAddr" and symbol "%b"] !**app_gfps_account_key_store: bd_addr C4::77::64::DE::EC::70 already exist, key update index i 1, key 04 1C BC F4 B4 70 31 BB 0D 52 45 56 1D 34 D7 C1
+ Line 29655: 0009548 11-17#13:56:53.667 181 0024787.154 [APP] !**gfps_get_owner_key_valid: 1
+ Line 29739: 0009632 11-17#13:56:53.668 009 0024792.569 [APP] !**app_gfps_account_key_remote_add |
+
+
+
diff --git a/16+!!!app_gfps_cb_handle_accountkey_+account_key_write_counts+2.md b/16+!!!app_gfps_cb_handle_accountkey_+account_key_write_counts+2.md
new file mode 100644
index 0000000..17425b3
--- /dev/null
+++ b/16+!!!app_gfps_cb_handle_accountkey_+account_key_write_counts+2.md
@@ -0,0 +1,22 @@
+# 16 !!!app_gfps_cb_handle_accountkey: account_key_write_counts 2
+
+google spec 上是说一分钟内不可以连续写多个account key, 但是客户在一分钟内做了两次retroactive pair，写了两次account key
+
+不过两次retroactive pair中间有LE断线，我预期会在LE 断线之后将gfps_db.account_key_write_counts 设置成0
+
+
+
+
+
+
+ 11-19#11:41:21.302 177 0059462.784 [APP] !**gfps_handle_char_account_key: encrypted key FF 27 E5 C8 1B 8D DD A3 FE 00 57 2D D3 21 31 27, decrypted key 04 97 A5 FB 2F 8D 3A DB 22 DE 40 2B C2 74 3F 41
+ 11-19#11:41:21.302 178 0059462.890 [APP] !!!app_gfps_cb_handle_accountkey: account_key_write_counts 2
+//timer_id 2: APP_GFPS_TIMER_CHECK_RECEIVE_PAIR_REQ
+11-19#11:41:31.109 218 0069286.523 [APP] app_gfps_timer_timeout_cb: timer_id 2, timer_chann 0
+ 11-19#11:41:31.109 219 0069286.613 [APP] app_ble_gap_disconnect: conn_id 0, disc_cause 19
+ 11-19#11:41:31.109 220 0069286.656 [GAP] !**le_disconnect_with_reason: conn_id 0, reason 19 |
+
+
+
+
+
diff --git a/16+手机端测试响铃功能时，找不到响铃的按键.md b/16+手机端测试响铃功能时，找不到响铃的按键.md
new file mode 100644
index 0000000..d7bef50
--- /dev/null
+++ b/16+手机端测试响铃功能时，找不到响铃的按键.md
@@ -0,0 +1,31 @@
+# 16 手机端测试响铃功能时，找不到响铃的按键
+
+正常手机端响铃按键在如下位置
+
+
+
+\
+
+有的客户测试的时候说是手机端UI上找不到 Ring Right或者是Ring Left的按键
+
+很可能是客户注册model id的时候没有勾选Support Ring Device
+
+
+
+\
+
+ BB2BUG-15892 - \[BB2\]\[C-CUT\]\[8763EF\]\[HARMAN\] BT520_GFPS_尋找耳機測試,可連線但無出現提示音 Closed
+
+ BB2BUG-17511 - \[BB2\]\[C-CUT\]\[8763EF\]\[HARMAN\] BT520_GFPS_Initial Pairing 彈窗 Closed
+
+\
+
+如果确定model id 配置的没有问题，并且有勾选 Support Ringing Device, 可以查看log看手机有没有来查询Active Components
+
+
+
+以及Provided 回复的Active Components是否正确
+
+
+
+Retroactive Pair之后没办法使用响铃功能 - BT_Market - WIKI
diff --git a/2+BREDR+++GFPS+++Find+hub.md b/2+BREDR+++GFPS+++Find+hub.md
new file mode 100644
index 0000000..ed93785
--- /dev/null
+++ b/2+BREDR+++GFPS+++Find+hub.md
@@ -0,0 +1,3 @@
+# 2 BREDR + GFPS + Find hub
+
+该功能是通过GFPS快速配对BREDR， 并实现查找功能(类似苹果的findmy)
diff --git a/2+Enable+new+feature+test+in+Validator.md b/2+Enable+new+feature+test+in+Validator.md
new file mode 100644
index 0000000..cc79a15
--- /dev/null
+++ b/2+Enable+new+feature+test+in+Validator.md
@@ -0,0 +1,23 @@
+# 2 Enable new feature test in Validator
+
+**Device actions which can be verified validator app: personalized name and retroactive pairing**
+
+**How to enable new feature test in validator**:
+
+安装adb:[adb安装及使用方法](/pages/viewpage.action?pageId=87464469) 该wiki上提供的adb版本太旧，会出现device offline的问题，下载最新的https://adbshell.com/downloads
+
+安装adb之后找到adb.exe所在的目录，在该目录下打开cmd命令行
+
+输入如下命令：
+
+adb shell am broadcast -a com.google.location.nearby.apps.fastpair.validator.FLAG_OVERRIDE --es flag enable_features_for_v3 --es value true --es type boolean com.google.location.nearby.apps.fastpair.validator
+
+
+
+按enter执行命令。
+
+命令执行成功之后，打开fast pair validator 能看到新的feature，如下图红框所示。
+
+界面如下图所示， 红框内是新增的测项：
+
+\
diff --git a/2+Scan_Connected+timing+测试fail.md b/2+Scan_Connected+timing+测试fail.md
new file mode 100644
index 0000000..fef2b50
--- /dev/null
+++ b/2+Scan_Connected+timing+测试fail.md
@@ -0,0 +1,7 @@
+# 2 Scan/Connected timing 测试fail
+
+
+
+
+
+spec 说这个测项不是强制的，需要和google 确认
diff --git a/2+UI显示设备已关联到其他人的账号.md b/2+UI显示设备已关联到其他人的账号.md
new file mode 100644
index 0000000..4b691d7
--- /dev/null
+++ b/2+UI显示设备已关联到其他人的账号.md
@@ -0,0 +1,35 @@
+# 2 UI显示设备已关联到其他人的账号
+
+[BB2BUG-50316] [BB2][RTL8763ESH/ROM][GMI][沃莱特/MINAMI][Harman][Pace][JBLES2-1895][Finder] 首次通过GFP连接的时候，跳过添加到Finder，取消配对耳机，重新配对的时候就无法添加耳机，现在已经被其他账号添加 - Jira
+
+点击 ”移除上一任所有者”， 之后再测试
+
+
+
+如果移除上一任所有者之后，测试依然有问题， 麻烦请客户确认：开始测试之前耳机端一定要做factory reset 清除配对信息， 手机端也要清除配对信息 参考wiki 17 gfps/finder 如何清除配对信息 - BT_Market - WIKI
+
+\
+
+[BB2BUG-50316] [BB2][RTL8763ESH/ROM][GMI][沃莱特/MINAMI][Harman][Pace][JBLES2-1895][Finder] 首次通过GFP连接的时候，跳过添加到Finder，取消配对耳机，重新配对的时候就无法添加耳机，现在已经被其他账号添加 - Jira
+
+\
+
+//因为没有做factory reset， 所以owner account key一直处于valid的状态
+
+Line 16206: 0006198 06-11#13:34:18.321 213 0080765.751 \[APP\] gfps_finder_get_owner_accountkey: valid 1, key 04 A8 4A AA F5 4E 8D 73 37 92 EF 94 D4 D1 47 71
+
+Line 16291: 0006283 06-11#13:34:18.510 093 0080966.054 \[APP\] gfps_finder_get_owner_accountkey: valid 1, key 04 A8 4A AA F5 4E 8D 73 37 92 EF 94 D4 D1 47 71
+
+Line 17957: 0007949 06-11#13:34:30.696 143 0093070.146 \[APP\] gfps_finder_get_owner_accountkey: valid 1, key 04 A8 4A AA F5 4E 8D 73 37 92 EF 94 D4 D1 47 71
+
+ Line 18023: 0008012 06-11#13:34:30.944 102 0093334.534 \[APP\] gfps_finder_get_owner_accountkey: valid 1, key 04 A8 4A AA F5 4E 8D 73 37 92 EF 94 D4 D1 47 71
+
+ Line 29610: 0009598 06-11#13:35:05.871 166 0127806.495 \[APP\] gfps_finder_get_owner_accountkey: valid 1, key 04 A8 4A AA F5 4E 8D 73 37 92 EF 94 D4 D1 47 71
+
+//因为没有做factory reset，耳机端有配对信息，所以finder处于provisioned的状态
+
+0009657 06-11#13:35:05.876 239 0127815.863 \[APP\] gfps_finder_rsp_beacon_provision_state: flag 3
+
+//进而手机端显示已关联到其他人的账号
+
+\
diff --git a/2.+耳机不支援LEA,+手机支援LEA.md b/2.+耳机不支援LEA,+手机支援LEA.md
new file mode 100644
index 0000000..7df3532
--- /dev/null
+++ b/2.+耳机不支援LEA,+手机支援LEA.md
@@ -0,0 +1,63 @@
+# 2. 耳机不支援LEA, 手机支援LEA
+
+
+
+
+
+**测试手机支援LEA, 开发者选项中将 Bypass Bluetooth LE Audio 选项关掉，然后重启手机，再重新测试，好像就不会遇到上面截图对应的问题了**
+
+****
+
+[BB2BUG-49617] [BB2][RTL8763ESH/ROM][GMI][沃莱特][Harman][T530] [finder] 455-[LEA][Finder]EIK rotation Automated test fail - Jira
+
+https://partnerissuetracker.corp.google.com/u/0/issues/420766718
+
+#### hi Mark:\
+\
+‘EIK Rotation’ test fail, can you help see the reason, thanks.\
+\
+test fail screen: Fail_screen.jpg\
+18:24:26 BLE connected\
+After BLE is connected, there is no service discovery and no reading beacon parameters,\
+and the connection is immediately disconnected;
+
+\
+
+\
+
+#### gmark@google.com\google.com\> #2May 28, 2025 03:40PM
+
+Reassigned to android-bluetooth@google.com.
+
+**To android-bluetooth@ - per HCI service discovery not perofrmed, yet onServicesDiscovered() is called. The GATT connection does not seem functional after that.**
+
+ // Validator calls BluetoothDevice.connectGatt()
+ 05-27 18:24:26.853 I GattClientImpl: BluetoothDevice.connectGatt() - 00:00:00:00:00:0D [CONTEXT service_id=284 ]
+
+ // This follows to BluetoothDevice.connectGatt() calls, apparently one made by another app at the same time.
+
+ 05-27 18:24:26.853 D BluetoothGatt: connect() - device: XX:XX:XX:XX:00:0D, auto: false
+ 05-27 18:24:26.853 D BluetoothGatt: registerApp()
+ 05-27 18:24:26.854 D BluetoothGatt: registerApp() - UUID=8f31e253-d3a8-492f-9165-d806b6c95c32
+ 05-27 18:24:26.856 D BluetoothGatt: onClientRegistered() - status=0 clientIf=14
+
+ 05-27 18:24:26.976 D BluetoothGatt: connect() - device: XX:XX:XX:XX:00:0D, auto: false
+ 05-27 18:24:26.976 D BluetoothGatt: registerApp()
+ 05-27 18:24:26.976 D BluetoothGatt: registerApp() - UUID=b48ee071-2016-4f0e-8e65-815a00cec43b
+ 05-27 18:24:26.988 D BluetoothGatt: onClientConnectionState() - status=0 clientIf=14 device=00:00:00:00:00:0D
+ 05-27 18:24:26.989 D BluetoothGatt: onClientRegistered() - status=0 clientIf=16
+
+ 05-27 18:24:26.989 I GattClientImpl: Bluetooth connection state changed, status: GATT_SUCCESS, state: 2 - 00:00:00:00:00:0D [CONTEXT service_id=284 ]
+ 05-27 18:24:26.990 D BluetoothGatt: requestConnectionPriority() - params: 0
+
+ // BluetoothDevice.discoverServices() called. There's also a second call to this API. From HCI service discovery is not in fact performed.
+ // onServicesDiscovered() is invoked right away
+ 05-27 18:24:26.991 I GattClientImpl: discoverServices() - 00:00:00:00:00:0D [CONTEXT service_id=284 ]
+ 05-27 18:24:26.992 D BluetoothGatt: discoverServices() - device: XX:XX:XX:XX:00:0D
+ 05-27 18:24:26.997 D BluetoothGatt: onClientConnectionState() - status=0 clientIf=16 device=00:00:00:00:00:0D
+ 05-27 18:24:26.998 D BluetoothGatt: discoverServices() - device: XX:XX:XX:XX:00:0D
+ 05-27 18:24:27.001 D BluetoothGatt: onSearchComplete() = Device=00:00:00:00:00:0D Status=0
+ 05-27 18:24:27.001 I GattClientImpl: onServicesDiscovered() - 00:00:00:00:00:0D [CONTEXT service_id=284 ]
+
+ // bluetoothGatt.writeDescriptor(Descriptor) returns false
+ 05-27 18:24:27.101 I ValidatorImpl: Asynchronously failing: Error performing GATT operation (fe2c1238-8366-4814-8eb0-01de32100bea SUBSCRIBE_TO_NOTIFICATIONS returned false)
diff --git a/2.1+!!!gfps_handle_char_kbp_+failed,+result+3.md b/2.1+!!!gfps_handle_char_kbp_+failed,+result+3.md
new file mode 100644
index 0000000..881d2b6
--- /dev/null
+++ b/2.1+!!!gfps_handle_char_kbp_+failed,+result+3.md
@@ -0,0 +1,13 @@
+# 2.1 !!!gfps_handle_char_kbp: failed, result 3
+
+COM8_2023-05-24_10-51-54.log
+
+
+
+原因是 model id注册成功之后， google 会提供注册的model id以及对应的public key和 private key。
+
+mcu cfg tool 输入的public key/private key不正确, 或者是输入的public key/ private key和model id 不匹配. 耳机端log就会提示 !!!gfps_handle_char_kbp: failed, result 3
+
+请check 是不是 model id， public key, private key 输入错误。
+
+
diff --git a/2.1+Project+工程enable对应功能.md b/2.1+Project+工程enable对应功能.md
new file mode 100644
index 0000000..7909745
--- /dev/null
+++ b/2.1+Project+工程enable对应功能.md
@@ -0,0 +1,49 @@
+# 2.1 Project 工程enable对应功能
+
+app_flags.h 里面找到 CONFIG_REALTEK_GFPS_XXX 相关的宏并按照以下信息配置：
+
+\#define CONFIG_REALTEK_GFPS_FEATURE_SUPPORT 1\
+\#define CONFIG_REALTEK_GFPS_LE_DEVICE_SUPPORT (0 && CONFIG_REALTEK_GFPS_FEATURE_SUPPORT)\
+\#define CONFIG_REALTEK_GFPS_SASS_SUPPORT (0 && CONFIG_REALTEK_GFPS_FEATURE_SUPPORT)\
+\#define CONFIG_REALTEK_GFPS_FINDER_SUPPORT (1 && CONFIG_REALTEK_GFPS_FEATURE_SUPPORT)
+
+GFPS依赖的其他的模块：
+
+\#if CONFIG_REALTEK_GFPS_FEATURE_SUPPORT\
+\#undef F_APP_RWS_BLE_USE_RPA_SUPPORT\
+\#define F_APP_RWS_BLE_USE_RPA_SUPPORT 1
+
+\#undef F_APP_SC_KEY_DERIVE_SUPPORT\
+\#define F_APP_SC_KEY_DERIVE_SUPPORT 1
+
+\#if CONFIG_REALTEK_GFPS_FINDER_SUPPORT\
+\#undef F_APP_PERIODIC_WAKEUP\
+\#define F_APP_PERIODIC_WAKEUP 0// default not enable\
+\#endif\
+\#endif
+
+\
+
+Note:
+
+有的IC宏的名字是 GFPS_XXX, app_flags.h 里面找到 GFPS_XXX 相关的宏并按照以下信息配置：
+
+\#define GFPS_FEATURE_SUPPORT 1\
+\#define GFPS_LE_DEVICE_SUPPORT (0 && GFPS_FEATURE_SUPPORT)\
+\#define GFPS_SASS_SUPPORT (0 && GFPS_FEATURE_SUPPORT)\
+\#define GFPS_FINDER_SUPPORT (1 && GFPS_FEATURE_SUPPORT)
+
+GFPS依赖的其他的模块：
+
+\#if GFPS_FEATURE_SUPPORT\
+\#undef F_APP_RWS_BLE_USE_RPA_SUPPORT\
+\#define F_APP_RWS_BLE_USE_RPA_SUPPORT 1
+
+\#undef F_APP_SC_KEY_DERIVE_SUPPORT\
+\#define F_APP_SC_KEY_DERIVE_SUPPORT 1
+
+\#if GFPS_FINDER_SUPPORT\
+\#undef F_APP_PERIODIC_WAKEUP\
+\#define F_APP_PERIODIC_WAKEUP 0// default not enable\
+\#endif\
+\#endif
diff --git a/2.2+Provider+send+kbp+rsp+but+seeker+disconnect+BLE+link.md b/2.2+Provider+send+kbp+rsp+but+seeker+disconnect+BLE+link.md
new file mode 100644
index 0000000..31cd4c8
--- /dev/null
+++ b/2.2+Provider+send+kbp+rsp+but+seeker+disconnect+BLE+link.md
@@ -0,0 +1,3 @@
+# 2.2 Provider send kbp rsp but seeker disconnect BLE link
+
+ BB2BUG-20554 - \[BB2\]\[8773ESL\]\[v3.13.0.8\]\[GFPS\]\[LE Audio\] 手机与耳机配对失败，手机端提示Couldn't connect Closed
diff --git a/2.2+测试环境搭建.md b/2.2+测试环境搭建.md
new file mode 100644
index 0000000..839c87b
--- /dev/null
+++ b/2.2+测试环境搭建.md
@@ -0,0 +1 @@
+# 2.2 测试环境搭建
diff --git a/2.2.1+设备端环境搭建.md b/2.2.1+设备端环境搭建.md
new file mode 100644
index 0000000..bd85b95
--- /dev/null
+++ b/2.2.1+设备端环境搭建.md
@@ -0,0 +1,306 @@
+# 2.2.1 设备端环境搭建
+
+
+
+
+
+- [1 MCUConfigTool 配置](#id-2.2.1设备端环境搭建-1MCUConfigTool配置)
+ - [1.1 General 页面 : 不勾选 Enable auto power off, 不勾选 Enable pairing timeout 修改为了便于GFPS测试，GFPS 测试的时候或者是过认证的时候需要修改， 量产时可以考虑不修改。](#id-2.2.1设备端环境搭建-1.1General页面:不勾选Enableautopoweroff,不勾选Enablepairingtimeout修改为了便于GFPS测试，GFPS测试的时候或者是过认证的时候需要修改，量产时可以考虑不修改。)
+ - [1.2 General 页面 : Discoverable in standby mode 设置成disable。强制要求必须修改](#id-2.2.1设备端环境搭建-1.2General页面:Discoverableinstandbymode设置成disable。强制要求必须修改)
+ - [1.3 General 页面: 勾选 Non-discoverable when linkback 强制要求必须修改](#id-2.2.1设备端环境搭建-1.3General页面:勾选Non-discoverablewhenlinkback强制要求必须修改)
+ - [1.4 勾选Multi-link support, 并且不要勾选 Enter pairing state while only available device is connected 强制要求必须修改](#id-2.2.1设备端环境搭建-1.4勾选Multi-linksupport,并且不要勾选Enterpairingstatewhileonlyavailabledeviceisconnected强制要求必须修改)
+ - [1.5 Third Party页面配置GFPS参数](#id-2.2.1设备端环境搭建-1.5ThirdParty页面配置GFPS参数)
+ - [1.6 配置GFPS findme voice prompt tone](#id-2.2.1设备端环境搭建-1.6配置GFPSfindmevoiceprompttone)
+ - [1.7 保存新生成的 APP UI Parameter File 和 System Config File](#id-2.2.1设备端环境搭建-1.7保存新生成的APPUIParameterFile和SystemConfigFile)
+ - [1.8 Note](#id-2.2.1设备端环境搭建-1.8Note)
+ - [1.建议把BD Address和Device Name也改一下](#id-2.2.1设备端环境搭建-1.建议把BDAddress和DeviceName也改一下)
+ - [2.建议Export 生成rcfg之前先导入正确的flash_map.ini](#id-2.2.1设备端环境搭建-2.建议Export生成rcfg之前先导入正确的flash_map.ini)
+ - [3.因为设备不支援LEA， LEA相关的配置要务必关掉：](#id-2.2.1设备端环境搭建-3.因为设备不支援LEA，LEA相关的配置要务必关掉：)
+- [2 TWS 耳机 GFPS battery feature测试环境搭建(只有TWS耳机需要做GFPS battery测试，single mode 不需要测试)](#id-2.2.1设备端环境搭建-2TWS耳机GFPSbatteryfeature测试环境搭建(只有TWS耳机需要做GFPSbattery测试，singlemode不需要测试))
+ - [2.1.mcu config tool 配置：](#id-2.2.1设备端环境搭建-2.1.mcuconfigtool配置：)
+ - [2.1.1 HW Feature 模块](#id-2.2.1设备端环境搭建-2.1.1HWFeature模块)
+ - [2.1.2 charger 模块，勾选battery detection support](#id-2.2.1设备端环境搭建-2.1.2charger模块，勾选batterydetectionsupport)
+ - [2.1.3 general 模块](#id-2.2.1设备端环境搭建-2.1.3general模块)
+ - [2.2.充电盒配置：](#id-2.2.1设备端环境搭建-2.2.充电盒配置：)
+ - [2.2.1 接线设置](#id-2.2.1设备端环境搭建-2.2.1接线设置)
+ - [2.2.2 充电盒操作](#id-2.2.1设备端环境搭建-2.2.2充电盒操作)
+ - [2.3 Note](#id-2.2.1设备端环境搭建-2.3Note)
+ - [2.3.1 开关盒操作步骤](#id-2.2.1设备端环境搭建-2.3.1开关盒操作步骤)
+ - [2.3.2 HUN显示测试](#id-2.2.1设备端环境搭建-2.3.2HUN显示测试)
+ - [2.3.3 demo rcfg](#id-2.2.1设备端环境搭建-2.3.3demorcfg)
+- [3 Find Hub测试环境搭建：](#id-2.2.1设备端环境搭建-3FindHub测试环境搭建：)
+ - [3.1 每一轮测试开始之前耳机端需要做factory reset操作，测试中请不要做factory reset。原因如下：8 手机端清掉配对信息之后，耳机端也要做factory reset，不然finder功能用不起来](#id-2.2.1设备端环境搭建-3.1每一轮测试开始之前耳机端需要做factoryreset操作，测试中请不要做factoryreset。原因如下：)
+ - [3.2 finder 所有功能测试完成之后，测试手机归还QC之前，手机端一定要清掉配对信息，不然过段时间再测试的时候可能会有问题，手机log会提示设备已经有owner了，会比较麻烦，建议测试完成之后一定要先把手机端的配对信息全清掉 1 gfps/finder 如何清除配对信息](#id-2.2.1设备端环境搭建-3.2finder所有功能测试完成之后，测试手机归还QC之前，手机端一定要清掉配对信息，不然过段时间再测试的时候可能会有问题，手机log会提示设备已经有owner了，会比较麻烦，建议测试完成之后一定要先把手机端的配对信息全清掉)
+ - [3.3 MCU cfg tool中model id和key的信息要换成支持finder 的model id 和key的信息，测试账号必须只能使用某个固定的Google账号，暂时还不可以使用多个Google账号进行测试。](#id-2.2.1设备端环境搭建-3.3MCUcfgtool中modelid和key的信息要换成支持finder的modelid和key的信息，测试账号必须只能使用某个固定的Google账号，暂时还不可以使用多个Google账号进行测试。)
+ - [3.4 2024/5/11以后：更新至finder1.3后，需要填写注册model id的时候填写的 ”Company name”, ”Device name” 和 ”Device type”（当前已支持harman T520）](#id-2.2.1设备端环境搭建-3.42024/5/11以后：更新至finder1.3后，需要填写注册modelid的时候填写的”Companyname”,”Devicename”和”Devicetype”（当前已支持harmanT520）)
+ - [3.5 .MCU cfg tool 需要配置按键停止响铃功能](#id-2.2.1设备端环境搭建-3.5.MCUcfgtool需要配置按键停止响铃功能)
+ - [3.6 Finder adv 需要占用一条BLE link，GFPS adv要占用一条 BLE link, 所以这边LE link number 和 LE slave link number要在原有的基础上+2](#id-2.2.1设备端环境搭建-3.6Finderadv需要占用一条BLElink，GFPSadv要占用一条BLElink,所以这边LElinknumber和LEslavelinknumber要在原有的基础上+2)
+ - [3.7 要想让finder响铃，mcu cfg tool 需要配置对应的vp](#id-2.2.1设备端环境搭建-3.7要想让finder响铃，mcucfgtool需要配置对应的vp)
+ - [3.8 mcu cfg tool 需要enable finder 功能](#id-2.2.1设备端环境搭建-3.8mcucfgtool需要enablefinder功能)
+ - [3.9 2024/5/11： 更新至finder1.3后，KEY配置界面需要配置按键0xBB Dult enter id read state mode](#id-2.2.1设备端环境搭建-3.92024/5/11：更新至finder1.3后，KEY配置界面需要配置按键0xBBDultenteridreadstatemode)
+ - [3.10 2024/5/11： 更新至finder1.3后，Ringtone配置页面需要配置GFPS find dult（当前已支持harman T520，该案比较特殊，分为两个响铃：GFPS find dult tone和GFPS find dult vp）](#id-2.2.1设备端环境搭建-3.102024/5/11：更新至finder1.3后，Ringtone配置页面需要配置GFPSfinddult（当前已支持harmanT520，该案比较特殊，分为两个响铃：GFPSfinddulttone和GFPSfinddultvp）)
+ - [3.11 如果需要关机之后依然打finder广播需要配置以下信息：](#id-2.2.1设备端环境搭建-3.11如果需要关机之后依然打finder广播需要配置以下信息：)
+
+
+
+### 1 MCUConfigTool 配置
+
+#### 1.1 General 页面 : 不勾选 Enable auto power off, 不勾选 Enable pairing timeout 修改为了便于GFPS测试，GFPS 测试的时候或者是过认证的时候需要修改， **量产时可以考虑不修改。**
+
+
+
+#### 1.2 General 页面 : Discoverable in standby mode 设置成disable。**强制要求必须修改**
+
+**Note**:
+
+GFPS 耳机第一次和一只手机配对成功之后(initial pairing 成功)，就会进入 subsequent pairing mode。
+
+所以initial pairing 成功之后，不管耳机是进入idle mode 还是进入connectable mode(multilink 支持)，都不应该再设置成discoverable。
+
+
+
+#### 1.3 General 页面: 勾选 Non-discoverable when linkback **强制要求必须修改**
+
+linkback模式下DUT不应该discoverable，不然手机端会一直弹配对窗口。
+
+\
+
+
+
+#### 1.4 勾选Multi-link support, 并且不要勾选 Enter pairing state while only available device is connected **强制要求必须修改**
+
+下面红框里的**不可以勾选 **不然battery HUN测试可能测不过， ** BBPRO2BUG-21515 - Getting issue details... STATUS **
+
+
+
+#### 1.5 Third Party页面配置GFPS参数
+
+在Third Party页面配置GFPS参数，详细信息参考 mcu cfg tool中 GFPS 各配置项的含义 - BT_Market - WIKI
+
+
+
+下面是RTK已通过认证的Module ID
+
+[认证结果及认证通过的model_id 和key](/pages/viewpage.action?pageId=204620689)
+
+#### 1.6 配置GFPS findme voice prompt tone
+
+gfps_findme.wav
+
+自行选择wav文件作为findme vp tone，
+
+wav文件名称可以自行修改，放入MCU config tool vp目录，
+
+建议findme的wav文件可以播放久一些，这样才能达到提示的效果。
+
+如下图所示：
+
+
+
+打开MCU config tool开始配置findme tone，
+
+首先refresh一下，让tool能够识别新的wav文件，
+
+然后就可以选择vp tone了，
+
+如下图所示：
+
+
+
+
+
+#### 1.7 保存新生成的 APP UI Parameter File 和 System Config File
+
+#### **1.8 Note**
+
+##### 1.建议把BD Address和Device Name也改一下
+
+##### 2.建议Export 生成rcfg之前先导入正确的flash_map.ini
+
+
+
+##### 3.因为设备不支援LEA， LEA相关的配置要务必关掉：
+
+
+
+
+
+
+
+### 2 TWS 耳机 GFPS battery feature测试环境搭建(只有TWS耳机需要做GFPS battery测试，single mode 不需要测试)
+
+Note：
+
+测试battery的时候需要搭配充电盒
+
+#### 2.1.mcu config tool 配置：
+
+##### 2.1.1 HW Feature 模块
+
+ 勾选Charger功能：
+
+
+
+勾选支持充电盒功能，注意如果充电盒image烧录的是20ms,下面红色框中的40ms也要改成20ms,这个要和充电盒image匹配的。
+
+如果充电盒image 烧录的是40ms：
+
+
+
+如果充电盒image烧录的是20ms:\
+
+
+勾选power off immediately when chose case和do not auto power off when case not close
+
+
+
+##### 2.1.2 charger 模块，勾选battery detection support
+
+
+
+
+
+
+
+##### 2.1.3 general 模块
+
+
+
+2.1.4 third party 模块 enable battery 功能
+
+
+
+#### 2.2.充电盒配置：
+
+##### 2.2.1 接线设置
+
+
+
+##### 2.2.2 充电盒操作
+
+
+
+#### **2.3 Note**
+
+##### 2.3.1 开关盒操作步骤
+
+1.左右耳factory reset 之后，先按下出盒入盒按钮（确保两个按钮同时按下，代表左右耳机入盒），耳机入盒之后，再按下开盒关盒按钮(按键弹起是开盒)，耳机端可以听到power on的提示音，说明开盒成功。有时候开盒成功但是没有提示音，此时可以看一下log：
+
+app_adp_handle_msg +++++ AD2B_CMD_POWER_ON =3，如果有AD2B_CMD_POWER_ON的log说明开盒成功
+
+2.按下开盒关盒按钮，按键按下是关盒，耳机端可以听到power off的提示音，说明关盒成功。有时候关盒成功但是没有提示音，此时可以看一下log：
+
+app_adp_handle_msg +++++ AD2B_CMD_POWER_OFF =4，如果有AD2B_CMD_POWER_OFF的log说明关盒成功
+
+3.如果重新烧录app的bin. 烧录完成之后要先按一下reset按键，然后按开盒关盒按钮进行操作。
+
+**4.关盒之后，3s关机，关机之后 3s会 watch dog reset，故关盒之后建议等10s才可以再次开盒，否则开机流程可能会不正常：**
+
+相关代码修改(仅用于GFPS认证)：
+
+关盒之后3s关机：
+
+\#define ADP_CLOSE_CASE_TIMEOUT_MS 3000
+
+关机之后，打开power off的提示音(目前没有打开，可以不需要修改，使用默认配置就好)
+
+
+
+watch dog reset的时间改成6s,目前没有设置成6s,使用默认设置3s，目前测试看是ok的，所以这个也可以不用修改
+
+
+
+##### 2.3.2 HUN显示测试
+
+HUN(Heads up notification)显示图如下：
+
+
+
+一次HUN显示成功之后，需要先把上次的显示信息清掉,再执行下一次操作：
+
+
+
+\
+
+##### 2.3.3 demo rcfg
+
+GFPS_Left.rcfg
+
+GFPS_Right.rcfg
+
+### **3 Find Hub测试环境搭建：**
+
+#### 3.1 每一轮测试开始之前耳机端需要做factory reset操作，测试中请不要做factory reset。原因如下：[8 手机端清掉配对信息之后，耳机端也要做factory reset，不然finder功能用不起来](/pages/viewpage.action?pageId=350190807)
+
+#### 3.2 finder 所有功能测试完成之后，测试手机归还QC之前，手机端一定要清掉配对信息，不然过段时间再测试的时候可能会有问题，手机log会提示设备已经有owner了，会比较麻烦，建议测试完成之后一定要先把手机端的配对信息全清掉 [1 gfps/finder 如何清除配对信息](/pages/viewpage.action?pageId=401291585)
+
+#### 3.3 MCU cfg tool中model id和key的信息要换成支持finder 的model id 和key的信息，测试账号必须只能使用某个固定的Google账号，暂时还不可以使用多个Google账号进行测试。
+
+ 内部测试model id 和Company name, Device name 和 Device type 请参考 [7 TWS耳机-finder-内部测试model id](/pages/viewpage.action?pageId=350177663)：
+
+
+
+#### 3.4 2024/5/11以后：更新至finder1.3后，需要填写注册model id的时候填写的 ”Company name”, ”Device name” 和 ”Device type”（当前已支持harman T520）
+
+Device type双耳测试选Earphones，单耳测试选Headphones
+
+
+
+#### 3.5 .MCU cfg tool 需要配置按键停止响铃功能
+
+for example:
+
+配置key1接P3_1
+
+
+
+配置key1短按之后触发GFPS finder停止响铃
+
+
+
+开发板上 key1 接到M3_1
+
+
+
+#### 3.6 Finder adv 需要占用一条BLE link，GFPS adv要占用一条 BLE link, 所以这边LE link number 和 LE slave link number要在原有的基础上+2
+
+
+
+\
+
+#### 3.7 要想让finder响铃，mcu cfg tool 需要配置对应的vp
+
+
+
+\
+
+#### 3.8 mcu cfg tool 需要enable finder 功能
+
+
+
+\
+
+#### 3.9 2024/5/11： 更新至finder1.3后，KEY配置界面需要配置按键0xBB Dult enter id read state mode
+
+
+
+\
+
+#### 3.10 2024/5/11： 更新至finder1.3后，Ringtone配置页面需要配置GFPS find dult（当前已支持harman T520，该案比较特殊，分为两个响铃：GFPS find dult tone和GFPS find dult vp）
+
+
+
+
+
+\
+
+#### 3.11 如果需要关机之后依然打finder广播需要配置以下信息：
+
+详细信息可以参考mcu cfg tool中 GFPS 各配置项的含义 - BT_Market - WIKI 中的: ”9. GFPS Finder相关配置信息描述”
+
+
diff --git a/2.2.2+手机端环境搭建.md b/2.2.2+手机端环境搭建.md
new file mode 100644
index 0000000..5e00441
--- /dev/null
+++ b/2.2.2+手机端环境搭建.md
@@ -0,0 +1,248 @@
+# 2.2.2 手机端环境搭建
+
+
+
+
+
+- [GFPS 环境搭建](#id-2.2.2手机端环境搭建-GFPS环境搭建)
+ - [1.手机需要连接google网络](#id-2.2.2手机端环境搭建-1.手机需要连接google网络)
+ - [2.手机不可以打开勿扰模式，不然可能看不到弹窗](#id-2.2.2手机端环境搭建-2.手机不可以打开勿扰模式，不然可能看不到弹窗)
+ - [3.检查手机是否打开Google Play服务通知](#id-2.2.2手机端环境搭建-3.检查手机是否打开GooglePlay服务通知)
+ - [4.检查google play 服务是否更新到最新的版本](#id-2.2.2手机端环境搭建-4.检查googleplay服务是否更新到最新的版本)
+ - [5.登陆google账号](#id-2.2.2手机端环境搭建-5.登陆google账号)
+ - [6 打开自动同步数据功能](#id-2.2.2手机端环境搭建-6打开自动同步数据功能)
+ - [7.检查Show notification是否打开：](#id-2.2.2手机端环境搭建-7.检查Shownotification是否打开：)
+ - [8.Setting界面打开蓝牙，以及位置信息。](#id-2.2.2手机端环境搭建-8.Setting界面打开蓝牙，以及位置信息。)
+ - [9.Enable debug mode ID：](#id-2.2.2手机端环境搭建-9.EnabledebugmodeID：)
+ - [10.Check Google Play Service version](#id-2.2.2手机端环境搭建-10.CheckGooglePlayServiceversion)
+ - [11.注册成为google beta tester（内部测试账号已经注册过了，这一步不需要，如果是客户自己注册的Google账号，需要提醒客户check）](#id-2.2.2手机端环境搭建-11.注册成为googlebetatester（内部测试账号已经注册过了，这一步不需要，如果是客户自己注册的Google账号，需要提醒客户check）)
+- [Find hub 环境搭建](#id-2.2.2手机端环境搭建-Findhub环境搭建)
+ - [1. The Google Find Hub App must be installed and updated to the latest Beta version.](#id-2.2.2手机端环境搭建-1.TheGoogleFindHubAppmustbeinstalledandupdatedtothelatestBetaversion.)
+ - [1.1 如果没有安装：](#id-2.2.2手机端环境搭建-1.1如果没有安装：)
+ - [1.2 如果已经安装：](#id-2.2.2手机端环境搭建-1.2如果已经安装：)
+ - [1.2.1 长按 Find hub 图标，会看到App info](#id-2.2.2手机端环境搭建-1.2.1长按Findhub图标，会看到Appinfo)
+ - [1.2.2 点击App info,会看到 App details](#id-2.2.2手机端环境搭建-1.2.2点击Appinfo,会看到Appdetails)
+ - [1.2.3 点击App details,会看到以下页面，如果有新版本请手动更新到最新的版本。如果是beta版本则不需要更新，系统会自动帮忙更新。](#id-2.2.2手机端环境搭建-1.2.3点击Appdetails,会看到以下页面，如果有新版本请手动更新到最新的版本。如果是beta版本则不需要更新，系统会自动帮忙更新。)
+ - [2."Use Find Hub" must be enabled under "Settings \> Google \> Find Hub".](#id-2.2.2手机端环境搭建-2.%22UseFindHub%22mustbeenabledunder%22Settings%3EGoogle%3EFindHub%22.)
+ - [3 "Find your offline devices" must be set to "With network in all areas" under "Settings \> Google \> Find Hub".](#id-2.2.2手机端环境搭建-3%22Findyourofflinedevices%22mustbesetto%22Withnetworkinallareas%22under%22Settings%3EGoogle%3EFindHub%22.)
+ - [4.“Scan for nearby devices” and “Include debug results” must be enabled under “Settings\> Google \> Devices and sharing \> Devices”.](#id-2.2.2手机端环境搭建-4.“Scanfornearbydevices”and“Includedebugresults”mustbeenabledunder“Settings%3EGoogle%3EDevicesandsharing%3EDevices”.)
+ - [5.Should be connected to the google Internet and have Bluetooth and Location turned on in Settings.](#id-2.2.2手机端环境搭建-5.ShouldbeconnectedtothegoogleInternetandhaveBluetoothandLocationturnedoninSettings.)
+ - [6 测试账号需要加入(内部测试账号已加入，qc测试不需要关心，FAE需要提醒客户自查)](#id-2.2.2手机端环境搭建-6测试账号需要加入(内部测试账号已加入，qc测试不需要关心，FAE需要提醒客户自查))
+ - [7 如果测试手机支援LEA, 开发者选项中将 Bypass Bluetooth LE Audio 选项关掉，然后重启手机](#id-2.2.2手机端环境搭建-7如果测试手机支援LEA,开发者选项中将BypassBluetoothLEAudio选项关掉，然后重启手机)
+
+
+
+\
+
+该测试至少要准备两只手机。测试手机建议使用Google pixel手机，请**务必确保**手机端有打开开发者选项 https://developer.android.com/studio/debug/dev-options?hl=zh-cn
+
+### GFPS 环境搭建
+
+#### 1.手机需要连接google网络
+
+该网络必须可以登陆google的网站，在测试前请先测试一下是否可以登录google的网站(**建议试试能不能打开youtube之类的**）。
+
+#### 2.手机不可以打开勿扰模式，不然可能看不到弹窗
+
+
+
+#### 3.检查手机是否打开Google Play服务通知
+
+Setting-\>(Apps¬ification or Apps)应用和通知-\> See all apps -\>Google Play服务-\>通知-\>All Google Play services notifications, 开启(显示通知)
+
+
+
+\
+
+#### 4.检查google play 服务是否更新到最新的版本
+
+setting-\>(Apps¬ification or Apps)应用和通知-\>See all apps-\>Google Play 服务-\>高级-\>商店, 点击 App details or google play，界面会跳转到google play 商店，点击更新.
+
+如果已经成为 beta tester, google play service可能会自动更新到最新的。
+
+
+
+
+
+\
+
+#### 5.登陆google账号
+
+Settings\>Accounts or Seetings-\>Google(内部账号(不可给客户)：
+
+Fast Pair Validator 测试 请使用 realsilbt8888@gmail.com
+
+手动测试账号请参考 Google 账号 - BT_Market - WIKI (realtek.com)
+
+#### 6 打开自动同步数据功能
+
+由于GFPS的account key是存在google账号的云端的，所以必须要登陆google账号并且需要打开自动同步数据功能
+
+Settings\>Accounts ：
+
+
+
+or
+
+Seetings→Google:
+
+
+
+#### 7.检查Show notification是否打开：
+
+Settings\>Google\>(Devices & sharing)\>Devices(设置\>Google\>设备连接\>设备\>)
+
+pixel 2xl:
+
+
+
+pixel 7:
+
+
+
+\
+
+#### 8.Setting界面打开蓝牙，以及位置信息。
+
+\
+
+#### 9.Enable debug mode ID：
+
+The model ID provided to you is a debug mode ID. To enable it, go to Settings \> Google \> Devices & sharing \> Devices \> top right 3 dot menu to enable “Include debug results”.
+
+If the option “Include debug results” is missing in this page, please ensure Developer options in the phone is enabled.
+
+or go to Settings \> Google \> Devices & sharing \> Devices \>“Include debug results”
+
+Settings \> Google \> Devices & sharing \> Devices \> top right 3 dot menu to enable “Include debug results”
+
+
+
+or
+
+Settings \> Google \> Devices & sharing \> Devices \>“Include debug results”
+
+
+
+https://developer.android.com/studio/debug/dev-options?hl=zh-cn
+
+#### 10.Check Google Play Service version
+
+Purpose: To confirm we use right version of Fast Pair module for testing
+
+Go to Settings \> Apps¬ification or Apps\>google play services \> advanced, then check Google Play services version (It should be 20.XX.XX or higher).
+
+
+
+\
+
+\
+
+#### **11.注册成为google beta tester（内部测试账号已经注册过了，这一步不需要，如果是客户自己注册的Google账号，需要提醒客户check）**
+
+Sign up for the Google Play services beta program https://play.google.com/apps/testing/com.google.android.gms
+
+join the Android Beta group at https://www.google.com/android/beta to get latest update via OTA
+
+Finder/Find Hub testing program please Navigate to https://play.google.com/apps/testing/com.google.android.apps.adm
+
+\
+
+可以登陆Google账号之后在以下链接查看是否有添加成功：我的群组
+
+
+
+需要注意的是：
+
+
+
+如果没有权限添加，FAE需要联系YingTsung (YT) Lin， 请他发邮件给Google， 让Google把客户注册的Google账号添加到Google的Test group。
+
+\
+
+### Find hub 环境搭建
+
+#### 1. The Google Find Hub App must be installed and updated to the latest Beta version.
+
+确认手机是否安装 Find Hub, 图标如下图：
+
+ 
+
+##### 1.1 如果没有安装：
+
+去 Play Store/应用商店 下载Find Hub并且安装。
+
+##### 1.2 如果已经安装：
+
+确认安装的是否是最新版。不是最新版，请手动升级到最新版。确认步骤如下：
+
+###### 1.2.1 长按 Find hub 图标，会看到App info
+
+
+
+###### 1.2.2 点击App info,会看到 App details
+
+
+
+###### 1.2.3 点击App details,会看到以下页面，如果有新版本请手动更新到最新的版本。如果是beta版本则不需要更新，系统会自动帮忙更新。
+
+
+
+\
+
+#### 2.*"Use Find Hub"* must be enabled under *"Settings \> Google \> Find Hub"*.
+
+
+
+
+
+or
+
+手机端打开 finder功能.mp4
+
+\
+
+#### *3 "Find your offline devices"* must be set to *"With network in all areas"* under *"Settings \> Google \> Find Hub"*.
+
+
+
+
+
+\
+
+\
+
+#### 4.“Scan for nearby devices” and “Include debug results” must be enabled under “Settings\> Google \> Devices and sharing \> Devices”.
+
+
+
+\
+
+#### 5.Should be connected to the google Internet and have Bluetooth and Location turned on in Settings.
+
+
+
+\
+
+#### **6 测试账号需要加入(内部测试账号已加入，qc测试不需要关心，FAE需要提醒客户自查)**
+
+Google Play services testing program： Navigate to https://play.google.com/apps/testing/com.google.android.gms
+
+Find My Device testing program： Navigate to https://play.google.com/apps/testing/com.google.android.apps.adm.
+
+如果没有权限，需要联系Google帮忙添加账号权限。
+
+\
+
+#### **7 如果测试手机支援LEA, 开发者选项中将 Bypass Bluetooth LE Audio 选项关掉，然后重启手机**
+
+****
+
+\
+
+\
diff --git a/2.2.3+Fast+Pair+Validator+环境搭建.md b/2.2.3+Fast+Pair+Validator+环境搭建.md
new file mode 100644
index 0000000..5f7f077
--- /dev/null
+++ b/2.2.3+Fast+Pair+Validator+环境搭建.md
@@ -0,0 +1,326 @@
+# 2.2.3 Fast Pair Validator 环境搭建
+
+
+
+
+
+- [1 搭建手机端的测试环境](#id-2.2.3FastPairValidator环境搭建-1搭建手机端的测试环境)
+ - [1.1 手机需要连接google网络](#id-2.2.3FastPairValidator环境搭建-1.1手机需要连接google网络)
+ - [1.2 手机不可以打开勿扰模式，不然可能看不到弹窗](#id-2.2.3FastPairValidator环境搭建-1.2手机不可以打开勿扰模式，不然可能看不到弹窗)
+ - [1.3 检查手机是否打开Google Play服务通知](#id-2.2.3FastPairValidator环境搭建-1.3检查手机是否打开GooglePlay服务通知)
+ - [1.4 检查google play 服务是否更新到最新的版本](#id-2.2.3FastPairValidator环境搭建-1.4检查googleplay服务是否更新到最新的版本)
+ - [1.5 登陆google账号](#id-2.2.3FastPairValidator环境搭建-1.5登陆google账号)
+ - [1.6 打开自动同步数据功能](#id-2.2.3FastPairValidator环境搭建-1.6打开自动同步数据功能)
+ - [1.7 检查Show notification是否打开：](#id-2.2.3FastPairValidator环境搭建-1.7检查Shownotification是否打开：)
+ - [1.8 Setting界面打开蓝牙，以及位置信息。](#id-2.2.3FastPairValidator环境搭建-1.8Setting界面打开蓝牙，以及位置信息。)
+ - [1.9 Enable debug mode ID：](#id-2.2.3FastPairValidator环境搭建-1.9EnabledebugmodeID：)
+ - [1.10 Check Google Play Service version](#id-2.2.3FastPairValidator环境搭建-1.10CheckGooglePlayServiceversion)
+ - [1.11 注册成为google beta tester（内部测试账号已经注册过了，这一步不需要，如果是客户自己注册的Google账号，需要提醒客户check）](#id-2.2.3FastPairValidator环境搭建-1.11注册成为googlebetatester（内部测试账号已经注册过了，这一步不需要，如果是客户自己注册的Google账号，需要提醒客户check）)
+- [2 Fast Pair Validator APP安装](#id-2.2.3FastPairValidator环境搭建-2FastPairValidatorAPP安装)
+- [3 Enable fast pair validator app中的测项](#id-2.2.3FastPairValidator环境搭建-3Enablefastpairvalidatorapp中的测项)
+ - [3.1 安装adb:](#id-2.2.3FastPairValidator环境搭建-3.1安装adb:)
+ - [3.2 输入如下命令：](#id-2.2.3FastPairValidator环境搭建-3.2输入如下命令：)
+- [4 uninstall amazon 相关app](#id-2.2.3FastPairValidator环境搭建-4uninstallamazon相关app)
+- [5 测试账号和MODEL ID](#id-2.2.3FastPairValidator环境搭建-5测试账号和MODELID)
+- [6 测试准备](#id-2.2.3FastPairValidator环境搭建-6测试准备)
+- [7 Find hub 环境搭建:](#id-2.2.3FastPairValidator环境搭建-7Findhub环境搭建:)
+ - [1.认证实验室会重新跑 fast pair validator中finder相关的测项，所以送认证前最好提供各个测项的操作视频以及详细的操作步骤(如何开机，如何factory reset，如何进pairing mode..)](#id-2.2.3FastPairValidator环境搭建-1.认证实验室会重新跑fastpairvalidator中finder相关的测项，所以送认证前最好提供各个测项的操作视频以及详细的操作步骤(如何开机，如何factoryreset，如何进pairingmode..))
+ - [2.如果测试手机支援LEA, 开发者选项中将 Bypass Bluetooth LE Audio 选项关掉，然后重启手机](#id-2.2.3FastPairValidator环境搭建-2.如果测试手机支援LEA,开发者选项中将BypassBluetoothLEAudio选项关掉，然后重启手机)
+ - [3.一定要等所有的测项都测试PASS之后才可以提交测试结果](#id-2.2.3FastPairValidator环境搭建-3.一定要等所有的测项都测试PASS之后才可以提交测试结果)
+ - [4. Fast pair validator enable EDDYSTONE：](#id-2.2.3FastPairValidator环境搭建-4.FastpairvalidatorenableEDDYSTONE：)
+ - [1.打开fast pair validator, 登陆Google账号，找到和耳机对应的model id，点击model id之后会看到EDDYSTONE, 点击进行测试](#id-2.2.3FastPairValidator环境搭建-1.打开fastpairvalidator,登陆Google账号，找到和耳机对应的modelid，点击modelid之后会看到EDDYSTONE,点击进行测试)
+ - [2.如果看不到 EDDYSTONE， 需要 adb 执行以下两个commands:](#id-2.2.3FastPairValidator环境搭建-2.如果看不到EDDYSTONE，需要adb执行以下两个commands:)
+ - [3.然后选择EDDYSTONE 进行测试：](#id-2.2.3FastPairValidator环境搭建-3.然后选择EDDYSTONE进行测试：)
+ - [4.Finder Fast Pair Validator EDDYSTONE测试完成。测试结果提交：](#id-2.2.3FastPairValidator环境搭建-4.FinderFastPairValidatorEDDYSTONE测试完成。测试结果提交：)
+
+
+
+### 1 搭建手机端的测试环境
+
+测试手机建议使用Google pixel手机，请**务必确保**手机端有打开开发者选项 https://developer.android.com/studio/debug/dev-options?hl=zh-cn
+
+\
+
+#### 1.1 手机需要连接google网络
+
+该网络必须可以登陆google的网站，在测试前请先测试一下是否可以登录google的网站(**建议试试能不能打开youtube之类的**）。
+
+#### 1.2 手机不可以打开勿扰模式，不然可能看不到弹窗
+
+
+
+#### 1.3 检查手机是否打开Google Play服务通知
+
+Setting-\>(Apps¬ification or Apps)应用和通知-\> See all apps -\>Google Play服务-\>通知-\>All Google Play services notifications, 开启(显示通知)
+
+
+
+#### 1.4 检查google play 服务是否更新到最新的版本
+
+setting-\>(Apps¬ification or Apps)应用和通知-\>See all apps-\>Google Play 服务-\>高级-\>商店, 点击 App details or google play，界面会跳转到google play 商店，点击更新.
+
+如果已经成为 beta tester, google play service可能会自动更新到最新的。
+
+
+
+
+
+\
+
+#### 1.5 登陆google账号
+
+Settings\>Accounts or Seetings-\>Google(内部账号(不可给客户)：
+
+Fast Pair Validator 测试 请使用 realsilbt8888@gmail.com
+
+手动测试账号请参考 Google 账号 - BT_Market - WIKI (realtek.com)
+
+#### 1.6 打开自动同步数据功能
+
+由于GFPS的account key是存在google账号的云端的，所以必须要登陆google账号并且需要打开自动同步数据功能
+
+Settings\>Accounts ：
+
+
+
+or
+
+Seetings→Google:
+
+
+
+#### 1.7 检查Show notification是否打开：
+
+Settings\>Google\>(Devices & sharing)\>Devices(设置\>Google\>设备连接\>设备\>)
+
+pixel 2xl:
+
+
+
+pixel 7:
+
+
+
+\
+
+跑 Fast pair validator 测试之前关掉 Automatically save devices
+
+**Note: 只有realsilbt8888的账号需要关掉 Automatically save devices， 其他手动测试的账号Automatically save devices需要打开**
+
+
+
+\
+
+#### 1.8 Setting界面打开蓝牙，以及位置信息。
+
+\
+
+#### 1.9 Enable debug mode ID：
+
+The model ID provided to you is a debug mode ID. To enable it, go to Settings \> Google \> Devices & sharing \> Devices \> top right 3 dot menu to enable “Include debug results”.
+
+If the option “Include debug results” is missing in this page, please ensure Developer options in the phone is enabled.
+
+or go to Settings \> Google \> Devices & sharing \> Devices \>“Include debug results”
+
+Settings \> Google \> Devices & sharing \> Devices \> top right 3 dot menu to enable “Include debug results”
+
+
+
+or
+
+Settings \> Google \> Devices & sharing \> Devices \>“Include debug results”
+
+
+
+https://developer.android.com/studio/debug/dev-options?hl=zh-cn
+
+#### 1.10 Check Google Play Service version
+
+Purpose: To confirm we use right version of Fast Pair module for testing
+
+Go to Settings \> Apps¬ification or Apps\>google play services \> advanced, then check Google Play services version (It should be 20.XX.XX or higher).
+
+
+
+\
+
+\
+
+#### **1.11 注册成为google beta tester（内部测试账号已经注册过了，这一步不需要，如果是客户自己注册的Google账号，需要提醒客户check）**
+
+Sign up for the Google Play services beta program\
+https://play.google.com/apps/testing/com.google.android.gms
+
+join the Android Beta group at https://www.google.com/android/beta to get latest update via OTA
+
+Finder/Find Hub testing program please Navigate to https://play.google.com/apps/testing/com.google.android.apps.adm
+
+如果没有权限添加，FAE需要联系YingTsung (YT) Lin， 请他发邮件给Google， 让Google把客户注册的Google账号添加到Google的Test group。
+
+可以登陆Google账号之后在以下链接查看是否有添加成功：我的群组
+
+
+
+需要注意的是：
+
+
+
+### **2 Fast Pair Validator APP安装**
+
+确认手机是否安装 Fast Pair Validator APP
+
+Fast pair validator app 图标如下图：
+
+
+
+如果没有安装:
+
+去 Play Store/应用商店 下载 Fast Pair Validator APP并且安装。
+
+如果已经安装:
+
+确认安装的是否是最新版。不是最新版，请手动升级到最新版。确认步骤如下：
+
+长按 Fast Pair Validator 图标，会看到App info
+
+
+
+点击App info,会看到App details
+
+
+
+点击App details,会看到以下页面，如果有新版本请手动更新到最新的版本。如果是beta版本则不需要更新，系统会自动帮忙更新。
+
+
+
+### 3 Enable fast pair validator app中的测项
+
+#### 3.1 安装adb:
+
+adb安装及使用方法 该wiki上提供的adb版本太旧，会出现device offline的问题，下载最新的https://adbshell.com/downloads
+
+安装adb之后找到adb.exe所在的目录，在该目录下打开cmd命令行
+
+#### 3.2 输入如下命令：
+
+adb shell am broadcast -a com.google.location.nearby.apps.fastpair.validator.FLAG_OVERRIDE --es flag enable_features_for_v3 --es value true --es type boolean com.google.location.nearby.apps.fastpair.validator
+
+
+
+按enter执行命令。
+
+命令执行成功之后，
+
+打开fast pair validator 能看到新的feature
+
+\
+
+### 4 uninstall amazon 相关app
+
+Alexa (com.amazon.dee.app) 和com.amazon.wellness app， 会影响到Validator的测试，需要Uninstall。
+
+The Alexa (com.amazon.dee.app) took too much time on handling the ACL_CONNECTED intent, which impacts the Validator's flow.
+
+There is still another **app,com.amazon.wellness** app, who handled ACL_CONNECTED for 20+ seconds.Please uninstall it as well.
+
+现象： End-to-end integration测试，出现Pairing timeout
+
+操作方式：
+
+adb uninstall com.amazon.wellness
+
+adb uninstall com.amazon.dee.app
+
+\
+
+### 5 测试账号和MODEL ID
+
+使用Fast Pair Validator测试，需要先登陆Google账号，测试设备使用的Model ID,public key, private key 必须是该google账号注册的Device。
+
+场内测试账号：realsilbt8888@gmail.com
+
+**Note：**
+
+fast pair validator app使用的model id 要和DUT开发板配置的model id一致。
+
+
+
+### **6 测试准备**
+
+测试过程中需要注意
+
+手机端弹出配对提示框时不要手动点击，fast pair validator app会自己触发配对.
+
+开始测试前，需要确认是否已经和待测试耳机配对过，需要删除配对信息。 最后最好在开始测试前，开关一下飞行模式。
+
+点击GOT IT开始测试时，耳机端一定要处于Pairable mode，否则会scan不到设备, scan 到设备后，点击Test开始测试。
+
+
+
+\
+
+\
+
+### 7 Find hub 环境搭建:
+
+#### **1.认证实验室会重新跑 fast pair validator中finder相关的测项，所以送认证前最好提供各个测项的操作视频以及详细的操作步骤(如何开机，如何factory reset，如何进pairing mode..)**
+
+#### **2.如果测试手机支援LEA, 开发者选项中将 Bypass Bluetooth LE Audio 选项关掉，然后重启手机**
+
+****
+
+#### **3.一定要等所有的测项都测试PASS之后才可以提交测试结果**
+
+如果存在Fail的测项，不可以提交测试结果！！！
+
+如果存在Fail的测项，不可以提交测试结果！！！
+
+如果存在Fail的测项，不可以提交测试结果！！！
+
+#### 4. Fast pair validator enable EDDYSTONE：
+
+##### 1.打开fast pair validator, 登陆Google账号，找到和耳机对应的model id，点击model id之后会看到EDDYSTONE, 点击进行测试
+
+##### 2.如果看不到 EDDYSTONE， 需要 adb 执行以下两个commands:
+
+cmd1:
+
+adb shell am broadcast -a com.google.location.nearby.apps.fastpair.validator.FLAG_OVERRIDE --es flag enable_qa_input_for_fast_pair --es value true --es type boolean com.google.location.nearby.apps.fastpair.validator
+
+cmd2：
+
+adb shell am broadcast -a com.google.location.nearby.apps.fastpair.validator.FLAG_OVERRIDE --es flag enable_spot_tests --es value true --es type boolean com.google.location.nearby.apps.fastpair.validator
+
+log信息如下：
+
+
+
+\
+
+For locator tags that don't create a bond during pairing, also run the following command:
+
+cmd3：
+
+```
+adb shell am broadcast -a com.google.location.nearby.apps.fastpair.validator.FLAG_OVERRIDE --es flag skip_bonding_for_spot_locator_tags --es value true --es type boolean com.google.location.nearby.apps.fastpair.validator
+```
+
+##### 3.然后选择EDDYSTONE 进行测试：
+
+
+
+
+
+##### 4.Finder Fast Pair Validator EDDYSTONE测试完成。测试结果提交：\
+
\
+
+
+测试jira:
+
+ BTQCSZ-6106 - Getting issue details... STATUS
diff --git a/2.3+测试.md b/2.3+测试.md
new file mode 100644
index 0000000..c1228c6
--- /dev/null
+++ b/2.3+测试.md
@@ -0,0 +1,7 @@
+# 2.3 测试
+
+测试完成之后要填写测试报告, 测试报告 从以下位置获取：
+
+Test Case of the Third Party - BT Test - WIKI
+
+
diff --git a/2.3.1+Fast+Pair+Validator测试.md b/2.3.1+Fast+Pair+Validator测试.md
new file mode 100644
index 0000000..d5ba26e
--- /dev/null
+++ b/2.3.1+Fast+Pair+Validator测试.md
@@ -0,0 +1,17 @@
+# 2.3.1 Fast Pair Validator测试
+
+2.3.1.2 EDDYSTONE
+
+** 这个必须要保证可以PASS，因为认证实验室会使用Fast Pair Validator 测试Finder相关的测项**
+
+\
+
+2.3.1.1 FAST PAIR
+
+这个测项客户自测并且提交测试结果到Google云端，认证实验室暂时不会测试。
+
+目前来看只要有一次测试成功，并且有提交成功的测试结果到Google云端就可以，即使偶尔失败了，如果确定不是我们设备端的bug, 也没关系的
+
+https://partnerissuetracker.corp.google.com/u/0/issues/473688165
+
+
diff --git a/2.3.1.1+FAST+PAIR.md b/2.3.1.1+FAST+PAIR.md
new file mode 100644
index 0000000..b3866f6
--- /dev/null
+++ b/2.3.1.1+FAST+PAIR.md
@@ -0,0 +1,687 @@
+# 2.3.1.1 FAST PAIR
+
+
+
+
+
+- [Note](#id-2.3.1.1FASTPAIR-Note)
+ - [1 以下关于mcu cfg tool 的修改仅仅是为了通过fast pair validator测试，待测试通过之后，需要将相应的修改恢复默认值。否则GFPS功能没法正常使用。](#id-2.3.1.1FASTPAIR-1以下关于mcucfgtool的修改仅仅是为了通过fastpairvalidator测试，待测试通过之后，需要将相应的修改恢复默认值。否则GFPS功能没法正常使用。)
+ - [2 测试过程中GFPS 弹窗出来之后请不要点击弹窗！！！](#id-2.3.1.1FASTPAIR-2测试过程中GFPS弹窗出来之后请不要点击弹窗！！！)
+ - [3 GFPS Fast pair validator 测试走的Legacy flow, 通过gfps配对 legacy BREDR.](#id-2.3.1.1FASTPAIR-3GFPSFastpairvalidator测试走的Legacyflow,通过gfps配对legacyBREDR.)
+ - [4 mcu cfg tool 中 可以配置按键key1进入legacy Pairing mode(MMI 0x6C)，有些测试会需要短按key1进入Pairing mode](#id-2.3.1.1FASTPAIR-4mcucfgtool中可以配置按键key1进入legacyPairingmode(MMI0x6C)，有些测试会需要短按key1进入Pairingmode)
+ - [5 手机提示信息解读：](#id-2.3.1.1FASTPAIR-5手机提示信息解读：)
+ - [Upair the device：耳机做factory reset清掉配对信息](#id-2.3.1.1FASTPAIR-Upairthedevice：耳机做factoryreset清掉配对信息)
+ - [place the device back into pairing mode：耳机进入pairing mode](#id-2.3.1.1FASTPAIR-placethedevicebackintopairingmode：耳机进入pairingmode)
+ - [6 测试准备](#id-2.3.1.1FASTPAIR-6测试准备)
+ - [打开Fast Pair Validator app](#id-2.3.1.1FASTPAIR-打开FastPairValidatorapp)
+ - [通过model id找到待测试设备](#id-2.3.1.1FASTPAIR-通过modelid找到待测试设备)
+ - [选择FAST PAIR进行测试](#id-2.3.1.1FASTPAIR-选择FASTPAIR进行测试)
+ - [不要Enable LE spec test](#id-2.3.1.1FASTPAIR-不要EnableLEspectest)
+- [Calibration 测试](#id-2.3.1.1FASTPAIR-Calibration测试)
+- [End-to-end integration 测试](#id-2.3.1.1FASTPAIR-End-to-endintegration测试)
+- [Auto pairing 测试](#id-2.3.1.1FASTPAIR-Autopairing测试)
+- [Auto Subsequent Pairing 测试](#id-2.3.1.1FASTPAIR-AutoSubsequentPairing测试)
+- [Cross Seekers Auto Subsequent Pairing Test 测试](#id-2.3.1.1FASTPAIR-CrossSeekersAutoSubsequentPairingTest测试)
+- [Public Key Based Pairing Request in Non Discoverable Mode 测试](#id-2.3.1.1FASTPAIR-PublicKeyBasedPairingRequestinNonDiscoverableMode测试)
+- [Public Key Based Pairing Request After Retroactive Pair 测试](#id-2.3.1.1FASTPAIR-PublicKeyBasedPairingRequestAfterRetroactivePair测试)
+- [Account key Broadcasting & Rotation of RPA测试](#id-2.3.1.1FASTPAIR-AccountkeyBroadcasting&RotationofRPA测试)
+- [Key Based Request Flags Reserved Bit Verification 测试](#id-2.3.1.1FASTPAIR-KeyBasedRequestFlagsReservedBitVerification测试)
+- [Distance 0.3 Meter 测试](#id-2.3.1.1FASTPAIR-Distance0.3Meter测试)
+- [](#id-2.3.1.1FASTPAIR-)
+- [Distance 1.2 Meter 测试](#id-2.3.1.1FASTPAIR-Distance1.2Meter测试)
+- [Distance 2 Meter 测试](#id-2.3.1.1FASTPAIR-Distance2Meter测试)
+- [Battery Notification Verification 测试](#id-2.3.1.1FASTPAIR-BatteryNotificationVerification测试)
+- [Battery Suppress Notification Verification 测试](#id-2.3.1.1FASTPAIR-BatterySuppressNotificationVerification测试)
+- [Battery Level Update Verification 测试](#id-2.3.1.1FASTPAIR-BatteryLevelUpdateVerification测试)
+- [Personalized Name Update 测试](#id-2.3.1.1FASTPAIR-PersonalizedNameUpdate测试)
+- [Personalized Name with Provider First Time Pairing 测试](#id-2.3.1.1FASTPAIR-PersonalizedNamewithProviderFirstTimePairing测试)
+- [Ring a Device 测试](#id-2.3.1.1FASTPAIR-RingaDevice测试)
+- [Retroactive Pair 测试](#id-2.3.1.1FASTPAIR-RetroactivePair测试)
+- [Active Noise Control Verification 测试](#id-2.3.1.1FASTPAIR-ActiveNoiseControlVerification测试)
+- [Active Noise Control Disable 测试](#id-2.3.1.1FASTPAIR-ActiveNoiseControlDisable测试)
+- [Firmware Version 测试](#id-2.3.1.1FASTPAIR-FirmwareVersion测试)
+- [Dynamic Buffer Size测试](#id-2.3.1.1FASTPAIR-DynamicBufferSize测试)
+- [10.测试结果上报](#id-2.3.1.1FASTPAIR-10.测试结果上报)
+
+
+
+### **Note**
+
+#### 1 以下关于mcu cfg tool 的修改仅仅是为了通过fast pair validator测试，待测试通过之后，需要将相应的修改恢复默认值。否则GFPS功能没法正常使用。
+
+ 也就是说以下修改只能搭配fast pair validator app使用，请不要将对应的修改提交到正式release版本。
+
+#### 2 测试过程中GFPS 弹窗出来之后请不要点击弹窗！！！
+
+#### 3 GFPS Fast pair validator 测试走的Legacy flow, 通过gfps配对 legacy BREDR.
+
+#### 4 mcu cfg tool 中 可以配置按键key1进入legacy Pairing mode(MMI 0x6C)，有些测试会需要短按key1进入Pairing mode
+
+
+
+
+
+\
+
+#### 5 手机提示信息解读：
+
+##### Upair the device：耳机做factory reset清掉配对信息
+
+##### place the device back into pairing mode：耳机进入pairing mode
+
+#### 6 测试准备
+
+##### 打开Fast Pair Validator app
+
+
+
+##### 通过model id找到待测试设备
+
+
+
+##### 选择FAST PAIR进行测试
+
+
+
+##### 不要Enable LE spec test
+
+
+
+### Calibration 测试
+
+Note:
+
+calibration 测试， discoverable adv interval需要足够小，spec 规定 discoverable mode adv \<= 100ms，mcu cfg tool目前设为32(20 ms) 可以测试通过。
+
+开机legacy进pairing mode后，按键key1进入GFPS LEA 配对模式，按app提示将手机放置离耳机 1m、3m、0.3m米处，等待测试完成。
+
+Note:
+
+GFPS 弹窗出来之后请**不要**点击弹窗！！！
+
+如果1m测项测试失败，Fast pair validator可以协助我们手动调整tx power值:
+
+
+
+详细文档可以参考：tx power adjust user guide - BT_Market - WIKI
+
+### End-to-end integration 测试
+
+Note:
+
+spec 规定not discoverable mode adv interval \<= 250ms，该测项中有verify 500ms frequency检查，超过500 会fail，目前设置成62.5ms可以通过测试。
+
+\
+
+MCU cfg tool 配置：
+
+测试该测项的时候，手机清除配对信息(unpair device)，DUT断线需要进入non discoverable mode, 所以mcu config tool 中rws normal disconnect enter pairing mode需要设置成disable(不勾选)。
+
+
+
+如果找不到 rws normal disconnect enter pairing mode 这个配置项 ，原因是这个配置项挪位置了，请参考jira BTSOCTOOL-2822 - Getting issue details... STATUS 进行配置，RWS normal disconnect enter pairing mode 改成Normal disconnect enter pairing mode
+
+
+
+\
+
+（1）手机提示 Next steps时，控制耳机进入配对模式，点击next，等待手机 prescan-\> pair device -\> check account key != null -\> unpair device-\>verify account key –\> verify 500ms frequency -\> Check subsequent pairing tx power level -\> repair device -\> un-repair device.。
+
+（2）点击next。 注意一定要在“10.Un-Repair device”显示“Unpairing finished!”后才能点NEXT。
+
+如此反复5遍。
+
+
+
+
+
+测试视频：
+
+End To End test.mp4
+
+### Auto pairing 测试
+
+Mcu cfg tool配置：
+
+测试该测项的时候，手机清除配对信息(unpair device)，DUT断线需要进入discoverable mode, 所以mcu config tool 中 RWS页面下 rws normal disconnect enter pairing mode需要设置成enable(勾选)。\
+app_cfg_const.rws_disconnect_enter_pairing
+
+
+
+如果找不到 rws normal disconnect enter pairing mode 这个配置项 ，原因是这个配置项挪位置了，请参考jira BTSOCTOOL-2822 - Getting issue details... STATUS 进行配置，RWS normal disconnect enter pairing mode 改成Normal disconnect enter pairing mode
+
+
+
+\
+
+
+设置每一轮测试持续时间以及重复进行多少轮测试(推荐使用APP中提供的默认值进行测试（100次，一次120s)，然后点击test,
+
+测试时将手机setting-》显示-》屏幕超时设置成最大值。灭屏之后测试好像会stop，所以屏幕要保持常亮的状态。
+
+\
+
+**Note:**
+
+这个测试按照Google的测试spec是要求每轮测试之前都要强制进pairing mode的。
+
+正常每轮测试结束后手机会主动断线，为了方便测试我们soc端有设置只要soc收到手机主动断线的指令之后就会主动进入pairing mode,等待下一轮测试。
+
+因为是跑测试，我们soc端没办法预测所有的失败场景，所以针对异常的情况，soc端是没办法做到所有的失败场景下都能保证下一轮测试一定会正常进pairing mode， 因为手机端并不会告诉soc 什么时候测试开始。
+
+所以如果跑自动化测试遇到失败的情况，建议手动测试， 每一轮测试结束之后根据提示让设备主动进入pairing mode
+
+\
+
+
+
+\
+
+### Auto Subsequent Pairing 测试
+
+MCU cfg tool 配置：
+
+测试该测项的时候，手机清除配对信息(unpair device)，DUT断线需要进入non discoverable mode, 所以mcu config tool 中rws normal disconnect enter pairing mode需要设置成disable(不勾选)。
+
+
+
+如果找不到 rws normal disconnect enter pairing mode 这个配置项 ，原因是这个配置项挪位置了，请参考jira BTSOCTOOL-2822 - Getting issue details... STATUS 进行配置，RWS normal disconnect enter pairing mode 改成Normal disconnect enter pairing mode
+
+
+
+**Note:**
+
+这个测试按照Google的测试spec是要求每轮测试之前都要打nondiscoverable 广播的。
+
+正常每轮测试结束后手机会主动断线，为了方便测试我们soc端有设置只要soc收到手机主动断线的指令之后就会主动打nondiscoverable 广播,等待下一轮测试。
+
+因为是跑测试，
+
+我们soc端没办法预测所有的失败场景，
+
+所以针对异常的情况，
+
+soc端是没办法做到所有的失败场景下都能保证下一轮测试一定会主动打nondiscoverable 广播(不在pairing mode才会打nondiscoverable 广播)， 因为手机端并不会告诉soc 什么时候测试开始。
+
+所以如果跑自动化测试遇到失败的情况，建议手动测试：
+
+每一轮测试结束之后EVB按一下reset或者是关机再开机让设备端主动打nondiscoverable 广播(注意这个时候EVB一定不能做factory reset，也不能进pairing mode, 因为这个时候是期望打 nondiscoverable 广播)
+
+BLE advertisements don't contain fast pair account key while not in pairing mode 如果频繁遇到这个error， 可以尝试手动测试试试看
+
+\
+
+测试信息设置：
+
+
+
+手机端测试信息设置完成之后，
+
+耳机先做factory reset，之后耳机开机进pairing mode，
+
+之后手机端点击test 开始测试
+
+
+
+\
+
+### Cross Seekers Auto Subsequent Pairing Test 测试
+
+MCU cfg tool 配置：
+
+测试该测项的时候，手机清除配对信息(unpair device)，DUT断线需要进入non discoverable mode, 所以mcu config tool 中rws normal disconnect enter pairing mode需要设置成disable(不勾选)。
+
+
+
+如果找不到 rws normal disconnect enter pairing mode 这个配置项 ，原因是这个配置项挪位置了，请参考jira BTSOCTOOL-2822 - Getting issue details... STATUS 进行配置，RWS normal disconnect enter pairing mode 改成Normal disconnect enter pairing mode
+
+
+
+\
+
+\
+
+测试信息设置：
+
+
+
+\
+
+耳机先做factory reset，手机端清掉配对信息1 gfps/finder 如何清除配对信息 - BT_Market - WIKI， 之后耳机开机进pairing mode，之后手机端点击test 开始测试
+
+\
+
+测试视频：
+
+Cross Seekers Auto Subsequent Pairing Test.mp4
+
+测试log：
+
+COM12_2025-09-30_16-56-51.log
+
+COM12_btsnoop_2025-09-30_16-51-45.cfa
+
+COM12_2025-09-30_16-51-39.log
+
+COM12_2025-09-26_14-19-00.log
+
+
+
+
+
+\
+
+### Public Key Based Pairing Request in Non Discoverable Mode 测试
+
+MCU cfg tool 配置：
+
+测试该测项的时候，手机清除配对信息(unpair device)，DUT断线需要进入non discoverable mode, 所以mcu config tool 中rws normal disconnect enter pairing mode需要设置成disable(不勾选)。
+
+
+
+如果找不到 rws normal disconnect enter pairing mode 这个配置项 ，原因是这个配置项挪位置了，请参考jira BTSOCTOOL-2822 - Getting issue details... STATUS 进行配置，RWS normal disconnect enter pairing mode 改成Normal disconnect enter pairing mode
+
+
+
+\
+
+\
+
+测试信息设置：
+
+
+
+\
+
+耳机先做factory reset，手机端清掉配对信息1 gfps/finder 如何清除配对信息 - BT_Market - WIKI， 之后耳机开机进pairing mode，之后手机端点击test 开始测试
+
+\
+
+测试视频：
+
+public key based request in non discoverable mode-Non LEA.mp4
+
+测试log：
+
+COM12_2025-09-30_17-33-58.log
+
+COM12_btsnoop_2025-09-30_17-29-41.cfa
+
+COM12_2025-09-30_17-29-39.log
+
+
+
+\
+
+### Public Key Based Pairing Request After Retroactive Pair 测试
+
+MCU cfg tool 配置：
+
+测试该测项的时候，手机清除配对信息(unpair device)，DUT断线需要进入non discoverable mode, 所以mcu config tool 中rws normal disconnect enter pairing mode需要设置成disable(不勾选)。
+
+
+
+如果找不到 rws normal disconnect enter pairing mode 这个配置项 ，原因是这个配置项挪位置了，请参考jira BTSOCTOOL-2822 - Getting issue details... STATUS 进行配置，RWS normal disconnect enter pairing mode 改成Normal disconnect enter pairing mode
+
+
+
+\
+
+\
+
+测试信息设置：
+
+耳机先做factory reset，手机端清掉配对信息1 gfps/finder 如何清除配对信息 - BT_Market - WIKI， 之后耳机开机进pairing mode，之后手机端点击test 开始测试
+
+\
+
+测试视频：
+
+如果测试过程中遇到 Get account key fail, 参考以下视频：
+
+Public key based pairing request after retroactive pair-nonLEA-Get account key fail.mp4
+
+测试成功视频：
+
+Public key based pairing request after retroactive pair-nonLEA.mp4
+
+\
+
+测试log：
+
+Public Key Based Pairing Request After Retroactive Pair测试pass.7z
+
+\
+
+\
+
+### Account key Broadcasting & Rotation of RPA测试
+
+MCU cfg tool 配置：
+
+测试该测项的时候，手机清除配对信息(unpair device)，DUT断线需要进入non discoverable mode, 所以mcu config tool 中rws normal disconnect enter pairing mode需要设置成disable(不勾选)。
+
+
+
+如果找不到 rws normal disconnect enter pairing mode 这个配置项 ，原因是这个配置项挪位置了，请参考jira BTSOCTOOL-2822 - Getting issue details... STATUS 进行配置，RWS normal disconnect enter pairing mode 改成Normal disconnect enter pairing mode
+
+
+
+\
+
+板子做factory reset之后，开机进pairing mode，点击test开始测试, 测试时间大概30min左右
+
+
+
+### Key Based Request Flags Reserved Bit Verification 测试
+
+MCU cfg tool 配置：
+
+测试该测项的时候，手机清除配对信息(unpair device)，DUT断线需要进入non discoverable mode, 所以mcu config tool 中rws normal disconnect enter pairing mode需要设置成disable(不勾选)。
+
+
+
+如果找不到 rws normal disconnect enter pairing mode 这个配置项 ，原因是这个配置项挪位置了，请参考jira BTSOCTOOL-2822 - \[BBPro2\]\[BBlite D Cut\] RWS界面 rws normal disconnect enter pairing mode 的修改与移动 Resolved 进行配置，RWS normal disconnect enter pairing mode 改成Normal disconnect enter pairing mode
+
+
+
+\
+
+板子做factory reset之后，开机进pairing mode，点击test开始测试
+
+测试过程中看到"Please places the headset to pairing mode"的时候，短按key1进入pairing mode， 测试过程中不可以做factory reset
+
+测试视频：
+
+Key Based Request Flags Reserved Bit Verification.mp4
+
+\
+
+### Distance 0.3 Meter 测试
+
+耳机开机，按键key1进入GFPS LEA配对模式，然后开始测试，等待测试完成。
+
+Note:
+
+GFPS 弹窗出来之后不要点；
+
+如果该测项测不过，MCU cfg tool Thirdparty 页面需要适当减小tx power(比如从-10，减小到-12)；并重新跑 "**Calibration 测试"** 以及该测项
+
+\
+
+### 
+
+\
+
+### Distance 1.2 Meter 测试
+
+耳机开机，按键key1进入GFPS LEA配对模式，然后开始测试，等待测试完成。
+
+Note:
+
+GFPS 弹窗出来之后不要点；
+
+如果该测项测不过，MCU cfg tool Thirdparty 页面需要适当增大tx power(比如从-12增大到-10）；并重新跑 "**Calibration 测试"** 以及该测项
+
+\
+
+\
+
+### Distance 2 Meter 测试
+
+耳机开机，按键key1进入GFPS LEA配对模式，然后开始测试，等待测试完成。
+
+Note:
+
+GFPS 弹窗出来之后不要点；
+
+如果该测项测不过，MCU cfg tool Thirdparty 页面需要适当增大tx power(比如从-12增大到-10）；并重新跑 "**Calibration 测试"** 以及该测项
+
+
+
+### Battery Notification Verification 测试
+
+Note:
+
+该测项测试的时候需要接充电盒
+
+MCU cfg tool 配置：
+
+测试该测项的时候，手机清除配对信息(unpair device)，DUT断线需要进入non discoverable mode, 所以mcu config tool 中rws normal disconnect enter pairing mode需要设置成disable(不勾选)。
+
+
+
+如果找不到 rws normal disconnect enter pairing mode 这个配置项 ，原因是这个配置项挪位置了，请参考jira BTSOCTOOL-2822 - Getting issue details... STATUS 进行配置，RWS normal disconnect enter pairing mode 改成Normal disconnect enter pairing mode
+
+
+
+\
+
+测试前板子先做factory reset，之后再开机进pairing mode
+
+ 
+
+\
+
+### Battery Suppress Notification Verification 测试
+
+Note:
+
+该测项测试的时候需要接充电盒
+
+MCU cfg tool 配置：
+
+测试该测项的时候，手机清除配对信息(unpair device)，DUT断线需要进入non discoverable mode, 所以mcu config tool 中rws normal disconnect enter pairing mode需要设置成disable(不勾选)。
+
+
+
+如果找不到 rws normal disconnect enter pairing mode 这个配置项 ，原因是这个配置项挪位置了，请参考jira BTSOCTOOL-2822 - Getting issue details... STATUS 进行配置，RWS normal disconnect enter pairing mode 改成Normal disconnect enter pairing mode
+
+
+
+\
+
+测试前板子先做factory reset，之后再开机进pairing mode
+
+\
+
+### Battery Level Update Verification 测试
+
+Note:
+
+该测项测试的时候需要接充电盒
+
+MCU cfg tool 配置：
+
+测试该测项的时候，手机清除配对信息(unpair device)，DUT断线需要进入non discoverable mode, 所以mcu config tool 中rws normal disconnect enter pairing mode需要设置成disable(不勾选)。
+
+
+
+如果找不到 rws normal disconnect enter pairing mode 这个配置项 ，原因是这个配置项挪位置了，请参考jira BTSOCTOOL-2822 - Getting issue details... STATUS 进行配置，RWS normal disconnect enter pairing mode 改成Normal disconnect enter pairing mode
+
+
+
+\
+
+测试前板子先做factory reset，之后再开机进pairing mode
+
+\
+
+### Personalized Name Update 测试
+
+MCU cfg tool 配置：
+
+测试该测项的时候，手机清除配对信息(unpair device)，DUT断线需要进入non discoverable mode, 所以mcu config tool 中rws normal disconnect enter pairing mode需要设置成disable(不勾选)。
+
+
+
+如果找不到 rws normal disconnect enter pairing mode 这个配置项 ，原因是这个配置项挪位置了，请参考jira BTSOCTOOL-2822 - Getting issue details... STATUS 进行配置，RWS normal disconnect enter pairing mode 改成Normal disconnect enter pairing mode
+
+
+
+\
+
+\
+
+\
+
+测试注意事项：
+
+测试之前板子先做factory reset， 然后开机进pairing mode, 开始测试
+
+测试过程中看到"Please places the headset to pairing mode"的时候，短按key1进入pairing mode， 测试过程中不可以做factory reset
+
+
+
+\
+
+测试log:
+
+
+
+测试视频：
+
+Personalized name update.mp4
+
+### Personalized Name with Provider First Time Pairing 测试
+
+MCU cfg tool 配置：
+
+测试该测项的时候，手机清除配对信息(unpair device)，DUT断线需要进入non discoverable mode, 所以mcu config tool 中rws normal disconnect enter pairing mode需要设置成disable(不勾选)。
+
+
+
+如果找不到 rws normal disconnect enter pairing mode 这个配置项 ，原因是这个配置项挪位置了，请参考jira BTSOCTOOL-2822 - Getting issue details... STATUS 进行配置，RWS normal disconnect enter pairing mode 改成Normal disconnect enter pairing mode
+
+
+
+\
+
+\
+
+测试注意事项：
+
+测试之前板子做factory reset，然后再开机进pairing mode,然后开始测试
+
+看到"Please places the headset to pairing mode"的时候，短按key1让耳机进入 pairing mode
+
+测试log:
+
+
+
+测试视频：
+
+\
+
+### Ring a Device 测试
+
+MCU cfg tool 配置：
+
+测试该测项的时候，手机清除配对信息(unpair device)，DUT断线需要进入non discoverable mode, 所以mcu config tool 中rws normal disconnect enter pairing mode需要设置成disable(不勾选)。
+
+
+
+如果找不到 rws normal disconnect enter pairing mode 这个配置项 ，原因是这个配置项挪位置了，请参考jira BTSOCTOOL-2822 - Getting issue details... STATUS 进行配置，RWS normal disconnect enter pairing mode 改成Normal disconnect enter pairing mode
+
+
+
+\
+
+配置ring tone
+
+
+
+\
+
+测试注意事项：
+
+测试之前板子做factory reset，然后再开机进pairing mode, 然后开始测试
+
+看到"Please places the headset to pairing mode"的时候，短按key1让耳机进入 pairing mode
+
+测试log:
+
+
+
+
+
+
+
+\
+
+测试视频：
+
+Ring a Device.mp4
+
+### Retroactive Pair 测试
+
+MCU cfg tool 配置：
+
+测试该测项的时候，手机清除配对信息(unpair device)，DUT断线需要进入non discoverable mode, 所以mcu config tool 中rws normal disconnect enter pairing mode需要设置成disable(不勾选)。
+
+
+
+如果找不到 rws normal disconnect enter pairing mode 这个配置项 ，原因是这个配置项挪位置了，请参考jira BTSOCTOOL-2822 - Getting issue details... STATUS 进行配置，RWS normal disconnect enter pairing mode 改成Normal disconnect enter pairing mode
+
+
+
+\
+
+\
+
+在Available device点选要测试的设备：
+
+
+
+测试视频：
+
+retroactive pair test.mp4
+
+测试log：
+
+Retroactive Pair测试pass.7z
+
+### Active Noise Control Verification 测试
+
+目前还不清楚怎么测试，如果不支援可以不测
+
+### Active Noise Control Disable 测试
+
+目前还不清楚怎么测试，如果不支援可以不测
+
+### Firmware Version 测试
+
+MCU cfg tool 配置：
+
+测试该测项的时候，手机清除配对信息(unpair device)，DUT断线需要进入non discoverable mode, 所以mcu config tool 中rws normal disconnect enter pairing mode需要设置成disable(不勾选)。
+
+
+
+如果找不到 rws normal disconnect enter pairing mode 这个配置项 ，原因是这个配置项挪位置了，请参考jira BTSOCTOOL-2822 - Getting issue details... STATUS 进行配置，RWS normal disconnect enter pairing mode 改成Normal disconnect enter pairing mode
+
+
+
+\
+
+### Dynamic Buffer Size测试
+
+目前还不清楚怎么测试，如果不支援 可以不测
+
+\
+
+### 10.测试结果上报
+
+测试成功后，除了 目前还不清楚怎么测试 的测项之外的，其他所有的测试结果都为PASS，可以SUBMIT测试结果，否则请不要提交测试结果！！！
+
+\
+
+\
+
+\
+
+\
diff --git a/2.3.2+EDDYSTONE.md b/2.3.2+EDDYSTONE.md
new file mode 100644
index 0000000..fb0087c
--- /dev/null
+++ b/2.3.2+EDDYSTONE.md
@@ -0,0 +1,7 @@
+# 2.3.2 EDDYSTONE
+
+请参考以下Wiki中的测项进行测试 2 Fast Pair validator Finder 测试 - BT_Market - WIKI
+
+
+
+\
diff --git a/2.3.2+手动测试.md b/2.3.2+手动测试.md
new file mode 100644
index 0000000..d1b3487
--- /dev/null
+++ b/2.3.2+手动测试.md
@@ -0,0 +1 @@
+# 2.3.2 手动测试
diff --git a/2.3.2.1+Initial+pair+and+subsequent+pair.md b/2.3.2.1+Initial+pair+and+subsequent+pair.md
new file mode 100644
index 0000000..2c6f571
--- /dev/null
+++ b/2.3.2.1+Initial+pair+and+subsequent+pair.md
@@ -0,0 +1,13 @@
+# 2.3.2.1 Initial pair and subsequent pair
+
+google 官方测试文档：
+
+Fast Pair 3.2 & 3.3 Certification Guidelines | Google for Developers
+
+Realtek内部整理文档：
+
+1 Initial Pairing and Subsequent Pairing Test Guideline(中文文档) - BT_Market - WIKI
+
+测试视频：
+
+initial_pairing.mp4
diff --git a/2.3.2.2+extended+feature.md b/2.3.2.2+extended+feature.md
new file mode 100644
index 0000000..cf9df1b
--- /dev/null
+++ b/2.3.2.2+extended+feature.md
@@ -0,0 +1,13 @@
+# 2.3.2.2 extended feature
+
+Google 官方文档：
+
+https://developers.google.com/nearby/fast-pair/fast-pair-certification-guideline#4_feature_certification_criteria
+
+Realtek 内部整理文档：
+
+1 Extension Feature Test Guideline(中文文档) - BT_Market - WIKI
+
+\
+
+\
diff --git a/2.3.2.3+find+hub.md b/2.3.2.3+find+hub.md
new file mode 100644
index 0000000..3024f21
--- /dev/null
+++ b/2.3.2.3+find+hub.md
@@ -0,0 +1,11 @@
+# 2.3.2.3 find hub
+
+请参考以下Wiki 中的test case 进行测试 1 Finder-手机"Find My Device"APP测试-v1.3 - BT_Market - WIKI
+
+\
+
+
+
+\
+
+\
diff --git a/2.provider支援LE+audio,+必须打开_Enable+LE+Spec+Test__.md b/2.provider支援LE+audio,+必须打开_Enable+LE+Spec+Test__.md
new file mode 100644
index 0000000..773bfdf
--- /dev/null
+++ b/2.provider支援LE+audio,+必须打开_Enable+LE+Spec+Test__.md
@@ -0,0 +1,21 @@
+# 2.provider支援LE audio, 必须打开"Enable LE Spec Test"?
+
+答案：是的
+
+hi @Vito Kao If our product supports LE audio, does the Fast Pair validator only need to test scenarios where the 'Enable LE Spec Test" button is turned on?\
+\
+
+
+\
+When we turn off ''Enable LE Spec Test" button to test the GFPS legacy pair, it indicates a test failure. The reason is as follows:\
+\
+\
+we checking the logs on the earphone side, the BR pairing actually completes within 2 seconds. We are not sure why the tool shows a pairing timeout.\
+
+if headphones support LE audio, ''Enable LE Spec Test" button shall be turned on to test, does it right?
+
+\
+Vito Kao, \
+Hi @danni Realtek in general the headset support the LE audio, you would need to test the "Enable LE Spec Test"\
+you can refer to the LE audio Validator app user manual as well\
+https://developers.google.com/nearby/fast-pair/lea-validator-app-user-manual\
diff --git a/2.手机端点击Ring,耳机端没有响铃.md b/2.手机端点击Ring,耳机端没有响铃.md
new file mode 100644
index 0000000..9bd07e4
--- /dev/null
+++ b/2.手机端点击Ring,耳机端没有响铃.md
@@ -0,0 +1,11 @@
+# 2.手机端点击Ring,耳机端没有响铃
+
+ BB2BUG-18476 - \[BB2\]\[8773ESL\]\[v3.13.0.7\]\[GFPS\]\[LE Audio\]Find device响铃时，有时候停止响铃失败 In Progress ：
+
+看样子是手机先读了附耳的psm, 附耳有答复psm state 2(GFPS_PSM_STATE_NOT_AVAILABLE),告知手机附耳不支持创建PSM，但是手机没有尝试读主耳的PSM
+
+Line 32640: 0002246 07-28#10:07:44.162 035 0038072.274 \[APP\] gfps_read_cb: psm state 2, psm 0x80\
+Line 34922: 0004528 07-28#10:07:49.298 104 0043201.831 \[APP\] gfps_read_cb: psm state 2, psm 0x80\
+Line 41301: 0000706 07-28#10:07:54.464 033 0048358.109 \[APP\] gfps_read_cb: psm state 2, psm 0x80\
+Line 53504: 0002379 07-28#10:07:59.645 094 0053559.080 \[APP\] gfps_read_cb: psm state 2, psm 0x80\
+这个问题是google的已知问题，他们说后续会修正，暂时先作为已知问题处理
diff --git a/20+initial+pair成功之后维持BR+link,耳机再次进入Pairing+mode,GFPS弹窗出来点击弹窗显示连接成功，但是会再次马上跳出配对弹框.md b/20+initial+pair成功之后维持BR+link,耳机再次进入Pairing+mode,GFPS弹窗出来点击弹窗显示连接成功，但是会再次马上跳出配对弹框.md
new file mode 100644
index 0000000..47e99ab
--- /dev/null
+++ b/20+initial+pair成功之后维持BR+link,耳机再次进入Pairing+mode,GFPS弹窗出来点击弹窗显示连接成功，但是会再次马上跳出配对弹框.md
@@ -0,0 +1,50 @@
+# 20 initial pair成功之后维持BR link,耳机再次进入Pairing mode,GFPS弹窗出来点击弹窗显示连接成功，但是会再次马上跳出配对弹框
+
+[BB2BUG-50358] [BB2][RTL8763ESH/ROM][GMI][沃莱特][Harman][T530]759：After clicking the reappeared "fast pair" notification to connect, it prompts that the connection cannot be made（5/5） - Jira
+
+非LEA测试步骤：
+
+1、耳机开机，进配对，通过GFPS弹框与手机 Legacy连接，
+
+3、在【16:41:22】左右耳机按键进入配对，耳机与手机保持连接 ，手机跳出GFPS配对弹框
+
+4、在【16:41:24】左右点击弹框进行配对，**弹框显示连接成功，但是会再次马上跳出配对弹框**
+
+\
+
+
+
+
+ //手机和耳机 Legacy ACL link已经存在的情况下，16:41:22 耳机再次进入Pairing mode， gfps打discoverable adv
+Line 21506: 0001225 06-16#16:41:22.481 194 0027571.561 [APP] !**gfps_gen_adv_data: adv mode 0, tx_power -12, popup_show_ui 1, adv data 02 0A F4 06 16 2C FE C2 4E A0, len 10
+
+ //手机扫到GFPS discoverable adv之后会有GFPS弹窗出来， 点击弹窗，手机会建BLE 连线
+ Line 29448: 0008996 06-16#16:41:27.571 124 0032691.486 [APP] !**gfps_gen_aes_key:public key 76 92 80 49 D3 64 B1 A9 DA 7F 61 2B A4 E4 D5 49 37 05 C8 83 94 3B 43 1F CE 56 45 87 F9 B5 EF 49 F4 F9 F0 DE 5A 3B 1B 50 59 18 5D BC 6F 97 2E 09 C1 B9 8F 76 16 8D DA DA DE 02 85 49 0C F8 9A C3, private key FC 49 2E BD 02 04 F1 F1 C8 80 06 13 0D 30 04 67 29 61 3F 53 FF 45 77 CB F9 49 41 05 17 0E 0A DE, ECDH key 81 10 C2 99 9D 6C 2C FF 26 3B A6 EC 5A 88 27 A6 AC C1 35 9C 2A 87 80 7E AC D7 FD 93 6A B8 8E 01
+ Line 29449: 0008997 06-16#16:41:27.578 125 0032691.700 [APP] !**gfps_gen_aes_key:aes key FB 6D 55 C1 FE DC FD 4B 85 4A 3D 22 2F 0F 62 3D, SHA256 key FB 6D 55 C1 FE DC FD 4B 85 4A 3D 22 2F 0F 62 3D C9 A0 CB 4A 06 DB AF 54 0F 1B 7F 3E B2 0F 06 4F
+
+//手机发送kbp request
+Line 29451: 0008999 06-16#16:41:27.578 127 0032691.833 [APP] gfps_decrypt_kbp_request: encrypted request 81 A1 03 F2 5D 4C FA 35 98 A1 BE A4 58 60 07 A3, raw request 00 2C 55 22 44 44 22 55 5E F9 0B C2 52 2C 67 F7
+ Line 29452: 0009000 06-16#16:41:27.578 128 0032691.899 [APP] !**gfps_handle_kbp_request: seeker_ble_device_support 1, seeker_ble_audio_support 1, provider le_device_support 0
+ Line 29453: 0009001 06-16#16:41:27.578 129 0032692.007 [APP] !**app_gfps_link_add_link_into_priority_queue: conn_id 0
+ Line 29454: 0009002 06-16#16:41:27.578 130 0032692.169 [APP] !**app_gfps_print_link_priority: conn_id 0, priority 0
+ Line 29455: 0009003 06-16#16:41:27.578 131 0032692.275 [APP] !**app_gfps_cb_handle_kbp_write_req: provider bond 0, notify name 1, retroactively 0, pk exist 1, accountkey idx 0, provider addr 55::22::44::44::22::55, seek addr 00::00::00::00::00::00
+ Line 29459: 0009007 06-16#16:41:27.578 135 0032692.879 [APP] !**app_gfps_cb_handle_kbp_write_req: gap_set_pairable_mode, io_cap 1, authen_flag 0x40d
+//手机读存储的名字
+ Line 29460: 0009008 06-16#16:41:27.578 136 0032692.960 [APP] app_gfps_personalized_name_read: personalized_name in ftl BTQCTest2的JBL Tune 135BT, stored_personalized_name_len 26, is_valid 1
+ Line 29461: 0009009 06-16#16:41:27.578 137 0032693.138 [APP] !**gfps_ase_ctr_concat: input_data 42 54 51 43 54 65 73 74 32 E7 9A 84 4A 42 4C 20 54 75 6E 65 20 31 33 35 42 54
+ Line 29464: 0009012 06-16#16:41:27.611 140 0032693.308 [APP] !**gfps_ase_ctr_concat: output_data[26] 00 D1 6B D4 35 27 C1 62 A0 45 58 2B 88 94 A1 0D 90 5E 3F B9 90 2B 9E 16 7F 74
+ Line 29465: 0009013 06-16#16:41:27.611 141 0032694.063 [APP] !**gfps_hmac_sha256: E7 80 67 2E 6C C7 5A A6
+ Line 29474: 0009022 06-16#16:41:27.611 150 0032695.910 [APP] gfps_send_personalized_name: success name BTQCTest2的JBL Tune 135BT, input_nonce F8 DA 94 FB 86 99 FB 47, name_packet E7 80 67 2E 6C C7 5A A6 F8 DA 94 FB 86 99 FB 47 00 D1 6B D4 35 27 C1 62 A0 45 58 2B 88 94 A1 0D 90 5E 3F B9 90 2B 9E 16 7F 74
+ Line 29475: 0009023 06-16#16:41:27.611 151 0032695.949 [APP] !** app_gfps_personalized_name_send: is_send = 1
+ Line 29476: 0009024 06-16#16:41:27.611 152 0032696.050 [APP] !**app_gfps_cb_handle_kbp_write_req: ret 0, app_result 0
+ Line 29496: 0009044 06-16#16:41:27.611 172 0032715.202 [APP] !**gfps_send_kbp_response:raw response 01 55 22 44 44 22 55 C0 97 AE 5C 47 7C 2B BB 3D, encrypt response 4C 75 D1 15 A5 D5 99 E6 94 21 6E 99 A3 0D 2D 22
+
+
+//手机写accountkey
+ Line 29934: 0009470 06-16#16:41:27.838 045 0032947.192 [APP] !**gfps_handle_char_account_key: encrypted key 20 36 76 E9 07 5D F9 77 FA 23 13 AA EE 45 0F 4F, decrypted key 04 A4 46 1F 0A 32 07 4E 1E 17 B5 C5 19 A6 84 D4
+ Line 30008: 0009544 06-16#16:41:27.845 119 0032952.423 [APP] !**app_gfps_account_key_remote_add
+//因为legacy ACL link一直存在，所以手机不会再执行任何legacy相关的操作，这边 legacy 的radio mode 也会一直保持在discoverable and connectable, gfps就会一直打discoverable adv, 进而手机端GFPS 弹窗会一直出现
+ Line 30009: 0009545 06-16#16:41:27.845 120 0032952.521 [APP] !**app_gfps_device_check_state: radio_mode 3, bud_role 0, b2s link 1 |
+
+
+
diff --git a/21++android+13设备无GFPS弹窗.md b/21++android+13设备无GFPS弹窗.md
new file mode 100644
index 0000000..70547b5
--- /dev/null
+++ b/21++android+13设备无GFPS弹窗.md
@@ -0,0 +1,5 @@
+# 21 android 13设备无GFPS弹窗
+
+[BBPRO3BUG-27740] [BBPro3][RTL8773DFL+RTL8763EAU][GMI/WLT/JLAB_Daybreak][Gaming Stereo/Audio mixing]: android 13设备无GFPS弹窗 - Jira
+
+是因为Initial Pair有问题，Initial Pair失败之后弹窗的优先级会降低，就会不弹窗， 可以先解决配对问题之后再看弹窗的问题
diff --git a/22+Android+12+GFPS不弹窗.md b/22+Android+12+GFPS不弹窗.md
new file mode 100644
index 0000000..1ffe5fd
--- /dev/null
+++ b/22+Android+12+GFPS不弹窗.md
@@ -0,0 +1,7 @@
+# 22 Android 12 GFPS不弹窗
+
+如果设备端有打开legacy CTKD le ltk 功能， Android 12 通过GFPS弹窗配对会失败，配对失败之后弹窗的优先级就会降低
+
+这是Google已知问题
+
+4 pixel6(android 12) 不连A2DP - BT_Market - WIKI
diff --git a/23+很多客户要求不在Pairing+mode不允许配对新的设备，和GFPS+subsequent+Pair+有冲突，修改策略如下.md b/23+很多客户要求不在Pairing+mode不允许配对新的设备，和GFPS+subsequent+Pair+有冲突，修改策略如下.md
new file mode 100644
index 0000000..6830d9c
--- /dev/null
+++ b/23+很多客户要求不在Pairing+mode不允许配对新的设备，和GFPS+subsequent+Pair+有冲突，修改策略如下.md
@@ -0,0 +1,39 @@
+# 23 很多客户要求不在Pairing mode不允许配对新的设备，和GFPS subsequent Pair 有冲突，修改策略如下
+
+之前是在ACL 连线的时候卡的，现在把这边的code拿掉了，会在配对的时候需要回CFM的地方卡
+
+
+
+\
+
+\
+
+LE 处理的地方：
+
+如果是gfps配对：
+
+app_gfps_handle_le_numerical_comparison_bond_cfm会返回 true， GFPS 会根据自己的逻辑来决定 ACCEPT 还是REJECT
+
+\
+
+如果app_gfps_handle_le_numerical_comparison_bond_cfm返回false，说明不是GFPS 配对：
+
+由APP逻辑决定具体是GAP_CFM_CAUSE_ACCEPT 还是 GAP_CFM_CAUSE_REJECT
+
+
+
+\
+
+BR 处理的地方：
+
+如果是gfps配对：
+
+app_gfps_handle_bt_user_confirm会返回 true， GFPS 会根据自己的逻辑来决定 ACCEPT 还是REJECT
+
+\
+
+如果app_gfps_handle_bt_user_confirm返回false，说明不是GFPS 配对：
+
+由APP逻辑决定具体是GAP_CFM_CAUSE_ACCEPT 还是 GAP_CFM_CAUSE_REJECT
+
+
diff --git a/24+BLE+连上之后手机没有查服务，紧接着手机主动下了断线.md b/24+BLE+连上之后手机没有查服务，紧接着手机主动下了断线.md
new file mode 100644
index 0000000..b7a27d5
--- /dev/null
+++ b/24+BLE+连上之后手机没有查服务，紧接着手机主动下了断线.md
@@ -0,0 +1,55 @@
+# 24 BLE 连上之后手机没有查服务，紧接着手机主动下了断线
+
+问题1：
+
+https://partnerissuetracker.corp.google.com/u/0/issues/420766718
+
+
+
+
+// Validator calls BluetoothDevice.connectGatt()
+05-27 18:24:26.853 I GattClientImpl: BluetoothDevice.connectGatt() - 00:00:00:00:00:0D [CONTEXT service_id=284 ]
+
// This follows to BluetoothDevice.connectGatt() calls, apparently one made by another app at the same time.
+
05-27 18:24:26.853 D BluetoothGatt: connect() - device: XX:XX:XX:XX:00:0D, auto: false
+05-27 18:24:26.853 D BluetoothGatt: registerApp()
+05-27 18:24:26.854 D BluetoothGatt: registerApp() - UUID=8f31e253-d3a8-492f-9165-d806b6c95c32
+05-27 18:24:26.856 D BluetoothGatt: onClientRegistered() - status=0 clientIf=14
+
05-27 18:24:26.976 D BluetoothGatt: connect() - device: XX:XX:XX:XX:00:0D, auto: false
+05-27 18:24:26.976 D BluetoothGatt: registerApp()
+05-27 18:24:26.976 D BluetoothGatt: registerApp() - UUID=b48ee071-2016-4f0e-8e65-815a00cec43b
+05-27 18:24:26.988 D BluetoothGatt: onClientConnectionState() - status=0 clientIf=14 device=00:00:00:00:00:0D
+05-27 18:24:26.989 D BluetoothGatt: onClientRegistered() - status=0 clientIf=16
+
05-27 18:24:26.989 I GattClientImpl: Bluetooth connection state changed, status: GATT_SUCCESS, state: 2 - 00:00:00:00:00:0D [CONTEXT service_id=284 ]
+05-27 18:24:26.990 D BluetoothGatt: requestConnectionPriority() - params: 0
+
// BluetoothDevice.discoverServices() called. There's also a second call to this API. From HCI service discovery is not in fact performed.
+// onServicesDiscovered() is invoked right away
+05-27 18:24:26.991 I GattClientImpl: discoverServices() - 00:00:00:00:00:0D [CONTEXT service_id=284 ]
+05-27 18:24:26.992 D BluetoothGatt: discoverServices() - device: XX:XX:XX:XX:00:0D
+05-27 18:24:26.997 D BluetoothGatt: onClientConnectionState() - status=0 clientIf=16 device=00:00:00:00:00:0D
+05-27 18:24:26.998 D BluetoothGatt: discoverServices() - device: XX:XX:XX:XX:00:0D
+05-27 18:24:27.001 D BluetoothGatt: onSearchComplete() = Device=00:00:00:00:00:0D Status=0
+05-27 18:24:27.001 I GattClientImpl: onServicesDiscovered() - 00:00:00:00:00:0D [CONTEXT service_id=284 ]
+
// bluetoothGatt.writeDescriptor(Descriptor) returns false
+05-27 18:24:27.101 I ValidatorImpl: Asynchronously failing: Error performing GATT operation (fe2c1238-8366-4814-8eb0-01de32100bea SUBSCRIBE_TO_NOTIFICATIONS returned false)
|
+
+
+
+
+
+
+
+After BLE is connected, retroactive pairing failed due to no cache is found.
+05-27 18:24:21.381 I NearbyDiscovery: [trigger-id=Paed20819D34, feature-id=Repa] RetroactivePairManager: Skip, some info is null, mac=XX:XX:XX:XX:00:0D, remainingTime=0, ble-mac=XX:XX:XX:XX:1C:2D, model-id=99F751, bleCache=NONE [CONTEXT service_id=265 ]
+It may because the model-id 99f751 is filtered by spoofing detected.
+ModelIdScanTriggerStats ** last-seen-ms-ago= 95982, first-seen-ms-ago= 107254, count= 90, model-id=99f751, NotDownloadedYet, mac=XX:XX:XX:XX:1C:2D, min-distance= 0.07, max-distance= 1.00, result=SPOOFING_DETECTED
+Since the model-id 99f751 has still not approved in the device console yet,
+could you go to Settings > Google > All services > Devices and enable Include debug results (requires to enable developer mode first)
+
+Then, test again to see if the device can detect the advertisement correctly. Thanks!
|
+
+
+
+
+问题2:
+
+https://partnerissuetracker.corp.google.com/u/0/issues/502346693
diff --git a/3+GFPS+LEA+FAQ.md b/3+GFPS+LEA+FAQ.md
new file mode 100644
index 0000000..65b08a1
--- /dev/null
+++ b/3+GFPS+LEA+FAQ.md
@@ -0,0 +1 @@
+# 3 GFPS LEA FAQ
diff --git a/3+LEA+++GFPS.md b/3+LEA+++GFPS.md
new file mode 100644
index 0000000..23a5aaf
--- /dev/null
+++ b/3+LEA+++GFPS.md
@@ -0,0 +1,3 @@
+# 3 LEA + GFPS
+
+该功能是通过GFPS 快速配对 LE audio， 如果同时支援BREDR， 会通过LE 的 LTK CTKD 生成 BREDR 的 linkkey
diff --git a/3+UI+提示+Not+receive+KeyBasedPairingResponse.md b/3+UI+提示+Not+receive+KeyBasedPairingResponse.md
new file mode 100644
index 0000000..be9cc18
--- /dev/null
+++ b/3+UI+提示+Not+receive+KeyBasedPairingResponse.md
@@ -0,0 +1,9 @@
+# 3 UI 提示 Not receive KeyBasedPairingResponse
+
+
+
+\
+
+原因是手机端发了Kbp request 之后，会等我们耳机端答复KBP response， 但是手机端似乎没有收到kbp response ,导致timeout了
+
+查看耳机的firmware log 和 cfa log, 发现耳机端并未收到 手机端发送的KBP request， 需要同步抓取手机端的log和air log 来确认是手机端没发还是手机端发了但是我们lowerstack没有收到
diff --git a/3.+initial+pair+走的LE+配对，+subsequent+pair+走的legacy+配对.md b/3.+initial+pair+走的LE+配对，+subsequent+pair+走的legacy+配对.md
new file mode 100644
index 0000000..e8c7327
--- /dev/null
+++ b/3.+initial+pair+走的LE+配对，+subsequent+pair+走的legacy+配对.md
@@ -0,0 +1,15 @@
+# 3. initial pair 走的LE 配对， subsequent pair 走的legacy 配对
+
+查看 subsequent pair log，做subsequent pair的那只手机好像不支持le audio ,所以走了legacy 配对
+
+!\*\*gfps_handle_kbp_request: seeker_ble_device_support 1, seeker_ble_audio_support 0, provider le_device_support 1
+
+\
+
+请check 是不是setting界面LE audio 相关的配置信息不正确，正确的配置如下：
+
+
+
+COM8_btsnoop_2023-05-24_11-04-41.cfa
+
+COM8_2023-05-24_11-04-30.log
diff --git a/3.1+Project+工程enable对应功能.md b/3.1+Project+工程enable对应功能.md
new file mode 100644
index 0000000..b571afa
--- /dev/null
+++ b/3.1+Project+工程enable对应功能.md
@@ -0,0 +1,51 @@
+# 3.1 Project 工程enable对应功能
+
+app_flags.h 里面找到 CONFIG_REALTEK_GFPS_XXX 相关的宏并按照以下信息配置：
+
+\#define CONFIG_REALTEK_GFPS_FEATURE_SUPPORT 1\
+\#define CONFIG_REALTEK_GFPS_LE_DEVICE_SUPPORT (1 && CONFIG_REALTEK_GFPS_FEATURE_SUPPORT)\
+\#define CONFIG_REALTEK_GFPS_SASS_SUPPORT (0 && CONFIG_REALTEK_GFPS_FEATURE_SUPPORT)\
+\#define CONFIG_REALTEK_GFPS_FINDER_SUPPORT (0 && CONFIG_REALTEK_GFPS_FEATURE_SUPPORT)
+
+GFPS依赖的其他的模块：
+
+\#if CONFIG_REALTEK_GFPS_FEATURE_SUPPORT\
+\#undef F_APP_RWS_BLE_USE_RPA_SUPPORT\
+\#define F_APP_RWS_BLE_USE_RPA_SUPPORT 1
+
+\#undef F_APP_SC_KEY_DERIVE_SUPPORT\
+\#define F_APP_SC_KEY_DERIVE_SUPPORT 1
+
+\#if CONFIG_REALTEK_GFPS_LE_DEVICE_SUPPORT\
+\#undef F_APP_GATT_CACHING_SUPPORT\
+\#define F_APP_GATT_CACHING_SUPPORT 1\
+\#endif
+
+\#endif
+
+\
+
+Note:
+
+有的IC宏的名字是 GFPS_XXX, app_flags.h 里面找到 GFPS_XXX 相关的宏并按照以下信息配置：
+
+\#define GFPS_FEATURE_SUPPORT 1\
+\#define GFPS_LE_DEVICE_SUPPORT (1 && GFPS_FEATURE_SUPPORT)\
+\#define GFPS_SASS_SUPPORT (0 && GFPS_FEATURE_SUPPORT)\
+\#define GFPS_FINDER_SUPPORT (0 && GFPS_FEATURE_SUPPORT)
+
+GFPS依赖的其他的模块：
+
+\#if GFPS_FEATURE_SUPPORT\
+\#undef F_APP_RWS_BLE_USE_RPA_SUPPORT\
+\#define F_APP_RWS_BLE_USE_RPA_SUPPORT 1
+
+\#undef F_APP_SC_KEY_DERIVE_SUPPORT\
+\#define F_APP_SC_KEY_DERIVE_SUPPORT 1
+
+\#if GFPS_LE_DEVICE_SUPPORT\
+\#undef F_APP_GATT_CACHING_SUPPORT\
+\#define F_APP_GATT_CACHING_SUPPORT 1\
+\#endif
+
+\#endif
diff --git a/3.2+测试环境搭建.md b/3.2+测试环境搭建.md
new file mode 100644
index 0000000..93048ce
--- /dev/null
+++ b/3.2+测试环境搭建.md
@@ -0,0 +1 @@
+# 3.2 测试环境搭建
diff --git a/3.2.1+设备端环境搭建.md b/3.2.1+设备端环境搭建.md
new file mode 100644
index 0000000..7f01b38
--- /dev/null
+++ b/3.2.1+设备端环境搭建.md
@@ -0,0 +1,321 @@
+# 3.2.1 设备端环境搭建
+
+
+
+
+
+- [1 MCUConfigTool 配置](#id-3.2.1设备端环境搭建-1MCUConfigTool配置)
+ - [1.1 General 页面 : 不勾选 Enable auto power off, 不勾选 Enable pairing timeout](#id-3.2.1设备端环境搭建-1.1General页面:不勾选Enableautopoweroff,不勾选Enablepairingtimeout)
+ - [1.2 General 页面 : Discoverable in standby mode 设置成disable。强制要求必须修改](#id-3.2.1设备端环境搭建-1.2General页面:Discoverableinstandbymode设置成disable。强制要求必须修改)
+ - [1.3 General 页面: 勾选 Non-discoverable when linkback 强制要求必须修改](#id-3.2.1设备端环境搭建-1.3General页面:勾选Non-discoverablewhenlinkback强制要求必须修改)
+ - [1.4 勾选Multi-link support, 并且不要勾选 Enter pairing state while only available device is connected 强制要求必须修改](#id-3.2.1设备端环境搭建-1.4勾选Multi-linksupport,并且不要勾选Enterpairingstatewhileonlyavailabledeviceisconnected强制要求必须修改)
+ - [1.5 Third Party页面配置GFPS参数](#id-3.2.1设备端环境搭建-1.5ThirdParty页面配置GFPS参数)
+ - [1.6 配置GFPS findme voice prompt tone](#id-3.2.1设备端环境搭建-1.6配置GFPSfindmevoiceprompttone)
+ - [1.7 保存新生成的 APP UI Parameter File 和 System Config File](#id-3.2.1设备端环境搭建-1.7保存新生成的APPUIParameterFile和SystemConfigFile)
+ - [1.8 Note](#id-3.2.1设备端环境搭建-1.8Note)
+- [2 TWS 耳机 GFPS battery feature测试环境搭建(只有TWS耳机需要做GFPS battery测试，single mode 不需要测试)](#id-3.2.1设备端环境搭建-2TWS耳机GFPSbatteryfeature测试环境搭建(只有TWS耳机需要做GFPSbattery测试，singlemode不需要测试))
+ - [2.1.mcu config tool 配置：](#id-3.2.1设备端环境搭建-2.1.mcuconfigtool配置：)
+ - [2.1.1 HW Feature 模块](#id-3.2.1设备端环境搭建-2.1.1HWFeature模块)
+ - [2.1.2 charger 模块，勾选battery detection support](#id-3.2.1设备端环境搭建-2.1.2charger模块，勾选batterydetectionsupport)
+ - [2.1.3 general 模块](#id-3.2.1设备端环境搭建-2.1.3general模块)
+ - [2.2.充电盒配置：](#id-3.2.1设备端环境搭建-2.2.充电盒配置：)
+ - [2.2.1 接线设置](#id-3.2.1设备端环境搭建-2.2.1接线设置)
+ - [2.2.2 充电盒操作](#id-3.2.1设备端环境搭建-2.2.2充电盒操作)
+ - [2.3 Note](#id-3.2.1设备端环境搭建-2.3Note)
+ - [2.3.1 开关盒操作步骤](#id-3.2.1设备端环境搭建-2.3.1开关盒操作步骤)
+ - [2.3.2 HUN显示测试](#id-3.2.1设备端环境搭建-2.3.2HUN显示测试)
+ - [2.3.3 demo rcfg](#id-3.2.1设备端环境搭建-2.3.3demorcfg)
+- [3 GFPS LEA 环境搭建](#id-3.2.1设备端环境搭建-3GFPSLEA环境搭建)
+ - [1. enbale lea 以及disconnect enter lea pairing mode](#id-3.2.1设备端环境搭建-1.enbalelea以及disconnectenterleapairingmode)
+ - [2.配置stack相关参数](#id-3.2.1设备端环境搭建-2.配置stack相关参数)
+ - [EATT 暂时设置成 Disable](#id-3.2.1设备端环境搭建-EATT暂时设置成Disable)
+ - [Enable GATT Caching](#id-3.2.1设备端环境搭建-EnableGATTCaching)
+ - [3.配置GFPS参数](#id-3.2.1设备端环境搭建-3.配置GFPS参数)
+ - [4.配置ringtone](#id-3.2.1设备端环境搭建-4.配置ringtone)
+ - [5. 配置按键进入pairing mode](#id-3.2.1设备端环境搭建-5.配置按键进入pairingmode)
+ - [6 配置按键退出pairing mode](#id-3.2.1设备端环境搭建-6配置按键退出pairingmode)
+ - [7 配置GFPS LEA pairing mode 提示音](#id-3.2.1设备端环境搭建-7配置GFPSLEApairingmode提示音)
+
+
+
+### 1 MCUConfigTool 配置
+
+#### 1.1 General 页面 : 不勾选 Enable auto power off, 不勾选 Enable pairing timeout
+
+**Note**:
+
+修改为了便于GFPS测试，GFPS 测试的时候或者是过认证的时候需要修改， **量产时可以考虑不修改。**
+
+
+
+#### 1.2 General 页面 : Discoverable in standby mode 设置成disable。**强制要求必须修改**
+
+**Note**:
+
+GFPS 耳机第一次和一只手机配对成功之后(initial pairing 成功)，就会进入 subsequent pairing mode。
+
+所以initial pairing 成功之后，不管耳机是进入idle mode 还是进入connectable mode(multilink 支持)，都不应该再设置成discoverable。
+
+
+
+#### 1.3 General 页面: 勾选 Non-discoverable when linkback **强制要求必须修改**
+
+linkback模式下DUT不应该discoverable，不然手机端会一直弹配对窗口。
+
+\
+
+
+
+#### 1.4 勾选Multi-link support, 并且不要勾选 Enter pairing state while only available device is connected **强制要求必须修改**
+
+下面红框里的**不可以勾选 **不然battery HUN测试可能测不过， ** BBPRO2BUG-21515 - Getting issue details... STATUS **
+
+
+
+#### 1.5 Third Party页面配置GFPS参数
+
+在Third Party页面配置GFPS参数，详细信息参考 mcu cfg tool中 GFPS 各配置项的含义 - BT_Market - WIKI
+
+
+
+下面是RTK已通过认证的Module ID
+
+[认证结果及认证通过的model_id 和key](/pages/viewpage.action?pageId=204620689)
+
+#### 1.6 配置GFPS findme voice prompt tone
+
+gfps_findme.wav
+
+自行选择wav文件作为findme vp tone，
+
+wav文件名称可以自行修改，放入MCU config tool vp目录，
+
+建议findme的wav文件可以播放久一些，这样才能达到提示的效果。
+
+如下图所示：
+
+
+
+打开MCU config tool开始配置findme tone，
+
+首先refresh一下，让tool能够识别新的wav文件，
+
+然后就可以选择vp tone了，
+
+如下图所示：
+
+
+
+
+
+#### 1.7 保存新生成的 APP UI Parameter File 和 System Config File
+
+#### **1.8 Note**
+
+1.建议把BD Address和Device Name也改一下
+
+2.建议Export 生成rcfg之前先导入正确的flash_map.ini
+
+
+
+\
+
+### 2 TWS 耳机 GFPS battery feature测试环境搭建(只有TWS耳机需要做GFPS battery测试，single mode 不需要测试)
+
+Note：
+
+测试battery的时候需要搭配充电盒
+
+#### 2.1.mcu config tool 配置：
+
+##### 2.1.1 HW Feature 模块
+
+ 勾选Charger功能：
+
+
+
+勾选支持充电盒功能，注意如果充电盒image烧录的是20ms,下面红色框中的40ms也要改成20ms,这个要和充电盒image匹配的。
+
+如果充电盒image 烧录的是40ms：
+
+
+
+如果充电盒image烧录的是20ms:\
+
+
+勾选power off immediately when chose case和do not auto power off when case not close
+
+
+
+##### 2.1.2 charger 模块，勾选battery detection support
+
+
+
+
+
+
+
+##### 2.1.3 general 模块
+
+
+
+2.1.4 third party 模块 enable battery 功能
+
+
+
+#### 2.2.充电盒配置：
+
+##### 2.2.1 接线设置
+
+
+
+##### 2.2.2 充电盒操作
+
+
+
+#### **2.3 Note**
+
+##### 2.3.1 开关盒操作步骤
+
+1.左右耳factory reset 之后，先按下出盒入盒按钮（确保两个按钮同时按下，代表左右耳机入盒），耳机入盒之后，再按下开盒关盒按钮(按键弹起是开盒)，耳机端可以听到power on的提示音，说明开盒成功。有时候开盒成功但是没有提示音，此时可以看一下log：
+
+app_adp_handle_msg +++++ AD2B_CMD_POWER_ON =3，如果有AD2B_CMD_POWER_ON的log说明开盒成功
+
+2.按下开盒关盒按钮，按键按下是关盒，耳机端可以听到power off的提示音，说明关盒成功。有时候关盒成功但是没有提示音，此时可以看一下log：
+
+app_adp_handle_msg +++++ AD2B_CMD_POWER_OFF =4，如果有AD2B_CMD_POWER_OFF的log说明关盒成功
+
+3.如果重新烧录app的bin. 烧录完成之后要先按一下reset按键，然后按开盒关盒按钮进行操作。
+
+**4.关盒之后，3s关机，关机之后 3s会 watch dog reset，故关盒之后建议等10s才可以再次开盒，否则开机流程可能会不正常：**
+
+相关代码修改(仅用于GFPS认证)：
+
+关盒之后3s关机：
+
+\#define ADP_CLOSE_CASE_TIMEOUT_MS 3000
+
+关机之后，打开power off的提示音(目前没有打开，可以不需要修改，使用默认配置就好)
+
+
+
+watch dog reset的时间改成6s,目前没有设置成6s,使用默认设置3s，目前测试看是ok的，所以这个也可以不用修改
+
+
+
+##### 2.3.2 HUN显示测试
+
+HUN(Heads up notification)显示图如下：
+
+
+
+一次HUN显示成功之后，需要先把上次的显示信息清掉,再执行下一次操作：
+
+
+
+\
+
+##### 2.3.3 demo rcfg
+
+GFPS_Left.rcfg
+
+GFPS_Right.rcfg
+
+\
+
+### 3 GFPS LEA 环境搭建
+
+#### 1. enbale lea 以及disconnect enter lea pairing mode
+
+
+
+
+
+#### 2.配置stack相关参数
+
+##### EATT 暂时设置成 Disable
+
+LE link 设置：
+
+
+
+
+
+##### Enable GATT Caching
+
+
+
+\
+
+#### 3.配置GFPS参数
+
+
+
+\
+
+GFPS device mode 设置成 Dual mode device with CSIP (**这边取名字为CSIP取的有点问题，实际是想声明是否支援LE audio, 后面会请tool 帮忙把CSIP 改成LE audio**)，
+
+**如果找不到 Dual mode device with CSIP 应该是 新的 mcu cfg tool 有改名字将 CSIP 统一改成 LE audio了， tool上可以设置成 Dual mode device with LE audio**
+
+[BTSOCTOOL-5234] GFPS页面CSIP改成LE audio - Jira
+
+
+
+\
+
+#### 4.配置ringtone
+
+
+
+
+
+\
+
+
+
+\
+
+#### 5. 配置按键进入pairing mode
+
+将key1设置成 GFPS LEA enter pair mode(0xB9), 作为GFPS le audio 按键强制进入pairing mode 的MMI，
+
+有的客户不想多配置一个按键，想要复用 legacy 进Pairing mode的mmi, 那么key1也可以配置成 MMI(0x6C)
+
+\
+
+
+
+或者是
+
+
+
+单击key1 GFPS LE audio 会强制进入pairing mode
+
+手机弹窗出来之后， 配对 GFPS LE audio,
+
+正常配对成功之后会直接退出pairing mode，
+
+如果按键进入pairing mode 之后，手机端一直没有配对耳机，那耳机会一直处于pairing mode，需要配置按键退出pairing mode。
+
+例如：
+
+#### 6 配置按键退出pairing mode
+
+
+
+或者是
+
+
+
+\
+
+#### 7 配置GFPS LEA pairing mode 提示音
+
+
+
+\
diff --git a/3.2.2+手机端环境搭建.md b/3.2.2+手机端环境搭建.md
new file mode 100644
index 0000000..5016007
--- /dev/null
+++ b/3.2.2+手机端环境搭建.md
@@ -0,0 +1,181 @@
+# 3.2.2 手机端环境搭建
+
+
+
+
+
+- [GFPS 环境搭建](#id-3.2.2手机端环境搭建-GFPS环境搭建)
+ - [1.手机需要连接google网络](#id-3.2.2手机端环境搭建-1.手机需要连接google网络)
+ - [2.手机不可以打开勿扰模式，不然可能看不到弹窗](#id-3.2.2手机端环境搭建-2.手机不可以打开勿扰模式，不然可能看不到弹窗)
+ - [3.检查手机是否打开Google Play服务通知](#id-3.2.2手机端环境搭建-3.检查手机是否打开GooglePlay服务通知)
+ - [4.检查google play 服务是否更新到最新的版本](#id-3.2.2手机端环境搭建-4.检查googleplay服务是否更新到最新的版本)
+ - [5.登陆google账号](#id-3.2.2手机端环境搭建-5.登陆google账号)
+ - [6 打开自动同步数据功能](#id-3.2.2手机端环境搭建-6打开自动同步数据功能)
+ - [7.检查Show notification是否打开：](#id-3.2.2手机端环境搭建-7.检查Shownotification是否打开：)
+ - [8.Setting界面打开蓝牙，以及位置信息。](#id-3.2.2手机端环境搭建-8.Setting界面打开蓝牙，以及位置信息。)
+ - [9.Enable debug mode ID：](#id-3.2.2手机端环境搭建-9.EnabledebugmodeID：)
+ - [10.Check Google Play Service version](#id-3.2.2手机端环境搭建-10.CheckGooglePlayServiceversion)
+ - [11.注册成为google beta tester（内部测试账号已经注册过了，这一步不需要，如果是客户自己注册的Google账号，需要提醒客户check）](#id-3.2.2手机端环境搭建-11.注册成为googlebetatester（内部测试账号已经注册过了，这一步不需要，如果是客户自己注册的Google账号，需要提醒客户check）)
+- [GFPS LEA 环境搭建](#id-3.2.2手机端环境搭建-GFPSLEA环境搭建)
+ - [1 https://www.google.com/android/beta your google account will need to join the Android Beta group to get the T-QPR2 release.( pixel7、pixel7 Pro 在realsilbt8888@gmail.com 上已经注册，场内QC测试可以不用关心这一步， FAE需要提醒客户自查)](#id-3.2.2手机端环境搭建-1https://www.google.com/android/betayourgoogleaccountwillneedtojointheAndroidBetagrouptogettheT-QPR2release.(pixel7、pixel7Pro在realsilbt8888@gmail.com上已经注册，场内QC测试可以不用关心这一步，FAE需要提醒客户自查))
+ - [2 setting 界面 enable LE audio功能](#id-3.2.2手机端环境搭建-2setting界面enableLEaudio功能)
+
+
+
+\
+
+该测试至少要准备两只手机。测试手机建议使用Google pixel手机， Pixel 5+ is recommended. 请**务必确保**手机端有打开开发者选项 https://developer.android.com/studio/debug/dev-options?hl=zh-cn
+
+\
+
+### GFPS 环境搭建
+
+#### 1.手机需要连接google网络
+
+该网络必须可以登陆google的网站，在测试前请先测试一下是否可以登录google的网站(**建议试试能不能打开youtube之类的**）。
+
+#### 2.手机不可以打开勿扰模式，不然可能看不到弹窗
+
+
+
+#### 3.检查手机是否打开Google Play服务通知
+
+Setting-\>(Apps¬ification or Apps)应用和通知-\> See all apps -\>Google Play服务-\>通知-\>All Google Play services notifications, 开启(显示通知)
+
+
+
+\
+
+#### 4.检查google play 服务是否更新到最新的版本
+
+setting-\>(Apps¬ification or Apps)应用和通知-\>See all apps-\>Google Play 服务-\>高级-\>商店, 点击 App details or google play，界面会跳转到google play 商店，点击更新.
+
+如果已经成为 beta tester, google play service可能会自动更新到最新的。
+
+
+
+
+
+\
+
+#### 5.登陆google账号
+
+Settings\>Accounts or Seetings-\>Google(内部账号(不可给客户)：
+
+Fast Pair Validator 测试 请使用 realsilbt8888@gmail.com
+
+手动测试账号请参考 Google 账号 - BT_Market - WIKI (realtek.com)
+
+#### 6 打开自动同步数据功能
+
+由于GFPS的account key是存在google账号的云端的，所以必须要登陆google账号并且需要打开自动同步数据功能
+
+Settings\>Accounts ：
+
+
+
+or
+
+Seetings→Google:
+
+
+
+#### 7.检查Show notification是否打开：
+
+Settings\>Google\>(Devices & sharing)\>Devices(设置\>Google\>设备连接\>设备\>)
+
+pixel 2xl:
+
+
+
+pixel 7:
+
+
+
+\
+
+#### 8.Setting界面打开蓝牙，以及位置信息。
+
+\
+
+#### 9.Enable debug mode ID：
+
+The model ID provided to you is a debug mode ID. To enable it, go to Settings \> Google \> Devices & sharing \> Devices \> top right 3 dot menu to enable “Include debug results”.
+
+If the option “Include debug results” is missing in this page, please ensure Developer options in the phone is enabled.
+
+or go to Settings \> Google \> Devices & sharing \> Devices \>“Include debug results”
+
+Settings \> Google \> Devices & sharing \> Devices \> top right 3 dot menu to enable “Include debug results”
+
+
+
+or
+
+Settings \> Google \> Devices & sharing \> Devices \>“Include debug results”
+
+
+
+https://developer.android.com/studio/debug/dev-options?hl=zh-cn
+
+#### 10.Check Google Play Service version
+
+Purpose: To confirm we use right version of Fast Pair module for testing
+
+Go to Settings \> Apps¬ification or Apps\>google play services \> advanced, then check Google Play services version (It should be 20.XX.XX or higher).
+
+
+
+\
+
+\
+
+#### **11.注册成为google beta tester（内部测试账号已经注册过了，这一步不需要，如果是客户自己注册的Google账号，需要提醒客户check）**
+
+Sign up for the Google Play services beta program https://play.google.com/apps/testing/com.google.android.gms
+
+join the Android Beta group at https://www.google.com/android/beta to get latest update via OTA
+
+Finder/Find Hub testing program please Navigate to https://play.google.com/apps/testing/com.google.android.apps.adm
+
+\
+
+可以登陆Google账号之后在以下链接查看是否有添加成功：我的群组
+
+
+
+需要注意的是：
+
+
+
+如果没有权限添加，FAE需要联系YingTsung (YT) Lin， 请他发邮件给Google， 让Google把客户注册的Google账号添加到Google的Test group。
+
+\
+
+### GFPS LEA 环境搭建
+
+#### 1 https://www.google.com/android/beta your google account will need to join the Android Beta group to get the T-QPR2 release.( pixel7、pixel7 Pro 在realsilbt8888@gmail.com 上已经注册，场内QC测试可以不用关心这一步， **FAE需要提醒客户自查**)
+
+https://developer.android.com/about/versions/13/release-notes?hl=zh-cn
+
+
+
+#### \
+2 setting 界面 enable LE audio功能
+
+ Here is the setting of LE Audio in phone, if you don't see it, please follow below link to enable "Developer options". https://developer.android.com/studio/debug/dev-options
+
+
+
+\
+
+\
+
+\
+
+\
diff --git a/3.2.3+Fast+Pair+Validator+环境搭建.md b/3.2.3+Fast+Pair+Validator+环境搭建.md
new file mode 100644
index 0000000..7f6cd77
--- /dev/null
+++ b/3.2.3+Fast+Pair+Validator+环境搭建.md
@@ -0,0 +1,282 @@
+# 3.2.3 Fast Pair Validator 环境搭建
+
+
+
+
+
+- [1 搭建手机端的测试环境](#id-3.2.3FastPairValidator环境搭建-1搭建手机端的测试环境)
+ - [1.1 手机需要连接google网络](#id-3.2.3FastPairValidator环境搭建-1.1手机需要连接google网络)
+ - [1.2 手机不可以打开勿扰模式，不然可能看不到弹窗](#id-3.2.3FastPairValidator环境搭建-1.2手机不可以打开勿扰模式，不然可能看不到弹窗)
+ - [1.3 检查手机是否打开Google Play服务通知](#id-3.2.3FastPairValidator环境搭建-1.3检查手机是否打开GooglePlay服务通知)
+ - [1.4 检查google play 服务是否更新到最新的版本](#id-3.2.3FastPairValidator环境搭建-1.4检查googleplay服务是否更新到最新的版本)
+ - [1.5 登陆google账号](#id-3.2.3FastPairValidator环境搭建-1.5登陆google账号)
+ - [1.6 打开自动同步数据功能](#id-3.2.3FastPairValidator环境搭建-1.6打开自动同步数据功能)
+ - [1.7 检查Show notification是否打开：](#id-3.2.3FastPairValidator环境搭建-1.7检查Shownotification是否打开：)
+ - [1.8 Setting界面打开蓝牙，以及位置信息。](#id-3.2.3FastPairValidator环境搭建-1.8Setting界面打开蓝牙，以及位置信息。)
+ - [1.9 Enable debug mode ID：](#id-3.2.3FastPairValidator环境搭建-1.9EnabledebugmodeID：)
+ - [1.10 Check Google Play Service version](#id-3.2.3FastPairValidator环境搭建-1.10CheckGooglePlayServiceversion)
+ - [1.11 注册成为google beta tester（内部测试账号已经注册过了，这一步不需要，如果是客户自己注册的Google账号，需要提醒客户check）](#id-3.2.3FastPairValidator环境搭建-1.11注册成为googlebetatester（内部测试账号已经注册过了，这一步不需要，如果是客户自己注册的Google账号，需要提醒客户check）)
+- [2 Fast Pair Validator APP安装](#id-3.2.3FastPairValidator环境搭建-2FastPairValidatorAPP安装)
+- [3 Enable fast pair validator app中的测项](#id-3.2.3FastPairValidator环境搭建-3Enablefastpairvalidatorapp中的测项)
+ - [3.1 安装adb:](#id-3.2.3FastPairValidator环境搭建-3.1安装adb:)
+ - [3.2 输入如下命令：](#id-3.2.3FastPairValidator环境搭建-3.2输入如下命令：)
+- [4 uninstall amazon 相关app](#id-3.2.3FastPairValidator环境搭建-4uninstallamazon相关app)
+- [5 测试账号和MODEL ID](#id-3.2.3FastPairValidator环境搭建-5测试账号和MODELID)
+- [6 测试准备](#id-3.2.3FastPairValidator环境搭建-6测试准备)
+- [7 GFPS LEA 环境搭建](#id-3.2.3FastPairValidator环境搭建-7GFPSLEA环境搭建)
+ - [1 官网测试spec请参考 https://developers.google.com/nearby/fast-pair/lea-validator-app-user-manual](#id-3.2.3FastPairValidator环境搭建-1官网测试spec请参考https://developers.google.com/nearby/fast-pair/lea-validator-app-user-manual)
+ - [2 setting 界面需要 enable Bypass Bluetooth LE audio，然后重启手机](#id-3.2.3FastPairValidator环境搭建-2setting界面需要enableBypassBluetoothLEaudio，然后重启手机)
+ - [3 Google 提供的文档 \[RealTek\] Validator App LE Spec User Manual.pptx](#id-3.2.3FastPairValidator环境搭建-3Google提供的文档)
+ - [4 测试账号需要加入Google test group(内部测试账号已添加，qc不需要关注，如果是客户自己注册的账号，需要提醒客户添加)](#id-3.2.3FastPairValidator环境搭建-4测试账号需要加入Googletestgroup(内部测试账号已添加，qc不需要关注，如果是客户自己注册的账号，需要提醒客户添加))
+
+
+
+### 1 搭建手机端的测试环境
+
+测试手机建议使用Google pixel手机，请**务必确保**手机端有打开开发者选项 https://developer.android.com/studio/debug/dev-options?hl=zh-cn
+
+\
+
+#### 1.1 手机需要连接google网络
+
+该网络必须可以登陆google的网站，在测试前请先测试一下是否可以登录google的网站(**建议试试能不能打开youtube之类的**）。
+
+#### 1.2 手机不可以打开勿扰模式，不然可能看不到弹窗
+
+
+
+#### 1.3 检查手机是否打开Google Play服务通知
+
+Setting-\>(Apps¬ification or Apps)应用和通知-\> See all apps -\>Google Play服务-\>通知-\>All Google Play services notifications, 开启(显示通知)
+
+
+
+#### 1.4 检查google play 服务是否更新到最新的版本
+
+setting-\>(Apps¬ification or Apps)应用和通知-\>See all apps-\>Google Play 服务-\>高级-\>商店, 点击 App details or google play，界面会跳转到google play 商店，点击更新.
+
+如果已经成为 beta tester, google play service可能会自动更新到最新的。
+
+
+
+
+
+\
+
+#### 1.5 登陆google账号
+
+Settings\>Accounts or Seetings-\>Google(内部账号(不可给客户)：
+
+Fast Pair Validator 测试 请使用 realsilbt8888@gmail.com
+
+手动测试账号请参考 Google 账号 - BT_Market - WIKI (realtek.com)
+
+#### 1.6 打开自动同步数据功能
+
+由于GFPS的account key是存在google账号的云端的，所以必须要登陆google账号并且需要打开自动同步数据功能
+
+Settings\>Accounts ：
+
+
+
+or
+
+Seetings→Google:
+
+
+
+#### 1.7 检查Show notification是否打开：
+
+Settings\>Google\>(Devices & sharing)\>Devices(设置\>Google\>设备连接\>设备\>)
+
+pixel 2xl:
+
+
+
+pixel 7:
+
+
+
+\
+
+跑 Fast pair validator 测试之前关掉 Automatically save devices
+
+**Note: 只有realsilbt8888的账号需要关掉 Automatically save devices， 其他手动测试的账号Automatically save devices需要打开**
+
+
+
+\
+
+#### 1.8 Setting界面打开蓝牙，以及位置信息。
+
+\
+
+#### 1.9 Enable debug mode ID：
+
+The model ID provided to you is a debug mode ID. To enable it, go to Settings \> Google \> Devices & sharing \> Devices \> top right 3 dot menu to enable “Include debug results”.
+
+If the option “Include debug results” is missing in this page, please ensure Developer options in the phone is enabled.
+
+or go to Settings \> Google \> Devices & sharing \> Devices \>“Include debug results”
+
+Settings \> Google \> Devices & sharing \> Devices \> top right 3 dot menu to enable “Include debug results”
+
+
+
+or
+
+Settings \> Google \> Devices & sharing \> Devices \>“Include debug results”
+
+
+
+https://developer.android.com/studio/debug/dev-options?hl=zh-cn
+
+#### 1.10 Check Google Play Service version
+
+Purpose: To confirm we use right version of Fast Pair module for testing
+
+Go to Settings \> Apps¬ification or Apps\>google play services \> advanced, then check Google Play services version (It should be 20.XX.XX or higher).
+
+
+
+\
+
+\
+
+#### **1.11 注册成为google beta tester（内部测试账号已经注册过了，这一步不需要，如果是客户自己注册的Google账号，需要提醒客户check）**
+
+Sign up for the Google Play services beta program\
+https://play.google.com/apps/testing/com.google.android.gms
+
+join the Android Beta group at https://www.google.com/android/beta to get latest update via OTA
+
+Finder/Find Hub testing program please Navigate to https://play.google.com/apps/testing/com.google.android.apps.adm
+
+如果没有权限添加，FAE需要联系YingTsung (YT) Lin， 请他发邮件给Google， 让Google把客户注册的Google账号添加到Google的Test group。
+
+可以登陆Google账号之后在以下链接查看是否有添加成功：我的群组
+
+
+
+需要注意的是：
+
+
+
+### **2 Fast Pair Validator APP安装**
+
+确认手机是否安装 Fast Pair Validator APP
+
+Fast pair validator app 图标如下图：
+
+
+
+如果没有安装:
+
+去 Play Store/应用商店 下载 Fast Pair Validator APP并且安装。
+
+如果已经安装:
+
+确认安装的是否是最新版。不是最新版，请手动升级到最新版。确认步骤如下：
+
+长按 Fast Pair Validator 图标，会看到App info
+
+
+
+点击App info,会看到App details
+
+
+
+点击App details,会看到以下页面，如果有新版本请手动更新到最新的版本。如果是beta版本则不需要更新，系统会自动帮忙更新。
+
+
+
+### 3 Enable fast pair validator app中的测项
+
+#### 3.1 安装adb:
+
+adb安装及使用方法 该wiki上提供的adb版本太旧，会出现device offline的问题，下载最新的https://adbshell.com/downloads
+
+安装adb之后找到adb.exe所在的目录，在该目录下打开cmd命令行
+
+#### 3.2 输入如下命令：
+
+adb shell am broadcast -a com.google.location.nearby.apps.fastpair.validator.FLAG_OVERRIDE --es flag enable_features_for_v3 --es value true --es type boolean com.google.location.nearby.apps.fastpair.validator
+
+
+
+按enter执行命令。
+
+命令执行成功之后，
+
+打开fast pair validator 能看到新的feature
+
+\
+
+### 4 uninstall amazon 相关app
+
+Alexa (com.amazon.dee.app) 和com.amazon.wellness app， 会影响到Validator的测试，需要Uninstall。
+
+The Alexa (com.amazon.dee.app) took too much time on handling the ACL_CONNECTED intent, which impacts the Validator's flow.
+
+There is still another **app,com.amazon.wellness** app, who handled ACL_CONNECTED for 20+ seconds.Please uninstall it as well.
+
+现象： End-to-end integration测试，出现Pairing timeout
+
+操作方式：
+
+adb uninstall com.amazon.wellness
+
+adb uninstall com.amazon.dee.app
+
+\
+
+### 5 测试账号和MODEL ID
+
+使用Fast Pair Validator测试，需要先登陆Google账号，测试设备使用的Model ID,public key, private key 必须是该google账号注册的Device。
+
+场内测试账号：realsilbt8888@gmail.com
+
+**Note：**
+
+fast pair validator app使用的model id 要和DUT开发板配置的model id一致。
+
+
+
+### **6 测试准备**
+
+测试过程中需要注意
+
+手机端弹出配对提示框时不要手动点击，fast pair validator app会自己触发配对.
+
+开始测试前，需要确认是否已经和待测试耳机配对过，需要删除配对信息。 最后最好在开始测试前，开关一下飞行模式。
+
+点击GOT IT开始测试时，耳机端一定要处于Pairable mode，否则会scan不到设备, scan 到设备后，点击Test开始测试。
+
+
+
+\
+
+### 7 GFPS LEA 环境搭建
+
+#### 1 官网测试spec请参考 https://developers.google.com/nearby/fast-pair/lea-validator-app-user-manual
+
+#### 2 setting 界面需要 enable Bypass Bluetooth LE audio，然后重启手机
+
+
+
+#### 3 Google 提供的文档 [RealTek] Validator App LE Spec User Manual.pptx
+
+#### 4 测试账号需要加入Google test group(**内部测试账号已添加，qc不需要关注，如果是客户自己注册的账号，需要提醒客户添加**)
+
+- Ensure your testing emails are part of the Fast Pair Partner Testing Group.
+
+ - It may take 6-24 hours for newly registered emails and phones to synchronize permissions.
+
+ - Logging in and out of the associated Google Account may also trigger an immediate sync.
+
+\
diff --git a/3.3+测试.md b/3.3+测试.md
new file mode 100644
index 0000000..9143260
--- /dev/null
+++ b/3.3+测试.md
@@ -0,0 +1,21 @@
+# 3.3 测试
+
+测试完成之后要填写测试报告, 测试报告从以下位置获取：
+
+Test Case of the Third Party - BT Test - WIKI
+
+
+
+\
+
+因为设备不支援find hub(类似于苹果的findmy功能)， 所以测试报告中：
+
+Find My Device 那一页不需要测试：
+
+
+
+\
+
+Fast Pair Validator那一页 EDDYSTONE 下面的测项不需要测试：
+
+
diff --git a/3.3.1+Fast+Pair+Validator+测试.md b/3.3.1+Fast+Pair+Validator+测试.md
new file mode 100644
index 0000000..015d564
--- /dev/null
+++ b/3.3.1+Fast+Pair+Validator+测试.md
@@ -0,0 +1,11 @@
+# 3.3.1 Fast Pair Validator 测试
+
+3.3.1.1 FAST PAIR
+
+这个测项客户自测并且提交测试结果到Google云端，认证实验室暂时不会测试。
+
+目前来看只要有一次测试成功，并且有提交成功的测试结果到Google云端就可以，即使偶尔失败了，如果确定不是我们设备端的bug, 也没关系的
+
+https://partnerissuetracker.corp.google.com/u/0/issues/473688165
+
+
diff --git a/3.3.1.1+FAST+PAIR.md b/3.3.1.1+FAST+PAIR.md
new file mode 100644
index 0000000..d1bd1ed
--- /dev/null
+++ b/3.3.1.1+FAST+PAIR.md
@@ -0,0 +1,7 @@
+# 3.3.1.1 FAST PAIR
+
+请参考以下Wiki 进行测试：
+
+2 fast pair validator 测试-LE Flow - BT_Market - WIKI
+
+
diff --git a/3.3.2+手动测试.md b/3.3.2+手动测试.md
new file mode 100644
index 0000000..3f23497
--- /dev/null
+++ b/3.3.2+手动测试.md
@@ -0,0 +1 @@
+# 3.3.2 手动测试
diff --git a/3.3.2.1+Initial+pair+and+subsequent+pair.md b/3.3.2.1+Initial+pair+and+subsequent+pair.md
new file mode 100644
index 0000000..cf3cb7f
--- /dev/null
+++ b/3.3.2.1+Initial+pair+and+subsequent+pair.md
@@ -0,0 +1,9 @@
+# 3.3.2.1 Initial pair and subsequent pair
+
+google 官方测试文档：
+
+Fast Pair 3.2 & 3.3 Certification Guidelines | Google for Developers
+
+Realtek内部整理文档：
+
+1 Initial Pairing and Subsequent Pairing Test Guideline(中文文档) - BT_Market - WIKI
diff --git a/3.3.2.2+extended+feature.md b/3.3.2.2+extended+feature.md
new file mode 100644
index 0000000..0763bbf
--- /dev/null
+++ b/3.3.2.2+extended+feature.md
@@ -0,0 +1,9 @@
+# 3.3.2.2 extended feature
+
+Google 官方文档：
+
+https://developers.google.com/nearby/fast-pair/fast-pair-certification-guideline#4_feature_certification_criteria
+
+Realtek 内部整理文档：
+
+1 Extension Feature Test Guideline(中文文档) - BT_Market - WIKI
diff --git a/4+GFPS+LEA+配对主耳之后没有配对附耳.md b/4+GFPS+LEA+配对主耳之后没有配对附耳.md
new file mode 100644
index 0000000..04d4226
--- /dev/null
+++ b/4+GFPS+LEA+配对主耳之后没有配对附耳.md
@@ -0,0 +1 @@
+# 4 GFPS LEA 配对主耳之后没有配对附耳
diff --git a/4+GFPS显示名字不是mcu+config+tool+里面设置的名字问题.md b/4+GFPS显示名字不是mcu+config+tool+里面设置的名字问题.md
new file mode 100644
index 0000000..3222366
--- /dev/null
+++ b/4+GFPS显示名字不是mcu+config+tool+里面设置的名字问题.md
@@ -0,0 +1,5 @@
+# 4 GFPS显示名字不是mcu config tool 里面设置的名字问题
+
+**Q:**GFPS显示的名字为什么不是mcu config tool 里面设置的名字
+
+**A:**GFPS显示的名字是注册model id时设置的名字，和mcu config tool 中设置的名字没有关系。可以在setting界面修改该名字
diff --git a/4+LEA+++GFPS+++Find+Hub.md b/4+LEA+++GFPS+++Find+Hub.md
new file mode 100644
index 0000000..166bcae
--- /dev/null
+++ b/4+LEA+++GFPS+++Find+Hub.md
@@ -0,0 +1,3 @@
+# 4 LEA + GFPS + Find Hub
+
+该功能是通过GFPS 快速配对 LE audio， 如果同时支援BREDR， 会通过LE 的 LTK CTKD 生成 BREDR 的 linkkey, 并实现查找功能(类似于苹果的findmy)
diff --git a/4+pixel6(android+12)+不连A2DP.md b/4+pixel6(android+12)+不连A2DP.md
new file mode 100644
index 0000000..7844341
--- /dev/null
+++ b/4+pixel6(android+12)+不连A2DP.md
@@ -0,0 +1,21 @@
+# 4 pixel6(android 12) 不连A2DP
+
+[BB2BUG-50550] [BB2][RTL8763ESH/ROM][GMI][沃莱特][Harman][T530] [IOP]794 After restoring the factory Settings, click on the previous record to re-pair and connect, only the calls will be connected(5/5) - Jira
+
+测试把legacy CTKD LE关掉就可以
+
+https://partnerissuetracker.corp.google.com/u/0/issues/427370430
+
+\
+
+这个问题Google最终给出的解决方案是：
+
+device console 上面会提供一个选项 “是否支援 legacy CTKD le功能”，
+
+如果客户注册model id的时候有勾选这个功能，
+
+Android 12 的pixel手机扫到这个model id对应的设备之后就不会弹窗出来，客户需要去setting界面配对
+
+\
+
++不连A2DP_3e6271b1.jpg)
diff --git a/4+弹框提示_无法连接到查找中心_.md b/4+弹框提示_无法连接到查找中心_.md
new file mode 100644
index 0000000..5715d30
--- /dev/null
+++ b/4+弹框提示_无法连接到查找中心_.md
@@ -0,0 +1,9 @@
+# 4 弹框提示"无法连接到查找中心"
+
+legacy GFPS 要打开legacy CTKD LE功能，不然搭配支援lea的手机测试，会出现手机不连legacy profile的情况
+
+
+
+\
+
+[BBPRO3BUG-24407] [BBPRO3][EVB][E Cut][3.15.0.5+TestBin][Single]配置Finder，耳机开机进配对，无法连接到Find Device - Jira
diff --git a/4.1+Observed+standard+deviation+is+too+low,+.........md b/4.1+Observed+standard+deviation+is+too+low,+.........md
new file mode 100644
index 0000000..553f903
--- /dev/null
+++ b/4.1+Observed+standard+deviation+is+too+low,+.........md
@@ -0,0 +1,42 @@
+# 4.1 Observed standard deviation is too low, ........
+
+ BB2BUG-17449 - \[BB2\]\[RTL8763EF/ROM\]\[GMI\]\[沃莱特\]\[Harman\]\[T520\]: Finder测项中，finder_advertisement rotation测试失败 Closed
+
+Hi Avner:
+
+We test advertising rotation failed, could you help see the reason, thanks
+
+
+
+\
+
+Hi Danni,\
+\
+The reason that this test fails is that the device under test rotates EID/MAC pretty much precisely every 1024 seconds (standard deviation is 0.83 seconds).\
+\
+Per spec the exact rotation time should be randomized, please refer to the "ID Rotation" section.
+
+\
+
+Hi Mark:
+
+
+
+1.Does the positive randomized time factor have a value range? Can you provide some reference ranges?
+
+2.Is the standard deviation must be greater than 0.83?
+
+\
+
++David Lazarov Can you please attach the latest version of the spec which includes the recommended randomization values?
+
+
+
+Hi Danni,
+
+
+
+1. The recommended size of the randomization window is 20% of the interval, i.e. 204 seconds. So when the device needs to compute the next time point to rotate EID/MAC, it's going to be *floor((last_rotation_time_seconds + 1024) / 1024) \* 1024 + random(0, 204). *
+2. *Standard deviation of 0.83 seconds practically means there's no randomization. We expect standard deviation to be much higher, typically 50-60 seconds, or more.*
+
+\
diff --git a/4.1+Project+工程enable对应功能.md b/4.1+Project+工程enable对应功能.md
new file mode 100644
index 0000000..edabe53
--- /dev/null
+++ b/4.1+Project+工程enable对应功能.md
@@ -0,0 +1,59 @@
+# 4.1 Project 工程enable对应功能
+
+app_flags.h 里面找到 CONFIG_REALTEK_GFPS_XXX 相关的宏并按照以下信息配置：
+
+\#define CONFIG_REALTEK_GFPS_FEATURE_SUPPORT 1\
+\#define CONFIG_REALTEK_GFPS_LE_DEVICE_SUPPORT (1 && CONFIG_REALTEK_GFPS_FEATURE_SUPPORT)\
+\#define CONFIG_REALTEK_GFPS_SASS_SUPPORT (0 && CONFIG_REALTEK_GFPS_FEATURE_SUPPORT)\
+\#define CONFIG_REALTEK_GFPS_FINDER_SUPPORT (1 && CONFIG_REALTEK_GFPS_FEATURE_SUPPORT)
+
+GFPS依赖的其他的模块：
+
+\#if CONFIG_REALTEK_GFPS_FEATURE_SUPPORT\
+\#undef F_APP_RWS_BLE_USE_RPA_SUPPORT\
+\#define F_APP_RWS_BLE_USE_RPA_SUPPORT 1
+
+\#undef F_APP_SC_KEY_DERIVE_SUPPORT\
+\#define F_APP_SC_KEY_DERIVE_SUPPORT 1
+
+\#if CONFIG_REALTEK_GFPS_LE_DEVICE_SUPPORT\
+\#undef F_APP_GATT_CACHING_SUPPORT\
+\#define F_APP_GATT_CACHING_SUPPORT 1\
+\#endif
+
+\#if CONFIG_REALTEK_GFPS_FINDER_SUPPORT\
+\#undef F_APP_PERIODIC_WAKEUP\
+\#define F_APP_PERIODIC_WAKEUP 0// default not enable\
+\#endif\
+\#endif
+
+\
+
+Note:
+
+有的IC宏的名字是GFPS_XXX, app_flags.h 里面找到 GFPS_XXX 相关的宏并按照以下信息配置：
+
+\#define GFPS_FEATURE_SUPPORT 1\
+\#define GFPS_LE_DEVICE_SUPPORT (1 && GFPS_FEATURE_SUPPORT)\
+\#define GFPS_SASS_SUPPORT (0 && GFPS_FEATURE_SUPPORT)\
+\#define GFPS_FINDER_SUPPORT (1 && GFPS_FEATURE_SUPPORT)
+
+GFPS依赖的其他的模块：
+
+\#if GFPS_FEATURE_SUPPORT\
+\#undef F_APP_RWS_BLE_USE_RPA_SUPPORT\
+\#define F_APP_RWS_BLE_USE_RPA_SUPPORT 1
+
+\#undef F_APP_SC_KEY_DERIVE_SUPPORT\
+\#define F_APP_SC_KEY_DERIVE_SUPPORT 1
+
+\#if GFPS_LE_DEVICE_SUPPORT\
+\#undef F_APP_GATT_CACHING_SUPPORT\
+\#define F_APP_GATT_CACHING_SUPPORT 1\
+\#endif
+
+\#if GFPS_FINDER_SUPPORT\
+\#undef F_APP_PERIODIC_WAKEUP\
+\#define F_APP_PERIODIC_WAKEUP 0// default not enable\
+\#endif\
+\#endif
diff --git a/4.2+advertisement+rotation+fail-“device+not+find+by+EID”.md b/4.2+advertisement+rotation+fail-“device+not+find+by+EID”.md
new file mode 100644
index 0000000..2148b6a
--- /dev/null
+++ b/4.2+advertisement+rotation+fail-“device+not+find+by+EID”.md
@@ -0,0 +1,7 @@
+# 4.2 advertisement rotation fail-“device not find by EID”
+
+
+
+ BTQCSZ-6289 - \[BB2\]\[C-CUT\]\[8763EF\]\[HARMAN\]\[Finder\]advertisement rotation fail Closed
+
+和[provisioning for non-owner fail--"invalid authentication not rejected"](/pages/viewpage.action?pageId=392048170) 好像是类似的问题。
diff --git a/4.2+测试环境搭建.md b/4.2+测试环境搭建.md
new file mode 100644
index 0000000..eacb135
--- /dev/null
+++ b/4.2+测试环境搭建.md
@@ -0,0 +1 @@
+# 4.2 测试环境搭建
diff --git a/4.2.1+设备端环境搭建.md b/4.2.1+设备端环境搭建.md
new file mode 100644
index 0000000..4d46586
--- /dev/null
+++ b/4.2.1+设备端环境搭建.md
@@ -0,0 +1,405 @@
+# 4.2.1 设备端环境搭建
+
+
+
+
+
+- [1 MCUConfigTool 配置](#id-4.2.1设备端环境搭建-1MCUConfigTool配置)
+ - [1.1 General 页面 : 不勾选 Enable auto power off, 不勾选 Enable pairing timeout](#id-4.2.1设备端环境搭建-1.1General页面:不勾选Enableautopoweroff,不勾选Enablepairingtimeout)
+ - [1.2 General 页面 : Discoverable in standby mode 设置成disable。强制要求必须修改](#id-4.2.1设备端环境搭建-1.2General页面:Discoverableinstandbymode设置成disable。强制要求必须修改)
+ - [1.3 General 页面: 勾选 Non-discoverable when linkback 强制要求必须修改](#id-4.2.1设备端环境搭建-1.3General页面:勾选Non-discoverablewhenlinkback强制要求必须修改)
+ - [1.4 勾选Multi-link support, 并且不要勾选 Enter pairing state while only available device is connected 强制要求必须修改](#id-4.2.1设备端环境搭建-1.4勾选Multi-linksupport,并且不要勾选Enterpairingstatewhileonlyavailabledeviceisconnected强制要求必须修改)
+ - [1.5 Third Party页面配置GFPS参数](#id-4.2.1设备端环境搭建-1.5ThirdParty页面配置GFPS参数)
+ - [1.6 配置GFPS findme voice prompt tone](#id-4.2.1设备端环境搭建-1.6配置GFPSfindmevoiceprompttone)
+ - [1.7 保存新生成的 APP UI Parameter File 和 System Config File](#id-4.2.1设备端环境搭建-1.7保存新生成的APPUIParameterFile和SystemConfigFile)
+ - [1.8 Note](#id-4.2.1设备端环境搭建-1.8Note)
+- [2 TWS 耳机 GFPS battery feature测试环境搭建(只有TWS耳机需要做GFPS battery测试，single mode 不需要测试)](#id-4.2.1设备端环境搭建-2TWS耳机GFPSbatteryfeature测试环境搭建(只有TWS耳机需要做GFPSbattery测试，singlemode不需要测试))
+ - [2.1.mcu config tool 配置：](#id-4.2.1设备端环境搭建-2.1.mcuconfigtool配置：)
+ - [2.1.1 HW Feature 模块](#id-4.2.1设备端环境搭建-2.1.1HWFeature模块)
+ - [2.1.2 charger 模块，勾选battery detection support](#id-4.2.1设备端环境搭建-2.1.2charger模块，勾选batterydetectionsupport)
+ - [2.1.3 general 模块](#id-4.2.1设备端环境搭建-2.1.3general模块)
+ - [2.2.充电盒配置：](#id-4.2.1设备端环境搭建-2.2.充电盒配置：)
+ - [2.2.1 接线设置](#id-4.2.1设备端环境搭建-2.2.1接线设置)
+ - [2.2.2 充电盒操作](#id-4.2.1设备端环境搭建-2.2.2充电盒操作)
+ - [2.3 Note](#id-4.2.1设备端环境搭建-2.3Note)
+ - [2.3.1 开关盒操作步骤](#id-4.2.1设备端环境搭建-2.3.1开关盒操作步骤)
+ - [2.3.2 HUN显示测试](#id-4.2.1设备端环境搭建-2.3.2HUN显示测试)
+ - [2.3.3 demo rcfg](#id-4.2.1设备端环境搭建-2.3.3demorcfg)
+- [3 GFPS LEA 环境搭建](#id-4.2.1设备端环境搭建-3GFPSLEA环境搭建)
+ - [1. enbale lea 以及disconnect enter lea pairing mode](#id-4.2.1设备端环境搭建-1.enbalelea以及disconnectenterleapairingmode)
+ - [2.配置stack相关参数](#id-4.2.1设备端环境搭建-2.配置stack相关参数)
+ - [EATT 暂时设置成 Disable](#id-4.2.1设备端环境搭建-EATT暂时设置成Disable)
+ - [Enable GATT Caching](#id-4.2.1设备端环境搭建-EnableGATTCaching)
+ - [3.配置GFPS参数](#id-4.2.1设备端环境搭建-3.配置GFPS参数)
+ - [4.配置ringtone](#id-4.2.1设备端环境搭建-4.配置ringtone)
+ - [5. 配置按键进入pairing mode](#id-4.2.1设备端环境搭建-5.配置按键进入pairingmode)
+ - [6 配置按键退出pairing mode](#id-4.2.1设备端环境搭建-6配置按键退出pairingmode)
+ - [7 配置GFPS LEA pairing mode 提示音](#id-4.2.1设备端环境搭建-7配置GFPSLEApairingmode提示音)
+- [4 Find Hub测试环境搭建：](#id-4.2.1设备端环境搭建-4FindHub测试环境搭建：)
+ - [4.1 每一轮测试开始之前耳机端需要做factory reset操作，测试中请不要做factory reset。原因如下：8 手机端清掉配对信息之后，耳机端也要做factory reset，不然finder功能用不起来](#id-4.2.1设备端环境搭建-4.1每一轮测试开始之前耳机端需要做factoryreset操作，测试中请不要做factoryreset。原因如下：)
+ - [4.2 finder 所有功能测试完成之后，测试手机归还QC之前，手机端一定要清掉配对信息，不然过段时间再测试的时候可能会有问题，手机log会提示设备已经有owner了，会比较麻烦，建议测试完成之后一定要先把手机端的配对信息全清掉 1 gfps/finder 如何清除配对信息](#id-4.2.1设备端环境搭建-4.2finder所有功能测试完成之后，测试手机归还QC之前，手机端一定要清掉配对信息，不然过段时间再测试的时候可能会有问题，手机log会提示设备已经有owner了，会比较麻烦，建议测试完成之后一定要先把手机端的配对信息全清掉)
+ - [4.3 MCU cfg tool中model id和key的信息要换成支持finder 的model id 和key的信息，测试账号必须只能使用某个固定的Google账号，暂时还不可以使用多个Google账号进行测试。](#id-4.2.1设备端环境搭建-4.3MCUcfgtool中modelid和key的信息要换成支持finder的modelid和key的信息，测试账号必须只能使用某个固定的Google账号，暂时还不可以使用多个Google账号进行测试。)
+ - [4.4 2024/5/11以后：更新至finder1.3后，需要填写注册model id的时候填写的 ”Company name”, ”Device name” 和 ”Device type”（当前已支持harman T520）](#id-4.2.1设备端环境搭建-4.42024/5/11以后：更新至finder1.3后，需要填写注册modelid的时候填写的”Companyname”,”Devicename”和”Devicetype”（当前已支持harmanT520）)
+ - [4.5 .MCU cfg tool 需要配置按键停止响铃功能](#id-4.2.1设备端环境搭建-4.5.MCUcfgtool需要配置按键停止响铃功能)
+ - [4.6 Finder adv 需要占用一条BLE link，GFPS adv要占用一条 BLE link, 所以这边LE link number 和 LE slave link number要在原有的基础上+2](#id-4.2.1设备端环境搭建-4.6Finderadv需要占用一条BLElink，GFPSadv要占用一条BLElink,所以这边LElinknumber和LEslavelinknumber要在原有的基础上+2)
+ - [4.7 要想让finder响铃，mcu cfg tool 需要配置对应的vp](#id-4.2.1设备端环境搭建-4.7要想让finder响铃，mcucfgtool需要配置对应的vp)
+ - [4.8 mcu cfg tool 需要enable finder 功能](#id-4.2.1设备端环境搭建-4.8mcucfgtool需要enablefinder功能)
+ - [4.9 2024/5/11： 更新至finder1.3后，KEY配置界面需要配置按键0xBB Dult enter id read state mode](#id-4.2.1设备端环境搭建-4.92024/5/11：更新至finder1.3后，KEY配置界面需要配置按键0xBBDultenteridreadstatemode)
+ - [4.10 2024/5/11： 更新至finder1.3后，Ringtone配置页面需要配置GFPS find dult（当前已支持harman T520，该案比较特殊，分为两个响铃：GFPS find dult tone和GFPS find dult vp）](#id-4.2.1设备端环境搭建-4.102024/5/11：更新至finder1.3后，Ringtone配置页面需要配置GFPSfinddult（当前已支持harmanT520，该案比较特殊，分为两个响铃：GFPSfinddulttone和GFPSfinddultvp）)
+ - [4.11 如果需要关机之后依然打finder广播需要配置以下信息：](#id-4.2.1设备端环境搭建-4.11如果需要关机之后依然打finder广播需要配置以下信息：)
+
+
+
+### 1 MCUConfigTool 配置
+
+#### 1.1 General 页面 : 不勾选 Enable auto power off, 不勾选 Enable pairing timeout
+
+**Note**:
+
+修改为了便于GFPS测试，GFPS 测试的时候或者是过认证的时候需要修改， **量产时可以考虑不修改。**
+
+
+
+#### 1.2 General 页面 : Discoverable in standby mode 设置成disable。**强制要求必须修改**
+
+**Note**:
+
+GFPS 耳机第一次和一只手机配对成功之后(initial pairing 成功)，就会进入 subsequent pairing mode。
+
+所以initial pairing 成功之后，不管耳机是进入idle mode 还是进入connectable mode(multilink 支持)，都不应该再设置成discoverable。
+
+
+
+#### 1.3 General 页面: 勾选 Non-discoverable when linkback **强制要求必须修改**
+
+linkback模式下DUT不应该discoverable，不然手机端会一直弹配对窗口。
+
+\
+
+
+
+#### 1.4 勾选Multi-link support, 并且不要勾选 Enter pairing state while only available device is connected **强制要求必须修改**
+
+下面红框里的**不可以勾选 **不然battery HUN测试可能测不过， ** BBPRO2BUG-21515 - Getting issue details... STATUS **
+
+
+
+#### 1.5 Third Party页面配置GFPS参数
+
+在Third Party页面配置GFPS参数，详细信息参考 mcu cfg tool中 GFPS 各配置项的含义 - BT_Market - WIKI
+
+
+
+下面是RTK已通过认证的Module ID
+
+[认证结果及认证通过的model_id 和key](/pages/viewpage.action?pageId=204620689)
+
+#### 1.6 配置GFPS findme voice prompt tone
+
+gfps_findme.wav
+
+自行选择wav文件作为findme vp tone，
+
+wav文件名称可以自行修改，放入MCU config tool vp目录，
+
+建议findme的wav文件可以播放久一些，这样才能达到提示的效果。
+
+如下图所示：
+
+
+
+打开MCU config tool开始配置findme tone，
+
+首先refresh一下，让tool能够识别新的wav文件，
+
+然后就可以选择vp tone了，
+
+如下图所示：
+
+
+
+
+
+#### 1.7 保存新生成的 APP UI Parameter File 和 System Config File
+
+#### **1.8 Note**
+
+1.建议把BD Address和Device Name也改一下
+
+2.建议Export 生成rcfg之前先导入正确的flash_map.ini
+
+
+
+\
+
+### 2 TWS 耳机 GFPS battery feature测试环境搭建(只有TWS耳机需要做GFPS battery测试，single mode 不需要测试)
+
+Note：
+
+测试battery的时候需要搭配充电盒
+
+#### 2.1.mcu config tool 配置：
+
+##### 2.1.1 HW Feature 模块
+
+ 勾选Charger功能：
+
+
+
+勾选支持充电盒功能，注意如果充电盒image烧录的是20ms,下面红色框中的40ms也要改成20ms,这个要和充电盒image匹配的。
+
+如果充电盒image 烧录的是40ms：
+
+
+
+如果充电盒image烧录的是20ms:\
+
+
+勾选power off immediately when chose case和do not auto power off when case not close
+
+
+
+##### 2.1.2 charger 模块，勾选battery detection support
+
+
+
+
+
+
+
+##### 2.1.3 general 模块
+
+
+
+2.1.4 third party 模块 enable battery 功能
+
+
+
+#### 2.2.充电盒配置：
+
+##### 2.2.1 接线设置
+
+
+
+##### 2.2.2 充电盒操作
+
+
+
+#### **2.3 Note**
+
+##### 2.3.1 开关盒操作步骤
+
+1.左右耳factory reset 之后，先按下出盒入盒按钮（确保两个按钮同时按下，代表左右耳机入盒），耳机入盒之后，再按下开盒关盒按钮(按键弹起是开盒)，耳机端可以听到power on的提示音，说明开盒成功。有时候开盒成功但是没有提示音，此时可以看一下log：
+
+app_adp_handle_msg +++++ AD2B_CMD_POWER_ON =3，如果有AD2B_CMD_POWER_ON的log说明开盒成功
+
+2.按下开盒关盒按钮，按键按下是关盒，耳机端可以听到power off的提示音，说明关盒成功。有时候关盒成功但是没有提示音，此时可以看一下log：
+
+app_adp_handle_msg +++++ AD2B_CMD_POWER_OFF =4，如果有AD2B_CMD_POWER_OFF的log说明关盒成功
+
+3.如果重新烧录app的bin. 烧录完成之后要先按一下reset按键，然后按开盒关盒按钮进行操作。
+
+**4.关盒之后，3s关机，关机之后 3s会 watch dog reset，故关盒之后建议等10s才可以再次开盒，否则开机流程可能会不正常：**
+
+相关代码修改(仅用于GFPS认证)：
+
+关盒之后3s关机：
+
+\#define ADP_CLOSE_CASE_TIMEOUT_MS 3000
+
+关机之后，打开power off的提示音(目前没有打开，可以不需要修改，使用默认配置就好)
+
+
+
+watch dog reset的时间改成6s,目前没有设置成6s,使用默认设置3s，目前测试看是ok的，所以这个也可以不用修改
+
+
+
+##### 2.3.2 HUN显示测试
+
+HUN(Heads up notification)显示图如下：
+
+
+
+一次HUN显示成功之后，需要先把上次的显示信息清掉,再执行下一次操作：
+
+
+
+\
+
+##### 2.3.3 demo rcfg
+
+GFPS_Left.rcfg
+
+GFPS_Right.rcfg
+
+\
+
+### 3 GFPS LEA 环境搭建
+
+#### 1. enbale lea 以及disconnect enter lea pairing mode
+
+
+
+
+
+#### 2.配置stack相关参数
+
+##### EATT 暂时设置成 Disable
+
+
+
+##### Enable GATT Caching
+
+
+
+\
+
+#### 3.配置GFPS参数
+
+
+
+\
+
+GFPS device mode 设置成 Dual mode device with CSIP (**这边取名字为CSIP取的有点问题，实际是想声明是否支援LE audio, 后面会请tool 帮忙把CSIP 改成LE audio**)，
+
+**如果找不到 Dual mode device with CSIP 应该是 新的 mcu cfg tool 有改名字将 CSIP 统一改成 LE audio了， tool上可以设置成 Dual mode device with LE audio**
+
+[BTSOCTOOL-5234] GFPS页面CSIP改成LE audio - Jira
+
+
+
+\
+
+#### 4.配置ringtone
+
+
+
+
+
+\
+
+
+
+\
+
+#### 5. 配置按键进入pairing mode
+
+将key1设置成 GFPS LEA enter pair mode(0xB9), 作为GFPS le audio 按键强制进入pairing mode 的MMI，
+
+有的客户不想多配置一个按键，想要复用 legacy 进Pairing mode的mmi, 那么key1也可以配置成 MMI(0x6C)
+
+\
+
+
+
+或者是
+
+
+
+单击key1 GFPS LE audio 会强制进入pairing mode
+
+手机弹窗出来之后， 配对 GFPS LE audio,
+
+正常配对成功之后会直接退出pairing mode，
+
+如果按键进入pairing mode 之后，手机端一直没有配对耳机，那耳机会一直处于pairing mode，需要配置按键退出pairing mode。
+
+例如：
+
+#### 6 配置按键退出pairing mode
+
+
+
+或者是
+
+
+
+\
+
+#### 7 配置GFPS LEA pairing mode 提示音
+
+
+
+\
+
+### **4 Find Hub测试环境搭建：**
+
+#### 4.1 每一轮测试开始之前耳机端需要做factory reset操作，测试中请不要做factory reset。原因如下：[8 手机端清掉配对信息之后，耳机端也要做factory reset，不然finder功能用不起来](/pages/viewpage.action?pageId=350190807)
+
+#### 4.2 finder 所有功能测试完成之后，测试手机归还QC之前，手机端一定要清掉配对信息，不然过段时间再测试的时候可能会有问题，手机log会提示设备已经有owner了，会比较麻烦，建议测试完成之后一定要先把手机端的配对信息全清掉 [1 gfps/finder 如何清除配对信息](/pages/viewpage.action?pageId=401291585)
+
+#### 4.3 MCU cfg tool中model id和key的信息要换成支持finder 的model id 和key的信息，测试账号必须只能使用某个固定的Google账号，暂时还不可以使用多个Google账号进行测试。
+
+ 内部测试model id 和Company name, Device name 和 Device type 请参考 [7 TWS耳机-finder-内部测试model id](/pages/viewpage.action?pageId=350177663)：
+
+
+
+#### 4.4 2024/5/11以后：更新至finder1.3后，需要填写注册model id的时候填写的 ”Company name”, ”Device name” 和 ”Device type”（当前已支持harman T520）
+
+Device type双耳测试选Earphones，单耳测试选Headphones
+
+
+
+#### 4.5 .MCU cfg tool 需要配置按键停止响铃功能
+
+for example:
+
+配置key1接P3_1
+
+
+
+配置key1短按之后触发GFPS finder停止响铃
+
+
+
+开发板上 key1 接到M3_1
+
+
+
+#### 4.6 Finder adv 需要占用一条BLE link，GFPS adv要占用一条 BLE link, 所以这边LE link number 和 LE slave link number要在原有的基础上+2
+
+
+
+\
+
+#### 4.7 要想让finder响铃，mcu cfg tool 需要配置对应的vp
+
+
+
+\
+
+#### 4.8 mcu cfg tool 需要enable finder 功能
+
+
+
+\
+
+#### 4.9 2024/5/11： 更新至finder1.3后，KEY配置界面需要配置按键0xBB Dult enter id read state mode
+
+
+
+\
+
+#### 4.10 2024/5/11： 更新至finder1.3后，Ringtone配置页面需要配置GFPS find dult（当前已支持harman T520，该案比较特殊，分为两个响铃：GFPS find dult tone和GFPS find dult vp）
+
+
+
+
+
+\
+
+#### 4.11 如果需要关机之后依然打finder广播需要配置以下信息：
+
+详细信息可以参考mcu cfg tool中 GFPS 各配置项的含义 - BT_Market - WIKI 中的: ”9. GFPS Finder相关配置信息描述”
+
+
+
+\
+
+\
diff --git a/4.2.2+手机端环境搭建.md b/4.2.2+手机端环境搭建.md
new file mode 100644
index 0000000..a60a7bc
--- /dev/null
+++ b/4.2.2+手机端环境搭建.md
@@ -0,0 +1,270 @@
+# 4.2.2 手机端环境搭建
+
+
+
+
+
+- [GFPS 环境搭建](#id-4.2.2手机端环境搭建-GFPS环境搭建)
+ - [1.手机需要连接google网络](#id-4.2.2手机端环境搭建-1.手机需要连接google网络)
+ - [2.手机不可以打开勿扰模式，不然可能看不到弹窗](#id-4.2.2手机端环境搭建-2.手机不可以打开勿扰模式，不然可能看不到弹窗)
+ - [3.检查手机是否打开Google Play服务通知](#id-4.2.2手机端环境搭建-3.检查手机是否打开GooglePlay服务通知)
+ - [4.检查google play 服务是否更新到最新的版本](#id-4.2.2手机端环境搭建-4.检查googleplay服务是否更新到最新的版本)
+ - [5.登陆google账号](#id-4.2.2手机端环境搭建-5.登陆google账号)
+ - [6 打开自动同步数据功能](#id-4.2.2手机端环境搭建-6打开自动同步数据功能)
+ - [7.检查Show notification是否打开：](#id-4.2.2手机端环境搭建-7.检查Shownotification是否打开：)
+ - [8.Setting界面打开蓝牙，以及位置信息。](#id-4.2.2手机端环境搭建-8.Setting界面打开蓝牙，以及位置信息。)
+ - [9.Enable debug mode ID：](#id-4.2.2手机端环境搭建-9.EnabledebugmodeID：)
+ - [10.Check Google Play Service version](#id-4.2.2手机端环境搭建-10.CheckGooglePlayServiceversion)
+ - [11.注册成为google beta tester（内部测试账号已经注册过了，这一步不需要，如果是客户自己注册的Google账号，需要提醒客户check）](#id-4.2.2手机端环境搭建-11.注册成为googlebetatester（内部测试账号已经注册过了，这一步不需要，如果是客户自己注册的Google账号，需要提醒客户check）)
+- [GFPS LEA 环境搭建](#id-4.2.2手机端环境搭建-GFPSLEA环境搭建)
+ - [1 https://www.google.com/android/beta your google account will need to join the Android Beta group to get the T-QPR2 release.( pixel7、pixel7 Pro 在realsilbt8888@gmail.com 上已经注册，场内QC测试可以不用关心这一步， FAE需要提醒客户自查)](#id-4.2.2手机端环境搭建-1https://www.google.com/android/betayourgoogleaccountwillneedtojointheAndroidBetagrouptogettheT-QPR2release.(pixel7、pixel7Pro在realsilbt8888@gmail.com上已经注册，场内QC测试可以不用关心这一步，FAE需要提醒客户自查))
+ - [2 setting 界面 enable LE audio功能](#id-4.2.2手机端环境搭建-2setting界面enableLEaudio功能)
+- [Find hub 环境搭建](#id-4.2.2手机端环境搭建-Findhub环境搭建)
+ - [1. The Google Find Hub App must be installed and updated to the latest Beta version.](#id-4.2.2手机端环境搭建-1.TheGoogleFindHubAppmustbeinstalledandupdatedtothelatestBetaversion.)
+ - [1.1 如果没有安装：](#id-4.2.2手机端环境搭建-1.1如果没有安装：)
+ - [1.2 如果已经安装：](#id-4.2.2手机端环境搭建-1.2如果已经安装：)
+ - [1.2.1 长按 Find hub 图标，会看到App info](#id-4.2.2手机端环境搭建-1.2.1长按Findhub图标，会看到Appinfo)
+ - [1.2.2 点击App info,会看到 App details](#id-4.2.2手机端环境搭建-1.2.2点击Appinfo,会看到Appdetails)
+ - [1.2.3 点击App details,会看到以下页面，如果有新版本请手动更新到最新的版本。如果是beta版本则不需要更新，系统会自动帮忙更新。](#id-4.2.2手机端环境搭建-1.2.3点击Appdetails,会看到以下页面，如果有新版本请手动更新到最新的版本。如果是beta版本则不需要更新，系统会自动帮忙更新。)
+ - [2."Use Find Hub" must be enabled under "Settings \> Google \> Find Hub".](#id-4.2.2手机端环境搭建-2.%22UseFindHub%22mustbeenabledunder%22Settings%3EGoogle%3EFindHub%22.)
+ - [3 "Find your offline devices" must be set to "With network in all areas" under "Settings \> Google \> Find Hub".](#id-4.2.2手机端环境搭建-3%22Findyourofflinedevices%22mustbesetto%22Withnetworkinallareas%22under%22Settings%3EGoogle%3EFindHub%22.)
+ - [4.“Scan for nearby devices” and “Include debug results” must be enabled under “Settings\> Google \> Devices and sharing \> Devices”.](#id-4.2.2手机端环境搭建-4.“Scanfornearbydevices”and“Includedebugresults”mustbeenabledunder“Settings%3EGoogle%3EDevicesandsharing%3EDevices”.)
+ - [5.Should be connected to the google Internet and have Bluetooth and Location turned on in Settings.](#id-4.2.2手机端环境搭建-5.ShouldbeconnectedtothegoogleInternetandhaveBluetoothandLocationturnedoninSettings.)
+ - [6 测试账号需要加入(内部测试账号已加入，qc测试不需要关心，FAE需要提醒客户自查)](#id-4.2.2手机端环境搭建-6测试账号需要加入(内部测试账号已加入，qc测试不需要关心，FAE需要提醒客户自查))
+ - [7 如果测试手机支援LEA, 开发者选项中将 Bypass Bluetooth LE Audio 选项关掉，然后重启手机](#id-4.2.2手机端环境搭建-7如果测试手机支援LEA,开发者选项中将BypassBluetoothLEAudio选项关掉，然后重启手机)
+
+
+
+\
+
+该测试至少要准备两只手机。测试手机建议使用Google pixel手机， Pixel 5+ is recommended. 请**务必确保**手机端有打开开发者选项 https://developer.android.com/studio/debug/dev-options?hl=zh-cn
+
+\
+
+### GFPS 环境搭建
+
+#### 1.手机需要连接google网络
+
+该网络必须可以登陆google的网站，在测试前请先测试一下是否可以登录google的网站(**建议试试能不能打开youtube之类的**）。
+
+#### 2.手机不可以打开勿扰模式，不然可能看不到弹窗
+
+
+
+#### 3.检查手机是否打开Google Play服务通知
+
+Setting-\>(Apps¬ification or Apps)应用和通知-\> See all apps -\>Google Play服务-\>通知-\>All Google Play services notifications, 开启(显示通知)
+
+
+
+\
+
+#### 4.检查google play 服务是否更新到最新的版本
+
+setting-\>(Apps¬ification or Apps)应用和通知-\>See all apps-\>Google Play 服务-\>高级-\>商店, 点击 App details or google play，界面会跳转到google play 商店，点击更新.
+
+如果已经成为 beta tester, google play service可能会自动更新到最新的。
+
+
+
+
+
+\
+
+#### 5.登陆google账号
+
+Settings\>Accounts or Seetings-\>Google(内部账号(不可给客户)：
+
+Fast Pair Validator 测试 请使用 realsilbt8888@gmail.com
+
+手动测试账号请参考 Google 账号 - BT_Market - WIKI (realtek.com)
+
+#### 6 打开自动同步数据功能
+
+由于GFPS的account key是存在google账号的云端的，所以必须要登陆google账号并且需要打开自动同步数据功能
+
+Settings\>Accounts ：
+
+
+
+or
+
+Seetings→Google:
+
+
+
+#### 7.检查Show notification是否打开：
+
+Settings\>Google\>(Devices & sharing)\>Devices(设置\>Google\>设备连接\>设备\>)
+
+pixel 2xl:
+
+
+
+pixel 7:
+
+
+
+\
+
+#### 8.Setting界面打开蓝牙，以及位置信息。
+
+\
+
+#### 9.Enable debug mode ID：
+
+The model ID provided to you is a debug mode ID. To enable it, go to Settings \> Google \> Devices & sharing \> Devices \> top right 3 dot menu to enable “Include debug results”.
+
+If the option “Include debug results” is missing in this page, please ensure Developer options in the phone is enabled.
+
+or go to Settings \> Google \> Devices & sharing \> Devices \>“Include debug results”
+
+Settings \> Google \> Devices & sharing \> Devices \> top right 3 dot menu to enable “Include debug results”
+
+
+
+or
+
+Settings \> Google \> Devices & sharing \> Devices \>“Include debug results”
+
+
+
+https://developer.android.com/studio/debug/dev-options?hl=zh-cn
+
+#### 10.Check Google Play Service version
+
+Purpose: To confirm we use right version of Fast Pair module for testing
+
+Go to Settings \> Apps¬ification or Apps\>google play services \> advanced, then check Google Play services version (It should be 20.XX.XX or higher).
+
+
+
+\
+
+\
+
+#### **11.注册成为google beta tester（内部测试账号已经注册过了，这一步不需要，如果是客户自己注册的Google账号，需要提醒客户check）**
+
+Sign up for the Google Play services beta program https://play.google.com/apps/testing/com.google.android.gms
+
+join the Android Beta group at https://www.google.com/android/beta to get latest update via OTA
+
+Finder/Find Hub testing program please Navigate to https://play.google.com/apps/testing/com.google.android.apps.adm
+
+\
+
+可以登陆Google账号之后在以下链接查看是否有添加成功：我的群组
+
+
+
+需要注意的是：
+
+
+
+如果没有权限添加，FAE需要联系YingTsung (YT) Lin， 请他发邮件给Google， 让Google把客户注册的Google账号添加到Google的Test group。
+
+\
+
+### GFPS LEA 环境搭建
+
+#### 1 https://www.google.com/android/beta your google account will need to join the Android Beta group to get the T-QPR2 release.( pixel7、pixel7 Pro 在realsilbt8888@gmail.com 上已经注册，场内QC测试可以不用关心这一步， **FAE需要提醒客户自查**)
+
+https://developer.android.com/about/versions/13/release-notes?hl=zh-cn
+
+
+
+#### \
+2 setting 界面 enable LE audio功能
+
+ Here is the setting of LE Audio in phone, if you don't see it, please follow below link to enable "Developer options". https://developer.android.com/studio/debug/dev-options
+
+
+
+\
+
+### Find hub 环境搭建
+
+#### 1. The Google Find Hub App must be installed and updated to the latest Beta version.
+
+确认手机是否安装 Find Hub, 图标如下图：
+
+ 
+
+##### 1.1 如果没有安装：
+
+去 Play Store/应用商店 下载Find Hub并且安装。
+
+##### 1.2 如果已经安装：
+
+确认安装的是否是最新版。不是最新版，请手动升级到最新版。确认步骤如下：
+
+###### 1.2.1 长按 Find hub 图标，会看到App info
+
+
+
+###### 1.2.2 点击App info,会看到 App details
+
+
+
+###### 1.2.3 点击App details,会看到以下页面，如果有新版本请手动更新到最新的版本。如果是beta版本则不需要更新，系统会自动帮忙更新。
+
+
+
+\
+
+#### 2.*"Use Find Hub"* must be enabled under *"Settings \> Google \> Find Hub"*.
+
+
+
+
+
+or
+
+手机端打开 finder功能.mp4
+
+\
+
+#### *3 "Find your offline devices"* must be set to *"With network in all areas"* under *"Settings \> Google \> Find Hub"*.
+
+
+
+
+
+\
+
+\
+
+#### 4.“Scan for nearby devices” and “Include debug results” must be enabled under “Settings\> Google \> Devices and sharing \> Devices”.
+
+
+
+\
+
+#### 5.Should be connected to the google Internet and have Bluetooth and Location turned on in Settings.
+
+
+
+\
+
+#### **6 测试账号需要加入(内部测试账号已加入，qc测试不需要关心，FAE需要提醒客户自查)**
+
+Google Play services testing program： Navigate to https://play.google.com/apps/testing/com.google.android.gms
+
+Find My Device testing program： Navigate to https://play.google.com/apps/testing/com.google.android.apps.adm.
+
+如果没有权限，需要联系Google帮忙添加账号权限。
+
+\
+
+#### **7 如果测试手机支援LEA, 开发者选项中将 Bypass Bluetooth LE Audio 选项关掉，然后重启手机**
+
+****
+
+\
+
+\
diff --git a/4.2.3+Fast+Pair+Validator+环境搭建.md b/4.2.3+Fast+Pair+Validator+环境搭建.md
new file mode 100644
index 0000000..d7a3151
--- /dev/null
+++ b/4.2.3+Fast+Pair+Validator+环境搭建.md
@@ -0,0 +1,351 @@
+# 4.2.3 Fast Pair Validator 环境搭建
+
+
+
+
+
+- [1 搭建手机端的测试环境](#id-4.2.3FastPairValidator环境搭建-1搭建手机端的测试环境)
+ - [1.1 手机需要连接google网络](#id-4.2.3FastPairValidator环境搭建-1.1手机需要连接google网络)
+ - [1.2 手机不可以打开勿扰模式，不然可能看不到弹窗](#id-4.2.3FastPairValidator环境搭建-1.2手机不可以打开勿扰模式，不然可能看不到弹窗)
+ - [1.3 检查手机是否打开Google Play服务通知](#id-4.2.3FastPairValidator环境搭建-1.3检查手机是否打开GooglePlay服务通知)
+ - [1.4 检查google play 服务是否更新到最新的版本](#id-4.2.3FastPairValidator环境搭建-1.4检查googleplay服务是否更新到最新的版本)
+ - [1.5 登陆google账号](#id-4.2.3FastPairValidator环境搭建-1.5登陆google账号)
+ - [1.6 打开自动同步数据功能](#id-4.2.3FastPairValidator环境搭建-1.6打开自动同步数据功能)
+ - [1.7 检查Show notification是否打开：](#id-4.2.3FastPairValidator环境搭建-1.7检查Shownotification是否打开：)
+ - [1.8 Setting界面打开蓝牙，以及位置信息。](#id-4.2.3FastPairValidator环境搭建-1.8Setting界面打开蓝牙，以及位置信息。)
+ - [1.9 Enable debug mode ID：](#id-4.2.3FastPairValidator环境搭建-1.9EnabledebugmodeID：)
+ - [1.10 Check Google Play Service version](#id-4.2.3FastPairValidator环境搭建-1.10CheckGooglePlayServiceversion)
+ - [1.11 注册成为google beta tester（内部测试账号已经注册过了，这一步不需要，如果是客户自己注册的Google账号，需要提醒客户check）](#id-4.2.3FastPairValidator环境搭建-1.11注册成为googlebetatester（内部测试账号已经注册过了，这一步不需要，如果是客户自己注册的Google账号，需要提醒客户check）)
+- [2 Fast Pair Validator APP安装](#id-4.2.3FastPairValidator环境搭建-2FastPairValidatorAPP安装)
+- [3 Enable fast pair validator app中的测项](#id-4.2.3FastPairValidator环境搭建-3Enablefastpairvalidatorapp中的测项)
+ - [3.1 安装adb:](#id-4.2.3FastPairValidator环境搭建-3.1安装adb:)
+ - [3.2 输入如下命令：](#id-4.2.3FastPairValidator环境搭建-3.2输入如下命令：)
+- [4 uninstall amazon 相关app](#id-4.2.3FastPairValidator环境搭建-4uninstallamazon相关app)
+- [5 测试账号和MODEL ID](#id-4.2.3FastPairValidator环境搭建-5测试账号和MODELID)
+- [6 测试准备](#id-4.2.3FastPairValidator环境搭建-6测试准备)
+- [7 GFPS LEA 环境搭建](#id-4.2.3FastPairValidator环境搭建-7GFPSLEA环境搭建)
+ - [1 官网测试spec请参考 https://developers.google.com/nearby/fast-pair/lea-validator-app-user-manual](#id-4.2.3FastPairValidator环境搭建-1官网测试spec请参考https://developers.google.com/nearby/fast-pair/lea-validator-app-user-manual)
+ - [2 setting 界面需要 enable Bypass Bluetooth LE audio，然后重启手机](#id-4.2.3FastPairValidator环境搭建-2setting界面需要enableBypassBluetoothLEaudio，然后重启手机)
+ - [3 Google 提供的文档 \[RealTek\] Validator App LE Spec User Manual.pptx](#id-4.2.3FastPairValidator环境搭建-3Google提供的文档)
+ - [4 测试账号需要加入Google test group(内部测试账号已添加，qc不需要关注，如果是客户自己注册的账号，需要提醒客户添加)](#id-4.2.3FastPairValidator环境搭建-4测试账号需要加入Googletestgroup(内部测试账号已添加，qc不需要关注，如果是客户自己注册的账号，需要提醒客户添加))
+- [8 Find hub 环境搭建:](#id-4.2.3FastPairValidator环境搭建-8Findhub环境搭建:)
+ - [1.认证实验室会重新跑 fast pair validator中finder相关的测项，所以送认证前最好提供各个测项的操作视频以及详细的操作步骤(如何开机，如何factory reset，如何进pairing mode..)](#id-4.2.3FastPairValidator环境搭建-1.认证实验室会重新跑fastpairvalidator中finder相关的测项，所以送认证前最好提供各个测项的操作视频以及详细的操作步骤(如何开机，如何factoryreset，如何进pairingmode..))
+ - [2.如果测试手机支援LEA, 开发者选项中将 Bypass Bluetooth LE Audio 选项关掉，然后重启手机](#id-4.2.3FastPairValidator环境搭建-2.如果测试手机支援LEA,开发者选项中将BypassBluetoothLEAudio选项关掉，然后重启手机)
+ - [3.一定要等所有的测项都测试PASS之后才可以提交测试结果](#id-4.2.3FastPairValidator环境搭建-3.一定要等所有的测项都测试PASS之后才可以提交测试结果)
+ - [4. Fast pair validator enable EDDYSTONE：](#id-4.2.3FastPairValidator环境搭建-4.FastpairvalidatorenableEDDYSTONE：)
+ - [1.打开fast pair validator, 登陆Google账号，找到和耳机对应的model id，点击model id之后会看到EDDYSTONE, 点击进行测试](#id-4.2.3FastPairValidator环境搭建-1.打开fastpairvalidator,登陆Google账号，找到和耳机对应的modelid，点击modelid之后会看到EDDYSTONE,点击进行测试)
+ - [2.如果看不到 EDDYSTONE， 需要 adb 执行以下两个commands:](#id-4.2.3FastPairValidator环境搭建-2.如果看不到EDDYSTONE，需要adb执行以下两个commands:)
+ - [3.然后选择EDDYSTONE 进行测试：](#id-4.2.3FastPairValidator环境搭建-3.然后选择EDDYSTONE进行测试：)
+ - [4.Finder Fast Pair Validator EDDYSTONE测试完成。测试结果提交：](#id-4.2.3FastPairValidator环境搭建-4.FinderFastPairValidatorEDDYSTONE测试完成。测试结果提交：)
+
+
+
+### 1 搭建手机端的测试环境
+
+测试手机建议使用Google pixel手机，请**务必确保**手机端有打开开发者选项 https://developer.android.com/studio/debug/dev-options?hl=zh-cn
+
+\
+
+#### 1.1 手机需要连接google网络
+
+该网络必须可以登陆google的网站，在测试前请先测试一下是否可以登录google的网站(**建议试试能不能打开youtube之类的**）。
+
+#### 1.2 手机不可以打开勿扰模式，不然可能看不到弹窗
+
+
+
+#### 1.3 检查手机是否打开Google Play服务通知
+
+Setting-\>(Apps¬ification or Apps)应用和通知-\> See all apps -\>Google Play服务-\>通知-\>All Google Play services notifications, 开启(显示通知)
+
+
+
+#### 1.4 检查google play 服务是否更新到最新的版本
+
+setting-\>(Apps¬ification or Apps)应用和通知-\>See all apps-\>Google Play 服务-\>高级-\>商店, 点击 App details or google play，界面会跳转到google play 商店，点击更新.
+
+如果已经成为 beta tester, google play service可能会自动更新到最新的。
+
+
+
+
+
+\
+
+#### 1.5 登陆google账号
+
+Settings\>Accounts or Seetings-\>Google(内部账号(不可给客户)：
+
+Fast Pair Validator 测试 请使用 realsilbt8888@gmail.com
+
+手动测试账号请参考 Google 账号 - BT_Market - WIKI (realtek.com)
+
+#### 1.6 打开自动同步数据功能
+
+由于GFPS的account key是存在google账号的云端的，所以必须要登陆google账号并且需要打开自动同步数据功能
+
+Settings\>Accounts ：
+
+
+
+or
+
+Seetings→Google:
+
+
+
+#### 1.7 检查Show notification是否打开：
+
+Settings\>Google\>(Devices & sharing)\>Devices(设置\>Google\>设备连接\>设备\>)
+
+pixel 2xl:
+
+
+
+pixel 7:
+
+
+
+\
+
+跑 Fast pair validator 测试之前关掉 Automatically save devices
+
+**Note: 只有realsilbt8888的账号需要关掉 Automatically save devices， 其他手动测试的账号Automatically save devices需要打开**
+
+
+
+\
+
+#### 1.8 Setting界面打开蓝牙，以及位置信息。
+
+\
+
+#### 1.9 Enable debug mode ID：
+
+The model ID provided to you is a debug mode ID. To enable it, go to Settings \> Google \> Devices & sharing \> Devices \> top right 3 dot menu to enable “Include debug results”.
+
+If the option “Include debug results” is missing in this page, please ensure Developer options in the phone is enabled.
+
+or go to Settings \> Google \> Devices & sharing \> Devices \>“Include debug results”
+
+Settings \> Google \> Devices & sharing \> Devices \> top right 3 dot menu to enable “Include debug results”
+
+
+
+or
+
+Settings \> Google \> Devices & sharing \> Devices \>“Include debug results”
+
+
+
+https://developer.android.com/studio/debug/dev-options?hl=zh-cn
+
+#### 1.10 Check Google Play Service version
+
+Purpose: To confirm we use right version of Fast Pair module for testing
+
+Go to Settings \> Apps¬ification or Apps\>google play services \> advanced, then check Google Play services version (It should be 20.XX.XX or higher).
+
+
+
+\
+
+\
+
+#### **1.11 注册成为google beta tester（内部测试账号已经注册过了，这一步不需要，如果是客户自己注册的Google账号，需要提醒客户check）**
+
+Sign up for the Google Play services beta program\
+https://play.google.com/apps/testing/com.google.android.gms
+
+join the Android Beta group at https://www.google.com/android/beta to get latest update via OTA
+
+Finder/Find Hub testing program please Navigate to https://play.google.com/apps/testing/com.google.android.apps.adm
+
+如果没有权限添加，FAE需要联系YingTsung (YT) Lin， 请他发邮件给Google， 让Google把客户注册的Google账号添加到Google的Test group。
+
+可以登陆Google账号之后在以下链接查看是否有添加成功：我的群组
+
+
+
+需要注意的是：
+
+
+
+### **2 Fast Pair Validator APP安装**
+
+确认手机是否安装 Fast Pair Validator APP
+
+Fast pair validator app 图标如下图：
+
+
+
+如果没有安装:
+
+去 Play Store/应用商店 下载 Fast Pair Validator APP并且安装。
+
+如果已经安装:
+
+确认安装的是否是最新版。不是最新版，请手动升级到最新版。确认步骤如下：
+
+长按 Fast Pair Validator 图标，会看到App info
+
+
+
+点击App info,会看到App details
+
+
+
+点击App details,会看到以下页面，如果有新版本请手动更新到最新的版本。如果是beta版本则不需要更新，系统会自动帮忙更新。
+
+
+
+### 3 Enable fast pair validator app中的测项
+
+#### 3.1 安装adb:
+
+adb安装及使用方法 该wiki上提供的adb版本太旧，会出现device offline的问题，下载最新的https://adbshell.com/downloads
+
+安装adb之后找到adb.exe所在的目录，在该目录下打开cmd命令行
+
+#### 3.2 输入如下命令：
+
+adb shell am broadcast -a com.google.location.nearby.apps.fastpair.validator.FLAG_OVERRIDE --es flag enable_features_for_v3 --es value true --es type boolean com.google.location.nearby.apps.fastpair.validator
+
+
+
+按enter执行命令。
+
+命令执行成功之后，
+
+打开fast pair validator 能看到新的feature
+
+\
+
+### 4 uninstall amazon 相关app
+
+Alexa (com.amazon.dee.app) 和com.amazon.wellness app， 会影响到Validator的测试，需要Uninstall。
+
+The Alexa (com.amazon.dee.app) took too much time on handling the ACL_CONNECTED intent, which impacts the Validator's flow.
+
+There is still another **app,com.amazon.wellness** app, who handled ACL_CONNECTED for 20+ seconds.Please uninstall it as well.
+
+现象： End-to-end integration测试，出现Pairing timeout
+
+操作方式：
+
+adb uninstall com.amazon.wellness
+
+adb uninstall com.amazon.dee.app
+
+\
+
+### 5 测试账号和MODEL ID
+
+使用Fast Pair Validator测试，需要先登陆Google账号，测试设备使用的Model ID,public key, private key 必须是该google账号注册的Device。
+
+场内测试账号：realsilbt8888@gmail.com
+
+**Note：**
+
+fast pair validator app使用的model id 要和DUT开发板配置的model id一致。
+
+
+
+### **6 测试准备**
+
+测试过程中需要注意
+
+手机端弹出配对提示框时不要手动点击，fast pair validator app会自己触发配对.
+
+开始测试前，需要确认是否已经和待测试耳机配对过，需要删除配对信息。 最后最好在开始测试前，开关一下飞行模式。
+
+点击GOT IT开始测试时，耳机端一定要处于Pairable mode，否则会scan不到设备, scan 到设备后，点击Test开始测试。
+
+
+
+\
+
+### 7 GFPS LEA 环境搭建
+
+#### 1 官网测试spec请参考 https://developers.google.com/nearby/fast-pair/lea-validator-app-user-manual
+
+#### 2 setting 界面需要 enable Bypass Bluetooth LE audio，然后重启手机
+
+
+
+#### 3 Google 提供的文档 [RealTek] Validator App LE Spec User Manual.pptx
+
+#### 4 测试账号需要加入Google test group(**内部测试账号已添加，qc不需要关注，如果是客户自己注册的账号，需要提醒客户添加**)
+
+- Ensure your testing emails are part of the Fast Pair Partner Testing Group.
+
+ - It may take 6-24 hours for newly registered emails and phones to synchronize permissions.
+
+ - Logging in and out of the associated Google Account may also trigger an immediate sync.
+
+\
+
+### 8 Find hub 环境搭建:
+
+#### **1.认证实验室会重新跑 fast pair validator中finder相关的测项，所以送认证前最好提供各个测项的操作视频以及详细的操作步骤(如何开机，如何factory reset，如何进pairing mode..)**
+
+#### **2.如果测试手机支援LEA, 开发者选项中将 Bypass Bluetooth LE Audio 选项关掉，然后重启手机**
+
+****
+
+#### **3.一定要等所有的测项都测试PASS之后才可以提交测试结果**
+
+如果存在Fail的测项，不可以提交测试结果！！！
+
+如果存在Fail的测项，不可以提交测试结果！！！
+
+如果存在Fail的测项，不可以提交测试结果！！！
+
+#### 4. Fast pair validator enable EDDYSTONE：
+
+##### 1.打开fast pair validator, 登陆Google账号，找到和耳机对应的model id，点击model id之后会看到EDDYSTONE, 点击进行测试
+
+##### 2.如果看不到 EDDYSTONE， 需要 adb 执行以下两个commands:
+
+cmd1:
+
+adb shell am broadcast -a com.google.location.nearby.apps.fastpair.validator.FLAG_OVERRIDE --es flag enable_qa_input_for_fast_pair --es value true --es type boolean com.google.location.nearby.apps.fastpair.validator
+
+cmd2：
+
+adb shell am broadcast -a com.google.location.nearby.apps.fastpair.validator.FLAG_OVERRIDE --es flag enable_spot_tests --es value true --es type boolean com.google.location.nearby.apps.fastpair.validator
+
+log信息如下：
+
+
+
+\
+
+For locator tags that don't create a bond during pairing, also run the following command:
+
+cmd3：
+
+```
+adb shell am broadcast -a com.google.location.nearby.apps.fastpair.validator.FLAG_OVERRIDE --es flag skip_bonding_for_spot_locator_tags --es value true --es type boolean com.google.location.nearby.apps.fastpair.validator
+```
+
+##### 3.然后选择EDDYSTONE 进行测试：
+
+
+
+
+
+##### 4.Finder Fast Pair Validator EDDYSTONE测试完成。测试结果提交：\
+ \
+
+
+测试jira:
+
+ BTQCSZ-6106 - Getting issue details... STATUS
+
+\
diff --git a/4.3+_MAC+address+rotated,+but+EID+did+not_.md b/4.3+_MAC+address+rotated,+but+EID+did+not_.md
new file mode 100644
index 0000000..a9ebd47
--- /dev/null
+++ b/4.3+_MAC+address+rotated,+but+EID+did+not_.md
@@ -0,0 +1,5 @@
+# 4.3 "MAC address rotated, but EID did not"
+
+[BB2BUG-47970] [BB2][D-CUT][8763EKH][Harman][T530][v3.13.2.2+test bin]advertisement rotation Test fail - Jira
+
+
diff --git a/4.3+测试.md b/4.3+测试.md
new file mode 100644
index 0000000..47cc872
--- /dev/null
+++ b/4.3+测试.md
@@ -0,0 +1,7 @@
+# 4.3 测试
+
+测试完成之后要填写测试报告, 测试报告从以下位置获取：
+
+Test Case of the Third Party - BT Test - WIKI
+
+
diff --git a/4.3.1+Fast+Pair+Validator+测试.md b/4.3.1+Fast+Pair+Validator+测试.md
new file mode 100644
index 0000000..5e06bde
--- /dev/null
+++ b/4.3.1+Fast+Pair+Validator+测试.md
@@ -0,0 +1,17 @@
+# 4.3.1 Fast Pair Validator 测试
+
+4.3.1.2 EDDYSTONE
+
+** 这个必须要保证可以PASS，因为认证实验室会使用Fast Pair Validator 测试Finder相关的测项**
+
+\
+
+4.3.1.1 FAST PAIR
+
+这个测项客户自测并且提交测试结果到Google云端，认证实验室暂时不会测试。
+
+目前来看只要有一次测试成功，并且有提交成功的测试结果到Google云端就可以，即使偶尔失败了，如果确定不是我们设备端的bug, 也没关系的
+
+https://partnerissuetracker.corp.google.com/u/0/issues/473688165
+
+
diff --git a/4.3.1.1+FAST+PAIR.md b/4.3.1.1+FAST+PAIR.md
new file mode 100644
index 0000000..e5b934e
--- /dev/null
+++ b/4.3.1.1+FAST+PAIR.md
@@ -0,0 +1,7 @@
+# 4.3.1.1 FAST PAIR
+
+请参考以下Wiki 进行测试：
+
+2 fast pair validator 测试-LE Flow - BT_Market - WIKI
+
+
diff --git a/4.3.1.2+EDDYSTONE.md b/4.3.1.2+EDDYSTONE.md
new file mode 100644
index 0000000..ddce8d1
--- /dev/null
+++ b/4.3.1.2+EDDYSTONE.md
@@ -0,0 +1,5 @@
+# 4.3.1.2 EDDYSTONE
+
+请参考以下Wiki中的测项进行测试 2 Fast Pair validator Finder 测试 - BT_Market - WIKI
+
+
diff --git a/4.3.2+手动测试.md b/4.3.2+手动测试.md
new file mode 100644
index 0000000..6addfb7
--- /dev/null
+++ b/4.3.2+手动测试.md
@@ -0,0 +1 @@
+# 4.3.2 手动测试
diff --git a/4.3.2.1+Initial+pair+and+subsequent+pair.md b/4.3.2.1+Initial+pair+and+subsequent+pair.md
new file mode 100644
index 0000000..13f8912
--- /dev/null
+++ b/4.3.2.1+Initial+pair+and+subsequent+pair.md
@@ -0,0 +1,9 @@
+# 4.3.2.1 Initial pair and subsequent pair
+
+google 官方测试文档：
+
+Fast Pair 3.2 & 3.3 Certification Guidelines | Google for Developers
+
+Realtek内部整理文档：
+
+1 Initial Pairing and Subsequent Pairing Test Guideline(中文文档) - BT_Market - WIKI
diff --git a/4.3.2.2+extended+feature.md b/4.3.2.2+extended+feature.md
new file mode 100644
index 0000000..163e4ad
--- /dev/null
+++ b/4.3.2.2+extended+feature.md
@@ -0,0 +1,9 @@
+# 4.3.2.2 extended feature
+
+Google 官方文档：
+
+https://developers.google.com/nearby/fast-pair/fast-pair-certification-guideline#4_feature_certification_criteria
+
+Realtek 内部整理文档：
+
+1 Extension Feature Test Guideline(中文文档) - BT_Market - WIKI
diff --git a/4.3.2.3+find+hub.md b/4.3.2.3+find+hub.md
new file mode 100644
index 0000000..feb9e7b
--- /dev/null
+++ b/4.3.2.3+find+hub.md
@@ -0,0 +1,5 @@
+# 4.3.2.3 find hub
+
+请参考以下Wiki 中的test case 进行测试 1 Finder-手机"Find My Device"APP测试-v1.3 - BT_Market - WIKI
+
+
diff --git a/5+Find+device响铃时，手机端提示couldn't+connect.md b/5+Find+device响铃时，手机端提示couldn't+connect.md
new file mode 100644
index 0000000..9222439
--- /dev/null
+++ b/5+Find+device响铃时，手机端提示couldn't+connect.md
@@ -0,0 +1,19 @@
+# 5 Find device响铃时，手机端提示couldn't connect
+
+
+
+ BB2BUG-18476 - \[BB2\]\[8773ESL\]\[v3.13.0.7\]\[GFPS\]\[LE Audio\]Find device响铃时，有时候停止响铃失败 In Progress
+
+\
+
+Hey Danni,
+
+It looks like the Provider did not respond on the Ring action.
+
+Per Device action spec, please send ACK to the Seeker, thanks!
+
+\
+
+适配 GFPS msg through BLE 的时候 忘记回ACK了
+
+
diff --git a/5+find+hub.md b/5+find+hub.md
new file mode 100644
index 0000000..770becc
--- /dev/null
+++ b/5+find+hub.md
@@ -0,0 +1,3 @@
+# 5 find hub
+
+该功能不需要配对LE，只是通过GFPS实现查找功能(类似于苹果的findmy）
diff --git a/5+finder+弹窗不出现.md b/5+finder+弹窗不出现.md
new file mode 100644
index 0000000..ff39c1f
--- /dev/null
+++ b/5+finder+弹窗不出现.md
@@ -0,0 +1,35 @@
+# 5 finder 弹窗不出现
+
+建议分析步骤：
+
+1.请qc先用我们内部finder测试账号试试看，finder弹窗是否可以正常出现， 测试请参考 Test case1：Pairing and provisioning 测试视频 - BT_Market - WIKI
+
+ 如果内部finder测试账号也没有finder弹窗，可以建jira给danni
+
+\
+
+2.如果内部finder测试账号有finder弹窗，但是客户测试账号没有finder弹窗， 应该是客户的测试账号没有加入到finder的test group
+
+可以把客户的测试账号给YingTsung (YT) Lin，请他忙咨询Google，是不是客户账号没有加入GFPS/Find Hub/LE audio/SASS的test group
+
+\
+
+\
+
+测试情况：
+
+1.我们内部账号下载的谷歌查找中心app（版本和客户账号下载的不一样，并且可以加入beta版本），可以正常弹finder弹窗
+
+2.使用客户账号下载谷歌查找中心app，下载的版本是固定的（和我们账号下载的版本不一样，且无法加入beta版本），和我们账号下载的app版本不一样，测试下来是无法弹finder弹窗的
+
+\
+
+解决方案:
+
+请FAE将客户账号给YT， 请YT(YingTsung (YT) Lin)忙咨询Google，是不是客户账号没有加入GFPS/Find Hub/LE audio/SASS的test group
+
+\
+
+\
+
+\
diff --git a/5.1+project+工程enable对应功能.md b/5.1+project+工程enable对应功能.md
new file mode 100644
index 0000000..bbd364f
--- /dev/null
+++ b/5.1+project+工程enable对应功能.md
@@ -0,0 +1,51 @@
+# 5.1 project 工程enable对应功能
+
+app_flags.h 里面找到 CONFIG_REALTEK_GFPS_XXX 相关的宏并按照以下信息配置：
+
+\#define CONFIG_REALTEK_GFPS_FEATURE_SUPPORT 1\
+\#define CONFIG_REALTEK_GFPS_LE_DEVICE_SUPPORT (1 && CONFIG_REALTEK_GFPS_FEATURE_SUPPORT)\
+\#define CONFIG_REALTEK_GFPS_SASS_SUPPORT (0 && CONFIG_REALTEK_GFPS_FEATURE_SUPPORT)\
+\#define CONFIG_REALTEK_GFPS_FINDER_SUPPORT (1 && CONFIG_REALTEK_GFPS_FEATURE_SUPPORT)
+
+GFPS依赖的其他的模块：
+
+\#if CONFIG_REALTEK_GFPS_FEATURE_SUPPORT\
+\#undef F_APP_RWS_BLE_USE_RPA_SUPPORT\
+\#define F_APP_RWS_BLE_USE_RPA_SUPPORT 1
+
+\#if CONFIG_REALTEK_GFPS_FINDER_SUPPORT\
+\#undef F_APP_PERIODIC_WAKEUP\
+\#define F_APP_PERIODIC_WAKEUP 0// default not enable\
+\#endif\
+\#endif
+
+Note:
+
+有的IC宏的名字是GFPS_XXX, app_flags.h 里面找到 GFPS_XXX 相关的宏并按照以下信息配置：
+
+\#define GFPS_FEATURE_SUPPORT 1\
+\#define GFPS_LE_DEVICE_SUPPORT (1 && GFPS_FEATURE_SUPPORT)\
+\#define GFPS_SASS_SUPPORT (0 && GFPS_FEATURE_SUPPORT)\
+\#define GFPS_FINDER_SUPPORT (1 && GFPS_FEATURE_SUPPORT)
+
+GFPS依赖的其他的模块：
+
+\#if GFPS_FEATURE_SUPPORT\
+\#undef F_APP_RWS_BLE_USE_RPA_SUPPORT\
+\#define F_APP_RWS_BLE_USE_RPA_SUPPORT 1
+
+\#if GFPS_FINDER_SUPPORT\
+\#undef F_APP_PERIODIC_WAKEUP\
+\#define F_APP_PERIODIC_WAKEUP 0// default not enable\
+\#endif\
+\#endif
+
+\
+
+内部测试的话，工程里面需要替换以下文件(**里面包含model id信息 不可以给客户！！！**)：
+
+app_gfps_cfg.c
+
+app_gfps_cfg.h
+
+
diff --git a/5.2+测试环境搭建.md b/5.2+测试环境搭建.md
new file mode 100644
index 0000000..c039539
--- /dev/null
+++ b/5.2+测试环境搭建.md
@@ -0,0 +1 @@
+# 5.2 测试环境搭建
diff --git a/5.2.1+设备端环境搭建.md b/5.2.1+设备端环境搭建.md
new file mode 100644
index 0000000..6ea77dc
--- /dev/null
+++ b/5.2.1+设备端环境搭建.md
@@ -0,0 +1,191 @@
+# 5.2.1 设备端环境搭建
+
+
+
+
+
+- [1 MCUConfigTool 配置](#id-5.2.1设备端环境搭建-1MCUConfigTool配置)
+ - [1.1 General 页面 : 不勾选 Enable auto power off, 不勾选 Enable pairing timeout](#id-5.2.1设备端环境搭建-1.1General页面:不勾选Enableautopoweroff,不勾选Enablepairingtimeout)
+ - [1.2 General 页面 : Discoverable in standby mode 设置成disable。强制要求必须修改](#id-5.2.1设备端环境搭建-1.2General页面:Discoverableinstandbymode设置成disable。强制要求必须修改)
+ - [1.3 General 页面: 勾选 Non-discoverable when linkback 强制要求必须修改](#id-5.2.1设备端环境搭建-1.3General页面:勾选Non-discoverablewhenlinkback强制要求必须修改)
+ - [1.4 Third Party页面配置GFPS参数](#id-5.2.1设备端环境搭建-1.4ThirdParty页面配置GFPS参数)
+ - [1.5 配置GFPS findme voice prompt tone](#id-5.2.1设备端环境搭建-1.5配置GFPSfindmevoiceprompttone)
+ - [1.6 保存新生成的 APP UI Parameter File 和 System Config File](#id-5.2.1设备端环境搭建-1.6保存新生成的APPUIParameterFile和SystemConfigFile)
+ - [1.7 Note](#id-5.2.1设备端环境搭建-1.7Note)
+ - [1.建议把BD Address和Device Name也改一下](#id-5.2.1设备端环境搭建-1.建议把BDAddress和DeviceName也改一下)
+ - [2.建议Export 生成rcfg之前先导入正确的flash_map.ini](#id-5.2.1设备端环境搭建-2.建议Export生成rcfg之前先导入正确的flash_map.ini)
+- [2 Find Hub测试环境搭建](#id-5.2.1设备端环境搭建-2FindHub测试环境搭建)
+ - [2.1 每一轮测试开始之前耳机端需要做factory reset操作，测试中请不要做factory reset。原因如下：8 手机端清掉配对信息之后，耳机端也要做factory reset，不然finder功能用不起来](#id-5.2.1设备端环境搭建-2.1每一轮测试开始之前耳机端需要做factoryreset操作，测试中请不要做factoryreset。原因如下：)
+ - [2.2 finder 所有功能测试完成之后，测试手机归还QC之前，手机端一定要清掉配对信息，不然过段时间再测试的时候可能会有问题，手机log会提示设备已经有owner了，会比较麻烦，建议测试完成之后一定要先把手机端的配对信息全清掉 1 gfps/finder 如何清除配对信息](#id-5.2.1设备端环境搭建-2.2finder所有功能测试完成之后，测试手机归还QC之前，手机端一定要清掉配对信息，不然过段时间再测试的时候可能会有问题，手机log会提示设备已经有owner了，会比较麻烦，建议测试完成之后一定要先把手机端的配对信息全清掉)
+ - [2.3 MCU cfg tool中model id和key的信息要换成支持finder 的model id 和key的信息，测试账号必须只能使用某个固定的Google账号，暂时还不可以使用多个Google账号进行测试。](#id-5.2.1设备端环境搭建-2.3MCUcfgtool中modelid和key的信息要换成支持finder的modelid和key的信息，测试账号必须只能使用某个固定的Google账号，暂时还不可以使用多个Google账号进行测试。)
+ - [2.4 2024/5/11以后：更新至finder1.3后，需要填写注册model id的时候填写的 ”Company name”, ”Device name” 和 ”Device type”](#id-5.2.1设备端环境搭建-2.42024/5/11以后：更新至finder1.3后，需要填写注册modelid的时候填写的”Companyname”,”Devicename”和”Devicetype”)
+ - [2.5 .MCU cfg tool 需要配置按键停止响铃功能](#id-5.2.1设备端环境搭建-2.5.MCUcfgtool需要配置按键停止响铃功能)
+ - [2.6 Finder adv 需要占用一条BLE link，GFPS adv要占用一条 BLE link, 所以这边LE link number 和 LE slave link number要在原有的基础上+2](#id-5.2.1设备端环境搭建-2.6Finderadv需要占用一条BLElink，GFPSadv要占用一条BLElink,所以这边LElinknumber和LEslavelinknumber要在原有的基础上+2)
+ - [2.7 要想让finder响铃，mcu cfg tool 需要配置对应的vp](#id-5.2.1设备端环境搭建-2.7要想让finder响铃，mcucfgtool需要配置对应的vp)
+ - [2.8 mcu cfg tool 需要enable finder 功能](#id-5.2.1设备端环境搭建-2.8mcucfgtool需要enablefinder功能)
+ - [2.9 2024/5/11： 更新至finder1.3后，KEY配置界面需要配置按键0xBB Dult enter id read state mode](#id-5.2.1设备端环境搭建-2.92024/5/11：更新至finder1.3后，KEY配置界面需要配置按键0xBBDultenteridreadstatemode)
+ - [2.10 2024/5/11： 更新至finder1.3后，Ringtone配置页面需要配置GFPS find dult（Harman案子比较特殊，分为两个响铃：GFPS find dult tone和GFPS find dult vp， 其他案子一般就一个）](#id-5.2.1设备端环境搭建-2.102024/5/11：更新至finder1.3后，Ringtone配置页面需要配置GFPSfinddult（Harman案子比较特殊，分为两个响铃：GFPSfinddulttone和GFPSfinddultvp，其他案子一般就一个）)
+ - [2.11 如果需要关机之后依然打finder广播需要配置以下信息：](#id-5.2.1设备端环境搭建-2.11如果需要关机之后依然打finder广播需要配置以下信息：)
+
+
+
+### 1 MCUConfigTool 配置
+
+#### 1.1 General 页面 : 不勾选 Enable auto power off, 不勾选 Enable pairing timeout
+
+**Note**:
+
+修改为了便于GFPS测试，GFPS 测试的时候或者是过认证的时候需要修改， **量产时可以考虑不修改。**
+
+
+
+#### 1.2 General 页面 : Discoverable in standby mode 设置成disable。**强制要求必须修改**
+
+**Note**:
+
+GFPS 耳机第一次和一只手机配对成功之后(initial pairing 成功)，就会进入 subsequent pairing mode。
+
+所以initial pairing 成功之后，不管耳机是进入idle mode 还是进入connectable mode(multilink 支持)，都不应该再设置成discoverable。
+
+
+
+#### 1.3 General 页面: 勾选 Non-discoverable when linkback **强制要求必须修改**
+
+linkback模式下DUT不应该discoverable，不然手机端会一直弹配对窗口。
+
+\
+
+
+
+#### 1.4 Third Party页面配置GFPS参数
+
+在Third Party页面配置GFPS参数，详细信息参考 mcu cfg tool中 GFPS 各配置项的含义 - BT_Market - WIKI
+
+
+
+\
+
+
+
+\
+
+#### 1.5 配置GFPS findme voice prompt tone
+
+gfps_findme.wav
+
+自行选择wav文件作为findme vp tone，
+
+wav文件名称可以自行修改，放入MCU config tool vp目录，
+
+建议findme的wav文件可以播放久一些，这样才能达到提示的效果。
+
+如下图所示：
+
+
+
+打开MCU config tool开始配置findme tone，
+
+首先refresh一下，让tool能够识别新的wav文件，
+
+然后就可以选择vp tone了，
+
+如下图所示：
+
+
+
+
+
+#### 1.6 保存新生成的 APP UI Parameter File 和 System Config File
+
+#### **1.7 Note**
+
+##### 1.建议把BD Address和Device Name也改一下
+
+##### 2.建议Export 生成rcfg之前先导入正确的flash_map.ini
+
+
+
+\
+
+### **2 Find Hub测试环境搭建**
+
+#### 2.1 每一轮测试开始之前耳机端需要做factory reset操作，测试中请不要做factory reset。原因如下：[8 手机端清掉配对信息之后，耳机端也要做factory reset，不然finder功能用不起来](/pages/viewpage.action?pageId=350190807)
+
+#### 2.2 finder 所有功能测试完成之后，测试手机归还QC之前，手机端一定要清掉配对信息，不然过段时间再测试的时候可能会有问题，手机log会提示设备已经有owner了，会比较麻烦，建议测试完成之后一定要先把手机端的配对信息全清掉 [1 gfps/finder 如何清除配对信息](/pages/viewpage.action?pageId=401291585)
+
+#### 2.3 MCU cfg tool中model id和key的信息要换成支持finder 的model id 和key的信息，测试账号必须只能使用某个固定的Google账号，暂时还不可以使用多个Google账号进行测试。
+
+ 内部测试model id 和Company name, Device name 和 Device type 请参考
+
+如果是Dual mode， model id 请参考 4. dual mode locator tag model id - BT_Market - WIKI
+
+如果是le only mode, model id 请参考 LE only locator tracker model id - BT_Market - WIKI
+
+
+
+#### 2.4 2024/5/11以后：更新至finder1.3后，需要填写注册model id的时候填写的 ”Company name”, ”Device name” 和 ”Device type”
+
+
+
+#### 2.5 .MCU cfg tool 需要配置按键停止响铃功能
+
+for example:
+
+配置key1接P3_1
+
+
+
+配置key1短按之后触发GFPS finder停止响铃
+
+
+
+开发板上 key1 接到M3_1
+
+
+
+#### 2.6 Finder adv 需要占用一条BLE link，GFPS adv要占用一条 BLE link, 所以这边LE link number 和 LE slave link number要在原有的基础上+2
+
+
+
+\
+
+#### 2.7 要想让finder响铃，mcu cfg tool 需要配置对应的vp
+
+
+
+\
+
+#### 2.8 mcu cfg tool 需要enable finder 功能
+
+
+
+\
+
+#### 2.9 2024/5/11： 更新至finder1.3后，KEY配置界面需要配置按键0xBB Dult enter id read state mode
+
+
+
+\
+
+#### 2.10 2024/5/11： 更新至finder1.3后，Ringtone配置页面需要配置GFPS find dult（Harman案子比较特殊，分为两个响铃：GFPS find dult tone和GFPS find dult vp， 其他案子一般就一个）
+
+
+
+
+
+\
+
+#### 2.11 如果需要关机之后依然打finder广播需要配置以下信息：
+
+详细信息可以参考mcu cfg tool中 GFPS 各配置项的含义 - BT_Market - WIKI 中的: ”9. GFPS Finder相关配置信息描述”
+
+
+
+\
+
+\
diff --git a/5.2.2+手机端环境搭建.md b/5.2.2+手机端环境搭建.md
new file mode 100644
index 0000000..b6afe29
--- /dev/null
+++ b/5.2.2+手机端环境搭建.md
@@ -0,0 +1,254 @@
+# 5.2.2 手机端环境搭建
+
+
+
+
+
+- [GFPS 环境搭建](#id-5.2.2手机端环境搭建-GFPS环境搭建)
+ - [1.手机需要连接google网络](#id-5.2.2手机端环境搭建-1.手机需要连接google网络)
+ - [2.手机不可以打开勿扰模式，不然可能看不到弹窗](#id-5.2.2手机端环境搭建-2.手机不可以打开勿扰模式，不然可能看不到弹窗)
+ - [3.检查手机是否打开Google Play服务通知](#id-5.2.2手机端环境搭建-3.检查手机是否打开GooglePlay服务通知)
+ - [4.检查google play 服务是否更新到最新的版本](#id-5.2.2手机端环境搭建-4.检查googleplay服务是否更新到最新的版本)
+ - [5.登陆google账号](#id-5.2.2手机端环境搭建-5.登陆google账号)
+ - [6 打开自动同步数据功能](#id-5.2.2手机端环境搭建-6打开自动同步数据功能)
+ - [7.检查Show notification是否打开：](#id-5.2.2手机端环境搭建-7.检查Shownotification是否打开：)
+ - [8.Setting界面打开蓝牙，以及位置信息。](#id-5.2.2手机端环境搭建-8.Setting界面打开蓝牙，以及位置信息。)
+ - [9.Enable debug mode ID：](#id-5.2.2手机端环境搭建-9.EnabledebugmodeID：)
+ - [10.Check Google Play Service version](#id-5.2.2手机端环境搭建-10.CheckGooglePlayServiceversion)
+ - [11.注册成为google beta tester（内部测试账号已经注册过了，这一步不需要，如果是客户自己注册的Google账号，需要提醒客户check）](#id-5.2.2手机端环境搭建-11.注册成为googlebetatester（内部测试账号已经注册过了，这一步不需要，如果是客户自己注册的Google账号，需要提醒客户check）)
+- [Find hub 环境搭建](#id-5.2.2手机端环境搭建-Findhub环境搭建)
+ - [1. The Google Find Hub App must be installed and updated to the latest Beta version.](#id-5.2.2手机端环境搭建-1.TheGoogleFindHubAppmustbeinstalledandupdatedtothelatestBetaversion.)
+ - [1.1 如果没有安装：](#id-5.2.2手机端环境搭建-1.1如果没有安装：)
+ - [1.2 如果已经安装：](#id-5.2.2手机端环境搭建-1.2如果已经安装：)
+ - [1.2.1 长按 Find hub 图标，会看到App info](#id-5.2.2手机端环境搭建-1.2.1长按Findhub图标，会看到Appinfo)
+ - [1.2.2 点击App info,会看到 App details](#id-5.2.2手机端环境搭建-1.2.2点击Appinfo,会看到Appdetails)
+ - [1.2.3 点击App details,会看到以下页面，如果有新版本请手动更新到最新的版本。如果是beta版本则不需要更新，系统会自动帮忙更新。](#id-5.2.2手机端环境搭建-1.2.3点击Appdetails,会看到以下页面，如果有新版本请手动更新到最新的版本。如果是beta版本则不需要更新，系统会自动帮忙更新。)
+ - [2."Use Find Hub" must be enabled under "Settings \> Google \> Find Hub".](#id-5.2.2手机端环境搭建-2.%22UseFindHub%22mustbeenabledunder%22Settings%3EGoogle%3EFindHub%22.)
+ - [3 "Find your offline devices" must be set to "With network in all areas" under "Settings \> Google \> Find Hub".](#id-5.2.2手机端环境搭建-3%22Findyourofflinedevices%22mustbesetto%22Withnetworkinallareas%22under%22Settings%3EGoogle%3EFindHub%22.)
+ - [4.“Scan for nearby devices” and “Include debug results” must be enabled under “Settings\> Google \> Devices and sharing \> Devices”.](#id-5.2.2手机端环境搭建-4.“Scanfornearbydevices”and“Includedebugresults”mustbeenabledunder“Settings%3EGoogle%3EDevicesandsharing%3EDevices”.)
+ - [5.Should be connected to the google Internet and have Bluetooth and Location turned on in Settings.](#id-5.2.2手机端环境搭建-5.ShouldbeconnectedtothegoogleInternetandhaveBluetoothandLocationturnedoninSettings.)
+ - [6 测试账号需要加入(内部测试账号已加入，qc测试不需要关心，FAE需要提醒客户自查)](#id-5.2.2手机端环境搭建-6测试账号需要加入(内部测试账号已加入，qc测试不需要关心，FAE需要提醒客户自查))
+ - [7 如果测试手机支援LEA, 开发者选项中将 Bypass Bluetooth LE Audio 选项关掉，然后重启手机](#id-5.2.2手机端环境搭建-7如果测试手机支援LEA,开发者选项中将BypassBluetoothLEAudio选项关掉，然后重启手机)
+
+
+
+\
+
+测试手机建议使用Google pixel手机， Pixel 5+ is recommended. 请**务必确保**手机端有打开开发者选项 https://developer.android.com/studio/debug/dev-options?hl=zh-cn
+
+### GFPS 环境搭建
+
+#### 1.手机需要连接google网络
+
+该网络必须可以登陆google的网站，在测试前请先测试一下是否可以登录google的网站(**建议试试能不能打开youtube之类的**）。
+
+#### 2.手机不可以打开勿扰模式，不然可能看不到弹窗
+
+
+
+#### 3.检查手机是否打开Google Play服务通知
+
+Setting-\>(Apps¬ification or Apps)应用和通知-\> See all apps -\>Google Play服务-\>通知-\>All Google Play services notifications, 开启(显示通知)
+
+
+
+\
+
+#### 4.检查google play 服务是否更新到最新的版本
+
+setting-\>(Apps¬ification or Apps)应用和通知-\>See all apps-\>Google Play 服务-\>高级-\>商店, 点击 App details or google play，界面会跳转到google play 商店，点击更新.
+
+如果已经成为 beta tester, google play service可能会自动更新到最新的。
+
+
+
+
+
+\
+
+#### 5.登陆google账号
+
+Settings\>Accounts or Seetings-\>Google(内部账号(不可给客户)：
+
+Fast Pair Validator 测试 请使用 realsilbt8888@gmail.com
+
+手动测试账号请参考 Google 账号 - BT_Market - WIKI (realtek.com)
+
+#### 6 打开自动同步数据功能
+
+由于GFPS的account key是存在google账号的云端的，所以必须要登陆google账号并且需要打开自动同步数据功能
+
+Settings\>Accounts ：
+
+
+
+or
+
+Seetings→Google:
+
+
+
+#### 7.检查Show notification是否打开：
+
+Settings\>Google\>(Devices & sharing)\>Devices(设置\>Google\>设备连接\>设备\>)
+
+pixel 2xl:
+
+
+
+pixel 7:
+
+
+
+\
+
+#### 8.Setting界面打开蓝牙，以及位置信息。
+
+\
+
+#### 9.Enable debug mode ID：
+
+The model ID provided to you is a debug mode ID. To enable it, go to Settings \> Google \> Devices & sharing \> Devices \> top right 3 dot menu to enable “Include debug results”.
+
+If the option “Include debug results” is missing in this page, please ensure Developer options in the phone is enabled.
+
+or go to Settings \> Google \> Devices & sharing \> Devices \>“Include debug results”
+
+Settings \> Google \> Devices & sharing \> Devices \> top right 3 dot menu to enable “Include debug results”
+
+
+
+or
+
+Settings \> Google \> Devices & sharing \> Devices \>“Include debug results”
+
+
+
+https://developer.android.com/studio/debug/dev-options?hl=zh-cn
+
+#### 10.Check Google Play Service version
+
+Purpose: To confirm we use right version of Fast Pair module for testing
+
+Go to Settings \> Apps¬ification or Apps\>google play services \> advanced, then check Google Play services version (It should be 20.XX.XX or higher).
+
+
+
+\
+
+\
+
+#### **11.注册成为google beta tester（内部测试账号已经注册过了，这一步不需要，如果是客户自己注册的Google账号，需要提醒客户check）**
+
+Sign up for the Google Play services beta program https://play.google.com/apps/testing/com.google.android.gms
+
+join the Android Beta group at https://www.google.com/android/beta to get latest update via OTA
+
+Finder/Find Hub testing program please Navigate to https://play.google.com/apps/testing/com.google.android.apps.adm
+
+\
+
+可以登陆Google账号之后在以下链接查看是否有添加成功：我的群组
+
+
+
+需要注意的是：
+
+
+
+如果没有权限添加，FAE需要联系YingTsung (YT) Lin， 请他发邮件给Google， 让Google把客户注册的Google账号添加到Google的Test group。
+
+### Find hub 环境搭建
+
+#### 1. The Google Find Hub App must be installed and updated to the latest Beta version.
+
+确认手机是否安装 Find Hub, 图标如下图：
+
+ 
+
+##### 1.1 如果没有安装：
+
+去 Play Store/应用商店 下载Find Hub并且安装。
+
+##### 1.2 如果已经安装：
+
+确认安装的是否是最新版。不是最新版，请手动升级到最新版。确认步骤如下：
+
+###### 1.2.1 长按 Find hub 图标，会看到App info
+
+
+
+###### 1.2.2 点击App info,会看到 App details
+
+
+
+###### 1.2.3 点击App details,会看到以下页面，如果有新版本请手动更新到最新的版本。如果是beta版本则不需要更新，系统会自动帮忙更新。
+
+
+
+\
+
+#### 2.*"Use Find Hub"* must be enabled under *"Settings \> Google \> Find Hub"*.
+
+
+
+
+
+or
+
+手机端打开 finder功能.mp4
+
+\
+
+#### *3 "Find your offline devices"* must be set to *"With network in all areas"* under *"Settings \> Google \> Find Hub"*.
+
+
+
+
+
+\
+
+\
+
+#### 4.“Scan for nearby devices” and “Include debug results” must be enabled under “Settings\> Google \> Devices and sharing \> Devices”.
+
+
+
+\
+
+#### 5.Should be connected to the google Internet and have Bluetooth and Location turned on in Settings.
+
+
+
+\
+
+#### **6 测试账号需要加入(内部测试账号已加入，qc测试不需要关心，FAE需要提醒客户自查)**
+
+Google Play services testing program： Navigate to https://play.google.com/apps/testing/com.google.android.gms
+
+Find My Device testing program： Navigate to https://play.google.com/apps/testing/com.google.android.apps.adm.
+
+如果没有权限，需要联系Google帮忙添加账号权限。
+
+\
+
+#### **7 如果测试手机支援LEA, 开发者选项中将 Bypass Bluetooth LE Audio 选项关掉，然后重启手机**
+
+****
+
+\
+
+\
+
+\
+
+\
+
+\
+
+\
diff --git a/5.2.3+Fast+Pair+Validator+环境搭建.md b/5.2.3+Fast+Pair+Validator+环境搭建.md
new file mode 100644
index 0000000..35b6778
--- /dev/null
+++ b/5.2.3+Fast+Pair+Validator+环境搭建.md
@@ -0,0 +1,326 @@
+# 5.2.3 Fast Pair Validator 环境搭建
+
+
+
+
+
+- [1 搭建手机端的测试环境](#id-5.2.3FastPairValidator环境搭建-1搭建手机端的测试环境)
+ - [1.1 手机需要连接google网络](#id-5.2.3FastPairValidator环境搭建-1.1手机需要连接google网络)
+ - [1.2 手机不可以打开勿扰模式，不然可能看不到弹窗](#id-5.2.3FastPairValidator环境搭建-1.2手机不可以打开勿扰模式，不然可能看不到弹窗)
+ - [1.3 检查手机是否打开Google Play服务通知](#id-5.2.3FastPairValidator环境搭建-1.3检查手机是否打开GooglePlay服务通知)
+ - [1.4 检查google play 服务是否更新到最新的版本](#id-5.2.3FastPairValidator环境搭建-1.4检查googleplay服务是否更新到最新的版本)
+ - [1.5 登陆google账号](#id-5.2.3FastPairValidator环境搭建-1.5登陆google账号)
+ - [1.6 打开自动同步数据功能](#id-5.2.3FastPairValidator环境搭建-1.6打开自动同步数据功能)
+ - [1.7 检查Show notification是否打开：](#id-5.2.3FastPairValidator环境搭建-1.7检查Shownotification是否打开：)
+ - [1.8 Setting界面打开蓝牙，以及位置信息。](#id-5.2.3FastPairValidator环境搭建-1.8Setting界面打开蓝牙，以及位置信息。)
+ - [1.9 Enable debug mode ID：](#id-5.2.3FastPairValidator环境搭建-1.9EnabledebugmodeID：)
+ - [1.10 Check Google Play Service version](#id-5.2.3FastPairValidator环境搭建-1.10CheckGooglePlayServiceversion)
+ - [1.11 注册成为google beta tester（内部测试账号已经注册过了，这一步不需要，如果是客户自己注册的Google账号，需要提醒客户check）](#id-5.2.3FastPairValidator环境搭建-1.11注册成为googlebetatester（内部测试账号已经注册过了，这一步不需要，如果是客户自己注册的Google账号，需要提醒客户check）)
+- [2 Fast Pair Validator APP安装](#id-5.2.3FastPairValidator环境搭建-2FastPairValidatorAPP安装)
+- [3 Enable fast pair validator app中的测项](#id-5.2.3FastPairValidator环境搭建-3Enablefastpairvalidatorapp中的测项)
+ - [3.1 安装adb:](#id-5.2.3FastPairValidator环境搭建-3.1安装adb:)
+ - [3.2 输入如下命令：](#id-5.2.3FastPairValidator环境搭建-3.2输入如下命令：)
+- [4 uninstall amazon 相关app](#id-5.2.3FastPairValidator环境搭建-4uninstallamazon相关app)
+- [5 测试账号和MODEL ID](#id-5.2.3FastPairValidator环境搭建-5测试账号和MODELID)
+- [6 测试准备](#id-5.2.3FastPairValidator环境搭建-6测试准备)
+- [7 Find hub 环境搭建:](#id-5.2.3FastPairValidator环境搭建-7Findhub环境搭建:)
+ - [1.认证实验室会重新跑 fast pair validator中finder相关的测项，所以送认证前最好提供各个测项的操作视频以及详细的操作步骤(如何开机，如何factory reset，如何进pairing mode..)](#id-5.2.3FastPairValidator环境搭建-1.认证实验室会重新跑fastpairvalidator中finder相关的测项，所以送认证前最好提供各个测项的操作视频以及详细的操作步骤(如何开机，如何factoryreset，如何进pairingmode..))
+ - [2.如果测试手机支援LEA, 开发者选项中将 Bypass Bluetooth LE Audio 选项关掉，然后重启手机](#id-5.2.3FastPairValidator环境搭建-2.如果测试手机支援LEA,开发者选项中将BypassBluetoothLEAudio选项关掉，然后重启手机)
+ - [3.一定要等所有的测项都测试PASS之后才可以提交测试结果](#id-5.2.3FastPairValidator环境搭建-3.一定要等所有的测项都测试PASS之后才可以提交测试结果)
+ - [4. Fast pair validator enable EDDYSTONE：](#id-5.2.3FastPairValidator环境搭建-4.FastpairvalidatorenableEDDYSTONE：)
+ - [1.打开fast pair validator, 登陆Google账号，找到和耳机对应的model id，点击model id之后会看到EDDYSTONE, 点击进行测试](#id-5.2.3FastPairValidator环境搭建-1.打开fastpairvalidator,登陆Google账号，找到和耳机对应的modelid，点击modelid之后会看到EDDYSTONE,点击进行测试)
+ - [2.如果看不到 EDDYSTONE， 需要 adb 执行以下两个commands:](#id-5.2.3FastPairValidator环境搭建-2.如果看不到EDDYSTONE，需要adb执行以下两个commands:)
+ - [3 For locator tags that don't create a bond during pairing, also run the following command:](#id-5.2.3FastPairValidator环境搭建-3Forlocatortagsthatdon'tcreateabondduringpairing,alsorunthefollowingcommand:)
+ - [3.然后选择EDDYSTONE 进行测试：](#id-5.2.3FastPairValidator环境搭建-3.然后选择EDDYSTONE进行测试：)
+ - [4.Finder Fast Pair Validator EDDYSTONE测试完成。测试结果提交：](#id-5.2.3FastPairValidator环境搭建-4.FinderFastPairValidatorEDDYSTONE测试完成。测试结果提交：)
+
+
+
+### 1 搭建手机端的测试环境
+
+测试手机建议使用Google pixel手机，请**务必确保**手机端有打开开发者选项 https://developer.android.com/studio/debug/dev-options?hl=zh-cn
+
+\
+
+#### 1.1 手机需要连接google网络
+
+该网络必须可以登陆google的网站，在测试前请先测试一下是否可以登录google的网站(**建议试试能不能打开youtube之类的**）。
+
+#### 1.2 手机不可以打开勿扰模式，不然可能看不到弹窗
+
+
+
+#### 1.3 检查手机是否打开Google Play服务通知
+
+Setting-\>(Apps¬ification or Apps)应用和通知-\> See all apps -\>Google Play服务-\>通知-\>All Google Play services notifications, 开启(显示通知)
+
+
+
+#### 1.4 检查google play 服务是否更新到最新的版本
+
+setting-\>(Apps¬ification or Apps)应用和通知-\>See all apps-\>Google Play 服务-\>高级-\>商店, 点击 App details or google play，界面会跳转到google play 商店，点击更新.
+
+如果已经成为 beta tester, google play service可能会自动更新到最新的。
+
+
+
+
+
+\
+
+#### 1.5 登陆google账号
+
+Settings\>Accounts or Seetings-\>Google(内部账号(不可给客户)：
+
+Fast Pair Validator 测试 请使用 realsilbt8888@gmail.com
+
+手动测试账号请参考 Google 账号 - BT_Market - WIKI (realtek.com)
+
+#### 1.6 打开自动同步数据功能
+
+由于GFPS的account key是存在google账号的云端的，所以必须要登陆google账号并且需要打开自动同步数据功能
+
+Settings\>Accounts ：
+
+
+
+or
+
+Seetings→Google:
+
+
+
+#### 1.7 检查Show notification是否打开：
+
+Settings\>Google\>(Devices & sharing)\>Devices(设置\>Google\>设备连接\>设备\>)
+
+pixel 2xl:
+
+
+
+pixel 7:
+
+
+
+\
+
+跑 Fast pair validator 测试之前关掉 Automatically save devices
+
+**Note: 只有realsilbt8888的账号需要关掉 Automatically save devices， 其他手动测试的账号Automatically save devices需要打开**
+
+
+
+\
+
+#### 1.8 Setting界面打开蓝牙，以及位置信息。
+
+\
+
+#### 1.9 Enable debug mode ID：
+
+The model ID provided to you is a debug mode ID. To enable it, go to Settings \> Google \> Devices & sharing \> Devices \> top right 3 dot menu to enable “Include debug results”.
+
+If the option “Include debug results” is missing in this page, please ensure Developer options in the phone is enabled.
+
+or go to Settings \> Google \> Devices & sharing \> Devices \>“Include debug results”
+
+Settings \> Google \> Devices & sharing \> Devices \> top right 3 dot menu to enable “Include debug results”
+
+
+
+or
+
+Settings \> Google \> Devices & sharing \> Devices \>“Include debug results”
+
+
+
+https://developer.android.com/studio/debug/dev-options?hl=zh-cn
+
+#### 1.10 Check Google Play Service version
+
+Purpose: To confirm we use right version of Fast Pair module for testing
+
+Go to Settings \> Apps¬ification or Apps\>google play services \> advanced, then check Google Play services version (It should be 20.XX.XX or higher).
+
+
+
+\
+
+\
+
+#### **1.11 注册成为google beta tester（内部测试账号已经注册过了，这一步不需要，如果是客户自己注册的Google账号，需要提醒客户check）**
+
+Sign up for the Google Play services beta program https://play.google.com/apps/testing/com.google.android.gms
+
+join the Android Beta group at https://www.google.com/android/beta to get latest update via OTA
+
+Finder/Find Hub testing program please Navigate to https://play.google.com/apps/testing/com.google.android.apps.adm
+
+\
+
+可以登陆Google账号之后在以下链接查看是否有添加成功：我的群组
+
+
+
+需要注意的是：
+
+
+
+如果没有权限添加，FAE需要联系YingTsung (YT) Lin， 请他发邮件给Google， 让Google把客户注册的Google账号添加到Google的Test group。
+
+### **2 Fast Pair Validator APP安装**
+
+确认手机是否安装 Fast Pair Validator APP
+
+Fast pair validator app 图标如下图：
+
+
+
+如果没有安装:
+
+去 Play Store/应用商店 下载 Fast Pair Validator APP并且安装。
+
+如果已经安装:
+
+确认安装的是否是最新版。不是最新版，请手动升级到最新版。确认步骤如下：
+
+长按 Fast Pair Validator 图标，会看到App info
+
+
+
+点击App info,会看到App details
+
+
+
+点击App details,会看到以下页面，如果有新版本请手动更新到最新的版本。如果是beta版本则不需要更新，系统会自动帮忙更新。
+
+
+
+### 3 Enable fast pair validator app中的测项
+
+#### 3.1 安装adb:
+
+adb安装及使用方法 该wiki上提供的adb版本太旧，会出现device offline的问题，下载最新的https://adbshell.com/downloads
+
+安装adb之后找到adb.exe所在的目录，在该目录下打开cmd命令行
+
+#### 3.2 输入如下命令：
+
+adb shell am broadcast -a com.google.location.nearby.apps.fastpair.validator.FLAG_OVERRIDE --es flag enable_features_for_v3 --es value true --es type boolean com.google.location.nearby.apps.fastpair.validator
+
+
+
+按enter执行命令。
+
+命令执行成功之后，
+
+打开fast pair validator 能看到新的feature
+
+\
+
+### 4 uninstall amazon 相关app
+
+Alexa (com.amazon.dee.app) 和com.amazon.wellness app， 会影响到Validator的测试，需要Uninstall。
+
+The Alexa (com.amazon.dee.app) took too much time on handling the ACL_CONNECTED intent, which impacts the Validator's flow.
+
+There is still another **app,com.amazon.wellness** app, who handled ACL_CONNECTED for 20+ seconds.Please uninstall it as well.
+
+现象： End-to-end integration测试，出现Pairing timeout
+
+操作方式：
+
+adb uninstall com.amazon.wellness
+
+adb uninstall com.amazon.dee.app
+
+\
+
+### 5 测试账号和MODEL ID
+
+使用Fast Pair Validator测试，需要先登陆Google账号，测试设备使用的Model ID,public key, private key 必须是该google账号注册的Device。
+
+场内测试账号：realsilbt8888@gmail.com
+
+**Note：**
+
+fast pair validator app使用的model id 要和DUT开发板配置的model id一致。
+
+
+
+### **6 测试准备**
+
+测试过程中需要注意
+
+手机端弹出配对提示框时不要手动点击，fast pair validator app会自己触发配对.
+
+开始测试前，需要确认是否已经和待测试耳机配对过，需要删除配对信息。 最后最好在开始测试前，开关一下飞行模式。
+
+点击GOT IT开始测试时，耳机端一定要处于Pairable mode，否则会scan不到设备, scan 到设备后，点击Test开始测试。
+
+
+
+### 7 Find hub 环境搭建:
+
+#### **1.认证实验室会重新跑 fast pair validator中finder相关的测项，所以送认证前最好提供各个测项的操作视频以及详细的操作步骤(如何开机，如何factory reset，如何进pairing mode..)**
+
+#### **2.如果测试手机支援LEA, 开发者选项中将 Bypass Bluetooth LE Audio 选项关掉，然后重启手机**
+
+****
+
+#### **3.一定要等所有的测项都测试PASS之后才可以提交测试结果**
+
+如果存在Fail的测项，不可以提交测试结果！！！
+
+如果存在Fail的测项，不可以提交测试结果！！！
+
+如果存在Fail的测项，不可以提交测试结果！！！
+
+#### 4. Fast pair validator enable EDDYSTONE：
+
+##### 1.打开fast pair validator, 登陆Google账号，找到和耳机对应的model id，点击model id之后会看到EDDYSTONE, 点击进行测试
+
+##### 2.如果看不到 EDDYSTONE， 需要 adb 执行以下两个commands:
+
+cmd1:
+
+adb shell am broadcast -a com.google.location.nearby.apps.fastpair.validator.FLAG_OVERRIDE --es flag enable_qa_input_for_fast_pair --es value true --es type boolean com.google.location.nearby.apps.fastpair.validator
+
+cmd2：
+
+adb shell am broadcast -a com.google.location.nearby.apps.fastpair.validator.FLAG_OVERRIDE --es flag enable_spot_tests --es value true --es type boolean com.google.location.nearby.apps.fastpair.validator
+
+log信息如下：
+
+
+
+\
+
+##### 3 For locator tags that don't create a bond during pairing, also run the following command:
+
+cmd3：
+
+```
+adb shell am broadcast -a com.google.location.nearby.apps.fastpair.validator.FLAG_OVERRIDE --es flag skip_bonding_for_spot_locator_tags --es value true --es type boolean com.google.location.nearby.apps.fastpair.validator
+```
+
+##### 3.然后选择EDDYSTONE 进行测试：
+
+
+
+
+
+##### 4.Finder Fast Pair Validator EDDYSTONE测试完成。测试结果提交：\
+ \
+
+
+测试jira:
+
+ BTQCSZ-6106 - Getting issue details... STATUS
+
+\
diff --git a/5.3+测试.md b/5.3+测试.md
new file mode 100644
index 0000000..2ef9e21
--- /dev/null
+++ b/5.3+测试.md
@@ -0,0 +1,7 @@
+# 5.3 测试
+
+测试完成之后要填写测试报告, 测试报告从以下位置获取：
+
+Test Case of the Third Party - BT Test - WIKI
+
+
diff --git a/5.3.1+Fast+Pair+Validator+测试.md b/5.3.1+Fast+Pair+Validator+测试.md
new file mode 100644
index 0000000..ac7c71e
--- /dev/null
+++ b/5.3.1+Fast+Pair+Validator+测试.md
@@ -0,0 +1,17 @@
+# 5.3.1 Fast Pair Validator 测试
+
+5.3.1.2 EDDYSTONE
+
+** 这个必须要保证可以PASS，因为认证实验室会使用Fast Pair Validator 测试Finder相关的测项**
+
+\
+
+5.3.1.1 FAST PAIR
+
+ 这个测项客户自测并且提交测试结果到Google云端，认证实验室暂时不会测试。
+
+目前来看只要有一次测试成功，并且有提交成功的测试结果到Google云端就可以，即使偶尔失败了，如果确定不是我们设备端的bug, 也没关系的
+
+https://partnerissuetracker.corp.google.com/u/0/issues/473688165
+
+
diff --git a/5.3.1.1+FAST+PAIR.md b/5.3.1.1+FAST+PAIR.md
new file mode 100644
index 0000000..5b41d7c
--- /dev/null
+++ b/5.3.1.1+FAST+PAIR.md
@@ -0,0 +1,110 @@
+# 5.3.1.1 FAST PAIR
+
+
+
+
+
+- [只需要测试以下几个测项：](#id-5.3.1.1FASTPAIR-只需要测试以下几个测项：)
+- [测试准备](#id-5.3.1.1FASTPAIR-测试准备)
+ - [打开Fast Pair Validator app](#id-5.3.1.1FASTPAIR-打开FastPairValidatorapp)
+ - [通过model id找到待测试设备](#id-5.3.1.1FASTPAIR-通过modelid找到待测试设备)
+ - [选择FAST PAIR进行测试](#id-5.3.1.1FASTPAIR-选择FASTPAIR进行测试)
+ - [不要Enable LE spec test](#id-5.3.1.1FASTPAIR-不要EnableLEspectest)
+- [Calibration 测试](#id-5.3.1.1FASTPAIR-Calibration测试)
+- [Distance 0.3 Meter 测试](#id-5.3.1.1FASTPAIR-Distance0.3Meter测试)
+
+[](#id-5.3.1.1FASTPAIR-)
+
+- [Distance 1.2 Meter 测试](#id-5.3.1.1FASTPAIR-Distance1.2Meter测试)
+- [Distance 2 Meter 测试](#id-5.3.1.1FASTPAIR-Distance2Meter测试)
+
+
+
+#### 只需要测试以下几个测项：
+
+
+
+#### 测试准备
+
+##### 打开Fast Pair Validator app
+
+
+
+##### 通过model id找到待测试设备
+
+
+
+##### 选择FAST PAIR进行测试
+
+
+
+##### 不要Enable LE spec test
+
+
+
+#### Calibration 测试
+
+Note:
+
+calibration 测试， discoverable adv interval需要足够小，spec 规定 discoverable mode adv \<= 100ms，mcu cfg tool目前设为32(20 ms) 可以测试通过。
+
+开机legacy进pairing mode后，按键key1进入GFPS LEA 配对模式，按app提示将手机放置离耳机 1m、3m、0.3m米处，等待测试完成。
+
+Note:
+
+GFPS 弹窗出来之后请**不要**点击弹窗！！！
+
+如果1m测项测试失败，Fast pair validator可以协助我们手动调整tx power值:
+
+
+
+\
+
+#### Distance 0.3 Meter 测试
+
+耳机开机，按键key1进入GFPS LEA配对模式，然后开始测试，等待测试完成。
+
+Note:
+
+GFPS 弹窗出来之后不要点；
+
+如果该测项测不过，MCU cfg tool Thirdparty 页面需要适当减小tx power(比如从-10，减小到-12)；并重新跑 "**Calibration 测试"** 以及该测项
+
+\
+
+### 
+
+\
+
+#### Distance 1.2 Meter 测试
+
+耳机开机，按键key1进入GFPS LEA配对模式，然后开始测试，等待测试完成。
+
+Note:
+
+GFPS 弹窗出来之后不要点；
+
+如果该测项测不过，MCU cfg tool Thirdparty 页面需要适当增大tx power(比如从-12增大到-10）；并重新跑 "**Calibration 测试"** 以及该测项
+
+\
+
+\
+
+#### Distance 2 Meter 测试
+
+耳机开机，按键key1进入GFPS LEA配对模式，然后开始测试，等待测试完成。
+
+Note:
+
+GFPS 弹窗出来之后不要点；
+
+如果该测项测不过，MCU cfg tool Thirdparty 页面需要适当增大tx power(比如从-12增大到-10）；并重新跑 "**Calibration 测试"** 以及该测项
+
+
+
+\
diff --git a/5.3.1.2+EDDYSTONE.md b/5.3.1.2+EDDYSTONE.md
new file mode 100644
index 0000000..00a2549
--- /dev/null
+++ b/5.3.1.2+EDDYSTONE.md
@@ -0,0 +1,5 @@
+# 5.3.1.2 EDDYSTONE
+
+请参考以下Wiki中的测项进行测试 2 Fast Pair validator Finder 测试 - BT_Market - WIKI
+
+
diff --git a/5.3.2+手动测试.md b/5.3.2+手动测试.md
new file mode 100644
index 0000000..90b6c66
--- /dev/null
+++ b/5.3.2+手动测试.md
@@ -0,0 +1 @@
+# 5.3.2 手动测试
diff --git a/5.3.2.1+Notification+dialog+for+initial+pairing.md b/5.3.2.1+Notification+dialog+for+initial+pairing.md
new file mode 100644
index 0000000..7462c85
--- /dev/null
+++ b/5.3.2.1+Notification+dialog+for+initial+pairing.md
@@ -0,0 +1,15 @@
+# 5.3.2.1 Notification dialog for initial pairing
+
+耳机做factory reset，手机setting界面清掉所有的蓝牙配对信息。
+
+耳机 和 手机放置距离小于0.3m
+
+耳机进入pairing mode，听到pairing mode提示音后 开始计时
+
+手机弹窗出现，停止计时，
+
+记录从听到pairing mode提示音到手机弹窗出现所需的时间，这个时间就是excel 中的 Notification Pop-up time。
+
+从听到pairing mode提示音 到 手机弹窗出现时间应该小于5s
+
+
diff --git a/5.3.2.2+Certification+specification+for+distance.md b/5.3.2.2+Certification+specification+for+distance.md
new file mode 100644
index 0000000..ccc3e8f
--- /dev/null
+++ b/5.3.2.2+Certification+specification+for+distance.md
@@ -0,0 +1,60 @@
+# 5.3.2.2 Certification specification for distance
+
+At least 80% of all reference phones must meet the criteria of this section when tested at the 3 proscribed distances (0.3 meters, 1.2 meters, and 2 meters).
+
+- The success rate at 0.3 meters must be 100%. In other words, each reference phone must run the 0.3 meters test 10 times and show every notification.
+- The pairing notification appearance rate sent to reference phones at 1.2 meters must be less than or equal to 20% in 10 times.
+- Each test performed at a 2 meter distance must never cause a notification to appear on the reference phones for at least 1 minute.
+- Each distance will be tested 10 times for each reference phone.
+
+\
+
+\
+
+#### test case 4：距离测试
+
+耳机做factory reset，手机X setting界面清掉所有的蓝牙配对信息。
+
+**手机X 和耳机距离0.3m, **
+
+1 耳机开机进入pairing mode，听到pairing mode提示音后 开始计时
+
+2 手机X 弹窗出现，停止计时
+
+3 从耳机进入pairing mode 到 手机X 弹窗出现时间小于5s, 认为测试成功，记录弹窗出现的时间。
+
+4 耳机关机，等待手机端弹窗自动消失之后，再次从步骤1开始执行下一轮测试
+
+循环测试10次，10次必须**全部弹窗**。
+
+\
+
+**手机和耳机距离1.2m, **
+
+耳机做factory reset，手机X setting界面清掉所有的蓝牙配对信息。
+
+手机X 和耳机距离1.2m,
+
+1 耳机开机进入pairing mode，听到pairing mode提示音后 开始计时
+
+2 1min 之后弹窗仍不出现，认为测试成功，如果1 min之内有弹窗出现，认为测试失败
+
+循环测试10次，10次最多允许有**两次弹窗**。
+
+\
+
+**手机和耳机距离2m,**
+
+耳机做factory reset，手机X setting界面清掉所有的蓝牙配对信息。
+
+手机X 和耳机距离 2m,
+
+1 耳机开机进入pairing mode，听到pairing mode提示音后 开始计时
+
+2 1min 之后弹窗仍不出现，认为测试成功，如果1 min之内有弹窗出现，认为测试失败
+
+循环测试10次，10次必须全部**不弹窗**。
+
+填写excel，Y是指弹窗出现， N是指弹窗不出现。
+
+
diff --git a/5.3.2.3+find+hub.md b/5.3.2.3+find+hub.md
new file mode 100644
index 0000000..89852ef
--- /dev/null
+++ b/5.3.2.3+find+hub.md
@@ -0,0 +1,5 @@
+# 5.3.2.3 find hub
+
+请参考以下Wiki 中的test case 进行测试 1 Finder-手机"Find My Device"APP测试-v1.3 - BT_Market - WIKI
+
+
diff --git a/5手机提示+_无法连接，请转到设置尝试手动与该设备配对_.md b/5手机提示+_无法连接，请转到设置尝试手动与该设备配对_.md
new file mode 100644
index 0000000..3c6e52a
--- /dev/null
+++ b/5手机提示+_无法连接，请转到设置尝试手动与该设备配对_.md
@@ -0,0 +1,17 @@
+# 5手机提示 "无法连接，请转到设置尝试手动与该设备配对"
+
+
+
+\
+
+1 可以先换个Google账号再试试看，有的Google账号连的设备太多好像就会有问题
+
+2 可以尝试按提示信息，转到设置界面手动进行配对，看是否配对成功。如果可以配对成功，应该是每次做完initial pairing之后，手机没有清除配对信息，也没有开关一下飞行模式，导致手机蓝牙状态没有恢复，此时可以重启一下手机再试试看
+
+3 如果setting界面也配对失败，需要抓log 看一下耳机是否处于pairing mode，并且分析一下BREDR配对失败的原因。 BBPRO3BUG-362 - \[BBPRO3\]\[EVB\]\[release_1220\]\[GFPS\]RWS与Google Pixel配对失败，提示无法连接 In Progress
+
+\
+
+如果依然有问题，麻烦帮忙抓手机log，耳机log 和失败截图
+
+\
diff --git a/6+Provisioning+for+non-owner+test+fail.md b/6+Provisioning+for+non-owner+test+fail.md
new file mode 100644
index 0000000..2cf9501
--- /dev/null
+++ b/6+Provisioning+for+non-owner+test+fail.md
@@ -0,0 +1,31 @@
+# 6 Provisioning for non-owner test fail
+
+
+
+这边提示说是耳机设备不正确的上报：account key is owner account key
+
+原因是这个测项想要测试非owner手机 provisioning 耳机对应的行为。
+
+第一次手机A和耳机配对成功之后，耳机会存储手机A的地址，并将这个地址和account key进行绑定，认为这个手机是耳机的owner。
+
+手机A清掉配对信息之后，耳机端没有清配对信息，手机A再次和耳机配对，耳机一看有存储这个手机的地址，会直接更新account key, 认为手机A只是想更新 owner account key, 手机A还是耳机的owner.
+
+\
+
+但是从google 设计的这个测项来看，google会认为手机A再次配对耳机的时候，这个手机A就不再是耳机的owner了，所以我们要用一块新的区间来存储这个新的account key，并且认为这个account key是非owner account key.
+
+我觉得google 设计的这个测项好像有点问题~我有发邮件询问google，但是还没有得到答复。
+
+\
+
+我有针对这个测项进行修改code，code修改之后，如果手机端清掉配对信息之后，耳机端要同步做factory reset，不然finder功能就用不起来
+
+
+
+目前问题应该是如何界定owner device。后续会咨询google
+
+
+
+google 答复见 FAQ： [8 手机端清掉配对信息之后，耳机端也要做factory reset，不然finder功能用不起来](/pages/viewpage.action?pageId=350190807)
+
+ 
BTQCSZ-6106 - \[BB2\]\[C-CUT\]\[8763EF\]\[HARMAN\]\[Finder\]Harman T520 GFPS Finder测试 REVIEW
diff --git a/6+同一个手机搭配RTK耳机不会弹窗，搭配竞品耳机可以弹窗.md b/6+同一个手机搭配RTK耳机不会弹窗，搭配竞品耳机可以弹窗.md
new file mode 100644
index 0000000..0a4e9e6
--- /dev/null
+++ b/6+同一个手机搭配RTK耳机不会弹窗，搭配竞品耳机可以弹窗.md
@@ -0,0 +1,7 @@
+# 6 同一个手机搭配RTK耳机不会弹窗，搭配竞品耳机可以弹窗
+
+1.首先确认model id是不是在Google网站上成功注册的model id。[model_id 注册](/pages/viewpage.action?pageId=157379126)
+
+2.原因可能是用户注册的model id是debug model id 尚未通过Google认证，如果要使用这个model id 需要手机端enable以下这个功能：
+
+
diff --git a/6+弹窗功能测试时手机不弹窗.md b/6+弹窗功能测试时手机不弹窗.md
new file mode 100644
index 0000000..a8e9952
--- /dev/null
+++ b/6+弹窗功能测试时手机不弹窗.md
@@ -0,0 +1,17 @@
+# 6 弹窗功能测试时手机不弹窗
+
+测试步骤：
+
+1 耳机开机进pairing mode ，手机端弹窗出现，不点击弹窗
+
+2\. 耳机关机，等待手机端弹窗消失
+
+3.耳机再开机进pairing mode ，手机端弹窗出现，不点击弹窗
+
+重复 步骤2,3
+
+不弹窗原因：
+
+手机端弹窗出现时，不能手动划掉弹窗，而是耳机关机，手机端扫不到GFPS广播，弹窗会自动退出，弹窗自动退出之后，再次开机进Pairing mode时，每次就能正常弹窗
+
+ BB2BUG-5377 - \[BB2\]\[RTL8763EF/ROM\]\[GMI\]\[沃莱特\]\[Harman\]\[T520\]: google手机快速配对不弹窗的 Closed
diff --git a/6+用客户自己注册的model+id不弹窗，用rtk认证过的model+id就可以弹窗.md b/6+用客户自己注册的model+id不弹窗，用rtk认证过的model+id就可以弹窗.md
new file mode 100644
index 0000000..aad4792
--- /dev/null
+++ b/6+用客户自己注册的model+id不弹窗，用rtk认证过的model+id就可以弹窗.md
@@ -0,0 +1,5 @@
+# 6 用客户自己注册的model id不弹窗，用rtk认证过的model id就可以弹窗
+
+原因是用户注册的model id是debug model id 尚未通过认证，如果要使用这个model id 需要手机端enable这个功能
+
+
diff --git a/6.1++Device+not+found+by+AK.md b/6.1++Device+not+found+by+AK.md
new file mode 100644
index 0000000..5e92b9f
--- /dev/null
+++ b/6.1++Device+not+found+by+AK.md
@@ -0,0 +1,7 @@
+# 6.1 Device not found by AK
+
+**设备没有打non discoverable advertising**
+
+
+
+ BB2BUG-26243 - \[BB2\]\[C-CUT\]\[RTL8763EFL\]\[Harman\]\[T530\]\[v2.13.2.0\]\[Finder\]Provisioning for non owner fail Closed
diff --git a/7++cross_seeker_auto_subsequent_pairing_test_from_LEA_phone_to_LEA_phone+_+Receive+unexpected+profile+connection.md b/7++cross_seeker_auto_subsequent_pairing_test_from_LEA_phone_to_LEA_phone+_+Receive+unexpected+profile+connection.md
new file mode 100644
index 0000000..8a504a2
--- /dev/null
+++ b/7++cross_seeker_auto_subsequent_pairing_test_from_LEA_phone_to_LEA_phone+_+Receive+unexpected+profile+connection.md
@@ -0,0 +1,27 @@
+# 7 cross_seeker_auto_subsequent_pairing_test_from_LEA_phone_to_LEA_phone : Receive unexpected profile connection
+
+
+
+手机UI提示接收到不期望的profile 连线 A2dp, 是指这个测试不期望手机建立A2DP的连线，但是实际上手机却建立了A2DP的连线，** 怀疑是手机setting 界面没有开启 Bypass Bluetooth LE Audio Allowlist**
+
+如果开启Bypass Bluetooth LE Audio Allowlist，手机默认会连LEA， 如果不开启Bypass Bluetooth LE Audio Allowlist 手机默认会连 legacy profile
+
+
+
+\
+
+\
+
+手机UI显示 Wait 60000ms for the connection and UUID event if not yet received的时候手机端在等什么UUID：
+
+如果手机端开了Bypass Bluetooth LE Audio Allowlist ：
+
+
+
+如果手机端没有开启Bypass Bluetooth LE Audio Allowlist ：
+
+手机默认应该是会连legacy profile 110B or 1108 or 111E
+
+\
+
+[BB2ULTRA-255] [BB2 Ultra][Transceiver SDK][RTL8763GWS][Harman]Add GFPS in speaker - Jira
diff --git a/7+Cross+Seekers+Auto+Subsequent+Pairing+Test+from+LE+audio+phone+to+LE+audio+phone+測試fail：+Not+receive+UUID,+is+connected_+false.md b/7+Cross+Seekers+Auto+Subsequent+Pairing+Test+from+LE+audio+phone+to+LE+audio+phone+測試fail：+Not+receive+UUID,+is+connected_+false.md
new file mode 100644
index 0000000..5cda9b5
--- /dev/null
+++ b/7+Cross+Seekers+Auto+Subsequent+Pairing+Test+from+LE+audio+phone+to+LE+audio+phone+測試fail：+Not+receive+UUID,+is+connected_+false.md
@@ -0,0 +1,15 @@
+# 7 Cross Seekers Auto Subsequent Pairing Test from LE audio phone to LE audio phone 測試fail： Not receive UUID, is connected: false
+
+这个测项需要支援同时连两支手机
+
+[BB2BUG-52863] [BB2][8763EWM][Tiger][GFPS][fast pair validator][fast pair測項][LE Audio] test case 1：Cross Seekers Auto Subsequent Pairing Test from LE audio phone to LE audio phone 測試fail - Jira
+
+做subsequent pair的那支LEA的手机UI显示Wait 60000ms for the connection and UUID event if not yet received的时候，这个时候手机UI在check LEA的ACL 连线，以及leagcy的 ACL 连线有没有建立， 以及有没有收到 184E的UUID
+
+\
+
+
+
+\
+
+
diff --git a/7+cross_seeker_auto_subsequent_pairing_test_from_NonLEA_phone_to_LEA_phone+_++Not+receive+UUID+Is+connected+false.md b/7+cross_seeker_auto_subsequent_pairing_test_from_NonLEA_phone_to_LEA_phone+_++Not+receive+UUID+Is+connected+false.md
new file mode 100644
index 0000000..b086e0d
--- /dev/null
+++ b/7+cross_seeker_auto_subsequent_pairing_test_from_NonLEA_phone_to_LEA_phone+_++Not+receive+UUID+Is+connected+false.md
@@ -0,0 +1,17 @@
+# 7 cross_seeker_auto_subsequent_pairing_test_from_NonLEA_phone_to_LEA_phone : Not receive UUID Is connected false
+
+\
+
+
+
+\
+
+LEA phone 确保手机setting界面有开启 Bypass 功能 Bypass Bluetooth LE Audio Allowlist 开启或关闭，手机端默认连接的profile是不一样的 - BT_Market - WIKI
+
+provider 支援LEA，手机UI 显示 Wait 60000ms for the connection and UUID event if not yet received的时候 应该是在等 LEA ACL的连线 和leagcy ACL 的连线 以及 UUID 184E
+
+从error log 来看 Connection 和UUID 都没有等到
+
+\
+
+\
diff --git a/7+cross_seeker_auto_subsequent_pairing_test_from_NonLEA_phone_to_LEA_phone+_.md b/7+cross_seeker_auto_subsequent_pairing_test_from_NonLEA_phone_to_LEA_phone+_.md
new file mode 100644
index 0000000..9150dfa
--- /dev/null
+++ b/7+cross_seeker_auto_subsequent_pairing_test_from_NonLEA_phone_to_LEA_phone+_.md
@@ -0,0 +1,16 @@
+# 7 cross_seeker_auto_subsequent_pairing_test_from_NonLEA_phone_to_LEA_phone :
+
+TWS 耳机对应时间点在特别频繁的做roleswap，而且gfps配对的时候好像没有engage成功
+
+Line 42167: 0003328 12-12#15:00:48.358 150 0060803.823 \[APP\] !\*\*gfps_send_kbp_response_le: le_device_support 1, le_device_mode 1
+
+//这边b2b没有连线成功，所以就只送了主耳的地址\
+Line 42169: 0003330 12-12#15:00:48.358 152 0060810.701 \[APP\] !\*\*gfps_send_kbp_response_le: raw response 02 40 01 20 24 19 97 88 00 18 7F C8 99 9B 5B 04, encrypt response 0E EF 7D F4 BA 60 7B E9 73 3A C8 9A 20 63 73 DB
+
+
+
+\
+
+[BBPRO3BUG-27089] [BBPRO3][EVB][E Cut][PEGA_HA_v1.0.4_20251106][24110 testbin][GFPS][FastPair][LEA phone]Cross Seekers Auto Subsequent Test from non LE audio phone to LE audio phone 测试fail（pairing process error & subsequent pair fail） - Jira
+
+\
diff --git a/7+点击谷歌配对连接上手机后，还会弹出谷歌配对窗.md b/7+点击谷歌配对连接上手机后，还会弹出谷歌配对窗.md
new file mode 100644
index 0000000..bf0c4fc
--- /dev/null
+++ b/7+点击谷歌配对连接上手机后，还会弹出谷歌配对窗.md
@@ -0,0 +1,3 @@
+# 7 点击谷歌配对连接上手机后，还会弹出谷歌配对窗
+
+ BUMBEEBUG-8013 - \[BBlite\]\[8753BFJ\]\[凯力威\]\[QCY\]\[TW06\] v1.7.5.1BFJ2:点击谷歌配对连接上手机后，还会弹出谷歌配对窗 Closed
diff --git a/7.GFPS+msg+through+LE+L2cap+Channel+Fail.md b/7.GFPS+msg+through+LE+L2cap+Channel+Fail.md
new file mode 100644
index 0000000..5e83ed1
--- /dev/null
+++ b/7.GFPS+msg+through+LE+L2cap+Channel+Fail.md
@@ -0,0 +1 @@
+# 7.GFPS msg through LE L2cap Channel Fail
diff --git a/9+[GFPS]查找设备功能中，让设备响铃，但耳机端没有铃声.md b/9+[GFPS]查找设备功能中，让设备响铃，但耳机端没有铃声.md
new file mode 100644
index 0000000..3873129
--- /dev/null
+++ b/9+[GFPS]查找设备功能中，让设备响铃，但耳机端没有铃声.md
@@ -0,0 +1,9 @@
+# 9 \[GFPS\]查找设备功能中，让设备响铃，但耳机端没有铃声
+
+ BB2BUG-670 - \[BB2\]\[B-CUT\]\[8763EFL\]\[V3.9.1.1_4M\]\[GFPS\]查找设备功能中，让设备响铃，但耳机端没有铃声 Closed
+
+ 
BB2BUG-14226 - \[Harman\]\[Finder\]响铃无声 Closed
+
+需要参考wiki[1.GFPS 基本测试环境搭建](/pages/viewpage.action?pageId=131148812)配置GFPS findme ring tone
+
+\
diff --git a/9.1+“Error+while+scaning+by+EID_+Scan+timed+out”.md b/9.1+“Error+while+scaning+by+EID_+Scan+timed+out”.md
new file mode 100644
index 0000000..207e798
--- /dev/null
+++ b/9.1+“Error+while+scaning+by+EID_+Scan+timed+out”.md
@@ -0,0 +1,19 @@
+# 9.1 “Error while scaning by EID: Scan timed out”
+
+ BTQCSZ-6288 - \[BB2\]\[C-CUT\]\[8763EF\]\[HARMAN\]\[Finder\]Authentication of configuration operations fail Resolved
+
+
+
+owner account key: 04 A2 C1 68 11 9E 79 54 BB 54 3C B0 7E EE 2F 7B
+
+EIK: AB CC 34 CB A8 66 05 C3 91 32 FE 4A 7C 57 84 AD 8F CF 16 7F 09 EF B9 16 FF 46 01 E6 29 7B 65 64
+
+EID: 9C EA 5C 4D AB 3D 78 21 62 28 73 DE C6 D0 E4 EE 5F 1F DB 66
+
+hash flag: 180
+
+\
+
+Hi Danni,
+
+I believe this is caused by a known regression, supposed to be fixed in Fast pair Validator 3.0.544659229 released yesterday.
diff --git a/9.2+Invalid+authentication+not+rejected.md b/9.2+Invalid+authentication+not+rejected.md
new file mode 100644
index 0000000..9d53614
--- /dev/null
+++ b/9.2+Invalid+authentication+not+rejected.md
@@ -0,0 +1,5 @@
+# 9.2 Invalid authentication not rejected
+
+
+
+ BB2BUG-26461 - \[BB2\]\[C-CUT\]\[RTL8763EFL\]\[Harman\]\[T530\]\[v2.13.2.0\]\[Finder\]Authentication of configuration operations fail Closed
diff --git a/9.3+device+not+found+by+Account+key.md b/9.3+device+not+found+by+Account+key.md
new file mode 100644
index 0000000..ab06317
--- /dev/null
+++ b/9.3+device+not+found+by+Account+key.md
@@ -0,0 +1,7 @@
+# 9.3 device not found by Account key
+
+设备没有打non discoverable advertising
+
+
+
+ BB2BUG-26461 - \[BB2\]\[C-CUT\]\[RTL8763EFL\]\[Harman\]\[T530\]\[v2.13.2.0\]\[Finder\]Authentication of configuration operations fail Closed
diff --git a/9.通过GFPS弹窗配对之后，手机setting不显示LE+audio的button.md b/9.通过GFPS弹窗配对之后，手机setting不显示LE+audio的button.md
new file mode 100644
index 0000000..8fe0024
--- /dev/null
+++ b/9.通过GFPS弹窗配对之后，手机setting不显示LE+audio的button.md
@@ -0,0 +1,15 @@
+# 9.通过GFPS弹窗配对之后，手机setting不显示LE audio的button
+
+[BB2BUG-47528] [BB2][RTL8763ESH/ROM][GMI][沃莱特][Harman][T530] 166- some device do not display the LEA button - Jira
+
+原因是 mcu cfg tool中并未enable GFPS LE audio功能，
+
+GFPS 弹窗出来之后，点击弹窗是配对的legacy，并不是配对的LE audio,
+
+所以setting 界面看到的是A2dp/HFP的button 而不是LE audio的button
+
+
+
+\
+
+如果要想让setting界面显示LE audio的button，需要enable GFPS LE audio功能，如何enable GFPS LE audio请参考耳机环境配置 - BT_Market - WIKI
diff --git a/Advertise+Address+Verification+fail.md b/Advertise+Address+Verification+fail.md
new file mode 100644
index 0000000..30c1c12
--- /dev/null
+++ b/Advertise+Address+Verification+fail.md
@@ -0,0 +1,3 @@
+# Advertise Address Verification fail
+
+
diff --git a/Android+13+initial+pair+fail+手机不来连BREDR.md b/Android+13+initial+pair+fail+手机不来连BREDR.md
new file mode 100644
index 0000000..54a38e7
--- /dev/null
+++ b/Android+13+initial+pair+fail+手机不来连BREDR.md
@@ -0,0 +1,7 @@
+# Android 13 initial pair fail 手机不来连BREDR
+
+https://partnerissuetracker.corp.google.com/u/0/issues/471505212
+
+[BB2BUG-53488] [BB2][RTL8763ESH/ROM][GMI][沃莱特][Harman][T530]2423:[IOP] GFPS Fail when SASS verify - Jira
+
+
diff --git a/Auto+Subsequent+Pairing...+测试fail（fail+reason：creatbond+failed，multiple+components）.md b/Auto+Subsequent+Pairing...+测试fail（fail+reason：creatbond+failed，multiple+components）.md
new file mode 100644
index 0000000..13e485a
--- /dev/null
+++ b/Auto+Subsequent+Pairing...+测试fail（fail+reason：creatbond+failed，multiple+components）.md
@@ -0,0 +1,3 @@
+# Auto Subsequent Pairing... 测试fail（fail reason：creatbond failed，multiple components）
+
+[BBPRO3BUG-27030] [BBPRO3][EVB][E Cut][PEGA_HA_v1.0.4_20251106][24110 testbin][GFPS][FastPair][LEA phone]Auto Subsequent Pairing... 测试fail（fail reason：creatbond failed，multiple components） - Jira
diff --git a/BLE+advertisements+don't+contain+Fast+Pair+account+key+while+not+in+pairing+mode.md b/BLE+advertisements+don't+contain+Fast+Pair+account+key+while+not+in+pairing+mode.md
new file mode 100644
index 0000000..64d4fb4
--- /dev/null
+++ b/BLE+advertisements+don't+contain+Fast+Pair+account+key+while+not+in+pairing+mode.md
@@ -0,0 +1,17 @@
+# BLE advertisements don't contain Fast Pair account key while not in pairing mode
+
+[BBPRO3BUG-27031] [BBPRO3][EVB][E Cut][PEGA_HA_v1.0.4_20251106][24110 testbin][GFPS][FastPair][LEA phone]Auto Subsequent Pairing... 测试fail（BLE advertisements don't contain fast pair account key while not in pairing mode） - Jira
+
+
+
+
+
+\
+
+bugreport-caiman_beta-BP41.250916.015.A1-2025-12-17-13-24-33.zip
+
+https://partnerissuetracker.corp.google.com/u/0/issues/469586772
+
+[BBPRO3BUG-27189] [GFPS][FastPair][LEA phone]BLE advertisements don't contain Fast Pair account key while not in pairing mode - Jira
+
+\
diff --git a/Bypass+Bluetooth+LE+Audio+Allowlist+开启或关闭，手机端默认连接的profile是不一样的.md b/Bypass+Bluetooth+LE+Audio+Allowlist+开启或关闭，手机端默认连接的profile是不一样的.md
new file mode 100644
index 0000000..c275730
--- /dev/null
+++ b/Bypass+Bluetooth+LE+Audio+Allowlist+开启或关闭，手机端默认连接的profile是不一样的.md
@@ -0,0 +1,7 @@
+# Bypass Bluetooth LE Audio Allowlist 开启或关闭，手机端默认连接的profile是不一样的
+
+如果开启Bypass Bluetooth LE Audio Allowlist，手机默认会连LEA，
+
+如果不开启Bypass Bluetooth LE Audio Allowlist 手机默认会连 legacy profile
+
+
diff --git a/Could+not+connect+to+......md b/Could+not+connect+to+......md
new file mode 100644
index 0000000..f763556
--- /dev/null
+++ b/Could+not+connect+to+......md
@@ -0,0 +1,9 @@
+# Could not connect to .....
+
+需要确认设备在这个时间段是不是没有打 non discoverable 广播
+
+
+
+ BB2BUG-26243 - \[BB2\]\[C-CUT\]\[RTL8763EFL\]\[Harman\]\[T530\]\[v2.13.2.0\]\[Finder\]Provisioning for non owner fail Closed
+
+\
diff --git a/Cross+Seekers+Auto+Subsequent+Test+Fail.md b/Cross+Seekers+Auto+Subsequent+Test+Fail.md
new file mode 100644
index 0000000..0f7db84
--- /dev/null
+++ b/Cross+Seekers+Auto+Subsequent+Test+Fail.md
@@ -0,0 +1,9 @@
+# Cross Seekers Auto Subsequent Test Fail
+
+这个测项要支援同时连两支手机
+
+[BBPRO3BUG-25181] [BBPRO3][EVB][E Cut][3.15.0.6+TestBin]Fast pair Validator APP测试，Cross Seekers Auto Subsequent Test Fail - Jira
+
+\
+
+
diff --git a/Device(XXXXXX)+not+found.md b/Device(XXXXXX)+not+found.md
new file mode 100644
index 0000000..645c589
--- /dev/null
+++ b/Device(XXXXXX)+not+found.md
@@ -0,0 +1,9 @@
+# Device(XXXXXX) not found
+
++not+found_b982d525.jpg)
+
+\
+
+1.先重启手机试试看，有时候手机端蓝牙状态会有问题，导致扫不到广播
+
+2.重启手机依然失败，查看设备端的log， 设备是否处于Pairing mode，以及GFPS adv data 里面有没有包含model id信息
diff --git a/EID+rotated+but+MAC+address+did+not.md b/EID+rotated+but+MAC+address+did+not.md
new file mode 100644
index 0000000..030ff71
--- /dev/null
+++ b/EID+rotated+but+MAC+address+did+not.md
@@ -0,0 +1,7 @@
+# EID rotated but MAC address did not
+
+
+
+\
+
+[BB2ULTRA-866] [B-CUT][RTL87X3G_MCU_SDK_Common_Zephyr_v1.0.0.3_20251210][TestBin]gfps finder，EDDYSTONE -> Advertisement rotation测试fail - Jira
diff --git a/End-to-end_+'ble+advertisement+doesn't+contain+fast+pair+account+key'.md b/End-to-end_+'ble+advertisement+doesn't+contain+fast+pair+account+key'.md
new file mode 100644
index 0000000..71dbcbd
--- /dev/null
+++ b/End-to-end_+'ble+advertisement+doesn't+contain+fast+pair+account+key'.md
@@ -0,0 +1,9 @@
+# End-to-end: 'ble advertisement doesn't contain fast pair account key'
+
+
+
+测试该测项的时候，手机清除配对信息(unpair device)，DUT断线需要进入non discoverable mode,
+
+参考如下wiki配置cfg tool:
+
+[fast pair validator 测试-Legacy Flow](/pages/viewpage.action?pageId=145776737)
diff --git a/End-to-end__Pairing++failed[state+error]_.md b/End-to-end__Pairing++failed[state+error]_.md
new file mode 100644
index 0000000..80f4ebe
--- /dev/null
+++ b/End-to-end__Pairing++failed[state+error]_.md
@@ -0,0 +1,12 @@
+# End-to-end:"Pairing failed\[state error\]"
+
+bugreport-cheetah_beta-U1B1.230908.003-2023-09-21-16-44-03.zip
+
+hi tony:\
+End to end test fail\
+success ration:3/5\
+can you help see the reason?
+
+\
+
+\
diff --git a/End-to-end__Pairing+failed_.md b/End-to-end__Pairing+failed_.md
new file mode 100644
index 0000000..e5bb2ec
--- /dev/null
+++ b/End-to-end__Pairing+failed_.md
@@ -0,0 +1,21 @@
+# End-to-end:"Pairing failed"
+
+提示Pairing failed!
+
+
+
+出现该问题抓取log，并且记录一下：
+
+耳机进pairing mode 的时间点，手机界面上提示"2.Pair device" 的时间点，以及手机界面提示"Pairing Failed"的时间点
+
+log分析：
+
+首先查看耳机是否处于pairing mode，
+
+如果耳机在pairing mode 但是手机还是提示pairing fail，
+
+查下log看手机是否有来建BREDR ACL Link，
+
+如果手机没来建BREDR ACL Link，那可能是手机端自己的原因
+
+如果手机端有来建BREDR ACL Link，再进一步分析 配对失败的原因
diff --git a/F1+GFPS+Legacy+FAQ.md b/F1+GFPS+Legacy+FAQ.md
new file mode 100644
index 0000000..1d88838
--- /dev/null
+++ b/F1+GFPS+Legacy+FAQ.md
@@ -0,0 +1 @@
+# F1 GFPS Legacy FAQ
diff --git a/FF_+Find+my+device+app界面电量不显示.md b/FF_+Find+my+device+app界面电量不显示.md
new file mode 100644
index 0000000..570d5f0
--- /dev/null
+++ b/FF_+Find+my+device+app界面电量不显示.md
@@ -0,0 +1,48 @@
+# FF: Find my device app界面电量不显示
+
+[BB2BUG-47595] [BB2][RTL8763EF/ROM][GMI][沃莱特][Harman][T520]: Finder电量不显示或者显示错误 - Jira
+
+[BB2BUG-47581] [BB2][D-CUT][8763EKH][Harman][T530]耳机开机连接手机添加至查找设备APP，APP中无电量显示 - Jira
+
+**只有 Low battery level 和 critical low battery level 才会显示电量信息，提示用户充电**
+
+**可以查看以下位置battery信息是否正确：**
+
+
+
+\
+
+
+
+\
+
+如果battery status设置的是11，手机 Find my device app依然不显示电量
+
+\
+
+
+
+可以查看以下位置battery信息是否正确：
+
+
+
+\
+
+ hash input = 0x00000XXX;
+
+bit\[0\]: 代表是否active UTP mode, 1 active, 0 deactive;
+
+bit\[2\]bit\[1\]: 两个bit 代表电池电量，00 表示不支持， 01表示normal 电量， 10表示low， 11表示非常低
+
+\
+
+for example：
+
+ 0087217 04-09#08:59:02.349 032 0030125.076 \[APP\] !\*\*app_gfps_finder_generate_hash_flag: sha256 input 59 87 C6 9B DE CA 24 B6 0E C6 25 A3 4F B1 2C 38 12 88 AB 78, sha256 output B4 44 54 B9 FB 69 1E 7A 53 2E 8D 71 F0 F4 9D 3B 13 6C 47 B7 B0 C4 24 40 67 F4 55 FC CA F1 A1 17, hash input 0x6, hash result 0x11\
+ 0087218 04-09#08:59:02.349 033 0030125.142 \[BTM\] !\*\*ble_ext_adv_mgr_set_adv_data: adv_handle 2
+
+\
+
+ hash input 0x6： bit\[0\]是0 表示deactive UTP mode; Bit\[2\]bit\[1\]是11 表示电量非常低
+
+\
diff --git a/FF_+有时候显示“Near+you+right+now”,有时候显示“last+seen+near+you+just+now”.md b/FF_+有时候显示“Near+you+right+now”,有时候显示“last+seen+near+you+just+now”.md
new file mode 100644
index 0000000..3f248de
--- /dev/null
+++ b/FF_+有时候显示“Near+you+right+now”,有时候显示“last+seen+near+you+just+now”.md
@@ -0,0 +1,5 @@
+# FF: 有时候显示“Near you right now”,有时候显示“last seen near you just now”
+
+google的答复“Near you right now” 和“last seen near you just now”其实是一样的意思，没什么区别
+
+
diff --git a/Fail+Reason_+Firmware+version+should+not+be+readable.md b/Fail+Reason_+Firmware+version+should+not+be+readable.md
new file mode 100644
index 0000000..32d3bcc
--- /dev/null
+++ b/Fail+Reason_+Firmware+version+should+not+be+readable.md
@@ -0,0 +1,7 @@
+# Fail Reason: Firmware version should not be readable
+
+\
+
+原因是tag不允许读firmware version，添加以下修正后测试OK
+
+
diff --git a/Failed+to+start+ringing.md b/Failed+to+start+ringing.md
new file mode 100644
index 0000000..3d8aa83
--- /dev/null
+++ b/Failed+to+start+ringing.md
@@ -0,0 +1,42 @@
+# Failed to start ringing
+
+
+
+\
+
+tone_index 0xff 是不对的, 麻烦check是不是mcu cfg tool没有配置对应的vp或ringtone
+
+
+
+\
+
+
+
+\
+
+失败log:
+
+
+
+
+
+
+
+ 0001558 04-21#15:30:37.893 171 0061084.191 [APP] !**app_dult_cb: msg_type 3
|
+
+
+ 0001559 04-21#15:30:37.893 172 0061084.226 [APP] !**app_dult_handle_ctrl_opcode: opcode 0x300, len 0
|
+
+
+ 0001560 04-21#15:30:37.893 173 0061084.348 [APP] !**app_audio_tone_type_play: tone_type 0x4f, tone_index 0xff, state=0, index=0xff, flush=0, check_result = 0
|
+
+
+ 0001561 04-21#15:30:37.893 174 0061084.404 [APP] !**app_dult_report_cmd_rsp: opcode 0x300, rsp_state 1
|
+
+
+ 0001562 04-21#15:30:37.893 175 0061084.431 [APP] !**app_dult_send_indication
|
+
+
+
+
+[BB2BUG-52986] [BB2][C-CUT][8763ESE][Amazon][v3.13.3.8+test bin][GFPS]Ringing using the accessory non-owner service测试失败 - Jira
diff --git a/Filter+address(XX+XX+XX)+by+model+id(XX+XX+XX)+failed_+no+service.md b/Filter+address(XX+XX+XX)+by+model+id(XX+XX+XX)+failed_+no+service.md
new file mode 100644
index 0000000..667189a
--- /dev/null
+++ b/Filter+address(XX+XX+XX)+by+model+id(XX+XX+XX)+failed_+no+service.md
@@ -0,0 +1,9 @@
+# Filter address(XX XX XX) by model id(XX XX XX) failed: no service
+
++by+model+id(XX+XX+XX)+failed_+no+service_7a74e0dc.jpg)
+
+BBPRO3BUG-28398-20260324-RetroactivePairTestFail-1.7z
+
+[BBPRO3BUG-28398] [BBPRO3][EVB][E Cut][3.15.0.8_0128+TestBin]Fast pair Validator APP测试，Retroactive Pair Test Fail - Jira
+
+https://partnerissuetracker.corp.google.com/u/0/issues/new?template_issue=403164452&component=1084169
diff --git a/Found+device+by+AK,+but+it+is+not+expected+to+advertise+Fast+Pair.md b/Found+device+by+AK,+but+it+is+not+expected+to+advertise+Fast+Pair.md
new file mode 100644
index 0000000..93f5796
--- /dev/null
+++ b/Found+device+by+AK,+but+it+is+not+expected+to+advertise+Fast+Pair.md
@@ -0,0 +1,23 @@
+# Found device by AK, but it is not expected to advertise Fast Pair
+
+
+
+factory reset 之后没有更新 gfps adv data, gfps adv data 里面还携带account key filter
+
+//gfps_gen_adv_data 最后一次生成adv data, 42(filter length 是4， 说明存在一组account key) 44 84 84 20
+
+0007327 01-14#15:45:11.940 215 0013643.981 \[APP\] !\*\*gfps_gen_adv_data: adv mode 1, tx_power -6, popup_show_ui 0, adv data 02 01 02 02 0A FA 0C 16 2C FE 00 42 44 84 84 20 21 1C 8E, len 19
+
+ 0000117 01-14#15:50:10.942 072 0312679.101 \[APP\] app_gfps_timer_timeout_cb: timer_id 5, timer_chann 0\
+ 0000118 01-14#15:50:10.942 073 0312679.135 \[APP\] app_gfps_timer_timeout_cb: not provisioned within 5 minutes, shall do factory reset
+
+//删掉account key之后要更新adv data\
+ 0000119 01-14#15:50:10.942 074 0312679.156 \[APP\] !!\*app_gfps_account_key_clear
+
+\
+
+正常的adv data 应该是：02(没有account key, filter length 是0) 21 66 B8
+
+ 0001269 11-04#11:47:47.755 223 0646200.670 \[APP\] !\*\*gfps_gen_adv_data: adv mode 1, tx_power -6, popup_show_ui 0, adv data 02 0A FA 08 16 2C FE 00 02 21 66 B8, len 12
+
+
diff --git a/GFPS+FAQ.md b/GFPS+FAQ.md
new file mode 100644
index 0000000..2cf212e
--- /dev/null
+++ b/GFPS+FAQ.md
@@ -0,0 +1,105 @@
+# GFPS FAQ
+
+(The following questions and answers are extracted from the discussion with Google team)
+
+**1. ** **How do I register the mode id and get the Anti-Spoofing Public/Private Key Pair? Is it necessary to register once for each headset registration (exclusive mode id) or a batch of product registration (shared mode id)?**
+
+A batch of products registered once.
+
+**2. ** **If our headphones use this feature, do we need google authentication?**
+
+Need to give Google a headset for testing.
+
+**3. ** **In pairing mode provider using discoverable advertising, and not in pairing mode provider using not discoverable advertising. But how the fast pair provider decide which mode it is?**
+
+Fast pair provider is in headset side. So it should be able to know headset status to see if headset is in pairing mode or not. For example, the user can force headset in pairing mode like long press some button. After headset is connected, then it is not in pairing mode.
+
+In short, in pair mode, we advertise BLE with model ID. When headset is not discoverable, we advertise BLE with account key list.
+
+**4. ** **What’s the difference between these two modes in fast pair procedure?**
+
+One key feature of Fast Pair 2.0 is when you have paired the headset to a phone, other phones or devices with the same account will know and are able to pair the headset via fast pair notification directly.
+
+So in pairing mode, if a phone pairs with the headset via fast pair notification, the account info will bring back to headset in account key list. So when headset not in pairing mode, the headset will broadcast BLE advertisement with account key list and nearby devices will be aware of.
+
+**5. ** **One scenario, if headset want to pair with android device, it should enter the pairing mode, advertise mode ID (trigger by user, such as press some button of headset). Android device show a high priority notification, user should click this notification to complete the fast pair procedure. Also another scenario, once provider broadcast BLE advertisement with account key filter, android device with the same account aware that there is a previously paired headset nearby, so android device with pair the headset directly, user need to do nothing, is that right?**
+
+For second scenario, a fast pair notification will appear with wordings like "Your paired device is available..." in description. And the user still has to tap the fast pair notification to complete pairing.
+
+**6. ** **In both pairing modes user should tap fast pair notification to complete pairing. Spec D11 provides that both discoverable advertising and not discoverable advertising are using random resolvable private address (RPA). It seems that pairing mode and not in pairing mode have no difference? Both modes using RPA to prevent tracking, in both modes user need to tap notification to complete pairing.**
+
+To sum up, it is necessary to send the discoverable advertising to start pair procedure with android device unpaired before. If android device has paired before, to start pair procedure, provider can send either discoverable advertising or not discoverable advertising.
+
+There is a situation where not discoverable advertising is used. The headset is paired with a device and remains connected. At this time, provider send not discoverable advertising, if the device login the same google account close, the device will receive the pairing prompt. That is, one headset can be paired with multiple devices at the same time.
+
+**7. ** **Android device must be logged in to google account to use this fast pair feature?**
+
+Currently the answer is yes since you need to be whitelisted to get to see the notifications. After Fast Pair goes public in about a month, the requirement is that the user gets the relevant Play Services update, which should happen for pretty much all Android 6.0+ users across the world (with the exception of Chinese devices that don't have Play).
+
+**8. ** **Is the provider must support the Numeric Comparison pairing method of LE? BR/EDR also support method of Numeric Comparison?**
+
+The provider should support numeric comparison through either method, although our code should be sending the request over BR/EDR.
+
+**9. ** **Does it means if LE Secure connection is mandatory for provider if it need to support Google fast pairing?**
+
+Correct, in the future it is possible that we could attempt an LE connection first instead of BR/EDR so support for that should be included if at all possible.
+
+**10. ** **Make sure that in pairing mode use resolvable private address.**
+
+We want to use a rotating private address for privacy reasons, this helps to prevent headphones from being tracked throughout the day.
+
+**11. ** **Is it mandatory or just strongly recommend provider to follow it. Because customers may use other BLE random address type (such as static random address) to implement some other features.**
+
+It is not a hard requirement, we only really care that the address returned as part of step 5 in the spec (although some partners were running into issues if they advertise with the same address as their public address, so I would still recommend using a different address, even if it is static, if you run into problems there).
+
+**12. ** **In step 5, what does it mean become discoverable for 10 seconds but shall not advertise Fast Pair Model ID, and what’s the reaction on seeker’s side.**
+
+Here we want the headphones to become discoverable (IE, what would normally happen if the user holds the pairing button or something like that, depending on the headset), but not advertise the model ID so that we don't show a notification for it on other phones in the area. From the seekers side, we have to scan for it to work around a bug on older Android versions where we're not able to pair until we've actually discovered the device first. This flag will only be set for Android devices on 7.0 or lower where the bug exists.
+
+**13. ** **“headphones to become discoverable” means headphone advertise like the pairing mode advertising, the same Advertising interval and BLE address, but the payload only include service UUID, no model ID. And we can test this scenario in Android devices on 7.0 or lower, correct?**
+
+Correct, everything should stay the same as pairing mode except the model ID shouldn't be advertised so that other devices in the area won't display a notification and try and steal the connection. You can test with any device that is Android 7.0 or lower, that's right. We're actually experimenting with removing this step to see if the connection can still succeed (there was an old bug on Android devices that this originally worked around), however it is in place right now so if you're testing with a 7.0 or below device then it won't work unless this is in place.
+
+**14. ** **In step 8/9/10, request’s flags byte has bit 1 set to 1 means provider shall send pairing request to seeker on BR/EDR, right? I have never encountered this situation. Request’s flags byte has bit 1 set to 0 means seeker will send pairing request to provider via BR/EDR or BLE, and in which situation via BR/EDR, which situation via BLE? Rules of step 10 shall be follow on Pairing via BR/EDR and BLE, right?**
+
+The provider bonding with the seeker is a bit of a different situation that isn't very common, but helps to work around a security issue that was brought up by some of our reviewers. It isn't a likely case though and this flag is off right now, so you won't see it happen in testing and I'm not sure that we'll ever turn it on.
+
+**15. ** **If some days later you turn it on, please let us know, we want to verify it to make sure the code flow is correct.**
+
+Yes we'll absolutely let you know if this change is made, but like I said I don't think it will be so not too much to worry about for now.
+
+**16. ** **Passkey Block salt means the last 12 bytes of Raw Passkey Block, right?**
+
+Yes, the salt is whatever is needed to fill up the packet to 16 bytes.
+
+**17. ** **It is Raw Passkey Block, not Raw Response. From table 2.2 Octet 4-15 is reserved, it is not the salt. Would you please check it again?**
+
+This is a bit unclear in the spec, I'll update it to include more details. Step 15 discusses filling this packet and mentions a salt, but the table itself does not mention a salt. The salt should be bytes 4-15, you can generate any random value and put it there to complete the packet.
+
+**18. ** **If the optional Public Key field is present: if the device is not in pairing mode, ignore the write and exit. The “exit” means provider to disconnect the BLE link, or keep BLE connecting and don’t perform the pairing process?**
+
+Provider can disconnect the link at this point if an invalid request comes in, this will stop the seeker from continuing.
+
+**19. ** **In table 1.2, Raw Request octet 2-7 maybe provider’s current BLE address or provider’s public address. Provider’s current BLE address means the resolvable private address used in advertising, and provider’s public address means the BR/EDR public address, right? In what circumstances Raw Request contain current BLE address or public address?**
+
+Those are both correct. Android will automatically resolve the BLE address into the BR/EDR address in some cases if the two devices have connected previously, meaning there isn't a way for us to know whether we're sending the provider its BLE address or BR/EDR address, so that is why this provision needed to be included.
+
+**20. ** **After pairing, the Fast Pair Seeker may write an Account Key to the Fast Pair Provider.** **So, sometimes seeker may not send account key to provider, in what circumstances seeker will distribute account key and what circumstances won’t?**
+
+We'll always write the account key as long as the GATT connection is maintained (and we'll try and recreate it if it isn't maintained). I'll reword this so that it is clearer.
+
+**21. ** **If no key could successfully decrypt the value, ignore the write and exit. a. Keep a count of these failures. When the failure count hits 10, fail all new requests immediately. Reset the failure count after 5 minutes, after power on, or after a success. Does the “fail all new requests immediately” means provider disconnect the link?**
+
+If provider didn’t analysis request successful, no need to response, seeker will retry write request, after retry 3 times and get no response, seeker will disconnect the link. Provider only need to disconnect the link once calculate failure times up to 10.
+
+**22. ** **If the decrypted request’s Flags bit requesting discoverability is set to 1, become discoverable for 10 seconds, or until this pairing process completes, whichever comes first.** **I am not sure about this process. Can you analyze it?**
+
+Broadcast for 10 seconds or broadcast until the pairing process complete (the pairing process may be completed in 3s), clarifying that this is for work around an android bug.
+
+**23. ** **When confirmation of the passkey is needed, wait up to 10 seconds for a write to the Passkey characteristic. If provider doesn’t receive passkey in 10 seconds, what shall provider do?**
+
+Try to disconnect the link if provider doesn’t receive passkey in 10 seconds.
+
+
+
+相关jira： BUMBEERD-667 - \[BBPro\] \[Upperstack\]\[BLE\]Google Fast Pairing Service Resolved
diff --git a/GFPS+认证测试.md b/GFPS+认证测试.md
new file mode 100644
index 0000000..da88632
--- /dev/null
+++ b/GFPS+认证测试.md
@@ -0,0 +1,15 @@
+# GFPS 认证测试
+
+手动测试视频: 认证Video.7z
+
+Note:
+
+ 1. realsilbt8888@gmail.com 这个账号只能用于 Fast Pair validator 测试，不可以用于手动测试
+
+realsilbt8888@gmail.com 这个账号下面的 Automatically save devices要关掉
+
+
+
+\
+
+**除了realsilbt8888@gmail.com之外的其他账号 Automatically save devices要打开**
diff --git a/Get+account+key+fail.md b/Get+account+key+fail.md
new file mode 100644
index 0000000..0eb5315
--- /dev/null
+++ b/Get+account+key+fail.md
@@ -0,0 +1,29 @@
+# Get account key fail
+
+
+
+\
+
+**case1.**Retroactive pairing didn't be triggered. It may related to **Geller read failed.**
+
+**Please try below steps and see if we can cleanup your geller database. Thanks!**
+
+forget headset from the Phone \
+go to "Settings -\> Google -\> Device & sharing -\> Devices -\> Saved devices" \
+toggle OFF "Automatically save devices" (this deletes all the FastPair devices from footprints) \
+wait for 3 hours for the recon sync to be triggered (it's handled by a job scheduler)
+
+**case2.** Handshake failed. **When we do GATT operation during retroactive pairing, it time-outed. Please check it on provider side**
+
+\[bugreport-panther-AP2A.240302.001-2025-03-13-16-47-25.zip\]
+
+**// Type 1 Geller read failed. 需要参考上面case1进行解决**\
+03-13 15:28:55.941258 10166 5724 30662 I NearbyDiscovery: \[trigger-id=Paed742B4076, feature-id=Repa\] RetroactivePairManager: Skip, timeout exceeds, mac=XX:XX:XX:XX:77:42 \[CONTEXT service_id=265 \]\
+03-13 15:28:59.518245 10166 5724 28547 E Geller : **Geller read failed.**\
+03-13 15:29:53.610999 10298 5295 30528 I BaseModuleTask: event=ModuleEvent{message=Get account key (XX:XX:XX:XX:77:42), status=FAILURE}, callback=dwj@743606b, executor=ayd@cd2d7c8
+
+**// Type 2 GATT_CONNECTION_AND_SECRET_HANDSHAKE FAILURE 需要参考上面case2, seeker 发送kbp request, provider没有回kbp response**\
+ 03-13 15:34:13.519260 10166 5724 31127 I NearbyDiscovery: \[trigger-id=Paed632BE4B5, feature-id=Repa\] Analytics: cuj-state=UPDATE: **GATT_CONNECTION_AND_SECRET_HANDSHAKE FAILURE **\[CONTEXT service_id=265 \]\
+GATT_CONNECTION_AND_SECRET_HANDSHAKE\
+03-13 15:34:13.541641 10166 5724 31127 E NearbyDiscovery: com.google.android.libraries.bluetooth.BluetoothTimeoutException: Operation timed out after 10000ms\
+03-13 15:34:59.870081 10298 5295 31118 I BaseModuleTask: event=ModuleEvent{message=Get account key (XX:XX:XX:XX:77:42), status=FAILURE}, callback=dwj@743606b, executor=ayd@14f4f57
diff --git a/Locator+Tracker+Pair+device+fail.md b/Locator+Tracker+Pair+device+fail.md
new file mode 100644
index 0000000..eadfbbd
--- /dev/null
+++ b/Locator+Tracker+Pair+device+fail.md
@@ -0,0 +1,9 @@
+# Locator Tracker Pair device fail
+
+
+
+\
+
+model id 注册的时候 Data-Only Connection 需要设置成true
+
+
diff --git a/Name+test+fail--提示_Write+name+to()by+initial+pair+fail_.md b/Name+test+fail--提示_Write+name+to()by+initial+pair+fail_.md
new file mode 100644
index 0000000..58c28cc
--- /dev/null
+++ b/Name+test+fail--提示_Write+name+to()by+initial+pair+fail_.md
@@ -0,0 +1,3 @@
+# Name test fail--提示"Write name to()by initial pair fail"
+
+by+initial+pair+fail__041ec819.jpg)
diff --git a/Pair+device+fail.md b/Pair+device+fail.md
new file mode 100644
index 0000000..797d1bf
--- /dev/null
+++ b/Pair+device+fail.md
@@ -0,0 +1,35 @@
+# Pair device fail
+
+
+
+看样子是手机端出问题了，可以重启手机之后再次尝试该测项。
+
+log 分析：
+
+BLE 连上之后，手机查耳机端的primary service，
+
+当手机从start handle 是26 开始查primary service的时候
+
+耳机有答复对应的primary service， start handle 是 26 ，end handle 是 46
+
+
+
+接下来手机应该从start handle 47 开始继续往下查primary service，但是后面手机一直从 start handle 26查服务
+
+
+
+因为gfps service 在后面注册的，导致手机查不到gfps的service，再后面手机就断线了。
+
+\
+
+出问题的log:
+
+COM3_btsnoop_2023-03-22_14-42-45.cfa
+
+COM3_2023-03-22_14-42-34.log
+
+正常的log：
+
+COM3_2023-03-22_14-59-12.log
+
+COM3_btsnoop_2023-03-22_14-59-14.cfa
diff --git a/Pairing+Failed!+[Pair+time-out,+Not+receive+UUID,+Is+primary+address+connected_+false,+Is+secondary+address+connected_+false].md b/Pairing+Failed!+[Pair+time-out,+Not+receive+UUID,+Is+primary+address+connected_+false,+Is+secondary+address+connected_+false].md
new file mode 100644
index 0000000..f38697f
--- /dev/null
+++ b/Pairing+Failed!+[Pair+time-out,+Not+receive+UUID,+Is+primary+address+connected_+false,+Is+secondary+address+connected_+false].md
@@ -0,0 +1,33 @@
+# Pairing Failed! \[Pair time-out, Not receive UUID, Is primary address connected: false, Is secondary address connected: false\]
+
+GG18.zip
+
+/RS/QC/lucy_ge/bbpro3 bug/28142/lucy/GG18 换了只手机第4轮遇到这个
+
+
+
+\
+
+\
+
+
+
+
+
+
+
+ 0003173 03-06#17:23:56.048 005 0056462.036 [SMP] !**sm_handle_le_encrypt_change: p_link 0x004200b8, handle 0x0011, status 0x0124, encrypted 0
|
+
+
+ 0003174 03-06#17:23:56.048 006 0056462.062 [PATCH] sm_authen_cmpl: remote addr type 0x01, mode 0x00001500, state 0x09, cause 0x0124, type 0
|
+
+
+
+
+\
+
+
+
+\
+
+[BBPRO3BUG-28142] [Laplace][Earbud]PTS-135] GFPS：Fail in "End-to-End Integration" - Jira
diff --git a/Pairing+Failed!+[Total+pairing+time+15490ms+_threshold+15000ms].md b/Pairing+Failed!+[Total+pairing+time+15490ms+_threshold+15000ms].md
new file mode 100644
index 0000000..2674562
--- /dev/null
+++ b/Pairing+Failed!+[Total+pairing+time+15490ms+_threshold+15000ms].md
@@ -0,0 +1,34 @@
+# Pairing Failed! \[Total pairing time 15490ms \>threshold 15000ms\]
+
+
+
+
+
+step：
+
+1. 双耳进pairing 测试
+2. 会报pairing time超时的问题（164904）/（164956），每轮都会
+
+log;20260302 28142.zip
+
+
+
+\
+
+主附耳总的配对时间超过Google规定的值15s，建议：
+
+1.查看附耳在处理 Fast Pair 强制进入配对模式的逻辑处（app_gfps_sec_handle_additional_io_cap 接收到同步消息改变 io_cap 之后），le audio 广播有没有Enable，以及广播的interval是多少Google强烈建议为了使手机能够尽快的通过LE audio广播发现附耳， 此时附耳的le audio 广播interval要尽可能的小，Google推荐是0x20(20ms), 但是我看 le audio设置的
+
+APP_LEA_ADV_INTERVAL_FAST 0x30，
+
+如果此时le audio的interval是 APP_LEA_ADV_INTERVAL_SLOW 0x140 那肯定是会影响发现的速度的
+
+\
+
+2.附耳BLE连线建立之后，ATT层LE audio 相关service的发现比较耗时，一个建议是打开GATT caching，还有一个建议是缩小connection interval(但是le audio同事说如果设备端主动更新connection interval， 有的手机会断线，所以这个方式不可行)
+
+\
+
+3. 去屏蔽室测试，排除环境干扰，屏蔽室测试OK之后，把pass的结果submit就可以，Google 认证实验室不会验证，只需要我们验证pass之后提交pass的测试结果到Google后台即可。
+
+
diff --git a/Pairing+failed!+[Pair+time-out,+total+pair+time+21126+_+threshold+15000ms....].md b/Pairing+failed!+[Pair+time-out,+total+pair+time+21126+_+threshold+15000ms....].md
new file mode 100644
index 0000000..0620cf8
--- /dev/null
+++ b/Pairing+failed!+[Pair+time-out,+total+pair+time+21126+_+threshold+15000ms....].md
@@ -0,0 +1,31 @@
+# Pairing failed! \[Pair time-out, total pair time 21126 \> threshold 15000ms....\]
+
+
+
+\
+
+hi Wade Li(李伟东) ：
+
+附耳的LEA广播好像有问题，想请你协助客户分析一下app层的code
+
+一个是adv data 的设置必须要在 adv 参数初始化之后设置
+
+
+
+还有一个是感觉lea adv似乎没有初始化
+
+
+
+
+
+\
+
+林詩皓 added a comment - 2026/03/02 12:08
+
+https://cn4soc.rtkbf.com/gerrit/c/HoneyRepo/lowerpatch/+/303949/1
+
+可以用這筆試試看
+
+\
+
+[BBPRO3BUG-28142] [Laplace][Earbud]PTS-135] GFPS：Fail in "End-to-End Integration" - Jira
diff --git a/Pairing+failed!+[Pair+time-out].md b/Pairing+failed!+[Pair+time-out].md
new file mode 100644
index 0000000..877858d
--- /dev/null
+++ b/Pairing+failed!+[Pair+time-out].md
@@ -0,0 +1,15 @@
+# Pairing failed! \[Pair time-out\]
+
+
+
+\
+
+原因是setting 界面 开发者选项里面没有enable以下配置
+
+
+
+\
+
+详细信息请参考：
+
+1 测试准备工作 - BT_Market - WIKI
diff --git a/Pairing+failed!+[Pair+timeout+only+receive+correct+UUID+from+1+address......].md b/Pairing+failed!+[Pair+timeout+only+receive+correct+UUID+from+1+address......].md
new file mode 100644
index 0000000..1e66cef
--- /dev/null
+++ b/Pairing+failed!+[Pair+timeout+only+receive+correct+UUID+from+1+address......].md
@@ -0,0 +1,3 @@
+# Pairing failed! \[Pair timeout only receive correct UUID from 1 address......\]
+
+
diff --git a/Pairing+failed!......KeyBasedPairingExtensionResponse+wrong+address+length_+1.md b/Pairing+failed!......KeyBasedPairingExtensionResponse+wrong+address+length_+1.md
new file mode 100644
index 0000000..e57c058
--- /dev/null
+++ b/Pairing+failed!......KeyBasedPairingExtensionResponse+wrong+address+length_+1.md
@@ -0,0 +1,29 @@
+# Pairing failed!......KeyBasedPairingExtensionResponse wrong address length: 1
+
+
+
+End-to-End Integration-pairing failed.7z
+
+设备：TWS 耳机支援LE audio
+
+手机：支援LE audio
+
+测试的时候有Enable LE Spec Test
+
+\
+
+ **// 设备是支援LE audio的TWS耳机，le_device_mode 0 是不对的，这个值是MCU cfg tool配置的，麻烦自查认证测试文档**
+
+0001530 02-10#15:13:12.989 143 0027119.990 \[APP\] !\*\*gfps_send_kbp_response_le: le_device_support 1, le_device_mode 0\
+ 0001531 02-10#15:13:12.989 144 0027140.696 \[PATCH\] patch_hw_aes_operate_imp: error code: 0x0\
+ 0001532 02-10#15:13:12.989 145 0027140.775 \[APP\] !\*\*gfps_send_kbp_response_le: raw response 02 00 01 19 97 88 00 00 00 91 21 1F 31 DD C7 5C, encrypt response AC D6 3E CA C6 A1 84 71 9C 6C A7 71 7E C4 DE BF
+
+\
+
+**如果设备是支援LE audio的， Enable GFPS LE Pair 要勾选，GFPS device mode 设成 Dual mode device with CSIP/Dual mode device with LE Audio**
+
+
+
+[BBPRO3BUG-28142] [Laplace][Earbud]PTS-135] GFPS：Fail in "End-to-End Integration" - Jira
+
+\
diff --git a/Pairing+failed![Pair+time-out,+Total+pairing+time+18020ms_threshold+12000ms].md b/Pairing+failed![Pair+time-out,+Total+pairing+time+18020ms_threshold+12000ms].md
new file mode 100644
index 0000000..9282791
--- /dev/null
+++ b/Pairing+failed![Pair+time-out,+Total+pairing+time+18020ms_threshold+12000ms].md
@@ -0,0 +1,19 @@
+# Pairing failed\![Pair time-out, Total pairing time 18020ms\>threshold 12000ms\]
+
+
+
+\
+
+设备端是支援LE audio的立体声耳机，原因是耳机是支援 GFPS LE的
+
+
+
+\
+
+但是 fast pair validator 没有Enable LE spec test
+
+Enable LE spec test之后要根据耳机实际的配置选择是否支援LE audio, 以及是否支援CSIP(TWS耳机支援CSIP，single mode 不支援CSIP)
+
+
+
+\
diff --git a/Pairing+failed！[Pair+time-out].md b/Pairing+failed！[Pair+time-out].md
new file mode 100644
index 0000000..4e5aa4d
--- /dev/null
+++ b/Pairing+failed！[Pair+time-out].md
@@ -0,0 +1,69 @@
+# Pairing failed！\[Pair time-out\]
+
+140522 Pairing Failed Pair timeout.zip
+
+
+
+\
+
+原因是BR ACL link 建立之后，4s没连legacy profile， 设备端主动把BR ACL link 断掉了，导致GFPS 流程异常
+
+Line 81655: 0008329 03-03#14:05:14.028 249 0047231.527 \[APP\] !\*\*connected: b2s, bd_addr AC::3E::B1::09::07::C6, profs 0x00000000
+
+\
+
+**问：**
+
+设备端断开L2cap的原因是设备端没有收到手机端主动连A2dp/hfp ，这好像是符合蓝牙spec的， 设备是支援le audio的TWS耳机，手机也支援le audio, 是不是手机本身就不会连A2dp/hfp, 而是会通过le audio交互音频数据
+
+\
+
+**答：**
+
+\*\*在支持 LE Audio 的双模（Dual-Mode）TWS 耳机测试中，Android 手机（特别是支持 LE Audio 的较新系统）的配对和连接行为确实与纯经典蓝牙耳机有很大不同。\*\* 手机在连接时会优先进行 LE Audio 的服务发现和配置，从而“冷落”或延迟建立经典蓝牙的 A2DP/HFP 业务。
+
+这不仅没有推翻之前的分析，反而\*\*完美地解释了为什么会发生 L2CAP 超时。\*\* 之前的分析依然绝对可靠，我们可以结合 LE Audio 的特性来彻底还原这个 Google 测项失败的完整逻辑。
+
+\### 1. 为什么说分析依然可靠？（结合日志的铁证）
+
+在左耳（COM4）主动断开经典蓝牙连接（14:05:18.140）的\*\*同一毫秒\*\*，我们看看耳机在 BLE 链路上正在忙什么：
+
+\`\`\`text\
+ 0004586 03-03#14:05:18.140 005 \[PROTOCOL\] !\*\*ascs_attr_read_cb: attrib_index 8, offset 0\
+ 0004587 03-03#14:05:18.140 006 \[PROTOCOL\] !\*\*ase_gen_char_data: ase_id 2, direction: 1, ase_state 0, len 2\
+ 0004588 03-03#14:05:18.140 007 \[BTIFMSG\]↙BTIF_MSG_GATT_ATTR_READ_CFM...\
+ ...\
+ 0004594 03-03#14:05:18.140 013 \[PATCH\] l2c_handle_timeout: timer_id 0x84, timer_chann 0x0042\
+ 0004595 03-03#14:05:18.140 014 \[HCI\] !\*\*hci_cmd_disconnect: handle 0x0002, cause 0x13\
+ 0004599 03-03#14:05:18.140 018 \[MODULE_LOWERSTACK\] ... --\> send lmp opc:7 ... Name is LMP_detach\
+\`\`\`
+
+\*\*解析：\*\*
+
+\* \`ascs_attr_read_cb\`：\*\*ASCS (Audio Stream Control Service)\*\* 是 LE Audio 的核心服务。这证明手机此刻并没有闲着，它正在疯狂地通过 BLE 读取耳机的 LE Audio 属性（GATT Discovery）。\
+\* 手机在 \`14:05:14\` 的时候，其实已经顺手把经典蓝牙的底层 ACL 链路（handle \`0x0002\`）建好了（为了双模兼容性）。\
+\* 但是，因为手机正忙着在 BLE 上配置 LE Audio，它\*\*延迟了\*\*在经典蓝牙链路上发起 SDP / A2DP / HFP。\
+\* 耳机端（底层协议栈）有个死板的定时器（\`timer_id 0x84\`）：如果经典蓝牙 ACL 建连后大约 \*\*4 秒内\*\*没有收到 Profile 级的 L2CAP 交互（\`timer_chann 0x0042\`），耳机就认为经典链路是“死链接”，从而\*\*主动将其断开\*\*。
+
+**\*\*结论：\*\* 手机觉得“我正在忙着配 LE Audio，经典蓝牙你先等着”，但耳机觉得“经典蓝牙连上了4秒你还不理我，我把你挂了”。\*\*耳机主动挂断经典蓝牙，导致 Android 系统的蓝牙状态机认为整个双模配对流程出现异常，从而在 3.8 秒后（14:05:22）把 BLE 链路也彻底断了，报出 Pairing Failed。\*\***
+
+\
+
+**您的耳机固件目前的逻辑对于纯经典蓝牙是合理的（防呆机制，防止占着信道不发数据），但\*\*对于 LE Audio 双模流程来说是致命的 bug\*\*。**
+
+**\*\*修复建议：\*\***
+
+1\. \*\*修改 L2CAP Idle Timeout 机制\*\*：\
+ 在检测到当前正处于 Google Fast Pair 流程中，或者当前 BLE 链路正在进行 LE Audio (ASCS/PACS) GATT 发现时，\*\*必须显著延长或直接禁用经典蓝牙侧的 L2CAP 空闲断开定时器（将 4 秒至少延长至 15-30 秒，或者等待 BLE 侧彻底配置完毕）\*\*。\
+2. \*\*状态机关联\*\*：\
+ 让经典蓝牙的连接状态机能够“感知”到 BLE 侧的繁忙状态。只要 BLE 侧的 GFPS/LE Audio 协商还在进行，就允许经典蓝牙保留一条没有 Profile 数据的“空” ACL 链路，不要主动发送 \`LMP_detach\`。
+
+\
+
+\
+
+\
+
+\
+
+\
diff --git a/Pairing+process+error_+Reason_+Is+connected+false.md b/Pairing+process+error_+Reason_+Is+connected+false.md
new file mode 100644
index 0000000..d5a0e2e
--- /dev/null
+++ b/Pairing+process+error_+Reason_+Is+connected+false.md
@@ -0,0 +1,149 @@
+# Pairing process error: Reason: Is connected false
+
+
+
+https://partnerissuetracker.corp.google.com/u/0/issues/411582869
+
+\
+
+Hi BT team,
+
+When our partner tested Fast Pair via the Validator, it didn't connect to the phone correctly. Provider not support LEA and phone support LEA.\
+It looks like after device bonded and getting the UUIDs, the phone policy didn't trigger the classic profile connection, so the phone disconnected from the provider after a timeout.\
+Could you please check why it didn't trigger the classic profile connection?\
+Thanks a lot!
+
+ [bugreport-caiman-AD1A.240905.004-2025-04-18-14-32-41.zip]
+ // Device bonded
+ 04-18 14:30:36.473 1002 2508 2994 I BluetoothBondStateMachine: XX:XX:XX:XX:22:88 is bonded, wait for SDP complete to broadcast bonded intent
+
+ // SDP
+
+ 04-18 14:30:36.606 1002 2508 2910 I bt_bta_dm: bta_dm_sdp_result: GATT services discovered using SDP
+ 04-18 14:30:36.606 1002 2508 2910 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:1798 - btif_dm_search_services_evt: SDP finished for xx:xx:xx:xx:22:88:
+ 04-18 14:30:36.606 1002 2508 2910 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:1807 - btif_dm_search_services_evt: New UUIDs for xx:xx:xx:xx:22:88:
+ 04-18 14:30:36.606 1002 2508 2910 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:1813 - btif_dm_search_services_evt: index:0 uuid:00001101-0000-1000-8000-00805f9b34fb
+ 04-18 14:30:36.606 1002 2508 2910 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:1813 - btif_dm_search_services_evt: index:1 uuid:00001108-0000-1000-8000-00805f9b34fb
+ 04-18 14:30:36.607 1002 2508 2910 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:1813 - btif_dm_search_services_evt: index:2 uuid:0000111e-0000-1000-8000-00805f9b34fb
+ 04-18 14:30:36.607 1002 2508 2910 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:1813 - btif_dm_search_services_evt: index:3 uuid:0000110b-0000-1000-8000-00805f9b34fb
+ 04-18 14:30:36.607 1002 2508 2910 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:1813 - btif_dm_search_services_evt: index:4 uuid:0000110e-0000-1000-8000-00805f9b34fb
+ 04-18 14:30:36.607 1002 2508 2910 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:1813 - btif_dm_search_services_evt: index:7 uuid:6a24eeab-4b65-4693-986b-3c26c352264f
+ 04-18 14:30:36.607 1002 2508 2910 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:1813 - btif_dm_search_services_evt: index:8 uuid:df21fe2c-2515-4fdb-8886-f12c4d67927c
+ 04-18 14:30:36.607 1002 2508 2910 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:498 - get_cod: remote_cod=0x00244404
+ 04-18 14:30:36.607 1002 2508 2910 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:1863 - btif_dm_search_services_evt: SDP search done for xx:xx:xx:xx:22:88
+
+ // Not sure if waiting for LE service discovery here
+ 04-18 14:30:36.607 1002 2508 2910 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:1917 - btif_dm_search_services_evt: Bonding LE Audio sink - must wait for le services discovery to pass all services to java xx:xx:xx:xx:22:88
+ 04-18 14:30:36.607 1002 2508 2910 I bt_bta_dm: bta_dm_search_cmpl: No BLE connection, processing classic results
+
+ // Phone disconnected from provider.
+ 04-18 14:30:40.615 1002 2508 2910 I btm_acl : disconnect_acl: Disconnecting peer:xx:xx:xx:xx:22:88 reason:HCI_ERR_PEER_USER comment:stack::l2cap::l2c_link::l2c_link_timeout All channels closed
+ 32183 06:30:40.616070 host controller HCI_CMD 7 Sent Disconnect
+
+\
+
+\
+
+ // ACL LE connected
+
+ 04-18 14:30:32.132 1002 1048 2043 I bthal.activity: handle_ble_meta_event: LE Enhanced Connection Complete, conn_handle:041, conn_bda: XX:XX:44:44:22:88
+ 04-18 14:30:32.223 1002 2508 2910 I bt_bta_dm: bta_dm_acl_up: Acl connected peer:xx:xx:xx:xx:22:88 transport:BT_TRANSPORT_LE handle:65
+ 04-18 14:30:34.934 1002 2508 2910 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:586 - bond_state_changed: Bond state changed to state=1[0:none, 1:bonding, 2:bonded],prev_state=0, sdp_attempts=0
+ 04-18 14:30:34.934 1002 2508 2954 I BluetoothBondStateMachine: bondStateChangeCallback: Status: 0 Address: XX:XX:XX:XX:22:88 newState: 1 hciReason: 0
+ 04-18 14:30:34.944 1002 2508 2994 I BluetoothBondStateMachine: Bond State Change Intent:XX:XX:XX:XX:22:88 BOND_NONE => BOND_BONDING
+
+ // ACL BR/EDR connected
+ 04-18 14:30:36.075 1002 2508 2910 I bt_bta_dm: bta_dm_acl_up: Acl connected peer:xx:xx:xx:xx:22:88 transport:BT_TRANSPORT_BR_EDR handle:11
+ 04-18 14:30:36.467 1002 2508 2910 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:586 - bond_state_changed: Bond state changed to state=2[0:none, 1:bonding, 2:bonded],prev_state=1, sdp_attempts=1
+ 04-18 14:30:36.467 1002 2508 2954 I BluetoothBondStateMachine: bondStateChangeCallback: Status: 0 Address: XX:XX:XX:XX:22:88 newState: 2 hciReason: 0
+ 04-18 14:30:36.473 1002 2508 2994 I BluetoothBondStateMachine: XX:XX:XX:XX:22:88 is bonded, wait for SDP complete to broadcast bonded intent
+ 04-18 14:30:36.473 1002 2508 2994 I BluetoothBondStateMachine: StableState(): Entering Off State
+ 04-18 14:30:36.607 1002 2508 2910 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:1917 - btif_dm_search_services_evt: Bonding LE Audio sink - must wait for le services discovery to pass all services to java xx:xx:xx:xx:22:88
+ 04-18 14:30:39.492 1002 2508 2994 I BluetoothBondStateMachine: Bond State Change Intent:XX:XX:XX:XX:22:88 BOND_BONDING => BOND_BONDED
+
+ / BT_ACL_STATE_DISCONNECTED
+
+ 04-18 14:30:40.768 1002 2508 2910 I bt_shim_hci: packages/modules/Bluetooth/system/main/shim/hci_layer.cc:304 - operator(): ISO disconnection from GD, handle: 0x0b, reason: 0x13
+ 04-18 14:30:40.769 1002 2508 2910 D bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:2552 - btif_dm_acl_evt: Sent BT_ACL_STATE_DISCONNECTED upward as ACL link down event device:xx:xx:xx:xx:22:88 reason:HCI_ERR_PEER_USER
+ 04-18 14:30:51.134 1002 2508 2910 I bt_shim_hci: packages/modules/Bluetooth/system/main/shim/hci_layer.cc:304 - operator(): ISO disconnection from GD, handle: 0x41, reason: 0x16
+ 04-18 14:30:51.137 1002 2508 2910 D bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:2552 - btif_dm_acl_evt: Sent BT_ACL_STATE_DISCONNECTED upward as ACL link down event device:xx:xx:xx:xx:22:88 reason:HCI_ERR_CONN_CAUSE_LOCAL_HOST
+
+ // Bonding Removed
+
+ 04-18 14:31:50.137 1002 2508 2910 I bt_btif_storage: packages/modules/Bluetooth/system/btif/src/btif_storage.cc:889 - btif_storage_remove_bonded_device: Removing bonded device addr=xx:xx:xx:xx:22:88
+ 04-18 14:31:50.137 1002 2508 2910 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:586 - bond_state_changed: Bond state changed to state=0[0:none, 1:bonding, 2:bonded],prev_state=2, sdp_attempts=0
+ 04-18 14:31:50.137 1002 2508 2910 I bt_btif_storage: packages/modules/Bluetooth/system/btif/src/btif_storage.cc:889 - btif_storage_remove_bonded_device: Removing bonded device addr=xx:xx:xx:xx:22:88
+ 04-18 14:31:50.137 1002 2508 2910 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:586 - bond_state_changed: Bond state changed to state=0[0:none, 1:bonding, 2:bonded],prev_state=0, sdp_attempts=0
+ 04-18 14:31:50.137 1002 2508 2910 E BluetoothMetricIdManager: packages/modules/Bluetooth/system/gd/common/metric_id_manager.cc:190 - ForgetDevice: Failed to remove device from paired_device_cache_
+ 04-18 14:31:50.140 1002 2508 2994 D AdapterProperties: Removing bonded device:XX:XX:XX:XX:22:88
+ 04-18 14:31:50.146 1002 2508 2994 I BluetoothBondStateMachine: Bond State Change Intent:XX:XX:XX:XX:22:88 BOND_BONDED => BOND_NONE
+ 04-18 14:31:50.147 1002 2508 2994 I BluetoothBondStateMachine: StableState(): Entering Off State
+
+`Fastpair made some configurations`
+
+ 04-18 14:30:30.959 10298 19745 26174 I BaseModuleTask: event=ModuleEvent{message=LE spec config: Enable LE spec: false, is module test LE spec supported false, expect LE audio connection: false, is provider CSIP supported: false, is provider LE audio supported: false, is provider data only: false, device type number: TRUE_WIRELESS_HEADPHONES, status=SUCCESS}, callback=dxh@74d2dcb, executor=ayp@5d289a8
+ 04-18 14:30:30.965 10298 19745 26174 I BaseModuleTask: event=ModuleEvent{message=Pairing time threshold is: 12000 ms., status=INFORMATION}, callback=dxh@74d2dcb, executor=ayp@5d289a8
+ 04-18 14:30:32.033 10298 19745 26174 I BaseModuleTask: event=ModuleEvent{message=Start to scan model id: DCC22B , status=SUCCESS}, callback=dxh@74d2dcb, executor=ayp@5d289a8
+ 04-18 14:30:32.085 10298 19745 26174 I BaseModuleTask: event=ModuleEvent{message=Succeed to scan model id: DCC22B , status=SUCCESS}, callback=dxh@74d2dcb, executor=ayp@5d289a8
+ 04-18 14:30:32.085 10298 19745 26174 I BaseModuleTask: event=ModuleEvent{message=Start to initial pair model id: DCC22B , status=SUCCESS}, callback=dxh@74d2dcb, executor=ayp@5d289a8
+ 04-18 14:30:32.100 10186 27707 26135 I FastPair: FPDC: Starting to pair XX:XX:XX:XX:22:88: key[64], Preferences{gattOperationTimeoutSeconds=10, gattConnectionTimeoutSeconds=15, bluetoothToggleTimeoutSeconds=10, bluetoothToggleSleepSeconds=2, classicDiscoveryTimeoutSeconds=13, numDiscoverAttempts=3, discoveryRetrySleepSeconds=1, ignoreDiscoveryError=false, sdpTimeoutSeconds=10, numSdpAttempts=0, numCreateBondAttempts=3, numConnectAttempts=2, numWriteAccountKeyAttempts=3, bluetoothStatePollingMillis=1000, numAttempts=2, enableBrEdrHandover=false, brHandoverDataCharacteristicId=11265, bluetoothSigDataCharacteristicId=11266, firmwareVersionCharacteristicId=10790, brTransportBlockDataDescriptorId=11267, removeBondTimeoutSeconds=5, removeBondSleepMillis=1000, createBondTimeoutSeconds=15, hidCreateBondTimeoutSeconds=40, proxyTimeoutSeconds=2, rejectPhonebookAccess=false, writeAccountKeySleepMillis=2000, queryDeviceForEddystoneSupport=true, readEddystoneProvisioningStateWhilePairing=false, eddystoneProvisioningStateSleepMillis=2000, eddystoneProvisioningStateReadAttemptsNum=3, checkRogueCharacteristicDuringProvisioning=false, skipBondCreation=false, retryGattConnectionAndSecretHandshake=false, gattConnectShortTimeoutMs=7000, gattConnectLongTimeoutMs=15000, gattConnectShortTimeoutRetryMaxSpentTimeMs=10000, addressRotateRetryMaxSpentTimeMs=20000, pairingRetryDelayMs=1000, secretHandshakeShortTimeoutMs=5000, secretHandshakeLongTimeoutMs=10000, secretHandshakeShortTimeoutRetryMaxSpentTimeMs=5000, secretHandshakeLongTimeoutRetryMaxSpentTimeMs=7000, secretHandshakeRetryAttempts=0, secretHandshakeRetryDelayMs=0, secretHandshakeRetryGattConnectionMaxSpentTimeMs=20000, signalLostRetryMaxSpentTimeMs=15000, pairFailureCounts=0, cachedDeviceAddress=, cachedDeviceIdentityAddress=, sameModelIdPairedDeviceCount=0, writeLeAudioMetadata=false, isDeviceFinishCheckAddressFromCache=true, enableBredrBondingForKeyBasedPairingResponse=true, maybeRemoveBondIfDeviceSupportsLe=true, maybeRemoveBondBeforeHandshake=true, connectWithoutSpecifyingProfileWithLeaDevice=true, enableObserveKeyMissingIntent=false, enableHandleKeyMissingIntentForClassicConnection=true, supportedProfileUuids=[17, 11, 17, 8, 17, 30, 24, 78], skipConnectingProfiles=false, evaluatePerformance=true, enableNamingCharacteristic=true, enableFirmwareVersionCharacteristic=true, isRetroactivePairing=false, isLeDevicePairing=false, numSdpAttemptsAfterBonded=1, gattConnectRetryTimeoutMillis=18000, gattConnectMaxAttempts=0, handlePasskeyConfirmationByUi=false, enterPasskeyByUi=false, isSeekerWearOs=false, isTempBondForAudioSharing=false, bleDeviceSpecEnabledByGatt=false, bleDeviceSpecSupported=false, leAudioSupported=false, logCheckLeaSupport=false, logLeAudioMetadataError=true, skipGattRefresh=true, verificationCodeForKeyBasedPairingRequest=[], mitmGattNotificationTimeoutSeconds=3, mitmGattReadRetryCount=15, mitmGattReadIdleMilliseconds=200, forcePublicAddressTypeForAdditionalComponents=false, checkAddressRotationBeforePairing=false, logRobustCacheHash=false, validatorMockKeyBasedPairingRequestFlags=null, dtNumber=-1}
+ 04-18 14:30:32.104 10298 19745 19745 I BaseModuleTask: event=ModuleEvent{message=Pair Step: Connect GATT, status=SUCCESS}, callback=dxh@74d2dcb, executor=ayp@5d289a8
+ 04-18 14:30:33.870 10298 19745 19745 I BaseModuleTask: event=ModuleEvent{message=Pair Step: Handshake, status=SUCCESS}, callback=dxh@74d2dcb, executor=ayp@5d289a8
+ 04-18 14:30:34.914 10298 19745 19745 I BaseModuleTask: event=ModuleEvent{message=Received key based response., status=SUCCESS}, callback=dxh@74d2dcb, executor=ayp@5d289a8
+ 04-18 14:30:34.922 10298 19745 19745 I BaseModuleTask: event=ModuleEvent{message=Pair Step: Create bond, status=SUCCESS}, callback=dxh@74d2dcb, executor=ayp@5d289a8
+
+`Bonding was started, ACL got connected and device paired successfully`
+
+ 04-18 14:30:34.925 10186 27707 26135 I FastPair: BluetoothAudioPairer: createBond, device=XX:XX:XX:XX:22:88, transport=BREDR
+ 04-18 14:30:34.935 1002 2508 2922 I bluetooth: packages/modules/Bluetooth/system/gd/hci/acl_manager/acl_scheduler.cc:168 - try_dequeue_next_operation: Pending connections is not empty; so sending next connection
+ 04-18 14:30:34.944 1002 2508 2994 I BluetoothBondStateMachine: Bond State Change Intent:XX:XX:XX:XX:22:88 BOND_NONE => BOND_BONDING
+ 04-18 14:30:36.024 1002 2508 2910 D bluetooth: packages/modules/Bluetooth/system/main/shim/acl.cc:1464 - CreateClassicConnection: Connection initiated for classic to remote:xx:xx:xx:xx:22:88
+ 04-18 14:30:36.024 1002 2508 2922 I bluetooth: packages/modules/Bluetooth/system/gd/hci/acl_manager/acl_scheduler.cc:168 - try_dequeue_next_operation: Pending connections is not empty; so sending next connection
+ 04-18 14:30:36.072 1002 1048 2043 I bthal.activity: CreateConnectCompleteEvent, conn_handle:00B, conn_bda: XX:XX:44:44:22:88
+ 04-18 14:30:36.606 1002 2508 2910 D bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:1985 - btif_dm_search_services_evt: New GATT over SDP UUIDs for xx:xx:xx:xx:22:88:
+ 04-18 14:30:36.606 1002 2508 2910 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:2002 - btif_dm_search_services_evt: No well known GATT services discovered
+ 04-18 14:30:36.606 1002 2508 2910 V bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:1777 - btif_dm_search_services_evt: result=0x0, services 0xc00c0062
+ 04-18 14:30:36.606 1002 2508 2910 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:1798 - btif_dm_search_services_evt: SDP finished for xx:xx:xx:xx:22:88:
+ 04-18 14:30:36.606 1002 2508 2910 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:1807 - btif_dm_search_services_evt: New UUIDs for xx:xx:xx:xx:22:88:
+ 04-18 14:30:36.606 1002 2508 2910 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:1813 - btif_dm_search_services_evt: index:0 uuid:00001101-0000-1000-8000-00805f9b34fb
+ 04-18 14:30:36.606 1002 2508 2910 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:1813 - btif_dm_search_services_evt: index:1 uuid:00001108-0000-1000-8000-00805f9b34fb
+ 04-18 14:30:36.607 1002 2508 2910 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:1813 - btif_dm_search_services_evt: index:2 uuid:0000111e-0000-1000-8000-00805f9b34fb
+ 04-18 14:30:36.607 1002 2508 2910 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:1813 - btif_dm_search_services_evt: index:3 uuid:0000110b-0000-1000-8000-00805f9b34fb
+ 04-18 14:30:36.607 1002 2508 2910 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:1813 - btif_dm_search_services_evt: index:4 uuid:0000110e-0000-1000-8000-00805f9b34fb
+ 04-18 14:30:36.607 1002 2508 2910 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:1813 - btif_dm_search_services_evt: index:7 uuid:6a24eeab-4b65-4693-986b-3c26c352264f
+ 04-18 14:30:36.607 1002 2508 2910 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:1813 - btif_dm_search_services_evt: index:8 uuid:df21fe2c-2515-4fdb-8886-f12c4d67927c
+ 04-18 14:30:36.607 1002 2508 2910 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:1863 - btif_dm_search_services_evt: SDP search done for xx:xx:xx:xx:22:88
+ 04-18 14:30:36.607 1002 2508 2910 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:1917 - btif_dm_search_services_evt: Bonding LE Audio sink - must wait for le services discovery to pass all services to java xx:xx:xx:xx:22:88
+ 04-18 14:30:39.492 1002 2508 2994 I BluetoothBondStateMachine: Bond State Change Intent:XX:XX:XX:XX:22:88 BOND_BONDING => BOND_BONDED
+ 04-18 14:30:39.999 10298 19745 19745 I BaseModuleTask: event=ModuleEvent{message=Received deceive XX:XX:XX:XX:22:88 bonded., status=SUCCESS}, callback=dxh@74d2dcb, executor=ayp@5d289a8
+
+`Due to no activity on link, we could see ACL getting terminated by l2c_link_timeout`
+
+ 04-18 14:30:40.615 1002 2508 2910 I btm_acl : disconnect_acl: Disconnecting peer:xx:xx:xx:xx:22:88 reason:HCI_ERR_PEER_USER comment:stack::l2cap::l2c_link::l2c_link_timeout All channels closed
+ 04-18 14:30:40.615 1002 2508 2922 D bluetooth: packages/modules/Bluetooth/system/main/shim/acl.cc:1047 - disconnect_classic: Disconnection initiated classic remote:xx:xx:xx:xx:22:88 handle:11
+ 04-18 14:30:40.768 1002 2508 2910 I bt_shim_hci: packages/modules/Bluetooth/system/main/shim/hci_layer.cc:304 - operator(): ISO disconnection from GD, handle: 0x0b, reason: 0x13
+
+`Wait 60000 ms for the connection event if not yet received`
+
+ 04-18 14:30:49.956 10298 19745 19745 I BaseModuleTask: event=ModuleEvent{message=Pair Step: Write account key, status=SUCCESS}, callback=dxh@74d2dcb, executor=ayp@5d289a8
+ 04-18 14:30:50.096 10298 19745 19745 I BaseModuleTask: event=ModuleEvent{message=Pair Step: FINISHED, status=SUCCESS}, callback=dxh@74d2dcb, executor=ayp@5d289a8
+ 04-18 14:30:50.098 10298 19745 26174 I BaseModuleTask: event=ModuleEvent{message=Wait 60000 ms for the connection event if not yet received., status=SUCCESS}, callback=dxh@74d2dcb, executor=ayp@5d289a8
+
+`LE ACL also disconnected due to l2c_link_timeout`
+
+`04-18 14:30:51.083 1002 2508 2910 I btm_acl : disconnect_acl: Disconnecting peer:xx:xx:xx:xx:22:88 reason:HCI_ERR_PEER_USER comment:stack::l2cap::l2c_link::l2c_link_timeout All channels closed 04-18 14:30:51.134 1002 2508 2910 I bt_shim_hci: packages/modules/Bluetooth/system/main/shim/hci_layer.cc:304 - operator(): ISO disconnection from GD, handle: 0x41, reason: 0x16 `
+
+`We could see pairing process failed because ACL was not connected`
+
+ 04-18 14:31:50.101 10298 19745 26174 I BaseModuleTask: event=ModuleEvent{message=Pairing process error. Reason: Is connected: false
+ 04-18 14:31:50.102 10298 19745 26174 I BaseModuleTask: event=ModuleEvent{message=Initial pair failed, status=FAILURE}, callback=dxh@74d2dcb, executor=ayp@5d289a8
+ 04-18 14:31:50.122 10298 19745 26174 I BaseModuleTask: event=ModuleEvent{message=Test finished, status=FAILURE}, callback=dxh@74d2dcb, executor=ayp@5d289a8
+
+`Bond was removed`
+
+ 04-18 14:31:50.133 10298 19745 26174 I FastPair: BluetoothAudioPairer: unpair: device=XX:XX:XX:XX:22:88, methodName=removeBond
+ 04-18 14:31:50.134 10298 19745 26174 I BluetoothDevice: removeBond() for device XX:XX:XX:XX:22:88 called by pid: 19745 tid: 26174
+ 04-18 14:31:50.146 1002 2508 2994 I BluetoothBondStateMachine: Bond State Change Intent:XX:XX:XX:XX:22:88 BOND_BONDED => BOND_NONE
+ 04-18 14:31:51.167 10298 19745 26174 I BaseModuleTask: event=ModuleEvent{message=Task done, status=SUCCESS}, callback=dxh@74d2dcb, executor=ayp@5d289a8
+
+\
diff --git a/Public+Key+Based+Pairing+Request+in+non+discoverable+mode.md b/Public+Key+Based+Pairing+Request+in+non+discoverable+mode.md
new file mode 100644
index 0000000..ca852aa
--- /dev/null
+++ b/Public+Key+Based+Pairing+Request+in+non+discoverable+mode.md
@@ -0,0 +1,5 @@
+# Public Key Based Pairing Request in non discoverable mode
+
+
+
+[BB2BUG-52885] [BB2][RTL8763ESE][Amazon/OSM][头戴立体声耳机][OSHA-37]Fast Pair Validator软件测试项public key based pairing request in non discoverable mode运行失败 - Jira
diff --git a/Public+key+Based+Pairing+Failed+in+Non-Discoverable+Mode+Test+Fail.md b/Public+key+Based+Pairing+Failed+in+Non-Discoverable+Mode+Test+Fail.md
new file mode 100644
index 0000000..2f31e20
--- /dev/null
+++ b/Public+key+Based+Pairing+Failed+in+Non-Discoverable+Mode+Test+Fail.md
@@ -0,0 +1,7 @@
+# Public key Based Pairing Failed in Non-Discoverable Mode Test Fail
+
+[BBPRO3BUG-28457] [BBPRO3][EVB][E Cut][3.15.0.8_0128+TestBin]Fast pair Validator APP测试， Public key Based Pairing Failed in Non-Discoverable Mode Test Fail - Jira
+
+[BB2BUG-54004] [BB2][RTL8763ESH/ROM][GMI][沃莱特/MINAMI][Harman][Pace] GFPS Public Key Based Pairing Failedin Non-Discoverable Mode测试failed - Jira
+
+\
diff --git a/Reason_+Test+fail+after+connectioning.md b/Reason_+Test+fail+after+connectioning.md
new file mode 100644
index 0000000..14adbd9
--- /dev/null
+++ b/Reason_+Test+fail+after+connectioning.md
@@ -0,0 +1,5 @@
+# Reason: Test fail after connectioning
+
+
+
+COM96_2023-03-29_17-47-45.zip
diff --git a/Reason_+device+not+found+by+EID.md b/Reason_+device+not+found+by+EID.md
new file mode 100644
index 0000000..ed0f5e8
--- /dev/null
+++ b/Reason_+device+not+found+by+EID.md
@@ -0,0 +1,19 @@
+# Reason: device not found by EID
+
+\
+
+原因是测试过程中auto power off了。
+
+MCU cfg tool 里面需要disable auto power off ，disable pairing timeout 这两个选项
+
+1)disable auto power off, disable pairing timeout
+
+**Note**:修改仅为了便于GFPS测试
+
+
+
+\
+
+COM3_2023-03-28_11-15-29.log
+
+COM3_btsnoop_2023-03-28_11-06-35.cfa
diff --git a/Reason_+wrong+value+of+'unwanted+tracking+protection+mode'+in+Hashed+Flags_disabled.md b/Reason_+wrong+value+of+'unwanted+tracking+protection+mode'+in+Hashed+Flags_disabled.md
new file mode 100644
index 0000000..2b7b31b
--- /dev/null
+++ b/Reason_+wrong+value+of+'unwanted+tracking+protection+mode'+in+Hashed+Flags_disabled.md
@@ -0,0 +1,26 @@
+# Reason: wrong value of 'unwanted tracking protection mode' in Hashed Flags:disabled
+
+[BB2BUG-47983] [BB2][RTL8763ESH/ROM][GMI][沃莱特][Harman][T530][IOS]188- [Google Finder]Unwanted tracking protection Automated test fail - Jira
+
+这个error 感觉像是手机的问题呢，请问重启手机再试试看呢？
+
+\
+
+
+
+
+
+
+
+//我们有成功设置成enable UTP mode,hash input 0x5， 但是手机端显示disable
|
+
+
+0002575 04-08#18:03:35.153 151 0051734.945 [APP] !**app_gfps_finder_generate_hash_flag: sha256 input 8B 16 71 09 5B 93 FC 00 84 9A A4 A1 F1 78 D2 4B 05 95 93 D6, sha256 output 37 69 97 22 7E 32 57 70 C7 D7 72 F0 9C 18 DA 4A 65 D7 28 BC C7 F7 31 A6 04 F9 D5 C7 1B 5E 6B 45, hash input 0x5, hash result 0x40
|
+
+
+
|
+
+
+
+
+
diff --git a/Reason_+附耳没有enable+lea+adv.md b/Reason_+附耳没有enable+lea+adv.md
new file mode 100644
index 0000000..87567eb
--- /dev/null
+++ b/Reason_+附耳没有enable+lea+adv.md
@@ -0,0 +1,60 @@
+# Reason: 附耳没有enable lea adv
+
+问题1：
+
+https://jira.realtek.com/browse/BB2RD-2516
+
+ BB2BUG-20296 - \[BB2\]\[8773ESL\]\[v3.13.0.8\]\[GFPS\]\[LE Audio\]Initial Pair播放音乐，有一只耳朵没有声音 Resolved :
+
+这边是因为切到legacy后，对端发了a2dp start 虽然是silence data, 但我们这边会建立sniffing/recovery link,并把adv停掉，主耳能连上是因为gfps的广播还开着.
+
+0001854 07-26#17:37:25.864 185 0033230.788 \[APP\] !\*\*app_audio_bt_cback: event_type 0x3107(BT_EVENT_A2DP_STREAM_START_IND)\
+0001859 07-26#17:37:25.864 190 0033231.408 \[BTM\] bt_roleswap_conn_sniffing_link: audio addr AC::3E::B1::01::16::A6, peer_addr 73::EF::66::23::15::2B, sniffing state 0x00//\
+0001864 07-26#17:37:25.864 195 0033231.690 \[BTM\] !\*\*bt_sniffing_state_setup_sniffing: event 0x0000, recovery_link_type 0//\
+0001882 07-26#17:37:25.879 213 0033235.288 \[APP\] app_bt_sniffing_start: p_link 0x002c0a4c, bt_sniffing_state 2, type 1, check_result 0, bd_addr AC::3E::B1::01::16::A6, result 1, pending_action //\
+0001908 07-26#17:37:25.879 239 0033241.020 \[BTIFMSG\]↙BTIF_MSG_LE_EXT_ADV_ENABLE_REQ(CMD:0x0189) mode:0x00(BTIF_LE_EXT_ADV_MODE_DISABLED) num_of_sets:0x01 adv_set_param: \[ adv_handle:0x01 duration:0x0000 max_ext_adv_evt:0xA5 adv_handle:0x01 duration:0x0000 max_ext_adv_evt:0x01 adv_handle:0x00 duration:0x0001 max_ext_adv_evt:0x00 adv_handle:0x00 duration:0x0000 max_ext_adv_evt:0x03\]
+
+\
+
+问题2：
+
+ BB2BUG-20764 - \[BB2\]\[8773ESL\]\[v3.13.0.8\]\[GFPS\]\[LE Audio\] Subsequent pairing只连接了一只耳朵 Resolved :
+
+耳机和phone B配对 不连附耳的原因是附耳没有enable le audio广播，请帮忙看看是否和recovery link有关
+
+0006772 07-28#16:47:20.567 036 0146460.743 \[HCI\] hci_if_confirm: buf 0x0020e043\
+0006773 07-28#16:47:20.567 037 0146461.005 \[BTM\] !\*\*ble_ext_adv_action_stop: adv_handle 1, result 0\
+0006774 07-28#16:47:20.567 038 0146461.051 \[APP\] app_lea_adv_callback: change from 1 to 0, adv_handle 1, stop_cause 1
+
+**原因是：**
+
+0008607 07-28#16:47:20.509 070 0146403.294 \[APP\] app_bt_policy_sync_b2s_connected: b2s_connected_num 2
+
+// curr mode 0(MULTI_PRO_BT_BREDR) ,event 6(MTC_TOPO_EVENT_LEGACY_CONN)
+
+0008706 07-28#16:47:20.530 169 0146423.503 \[APP\] !\*\*mtc_topology_dm: curr mode 0, event 6, bud_role 1, 2
+
+0008747 07-28#16:47:20.540 210 0146430.850 \[APP\] !\*\*mtc_topology_dm: le_conn_fg 0, edr_conn_fg 1, bis_state 0\
+0008748 07-28#16:47:20.540 211 0146430.887 \[APP\] !\*\*mtc_topology_dm: mode change 0 to 0
+
+//event 0x0002(MTC_REMOTE_SYNC_CIS_STOP)
+
+0008786 07-28#16:47:20.552 249 0146442.512 \[APP\] mtc_relay_cback: event 0x0002, status 8
+
+//event 0x8(LEA_ADV_STOP)
+
+0008789 07-28#16:47:20.552 252 0146442.648 \[APP\] !\*\*app_lea_mgr_dev_adv: event 0x8
+
+
+
+0008607 07-28#16:47:20.509 070 0146403.294 \[APP\] app_bt_policy_sync_b2s_connected: b2s_connected_num 2
+
+目前b2s link number是2， mtc_db.device.max_conn_num也是2，code就走到 mtc_terminate_cis()了
+
+
+
+**解决办法：**
+
+**MTC_MAX_LINK_NUM目前是2**
+
+将 MTC_MAX_LINK_NUM改成4
diff --git a/Reason_EATT+enable,+subsequent+pair配对主耳并未配对附耳.md b/Reason_EATT+enable,+subsequent+pair配对主耳并未配对附耳.md
new file mode 100644
index 0000000..e3b6b1d
--- /dev/null
+++ b/Reason_EATT+enable,+subsequent+pair配对主耳并未配对附耳.md
@@ -0,0 +1,7 @@
+# Reason:EATT enable, subsequent pair配对主耳并未配对附耳
+
+COM8_2023-05-24_13-08-08.log
+
+COM8_btsnoop_2023-05-24_13-08-09.cfa
+
+ BB2RD-2289 - \[GFPS LEA\] \[EATT enable\] subsequent pair fail to pair secondary bud，because EATT not support two link Closed
diff --git a/Reason_Initialpair附耳start+lea+adv的时候还未获取SIRK.md b/Reason_Initialpair附耳start+lea+adv的时候还未获取SIRK.md
new file mode 100644
index 0000000..9c0f6d0
--- /dev/null
+++ b/Reason_Initialpair附耳start+lea+adv的时候还未获取SIRK.md
@@ -0,0 +1,177 @@
+# Reason:Initialpair附耳start lea adv的时候还未获取SIRK
+
+**原因：**
+
+b2b尚未connected， 主耳的SIRK还没有relay给附耳 ，这个时候附耳就打了 gfps adv 和 le audio adv， 手机端scan到 le audio adv 然后建立了BLE link， 但是因为附耳还没有获取到正确的SIRK，所以手机端不认为主附耳是一个group。
+
+\
+
+**复现JIRA:**
+
+ BB2BUG-20294 - \[BB2\]\[8773ESL\]\[v3.13.0.8\]\[GFPS\]\[LE Audio\] 只连接一个耳机 In Progress
+
+测试版本：RTL87X3E-MCU-SDK-v3.13.0.8_20230526.zip + APP_test_bin_v3_sec_stop_gfps_hide_ui_adv_flash_4M_dualbank\
+手机：Google Pixel 7, Android 14 AC:3E:B1:01:16:A6\
+Log 0718_连接一只耳机.zip
+
+\
+耳机做factory Reset，
+
+10：06：47耳机开机engage并进入pairing mode\
+10：07：01点击手机UI上弹框配对\
+10：07：06听到一只耳朵连接的提示音\
+10：07：15听到BREDR Connected提示音，
+
+10：07：16疑似另一只耳朵的提示音\
+但10：07：37配对结束后又听到engage提示音，手机上可以看到只配对了一只耳朵\
+10：57：56建立LE Audio连接，但仍然只连接了一只耳朵
+
+\
+
+**LOG 分析：**
+
+hi tony:
+
+This Log still show phone firstly connected to secondary bud through le audio advertising, but not create BLE bond.\
+and then phone do GFPS pair with primary bud.\
+After primary bud bonded, phone still do not create bond with secondary bud.
+
+Primary bud RPA:4E:1A:3D:C1:F3:E3\
+Primary bud identity address: 73:EF:CC:15:23:01\
+Secondary bud identity address 73:EF:66:23:15:2B
+
+\
+
+//phone Bluetooth first scan le audio advertising and create BLE link with secondary bud\
+07-18 10:06:46.515 1002 2292 2401 I bt_stack: \[INFO:client.cc(1944)\] xx:xx:xx:xx:15:2b set preferred PHY to 2M
+
+//OnGattConnected Encryption error?\
+07-18 10:06:46.516 1002 2292 2401 E bt_stack: \[ERROR:client.cc(1985)\] OnGattConnected Encryption error\
+07-18 10:06:46.521 1002 2292 2600 D BtGatt.GattService: onClientConnected() connId=12, address=73:EF:66:23:15:2B, connected=true\
+07-18 10:06:46.544 1002 2292 2292 D BluetoothDatabase: setConnection: device XX:XX:XX:XX:15:2B and isA2dpDevice=false\
+07-18 10:06:46.544 1002 2292 2292 D BluetoothDatabase: Updating last connected time for device: XX:XX:XX:XX:15:2B to 190\
+07-18 10:06:46.544 1002 2292 2292 D BluetoothDatabase: updateDatabase XX:XX:XX:XX:15:2B\
+07-18 10:06:46.549 1002 2292 2600 D BluetoothGattServer: onPhyUpdate() - device=73:EF:66:23:15:2B, txPHy=2, rxPHy=2\
+07-18 10:06:46.549 1002 2292 2600 D BtGatt.GattService: onServerPhyUpdate() - connId=9, status=0\
+07-18 10:06:46.580 10177 16103 16279 I BistoWorker: bluetoothConnectionStateChanged. Action: android.bluetooth.device.action.ACL_CONNECTED
+
+\
+
+//10:06:46.613 Fast pair find primary bud\
+07-18 10:06:46.613 10166 15256 15572 I NearbyDiscovery: FastPairCache: found device XX:XX:XX:XX:F3:E3 advertising model id ecf4ac, scanMode=1 \[CONTEXT service_id=265 \]\
+07-18 10:06:46.615 10166 15256 15572 I NearbyDiscovery: FastPairCache: First time device XX:XX:XX:XX:F3:E3 with model id ecf4ac found, scanMode=1. \[CONTEXT service_id=265 \]\
+07-18 10:06:46.652 10166 15256 15572 I NearbyDiscovery: FastPairCache: Item has model ID and should trigger a halfsheet or atv_bottomsheet, XX:XX:XX:XX:F3:E3, ecf4ac, 7 \[CONTEXT service_id=265 \]\
+07-18 10:06:46.654 10166 15256 27325 I NearbyDiscovery: InitialPairingDeviceChecker: Start checking device XX:XX:XX:XX:F3:E3, modelId ecf4ac \[CONTEXT service_id=265 \]
+
+\
+
+//10:07:00.553 ACTION_FAST_PAIR_NOTIFICATION_CLICKED\
+07-18 10:07:00.553 10166 15256 15572 I NearbyDiscovery: FastPairHandler: Received action com.google.android.gms.nearby.discovery:ACTION_FAST_PAIR_NOTIFICATION_CLICKED \[CONTEXT service_id=265 \]
+
+\
+
+//10:07:00.617 FastPair: start pair\
+07-18 10:07:00.617 10166 15256 15572 I NearbyDiscovery: FastPair: start pair, item=\[type=NEARBY_DEVICE\], \[triggerId=ecf4ac\], \[id=ecf4ac\], \[title=RTL8773C-rws\], url=intent:#Intent;action=com.google.android.gms.nearby.discovery%3AACTION_MAGIC_PAIR;package=com.google.android.gms;component=com.google.android.gms/.nearby.discovery.service.DiscoveryService;end, \[targeting=false\], \[R=EVALUATION_GREAT\], \[ready=true\], \[macAddress=XX:XX:XX:XX:F3:E3\] \[CONTEXT service_id=265 \]
+
+\
+
+//10:07:28.563 10166 failed to wait for other components\
+07-18 10:07:28.563 10166 15256 27091 W FastPair: Passkey verification complete, failed to wait for other components, bonded=\[\], unbonded=\[XX:XX:XX:XX:15:2B\]
+
+\
+
+hi danni:
+
+FastPair use BluetoothLeAudio#getGroupId with XX:XX:XX:XX:F3:E3, but it returns GROUP_ID_INVALID.
+
+Before routing the issue to the ble-audio@ team, could you see if the issue can be reproduced when you "+ Pair new device" in the Bluetooth Settings page?
+
+If it's reproducible, please check your implementation on the coordinate set.
+
+If it's not reproducible, please share the logs and we will need ble-audio team to help.
+
+\
+
+
+
+
+| [bugreport-panther-UP1A.230623.006-2023-07-18-10-10-21.zip] |
+
+
+| 07-18 10:07:04.370770 15256 27091 I FastPair: Handshake success with public XX:XX:XX:XX:23:01, ble XX:XX:XX:XX:F3:E3, additional=[XX:XX:XX:XX:15:2B] |
+
+
+
+ |
+
+
+| 07-18 10:07:04.448515 15256 27091 I FastPair: BluetoothAudioPairer: createBond, device=XX:XX:XX:XX:F3:E3, transport=LE |
+
+
+| 07-18 10:07:09.740549 2292 2664 I BluetoothBondStateMachine: Bond State Change Intent:XX:XX:XX:XX:F3:E3 BOND_BONDING => BOND_BONDED |
+
+
+
+ |
+
+
+| 07-18 10:07:13.539032 2292 2600 I BluetoothPhonePolicy: clear LEA profile priority because LE audio is not allowed |
+
+
+
+ |
+
+
+| 07-18 10:07:14.670802 15256 15572 I NearbyDiscovery: FastPairController: DeviceStateManager: addCsipGroup: invalid group id, device=XX:XX:XX: |
+
+
+
+
+\
+
+可以帮忙试试看在b2b连上之后附耳再打gfps和lea的广播么？\
+看起来在b2b连上之前副耳的gfps adv和lea的adv就打起来了，并且对端通过这个广播连上了le link. 但之前有做过factory reset，b2b又还没连上，所以主耳的sirk还未送过来，两边bud的sirk还没sync.
+
+
+
+
+0001925 07-18#10:06:46.103 031 0004308.206 [ENGAGE] bud_fe_adv_start: factory_role 2
|
+
+
+0001935 07-18#10:06:46.103 041 0004309.942 [BTM] !**ble_ext_adv_action_update: adv_handle 0, adv_param_set 0, update_flags 0x3, result 0
|
+
+
+0002046 07-18#10:06:46.187 152 0004391.212 [BTM] !**ble_ext_adv_action_update: adv_handle 0, adv_param_set 1, update_flags 0x2, result 0
|
+
+
+0002136 07-18#10:06:46.200 243 0004407.416 [APP] !**app_gfps_le_device_adv_start: bud_role 2, force enter pairing mode 0【】
|
+
+
+0002140 07-18#10:06:46.200 247 0004407.734 [APP] !**app_lea_adv_start: public addr 73::EF::66::23::15::2B random addr 00::00::00::00::00::00 mode 0(LEA_ADV_MODE_PAIRING)【】
|
+
+
+0002142 07-18#10:06:46.200 249 0004407.972 [BTM] !**ble_ext_adv_mgr_send_msg: adv_handle 1, action 2(BLE_EXT_ADV_ACTION_UPDATE), param 0x3, result 0
|
+
+
+0002175 07-18#10:06:46.208 026 0004412.463 [BTM] !**ble_ext_adv_action_update: adv_handle 1, adv_param_set 0, update_flags 0x3, result 0
|
+
+
+0002296 07-18#10:06:46.271 147 0004476.787 [BTIFMSG]↗BTIF_MSG_LE_CONN_CMPL_INFO(CMD:0x012C) cause:0x0000 link_id:0x000F mtu_size:0x0017 ds_credits:0x0A own_addr_type:0x00(BTIF_LOCAL_ADDR_LE_PUBLIC) remote_addr_type:0x01(BTIF_REMOTE_ADDR_LE_RANDOM) bd_addr[79:B2:27:9B:0A:08] interval:0x0024 latency:0x0000 supv_tout:0x01F4 tx_phy:0x01(BTIF_LE_PHY_1M) rx_phy:0x00(0) csa:0x00【】
|
+
+
+0002324 07-18#10:06:46.276 175 0004480.597 [APP] !**app_lea_adv_start: public addr 73::EF::66::23::15::2B random addr 00::00::00::00::00::00 mode 0(LEA_ADV_MODE_PAIRING)
|
+
+
+0002743 07-18#10:06:46.574 082 0004784.619 [BTM] !**acl (0) link connect success, handle 0x1【】
|
+
+
+0002748 07-18#10:06:46.574 087 0004785.520 [ENGAGE] app_bt_policy_b2b_connected_add_node: bd_addr 73::EF::CC::15::23::01, p_link 0x002c09a8 0003935 07-18#10:06:47.238 182 0005426.250 [APP] !**app_gfps_le_device_adv_start: bud_role 2, force enter pairing mode 0 0003941 07-18#10:06:47.238 188 0005426.848 [APP] !**app_lea_adv_start: public addr 73::EF::66::23::15::2B random addr 00::00::00::00::00::00 mode 0(LEA_ADV_MODE_PAIRING)
|
+
+
+0004135 07-18#10:06:47.266 113 0005471.006 [PROTOCOL] !**[CSIS] csis_gen_rsi: SIRK CB D1 F0 FF D9 EC C6 3F 58 90 CB C4 D4 0E 2E 6A, PSRI A5 CC 5E EE 40 54//【】
|
+
+
+0004144 07-18#10:06:47.266 122 0005473.515 [BTM] !**ble_ext_adv_action_update: adv_handle 1, adv_param_set 1, update_flags 0x2, result 0【】
|
+
+
+
diff --git a/Reason：Observed+standard+deviation+is+too+low,+.........md b/Reason：Observed+standard+deviation+is+too+low,+.........md
new file mode 100644
index 0000000..162c997
--- /dev/null
+++ b/Reason：Observed+standard+deviation+is+too+low,+.........md
@@ -0,0 +1,36 @@
+# Reason：Observed standard deviation is too low, ........
+
+
+
+ BB2BUG-17453 - \[BB2\]\[RTL8763EF/ROM\]\[GMI\]\[沃莱特\]\[Harman\]\[T520\]: Finder测项中，finder_unwanted tracking protection测试失败 Closed
+
+\
+
+Hi Danni,\
+\
+The reason that this test fails is that the device under test rotates EID/MAC pretty much precisely every 1024 seconds (standard deviation is 0.83 seconds).\
+\
+Per spec the exact rotation time should be randomized, please refer to the "ID Rotation" section.
+
+\
+
+Hi Mark:
+
+
+
+1.Does the positive randomized time factor have a value range? Can you provide some reference ranges?
+
+2.Is the standard deviation must be greater than 0.83?
+
+\
+
++David Lazarov Can you please attach the latest version of the spec which includes the recommended randomization values?
+
+
+
+Hi Danni,
+
+
+
+1. The recommended size of the randomization window is 20% of the interval, i.e. 204 seconds. So when the device needs to compute the next time point to rotate EID/MAC, it's going to be *floor((last_rotation_time_seconds + 1024) / 1024) \* 1024 + random(0, 204). *
+2. *Standard deviation of 0.83 seconds practically means there's no randomization. We expect standard deviation to be much higher, typically 50-60 seconds, or more.*
diff --git a/Receive+unexpected+profile+connection+android.blurtooth.a2dp.profile.....md b/Receive+unexpected+profile+connection+android.blurtooth.a2dp.profile.....md
new file mode 100644
index 0000000..34fa341
--- /dev/null
+++ b/Receive+unexpected+profile+connection+android.blurtooth.a2dp.profile.....md
@@ -0,0 +1,9 @@
+# Receive unexpected profile connection android.blurtooth.a2dp.profile....
+
+
+
+\
+
+手机setting界面没有打开 bypass Bluetooth LE Audio Allowlist
+
+
diff --git a/Retroactive+Pair+Fail.md b/Retroactive+Pair+Fail.md
new file mode 100644
index 0000000..5d35be1
--- /dev/null
+++ b/Retroactive+Pair+Fail.md
@@ -0,0 +1 @@
+# Retroactive Pair Fail
diff --git a/Retroactive+Pair+test+fail--提示_Get+account+key+fail_.md b/Retroactive+Pair+test+fail--提示_Get+account+key+fail_.md
new file mode 100644
index 0000000..beef21d
--- /dev/null
+++ b/Retroactive+Pair+test+fail--提示_Get+account+key+fail_.md
@@ -0,0 +1,62 @@
+# Retroactive Pair test fail--提示"Get account key fail"
+
+**问题分析：**
+
+
+
+
+
+- [1.确保此时耳机是否在打non discoverable adv(即确保耳机不在pairing mode)](#RetroactivePairtestfail提示%22Getaccountkeyfail%22-1.确保此时耳机是否在打nondiscoverableadv(即确保耳机不在pairingmode))
+- [2.如果确认此时耳机确实不在pairing mode，手机靠近耳机试试看](#RetroactivePairtestfail提示%22Getaccountkeyfail%22-2.如果确认此时耳机确实不在pairingmode，手机靠近耳机试试看)
+- [3.如果还是不行，可能是手机端的蓝牙状态没有恢复，可以尝试重启手机，重新执行Retroactive Pair 测项](#RetroactivePairtestfail提示%22Getaccountkeyfail%22-3.如果还是不行，可能是手机端的蓝牙状态没有恢复，可以尝试重启手机，重新执行RetroactivePair测项)
+- [4 如果还是不行，执行以下操作， 注意以下操作一定要等下班之后再操作， 因为很多人都在用这个账号， 以防中间又被哪位测试同仁给打开了](#RetroactivePairtestfail提示%22Getaccountkeyfail%22-4如果还是不行，执行以下操作，注意以下操作一定要等下班之后再操作，因为很多人都在用这个账号，以防中间又被哪位测试同仁给打开了)
+- [5.如果还是有问题，请抓取耳机及手机端的log以及air log还有测试失败的截图，并且记录关键步骤以及对应的时间点](#RetroactivePairtestfail提示%22Getaccountkeyfail%22-5.如果还是有问题，请抓取耳机及手机端的log以及airlog还有测试失败的截图，并且记录关键步骤以及对应的时间点)
+
+
+
+#### 1.确保此时耳机是否在打non discoverable adv(**即确保耳机不在pairing mode**)
+
+可以通过nrf connect APP 查看一下广播数据，如果广播数据中含有 model id 信息，说明耳机是处于pairing mode 的：
+
+
+
+如果广播数据中不包含model id 信息，说明耳机并未处于pairing mode：
+
+
+
+#### 2.如果确认此时耳机确实不在pairing mode，手机靠近耳机试试看
+
+\
+
+#### 3.如果还是不行，可能是手机端的蓝牙状态没有恢复，可以尝试重启手机，重新执行Retroactive Pair 测项
+
+\
+
+#### 4 如果还是不行，执行以下操作， 注意以下操作一定要等下班之后再操作， 因为很多人都在用这个账号， 以防中间又被哪位测试同仁给打开了
+
+**Please try below steps and see if we can cleanup your geller database. Thanks!**
+
+forget headset from the Phone \
+go to "Settings -\> Google -\> Device & sharing -\> Devices -\> Saved devices" \
+toggle OFF "Automatically save devices" (this deletes all the FastPair devices from footprints) \
+wait for 3 hours for the recon sync to be triggered (it's handled by a job scheduler) \
+go to "Settings -\> Google -\> Device & sharing -\> Devices -\> Saved devices" \
+toggle ON "Automatically save devices" (since all the devices are deleted from footprints, it's empty) \
+do initial pair with a headset \
+go to "Settings -\> Google -\> Device & sharing -\> Devices -\> Saved devices" \
+see if the newly paired headset is shown in the Saved devices list
+
+#### 5.如果还是有问题，请抓取耳机及手机端的log以及air log还有测试失败的截图，并且记录关键步骤以及对应的时间点
+
+jira:
+
+ BBPRO3BUG-348 - Getting issue details... STATUS
+
+[BB2BUG-52829] [BB2][8763EWM][Tiger][GFPS][fast pair validator][fast pair測項][LE Audio] Retroactive 測試fail - Jira
+
+\
diff --git a/Retroactive+Pair之后没办法使用响铃功能.md b/Retroactive+Pair之后没办法使用响铃功能.md
new file mode 100644
index 0000000..6d97f17
--- /dev/null
+++ b/Retroactive+Pair之后没办法使用响铃功能.md
@@ -0,0 +1,55 @@
+# Retroactive Pair之后没办法使用响铃功能
+
+Retroactive_pair_no_ring_function-.mp4
+
+15:24 左右通过GFPS 弹窗进行配对，配对成功之后，setting 界面 可以看到 Find device 的UI
+
+
+
+\
+
+15:26 左右 通过Retroactive Pair 配对成功之后,setting界面看不到 Find Device的UI
+
+
+
+\
+
+对比log 发现通过GFPS 弹窗配对手机会查询 provider 的 Active Components, 但是 通过Retroactive Pair 手机好像不会查询 provider 的 Active Components
+
+
+
+\
+
+主耳
+
+COM12_2025-12-25_15-26-09.log
+
+COM12_btsnoop_2025-12-25_15-23-50.cfa
+
+附耳：
+
+COM15_2025-12-25_15-23-51.log
+
+COM15_btsnoop_2025-12-25_15-23-52.cfa
+
+\
+
+手机：
+
+bugreport-panther_beta-BP41.250916.015.A1-2025-12-25-15-27-12.zip
+
+\
+
+https://partnerissuetracker.corp.google.com/u/0/issues/471311353
+
+#### tonyysliu@google.com\google.com\> #6Dec 26, 2025 10:27AM
+
+Status: Won't Fix (Intended Behavior)
+
+Hey Danni,
+
+Sorry for the confusion, this is caused by a recent change on the Seeker side.
+
+Initial pair and subsequent pair will have the "Find device" slice, but not the retroactive pair.
+
+I am closing this as WAI, and we are planning to re-provide the "Find device" slice for the retroactive pair next year.
diff --git a/SpotUpgrade+-+Device+is+owned+by+a+different+account.md b/SpotUpgrade+-+Device+is+owned+by+a+different+account.md
new file mode 100644
index 0000000..78cc3ca
--- /dev/null
+++ b/SpotUpgrade+-+Device+is+owned+by+a+different+account.md
@@ -0,0 +1,3 @@
+# SpotUpgrade - Device is owned by a different account
+
+[BB2BUG-47679] [BB2][RTL8763ESH/ROM][GMI][沃莱特][Harman][T135]Finder测试，耳机OTA到支持Finder的版本，手机没有弹框 - Jira
diff --git a/Subsequent+pairing只连接了一只耳朵.md b/Subsequent+pairing只连接了一只耳朵.md
new file mode 100644
index 0000000..9c801af
--- /dev/null
+++ b/Subsequent+pairing只连接了一只耳朵.md
@@ -0,0 +1 @@
+# Subsequent pairing只连接了一只耳朵
diff --git a/Test+case+5_BR+reconnect+we+do+not+see+the+upgrade+notification+window+popup.md b/Test+case+5_BR+reconnect+we+do+not+see+the+upgrade+notification+window+popup.md
new file mode 100644
index 0000000..68435a7
--- /dev/null
+++ b/Test+case+5_BR+reconnect+we+do+not+see+the+upgrade+notification+window+popup.md
@@ -0,0 +1,47 @@
+# Test case 5:BR reconnect we do not see the upgrade notification window popup
+
+Hi David:
+
+‘Upgrade from Find My Accessory to FMDN’ test fail, can you help see the reason, thanks.
+
+When we restart the phone, we can see the upgrade notification popup, can you help see the reason, thanks.
+
+14:46:10 BR reconnect however we do not see the upgrade notification window popup, **why?**
+
+14:49:34 pixel phone restart
+
+14:50:48 we can see the upgrade notification window popup
+
+\
+
+结论：
+
+Test case 5测试的时候 ota完成之后如果没有finder的弹窗出来，可能是手机端还没有通过云端更新本地缓存，建议等个5到10分钟看看弹窗是否会出来，或者重启手机看看弹窗是否会出来。
+
+\
+
+\
+
+**From google:**
+
+These are the logs I'm seeing:
+
+11-18 09:42:49.360 I NearbyDiscovery: SpotUpgrade - eligibility check: b845a8 \[CONTEXT service_id=265 \]\
+11-18 09:42:49.379 I NearbyDiscovery: SpotUpgrade - eligibility check: model isn't certified for Eddystone tracking, mac=XX:XX:XX:XX:E7:19, triggerId=b845a8 \[CONTEXT service_id=265 \]
+
+//手机查到这个model id不支援finder\
+11-18 09:42:49.379 I NearbyDiscovery: SpotUpgrade - eligibility check: Device model does not support tracking \[CONTEXT service_id=265 \]
+
+
+
+The phone believes that the accessory does not support the tracking feature.
+
+It could be that the user isn't allowlisted,//我们确认model id是有支援finder功能的，所以不是这个原因
+
+//另一个原因是手机端还没有更新本地缓存，重启手机可能会执行更新的动作，应该就是这个原因了
+
+or that the feature was enabled in the console, but it takes a long time for the local cache to be updated with the new capability (a day or even more) and restarting the phone could make it update.
+
+\
+
+\
diff --git a/Test+case+5_Upgrade+from+Find+My+Accessories+to+Finder+fail.md b/Test+case+5_Upgrade+from+Find+My+Accessories+to+Finder+fail.md
new file mode 100644
index 0000000..4ee0a7b
--- /dev/null
+++ b/Test+case+5_Upgrade+from+Find+My+Accessories+to+Finder+fail.md
@@ -0,0 +1,51 @@
+# Test case 5:Upgrade from Find My Accessories to Finder fail
+
+ BTQCSZ-6275 - \[BB2\]\[C-CUT\]\[8763EF\]\[HARMAN\]\[Finder\]Find My Device Case5 fail OPEN
+
+ BB2BUG-43837 - \[BB2\]\[RTL8763EF/ROM\]\[GMI\]\[沃莱特\]\[Harman\]\[T520\]: 客户反馈Upgrade from Find My Accessories to Finder 测项fail Resolved
+
+Hi avner:
+
+We enable finder through OTA, after OTA is successful, the pairing window of finder still not pop up.
+
+We have already implemented Classic Bluetooth device specific guidelines
+
+BLE address is Random Address 4F:BA:17:EB:45:D4 (Resolvable)
+
+Can you help see the reason
+
+thanks
+
+
+
+
+
+\
+
+Hi Danni,
+
+The logs indicate that the device is owned by a different account key and therefore the upgrade notification wasn't displayed:
+
+06-20 17:41:31.423 I NearbyDiscovery: RfcommEventStreamMedium: \[XX:XX:XX:XX:E7:19\] Received EventGroup=6, EventCode=3, AdditionalDataLength=7, BytesRead=7 \[CONTEXT service_id=265 \]\
+06-20 17:41:31.425 I NearbyDiscovery: SPOT eligibility check: model is certified for Eddystone tracking, address=XX:XX:XX:XX:E7:19, triggerId=dcc22b \[CONTEXT service_id=265 \]\
+06-20 17:41:36.137 I NearbyDiscovery: SPOT eligibility check: Device is owned by a different account, address=XX:XX:XX:XX:E7:19 \[CONTEXT service_id=265 \]
+
+\
+
+Hi Avner:
+
+The logs indicate that the device is owned by a different account key and therefore the upgrade notification wasn't displayed:
+
+--》
+
+We don't know why the device be owned by different account key. Could it be that we are testing finder with a different Google account?
+
+In this case, can the finder pairing window pop up and ask user if they want to delete the old owner?
+
+thanks
+
+\
+
+hi Danni:
+
+We're currently working on a notification that warns secondary users of the device that the device owner has turned Finder tracking on. There's no way to delete the old owner, but the device can be factory reset to delete all the owners. The first user that pairs after a factory reset may be the new owner.
diff --git a/Test+case+6_+Clock+sync+fail.md b/Test+case+6_+Clock+sync+fail.md
new file mode 100644
index 0000000..242a43f
--- /dev/null
+++ b/Test+case+6_+Clock+sync+fail.md
@@ -0,0 +1,33 @@
+# Test case 6: Clock sync fail
+
+Clock sync:
+
+
+
+hi Avner:
+
+20230630 11:05 success provisioned
+
+20230630 11:42 Fully drain the battery
+
+20230703 09:00 charge the battery
+
+20230703 09:11 Turn on the power and BT connected
+
+20230703 09:30 Open Find my device app, do not see "Nearly"
+
+
+
+20230703 09:36 Tap on the device in the list, clock sync fail
+
+
+
+\
+
+Hi Danni,
+
+Thank you for the detailed information with timestamps. It's really helpful!
+
+Looks like there was an attempt to sync the clock of the device at 9:11, in which the clock was successfully read. However, there was a problem while processing the update on our end. We're investigating it. I'll keep you posted.
+
+\
diff --git a/Test+case+8-1+&&+8-2.md b/Test+case+8-1+&&+8-2.md
new file mode 100644
index 0000000..b1b6697
--- /dev/null
+++ b/Test+case+8-1+&&+8-2.md
@@ -0,0 +1,7 @@
+# Test case 8-1 && 8-2
+
+[BBPRO3BUG-27997] [BBPRO3][EVB][E Cut][SDK_Gaming_Stereo_v3.15.0.8_0128][Single][NonLEA]GFPS+Finder，Unwanted Tracking Prevention，按键GFPS Finder stop adv，耳机再次开机进配对，non owner phone搜不到设备 - Jira
+
+只有owner phone主动让设备进入 Active Unwanted Tracking Mode, non owner phone 才有可能扫到Finder的广播。
+
+设备重启之后，设备会自动退出 Active Unwanted Tracking Mode， 此时non owner phone 扫不到Finder广播是正常的。
diff --git a/Test+case+8-2_+Unwanted+Tracking+Prevention+without+network+connection注意事项.md b/Test+case+8-2_+Unwanted+Tracking+Prevention+without+network+connection注意事项.md
new file mode 100644
index 0000000..b504436
--- /dev/null
+++ b/Test+case+8-2_+Unwanted+Tracking+Prevention+without+network+connection注意事项.md
@@ -0,0 +1,43 @@
+# Test case 8-2: Unwanted Tracking Prevention without network connection注意事项
+
+
+
+\
+
+google 的答复是每个EID只能deactive一次， 也就是差不多15分钟之内只能deactive一次
+
+\
+
+**Testing steps**
+
+1. Tap on the device in the list.
+ - Device view should open, *"Last seen near you just now"* should be displayed under the name of the device.
+2. Tap the gear icon (⚙).
+ - Device settings screen should open.
+3. Tap the 3-dot menu and then tap "Inspect ...".
+ - Inspect view should open.
+4. Tap the 3-dot menu and then tap "Activate Unwanted Tracking Mode".
+ - Wait until the operation completes successfully.
+5. Turn off the owner's phone (or turn on airplane mode while Bluetooth is off) to prevent it from automatically deactivating the configuration. That should be done as quickly as possible after activating the "Unwanted Tracking Protection Mode".
+
+\
+
+注意：
+
+step4 注意事项:
+
+**设置成"Activate Unwanted Tracking Mode"之后，一定不能再设置成 "Deactivate Unwanted Tracking Mode"**
+
+**step5注意事项:**
+
+**"Activate Unwanted Tracking Mode"设置成功之后，要尽可能快的关掉蓝牙，然后打开飞行模式。**
+
+**另外:**
+
+**1.测试这个测项的时候建议用pixel7 以上的手机， 因为发现旧的pixel手机好像不会主动退出"Activate Unwanted Tracking Mode"**
+
+**2.Make sure there are no other phones in BLE range with owner's account**
+
+**3.以下红框里面的测试步骤需要特别注意一下：**
+
+
diff --git a/Total+pair+time+_+12s++or++Total+pair+time+_+15s.md b/Total+pair+time+_+12s++or++Total+pair+time+_+15s.md
new file mode 100644
index 0000000..a8cacea
--- /dev/null
+++ b/Total+pair+time+_+12s++or++Total+pair+time+_+15s.md
@@ -0,0 +1,9 @@
+# Total pair time \> 12s or Total pair time \> 15s
+
+LE audio ATT层数据交互比较耗时，Google建议是将interval改成7.5ms, 但是我们家的le audio 逻辑好像不支援，听伟东说会有频繁的断线回连
+
+[BB2BUG-52192] [BB2][D-CUT][8763EKH][Harman][T530][v3.13.2.20+Test bin] Fast pair Validator APP测试，Auto Subsequent Pairing Test Test Fail - Jira
+
+\
+
+[BBPRO3BUG-27493] [BBPRO3][EVB][E Cut][PEGA_HA_v1.0.4_20251106][27089 testbin][GFPS][FastPair][LEA phone]Auto Subsequent Pairing... 测试fail（Total pairing time 16026ms > threshold 15000ms)） - Jira
diff --git a/[legacy+GFPS][Retroactive+Pair+fail]+RFCOMM+连上之后设备端送给手机端的BLE地址不对.md b/[legacy+GFPS][Retroactive+Pair+fail]+RFCOMM+连上之后设备端送给手机端的BLE地址不对.md
new file mode 100644
index 0000000..ec40e82
--- /dev/null
+++ b/[legacy+GFPS][Retroactive+Pair+fail]+RFCOMM+连上之后设备端送给手机端的BLE地址不对.md
@@ -0,0 +1,9 @@
+# \[legacy GFPS\]\[Retroactive Pair fail\] RFCOMM 连上之后设备端送给手机端的BLE地址不对
+
+RFCOMM 连上之后， 设备端会将model id和BLE地址送给手机， 请先确认设备端送给手机的model id和BLE address 是否正确
+
+\
+
+
+
+[BB2BUG-53060] [BB2][C-CUT][8763ESE][Amazon][v3.13.3.8+test bin][GFPS]rcfg中不勾选Enter pairing state while only available device is connected的话Retroactive Pair测试则会失败 - Jira
diff --git a/analyze.py b/analyze.py
new file mode 100644
index 0000000..308741d
--- /dev/null
+++ b/analyze.py
@@ -0,0 +1,45 @@
+import os
+import email
+from email import policy
+import re
+from bs4 import BeautifulSoup
+
+def analyze_file(filepath):
+ print(f"--- Analyzing {filepath} ---")
+ with open(filepath, 'rb') as f:
+ msg = email.message_from_bytes(f.read(), policy=policy.default)
+
+ html_content = ""
+ images = []
+
+ if msg.is_multipart():
+ for part in msg.walk():
+ ctype = part.get_content_type()
+ if ctype == 'text/html':
+ html_content = part.get_payload(decode=True).decode(part.get_content_charset() or 'utf-8', errors='ignore')
+ elif ctype.startswith('image/'):
+ cloc = part.get("Content-Location")
+ cid = part.get("Content-ID")
+ images.append({"type": ctype, "location": cloc, "id": cid})
+
+ if not html_content:
+ print("No HTML found.")
+ return
+
+ soup = BeautifulSoup(html_content, 'html.parser')
+ wiki_content = soup.find(class_='wiki-content')
+ if wiki_content:
+ print("Found .wiki-content!")
+ else:
+ print("No .wiki-content found, using full body.")
+
+ img_tags = soup.find_all('img')
+ print(f"Found {len(img_tags)} img tags.")
+ for img in img_tags[:5]:
+ print(f" img src: {img.get('src')}")
+
+ print(f"Images in MHT: {len(images)}")
+ for img in images[:5]:
+ print(f" {img}")
+
+analyze_file("1. Google test group.doc")
diff --git a/auto+pair+test+fail--+_fail+to+scan+model+id+XXXX_.md b/auto+pair+test+fail--+_fail+to+scan+model+id+XXXX_.md
new file mode 100644
index 0000000..a63c985
--- /dev/null
+++ b/auto+pair+test+fail--+_fail+to+scan+model+id+XXXX_.md
@@ -0,0 +1,23 @@
+# auto pair test fail-- "fail to scan model id XXXX"
+
+
+
+原因很可能是耳机此时并未处于pairing mode
+
+可以通过nrf connect APP 查看一下广播数据，如果广播数据中含有 model id 信息，说明耳机是处于pairing mode 的：
+
+
+
+如果广播数据中不包含model id 信息，说明耳机并未处于pairing mode：
+
+
+
+需要查看耳机不在pairing mode的原因
+
+jira:
+
+ BBPRO3BUG-343 - \[BBPRO3\]\[EVB\]\[release_1220\]\[GFPS\]Auto Pairing Test Fail Preview
+
+ BB2BUG-13736 - \[fast pair validator\]\[Auto pairing test\]\[fail\]-Reason:BR local disconnected Closed
+
+ BB2BUG-17406 - \[BB2\]\[RTL8763EF/ROM\]\[GMI\]\[沃莱特\]\[Harman\]\[T520\]: GFPS测项中，auto pairing test测试失败 Closed
diff --git a/convert_docs.py b/convert_docs.py
new file mode 100644
index 0000000..9cf28ba
--- /dev/null
+++ b/convert_docs.py
@@ -0,0 +1,145 @@
+import os
+import glob
+import email
+from email import policy
+import subprocess
+import urllib.parse
+from bs4 import BeautifulSoup
+import uuid
+
+def create_dirs():
+ os.makedirs('convert_md/images', exist_ok=True)
+
+def clean_filename(name):
+ # remove .doc extension
+ if name.endswith('.doc'):
+ name = name[:-4]
+ return name
+
+def process_file(filepath):
+ print(f"Processing: {filepath}")
+ filename = os.path.basename(filepath)
+ base_name = clean_filename(filename)
+
+ with open(filepath, 'rb') as f:
+ msg = email.message_from_bytes(f.read(), policy=policy.default)
+
+ html_content = ""
+ images = {}
+
+ # Extract parts
+ if msg.is_multipart():
+ for part in msg.walk():
+ ctype = part.get_content_type()
+ if ctype == 'text/html':
+ html_content = part.get_payload(decode=True).decode(part.get_content_charset() or 'utf-8', errors='ignore')
+ elif ctype.startswith('image/') or ctype == 'application/octet-stream':
+ cloc = part.get("Content-Location")
+ cid = part.get("Content-ID")
+
+ if not cloc and not cid:
+ continue
+
+ img_data = part.get_payload(decode=True)
+ if not img_data:
+ continue
+
+ # guess extension
+ ext = 'png'
+ if img_data.startswith(b'\xff\xd8\xff'): ext = 'jpg'
+ elif img_data.startswith(b'GIF8'): ext = 'gif'
+
+ safe_img_name = f"{base_name}_{uuid.uuid4().hex[:8]}.{ext}"
+
+ img_save_path = os.path.join('convert_md', 'images', safe_img_name)
+ with open(img_save_path, 'wb') as img_f:
+ img_f.write(img_data)
+
+ if cloc:
+ images[cloc.strip()] = f"images/{safe_img_name}"
+ if cid:
+ clean_cid = cid.strip('<> \r\n')
+ images[f"cid:{clean_cid}"] = f"images/{safe_img_name}"
+
+ if not html_content:
+ print(f" No HTML content found in {filepath}. Skipping.")
+ return
+
+ # Parse HTML and fix image links
+ soup = BeautifulSoup(html_content, 'html.parser')
+
+ # Try to find the actual content wrapper to skip headers/footers
+ wiki_content = soup.find(class_='wiki-content')
+ if wiki_content:
+ content_to_convert = str(wiki_content)
+ else:
+ # fallback to body
+ body = soup.find('body')
+ content_to_convert = str(body) if body else html_content
+
+ # Re-parse to fix images in the scoped content
+ content_soup = BeautifulSoup(content_to_convert, 'html.parser')
+ for img in content_soup.find_all('img'):
+ src = img.get('src')
+ if not src:
+ continue
+
+ src = src.strip()
+
+ # Check if the src matches any of our extracted images
+ matched = False
+ for loc, new_path in images.items():
+ if src == loc or src.endswith(loc) or loc.endswith(src):
+ img['src'] = new_path
+ matched = True
+ break
+
+ if not matched:
+ unquoted = urllib.parse.unquote(src)
+ for loc, new_path in images.items():
+ if unquoted == loc or unquoted.endswith(loc) or loc.endswith(unquoted):
+ img['src'] = new_path
+ matched = True
+ break
+
+ # Remove some common Confluence boilerplate if any
+ for el in content_soup.find_all(class_=['aui-message', 'table-wrap', 'confluence-embedded-file-wrapper', 'Section1']):
+ if el.name in ('div', 'span'):
+ el.unwrap()
+
+ # Clean up img tags to just src and alt so pandoc converts them to pure markdown images
+ for img in content_soup.find_all('img'):
+ src = img.get('src', '')
+ alt = img.get('alt', '')
+ img.attrs = {'src': src, 'alt': alt}
+
+ cleaned_html = str(content_soup)
+
+ # Convert HTML to Markdown using Pandoc
+ # We use markdown_strict or gfm (GitHub Flavored Markdown) for good table support
+ try:
+ result = subprocess.run(
+ ['pandoc', '-f', 'html', '-t', 'gfm', '--wrap=none'],
+ input=cleaned_html.encode('utf-8'),
+ capture_output=True,
+ check=True
+ )
+ md_content = result.stdout.decode('utf-8')
+
+ md_filepath = os.path.join('convert_md', f"{base_name}.md")
+ with open(md_filepath, 'w', encoding='utf-8') as f:
+ f.write(md_content)
+ print(f" Successfully converted to {md_filepath}")
+
+ except subprocess.CalledProcessError as e:
+ print(f" Pandoc conversion failed for {filepath}: {e.stderr.decode('utf-8', errors='ignore')}")
+
+
+def main():
+ create_dirs()
+ files = glob.glob('*.doc')
+ for f in files:
+ process_file(f)
+
+if __name__ == '__main__':
+ main()
diff --git a/eligibility+check_+Device+model+does+not+support+tracking.md b/eligibility+check_+Device+model+does+not+support+tracking.md
new file mode 100644
index 0000000..b5e5846
--- /dev/null
+++ b/eligibility+check_+Device+model+does+not+support+tracking.md
@@ -0,0 +1,43 @@
+# eligibility check: Device model does not support tracking
+
+Hi David:
+
+‘Upgrade from Find My Accessory to FMDN’ test fail, can you help see the reason, thanks.
+
+When we restart the phone, we can see the upgrade notification popup, can you help see the reason, thanks.
+
+14:46:10 BR reconnect however we do not see the upgrade notification window popup, **why?**
+
+14:49:34 pixel phone restart
+
+14:50:48 we can see the upgrade notification window popup
+
+\
+
+结论：
+
+Test case 5测试的时候 ota完成之后如果没有finder的弹窗出来，可能是手机端还没有通过云端更新本地缓存，建议等个5到10分钟看看弹窗是否会出来，或者重启手机看看弹窗是否会出来。
+
+\
+
+\
+
+**From google:**
+
+These are the logs I'm seeing:
+
+11-18 09:42:49.360 I NearbyDiscovery: SpotUpgrade - eligibility check: b845a8 \[CONTEXT service_id=265 \]\
+11-18 09:42:49.379 I NearbyDiscovery: SpotUpgrade - eligibility check: model isn't certified for Eddystone tracking, mac=XX:XX:XX:XX:E7:19, triggerId=b845a8 \[CONTEXT service_id=265 \]
+
+//手机查到这个model id不支援finder\
+11-18 09:42:49.379 I NearbyDiscovery: SpotUpgrade - eligibility check: Device model does not support tracking \[CONTEXT service_id=265 \]
+
+
+
+The phone believes that the accessory does not support the tracking feature.
+
+It could be that the user isn't allowlisted,//我们确认model id是有支援finder功能的，所以不是这个原因
+
+//另一个原因是手机端还没有更新本地缓存，重启手机可能会执行更新的动作，应该就是这个原因了
+
+or that the feature was enabled in the console, but it takes a long time for the local cache to be updated with the new capability (a day or even more) and restarting the phone could make it update.
diff --git a/end+to+end_+A+timeout+occured+when+processing+CONNECT....md b/end+to+end_+A+timeout+occured+when+processing+CONNECT....md
new file mode 100644
index 0000000..52f47f3
--- /dev/null
+++ b/end+to+end_+A+timeout+occured+when+processing+CONNECT....md
@@ -0,0 +1,11 @@
+# end to end: A timeout occured when processing CONNECT...
+
+
+
+\
+
+
+
+\
+
+[BB2BUG-52659] [Tiger][GFPS][fast pair validator][fast pair測項] End-to-end integration 測試fail - Jira
diff --git a/fail+reason：creatbond+failed，multiple+components.md b/fail+reason：creatbond+failed，multiple+components.md
new file mode 100644
index 0000000..d988c0f
--- /dev/null
+++ b/fail+reason：creatbond+failed，multiple+components.md
@@ -0,0 +1,5 @@
+# fail reason：creatbond failed，multiple components
+
+[BBPRO3BUG-27030] [BBPRO3][EVB][E Cut][PEGA_HA_v1.0.4_20251106][24110 testbin][GFPS][FastPair][LEA phone]Auto Subsequent Pairing... 测试fail（fail reason：creatbond failed，multiple components） - Jira
+
+\
diff --git a/finder响铃失败.md b/finder响铃失败.md
new file mode 100644
index 0000000..54c7110
--- /dev/null
+++ b/finder响铃失败.md
@@ -0,0 +1,5 @@
+# finder响铃失败
+
+
+
+[BB2BUG-52959] [BB2][C-CUT][8763ESE][Amazon][v3.13.3.8+test bin]耳机无法在查找中心中响铃 - Jira
diff --git a/get+account+key+fail+--+Geller+read+failed..md b/get+account+key+fail+--+Geller+read+failed..md
new file mode 100644
index 0000000..efc9ebc
--- /dev/null
+++ b/get+account+key+fail+--+Geller+read+failed..md
@@ -0,0 +1,28 @@
+# get account key fail -- Geller read failed.
+
+https://partnerissuetracker.corp.google.com/u/0/issues/445852917
+
+This is the known issue that the testing account paired with too many providers so the footprints exceed the limit, which often happens on QA's phone. Please reset the footprints by:
+
+- Forget all the devices.
+- Go to `Settings > Google > All services > Devices > Saved devices`
+- Toggle off `Automatically saved devices`
+- Wait for about 3 hours, toggling on again.
+- Try to do the test again and see if this issue still happens.
+
+Thanks
+
+ 09-18 17:18:04.514794 10191 2524 19732 E Geller : Geller read failed.
+ 09-18 17:18:04.514794 10191 2524 19732 E Geller : com.google.android.libraries.geller.portable.GellerException: Code: UNKNOWN, Message: Result of read exceeded maximum read result size. The size of the result was: 45784832, and the maximum size is: 5000000.
+ 09-18 17:18:04.514794 10191 2524 19732 E Geller : at com.google.android.libraries.geller.portable.Geller.m(:com.google.android.gms@253731029@25.37.31 (190400-806001533):213)
+ 09-18 17:18:04.514794 10191 2524 19732 E Geller : at fioy.call(:com.google.android.gms@253731029@25.37.31 (190400-806001533):15)
+ 09-18 17:18:04.514794 10191 2524 19732 E Geller : at gfij.call(:com.google.android.gms@253731029@25.37.31 (190400-806001533):13)
+ 09-18 17:18:04.514794 10191 2524 19732 E Geller : at gnvl.a(:com.google.android.gms@253731029@25.37.31 (190400-806001533):3)
+ 09-18 17:18:04.514794 10191 2524 19732 E Geller : at gnul.run(:com.google.android.gms@253731029@25.37.31 (190400-806001533):19)
+ 09-18 17:18:04.514794 10191 2524 19732 E Geller : at gnvm.run(:com.google.android.gms@253731029@25.37.31 (190400-806001533):5)
+ 09-18 17:18:04.514794 10191 2524 19732 E Geller : at bbwy.c(:com.google.android.gms@253731029@25.37.31 (190400-806001533):50)
+ 09-18 17:18:04.514794 10191 2524 19732 E Geller : at bbwy.run(:com.google.android.gms@253731029@25.37.31 (190400-806001533):89)
+ 09-18 17:18:04.514794 10191 2524 19732 E Geller : at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1156)
+ 09-18 17:18:04.514794 10191 2524 19732 E Geller : at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:651)
+ 09-18 17:18:04.514794 10191 2524 19732 E Geller : at bccr.run(:com.google.android.gms@253731029@25.37.31 (190400-806001533):8)
+ 09-18 17:18:04.514794 10191 2524 19732 E Geller : at java.lang.Thread.run(Thread.java:1119)
diff --git a/gfps_handle_char_kbp_+failed,+result+3.md b/gfps_handle_char_kbp_+failed,+result+3.md
new file mode 100644
index 0000000..e83c208
--- /dev/null
+++ b/gfps_handle_char_kbp_+failed,+result+3.md
@@ -0,0 +1,19 @@
+# gfps_handle_char_kbp: failed, result 3
+
+**Q:**GFPS 配对失败，log提示：
+
+gfps_handle_char_kbp: failed, result 3(GFPS_WRITE_RESULT_ERROR_MESSAGE_TYPE) or
+
+ gfps_handle_char_kbp: failed, decrypt_result 3(GFPS_WRITE_RESULT_ERROR_MESSAGE_TYPE)
+
+**A:**解密出来的kbp(key based pairing request )不正确，原因是model id和public key,private key不匹配，导致解密kbp时使用的aes key不正确。
+
+请确认MCU cfg tool中填写的model id和public key,private key是不是匹配的
+
+另外需要注意：
+
+
+
+model id的注册请参考wiki：[model_id 注册](/pages/viewpage.action?pageId=157379126)
+
+\
diff --git a/images/1+Distance+测试失败_8399b64f.jpg b/images/1+Distance+测试失败_8399b64f.jpg
new file mode 100644
index 0000000..a1c0096
Binary files /dev/null and b/images/1+Distance+测试失败_8399b64f.jpg differ
diff --git a/images/1+Distance+测试失败_f9b03905.jpg b/images/1+Distance+测试失败_f9b03905.jpg
new file mode 100644
index 0000000..a1c0096
Binary files /dev/null and b/images/1+Distance+测试失败_f9b03905.jpg differ
diff --git a/images/1+Error+performing+GATT+operation_+......_7f7918d4.jpg b/images/1+Error+performing+GATT+operation_+......_7f7918d4.jpg
new file mode 100644
index 0000000..dc083f1
Binary files /dev/null and b/images/1+Error+performing+GATT+operation_+......_7f7918d4.jpg differ
diff --git a/images/1+Error+performing+GATT+operation_+......_8599f49f.jpg b/images/1+Error+performing+GATT+operation_+......_8599f49f.jpg
new file mode 100644
index 0000000..dc083f1
Binary files /dev/null and b/images/1+Error+performing+GATT+operation_+......_8599f49f.jpg differ
diff --git a/images/1+Error+performing+GATT+operation_+......_e733dd2c.jpg b/images/1+Error+performing+GATT+operation_+......_e733dd2c.jpg
new file mode 100644
index 0000000..ef00238
Binary files /dev/null and b/images/1+Error+performing+GATT+operation_+......_e733dd2c.jpg differ
diff --git a/images/1+Error+performing+GATT+operation_+......_eaf6e36f.jpg b/images/1+Error+performing+GATT+operation_+......_eaf6e36f.jpg
new file mode 100644
index 0000000..ef00238
Binary files /dev/null and b/images/1+Error+performing+GATT+operation_+......_eaf6e36f.jpg differ
diff --git a/images/1+Error+performing+GATT+operation_+fe2c1238-8366-....._02dfc104.jpg b/images/1+Error+performing+GATT+operation_+fe2c1238-8366-....._02dfc104.jpg
new file mode 100644
index 0000000..21f4058
Binary files /dev/null and b/images/1+Error+performing+GATT+operation_+fe2c1238-8366-....._02dfc104.jpg differ
diff --git a/images/1+Error+performing+GATT+operation_+fe2c1238-8366-....._3e809749.jpg b/images/1+Error+performing+GATT+operation_+fe2c1238-8366-....._3e809749.jpg
new file mode 100644
index 0000000..21f4058
Binary files /dev/null and b/images/1+Error+performing+GATT+operation_+fe2c1238-8366-....._3e809749.jpg differ
diff --git a/images/1+Error+performing+GATT+operation_+fe2c1238-8366-....._72e94583.jpg b/images/1+Error+performing+GATT+operation_+fe2c1238-8366-....._72e94583.jpg
new file mode 100644
index 0000000..58e9b8b
Binary files /dev/null and b/images/1+Error+performing+GATT+operation_+fe2c1238-8366-....._72e94583.jpg differ
diff --git a/images/1+Error+performing+GATT+operation_+fe2c1238-8366-....._8315e55a.jpg b/images/1+Error+performing+GATT+operation_+fe2c1238-8366-....._8315e55a.jpg
new file mode 100644
index 0000000..58e9b8b
Binary files /dev/null and b/images/1+Error+performing+GATT+operation_+fe2c1238-8366-....._8315e55a.jpg differ
diff --git a/images/1+Error+performing+GATT+operation_+fe2c1238-8366-....._bce86266.jpg b/images/1+Error+performing+GATT+operation_+fe2c1238-8366-....._bce86266.jpg
new file mode 100644
index 0000000..7e09350
Binary files /dev/null and b/images/1+Error+performing+GATT+operation_+fe2c1238-8366-....._bce86266.jpg differ
diff --git a/images/1+Error+performing+GATT+operation_+fe2c1238-8366-....._fd45bc79.jpg b/images/1+Error+performing+GATT+operation_+fe2c1238-8366-....._fd45bc79.jpg
new file mode 100644
index 0000000..7e09350
Binary files /dev/null and b/images/1+Error+performing+GATT+operation_+fe2c1238-8366-....._fd45bc79.jpg differ
diff --git a/images/1+Firmware+Version+with+LE+audio+conn..._87cc9936.jpg b/images/1+Firmware+Version+with+LE+audio+conn..._87cc9936.jpg
new file mode 100644
index 0000000..020dc52
Binary files /dev/null and b/images/1+Firmware+Version+with+LE+audio+conn..._87cc9936.jpg differ
diff --git a/images/1+Firmware+Version+with+LE+audio+conn..._d4c80c63.jpg b/images/1+Firmware+Version+with+LE+audio+conn..._d4c80c63.jpg
new file mode 100644
index 0000000..020dc52
Binary files /dev/null and b/images/1+Firmware+Version+with+LE+audio+conn..._d4c80c63.jpg differ
diff --git a/images/1+GFPS_Finder如何抓取手机log_18822135.jpg b/images/1+GFPS_Finder如何抓取手机log_18822135.jpg
new file mode 100644
index 0000000..4305869
Binary files /dev/null and b/images/1+GFPS_Finder如何抓取手机log_18822135.jpg differ
diff --git a/images/1+GFPS_Finder如何抓取手机log_4c16b2e7.jpg b/images/1+GFPS_Finder如何抓取手机log_4c16b2e7.jpg
new file mode 100644
index 0000000..94b9c99
Binary files /dev/null and b/images/1+GFPS_Finder如何抓取手机log_4c16b2e7.jpg differ
diff --git a/images/1+GFPS_Finder如何抓取手机log_9340c24b.jpg b/images/1+GFPS_Finder如何抓取手机log_9340c24b.jpg
new file mode 100644
index 0000000..94b9c99
Binary files /dev/null and b/images/1+GFPS_Finder如何抓取手机log_9340c24b.jpg differ
diff --git a/images/1+GFPS_Finder如何抓取手机log_b0912748.jpg b/images/1+GFPS_Finder如何抓取手机log_b0912748.jpg
new file mode 100644
index 0000000..4305869
Binary files /dev/null and b/images/1+GFPS_Finder如何抓取手机log_b0912748.jpg differ
diff --git a/images/1+Initialize+fast+pair+service+failed_347f912c.jpg b/images/1+Initialize+fast+pair+service+failed_347f912c.jpg
new file mode 100644
index 0000000..ceae61b
Binary files /dev/null and b/images/1+Initialize+fast+pair+service+failed_347f912c.jpg differ
diff --git a/images/1+Initialize+fast+pair+service+failed_4d746766.jpg b/images/1+Initialize+fast+pair+service+failed_4d746766.jpg
new file mode 100644
index 0000000..41f4408
Binary files /dev/null and b/images/1+Initialize+fast+pair+service+failed_4d746766.jpg differ
diff --git a/images/1+Initialize+fast+pair+service+failed_55b09b69.jpg b/images/1+Initialize+fast+pair+service+failed_55b09b69.jpg
new file mode 100644
index 0000000..41f4408
Binary files /dev/null and b/images/1+Initialize+fast+pair+service+failed_55b09b69.jpg differ
diff --git a/images/1+Initialize+fast+pair+service+failed_5a818bd7.jpg b/images/1+Initialize+fast+pair+service+failed_5a818bd7.jpg
new file mode 100644
index 0000000..38cefb4
Binary files /dev/null and b/images/1+Initialize+fast+pair+service+failed_5a818bd7.jpg differ
diff --git a/images/1+Initialize+fast+pair+service+failed_7cb9b11d.jpg b/images/1+Initialize+fast+pair+service+failed_7cb9b11d.jpg
new file mode 100644
index 0000000..1256bd4
Binary files /dev/null and b/images/1+Initialize+fast+pair+service+failed_7cb9b11d.jpg differ
diff --git a/images/1+Initialize+fast+pair+service+failed_850bbd55.jpg b/images/1+Initialize+fast+pair+service+failed_850bbd55.jpg
new file mode 100644
index 0000000..38cefb4
Binary files /dev/null and b/images/1+Initialize+fast+pair+service+failed_850bbd55.jpg differ
diff --git a/images/1+Initialize+fast+pair+service+failed_a45115c4.jpg b/images/1+Initialize+fast+pair+service+failed_a45115c4.jpg
new file mode 100644
index 0000000..1393633
Binary files /dev/null and b/images/1+Initialize+fast+pair+service+failed_a45115c4.jpg differ
diff --git a/images/1+Initialize+fast+pair+service+failed_aadaec3f.jpg b/images/1+Initialize+fast+pair+service+failed_aadaec3f.jpg
new file mode 100644
index 0000000..1256bd4
Binary files /dev/null and b/images/1+Initialize+fast+pair+service+failed_aadaec3f.jpg differ
diff --git a/images/1+Initialize+fast+pair+service+failed_d2f91153.jpg b/images/1+Initialize+fast+pair+service+failed_d2f91153.jpg
new file mode 100644
index 0000000..1393633
Binary files /dev/null and b/images/1+Initialize+fast+pair+service+failed_d2f91153.jpg differ
diff --git a/images/1+Initialize+fast+pair+service+failed_df95c999.jpg b/images/1+Initialize+fast+pair+service+failed_df95c999.jpg
new file mode 100644
index 0000000..ceae61b
Binary files /dev/null and b/images/1+Initialize+fast+pair+service+failed_df95c999.jpg differ
diff --git a/images/1+Pairing+process+error,+Reason_+Not+receive+UUID,+Is+connected_false_4533d028.jpg b/images/1+Pairing+process+error,+Reason_+Not+receive+UUID,+Is+connected_false_4533d028.jpg
new file mode 100644
index 0000000..3fd93cc
Binary files /dev/null and b/images/1+Pairing+process+error,+Reason_+Not+receive+UUID,+Is+connected_false_4533d028.jpg differ
diff --git a/images/1+Pairing+process+error,+Reason_+Not+receive+UUID,+Is+connected_false_7e13448c.jpg b/images/1+Pairing+process+error,+Reason_+Not+receive+UUID,+Is+connected_false_7e13448c.jpg
new file mode 100644
index 0000000..3fd93cc
Binary files /dev/null and b/images/1+Pairing+process+error,+Reason_+Not+receive+UUID,+Is+connected_false_7e13448c.jpg differ
diff --git a/images/1+Pairing+process+error,+Reason_+Not+receive+UUID,+Is+connected_false_8f817c87.jpg b/images/1+Pairing+process+error,+Reason_+Not+receive+UUID,+Is+connected_false_8f817c87.jpg
new file mode 100644
index 0000000..636153a
Binary files /dev/null and b/images/1+Pairing+process+error,+Reason_+Not+receive+UUID,+Is+connected_false_8f817c87.jpg differ
diff --git a/images/1+Pairing+process+error,+Reason_+Not+receive+UUID,+Is+connected_false_b21adeaf.jpg b/images/1+Pairing+process+error,+Reason_+Not+receive+UUID,+Is+connected_false_b21adeaf.jpg
new file mode 100644
index 0000000..636153a
Binary files /dev/null and b/images/1+Pairing+process+error,+Reason_+Not+receive+UUID,+Is+connected_false_b21adeaf.jpg differ
diff --git a/images/1+Pairing+process+error_+Reason_+Is+connected+false_93a896fd.jpg b/images/1+Pairing+process+error_+Reason_+Is+connected+false_93a896fd.jpg
new file mode 100644
index 0000000..76fc037
Binary files /dev/null and b/images/1+Pairing+process+error_+Reason_+Is+connected+false_93a896fd.jpg differ
diff --git a/images/1+Pairing+process+error_+Reason_+Is+connected+false_abcf6a4a.jpg b/images/1+Pairing+process+error_+Reason_+Is+connected+false_abcf6a4a.jpg
new file mode 100644
index 0000000..636153a
Binary files /dev/null and b/images/1+Pairing+process+error_+Reason_+Is+connected+false_abcf6a4a.jpg differ
diff --git a/images/1+Pairing+process+error_+Reason_+Is+connected+false_b118c00f.jpg b/images/1+Pairing+process+error_+Reason_+Is+connected+false_b118c00f.jpg
new file mode 100644
index 0000000..76fc037
Binary files /dev/null and b/images/1+Pairing+process+error_+Reason_+Is+connected+false_b118c00f.jpg differ
diff --git a/images/1+Pairing+process+error_+Reason_+Is+connected+false_e64c639f.jpg b/images/1+Pairing+process+error_+Reason_+Is+connected+false_e64c639f.jpg
new file mode 100644
index 0000000..636153a
Binary files /dev/null and b/images/1+Pairing+process+error_+Reason_+Is+connected+false_e64c639f.jpg differ
diff --git a/images/1+Reason_+could+not+connected_2f56140c.jpg b/images/1+Reason_+could+not+connected_2f56140c.jpg
new file mode 100644
index 0000000..7480930
Binary files /dev/null and b/images/1+Reason_+could+not+connected_2f56140c.jpg differ
diff --git a/images/1+Reason_+could+not+connected_84efa236.jpg b/images/1+Reason_+could+not+connected_84efa236.jpg
new file mode 100644
index 0000000..7480930
Binary files /dev/null and b/images/1+Reason_+could+not+connected_84efa236.jpg differ
diff --git a/images/1+Reason_+could+not+connected_d82793d7.jpg b/images/1+Reason_+could+not+connected_d82793d7.jpg
new file mode 100644
index 0000000..59a0b0a
Binary files /dev/null and b/images/1+Reason_+could+not+connected_d82793d7.jpg differ
diff --git a/images/1+Reason_+could+not+connected_fd12c263.jpg b/images/1+Reason_+could+not+connected_fd12c263.jpg
new file mode 100644
index 0000000..59a0b0a
Binary files /dev/null and b/images/1+Reason_+could+not+connected_fd12c263.jpg differ
diff --git a/images/1+legacy+CTKD+LE+功能打开之后+provision+fail_011aff79.jpg b/images/1+legacy+CTKD+LE+功能打开之后+provision+fail_011aff79.jpg
new file mode 100644
index 0000000..5429dc3
Binary files /dev/null and b/images/1+legacy+CTKD+LE+功能打开之后+provision+fail_011aff79.jpg differ
diff --git a/images/1+legacy+CTKD+LE+功能打开之后+provision+fail_96a92bc6.jpg b/images/1+legacy+CTKD+LE+功能打开之后+provision+fail_96a92bc6.jpg
new file mode 100644
index 0000000..5429dc3
Binary files /dev/null and b/images/1+legacy+CTKD+LE+功能打开之后+provision+fail_96a92bc6.jpg differ
diff --git a/images/1+手机端显示+“Could+not+authenticate”_008a28b0.jpg b/images/1+手机端显示+“Could+not+authenticate”_008a28b0.jpg
new file mode 100644
index 0000000..77aa9cc
Binary files /dev/null and b/images/1+手机端显示+“Could+not+authenticate”_008a28b0.jpg differ
diff --git a/images/1+手机端显示+“Could+not+authenticate”_d968237a.jpg b/images/1+手机端显示+“Could+not+authenticate”_d968237a.jpg
new file mode 100644
index 0000000..77aa9cc
Binary files /dev/null and b/images/1+手机端显示+“Could+not+authenticate”_d968237a.jpg differ
diff --git a/images/1+认证实验室要求认证期间弹窗的图片和名字需要隐藏_23158e93.jpg b/images/1+认证实验室要求认证期间弹窗的图片和名字需要隐藏_23158e93.jpg
new file mode 100644
index 0000000..3bfa66f
Binary files /dev/null and b/images/1+认证实验室要求认证期间弹窗的图片和名字需要隐藏_23158e93.jpg differ
diff --git a/images/1+认证实验室要求认证期间弹窗的图片和名字需要隐藏_55b282c3.jpg b/images/1+认证实验室要求认证期间弹窗的图片和名字需要隐藏_55b282c3.jpg
new file mode 100644
index 0000000..6ffebc2
Binary files /dev/null and b/images/1+认证实验室要求认证期间弹窗的图片和名字需要隐藏_55b282c3.jpg differ
diff --git a/images/1+认证实验室要求认证期间弹窗的图片和名字需要隐藏_63a28d45.jpg b/images/1+认证实验室要求认证期间弹窗的图片和名字需要隐藏_63a28d45.jpg
new file mode 100644
index 0000000..6ffebc2
Binary files /dev/null and b/images/1+认证实验室要求认证期间弹窗的图片和名字需要隐藏_63a28d45.jpg differ
diff --git a/images/1+认证实验室要求认证期间弹窗的图片和名字需要隐藏_8c24bd51.jpg b/images/1+认证实验室要求认证期间弹窗的图片和名字需要隐藏_8c24bd51.jpg
new file mode 100644
index 0000000..cbc4f66
Binary files /dev/null and b/images/1+认证实验室要求认证期间弹窗的图片和名字需要隐藏_8c24bd51.jpg differ
diff --git a/images/1+认证实验室要求认证期间弹窗的图片和名字需要隐藏_98c330cf.jpg b/images/1+认证实验室要求认证期间弹窗的图片和名字需要隐藏_98c330cf.jpg
new file mode 100644
index 0000000..3bfa66f
Binary files /dev/null and b/images/1+认证实验室要求认证期间弹窗的图片和名字需要隐藏_98c330cf.jpg differ
diff --git a/images/1+认证实验室要求认证期间弹窗的图片和名字需要隐藏_b2eba42f.jpg b/images/1+认证实验室要求认证期间弹窗的图片和名字需要隐藏_b2eba42f.jpg
new file mode 100644
index 0000000..6646127
Binary files /dev/null and b/images/1+认证实验室要求认证期间弹窗的图片和名字需要隐藏_b2eba42f.jpg differ
diff --git a/images/1+认证实验室要求认证期间弹窗的图片和名字需要隐藏_b73e0167.jpg b/images/1+认证实验室要求认证期间弹窗的图片和名字需要隐藏_b73e0167.jpg
new file mode 100644
index 0000000..cbc4f66
Binary files /dev/null and b/images/1+认证实验室要求认证期间弹窗的图片和名字需要隐藏_b73e0167.jpg differ
diff --git a/images/1+认证实验室要求认证期间弹窗的图片和名字需要隐藏_c4d38413.jpg b/images/1+认证实验室要求认证期间弹窗的图片和名字需要隐藏_c4d38413.jpg
new file mode 100644
index 0000000..6646127
Binary files /dev/null and b/images/1+认证实验室要求认证期间弹窗的图片和名字需要隐藏_c4d38413.jpg differ
diff --git a/images/1-+SUT+A打开蓝牙关闭飞行模式后，SUT+B依然能搜索到设备_e4d899e0.jpg b/images/1-+SUT+A打开蓝牙关闭飞行模式后，SUT+B依然能搜索到设备_e4d899e0.jpg
new file mode 100644
index 0000000..ceb4221
Binary files /dev/null and b/images/1-+SUT+A打开蓝牙关闭飞行模式后，SUT+B依然能搜索到设备_e4d899e0.jpg differ
diff --git a/images/1-+SUT+A打开蓝牙关闭飞行模式后，SUT+B依然能搜索到设备_e7ebe3d3.jpg b/images/1-+SUT+A打开蓝牙关闭飞行模式后，SUT+B依然能搜索到设备_e7ebe3d3.jpg
new file mode 100644
index 0000000..ceb4221
Binary files /dev/null and b/images/1-+SUT+A打开蓝牙关闭飞行模式后，SUT+B依然能搜索到设备_e7ebe3d3.jpg differ
diff --git a/images/1.+Google+test+group_1b7510c7.jpg b/images/1.+Google+test+group_1b7510c7.jpg
new file mode 100644
index 0000000..b14f26e
Binary files /dev/null and b/images/1.+Google+test+group_1b7510c7.jpg differ
diff --git a/images/1.+Google+test+group_471eafff.jpg b/images/1.+Google+test+group_471eafff.jpg
new file mode 100644
index 0000000..b14f26e
Binary files /dev/null and b/images/1.+Google+test+group_471eafff.jpg differ
diff --git a/images/1.+Google+test+group_7001d339.jpg b/images/1.+Google+test+group_7001d339.jpg
new file mode 100644
index 0000000..b646e96
Binary files /dev/null and b/images/1.+Google+test+group_7001d339.jpg differ
diff --git a/images/1.+Google+test+group_c32622ed.jpg b/images/1.+Google+test+group_c32622ed.jpg
new file mode 100644
index 0000000..b646e96
Binary files /dev/null and b/images/1.+Google+test+group_c32622ed.jpg differ
diff --git a/images/1.+initial+pair+一直显示connecting_317e2c88.jpg b/images/1.+initial+pair+一直显示connecting_317e2c88.jpg
new file mode 100644
index 0000000..847648e
Binary files /dev/null and b/images/1.+initial+pair+一直显示connecting_317e2c88.jpg differ
diff --git a/images/1.+initial+pair+一直显示connecting_37267a82.jpg b/images/1.+initial+pair+一直显示connecting_37267a82.jpg
new file mode 100644
index 0000000..847648e
Binary files /dev/null and b/images/1.+initial+pair+一直显示connecting_37267a82.jpg differ
diff --git a/images/1.+如何从手机+setting+界面判断+LEA_A2DP_HFP有connected_a3a39fa2.jpg b/images/1.+如何从手机+setting+界面判断+LEA_A2DP_HFP有connected_a3a39fa2.jpg
new file mode 100644
index 0000000..7a4548f
Binary files /dev/null and b/images/1.+如何从手机+setting+界面判断+LEA_A2DP_HFP有connected_a3a39fa2.jpg differ
diff --git a/images/1.+如何从手机+setting+界面判断+LEA_A2DP_HFP有connected_dc5ac9ac.jpg b/images/1.+如何从手机+setting+界面判断+LEA_A2DP_HFP有connected_dc5ac9ac.jpg
new file mode 100644
index 0000000..62810bc
Binary files /dev/null and b/images/1.+如何从手机+setting+界面判断+LEA_A2DP_HFP有connected_dc5ac9ac.jpg differ
diff --git a/images/1.+如何从手机+setting+界面判断+LEA_A2DP_HFP有connected_dede7884.jpg b/images/1.+如何从手机+setting+界面判断+LEA_A2DP_HFP有connected_dede7884.jpg
new file mode 100644
index 0000000..7a4548f
Binary files /dev/null and b/images/1.+如何从手机+setting+界面判断+LEA_A2DP_HFP有connected_dede7884.jpg differ
diff --git a/images/1.+如何从手机+setting+界面判断+LEA_A2DP_HFP有connected_e5fed7ed.jpg b/images/1.+如何从手机+setting+界面判断+LEA_A2DP_HFP有connected_e5fed7ed.jpg
new file mode 100644
index 0000000..62810bc
Binary files /dev/null and b/images/1.+如何从手机+setting+界面判断+LEA_A2DP_HFP有connected_e5fed7ed.jpg differ
diff --git a/images/1.+手机端点击+ring+stop，耳机端并未停止响铃_1f96683b.gif b/images/1.+手机端点击+ring+stop，耳机端并未停止响铃_1f96683b.gif
new file mode 100644
index 0000000..a3b7d9f
Binary files /dev/null and b/images/1.+手机端点击+ring+stop，耳机端并未停止响铃_1f96683b.gif differ
diff --git a/images/1.+手机端点击+ring+stop，耳机端并未停止响铃_98753375.gif b/images/1.+手机端点击+ring+stop，耳机端并未停止响铃_98753375.gif
new file mode 100644
index 0000000..a3b7d9f
Binary files /dev/null and b/images/1.+手机端点击+ring+stop，耳机端并未停止响铃_98753375.gif differ
diff --git a/images/1.+手机端点击+ring+stop，耳机端并未停止响铃_b8f07f5b.gif b/images/1.+手机端点击+ring+stop，耳机端并未停止响铃_b8f07f5b.gif
new file mode 100644
index 0000000..a3b7d9f
Binary files /dev/null and b/images/1.+手机端点击+ring+stop，耳机端并未停止响铃_b8f07f5b.gif differ
diff --git a/images/1.2.1+设备端环境搭建_01ca4548.jpg b/images/1.2.1+设备端环境搭建_01ca4548.jpg
new file mode 100644
index 0000000..dfe03bf
Binary files /dev/null and b/images/1.2.1+设备端环境搭建_01ca4548.jpg differ
diff --git a/images/1.2.1+设备端环境搭建_063fe3ac.jpg b/images/1.2.1+设备端环境搭建_063fe3ac.jpg
new file mode 100644
index 0000000..d2665a4
Binary files /dev/null and b/images/1.2.1+设备端环境搭建_063fe3ac.jpg differ
diff --git a/images/1.2.1+设备端环境搭建_0a9c75ec.jpg b/images/1.2.1+设备端环境搭建_0a9c75ec.jpg
new file mode 100644
index 0000000..78e4e1a
Binary files /dev/null and b/images/1.2.1+设备端环境搭建_0a9c75ec.jpg differ
diff --git a/images/1.2.1+设备端环境搭建_0ef42c25.jpg b/images/1.2.1+设备端环境搭建_0ef42c25.jpg
new file mode 100644
index 0000000..d2665a4
Binary files /dev/null and b/images/1.2.1+设备端环境搭建_0ef42c25.jpg differ
diff --git a/images/1.2.1+设备端环境搭建_114e6d28.jpg b/images/1.2.1+设备端环境搭建_114e6d28.jpg
new file mode 100644
index 0000000..5b92cbc
Binary files /dev/null and b/images/1.2.1+设备端环境搭建_114e6d28.jpg differ
diff --git a/images/1.2.1+设备端环境搭建_199404fc.jpg b/images/1.2.1+设备端环境搭建_199404fc.jpg
new file mode 100644
index 0000000..19538f0
Binary files /dev/null and b/images/1.2.1+设备端环境搭建_199404fc.jpg differ
diff --git a/images/1.2.1+设备端环境搭建_2b75a162.jpg b/images/1.2.1+设备端环境搭建_2b75a162.jpg
new file mode 100644
index 0000000..9af42b6
Binary files /dev/null and b/images/1.2.1+设备端环境搭建_2b75a162.jpg differ
diff --git a/images/1.2.1+设备端环境搭建_2c7a3a42.jpg b/images/1.2.1+设备端环境搭建_2c7a3a42.jpg
new file mode 100644
index 0000000..6b903d7
Binary files /dev/null and b/images/1.2.1+设备端环境搭建_2c7a3a42.jpg differ
diff --git a/images/1.2.1+设备端环境搭建_325afb1a.jpg b/images/1.2.1+设备端环境搭建_325afb1a.jpg
new file mode 100644
index 0000000..93b4195
Binary files /dev/null and b/images/1.2.1+设备端环境搭建_325afb1a.jpg differ
diff --git a/images/1.2.1+设备端环境搭建_3598ccf2.jpg b/images/1.2.1+设备端环境搭建_3598ccf2.jpg
new file mode 100644
index 0000000..013773f
Binary files /dev/null and b/images/1.2.1+设备端环境搭建_3598ccf2.jpg differ
diff --git a/images/1.2.1+设备端环境搭建_37c0eb49.jpg b/images/1.2.1+设备端环境搭建_37c0eb49.jpg
new file mode 100644
index 0000000..72ad6b6
Binary files /dev/null and b/images/1.2.1+设备端环境搭建_37c0eb49.jpg differ
diff --git a/images/1.2.1+设备端环境搭建_38478b95.jpg b/images/1.2.1+设备端环境搭建_38478b95.jpg
new file mode 100644
index 0000000..ee5cee0
Binary files /dev/null and b/images/1.2.1+设备端环境搭建_38478b95.jpg differ
diff --git a/images/1.2.1+设备端环境搭建_3a9e0c84.jpg b/images/1.2.1+设备端环境搭建_3a9e0c84.jpg
new file mode 100644
index 0000000..6c88cec
Binary files /dev/null and b/images/1.2.1+设备端环境搭建_3a9e0c84.jpg differ
diff --git a/images/1.2.1+设备端环境搭建_3bc0451e.jpg b/images/1.2.1+设备端环境搭建_3bc0451e.jpg
new file mode 100644
index 0000000..c7c022b
Binary files /dev/null and b/images/1.2.1+设备端环境搭建_3bc0451e.jpg differ
diff --git a/images/1.2.1+设备端环境搭建_4488a54d.jpg b/images/1.2.1+设备端环境搭建_4488a54d.jpg
new file mode 100644
index 0000000..6b903d7
Binary files /dev/null and b/images/1.2.1+设备端环境搭建_4488a54d.jpg differ
diff --git a/images/1.2.1+设备端环境搭建_44f49178.jpg b/images/1.2.1+设备端环境搭建_44f49178.jpg
new file mode 100644
index 0000000..1144201
Binary files /dev/null and b/images/1.2.1+设备端环境搭建_44f49178.jpg differ
diff --git a/images/1.2.1+设备端环境搭建_47b6458d.jpg b/images/1.2.1+设备端环境搭建_47b6458d.jpg
new file mode 100644
index 0000000..1699bb3
Binary files /dev/null and b/images/1.2.1+设备端环境搭建_47b6458d.jpg differ
diff --git a/images/1.2.1+设备端环境搭建_4addbd79.jpg b/images/1.2.1+设备端环境搭建_4addbd79.jpg
new file mode 100644
index 0000000..c6ad91f
Binary files /dev/null and b/images/1.2.1+设备端环境搭建_4addbd79.jpg differ
diff --git a/images/1.2.1+设备端环境搭建_4d7ac51f.jpg b/images/1.2.1+设备端环境搭建_4d7ac51f.jpg
new file mode 100644
index 0000000..9af42b6
Binary files /dev/null and b/images/1.2.1+设备端环境搭建_4d7ac51f.jpg differ
diff --git a/images/1.2.1+设备端环境搭建_508076bd.jpg b/images/1.2.1+设备端环境搭建_508076bd.jpg
new file mode 100644
index 0000000..44aa483
Binary files /dev/null and b/images/1.2.1+设备端环境搭建_508076bd.jpg differ
diff --git a/images/1.2.1+设备端环境搭建_52b1450c.jpg b/images/1.2.1+设备端环境搭建_52b1450c.jpg
new file mode 100644
index 0000000..fb2c74b
Binary files /dev/null and b/images/1.2.1+设备端环境搭建_52b1450c.jpg differ
diff --git a/images/1.2.1+设备端环境搭建_5776e5d1.jpg b/images/1.2.1+设备端环境搭建_5776e5d1.jpg
new file mode 100644
index 0000000..29508c7
Binary files /dev/null and b/images/1.2.1+设备端环境搭建_5776e5d1.jpg differ
diff --git a/images/1.2.1+设备端环境搭建_60864ced.jpg b/images/1.2.1+设备端环境搭建_60864ced.jpg
new file mode 100644
index 0000000..fb2c74b
Binary files /dev/null and b/images/1.2.1+设备端环境搭建_60864ced.jpg differ
diff --git a/images/1.2.1+设备端环境搭建_6fac7144.jpg b/images/1.2.1+设备端环境搭建_6fac7144.jpg
new file mode 100644
index 0000000..54a3952
Binary files /dev/null and b/images/1.2.1+设备端环境搭建_6fac7144.jpg differ
diff --git a/images/1.2.1+设备端环境搭建_739f0969.jpg b/images/1.2.1+设备端环境搭建_739f0969.jpg
new file mode 100644
index 0000000..19538f0
Binary files /dev/null and b/images/1.2.1+设备端环境搭建_739f0969.jpg differ
diff --git a/images/1.2.1+设备端环境搭建_80c333bc.jpg b/images/1.2.1+设备端环境搭建_80c333bc.jpg
new file mode 100644
index 0000000..db704d5
Binary files /dev/null and b/images/1.2.1+设备端环境搭建_80c333bc.jpg differ
diff --git a/images/1.2.1+设备端环境搭建_86a2749a.jpg b/images/1.2.1+设备端环境搭建_86a2749a.jpg
new file mode 100644
index 0000000..386696a
Binary files /dev/null and b/images/1.2.1+设备端环境搭建_86a2749a.jpg differ
diff --git a/images/1.2.1+设备端环境搭建_937b125d.jpg b/images/1.2.1+设备端环境搭建_937b125d.jpg
new file mode 100644
index 0000000..44aa483
Binary files /dev/null and b/images/1.2.1+设备端环境搭建_937b125d.jpg differ
diff --git a/images/1.2.1+设备端环境搭建_9754b655.jpg b/images/1.2.1+设备端环境搭建_9754b655.jpg
new file mode 100644
index 0000000..386696a
Binary files /dev/null and b/images/1.2.1+设备端环境搭建_9754b655.jpg differ
diff --git a/images/1.2.1+设备端环境搭建_9cf79166.jpg b/images/1.2.1+设备端环境搭建_9cf79166.jpg
new file mode 100644
index 0000000..78e4e1a
Binary files /dev/null and b/images/1.2.1+设备端环境搭建_9cf79166.jpg differ
diff --git a/images/1.2.1+设备端环境搭建_9e0e41b4.jpg b/images/1.2.1+设备端环境搭建_9e0e41b4.jpg
new file mode 100644
index 0000000..2eae932
Binary files /dev/null and b/images/1.2.1+设备端环境搭建_9e0e41b4.jpg differ
diff --git a/images/1.2.1+设备端环境搭建_a176185f.jpg b/images/1.2.1+设备端环境搭建_a176185f.jpg
new file mode 100644
index 0000000..013773f
Binary files /dev/null and b/images/1.2.1+设备端环境搭建_a176185f.jpg differ
diff --git a/images/1.2.1+设备端环境搭建_a5e389da.jpg b/images/1.2.1+设备端环境搭建_a5e389da.jpg
new file mode 100644
index 0000000..dfe03bf
Binary files /dev/null and b/images/1.2.1+设备端环境搭建_a5e389da.jpg differ
diff --git a/images/1.2.1+设备端环境搭建_a7b74174.jpg b/images/1.2.1+设备端环境搭建_a7b74174.jpg
new file mode 100644
index 0000000..0c2eee5
Binary files /dev/null and b/images/1.2.1+设备端环境搭建_a7b74174.jpg differ
diff --git a/images/1.2.1+设备端环境搭建_ae2a194b.jpg b/images/1.2.1+设备端环境搭建_ae2a194b.jpg
new file mode 100644
index 0000000..e5ad8ea
Binary files /dev/null and b/images/1.2.1+设备端环境搭建_ae2a194b.jpg differ
diff --git a/images/1.2.1+设备端环境搭建_ae45a914.jpg b/images/1.2.1+设备端环境搭建_ae45a914.jpg
new file mode 100644
index 0000000..54a3952
Binary files /dev/null and b/images/1.2.1+设备端环境搭建_ae45a914.jpg differ
diff --git a/images/1.2.1+设备端环境搭建_ae49306f.jpg b/images/1.2.1+设备端环境搭建_ae49306f.jpg
new file mode 100644
index 0000000..db704d5
Binary files /dev/null and b/images/1.2.1+设备端环境搭建_ae49306f.jpg differ
diff --git a/images/1.2.1+设备端环境搭建_b86dda21.jpg b/images/1.2.1+设备端环境搭建_b86dda21.jpg
new file mode 100644
index 0000000..0a86490
Binary files /dev/null and b/images/1.2.1+设备端环境搭建_b86dda21.jpg differ
diff --git a/images/1.2.1+设备端环境搭建_bcd362b7.jpg b/images/1.2.1+设备端环境搭建_bcd362b7.jpg
new file mode 100644
index 0000000..6c88cec
Binary files /dev/null and b/images/1.2.1+设备端环境搭建_bcd362b7.jpg differ
diff --git a/images/1.2.1+设备端环境搭建_bf31c91b.jpg b/images/1.2.1+设备端环境搭建_bf31c91b.jpg
new file mode 100644
index 0000000..72ad6b6
Binary files /dev/null and b/images/1.2.1+设备端环境搭建_bf31c91b.jpg differ
diff --git a/images/1.2.1+设备端环境搭建_bf9a564e.jpg b/images/1.2.1+设备端环境搭建_bf9a564e.jpg
new file mode 100644
index 0000000..1699bb3
Binary files /dev/null and b/images/1.2.1+设备端环境搭建_bf9a564e.jpg differ
diff --git a/images/1.2.1+设备端环境搭建_c67fec09.jpg b/images/1.2.1+设备端环境搭建_c67fec09.jpg
new file mode 100644
index 0000000..0a86490
Binary files /dev/null and b/images/1.2.1+设备端环境搭建_c67fec09.jpg differ
diff --git a/images/1.2.1+设备端环境搭建_d0e3475d.jpg b/images/1.2.1+设备端环境搭建_d0e3475d.jpg
new file mode 100644
index 0000000..e5ad8ea
Binary files /dev/null and b/images/1.2.1+设备端环境搭建_d0e3475d.jpg differ
diff --git a/images/1.2.1+设备端环境搭建_e2ad22ee.jpg b/images/1.2.1+设备端环境搭建_e2ad22ee.jpg
new file mode 100644
index 0000000..0c2eee5
Binary files /dev/null and b/images/1.2.1+设备端环境搭建_e2ad22ee.jpg differ
diff --git a/images/1.2.1+设备端环境搭建_e35f90ef.jpg b/images/1.2.1+设备端环境搭建_e35f90ef.jpg
new file mode 100644
index 0000000..1144201
Binary files /dev/null and b/images/1.2.1+设备端环境搭建_e35f90ef.jpg differ
diff --git a/images/1.2.1+设备端环境搭建_e897c395.jpg b/images/1.2.1+设备端环境搭建_e897c395.jpg
new file mode 100644
index 0000000..c6ad91f
Binary files /dev/null and b/images/1.2.1+设备端环境搭建_e897c395.jpg differ
diff --git a/images/1.2.1+设备端环境搭建_e93dd0c7.jpg b/images/1.2.1+设备端环境搭建_e93dd0c7.jpg
new file mode 100644
index 0000000..5b92cbc
Binary files /dev/null and b/images/1.2.1+设备端环境搭建_e93dd0c7.jpg differ
diff --git a/images/1.2.1+设备端环境搭建_eb128f16.jpg b/images/1.2.1+设备端环境搭建_eb128f16.jpg
new file mode 100644
index 0000000..29508c7
Binary files /dev/null and b/images/1.2.1+设备端环境搭建_eb128f16.jpg differ
diff --git a/images/1.2.1+设备端环境搭建_ecc9e5f4.jpg b/images/1.2.1+设备端环境搭建_ecc9e5f4.jpg
new file mode 100644
index 0000000..93b4195
Binary files /dev/null and b/images/1.2.1+设备端环境搭建_ecc9e5f4.jpg differ
diff --git a/images/1.2.1+设备端环境搭建_f1131ed7.jpg b/images/1.2.1+设备端环境搭建_f1131ed7.jpg
new file mode 100644
index 0000000..e405626
Binary files /dev/null and b/images/1.2.1+设备端环境搭建_f1131ed7.jpg differ
diff --git a/images/1.2.1+设备端环境搭建_f35a5eb2.jpg b/images/1.2.1+设备端环境搭建_f35a5eb2.jpg
new file mode 100644
index 0000000..c7c022b
Binary files /dev/null and b/images/1.2.1+设备端环境搭建_f35a5eb2.jpg differ
diff --git a/images/1.2.1+设备端环境搭建_f4a95b98.jpg b/images/1.2.1+设备端环境搭建_f4a95b98.jpg
new file mode 100644
index 0000000..ee5cee0
Binary files /dev/null and b/images/1.2.1+设备端环境搭建_f4a95b98.jpg differ
diff --git a/images/1.2.1+设备端环境搭建_f726f7a6.jpg b/images/1.2.1+设备端环境搭建_f726f7a6.jpg
new file mode 100644
index 0000000..2eae932
Binary files /dev/null and b/images/1.2.1+设备端环境搭建_f726f7a6.jpg differ
diff --git a/images/1.2.1+设备端环境搭建_f8d767c3.jpg b/images/1.2.1+设备端环境搭建_f8d767c3.jpg
new file mode 100644
index 0000000..e405626
Binary files /dev/null and b/images/1.2.1+设备端环境搭建_f8d767c3.jpg differ
diff --git a/images/1.2.2+手机端环境搭建_07ae5982.jpg b/images/1.2.2+手机端环境搭建_07ae5982.jpg
new file mode 100644
index 0000000..facfdbb
Binary files /dev/null and b/images/1.2.2+手机端环境搭建_07ae5982.jpg differ
diff --git a/images/1.2.2+手机端环境搭建_087c00a6.jpg b/images/1.2.2+手机端环境搭建_087c00a6.jpg
new file mode 100644
index 0000000..de363b1
Binary files /dev/null and b/images/1.2.2+手机端环境搭建_087c00a6.jpg differ
diff --git a/images/1.2.2+手机端环境搭建_1c55c35b.jpg b/images/1.2.2+手机端环境搭建_1c55c35b.jpg
new file mode 100644
index 0000000..b7ce1dd
Binary files /dev/null and b/images/1.2.2+手机端环境搭建_1c55c35b.jpg differ
diff --git a/images/1.2.2+手机端环境搭建_289ffa79.jpg b/images/1.2.2+手机端环境搭建_289ffa79.jpg
new file mode 100644
index 0000000..b84908a
Binary files /dev/null and b/images/1.2.2+手机端环境搭建_289ffa79.jpg differ
diff --git a/images/1.2.2+手机端环境搭建_36e29814.jpg b/images/1.2.2+手机端环境搭建_36e29814.jpg
new file mode 100644
index 0000000..facfdbb
Binary files /dev/null and b/images/1.2.2+手机端环境搭建_36e29814.jpg differ
diff --git a/images/1.2.2+手机端环境搭建_38156398.jpg b/images/1.2.2+手机端环境搭建_38156398.jpg
new file mode 100644
index 0000000..2a1ff26
Binary files /dev/null and b/images/1.2.2+手机端环境搭建_38156398.jpg differ
diff --git a/images/1.2.2+手机端环境搭建_3a6eb1d1.jpg b/images/1.2.2+手机端环境搭建_3a6eb1d1.jpg
new file mode 100644
index 0000000..631b957
Binary files /dev/null and b/images/1.2.2+手机端环境搭建_3a6eb1d1.jpg differ
diff --git a/images/1.2.2+手机端环境搭建_3d0c722b.jpg b/images/1.2.2+手机端环境搭建_3d0c722b.jpg
new file mode 100644
index 0000000..6d2af57
Binary files /dev/null and b/images/1.2.2+手机端环境搭建_3d0c722b.jpg differ
diff --git a/images/1.2.2+手机端环境搭建_3d7ae840.jpg b/images/1.2.2+手机端环境搭建_3d7ae840.jpg
new file mode 100644
index 0000000..2a1ff26
Binary files /dev/null and b/images/1.2.2+手机端环境搭建_3d7ae840.jpg differ
diff --git a/images/1.2.2+手机端环境搭建_41c6857f.jpg b/images/1.2.2+手机端环境搭建_41c6857f.jpg
new file mode 100644
index 0000000..9ed6549
Binary files /dev/null and b/images/1.2.2+手机端环境搭建_41c6857f.jpg differ
diff --git a/images/1.2.2+手机端环境搭建_52fcba79.jpg b/images/1.2.2+手机端环境搭建_52fcba79.jpg
new file mode 100644
index 0000000..15ae088
Binary files /dev/null and b/images/1.2.2+手机端环境搭建_52fcba79.jpg differ
diff --git a/images/1.2.2+手机端环境搭建_5b074269.jpg b/images/1.2.2+手机端环境搭建_5b074269.jpg
new file mode 100644
index 0000000..3742274
Binary files /dev/null and b/images/1.2.2+手机端环境搭建_5b074269.jpg differ
diff --git a/images/1.2.2+手机端环境搭建_6ee80d18.jpg b/images/1.2.2+手机端环境搭建_6ee80d18.jpg
new file mode 100644
index 0000000..302ade0
Binary files /dev/null and b/images/1.2.2+手机端环境搭建_6ee80d18.jpg differ
diff --git a/images/1.2.2+手机端环境搭建_78ed5e9c.jpg b/images/1.2.2+手机端环境搭建_78ed5e9c.jpg
new file mode 100644
index 0000000..64d2e42
Binary files /dev/null and b/images/1.2.2+手机端环境搭建_78ed5e9c.jpg differ
diff --git a/images/1.2.2+手机端环境搭建_7b36489c.jpg b/images/1.2.2+手机端环境搭建_7b36489c.jpg
new file mode 100644
index 0000000..4c1855f
Binary files /dev/null and b/images/1.2.2+手机端环境搭建_7b36489c.jpg differ
diff --git a/images/1.2.2+手机端环境搭建_7b63a76b.jpg b/images/1.2.2+手机端环境搭建_7b63a76b.jpg
new file mode 100644
index 0000000..2b46edf
Binary files /dev/null and b/images/1.2.2+手机端环境搭建_7b63a76b.jpg differ
diff --git a/images/1.2.2+手机端环境搭建_7e63d95b.jpg b/images/1.2.2+手机端环境搭建_7e63d95b.jpg
new file mode 100644
index 0000000..c3def5e
Binary files /dev/null and b/images/1.2.2+手机端环境搭建_7e63d95b.jpg differ
diff --git a/images/1.2.2+手机端环境搭建_80004376.jpg b/images/1.2.2+手机端环境搭建_80004376.jpg
new file mode 100644
index 0000000..302ade0
Binary files /dev/null and b/images/1.2.2+手机端环境搭建_80004376.jpg differ
diff --git a/images/1.2.2+手机端环境搭建_8338f44a.jpg b/images/1.2.2+手机端环境搭建_8338f44a.jpg
new file mode 100644
index 0000000..3f84e71
Binary files /dev/null and b/images/1.2.2+手机端环境搭建_8338f44a.jpg differ
diff --git a/images/1.2.2+手机端环境搭建_8acf2c88.jpg b/images/1.2.2+手机端环境搭建_8acf2c88.jpg
new file mode 100644
index 0000000..1dda003
Binary files /dev/null and b/images/1.2.2+手机端环境搭建_8acf2c88.jpg differ
diff --git a/images/1.2.2+手机端环境搭建_8fb751f2.jpg b/images/1.2.2+手机端环境搭建_8fb751f2.jpg
new file mode 100644
index 0000000..1dda003
Binary files /dev/null and b/images/1.2.2+手机端环境搭建_8fb751f2.jpg differ
diff --git a/images/1.2.2+手机端环境搭建_90c0ac65.jpg b/images/1.2.2+手机端环境搭建_90c0ac65.jpg
new file mode 100644
index 0000000..631b957
Binary files /dev/null and b/images/1.2.2+手机端环境搭建_90c0ac65.jpg differ
diff --git a/images/1.2.2+手机端环境搭建_90daad55.jpg b/images/1.2.2+手机端环境搭建_90daad55.jpg
new file mode 100644
index 0000000..3f84e71
Binary files /dev/null and b/images/1.2.2+手机端环境搭建_90daad55.jpg differ
diff --git a/images/1.2.2+手机端环境搭建_94b42af3.jpg b/images/1.2.2+手机端环境搭建_94b42af3.jpg
new file mode 100644
index 0000000..6d2af57
Binary files /dev/null and b/images/1.2.2+手机端环境搭建_94b42af3.jpg differ
diff --git a/images/1.2.2+手机端环境搭建_9e5acce8.jpg b/images/1.2.2+手机端环境搭建_9e5acce8.jpg
new file mode 100644
index 0000000..b7ce1dd
Binary files /dev/null and b/images/1.2.2+手机端环境搭建_9e5acce8.jpg differ
diff --git a/images/1.2.2+手机端环境搭建_a39c7e0b.jpg b/images/1.2.2+手机端环境搭建_a39c7e0b.jpg
new file mode 100644
index 0000000..b447433
Binary files /dev/null and b/images/1.2.2+手机端环境搭建_a39c7e0b.jpg differ
diff --git a/images/1.2.2+手机端环境搭建_aad79b43.jpg b/images/1.2.2+手机端环境搭建_aad79b43.jpg
new file mode 100644
index 0000000..c0e85e0
Binary files /dev/null and b/images/1.2.2+手机端环境搭建_aad79b43.jpg differ
diff --git a/images/1.2.2+手机端环境搭建_aebeee88.jpg b/images/1.2.2+手机端环境搭建_aebeee88.jpg
new file mode 100644
index 0000000..9ed6549
Binary files /dev/null and b/images/1.2.2+手机端环境搭建_aebeee88.jpg differ
diff --git a/images/1.2.2+手机端环境搭建_b4d0b912.jpg b/images/1.2.2+手机端环境搭建_b4d0b912.jpg
new file mode 100644
index 0000000..15ae088
Binary files /dev/null and b/images/1.2.2+手机端环境搭建_b4d0b912.jpg differ
diff --git a/images/1.2.2+手机端环境搭建_be1e6bd2.jpg b/images/1.2.2+手机端环境搭建_be1e6bd2.jpg
new file mode 100644
index 0000000..64d2e42
Binary files /dev/null and b/images/1.2.2+手机端环境搭建_be1e6bd2.jpg differ
diff --git a/images/1.2.2+手机端环境搭建_c1264833.jpg b/images/1.2.2+手机端环境搭建_c1264833.jpg
new file mode 100644
index 0000000..de363b1
Binary files /dev/null and b/images/1.2.2+手机端环境搭建_c1264833.jpg differ
diff --git a/images/1.2.2+手机端环境搭建_c50eee0a.jpg b/images/1.2.2+手机端环境搭建_c50eee0a.jpg
new file mode 100644
index 0000000..2b46edf
Binary files /dev/null and b/images/1.2.2+手机端环境搭建_c50eee0a.jpg differ
diff --git a/images/1.2.2+手机端环境搭建_cd375b21.jpg b/images/1.2.2+手机端环境搭建_cd375b21.jpg
new file mode 100644
index 0000000..3742274
Binary files /dev/null and b/images/1.2.2+手机端环境搭建_cd375b21.jpg differ
diff --git a/images/1.2.2+手机端环境搭建_ceaa46d9.jpg b/images/1.2.2+手机端环境搭建_ceaa46d9.jpg
new file mode 100644
index 0000000..c3def5e
Binary files /dev/null and b/images/1.2.2+手机端环境搭建_ceaa46d9.jpg differ
diff --git a/images/1.2.2+手机端环境搭建_d1e1bfac.jpg b/images/1.2.2+手机端环境搭建_d1e1bfac.jpg
new file mode 100644
index 0000000..c0e85e0
Binary files /dev/null and b/images/1.2.2+手机端环境搭建_d1e1bfac.jpg differ
diff --git a/images/1.2.2+手机端环境搭建_d60f9bb7.jpg b/images/1.2.2+手机端环境搭建_d60f9bb7.jpg
new file mode 100644
index 0000000..b84908a
Binary files /dev/null and b/images/1.2.2+手机端环境搭建_d60f9bb7.jpg differ
diff --git a/images/1.2.2+手机端环境搭建_e2ba0ca3.jpg b/images/1.2.2+手机端环境搭建_e2ba0ca3.jpg
new file mode 100644
index 0000000..b447433
Binary files /dev/null and b/images/1.2.2+手机端环境搭建_e2ba0ca3.jpg differ
diff --git a/images/1.2.2+手机端环境搭建_fb390322.jpg b/images/1.2.2+手机端环境搭建_fb390322.jpg
new file mode 100644
index 0000000..4c1855f
Binary files /dev/null and b/images/1.2.2+手机端环境搭建_fb390322.jpg differ
diff --git a/images/1.2.3+Fast+Pair+Validator+环境搭建_08158b19.jpg b/images/1.2.3+Fast+Pair+Validator+环境搭建_08158b19.jpg
new file mode 100644
index 0000000..4c1855f
Binary files /dev/null and b/images/1.2.3+Fast+Pair+Validator+环境搭建_08158b19.jpg differ
diff --git a/images/1.2.3+Fast+Pair+Validator+环境搭建_092d8533.jpg b/images/1.2.3+Fast+Pair+Validator+环境搭建_092d8533.jpg
new file mode 100644
index 0000000..b447433
Binary files /dev/null and b/images/1.2.3+Fast+Pair+Validator+环境搭建_092d8533.jpg differ
diff --git a/images/1.2.3+Fast+Pair+Validator+环境搭建_160188cd.jpg b/images/1.2.3+Fast+Pair+Validator+环境搭建_160188cd.jpg
new file mode 100644
index 0000000..64d2e42
Binary files /dev/null and b/images/1.2.3+Fast+Pair+Validator+环境搭建_160188cd.jpg differ
diff --git a/images/1.2.3+Fast+Pair+Validator+环境搭建_1b5cc348.jpg b/images/1.2.3+Fast+Pair+Validator+环境搭建_1b5cc348.jpg
new file mode 100644
index 0000000..7dcfef7
Binary files /dev/null and b/images/1.2.3+Fast+Pair+Validator+环境搭建_1b5cc348.jpg differ
diff --git a/images/1.2.3+Fast+Pair+Validator+环境搭建_1c95b518.jpg b/images/1.2.3+Fast+Pair+Validator+环境搭建_1c95b518.jpg
new file mode 100644
index 0000000..302ade0
Binary files /dev/null and b/images/1.2.3+Fast+Pair+Validator+环境搭建_1c95b518.jpg differ
diff --git a/images/1.2.3+Fast+Pair+Validator+环境搭建_1e158034.jpg b/images/1.2.3+Fast+Pair+Validator+环境搭建_1e158034.jpg
new file mode 100644
index 0000000..6a7bd33
Binary files /dev/null and b/images/1.2.3+Fast+Pair+Validator+环境搭建_1e158034.jpg differ
diff --git a/images/1.2.3+Fast+Pair+Validator+环境搭建_1fe8ca67.jpg b/images/1.2.3+Fast+Pair+Validator+环境搭建_1fe8ca67.jpg
new file mode 100644
index 0000000..6d2af57
Binary files /dev/null and b/images/1.2.3+Fast+Pair+Validator+环境搭建_1fe8ca67.jpg differ
diff --git a/images/1.2.3+Fast+Pair+Validator+环境搭建_2b92b5e2.jpg b/images/1.2.3+Fast+Pair+Validator+环境搭建_2b92b5e2.jpg
new file mode 100644
index 0000000..6d2af57
Binary files /dev/null and b/images/1.2.3+Fast+Pair+Validator+环境搭建_2b92b5e2.jpg differ
diff --git a/images/1.2.3+Fast+Pair+Validator+环境搭建_3d9fde26.jpg b/images/1.2.3+Fast+Pair+Validator+环境搭建_3d9fde26.jpg
new file mode 100644
index 0000000..facfdbb
Binary files /dev/null and b/images/1.2.3+Fast+Pair+Validator+环境搭建_3d9fde26.jpg differ
diff --git a/images/1.2.3+Fast+Pair+Validator+环境搭建_405cea99.jpg b/images/1.2.3+Fast+Pair+Validator+环境搭建_405cea99.jpg
new file mode 100644
index 0000000..c0e85e0
Binary files /dev/null and b/images/1.2.3+Fast+Pair+Validator+环境搭建_405cea99.jpg differ
diff --git a/images/1.2.3+Fast+Pair+Validator+环境搭建_4092d791.jpg b/images/1.2.3+Fast+Pair+Validator+环境搭建_4092d791.jpg
new file mode 100644
index 0000000..c5bbb74
Binary files /dev/null and b/images/1.2.3+Fast+Pair+Validator+环境搭建_4092d791.jpg differ
diff --git a/images/1.2.3+Fast+Pair+Validator+环境搭建_43610ad1.jpg b/images/1.2.3+Fast+Pair+Validator+环境搭建_43610ad1.jpg
new file mode 100644
index 0000000..1dda003
Binary files /dev/null and b/images/1.2.3+Fast+Pair+Validator+环境搭建_43610ad1.jpg differ
diff --git a/images/1.2.3+Fast+Pair+Validator+环境搭建_47eeaefd.jpg b/images/1.2.3+Fast+Pair+Validator+环境搭建_47eeaefd.jpg
new file mode 100644
index 0000000..ab658c5
Binary files /dev/null and b/images/1.2.3+Fast+Pair+Validator+环境搭建_47eeaefd.jpg differ
diff --git a/images/1.2.3+Fast+Pair+Validator+环境搭建_50924099.jpg b/images/1.2.3+Fast+Pair+Validator+环境搭建_50924099.jpg
new file mode 100644
index 0000000..6a7bd33
Binary files /dev/null and b/images/1.2.3+Fast+Pair+Validator+环境搭建_50924099.jpg differ
diff --git a/images/1.2.3+Fast+Pair+Validator+环境搭建_54bd55b8.jpg b/images/1.2.3+Fast+Pair+Validator+环境搭建_54bd55b8.jpg
new file mode 100644
index 0000000..2b46edf
Binary files /dev/null and b/images/1.2.3+Fast+Pair+Validator+环境搭建_54bd55b8.jpg differ
diff --git a/images/1.2.3+Fast+Pair+Validator+环境搭建_55741080.jpg b/images/1.2.3+Fast+Pair+Validator+环境搭建_55741080.jpg
new file mode 100644
index 0000000..b7ce1dd
Binary files /dev/null and b/images/1.2.3+Fast+Pair+Validator+环境搭建_55741080.jpg differ
diff --git a/images/1.2.3+Fast+Pair+Validator+环境搭建_575814a4.jpg b/images/1.2.3+Fast+Pair+Validator+环境搭建_575814a4.jpg
new file mode 100644
index 0000000..c3def5e
Binary files /dev/null and b/images/1.2.3+Fast+Pair+Validator+环境搭建_575814a4.jpg differ
diff --git a/images/1.2.3+Fast+Pair+Validator+环境搭建_5927b931.jpg b/images/1.2.3+Fast+Pair+Validator+环境搭建_5927b931.jpg
new file mode 100644
index 0000000..6ec45ec
Binary files /dev/null and b/images/1.2.3+Fast+Pair+Validator+环境搭建_5927b931.jpg differ
diff --git a/images/1.2.3+Fast+Pair+Validator+环境搭建_5dbc9d7c.jpg b/images/1.2.3+Fast+Pair+Validator+环境搭建_5dbc9d7c.jpg
new file mode 100644
index 0000000..631b957
Binary files /dev/null and b/images/1.2.3+Fast+Pair+Validator+环境搭建_5dbc9d7c.jpg differ
diff --git a/images/1.2.3+Fast+Pair+Validator+环境搭建_648f64f2.jpg b/images/1.2.3+Fast+Pair+Validator+环境搭建_648f64f2.jpg
new file mode 100644
index 0000000..2a1ff26
Binary files /dev/null and b/images/1.2.3+Fast+Pair+Validator+环境搭建_648f64f2.jpg differ
diff --git a/images/1.2.3+Fast+Pair+Validator+环境搭建_6809daba.jpg b/images/1.2.3+Fast+Pair+Validator+环境搭建_6809daba.jpg
new file mode 100644
index 0000000..9ed6549
Binary files /dev/null and b/images/1.2.3+Fast+Pair+Validator+环境搭建_6809daba.jpg differ
diff --git a/images/1.2.3+Fast+Pair+Validator+环境搭建_6caa985d.jpg b/images/1.2.3+Fast+Pair+Validator+环境搭建_6caa985d.jpg
new file mode 100644
index 0000000..b84908a
Binary files /dev/null and b/images/1.2.3+Fast+Pair+Validator+环境搭建_6caa985d.jpg differ
diff --git a/images/1.2.3+Fast+Pair+Validator+环境搭建_6fde08a4.jpg b/images/1.2.3+Fast+Pair+Validator+环境搭建_6fde08a4.jpg
new file mode 100644
index 0000000..2a1ff26
Binary files /dev/null and b/images/1.2.3+Fast+Pair+Validator+环境搭建_6fde08a4.jpg differ
diff --git a/images/1.2.3+Fast+Pair+Validator+环境搭建_71878eb9.jpg b/images/1.2.3+Fast+Pair+Validator+环境搭建_71878eb9.jpg
new file mode 100644
index 0000000..c3def5e
Binary files /dev/null and b/images/1.2.3+Fast+Pair+Validator+环境搭建_71878eb9.jpg differ
diff --git a/images/1.2.3+Fast+Pair+Validator+环境搭建_78b700c6.jpg b/images/1.2.3+Fast+Pair+Validator+环境搭建_78b700c6.jpg
new file mode 100644
index 0000000..c7ccda3
Binary files /dev/null and b/images/1.2.3+Fast+Pair+Validator+环境搭建_78b700c6.jpg differ
diff --git a/images/1.2.3+Fast+Pair+Validator+环境搭建_7a6bd18a.jpg b/images/1.2.3+Fast+Pair+Validator+环境搭建_7a6bd18a.jpg
new file mode 100644
index 0000000..071d3f9
Binary files /dev/null and b/images/1.2.3+Fast+Pair+Validator+环境搭建_7a6bd18a.jpg differ
diff --git a/images/1.2.3+Fast+Pair+Validator+环境搭建_7d8e5009.jpg b/images/1.2.3+Fast+Pair+Validator+环境搭建_7d8e5009.jpg
new file mode 100644
index 0000000..64d2e42
Binary files /dev/null and b/images/1.2.3+Fast+Pair+Validator+环境搭建_7d8e5009.jpg differ
diff --git a/images/1.2.3+Fast+Pair+Validator+环境搭建_8110ca22.jpg b/images/1.2.3+Fast+Pair+Validator+环境搭建_8110ca22.jpg
new file mode 100644
index 0000000..6ec45ec
Binary files /dev/null and b/images/1.2.3+Fast+Pair+Validator+环境搭建_8110ca22.jpg differ
diff --git a/images/1.2.3+Fast+Pair+Validator+环境搭建_8166a972.jpg b/images/1.2.3+Fast+Pair+Validator+环境搭建_8166a972.jpg
new file mode 100644
index 0000000..1dda003
Binary files /dev/null and b/images/1.2.3+Fast+Pair+Validator+环境搭建_8166a972.jpg differ
diff --git a/images/1.2.3+Fast+Pair+Validator+环境搭建_821911a5.jpg b/images/1.2.3+Fast+Pair+Validator+环境搭建_821911a5.jpg
new file mode 100644
index 0000000..ab658c5
Binary files /dev/null and b/images/1.2.3+Fast+Pair+Validator+环境搭建_821911a5.jpg differ
diff --git a/images/1.2.3+Fast+Pair+Validator+环境搭建_8cd5759f.jpg b/images/1.2.3+Fast+Pair+Validator+环境搭建_8cd5759f.jpg
new file mode 100644
index 0000000..facfdbb
Binary files /dev/null and b/images/1.2.3+Fast+Pair+Validator+环境搭建_8cd5759f.jpg differ
diff --git a/images/1.2.3+Fast+Pair+Validator+环境搭建_98dd9919.jpg b/images/1.2.3+Fast+Pair+Validator+环境搭建_98dd9919.jpg
new file mode 100644
index 0000000..4c1855f
Binary files /dev/null and b/images/1.2.3+Fast+Pair+Validator+环境搭建_98dd9919.jpg differ
diff --git a/images/1.2.3+Fast+Pair+Validator+环境搭建_9b3bcd49.jpg b/images/1.2.3+Fast+Pair+Validator+环境搭建_9b3bcd49.jpg
new file mode 100644
index 0000000..15ae088
Binary files /dev/null and b/images/1.2.3+Fast+Pair+Validator+环境搭建_9b3bcd49.jpg differ
diff --git a/images/1.2.3+Fast+Pair+Validator+环境搭建_a315c9c3.jpg b/images/1.2.3+Fast+Pair+Validator+环境搭建_a315c9c3.jpg
new file mode 100644
index 0000000..7dcfef7
Binary files /dev/null and b/images/1.2.3+Fast+Pair+Validator+环境搭建_a315c9c3.jpg differ
diff --git a/images/1.2.3+Fast+Pair+Validator+环境搭建_a4cb2863.jpg b/images/1.2.3+Fast+Pair+Validator+环境搭建_a4cb2863.jpg
new file mode 100644
index 0000000..c7ccda3
Binary files /dev/null and b/images/1.2.3+Fast+Pair+Validator+环境搭建_a4cb2863.jpg differ
diff --git a/images/1.2.3+Fast+Pair+Validator+环境搭建_a914d40f.jpg b/images/1.2.3+Fast+Pair+Validator+环境搭建_a914d40f.jpg
new file mode 100644
index 0000000..b447433
Binary files /dev/null and b/images/1.2.3+Fast+Pair+Validator+环境搭建_a914d40f.jpg differ
diff --git a/images/1.2.3+Fast+Pair+Validator+环境搭建_ac87ca72.jpg b/images/1.2.3+Fast+Pair+Validator+环境搭建_ac87ca72.jpg
new file mode 100644
index 0000000..b84908a
Binary files /dev/null and b/images/1.2.3+Fast+Pair+Validator+环境搭建_ac87ca72.jpg differ
diff --git a/images/1.2.3+Fast+Pair+Validator+环境搭建_b3f1b8f4.jpg b/images/1.2.3+Fast+Pair+Validator+环境搭建_b3f1b8f4.jpg
new file mode 100644
index 0000000..9ed6549
Binary files /dev/null and b/images/1.2.3+Fast+Pair+Validator+环境搭建_b3f1b8f4.jpg differ
diff --git a/images/1.2.3+Fast+Pair+Validator+环境搭建_be5ea8c1.jpg b/images/1.2.3+Fast+Pair+Validator+环境搭建_be5ea8c1.jpg
new file mode 100644
index 0000000..15ae088
Binary files /dev/null and b/images/1.2.3+Fast+Pair+Validator+环境搭建_be5ea8c1.jpg differ
diff --git a/images/1.2.3+Fast+Pair+Validator+环境搭建_be60a165.jpg b/images/1.2.3+Fast+Pair+Validator+环境搭建_be60a165.jpg
new file mode 100644
index 0000000..b4477df
Binary files /dev/null and b/images/1.2.3+Fast+Pair+Validator+环境搭建_be60a165.jpg differ
diff --git a/images/1.2.3+Fast+Pair+Validator+环境搭建_bef4026e.jpg b/images/1.2.3+Fast+Pair+Validator+环境搭建_bef4026e.jpg
new file mode 100644
index 0000000..503cb7d
Binary files /dev/null and b/images/1.2.3+Fast+Pair+Validator+环境搭建_bef4026e.jpg differ
diff --git a/images/1.2.3+Fast+Pair+Validator+环境搭建_bffda93e.jpg b/images/1.2.3+Fast+Pair+Validator+环境搭建_bffda93e.jpg
new file mode 100644
index 0000000..b4477df
Binary files /dev/null and b/images/1.2.3+Fast+Pair+Validator+环境搭建_bffda93e.jpg differ
diff --git a/images/1.2.3+Fast+Pair+Validator+环境搭建_c0cb26a7.jpg b/images/1.2.3+Fast+Pair+Validator+环境搭建_c0cb26a7.jpg
new file mode 100644
index 0000000..631b957
Binary files /dev/null and b/images/1.2.3+Fast+Pair+Validator+环境搭建_c0cb26a7.jpg differ
diff --git a/images/1.2.3+Fast+Pair+Validator+环境搭建_c708d767.jpg b/images/1.2.3+Fast+Pair+Validator+环境搭建_c708d767.jpg
new file mode 100644
index 0000000..b7ce1dd
Binary files /dev/null and b/images/1.2.3+Fast+Pair+Validator+环境搭建_c708d767.jpg differ
diff --git a/images/1.2.3+Fast+Pair+Validator+环境搭建_cf9ffcda.jpg b/images/1.2.3+Fast+Pair+Validator+环境搭建_cf9ffcda.jpg
new file mode 100644
index 0000000..3f84e71
Binary files /dev/null and b/images/1.2.3+Fast+Pair+Validator+环境搭建_cf9ffcda.jpg differ
diff --git a/images/1.2.3+Fast+Pair+Validator+环境搭建_d2f1d705.jpg b/images/1.2.3+Fast+Pair+Validator+环境搭建_d2f1d705.jpg
new file mode 100644
index 0000000..c0e85e0
Binary files /dev/null and b/images/1.2.3+Fast+Pair+Validator+环境搭建_d2f1d705.jpg differ
diff --git a/images/1.2.3+Fast+Pair+Validator+环境搭建_d33c029a.jpg b/images/1.2.3+Fast+Pair+Validator+环境搭建_d33c029a.jpg
new file mode 100644
index 0000000..503cb7d
Binary files /dev/null and b/images/1.2.3+Fast+Pair+Validator+环境搭建_d33c029a.jpg differ
diff --git a/images/1.2.3+Fast+Pair+Validator+环境搭建_d6fa9b2d.jpg b/images/1.2.3+Fast+Pair+Validator+环境搭建_d6fa9b2d.jpg
new file mode 100644
index 0000000..3f84e71
Binary files /dev/null and b/images/1.2.3+Fast+Pair+Validator+环境搭建_d6fa9b2d.jpg differ
diff --git a/images/1.2.3+Fast+Pair+Validator+环境搭建_d84203e0.jpg b/images/1.2.3+Fast+Pair+Validator+环境搭建_d84203e0.jpg
new file mode 100644
index 0000000..071d3f9
Binary files /dev/null and b/images/1.2.3+Fast+Pair+Validator+环境搭建_d84203e0.jpg differ
diff --git a/images/1.2.3+Fast+Pair+Validator+环境搭建_dce3b2be.jpg b/images/1.2.3+Fast+Pair+Validator+环境搭建_dce3b2be.jpg
new file mode 100644
index 0000000..c5bbb74
Binary files /dev/null and b/images/1.2.3+Fast+Pair+Validator+环境搭建_dce3b2be.jpg differ
diff --git a/images/1.2.3+Fast+Pair+Validator+环境搭建_e2a5a4bc.jpg b/images/1.2.3+Fast+Pair+Validator+环境搭建_e2a5a4bc.jpg
new file mode 100644
index 0000000..2b46edf
Binary files /dev/null and b/images/1.2.3+Fast+Pair+Validator+环境搭建_e2a5a4bc.jpg differ
diff --git a/images/1.2.3+Fast+Pair+Validator+环境搭建_faa6f120.jpg b/images/1.2.3+Fast+Pair+Validator+环境搭建_faa6f120.jpg
new file mode 100644
index 0000000..302ade0
Binary files /dev/null and b/images/1.2.3+Fast+Pair+Validator+环境搭建_faa6f120.jpg differ
diff --git a/images/1.3+测试_0370e51b.jpg b/images/1.3+测试_0370e51b.jpg
new file mode 100644
index 0000000..e363de3
Binary files /dev/null and b/images/1.3+测试_0370e51b.jpg differ
diff --git a/images/1.3+测试_1cf1e800.jpg b/images/1.3+测试_1cf1e800.jpg
new file mode 100644
index 0000000..0dece59
Binary files /dev/null and b/images/1.3+测试_1cf1e800.jpg differ
diff --git a/images/1.3+测试_1d197ddc.jpg b/images/1.3+测试_1d197ddc.jpg
new file mode 100644
index 0000000..0dece59
Binary files /dev/null and b/images/1.3+测试_1d197ddc.jpg differ
diff --git a/images/1.3+测试_4f6eaa9e.jpg b/images/1.3+测试_4f6eaa9e.jpg
new file mode 100644
index 0000000..af58731
Binary files /dev/null and b/images/1.3+测试_4f6eaa9e.jpg differ
diff --git a/images/1.3+测试_56c5b765.jpg b/images/1.3+测试_56c5b765.jpg
new file mode 100644
index 0000000..e363de3
Binary files /dev/null and b/images/1.3+测试_56c5b765.jpg differ
diff --git a/images/1.3+测试_d7a80e4b.jpg b/images/1.3+测试_d7a80e4b.jpg
new file mode 100644
index 0000000..af58731
Binary files /dev/null and b/images/1.3+测试_d7a80e4b.jpg differ
diff --git a/images/1.3.1+Fast+Pair+Validator测试_3e518a6c.jpg b/images/1.3.1+Fast+Pair+Validator测试_3e518a6c.jpg
new file mode 100644
index 0000000..240e358
Binary files /dev/null and b/images/1.3.1+Fast+Pair+Validator测试_3e518a6c.jpg differ
diff --git a/images/1.3.1+Fast+Pair+Validator测试_bf03dc2e.jpg b/images/1.3.1+Fast+Pair+Validator测试_bf03dc2e.jpg
new file mode 100644
index 0000000..240e358
Binary files /dev/null and b/images/1.3.1+Fast+Pair+Validator测试_bf03dc2e.jpg differ
diff --git a/images/1.3.1.1+FAST+PAIR_01741b88.jpg b/images/1.3.1.1+FAST+PAIR_01741b88.jpg
new file mode 100644
index 0000000..86a991f
Binary files /dev/null and b/images/1.3.1.1+FAST+PAIR_01741b88.jpg differ
diff --git a/images/1.3.1.1+FAST+PAIR_01c3caae.jpg b/images/1.3.1.1+FAST+PAIR_01c3caae.jpg
new file mode 100644
index 0000000..b1a6228
Binary files /dev/null and b/images/1.3.1.1+FAST+PAIR_01c3caae.jpg differ
diff --git a/images/1.3.1.1+FAST+PAIR_039d4771.jpg b/images/1.3.1.1+FAST+PAIR_039d4771.jpg
new file mode 100644
index 0000000..45ab59e
Binary files /dev/null and b/images/1.3.1.1+FAST+PAIR_039d4771.jpg differ
diff --git a/images/1.3.1.1+FAST+PAIR_04d50156.jpg b/images/1.3.1.1+FAST+PAIR_04d50156.jpg
new file mode 100644
index 0000000..721b73d
Binary files /dev/null and b/images/1.3.1.1+FAST+PAIR_04d50156.jpg differ
diff --git a/images/1.3.1.1+FAST+PAIR_05e561f7.jpg b/images/1.3.1.1+FAST+PAIR_05e561f7.jpg
new file mode 100644
index 0000000..d336f77
Binary files /dev/null and b/images/1.3.1.1+FAST+PAIR_05e561f7.jpg differ
diff --git a/images/1.3.1.1+FAST+PAIR_0f04dd49.jpg b/images/1.3.1.1+FAST+PAIR_0f04dd49.jpg
new file mode 100644
index 0000000..1347313
Binary files /dev/null and b/images/1.3.1.1+FAST+PAIR_0f04dd49.jpg differ
diff --git a/images/1.3.1.1+FAST+PAIR_0f46ea09.jpg b/images/1.3.1.1+FAST+PAIR_0f46ea09.jpg
new file mode 100644
index 0000000..9ff0e76
Binary files /dev/null and b/images/1.3.1.1+FAST+PAIR_0f46ea09.jpg differ
diff --git a/images/1.3.1.1+FAST+PAIR_10ec8b90.jpg b/images/1.3.1.1+FAST+PAIR_10ec8b90.jpg
new file mode 100644
index 0000000..d6bfd8c
Binary files /dev/null and b/images/1.3.1.1+FAST+PAIR_10ec8b90.jpg differ
diff --git a/images/1.3.1.1+FAST+PAIR_145d5c13.jpg b/images/1.3.1.1+FAST+PAIR_145d5c13.jpg
new file mode 100644
index 0000000..ad4f24e
Binary files /dev/null and b/images/1.3.1.1+FAST+PAIR_145d5c13.jpg differ
diff --git a/images/1.3.1.1+FAST+PAIR_1835de60.jpg b/images/1.3.1.1+FAST+PAIR_1835de60.jpg
new file mode 100644
index 0000000..4b129ea
Binary files /dev/null and b/images/1.3.1.1+FAST+PAIR_1835de60.jpg differ
diff --git a/images/1.3.1.1+FAST+PAIR_1970e0a5.jpg b/images/1.3.1.1+FAST+PAIR_1970e0a5.jpg
new file mode 100644
index 0000000..516f98a
Binary files /dev/null and b/images/1.3.1.1+FAST+PAIR_1970e0a5.jpg differ
diff --git a/images/1.3.1.1+FAST+PAIR_1d522cb8.jpg b/images/1.3.1.1+FAST+PAIR_1d522cb8.jpg
new file mode 100644
index 0000000..3782f36
Binary files /dev/null and b/images/1.3.1.1+FAST+PAIR_1d522cb8.jpg differ
diff --git a/images/1.3.1.1+FAST+PAIR_216d26df.jpg b/images/1.3.1.1+FAST+PAIR_216d26df.jpg
new file mode 100644
index 0000000..4a04f11
Binary files /dev/null and b/images/1.3.1.1+FAST+PAIR_216d26df.jpg differ
diff --git a/images/1.3.1.1+FAST+PAIR_22034e16.jpg b/images/1.3.1.1+FAST+PAIR_22034e16.jpg
new file mode 100644
index 0000000..e16373b
Binary files /dev/null and b/images/1.3.1.1+FAST+PAIR_22034e16.jpg differ
diff --git a/images/1.3.1.1+FAST+PAIR_2297f2b1.jpg b/images/1.3.1.1+FAST+PAIR_2297f2b1.jpg
new file mode 100644
index 0000000..852aa5a
Binary files /dev/null and b/images/1.3.1.1+FAST+PAIR_2297f2b1.jpg differ
diff --git a/images/1.3.1.1+FAST+PAIR_2396302a.jpg b/images/1.3.1.1+FAST+PAIR_2396302a.jpg
new file mode 100644
index 0000000..404e1db
Binary files /dev/null and b/images/1.3.1.1+FAST+PAIR_2396302a.jpg differ
diff --git a/images/1.3.1.1+FAST+PAIR_2d1f321b.jpg b/images/1.3.1.1+FAST+PAIR_2d1f321b.jpg
new file mode 100644
index 0000000..32891b9
Binary files /dev/null and b/images/1.3.1.1+FAST+PAIR_2d1f321b.jpg differ
diff --git a/images/1.3.1.1+FAST+PAIR_2e244636.jpg b/images/1.3.1.1+FAST+PAIR_2e244636.jpg
new file mode 100644
index 0000000..fddba4f
Binary files /dev/null and b/images/1.3.1.1+FAST+PAIR_2e244636.jpg differ
diff --git a/images/1.3.1.1+FAST+PAIR_3b8c0c37.jpg b/images/1.3.1.1+FAST+PAIR_3b8c0c37.jpg
new file mode 100644
index 0000000..b8710bd
Binary files /dev/null and b/images/1.3.1.1+FAST+PAIR_3b8c0c37.jpg differ
diff --git a/images/1.3.1.1+FAST+PAIR_3c2e2213.jpg b/images/1.3.1.1+FAST+PAIR_3c2e2213.jpg
new file mode 100644
index 0000000..c57fcea
Binary files /dev/null and b/images/1.3.1.1+FAST+PAIR_3c2e2213.jpg differ
diff --git a/images/1.3.1.1+FAST+PAIR_40d23f12.jpg b/images/1.3.1.1+FAST+PAIR_40d23f12.jpg
new file mode 100644
index 0000000..4a1a3d5
Binary files /dev/null and b/images/1.3.1.1+FAST+PAIR_40d23f12.jpg differ
diff --git a/images/1.3.1.1+FAST+PAIR_4c1597cc.jpg b/images/1.3.1.1+FAST+PAIR_4c1597cc.jpg
new file mode 100644
index 0000000..d207df6
Binary files /dev/null and b/images/1.3.1.1+FAST+PAIR_4c1597cc.jpg differ
diff --git a/images/1.3.1.1+FAST+PAIR_4c550111.jpg b/images/1.3.1.1+FAST+PAIR_4c550111.jpg
new file mode 100644
index 0000000..fc9d19d
Binary files /dev/null and b/images/1.3.1.1+FAST+PAIR_4c550111.jpg differ
diff --git a/images/1.3.1.1+FAST+PAIR_4d57dedc.jpg b/images/1.3.1.1+FAST+PAIR_4d57dedc.jpg
new file mode 100644
index 0000000..32891b9
Binary files /dev/null and b/images/1.3.1.1+FAST+PAIR_4d57dedc.jpg differ
diff --git a/images/1.3.1.1+FAST+PAIR_566b3937.jpg b/images/1.3.1.1+FAST+PAIR_566b3937.jpg
new file mode 100644
index 0000000..c57fcea
Binary files /dev/null and b/images/1.3.1.1+FAST+PAIR_566b3937.jpg differ
diff --git a/images/1.3.1.1+FAST+PAIR_5966221f.jpg b/images/1.3.1.1+FAST+PAIR_5966221f.jpg
new file mode 100644
index 0000000..c2aa7cc
Binary files /dev/null and b/images/1.3.1.1+FAST+PAIR_5966221f.jpg differ
diff --git a/images/1.3.1.1+FAST+PAIR_6985367b.jpg b/images/1.3.1.1+FAST+PAIR_6985367b.jpg
new file mode 100644
index 0000000..45ab59e
Binary files /dev/null and b/images/1.3.1.1+FAST+PAIR_6985367b.jpg differ
diff --git a/images/1.3.1.1+FAST+PAIR_6a682683.jpg b/images/1.3.1.1+FAST+PAIR_6a682683.jpg
new file mode 100644
index 0000000..ce54135
Binary files /dev/null and b/images/1.3.1.1+FAST+PAIR_6a682683.jpg differ
diff --git a/images/1.3.1.1+FAST+PAIR_6dfbcaae.jpg b/images/1.3.1.1+FAST+PAIR_6dfbcaae.jpg
new file mode 100644
index 0000000..90bffde
Binary files /dev/null and b/images/1.3.1.1+FAST+PAIR_6dfbcaae.jpg differ
diff --git a/images/1.3.1.1+FAST+PAIR_709fdde6.jpg b/images/1.3.1.1+FAST+PAIR_709fdde6.jpg
new file mode 100644
index 0000000..4b129ea
Binary files /dev/null and b/images/1.3.1.1+FAST+PAIR_709fdde6.jpg differ
diff --git a/images/1.3.1.1+FAST+PAIR_7153b81f.jpg b/images/1.3.1.1+FAST+PAIR_7153b81f.jpg
new file mode 100644
index 0000000..fddba4f
Binary files /dev/null and b/images/1.3.1.1+FAST+PAIR_7153b81f.jpg differ
diff --git a/images/1.3.1.1+FAST+PAIR_719bd423.jpg b/images/1.3.1.1+FAST+PAIR_719bd423.jpg
new file mode 100644
index 0000000..8433e22
Binary files /dev/null and b/images/1.3.1.1+FAST+PAIR_719bd423.jpg differ
diff --git a/images/1.3.1.1+FAST+PAIR_738a911e.jpg b/images/1.3.1.1+FAST+PAIR_738a911e.jpg
new file mode 100644
index 0000000..e16373b
Binary files /dev/null and b/images/1.3.1.1+FAST+PAIR_738a911e.jpg differ
diff --git a/images/1.3.1.1+FAST+PAIR_77b9089c.jpg b/images/1.3.1.1+FAST+PAIR_77b9089c.jpg
new file mode 100644
index 0000000..3782f36
Binary files /dev/null and b/images/1.3.1.1+FAST+PAIR_77b9089c.jpg differ
diff --git a/images/1.3.1.1+FAST+PAIR_7d195d82.jpg b/images/1.3.1.1+FAST+PAIR_7d195d82.jpg
new file mode 100644
index 0000000..ce54135
Binary files /dev/null and b/images/1.3.1.1+FAST+PAIR_7d195d82.jpg differ
diff --git a/images/1.3.1.1+FAST+PAIR_82b6bae7.jpg b/images/1.3.1.1+FAST+PAIR_82b6bae7.jpg
new file mode 100644
index 0000000..d336f77
Binary files /dev/null and b/images/1.3.1.1+FAST+PAIR_82b6bae7.jpg differ
diff --git a/images/1.3.1.1+FAST+PAIR_83666ed3.jpg b/images/1.3.1.1+FAST+PAIR_83666ed3.jpg
new file mode 100644
index 0000000..0b6dfcf
Binary files /dev/null and b/images/1.3.1.1+FAST+PAIR_83666ed3.jpg differ
diff --git a/images/1.3.1.1+FAST+PAIR_84f9cb60.jpg b/images/1.3.1.1+FAST+PAIR_84f9cb60.jpg
new file mode 100644
index 0000000..1347313
Binary files /dev/null and b/images/1.3.1.1+FAST+PAIR_84f9cb60.jpg differ
diff --git a/images/1.3.1.1+FAST+PAIR_853c1c58.jpg b/images/1.3.1.1+FAST+PAIR_853c1c58.jpg
new file mode 100644
index 0000000..7c7d2fa
Binary files /dev/null and b/images/1.3.1.1+FAST+PAIR_853c1c58.jpg differ
diff --git a/images/1.3.1.1+FAST+PAIR_8965cff2.jpg b/images/1.3.1.1+FAST+PAIR_8965cff2.jpg
new file mode 100644
index 0000000..852aa5a
Binary files /dev/null and b/images/1.3.1.1+FAST+PAIR_8965cff2.jpg differ
diff --git a/images/1.3.1.1+FAST+PAIR_8b620dc0.jpg b/images/1.3.1.1+FAST+PAIR_8b620dc0.jpg
new file mode 100644
index 0000000..d207df6
Binary files /dev/null and b/images/1.3.1.1+FAST+PAIR_8b620dc0.jpg differ
diff --git a/images/1.3.1.1+FAST+PAIR_8e092f56.jpg b/images/1.3.1.1+FAST+PAIR_8e092f56.jpg
new file mode 100644
index 0000000..86a991f
Binary files /dev/null and b/images/1.3.1.1+FAST+PAIR_8e092f56.jpg differ
diff --git a/images/1.3.1.1+FAST+PAIR_912aa6e9.jpg b/images/1.3.1.1+FAST+PAIR_912aa6e9.jpg
new file mode 100644
index 0000000..b8710bd
Binary files /dev/null and b/images/1.3.1.1+FAST+PAIR_912aa6e9.jpg differ
diff --git a/images/1.3.1.1+FAST+PAIR_91a16572.jpg b/images/1.3.1.1+FAST+PAIR_91a16572.jpg
new file mode 100644
index 0000000..1e57336
Binary files /dev/null and b/images/1.3.1.1+FAST+PAIR_91a16572.jpg differ
diff --git a/images/1.3.1.1+FAST+PAIR_92349ae5.jpg b/images/1.3.1.1+FAST+PAIR_92349ae5.jpg
new file mode 100644
index 0000000..4f4b48b
Binary files /dev/null and b/images/1.3.1.1+FAST+PAIR_92349ae5.jpg differ
diff --git a/images/1.3.1.1+FAST+PAIR_943b5ff4.jpg b/images/1.3.1.1+FAST+PAIR_943b5ff4.jpg
new file mode 100644
index 0000000..7c7d2fa
Binary files /dev/null and b/images/1.3.1.1+FAST+PAIR_943b5ff4.jpg differ
diff --git a/images/1.3.1.1+FAST+PAIR_968092bd.jpg b/images/1.3.1.1+FAST+PAIR_968092bd.jpg
new file mode 100644
index 0000000..ad4f24e
Binary files /dev/null and b/images/1.3.1.1+FAST+PAIR_968092bd.jpg differ
diff --git a/images/1.3.1.1+FAST+PAIR_96e7a767.jpg b/images/1.3.1.1+FAST+PAIR_96e7a767.jpg
new file mode 100644
index 0000000..9e0995e
Binary files /dev/null and b/images/1.3.1.1+FAST+PAIR_96e7a767.jpg differ
diff --git a/images/1.3.1.1+FAST+PAIR_9874b01c.jpg b/images/1.3.1.1+FAST+PAIR_9874b01c.jpg
new file mode 100644
index 0000000..404e1db
Binary files /dev/null and b/images/1.3.1.1+FAST+PAIR_9874b01c.jpg differ
diff --git a/images/1.3.1.1+FAST+PAIR_990f7922.jpg b/images/1.3.1.1+FAST+PAIR_990f7922.jpg
new file mode 100644
index 0000000..4a1a3d5
Binary files /dev/null and b/images/1.3.1.1+FAST+PAIR_990f7922.jpg differ
diff --git a/images/1.3.1.1+FAST+PAIR_9d016119.jpg b/images/1.3.1.1+FAST+PAIR_9d016119.jpg
new file mode 100644
index 0000000..bc29350
Binary files /dev/null and b/images/1.3.1.1+FAST+PAIR_9d016119.jpg differ
diff --git a/images/1.3.1.1+FAST+PAIR_9f9ed241.jpg b/images/1.3.1.1+FAST+PAIR_9f9ed241.jpg
new file mode 100644
index 0000000..d6bfd8c
Binary files /dev/null and b/images/1.3.1.1+FAST+PAIR_9f9ed241.jpg differ
diff --git a/images/1.3.1.1+FAST+PAIR_a65ff5ca.jpg b/images/1.3.1.1+FAST+PAIR_a65ff5ca.jpg
new file mode 100644
index 0000000..85af556
Binary files /dev/null and b/images/1.3.1.1+FAST+PAIR_a65ff5ca.jpg differ
diff --git a/images/1.3.1.1+FAST+PAIR_a7642eba.jpg b/images/1.3.1.1+FAST+PAIR_a7642eba.jpg
new file mode 100644
index 0000000..b1a6228
Binary files /dev/null and b/images/1.3.1.1+FAST+PAIR_a7642eba.jpg differ
diff --git a/images/1.3.1.1+FAST+PAIR_a7d61f10.jpg b/images/1.3.1.1+FAST+PAIR_a7d61f10.jpg
new file mode 100644
index 0000000..4a04f11
Binary files /dev/null and b/images/1.3.1.1+FAST+PAIR_a7d61f10.jpg differ
diff --git a/images/1.3.1.1+FAST+PAIR_a9d42650.jpg b/images/1.3.1.1+FAST+PAIR_a9d42650.jpg
new file mode 100644
index 0000000..1e57336
Binary files /dev/null and b/images/1.3.1.1+FAST+PAIR_a9d42650.jpg differ
diff --git a/images/1.3.1.1+FAST+PAIR_ad8427fb.jpg b/images/1.3.1.1+FAST+PAIR_ad8427fb.jpg
new file mode 100644
index 0000000..c2aa7cc
Binary files /dev/null and b/images/1.3.1.1+FAST+PAIR_ad8427fb.jpg differ
diff --git a/images/1.3.1.1+FAST+PAIR_adc0fadd.jpg b/images/1.3.1.1+FAST+PAIR_adc0fadd.jpg
new file mode 100644
index 0000000..90bffde
Binary files /dev/null and b/images/1.3.1.1+FAST+PAIR_adc0fadd.jpg differ
diff --git a/images/1.3.1.1+FAST+PAIR_aedd7787.jpg b/images/1.3.1.1+FAST+PAIR_aedd7787.jpg
new file mode 100644
index 0000000..721b73d
Binary files /dev/null and b/images/1.3.1.1+FAST+PAIR_aedd7787.jpg differ
diff --git a/images/1.3.1.1+FAST+PAIR_b4088d95.jpg b/images/1.3.1.1+FAST+PAIR_b4088d95.jpg
new file mode 100644
index 0000000..67cd336
Binary files /dev/null and b/images/1.3.1.1+FAST+PAIR_b4088d95.jpg differ
diff --git a/images/1.3.1.1+FAST+PAIR_b4f9ca76.jpg b/images/1.3.1.1+FAST+PAIR_b4f9ca76.jpg
new file mode 100644
index 0000000..fc9d19d
Binary files /dev/null and b/images/1.3.1.1+FAST+PAIR_b4f9ca76.jpg differ
diff --git a/images/1.3.1.1+FAST+PAIR_be46d5e0.jpg b/images/1.3.1.1+FAST+PAIR_be46d5e0.jpg
new file mode 100644
index 0000000..c2b0529
Binary files /dev/null and b/images/1.3.1.1+FAST+PAIR_be46d5e0.jpg differ
diff --git a/images/1.3.1.1+FAST+PAIR_bfba30ae.jpg b/images/1.3.1.1+FAST+PAIR_bfba30ae.jpg
new file mode 100644
index 0000000..4b7fdeb
Binary files /dev/null and b/images/1.3.1.1+FAST+PAIR_bfba30ae.jpg differ
diff --git a/images/1.3.1.1+FAST+PAIR_bff005b1.jpg b/images/1.3.1.1+FAST+PAIR_bff005b1.jpg
new file mode 100644
index 0000000..fa50efb
Binary files /dev/null and b/images/1.3.1.1+FAST+PAIR_bff005b1.jpg differ
diff --git a/images/1.3.1.1+FAST+PAIR_cf6fc278.jpg b/images/1.3.1.1+FAST+PAIR_cf6fc278.jpg
new file mode 100644
index 0000000..529fbe5
Binary files /dev/null and b/images/1.3.1.1+FAST+PAIR_cf6fc278.jpg differ
diff --git a/images/1.3.1.1+FAST+PAIR_d1682cdc.jpg b/images/1.3.1.1+FAST+PAIR_d1682cdc.jpg
new file mode 100644
index 0000000..4f4b48b
Binary files /dev/null and b/images/1.3.1.1+FAST+PAIR_d1682cdc.jpg differ
diff --git a/images/1.3.1.1+FAST+PAIR_d216db90.jpg b/images/1.3.1.1+FAST+PAIR_d216db90.jpg
new file mode 100644
index 0000000..282c6fc
Binary files /dev/null and b/images/1.3.1.1+FAST+PAIR_d216db90.jpg differ
diff --git a/images/1.3.1.1+FAST+PAIR_d736b5c5.jpg b/images/1.3.1.1+FAST+PAIR_d736b5c5.jpg
new file mode 100644
index 0000000..8433e22
Binary files /dev/null and b/images/1.3.1.1+FAST+PAIR_d736b5c5.jpg differ
diff --git a/images/1.3.1.1+FAST+PAIR_df0578ed.jpg b/images/1.3.1.1+FAST+PAIR_df0578ed.jpg
new file mode 100644
index 0000000..9e0995e
Binary files /dev/null and b/images/1.3.1.1+FAST+PAIR_df0578ed.jpg differ
diff --git a/images/1.3.1.1+FAST+PAIR_e0ff2701.jpg b/images/1.3.1.1+FAST+PAIR_e0ff2701.jpg
new file mode 100644
index 0000000..282c6fc
Binary files /dev/null and b/images/1.3.1.1+FAST+PAIR_e0ff2701.jpg differ
diff --git a/images/1.3.1.1+FAST+PAIR_e1bb02c6.jpg b/images/1.3.1.1+FAST+PAIR_e1bb02c6.jpg
new file mode 100644
index 0000000..bc29350
Binary files /dev/null and b/images/1.3.1.1+FAST+PAIR_e1bb02c6.jpg differ
diff --git a/images/1.3.1.1+FAST+PAIR_e21fb9ca.jpg b/images/1.3.1.1+FAST+PAIR_e21fb9ca.jpg
new file mode 100644
index 0000000..529fbe5
Binary files /dev/null and b/images/1.3.1.1+FAST+PAIR_e21fb9ca.jpg differ
diff --git a/images/1.3.1.1+FAST+PAIR_e40ebd75.jpg b/images/1.3.1.1+FAST+PAIR_e40ebd75.jpg
new file mode 100644
index 0000000..67cd336
Binary files /dev/null and b/images/1.3.1.1+FAST+PAIR_e40ebd75.jpg differ
diff --git a/images/1.3.1.1+FAST+PAIR_e8c5dead.jpg b/images/1.3.1.1+FAST+PAIR_e8c5dead.jpg
new file mode 100644
index 0000000..c2b0529
Binary files /dev/null and b/images/1.3.1.1+FAST+PAIR_e8c5dead.jpg differ
diff --git a/images/1.3.1.1+FAST+PAIR_eb75bb6a.jpg b/images/1.3.1.1+FAST+PAIR_eb75bb6a.jpg
new file mode 100644
index 0000000..516f98a
Binary files /dev/null and b/images/1.3.1.1+FAST+PAIR_eb75bb6a.jpg differ
diff --git a/images/1.3.1.1+FAST+PAIR_f1690a5c.jpg b/images/1.3.1.1+FAST+PAIR_f1690a5c.jpg
new file mode 100644
index 0000000..0b6dfcf
Binary files /dev/null and b/images/1.3.1.1+FAST+PAIR_f1690a5c.jpg differ
diff --git a/images/1.3.1.1+FAST+PAIR_f4561327.jpg b/images/1.3.1.1+FAST+PAIR_f4561327.jpg
new file mode 100644
index 0000000..4b7fdeb
Binary files /dev/null and b/images/1.3.1.1+FAST+PAIR_f4561327.jpg differ
diff --git a/images/1.3.1.1+FAST+PAIR_f8038a19.jpg b/images/1.3.1.1+FAST+PAIR_f8038a19.jpg
new file mode 100644
index 0000000..fa50efb
Binary files /dev/null and b/images/1.3.1.1+FAST+PAIR_f8038a19.jpg differ
diff --git a/images/1.3.1.1+FAST+PAIR_f8856148.jpg b/images/1.3.1.1+FAST+PAIR_f8856148.jpg
new file mode 100644
index 0000000..9ff0e76
Binary files /dev/null and b/images/1.3.1.1+FAST+PAIR_f8856148.jpg differ
diff --git a/images/1.3.1.1+FAST+PAIR_fb995c6e.jpg b/images/1.3.1.1+FAST+PAIR_fb995c6e.jpg
new file mode 100644
index 0000000..85af556
Binary files /dev/null and b/images/1.3.1.1+FAST+PAIR_fb995c6e.jpg differ
diff --git a/images/1.provider支援LE+audio+++Legacy+audio,不用单独过GFPS+Legacy的认证__198d1a3e.jpg b/images/1.provider支援LE+audio+++Legacy+audio,不用单独过GFPS+Legacy的认证__198d1a3e.jpg
new file mode 100644
index 0000000..dc052f9
Binary files /dev/null and b/images/1.provider支援LE+audio+++Legacy+audio,不用单独过GFPS+Legacy的认证__198d1a3e.jpg differ
diff --git a/images/1.provider支援LE+audio+++Legacy+audio,不用单独过GFPS+Legacy的认证__6e23b1c9.jpg b/images/1.provider支援LE+audio+++Legacy+audio,不用单独过GFPS+Legacy的认证__6e23b1c9.jpg
new file mode 100644
index 0000000..dc052f9
Binary files /dev/null and b/images/1.provider支援LE+audio+++Legacy+audio,不用单独过GFPS+Legacy的认证__6e23b1c9.jpg differ
diff --git a/images/1.耳机支援LEA,手机也支援LEA,测试fail_169b8618.jpg b/images/1.耳机支援LEA,手机也支援LEA,测试fail_169b8618.jpg
new file mode 100644
index 0000000..e602dec
Binary files /dev/null and b/images/1.耳机支援LEA,手机也支援LEA,测试fail_169b8618.jpg differ
diff --git a/images/1.耳机支援LEA,手机也支援LEA,测试fail_370b6457.jpg b/images/1.耳机支援LEA,手机也支援LEA,测试fail_370b6457.jpg
new file mode 100644
index 0000000..35fb739
Binary files /dev/null and b/images/1.耳机支援LEA,手机也支援LEA,测试fail_370b6457.jpg differ
diff --git a/images/1.耳机支援LEA,手机也支援LEA,测试fail_46ca7971.jpg b/images/1.耳机支援LEA,手机也支援LEA,测试fail_46ca7971.jpg
new file mode 100644
index 0000000..44bcde0
Binary files /dev/null and b/images/1.耳机支援LEA,手机也支援LEA,测试fail_46ca7971.jpg differ
diff --git a/images/1.耳机支援LEA,手机也支援LEA,测试fail_67d22ed7.jpg b/images/1.耳机支援LEA,手机也支援LEA,测试fail_67d22ed7.jpg
new file mode 100644
index 0000000..44bcde0
Binary files /dev/null and b/images/1.耳机支援LEA,手机也支援LEA,测试fail_67d22ed7.jpg differ
diff --git a/images/1.耳机支援LEA,手机也支援LEA,测试fail_8b12fd51.jpg b/images/1.耳机支援LEA,手机也支援LEA,测试fail_8b12fd51.jpg
new file mode 100644
index 0000000..35fb739
Binary files /dev/null and b/images/1.耳机支援LEA,手机也支援LEA,测试fail_8b12fd51.jpg differ
diff --git a/images/1.耳机支援LEA,手机也支援LEA,测试fail_fa728633.jpg b/images/1.耳机支援LEA,手机也支援LEA,测试fail_fa728633.jpg
new file mode 100644
index 0000000..e602dec
Binary files /dev/null and b/images/1.耳机支援LEA,手机也支援LEA,测试fail_fa728633.jpg differ
diff --git a/images/10+battery+HUN弹窗一直不消失，或者是一直不显示_2e26454b.jpg b/images/10+battery+HUN弹窗一直不消失，或者是一直不显示_2e26454b.jpg
new file mode 100644
index 0000000..bc7882e
Binary files /dev/null and b/images/10+battery+HUN弹窗一直不消失，或者是一直不显示_2e26454b.jpg differ
diff --git a/images/10+battery+HUN弹窗一直不消失，或者是一直不显示_80a27fda.jpg b/images/10+battery+HUN弹窗一直不消失，或者是一直不显示_80a27fda.jpg
new file mode 100644
index 0000000..e46e4f0
Binary files /dev/null and b/images/10+battery+HUN弹窗一直不消失，或者是一直不显示_80a27fda.jpg differ
diff --git a/images/10+battery+HUN弹窗一直不消失，或者是一直不显示_8f056b78.jpg b/images/10+battery+HUN弹窗一直不消失，或者是一直不显示_8f056b78.jpg
new file mode 100644
index 0000000..e46e4f0
Binary files /dev/null and b/images/10+battery+HUN弹窗一直不消失，或者是一直不显示_8f056b78.jpg differ
diff --git a/images/10+battery+HUN弹窗一直不消失，或者是一直不显示_ac930b96.jpg b/images/10+battery+HUN弹窗一直不消失，或者是一直不显示_ac930b96.jpg
new file mode 100644
index 0000000..bc7882e
Binary files /dev/null and b/images/10+battery+HUN弹窗一直不消失，或者是一直不显示_ac930b96.jpg differ
diff --git a/images/10+initial+pair成功,LE+ACL+link存在,耳机再次进入Pairing+mode,手机弹窗出来点击弹窗配对失败_35744622.jpg b/images/10+initial+pair成功,LE+ACL+link存在,耳机再次进入Pairing+mode,手机弹窗出来点击弹窗配对失败_35744622.jpg
new file mode 100644
index 0000000..a9cbeaa
Binary files /dev/null and b/images/10+initial+pair成功,LE+ACL+link存在,耳机再次进入Pairing+mode,手机弹窗出来点击弹窗配对失败_35744622.jpg differ
diff --git a/images/10+initial+pair成功,LE+ACL+link存在,耳机再次进入Pairing+mode,手机弹窗出来点击弹窗配对失败_53b88440.jpg b/images/10+initial+pair成功,LE+ACL+link存在,耳机再次进入Pairing+mode,手机弹窗出来点击弹窗配对失败_53b88440.jpg
new file mode 100644
index 0000000..a9cbeaa
Binary files /dev/null and b/images/10+initial+pair成功,LE+ACL+link存在,耳机再次进入Pairing+mode,手机弹窗出来点击弹窗配对失败_53b88440.jpg differ
diff --git a/images/11+Ringing+using+the+accessory+non-owner+service(dult)+fail_0217de29.jpg b/images/11+Ringing+using+the+accessory+non-owner+service(dult)+fail_0217de29.jpg
new file mode 100644
index 0000000..030b1b1
Binary files /dev/null and b/images/11+Ringing+using+the+accessory+non-owner+service(dult)+fail_0217de29.jpg differ
diff --git a/images/11+Ringing+using+the+accessory+non-owner+service(dult)+fail_0eb3469a.jpg b/images/11+Ringing+using+the+accessory+non-owner+service(dult)+fail_0eb3469a.jpg
new file mode 100644
index 0000000..030b1b1
Binary files /dev/null and b/images/11+Ringing+using+the+accessory+non-owner+service(dult)+fail_0eb3469a.jpg differ
diff --git a/images/11+Ringing+using+the+accessory+non-owner+service(dult)+fail_61793064.jpg b/images/11+Ringing+using+the+accessory+non-owner+service(dult)+fail_61793064.jpg
new file mode 100644
index 0000000..c97bbd1
Binary files /dev/null and b/images/11+Ringing+using+the+accessory+non-owner+service(dult)+fail_61793064.jpg differ
diff --git a/images/11+Ringing+using+the+accessory+non-owner+service(dult)+fail_69ce7f34.jpg b/images/11+Ringing+using+the+accessory+non-owner+service(dult)+fail_69ce7f34.jpg
new file mode 100644
index 0000000..d521c1c
Binary files /dev/null and b/images/11+Ringing+using+the+accessory+non-owner+service(dult)+fail_69ce7f34.jpg differ
diff --git a/images/11+Ringing+using+the+accessory+non-owner+service(dult)+fail_6f086002.jpg b/images/11+Ringing+using+the+accessory+non-owner+service(dult)+fail_6f086002.jpg
new file mode 100644
index 0000000..c97bbd1
Binary files /dev/null and b/images/11+Ringing+using+the+accessory+non-owner+service(dult)+fail_6f086002.jpg differ
diff --git a/images/11+Ringing+using+the+accessory+non-owner+service(dult)+fail_ccfcade3.jpg b/images/11+Ringing+using+the+accessory+non-owner+service(dult)+fail_ccfcade3.jpg
new file mode 100644
index 0000000..d521c1c
Binary files /dev/null and b/images/11+Ringing+using+the+accessory+non-owner+service(dult)+fail_ccfcade3.jpg differ
diff --git a/images/12+Pairing+process+error,+Reason_+Not+receive+UUID,+Is+connected_false_0dc2bf30.jpg b/images/12+Pairing+process+error,+Reason_+Not+receive+UUID,+Is+connected_false_0dc2bf30.jpg
new file mode 100644
index 0000000..636153a
Binary files /dev/null and b/images/12+Pairing+process+error,+Reason_+Not+receive+UUID,+Is+connected_false_0dc2bf30.jpg differ
diff --git a/images/12+Pairing+process+error,+Reason_+Not+receive+UUID,+Is+connected_false_50a6e196.jpg b/images/12+Pairing+process+error,+Reason_+Not+receive+UUID,+Is+connected_false_50a6e196.jpg
new file mode 100644
index 0000000..3fd93cc
Binary files /dev/null and b/images/12+Pairing+process+error,+Reason_+Not+receive+UUID,+Is+connected_false_50a6e196.jpg differ
diff --git a/images/12+Pairing+process+error,+Reason_+Not+receive+UUID,+Is+connected_false_eb209f5b.jpg b/images/12+Pairing+process+error,+Reason_+Not+receive+UUID,+Is+connected_false_eb209f5b.jpg
new file mode 100644
index 0000000..3fd93cc
Binary files /dev/null and b/images/12+Pairing+process+error,+Reason_+Not+receive+UUID,+Is+connected_false_eb209f5b.jpg differ
diff --git a/images/12+Pairing+process+error,+Reason_+Not+receive+UUID,+Is+connected_false_ee284632.jpg b/images/12+Pairing+process+error,+Reason_+Not+receive+UUID,+Is+connected_false_ee284632.jpg
new file mode 100644
index 0000000..636153a
Binary files /dev/null and b/images/12+Pairing+process+error,+Reason_+Not+receive+UUID,+Is+connected_false_ee284632.jpg differ
diff --git a/images/12+Pairing+process+error.+Reason_+Only+receive+correct+UUID+from+1+address_59d98e8b.jpg b/images/12+Pairing+process+error.+Reason_+Only+receive+correct+UUID+from+1+address_59d98e8b.jpg
new file mode 100644
index 0000000..29ec821
Binary files /dev/null and b/images/12+Pairing+process+error.+Reason_+Only+receive+correct+UUID+from+1+address_59d98e8b.jpg differ
diff --git a/images/12+Pairing+process+error.+Reason_+Only+receive+correct+UUID+from+1+address_fc91a6d1.jpg b/images/12+Pairing+process+error.+Reason_+Only+receive+correct+UUID+from+1+address_fc91a6d1.jpg
new file mode 100644
index 0000000..29ec821
Binary files /dev/null and b/images/12+Pairing+process+error.+Reason_+Only+receive+correct+UUID+from+1+address_fc91a6d1.jpg differ
diff --git a/images/12+Pairing+process+error_+Reason_+Is+connected+false_06fb8fbe.jpg b/images/12+Pairing+process+error_+Reason_+Is+connected+false_06fb8fbe.jpg
new file mode 100644
index 0000000..76fc037
Binary files /dev/null and b/images/12+Pairing+process+error_+Reason_+Is+connected+false_06fb8fbe.jpg differ
diff --git a/images/12+Pairing+process+error_+Reason_+Is+connected+false_4a1b4ce9.jpg b/images/12+Pairing+process+error_+Reason_+Is+connected+false_4a1b4ce9.jpg
new file mode 100644
index 0000000..76fc037
Binary files /dev/null and b/images/12+Pairing+process+error_+Reason_+Is+connected+false_4a1b4ce9.jpg differ
diff --git a/images/12+Pairing+process+error_+Reason_+Is+connected+false_b359d351.jpg b/images/12+Pairing+process+error_+Reason_+Is+connected+false_b359d351.jpg
new file mode 100644
index 0000000..636153a
Binary files /dev/null and b/images/12+Pairing+process+error_+Reason_+Is+connected+false_b359d351.jpg differ
diff --git a/images/12+Pairing+process+error_+Reason_+Is+connected+false_f9e6c4a2.jpg b/images/12+Pairing+process+error_+Reason_+Is+connected+false_f9e6c4a2.jpg
new file mode 100644
index 0000000..636153a
Binary files /dev/null and b/images/12+Pairing+process+error_+Reason_+Is+connected+false_f9e6c4a2.jpg differ
diff --git a/images/14+Initial+Pair+with+(XX_XX_)+fail_6d655369.jpg b/images/14+Initial+Pair+with+(XX_XX_)+fail_6d655369.jpg
new file mode 100644
index 0000000..ae33446
Binary files /dev/null and b/images/14+Initial+Pair+with+(XX_XX_)+fail_6d655369.jpg differ
diff --git a/images/14+Initial+Pair+with+(XX_XX_)+fail_77955b5d.jpg b/images/14+Initial+Pair+with+(XX_XX_)+fail_77955b5d.jpg
new file mode 100644
index 0000000..ae33446
Binary files /dev/null and b/images/14+Initial+Pair+with+(XX_XX_)+fail_77955b5d.jpg differ
diff --git a/images/14+Initialize+fast+pair+service+failed_08f44326.jpg b/images/14+Initialize+fast+pair+service+failed_08f44326.jpg
new file mode 100644
index 0000000..41f4408
Binary files /dev/null and b/images/14+Initialize+fast+pair+service+failed_08f44326.jpg differ
diff --git a/images/14+Initialize+fast+pair+service+failed_3d30ef4d.jpg b/images/14+Initialize+fast+pair+service+failed_3d30ef4d.jpg
new file mode 100644
index 0000000..1393633
Binary files /dev/null and b/images/14+Initialize+fast+pair+service+failed_3d30ef4d.jpg differ
diff --git a/images/14+Initialize+fast+pair+service+failed_52b74a2b.jpg b/images/14+Initialize+fast+pair+service+failed_52b74a2b.jpg
new file mode 100644
index 0000000..1256bd4
Binary files /dev/null and b/images/14+Initialize+fast+pair+service+failed_52b74a2b.jpg differ
diff --git a/images/14+Initialize+fast+pair+service+failed_803b9943.jpg b/images/14+Initialize+fast+pair+service+failed_803b9943.jpg
new file mode 100644
index 0000000..ceae61b
Binary files /dev/null and b/images/14+Initialize+fast+pair+service+failed_803b9943.jpg differ
diff --git a/images/14+Initialize+fast+pair+service+failed_957ec354.jpg b/images/14+Initialize+fast+pair+service+failed_957ec354.jpg
new file mode 100644
index 0000000..38cefb4
Binary files /dev/null and b/images/14+Initialize+fast+pair+service+failed_957ec354.jpg differ
diff --git a/images/14+Initialize+fast+pair+service+failed_a2cb1512.jpg b/images/14+Initialize+fast+pair+service+failed_a2cb1512.jpg
new file mode 100644
index 0000000..ceae61b
Binary files /dev/null and b/images/14+Initialize+fast+pair+service+failed_a2cb1512.jpg differ
diff --git a/images/14+Initialize+fast+pair+service+failed_a7460c84.jpg b/images/14+Initialize+fast+pair+service+failed_a7460c84.jpg
new file mode 100644
index 0000000..41f4408
Binary files /dev/null and b/images/14+Initialize+fast+pair+service+failed_a7460c84.jpg differ
diff --git a/images/14+Initialize+fast+pair+service+failed_bef0240b.jpg b/images/14+Initialize+fast+pair+service+failed_bef0240b.jpg
new file mode 100644
index 0000000..38cefb4
Binary files /dev/null and b/images/14+Initialize+fast+pair+service+failed_bef0240b.jpg differ
diff --git a/images/14+Initialize+fast+pair+service+failed_db2c121c.jpg b/images/14+Initialize+fast+pair+service+failed_db2c121c.jpg
new file mode 100644
index 0000000..1393633
Binary files /dev/null and b/images/14+Initialize+fast+pair+service+failed_db2c121c.jpg differ
diff --git a/images/14+Initialize+fast+pair+service+failed_f068d3a7.jpg b/images/14+Initialize+fast+pair+service+failed_f068d3a7.jpg
new file mode 100644
index 0000000..1256bd4
Binary files /dev/null and b/images/14+Initialize+fast+pair+service+failed_f068d3a7.jpg differ
diff --git a/images/15+GFPS+TWS+mode+测试ring功能的时候+++手机端只显示一个耳机设备_0137b155.jpg b/images/15+GFPS+TWS+mode+测试ring功能的时候+++手机端只显示一个耳机设备_0137b155.jpg
new file mode 100644
index 0000000..fadf92d
Binary files /dev/null and b/images/15+GFPS+TWS+mode+测试ring功能的时候+++手机端只显示一个耳机设备_0137b155.jpg differ
diff --git a/images/15+GFPS+TWS+mode+测试ring功能的时候+++手机端只显示一个耳机设备_3700d85d.jpg b/images/15+GFPS+TWS+mode+测试ring功能的时候+++手机端只显示一个耳机设备_3700d85d.jpg
new file mode 100644
index 0000000..2e10097
Binary files /dev/null and b/images/15+GFPS+TWS+mode+测试ring功能的时候+++手机端只显示一个耳机设备_3700d85d.jpg differ
diff --git a/images/15+GFPS+TWS+mode+测试ring功能的时候+++手机端只显示一个耳机设备_5d351fea.jpg b/images/15+GFPS+TWS+mode+测试ring功能的时候+++手机端只显示一个耳机设备_5d351fea.jpg
new file mode 100644
index 0000000..fadf92d
Binary files /dev/null and b/images/15+GFPS+TWS+mode+测试ring功能的时候+++手机端只显示一个耳机设备_5d351fea.jpg differ
diff --git a/images/15+GFPS+TWS+mode+测试ring功能的时候+++手机端只显示一个耳机设备_6d9cb147.jpg b/images/15+GFPS+TWS+mode+测试ring功能的时候+++手机端只显示一个耳机设备_6d9cb147.jpg
new file mode 100644
index 0000000..d9e58ea
Binary files /dev/null and b/images/15+GFPS+TWS+mode+测试ring功能的时候+++手机端只显示一个耳机设备_6d9cb147.jpg differ
diff --git a/images/15+GFPS+TWS+mode+测试ring功能的时候+++手机端只显示一个耳机设备_7f190ae5.jpg b/images/15+GFPS+TWS+mode+测试ring功能的时候+++手机端只显示一个耳机设备_7f190ae5.jpg
new file mode 100644
index 0000000..312e770
Binary files /dev/null and b/images/15+GFPS+TWS+mode+测试ring功能的时候+++手机端只显示一个耳机设备_7f190ae5.jpg differ
diff --git a/images/15+GFPS+TWS+mode+测试ring功能的时候+++手机端只显示一个耳机设备_c1d38e7d.jpg b/images/15+GFPS+TWS+mode+测试ring功能的时候+++手机端只显示一个耳机设备_c1d38e7d.jpg
new file mode 100644
index 0000000..312e770
Binary files /dev/null and b/images/15+GFPS+TWS+mode+测试ring功能的时候+++手机端只显示一个耳机设备_c1d38e7d.jpg differ
diff --git a/images/15+GFPS+TWS+mode+测试ring功能的时候+++手机端只显示一个耳机设备_caa7266f.jpg b/images/15+GFPS+TWS+mode+测试ring功能的时候+++手机端只显示一个耳机设备_caa7266f.jpg
new file mode 100644
index 0000000..d9e58ea
Binary files /dev/null and b/images/15+GFPS+TWS+mode+测试ring功能的时候+++手机端只显示一个耳机设备_caa7266f.jpg differ
diff --git a/images/15+GFPS+TWS+mode+测试ring功能的时候+++手机端只显示一个耳机设备_fc7b7ee3.jpg b/images/15+GFPS+TWS+mode+测试ring功能的时候+++手机端只显示一个耳机设备_fc7b7ee3.jpg
new file mode 100644
index 0000000..2e10097
Binary files /dev/null and b/images/15+GFPS+TWS+mode+测试ring功能的时候+++手机端只显示一个耳机设备_fc7b7ee3.jpg differ
diff --git a/images/15+app_gfps_check_receive_pair_req_+receive_pair_req+0_2a911564.jpg b/images/15+app_gfps_check_receive_pair_req_+receive_pair_req+0_2a911564.jpg
new file mode 100644
index 0000000..8eacc22
Binary files /dev/null and b/images/15+app_gfps_check_receive_pair_req_+receive_pair_req+0_2a911564.jpg differ
diff --git a/images/15+app_gfps_check_receive_pair_req_+receive_pair_req+0_6e191cd4.jpg b/images/15+app_gfps_check_receive_pair_req_+receive_pair_req+0_6e191cd4.jpg
new file mode 100644
index 0000000..8eacc22
Binary files /dev/null and b/images/15+app_gfps_check_receive_pair_req_+receive_pair_req+0_6e191cd4.jpg differ
diff --git a/images/16+!!!app_gfps_cb_handle_accountkey_+account_key_write_counts+2_1364318b.jpg b/images/16+!!!app_gfps_cb_handle_accountkey_+account_key_write_counts+2_1364318b.jpg
new file mode 100644
index 0000000..d184632
Binary files /dev/null and b/images/16+!!!app_gfps_cb_handle_accountkey_+account_key_write_counts+2_1364318b.jpg differ
diff --git a/images/16+!!!app_gfps_cb_handle_accountkey_+account_key_write_counts+2_6151b611.jpg b/images/16+!!!app_gfps_cb_handle_accountkey_+account_key_write_counts+2_6151b611.jpg
new file mode 100644
index 0000000..f8ea98d
Binary files /dev/null and b/images/16+!!!app_gfps_cb_handle_accountkey_+account_key_write_counts+2_6151b611.jpg differ
diff --git a/images/16+!!!app_gfps_cb_handle_accountkey_+account_key_write_counts+2_73807434.jpg b/images/16+!!!app_gfps_cb_handle_accountkey_+account_key_write_counts+2_73807434.jpg
new file mode 100644
index 0000000..d184632
Binary files /dev/null and b/images/16+!!!app_gfps_cb_handle_accountkey_+account_key_write_counts+2_73807434.jpg differ
diff --git a/images/16+!!!app_gfps_cb_handle_accountkey_+account_key_write_counts+2_a2b05af4.jpg b/images/16+!!!app_gfps_cb_handle_accountkey_+account_key_write_counts+2_a2b05af4.jpg
new file mode 100644
index 0000000..f8ea98d
Binary files /dev/null and b/images/16+!!!app_gfps_cb_handle_accountkey_+account_key_write_counts+2_a2b05af4.jpg differ
diff --git a/images/16+手机端测试响铃功能时，找不到响铃的按键_178cc112.jpg b/images/16+手机端测试响铃功能时，找不到响铃的按键_178cc112.jpg
new file mode 100644
index 0000000..1a5b05f
Binary files /dev/null and b/images/16+手机端测试响铃功能时，找不到响铃的按键_178cc112.jpg differ
diff --git a/images/16+手机端测试响铃功能时，找不到响铃的按键_5e4c1921.jpg b/images/16+手机端测试响铃功能时，找不到响铃的按键_5e4c1921.jpg
new file mode 100644
index 0000000..7f60a5b
Binary files /dev/null and b/images/16+手机端测试响铃功能时，找不到响铃的按键_5e4c1921.jpg differ
diff --git a/images/16+手机端测试响铃功能时，找不到响铃的按键_7ad974ba.jpg b/images/16+手机端测试响铃功能时，找不到响铃的按键_7ad974ba.jpg
new file mode 100644
index 0000000..7f60a5b
Binary files /dev/null and b/images/16+手机端测试响铃功能时，找不到响铃的按键_7ad974ba.jpg differ
diff --git a/images/16+手机端测试响铃功能时，找不到响铃的按键_89f15a96.jpg b/images/16+手机端测试响铃功能时，找不到响铃的按键_89f15a96.jpg
new file mode 100644
index 0000000..1a5b05f
Binary files /dev/null and b/images/16+手机端测试响铃功能时，找不到响铃的按键_89f15a96.jpg differ
diff --git a/images/16+手机端测试响铃功能时，找不到响铃的按键_b53597a5.jpg b/images/16+手机端测试响铃功能时，找不到响铃的按键_b53597a5.jpg
new file mode 100644
index 0000000..ba4d062
Binary files /dev/null and b/images/16+手机端测试响铃功能时，找不到响铃的按键_b53597a5.jpg differ
diff --git a/images/16+手机端测试响铃功能时，找不到响铃的按键_d03366e8.jpg b/images/16+手机端测试响铃功能时，找不到响铃的按键_d03366e8.jpg
new file mode 100644
index 0000000..ba4d062
Binary files /dev/null and b/images/16+手机端测试响铃功能时，找不到响铃的按键_d03366e8.jpg differ
diff --git a/images/16+手机端测试响铃功能时，找不到响铃的按键_dde9f721.jpg b/images/16+手机端测试响铃功能时，找不到响铃的按键_dde9f721.jpg
new file mode 100644
index 0000000..e57c1a2
Binary files /dev/null and b/images/16+手机端测试响铃功能时，找不到响铃的按键_dde9f721.jpg differ
diff --git a/images/16+手机端测试响铃功能时，找不到响铃的按键_fda1a428.jpg b/images/16+手机端测试响铃功能时，找不到响铃的按键_fda1a428.jpg
new file mode 100644
index 0000000..e57c1a2
Binary files /dev/null and b/images/16+手机端测试响铃功能时，找不到响铃的按键_fda1a428.jpg differ
diff --git a/images/2+Enable+new+feature+test+in+Validator_01716312.jpg b/images/2+Enable+new+feature+test+in+Validator_01716312.jpg
new file mode 100644
index 0000000..ff57232
Binary files /dev/null and b/images/2+Enable+new+feature+test+in+Validator_01716312.jpg differ
diff --git a/images/2+Enable+new+feature+test+in+Validator_92806b67.jpg b/images/2+Enable+new+feature+test+in+Validator_92806b67.jpg
new file mode 100644
index 0000000..b4477df
Binary files /dev/null and b/images/2+Enable+new+feature+test+in+Validator_92806b67.jpg differ
diff --git a/images/2+Enable+new+feature+test+in+Validator_acc198ea.jpg b/images/2+Enable+new+feature+test+in+Validator_acc198ea.jpg
new file mode 100644
index 0000000..ff57232
Binary files /dev/null and b/images/2+Enable+new+feature+test+in+Validator_acc198ea.jpg differ
diff --git a/images/2+Enable+new+feature+test+in+Validator_ee4b5cb3.jpg b/images/2+Enable+new+feature+test+in+Validator_ee4b5cb3.jpg
new file mode 100644
index 0000000..b4477df
Binary files /dev/null and b/images/2+Enable+new+feature+test+in+Validator_ee4b5cb3.jpg differ
diff --git a/images/2+Scan_Connected+timing+测试fail_9e6ccc12.jpg b/images/2+Scan_Connected+timing+测试fail_9e6ccc12.jpg
new file mode 100644
index 0000000..bfb8662
Binary files /dev/null and b/images/2+Scan_Connected+timing+测试fail_9e6ccc12.jpg differ
diff --git a/images/2+Scan_Connected+timing+测试fail_baa3c7a9.jpg b/images/2+Scan_Connected+timing+测试fail_baa3c7a9.jpg
new file mode 100644
index 0000000..a4f214f
Binary files /dev/null and b/images/2+Scan_Connected+timing+测试fail_baa3c7a9.jpg differ
diff --git a/images/2+Scan_Connected+timing+测试fail_ed6cc7f7.jpg b/images/2+Scan_Connected+timing+测试fail_ed6cc7f7.jpg
new file mode 100644
index 0000000..bfb8662
Binary files /dev/null and b/images/2+Scan_Connected+timing+测试fail_ed6cc7f7.jpg differ
diff --git a/images/2+Scan_Connected+timing+测试fail_f38d330a.jpg b/images/2+Scan_Connected+timing+测试fail_f38d330a.jpg
new file mode 100644
index 0000000..a4f214f
Binary files /dev/null and b/images/2+Scan_Connected+timing+测试fail_f38d330a.jpg differ
diff --git a/images/2+UI显示设备已关联到其他人的账号_df18e7d0.jpg b/images/2+UI显示设备已关联到其他人的账号_df18e7d0.jpg
new file mode 100644
index 0000000..8c12031
Binary files /dev/null and b/images/2+UI显示设备已关联到其他人的账号_df18e7d0.jpg differ
diff --git a/images/2+UI显示设备已关联到其他人的账号_ebfe3bb6.jpg b/images/2+UI显示设备已关联到其他人的账号_ebfe3bb6.jpg
new file mode 100644
index 0000000..8c12031
Binary files /dev/null and b/images/2+UI显示设备已关联到其他人的账号_ebfe3bb6.jpg differ
diff --git a/images/2.+耳机不支援LEA,+手机支援LEA_55144662.jpg b/images/2.+耳机不支援LEA,+手机支援LEA_55144662.jpg
new file mode 100644
index 0000000..a377630
Binary files /dev/null and b/images/2.+耳机不支援LEA,+手机支援LEA_55144662.jpg differ
diff --git a/images/2.+耳机不支援LEA,+手机支援LEA_630ee5b1.jpg b/images/2.+耳机不支援LEA,+手机支援LEA_630ee5b1.jpg
new file mode 100644
index 0000000..05b9d1f
Binary files /dev/null and b/images/2.+耳机不支援LEA,+手机支援LEA_630ee5b1.jpg differ
diff --git a/images/2.+耳机不支援LEA,+手机支援LEA_8d37087a.jpg b/images/2.+耳机不支援LEA,+手机支援LEA_8d37087a.jpg
new file mode 100644
index 0000000..58e9b8b
Binary files /dev/null and b/images/2.+耳机不支援LEA,+手机支援LEA_8d37087a.jpg differ
diff --git a/images/2.+耳机不支援LEA,+手机支援LEA_d0253de6.jpg b/images/2.+耳机不支援LEA,+手机支援LEA_d0253de6.jpg
new file mode 100644
index 0000000..a377630
Binary files /dev/null and b/images/2.+耳机不支援LEA,+手机支援LEA_d0253de6.jpg differ
diff --git a/images/2.+耳机不支援LEA,+手机支援LEA_d7ac6458.jpg b/images/2.+耳机不支援LEA,+手机支援LEA_d7ac6458.jpg
new file mode 100644
index 0000000..05b9d1f
Binary files /dev/null and b/images/2.+耳机不支援LEA,+手机支援LEA_d7ac6458.jpg differ
diff --git a/images/2.+耳机不支援LEA,+手机支援LEA_f57aa6c0.jpg b/images/2.+耳机不支援LEA,+手机支援LEA_f57aa6c0.jpg
new file mode 100644
index 0000000..58e9b8b
Binary files /dev/null and b/images/2.+耳机不支援LEA,+手机支援LEA_f57aa6c0.jpg differ
diff --git a/images/2.1+!!!gfps_handle_char_kbp_+failed,+result+3_321cba28.jpg b/images/2.1+!!!gfps_handle_char_kbp_+failed,+result+3_321cba28.jpg
new file mode 100644
index 0000000..2ef8ce0
Binary files /dev/null and b/images/2.1+!!!gfps_handle_char_kbp_+failed,+result+3_321cba28.jpg differ
diff --git a/images/2.1+!!!gfps_handle_char_kbp_+failed,+result+3_6e4ebc40.jpg b/images/2.1+!!!gfps_handle_char_kbp_+failed,+result+3_6e4ebc40.jpg
new file mode 100644
index 0000000..ddb60f2
Binary files /dev/null and b/images/2.1+!!!gfps_handle_char_kbp_+failed,+result+3_6e4ebc40.jpg differ
diff --git a/images/2.1+!!!gfps_handle_char_kbp_+failed,+result+3_7bc3ad54.jpg b/images/2.1+!!!gfps_handle_char_kbp_+failed,+result+3_7bc3ad54.jpg
new file mode 100644
index 0000000..ddb60f2
Binary files /dev/null and b/images/2.1+!!!gfps_handle_char_kbp_+failed,+result+3_7bc3ad54.jpg differ
diff --git a/images/2.1+!!!gfps_handle_char_kbp_+failed,+result+3_a4f6aa83.jpg b/images/2.1+!!!gfps_handle_char_kbp_+failed,+result+3_a4f6aa83.jpg
new file mode 100644
index 0000000..2ef8ce0
Binary files /dev/null and b/images/2.1+!!!gfps_handle_char_kbp_+failed,+result+3_a4f6aa83.jpg differ
diff --git a/images/2.2.1+设备端环境搭建_01e20658.jpg b/images/2.2.1+设备端环境搭建_01e20658.jpg
new file mode 100644
index 0000000..19538f0
Binary files /dev/null and b/images/2.2.1+设备端环境搭建_01e20658.jpg differ
diff --git a/images/2.2.1+设备端环境搭建_05cd32ff.jpg b/images/2.2.1+设备端环境搭建_05cd32ff.jpg
new file mode 100644
index 0000000..44aa483
Binary files /dev/null and b/images/2.2.1+设备端环境搭建_05cd32ff.jpg differ
diff --git a/images/2.2.1+设备端环境搭建_0853bf71.jpg b/images/2.2.1+设备端环境搭建_0853bf71.jpg
new file mode 100644
index 0000000..72ad6b6
Binary files /dev/null and b/images/2.2.1+设备端环境搭建_0853bf71.jpg differ
diff --git a/images/2.2.1+设备端环境搭建_0a5dff48.jpg b/images/2.2.1+设备端环境搭建_0a5dff48.jpg
new file mode 100644
index 0000000..e5ad8ea
Binary files /dev/null and b/images/2.2.1+设备端环境搭建_0a5dff48.jpg differ
diff --git a/images/2.2.1+设备端环境搭建_10721780.jpg b/images/2.2.1+设备端环境搭建_10721780.jpg
new file mode 100644
index 0000000..5883aeb
Binary files /dev/null and b/images/2.2.1+设备端环境搭建_10721780.jpg differ
diff --git a/images/2.2.1+设备端环境搭建_1760c626.jpg b/images/2.2.1+设备端环境搭建_1760c626.jpg
new file mode 100644
index 0000000..386696a
Binary files /dev/null and b/images/2.2.1+设备端环境搭建_1760c626.jpg differ
diff --git a/images/2.2.1+设备端环境搭建_176efe17.jpg b/images/2.2.1+设备端环境搭建_176efe17.jpg
new file mode 100644
index 0000000..afda906
Binary files /dev/null and b/images/2.2.1+设备端环境搭建_176efe17.jpg differ
diff --git a/images/2.2.1+设备端环境搭建_2106587b.jpg b/images/2.2.1+设备端环境搭建_2106587b.jpg
new file mode 100644
index 0000000..1699bb3
Binary files /dev/null and b/images/2.2.1+设备端环境搭建_2106587b.jpg differ
diff --git a/images/2.2.1+设备端环境搭建_22435b66.jpg b/images/2.2.1+设备端环境搭建_22435b66.jpg
new file mode 100644
index 0000000..6c88cec
Binary files /dev/null and b/images/2.2.1+设备端环境搭建_22435b66.jpg differ
diff --git a/images/2.2.1+设备端环境搭建_265eb83b.jpg b/images/2.2.1+设备端环境搭建_265eb83b.jpg
new file mode 100644
index 0000000..6b903d7
Binary files /dev/null and b/images/2.2.1+设备端环境搭建_265eb83b.jpg differ
diff --git a/images/2.2.1+设备端环境搭建_2b17cb35.jpg b/images/2.2.1+设备端环境搭建_2b17cb35.jpg
new file mode 100644
index 0000000..0918a08
Binary files /dev/null and b/images/2.2.1+设备端环境搭建_2b17cb35.jpg differ
diff --git a/images/2.2.1+设备端环境搭建_2e2e9207.jpg b/images/2.2.1+设备端环境搭建_2e2e9207.jpg
new file mode 100644
index 0000000..4898332
Binary files /dev/null and b/images/2.2.1+设备端环境搭建_2e2e9207.jpg differ
diff --git a/images/2.2.1+设备端环境搭建_319caf57.jpg b/images/2.2.1+设备端环境搭建_319caf57.jpg
new file mode 100644
index 0000000..44aa483
Binary files /dev/null and b/images/2.2.1+设备端环境搭建_319caf57.jpg differ
diff --git a/images/2.2.1+设备端环境搭建_3a8689f1.jpg b/images/2.2.1+设备端环境搭建_3a8689f1.jpg
new file mode 100644
index 0000000..93b4195
Binary files /dev/null and b/images/2.2.1+设备端环境搭建_3a8689f1.jpg differ
diff --git a/images/2.2.1+设备端环境搭建_3b50f6c4.jpg b/images/2.2.1+设备端环境搭建_3b50f6c4.jpg
new file mode 100644
index 0000000..013773f
Binary files /dev/null and b/images/2.2.1+设备端环境搭建_3b50f6c4.jpg differ
diff --git a/images/2.2.1+设备端环境搭建_42fa7300.jpg b/images/2.2.1+设备端环境搭建_42fa7300.jpg
new file mode 100644
index 0000000..0a86490
Binary files /dev/null and b/images/2.2.1+设备端环境搭建_42fa7300.jpg differ
diff --git a/images/2.2.1+设备端环境搭建_4ca2dfcf.jpg b/images/2.2.1+设备端环境搭建_4ca2dfcf.jpg
new file mode 100644
index 0000000..1699bb3
Binary files /dev/null and b/images/2.2.1+设备端环境搭建_4ca2dfcf.jpg differ
diff --git a/images/2.2.1+设备端环境搭建_4dd4e0b9.jpg b/images/2.2.1+设备端环境搭建_4dd4e0b9.jpg
new file mode 100644
index 0000000..e405626
Binary files /dev/null and b/images/2.2.1+设备端环境搭建_4dd4e0b9.jpg differ
diff --git a/images/2.2.1+设备端环境搭建_59432eff.jpg b/images/2.2.1+设备端环境搭建_59432eff.jpg
new file mode 100644
index 0000000..93b4195
Binary files /dev/null and b/images/2.2.1+设备端环境搭建_59432eff.jpg differ
diff --git a/images/2.2.1+设备端环境搭建_5b365bb0.jpg b/images/2.2.1+设备端环境搭建_5b365bb0.jpg
new file mode 100644
index 0000000..1144201
Binary files /dev/null and b/images/2.2.1+设备端环境搭建_5b365bb0.jpg differ
diff --git a/images/2.2.1+设备端环境搭建_5cceffb7.jpg b/images/2.2.1+设备端环境搭建_5cceffb7.jpg
new file mode 100644
index 0000000..78e4e1a
Binary files /dev/null and b/images/2.2.1+设备端环境搭建_5cceffb7.jpg differ
diff --git a/images/2.2.1+设备端环境搭建_5fc65599.jpg b/images/2.2.1+设备端环境搭建_5fc65599.jpg
new file mode 100644
index 0000000..0e69dd3
Binary files /dev/null and b/images/2.2.1+设备端环境搭建_5fc65599.jpg differ
diff --git a/images/2.2.1+设备端环境搭建_629c1520.jpg b/images/2.2.1+设备端环境搭建_629c1520.jpg
new file mode 100644
index 0000000..db704d5
Binary files /dev/null and b/images/2.2.1+设备端环境搭建_629c1520.jpg differ
diff --git a/images/2.2.1+设备端环境搭建_67e885b0.jpg b/images/2.2.1+设备端环境搭建_67e885b0.jpg
new file mode 100644
index 0000000..6c88cec
Binary files /dev/null and b/images/2.2.1+设备端环境搭建_67e885b0.jpg differ
diff --git a/images/2.2.1+设备端环境搭建_67eccec0.jpg b/images/2.2.1+设备端环境搭建_67eccec0.jpg
new file mode 100644
index 0000000..3ccf4f5
Binary files /dev/null and b/images/2.2.1+设备端环境搭建_67eccec0.jpg differ
diff --git a/images/2.2.1+设备端环境搭建_6aca2eff.jpg b/images/2.2.1+设备端环境搭建_6aca2eff.jpg
new file mode 100644
index 0000000..0918a08
Binary files /dev/null and b/images/2.2.1+设备端环境搭建_6aca2eff.jpg differ
diff --git a/images/2.2.1+设备端环境搭建_6ce7649f.jpg b/images/2.2.1+设备端环境搭建_6ce7649f.jpg
new file mode 100644
index 0000000..0e69dd3
Binary files /dev/null and b/images/2.2.1+设备端环境搭建_6ce7649f.jpg differ
diff --git a/images/2.2.1+设备端环境搭建_6de53ff7.jpg b/images/2.2.1+设备端环境搭建_6de53ff7.jpg
new file mode 100644
index 0000000..95dce9e
Binary files /dev/null and b/images/2.2.1+设备端环境搭建_6de53ff7.jpg differ
diff --git a/images/2.2.1+设备端环境搭建_6f81602c.jpg b/images/2.2.1+设备端环境搭建_6f81602c.jpg
new file mode 100644
index 0000000..f19a8ff
Binary files /dev/null and b/images/2.2.1+设备端环境搭建_6f81602c.jpg differ
diff --git a/images/2.2.1+设备端环境搭建_71a306fa.jpg b/images/2.2.1+设备端环境搭建_71a306fa.jpg
new file mode 100644
index 0000000..e5cd8dd
Binary files /dev/null and b/images/2.2.1+设备端环境搭建_71a306fa.jpg differ
diff --git a/images/2.2.1+设备端环境搭建_73fb31a9.jpg b/images/2.2.1+设备端环境搭建_73fb31a9.jpg
new file mode 100644
index 0000000..e5cd8dd
Binary files /dev/null and b/images/2.2.1+设备端环境搭建_73fb31a9.jpg differ
diff --git a/images/2.2.1+设备端环境搭建_75bb4f99.jpg b/images/2.2.1+设备端环境搭建_75bb4f99.jpg
new file mode 100644
index 0000000..f19a8ff
Binary files /dev/null and b/images/2.2.1+设备端环境搭建_75bb4f99.jpg differ
diff --git a/images/2.2.1+设备端环境搭建_7679c34e.jpg b/images/2.2.1+设备端环境搭建_7679c34e.jpg
new file mode 100644
index 0000000..54a3952
Binary files /dev/null and b/images/2.2.1+设备端环境搭建_7679c34e.jpg differ
diff --git a/images/2.2.1+设备端环境搭建_7c939b1b.jpg b/images/2.2.1+设备端环境搭建_7c939b1b.jpg
new file mode 100644
index 0000000..0a86490
Binary files /dev/null and b/images/2.2.1+设备端环境搭建_7c939b1b.jpg differ
diff --git a/images/2.2.1+设备端环境搭建_7d1153f1.jpg b/images/2.2.1+设备端环境搭建_7d1153f1.jpg
new file mode 100644
index 0000000..f8b4d5a
Binary files /dev/null and b/images/2.2.1+设备端环境搭建_7d1153f1.jpg differ
diff --git a/images/2.2.1+设备端环境搭建_7d783562.jpg b/images/2.2.1+设备端环境搭建_7d783562.jpg
new file mode 100644
index 0000000..0c2eee5
Binary files /dev/null and b/images/2.2.1+设备端环境搭建_7d783562.jpg differ
diff --git a/images/2.2.1+设备端环境搭建_83cc1a3c.jpg b/images/2.2.1+设备端环境搭建_83cc1a3c.jpg
new file mode 100644
index 0000000..9af42b6
Binary files /dev/null and b/images/2.2.1+设备端环境搭建_83cc1a3c.jpg differ
diff --git a/images/2.2.1+设备端环境搭建_8806cf01.jpg b/images/2.2.1+设备端环境搭建_8806cf01.jpg
new file mode 100644
index 0000000..c418c0d
Binary files /dev/null and b/images/2.2.1+设备端环境搭建_8806cf01.jpg differ
diff --git a/images/2.2.1+设备端环境搭建_8a4cb645.jpg b/images/2.2.1+设备端环境搭建_8a4cb645.jpg
new file mode 100644
index 0000000..78e4e1a
Binary files /dev/null and b/images/2.2.1+设备端环境搭建_8a4cb645.jpg differ
diff --git a/images/2.2.1+设备端环境搭建_90027c24.jpg b/images/2.2.1+设备端环境搭建_90027c24.jpg
new file mode 100644
index 0000000..c6ad91f
Binary files /dev/null and b/images/2.2.1+设备端环境搭建_90027c24.jpg differ
diff --git a/images/2.2.1+设备端环境搭建_938e8e81.jpg b/images/2.2.1+设备端环境搭建_938e8e81.jpg
new file mode 100644
index 0000000..c7c022b
Binary files /dev/null and b/images/2.2.1+设备端环境搭建_938e8e81.jpg differ
diff --git a/images/2.2.1+设备端环境搭建_9b86ffe1.jpg b/images/2.2.1+设备端环境搭建_9b86ffe1.jpg
new file mode 100644
index 0000000..9af42b6
Binary files /dev/null and b/images/2.2.1+设备端环境搭建_9b86ffe1.jpg differ
diff --git a/images/2.2.1+设备端环境搭建_9df186a7.jpg b/images/2.2.1+设备端环境搭建_9df186a7.jpg
new file mode 100644
index 0000000..386696a
Binary files /dev/null and b/images/2.2.1+设备端环境搭建_9df186a7.jpg differ
diff --git a/images/2.2.1+设备端环境搭建_a3b32eaf.jpg b/images/2.2.1+设备端环境搭建_a3b32eaf.jpg
new file mode 100644
index 0000000..d2665a4
Binary files /dev/null and b/images/2.2.1+设备端环境搭建_a3b32eaf.jpg differ
diff --git a/images/2.2.1+设备端环境搭建_a3e8d5c8.jpg b/images/2.2.1+设备端环境搭建_a3e8d5c8.jpg
new file mode 100644
index 0000000..2eae932
Binary files /dev/null and b/images/2.2.1+设备端环境搭建_a3e8d5c8.jpg differ
diff --git a/images/2.2.1+设备端环境搭建_a43bfa78.jpg b/images/2.2.1+设备端环境搭建_a43bfa78.jpg
new file mode 100644
index 0000000..54a3952
Binary files /dev/null and b/images/2.2.1+设备端环境搭建_a43bfa78.jpg differ
diff --git a/images/2.2.1+设备端环境搭建_a5469a1d.jpg b/images/2.2.1+设备端环境搭建_a5469a1d.jpg
new file mode 100644
index 0000000..db704d5
Binary files /dev/null and b/images/2.2.1+设备端环境搭建_a5469a1d.jpg differ
diff --git a/images/2.2.1+设备端环境搭建_a68ca167.jpg b/images/2.2.1+设备端环境搭建_a68ca167.jpg
new file mode 100644
index 0000000..19538f0
Binary files /dev/null and b/images/2.2.1+设备端环境搭建_a68ca167.jpg differ
diff --git a/images/2.2.1+设备端环境搭建_b109f957.jpg b/images/2.2.1+设备端环境搭建_b109f957.jpg
new file mode 100644
index 0000000..ee5cee0
Binary files /dev/null and b/images/2.2.1+设备端环境搭建_b109f957.jpg differ
diff --git a/images/2.2.1+设备端环境搭建_b1da60c4.jpg b/images/2.2.1+设备端环境搭建_b1da60c4.jpg
new file mode 100644
index 0000000..fb2c74b
Binary files /dev/null and b/images/2.2.1+设备端环境搭建_b1da60c4.jpg differ
diff --git a/images/2.2.1+设备端环境搭建_b61271af.jpg b/images/2.2.1+设备端环境搭建_b61271af.jpg
new file mode 100644
index 0000000..1144201
Binary files /dev/null and b/images/2.2.1+设备端环境搭建_b61271af.jpg differ
diff --git a/images/2.2.1+设备端环境搭建_bb98816c.jpg b/images/2.2.1+设备端环境搭建_bb98816c.jpg
new file mode 100644
index 0000000..3ccf4f5
Binary files /dev/null and b/images/2.2.1+设备端环境搭建_bb98816c.jpg differ
diff --git a/images/2.2.1+设备端环境搭建_bf2c956f.jpg b/images/2.2.1+设备端环境搭建_bf2c956f.jpg
new file mode 100644
index 0000000..f8b4d5a
Binary files /dev/null and b/images/2.2.1+设备端环境搭建_bf2c956f.jpg differ
diff --git a/images/2.2.1+设备端环境搭建_c1704049.jpg b/images/2.2.1+设备端环境搭建_c1704049.jpg
new file mode 100644
index 0000000..afda906
Binary files /dev/null and b/images/2.2.1+设备端环境搭建_c1704049.jpg differ
diff --git a/images/2.2.1+设备端环境搭建_c2e48143.jpg b/images/2.2.1+设备端环境搭建_c2e48143.jpg
new file mode 100644
index 0000000..6b903d7
Binary files /dev/null and b/images/2.2.1+设备端环境搭建_c2e48143.jpg differ
diff --git a/images/2.2.1+设备端环境搭建_c8a58a63.jpg b/images/2.2.1+设备端环境搭建_c8a58a63.jpg
new file mode 100644
index 0000000..e5ad8ea
Binary files /dev/null and b/images/2.2.1+设备端环境搭建_c8a58a63.jpg differ
diff --git a/images/2.2.1+设备端环境搭建_c9202c73.jpg b/images/2.2.1+设备端环境搭建_c9202c73.jpg
new file mode 100644
index 0000000..29508c7
Binary files /dev/null and b/images/2.2.1+设备端环境搭建_c9202c73.jpg differ
diff --git a/images/2.2.1+设备端环境搭建_c9315598.jpg b/images/2.2.1+设备端环境搭建_c9315598.jpg
new file mode 100644
index 0000000..56c2ce9
Binary files /dev/null and b/images/2.2.1+设备端环境搭建_c9315598.jpg differ
diff --git a/images/2.2.1+设备端环境搭建_cd631ac7.jpg b/images/2.2.1+设备端环境搭建_cd631ac7.jpg
new file mode 100644
index 0000000..c6ad91f
Binary files /dev/null and b/images/2.2.1+设备端环境搭建_cd631ac7.jpg differ
diff --git a/images/2.2.1+设备端环境搭建_cfd2080b.jpg b/images/2.2.1+设备端环境搭建_cfd2080b.jpg
new file mode 100644
index 0000000..4f4a53b
Binary files /dev/null and b/images/2.2.1+设备端环境搭建_cfd2080b.jpg differ
diff --git a/images/2.2.1+设备端环境搭建_d324db7f.jpg b/images/2.2.1+设备端环境搭建_d324db7f.jpg
new file mode 100644
index 0000000..0c2eee5
Binary files /dev/null and b/images/2.2.1+设备端环境搭建_d324db7f.jpg differ
diff --git a/images/2.2.1+设备端环境搭建_d4c22a9a.jpg b/images/2.2.1+设备端环境搭建_d4c22a9a.jpg
new file mode 100644
index 0000000..4898332
Binary files /dev/null and b/images/2.2.1+设备端环境搭建_d4c22a9a.jpg differ
diff --git a/images/2.2.1+设备端环境搭建_d57f0a59.jpg b/images/2.2.1+设备端环境搭建_d57f0a59.jpg
new file mode 100644
index 0000000..56c2ce9
Binary files /dev/null and b/images/2.2.1+设备端环境搭建_d57f0a59.jpg differ
diff --git a/images/2.2.1+设备端环境搭建_d995434b.jpg b/images/2.2.1+设备端环境搭建_d995434b.jpg
new file mode 100644
index 0000000..2eae932
Binary files /dev/null and b/images/2.2.1+设备端环境搭建_d995434b.jpg differ
diff --git a/images/2.2.1+设备端环境搭建_da041843.jpg b/images/2.2.1+设备端环境搭建_da041843.jpg
new file mode 100644
index 0000000..241e744
Binary files /dev/null and b/images/2.2.1+设备端环境搭建_da041843.jpg differ
diff --git a/images/2.2.1+设备端环境搭建_de20e722.jpg b/images/2.2.1+设备端环境搭建_de20e722.jpg
new file mode 100644
index 0000000..72ad6b6
Binary files /dev/null and b/images/2.2.1+设备端环境搭建_de20e722.jpg differ
diff --git a/images/2.2.1+设备端环境搭建_e21ecd75.jpg b/images/2.2.1+设备端环境搭建_e21ecd75.jpg
new file mode 100644
index 0000000..c7c022b
Binary files /dev/null and b/images/2.2.1+设备端环境搭建_e21ecd75.jpg differ
diff --git a/images/2.2.1+设备端环境搭建_e7898a15.jpg b/images/2.2.1+设备端环境搭建_e7898a15.jpg
new file mode 100644
index 0000000..fb2c74b
Binary files /dev/null and b/images/2.2.1+设备端环境搭建_e7898a15.jpg differ
diff --git a/images/2.2.1+设备端环境搭建_eb15be77.jpg b/images/2.2.1+设备端环境搭建_eb15be77.jpg
new file mode 100644
index 0000000..241e744
Binary files /dev/null and b/images/2.2.1+设备端环境搭建_eb15be77.jpg differ
diff --git a/images/2.2.1+设备端环境搭建_ec42890d.jpg b/images/2.2.1+设备端环境搭建_ec42890d.jpg
new file mode 100644
index 0000000..95dce9e
Binary files /dev/null and b/images/2.2.1+设备端环境搭建_ec42890d.jpg differ
diff --git a/images/2.2.1+设备端环境搭建_ed9d8238.jpg b/images/2.2.1+设备端环境搭建_ed9d8238.jpg
new file mode 100644
index 0000000..c418c0d
Binary files /dev/null and b/images/2.2.1+设备端环境搭建_ed9d8238.jpg differ
diff --git a/images/2.2.1+设备端环境搭建_eeb8e040.jpg b/images/2.2.1+设备端环境搭建_eeb8e040.jpg
new file mode 100644
index 0000000..4f4a53b
Binary files /dev/null and b/images/2.2.1+设备端环境搭建_eeb8e040.jpg differ
diff --git a/images/2.2.1+设备端环境搭建_f36d91e4.jpg b/images/2.2.1+设备端环境搭建_f36d91e4.jpg
new file mode 100644
index 0000000..e405626
Binary files /dev/null and b/images/2.2.1+设备端环境搭建_f36d91e4.jpg differ
diff --git a/images/2.2.1+设备端环境搭建_f3b5c168.jpg b/images/2.2.1+设备端环境搭建_f3b5c168.jpg
new file mode 100644
index 0000000..013773f
Binary files /dev/null and b/images/2.2.1+设备端环境搭建_f3b5c168.jpg differ
diff --git a/images/2.2.1+设备端环境搭建_f59441dd.jpg b/images/2.2.1+设备端环境搭建_f59441dd.jpg
new file mode 100644
index 0000000..ee5cee0
Binary files /dev/null and b/images/2.2.1+设备端环境搭建_f59441dd.jpg differ
diff --git a/images/2.2.1+设备端环境搭建_f83ef1ca.jpg b/images/2.2.1+设备端环境搭建_f83ef1ca.jpg
new file mode 100644
index 0000000..29508c7
Binary files /dev/null and b/images/2.2.1+设备端环境搭建_f83ef1ca.jpg differ
diff --git a/images/2.2.1+设备端环境搭建_f8873d22.jpg b/images/2.2.1+设备端环境搭建_f8873d22.jpg
new file mode 100644
index 0000000..d2665a4
Binary files /dev/null and b/images/2.2.1+设备端环境搭建_f8873d22.jpg differ
diff --git a/images/2.2.1+设备端环境搭建_fc498fe9.jpg b/images/2.2.1+设备端环境搭建_fc498fe9.jpg
new file mode 100644
index 0000000..5883aeb
Binary files /dev/null and b/images/2.2.1+设备端环境搭建_fc498fe9.jpg differ
diff --git a/images/2.2.2+手机端环境搭建_065ee5de.jpg b/images/2.2.2+手机端环境搭建_065ee5de.jpg
new file mode 100644
index 0000000..2b46edf
Binary files /dev/null and b/images/2.2.2+手机端环境搭建_065ee5de.jpg differ
diff --git a/images/2.2.2+手机端环境搭建_09f8c8e7.jpg b/images/2.2.2+手机端环境搭建_09f8c8e7.jpg
new file mode 100644
index 0000000..891808f
Binary files /dev/null and b/images/2.2.2+手机端环境搭建_09f8c8e7.jpg differ
diff --git a/images/2.2.2+手机端环境搭建_0af6c82e.jpg b/images/2.2.2+手机端环境搭建_0af6c82e.jpg
new file mode 100644
index 0000000..3742274
Binary files /dev/null and b/images/2.2.2+手机端环境搭建_0af6c82e.jpg differ
diff --git a/images/2.2.2+手机端环境搭建_0b6ee88b.jpg b/images/2.2.2+手机端环境搭建_0b6ee88b.jpg
new file mode 100644
index 0000000..b447433
Binary files /dev/null and b/images/2.2.2+手机端环境搭建_0b6ee88b.jpg differ
diff --git a/images/2.2.2+手机端环境搭建_1871c94f.jpg b/images/2.2.2+手机端环境搭建_1871c94f.jpg
new file mode 100644
index 0000000..5daf99d
Binary files /dev/null and b/images/2.2.2+手机端环境搭建_1871c94f.jpg differ
diff --git a/images/2.2.2+手机端环境搭建_1f9ad7c2.jpg b/images/2.2.2+手机端环境搭建_1f9ad7c2.jpg
new file mode 100644
index 0000000..9fda635
Binary files /dev/null and b/images/2.2.2+手机端环境搭建_1f9ad7c2.jpg differ
diff --git a/images/2.2.2+手机端环境搭建_221878de.jpg b/images/2.2.2+手机端环境搭建_221878de.jpg
new file mode 100644
index 0000000..4c1855f
Binary files /dev/null and b/images/2.2.2+手机端环境搭建_221878de.jpg differ
diff --git a/images/2.2.2+手机端环境搭建_2a92b7ce.jpg b/images/2.2.2+手机端环境搭建_2a92b7ce.jpg
new file mode 100644
index 0000000..631b957
Binary files /dev/null and b/images/2.2.2+手机端环境搭建_2a92b7ce.jpg differ
diff --git a/images/2.2.2+手机端环境搭建_2ef55f3d.jpg b/images/2.2.2+手机端环境搭建_2ef55f3d.jpg
new file mode 100644
index 0000000..631b957
Binary files /dev/null and b/images/2.2.2+手机端环境搭建_2ef55f3d.jpg differ
diff --git a/images/2.2.2+手机端环境搭建_38ba016d.jpg b/images/2.2.2+手机端环境搭建_38ba016d.jpg
new file mode 100644
index 0000000..c3def5e
Binary files /dev/null and b/images/2.2.2+手机端环境搭建_38ba016d.jpg differ
diff --git a/images/2.2.2+手机端环境搭建_391daab9.jpg b/images/2.2.2+手机端环境搭建_391daab9.jpg
new file mode 100644
index 0000000..2a1ff26
Binary files /dev/null and b/images/2.2.2+手机端环境搭建_391daab9.jpg differ
diff --git a/images/2.2.2+手机端环境搭建_3995aaf6.jpg b/images/2.2.2+手机端环境搭建_3995aaf6.jpg
new file mode 100644
index 0000000..3742274
Binary files /dev/null and b/images/2.2.2+手机端环境搭建_3995aaf6.jpg differ
diff --git a/images/2.2.2+手机端环境搭建_3b8637aa.jpg b/images/2.2.2+手机端环境搭建_3b8637aa.jpg
new file mode 100644
index 0000000..fcb7f36
Binary files /dev/null and b/images/2.2.2+手机端环境搭建_3b8637aa.jpg differ
diff --git a/images/2.2.2+手机端环境搭建_4eda2909.jpg b/images/2.2.2+手机端环境搭建_4eda2909.jpg
new file mode 100644
index 0000000..facfdbb
Binary files /dev/null and b/images/2.2.2+手机端环境搭建_4eda2909.jpg differ
diff --git a/images/2.2.2+手机端环境搭建_50c41446.jpg b/images/2.2.2+手机端环境搭建_50c41446.jpg
new file mode 100644
index 0000000..c3def5e
Binary files /dev/null and b/images/2.2.2+手机端环境搭建_50c41446.jpg differ
diff --git a/images/2.2.2+手机端环境搭建_518f2a71.jpg b/images/2.2.2+手机端环境搭建_518f2a71.jpg
new file mode 100644
index 0000000..6d2af57
Binary files /dev/null and b/images/2.2.2+手机端环境搭建_518f2a71.jpg differ
diff --git a/images/2.2.2+手机端环境搭建_530befda.jpg b/images/2.2.2+手机端环境搭建_530befda.jpg
new file mode 100644
index 0000000..1dda003
Binary files /dev/null and b/images/2.2.2+手机端环境搭建_530befda.jpg differ
diff --git a/images/2.2.2+手机端环境搭建_53d119de.jpg b/images/2.2.2+手机端环境搭建_53d119de.jpg
new file mode 100644
index 0000000..15ae088
Binary files /dev/null and b/images/2.2.2+手机端环境搭建_53d119de.jpg differ
diff --git a/images/2.2.2+手机端环境搭建_55785b16.jpg b/images/2.2.2+手机端环境搭建_55785b16.jpg
new file mode 100644
index 0000000..3f84e71
Binary files /dev/null and b/images/2.2.2+手机端环境搭建_55785b16.jpg differ
diff --git a/images/2.2.2+手机端环境搭建_57f59b7f.jpg b/images/2.2.2+手机端环境搭建_57f59b7f.jpg
new file mode 100644
index 0000000..a4ce3bd
Binary files /dev/null and b/images/2.2.2+手机端环境搭建_57f59b7f.jpg differ
diff --git a/images/2.2.2+手机端环境搭建_59fe7ccb.jpg b/images/2.2.2+手机端环境搭建_59fe7ccb.jpg
new file mode 100644
index 0000000..302ade0
Binary files /dev/null and b/images/2.2.2+手机端环境搭建_59fe7ccb.jpg differ
diff --git a/images/2.2.2+手机端环境搭建_5f8eb235.jpg b/images/2.2.2+手机端环境搭建_5f8eb235.jpg
new file mode 100644
index 0000000..58e9b8b
Binary files /dev/null and b/images/2.2.2+手机端环境搭建_5f8eb235.jpg differ
diff --git a/images/2.2.2+手机端环境搭建_6370bab0.jpg b/images/2.2.2+手机端环境搭建_6370bab0.jpg
new file mode 100644
index 0000000..b447433
Binary files /dev/null and b/images/2.2.2+手机端环境搭建_6370bab0.jpg differ
diff --git a/images/2.2.2+手机端环境搭建_6f2213d2.jpg b/images/2.2.2+手机端环境搭建_6f2213d2.jpg
new file mode 100644
index 0000000..9ed6549
Binary files /dev/null and b/images/2.2.2+手机端环境搭建_6f2213d2.jpg differ
diff --git a/images/2.2.2+手机端环境搭建_71ee4dab.jpg b/images/2.2.2+手机端环境搭建_71ee4dab.jpg
new file mode 100644
index 0000000..f8d9645
Binary files /dev/null and b/images/2.2.2+手机端环境搭建_71ee4dab.jpg differ
diff --git a/images/2.2.2+手机端环境搭建_72afb6eb.jpg b/images/2.2.2+手机端环境搭建_72afb6eb.jpg
new file mode 100644
index 0000000..1408b2d
Binary files /dev/null and b/images/2.2.2+手机端环境搭建_72afb6eb.jpg differ
diff --git a/images/2.2.2+手机端环境搭建_742e563c.jpg b/images/2.2.2+手机端环境搭建_742e563c.jpg
new file mode 100644
index 0000000..f8d9645
Binary files /dev/null and b/images/2.2.2+手机端环境搭建_742e563c.jpg differ
diff --git a/images/2.2.2+手机端环境搭建_755d8ae5.jpg b/images/2.2.2+手机端环境搭建_755d8ae5.jpg
new file mode 100644
index 0000000..c0e85e0
Binary files /dev/null and b/images/2.2.2+手机端环境搭建_755d8ae5.jpg differ
diff --git a/images/2.2.2+手机端环境搭建_7790d6c1.jpg b/images/2.2.2+手机端环境搭建_7790d6c1.jpg
new file mode 100644
index 0000000..1408b2d
Binary files /dev/null and b/images/2.2.2+手机端环境搭建_7790d6c1.jpg differ
diff --git a/images/2.2.2+手机端环境搭建_83074ab4.jpg b/images/2.2.2+手机端环境搭建_83074ab4.jpg
new file mode 100644
index 0000000..64d2e42
Binary files /dev/null and b/images/2.2.2+手机端环境搭建_83074ab4.jpg differ
diff --git a/images/2.2.2+手机端环境搭建_8a72c199.jpg b/images/2.2.2+手机端环境搭建_8a72c199.jpg
new file mode 100644
index 0000000..b84908a
Binary files /dev/null and b/images/2.2.2+手机端环境搭建_8a72c199.jpg differ
diff --git a/images/2.2.2+手机端环境搭建_8b07b076.jpg b/images/2.2.2+手机端环境搭建_8b07b076.jpg
new file mode 100644
index 0000000..c0e85e0
Binary files /dev/null and b/images/2.2.2+手机端环境搭建_8b07b076.jpg differ
diff --git a/images/2.2.2+手机端环境搭建_96e73018.jpg b/images/2.2.2+手机端环境搭建_96e73018.jpg
new file mode 100644
index 0000000..1dda003
Binary files /dev/null and b/images/2.2.2+手机端环境搭建_96e73018.jpg differ
diff --git a/images/2.2.2+手机端环境搭建_974fb425.jpg b/images/2.2.2+手机端环境搭建_974fb425.jpg
new file mode 100644
index 0000000..832578b
Binary files /dev/null and b/images/2.2.2+手机端环境搭建_974fb425.jpg differ
diff --git a/images/2.2.2+手机端环境搭建_a20fd455.jpg b/images/2.2.2+手机端环境搭建_a20fd455.jpg
new file mode 100644
index 0000000..a4ce3bd
Binary files /dev/null and b/images/2.2.2+手机端环境搭建_a20fd455.jpg differ
diff --git a/images/2.2.2+手机端环境搭建_a5acfdf7.jpg b/images/2.2.2+手机端环境搭建_a5acfdf7.jpg
new file mode 100644
index 0000000..4c1855f
Binary files /dev/null and b/images/2.2.2+手机端环境搭建_a5acfdf7.jpg differ
diff --git a/images/2.2.2+手机端环境搭建_a82d1777.jpg b/images/2.2.2+手机端环境搭建_a82d1777.jpg
new file mode 100644
index 0000000..832578b
Binary files /dev/null and b/images/2.2.2+手机端环境搭建_a82d1777.jpg differ
diff --git a/images/2.2.2+手机端环境搭建_aa150545.jpg b/images/2.2.2+手机端环境搭建_aa150545.jpg
new file mode 100644
index 0000000..58e9b8b
Binary files /dev/null and b/images/2.2.2+手机端环境搭建_aa150545.jpg differ
diff --git a/images/2.2.2+手机端环境搭建_b9289c10.jpg b/images/2.2.2+手机端环境搭建_b9289c10.jpg
new file mode 100644
index 0000000..302ade0
Binary files /dev/null and b/images/2.2.2+手机端环境搭建_b9289c10.jpg differ
diff --git a/images/2.2.2+手机端环境搭建_bad7ef45.jpg b/images/2.2.2+手机端环境搭建_bad7ef45.jpg
new file mode 100644
index 0000000..e2e2b1c
Binary files /dev/null and b/images/2.2.2+手机端环境搭建_bad7ef45.jpg differ
diff --git a/images/2.2.2+手机端环境搭建_c523ed72.jpg b/images/2.2.2+手机端环境搭建_c523ed72.jpg
new file mode 100644
index 0000000..2b46edf
Binary files /dev/null and b/images/2.2.2+手机端环境搭建_c523ed72.jpg differ
diff --git a/images/2.2.2+手机端环境搭建_c52519b2.jpg b/images/2.2.2+手机端环境搭建_c52519b2.jpg
new file mode 100644
index 0000000..b7ce1dd
Binary files /dev/null and b/images/2.2.2+手机端环境搭建_c52519b2.jpg differ
diff --git a/images/2.2.2+手机端环境搭建_cd49883d.jpg b/images/2.2.2+手机端环境搭建_cd49883d.jpg
new file mode 100644
index 0000000..fcb7f36
Binary files /dev/null and b/images/2.2.2+手机端环境搭建_cd49883d.jpg differ
diff --git a/images/2.2.2+手机端环境搭建_cf01db8b.jpg b/images/2.2.2+手机端环境搭建_cf01db8b.jpg
new file mode 100644
index 0000000..9fda635
Binary files /dev/null and b/images/2.2.2+手机端环境搭建_cf01db8b.jpg differ
diff --git a/images/2.2.2+手机端环境搭建_d0a01a8e.jpg b/images/2.2.2+手机端环境搭建_d0a01a8e.jpg
new file mode 100644
index 0000000..e93fb27
Binary files /dev/null and b/images/2.2.2+手机端环境搭建_d0a01a8e.jpg differ
diff --git a/images/2.2.2+手机端环境搭建_d1ff5bcd.jpg b/images/2.2.2+手机端环境搭建_d1ff5bcd.jpg
new file mode 100644
index 0000000..facfdbb
Binary files /dev/null and b/images/2.2.2+手机端环境搭建_d1ff5bcd.jpg differ
diff --git a/images/2.2.2+手机端环境搭建_d639baf2.jpg b/images/2.2.2+手机端环境搭建_d639baf2.jpg
new file mode 100644
index 0000000..e2e2b1c
Binary files /dev/null and b/images/2.2.2+手机端环境搭建_d639baf2.jpg differ
diff --git a/images/2.2.2+手机端环境搭建_d8dcf478.jpg b/images/2.2.2+手机端环境搭建_d8dcf478.jpg
new file mode 100644
index 0000000..891808f
Binary files /dev/null and b/images/2.2.2+手机端环境搭建_d8dcf478.jpg differ
diff --git a/images/2.2.2+手机端环境搭建_d92719fb.jpg b/images/2.2.2+手机端环境搭建_d92719fb.jpg
new file mode 100644
index 0000000..b7ce1dd
Binary files /dev/null and b/images/2.2.2+手机端环境搭建_d92719fb.jpg differ
diff --git a/images/2.2.2+手机端环境搭建_e134ccda.jpg b/images/2.2.2+手机端环境搭建_e134ccda.jpg
new file mode 100644
index 0000000..64d2e42
Binary files /dev/null and b/images/2.2.2+手机端环境搭建_e134ccda.jpg differ
diff --git a/images/2.2.2+手机端环境搭建_e2794111.jpg b/images/2.2.2+手机端环境搭建_e2794111.jpg
new file mode 100644
index 0000000..9ed6549
Binary files /dev/null and b/images/2.2.2+手机端环境搭建_e2794111.jpg differ
diff --git a/images/2.2.2+手机端环境搭建_e86d8403.jpg b/images/2.2.2+手机端环境搭建_e86d8403.jpg
new file mode 100644
index 0000000..5daf99d
Binary files /dev/null and b/images/2.2.2+手机端环境搭建_e86d8403.jpg differ
diff --git a/images/2.2.2+手机端环境搭建_e9de08f7.jpg b/images/2.2.2+手机端环境搭建_e9de08f7.jpg
new file mode 100644
index 0000000..e93fb27
Binary files /dev/null and b/images/2.2.2+手机端环境搭建_e9de08f7.jpg differ
diff --git a/images/2.2.2+手机端环境搭建_eb7c1957.jpg b/images/2.2.2+手机端环境搭建_eb7c1957.jpg
new file mode 100644
index 0000000..6d2af57
Binary files /dev/null and b/images/2.2.2+手机端环境搭建_eb7c1957.jpg differ
diff --git a/images/2.2.2+手机端环境搭建_ed548277.jpg b/images/2.2.2+手机端环境搭建_ed548277.jpg
new file mode 100644
index 0000000..15ae088
Binary files /dev/null and b/images/2.2.2+手机端环境搭建_ed548277.jpg differ
diff --git a/images/2.2.2+手机端环境搭建_f2eb6f94.jpg b/images/2.2.2+手机端环境搭建_f2eb6f94.jpg
new file mode 100644
index 0000000..de363b1
Binary files /dev/null and b/images/2.2.2+手机端环境搭建_f2eb6f94.jpg differ
diff --git a/images/2.2.2+手机端环境搭建_f31d5963.jpg b/images/2.2.2+手机端环境搭建_f31d5963.jpg
new file mode 100644
index 0000000..2a1ff26
Binary files /dev/null and b/images/2.2.2+手机端环境搭建_f31d5963.jpg differ
diff --git a/images/2.2.2+手机端环境搭建_f4e30409.jpg b/images/2.2.2+手机端环境搭建_f4e30409.jpg
new file mode 100644
index 0000000..3f84e71
Binary files /dev/null and b/images/2.2.2+手机端环境搭建_f4e30409.jpg differ
diff --git a/images/2.2.2+手机端环境搭建_f974af07.jpg b/images/2.2.2+手机端环境搭建_f974af07.jpg
new file mode 100644
index 0000000..b84908a
Binary files /dev/null and b/images/2.2.2+手机端环境搭建_f974af07.jpg differ
diff --git a/images/2.2.2+手机端环境搭建_fc4a7274.jpg b/images/2.2.2+手机端环境搭建_fc4a7274.jpg
new file mode 100644
index 0000000..de363b1
Binary files /dev/null and b/images/2.2.2+手机端环境搭建_fc4a7274.jpg differ
diff --git a/images/2.2.3+Fast+Pair+Validator+环境搭建_015f20be.jpg b/images/2.2.3+Fast+Pair+Validator+环境搭建_015f20be.jpg
new file mode 100644
index 0000000..3f84e71
Binary files /dev/null and b/images/2.2.3+Fast+Pair+Validator+环境搭建_015f20be.jpg differ
diff --git a/images/2.2.3+Fast+Pair+Validator+环境搭建_035bbf2a.jpg b/images/2.2.3+Fast+Pair+Validator+环境搭建_035bbf2a.jpg
new file mode 100644
index 0000000..631b957
Binary files /dev/null and b/images/2.2.3+Fast+Pair+Validator+环境搭建_035bbf2a.jpg differ
diff --git a/images/2.2.3+Fast+Pair+Validator+环境搭建_040ed07b.jpg b/images/2.2.3+Fast+Pair+Validator+环境搭建_040ed07b.jpg
new file mode 100644
index 0000000..facfdbb
Binary files /dev/null and b/images/2.2.3+Fast+Pair+Validator+环境搭建_040ed07b.jpg differ
diff --git a/images/2.2.3+Fast+Pair+Validator+环境搭建_0ead506f.jpg b/images/2.2.3+Fast+Pair+Validator+环境搭建_0ead506f.jpg
new file mode 100644
index 0000000..53ef204
Binary files /dev/null and b/images/2.2.3+Fast+Pair+Validator+环境搭建_0ead506f.jpg differ
diff --git a/images/2.2.3+Fast+Pair+Validator+环境搭建_17160479.jpg b/images/2.2.3+Fast+Pair+Validator+环境搭建_17160479.jpg
new file mode 100644
index 0000000..6ec45ec
Binary files /dev/null and b/images/2.2.3+Fast+Pair+Validator+环境搭建_17160479.jpg differ
diff --git a/images/2.2.3+Fast+Pair+Validator+环境搭建_171815d6.jpg b/images/2.2.3+Fast+Pair+Validator+环境搭建_171815d6.jpg
new file mode 100644
index 0000000..64d2e42
Binary files /dev/null and b/images/2.2.3+Fast+Pair+Validator+环境搭建_171815d6.jpg differ
diff --git a/images/2.2.3+Fast+Pair+Validator+环境搭建_19b194cb.jpg b/images/2.2.3+Fast+Pair+Validator+环境搭建_19b194cb.jpg
new file mode 100644
index 0000000..071d3f9
Binary files /dev/null and b/images/2.2.3+Fast+Pair+Validator+环境搭建_19b194cb.jpg differ
diff --git a/images/2.2.3+Fast+Pair+Validator+环境搭建_1f22d450.jpg b/images/2.2.3+Fast+Pair+Validator+环境搭建_1f22d450.jpg
new file mode 100644
index 0000000..58e9b8b
Binary files /dev/null and b/images/2.2.3+Fast+Pair+Validator+环境搭建_1f22d450.jpg differ
diff --git a/images/2.2.3+Fast+Pair+Validator+环境搭建_242dbb0d.jpg b/images/2.2.3+Fast+Pair+Validator+环境搭建_242dbb0d.jpg
new file mode 100644
index 0000000..071d3f9
Binary files /dev/null and b/images/2.2.3+Fast+Pair+Validator+环境搭建_242dbb0d.jpg differ
diff --git a/images/2.2.3+Fast+Pair+Validator+环境搭建_2fef4e2a.jpg b/images/2.2.3+Fast+Pair+Validator+环境搭建_2fef4e2a.jpg
new file mode 100644
index 0000000..2b46edf
Binary files /dev/null and b/images/2.2.3+Fast+Pair+Validator+环境搭建_2fef4e2a.jpg differ
diff --git a/images/2.2.3+Fast+Pair+Validator+环境搭建_3c90bfa8.jpg b/images/2.2.3+Fast+Pair+Validator+环境搭建_3c90bfa8.jpg
new file mode 100644
index 0000000..6d2af57
Binary files /dev/null and b/images/2.2.3+Fast+Pair+Validator+环境搭建_3c90bfa8.jpg differ
diff --git a/images/2.2.3+Fast+Pair+Validator+环境搭建_3e4bbf61.jpg b/images/2.2.3+Fast+Pair+Validator+环境搭建_3e4bbf61.jpg
new file mode 100644
index 0000000..b84908a
Binary files /dev/null and b/images/2.2.3+Fast+Pair+Validator+环境搭建_3e4bbf61.jpg differ
diff --git a/images/2.2.3+Fast+Pair+Validator+环境搭建_43e875d7.jpg b/images/2.2.3+Fast+Pair+Validator+环境搭建_43e875d7.jpg
new file mode 100644
index 0000000..c7ccda3
Binary files /dev/null and b/images/2.2.3+Fast+Pair+Validator+环境搭建_43e875d7.jpg differ
diff --git a/images/2.2.3+Fast+Pair+Validator+环境搭建_4d8385bd.jpg b/images/2.2.3+Fast+Pair+Validator+环境搭建_4d8385bd.jpg
new file mode 100644
index 0000000..c5bbb74
Binary files /dev/null and b/images/2.2.3+Fast+Pair+Validator+环境搭建_4d8385bd.jpg differ
diff --git a/images/2.2.3+Fast+Pair+Validator+环境搭建_4db6969d.jpg b/images/2.2.3+Fast+Pair+Validator+环境搭建_4db6969d.jpg
new file mode 100644
index 0000000..a80fc45
Binary files /dev/null and b/images/2.2.3+Fast+Pair+Validator+环境搭建_4db6969d.jpg differ
diff --git a/images/2.2.3+Fast+Pair+Validator+环境搭建_4fd78a1d.jpg b/images/2.2.3+Fast+Pair+Validator+环境搭建_4fd78a1d.jpg
new file mode 100644
index 0000000..9ed6549
Binary files /dev/null and b/images/2.2.3+Fast+Pair+Validator+环境搭建_4fd78a1d.jpg differ
diff --git a/images/2.2.3+Fast+Pair+Validator+环境搭建_549d1e0f.jpg b/images/2.2.3+Fast+Pair+Validator+环境搭建_549d1e0f.jpg
new file mode 100644
index 0000000..15ae088
Binary files /dev/null and b/images/2.2.3+Fast+Pair+Validator+环境搭建_549d1e0f.jpg differ
diff --git a/images/2.2.3+Fast+Pair+Validator+环境搭建_5c71ef86.jpg b/images/2.2.3+Fast+Pair+Validator+环境搭建_5c71ef86.jpg
new file mode 100644
index 0000000..9ed6549
Binary files /dev/null and b/images/2.2.3+Fast+Pair+Validator+环境搭建_5c71ef86.jpg differ
diff --git a/images/2.2.3+Fast+Pair+Validator+环境搭建_614b0e7f.jpg b/images/2.2.3+Fast+Pair+Validator+环境搭建_614b0e7f.jpg
new file mode 100644
index 0000000..1af0580
Binary files /dev/null and b/images/2.2.3+Fast+Pair+Validator+环境搭建_614b0e7f.jpg differ
diff --git a/images/2.2.3+Fast+Pair+Validator+环境搭建_672088f4.jpg b/images/2.2.3+Fast+Pair+Validator+环境搭建_672088f4.jpg
new file mode 100644
index 0000000..2a1ff26
Binary files /dev/null and b/images/2.2.3+Fast+Pair+Validator+环境搭建_672088f4.jpg differ
diff --git a/images/2.2.3+Fast+Pair+Validator+环境搭建_67e112b8.jpg b/images/2.2.3+Fast+Pair+Validator+环境搭建_67e112b8.jpg
new file mode 100644
index 0000000..2a1ff26
Binary files /dev/null and b/images/2.2.3+Fast+Pair+Validator+环境搭建_67e112b8.jpg differ
diff --git a/images/2.2.3+Fast+Pair+Validator+环境搭建_6d1d6795.jpg b/images/2.2.3+Fast+Pair+Validator+环境搭建_6d1d6795.jpg
new file mode 100644
index 0000000..3f84e71
Binary files /dev/null and b/images/2.2.3+Fast+Pair+Validator+环境搭建_6d1d6795.jpg differ
diff --git a/images/2.2.3+Fast+Pair+Validator+环境搭建_6e7ad7fd.jpg b/images/2.2.3+Fast+Pair+Validator+环境搭建_6e7ad7fd.jpg
new file mode 100644
index 0000000..ab658c5
Binary files /dev/null and b/images/2.2.3+Fast+Pair+Validator+环境搭建_6e7ad7fd.jpg differ
diff --git a/images/2.2.3+Fast+Pair+Validator+环境搭建_70fb11ff.jpg b/images/2.2.3+Fast+Pair+Validator+环境搭建_70fb11ff.jpg
new file mode 100644
index 0000000..c7ccda3
Binary files /dev/null and b/images/2.2.3+Fast+Pair+Validator+环境搭建_70fb11ff.jpg differ
diff --git a/images/2.2.3+Fast+Pair+Validator+环境搭建_796cc135.jpg b/images/2.2.3+Fast+Pair+Validator+环境搭建_796cc135.jpg
new file mode 100644
index 0000000..b4477df
Binary files /dev/null and b/images/2.2.3+Fast+Pair+Validator+环境搭建_796cc135.jpg differ
diff --git a/images/2.2.3+Fast+Pair+Validator+环境搭建_7a7cf8a1.jpg b/images/2.2.3+Fast+Pair+Validator+环境搭建_7a7cf8a1.jpg
new file mode 100644
index 0000000..facfdbb
Binary files /dev/null and b/images/2.2.3+Fast+Pair+Validator+环境搭建_7a7cf8a1.jpg differ
diff --git a/images/2.2.3+Fast+Pair+Validator+环境搭建_7c5af012.jpg b/images/2.2.3+Fast+Pair+Validator+环境搭建_7c5af012.jpg
new file mode 100644
index 0000000..15ae088
Binary files /dev/null and b/images/2.2.3+Fast+Pair+Validator+环境搭建_7c5af012.jpg differ
diff --git a/images/2.2.3+Fast+Pair+Validator+环境搭建_81482d9c.jpg b/images/2.2.3+Fast+Pair+Validator+环境搭建_81482d9c.jpg
new file mode 100644
index 0000000..b4477df
Binary files /dev/null and b/images/2.2.3+Fast+Pair+Validator+环境搭建_81482d9c.jpg differ
diff --git a/images/2.2.3+Fast+Pair+Validator+环境搭建_87b40ca2.jpg b/images/2.2.3+Fast+Pair+Validator+环境搭建_87b40ca2.jpg
new file mode 100644
index 0000000..c3def5e
Binary files /dev/null and b/images/2.2.3+Fast+Pair+Validator+环境搭建_87b40ca2.jpg differ
diff --git a/images/2.2.3+Fast+Pair+Validator+环境搭建_8cc5b6a5.jpg b/images/2.2.3+Fast+Pair+Validator+环境搭建_8cc5b6a5.jpg
new file mode 100644
index 0000000..4c1855f
Binary files /dev/null and b/images/2.2.3+Fast+Pair+Validator+环境搭建_8cc5b6a5.jpg differ
diff --git a/images/2.2.3+Fast+Pair+Validator+环境搭建_8fe6f383.jpg b/images/2.2.3+Fast+Pair+Validator+环境搭建_8fe6f383.jpg
new file mode 100644
index 0000000..b7ce1dd
Binary files /dev/null and b/images/2.2.3+Fast+Pair+Validator+环境搭建_8fe6f383.jpg differ
diff --git a/images/2.2.3+Fast+Pair+Validator+环境搭建_9525effa.jpg b/images/2.2.3+Fast+Pair+Validator+环境搭建_9525effa.jpg
new file mode 100644
index 0000000..b447433
Binary files /dev/null and b/images/2.2.3+Fast+Pair+Validator+环境搭建_9525effa.jpg differ
diff --git a/images/2.2.3+Fast+Pair+Validator+环境搭建_a0b640a3.jpg b/images/2.2.3+Fast+Pair+Validator+环境搭建_a0b640a3.jpg
new file mode 100644
index 0000000..b447433
Binary files /dev/null and b/images/2.2.3+Fast+Pair+Validator+环境搭建_a0b640a3.jpg differ
diff --git a/images/2.2.3+Fast+Pair+Validator+环境搭建_a17e0dd3.jpg b/images/2.2.3+Fast+Pair+Validator+环境搭建_a17e0dd3.jpg
new file mode 100644
index 0000000..1dda003
Binary files /dev/null and b/images/2.2.3+Fast+Pair+Validator+环境搭建_a17e0dd3.jpg differ
diff --git a/images/2.2.3+Fast+Pair+Validator+环境搭建_a3c459f1.jpg b/images/2.2.3+Fast+Pair+Validator+环境搭建_a3c459f1.jpg
new file mode 100644
index 0000000..b7ce1dd
Binary files /dev/null and b/images/2.2.3+Fast+Pair+Validator+环境搭建_a3c459f1.jpg differ
diff --git a/images/2.2.3+Fast+Pair+Validator+环境搭建_a4886bc2.jpg b/images/2.2.3+Fast+Pair+Validator+环境搭建_a4886bc2.jpg
new file mode 100644
index 0000000..6a7bd33
Binary files /dev/null and b/images/2.2.3+Fast+Pair+Validator+环境搭建_a4886bc2.jpg differ
diff --git a/images/2.2.3+Fast+Pair+Validator+环境搭建_a80df178.jpg b/images/2.2.3+Fast+Pair+Validator+环境搭建_a80df178.jpg
new file mode 100644
index 0000000..302ade0
Binary files /dev/null and b/images/2.2.3+Fast+Pair+Validator+环境搭建_a80df178.jpg differ
diff --git a/images/2.2.3+Fast+Pair+Validator+环境搭建_adb3e962.jpg b/images/2.2.3+Fast+Pair+Validator+环境搭建_adb3e962.jpg
new file mode 100644
index 0000000..a80fc45
Binary files /dev/null and b/images/2.2.3+Fast+Pair+Validator+环境搭建_adb3e962.jpg differ
diff --git a/images/2.2.3+Fast+Pair+Validator+环境搭建_af3d84be.jpg b/images/2.2.3+Fast+Pair+Validator+环境搭建_af3d84be.jpg
new file mode 100644
index 0000000..7dcfef7
Binary files /dev/null and b/images/2.2.3+Fast+Pair+Validator+环境搭建_af3d84be.jpg differ
diff --git a/images/2.2.3+Fast+Pair+Validator+环境搭建_afb9a593.jpg b/images/2.2.3+Fast+Pair+Validator+环境搭建_afb9a593.jpg
new file mode 100644
index 0000000..ab658c5
Binary files /dev/null and b/images/2.2.3+Fast+Pair+Validator+环境搭建_afb9a593.jpg differ
diff --git a/images/2.2.3+Fast+Pair+Validator+环境搭建_afbf1587.jpg b/images/2.2.3+Fast+Pair+Validator+环境搭建_afbf1587.jpg
new file mode 100644
index 0000000..302ade0
Binary files /dev/null and b/images/2.2.3+Fast+Pair+Validator+环境搭建_afbf1587.jpg differ
diff --git a/images/2.2.3+Fast+Pair+Validator+环境搭建_b542b518.jpg b/images/2.2.3+Fast+Pair+Validator+环境搭建_b542b518.jpg
new file mode 100644
index 0000000..1af0580
Binary files /dev/null and b/images/2.2.3+Fast+Pair+Validator+环境搭建_b542b518.jpg differ
diff --git a/images/2.2.3+Fast+Pair+Validator+环境搭建_b61f2cd1.jpg b/images/2.2.3+Fast+Pair+Validator+环境搭建_b61f2cd1.jpg
new file mode 100644
index 0000000..c0e85e0
Binary files /dev/null and b/images/2.2.3+Fast+Pair+Validator+环境搭建_b61f2cd1.jpg differ
diff --git a/images/2.2.3+Fast+Pair+Validator+环境搭建_b898d0f0.jpg b/images/2.2.3+Fast+Pair+Validator+环境搭建_b898d0f0.jpg
new file mode 100644
index 0000000..c3def5e
Binary files /dev/null and b/images/2.2.3+Fast+Pair+Validator+环境搭建_b898d0f0.jpg differ
diff --git a/images/2.2.3+Fast+Pair+Validator+环境搭建_bab2e72e.jpg b/images/2.2.3+Fast+Pair+Validator+环境搭建_bab2e72e.jpg
new file mode 100644
index 0000000..7dcfef7
Binary files /dev/null and b/images/2.2.3+Fast+Pair+Validator+环境搭建_bab2e72e.jpg differ
diff --git a/images/2.2.3+Fast+Pair+Validator+环境搭建_bd193d26.jpg b/images/2.2.3+Fast+Pair+Validator+环境搭建_bd193d26.jpg
new file mode 100644
index 0000000..1dda003
Binary files /dev/null and b/images/2.2.3+Fast+Pair+Validator+环境搭建_bd193d26.jpg differ
diff --git a/images/2.2.3+Fast+Pair+Validator+环境搭建_c1ad2bb2.jpg b/images/2.2.3+Fast+Pair+Validator+环境搭建_c1ad2bb2.jpg
new file mode 100644
index 0000000..6d2af57
Binary files /dev/null and b/images/2.2.3+Fast+Pair+Validator+环境搭建_c1ad2bb2.jpg differ
diff --git a/images/2.2.3+Fast+Pair+Validator+环境搭建_c2821619.jpg b/images/2.2.3+Fast+Pair+Validator+环境搭建_c2821619.jpg
new file mode 100644
index 0000000..53ef204
Binary files /dev/null and b/images/2.2.3+Fast+Pair+Validator+环境搭建_c2821619.jpg differ
diff --git a/images/2.2.3+Fast+Pair+Validator+环境搭建_c44a9a35.jpg b/images/2.2.3+Fast+Pair+Validator+环境搭建_c44a9a35.jpg
new file mode 100644
index 0000000..6a7bd33
Binary files /dev/null and b/images/2.2.3+Fast+Pair+Validator+环境搭建_c44a9a35.jpg differ
diff --git a/images/2.2.3+Fast+Pair+Validator+环境搭建_caeff4d6.jpg b/images/2.2.3+Fast+Pair+Validator+环境搭建_caeff4d6.jpg
new file mode 100644
index 0000000..4c1855f
Binary files /dev/null and b/images/2.2.3+Fast+Pair+Validator+环境搭建_caeff4d6.jpg differ
diff --git a/images/2.2.3+Fast+Pair+Validator+环境搭建_cd792601.jpg b/images/2.2.3+Fast+Pair+Validator+环境搭建_cd792601.jpg
new file mode 100644
index 0000000..503cb7d
Binary files /dev/null and b/images/2.2.3+Fast+Pair+Validator+环境搭建_cd792601.jpg differ
diff --git a/images/2.2.3+Fast+Pair+Validator+环境搭建_d941b338.jpg b/images/2.2.3+Fast+Pair+Validator+环境搭建_d941b338.jpg
new file mode 100644
index 0000000..2b46edf
Binary files /dev/null and b/images/2.2.3+Fast+Pair+Validator+环境搭建_d941b338.jpg differ
diff --git a/images/2.2.3+Fast+Pair+Validator+环境搭建_dab840d3.jpg b/images/2.2.3+Fast+Pair+Validator+环境搭建_dab840d3.jpg
new file mode 100644
index 0000000..6ec45ec
Binary files /dev/null and b/images/2.2.3+Fast+Pair+Validator+环境搭建_dab840d3.jpg differ
diff --git a/images/2.2.3+Fast+Pair+Validator+环境搭建_dd8e2c78.jpg b/images/2.2.3+Fast+Pair+Validator+环境搭建_dd8e2c78.jpg
new file mode 100644
index 0000000..58e9b8b
Binary files /dev/null and b/images/2.2.3+Fast+Pair+Validator+环境搭建_dd8e2c78.jpg differ
diff --git a/images/2.2.3+Fast+Pair+Validator+环境搭建_e002872e.jpg b/images/2.2.3+Fast+Pair+Validator+环境搭建_e002872e.jpg
new file mode 100644
index 0000000..64d2e42
Binary files /dev/null and b/images/2.2.3+Fast+Pair+Validator+环境搭建_e002872e.jpg differ
diff --git a/images/2.2.3+Fast+Pair+Validator+环境搭建_e0149494.jpg b/images/2.2.3+Fast+Pair+Validator+环境搭建_e0149494.jpg
new file mode 100644
index 0000000..c0e85e0
Binary files /dev/null and b/images/2.2.3+Fast+Pair+Validator+环境搭建_e0149494.jpg differ
diff --git a/images/2.2.3+Fast+Pair+Validator+环境搭建_e16b08f0.jpg b/images/2.2.3+Fast+Pair+Validator+环境搭建_e16b08f0.jpg
new file mode 100644
index 0000000..631b957
Binary files /dev/null and b/images/2.2.3+Fast+Pair+Validator+环境搭建_e16b08f0.jpg differ
diff --git a/images/2.2.3+Fast+Pair+Validator+环境搭建_ee9f3a72.jpg b/images/2.2.3+Fast+Pair+Validator+环境搭建_ee9f3a72.jpg
new file mode 100644
index 0000000..503cb7d
Binary files /dev/null and b/images/2.2.3+Fast+Pair+Validator+环境搭建_ee9f3a72.jpg differ
diff --git a/images/2.2.3+Fast+Pair+Validator+环境搭建_f5f07b2a.jpg b/images/2.2.3+Fast+Pair+Validator+环境搭建_f5f07b2a.jpg
new file mode 100644
index 0000000..c5bbb74
Binary files /dev/null and b/images/2.2.3+Fast+Pair+Validator+环境搭建_f5f07b2a.jpg differ
diff --git a/images/2.2.3+Fast+Pair+Validator+环境搭建_fe2fd06f.jpg b/images/2.2.3+Fast+Pair+Validator+环境搭建_fe2fd06f.jpg
new file mode 100644
index 0000000..b84908a
Binary files /dev/null and b/images/2.2.3+Fast+Pair+Validator+环境搭建_fe2fd06f.jpg differ
diff --git a/images/2.3+测试_140e2f2b.jpg b/images/2.3+测试_140e2f2b.jpg
new file mode 100644
index 0000000..af58731
Binary files /dev/null and b/images/2.3+测试_140e2f2b.jpg differ
diff --git a/images/2.3+测试_2d2c083d.jpg b/images/2.3+测试_2d2c083d.jpg
new file mode 100644
index 0000000..af58731
Binary files /dev/null and b/images/2.3+测试_2d2c083d.jpg differ
diff --git a/images/2.3.1+Fast+Pair+Validator测试_4fd09b89.jpg b/images/2.3.1+Fast+Pair+Validator测试_4fd09b89.jpg
new file mode 100644
index 0000000..240e358
Binary files /dev/null and b/images/2.3.1+Fast+Pair+Validator测试_4fd09b89.jpg differ
diff --git a/images/2.3.1+Fast+Pair+Validator测试_a9ad4980.jpg b/images/2.3.1+Fast+Pair+Validator测试_a9ad4980.jpg
new file mode 100644
index 0000000..240e358
Binary files /dev/null and b/images/2.3.1+Fast+Pair+Validator测试_a9ad4980.jpg differ
diff --git a/images/2.3.1.1+FAST+PAIR_0042d878.jpg b/images/2.3.1.1+FAST+PAIR_0042d878.jpg
new file mode 100644
index 0000000..6265c1b
Binary files /dev/null and b/images/2.3.1.1+FAST+PAIR_0042d878.jpg differ
diff --git a/images/2.3.1.1+FAST+PAIR_01b013f0.jpg b/images/2.3.1.1+FAST+PAIR_01b013f0.jpg
new file mode 100644
index 0000000..fa50efb
Binary files /dev/null and b/images/2.3.1.1+FAST+PAIR_01b013f0.jpg differ
diff --git a/images/2.3.1.1+FAST+PAIR_01e88241.jpg b/images/2.3.1.1+FAST+PAIR_01e88241.jpg
new file mode 100644
index 0000000..ad4f24e
Binary files /dev/null and b/images/2.3.1.1+FAST+PAIR_01e88241.jpg differ
diff --git a/images/2.3.1.1+FAST+PAIR_06c4dd4b.jpg b/images/2.3.1.1+FAST+PAIR_06c4dd4b.jpg
new file mode 100644
index 0000000..9e0995e
Binary files /dev/null and b/images/2.3.1.1+FAST+PAIR_06c4dd4b.jpg differ
diff --git a/images/2.3.1.1+FAST+PAIR_099e2862.jpg b/images/2.3.1.1+FAST+PAIR_099e2862.jpg
new file mode 100644
index 0000000..e16373b
Binary files /dev/null and b/images/2.3.1.1+FAST+PAIR_099e2862.jpg differ
diff --git a/images/2.3.1.1+FAST+PAIR_0a95a121.jpg b/images/2.3.1.1+FAST+PAIR_0a95a121.jpg
new file mode 100644
index 0000000..ce54135
Binary files /dev/null and b/images/2.3.1.1+FAST+PAIR_0a95a121.jpg differ
diff --git a/images/2.3.1.1+FAST+PAIR_0d4f57e8.jpg b/images/2.3.1.1+FAST+PAIR_0d4f57e8.jpg
new file mode 100644
index 0000000..e16373b
Binary files /dev/null and b/images/2.3.1.1+FAST+PAIR_0d4f57e8.jpg differ
diff --git a/images/2.3.1.1+FAST+PAIR_103177cc.jpg b/images/2.3.1.1+FAST+PAIR_103177cc.jpg
new file mode 100644
index 0000000..6a77749
Binary files /dev/null and b/images/2.3.1.1+FAST+PAIR_103177cc.jpg differ
diff --git a/images/2.3.1.1+FAST+PAIR_10b5dc7b.jpg b/images/2.3.1.1+FAST+PAIR_10b5dc7b.jpg
new file mode 100644
index 0000000..ad4f24e
Binary files /dev/null and b/images/2.3.1.1+FAST+PAIR_10b5dc7b.jpg differ
diff --git a/images/2.3.1.1+FAST+PAIR_1215e4ce.jpg b/images/2.3.1.1+FAST+PAIR_1215e4ce.jpg
new file mode 100644
index 0000000..d207df6
Binary files /dev/null and b/images/2.3.1.1+FAST+PAIR_1215e4ce.jpg differ
diff --git a/images/2.3.1.1+FAST+PAIR_15e52a00.jpg b/images/2.3.1.1+FAST+PAIR_15e52a00.jpg
new file mode 100644
index 0000000..e36d6b4
Binary files /dev/null and b/images/2.3.1.1+FAST+PAIR_15e52a00.jpg differ
diff --git a/images/2.3.1.1+FAST+PAIR_164c75b5.jpg b/images/2.3.1.1+FAST+PAIR_164c75b5.jpg
new file mode 100644
index 0000000..1e57336
Binary files /dev/null and b/images/2.3.1.1+FAST+PAIR_164c75b5.jpg differ
diff --git a/images/2.3.1.1+FAST+PAIR_3d03868f.jpg b/images/2.3.1.1+FAST+PAIR_3d03868f.jpg
new file mode 100644
index 0000000..fddba4f
Binary files /dev/null and b/images/2.3.1.1+FAST+PAIR_3d03868f.jpg differ
diff --git a/images/2.3.1.1+FAST+PAIR_428dc17d.jpg b/images/2.3.1.1+FAST+PAIR_428dc17d.jpg
new file mode 100644
index 0000000..fc9d19d
Binary files /dev/null and b/images/2.3.1.1+FAST+PAIR_428dc17d.jpg differ
diff --git a/images/2.3.1.1+FAST+PAIR_442c88ac.jpg b/images/2.3.1.1+FAST+PAIR_442c88ac.jpg
new file mode 100644
index 0000000..282c6fc
Binary files /dev/null and b/images/2.3.1.1+FAST+PAIR_442c88ac.jpg differ
diff --git a/images/2.3.1.1+FAST+PAIR_48b9e933.jpg b/images/2.3.1.1+FAST+PAIR_48b9e933.jpg
new file mode 100644
index 0000000..8433e22
Binary files /dev/null and b/images/2.3.1.1+FAST+PAIR_48b9e933.jpg differ
diff --git a/images/2.3.1.1+FAST+PAIR_54319dbf.jpg b/images/2.3.1.1+FAST+PAIR_54319dbf.jpg
new file mode 100644
index 0000000..fc9d19d
Binary files /dev/null and b/images/2.3.1.1+FAST+PAIR_54319dbf.jpg differ
diff --git a/images/2.3.1.1+FAST+PAIR_5fead0d5.jpg b/images/2.3.1.1+FAST+PAIR_5fead0d5.jpg
new file mode 100644
index 0000000..fddba4f
Binary files /dev/null and b/images/2.3.1.1+FAST+PAIR_5fead0d5.jpg differ
diff --git a/images/2.3.1.1+FAST+PAIR_60a17240.jpg b/images/2.3.1.1+FAST+PAIR_60a17240.jpg
new file mode 100644
index 0000000..416587f
Binary files /dev/null and b/images/2.3.1.1+FAST+PAIR_60a17240.jpg differ
diff --git a/images/2.3.1.1+FAST+PAIR_644ce66c.jpg b/images/2.3.1.1+FAST+PAIR_644ce66c.jpg
new file mode 100644
index 0000000..b8710bd
Binary files /dev/null and b/images/2.3.1.1+FAST+PAIR_644ce66c.jpg differ
diff --git a/images/2.3.1.1+FAST+PAIR_66e9f145.jpg b/images/2.3.1.1+FAST+PAIR_66e9f145.jpg
new file mode 100644
index 0000000..1347313
Binary files /dev/null and b/images/2.3.1.1+FAST+PAIR_66e9f145.jpg differ
diff --git a/images/2.3.1.1+FAST+PAIR_693c89bb.jpg b/images/2.3.1.1+FAST+PAIR_693c89bb.jpg
new file mode 100644
index 0000000..3782f36
Binary files /dev/null and b/images/2.3.1.1+FAST+PAIR_693c89bb.jpg differ
diff --git a/images/2.3.1.1+FAST+PAIR_6dbfbf63.jpg b/images/2.3.1.1+FAST+PAIR_6dbfbf63.jpg
new file mode 100644
index 0000000..4f4b48b
Binary files /dev/null and b/images/2.3.1.1+FAST+PAIR_6dbfbf63.jpg differ
diff --git a/images/2.3.1.1+FAST+PAIR_6ec32327.jpg b/images/2.3.1.1+FAST+PAIR_6ec32327.jpg
new file mode 100644
index 0000000..416587f
Binary files /dev/null and b/images/2.3.1.1+FAST+PAIR_6ec32327.jpg differ
diff --git a/images/2.3.1.1+FAST+PAIR_6f79b1bd.jpg b/images/2.3.1.1+FAST+PAIR_6f79b1bd.jpg
new file mode 100644
index 0000000..e36d6b4
Binary files /dev/null and b/images/2.3.1.1+FAST+PAIR_6f79b1bd.jpg differ
diff --git a/images/2.3.1.1+FAST+PAIR_7396eb54.jpg b/images/2.3.1.1+FAST+PAIR_7396eb54.jpg
new file mode 100644
index 0000000..db2bedf
Binary files /dev/null and b/images/2.3.1.1+FAST+PAIR_7396eb54.jpg differ
diff --git a/images/2.3.1.1+FAST+PAIR_74d5d0fb.jpg b/images/2.3.1.1+FAST+PAIR_74d5d0fb.jpg
new file mode 100644
index 0000000..fa50efb
Binary files /dev/null and b/images/2.3.1.1+FAST+PAIR_74d5d0fb.jpg differ
diff --git a/images/2.3.1.1+FAST+PAIR_75fddf9b.jpg b/images/2.3.1.1+FAST+PAIR_75fddf9b.jpg
new file mode 100644
index 0000000..d6bfd8c
Binary files /dev/null and b/images/2.3.1.1+FAST+PAIR_75fddf9b.jpg differ
diff --git a/images/2.3.1.1+FAST+PAIR_7643c725.jpg b/images/2.3.1.1+FAST+PAIR_7643c725.jpg
new file mode 100644
index 0000000..1e57336
Binary files /dev/null and b/images/2.3.1.1+FAST+PAIR_7643c725.jpg differ
diff --git a/images/2.3.1.1+FAST+PAIR_76c00dd0.jpg b/images/2.3.1.1+FAST+PAIR_76c00dd0.jpg
new file mode 100644
index 0000000..852aa5a
Binary files /dev/null and b/images/2.3.1.1+FAST+PAIR_76c00dd0.jpg differ
diff --git a/images/2.3.1.1+FAST+PAIR_79299845.jpg b/images/2.3.1.1+FAST+PAIR_79299845.jpg
new file mode 100644
index 0000000..9e0995e
Binary files /dev/null and b/images/2.3.1.1+FAST+PAIR_79299845.jpg differ
diff --git a/images/2.3.1.1+FAST+PAIR_7aa4e985.jpg b/images/2.3.1.1+FAST+PAIR_7aa4e985.jpg
new file mode 100644
index 0000000..852aa5a
Binary files /dev/null and b/images/2.3.1.1+FAST+PAIR_7aa4e985.jpg differ
diff --git a/images/2.3.1.1+FAST+PAIR_7cba31ac.jpg b/images/2.3.1.1+FAST+PAIR_7cba31ac.jpg
new file mode 100644
index 0000000..4a1a3d5
Binary files /dev/null and b/images/2.3.1.1+FAST+PAIR_7cba31ac.jpg differ
diff --git a/images/2.3.1.1+FAST+PAIR_7e31cfb6.jpg b/images/2.3.1.1+FAST+PAIR_7e31cfb6.jpg
new file mode 100644
index 0000000..516f98a
Binary files /dev/null and b/images/2.3.1.1+FAST+PAIR_7e31cfb6.jpg differ
diff --git a/images/2.3.1.1+FAST+PAIR_83f60f69.jpg b/images/2.3.1.1+FAST+PAIR_83f60f69.jpg
new file mode 100644
index 0000000..8433e22
Binary files /dev/null and b/images/2.3.1.1+FAST+PAIR_83f60f69.jpg differ
diff --git a/images/2.3.1.1+FAST+PAIR_8a9dde0f.jpg b/images/2.3.1.1+FAST+PAIR_8a9dde0f.jpg
new file mode 100644
index 0000000..4a04f11
Binary files /dev/null and b/images/2.3.1.1+FAST+PAIR_8a9dde0f.jpg differ
diff --git a/images/2.3.1.1+FAST+PAIR_8e3e2cd5.jpg b/images/2.3.1.1+FAST+PAIR_8e3e2cd5.jpg
new file mode 100644
index 0000000..4a1a3d5
Binary files /dev/null and b/images/2.3.1.1+FAST+PAIR_8e3e2cd5.jpg differ
diff --git a/images/2.3.1.1+FAST+PAIR_8ede8679.jpg b/images/2.3.1.1+FAST+PAIR_8ede8679.jpg
new file mode 100644
index 0000000..ce54135
Binary files /dev/null and b/images/2.3.1.1+FAST+PAIR_8ede8679.jpg differ
diff --git a/images/2.3.1.1+FAST+PAIR_90f706c7.jpg b/images/2.3.1.1+FAST+PAIR_90f706c7.jpg
new file mode 100644
index 0000000..86a991f
Binary files /dev/null and b/images/2.3.1.1+FAST+PAIR_90f706c7.jpg differ
diff --git a/images/2.3.1.1+FAST+PAIR_91442583.jpg b/images/2.3.1.1+FAST+PAIR_91442583.jpg
new file mode 100644
index 0000000..4b7fdeb
Binary files /dev/null and b/images/2.3.1.1+FAST+PAIR_91442583.jpg differ
diff --git a/images/2.3.1.1+FAST+PAIR_91876d62.jpg b/images/2.3.1.1+FAST+PAIR_91876d62.jpg
new file mode 100644
index 0000000..db2bedf
Binary files /dev/null and b/images/2.3.1.1+FAST+PAIR_91876d62.jpg differ
diff --git a/images/2.3.1.1+FAST+PAIR_940c116c.jpg b/images/2.3.1.1+FAST+PAIR_940c116c.jpg
new file mode 100644
index 0000000..282c6fc
Binary files /dev/null and b/images/2.3.1.1+FAST+PAIR_940c116c.jpg differ
diff --git a/images/2.3.1.1+FAST+PAIR_9ad8001b.jpg b/images/2.3.1.1+FAST+PAIR_9ad8001b.jpg
new file mode 100644
index 0000000..0b6dfcf
Binary files /dev/null and b/images/2.3.1.1+FAST+PAIR_9ad8001b.jpg differ
diff --git a/images/2.3.1.1+FAST+PAIR_9b1f8b1c.jpg b/images/2.3.1.1+FAST+PAIR_9b1f8b1c.jpg
new file mode 100644
index 0000000..b8710bd
Binary files /dev/null and b/images/2.3.1.1+FAST+PAIR_9b1f8b1c.jpg differ
diff --git a/images/2.3.1.1+FAST+PAIR_9b6684ad.jpg b/images/2.3.1.1+FAST+PAIR_9b6684ad.jpg
new file mode 100644
index 0000000..529fbe5
Binary files /dev/null and b/images/2.3.1.1+FAST+PAIR_9b6684ad.jpg differ
diff --git a/images/2.3.1.1+FAST+PAIR_9fcfcd1d.jpg b/images/2.3.1.1+FAST+PAIR_9fcfcd1d.jpg
new file mode 100644
index 0000000..6a77749
Binary files /dev/null and b/images/2.3.1.1+FAST+PAIR_9fcfcd1d.jpg differ
diff --git a/images/2.3.1.1+FAST+PAIR_a70eeadc.jpg b/images/2.3.1.1+FAST+PAIR_a70eeadc.jpg
new file mode 100644
index 0000000..45ab59e
Binary files /dev/null and b/images/2.3.1.1+FAST+PAIR_a70eeadc.jpg differ
diff --git a/images/2.3.1.1+FAST+PAIR_a826423d.jpg b/images/2.3.1.1+FAST+PAIR_a826423d.jpg
new file mode 100644
index 0000000..85af556
Binary files /dev/null and b/images/2.3.1.1+FAST+PAIR_a826423d.jpg differ
diff --git a/images/2.3.1.1+FAST+PAIR_ab3286f1.jpg b/images/2.3.1.1+FAST+PAIR_ab3286f1.jpg
new file mode 100644
index 0000000..d207df6
Binary files /dev/null and b/images/2.3.1.1+FAST+PAIR_ab3286f1.jpg differ
diff --git a/images/2.3.1.1+FAST+PAIR_ab6891f1.jpg b/images/2.3.1.1+FAST+PAIR_ab6891f1.jpg
new file mode 100644
index 0000000..9ff0e76
Binary files /dev/null and b/images/2.3.1.1+FAST+PAIR_ab6891f1.jpg differ
diff --git a/images/2.3.1.1+FAST+PAIR_ad22c15b.jpg b/images/2.3.1.1+FAST+PAIR_ad22c15b.jpg
new file mode 100644
index 0000000..4f4b48b
Binary files /dev/null and b/images/2.3.1.1+FAST+PAIR_ad22c15b.jpg differ
diff --git a/images/2.3.1.1+FAST+PAIR_ae941214.jpg b/images/2.3.1.1+FAST+PAIR_ae941214.jpg
new file mode 100644
index 0000000..6265c1b
Binary files /dev/null and b/images/2.3.1.1+FAST+PAIR_ae941214.jpg differ
diff --git a/images/2.3.1.1+FAST+PAIR_b2de93b7.jpg b/images/2.3.1.1+FAST+PAIR_b2de93b7.jpg
new file mode 100644
index 0000000..0b6dfcf
Binary files /dev/null and b/images/2.3.1.1+FAST+PAIR_b2de93b7.jpg differ
diff --git a/images/2.3.1.1+FAST+PAIR_b2e699c8.jpg b/images/2.3.1.1+FAST+PAIR_b2e699c8.jpg
new file mode 100644
index 0000000..c2b0529
Binary files /dev/null and b/images/2.3.1.1+FAST+PAIR_b2e699c8.jpg differ
diff --git a/images/2.3.1.1+FAST+PAIR_b4129b38.jpg b/images/2.3.1.1+FAST+PAIR_b4129b38.jpg
new file mode 100644
index 0000000..c2b0529
Binary files /dev/null and b/images/2.3.1.1+FAST+PAIR_b4129b38.jpg differ
diff --git a/images/2.3.1.1+FAST+PAIR_b47e906b.jpg b/images/2.3.1.1+FAST+PAIR_b47e906b.jpg
new file mode 100644
index 0000000..4b7fdeb
Binary files /dev/null and b/images/2.3.1.1+FAST+PAIR_b47e906b.jpg differ
diff --git a/images/2.3.1.1+FAST+PAIR_b665881b.jpg b/images/2.3.1.1+FAST+PAIR_b665881b.jpg
new file mode 100644
index 0000000..4a04f11
Binary files /dev/null and b/images/2.3.1.1+FAST+PAIR_b665881b.jpg differ
diff --git a/images/2.3.1.1+FAST+PAIR_ba408fdf.jpg b/images/2.3.1.1+FAST+PAIR_ba408fdf.jpg
new file mode 100644
index 0000000..c57fcea
Binary files /dev/null and b/images/2.3.1.1+FAST+PAIR_ba408fdf.jpg differ
diff --git a/images/2.3.1.1+FAST+PAIR_bf86c779.jpg b/images/2.3.1.1+FAST+PAIR_bf86c779.jpg
new file mode 100644
index 0000000..32891b9
Binary files /dev/null and b/images/2.3.1.1+FAST+PAIR_bf86c779.jpg differ
diff --git a/images/2.3.1.1+FAST+PAIR_c6f4a29e.jpg b/images/2.3.1.1+FAST+PAIR_c6f4a29e.jpg
new file mode 100644
index 0000000..4b129ea
Binary files /dev/null and b/images/2.3.1.1+FAST+PAIR_c6f4a29e.jpg differ
diff --git a/images/2.3.1.1+FAST+PAIR_c723926f.jpg b/images/2.3.1.1+FAST+PAIR_c723926f.jpg
new file mode 100644
index 0000000..85af556
Binary files /dev/null and b/images/2.3.1.1+FAST+PAIR_c723926f.jpg differ
diff --git a/images/2.3.1.1+FAST+PAIR_c7e1a98c.jpg b/images/2.3.1.1+FAST+PAIR_c7e1a98c.jpg
new file mode 100644
index 0000000..32891b9
Binary files /dev/null and b/images/2.3.1.1+FAST+PAIR_c7e1a98c.jpg differ
diff --git a/images/2.3.1.1+FAST+PAIR_c8242ed8.jpg b/images/2.3.1.1+FAST+PAIR_c8242ed8.jpg
new file mode 100644
index 0000000..529fbe5
Binary files /dev/null and b/images/2.3.1.1+FAST+PAIR_c8242ed8.jpg differ
diff --git a/images/2.3.1.1+FAST+PAIR_cbf1a3bb.jpg b/images/2.3.1.1+FAST+PAIR_cbf1a3bb.jpg
new file mode 100644
index 0000000..3782f36
Binary files /dev/null and b/images/2.3.1.1+FAST+PAIR_cbf1a3bb.jpg differ
diff --git a/images/2.3.1.1+FAST+PAIR_cdca1082.jpg b/images/2.3.1.1+FAST+PAIR_cdca1082.jpg
new file mode 100644
index 0000000..b1a6228
Binary files /dev/null and b/images/2.3.1.1+FAST+PAIR_cdca1082.jpg differ
diff --git a/images/2.3.1.1+FAST+PAIR_d19de1a7.jpg b/images/2.3.1.1+FAST+PAIR_d19de1a7.jpg
new file mode 100644
index 0000000..9ff0e76
Binary files /dev/null and b/images/2.3.1.1+FAST+PAIR_d19de1a7.jpg differ
diff --git a/images/2.3.1.1+FAST+PAIR_dc2894ee.jpg b/images/2.3.1.1+FAST+PAIR_dc2894ee.jpg
new file mode 100644
index 0000000..1347313
Binary files /dev/null and b/images/2.3.1.1+FAST+PAIR_dc2894ee.jpg differ
diff --git a/images/2.3.1.1+FAST+PAIR_e194e530.jpg b/images/2.3.1.1+FAST+PAIR_e194e530.jpg
new file mode 100644
index 0000000..4b129ea
Binary files /dev/null and b/images/2.3.1.1+FAST+PAIR_e194e530.jpg differ
diff --git a/images/2.3.1.1+FAST+PAIR_ef0e9a4f.jpg b/images/2.3.1.1+FAST+PAIR_ef0e9a4f.jpg
new file mode 100644
index 0000000..d6bfd8c
Binary files /dev/null and b/images/2.3.1.1+FAST+PAIR_ef0e9a4f.jpg differ
diff --git a/images/2.3.1.1+FAST+PAIR_f19c4275.jpg b/images/2.3.1.1+FAST+PAIR_f19c4275.jpg
new file mode 100644
index 0000000..45ab59e
Binary files /dev/null and b/images/2.3.1.1+FAST+PAIR_f19c4275.jpg differ
diff --git a/images/2.3.1.1+FAST+PAIR_f69dae33.jpg b/images/2.3.1.1+FAST+PAIR_f69dae33.jpg
new file mode 100644
index 0000000..c57fcea
Binary files /dev/null and b/images/2.3.1.1+FAST+PAIR_f69dae33.jpg differ
diff --git a/images/2.3.1.1+FAST+PAIR_f96463d0.jpg b/images/2.3.1.1+FAST+PAIR_f96463d0.jpg
new file mode 100644
index 0000000..b1a6228
Binary files /dev/null and b/images/2.3.1.1+FAST+PAIR_f96463d0.jpg differ
diff --git a/images/2.3.1.1+FAST+PAIR_fa130fa9.jpg b/images/2.3.1.1+FAST+PAIR_fa130fa9.jpg
new file mode 100644
index 0000000..86a991f
Binary files /dev/null and b/images/2.3.1.1+FAST+PAIR_fa130fa9.jpg differ
diff --git a/images/2.3.1.1+FAST+PAIR_ff40ed50.jpg b/images/2.3.1.1+FAST+PAIR_ff40ed50.jpg
new file mode 100644
index 0000000..516f98a
Binary files /dev/null and b/images/2.3.1.1+FAST+PAIR_ff40ed50.jpg differ
diff --git a/images/2.3.2+EDDYSTONE_3c69f751.jpg b/images/2.3.2+EDDYSTONE_3c69f751.jpg
new file mode 100644
index 0000000..46e07a5
Binary files /dev/null and b/images/2.3.2+EDDYSTONE_3c69f751.jpg differ
diff --git a/images/2.3.2+EDDYSTONE_4da56b0a.jpg b/images/2.3.2+EDDYSTONE_4da56b0a.jpg
new file mode 100644
index 0000000..46e07a5
Binary files /dev/null and b/images/2.3.2+EDDYSTONE_4da56b0a.jpg differ
diff --git a/images/2.3.2.3+find+hub_400dcc97.jpg b/images/2.3.2.3+find+hub_400dcc97.jpg
new file mode 100644
index 0000000..2405131
Binary files /dev/null and b/images/2.3.2.3+find+hub_400dcc97.jpg differ
diff --git a/images/2.3.2.3+find+hub_c22ea6b7.jpg b/images/2.3.2.3+find+hub_c22ea6b7.jpg
new file mode 100644
index 0000000..2405131
Binary files /dev/null and b/images/2.3.2.3+find+hub_c22ea6b7.jpg differ
diff --git a/images/23+很多客户要求不在Pairing+mode不允许配对新的设备，和GFPS+subsequent+Pair+有冲突，修改策略如下_428c8b20.jpg b/images/23+很多客户要求不在Pairing+mode不允许配对新的设备，和GFPS+subsequent+Pair+有冲突，修改策略如下_428c8b20.jpg
new file mode 100644
index 0000000..7631078
Binary files /dev/null and b/images/23+很多客户要求不在Pairing+mode不允许配对新的设备，和GFPS+subsequent+Pair+有冲突，修改策略如下_428c8b20.jpg differ
diff --git a/images/23+很多客户要求不在Pairing+mode不允许配对新的设备，和GFPS+subsequent+Pair+有冲突，修改策略如下_4445606f.jpg b/images/23+很多客户要求不在Pairing+mode不允许配对新的设备，和GFPS+subsequent+Pair+有冲突，修改策略如下_4445606f.jpg
new file mode 100644
index 0000000..0130303
Binary files /dev/null and b/images/23+很多客户要求不在Pairing+mode不允许配对新的设备，和GFPS+subsequent+Pair+有冲突，修改策略如下_4445606f.jpg differ
diff --git a/images/23+很多客户要求不在Pairing+mode不允许配对新的设备，和GFPS+subsequent+Pair+有冲突，修改策略如下_63cc438b.jpg b/images/23+很多客户要求不在Pairing+mode不允许配对新的设备，和GFPS+subsequent+Pair+有冲突，修改策略如下_63cc438b.jpg
new file mode 100644
index 0000000..9e59247
Binary files /dev/null and b/images/23+很多客户要求不在Pairing+mode不允许配对新的设备，和GFPS+subsequent+Pair+有冲突，修改策略如下_63cc438b.jpg differ
diff --git a/images/23+很多客户要求不在Pairing+mode不允许配对新的设备，和GFPS+subsequent+Pair+有冲突，修改策略如下_89ccdf0f.jpg b/images/23+很多客户要求不在Pairing+mode不允许配对新的设备，和GFPS+subsequent+Pair+有冲突，修改策略如下_89ccdf0f.jpg
new file mode 100644
index 0000000..7631078
Binary files /dev/null and b/images/23+很多客户要求不在Pairing+mode不允许配对新的设备，和GFPS+subsequent+Pair+有冲突，修改策略如下_89ccdf0f.jpg differ
diff --git a/images/23+很多客户要求不在Pairing+mode不允许配对新的设备，和GFPS+subsequent+Pair+有冲突，修改策略如下_bbd1aa6e.jpg b/images/23+很多客户要求不在Pairing+mode不允许配对新的设备，和GFPS+subsequent+Pair+有冲突，修改策略如下_bbd1aa6e.jpg
new file mode 100644
index 0000000..0130303
Binary files /dev/null and b/images/23+很多客户要求不在Pairing+mode不允许配对新的设备，和GFPS+subsequent+Pair+有冲突，修改策略如下_bbd1aa6e.jpg differ
diff --git a/images/23+很多客户要求不在Pairing+mode不允许配对新的设备，和GFPS+subsequent+Pair+有冲突，修改策略如下_c93bdfcc.jpg b/images/23+很多客户要求不在Pairing+mode不允许配对新的设备，和GFPS+subsequent+Pair+有冲突，修改策略如下_c93bdfcc.jpg
new file mode 100644
index 0000000..9e59247
Binary files /dev/null and b/images/23+很多客户要求不在Pairing+mode不允许配对新的设备，和GFPS+subsequent+Pair+有冲突，修改策略如下_c93bdfcc.jpg differ
diff --git a/images/3+UI+提示+Not+receive+KeyBasedPairingResponse_5f112017.jpg b/images/3+UI+提示+Not+receive+KeyBasedPairingResponse_5f112017.jpg
new file mode 100644
index 0000000..09fb4af
Binary files /dev/null and b/images/3+UI+提示+Not+receive+KeyBasedPairingResponse_5f112017.jpg differ
diff --git a/images/3+UI+提示+Not+receive+KeyBasedPairingResponse_e4fbcec4.jpg b/images/3+UI+提示+Not+receive+KeyBasedPairingResponse_e4fbcec4.jpg
new file mode 100644
index 0000000..09fb4af
Binary files /dev/null and b/images/3+UI+提示+Not+receive+KeyBasedPairingResponse_e4fbcec4.jpg differ
diff --git a/images/3.+initial+pair+走的LE+配对，+subsequent+pair+走的legacy+配对_dafdc01a.jpg b/images/3.+initial+pair+走的LE+配对，+subsequent+pair+走的legacy+配对_dafdc01a.jpg
new file mode 100644
index 0000000..fbe7592
Binary files /dev/null and b/images/3.+initial+pair+走的LE+配对，+subsequent+pair+走的legacy+配对_dafdc01a.jpg differ
diff --git a/images/3.+initial+pair+走的LE+配对，+subsequent+pair+走的legacy+配对_e0cce3a3.jpg b/images/3.+initial+pair+走的LE+配对，+subsequent+pair+走的legacy+配对_e0cce3a3.jpg
new file mode 100644
index 0000000..fbe7592
Binary files /dev/null and b/images/3.+initial+pair+走的LE+配对，+subsequent+pair+走的legacy+配对_e0cce3a3.jpg differ
diff --git a/images/3.2.1+设备端环境搭建_03797d18.jpg b/images/3.2.1+设备端环境搭建_03797d18.jpg
new file mode 100644
index 0000000..e5ad8ea
Binary files /dev/null and b/images/3.2.1+设备端环境搭建_03797d18.jpg differ
diff --git a/images/3.2.1+设备端环境搭建_097c463b.jpg b/images/3.2.1+设备端环境搭建_097c463b.jpg
new file mode 100644
index 0000000..54a3952
Binary files /dev/null and b/images/3.2.1+设备端环境搭建_097c463b.jpg differ
diff --git a/images/3.2.1+设备端环境搭建_09d79211.jpg b/images/3.2.1+设备端环境搭建_09d79211.jpg
new file mode 100644
index 0000000..db704d5
Binary files /dev/null and b/images/3.2.1+设备端环境搭建_09d79211.jpg differ
diff --git a/images/3.2.1+设备端环境搭建_0e82a2e9.jpg b/images/3.2.1+设备端环境搭建_0e82a2e9.jpg
new file mode 100644
index 0000000..c7c022b
Binary files /dev/null and b/images/3.2.1+设备端环境搭建_0e82a2e9.jpg differ
diff --git a/images/3.2.1+设备端环境搭建_10f254f6.jpg b/images/3.2.1+设备端环境搭建_10f254f6.jpg
new file mode 100644
index 0000000..d1c576d
Binary files /dev/null and b/images/3.2.1+设备端环境搭建_10f254f6.jpg differ
diff --git a/images/3.2.1+设备端环境搭建_1db0c21f.jpg b/images/3.2.1+设备端环境搭建_1db0c21f.jpg
new file mode 100644
index 0000000..56c2ce9
Binary files /dev/null and b/images/3.2.1+设备端环境搭建_1db0c21f.jpg differ
diff --git a/images/3.2.1+设备端环境搭建_252caec7.jpg b/images/3.2.1+设备端环境搭建_252caec7.jpg
new file mode 100644
index 0000000..f6db634
Binary files /dev/null and b/images/3.2.1+设备端环境搭建_252caec7.jpg differ
diff --git a/images/3.2.1+设备端环境搭建_29219f10.jpg b/images/3.2.1+设备端环境搭建_29219f10.jpg
new file mode 100644
index 0000000..9af42b6
Binary files /dev/null and b/images/3.2.1+设备端环境搭建_29219f10.jpg differ
diff --git a/images/3.2.1+设备端环境搭建_29d62785.jpg b/images/3.2.1+设备端环境搭建_29d62785.jpg
new file mode 100644
index 0000000..1433f73
Binary files /dev/null and b/images/3.2.1+设备端环境搭建_29d62785.jpg differ
diff --git a/images/3.2.1+设备端环境搭建_2b97f984.jpg b/images/3.2.1+设备端环境搭建_2b97f984.jpg
new file mode 100644
index 0000000..72ad6b6
Binary files /dev/null and b/images/3.2.1+设备端环境搭建_2b97f984.jpg differ
diff --git a/images/3.2.1+设备端环境搭建_2c1853f2.jpg b/images/3.2.1+设备端环境搭建_2c1853f2.jpg
new file mode 100644
index 0000000..9175d8d
Binary files /dev/null and b/images/3.2.1+设备端环境搭建_2c1853f2.jpg differ
diff --git a/images/3.2.1+设备端环境搭建_2ec82dcc.jpg b/images/3.2.1+设备端环境搭建_2ec82dcc.jpg
new file mode 100644
index 0000000..d2665a4
Binary files /dev/null and b/images/3.2.1+设备端环境搭建_2ec82dcc.jpg differ
diff --git a/images/3.2.1+设备端环境搭建_343f05ce.jpg b/images/3.2.1+设备端环境搭建_343f05ce.jpg
new file mode 100644
index 0000000..78e4e1a
Binary files /dev/null and b/images/3.2.1+设备端环境搭建_343f05ce.jpg differ
diff --git a/images/3.2.1+设备端环境搭建_425abb0d.jpg b/images/3.2.1+设备端环境搭建_425abb0d.jpg
new file mode 100644
index 0000000..93b4195
Binary files /dev/null and b/images/3.2.1+设备端环境搭建_425abb0d.jpg differ
diff --git a/images/3.2.1+设备端环境搭建_4549444f.jpg b/images/3.2.1+设备端环境搭建_4549444f.jpg
new file mode 100644
index 0000000..54a3952
Binary files /dev/null and b/images/3.2.1+设备端环境搭建_4549444f.jpg differ
diff --git a/images/3.2.1+设备端环境搭建_4da279b3.jpg b/images/3.2.1+设备端环境搭建_4da279b3.jpg
new file mode 100644
index 0000000..29508c7
Binary files /dev/null and b/images/3.2.1+设备端环境搭建_4da279b3.jpg differ
diff --git a/images/3.2.1+设备端环境搭建_4f347189.jpg b/images/3.2.1+设备端环境搭建_4f347189.jpg
new file mode 100644
index 0000000..1144201
Binary files /dev/null and b/images/3.2.1+设备端环境搭建_4f347189.jpg differ
diff --git a/images/3.2.1+设备端环境搭建_52db206c.jpg b/images/3.2.1+设备端环境搭建_52db206c.jpg
new file mode 100644
index 0000000..cb0b64a
Binary files /dev/null and b/images/3.2.1+设备端环境搭建_52db206c.jpg differ
diff --git a/images/3.2.1+设备端环境搭建_58b54748.jpg b/images/3.2.1+设备端环境搭建_58b54748.jpg
new file mode 100644
index 0000000..6b903d7
Binary files /dev/null and b/images/3.2.1+设备端环境搭建_58b54748.jpg differ
diff --git a/images/3.2.1+设备端环境搭建_59add6df.jpg b/images/3.2.1+设备端环境搭建_59add6df.jpg
new file mode 100644
index 0000000..c5f9cf0
Binary files /dev/null and b/images/3.2.1+设备端环境搭建_59add6df.jpg differ
diff --git a/images/3.2.1+设备端环境搭建_5c85ab22.jpg b/images/3.2.1+设备端环境搭建_5c85ab22.jpg
new file mode 100644
index 0000000..3c523d9
Binary files /dev/null and b/images/3.2.1+设备端环境搭建_5c85ab22.jpg differ
diff --git a/images/3.2.1+设备端环境搭建_5cd32631.jpg b/images/3.2.1+设备端环境搭建_5cd32631.jpg
new file mode 100644
index 0000000..67278f1
Binary files /dev/null and b/images/3.2.1+设备端环境搭建_5cd32631.jpg differ
diff --git a/images/3.2.1+设备端环境搭建_5cdb6740.jpg b/images/3.2.1+设备端环境搭建_5cdb6740.jpg
new file mode 100644
index 0000000..6b903d7
Binary files /dev/null and b/images/3.2.1+设备端环境搭建_5cdb6740.jpg differ
diff --git a/images/3.2.1+设备端环境搭建_5f0bb9e1.jpg b/images/3.2.1+设备端环境搭建_5f0bb9e1.jpg
new file mode 100644
index 0000000..a046754
Binary files /dev/null and b/images/3.2.1+设备端环境搭建_5f0bb9e1.jpg differ
diff --git a/images/3.2.1+设备端环境搭建_6112c00b.jpg b/images/3.2.1+设备端环境搭建_6112c00b.jpg
new file mode 100644
index 0000000..56c2ce9
Binary files /dev/null and b/images/3.2.1+设备端环境搭建_6112c00b.jpg differ
diff --git a/images/3.2.1+设备端环境搭建_64aea5ae.jpg b/images/3.2.1+设备端环境搭建_64aea5ae.jpg
new file mode 100644
index 0000000..e405626
Binary files /dev/null and b/images/3.2.1+设备端环境搭建_64aea5ae.jpg differ
diff --git a/images/3.2.1+设备端环境搭建_68e8b8d6.jpg b/images/3.2.1+设备端环境搭建_68e8b8d6.jpg
new file mode 100644
index 0000000..a046754
Binary files /dev/null and b/images/3.2.1+设备端环境搭建_68e8b8d6.jpg differ
diff --git a/images/3.2.1+设备端环境搭建_70fc70bb.jpg b/images/3.2.1+设备端环境搭建_70fc70bb.jpg
new file mode 100644
index 0000000..c7c022b
Binary files /dev/null and b/images/3.2.1+设备端环境搭建_70fc70bb.jpg differ
diff --git a/images/3.2.1+设备端环境搭建_73810d7b.jpg b/images/3.2.1+设备端环境搭建_73810d7b.jpg
new file mode 100644
index 0000000..f6d95c1
Binary files /dev/null and b/images/3.2.1+设备端环境搭建_73810d7b.jpg differ
diff --git a/images/3.2.1+设备端环境搭建_742c3d62.jpg b/images/3.2.1+设备端环境搭建_742c3d62.jpg
new file mode 100644
index 0000000..fb2c74b
Binary files /dev/null and b/images/3.2.1+设备端环境搭建_742c3d62.jpg differ
diff --git a/images/3.2.1+设备端环境搭建_7b61706a.jpg b/images/3.2.1+设备端环境搭建_7b61706a.jpg
new file mode 100644
index 0000000..9af42b6
Binary files /dev/null and b/images/3.2.1+设备端环境搭建_7b61706a.jpg differ
diff --git a/images/3.2.1+设备端环境搭建_7d634684.jpg b/images/3.2.1+设备端环境搭建_7d634684.jpg
new file mode 100644
index 0000000..2eae932
Binary files /dev/null and b/images/3.2.1+设备端环境搭建_7d634684.jpg differ
diff --git a/images/3.2.1+设备端环境搭建_7e886712.jpg b/images/3.2.1+设备端环境搭建_7e886712.jpg
new file mode 100644
index 0000000..09188bf
Binary files /dev/null and b/images/3.2.1+设备端环境搭建_7e886712.jpg differ
diff --git a/images/3.2.1+设备端环境搭建_81ad6b9a.jpg b/images/3.2.1+设备端环境搭建_81ad6b9a.jpg
new file mode 100644
index 0000000..f6db634
Binary files /dev/null and b/images/3.2.1+设备端环境搭建_81ad6b9a.jpg differ
diff --git a/images/3.2.1+设备端环境搭建_823fbf23.jpg b/images/3.2.1+设备端环境搭建_823fbf23.jpg
new file mode 100644
index 0000000..c5f9cf0
Binary files /dev/null and b/images/3.2.1+设备端环境搭建_823fbf23.jpg differ
diff --git a/images/3.2.1+设备端环境搭建_8cfd479d.jpg b/images/3.2.1+设备端环境搭建_8cfd479d.jpg
new file mode 100644
index 0000000..d1c576d
Binary files /dev/null and b/images/3.2.1+设备端环境搭建_8cfd479d.jpg differ
diff --git a/images/3.2.1+设备端环境搭建_8f09ba3c.jpg b/images/3.2.1+设备端环境搭建_8f09ba3c.jpg
new file mode 100644
index 0000000..013773f
Binary files /dev/null and b/images/3.2.1+设备端环境搭建_8f09ba3c.jpg differ
diff --git a/images/3.2.1+设备端环境搭建_90a61fa1.jpg b/images/3.2.1+设备端环境搭建_90a61fa1.jpg
new file mode 100644
index 0000000..1144201
Binary files /dev/null and b/images/3.2.1+设备端环境搭建_90a61fa1.jpg differ
diff --git a/images/3.2.1+设备端环境搭建_923a4b2f.jpg b/images/3.2.1+设备端环境搭建_923a4b2f.jpg
new file mode 100644
index 0000000..1699bb3
Binary files /dev/null and b/images/3.2.1+设备端环境搭建_923a4b2f.jpg differ
diff --git a/images/3.2.1+设备端环境搭建_9a21018d.jpg b/images/3.2.1+设备端环境搭建_9a21018d.jpg
new file mode 100644
index 0000000..7947da6
Binary files /dev/null and b/images/3.2.1+设备端环境搭建_9a21018d.jpg differ
diff --git a/images/3.2.1+设备端环境搭建_9ad77753.jpg b/images/3.2.1+设备端环境搭建_9ad77753.jpg
new file mode 100644
index 0000000..1433f73
Binary files /dev/null and b/images/3.2.1+设备端环境搭建_9ad77753.jpg differ
diff --git a/images/3.2.1+设备端环境搭建_9bed7f8b.jpg b/images/3.2.1+设备端环境搭建_9bed7f8b.jpg
new file mode 100644
index 0000000..09188bf
Binary files /dev/null and b/images/3.2.1+设备端环境搭建_9bed7f8b.jpg differ
diff --git a/images/3.2.1+设备端环境搭建_9cb3f9a2.jpg b/images/3.2.1+设备端环境搭建_9cb3f9a2.jpg
new file mode 100644
index 0000000..f2be290
Binary files /dev/null and b/images/3.2.1+设备端环境搭建_9cb3f9a2.jpg differ
diff --git a/images/3.2.1+设备端环境搭建_a10bd948.jpg b/images/3.2.1+设备端环境搭建_a10bd948.jpg
new file mode 100644
index 0000000..c6ad91f
Binary files /dev/null and b/images/3.2.1+设备端环境搭建_a10bd948.jpg differ
diff --git a/images/3.2.1+设备端环境搭建_a1569809.jpg b/images/3.2.1+设备端环境搭建_a1569809.jpg
new file mode 100644
index 0000000..013773f
Binary files /dev/null and b/images/3.2.1+设备端环境搭建_a1569809.jpg differ
diff --git a/images/3.2.1+设备端环境搭建_a4eb7403.jpg b/images/3.2.1+设备端环境搭建_a4eb7403.jpg
new file mode 100644
index 0000000..44aa483
Binary files /dev/null and b/images/3.2.1+设备端环境搭建_a4eb7403.jpg differ
diff --git a/images/3.2.1+设备端环境搭建_a6b05c16.jpg b/images/3.2.1+设备端环境搭建_a6b05c16.jpg
new file mode 100644
index 0000000..fb2c74b
Binary files /dev/null and b/images/3.2.1+设备端环境搭建_a6b05c16.jpg differ
diff --git a/images/3.2.1+设备端环境搭建_a9bc57a8.jpg b/images/3.2.1+设备端环境搭建_a9bc57a8.jpg
new file mode 100644
index 0000000..0d8f6c4
Binary files /dev/null and b/images/3.2.1+设备端环境搭建_a9bc57a8.jpg differ
diff --git a/images/3.2.1+设备端环境搭建_ac199d1b.jpg b/images/3.2.1+设备端环境搭建_ac199d1b.jpg
new file mode 100644
index 0000000..2eae932
Binary files /dev/null and b/images/3.2.1+设备端环境搭建_ac199d1b.jpg differ
diff --git a/images/3.2.1+设备端环境搭建_ac9e20e5.jpg b/images/3.2.1+设备端环境搭建_ac9e20e5.jpg
new file mode 100644
index 0000000..6259921
Binary files /dev/null and b/images/3.2.1+设备端环境搭建_ac9e20e5.jpg differ
diff --git a/images/3.2.1+设备端环境搭建_acdbdb52.jpg b/images/3.2.1+设备端环境搭建_acdbdb52.jpg
new file mode 100644
index 0000000..44aa483
Binary files /dev/null and b/images/3.2.1+设备端环境搭建_acdbdb52.jpg differ
diff --git a/images/3.2.1+设备端环境搭建_adcf7ea6.jpg b/images/3.2.1+设备端环境搭建_adcf7ea6.jpg
new file mode 100644
index 0000000..0a86490
Binary files /dev/null and b/images/3.2.1+设备端环境搭建_adcf7ea6.jpg differ
diff --git a/images/3.2.1+设备端环境搭建_af574b10.jpg b/images/3.2.1+设备端环境搭建_af574b10.jpg
new file mode 100644
index 0000000..0d8f6c4
Binary files /dev/null and b/images/3.2.1+设备端环境搭建_af574b10.jpg differ
diff --git a/images/3.2.1+设备端环境搭建_b3c9b188.jpg b/images/3.2.1+设备端环境搭建_b3c9b188.jpg
new file mode 100644
index 0000000..9175d8d
Binary files /dev/null and b/images/3.2.1+设备端环境搭建_b3c9b188.jpg differ
diff --git a/images/3.2.1+设备端环境搭建_b643e9a4.jpg b/images/3.2.1+设备端环境搭建_b643e9a4.jpg
new file mode 100644
index 0000000..72ad6b6
Binary files /dev/null and b/images/3.2.1+设备端环境搭建_b643e9a4.jpg differ
diff --git a/images/3.2.1+设备端环境搭建_b7531482.jpg b/images/3.2.1+设备端环境搭建_b7531482.jpg
new file mode 100644
index 0000000..0c2eee5
Binary files /dev/null and b/images/3.2.1+设备端环境搭建_b7531482.jpg differ
diff --git a/images/3.2.1+设备端环境搭建_bc8b6e71.jpg b/images/3.2.1+设备端环境搭建_bc8b6e71.jpg
new file mode 100644
index 0000000..93b4195
Binary files /dev/null and b/images/3.2.1+设备端环境搭建_bc8b6e71.jpg differ
diff --git a/images/3.2.1+设备端环境搭建_bffc8745.jpg b/images/3.2.1+设备端环境搭建_bffc8745.jpg
new file mode 100644
index 0000000..0c2eee5
Binary files /dev/null and b/images/3.2.1+设备端环境搭建_bffc8745.jpg differ
diff --git a/images/3.2.1+设备端环境搭建_c1c196c8.jpg b/images/3.2.1+设备端环境搭建_c1c196c8.jpg
new file mode 100644
index 0000000..c6ad91f
Binary files /dev/null and b/images/3.2.1+设备端环境搭建_c1c196c8.jpg differ
diff --git a/images/3.2.1+设备端环境搭建_c618f5fd.jpg b/images/3.2.1+设备端环境搭建_c618f5fd.jpg
new file mode 100644
index 0000000..becf9c5
Binary files /dev/null and b/images/3.2.1+设备端环境搭建_c618f5fd.jpg differ
diff --git a/images/3.2.1+设备端环境搭建_cd75c78f.jpg b/images/3.2.1+设备端环境搭建_cd75c78f.jpg
new file mode 100644
index 0000000..f6d95c1
Binary files /dev/null and b/images/3.2.1+设备端环境搭建_cd75c78f.jpg differ
diff --git a/images/3.2.1+设备端环境搭建_cfe5d409.jpg b/images/3.2.1+设备端环境搭建_cfe5d409.jpg
new file mode 100644
index 0000000..cb0b64a
Binary files /dev/null and b/images/3.2.1+设备端环境搭建_cfe5d409.jpg differ
diff --git a/images/3.2.1+设备端环境搭建_d8c95a8b.jpg b/images/3.2.1+设备端环境搭建_d8c95a8b.jpg
new file mode 100644
index 0000000..29508c7
Binary files /dev/null and b/images/3.2.1+设备端环境搭建_d8c95a8b.jpg differ
diff --git a/images/3.2.1+设备端环境搭建_d9ec7592.jpg b/images/3.2.1+设备端环境搭建_d9ec7592.jpg
new file mode 100644
index 0000000..7947da6
Binary files /dev/null and b/images/3.2.1+设备端环境搭建_d9ec7592.jpg differ
diff --git a/images/3.2.1+设备端环境搭建_dba3a558.jpg b/images/3.2.1+设备端环境搭建_dba3a558.jpg
new file mode 100644
index 0000000..6259921
Binary files /dev/null and b/images/3.2.1+设备端环境搭建_dba3a558.jpg differ
diff --git a/images/3.2.1+设备端环境搭建_de506e81.jpg b/images/3.2.1+设备端环境搭建_de506e81.jpg
new file mode 100644
index 0000000..e405626
Binary files /dev/null and b/images/3.2.1+设备端环境搭建_de506e81.jpg differ
diff --git a/images/3.2.1+设备端环境搭建_e689eab4.jpg b/images/3.2.1+设备端环境搭建_e689eab4.jpg
new file mode 100644
index 0000000..6c88cec
Binary files /dev/null and b/images/3.2.1+设备端环境搭建_e689eab4.jpg differ
diff --git a/images/3.2.1+设备端环境搭建_e8e3cbb6.jpg b/images/3.2.1+设备端环境搭建_e8e3cbb6.jpg
new file mode 100644
index 0000000..67278f1
Binary files /dev/null and b/images/3.2.1+设备端环境搭建_e8e3cbb6.jpg differ
diff --git a/images/3.2.1+设备端环境搭建_ed3de84f.jpg b/images/3.2.1+设备端环境搭建_ed3de84f.jpg
new file mode 100644
index 0000000..db704d5
Binary files /dev/null and b/images/3.2.1+设备端环境搭建_ed3de84f.jpg differ
diff --git a/images/3.2.1+设备端环境搭建_f081533e.jpg b/images/3.2.1+设备端环境搭建_f081533e.jpg
new file mode 100644
index 0000000..f2be290
Binary files /dev/null and b/images/3.2.1+设备端环境搭建_f081533e.jpg differ
diff --git a/images/3.2.1+设备端环境搭建_f57f20be.jpg b/images/3.2.1+设备端环境搭建_f57f20be.jpg
new file mode 100644
index 0000000..6c88cec
Binary files /dev/null and b/images/3.2.1+设备端环境搭建_f57f20be.jpg differ
diff --git a/images/3.2.1+设备端环境搭建_f58f7435.jpg b/images/3.2.1+设备端环境搭建_f58f7435.jpg
new file mode 100644
index 0000000..e5ad8ea
Binary files /dev/null and b/images/3.2.1+设备端环境搭建_f58f7435.jpg differ
diff --git a/images/3.2.1+设备端环境搭建_f5c61899.jpg b/images/3.2.1+设备端环境搭建_f5c61899.jpg
new file mode 100644
index 0000000..0a86490
Binary files /dev/null and b/images/3.2.1+设备端环境搭建_f5c61899.jpg differ
diff --git a/images/3.2.1+设备端环境搭建_f78cd98e.jpg b/images/3.2.1+设备端环境搭建_f78cd98e.jpg
new file mode 100644
index 0000000..d2665a4
Binary files /dev/null and b/images/3.2.1+设备端环境搭建_f78cd98e.jpg differ
diff --git a/images/3.2.1+设备端环境搭建_f7b6759c.jpg b/images/3.2.1+设备端环境搭建_f7b6759c.jpg
new file mode 100644
index 0000000..78e4e1a
Binary files /dev/null and b/images/3.2.1+设备端环境搭建_f7b6759c.jpg differ
diff --git a/images/3.2.1+设备端环境搭建_f7b874d6.jpg b/images/3.2.1+设备端环境搭建_f7b874d6.jpg
new file mode 100644
index 0000000..1699bb3
Binary files /dev/null and b/images/3.2.1+设备端环境搭建_f7b874d6.jpg differ
diff --git a/images/3.2.1+设备端环境搭建_f8279dc1.jpg b/images/3.2.1+设备端环境搭建_f8279dc1.jpg
new file mode 100644
index 0000000..becf9c5
Binary files /dev/null and b/images/3.2.1+设备端环境搭建_f8279dc1.jpg differ
diff --git a/images/3.2.1+设备端环境搭建_f8d77b26.jpg b/images/3.2.1+设备端环境搭建_f8d77b26.jpg
new file mode 100644
index 0000000..3c523d9
Binary files /dev/null and b/images/3.2.1+设备端环境搭建_f8d77b26.jpg differ
diff --git a/images/3.2.2+手机端环境搭建_087cd5ed.jpg b/images/3.2.2+手机端环境搭建_087cd5ed.jpg
new file mode 100644
index 0000000..b84908a
Binary files /dev/null and b/images/3.2.2+手机端环境搭建_087cd5ed.jpg differ
diff --git a/images/3.2.2+手机端环境搭建_1821108c.jpg b/images/3.2.2+手机端环境搭建_1821108c.jpg
new file mode 100644
index 0000000..64d2e42
Binary files /dev/null and b/images/3.2.2+手机端环境搭建_1821108c.jpg differ
diff --git a/images/3.2.2+手机端环境搭建_18e677a2.jpg b/images/3.2.2+手机端环境搭建_18e677a2.jpg
new file mode 100644
index 0000000..2b46edf
Binary files /dev/null and b/images/3.2.2+手机端环境搭建_18e677a2.jpg differ
diff --git a/images/3.2.2+手机端环境搭建_1a9a05dd.jpg b/images/3.2.2+手机端环境搭建_1a9a05dd.jpg
new file mode 100644
index 0000000..77a8e3f
Binary files /dev/null and b/images/3.2.2+手机端环境搭建_1a9a05dd.jpg differ
diff --git a/images/3.2.2+手机端环境搭建_257ce6f8.jpg b/images/3.2.2+手机端环境搭建_257ce6f8.jpg
new file mode 100644
index 0000000..1dda003
Binary files /dev/null and b/images/3.2.2+手机端环境搭建_257ce6f8.jpg differ
diff --git a/images/3.2.2+手机端环境搭建_2be7820a.jpg b/images/3.2.2+手机端环境搭建_2be7820a.jpg
new file mode 100644
index 0000000..1dda003
Binary files /dev/null and b/images/3.2.2+手机端环境搭建_2be7820a.jpg differ
diff --git a/images/3.2.2+手机端环境搭建_312f9d70.jpg b/images/3.2.2+手机端环境搭建_312f9d70.jpg
new file mode 100644
index 0000000..9ed6549
Binary files /dev/null and b/images/3.2.2+手机端环境搭建_312f9d70.jpg differ
diff --git a/images/3.2.2+手机端环境搭建_3699c4a3.jpg b/images/3.2.2+手机端环境搭建_3699c4a3.jpg
new file mode 100644
index 0000000..3f84e71
Binary files /dev/null and b/images/3.2.2+手机端环境搭建_3699c4a3.jpg differ
diff --git a/images/3.2.2+手机端环境搭建_40842afd.jpg b/images/3.2.2+手机端环境搭建_40842afd.jpg
new file mode 100644
index 0000000..c0e85e0
Binary files /dev/null and b/images/3.2.2+手机端环境搭建_40842afd.jpg differ
diff --git a/images/3.2.2+手机端环境搭建_41bafee1.jpg b/images/3.2.2+手机端环境搭建_41bafee1.jpg
new file mode 100644
index 0000000..15ae088
Binary files /dev/null and b/images/3.2.2+手机端环境搭建_41bafee1.jpg differ
diff --git a/images/3.2.2+手机端环境搭建_45788efc.jpg b/images/3.2.2+手机端环境搭建_45788efc.jpg
new file mode 100644
index 0000000..3742274
Binary files /dev/null and b/images/3.2.2+手机端环境搭建_45788efc.jpg differ
diff --git a/images/3.2.2+手机端环境搭建_48e69713.jpg b/images/3.2.2+手机端环境搭建_48e69713.jpg
new file mode 100644
index 0000000..ee2114e
Binary files /dev/null and b/images/3.2.2+手机端环境搭建_48e69713.jpg differ
diff --git a/images/3.2.2+手机端环境搭建_4da75d07.jpg b/images/3.2.2+手机端环境搭建_4da75d07.jpg
new file mode 100644
index 0000000..b7ce1dd
Binary files /dev/null and b/images/3.2.2+手机端环境搭建_4da75d07.jpg differ
diff --git a/images/3.2.2+手机端环境搭建_5b2606fc.jpg b/images/3.2.2+手机端环境搭建_5b2606fc.jpg
new file mode 100644
index 0000000..facfdbb
Binary files /dev/null and b/images/3.2.2+手机端环境搭建_5b2606fc.jpg differ
diff --git a/images/3.2.2+手机端环境搭建_63d75846.jpg b/images/3.2.2+手机端环境搭建_63d75846.jpg
new file mode 100644
index 0000000..de363b1
Binary files /dev/null and b/images/3.2.2+手机端环境搭建_63d75846.jpg differ
diff --git a/images/3.2.2+手机端环境搭建_6b279132.jpg b/images/3.2.2+手机端环境搭建_6b279132.jpg
new file mode 100644
index 0000000..4c1855f
Binary files /dev/null and b/images/3.2.2+手机端环境搭建_6b279132.jpg differ
diff --git a/images/3.2.2+手机端环境搭建_71144882.jpg b/images/3.2.2+手机端环境搭建_71144882.jpg
new file mode 100644
index 0000000..2a1ff26
Binary files /dev/null and b/images/3.2.2+手机端环境搭建_71144882.jpg differ
diff --git a/images/3.2.2+手机端环境搭建_79f52010.jpg b/images/3.2.2+手机端环境搭建_79f52010.jpg
new file mode 100644
index 0000000..3742274
Binary files /dev/null and b/images/3.2.2+手机端环境搭建_79f52010.jpg differ
diff --git a/images/3.2.2+手机端环境搭建_841e1520.jpg b/images/3.2.2+手机端环境搭建_841e1520.jpg
new file mode 100644
index 0000000..77a8e3f
Binary files /dev/null and b/images/3.2.2+手机端环境搭建_841e1520.jpg differ
diff --git a/images/3.2.2+手机端环境搭建_93892106.jpg b/images/3.2.2+手机端环境搭建_93892106.jpg
new file mode 100644
index 0000000..15ae088
Binary files /dev/null and b/images/3.2.2+手机端环境搭建_93892106.jpg differ
diff --git a/images/3.2.2+手机端环境搭建_96093a74.jpg b/images/3.2.2+手机端环境搭建_96093a74.jpg
new file mode 100644
index 0000000..4c1855f
Binary files /dev/null and b/images/3.2.2+手机端环境搭建_96093a74.jpg differ
diff --git a/images/3.2.2+手机端环境搭建_9732f77a.jpg b/images/3.2.2+手机端环境搭建_9732f77a.jpg
new file mode 100644
index 0000000..6d2af57
Binary files /dev/null and b/images/3.2.2+手机端环境搭建_9732f77a.jpg differ
diff --git a/images/3.2.2+手机端环境搭建_a323ef31.jpg b/images/3.2.2+手机端环境搭建_a323ef31.jpg
new file mode 100644
index 0000000..2a1ff26
Binary files /dev/null and b/images/3.2.2+手机端环境搭建_a323ef31.jpg differ
diff --git a/images/3.2.2+手机端环境搭建_ad646e96.jpg b/images/3.2.2+手机端环境搭建_ad646e96.jpg
new file mode 100644
index 0000000..facfdbb
Binary files /dev/null and b/images/3.2.2+手机端环境搭建_ad646e96.jpg differ
diff --git a/images/3.2.2+手机端环境搭建_ad916708.jpg b/images/3.2.2+手机端环境搭建_ad916708.jpg
new file mode 100644
index 0000000..c3def5e
Binary files /dev/null and b/images/3.2.2+手机端环境搭建_ad916708.jpg differ
diff --git a/images/3.2.2+手机端环境搭建_ae270705.jpg b/images/3.2.2+手机端环境搭建_ae270705.jpg
new file mode 100644
index 0000000..302ade0
Binary files /dev/null and b/images/3.2.2+手机端环境搭建_ae270705.jpg differ
diff --git a/images/3.2.2+手机端环境搭建_af68af94.jpg b/images/3.2.2+手机端环境搭建_af68af94.jpg
new file mode 100644
index 0000000..9ed6549
Binary files /dev/null and b/images/3.2.2+手机端环境搭建_af68af94.jpg differ
diff --git a/images/3.2.2+手机端环境搭建_af72ff1d.jpg b/images/3.2.2+手机端环境搭建_af72ff1d.jpg
new file mode 100644
index 0000000..631b957
Binary files /dev/null and b/images/3.2.2+手机端环境搭建_af72ff1d.jpg differ
diff --git a/images/3.2.2+手机端环境搭建_b1ba9267.jpg b/images/3.2.2+手机端环境搭建_b1ba9267.jpg
new file mode 100644
index 0000000..c0e85e0
Binary files /dev/null and b/images/3.2.2+手机端环境搭建_b1ba9267.jpg differ
diff --git a/images/3.2.2+手机端环境搭建_b80a0848.jpg b/images/3.2.2+手机端环境搭建_b80a0848.jpg
new file mode 100644
index 0000000..b447433
Binary files /dev/null and b/images/3.2.2+手机端环境搭建_b80a0848.jpg differ
diff --git a/images/3.2.2+手机端环境搭建_bac92254.jpg b/images/3.2.2+手机端环境搭建_bac92254.jpg
new file mode 100644
index 0000000..b7ce1dd
Binary files /dev/null and b/images/3.2.2+手机端环境搭建_bac92254.jpg differ
diff --git a/images/3.2.2+手机端环境搭建_bbf365ad.jpg b/images/3.2.2+手机端环境搭建_bbf365ad.jpg
new file mode 100644
index 0000000..c3def5e
Binary files /dev/null and b/images/3.2.2+手机端环境搭建_bbf365ad.jpg differ
diff --git a/images/3.2.2+手机端环境搭建_bcf773aa.jpg b/images/3.2.2+手机端环境搭建_bcf773aa.jpg
new file mode 100644
index 0000000..de363b1
Binary files /dev/null and b/images/3.2.2+手机端环境搭建_bcf773aa.jpg differ
diff --git a/images/3.2.2+手机端环境搭建_beeb9b6e.jpg b/images/3.2.2+手机端环境搭建_beeb9b6e.jpg
new file mode 100644
index 0000000..2b46edf
Binary files /dev/null and b/images/3.2.2+手机端环境搭建_beeb9b6e.jpg differ
diff --git a/images/3.2.2+手机端环境搭建_c01e09e4.jpg b/images/3.2.2+手机端环境搭建_c01e09e4.jpg
new file mode 100644
index 0000000..631b957
Binary files /dev/null and b/images/3.2.2+手机端环境搭建_c01e09e4.jpg differ
diff --git a/images/3.2.2+手机端环境搭建_c2620529.jpg b/images/3.2.2+手机端环境搭建_c2620529.jpg
new file mode 100644
index 0000000..3f84e71
Binary files /dev/null and b/images/3.2.2+手机端环境搭建_c2620529.jpg differ
diff --git a/images/3.2.2+手机端环境搭建_c4822c36.jpg b/images/3.2.2+手机端环境搭建_c4822c36.jpg
new file mode 100644
index 0000000..b84908a
Binary files /dev/null and b/images/3.2.2+手机端环境搭建_c4822c36.jpg differ
diff --git a/images/3.2.2+手机端环境搭建_d0fdd334.jpg b/images/3.2.2+手机端环境搭建_d0fdd334.jpg
new file mode 100644
index 0000000..6d2af57
Binary files /dev/null and b/images/3.2.2+手机端环境搭建_d0fdd334.jpg differ
diff --git a/images/3.2.2+手机端环境搭建_da62de8e.jpg b/images/3.2.2+手机端环境搭建_da62de8e.jpg
new file mode 100644
index 0000000..b447433
Binary files /dev/null and b/images/3.2.2+手机端环境搭建_da62de8e.jpg differ
diff --git a/images/3.2.2+手机端环境搭建_e2ee4936.jpg b/images/3.2.2+手机端环境搭建_e2ee4936.jpg
new file mode 100644
index 0000000..302ade0
Binary files /dev/null and b/images/3.2.2+手机端环境搭建_e2ee4936.jpg differ
diff --git a/images/3.2.2+手机端环境搭建_f090abb3.jpg b/images/3.2.2+手机端环境搭建_f090abb3.jpg
new file mode 100644
index 0000000..64d2e42
Binary files /dev/null and b/images/3.2.2+手机端环境搭建_f090abb3.jpg differ
diff --git a/images/3.2.2+手机端环境搭建_f7057ebc.jpg b/images/3.2.2+手机端环境搭建_f7057ebc.jpg
new file mode 100644
index 0000000..ee2114e
Binary files /dev/null and b/images/3.2.2+手机端环境搭建_f7057ebc.jpg differ
diff --git a/images/3.2.3+Fast+Pair+Validator+环境搭建_0bd7a51e.jpg b/images/3.2.3+Fast+Pair+Validator+环境搭建_0bd7a51e.jpg
new file mode 100644
index 0000000..c5bbb74
Binary files /dev/null and b/images/3.2.3+Fast+Pair+Validator+环境搭建_0bd7a51e.jpg differ
diff --git a/images/3.2.3+Fast+Pair+Validator+环境搭建_0bf7e831.jpg b/images/3.2.3+Fast+Pair+Validator+环境搭建_0bf7e831.jpg
new file mode 100644
index 0000000..7dcfef7
Binary files /dev/null and b/images/3.2.3+Fast+Pair+Validator+环境搭建_0bf7e831.jpg differ
diff --git a/images/3.2.3+Fast+Pair+Validator+环境搭建_0c0e1ac5.jpg b/images/3.2.3+Fast+Pair+Validator+环境搭建_0c0e1ac5.jpg
new file mode 100644
index 0000000..b84908a
Binary files /dev/null and b/images/3.2.3+Fast+Pair+Validator+环境搭建_0c0e1ac5.jpg differ
diff --git a/images/3.2.3+Fast+Pair+Validator+环境搭建_15ed8fbc.jpg b/images/3.2.3+Fast+Pair+Validator+环境搭建_15ed8fbc.jpg
new file mode 100644
index 0000000..64d2e42
Binary files /dev/null and b/images/3.2.3+Fast+Pair+Validator+环境搭建_15ed8fbc.jpg differ
diff --git a/images/3.2.3+Fast+Pair+Validator+环境搭建_184d5cce.jpg b/images/3.2.3+Fast+Pair+Validator+环境搭建_184d5cce.jpg
new file mode 100644
index 0000000..9ed6549
Binary files /dev/null and b/images/3.2.3+Fast+Pair+Validator+环境搭建_184d5cce.jpg differ
diff --git a/images/3.2.3+Fast+Pair+Validator+环境搭建_1c39b7f3.jpg b/images/3.2.3+Fast+Pair+Validator+环境搭建_1c39b7f3.jpg
new file mode 100644
index 0000000..2b46edf
Binary files /dev/null and b/images/3.2.3+Fast+Pair+Validator+环境搭建_1c39b7f3.jpg differ
diff --git a/images/3.2.3+Fast+Pair+Validator+环境搭建_1f7523d2.jpg b/images/3.2.3+Fast+Pair+Validator+环境搭建_1f7523d2.jpg
new file mode 100644
index 0000000..6d2af57
Binary files /dev/null and b/images/3.2.3+Fast+Pair+Validator+环境搭建_1f7523d2.jpg differ
diff --git a/images/3.2.3+Fast+Pair+Validator+环境搭建_2014efee.jpg b/images/3.2.3+Fast+Pair+Validator+环境搭建_2014efee.jpg
new file mode 100644
index 0000000..503cb7d
Binary files /dev/null and b/images/3.2.3+Fast+Pair+Validator+环境搭建_2014efee.jpg differ
diff --git a/images/3.2.3+Fast+Pair+Validator+环境搭建_228ec9dd.jpg b/images/3.2.3+Fast+Pair+Validator+环境搭建_228ec9dd.jpg
new file mode 100644
index 0000000..2a1ff26
Binary files /dev/null and b/images/3.2.3+Fast+Pair+Validator+环境搭建_228ec9dd.jpg differ
diff --git a/images/3.2.3+Fast+Pair+Validator+环境搭建_27c4c280.jpg b/images/3.2.3+Fast+Pair+Validator+环境搭建_27c4c280.jpg
new file mode 100644
index 0000000..4c1855f
Binary files /dev/null and b/images/3.2.3+Fast+Pair+Validator+环境搭建_27c4c280.jpg differ
diff --git a/images/3.2.3+Fast+Pair+Validator+环境搭建_2c7523ad.jpg b/images/3.2.3+Fast+Pair+Validator+环境搭建_2c7523ad.jpg
new file mode 100644
index 0000000..15ae088
Binary files /dev/null and b/images/3.2.3+Fast+Pair+Validator+环境搭建_2c7523ad.jpg differ
diff --git a/images/3.2.3+Fast+Pair+Validator+环境搭建_33263cca.jpg b/images/3.2.3+Fast+Pair+Validator+环境搭建_33263cca.jpg
new file mode 100644
index 0000000..3f84e71
Binary files /dev/null and b/images/3.2.3+Fast+Pair+Validator+环境搭建_33263cca.jpg differ
diff --git a/images/3.2.3+Fast+Pair+Validator+环境搭建_3f781af7.jpg b/images/3.2.3+Fast+Pair+Validator+环境搭建_3f781af7.jpg
new file mode 100644
index 0000000..c0e85e0
Binary files /dev/null and b/images/3.2.3+Fast+Pair+Validator+环境搭建_3f781af7.jpg differ
diff --git a/images/3.2.3+Fast+Pair+Validator+环境搭建_4794eeeb.jpg b/images/3.2.3+Fast+Pair+Validator+环境搭建_4794eeeb.jpg
new file mode 100644
index 0000000..b447433
Binary files /dev/null and b/images/3.2.3+Fast+Pair+Validator+环境搭建_4794eeeb.jpg differ
diff --git a/images/3.2.3+Fast+Pair+Validator+环境搭建_4df5f09f.jpg b/images/3.2.3+Fast+Pair+Validator+环境搭建_4df5f09f.jpg
new file mode 100644
index 0000000..3f84e71
Binary files /dev/null and b/images/3.2.3+Fast+Pair+Validator+环境搭建_4df5f09f.jpg differ
diff --git a/images/3.2.3+Fast+Pair+Validator+环境搭建_51afc947.jpg b/images/3.2.3+Fast+Pair+Validator+环境搭建_51afc947.jpg
new file mode 100644
index 0000000..631b957
Binary files /dev/null and b/images/3.2.3+Fast+Pair+Validator+环境搭建_51afc947.jpg differ
diff --git a/images/3.2.3+Fast+Pair+Validator+环境搭建_55227e2f.jpg b/images/3.2.3+Fast+Pair+Validator+环境搭建_55227e2f.jpg
new file mode 100644
index 0000000..6d2af57
Binary files /dev/null and b/images/3.2.3+Fast+Pair+Validator+环境搭建_55227e2f.jpg differ
diff --git a/images/3.2.3+Fast+Pair+Validator+环境搭建_5a8372c9.jpg b/images/3.2.3+Fast+Pair+Validator+环境搭建_5a8372c9.jpg
new file mode 100644
index 0000000..302ade0
Binary files /dev/null and b/images/3.2.3+Fast+Pair+Validator+环境搭建_5a8372c9.jpg differ
diff --git a/images/3.2.3+Fast+Pair+Validator+环境搭建_62b681a3.jpg b/images/3.2.3+Fast+Pair+Validator+环境搭建_62b681a3.jpg
new file mode 100644
index 0000000..2b46edf
Binary files /dev/null and b/images/3.2.3+Fast+Pair+Validator+环境搭建_62b681a3.jpg differ
diff --git a/images/3.2.3+Fast+Pair+Validator+环境搭建_660344ce.jpg b/images/3.2.3+Fast+Pair+Validator+环境搭建_660344ce.jpg
new file mode 100644
index 0000000..503cb7d
Binary files /dev/null and b/images/3.2.3+Fast+Pair+Validator+环境搭建_660344ce.jpg differ
diff --git a/images/3.2.3+Fast+Pair+Validator+环境搭建_6c8d68f3.jpg b/images/3.2.3+Fast+Pair+Validator+环境搭建_6c8d68f3.jpg
new file mode 100644
index 0000000..7dcfef7
Binary files /dev/null and b/images/3.2.3+Fast+Pair+Validator+环境搭建_6c8d68f3.jpg differ
diff --git a/images/3.2.3+Fast+Pair+Validator+环境搭建_70149c62.jpg b/images/3.2.3+Fast+Pair+Validator+环境搭建_70149c62.jpg
new file mode 100644
index 0000000..c7ccda3
Binary files /dev/null and b/images/3.2.3+Fast+Pair+Validator+环境搭建_70149c62.jpg differ
diff --git a/images/3.2.3+Fast+Pair+Validator+环境搭建_7199c69b.jpg b/images/3.2.3+Fast+Pair+Validator+环境搭建_7199c69b.jpg
new file mode 100644
index 0000000..64d2e42
Binary files /dev/null and b/images/3.2.3+Fast+Pair+Validator+环境搭建_7199c69b.jpg differ
diff --git a/images/3.2.3+Fast+Pair+Validator+环境搭建_77a5b9af.jpg b/images/3.2.3+Fast+Pair+Validator+环境搭建_77a5b9af.jpg
new file mode 100644
index 0000000..b7ce1dd
Binary files /dev/null and b/images/3.2.3+Fast+Pair+Validator+环境搭建_77a5b9af.jpg differ
diff --git a/images/3.2.3+Fast+Pair+Validator+环境搭建_831201f3.jpg b/images/3.2.3+Fast+Pair+Validator+环境搭建_831201f3.jpg
new file mode 100644
index 0000000..4c1855f
Binary files /dev/null and b/images/3.2.3+Fast+Pair+Validator+环境搭建_831201f3.jpg differ
diff --git a/images/3.2.3+Fast+Pair+Validator+环境搭建_9158c97c.jpg b/images/3.2.3+Fast+Pair+Validator+环境搭建_9158c97c.jpg
new file mode 100644
index 0000000..c0e85e0
Binary files /dev/null and b/images/3.2.3+Fast+Pair+Validator+环境搭建_9158c97c.jpg differ
diff --git a/images/3.2.3+Fast+Pair+Validator+环境搭建_96e7a442.jpg b/images/3.2.3+Fast+Pair+Validator+环境搭建_96e7a442.jpg
new file mode 100644
index 0000000..b4477df
Binary files /dev/null and b/images/3.2.3+Fast+Pair+Validator+环境搭建_96e7a442.jpg differ
diff --git a/images/3.2.3+Fast+Pair+Validator+环境搭建_9aa353cb.jpg b/images/3.2.3+Fast+Pair+Validator+环境搭建_9aa353cb.jpg
new file mode 100644
index 0000000..ab658c5
Binary files /dev/null and b/images/3.2.3+Fast+Pair+Validator+环境搭建_9aa353cb.jpg differ
diff --git a/images/3.2.3+Fast+Pair+Validator+环境搭建_9b9ccc52.jpg b/images/3.2.3+Fast+Pair+Validator+环境搭建_9b9ccc52.jpg
new file mode 100644
index 0000000..b4477df
Binary files /dev/null and b/images/3.2.3+Fast+Pair+Validator+环境搭建_9b9ccc52.jpg differ
diff --git a/images/3.2.3+Fast+Pair+Validator+环境搭建_a063892b.jpg b/images/3.2.3+Fast+Pair+Validator+环境搭建_a063892b.jpg
new file mode 100644
index 0000000..6ec45ec
Binary files /dev/null and b/images/3.2.3+Fast+Pair+Validator+环境搭建_a063892b.jpg differ
diff --git a/images/3.2.3+Fast+Pair+Validator+环境搭建_a451d380.jpg b/images/3.2.3+Fast+Pair+Validator+环境搭建_a451d380.jpg
new file mode 100644
index 0000000..b7ce1dd
Binary files /dev/null and b/images/3.2.3+Fast+Pair+Validator+环境搭建_a451d380.jpg differ
diff --git a/images/3.2.3+Fast+Pair+Validator+环境搭建_a74ae4d1.jpg b/images/3.2.3+Fast+Pair+Validator+环境搭建_a74ae4d1.jpg
new file mode 100644
index 0000000..ab658c5
Binary files /dev/null and b/images/3.2.3+Fast+Pair+Validator+环境搭建_a74ae4d1.jpg differ
diff --git a/images/3.2.3+Fast+Pair+Validator+环境搭建_aa196b62.jpg b/images/3.2.3+Fast+Pair+Validator+环境搭建_aa196b62.jpg
new file mode 100644
index 0000000..15ae088
Binary files /dev/null and b/images/3.2.3+Fast+Pair+Validator+环境搭建_aa196b62.jpg differ
diff --git a/images/3.2.3+Fast+Pair+Validator+环境搭建_b37cf3b3.jpg b/images/3.2.3+Fast+Pair+Validator+环境搭建_b37cf3b3.jpg
new file mode 100644
index 0000000..071d3f9
Binary files /dev/null and b/images/3.2.3+Fast+Pair+Validator+环境搭建_b37cf3b3.jpg differ
diff --git a/images/3.2.3+Fast+Pair+Validator+环境搭建_b90fcff2.jpg b/images/3.2.3+Fast+Pair+Validator+环境搭建_b90fcff2.jpg
new file mode 100644
index 0000000..c5bbb74
Binary files /dev/null and b/images/3.2.3+Fast+Pair+Validator+环境搭建_b90fcff2.jpg differ
diff --git a/images/3.2.3+Fast+Pair+Validator+环境搭建_b958155e.jpg b/images/3.2.3+Fast+Pair+Validator+环境搭建_b958155e.jpg
new file mode 100644
index 0000000..6ec45ec
Binary files /dev/null and b/images/3.2.3+Fast+Pair+Validator+环境搭建_b958155e.jpg differ
diff --git a/images/3.2.3+Fast+Pair+Validator+环境搭建_ba4aa01c.jpg b/images/3.2.3+Fast+Pair+Validator+环境搭建_ba4aa01c.jpg
new file mode 100644
index 0000000..1dda003
Binary files /dev/null and b/images/3.2.3+Fast+Pair+Validator+环境搭建_ba4aa01c.jpg differ
diff --git a/images/3.2.3+Fast+Pair+Validator+环境搭建_bd6c07be.jpg b/images/3.2.3+Fast+Pair+Validator+环境搭建_bd6c07be.jpg
new file mode 100644
index 0000000..1dda003
Binary files /dev/null and b/images/3.2.3+Fast+Pair+Validator+环境搭建_bd6c07be.jpg differ
diff --git a/images/3.2.3+Fast+Pair+Validator+环境搭建_bee00688.jpg b/images/3.2.3+Fast+Pair+Validator+环境搭建_bee00688.jpg
new file mode 100644
index 0000000..c3def5e
Binary files /dev/null and b/images/3.2.3+Fast+Pair+Validator+环境搭建_bee00688.jpg differ
diff --git a/images/3.2.3+Fast+Pair+Validator+环境搭建_c64987c6.jpg b/images/3.2.3+Fast+Pair+Validator+环境搭建_c64987c6.jpg
new file mode 100644
index 0000000..2a1ff26
Binary files /dev/null and b/images/3.2.3+Fast+Pair+Validator+环境搭建_c64987c6.jpg differ
diff --git a/images/3.2.3+Fast+Pair+Validator+环境搭建_c833530c.jpg b/images/3.2.3+Fast+Pair+Validator+环境搭建_c833530c.jpg
new file mode 100644
index 0000000..9ed6549
Binary files /dev/null and b/images/3.2.3+Fast+Pair+Validator+环境搭建_c833530c.jpg differ
diff --git a/images/3.2.3+Fast+Pair+Validator+环境搭建_cce3e315.jpg b/images/3.2.3+Fast+Pair+Validator+环境搭建_cce3e315.jpg
new file mode 100644
index 0000000..071d3f9
Binary files /dev/null and b/images/3.2.3+Fast+Pair+Validator+环境搭建_cce3e315.jpg differ
diff --git a/images/3.2.3+Fast+Pair+Validator+环境搭建_cf2fb9b6.jpg b/images/3.2.3+Fast+Pair+Validator+环境搭建_cf2fb9b6.jpg
new file mode 100644
index 0000000..6a7bd33
Binary files /dev/null and b/images/3.2.3+Fast+Pair+Validator+环境搭建_cf2fb9b6.jpg differ
diff --git a/images/3.2.3+Fast+Pair+Validator+环境搭建_d3f5b883.jpg b/images/3.2.3+Fast+Pair+Validator+环境搭建_d3f5b883.jpg
new file mode 100644
index 0000000..631b957
Binary files /dev/null and b/images/3.2.3+Fast+Pair+Validator+环境搭建_d3f5b883.jpg differ
diff --git a/images/3.2.3+Fast+Pair+Validator+环境搭建_d84806a2.jpg b/images/3.2.3+Fast+Pair+Validator+环境搭建_d84806a2.jpg
new file mode 100644
index 0000000..b447433
Binary files /dev/null and b/images/3.2.3+Fast+Pair+Validator+环境搭建_d84806a2.jpg differ
diff --git a/images/3.2.3+Fast+Pair+Validator+环境搭建_ead146a4.jpg b/images/3.2.3+Fast+Pair+Validator+环境搭建_ead146a4.jpg
new file mode 100644
index 0000000..302ade0
Binary files /dev/null and b/images/3.2.3+Fast+Pair+Validator+环境搭建_ead146a4.jpg differ
diff --git a/images/3.2.3+Fast+Pair+Validator+环境搭建_eb372dad.jpg b/images/3.2.3+Fast+Pair+Validator+环境搭建_eb372dad.jpg
new file mode 100644
index 0000000..facfdbb
Binary files /dev/null and b/images/3.2.3+Fast+Pair+Validator+环境搭建_eb372dad.jpg differ
diff --git a/images/3.2.3+Fast+Pair+Validator+环境搭建_efe34ee0.jpg b/images/3.2.3+Fast+Pair+Validator+环境搭建_efe34ee0.jpg
new file mode 100644
index 0000000..6a7bd33
Binary files /dev/null and b/images/3.2.3+Fast+Pair+Validator+环境搭建_efe34ee0.jpg differ
diff --git a/images/3.2.3+Fast+Pair+Validator+环境搭建_f075b770.jpg b/images/3.2.3+Fast+Pair+Validator+环境搭建_f075b770.jpg
new file mode 100644
index 0000000..b84908a
Binary files /dev/null and b/images/3.2.3+Fast+Pair+Validator+环境搭建_f075b770.jpg differ
diff --git a/images/3.2.3+Fast+Pair+Validator+环境搭建_f265bbcf.jpg b/images/3.2.3+Fast+Pair+Validator+环境搭建_f265bbcf.jpg
new file mode 100644
index 0000000..c3def5e
Binary files /dev/null and b/images/3.2.3+Fast+Pair+Validator+环境搭建_f265bbcf.jpg differ
diff --git a/images/3.2.3+Fast+Pair+Validator+环境搭建_f45eb9e5.jpg b/images/3.2.3+Fast+Pair+Validator+环境搭建_f45eb9e5.jpg
new file mode 100644
index 0000000..facfdbb
Binary files /dev/null and b/images/3.2.3+Fast+Pair+Validator+环境搭建_f45eb9e5.jpg differ
diff --git a/images/3.2.3+Fast+Pair+Validator+环境搭建_f4e4684b.jpg b/images/3.2.3+Fast+Pair+Validator+环境搭建_f4e4684b.jpg
new file mode 100644
index 0000000..c7ccda3
Binary files /dev/null and b/images/3.2.3+Fast+Pair+Validator+环境搭建_f4e4684b.jpg differ
diff --git a/images/3.3+测试_1f9290b8.jpg b/images/3.3+测试_1f9290b8.jpg
new file mode 100644
index 0000000..452df53
Binary files /dev/null and b/images/3.3+测试_1f9290b8.jpg differ
diff --git a/images/3.3+测试_255d311f.jpg b/images/3.3+测试_255d311f.jpg
new file mode 100644
index 0000000..0dece59
Binary files /dev/null and b/images/3.3+测试_255d311f.jpg differ
diff --git a/images/3.3+测试_3969bbe0.jpg b/images/3.3+测试_3969bbe0.jpg
new file mode 100644
index 0000000..e363de3
Binary files /dev/null and b/images/3.3+测试_3969bbe0.jpg differ
diff --git a/images/3.3+测试_520a2573.jpg b/images/3.3+测试_520a2573.jpg
new file mode 100644
index 0000000..0dece59
Binary files /dev/null and b/images/3.3+测试_520a2573.jpg differ
diff --git a/images/3.3+测试_76ded63e.jpg b/images/3.3+测试_76ded63e.jpg
new file mode 100644
index 0000000..452df53
Binary files /dev/null and b/images/3.3+测试_76ded63e.jpg differ
diff --git a/images/3.3+测试_a4b6b498.jpg b/images/3.3+测试_a4b6b498.jpg
new file mode 100644
index 0000000..e363de3
Binary files /dev/null and b/images/3.3+测试_a4b6b498.jpg differ
diff --git a/images/3.3.1+Fast+Pair+Validator+测试_70de39f0.jpg b/images/3.3.1+Fast+Pair+Validator+测试_70de39f0.jpg
new file mode 100644
index 0000000..240e358
Binary files /dev/null and b/images/3.3.1+Fast+Pair+Validator+测试_70de39f0.jpg differ
diff --git a/images/3.3.1+Fast+Pair+Validator+测试_e82e0572.jpg b/images/3.3.1+Fast+Pair+Validator+测试_e82e0572.jpg
new file mode 100644
index 0000000..240e358
Binary files /dev/null and b/images/3.3.1+Fast+Pair+Validator+测试_e82e0572.jpg differ
diff --git a/images/3.3.1.1+FAST+PAIR_66c14477.jpg b/images/3.3.1.1+FAST+PAIR_66c14477.jpg
new file mode 100644
index 0000000..ca1059e
Binary files /dev/null and b/images/3.3.1.1+FAST+PAIR_66c14477.jpg differ
diff --git a/images/3.3.1.1+FAST+PAIR_7939a8ab.jpg b/images/3.3.1.1+FAST+PAIR_7939a8ab.jpg
new file mode 100644
index 0000000..ca1059e
Binary files /dev/null and b/images/3.3.1.1+FAST+PAIR_7939a8ab.jpg differ
diff --git a/images/4+pixel6(android+12)+不连A2DP_1cdf2e3d.jpg b/images/4+pixel6(android+12)+不连A2DP_1cdf2e3d.jpg
new file mode 100644
index 0000000..553f2a1
Binary files /dev/null and b/images/4+pixel6(android+12)+不连A2DP_1cdf2e3d.jpg differ
diff --git a/images/4+pixel6(android+12)+不连A2DP_3e6271b1.jpg b/images/4+pixel6(android+12)+不连A2DP_3e6271b1.jpg
new file mode 100644
index 0000000..553f2a1
Binary files /dev/null and b/images/4+pixel6(android+12)+不连A2DP_3e6271b1.jpg differ
diff --git a/images/4+弹框提示_无法连接到查找中心__cb3062b4.jpg b/images/4+弹框提示_无法连接到查找中心__cb3062b4.jpg
new file mode 100644
index 0000000..9e4755d
Binary files /dev/null and b/images/4+弹框提示_无法连接到查找中心__cb3062b4.jpg differ
diff --git a/images/4+弹框提示_无法连接到查找中心__ce2c0101.jpg b/images/4+弹框提示_无法连接到查找中心__ce2c0101.jpg
new file mode 100644
index 0000000..9e4755d
Binary files /dev/null and b/images/4+弹框提示_无法连接到查找中心__ce2c0101.jpg differ
diff --git a/images/4.1+Observed+standard+deviation+is+too+low,+........_113ce3ab.jpg b/images/4.1+Observed+standard+deviation+is+too+low,+........_113ce3ab.jpg
new file mode 100644
index 0000000..333e549
Binary files /dev/null and b/images/4.1+Observed+standard+deviation+is+too+low,+........_113ce3ab.jpg differ
diff --git a/images/4.1+Observed+standard+deviation+is+too+low,+........_3fbae7c4.jpg b/images/4.1+Observed+standard+deviation+is+too+low,+........_3fbae7c4.jpg
new file mode 100644
index 0000000..333e549
Binary files /dev/null and b/images/4.1+Observed+standard+deviation+is+too+low,+........_3fbae7c4.jpg differ
diff --git a/images/4.1+Observed+standard+deviation+is+too+low,+........_4b45b6f2.jpg b/images/4.1+Observed+standard+deviation+is+too+low,+........_4b45b6f2.jpg
new file mode 100644
index 0000000..703ce7a
Binary files /dev/null and b/images/4.1+Observed+standard+deviation+is+too+low,+........_4b45b6f2.jpg differ
diff --git a/images/4.1+Observed+standard+deviation+is+too+low,+........_9e367358.jpg b/images/4.1+Observed+standard+deviation+is+too+low,+........_9e367358.jpg
new file mode 100644
index 0000000..703ce7a
Binary files /dev/null and b/images/4.1+Observed+standard+deviation+is+too+low,+........_9e367358.jpg differ
diff --git a/images/4.2+advertisement+rotation+fail-“device+not+find+by+EID”_4991543f.jpg b/images/4.2+advertisement+rotation+fail-“device+not+find+by+EID”_4991543f.jpg
new file mode 100644
index 0000000..a89b347
Binary files /dev/null and b/images/4.2+advertisement+rotation+fail-“device+not+find+by+EID”_4991543f.jpg differ
diff --git a/images/4.2+advertisement+rotation+fail-“device+not+find+by+EID”_c2bb91e9.jpg b/images/4.2+advertisement+rotation+fail-“device+not+find+by+EID”_c2bb91e9.jpg
new file mode 100644
index 0000000..a89b347
Binary files /dev/null and b/images/4.2+advertisement+rotation+fail-“device+not+find+by+EID”_c2bb91e9.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_0284f230.jpg b/images/4.2.1+设备端环境搭建_0284f230.jpg
new file mode 100644
index 0000000..f2be290
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_0284f230.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_053805ac.jpg b/images/4.2.1+设备端环境搭建_053805ac.jpg
new file mode 100644
index 0000000..29508c7
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_053805ac.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_092e3d72.jpg b/images/4.2.1+设备端环境搭建_092e3d72.jpg
new file mode 100644
index 0000000..013773f
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_092e3d72.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_0acf8ab6.jpg b/images/4.2.1+设备端环境搭建_0acf8ab6.jpg
new file mode 100644
index 0000000..0918a08
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_0acf8ab6.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_0dbc15a8.jpg b/images/4.2.1+设备端环境搭建_0dbc15a8.jpg
new file mode 100644
index 0000000..0d8f6c4
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_0dbc15a8.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_0e2cdd12.jpg b/images/4.2.1+设备端环境搭建_0e2cdd12.jpg
new file mode 100644
index 0000000..d4d7f50
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_0e2cdd12.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_0e7f370d.jpg b/images/4.2.1+设备端环境搭建_0e7f370d.jpg
new file mode 100644
index 0000000..1699bb3
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_0e7f370d.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_12a454dc.jpg b/images/4.2.1+设备端环境搭建_12a454dc.jpg
new file mode 100644
index 0000000..fb2c74b
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_12a454dc.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_1fe878fc.jpg b/images/4.2.1+设备端环境搭建_1fe878fc.jpg
new file mode 100644
index 0000000..d1c576d
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_1fe878fc.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_21049149.jpg b/images/4.2.1+设备端环境搭建_21049149.jpg
new file mode 100644
index 0000000..cb0b64a
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_21049149.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_21438ec8.jpg b/images/4.2.1+设备端环境搭建_21438ec8.jpg
new file mode 100644
index 0000000..5b771ea
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_21438ec8.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_2273ec86.jpg b/images/4.2.1+设备端环境搭建_2273ec86.jpg
new file mode 100644
index 0000000..7947da6
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_2273ec86.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_23a403d7.jpg b/images/4.2.1+设备端环境搭建_23a403d7.jpg
new file mode 100644
index 0000000..1433f73
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_23a403d7.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_2661c85e.jpg b/images/4.2.1+设备端环境搭建_2661c85e.jpg
new file mode 100644
index 0000000..0c2eee5
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_2661c85e.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_277c9ade.jpg b/images/4.2.1+设备端环境搭建_277c9ade.jpg
new file mode 100644
index 0000000..78e4e1a
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_277c9ade.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_29595b73.jpg b/images/4.2.1+设备端环境搭建_29595b73.jpg
new file mode 100644
index 0000000..29508c7
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_29595b73.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_2b7172d2.jpg b/images/4.2.1+设备端环境搭建_2b7172d2.jpg
new file mode 100644
index 0000000..3c523d9
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_2b7172d2.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_2bfda4dc.jpg b/images/4.2.1+设备端环境搭建_2bfda4dc.jpg
new file mode 100644
index 0000000..67278f1
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_2bfda4dc.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_307c74f6.jpg b/images/4.2.1+设备端环境搭建_307c74f6.jpg
new file mode 100644
index 0000000..7947da6
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_307c74f6.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_33d0b306.jpg b/images/4.2.1+设备端环境搭建_33d0b306.jpg
new file mode 100644
index 0000000..241e744
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_33d0b306.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_376e249f.jpg b/images/4.2.1+设备端环境搭建_376e249f.jpg
new file mode 100644
index 0000000..56c2ce9
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_376e249f.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_379047b0.jpg b/images/4.2.1+设备端环境搭建_379047b0.jpg
new file mode 100644
index 0000000..d2665a4
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_379047b0.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_37be2cae.jpg b/images/4.2.1+设备端环境搭建_37be2cae.jpg
new file mode 100644
index 0000000..5883aeb
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_37be2cae.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_37f0f310.jpg b/images/4.2.1+设备端环境搭建_37f0f310.jpg
new file mode 100644
index 0000000..0a86490
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_37f0f310.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_387aa2ea.jpg b/images/4.2.1+设备端环境搭建_387aa2ea.jpg
new file mode 100644
index 0000000..0c2eee5
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_387aa2ea.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_3d029114.jpg b/images/4.2.1+设备端环境搭建_3d029114.jpg
new file mode 100644
index 0000000..e405626
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_3d029114.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_40c8edaf.jpg b/images/4.2.1+设备端环境搭建_40c8edaf.jpg
new file mode 100644
index 0000000..33029ae
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_40c8edaf.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_42fca78c.jpg b/images/4.2.1+设备端环境搭建_42fca78c.jpg
new file mode 100644
index 0000000..4f4a53b
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_42fca78c.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_43bfc7c9.jpg b/images/4.2.1+设备端环境搭建_43bfc7c9.jpg
new file mode 100644
index 0000000..0a86490
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_43bfc7c9.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_4f416667.jpg b/images/4.2.1+设备端环境搭建_4f416667.jpg
new file mode 100644
index 0000000..becf9c5
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_4f416667.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_51a0a676.jpg b/images/4.2.1+设备端环境搭建_51a0a676.jpg
new file mode 100644
index 0000000..553bbad
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_51a0a676.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_52d37364.jpg b/images/4.2.1+设备端环境搭建_52d37364.jpg
new file mode 100644
index 0000000..a046754
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_52d37364.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_53168a6d.jpg b/images/4.2.1+设备端环境搭建_53168a6d.jpg
new file mode 100644
index 0000000..db704d5
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_53168a6d.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_53927f63.jpg b/images/4.2.1+设备端环境搭建_53927f63.jpg
new file mode 100644
index 0000000..e5ad8ea
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_53927f63.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_54b68a32.jpg b/images/4.2.1+设备端环境搭建_54b68a32.jpg
new file mode 100644
index 0000000..013773f
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_54b68a32.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_54eb261f.jpg b/images/4.2.1+设备端环境搭建_54eb261f.jpg
new file mode 100644
index 0000000..db704d5
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_54eb261f.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_590ea6d6.jpg b/images/4.2.1+设备端环境搭建_590ea6d6.jpg
new file mode 100644
index 0000000..1144201
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_590ea6d6.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_59efe536.jpg b/images/4.2.1+设备端环境搭建_59efe536.jpg
new file mode 100644
index 0000000..54a3952
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_59efe536.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_5a2ce1eb.jpg b/images/4.2.1+设备端环境搭建_5a2ce1eb.jpg
new file mode 100644
index 0000000..f2be290
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_5a2ce1eb.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_5dacbbf4.jpg b/images/4.2.1+设备端环境搭建_5dacbbf4.jpg
new file mode 100644
index 0000000..4898332
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_5dacbbf4.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_64866d7c.jpg b/images/4.2.1+设备端环境搭建_64866d7c.jpg
new file mode 100644
index 0000000..f19a8ff
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_64866d7c.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_6525469f.jpg b/images/4.2.1+设备端环境搭建_6525469f.jpg
new file mode 100644
index 0000000..93b4195
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_6525469f.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_657171c9.jpg b/images/4.2.1+设备端环境搭建_657171c9.jpg
new file mode 100644
index 0000000..54a3952
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_657171c9.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_67e707a6.jpg b/images/4.2.1+设备端环境搭建_67e707a6.jpg
new file mode 100644
index 0000000..d2665a4
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_67e707a6.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_69767f92.jpg b/images/4.2.1+设备端环境搭建_69767f92.jpg
new file mode 100644
index 0000000..4de3342
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_69767f92.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_6e97d993.jpg b/images/4.2.1+设备端环境搭建_6e97d993.jpg
new file mode 100644
index 0000000..2eae932
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_6e97d993.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_73e7e943.jpg b/images/4.2.1+设备端环境搭建_73e7e943.jpg
new file mode 100644
index 0000000..5b771ea
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_73e7e943.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_75e25546.jpg b/images/4.2.1+设备端环境搭建_75e25546.jpg
new file mode 100644
index 0000000..44aa483
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_75e25546.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_76d42e18.jpg b/images/4.2.1+设备端环境搭建_76d42e18.jpg
new file mode 100644
index 0000000..72ad6b6
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_76d42e18.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_782bf5a8.jpg b/images/4.2.1+设备端环境搭建_782bf5a8.jpg
new file mode 100644
index 0000000..6259921
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_782bf5a8.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_7901d0db.jpg b/images/4.2.1+设备端环境搭建_7901d0db.jpg
new file mode 100644
index 0000000..f8b4d5a
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_7901d0db.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_7977904a.jpg b/images/4.2.1+设备端环境搭建_7977904a.jpg
new file mode 100644
index 0000000..5883aeb
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_7977904a.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_7c1d7150.jpg b/images/4.2.1+设备端环境搭建_7c1d7150.jpg
new file mode 100644
index 0000000..56c2ce9
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_7c1d7150.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_7d303d1e.jpg b/images/4.2.1+设备端环境搭建_7d303d1e.jpg
new file mode 100644
index 0000000..6c88cec
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_7d303d1e.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_7e46e028.jpg b/images/4.2.1+设备端环境搭建_7e46e028.jpg
new file mode 100644
index 0000000..f6db634
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_7e46e028.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_7fe3a961.jpg b/images/4.2.1+设备端环境搭建_7fe3a961.jpg
new file mode 100644
index 0000000..3c523d9
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_7fe3a961.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_85574a52.jpg b/images/4.2.1+设备端环境搭建_85574a52.jpg
new file mode 100644
index 0000000..f6db634
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_85574a52.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_869640cf.jpg b/images/4.2.1+设备端环境搭建_869640cf.jpg
new file mode 100644
index 0000000..f6d95c1
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_869640cf.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_869d0296.jpg b/images/4.2.1+设备端环境搭建_869d0296.jpg
new file mode 100644
index 0000000..e5ad8ea
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_869d0296.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_87769b03.jpg b/images/4.2.1+设备端环境搭建_87769b03.jpg
new file mode 100644
index 0000000..c6ad91f
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_87769b03.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_87ebb23b.jpg b/images/4.2.1+设备端环境搭建_87ebb23b.jpg
new file mode 100644
index 0000000..f19a8ff
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_87ebb23b.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_8ba3d886.jpg b/images/4.2.1+设备端环境搭建_8ba3d886.jpg
new file mode 100644
index 0000000..78e4e1a
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_8ba3d886.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_8cc24144.jpg b/images/4.2.1+设备端环境搭建_8cc24144.jpg
new file mode 100644
index 0000000..4de3342
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_8cc24144.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_8e2fc660.jpg b/images/4.2.1+设备端环境搭建_8e2fc660.jpg
new file mode 100644
index 0000000..c7c022b
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_8e2fc660.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_97943a0d.jpg b/images/4.2.1+设备端环境搭建_97943a0d.jpg
new file mode 100644
index 0000000..67278f1
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_97943a0d.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_9e5c67ee.jpg b/images/4.2.1+设备端环境搭建_9e5c67ee.jpg
new file mode 100644
index 0000000..f6d95c1
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_9e5c67ee.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_a10eab06.jpg b/images/4.2.1+设备端环境搭建_a10eab06.jpg
new file mode 100644
index 0000000..becf9c5
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_a10eab06.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_a13f6bf9.jpg b/images/4.2.1+设备端环境搭建_a13f6bf9.jpg
new file mode 100644
index 0000000..44aa483
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_a13f6bf9.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_a1b2f58b.jpg b/images/4.2.1+设备端环境搭建_a1b2f58b.jpg
new file mode 100644
index 0000000..c6ad91f
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_a1b2f58b.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_a2108a78.jpg b/images/4.2.1+设备端环境搭建_a2108a78.jpg
new file mode 100644
index 0000000..cb0b64a
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_a2108a78.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_a291bc2b.jpg b/images/4.2.1+设备端环境搭建_a291bc2b.jpg
new file mode 100644
index 0000000..33029ae
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_a291bc2b.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_b438b01d.jpg b/images/4.2.1+设备端环境搭建_b438b01d.jpg
new file mode 100644
index 0000000..f8b4d5a
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_b438b01d.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_b5ea6369.jpg b/images/4.2.1+设备端环境搭建_b5ea6369.jpg
new file mode 100644
index 0000000..fb2c74b
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_b5ea6369.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_b793f59a.jpg b/images/4.2.1+设备端环境搭建_b793f59a.jpg
new file mode 100644
index 0000000..4eb4b6e
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_b793f59a.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_bb6daf30.jpg b/images/4.2.1+设备端环境搭建_bb6daf30.jpg
new file mode 100644
index 0000000..d1c576d
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_bb6daf30.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_bc1bffaa.jpg b/images/4.2.1+设备端环境搭建_bc1bffaa.jpg
new file mode 100644
index 0000000..a046754
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_bc1bffaa.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_bc3b00b1.jpg b/images/4.2.1+设备端环境搭建_bc3b00b1.jpg
new file mode 100644
index 0000000..e405626
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_bc3b00b1.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_bc878acc.jpg b/images/4.2.1+设备端环境搭建_bc878acc.jpg
new file mode 100644
index 0000000..1699bb3
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_bc878acc.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_c1e6411a.jpg b/images/4.2.1+设备端环境搭建_c1e6411a.jpg
new file mode 100644
index 0000000..72ad6b6
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_c1e6411a.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_c235cac6.jpg b/images/4.2.1+设备端环境搭建_c235cac6.jpg
new file mode 100644
index 0000000..241e744
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_c235cac6.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_c26d7866.jpg b/images/4.2.1+设备端环境搭建_c26d7866.jpg
new file mode 100644
index 0000000..4f4a53b
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_c26d7866.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_c3a321fa.jpg b/images/4.2.1+设备端环境搭建_c3a321fa.jpg
new file mode 100644
index 0000000..1433f73
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_c3a321fa.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_c508659a.jpg b/images/4.2.1+设备端环境搭建_c508659a.jpg
new file mode 100644
index 0000000..1144201
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_c508659a.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_c62799ce.jpg b/images/4.2.1+设备端环境搭建_c62799ce.jpg
new file mode 100644
index 0000000..4898332
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_c62799ce.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_cdfc8f93.jpg b/images/4.2.1+设备端环境搭建_cdfc8f93.jpg
new file mode 100644
index 0000000..6259921
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_cdfc8f93.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_cf14d853.jpg b/images/4.2.1+设备端环境搭建_cf14d853.jpg
new file mode 100644
index 0000000..e5cd8dd
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_cf14d853.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_d5815baf.jpg b/images/4.2.1+设备端环境搭建_d5815baf.jpg
new file mode 100644
index 0000000..9af42b6
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_d5815baf.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_d66a2a36.jpg b/images/4.2.1+设备端环境搭建_d66a2a36.jpg
new file mode 100644
index 0000000..0d8f6c4
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_d66a2a36.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_d79f274b.jpg b/images/4.2.1+设备端环境搭建_d79f274b.jpg
new file mode 100644
index 0000000..0918a08
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_d79f274b.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_d7b10852.jpg b/images/4.2.1+设备端环境搭建_d7b10852.jpg
new file mode 100644
index 0000000..9af42b6
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_d7b10852.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_daa28fc5.jpg b/images/4.2.1+设备端环境搭建_daa28fc5.jpg
new file mode 100644
index 0000000..553bbad
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_daa28fc5.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_de3a321d.jpg b/images/4.2.1+设备端环境搭建_de3a321d.jpg
new file mode 100644
index 0000000..2eae932
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_de3a321d.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_e2a1ba95.jpg b/images/4.2.1+设备端环境搭建_e2a1ba95.jpg
new file mode 100644
index 0000000..c7c022b
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_e2a1ba95.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_e3d473fe.jpg b/images/4.2.1+设备端环境搭建_e3d473fe.jpg
new file mode 100644
index 0000000..6c88cec
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_e3d473fe.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_e9fe04a6.jpg b/images/4.2.1+设备端环境搭建_e9fe04a6.jpg
new file mode 100644
index 0000000..e5cd8dd
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_e9fe04a6.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_ece6749d.jpg b/images/4.2.1+设备端环境搭建_ece6749d.jpg
new file mode 100644
index 0000000..6b903d7
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_ece6749d.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_f1c0de5a.jpg b/images/4.2.1+设备端环境搭建_f1c0de5a.jpg
new file mode 100644
index 0000000..6b903d7
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_f1c0de5a.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_f4478dff.jpg b/images/4.2.1+设备端环境搭建_f4478dff.jpg
new file mode 100644
index 0000000..d4d7f50
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_f4478dff.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_f849766e.jpg b/images/4.2.1+设备端环境搭建_f849766e.jpg
new file mode 100644
index 0000000..93b4195
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_f849766e.jpg differ
diff --git a/images/4.2.1+设备端环境搭建_ff68cd25.jpg b/images/4.2.1+设备端环境搭建_ff68cd25.jpg
new file mode 100644
index 0000000..4eb4b6e
Binary files /dev/null and b/images/4.2.1+设备端环境搭建_ff68cd25.jpg differ
diff --git a/images/4.2.2+手机端环境搭建_02c946e1.jpg b/images/4.2.2+手机端环境搭建_02c946e1.jpg
new file mode 100644
index 0000000..15ae088
Binary files /dev/null and b/images/4.2.2+手机端环境搭建_02c946e1.jpg differ
diff --git a/images/4.2.2+手机端环境搭建_0488257e.jpg b/images/4.2.2+手机端环境搭建_0488257e.jpg
new file mode 100644
index 0000000..ee2114e
Binary files /dev/null and b/images/4.2.2+手机端环境搭建_0488257e.jpg differ
diff --git a/images/4.2.2+手机端环境搭建_0c6abb17.jpg b/images/4.2.2+手机端环境搭建_0c6abb17.jpg
new file mode 100644
index 0000000..891808f
Binary files /dev/null and b/images/4.2.2+手机端环境搭建_0c6abb17.jpg differ
diff --git a/images/4.2.2+手机端环境搭建_1ee89b5b.jpg b/images/4.2.2+手机端环境搭建_1ee89b5b.jpg
new file mode 100644
index 0000000..c0e85e0
Binary files /dev/null and b/images/4.2.2+手机端环境搭建_1ee89b5b.jpg differ
diff --git a/images/4.2.2+手机端环境搭建_25e0a93b.jpg b/images/4.2.2+手机端环境搭建_25e0a93b.jpg
new file mode 100644
index 0000000..3742274
Binary files /dev/null and b/images/4.2.2+手机端环境搭建_25e0a93b.jpg differ
diff --git a/images/4.2.2+手机端环境搭建_26e655a9.jpg b/images/4.2.2+手机端环境搭建_26e655a9.jpg
new file mode 100644
index 0000000..58e9b8b
Binary files /dev/null and b/images/4.2.2+手机端环境搭建_26e655a9.jpg differ
diff --git a/images/4.2.2+手机端环境搭建_2981727a.jpg b/images/4.2.2+手机端环境搭建_2981727a.jpg
new file mode 100644
index 0000000..b84908a
Binary files /dev/null and b/images/4.2.2+手机端环境搭建_2981727a.jpg differ
diff --git a/images/4.2.2+手机端环境搭建_2b2038b0.jpg b/images/4.2.2+手机端环境搭建_2b2038b0.jpg
new file mode 100644
index 0000000..c3def5e
Binary files /dev/null and b/images/4.2.2+手机端环境搭建_2b2038b0.jpg differ
diff --git a/images/4.2.2+手机端环境搭建_2ffa24cc.jpg b/images/4.2.2+手机端环境搭建_2ffa24cc.jpg
new file mode 100644
index 0000000..b447433
Binary files /dev/null and b/images/4.2.2+手机端环境搭建_2ffa24cc.jpg differ
diff --git a/images/4.2.2+手机端环境搭建_30bba787.jpg b/images/4.2.2+手机端环境搭建_30bba787.jpg
new file mode 100644
index 0000000..f8d9645
Binary files /dev/null and b/images/4.2.2+手机端环境搭建_30bba787.jpg differ
diff --git a/images/4.2.2+手机端环境搭建_3280f096.jpg b/images/4.2.2+手机端环境搭建_3280f096.jpg
new file mode 100644
index 0000000..832578b
Binary files /dev/null and b/images/4.2.2+手机端环境搭建_3280f096.jpg differ
diff --git a/images/4.2.2+手机端环境搭建_35335781.jpg b/images/4.2.2+手机端环境搭建_35335781.jpg
new file mode 100644
index 0000000..3f84e71
Binary files /dev/null and b/images/4.2.2+手机端环境搭建_35335781.jpg differ
diff --git a/images/4.2.2+手机端环境搭建_35d76b26.jpg b/images/4.2.2+手机端环境搭建_35d76b26.jpg
new file mode 100644
index 0000000..9fda635
Binary files /dev/null and b/images/4.2.2+手机端环境搭建_35d76b26.jpg differ
diff --git a/images/4.2.2+手机端环境搭建_3d237f57.jpg b/images/4.2.2+手机端环境搭建_3d237f57.jpg
new file mode 100644
index 0000000..9ed6549
Binary files /dev/null and b/images/4.2.2+手机端环境搭建_3d237f57.jpg differ
diff --git a/images/4.2.2+手机端环境搭建_40a53d1a.jpg b/images/4.2.2+手机端环境搭建_40a53d1a.jpg
new file mode 100644
index 0000000..2a1ff26
Binary files /dev/null and b/images/4.2.2+手机端环境搭建_40a53d1a.jpg differ
diff --git a/images/4.2.2+手机端环境搭建_46b6acd5.jpg b/images/4.2.2+手机端环境搭建_46b6acd5.jpg
new file mode 100644
index 0000000..832578b
Binary files /dev/null and b/images/4.2.2+手机端环境搭建_46b6acd5.jpg differ
diff --git a/images/4.2.2+手机端环境搭建_4c2832ba.jpg b/images/4.2.2+手机端环境搭建_4c2832ba.jpg
new file mode 100644
index 0000000..2b46edf
Binary files /dev/null and b/images/4.2.2+手机端环境搭建_4c2832ba.jpg differ
diff --git a/images/4.2.2+手机端环境搭建_4de33e4e.jpg b/images/4.2.2+手机端环境搭建_4de33e4e.jpg
new file mode 100644
index 0000000..c0e85e0
Binary files /dev/null and b/images/4.2.2+手机端环境搭建_4de33e4e.jpg differ
diff --git a/images/4.2.2+手机端环境搭建_5a16c59e.jpg b/images/4.2.2+手机端环境搭建_5a16c59e.jpg
new file mode 100644
index 0000000..e2e2b1c
Binary files /dev/null and b/images/4.2.2+手机端环境搭建_5a16c59e.jpg differ
diff --git a/images/4.2.2+手机端环境搭建_5f598543.jpg b/images/4.2.2+手机端环境搭建_5f598543.jpg
new file mode 100644
index 0000000..9ed6549
Binary files /dev/null and b/images/4.2.2+手机端环境搭建_5f598543.jpg differ
diff --git a/images/4.2.2+手机端环境搭建_5fbe2fcf.jpg b/images/4.2.2+手机端环境搭建_5fbe2fcf.jpg
new file mode 100644
index 0000000..77a8e3f
Binary files /dev/null and b/images/4.2.2+手机端环境搭建_5fbe2fcf.jpg differ
diff --git a/images/4.2.2+手机端环境搭建_61116bea.jpg b/images/4.2.2+手机端环境搭建_61116bea.jpg
new file mode 100644
index 0000000..9fda635
Binary files /dev/null and b/images/4.2.2+手机端环境搭建_61116bea.jpg differ
diff --git a/images/4.2.2+手机端环境搭建_611a1310.jpg b/images/4.2.2+手机端环境搭建_611a1310.jpg
new file mode 100644
index 0000000..1dda003
Binary files /dev/null and b/images/4.2.2+手机端环境搭建_611a1310.jpg differ
diff --git a/images/4.2.2+手机端环境搭建_644d1f4f.jpg b/images/4.2.2+手机端环境搭建_644d1f4f.jpg
new file mode 100644
index 0000000..302ade0
Binary files /dev/null and b/images/4.2.2+手机端环境搭建_644d1f4f.jpg differ
diff --git a/images/4.2.2+手机端环境搭建_64f86642.jpg b/images/4.2.2+手机端环境搭建_64f86642.jpg
new file mode 100644
index 0000000..58e9b8b
Binary files /dev/null and b/images/4.2.2+手机端环境搭建_64f86642.jpg differ
diff --git a/images/4.2.2+手机端环境搭建_6a4a38d2.jpg b/images/4.2.2+手机端环境搭建_6a4a38d2.jpg
new file mode 100644
index 0000000..fcb7f36
Binary files /dev/null and b/images/4.2.2+手机端环境搭建_6a4a38d2.jpg differ
diff --git a/images/4.2.2+手机端环境搭建_6d9aacfd.jpg b/images/4.2.2+手机端环境搭建_6d9aacfd.jpg
new file mode 100644
index 0000000..1408b2d
Binary files /dev/null and b/images/4.2.2+手机端环境搭建_6d9aacfd.jpg differ
diff --git a/images/4.2.2+手机端环境搭建_7081727d.jpg b/images/4.2.2+手机端环境搭建_7081727d.jpg
new file mode 100644
index 0000000..631b957
Binary files /dev/null and b/images/4.2.2+手机端环境搭建_7081727d.jpg differ
diff --git a/images/4.2.2+手机端环境搭建_75a42d33.jpg b/images/4.2.2+手机端环境搭建_75a42d33.jpg
new file mode 100644
index 0000000..4c1855f
Binary files /dev/null and b/images/4.2.2+手机端环境搭建_75a42d33.jpg differ
diff --git a/images/4.2.2+手机端环境搭建_7c5780dd.jpg b/images/4.2.2+手机端环境搭建_7c5780dd.jpg
new file mode 100644
index 0000000..de363b1
Binary files /dev/null and b/images/4.2.2+手机端环境搭建_7c5780dd.jpg differ
diff --git a/images/4.2.2+手机端环境搭建_7d067d5c.jpg b/images/4.2.2+手机端环境搭建_7d067d5c.jpg
new file mode 100644
index 0000000..b447433
Binary files /dev/null and b/images/4.2.2+手机端环境搭建_7d067d5c.jpg differ
diff --git a/images/4.2.2+手机端环境搭建_81d4d107.jpg b/images/4.2.2+手机端环境搭建_81d4d107.jpg
new file mode 100644
index 0000000..a4ce3bd
Binary files /dev/null and b/images/4.2.2+手机端环境搭建_81d4d107.jpg differ
diff --git a/images/4.2.2+手机端环境搭建_82b573c8.jpg b/images/4.2.2+手机端环境搭建_82b573c8.jpg
new file mode 100644
index 0000000..631b957
Binary files /dev/null and b/images/4.2.2+手机端环境搭建_82b573c8.jpg differ
diff --git a/images/4.2.2+手机端环境搭建_8622bde7.jpg b/images/4.2.2+手机端环境搭建_8622bde7.jpg
new file mode 100644
index 0000000..a4ce3bd
Binary files /dev/null and b/images/4.2.2+手机端环境搭建_8622bde7.jpg differ
diff --git a/images/4.2.2+手机端环境搭建_87327ea2.jpg b/images/4.2.2+手机端环境搭建_87327ea2.jpg
new file mode 100644
index 0000000..891808f
Binary files /dev/null and b/images/4.2.2+手机端环境搭建_87327ea2.jpg differ
diff --git a/images/4.2.2+手机端环境搭建_98c29050.jpg b/images/4.2.2+手机端环境搭建_98c29050.jpg
new file mode 100644
index 0000000..2a1ff26
Binary files /dev/null and b/images/4.2.2+手机端环境搭建_98c29050.jpg differ
diff --git a/images/4.2.2+手机端环境搭建_9bcaeedd.jpg b/images/4.2.2+手机端环境搭建_9bcaeedd.jpg
new file mode 100644
index 0000000..facfdbb
Binary files /dev/null and b/images/4.2.2+手机端环境搭建_9bcaeedd.jpg differ
diff --git a/images/4.2.2+手机端环境搭建_a5d9b075.jpg b/images/4.2.2+手机端环境搭建_a5d9b075.jpg
new file mode 100644
index 0000000..3f84e71
Binary files /dev/null and b/images/4.2.2+手机端环境搭建_a5d9b075.jpg differ
diff --git a/images/4.2.2+手机端环境搭建_ab20463d.jpg b/images/4.2.2+手机端环境搭建_ab20463d.jpg
new file mode 100644
index 0000000..b7ce1dd
Binary files /dev/null and b/images/4.2.2+手机端环境搭建_ab20463d.jpg differ
diff --git a/images/4.2.2+手机端环境搭建_ab694f87.jpg b/images/4.2.2+手机端环境搭建_ab694f87.jpg
new file mode 100644
index 0000000..15ae088
Binary files /dev/null and b/images/4.2.2+手机端环境搭建_ab694f87.jpg differ
diff --git a/images/4.2.2+手机端环境搭建_ace5d278.jpg b/images/4.2.2+手机端环境搭建_ace5d278.jpg
new file mode 100644
index 0000000..e2e2b1c
Binary files /dev/null and b/images/4.2.2+手机端环境搭建_ace5d278.jpg differ
diff --git a/images/4.2.2+手机端环境搭建_b127bf6c.jpg b/images/4.2.2+手机端环境搭建_b127bf6c.jpg
new file mode 100644
index 0000000..6d2af57
Binary files /dev/null and b/images/4.2.2+手机端环境搭建_b127bf6c.jpg differ
diff --git a/images/4.2.2+手机端环境搭建_b32bbeba.jpg b/images/4.2.2+手机端环境搭建_b32bbeba.jpg
new file mode 100644
index 0000000..3742274
Binary files /dev/null and b/images/4.2.2+手机端环境搭建_b32bbeba.jpg differ
diff --git a/images/4.2.2+手机端环境搭建_b35d4a33.jpg b/images/4.2.2+手机端环境搭建_b35d4a33.jpg
new file mode 100644
index 0000000..4c1855f
Binary files /dev/null and b/images/4.2.2+手机端环境搭建_b35d4a33.jpg differ
diff --git a/images/4.2.2+手机端环境搭建_b72159d4.jpg b/images/4.2.2+手机端环境搭建_b72159d4.jpg
new file mode 100644
index 0000000..64d2e42
Binary files /dev/null and b/images/4.2.2+手机端环境搭建_b72159d4.jpg differ
diff --git a/images/4.2.2+手机端环境搭建_ba72e724.jpg b/images/4.2.2+手机端环境搭建_ba72e724.jpg
new file mode 100644
index 0000000..77a8e3f
Binary files /dev/null and b/images/4.2.2+手机端环境搭建_ba72e724.jpg differ
diff --git a/images/4.2.2+手机端环境搭建_bd513952.jpg b/images/4.2.2+手机端环境搭建_bd513952.jpg
new file mode 100644
index 0000000..6d2af57
Binary files /dev/null and b/images/4.2.2+手机端环境搭建_bd513952.jpg differ
diff --git a/images/4.2.2+手机端环境搭建_c40bab0a.jpg b/images/4.2.2+手机端环境搭建_c40bab0a.jpg
new file mode 100644
index 0000000..2b46edf
Binary files /dev/null and b/images/4.2.2+手机端环境搭建_c40bab0a.jpg differ
diff --git a/images/4.2.2+手机端环境搭建_c705b2e6.jpg b/images/4.2.2+手机端环境搭建_c705b2e6.jpg
new file mode 100644
index 0000000..5daf99d
Binary files /dev/null and b/images/4.2.2+手机端环境搭建_c705b2e6.jpg differ
diff --git a/images/4.2.2+手机端环境搭建_cc839c24.jpg b/images/4.2.2+手机端环境搭建_cc839c24.jpg
new file mode 100644
index 0000000..c3def5e
Binary files /dev/null and b/images/4.2.2+手机端环境搭建_cc839c24.jpg differ
diff --git a/images/4.2.2+手机端环境搭建_cd9f1479.jpg b/images/4.2.2+手机端环境搭建_cd9f1479.jpg
new file mode 100644
index 0000000..b7ce1dd
Binary files /dev/null and b/images/4.2.2+手机端环境搭建_cd9f1479.jpg differ
diff --git a/images/4.2.2+手机端环境搭建_d26bf10f.jpg b/images/4.2.2+手机端环境搭建_d26bf10f.jpg
new file mode 100644
index 0000000..b84908a
Binary files /dev/null and b/images/4.2.2+手机端环境搭建_d26bf10f.jpg differ
diff --git a/images/4.2.2+手机端环境搭建_d572f1b8.jpg b/images/4.2.2+手机端环境搭建_d572f1b8.jpg
new file mode 100644
index 0000000..302ade0
Binary files /dev/null and b/images/4.2.2+手机端环境搭建_d572f1b8.jpg differ
diff --git a/images/4.2.2+手机端环境搭建_d78d647b.jpg b/images/4.2.2+手机端环境搭建_d78d647b.jpg
new file mode 100644
index 0000000..5daf99d
Binary files /dev/null and b/images/4.2.2+手机端环境搭建_d78d647b.jpg differ
diff --git a/images/4.2.2+手机端环境搭建_de0c0601.jpg b/images/4.2.2+手机端环境搭建_de0c0601.jpg
new file mode 100644
index 0000000..1dda003
Binary files /dev/null and b/images/4.2.2+手机端环境搭建_de0c0601.jpg differ
diff --git a/images/4.2.2+手机端环境搭建_e23e8747.jpg b/images/4.2.2+手机端环境搭建_e23e8747.jpg
new file mode 100644
index 0000000..e93fb27
Binary files /dev/null and b/images/4.2.2+手机端环境搭建_e23e8747.jpg differ
diff --git a/images/4.2.2+手机端环境搭建_e290372c.jpg b/images/4.2.2+手机端环境搭建_e290372c.jpg
new file mode 100644
index 0000000..f8d9645
Binary files /dev/null and b/images/4.2.2+手机端环境搭建_e290372c.jpg differ
diff --git a/images/4.2.2+手机端环境搭建_e3ad5de3.jpg b/images/4.2.2+手机端环境搭建_e3ad5de3.jpg
new file mode 100644
index 0000000..1408b2d
Binary files /dev/null and b/images/4.2.2+手机端环境搭建_e3ad5de3.jpg differ
diff --git a/images/4.2.2+手机端环境搭建_ea431ad9.jpg b/images/4.2.2+手机端环境搭建_ea431ad9.jpg
new file mode 100644
index 0000000..64d2e42
Binary files /dev/null and b/images/4.2.2+手机端环境搭建_ea431ad9.jpg differ
diff --git a/images/4.2.2+手机端环境搭建_eeca0be0.jpg b/images/4.2.2+手机端环境搭建_eeca0be0.jpg
new file mode 100644
index 0000000..fcb7f36
Binary files /dev/null and b/images/4.2.2+手机端环境搭建_eeca0be0.jpg differ
diff --git a/images/4.2.2+手机端环境搭建_f2e6a7d6.jpg b/images/4.2.2+手机端环境搭建_f2e6a7d6.jpg
new file mode 100644
index 0000000..de363b1
Binary files /dev/null and b/images/4.2.2+手机端环境搭建_f2e6a7d6.jpg differ
diff --git a/images/4.2.2+手机端环境搭建_f3063df3.jpg b/images/4.2.2+手机端环境搭建_f3063df3.jpg
new file mode 100644
index 0000000..e93fb27
Binary files /dev/null and b/images/4.2.2+手机端环境搭建_f3063df3.jpg differ
diff --git a/images/4.2.2+手机端环境搭建_f3fe6db3.jpg b/images/4.2.2+手机端环境搭建_f3fe6db3.jpg
new file mode 100644
index 0000000..facfdbb
Binary files /dev/null and b/images/4.2.2+手机端环境搭建_f3fe6db3.jpg differ
diff --git a/images/4.2.2+手机端环境搭建_f7387c13.jpg b/images/4.2.2+手机端环境搭建_f7387c13.jpg
new file mode 100644
index 0000000..ee2114e
Binary files /dev/null and b/images/4.2.2+手机端环境搭建_f7387c13.jpg differ
diff --git a/images/4.2.3+Fast+Pair+Validator+环境搭建_037127e1.jpg b/images/4.2.3+Fast+Pair+Validator+环境搭建_037127e1.jpg
new file mode 100644
index 0000000..7dcfef7
Binary files /dev/null and b/images/4.2.3+Fast+Pair+Validator+环境搭建_037127e1.jpg differ
diff --git a/images/4.2.3+Fast+Pair+Validator+环境搭建_14e96842.jpg b/images/4.2.3+Fast+Pair+Validator+环境搭建_14e96842.jpg
new file mode 100644
index 0000000..b84908a
Binary files /dev/null and b/images/4.2.3+Fast+Pair+Validator+环境搭建_14e96842.jpg differ
diff --git a/images/4.2.3+Fast+Pair+Validator+环境搭建_17982628.jpg b/images/4.2.3+Fast+Pair+Validator+环境搭建_17982628.jpg
new file mode 100644
index 0000000..53ef204
Binary files /dev/null and b/images/4.2.3+Fast+Pair+Validator+环境搭建_17982628.jpg differ
diff --git a/images/4.2.3+Fast+Pair+Validator+环境搭建_1d91cad7.jpg b/images/4.2.3+Fast+Pair+Validator+环境搭建_1d91cad7.jpg
new file mode 100644
index 0000000..6a7bd33
Binary files /dev/null and b/images/4.2.3+Fast+Pair+Validator+环境搭建_1d91cad7.jpg differ
diff --git a/images/4.2.3+Fast+Pair+Validator+环境搭建_21aea051.jpg b/images/4.2.3+Fast+Pair+Validator+环境搭建_21aea051.jpg
new file mode 100644
index 0000000..6ec45ec
Binary files /dev/null and b/images/4.2.3+Fast+Pair+Validator+环境搭建_21aea051.jpg differ
diff --git a/images/4.2.3+Fast+Pair+Validator+环境搭建_21f58979.jpg b/images/4.2.3+Fast+Pair+Validator+环境搭建_21f58979.jpg
new file mode 100644
index 0000000..c0e85e0
Binary files /dev/null and b/images/4.2.3+Fast+Pair+Validator+环境搭建_21f58979.jpg differ
diff --git a/images/4.2.3+Fast+Pair+Validator+环境搭建_2263b15e.jpg b/images/4.2.3+Fast+Pair+Validator+环境搭建_2263b15e.jpg
new file mode 100644
index 0000000..58e9b8b
Binary files /dev/null and b/images/4.2.3+Fast+Pair+Validator+环境搭建_2263b15e.jpg differ
diff --git a/images/4.2.3+Fast+Pair+Validator+环境搭建_2e85f892.jpg b/images/4.2.3+Fast+Pair+Validator+环境搭建_2e85f892.jpg
new file mode 100644
index 0000000..facfdbb
Binary files /dev/null and b/images/4.2.3+Fast+Pair+Validator+环境搭建_2e85f892.jpg differ
diff --git a/images/4.2.3+Fast+Pair+Validator+环境搭建_2f6353ca.jpg b/images/4.2.3+Fast+Pair+Validator+环境搭建_2f6353ca.jpg
new file mode 100644
index 0000000..631b957
Binary files /dev/null and b/images/4.2.3+Fast+Pair+Validator+环境搭建_2f6353ca.jpg differ
diff --git a/images/4.2.3+Fast+Pair+Validator+环境搭建_35b9446e.jpg b/images/4.2.3+Fast+Pair+Validator+环境搭建_35b9446e.jpg
new file mode 100644
index 0000000..6d2af57
Binary files /dev/null and b/images/4.2.3+Fast+Pair+Validator+环境搭建_35b9446e.jpg differ
diff --git a/images/4.2.3+Fast+Pair+Validator+环境搭建_44dfb017.jpg b/images/4.2.3+Fast+Pair+Validator+环境搭建_44dfb017.jpg
new file mode 100644
index 0000000..b4477df
Binary files /dev/null and b/images/4.2.3+Fast+Pair+Validator+环境搭建_44dfb017.jpg differ
diff --git a/images/4.2.3+Fast+Pair+Validator+环境搭建_45eea884.jpg b/images/4.2.3+Fast+Pair+Validator+环境搭建_45eea884.jpg
new file mode 100644
index 0000000..631b957
Binary files /dev/null and b/images/4.2.3+Fast+Pair+Validator+环境搭建_45eea884.jpg differ
diff --git a/images/4.2.3+Fast+Pair+Validator+环境搭建_4982a305.jpg b/images/4.2.3+Fast+Pair+Validator+环境搭建_4982a305.jpg
new file mode 100644
index 0000000..2a1ff26
Binary files /dev/null and b/images/4.2.3+Fast+Pair+Validator+环境搭建_4982a305.jpg differ
diff --git a/images/4.2.3+Fast+Pair+Validator+环境搭建_4a8724d6.jpg b/images/4.2.3+Fast+Pair+Validator+环境搭建_4a8724d6.jpg
new file mode 100644
index 0000000..b4477df
Binary files /dev/null and b/images/4.2.3+Fast+Pair+Validator+环境搭建_4a8724d6.jpg differ
diff --git a/images/4.2.3+Fast+Pair+Validator+环境搭建_4babbf8e.jpg b/images/4.2.3+Fast+Pair+Validator+环境搭建_4babbf8e.jpg
new file mode 100644
index 0000000..b84908a
Binary files /dev/null and b/images/4.2.3+Fast+Pair+Validator+环境搭建_4babbf8e.jpg differ
diff --git a/images/4.2.3+Fast+Pair+Validator+环境搭建_4f5bcdba.jpg b/images/4.2.3+Fast+Pair+Validator+环境搭建_4f5bcdba.jpg
new file mode 100644
index 0000000..53ef204
Binary files /dev/null and b/images/4.2.3+Fast+Pair+Validator+环境搭建_4f5bcdba.jpg differ
diff --git a/images/4.2.3+Fast+Pair+Validator+环境搭建_5d8d04b3.jpg b/images/4.2.3+Fast+Pair+Validator+环境搭建_5d8d04b3.jpg
new file mode 100644
index 0000000..58e9b8b
Binary files /dev/null and b/images/4.2.3+Fast+Pair+Validator+环境搭建_5d8d04b3.jpg differ
diff --git a/images/4.2.3+Fast+Pair+Validator+环境搭建_60db85d7.jpg b/images/4.2.3+Fast+Pair+Validator+环境搭建_60db85d7.jpg
new file mode 100644
index 0000000..503cb7d
Binary files /dev/null and b/images/4.2.3+Fast+Pair+Validator+环境搭建_60db85d7.jpg differ
diff --git a/images/4.2.3+Fast+Pair+Validator+环境搭建_6b0cae18.jpg b/images/4.2.3+Fast+Pair+Validator+环境搭建_6b0cae18.jpg
new file mode 100644
index 0000000..3f84e71
Binary files /dev/null and b/images/4.2.3+Fast+Pair+Validator+环境搭建_6b0cae18.jpg differ
diff --git a/images/4.2.3+Fast+Pair+Validator+环境搭建_6e08e767.jpg b/images/4.2.3+Fast+Pair+Validator+环境搭建_6e08e767.jpg
new file mode 100644
index 0000000..a80fc45
Binary files /dev/null and b/images/4.2.3+Fast+Pair+Validator+环境搭建_6e08e767.jpg differ
diff --git a/images/4.2.3+Fast+Pair+Validator+环境搭建_725e819f.jpg b/images/4.2.3+Fast+Pair+Validator+环境搭建_725e819f.jpg
new file mode 100644
index 0000000..15ae088
Binary files /dev/null and b/images/4.2.3+Fast+Pair+Validator+环境搭建_725e819f.jpg differ
diff --git a/images/4.2.3+Fast+Pair+Validator+环境搭建_7bacc95c.jpg b/images/4.2.3+Fast+Pair+Validator+环境搭建_7bacc95c.jpg
new file mode 100644
index 0000000..503cb7d
Binary files /dev/null and b/images/4.2.3+Fast+Pair+Validator+环境搭建_7bacc95c.jpg differ
diff --git a/images/4.2.3+Fast+Pair+Validator+环境搭建_7f064df0.jpg b/images/4.2.3+Fast+Pair+Validator+环境搭建_7f064df0.jpg
new file mode 100644
index 0000000..b447433
Binary files /dev/null and b/images/4.2.3+Fast+Pair+Validator+环境搭建_7f064df0.jpg differ
diff --git a/images/4.2.3+Fast+Pair+Validator+环境搭建_7f28a039.jpg b/images/4.2.3+Fast+Pair+Validator+环境搭建_7f28a039.jpg
new file mode 100644
index 0000000..ab658c5
Binary files /dev/null and b/images/4.2.3+Fast+Pair+Validator+环境搭建_7f28a039.jpg differ
diff --git a/images/4.2.3+Fast+Pair+Validator+环境搭建_816a3677.jpg b/images/4.2.3+Fast+Pair+Validator+环境搭建_816a3677.jpg
new file mode 100644
index 0000000..302ade0
Binary files /dev/null and b/images/4.2.3+Fast+Pair+Validator+环境搭建_816a3677.jpg differ
diff --git a/images/4.2.3+Fast+Pair+Validator+环境搭建_8843efa0.jpg b/images/4.2.3+Fast+Pair+Validator+环境搭建_8843efa0.jpg
new file mode 100644
index 0000000..4c1855f
Binary files /dev/null and b/images/4.2.3+Fast+Pair+Validator+环境搭建_8843efa0.jpg differ
diff --git a/images/4.2.3+Fast+Pair+Validator+环境搭建_89cdc350.jpg b/images/4.2.3+Fast+Pair+Validator+环境搭建_89cdc350.jpg
new file mode 100644
index 0000000..c5bbb74
Binary files /dev/null and b/images/4.2.3+Fast+Pair+Validator+环境搭建_89cdc350.jpg differ
diff --git a/images/4.2.3+Fast+Pair+Validator+环境搭建_8a5bb06c.jpg b/images/4.2.3+Fast+Pair+Validator+环境搭建_8a5bb06c.jpg
new file mode 100644
index 0000000..1dda003
Binary files /dev/null and b/images/4.2.3+Fast+Pair+Validator+环境搭建_8a5bb06c.jpg differ
diff --git a/images/4.2.3+Fast+Pair+Validator+环境搭建_8b5a5d26.jpg b/images/4.2.3+Fast+Pair+Validator+环境搭建_8b5a5d26.jpg
new file mode 100644
index 0000000..1af0580
Binary files /dev/null and b/images/4.2.3+Fast+Pair+Validator+环境搭建_8b5a5d26.jpg differ
diff --git a/images/4.2.3+Fast+Pair+Validator+环境搭建_8fa475b5.jpg b/images/4.2.3+Fast+Pair+Validator+环境搭建_8fa475b5.jpg
new file mode 100644
index 0000000..6d2af57
Binary files /dev/null and b/images/4.2.3+Fast+Pair+Validator+环境搭建_8fa475b5.jpg differ
diff --git a/images/4.2.3+Fast+Pair+Validator+环境搭建_909113c4.jpg b/images/4.2.3+Fast+Pair+Validator+环境搭建_909113c4.jpg
new file mode 100644
index 0000000..2b46edf
Binary files /dev/null and b/images/4.2.3+Fast+Pair+Validator+环境搭建_909113c4.jpg differ
diff --git a/images/4.2.3+Fast+Pair+Validator+环境搭建_90d692a5.jpg b/images/4.2.3+Fast+Pair+Validator+环境搭建_90d692a5.jpg
new file mode 100644
index 0000000..2a1ff26
Binary files /dev/null and b/images/4.2.3+Fast+Pair+Validator+环境搭建_90d692a5.jpg differ
diff --git a/images/4.2.3+Fast+Pair+Validator+环境搭建_914d87ad.jpg b/images/4.2.3+Fast+Pair+Validator+环境搭建_914d87ad.jpg
new file mode 100644
index 0000000..3f84e71
Binary files /dev/null and b/images/4.2.3+Fast+Pair+Validator+环境搭建_914d87ad.jpg differ
diff --git a/images/4.2.3+Fast+Pair+Validator+环境搭建_91e948eb.jpg b/images/4.2.3+Fast+Pair+Validator+环境搭建_91e948eb.jpg
new file mode 100644
index 0000000..a80fc45
Binary files /dev/null and b/images/4.2.3+Fast+Pair+Validator+环境搭建_91e948eb.jpg differ
diff --git a/images/4.2.3+Fast+Pair+Validator+环境搭建_9ac5ed4b.jpg b/images/4.2.3+Fast+Pair+Validator+环境搭建_9ac5ed4b.jpg
new file mode 100644
index 0000000..2b46edf
Binary files /dev/null and b/images/4.2.3+Fast+Pair+Validator+环境搭建_9ac5ed4b.jpg differ
diff --git a/images/4.2.3+Fast+Pair+Validator+环境搭建_a0c9f2dd.jpg b/images/4.2.3+Fast+Pair+Validator+环境搭建_a0c9f2dd.jpg
new file mode 100644
index 0000000..1af0580
Binary files /dev/null and b/images/4.2.3+Fast+Pair+Validator+环境搭建_a0c9f2dd.jpg differ
diff --git a/images/4.2.3+Fast+Pair+Validator+环境搭建_a24bd470.jpg b/images/4.2.3+Fast+Pair+Validator+环境搭建_a24bd470.jpg
new file mode 100644
index 0000000..302ade0
Binary files /dev/null and b/images/4.2.3+Fast+Pair+Validator+环境搭建_a24bd470.jpg differ
diff --git a/images/4.2.3+Fast+Pair+Validator+环境搭建_a9bc80f9.jpg b/images/4.2.3+Fast+Pair+Validator+环境搭建_a9bc80f9.jpg
new file mode 100644
index 0000000..64d2e42
Binary files /dev/null and b/images/4.2.3+Fast+Pair+Validator+环境搭建_a9bc80f9.jpg differ
diff --git a/images/4.2.3+Fast+Pair+Validator+环境搭建_abd70774.jpg b/images/4.2.3+Fast+Pair+Validator+环境搭建_abd70774.jpg
new file mode 100644
index 0000000..64d2e42
Binary files /dev/null and b/images/4.2.3+Fast+Pair+Validator+环境搭建_abd70774.jpg differ
diff --git a/images/4.2.3+Fast+Pair+Validator+环境搭建_b2202b09.jpg b/images/4.2.3+Fast+Pair+Validator+环境搭建_b2202b09.jpg
new file mode 100644
index 0000000..c3def5e
Binary files /dev/null and b/images/4.2.3+Fast+Pair+Validator+环境搭建_b2202b09.jpg differ
diff --git a/images/4.2.3+Fast+Pair+Validator+环境搭建_b3609ea1.jpg b/images/4.2.3+Fast+Pair+Validator+环境搭建_b3609ea1.jpg
new file mode 100644
index 0000000..9ed6549
Binary files /dev/null and b/images/4.2.3+Fast+Pair+Validator+环境搭建_b3609ea1.jpg differ
diff --git a/images/4.2.3+Fast+Pair+Validator+环境搭建_b7a2d031.jpg b/images/4.2.3+Fast+Pair+Validator+环境搭建_b7a2d031.jpg
new file mode 100644
index 0000000..9ed6549
Binary files /dev/null and b/images/4.2.3+Fast+Pair+Validator+环境搭建_b7a2d031.jpg differ
diff --git a/images/4.2.3+Fast+Pair+Validator+环境搭建_b9f8402b.jpg b/images/4.2.3+Fast+Pair+Validator+环境搭建_b9f8402b.jpg
new file mode 100644
index 0000000..facfdbb
Binary files /dev/null and b/images/4.2.3+Fast+Pair+Validator+环境搭建_b9f8402b.jpg differ
diff --git a/images/4.2.3+Fast+Pair+Validator+环境搭建_bf169c25.jpg b/images/4.2.3+Fast+Pair+Validator+环境搭建_bf169c25.jpg
new file mode 100644
index 0000000..c7ccda3
Binary files /dev/null and b/images/4.2.3+Fast+Pair+Validator+环境搭建_bf169c25.jpg differ
diff --git a/images/4.2.3+Fast+Pair+Validator+环境搭建_c07117dd.jpg b/images/4.2.3+Fast+Pair+Validator+环境搭建_c07117dd.jpg
new file mode 100644
index 0000000..071d3f9
Binary files /dev/null and b/images/4.2.3+Fast+Pair+Validator+环境搭建_c07117dd.jpg differ
diff --git a/images/4.2.3+Fast+Pair+Validator+环境搭建_c21fc823.jpg b/images/4.2.3+Fast+Pair+Validator+环境搭建_c21fc823.jpg
new file mode 100644
index 0000000..071d3f9
Binary files /dev/null and b/images/4.2.3+Fast+Pair+Validator+环境搭建_c21fc823.jpg differ
diff --git a/images/4.2.3+Fast+Pair+Validator+环境搭建_c2e1593a.jpg b/images/4.2.3+Fast+Pair+Validator+环境搭建_c2e1593a.jpg
new file mode 100644
index 0000000..6ec45ec
Binary files /dev/null and b/images/4.2.3+Fast+Pair+Validator+环境搭建_c2e1593a.jpg differ
diff --git a/images/4.2.3+Fast+Pair+Validator+环境搭建_c55b6d92.jpg b/images/4.2.3+Fast+Pair+Validator+环境搭建_c55b6d92.jpg
new file mode 100644
index 0000000..c3def5e
Binary files /dev/null and b/images/4.2.3+Fast+Pair+Validator+环境搭建_c55b6d92.jpg differ
diff --git a/images/4.2.3+Fast+Pair+Validator+环境搭建_c6672f82.jpg b/images/4.2.3+Fast+Pair+Validator+环境搭建_c6672f82.jpg
new file mode 100644
index 0000000..b7ce1dd
Binary files /dev/null and b/images/4.2.3+Fast+Pair+Validator+环境搭建_c6672f82.jpg differ
diff --git a/images/4.2.3+Fast+Pair+Validator+环境搭建_c7f9e394.jpg b/images/4.2.3+Fast+Pair+Validator+环境搭建_c7f9e394.jpg
new file mode 100644
index 0000000..15ae088
Binary files /dev/null and b/images/4.2.3+Fast+Pair+Validator+环境搭建_c7f9e394.jpg differ
diff --git a/images/4.2.3+Fast+Pair+Validator+环境搭建_cba26c37.jpg b/images/4.2.3+Fast+Pair+Validator+环境搭建_cba26c37.jpg
new file mode 100644
index 0000000..c0e85e0
Binary files /dev/null and b/images/4.2.3+Fast+Pair+Validator+环境搭建_cba26c37.jpg differ
diff --git a/images/4.2.3+Fast+Pair+Validator+环境搭建_d547c0b7.jpg b/images/4.2.3+Fast+Pair+Validator+环境搭建_d547c0b7.jpg
new file mode 100644
index 0000000..b7ce1dd
Binary files /dev/null and b/images/4.2.3+Fast+Pair+Validator+环境搭建_d547c0b7.jpg differ
diff --git a/images/4.2.3+Fast+Pair+Validator+环境搭建_d8670ff1.jpg b/images/4.2.3+Fast+Pair+Validator+环境搭建_d8670ff1.jpg
new file mode 100644
index 0000000..7dcfef7
Binary files /dev/null and b/images/4.2.3+Fast+Pair+Validator+环境搭建_d8670ff1.jpg differ
diff --git a/images/4.2.3+Fast+Pair+Validator+环境搭建_e97cc025.jpg b/images/4.2.3+Fast+Pair+Validator+环境搭建_e97cc025.jpg
new file mode 100644
index 0000000..1dda003
Binary files /dev/null and b/images/4.2.3+Fast+Pair+Validator+环境搭建_e97cc025.jpg differ
diff --git a/images/4.2.3+Fast+Pair+Validator+环境搭建_f17e2efd.jpg b/images/4.2.3+Fast+Pair+Validator+环境搭建_f17e2efd.jpg
new file mode 100644
index 0000000..6a7bd33
Binary files /dev/null and b/images/4.2.3+Fast+Pair+Validator+环境搭建_f17e2efd.jpg differ
diff --git a/images/4.2.3+Fast+Pair+Validator+环境搭建_f223efd9.jpg b/images/4.2.3+Fast+Pair+Validator+环境搭建_f223efd9.jpg
new file mode 100644
index 0000000..4c1855f
Binary files /dev/null and b/images/4.2.3+Fast+Pair+Validator+环境搭建_f223efd9.jpg differ
diff --git a/images/4.2.3+Fast+Pair+Validator+环境搭建_f73a5e01.jpg b/images/4.2.3+Fast+Pair+Validator+环境搭建_f73a5e01.jpg
new file mode 100644
index 0000000..b447433
Binary files /dev/null and b/images/4.2.3+Fast+Pair+Validator+环境搭建_f73a5e01.jpg differ
diff --git a/images/4.2.3+Fast+Pair+Validator+环境搭建_f9071f6d.jpg b/images/4.2.3+Fast+Pair+Validator+环境搭建_f9071f6d.jpg
new file mode 100644
index 0000000..ab658c5
Binary files /dev/null and b/images/4.2.3+Fast+Pair+Validator+环境搭建_f9071f6d.jpg differ
diff --git a/images/4.2.3+Fast+Pair+Validator+环境搭建_f9b664df.jpg b/images/4.2.3+Fast+Pair+Validator+环境搭建_f9b664df.jpg
new file mode 100644
index 0000000..c7ccda3
Binary files /dev/null and b/images/4.2.3+Fast+Pair+Validator+环境搭建_f9b664df.jpg differ
diff --git a/images/4.2.3+Fast+Pair+Validator+环境搭建_faba6b04.jpg b/images/4.2.3+Fast+Pair+Validator+环境搭建_faba6b04.jpg
new file mode 100644
index 0000000..c5bbb74
Binary files /dev/null and b/images/4.2.3+Fast+Pair+Validator+环境搭建_faba6b04.jpg differ
diff --git a/images/4.3+_MAC+address+rotated,+but+EID+did+not__5c312f42.jpg b/images/4.3+_MAC+address+rotated,+but+EID+did+not__5c312f42.jpg
new file mode 100644
index 0000000..acb60b1
Binary files /dev/null and b/images/4.3+_MAC+address+rotated,+but+EID+did+not__5c312f42.jpg differ
diff --git a/images/4.3+_MAC+address+rotated,+but+EID+did+not__b391897c.jpg b/images/4.3+_MAC+address+rotated,+but+EID+did+not__b391897c.jpg
new file mode 100644
index 0000000..acb60b1
Binary files /dev/null and b/images/4.3+_MAC+address+rotated,+but+EID+did+not__b391897c.jpg differ
diff --git a/images/4.3+测试_197e7c8b.jpg b/images/4.3+测试_197e7c8b.jpg
new file mode 100644
index 0000000..452df53
Binary files /dev/null and b/images/4.3+测试_197e7c8b.jpg differ
diff --git a/images/4.3+测试_8593de8a.jpg b/images/4.3+测试_8593de8a.jpg
new file mode 100644
index 0000000..452df53
Binary files /dev/null and b/images/4.3+测试_8593de8a.jpg differ
diff --git a/images/4.3.1+Fast+Pair+Validator+测试_4959ec92.jpg b/images/4.3.1+Fast+Pair+Validator+测试_4959ec92.jpg
new file mode 100644
index 0000000..240e358
Binary files /dev/null and b/images/4.3.1+Fast+Pair+Validator+测试_4959ec92.jpg differ
diff --git a/images/4.3.1+Fast+Pair+Validator+测试_59383b26.jpg b/images/4.3.1+Fast+Pair+Validator+测试_59383b26.jpg
new file mode 100644
index 0000000..240e358
Binary files /dev/null and b/images/4.3.1+Fast+Pair+Validator+测试_59383b26.jpg differ
diff --git a/images/4.3.1.1+FAST+PAIR_29ae76ff.jpg b/images/4.3.1.1+FAST+PAIR_29ae76ff.jpg
new file mode 100644
index 0000000..7382011
Binary files /dev/null and b/images/4.3.1.1+FAST+PAIR_29ae76ff.jpg differ
diff --git a/images/4.3.1.1+FAST+PAIR_4e64c7e2.jpg b/images/4.3.1.1+FAST+PAIR_4e64c7e2.jpg
new file mode 100644
index 0000000..7382011
Binary files /dev/null and b/images/4.3.1.1+FAST+PAIR_4e64c7e2.jpg differ
diff --git a/images/4.3.1.2+EDDYSTONE_07d29b64.jpg b/images/4.3.1.2+EDDYSTONE_07d29b64.jpg
new file mode 100644
index 0000000..d9995dc
Binary files /dev/null and b/images/4.3.1.2+EDDYSTONE_07d29b64.jpg differ
diff --git a/images/4.3.1.2+EDDYSTONE_1c18715e.jpg b/images/4.3.1.2+EDDYSTONE_1c18715e.jpg
new file mode 100644
index 0000000..d9995dc
Binary files /dev/null and b/images/4.3.1.2+EDDYSTONE_1c18715e.jpg differ
diff --git a/images/4.3.2.3+find+hub_924ad55e.jpg b/images/4.3.2.3+find+hub_924ad55e.jpg
new file mode 100644
index 0000000..d4b395e
Binary files /dev/null and b/images/4.3.2.3+find+hub_924ad55e.jpg differ
diff --git a/images/4.3.2.3+find+hub_b34c2657.jpg b/images/4.3.2.3+find+hub_b34c2657.jpg
new file mode 100644
index 0000000..d4b395e
Binary files /dev/null and b/images/4.3.2.3+find+hub_b34c2657.jpg differ
diff --git a/images/5+Find+device响铃时，手机端提示couldn't+connect_2e1b3f63.jpg b/images/5+Find+device响铃时，手机端提示couldn't+connect_2e1b3f63.jpg
new file mode 100644
index 0000000..fc973a9
Binary files /dev/null and b/images/5+Find+device响铃时，手机端提示couldn't+connect_2e1b3f63.jpg differ
diff --git a/images/5+Find+device响铃时，手机端提示couldn't+connect_2e6e7150.jpg b/images/5+Find+device响铃时，手机端提示couldn't+connect_2e6e7150.jpg
new file mode 100644
index 0000000..fc973a9
Binary files /dev/null and b/images/5+Find+device响铃时，手机端提示couldn't+connect_2e6e7150.jpg differ
diff --git a/images/5+Find+device响铃时，手机端提示couldn't+connect_791017a7.jpg b/images/5+Find+device响铃时，手机端提示couldn't+connect_791017a7.jpg
new file mode 100644
index 0000000..15dd2ed
Binary files /dev/null and b/images/5+Find+device响铃时，手机端提示couldn't+connect_791017a7.jpg differ
diff --git a/images/5+Find+device响铃时，手机端提示couldn't+connect_d04c977e.jpg b/images/5+Find+device响铃时，手机端提示couldn't+connect_d04c977e.jpg
new file mode 100644
index 0000000..15dd2ed
Binary files /dev/null and b/images/5+Find+device响铃时，手机端提示couldn't+connect_d04c977e.jpg differ
diff --git a/images/5.1+project+工程enable对应功能_26edcb43.jpg b/images/5.1+project+工程enable对应功能_26edcb43.jpg
new file mode 100644
index 0000000..cf0b8c5
Binary files /dev/null and b/images/5.1+project+工程enable对应功能_26edcb43.jpg differ
diff --git a/images/5.1+project+工程enable对应功能_a52f2a9d.jpg b/images/5.1+project+工程enable对应功能_a52f2a9d.jpg
new file mode 100644
index 0000000..cf0b8c5
Binary files /dev/null and b/images/5.1+project+工程enable对应功能_a52f2a9d.jpg differ
diff --git a/images/5.2.1+设备端环境搭建_0ecc87fb.jpg b/images/5.2.1+设备端环境搭建_0ecc87fb.jpg
new file mode 100644
index 0000000..1144201
Binary files /dev/null and b/images/5.2.1+设备端环境搭建_0ecc87fb.jpg differ
diff --git a/images/5.2.1+设备端环境搭建_0f0a32e1.jpg b/images/5.2.1+设备端环境搭建_0f0a32e1.jpg
new file mode 100644
index 0000000..e5ad8ea
Binary files /dev/null and b/images/5.2.1+设备端环境搭建_0f0a32e1.jpg differ
diff --git a/images/5.2.1+设备端环境搭建_13ae3d9e.jpg b/images/5.2.1+设备端环境搭建_13ae3d9e.jpg
new file mode 100644
index 0000000..013773f
Binary files /dev/null and b/images/5.2.1+设备端环境搭建_13ae3d9e.jpg differ
diff --git a/images/5.2.1+设备端环境搭建_19cd012f.jpg b/images/5.2.1+设备端环境搭建_19cd012f.jpg
new file mode 100644
index 0000000..4898332
Binary files /dev/null and b/images/5.2.1+设备端环境搭建_19cd012f.jpg differ
diff --git a/images/5.2.1+设备端环境搭建_28d0ce48.jpg b/images/5.2.1+设备端环境搭建_28d0ce48.jpg
new file mode 100644
index 0000000..4d4fe08
Binary files /dev/null and b/images/5.2.1+设备端环境搭建_28d0ce48.jpg differ
diff --git a/images/5.2.1+设备端环境搭建_2c1292fb.jpg b/images/5.2.1+设备端环境搭建_2c1292fb.jpg
new file mode 100644
index 0000000..0918a08
Binary files /dev/null and b/images/5.2.1+设备端环境搭建_2c1292fb.jpg differ
diff --git a/images/5.2.1+设备端环境搭建_2d80b99b.jpg b/images/5.2.1+设备端环境搭建_2d80b99b.jpg
new file mode 100644
index 0000000..a729660
Binary files /dev/null and b/images/5.2.1+设备端环境搭建_2d80b99b.jpg differ
diff --git a/images/5.2.1+设备端环境搭建_30f147ea.jpg b/images/5.2.1+设备端环境搭建_30f147ea.jpg
new file mode 100644
index 0000000..4f4a53b
Binary files /dev/null and b/images/5.2.1+设备端环境搭建_30f147ea.jpg differ
diff --git a/images/5.2.1+设备端环境搭建_35c1cc44.jpg b/images/5.2.1+设备端环境搭建_35c1cc44.jpg
new file mode 100644
index 0000000..e5cd8dd
Binary files /dev/null and b/images/5.2.1+设备端环境搭建_35c1cc44.jpg differ
diff --git a/images/5.2.1+设备端环境搭建_3a6ea962.jpg b/images/5.2.1+设备端环境搭建_3a6ea962.jpg
new file mode 100644
index 0000000..93b4195
Binary files /dev/null and b/images/5.2.1+设备端环境搭建_3a6ea962.jpg differ
diff --git a/images/5.2.1+设备端环境搭建_40f09f9c.jpg b/images/5.2.1+设备端环境搭建_40f09f9c.jpg
new file mode 100644
index 0000000..6c88cec
Binary files /dev/null and b/images/5.2.1+设备端环境搭建_40f09f9c.jpg differ
diff --git a/images/5.2.1+设备端环境搭建_44f81150.jpg b/images/5.2.1+设备端环境搭建_44f81150.jpg
new file mode 100644
index 0000000..0918a08
Binary files /dev/null and b/images/5.2.1+设备端环境搭建_44f81150.jpg differ
diff --git a/images/5.2.1+设备端环境搭建_49b5e247.jpg b/images/5.2.1+设备端环境搭建_49b5e247.jpg
new file mode 100644
index 0000000..241e744
Binary files /dev/null and b/images/5.2.1+设备端环境搭建_49b5e247.jpg differ
diff --git a/images/5.2.1+设备端环境搭建_51011cff.jpg b/images/5.2.1+设备端环境搭建_51011cff.jpg
new file mode 100644
index 0000000..241e744
Binary files /dev/null and b/images/5.2.1+设备端环境搭建_51011cff.jpg differ
diff --git a/images/5.2.1+设备端环境搭建_53279823.jpg b/images/5.2.1+设备端环境搭建_53279823.jpg
new file mode 100644
index 0000000..4898332
Binary files /dev/null and b/images/5.2.1+设备端环境搭建_53279823.jpg differ
diff --git a/images/5.2.1+设备端环境搭建_6ae6f801.jpg b/images/5.2.1+设备端环境搭建_6ae6f801.jpg
new file mode 100644
index 0000000..a729660
Binary files /dev/null and b/images/5.2.1+设备端环境搭建_6ae6f801.jpg differ
diff --git a/images/5.2.1+设备端环境搭建_6fa97bfb.jpg b/images/5.2.1+设备端环境搭建_6fa97bfb.jpg
new file mode 100644
index 0000000..f19a8ff
Binary files /dev/null and b/images/5.2.1+设备端环境搭建_6fa97bfb.jpg differ
diff --git a/images/5.2.1+设备端环境搭建_720998e1.jpg b/images/5.2.1+设备端环境搭建_720998e1.jpg
new file mode 100644
index 0000000..1699bb3
Binary files /dev/null and b/images/5.2.1+设备端环境搭建_720998e1.jpg differ
diff --git a/images/5.2.1+设备端环境搭建_7256fab9.jpg b/images/5.2.1+设备端环境搭建_7256fab9.jpg
new file mode 100644
index 0000000..db704d5
Binary files /dev/null and b/images/5.2.1+设备端环境搭建_7256fab9.jpg differ
diff --git a/images/5.2.1+设备端环境搭建_773dbdeb.jpg b/images/5.2.1+设备端环境搭建_773dbdeb.jpg
new file mode 100644
index 0000000..1699bb3
Binary files /dev/null and b/images/5.2.1+设备端环境搭建_773dbdeb.jpg differ
diff --git a/images/5.2.1+设备端环境搭建_7aa42708.jpg b/images/5.2.1+设备端环境搭建_7aa42708.jpg
new file mode 100644
index 0000000..09df46f
Binary files /dev/null and b/images/5.2.1+设备端环境搭建_7aa42708.jpg differ
diff --git a/images/5.2.1+设备端环境搭建_7cf2eb21.jpg b/images/5.2.1+设备端环境搭建_7cf2eb21.jpg
new file mode 100644
index 0000000..5883aeb
Binary files /dev/null and b/images/5.2.1+设备端环境搭建_7cf2eb21.jpg differ
diff --git a/images/5.2.1+设备端环境搭建_9150821a.jpg b/images/5.2.1+设备端环境搭建_9150821a.jpg
new file mode 100644
index 0000000..d42c4e4
Binary files /dev/null and b/images/5.2.1+设备端环境搭建_9150821a.jpg differ
diff --git a/images/5.2.1+设备端环境搭建_92d3c8dd.jpg b/images/5.2.1+设备端环境搭建_92d3c8dd.jpg
new file mode 100644
index 0000000..93b4195
Binary files /dev/null and b/images/5.2.1+设备端环境搭建_92d3c8dd.jpg differ
diff --git a/images/5.2.1+设备端环境搭建_9c951882.jpg b/images/5.2.1+设备端环境搭建_9c951882.jpg
new file mode 100644
index 0000000..013773f
Binary files /dev/null and b/images/5.2.1+设备端环境搭建_9c951882.jpg differ
diff --git a/images/5.2.1+设备端环境搭建_9e519b30.jpg b/images/5.2.1+设备端环境搭建_9e519b30.jpg
new file mode 100644
index 0000000..d42c4e4
Binary files /dev/null and b/images/5.2.1+设备端环境搭建_9e519b30.jpg differ
diff --git a/images/5.2.1+设备端环境搭建_a28e08cb.jpg b/images/5.2.1+设备端环境搭建_a28e08cb.jpg
new file mode 100644
index 0000000..56c2ce9
Binary files /dev/null and b/images/5.2.1+设备端环境搭建_a28e08cb.jpg differ
diff --git a/images/5.2.1+设备端环境搭建_bae9ee80.jpg b/images/5.2.1+设备端环境搭建_bae9ee80.jpg
new file mode 100644
index 0000000..e30d1e3
Binary files /dev/null and b/images/5.2.1+设备端环境搭建_bae9ee80.jpg differ
diff --git a/images/5.2.1+设备端环境搭建_bbe5e3cd.jpg b/images/5.2.1+设备端环境搭建_bbe5e3cd.jpg
new file mode 100644
index 0000000..f8b4d5a
Binary files /dev/null and b/images/5.2.1+设备端环境搭建_bbe5e3cd.jpg differ
diff --git a/images/5.2.1+设备端环境搭建_bf169e87.jpg b/images/5.2.1+设备端环境搭建_bf169e87.jpg
new file mode 100644
index 0000000..db704d5
Binary files /dev/null and b/images/5.2.1+设备端环境搭建_bf169e87.jpg differ
diff --git a/images/5.2.1+设备端环境搭建_bfed6a27.jpg b/images/5.2.1+设备端环境搭建_bfed6a27.jpg
new file mode 100644
index 0000000..4f4a53b
Binary files /dev/null and b/images/5.2.1+设备端环境搭建_bfed6a27.jpg differ
diff --git a/images/5.2.1+设备端环境搭建_c3f13fee.jpg b/images/5.2.1+设备端环境搭建_c3f13fee.jpg
new file mode 100644
index 0000000..f19a8ff
Binary files /dev/null and b/images/5.2.1+设备端环境搭建_c3f13fee.jpg differ
diff --git a/images/5.2.1+设备端环境搭建_c4731a0f.jpg b/images/5.2.1+设备端环境搭建_c4731a0f.jpg
new file mode 100644
index 0000000..4d4fe08
Binary files /dev/null and b/images/5.2.1+设备端环境搭建_c4731a0f.jpg differ
diff --git a/images/5.2.1+设备端环境搭建_ce0b5690.jpg b/images/5.2.1+设备端环境搭建_ce0b5690.jpg
new file mode 100644
index 0000000..e30d1e3
Binary files /dev/null and b/images/5.2.1+设备端环境搭建_ce0b5690.jpg differ
diff --git a/images/5.2.1+设备端环境搭建_d0d60aaf.jpg b/images/5.2.1+设备端环境搭建_d0d60aaf.jpg
new file mode 100644
index 0000000..56c2ce9
Binary files /dev/null and b/images/5.2.1+设备端环境搭建_d0d60aaf.jpg differ
diff --git a/images/5.2.1+设备端环境搭建_d1325426.jpg b/images/5.2.1+设备端环境搭建_d1325426.jpg
new file mode 100644
index 0000000..1144201
Binary files /dev/null and b/images/5.2.1+设备端环境搭建_d1325426.jpg differ
diff --git a/images/5.2.1+设备端环境搭建_d6a9bb6e.jpg b/images/5.2.1+设备端环境搭建_d6a9bb6e.jpg
new file mode 100644
index 0000000..09df46f
Binary files /dev/null and b/images/5.2.1+设备端环境搭建_d6a9bb6e.jpg differ
diff --git a/images/5.2.1+设备端环境搭建_da818ff3.jpg b/images/5.2.1+设备端环境搭建_da818ff3.jpg
new file mode 100644
index 0000000..f8b4d5a
Binary files /dev/null and b/images/5.2.1+设备端环境搭建_da818ff3.jpg differ
diff --git a/images/5.2.1+设备端环境搭建_dcc7f264.jpg b/images/5.2.1+设备端环境搭建_dcc7f264.jpg
new file mode 100644
index 0000000..e5ad8ea
Binary files /dev/null and b/images/5.2.1+设备端环境搭建_dcc7f264.jpg differ
diff --git a/images/5.2.1+设备端环境搭建_df408f64.jpg b/images/5.2.1+设备端环境搭建_df408f64.jpg
new file mode 100644
index 0000000..6c88cec
Binary files /dev/null and b/images/5.2.1+设备端环境搭建_df408f64.jpg differ
diff --git a/images/5.2.1+设备端环境搭建_eb1a7423.jpg b/images/5.2.1+设备端环境搭建_eb1a7423.jpg
new file mode 100644
index 0000000..5883aeb
Binary files /dev/null and b/images/5.2.1+设备端环境搭建_eb1a7423.jpg differ
diff --git a/images/5.2.1+设备端环境搭建_edd3e39b.jpg b/images/5.2.1+设备端环境搭建_edd3e39b.jpg
new file mode 100644
index 0000000..e5cd8dd
Binary files /dev/null and b/images/5.2.1+设备端环境搭建_edd3e39b.jpg differ
diff --git a/images/5.2.2+手机端环境搭建_01cfc73c.jpg b/images/5.2.2+手机端环境搭建_01cfc73c.jpg
new file mode 100644
index 0000000..4c1855f
Binary files /dev/null and b/images/5.2.2+手机端环境搭建_01cfc73c.jpg differ
diff --git a/images/5.2.2+手机端环境搭建_01e956d7.jpg b/images/5.2.2+手机端环境搭建_01e956d7.jpg
new file mode 100644
index 0000000..631b957
Binary files /dev/null and b/images/5.2.2+手机端环境搭建_01e956d7.jpg differ
diff --git a/images/5.2.2+手机端环境搭建_0591bee7.jpg b/images/5.2.2+手机端环境搭建_0591bee7.jpg
new file mode 100644
index 0000000..3742274
Binary files /dev/null and b/images/5.2.2+手机端环境搭建_0591bee7.jpg differ
diff --git a/images/5.2.2+手机端环境搭建_05993b1f.jpg b/images/5.2.2+手机端环境搭建_05993b1f.jpg
new file mode 100644
index 0000000..b84908a
Binary files /dev/null and b/images/5.2.2+手机端环境搭建_05993b1f.jpg differ
diff --git a/images/5.2.2+手机端环境搭建_0ef228b1.jpg b/images/5.2.2+手机端环境搭建_0ef228b1.jpg
new file mode 100644
index 0000000..3f84e71
Binary files /dev/null and b/images/5.2.2+手机端环境搭建_0ef228b1.jpg differ
diff --git a/images/5.2.2+手机端环境搭建_0fc5f828.jpg b/images/5.2.2+手机端环境搭建_0fc5f828.jpg
new file mode 100644
index 0000000..f8d9645
Binary files /dev/null and b/images/5.2.2+手机端环境搭建_0fc5f828.jpg differ
diff --git a/images/5.2.2+手机端环境搭建_18a777c9.jpg b/images/5.2.2+手机端环境搭建_18a777c9.jpg
new file mode 100644
index 0000000..b447433
Binary files /dev/null and b/images/5.2.2+手机端环境搭建_18a777c9.jpg differ
diff --git a/images/5.2.2+手机端环境搭建_1f55632a.jpg b/images/5.2.2+手机端环境搭建_1f55632a.jpg
new file mode 100644
index 0000000..b7ce1dd
Binary files /dev/null and b/images/5.2.2+手机端环境搭建_1f55632a.jpg differ
diff --git a/images/5.2.2+手机端环境搭建_20458ee3.jpg b/images/5.2.2+手机端环境搭建_20458ee3.jpg
new file mode 100644
index 0000000..c0e85e0
Binary files /dev/null and b/images/5.2.2+手机端环境搭建_20458ee3.jpg differ
diff --git a/images/5.2.2+手机端环境搭建_2512f8d2.jpg b/images/5.2.2+手机端环境搭建_2512f8d2.jpg
new file mode 100644
index 0000000..4c1855f
Binary files /dev/null and b/images/5.2.2+手机端环境搭建_2512f8d2.jpg differ
diff --git a/images/5.2.2+手机端环境搭建_3024354d.jpg b/images/5.2.2+手机端环境搭建_3024354d.jpg
new file mode 100644
index 0000000..302ade0
Binary files /dev/null and b/images/5.2.2+手机端环境搭建_3024354d.jpg differ
diff --git a/images/5.2.2+手机端环境搭建_30d56fde.jpg b/images/5.2.2+手机端环境搭建_30d56fde.jpg
new file mode 100644
index 0000000..9ed6549
Binary files /dev/null and b/images/5.2.2+手机端环境搭建_30d56fde.jpg differ
diff --git a/images/5.2.2+手机端环境搭建_31e343bf.jpg b/images/5.2.2+手机端环境搭建_31e343bf.jpg
new file mode 100644
index 0000000..9fda635
Binary files /dev/null and b/images/5.2.2+手机端环境搭建_31e343bf.jpg differ
diff --git a/images/5.2.2+手机端环境搭建_3d002eb2.jpg b/images/5.2.2+手机端环境搭建_3d002eb2.jpg
new file mode 100644
index 0000000..9fda635
Binary files /dev/null and b/images/5.2.2+手机端环境搭建_3d002eb2.jpg differ
diff --git a/images/5.2.2+手机端环境搭建_405ee4d9.jpg b/images/5.2.2+手机端环境搭建_405ee4d9.jpg
new file mode 100644
index 0000000..15ae088
Binary files /dev/null and b/images/5.2.2+手机端环境搭建_405ee4d9.jpg differ
diff --git a/images/5.2.2+手机端环境搭建_4090869a.jpg b/images/5.2.2+手机端环境搭建_4090869a.jpg
new file mode 100644
index 0000000..2b46edf
Binary files /dev/null and b/images/5.2.2+手机端环境搭建_4090869a.jpg differ
diff --git a/images/5.2.2+手机端环境搭建_421baeac.jpg b/images/5.2.2+手机端环境搭建_421baeac.jpg
new file mode 100644
index 0000000..832578b
Binary files /dev/null and b/images/5.2.2+手机端环境搭建_421baeac.jpg differ
diff --git a/images/5.2.2+手机端环境搭建_424b0c23.jpg b/images/5.2.2+手机端环境搭建_424b0c23.jpg
new file mode 100644
index 0000000..fcb7f36
Binary files /dev/null and b/images/5.2.2+手机端环境搭建_424b0c23.jpg differ
diff --git a/images/5.2.2+手机端环境搭建_426e8049.jpg b/images/5.2.2+手机端环境搭建_426e8049.jpg
new file mode 100644
index 0000000..f8d9645
Binary files /dev/null and b/images/5.2.2+手机端环境搭建_426e8049.jpg differ
diff --git a/images/5.2.2+手机端环境搭建_438dc20f.jpg b/images/5.2.2+手机端环境搭建_438dc20f.jpg
new file mode 100644
index 0000000..302ade0
Binary files /dev/null and b/images/5.2.2+手机端环境搭建_438dc20f.jpg differ
diff --git a/images/5.2.2+手机端环境搭建_45f5a0bd.jpg b/images/5.2.2+手机端环境搭建_45f5a0bd.jpg
new file mode 100644
index 0000000..2a1ff26
Binary files /dev/null and b/images/5.2.2+手机端环境搭建_45f5a0bd.jpg differ
diff --git a/images/5.2.2+手机端环境搭建_477b065f.jpg b/images/5.2.2+手机端环境搭建_477b065f.jpg
new file mode 100644
index 0000000..c3def5e
Binary files /dev/null and b/images/5.2.2+手机端环境搭建_477b065f.jpg differ
diff --git a/images/5.2.2+手机端环境搭建_49d07ca2.jpg b/images/5.2.2+手机端环境搭建_49d07ca2.jpg
new file mode 100644
index 0000000..1408b2d
Binary files /dev/null and b/images/5.2.2+手机端环境搭建_49d07ca2.jpg differ
diff --git a/images/5.2.2+手机端环境搭建_4bb8b6e7.jpg b/images/5.2.2+手机端环境搭建_4bb8b6e7.jpg
new file mode 100644
index 0000000..1408b2d
Binary files /dev/null and b/images/5.2.2+手机端环境搭建_4bb8b6e7.jpg differ
diff --git a/images/5.2.2+手机端环境搭建_54c70aa0.jpg b/images/5.2.2+手机端环境搭建_54c70aa0.jpg
new file mode 100644
index 0000000..9ed6549
Binary files /dev/null and b/images/5.2.2+手机端环境搭建_54c70aa0.jpg differ
diff --git a/images/5.2.2+手机端环境搭建_55844458.jpg b/images/5.2.2+手机端环境搭建_55844458.jpg
new file mode 100644
index 0000000..2a1ff26
Binary files /dev/null and b/images/5.2.2+手机端环境搭建_55844458.jpg differ
diff --git a/images/5.2.2+手机端环境搭建_70c76a3c.jpg b/images/5.2.2+手机端环境搭建_70c76a3c.jpg
new file mode 100644
index 0000000..a4ce3bd
Binary files /dev/null and b/images/5.2.2+手机端环境搭建_70c76a3c.jpg differ
diff --git a/images/5.2.2+手机端环境搭建_718315c8.jpg b/images/5.2.2+手机端环境搭建_718315c8.jpg
new file mode 100644
index 0000000..de363b1
Binary files /dev/null and b/images/5.2.2+手机端环境搭建_718315c8.jpg differ
diff --git a/images/5.2.2+手机端环境搭建_72d9d519.jpg b/images/5.2.2+手机端环境搭建_72d9d519.jpg
new file mode 100644
index 0000000..15ae088
Binary files /dev/null and b/images/5.2.2+手机端环境搭建_72d9d519.jpg differ
diff --git a/images/5.2.2+手机端环境搭建_7ae52d64.jpg b/images/5.2.2+手机端环境搭建_7ae52d64.jpg
new file mode 100644
index 0000000..64d2e42
Binary files /dev/null and b/images/5.2.2+手机端环境搭建_7ae52d64.jpg differ
diff --git a/images/5.2.2+手机端环境搭建_86a15e1e.jpg b/images/5.2.2+手机端环境搭建_86a15e1e.jpg
new file mode 100644
index 0000000..6d2af57
Binary files /dev/null and b/images/5.2.2+手机端环境搭建_86a15e1e.jpg differ
diff --git a/images/5.2.2+手机端环境搭建_874ebdd3.jpg b/images/5.2.2+手机端环境搭建_874ebdd3.jpg
new file mode 100644
index 0000000..5daf99d
Binary files /dev/null and b/images/5.2.2+手机端环境搭建_874ebdd3.jpg differ
diff --git a/images/5.2.2+手机端环境搭建_90bfb898.jpg b/images/5.2.2+手机端环境搭建_90bfb898.jpg
new file mode 100644
index 0000000..1dda003
Binary files /dev/null and b/images/5.2.2+手机端环境搭建_90bfb898.jpg differ
diff --git a/images/5.2.2+手机端环境搭建_9300616d.jpg b/images/5.2.2+手机端环境搭建_9300616d.jpg
new file mode 100644
index 0000000..facfdbb
Binary files /dev/null and b/images/5.2.2+手机端环境搭建_9300616d.jpg differ
diff --git a/images/5.2.2+手机端环境搭建_93acb67a.jpg b/images/5.2.2+手机端环境搭建_93acb67a.jpg
new file mode 100644
index 0000000..1dda003
Binary files /dev/null and b/images/5.2.2+手机端环境搭建_93acb67a.jpg differ
diff --git a/images/5.2.2+手机端环境搭建_96b320bc.jpg b/images/5.2.2+手机端环境搭建_96b320bc.jpg
new file mode 100644
index 0000000..5daf99d
Binary files /dev/null and b/images/5.2.2+手机端环境搭建_96b320bc.jpg differ
diff --git a/images/5.2.2+手机端环境搭建_9f491f40.jpg b/images/5.2.2+手机端环境搭建_9f491f40.jpg
new file mode 100644
index 0000000..e93fb27
Binary files /dev/null and b/images/5.2.2+手机端环境搭建_9f491f40.jpg differ
diff --git a/images/5.2.2+手机端环境搭建_a4668ba0.jpg b/images/5.2.2+手机端环境搭建_a4668ba0.jpg
new file mode 100644
index 0000000..3742274
Binary files /dev/null and b/images/5.2.2+手机端环境搭建_a4668ba0.jpg differ
diff --git a/images/5.2.2+手机端环境搭建_a7bcaee3.jpg b/images/5.2.2+手机端环境搭建_a7bcaee3.jpg
new file mode 100644
index 0000000..e2e2b1c
Binary files /dev/null and b/images/5.2.2+手机端环境搭建_a7bcaee3.jpg differ
diff --git a/images/5.2.2+手机端环境搭建_acf31df7.jpg b/images/5.2.2+手机端环境搭建_acf31df7.jpg
new file mode 100644
index 0000000..e93fb27
Binary files /dev/null and b/images/5.2.2+手机端环境搭建_acf31df7.jpg differ
diff --git a/images/5.2.2+手机端环境搭建_add9116f.jpg b/images/5.2.2+手机端环境搭建_add9116f.jpg
new file mode 100644
index 0000000..c3def5e
Binary files /dev/null and b/images/5.2.2+手机端环境搭建_add9116f.jpg differ
diff --git a/images/5.2.2+手机端环境搭建_aed00ee4.jpg b/images/5.2.2+手机端环境搭建_aed00ee4.jpg
new file mode 100644
index 0000000..891808f
Binary files /dev/null and b/images/5.2.2+手机端环境搭建_aed00ee4.jpg differ
diff --git a/images/5.2.2+手机端环境搭建_b0ce1a0e.jpg b/images/5.2.2+手机端环境搭建_b0ce1a0e.jpg
new file mode 100644
index 0000000..facfdbb
Binary files /dev/null and b/images/5.2.2+手机端环境搭建_b0ce1a0e.jpg differ
diff --git a/images/5.2.2+手机端环境搭建_b33c00c1.jpg b/images/5.2.2+手机端环境搭建_b33c00c1.jpg
new file mode 100644
index 0000000..2b46edf
Binary files /dev/null and b/images/5.2.2+手机端环境搭建_b33c00c1.jpg differ
diff --git a/images/5.2.2+手机端环境搭建_b7611fb0.jpg b/images/5.2.2+手机端环境搭建_b7611fb0.jpg
new file mode 100644
index 0000000..de363b1
Binary files /dev/null and b/images/5.2.2+手机端环境搭建_b7611fb0.jpg differ
diff --git a/images/5.2.2+手机端环境搭建_ba366995.jpg b/images/5.2.2+手机端环境搭建_ba366995.jpg
new file mode 100644
index 0000000..58e9b8b
Binary files /dev/null and b/images/5.2.2+手机端环境搭建_ba366995.jpg differ
diff --git a/images/5.2.2+手机端环境搭建_bad71306.jpg b/images/5.2.2+手机端环境搭建_bad71306.jpg
new file mode 100644
index 0000000..3f84e71
Binary files /dev/null and b/images/5.2.2+手机端环境搭建_bad71306.jpg differ
diff --git a/images/5.2.2+手机端环境搭建_c2ee773f.jpg b/images/5.2.2+手机端环境搭建_c2ee773f.jpg
new file mode 100644
index 0000000..a4ce3bd
Binary files /dev/null and b/images/5.2.2+手机端环境搭建_c2ee773f.jpg differ
diff --git a/images/5.2.2+手机端环境搭建_c305ab22.jpg b/images/5.2.2+手机端环境搭建_c305ab22.jpg
new file mode 100644
index 0000000..b447433
Binary files /dev/null and b/images/5.2.2+手机端环境搭建_c305ab22.jpg differ
diff --git a/images/5.2.2+手机端环境搭建_c5b95806.jpg b/images/5.2.2+手机端环境搭建_c5b95806.jpg
new file mode 100644
index 0000000..64d2e42
Binary files /dev/null and b/images/5.2.2+手机端环境搭建_c5b95806.jpg differ
diff --git a/images/5.2.2+手机端环境搭建_c88c28ca.jpg b/images/5.2.2+手机端环境搭建_c88c28ca.jpg
new file mode 100644
index 0000000..e2e2b1c
Binary files /dev/null and b/images/5.2.2+手机端环境搭建_c88c28ca.jpg differ
diff --git a/images/5.2.2+手机端环境搭建_cf1f1e63.jpg b/images/5.2.2+手机端环境搭建_cf1f1e63.jpg
new file mode 100644
index 0000000..b84908a
Binary files /dev/null and b/images/5.2.2+手机端环境搭建_cf1f1e63.jpg differ
diff --git a/images/5.2.2+手机端环境搭建_d4160c4d.jpg b/images/5.2.2+手机端环境搭建_d4160c4d.jpg
new file mode 100644
index 0000000..631b957
Binary files /dev/null and b/images/5.2.2+手机端环境搭建_d4160c4d.jpg differ
diff --git a/images/5.2.2+手机端环境搭建_dd0980fe.jpg b/images/5.2.2+手机端环境搭建_dd0980fe.jpg
new file mode 100644
index 0000000..832578b
Binary files /dev/null and b/images/5.2.2+手机端环境搭建_dd0980fe.jpg differ
diff --git a/images/5.2.2+手机端环境搭建_debe6113.jpg b/images/5.2.2+手机端环境搭建_debe6113.jpg
new file mode 100644
index 0000000..891808f
Binary files /dev/null and b/images/5.2.2+手机端环境搭建_debe6113.jpg differ
diff --git a/images/5.2.2+手机端环境搭建_e61fcd8a.jpg b/images/5.2.2+手机端环境搭建_e61fcd8a.jpg
new file mode 100644
index 0000000..b7ce1dd
Binary files /dev/null and b/images/5.2.2+手机端环境搭建_e61fcd8a.jpg differ
diff --git a/images/5.2.2+手机端环境搭建_ef1f5c0f.jpg b/images/5.2.2+手机端环境搭建_ef1f5c0f.jpg
new file mode 100644
index 0000000..58e9b8b
Binary files /dev/null and b/images/5.2.2+手机端环境搭建_ef1f5c0f.jpg differ
diff --git a/images/5.2.2+手机端环境搭建_ef5963f5.jpg b/images/5.2.2+手机端环境搭建_ef5963f5.jpg
new file mode 100644
index 0000000..c0e85e0
Binary files /dev/null and b/images/5.2.2+手机端环境搭建_ef5963f5.jpg differ
diff --git a/images/5.2.2+手机端环境搭建_fbc04818.jpg b/images/5.2.2+手机端环境搭建_fbc04818.jpg
new file mode 100644
index 0000000..fcb7f36
Binary files /dev/null and b/images/5.2.2+手机端环境搭建_fbc04818.jpg differ
diff --git a/images/5.2.2+手机端环境搭建_ff06cbd0.jpg b/images/5.2.2+手机端环境搭建_ff06cbd0.jpg
new file mode 100644
index 0000000..6d2af57
Binary files /dev/null and b/images/5.2.2+手机端环境搭建_ff06cbd0.jpg differ
diff --git a/images/5.2.3+Fast+Pair+Validator+环境搭建_035aa57e.jpg b/images/5.2.3+Fast+Pair+Validator+环境搭建_035aa57e.jpg
new file mode 100644
index 0000000..c7ccda3
Binary files /dev/null and b/images/5.2.3+Fast+Pair+Validator+环境搭建_035aa57e.jpg differ
diff --git a/images/5.2.3+Fast+Pair+Validator+环境搭建_0ad4dfc1.jpg b/images/5.2.3+Fast+Pair+Validator+环境搭建_0ad4dfc1.jpg
new file mode 100644
index 0000000..1dda003
Binary files /dev/null and b/images/5.2.3+Fast+Pair+Validator+环境搭建_0ad4dfc1.jpg differ
diff --git a/images/5.2.3+Fast+Pair+Validator+环境搭建_0dc20951.jpg b/images/5.2.3+Fast+Pair+Validator+环境搭建_0dc20951.jpg
new file mode 100644
index 0000000..b447433
Binary files /dev/null and b/images/5.2.3+Fast+Pair+Validator+环境搭建_0dc20951.jpg differ
diff --git a/images/5.2.3+Fast+Pair+Validator+环境搭建_0ee0d186.jpg b/images/5.2.3+Fast+Pair+Validator+环境搭建_0ee0d186.jpg
new file mode 100644
index 0000000..58e9b8b
Binary files /dev/null and b/images/5.2.3+Fast+Pair+Validator+环境搭建_0ee0d186.jpg differ
diff --git a/images/5.2.3+Fast+Pair+Validator+环境搭建_15f94a31.jpg b/images/5.2.3+Fast+Pair+Validator+环境搭建_15f94a31.jpg
new file mode 100644
index 0000000..6a7bd33
Binary files /dev/null and b/images/5.2.3+Fast+Pair+Validator+环境搭建_15f94a31.jpg differ
diff --git a/images/5.2.3+Fast+Pair+Validator+环境搭建_1b704372.jpg b/images/5.2.3+Fast+Pair+Validator+环境搭建_1b704372.jpg
new file mode 100644
index 0000000..6d2af57
Binary files /dev/null and b/images/5.2.3+Fast+Pair+Validator+环境搭建_1b704372.jpg differ
diff --git a/images/5.2.3+Fast+Pair+Validator+环境搭建_2eba02f5.jpg b/images/5.2.3+Fast+Pair+Validator+环境搭建_2eba02f5.jpg
new file mode 100644
index 0000000..2b46edf
Binary files /dev/null and b/images/5.2.3+Fast+Pair+Validator+环境搭建_2eba02f5.jpg differ
diff --git a/images/5.2.3+Fast+Pair+Validator+环境搭建_2ef4b789.jpg b/images/5.2.3+Fast+Pair+Validator+环境搭建_2ef4b789.jpg
new file mode 100644
index 0000000..58e9b8b
Binary files /dev/null and b/images/5.2.3+Fast+Pair+Validator+环境搭建_2ef4b789.jpg differ
diff --git a/images/5.2.3+Fast+Pair+Validator+环境搭建_306d6c6b.jpg b/images/5.2.3+Fast+Pair+Validator+环境搭建_306d6c6b.jpg
new file mode 100644
index 0000000..a80fc45
Binary files /dev/null and b/images/5.2.3+Fast+Pair+Validator+环境搭建_306d6c6b.jpg differ
diff --git a/images/5.2.3+Fast+Pair+Validator+环境搭建_37101f3e.jpg b/images/5.2.3+Fast+Pair+Validator+环境搭建_37101f3e.jpg
new file mode 100644
index 0000000..b4477df
Binary files /dev/null and b/images/5.2.3+Fast+Pair+Validator+环境搭建_37101f3e.jpg differ
diff --git a/images/5.2.3+Fast+Pair+Validator+环境搭建_3ba1bed4.jpg b/images/5.2.3+Fast+Pair+Validator+环境搭建_3ba1bed4.jpg
new file mode 100644
index 0000000..2b46edf
Binary files /dev/null and b/images/5.2.3+Fast+Pair+Validator+环境搭建_3ba1bed4.jpg differ
diff --git a/images/5.2.3+Fast+Pair+Validator+环境搭建_3c342573.jpg b/images/5.2.3+Fast+Pair+Validator+环境搭建_3c342573.jpg
new file mode 100644
index 0000000..071d3f9
Binary files /dev/null and b/images/5.2.3+Fast+Pair+Validator+环境搭建_3c342573.jpg differ
diff --git a/images/5.2.3+Fast+Pair+Validator+环境搭建_3e6fd9c5.jpg b/images/5.2.3+Fast+Pair+Validator+环境搭建_3e6fd9c5.jpg
new file mode 100644
index 0000000..c0e85e0
Binary files /dev/null and b/images/5.2.3+Fast+Pair+Validator+环境搭建_3e6fd9c5.jpg differ
diff --git a/images/5.2.3+Fast+Pair+Validator+环境搭建_3ecd214a.jpg b/images/5.2.3+Fast+Pair+Validator+环境搭建_3ecd214a.jpg
new file mode 100644
index 0000000..302ade0
Binary files /dev/null and b/images/5.2.3+Fast+Pair+Validator+环境搭建_3ecd214a.jpg differ
diff --git a/images/5.2.3+Fast+Pair+Validator+环境搭建_46138484.jpg b/images/5.2.3+Fast+Pair+Validator+环境搭建_46138484.jpg
new file mode 100644
index 0000000..facfdbb
Binary files /dev/null and b/images/5.2.3+Fast+Pair+Validator+环境搭建_46138484.jpg differ
diff --git a/images/5.2.3+Fast+Pair+Validator+环境搭建_48a2fc7c.jpg b/images/5.2.3+Fast+Pair+Validator+环境搭建_48a2fc7c.jpg
new file mode 100644
index 0000000..b84908a
Binary files /dev/null and b/images/5.2.3+Fast+Pair+Validator+环境搭建_48a2fc7c.jpg differ
diff --git a/images/5.2.3+Fast+Pair+Validator+环境搭建_49d47e94.jpg b/images/5.2.3+Fast+Pair+Validator+环境搭建_49d47e94.jpg
new file mode 100644
index 0000000..c5bbb74
Binary files /dev/null and b/images/5.2.3+Fast+Pair+Validator+环境搭建_49d47e94.jpg differ
diff --git a/images/5.2.3+Fast+Pair+Validator+环境搭建_4f5baa26.jpg b/images/5.2.3+Fast+Pair+Validator+环境搭建_4f5baa26.jpg
new file mode 100644
index 0000000..503cb7d
Binary files /dev/null and b/images/5.2.3+Fast+Pair+Validator+环境搭建_4f5baa26.jpg differ
diff --git a/images/5.2.3+Fast+Pair+Validator+环境搭建_53955dc7.jpg b/images/5.2.3+Fast+Pair+Validator+环境搭建_53955dc7.jpg
new file mode 100644
index 0000000..b84908a
Binary files /dev/null and b/images/5.2.3+Fast+Pair+Validator+环境搭建_53955dc7.jpg differ
diff --git a/images/5.2.3+Fast+Pair+Validator+环境搭建_5418b6e3.jpg b/images/5.2.3+Fast+Pair+Validator+环境搭建_5418b6e3.jpg
new file mode 100644
index 0000000..4c1855f
Binary files /dev/null and b/images/5.2.3+Fast+Pair+Validator+环境搭建_5418b6e3.jpg differ
diff --git a/images/5.2.3+Fast+Pair+Validator+环境搭建_5a8a422d.jpg b/images/5.2.3+Fast+Pair+Validator+环境搭建_5a8a422d.jpg
new file mode 100644
index 0000000..1af0580
Binary files /dev/null and b/images/5.2.3+Fast+Pair+Validator+环境搭建_5a8a422d.jpg differ
diff --git a/images/5.2.3+Fast+Pair+Validator+环境搭建_5e0d016c.jpg b/images/5.2.3+Fast+Pair+Validator+环境搭建_5e0d016c.jpg
new file mode 100644
index 0000000..a80fc45
Binary files /dev/null and b/images/5.2.3+Fast+Pair+Validator+环境搭建_5e0d016c.jpg differ
diff --git a/images/5.2.3+Fast+Pair+Validator+环境搭建_60aaefc2.jpg b/images/5.2.3+Fast+Pair+Validator+环境搭建_60aaefc2.jpg
new file mode 100644
index 0000000..c0e85e0
Binary files /dev/null and b/images/5.2.3+Fast+Pair+Validator+环境搭建_60aaefc2.jpg differ
diff --git a/images/5.2.3+Fast+Pair+Validator+环境搭建_6276c471.jpg b/images/5.2.3+Fast+Pair+Validator+环境搭建_6276c471.jpg
new file mode 100644
index 0000000..b4477df
Binary files /dev/null and b/images/5.2.3+Fast+Pair+Validator+环境搭建_6276c471.jpg differ
diff --git a/images/5.2.3+Fast+Pair+Validator+环境搭建_62f4aab6.jpg b/images/5.2.3+Fast+Pair+Validator+环境搭建_62f4aab6.jpg
new file mode 100644
index 0000000..c5bbb74
Binary files /dev/null and b/images/5.2.3+Fast+Pair+Validator+环境搭建_62f4aab6.jpg differ
diff --git a/images/5.2.3+Fast+Pair+Validator+环境搭建_716226a1.jpg b/images/5.2.3+Fast+Pair+Validator+环境搭建_716226a1.jpg
new file mode 100644
index 0000000..7dcfef7
Binary files /dev/null and b/images/5.2.3+Fast+Pair+Validator+环境搭建_716226a1.jpg differ
diff --git a/images/5.2.3+Fast+Pair+Validator+环境搭建_72c7ae37.jpg b/images/5.2.3+Fast+Pair+Validator+环境搭建_72c7ae37.jpg
new file mode 100644
index 0000000..facfdbb
Binary files /dev/null and b/images/5.2.3+Fast+Pair+Validator+环境搭建_72c7ae37.jpg differ
diff --git a/images/5.2.3+Fast+Pair+Validator+环境搭建_7306a412.jpg b/images/5.2.3+Fast+Pair+Validator+环境搭建_7306a412.jpg
new file mode 100644
index 0000000..64d2e42
Binary files /dev/null and b/images/5.2.3+Fast+Pair+Validator+环境搭建_7306a412.jpg differ
diff --git a/images/5.2.3+Fast+Pair+Validator+环境搭建_756586c8.jpg b/images/5.2.3+Fast+Pair+Validator+环境搭建_756586c8.jpg
new file mode 100644
index 0000000..15ae088
Binary files /dev/null and b/images/5.2.3+Fast+Pair+Validator+环境搭建_756586c8.jpg differ
diff --git a/images/5.2.3+Fast+Pair+Validator+环境搭建_75aca606.jpg b/images/5.2.3+Fast+Pair+Validator+环境搭建_75aca606.jpg
new file mode 100644
index 0000000..c3def5e
Binary files /dev/null and b/images/5.2.3+Fast+Pair+Validator+环境搭建_75aca606.jpg differ
diff --git a/images/5.2.3+Fast+Pair+Validator+环境搭建_80b27a07.jpg b/images/5.2.3+Fast+Pair+Validator+环境搭建_80b27a07.jpg
new file mode 100644
index 0000000..6ec45ec
Binary files /dev/null and b/images/5.2.3+Fast+Pair+Validator+环境搭建_80b27a07.jpg differ
diff --git a/images/5.2.3+Fast+Pair+Validator+环境搭建_8301c666.jpg b/images/5.2.3+Fast+Pair+Validator+环境搭建_8301c666.jpg
new file mode 100644
index 0000000..15ae088
Binary files /dev/null and b/images/5.2.3+Fast+Pair+Validator+环境搭建_8301c666.jpg differ
diff --git a/images/5.2.3+Fast+Pair+Validator+环境搭建_8336b092.jpg b/images/5.2.3+Fast+Pair+Validator+环境搭建_8336b092.jpg
new file mode 100644
index 0000000..3f84e71
Binary files /dev/null and b/images/5.2.3+Fast+Pair+Validator+环境搭建_8336b092.jpg differ
diff --git a/images/5.2.3+Fast+Pair+Validator+环境搭建_838c6315.jpg b/images/5.2.3+Fast+Pair+Validator+环境搭建_838c6315.jpg
new file mode 100644
index 0000000..64d2e42
Binary files /dev/null and b/images/5.2.3+Fast+Pair+Validator+环境搭建_838c6315.jpg differ
diff --git a/images/5.2.3+Fast+Pair+Validator+环境搭建_84f0fb0e.jpg b/images/5.2.3+Fast+Pair+Validator+环境搭建_84f0fb0e.jpg
new file mode 100644
index 0000000..ab658c5
Binary files /dev/null and b/images/5.2.3+Fast+Pair+Validator+环境搭建_84f0fb0e.jpg differ
diff --git a/images/5.2.3+Fast+Pair+Validator+环境搭建_8c696322.jpg b/images/5.2.3+Fast+Pair+Validator+环境搭建_8c696322.jpg
new file mode 100644
index 0000000..c7ccda3
Binary files /dev/null and b/images/5.2.3+Fast+Pair+Validator+环境搭建_8c696322.jpg differ
diff --git a/images/5.2.3+Fast+Pair+Validator+环境搭建_8f0890ef.jpg b/images/5.2.3+Fast+Pair+Validator+环境搭建_8f0890ef.jpg
new file mode 100644
index 0000000..7dcfef7
Binary files /dev/null and b/images/5.2.3+Fast+Pair+Validator+环境搭建_8f0890ef.jpg differ
diff --git a/images/5.2.3+Fast+Pair+Validator+环境搭建_8fb29c75.jpg b/images/5.2.3+Fast+Pair+Validator+环境搭建_8fb29c75.jpg
new file mode 100644
index 0000000..6d2af57
Binary files /dev/null and b/images/5.2.3+Fast+Pair+Validator+环境搭建_8fb29c75.jpg differ
diff --git a/images/5.2.3+Fast+Pair+Validator+环境搭建_90b2fb98.jpg b/images/5.2.3+Fast+Pair+Validator+环境搭建_90b2fb98.jpg
new file mode 100644
index 0000000..6a7bd33
Binary files /dev/null and b/images/5.2.3+Fast+Pair+Validator+环境搭建_90b2fb98.jpg differ
diff --git a/images/5.2.3+Fast+Pair+Validator+环境搭建_98965b9e.jpg b/images/5.2.3+Fast+Pair+Validator+环境搭建_98965b9e.jpg
new file mode 100644
index 0000000..071d3f9
Binary files /dev/null and b/images/5.2.3+Fast+Pair+Validator+环境搭建_98965b9e.jpg differ
diff --git a/images/5.2.3+Fast+Pair+Validator+环境搭建_98c46abe.jpg b/images/5.2.3+Fast+Pair+Validator+环境搭建_98c46abe.jpg
new file mode 100644
index 0000000..503cb7d
Binary files /dev/null and b/images/5.2.3+Fast+Pair+Validator+环境搭建_98c46abe.jpg differ
diff --git a/images/5.2.3+Fast+Pair+Validator+环境搭建_afbe52db.jpg b/images/5.2.3+Fast+Pair+Validator+环境搭建_afbe52db.jpg
new file mode 100644
index 0000000..2a1ff26
Binary files /dev/null and b/images/5.2.3+Fast+Pair+Validator+环境搭建_afbe52db.jpg differ
diff --git a/images/5.2.3+Fast+Pair+Validator+环境搭建_b3cba0bd.jpg b/images/5.2.3+Fast+Pair+Validator+环境搭建_b3cba0bd.jpg
new file mode 100644
index 0000000..631b957
Binary files /dev/null and b/images/5.2.3+Fast+Pair+Validator+环境搭建_b3cba0bd.jpg differ
diff --git a/images/5.2.3+Fast+Pair+Validator+环境搭建_b51c93df.jpg b/images/5.2.3+Fast+Pair+Validator+环境搭建_b51c93df.jpg
new file mode 100644
index 0000000..302ade0
Binary files /dev/null and b/images/5.2.3+Fast+Pair+Validator+环境搭建_b51c93df.jpg differ
diff --git a/images/5.2.3+Fast+Pair+Validator+环境搭建_be45c657.jpg b/images/5.2.3+Fast+Pair+Validator+环境搭建_be45c657.jpg
new file mode 100644
index 0000000..c3def5e
Binary files /dev/null and b/images/5.2.3+Fast+Pair+Validator+环境搭建_be45c657.jpg differ
diff --git a/images/5.2.3+Fast+Pair+Validator+环境搭建_c4db2bed.jpg b/images/5.2.3+Fast+Pair+Validator+环境搭建_c4db2bed.jpg
new file mode 100644
index 0000000..b7ce1dd
Binary files /dev/null and b/images/5.2.3+Fast+Pair+Validator+环境搭建_c4db2bed.jpg differ
diff --git a/images/5.2.3+Fast+Pair+Validator+环境搭建_ce542e55.jpg b/images/5.2.3+Fast+Pair+Validator+环境搭建_ce542e55.jpg
new file mode 100644
index 0000000..4c1855f
Binary files /dev/null and b/images/5.2.3+Fast+Pair+Validator+环境搭建_ce542e55.jpg differ
diff --git a/images/5.2.3+Fast+Pair+Validator+环境搭建_ceea292b.jpg b/images/5.2.3+Fast+Pair+Validator+环境搭建_ceea292b.jpg
new file mode 100644
index 0000000..3f84e71
Binary files /dev/null and b/images/5.2.3+Fast+Pair+Validator+环境搭建_ceea292b.jpg differ
diff --git a/images/5.2.3+Fast+Pair+Validator+环境搭建_d89d8930.jpg b/images/5.2.3+Fast+Pair+Validator+环境搭建_d89d8930.jpg
new file mode 100644
index 0000000..b7ce1dd
Binary files /dev/null and b/images/5.2.3+Fast+Pair+Validator+环境搭建_d89d8930.jpg differ
diff --git a/images/5.2.3+Fast+Pair+Validator+环境搭建_dba8e4be.jpg b/images/5.2.3+Fast+Pair+Validator+环境搭建_dba8e4be.jpg
new file mode 100644
index 0000000..631b957
Binary files /dev/null and b/images/5.2.3+Fast+Pair+Validator+环境搭建_dba8e4be.jpg differ
diff --git a/images/5.2.3+Fast+Pair+Validator+环境搭建_dd450f28.jpg b/images/5.2.3+Fast+Pair+Validator+环境搭建_dd450f28.jpg
new file mode 100644
index 0000000..9ed6549
Binary files /dev/null and b/images/5.2.3+Fast+Pair+Validator+环境搭建_dd450f28.jpg differ
diff --git a/images/5.2.3+Fast+Pair+Validator+环境搭建_e381fe80.jpg b/images/5.2.3+Fast+Pair+Validator+环境搭建_e381fe80.jpg
new file mode 100644
index 0000000..ab658c5
Binary files /dev/null and b/images/5.2.3+Fast+Pair+Validator+环境搭建_e381fe80.jpg differ
diff --git a/images/5.2.3+Fast+Pair+Validator+环境搭建_e5f052e8.jpg b/images/5.2.3+Fast+Pair+Validator+环境搭建_e5f052e8.jpg
new file mode 100644
index 0000000..53ef204
Binary files /dev/null and b/images/5.2.3+Fast+Pair+Validator+环境搭建_e5f052e8.jpg differ
diff --git a/images/5.2.3+Fast+Pair+Validator+环境搭建_f072bbed.jpg b/images/5.2.3+Fast+Pair+Validator+环境搭建_f072bbed.jpg
new file mode 100644
index 0000000..1af0580
Binary files /dev/null and b/images/5.2.3+Fast+Pair+Validator+环境搭建_f072bbed.jpg differ
diff --git a/images/5.2.3+Fast+Pair+Validator+环境搭建_f57bd2a6.jpg b/images/5.2.3+Fast+Pair+Validator+环境搭建_f57bd2a6.jpg
new file mode 100644
index 0000000..53ef204
Binary files /dev/null and b/images/5.2.3+Fast+Pair+Validator+环境搭建_f57bd2a6.jpg differ
diff --git a/images/5.2.3+Fast+Pair+Validator+环境搭建_f978517e.jpg b/images/5.2.3+Fast+Pair+Validator+环境搭建_f978517e.jpg
new file mode 100644
index 0000000..2a1ff26
Binary files /dev/null and b/images/5.2.3+Fast+Pair+Validator+环境搭建_f978517e.jpg differ
diff --git a/images/5.2.3+Fast+Pair+Validator+环境搭建_fbcbe534.jpg b/images/5.2.3+Fast+Pair+Validator+环境搭建_fbcbe534.jpg
new file mode 100644
index 0000000..6ec45ec
Binary files /dev/null and b/images/5.2.3+Fast+Pair+Validator+环境搭建_fbcbe534.jpg differ
diff --git a/images/5.2.3+Fast+Pair+Validator+环境搭建_fca1b64a.jpg b/images/5.2.3+Fast+Pair+Validator+环境搭建_fca1b64a.jpg
new file mode 100644
index 0000000..b447433
Binary files /dev/null and b/images/5.2.3+Fast+Pair+Validator+环境搭建_fca1b64a.jpg differ
diff --git a/images/5.2.3+Fast+Pair+Validator+环境搭建_fde76880.jpg b/images/5.2.3+Fast+Pair+Validator+环境搭建_fde76880.jpg
new file mode 100644
index 0000000..1dda003
Binary files /dev/null and b/images/5.2.3+Fast+Pair+Validator+环境搭建_fde76880.jpg differ
diff --git a/images/5.2.3+Fast+Pair+Validator+环境搭建_ff8b1de7.jpg b/images/5.2.3+Fast+Pair+Validator+环境搭建_ff8b1de7.jpg
new file mode 100644
index 0000000..9ed6549
Binary files /dev/null and b/images/5.2.3+Fast+Pair+Validator+环境搭建_ff8b1de7.jpg differ
diff --git a/images/5.3+测试_19a1a9e2.jpg b/images/5.3+测试_19a1a9e2.jpg
new file mode 100644
index 0000000..1dfa124
Binary files /dev/null and b/images/5.3+测试_19a1a9e2.jpg differ
diff --git a/images/5.3+测试_2af41c12.jpg b/images/5.3+测试_2af41c12.jpg
new file mode 100644
index 0000000..1dfa124
Binary files /dev/null and b/images/5.3+测试_2af41c12.jpg differ
diff --git a/images/5.3.1+Fast+Pair+Validator+测试_08d218f0.jpg b/images/5.3.1+Fast+Pair+Validator+测试_08d218f0.jpg
new file mode 100644
index 0000000..240e358
Binary files /dev/null and b/images/5.3.1+Fast+Pair+Validator+测试_08d218f0.jpg differ
diff --git a/images/5.3.1+Fast+Pair+Validator+测试_ec103805.jpg b/images/5.3.1+Fast+Pair+Validator+测试_ec103805.jpg
new file mode 100644
index 0000000..240e358
Binary files /dev/null and b/images/5.3.1+Fast+Pair+Validator+测试_ec103805.jpg differ
diff --git a/images/5.3.1.1+FAST+PAIR_027f4a04.jpg b/images/5.3.1.1+FAST+PAIR_027f4a04.jpg
new file mode 100644
index 0000000..d6bfd8c
Binary files /dev/null and b/images/5.3.1.1+FAST+PAIR_027f4a04.jpg differ
diff --git a/images/5.3.1.1+FAST+PAIR_07079905.jpg b/images/5.3.1.1+FAST+PAIR_07079905.jpg
new file mode 100644
index 0000000..45ab59e
Binary files /dev/null and b/images/5.3.1.1+FAST+PAIR_07079905.jpg differ
diff --git a/images/5.3.1.1+FAST+PAIR_0ddfb703.jpg b/images/5.3.1.1+FAST+PAIR_0ddfb703.jpg
new file mode 100644
index 0000000..284f0ea
Binary files /dev/null and b/images/5.3.1.1+FAST+PAIR_0ddfb703.jpg differ
diff --git a/images/5.3.1.1+FAST+PAIR_150abe8a.jpg b/images/5.3.1.1+FAST+PAIR_150abe8a.jpg
new file mode 100644
index 0000000..d6bfd8c
Binary files /dev/null and b/images/5.3.1.1+FAST+PAIR_150abe8a.jpg differ
diff --git a/images/5.3.1.1+FAST+PAIR_17136798.jpg b/images/5.3.1.1+FAST+PAIR_17136798.jpg
new file mode 100644
index 0000000..83fd46e
Binary files /dev/null and b/images/5.3.1.1+FAST+PAIR_17136798.jpg differ
diff --git a/images/5.3.1.1+FAST+PAIR_191a050d.jpg b/images/5.3.1.1+FAST+PAIR_191a050d.jpg
new file mode 100644
index 0000000..c57fcea
Binary files /dev/null and b/images/5.3.1.1+FAST+PAIR_191a050d.jpg differ
diff --git a/images/5.3.1.1+FAST+PAIR_1aac8a7f.jpg b/images/5.3.1.1+FAST+PAIR_1aac8a7f.jpg
new file mode 100644
index 0000000..284f0ea
Binary files /dev/null and b/images/5.3.1.1+FAST+PAIR_1aac8a7f.jpg differ
diff --git a/images/5.3.1.1+FAST+PAIR_1e6d0eb5.jpg b/images/5.3.1.1+FAST+PAIR_1e6d0eb5.jpg
new file mode 100644
index 0000000..1d09fa6
Binary files /dev/null and b/images/5.3.1.1+FAST+PAIR_1e6d0eb5.jpg differ
diff --git a/images/5.3.1.1+FAST+PAIR_2d7f6524.jpg b/images/5.3.1.1+FAST+PAIR_2d7f6524.jpg
new file mode 100644
index 0000000..4117829
Binary files /dev/null and b/images/5.3.1.1+FAST+PAIR_2d7f6524.jpg differ
diff --git a/images/5.3.1.1+FAST+PAIR_31227d8a.jpg b/images/5.3.1.1+FAST+PAIR_31227d8a.jpg
new file mode 100644
index 0000000..e0855a5
Binary files /dev/null and b/images/5.3.1.1+FAST+PAIR_31227d8a.jpg differ
diff --git a/images/5.3.1.1+FAST+PAIR_4182d368.jpg b/images/5.3.1.1+FAST+PAIR_4182d368.jpg
new file mode 100644
index 0000000..e0855a5
Binary files /dev/null and b/images/5.3.1.1+FAST+PAIR_4182d368.jpg differ
diff --git a/images/5.3.1.1+FAST+PAIR_44ac9e83.jpg b/images/5.3.1.1+FAST+PAIR_44ac9e83.jpg
new file mode 100644
index 0000000..416587f
Binary files /dev/null and b/images/5.3.1.1+FAST+PAIR_44ac9e83.jpg differ
diff --git a/images/5.3.1.1+FAST+PAIR_607670fa.jpg b/images/5.3.1.1+FAST+PAIR_607670fa.jpg
new file mode 100644
index 0000000..fc9d19d
Binary files /dev/null and b/images/5.3.1.1+FAST+PAIR_607670fa.jpg differ
diff --git a/images/5.3.1.1+FAST+PAIR_6a24c835.jpg b/images/5.3.1.1+FAST+PAIR_6a24c835.jpg
new file mode 100644
index 0000000..4b129ea
Binary files /dev/null and b/images/5.3.1.1+FAST+PAIR_6a24c835.jpg differ
diff --git a/images/5.3.1.1+FAST+PAIR_6a2b6bb6.jpg b/images/5.3.1.1+FAST+PAIR_6a2b6bb6.jpg
new file mode 100644
index 0000000..c57fcea
Binary files /dev/null and b/images/5.3.1.1+FAST+PAIR_6a2b6bb6.jpg differ
diff --git a/images/5.3.1.1+FAST+PAIR_77d3df3a.jpg b/images/5.3.1.1+FAST+PAIR_77d3df3a.jpg
new file mode 100644
index 0000000..4117829
Binary files /dev/null and b/images/5.3.1.1+FAST+PAIR_77d3df3a.jpg differ
diff --git a/images/5.3.1.1+FAST+PAIR_79cf6a99.jpg b/images/5.3.1.1+FAST+PAIR_79cf6a99.jpg
new file mode 100644
index 0000000..9be4f15
Binary files /dev/null and b/images/5.3.1.1+FAST+PAIR_79cf6a99.jpg differ
diff --git a/images/5.3.1.1+FAST+PAIR_7b8e89f3.jpg b/images/5.3.1.1+FAST+PAIR_7b8e89f3.jpg
new file mode 100644
index 0000000..20b5009
Binary files /dev/null and b/images/5.3.1.1+FAST+PAIR_7b8e89f3.jpg differ
diff --git a/images/5.3.1.1+FAST+PAIR_7e57a73f.jpg b/images/5.3.1.1+FAST+PAIR_7e57a73f.jpg
new file mode 100644
index 0000000..4b129ea
Binary files /dev/null and b/images/5.3.1.1+FAST+PAIR_7e57a73f.jpg differ
diff --git a/images/5.3.1.1+FAST+PAIR_82c78f69.jpg b/images/5.3.1.1+FAST+PAIR_82c78f69.jpg
new file mode 100644
index 0000000..6265c1b
Binary files /dev/null and b/images/5.3.1.1+FAST+PAIR_82c78f69.jpg differ
diff --git a/images/5.3.1.1+FAST+PAIR_9496abee.jpg b/images/5.3.1.1+FAST+PAIR_9496abee.jpg
new file mode 100644
index 0000000..3db89e9
Binary files /dev/null and b/images/5.3.1.1+FAST+PAIR_9496abee.jpg differ
diff --git a/images/5.3.1.1+FAST+PAIR_9b54f226.jpg b/images/5.3.1.1+FAST+PAIR_9b54f226.jpg
new file mode 100644
index 0000000..416587f
Binary files /dev/null and b/images/5.3.1.1+FAST+PAIR_9b54f226.jpg differ
diff --git a/images/5.3.1.1+FAST+PAIR_9d4a14fb.jpg b/images/5.3.1.1+FAST+PAIR_9d4a14fb.jpg
new file mode 100644
index 0000000..9be4f15
Binary files /dev/null and b/images/5.3.1.1+FAST+PAIR_9d4a14fb.jpg differ
diff --git a/images/5.3.1.1+FAST+PAIR_a2e04649.jpg b/images/5.3.1.1+FAST+PAIR_a2e04649.jpg
new file mode 100644
index 0000000..b8710bd
Binary files /dev/null and b/images/5.3.1.1+FAST+PAIR_a2e04649.jpg differ
diff --git a/images/5.3.1.1+FAST+PAIR_a59ab796.jpg b/images/5.3.1.1+FAST+PAIR_a59ab796.jpg
new file mode 100644
index 0000000..83fd46e
Binary files /dev/null and b/images/5.3.1.1+FAST+PAIR_a59ab796.jpg differ
diff --git a/images/5.3.1.1+FAST+PAIR_b2dafa01.jpg b/images/5.3.1.1+FAST+PAIR_b2dafa01.jpg
new file mode 100644
index 0000000..20b5009
Binary files /dev/null and b/images/5.3.1.1+FAST+PAIR_b2dafa01.jpg differ
diff --git a/images/5.3.1.1+FAST+PAIR_b401740e.jpg b/images/5.3.1.1+FAST+PAIR_b401740e.jpg
new file mode 100644
index 0000000..b8710bd
Binary files /dev/null and b/images/5.3.1.1+FAST+PAIR_b401740e.jpg differ
diff --git a/images/5.3.1.1+FAST+PAIR_b7872199.jpg b/images/5.3.1.1+FAST+PAIR_b7872199.jpg
new file mode 100644
index 0000000..1d09fa6
Binary files /dev/null and b/images/5.3.1.1+FAST+PAIR_b7872199.jpg differ
diff --git a/images/5.3.1.1+FAST+PAIR_c15b7610.jpg b/images/5.3.1.1+FAST+PAIR_c15b7610.jpg
new file mode 100644
index 0000000..45ab59e
Binary files /dev/null and b/images/5.3.1.1+FAST+PAIR_c15b7610.jpg differ
diff --git a/images/5.3.1.1+FAST+PAIR_c2897732.jpg b/images/5.3.1.1+FAST+PAIR_c2897732.jpg
new file mode 100644
index 0000000..e36d6b4
Binary files /dev/null and b/images/5.3.1.1+FAST+PAIR_c2897732.jpg differ
diff --git a/images/5.3.1.1+FAST+PAIR_c63b97c8.jpg b/images/5.3.1.1+FAST+PAIR_c63b97c8.jpg
new file mode 100644
index 0000000..9ff0e76
Binary files /dev/null and b/images/5.3.1.1+FAST+PAIR_c63b97c8.jpg differ
diff --git a/images/5.3.1.1+FAST+PAIR_c7c45301.jpg b/images/5.3.1.1+FAST+PAIR_c7c45301.jpg
new file mode 100644
index 0000000..9ff0e76
Binary files /dev/null and b/images/5.3.1.1+FAST+PAIR_c7c45301.jpg differ
diff --git a/images/5.3.1.1+FAST+PAIR_c815fee0.jpg b/images/5.3.1.1+FAST+PAIR_c815fee0.jpg
new file mode 100644
index 0000000..fc9d19d
Binary files /dev/null and b/images/5.3.1.1+FAST+PAIR_c815fee0.jpg differ
diff --git a/images/5.3.1.1+FAST+PAIR_ccffb068.jpg b/images/5.3.1.1+FAST+PAIR_ccffb068.jpg
new file mode 100644
index 0000000..e36d6b4
Binary files /dev/null and b/images/5.3.1.1+FAST+PAIR_ccffb068.jpg differ
diff --git a/images/5.3.1.1+FAST+PAIR_da5645f2.jpg b/images/5.3.1.1+FAST+PAIR_da5645f2.jpg
new file mode 100644
index 0000000..516f98a
Binary files /dev/null and b/images/5.3.1.1+FAST+PAIR_da5645f2.jpg differ
diff --git a/images/5.3.1.1+FAST+PAIR_dd291069.jpg b/images/5.3.1.1+FAST+PAIR_dd291069.jpg
new file mode 100644
index 0000000..3db89e9
Binary files /dev/null and b/images/5.3.1.1+FAST+PAIR_dd291069.jpg differ
diff --git a/images/5.3.1.1+FAST+PAIR_fa6339fd.jpg b/images/5.3.1.1+FAST+PAIR_fa6339fd.jpg
new file mode 100644
index 0000000..6265c1b
Binary files /dev/null and b/images/5.3.1.1+FAST+PAIR_fa6339fd.jpg differ
diff --git a/images/5.3.1.1+FAST+PAIR_fcbdebb1.jpg b/images/5.3.1.1+FAST+PAIR_fcbdebb1.jpg
new file mode 100644
index 0000000..516f98a
Binary files /dev/null and b/images/5.3.1.1+FAST+PAIR_fcbdebb1.jpg differ
diff --git a/images/5.3.1.2+EDDYSTONE_3b96621d.jpg b/images/5.3.1.2+EDDYSTONE_3b96621d.jpg
new file mode 100644
index 0000000..d9995dc
Binary files /dev/null and b/images/5.3.1.2+EDDYSTONE_3b96621d.jpg differ
diff --git a/images/5.3.1.2+EDDYSTONE_654542e6.jpg b/images/5.3.1.2+EDDYSTONE_654542e6.jpg
new file mode 100644
index 0000000..d9995dc
Binary files /dev/null and b/images/5.3.1.2+EDDYSTONE_654542e6.jpg differ
diff --git a/images/5.3.2.1+Notification+dialog+for+initial+pairing_0af48098.jpg b/images/5.3.2.1+Notification+dialog+for+initial+pairing_0af48098.jpg
new file mode 100644
index 0000000..aa3fb42
Binary files /dev/null and b/images/5.3.2.1+Notification+dialog+for+initial+pairing_0af48098.jpg differ
diff --git a/images/5.3.2.1+Notification+dialog+for+initial+pairing_2327d23e.jpg b/images/5.3.2.1+Notification+dialog+for+initial+pairing_2327d23e.jpg
new file mode 100644
index 0000000..aa3fb42
Binary files /dev/null and b/images/5.3.2.1+Notification+dialog+for+initial+pairing_2327d23e.jpg differ
diff --git a/images/5.3.2.2+Certification+specification+for+distance_44214d5a.jpg b/images/5.3.2.2+Certification+specification+for+distance_44214d5a.jpg
new file mode 100644
index 0000000..63fb5b9
Binary files /dev/null and b/images/5.3.2.2+Certification+specification+for+distance_44214d5a.jpg differ
diff --git a/images/5.3.2.2+Certification+specification+for+distance_fec4bd43.jpg b/images/5.3.2.2+Certification+specification+for+distance_fec4bd43.jpg
new file mode 100644
index 0000000..63fb5b9
Binary files /dev/null and b/images/5.3.2.2+Certification+specification+for+distance_fec4bd43.jpg differ
diff --git a/images/5.3.2.3+find+hub_6bd62d2a.jpg b/images/5.3.2.3+find+hub_6bd62d2a.jpg
new file mode 100644
index 0000000..d4b395e
Binary files /dev/null and b/images/5.3.2.3+find+hub_6bd62d2a.jpg differ
diff --git a/images/5.3.2.3+find+hub_9116d8aa.jpg b/images/5.3.2.3+find+hub_9116d8aa.jpg
new file mode 100644
index 0000000..d4b395e
Binary files /dev/null and b/images/5.3.2.3+find+hub_9116d8aa.jpg differ
diff --git a/images/5手机提示+_无法连接，请转到设置尝试手动与该设备配对__19ce13fa.jpg b/images/5手机提示+_无法连接，请转到设置尝试手动与该设备配对__19ce13fa.jpg
new file mode 100644
index 0000000..8bece25
Binary files /dev/null and b/images/5手机提示+_无法连接，请转到设置尝试手动与该设备配对__19ce13fa.jpg differ
diff --git a/images/5手机提示+_无法连接，请转到设置尝试手动与该设备配对__7a4b4c5a.jpg b/images/5手机提示+_无法连接，请转到设置尝试手动与该设备配对__7a4b4c5a.jpg
new file mode 100644
index 0000000..8bece25
Binary files /dev/null and b/images/5手机提示+_无法连接，请转到设置尝试手动与该设备配对__7a4b4c5a.jpg differ
diff --git a/images/6+Provisioning+for+non-owner+test+fail_0b136cb5.jpg b/images/6+Provisioning+for+non-owner+test+fail_0b136cb5.jpg
new file mode 100644
index 0000000..b205d38
Binary files /dev/null and b/images/6+Provisioning+for+non-owner+test+fail_0b136cb5.jpg differ
diff --git a/images/6+Provisioning+for+non-owner+test+fail_8db142a9.jpg b/images/6+Provisioning+for+non-owner+test+fail_8db142a9.jpg
new file mode 100644
index 0000000..fbb91e1
Binary files /dev/null and b/images/6+Provisioning+for+non-owner+test+fail_8db142a9.jpg differ
diff --git a/images/6+Provisioning+for+non-owner+test+fail_b0e9cfe8.jpg b/images/6+Provisioning+for+non-owner+test+fail_b0e9cfe8.jpg
new file mode 100644
index 0000000..b205d38
Binary files /dev/null and b/images/6+Provisioning+for+non-owner+test+fail_b0e9cfe8.jpg differ
diff --git a/images/6+Provisioning+for+non-owner+test+fail_c08e6b9f.jpg b/images/6+Provisioning+for+non-owner+test+fail_c08e6b9f.jpg
new file mode 100644
index 0000000..fbb91e1
Binary files /dev/null and b/images/6+Provisioning+for+non-owner+test+fail_c08e6b9f.jpg differ
diff --git a/images/6+同一个手机搭配RTK耳机不会弹窗，搭配竞品耳机可以弹窗_302bfce2.jpg b/images/6+同一个手机搭配RTK耳机不会弹窗，搭配竞品耳机可以弹窗_302bfce2.jpg
new file mode 100644
index 0000000..79e24a2
Binary files /dev/null and b/images/6+同一个手机搭配RTK耳机不会弹窗，搭配竞品耳机可以弹窗_302bfce2.jpg differ
diff --git a/images/6+同一个手机搭配RTK耳机不会弹窗，搭配竞品耳机可以弹窗_cdad8810.jpg b/images/6+同一个手机搭配RTK耳机不会弹窗，搭配竞品耳机可以弹窗_cdad8810.jpg
new file mode 100644
index 0000000..79e24a2
Binary files /dev/null and b/images/6+同一个手机搭配RTK耳机不会弹窗，搭配竞品耳机可以弹窗_cdad8810.jpg differ
diff --git a/images/6+用客户自己注册的model+id不弹窗，用rtk认证过的model+id就可以弹窗_1fc5c4ef.jpg b/images/6+用客户自己注册的model+id不弹窗，用rtk认证过的model+id就可以弹窗_1fc5c4ef.jpg
new file mode 100644
index 0000000..79e24a2
Binary files /dev/null and b/images/6+用客户自己注册的model+id不弹窗，用rtk认证过的model+id就可以弹窗_1fc5c4ef.jpg differ
diff --git a/images/6+用客户自己注册的model+id不弹窗，用rtk认证过的model+id就可以弹窗_b9e9f47b.jpg b/images/6+用客户自己注册的model+id不弹窗，用rtk认证过的model+id就可以弹窗_b9e9f47b.jpg
new file mode 100644
index 0000000..79e24a2
Binary files /dev/null and b/images/6+用客户自己注册的model+id不弹窗，用rtk认证过的model+id就可以弹窗_b9e9f47b.jpg differ
diff --git a/images/6.1++Device+not+found+by+AK_89d54256.jpg b/images/6.1++Device+not+found+by+AK_89d54256.jpg
new file mode 100644
index 0000000..a3ce419
Binary files /dev/null and b/images/6.1++Device+not+found+by+AK_89d54256.jpg differ
diff --git a/images/6.1++Device+not+found+by+AK_f95601fa.jpg b/images/6.1++Device+not+found+by+AK_f95601fa.jpg
new file mode 100644
index 0000000..a3ce419
Binary files /dev/null and b/images/6.1++Device+not+found+by+AK_f95601fa.jpg differ
diff --git a/images/7++cross_seeker_auto_subsequent_pairing_test_from_LEA_phone_to_LEA_phone+_+Receive+unexpected+profile+connection_485cc1f9.jpg b/images/7++cross_seeker_auto_subsequent_pairing_test_from_LEA_phone_to_LEA_phone+_+Receive+unexpected+profile+connection_485cc1f9.jpg
new file mode 100644
index 0000000..37308a6
Binary files /dev/null and b/images/7++cross_seeker_auto_subsequent_pairing_test_from_LEA_phone_to_LEA_phone+_+Receive+unexpected+profile+connection_485cc1f9.jpg differ
diff --git a/images/7++cross_seeker_auto_subsequent_pairing_test_from_LEA_phone_to_LEA_phone+_+Receive+unexpected+profile+connection_62c59ab2.jpg b/images/7++cross_seeker_auto_subsequent_pairing_test_from_LEA_phone_to_LEA_phone+_+Receive+unexpected+profile+connection_62c59ab2.jpg
new file mode 100644
index 0000000..85e189d
Binary files /dev/null and b/images/7++cross_seeker_auto_subsequent_pairing_test_from_LEA_phone_to_LEA_phone+_+Receive+unexpected+profile+connection_62c59ab2.jpg differ
diff --git a/images/7++cross_seeker_auto_subsequent_pairing_test_from_LEA_phone_to_LEA_phone+_+Receive+unexpected+profile+connection_99da945b.jpg b/images/7++cross_seeker_auto_subsequent_pairing_test_from_LEA_phone_to_LEA_phone+_+Receive+unexpected+profile+connection_99da945b.jpg
new file mode 100644
index 0000000..d7b4446
Binary files /dev/null and b/images/7++cross_seeker_auto_subsequent_pairing_test_from_LEA_phone_to_LEA_phone+_+Receive+unexpected+profile+connection_99da945b.jpg differ
diff --git a/images/7++cross_seeker_auto_subsequent_pairing_test_from_LEA_phone_to_LEA_phone+_+Receive+unexpected+profile+connection_b38109a0.jpg b/images/7++cross_seeker_auto_subsequent_pairing_test_from_LEA_phone_to_LEA_phone+_+Receive+unexpected+profile+connection_b38109a0.jpg
new file mode 100644
index 0000000..85e189d
Binary files /dev/null and b/images/7++cross_seeker_auto_subsequent_pairing_test_from_LEA_phone_to_LEA_phone+_+Receive+unexpected+profile+connection_b38109a0.jpg differ
diff --git a/images/7++cross_seeker_auto_subsequent_pairing_test_from_LEA_phone_to_LEA_phone+_+Receive+unexpected+profile+connection_d1dc9e9e.jpg b/images/7++cross_seeker_auto_subsequent_pairing_test_from_LEA_phone_to_LEA_phone+_+Receive+unexpected+profile+connection_d1dc9e9e.jpg
new file mode 100644
index 0000000..37308a6
Binary files /dev/null and b/images/7++cross_seeker_auto_subsequent_pairing_test_from_LEA_phone_to_LEA_phone+_+Receive+unexpected+profile+connection_d1dc9e9e.jpg differ
diff --git a/images/7++cross_seeker_auto_subsequent_pairing_test_from_LEA_phone_to_LEA_phone+_+Receive+unexpected+profile+connection_f3ad48c6.jpg b/images/7++cross_seeker_auto_subsequent_pairing_test_from_LEA_phone_to_LEA_phone+_+Receive+unexpected+profile+connection_f3ad48c6.jpg
new file mode 100644
index 0000000..d7b4446
Binary files /dev/null and b/images/7++cross_seeker_auto_subsequent_pairing_test_from_LEA_phone_to_LEA_phone+_+Receive+unexpected+profile+connection_f3ad48c6.jpg differ
diff --git a/images/7+Cross+Seekers+Auto+Subsequent+Pairing+Test+from+LE+audio+phone+to+LE+audio+phone+測試fail：+Not+receive+UUID,+is+connected_+false_21daea25.jpg b/images/7+Cross+Seekers+Auto+Subsequent+Pairing+Test+from+LE+audio+phone+to+LE+audio+phone+測試fail：+Not+receive+UUID,+is+connected_+false_21daea25.jpg
new file mode 100644
index 0000000..25af285
Binary files /dev/null and b/images/7+Cross+Seekers+Auto+Subsequent+Pairing+Test+from+LE+audio+phone+to+LE+audio+phone+測試fail：+Not+receive+UUID,+is+connected_+false_21daea25.jpg differ
diff --git a/images/7+Cross+Seekers+Auto+Subsequent+Pairing+Test+from+LE+audio+phone+to+LE+audio+phone+測試fail：+Not+receive+UUID,+is+connected_+false_2808da13.jpg b/images/7+Cross+Seekers+Auto+Subsequent+Pairing+Test+from+LE+audio+phone+to+LE+audio+phone+測試fail：+Not+receive+UUID,+is+connected_+false_2808da13.jpg
new file mode 100644
index 0000000..79f3c20
Binary files /dev/null and b/images/7+Cross+Seekers+Auto+Subsequent+Pairing+Test+from+LE+audio+phone+to+LE+audio+phone+測試fail：+Not+receive+UUID,+is+connected_+false_2808da13.jpg differ
diff --git a/images/7+Cross+Seekers+Auto+Subsequent+Pairing+Test+from+LE+audio+phone+to+LE+audio+phone+測試fail：+Not+receive+UUID,+is+connected_+false_776208e4.jpg b/images/7+Cross+Seekers+Auto+Subsequent+Pairing+Test+from+LE+audio+phone+to+LE+audio+phone+測試fail：+Not+receive+UUID,+is+connected_+false_776208e4.jpg
new file mode 100644
index 0000000..79f3c20
Binary files /dev/null and b/images/7+Cross+Seekers+Auto+Subsequent+Pairing+Test+from+LE+audio+phone+to+LE+audio+phone+測試fail：+Not+receive+UUID,+is+connected_+false_776208e4.jpg differ
diff --git a/images/7+Cross+Seekers+Auto+Subsequent+Pairing+Test+from+LE+audio+phone+to+LE+audio+phone+測試fail：+Not+receive+UUID,+is+connected_+false_c7ca74f7.jpg b/images/7+Cross+Seekers+Auto+Subsequent+Pairing+Test+from+LE+audio+phone+to+LE+audio+phone+測試fail：+Not+receive+UUID,+is+connected_+false_c7ca74f7.jpg
new file mode 100644
index 0000000..25af285
Binary files /dev/null and b/images/7+Cross+Seekers+Auto+Subsequent+Pairing+Test+from+LE+audio+phone+to+LE+audio+phone+測試fail：+Not+receive+UUID,+is+connected_+false_c7ca74f7.jpg differ
diff --git a/images/7+cross_seeker_auto_subsequent_pairing_test_from_NonLEA_phone_to_LEA_phone+_++Not+receive+UUID+Is+connected+false_704d28da.jpg b/images/7+cross_seeker_auto_subsequent_pairing_test_from_NonLEA_phone_to_LEA_phone+_++Not+receive+UUID+Is+connected+false_704d28da.jpg
new file mode 100644
index 0000000..1e2f19d
Binary files /dev/null and b/images/7+cross_seeker_auto_subsequent_pairing_test_from_NonLEA_phone_to_LEA_phone+_++Not+receive+UUID+Is+connected+false_704d28da.jpg differ
diff --git a/images/7+cross_seeker_auto_subsequent_pairing_test_from_NonLEA_phone_to_LEA_phone+_++Not+receive+UUID+Is+connected+false_aaef53de.jpg b/images/7+cross_seeker_auto_subsequent_pairing_test_from_NonLEA_phone_to_LEA_phone+_++Not+receive+UUID+Is+connected+false_aaef53de.jpg
new file mode 100644
index 0000000..1e2f19d
Binary files /dev/null and b/images/7+cross_seeker_auto_subsequent_pairing_test_from_NonLEA_phone_to_LEA_phone+_++Not+receive+UUID+Is+connected+false_aaef53de.jpg differ
diff --git a/images/7+cross_seeker_auto_subsequent_pairing_test_from_NonLEA_phone_to_LEA_phone+__5f1de099.jpg b/images/7+cross_seeker_auto_subsequent_pairing_test_from_NonLEA_phone_to_LEA_phone+__5f1de099.jpg
new file mode 100644
index 0000000..0e9a7d0
Binary files /dev/null and b/images/7+cross_seeker_auto_subsequent_pairing_test_from_NonLEA_phone_to_LEA_phone+__5f1de099.jpg differ
diff --git a/images/7+cross_seeker_auto_subsequent_pairing_test_from_NonLEA_phone_to_LEA_phone+__97aadabc.jpg b/images/7+cross_seeker_auto_subsequent_pairing_test_from_NonLEA_phone_to_LEA_phone+__97aadabc.jpg
new file mode 100644
index 0000000..0e9a7d0
Binary files /dev/null and b/images/7+cross_seeker_auto_subsequent_pairing_test_from_NonLEA_phone_to_LEA_phone+__97aadabc.jpg differ
diff --git a/images/9.1+“Error+while+scaning+by+EID_+Scan+timed+out”_ca4bd62c.jpg b/images/9.1+“Error+while+scaning+by+EID_+Scan+timed+out”_ca4bd62c.jpg
new file mode 100644
index 0000000..124f5ec
Binary files /dev/null and b/images/9.1+“Error+while+scaning+by+EID_+Scan+timed+out”_ca4bd62c.jpg differ
diff --git a/images/9.1+“Error+while+scaning+by+EID_+Scan+timed+out”_e19959c3.jpg b/images/9.1+“Error+while+scaning+by+EID_+Scan+timed+out”_e19959c3.jpg
new file mode 100644
index 0000000..124f5ec
Binary files /dev/null and b/images/9.1+“Error+while+scaning+by+EID_+Scan+timed+out”_e19959c3.jpg differ
diff --git a/images/9.2+Invalid+authentication+not+rejected_47c8ac63.jpg b/images/9.2+Invalid+authentication+not+rejected_47c8ac63.jpg
new file mode 100644
index 0000000..401f6fc
Binary files /dev/null and b/images/9.2+Invalid+authentication+not+rejected_47c8ac63.jpg differ
diff --git a/images/9.2+Invalid+authentication+not+rejected_ed0b4526.jpg b/images/9.2+Invalid+authentication+not+rejected_ed0b4526.jpg
new file mode 100644
index 0000000..401f6fc
Binary files /dev/null and b/images/9.2+Invalid+authentication+not+rejected_ed0b4526.jpg differ
diff --git a/images/9.3+device+not+found+by+Account+key_1b6ff5fb.jpg b/images/9.3+device+not+found+by+Account+key_1b6ff5fb.jpg
new file mode 100644
index 0000000..e9db672
Binary files /dev/null and b/images/9.3+device+not+found+by+Account+key_1b6ff5fb.jpg differ
diff --git a/images/9.3+device+not+found+by+Account+key_bc900d11.jpg b/images/9.3+device+not+found+by+Account+key_bc900d11.jpg
new file mode 100644
index 0000000..e9db672
Binary files /dev/null and b/images/9.3+device+not+found+by+Account+key_bc900d11.jpg differ
diff --git a/images/9.通过GFPS弹窗配对之后，手机setting不显示LE+audio的button_5720545f.jpg b/images/9.通过GFPS弹窗配对之后，手机setting不显示LE+audio的button_5720545f.jpg
new file mode 100644
index 0000000..091d5bf
Binary files /dev/null and b/images/9.通过GFPS弹窗配对之后，手机setting不显示LE+audio的button_5720545f.jpg differ
diff --git a/images/9.通过GFPS弹窗配对之后，手机setting不显示LE+audio的button_b51d6a16.jpg b/images/9.通过GFPS弹窗配对之后，手机setting不显示LE+audio的button_b51d6a16.jpg
new file mode 100644
index 0000000..091d5bf
Binary files /dev/null and b/images/9.通过GFPS弹窗配对之后，手机setting不显示LE+audio的button_b51d6a16.jpg differ
diff --git a/images/Advertise+Address+Verification+fail_503731d2.jpg b/images/Advertise+Address+Verification+fail_503731d2.jpg
new file mode 100644
index 0000000..e8db744
Binary files /dev/null and b/images/Advertise+Address+Verification+fail_503731d2.jpg differ
diff --git a/images/Advertise+Address+Verification+fail_5f03ad30.jpg b/images/Advertise+Address+Verification+fail_5f03ad30.jpg
new file mode 100644
index 0000000..e8db744
Binary files /dev/null and b/images/Advertise+Address+Verification+fail_5f03ad30.jpg differ
diff --git a/images/Android+13+initial+pair+fail+手机不来连BREDR_c8223c5f.jpg b/images/Android+13+initial+pair+fail+手机不来连BREDR_c8223c5f.jpg
new file mode 100644
index 0000000..9c7ee36
Binary files /dev/null and b/images/Android+13+initial+pair+fail+手机不来连BREDR_c8223c5f.jpg differ
diff --git a/images/Android+13+initial+pair+fail+手机不来连BREDR_cf4b59fb.jpg b/images/Android+13+initial+pair+fail+手机不来连BREDR_cf4b59fb.jpg
new file mode 100644
index 0000000..9c7ee36
Binary files /dev/null and b/images/Android+13+initial+pair+fail+手机不来连BREDR_cf4b59fb.jpg differ
diff --git a/images/BLE+advertisements+don't+contain+Fast+Pair+account+key+while+not+in+pairing+mode_61611a7f.jpg b/images/BLE+advertisements+don't+contain+Fast+Pair+account+key+while+not+in+pairing+mode_61611a7f.jpg
new file mode 100644
index 0000000..c0e232c
Binary files /dev/null and b/images/BLE+advertisements+don't+contain+Fast+Pair+account+key+while+not+in+pairing+mode_61611a7f.jpg differ
diff --git a/images/BLE+advertisements+don't+contain+Fast+Pair+account+key+while+not+in+pairing+mode_98b978d3.jpg b/images/BLE+advertisements+don't+contain+Fast+Pair+account+key+while+not+in+pairing+mode_98b978d3.jpg
new file mode 100644
index 0000000..3b45674
Binary files /dev/null and b/images/BLE+advertisements+don't+contain+Fast+Pair+account+key+while+not+in+pairing+mode_98b978d3.jpg differ
diff --git a/images/BLE+advertisements+don't+contain+Fast+Pair+account+key+while+not+in+pairing+mode_9cba252e.jpg b/images/BLE+advertisements+don't+contain+Fast+Pair+account+key+while+not+in+pairing+mode_9cba252e.jpg
new file mode 100644
index 0000000..3b45674
Binary files /dev/null and b/images/BLE+advertisements+don't+contain+Fast+Pair+account+key+while+not+in+pairing+mode_9cba252e.jpg differ
diff --git a/images/BLE+advertisements+don't+contain+Fast+Pair+account+key+while+not+in+pairing+mode_f3213c99.jpg b/images/BLE+advertisements+don't+contain+Fast+Pair+account+key+while+not+in+pairing+mode_f3213c99.jpg
new file mode 100644
index 0000000..c0e232c
Binary files /dev/null and b/images/BLE+advertisements+don't+contain+Fast+Pair+account+key+while+not+in+pairing+mode_f3213c99.jpg differ
diff --git a/images/Bypass+Bluetooth+LE+Audio+Allowlist+开启或关闭，手机端默认连接的profile是不一样的_18a6cf07.jpg b/images/Bypass+Bluetooth+LE+Audio+Allowlist+开启或关闭，手机端默认连接的profile是不一样的_18a6cf07.jpg
new file mode 100644
index 0000000..85e189d
Binary files /dev/null and b/images/Bypass+Bluetooth+LE+Audio+Allowlist+开启或关闭，手机端默认连接的profile是不一样的_18a6cf07.jpg differ
diff --git a/images/Bypass+Bluetooth+LE+Audio+Allowlist+开启或关闭，手机端默认连接的profile是不一样的_be6e99be.jpg b/images/Bypass+Bluetooth+LE+Audio+Allowlist+开启或关闭，手机端默认连接的profile是不一样的_be6e99be.jpg
new file mode 100644
index 0000000..85e189d
Binary files /dev/null and b/images/Bypass+Bluetooth+LE+Audio+Allowlist+开启或关闭，手机端默认连接的profile是不一样的_be6e99be.jpg differ
diff --git a/images/Could+not+connect+to+....._428ce5aa.jpg b/images/Could+not+connect+to+....._428ce5aa.jpg
new file mode 100644
index 0000000..c967bb7
Binary files /dev/null and b/images/Could+not+connect+to+....._428ce5aa.jpg differ
diff --git a/images/Could+not+connect+to+....._86ad201e.jpg b/images/Could+not+connect+to+....._86ad201e.jpg
new file mode 100644
index 0000000..c967bb7
Binary files /dev/null and b/images/Could+not+connect+to+....._86ad201e.jpg differ
diff --git a/images/Cross+Seekers+Auto+Subsequent+Test+Fail_74004aa9.jpg b/images/Cross+Seekers+Auto+Subsequent+Test+Fail_74004aa9.jpg
new file mode 100644
index 0000000..52aa83e
Binary files /dev/null and b/images/Cross+Seekers+Auto+Subsequent+Test+Fail_74004aa9.jpg differ
diff --git a/images/Cross+Seekers+Auto+Subsequent+Test+Fail_cc322fcc.jpg b/images/Cross+Seekers+Auto+Subsequent+Test+Fail_cc322fcc.jpg
new file mode 100644
index 0000000..52aa83e
Binary files /dev/null and b/images/Cross+Seekers+Auto+Subsequent+Test+Fail_cc322fcc.jpg differ
diff --git a/images/Device(XXXXXX)+not+found_a00bd826.jpg b/images/Device(XXXXXX)+not+found_a00bd826.jpg
new file mode 100644
index 0000000..4261f40
Binary files /dev/null and b/images/Device(XXXXXX)+not+found_a00bd826.jpg differ
diff --git a/images/Device(XXXXXX)+not+found_b982d525.jpg b/images/Device(XXXXXX)+not+found_b982d525.jpg
new file mode 100644
index 0000000..4261f40
Binary files /dev/null and b/images/Device(XXXXXX)+not+found_b982d525.jpg differ
diff --git a/images/EID+rotated+but+MAC+address+did+not_7b1393c8.jpg b/images/EID+rotated+but+MAC+address+did+not_7b1393c8.jpg
new file mode 100644
index 0000000..104e301
Binary files /dev/null and b/images/EID+rotated+but+MAC+address+did+not_7b1393c8.jpg differ
diff --git a/images/EID+rotated+but+MAC+address+did+not_c6fb7712.jpg b/images/EID+rotated+but+MAC+address+did+not_c6fb7712.jpg
new file mode 100644
index 0000000..104e301
Binary files /dev/null and b/images/EID+rotated+but+MAC+address+did+not_c6fb7712.jpg differ
diff --git a/images/End-to-end_+'ble+advertisement+doesn't+contain+fast+pair+account+key'_06097ef2.jpg b/images/End-to-end_+'ble+advertisement+doesn't+contain+fast+pair+account+key'_06097ef2.jpg
new file mode 100644
index 0000000..d9b5891
Binary files /dev/null and b/images/End-to-end_+'ble+advertisement+doesn't+contain+fast+pair+account+key'_06097ef2.jpg differ
diff --git a/images/End-to-end_+'ble+advertisement+doesn't+contain+fast+pair+account+key'_f3ba12ce.jpg b/images/End-to-end_+'ble+advertisement+doesn't+contain+fast+pair+account+key'_f3ba12ce.jpg
new file mode 100644
index 0000000..d9b5891
Binary files /dev/null and b/images/End-to-end_+'ble+advertisement+doesn't+contain+fast+pair+account+key'_f3ba12ce.jpg differ
diff --git a/images/End-to-end__Pairing+failed__040b39b6.jpg b/images/End-to-end__Pairing+failed__040b39b6.jpg
new file mode 100644
index 0000000..bc64cdf
Binary files /dev/null and b/images/End-to-end__Pairing+failed__040b39b6.jpg differ
diff --git a/images/End-to-end__Pairing+failed__413e3dd5.jpg b/images/End-to-end__Pairing+failed__413e3dd5.jpg
new file mode 100644
index 0000000..bc64cdf
Binary files /dev/null and b/images/End-to-end__Pairing+failed__413e3dd5.jpg differ
diff --git a/images/FF_+Find+my+device+app界面电量不显示_0dbcba01.jpg b/images/FF_+Find+my+device+app界面电量不显示_0dbcba01.jpg
new file mode 100644
index 0000000..a0b6793
Binary files /dev/null and b/images/FF_+Find+my+device+app界面电量不显示_0dbcba01.jpg differ
diff --git a/images/FF_+Find+my+device+app界面电量不显示_13fb0581.jpg b/images/FF_+Find+my+device+app界面电量不显示_13fb0581.jpg
new file mode 100644
index 0000000..81a75ac
Binary files /dev/null and b/images/FF_+Find+my+device+app界面电量不显示_13fb0581.jpg differ
diff --git a/images/FF_+Find+my+device+app界面电量不显示_2872dcdd.jpg b/images/FF_+Find+my+device+app界面电量不显示_2872dcdd.jpg
new file mode 100644
index 0000000..41e9ba2
Binary files /dev/null and b/images/FF_+Find+my+device+app界面电量不显示_2872dcdd.jpg differ
diff --git a/images/FF_+Find+my+device+app界面电量不显示_40781c9c.jpg b/images/FF_+Find+my+device+app界面电量不显示_40781c9c.jpg
new file mode 100644
index 0000000..81a75ac
Binary files /dev/null and b/images/FF_+Find+my+device+app界面电量不显示_40781c9c.jpg differ
diff --git a/images/FF_+Find+my+device+app界面电量不显示_46d9ea86.jpg b/images/FF_+Find+my+device+app界面电量不显示_46d9ea86.jpg
new file mode 100644
index 0000000..41e9ba2
Binary files /dev/null and b/images/FF_+Find+my+device+app界面电量不显示_46d9ea86.jpg differ
diff --git a/images/FF_+Find+my+device+app界面电量不显示_5953aa23.jpg b/images/FF_+Find+my+device+app界面电量不显示_5953aa23.jpg
new file mode 100644
index 0000000..a0b6793
Binary files /dev/null and b/images/FF_+Find+my+device+app界面电量不显示_5953aa23.jpg differ
diff --git a/images/FF_+有时候显示“Near+you+right+now”,有时候显示“last+seen+near+you+just+now”_52faf25a.jpg b/images/FF_+有时候显示“Near+you+right+now”,有时候显示“last+seen+near+you+just+now”_52faf25a.jpg
new file mode 100644
index 0000000..05822bb
Binary files /dev/null and b/images/FF_+有时候显示“Near+you+right+now”,有时候显示“last+seen+near+you+just+now”_52faf25a.jpg differ
diff --git a/images/FF_+有时候显示“Near+you+right+now”,有时候显示“last+seen+near+you+just+now”_aca9e799.jpg b/images/FF_+有时候显示“Near+you+right+now”,有时候显示“last+seen+near+you+just+now”_aca9e799.jpg
new file mode 100644
index 0000000..05822bb
Binary files /dev/null and b/images/FF_+有时候显示“Near+you+right+now”,有时候显示“last+seen+near+you+just+now”_aca9e799.jpg differ
diff --git a/images/Fail+Reason_+Firmware+version+should+not+be+readable_42634d13.jpg b/images/Fail+Reason_+Firmware+version+should+not+be+readable_42634d13.jpg
new file mode 100644
index 0000000..9bbe616
Binary files /dev/null and b/images/Fail+Reason_+Firmware+version+should+not+be+readable_42634d13.jpg differ
diff --git a/images/Fail+Reason_+Firmware+version+should+not+be+readable_503d4c0e.jpg b/images/Fail+Reason_+Firmware+version+should+not+be+readable_503d4c0e.jpg
new file mode 100644
index 0000000..9bbe616
Binary files /dev/null and b/images/Fail+Reason_+Firmware+version+should+not+be+readable_503d4c0e.jpg differ
diff --git a/images/Failed+to+start+ringing_74679173.jpg b/images/Failed+to+start+ringing_74679173.jpg
new file mode 100644
index 0000000..fd8c9e5
Binary files /dev/null and b/images/Failed+to+start+ringing_74679173.jpg differ
diff --git a/images/Failed+to+start+ringing_939d4a68.jpg b/images/Failed+to+start+ringing_939d4a68.jpg
new file mode 100644
index 0000000..f6d630a
Binary files /dev/null and b/images/Failed+to+start+ringing_939d4a68.jpg differ
diff --git a/images/Failed+to+start+ringing_a890f2ad.jpg b/images/Failed+to+start+ringing_a890f2ad.jpg
new file mode 100644
index 0000000..fd8c9e5
Binary files /dev/null and b/images/Failed+to+start+ringing_a890f2ad.jpg differ
diff --git a/images/Failed+to+start+ringing_bbed4996.jpg b/images/Failed+to+start+ringing_bbed4996.jpg
new file mode 100644
index 0000000..787cbf7
Binary files /dev/null and b/images/Failed+to+start+ringing_bbed4996.jpg differ
diff --git a/images/Failed+to+start+ringing_bd12b64c.jpg b/images/Failed+to+start+ringing_bd12b64c.jpg
new file mode 100644
index 0000000..787cbf7
Binary files /dev/null and b/images/Failed+to+start+ringing_bd12b64c.jpg differ
diff --git a/images/Failed+to+start+ringing_d30237ca.jpg b/images/Failed+to+start+ringing_d30237ca.jpg
new file mode 100644
index 0000000..f6d630a
Binary files /dev/null and b/images/Failed+to+start+ringing_d30237ca.jpg differ
diff --git a/images/Filter+address(XX+XX+XX)+by+model+id(XX+XX+XX)+failed_+no+service_2853b108.jpg b/images/Filter+address(XX+XX+XX)+by+model+id(XX+XX+XX)+failed_+no+service_2853b108.jpg
new file mode 100644
index 0000000..87d898e
Binary files /dev/null and b/images/Filter+address(XX+XX+XX)+by+model+id(XX+XX+XX)+failed_+no+service_2853b108.jpg differ
diff --git a/images/Filter+address(XX+XX+XX)+by+model+id(XX+XX+XX)+failed_+no+service_7a74e0dc.jpg b/images/Filter+address(XX+XX+XX)+by+model+id(XX+XX+XX)+failed_+no+service_7a74e0dc.jpg
new file mode 100644
index 0000000..87d898e
Binary files /dev/null and b/images/Filter+address(XX+XX+XX)+by+model+id(XX+XX+XX)+failed_+no+service_7a74e0dc.jpg differ
diff --git a/images/Found+device+by+AK,+but+it+is+not+expected+to+advertise+Fast+Pair_32e9ca76.jpg b/images/Found+device+by+AK,+but+it+is+not+expected+to+advertise+Fast+Pair_32e9ca76.jpg
new file mode 100644
index 0000000..3cfa63c
Binary files /dev/null and b/images/Found+device+by+AK,+but+it+is+not+expected+to+advertise+Fast+Pair_32e9ca76.jpg differ
diff --git a/images/Found+device+by+AK,+but+it+is+not+expected+to+advertise+Fast+Pair_db8393cf.jpg b/images/Found+device+by+AK,+but+it+is+not+expected+to+advertise+Fast+Pair_db8393cf.jpg
new file mode 100644
index 0000000..d04e59a
Binary files /dev/null and b/images/Found+device+by+AK,+but+it+is+not+expected+to+advertise+Fast+Pair_db8393cf.jpg differ
diff --git a/images/Found+device+by+AK,+but+it+is+not+expected+to+advertise+Fast+Pair_e30430be.jpg b/images/Found+device+by+AK,+but+it+is+not+expected+to+advertise+Fast+Pair_e30430be.jpg
new file mode 100644
index 0000000..3cfa63c
Binary files /dev/null and b/images/Found+device+by+AK,+but+it+is+not+expected+to+advertise+Fast+Pair_e30430be.jpg differ
diff --git a/images/Found+device+by+AK,+but+it+is+not+expected+to+advertise+Fast+Pair_fd1ae77d.jpg b/images/Found+device+by+AK,+but+it+is+not+expected+to+advertise+Fast+Pair_fd1ae77d.jpg
new file mode 100644
index 0000000..d04e59a
Binary files /dev/null and b/images/Found+device+by+AK,+but+it+is+not+expected+to+advertise+Fast+Pair_fd1ae77d.jpg differ
diff --git a/images/GFPS+认证测试_6074400f.jpg b/images/GFPS+认证测试_6074400f.jpg
new file mode 100644
index 0000000..bca1846
Binary files /dev/null and b/images/GFPS+认证测试_6074400f.jpg differ
diff --git a/images/GFPS+认证测试_98869611.jpg b/images/GFPS+认证测试_98869611.jpg
new file mode 100644
index 0000000..bca1846
Binary files /dev/null and b/images/GFPS+认证测试_98869611.jpg differ
diff --git a/images/Get+account+key+fail_28264f54.jpg b/images/Get+account+key+fail_28264f54.jpg
new file mode 100644
index 0000000..da38ef9
Binary files /dev/null and b/images/Get+account+key+fail_28264f54.jpg differ
diff --git a/images/Get+account+key+fail_7516c002.jpg b/images/Get+account+key+fail_7516c002.jpg
new file mode 100644
index 0000000..da38ef9
Binary files /dev/null and b/images/Get+account+key+fail_7516c002.jpg differ
diff --git a/images/Locator+Tracker+Pair+device+fail_1a6fb2c9.jpg b/images/Locator+Tracker+Pair+device+fail_1a6fb2c9.jpg
new file mode 100644
index 0000000..eb1f4cd
Binary files /dev/null and b/images/Locator+Tracker+Pair+device+fail_1a6fb2c9.jpg differ
diff --git a/images/Locator+Tracker+Pair+device+fail_1fe5826d.jpg b/images/Locator+Tracker+Pair+device+fail_1fe5826d.jpg
new file mode 100644
index 0000000..eb1f4cd
Binary files /dev/null and b/images/Locator+Tracker+Pair+device+fail_1fe5826d.jpg differ
diff --git a/images/Locator+Tracker+Pair+device+fail_60910f85.jpg b/images/Locator+Tracker+Pair+device+fail_60910f85.jpg
new file mode 100644
index 0000000..d836b9f
Binary files /dev/null and b/images/Locator+Tracker+Pair+device+fail_60910f85.jpg differ
diff --git a/images/Locator+Tracker+Pair+device+fail_f462eb94.jpg b/images/Locator+Tracker+Pair+device+fail_f462eb94.jpg
new file mode 100644
index 0000000..d836b9f
Binary files /dev/null and b/images/Locator+Tracker+Pair+device+fail_f462eb94.jpg differ
diff --git a/images/Name+test+fail--提示_Write+name+to()by+initial+pair+fail__041ec819.jpg b/images/Name+test+fail--提示_Write+name+to()by+initial+pair+fail__041ec819.jpg
new file mode 100644
index 0000000..71d0444
Binary files /dev/null and b/images/Name+test+fail--提示_Write+name+to()by+initial+pair+fail__041ec819.jpg differ
diff --git a/images/Name+test+fail--提示_Write+name+to()by+initial+pair+fail__ca4acbbc.jpg b/images/Name+test+fail--提示_Write+name+to()by+initial+pair+fail__ca4acbbc.jpg
new file mode 100644
index 0000000..71d0444
Binary files /dev/null and b/images/Name+test+fail--提示_Write+name+to()by+initial+pair+fail__ca4acbbc.jpg differ
diff --git a/images/Pair+device+fail_533160fa.jpg b/images/Pair+device+fail_533160fa.jpg
new file mode 100644
index 0000000..ece6395
Binary files /dev/null and b/images/Pair+device+fail_533160fa.jpg differ
diff --git a/images/Pair+device+fail_567827d3.jpg b/images/Pair+device+fail_567827d3.jpg
new file mode 100644
index 0000000..7ea4ecc
Binary files /dev/null and b/images/Pair+device+fail_567827d3.jpg differ
diff --git a/images/Pair+device+fail_96c85301.jpg b/images/Pair+device+fail_96c85301.jpg
new file mode 100644
index 0000000..ece6395
Binary files /dev/null and b/images/Pair+device+fail_96c85301.jpg differ
diff --git a/images/Pair+device+fail_b1a10f36.jpg b/images/Pair+device+fail_b1a10f36.jpg
new file mode 100644
index 0000000..b7562ba
Binary files /dev/null and b/images/Pair+device+fail_b1a10f36.jpg differ
diff --git a/images/Pair+device+fail_dd043a6e.jpg b/images/Pair+device+fail_dd043a6e.jpg
new file mode 100644
index 0000000..b7562ba
Binary files /dev/null and b/images/Pair+device+fail_dd043a6e.jpg differ
diff --git a/images/Pair+device+fail_f7e178b4.jpg b/images/Pair+device+fail_f7e178b4.jpg
new file mode 100644
index 0000000..7ea4ecc
Binary files /dev/null and b/images/Pair+device+fail_f7e178b4.jpg differ
diff --git a/images/Pairing+Failed!+[Total+pairing+time+15490ms+_threshold+15000ms]_1e160fda.gif b/images/Pairing+Failed!+[Total+pairing+time+15490ms+_threshold+15000ms]_1e160fda.gif
new file mode 100644
index 0000000..cb4c386
Binary files /dev/null and b/images/Pairing+Failed!+[Total+pairing+time+15490ms+_threshold+15000ms]_1e160fda.gif differ
diff --git a/images/Pairing+Failed!+[Total+pairing+time+15490ms+_threshold+15000ms]_22812323.jpg b/images/Pairing+Failed!+[Total+pairing+time+15490ms+_threshold+15000ms]_22812323.jpg
new file mode 100644
index 0000000..765cef8
Binary files /dev/null and b/images/Pairing+Failed!+[Total+pairing+time+15490ms+_threshold+15000ms]_22812323.jpg differ
diff --git a/images/Pairing+Failed!+[Total+pairing+time+15490ms+_threshold+15000ms]_6fd5149c.jpg b/images/Pairing+Failed!+[Total+pairing+time+15490ms+_threshold+15000ms]_6fd5149c.jpg
new file mode 100644
index 0000000..b18ee07
Binary files /dev/null and b/images/Pairing+Failed!+[Total+pairing+time+15490ms+_threshold+15000ms]_6fd5149c.jpg differ
diff --git a/images/Pairing+Failed!+[Total+pairing+time+15490ms+_threshold+15000ms]_7f6414ce.jpg b/images/Pairing+Failed!+[Total+pairing+time+15490ms+_threshold+15000ms]_7f6414ce.jpg
new file mode 100644
index 0000000..765cef8
Binary files /dev/null and b/images/Pairing+Failed!+[Total+pairing+time+15490ms+_threshold+15000ms]_7f6414ce.jpg differ
diff --git a/images/Pairing+Failed!+[Total+pairing+time+15490ms+_threshold+15000ms]_875f0771.gif b/images/Pairing+Failed!+[Total+pairing+time+15490ms+_threshold+15000ms]_875f0771.gif
new file mode 100644
index 0000000..cb4c386
Binary files /dev/null and b/images/Pairing+Failed!+[Total+pairing+time+15490ms+_threshold+15000ms]_875f0771.gif differ
diff --git a/images/Pairing+Failed!+[Total+pairing+time+15490ms+_threshold+15000ms]_c106de87.gif b/images/Pairing+Failed!+[Total+pairing+time+15490ms+_threshold+15000ms]_c106de87.gif
new file mode 100644
index 0000000..cb4c386
Binary files /dev/null and b/images/Pairing+Failed!+[Total+pairing+time+15490ms+_threshold+15000ms]_c106de87.gif differ
diff --git a/images/Pairing+Failed!+[Total+pairing+time+15490ms+_threshold+15000ms]_ed259a5f.jpg b/images/Pairing+Failed!+[Total+pairing+time+15490ms+_threshold+15000ms]_ed259a5f.jpg
new file mode 100644
index 0000000..b18ee07
Binary files /dev/null and b/images/Pairing+Failed!+[Total+pairing+time+15490ms+_threshold+15000ms]_ed259a5f.jpg differ
diff --git a/images/Pairing+failed!+[Pair+time-out,+total+pair+time+21126+_+threshold+15000ms....]_3194d813.jpg b/images/Pairing+failed!+[Pair+time-out,+total+pair+time+21126+_+threshold+15000ms....]_3194d813.jpg
new file mode 100644
index 0000000..79732db
Binary files /dev/null and b/images/Pairing+failed!+[Pair+time-out,+total+pair+time+21126+_+threshold+15000ms....]_3194d813.jpg differ
diff --git a/images/Pairing+failed!+[Pair+time-out,+total+pair+time+21126+_+threshold+15000ms....]_41472ddc.jpg b/images/Pairing+failed!+[Pair+time-out,+total+pair+time+21126+_+threshold+15000ms....]_41472ddc.jpg
new file mode 100644
index 0000000..79732db
Binary files /dev/null and b/images/Pairing+failed!+[Pair+time-out,+total+pair+time+21126+_+threshold+15000ms....]_41472ddc.jpg differ
diff --git a/images/Pairing+failed!+[Pair+time-out]_2162d3fb.jpg b/images/Pairing+failed!+[Pair+time-out]_2162d3fb.jpg
new file mode 100644
index 0000000..502433d
Binary files /dev/null and b/images/Pairing+failed!+[Pair+time-out]_2162d3fb.jpg differ
diff --git a/images/Pairing+failed!+[Pair+time-out]_3904e36a.jpg b/images/Pairing+failed!+[Pair+time-out]_3904e36a.jpg
new file mode 100644
index 0000000..68d3c58
Binary files /dev/null and b/images/Pairing+failed!+[Pair+time-out]_3904e36a.jpg differ
diff --git a/images/Pairing+failed!+[Pair+time-out]_b02fb85d.jpg b/images/Pairing+failed!+[Pair+time-out]_b02fb85d.jpg
new file mode 100644
index 0000000..502433d
Binary files /dev/null and b/images/Pairing+failed!+[Pair+time-out]_b02fb85d.jpg differ
diff --git a/images/Pairing+failed!+[Pair+time-out]_e97013f4.jpg b/images/Pairing+failed!+[Pair+time-out]_e97013f4.jpg
new file mode 100644
index 0000000..68d3c58
Binary files /dev/null and b/images/Pairing+failed!+[Pair+time-out]_e97013f4.jpg differ
diff --git a/images/Pairing+failed!+[Pair+timeout+only+receive+correct+UUID+from+1+address......]_cb4e2bd7.jpg b/images/Pairing+failed!+[Pair+timeout+only+receive+correct+UUID+from+1+address......]_cb4e2bd7.jpg
new file mode 100644
index 0000000..8fcde3d
Binary files /dev/null and b/images/Pairing+failed!+[Pair+timeout+only+receive+correct+UUID+from+1+address......]_cb4e2bd7.jpg differ
diff --git a/images/Pairing+failed!+[Pair+timeout+only+receive+correct+UUID+from+1+address......]_f0b35d18.jpg b/images/Pairing+failed!+[Pair+timeout+only+receive+correct+UUID+from+1+address......]_f0b35d18.jpg
new file mode 100644
index 0000000..8fcde3d
Binary files /dev/null and b/images/Pairing+failed!+[Pair+timeout+only+receive+correct+UUID+from+1+address......]_f0b35d18.jpg differ
diff --git a/images/Pairing+failed!......KeyBasedPairingExtensionResponse+wrong+address+length_+1_bb126886.jpg b/images/Pairing+failed!......KeyBasedPairingExtensionResponse+wrong+address+length_+1_bb126886.jpg
new file mode 100644
index 0000000..b58f90f
Binary files /dev/null and b/images/Pairing+failed!......KeyBasedPairingExtensionResponse+wrong+address+length_+1_bb126886.jpg differ
diff --git a/images/Pairing+failed!......KeyBasedPairingExtensionResponse+wrong+address+length_+1_f9f4eb2a.jpg b/images/Pairing+failed!......KeyBasedPairingExtensionResponse+wrong+address+length_+1_f9f4eb2a.jpg
new file mode 100644
index 0000000..b58f90f
Binary files /dev/null and b/images/Pairing+failed!......KeyBasedPairingExtensionResponse+wrong+address+length_+1_f9f4eb2a.jpg differ
diff --git a/images/Pairing+failed![Pair+time-out,+Total+pairing+time+18020ms_threshold+12000ms]_0d478858.jpg b/images/Pairing+failed![Pair+time-out,+Total+pairing+time+18020ms_threshold+12000ms]_0d478858.jpg
new file mode 100644
index 0000000..cc4ed34
Binary files /dev/null and b/images/Pairing+failed![Pair+time-out,+Total+pairing+time+18020ms_threshold+12000ms]_0d478858.jpg differ
diff --git a/images/Pairing+failed![Pair+time-out,+Total+pairing+time+18020ms_threshold+12000ms]_18396df5.jpg b/images/Pairing+failed![Pair+time-out,+Total+pairing+time+18020ms_threshold+12000ms]_18396df5.jpg
new file mode 100644
index 0000000..6932c1c
Binary files /dev/null and b/images/Pairing+failed![Pair+time-out,+Total+pairing+time+18020ms_threshold+12000ms]_18396df5.jpg differ
diff --git a/images/Pairing+failed![Pair+time-out,+Total+pairing+time+18020ms_threshold+12000ms]_2fde1a26.jpg b/images/Pairing+failed![Pair+time-out,+Total+pairing+time+18020ms_threshold+12000ms]_2fde1a26.jpg
new file mode 100644
index 0000000..cc4ed34
Binary files /dev/null and b/images/Pairing+failed![Pair+time-out,+Total+pairing+time+18020ms_threshold+12000ms]_2fde1a26.jpg differ
diff --git a/images/Pairing+failed![Pair+time-out,+Total+pairing+time+18020ms_threshold+12000ms]_a5370631.jpg b/images/Pairing+failed![Pair+time-out,+Total+pairing+time+18020ms_threshold+12000ms]_a5370631.jpg
new file mode 100644
index 0000000..6932c1c
Binary files /dev/null and b/images/Pairing+failed![Pair+time-out,+Total+pairing+time+18020ms_threshold+12000ms]_a5370631.jpg differ
diff --git a/images/Pairing+failed![Pair+time-out,+Total+pairing+time+18020ms_threshold+12000ms]_b98656e2.jpg b/images/Pairing+failed![Pair+time-out,+Total+pairing+time+18020ms_threshold+12000ms]_b98656e2.jpg
new file mode 100644
index 0000000..51da48e
Binary files /dev/null and b/images/Pairing+failed![Pair+time-out,+Total+pairing+time+18020ms_threshold+12000ms]_b98656e2.jpg differ
diff --git a/images/Pairing+failed![Pair+time-out,+Total+pairing+time+18020ms_threshold+12000ms]_d9d96011.jpg b/images/Pairing+failed![Pair+time-out,+Total+pairing+time+18020ms_threshold+12000ms]_d9d96011.jpg
new file mode 100644
index 0000000..51da48e
Binary files /dev/null and b/images/Pairing+failed![Pair+time-out,+Total+pairing+time+18020ms_threshold+12000ms]_d9d96011.jpg differ
diff --git a/images/Pairing+failed！[Pair+time-out]_43e7d89f.jpg b/images/Pairing+failed！[Pair+time-out]_43e7d89f.jpg
new file mode 100644
index 0000000..fb6ade7
Binary files /dev/null and b/images/Pairing+failed！[Pair+time-out]_43e7d89f.jpg differ
diff --git a/images/Pairing+failed！[Pair+time-out]_d717feaa.jpg b/images/Pairing+failed！[Pair+time-out]_d717feaa.jpg
new file mode 100644
index 0000000..fb6ade7
Binary files /dev/null and b/images/Pairing+failed！[Pair+time-out]_d717feaa.jpg differ
diff --git a/images/Pairing+process+error_+Reason_+Is+connected+false_71b58462.jpg b/images/Pairing+process+error_+Reason_+Is+connected+false_71b58462.jpg
new file mode 100644
index 0000000..76fc037
Binary files /dev/null and b/images/Pairing+process+error_+Reason_+Is+connected+false_71b58462.jpg differ
diff --git a/images/Pairing+process+error_+Reason_+Is+connected+false_912b34d0.jpg b/images/Pairing+process+error_+Reason_+Is+connected+false_912b34d0.jpg
new file mode 100644
index 0000000..76fc037
Binary files /dev/null and b/images/Pairing+process+error_+Reason_+Is+connected+false_912b34d0.jpg differ
diff --git a/images/Public+Key+Based+Pairing+Request+in+non+discoverable+mode_20d79a54.jpg b/images/Public+Key+Based+Pairing+Request+in+non+discoverable+mode_20d79a54.jpg
new file mode 100644
index 0000000..64e0066
Binary files /dev/null and b/images/Public+Key+Based+Pairing+Request+in+non+discoverable+mode_20d79a54.jpg differ
diff --git a/images/Public+Key+Based+Pairing+Request+in+non+discoverable+mode_83045e99.jpg b/images/Public+Key+Based+Pairing+Request+in+non+discoverable+mode_83045e99.jpg
new file mode 100644
index 0000000..64e0066
Binary files /dev/null and b/images/Public+Key+Based+Pairing+Request+in+non+discoverable+mode_83045e99.jpg differ
diff --git a/images/Reason_+Test+fail+after+connectioning_2f9950b3.jpg b/images/Reason_+Test+fail+after+connectioning_2f9950b3.jpg
new file mode 100644
index 0000000..7053a70
Binary files /dev/null and b/images/Reason_+Test+fail+after+connectioning_2f9950b3.jpg differ
diff --git a/images/Reason_+Test+fail+after+connectioning_7dc03124.jpg b/images/Reason_+Test+fail+after+connectioning_7dc03124.jpg
new file mode 100644
index 0000000..7053a70
Binary files /dev/null and b/images/Reason_+Test+fail+after+connectioning_7dc03124.jpg differ
diff --git a/images/Reason_+device+not+found+by+EID_1c0139d1.jpg b/images/Reason_+device+not+found+by+EID_1c0139d1.jpg
new file mode 100644
index 0000000..6c88cec
Binary files /dev/null and b/images/Reason_+device+not+found+by+EID_1c0139d1.jpg differ
diff --git a/images/Reason_+device+not+found+by+EID_cfc48bfc.jpg b/images/Reason_+device+not+found+by+EID_cfc48bfc.jpg
new file mode 100644
index 0000000..6c88cec
Binary files /dev/null and b/images/Reason_+device+not+found+by+EID_cfc48bfc.jpg differ
diff --git a/images/Reason_+wrong+value+of+'unwanted+tracking+protection+mode'+in+Hashed+Flags_disabled_3af63a7e.jpg b/images/Reason_+wrong+value+of+'unwanted+tracking+protection+mode'+in+Hashed+Flags_disabled_3af63a7e.jpg
new file mode 100644
index 0000000..fb9ca30
Binary files /dev/null and b/images/Reason_+wrong+value+of+'unwanted+tracking+protection+mode'+in+Hashed+Flags_disabled_3af63a7e.jpg differ
diff --git a/images/Reason_+wrong+value+of+'unwanted+tracking+protection+mode'+in+Hashed+Flags_disabled_79fdf8cf.jpg b/images/Reason_+wrong+value+of+'unwanted+tracking+protection+mode'+in+Hashed+Flags_disabled_79fdf8cf.jpg
new file mode 100644
index 0000000..fb9ca30
Binary files /dev/null and b/images/Reason_+wrong+value+of+'unwanted+tracking+protection+mode'+in+Hashed+Flags_disabled_79fdf8cf.jpg differ
diff --git a/images/Reason_+附耳没有enable+lea+adv_51768683.jpg b/images/Reason_+附耳没有enable+lea+adv_51768683.jpg
new file mode 100644
index 0000000..8619a14
Binary files /dev/null and b/images/Reason_+附耳没有enable+lea+adv_51768683.jpg differ
diff --git a/images/Reason_+附耳没有enable+lea+adv_7554e1e0.jpg b/images/Reason_+附耳没有enable+lea+adv_7554e1e0.jpg
new file mode 100644
index 0000000..8619a14
Binary files /dev/null and b/images/Reason_+附耳没有enable+lea+adv_7554e1e0.jpg differ
diff --git a/images/Reason_+附耳没有enable+lea+adv_b29c8358.jpg b/images/Reason_+附耳没有enable+lea+adv_b29c8358.jpg
new file mode 100644
index 0000000..9c3ee71
Binary files /dev/null and b/images/Reason_+附耳没有enable+lea+adv_b29c8358.jpg differ
diff --git a/images/Reason_+附耳没有enable+lea+adv_f0612172.jpg b/images/Reason_+附耳没有enable+lea+adv_f0612172.jpg
new file mode 100644
index 0000000..9c3ee71
Binary files /dev/null and b/images/Reason_+附耳没有enable+lea+adv_f0612172.jpg differ
diff --git a/images/Reason_Initialpair附耳start+lea+adv的时候还未获取SIRK_60456d02.gif b/images/Reason_Initialpair附耳start+lea+adv的时候还未获取SIRK_60456d02.gif
new file mode 100644
index 0000000..cb4c386
Binary files /dev/null and b/images/Reason_Initialpair附耳start+lea+adv的时候还未获取SIRK_60456d02.gif differ
diff --git a/images/Reason_Initialpair附耳start+lea+adv的时候还未获取SIRK_60c3ed38.gif b/images/Reason_Initialpair附耳start+lea+adv的时候还未获取SIRK_60c3ed38.gif
new file mode 100644
index 0000000..cb4c386
Binary files /dev/null and b/images/Reason_Initialpair附耳start+lea+adv的时候还未获取SIRK_60c3ed38.gif differ
diff --git a/images/Reason_Initialpair附耳start+lea+adv的时候还未获取SIRK_c01ffb94.gif b/images/Reason_Initialpair附耳start+lea+adv的时候还未获取SIRK_c01ffb94.gif
new file mode 100644
index 0000000..cb4c386
Binary files /dev/null and b/images/Reason_Initialpair附耳start+lea+adv的时候还未获取SIRK_c01ffb94.gif differ
diff --git a/images/Reason：Observed+standard+deviation+is+too+low,+........_0e689693.jpg b/images/Reason：Observed+standard+deviation+is+too+low,+........_0e689693.jpg
new file mode 100644
index 0000000..18038d6
Binary files /dev/null and b/images/Reason：Observed+standard+deviation+is+too+low,+........_0e689693.jpg differ
diff --git a/images/Reason：Observed+standard+deviation+is+too+low,+........_1ef0a06d.jpg b/images/Reason：Observed+standard+deviation+is+too+low,+........_1ef0a06d.jpg
new file mode 100644
index 0000000..703ce7a
Binary files /dev/null and b/images/Reason：Observed+standard+deviation+is+too+low,+........_1ef0a06d.jpg differ
diff --git a/images/Reason：Observed+standard+deviation+is+too+low,+........_2911bcbd.jpg b/images/Reason：Observed+standard+deviation+is+too+low,+........_2911bcbd.jpg
new file mode 100644
index 0000000..703ce7a
Binary files /dev/null and b/images/Reason：Observed+standard+deviation+is+too+low,+........_2911bcbd.jpg differ
diff --git a/images/Reason：Observed+standard+deviation+is+too+low,+........_c043a434.jpg b/images/Reason：Observed+standard+deviation+is+too+low,+........_c043a434.jpg
new file mode 100644
index 0000000..18038d6
Binary files /dev/null and b/images/Reason：Observed+standard+deviation+is+too+low,+........_c043a434.jpg differ
diff --git a/images/Receive+unexpected+profile+connection+android.blurtooth.a2dp.profile...._32a8069c.jpg b/images/Receive+unexpected+profile+connection+android.blurtooth.a2dp.profile...._32a8069c.jpg
new file mode 100644
index 0000000..578457f
Binary files /dev/null and b/images/Receive+unexpected+profile+connection+android.blurtooth.a2dp.profile...._32a8069c.jpg differ
diff --git a/images/Receive+unexpected+profile+connection+android.blurtooth.a2dp.profile...._5b7635ed.jpg b/images/Receive+unexpected+profile+connection+android.blurtooth.a2dp.profile...._5b7635ed.jpg
new file mode 100644
index 0000000..8819746
Binary files /dev/null and b/images/Receive+unexpected+profile+connection+android.blurtooth.a2dp.profile...._5b7635ed.jpg differ
diff --git a/images/Receive+unexpected+profile+connection+android.blurtooth.a2dp.profile...._8377c920.jpg b/images/Receive+unexpected+profile+connection+android.blurtooth.a2dp.profile...._8377c920.jpg
new file mode 100644
index 0000000..578457f
Binary files /dev/null and b/images/Receive+unexpected+profile+connection+android.blurtooth.a2dp.profile...._8377c920.jpg differ
diff --git a/images/Receive+unexpected+profile+connection+android.blurtooth.a2dp.profile...._c9488e68.jpg b/images/Receive+unexpected+profile+connection+android.blurtooth.a2dp.profile...._c9488e68.jpg
new file mode 100644
index 0000000..8819746
Binary files /dev/null and b/images/Receive+unexpected+profile+connection+android.blurtooth.a2dp.profile...._c9488e68.jpg differ
diff --git a/images/Retroactive+Pair+test+fail--提示_Get+account+key+fail__0be3be1a.jpg b/images/Retroactive+Pair+test+fail--提示_Get+account+key+fail__0be3be1a.jpg
new file mode 100644
index 0000000..6137ef4
Binary files /dev/null and b/images/Retroactive+Pair+test+fail--提示_Get+account+key+fail__0be3be1a.jpg differ
diff --git a/images/Retroactive+Pair+test+fail--提示_Get+account+key+fail__21ae298d.jpg b/images/Retroactive+Pair+test+fail--提示_Get+account+key+fail__21ae298d.jpg
new file mode 100644
index 0000000..cea452c
Binary files /dev/null and b/images/Retroactive+Pair+test+fail--提示_Get+account+key+fail__21ae298d.jpg differ
diff --git a/images/Retroactive+Pair+test+fail--提示_Get+account+key+fail__4409b8c3.jpg b/images/Retroactive+Pair+test+fail--提示_Get+account+key+fail__4409b8c3.jpg
new file mode 100644
index 0000000..cea452c
Binary files /dev/null and b/images/Retroactive+Pair+test+fail--提示_Get+account+key+fail__4409b8c3.jpg differ
diff --git a/images/Retroactive+Pair+test+fail--提示_Get+account+key+fail__f016f06c.jpg b/images/Retroactive+Pair+test+fail--提示_Get+account+key+fail__f016f06c.jpg
new file mode 100644
index 0000000..6137ef4
Binary files /dev/null and b/images/Retroactive+Pair+test+fail--提示_Get+account+key+fail__f016f06c.jpg differ
diff --git a/images/Retroactive+Pair之后没办法使用响铃功能_20931516.jpg b/images/Retroactive+Pair之后没办法使用响铃功能_20931516.jpg
new file mode 100644
index 0000000..0d8bb5f
Binary files /dev/null and b/images/Retroactive+Pair之后没办法使用响铃功能_20931516.jpg differ
diff --git a/images/Retroactive+Pair之后没办法使用响铃功能_54b1c7c0.jpg b/images/Retroactive+Pair之后没办法使用响铃功能_54b1c7c0.jpg
new file mode 100644
index 0000000..d1b6dda
Binary files /dev/null and b/images/Retroactive+Pair之后没办法使用响铃功能_54b1c7c0.jpg differ
diff --git a/images/Retroactive+Pair之后没办法使用响铃功能_8581f0bf.jpg b/images/Retroactive+Pair之后没办法使用响铃功能_8581f0bf.jpg
new file mode 100644
index 0000000..d1b6dda
Binary files /dev/null and b/images/Retroactive+Pair之后没办法使用响铃功能_8581f0bf.jpg differ
diff --git a/images/Retroactive+Pair之后没办法使用响铃功能_8f6cc48d.jpg b/images/Retroactive+Pair之后没办法使用响铃功能_8f6cc48d.jpg
new file mode 100644
index 0000000..0d8bb5f
Binary files /dev/null and b/images/Retroactive+Pair之后没办法使用响铃功能_8f6cc48d.jpg differ
diff --git a/images/Retroactive+Pair之后没办法使用响铃功能_a8e113bd.jpg b/images/Retroactive+Pair之后没办法使用响铃功能_a8e113bd.jpg
new file mode 100644
index 0000000..c9147cc
Binary files /dev/null and b/images/Retroactive+Pair之后没办法使用响铃功能_a8e113bd.jpg differ
diff --git a/images/Retroactive+Pair之后没办法使用响铃功能_b494c24b.jpg b/images/Retroactive+Pair之后没办法使用响铃功能_b494c24b.jpg
new file mode 100644
index 0000000..c9147cc
Binary files /dev/null and b/images/Retroactive+Pair之后没办法使用响铃功能_b494c24b.jpg differ
diff --git a/images/Test+case+5_Upgrade+from+Find+My+Accessories+to+Finder+fail_0d5b0bb9.jpg b/images/Test+case+5_Upgrade+from+Find+My+Accessories+to+Finder+fail_0d5b0bb9.jpg
new file mode 100644
index 0000000..6425789
Binary files /dev/null and b/images/Test+case+5_Upgrade+from+Find+My+Accessories+to+Finder+fail_0d5b0bb9.jpg differ
diff --git a/images/Test+case+5_Upgrade+from+Find+My+Accessories+to+Finder+fail_21e74771.jpg b/images/Test+case+5_Upgrade+from+Find+My+Accessories+to+Finder+fail_21e74771.jpg
new file mode 100644
index 0000000..2478d9c
Binary files /dev/null and b/images/Test+case+5_Upgrade+from+Find+My+Accessories+to+Finder+fail_21e74771.jpg differ
diff --git a/images/Test+case+5_Upgrade+from+Find+My+Accessories+to+Finder+fail_42c5d501.jpg b/images/Test+case+5_Upgrade+from+Find+My+Accessories+to+Finder+fail_42c5d501.jpg
new file mode 100644
index 0000000..2478d9c
Binary files /dev/null and b/images/Test+case+5_Upgrade+from+Find+My+Accessories+to+Finder+fail_42c5d501.jpg differ
diff --git a/images/Test+case+5_Upgrade+from+Find+My+Accessories+to+Finder+fail_63a2a09a.jpg b/images/Test+case+5_Upgrade+from+Find+My+Accessories+to+Finder+fail_63a2a09a.jpg
new file mode 100644
index 0000000..6425789
Binary files /dev/null and b/images/Test+case+5_Upgrade+from+Find+My+Accessories+to+Finder+fail_63a2a09a.jpg differ
diff --git a/images/Test+case+6_+Clock+sync+fail_6a35003f.jpg b/images/Test+case+6_+Clock+sync+fail_6a35003f.jpg
new file mode 100644
index 0000000..ee79027
Binary files /dev/null and b/images/Test+case+6_+Clock+sync+fail_6a35003f.jpg differ
diff --git a/images/Test+case+6_+Clock+sync+fail_7a4b3b1c.jpg b/images/Test+case+6_+Clock+sync+fail_7a4b3b1c.jpg
new file mode 100644
index 0000000..69330f4
Binary files /dev/null and b/images/Test+case+6_+Clock+sync+fail_7a4b3b1c.jpg differ
diff --git a/images/Test+case+6_+Clock+sync+fail_8a2a4e8c.jpg b/images/Test+case+6_+Clock+sync+fail_8a2a4e8c.jpg
new file mode 100644
index 0000000..ee79027
Binary files /dev/null and b/images/Test+case+6_+Clock+sync+fail_8a2a4e8c.jpg differ
diff --git a/images/Test+case+6_+Clock+sync+fail_d56180fe.jpg b/images/Test+case+6_+Clock+sync+fail_d56180fe.jpg
new file mode 100644
index 0000000..69330f4
Binary files /dev/null and b/images/Test+case+6_+Clock+sync+fail_d56180fe.jpg differ
diff --git a/images/Test+case+6_+Clock+sync+fail_d8a5e189.jpg b/images/Test+case+6_+Clock+sync+fail_d8a5e189.jpg
new file mode 100644
index 0000000..680d374
Binary files /dev/null and b/images/Test+case+6_+Clock+sync+fail_d8a5e189.jpg differ
diff --git a/images/Test+case+6_+Clock+sync+fail_e6942738.jpg b/images/Test+case+6_+Clock+sync+fail_e6942738.jpg
new file mode 100644
index 0000000..680d374
Binary files /dev/null and b/images/Test+case+6_+Clock+sync+fail_e6942738.jpg differ
diff --git a/images/Test+case+8-2_+Unwanted+Tracking+Prevention+without+network+connection注意事项_8fc2b006.jpg b/images/Test+case+8-2_+Unwanted+Tracking+Prevention+without+network+connection注意事项_8fc2b006.jpg
new file mode 100644
index 0000000..3828c57
Binary files /dev/null and b/images/Test+case+8-2_+Unwanted+Tracking+Prevention+without+network+connection注意事项_8fc2b006.jpg differ
diff --git a/images/Test+case+8-2_+Unwanted+Tracking+Prevention+without+network+connection注意事项_97842b1e.jpg b/images/Test+case+8-2_+Unwanted+Tracking+Prevention+without+network+connection注意事项_97842b1e.jpg
new file mode 100644
index 0000000..3828c57
Binary files /dev/null and b/images/Test+case+8-2_+Unwanted+Tracking+Prevention+without+network+connection注意事项_97842b1e.jpg differ
diff --git a/images/Test+case+8-2_+Unwanted+Tracking+Prevention+without+network+connection注意事项_adb870c3.jpg b/images/Test+case+8-2_+Unwanted+Tracking+Prevention+without+network+connection注意事项_adb870c3.jpg
new file mode 100644
index 0000000..26e468d
Binary files /dev/null and b/images/Test+case+8-2_+Unwanted+Tracking+Prevention+without+network+connection注意事项_adb870c3.jpg differ
diff --git a/images/Test+case+8-2_+Unwanted+Tracking+Prevention+without+network+connection注意事项_e540d1da.jpg b/images/Test+case+8-2_+Unwanted+Tracking+Prevention+without+network+connection注意事项_e540d1da.jpg
new file mode 100644
index 0000000..26e468d
Binary files /dev/null and b/images/Test+case+8-2_+Unwanted+Tracking+Prevention+without+network+connection注意事项_e540d1da.jpg differ
diff --git a/images/[legacy+GFPS][Retroactive+Pair+fail]+RFCOMM+连上之后设备端送给手机端的BLE地址不对_22ad18ed.jpg b/images/[legacy+GFPS][Retroactive+Pair+fail]+RFCOMM+连上之后设备端送给手机端的BLE地址不对_22ad18ed.jpg
new file mode 100644
index 0000000..545610f
Binary files /dev/null and b/images/[legacy+GFPS][Retroactive+Pair+fail]+RFCOMM+连上之后设备端送给手机端的BLE地址不对_22ad18ed.jpg differ
diff --git a/images/[legacy+GFPS][Retroactive+Pair+fail]+RFCOMM+连上之后设备端送给手机端的BLE地址不对_ab0c4721.jpg b/images/[legacy+GFPS][Retroactive+Pair+fail]+RFCOMM+连上之后设备端送给手机端的BLE地址不对_ab0c4721.jpg
new file mode 100644
index 0000000..545610f
Binary files /dev/null and b/images/[legacy+GFPS][Retroactive+Pair+fail]+RFCOMM+连上之后设备端送给手机端的BLE地址不对_ab0c4721.jpg differ
diff --git a/images/auto+pair+test+fail--+_fail+to+scan+model+id+XXXX__071a12bf.jpg b/images/auto+pair+test+fail--+_fail+to+scan+model+id+XXXX__071a12bf.jpg
new file mode 100644
index 0000000..cea452c
Binary files /dev/null and b/images/auto+pair+test+fail--+_fail+to+scan+model+id+XXXX__071a12bf.jpg differ
diff --git a/images/auto+pair+test+fail--+_fail+to+scan+model+id+XXXX__09eb4c42.jpg b/images/auto+pair+test+fail--+_fail+to+scan+model+id+XXXX__09eb4c42.jpg
new file mode 100644
index 0000000..a3fb6ce
Binary files /dev/null and b/images/auto+pair+test+fail--+_fail+to+scan+model+id+XXXX__09eb4c42.jpg differ
diff --git a/images/auto+pair+test+fail--+_fail+to+scan+model+id+XXXX__405a30e0.jpg b/images/auto+pair+test+fail--+_fail+to+scan+model+id+XXXX__405a30e0.jpg
new file mode 100644
index 0000000..a3fb6ce
Binary files /dev/null and b/images/auto+pair+test+fail--+_fail+to+scan+model+id+XXXX__405a30e0.jpg differ
diff --git a/images/auto+pair+test+fail--+_fail+to+scan+model+id+XXXX__5a7182bf.jpg b/images/auto+pair+test+fail--+_fail+to+scan+model+id+XXXX__5a7182bf.jpg
new file mode 100644
index 0000000..cea452c
Binary files /dev/null and b/images/auto+pair+test+fail--+_fail+to+scan+model+id+XXXX__5a7182bf.jpg differ
diff --git a/images/auto+pair+test+fail--+_fail+to+scan+model+id+XXXX__7661acda.jpg b/images/auto+pair+test+fail--+_fail+to+scan+model+id+XXXX__7661acda.jpg
new file mode 100644
index 0000000..6137ef4
Binary files /dev/null and b/images/auto+pair+test+fail--+_fail+to+scan+model+id+XXXX__7661acda.jpg differ
diff --git a/images/auto+pair+test+fail--+_fail+to+scan+model+id+XXXX__d3d60dbf.jpg b/images/auto+pair+test+fail--+_fail+to+scan+model+id+XXXX__d3d60dbf.jpg
new file mode 100644
index 0000000..6137ef4
Binary files /dev/null and b/images/auto+pair+test+fail--+_fail+to+scan+model+id+XXXX__d3d60dbf.jpg differ
diff --git a/images/end+to+end_+A+timeout+occured+when+processing+CONNECT..._8c07efe8.jpg b/images/end+to+end_+A+timeout+occured+when+processing+CONNECT..._8c07efe8.jpg
new file mode 100644
index 0000000..955c798
Binary files /dev/null and b/images/end+to+end_+A+timeout+occured+when+processing+CONNECT..._8c07efe8.jpg differ
diff --git a/images/end+to+end_+A+timeout+occured+when+processing+CONNECT..._914468a0.jpg b/images/end+to+end_+A+timeout+occured+when+processing+CONNECT..._914468a0.jpg
new file mode 100644
index 0000000..955c798
Binary files /dev/null and b/images/end+to+end_+A+timeout+occured+when+processing+CONNECT..._914468a0.jpg differ
diff --git a/images/end+to+end_+A+timeout+occured+when+processing+CONNECT..._95fa876d.jpg b/images/end+to+end_+A+timeout+occured+when+processing+CONNECT..._95fa876d.jpg
new file mode 100644
index 0000000..ec0d4aa
Binary files /dev/null and b/images/end+to+end_+A+timeout+occured+when+processing+CONNECT..._95fa876d.jpg differ
diff --git a/images/end+to+end_+A+timeout+occured+when+processing+CONNECT..._fdb2822a.jpg b/images/end+to+end_+A+timeout+occured+when+processing+CONNECT..._fdb2822a.jpg
new file mode 100644
index 0000000..ec0d4aa
Binary files /dev/null and b/images/end+to+end_+A+timeout+occured+when+processing+CONNECT..._fdb2822a.jpg differ
diff --git a/images/finder响铃失败_981a2591.jpg b/images/finder响铃失败_981a2591.jpg
new file mode 100644
index 0000000..74d984b
Binary files /dev/null and b/images/finder响铃失败_981a2591.jpg differ
diff --git a/images/finder响铃失败_dcd873ab.jpg b/images/finder响铃失败_dcd873ab.jpg
new file mode 100644
index 0000000..74d984b
Binary files /dev/null and b/images/finder响铃失败_dcd873ab.jpg differ
diff --git a/images/gfps_handle_char_kbp_+failed,+result+3_4d30771c.jpg b/images/gfps_handle_char_kbp_+failed,+result+3_4d30771c.jpg
new file mode 100644
index 0000000..a2c936f
Binary files /dev/null and b/images/gfps_handle_char_kbp_+failed,+result+3_4d30771c.jpg differ
diff --git a/images/gfps_handle_char_kbp_+failed,+result+3_eddd7671.jpg b/images/gfps_handle_char_kbp_+failed,+result+3_eddd7671.jpg
new file mode 100644
index 0000000..a2c936f
Binary files /dev/null and b/images/gfps_handle_char_kbp_+failed,+result+3_eddd7671.jpg differ
diff --git a/images/initial+pair，手机不来连bredr_06371dd8.jpg b/images/initial+pair，手机不来连bredr_06371dd8.jpg
new file mode 100644
index 0000000..c63af54
Binary files /dev/null and b/images/initial+pair，手机不来连bredr_06371dd8.jpg differ
diff --git a/images/initial+pair，手机不来连bredr_704370ee.jpg b/images/initial+pair，手机不来连bredr_704370ee.jpg
new file mode 100644
index 0000000..f27c60d
Binary files /dev/null and b/images/initial+pair，手机不来连bredr_704370ee.jpg differ
diff --git a/images/initial+pair，手机不来连bredr_9614802d.jpg b/images/initial+pair，手机不来连bredr_9614802d.jpg
new file mode 100644
index 0000000..c63af54
Binary files /dev/null and b/images/initial+pair，手机不来连bredr_9614802d.jpg differ
diff --git a/images/initial+pair，手机不来连bredr_c65bc64f.jpg b/images/initial+pair，手机不来连bredr_c65bc64f.jpg
new file mode 100644
index 0000000..f27c60d
Binary files /dev/null and b/images/initial+pair，手机不来连bredr_c65bc64f.jpg differ
diff --git a/images/model_id+注册_1e57e3fd.jpg b/images/model_id+注册_1e57e3fd.jpg
new file mode 100644
index 0000000..a8d35a8
Binary files /dev/null and b/images/model_id+注册_1e57e3fd.jpg differ
diff --git a/images/model_id+注册_3fab1d71.jpg b/images/model_id+注册_3fab1d71.jpg
new file mode 100644
index 0000000..a74ded6
Binary files /dev/null and b/images/model_id+注册_3fab1d71.jpg differ
diff --git a/images/model_id+注册_59121f4f.jpg b/images/model_id+注册_59121f4f.jpg
new file mode 100644
index 0000000..d4b1136
Binary files /dev/null and b/images/model_id+注册_59121f4f.jpg differ
diff --git a/images/model_id+注册_78f04ded.jpg b/images/model_id+注册_78f04ded.jpg
new file mode 100644
index 0000000..56a8239
Binary files /dev/null and b/images/model_id+注册_78f04ded.jpg differ
diff --git a/images/model_id+注册_7a603da7.jpg b/images/model_id+注册_7a603da7.jpg
new file mode 100644
index 0000000..404f746
Binary files /dev/null and b/images/model_id+注册_7a603da7.jpg differ
diff --git a/images/model_id+注册_8e7c39b8.jpg b/images/model_id+注册_8e7c39b8.jpg
new file mode 100644
index 0000000..ec339e1
Binary files /dev/null and b/images/model_id+注册_8e7c39b8.jpg differ
diff --git a/images/model_id+注册_8e8431ca.jpg b/images/model_id+注册_8e8431ca.jpg
new file mode 100644
index 0000000..404f746
Binary files /dev/null and b/images/model_id+注册_8e8431ca.jpg differ
diff --git a/images/model_id+注册_9037204c.jpg b/images/model_id+注册_9037204c.jpg
new file mode 100644
index 0000000..a74ded6
Binary files /dev/null and b/images/model_id+注册_9037204c.jpg differ
diff --git a/images/model_id+注册_99ded9ae.jpg b/images/model_id+注册_99ded9ae.jpg
new file mode 100644
index 0000000..ec339e1
Binary files /dev/null and b/images/model_id+注册_99ded9ae.jpg differ
diff --git a/images/model_id+注册_9e278c59.jpg b/images/model_id+注册_9e278c59.jpg
new file mode 100644
index 0000000..d4b1136
Binary files /dev/null and b/images/model_id+注册_9e278c59.jpg differ
diff --git a/images/model_id+注册_b5e48457.jpg b/images/model_id+注册_b5e48457.jpg
new file mode 100644
index 0000000..56a8239
Binary files /dev/null and b/images/model_id+注册_b5e48457.jpg differ
diff --git a/images/model_id+注册_fdcce585.jpg b/images/model_id+注册_fdcce585.jpg
new file mode 100644
index 0000000..a8d35a8
Binary files /dev/null and b/images/model_id+注册_fdcce585.jpg differ
diff --git a/images/ota成功之后，弹窗出现，如果不及时点击弹窗，弹窗显示几秒后就会消失_014a0b42.jpg b/images/ota成功之后，弹窗出现，如果不及时点击弹窗，弹窗显示几秒后就会消失_014a0b42.jpg
new file mode 100644
index 0000000..57c1545
Binary files /dev/null and b/images/ota成功之后，弹窗出现，如果不及时点击弹窗，弹窗显示几秒后就会消失_014a0b42.jpg differ
diff --git a/images/ota成功之后，弹窗出现，如果不及时点击弹窗，弹窗显示几秒后就会消失_29c38b69.jpg b/images/ota成功之后，弹窗出现，如果不及时点击弹窗，弹窗显示几秒后就会消失_29c38b69.jpg
new file mode 100644
index 0000000..57c1545
Binary files /dev/null and b/images/ota成功之后，弹窗出现，如果不及时点击弹窗，弹窗显示几秒后就会消失_29c38b69.jpg differ
diff --git a/images/pair+with+xx_xx_xx_xx_xx_xx+fail_500aa0ca.jpg b/images/pair+with+xx_xx_xx_xx_xx_xx+fail_500aa0ca.jpg
new file mode 100644
index 0000000..c53f384
Binary files /dev/null and b/images/pair+with+xx_xx_xx_xx_xx_xx+fail_500aa0ca.jpg differ
diff --git a/images/pair+with+xx_xx_xx_xx_xx_xx+fail_f6feb7d8.jpg b/images/pair+with+xx_xx_xx_xx_xx_xx+fail_f6feb7d8.jpg
new file mode 100644
index 0000000..c53f384
Binary files /dev/null and b/images/pair+with+xx_xx_xx_xx_xx_xx+fail_f6feb7d8.jpg differ
diff --git a/images/provisioning+for+non-owner+fail--_Scan+the+device+by+model+id_+fail_86e68b85.jpg b/images/provisioning+for+non-owner+fail--_Scan+the+device+by+model+id_+fail_86e68b85.jpg
new file mode 100644
index 0000000..4f5445a
Binary files /dev/null and b/images/provisioning+for+non-owner+fail--_Scan+the+device+by+model+id_+fail_86e68b85.jpg differ
diff --git a/images/provisioning+for+non-owner+fail--_Scan+the+device+by+model+id_+fail_ffb43a3a.jpg b/images/provisioning+for+non-owner+fail--_Scan+the+device+by+model+id_+fail_ffb43a3a.jpg
new file mode 100644
index 0000000..4f5445a
Binary files /dev/null and b/images/provisioning+for+non-owner+fail--_Scan+the+device+by+model+id_+fail_ffb43a3a.jpg differ
diff --git a/images/provisioning+for+non-owner+fail--_invalid+authentication+not+rejected__0b737d15.jpg b/images/provisioning+for+non-owner+fail--_invalid+authentication+not+rejected__0b737d15.jpg
new file mode 100644
index 0000000..4c578c7
Binary files /dev/null and b/images/provisioning+for+non-owner+fail--_invalid+authentication+not+rejected__0b737d15.jpg differ
diff --git a/images/provisioning+for+non-owner+fail--_invalid+authentication+not+rejected__4e961f1f.jpg b/images/provisioning+for+non-owner+fail--_invalid+authentication+not+rejected__4e961f1f.jpg
new file mode 100644
index 0000000..1afa45f
Binary files /dev/null and b/images/provisioning+for+non-owner+fail--_invalid+authentication+not+rejected__4e961f1f.jpg differ
diff --git a/images/provisioning+for+non-owner+fail--_invalid+authentication+not+rejected__5e01f20b.jpg b/images/provisioning+for+non-owner+fail--_invalid+authentication+not+rejected__5e01f20b.jpg
new file mode 100644
index 0000000..4c578c7
Binary files /dev/null and b/images/provisioning+for+non-owner+fail--_invalid+authentication+not+rejected__5e01f20b.jpg differ
diff --git a/images/provisioning+for+non-owner+fail--_invalid+authentication+not+rejected__70d87709.jpg b/images/provisioning+for+non-owner+fail--_invalid+authentication+not+rejected__70d87709.jpg
new file mode 100644
index 0000000..1afa45f
Binary files /dev/null and b/images/provisioning+for+non-owner+fail--_invalid+authentication+not+rejected__70d87709.jpg differ
diff --git a/images/provisioning+for+non-owner+fail--_invalid+authentication+not+rejected__8a468fa7.jpg b/images/provisioning+for+non-owner+fail--_invalid+authentication+not+rejected__8a468fa7.jpg
new file mode 100644
index 0000000..6508546
Binary files /dev/null and b/images/provisioning+for+non-owner+fail--_invalid+authentication+not+rejected__8a468fa7.jpg differ
diff --git a/images/provisioning+for+non-owner+fail--_invalid+authentication+not+rejected__a1ef8dca.jpg b/images/provisioning+for+non-owner+fail--_invalid+authentication+not+rejected__a1ef8dca.jpg
new file mode 100644
index 0000000..c90f845
Binary files /dev/null and b/images/provisioning+for+non-owner+fail--_invalid+authentication+not+rejected__a1ef8dca.jpg differ
diff --git a/images/provisioning+for+non-owner+fail--_invalid+authentication+not+rejected__cc33d5e9.jpg b/images/provisioning+for+non-owner+fail--_invalid+authentication+not+rejected__cc33d5e9.jpg
new file mode 100644
index 0000000..c90f845
Binary files /dev/null and b/images/provisioning+for+non-owner+fail--_invalid+authentication+not+rejected__cc33d5e9.jpg differ
diff --git a/images/provisioning+for+non-owner+fail--_invalid+authentication+not+rejected__ea51884c.jpg b/images/provisioning+for+non-owner+fail--_invalid+authentication+not+rejected__ea51884c.jpg
new file mode 100644
index 0000000..6508546
Binary files /dev/null and b/images/provisioning+for+non-owner+fail--_invalid+authentication+not+rejected__ea51884c.jpg differ
diff --git a/images/使用不支援lea的手机测试：Initial+pair+with+xxxx+fail_e5c7d4d4.jpg b/images/使用不支援lea的手机测试：Initial+pair+with+xxxx+fail_e5c7d4d4.jpg
new file mode 100644
index 0000000..657b59c
Binary files /dev/null and b/images/使用不支援lea的手机测试：Initial+pair+with+xxxx+fail_e5c7d4d4.jpg differ
diff --git a/images/使用不支援lea的手机测试：Initial+pair+with+xxxx+fail_fa7fd0ea.jpg b/images/使用不支援lea的手机测试：Initial+pair+with+xxxx+fail_fa7fd0ea.jpg
new file mode 100644
index 0000000..657b59c
Binary files /dev/null and b/images/使用不支援lea的手机测试：Initial+pair+with+xxxx+fail_fa7fd0ea.jpg differ
diff --git a/images/手机UI显示Wait+60000ms+for+the+connection+and+UUID+event+if+not+yet+received的时候手机端在等什么_327ecf12.jpg b/images/手机UI显示Wait+60000ms+for+the+connection+and+UUID+event+if+not+yet+received的时候手机端在等什么_327ecf12.jpg
new file mode 100644
index 0000000..c62bc3b
Binary files /dev/null and b/images/手机UI显示Wait+60000ms+for+the+connection+and+UUID+event+if+not+yet+received的时候手机端在等什么_327ecf12.jpg differ
diff --git a/images/手机UI显示Wait+60000ms+for+the+connection+and+UUID+event+if+not+yet+received的时候手机端在等什么_57dd05b1.jpg b/images/手机UI显示Wait+60000ms+for+the+connection+and+UUID+event+if+not+yet+received的时候手机端在等什么_57dd05b1.jpg
new file mode 100644
index 0000000..c62bc3b
Binary files /dev/null and b/images/手机UI显示Wait+60000ms+for+the+connection+and+UUID+event+if+not+yet+received的时候手机端在等什么_57dd05b1.jpg differ
diff --git a/images/手机不弹窗原因整理_1ced575b.jpg b/images/手机不弹窗原因整理_1ced575b.jpg
new file mode 100644
index 0000000..e1f0f9b
Binary files /dev/null and b/images/手机不弹窗原因整理_1ced575b.jpg differ
diff --git a/images/手机不弹窗原因整理_23ca5b2d.jpg b/images/手机不弹窗原因整理_23ca5b2d.jpg
new file mode 100644
index 0000000..776720a
Binary files /dev/null and b/images/手机不弹窗原因整理_23ca5b2d.jpg differ
diff --git a/images/手机不弹窗原因整理_4416c54e.jpg b/images/手机不弹窗原因整理_4416c54e.jpg
new file mode 100644
index 0000000..0678ca6
Binary files /dev/null and b/images/手机不弹窗原因整理_4416c54e.jpg differ
diff --git a/images/手机不弹窗原因整理_463000a8.jpg b/images/手机不弹窗原因整理_463000a8.jpg
new file mode 100644
index 0000000..000b5c9
Binary files /dev/null and b/images/手机不弹窗原因整理_463000a8.jpg differ
diff --git a/images/手机不弹窗原因整理_5056272c.jpg b/images/手机不弹窗原因整理_5056272c.jpg
new file mode 100644
index 0000000..0968050
Binary files /dev/null and b/images/手机不弹窗原因整理_5056272c.jpg differ
diff --git a/images/手机不弹窗原因整理_711a164c.jpg b/images/手机不弹窗原因整理_711a164c.jpg
new file mode 100644
index 0000000..776720a
Binary files /dev/null and b/images/手机不弹窗原因整理_711a164c.jpg differ
diff --git a/images/手机不弹窗原因整理_9bffc870.jpg b/images/手机不弹窗原因整理_9bffc870.jpg
new file mode 100644
index 0000000..0678ca6
Binary files /dev/null and b/images/手机不弹窗原因整理_9bffc870.jpg differ
diff --git a/images/手机不弹窗原因整理_bb96b386.jpg b/images/手机不弹窗原因整理_bb96b386.jpg
new file mode 100644
index 0000000..0968050
Binary files /dev/null and b/images/手机不弹窗原因整理_bb96b386.jpg differ
diff --git a/images/手机不弹窗原因整理_e15beaaf.jpg b/images/手机不弹窗原因整理_e15beaaf.jpg
new file mode 100644
index 0000000..c18976f
Binary files /dev/null and b/images/手机不弹窗原因整理_e15beaaf.jpg differ
diff --git a/images/手机不弹窗原因整理_ea5ba847.jpg b/images/手机不弹窗原因整理_ea5ba847.jpg
new file mode 100644
index 0000000..000b5c9
Binary files /dev/null and b/images/手机不弹窗原因整理_ea5ba847.jpg differ
diff --git a/images/手机不弹窗原因整理_f0792652.jpg b/images/手机不弹窗原因整理_f0792652.jpg
new file mode 100644
index 0000000..c18976f
Binary files /dev/null and b/images/手机不弹窗原因整理_f0792652.jpg differ
diff --git a/images/手机不弹窗原因整理_f372849d.jpg b/images/手机不弹窗原因整理_f372849d.jpg
new file mode 100644
index 0000000..e1f0f9b
Binary files /dev/null and b/images/手机不弹窗原因整理_f372849d.jpg differ
diff --git a/images/手机不连legacy+profile_01785679.jpg b/images/手机不连legacy+profile_01785679.jpg
new file mode 100644
index 0000000..6234cbd
Binary files /dev/null and b/images/手机不连legacy+profile_01785679.jpg differ
diff --git a/images/手机不连legacy+profile_03f987e9.jpg b/images/手机不连legacy+profile_03f987e9.jpg
new file mode 100644
index 0000000..47a53aa
Binary files /dev/null and b/images/手机不连legacy+profile_03f987e9.jpg differ
diff --git a/images/手机不连legacy+profile_19653fbb.jpg b/images/手机不连legacy+profile_19653fbb.jpg
new file mode 100644
index 0000000..5a257f8
Binary files /dev/null and b/images/手机不连legacy+profile_19653fbb.jpg differ
diff --git a/images/手机不连legacy+profile_316cca8b.jpg b/images/手机不连legacy+profile_316cca8b.jpg
new file mode 100644
index 0000000..134acec
Binary files /dev/null and b/images/手机不连legacy+profile_316cca8b.jpg differ
diff --git a/images/手机不连legacy+profile_45c1bad2.jpg b/images/手机不连legacy+profile_45c1bad2.jpg
new file mode 100644
index 0000000..47a53aa
Binary files /dev/null and b/images/手机不连legacy+profile_45c1bad2.jpg differ
diff --git a/images/手机不连legacy+profile_554c8d1f.jpg b/images/手机不连legacy+profile_554c8d1f.jpg
new file mode 100644
index 0000000..636153a
Binary files /dev/null and b/images/手机不连legacy+profile_554c8d1f.jpg differ
diff --git a/images/手机不连legacy+profile_55f7d1df.jpg b/images/手机不连legacy+profile_55f7d1df.jpg
new file mode 100644
index 0000000..76fc037
Binary files /dev/null and b/images/手机不连legacy+profile_55f7d1df.jpg differ
diff --git a/images/手机不连legacy+profile_5fab7d9c.jpg b/images/手机不连legacy+profile_5fab7d9c.jpg
new file mode 100644
index 0000000..6234cbd
Binary files /dev/null and b/images/手机不连legacy+profile_5fab7d9c.jpg differ
diff --git a/images/手机不连legacy+profile_68ee75aa.jpg b/images/手机不连legacy+profile_68ee75aa.jpg
new file mode 100644
index 0000000..134acec
Binary files /dev/null and b/images/手机不连legacy+profile_68ee75aa.jpg differ
diff --git a/images/手机不连legacy+profile_6c9129ba.jpg b/images/手机不连legacy+profile_6c9129ba.jpg
new file mode 100644
index 0000000..6d95664
Binary files /dev/null and b/images/手机不连legacy+profile_6c9129ba.jpg differ
diff --git a/images/手机不连legacy+profile_836add9f.jpg b/images/手机不连legacy+profile_836add9f.jpg
new file mode 100644
index 0000000..636153a
Binary files /dev/null and b/images/手机不连legacy+profile_836add9f.jpg differ
diff --git a/images/手机不连legacy+profile_8aabbb2c.jpg b/images/手机不连legacy+profile_8aabbb2c.jpg
new file mode 100644
index 0000000..76fc037
Binary files /dev/null and b/images/手机不连legacy+profile_8aabbb2c.jpg differ
diff --git a/images/手机不连legacy+profile_8e5366b5.jpg b/images/手机不连legacy+profile_8e5366b5.jpg
new file mode 100644
index 0000000..6d95664
Binary files /dev/null and b/images/手机不连legacy+profile_8e5366b5.jpg differ
diff --git a/images/手机不连legacy+profile_a9222f70.jpg b/images/手机不连legacy+profile_a9222f70.jpg
new file mode 100644
index 0000000..1dcf485
Binary files /dev/null and b/images/手机不连legacy+profile_a9222f70.jpg differ
diff --git a/images/手机不连legacy+profile_d399ac34.jpg b/images/手机不连legacy+profile_d399ac34.jpg
new file mode 100644
index 0000000..5a257f8
Binary files /dev/null and b/images/手机不连legacy+profile_d399ac34.jpg differ
diff --git a/images/手机不连legacy+profile_f519ae64.jpg b/images/手机不连legacy+profile_f519ae64.jpg
new file mode 100644
index 0000000..1dcf485
Binary files /dev/null and b/images/手机不连legacy+profile_f519ae64.jpg differ
diff --git a/images/手机本来应该连主耳并且配对主耳的，但是手机却连了附耳，并且尝试配对附耳_8462fc9f.jpg b/images/手机本来应该连主耳并且配对主耳的，但是手机却连了附耳，并且尝试配对附耳_8462fc9f.jpg
new file mode 100644
index 0000000..e8684a1
Binary files /dev/null and b/images/手机本来应该连主耳并且配对主耳的，但是手机却连了附耳，并且尝试配对附耳_8462fc9f.jpg differ
diff --git a/images/手机本来应该连主耳并且配对主耳的，但是手机却连了附耳，并且尝试配对附耳_c48bcbd8.jpg b/images/手机本来应该连主耳并且配对主耳的，但是手机却连了附耳，并且尝试配对附耳_c48bcbd8.jpg
new file mode 100644
index 0000000..e8684a1
Binary files /dev/null and b/images/手机本来应该连主耳并且配对主耳的，但是手机却连了附耳，并且尝试配对附耳_c48bcbd8.jpg differ
diff --git a/images/支援lea的手机不打开bypass功能+retroactive+pair+fail_cb055910.jpg b/images/支援lea的手机不打开bypass功能+retroactive+pair+fail_cb055910.jpg
new file mode 100644
index 0000000..1a23074
Binary files /dev/null and b/images/支援lea的手机不打开bypass功能+retroactive+pair+fail_cb055910.jpg differ
diff --git a/images/支援lea的手机不打开bypass功能+retroactive+pair+fail_d21d402d.jpg b/images/支援lea的手机不打开bypass功能+retroactive+pair+fail_d21d402d.jpg
new file mode 100644
index 0000000..1a23074
Binary files /dev/null and b/images/支援lea的手机不打开bypass功能+retroactive+pair+fail_d21d402d.jpg differ
diff --git a/images/设备有打non+discoverable+adv,+依然报device+not+found+by+AK_6883f19f.jpg b/images/设备有打non+discoverable+adv,+依然报device+not+found+by+AK_6883f19f.jpg
new file mode 100644
index 0000000..077a7f4
Binary files /dev/null and b/images/设备有打non+discoverable+adv,+依然报device+not+found+by+AK_6883f19f.jpg differ
diff --git a/images/设备有打non+discoverable+adv,+依然报device+not+found+by+AK_8b977c1e.jpg b/images/设备有打non+discoverable+adv,+依然报device+not+found+by+AK_8b977c1e.jpg
new file mode 100644
index 0000000..077a7f4
Binary files /dev/null and b/images/设备有打non+discoverable+adv,+依然报device+not+found+by+AK_8b977c1e.jpg differ
diff --git a/images/配对成功之后+setting界面+音频设备类型+是灰色的_45d99bc9.jpg b/images/配对成功之后+setting界面+音频设备类型+是灰色的_45d99bc9.jpg
new file mode 100644
index 0000000..58b9385
Binary files /dev/null and b/images/配对成功之后+setting界面+音频设备类型+是灰色的_45d99bc9.jpg differ
diff --git a/images/配对成功之后+setting界面+音频设备类型+是灰色的_b99e623d.jpg b/images/配对成功之后+setting界面+音频设备类型+是灰色的_b99e623d.jpg
new file mode 100644
index 0000000..58b9385
Binary files /dev/null and b/images/配对成功之后+setting界面+音频设备类型+是灰色的_b99e623d.jpg differ
diff --git a/images/附耳没有收到UUID+0x184E_55f018aa.jpg b/images/附耳没有收到UUID+0x184E_55f018aa.jpg
new file mode 100644
index 0000000..1e4e9a9
Binary files /dev/null and b/images/附耳没有收到UUID+0x184E_55f018aa.jpg differ
diff --git a/images/附耳没有收到UUID+0x184E_d723ae58.jpg b/images/附耳没有收到UUID+0x184E_d723ae58.jpg
new file mode 100644
index 0000000..1e4e9a9
Binary files /dev/null and b/images/附耳没有收到UUID+0x184E_d723ae58.jpg differ
diff --git a/images/附耳没有收到UUID+0x184E_e02ddfc4.jpg b/images/附耳没有收到UUID+0x184E_e02ddfc4.jpg
new file mode 100644
index 0000000..7c66bd3
Binary files /dev/null and b/images/附耳没有收到UUID+0x184E_e02ddfc4.jpg differ
diff --git a/images/附耳没有收到UUID+0x184E_f4fa2e7f.jpg b/images/附耳没有收到UUID+0x184E_f4fa2e7f.jpg
new file mode 100644
index 0000000..7c66bd3
Binary files /dev/null and b/images/附耳没有收到UUID+0x184E_f4fa2e7f.jpg differ
diff --git a/images/附耳配对失败+cause+Numeric+Comparison+Failed_0x050C_02a03764.jpg b/images/附耳配对失败+cause+Numeric+Comparison+Failed_0x050C_02a03764.jpg
new file mode 100644
index 0000000..63fcacf
Binary files /dev/null and b/images/附耳配对失败+cause+Numeric+Comparison+Failed_0x050C_02a03764.jpg differ
diff --git a/images/附耳配对失败+cause+Numeric+Comparison+Failed_0x050C_84becae5.jpg b/images/附耳配对失败+cause+Numeric+Comparison+Failed_0x050C_84becae5.jpg
new file mode 100644
index 0000000..ac4c323
Binary files /dev/null and b/images/附耳配对失败+cause+Numeric+Comparison+Failed_0x050C_84becae5.jpg differ
diff --git a/images/附耳配对失败+cause+Numeric+Comparison+Failed_0x050C_c8c8bee7.jpg b/images/附耳配对失败+cause+Numeric+Comparison+Failed_0x050C_c8c8bee7.jpg
new file mode 100644
index 0000000..9ebd556
Binary files /dev/null and b/images/附耳配对失败+cause+Numeric+Comparison+Failed_0x050C_c8c8bee7.jpg differ
diff --git a/images/附耳配对失败+cause+Numeric+Comparison+Failed_0x050C_ca4c0f55.jpg b/images/附耳配对失败+cause+Numeric+Comparison+Failed_0x050C_ca4c0f55.jpg
new file mode 100644
index 0000000..9ebd556
Binary files /dev/null and b/images/附耳配对失败+cause+Numeric+Comparison+Failed_0x050C_ca4c0f55.jpg differ
diff --git a/images/附耳配对失败+cause+Numeric+Comparison+Failed_0x050C_de83beea.jpg b/images/附耳配对失败+cause+Numeric+Comparison+Failed_0x050C_de83beea.jpg
new file mode 100644
index 0000000..63fcacf
Binary files /dev/null and b/images/附耳配对失败+cause+Numeric+Comparison+Failed_0x050C_de83beea.jpg differ
diff --git a/images/附耳配对失败+cause+Numeric+Comparison+Failed_0x050C_eb41fecc.jpg b/images/附耳配对失败+cause+Numeric+Comparison+Failed_0x050C_eb41fecc.jpg
new file mode 100644
index 0000000..ac4c323
Binary files /dev/null and b/images/附耳配对失败+cause+Numeric+Comparison+Failed_0x050C_eb41fecc.jpg differ
diff --git a/images/附耳配对失败,+cause+Unspecified+Reason_0db15cd9.jpg b/images/附耳配对失败,+cause+Unspecified+Reason_0db15cd9.jpg
new file mode 100644
index 0000000..c1100cd
Binary files /dev/null and b/images/附耳配对失败,+cause+Unspecified+Reason_0db15cd9.jpg differ
diff --git a/images/附耳配对失败,+cause+Unspecified+Reason_19702742.jpg b/images/附耳配对失败,+cause+Unspecified+Reason_19702742.jpg
new file mode 100644
index 0000000..18651a5
Binary files /dev/null and b/images/附耳配对失败,+cause+Unspecified+Reason_19702742.jpg differ
diff --git a/images/附耳配对失败,+cause+Unspecified+Reason_56326c85.jpg b/images/附耳配对失败,+cause+Unspecified+Reason_56326c85.jpg
new file mode 100644
index 0000000..18651a5
Binary files /dev/null and b/images/附耳配对失败,+cause+Unspecified+Reason_56326c85.jpg differ
diff --git a/images/附耳配对失败,+cause+Unspecified+Reason_e6f9f15d.jpg b/images/附耳配对失败,+cause+Unspecified+Reason_e6f9f15d.jpg
new file mode 100644
index 0000000..348b71a
Binary files /dev/null and b/images/附耳配对失败,+cause+Unspecified+Reason_e6f9f15d.jpg differ
diff --git a/images/附耳配对失败,+cause+Unspecified+Reason_f1e15c12.jpg b/images/附耳配对失败,+cause+Unspecified+Reason_f1e15c12.jpg
new file mode 100644
index 0000000..348b71a
Binary files /dev/null and b/images/附耳配对失败,+cause+Unspecified+Reason_f1e15c12.jpg differ
diff --git a/images/附耳配对失败,+cause+Unspecified+Reason_fdc5d3de.jpg b/images/附耳配对失败,+cause+Unspecified+Reason_fdc5d3de.jpg
new file mode 100644
index 0000000..c1100cd
Binary files /dev/null and b/images/附耳配对失败,+cause+Unspecified+Reason_fdc5d3de.jpg differ
diff --git a/initial+pairing成功之后通知栏不显示电量HUN.md b/initial+pairing成功之后通知栏不显示电量HUN.md
new file mode 100644
index 0000000..c43a39a
--- /dev/null
+++ b/initial+pairing成功之后通知栏不显示电量HUN.md
@@ -0,0 +1,5 @@
+# initial pairing成功之后通知栏不显示电量HUN
+
+spec 规定
+
+initial pairing 通知栏本身就不会显示电量HUN
diff --git a/initial+pair，手机不来连bredr.md b/initial+pair，手机不来连bredr.md
new file mode 100644
index 0000000..7118bad
--- /dev/null
+++ b/initial+pair，手机不来连bredr.md
@@ -0,0 +1,33 @@
+# initial pair，手机不来连bredr
+
+手机log显示 Secret handshake failed
+
+
+
+
+ Line 155121: 11-13 18:53:14.873 10160 23283 24046 I FastPair: Send Progress to validator, step=Handshake
+ Line 155130: 11-13 18:53:14.993 10160 23283 24046 I FastPair: [trigger-id=Scan2745BCA1, feature-id=Inpa]: FPDC: handshakeForKeyBasedPairing: device=XX:XX:XX:XX:82:D6, type=0x00, flag=0x2C
+ Line 155131: 11-13 18:53:14.994 10160 23283 24046 I FastPair: Handshake XX:XX:XX:XX:82:D6, generates key by ECDH.
+ Line 155132: 11-13 18:53:15.001 10160 23283 24046 I FastPair: Handshake XX:XX:XX:XX:82:D6, flags 44.
+ Line 155133: 11-13 18:53:15.001 10160 23283 24046 I FastPair: [trigger-id=Scan2745BCA1, feature-id=Inpa]: EventLoggerWrapper: cuj-state=UPDATE: SECRET_HANDSHAKE_GATT_COMMUNICATION START
+ Line 155134: 11-13 18:53:15.003 10160 23283 24046 I FastPair: Handshake Message: type (00), flag (2C).
+ Line 155136: 11-13 18:53:15.083 10160 23283 24046 I FastPair: Writing handshake packet to address=XX:XX:XX:XX:82:D6
+ Line 155137: 11-13 18:53:15.218 10160 23283 24046 I FastPair: Waiting handshake packet from address=XX:XX:XX:XX:82:D6
+ Line 155356: 11-13 18:53:25.222 10160 23283 24046 W FastPair: Secret handshake failed, address=XX:XX:XX:XX:82:D6, spent time=10219ms, retryCount=0 |
+
+
+
+
+耳机log对应的现象就是
+
+正常log：
+
+我们有回kbp response的
+
+
+
+不正常的log
+
+我们没有回kbp response
+
+
diff --git a/media/1.2.1+设备端环境搭建/08271864e4343f90c4a3c604c18353f4.png b/media/1.2.1+设备端环境搭建/08271864e4343f90c4a3c604c18353f4.png
deleted file mode 100644
index d46e839..0000000
Binary files a/media/1.2.1+设备端环境搭建/08271864e4343f90c4a3c604c18353f4.png and /dev/null differ
diff --git a/media/1.2.1+设备端环境搭建/1184039875b1b2e3119c18c9f50f7a86.png b/media/1.2.1+设备端环境搭建/1184039875b1b2e3119c18c9f50f7a86.png
deleted file mode 100644
index 438cf1c..0000000
Binary files a/media/1.2.1+设备端环境搭建/1184039875b1b2e3119c18c9f50f7a86.png and /dev/null differ
diff --git a/media/1.2.1+设备端环境搭建/12993266da101944d424e1511aee4fc6.png b/media/1.2.1+设备端环境搭建/12993266da101944d424e1511aee4fc6.png
deleted file mode 100644
index f0dca6d..0000000
Binary files a/media/1.2.1+设备端环境搭建/12993266da101944d424e1511aee4fc6.png and /dev/null differ
diff --git a/media/1.2.1+设备端环境搭建/2341c78f84b2b1be53683ee2fe88e7cf.png b/media/1.2.1+设备端环境搭建/2341c78f84b2b1be53683ee2fe88e7cf.png
deleted file mode 100644
index 3f0dace..0000000
Binary files a/media/1.2.1+设备端环境搭建/2341c78f84b2b1be53683ee2fe88e7cf.png and /dev/null differ
diff --git a/media/1.2.1+设备端环境搭建/2995cee295e29c60b1d5b454ce57ebd0.png b/media/1.2.1+设备端环境搭建/2995cee295e29c60b1d5b454ce57ebd0.png
deleted file mode 100644
index 0ef9ce6..0000000
Binary files a/media/1.2.1+设备端环境搭建/2995cee295e29c60b1d5b454ce57ebd0.png and /dev/null differ
diff --git a/media/1.2.1+设备端环境搭建/376350bb02b315be95274cec1b03fa1d.png b/media/1.2.1+设备端环境搭建/376350bb02b315be95274cec1b03fa1d.png
deleted file mode 100644
index 08df83a..0000000
Binary files a/media/1.2.1+设备端环境搭建/376350bb02b315be95274cec1b03fa1d.png and /dev/null differ
diff --git a/media/1.2.1+设备端环境搭建/38d2923796490cb846076477f7aa2e6a.png b/media/1.2.1+设备端环境搭建/38d2923796490cb846076477f7aa2e6a.png
deleted file mode 100644
index 011ab75..0000000
Binary files a/media/1.2.1+设备端环境搭建/38d2923796490cb846076477f7aa2e6a.png and /dev/null differ
diff --git a/media/1.2.1+设备端环境搭建/4bf5ee1adce5f42f2850af333c894b14.png b/media/1.2.1+设备端环境搭建/4bf5ee1adce5f42f2850af333c894b14.png
deleted file mode 100644
index aeca4ca..0000000
Binary files a/media/1.2.1+设备端环境搭建/4bf5ee1adce5f42f2850af333c894b14.png and /dev/null differ
diff --git a/media/1.2.1+设备端环境搭建/4fbd46cb906e3341fd72fa298fa820cf.png b/media/1.2.1+设备端环境搭建/4fbd46cb906e3341fd72fa298fa820cf.png
deleted file mode 100644
index a224db5..0000000
Binary files a/media/1.2.1+设备端环境搭建/4fbd46cb906e3341fd72fa298fa820cf.png and /dev/null differ
diff --git a/media/1.2.1+设备端环境搭建/500bc6e0f02e7d9c0c068090d4d90310.png b/media/1.2.1+设备端环境搭建/500bc6e0f02e7d9c0c068090d4d90310.png
deleted file mode 100644
index 84bf780..0000000
Binary files a/media/1.2.1+设备端环境搭建/500bc6e0f02e7d9c0c068090d4d90310.png and /dev/null differ
diff --git a/media/1.2.1+设备端环境搭建/51a0e41fdd5cb323f5cd8e5266bbb005.png b/media/1.2.1+设备端环境搭建/51a0e41fdd5cb323f5cd8e5266bbb005.png
deleted file mode 100644
index 0f478b9..0000000
Binary files a/media/1.2.1+设备端环境搭建/51a0e41fdd5cb323f5cd8e5266bbb005.png and /dev/null differ
diff --git a/media/1.2.1+设备端环境搭建/524208b2e6abc1f6646aeba14bd59d65.png b/media/1.2.1+设备端环境搭建/524208b2e6abc1f6646aeba14bd59d65.png
deleted file mode 100644
index 8987b86..0000000
Binary files a/media/1.2.1+设备端环境搭建/524208b2e6abc1f6646aeba14bd59d65.png and /dev/null differ
diff --git a/media/1.2.1+设备端环境搭建/60edd7696c5c11c06f000f97097a3acb.png b/media/1.2.1+设备端环境搭建/60edd7696c5c11c06f000f97097a3acb.png
deleted file mode 100644
index e138cad..0000000
Binary files a/media/1.2.1+设备端环境搭建/60edd7696c5c11c06f000f97097a3acb.png and /dev/null differ
diff --git a/media/1.2.1+设备端环境搭建/65276f35c42f7a8bfcb298a26c2e6f8d.png b/media/1.2.1+设备端环境搭建/65276f35c42f7a8bfcb298a26c2e6f8d.png
deleted file mode 100644
index b0eb1f8..0000000
Binary files a/media/1.2.1+设备端环境搭建/65276f35c42f7a8bfcb298a26c2e6f8d.png and /dev/null differ
diff --git a/media/1.2.1+设备端环境搭建/80bd69652553556fad57c0794099a55d.png b/media/1.2.1+设备端环境搭建/80bd69652553556fad57c0794099a55d.png
deleted file mode 100644
index c998b23..0000000
Binary files a/media/1.2.1+设备端环境搭建/80bd69652553556fad57c0794099a55d.png and /dev/null differ
diff --git a/media/1.2.1+设备端环境搭建/89818e83841c7886e8954c77c415deec.png b/media/1.2.1+设备端环境搭建/89818e83841c7886e8954c77c415deec.png
deleted file mode 100644
index 4916085..0000000
Binary files a/media/1.2.1+设备端环境搭建/89818e83841c7886e8954c77c415deec.png and /dev/null differ
diff --git a/media/1.2.1+设备端环境搭建/95b03ee961d34cf393b9e32ceb54e1cd.png b/media/1.2.1+设备端环境搭建/95b03ee961d34cf393b9e32ceb54e1cd.png
deleted file mode 100644
index 3772c7d..0000000
Binary files a/media/1.2.1+设备端环境搭建/95b03ee961d34cf393b9e32ceb54e1cd.png and /dev/null differ
diff --git a/media/1.2.1+设备端环境搭建/a73ebf874561ef037ea7cc0e0eec3c1a.png b/media/1.2.1+设备端环境搭建/a73ebf874561ef037ea7cc0e0eec3c1a.png
deleted file mode 100644
index b3c8d9c..0000000
Binary files a/media/1.2.1+设备端环境搭建/a73ebf874561ef037ea7cc0e0eec3c1a.png and /dev/null differ
diff --git a/media/1.2.1+设备端环境搭建/a75da87126dabd34a9c54e26b5008fd5.png b/media/1.2.1+设备端环境搭建/a75da87126dabd34a9c54e26b5008fd5.png
deleted file mode 100644
index 1f157c7..0000000
Binary files a/media/1.2.1+设备端环境搭建/a75da87126dabd34a9c54e26b5008fd5.png and /dev/null differ
diff --git a/media/1.2.1+设备端环境搭建/b5ca29b78d55f32174c569e6d26e9a0b.png b/media/1.2.1+设备端环境搭建/b5ca29b78d55f32174c569e6d26e9a0b.png
deleted file mode 100644
index 985b7bc..0000000
Binary files a/media/1.2.1+设备端环境搭建/b5ca29b78d55f32174c569e6d26e9a0b.png and /dev/null differ
diff --git a/media/1.2.1+设备端环境搭建/bd1aae2090097e031e53873968a1d6f4.png b/media/1.2.1+设备端环境搭建/bd1aae2090097e031e53873968a1d6f4.png
deleted file mode 100644
index 854f536..0000000
Binary files a/media/1.2.1+设备端环境搭建/bd1aae2090097e031e53873968a1d6f4.png and /dev/null differ
diff --git a/media/1.2.1+设备端环境搭建/bf3b347414521efeed1e046f0f2a279c.png b/media/1.2.1+设备端环境搭建/bf3b347414521efeed1e046f0f2a279c.png
deleted file mode 100644
index 1518278..0000000
Binary files a/media/1.2.1+设备端环境搭建/bf3b347414521efeed1e046f0f2a279c.png and /dev/null differ
diff --git a/media/1.2.1+设备端环境搭建/c564ca9d4cb3db32c6a593bdda5b3617.png b/media/1.2.1+设备端环境搭建/c564ca9d4cb3db32c6a593bdda5b3617.png
deleted file mode 100644
index 90ab0df..0000000
Binary files a/media/1.2.1+设备端环境搭建/c564ca9d4cb3db32c6a593bdda5b3617.png and /dev/null differ
diff --git a/media/1.2.1+设备端环境搭建/deb4e2f66d2e71d13625d9a84e02f4a9.png b/media/1.2.1+设备端环境搭建/deb4e2f66d2e71d13625d9a84e02f4a9.png
deleted file mode 100644
index 6e15aaa..0000000
Binary files a/media/1.2.1+设备端环境搭建/deb4e2f66d2e71d13625d9a84e02f4a9.png and /dev/null differ
diff --git a/media/1.2.1+设备端环境搭建/ea1bba5a0188d660a7843b301bd45575.png b/media/1.2.1+设备端环境搭建/ea1bba5a0188d660a7843b301bd45575.png
deleted file mode 100644
index cd7a26d..0000000
Binary files a/media/1.2.1+设备端环境搭建/ea1bba5a0188d660a7843b301bd45575.png and /dev/null differ
diff --git a/media/1.2.1+设备端环境搭建/ec289f7c9f337a00ff4eed1b2731265c.png b/media/1.2.1+设备端环境搭建/ec289f7c9f337a00ff4eed1b2731265c.png
deleted file mode 100644
index edc52b2..0000000
Binary files a/media/1.2.1+设备端环境搭建/ec289f7c9f337a00ff4eed1b2731265c.png and /dev/null differ
diff --git a/media/1.2.1+设备端环境搭建/f7cf5e80b139e58c372ee7bd3b58734d.png b/media/1.2.1+设备端环境搭建/f7cf5e80b139e58c372ee7bd3b58734d.png
deleted file mode 100644
index e3c1952..0000000
Binary files a/media/1.2.1+设备端环境搭建/f7cf5e80b139e58c372ee7bd3b58734d.png and /dev/null differ
diff --git a/media/1.2.2+手机端环境搭建/02d69ad5e64edc68be395ec8424e3d77.png b/media/1.2.2+手机端环境搭建/02d69ad5e64edc68be395ec8424e3d77.png
deleted file mode 100644
index 1bc0bf3..0000000
Binary files a/media/1.2.2+手机端环境搭建/02d69ad5e64edc68be395ec8424e3d77.png and /dev/null differ
diff --git a/media/1.2.2+手机端环境搭建/04ad6633f70aaf5f2874183ab21105f2.png b/media/1.2.2+手机端环境搭建/04ad6633f70aaf5f2874183ab21105f2.png
deleted file mode 100644
index df8860b..0000000
Binary files a/media/1.2.2+手机端环境搭建/04ad6633f70aaf5f2874183ab21105f2.png and /dev/null differ
diff --git a/media/1.2.2+手机端环境搭建/0adfe8650d8c0daefd5a769e26f3d0b1.png b/media/1.2.2+手机端环境搭建/0adfe8650d8c0daefd5a769e26f3d0b1.png
deleted file mode 100644
index 8a864b4..0000000
Binary files a/media/1.2.2+手机端环境搭建/0adfe8650d8c0daefd5a769e26f3d0b1.png and /dev/null differ
diff --git a/media/1.2.2+手机端环境搭建/0afddbb13a88680ea12e60051fd70d3f.png b/media/1.2.2+手机端环境搭建/0afddbb13a88680ea12e60051fd70d3f.png
deleted file mode 100644
index 3c271fe..0000000
Binary files a/media/1.2.2+手机端环境搭建/0afddbb13a88680ea12e60051fd70d3f.png and /dev/null differ
diff --git a/media/1.2.2+手机端环境搭建/307093c833475fc3c0876cd87a2d23a6.png b/media/1.2.2+手机端环境搭建/307093c833475fc3c0876cd87a2d23a6.png
deleted file mode 100644
index bb4646a..0000000
Binary files a/media/1.2.2+手机端环境搭建/307093c833475fc3c0876cd87a2d23a6.png and /dev/null differ
diff --git a/media/1.2.2+手机端环境搭建/4099155117e47e8fd6a2928139f023cf.png b/media/1.2.2+手机端环境搭建/4099155117e47e8fd6a2928139f023cf.png
deleted file mode 100644
index 9b82fd7..0000000
Binary files a/media/1.2.2+手机端环境搭建/4099155117e47e8fd6a2928139f023cf.png and /dev/null differ
diff --git a/media/1.2.2+手机端环境搭建/47fc85072a213d1ef683962c106e12a7.png b/media/1.2.2+手机端环境搭建/47fc85072a213d1ef683962c106e12a7.png
deleted file mode 100644
index 1075722..0000000
Binary files a/media/1.2.2+手机端环境搭建/47fc85072a213d1ef683962c106e12a7.png and /dev/null differ
diff --git a/media/1.2.2+手机端环境搭建/6145f25973da8c0950b116a685608f22.png b/media/1.2.2+手机端环境搭建/6145f25973da8c0950b116a685608f22.png
deleted file mode 100644
index 0e06c2a..0000000
Binary files a/media/1.2.2+手机端环境搭建/6145f25973da8c0950b116a685608f22.png and /dev/null differ
diff --git a/media/1.2.2+手机端环境搭建/75f47b0f791e44a49a705a8576f20aee.png b/media/1.2.2+手机端环境搭建/75f47b0f791e44a49a705a8576f20aee.png
deleted file mode 100644
index c94c767..0000000
Binary files a/media/1.2.2+手机端环境搭建/75f47b0f791e44a49a705a8576f20aee.png and /dev/null differ
diff --git a/media/1.2.2+手机端环境搭建/804d309c95c25e78feb23f450d7755ca.png b/media/1.2.2+手机端环境搭建/804d309c95c25e78feb23f450d7755ca.png
deleted file mode 100644
index 95011ad..0000000
Binary files a/media/1.2.2+手机端环境搭建/804d309c95c25e78feb23f450d7755ca.png and /dev/null differ
diff --git a/media/1.2.2+手机端环境搭建/8961bf5217e5264df9f43b1e5dc19472.png b/media/1.2.2+手机端环境搭建/8961bf5217e5264df9f43b1e5dc19472.png
deleted file mode 100644
index 1de844e..0000000
Binary files a/media/1.2.2+手机端环境搭建/8961bf5217e5264df9f43b1e5dc19472.png and /dev/null differ
diff --git a/media/1.2.2+手机端环境搭建/9e02ae63f1a480cd8aae5e995ec6292b.png b/media/1.2.2+手机端环境搭建/9e02ae63f1a480cd8aae5e995ec6292b.png
deleted file mode 100644
index 487b81d..0000000
Binary files a/media/1.2.2+手机端环境搭建/9e02ae63f1a480cd8aae5e995ec6292b.png and /dev/null differ
diff --git a/media/1.2.2+手机端环境搭建/a6eec7350b2c54e15ff34925a091b308.png b/media/1.2.2+手机端环境搭建/a6eec7350b2c54e15ff34925a091b308.png
deleted file mode 100644
index b9f1458..0000000
Binary files a/media/1.2.2+手机端环境搭建/a6eec7350b2c54e15ff34925a091b308.png and /dev/null differ
diff --git a/media/1.2.2+手机端环境搭建/acb641ca23621734850802d675256d78.png b/media/1.2.2+手机端环境搭建/acb641ca23621734850802d675256d78.png
deleted file mode 100644
index 9f64f6b..0000000
Binary files a/media/1.2.2+手机端环境搭建/acb641ca23621734850802d675256d78.png and /dev/null differ
diff --git a/media/1.2.2+手机端环境搭建/cb73f9490ed6394cbc3076b4a20ab714.png b/media/1.2.2+手机端环境搭建/cb73f9490ed6394cbc3076b4a20ab714.png
deleted file mode 100644
index f4da861..0000000
Binary files a/media/1.2.2+手机端环境搭建/cb73f9490ed6394cbc3076b4a20ab714.png and /dev/null differ
diff --git a/media/1.2.2+手机端环境搭建/e2f389cdc0fd9e3536b611b068529f10.png b/media/1.2.2+手机端环境搭建/e2f389cdc0fd9e3536b611b068529f10.png
deleted file mode 100644
index dd8cc64..0000000
Binary files a/media/1.2.2+手机端环境搭建/e2f389cdc0fd9e3536b611b068529f10.png and /dev/null differ
diff --git a/media/1.2.2+手机端环境搭建/e93f5957349d40e509c2e561d161858d.png b/media/1.2.2+手机端环境搭建/e93f5957349d40e509c2e561d161858d.png
deleted file mode 100644
index 3748ca3..0000000
Binary files a/media/1.2.2+手机端环境搭建/e93f5957349d40e509c2e561d161858d.png and /dev/null differ
diff --git a/media/1.2.2+手机端环境搭建/ea2aefeffbdf707acdd65a7a66083d1a.png b/media/1.2.2+手机端环境搭建/ea2aefeffbdf707acdd65a7a66083d1a.png
deleted file mode 100644
index de79f76..0000000
Binary files a/media/1.2.2+手机端环境搭建/ea2aefeffbdf707acdd65a7a66083d1a.png and /dev/null differ
diff --git a/media/1.2.2+手机端环境搭建/fdf003aa6f88c7bf2cfd73319f751c3f.png b/media/1.2.2+手机端环境搭建/fdf003aa6f88c7bf2cfd73319f751c3f.png
deleted file mode 100644
index 913d319..0000000
Binary files a/media/1.2.2+手机端环境搭建/fdf003aa6f88c7bf2cfd73319f751c3f.png and /dev/null differ
diff --git a/media/1.2.3+Fast+Pair+Validator+环境搭建/0b8ab45807f00be2a354fdb1f6568f26.png b/media/1.2.3+Fast+Pair+Validator+环境搭建/0b8ab45807f00be2a354fdb1f6568f26.png
deleted file mode 100644
index 95011ad..0000000
Binary files a/media/1.2.3+Fast+Pair+Validator+环境搭建/0b8ab45807f00be2a354fdb1f6568f26.png and /dev/null differ
diff --git a/media/1.2.3+Fast+Pair+Validator+环境搭建/0ba213fcc09099ab41c8e0221e4928f5.png b/media/1.2.3+Fast+Pair+Validator+环境搭建/0ba213fcc09099ab41c8e0221e4928f5.png
deleted file mode 100644
index 1dd9dc3..0000000
Binary files a/media/1.2.3+Fast+Pair+Validator+环境搭建/0ba213fcc09099ab41c8e0221e4928f5.png and /dev/null differ
diff --git a/media/1.2.3+Fast+Pair+Validator+环境搭建/0bab20060f6b2f3bfb155b88a05828b1.png b/media/1.2.3+Fast+Pair+Validator+环境搭建/0bab20060f6b2f3bfb155b88a05828b1.png
deleted file mode 100644
index dd8cc64..0000000
Binary files a/media/1.2.3+Fast+Pair+Validator+环境搭建/0bab20060f6b2f3bfb155b88a05828b1.png and /dev/null differ
diff --git a/media/1.2.3+Fast+Pair+Validator+环境搭建/1e4f2c79976f21a9e067e2b7f94dc4d5.png b/media/1.2.3+Fast+Pair+Validator+环境搭建/1e4f2c79976f21a9e067e2b7f94dc4d5.png
deleted file mode 100644
index 8a864b4..0000000
Binary files a/media/1.2.3+Fast+Pair+Validator+环境搭建/1e4f2c79976f21a9e067e2b7f94dc4d5.png and /dev/null differ
diff --git a/media/1.2.3+Fast+Pair+Validator+环境搭建/3843e586b6e1f94639186b0584b86176.png b/media/1.2.3+Fast+Pair+Validator+环境搭建/3843e586b6e1f94639186b0584b86176.png
deleted file mode 100644
index b9f1458..0000000
Binary files a/media/1.2.3+Fast+Pair+Validator+环境搭建/3843e586b6e1f94639186b0584b86176.png and /dev/null differ
diff --git a/media/1.2.3+Fast+Pair+Validator+环境搭建/389cce5910af360b6867f26f36c1b9a3.png b/media/1.2.3+Fast+Pair+Validator+环境搭建/389cce5910af360b6867f26f36c1b9a3.png
deleted file mode 100644
index ee12075..0000000
Binary files a/media/1.2.3+Fast+Pair+Validator+环境搭建/389cce5910af360b6867f26f36c1b9a3.png and /dev/null differ
diff --git a/media/1.2.3+Fast+Pair+Validator+环境搭建/3f2cbf0fb83aedb623ce6a6af44aede9.png b/media/1.2.3+Fast+Pair+Validator+环境搭建/3f2cbf0fb83aedb623ce6a6af44aede9.png
deleted file mode 100644
index 487b81d..0000000
Binary files a/media/1.2.3+Fast+Pair+Validator+环境搭建/3f2cbf0fb83aedb623ce6a6af44aede9.png and /dev/null differ
diff --git a/media/1.2.3+Fast+Pair+Validator+环境搭建/4e9dd6bc92d127639a4e5a538c9acc42.png b/media/1.2.3+Fast+Pair+Validator+环境搭建/4e9dd6bc92d127639a4e5a538c9acc42.png
deleted file mode 100644
index 1075722..0000000
Binary files a/media/1.2.3+Fast+Pair+Validator+环境搭建/4e9dd6bc92d127639a4e5a538c9acc42.png and /dev/null differ
diff --git a/media/1.2.3+Fast+Pair+Validator+环境搭建/5040df7f9e4af787dd63c45576f1d7f2.png b/media/1.2.3+Fast+Pair+Validator+环境搭建/5040df7f9e4af787dd63c45576f1d7f2.png
deleted file mode 100644
index 1e88bb6..0000000
Binary files a/media/1.2.3+Fast+Pair+Validator+环境搭建/5040df7f9e4af787dd63c45576f1d7f2.png and /dev/null differ
diff --git a/media/1.2.3+Fast+Pair+Validator+环境搭建/6e51bd1141ca846e4af0bb2e93e17334.png b/media/1.2.3+Fast+Pair+Validator+环境搭建/6e51bd1141ca846e4af0bb2e93e17334.png
deleted file mode 100644
index f4da861..0000000
Binary files a/media/1.2.3+Fast+Pair+Validator+环境搭建/6e51bd1141ca846e4af0bb2e93e17334.png and /dev/null differ
diff --git a/media/1.2.3+Fast+Pair+Validator+环境搭建/6f2e8db9a220e705bf4d48b3aaf9c482.png b/media/1.2.3+Fast+Pair+Validator+环境搭建/6f2e8db9a220e705bf4d48b3aaf9c482.png
deleted file mode 100644
index 4dd8da1..0000000
Binary files a/media/1.2.3+Fast+Pair+Validator+环境搭建/6f2e8db9a220e705bf4d48b3aaf9c482.png and /dev/null differ
diff --git a/media/1.2.3+Fast+Pair+Validator+环境搭建/6fa8e8c938098fc1362ca8cadcd5f68f.png b/media/1.2.3+Fast+Pair+Validator+环境搭建/6fa8e8c938098fc1362ca8cadcd5f68f.png
deleted file mode 100644
index 007341f..0000000
Binary files a/media/1.2.3+Fast+Pair+Validator+环境搭建/6fa8e8c938098fc1362ca8cadcd5f68f.png and /dev/null differ
diff --git a/media/1.2.3+Fast+Pair+Validator+环境搭建/7313649e14e054046dc31eafc26a99a0.png b/media/1.2.3+Fast+Pair+Validator+环境搭建/7313649e14e054046dc31eafc26a99a0.png
deleted file mode 100644
index 1bc0bf3..0000000
Binary files a/media/1.2.3+Fast+Pair+Validator+环境搭建/7313649e14e054046dc31eafc26a99a0.png and /dev/null differ
diff --git a/media/1.2.3+Fast+Pair+Validator+环境搭建/80eb0310afca33931827d2287ded6836.png b/media/1.2.3+Fast+Pair+Validator+环境搭建/80eb0310afca33931827d2287ded6836.png
deleted file mode 100644
index 9f64f6b..0000000
Binary files a/media/1.2.3+Fast+Pair+Validator+环境搭建/80eb0310afca33931827d2287ded6836.png and /dev/null differ
diff --git a/media/1.2.3+Fast+Pair+Validator+环境搭建/824e58e4157c13a7a9ae26740fdc94fa.png b/media/1.2.3+Fast+Pair+Validator+环境搭建/824e58e4157c13a7a9ae26740fdc94fa.png
deleted file mode 100644
index 3748ca3..0000000
Binary files a/media/1.2.3+Fast+Pair+Validator+环境搭建/824e58e4157c13a7a9ae26740fdc94fa.png and /dev/null differ
diff --git a/media/1.2.3+Fast+Pair+Validator+环境搭建/8ec23fa1fcbeed94cd2fd9578f0002e5.png b/media/1.2.3+Fast+Pair+Validator+环境搭建/8ec23fa1fcbeed94cd2fd9578f0002e5.png
deleted file mode 100644
index de79f76..0000000
Binary files a/media/1.2.3+Fast+Pair+Validator+环境搭建/8ec23fa1fcbeed94cd2fd9578f0002e5.png and /dev/null differ
diff --git a/media/1.2.3+Fast+Pair+Validator+环境搭建/940b91547f4e49233ceaaf7092386c29.png b/media/1.2.3+Fast+Pair+Validator+环境搭建/940b91547f4e49233ceaaf7092386c29.png
deleted file mode 100644
index c5891b3..0000000
Binary files a/media/1.2.3+Fast+Pair+Validator+环境搭建/940b91547f4e49233ceaaf7092386c29.png and /dev/null differ
diff --git a/media/1.2.3+Fast+Pair+Validator+环境搭建/94667834a280a4a9bbc13db5dbc554fc.png b/media/1.2.3+Fast+Pair+Validator+环境搭建/94667834a280a4a9bbc13db5dbc554fc.png
deleted file mode 100644
index 1de844e..0000000
Binary files a/media/1.2.3+Fast+Pair+Validator+环境搭建/94667834a280a4a9bbc13db5dbc554fc.png and /dev/null differ
diff --git a/media/1.2.3+Fast+Pair+Validator+环境搭建/9623d91573182c7f5b1493f12c4356e3.png b/media/1.2.3+Fast+Pair+Validator+环境搭建/9623d91573182c7f5b1493f12c4356e3.png
deleted file mode 100644
index bb4646a..0000000
Binary files a/media/1.2.3+Fast+Pair+Validator+环境搭建/9623d91573182c7f5b1493f12c4356e3.png and /dev/null differ
diff --git a/media/1.2.3+Fast+Pair+Validator+环境搭建/bb062e88ef90abe40f8398b64950b341.png b/media/1.2.3+Fast+Pair+Validator+环境搭建/bb062e88ef90abe40f8398b64950b341.png
deleted file mode 100644
index cb8d7d8..0000000
Binary files a/media/1.2.3+Fast+Pair+Validator+环境搭建/bb062e88ef90abe40f8398b64950b341.png and /dev/null differ
diff --git a/media/1.2.3+Fast+Pair+Validator+环境搭建/bbdfcb16c991936618508c182350d221.png b/media/1.2.3+Fast+Pair+Validator+环境搭建/bbdfcb16c991936618508c182350d221.png
deleted file mode 100644
index 419c941..0000000
Binary files a/media/1.2.3+Fast+Pair+Validator+环境搭建/bbdfcb16c991936618508c182350d221.png and /dev/null differ
diff --git a/media/1.2.3+Fast+Pair+Validator+环境搭建/c1a5e093b0c30a6ec18f3a502923afd7.png b/media/1.2.3+Fast+Pair+Validator+环境搭建/c1a5e093b0c30a6ec18f3a502923afd7.png
deleted file mode 100644
index 78d5902..0000000
Binary files a/media/1.2.3+Fast+Pair+Validator+环境搭建/c1a5e093b0c30a6ec18f3a502923afd7.png and /dev/null differ
diff --git a/media/1.2.3+Fast+Pair+Validator+环境搭建/c53346bd740285ec3eff9a183d840538.png b/media/1.2.3+Fast+Pair+Validator+环境搭建/c53346bd740285ec3eff9a183d840538.png
deleted file mode 100644
index c94c767..0000000
Binary files a/media/1.2.3+Fast+Pair+Validator+环境搭建/c53346bd740285ec3eff9a183d840538.png and /dev/null differ
diff --git a/media/1.2.3+Fast+Pair+Validator+环境搭建/eb0dd21fa08cde04a9b83381d4884e1e.png b/media/1.2.3+Fast+Pair+Validator+环境搭建/eb0dd21fa08cde04a9b83381d4884e1e.png
deleted file mode 100644
index 913d319..0000000
Binary files a/media/1.2.3+Fast+Pair+Validator+环境搭建/eb0dd21fa08cde04a9b83381d4884e1e.png and /dev/null differ
diff --git a/media/1.2.3+Fast+Pair+Validator+环境搭建/ebec7d388fb86d05aca3ba2165f5098e.png b/media/1.2.3+Fast+Pair+Validator+环境搭建/ebec7d388fb86d05aca3ba2165f5098e.png
deleted file mode 100644
index 0e06c2a..0000000
Binary files a/media/1.2.3+Fast+Pair+Validator+环境搭建/ebec7d388fb86d05aca3ba2165f5098e.png and /dev/null differ
diff --git a/media/1.2.3+Fast+Pair+Validator+环境搭建/f2fdc69e7658e7f5955988ca5f9280d5.png b/media/1.2.3+Fast+Pair+Validator+环境搭建/f2fdc69e7658e7f5955988ca5f9280d5.png
deleted file mode 100644
index 9b82fd7..0000000
Binary files a/media/1.2.3+Fast+Pair+Validator+环境搭建/f2fdc69e7658e7f5955988ca5f9280d5.png and /dev/null differ
diff --git a/media/1.3+测试/0683707db76fff45c025b6472bd589cd.png b/media/1.3+测试/0683707db76fff45c025b6472bd589cd.png
deleted file mode 100644
index 3812a99..0000000
Binary files a/media/1.3+测试/0683707db76fff45c025b6472bd589cd.png and /dev/null differ
diff --git a/media/1.3+测试/60166fa4da7468639014c496e6182937.png b/media/1.3+测试/60166fa4da7468639014c496e6182937.png
deleted file mode 100644
index 448b7a7..0000000
Binary files a/media/1.3+测试/60166fa4da7468639014c496e6182937.png and /dev/null differ
diff --git a/media/1.3+测试/6d6c19d4cd32e603d5dee783c1c52050.png b/media/1.3+测试/6d6c19d4cd32e603d5dee783c1c52050.png
deleted file mode 100644
index 17d9529..0000000
Binary files a/media/1.3+测试/6d6c19d4cd32e603d5dee783c1c52050.png and /dev/null differ
diff --git a/media/1.3.1+Fast+Pair+Validator测试/314cb995ea0ae6c488df07b4811c6a76.png b/media/1.3.1+Fast+Pair+Validator测试/314cb995ea0ae6c488df07b4811c6a76.png
deleted file mode 100644
index f5d8601..0000000
Binary files a/media/1.3.1+Fast+Pair+Validator测试/314cb995ea0ae6c488df07b4811c6a76.png and /dev/null differ
diff --git a/media/1.3.1.1+FAST+PAIR/03187c9b096259e2fea8747010de6691.png b/media/1.3.1.1+FAST+PAIR/03187c9b096259e2fea8747010de6691.png
deleted file mode 100644
index 5c05727..0000000
Binary files a/media/1.3.1.1+FAST+PAIR/03187c9b096259e2fea8747010de6691.png and /dev/null differ
diff --git a/media/1.3.1.1+FAST+PAIR/03b5e8532bfbd9c5e78f3ca23df51c20.png b/media/1.3.1.1+FAST+PAIR/03b5e8532bfbd9c5e78f3ca23df51c20.png
deleted file mode 100644
index 60813ac..0000000
Binary files a/media/1.3.1.1+FAST+PAIR/03b5e8532bfbd9c5e78f3ca23df51c20.png and /dev/null differ
diff --git a/media/1.3.1.1+FAST+PAIR/043f058384a293e73a53923bff772afc.png b/media/1.3.1.1+FAST+PAIR/043f058384a293e73a53923bff772afc.png
deleted file mode 100644
index 783bf21..0000000
Binary files a/media/1.3.1.1+FAST+PAIR/043f058384a293e73a53923bff772afc.png and /dev/null differ
diff --git a/media/1.3.1.1+FAST+PAIR/0935c3983a9f6b7fc73b396e06d78dc3.png b/media/1.3.1.1+FAST+PAIR/0935c3983a9f6b7fc73b396e06d78dc3.png
deleted file mode 100644
index 3e31671..0000000
Binary files a/media/1.3.1.1+FAST+PAIR/0935c3983a9f6b7fc73b396e06d78dc3.png and /dev/null differ
diff --git a/media/1.3.1.1+FAST+PAIR/1f657ae36b57a71a1d4c427773998fe2.png b/media/1.3.1.1+FAST+PAIR/1f657ae36b57a71a1d4c427773998fe2.png
deleted file mode 100644
index 800ea8a..0000000
Binary files a/media/1.3.1.1+FAST+PAIR/1f657ae36b57a71a1d4c427773998fe2.png and /dev/null differ
diff --git a/media/1.3.1.1+FAST+PAIR/23d8f2c04f247380e20d168814631501.png b/media/1.3.1.1+FAST+PAIR/23d8f2c04f247380e20d168814631501.png
deleted file mode 100644
index b9a30c9..0000000
Binary files a/media/1.3.1.1+FAST+PAIR/23d8f2c04f247380e20d168814631501.png and /dev/null differ
diff --git a/media/1.3.1.1+FAST+PAIR/2401fff5f00ae7435cafdaf8752b722f.png b/media/1.3.1.1+FAST+PAIR/2401fff5f00ae7435cafdaf8752b722f.png
deleted file mode 100644
index d9d31f5..0000000
Binary files a/media/1.3.1.1+FAST+PAIR/2401fff5f00ae7435cafdaf8752b722f.png and /dev/null differ
diff --git a/media/1.3.1.1+FAST+PAIR/2b63da6b1faeb6f3ea8fcfbc7ba4d96a.png b/media/1.3.1.1+FAST+PAIR/2b63da6b1faeb6f3ea8fcfbc7ba4d96a.png
deleted file mode 100644
index 89b5e27..0000000
Binary files a/media/1.3.1.1+FAST+PAIR/2b63da6b1faeb6f3ea8fcfbc7ba4d96a.png and /dev/null differ
diff --git a/media/1.3.1.1+FAST+PAIR/2c887e8d44f0b7d6a9f8900d146329a4.png b/media/1.3.1.1+FAST+PAIR/2c887e8d44f0b7d6a9f8900d146329a4.png
deleted file mode 100644
index ee1db11..0000000
Binary files a/media/1.3.1.1+FAST+PAIR/2c887e8d44f0b7d6a9f8900d146329a4.png and /dev/null differ
diff --git a/media/1.3.1.1+FAST+PAIR/392c064173faa2951c00cadd7dfdda3c.png b/media/1.3.1.1+FAST+PAIR/392c064173faa2951c00cadd7dfdda3c.png
deleted file mode 100644
index d6251d2..0000000
Binary files a/media/1.3.1.1+FAST+PAIR/392c064173faa2951c00cadd7dfdda3c.png and /dev/null differ
diff --git a/media/1.3.1.1+FAST+PAIR/3c6dc775a227108e0bbba6b555aa32b3.png b/media/1.3.1.1+FAST+PAIR/3c6dc775a227108e0bbba6b555aa32b3.png
deleted file mode 100644
index f1efb99..0000000
Binary files a/media/1.3.1.1+FAST+PAIR/3c6dc775a227108e0bbba6b555aa32b3.png and /dev/null differ
diff --git a/media/1.3.1.1+FAST+PAIR/50d033783387d97216c65a8114f87853.png b/media/1.3.1.1+FAST+PAIR/50d033783387d97216c65a8114f87853.png
deleted file mode 100644
index 5fa2622..0000000
Binary files a/media/1.3.1.1+FAST+PAIR/50d033783387d97216c65a8114f87853.png and /dev/null differ
diff --git a/media/1.3.1.1+FAST+PAIR/52772a16ee0fcfa9700aff47528d8a24.png b/media/1.3.1.1+FAST+PAIR/52772a16ee0fcfa9700aff47528d8a24.png
deleted file mode 100644
index 946307e..0000000
Binary files a/media/1.3.1.1+FAST+PAIR/52772a16ee0fcfa9700aff47528d8a24.png and /dev/null differ
diff --git a/media/1.3.1.1+FAST+PAIR/57b199affa5c0c3a7559b0aad1c3724b.png b/media/1.3.1.1+FAST+PAIR/57b199affa5c0c3a7559b0aad1c3724b.png
deleted file mode 100644
index a5c0f40..0000000
Binary files a/media/1.3.1.1+FAST+PAIR/57b199affa5c0c3a7559b0aad1c3724b.png and /dev/null differ
diff --git a/media/1.3.1.1+FAST+PAIR/63044559a7bb37335a34c3e82d547cb3.png b/media/1.3.1.1+FAST+PAIR/63044559a7bb37335a34c3e82d547cb3.png
deleted file mode 100644
index 1a596f6..0000000
Binary files a/media/1.3.1.1+FAST+PAIR/63044559a7bb37335a34c3e82d547cb3.png and /dev/null differ
diff --git a/media/1.3.1.1+FAST+PAIR/800dcc6a460f70646d3ee1f58129b02f.png b/media/1.3.1.1+FAST+PAIR/800dcc6a460f70646d3ee1f58129b02f.png
deleted file mode 100644
index 0d00bdc..0000000
Binary files a/media/1.3.1.1+FAST+PAIR/800dcc6a460f70646d3ee1f58129b02f.png and /dev/null differ
diff --git a/media/1.3.1.1+FAST+PAIR/87be26035280a85301524861a8ac0da9.png b/media/1.3.1.1+FAST+PAIR/87be26035280a85301524861a8ac0da9.png
deleted file mode 100644
index 97a6207..0000000
Binary files a/media/1.3.1.1+FAST+PAIR/87be26035280a85301524861a8ac0da9.png and /dev/null differ
diff --git a/media/1.3.1.1+FAST+PAIR/90d99727d0c624cccc2b4a41e055b992.png b/media/1.3.1.1+FAST+PAIR/90d99727d0c624cccc2b4a41e055b992.png
deleted file mode 100644
index 2d6a42d..0000000
Binary files a/media/1.3.1.1+FAST+PAIR/90d99727d0c624cccc2b4a41e055b992.png and /dev/null differ
diff --git a/media/1.3.1.1+FAST+PAIR/93a20032a164b156ca9e612505c55791.png b/media/1.3.1.1+FAST+PAIR/93a20032a164b156ca9e612505c55791.png
deleted file mode 100644
index 6dea9c2..0000000
Binary files a/media/1.3.1.1+FAST+PAIR/93a20032a164b156ca9e612505c55791.png and /dev/null differ
diff --git a/media/1.3.1.1+FAST+PAIR/9e0eb1856a0898d3ed225d7049640661.png b/media/1.3.1.1+FAST+PAIR/9e0eb1856a0898d3ed225d7049640661.png
deleted file mode 100644
index 8b9ef28..0000000
Binary files a/media/1.3.1.1+FAST+PAIR/9e0eb1856a0898d3ed225d7049640661.png and /dev/null differ
diff --git a/media/1.3.1.1+FAST+PAIR/9f55833bffc337406d8ad3183f14d339.png b/media/1.3.1.1+FAST+PAIR/9f55833bffc337406d8ad3183f14d339.png
deleted file mode 100644
index cb58620..0000000
Binary files a/media/1.3.1.1+FAST+PAIR/9f55833bffc337406d8ad3183f14d339.png and /dev/null differ
diff --git a/media/1.3.1.1+FAST+PAIR/a34463886fa9bcdedf0635825d0616ab.png b/media/1.3.1.1+FAST+PAIR/a34463886fa9bcdedf0635825d0616ab.png
deleted file mode 100644
index be08f6d..0000000
Binary files a/media/1.3.1.1+FAST+PAIR/a34463886fa9bcdedf0635825d0616ab.png and /dev/null differ
diff --git a/media/1.3.1.1+FAST+PAIR/a644beb33819734765801b155f5f0bb4.png b/media/1.3.1.1+FAST+PAIR/a644beb33819734765801b155f5f0bb4.png
deleted file mode 100644
index 3738ce4..0000000
Binary files a/media/1.3.1.1+FAST+PAIR/a644beb33819734765801b155f5f0bb4.png and /dev/null differ
diff --git a/media/1.3.1.1+FAST+PAIR/ba5599cbe19710a0b8d35fa2cece0ea3.png b/media/1.3.1.1+FAST+PAIR/ba5599cbe19710a0b8d35fa2cece0ea3.png
deleted file mode 100644
index 788da83..0000000
Binary files a/media/1.3.1.1+FAST+PAIR/ba5599cbe19710a0b8d35fa2cece0ea3.png and /dev/null differ
diff --git a/media/1.3.1.1+FAST+PAIR/ba694c3d598f3288fe64317cb121bcc3.png b/media/1.3.1.1+FAST+PAIR/ba694c3d598f3288fe64317cb121bcc3.png
deleted file mode 100644
index 85f324a..0000000
Binary files a/media/1.3.1.1+FAST+PAIR/ba694c3d598f3288fe64317cb121bcc3.png and /dev/null differ
diff --git a/media/1.3.1.1+FAST+PAIR/bb33026d3bd31db5cae4fae209208ff4.png b/media/1.3.1.1+FAST+PAIR/bb33026d3bd31db5cae4fae209208ff4.png
deleted file mode 100644
index f92066e..0000000
Binary files a/media/1.3.1.1+FAST+PAIR/bb33026d3bd31db5cae4fae209208ff4.png and /dev/null differ
diff --git a/media/1.3.1.1+FAST+PAIR/bcd9b3c76d386f326fdd45a144328dab.png b/media/1.3.1.1+FAST+PAIR/bcd9b3c76d386f326fdd45a144328dab.png
deleted file mode 100644
index 537528d..0000000
Binary files a/media/1.3.1.1+FAST+PAIR/bcd9b3c76d386f326fdd45a144328dab.png and /dev/null differ
diff --git a/media/1.3.1.1+FAST+PAIR/c0e8b2bb4be8fc3ba806ebb6f2c53d39.png b/media/1.3.1.1+FAST+PAIR/c0e8b2bb4be8fc3ba806ebb6f2c53d39.png
deleted file mode 100644
index fed7d16..0000000
Binary files a/media/1.3.1.1+FAST+PAIR/c0e8b2bb4be8fc3ba806ebb6f2c53d39.png and /dev/null differ
diff --git a/media/1.3.1.1+FAST+PAIR/c476ea9a254033b107738a4399923a84.png b/media/1.3.1.1+FAST+PAIR/c476ea9a254033b107738a4399923a84.png
deleted file mode 100644
index f5c5824..0000000
Binary files a/media/1.3.1.1+FAST+PAIR/c476ea9a254033b107738a4399923a84.png and /dev/null differ
diff --git a/media/1.3.1.1+FAST+PAIR/c53c9297abe1a8e58e8a6bb451597cd9.png b/media/1.3.1.1+FAST+PAIR/c53c9297abe1a8e58e8a6bb451597cd9.png
deleted file mode 100644
index 51d4d99..0000000
Binary files a/media/1.3.1.1+FAST+PAIR/c53c9297abe1a8e58e8a6bb451597cd9.png and /dev/null differ
diff --git a/media/1.3.1.1+FAST+PAIR/c58a228e1cdc75d452396a889556769c.png b/media/1.3.1.1+FAST+PAIR/c58a228e1cdc75d452396a889556769c.png
deleted file mode 100644
index 7c846c2..0000000
Binary files a/media/1.3.1.1+FAST+PAIR/c58a228e1cdc75d452396a889556769c.png and /dev/null differ
diff --git a/media/1.3.1.1+FAST+PAIR/c6e4c5adda43f5ad0a784e16ad2cdf74.png b/media/1.3.1.1+FAST+PAIR/c6e4c5adda43f5ad0a784e16ad2cdf74.png
deleted file mode 100644
index 9c6df34..0000000
Binary files a/media/1.3.1.1+FAST+PAIR/c6e4c5adda43f5ad0a784e16ad2cdf74.png and /dev/null differ
diff --git a/media/1.3.1.1+FAST+PAIR/cb3e902b64e0abf0063e4ac29d3935b0.png b/media/1.3.1.1+FAST+PAIR/cb3e902b64e0abf0063e4ac29d3935b0.png
deleted file mode 100644
index b43deb9..0000000
Binary files a/media/1.3.1.1+FAST+PAIR/cb3e902b64e0abf0063e4ac29d3935b0.png and /dev/null differ
diff --git a/media/1.3.1.1+FAST+PAIR/d19e2b3c4a860ab0b6310a6e81f7c058.png b/media/1.3.1.1+FAST+PAIR/d19e2b3c4a860ab0b6310a6e81f7c058.png
deleted file mode 100644
index ed3863d..0000000
Binary files a/media/1.3.1.1+FAST+PAIR/d19e2b3c4a860ab0b6310a6e81f7c058.png and /dev/null differ
diff --git a/media/1.3.1.1+FAST+PAIR/d1f4e69a1ecc7f68fa8e7eaae54ffeac.png b/media/1.3.1.1+FAST+PAIR/d1f4e69a1ecc7f68fa8e7eaae54ffeac.png
deleted file mode 100644
index dca131d..0000000
Binary files a/media/1.3.1.1+FAST+PAIR/d1f4e69a1ecc7f68fa8e7eaae54ffeac.png and /dev/null differ
diff --git a/media/1.3.1.1+FAST+PAIR/d2e262415c1e2f9d9528dfff6d83ed79.png b/media/1.3.1.1+FAST+PAIR/d2e262415c1e2f9d9528dfff6d83ed79.png
deleted file mode 100644
index 5d6fe85..0000000
Binary files a/media/1.3.1.1+FAST+PAIR/d2e262415c1e2f9d9528dfff6d83ed79.png and /dev/null differ
diff --git a/media/1.3.1.1+FAST+PAIR/d7939a45f30ae3c7e67a65edf0cc28b8.png b/media/1.3.1.1+FAST+PAIR/d7939a45f30ae3c7e67a65edf0cc28b8.png
deleted file mode 100644
index 0b9fe97..0000000
Binary files a/media/1.3.1.1+FAST+PAIR/d7939a45f30ae3c7e67a65edf0cc28b8.png and /dev/null differ
diff --git a/media/1.3.1.1+FAST+PAIR/dafdadb61405ace826c4efea73f32a58.png b/media/1.3.1.1+FAST+PAIR/dafdadb61405ace826c4efea73f32a58.png
deleted file mode 100644
index 53b3a48..0000000
Binary files a/media/1.3.1.1+FAST+PAIR/dafdadb61405ace826c4efea73f32a58.png and /dev/null differ
diff --git a/media/1.3.1.1+FAST+PAIR/f12815534877e22c540fd6ad2314c46f.png b/media/1.3.1.1+FAST+PAIR/f12815534877e22c540fd6ad2314c46f.png
deleted file mode 100644
index 58b1105..0000000
Binary files a/media/1.3.1.1+FAST+PAIR/f12815534877e22c540fd6ad2314c46f.png and /dev/null differ
diff --git a/media/1.3.1.1+FAST+PAIR/f93dfe7bd322a3e78b7f4f8ca879f6a5.png b/media/1.3.1.1+FAST+PAIR/f93dfe7bd322a3e78b7f4f8ca879f6a5.png
deleted file mode 100644
index 7225804..0000000
Binary files a/media/1.3.1.1+FAST+PAIR/f93dfe7bd322a3e78b7f4f8ca879f6a5.png and /dev/null differ
diff --git a/media/GFPS+认证测试/90b2adad442da11e1f20eee390eaaa82.png b/media/GFPS+认证测试/90b2adad442da11e1f20eee390eaaa82.png
deleted file mode 100644
index fa59ec7..0000000
Binary files a/media/GFPS+认证测试/90b2adad442da11e1f20eee390eaaa82.png and /dev/null differ
diff --git a/model_id+注册.md b/model_id+注册.md
new file mode 100644
index 0000000..022dd98
--- /dev/null
+++ b/model_id+注册.md
@@ -0,0 +1,137 @@
+# model_id 注册
+
+
+
+
+
+- [参考链接：](#model_id注册-参考链接：)
+- [注册地址：](#model_id注册-注册地址：)
+- [注册新的model id:](#model_id注册-注册新的modelid:)
+- [Note:](#model_id注册-Note:)
+ - [1. 注册成功之后的 public key 和 private key 是 base64 形式的需要自己转化成hex(model id 本身就是hex格式 所以不需要转化) ，填入到mcu cfg tool 里的 public key 和 private key必须是hex形式的, 提供转化工具如下https://base64.guru/converter/decode/hex](#model_id注册-1.注册成功之后的publickey和privatekey是base64形式的需要自己转化成hex(modelid本身就是hex格式所以不需要转化)，填入到mcucfgtool里的publickey和privatekey必须是hex形式的,提供转化工具如下https://base64.guru/converter/decode/hex)
+ - [2. 如果注册model id的时候找不到对应的device type, 说明Google暂时不支援，需要PM/BD向Google提需求：](#model_id注册-2.如果注册modelid的时候找不到对应的devicetype,说明Google暂时不支援，需要PM/BD向Google提需求：)
+ - [3. 2024年以后注册的model id， 对应的project 需要请google 激活之后才可以使用，详细信息咨询 YT](#model_id注册-3.2024年以后注册的modelid，对应的project需要请google激活之后才可以使用，详细信息咨询YT)
+- [查看已注册信息：](#model_id注册-查看已注册信息：)
+
+
+
+#### 参考链接：
+
+https://developers.google.com/nearby/fast-pair/specifications/service/modelregistration#CreateModelId
+
+帮助文档;https://developers.google.com/nearby/devices/
+
+#### 注册地址：
+
+https://developers.google.com/nearby/devices/ (可以在该地址查看注册的model id和key的信息)
+
+#### 注册新的model id:
+
+右上角点击sign in, 使用google 账号和密码登陆。
+
+
+
+\
+
+如果尚未创建project，需要点击 Add project -》输入名称 -》Create project
+
+
+
+点击 Add device
+
+
+
+填写信息：
+
+
+
+\
+
+
+
+注册成功之后，可以查看model id和key的信息：
+
+
+
+\
+
+#### Note:
+
+##### 1. 注册成功之后的 public key 和 private key 是 base64 形式的需要自己转化成hex(model id 本身就是hex格式 所以不需要转化) ，填入到mcu cfg tool 里的 public key 和 private key必须是hex形式的, 提供转化工具如下https://base64.guru/converter/decode/hex
+
+for example:
+
+转化前 base64：
+
+转化后 hex:
+
+
+
+\
+
+##### 2. 如果注册model id的时候找不到对应的device type, 说明Google暂时不支援，需要PM/BD向Google提需求：
+
+hi @Tony.YS Liu @Vito Kao The customer's product is a printer, can we choose device type headphones to register model id?
+
+danni Realtek, \
+周五 18:11\
+Or do you have any suggestions?😃 thanks
+
+Tony.YS Liu, \
+周六 10:11\
+FastPair does not support printer, I'm not sure if there is any customization Seeker needs to make for this kind of device.\
+@Chris Chang should this request goes to BD and PM ?
+
+Chris Chang, \
+周六 17:52, 已修改\
+@danni Realtek please help the partner fill the form below. My Google BD colleague will reach out to the partner to know more details.\
+https://forms.gle/xX9j1Vc5PDJs8ahB7
+
+\
+
+##### 3. 2024年以后注册的model id， 对应的project 需要请google 激活之后才可以使用，详细信息咨询 YT
+
+Hi Realtek team,
+
+We’re reaching out to notify you that as of March 7, 2024
+
+如何激活请参考：
+
+ in order to activate your model id, we ask that OEMs first create a model ID and provide the model ID in the Google Fast Pair Audio Switch Device Proposal Form instead of emailing our team directly.
+
+ 如何注册请参考：
+
+The Fast Pair Overview has been updated to reflect this new process. See instructions on How to Register a Model ID.
+
+注册遇到问题请参考FAQ:
+
+As a reminder, partners can now check if a project has been activated in the Device Console. See details in the Fast Pair FAQ.
+
+
+
+Please let us know if you have any questions.
+
+Thanks,
+
+The Fast Pair Team
+
+#### 查看已注册信息：
+
+右上角点击sign in, 使用google 账号和密码登陆。
+
+
+
+\
+
+点击 Devices 查看已经创建的model id和key的信息：
+
+
+
+点击上图 对应的 model id 页面会自动跳转(比如点击 0xECF4AC)
+
+
diff --git a/ota成功之后，弹窗出现，如果不及时点击弹窗，弹窗显示几秒后就会消失.md b/ota成功之后，弹窗出现，如果不及时点击弹窗，弹窗显示几秒后就会消失.md
new file mode 100644
index 0000000..fd4678c
--- /dev/null
+++ b/ota成功之后，弹窗出现，如果不及时点击弹窗，弹窗显示几秒后就会消失.md
@@ -0,0 +1,17 @@
+# ota成功之后，弹窗出现，如果不及时点击弹窗，弹窗显示几秒后就会消失
+
+弹窗实际上没有真正的消失，只是隐藏了， 可以在下拉框中看到弹窗信息[BB2BUG-47700] [BB2][D-CUT][8763EKH][Harman][T530]Finder测试，耳机OTA到支持Finder的版本，手机没有弹框 - Jira
+
+\
+
+Status: Won't Fix (Intended Behavior)
+
+Hi Danni,
+
+This seems to be working as intended. The notification is shown briefly on the screen and then can be found by dragging down the notification panel (the top bar). From what I see in the bugreport it is not removed.
+
+Please reopen if you don't see this message in the notification panel.
+
+\
+
+
diff --git a/ota成功之后，手机没有重新查服务.md b/ota成功之后，手机没有重新查服务.md
new file mode 100644
index 0000000..fc4c0c5
--- /dev/null
+++ b/ota成功之后，手机没有重新查服务.md
@@ -0,0 +1,17 @@
+# ota成功之后，手机没有重新查服务
+
+原因大概是
+
+耳机支援LE audio, 所以BLE会走配对流程，
+
+ota成功之后因为之前BLE配对过，耳机和手机端都有存储LTK，所以手机会使用之前缓存的service table，
+
+手机端不重新查服务，使用之前缓存的service table， 因为之前缓存的service table是不支援finder的，
+
+所以ota成功之后不会有弹窗出来。
+
+需要咨询一下Google是手机端主动来查服务，还是我们发service change indication 请求手机端来查服务
+
+\
+
+[BB2BUG-47700] [BB2][D-CUT][8763EKH][Harman][T530]Finder测试，耳机OTA到支持Finder的版本，手机没有弹框 - Jira
diff --git a/owner+phone+taken+out+of+_Unwanted+Tracking+Protection+Mode_+fail.md b/owner+phone+taken+out+of+_Unwanted+Tracking+Protection+Mode_+fail.md
new file mode 100644
index 0000000..e056571
--- /dev/null
+++ b/owner+phone+taken+out+of+_Unwanted+Tracking+Protection+Mode_+fail.md
@@ -0,0 +1,118 @@
+# owner phone taken out of "Unwanted Tracking Protection Mode" fail
+
+hi Mark:\
+\
+Unwanted Tracking Prevention test:\
+Turn the owner's phone back online. Turn on the screen while in close range to the tested device. The device should be taken out of "Unwanted Tracking Protection Mode"\
+\
+we do not see owner's phone take out of "Unwanted Tracking Protection Mode"\
+\
+Turn the owner's phone back online, 15:39:37 BR reconnected;\
+we do not see owner's phone create LE link and take out of "Unwanted Tracking Protection Mode" ;\
+\
+15:40:45 open find my device app;\
+\
+thanks
+
+\
+
+#### gmark@google.com\google.com\> #2Mar 17, 2025 08:23PM
+
+Hi Danni,
+
+Per the included logs Finder (the GMS core component) deactivated UTP mode the device at 15:35:12:
+
+ 03-12 15:35:09.519 I AdvertisedStateHandler: Detected owned device with unwanted tracking protection mode: 41D6F9BAD972854BB4054180BD454A09C10E7A99B036 [CONTEXT service_id=284 ]
+ 03-12 15:35:12.425 I m.nkj : reading ES+FP Beacon Actions [CONTEXT service_id=284 ]
+ 03-12 15:35:12.655 I m.nkj : writing ES+FP Beacon Actions, data: 08XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX [CONTEXT service_id=284 ]
+ 03-12 15:35:12.739 I DeUnwantedTrackingIntOp: Deactivated unwanted tracking mode successfully. [CONTEXT service_id=284 ]
+
+Later the Inspector detected that UTP mode is indeed deactivated on this device:
+
+ 03-12 15:38:15.438 I UiLogger: Device found by EID D6F9BAD972854BB4054180BD454A09C10E7A99B0, time offset: 333 sec., UTP mode is inactive
+
+HCI traces only start at 15:38:27 so not possible to check what device advertised right after disabling the UTP mode, but from 15:38:27 it still advertised the same EID with the frame type 0x41 (UTP mode active). It seems that something enabled UTP mode between 15:38:15 and 15:38:27.
+
+
+
+Reassigned to gmark@google.com.
+
+\
+hi mark:\
+\
+1 .Per the included logs Finder (the GMS core component) deactivated UTP mode the device at 15:35:12\
+---\>15:35:12 We haven't started testing yet\
+\
+2. 15:38:18 owner phone, find my device app -\>Inspect-\> active unwanted tracking mode\
+0005109 03-12#15:38:18.642 109 0478109.262 \[APP\] gfps_handle_active_utp_request\
+\
+3. 15:39:37 Turn the owner's phone back online, BR reconnected\
+we do not see owner's phone create LE link and take out of "Unwanted Tracking Protection Mode" ;\
+\
+
+BB2BUG-47667-0312 (1).7z\
+7.7 MBDownload
+
+
+
+#### gmark@google.com\google.com\> #4Mar 19, 2025 08:56PM
+
+Reassigned to danni_dong@realtek.corp-partner.google.com.
+
+Hi Danni,
+
+Finder deactivates a UTP mode at most once per EID. If UTP mode is detected active after it was deactivated and the device still advertises the same EID, the UTP mode won't be deactivated again till EID rotates. I think this explains what you observed.
+
+
+
+#### Danni Dong\realtek.corp-partner.google.com\> #5Mar 20, 2025 04:53PM
+
+Reassigned to gmark@google.com.
+
+hi Mark:\
+It seems that we already set right frame type, please see Thu Mar 20 2025 16:49:34 GMT+0800 (中国标准时间).png\
+\
+How can we avoid this situation? thanks
+
+Thu Mar 20 2025 16:49:34 GMT+0800 (中国标准时间).png\
+67 KBViewDownload
+
+
+
+#### Danni Dong\realtek.corp-partner.google.com\> #6Mar 25, 2025 04:44PM
+
+hi Mark:\
+in finder spec:\
+\
+Turn off the owner's phone (or turn on airplane mode while Bluetooth is off) to prevent it from automatically deactivating the configuration. That should be done as quickly as possible after activating the "Unwanted Tracking Protection Mode".\
+\
+--\>Why does the owner phone will automatically deactivate the configuration? I see that sometimes owner phone will set to deactive mode in about 10 seconds, We don't have time to turn off owner phone in such a short time.\
+\
+\
+3. 15:39:37 Turn the owner's phone back online, BR reconnected\
+we do not see owner's phone create LE link and take out of "Unwanted Tracking Protection Mode" ;\
+---\>In this case, can we actively set it to deactive mode in the Find my device app? Will this affect certification?\
+\
+Our customers are anxious to pass the finder certification, but they always fail this test. Looking forward to your reply
+
+
+
+#### gmark@google.com\google.com\> #7Mar 26, 2025 06:45PM
+
+Reassigned to danni_dong@realtek.corp-partner.google.com.
+
+> Why does the owner phone will automatically deactivate the configuration?
+
+UTP mode should only be active when owner's phone is not nearby. For that reason the owner's phone will try to disable this mode as soon as it sees an owned device in this mode, unless it already tried to disable UTP for the same EID.
+
+> I see that sometimes owner phone will set to deactive mode in about 10 seconds, We don't have time to turn off owner phone in such a short time.
+
+There's no need to turn off the phone. It is enough to turn on the airplane mode (ensure that BT is off).
+
+Alternatively, I think you can do the following trick:
+
+1. **Make sure there are no other phones in BLE range with owner's account**
+2. Activate UTP mode in Inspector
+3. Wait till it gets automatically deactivated (check the line mid-screen that looks like "flags aa/bb (battery: NORMAL, UTP:inactive / 40)"
+4. Activate UTP mode in Inspector. Now it won't deactivate till EID rotates.
+5. Put the phone into airplane mode
diff --git a/pair+with+xx_xx_xx_xx_xx_xx+fail.md b/pair+with+xx_xx_xx_xx_xx_xx+fail.md
new file mode 100644
index 0000000..7706efe
--- /dev/null
+++ b/pair+with+xx_xx_xx_xx_xx_xx+fail.md
@@ -0,0 +1,13 @@
+# pair with xx:xx:xx:xx:xx:xx fail
+
+
+
+\
+
+https://partnerissuetracker.corp.google.com/u/0/issues/409459681
+
+\
+
+[BB2BUG-47642] [BB2][RTL8763ESH/ROM][GMI][沃莱特][Harman][T530][GFPS] 192 Subsequent pairing automated test fail - Jira
+
+\
diff --git a/provider支援lea,+phone不支援lea.md b/provider支援lea,+phone不支援lea.md
new file mode 100644
index 0000000..a1496a0
--- /dev/null
+++ b/provider支援lea,+phone不支援lea.md
@@ -0,0 +1,3 @@
+# provider支援lea, phone不支援lea
+
+[BB2BUG-52194] [BB2][D-CUT][8763EKH][Harman][T530][v3.13.2.20+Test bin] Fast pair Validator APP测试，Key Based Request Fiags Reserved Bit verification Test Fail - Jira
diff --git a/provider支援lea,+手机不支援lea.md b/provider支援lea,+手机不支援lea.md
new file mode 100644
index 0000000..4378dbe
--- /dev/null
+++ b/provider支援lea,+手机不支援lea.md
@@ -0,0 +1,3 @@
+# provider支援lea, 手机不支援lea
+
+[BB2BUG-52173] [BB2][D-CUT][8763EKH][Harman][T530][v3.13.2.20+Test bin] Fast pair Validator APP测试，Ringing A Device with classic profile connection Test Fail - Jira
diff --git a/provisioning+for+non-owner+fail--_Scan+the+device+by+model+id_+fail.md b/provisioning+for+non-owner+fail--_Scan+the+device+by+model+id_+fail.md
new file mode 100644
index 0000000..29d218a
--- /dev/null
+++ b/provisioning+for+non-owner+fail--_Scan+the+device+by+model+id_+fail.md
@@ -0,0 +1,13 @@
+# provisioning for non-owner fail--"Scan the device by model id" fail
+
+问题原因：
+
+测试开始前需要做factory reset，然后再开机让设备进入pairing mode，之后点击Test开始测试.
+
+测试过程中手机会提示让设备再次进入pairing mode， 这个时候一定不可以做factory reset， 可以配置按键进入pairing mode， 也可以关机再开机进入pairing mode， 但是一定不可以做factory reset。
+
+
+
+ BB2BUG-26243 - \[BB2\]\[C-CUT\]\[RTL8763EFL\]\[Harman\]\[T530\]\[v2.13.2.0\]\[Finder\]Provisioning for non owner fail Closed
+
+ BTQCSZ-6290 - \[BB2\]\[C-CUT\]\[8763EF\]\[HARMAN\]\[Finder\]provisioning for non-owner fail Resolved
diff --git a/provisioning+for+non-owner+fail--_invalid+authentication+not+rejected_.md b/provisioning+for+non-owner+fail--_invalid+authentication+not+rejected_.md
new file mode 100644
index 0000000..aa545d3
--- /dev/null
+++ b/provisioning+for+non-owner+fail--_invalid+authentication+not+rejected_.md
@@ -0,0 +1,99 @@
+# provisioning for non-owner fail--"invalid authentication not rejected"
+
+ BTQCSZ-6290 - \[BB2\]\[C-CUT\]\[8763EF\]\[HARMAN\]\[Finder\]provisioning for non-owner fail Resolved
+
+
+
+大概原因是finder spec v1.2 修改了 owner key 相关的东西
+
+导致
+
+provider 端用的owner account key 和 Fast pair validator seeker 端用的owner account key不一致导致的。
+
+\
+
+目前测试版本：Fast pair validator version: 3.0.538491127
+
+该版本只支持到 finder spec v1.1 ， 还不支持 finder spec v1.2
+
+\
+
+hi Avner:
+
+when we update finder spec to v1.2 and test " Provisioning for non-owner".
+
+it test failed with reason "invalid authentication not rejected"
+
+\
+
+The reason for fail is that:
+
+In finder spec v1.1 says:
+
+Owner Account Key: the first Account Key introduced to the Provider (for the first time\
+or after a factory reset).
+
+We use this version run fast pair validator, provisioning for non-owner can test PASS.
+
+However when we update to finder sepc 1.2:
+
+Owner Account Key: One of the existing Account Keys on the Provider will be chosen\
+as the Owner Account Key. At the latest, the Owner Account Key must be chosen on the\
+first time a Seeker accesses the Beacon Actions characteristic.
+
+So we choose the first Account Key that is used to read the provisioning\
+state as provider's owner.
+
+when we use this version test Provisioning for non-owner.
+
+step 1:
+
+seeker will pair with provider, but seeker do not read finder provisioning state,
+
+so provider does not think that the account key paired this time is the owner key.
+
+
+
+step 2:
+
+This is the first time Seeker accesses the Beacon Actions characteristic.
+
+so provider think that the account key paired this time is the owner key.
+
+However seeker show "Provisioning device using non-owner account key"
+
+
+
+step 3:
+
+test fail:
+
+
+
+can you help see the reason？
+
+thanks
+
+\
+
+Hi Danni,
+
+You are right, this Validator test still verifies behavior per spec v1.1. We will extend it to support v1.2. I'll let you know when the updated test is released.
+
+\
+
+Fast pair validator version: 3.0.538491127 版本只支持到 finder spec v1.1 还不支持 finder spec v1.2
+
+\
+
+Hi Danni,
+
+We updated the "Non-owner" test as described earlier, so that it is fully compatible with v1.2. This is included from version 3.0.552485558.
+
+\
+
+Hi Danni,
+
+Sorry, this got miscommunicated. 3.0.552485558 is a month-old version.
+
+The version containing the updated test got delayed and yet to be released next Monday. I'll confirm once this happens.
diff --git a/reason_+pairing+not+support.md b/reason_+pairing+not+support.md
new file mode 100644
index 0000000..10c8515
--- /dev/null
+++ b/reason_+pairing+not+support.md
@@ -0,0 +1,28 @@
+# reason: pairing not support
+
+ BB2BUG-18006 - \[BB2\]\[8773ESL\]\[v3.13.0.7\]\[GFPS\]\[LE Audio\] Subsequent Pairing Fail Resolved
+
+GFPS LE audio配对第二支手机的时候，耳机端答复 pairing not support，导致第二支手机配对失败.
+
+\
+
+查看code看好像只有le audio会设置GAP_PAIRING_MODE_NO_PAIRING，请您帮忙看看:\
+void app_lea_adv_stop(bool disable_pairable)\
+{\
+ mtc_stop_timer(MTC_TMR_CIS);
+
+ if (ble_ext_adv_mgr_disable(app_lea_adv_handle, 0) == GAP_CAUSE_SUCCESS)\
+ {\
+ if (disable_pairable == true)
+
+ { uint8_t pairable = GAP_PAIRING_MODE_NO_PAIRING;
+
+ gap_set_param(GAP_PARAM_BOND_LE_PAIRING_MODE, sizeof(uint8_t), &pairable);
+
+ }
+
+ }
+
+}\
+ \
+
diff --git a/test_match.py b/test_match.py
new file mode 100644
index 0000000..1e7bea3
--- /dev/null
+++ b/test_match.py
@@ -0,0 +1,6 @@
+import sys
+
+loc = "file:///C:/b1330068943497508f1faa4108fa1f75\r\n"
+src = "b1330068943497508f1faa4108fa1f75"
+print("Ends with:", loc.endswith(src))
+print("Ends with stripped:", loc.strip().endswith(src))
diff --git a/使用不支援lea的手机测试：Initial+pair+with+xxxx+fail.md b/使用不支援lea的手机测试：Initial+pair+with+xxxx+fail.md
new file mode 100644
index 0000000..d9b70ac
--- /dev/null
+++ b/使用不支援lea的手机测试：Initial+pair+with+xxxx+fail.md
@@ -0,0 +1,16 @@
+# 使用不支援lea的手机测试：Initial pair with xxxx fail
+
+
+
+\
+
+[BB2ULTRA-255] [BB2 Ultra][Transceiver SDK][RTL8763GWS][Harman]Add GFPS in speaker - Jira
+
+\
+
+测试失败原因是手机没有连 legacy profile 可以参考这个wiki 逐一排查 手机不连legacy profile - BT_Market - WIKI
+
+0001731 12-04#10:33:30.633 135 0891993.376 \[ENGAGE\] !\*\*connected: b2s 1\
+0001732 12-04#10:33:30.633 136 0891993.403 \[ENGAGE\] !\*\*connected: b2s, bd_addr 0C::C4::13::DE::0E::68, profs 0x00000000
+
+\
diff --git a/手机UI显示Wait+60000ms+for+the+connection+and+UUID+event+if+not+yet+received的时候手机端在等什么.md b/手机UI显示Wait+60000ms+for+the+connection+and+UUID+event+if+not+yet+received的时候手机端在等什么.md
new file mode 100644
index 0000000..edfc366
--- /dev/null
+++ b/手机UI显示Wait+60000ms+for+the+connection+and+UUID+event+if+not+yet+received的时候手机端在等什么.md
@@ -0,0 +1,25 @@
+# 手机UI显示Wait 60000ms for the connection and UUID event if not yet received的时候手机端在等什么
+
+手机UI显示 Wait 60000ms for the connection and UUID event if not yet received的时候手机端在等什么Connection以及UUID：
+
+\
+
+Connection：
+
+Dual mode支援LEA 是等LEA的ACL 连线以及legacy的ACL 连线
+
+Dual mode 不支援LEA 是等legacy 的ACL 连线
+
+\
+
+UUID:
+
+如果手机端开了Bypass Bluetooth LE Audio Allowlist ：
+
+
+
+\
+
+如果手机端没有开启Bypass Bluetooth LE Audio Allowlist ：
+
+手机默认应该是会连legacy profile 110B(Audio Sink) or 1108(Headset) or 111E(Hands Free)
diff --git a/手机不弹窗原因整理.md b/手机不弹窗原因整理.md
new file mode 100644
index 0000000..c360c6d
--- /dev/null
+++ b/手机不弹窗原因整理.md
@@ -0,0 +1,126 @@
+# 手机不弹窗原因整理
+
+首先请参考 GFPS 认证测试 - BT_Market - WIKI 确认环境配置
+
+如果弹窗还不出现，以下整理了一些常见的手机不弹窗的原因：
+
+1.如果手机端弹窗出现之后，一直不点击弹窗进行配对，弹窗的优先级就会降低，后面就有可能不会弹窗了，如果想要解决这个问题，只能是重启一下手机，来恢复弹窗的优先级。
+
+\
+
+2.正常情况下耳机进入pairing mode之后，手机会出现如下图所示的GFPS notification弹窗(弹窗图片可能不完全一样)
+
+
+
+\
+
+3.如果出现如下图所示的情况：
+
+只弹出小图标，下拉打开通知中心，在通知中心可以看到GFPS Notification。
+
+
+
+\
+
+4.不弹窗还有可能是手机开启了勿扰模式，请把勿扰模式关闭。关闭方式如下图：
+
+
+
+\
+
+5.确保手机setting界面：位置信息-》使用位置信息已经打开
+
+\
+
+如果客户注册的model id 不弹窗，可以请QC换成场内测试model id试试看，如果场内测试model id可以弹窗， 那可能是客户注册的model id有问题， model id注册参考 [model_id 注册](/pages/viewpage.action?pageId=157379126)
+
+**Note:**
+
+20240101之后注册的model id 好像需要google设置成active 之后才可以使用，如果注册model id页面有如下提示：
+
+
+
+需要FAE帮助客户向 Realtek YT(YingTsung (YT) Lin) 提ticket， 提了ticket之后， google就会帮忙激活这个model id
+
+\
+
+6.如果始终不出现GFPS Notification弹窗。\
+可以将手机靠近耳机，如果靠近后出现GFPS Notification弹窗，说明GFPS Advertising Data中的TX Power Level设置的不对，需要重新调整(增大tx power 缩小被发现的距离，减小tx power 增大被发现的距离)。\
+如果调整mcu cfg tool 中的tx power之后仍然不起作用，请查看注册model id的时候是不是有设置tx power, 如果注册model id的时候有设置tx power, mcu cfg tool中设置的tx power就不会起作用。
+
+
+
+\
+
+7.如果手机靠近耳机后还是不出现GFPS Notification弹窗，可以用另外一只手机试一下。如果另外一只手机也没有出现，看一下是不是耳机的问题(耳机gfps adv是否正常广播，广播包的内容是否正确)。
+
+ 7.1 initial pair(discoverable mode) adv data 格式如下：
+
+ gfps_gen_adv_data: adv mode 0, tx_power -19, popup_show_ui 1, adv data 02 01 19 02 0A ED 06 16 2C FE EC F4 AC, len 13
+
+ 红色位置是GFPS service UUID 0xFE2C
+
+ 绿色位置是model id
+
+ 7.2 subsequent pair(nondiscoverable mode) adv data 格式如下：
+
+ gfps_gen_adv_data: adv mode 1, tx_power -19, popup_show_ui 1, adv data 02 01 19 02 0A ED 0B 16 2C FE 00 40 18 04 88 80 11 72, len 18
+
+ 红色位置是GFPS service UUID 0xFE2C
+
+ 绿色位置是account key length 和 type: 0x40是指length是4(对应一个account key), type是0(对应show ui)
+
+ 以下是一个错误的log：
+
+ gfps_gen_adv_data: adv mode 1, tx_power -19, popup_show_ui 1, adv data 02 01 19 02 0A ED 07 16 2C FE 00 **00** 11 C4, len 14
+
+ 红色位置是account key length 和 type，**00**是指耳机端没有account key,**在没有account key的情况下做subsequent pair，这肯定是有问题的**。
+
+\
+
+8.如果弹框仍然不出现，可以手动点击一下，setting\>Google\>开发者 Firebase App Indexing 手动刷新一下里面的内容,然后重启手机。
+
+\
+
+9.如果subsequent pairing过程中弹窗没有出现，
+
+ 9.1 除了上面列出的原因之外，请确认一下google的网络是不是可用，以及Settings\>Google\>Devices\>Saved devices界面下是否已经有同步的saved device,
+
+ 如果没有saved device，手机肯定不会弹窗的，这个时候要确认一下Google网络是否正常
+
+ 
+
+ 9.2 如果saved device里面有设备，但是依然没有弹窗，需要考虑是否account key filter 生成的有问题 ， 验证脚本：verify_bloom_filter.py 验证文档 Fast Pair Bloom Filter 验证工具 - README.md
+
+ Line 24586: 0004564 03-06#16:43:44.479 015 0033813.407 \[APP\] !\*\*gfps_gen_account_key_filter: key 04 1D 75 FB 16 47 B7 91 07 EB 69 50 D2 68 9A CD\
+ Line 24587: 0004565 03-06#16:43:44.479 016 0033813.599 \[APP\] !\*\*gfps_gen_account_key_filter: key 04 1D 75 FB 16 47 B7 91 07 EB 69 50 D2 68 9A CD\
+ Line 24588: 0004566 03-06#16:43:44.479 017 0033813.750 \[APP\] !\*\*gfps_gen_account_key_filter: key 04 1D 75 FB 16 47 B7 91 07 EB 69 50 D2 68 9A CD\
+ Line 24589: 0004567 03-06#16:43:44.479 018 0033813.903 \[APP\] !\*\*gfps_gen_account_key_filter: key 04 1D 75 FB 16 47 B7 91 07 EB 69 50 D2 68 9A CD\
+ Line 24590: 0004568 03-06#16:43:44.479 019 0033814.055 \[APP\] !\*\*gfps_gen_account_key_filter: key 04 1D 75 FB 16 47 B7 91 07 EB 69 50 D2 68 9A CD\
+ Line 24591: 0004569 03-06#16:43:44.479 020 0033814.211 \[APP\] !\*\*gfps_gen_account_key_filter: filter 21 00 04 00 28 40 04 00 00
+
+\
+
+6 用客户自己注册的model id不弹窗，用rtk认证过的model id就可以弹窗 - BT_Market - WIKI6 用客户自己注册的model id不弹窗，用rtk认证过的model id就可以弹窗 - BT_Market - WIKI
+
+6 同一个手机搭配RTK耳机不会弹窗，搭配竞品耳机可以弹窗 - BT_Market - WIKI
+
+6 弹窗功能测试时手机不弹窗 - BT_Market - WIKI
+
+21 android 13设备无GFPS弹窗 - BT_Market - WIKI
+
+22 Android 12 GFPS不弹窗 - BT_Market - WIKI
+
+ BBPRO2BUG-21347 - \[BBPro2\]\[RTL8773CO SDK\]\[沃莱特/飞利浦\]\[RHA\]GFPS 30cm 不弹框 Closed
+
+ BB2BUG-7057 - \[BB2\]\[RTL8763EF/ROM\]\[GMI\]\[沃莱特\]\[Harman\]\[T520\]\[133\]: google手机不弹窗 Closed
+
+ BB2BUG-5778 - \[BB2\]\[RTL8763EF/ROM\]\[GMI\]\[沃莱特\]\[Harman\]\[T520\]\[JBL1366\]: 谷歌6P和谷歌6手机登陆相同的账号，耳机多次开机进入配对与谷歌6P配对，谷歌6手机概率出现不弹窗 Closed
+
+ BB2BUG-5654 - \[BB2\]\[RTL8763EF/ROM\]\[GMI\]\[沃莱特\]\[Harman\]\[T520\]\[127\]:谷歌快速配对，耳机开机进配对，靠近两个谷歌手机，只有一个手机能弹窗 Closed
+
+ BB2BUG-5377 - \[BB2\]\[RTL8763EF/ROM\]\[GMI\]\[沃莱特\]\[Harman\]\[T520\]: google手机快速配对不弹窗的 Closed
+
+ BUMBEEBUG-7880 - \[BBlite\]\[8753BFJ\]\[凯力威\]\[QCY\]\[TW02\]\[ v1.7.5.1\]: GFPS 第三次开机谷歌不弹出窗口了 Closed
+
+ BB2RD-2200 - \[GFPS\]\[LEA\] subsequent pair 手机 nrf connect scan不到GFPS adv Closed
diff --git a/手机不连legacy+profile.md b/手机不连legacy+profile.md
new file mode 100644
index 0000000..13ddb02
--- /dev/null
+++ b/手机不连legacy+profile.md
@@ -0,0 +1,126 @@
+# 手机不连legacy profile
+
+目前遇到以下原因，可以逐一排查：
+
+
+
+
+
+- [Note: 首先查看设备端log是否有什么异常， 如果确定设备端log一切正常, 麻烦check以下原因：](#id-手机不连legacyprofile-Note:首先查看设备端log是否有什么异常，如果确定设备端log一切正常,麻烦check以下原因：)
+- [原因1：可能是手机系统蓝牙出了问题，setting界面 system\>reset options\>reset Bluetooth & wifi , 然后重启手机试试看](#id-手机不连legacyprofile-原因1：可能是手机系统蓝牙出了问题，setting界面system%3Eresetoptions%3EresetBluetooth&wifi,然后重启手机试试看)
+- [原因2：如果设备端不支援LEA，和支援LEA的手机对测，发现手机不连legacy profile， 需要打开 legacy CTKD LE 的功能(已确认原因5修正之后，不需要打开CTKD也可以正常连legacy profile)](#id-手机不连legacyprofile-原因2：如果设备端不支援LEA，和支援LEA的手机对测，发现手机不连legacyprofile，需要打开legacyCTKDLE的功能(已确认原因5修正之后，不需要打开CTKD也可以正常连legacyprofile))
+- [原因3： 如果设备端支援LEA，和不支援LEA的手机对测，发现手机不连legacy profile， 需要关闭 legacy CTKD LE 的功能，这个是Google的bug，(只有Android 12 复现)](#id-手机不连legacyprofile-原因3：如果设备端支援LEA，和不支援LEA的手机对测，发现手机不连legacyprofile，需要关闭legacyCTKDLE的功能，这个是Google的bug，(只有Android12复现))
+- [原因4：测试账号连的设备太多了，需要定期清除](#id-手机不连legacyprofile-原因4：测试账号连的设备太多了，需要定期清除)
+ - [4.1 setting界面清掉所有的配对信息 1 gfps/finder 如何清除配对信息 - BT_Market - WIKI](#id-手机不连legacyprofile-4.1setting界面清掉所有的配对信息1gfps/finder如何清除配对信息-BT_Market-WIKI)
+ - [4.2 Go to Settings \> Google \> All services \> Devices \> Saved devices：](#id-手机不连legacyprofile-4.2GotoSettings%3EGoogle%3EAllservices%3EDevices%3ESaveddevices：)
+ - [4.2.1 Toggle off Automatically saved devices](#id-手机不连legacyprofile-4.2.1ToggleoffAutomaticallysaveddevices)
+ - [4.2.2 Wait for about 3 hours, toggling on again.](#id-手机不连legacyprofile-4.2.2Waitforabout3hours,togglingonagain.)
+ - [4.2.3 Try to do the test again and see if this issue still happens.](#id-手机不连legacyprofile-4.2.3Trytodothetestagainandseeifthisissuestillhappens.)
+- [原因5： 设备不支援Lea, Pixel 7 (Android 16) Initial Pair fail， 手机不连legacy profile(原因是设备不支援lea,但是有配置lea的cod),不确定这个问题修正之后，是不是 原因2就不用开CTKD做workaround了((已确认原因5修正之后，原因2不需要打开CTKD也可以正常连legacy profile))](#id-手机不连legacyprofile-原因5：设备不支援Lea,Pixel7(Android16)InitialPairfail，手机不连legacyprofile(原因是设备不支援lea,但是有配置lea的cod),不确定这个问题修正之后，是不是原因2就不用开CTKD做workaround了((已确认原因5修正之后，原因2不需要打开CTKD也可以正常连legacyprofile)))
+ - [1 如果我们设备不支援lea, 不能打开lea的cod， 如果确认开了，需要将LE audio取消勾选：](#id-手机不连legacyprofile-1如果我们设备不支援lea,不能打开lea的cod，如果确认开了，需要将LEaudio取消勾选：)
+ - [2 如果我们设备不支援lea, GAP BLE Appearance 不能设置成Category Wearable Audio Device， 如果设置了，需要改成其他的](#id-手机不连legacyprofile-2如果我们设备不支援lea,GAPBLEAppearance不能设置成CategoryWearableAudioDevice，如果设置了，需要改成其他的)
+ - [3 如果我们设备不支援lea BLE Advertising data 中 appearance不能设置成Category Wearable Audio Device，如果设置了 需要改成其他的](#id-手机不连legacyprofile-3如果我们设备不支援leaBLEAdvertisingdata中appearance不能设置成CategoryWearableAudioDevice，如果设置了需要改成其他的)
+- [原因6： 设备不支援Lea, Pixel 7 (Android 13) Initial Pair fail， 手机不连legacy profile](#id-手机不连legacyprofile-原因6：设备不支援Lea,Pixel7(Android13)InitialPairfail，手机不连legacyprofile)
+
+
+
+#### Note: 首先查看设备端log是否有什么异常， 如果确定设备端log一切正常, 麻烦check以下原因：
+
+#### 原因1：可能是手机系统蓝牙出了问题，setting界面 system\>reset options\>reset Bluetooth & wifi , 然后重启手机试试看
+
+
+
+\
+
+#### 原因2：如果设备端不支援LEA，和支援LEA的手机对测，发现手机不连legacy profile， 需要打开 legacy CTKD LE 的功能(已确认原因5修正之后，不需要打开CTKD也可以正常连legacy profile)
+
+[BB2BUG-52936] [BB2][C-CUT][8763ESE][Amazon][v3.13.3.8+test bin]GG19手机（支持LEA手机）点击gfps弹窗连接耳机，连接失败 - Jira
+
+1 GFPS legacy pair 搭配支援LEA手机不连 legacy profile(A2DP/HFP) - BT_Market - WIKI
+
+\
+
+
+
+\
+
+#### 原因3： 如果设备端支援LEA，和不支援LEA的手机对测，发现手机不连legacy profile， 需要关闭 legacy CTKD LE 的功能，这个是Google的bug，(只有Android 12 复现)
+
+4 pixel6(android 12) 不连A2DP - BT_Market - WIKI
+
+\
+
+#### 原因4：测试账号连的设备太多了，需要定期清除
+
+##### 4.1 setting界面清掉所有的配对信息 1 gfps/finder 如何清除配对信息 - BT_Market - WIKI
+
+##### **4.2 Go to `Settings > Google > All services > Devices > Saved devices：`**
+
+###### ** 4.2.1 Toggle off `Automatically saved devices`**
+
+###### ** 4.2.2 Wait for about 3 hours, toggling on again.**
+
+###### ** 4.2.3 Try to do the test again and see if this issue still happens.**
+
+\
+
+#### 原因5： 设备不支援Lea, Pixel 7 (Android 16) Initial Pair fail， 手机不连legacy profile(原因是设备不支援lea,但是有配置lea的cod),**不确定这个问题修正之后，是不是 原因2就不用开CTKD做workaround了((已确认原因5修正之后，原因2不需要打开CTKD也可以正常连legacy profile))**
+
+**[BB2BUG-52936] [BB2][C-CUT][8763ESE][Amazon][v3.13.3.8+test bin]GG19手机（支持LEA手机）点击gfps弹窗连接耳机，连接失败 - Jira **
+
+GG19 Pixel7（16） 弹窗显示连接，进入setting端显示未连接
+
+143724点击gfps弹窗连接，143745显示连接成功，切到setting端则显示未连接上
+
+Line 8385: 0008293 01-06#14:37:30.084 057 0011801.851 \[APP\] !\*\*connected: b2s, bd_addr AC::3E::B1::72::92::ED, profs 0x00000000
+
+[BB2BUG-53526] [BB2][RTL8763ESE][Amazon/OSM][头戴立体声耳机][OSHA-79]实验室反馈使用部分手机没办法实现google fast pair连接 - Jira
+
+https://partnerissuetracker.corp.google.com/u/0/issues/473712440
+
+https://partnerissuetracker.corp.google.com/issues/474043881
+
+需要check以下地方：
+
+##### **1 如果我们设备不支援lea, 不能打开lea的cod， 如果确认开了，需要将LE audio取消勾选：**
+
+
+
+\
+
+##### **2 如果我们设备不支援lea, GAP BLE Appearance 不能设置成Category Wearable Audio Device， 如果设置了，需要改成其他的**
+
+GAP_APPEARANCE_CATEGORY_WEARABLE_AUDIO_DEVICE
+
+
+
+##### 3 **如果我们设备不支援lea BLE Advertising data 中 appearance不能设置成Category Wearable Audio Device，如果设置了 需要改成其他的**
+
+GAP_APPEARANCE_CATEGORY_WEARABLE_AUDIO_DEVICE
+
+
+
+\
+
+
+
+
+
+\
+
+你看下air中的page交互就可以，耳机给的FHS会带COD信息的
+
+
+
+\
+
+\
+
+#### 原因6： 设备不支援Lea, Pixel 7 (Android 13) Initial Pair fail， 手机不连legacy profile
+
+https://partnerissuetracker.corp.google.com/issues/475999795#attachment72551864
diff --git a/手机本来应该连主耳并且配对主耳的，但是手机却连了附耳，并且尝试配对附耳.md b/手机本来应该连主耳并且配对主耳的，但是手机却连了附耳，并且尝试配对附耳.md
new file mode 100644
index 0000000..7812c4f
--- /dev/null
+++ b/手机本来应该连主耳并且配对主耳的，但是手机却连了附耳，并且尝试配对附耳.md
@@ -0,0 +1,78 @@
+# 手机本来应该连主耳并且配对主耳的，但是手机却连了附耳，并且尝试配对附耳
+
+
+
+\
+
+hi hao:\
+\
+The provider is TWS earbuds and has two components.\
+\
+**The specifications state that if a pairing request is not received within 10 seconds after receiving the KBP request, we can manually disconnect the connection.**\
+**Our headset also follows this procedure. Please check why the pairing process wasn't initiated immediately after the phone sent the KBP request.**\
+\
+primary address：DD 24 DD 97 DD 00\
+secondary address： AA 24 AA 97 AA 00\
+\
+\
+\
+**//primary log: send kbp response**\
+ Line 104464: 0004415 12-15#16:32:19.890 008 0059128.956 \[APP\] !\*\*gfps_send_kbp_response_le: raw response 02 40 02 DD 24 DD 97 DD 00 AA 24 AA 97 AA 00 E3, encrypt response FA E9 BA 53 23 56 FA 0A 55 E1 2E A6 F1 84 14 5A\
+\
+**//primary not receive pairing request, and disconnect ACL link **\
+Line 121857: 0001804 12-15#16:32:29.865 238 0069100.729 \[APP\] app_gfps_timer_timeout_cb: timer_id 2, timer_chann 0\
+ Line 121959: 0001906 12-15#16:32:29.881 085 0069117.146 \[APP\] app_gfps_le_disconnect_cb: conn_id 0, local_disc_cause 17, disc_cause 0x116\
+\
+**//it seems seeker connected to the secondary bud?**\
+\
+can you help see the reason?
+
+\
+
+hi hao:\
+**XX:XX:XX:XX:AA:00 is secondary buds,**\
+**I think the phone shouldn't connected to the secondary buds,**\
+**because after the primary buds(address: DD 24 DD 97 DD 00) send kbps response to phone,**\
+**it seems the phone directly connects to the secondary buds(address: AA 24 AA 97 AA 00).**\
+\
+//primary buds log: 16:32:19 send kbp response to phone\
+ Line 104464: 0004415 12-15#16:32:19.890 008 0059128.956 \[APP\] !\*\*gfps_send_kbp_response_le: raw response 02 40 02 DD 24 DD 97 DD 00 AA 24 AA 97 AA 00 E3, encrypt response FA E9 BA 53 23 56 FA 0A 55 E1 2E A6 F1 84 14 5A\
+\
+//primary buds not receive create bond info, and disconnect ACL link \
+Line 121857: 0001804 12-15#16:32:29.865 238 0069100.729 \[APP\] app_gfps_timer_timeout_cb: timer_id 2, timer_chann 0\
+ Line 121959: 0001906 12-15#16:32:29.881 085 0069117.146 \[APP\] app_gfps_le_disconnect_cb: conn_id 0, local_disc_cause 17, disc_cause 0x116
+
+\
+
+Hi Danni,
+
+**After checking bluetooth manager log, looks like still in the bonding process with `xx:xx:xx:xx:AA:00`. Then, it start next round pairing.**
+
+ // After
+ shim::legacy::btm 2025-12-15 16:32:19.164 CBACK Bond state changed : xx:xx:xx:xx:aa:00 bt_status:fail bond_state:0 reason:HCI_SUCCESS
+ shim::legacy::btm 2025-12-15 16:32:19.199 SMP Security state changed : xx:xx:xx:xx:aa:00[public] SMP_STATE_IDLE => SMP_STATE_WAIT_APP_RSP
+ shim::legacy::btm 2025-12-15 16:32:19.200 SMP Security state changed : xx:xx:xx:xx:aa:00[public] SMP_STATE_WAIT_APP_RSP => SMP_STATE_PAIR_REQ_RSP
+ shim::legacy::btm 2025-12-15 16:32:19.266 API Get connection state : xx:xx:xx:xx:aa:00 connected:T classic_encrypted:F le_encrypted:F
+ shim::legacy::btm 2025-12-15 16:32:19.290 SMP Security state changed : xx:xx:xx:xx:aa:00[public] SMP_STATE_PAIR_REQ_RSP => SMP_STATE_PUBLIC_KEY_EXCH
+ shim::legacy::btm 2025-12-15 16:32:19.805 SMP Security state changed : xx:xx:xx:xx:aa:00[public] SMP_STATE_PUBLIC_KEY_EXCH => SMP_STATE_SEC_CONN_PHS1_START
+ shim::legacy::btm 2025-12-15 16:32:19.811 SMP Security state changed : xx:xx:xx:xx:aa:00[public] SMP_STATE_SEC_CONN_PHS1_START => SMP_STATE_WAIT_COMMITMENT
+
+ // Start subsequent pairing
+ shim::legacy::btm 2025-12-15 16:32:20.044 ACL Allow connection from : xx:xx:xx:xx:fd:93[random] Le
+ shim::legacy::btm 2025-12-15 16:32:20.075 ACL Connection successful : xx:xx:xx:xx:fd:93[random] Le
+ shim::legacy::btm 2025-12-15 16:32:20.149 API Get connection state : xx:xx:xx:xx:fd:93 connected:T classic_encrypted:F le_encrypted:F
+
+ // The interaction with XX:XX:XX:XX:AA:00 persists unexpectedly.
+ shim::legacy::btm 2025-12-15 16:32:20.326 SMP Security state changed : xx:xx:xx:xx:aa:00[public] SMP_STATE_WAIT_COMMITMENT => SMP_STATE_WAIT_NONCE
+ shim::legacy::btm 2025-12-15 16:32:20.405 SMP Security state changed : xx:xx:xx:xx:aa:00[public] SMP_STATE_WAIT_NONCE => SMP_STATE_SEC_CONN_PHS2_START
+ shim::legacy::btm 2025-12-15 16:32:20.406 SMP Security state changed : xx:xx:xx:xx:aa:00[public] SMP_STATE_SEC_CONN_PHS2_START => SMP_STATE_WAIT_NONCE
+ shim::legacy::btm 2025-12-15 16:32:20.406 SMP Security state changed : xx:xx:xx:xx:aa:00[public] SMP_STATE_WAIT_NONCE => SMP_STATE_WAIT_APP_RSP
+ shim::legacy::btm 2025-12-15 16:32:20.407 CBACK Bond state changed : xx:xx:xx:xx:aa:00 bt_status:success bond_state:1 reason:HCI_SUCCESS
+ shim::legacy::btm 2025-12-15 16:32:20.407 CBACK SSP ble request : xx:xx:xx:xx:aa:00 name:'' BT_SSP_VARIANT_CONSENT
+
+**Regarding why the Pixel phone re-creates a bond immediately after the Validator unpairs, I believe this is related to a BT known issue that should be fixed in the latest image.**\
+However, I'm unsure about the failure rate.\
+Is this bug easily reproducible on your side? And, more importantly, is it blocking your testing?\
+If it is, I will need to find a workaround to prevent it.
+
+\
diff --git a/支援lea的手机不打开bypass功能+retroactive+pair+fail.md b/支援lea的手机不打开bypass功能+retroactive+pair+fail.md
new file mode 100644
index 0000000..0cfd4a1
--- /dev/null
+++ b/支援lea的手机不打开bypass功能+retroactive+pair+fail.md
@@ -0,0 +1,7 @@
+# 支援lea的手机不打开bypass功能 retroactive pair fail
+
+https://partnerissuetracker.corp.google.com/u/0/issues/471311353
+
+[BBPRO3BUG-27201] [BBPRO3][EVB][E Cut][PEGA_HA_v1.0.4_20251106][24110 testbin][GFPS]与手机蓝牙连线，弹出GFPS弹窗点击保存，一直无查找设备功能 - Jira
+
+
diff --git a/耳机log：gfps_handle_beacon_provision_request_+authen+fail.md b/耳机log：gfps_handle_beacon_provision_request_+authen+fail.md
new file mode 100644
index 0000000..cb52b33
--- /dev/null
+++ b/耳机log：gfps_handle_beacon_provision_request_+authen+fail.md
@@ -0,0 +1,25 @@
+# 耳机log：gfps_handle_beacon_provision_request: authen fail
+
+[BB2BUG-50928] [BB2][RTL8763ESH/ROM][GMI][沃莱特/MINAMI][Harman][Pace][JBLES2-1935] Finder Provisioning for non-owner 测试不通过 - Jira
+
+原因是耳机端factory reset的时候没有清掉gfps和finder的account信息，导致finder用错owner key
+
+
+
+
+ 0007959 06-25#19:00:06.905 180 0059896.568 [APP] !**gfps_get_owner_key_valid: 1
+ 0007960 06-25#19:00:06.905 181 0059896.589 [APP] gfps_finder_get_owner_accountkey: valid 1, key 04 86 A6 1D 8F 3D 95 D2 00 FF 68 09 63 D2 B6 19
+ 0007961 06-25#19:00:06.905 182 0059896.617 [APP] gfps_finder_get_random_nonce: 5B 81 05 C2 C9 88 40 2A
+ 0007962 06-25#19:00:06.905 183 0059897.050 [APP] !**gfps_hmac_sha256: 94 4D 00 B1 03 47 01 D0
+ 0007963 06-25#19:00:06.905 184 0059897.077 [APP] !!!gfps_finder_verify_authkey: fail
+ 0007964 06-25#19:00:06.905 185 0059904.584 [APP] gfps_finder_set_random_nonce: 26 A4 21 CC 55 F2 9F 6D
+ 0007965 06-25#19:00:06.905 186 0059904.605 [APP] gfps_handle_beacon_provision_request: authen fail reset random nonce 26 A4 21 CC 55 F2 9F 6D |
+
+
+
+
+filter的length是9 bytes， 对应存储了5组key, 1.2\*5 +3= 9
+
+| |
+|----|
+| 0035272 06-25#19:00:59.329 002 0024188.405 \[APP\] !\*\*gfps_gen_account_key_filter: filter 03 AE 4B 34 13 D1 BC 06 CA |
diff --git a/设备有打non+discoverable+adv,+依然报device+not+found+by+AK.md b/设备有打non+discoverable+adv,+依然报device+not+found+by+AK.md
new file mode 100644
index 0000000..2662284
--- /dev/null
+++ b/设备有打non+discoverable+adv,+依然报device+not+found+by+AK.md
@@ -0,0 +1,7 @@
+# 设备有打non discoverable adv, 依然报device not found by AK
+
+看样子是owner key被覆盖掉了， 应该是code porting的有问题
+
+
+
+[BB2BUG-53010] [BB2][C-CUT][8763ESE][Amazon][v3.13.3.8+test bin][GFPS]provisioning for non-owner测试失败 - Jira
diff --git a/配对成功之后+setting界面+音频设备类型+是灰色的.md b/配对成功之后+setting界面+音频设备类型+是灰色的.md
new file mode 100644
index 0000000..3b045ff
--- /dev/null
+++ b/配对成功之后+setting界面+音频设备类型+是灰色的.md
@@ -0,0 +1,5 @@
+# 配对成功之后 setting界面 音频设备类型 是灰色的
+
+
+
+[BBPRO3BUG-28011] [BBPRO3][EVB][E Cut][SDK_Gaming_Stereo_v3.15.0.8_0128][Single][NonLEA]Retroactively Write Account Key，设备详细信息中“音频设备类型”置灰 - Jira
diff --git a/附耳没有收到UUID+0x184E.md b/附耳没有收到UUID+0x184E.md
new file mode 100644
index 0000000..11b5b95
--- /dev/null
+++ b/附耳没有收到UUID+0x184E.md
@@ -0,0 +1,211 @@
+# 附耳没有收到UUID 0x184E
+
+[BBPRO3BUG-27045] [BBPRO3][EVB][E Cut][PEGA_HA_v1.0.4_20251106][24110 testbin][GFPS][FastPair][LEA phone]Personalized Name Update 测试 fail - Jira
+
+https://partnerissuetracker.corp.google.com/u/0/issues/473688165
+
+
+
+\
+
+
+
+\
+
+hi hao:\
+\
+The provider is TWS earbuds and has two components.\
+\
+primary address：20 24 19 97 88 00\
+secondary address： 19 00 17 17 00 19\
+\
+17:07:47 Fast Pair validator show "Pairing process error: Reason: Only receive correct UUID from 1 address"\
+At this point, on the phone side, is it to check if the UUID 0x184E has been received?\
+\
+//maybe seeker already received 0x184E?\
+01-05 17:07:47.413 10186 2772 5000 I NearbyDiscovery: FastPairUtils: isBluetoothDeviceSupportingTargetUuid: Target profile found, profile=0000184e-0000-1000-8000-00805f9b34fb, mac=XX:XX:XX:XX:00:19 \[CONTEXT service_id=265 \]\
+01-05 17:07:47.413 10186 2772 5000 I NearbyDiscovery: FastPairUtils: isBluetoothDeviceSupportingLeaUuid: Lea profile found, mac=XX:XX:XX:XX:00:19 \[CONTEXT service_id=265 \]\
+\
+\
+\
+can you help see the reason?\
+\
+\
+thanks
+
+bugreport-caiman_beta-BP41.250916.015.A1-2026-01-05-17-08-27.zip\
+20 MBDownload
+
+Tue Jan 06 2026 15:07:51 GMT+0800 (中国标准时间).png\
+869 KBViewDownload
+
+#### Comments
+
+All comments
+
+
+
+#### haoho@google.com\google.com\> #2Jan 6, 2026 05:58PM
+
+Reassigned to danni_dong@realtek.corp-partner.google.com.
+
+Hi Danni,
+
+When a device has two components, the Validator expects to receive UUID events from both. The error message `Pairing process error: Reason: Only receive correct UUID from 1 address` indicates that we did not receive the UUID from the secondary component.
+
+For future troubleshooting, it would be better if you could provide the full logcat (using adb logcat \> log.txt). The current logs do not provide enough information for a detailed analysis.
+
+Thanks!
+
+
+
+#### Danni Dong\realtek.corp-partner.google.com\> #3Jan 6, 2026 06:02PM
+
+Reassigned to haoho@google.com.
+
+hi hao\
+XX:XX:XX:XX:00:19 is the secondary bud\
+\
+//maybe seeker already received 0x184E?\
+01-05 17:07:47.413 10186 2772 5000 I NearbyDiscovery: FastPairUtils: isBluetoothDeviceSupportingTargetUuid: Target profile found, profile=0000184e-0000-1000-8000-00805f9b34fb, mac=XX:XX:XX:XX:00:19 \[CONTEXT service_id=265 \]
+
+
+
+#### haoho@google.com\google.com\> #4Jan 6, 2026 06:09PM
+
+Reassigned to danni_dong@realtek.corp-partner.google.com.
+
+Hi Danni,
+
+The UUID event arrival was significantly delayed.\
+Our test timed out at the exact same second the event was received.\
+Could you investigate why there was such a long latency for the UUID event?
+
+ 01-05 17:07:47.413 10186 2772 5000 I NearbyDiscovery: FastPairUtils: isBluetoothDeviceSupportingTargetUuid: Target profile found, profile=0000184e-0000-1000-8000-00805f9b34fb, mac=XX:XX:XX:XX:00:19 [CONTEXT service_id=265 ]
+ 01-05 17:07:47.413 10186 2772 5000 I NearbyDiscovery: FastPairUtils: isBluetoothDeviceSupportingLeaUuid: Lea profile found, mac=XX:XX:XX:XX:00:19 [CONTEXT service_id=265 ]
+
+ // Test timeout
+ 01-05 17:07:47.612 10298 7314 9879 I BaseModuleTask: event=ModuleEvent{message=Pairing process error. Reason: Only receive correct UUID from 1 address
+ 01-05 17:07:47.612 10298 7314 9879 I BaseModuleTask: , status=FAILURE}, callback=dzj@52da1a, executor=bah@ad7e9e8
+ 01-05 17:07:47.616 10298 7314 9879 I BaseModuleTask: event=ModuleEvent{message=Test finished, status=FAILURE}, callback=dzj@52da1a, executor=bah@ad7e9e8
+ 01-05 17:07:47.616 10298 7314 9879 W BaseModuleTask: Failed to finish test for PersonalizedNameUpdateTask
+
+
+
+#### Danni Dong\realtek.corp-partner.google.com\> #5Jan 7, 2026 10:09AM
+
+Reassigned to haoho@google.com.
+
+hi hao:\
+\
+Does the seeker determine whether it has received UUID 0x184E by checking if it has received UUID 0x184e from the LE Audio Advertising data?\
+Wed Jan 07 2026 10:04:20 GMT+0800 (中国标准时间).png
+
+Wed Jan 07 2026 10:04:20 GMT+0800 (中国标准时间).png\
+226 KBViewDownload
+
+
+
+#### Danni Dong\realtek.corp-partner.google.com\> #6Jan 7, 2026 10:26AM
+
+We observed that the phone accessed the 0x184e service around 17:06:51.\
+Therefore, we would like to ask how the phone determines whether it has received the 0x184E service UUID.\
+thanks\
+Wed Jan 07 2026 10:23:39 GMT+0800 (中国标准时间).png
+
+Wed Jan 07 2026 10:23:39 GMT+0800 (中国标准时间).png\
+180 KBViewDownload
+
+
+
+#### haoho@google.com\google.com\> #7Jan 7, 2026 10:47AM
+
+Reassigned to danni_dong@realtek.corp-partner.google.com.
+
+Hi Danni,
+
+In the Android, there is a UUID broadcast mechanism where the Bluetooth stack sends an ACTION_UUID intent to the app layer. Upon receiving this broadcast, the Validator checks for 0x184e (for LE Audio cases) or verifies A2DP and HFP (for Classic Bluetooth cases).
+
+According to the Android Developers website, this intent is only triggered when the remote device's UUIDs are fetched via the Service Discovery Protocol.
+
+
+
+#### Danni Dong\realtek.corp-partner.google.com\> #8Jan 8, 2026 11:00AM
+
+hi hao:\
+provider has GATT caching enabled, and the seeker seems to be using a cached service table, so seeker doesn't start to do Service Discovery again?
+
+GFPS_spec_gattcaching.png\
+285 KBViewDownload
+
+
+
+#### Danni Dong\realtek.corp-partner.google.com\> #9Jan 8, 2026 11:17AM
+
+Reassigned to haoho@google.com.
+
+here is the new log with logcat （103820）fail
+
+bugreport-caiman_beta-BP41.250916.015.A1-2026-01-07-10-38-33.zip\
+19 MBDownload
+
+FILENAME7.log\
+27 MBViewDownload
+
+20260107 27045.zip\
+1.9 MBDownload
+
+
+
+#### haoho@google.com\google.com\> #10Jan 8, 2026 12:39PM
+
+Reassigned to danni_dong@realtek.corp-partner.google.com.
+
+Hi Danni,
+
+Looks like you succeeded the first time.
+
+ [FILENAME7.log]
+ 01-07 10:36:40.025 9477 9555 D BaseModuleTask: Succeed to finish test for PersonalizedNameUpdateTask
+
+In failed case, we only receive UUID from `XX:XX:XX:XX:88:00`, but not `XX:XX:XX:XX:00:19`.
+
+ 01-07 10:37:24.296 9477 9477 I BaseModuleTask: event=ModuleEvent{message=Received UUID from XX:XX:XX:XX:88:00, status=SUCCESS}, callback=dzj@cabcee2, executor=bah@a20c9cc
+ 01-07 10:37:24.297 9477 9477 D FeatureTestActivity: ModuleEvent{message=Received UUID from XX:XX:XX:XX:88:00, status=SUCCESS}
+ 01-07 10:38:20.067 9477 10309 I BaseModuleTask: event=ModuleEvent{message=Pairing process error. Reason: Only receive correct UUID from 1 address
+
+If the earbuds didn't receive the SDP, I suspect it might be due to a Bluetooth cache issue.\
+If that's the case, I think we can disregard this instance, especially since you’ve successfully passed the test before.\
+Do you have any other concerns regarding this?
+
+
+
+#### Danni Dong\realtek.corp-partner.google.com\> #11Jan 8, 2026 02:09PM
+
+Reassigned to haoho@google.com.
+
+hi hao:\
+\
+it's not 100% reproducible, but the probability of reproduction is very high 5/10.\
+Do you mean that if we fail 5 out of 10 times, is that acceptable? Or is it acceptable as long as we pass 1 out of 10 times?\
+Don't certification labs use Fast Pair Validator testing? What should we do if the certification lab encounters a similar problem?\
+\
+If it's a Bluetooth cache issue, how can we clear the cache?\
+\
+thanks
+
+
+
+#### haoho@google.com\google.com\> #12Jan 8, 2026 05:04PM
+
+Reassigned to danni_dong@realtek.corp-partner.google.com.
+
+Hi Danni,\
+\
+According to your test results, the UUID event is not related to the naming feature. Therefore, you can safely ignore it.\
+\
+Regarding the certification labs, they do not use the Validator app. Since they perform testing manually, you won't encounter the same issue there.\
+\
+I hope this clears up your doubts.
+
+### Add comment
diff --git a/附耳配对失败+cause+Numeric+Comparison+Failed_0x050C.md b/附耳配对失败+cause+Numeric+Comparison+Failed_0x050C.md
new file mode 100644
index 0000000..f7d7fee
--- /dev/null
+++ b/附耳配对失败+cause+Numeric+Comparison+Failed_0x050C.md
@@ -0,0 +1,44 @@
+# 附耳配对失败 cause Numeric Comparison Failed 0x050C
+
+
+
+\
+
+原因是gfps_handle_char_additional_passkey 解密 additional passkey 失败了
+
+
+
+
+ 0008066 12-30#14:08:38.005 199 0598425.808 [BTIFMSG]↗BTIF_MSG_GATT_ATTR_WRITE_REQ_IND(CMD:0x010A) link_id:0x0012 cid:0x0004 p_srv_handle:0x004204C8 attr_index:0x0011 attr_len:0x0010 handle:0x0000 write_offset:0x0000 gap:0x09 data:0x17
+ 0008067 12-30#14:08:38.005 200 0598426.097 [PATCH] patch_hw_aes_operate_imp: error code: 0x0
+ 0008068 12-30#14:08:38.005 201 0598426.132 [APP] !!!gfps_handle_char_additional_passkey: message type error 240
+ 0008069 12-30#14:08:38.005 202 0598426.162 [APP] !**gfps_attr_write_cb: pending, attr_index 17, cause 0xd04
+ 0008070 12-30#14:08:38.005 203 0598426.187 [BTIFMSG]↙BTIF_MSG_GATT_ATTR_WRITE_REQ_CFM(CMD:0x010B) link_id:0x0012 cid:0x0004 p_srv_handle:0x004204C8 cause:0x0D04 attr_index:0x0011 |
+
+
+
+
+gfps_handle_char_additional_passkey 解密：
+
+
+
+怀疑 gfps→aes_key 被改了
+
+
+
+
+//这边有一次异常断线，异常断线之后 我们有reset aes_key
+0004136 12-30#14:08:28.521 142 0588963.226 [APP] app_gfps_le_disconnect_cb: conn_id 0, local_disc_cause 0, disc_cause 0x108
+ 0004137 12-30#14:08:28.521 143 0588963.260 [APP] !!!app_gfps_le_disconnect_cb: plink connid 0, gfps link connid 0, gfps curr conn_id 0
+ 0004138 12-30#14:08:28.521 144 0588963.324 [APP] !**gfps_reset_aeskey_and_pairing_status: aes_key 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |
+
+
+
+
+因为Google spec 是说 shall discard aes key and pairing mode if this LE link disconnects，所以优先要请 lowerstack 帮忙查看disc_cause 0x108
+
+目前的workaround 是：不清楚会不会引入新的问题：
+
+
+
+[BBPRO3BUG-27030] [BBPRO3][EVB][E Cut][PEGA_HA_v1.0.4_20251106][24110 testbin][GFPS][FastPair][LEA phone]Auto Subsequent Pairing... 测试fail（fail reason：creatbond failed，multiple components） - Jira
diff --git a/附耳配对失败,+cause+Unspecified+Reason.md b/附耳配对失败,+cause+Unspecified+Reason.md
new file mode 100644
index 0000000..9bebf74
--- /dev/null
+++ b/附耳配对失败,+cause+Unspecified+Reason.md
@@ -0,0 +1,45 @@
+# 附耳配对失败, cause Unspecified Reason
+
+[BBPRO3BUG-27188] [BBPRO3][EVB][E Cut][PEGA_HA_v1.0.4_20251106][24110 testbin][GFPS][FastPair][LEA phone]Auto Subsequent Pairing... 测试fail（fail reason：creatbond failed，multiple components） - Jira
+
+
+
+\
+
+这一次附耳没有回 BTIF_MSG_USER_CFM_REQ_CFM
+
+
+
+\
+
+原因是附耳没有收到主耳 relay 给附耳的passkey：
+
+0002606 12-17#11:47:47.540 014 0616624.893 \[BTIFMSG\]↗BTIF_MSG_USER_CFM_REQ_IND(CMD:0x001B) bd_addr\[58:7E:79:C5:52:13\] remote_addr_type:0x01(BTIF_REMOTE_ADDR_LE_RANDOM) display_value:0x00097A21\
+0002615 12-17#11:47:47.540 023 0616625.744 \[APP\] !\*\*app_gfps_handle_additional_ble_user_confirm: additional passkey 621089
+
+\
+
+
+
+\
+
+主耳发 relay 消息的地方 module type = 0x83, msg type = 0x4
+
+0007190 12-17#11:47:47.714 098 0617463.983 \[APP\] !\*\*app_gfps_cb_handle_additional_passkey\
+ 0007191 12-17#11:47:47.714 099 0617464.026 \[APP\] app_relay_async_single_with_raw_msg: module type = 0x83, msg type = 0x4,payload_len = 16\
+ 0007192 12-17#11:47:47.714 100 0617464.150 \[REMOTE\] remote_async_msg_relay: handle 0x00427458, seq 0x5f, msg_id 0x00f3, loopback 0
+
+\
+
+附耳好像没有收到, 附耳如果收到的话 log中通过app_relay_cback: 应该能看到对应的信息
+
+ Line 124093: 0003945 12-17#16:53:24.501 151 0254140.963 \[APP\] app_relay_cback: event 0x00f3, status 9\
+ Line 124094: 0003946 12-17#16:53:24.501 152 0254140.983 \[APP\] app_relay_cback: msg_len 5, module_type 0x1d, msg_type 0x6, len 5, offset 0,\
+ Line 134125: 0003962 12-17#16:54:07.529 106 0297191.734 \[APP\] app_relay_cback: event 0x00f3, status 0\
+ Line 134126: 0003963 12-17#16:54:07.529 107 0297191.768 \[APP\] app_relay_cback: msg_len 5, module_type 0x83, msg_type 0x5, len 5, offset 0,\
+ Line 134497: 0004334 12-17#16:54:08.813 222 0298465.649 \[APP\] app_relay_cback: event 0x00f3, status 0\
+ Line 134498: 0004335 12-17#16:54:08.813 223 0298465.669 \[APP\] app_relay_cback: msg_len 4, module_type 0x83, msg_type 0x3, len 4, offset 0,\
+ Line 134645: 0004482 12-17#16:54:09.162 111 0298846.997 \[APP\] app_relay_cback: event 0x00f3, status 0\
+ Line 134646: 0004483 12-17#16:54:09.162 112 0298847.020 \[APP\] app_relay_cback: msg_len 28, module_type 0xc, msg_type 0x2, len 28, offset 0,\
+ Line 134699: 0004536 12-17#16:54:09.197 165 0298851.355 \[APP\] app_relay_cback: event 0x00f3, status 0\
+ Line 134700: 0004537 12-17#16:54:09.197 166 0298851.375 \[APP\] app_relay_cback: msg_len 11, module_type 0xd, msg_type 0xc, len 11, offset 0,
\
+
+
+测试jira:
+
+ BTQCSZ-6106 - Getting issue details... STATUS
diff --git a/2.3+测试.md b/2.3+测试.md
new file mode 100644
index 0000000..c1228c6
--- /dev/null
+++ b/2.3+测试.md
@@ -0,0 +1,7 @@
+# 2.3 测试
+
+测试完成之后要填写测试报告, 测试报告 从以下位置获取：
+
+Test Case of the Third Party - BT Test - WIKI
+
+
diff --git a/2.3.1+Fast+Pair+Validator测试.md b/2.3.1+Fast+Pair+Validator测试.md
new file mode 100644
index 0000000..d5ba26e
--- /dev/null
+++ b/2.3.1+Fast+Pair+Validator测试.md
@@ -0,0 +1,17 @@
+# 2.3.1 Fast Pair Validator测试
+
+2.3.1.2 EDDYSTONE
+
+** 这个必须要保证可以PASS，因为认证实验室会使用Fast Pair Validator 测试Finder相关的测项**
+
+\
+
+2.3.1.1 FAST PAIR
+
+这个测项客户自测并且提交测试结果到Google云端，认证实验室暂时不会测试。
+
+目前来看只要有一次测试成功，并且有提交成功的测试结果到Google云端就可以，即使偶尔失败了，如果确定不是我们设备端的bug, 也没关系的
+
+https://partnerissuetracker.corp.google.com/u/0/issues/473688165
+
+
diff --git a/2.3.1.1+FAST+PAIR.md b/2.3.1.1+FAST+PAIR.md
new file mode 100644
index 0000000..b3866f6
--- /dev/null
+++ b/2.3.1.1+FAST+PAIR.md
@@ -0,0 +1,687 @@
+# 2.3.1.1 FAST PAIR
+
+
+
+
+
+\
+
+主附耳总的配对时间超过Google规定的值15s，建议：
+
+1.查看附耳在处理 Fast Pair 强制进入配对模式的逻辑处（app_gfps_sec_handle_additional_io_cap 接收到同步消息改变 io_cap 之后），le audio 广播有没有Enable，以及广播的interval是多少Google强烈建议为了使手机能够尽快的通过LE audio广播发现附耳， 此时附耳的le audio 广播interval要尽可能的小，Google推荐是0x20(20ms), 但是我看 le audio设置的
+
+APP_LEA_ADV_INTERVAL_FAST 0x30，
+
+如果此时le audio的interval是 APP_LEA_ADV_INTERVAL_SLOW 0x140 那肯定是会影响发现的速度的
+
+\
+
+2.附耳BLE连线建立之后，ATT层LE audio 相关service的发现比较耗时，一个建议是打开GATT caching，还有一个建议是缩小connection interval(但是le audio同事说如果设备端主动更新connection interval， 有的手机会断线，所以这个方式不可行)
+
+\
+
+3. 去屏蔽室测试，排除环境干扰，屏蔽室测试OK之后，把pass的结果submit就可以，Google 认证实验室不会验证，只需要我们验证pass之后提交pass的测试结果到Google后台即可。
+
+
diff --git a/Pairing+failed!+[Pair+time-out,+total+pair+time+21126+_+threshold+15000ms....].md b/Pairing+failed!+[Pair+time-out,+total+pair+time+21126+_+threshold+15000ms....].md
new file mode 100644
index 0000000..0620cf8
--- /dev/null
+++ b/Pairing+failed!+[Pair+time-out,+total+pair+time+21126+_+threshold+15000ms....].md
@@ -0,0 +1,31 @@
+# Pairing failed! \[Pair time-out, total pair time 21126 \> threshold 15000ms....\]
+
+
+
+\
+
+hi Wade Li(李伟东) ：
+
+附耳的LEA广播好像有问题，想请你协助客户分析一下app层的code
+
+一个是adv data 的设置必须要在 adv 参数初始化之后设置
+
+
+
+还有一个是感觉lea adv似乎没有初始化
+
+
+
+
+
+\
+
+林詩皓 added a comment - 2026/03/02 12:08
+
+https://cn4soc.rtkbf.com/gerrit/c/HoneyRepo/lowerpatch/+/303949/1
+
+可以用這筆試試看
+
+\
+
+[BBPRO3BUG-28142] [Laplace][Earbud]PTS-135] GFPS：Fail in "End-to-End Integration" - Jira
diff --git a/Pairing+failed!+[Pair+time-out].md b/Pairing+failed!+[Pair+time-out].md
new file mode 100644
index 0000000..877858d
--- /dev/null
+++ b/Pairing+failed!+[Pair+time-out].md
@@ -0,0 +1,15 @@
+# Pairing failed! \[Pair time-out\]
+
+
+
+\
+
+原因是setting 界面 开发者选项里面没有enable以下配置
+
+
+
+\
+
+详细信息请参考：
+
+1 测试准备工作 - BT_Market - WIKI
diff --git a/Pairing+failed!+[Pair+timeout+only+receive+correct+UUID+from+1+address......].md b/Pairing+failed!+[Pair+timeout+only+receive+correct+UUID+from+1+address......].md
new file mode 100644
index 0000000..1e66cef
--- /dev/null
+++ b/Pairing+failed!+[Pair+timeout+only+receive+correct+UUID+from+1+address......].md
@@ -0,0 +1,3 @@
+# Pairing failed! \[Pair timeout only receive correct UUID from 1 address......\]
+
+
diff --git a/Pairing+failed!......KeyBasedPairingExtensionResponse+wrong+address+length_+1.md b/Pairing+failed!......KeyBasedPairingExtensionResponse+wrong+address+length_+1.md
new file mode 100644
index 0000000..e57c058
--- /dev/null
+++ b/Pairing+failed!......KeyBasedPairingExtensionResponse+wrong+address+length_+1.md
@@ -0,0 +1,29 @@
+# Pairing failed!......KeyBasedPairingExtensionResponse wrong address length: 1
+
+
+
+End-to-End Integration-pairing failed.7z
+
+设备：TWS 耳机支援LE audio
+
+手机：支援LE audio
+
+测试的时候有Enable LE Spec Test
+
+\
+
+ **// 设备是支援LE audio的TWS耳机，le_device_mode 0 是不对的，这个值是MCU cfg tool配置的，麻烦自查认证测试文档**
+
+0001530 02-10#15:13:12.989 143 0027119.990 \[APP\] !\*\*gfps_send_kbp_response_le: le_device_support 1, le_device_mode 0\
+ 0001531 02-10#15:13:12.989 144 0027140.696 \[PATCH\] patch_hw_aes_operate_imp: error code: 0x0\
+ 0001532 02-10#15:13:12.989 145 0027140.775 \[APP\] !\*\*gfps_send_kbp_response_le: raw response 02 00 01 19 97 88 00 00 00 91 21 1F 31 DD C7 5C, encrypt response AC D6 3E CA C6 A1 84 71 9C 6C A7 71 7E C4 DE BF
+
+\
+
+**如果设备是支援LE audio的， Enable GFPS LE Pair 要勾选，GFPS device mode 设成 Dual mode device with CSIP/Dual mode device with LE Audio**
+
+
+
+[BBPRO3BUG-28142] [Laplace][Earbud]PTS-135] GFPS：Fail in "End-to-End Integration" - Jira
+
+\
diff --git a/Pairing+failed![Pair+time-out,+Total+pairing+time+18020ms_threshold+12000ms].md b/Pairing+failed![Pair+time-out,+Total+pairing+time+18020ms_threshold+12000ms].md
new file mode 100644
index 0000000..9282791
--- /dev/null
+++ b/Pairing+failed![Pair+time-out,+Total+pairing+time+18020ms_threshold+12000ms].md
@@ -0,0 +1,19 @@
+# Pairing failed\![Pair time-out, Total pairing time 18020ms\>threshold 12000ms\]
+
+
+
+\
+
+设备端是支援LE audio的立体声耳机，原因是耳机是支援 GFPS LE的
+
+
+
+\
+
+但是 fast pair validator 没有Enable LE spec test
+
+Enable LE spec test之后要根据耳机实际的配置选择是否支援LE audio, 以及是否支援CSIP(TWS耳机支援CSIP，single mode 不支援CSIP)
+
+
+
+\
diff --git a/Pairing+failed！[Pair+time-out].md b/Pairing+failed！[Pair+time-out].md
new file mode 100644
index 0000000..4e5aa4d
--- /dev/null
+++ b/Pairing+failed！[Pair+time-out].md
@@ -0,0 +1,69 @@
+# Pairing failed！\[Pair time-out\]
+
+140522 Pairing Failed Pair timeout.zip
+
+
+
+\
+
+原因是BR ACL link 建立之后，4s没连legacy profile， 设备端主动把BR ACL link 断掉了，导致GFPS 流程异常
+
+Line 81655: 0008329 03-03#14:05:14.028 249 0047231.527 \[APP\] !\*\*connected: b2s, bd_addr AC::3E::B1::09::07::C6, profs 0x00000000
+
+\
+
+**问：**
+
+设备端断开L2cap的原因是设备端没有收到手机端主动连A2dp/hfp ，这好像是符合蓝牙spec的， 设备是支援le audio的TWS耳机，手机也支援le audio, 是不是手机本身就不会连A2dp/hfp, 而是会通过le audio交互音频数据
+
+\
+
+**答：**
+
+\*\*在支持 LE Audio 的双模（Dual-Mode）TWS 耳机测试中，Android 手机（特别是支持 LE Audio 的较新系统）的配对和连接行为确实与纯经典蓝牙耳机有很大不同。\*\* 手机在连接时会优先进行 LE Audio 的服务发现和配置，从而“冷落”或延迟建立经典蓝牙的 A2DP/HFP 业务。
+
+这不仅没有推翻之前的分析，反而\*\*完美地解释了为什么会发生 L2CAP 超时。\*\* 之前的分析依然绝对可靠，我们可以结合 LE Audio 的特性来彻底还原这个 Google 测项失败的完整逻辑。
+
+\### 1. 为什么说分析依然可靠？（结合日志的铁证）
+
+在左耳（COM4）主动断开经典蓝牙连接（14:05:18.140）的\*\*同一毫秒\*\*，我们看看耳机在 BLE 链路上正在忙什么：
+
+\`\`\`text\
+ 0004586 03-03#14:05:18.140 005 \[PROTOCOL\] !\*\*ascs_attr_read_cb: attrib_index 8, offset 0\
+ 0004587 03-03#14:05:18.140 006 \[PROTOCOL\] !\*\*ase_gen_char_data: ase_id 2, direction: 1, ase_state 0, len 2\
+ 0004588 03-03#14:05:18.140 007 \[BTIFMSG\]↙BTIF_MSG_GATT_ATTR_READ_CFM...\
+ ...\
+ 0004594 03-03#14:05:18.140 013 \[PATCH\] l2c_handle_timeout: timer_id 0x84, timer_chann 0x0042\
+ 0004595 03-03#14:05:18.140 014 \[HCI\] !\*\*hci_cmd_disconnect: handle 0x0002, cause 0x13\
+ 0004599 03-03#14:05:18.140 018 \[MODULE_LOWERSTACK\] ... --\> send lmp opc:7 ... Name is LMP_detach\
+\`\`\`
+
+\*\*解析：\*\*
+
+\* \`ascs_attr_read_cb\`：\*\*ASCS (Audio Stream Control Service)\*\* 是 LE Audio 的核心服务。这证明手机此刻并没有闲着，它正在疯狂地通过 BLE 读取耳机的 LE Audio 属性（GATT Discovery）。\
+\* 手机在 \`14:05:14\` 的时候，其实已经顺手把经典蓝牙的底层 ACL 链路（handle \`0x0002\`）建好了（为了双模兼容性）。\
+\* 但是，因为手机正忙着在 BLE 上配置 LE Audio，它\*\*延迟了\*\*在经典蓝牙链路上发起 SDP / A2DP / HFP。\
+\* 耳机端（底层协议栈）有个死板的定时器（\`timer_id 0x84\`）：如果经典蓝牙 ACL 建连后大约 \*\*4 秒内\*\*没有收到 Profile 级的 L2CAP 交互（\`timer_chann 0x0042\`），耳机就认为经典链路是“死链接”，从而\*\*主动将其断开\*\*。
+
+**\*\*结论：\*\* 手机觉得“我正在忙着配 LE Audio，经典蓝牙你先等着”，但耳机觉得“经典蓝牙连上了4秒你还不理我，我把你挂了”。\*\*耳机主动挂断经典蓝牙，导致 Android 系统的蓝牙状态机认为整个双模配对流程出现异常，从而在 3.8 秒后（14:05:22）把 BLE 链路也彻底断了，报出 Pairing Failed。\*\***
+
+\
+
+**您的耳机固件目前的逻辑对于纯经典蓝牙是合理的（防呆机制，防止占着信道不发数据），但\*\*对于 LE Audio 双模流程来说是致命的 bug\*\*。**
+
+**\*\*修复建议：\*\***
+
+1\. \*\*修改 L2CAP Idle Timeout 机制\*\*：\
+ 在检测到当前正处于 Google Fast Pair 流程中，或者当前 BLE 链路正在进行 LE Audio (ASCS/PACS) GATT 发现时，\*\*必须显著延长或直接禁用经典蓝牙侧的 L2CAP 空闲断开定时器（将 4 秒至少延长至 15-30 秒，或者等待 BLE 侧彻底配置完毕）\*\*。\
+2. \*\*状态机关联\*\*：\
+ 让经典蓝牙的连接状态机能够“感知”到 BLE 侧的繁忙状态。只要 BLE 侧的 GFPS/LE Audio 协商还在进行，就允许经典蓝牙保留一条没有 Profile 数据的“空” ACL 链路，不要主动发送 \`LMP_detach\`。
+
+\
+
+\
+
+\
+
+\
+
+\
diff --git a/Pairing+process+error_+Reason_+Is+connected+false.md b/Pairing+process+error_+Reason_+Is+connected+false.md
new file mode 100644
index 0000000..d5a0e2e
--- /dev/null
+++ b/Pairing+process+error_+Reason_+Is+connected+false.md
@@ -0,0 +1,149 @@
+# Pairing process error: Reason: Is connected false
+
+
+
+https://partnerissuetracker.corp.google.com/u/0/issues/411582869
+
+\
+
+Hi BT team,
+
+When our partner tested Fast Pair via the Validator, it didn't connect to the phone correctly. Provider not support LEA and phone support LEA.\
+It looks like after device bonded and getting the UUIDs, the phone policy didn't trigger the classic profile connection, so the phone disconnected from the provider after a timeout.\
+Could you please check why it didn't trigger the classic profile connection?\
+Thanks a lot!
+
+ [bugreport-caiman-AD1A.240905.004-2025-04-18-14-32-41.zip]
+ // Device bonded
+ 04-18 14:30:36.473 1002 2508 2994 I BluetoothBondStateMachine: XX:XX:XX:XX:22:88 is bonded, wait for SDP complete to broadcast bonded intent
+
+ // SDP
+
+ 04-18 14:30:36.606 1002 2508 2910 I bt_bta_dm: bta_dm_sdp_result: GATT services discovered using SDP
+ 04-18 14:30:36.606 1002 2508 2910 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:1798 - btif_dm_search_services_evt: SDP finished for xx:xx:xx:xx:22:88:
+ 04-18 14:30:36.606 1002 2508 2910 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:1807 - btif_dm_search_services_evt: New UUIDs for xx:xx:xx:xx:22:88:
+ 04-18 14:30:36.606 1002 2508 2910 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:1813 - btif_dm_search_services_evt: index:0 uuid:00001101-0000-1000-8000-00805f9b34fb
+ 04-18 14:30:36.606 1002 2508 2910 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:1813 - btif_dm_search_services_evt: index:1 uuid:00001108-0000-1000-8000-00805f9b34fb
+ 04-18 14:30:36.607 1002 2508 2910 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:1813 - btif_dm_search_services_evt: index:2 uuid:0000111e-0000-1000-8000-00805f9b34fb
+ 04-18 14:30:36.607 1002 2508 2910 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:1813 - btif_dm_search_services_evt: index:3 uuid:0000110b-0000-1000-8000-00805f9b34fb
+ 04-18 14:30:36.607 1002 2508 2910 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:1813 - btif_dm_search_services_evt: index:4 uuid:0000110e-0000-1000-8000-00805f9b34fb
+ 04-18 14:30:36.607 1002 2508 2910 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:1813 - btif_dm_search_services_evt: index:7 uuid:6a24eeab-4b65-4693-986b-3c26c352264f
+ 04-18 14:30:36.607 1002 2508 2910 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:1813 - btif_dm_search_services_evt: index:8 uuid:df21fe2c-2515-4fdb-8886-f12c4d67927c
+ 04-18 14:30:36.607 1002 2508 2910 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:498 - get_cod: remote_cod=0x00244404
+ 04-18 14:30:36.607 1002 2508 2910 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:1863 - btif_dm_search_services_evt: SDP search done for xx:xx:xx:xx:22:88
+
+ // Not sure if waiting for LE service discovery here
+ 04-18 14:30:36.607 1002 2508 2910 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:1917 - btif_dm_search_services_evt: Bonding LE Audio sink - must wait for le services discovery to pass all services to java xx:xx:xx:xx:22:88
+ 04-18 14:30:36.607 1002 2508 2910 I bt_bta_dm: bta_dm_search_cmpl: No BLE connection, processing classic results
+
+ // Phone disconnected from provider.
+ 04-18 14:30:40.615 1002 2508 2910 I btm_acl : disconnect_acl: Disconnecting peer:xx:xx:xx:xx:22:88 reason:HCI_ERR_PEER_USER comment:stack::l2cap::l2c_link::l2c_link_timeout All channels closed
+ 32183 06:30:40.616070 host controller HCI_CMD 7 Sent Disconnect
+
+\
+
+\
+
+ // ACL LE connected
+
+ 04-18 14:30:32.132 1002 1048 2043 I bthal.activity: handle_ble_meta_event: LE Enhanced Connection Complete, conn_handle:041, conn_bda: XX:XX:44:44:22:88
+ 04-18 14:30:32.223 1002 2508 2910 I bt_bta_dm: bta_dm_acl_up: Acl connected peer:xx:xx:xx:xx:22:88 transport:BT_TRANSPORT_LE handle:65
+ 04-18 14:30:34.934 1002 2508 2910 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:586 - bond_state_changed: Bond state changed to state=1[0:none, 1:bonding, 2:bonded],prev_state=0, sdp_attempts=0
+ 04-18 14:30:34.934 1002 2508 2954 I BluetoothBondStateMachine: bondStateChangeCallback: Status: 0 Address: XX:XX:XX:XX:22:88 newState: 1 hciReason: 0
+ 04-18 14:30:34.944 1002 2508 2994 I BluetoothBondStateMachine: Bond State Change Intent:XX:XX:XX:XX:22:88 BOND_NONE => BOND_BONDING
+
+ // ACL BR/EDR connected
+ 04-18 14:30:36.075 1002 2508 2910 I bt_bta_dm: bta_dm_acl_up: Acl connected peer:xx:xx:xx:xx:22:88 transport:BT_TRANSPORT_BR_EDR handle:11
+ 04-18 14:30:36.467 1002 2508 2910 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:586 - bond_state_changed: Bond state changed to state=2[0:none, 1:bonding, 2:bonded],prev_state=1, sdp_attempts=1
+ 04-18 14:30:36.467 1002 2508 2954 I BluetoothBondStateMachine: bondStateChangeCallback: Status: 0 Address: XX:XX:XX:XX:22:88 newState: 2 hciReason: 0
+ 04-18 14:30:36.473 1002 2508 2994 I BluetoothBondStateMachine: XX:XX:XX:XX:22:88 is bonded, wait for SDP complete to broadcast bonded intent
+ 04-18 14:30:36.473 1002 2508 2994 I BluetoothBondStateMachine: StableState(): Entering Off State
+ 04-18 14:30:36.607 1002 2508 2910 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:1917 - btif_dm_search_services_evt: Bonding LE Audio sink - must wait for le services discovery to pass all services to java xx:xx:xx:xx:22:88
+ 04-18 14:30:39.492 1002 2508 2994 I BluetoothBondStateMachine: Bond State Change Intent:XX:XX:XX:XX:22:88 BOND_BONDING => BOND_BONDED
+
+ / BT_ACL_STATE_DISCONNECTED
+
+ 04-18 14:30:40.768 1002 2508 2910 I bt_shim_hci: packages/modules/Bluetooth/system/main/shim/hci_layer.cc:304 - operator(): ISO disconnection from GD, handle: 0x0b, reason: 0x13
+ 04-18 14:30:40.769 1002 2508 2910 D bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:2552 - btif_dm_acl_evt: Sent BT_ACL_STATE_DISCONNECTED upward as ACL link down event device:xx:xx:xx:xx:22:88 reason:HCI_ERR_PEER_USER
+ 04-18 14:30:51.134 1002 2508 2910 I bt_shim_hci: packages/modules/Bluetooth/system/main/shim/hci_layer.cc:304 - operator(): ISO disconnection from GD, handle: 0x41, reason: 0x16
+ 04-18 14:30:51.137 1002 2508 2910 D bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:2552 - btif_dm_acl_evt: Sent BT_ACL_STATE_DISCONNECTED upward as ACL link down event device:xx:xx:xx:xx:22:88 reason:HCI_ERR_CONN_CAUSE_LOCAL_HOST
+
+ // Bonding Removed
+
+ 04-18 14:31:50.137 1002 2508 2910 I bt_btif_storage: packages/modules/Bluetooth/system/btif/src/btif_storage.cc:889 - btif_storage_remove_bonded_device: Removing bonded device addr=xx:xx:xx:xx:22:88
+ 04-18 14:31:50.137 1002 2508 2910 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:586 - bond_state_changed: Bond state changed to state=0[0:none, 1:bonding, 2:bonded],prev_state=2, sdp_attempts=0
+ 04-18 14:31:50.137 1002 2508 2910 I bt_btif_storage: packages/modules/Bluetooth/system/btif/src/btif_storage.cc:889 - btif_storage_remove_bonded_device: Removing bonded device addr=xx:xx:xx:xx:22:88
+ 04-18 14:31:50.137 1002 2508 2910 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:586 - bond_state_changed: Bond state changed to state=0[0:none, 1:bonding, 2:bonded],prev_state=0, sdp_attempts=0
+ 04-18 14:31:50.137 1002 2508 2910 E BluetoothMetricIdManager: packages/modules/Bluetooth/system/gd/common/metric_id_manager.cc:190 - ForgetDevice: Failed to remove device from paired_device_cache_
+ 04-18 14:31:50.140 1002 2508 2994 D AdapterProperties: Removing bonded device:XX:XX:XX:XX:22:88
+ 04-18 14:31:50.146 1002 2508 2994 I BluetoothBondStateMachine: Bond State Change Intent:XX:XX:XX:XX:22:88 BOND_BONDED => BOND_NONE
+ 04-18 14:31:50.147 1002 2508 2994 I BluetoothBondStateMachine: StableState(): Entering Off State
+
+`Fastpair made some configurations`
+
+ 04-18 14:30:30.959 10298 19745 26174 I BaseModuleTask: event=ModuleEvent{message=LE spec config: Enable LE spec: false, is module test LE spec supported false, expect LE audio connection: false, is provider CSIP supported: false, is provider LE audio supported: false, is provider data only: false, device type number: TRUE_WIRELESS_HEADPHONES, status=SUCCESS}, callback=dxh@74d2dcb, executor=ayp@5d289a8
+ 04-18 14:30:30.965 10298 19745 26174 I BaseModuleTask: event=ModuleEvent{message=Pairing time threshold is: 12000 ms., status=INFORMATION}, callback=dxh@74d2dcb, executor=ayp@5d289a8
+ 04-18 14:30:32.033 10298 19745 26174 I BaseModuleTask: event=ModuleEvent{message=Start to scan model id: DCC22B , status=SUCCESS}, callback=dxh@74d2dcb, executor=ayp@5d289a8
+ 04-18 14:30:32.085 10298 19745 26174 I BaseModuleTask: event=ModuleEvent{message=Succeed to scan model id: DCC22B , status=SUCCESS}, callback=dxh@74d2dcb, executor=ayp@5d289a8
+ 04-18 14:30:32.085 10298 19745 26174 I BaseModuleTask: event=ModuleEvent{message=Start to initial pair model id: DCC22B , status=SUCCESS}, callback=dxh@74d2dcb, executor=ayp@5d289a8
+ 04-18 14:30:32.100 10186 27707 26135 I FastPair: FPDC: Starting to pair XX:XX:XX:XX:22:88: key[64], Preferences{gattOperationTimeoutSeconds=10, gattConnectionTimeoutSeconds=15, bluetoothToggleTimeoutSeconds=10, bluetoothToggleSleepSeconds=2, classicDiscoveryTimeoutSeconds=13, numDiscoverAttempts=3, discoveryRetrySleepSeconds=1, ignoreDiscoveryError=false, sdpTimeoutSeconds=10, numSdpAttempts=0, numCreateBondAttempts=3, numConnectAttempts=2, numWriteAccountKeyAttempts=3, bluetoothStatePollingMillis=1000, numAttempts=2, enableBrEdrHandover=false, brHandoverDataCharacteristicId=11265, bluetoothSigDataCharacteristicId=11266, firmwareVersionCharacteristicId=10790, brTransportBlockDataDescriptorId=11267, removeBondTimeoutSeconds=5, removeBondSleepMillis=1000, createBondTimeoutSeconds=15, hidCreateBondTimeoutSeconds=40, proxyTimeoutSeconds=2, rejectPhonebookAccess=false, writeAccountKeySleepMillis=2000, queryDeviceForEddystoneSupport=true, readEddystoneProvisioningStateWhilePairing=false, eddystoneProvisioningStateSleepMillis=2000, eddystoneProvisioningStateReadAttemptsNum=3, checkRogueCharacteristicDuringProvisioning=false, skipBondCreation=false, retryGattConnectionAndSecretHandshake=false, gattConnectShortTimeoutMs=7000, gattConnectLongTimeoutMs=15000, gattConnectShortTimeoutRetryMaxSpentTimeMs=10000, addressRotateRetryMaxSpentTimeMs=20000, pairingRetryDelayMs=1000, secretHandshakeShortTimeoutMs=5000, secretHandshakeLongTimeoutMs=10000, secretHandshakeShortTimeoutRetryMaxSpentTimeMs=5000, secretHandshakeLongTimeoutRetryMaxSpentTimeMs=7000, secretHandshakeRetryAttempts=0, secretHandshakeRetryDelayMs=0, secretHandshakeRetryGattConnectionMaxSpentTimeMs=20000, signalLostRetryMaxSpentTimeMs=15000, pairFailureCounts=0, cachedDeviceAddress=, cachedDeviceIdentityAddress=, sameModelIdPairedDeviceCount=0, writeLeAudioMetadata=false, isDeviceFinishCheckAddressFromCache=true, enableBredrBondingForKeyBasedPairingResponse=true, maybeRemoveBondIfDeviceSupportsLe=true, maybeRemoveBondBeforeHandshake=true, connectWithoutSpecifyingProfileWithLeaDevice=true, enableObserveKeyMissingIntent=false, enableHandleKeyMissingIntentForClassicConnection=true, supportedProfileUuids=[17, 11, 17, 8, 17, 30, 24, 78], skipConnectingProfiles=false, evaluatePerformance=true, enableNamingCharacteristic=true, enableFirmwareVersionCharacteristic=true, isRetroactivePairing=false, isLeDevicePairing=false, numSdpAttemptsAfterBonded=1, gattConnectRetryTimeoutMillis=18000, gattConnectMaxAttempts=0, handlePasskeyConfirmationByUi=false, enterPasskeyByUi=false, isSeekerWearOs=false, isTempBondForAudioSharing=false, bleDeviceSpecEnabledByGatt=false, bleDeviceSpecSupported=false, leAudioSupported=false, logCheckLeaSupport=false, logLeAudioMetadataError=true, skipGattRefresh=true, verificationCodeForKeyBasedPairingRequest=[], mitmGattNotificationTimeoutSeconds=3, mitmGattReadRetryCount=15, mitmGattReadIdleMilliseconds=200, forcePublicAddressTypeForAdditionalComponents=false, checkAddressRotationBeforePairing=false, logRobustCacheHash=false, validatorMockKeyBasedPairingRequestFlags=null, dtNumber=-1}
+ 04-18 14:30:32.104 10298 19745 19745 I BaseModuleTask: event=ModuleEvent{message=Pair Step: Connect GATT, status=SUCCESS}, callback=dxh@74d2dcb, executor=ayp@5d289a8
+ 04-18 14:30:33.870 10298 19745 19745 I BaseModuleTask: event=ModuleEvent{message=Pair Step: Handshake, status=SUCCESS}, callback=dxh@74d2dcb, executor=ayp@5d289a8
+ 04-18 14:30:34.914 10298 19745 19745 I BaseModuleTask: event=ModuleEvent{message=Received key based response., status=SUCCESS}, callback=dxh@74d2dcb, executor=ayp@5d289a8
+ 04-18 14:30:34.922 10298 19745 19745 I BaseModuleTask: event=ModuleEvent{message=Pair Step: Create bond, status=SUCCESS}, callback=dxh@74d2dcb, executor=ayp@5d289a8
+
+`Bonding was started, ACL got connected and device paired successfully`
+
+ 04-18 14:30:34.925 10186 27707 26135 I FastPair: BluetoothAudioPairer: createBond, device=XX:XX:XX:XX:22:88, transport=BREDR
+ 04-18 14:30:34.935 1002 2508 2922 I bluetooth: packages/modules/Bluetooth/system/gd/hci/acl_manager/acl_scheduler.cc:168 - try_dequeue_next_operation: Pending connections is not empty; so sending next connection
+ 04-18 14:30:34.944 1002 2508 2994 I BluetoothBondStateMachine: Bond State Change Intent:XX:XX:XX:XX:22:88 BOND_NONE => BOND_BONDING
+ 04-18 14:30:36.024 1002 2508 2910 D bluetooth: packages/modules/Bluetooth/system/main/shim/acl.cc:1464 - CreateClassicConnection: Connection initiated for classic to remote:xx:xx:xx:xx:22:88
+ 04-18 14:30:36.024 1002 2508 2922 I bluetooth: packages/modules/Bluetooth/system/gd/hci/acl_manager/acl_scheduler.cc:168 - try_dequeue_next_operation: Pending connections is not empty; so sending next connection
+ 04-18 14:30:36.072 1002 1048 2043 I bthal.activity: CreateConnectCompleteEvent, conn_handle:00B, conn_bda: XX:XX:44:44:22:88
+ 04-18 14:30:36.606 1002 2508 2910 D bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:1985 - btif_dm_search_services_evt: New GATT over SDP UUIDs for xx:xx:xx:xx:22:88:
+ 04-18 14:30:36.606 1002 2508 2910 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:2002 - btif_dm_search_services_evt: No well known GATT services discovered
+ 04-18 14:30:36.606 1002 2508 2910 V bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:1777 - btif_dm_search_services_evt: result=0x0, services 0xc00c0062
+ 04-18 14:30:36.606 1002 2508 2910 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:1798 - btif_dm_search_services_evt: SDP finished for xx:xx:xx:xx:22:88:
+ 04-18 14:30:36.606 1002 2508 2910 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:1807 - btif_dm_search_services_evt: New UUIDs for xx:xx:xx:xx:22:88:
+ 04-18 14:30:36.606 1002 2508 2910 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:1813 - btif_dm_search_services_evt: index:0 uuid:00001101-0000-1000-8000-00805f9b34fb
+ 04-18 14:30:36.606 1002 2508 2910 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:1813 - btif_dm_search_services_evt: index:1 uuid:00001108-0000-1000-8000-00805f9b34fb
+ 04-18 14:30:36.607 1002 2508 2910 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:1813 - btif_dm_search_services_evt: index:2 uuid:0000111e-0000-1000-8000-00805f9b34fb
+ 04-18 14:30:36.607 1002 2508 2910 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:1813 - btif_dm_search_services_evt: index:3 uuid:0000110b-0000-1000-8000-00805f9b34fb
+ 04-18 14:30:36.607 1002 2508 2910 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:1813 - btif_dm_search_services_evt: index:4 uuid:0000110e-0000-1000-8000-00805f9b34fb
+ 04-18 14:30:36.607 1002 2508 2910 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:1813 - btif_dm_search_services_evt: index:7 uuid:6a24eeab-4b65-4693-986b-3c26c352264f
+ 04-18 14:30:36.607 1002 2508 2910 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:1813 - btif_dm_search_services_evt: index:8 uuid:df21fe2c-2515-4fdb-8886-f12c4d67927c
+ 04-18 14:30:36.607 1002 2508 2910 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:1863 - btif_dm_search_services_evt: SDP search done for xx:xx:xx:xx:22:88
+ 04-18 14:30:36.607 1002 2508 2910 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/btif_dm.cc:1917 - btif_dm_search_services_evt: Bonding LE Audio sink - must wait for le services discovery to pass all services to java xx:xx:xx:xx:22:88
+ 04-18 14:30:39.492 1002 2508 2994 I BluetoothBondStateMachine: Bond State Change Intent:XX:XX:XX:XX:22:88 BOND_BONDING => BOND_BONDED
+ 04-18 14:30:39.999 10298 19745 19745 I BaseModuleTask: event=ModuleEvent{message=Received deceive XX:XX:XX:XX:22:88 bonded., status=SUCCESS}, callback=dxh@74d2dcb, executor=ayp@5d289a8
+
+`Due to no activity on link, we could see ACL getting terminated by l2c_link_timeout`
+
+ 04-18 14:30:40.615 1002 2508 2910 I btm_acl : disconnect_acl: Disconnecting peer:xx:xx:xx:xx:22:88 reason:HCI_ERR_PEER_USER comment:stack::l2cap::l2c_link::l2c_link_timeout All channels closed
+ 04-18 14:30:40.615 1002 2508 2922 D bluetooth: packages/modules/Bluetooth/system/main/shim/acl.cc:1047 - disconnect_classic: Disconnection initiated classic remote:xx:xx:xx:xx:22:88 handle:11
+ 04-18 14:30:40.768 1002 2508 2910 I bt_shim_hci: packages/modules/Bluetooth/system/main/shim/hci_layer.cc:304 - operator(): ISO disconnection from GD, handle: 0x0b, reason: 0x13
+
+`Wait 60000 ms for the connection event if not yet received`
+
+ 04-18 14:30:49.956 10298 19745 19745 I BaseModuleTask: event=ModuleEvent{message=Pair Step: Write account key, status=SUCCESS}, callback=dxh@74d2dcb, executor=ayp@5d289a8
+ 04-18 14:30:50.096 10298 19745 19745 I BaseModuleTask: event=ModuleEvent{message=Pair Step: FINISHED, status=SUCCESS}, callback=dxh@74d2dcb, executor=ayp@5d289a8
+ 04-18 14:30:50.098 10298 19745 26174 I BaseModuleTask: event=ModuleEvent{message=Wait 60000 ms for the connection event if not yet received., status=SUCCESS}, callback=dxh@74d2dcb, executor=ayp@5d289a8
+
+`LE ACL also disconnected due to l2c_link_timeout`
+
+`04-18 14:30:51.083 1002 2508 2910 I btm_acl : disconnect_acl: Disconnecting peer:xx:xx:xx:xx:22:88 reason:HCI_ERR_PEER_USER comment:stack::l2cap::l2c_link::l2c_link_timeout All channels closed 04-18 14:30:51.134 1002 2508 2910 I bt_shim_hci: packages/modules/Bluetooth/system/main/shim/hci_layer.cc:304 - operator(): ISO disconnection from GD, handle: 0x41, reason: 0x16 `
+
+`We could see pairing process failed because ACL was not connected`
+
+ 04-18 14:31:50.101 10298 19745 26174 I BaseModuleTask: event=ModuleEvent{message=Pairing process error. Reason: Is connected: false
+ 04-18 14:31:50.102 10298 19745 26174 I BaseModuleTask: event=ModuleEvent{message=Initial pair failed, status=FAILURE}, callback=dxh@74d2dcb, executor=ayp@5d289a8
+ 04-18 14:31:50.122 10298 19745 26174 I BaseModuleTask: event=ModuleEvent{message=Test finished, status=FAILURE}, callback=dxh@74d2dcb, executor=ayp@5d289a8
+
+`Bond was removed`
+
+ 04-18 14:31:50.133 10298 19745 26174 I FastPair: BluetoothAudioPairer: unpair: device=XX:XX:XX:XX:22:88, methodName=removeBond
+ 04-18 14:31:50.134 10298 19745 26174 I BluetoothDevice: removeBond() for device XX:XX:XX:XX:22:88 called by pid: 19745 tid: 26174
+ 04-18 14:31:50.146 1002 2508 2994 I BluetoothBondStateMachine: Bond State Change Intent:XX:XX:XX:XX:22:88 BOND_BONDED => BOND_NONE
+ 04-18 14:31:51.167 10298 19745 26174 I BaseModuleTask: event=ModuleEvent{message=Task done, status=SUCCESS}, callback=dxh@74d2dcb, executor=ayp@5d289a8
+
+\
diff --git a/Public+Key+Based+Pairing+Request+in+non+discoverable+mode.md b/Public+Key+Based+Pairing+Request+in+non+discoverable+mode.md
new file mode 100644
index 0000000..ca852aa
--- /dev/null
+++ b/Public+Key+Based+Pairing+Request+in+non+discoverable+mode.md
@@ -0,0 +1,5 @@
+# Public Key Based Pairing Request in non discoverable mode
+
+
+
+[BB2BUG-52885] [BB2][RTL8763ESE][Amazon/OSM][头戴立体声耳机][OSHA-37]Fast Pair Validator软件测试项public key based pairing request in non discoverable mode运行失败 - Jira
diff --git a/Public+key+Based+Pairing+Failed+in+Non-Discoverable+Mode+Test+Fail.md b/Public+key+Based+Pairing+Failed+in+Non-Discoverable+Mode+Test+Fail.md
new file mode 100644
index 0000000..2f31e20
--- /dev/null
+++ b/Public+key+Based+Pairing+Failed+in+Non-Discoverable+Mode+Test+Fail.md
@@ -0,0 +1,7 @@
+# Public key Based Pairing Failed in Non-Discoverable Mode Test Fail
+
+[BBPRO3BUG-28457] [BBPRO3][EVB][E Cut][3.15.0.8_0128+TestBin]Fast pair Validator APP测试， Public key Based Pairing Failed in Non-Discoverable Mode Test Fail - Jira
+
+[BB2BUG-54004] [BB2][RTL8763ESH/ROM][GMI][沃莱特/MINAMI][Harman][Pace] GFPS Public Key Based Pairing Failedin Non-Discoverable Mode测试failed - Jira
+
+\
diff --git a/Reason_+Test+fail+after+connectioning.md b/Reason_+Test+fail+after+connectioning.md
new file mode 100644
index 0000000..14adbd9
--- /dev/null
+++ b/Reason_+Test+fail+after+connectioning.md
@@ -0,0 +1,5 @@
+# Reason: Test fail after connectioning
+
+
+
+COM96_2023-03-29_17-47-45.zip
diff --git a/Reason_+device+not+found+by+EID.md b/Reason_+device+not+found+by+EID.md
new file mode 100644
index 0000000..ed0f5e8
--- /dev/null
+++ b/Reason_+device+not+found+by+EID.md
@@ -0,0 +1,19 @@
+# Reason: device not found by EID
+
+\
+
+原因是测试过程中auto power off了。
+
+MCU cfg tool 里面需要disable auto power off ，disable pairing timeout 这两个选项
+
+1)disable auto power off, disable pairing timeout
+
+**Note**:修改仅为了便于GFPS测试
+
+
+
+\
+
+COM3_2023-03-28_11-15-29.log
+
+COM3_btsnoop_2023-03-28_11-06-35.cfa
diff --git a/Reason_+wrong+value+of+'unwanted+tracking+protection+mode'+in+Hashed+Flags_disabled.md b/Reason_+wrong+value+of+'unwanted+tracking+protection+mode'+in+Hashed+Flags_disabled.md
new file mode 100644
index 0000000..2b7b31b
--- /dev/null
+++ b/Reason_+wrong+value+of+'unwanted+tracking+protection+mode'+in+Hashed+Flags_disabled.md
@@ -0,0 +1,26 @@
+# Reason: wrong value of 'unwanted tracking protection mode' in Hashed Flags:disabled
+
+[BB2BUG-47983] [BB2][RTL8763ESH/ROM][GMI][沃莱特][Harman][T530][IOS]188- [Google Finder]Unwanted tracking protection Automated test fail - Jira
+
+这个error 感觉像是手机的问题呢，请问重启手机再试试看呢？
+
+\
+
+