Closed
Bug 932677
Opened 11 years ago
Closed 7 years ago
[Flatfish][bluetooth] unable to transfer file by bluetooth
Categories
(Firefox OS Graveyard :: Gaia::Bluetooth, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
1.3 Sprint 6 - 12/6
People
(Reporter: atsai, Assigned: shawnjohnjr)
Details
(Whiteboard: [Flatfish][TCP][POVB])
STR: 1. Enable bluetooth and pair two phones 2. Send a image from a phone to the Flatfish device by bluetooth Expected Result: *. Flatfish shows a warning page to ask for permission Actual Result: *. nothing happens Gaia: b93de939502cff5dc7ef242a6ec9af34b0864f91 Gecko: 94801a471800e7edcce71fb4d02e89a38d1b99ef BuildID 20131030064537 Version 28.0a1 ** The case is by the testing on Flatfish devices. It might not be able to reproduce on other mobile devices **
Comment 1•11 years ago
|
||
this is function fail, mark it koi+. hi Eric, are you able to fix this bug?
blocking-b2g: --- → koi+
Flags: needinfo?(echou)
Assignee | ||
Updated•11 years ago
|
Assignee: nobody → shuang
Assignee | ||
Comment 2•11 years ago
|
||
Hi Sam, Can you help to confirm backport bluez kernel and userspace had summited to codebase?
blocking-b2g: koi+ → ---
Flags: needinfo?(ckjboy2003)
Assignee | ||
Comment 3•11 years ago
|
||
I'm able to reproduce this bug. The first time you open Gallery and share photo, the Page which you can select to send to device is missing. Workaround is that you can return to "Home" and launch Gallery again. And share photo via Bluetooth File Transfer and then you can find selective devices page. I try with OPP, and function is working. So I think it's problem related to Gallery.
Flags: needinfo?(echou)
Flags: needinfo?(ckjboy2003)
Assignee | ||
Comment 4•11 years ago
|
||
Oh. Sorry. Comment 3, is sending out file via Bluetooth. It's not related to Bluetooth receiving file.
Assignee | ||
Updated•11 years ago
|
blocking-b2g: --- → koi?
Assignee | ||
Comment 5•11 years ago
|
||
Hi Sam, It looks like connection drop after L2CAP established. Can you confirm kernel with backport bluez? After commits from Thomas, I saw there are two kernel commit from Iean.
Flags: needinfo?(ckjboy2003)
Assignee | ||
Comment 8•11 years ago
|
||
We need to align with flatfish kernel code and check why connection will be dropped whenever remote side is trying to connect back flatish. I checked the rfcomm port that OPP listening, it looks normal. My another guess is to check rfcomm security level related.
Updated•11 years ago
|
Whiteboard: [Flatfish] → [Flatfish][developer+]
Comment 9•11 years ago
|
||
until final decision of Flatfish base version (v1.2 or v1.3) announce, change to --- for now.
blocking-b2g: koi? → ---
Comment 10•11 years ago
|
||
as we confirmed that Flatfish will use v1.3 and we need to respect current testing cycle, set target milestone to 12/6 since 1.3FC tag is not created yet.
blocking-b2g: --- → 1.3+
Target Milestone: --- → 1.3 Sprint 6 - 12/6
Assignee | ||
Comment 11•11 years ago
|
||
Currently rfcomm disconnect caused by RFCOMM AUTH REJECT, ECONNREFUSED. It does not look like problem with gecko part. I suspect it's still related to security level. <4>[ 358.739478] __rfcomm_dlc_close: ++++BT_CONNECT2 condition: Set bit ++++ <4>[ 358.746895] rfcomm_sock_kill: sk ee601000 state 6 refcnt 2 <4>[ 358.746909] rfcomm_process_rx: session ee3f52c0 state 1 qlen 0 <4>[ 358.746924] rfcomm_process_dlcs: session ee3f52c0 state 1 <4>[ 358.746937] rfcomm_dlc_clear_timer: dlc ee3f53c0 state 6 <4>[ 358.746951] rfcomm_send_dm: ee3f52c0 dlci 24 <4>[ 358.746961] rfcomm_send_frame: session ee3f52c0 len 4 <4>[ 358.746974] l2cap_sock_sendmsg: sock ecc77c80, sk ee3fb800 <4>[ 358.747049] __rfcomm_dlc_close: dlc ee3f53c0 state 6 dlci 24 err 111 session ee3f52c0 <4>[ 358.747062] rfcomm_dlc_clear_timer: dlc ee3f53c0 state 6 <4>[ 358.747073] rfcomm_sk_state_change: dlc ee3f53c0 state 9 err 111 <4>[ 358.747087] rfcomm_dlc_unlink: dlc ee3f53c0 refcnt 2 session ee3f52c0 <4>[ 358.747100] rfcomm_session_set_timer: session ee3f52c0 state 1 timeout 200 <4>[ 358.747114] rfcomm_process_dlcs: RFCOMM AUTH REJECT, ECONNREFUSED
Comment 12•10 years ago
|
||
I'm unsure why this would be 1.3 blocker specifically, as I don't recall work happening for flatfish on any branch other than trunk. Renominating for more discussion.
blocking-b2g: 1.3+ → 1.3?
Comment 13•10 years ago
|
||
See https://bugzilla.mozilla.org/show_bug.cgi?id=944594#c5.
blocking-b2g: 1.3? → ---
Assignee | ||
Comment 14•10 years ago
|
||
This bug is related to HAL layer, nothing we can do in gecko/gaia.
Comment 15•10 years ago
|
||
we pended this bug due to the migration from bluez to bluedroid.
Flags: needinfo?(ckjboy2003)
Updated•10 years ago
|
Whiteboard: [Flatfish][developer+] → [Flatfish][TCP]
Updated•10 years ago
|
Whiteboard: [Flatfish][TCP] → [Flatfish][TCP][POVB]
Assignee | ||
Updated•7 years ago
|
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•