979699 - [Sora][PTS][AVRCP] TC_TG_RCR_BV_02_C & TC_TG_RCR_BV_04_C failed.

Status: RESOLVED INVALID

(Firefox OS Graveyard :: Bluetooth, defect, P1)

Description

[sync-1]

FFOS1.3 Mozilla build ID: 20140208004002
 
 
 Profile Tuning Suite Test Case:
 
 DEFECT DESCRIPTION:
  TC_TG_RCR_BV_02_C & TC_TG_RCR_BV_04_C failed.
 
  REPRODUCING PROCEDURES:
  
 Test case : TC_TG_RCR_BV_02_C started
 	- MTC: SDP Service record was successfully registered.
 	- A2DP SNK SDP Service record successfully registered
 	- A2DP SNKsuccessfully registered
 	- MTC: IUT successfully responded to AVDTP CONNECT.
 	- MTC: IUT successfully accepted AVCTP channel connection.
 	- MTC INCONC: IUT did not respond with enough data to trigger the continuing response, please configure the IUT to respond with more data.
 	- AVDTP: Exiting AVDTP1 PTC
 	- AVCTP: Exiting AVCTP1 PTC
 	- CM_PTC_EXIT
 	- MMI CM_EXIT
 	- MTC: Test case ended
 Final Verdict : Inconclusive
 
 Test case : TC_TG_RCR_BV_04_C started
 	- MTC: SDP Service record was successfully registered.
 	- A2DP SNK SDP Service record successfully registered
 	- A2DP SNKsuccessfully registered
 	- MTC: IUT successfully responded to AVDTP CONNECT.
 	- MTC: IUT successfully accepted AVCTP channel connection.
 	- MTC INCONC: IUT did not respond with enough data to trigger the continuing response, please configure the IUT to respond with more data.
 	- AVDTP: Exiting AVDTP1 PTC
 	- AVCTP: Exiting AVCTP1 PTC
 	- CM_PTC_EXIT
 	- MTC: Test case ended
 Final Verdict : Inconclusive
  
  EXPECTED BEHAVIOUR:
  Expect this case can pass.

Comment 1

[sync-1]

Attachment: Sniffer log.

Comment 2

[Shawn Huang [:shawnjohnjr][:shuang] (as a happy gecko contributor)]

Jamin,
Please help to clarify this bug. I think this shall pass.

Comment 3

[Jason Smith [:jsmith]]

Is this a certification test that has to pass for Bluetooth? Trying to understand if this is a certification blocker for Bluetooth.

Comment 4

[Kunny Liu]

(In reply to Jason Smith [:jsmith] from comment #3)
> Is this a certification test that has to pass for Bluetooth? Trying to
> understand if this is a certification blocker for Bluetooth.


Yes, this a certification test case.

Comment 5

[Jamin Liu [:jaliu][:Jamin]]

Hi reporter,

I've tested it on Sora with gecko v1.3 and both test cases passed.

Would you mind to test it again by following these steps ?
1. Prepare a media file with 512 bytes worth of metadata. [1]
2. Make sure you device has been paired and connected with PTS A2DP profile before.
3. Start to run test case TC_TG_RCR_BV_02_C and follow the instructions.

[1] How to generate a 512 bytes worth of metadata
  The PTS test case ask TG(Target Device) to play a 512 bytes worth of metadata media item.
  However, we can't just put 512 bytes data into a single field, since the length of each field are limited   by Bluez.
  (The maximum of metadata strings is defined at line 155. Even though METADATA_MAX_STRING_LEN is 150, METADATA_MAX_NUMBER_LEN is 40)

  I suggest to fill dummy data to these metadata fields for the media file.
  title -> 150 bytes,
  artist -> 150 bytes,
  album -> 150 bytes,
  media number -> 40 bytes,
  total media count -> 40 bytes,
  playingtime -> few bytes.
  P.S. The data length of 'genre' doesn't count in current Gecko version.

Thank you.

Comment 6

[Jason Smith [:jsmith]]

Clearing nom, as comment 5 indicates we can't reproduce.

Comment 7

[Kunny Liu]

OK, we can pass this case. Thanks!

Comment 8

[John Tobias]

(In reply to Jamin Liu [:jaliu] from comment #5)
> Hi reporter,
> 
> I've tested it on Sora with gecko v1.3 and both test cases passed.
> 
> Would you mind to test it again by following these steps ?
> 1. Prepare a media file with 512 bytes worth of metadata. [1]
> 2. Make sure you device has been paired and connected with PTS A2DP profile
> before.
> 3. Start to run test case TC_TG_RCR_BV_02_C and follow the instructions.
> 
> [1] How to generate a 512 bytes worth of metadata
>   The PTS test case ask TG(Target Device) to play a 512 bytes worth of
> metadata media item.
>   However, we can't just put 512 bytes data into a single field, since the
> length of each field are limited   by Bluez.
>   (The maximum of metadata strings is defined at line 155. Even though
> METADATA_MAX_STRING_LEN is 150, METADATA_MAX_NUMBER_LEN is 40)
> 
>   I suggest to fill dummy data to these metadata fields for the media file.
>   title -> 150 bytes,
>   artist -> 150 bytes,
>   album -> 150 bytes,
>   media number -> 40 bytes,
>   total media count -> 40 bytes,
>   playingtime -> few bytes.
>   P.S. The data length of 'genre' doesn't count in current Gecko version.
> 
> Thank you.


Hi,

I built bluez 5.23 for on non-android device and I've encountered the same problem.
I would like to know what is the command line did you use for creating an metadata and send it to the PTS.

Could you give me some instructions or files?

Regards,

john

Comment 9

[Pham Van Huynh]

(In reply to Kunny Liu from comment #7)
> OK, we can pass this case. Thanks!

Hello Kunny Liu,
Please send for me audio file more than 512 byte meatadata which you pass for this test case or tell to me how to create metadata file.?

Many thanks

Comment 10

[Shawn Huang [:shawnjohnjr][:shuang] (as a happy gecko contributor)]

(In reply to Pham Van Huynh from comment #9)
> (In reply to Kunny Liu from comment #7)
> > OK, we can pass this case. Thanks!
> 
> Hello Kunny Liu,
> Please send for me audio file more than 512 byte meatadata which you pass
> for this test case or tell to me how to create metadata file.?
> 
> Many thanks

You can use any of mp3 ID3 tag editor and add each field with a lot of utf-8 characters.

Comment 11

[Pham Van Huynh]

(In reply to Shawn Huang [:shawnjohnjr] from comment #10)
> (In reply to Pham Van Huynh from comment #9)
> > (In reply to Kunny Liu from comment #7)
> > > OK, we can pass this case. Thanks!
> > 
> > Hello Kunny Liu,
> > Please send for me audio file more than 512 byte meatadata which you pass
> > for this test case or tell to me how to create metadata file.?
> > 
> > Many thanks
> 
> You can use any of mp3 ID3 tag editor and add each field with a lot of utf-8
> characters.

Thanks for your answer. I used EasyTAG to edit metadata file, but It still returns INCONC result "IUT did not respond with enough data to trigger the continuing response, please configure the IUT to respond with more data." If you have metadata file which more than 512 byte, please send for me? I want to again check why PTS return INCONC for this test case.

Comment 12

[Shawn Huang [:shawnjohnjr][:shuang] (as a happy gecko contributor)]

Attachment: yuandeyixinren.mp3

Comment 13

[Shawn Huang [:shawnjohnjr][:shuang] (as a happy gecko contributor)]

Attached files over 512 bytes.

Comment 14

[Pham Van Huynh]

Thanks you very much, but IUT still response INCONC with message "MTC INCONC: IUT did not respond with enough data to trigger the continuing response, please configure the IUT to respond with more data".

Comment 15

[Pham Van Huynh]

Attachment: TC_TG_RCR_BV_02_C_2016_06_28_15_10_41.zip

I attached log for this test case, please check for me?

Comment 16

[Shawn Huang [:shawnjohnjr][:shuang] (as a happy gecko contributor)]

(In reply to Pham Van Huynh from comment #15)
> Created attachment 8765849 [details]
> TC_TG_RCR_BV_02_C_2016_06_28_15_10_41.zip
> 
> I attached log for this test case, please check for me?

Not sure which fxos release do you use? And maybe bug 1142417 may help.

Comment 17

[Pham Van Huynh]

Thanks you for your support. IUT is response "attribute_id:ELEMENT_ATTRIBUTE_ALBUM_NAME,
                                       character_set_id:'006A'O,
                                       attribute_value_length:0,
                                       attribute_value:
                                     }", I think it is issue of stack bluetooth, but I did not find root cause. I refer to bug 1142417, but I don't know how to increase BTRC_MAX_ATTR_STR_LEN in stack?