OPI zero plus 2 H5: Wifi driver loading on boot fails 60% of the time

kokonuts

Hi, I have ordered tow zero+2 H5 boards and on both the wifi does not load on boot all the time. I have to reboot many times till it works. I change nothing just keep rebooting till I get lucky and it loads. Here is logcat when it does not load:

1. 01-01 08:00:18.525 2041-2041/? I/SystemServiceManager: Starting com.android.server.wifi.p2p.WifiP2pService
   
2. 01-01 08:00:18.609 2041-2041/? I/WifiP2pService: Registering wifip2p
   
3. 01-01 08:00:18.613 2041-2041/? I/SystemServiceManager: Starting com.android.server.wifi.WifiService
   
4. 01-01 08:00:18.900 2041-2041/? E/WifiConfigStore: associatedPartialScanPeriodMilli set to 20000
   
5. 01-01 08:00:18.913 2041-2207/? D/WifiHWInfo: /data/misc/wifi/wifi_hardware_info exist, try to get wifi_hardware_info
   
6. 01-01 08:00:18.913 2041-2207/? D/WifiHWInfo: wifi_hardware_info from /data/misc/wifi/wifi_hardware_info: broadcom:ap6212
   
7. 01-01 08:00:18.930 2041-2041/? D/WifiController: isAirplaneModeOn = false, isWifiEnabled = true, isScanningAvailable = false
   
8. 01-01 08:00:18.933 2041-2041/? I/WifiService: Registering wifi
   
9. 01-01 08:00:18.936 2041-2041/? I/SystemServiceManager: Starting com.android.server.wifi.WifiScanningService
   
10. 01-01 08:00:18.936 2041-2041/? I/WifiScanningService: Creating wifiscanner
    
11. 01-01 08:00:18.936 2041-2041/? I/WifiScanningService: Starting wifiscanner
    
12. 01-01 08:00:18.939 2041-2041/? I/SystemServiceManager: Starting com.android.server.wifi.RttService
    
13. 01-01 08:00:18.972 2041-2041/? D/ConnectivityService: wifiOnly=false
    
14. 01-01 08:00:19.115 2041-2207/? D/WifiHW: Unable to unload driver module "bcmdhd": No such file or directory
    
15. 01-01 08:00:19.534 2041-2041/? I/WifiService: WifiService starting up with Wi-Fi enabled
    
16. 01-01 08:00:19.536 2041-2041/? D/WifiService: setWifiEnabled: true pid=2041, uid=1000
    
17. 01-01 08:00:19.536 2041-2041/? E/WifiService: Invoking mWifiStateMachine.setWifiEnabled
    
18. 01-01 08:00:19.541 2041-2214/? D/WifiController: WifiController msg { when=-3ms what=155656 target=com.android.internal.util.StateMachine$SmHandler } deferred for 500ms
    
19. 01-01 08:00:19.549 2041-2214/? D/WifiService: New client listening to asynchronous messages
    
20. 01-01 08:00:19.553 2041-2041/? I/WifiScanningService: Registering wifiscanner
    
21. 01-01 08:00:19.566 2041-2041/? D/WifiScanningService: New client, channel: null messenger: null
    
22. 01-01 08:00:19.581 2041-2249/? D/WifiChangeStateMachine: Entering IdleState
    
23. 01-01 08:00:19.582 2041-2249/? D/WifiScanningService: DefaultState
    
24. 01-01 08:00:19.598 2041-2253/? D/Ethernet: got request NetworkRequest [ id=2, legacyType=1, [ Transports: WIFI Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VPN] ] with score 0
    
25. 01-01 08:00:20.047 2041-2214/? D/WifiController: DEFERRED_TOGGLE handled
    
26. 01-01 08:00:20.048 2041-2207/? D/WifiHW: Start to insmod bcmdhd.ko
    
27. 01-01 08:00:20.048 2041-2207/? D/WifiHW: module_arg=nvram_path=/system/vendor/modules/nvram_ap6212.txt config_path=/system/vendor/modules/config_ap6212.txt
    
28. 01-01 08:00:20.048 2041-2207/? D/WifiHW: module_path=/system/vendor/modules/bcmdhd.ko
    
29. 01-01 08:00:22.879 2041-2041/? D/WifiScanningService: SCAN_AVAILABLE : 1
    
30. 01-01 08:00:22.910 2041-2249/? D/WifiScanningService: DefaultState got{ when=-1ms what=160007 target=com.android.internal.util.StateMachine$SmHandler }
    
31. 01-01 08:01:14.725 2041-2207/? E/WifiHW: insmod bcmdhd ko failed!
    
32. 01-01 08:01:14.725 2041-2207/? D/WifiHW: Unable to unload driver module "bcmdhd": No such file or directory
    
33. 01-01 08:01:14.737 2041-2207/? E/WifiStateMachine: Failed to load driver
    
34. 01-01 08:01:14.755 2041-2207/? D/WIFI: Registering NetworkFactory
    
35. 01-01 08:01:14.760 2041-2207/? D/WIFI_UT: Registering NetworkFactory
    
36. 01-01 08:01:14.760 2041-2217/? D/ConnectivityService: Got NetworkFactory Messenger for WIFI
    
37. 01-01 08:01:14.760 2041-2217/? D/ConnectivityService: Got NetworkFactory Messenger for WIFI_UT
    
38. 01-01 08:01:14.763 2041-2207/? D/WIFI: got request NetworkRequest [ id=2, legacyType=1, [ Transports: WIFI Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VPN] ] with score 0
    
39. 01-01 08:01:14.767 2041-2207/? D/WIFI: got request NetworkRequest [ id=1, legacyType=-1, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VPN] ] with score 0
    
40. 01-01 08:01:14.767 2041-2207/? D/WIFI_UT: got request NetworkRequest [ id=2, legacyType=1, [ Transports: WIFI Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VPN] ] with score 0
    
41. 01-01 08:01:14.768 2041-2207/? D/WIFI_UT: got request NetworkRequest [ id=1, legacyType=-1, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VPN] ] with score 0
    
42. 
    

Copy code

I do not understand why they keep making unusable boards and they never release fixed ROM. they keep making and we keep buying boards with crap ROM. It is sad because the hardware is good, but the ROM sucks.

Any ideas how to fix this problem? is it race condition? why would it work only sometimes?

Thanks.

kotcza

you can:
1/ use armbian
2/ buy h3 version of opi0+2 and use h3droid

kokonuts

I have many other working android boards, but they are all closed source. I need a board that comes with a working open source tree that's why I bought Orange Pi. There is also Khadas but pretty expensive. Do you know of any other alternatives, since Orange pi does not care about providing a work rom, they seem just want to put hardware out to get sales.

kotcza

its hard to find any cheaper, so you get what you pay for. and if you want to work on the source it's doable, for example i've grabbed H2+ dump of android 4.4.2 (i think it was one of the latest) and followed http://www.orangepi.org/Docs/BuildingyourownAndroidfirmware.html
keep in mind instructions are for another soc but overall works (for example h2/h3 platform is named dolphin, i think h5 is named cheetah). it took me a lot of work to make it stable and added lots of features, but it's doable. i still recommend getting h3 board too

kokonuts

I understand the price/quality compromise, but it is WIFI that I am talking about. It is pretty fundamental thing.  I am just wondering how come other people buying it, just to be disappointed and frustrated.

I have ordered the H3 version. Thanks for your responses!

ecolyx

We buy because they are cheap and look usable. There appears enough information to get a working linux system and begin development, but as you and we all find out, the images and information provided are simply not enough for the majority, do not work out of the box, and the learning curve to fix everything is steep.

I kind of feel like we were sold prototypes of boards that have been superceded.

Armbian is using a later kernel with better wifi support. It shouldn't be so hard to create an ubuntu or debian from the xunlong build system, using the later kernel, but the process isn't straightforward.

I keep revisiting every few months and find we are closer to where I can contribute, or just start porting/developing, learning something new each time.

Next mainline kernel release (4.17) is significant for H5, but I'm still trying to get from using downloaded images that I can run, but don't work well enough, to using images I build myself.  Getting the image to boot from SD is latest challenge.

igorpec

But both Plus2 H3 and Plus2 H5 have the same wireless Broadcom based chip AP6212 ... which is in fact pretty decent.

kokonuts

AP6212 is ok and working in many boards, but Orange Android ROM for H5 is not.