Files
gfps/Test+case+6_+Clock+sync+fail.md
danni_dong bdbb2527e6
All checks were successful
Sync To /home/ubuntu/gfps / sync (push) Successful in 2s
gfps: 添加认证测试和FAQ 20260505
Change-Id: I71e676b997159a141ca07d16f82a73b45f4b2410
2026-05-05 19:24:08 +08:00

34 lines
875 B
Markdown
Raw Permalink Blame History

This file contains invisible Unicode characters
This file contains invisible Unicode characters that are indistinguishable to humans but may be processed differently by a computer. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# Test case 6: Clock sync fail
Clock sync:
![](images/Test+case+6_+Clock+sync+fail_e6942738.jpg)
hi Avner:
20230630  11:05    success provisioned
20230630  11:42    Fully drain the battery
20230703  09:00    charge the battery
20230703  09:11    Turn on the power and BT connected
20230703  09:30    Open Find my device app, do not see "Nearly"
![](images/Test+case+6_+Clock+sync+fail_d56180fe.jpg)
20230703 09:36     Tap on the device in the list, clock sync fail
![](images/Test+case+6_+Clock+sync+fail_6a35003f.jpg)
\
Hi Danni,
Thank you for the detailed information with timestamps. It's really helpful!
Looks like there was an attempt to sync the clock of the device at 9:11, in which the clock was successfully read. However, there was a problem while processing the update on our end. We're investigating it. I'll keep you posted.
\