n41/n38 detection is broken in NetMonster 2.22.2

mroczis / netmonster-core

Android Telephony SDK bridge with some additional features

Apache License 2.0

339 stars 72 forks source link

n41/n38 detection is broken in NetMonster 2.22.2 #80

Open eladts opened 1 year ago

eladts commented 1 year ago

I downloaded NetMonster 2.22.2 and unfortunately it looks like n41/n38 regional rules the were discussed in #69 were not implemented. ARFCN 524190 is not identified even though it should be identified as n41 2500 in the US. On the other hand, ARFCN 513390 is properly identified.

report.txt

Screenshot_20230519-140523

eladts commented 1 year ago

ARFCN 529998 is not identified as well.

eladts commented 1 year ago

@mroczis It looks like n90 2500 which isn't currently being used anywhere messes up n38/n41 detection. Also another unused band, n53 2400, is incorrectly labeled as 2500 in BandTableNr.kt, which may also relate to this issue.

eladts commented 1 year ago

After Android QPR3 update for my Pixel 7, now NR SA ARFCN 524190 is properly identified by NetMonster 2.22.2. However NR NSA ARFCN 524190 is still not identified and NR SA ARFCN 524190 cells are not identified in the log. report.txt