Wifi doesn't auto connect after reboot

[Aradyn]

Does anyone else have this problem? After rebooting, wifi is technically turned on, but doesn't connect. After I click on the wifi settings it then auto detects my network and auto connects. Is there a setting I can try to get it to auto connect when the Android PI starts up?

Using build: rtandroid-n-20160814-rpi3 currently.

[Igor Kalkov]

There is an open issue for this: https://github.com/peyo-hd/device_brcm_rpi3/issues/19

But it seems nobody tried to debug it yet.

[Aradyn]

Day 2 of debug leaves me at the same starting point, just with a lot more information learned.

I have noticed that settings do not seem to save properly, such as changing the region code with" # iw reg set US" After setting this, it does not save. So my testing has pretty much gotten me no where. After I compile more information I plan to reach out to the Android Linux Kernal group to see if anyone there has any suggestions on how to change some of the settings.

In the meantime, I know how to CHANGE the power_save state using "iw dev wlan0 set power_save on" but I don't know of any commands to check it and see if my change actually saved. Does anyone know of a setting to verify what the power_save state is currently set to (before and after the command)?

[Aradyn]

Quick side comment, I used iw dev wlan0 power_save off, not on. I need to verify that it is actually saving as off though.

[Igor Kalkov]

I don't know much about the wifi interface, but just as a hint: Are you keeping track of the "dmesg" and "logcat" output on saving new settings? Maybe there are error messages or something we can use to narrow down the actual problem.

[Aradyn]

No I am not. I am not familiar with linux logging. I will try to brush up my knowledge on it tomorrow night.

[Igor Kalkov]

Well, it's not very difficult. I assume you have a working ADB connection:

> adb logcat

Will output the full (Android) system log. It usually includes all the apps' output and everything what is happening in the system. The output is continuous, so you have to explicitly terminate it with Ctrl+C.

I think you can ignore the beginning of the log and just monitor changes in the output during your changes in the settings.

> adb shell dmesg

Will output the full (Linux kernel) system log. This one includes low level (drivers and kernel) information and isn't continouos. You will only see what happened prior to your call.

I don't actually know how Linux professionals are using this - I usually just call it twice (before and after some actions) and compare the outputs.

[imguru...@gmail.com]

We are also facing the same issue.we tried to install some third party apps(https://play.google.com/store/apps/details?id=de.j4velin.wifiAutoOff&hl=en), which connects the Android automatically to wifi. But this does not help after reboot for RPI. Please post the solution if any finds it.

[maurice...@gmail.com]

It is strange, because it sees the WiFi networks but I think ignores them:

01-01 01:00:25.933   439   439 D ConnectivityService: ConnectivityService starting up
01-01 01:00:25.937   439   439 D ConnectivityService: wifiOnly=true
01-01 01:00:25.938   439   439 E ConnectivityService: Ignoring protectedNetwork 10
01-01 01:00:25.938   439   439 E ConnectivityService: Ignoring protectedNetwork 11
01-01 01:00:25.938   439   439 E ConnectivityService: Ignoring protectedNetwork 12
01-01 01:00:25.938   439   439 E ConnectivityService: Ignoring protectedNetwork 14
01-01 01:00:25.938   439   439 E ConnectivityService: Ignoring protectedNetwork 15

Op woensdag 17 augustus 2016 13:31:21 UTC+2 schreef Aradyn:

[maurice...@gmail.com]

Or it just gives another ¨no such file or directory¨, there are as far as I can see a lot of errors in the logcat, so good luck ;) :

01-01 01:00:27.182   439   489 D wifi    : set interface wlan0 flags (UP)
01-01 01:00:27.182   439   489 I WifiHAL : Initializing wifi
01-01 01:00:27.182   439   489 I WifiHAL : Creating socket
01-01 01:00:27.196   536   536 W System  : ClassLoader referenced unknown path: /system/priv-app/SystemUI/lib/arm
01-01 01:00:27.198   439   489 I WifiHAL : Initialized Wifi HAL Successfully; vendor cmd = 103
01-01 01:00:27.199   439   489 D wifi    : Did set static halHandle = 0xa4b3d8e0
01-01 01:00:27.199   439   489 D wifi    : halHandle = 0xa4b3d8e0, mVM = 0xafab20c0, mCls = 0x10092a
01-01 01:00:27.199   439   489 D wifi    : array field set
01-01 01:00:27.213   439   575 I WifiNative-HAL: Waiting for HAL events mWifiHalHandle=-1531717408
01-01 01:00:27.213   439   575 D wifi    : waitForHalEvents called, vm = 0xafab20c0, obj = 0x10092a, env = 0x9b4a3190
01-01 01:00:27.218   439   489 D WifiMonitor: startMonitoring(wlan0) with mConnected = false
01-01 01:00:27.219   439   489 E WifiHW  : Unable to open connection to supplicant on "@android:wpa_wlan0": No such file or directory

Op zondag 22 januari 2017 13:28:43 UTC+1 schreef maurice...@gmail.com: