Q10 Pro WiFi stuck "turning on"

[apg360]

Good morning everyone,

I have HIMedia Q10 Pro with a faulty WiFi. I will appreciate your help or guidance please.

It is a Chinese hardware version HIMedia Q10 Pro, not European. (* assumption because bought from china)

Originally came with Android 5.1.1, updated to latest firmware (of that time) 7.0 HMD-2.0.7   2018-01-12.113104

Of course I first did L to N firmware update before going to latest firmware.
(http://www.mediafire.com/file/sgwbfs3gqnduwf7/update.zip for Q10 Pro is used to upgrade from Android L OS to Android N 2.0.4 (Android L to Android N)

Before update and after update, Wifi was not working, stuck on "turning on wifi..."

I tried to switch off ethernet before turning on the wifi.
Also Tried factory reset and firmware restore several time.
Nothing helped.

At the time I am writing this, I see a more recent firmware has been released  HMD-2.0.9 2018-07-10.172915.
But I am reluctant to try it as I am pretty sure it won't resolve the issue.


Here the logs output when trying to enable the wifi.
Would appreciate your valuable feedback on what could be the problem behind this issue and if possible a solution I can try out.

*** dmesg
wifi_platform_set_power = 0
======== PULL WL_REG_ON(-1) LOW! ========
wl_android_wifi_on: Failed
dhd_open : wl_android_wifi_on failed (-1)
dhd_stop: Enter d7335800
wl_android_wifi_off in 1
wl_android_wifi_off in 2: g_wifi_on=0, on_failure=1
dhd_wl_ioctl: returning as busstate=0
dhd_net_bus_devreset: dhd_bus_devreset: -35
wifi_platform_set_power = 0
======== PULL WL_REG_ON(-1) LOW! ========
wl_android_wifi_off out
dhd_stop: Exit
dhd_open: Exit ret=-1
init: Service 'bcm_supplicant' (pid 9071) exited with status 255



**adb logcat *:WE
........
07-22 01:34:56.818  2492  2804 E WifiMonitor: startMonitoring(wlan0) failed!
07-22 01:34:56.819  2492  2804 E WifiStateMachine: Failed to setup control channel, restart supplicant
07-22 01:34:56.819  2492  2804 E WifiMonitor: killSupplicant p2ptrue init.svc.wpa_supplicant=unknown init.svc.p2p_supplicant=unknown
07-22 01:35:01.825  2492  2804 E WifiHW  : wifi_get_sdio_device_id,fp is null
07-22 01:35:01.825  2492  2804 E WifiHW  : wifi_get_sdio_device_id,fp is null
07-22 01:35:01.825  2492  2804 E WifiHW  : Cannot find usb supported device,load sdio device
07-22 01:35:03.349  1751  2783 E WifiHW  : wifi_get_sdio_device_id,fp is null
07-22 01:35:03.349  1751  2783 E WifiHW  : wifi_get_sdio_device_id,fp is null
07-22 01:35:03.349  1751  2783 E WifiHW  : Cannot find usb supported device,load sdio device
07-22 01:35:03.349  1751  2783 E SoftapController: Softap fwReload - NULL path for STA
07-22 01:35:03.357  2492  2804 E WifiMonitor: killSupplicant p2ptrue init.svc.wpa_supplicant=unknown init.svc.p2p_supplicant=unknown
07-22 01:35:04.481  2492  2804 E wifi    : Could not set interface wlan0 flags: 1
07-22 01:35:04.481  2492  2804 E WifiNative-HAL: Could not start hal
07-22 01:35:04.481  2492  2804 E WifiStateMachine: Failed to start HAL
07-22 01:35:05.640  9071  9071 E wpa_supplicant: Could not set interface wlan0 flags (UP): Operation not permitted
07-22 01:35:05.640  9071  9071 E wpa_supplicant: nl80211: Could not set interface 'wlan0' UP
07-22 01:35:05.640  9071  9071 E wpa_supplicant: wlan0: Failed to initialize driver interface
07-22 01:35:15.596  2492  2804 E WifiHW  : Supplicant not running, cannot connect
07-22 01:35:16.597  2492  2804 E WifiHW  : Supplicant not running, cannot connect
07-22 01:35:17.598  2492  2804 E WifiHW  : Supplicant not running, cannot connect
07-22 01:35:18.599  2492  2804 E WifiHW  : Supplicant not running, cannot connect
07-22 01:35:19.600  2492  2804 E WifiHW  : Supplicant not running, cannot connect
07-22 01:35:19.600  2492  2804 E WifiMonitor: startMonitoring(wlan0) failed!
07-22 01:35:19.600  2492  2804 E WifiStateMachine: Failed 6 times to start supplicant, unload driver
.......
.......
07-22 02:02:08.297  2492  2804 E WifiHW  : wifi_get_sdio_device_id,fp is null
07-22 02:02:08.297  2492  2804 E WifiHW  : wifi_get_sdio_device_id,fp is null
07-22 02:02:08.297  2492  2804 E WifiHW  : Cannot find usb supported device,load sdio device
07-22 02:02:09.617  1751  2783 E WifiHW  : wifi_get_sdio_device_id,fp is null
07-22 02:02:09.617  1751  2783 E WifiHW  : wifi_get_sdio_device_id,fp is null
07-22 02:02:09.617  1751  2783 E WifiHW  : Cannot find usb supported device,load sdio device
07-22 02:02:09.618  1751  2783 E SoftapController: Softap fwReload - NULL path for STA
07-22 02:02:09.626  2492  2804 E WifiMonitor: killSupplicant p2ptrue init.svc.wpa_supplicant=unknown init.svc.p2p_supplicant=unknown
07-22 02:02:10.785  2492  2804 E wifi    : Could not set interface wlan0 flags: 1
07-22 02:02:10.785  2492  2804 E WifiNative-HAL: Could not start hal
07-22 02:02:10.785  2492  2804 E WifiStateMachine: Failed to start HAL
07-22 02:02:11.979 12818 12818 E wpa_supplicant: Could not set interface wlan0 flags (UP): Operation not permitted
07-22 02:02:11.979 12818 12818 E wpa_supplicant: nl80211: Could not set interface 'wlan0' UP
07-22 02:02:11.980 12818 12818 E wpa_supplicant: wlan0: Failed to initialize driver interface
07-22 02:02:16.978  2492  2646 W ActivityManager: Launch timeout has expired, giving up wake lock!
.......


Kind regards

[apg360]

It seems I am not the only one ....

http://www.futeko.com/newforum/index.php?topic=1031.0

[Joker]

Which version of country firmware did you use to upgrade your box, Chinese or European?

Did you see the warning about upgrading a Chinese Box with the European firmware?

[futeko.com]

It seems I am not the only one ....

http://www.futeko.com/newforum/index.php?topic=1031.0

The thread you link to is more than 2 years old. That Q10 Pro would be running a very old version of Android 5.1. I think the fact it's not been posted on for more than 2 years indicates this is not a common problem.

There are hardware differences between Chinese and 'European' version Q10 Pro. You can't install European firmware and expect a Chinese Q10 Pro to function correctly. Saying that, just because you bought the box from China doesn't mean it's the Chinese version. See here for differences: http://www.futeko.com/newforum/index.php?topic=1175.msg9321#msg9321

If you have the European version I advise installing 2.0.9 and seeing if it makes any difference. If it doesn't then it may be a hardware fault and you should contact your reseller.

[apg360]

<< just because you bought the box from China doesn't mean it's the Chinese version. >>
Thanks goodness ! 

1) I bought from geekbuying
2) It is 16GB
3) Not seen any chinese word ever, at least so far
4) In the box nothing had a single chinese word (box itself, manuals, etc...)
5) I use only firmware from HiMedia support website (http://www.himediatech.com/support.htm)
6) I am right now on the custom firmware from futeko forum (2.0.9 from pcristi)


I have been avoiding European firmware so far because I was convinced my Q10 Pro is chinese version ..... I was wrong, thanks to you.
I only used international firmware so far.

Maybe this could be my solution...... to use futeko forum Q10 Pro Official Firmware (European version) and cross finger.

Full factory reset using that restore button, use futeko firmware (first Android L to Android N) then the rest.
If Full factory reset using restore button does not (downgrade) bring back to the original firmware which came originally (Android 5) then I shall take the downgrading firmware steps instead : http://www.futeko.com/newforum/index.php?topic=1392.msg10920#msg10920

I feel like HiMedia support website and futeko Q10 Pro Official Firmware, are both international firmware.
And all international firmware are also European firmware, no difference between international and european.
Still not sure of this, if somebody knows please help by confirming it.

However what I know is being on custom firmware (2.0.9 from pcristi) hasn't helped.... the original firmware after opening the box, wi-fi did not work neither.
I need a firmware (custom or not) that will attack the bios, to reinitialize the hardware and start with new kernel.

Kind Regards

[rollingrock]

Unplug the power for 30 secs and replug and power back on. Worked for me when wifi got stuck.

[apg360]

Thank you rollingrock,

I tried that already, at first when I was opening the box and using it for the first time. Didn't help.

Unfortunately I am a zero in mobile dev. And unable to find "android dev forums or stackoverflow" that clearly explain my android kernel/system log.

If only I can get confirmation that's its hardware related or not. Because if not hardware, I will then surely taking the risk of messing with BIOS initialization and other (high risk of brick )

But right now, I still have no clue if its software layer, kernel layer or hardware layer.

Thanks again for your reply.
Kind Regards