Closed
Bug 1253761
Opened 9 years ago
Closed 9 years ago
[FlyWeb] Implement WiFi-Direct backend on Android
Categories
(Core :: Networking, defect)
Core
Networking
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: djvj, Assigned: djvj)
References
Details
(Whiteboard: [necko-would-take])
Attachments
(1 file, 1 obsolete file)
|
70.33 KB,
patch
|
Details | Diff | Splinter Review |
Write the fennec implementation of the Wi-Fi Direct backend for FlyWeb.
|
Assignee | |
Updated•9 years ago
|
Assignee: nobody → kvijayan
|
|
Assignee | |
Comment 1•9 years ago
|
||
Initial patch. Doesn't do much yet, but the basic boilerplate for shimming between C++ and the Java code is there.
|
||
Updated•9 years ago
|
Whiteboard: [necko-would-take]
|
|
Assignee | |
Comment 3•9 years ago
|
||
So, after much experimentation and reading up online, the conclusion is that Wi-Fi Direct support in the wild is just not up to par. Both device discovery and service discovery on even flagship Android devices is super flaky. Sometimes services are seen, sometimes not.
It seems adoption and implementation in devices for Wi-Fi Direct is not there yet, so I'm shelving this implementation effort until we revisit at a later time if/when WiDi is better supported.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•