The default bug view has changed. See this FAQ.

[FlyWeb] Implement WiFi-Direct backend on Android

RESOLVED WONTFIX

Status

()

Core
Networking
RESOLVED WONTFIX
a year ago
a year ago

People

(Reporter: djvj, Assigned: djvj)

Tracking

(Blocks: 1 bug)

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [necko-would-take])

Attachments

(1 attachment, 1 obsolete attachment)

(Assignee)

Description

a year ago
Write the fennec implementation of the Wi-Fi Direct backend for FlyWeb.
(Assignee)

Updated

a year ago
Assignee: nobody → kvijayan
(Assignee)

Comment 1

a year ago
Created attachment 8726964 [details] [diff] [review]
wifi-direct-backend.patch

Initial patch.  Doesn't do much yet, but the basic boilerplate for shimming between C++ and the Java code is there.
Whiteboard: [necko-would-take]
(Assignee)

Comment 2

a year ago
Created attachment 8730926 [details] [diff] [review]
add-wifi-direct-support.patch

Latest patch.
Attachment #8726964 - Attachment is obsolete: true
(Assignee)

Comment 3

a year 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
Last Resolved: a year ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.