search

bluelinepc / signalcheck

SignalCheck Pro for Android
https://get.signalcheck.app
7 stars 0 forks source link

n41 reported as n7/n38 on Samsung A32 when PLMN is unknown #17

Closed mikejeep closed 1 year ago

mikejeep commented 2 years ago

----- 5G-NR 2600 ----- SS-RSRP: -107 dBm (33 asu) SS-RSRQ: -11 dB, SS-SINR: 10 dB PCI: 437 DL NR-ARFCN: 527790 (2638.95 MHz)

7 Neighbor Cells: 369 n7 (-115 dBm) 464 n7 (-118 dBm) 293 n7 (-122 dBm) 169 n7 (-123 dBm) 748 n7 (-125 dBm) 492 n7 (-125 dBm) 422 n7 (-44 dBm)

mikejeep commented 2 years ago

Fix pending in 4.714 Work in progress

TomSenpai commented 2 years ago

Also been having the same issue on my Samsung Galaxy s22 Ultra. It shows n38/n7 in areas where n41 and n71 are present. I'm on the T-Mobile network and as far as I know n71 and n41 are the only 5G bands deployed at the moment and n25 currently in testing phase not yet deployed.

mikejeep commented 2 years ago

Thanks @TomSenpai . It is an issue with the Samsung firmware that they have not resolved; I have a workaround in testing that will likely be included in the next app update.

mikejeep commented 1 year ago

Updated fix pending in 4.715 Work in progress

mikejeep commented 1 year ago

Fix pending in 4.716 Work in progress.

mikejeep commented 1 year ago

This is an Android bug; if users could add a "+1" on it, this will help attract attention for it to be properly fixed at the OS level: https://issuetracker.google.com/issues/253539094

TomSenpai commented 1 year ago

It seems like this bug might have been fixed. Signal Check Pro is now showing the right band (N41) when connected to NR - 2500 MHz.

Screenshot_20221121_171757_SignalCheck Pro

mikejeep commented 1 year ago

Resolved in version 4.73, released today.