As part of the larger "flashing" issue (#13), many if not all Mediatek 5G devices, report NR cells with NCI 0 or 268435455 (max LTE CID) as primary cells in NSA mode.
In some cases these cells are completely bogus, they've the PCI and NR-ARFCN of an old or future NR cell (most likely the cell they are connecting/disconnecting to), TAC is N/A, SINR N/A, SS-RSRP -44 dBm, CSI-RSRP -44, dBm, SS-RSRQ -3 dB, CSI-RSRQ -3 dB.
I have received reports of this issue from users with the following devices:
Xiaomi M2007J22G (API 29 and 30)
Oneplus DN2103 (API 30)
Oppo CPH2211 (API 30)
Realme RMX2111 (API 29 and 30)
This is an example:
Due to the previously mentioned "flashing" issue, it's really hard (not being able to test it personally) to understand how and what has changed in NR detection. So I would be glad to see a beta version of netmonster and/or netmonster-core with these changes, it would make it much easier to collect feedback
As part of the larger "flashing" issue (#13), many if not all Mediatek 5G devices, report NR cells with NCI 0 or 268435455 (max LTE CID) as primary cells in NSA mode.
In some cases these cells are completely bogus, they've the PCI and NR-ARFCN of an old or future NR cell (most likely the cell they are connecting/disconnecting to), TAC is N/A, SINR N/A, SS-RSRP -44 dBm, CSI-RSRP -44, dBm, SS-RSRQ -3 dB, CSI-RSRQ -3 dB.
I have received reports of this issue from users with the following devices: Xiaomi M2007J22G (API 29 and 30) Oneplus DN2103 (API 30) Oppo CPH2211 (API 30) Realme RMX2111 (API 29 and 30)
This is an example:
Due to the previously mentioned "flashing" issue, it's really hard (not being able to test it personally) to understand how and what has changed in NR detection. So I would be glad to see a beta version of netmonster and/or netmonster-core with these changes, it would make it much easier to collect feedback