Hotspot is hard to start since upgrade to LineageOS 16

Hi,

Today I upgraded my FP2 from LineageOS 15.1 to 16. Since then, I have to tap several times on the hotspot icon to start it; I had no issue before.
When it’s started, it works fine.

I’m wondering if I’m the only in this case, and if someone already has a solution or a workaround.
I made some researches, but found nothing.

Cheers!
PS: I’m not sure that the topic title is very well descriptive, I will perhaps change it if a better idea comes to me.

Can not confirm this with LineageOS 16.0 for microG (build 20190513).
Starting Hotspot takes one tap, Hotspot starts without a problem.
I didn’t upgrade though, I installed from scratch.

1 Like

I used logcat to have more informations about what’s hapenning under the wood. I spotted some interesting lines:

05-30 23:36:14.681   902   902 I hostapd : Add interface 'wlan0'
05-30 23:36:14.728   793  3079 D EthernetNetworkFactory: updateCapabilityFilter: []
05-30 23:36:14.757   902   902 I hostapd : rfkill: Cannot open RFKILL control device
05-30 23:36:14.767   902   902 I hostapd : Channel 56 (primary) not allowed for AP mode
05-30 23:36:14.768   902   902 I hostapd : wlan0: IEEE 802.11 Configured channel (56) not found from the channel list of current mode (2) IEEE 802.11a
05-30 23:36:14.768   902   902 W hostapd : wlan0: IEEE 802.11 Configured channel (56) not found from the channel list of current mode (2) IEEE 802.11a
05-30 23:36:14.768   902   902 I hostapd : wlan0: IEEE 802.11 Hardware does not support configured channel
05-30 23:36:14.768   902   902 W hostapd : wlan0: IEEE 802.11 Hardware does not support configured channel
05-30 23:36:14.768   902   902 E hostapd : Could not select hw_mode and channel. (-3)
05-30 23:36:14.768   902   902 I hostapd : wlan0: interface state UNINITIALIZED->DISABLED
05-30 23:36:14.768   902   902 I hostapd : wlan0: AP-DISABLED 
05-30 23:36:14.768   902   902 E hostapd : wlan0: Unable to setup interface.
05-30 23:36:14.768   902   902 I hostapd : nl80211: deinit ifname=wlan0 disabled_11b_rates=0
05-30 23:36:14.793   345   901 I WifiHAL : event received NL80211_CMD_VENDOR, vendor_id = 0x1374, subcmd = 0xa
05-30 23:36:14.794   902   902 E hostapd : Enabling interface wlan0 failed
05-30 23:36:14.795   793  2855 E HostapdHal: IHostapd.addAccessPoint failed: 1, 
05-30 23:36:14.795   793  2855 E WifiNative: Failed to add acccess point
05-30 23:36:14.795   793  2855 E SoftApManager: Soft AP start failed

The complete log is here: https://paste.swordarmor.fr/raw/Yrgc

When it works, I have this logs: https://paste.swordarmor.fr/raw/3OkD

Thanks for your reply! I will probably install a new image from scratch if I don’t find a solution, but if I can avoid backup & recovery, I prefer :wink:

I tested to switch back to 2.4 GHz in the AP settings, it works all the time.

But those frequencies are pretty saturated by there, so I will be glad if I could use the 5 GHz option.

2 Likes

I can confirm that behaviour

  • LOS updated from 15.1 to 16.0
  • 2.4 GHz: tapping the icon works
  • 5 GHz: tapping the icon does NOT work
    • what seems to work (tested once): enabling the hotspot from the settings app instead of quick access icons
2 Likes

Thanks for the confirmation.
I have the same success rate from the settings than from the shortcut.

1 Like

I’m not a Wi-Fi expert, but it seems to me that reserved frequencies reflect those I can find on other devices, and the country matches mine. As root, iw reg get and iw list outputs: https://paste.swordarmor.fr/raw/hQdK

5 GHz WLAN shouldn’t be used outdoors. It is for indoor usage only. Of course, it could be possible you are setting up the hotspot whilst being indoor. If your 2.4 GHz WLAN is saturated try to move your client closer to the hotspot server (FP2).

This topic was automatically closed 182 days after the last reply. New replies are no longer allowed.