Closed
Bug 1283006
Opened 9 years ago
Closed 9 years ago
[Remote Control] Fennec cannot pairing with TV after TV's network disconnect and connect again
Categories
(Firefox OS Graveyard :: Gaia::TV, defect, P1)
Tracking
(blocking-b2g:2.6+, b2g-v2.6 fixed)
People
(Reporter: mlien, Assigned: etsai)
References
Details
(Whiteboard: [ft:conndevices])
Attachments
(1 file)
48 bytes,
text/x-github-pull-request
|
chunmin
:
review+
jocheng
:
approval-gaia-v2.6+
|
Details | Review |
[Testing Steps]
0. Fennec and TV connect to the same domain
1. Send a tab from Fennec to TV (will show first time pairing page)
2. Close pairing page
3. Disable TV's network
4. Enable TV's network
5. Repeat step 1 again
[Expected result]
Be able to show pairing page normally
[Actual result]
Cannot show pairing page normally, it will open pairing page but always under loading status
[Build Info]
Environment: 2.6 Nexus Player
gaia:
https://github.com/mozilla-b2g/gaia/commit/508825d1599d6596292e15789181568d00dd4acf
gecko:
https://github.com/mozilla-b2g/gecko-b2g/commit/49b98aa3b415380cc7a021d740b242894654245a
Fennec add-on:
https://github.com/ChunMinChang/fennec-fxos-tv/commit/48bee4df266fe08e19c81e1d8aa3d4fa8b3da6c2
[Error Log]
https://gist.github.com/anonymous/95c42dc26a2dfa39dce4a97bab232b69
Comment 1•9 years ago
|
||
Hi,
Does it *only* happen in the first pairing after re-enabling TV's network, or they can't build the connection permanently?
Reporter | ||
Comment 2•9 years ago
|
||
It cannot build the connection permanently no matter first pairing or already paired before. And this situation only happen when re-enable connection from TV side. Re-enable connection from Fennec side won't have this problem.
Assignee | ||
Comment 3•9 years ago
|
||
No sure if network stops also trigger presentation discovery stop? If so, network restarts may cause remote control restarts in different port, the port should be update.
Comment 4•9 years ago
|
||
The port in Fennec side update dynamically. Would you provide some log for this problem?
Reporter | ||
Comment 5•9 years ago
|
||
In this case, Fennec won't update remote control port while TV re-enable network.
Comment 6•9 years ago
|
||
Did this happen only before you re-click the "search devices" button? Or it happen after you re-click the "search devices" button?
Comment 7•9 years ago
|
||
After the TV shutdowns, MDNS should fire a "remove" event to notify add-on that the device is removed. Did you receive this event?
Comment 8•9 years ago
|
||
NOTE:
1. Check whether Fennec receives the *new* port info from MDNS boardcast
2. Chech whether Fennec can receive the *remove* event from MDNS
I will check these issues today
Comment 9•9 years ago
|
||
(In reply to Chun-Min Chang[:chunmin] from comment #8)
> NOTE:
> 1. Check whether Fennec receives the *new* port info from MDNS boardcast
No. The port info boardcasted by TV is not changed.
> 2. Chech whether Fennec can receive the *remove* event from MDNS
No. Fennec can't get the notification.
*Before* the TV turn-off wifi, Fennec can build the TLS connection successfully, and the openssl shows CONNECTED
> $ openssl s_client -connect 10.247.36.119:53906
> CONNECTED(00000003)
> 55786:error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol:/BuildRoot/Library/Caches/com.apple.xbs/Sources/OpenSSL098/OpenSSL098-59.40.2/src/ssl/s23_clnt.c:618:
*After* the TV turn-off wifi, and then turn-on wifi again, Fennec can *NOT* build the TLS connection. The openssl shows that
> $ openssl s_client -connect 10.247.36.119:53906
> connect: Operation timed out
> connect:errno=60
The above openssl might not be correct, but it gives some info at least.
Comment 10•9 years ago
|
||
Note:
Check whether |dom.presentation.discoverable| is changed into |false| when wifi is turned-off.
Assignee | ||
Comment 11•9 years ago
|
||
Root cause of this bug is when wifi turned off, tls server socket is forced to stop listening. Turn on wifi will not restart tls server socket. Solution is to add network status observer, while no active network, stop remote control service and start when active network back.
Attachment #8766661 -
Flags: review?(cchang)
Updated•9 years ago
|
Attachment #8766661 -
Flags: review?(cchang) → review+
Comment 12•9 years ago
|
||
Would you have time to fix the nits? Or just land it ASAP for QA's testing. I am OK for both.
Flags: needinfo?(etsai)
Assignee | ||
Comment 13•9 years ago
|
||
I'm fine with the nit, just fixed. You can send approve now.
Flags: needinfo?(etsai)
Comment 14•9 years ago
|
||
Comment on attachment 8766661 [details] [review]
Patch 1. Implement network status change observer
[Approval Request Comment]
[Bug caused by] (feature/regressing bug #):
[User impact] if declined:
[Testing completed]:
[Risk to taking this patch] (and alternatives if risky):
[String changes made]:
Attachment #8766661 -
Flags: approval-gaia-v2.6?(jocheng)
Updated•9 years ago
|
Assignee: nobody → etsai
Updated•9 years ago
|
blocking-b2g: 2.6? → 2.6+
Comment 15•9 years ago
|
||
Comment on attachment 8766661 [details] [review]
Patch 1. Implement network status change observer
Approve for TV 2.6
Attachment #8766661 -
Flags: approval-gaia-v2.6?(jocheng) → approval-gaia-v2.6+
Comment 16•9 years ago
|
||
You need to log in
before you can comment on or make changes to this bug.
Description
•