Follow-ups left open by the 8822B fast bandwidth toggle fix (#584)
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 42/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- c
Research direction
Start with tests/fast_bw_rxcheck.cpp and compare the 20 MHz to 10 MHz FastSetBandwidth path described here with the full SetMonitorChannel path. Reproduce the intermittent near-zero hit count using the stated RTL8812BU receiver and RTL8812CU transmitter setup. The issue is resolved when the cause is identified and the fast switch reliably decodes the partner during the narrowband window.
Written by the indexing model from the issue text.
Description
One item left open by #584, which fixes the 8822B fast bandwidth paths but does not touch this.
The fast 20 MHz -> narrowband switch sometimes decodes nothing
tests/fast_bw_rxcheck.cpp on an RTL8812BU (0bda:b812, USB 2, channel 36), with an RTL8812CU (0bda:c812) transmitting 10 MHz narrowband (DEVOURER_NB_BW=10). The RX starts at 20 MHz, toggles to 10 MHz with FastSetBandwidth, and should decode the partner only in that window.
| build | runs with 0 or 1 hits in the narrowband window | healthy runs |
|---|---|---|
master 0761c60c |
1 of 6 | 5 of 6, ~1800 hits each |
| #584 | 4 of 9 | 5 of 9, ~1800 hits each |
Each run is a fresh RX bring-up; the transmitter stayed up across runs. The fast_set_bandwidth 20 -> narrowband branch is identical on the two builds for a toggle without a hop, and the two rates cannot be told apart at these counts, so this is treated as pre-existing.
Not investigated
- Whether the RF18 edge in that branch is itself unreliable, the way the missing edge on the return was (#584 measured 3 of 6 deaf there before adding it).
- Whether the transmitter is at fault. It was a build from 9 November, and a Jaguar3 part; a different narrowband partner would separate the two.
- Whether the full path (
SetMonitorChannelto 10 MHz) shows the same rate. If it does not, the difference between the two paths is the lead. - 5 MHz, and 2.4 GHz.
A run counts as failed here when the narrowband window has at most 1 hit against ~1800 in a healthy run; nothing in between was seen.
- Dominant language
- C
- Stars
- 56
- Forks
- 29
- Avg merge
- 3h 43m
- Merged PRs (30d)
- 75
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from OpenIPC/devourer
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 12/100
OpenIPC/devourer#579 · 1 comment ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 12/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 8/100
Maintainers usually reply within 1 day
-
M6 test realism — a moving-UE handover bench (conducted path-loss matrix, then an over-the-air walk)Openenhancement
Difficulty 5/5 Over a week Newbie friendliness 25/100
OpenIPC/devourer#563 · 1 comment ·
Maintainers usually reply within 1 day
All issues in OpenIPC/devourer
Similar issues
-
needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
389ds/389-ds-base#8157 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
coolsnowwolf/lede#14305 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Needs-Triage
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 2 days