Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[aosp-13] Wifi fails to get supplicant interface #4

Open
fabricedesre opened this issue Oct 26, 2022 · 0 comments
Open

[aosp-13] Wifi fails to get supplicant interface #4

fabricedesre opened this issue Oct 26, 2022 · 0 comments

Comments

@fabricedesre
Copy link 

110-26 11:42:21.609     1     1 I init    : service 'wpa_supplicant' requested start, but it is already running (flags: 134)
10-26 11:42:21.609     1     1 I init    : Control message: Processed ctl.start for 'wpa_supplicant' from pid: 27078 (/system/b2g/b2g)
10-26 11:42:26.593 27078 27161 E WifiNative: Failed to initialize supplicant
10-26 11:42:57.833   432   432 I hwservicemanager: getTransport: Cannot find entry [email protected]::ISupplicant/default in either framework or device VINTF manifest.
10-26 11:42:57.867     1     1 I init    : Sending signal 9 to service 'wpa_supplicant' (pid 11721) process group...
10-26 11:42:57.880     1     1 I init    : Control message: Processed ctl.stop for 'wpa_supplicant' from pid: 27078 (/system/b2g/b2g)
10-26 11:42:57.881     1     1 I init    : Service 'wpa_supplicant' (pid 11721) received signal 9 oneshot service took 1131.500000 seconds in background
10-26 11:42:57.885     1     1 I init    : processing action (init.svc.wpa_supplicant=stopped) from (/init.b2g.rc:73)
10-26 11:42:57.886     1     1 I init    : Command 'stop dhcpcd' action=init.svc.wpa_supplicant=stopped (/init.b2g.rc:74) took 0ms and failed: service dhcpcd not found
10-26 11:42:58.447     1     1 I init    : starting service 'wpa_supplicant'...
10-26 11:42:58.455     1     1 I init    : Control message: Processed ctl.start for 'wpa_supplicant' from pid: 27078 (/system/b2g/b2g)
10-26 11:42:58.468 27992 27992 D wpa_supplicant: wpa_supplicant v2.11-devel-13
10-26 11:42:58.468 27992 27992 D wpa_supplicant: Global control interface '@android:wpa_wlan0'
10-26 11:42:58.468 27992 27992 D wpa_supplicant: Using Android control socket 'wpa_wlan0'
10-26 11:42:58.468 27992 27992 D wpa_supplicant: Initing aidl control
10-26 11:42:58.469 27992 27992 I wpa_supplicant: Processing aidl events on FD 5
10-26 11:42:58.469 27992 27992 I wpa_supplicant: Starting AIDL supplicant
10-26 11:42:58.470   431   431 I servicemanager: Found android.hardware.wifi.supplicant.ISupplicant/default in device VINTF manifest.
10-26 11:42:58.470 27992 27992 I wpa_supplicant: Successfully initialized wpa_supplicant
10-26 11:43:03.451 27078 27161 E WifiNative: Failed to initialize supplicant
fabricedesre pushed a commit that referenced this issue Dec 16, 2022
@mfromanmoz
Bug 1800920 - Vendor libwebrtc from 1cdcbe12e8
6019fdb 
Upstream commit: https://webrtc.googlesource.com/src/+/1cdcbe12e8091d0f067503837131c86b2c3214fc
    [106] FrameCadenceAdapter: survive layer updates for unconfigured layers.

    The frame cadence adapter would previously crash on encountering
    unconfigured layer updates. Fix this to silently ignore such updates.

    (cherry picked from commit 5a77e51c17762fdc938e04541578ab06f50dbdc2)

    Fixed: webrtc:14417
    Bug: chromium:1360936
    Change-Id: I524aa196f6aed10ffb8cd4ddcb4b053c71dfabba
    Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/273325
    Reviewed-by: Ilya Nikolaevskiy <[email protected]>
    Commit-Queue: Markus Handell <[email protected]>
    Cr-Original-Commit-Position: refs/heads/main@{#37980}
    Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/275201
    Cr-Commit-Position: refs/branch-heads/5249@{#4}
    Cr-Branched-From: 7aaeb5a270ba23f5844f7301a50aaff9b6ca6126-refs/heads/main@{#37825}
fabricedesre pushed a commit that referenced this issue Jan 23, 2023
@Drekabi
Bug 1806510 - Vendor libwebrtc from 18408391ad
010540c 
Upstream commit: https://webrtc.googlesource.com/src/+/18408391ad4c947ad1a3eeae424663f15e6346ef
    Keep state internally of connections added to P2PTransportChannel (#4/n)

    P2PTransportChannel currently relies on the ICE controller to keep track of this, even though P2PTransportChannel is actually supposed to hold the mutable connections.

    Reading connections from the ICE controller also leaks some internal state from the ICE controller through the ordering of connections, which isn't strictly part of the interface. This change is a step towards fixing this.

    This change is functionally no-op for now. The internal state will be used behind a field-trial in a future CL. That is also when some tests will be updated to work with the new internal state.

    Bug: webrtc:14367, webrtc:1413
    Change-Id: I6f8c5d805c780411fe940926f192fd2d6ce86d29
    Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/275081
    Commit-Queue: Sameer Vijaykar <[email protected]>
    Reviewed-by: Jonas Oreland <[email protected]>
    Cr-Commit-Position: refs/heads/main@{#38080}
fabricedesre pushed a commit that referenced this issue Jan 23, 2023
@Drekabi
Bug 1806510 - Vendor libwebrtc from eef098d1c7
c811ba9 
Upstream commit: https://webrtc.googlesource.com/src/+/eef098d1c7d50613d8bff2467d674525a9d0c57c
    [Merge-107] [Stats] Avoid DCHECK crashing if SSRCs are not unique.

    To properly handle SSRC collisions in non-BUNDLE we need to change how
    RTP stats IDs are generated, but that is a riskier change to be dealt
    with in a separate CL.

    For now, we just make sure that crashing is not a possibility during
    SSRC collisions as a mitigation for https://crbug.com/1361612. This is
    achieved by adding a TryAddStats() method to RTCStatsReport returning
    whether successful.

    (cherry picked from commit da6297dc53cb2eaae7b1c5381652de9d707a7d48)

    Bug: chromium:1361612
    Change-Id: I8577ae4c84a7c1eb3c7527e9efd8d1b0254269a3
    Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/275766
    Reviewed-by: Harald Alvestrand <[email protected]>
    Commit-Queue: Henrik Boström <[email protected]>
    Cr-Original-Commit-Position: refs/heads/main@{#38197}
    Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/277900
    Reviewed-by: Evan Shrubsole <[email protected]>
    Cr-Commit-Position: refs/branch-heads/5304@{#4}
    Cr-Branched-From: 024bd84ca1cf7d3650c27912a3b5bfbb54da152a-refs/heads/main@{#38083}
fabricedesre pushed a commit that referenced this issue Apr 12, 2023
@docfaraday
Bug 1822194 - Vendor libwebrtc from 1e675c7835
3c604b3 
Upstream commit: https://webrtc.googlesource.com/src/+/1e675c7835f188cd8be228f5da6d3467690355b8
    Zero memory for FEC recovered packets when size increases

    rtc::CopyOnWriteBuffer::SetSize extends buffer with uninitialized memory by design.
    It is up to the user of the rtc::CopyOnWriteBuffer to ensure it is initialized.

    (cherry picked from commit 4f74385b4f568df77055f99b04de41557ffd022a)

    No-Try: true
    Bug: chromium:1404299
    Change-Id: I41f3f91bf20ff440984d78ed81e01f5db36ff509
    Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/290400
    Commit-Queue: Danil Chapovalov <[email protected]>
    Reviewed-by: Per Kjellander <[email protected]>
    Cr-Original-Commit-Position: refs/heads/main@{#38972}
    Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/291541
    Cr-Commit-Position: refs/branch-heads/5481@{#4}
    Cr-Branched-From: 2e1a9a4ae0234d4b1ea7a6fd4188afa1fb20379d-refs/heads/main@{#38901}
fabricedesre pushed a commit that referenced this issue Jul 11, 2023
@jan-ivar
Bug 1839451 - Vendor libwebrtc from 8cb31cf125
c1e0947 
Upstream commit: https://webrtc.googlesource.com/src/+/8cb31cf1255a722d9a6591ddd8ccd76aae9eec9c
    Implement support for Chrome task origin tracing. #4/4

    This CL forwards BlockingCall client locations to
    BlockingCallImpl.

    Fixed: chromium:1416199
    Change-Id: Ic5865280ec5c72a09a64419940b8343e8a54986b
    Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/295624
    Commit-Queue: Markus Handell <[email protected]>
    Reviewed-by: Harald Alvestrand <[email protected]>
    Cr-Commit-Position: refs/heads/main@{#39442}
fabricedesre pushed a commit that referenced this issue Aug 3, 2023
@mfromanmoz
Bug 1843113 - Vendor libwebrtc from d20849d071
150ce03 
Upstream commit: https://webrtc.googlesource.com/src/+/d20849d0710783142175551d81dfe0dcbffcf2b1
    [M114] sdp: reject duplicate ssrcs in ssrc-groups

    while not really covered by
      https://www.rfc-editor.org/rfc/rfc5576.html#section-4.2
    and using the same SSRC for RTX and primary payload may work
    since payload type demuxing *could* be used is not a good idea.
    This also applies to flexfec's FEC-FR.

    For the nonstandard SIM ssrc-group duplicates make no sense.
    This rejects duplicates for unknown ssrc-groups as well.

    BUG=chromium:1454860

    (cherry picked from commit 6a38a3eb38f732b89ca0d8e36c43a434670c4ef5)

    No-Try: true
    Change-Id: I3e86101dbd5d6c4099f2fdb7b4a52d5cd0809c5f
    Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/308820
    Reviewed-by: Taylor Brandstetter <[email protected]>
    Reviewed-by: Harald Alvestrand <[email protected]>
    Commit-Queue: Philipp Hancke <[email protected]>
    Cr-Original-Commit-Position: refs/heads/main@{#40292}
    Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/309601
    Cr-Commit-Position: refs/branch-heads/5735@{#4}
    Cr-Branched-From: df7df199abd619e75b9f1d9a7e12fc3f3f748775-refs/heads/main@{#39949}
fabricedesre pushed a commit that referenced this issue Aug 3, 2023
@mfreed7 @moz-wptsync-bot
Bug 1845217 [wpt PR 41168] - Fix cloning of templates with DOM Parts,…
ef933d8 
… and improve testing, a=testonly

Automatic update from web-platform-tests
Fix cloning of templates with DOM Parts, and improve testing

This CL improves the testing of template cloning with Parts, testing
these four cases:

  1. Main document parsing
  2. Template (content fragment) parsing
  3. Template/fragment cloning
  4. Declarative Shadow DOM parsing and cloning

This CL fixes the behavior for #3 above, but leaves #4 broken. The
following changes in behavior are made:

1. Part::MoveToRoot() can be used to change the root(), including
   to set it to nullptr. This happens when a Node tree is removed
   from the DOM, and it contains Parts that refer to the old root.
2. IsDocumentPartRoot() is now virtual, because during a tree move,
   the root() for a Part can be made nullptr even when it's a
   ChildNodePart.
3. Part::disconnected_ is added to keep track of whether the
   Part has been disconnected, since root() can now be nullptr.
4. (This is a bug fix) When using ChildNodePart::setNextSibling(),
   the new sibling node wasn't having its Part registered with
   NodeRareData, which caused a CHECK failure when trying to
   subsequently clone that Part. This is caught in the new test
   which clones declaratively-built templates containing Parts.

Bug: 1453291
Change-Id: Ic1c1475431cf6bd658f191db78003204412ef78f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4713668
Reviewed-by: David Baron <[email protected]>
Auto-Submit: Mason Freed <[email protected]>
Commit-Queue: Mason Freed <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1175782}

--

wpt-commits: e03faa12a86fced56d076740e95fc7557db5eac4
wpt-pr: 41168
fabricedesre pushed a commit that referenced this issue Aug 29, 2023
@mfromanmoz
Bug 1847074 - Vendor libwebrtc from f5ffd45855
9e4f656 
We already cherry-picked this when we vendored d20849d071.

Upstream commit: https://webrtc.googlesource.com/src/+/f5ffd458556d7be6eafb4c644898f26f271388c0
    [M115] sdp: reject duplicate ssrcs in ssrc-groups

    while not really covered by
      https://www.rfc-editor.org/rfc/rfc5576.html#section-4.2
    and using the same SSRC for RTX and primary payload may work
    since payload type demuxing *could* be used is not a good idea.
    This also applies to flexfec's FEC-FR.

    For the nonstandard SIM ssrc-group duplicates make no sense.
    This rejects duplicates for unknown ssrc-groups as well.

    BUG=chromium:1454860

    (cherry picked from commit 6a38a3eb38f732b89ca0d8e36c43a434670c4ef5)

    Change-Id: I3e86101dbd5d6c4099f2fdb7b4a52d5cd0809c5f
    Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/308820
    Reviewed-by: Taylor Brandstetter <[email protected]>
    Reviewed-by: Harald Alvestrand <[email protected]>
    Commit-Queue: Philipp Hancke <[email protected]>
    Cr-Original-Commit-Position: refs/heads/main@{#40292}
    Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/309620
    Cr-Commit-Position: refs/branch-heads/5790@{#4}
    Cr-Branched-From: 2eacbbc03a4a41ea658661225eb1c8fc07884c33-refs/heads/main@{#40122}
fabricedesre pushed a commit that referenced this issue Oct 4, 2023
@mfromanmoz
Bug 1851693 - Vendor libwebrtc from aa6c910f47
8703715 
Upstream commit: https://webrtc.googlesource.com/src/+/aa6c910f476ddcf48471e268276412265869732f
    [116] Set surrogate receive times for transformed sender frames

    Without this, 'Sender' frames inserted into the writer of an encoded
    transform have an invalid receive time (0), which breaks all later
    heuristics which build on the receive time, eg the VCMTiming estimators
    used for controlling the playback delay.

    (cherry picked from commit 9d677f4cdcd536a2beb9f195b93e0d3df1cd6c9c)

    Bug: chromium:1463451
    Change-Id: I413c884e08986148d4a854cd275212b21d093ceb
    Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/311544
    Reviewed-by: Guido Urdaneta <[email protected]>
    Reviewed-by: Danil Chapovalov <[email protected]>
    Reviewed-by: Palak Agarwal <[email protected]>
    Reviewed-by: Erik Språng <[email protected]>
    Commit-Queue: Tony Herre <[email protected]>
    Cr-Original-Commit-Position: refs/heads/main@{#40416}
    Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/311662
    Commit-Queue: Erik Språng <[email protected]>
    Cr-Commit-Position: refs/branch-heads/5845@{#4}
    Cr-Branched-From: f80cf814353d11a9f22bef5ce5e8868f2c72f0d0-refs/heads/main@{#40319}
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@fabricedesre