AB
1
About this file
2
This file is a branch of a main template file and syncs content from it.
Please refresh the page after you open this file every time to keep it up-to-date.
Last update: 2/14
3
4
Test devices
5
Please prepare 5 Android phones, must include:
at least one Android T(13) and one Android S(12),
at least one Samsung and one Pixel.

For example, 1 OnePlus (Android 10) + 3 Samsung (Android 10, 12, 12) + 1 Pixel (Android 13) are ok.
6
7
Non-SASS device
8
Any iPhone, PC, laptop which support Bluetooth can be used,
or an Android phone which disabled SASS. (turn off by Bluetooth device detail)
Test case 2.8 will need a non-SASS device in addition to the 5 test phones.
9
10
Generic_test and Multipoint_only
11
For singlepoint only headset, only Generic_test needs to be run.
For multipoint only headset, both Generic_test and Multipoint_only need to be run.
If the headset supports multipoint and can be toggled, please run Generic_test with multipoint off, and run Generic_test & Multipoint_only with multipoint on.
12
13
Partner test group
14
Please join https://groups.google.com/g/fp-sass-partner-test with your test accounts.
To show debug notifications on test phones, and we can collect the test data to analytics.
15
16
How to test & fill the form
17
Run all test cases at least twice,
1. Device A=Android S(12) + Device B=Android T(13)
2. Device A=Android T(13) + Device B=Android S(12)

Device B will be the main device under test,
so please fill the "Phone" and "OS" fields on the top of the template with the detail of device B.

For example,
test phones are 1 Samsung (Android 13) and 2 Pixel (Android 12/13) and others,
Run 1. Device A=Samsung S10+ (12), Device B=Pixel 7pro (13)
column D: Phone=Pixel 7pro, OS=Android 13
Run 2. Device A=Pixel 7pro (13), Device B=Pixel 6(12)
column E: Phone=Pixel 6, OS=Android 12

And fill in the result to the corresponding column.
18
19
About seeker apps
20
There are 4 kinds of audio events that will be used in test cases:
Call: Please use the native phone app.
Voip: Can use FP SASS test app. Or FP Messenger, Line, WhatsApp, Google Duo, Google meet...
Media: Can use FP SASS test app. Or Youtube Music, Apple music, Spotify, Google Podcasts...
Game: Please use FP SASS test app.
About FP SASS test app, please refer "Criteria" sheet.
21
22
Debug notification
23
After joining SassPartnerTest(fp-sass-partner-test), you will see a or more debug notification on seeker when there is a SASS headset nearby.
1. Latest state notification:
[Device Name] (red)
[Current state] (green)
Latest state: XX:XX:XX - XX:XX:XX, State: LASTEST_CONNECTION_STATE, other args....

2. No switch notification: (After an audio event happened, show reason if switch was not triggered)
[Device Name] (red)
[No switch reason] (green)
Trigger time: the audio event triggers timestamp
Latest state: the connection state at the time of the audio event happens, NOT the current latest event.

3. Switch latency notification: (After a SASS switch happened, show latency measured by SASS)
[Device Name] (red)
[Latency XXXXms] (green)
Latest switch: XX:XX:XX - XX:XX:XX, latency XXXXms, switch reason.
24
25
Known seeker issue
26
If you meet below problems during test, you can ignore it becasue they are cause by seeker.
1. When playing game on Samsung phones, the connection state will be CONNECTED_A2DP_WITH_AVRCP, instead of CONNECTED_A2DP_ONLY.
2. Some games(e.g. Candy crush) may replay BGM and trigger a new audio event without user input,
in this case if both two phones open the game, they may switch headset connection back from another in turns.
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100