1088644 - Bluetooth is not deactivated after file transfer initiated by NFC in 2.1

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: NFC, defect)

Description

[Stephanie Ouillon [:arroway] (needinfo me)]

Build Information
Gaia-Rev        1e48e3e40e0780c0cd07a3457e5fe2efeeb542d1
Gecko-Rev       https://hg.mozilla.org/releases/mozilla-b2g34_v2_1/rev/09fb60a37850
Build-ID        20141023001201
Version         34.0
Device-Name     flame
Base image: ***Please update this field to say if you're running the v180 or the v188 base image***


Description
If Bluetooth was initially turned off by the user, it shouldn't be left as turned on after a file transfer initiated by NFC.

Steps to Reproduce
1. Turn off bluetooth
2. Turn on NFC 
3. Share a file (picture, video) with NFC by tapping two phones together

Expected Results
After the file transfer is completed, BT should be turned off again.

Actual Results
BT is turned on, and the device to which the file was sent to is shown in the paired devices list in the Bluetooth menu.

Other Notes
This is a regression compared with 2.0, and a security issue since the user is not necessarily aware BT is being used, and devices are being paired permanently.


Reproduction Frequency: always

Comment 1

[Garner Lee]

--> Regression, though it could also be a Bluetooth API/timing change rather than strictly with NFC handover. Arno?

Comment 2

[arno]

I flashed a device with the gecko/gaia versions mentioned in the bug report, however, with that version I was not even able to trigger sharing from an Android device (the Android device kept on saying that the Flame device does not support large file transfers). I suspect this is due to an inconsistent mismatch of components. Stephanie: which versions of the external/bluetooth directories are you using? Please post the info and then ni? echou: so he can verify the versions are consistent.

Comment 3

[Stephanie Ouillon [:arroway] (needinfo me)]

(In reply to arno from comment #2)
> I flashed a device with the gecko/gaia versions mentioned in the bug report,
> however, with that version I was not even able to trigger sharing from an
> Android device (the Android device kept on saying that the Flame device does
> not support large file transfers). I suspect this is due to an inconsistent
> mismatch of components. Stephanie: which versions of the external/bluetooth
> directories are you using? Please post the info and then ni? echou: so he
> can verify the versions are consistent.

I flashed a Flame with the v188 base image, and then flashed the flame-kk nightly-b2g34 2.1 images from pvt builds.

Comment 4

[Tony Chung [:tchung]]

(In reply to Stephanie Ouillon [:arroway] from comment #0)
> Other Notes
> This is a regression compared with 2.0, and a security issue since the user
> is not necessarily aware BT is being used, and devices are being paired
> permanently.
> 
> 
> Reproduction Frequency: always

Qawanted to find if this is a regression, on why BT is turning itself back on after an NFC transfer

Comment 5

[Garner Lee]

My particular build findings: NFC on, BT off starting state.

Just tried it with v188 kk base + latest and greatest Git: gaia=35e87ac4324f0f3abd93dcc70d61c9f37256a0f5, gecko=b5ad3226bcaf6221892c9f438e19771053f07b55, external/bluetooth/bluedroid=30b96dfca99cb384bf520a16b81f3aba56f09907

(There's more, but it's just head revision):

Android --> FirefoxOS ==> BT is off after transfer.
FirefoxOS --> Android ==> BT is off after transfer.

Seems to be okay currently on flame-kk so far.

I know some of us still need the old flame-jb base image...

Useful note to everyone else trying, flame(-jb) is no longer supported. config.sh flame-kk. There's different bluetooth repo in use bluez (jb) --> bluedroid (kk) at the very least.

Comment 6

[Chris Kreinbring [:CKreinbring]]

Unable to repro on Flame 2.2 engineering or Flame 2.1 engineering and nightly.  The nightly builds received a full flash and the engineering builds received a shallow flash.
Actual result: The Bluetooth connection terminates after the device receives a file through an NFC connection.

Flame 2.2 engineering
BuildID: 20141029054810
Gaia: a9a847920b51b79c4ad4ad339f0a005777a6228c
Gecko: c6989e473f97
Platform Version: 36.0a1
Firmware Version: V188
User Agent: Mozilla/5.0 (Mobile; rv:36.0) Gecko/36.0 Firefox/36.0

Flame 2.1 engineering
BuildID: 20141030065818
Gaia: 04379be42b1bf38817370a276d90931b53257706
Gecko: 601d265ad3aa
Platform Version: 34.0
Firmware Version: V188
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0

Flame 2.1 nightly
BuildID: 20141030001201
Gaia: 3e585d8be5e2dffc376f83313299c9b6d53c3db4
Gecko: b643d78a23c6
Gonk: 48835395daa6a49b281db62c50805bd6ca24077e
Platform Version: 34.0
Firmware Version: V188
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0

Flame 2.1, same nightly as original comment
BuildID: 20141023001201
Gaia: 1e48e3e40e0780c0cd07a3457e5fe2efeeb542d1
Gecko: 09fb60a37850
Gonk: 05aa7b98d3f891b334031dc710d48d0d6b82ec1d
Platform Version: 34.0
Firmware Version: V188
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0

Adding a NeedInfo to the reporter for additional steps, possibly setup steps.

Comment 7

[Eric Chou [:ericchou] [:echou]]

Clear my ni per comment 6, and also cc Jamin Liu who is in charge of BT/NFC integration issues for tracking.

Comment 8

[Stephanie Ouillon [:arroway] (needinfo me)]

I followed the standard setup for the bugs bash party: l.110 to l.126 https://etherpad.mozilla.org/b2g-qa-bug-bash-2014-10-23). I will do tests again and post the update.

Comment 9

[Stephanie Ouillon [:arroway] (needinfo me)]

So, the bug is reproduced on:

Flame 2.1 user build
BuildID: 20141031001201
Platform Version: 34.0
Firmware Version: V188

Here are the steps I followed to flash the phone:

1) flash the v188 firmware
2) run ./flash_pvt.py with:
* device (flame-kk)
* nightly-b2g34 branch
* User build
* images

If I choose gecko+gaia, I can't reproduce the bug.
If I flash an engineering build instead of a user build, I can't reproduce it either.

Comment 10

[Pi Wei Cheng [:piwei] (inactive)]

Unable to reproduce the bug on the reported build. Bluetooth does NOT get turned on after sending a photo/video by NFC to another device.

Repro rate: 0/5. Removing related qawanted tags due to inability to repro by multiple parties.

Device: Flame (shallow flash, 512MB mem)
BuildID: 20141023001201
Gaia: 1e48e3e40e0780c0cd07a3457e5fe2efeeb542d1
Gecko: 09fb60a37850 
Version: 34.0 (2.1)
Firmware: V188-1
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0

Comment 11

[BMO Automation]

Firefox OS is not being worked on