Closed
Bug 1111970
Opened 10 years ago
Closed 10 years ago
[Wifi Direct] group owner's ip is not populated to content properly
Categories
(Firefox OS Graveyard :: Wifi, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
2.2 S3 (9jan)
People
(Reporter: hchang, Assigned: hchang)
Details
Attachments
(3 files)
|
5.82 MB,
application/octet-stream
|
Details | |
|
1.05 KB,
patch
|
vchang
:
review+
|
Details | Diff | Splinter Review |
|
1.67 KB,
patch
|
Details | Diff | Splinter Review |
MozWifiP2pManager.groupOwner.ip is always undefined due to [1]. It should be |gateways[0]|
[1] http://hg.mozilla.org/mozilla-central/file/5d6e0d038f95/dom/wifi/WifiP2pManager.jsm#l1184
| Assignee | ||
Updated•10 years ago
|
Summary: [Wifi Direct] group owner's ip is not populated to DOM properly → [Wifi Direct] group owner's ip is not populated to content properly
| Assignee | ||
Comment 1•10 years ago
|
||
| Assignee | ||
Comment 2•10 years ago
|
||
| Assignee | ||
Comment 3•10 years ago
|
||
| Assignee | ||
Comment 4•10 years ago
|
||
| Assignee | ||
Comment 5•10 years ago
|
||
For those who have a hard time building gecko, push the attachment omni.ja to system/b2g/
$ adb push omni.ja system/b2g/
Comment 6•10 years ago
|
||
(In reply to Henry Chang [:henry] from comment #5)
> For those who have a hard time building gecko, push the attachment omni.ja
> to system/b2g/
>
> $ adb push omni.ja system/b2g/
Thanks Henry! This patch worked for me. I'm now able to connect to the peer by getting its ipAddress.
| Assignee | ||
Updated•10 years ago
|
Attachment #8536992 -
Flags: review?(vchang)
| Assignee | ||
Comment 8•10 years ago
|
||
(In reply to Justin D'Arcangelo [:justindarc] from comment #6)
> (In reply to Henry Chang [:henry] from comment #5)
> > For those who have a hard time building gecko, push the attachment omni.ja
> > to system/b2g/
> >
> > $ adb push omni.ja system/b2g/
>
> Thanks Henry! This patch worked for me. I'm now able to connect to the peer
> by getting its ipAddress.
Oops I forgot to request to review. Will land after getting reviewed.
Thanks!
Flags: needinfo?(hchang)
Comment 9•10 years ago
|
||
Comment on attachment 8536992 [details] [diff] [review]
Bug111970.patch
Review of attachment 8536992 [details] [diff] [review]:
-----------------------------------------------------------------
Thank you.
Attachment #8536992 -
Flags: review?(vchang) → review+
Comment 11•10 years ago
|
||
Henry. I noticed that if push omni.ja to the latest gecko my phone doesn't boot.
It works fine with the build 20141215040201
| Assignee | ||
Updated•10 years ago
|
Flags: needinfo?(hchang)
Keywords: checkin-needed
Comment 12•10 years ago
|
||
Assignee: nobody → hchang
Keywords: checkin-needed
Comment 13•10 years ago
|
||
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Target Milestone: --- → 2.2 S3 (9jan)
Comment 14•10 years ago
|
||
Henry, we're finding the functionality in this patch very flaky. We can generally get 1-2 connections going before needing to reboot. This is making iteration on an important WiFi Direct project very difficult. Is this known, is there any eta, etc? Thanks for any help you can provide.
Flags: needinfo?(hchang)
| Assignee | ||
Comment 15•10 years ago
|
||
(In reply to Doug Sherk (:drs) (use needinfo?) from comment #14)
> Henry, we're finding the functionality in this patch very flaky. We can
> generally get 1-2 connections going before needing to reboot. This is making
> iteration on an important WiFi Direct project very difficult. Is this known,
> is there any eta, etc? Thanks for any help you can provide.
Hi,
I don't it has anything to do with this patch. Can you elaborate the
issue you met or file a bug?
Thanks :)
Flags: needinfo?(hchang)
Comment 16•10 years ago
|
||
Hi Doug, can you describe in more detail about your problem? Which device do you use?
Flags: needinfo?(drs.bugzilla)
Comment 17•10 years ago
|
||
(In reply to Vincent Chang[:vchang] from comment #16)
> Hi Doug, can you describe in more detail about your problem? Which device do
> you use?
Filed bug 1119853.
Flags: needinfo?(drs.bugzilla)
You need to log in
before you can comment on or make changes to this bug.
Description
•