[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] Mywayorthehuawei:
Been trying to look into the hotspot problem more (I don't have any experience on roms or android other than using stock just started looking at and installing this last week so this may be obvious stuff or completely wrong :silly:)

Logcat:

05-04 13:39:56.774 5163 5163 D WifiTetherSsidPref: Updating SSID in Preference, ANYWIFI

05-04 13:39:56.776 5163 5555 D SharedPreferencesLogger: Tried to log string preference wifi.tether.WifiTetherSettings/wifi_tether_network_name = ANYWIFI

05-04 13:39:56.780 5163 5163 D WifiTetherApBandPref: 5Ghz not supported, updating band index to 0

05-04 13:39:56.782 5163 5163 D WifiTetherSettings: updating display config due to receiving broadcast action android.net.wifi.WIFI_AP_STATE_CHANGED

05-04 13:39:56.784 5163 5163 D WifiTetherSsidPref: Updating SSID in Preference, ANYWIFI

05-04 13:39:56.787 5163 5554 D SharedPreferencesLogger: Tried to log string preference wifi.tether.WifiTetherSettings/wifi_tether_network_name = ANYWIFI

05-04 13:39:56.791 5163 5163 D WifiTetherApBandPref: 5Ghz not supported, updating band index to 0

05-04 13:39:57.303 5163 5184 W libEGL : EGLNativeWindowType 0x70588d9010 disconnect failed

05-04 13:39:57.312 5163 5163 V WifiManager: unregisterSoftApCallback: callback=com.android.settings.wifi.tether.WifiTetherSoftApManager$1@3382ffa

05-04 13:39:57.423 802 802 I aptouch_daemon: filter_touch_detect, down, in: 1, out: 1

05-04 13:39:57.480 802 802 I aptouch_daemon: filter_touch_detect, all_touch_up

05-04 13:39:57.485 5163 5163 I ConnectivityManager: startTethering caller:com.android.settings

05-04 13:39:57.492 770 770 E WifiHAL : Enter init_wifi_vendor_hal_func_table

05-04 13:39:57.492 770 770 I vendor.huawei.hardware.wifi@1.1-service: Wifi HAL started

05-04 13:39:57.510 770 770 I : get_fw_path_from_dt, dt_file=/proc/device-tree/bcm_wifi/wifi_fw_ap_name, fw_path: /vendor/firmware/fw_bcm43455_apsta_hw.bin

05-04 13:39:57.511 770 770 D : hwwifi_change_fw_path, fw_path: write /vendor/firmware/fw_bcm43455_apsta_hw.bin to /sys/module/bcmdhd/parameters/firmware_path

05-04 13:39:58.121 770 770 I WifiHAL : Initializing wifi

05-04 13:39:58.122 770 770 I WifiHAL : Creating socket

05-04 13:39:58.125 770 770 I WifiHAL : Initialized Wifi HAL Successfully; vendor cmd = 103

05-04 13:39:58.130 770 770 E hw-IPCThreadState: binder thread pool (1 threads) starved for 623 ms

05-04 13:39:58.167 1736 1736 E wificond: No usable interface found

05-04 13:39:58.264 770 5635 E WifiHAL : wifi_event_loop: Read after POLL returned 4, error no = 0 (Success)

05-04 13:39:58.264 770 5635 D WifiHAL : Got a signal to exit!!!

05-04 13:39:58.264 770 5635 I WifiHAL : Exit wifi_event_loop

05-04 13:39:58.265 770 770 E WifiHAL : wifi_cleanup: Read after POLL returned 4, error no = 13 (Permission denied)

05-04 13:39:58.265 770 770 E WifiHAL : Event processing terminated

05-04 13:39:58.265 770 770 I WifiHAL : Internal cleanup completed

Looks like its falling over at the wificond: No usable interface found (Wifi manager) I'm not sure if it means the wifi manager (wificond) can't get the info it needs from the wifidriver - but normal wifi connections work fine so unlikely? Or something else I noticed is if you go into access point names(APN) you have your default carrier apn and another called hotspot: the hotspot one is greyed out as if disabled and can't be edited but has dun in the apn type.

From what I can see online dun is a way to emulate a modem and a way to set up tethering that would bypass carrier tethering blocks. Saw something online that google was allowing the carrier to specify what apn types are user configurable and what is disabled such as dun.

"dun

Indicates the current APN configuration may be used for Dial-Up Networking connections. This refers to an outdated method for using your phone to emulate a dial-up modem and is not the way that modern smartphones do tethering anymore. There should be no need to use this value."

You can create a new APN and put all the details in and set apn type as dun and when you save you get the message operator does not allow adding APNs of type dun. Could it be that when you start the hotspot the wifi manager is attempting to use the disabled hotspot dun APN? (Tethering works on stock rom or other devices just to confirm my carrier allows it)

Also the bundled app net monitor tries to load and fails for me everytime - can anyone confirm it is the same for them?

I'm thinking along this kind of idea

/system/etc/apns-conf.xml

Orginal:

<apn carrier="3"

mcc="234"

mnc="20"

apn="three.co.uk"

mmsc="ttp://mms.um.three.co.uk:10021/mmsc"

mmsproxy="mms.three.co.uk"

mmsport="8799"

type="default,supl,mms"

/>

<apn carrier="3 Hotspot"

mcc="234"

mnc="20"

apn="3hotspot"

authtype="0"

type="dun"

/>

Change to:

<apn carrier="3"

mcc="234"

mnc="20"

apn="three.co.uk"

mmsc="ttp://mms.um.three.co.uk:10021/mmsc"

mmsproxy="mms.three.co.uk"

mmsport="8799"

type="default,supl,mms,dun"

/>

and delete the hotspot apn

(H is missing from mmsc - blocked from posting links until 10 posts)

Edit: Updated orginal prefered APN with dun and made no difference :(