gfps: 添加认证测试和FAQ 20260505
All checks were successful
Sync To /home/ubuntu/gfps / sync (push) Successful in 2s
All checks were successful
Sync To /home/ubuntu/gfps / sync (push) Successful in 2s
Change-Id: I71e676b997159a141ca07d16f82a73b45f4b2410
This commit is contained in:
danni_dong
3
1+BREDR+++GFPS.md
Normal file
3
1+BREDR+++GFPS.md
Normal file
@@ -0,0 +1,3 @@
|
||||
# 1 BREDR + GFPS
|
||||
|
||||
该功能是通过GFPS 快速配对BREDR
|
||||
7
1+Distance+测试失败.md
Normal file
7
1+Distance+测试失败.md
Normal file
@@ -0,0 +1,7 @@
|
||||
# 1 Distance 测试失败
|
||||
|
||||
客户端测试1.2m不会有弹窗，认证实验室验证的时候1.2m却有弹窗：
|
||||
|
||||
|
||||
|
||||
<a href="https://jira.realtek.com/browse/BBPRO3BUG-28971" class="external-link" rel="nofollow">[BBPRO3BUG-28971] [BBPro3][RTL8773DFL+RTL8763EAU][GMI/WLT/JLAB_Daybreak][Gaming Stereo/Audio mixing]: GFPS pixel 7(android 13)没有弹窗 - Jira</a>
|
||||
13
1+Error+performing+GATT+operation_+.......md
Normal file
13
1+Error+performing+GATT+operation_+.......md
Normal file
@@ -0,0 +1,13 @@
|
||||
# 1 Error performing GATT operation: ......
|
||||
|
||||
|
||||
|
||||
耳机端不支援LEA， 手机端测试的时候好像setting界面开发者选项里面把 Bypass Bluetooth LE Audio Allowlist 打开了， 需要把Bypass Bluetooth LE Audio Allowlist 关掉并且重启手机再测试
|
||||
|
||||
|
||||
|
||||
\
|
||||
|
||||
<a href="https://partnerissuetracker.corp.google.com/u/0/issues/422213477" class="external-link" rel="nofollow">https://partnerissuetracker.corp.google.com/u/0/issues/422213477</a>
|
||||
|
||||
\
|
||||
11
1+Error+performing+GATT+operation_+fe2c1238-8366-......md
Normal file
11
1+Error+performing+GATT+operation_+fe2c1238-8366-......md
Normal file
@@ -0,0 +1,11 @@
|
||||
# 1 Error performing GATT operation: fe2c1238-8366-.....
|
||||
|
||||
<span style="color: rgb(0,51,102);">**测试手机支援LEA, 开发者选项中将 Bypass Bluetooth LE Audio 选项关掉，然后重启手机，再重新测试，好像就不会遇到上面截图对应的问题了**</span>
|
||||
|
||||
<span style="color: rgb(255,0,0);">****</span>
|
||||
|
||||
|
||||
|
||||
\
|
||||
|
||||
|
||||
1
1+Fast+Pair+Validator+FAQ.md
Normal file
1
1+Fast+Pair+Validator+FAQ.md
Normal file
@@ -0,0 +1 @@
|
||||
# 1 Fast Pair Validator FAQ
|
||||
5
1+Firmware+Version+with+LE+audio+conn....md
Normal file
5
1+Firmware+Version+with+LE+audio+conn....md
Normal file
@@ -0,0 +1,5 @@
|
||||
# 1 Firmware Version with LE audio conn...
|
||||
|
||||
|
||||
|
||||
<a href="https://jira.realtek.com/browse/BB2BUG-52827" class="external-link" rel="nofollow">[BB2BUG-52827] [BB2][8763EWM][Tiger][GFPS][fast pair validator][fast pair測項][LE Audio] Firmware version 測試fail - Jira</a>
|
||||
228
1+GFPS+legacy+pair+搭配支援LEA手机不连+legacy+profile(A2DP_HFP).md
Normal file
228
1+GFPS+legacy+pair+搭配支援LEA手机不连+legacy+profile(A2DP_HFP).md
Normal file
@@ -0,0 +1,228 @@
|
||||
# 1 GFPS legacy pair 搭配支援LEA手机不连 legacy profile(A2DP/HFP)
|
||||
|
||||
耳机端走的是GFPS legacy pair， 和支援LEA的手机做initial pair， 支援LEA的手机不连legacy profile,
|
||||
|
||||
**测试发现：**
|
||||
|
||||
**<span style="color: rgb(255,0,0);">打开legacy CTKD LE </span>的功能之后 <span style="color: rgb(255,0,0);">支援LEA的手机就会来连legacy profile</span>**
|
||||
|
||||
**<span style="color: rgb(255,0,0);">关闭 legacy CTKD LE </span>功能之后， <span style="color: rgb(255,0,0);">支援LEA的手机就不会来连legacy profile</span>**
|
||||
|
||||
<a href="https://jira.realtek.com/browse/BBPRO3BUG-24407" class="external-link" rel="nofollow">[BBPRO3BUG-24407] [BBPRO3][EVB][E Cut][3.15.0.5+TestBin][Single]配置Finder，耳机开机进配对，无法连接到Find Device - Jira</a>
|
||||
|
||||
<a href="https://partnerissuetracker.corp.google.com/u/0/issues/441653921" class="external-link" rel="nofollow">https://partnerissuetracker.corp.google.com/u/0/issues/441653921</a>
|
||||
|
||||
\
|
||||
|
||||
\
|
||||
|
||||
<a href="https://partnerissuetracker.corp.google.com/u/0/issues/411582869" class="external-link" rel="nofollow">https://partnerissuetracker.corp.google.com/u/0/issues/411582869</a>
|
||||
|
||||
<table class="wrapped confluenceTable">
|
||||
<tbody>
|
||||
<tr>
|
||||
<th class="confluenceTh" scope="col"><p><span style="color: rgb(255,0,0);">// Device bonded</span><br />
|
||||
04-18 14:30:36.473 1002 2508 2994 I <span style="color: rgb(255,0,0);">BluetoothBondStateMachine</span>: XX:XX:XX:XX:22:88 is bonded, wait for SDP complete to broadcast bonded intent</p>
|
||||
<p><strong><span style="color: rgb(255,0,0);">// SDP</span></strong><br />
|
||||
04-18 14:30:36.606 1002 2508 2910 I bt_bta_dm: bta_dm_sdp_result: <span style="color: rgb(255,0,0);">GATT services discovered using SDP</span><br />
|
||||
04-18 14:30:36.606 1002 2508 2910 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/<a href="http://btif_dm.cc" class="external-link" rel="nofollow">btif_dm.cc</a>:1798 - btif_dm_search_services_evt:<span style="color: rgb(255,0,0);"> SDP finished</span> for xx:xx:xx:xx:22:88:<br />
|
||||
04-18 14:30:36.606 1002 2508 2910 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/<a href="http://btif_dm.cc" class="external-link" rel="nofollow">btif_dm.cc</a>:1807 - btif_dm_search_services_evt: New UUIDs for xx:xx:xx:xx:22:88:<br />
|
||||
04-18 14:30:36.606 1002 2508 2910 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/<a href="http://btif_dm.cc" class="external-link" rel="nofollow">btif_dm.cc</a>:1813 - btif_dm_search_services_evt: index:0 uuid:00001101-0000-1000-8000-00805f9b34fb</p>
|
||||
<p><span style="color: rgb(255,0,0);">// 1108 UUID_HEADSET</span><br />
|
||||
04-18 14:30:36.606 1002 2508 2910 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/<a href="http://btif_dm.cc" class="external-link" rel="nofollow">btif_dm.cc</a>:1813 - btif_dm_search_services_evt: index:1 uuid:0000<span style="color: rgb(255,0,0);">1108</span>-0000-1000-8000-00805f9b34fb</p>
|
||||
<p><span style="color: rgb(255,0,0);">// 111E UUID_HANDSFREE</span><br />
|
||||
04-18 14:30:36.607 1002 2508 2910 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/<a href="http://btif_dm.cc" class="external-link" rel="nofollow">btif_dm.cc</a>:1813 - btif_dm_search_services_evt: index:2 uuid:0000<span style="color: rgb(255,0,0);">111e</span>-0000-1000-8000-00805f9b34fb</p>
|
||||
<p><span style="color: rgb(255,0,0);">//110B UUID_AUDIO_SINK</span><br />
|
||||
04-18 14:30:36.607 1002 2508 2910 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/<a href="http://btif_dm.cc" class="external-link" rel="nofollow">btif_dm.cc</a>:1813 - btif_dm_search_services_evt: index:3 uuid:0000<span style="color: rgb(255,0,0);">110b</span>-0000-1000-8000-00805f9b34fb<br />
|
||||
04-18 14:30:36.607 1002 2508 2910 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/<a href="http://btif_dm.cc" class="external-link" rel="nofollow">btif_dm.cc</a>:1813 - btif_dm_search_services_evt: index:4 uuid:0000110e-0000-1000-8000-00805f9b34fb<br />
|
||||
04-18 14:30:36.607 1002 2508 2910 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/<a href="http://btif_dm.cc" class="external-link" rel="nofollow">btif_dm.cc</a>:1813 - btif_dm_search_services_evt: index:7 uuid:6a24eeab-4b65-4693-986b-3c26c352264f<br />
|
||||
04-18 14:30:36.607 1002 2508 2910 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/<a href="http://btif_dm.cc" class="external-link" rel="nofollow">btif_dm.cc</a>:1813 - btif_dm_search_services_evt: index:8 uuid:df21fe2c-2515-4fdb-8886-f12c4d67927c<br />
|
||||
04-18 14:30:36.607 1002 2508 2910 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/<a href="http://btif_dm.cc" class="external-link" rel="nofollow">btif_dm.cc</a>:498 - get_cod: remote_cod=0x00244404<br />
|
||||
04-18 14:30:36.607 1002 2508 2910 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/<a href="http://btif_dm.cc" class="external-link" rel="nofollow">btif_dm.cc</a>:1863 - btif_dm_search_services_evt: SDP search done for xx:xx:xx:xx:22:88</p>
|
||||
<p><span style="color: rgb(255,0,0);">// Not sure if waiting for LE service discovery here</span><br />
|
||||
04-18 14:30:36.607 1002 2508 2910 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/<a href="http://btif_dm.cc" class="external-link" rel="nofollow">btif_dm.cc</a>: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<br />
|
||||
04-18 14:30:36.607 1002 2508 2910 I bt_bta_dm: bta_dm_search_cmpl: No BLE connection, processing classic results</p>
|
||||
<p><span style="color: rgb(255,0,0);">// Phone disconnected from provider.</span><br />
|
||||
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<br />
|
||||
32183 06:30:40.616070 host controller HCI_CMD 7 Sent Disconnect</p></th>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
<table class="wrapped confluenceTable">
|
||||
<tbody>
|
||||
<tr>
|
||||
<th class="confluenceTh" scope="col"><p><span style="color: rgb(255,0,0);">// ACL LE connected</span></p>
|
||||
<p>04-18 14:30:32.132 1002 1048 2043 I bthal.activity: handle_ble_meta_event:<span style="color: rgb(255,0,0);"> LE Enhanced Connection Complete</span>, conn_handle:041, conn_bda: XX:XX:44:44:22:88<br />
|
||||
04-18 14:30:32.223 1002 2508 2910 I bt_bta_dm: bta_dm_acl_up:<span style="color: rgb(255,0,0);"> Acl connected</span> peer:xx:xx:xx:xx:22:88 <span style="color: rgb(255,0,0);">transport:BT_TRANSPORT_LE</span> handle:65<br />
|
||||
04-18 14:30:34.934 1002 2508 2910 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/<a href="http://btif_dm.cc" class="external-link" rel="nofollow">btif_dm.cc</a>:586 - bond_state_changed: Bond state changed to state=1[0:none, 1:bonding, 2:bonded],prev_state=0, sdp_attempts=0<br />
|
||||
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<br />
|
||||
04-18 14:30:34.944 1002 2508 2994 I BluetoothBondStateMachine: Bond State Change Intent:XX:XX:XX:XX:22:88 <span style="color: rgb(255,0,0);">BOND_NONE => BOND_BONDING</span></p>
|
||||
<p><span style="color: rgb(255,0,0);">// ACL BR/EDR connected</span></p>
|
||||
<p>04-18 14:30:36.075 1002 2508 2910 I bt_bta_dm: bta_dm_acl_up: <span style="color: rgb(255,0,0);">Acl connected</span> peer:xx:xx:xx:xx:22:88 <span style="color: rgb(255,0,0);">transport:BT_TRANSPORT_BR_EDR </span>handle:11<br />
|
||||
04-18 14:30:36.467 1002 2508 2910 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/<a href="http://btif_dm.cc" class="external-link" rel="nofollow">btif_dm.cc</a>:586 - bond_state_changed: Bond state changed to state=2[0:none, 1:bonding, 2:bonded],prev_state=1, sdp_attempts=1<br />
|
||||
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<br />
|
||||
04-18 14:30:36.473 1002 2508 2994 I BluetoothBondStateMachine: XX:XX:XX:XX:22:88 is bonded, <span style="color: rgb(255,0,0);">wait for SDP complete to broadcast bonded intent</span><br />
|
||||
04-18 14:30:36.473 1002 2508 2994 I BluetoothBondStateMachine: StableState(): Entering Off State<br />
|
||||
04-18 14:30:36.607 1002 2508 2910 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/<a href="http://btif_dm.cc" class="external-link" rel="nofollow">btif_dm.cc</a>: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<br />
|
||||
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<br />
|
||||
<span style="color: rgb(255,0,0);">// BT_ACL_STATE_DISCONNECTED</span></p>
|
||||
<p>04-18 14:30:40.768 1002 2508 2910 I bt_shim_hci: packages/modules/Bluetooth/system/main/shim/<a href="http://hci_layer.cc" class="external-link" rel="nofollow">hci_layer.cc</a>:304 - operator(): ISO disconnection from GD, handle: 0x0b, reason: 0x13<br />
|
||||
04-18 14:30:40.769 1002 2508 2910 D bt_btif_dm: packages/modules/Bluetooth/system/btif/src/<a href="http://btif_dm.cc" class="external-link" rel="nofollow">btif_dm.cc</a>: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<br />
|
||||
04-18 14:30:51.134 1002 2508 2910 I bt_shim_hci: packages/modules/Bluetooth/system/main/shim/<a href="http://hci_layer.cc" class="external-link" rel="nofollow">hci_layer.cc</a>:304 - operator(): ISO disconnection from GD, handle: 0x41, reason: 0x16<br />
|
||||
04-18 14:30:51.137 1002 2508 2910 D bt_btif_dm: packages/modules/Bluetooth/system/btif/src/<a href="http://btif_dm.cc" class="external-link" rel="nofollow">btif_dm.cc</a>:2552 - btif_dm_acl_evt: Sent BT_ACL_STATE_DISCONNECTED upward as ACL link down event device:xx:xx:xx:xx:22:88 reason:<span style="color: rgb(255,0,0);">HCI_ERR_CONN_CAUSE_LOCAL_HOST</span><br />
|
||||
<span style="color: rgb(255,0,0);">// Bonding Removed</span></p>
|
||||
<p>04-18 14:31:50.137 1002 2508 2910 I bt_btif_storage: packages/modules/Bluetooth/system/btif/src/<a href="http://btif_storage.cc" class="external-link" rel="nofollow">btif_storage.cc</a>:889 - btif_storage_remove_bonded_device: Removing bonded device addr=xx:xx:xx:xx:22:88<br />
|
||||
04-18 14:31:50.137 1002 2508 2910 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/<a href="http://btif_dm.cc" class="external-link" rel="nofollow">btif_dm.cc</a>:586 - bond_state_changed: Bond state changed to state=0[0:none, 1:bonding, 2:bonded],prev_state=2, sdp_attempts=0<br />
|
||||
04-18 14:31:50.137 1002 2508 2910 I bt_btif_storage: packages/modules/Bluetooth/system/btif/src/<a href="http://btif_storage.cc" class="external-link" rel="nofollow">btif_storage.cc</a>:889 - <span style="color: rgb(255,0,0);">btif_storage_remove_bonded_device</span>: Removing bonded device addr=xx:xx:xx:xx:22:88<br />
|
||||
04-18 14:31:50.137 1002 2508 2910 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/<a href="http://btif_dm.cc" class="external-link" rel="nofollow">btif_dm.cc</a>:586 - bond_state_changed: Bond state changed to state=0[0:none, 1:bonding, 2:bonded],prev_state=0, sdp_attempts=0<br />
|
||||
04-18 14:31:50.137 1002 2508 2910 E BluetoothMetricIdManager: packages/modules/Bluetooth/system/gd/common/<a href="http://metric_id_manager.cc" class="external-link" rel="nofollow">metric_id_manager.cc</a>:190 - ForgetDevice: Failed to remove device from paired_device_cache_<br />
|
||||
04-18 14:31:50.140 1002 2508 2994 D AdapterProperties: Removing bonded device:XX:XX:XX:XX:22:88<br />
|
||||
04-18 14:31:50.146 1002 2508 2994 I BluetoothBondStateMachine: Bond State Change Intent:XX:XX:XX:XX:22:88 <span style="color: rgb(255,0,0);">BOND_BONDED => BOND_NONE</span><br />
|
||||
04-18 14:31:50.147 1002 2508 2994 I BluetoothBondStateMachine: StableState(): Entering Off State</p></th>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
<table class="wrapped confluenceTable">
|
||||
<tbody>
|
||||
<tr>
|
||||
<th class="confluenceTh" scope="col"><p><span style="color: rgb(255,0,0);">//Pairing starts</span></p>
|
||||
<p>04-18 14:30:32.100 I NearbyDiscovery: FastPairController: Validator: onValidatorConnectionRequested [CONTEXT service_id=265 ] <br />
|
||||
04-18 14:30:32.100 I<span style="color: rgb(255,0,0);"> FastPair: FPDC: Starting to pair</span> XX:XX:XX:XX:22:88: key[64], Preferences{gattOperationTimeoutSeconds=10, gattConnectionTimeoutSeconds=15, bluetoothToggleTimeoutSeconds=10, bluetoothToggleSleepSeconds=2, <br />
|
||||
04-18 14:30:32.107 D FastPairUtils: FastPair: Pairing finished with intent action: com.google.android.gms.nearby.discovery.ACTION_VALIDATOR_PAIR_PROGRESS <br />
|
||||
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 <br />
|
||||
04-18 14:30:32.223 I bt_bta_dm: bta_dm_acl_up:<span style="color: rgb(255,0,0);"> Acl connected peer:xx:xx:xx:xx:22:88 transport:BT_TRANSPORT_LE</span> handle:65 <br />
|
||||
04-18 14:30:32.224 D BluetoothDatabase: getProfileConnectionPolicy: device XX:XX:XX:XX:22:88 is not in cache <br />
|
||||
04-18 14:30:33.870 D FastPairUtils: FastPair: Pairing finished with intent action: com.google.android.gms.nearby.discovery.ACTION_VALIDATOR_PAIR_PROGRESS <br />
|
||||
04-18 14:30:34.922 D FastPairUtils: FastPair: Pairing finished with intent action: com.google.android.gms.nearby.discovery.ACTION_VALIDATOR_PAIR_PROGRESS <br />
|
||||
04-18 14:30:34.944 I BluetoothBondStateMachine: Bond State Change Intent:XX:XX:XX:XX:22:88 <span style="color: rgb(255,0,0);">BOND_NONE => BOND_BONDING </span> <br />
|
||||
04-18 14:30:36.075 I bt_bta_dm: bta_dm_acl_up: <span style="color: rgb(255,0,0);">Acl connected peer:xx:xx:xx:xx:22:88 transport:BT_TRANSPORT_BR_EDR</span> handle:11 <br />
|
||||
04-18 14:30:36.201 D CachedBluetoothDevice: Device name: JBL Tune 530BT <br />
|
||||
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]</p>
|
||||
<p><span style="color: rgb(255,0,0);">//UUIDs discovered and device bonded</span></p>
|
||||
<p>04-18 14:30:36.606 D bt_btif_dm: packages/modules/Bluetooth/system/btif/src/<a href="http://btif_dm.cc" class="external-link" rel="nofollow">btif_dm.cc</a>:1985 - btif_dm_search_services_evt: New GATT over SDP UUIDs for xx:xx:xx:xx:22:88: <br />
|
||||
04-18 14:30:36.606 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/<a href="http://btif_dm.cc" class="external-link" rel="nofollow">btif_dm.cc</a>:2002 - btif_dm_search_services_evt: No well known GATT services discovered <br />
|
||||
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] <br />
|
||||
04-18 14:30:36.606 V bt_btif_dm: packages/modules/Bluetooth/system/btif/src/<a href="http://btif_dm.cc" class="external-link" rel="nofollow">btif_dm.cc</a>:1777 - btif_dm_search_services_evt: result=0x0, services 0xc00c0062 <br />
|
||||
04-18 14:30:36.606 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/<a href="http://btif_dm.cc" class="external-link" rel="nofollow">btif_dm.cc</a>:1798 - btif_dm_search_services_evt: <span style="color: rgb(255,0,0);">SDP finished</span> for xx:xx:xx:xx:22:88: <br />
|
||||
04-18 14:30:36.606 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/<a href="http://btif_dm.cc" class="external-link" rel="nofollow">btif_dm.cc</a>:1807 - btif_dm_search_services_evt: New UUIDs for xx:xx:xx:xx:22:88: <br />
|
||||
04-18 14:30:36.606 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/<a href="http://btif_dm.cc" class="external-link" rel="nofollow">btif_dm.cc</a>:1813 - btif_dm_search_services_evt: index:0 uuid:00001101-0000-1000-8000-00805f9b34fb <br />
|
||||
04-18 14:30:36.606 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/<a href="http://btif_dm.cc" class="external-link" rel="nofollow">btif_dm.cc</a>:1813 - btif_dm_search_services_evt: index:1 uuid:00001108-0000-1000-8000-00805f9b34fb <br />
|
||||
04-18 14:30:36.607 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/<a href="http://btif_dm.cc" class="external-link" rel="nofollow">btif_dm.cc</a>:1813 - btif_dm_search_services_evt: index:2 uuid:0000111e-0000-1000-8000-00805f9b34fb <br />
|
||||
04-18 14:30:36.607 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/<a href="http://btif_dm.cc" class="external-link" rel="nofollow">btif_dm.cc</a>:1813 - btif_dm_search_services_evt: index:3 uuid:0000110b-0000-1000-8000-00805f9b34fb <br />
|
||||
04-18 14:30:36.607 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/<a href="http://btif_dm.cc" class="external-link" rel="nofollow">btif_dm.cc</a>:1813 - btif_dm_search_services_evt: index:4 uuid:0000110e-0000-1000-8000-00805f9b34fb <br />
|
||||
04-18 14:30:36.607 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/<a href="http://btif_dm.cc" class="external-link" rel="nofollow">btif_dm.cc</a>:1813 - btif_dm_search_services_evt: index:7 uuid:6a24eeab-4b65-4693-986b-3c26c352264f <br />
|
||||
04-18 14:30:36.607 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/<a href="http://btif_dm.cc" class="external-link" rel="nofollow">btif_dm.cc</a>:1813 - btif_dm_search_services_evt: index:8 uuid:df21fe2c-2515-4fdb-8886-f12c4d67927c <br />
|
||||
04-18 14:30:36.607 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/<a href="http://btif_dm.cc" class="external-link" rel="nofollow">btif_dm.cc</a>:1863 - btif_dm_search_services_evt: SDP search done for xx:xx:xx:xx:22:88 <br />
|
||||
04-18 14:30:36.607 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/<a href="http://btif_dm.cc" class="external-link" rel="nofollow">btif_dm.cc</a>: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 <br />
|
||||
04-18 14:30:36.607 I bt_bta_dm: bta_dm_search_cmpl: No BLE connection, processing classic results <br />
|
||||
04-18 14:30:39.492 I BluetoothBondStateMachine: Bond State Change Intent:XX:XX:XX:XX:22:88 BOND_BONDING => BOND_BONDED <br />
|
||||
04-18 14:30:39.993 I FastPair: BluetoothAudioPairer: BondedReceiver: handleBondStateChanged: device=XX:XX:XX:XX:22:88, state=12, reason=-2147483648<br />
|
||||
Connectionpolicy is -1 for all profiles</p>
|
||||
<p>04-18 14:30:40.018 D CachedBluetoothDevice: No profiles. Maybe we will connect later for device XX:XX:XX:XX:22:88 <br />
|
||||
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::<span style="color: rgb(255,0,0);">l2c_link_timeout </span>All channels closed <br />
|
||||
04-18 14:30:40.768 I bt_shim_hci: packages/modules/Bluetooth/system/main/shim/<a href="http://hci_layer.cc" class="external-link" rel="nofollow">hci_layer.cc</a>:304 - operator(): ISO disconnection from GD, handle: 0x0b, reason: 0x13 </p>
|
||||
<p><span style="color: rgb(255,0,0);">// connectionPolicy=-1 -1是指失败</span><br />
|
||||
04-18 14:30:40.777 V BluetoothDatabase: getProfileConnectionPolicy: device XX:XX:XX:XX:22:88 profile=A2DP, connectionPolicy=-1<br />
|
||||
04-18 14:30:40.777 V BluetoothDatabase: getProfileConnectionPolicy: device XX:XX:XX:XX:22:88 profile=HEADSET, connectionPolicy=-1<br />
|
||||
04-18 14:30:40.777 V BluetoothDatabase: getProfileConnectionPolicy: device XX:XX:XX:XX:22:88 profile=HID_HOST, connectionPolicy=-1<br />
|
||||
04-18 14:30:40.777 V BluetoothDatabase: getProfileConnectionPolicy: device XX:XX:XX:XX:22:88 profile=PAN, connectionPolicy=-1<br />
|
||||
04-18 14:30:40.777 V BluetoothDatabase: getProfileConnectionPolicy: device XX:XX:XX:XX:22:88 profile=HEARING_AID, connectionPolicy=-1<br />
|
||||
04-18 14:30:40.777 V BluetoothDatabase: getProfileConnectionPolicy: device XX:XX:XX:XX:22:88 profile=HAP_CLIENT, connectionPolicy=-1<br />
|
||||
04-18 14:30:40.777 V BluetoothDatabase: getProfileConnectionPolicy: device XX:XX:XX:XX:22:88 profile=VOLUME_CONTROL, connectionPolicy=-1<br />
|
||||
04-18 14:30:40.777 V BluetoothDatabase: getProfileConnectionPolicy: device XX:XX:XX:XX:22:88 profile=CSIP_SET_COORDINATOR, connectionPolicy=-1<br />
|
||||
04-18 14:30:40.777 V BluetoothDatabase: getProfileConnectionPolicy: device XX:XX:XX:XX:22:88 profile=LE_AUDIO, connectionPolicy=-1 </p>
|
||||
<p><span style="color: rgb(255,0,0);">//created bond but never received UUIDs</span></p>
|
||||
<p>04-18 14:30:49.941 W FastPair: BluetoothAudioPairer: pair: created bond but never received UUIDs, attempting to continue. <br />
|
||||
Device disconnected</p>
|
||||
<p>04-18 14:30:50.083 I bluetooth: disconnect: Device: xx:xx:xx:xx:22:88, cid: 0xffff <br />
|
||||
04-18 14:30:50.086 I FastPair: Gatt connection with XX:XX:XX:XX:22:88 closed. <br />
|
||||
04-18 14:30:50.097 D FastPairUtils: FastPair: Pairing finished with intent action: com.google.android.gms.nearby.discovery.ACTION_VALIDATOR_PAIR_PROGRESS <br />
|
||||
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 <br />
|
||||
04-18 14:30:51.134 I bt_shim_hci: packages/modules/Bluetooth/system/main/shim/<a href="http://hci_layer.cc" class="external-link" rel="nofollow">hci_layer.cc</a>:304 - operator(): ISO disconnection from GD, handle: 0x41, reason: 0x16 <br />
|
||||
04-18 14:30:51.135 I bluetooth: disconnect: Device: xx:xx:xx:xx:22:88, cid: 0xffff <br />
|
||||
04-18 14:31:50.101 I BaseModuleTask: event=ModuleEvent{message=Pairing process error. Reason: Is connected: false <br />
|
||||
04-18 14:31:50.102 D FeatureTestActivity: ModuleEvent{message=Pairing process error. Reason: Is connected: false <br />
|
||||
04-18 14:31:50.133 I FastPair: BluetoothAudioPairer: unpair: device=XX:XX:XX:XX:22:88, methodName=removeBond <br />
|
||||
04-18 14:31:50.134 I BluetoothDevice: removeBond() for device XX:XX:XX:XX:22:88 called by pid: 19745 tid: 26174 <br />
|
||||
04-18 14:31:50.146 I BluetoothBondStateMachine: Bond State Change Intent:XX:XX:XX:XX:22:88 <span style="color: rgb(255,0,0);">BOND_BONDED => BOND_NONE </span></p>
|
||||
<p><br />
|
||||
</p>
|
||||
<p><br />
|
||||
</p>
|
||||
<p>正常的流程</p>
|
||||
<p><span style="color: rgb(255,0,0);">//Pairing starts</span></p>
|
||||
<p>04-18 10:50:49.219 I NearbyDiscovery: FastPairController: Validator: onValidatorConnectionRequested [CONTEXT service_id=265 ] <br />
|
||||
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, <br />
|
||||
04-18 10:50:49.288 I bthal.activity: handle_ble_meta_event: <span style="color: rgb(255,0,0);">LE Enhanced Connection Complete</span>, conn_handle:041, conn_bda: XX:XX:55:0b:94:09 <br />
|
||||
04-18 10:50:49.412 I bt_bta_dm: bta_dm_acl_up: Acl connected peer:xx:xx:xx:xx:94:09 transport:<span style="color: rgb(255,0,0);">BT_TRANSPORT_LE handle:65 </span> <br />
|
||||
04-18 10:50:49.416 D BluetoothDatabase: getProfileConnectionPolicy: device XX:XX:XX:XX:94:09 is not in cache <br />
|
||||
04-18 10:50:51.779 I BluetoothBondStateMachine: Bond State Change Intent:XX:XX:XX:XX:94:09 <span style="color: rgb(255,0,0);">BOND_NONE => BOND_BONDING </span> <br />
|
||||
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] <br />
|
||||
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] </p>
|
||||
<p> <br />
|
||||
<span style="color: rgb(255,0,0);">//UUIDs discovered</span></p>
|
||||
<p>04-18 10:50:54.679 I bt_bta_dm: bta_dm_execute_queued_request: Start pending discovery <br />
|
||||
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] <br />
|
||||
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 <br />
|
||||
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] <br />
|
||||
04-18 10:50:54.680 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/<a href="http://btif_dm.cc" class="external-link" rel="nofollow">btif_dm.cc</a>:1952 - btif_dm_search_services_evt: New GATT over LE UUIDs for xx:xx:xx:xx:94:09: <br />
|
||||
04-18 10:50:54.680 D bt_btif_dm: packages/modules/Bluetooth/system/btif/src/<a href="http://btif_dm.cc" class="external-link" rel="nofollow">btif_dm.cc</a>:1963 - btif_dm_search_services_evt: clearing pairing_cb <br />
|
||||
04-18 10:50:54.680 D bt_btif_dm: packages/modules/Bluetooth/system/btif/src/<a href="http://btif_dm.cc" class="external-link" rel="nofollow">btif_dm.cc</a>:1971 - btif_dm_search_services_evt: Scheduling conn params unlock for xx:xx:xx:xx:94:09 <br />
|
||||
04-18 10:50:54.680 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/<a href="http://btif_dm.cc" class="external-link" rel="nofollow">btif_dm.cc</a>:1996 - btif_dm_search_services_evt: index:0 uuid:0000180f-0000-1000-8000-00805f9b34fb <br />
|
||||
04-18 10:50:54.680 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/<a href="http://btif_dm.cc" class="external-link" rel="nofollow">btif_dm.cc</a>:1996 - btif_dm_search_services_evt: index:1 uuid:00001844-0000-1000-8000-00805f9b34fb <br />
|
||||
04-18 10:50:54.680 I bt_btif_dm: packages/modules/Bluetooth/system/btif/src/<a href="http://btif_dm.cc" class="external-link" rel="nofollow">btif_dm.cc</a>:1996 - btif_dm_search_services_evt: index:2 uuid:0000184e-0000-1000-8000-00805f9b34fb <br />
|
||||
04-18 10:50:54.681 I BluetoothAdapterService: sendUuidsInternal: <span style="color: rgb(255,0,0);">Received service discovery UUIDs</span> for device XX:XX:XX:XX:94:09 <br />
|
||||
04-18 10:50:54.681 D BluetoothAdapterService: sendUuidsInternal: index=0 uuid=00001101-0000-1000-8000-00805f9b34fb <br />
|
||||
04-18 10:50:54.681 D BluetoothAdapterService: sendUuidsInternal: index=1 uuid=00001108-0000-1000-8000-00805f9b34fb <br />
|
||||
04-18 10:50:54.681 D BluetoothAdapterService: sendUuidsInternal: index=2 uuid=0000110b-0000-1000-8000-00805f9b34fb <br />
|
||||
04-18 10:50:54.681 D BluetoothAdapterService: sendUuidsInternal: index=3 uuid=0000110e-0000-1000-8000-00805f9b34fb <br />
|
||||
04-18 10:50:54.681 D BluetoothAdapterService: sendUuidsInternal: index=4 uuid=0000111e-0000-1000-8000-00805f9b34fb <br />
|
||||
04-18 10:50:54.681 D BluetoothAdapterService: sendUuidsInternal: index=5 uuid=0000180f-0000-1000-8000-00805f9b34fb <br />
|
||||
04-18 10:50:54.681 D BluetoothAdapterService: sendUuidsInternal: index=6 uuid=00001844-0000-1000-8000-00805f9b34fb <br />
|
||||
04-18 10:50:54.681 D BluetoothAdapterService: sendUuidsInternal: index=7 uuid=0000184e-0000-1000-8000-00805f9b34fb <br />
|
||||
04-18 10:50:54.681 D BluetoothAdapterService: sendUuidsInternal: index=8 uuid=6a24eeab-4b65-4693-986b-3c26c352264f <br />
|
||||
04-18 10:50:54.681 D BluetoothAdapterService: sendUuidsInternal: index=9 uuid=df21fe2c-2515-4fdb-8886-f12c4d67927c </p>
|
||||
<p><span style="color: rgb(255,0,0);">//Bonded</span></p>
|
||||
<p>04-18 10:50:54.701 I BluetoothBondStateMachine: Bond State Change Intent:XX:XX:XX:XX:94:09<span style="color: rgb(255,0,0);"> BOND_BONDING => BOND_BONDED </span></p>
|
||||
<p>// <span style="color: rgb(255,0,0);">profile=A2DP, connectionPolicy=0</span> <span style="color: rgb(255,0,0);">0 是指连线成功 </span> <br />
|
||||
04-18 10:50:54.737 V BluetoothDatabase: getProfileConnectionPolicy: device XX:XX:XX:XX:94:09<span style="color: rgb(255,0,0);"> profile=A2DP, connectionPolicy=0</span> <br />
|
||||
04-18 10:50:54.737 V BluetoothDatabase: getProfileConnectionPolicy: device XX:XX:XX:XX:94:09 profile=A2DP, connectionPolicy=0 <br />
|
||||
04-18 10:50:54.738 V BluetoothDatabase: getProfileConnectionPolicy: device XX:XX:XX:XX:94:09 profile=<span style="color: rgb(255,0,0);">HEADSET, connectionPolicy=0 </span> <br />
|
||||
04-18 10:50:54.738 V BluetoothDatabase: getProfileConnectionPolicy: device XX:XX:XX:XX:94:09 profile=VOLUME_CONTROL, connectionPolicy=100 <br />
|
||||
04-18 10:50:54.738 V BluetoothDatabase: getProfileConnectionPolicy: device XX:XX:XX:XX:94:09 profile=LE_AUDIO, connectionPolicy=100 </p>
|
||||
<p><span style="color: rgb(255,0,0);">//action.UUID is received and profiles connected</span></p>
|
||||
<p>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] <br />
|
||||
04-18 10:50:54.785 I FastPair: BluetoothAudioPairer: AdditionalBondedReceiver: onReceive: action=android.bluetooth.device.action.UUID, device=XX:XX:XX:XX:94:09 <br />
|
||||
04-18 10:50:56.829 I BluetoothPhonePolicy: processProfileStateChanged, device=XX:XX:XX:XX:94:09, profile=LE_AUDIO, 1 -> 2 <br />
|
||||
04-18 10:50:56.849 I BluetoothPhonePolicy: processProfileStateChanged, device=XX:XX:XX:XX:94:09, profile=VOLUME_CONTROL, 1 -> 2 </p>
|
||||
<p><span style="color: rgb(255,0,0);">//Classic ACL disconnected due no available profiles</span></p>
|
||||
<p>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 <br />
|
||||
04-18 10:50:58.847 I bt_shim_hci: packages/modules/Bluetooth/system/main/shim/<a href="http://hci_layer.cc" class="external-link" rel="nofollow">hci_layer.cc</a>:304 - operator(): ISO disconnection from GD, handle: 0x0b, reason: 0x13 </p>
|
||||
<p><span style="color: rgb(255,0,0);">// Bond removed</span></p>
|
||||
<p>04-18 10:51:06.883 I FastPair: BluetoothAudioPairer: unpair: device=XX:XX:XX:XX:94:09, methodName=removeBond <br />
|
||||
04-18 10:51:06.883 I BluetoothDevice: removeBond() for device XX:XX:XX:XX:94:09 called by pid: 5098 tid: 17729 <br />
|
||||
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 <br />
|
||||
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 <br />
|
||||
04-18 10:51:06.896 I BluetoothPhonePolicy: processProfileStateChanged, device=XX:XX:XX:XX:94:09, profile=VOLUME_CONTROL, 2 -> 3 <br />
|
||||
04-18 10:51:06.897 I BluetoothPhonePolicy: processProfileStateChanged, device=XX:XX:XX:XX:94:09, profile=LE_AUDIO, 2 -> 3 <br />
|
||||
04-18 10:51:06.901 I BluetoothBondStateMachine: Bond State Change Intent:XX:XX:XX:XX:94:09 BOND_BONDED => BOND_NONE <br />
|
||||
04-18 10:51:06.912 I bt_shim_hci: packages/modules/Bluetooth/system/main/shim/<a href="http://hci_layer.cc" class="external-link" rel="nofollow">hci_layer.cc</a>:304 - operator(): ISO disconnection from GD, handle: 0x41, reason: 0x16</p>
|
||||
<p><br />
|
||||
</p>
|
||||
<p><strong><span style="color: rgb(255,0,0);">//Conclusion:</span></strong></p>
|
||||
<p>The uuids are not passed to upper layer.</p>
|
||||
<p>The build seems to be old and there have been changes in this module, please check if it is repro in the latest build.</p>
|
||||
<p>If reproducible, please provide bug report along with issue timestamp/video.</p>
|
||||
<p>Steps to enable full bt_snoop logs:</p>
|
||||
<p>1.Enable Developer options on the device.</p>
|
||||
<p>2.In the Developer options menu, change the Enable Bluetooth HCI snoop log setting to Enabled.</p>
|
||||
<p>3.In the "Logger buffer sizes", change the buffer size to "16M"(or highest possible).</p>
|
||||
<p>4.Enable Verbose Logging from Developer Options (Developer Options -> Enable Bluetooth Stack log -> Select Verbose)</p>
|
||||
<p>5.In the "Store logger data persistently on device" to "All log buffers"</p>
|
||||
<p>6.Restart your phone for logging to take effect</p>
|
||||
<p>7.Try reproducing your issue again and take a new bugreport</p></th>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
70
1+GFPS_Finder如何抓取手机log.md
Normal file
70
1+GFPS_Finder如何抓取手机log.md
Normal file
@@ -0,0 +1,70 @@
|
||||
# 1 GFPS/Finder如何抓取手机log
|
||||
|
||||
<style type="text/css">/**/
|
||||
div.rbtoc1777701819908 {padding: 0px;}
|
||||
div.rbtoc1777701819908 ul {margin-left: 0px;}
|
||||
div.rbtoc1777701819908 li {margin-left: 0px;padding-left: 0px;}
|
||||
|
||||
/**/</style>
|
||||
|
||||
<div class="toc-macro rbtoc1777701819908">
|
||||
|
||||
- [1.请务必详细描述测试步骤及对应时间点，比如：](#id-1GFPS/Finder如何抓取手机log-1.请务必详细描述测试步骤及对应时间点，比如：)
|
||||
- [2.要同步抓取手机端log，耳机端log 以及测试失败截图](#id-1GFPS/Finder如何抓取手机log-2.要同步抓取手机端log，耳机端log以及测试失败截图)
|
||||
- [3.手机端log抓取步骤：](#id-1GFPS/Finder如何抓取手机log-3.手机端log抓取步骤：)
|
||||
|
||||
</div>
|
||||
|
||||
#### **1.请务必详细描述测试步骤及对应时间点，比如：**
|
||||
|
||||
**什么时间点开机；**
|
||||
|
||||
**什么时间点进Pairing mode；**
|
||||
|
||||
**什么时间点点击手机端的GFPS弹窗；**
|
||||
|
||||
**什么时间点失败，手机UI失败原因是什么；**
|
||||
|
||||
**......**
|
||||
|
||||
#### **2.要同步抓取手机端log，耳机端log 以及测试失败截图**
|
||||
|
||||
#### **3.手机端log抓取步骤：**
|
||||
|
||||
<span style="color: rgb(0,51,102);">**3.1.手机setting界面开启 Bluetooth HCI snoop log**</span>
|
||||
|
||||
<span style="color: rgb(0,51,102);">****</span>
|
||||
|
||||
<span style="color: rgb(0,51,102);">****</span>
|
||||
|
||||
<span style="color: rgb(0,51,102);">**3.2.开始复现问题之前，adb 输入以下cmd:**</span>
|
||||
|
||||
<span class="lit"><span style="color: rgb(24,128,56);"><span style="color: rgb(0,51,102);">**`cmd1: `**</span></span></span>`adb`<span class="devsite-syntax-w">` `</span>`logcat`<span class="devsite-syntax-w">` `</span>`-G`<span class="devsite-syntax-w">` `</span>`16M`
|
||||
|
||||
<span class="pln"><span style="color: rgb(0,51,102);">**`cmd2:`**` `</span>`adb shell setprop log`</span><span class="pun">`.`</span><span class="pln">`tag`</span><span class="pun">`.`</span><span class="typ">`NearbyMessages`</span><span class="pln">` VERBOSE`\
|
||||
<span style="color: rgb(0,51,102);">**`cmd3`**</span>`: adb shell setprop log`</span><span class="pun">`.`</span><span class="pln">`tag`</span><span class="pun">`.`</span><span class="typ">`NearbyDiscovery`</span><span class="pln">` VERBOSE`\
|
||||
<span style="color: rgb(0,51,102);">**`cmd4:`**` `</span>`adb shell setprop log`</span><span class="pun">`.`</span><span class="pln">`tag`</span><span class="pun">`.`</span><span class="typ">`FastPair`</span><span class="pln">` VERBOSE`\
|
||||
</span>
|
||||
|
||||
<span class="pln"><span style="color: rgb(0,51,102);">**`cmd5:`**` `</span></span>`adb shell device_config set_sync_disabled_for_tests persistent `
|
||||
|
||||
<span class="pln"><span style="color: rgb(0,51,102);">**`cmd6:`**` `</span></span>`adb shell device_config put bluetooth INIT_logging_debug_enabled_for_all true`
|
||||
|
||||
<span class="pln"><span style="color: rgb(0,51,102);">**`cmd7:`**` `</span></span>`adb shell device_config put bluetooth INIT_default_log_level_str LOG_VERBOSE`
|
||||
|
||||
cmd8: adb logcat \> FILENAME.log
|
||||
|
||||
**3.3.开始复现问题**
|
||||
|
||||
\
|
||||
<span style="color: rgb(0,51,102);">**3.4.问题复现之后,**</span>
|
||||
|
||||
Terminate the logcat by “Ctrl + C”
|
||||
|
||||
<span style="color: rgb(0,51,102);"> **adb输入：** </span><span style="color: rgb(0,51,102);">**`adb bugreport 获取log信息`**</span>\
|
||||
|
||||
<span style="color: rgb(0,51,102);">**`请提供bugreport-XXX.zip 文件 和 FILENAME.log文件`**</span>
|
||||
|
||||
\
|
||||
|
||||
\
|
||||
70
1+Initialize+fast+pair+service+failed.md
Normal file
70
1+Initialize+fast+pair+service+failed.md
Normal file
@@ -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 <a href="https://issuetracker.google.com/issues/444061781#comment7" class="external-link" rel="nofollow" style="text-decoration: none;">Comment #7</a>, 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 <a href="https://issuetracker.google.com/issues/409388435#comment6" class="external-link" rel="nofollow" style="text-decoration: none;">b/409388435#comment6</a>.
|
||||
|
||||
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.
|
||||
|
||||
\
|
||||
|
||||
<span style="color: rgb(255,0,0);">**最终找到原因是因为QC实验室的Google网络开了防火墙：**</span>
|
||||
|
||||
|
||||
|
||||
\
|
||||
|
||||
\
|
||||
|
||||
**<span style="color: rgb(255,0,0);">对比试验，测试过程中遇到该问题后，</span>**
|
||||
|
||||
**<span style="color: rgb(255,0,0);">在google-》所有服务-》设备中关闭自动保存设备选项后，大概率可以测试通过， </span>**
|
||||
|
||||
**<span style="color: rgb(255,0,0);">Fast pair validator 测试的时候可以关掉， 但是手动测试必须打开</span>**
|
||||
|
||||
\
|
||||
|
||||
\
|
||||
|
||||
|
||||
|
||||
<a href="https://partnerissuetracker.corp.google.com/u/0/issues/444061781" class="external-link" rel="nofollow">https://partnerissuetracker.corp.google.com/u/0/issues/444061781</a>
|
||||
|
||||
\
|
||||
|
||||
\
|
||||
|
||||
|
||||
|
||||
\
|
||||
|
||||
|
||||
|
||||
\
|
||||
|
||||
\
|
||||
|
||||
\
|
||||
|
||||
|
||||
|
||||
\
|
||||
@@ -0,0 +1,79 @@
|
||||
# 1 Pairing process error, Reason: Not receive UUID, Is connected:false
|
||||
|
||||
<span style="color: rgb(23,43,77);">目前遇到以下两个原因，可以逐一排查：</span>
|
||||
|
||||
<span style="color: rgb(23,43,77);"></span><style type="text/css">/**/
|
||||
div.rbtoc1777702534829 {padding: 0px;}
|
||||
div.rbtoc1777702534829 ul {margin-left: 0px;}
|
||||
div.rbtoc1777702534829 li {margin-left: 0px;padding-left: 0px;}
|
||||
|
||||
/**/</style>
|
||||
|
||||
<div class="toc-macro rbtoc1777702534829">
|
||||
|
||||
- [原因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.)
|
||||
|
||||
</div>
|
||||
|
||||
#### 原因1：可能是手机系统蓝牙出了问题，setting界面 system\>reset options\>reset Bluetooth & wifi , 然后重启手机试试看
|
||||
|
||||
<span style="color: rgb(23,43,77);"></span>
|
||||
|
||||
\
|
||||
|
||||
#### 原因2：如果设备端不支援LEA，和支援LEA的手机对测，发现手机不连legacy profile， 需要打开 legacy CTKD LE 的功能
|
||||
|
||||
<a href="https://wiki.realtek.com/pages/viewpage.action?pageId=908249385" rel="nofollow">1 GFPS legacy pair 搭配支援LEA手机不连 legacy profile(A2DP/HFP) - BT_Market - WIKI</a>
|
||||
|
||||
#### 原因3： 如果设备端支援LEA，和不支援LEA的手机对测，发现手机不连legacy profile， 需要关闭 legacy CTKD LE 的功能，这个是Google的bug，google 后续会给出修正
|
||||
|
||||
<a href="https://wiki.realtek.com/pages/viewpage.action?pageId=821520803" rel="nofollow">4 pixel6(android 12) 不连A2DP - BT_Market - WIKI</a>
|
||||
|
||||
\
|
||||
|
||||
\
|
||||
|
||||
<span style="color: rgb(23,43,77);"><a href="https://partnerissuetracker.corp.google.com/u/0/issues/443202640" class="external-link" rel="nofollow">https://partnerissuetracker.corp.google.com/u/0/issues/443202640</a></span>
|
||||
|
||||
<span style="color: rgb(23,43,77);"><a href="https://partnerissuetracker.corp.google.com/u/0/issues/445592517" class="external-link" rel="nofollow">https://partnerissuetracker.corp.google.com/u/0/issues/445592517</a></span>
|
||||
|
||||
<span style="color: rgb(23,43,77);"></span>
|
||||
|
||||
\
|
||||
|
||||
<span style="color: rgb(23,43,77);">手机没有来连legacy profile：</span>
|
||||
|
||||
<span style="color: rgb(23,43,77);">Line 32281: 0002123 09-05#11:00:37.169 194 0009843.085 </span><span class="error" style="color: rgb(23,43,77);">\[APP\]</span><span style="color: rgb(23,43,77);"> !\*\*connected: b2s, bd_addr 88::54::1F::10::0C::5F, profs 0x00000000</span>\
|
||||
<span style="color: rgb(23,43,77);">Line 34379: 0004221 09-05#11:00:38.529 169 0011221.541 </span><span class="error" style="color: rgb(23,43,77);">\[ENGAGE\]</span><span style="color: rgb(23,43,77);"> connected: b2s, bd_addr 88::54::1F::10::0C::5F, profs 0x00000000</span>\
|
||||
<span style="color: rgb(23,43,77);">Line 34741: 0004583 09-05#11:00:38.607 203 0011285.575 </span><span class="error" style="color: rgb(23,43,77);">\[ENGAGE\]</span><span style="color: rgb(23,43,77);"> connected: b2s, bd_addr 88::54::1F::10::0C::5F, profs 0x00000000</span>\
|
||||
<span style="color: rgb(23,43,77);">Line 35042: 0004883 09-05#11:00:38.700 095 0011358.903 </span><span class="error" style="color: rgb(23,43,77);">\[ENGAGE\]</span><span style="color: rgb(23,43,77);"> connected: b2s, bd_addr 88::54::1F::10::0C::5F, profs 0x00000000</span>
|
||||
|
||||
\
|
||||
|
||||
<a href="https://jira.realtek.com/browse/BB2BUG-52175" class="external-link" rel="nofollow">[BB2BUG-52175] [BB2][D-CUT][8763EKH][Harman][T530][v3.13.2.20+Test bin] Fast pair Validator APP测试，Personalized Name Update Test Fail - Jira</a>
|
||||
|
||||
<a href="https://jira.realtek.com/browse/BB2BUG-52173" class="external-link" rel="nofollow">[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</a>
|
||||
|
||||
<a href="https://jira.realtek.com/browse/BB2BUG-52194" class="external-link" rel="nofollow">[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</a>
|
||||
|
||||
\
|
||||
|
||||
#### 原因4：测试账号连的设备太多了，需要定期清除
|
||||
|
||||
##### 4.1 setting界面清掉所有的配对信息 <a href="https://wiki.realtek.com/pages/viewpage.action?pageId=401291585" rel="nofollow">1 gfps/finder 如何清除配对信息 - BT_Market - WIKI</a>
|
||||
|
||||
##### <span style="color: rgb(0,0,0);">**4.2 Go to `Settings > Google > All services > Devices > Saved devices：`**</span>
|
||||
|
||||
###### <span style="color: rgb(0,0,0);">** 4.2.1 Toggle off `Automatically saved devices`**</span>
|
||||
|
||||
###### <span style="color: rgb(0,0,0);">** 4.2.2 Wait for about 3 hours, toggling on again.**</span>
|
||||
|
||||
###### <span style="color: rgb(0,0,0);">** 4.2.3 Try to do the test again and see if this issue still happens.**</span>
|
||||
60
1+Pairing+process+error_+Reason_+Is+connected+false.md
Normal file
60
1+Pairing+process+error_+Reason_+Is+connected+false.md
Normal file
@@ -0,0 +1,60 @@
|
||||
# 1 Pairing process error: Reason: Is connected false
|
||||
|
||||
<span style="color: rgb(23,43,77);">目前遇到以下两个原因，可以逐一排查：</span>
|
||||
|
||||
<span style="color: rgb(23,43,77);"></span><style type="text/css">/**/
|
||||
div.rbtoc1777702541807 {padding: 0px;}
|
||||
div.rbtoc1777702541807 ul {margin-left: 0px;}
|
||||
div.rbtoc1777702541807 li {margin-left: 0px;padding-left: 0px;}
|
||||
|
||||
/**/</style>
|
||||
|
||||
<div class="toc-macro rbtoc1777702541807">
|
||||
|
||||
- [原因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.)
|
||||
|
||||
</div>
|
||||
|
||||
#### 原因1：可能是手机系统蓝牙出了问题，setting界面 system\>reset options\>reset Bluetooth & wifi , 然后重启手机试试看
|
||||
|
||||
<span style="color: rgb(23,43,77);"></span>
|
||||
|
||||
\
|
||||
|
||||
#### 原因2：如果设备端不支援LEA，和支援LEA的手机对测，发现手机不连legacy profile， 需要打开 legacy CTKD LE 的功能
|
||||
|
||||
<a href="https://wiki.realtek.com/pages/viewpage.action?pageId=908249385" rel="nofollow">1 GFPS legacy pair 搭配支援LEA手机不连 legacy profile(A2DP/HFP) - BT_Market - WIKI</a>
|
||||
|
||||
\
|
||||
|
||||
|
||||
|
||||
\
|
||||
|
||||
#### 原因3： 如果设备端支援LEA，和不支援LEA的手机对测，发现手机不连legacy profile， 需要关闭 legacy CTKD LE 的功能，这个是Google的bug，google 后续会给出修正
|
||||
|
||||
<a href="https://wiki.realtek.com/pages/viewpage.action?pageId=821520803" rel="nofollow">4 pixel6(android 12) 不连A2DP - BT_Market - WIKI</a>
|
||||
|
||||
\
|
||||
|
||||
#### 原因4：测试账号连的设备太多了，需要定期清除
|
||||
|
||||
##### 4.1 setting界面清掉所有的配对信息 <a href="https://wiki.realtek.com/pages/viewpage.action?pageId=401291585" rel="nofollow">1 gfps/finder 如何清除配对信息 - BT_Market - WIKI</a>
|
||||
|
||||
##### <span style="color: rgb(0,0,0);">**4.2 Go to `Settings > Google > All services > Devices > Saved devices：`**</span>
|
||||
|
||||
###### <span style="color: rgb(0,0,0);">** 4.2.1 Toggle off `Automatically saved devices`**</span>
|
||||
|
||||
###### <span style="color: rgb(0,0,0);">** 4.2.2 Wait for about 3 hours, toggling on again.**</span>
|
||||
|
||||
###### <span style="color: rgb(0,0,0);">** 4.2.3 Try to do the test again and see if this issue still happens.**</span>
|
||||
|
||||
\
|
||||
85
1+Reason_+could+not+connected.md
Normal file
85
1+Reason_+could+not+connected.md
Normal file
@@ -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
|
||||
|
||||
<a href="/download/attachments/354615356/COM3_btsnoop_2023-03-28_14-17-41.cfa?version=1&modificationDate=1679986972847&api=v2" data-linked-resource-container-id="354615356" data-linked-resource-container-version="6" data-linked-resource-content-type="application/octet-stream" data-linked-resource-default-alias="COM3_btsnoop_2023-03-28_14-17-41.cfa" data-linked-resource-id="354616339" data-linked-resource-type="attachment" data-linked-resource-version="1">COM3_btsnoop_2023-03-28_14-17-41.cfa</a>
|
||||
|
||||
<a href="/download/attachments/354615356/COM3_2023-03-28_14-17-31.log?version=1&modificationDate=1679986973150&api=v2" data-linked-resource-container-id="354615356" data-linked-resource-container-version="6" data-linked-resource-content-type="text/plain" data-linked-resource-default-alias="COM3_2023-03-28_14-17-31.log" data-linked-resource-id="354616340" data-linked-resource-type="attachment" data-linked-resource-version="1" data-nice-type="Text File">COM3_2023-03-28_14-17-31.log</a>
|
||||
|
||||
<a href="/download/attachments/354615356/air_log_could_not_connect.btt?version=1&modificationDate=1679987048577&api=v2" data-linked-resource-container-id="354615356" data-linked-resource-container-version="6" data-linked-resource-content-type="application/octet-stream" data-linked-resource-default-alias="air_log_could_not_connect.btt" data-linked-resource-id="354616358" data-linked-resource-type="attachment" data-linked-resource-version="1">air_log_could_not_connect.btt</a>
|
||||
|
||||
<a href="/download/attachments/354615356/bugreport-taimen-RP1A.201005.004.A1-2023-03-28-14-19-27.zip?version=1&modificationDate=1679987190717&api=v2" data-linked-resource-container-id="354615356" data-linked-resource-container-version="6" data-linked-resource-content-type="application/zip" data-linked-resource-default-alias="bugreport-taimen-RP1A.201005.004.A1-2023-03-28-14-19-27.zip" data-linked-resource-id="354616374" data-linked-resource-type="attachment" data-linked-resource-version="1" data-nice-type="Zip Archive">bugreport-taimen-RP1A.201005.004.A1-2023-03-28-14-19-27.zip</a>
|
||||
|
||||
这个问题需要咨询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: <a href="/download/attachments/354615356/validator_realtek_diag.apk?version=1&modificationDate=1680072057193&api=v2" data-linked-resource-container-id="354615356" data-linked-resource-container-version="6" data-linked-resource-content-type="application/octet-stream" data-linked-resource-default-alias="validator_realtek_diag.apk" data-linked-resource-id="354620886" data-linked-resource-type="attachment" data-linked-resource-version="1">validator_realtek_diag.apk</a>
|
||||
|
||||
<a href="/display/~alice_zhou" class="confluence-userlink user-mention" data-base-url="https://wiki.realtek.com" data-linked-resource-id="7897267" data-linked-resource-type="userinfo" data-linked-resource-version="1" data-username="alice_zhou">Alice Zhou(周丽)</a> 麻烦用这个apk压测试试看，是否还能复现到这个问题
|
||||
|
||||
\
|
||||
33
1+gfps_finder+如何清除配对信息.md
Normal file
33
1+gfps_finder+如何清除配对信息.md
Normal file
@@ -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.重启手机
|
||||
|
||||
<span class="jira-issue resolved" jira-key="BEE3PLUSRD-231"> <a href="https://jira.realtek.com/browse/BEE3PLUSRD-231" class="jira-issue-key"><img src="https://jira.realtek.com/secure/viewavatar?size=xsmall&avatarId=10916&avatarType=issuetype" />BEE3PLUSRD-231</a> - <span class="summary">\[Bee3+\]\[GFPS\]initial pairing流程不正确问题</span> <span class="aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf">Closed</span> </span>
|
||||
|
||||
\
|
||||
|
||||
<span style="color: rgb(255,0,0);">**Note：**</span>
|
||||
|
||||
<span style="color: rgb(255,0,0);">测试手机归还QC之前务必先执行上面的操作，并且setting界面移除测试账号</span>
|
||||
|
||||
\
|
||||
|
||||
\
|
||||
5
1+legacy+CTKD+LE+功能打开之后+provision+fail.md
Normal file
5
1+legacy+CTKD+LE+功能打开之后+provision+fail.md
Normal file
@@ -0,0 +1,5 @@
|
||||
# 1 legacy CTKD LE 功能打开之后 provision fail
|
||||
|
||||
<a href="https://jira.realtek.com/browse/BB2BUG-50237" class="external-link" rel="nofollow">[BB2BUG-50237] [BB2][RTL8763ESH/ROM][GMI][沃莱特][Harman][T530] [finder] 738：[Finder]Headphones cannot be added to the Finder APP - Jira</a>
|
||||
|
||||
|
||||
33
1+mcu+cfg+tool+设置的public+key+其实是没有起作用的，+后面会考虑隐藏起来.md
Normal file
33
1+mcu+cfg+tool+设置的public+key+其实是没有起作用的，+后面会考虑隐藏起来.md
Normal file
@@ -0,0 +1,33 @@
|
||||
# 1 mcu cfg tool 设置的public key 其实是没有起作用的， 后面会考虑隐藏起来
|
||||
|
||||
GFPS 加解密过程中， public key是手机端提供的， 每次配对 手机端提供的public key好像都是不一样的
|
||||
|
||||
private key是我们mcu cfg tool里面设置的，每次配对private key是一样的
|
||||
|
||||
<table class="confluenceTable">
|
||||
<tbody>
|
||||
<tr>
|
||||
<th class="confluenceTh" scope="col"><p>//第一次配对</p>
|
||||
<p>[APP] !**gfps_gen_aes_key:<span style="color: rgb(255,0,0);">public key F3 C9 0F CB</span> 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,</p>
|
||||
<p> <span style="color: rgb(51,153,102);"> private key 69 02 DC F8</span> 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</p>
|
||||
<p>//第二次配对 </p>
|
||||
<p>[APP] !**gfps_gen_aes_key:<span style="color: rgb(255,0,0);">public key 78 6F 6D AE</span> 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,</p>
|
||||
<p> 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</p>
|
||||
<p>//第三次配对 </p>
|
||||
<p>[APP] !**gfps_gen_aes_key:<span style="color: rgb(255,0,0);">public key C1 44 1F 26</span> 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,</p>
|
||||
<p> <span style="color: rgb(51,153,102);">private key 69 02 DC F8</span> 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</p>
|
||||
<p>//第四次配对 </p>
|
||||
<p>[APP] !**gfps_gen_aes_key:<span style="color: rgb(255,0,0);">public key B4 8D B2 CD</span> 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,</p>
|
||||
<p> <span style="color: rgb(51,153,102);">private key 69 02 DC F8</span> 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<br />
|
||||
</p>
|
||||
<p>//第五次配对 </p>
|
||||
<p>[APP] !**gfps_gen_aes_key:<span style="color: rgb(255,0,0);">public key 5B E7 FA B5 </span>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,</p>
|
||||
<p> <span style="color: rgb(51,153,102);">private key 69 02 DC F8</span> 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</p>
|
||||
<p><br />
|
||||
</p>
|
||||
<p>//第六次配对 </p>
|
||||
<p>[APP] !**gfps_gen_aes_key:<span style="color: rgb(255,0,0);">public key 1F 6D EB 32</span> 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,</p>
|
||||
<p> <span style="color: rgb(51,153,102);">private key 69 02 DC F8</span> 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</p></th>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
109
1+客户使用GFPS流程.md
Normal file
109
1+客户使用GFPS流程.md
Normal file
@@ -0,0 +1,109 @@
|
||||
# 1 客户使用GFPS流程
|
||||
|
||||
1\. 客户需要阅读GFPS spec 了解GFPS是什么以及有哪些features
|
||||
|
||||
<a href="https://developers.google.com/nearby/fast-pair/landing-page" class="external-link" rel="nofollow">The Google Fast Pair Service | Google for Developers</a>
|
||||
|
||||
<a href="https://developers.google.com/nearby/fast-pair/specifications/introduction" class="external-link" rel="nofollow">https://developers.google.com/nearby/fast-pair/specifications/introduction</a>
|
||||
|
||||
<a href="https://developers.google.com/nearby/fast-pair/landing-page-find-hub" class="external-link" rel="nofollow">Partner Integration Guide for Google's Find Hub Network | Fast Pair | Google for Developers</a>
|
||||
|
||||
<a href="https://developers.google.com/nearby/fast-pair/specifications/extensions/fmdn" class="external-link" rel="nofollow">Find Hub Network Accessory Specification | Fast Pair | Google for Developers</a>
|
||||
|
||||
有關於 GFPS 的認證流程請參照: (此流程是 RTK協助客戶 註冊 Google project kickoff 以及 認證流程介紹)
|
||||
|
||||
<table class="wrapped confluenceTable">
|
||||
<tbody>
|
||||
<tr>
|
||||
<th class="confluenceTh" scope="col">Date </th>
|
||||
<th class="confluenceTh" scope="col">File</th>
|
||||
<th class="confluenceTh" scope="col"><br />
|
||||
</th>
|
||||
</tr>
|
||||
<tr>
|
||||
<td class="confluenceTd">25/11/24</td>
|
||||
<td class="confluenceTd"><div class="content-wrapper">
|
||||
<p><a href="/download/attachments/516624277/2025Q4_BT_GFPS_CertificationFlow_251124.pptx?version=1&modificationDate=1765419979560&api=v2" data-linked-resource-container-id="516624277" data-linked-resource-container-version="25" data-linked-resource-content-type="application/vnd.openxmlformats-officedocument.presentationml.presentation" data-linked-resource-default-alias="2025Q4_BT_GFPS_CertificationFlow_251124.pptx" data-linked-resource-id="1014596282" data-linked-resource-type="attachment" data-linked-resource-version="1" data-nice-type="PowerPoint Presentation">2025Q4_BT_GFPS_CertificationFlow_251124.pptx</a> </p>
|
||||
<p><a href="/download/attachments/516624277/2025Q4_BT_GFPS_CertificationFlow_251124.pdf?version=1&modificationDate=1765419978843&api=v2" data-linked-resource-container-id="516624277" data-linked-resource-container-version="25" data-linked-resource-content-type="application/pdf" data-linked-resource-default-alias="2025Q4_BT_GFPS_CertificationFlow_251124.pdf" data-linked-resource-id="1014596281" data-linked-resource-type="attachment" data-linked-resource-version="1" data-nice-type="PDF Document">2025Q4_BT_GFPS_CertificationFlow_251124.pdf</a></p>
|
||||
</div></td>
|
||||
<td class="confluenceTd"><br />
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td class="confluenceTd">25/12/18</td>
|
||||
<td class="confluenceTd"><div class="content-wrapper">
|
||||
<p><a href="/download/attachments/516624277/2025Q4_BT_GFPS_CertificationFlow_251218.pptx?version=1&modificationDate=1766041229793&api=v2" data-linked-resource-container-id="516624277" data-linked-resource-container-version="25" data-linked-resource-content-type="application/vnd.openxmlformats-officedocument.presentationml.presentation" data-linked-resource-default-alias="2025Q4_BT_GFPS_CertificationFlow_251218.pptx" data-linked-resource-id="1018139986" data-linked-resource-type="attachment" data-linked-resource-version="1" data-nice-type="PowerPoint Presentation">2025Q4_BT_GFPS_CertificationFlow_251218.pptx</a></p>
|
||||
</div></td>
|
||||
<td class="confluenceTd"><br />
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
\
|
||||
|
||||
\
|
||||
|
||||
2\. 客户至少要注册三个google账号 <a href="mailto:xxx@gmail.com" class="external-link" rel="nofollow">xxx_test_account1@gmail.com</a>，<a href="mailto:xxx@gmail.com" class="external-link" rel="nofollow">xxx_test_account2@gmail.com</a>, <a href="mailto:xxx@gmail.com" class="external-link" rel="nofollow">xxx_test_account3@gmail.com</a>, 如果是le only设备并且只需要find hub功能，可以只注册一个Google账号。
|
||||
|
||||
另外建议客户注册一个专门的临时测试账号提供给Realtek qc 内部测试用，比如 <a href="mailto:xxx_customer_for_realtek_test@gmail.com" class="external-link" rel="nofollow">xxx_customer_for_realtek_test@gmail.com</a> 并且要在这个测试账号下注册一个临时的测试model id,
|
||||
|
||||
Realtek QC 会帮忙用这个临时测试账号和这个临时测试账号下的model id过完整的GFPS 认证相关的测项
|
||||
|
||||
\
|
||||
|
||||
3\. 客户需要自己注册model id <a href="https://developers.google.com/nearby/devices/" class="external-link" rel="nofollow">https://developers.google.com/nearby/devices/</a>, 注意model id是和Google账号绑定的。如果客户不清楚怎么注册，FAE可以参考这个wiki 协助客户注册 <a href="https://wiki.realtek.com/pages/viewpage.action?pageId=157379126" rel="nofollow">model_id 注册 - BT_Market - WIKI</a>
|
||||
|
||||
\
|
||||
|
||||
4\. 客户需要将注册的model id 信息提供给 Realtek FAE， FAE需要请 YT(<span class="ui-provider ed bvb bmm bvc bvd bve bvf bvg bvh bvi bvj bvk bvl bvm bvn bvo bvp bvq bvr bvs bvt bvu bvv bvw bvx bvy bvz bwa bwb bwc bwd bwe bwf bwg bwh">YingTsung (YT) Lin</span>) 让google帮忙激活该model id 并且开案, 具体开案需要提供哪些信息，请咨询YT(<span class="ui-provider ed bvb bmm bvc bvd bve bvf bvg bvh bvi bvj bvk bvl bvm bvn bvo bvp bvq bvr bvs bvt bvu bvv bvw bvx bvy bvz bwa bwb bwc bwd bwe bwf bwg bwh">YingTsung (YT) Lin</span>) .
|
||||
|
||||
另外客户需要将所有注册的Google账号提供给 Realtek FAE， Realtek FAE需要请YT(<span class="ui-provider ed bvb bmm bvc bvd bve bvf bvg bvh bvi bvj bvk bvl bvm bvn bvo bvp bvq bvr bvs bvt bvu bvv bvw bvx bvy bvz bwa bwb bwc bwd bwe bwf bwg bwh">YingTsung (YT) Lin</span>)联系Google， 让Google把客户的Google账号加入到Google GFPS/Finder/SASS 的 Test group
|
||||
|
||||
for example：
|
||||
|
||||
<a href="mailto:xxx@gmail.com" class="external-link" rel="nofollow">xxx_test_account1@gmail.com</a>，model id: xxxxxx （这个账号由客户自己管理）
|
||||
|
||||
<a href="mailto:xxx@gmail.com" class="external-link" rel="nofollow">xxx_test_account2@gmail.com</a>, model id: xxxxxx （这个账号由客户自己管理）
|
||||
|
||||
<a href="mailto:xxx@gmail.com" class="external-link" rel="nofollow">xxx_test_account3@gmail.com</a>, model id: xxxxxx （这个账号由客户自己管理）
|
||||
|
||||
<a href="mailto:xxx_customer_for_realtek_test@gmail.com" class="external-link" rel="nofollow">xxx_customer_for_realtek_test@gmail.com</a>, model id: xxxxxx（这个是客户注册的临时测试账号给Realtek QC内部测试用，请FAE提醒客户不要暴露私有信息, 产品量产之后，客户可以将这个账号注销）
|
||||
|
||||
\
|
||||
|
||||
5\. google 开案成功之后，YT(<span class="ui-provider ed bvb bmm bvc bvd bve bvf bvg bvh bvi bvj bvk bvl bvm bvn bvo bvp bvq bvr bvs bvt bvu bvv bvw bvx bvy bvz bwa bwb bwc bwd bwe bwf bwg bwh">YingTsung (YT) Lin</span>) 会通知Realtek FAE，Realtek FAE 通知客户可以使用注册的model id信息了
|
||||
|
||||
\
|
||||
|
||||
6\. Realtek FAE协助客户在mcu cfg tool 里面配置GFPS相关信息 [mcu cfg tool中 GFPS 各配置项的含义](/pages/viewpage.action?pageId=158870786)
|
||||
|
||||
\
|
||||
|
||||
7\. 请客户参考 <a href="https://developers.google.com/nearby/fast-pair/certification-process" class="external-link" rel="nofollow">https://developers.google.com/nearby/fast-pair/certification-process</a>熟悉GFPS认证流程
|
||||
|
||||
Device Feature Requirements 请参考以下文档：
|
||||
|
||||
Hearable devcie 请参考：<a href="https://developers.google.com/nearby/fast-pair/specifications/devicefeaturerequirement/devicefeaturerequirement_hearables" class="external-link" rel="nofollow"> Fast Pair | Google for Developers</a>
|
||||
|
||||
Locator tags 请参考：<a href="https://developers.google.com/nearby/fast-pair/specifications/devicefeaturerequirement/devicefeaturerequirement_locatortags" class="external-link" rel="nofollow">Fast Pair | Google for Developers</a>
|
||||
|
||||
\
|
||||
|
||||
8\. 请客户参考GFPS认证spec 进行测试:
|
||||
|
||||
GFPS认证请参考：<a href="https://developers.google.com/nearby/fast-pair/fast-pair-certification-guideline" class="external-link" rel="nofollow">https://developers.google.com/nearby/fast-pair/fast-pair-certification-guideline</a>，
|
||||
|
||||
SASS认证请参考：<a href="https://developers.google.com/nearby/fast-pair/audio-switch-certification-guideline" class="external-link" rel="nofollow">Audio Switch Certification Guidelines | Fast Pair | Google for Developers</a>
|
||||
|
||||
Finder/Find Hub认证请参考：<a href="https://developers.google.com/nearby/fast-pair/early-access/fmdn-certification-guideline" class="external-link" rel="nofollow">Find Hub Network Certification Guidelines | Fast Pair | Google for Developers</a>
|
||||
|
||||
\
|
||||
|
||||
9\. 请Realtek FAE指导客户参考这个wiki 进行测试： <a href="https://wiki.realtek.com/display/BTMKT/1+GFPS+Test+flow" rel="nofollow">1 GFPS Test flow - BT_Market - WIKI</a>
|
||||
|
||||
\
|
||||
|
||||
10\. 客户端所有的测试都PASS之后，需要过GFPS相关认证之前， 客户需要提交测试结果(即self test report)给 Realtek FAE， Realtek FAE 找 YT(<span class="ui-provider ed bvb bmm bvc bvd bve bvf bvg bvh bvi bvj bvk bvl bvm bvn bvo bvp bvq bvr bvs bvt bvu bvv bvw bvx bvy bvz bwa bwb bwc bwd bwe bwf bwg bwh">YingTsung (YT) Lin</span>) 讨论认证相关信息
|
||||
|
||||
\
|
||||
9
1+手机端显示+“Could+not+authenticate”.md
Normal file
9
1+手机端显示+“Could+not+authenticate”.md
Normal file
@@ -0,0 +1,9 @@
|
||||
# 1 手机端显示 “Could not authenticate”
|
||||
|
||||
|
||||
|
||||
手机端setting 界面删掉配对信息，之后耳机端也要做factory reset 不然finder功能用不起来。
|
||||
|
||||
每个测项测试之前手机端都会先清掉配对信息，所以每个测项测试之前耳机端都要主动做factory reset
|
||||
|
||||
[8 手机端清掉配对信息之后，耳机端也要做factory reset，不然finder功能用不起来](/pages/viewpage.action?pageId=350190807)
|
||||
25
1+认证实验室要求认证期间弹窗的图片和名字需要隐藏.md
Normal file
25
1+认证实验室要求认证期间弹窗的图片和名字需要隐藏.md
Normal file
@@ -0,0 +1,25 @@
|
||||
# 1 认证实验室要求认证期间弹窗的图片和名字需要隐藏
|
||||
|
||||
<a href="https://jira.realtek.com/browse/BB2BUG-53293" class="external-link" rel="nofollow">[BB2BUG-53293] [BB2][RTL8763ESE][Amazon/OSM][头戴立体声耳机][OSHA-67]Pegatron GFPS认证实验室反馈认证期间弹窗的图片和名字需要隐藏 - Jira</a>
|
||||
|
||||
和注册model id的时候填写的 Public Date有关系：
|
||||
|
||||
|
||||
|
||||
\
|
||||
|
||||
\
|
||||
|
||||
如果UI信息和上面描述的不一样，手机可以尝试做以下绿色框里面的操作:
|
||||
|
||||
|
||||
|
||||
\
|
||||
|
||||
<span style="color: rgb(255,0,0);">需要注意的是如果model id的Approval状态是 DRAFT, 在拿到认证之前需要开启debug mode：</span>
|
||||
|
||||
<span style="color: rgb(255,0,0);"></span>
|
||||
|
||||
|
||||
|
||||
\
|
||||
9
1-+SUT+A打开蓝牙关闭飞行模式后，SUT+B依然能搜索到设备.md
Normal file
9
1-+SUT+A打开蓝牙关闭飞行模式后，SUT+B依然能搜索到设备.md
Normal file
@@ -0,0 +1,9 @@
|
||||
# 1- SUT A打开蓝牙关闭飞行模式后，SUT B依然能搜索到设备
|
||||
|
||||
<a href="https://jira.realtek.com/browse/BB2BUG-47667" class="external-link" rel="nofollow">[BB2BUG-47667] [BB2][RTL8763ESH/ROM][GMI][沃莱特][Harman][T135]Finder测试，SUT A中耳机打开Activate Unwanted Tracking mode，SUT B搜索到设备，SUT A打开蓝牙关闭飞行模式后，SUT B依然能搜索到设备 - Jira</a>
|
||||
|
||||
SUT A是owner phone
|
||||
|
||||
SUT B是non owner phone
|
||||
|
||||
|
||||
32
1.+Google+test+group.md
Normal file
32
1.+Google+test+group.md
Normal file
@@ -0,0 +1,32 @@
|
||||
# 1. Google test group
|
||||
|
||||
客户需要关注的是以下红色框里面的test group：
|
||||
|
||||
|
||||
|
||||
\
|
||||
|
||||
\
|
||||
|
||||
\
|
||||
|
||||
Realtek全部test group 如下：
|
||||
|
||||
|
||||
|
||||
\
|
||||
Fast Pair **launched** feature --\> should join the <span style="color: rgb(244,67,54);">FastPairPartnerTest</span> group\
|
||||
Fast Pair **un-released** feature --\> should join the <span style="color: rgb(255,193,7);">Fast Pair external group</span>
|
||||
|
||||
Tony.YS Liu,\
|
||||
|
||||
looks like there is a typo, correction is:\
|
||||
Fast Pair **un-launched** feature --\> should join the <span style="color: rgb(255,193,7);">Fast Pair external group</span><span style="color: rgb(255,193,7);">\
|
||||
</span>So, for your customer and production users, they don't need to join <span style="color: rgb(255,193,7);">Fast Pair external group</span> 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!
|
||||
|
||||
\
|
||||
7
1.+initial+pair+一直显示connecting.md
Normal file
7
1.+initial+pair+一直显示connecting.md
Normal file
@@ -0,0 +1,7 @@
|
||||
# 1. initial pair 一直显示connecting
|
||||
|
||||
可能是Google 账号的问题， 可以尝试换个账号再试试看 realsilbt8888的账号没办法用来做手动测试
|
||||
|
||||
|
||||
|
||||
\
|
||||
11
1.+如何从手机+setting+界面判断+LEA_A2DP_HFP有connected.md
Normal file
11
1.+如何从手机+setting+界面判断+LEA_A2DP_HFP有connected.md
Normal file
@@ -0,0 +1,11 @@
|
||||
# 1. 如何从手机 setting 界面判断 LEA/A2DP/HFP有connected
|
||||
|
||||
<span style="color: rgb(32,33,36);">from google:</span>
|
||||
|
||||
<span style="color: rgb(32,33,36);">The LEA connected in the Settings UI when this "LE Audio" toggle on .</span>
|
||||
|
||||
<span style="color: rgb(32,33,36);"></span>
|
||||
|
||||
<span style="color: rgb(32,33,36);">if you turn off the "LE Audio" toggle off. you will see the options for A2DP/HFP , that means it connected to A2DP/HFP.</span>
|
||||
|
||||
<span style="color: rgb(32,33,36);"></span>
|
||||
73
1.+手机端点击+ring+stop，耳机端并未停止响铃.md
Normal file
73
1.+手机端点击+ring+stop，耳机端并未停止响铃.md
Normal file
@@ -0,0 +1,73 @@
|
||||
# 1. 手机端点击 ring stop，耳机端并未停止响铃
|
||||
|
||||
<span class="jira-issue" jira-key="BB2BUG-18476"> <a href="https://jira.realtek.com/browse/BB2BUG-18476" class="jira-issue-key"><img src="https://jira.realtek.com/secure/viewavatar?size=xsmall&avatarId=10916&avatarType=issuetype" />BB2BUG-18476</a> - <span class="summary">\[BB2\]\[8773ESL\]\[v3.13.0.7\]\[GFPS\]\[LE Audio\]Find device响铃时，有时候停止响铃失败</span> <span class="aui-lozenge aui-lozenge-subtle aui-lozenge-current jira-macro-single-issue-export-pdf">In Progress</span> </span>
|
||||
|
||||
<span style="color: rgb(32,33,36);">手机端点击 ring stop，耳机端并未停止响铃</span>
|
||||
|
||||
<span style="color: rgb(32,33,36);">原因是：</span>
|
||||
|
||||
<span style="color: rgb(32,33,36);">手机端有尝试发送停止响铃的cmd 给耳机端，</span>
|
||||
|
||||
但是因为我们耳机端没有发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 <span class="error">\[CONTEXT service_id=265 \]</span>
|
||||
|
||||
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.
|
||||
|
||||
<span style="color: rgb(23,43,77);">LE L2cap channel is not disconnected in the log. </span>
|
||||
|
||||
<span style="color: rgb(23,43,77);">Can you help to see why the PSM cannot be found? thanks</span>
|
||||
|
||||
\
|
||||
|
||||
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: <a href="https://issuetracker.google.com/issues/158958522#comment12" class="external-link" rel="nofollow">b/158958522#comment12</a>) when we worked with realtek on ringing through RFCOMM.
|
||||
|
||||
From <span class="nobr"><a href="mailto:wade_li@realsil.com.cn" class="external-link" rel="nofollow">wade_li@realsil.com.cn<sup><img src="images/1.+手机端点击+ring+stop，耳机端并未停止响铃_1f96683b.gif" /></sup></a></span> 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!
|
||||
|
||||
\
|
||||
|
||||
<span style="color: rgb(32,33,36);">hi tony:</span>\
|
||||
<span style="color: rgb(32,33,36);">The reason is Provider do not send credit to seeker, we have already fix this issue and test sucess.</span>\
|
||||
\
|
||||
<span style="color: rgb(32,33,36);">we have another problem：some times seeker do not create LE L2CAP channel, I will create another jira, thanks</span>
|
||||
|
||||
\
|
||||
|
||||
\
|
||||
43
1.1+Project+工程enable对应功能.md
Normal file
43
1.1+Project+工程enable对应功能.md
Normal file
@@ -0,0 +1,43 @@
|
||||
# 1.1 Project 工程enable对应功能
|
||||
|
||||
<span style="color: rgb(166,38,164);">app_flags.h 里面找到 <span style="color: rgb(64,120,242);">CONFIG_REALTEK_GFPS_XXX 相关的宏并按照以下信息配置</span>：</span>
|
||||
|
||||
<span style="color: rgb(166,38,164);">\#define</span><span style="color: rgb(56,58,66);"> </span><span style="color: rgb(64,120,242);">CONFIG_REALTEK_GFPS_FEATURE_SUPPORT</span><span style="color: rgb(56,58,66);"> </span><span style="color: rgb(152,104,1);">1</span>\
|
||||
<span style="color: rgb(166,38,164);">\#define</span><span style="color: rgb(56,58,66);"> </span><span style="color: rgb(64,120,242);">CONFIG_REALTEK_GFPS_LE_DEVICE_SUPPORT</span><span style="color: rgb(56,58,66);"> (0 && </span><span style="color: rgb(64,120,242);">CONFIG_REALTEK_GFPS_FEATURE_SUPPORT</span><span style="color: rgb(56,58,66);">)</span>\
|
||||
<span style="color: rgb(166,38,164);">\#define</span><span style="color: rgb(56,58,66);"> </span><span style="color: rgb(64,120,242);">CONFIG_REALTEK_GFPS_SASS_SUPPORT</span><span style="color: rgb(56,58,66);"> (0 && </span><span style="color: rgb(64,120,242);">CONFIG_REALTEK_GFPS_FEATURE_SUPPORT</span><span style="color: rgb(56,58,66);">)</span>\
|
||||
<span style="color: rgb(166,38,164);">\#define</span><span style="color: rgb(56,58,66);"> </span><span style="color: rgb(64,120,242);">CONFIG_REALTEK_GFPS_FINDER_SUPPORT</span><span style="color: rgb(56,58,66);"> (0 && </span><span style="color: rgb(64,120,242);">CONFIG_REALTEK_GFPS_FEATURE_SUPPORT</span><span style="color: rgb(56,58,66);">)</span>
|
||||
|
||||
<span style="color: rgb(56,58,66);">GFPS依赖的其他的模块：</span>
|
||||
|
||||
\#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
|
||||
|
||||
\
|
||||
|
||||
<span style="color: rgb(152,104,1);">Note:</span>
|
||||
|
||||
<span style="color: rgb(152,104,1);">有的IC宏的名字是GFPS_XXX, <span style="color: rgb(166,38,164);">app_flags.h 里面找到 <span style="color: rgb(64,120,242);">GFPS_XXX 相关的宏并按照以下信息配置</span>：</span></span>
|
||||
|
||||
<span style="color: rgb(166,38,164);">\#define</span><span style="color: rgb(56,58,66);"> </span><span style="color: rgb(64,120,242);">GFPS_FEATURE_SUPPORT</span><span style="color: rgb(56,58,66);"> </span><span style="color: rgb(152,104,1);">1</span>\
|
||||
<span style="color: rgb(166,38,164);">\#define</span><span style="color: rgb(56,58,66);"> </span><span style="color: rgb(64,120,242);">GFPS_LE_DEVICE_SUPPORT</span><span style="color: rgb(56,58,66);"> (0 && </span><span style="color: rgb(64,120,242);">GFPS_FEATURE_SUPPORT</span><span style="color: rgb(56,58,66);">)</span>\
|
||||
<span style="color: rgb(166,38,164);">\#define</span><span style="color: rgb(56,58,66);"> </span><span style="color: rgb(64,120,242);">GFPS_SASS_SUPPORT</span><span style="color: rgb(56,58,66);"> (0 && </span><span style="color: rgb(64,120,242);">GFPS_FEATURE_SUPPORT</span><span style="color: rgb(56,58,66);">)</span>\
|
||||
<span style="color: rgb(166,38,164);">\#define</span><span style="color: rgb(56,58,66);"> </span><span style="color: rgb(64,120,242);">GFPS_FINDER_SUPPORT</span><span style="color: rgb(56,58,66);"> (0 && </span><span style="color: rgb(64,120,242);">GFPS_FEATURE_SUPPORT</span><span style="color: rgb(56,58,66);">)</span>
|
||||
|
||||
<span style="color: rgb(56,58,66);">GFPS依赖的其他的模块：</span>
|
||||
|
||||
\#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
|
||||
|
||||
\
|
||||
|
||||
\
|
||||
@@ -1,4 +1 @@
|
||||
# 1.2 测试环境搭建 {#测试环境搭建}
|
||||
|
||||
::: {.Section1}
|
||||
:::
|
||||
# 1.2 测试环境搭建
|
||||
|
||||
144
1.2.1+设备端环境搭建.md
144
1.2.1+设备端环境搭建.md
@@ -1,14 +1,14 @@
|
||||
# 1.2.1 设备端环境搭建 {#设备端环境搭建}
|
||||
# 1.2.1 设备端环境搭建
|
||||
|
||||
:::: {.Section1}
|
||||
`<style type="text/css">/**/
|
||||
div.rbtoc1777598888652 {padding: 0px;}
|
||||
div.rbtoc1777598888652 ul {margin-left: 0px;}
|
||||
div.rbtoc1777598888652 li {margin-left: 0px;padding-left: 0px;}
|
||||
<style type="text/css">/**/
|
||||
div.rbtoc1777701049430 {padding: 0px;}
|
||||
div.rbtoc1777701049430 ul {margin-left: 0px;}
|
||||
div.rbtoc1777701049430 li {margin-left: 0px;padding-left: 0px;}
|
||||
|
||||
/**/</style>`{=html}
|
||||
/**/</style>
|
||||
|
||||
<div class="toc-macro rbtoc1777701049430">
|
||||
|
||||
::: {.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配置}
|
||||
</div>
|
||||
|
||||
#### 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, <span style="letter-spacing: -0.003em;">不勾选 Enable pairing timeout</span>
|
||||
|
||||
修改为了便于GFPS测试，GFPS 测试的时候或者是过认证的时候需要修改， **量产时可以考虑不修改。**
|
||||
<span style="color: rgb(255,0,0);">**Note**:</span>
|
||||
|
||||
|
||||
修改为了便于GFPS测试，GFPS 测试的时候或者是过认证的时候需要修改， **<span style="color: rgb(255,0,0);">量产时可以考虑不修改。</span>**
|
||||
|
||||
#### 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。<span style="color: rgb(255,0,0);">**强制要求必须修改**</span>
|
||||
|
||||
<span style="color: rgb(255,0,0);">**Note**:</span>
|
||||
|
||||
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 <span style="color: rgb(255,0,0);">**强制要求必须修改**</span>
|
||||
|
||||
linkback模式下DUT不应该discoverable，不然手机端会一直弹配对窗口。
|
||||
linkback模式下DUT不应该discoverable，不然手机端会一直弹配对窗口。<span style="color: rgb(255,0,0);"> </span>
|
||||
|
||||
\
|
||||
|
||||
|
||||
|
||||
|
||||
#### 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 <span style="color: rgb(255,0,0);">**强制要求必须修改**</span>
|
||||
|
||||
下面红框里的**不可以勾选 **不然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"}**
|
||||
下面红框里的**<span style="color: rgb(255,0,0);">不可以勾选</span> **<span style="color: rgb(0,0,0);letter-spacing: 0.0px;">不然battery HUN测试可能测不过，</span> **<span class="jira-issue" client-id="SINGLE_2d885edc-676b-3349-9548-fe5648c9d8cd_948641792_2c9082e76519d09101657ff5cfb3003b" jira-key="BBPRO2BUG-21515"> <a href="https://jira.realtek.com/browse/BBPRO2BUG-21515" class="jira-issue-key"><span class="aui-icon aui-icon-wait issue-placeholder"></span>BBPRO2BUG-21515</a> - <span class="summary">Getting issue details...</span> <span class="aui-lozenge aui-lozenge-subtle aui-lozenge-default issue-placeholder">STATUS</span> </span>**
|
||||
|
||||
|
||||
|
||||
|
||||
#### 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参数，详细信息参考 <a href="https://wiki.realtek.com/pages/viewpage.action?pageId=158870786" rel="nofollow">mcu cfg tool中 GFPS 各配置项的含义 - BT_Market - WIKI</a>
|
||||
|
||||
|
||||
|
||||
|
||||
下面是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}
|
||||
<a href="#" class="unresolved">gfps_findme.wav</a>
|
||||
|
||||
自行选择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测试环境搭建(<span style="color: rgb(255,0,0);">只有TWS耳机需要做GFPS battery测试，single mode 不需要测试</span>)
|
||||
|
||||
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匹配的。
|
||||
勾选支持充电盒功能，<span style="color: rgb(255,0,0);">注意如果充电盒image烧录的是20ms,下面红色框中的40ms也要改成20ms,这个要和充电盒image匹配的。</span>
|
||||
|
||||
如果充电盒image 烧录的是40ms：
|
||||
<span style="color: rgb(255,0,0);">如果充电盒image 烧录的是40ms：</span>
|
||||
|
||||
|
||||
|
||||
|
||||
如果充电盒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， <span style="color: rgb(255,0,0);">里面有model id信息，不可以直接开给客户！！！</span>
|
||||
|
||||
[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"}
|
||||
<a href="/download/attachments/139180496/GFPS_Left.rcfg?version=1&modificationDate=1636711808317&api=v2" data-linked-resource-container-id="139180496" data-linked-resource-container-version="20" data-linked-resource-content-type="application/octet-stream" data-linked-resource-default-alias="GFPS_Left.rcfg" data-linked-resource-id="205658521" data-linked-resource-type="attachment" data-linked-resource-version="1">GFPS_Left.rcfg</a>
|
||||
|
||||
[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"}
|
||||
<a href="/download/attachments/139180496/GFPS_Right.rcfg?version=1&modificationDate=1636711808877&api=v2" data-linked-resource-container-id="139180496" data-linked-resource-container-version="20" data-linked-resource-content-type="application/octet-stream" data-linked-resource-default-alias="GFPS_Right.rcfg" data-linked-resource-id="205658522" data-linked-resource-type="attachment" data-linked-resource-version="1">GFPS_Right.rcfg</a>
|
||||
|
||||
\
|
||||
|
||||
\
|
||||
::::
|
||||
|
||||
100
1.2.2+手机端环境搭建.md
100
1.2.2+手机端环境搭建.md
@@ -1,14 +1,14 @@
|
||||
# 1.2.2 手机端环境搭建 {#手机端环境搭建}
|
||||
# 1.2.2 手机端环境搭建
|
||||
|
||||
:::: {.Section1}
|
||||
`<style type="text/css">/**/
|
||||
div.rbtoc1777598900336 {padding: 0px;}
|
||||
div.rbtoc1777598900336 ul {margin-left: 0px;}
|
||||
div.rbtoc1777598900336 li {margin-left: 0px;padding-left: 0px;}
|
||||
<style type="text/css">/**/
|
||||
div.rbtoc1777701055143 {padding: 0px;}
|
||||
div.rbtoc1777701055143 ul {margin-left: 0px;}
|
||||
div.rbtoc1777701055143 li {margin-left: 0px;padding-left: 0px;}
|
||||
|
||||
/**/</style>`{=html}
|
||||
/**/</style>
|
||||
|
||||
<div class="toc-macro rbtoc1777701055143">
|
||||
|
||||
::: {.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）)
|
||||
:::
|
||||
|
||||
</div>
|
||||
|
||||
\
|
||||
|
||||
该测试至少要准备两只手机。测试手机建议使用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手机，<span style="color: rgb(32,33,36);"> Pixel 5+ is recommended. </span>请<span style="color: rgb(255,0,0);">**务必确保**</span>手机端有打开开发者选项 <a href="https://developer.android.com/studio/debug/dev-options?hl=zh-cn" class="external-link" rel="nofollow">https://developer.android.com/studio/debug/dev-options?hl=zh-cn</a>
|
||||
|
||||
\
|
||||
|
||||
#### 1.手机需要连接google网络 {#id-1.2.2手机端环境搭建-1.手机需要连接google网络}
|
||||
#### 1.手机需要连接google网络
|
||||
|
||||
该网络必须可以登陆google的网站，在测试前请先测试一下是否可以登录google的网站(**建议试试能不能打开youtube之类的**）。
|
||||
该网络必须可以登陆google的网站，在测试前请先测试一下是否可以登录google的网站(<span style="color: rgb(255,0,0);">**建议试试能不能打开youtube之类的**</span>）。
|
||||
|
||||
#### 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(<span style="color: rgb(255,0,0);">内部</span><span style="color: rgb(255,0,0);">账号(不可给客户)：</span>
|
||||
|
||||
[[[[[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);"}
|
||||
<span style="color: rgb(255,0,0);"><span style="color: rgb(0,0,0);"><span style="color: rgb(255,0,0);"><span style="color: rgb(23,43,77);"><span style="color: rgb(0,0,0);"><span style="color: rgb(255,0,0);">Fast Pair Validator 测试 请使用 </span></span></span></span></span></span><span style="color: rgb(255,0,0);"><a href="mailto:realsilbt8888@gmail.com" class="external-link" rel="nofollow">realsilbt8888@gmail.com</a><span style="color: rgb(23,43,77);"> </span><span style="color: rgb(23,43,77);"> </span></span>
|
||||
|
||||
[手动测试账号请参考 [[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);"}
|
||||
<span style="color: rgb(255,0,0);"><span style="color: rgb(23,43,77);">手动测试账号请参考 <span style="color: rgb(255,0,0);"><a href="https://wiki.realtek.com/pages/viewpage.action?pageId=394285307" rel="nofollow">Google 账号 - BT_Market - WIKI (realtek.com)</a> </span></span></span>
|
||||
|
||||
#### 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"}
|
||||
<a href="https://developer.android.com/studio/debug/dev-options?hl=zh-cn" class="external-link" rel="nofollow">https://developer.android.com/studio/debug/dev-options?hl=zh-cn</a>
|
||||
|
||||
#### 10.Check Google Play Service version {#id-1.2.2手机端环境搭建-10.CheckGooglePlayServiceversion}
|
||||
#### <span class="devsite-heading">10.Check Google Play Service version</span>
|
||||
|
||||
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）}
|
||||
#### **<span style="color: rgb(255,0,0);">11.注册成为google beta tester（内部测试账号已经注册过了，这一步不需要，如果是客户自己注册的Google账号，需要提醒客户check）</span>**
|
||||
|
||||
[1. Google test group - BT_Market - WIKI](https://wiki.realtek.com/display/BTMKT/1.+Google+test+group){rel="nofollow"}
|
||||
<a href="https://wiki.realtek.com/display/BTMKT/1.+Google+test+group" rel="nofollow">1. Google test group - BT_Market - WIKI</a>
|
||||
|
||||
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 <a href="https://play.google.com/apps/testing/com.google.android.gms" class="external-link" rel="nofollow">https://play.google.com/apps/testing/com.google.android.gms</a>
|
||||
|
||||
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 <a href="https://www.google.com/android/beta" class="external-link" rel="nofollow"><span>https://www.google.com/android/beta</span></a> 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 <a href="https://play.google.com/apps/testing/com.google.android.apps.adm" class="external-link" rel="nofollow">https://play.google.com/apps/testing/com.google.android.apps.adm</a>
|
||||
|
||||
\
|
||||
|
||||
可以登陆Google账号之后在以下链接查看是否有添加成功：[我的群组](https://groups.google.com/my-groups){.external-link rel="nofollow"}
|
||||
可以登陆Google账号之后在以下链接查看是否有添加成功：<a href="https://groups.google.com/my-groups" class="external-link" rel="nofollow">我的群组</a>
|
||||
|
||||
|
||||
|
||||
|
||||
需要注意的是：
|
||||
|
||||
|
||||
|
||||
|
||||
如果没有权限添加，FAE需要联系YingTsung (YT) Lin， 请他发邮件给Google， 让Google把客户注册的Google账号添加到Google的Test group。
|
||||
|
||||
\
|
||||
::::
|
||||
|
||||
@@ -1,14 +1,14 @@
|
||||
# 1.2.3 Fast Pair Validator 环境搭建 {#fast-pair-validator-环境搭建}
|
||||
# 1.2.3 Fast Pair Validator 环境搭建
|
||||
|
||||
:::: {.Section1}
|
||||
`<style type="text/css">/**/
|
||||
div.rbtoc1777598906641 {padding: 0px;}
|
||||
div.rbtoc1777598906641 ul {margin-left: 0px;}
|
||||
div.rbtoc1777598906641 li {margin-left: 0px;padding-left: 0px;}
|
||||
<span style="color: rgb(0,0,0);"></span><style type="text/css">/**/
|
||||
div.rbtoc1777701061253 {padding: 0px;}
|
||||
div.rbtoc1777701061253 ul {margin-left: 0px;}
|
||||
div.rbtoc1777701061253 li {margin-left: 0px;padding-left: 0px;}
|
||||
|
||||
/**/</style>`{=html}
|
||||
/**/</style>
|
||||
|
||||
<div class="toc-macro rbtoc1777701061253">
|
||||
|
||||
::: {.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搭建手机端的测试环境}
|
||||
</div>
|
||||
|
||||
测试手机建议使用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"}
|
||||
### <span style="color: rgb(0,0,0);">1 搭建手机端的测试环境</span>
|
||||
|
||||
测试手机建议使用Google pixel手机，请<span style="color: rgb(255,0,0);">**务必确保**</span>手机端有打开开发者选项 <a href="https://developer.android.com/studio/debug/dev-options?hl=zh-cn" class="external-link" rel="nofollow">https://developer.android.com/studio/debug/dev-options?hl=zh-cn</a>
|
||||
|
||||
\
|
||||
|
||||
#### 1.1 手机需要连接google网络 {#id-1.2.3FastPairValidator环境搭建-1.1手机需要连接google网络}
|
||||
#### 1.1 手机需要连接google网络
|
||||
|
||||
该网络必须可以登陆google的网站，在测试前请先测试一下是否可以登录google的网站(**建议试试能不能打开youtube之类的**）。
|
||||
该网络必须可以登陆google的网站，在测试前请先测试一下是否可以登录google的网站(<span style="color: rgb(255,0,0);">**建议试试能不能打开youtube之类的**</span>）。
|
||||
|
||||
#### 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(<span style="color: rgb(255,0,0);">内部</span><span style="color: rgb(255,0,0);">账号(不可给客户)：</span>
|
||||
|
||||
[[[[[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);"}
|
||||
<span style="color: rgb(255,0,0);"><span style="color: rgb(0,0,0);"><span style="color: rgb(255,0,0);"><span style="color: rgb(23,43,77);"><span style="color: rgb(0,0,0);"><span style="color: rgb(255,0,0);">Fast Pair Validator 测试 请使用 </span></span></span></span></span></span><span style="color: rgb(255,0,0);"><a href="mailto:realsilbt8888@gmail.com" class="external-link" rel="nofollow">realsilbt8888@gmail.com</a><span style="color: rgb(23,43,77);"> </span><span style="color: rgb(23,43,77);"> </span></span>
|
||||
|
||||
[手动测试账号请参考 [[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);"}
|
||||
<span style="color: rgb(255,0,0);"><span style="color: rgb(23,43,77);">手动测试账号请参考 <span style="color: rgb(255,0,0);"><a href="https://wiki.realtek.com/pages/viewpage.action?pageId=394285307" rel="nofollow">Google 账号 - BT_Market - WIKI (realtek.com)</a> </span></span></span>
|
||||
|
||||
#### 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需要打开**
|
||||
**<span style="color: rgb(255,0,0);">Note: 只有realsilbt8888的账号需要关掉 Automatically save devices， 其他手动测试的账号Automatically save devices需要打开</span>**
|
||||
|
||||
|
||||
|
||||
|
||||
#### 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"}
|
||||
<a href="https://developer.android.com/studio/debug/dev-options?hl=zh-cn" class="external-link" rel="nofollow">https://developer.android.com/studio/debug/dev-options?hl=zh-cn</a>
|
||||
|
||||
#### 1.10 Check Google Play Service version {#id-1.2.3FastPairValidator环境搭建-1.10CheckGooglePlayServiceversion}
|
||||
#### <span class="devsite-heading">1.10 Check Google Play Service version</span>
|
||||
|
||||
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）}
|
||||
#### **<span style="color: rgb(255,0,0);">1.11 注册成为google beta tester（内部测试账号已经注册过了，这一步不需要，如果是客户自己注册的Google账号，需要提醒客户check）</span>**
|
||||
|
||||
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 <a href="https://play.google.com/apps/testing/com.google.android.gms" class="external-link" rel="nofollow">https://play.google.com/apps/testing/com.google.android.gms</a>
|
||||
|
||||
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 <a href="https://www.google.com/android/beta" class="external-link" rel="nofollow"><span>https://www.google.com/android/beta</span></a> 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 <a href="https://play.google.com/apps/testing/com.google.android.apps.adm" class="external-link" rel="nofollow">https://play.google.com/apps/testing/com.google.android.apps.adm</a>
|
||||
|
||||
\
|
||||
|
||||
可以登陆Google账号之后在以下链接查看是否有添加成功：[我的群组](https://groups.google.com/my-groups){.external-link rel="nofollow"}
|
||||
可以登陆Google账号之后在以下链接查看是否有添加成功：<a href="https://groups.google.com/my-groups" class="external-link" rel="nofollow">我的群组</a>
|
||||
|
||||
|
||||
|
||||
|
||||
需要注意的是：
|
||||
|
||||
|
||||
|
||||
|
||||
如果没有权限添加，FAE需要联系YingTsung (YT) Lin， 请他发邮件给Google， 让Google把客户注册的Google账号添加到Google的Test group。
|
||||
|
||||
\
|
||||
|
||||
### **2 Fast Pair Validator APP安装** {#id-1.2.3FastPairValidator环境搭建-2FastPairValidatorAPP安装}
|
||||
### **<span style="color: rgb(153,51,0);">2 Fast Pair Validator APP安装</span>**
|
||||
|
||||
确认手机是否安装 Fast Pair Validator APP
|
||||
|
||||
Fast pair validator app 图标如下图：
|
||||
<span style="color: rgb(0,0,0);">Fast pair validator app 图标如下图：</span>
|
||||
|
||||
[]{style="color: rgb(153,51,0);"}
|
||||
<span style="color: rgb(153,51,0);"></span>
|
||||
|
||||
如果没有安装:
|
||||
|
||||
去 Play Store/应用商店 下载 Fast Pair Validator APP并且安装。
|
||||
去 Play Store/应用商店 下载 <span style="color: rgb(0,0,0);">Fast Pair Validator APP并且安装。</span>
|
||||
|
||||
如果已经安装:
|
||||
|
||||
@@ -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中的测项}
|
||||
### <span style="color: rgb(153,51,0);">3 </span><span style="color: rgb(153,51,0);">Enable fast pair validator app中的测项</span>
|
||||
|
||||
#### [3.1 安装adb:]{style="color: rgb(32,33,36);"} {#id-1.2.3FastPairValidator环境搭建-3.1安装adb:}
|
||||
#### <span style="color: rgb(32,33,36);"><span style="color: black;">3.1 安装adb:</span></span>
|
||||
|
||||
[[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);"}
|
||||
<span style="color: rgb(32,33,36);"><span style="color: black;"><a href="https://wiki.realtek.com/pages/viewpage.action?pageId=87464469" rel="nofollow">adb安装及使用方法</a> 该wiki上提供的adb版本太旧，会出现device offline的问题，下载最新的<a href="https://adbshell.com/downloads" class="external-link" rel="nofollow">https://adbshell.com/downloads</a></span></span>
|
||||
|
||||
安装adb之后找到adb.exe所在的目录，在该目录下打开cmd命令行
|
||||
<span style="color: rgb(32,33,36);">安装adb之后找到adb.exe所在的目录，在该目录下打开cmd命令行</span>
|
||||
|
||||
#### 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}
|
||||
### <span style="color: rgb(0,0,0);">4 uninstall amazon 相关app</span>
|
||||
|
||||
Alexa (com.amazon.dee.app) 和com.amazon.wellness app， 会影响到Validator的测试，需要Uninstall。
|
||||
<span style="color: rgb(0,0,0);">Alexa (com.amazon.dee.app) 和com.amazon.wellness app， 会影响到Validator的测试，需要Uninstall。</span>
|
||||
|
||||
The Alexa (com.amazon.dee.app) took too much time on handling the ACL_CONNECTED intent, which impacts the Validator\'s flow.
|
||||
<span style="color: rgb(0,0,0);">The Alexa (com.amazon.dee.app) took too much time on handling the ACL_CONNECTED intent, which impacts the Validator's flow.</span>
|
||||
|
||||
There is still another **app,com.amazon.wellness** app, who handled ACL_CONNECTED for 20+ seconds.Please uninstall it as well.
|
||||
<span style="color: rgb(0,0,0);">There is still another **app,com.amazon.wellness** app, who handled ACL_CONNECTED for 20+ seconds.Please uninstall it as well.</span>
|
||||
|
||||
现象： End-to-end integration测试，出现Pairing timeout
|
||||
<span style="color: rgb(255,0,0);">现象： End-to-end integration测试，出现Pairing timeout</span>
|
||||
|
||||
操作方式：
|
||||
<span style="color: rgb(255,0,0);">操作方式： </span>
|
||||
|
||||
adb uninstall com.amazon.wellness
|
||||
<span style="color: rgb(255,0,0);">adb uninstall com.amazon.wellness</span>
|
||||
|
||||
adb uninstall com.amazon.dee.app
|
||||
<span style="color: rgb(255,0,0);">adb uninstall com.amazon.dee.app</span>
|
||||
|
||||
\
|
||||
|
||||
### 5 测试账号和MODEL ID {#id-1.2.3FastPairValidator环境搭建-5测试账号和MODELID}
|
||||
### <span style="color: rgb(153,51,0);">5 测试账号和MODEL ID</span>
|
||||
|
||||
使用Fast Pair Validator测试，需要先登陆Google账号，测试设备使用的Model ID,public key, private key 必须是该google账号注册的Device。
|
||||
|
||||
场内测试账号：[realsilbt8888@gmail.com](mailto:realsilbt8888@gmail.com){.external-link rel="nofollow"}
|
||||
场内测试账号：<a href="mailto:realsilbt8888@gmail.com" class="external-link" rel="nofollow">realsilbt8888@gmail.com</a>
|
||||
|
||||
**Note：**
|
||||
**<span style="color: rgb(255,0,0);">Note：</span>**
|
||||
|
||||
fast pair validator app使用的model id 要和DUT开发板配置的model id一致。
|
||||
|
||||
|
||||
|
||||
|
||||
### **6 测试准备** {#id-1.2.3FastPairValidator环境搭建-6测试准备}
|
||||
### **<span style="color: rgb(153,51,0);">6 测试准备</span>**
|
||||
|
||||
测试过程中需要注意
|
||||
|
||||
手机端弹出配对提示框时不要手动点击，fast pair validator app会自己触发配对.
|
||||
<span style="color: rgb(255,0,0);">手机端弹出配对提示框时不要手动点击，fast pair validator app会自己触发配对</span>.
|
||||
|
||||
开始测试前，需要确认是否已经和待测试耳机配对过，需要删除配对信息。 最后最好在开始测试前，开关一下飞行模式。
|
||||
|
||||
点击GOT IT开始测试时，耳机端一定要处于Pairable mode，否则会scan不到设备, scan 到设备后，点击Test开始测试。
|
||||
|
||||
|
||||
::::
|
||||
|
||||
|
||||
12
1.3+测试.md
12
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"}
|
||||
<a href="https://wiki.realtek.com/display/BT/Test+Case+of+the+Third+Party" rel="nofollow">Test Case of the Third Party - BT Test - WIKI</a>
|
||||
|
||||
|
||||
|
||||
|
||||
\
|
||||
|
||||
@@ -13,11 +12,10 @@
|
||||
|
||||
Find My Device 那一页不需要测试：
|
||||
|
||||
|
||||
|
||||
|
||||
\
|
||||
|
||||
Fast Pair Validator那一页 EDDYSTONE 下面的测项不需要测试：
|
||||
|
||||
|
||||
:::
|
||||
|
||||
|
||||
@@ -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"}
|
||||
<span class="plugin_pagetree_children_span"><a href="https://wiki.realtek.com/display/BTMKT/1.3.1.1+FAST+PAIR?src=contextnavpagetreemode" rel="nofollow">1.3.1.1 FAST PAIR</a> </span>
|
||||
|
||||
这个测项客户自测并且提交测试结果到Google云端，认证实验室暂时不会测试。
|
||||
<span class="plugin_pagetree_children_span" style="color: rgb(255,0,0);">这个测项客户自测并且提交测试结果到Google云端，认证实验室暂时不会测试。</span>
|
||||
|
||||
目前来看只要有一次测试成功，并且有提交成功的测试结果到Google云端就可以，即使偶尔失败了，如果确定不是我们设备端的bug, 也没关系的
|
||||
<span class="plugin_pagetree_children_span">目前来看只要有一次测试成功，并且有提交成功的测试结果到Google云端就可以，即使偶尔失败了，如果确定不是我们设备端的bug, 也没关系的</span>
|
||||
|
||||
[https://partnerissuetracker.corp.google.com/u/0/issues/473688165](https://partnerissuetracker.corp.google.com/u/0/issues/473688165){.external-link rel="nofollow"}
|
||||
<span class="plugin_pagetree_children_span"><a href="https://partnerissuetracker.corp.google.com/u/0/issues/473688165" class="external-link" rel="nofollow">https://partnerissuetracker.corp.google.com/u/0/issues/473688165</a></span>
|
||||
|
||||
[]{.plugin_pagetree_children_span}
|
||||
:::
|
||||
<span class="plugin_pagetree_children_span"></span>
|
||||
|
||||
@@ -1,14 +1,13 @@
|
||||
# 1.3.1.1 FAST PAIR {#fast-pair}
|
||||
# 1.3.1.1 FAST PAIR
|
||||
|
||||
:::: {.Section1}
|
||||
`<style type="text/css">/**/
|
||||
div.rbtoc1777599001982 {padding: 0px;}
|
||||
div.rbtoc1777599001982 ul {margin-left: 0px;}
|
||||
div.rbtoc1777599001982 li {margin-left: 0px;padding-left: 0px;}
|
||||
<style type="text/css">/**/
|
||||
div.rbtoc1777701085477 {padding: 0px;}
|
||||
div.rbtoc1777701085477 ul {margin-left: 0px;}
|
||||
div.rbtoc1777701085477 li {margin-left: 0px;padding-left: 0px;}
|
||||
|
||||
/**/</style>`{=html}
|
||||
/**/</style>
|
||||
|
||||
::: {.toc-macro .rbtoc1777599001982}
|
||||
<div class="toc-macro rbtoc1777701085477">
|
||||
|
||||
- [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}
|
||||
</div>
|
||||
|
||||
#### 1 以下关于mcu cfg tool 的修改仅仅是为了通过fast pair validator测试，待测试通过之后，需要将相应的修改恢复默认值。否则GFPS功能没法正常使用。 {#id-1.3.1.1FASTPAIR-1以下关于mcucfgtool的修改仅仅是为了通过fastpairvalidator测试，待测试通过之后，需要将相应的修改恢复默认值。否则GFPS功能没法正常使用。}
|
||||
### <span style="color: rgb(0,51,102);">**Note**</span>
|
||||
|
||||
也就是说以下修改只能搭配fast pair validator app使用，请不要将对应的修改提交到正式release版本。
|
||||
#### <span style="color: rgb(0,51,102);">1 以下关于mcu cfg tool 的修改仅仅是为了通过fast pair validator测试，待测试通过之后，需要将相应的修改恢复默认值。否则GFPS功能没法正常使用。</span>
|
||||
|
||||
#### 2 测试过程中GFPS 弹窗出来之后请不要点击弹窗！！！ {#id-1.3.1.1FASTPAIR-2测试过程中GFPS弹窗出来之后请不要点击弹窗！！！}
|
||||
<span style="color: rgb(0,51,102);"> 也就是说以下修改只能搭配fast pair validator app使用，请不要将对应的修改提交到正式release版本。</span>
|
||||
|
||||
#### 3 GFPS Fast pair validator 测试走的Legacy flow, 通过gfps配对 legacy BREDR. {#id-1.3.1.1FASTPAIR-3GFPSFastpairvalidator测试走的Legacyflow,通过gfps配对legacyBREDR.}
|
||||
#### <span style="color: rgb(0,51,102);">2 测试过程中GFPS 弹窗出来之后请不要点击弹窗！！！</span>
|
||||
|
||||
#### 4 mcu cfg tool 中 可以配置按键key1进入legacy Pairing mode(MMI 0x6C)，有些测试会需要短按key1进入Pairing mode {#id-1.3.1.1FASTPAIR-4mcucfgtool中可以配置按键key1进入legacyPairingmode(MMI0x6C)，有些测试会需要短按key1进入Pairingmode}
|
||||
#### <span style="color: rgb(0,51,102);">3 GFPS Fast pair validator 测试走的Legacy flow, 通过gfps配对 legacy BREDR.</span>
|
||||
|
||||
|
||||
#### <span style="color: rgb(0,51,102);">4 mcu cfg tool 中 可以配置按键key1进入legacy Pairing mode(MMI 0x6C)，有些测试会需要短按key1进入Pairing mode</span>
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
\
|
||||
|
||||
#### 5 手机提示信息解读： {#id-1.3.1.1FASTPAIR-5手机提示信息解读：}
|
||||
#### <span style="color: rgb(153,51,0);">5 手机提示信息解读：</span>
|
||||
|
||||
##### Upair the device：耳机做factory reset清掉配对信息 {#id-1.3.1.1FASTPAIR-Upairthedevice：耳机做factoryreset清掉配对信息}
|
||||
##### <span style="color: rgb(153,51,0);"> Upair the device：耳机做factory reset清掉配对信息</span>
|
||||
|
||||
##### place the device back into pairing mode：耳机进入pairing mode {#id-1.3.1.1FASTPAIR-placethedevicebackintopairingmode：耳机进入pairingmode}
|
||||
##### <span style="color: rgb(153,51,0);"> place the device back into pairing mode：耳机进入pairing mode</span><span style="color: rgb(153,51,0);"> </span>
|
||||
|
||||
#### 6 测试准备 {#id-1.3.1.1FASTPAIR-6测试准备}
|
||||
#### <span style="color: rgb(153,51,0);">6 测试准备</span>
|
||||
|
||||
##### 打开Fast Pair Validator app {#id-1.3.1.1FASTPAIR-打开FastPairValidatorapp}
|
||||
##### <span style="color: rgb(153,51,0);">打开Fast Pair Validator app</span>
|
||||
|
||||
[]{style="color: rgb(153,51,0);"}
|
||||
<span style="color: rgb(153,51,0);"></span>
|
||||
|
||||
##### 通过model id找到待测试设备 {#id-1.3.1.1FASTPAIR-通过modelid找到待测试设备}
|
||||
##### <span style="color: rgb(153,51,0);">通过model id找到待测试设备</span>
|
||||
|
||||
[]{style="color: rgb(153,51,0);"}
|
||||
<span style="color: rgb(153,51,0);"></span>
|
||||
|
||||
##### 选择FAST PAIR进行测试 {#id-1.3.1.1FASTPAIR-选择FASTPAIR进行测试}
|
||||
##### <span style="color: rgb(153,51,0);">选择FAST PAIR进行测试</span>
|
||||
|
||||
[]{style="color: rgb(153,51,0);"}
|
||||
<span style="color: rgb(153,51,0);"></span>
|
||||
|
||||
##### 不要Enable LE spec test {#id-1.3.1.1FASTPAIR-不要EnableLEspectest}
|
||||
##### <span style="color: rgb(153,51,0);">不要Enable LE spec test</span>
|
||||
|
||||
[]{style="color: rgb(153,51,0);"}
|
||||
<span style="color: rgb(153,51,0);"></span>
|
||||
|
||||
### Calibration 测试 {#id-1.3.1.1FASTPAIR-Calibration测试}
|
||||
### <span style="color: rgb(153,51,0);">Calibration 测试</span>
|
||||
|
||||
Note:
|
||||
|
||||
@@ -102,15 +102,15 @@ calibration 测试， discoverable adv interval需要足够小，spec 规定 dis
|
||||
|
||||
Note:
|
||||
|
||||
GFPS 弹窗出来之后请**不要**点击弹窗！！！
|
||||
GFPS 弹窗出来之后请**<span style="color: rgb(255,0,0);">不要</span>**点击弹窗！！！
|
||||
|
||||
如果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"}
|
||||
<span style="color: rgb(153,51,0);">详细文档可以参考：</span><span style="color: rgb(153,51,0);"><a href="https://wiki.realtek.com/display/BTMKT/tx+power+adjust+user+guide" rel="nofollow">tx power adjust user guide - BT_Market - WIKI</a></span>
|
||||
|
||||
### End-to-end integration 测试 {#id-1.3.1.1FASTPAIR-End-to-endintegration测试}
|
||||
### <span style="color: rgb(153,51,0);">End-to-end integration 测试</span>
|
||||
|
||||
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<span style="color: rgb(255,0,0);">需要设置成disable(不勾选)</span>。
|
||||
|
||||
|
||||
|
||||
|
||||
如果找不到 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 <span class="jira-issue" client-id="SINGLE_2d885edc-676b-3349-9548-fe5648c9d8cd_948641808_2c9082e76519d09101657ff5cfb3003b" jira-key="BTSOCTOOL-2822"> <a href="https://jira.realtek.com/browse/BTSOCTOOL-2822" class="jira-issue-key"><span class="aui-icon aui-icon-wait issue-placeholder"></span>BTSOCTOOL-2822</a> - <span class="summary">Getting issue details...</span> <span class="aui-lozenge aui-lozenge-subtle aui-lozenge-default issue-placeholder">STATUS</span> </span> 进行配置，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。 <span style="color: rgb(255,0,0);">注意一定要在“10.Un-Repair device”显示“Unpairing finished!”后才能点NEXT。</span>
|
||||
|
||||
如此反复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"}
|
||||
<a href="/download/attachments/948641808/End%20To%20End%20test.mp4?version=1&modificationDate=1759129643533&api=v2" data-linked-resource-container-id="948641808" data-linked-resource-container-version="19" data-linked-resource-content-type="video/mp4" data-linked-resource-default-alias="End To End test.mp4" data-linked-resource-id="948642410" data-linked-resource-type="attachment" data-linked-resource-version="1" data-nice-type="Multimedia">End To End test.mp4</a>
|
||||
|
||||
### Auto pairing 测试 {#id-1.3.1.1FASTPAIR-Autopairing测试}
|
||||
### <span style="color: rgb(153,51,0);">Auto pairing </span><span style="color: rgb(153,51,0);">测试</span>
|
||||
|
||||
Mcu cfg tool配置：
|
||||
<span style="color: rgb(0,0,0);">Mcu cfg tool配置：</span>
|
||||
|
||||
测试该测项的时候，手机清除配对信息(unpair device)，DUT断线需要进入discoverable mode, 所以mcu config tool 中 RWS页面下 rws normal disconnect enter pairing mode[需要设置成enable(勾选)。]{style="color: rgb(0,0,0);"}\
|
||||
<span style="color: rgb(0,0,0);">测试该测项的时候，手机清除配对信息(unpair device)，DUT断线需要进入discoverable mode, 所以mcu config tool 中 RWS页面下 rws normal disconnect enter pairing mode<span style="color: rgb(255,0,0);">需要设置成enable(勾选)。</span></span>\
|
||||
app_cfg_const.rws_disconnect_enter_pairing
|
||||
|
||||
[]{style="color: rgb(0,0,0);"}
|
||||
<span style="color: rgb(0,0,0);"></span>
|
||||
|
||||
如果找不到 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 <span class="jira-issue" client-id="SINGLE_2d885edc-676b-3349-9548-fe5648c9d8cd_948641808_2c9082e76519d09101657ff5cfb3003b" jira-key="BTSOCTOOL-2822"> <a href="https://jira.realtek.com/browse/BTSOCTOOL-2822" class="jira-issue-key"><span class="aui-icon aui-icon-wait issue-placeholder"></span>BTSOCTOOL-2822</a> - <span class="summary">Getting issue details...</span> <span class="aui-lozenge aui-lozenge-subtle aui-lozenge-default issue-placeholder">STATUS</span> </span> 进行配置，RWS normal disconnect enter pairing mode 改成Normal disconnect enter pairing mode
|
||||
|
||||
|
||||
|
||||
|
||||
[\
|
||||
]{style="color: rgb(0,0,0);"}
|
||||
<span style="color: rgb(0,0,0);">\
|
||||
</span>
|
||||
|
||||
设置每一轮测试持续时间以及重复进行多少轮测试([推荐使用APP中提供的默认值进行测试（100次，一次120s)，然后点击test, ]{style="color: rgb(0,0,0);"}
|
||||
<span style="color: rgb(0,0,0);">设置每一轮测试持续时间以及重复进行多少轮测试(<span style="color: rgb(255,0,0);">推荐使用APP中提供的默认值进行测试（100次，一次120s</span>)，然后点击test, </span>
|
||||
|
||||
测试时将手机setting-》显示-》屏幕超时设置成最大值。灭屏之后测试好像会stop，所以屏幕要保持常亮的状态。
|
||||
<span style="color: rgb(255,0,0);">测试时将手机setting-》显示-》屏幕超时设置成最大值。灭屏之后测试好像会stop，所以屏幕要保持常亮的状态。</span>
|
||||
|
||||
\
|
||||
|
||||
**Note:**
|
||||
**<span style="color: rgb(255,0,0);">Note:</span>**
|
||||
|
||||
这个测试按照Google的测试spec是要求每轮测试之前都要强制进pairing mode的。
|
||||
|
||||
@@ -178,23 +178,23 @@ app_cfg_const.rws_disconnect_enter_pairing
|
||||
|
||||
\
|
||||
|
||||
|
||||
|
||||
|
||||
### Auto Subsequent Pairing 测试 {#id-1.3.1.1FASTPAIR-AutoSubsequentPairing测试}
|
||||
### <span style="color: rgb(153,51,0);">Auto Subsequent Pairing </span><span style="color: rgb(153,51,0);">测试</span>
|
||||
|
||||
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需要<span style="color: rgb(255,0,0);">设置成disable(不勾选)。</span>
|
||||
|
||||
|
||||
|
||||
|
||||
如果找不到 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 <span class="jira-issue" client-id="SINGLE_2d885edc-676b-3349-9548-fe5648c9d8cd_948641808_2c9082e76519d09101657ff5cfb3003b" jira-key="BTSOCTOOL-2822"> <a href="https://jira.realtek.com/browse/BTSOCTOOL-2822" class="jira-issue-key"><span class="aui-icon aui-icon-wait issue-placeholder"></span>BTSOCTOOL-2822</a> - <span class="summary">Getting issue details...</span> <span class="aui-lozenge aui-lozenge-subtle aui-lozenge-default issue-placeholder">STATUS</span> </span> 进行配置，RWS normal disconnect enter pairing mode 改成Normal disconnect enter pairing mode
|
||||
|
||||
|
||||
|
||||
|
||||
\
|
||||
|
||||
**Note:**
|
||||
**<span style="color: rgb(255,0,0);">Note:</span>**
|
||||
|
||||
这个测试按照Google的测试spec是要求每轮测试之前都要打nondiscoverable 广播的。
|
||||
|
||||
@@ -206,19 +206,19 @@ MCU cfg tool 配置：
|
||||
|
||||
所以针对异常的情况，
|
||||
|
||||
soc端是没办法做到所有的失败场景下都能保证下一轮测试一定会主动打nondiscoverable 广播(不在pairing mode才会打nondiscoverable 广播)， 因为手机端并不会告诉soc 什么时候测试开始。
|
||||
soc端是没办法做到所有的失败场景下都能保证下一轮测试一定会主动打nondiscoverable 广播(<span style="color: rgb(255,0,0);">不在pairing mode才会打nondiscoverable 广播</span>)， 因为手机端并不会告诉soc 什么时候测试开始。
|
||||
|
||||
所以如果跑自动化测试遇到失败的情况，建议手动测试：
|
||||
|
||||
每一轮测试结束之后EVB按一下reset或者是关机再开机让设备端主动打nondiscoverable 广播(注意这个时候EVB一定不能做factory reset，也不能进pairing mode, 因为这个时候是期望打 nondiscoverable 广播)
|
||||
每一轮测试结束之后EVB按一下reset或者是关机再开机让设备端主动打nondiscoverable 广播(<span style="color: rgb(255,0,0);">注意这个时候EVB一定不能做factory reset，也不能进pairing mode, 因为这个时候是期望打 nondiscoverable 广播</span>)
|
||||
|
||||
BLE advertisements don\'t contain fast pair account key while not in pairing mode 如果频繁遇到这个error， 可以尝试手动测试试试看
|
||||
<span style="color: rgb(41,41,41);">BLE advertisements don't contain fast pair account key while not in pairing mode 如果频繁遇到这个error， 可以尝试手动测试试试看</span>
|
||||
|
||||
\
|
||||
|
||||
测试信息设置：
|
||||
|
||||
|
||||
|
||||
|
||||
手机端测试信息设置完成之后，
|
||||
|
||||
@@ -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测试}
|
||||
### <span style="color: rgb(153,51,0);">Cross Seekers Auto Subsequent Pairing Test </span><span style="color: rgb(153,51,0);">测试</span>
|
||||
|
||||
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需要<span style="color: rgb(255,0,0);">设置成disable(不勾选)。</span>
|
||||
|
||||
|
||||
|
||||
|
||||
如果找不到 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 <span class="jira-issue" client-id="SINGLE_2d885edc-676b-3349-9548-fe5648c9d8cd_948641808_2c9082e76519d09101657ff5cfb3003b" jira-key="BTSOCTOOL-2822"> <a href="https://jira.realtek.com/browse/BTSOCTOOL-2822" class="jira-issue-key"><span class="aui-icon aui-icon-wait issue-placeholder"></span>BTSOCTOOL-2822</a> - <span class="summary">Getting issue details...</span> <span class="aui-lozenge aui-lozenge-subtle aui-lozenge-default issue-placeholder">STATUS</span> </span> 进行配置，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，手机端清掉配对信息<a href="https://wiki.realtek.com/pages/viewpage.action?pageId=401291585" rel="nofollow">1 gfps/finder 如何清除配对信息 - BT_Market - WIKI</a>， 之后耳机开机进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"}
|
||||
<a href="/download/attachments/948641808/Cross%20Seekers%20Auto%20Subsequent%20Pairing%20Test.mp4?version=1&modificationDate=1759224099177&api=v2" data-linked-resource-container-id="948641808" data-linked-resource-container-version="19" data-linked-resource-content-type="video/mp4" data-linked-resource-default-alias="Cross Seekers Auto Subsequent Pairing Test.mp4" data-linked-resource-id="948651208" data-linked-resource-type="attachment" data-linked-resource-version="1" data-nice-type="Multimedia">Cross Seekers Auto Subsequent Pairing Test.mp4</a>
|
||||
|
||||
测试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"}
|
||||
<a href="/download/attachments/948641808/COM12_2025-09-30_16-56-51.log?version=1&modificationDate=1759223471600&api=v2" data-linked-resource-container-id="948641808" data-linked-resource-container-version="19" data-linked-resource-content-type="text/plain" data-linked-resource-default-alias="COM12_2025-09-30_16-56-51.log" data-linked-resource-id="948651140" data-linked-resource-type="attachment" data-linked-resource-version="1" data-nice-type="Text File">COM12_2025-09-30_16-56-51.log</a>
|
||||
|
||||
[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"}
|
||||
<a href="/download/attachments/948641808/COM12_btsnoop_2025-09-30_16-51-45.cfa?version=1&modificationDate=1759223475897&api=v2" data-linked-resource-container-id="948641808" data-linked-resource-container-version="19" data-linked-resource-content-type="application/octet-stream" data-linked-resource-default-alias="COM12_btsnoop_2025-09-30_16-51-45.cfa" data-linked-resource-id="948651142" data-linked-resource-type="attachment" data-linked-resource-version="1">COM12_btsnoop_2025-09-30_16-51-45.cfa</a>
|
||||
|
||||
[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"}
|
||||
<a href="/download/attachments/948641808/COM12_2025-09-30_16-51-39.log?version=1&modificationDate=1759223476397&api=v2" data-linked-resource-container-id="948641808" data-linked-resource-container-version="19" data-linked-resource-content-type="text/plain" data-linked-resource-default-alias="COM12_2025-09-30_16-51-39.log" data-linked-resource-id="948651143" data-linked-resource-type="attachment" data-linked-resource-version="1" data-nice-type="Text File">COM12_2025-09-30_16-51-39.log</a>
|
||||
|
||||
[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"}
|
||||
<a href="/download/attachments/948641808/COM12_2025-09-26_14-19-00.log?version=1&modificationDate=1759223503080&api=v2" data-linked-resource-container-id="948641808" data-linked-resource-container-version="19" data-linked-resource-content-type="text/plain" data-linked-resource-default-alias="COM12_2025-09-26_14-19-00.log" data-linked-resource-id="948651148" data-linked-resource-type="attachment" data-linked-resource-version="1" data-nice-type="Text File">COM12_2025-09-26_14-19-00.log</a>
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
\
|
||||
|
||||
### Public Key Based Pairing Request in Non Discoverable Mode 测试 {#id-1.3.1.1FASTPAIR-PublicKeyBasedPairingRequestinNonDiscoverableMode测试}
|
||||
### <span style="color: rgb(153,51,0);">Public Key Based Pairing Request in Non Discoverable Mode </span><span style="color: rgb(153,51,0);">测试</span>
|
||||
|
||||
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需要<span style="color: rgb(255,0,0);">设置成disable(不勾选)。</span>
|
||||
|
||||
|
||||
|
||||
|
||||
如果找不到 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 <span class="jira-issue" client-id="SINGLE_2d885edc-676b-3349-9548-fe5648c9d8cd_948641808_2c9082e76519d09101657ff5cfb3003b" jira-key="BTSOCTOOL-2822"> <a href="https://jira.realtek.com/browse/BTSOCTOOL-2822" class="jira-issue-key"><span class="aui-icon aui-icon-wait issue-placeholder"></span>BTSOCTOOL-2822</a> - <span class="summary">Getting issue details...</span> <span class="aui-lozenge aui-lozenge-subtle aui-lozenge-default issue-placeholder">STATUS</span> </span> 进行配置，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，手机端清掉配对信息<a href="https://wiki.realtek.com/pages/viewpage.action?pageId=401291585" rel="nofollow">1 gfps/finder 如何清除配对信息 - BT_Market - WIKI</a>， 之后耳机开机进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"}
|
||||
<a href="/download/attachments/948641808/public%20key%20based%20request%20in%20non%20discoverable%20mode-Non%20LEA.mp4?version=1&modificationDate=1759225238333&api=v2" data-linked-resource-container-id="948641808" data-linked-resource-container-version="19" data-linked-resource-content-type="video/mp4" data-linked-resource-default-alias="public key based request in non discoverable mode-Non LEA.mp4" data-linked-resource-id="948651368" data-linked-resource-type="attachment" data-linked-resource-version="1" data-nice-type="Multimedia">public key based request in non discoverable mode-Non LEA.mp4</a>
|
||||
|
||||
测试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"}
|
||||
<a href="/download/attachments/948641808/COM12_2025-09-30_17-33-58.log?version=1&modificationDate=1759225010223&api=v2" data-linked-resource-container-id="948641808" data-linked-resource-container-version="19" data-linked-resource-content-type="text/plain" data-linked-resource-default-alias="COM12_2025-09-30_17-33-58.log" data-linked-resource-id="948651337" data-linked-resource-type="attachment" data-linked-resource-version="1" data-nice-type="Text File">COM12_2025-09-30_17-33-58.log</a>
|
||||
|
||||
[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"}
|
||||
<a href="/download/attachments/948641808/COM12_btsnoop_2025-09-30_17-29-41.cfa?version=1&modificationDate=1759225015190&api=v2" data-linked-resource-container-id="948641808" data-linked-resource-container-version="19" data-linked-resource-content-type="application/octet-stream" data-linked-resource-default-alias="COM12_btsnoop_2025-09-30_17-29-41.cfa" data-linked-resource-id="948651338" data-linked-resource-type="attachment" data-linked-resource-version="1">COM12_btsnoop_2025-09-30_17-29-41.cfa</a>
|
||||
|
||||
[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"}
|
||||
<a href="/download/attachments/948641808/COM12_2025-09-30_17-29-39.log?version=1&modificationDate=1759225015860&api=v2" data-linked-resource-container-id="948641808" data-linked-resource-container-version="19" data-linked-resource-content-type="text/plain" data-linked-resource-default-alias="COM12_2025-09-30_17-29-39.log" data-linked-resource-id="948651339" data-linked-resource-type="attachment" data-linked-resource-version="1" data-nice-type="Text File">COM12_2025-09-30_17-29-39.log</a>
|
||||
|
||||
|
||||
|
||||
|
||||
\
|
||||
|
||||
### Public Key Based Pairing Request After Retroactive Pair 测试 {#id-1.3.1.1FASTPAIR-PublicKeyBasedPairingRequestAfterRetroactivePair测试}
|
||||
### <span style="color: rgb(153,51,0);">Public Key Based Pairing Request After Retroactive Pair </span><span style="color: rgb(153,51,0);">测试</span>
|
||||
|
||||
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需要<span style="color: rgb(255,0,0);">设置成disable(不勾选)。</span>
|
||||
|
||||
|
||||
|
||||
|
||||
如果找不到 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 <span class="jira-issue" client-id="SINGLE_2d885edc-676b-3349-9548-fe5648c9d8cd_948641808_2c9082e76519d09101657ff5cfb3003b" jira-key="BTSOCTOOL-2822"> <a href="https://jira.realtek.com/browse/BTSOCTOOL-2822" class="jira-issue-key"><span class="aui-icon aui-icon-wait issue-placeholder"></span>BTSOCTOOL-2822</a> - <span class="summary">Getting issue details...</span> <span class="aui-lozenge aui-lozenge-subtle aui-lozenge-default issue-placeholder">STATUS</span> </span> 进行配置，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，手机端清掉配对信息<a href="https://wiki.realtek.com/pages/viewpage.action?pageId=401291585" rel="nofollow">1 gfps/finder 如何清除配对信息 - BT_Market - WIKI</a>， 之后耳机开机进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"}
|
||||
<a href="/download/attachments/948641808/Public%20key%20based%20pairing%20request%20after%20retroactive%20pair-nonLEA-Get%20account%20key%20fail.mp4?version=1&modificationDate=1759226451537&api=v2" data-linked-resource-container-id="948641808" data-linked-resource-container-version="19" data-linked-resource-content-type="video/mp4" data-linked-resource-default-alias="Public key based pairing request after retroactive pair-nonLEA-Get account key fail.mp4" data-linked-resource-id="948651473" data-linked-resource-type="attachment" data-linked-resource-version="1" data-nice-type="Multimedia">Public key based pairing request after retroactive pair-nonLEA-Get account key fail.mp4</a>
|
||||
|
||||
测试成功视频：
|
||||
|
||||
[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"}
|
||||
<a href="/download/attachments/948641808/Public%20key%20based%20pairing%20request%20after%20retroactive%20pair-nonLEA.mp4?version=1&modificationDate=1759226617723&api=v2" data-linked-resource-container-id="948641808" data-linked-resource-container-version="19" data-linked-resource-content-type="video/mp4" data-linked-resource-default-alias="Public key based pairing request after retroactive pair-nonLEA.mp4" data-linked-resource-id="948651483" data-linked-resource-type="attachment" data-linked-resource-version="1" data-nice-type="Multimedia">Public key based pairing request after retroactive pair-nonLEA.mp4</a>
|
||||
|
||||
\
|
||||
|
||||
测试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"}
|
||||
<a href="/download/attachments/948641808/COM12_2025-10-13_13-47-37.log?version=1&modificationDate=1760336127463&api=v2" data-linked-resource-container-id="948641808" data-linked-resource-container-version="19" data-linked-resource-content-type="text/plain" data-linked-resource-default-alias="COM12_2025-10-13_13-47-37.log" data-linked-resource-id="964439163" data-linked-resource-type="attachment" data-linked-resource-version="1" data-nice-type="Text File">COM12_2025-10-13_13-47-37.log</a>
|
||||
|
||||
[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"}
|
||||
<a href="/download/attachments/948641808/COM12_2025-10-13_13-51-37.log?version=1&modificationDate=1760336113757&api=v2" data-linked-resource-container-id="948641808" data-linked-resource-container-version="19" data-linked-resource-content-type="text/plain" data-linked-resource-default-alias="COM12_2025-10-13_13-51-37.log" data-linked-resource-id="964439159" data-linked-resource-type="attachment" data-linked-resource-version="1" data-nice-type="Text File">COM12_2025-10-13_13-51-37.log</a>
|
||||
|
||||
[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"}
|
||||
<a href="/download/attachments/948641808/COM12_btsnoop_2025-10-13_13-48-53.cfa?version=1&modificationDate=1760336126687&api=v2" data-linked-resource-container-id="948641808" data-linked-resource-container-version="19" data-linked-resource-content-type="application/octet-stream" data-linked-resource-default-alias="COM12_btsnoop_2025-10-13_13-48-53.cfa" data-linked-resource-id="964439162" data-linked-resource-type="attachment" data-linked-resource-version="1">COM12_btsnoop_2025-10-13_13-48-53.cfa</a>
|
||||
|
||||
[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"}
|
||||
<a href="/download/attachments/948641808/Public%20Key%20Based%20Pairing%20Request%20After%20Retroactive%20Pair%E6%B5%8B%E8%AF%95pass.7z?version=1&modificationDate=1763543863557&api=v2" data-linked-resource-container-id="948641808" data-linked-resource-container-version="19" data-linked-resource-content-type="application/octet-stream" data-linked-resource-default-alias="Public Key Based Pairing Request After Retroactive Pair测试pass.7z" data-linked-resource-id="998593044" data-linked-resource-type="attachment" data-linked-resource-version="1">Public Key Based Pairing Request After Retroactive Pair测试pass.7z</a>
|
||||
|
||||
### Account key Broadcasting & Rotation of RPA测试 {#id-1.3.1.1FASTPAIR-AccountkeyBroadcasting&RotationofRPA测试}
|
||||
### <span style="color: rgb(153,51,0);">Account key Broadcasting & Rotation of RPA</span><span style="color: rgb(153,51,0);">测试</span>
|
||||
|
||||
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需要<span style="color: rgb(255,0,0);">设置成disable(不勾选)。</span>
|
||||
|
||||
|
||||
|
||||
|
||||
如果找不到 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 <span class="jira-issue" client-id="SINGLE_2d885edc-676b-3349-9548-fe5648c9d8cd_948641808_2c9082e76519d09101657ff5cfb3003b" jira-key="BTSOCTOOL-2822"> <a href="https://jira.realtek.com/browse/BTSOCTOOL-2822" class="jira-issue-key"><span class="aui-icon aui-icon-wait issue-placeholder"></span>BTSOCTOOL-2822</a> - <span class="summary">Getting issue details...</span> <span class="aui-lozenge aui-lozenge-subtle aui-lozenge-default issue-placeholder">STATUS</span> </span> 进行配置，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测试}
|
||||
### <span style="color: rgb(153,51,0);">Key Based Request Flags Reserved Bit Verification </span><span style="color: rgb(153,51,0);">测试</span>
|
||||
|
||||
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需要<span style="color: rgb(255,0,0);">设置成disable(不勾选)。</span>
|
||||
|
||||
|
||||
|
||||
|
||||
如果找不到 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 <span class="jira-issue" client-id="SINGLE_2d885edc-676b-3349-9548-fe5648c9d8cd_948641808_2c9082e76519d09101657ff5cfb3003b" jira-key="BTSOCTOOL-2822"> <a href="https://jira.realtek.com/browse/BTSOCTOOL-2822" class="jira-issue-key"><span class="aui-icon aui-icon-wait issue-placeholder"></span>BTSOCTOOL-2822</a> - <span class="summary">Getting issue details...</span> <span class="aui-lozenge aui-lozenge-subtle aui-lozenge-default issue-placeholder">STATUS</span> </span> 进行配置，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"}
|
||||
<a href="/download/attachments/948641808/Key%20Based%20Request%20Flags%20Reserved%20Bit%20Verification.mp4?version=1&modificationDate=1760339352253&api=v2" data-linked-resource-container-id="948641808" data-linked-resource-container-version="19" data-linked-resource-content-type="video/mp4" data-linked-resource-default-alias="Key Based Request Flags Reserved Bit Verification.mp4" data-linked-resource-id="964439764" data-linked-resource-type="attachment" data-linked-resource-version="1" data-nice-type="Multimedia">Key Based Request Flags Reserved Bit Verification.mp4</a>
|
||||
|
||||
\
|
||||
|
||||
### Distance 0.3 Meter 测试 {#id-1.3.1.1FASTPAIR-Distance0.3Meter测试}
|
||||
### <span style="color: rgb(153,51,0);">Distance 0.3 Meter 测试</span>
|
||||
|
||||
耳机开机，[按键key1进入GFPS LEA配对模式，然后开始测试，等待测试完成。]{style="color: rgb(153,51,0);"}
|
||||
<span style="color: rgb(153,51,0);">耳机开机，<span style="color: rgb(0,0,0);">按键key1进入GFPS LEA配对模式，</span>然后开始测试，等待测试完成。</span>
|
||||
|
||||
Note:
|
||||
<span style="color: rgb(153,51,0);">Note:</span>
|
||||
|
||||
GFPS 弹窗出来之后不要点；
|
||||
<span style="color: rgb(153,51,0);">GFPS 弹窗出来之后不要点；</span>
|
||||
|
||||
如果该测项测不过，MCU cfg tool Thirdparty 页面需要适当减小tx power(比如从-10，减小到-12)；并重新跑 \"**Calibration 测试\"** 以及该测项
|
||||
<span style="color: rgb(153,51,0);">如果该测项测不过，MCU cfg tool Thirdparty 页面需要适当减小tx power(比如从-10，减小到-12)；并重新跑 "</span><span style="color: rgb(153,51,0);">**Calibration 测试"** 以及该测项 </span>
|
||||
|
||||
\
|
||||
|
||||
### []{style="color: rgb(153,51,0);"} {#id-1.3.1.1FASTPAIR-}
|
||||
### <span style="color: rgb(153,51,0);"></span>
|
||||
|
||||
\
|
||||
|
||||
### Distance 1.2 Meter 测试 {#id-1.3.1.1FASTPAIR-Distance1.2Meter测试}
|
||||
### <span style="color: rgb(153,51,0);">Distance 1.2 Meter 测试</span>
|
||||
|
||||
耳机开机，[按键key1进入GFPS LEA配对模式，然后开始测试，等待测试完成。]{style="color: rgb(153,51,0);"}
|
||||
<span style="color: rgb(153,51,0);">耳机开机，<span style="color: rgb(0,0,0);">按键key1进入GFPS LEA配对模式，</span>然后开始测试，等待测试完成。</span>
|
||||
|
||||
Note:
|
||||
<span style="color: rgb(153,51,0);">Note:</span>
|
||||
|
||||
GFPS 弹窗出来之后不要点；
|
||||
<span style="color: rgb(153,51,0);">GFPS 弹窗出来之后不要点；</span>
|
||||
|
||||
如果该测项测不过，MCU cfg tool Thirdparty 页面需要适当增大tx power(比如从-12增大到-10）；并重新跑 \"**Calibration 测试\"** 以及该测项
|
||||
<span style="color: rgb(153,51,0);">如果该测项测不过，MCU cfg tool Thirdparty 页面需要适当增大tx power(比如从-12增大到-10）；并重新跑 "</span><span style="color: rgb(153,51,0);">**Calibration 测试"** 以及该测项 </span>
|
||||
|
||||
\
|
||||
|
||||
\
|
||||
|
||||
### Distance 2 Meter 测试 {#id-1.3.1.1FASTPAIR-Distance2Meter测试}
|
||||
### <span style="color: rgb(153,51,0);">Distance 2 Meter 测试</span>
|
||||
|
||||
耳机开机，[按键key1进入GFPS LEA配对模式，然后开始测试，等待测试完成。]{style="color: rgb(153,51,0);"}
|
||||
<span style="color: rgb(153,51,0);">耳机开机，<span style="color: rgb(0,0,0);">按键key1进入GFPS LEA配对模式，</span>然后开始测试，等待测试完成。</span>
|
||||
|
||||
Note:
|
||||
<span style="color: rgb(153,51,0);">Note:</span>
|
||||
|
||||
GFPS 弹窗出来之后不要点；
|
||||
<span style="color: rgb(153,51,0);">GFPS 弹窗出来之后不要点；</span>
|
||||
|
||||
如果该测项测不过，MCU cfg tool Thirdparty 页面需要适当增大tx power(比如从-12增大到-10）；并重新跑 \"**Calibration 测试\"** 以及该测项
|
||||
<span style="color: rgb(153,51,0);">如果该测项测不过，MCU cfg tool Thirdparty 页面需要适当增大tx power(比如从-12增大到-10）；并重新跑 "</span><span style="color: rgb(153,51,0);">**Calibration 测试"** 以及该测项 </span>
|
||||
|
||||
|
||||
|
||||
@@ -460,21 +460,21 @@ GFPS 弹窗出来之后不要点；
|
||||
|
||||
\
|
||||
|
||||
### Battery Notification Verification 测试 {#id-1.3.1.1FASTPAIR-BatteryNotificationVerification测试}
|
||||
### <span style="color: rgb(153,51,0);">Battery Notification Verification 测试</span>
|
||||
|
||||
Note:
|
||||
<span style="color: rgb(153,51,0);">Note: </span>
|
||||
|
||||
该测项测试的时候需要接充电盒
|
||||
<span style="color: rgb(153,51,0);">该测项测试的时候需要接充电盒</span>
|
||||
|
||||
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需要<span style="color: rgb(255,0,0);">设置成disable(不勾选)。</span>
|
||||
|
||||
|
||||
|
||||
|
||||
如果找不到 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 <span class="jira-issue" client-id="SINGLE_2d885edc-676b-3349-9548-fe5648c9d8cd_948641808_2c9082e76519d09101657ff5cfb3003b" jira-key="BTSOCTOOL-2822"> <a href="https://jira.realtek.com/browse/BTSOCTOOL-2822" class="jira-issue-key"><span class="aui-icon aui-icon-wait issue-placeholder"></span>BTSOCTOOL-2822</a> - <span class="summary">Getting issue details...</span> <span class="aui-lozenge aui-lozenge-subtle aui-lozenge-default issue-placeholder">STATUS</span> </span> 进行配置，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测试}
|
||||
### <span style="color: rgb(153,51,0);">Battery Suppress Notification Verification 测试</span>
|
||||
|
||||
Note:
|
||||
<span style="color: rgb(153,51,0);">Note: </span>
|
||||
|
||||
该测项测试的时候需要接充电盒
|
||||
<span style="color: rgb(153,51,0);">该测项测试的时候需要接充电盒</span>
|
||||
|
||||
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需要<span style="color: rgb(255,0,0);">设置成disable(不勾选)。</span>
|
||||
|
||||
|
||||
|
||||
|
||||
如果找不到 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 <span class="jira-issue" client-id="SINGLE_2d885edc-676b-3349-9548-fe5648c9d8cd_948641808_2c9082e76519d09101657ff5cfb3003b" jira-key="BTSOCTOOL-2822"> <a href="https://jira.realtek.com/browse/BTSOCTOOL-2822" class="jira-issue-key"><span class="aui-icon aui-icon-wait issue-placeholder"></span>BTSOCTOOL-2822</a> - <span class="summary">Getting issue details...</span> <span class="aui-lozenge aui-lozenge-subtle aui-lozenge-default issue-placeholder">STATUS</span> </span> 进行配置，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测试}
|
||||
### <span style="color: rgb(153,51,0);">Battery Level Update Verification 测试</span>
|
||||
|
||||
Note:
|
||||
<span style="color: rgb(153,51,0);">Note: </span>
|
||||
|
||||
该测项测试的时候需要接充电盒
|
||||
<span style="color: rgb(153,51,0);">该测项测试的时候需要接充电盒</span>
|
||||
|
||||
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需要<span style="color: rgb(255,0,0);">设置成disable(不勾选)。</span>
|
||||
|
||||
|
||||
|
||||
|
||||
如果找不到 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 <span class="jira-issue" client-id="SINGLE_2d885edc-676b-3349-9548-fe5648c9d8cd_948641808_2c9082e76519d09101657ff5cfb3003b" jira-key="BTSOCTOOL-2822"> <a href="https://jira.realtek.com/browse/BTSOCTOOL-2822" class="jira-issue-key"><span class="aui-icon aui-icon-wait issue-placeholder"></span>BTSOCTOOL-2822</a> - <span class="summary">Getting issue details...</span> <span class="aui-lozenge aui-lozenge-subtle aui-lozenge-default issue-placeholder">STATUS</span> </span> 进行配置，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测试}
|
||||
### <span style="color: rgb(153,51,0);">Personalized Name Update 测试</span>
|
||||
|
||||
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需要<span style="color: rgb(255,0,0);">设置成disable(不勾选)。</span>
|
||||
|
||||
|
||||
|
||||
|
||||
如果找不到 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 <span class="jira-issue" client-id="SINGLE_2d885edc-676b-3349-9548-fe5648c9d8cd_948641808_2c9082e76519d09101657ff5cfb3003b" jira-key="BTSOCTOOL-2822"> <a href="https://jira.realtek.com/browse/BTSOCTOOL-2822" class="jira-issue-key"><span class="aui-icon aui-icon-wait issue-placeholder"></span>BTSOCTOOL-2822</a> - <span class="summary">Getting issue details...</span> <span class="aui-lozenge aui-lozenge-subtle aui-lozenge-default issue-placeholder">STATUS</span> </span> 进行配置，RWS normal disconnect enter pairing mode 改成Normal disconnect enter pairing mode
|
||||
|
||||
|
||||
|
||||
|
||||
\
|
||||
|
||||
@@ -546,11 +546,11 @@ MCU cfg tool 配置：
|
||||
|
||||
\
|
||||
|
||||
测试注意事项：
|
||||
<span style="color: rgb(255,0,0);">测试注意事项：</span>
|
||||
|
||||
测试之前板子先做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"}
|
||||
<a href="/download/attachments/948641808/Personalized%20name%20update.mp4?version=1&modificationDate=1759129788767&api=v2" data-linked-resource-container-id="948641808" data-linked-resource-container-version="19" data-linked-resource-content-type="video/mp4" data-linked-resource-default-alias="Personalized name update.mp4" data-linked-resource-id="948642419" data-linked-resource-type="attachment" data-linked-resource-version="1" data-nice-type="Multimedia">Personalized name update.mp4</a>
|
||||
|
||||
### Personalized Name with Provider First Time Pairing 测试 {#id-1.3.1.1FASTPAIR-PersonalizedNamewithProviderFirstTimePairing测试}
|
||||
### <span style="color: rgb(153,51,0);">Personalized Name with Provider First Time Pairing 测试</span>
|
||||
|
||||
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需要<span style="color: rgb(255,0,0);">设置成disable(不勾选)。</span>
|
||||
|
||||
|
||||
|
||||
|
||||
如果找不到 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 <span class="jira-issue" client-id="SINGLE_2d885edc-676b-3349-9548-fe5648c9d8cd_948641808_2c9082e76519d09101657ff5cfb3003b" jira-key="BTSOCTOOL-2822"> <a href="https://jira.realtek.com/browse/BTSOCTOOL-2822" class="jira-issue-key"><span class="aui-icon aui-icon-wait issue-placeholder"></span>BTSOCTOOL-2822</a> - <span class="summary">Getting issue details...</span> <span class="aui-lozenge aui-lozenge-subtle aui-lozenge-default issue-placeholder">STATUS</span> </span> 进行配置，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测试}
|
||||
### <span style="color: rgb(153,51,0);">Ring a Device 测试</span>
|
||||
|
||||
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需要<span style="color: rgb(255,0,0);">设置成disable(不勾选)。</span>
|
||||
|
||||
|
||||
|
||||
|
||||
如果找不到 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 <span class="jira-issue" client-id="SINGLE_2d885edc-676b-3349-9548-fe5648c9d8cd_948641808_2c9082e76519d09101657ff5cfb3003b" jira-key="BTSOCTOOL-2822"> <a href="https://jira.realtek.com/browse/BTSOCTOOL-2822" class="jira-issue-key"><span class="aui-icon aui-icon-wait issue-placeholder"></span>BTSOCTOOL-2822</a> - <span class="summary">Getting issue details...</span> <span class="aui-lozenge aui-lozenge-subtle aui-lozenge-default issue-placeholder">STATUS</span> </span> 进行配置，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"}
|
||||
<a href="/download/attachments/948641808/Ring%20a%20Device.mp4?version=1&modificationDate=1759129874047&api=v2" data-linked-resource-container-id="948641808" data-linked-resource-container-version="19" data-linked-resource-content-type="video/mp4" data-linked-resource-default-alias="Ring a Device.mp4" data-linked-resource-id="948642430" data-linked-resource-type="attachment" data-linked-resource-version="1" data-nice-type="Multimedia">Ring a Device.mp4</a>
|
||||
|
||||
### Retroactive Pair 测试 {#id-1.3.1.1FASTPAIR-RetroactivePair测试}
|
||||
### <span style="color: rgb(153,51,0);">Retroactive Pair 测试</span>
|
||||
|
||||
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需要设置成<span style="color: rgb(255,0,0);">disable(不勾选)。</span>
|
||||
|
||||
|
||||
|
||||
|
||||
如果找不到 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 <span class="jira-issue" client-id="SINGLE_2d885edc-676b-3349-9548-fe5648c9d8cd_948641808_2c9082e76519d09101657ff5cfb3003b" jira-key="BTSOCTOOL-2822"> <a href="https://jira.realtek.com/browse/BTSOCTOOL-2822" class="jira-issue-key"><span class="aui-icon aui-icon-wait issue-placeholder"></span>BTSOCTOOL-2822</a> - <span class="summary">Getting issue details...</span> <span class="aui-lozenge aui-lozenge-subtle aui-lozenge-default issue-placeholder">STATUS</span> </span> 进行配置，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"}
|
||||
<a href="/download/attachments/948641808/retroactive%20pair%20test.mp4?version=1&modificationDate=1759129956680&api=v2" data-linked-resource-container-id="948641808" data-linked-resource-container-version="19" data-linked-resource-content-type="video/mp4" data-linked-resource-default-alias="retroactive pair test.mp4" data-linked-resource-id="948642435" data-linked-resource-type="attachment" data-linked-resource-version="1" data-nice-type="Multimedia">retroactive pair test.mp4</a>
|
||||
|
||||
测试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"}
|
||||
<a href="/download/attachments/948641808/Retroactive%20Pair%E6%B5%8B%E8%AF%95pass.7z?version=1&modificationDate=1763543586347&api=v2" data-linked-resource-container-id="948641808" data-linked-resource-container-version="19" data-linked-resource-content-type="application/octet-stream" data-linked-resource-default-alias="Retroactive Pair测试pass.7z" data-linked-resource-id="998593012" data-linked-resource-type="attachment" data-linked-resource-version="1">Retroactive Pair测试pass.7z</a>
|
||||
|
||||
### Active Noise Control Verification 测试 {#id-1.3.1.1FASTPAIR-ActiveNoiseControlVerification测试}
|
||||
### <span style="color: rgb(153,51,0);">Active Noise Control Verification 测试</span>
|
||||
|
||||
目前还不清楚怎么测试，如果不支援可以不测
|
||||
<span style="color: rgb(153,51,0);">目前还不清楚怎么测试，如果不支援可以不测</span>
|
||||
|
||||
### Active Noise Control Disable 测试 {#id-1.3.1.1FASTPAIR-ActiveNoiseControlDisable测试}
|
||||
### <span style="color: rgb(153,51,0);">Active Noise Control Disable 测试</span>
|
||||
|
||||
目前还不清楚怎么测试，如果不支援可以不测
|
||||
<span style="color: rgb(153,51,0);">目前还不清楚怎么测试，如果不支援可以不测</span>
|
||||
|
||||
### Firmware Version 测试 {#id-1.3.1.1FASTPAIR-FirmwareVersion测试}
|
||||
### <span style="color: rgb(153,51,0);">Firmware Version 测试</span>
|
||||
|
||||
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需要<span style="color: rgb(255,0,0);">设置成disable(不勾选)。</span>
|
||||
|
||||
|
||||
|
||||
|
||||
如果找不到 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 <span class="jira-issue" client-id="SINGLE_2d885edc-676b-3349-9548-fe5648c9d8cd_948641808_2c9082e76519d09101657ff5cfb3003b" jira-key="BTSOCTOOL-2822"> <a href="https://jira.realtek.com/browse/BTSOCTOOL-2822" class="jira-issue-key"><span class="aui-icon aui-icon-wait issue-placeholder"></span>BTSOCTOOL-2822</a> - <span class="summary">Getting issue details...</span> <span class="aui-lozenge aui-lozenge-subtle aui-lozenge-default issue-placeholder">STATUS</span> </span> 进行配置，RWS normal disconnect enter pairing mode 改成Normal disconnect enter pairing mode
|
||||
|
||||
|
||||
|
||||
|
||||
\
|
||||
|
||||
### Dynamic Buffer Size测试 {#id-1.3.1.1FASTPAIR-DynamicBufferSize测试}
|
||||
### <span style="color: rgb(153,51,0);">Dynamic Buffer Size测试</span>
|
||||
|
||||
目前还不清楚怎么测试，如果不支援 可以不测
|
||||
<span style="color: rgb(153,51,0);">目前还不清楚怎么测试，如果不支援 可以不测</span>
|
||||
|
||||
\
|
||||
|
||||
### 10.测试结果上报 {#id-1.3.1.1FASTPAIR-10.测试结果上报}
|
||||
### 10.测试结果上报
|
||||
|
||||
测试成功后，除了 [目前还不清楚怎么测试 的测项之外的，其他所有的测试结果都为PASS，可以SUBMIT测试结果，否则请不要提交测试结果！！！]{style="color: rgb(255,0,0);"}
|
||||
<span style="color: rgb(255,0,0);">测试成功后，除了 <span style="color: rgb(153,51,0);">目前还不清楚怎么测试 的测项</span>之外的，其他所有的测试结果都为PASS，可以SUBMIT测试结果，否则请不要提交测试结果！！！</span>
|
||||
|
||||
\
|
||||
|
||||
@@ -701,4 +701,3 @@ MCU cfg tool 配置：
|
||||
\
|
||||
|
||||
\
|
||||
::::
|
||||
|
||||
@@ -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 <a href="https://developers.google.com/static/nearby/fast-pair/downloads/self-test-reports/Bluetooth_Classic_-_Google_Fast_Pair_Self_Test_Report_10142020.zip" class="external-link" rel="nofollow" style="">BlueTooth Classic</a>
|
||||
|
||||
@@ -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"}
|
||||
<a href="https://developers.google.com/nearby/fast-pair/fast-pair-certification-guideline#22_notification_popup_for_initial_pairing" class="external-link" rel="nofollow">Fast Pair 3.2 & 3.3 Certification Guidelines | Google for Developers</a>
|
||||
|
||||
Realtek内部整理文档：
|
||||
|
||||
[1 Initial Pairing and Subsequent Pairing Test Guideline(中文文档) - BT_Market - WIKI](https://wiki.realtek.com/pages/viewpage.action?pageId=288810503){rel="nofollow"}
|
||||
<a href="https://wiki.realtek.com/pages/viewpage.action?pageId=288810503" rel="nofollow">1 Initial Pairing and Subsequent Pairing Test Guideline(中文文档) - BT_Market - WIKI</a>
|
||||
|
||||
测试视频：
|
||||
|
||||
[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"}
|
||||
<a href="/download/attachments/948641817/initial_pairing.mp4?version=1&modificationDate=1759136017707&api=v2" data-linked-resource-container-id="948641817" data-linked-resource-container-version="3" data-linked-resource-content-type="video/mp4" data-linked-resource-default-alias="initial_pairing.mp4" data-linked-resource-id="948643166" data-linked-resource-type="attachment" data-linked-resource-version="1" data-nice-type="Multimedia">initial_pairing.mp4</a>
|
||||
|
||||
\
|
||||
:::
|
||||
|
||||
@@ -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"}
|
||||
<a href="https://developers.google.com/nearby/fast-pair/fast-pair-certification-guideline#4_feature_certification_criteria" class="external-link" rel="nofollow">https://developers.google.com/nearby/fast-pair/fast-pair-certification-guideline#4_feature_certification_criteria</a>
|
||||
|
||||
Realtek 内部整理文档：
|
||||
|
||||
[1 Extension Feature Test Guideline(中文文档) - BT_Market - WIKI](https://wiki.realtek.com/pages/viewpage.action?pageId=374584696){rel="nofollow"}
|
||||
<a href="https://wiki.realtek.com/pages/viewpage.action?pageId=374584696" rel="nofollow">1 Extension Feature Test Guideline(中文文档) - BT_Market - WIKI</a>
|
||||
|
||||
\
|
||||
|
||||
\
|
||||
:::
|
||||
|
||||
@@ -0,0 +1,5 @@
|
||||
# 1.provider支援LE audio + Legacy audio,不用单独过GFPS Legacy的认证?
|
||||
|
||||
答案：是的
|
||||
|
||||
|
||||
114
1.耳机支援LEA,手机也支援LEA,测试fail.md
Normal file
114
1.耳机支援LEA,手机也支援LEA,测试fail.md
Normal file
@@ -0,0 +1,114 @@
|
||||
# 1.耳机支援LEA,手机也支援LEA,测试fail
|
||||
|
||||
<a href="https://partnerissuetracker.corp.google.com/u/0/issues/419110816" class="external-link" rel="nofollow">https://partnerissuetracker.corp.google.com/u/0/issues/419110816</a>
|
||||
|
||||
<a href="https://jira.realtek.com/browse/BB2BUG-49617" class="external-link" rel="nofollow">[BB2BUG-49617] [BB2][RTL8763ESH/ROM][GMI][沃莱特][Harman][T530] [finder] 455-[LEA][Finder]EIK rotation Automated test fail - Jira</a>
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
<span style="color: rgb(32,33,36);">hi Mark:</span>\
|
||||
\
|
||||
<span style="color: rgb(32,33,36);">‘EIK Rotation’ test fail, can you help see the reason, thanks.</span>\
|
||||
\
|
||||
<span style="color: rgb(32,33,36);">test fail screen: Wed May 21 2025 10:06:37 GMT+0800 (中国标准时间).png</span>\
|
||||
\
|
||||
<span style="color: rgb(32,33,36);">20:01:31 phone rotating EIK and disconnect this ACL link,</span>\
|
||||
<span style="color: rgb(32,33,36);">when headsets receive disconnect command, The new EIK will take effect immediately after the BLE connection is terminated.</span>\
|
||||
<span style="color: rgb(32,33,36);">however headsets seems do not receive this disconnect command,</span>\
|
||||
\
|
||||
<span style="color: rgb(32,33,36);">we check logs in phone set:</span>\
|
||||
<span style="color: rgb(32,33,36);">//20:01:31.628 BluetoothGatt.disconnect</span>\
|
||||
<span style="color: rgb(32,33,36);">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 \]</span>\
|
||||
\
|
||||
<span style="color: rgb(32,33,36);">however headsets seems do not receive this disconnect command,</span>\
|
||||
<span style="color: rgb(32,33,36);">we also check air log, At 20:01:31, there was no disconnection command in the air log.</span>\
|
||||
\
|
||||
<span style="color: rgb(32,33,36);">Is it because the cmd to terminate the connection on the mobile phone was not sent out?</span>\
|
||||
\
|
||||
<span style="color: rgb(32,33,36);">Add the following information:</span>\
|
||||
<span style="color: rgb(32,33,36);">The disconnection at 20:01:53 was received by both the air log and the headphone log.</span>\
|
||||
<span style="color: rgb(32,33,36);">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 \]</span>\
|
||||
<span style="color: rgb(32,33,36);">thanks</span>
|
||||
|
||||
\
|
||||
|
||||
<span style="color: rgb(32,33,36);">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.</span>
|
||||
|
||||
\
|
||||
|
||||
\
|
||||
|
||||
Reassigned to <span class="bv2-email-with-profile-container"><span class="ng-star-inserted"><span class="user-avatar material ng-star-inserted"></span></span><span class="ng-star-inserted"><span class="ng-star-inserted"><a href="mailto:tonyysliu@google.com" class="external-link" rel="nofollow">tonyysliu@google.com</a></span></span></span>.
|
||||
|
||||
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
|
||||
|
||||
------------------------------------------------------------------------
|
||||
|
||||
<span rel="nofollow" style="text-decoration: none;"><span class="mention">@tonyysliu@google.com</span></span> - do you know whether FP or LEA stack could be creating/holding this connection?
|
||||
|
||||
<span style="color: rgb(32,33,36);">‘</span>
|
||||
|
||||
<span style="color: rgb(32,33,36);">’</span>
|
||||
|
||||
\
|
||||
|
||||
#### <a href="mailto:gmark@google.com" class="external-link" rel="nofollow">gmark@google.com</a><span class="ng-star-inserted"><span class="bv2-event-user-id ng-star-inserted" style="">\<gmark@<a href="http://google.com" class="external-link" rel="nofollow">google.com</a>\></span></span><span class="ng-star-inserted"><a href="https://partnerissuetracker.corp.google.com/u/0/issues/419110816#comment9" class="external-link" rel="nofollow" style="text-decoration: none;"><span> </span>#9</a></span><span class="bv2-event-info">May 28, 2025 06:11PM</span>
|
||||
|
||||
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.
|
||||
37
10+battery+HUN弹窗一直不消失，或者是一直不显示.md
Normal file
37
10+battery+HUN弹窗一直不消失，或者是一直不显示.md
Normal file
@@ -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**
|
||||
|
||||
\
|
||||
|
||||
**<span class="jira-issue resolved" jira-key="BBPRO2BUG-21515"> <a href="https://jira.realtek.com/browse/BBPRO2BUG-21515" class="jira-issue-key"><img src="https://jira.realtek.com/secure/viewavatar?size=xsmall&avatarId=10916&avatarType=issuetype" />BBPRO2BUG-21515</a> - <span class="summary">\[BBPro2\]\[RTL8773CO SDK\]\[沃莱特/飞利浦\]\[RHA\]耳机入盒关盖与手机断连后，手机上依旧显示耳机电量信息</span> <span class="aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf">Closed</span> </span>**
|
||||
|
||||
\
|
||||
@@ -0,0 +1,11 @@
|
||||
# 10 initial pair成功,LE ACL link存在,耳机再次进入Pairing mode,手机弹窗出来点击弹窗配对失败
|
||||
|
||||
<a href="https://jira.realtek.com/browse/BB2BUG-50358" class="external-link" rel="nofollow">[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</a>
|
||||
|
||||
<a href="https://partnerissuetracker.corp.google.com/u/0/issues/424368416" class="external-link" rel="nofollow">https://partnerissuetracker.corp.google.com/u/0/issues/424368416</a>
|
||||
|
||||
\
|
||||
|
||||
|
||||
|
||||
\
|
||||
@@ -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
|
||||
|
||||
|
||||
|
||||
<span class="jira-issue resolved" jira-key="BB2BUG-44729"> <a href="https://jira.realtek.com/browse/BB2BUG-44729" class="jira-issue-key"><img src="https://jira.realtek.com/secure/viewavatar?size=xsmall&avatarId=10916&avatarType=issuetype" />BB2BUG-44729</a> - <span class="summary">\[BB2\]\[RTL8763ESH/ROM\]\[GMI\]\[沃莱特\]\[Harman\]\[T135\] Google Finder (Ringing using the accessory non-owner service)项测试failed</span> <span class="aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf">Closed</span> </span>
|
||||
|
||||
修正： <a href="https://cn4soc.rtkbf.com/gerrit/c/HoneyComb/+/215092" class="external-link" rel="nofollow">https://cn4soc.rtkbf.com/gerrit/c/HoneyComb/+/215092</a>
|
||||
18
11+non-LEA动态切换到LEA.md
Normal file
18
11+non-LEA动态切换到LEA.md
Normal file
@@ -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
|
||||
|
||||
\
|
||||
|
||||
\
|
||||
@@ -0,0 +1,79 @@
|
||||
# 12 Pairing process error, Reason: Not receive UUID, Is connected:false
|
||||
|
||||
<span style="color: rgb(23,43,77);">目前遇到以下原因，可以逐一排查：</span>
|
||||
|
||||
<span style="color: rgb(23,43,77);"></span><style type="text/css">/**/
|
||||
div.rbtoc1777702176403 {padding: 0px;}
|
||||
div.rbtoc1777702176403 ul {margin-left: 0px;}
|
||||
div.rbtoc1777702176403 li {margin-left: 0px;padding-left: 0px;}
|
||||
|
||||
/**/</style>
|
||||
|
||||
<div class="toc-macro rbtoc1777702176403">
|
||||
|
||||
- [原因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.)
|
||||
|
||||
</div>
|
||||
|
||||
#### 原因1：可能是手机系统蓝牙出了问题，setting界面 system\>reset options\>reset Bluetooth & wifi , 然后重启手机试试看
|
||||
|
||||
<span style="color: rgb(23,43,77);"></span>
|
||||
|
||||
\
|
||||
|
||||
#### 原因2：如果设备端不支援LEA，和支援LEA的手机对测，发现手机不连legacy profile， 需要打开 legacy CTKD LE 的功能
|
||||
|
||||
<a href="https://wiki.realtek.com/pages/viewpage.action?pageId=908249385" rel="nofollow">1 GFPS legacy pair 搭配支援LEA手机不连 legacy profile(A2DP/HFP) - BT_Market - WIKI</a>
|
||||
|
||||
#### 原因3： 如果设备端支援LEA，和不支援LEA的手机对测，发现手机不连legacy profile， 需要关闭 legacy CTKD LE 的功能，这个是Google的bug，google 后续会给出修正
|
||||
|
||||
<a href="https://wiki.realtek.com/pages/viewpage.action?pageId=821520803" rel="nofollow">4 pixel6(android 12) 不连A2DP - BT_Market - WIKI</a>
|
||||
|
||||
\
|
||||
|
||||
\
|
||||
|
||||
<span style="color: rgb(23,43,77);"><a href="https://partnerissuetracker.corp.google.com/u/0/issues/443202640" class="external-link" rel="nofollow">https://partnerissuetracker.corp.google.com/u/0/issues/443202640</a></span>
|
||||
|
||||
<span style="color: rgb(23,43,77);"><a href="https://partnerissuetracker.corp.google.com/u/0/issues/445592517" class="external-link" rel="nofollow">https://partnerissuetracker.corp.google.com/u/0/issues/445592517</a></span>
|
||||
|
||||
<span style="color: rgb(23,43,77);"></span>
|
||||
|
||||
\
|
||||
|
||||
<span style="color: rgb(23,43,77);">手机没有来连legacy profile：</span>
|
||||
|
||||
<span style="color: rgb(23,43,77);">Line 32281: 0002123 09-05#11:00:37.169 194 0009843.085 </span><span class="error" style="color: rgb(23,43,77);">\[APP\]</span><span style="color: rgb(23,43,77);"> !\*\*connected: b2s, bd_addr 88::54::1F::10::0C::5F, profs 0x00000000</span>\
|
||||
<span style="color: rgb(23,43,77);">Line 34379: 0004221 09-05#11:00:38.529 169 0011221.541 </span><span class="error" style="color: rgb(23,43,77);">\[ENGAGE\]</span><span style="color: rgb(23,43,77);"> connected: b2s, bd_addr 88::54::1F::10::0C::5F, profs 0x00000000</span>\
|
||||
<span style="color: rgb(23,43,77);">Line 34741: 0004583 09-05#11:00:38.607 203 0011285.575 </span><span class="error" style="color: rgb(23,43,77);">\[ENGAGE\]</span><span style="color: rgb(23,43,77);"> connected: b2s, bd_addr 88::54::1F::10::0C::5F, profs 0x00000000</span>\
|
||||
<span style="color: rgb(23,43,77);">Line 35042: 0004883 09-05#11:00:38.700 095 0011358.903 </span><span class="error" style="color: rgb(23,43,77);">\[ENGAGE\]</span><span style="color: rgb(23,43,77);"> connected: b2s, bd_addr 88::54::1F::10::0C::5F, profs 0x00000000</span>
|
||||
|
||||
\
|
||||
|
||||
<a href="https://jira.realtek.com/browse/BB2BUG-52175" class="external-link" rel="nofollow">[BB2BUG-52175] [BB2][D-CUT][8763EKH][Harman][T530][v3.13.2.20+Test bin] Fast pair Validator APP测试，Personalized Name Update Test Fail - Jira</a>
|
||||
|
||||
<a href="https://jira.realtek.com/browse/BB2BUG-52173" class="external-link" rel="nofollow">[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</a>
|
||||
|
||||
<a href="https://jira.realtek.com/browse/BB2BUG-52194" class="external-link" rel="nofollow">[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</a>
|
||||
|
||||
\
|
||||
|
||||
#### 原因4：测试账号连的设备太多了，需要定期清除
|
||||
|
||||
##### 4.1 setting界面清掉所有的配对信息 <a href="https://wiki.realtek.com/pages/viewpage.action?pageId=401291585" rel="nofollow">1 gfps/finder 如何清除配对信息 - BT_Market - WIKI</a>
|
||||
|
||||
##### <span style="color: rgb(0,0,0);">**4.2 Go to `Settings > Google > All services > Devices > Saved devices：`**</span>
|
||||
|
||||
###### <span style="color: rgb(0,0,0);">** 4.2.1 Toggle off `Automatically saved devices`**</span>
|
||||
|
||||
###### <span style="color: rgb(0,0,0);">** 4.2.2 Wait for about 3 hours, toggling on again.**</span>
|
||||
|
||||
###### <span style="color: rgb(0,0,0);">** 4.2.3 Try to do the test again and see if this issue still happens.**</span>
|
||||
@@ -0,0 +1,5 @@
|
||||
# 12 Pairing process error. Reason: Only receive correct UUID from 1 address
|
||||
|
||||
|
||||
|
||||
<a href="https://jira.realtek.com/browse/BBPRO3BUG-27045" class="external-link" rel="nofollow">[BBPRO3BUG-27045] [BBPRO3][EVB][E Cut][PEGA_HA_v1.0.4_20251106][24110 testbin][GFPS][FastPair][LEA phone]Personalized Name Update 测试 fail - Jira</a>
|
||||
60
12+Pairing+process+error_+Reason_+Is+connected+false.md
Normal file
60
12+Pairing+process+error_+Reason_+Is+connected+false.md
Normal file
@@ -0,0 +1,60 @@
|
||||
# 12 Pairing process error: Reason: Is connected false
|
||||
|
||||
<span style="color: rgb(23,43,77);">目前遇到以下原因，可以逐一排查：</span>
|
||||
|
||||
<span style="color: rgb(23,43,77);"></span><style type="text/css">/**/
|
||||
div.rbtoc1777702181610 {padding: 0px;}
|
||||
div.rbtoc1777702181610 ul {margin-left: 0px;}
|
||||
div.rbtoc1777702181610 li {margin-left: 0px;padding-left: 0px;}
|
||||
|
||||
/**/</style>
|
||||
|
||||
<div class="toc-macro rbtoc1777702181610">
|
||||
|
||||
- [原因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.)
|
||||
|
||||
</div>
|
||||
|
||||
#### 原因1：可能是手机系统蓝牙出了问题，setting界面 system\>reset options\>reset Bluetooth & wifi , 然后重启手机试试看
|
||||
|
||||
<span style="color: rgb(23,43,77);"></span>
|
||||
|
||||
\
|
||||
|
||||
#### 原因2：如果设备端不支援LEA，和支援LEA的手机对测，发现手机不连legacy profile， 需要打开 legacy CTKD LE 的功能
|
||||
|
||||
<a href="https://wiki.realtek.com/pages/viewpage.action?pageId=908249385" rel="nofollow">1 GFPS legacy pair 搭配支援LEA手机不连 legacy profile(A2DP/HFP) - BT_Market - WIKI</a>
|
||||
|
||||
\
|
||||
|
||||
|
||||
|
||||
\
|
||||
|
||||
#### 原因3： 如果设备端支援LEA，和不支援LEA的手机对测，发现手机不连legacy profile， 需要关闭 legacy CTKD LE 的功能，这个是Google的bug，google 后续会给出修正
|
||||
|
||||
<a href="https://wiki.realtek.com/pages/viewpage.action?pageId=821520803" rel="nofollow">4 pixel6(android 12) 不连A2DP - BT_Market - WIKI</a>
|
||||
|
||||
\
|
||||
|
||||
#### 原因4：测试账号连的设备太多了，需要定期清除
|
||||
|
||||
##### 4.1 setting界面清掉所有的配对信息 <a href="https://wiki.realtek.com/pages/viewpage.action?pageId=401291585" rel="nofollow">1 gfps/finder 如何清除配对信息 - BT_Market - WIKI</a>
|
||||
|
||||
##### <span style="color: rgb(0,0,0);">**4.2 Go to `Settings > Google > All services > Devices > Saved devices：`**</span>
|
||||
|
||||
###### <span style="color: rgb(0,0,0);">** 4.2.1 Toggle off `Automatically saved devices`**</span>
|
||||
|
||||
###### <span style="color: rgb(0,0,0);">** 4.2.2 Wait for about 3 hours, toggling on again.**</span>
|
||||
|
||||
###### <span style="color: rgb(0,0,0);">** 4.2.3 Try to do the test again and see if this issue still happens.**</span>
|
||||
|
||||
\
|
||||
9
13+手机端显示名字为乱码.md
Normal file
9
13+手机端显示名字为乱码.md
Normal file
@@ -0,0 +1,9 @@
|
||||
# 13 手机端显示名字为乱码
|
||||
|
||||
请先帮忙按照如下wiki验证加解密算法，如果加解密算法没有问题 那就很可能是手机的问题
|
||||
|
||||
<a href="https://wiki.realtek.com/display/Bee1/gfps_lib_test" class="external-link" rel="nofollow" style="">https://wiki.realtek.com/display/Bee1/gfps_lib_test</a>
|
||||
|
||||
<span class="jira-issue resolved" jira-key="BUMBEEBUG-8940"> <a href="https://jira.realtek.com/browse/BUMBEEBUG-8940" class="jira-issue-key"><img src="https://jira.realtek.com/secure/viewavatar?size=xsmall&avatarId=10916&avatarType=issuetype" />BUMBEEBUG-8940</a> - <span class="summary">\[BBlite\]\[8773BFE\]\[1.8.3.4\]\[禾馳\]\[協宜\]\[帝品\]:GFPS连接后，蓝牙名处显示乱码</span> <span class="aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf">Closed</span> </span>
|
||||
|
||||
<span class="jira-issue resolved" jira-key="BBPRO3BUG-350"> <a href="https://jira.realtek.com/browse/BBPRO3BUG-350" class="jira-issue-key"><img src="https://jira.realtek.com/secure/viewavatar?size=xsmall&avatarId=10916&avatarType=issuetype" />BBPRO3BUG-350</a> - <span class="summary">\[BBPRO3\]\[EVB\]\[release_1220\]\[GFPS\]Naming测试之后，手机与RWS配对，RWS名字不对</span> <span class="aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf">Closed</span> </span>
|
||||
7
14+Initial+Pair+with+(XX_XX_)+fail.md
Normal file
7
14+Initial+Pair+with+(XX_XX_)+fail.md
Normal file
@@ -0,0 +1,7 @@
|
||||
# 14 Initial Pair with (XX:XX:) fail
|
||||
|
||||
+fail_77955b5d.jpg)
|
||||
|
||||
\
|
||||
|
||||
<a href="https://jira.realtek.com/browse/BBPRO3BUG-27064" class="external-link" rel="nofollow">[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</a>
|
||||
70
14+Initialize+fast+pair+service+failed.md
Normal file
70
14+Initialize+fast+pair+service+failed.md
Normal file
@@ -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 <a href="https://issuetracker.google.com/issues/444061781#comment7" class="external-link" rel="nofollow" style="text-decoration: none;">Comment #7</a>, 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 <a href="https://issuetracker.google.com/issues/409388435#comment6" class="external-link" rel="nofollow" style="text-decoration: none;">b/409388435#comment6</a>.
|
||||
|
||||
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.
|
||||
|
||||
\
|
||||
|
||||
<span style="color: rgb(255,0,0);">**最终找到原因是因为QC实验室的Google网络开了防火墙：**</span>
|
||||
|
||||
|
||||
|
||||
\
|
||||
|
||||
\
|
||||
|
||||
**<span style="color: rgb(255,0,0);">对比试验，测试过程中遇到该问题后，</span>**
|
||||
|
||||
**<span style="color: rgb(255,0,0);">在google-》所有服务-》设备中关闭自动保存设备选项后，大概率可以测试通过， </span>**
|
||||
|
||||
**<span style="color: rgb(255,0,0);">Fast pair validator 测试的时候可以关掉， 但是手动测试必须打开</span>**
|
||||
|
||||
\
|
||||
|
||||
\
|
||||
|
||||
|
||||
|
||||
<a href="https://partnerissuetracker.corp.google.com/u/0/issues/444061781" class="external-link" rel="nofollow">https://partnerissuetracker.corp.google.com/u/0/issues/444061781</a>
|
||||
|
||||
\
|
||||
|
||||
\
|
||||
|
||||
|
||||
|
||||
\
|
||||
|
||||
|
||||
|
||||
\
|
||||
|
||||
\
|
||||
|
||||
\
|
||||
|
||||
|
||||
|
||||
\
|
||||
7
14+subsequent+pairing手机提示+“无法连接，请尝试让设备进入配对模式”.md
Normal file
7
14+subsequent+pairing手机提示+“无法连接，请尝试让设备进入配对模式”.md
Normal file
@@ -0,0 +1,7 @@
|
||||
# 14 subsequent pairing手机提示 “无法连接，请尝试让设备进入配对模式”
|
||||
|
||||
原因很有可能是耳机不在connectable mode。
|
||||
|
||||
jira:
|
||||
|
||||
<span class="jira-issue" jira-key="BBPRO3BUG-390"> <a href="https://jira.realtek.com/browse/BBPRO3BUG-390" class="jira-issue-key"><img src="https://jira.realtek.com/secure/viewavatar?size=xsmall&avatarId=10916&avatarType=issuetype" />BBPRO3BUG-390</a> - <span class="summary">\[BBPRO3\]\[EVB\]\[release_1220\]\[GFPS\]Subsequent Pairing Failed</span> <span class="aui-lozenge aui-lozenge-subtle aui-lozenge-default jira-macro-single-issue-export-pdf">Preview</span> </span>
|
||||
55
15+GFPS+TWS+mode+测试ring功能的时候+++手机端只显示一个耳机设备.md
Normal file
55
15+GFPS+TWS+mode+测试ring功能的时候+++手机端只显示一个耳机设备.md
Normal file
@@ -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
|
||||
|
||||
<span class="ui-flex co bbe"></span>
|
||||
|
||||
\[17:45\] Barry Chu
|
||||
|
||||
看起來這段應該是沒甚麼問題 對嗎 ? 要請他們檢查 註冊時後填的資料嗎
|
||||
|
||||
\[17:45\] 董丹丹
|
||||
|
||||
手机端好像没有设置的地方，就是查我们的components
|
||||
|
||||
\[17:45\] 董丹丹
|
||||
|
||||
b2b是有连着的吗
|
||||
|
||||
\[17:46\] Barry Chu
|
||||
|
||||
應該是有連著的
|
||||
|
||||
\[17:46\] 董丹丹
|
||||
|
||||
是不是手机显示的问题呀
|
||||
|
||||
\[17:46\] Barry Chu
|
||||
|
||||
應該不是欸
|
||||
|
||||
他們用 BBLite 量產的就有看到 TWS
|
||||
|
||||
<span class="ui-provider vd b c d e f g h i j k l m n o p q r s t u v w x y z ab ac ae af ag ah ai aj ak"></span>
|
||||
|
||||
\[17:54\] 董丹丹
|
||||
|
||||
注册model id的时候 是填写的TWS 耳机还是 立体声耳机呀
|
||||
|
||||
\[17:54\] 董丹丹
|
||||
|
||||
是这个model id 都会显示一个设备吗，很可能是注册model id 的时候填写的信息不对
|
||||
|
||||
|
||||
|
||||
\
|
||||
50
15+app_gfps_check_receive_pair_req_+receive_pair_req+0.md
Normal file
50
15+app_gfps_check_receive_pair_req_+receive_pair_req+0.md
Normal file
@@ -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一样。
|
||||
|
||||
\
|
||||
|
||||
针对这种场景， 因为不会重新配对，所以<span style="color: rgb(0,51,102);">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//</span>
|
||||
|
||||
<span style="color: rgb(0,51,102);">但其实这种场景属于回连的情况，所以我们会在收到account key之后设置 gfps_db.receive_pair_req为 true</span>
|
||||
|
||||
\
|
||||
|
||||
<span style="color: rgb(0,51,102);"><a href="https://cn4soc.rtkbf.com/gerrit/c/HoneyComb/+/267318" class="external-link" rel="nofollow">APP-rws: modify gfps reconnect flow (267318) · Gerrit Code Review</a></span>
|
||||
|
||||
<span style="color: rgb(64,120,242);">app_gfps_cb_handle_accountkey:</span>
|
||||
|
||||
|
||||
|
||||
<table class="wrapped confluenceTable">
|
||||
<tbody>
|
||||
<tr>
|
||||
<th class="confluenceTh" scope="col"> 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<br />
|
||||
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<br />
|
||||
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<br />
|
||||
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<br />
|
||||
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<br />
|
||||
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<br />
|
||||
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<br />
|
||||
Line 29556: 0009449 11-17#13:56:53.591 077 0024703.813 [APP] !**gfps_hmac_sha256: 75 5F 52 FC 8D 10 B9 A7<br />
|
||||
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 <br />
|
||||
Line 29563: 0009456 11-17#13:56:53.591 085 0024705.619 [APP] !** app_gfps_personalized_name_send: is_send = 1<br />
|
||||
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<br />
|
||||
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<br />
|
||||
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<br />
|
||||
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<br />
|
||||
Line 29653: 0009546 11-17#13:56:53.667 179 0024787.072 [APP] !**gfps_get_owner_key_valid: 1 <br />
|
||||
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<br />
|
||||
Line 29655: 0009548 11-17#13:56:53.667 181 0024787.154 [APP] !**gfps_get_owner_key_valid: 1 <br />
|
||||
Line 29739: 0009632 11-17#13:56:53.668 009 0024792.569 [APP] !**app_gfps_account_key_remote_add</th>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
@@ -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 断线之后将<span style="color: rgb(228,86,73);">gfps_db</span><span style="color: rgb(56,58,66);">.</span><span style="color: rgb(228,86,73);">account_key_write_counts 设置成0</span>
|
||||
|
||||
|
||||
|
||||
<table class="confluenceTable">
|
||||
<tbody>
|
||||
<tr>
|
||||
<th class="confluenceTh" scope="col"><p> 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<br />
|
||||
11-19#11:41:21.302 178 0059462.890 [APP] !!!app_gfps_cb_handle_accountkey: account_key_write_counts 2</p>
|
||||
<p>//timer_id 2: APP_GFPS_TIMER_CHECK_RECEIVE_PAIR_REQ</p>
|
||||
<p>11-19#11:41:31.109 218 0069286.523 [APP] app_gfps_timer_timeout_cb: timer_id 2, timer_chann 0<br />
|
||||
11-19#11:41:31.109 219 0069286.613 [APP] app_ble_gap_disconnect: conn_id 0, disc_cause 19<br />
|
||||
11-19#11:41:31.109 220 0069286.656 [GAP] !**le_disconnect_with_reason: conn_id 0, reason 19</p></th>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
31
16+手机端测试响铃功能时，找不到响铃的按键.md
Normal file
31
16+手机端测试响铃功能时，找不到响铃的按键.md
Normal file
@@ -0,0 +1,31 @@
|
||||
# 16 手机端测试响铃功能时，找不到响铃的按键
|
||||
|
||||
正常手机端响铃按键在如下位置
|
||||
|
||||
|
||||
|
||||
\
|
||||
|
||||
有的客户测试的时候说是手机端UI上找不到 Ring Right或者是Ring Left的按键
|
||||
|
||||
很可能是客户注册model id的时候没有勾选Support Ring Device
|
||||
|
||||
|
||||
|
||||
\
|
||||
|
||||
<span class="jira-issue resolved" jira-key="BB2BUG-15892"> <a href="https://jira.realtek.com/browse/BB2BUG-15892" class="jira-issue-key"><img src="https://jira.realtek.com/secure/viewavatar?size=xsmall&avatarId=10916&avatarType=issuetype" />BB2BUG-15892</a> - <span class="summary">\[BB2\]\[C-CUT\]\[8763EF\]\[HARMAN\] BT520_GFPS_尋找耳機測試,可連線但無出現提示音</span> <span class="aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf">Closed</span> </span>
|
||||
|
||||
<span class="jira-issue resolved" jira-key="BB2BUG-17511"> <a href="https://jira.realtek.com/browse/BB2BUG-17511" class="jira-issue-key"><img src="https://jira.realtek.com/secure/viewavatar?size=xsmall&avatarId=10916&avatarType=issuetype" />BB2BUG-17511</a> - <span class="summary">\[BB2\]\[C-CUT\]\[8763EF\]\[HARMAN\] BT520_GFPS_Initial Pairing 彈窗</span> <span class="aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf">Closed</span> </span>
|
||||
|
||||
\
|
||||
|
||||
如果确定model id 配置的没有问题，并且有勾选 Support Ringing Device, 可以查看log看手机有没有来查询Active Components
|
||||
|
||||
|
||||
|
||||
以及Provided 回复的Active Components是否正确
|
||||
|
||||
|
||||
|
||||
<a href="https://wiki.realtek.com/pages/viewpage.action?pageId=1023058958" rel="nofollow">Retroactive Pair之后没办法使用响铃功能 - BT_Market - WIKI</a>
|
||||
3
2+BREDR+++GFPS+++Find+hub.md
Normal file
3
2+BREDR+++GFPS+++Find+hub.md
Normal file
@@ -0,0 +1,3 @@
|
||||
# 2 BREDR + GFPS + Find hub
|
||||
|
||||
该功能是通过GFPS快速配对BREDR， 并实现查找功能(类似苹果的findmy)
|
||||
23
2+Enable+new+feature+test+in+Validator.md
Normal file
23
2+Enable+new+feature+test+in+Validator.md
Normal file
@@ -0,0 +1,23 @@
|
||||
# 2 Enable new feature test in Validator
|
||||
|
||||
**<span style="color: rgb(32,33,36);"><span style="color: black;">Device actions which can be verified validator app: personalized name and retroactive pairing</span></span>**
|
||||
|
||||
<span style="color: rgb(32,33,36);"><span style="color: black;">**How to enable new feature test in validator**:</span></span>
|
||||
|
||||
<span style="color: rgb(32,33,36);"><span style="color: black;">安装adb:[adb安装及使用方法](/pages/viewpage.action?pageId=87464469) 该wiki上提供的adb版本太旧，会出现device offline的问题，下载最新的<a href="https://adbshell.com/downloads" class="external-link" rel="nofollow">https://adbshell.com/downloads</a></span></span>
|
||||
|
||||
<span style="color: rgb(32,33,36);">安装adb之后找到adb.exe所在的目录，在该目录下打开cmd命令行</span>
|
||||
|
||||
输入如下命令：
|
||||
|
||||
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，如下图红框所示。
|
||||
|
||||
界面如下图所示， 红框内是新增的测项：
|
||||
|
||||
\
|
||||
7
2+Scan_Connected+timing+测试fail.md
Normal file
7
2+Scan_Connected+timing+测试fail.md
Normal file
@@ -0,0 +1,7 @@
|
||||
# 2 Scan/Connected timing 测试fail
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
spec 说这个测项不是强制的，需要和google 确认
|
||||
35
2+UI显示设备已关联到其他人的账号.md
Normal file
35
2+UI显示设备已关联到其他人的账号.md
Normal file
@@ -0,0 +1,35 @@
|
||||
# 2 UI显示设备已关联到其他人的账号
|
||||
|
||||
<a href="https://jira.realtek.com/browse/BB2BUG-50316" class="external-link" rel="nofollow">[BB2BUG-50316] [BB2][RTL8763ESH/ROM][GMI][沃莱特/MINAMI][Harman][Pace][JBLES2-1895][Finder] 首次通过GFP连接的时候，跳过添加到Finder，取消配对耳机，重新配对的时候就无法添加耳机，现在已经被其他账号添加 - Jira</a>
|
||||
|
||||
点击 ”移除上一任所有者”， 之后再测试
|
||||
|
||||
|
||||
|
||||
如果移除上一任所有者之后，测试依然有问题， 麻烦请客户确认：开始测试之前耳机端一定要做factory reset 清除配对信息， 手机端也要清除配对信息 参考wiki <a href="https://wiki.realtek.com/pages/viewpage.action?pageId=401291585" rel="nofollow">17 gfps/finder 如何清除配对信息 - BT_Market - WIKI</a>
|
||||
|
||||
\
|
||||
|
||||
<a href="https://jira.realtek.com/browse/BB2BUG-50316" class="external-link" rel="nofollow">[BB2BUG-50316] [BB2][RTL8763ESH/ROM][GMI][沃莱特/MINAMI][Harman][Pace][JBLES2-1895][Finder] 首次通过GFP连接的时候，跳过添加到Finder，取消配对耳机，重新配对的时候就无法添加耳机，现在已经被其他账号添加 - Jira</a>
|
||||
|
||||
\
|
||||
|
||||
//因为没有做factory reset， 所以owner account key一直处于valid的状态
|
||||
|
||||
Line 16206: 0006198 06-11#13:34:18.321 213 0080765.751 <span class="error">\[APP\]</span> 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 <span class="error">\[APP\]</span> 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 <span class="error">\[APP\]</span> 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 <span class="error">\[APP\]</span> 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 <span class="error">\[APP\]</span> 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 <span class="error">\[APP\]</span> gfps_finder_rsp_beacon_provision_state: flag 3
|
||||
|
||||
//进而手机端显示已关联到其他人的账号
|
||||
|
||||
\
|
||||
63
2.+耳机不支援LEA,+手机支援LEA.md
Normal file
63
2.+耳机不支援LEA,+手机支援LEA.md
Normal file
@@ -0,0 +1,63 @@
|
||||
# 2. 耳机不支援LEA, 手机支援LEA
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
<span style="color: rgb(0,51,102);">**测试手机支援LEA, 开发者选项中将 Bypass Bluetooth LE Audio 选项关掉，然后重启手机，再重新测试，好像就不会遇到上面截图对应的问题了**</span>
|
||||
|
||||
<span style="color: rgb(255,0,0);">****</span>
|
||||
|
||||
<a href="https://jira.realtek.com/browse/BB2BUG-49617" class="external-link" rel="nofollow">[BB2BUG-49617] [BB2][RTL8763ESH/ROM][GMI][沃莱特][Harman][T530] [finder] 455-[LEA][Finder]EIK rotation Automated test fail - Jira</a>
|
||||
|
||||
<a href="https://partnerissuetracker.corp.google.com/u/0/issues/420766718" class="external-link" rel="nofollow">https://partnerissuetracker.corp.google.com/u/0/issues/420766718</a>
|
||||
|
||||
#### <span style="color: rgb(32,33,36);">hi Mark:</span>\
|
||||
\
|
||||
<span style="color: rgb(32,33,36);">‘EIK Rotation’ test fail, can you help see the reason, thanks.</span>\
|
||||
\
|
||||
<span style="color: rgb(32,33,36);">test fail screen: Fail_screen.jpg</span>\
|
||||
<span style="color: rgb(32,33,36);">18:24:26 BLE connected</span>\
|
||||
<span style="color: rgb(32,33,36);">After BLE is connected, there is no service discovery and no reading beacon parameters,</span>\
|
||||
<span style="color: rgb(32,33,36);">and the connection is immediately disconnected;</span>
|
||||
|
||||
\
|
||||
|
||||
\
|
||||
|
||||
#### <a href="mailto:gmark@google.com" class="external-link" rel="nofollow">gmark@google.com</a><span class="ng-star-inserted"><span class="bv2-event-user-id ng-star-inserted">\<gmark@<a href="http://google.com" class="external-link" rel="nofollow">google.com</a>\></span></span><span class="ng-star-inserted"><a href="https://partnerissuetracker.corp.google.com/u/0/issues/420766718#comment2" class="external-link" rel="nofollow" style="text-decoration: none;"><span> </span>#2</a></span><span class="bv2-event-info">May 28, 2025 03:40PM</span>
|
||||
|
||||
Reassigned to <span class="bv2-email-with-profile-container"><span class="ng-star-inserted"><span class="user-avatar material ng-star-inserted"></span></span><span class="ng-star-inserted"><span class="ng-star-inserted"><a href="mailto:android-bluetooth@google.com" class="external-link" rel="nofollow">android-bluetooth@google.com</a></span></span></span>.
|
||||
|
||||
**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)
|
||||
13
2.1+!!!gfps_handle_char_kbp_+failed,+result+3.md
Normal file
13
2.1+!!!gfps_handle_char_kbp_+failed,+result+3.md
Normal file
@@ -0,0 +1,13 @@
|
||||
# 2.1 !!!gfps_handle_char_kbp: failed, result 3
|
||||
|
||||
<a href="/download/attachments/374581806/COM8_2023-05-24_10-51-54.log?version=1&modificationDate=1684898303897&api=v2" data-linked-resource-container-id="374581806" data-linked-resource-container-version="2" data-linked-resource-content-type="text/plain" data-linked-resource-default-alias="COM8_2023-05-24_10-51-54.log" data-linked-resource-id="374581869" data-linked-resource-type="attachment" data-linked-resource-version="1" data-nice-type="Text File">COM8_2023-05-24_10-51-54.log</a>
|
||||
|
||||
|
||||
|
||||
原因是 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 输入错误。
|
||||
|
||||
|
||||
49
2.1+Project+工程enable对应功能.md
Normal file
49
2.1+Project+工程enable对应功能.md
Normal file
@@ -0,0 +1,49 @@
|
||||
# 2.1 Project 工程enable对应功能
|
||||
|
||||
<span style="color: rgb(166,38,164);">app_flags.h 里面找到 <span style="color: rgb(64,120,242);">CONFIG_REALTEK_GFPS_XXX 相关的宏并按照以下信息配置</span>：</span>
|
||||
|
||||
<span style="color: rgb(166,38,164);">\#define</span><span style="color: rgb(56,58,66);"> </span><span style="color: rgb(64,120,242);">CONFIG_REALTEK_GFPS_FEATURE_SUPPORT</span><span style="color: rgb(56,58,66);"> </span><span style="color: rgb(152,104,1);">1</span>\
|
||||
<span style="color: rgb(166,38,164);">\#define</span><span style="color: rgb(56,58,66);"> </span><span style="color: rgb(64,120,242);">CONFIG_REALTEK_GFPS_LE_DEVICE_SUPPORT</span><span style="color: rgb(56,58,66);"> (0 && </span><span style="color: rgb(64,120,242);">CONFIG_REALTEK_GFPS_FEATURE_SUPPORT</span><span style="color: rgb(56,58,66);">)</span>\
|
||||
<span style="color: rgb(166,38,164);">\#define</span><span style="color: rgb(56,58,66);"> </span><span style="color: rgb(64,120,242);">CONFIG_REALTEK_GFPS_SASS_SUPPORT</span><span style="color: rgb(56,58,66);"> (0 && </span><span style="color: rgb(64,120,242);">CONFIG_REALTEK_GFPS_FEATURE_SUPPORT</span><span style="color: rgb(56,58,66);">)</span>\
|
||||
<span style="color: rgb(166,38,164);">\#define</span><span style="color: rgb(56,58,66);"> </span><span style="color: rgb(64,120,242);">CONFIG_REALTEK_GFPS_FINDER_SUPPORT</span><span style="color: rgb(56,58,66);"> (1 && </span><span style="color: rgb(64,120,242);">CONFIG_REALTEK_GFPS_FEATURE_SUPPORT</span><span style="color: rgb(56,58,66);">)</span>
|
||||
|
||||
<span style="color: rgb(56,58,66);">GFPS依赖的其他的模块：</span>
|
||||
|
||||
\#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
|
||||
|
||||
\
|
||||
|
||||
<span style="color: rgb(152,104,1);">Note:</span>
|
||||
|
||||
<span style="color: rgb(152,104,1);">有的IC宏的名字是 GFPS_XXX, <span style="color: rgb(166,38,164);">app_flags.h 里面找到 <span style="color: rgb(64,120,242);">GFPS_XXX 相关的宏并按照以下信息配置</span>：</span></span>
|
||||
|
||||
<span style="color: rgb(166,38,164);">\#define</span><span style="color: rgb(56,58,66);"> </span><span style="color: rgb(64,120,242);">GFPS_FEATURE_SUPPORT</span><span style="color: rgb(56,58,66);"> </span><span style="color: rgb(152,104,1);">1</span>\
|
||||
<span style="color: rgb(166,38,164);">\#define</span><span style="color: rgb(56,58,66);"> </span><span style="color: rgb(64,120,242);">GFPS_LE_DEVICE_SUPPORT</span><span style="color: rgb(56,58,66);"> (0 && </span><span style="color: rgb(64,120,242);">GFPS_FEATURE_SUPPORT</span><span style="color: rgb(56,58,66);">)</span>\
|
||||
<span style="color: rgb(166,38,164);">\#define</span><span style="color: rgb(56,58,66);"> </span><span style="color: rgb(64,120,242);">GFPS_SASS_SUPPORT</span><span style="color: rgb(56,58,66);"> (0 && </span><span style="color: rgb(64,120,242);">GFPS_FEATURE_SUPPORT</span><span style="color: rgb(56,58,66);">)</span>\
|
||||
<span style="color: rgb(166,38,164);">\#define</span><span style="color: rgb(56,58,66);"> </span><span style="color: rgb(64,120,242);">GFPS_FINDER_SUPPORT</span><span style="color: rgb(56,58,66);"> (1 && </span><span style="color: rgb(64,120,242);">GFPS_FEATURE_SUPPORT</span><span style="color: rgb(56,58,66);">)</span>
|
||||
|
||||
<span style="color: rgb(56,58,66);">GFPS依赖的其他的模块：</span>
|
||||
|
||||
\#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
|
||||
@@ -0,0 +1,3 @@
|
||||
# 2.2 Provider send kbp rsp but seeker disconnect BLE link
|
||||
|
||||
<span class="jira-issue resolved" jira-key="BB2BUG-20554"> <a href="https://jira.realtek.com/browse/BB2BUG-20554" class="jira-issue-key"><img src="https://jira.realtek.com/secure/viewavatar?size=xsmall&avatarId=10916&avatarType=issuetype" />BB2BUG-20554</a> - <span class="summary">\[BB2\]\[8773ESL\]\[v3.13.0.8\]\[GFPS\]\[LE Audio\] 手机与耳机配对失败，手机端提示Couldn't connect</span> <span class="aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf">Closed</span> </span>
|
||||
1
2.2+测试环境搭建.md
Normal file
1
2.2+测试环境搭建.md
Normal file
@@ -0,0 +1 @@
|
||||
# 2.2 测试环境搭建
|
||||
306
2.2.1+设备端环境搭建.md
Normal file
306
2.2.1+设备端环境搭建.md
Normal file
@@ -0,0 +1,306 @@
|
||||
# 2.2.1 设备端环境搭建
|
||||
|
||||
<style type="text/css">/**/
|
||||
div.rbtoc1777700930417 {padding: 0px;}
|
||||
div.rbtoc1777700930417 ul {margin-left: 0px;}
|
||||
div.rbtoc1777700930417 li {margin-left: 0px;padding-left: 0px;}
|
||||
|
||||
/**/</style>
|
||||
|
||||
<div class="toc-macro rbtoc1777700930417">
|
||||
|
||||
- [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广播需要配置以下信息：)
|
||||
|
||||
</div>
|
||||
|
||||
### 1 MCUConfigTool 配置
|
||||
|
||||
#### 1.1 General 页面 : 不勾选 Enable auto power off, <span style="letter-spacing: -0.003em;">不勾选 Enable pairing timeout </span>修改为了便于GFPS测试，GFPS 测试的时候或者是过认证的时候需要修改， **<span style="color: rgb(255,0,0);">量产时可以考虑不修改。</span>**
|
||||
|
||||
|
||||
|
||||
#### 1.2 General 页面 : Discoverable in standby mode 设置成disable。<span style="color: rgb(255,0,0);">**强制要求必须修改**</span>
|
||||
|
||||
<span style="color: rgb(255,0,0);">**Note**:</span>
|
||||
|
||||
GFPS 耳机第一次和一只手机配对成功之后(initial pairing 成功)，就会进入 subsequent pairing mode。
|
||||
|
||||
所以initial pairing 成功之后，不管耳机是进入idle mode 还是进入connectable mode(multilink 支持)，都不应该再设置成discoverable。
|
||||
|
||||
|
||||
|
||||
#### 1.3 General 页面: 勾选 Non-discoverable when linkback <span style="color: rgb(255,0,0);">**强制要求必须修改**</span>
|
||||
|
||||
linkback模式下DUT不应该discoverable，不然手机端会一直弹配对窗口。<span style="color: rgb(255,0,0);"> </span>
|
||||
|
||||
\
|
||||
|
||||
|
||||
|
||||
#### 1.4 勾选Multi-link support, 并且不要勾选 Enter pairing state while only available device is connected <span style="color: rgb(255,0,0);">**强制要求必须修改**</span>
|
||||
|
||||
下面红框里的**<span style="color: rgb(255,0,0);">不可以勾选</span> **<span style="color: rgb(0,0,0);letter-spacing: 0.0px;">不然battery HUN测试可能测不过，</span> **<span class="jira-issue" client-id="SINGLE_2d885edc-676b-3349-9548-fe5648c9d8cd_948642484_2c9082e76519d09101657ff5cfb3003b" jira-key="BBPRO2BUG-21515"> <a href="https://jira.realtek.com/browse/BBPRO2BUG-21515" class="jira-issue-key"><span class="aui-icon aui-icon-wait issue-placeholder"></span>BBPRO2BUG-21515</a> - <span class="summary">Getting issue details...</span> <span class="aui-lozenge aui-lozenge-subtle aui-lozenge-default issue-placeholder">STATUS</span> </span>**
|
||||
|
||||
|
||||
|
||||
#### 1.5 Third Party页面配置GFPS参数
|
||||
|
||||
在Third Party页面配置GFPS参数，详细信息参考 <a href="https://wiki.realtek.com/pages/viewpage.action?pageId=158870786" rel="nofollow">mcu cfg tool中 GFPS 各配置项的含义 - BT_Market - WIKI</a>
|
||||
|
||||
|
||||
|
||||
下面是RTK已通过认证的Module ID
|
||||
|
||||
[认证结果及认证通过的model_id 和key](/pages/viewpage.action?pageId=204620689)
|
||||
|
||||
#### 1.6 配置GFPS findme voice prompt tone
|
||||
|
||||
<a href="#" class="unresolved">gfps_findme.wav</a>
|
||||
|
||||
自行选择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测试环境搭建(<span style="color: rgb(255,0,0);">只有TWS耳机需要做GFPS battery测试，single mode 不需要测试</span>)
|
||||
|
||||
Note：
|
||||
|
||||
测试battery的时候需要搭配充电盒
|
||||
|
||||
#### 2.1.mcu config tool 配置：
|
||||
|
||||
##### 2.1.1 HW Feature 模块
|
||||
|
||||
勾选Charger功能：
|
||||
|
||||
|
||||
|
||||
勾选支持充电盒功能，<span style="color: rgb(255,0,0);">注意如果充电盒image烧录的是20ms,下面红色框中的40ms也要改成20ms,这个要和充电盒image匹配的。</span>
|
||||
|
||||
<span style="color: rgb(255,0,0);">如果充电盒image 烧录的是40ms：</span>
|
||||
|
||||
|
||||
|
||||
如果充电盒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
|
||||
|
||||
<a href="/download/attachments/139180496/GFPS_Left.rcfg?version=1&modificationDate=1636711808317&api=v2" data-linked-resource-container-id="139180496" data-linked-resource-container-version="20" data-linked-resource-content-type="application/octet-stream" data-linked-resource-default-alias="GFPS_Left.rcfg" data-linked-resource-id="205658521" data-linked-resource-type="attachment" data-linked-resource-version="1">GFPS_Left.rcfg</a>
|
||||
|
||||
<a href="/download/attachments/139180496/GFPS_Right.rcfg?version=1&modificationDate=1636711808877&api=v2" data-linked-resource-container-id="139180496" data-linked-resource-container-version="20" data-linked-resource-content-type="application/octet-stream" data-linked-resource-default-alias="GFPS_Right.rcfg" data-linked-resource-id="205658522" data-linked-resource-type="attachment" data-linked-resource-version="1">GFPS_Right.rcfg</a>
|
||||
|
||||
### <span style="color: rgb(255,0,0);">**3 Find Hub测试环境搭建：**</span>
|
||||
|
||||
#### 3.1 每一轮测试开始之前耳机端需要做factory reset操作，测试中请不要做factory reset。原因如下：[8 手机端清掉配对信息之后，耳机端也要做factory reset，不然finder功能用不起来](/pages/viewpage.action?pageId=350190807)
|
||||
|
||||
#### <span style="color: rgb(255,0,0);">3.2 finder 所有功能测试完成之后，测试手机归还QC之前，手机端一定要清掉配对信息，不然过段时间再测试的时候可能会有问题，手机log会提示设备已经有owner了，会比较麻烦，建议测试完成之后一定要先把手机端的配对信息全清掉</span> [1 gfps/finder 如何清除配对信息](/pages/viewpage.action?pageId=401291585)
|
||||
|
||||
#### 3.3 MCU cfg tool中model id和key的信息要换成支持finder 的model id 和key的信息，测试账号必须只能使用某个固定的Google账号，暂时还不可以使用多个Google账号进行测试。
|
||||
|
||||
<span style="color: rgb(255,0,0);"> 内部测试model id 和Company name, Device name 和 Device type 请参考</span> [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广播需要配置以下信息：
|
||||
|
||||
详细信息可以参考<a href="https://wiki.realtek.com/pages/viewpage.action?pageId=158870786" rel="nofollow">mcu cfg tool中 GFPS 各配置项的含义 - BT_Market - WIKI</a> 中的: ”9. GFPS Finder相关配置信息描述”
|
||||
|
||||
|
||||
248
2.2.2+手机端环境搭建.md
Normal file
248
2.2.2+手机端环境搭建.md
Normal file
@@ -0,0 +1,248 @@
|
||||
# 2.2.2 手机端环境搭建
|
||||
|
||||
<style type="text/css">/**/
|
||||
div.rbtoc1777700936580 {padding: 0px;}
|
||||
div.rbtoc1777700936580 ul {margin-left: 0px;}
|
||||
div.rbtoc1777700936580 li {margin-left: 0px;padding-left: 0px;}
|
||||
|
||||
/**/</style>
|
||||
|
||||
<div class="toc-macro rbtoc1777700936580">
|
||||
|
||||
- [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选项关掉，然后重启手机)
|
||||
|
||||
</div>
|
||||
|
||||
\
|
||||
|
||||
该测试至少要准备两只手机。测试手机建议使用Google pixel手机，请<span style="color: rgb(255,0,0);">**务必确保**</span>手机端有打开开发者选项 <a href="https://developer.android.com/studio/debug/dev-options?hl=zh-cn" class="external-link" rel="nofollow">https://developer.android.com/studio/debug/dev-options?hl=zh-cn</a>
|
||||
|
||||
### GFPS 环境搭建
|
||||
|
||||
#### 1.手机需要连接google网络
|
||||
|
||||
该网络必须可以登陆google的网站，在测试前请先测试一下是否可以登录google的网站(<span style="color: rgb(255,0,0);">**建议试试能不能打开youtube之类的**</span>）。
|
||||
|
||||
#### 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(<span style="color: rgb(255,0,0);">内部</span><span style="color: rgb(255,0,0);">账号(不可给客户)：</span>
|
||||
|
||||
<span style="color: rgb(255,0,0);"><span style="color: rgb(0,0,0);"><span style="color: rgb(255,0,0);"><span style="color: rgb(23,43,77);"><span style="color: rgb(0,0,0);"><span style="color: rgb(255,0,0);">Fast Pair Validator 测试 请使用 </span></span></span></span></span></span><span style="color: rgb(255,0,0);"><a href="mailto:realsilbt8888@gmail.com" class="external-link" rel="nofollow">realsilbt8888@gmail.com</a><span style="color: rgb(23,43,77);"> </span><span style="color: rgb(23,43,77);"> </span></span>
|
||||
|
||||
<span style="color: rgb(255,0,0);"><span style="color: rgb(23,43,77);">手动测试账号请参考 <span style="color: rgb(255,0,0);"><a href="https://wiki.realtek.com/pages/viewpage.action?pageId=394285307" rel="nofollow">Google 账号 - BT_Market - WIKI (realtek.com)</a> </span></span></span>
|
||||
|
||||
#### 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”
|
||||
|
||||
|
||||
|
||||
<a href="https://developer.android.com/studio/debug/dev-options?hl=zh-cn" class="external-link" rel="nofollow">https://developer.android.com/studio/debug/dev-options?hl=zh-cn</a>
|
||||
|
||||
#### <span class="devsite-heading">10.Check Google Play Service version</span>
|
||||
|
||||
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).
|
||||
|
||||
|
||||
|
||||
\
|
||||
|
||||
\
|
||||
|
||||
#### **<span style="color: rgb(255,0,0);">11.注册成为google beta tester（内部测试账号已经注册过了，这一步不需要，如果是客户自己注册的Google账号，需要提醒客户check）</span>**
|
||||
|
||||
Sign up for the Google Play services beta program <a href="https://play.google.com/apps/testing/com.google.android.gms" class="external-link" rel="nofollow">https://play.google.com/apps/testing/com.google.android.gms</a>
|
||||
|
||||
join the Android Beta group at <a href="https://www.google.com/android/beta" class="external-link" rel="nofollow"><span>https://www.google.com/android/beta</span></a> to get latest update via OTA
|
||||
|
||||
Finder/Find Hub testing program please Navigate to <a href="https://play.google.com/apps/testing/com.google.android.apps.adm" class="external-link" rel="nofollow">https://play.google.com/apps/testing/com.google.android.apps.adm</a>
|
||||
|
||||
\
|
||||
|
||||
可以登陆Google账号之后在以下链接查看是否有添加成功：<a href="https://groups.google.com/my-groups" class="external-link" rel="nofollow">我的群组</a>
|
||||
|
||||
|
||||
|
||||
需要注意的是：
|
||||
|
||||
|
||||
|
||||
如果没有权限添加，FAE需要联系YingTsung (YT) Lin， 请他发邮件给Google， 让Google把客户注册的Google账号添加到Google的Test group。
|
||||
|
||||
\
|
||||
|
||||
### Find hub 环境搭建
|
||||
|
||||
#### <span style="color: rgb(0,0,0);">1. </span>The Google <a href="https://play.google.com/apps/testing/com.google.android.apps.adm" class="external-link" rel="nofollow">Find Hub App</a> must be installed and updated to the latest Beta version.
|
||||
|
||||
确认手机是否安装<span style="color: rgb(255,0,0);"> Find Hub,</span><span style="color: rgb(0,0,0);"> 图标如下图：</span>
|
||||
|
||||
<span style="color: rgb(153,51,0);"> </span><span style="color: rgb(153,51,0);"></span>
|
||||
|
||||
##### 1.1 如果没有安装：
|
||||
|
||||
去 Play Store/应用商店 下载<span style="color: rgb(0,0,0);">Find Hub</span><span style="color: rgb(0,0,0);">并且安装。</span>
|
||||
|
||||
##### 1.2 如果已经安装：
|
||||
|
||||
确认安装的是否是最新版。不是最新版，请手动升级到最新版。确认步骤如下：
|
||||
|
||||
###### 1.2.1 长按 <span style="color: rgb(0,0,0);">Find hub </span>图标，会看到App info
|
||||
|
||||
|
||||
|
||||
###### 1.2.2 点击App info,会看到 App details
|
||||
|
||||
|
||||
|
||||
###### 1.2.3 点击App details,会看到以下页面，如果有新版本请手动更新到最新的版本。如果是beta版本则不需要更新，系统会自动帮忙更新。
|
||||
|
||||
|
||||
|
||||
\
|
||||
|
||||
#### <span style="color: rgb(153,51,0);">2.</span>*"Use Find Hub"* must be enabled under *"Settings \> Google \> Find Hub"*.
|
||||
|
||||
<span style="color: rgb(153,51,0);"></span>
|
||||
|
||||
<span style="color: rgb(153,51,0);"></span>
|
||||
|
||||
<span style="color: rgb(153,51,0);">or</span>
|
||||
|
||||
<span style="color: rgb(153,51,0);"><a href="/download/attachments/948642517/%E6%89%8B%E6%9C%BA%E7%AB%AF%E6%89%93%E5%BC%80%20finder%E5%8A%9F%E8%83%BD.mp4?version=1&modificationDate=1759132789297&api=v2" data-linked-resource-container-id="948642517" data-linked-resource-container-version="8" data-linked-resource-content-type="video/mp4" data-linked-resource-default-alias="手机端打开 finder功能.mp4" data-linked-resource-id="948642789" data-linked-resource-type="attachment" data-linked-resource-version="1" data-nice-type="Multimedia">手机端打开 finder功能.mp4</a></span>
|
||||
|
||||
\
|
||||
|
||||
#### *3 "Find your offline devices"* must be set to *"With network in all areas"* under *"Settings \> Google \> Find Hub"*.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
\
|
||||
|
||||
\
|
||||
|
||||
#### <span style="color: rgb(153,51,0);">4.“Scan for nearby devices” and “Include debug results” must be enabled under “Settings\> Google \> Devices and sharing \> Devices”.</span>
|
||||
|
||||
<span style="color: rgb(153,51,0);"></span>
|
||||
|
||||
\
|
||||
|
||||
#### <span style="color: rgb(153,51,0);">5.Should be connected to the google Internet and have Bluetooth and Location turned on in Settings.</span>
|
||||
|
||||
<span style="color: rgb(153,51,0);"></span>
|
||||
|
||||
\
|
||||
|
||||
#### **6 测试账号需要加入(<span style="color: rgb(255,0,0);">内部测试账号已加入，qc测试不需要关心，FAE需要提醒客户自查</span>)**
|
||||
|
||||
Google Play services testing program： Navigate to <a href="https://play.google.com/apps/testing/com.google.android.gms" class="external-link" rel="nofollow">https://play.google.com/apps/testing/com.google.android.gms</a>
|
||||
|
||||
Find My Device testing program： Navigate to <a href="https://play.google.com/apps/testing/com.google.android.apps.adm" class="external-link" rel="nofollow">https://play.google.com/apps/testing/com.google.android.apps.adm</a>.
|
||||
|
||||
如果没有权限，需要联系Google帮忙添加账号权限。
|
||||
|
||||
\
|
||||
|
||||
#### <span style="color: rgb(0,51,102);">**7 如果测试手机支援LEA, 开发者选项中将 Bypass Bluetooth LE Audio 选项关掉，然后重启手机**</span>
|
||||
|
||||
<span style="color: rgb(255,0,0);">****</span>
|
||||
|
||||
\
|
||||
|
||||
\
|
||||
326
2.2.3+Fast+Pair+Validator+环境搭建.md
Normal file
326
2.2.3+Fast+Pair+Validator+环境搭建.md
Normal file
@@ -0,0 +1,326 @@
|
||||
# 2.2.3 Fast Pair Validator 环境搭建
|
||||
|
||||
<span style="color: rgb(0,0,0);"></span><style type="text/css">/**/
|
||||
div.rbtoc1777700943047 {padding: 0px;}
|
||||
div.rbtoc1777700943047 ul {margin-left: 0px;}
|
||||
div.rbtoc1777700943047 li {margin-left: 0px;padding-left: 0px;}
|
||||
|
||||
/**/</style>
|
||||
|
||||
<div class="toc-macro rbtoc1777700943047">
|
||||
|
||||
- [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测试完成。测试结果提交：)
|
||||
|
||||
</div>
|
||||
|
||||
### <span style="color: rgb(0,0,0);">1 搭建手机端的测试环境</span>
|
||||
|
||||
测试手机建议使用Google pixel手机，请<span style="color: rgb(255,0,0);">**务必确保**</span>手机端有打开开发者选项 <a href="https://developer.android.com/studio/debug/dev-options?hl=zh-cn" class="external-link" rel="nofollow">https://developer.android.com/studio/debug/dev-options?hl=zh-cn</a>
|
||||
|
||||
\
|
||||
|
||||
#### 1.1 手机需要连接google网络
|
||||
|
||||
该网络必须可以登陆google的网站，在测试前请先测试一下是否可以登录google的网站(<span style="color: rgb(255,0,0);">**建议试试能不能打开youtube之类的**</span>）。
|
||||
|
||||
#### 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(<span style="color: rgb(255,0,0);">内部</span><span style="color: rgb(255,0,0);">账号(不可给客户)：</span>
|
||||
|
||||
<span style="color: rgb(255,0,0);"><span style="color: rgb(0,0,0);"><span style="color: rgb(255,0,0);"><span style="color: rgb(23,43,77);"><span style="color: rgb(0,0,0);"><span style="color: rgb(255,0,0);">Fast Pair Validator 测试 请使用 </span></span></span></span></span></span><span style="color: rgb(255,0,0);"><a href="mailto:realsilbt8888@gmail.com" class="external-link" rel="nofollow">realsilbt8888@gmail.com</a><span style="color: rgb(23,43,77);"> </span><span style="color: rgb(23,43,77);"> </span></span>
|
||||
|
||||
<span style="color: rgb(255,0,0);"><span style="color: rgb(23,43,77);">手动测试账号请参考 <span style="color: rgb(255,0,0);"><a href="https://wiki.realtek.com/pages/viewpage.action?pageId=394285307" rel="nofollow">Google 账号 - BT_Market - WIKI (realtek.com)</a> </span></span></span>
|
||||
|
||||
#### 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
|
||||
|
||||
**<span style="color: rgb(255,0,0);">Note: 只有realsilbt8888的账号需要关掉 Automatically save devices， 其他手动测试的账号Automatically save devices需要打开</span>**
|
||||
|
||||
|
||||
|
||||
\
|
||||
|
||||
#### 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”
|
||||
|
||||
|
||||
|
||||
<a href="https://developer.android.com/studio/debug/dev-options?hl=zh-cn" class="external-link" rel="nofollow">https://developer.android.com/studio/debug/dev-options?hl=zh-cn</a>
|
||||
|
||||
#### <span class="devsite-heading">1.10 Check Google Play Service version</span>
|
||||
|
||||
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).
|
||||
|
||||
|
||||
|
||||
\
|
||||
|
||||
\
|
||||
|
||||
#### **<span style="color: rgb(255,0,0);">1.11 注册成为google beta tester（内部测试账号已经注册过了，这一步不需要，如果是客户自己注册的Google账号，需要提醒客户check）</span>**
|
||||
|
||||
Sign up for the Google Play services beta program\
|
||||
<a href="https://play.google.com/apps/testing/com.google.android.gms" class="external-link" rel="nofollow">https://play.google.com/apps/testing/com.google.android.gms</a>
|
||||
|
||||
join the Android Beta group at <a href="https://www.google.com/android/beta" class="external-link" rel="nofollow"><span>https://www.google.com/android/beta</span></a> to get latest update via OTA
|
||||
|
||||
Finder/Find Hub testing program please Navigate to <a href="https://play.google.com/apps/testing/com.google.android.apps.adm" class="external-link" rel="nofollow">https://play.google.com/apps/testing/com.google.android.apps.adm</a>
|
||||
|
||||
如果没有权限添加，FAE需要联系YingTsung (YT) Lin， 请他发邮件给Google， 让Google把客户注册的Google账号添加到Google的Test group。
|
||||
|
||||
可以登陆Google账号之后在以下链接查看是否有添加成功：<a href="https://groups.google.com/my-groups" class="external-link" rel="nofollow">我的群组</a>
|
||||
|
||||
|
||||
|
||||
需要注意的是：
|
||||
|
||||
|
||||
|
||||
### **<span style="color: rgb(153,51,0);">2 Fast Pair Validator APP安装</span>**
|
||||
|
||||
确认手机是否安装 Fast Pair Validator APP
|
||||
|
||||
<span style="color: rgb(0,0,0);">Fast pair validator app 图标如下图：</span>
|
||||
|
||||
<span style="color: rgb(153,51,0);"></span>
|
||||
|
||||
如果没有安装:
|
||||
|
||||
去 Play Store/应用商店 下载 <span style="color: rgb(0,0,0);">Fast Pair Validator APP并且安装。</span>
|
||||
|
||||
如果已经安装:
|
||||
|
||||
确认安装的是否是最新版。不是最新版，请手动升级到最新版。确认步骤如下：
|
||||
|
||||
长按 Fast Pair Validator 图标，会看到App info
|
||||
|
||||
|
||||
|
||||
点击App info,会看到App details
|
||||
|
||||
|
||||
|
||||
点击App details,会看到以下页面，如果有新版本请手动更新到最新的版本。如果是beta版本则不需要更新，系统会自动帮忙更新。
|
||||
|
||||
|
||||
|
||||
### <span style="color: rgb(153,51,0);">3 </span><span style="color: rgb(153,51,0);">Enable fast pair validator app中的测项</span>
|
||||
|
||||
#### <span style="color: rgb(32,33,36);"><span style="color: black;">3.1 安装adb:</span></span>
|
||||
|
||||
<span style="color: rgb(32,33,36);"><span style="color: black;"><a href="https://wiki.realtek.com/pages/viewpage.action?pageId=87464469" rel="nofollow">adb安装及使用方法</a> 该wiki上提供的adb版本太旧，会出现device offline的问题，下载最新的<a href="https://adbshell.com/downloads" class="external-link" rel="nofollow">https://adbshell.com/downloads</a></span></span>
|
||||
|
||||
<span style="color: rgb(32,33,36);">安装adb之后找到adb.exe所在的目录，在该目录下打开cmd命令行</span>
|
||||
|
||||
#### 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
|
||||
|
||||
\
|
||||
|
||||
### <span style="color: rgb(0,0,0);">4 uninstall amazon 相关app</span>
|
||||
|
||||
<span style="color: rgb(0,0,0);">Alexa (com.amazon.dee.app) 和com.amazon.wellness app， 会影响到Validator的测试，需要Uninstall。</span>
|
||||
|
||||
<span style="color: rgb(0,0,0);">The Alexa (com.amazon.dee.app) took too much time on handling the ACL_CONNECTED intent, which impacts the Validator's flow.</span>
|
||||
|
||||
<span style="color: rgb(0,0,0);">There is still another **app,com.amazon.wellness** app, who handled ACL_CONNECTED for 20+ seconds.Please uninstall it as well.</span>
|
||||
|
||||
<span style="color: rgb(255,0,0);">现象： End-to-end integration测试，出现Pairing timeout</span>
|
||||
|
||||
<span style="color: rgb(255,0,0);">操作方式： </span>
|
||||
|
||||
<span style="color: rgb(255,0,0);">adb uninstall com.amazon.wellness</span>
|
||||
|
||||
<span style="color: rgb(255,0,0);">adb uninstall com.amazon.dee.app</span>
|
||||
|
||||
\
|
||||
|
||||
### <span style="color: rgb(153,51,0);">5 测试账号和MODEL ID</span>
|
||||
|
||||
使用Fast Pair Validator测试，需要先登陆Google账号，测试设备使用的Model ID,public key, private key 必须是该google账号注册的Device。
|
||||
|
||||
场内测试账号：<a href="mailto:realsilbt8888@gmail.com" class="external-link" rel="nofollow">realsilbt8888@gmail.com</a>
|
||||
|
||||
**<span style="color: rgb(255,0,0);">Note：</span>**
|
||||
|
||||
fast pair validator app使用的model id 要和DUT开发板配置的model id一致。
|
||||
|
||||
|
||||
|
||||
### **<span style="color: rgb(153,51,0);">6 测试准备</span>**
|
||||
|
||||
测试过程中需要注意
|
||||
|
||||
<span style="color: rgb(255,0,0);">手机端弹出配对提示框时不要手动点击，fast pair validator app会自己触发配对</span>.
|
||||
|
||||
开始测试前，需要确认是否已经和待测试耳机配对过，需要删除配对信息。 最后最好在开始测试前，开关一下飞行模式。
|
||||
|
||||
点击GOT IT开始测试时，耳机端一定要处于Pairable mode，否则会scan不到设备, scan 到设备后，点击Test开始测试。
|
||||
|
||||
|
||||
|
||||
\
|
||||
|
||||
\
|
||||
|
||||
### <span style="color: rgb(255,0,0);">7 Find hub 环境搭建:</span>
|
||||
|
||||
#### <span style="color: rgb(0,51,102);">**1.认证实验室会重新跑 fast pair validator中finder相关的测项，所以送认证前最好提供各个测项的操作视频以及详细的操作步骤(如何开机，如何factory reset，如何进pairing mode..)**</span>
|
||||
|
||||
#### <span style="color: rgb(0,51,102);">**2.如果测试手机支援LEA, 开发者选项中将 Bypass Bluetooth LE Audio 选项关掉，然后重启手机**</span>
|
||||
|
||||
<span style="color: rgb(255,0,0);">****</span>
|
||||
|
||||
#### <span style="color: rgb(0,51,102);">**3.一定要等所有的测项都测试PASS之后才可以提交测试结果**</span>
|
||||
|
||||
<span style="color: rgb(255,0,0);">如果存在Fail的测项，不可以提交测试结果！！</span>！
|
||||
|
||||
<span style="color: rgb(255,0,0);">如果存在Fail的测项，不可以提交测试结果！！</span>！
|
||||
|
||||
<span style="color: rgb(255,0,0);">如果存在Fail的测项，不可以提交测试结果！！</span>！
|
||||
|
||||
#### <span style="color: rgb(153,51,0);">4. Fast pair validator enable EDDYSTONE：</span>
|
||||
|
||||
##### 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 进行测试：
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
##### <span class="Y2IQFc" lang="en"><span style="color: rgb(23,43,77);">4.Finder Fast Pair Validator EDDYSTONE测试完成。测试结果提交：</span>\
|
||||
<span class="image-wrap" style="color: rgb(23,43,77);"><a href="https://jira.realtek.com/secure/attachment/3095764/3095764_Result1.jpg" class="external-link" rel="nofollow" title="Result1.jpg"><img src="https://jira.realtek.com/secure/thumbnail/3095764/_thumb_3095764.png" /></a></span><span style="color: rgb(23,43,77);"> </span><span class="image-wrap" style="color: rgb(23,43,77);"><a href="https://jira.realtek.com/secure/attachment/3095765/3095765_Result2.jpg" class="external-link" rel="nofollow" title="Result2.jpg"><img src="https://jira.realtek.com/secure/thumbnail/3095765/_thumb_3095765.png" /></a></span>\
|
||||
<span class="image-wrap" style="color: rgb(23,43,77);"><a href="https://jira.realtek.com/secure/attachment/3095762/3095762_Submit1.jpg" class="external-link" rel="nofollow" title="Submit1.jpg"><img src="https://jira.realtek.com/secure/thumbnail/3095762/_thumb_3095762.png" /></a></span><span style="color: rgb(23,43,77);"> </span><span class="image-wrap" style="color: rgb(23,43,77);"><a href="https://jira.realtek.com/secure/attachment/3095763/3095763_Submit2.jpg" class="external-link" rel="nofollow" title="Submit2.jpg"><img src="https://jira.realtek.com/secure/thumbnail/3095763/_thumb_3095763.png" /></a></span></span>
|
||||
|
||||
测试jira:
|
||||
|
||||
<span class="jira-issue" client-id="SINGLE_2d885edc-676b-3349-9548-fe5648c9d8cd_948642541_2c9082e76519d09101657ff5cfb3003b" jira-key="BTQCSZ-6106"> <a href="https://jira.realtek.com/browse/BTQCSZ-6106" class="jira-issue-key"><span class="aui-icon aui-icon-wait issue-placeholder"></span>BTQCSZ-6106</a> - <span class="summary">Getting issue details...</span> <span class="aui-lozenge aui-lozenge-subtle aui-lozenge-default issue-placeholder">STATUS</span> </span>
|
||||
7
2.3+测试.md
Normal file
7
2.3+测试.md
Normal file
@@ -0,0 +1,7 @@
|
||||
# 2.3 测试
|
||||
|
||||
测试完成之后要填写测试报告, 测试报告 从以下位置获取：
|
||||
|
||||
<a href="https://wiki.realtek.com/display/BT/Test+Case+of+the+Third+Party" rel="nofollow">Test Case of the Third Party - BT Test - WIKI</a>
|
||||
|
||||
|
||||
17
2.3.1+Fast+Pair+Validator测试.md
Normal file
17
2.3.1+Fast+Pair+Validator测试.md
Normal file
@@ -0,0 +1,17 @@
|
||||
# 2.3.1 Fast Pair Validator测试
|
||||
|
||||
<span class="plugin_pagetree_children_span">2<a href="https://wiki.realtek.com/display/BTMKT/5.3.1.2+EDDYSTONE?src=contextnavpagetreemode" rel="nofollow">.3.1.2 EDDYSTONE</a></span>
|
||||
|
||||
**<span class="plugin_pagetree_children_span" style="color: rgb(255,0,0);"> 这个必须要保证可以PASS，因为认证实验室会使用Fast Pair Validator 测试Finder相关的测项</span>**
|
||||
|
||||
\
|
||||
|
||||
<span class="plugin_pagetree_children_span">2<a href="https://wiki.realtek.com/display/BTMKT/1.3.1.1+FAST+PAIR?src=contextnavpagetreemode" rel="nofollow">.3.1.1 FAST PAIR</a> </span>
|
||||
|
||||
<span class="plugin_pagetree_children_span" style="color: rgb(255,0,0);">这个测项客户自测并且提交测试结果到Google云端，认证实验室暂时不会测试。</span>
|
||||
|
||||
<span class="plugin_pagetree_children_span">目前来看只要有一次测试成功，并且有提交成功的测试结果到Google云端就可以，即使偶尔失败了，如果确定不是我们设备端的bug, 也没关系的</span>
|
||||
|
||||
<span class="plugin_pagetree_children_span"><a href="https://partnerissuetracker.corp.google.com/u/0/issues/473688165" class="external-link" rel="nofollow">https://partnerissuetracker.corp.google.com/u/0/issues/473688165</a></span>
|
||||
|
||||
<span class="plugin_pagetree_children_span"></span>
|
||||
687
2.3.1.1+FAST+PAIR.md
Normal file
687
2.3.1.1+FAST+PAIR.md
Normal file
@@ -0,0 +1,687 @@
|
||||
# 2.3.1.1 FAST PAIR
|
||||
|
||||
<style type="text/css">/**/
|
||||
div.rbtoc1777700962279 {padding: 0px;}
|
||||
div.rbtoc1777700962279 ul {margin-left: 0px;}
|
||||
div.rbtoc1777700962279 li {margin-left: 0px;padding-left: 0px;}
|
||||
|
||||
/**/</style>
|
||||
|
||||
<div class="toc-macro rbtoc1777700962279">
|
||||
|
||||
- [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.测试结果上报)
|
||||
|
||||
</div>
|
||||
|
||||
### <span style="color: rgb(0,51,102);">**Note**</span>
|
||||
|
||||
#### <span style="color: rgb(0,51,102);">1 以下关于mcu cfg tool 的修改仅仅是为了通过fast pair validator测试，待测试通过之后，需要将相应的修改恢复默认值。否则GFPS功能没法正常使用。</span>
|
||||
|
||||
<span style="color: rgb(0,51,102);"> 也就是说以下修改只能搭配fast pair validator app使用，请不要将对应的修改提交到正式release版本。</span>
|
||||
|
||||
#### <span style="color: rgb(0,51,102);">2 测试过程中GFPS 弹窗出来之后请不要点击弹窗！！！</span>
|
||||
|
||||
#### <span style="color: rgb(0,51,102);">3 GFPS Fast pair validator 测试走的Legacy flow, 通过gfps配对 legacy BREDR.</span>
|
||||
|
||||
#### <span style="color: rgb(0,51,102);">4 mcu cfg tool 中 可以配置按键key1进入legacy Pairing mode(MMI 0x6C)，有些测试会需要短按key1进入Pairing mode</span>
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
\
|
||||
|
||||
#### <span style="color: rgb(153,51,0);">5 手机提示信息解读：</span>
|
||||
|
||||
##### <span style="color: rgb(153,51,0);"> Upair the device：耳机做factory reset清掉配对信息</span>
|
||||
|
||||
##### <span style="color: rgb(153,51,0);"> place the device back into pairing mode：耳机进入pairing mode</span><span style="color: rgb(153,51,0);"> </span>
|
||||
|
||||
#### <span style="color: rgb(153,51,0);">6 测试准备</span>
|
||||
|
||||
##### <span style="color: rgb(153,51,0);">打开Fast Pair Validator app</span>
|
||||
|
||||
<span style="color: rgb(153,51,0);"></span>
|
||||
|
||||
##### <span style="color: rgb(153,51,0);">通过model id找到待测试设备</span>
|
||||
|
||||
<span style="color: rgb(153,51,0);"></span>
|
||||
|
||||
##### <span style="color: rgb(153,51,0);">选择FAST PAIR进行测试</span>
|
||||
|
||||
<span style="color: rgb(153,51,0);"></span>
|
||||
|
||||
##### <span style="color: rgb(153,51,0);">不要Enable LE spec test</span>
|
||||
|
||||
<span style="color: rgb(153,51,0);"></span>
|
||||
|
||||
### <span style="color: rgb(153,51,0);">Calibration 测试</span>
|
||||
|
||||
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 弹窗出来之后请**<span style="color: rgb(255,0,0);">不要</span>**点击弹窗！！！
|
||||
|
||||
如果1m测项测试失败，Fast pair validator可以协助我们手动调整tx power值:
|
||||
|
||||
|
||||
|
||||
<span style="color: rgb(153,51,0);">详细文档可以参考：</span><span style="color: rgb(153,51,0);"><a href="https://wiki.realtek.com/display/BTMKT/tx+power+adjust+user+guide" rel="nofollow">tx power adjust user guide - BT_Market - WIKI</a></span>
|
||||
|
||||
### <span style="color: rgb(153,51,0);">End-to-end integration 测试</span>
|
||||
|
||||
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<span style="color: rgb(255,0,0);">需要设置成disable(不勾选)</span>。
|
||||
|
||||
|
||||
|
||||
如果找不到 rws normal disconnect enter pairing mode 这个配置项 ，原因是这个配置项挪位置了，请参考jira <span class="jira-issue" client-id="SINGLE_2d885edc-676b-3349-9548-fe5648c9d8cd_948642827_2c9082e76519d09101657ff5cfb3003b" jira-key="BTSOCTOOL-2822"> <a href="https://jira.realtek.com/browse/BTSOCTOOL-2822" class="jira-issue-key"><span class="aui-icon aui-icon-wait issue-placeholder"></span>BTSOCTOOL-2822</a> - <span class="summary">Getting issue details...</span> <span class="aui-lozenge aui-lozenge-subtle aui-lozenge-default issue-placeholder">STATUS</span> </span> 进行配置，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。 <span style="color: rgb(255,0,0);">注意一定要在“10.Un-Repair device”显示“Unpairing finished!”后才能点NEXT。</span>
|
||||
|
||||
如此反复5遍。
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
测试视频：
|
||||
|
||||
<a href="/download/attachments/948642827/End%20To%20End%20test.mp4?version=1&modificationDate=1759133379450&api=v2" data-linked-resource-container-id="948642827" data-linked-resource-container-version="11" data-linked-resource-content-type="video/mp4" data-linked-resource-default-alias="End To End test.mp4" data-linked-resource-id="948642831" data-linked-resource-type="attachment" data-linked-resource-version="1" data-nice-type="Multimedia">End To End test.mp4</a>
|
||||
|
||||
### <span style="color: rgb(153,51,0);">Auto pairing </span><span style="color: rgb(153,51,0);">测试</span>
|
||||
|
||||
<span style="color: rgb(0,0,0);">Mcu cfg tool配置：</span>
|
||||
|
||||
<span style="color: rgb(0,0,0);">测试该测项的时候，手机清除配对信息(unpair device)，DUT断线需要进入discoverable mode, 所以mcu config tool 中 RWS页面下 rws normal disconnect enter pairing mode<span style="color: rgb(255,0,0);">需要设置成enable(勾选)。</span></span>\
|
||||
app_cfg_const.rws_disconnect_enter_pairing
|
||||
|
||||
<span style="color: rgb(0,0,0);"></span>
|
||||
|
||||
如果找不到 rws normal disconnect enter pairing mode 这个配置项 ，原因是这个配置项挪位置了，请参考jira <span class="jira-issue" client-id="SINGLE_2d885edc-676b-3349-9548-fe5648c9d8cd_948642827_2c9082e76519d09101657ff5cfb3003b" jira-key="BTSOCTOOL-2822"> <a href="https://jira.realtek.com/browse/BTSOCTOOL-2822" class="jira-issue-key"><span class="aui-icon aui-icon-wait issue-placeholder"></span>BTSOCTOOL-2822</a> - <span class="summary">Getting issue details...</span> <span class="aui-lozenge aui-lozenge-subtle aui-lozenge-default issue-placeholder">STATUS</span> </span> 进行配置，RWS normal disconnect enter pairing mode 改成Normal disconnect enter pairing mode
|
||||
|
||||
|
||||
|
||||
<span style="color: rgb(0,0,0);">\
|
||||
</span>
|
||||
|
||||
<span style="color: rgb(0,0,0);">设置每一轮测试持续时间以及重复进行多少轮测试(<span style="color: rgb(255,0,0);">推荐使用APP中提供的默认值进行测试（100次，一次120s</span>)，然后点击test, </span>
|
||||
|
||||
<span style="color: rgb(255,0,0);">测试时将手机setting-》显示-》屏幕超时设置成最大值。灭屏之后测试好像会stop，所以屏幕要保持常亮的状态。</span>
|
||||
|
||||
\
|
||||
|
||||
**<span style="color: rgb(255,0,0);">Note:</span>**
|
||||
|
||||
这个测试按照Google的测试spec是要求每轮测试之前都要强制进pairing mode的。
|
||||
|
||||
正常每轮测试结束后手机会主动断线，为了方便测试我们soc端有设置只要soc收到手机主动断线的指令之后就会主动进入pairing mode,等待下一轮测试。
|
||||
|
||||
因为是跑测试，我们soc端没办法预测所有的失败场景，所以针对异常的情况，soc端是没办法做到所有的失败场景下都能保证下一轮测试一定会正常进pairing mode， 因为手机端并不会告诉soc 什么时候测试开始。
|
||||
|
||||
所以如果跑自动化测试遇到失败的情况，建议手动测试， 每一轮测试结束之后根据提示让设备主动进入pairing mode
|
||||
|
||||
\
|
||||
|
||||
|
||||
|
||||
\
|
||||
|
||||
### <span style="color: rgb(153,51,0);">Auto Subsequent Pairing </span><span style="color: rgb(153,51,0);">测试</span>
|
||||
|
||||
MCU cfg tool 配置：
|
||||
|
||||
测试该测项的时候，手机清除配对信息(unpair device)，DUT断线需要进入non discoverable mode, 所以mcu config tool 中rws normal disconnect enter pairing mode需要<span style="color: rgb(255,0,0);">设置成disable(不勾选)。</span>
|
||||
|
||||
|
||||
|
||||
如果找不到 rws normal disconnect enter pairing mode 这个配置项 ，原因是这个配置项挪位置了，请参考jira <span class="jira-issue" client-id="SINGLE_2d885edc-676b-3349-9548-fe5648c9d8cd_948642827_2c9082e76519d09101657ff5cfb3003b" jira-key="BTSOCTOOL-2822"> <a href="https://jira.realtek.com/browse/BTSOCTOOL-2822" class="jira-issue-key"><span class="aui-icon aui-icon-wait issue-placeholder"></span>BTSOCTOOL-2822</a> - <span class="summary">Getting issue details...</span> <span class="aui-lozenge aui-lozenge-subtle aui-lozenge-default issue-placeholder">STATUS</span> </span> 进行配置，RWS normal disconnect enter pairing mode 改成Normal disconnect enter pairing mode
|
||||
|
||||
|
||||
|
||||
**<span style="color: rgb(255,0,0);">Note:</span>**
|
||||
|
||||
这个测试按照Google的测试spec是要求每轮测试之前都要打nondiscoverable 广播的。
|
||||
|
||||
正常每轮测试结束后手机会主动断线，为了方便测试我们soc端有设置只要soc收到手机主动断线的指令之后就会主动打nondiscoverable 广播,等待下一轮测试。
|
||||
|
||||
因为是跑测试，
|
||||
|
||||
我们soc端没办法预测所有的失败场景，
|
||||
|
||||
所以针对异常的情况，
|
||||
|
||||
soc端是没办法做到所有的失败场景下都能保证下一轮测试一定会主动打nondiscoverable 广播(<span style="color: rgb(255,0,0);">不在pairing mode才会打nondiscoverable 广播</span>)， 因为手机端并不会告诉soc 什么时候测试开始。
|
||||
|
||||
所以如果跑自动化测试遇到失败的情况，建议手动测试：
|
||||
|
||||
每一轮测试结束之后EVB按一下reset或者是关机再开机让设备端主动打nondiscoverable 广播(<span style="color: rgb(255,0,0);">注意这个时候EVB一定不能做factory reset，也不能进pairing mode, 因为这个时候是期望打 nondiscoverable 广播</span>)
|
||||
|
||||
<span style="color: rgb(41,41,41);">BLE advertisements don't contain fast pair account key while not in pairing mode 如果频繁遇到这个error， 可以尝试手动测试试试看</span>
|
||||
|
||||
\
|
||||
|
||||
测试信息设置：
|
||||
|
||||
|
||||
|
||||
手机端测试信息设置完成之后，
|
||||
|
||||
耳机先做factory reset，之后耳机开机进pairing mode，
|
||||
|
||||
之后手机端点击test 开始测试
|
||||
|
||||
|
||||
|
||||
\
|
||||
|
||||
### <span style="color: rgb(153,51,0);">Cross Seekers Auto Subsequent Pairing Test </span><span style="color: rgb(153,51,0);">测试</span>
|
||||
|
||||
MCU cfg tool 配置：
|
||||
|
||||
测试该测项的时候，手机清除配对信息(unpair device)，DUT断线需要进入non discoverable mode, 所以mcu config tool 中rws normal disconnect enter pairing mode需要<span style="color: rgb(255,0,0);">设置成disable(不勾选)。</span>
|
||||
|
||||
|
||||
|
||||
如果找不到 rws normal disconnect enter pairing mode 这个配置项 ，原因是这个配置项挪位置了，请参考jira <span class="jira-issue" client-id="SINGLE_2d885edc-676b-3349-9548-fe5648c9d8cd_948642827_2c9082e76519d09101657ff5cfb3003b" jira-key="BTSOCTOOL-2822"> <a href="https://jira.realtek.com/browse/BTSOCTOOL-2822" class="jira-issue-key"><span class="aui-icon aui-icon-wait issue-placeholder"></span>BTSOCTOOL-2822</a> - <span class="summary">Getting issue details...</span> <span class="aui-lozenge aui-lozenge-subtle aui-lozenge-default issue-placeholder">STATUS</span> </span> 进行配置，RWS normal disconnect enter pairing mode 改成Normal disconnect enter pairing mode
|
||||
|
||||
|
||||
|
||||
\
|
||||
|
||||
\
|
||||
|
||||
测试信息设置：
|
||||
|
||||
|
||||
|
||||
\
|
||||
|
||||
耳机先做factory reset，手机端清掉配对信息<a href="https://wiki.realtek.com/pages/viewpage.action?pageId=401291585" rel="nofollow">1 gfps/finder 如何清除配对信息 - BT_Market - WIKI</a>， 之后耳机开机进pairing mode，之后手机端点击test 开始测试
|
||||
|
||||
\
|
||||
|
||||
测试视频：
|
||||
|
||||
<a href="/download/attachments/948641808/Cross%20Seekers%20Auto%20Subsequent%20Pairing%20Test.mp4?version=1&modificationDate=1759224099177&api=v2" data-linked-resource-container-id="948641808" data-linked-resource-container-version="19" data-linked-resource-content-type="video/mp4" data-linked-resource-default-alias="Cross Seekers Auto Subsequent Pairing Test.mp4" data-linked-resource-id="948651208" data-linked-resource-type="attachment" data-linked-resource-version="1" data-nice-type="Multimedia">Cross Seekers Auto Subsequent Pairing Test.mp4</a>
|
||||
|
||||
测试log：
|
||||
|
||||
<a href="/download/attachments/948641808/COM12_2025-09-30_16-56-51.log?version=1&modificationDate=1759223471600&api=v2" data-linked-resource-container-id="948641808" data-linked-resource-container-version="19" data-linked-resource-content-type="text/plain" data-linked-resource-default-alias="COM12_2025-09-30_16-56-51.log" data-linked-resource-id="948651140" data-linked-resource-type="attachment" data-linked-resource-version="1" data-nice-type="Text File">COM12_2025-09-30_16-56-51.log</a>
|
||||
|
||||
<a href="/download/attachments/948641808/COM12_btsnoop_2025-09-30_16-51-45.cfa?version=1&modificationDate=1759223475897&api=v2" data-linked-resource-container-id="948641808" data-linked-resource-container-version="19" data-linked-resource-content-type="application/octet-stream" data-linked-resource-default-alias="COM12_btsnoop_2025-09-30_16-51-45.cfa" data-linked-resource-id="948651142" data-linked-resource-type="attachment" data-linked-resource-version="1">COM12_btsnoop_2025-09-30_16-51-45.cfa</a>
|
||||
|
||||
<a href="/download/attachments/948641808/COM12_2025-09-30_16-51-39.log?version=1&modificationDate=1759223476397&api=v2" data-linked-resource-container-id="948641808" data-linked-resource-container-version="19" data-linked-resource-content-type="text/plain" data-linked-resource-default-alias="COM12_2025-09-30_16-51-39.log" data-linked-resource-id="948651143" data-linked-resource-type="attachment" data-linked-resource-version="1" data-nice-type="Text File">COM12_2025-09-30_16-51-39.log</a>
|
||||
|
||||
<a href="/download/attachments/948641808/COM12_2025-09-26_14-19-00.log?version=1&modificationDate=1759223503080&api=v2" data-linked-resource-container-id="948641808" data-linked-resource-container-version="19" data-linked-resource-content-type="text/plain" data-linked-resource-default-alias="COM12_2025-09-26_14-19-00.log" data-linked-resource-id="948651148" data-linked-resource-type="attachment" data-linked-resource-version="1" data-nice-type="Text File">COM12_2025-09-26_14-19-00.log</a>
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
\
|
||||
|
||||
### <span style="color: rgb(153,51,0);">Public Key Based Pairing Request in Non Discoverable Mode </span><span style="color: rgb(153,51,0);">测试</span>
|
||||
|
||||
MCU cfg tool 配置：
|
||||
|
||||
测试该测项的时候，手机清除配对信息(unpair device)，DUT断线需要进入non discoverable mode, 所以mcu config tool 中rws normal disconnect enter pairing mode需要<span style="color: rgb(255,0,0);">设置成disable(不勾选)。</span>
|
||||
|
||||
|
||||
|
||||
如果找不到 rws normal disconnect enter pairing mode 这个配置项 ，原因是这个配置项挪位置了，请参考jira <span class="jira-issue" client-id="SINGLE_2d885edc-676b-3349-9548-fe5648c9d8cd_948642827_2c9082e76519d09101657ff5cfb3003b" jira-key="BTSOCTOOL-2822"> <a href="https://jira.realtek.com/browse/BTSOCTOOL-2822" class="jira-issue-key"><span class="aui-icon aui-icon-wait issue-placeholder"></span>BTSOCTOOL-2822</a> - <span class="summary">Getting issue details...</span> <span class="aui-lozenge aui-lozenge-subtle aui-lozenge-default issue-placeholder">STATUS</span> </span> 进行配置，RWS normal disconnect enter pairing mode 改成Normal disconnect enter pairing mode
|
||||
|
||||
|
||||
|
||||
\
|
||||
|
||||
\
|
||||
|
||||
测试信息设置：
|
||||
|
||||
|
||||
|
||||
\
|
||||
|
||||
耳机先做factory reset，手机端清掉配对信息<a href="https://wiki.realtek.com/pages/viewpage.action?pageId=401291585" rel="nofollow">1 gfps/finder 如何清除配对信息 - BT_Market - WIKI</a>， 之后耳机开机进pairing mode，之后手机端点击test 开始测试
|
||||
|
||||
\
|
||||
|
||||
测试视频：
|
||||
|
||||
<a href="/download/attachments/948641808/public%20key%20based%20request%20in%20non%20discoverable%20mode-Non%20LEA.mp4?version=1&modificationDate=1759225238333&api=v2" data-linked-resource-container-id="948641808" data-linked-resource-container-version="19" data-linked-resource-content-type="video/mp4" data-linked-resource-default-alias="public key based request in non discoverable mode-Non LEA.mp4" data-linked-resource-id="948651368" data-linked-resource-type="attachment" data-linked-resource-version="1" data-nice-type="Multimedia">public key based request in non discoverable mode-Non LEA.mp4</a>
|
||||
|
||||
测试log：
|
||||
|
||||
<a href="/download/attachments/948641808/COM12_2025-09-30_17-33-58.log?version=1&modificationDate=1759225010223&api=v2" data-linked-resource-container-id="948641808" data-linked-resource-container-version="19" data-linked-resource-content-type="text/plain" data-linked-resource-default-alias="COM12_2025-09-30_17-33-58.log" data-linked-resource-id="948651337" data-linked-resource-type="attachment" data-linked-resource-version="1" data-nice-type="Text File">COM12_2025-09-30_17-33-58.log</a>
|
||||
|
||||
<a href="/download/attachments/948641808/COM12_btsnoop_2025-09-30_17-29-41.cfa?version=1&modificationDate=1759225015190&api=v2" data-linked-resource-container-id="948641808" data-linked-resource-container-version="19" data-linked-resource-content-type="application/octet-stream" data-linked-resource-default-alias="COM12_btsnoop_2025-09-30_17-29-41.cfa" data-linked-resource-id="948651338" data-linked-resource-type="attachment" data-linked-resource-version="1">COM12_btsnoop_2025-09-30_17-29-41.cfa</a>
|
||||
|
||||
<a href="/download/attachments/948641808/COM12_2025-09-30_17-29-39.log?version=1&modificationDate=1759225015860&api=v2" data-linked-resource-container-id="948641808" data-linked-resource-container-version="19" data-linked-resource-content-type="text/plain" data-linked-resource-default-alias="COM12_2025-09-30_17-29-39.log" data-linked-resource-id="948651339" data-linked-resource-type="attachment" data-linked-resource-version="1" data-nice-type="Text File">COM12_2025-09-30_17-29-39.log</a>
|
||||
|
||||
|
||||
|
||||
\
|
||||
|
||||
### <span style="color: rgb(153,51,0);">Public Key Based Pairing Request After Retroactive Pair </span><span style="color: rgb(153,51,0);">测试</span>
|
||||
|
||||
MCU cfg tool 配置：
|
||||
|
||||
测试该测项的时候，手机清除配对信息(unpair device)，DUT断线需要进入non discoverable mode, 所以mcu config tool 中rws normal disconnect enter pairing mode需要<span style="color: rgb(255,0,0);">设置成disable(不勾选)。</span>
|
||||
|
||||
|
||||
|
||||
如果找不到 rws normal disconnect enter pairing mode 这个配置项 ，原因是这个配置项挪位置了，请参考jira <span class="jira-issue" client-id="SINGLE_2d885edc-676b-3349-9548-fe5648c9d8cd_948642827_2c9082e76519d09101657ff5cfb3003b" jira-key="BTSOCTOOL-2822"> <a href="https://jira.realtek.com/browse/BTSOCTOOL-2822" class="jira-issue-key"><span class="aui-icon aui-icon-wait issue-placeholder"></span>BTSOCTOOL-2822</a> - <span class="summary">Getting issue details...</span> <span class="aui-lozenge aui-lozenge-subtle aui-lozenge-default issue-placeholder">STATUS</span> </span> 进行配置，RWS normal disconnect enter pairing mode 改成Normal disconnect enter pairing mode
|
||||
|
||||
|
||||
|
||||
\
|
||||
|
||||
\
|
||||
|
||||
测试信息设置：
|
||||
|
||||
耳机先做factory reset，手机端清掉配对信息<a href="https://wiki.realtek.com/pages/viewpage.action?pageId=401291585" rel="nofollow">1 gfps/finder 如何清除配对信息 - BT_Market - WIKI</a>， 之后耳机开机进pairing mode，之后手机端点击test 开始测试
|
||||
|
||||
\
|
||||
|
||||
测试视频：
|
||||
|
||||
如果测试过程中遇到 Get account key fail, 参考以下视频：
|
||||
|
||||
<a href="/download/attachments/948641808/Public%20key%20based%20pairing%20request%20after%20retroactive%20pair-nonLEA-Get%20account%20key%20fail.mp4?version=1&modificationDate=1759226451537&api=v2" data-linked-resource-container-id="948641808" data-linked-resource-container-version="19" data-linked-resource-content-type="video/mp4" data-linked-resource-default-alias="Public key based pairing request after retroactive pair-nonLEA-Get account key fail.mp4" data-linked-resource-id="948651473" data-linked-resource-type="attachment" data-linked-resource-version="1" data-nice-type="Multimedia">Public key based pairing request after retroactive pair-nonLEA-Get account key fail.mp4</a>
|
||||
|
||||
测试成功视频：
|
||||
|
||||
<a href="/download/attachments/948641808/Public%20key%20based%20pairing%20request%20after%20retroactive%20pair-nonLEA.mp4?version=1&modificationDate=1759226617723&api=v2" data-linked-resource-container-id="948641808" data-linked-resource-container-version="19" data-linked-resource-content-type="video/mp4" data-linked-resource-default-alias="Public key based pairing request after retroactive pair-nonLEA.mp4" data-linked-resource-id="948651483" data-linked-resource-type="attachment" data-linked-resource-version="1" data-nice-type="Multimedia">Public key based pairing request after retroactive pair-nonLEA.mp4</a>
|
||||
|
||||
\
|
||||
|
||||
测试log：
|
||||
|
||||
<a href="/download/attachments/948642827/Public%20Key%20Based%20Pairing%20Request%20After%20Retroactive%20Pair%E6%B5%8B%E8%AF%95pass.7z?version=1&modificationDate=1763544236457&api=v2" data-linked-resource-container-id="948642827" data-linked-resource-container-version="11" data-linked-resource-content-type="application/octet-stream" data-linked-resource-default-alias="Public Key Based Pairing Request After Retroactive Pair测试pass.7z" data-linked-resource-id="998593087" data-linked-resource-type="attachment" data-linked-resource-version="1">Public Key Based Pairing Request After Retroactive Pair测试pass.7z</a>
|
||||
|
||||
\
|
||||
|
||||
\
|
||||
|
||||
### <span style="color: rgb(153,51,0);">Account key Broadcasting & Rotation of RPA</span><span style="color: rgb(153,51,0);">测试</span>
|
||||
|
||||
MCU cfg tool 配置：
|
||||
|
||||
测试该测项的时候，手机清除配对信息(unpair device)，DUT断线需要进入non discoverable mode, 所以mcu config tool 中rws normal disconnect enter pairing mode需要<span style="color: rgb(255,0,0);">设置成disable(不勾选)。</span>
|
||||
|
||||
|
||||
|
||||
如果找不到 rws normal disconnect enter pairing mode 这个配置项 ，原因是这个配置项挪位置了，请参考jira <span class="jira-issue" client-id="SINGLE_2d885edc-676b-3349-9548-fe5648c9d8cd_948642827_2c9082e76519d09101657ff5cfb3003b" jira-key="BTSOCTOOL-2822"> <a href="https://jira.realtek.com/browse/BTSOCTOOL-2822" class="jira-issue-key"><span class="aui-icon aui-icon-wait issue-placeholder"></span>BTSOCTOOL-2822</a> - <span class="summary">Getting issue details...</span> <span class="aui-lozenge aui-lozenge-subtle aui-lozenge-default issue-placeholder">STATUS</span> </span> 进行配置，RWS normal disconnect enter pairing mode 改成Normal disconnect enter pairing mode
|
||||
|
||||
|
||||
|
||||
\
|
||||
|
||||
板子做factory reset之后，开机进pairing mode，点击test开始测试, 测试时间大概30min左右
|
||||
|
||||
|
||||
|
||||
### <span style="color: rgb(153,51,0);">Key Based Request Flags Reserved Bit Verification </span><span style="color: rgb(153,51,0);">测试</span>
|
||||
|
||||
MCU cfg tool 配置：
|
||||
|
||||
测试该测项的时候，手机清除配对信息(unpair device)，DUT断线需要进入non discoverable mode, 所以mcu config tool 中rws normal disconnect enter pairing mode需要<span style="color: rgb(255,0,0);">设置成disable(不勾选)。</span>
|
||||
|
||||
|
||||
|
||||
如果找不到 rws normal disconnect enter pairing mode 这个配置项 ，原因是这个配置项挪位置了，请参考jira <a href="https://jira.realtek.com/browse/BTSOCTOOL-2822" class="external-link" rel="nofollow" style="text-decoration: line-through;"><img src="https://jira.realtek.com/secure/viewavatar?size=xsmall&avatarId=10916&avatarType=issuetype" />BTSOCTOOL-2822</a> - <span class="summary">\[BBPro2\]\[BBlite D Cut\] RWS界面 rws normal disconnect enter pairing mode 的修改与移动</span> <span class="aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf" style="color: rgb(0,102,68);text-decoration: none;">Resolved</span> 进行配置，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
|
||||
|
||||
测试视频：
|
||||
|
||||
<a href="https://wiki.realtek.com/download/attachments/948641808/Key%20Based%20Request%20Flags%20Reserved%20Bit%20Verification.mp4?version=1&modificationDate=1760339352253&api=v2" rel="nofollow">Key Based Request Flags Reserved Bit Verification.mp4</a>
|
||||
|
||||
\
|
||||
|
||||
### <span style="color: rgb(153,51,0);">Distance 0.3 Meter 测试</span>
|
||||
|
||||
<span style="color: rgb(153,51,0);">耳机开机，<span style="color: rgb(0,0,0);">按键key1进入GFPS LEA配对模式，</span>然后开始测试，等待测试完成。</span>
|
||||
|
||||
<span style="color: rgb(153,51,0);">Note:</span>
|
||||
|
||||
<span style="color: rgb(153,51,0);">GFPS 弹窗出来之后不要点；</span>
|
||||
|
||||
<span style="color: rgb(153,51,0);">如果该测项测不过，MCU cfg tool Thirdparty 页面需要适当减小tx power(比如从-10，减小到-12)；并重新跑 "</span><span style="color: rgb(153,51,0);">**Calibration 测试"** 以及该测项 </span>
|
||||
|
||||
\
|
||||
|
||||
### <span style="color: rgb(153,51,0);"></span>
|
||||
|
||||
\
|
||||
|
||||
### <span style="color: rgb(153,51,0);">Distance 1.2 Meter 测试</span>
|
||||
|
||||
<span style="color: rgb(153,51,0);">耳机开机，<span style="color: rgb(0,0,0);">按键key1进入GFPS LEA配对模式，</span>然后开始测试，等待测试完成。</span>
|
||||
|
||||
<span style="color: rgb(153,51,0);">Note:</span>
|
||||
|
||||
<span style="color: rgb(153,51,0);">GFPS 弹窗出来之后不要点；</span>
|
||||
|
||||
<span style="color: rgb(153,51,0);">如果该测项测不过，MCU cfg tool Thirdparty 页面需要适当增大tx power(比如从-12增大到-10）；并重新跑 "</span><span style="color: rgb(153,51,0);">**Calibration 测试"** 以及该测项 </span>
|
||||
|
||||
\
|
||||
|
||||
\
|
||||
|
||||
### <span style="color: rgb(153,51,0);">Distance 2 Meter 测试</span>
|
||||
|
||||
<span style="color: rgb(153,51,0);">耳机开机，<span style="color: rgb(0,0,0);">按键key1进入GFPS LEA配对模式，</span>然后开始测试，等待测试完成。</span>
|
||||
|
||||
<span style="color: rgb(153,51,0);">Note:</span>
|
||||
|
||||
<span style="color: rgb(153,51,0);">GFPS 弹窗出来之后不要点；</span>
|
||||
|
||||
<span style="color: rgb(153,51,0);">如果该测项测不过，MCU cfg tool Thirdparty 页面需要适当增大tx power(比如从-12增大到-10）；并重新跑 "</span><span style="color: rgb(153,51,0);">**Calibration 测试"** 以及该测项 </span>
|
||||
|
||||
|
||||
|
||||
### <span style="color: rgb(153,51,0);">Battery Notification Verification 测试</span>
|
||||
|
||||
<span style="color: rgb(153,51,0);">Note: </span>
|
||||
|
||||
<span style="color: rgb(153,51,0);">该测项测试的时候需要接充电盒</span>
|
||||
|
||||
MCU cfg tool 配置：
|
||||
|
||||
测试该测项的时候，手机清除配对信息(unpair device)，DUT断线需要进入non discoverable mode, 所以mcu config tool 中rws normal disconnect enter pairing mode需要<span style="color: rgb(255,0,0);">设置成disable(不勾选)。</span>
|
||||
|
||||
|
||||
|
||||
如果找不到 rws normal disconnect enter pairing mode 这个配置项 ，原因是这个配置项挪位置了，请参考jira <span class="jira-issue" client-id="SINGLE_2d885edc-676b-3349-9548-fe5648c9d8cd_948642827_2c9082e76519d09101657ff5cfb3003b" jira-key="BTSOCTOOL-2822"> <a href="https://jira.realtek.com/browse/BTSOCTOOL-2822" class="jira-issue-key"><span class="aui-icon aui-icon-wait issue-placeholder"></span>BTSOCTOOL-2822</a> - <span class="summary">Getting issue details...</span> <span class="aui-lozenge aui-lozenge-subtle aui-lozenge-default issue-placeholder">STATUS</span> </span> 进行配置，RWS normal disconnect enter pairing mode 改成Normal disconnect enter pairing mode
|
||||
|
||||
|
||||
|
||||
\
|
||||
|
||||
测试前板子先做factory reset，之后再开机进pairing mode
|
||||
|
||||
|
||||
|
||||
\
|
||||
|
||||
### <span style="color: rgb(153,51,0);">Battery Suppress Notification Verification 测试</span>
|
||||
|
||||
<span style="color: rgb(153,51,0);">Note: </span>
|
||||
|
||||
<span style="color: rgb(153,51,0);">该测项测试的时候需要接充电盒</span>
|
||||
|
||||
MCU cfg tool 配置：
|
||||
|
||||
测试该测项的时候，手机清除配对信息(unpair device)，DUT断线需要进入non discoverable mode, 所以mcu config tool 中rws normal disconnect enter pairing mode需要<span style="color: rgb(255,0,0);">设置成disable(不勾选)。</span>
|
||||
|
||||
|
||||
|
||||
如果找不到 rws normal disconnect enter pairing mode 这个配置项 ，原因是这个配置项挪位置了，请参考jira <span class="jira-issue" client-id="SINGLE_2d885edc-676b-3349-9548-fe5648c9d8cd_948642827_2c9082e76519d09101657ff5cfb3003b" jira-key="BTSOCTOOL-2822"> <a href="https://jira.realtek.com/browse/BTSOCTOOL-2822" class="jira-issue-key"><span class="aui-icon aui-icon-wait issue-placeholder"></span>BTSOCTOOL-2822</a> - <span class="summary">Getting issue details...</span> <span class="aui-lozenge aui-lozenge-subtle aui-lozenge-default issue-placeholder">STATUS</span> </span> 进行配置，RWS normal disconnect enter pairing mode 改成Normal disconnect enter pairing mode
|
||||
|
||||
|
||||
|
||||
\
|
||||
|
||||
测试前板子先做factory reset，之后再开机进pairing mode
|
||||
|
||||
\
|
||||
|
||||
### <span style="color: rgb(153,51,0);">Battery Level Update Verification 测试</span>
|
||||
|
||||
<span style="color: rgb(153,51,0);">Note: </span>
|
||||
|
||||
<span style="color: rgb(153,51,0);">该测项测试的时候需要接充电盒</span>
|
||||
|
||||
MCU cfg tool 配置：
|
||||
|
||||
测试该测项的时候，手机清除配对信息(unpair device)，DUT断线需要进入non discoverable mode, 所以mcu config tool 中rws normal disconnect enter pairing mode需要<span style="color: rgb(255,0,0);">设置成disable(不勾选)。</span>
|
||||
|
||||
|
||||
|
||||
如果找不到 rws normal disconnect enter pairing mode 这个配置项 ，原因是这个配置项挪位置了，请参考jira <span class="jira-issue" client-id="SINGLE_2d885edc-676b-3349-9548-fe5648c9d8cd_948642827_2c9082e76519d09101657ff5cfb3003b" jira-key="BTSOCTOOL-2822"> <a href="https://jira.realtek.com/browse/BTSOCTOOL-2822" class="jira-issue-key"><span class="aui-icon aui-icon-wait issue-placeholder"></span>BTSOCTOOL-2822</a> - <span class="summary">Getting issue details...</span> <span class="aui-lozenge aui-lozenge-subtle aui-lozenge-default issue-placeholder">STATUS</span> </span> 进行配置，RWS normal disconnect enter pairing mode 改成Normal disconnect enter pairing mode
|
||||
|
||||
|
||||
|
||||
\
|
||||
|
||||
测试前板子先做factory reset，之后再开机进pairing mode
|
||||
|
||||
\
|
||||
|
||||
### <span style="color: rgb(153,51,0);">Personalized Name Update 测试</span>
|
||||
|
||||
MCU cfg tool 配置：
|
||||
|
||||
测试该测项的时候，手机清除配对信息(unpair device)，DUT断线需要进入non discoverable mode, 所以mcu config tool 中rws normal disconnect enter pairing mode需要<span style="color: rgb(255,0,0);">设置成disable(不勾选)。</span>
|
||||
|
||||
|
||||
|
||||
如果找不到 rws normal disconnect enter pairing mode 这个配置项 ，原因是这个配置项挪位置了，请参考jira <span class="jira-issue" client-id="SINGLE_2d885edc-676b-3349-9548-fe5648c9d8cd_948642827_2c9082e76519d09101657ff5cfb3003b" jira-key="BTSOCTOOL-2822"> <a href="https://jira.realtek.com/browse/BTSOCTOOL-2822" class="jira-issue-key"><span class="aui-icon aui-icon-wait issue-placeholder"></span>BTSOCTOOL-2822</a> - <span class="summary">Getting issue details...</span> <span class="aui-lozenge aui-lozenge-subtle aui-lozenge-default issue-placeholder">STATUS</span> </span> 进行配置，RWS normal disconnect enter pairing mode 改成Normal disconnect enter pairing mode
|
||||
|
||||
|
||||
|
||||
\
|
||||
|
||||
\
|
||||
|
||||
\
|
||||
|
||||
<span style="color: rgb(255,0,0);">测试注意事项：</span>
|
||||
|
||||
测试之前板子先做factory reset， 然后开机进pairing mode, 开始测试
|
||||
|
||||
测试过程中看到"Please places the headset to pairing mode"的时候，短按key1进入pairing mode， 测试过程中不可以做factory reset
|
||||
|
||||
|
||||
|
||||
\
|
||||
|
||||
测试log:
|
||||
|
||||
|
||||
|
||||
测试视频：
|
||||
|
||||
<a href="/download/attachments/948642827/Personalized%20name%20update.mp4?version=1&modificationDate=1759133377917&api=v2" data-linked-resource-container-id="948642827" data-linked-resource-container-version="11" data-linked-resource-content-type="video/mp4" data-linked-resource-default-alias="Personalized name update.mp4" data-linked-resource-id="948642830" data-linked-resource-type="attachment" data-linked-resource-version="1" data-nice-type="Multimedia">Personalized name update.mp4</a>
|
||||
|
||||
### <span style="color: rgb(153,51,0);">Personalized Name with Provider First Time Pairing 测试</span>
|
||||
|
||||
MCU cfg tool 配置：
|
||||
|
||||
测试该测项的时候，手机清除配对信息(unpair device)，DUT断线需要进入non discoverable mode, 所以mcu config tool 中rws normal disconnect enter pairing mode需要<span style="color: rgb(255,0,0);">设置成disable(不勾选)。</span>
|
||||
|
||||
|
||||
|
||||
如果找不到 rws normal disconnect enter pairing mode 这个配置项 ，原因是这个配置项挪位置了，请参考jira <span class="jira-issue" client-id="SINGLE_2d885edc-676b-3349-9548-fe5648c9d8cd_948642827_2c9082e76519d09101657ff5cfb3003b" jira-key="BTSOCTOOL-2822"> <a href="https://jira.realtek.com/browse/BTSOCTOOL-2822" class="jira-issue-key"><span class="aui-icon aui-icon-wait issue-placeholder"></span>BTSOCTOOL-2822</a> - <span class="summary">Getting issue details...</span> <span class="aui-lozenge aui-lozenge-subtle aui-lozenge-default issue-placeholder">STATUS</span> </span> 进行配置，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:
|
||||
|
||||
|
||||
|
||||
测试视频：
|
||||
|
||||
\
|
||||
|
||||
### <span style="color: rgb(153,51,0);">Ring a Device 测试</span>
|
||||
|
||||
MCU cfg tool 配置：
|
||||
|
||||
测试该测项的时候，手机清除配对信息(unpair device)，DUT断线需要进入non discoverable mode, 所以mcu config tool 中rws normal disconnect enter pairing mode需要<span style="color: rgb(255,0,0);">设置成disable(不勾选)。</span>
|
||||
|
||||
|
||||
|
||||
如果找不到 rws normal disconnect enter pairing mode 这个配置项 ，原因是这个配置项挪位置了，请参考jira <span class="jira-issue" client-id="SINGLE_2d885edc-676b-3349-9548-fe5648c9d8cd_948642827_2c9082e76519d09101657ff5cfb3003b" jira-key="BTSOCTOOL-2822"> <a href="https://jira.realtek.com/browse/BTSOCTOOL-2822" class="jira-issue-key"><span class="aui-icon aui-icon-wait issue-placeholder"></span>BTSOCTOOL-2822</a> - <span class="summary">Getting issue details...</span> <span class="aui-lozenge aui-lozenge-subtle aui-lozenge-default issue-placeholder">STATUS</span> </span> 进行配置，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:
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
\
|
||||
|
||||
测试视频：
|
||||
|
||||
<a href="/download/attachments/948642827/Ring%20a%20Device.mp4?version=1&modificationDate=1759133376580&api=v2" data-linked-resource-container-id="948642827" data-linked-resource-container-version="11" data-linked-resource-content-type="video/mp4" data-linked-resource-default-alias="Ring a Device.mp4" data-linked-resource-id="948642829" data-linked-resource-type="attachment" data-linked-resource-version="1" data-nice-type="Multimedia">Ring a Device.mp4</a>
|
||||
|
||||
### <span style="color: rgb(153,51,0);">Retroactive Pair 测试</span>
|
||||
|
||||
MCU cfg tool 配置：
|
||||
|
||||
测试该测项的时候，手机清除配对信息(unpair device)，DUT断线需要进入non discoverable mode, 所以mcu config tool 中rws normal disconnect enter pairing mode需要设置成<span style="color: rgb(255,0,0);">disable(不勾选)。</span>
|
||||
|
||||
|
||||
|
||||
如果找不到 rws normal disconnect enter pairing mode 这个配置项 ，原因是这个配置项挪位置了，请参考jira <span class="jira-issue" client-id="SINGLE_2d885edc-676b-3349-9548-fe5648c9d8cd_948642827_2c9082e76519d09101657ff5cfb3003b" jira-key="BTSOCTOOL-2822"> <a href="https://jira.realtek.com/browse/BTSOCTOOL-2822" class="jira-issue-key"><span class="aui-icon aui-icon-wait issue-placeholder"></span>BTSOCTOOL-2822</a> - <span class="summary">Getting issue details...</span> <span class="aui-lozenge aui-lozenge-subtle aui-lozenge-default issue-placeholder">STATUS</span> </span> 进行配置，RWS normal disconnect enter pairing mode 改成Normal disconnect enter pairing mode
|
||||
|
||||
|
||||
|
||||
\
|
||||
|
||||
\
|
||||
|
||||
在Available device点选要测试的设备：
|
||||
|
||||
|
||||
|
||||
测试视频：
|
||||
|
||||
<a href="/download/attachments/948642827/retroactive%20pair%20test.mp4?version=1&modificationDate=1759133374553&api=v2" data-linked-resource-container-id="948642827" data-linked-resource-container-version="11" data-linked-resource-content-type="video/mp4" data-linked-resource-default-alias="retroactive pair test.mp4" data-linked-resource-id="948642828" data-linked-resource-type="attachment" data-linked-resource-version="1" data-nice-type="Multimedia">retroactive pair test.mp4</a>
|
||||
|
||||
测试log：
|
||||
|
||||
<a href="/download/attachments/948642827/Retroactive%20Pair%E6%B5%8B%E8%AF%95pass.7z?version=1&modificationDate=1763544047830&api=v2" data-linked-resource-container-id="948642827" data-linked-resource-container-version="11" data-linked-resource-content-type="application/octet-stream" data-linked-resource-default-alias="Retroactive Pair测试pass.7z" data-linked-resource-id="998593071" data-linked-resource-type="attachment" data-linked-resource-version="1">Retroactive Pair测试pass.7z</a>
|
||||
|
||||
### <span style="color: rgb(153,51,0);">Active Noise Control Verification 测试</span>
|
||||
|
||||
<span style="color: rgb(153,51,0);">目前还不清楚怎么测试，如果不支援可以不测</span>
|
||||
|
||||
### <span style="color: rgb(153,51,0);">Active Noise Control Disable 测试</span>
|
||||
|
||||
<span style="color: rgb(153,51,0);">目前还不清楚怎么测试，如果不支援可以不测</span>
|
||||
|
||||
### <span style="color: rgb(153,51,0);">Firmware Version 测试</span>
|
||||
|
||||
MCU cfg tool 配置：
|
||||
|
||||
测试该测项的时候，手机清除配对信息(unpair device)，DUT断线需要进入non discoverable mode, 所以mcu config tool 中rws normal disconnect enter pairing mode需要<span style="color: rgb(255,0,0);">设置成disable(不勾选)。</span>
|
||||
|
||||
|
||||
|
||||
如果找不到 rws normal disconnect enter pairing mode 这个配置项 ，原因是这个配置项挪位置了，请参考jira <span class="jira-issue" client-id="SINGLE_2d885edc-676b-3349-9548-fe5648c9d8cd_948642827_2c9082e76519d09101657ff5cfb3003b" jira-key="BTSOCTOOL-2822"> <a href="https://jira.realtek.com/browse/BTSOCTOOL-2822" class="jira-issue-key"><span class="aui-icon aui-icon-wait issue-placeholder"></span>BTSOCTOOL-2822</a> - <span class="summary">Getting issue details...</span> <span class="aui-lozenge aui-lozenge-subtle aui-lozenge-default issue-placeholder">STATUS</span> </span> 进行配置，RWS normal disconnect enter pairing mode 改成Normal disconnect enter pairing mode
|
||||
|
||||
|
||||
|
||||
\
|
||||
|
||||
### <span style="color: rgb(153,51,0);">Dynamic Buffer Size测试</span>
|
||||
|
||||
<span style="color: rgb(153,51,0);">目前还不清楚怎么测试，如果不支援 可以不测</span>
|
||||
|
||||
\
|
||||
|
||||
### 10.测试结果上报
|
||||
|
||||
<span style="color: rgb(255,0,0);">测试成功后，除了 <span style="color: rgb(153,51,0);">目前还不清楚怎么测试 的测项</span>之外的，其他所有的测试结果都为PASS，可以SUBMIT测试结果，否则请不要提交测试结果！！！</span>
|
||||
|
||||
\
|
||||
|
||||
\
|
||||
|
||||
\
|
||||
|
||||
\
|
||||
7
2.3.2+EDDYSTONE.md
Normal file
7
2.3.2+EDDYSTONE.md
Normal file
@@ -0,0 +1,7 @@
|
||||
# 2.3.2 EDDYSTONE
|
||||
|
||||
请参考以下Wiki中的测项进行测试 <a href="https://wiki.realtek.com/pages/viewpage.action?pageId=343561364" rel="nofollow">2 Fast Pair validator Finder 测试 - BT_Market - WIKI</a>
|
||||
|
||||
|
||||
|
||||
\
|
||||
1
2.3.2+手动测试.md
Normal file
1
2.3.2+手动测试.md
Normal file
@@ -0,0 +1 @@
|
||||
# 2.3.2 手动测试
|
||||
13
2.3.2.1+Initial+pair+and+subsequent+pair.md
Normal file
13
2.3.2.1+Initial+pair+and+subsequent+pair.md
Normal file
@@ -0,0 +1,13 @@
|
||||
# 2.3.2.1 Initial pair and subsequent pair
|
||||
|
||||
google 官方测试文档：
|
||||
|
||||
<a href="https://developers.google.com/nearby/fast-pair/fast-pair-certification-guideline#22_notification_popup_for_initial_pairing" class="external-link" rel="nofollow">Fast Pair 3.2 & 3.3 Certification Guidelines | Google for Developers</a>
|
||||
|
||||
Realtek内部整理文档：
|
||||
|
||||
<a href="https://wiki.realtek.com/pages/viewpage.action?pageId=288810503" rel="nofollow">1 Initial Pairing and Subsequent Pairing Test Guideline(中文文档) - BT_Market - WIKI</a>
|
||||
|
||||
测试视频：
|
||||
|
||||
<a href="/download/attachments/948642914/initial_pairing.mp4?version=1&modificationDate=1759136596260&api=v2" data-linked-resource-container-id="948642914" data-linked-resource-container-version="3" data-linked-resource-content-type="video/mp4" data-linked-resource-default-alias="initial_pairing.mp4" data-linked-resource-id="948643199" data-linked-resource-type="attachment" data-linked-resource-version="1" data-nice-type="Multimedia">initial_pairing.mp4</a>
|
||||
13
2.3.2.2+extended+feature.md
Normal file
13
2.3.2.2+extended+feature.md
Normal file
@@ -0,0 +1,13 @@
|
||||
# 2.3.2.2 extended feature
|
||||
|
||||
Google 官方文档：
|
||||
|
||||
<a href="https://developers.google.com/nearby/fast-pair/fast-pair-certification-guideline#4_feature_certification_criteria" class="external-link" rel="nofollow">https://developers.google.com/nearby/fast-pair/fast-pair-certification-guideline#4_feature_certification_criteria</a>
|
||||
|
||||
Realtek 内部整理文档：
|
||||
|
||||
<a href="https://wiki.realtek.com/pages/viewpage.action?pageId=374584696" rel="nofollow">1 Extension Feature Test Guideline(中文文档) - BT_Market - WIKI</a>
|
||||
|
||||
\
|
||||
|
||||
\
|
||||
11
2.3.2.3+find+hub.md
Normal file
11
2.3.2.3+find+hub.md
Normal file
@@ -0,0 +1,11 @@
|
||||
# 2.3.2.3 find hub
|
||||
|
||||
请参考以下Wiki 中的test case 进行测试 <a href="https://wiki.realtek.com/pages/viewpage.action?pageId=539896715" rel="nofollow">1 Finder-手机"Find My Device"APP测试-v1.3 - BT_Market - WIKI</a>
|
||||
|
||||
\
|
||||
|
||||
|
||||
|
||||
\
|
||||
|
||||
\
|
||||
21
2.provider支援LE+audio,+必须打开_Enable+LE+Spec+Test__.md
Normal file
21
2.provider支援LE+audio,+必须打开_Enable+LE+Spec+Test__.md
Normal file
@@ -0,0 +1,21 @@
|
||||
# 2.provider支援LE audio, 必须打开"Enable LE Spec Test"?
|
||||
|
||||
答案：是的
|
||||
|
||||
hi <span class="fWwrkf"><span rel="nofollow">@Vito Kao</span></span> 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 <span class="NhKrqd"><span rel="nofollow">@danni Realtek</span></span> 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\
|
||||
<a href="https://developers.google.com/nearby/fast-pair/lea-validator-app-user-manual" class="external-link" rel="nofollow">https://developers.google.com/nearby/fast-pair/lea-validator-app-user-manual</a>\
|
||||
11
2.手机端点击Ring,耳机端没有响铃.md
Normal file
11
2.手机端点击Ring,耳机端没有响铃.md
Normal file
@@ -0,0 +1,11 @@
|
||||
# 2.手机端点击Ring,耳机端没有响铃
|
||||
|
||||
<span class="jira-issue" jira-key="BB2BUG-18476"> <a href="https://jira.realtek.com/browse/BB2BUG-18476" class="jira-issue-key"><img src="https://jira.realtek.com/secure/viewavatar?size=xsmall&avatarId=10916&avatarType=issuetype" />BB2BUG-18476</a> - <span class="summary">\[BB2\]\[8773ESL\]\[v3.13.0.7\]\[GFPS\]\[LE Audio\]Find device响铃时，有时候停止响铃失败</span> <span class="aui-lozenge aui-lozenge-subtle aui-lozenge-current jira-macro-single-issue-export-pdf">In Progress</span> </span> ：
|
||||
|
||||
看样子是手机先读了附耳的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的已知问题，他们说后续会修正，暂时先作为已知问题处理
|
||||
@@ -0,0 +1,50 @@
|
||||
# 20 initial pair成功之后维持BR link,耳机再次进入Pairing mode,GFPS弹窗出来点击弹窗显示连接成功，但是会再次马上跳出配对弹框
|
||||
|
||||
<a href="https://jira.realtek.com/browse/BB2BUG-50358" class="external-link" rel="nofollow">[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</a>
|
||||
|
||||
非LEA测试步骤：
|
||||
|
||||
1、耳机开机，进配对，通过GFPS弹框与手机 Legacy连接，
|
||||
|
||||
3、在【16:41:22】左右耳机按键进入配对，耳机与手机保持连接 ，手机跳出GFPS配对弹框
|
||||
|
||||
4、在【16:41:24】左右点击弹框进行配对，**<span style="color: rgb(255,0,0);">弹框显示连接成功，但是会再次马上跳出配对弹框</span>**
|
||||
|
||||
\
|
||||
|
||||
<table class="confluenceTable">
|
||||
<tbody>
|
||||
<tr>
|
||||
<th class="confluenceTh" scope="col"><p> //手机和耳机 Legacy ACL link已经存在的情况下，16:41:22 耳机再次进入Pairing mode， gfps打discoverable adv</p>
|
||||
<p>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</p>
|
||||
<p><br />
|
||||
//手机扫到GFPS discoverable adv之后会有GFPS弹窗出来， 点击弹窗，手机会建BLE 连线<br />
|
||||
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<br />
|
||||
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<br />
|
||||
</p>
|
||||
<p>//手机发送kbp request </p>
|
||||
<p>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<br />
|
||||
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<br />
|
||||
Line 29453: 0009001 06-16#16:41:27.578 129 0032692.007 [APP] !**app_gfps_link_add_link_into_priority_queue: conn_id 0<br />
|
||||
Line 29454: 0009002 06-16#16:41:27.578 130 0032692.169 [APP] !**app_gfps_print_link_priority: conn_id 0, priority 0<br />
|
||||
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<br />
|
||||
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</p>
|
||||
<p>//手机读存储的名字<br />
|
||||
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<br />
|
||||
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<br />
|
||||
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<br />
|
||||
Line 29465: 0009013 06-16#16:41:27.611 141 0032694.063 [APP] !**gfps_hmac_sha256: E7 80 67 2E 6C C7 5A A6<br />
|
||||
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 <br />
|
||||
Line 29475: 0009023 06-16#16:41:27.611 151 0032695.949 [APP] !** app_gfps_personalized_name_send: is_send = 1<br />
|
||||
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<br />
|
||||
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</p>
|
||||
<p><br />
|
||||
</p>
|
||||
<p>//手机写accountkey<br />
|
||||
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<br />
|
||||
Line 30008: 0009544 06-16#16:41:27.845 119 0032952.423 [APP] !**app_gfps_account_key_remote_add</p>
|
||||
<p><strong><span style="color: rgb(255,0,0);">//因为legacy ACL link一直存在，所以手机不会再执行任何legacy相关的操作，这边 legacy 的radio mode 也会一直保持在discoverable and connectable, gfps就会一直打discoverable adv, 进而手机端GFPS 弹窗会一直出现</span></strong><br />
|
||||
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</p></th>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
5
21++android+13设备无GFPS弹窗.md
Normal file
5
21++android+13设备无GFPS弹窗.md
Normal file
@@ -0,0 +1,5 @@
|
||||
# 21 android 13设备无GFPS弹窗
|
||||
|
||||
<a href="https://jira.realtek.com/browse/BBPRO3BUG-27740" class="external-link" rel="nofollow">[BBPRO3BUG-27740] [BBPro3][RTL8773DFL+RTL8763EAU][GMI/WLT/JLAB_Daybreak][Gaming Stereo/Audio mixing]: android 13设备无GFPS弹窗 - Jira</a>
|
||||
|
||||
是因为Initial Pair有问题，Initial Pair失败之后弹窗的优先级会降低，就会不弹窗， 可以先解决配对问题之后再看弹窗的问题
|
||||
7
22+Android+12+GFPS不弹窗.md
Normal file
7
22+Android+12+GFPS不弹窗.md
Normal file
@@ -0,0 +1,7 @@
|
||||
# 22 Android 12 GFPS不弹窗
|
||||
|
||||
如果设备端有打开legacy CTKD le ltk 功能， Android 12 通过GFPS弹窗配对会失败，配对失败之后弹窗的优先级就会降低
|
||||
|
||||
这是Google已知问题
|
||||
|
||||
<a href="https://wiki.realtek.com/pages/viewpage.action?pageId=821520803" rel="nofollow">4 pixel6(android 12) 不连A2DP - BT_Market - WIKI</a>
|
||||
@@ -0,0 +1,39 @@
|
||||
# 23 很多客户要求不在Pairing mode不允许配对新的设备，和GFPS subsequent Pair 有冲突，修改策略如下
|
||||
|
||||
之前是在ACL 连线的时候卡的，现在把这边的code拿掉了，会在配对的时候需要回CFM的地方卡
|
||||
|
||||
|
||||
|
||||
\
|
||||
|
||||
\
|
||||
|
||||
LE 处理的地方：
|
||||
|
||||
如果是gfps配对：
|
||||
|
||||
<span style="color: rgb(64,120,242);">app_gfps_handle_le_numerical_comparison_bond_cfm会返回 true， GFPS 会根据自己的逻辑来决定 ACCEPT 还是REJECT</span>
|
||||
|
||||
\
|
||||
|
||||
<span style="color: rgb(64,120,242);">如果app_gfps_handle_le_numerical_comparison_bond_cfm返回false，说明不是GFPS 配对：</span>
|
||||
|
||||
<span style="color: rgb(64,120,242);">由APP逻辑决定具体是</span><span style="color: rgb(228,86,73);">GAP_CFM_CAUSE_ACCEPT 还是 </span><span style="color: rgb(228,86,73);">GAP_CFM_CAUSE_REJECT</span>
|
||||
|
||||
|
||||
|
||||
\
|
||||
|
||||
BR 处理的地方：
|
||||
|
||||
如果是gfps配对：
|
||||
|
||||
<span style="color: rgb(64,120,242);">app_gfps_handle_bt_user_confirm</span><span style="color: rgb(64,120,242);">会返回 true， GFPS 会根据自己的逻辑来决定 ACCEPT 还是REJECT</span>
|
||||
|
||||
\
|
||||
|
||||
<span style="color: rgb(64,120,242);">如果</span><span style="color: rgb(64,120,242);">app_gfps_handle_bt_user_confirm</span><span style="color: rgb(64,120,242);">返回false，说明不是GFPS 配对：</span>
|
||||
|
||||
<span style="color: rgb(64,120,242);">由APP逻辑决定具体是</span><span style="color: rgb(228,86,73);">GAP_CFM_CAUSE_ACCEPT 还是 </span><span style="color: rgb(228,86,73);">GAP_CFM_CAUSE_REJECT</span>
|
||||
|
||||
|
||||
55
24+BLE+连上之后手机没有查服务，紧接着手机主动下了断线.md
Normal file
55
24+BLE+连上之后手机没有查服务，紧接着手机主动下了断线.md
Normal file
@@ -0,0 +1,55 @@
|
||||
# 24 BLE 连上之后手机没有查服务，紧接着手机主动下了断线
|
||||
|
||||
问题1：
|
||||
|
||||
<a href="https://partnerissuetracker.corp.google.com/u/0/issues/420766718" class="external-link" rel="nofollow">https://partnerissuetracker.corp.google.com/u/0/issues/420766718</a>
|
||||
|
||||
<table class="confluenceTable">
|
||||
<tbody>
|
||||
<tr>
|
||||
<th class="confluenceTh" scope="col"><pre><code>// 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)</code></pre></th>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
<table class="confluenceTable">
|
||||
<tbody>
|
||||
<tr>
|
||||
<th class="confluenceTh" scope="col"><p>After BLE is connected, retroactive pairing failed due to no cache is found.</p>
|
||||
<pre><code>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 ]</code></pre>
|
||||
<p>It may because the model-id<span> </span><code>99f751</code><span> </span>is filtered by spoofing detected.</p>
|
||||
<pre><code>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</code></pre>
|
||||
<p>Since the model-id<span> </span><code>99f751</code><span> </span>has still not approved in the device console yet,</p>
|
||||
<p>could you go to<span> </span><code>Settings > Google > All services > Devices</code><span> </span>and enable<span> </span><code>Include debug results</code><span> </span>(requires to enable developer mode first)</p>
|
||||
<p><br />
|
||||
Then, test again to see if the device can detect the advertisement correctly. Thanks!</p></th>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
问题2:
|
||||
|
||||
<a href="https://partnerissuetracker.corp.google.com/u/0/issues/502346693" class="external-link" rel="nofollow">https://partnerissuetracker.corp.google.com/u/0/issues/502346693</a>
|
||||
1
3+GFPS+LEA+FAQ.md
Normal file
1
3+GFPS+LEA+FAQ.md
Normal file
@@ -0,0 +1 @@
|
||||
# 3 GFPS LEA FAQ
|
||||
3
3+LEA+++GFPS.md
Normal file
3
3+LEA+++GFPS.md
Normal file
@@ -0,0 +1,3 @@
|
||||
# 3 LEA + GFPS
|
||||
|
||||
该功能是通过GFPS 快速配对 LE audio， 如果同时支援BREDR， 会通过LE 的 LTK CTKD 生成 BREDR 的 linkkey
|
||||
9
3+UI+提示+Not+receive+KeyBasedPairingResponse.md
Normal file
9
3+UI+提示+Not+receive+KeyBasedPairingResponse.md
Normal file
@@ -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没有收到
|
||||
15
3.+initial+pair+走的LE+配对，+subsequent+pair+走的legacy+配对.md
Normal file
15
3.+initial+pair+走的LE+配对，+subsequent+pair+走的legacy+配对.md
Normal file
@@ -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 相关的配置信息不正确，正确的配置如下：
|
||||
|
||||
|
||||
|
||||
<a href="/download/attachments/374581864/COM8_btsnoop_2023-05-24_11-04-41.cfa?version=1&modificationDate=1684899001267&api=v2" data-linked-resource-container-id="374581864" data-linked-resource-container-version="3" data-linked-resource-content-type="application/octet-stream" data-linked-resource-default-alias="COM8_btsnoop_2023-05-24_11-04-41.cfa" data-linked-resource-id="374581949" data-linked-resource-type="attachment" data-linked-resource-version="1">COM8_btsnoop_2023-05-24_11-04-41.cfa</a>
|
||||
|
||||
<a href="/download/attachments/374581864/COM8_2023-05-24_11-04-30.log?version=1&modificationDate=1684899001733&api=v2" data-linked-resource-container-id="374581864" data-linked-resource-container-version="3" data-linked-resource-content-type="text/plain" data-linked-resource-default-alias="COM8_2023-05-24_11-04-30.log" data-linked-resource-id="374581950" data-linked-resource-type="attachment" data-linked-resource-version="1" data-nice-type="Text File">COM8_2023-05-24_11-04-30.log</a>
|
||||
51
3.1+Project+工程enable对应功能.md
Normal file
51
3.1+Project+工程enable对应功能.md
Normal file
@@ -0,0 +1,51 @@
|
||||
# 3.1 Project 工程enable对应功能
|
||||
|
||||
<span style="color: rgb(166,38,164);">app_flags.h 里面找到 <span style="color: rgb(64,120,242);">CONFIG_REALTEK_GFPS_XXX 相关的宏并按照以下信息配置</span>：</span>
|
||||
|
||||
<span style="color: rgb(166,38,164);">\#define</span><span style="color: rgb(56,58,66);"> </span><span style="color: rgb(64,120,242);">CONFIG_REALTEK_GFPS_FEATURE_SUPPORT</span><span style="color: rgb(56,58,66);"> </span><span style="color: rgb(152,104,1);">1</span>\
|
||||
<span style="color: rgb(166,38,164);">\#define</span><span style="color: rgb(56,58,66);"> </span><span style="color: rgb(64,120,242);">CONFIG_REALTEK_GFPS_LE_DEVICE_SUPPORT</span><span style="color: rgb(56,58,66);"> (1 && </span><span style="color: rgb(64,120,242);">CONFIG_REALTEK_GFPS_FEATURE_SUPPORT</span><span style="color: rgb(56,58,66);">)</span>\
|
||||
<span style="color: rgb(166,38,164);">\#define</span><span style="color: rgb(56,58,66);"> </span><span style="color: rgb(64,120,242);">CONFIG_REALTEK_GFPS_SASS_SUPPORT</span><span style="color: rgb(56,58,66);"> (0 && </span><span style="color: rgb(64,120,242);">CONFIG_REALTEK_GFPS_FEATURE_SUPPORT</span><span style="color: rgb(56,58,66);">)</span>\
|
||||
<span style="color: rgb(166,38,164);">\#define</span><span style="color: rgb(56,58,66);"> </span><span style="color: rgb(64,120,242);">CONFIG_REALTEK_GFPS_FINDER_SUPPORT</span><span style="color: rgb(56,58,66);"> (0 && </span><span style="color: rgb(64,120,242);">CONFIG_REALTEK_GFPS_FEATURE_SUPPORT</span><span style="color: rgb(56,58,66);">)</span>
|
||||
|
||||
<span style="color: rgb(56,58,66);">GFPS依赖的其他的模块：</span>
|
||||
|
||||
\#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
|
||||
|
||||
\
|
||||
|
||||
<span style="color: rgb(152,104,1);">Note:</span>
|
||||
|
||||
<span style="color: rgb(152,104,1);">有的IC宏的名字是 GFPS_XXX, <span style="color: rgb(166,38,164);">app_flags.h 里面找到 <span style="color: rgb(64,120,242);">GFPS_XXX 相关的宏并按照以下信息配置</span>：</span></span>
|
||||
|
||||
<span style="color: rgb(166,38,164);">\#define</span><span style="color: rgb(56,58,66);"> </span><span style="color: rgb(64,120,242);">GFPS_FEATURE_SUPPORT</span><span style="color: rgb(56,58,66);"> </span><span style="color: rgb(152,104,1);">1</span>\
|
||||
<span style="color: rgb(166,38,164);">\#define</span><span style="color: rgb(56,58,66);"> </span><span style="color: rgb(64,120,242);">GFPS_LE_DEVICE_SUPPORT</span><span style="color: rgb(56,58,66);"> (1 && </span><span style="color: rgb(64,120,242);">GFPS_FEATURE_SUPPORT</span><span style="color: rgb(56,58,66);">)</span>\
|
||||
<span style="color: rgb(166,38,164);">\#define</span><span style="color: rgb(56,58,66);"> </span><span style="color: rgb(64,120,242);">GFPS_SASS_SUPPORT</span><span style="color: rgb(56,58,66);"> (0 && </span><span style="color: rgb(64,120,242);">GFPS_FEATURE_SUPPORT</span><span style="color: rgb(56,58,66);">)</span>\
|
||||
<span style="color: rgb(166,38,164);">\#define</span><span style="color: rgb(56,58,66);"> </span><span style="color: rgb(64,120,242);">GFPS_FINDER_SUPPORT</span><span style="color: rgb(56,58,66);"> (0 && </span><span style="color: rgb(64,120,242);">GFPS_FEATURE_SUPPORT</span><span style="color: rgb(56,58,66);">)</span>
|
||||
|
||||
<span style="color: rgb(56,58,66);">GFPS依赖的其他的模块：</span>
|
||||
|
||||
\#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
|
||||
1
3.2+测试环境搭建.md
Normal file
1
3.2+测试环境搭建.md
Normal file
@@ -0,0 +1 @@
|
||||
# 3.2 测试环境搭建
|
||||
321
3.2.1+设备端环境搭建.md
Normal file
321
3.2.1+设备端环境搭建.md
Normal file
@@ -0,0 +1,321 @@
|
||||
# 3.2.1 设备端环境搭建
|
||||
|
||||
<style type="text/css">/**/
|
||||
div.rbtoc1777701128697 {padding: 0px;}
|
||||
div.rbtoc1777701128697 ul {margin-left: 0px;}
|
||||
div.rbtoc1777701128697 li {margin-left: 0px;padding-left: 0px;}
|
||||
|
||||
/**/</style>
|
||||
|
||||
<div class="toc-macro rbtoc1777701128697">
|
||||
|
||||
- [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提示音)
|
||||
|
||||
</div>
|
||||
|
||||
### 1 MCUConfigTool 配置
|
||||
|
||||
#### 1.1 General 页面 : 不勾选 Enable auto power off, <span style="letter-spacing: -0.003em;">不勾选 Enable pairing timeout</span>
|
||||
|
||||
<span style="color: rgb(255,0,0);">**Note**:</span>
|
||||
|
||||
修改为了便于GFPS测试，GFPS 测试的时候或者是过认证的时候需要修改， **<span style="color: rgb(255,0,0);">量产时可以考虑不修改。</span>**
|
||||
|
||||
|
||||
|
||||
#### 1.2 General 页面 : Discoverable in standby mode 设置成disable。<span style="color: rgb(255,0,0);">**强制要求必须修改**</span>
|
||||
|
||||
<span style="color: rgb(255,0,0);">**Note**:</span>
|
||||
|
||||
GFPS 耳机第一次和一只手机配对成功之后(initial pairing 成功)，就会进入 subsequent pairing mode。
|
||||
|
||||
所以initial pairing 成功之后，不管耳机是进入idle mode 还是进入connectable mode(multilink 支持)，都不应该再设置成discoverable。
|
||||
|
||||
|
||||
|
||||
#### 1.3 General 页面: 勾选 Non-discoverable when linkback <span style="color: rgb(255,0,0);">**强制要求必须修改**</span>
|
||||
|
||||
linkback模式下DUT不应该discoverable，不然手机端会一直弹配对窗口。<span style="color: rgb(255,0,0);"> </span>
|
||||
|
||||
\
|
||||
|
||||
|
||||
|
||||
#### 1.4 勾选Multi-link support, 并且不要勾选 Enter pairing state while only available device is connected <span style="color: rgb(255,0,0);">**强制要求必须修改**</span>
|
||||
|
||||
下面红框里的**<span style="color: rgb(255,0,0);">不可以勾选</span> **<span style="color: rgb(0,0,0);letter-spacing: 0.0px;">不然battery HUN测试可能测不过，</span> **<span class="jira-issue" client-id="SINGLE_2d885edc-676b-3349-9548-fe5648c9d8cd_948642932_2c9082e76519d09101657ff5cfb3003b" jira-key="BBPRO2BUG-21515"> <a href="https://jira.realtek.com/browse/BBPRO2BUG-21515" class="jira-issue-key"><span class="aui-icon aui-icon-wait issue-placeholder"></span>BBPRO2BUG-21515</a> - <span class="summary">Getting issue details...</span> <span class="aui-lozenge aui-lozenge-subtle aui-lozenge-default issue-placeholder">STATUS</span> </span>**
|
||||
|
||||
|
||||
|
||||
#### 1.5 Third Party页面配置GFPS参数
|
||||
|
||||
在Third Party页面配置GFPS参数，详细信息参考 <a href="https://wiki.realtek.com/pages/viewpage.action?pageId=158870786" rel="nofollow">mcu cfg tool中 GFPS 各配置项的含义 - BT_Market - WIKI</a>
|
||||
|
||||
|
||||
|
||||
下面是RTK已通过认证的Module ID
|
||||
|
||||
[认证结果及认证通过的model_id 和key](/pages/viewpage.action?pageId=204620689)
|
||||
|
||||
#### 1.6 配置GFPS findme voice prompt tone
|
||||
|
||||
<a href="#" class="unresolved">gfps_findme.wav</a>
|
||||
|
||||
自行选择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测试环境搭建(<span style="color: rgb(255,0,0);">只有TWS耳机需要做GFPS battery测试，single mode 不需要测试</span>)
|
||||
|
||||
Note：
|
||||
|
||||
测试battery的时候需要搭配充电盒
|
||||
|
||||
#### 2.1.mcu config tool 配置：
|
||||
|
||||
##### 2.1.1 HW Feature 模块
|
||||
|
||||
勾选Charger功能：
|
||||
|
||||
|
||||
|
||||
勾选支持充电盒功能，<span style="color: rgb(255,0,0);">注意如果充电盒image烧录的是20ms,下面红色框中的40ms也要改成20ms,这个要和充电盒image匹配的。</span>
|
||||
|
||||
<span style="color: rgb(255,0,0);">如果充电盒image 烧录的是40ms：</span>
|
||||
|
||||
|
||||
|
||||
如果充电盒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
|
||||
|
||||
<a href="/download/attachments/139180496/GFPS_Left.rcfg?version=1&modificationDate=1636711808317&api=v2" data-linked-resource-container-id="139180496" data-linked-resource-container-version="20" data-linked-resource-content-type="application/octet-stream" data-linked-resource-default-alias="GFPS_Left.rcfg" data-linked-resource-id="205658521" data-linked-resource-type="attachment" data-linked-resource-version="1">GFPS_Left.rcfg</a>
|
||||
|
||||
<a href="/download/attachments/139180496/GFPS_Right.rcfg?version=1&modificationDate=1636711808877&api=v2" data-linked-resource-container-id="139180496" data-linked-resource-container-version="20" data-linked-resource-content-type="application/octet-stream" data-linked-resource-default-alias="GFPS_Right.rcfg" data-linked-resource-id="205658522" data-linked-resource-type="attachment" data-linked-resource-version="1">GFPS_Right.rcfg</a>
|
||||
|
||||
\
|
||||
|
||||
### 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 (**<span style="color: rgb(255,0,0);">这边取名字为CSIP取的有点问题，实际是想声明是否支援LE audio, 后面会请tool 帮忙把CSIP 改成LE audio</span>**)，
|
||||
|
||||
**<span style="color: rgb(255,0,0);">如果找不到 Dual mode device with CSIP 应该是 新的 mcu cfg tool 有改名字将 CSIP 统一改成 LE audio了， tool上可以设置成 Dual mode device with LE audio</span>**
|
||||
|
||||
<a href="https://jira.realtek.com/browse/BTSOCTOOL-5234" class="external-link" rel="nofollow" title="https://jira.realtek.com/browse/btsoctool-5234">[BTSOCTOOL-5234] GFPS页面CSIP改成LE audio - Jira</a>
|
||||
|
||||
|
||||
|
||||
\
|
||||
|
||||
#### 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 提示音
|
||||
|
||||
|
||||
|
||||
\
|
||||
181
3.2.2+手机端环境搭建.md
Normal file
181
3.2.2+手机端环境搭建.md
Normal file
@@ -0,0 +1,181 @@
|
||||
# 3.2.2 手机端环境搭建
|
||||
|
||||
<style type="text/css">/**/
|
||||
div.rbtoc1777701137807 {padding: 0px;}
|
||||
div.rbtoc1777701137807 ul {margin-left: 0px;}
|
||||
div.rbtoc1777701137807 li {margin-left: 0px;padding-left: 0px;}
|
||||
|
||||
/**/</style>
|
||||
|
||||
<div class="toc-macro rbtoc1777701137807">
|
||||
|
||||
- [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功能)
|
||||
|
||||
</div>
|
||||
|
||||
\
|
||||
|
||||
该测试至少要准备两只手机。测试手机建议使用Google pixel手机，<span style="color: rgb(32,33,36);"> Pixel 5+ is recommended. </span>请<span style="color: rgb(255,0,0);">**务必确保**</span>手机端有打开开发者选项 <a href="https://developer.android.com/studio/debug/dev-options?hl=zh-cn" class="external-link" rel="nofollow">https://developer.android.com/studio/debug/dev-options?hl=zh-cn</a>
|
||||
|
||||
\
|
||||
|
||||
### GFPS 环境搭建
|
||||
|
||||
#### 1.手机需要连接google网络
|
||||
|
||||
该网络必须可以登陆google的网站，在测试前请先测试一下是否可以登录google的网站(<span style="color: rgb(255,0,0);">**建议试试能不能打开youtube之类的**</span>）。
|
||||
|
||||
#### 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(<span style="color: rgb(255,0,0);">内部</span><span style="color: rgb(255,0,0);">账号(不可给客户)：</span>
|
||||
|
||||
<span style="color: rgb(255,0,0);"><span style="color: rgb(0,0,0);"><span style="color: rgb(255,0,0);"><span style="color: rgb(23,43,77);"><span style="color: rgb(0,0,0);"><span style="color: rgb(255,0,0);">Fast Pair Validator 测试 请使用 </span></span></span></span></span></span><span style="color: rgb(255,0,0);"><a href="mailto:realsilbt8888@gmail.com" class="external-link" rel="nofollow">realsilbt8888@gmail.com</a><span style="color: rgb(23,43,77);"> </span><span style="color: rgb(23,43,77);"> </span></span>
|
||||
|
||||
<span style="color: rgb(255,0,0);"><span style="color: rgb(23,43,77);">手动测试账号请参考 <span style="color: rgb(255,0,0);"><a href="https://wiki.realtek.com/pages/viewpage.action?pageId=394285307" rel="nofollow">Google 账号 - BT_Market - WIKI (realtek.com)</a> </span></span></span>
|
||||
|
||||
#### 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”
|
||||
|
||||
|
||||
|
||||
<a href="https://developer.android.com/studio/debug/dev-options?hl=zh-cn" class="external-link" rel="nofollow">https://developer.android.com/studio/debug/dev-options?hl=zh-cn</a>
|
||||
|
||||
#### <span class="devsite-heading">10.Check Google Play Service version</span>
|
||||
|
||||
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).
|
||||
|
||||
|
||||
|
||||
\
|
||||
|
||||
\
|
||||
|
||||
#### **<span style="color: rgb(255,0,0);">11.注册成为google beta tester（内部测试账号已经注册过了，这一步不需要，如果是客户自己注册的Google账号，需要提醒客户check）</span>**
|
||||
|
||||
Sign up for the Google Play services beta program <a href="https://play.google.com/apps/testing/com.google.android.gms" class="external-link" rel="nofollow">https://play.google.com/apps/testing/com.google.android.gms</a>
|
||||
|
||||
join the Android Beta group at <a href="https://www.google.com/android/beta" class="external-link" rel="nofollow"><span>https://www.google.com/android/beta</span></a> to get latest update via OTA
|
||||
|
||||
Finder/Find Hub testing program please Navigate to <a href="https://play.google.com/apps/testing/com.google.android.apps.adm" class="external-link" rel="nofollow">https://play.google.com/apps/testing/com.google.android.apps.adm</a>
|
||||
|
||||
\
|
||||
|
||||
可以登陆Google账号之后在以下链接查看是否有添加成功：<a href="https://groups.google.com/my-groups" class="external-link" rel="nofollow">我的群组</a>
|
||||
|
||||
|
||||
|
||||
需要注意的是：
|
||||
|
||||
|
||||
|
||||
如果没有权限添加，FAE需要联系YingTsung (YT) Lin， 请他发邮件给Google， 让Google把客户注册的Google账号添加到Google的Test group。
|
||||
|
||||
\
|
||||
|
||||
### GFPS LEA 环境搭建
|
||||
|
||||
#### 1 <a href="https://www.google.com/android/beta" class="external-link" rel="nofollow" style="text-decoration: none;">https://www.google.com/android/beta</a> your google account will need to join the Android Beta group to get the T-QPR2 release.(<span style="color: rgb(255,0,0);"> pixel7、pixel7 Pro 在<a href="mailto:realsilbt8888@gmail.com" class="external-link" rel="nofollow">realsilbt8888@gmail.com</a> 上已经注册，场内QC测试可以不用关心这一步， **FAE需要提醒客户自查**</span>)
|
||||
|
||||
<a href="https://developer.android.com/about/versions/13/release-notes?hl=zh-cn" class="external-link" rel="nofollow">https://developer.android.com/about/versions/13/release-notes?hl=zh-cn</a>
|
||||
|
||||
|
||||
|
||||
#### <span style="color: rgb(32,33,36);">\
|
||||
2 setting 界面 enable LE audio功能</span>
|
||||
|
||||
<span style="color: rgb(32,33,36);"> Here is the setting of LE Audio in phone, if you don't see it, please follow below link to enable "Developer options". <a href="https://developer.android.com/studio/debug/dev-options" class="external-link" rel="nofollow" style="text-decoration: none;">https://developer.android.com/studio/debug/dev-options</a></span>
|
||||
|
||||
<span style="color: rgb(32,33,36);"></span>
|
||||
|
||||
\
|
||||
|
||||
\
|
||||
|
||||
\
|
||||
|
||||
\
|
||||
282
3.2.3+Fast+Pair+Validator+环境搭建.md
Normal file
282
3.2.3+Fast+Pair+Validator+环境搭建.md
Normal file
@@ -0,0 +1,282 @@
|
||||
# 3.2.3 Fast Pair Validator 环境搭建
|
||||
|
||||
<span style="color: rgb(0,0,0);"></span><style type="text/css">/**/
|
||||
div.rbtoc1777701144315 {padding: 0px;}
|
||||
div.rbtoc1777701144315 ul {margin-left: 0px;}
|
||||
div.rbtoc1777701144315 li {margin-left: 0px;padding-left: 0px;}
|
||||
|
||||
/**/</style>
|
||||
|
||||
<div class="toc-macro rbtoc1777701144315">
|
||||
|
||||
- [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不需要关注，如果是客户自己注册的账号，需要提醒客户添加))
|
||||
|
||||
</div>
|
||||
|
||||
### <span style="color: rgb(0,0,0);">1 搭建手机端的测试环境</span>
|
||||
|
||||
测试手机建议使用Google pixel手机，请<span style="color: rgb(255,0,0);">**务必确保**</span>手机端有打开开发者选项 <a href="https://developer.android.com/studio/debug/dev-options?hl=zh-cn" class="external-link" rel="nofollow">https://developer.android.com/studio/debug/dev-options?hl=zh-cn</a>
|
||||
|
||||
\
|
||||
|
||||
#### 1.1 手机需要连接google网络
|
||||
|
||||
该网络必须可以登陆google的网站，在测试前请先测试一下是否可以登录google的网站(<span style="color: rgb(255,0,0);">**建议试试能不能打开youtube之类的**</span>）。
|
||||
|
||||
#### 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(<span style="color: rgb(255,0,0);">内部</span><span style="color: rgb(255,0,0);">账号(不可给客户)：</span>
|
||||
|
||||
<span style="color: rgb(255,0,0);"><span style="color: rgb(0,0,0);"><span style="color: rgb(255,0,0);"><span style="color: rgb(23,43,77);"><span style="color: rgb(0,0,0);"><span style="color: rgb(255,0,0);">Fast Pair Validator 测试 请使用 </span></span></span></span></span></span><span style="color: rgb(255,0,0);"><a href="mailto:realsilbt8888@gmail.com" class="external-link" rel="nofollow">realsilbt8888@gmail.com</a><span style="color: rgb(23,43,77);"> </span><span style="color: rgb(23,43,77);"> </span></span>
|
||||
|
||||
<span style="color: rgb(255,0,0);"><span style="color: rgb(23,43,77);">手动测试账号请参考 <span style="color: rgb(255,0,0);"><a href="https://wiki.realtek.com/pages/viewpage.action?pageId=394285307" rel="nofollow">Google 账号 - BT_Market - WIKI (realtek.com)</a> </span></span></span>
|
||||
|
||||
#### 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
|
||||
|
||||
**<span style="color: rgb(255,0,0);">Note: 只有realsilbt8888的账号需要关掉 Automatically save devices， 其他手动测试的账号Automatically save devices需要打开</span>**
|
||||
|
||||
|
||||
|
||||
\
|
||||
|
||||
#### 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”
|
||||
|
||||
|
||||
|
||||
<a href="https://developer.android.com/studio/debug/dev-options?hl=zh-cn" class="external-link" rel="nofollow">https://developer.android.com/studio/debug/dev-options?hl=zh-cn</a>
|
||||
|
||||
#### <span class="devsite-heading">1.10 Check Google Play Service version</span>
|
||||
|
||||
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).
|
||||
|
||||
|
||||
|
||||
\
|
||||
|
||||
\
|
||||
|
||||
#### **<span style="color: rgb(255,0,0);">1.11 注册成为google beta tester（内部测试账号已经注册过了，这一步不需要，如果是客户自己注册的Google账号，需要提醒客户check）</span>**
|
||||
|
||||
Sign up for the Google Play services beta program\
|
||||
<a href="https://play.google.com/apps/testing/com.google.android.gms" class="external-link" rel="nofollow">https://play.google.com/apps/testing/com.google.android.gms</a>
|
||||
|
||||
join the Android Beta group at <a href="https://www.google.com/android/beta" class="external-link" rel="nofollow"><span>https://www.google.com/android/beta</span></a> to get latest update via OTA
|
||||
|
||||
Finder/Find Hub testing program please Navigate to <a href="https://play.google.com/apps/testing/com.google.android.apps.adm" class="external-link" rel="nofollow">https://play.google.com/apps/testing/com.google.android.apps.adm</a>
|
||||
|
||||
如果没有权限添加，FAE需要联系YingTsung (YT) Lin， 请他发邮件给Google， 让Google把客户注册的Google账号添加到Google的Test group。
|
||||
|
||||
可以登陆Google账号之后在以下链接查看是否有添加成功：<a href="https://groups.google.com/my-groups" class="external-link" rel="nofollow">我的群组</a>
|
||||
|
||||
|
||||
|
||||
需要注意的是：
|
||||
|
||||
|
||||
|
||||
### **<span style="color: rgb(153,51,0);">2 Fast Pair Validator APP安装</span>**
|
||||
|
||||
确认手机是否安装 Fast Pair Validator APP
|
||||
|
||||
<span style="color: rgb(0,0,0);">Fast pair validator app 图标如下图：</span>
|
||||
|
||||
<span style="color: rgb(153,51,0);"></span>
|
||||
|
||||
如果没有安装:
|
||||
|
||||
去 Play Store/应用商店 下载 <span style="color: rgb(0,0,0);">Fast Pair Validator APP并且安装。</span>
|
||||
|
||||
如果已经安装:
|
||||
|
||||
确认安装的是否是最新版。不是最新版，请手动升级到最新版。确认步骤如下：
|
||||
|
||||
长按 Fast Pair Validator 图标，会看到App info
|
||||
|
||||
|
||||
|
||||
点击App info,会看到App details
|
||||
|
||||
|
||||
|
||||
点击App details,会看到以下页面，如果有新版本请手动更新到最新的版本。如果是beta版本则不需要更新，系统会自动帮忙更新。
|
||||
|
||||
|
||||
|
||||
### <span style="color: rgb(153,51,0);">3 </span><span style="color: rgb(153,51,0);">Enable fast pair validator app中的测项</span>
|
||||
|
||||
#### <span style="color: rgb(32,33,36);"><span style="color: black;">3.1 安装adb:</span></span>
|
||||
|
||||
<span style="color: rgb(32,33,36);"><span style="color: black;"><a href="https://wiki.realtek.com/pages/viewpage.action?pageId=87464469" rel="nofollow">adb安装及使用方法</a> 该wiki上提供的adb版本太旧，会出现device offline的问题，下载最新的<a href="https://adbshell.com/downloads" class="external-link" rel="nofollow">https://adbshell.com/downloads</a></span></span>
|
||||
|
||||
<span style="color: rgb(32,33,36);">安装adb之后找到adb.exe所在的目录，在该目录下打开cmd命令行</span>
|
||||
|
||||
#### 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
|
||||
|
||||
\
|
||||
|
||||
### <span style="color: rgb(0,0,0);">4 uninstall amazon 相关app</span>
|
||||
|
||||
<span style="color: rgb(0,0,0);">Alexa (com.amazon.dee.app) 和com.amazon.wellness app， 会影响到Validator的测试，需要Uninstall。</span>
|
||||
|
||||
<span style="color: rgb(0,0,0);">The Alexa (com.amazon.dee.app) took too much time on handling the ACL_CONNECTED intent, which impacts the Validator's flow.</span>
|
||||
|
||||
<span style="color: rgb(0,0,0);">There is still another **app,com.amazon.wellness** app, who handled ACL_CONNECTED for 20+ seconds.Please uninstall it as well.</span>
|
||||
|
||||
<span style="color: rgb(255,0,0);">现象： End-to-end integration测试，出现Pairing timeout</span>
|
||||
|
||||
<span style="color: rgb(255,0,0);">操作方式： </span>
|
||||
|
||||
<span style="color: rgb(255,0,0);">adb uninstall com.amazon.wellness</span>
|
||||
|
||||
<span style="color: rgb(255,0,0);">adb uninstall com.amazon.dee.app</span>
|
||||
|
||||
\
|
||||
|
||||
### <span style="color: rgb(153,51,0);">5 测试账号和MODEL ID</span>
|
||||
|
||||
使用Fast Pair Validator测试，需要先登陆Google账号，测试设备使用的Model ID,public key, private key 必须是该google账号注册的Device。
|
||||
|
||||
场内测试账号：<a href="mailto:realsilbt8888@gmail.com" class="external-link" rel="nofollow">realsilbt8888@gmail.com</a>
|
||||
|
||||
**<span style="color: rgb(255,0,0);">Note：</span>**
|
||||
|
||||
fast pair validator app使用的model id 要和DUT开发板配置的model id一致。
|
||||
|
||||
|
||||
|
||||
### **<span style="color: rgb(153,51,0);">6 测试准备</span>**
|
||||
|
||||
测试过程中需要注意
|
||||
|
||||
<span style="color: rgb(255,0,0);">手机端弹出配对提示框时不要手动点击，fast pair validator app会自己触发配对</span>.
|
||||
|
||||
开始测试前，需要确认是否已经和待测试耳机配对过，需要删除配对信息。 最后最好在开始测试前，开关一下飞行模式。
|
||||
|
||||
点击GOT IT开始测试时，耳机端一定要处于Pairable mode，否则会scan不到设备, scan 到设备后，点击Test开始测试。
|
||||
|
||||
|
||||
|
||||
\
|
||||
|
||||
### 7 GFPS LEA 环境搭建
|
||||
|
||||
#### 1 官网测试spec请参考 <a href="https://developers.google.com/nearby/fast-pair/lea-validator-app-user-manual" class="external-link" rel="nofollow">https://developers.google.com/nearby/fast-pair/lea-validator-app-user-manual</a>
|
||||
|
||||
#### 2 setting 界面需要 enable Bypass Bluetooth LE audio，然后重启手机
|
||||
|
||||
|
||||
|
||||
#### 3 Google 提供的文档 <a href="#" class="unresolved">[RealTek] Validator App LE Spec User Manual.pptx</a>
|
||||
|
||||
#### 4 测试账号需要加入Google test group(<span style="color: rgb(255,0,0);">**内部测试账号已添加，qc不需要关注，如果是客户自己注册的账号，需要提醒客户添加**</span>)
|
||||
|
||||
- Ensure your testing emails are part of the <a href="mailto:fast-pair-integrations@google.com" class="external-link" rel="nofollow">Fast Pair Partner Testing Group</a>.
|
||||
|
||||
- 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.
|
||||
|
||||
\
|
||||
21
3.3+测试.md
Normal file
21
3.3+测试.md
Normal file
@@ -0,0 +1,21 @@
|
||||
# 3.3 测试
|
||||
|
||||
测试完成之后要填写测试报告, 测试报告从以下位置获取：
|
||||
|
||||
<a href="https://wiki.realtek.com/display/BT/Test+Case+of+the+Third+Party" rel="nofollow">Test Case of the Third Party - BT Test - WIKI</a>
|
||||
|
||||
|
||||
|
||||
\
|
||||
|
||||
因为设备不支援find hub(类似于苹果的findmy功能)， 所以测试报告中：
|
||||
|
||||
Find My Device 那一页不需要测试：
|
||||
|
||||
|
||||
|
||||
\
|
||||
|
||||
Fast Pair Validator那一页 EDDYSTONE 下面的测项不需要测试：
|
||||
|
||||
|
||||
11
3.3.1+Fast+Pair+Validator+测试.md
Normal file
11
3.3.1+Fast+Pair+Validator+测试.md
Normal file
@@ -0,0 +1,11 @@
|
||||
# 3.3.1 Fast Pair Validator 测试
|
||||
|
||||
<span class="plugin_pagetree_children_span">3<a href="https://wiki.realtek.com/display/BTMKT/1.3.1.1+FAST+PAIR?src=contextnavpagetreemode" rel="nofollow">.3.1.1 FAST PAIR</a> </span>
|
||||
|
||||
<span class="plugin_pagetree_children_span" style="color: rgb(255,0,0);">这个测项客户自测并且提交测试结果到Google云端，认证实验室暂时不会测试。</span>
|
||||
|
||||
<span class="plugin_pagetree_children_span">目前来看只要有一次测试成功，并且有提交成功的测试结果到Google云端就可以，即使偶尔失败了，如果确定不是我们设备端的bug, 也没关系的</span>
|
||||
|
||||
<span class="plugin_pagetree_children_span"><a href="https://partnerissuetracker.corp.google.com/u/0/issues/473688165" class="external-link" rel="nofollow">https://partnerissuetracker.corp.google.com/u/0/issues/473688165</a></span>
|
||||
|
||||
<span class="plugin_pagetree_children_span"></span>
|
||||
7
3.3.1.1+FAST+PAIR.md
Normal file
7
3.3.1.1+FAST+PAIR.md
Normal file
@@ -0,0 +1,7 @@
|
||||
# 3.3.1.1 FAST PAIR
|
||||
|
||||
请参考以下Wiki 进行测试：
|
||||
|
||||
<a href="https://wiki.realtek.com/pages/viewpage.action?pageId=431431640" rel="nofollow">2 fast pair validator 测试-LE Flow - BT_Market - WIKI</a>
|
||||
|
||||
|
||||
1
3.3.2+手动测试.md
Normal file
1
3.3.2+手动测试.md
Normal file
@@ -0,0 +1 @@
|
||||
# 3.3.2 手动测试
|
||||
9
3.3.2.1+Initial+pair+and+subsequent+pair.md
Normal file
9
3.3.2.1+Initial+pair+and+subsequent+pair.md
Normal file
@@ -0,0 +1,9 @@
|
||||
# 3.3.2.1 Initial pair and subsequent pair
|
||||
|
||||
google 官方测试文档：
|
||||
|
||||
<a href="https://developers.google.com/nearby/fast-pair/fast-pair-certification-guideline#22_notification_popup_for_initial_pairing" class="external-link" rel="nofollow" style="">Fast Pair 3.2 & 3.3 Certification Guidelines | Google for Developers</a>
|
||||
|
||||
Realtek内部整理文档：
|
||||
|
||||
<a href="https://wiki.realtek.com/pages/viewpage.action?pageId=288810503" rel="nofollow" style="">1 Initial Pairing and Subsequent Pairing Test Guideline(中文文档) - BT_Market - WIKI</a>
|
||||
9
3.3.2.2+extended+feature.md
Normal file
9
3.3.2.2+extended+feature.md
Normal file
@@ -0,0 +1,9 @@
|
||||
# 3.3.2.2 extended feature
|
||||
|
||||
Google 官方文档：
|
||||
|
||||
<a href="https://developers.google.com/nearby/fast-pair/fast-pair-certification-guideline#4_feature_certification_criteria" class="external-link" rel="nofollow" style="">https://developers.google.com/nearby/fast-pair/fast-pair-certification-guideline#4_feature_certification_criteria</a>
|
||||
|
||||
Realtek 内部整理文档：
|
||||
|
||||
<a href="https://wiki.realtek.com/pages/viewpage.action?pageId=374584696" rel="nofollow" style="">1 Extension Feature Test Guideline(中文文档) - BT_Market - WIKI</a>
|
||||
1
4+GFPS+LEA+配对主耳之后没有配对附耳.md
Normal file
1
4+GFPS+LEA+配对主耳之后没有配对附耳.md
Normal file
@@ -0,0 +1 @@
|
||||
# 4 GFPS LEA 配对主耳之后没有配对附耳
|
||||
5
4+GFPS显示名字不是mcu+config+tool+里面设置的名字问题.md
Normal file
5
4+GFPS显示名字不是mcu+config+tool+里面设置的名字问题.md
Normal file
@@ -0,0 +1,5 @@
|
||||
# 4 GFPS显示名字不是mcu config tool 里面设置的名字问题
|
||||
|
||||
**<span style="color: rgb(255,0,0);">Q:</span>**GFPS显示的名字为什么不是mcu config tool 里面设置的名字
|
||||
|
||||
<span style="color: rgb(255,0,0);">**A:**</span>GFPS显示的名字是注册model id时设置的名字，和mcu config tool 中设置的名字没有关系。可以在setting界面修改该名字
|
||||
3
4+LEA+++GFPS+++Find+Hub.md
Normal file
3
4+LEA+++GFPS+++Find+Hub.md
Normal file
@@ -0,0 +1,3 @@
|
||||
# 4 LEA + GFPS + Find Hub
|
||||
|
||||
<span style="color: rgb(23,43,77);">该功能是通过GFPS 快速配对 LE audio， 如果同时支援BREDR， 会通过LE 的 LTK CTKD 生成 BREDR 的 linkkey, 并实现查找功能(类似于苹果的findmy)</span>
|
||||
21
4+pixel6(android+12)+不连A2DP.md
Normal file
21
4+pixel6(android+12)+不连A2DP.md
Normal file
@@ -0,0 +1,21 @@
|
||||
# 4 pixel6(android 12) 不连A2DP
|
||||
|
||||
<a href="https://jira.realtek.com/browse/BB2BUG-50550" class="external-link" rel="nofollow">[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</a>
|
||||
|
||||
测试把legacy CTKD LE关掉就可以
|
||||
|
||||
<a href="https://partnerissuetracker.corp.google.com/u/0/issues/427370430" class="external-link" rel="nofollow">https://partnerissuetracker.corp.google.com/u/0/issues/427370430</a>
|
||||
|
||||
\
|
||||
|
||||
这个问题Google最终给出的解决方案是：
|
||||
|
||||
device console 上面会提供一个选项 “是否支援 legacy CTKD le功能”，
|
||||
|
||||
如果客户注册model id的时候有勾选这个功能，
|
||||
|
||||
Android 12 的pixel手机扫到这个model id对应的设备之后就不会弹窗出来，客户需要去setting界面配对
|
||||
|
||||
\
|
||||
|
||||
+不连A2DP_3e6271b1.jpg)
|
||||
9
4+弹框提示_无法连接到查找中心_.md
Normal file
9
4+弹框提示_无法连接到查找中心_.md
Normal file
@@ -0,0 +1,9 @@
|
||||
# 4 弹框提示"无法连接到查找中心"
|
||||
|
||||
legacy GFPS 要打开legacy CTKD LE功能，不然搭配支援lea的手机测试，会出现手机不连legacy profile的情况
|
||||
|
||||
|
||||
|
||||
\
|
||||
|
||||
<a href="https://jira.realtek.com/browse/BBPRO3BUG-24407" class="external-link" rel="nofollow">[BBPRO3BUG-24407] [BBPRO3][EVB][E Cut][3.15.0.5+TestBin][Single]配置Finder，耳机开机进配对，无法连接到Find Device - Jira</a>
|
||||
42
4.1+Observed+standard+deviation+is+too+low,+.........md
Normal file
42
4.1+Observed+standard+deviation+is+too+low,+.........md
Normal file
@@ -0,0 +1,42 @@
|
||||
# 4.1 Observed standard deviation is too low, ........
|
||||
|
||||
<span class="jira-issue resolved" jira-key="BB2BUG-17449"> <a href="https://jira.realtek.com/browse/BB2BUG-17449" class="jira-issue-key"><img src="https://jira.realtek.com/secure/viewavatar?size=xsmall&avatarId=10916&avatarType=issuetype" />BB2BUG-17449</a> - <span class="summary">\[BB2\]\[RTL8763EF/ROM\]\[GMI\]\[沃莱特\]\[Harman\]\[T520\]: Finder测项中，finder_advertisement rotation测试失败</span> <span class="aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf">Closed</span> </span>
|
||||
|
||||
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?
|
||||
|
||||
\
|
||||
|
||||
<a href="mailto:dlazarov@google.com" class="external-link" rel="nofollow">+David Lazarov</a> 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.*
|
||||
|
||||
\
|
||||
59
4.1+Project+工程enable对应功能.md
Normal file
59
4.1+Project+工程enable对应功能.md
Normal file
@@ -0,0 +1,59 @@
|
||||
# 4.1 Project 工程enable对应功能
|
||||
|
||||
<span style="color: rgb(166,38,164);">app_flags.h 里面找到 <span style="color: rgb(64,120,242);">CONFIG_REALTEK_GFPS_XXX 相关的宏并按照以下信息配置</span>：</span>
|
||||
|
||||
<span style="color: rgb(166,38,164);">\#define</span><span style="color: rgb(56,58,66);"> </span><span style="color: rgb(64,120,242);">CONFIG_REALTEK_GFPS_FEATURE_SUPPORT</span><span style="color: rgb(56,58,66);"> </span><span style="color: rgb(152,104,1);">1</span>\
|
||||
<span style="color: rgb(166,38,164);">\#define</span><span style="color: rgb(56,58,66);"> </span><span style="color: rgb(64,120,242);">CONFIG_REALTEK_GFPS_LE_DEVICE_SUPPORT</span><span style="color: rgb(56,58,66);"> (1 && </span><span style="color: rgb(64,120,242);">CONFIG_REALTEK_GFPS_FEATURE_SUPPORT</span><span style="color: rgb(56,58,66);">)</span>\
|
||||
<span style="color: rgb(166,38,164);">\#define</span><span style="color: rgb(56,58,66);"> </span><span style="color: rgb(64,120,242);">CONFIG_REALTEK_GFPS_SASS_SUPPORT</span><span style="color: rgb(56,58,66);"> (0 && </span><span style="color: rgb(64,120,242);">CONFIG_REALTEK_GFPS_FEATURE_SUPPORT</span><span style="color: rgb(56,58,66);">)</span>\
|
||||
<span style="color: rgb(166,38,164);">\#define</span><span style="color: rgb(56,58,66);"> </span><span style="color: rgb(64,120,242);">CONFIG_REALTEK_GFPS_FINDER_SUPPORT</span><span style="color: rgb(56,58,66);"> (1 && </span><span style="color: rgb(64,120,242);">CONFIG_REALTEK_GFPS_FEATURE_SUPPORT</span><span style="color: rgb(56,58,66);">)</span>
|
||||
|
||||
<span style="color: rgb(56,58,66);">GFPS依赖的其他的模块：</span>
|
||||
|
||||
\#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
|
||||
|
||||
\
|
||||
|
||||
<span style="color: rgb(152,104,1);">Note:</span>
|
||||
|
||||
<span style="color: rgb(152,104,1);">有的IC宏的名字是GFPS_XXX, <span style="color: rgb(166,38,164);">app_flags.h 里面找到 <span style="color: rgb(64,120,242);">GFPS_XXX 相关的宏并按照以下信息配置</span>：</span></span>
|
||||
|
||||
<span style="color: rgb(166,38,164);">\#define</span><span style="color: rgb(56,58,66);"> </span><span style="color: rgb(64,120,242);">GFPS_FEATURE_SUPPORT</span><span style="color: rgb(56,58,66);"> </span><span style="color: rgb(152,104,1);">1</span>\
|
||||
<span style="color: rgb(166,38,164);">\#define</span><span style="color: rgb(56,58,66);"> </span><span style="color: rgb(64,120,242);">GFPS_LE_DEVICE_SUPPORT</span><span style="color: rgb(56,58,66);"> (1 && </span><span style="color: rgb(64,120,242);">GFPS_FEATURE_SUPPORT</span><span style="color: rgb(56,58,66);">)</span>\
|
||||
<span style="color: rgb(166,38,164);">\#define</span><span style="color: rgb(56,58,66);"> </span><span style="color: rgb(64,120,242);">GFPS_SASS_SUPPORT</span><span style="color: rgb(56,58,66);"> (0 && </span><span style="color: rgb(64,120,242);">GFPS_FEATURE_SUPPORT</span><span style="color: rgb(56,58,66);">)</span>\
|
||||
<span style="color: rgb(166,38,164);">\#define</span><span style="color: rgb(56,58,66);"> </span><span style="color: rgb(64,120,242);">GFPS_FINDER_SUPPORT</span><span style="color: rgb(56,58,66);"> (1 && </span><span style="color: rgb(64,120,242);">GFPS_FEATURE_SUPPORT</span><span style="color: rgb(56,58,66);">)</span>
|
||||
|
||||
<span style="color: rgb(56,58,66);">GFPS依赖的其他的模块：</span>
|
||||
|
||||
\#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
|
||||
Some files were not shown because too many files have changed in this diff Show More
Reference in New Issue
Block a user