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

n41/n38 detection is broken in NetMonster 2.22.2 #80

Open
eladts opened this issue May 19, 2023 · 3 comments
Open

n41/n38 detection is broken in NetMonster 2.22.2 #80

eladts opened this issue May 19, 2023 · 3 comments

Comments

@eladts
Copy link

eladts commented May 19, 2023 •
edited
Loading

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
Copy link
Author

eladts commented May 29, 2023 •
edited
Loading

ARFCN 529998 is not identified as well.

@eladts
Copy link
Author

eladts commented Jun 7, 2023 •
edited
Loading

@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
Copy link
Author

eladts commented Jun 20, 2023 •
edited
Loading

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.
screenshot.png
report.txt

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
@eladts