My android phone, specifically. It all works if I switch “Extend compatibility” on, it does not otherwise. The main thing the switch does is set the hotspot on 2.4GHz instead of 5, there is no dual band hotspot on my phone.
What’s your phone model?
Poco X3 NFC (europe/global) running LineageOS 20
Some phones have made their own special encryption methods. So it must use " Extend compatibility" to be compatible with other cryptography.
I am root, I should probably be able to config that. Any reading material you can point me to?
I experimented a little bit more, and I discovered that it’s not that it doesn’t connect: it doesn’t see the network at all, if I turn that switch off.
Both phone and router know what country they’re in, and the hotspot should change channel every time I turn it on. So I doubt it’s that.
I misunderstood. I thought that hotspot could be scanned. But it could not be linked.
Because When we were compatible with the iphone 13, it was due to encryption compatibility issues.
You select the following option for the test.
1 Like
That’s what I believed as well. I’m not with my router right now. I’ll try later today or tomorrow.
Nothing changes with that option. And I see nothing suspect in the logs.
There is such a issue.Any new developments will be updated to you.
1 Like
I installed InSSIDer on my laptop and I discovered my hotspot goes on channel 155 [149]. The selector dropdown on my slate ax only goes up to 128 (DFS).
149 is marked as SRD here. 
I was wondering about this stuff in GL-MT3000 (Berly AX) in the WiFi 5G iPhone 13 Pro Max Not working? - #20 by lecmipahu. Even if a channel is SRD, shouldn’t it be still available, but with limited power?
Yes, but not all SRD are made equal and I assume it’s either an oversight (SRD is only a thing in Europe and gl.inet lives in HK/US) or they’re still thinking how to make it work.*
* : (there’s only one 5GHz radio, if you connect to an SRD channel you have to stay within those limits when you transmit. You’d need another radio to transmit on a different channel.)
(in the meanwhile, I have been unable to force my phone to transmit on a lower-numbered channel, and no, there is nobody near me blasting on 5GHz, I barely see five 2.4GHz networks)
(if I tell my slate ax we’re in the US, everything works as I expect. But I don’t want to blast frequencies I should not.)
Thank you very much for your information.
1 Like
Please show the country code of your slate ax.
uci get wireless.@wifi-device[0].country
It’s IT. I set it up manually from Luci.
root@GL-AXT1800:~# uci get wireless.@wifi-device[0].country
IT
root@GL-AXT1800:~# uci get wireless.@wifi-device[1].country
IT
root@GL-AXT1800:~#
also:
root@GL-AXT1800:~# iw reg get
global
country IT: DFS-ETSI
(2400 - 2483 @ 40), (N/A, 20), (N/A)
(5150 - 5250 @ 80), (N/A, 23), (N/A), NO-OUTDOOR, AUTO-BW
(5250 - 5350 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS, AUTO-BW
(5470 - 5725 @ 160), (N/A, 26), (0 ms), DFS
(5725 - 5875 @ 80), (N/A, 13), (N/A)
(57000 - 66000 @ 2160), (N/A, 40), (N/A)
phy#1 (self-managed)
country IT: DFS-ETSI
(2402 - 2482 @ 40), (N/A, 20), (N/A)
(5170 - 5250 @ 80), (N/A, 23), (N/A), NO-OUTDOOR, AUTO-BW
(5250 - 5330 @ 80), (N/A, 23), (0 ms), NO-OUTDOOR, DFS, AUTO-BW
(5490 - 5590 @ 80), (N/A, 30), (0 ms), DFS, AUTO-BW
(5590 - 5650 @ 40), (N/A, 30), (600000 ms), DFS, AUTO-BW
(5650 - 5710 @ 40), (N/A, 30), (0 ms), DFS, AUTO-BW
phy#0 (self-managed)
country IT: DFS-ETSI
(2402 - 2482 @ 40), (N/A, 20), (N/A)
(5170 - 5250 @ 80), (N/A, 23), (N/A), NO-OUTDOOR, AUTO-BW
(5250 - 5330 @ 80), (N/A, 23), (0 ms), NO-OUTDOOR, DFS, AUTO-BW
(5490 - 5590 @ 80), (N/A, 30), (0 ms), DFS, AUTO-BW
(5590 - 5650 @ 40), (N/A, 30), (600000 ms), DFS, AUTO-BW
(5650 - 5710 @ 40), (N/A, 30), (0 ms), DFS, AUTO-BW
root@GL-AXT1800:~#
SRD is 5710–5730 and 5735-5875 (according to wikipedia). it looks like this line
(5725 - 5875 @ 80), (N/A, 13), (N/A)
Which I can see in the global reg but not in each radio section.
It’s only support these channels for IT.
5.180 GHz (Channel 36)
5.200 GHz (Channel 40)
5.220 GHz (Channel 44)
5.240 GHz (Channel 48)
5.260 GHz (Channel 52)
5.280 GHz (Channel 56)
5.300 GHz (Channel 60)
5.320 GHz (Channel 64)
5.500 GHz (Channel 100)
5.520 GHz (Channel 104)
5.540 GHz (Channel 108)
5.560 GHz (Channel 112)
5.580 GHz (Channel 116)
5.600 GHz (Channel 120)
5.620 GHz (Channel 124)
5.640 GHz (Channel 128)
5.660 GHz (Channel 132)
5.680 GHz (Channel 136)
5.700 GHz (Channel 140)
that’s what it’s doing now, and this is not how it’s supposed to be.
it should support 144, 149, all the way to 173, but at a reduced power. the entire 5.725 - 5.875 GHz range
(all across the EU, not just for IT – some countries might get picky, but iw reg knows all about it.)
For example, this is what my phone says on iw list
Frequencies:
* 5180 MHz [36] (23.0 dBm) (no IR)
* 5200 MHz [40] (23.0 dBm) (no IR)
* 5220 MHz [44] (23.0 dBm) (no IR)
* 5240 MHz [48] (23.0 dBm) (no IR)
* 5260 MHz [52] (23.0 dBm) (no IR, radar detection)
* 5280 MHz [56] (23.0 dBm) (no IR, radar detection)
* 5300 MHz [60] (23.0 dBm) (no IR, radar detection)
* 5320 MHz [64] (23.0 dBm) (no IR, radar detection)
* 5500 MHz [100] (30.0 dBm) (radar detection)
* 5520 MHz [104] (30.0 dBm) (radar detection)
* 5540 MHz [108] (30.0 dBm) (radar detection)
* 5560 MHz [112] (30.0 dBm) (radar detection)
* 5580 MHz [116] (30.0 dBm) (radar detection)
* 5600 MHz [120] (30.0 dBm) (radar detection)
* 5620 MHz [124] (30.0 dBm) (radar detection)
* 5640 MHz [128] (30.0 dBm) (radar detection)
* 5660 MHz [132] (30.0 dBm) (radar detection)
* 5680 MHz [136] (30.0 dBm) (radar detection)
* 5700 MHz [140] (30.0 dBm) (radar detection)
* 5720 MHz [144] (30.0 dBm) (radar detection)
* 5745 MHz [149] (14.0 dBm)
* 5765 MHz [153] (14.0 dBm)
* 5785 MHz [157] (14.0 dBm)
* 5805 MHz [161] (14.0 dBm)
* 5825 MHz [165] (14.0 dBm)
* 5845 MHz [169] (14.0 dBm)
* 5865 MHz [173] (14.0 dBm)
And this is what my slate ax tells me
Frequencies:
* 5180 MHz [36] (23.0 dBm)
* 5200 MHz [40] (23.0 dBm)
* 5220 MHz [44] (23.0 dBm)
* 5240 MHz [48] (23.0 dBm)
* 5260 MHz [52] (23.0 dBm) (radar detection)
* 5280 MHz [56] (23.0 dBm) (radar detection)
* 5300 MHz [60] (23.0 dBm) (radar detection)
* 5320 MHz [64] (23.0 dBm) (radar detection)
* 5500 MHz [100] (30.0 dBm) (radar detection)
* 5520 MHz [104] (30.0 dBm) (radar detection)
* 5540 MHz [108] (30.0 dBm) (radar detection)
* 5560 MHz [112] (30.0 dBm) (radar detection)
* 5580 MHz [116] (30.0 dBm) (radar detection)
* 5600 MHz [120] (30.0 dBm) (radar detection)
* 5620 MHz [124] (30.0 dBm) (radar detection)
* 5640 MHz [128] (30.0 dBm) (radar detection)
* 5660 MHz [132] (30.0 dBm) (radar detection)
* 5680 MHz [136] (30.0 dBm) (radar detection)
* 5700 MHz [140] (30.0 dBm) (radar detection)
* 5720 MHz [144] (disabled)
* 5745 MHz [149] (disabled)
* 5765 MHz [153] (disabled)
* 5785 MHz [157] (disabled)
* 5805 MHz [161] (disabled)
* 5825 MHz [165] (disabled)
* 5845 MHz [169] (disabled)
* 5865 MHz [173] (disabled)
* 5885 MHz [177] (disabled)
All those (disabled) shouldn’t be. (Other than 177. No idea what it’s doing there. Old database?)
1 Like
I would solve this myself, but I have no idea how.
I followed the config back from hostapd.conf to netifd, but I have no idea where netifd gets their information. I’ve seen nothing suspicious in /etc/config or in sysctl.d
@lizh @JerryZhao You might be happy to know that this issue could be (at least partially) solved by using kernel 5.4. I don’t know if flashing a kernel changes the regulatory domain, but if it doesn’t, then at least a few of those channels become available. I don’t know if it’s all the channels I expect because I had it set up on 80MHz channels.
I cannot investigate further because I then flashed the beta firmware as well and I don’t have an ethernet adapter with me.
1 Like