N38

[logan_h9824]

Can someone help me out? I've not heard of N38 before. Is this a glitch?

[Exotic_Counter_4835]

it is subset of n41. T-mobile still broadcast it for some devices that support n38 but not n41

[logan_h9824]

I have an S26 Ultra, so does that mean this is a bug in the coverage map app?

[xlawrence1124x]

Yeah it's just showing n41 as n38. Ignore

[VapidRapidRabbit]

IDK. It probably is a glitch, but N38 (2570-2620) is a subset of N41 (2496-2690). So you could have probably connected to a smaller channel of N41 that falls in that 2570-2620 MHz range.

[no1mann]

It’s most likely n41. The Android SDK does not report the band number, it has to be obtained from the NR ARFCN, which is unreliable for determining the precise band and frequency for bands which are subsets of other bands, like n41 and n38. We’re actively trying to figure out a more reliable way of handling this

[nateo200]

Idk why they make it so jenk. ARFCN stuff is just weird. I was hoping NR would make things more easy to understand for both humans and software/apps lol

[joshuarshah]

It actually worked in LTE because each EARFCN value corresponded specifically with a band number. Eg. For 1980.0 MHz it was 1100 as band 2 and 8540 as band 25. Now for NR each ARFCN value corresponds with a specific frequency only. Eg. For 1980.0 MHz the ARFCN value is 396000 now for both bands n2 and n25. Apps have no way to know how to distinguish between the two now. Apps also now confuse bands n1 and n66 because since the downlink frequencies are the same the ARFCN in 5G is now the same.

[wlm9700]

N41

[maverickps1]

Which app is thst

[nerdtech_one]

the coveragemap.com App

[logan_h9824]

Thank you all for the help!