1138000 - [FFOS2.0][Woodduck][screen reader]Gsensor devices test fail for MCT

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: Hardware, defect, P2)

Description

[sync-1]

Dear mozilla friends:
      When test Gsensor devices orientations for MCT there always test fails. The test error is expected absolute. What does this meat when the error occur.
 	
 CONTACT INFO (Name,Phone number):
 
  DEFECT DESCRIPTION:
 
  REPRODUCING PROCEDURES:
 
  EXPECTED BEHAVIOUR:
 
  ASSOCIATE SPECIFICATION:
 
  TEST PLAN REFERENCE:
 
  TOOLS AND PLATFORMS USED:
 
  USER IMPACT:
 
  REPRODUCING RATE:
 
  For FT PR, Please list reference mobile's behavior:

Comment 1

[Josh Cheng [:josh]]

Hi Wesly,
Since Woodduck does not have G sensor. The test is expected to be fail. Am I correct?
Thanks!

Comment 2

[Josh Cheng [:josh]]

Also loop Al

Comment 3

[Al Tsai [:atsai]]

Orientation is calculated by accelerator. Therefore, we don't need a G-sensor and still be able to bring the correct orientation to user. I believe there's no reason to waive the failure if there's no more evidence.

Comment 4

[Josh Cheng [:josh]]

Hi Reporter,
Can you attach the test result which we can check? Thanks!

Comment 5

[sync-1]

Created an attachment (id=1180103)
 The test failure
 
 The test failure

Comment 6

[sync-1]

Created an attachment (id=1180103)
 The test failure
 
 The test failure

Comment 7

[sync-1]

Attachment: The test failure

Created an attachment (id=1180103)
 The test failure
 
 The test failure

Comment 8

[sync-1]

Sometimes the error is expected absolute.

Comment 9

[sync-1]

Mozilla friends:
     What about this issue?

Comment 10

[Josh Cheng [:josh]]

Hi Al,
Could you please help to check the issue again?
Thanks!

Comment 11

[sync-1]

Dear mozilla friends:
      We have check it agian for many times,but the result is the same, failure.

Comment 12

[Al Tsai [:atsai]]

I don't have a Fire E device with shipping version now. The only information I have here is some return values of orientation event are missing. There's no such failure on Flame devices. We'll need partner's effort on figuring out the root cause.

Comment 13

[sync-1]

How can we find the root cause? Do you have the suggestion? Where can we write the log and see how the test work?

Comment 14

[Al Tsai [:atsai]]

You can hook eventListener and add logs to the orientationchange event.
https://developer.mozilla.org/zh-TW/docs/WebAPI/Detecting_device_orientation

If you wonder the test work or not, you can trace the code at:
https://github.com/mozilla-b2g/fxos-certsuite/blob/master/webapi_tests/orientation/test_device_orientation.py#L78

Comment 15

[Wesly Huang (EPM)]

Similar case is seen in TCL Fire C and it's because of no e-compass thus no Alpha value returns, in the mean time we expect Beta and Gamma still works. Suggest you can align the experience with [e-mail]. Thanks.

Comment 16

[sync-1]

It has supply waiver, this problem can be closed

Comment 17

[sync-1]

It has supply waiver, this problem can be closed

Comment 18

[Peipei Cheng (needinfo if you need my action)]

close per comment 17