1043878 - [NFC] Cannot share files often

Status: RESOLVED DUPLICATE of bug 1043856

(Firefox OS Graveyard :: NFC, defect)

Description

[Alison Shiue]

Gaia      c72257b2d27135bfcd68e89dd584182797784016
Gecko     https://hg.mozilla.org/mozilla-central/rev/616e6924cb0b
BuildID   20140724160202
Version   34.0a1

STR:
Tap 2 phones to share an image

Expected result:
Share successfully

Actual result:
Files cannot be shared easily.

Comment 1

[Alison Shiue]

Attachment: sender_logcat.log

Comment 2

[Alison Shiue]

Attachment: receiver_logcat.log

Comment 3

[Alison Shiue]

Attachment: receiver_hcidump.log

Comment 4

[Alison Shiue]

[Blocking Requested - why for this release]:

Comment 5

[Alison Shiue]

[Blocking Requested - why for this release]: 

2.0 also has this issue. 

Gaia  	0a864988f5dce7f9f3dea9609e8ef054679c30ff
Gecko 	https://hg.mozilla.org/releases/mozilla-b2g32_v2_0/rev/2da96d621030
BuildID   20140727160207
Version   32.0

Comment 6

[Vincent Chang[:vchang][changyihsin]]

After discussing with Yoshi offline, this seems a duplicated of Bug 1043856.

Hi ashiue, can you help to double confirm after Bug 1043856 is fixed.

Comment 7

[Alison Shiue]

Sure, I will try this issue again once Bug 1043856 has been fixed.

Comment 8

[Jason Smith [:jsmith]]

basic use case of a 2.0 feature, so blocking

Comment 9

[Vincent Chang[:vchang][changyihsin]]

Hi Arno, do you mind to take this? Or we can mark it as duplicated of bug 1043856.

Comment 10

[Alison Shiue]

Attachment: nfc_sender_20140811.log

Hi Arno, 

I try full flash 2.0 build
Gaia      de28796a8956a48bb98ca67df6a33e0622d642d1
Gecko     https://hg.mozilla.org/releases/mozilla-b2g32_v2_0/rev/5256345f62bd
BuildID   20140810160202
Version   32.0

After I try transfer file almost 30 times (BT initial off), I encounter a problem that nfc would not turn off sender's BT after a fail transfer, and since then, the device always cannot transfer file successfully unless I reboot sender.

Comment 11

[arno]

(In reply to ashiue from comment #10)
> After I try transfer file almost 30 times (BT initial off), I encounter a
> problem that nfc would not turn off sender's BT after a fail transfer, and
> since then, the device always cannot transfer file successfully unless I
> reboot sender.

Alison: I cannot replicate the problem. When sharing between two Flame devices whose BT is initially off, it is fairly easy to provoke a failed transfer by quickly removing the two devices. But in my tests the sender always correctly turns off BT. The logs you've uploaded don't show debug information from the NFC module so I can't see what is going on. Rebooting the device seems to indicate a deeper problem. Can you please tell me how you manage to provoke the error (quickly remove two devices or something else?). Also: when you come to the point where you have to reboot the sender, can you please try and share a file via BT sharing (without the NFC handover)? If this fails as well, it seems to indicate a problem with the BT layer.

Comment 12

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

Hi arno,
I think this is something relate to bluetooth. I will take the new bug.

Comment 13

[Alison Shiue]

Thanks, Shawn. I file another bug (bug 1052304) for tracking this issue.

Marked this issue as duplicate of bug 1043856 since the latest 2.0 and 2.1 build no longer fail transfer file easily.