FORUMS

Wifi Keeps turning on but never turn on (MAC address shows 20:00:00:00:00:00)

271 posts
Thanks Meter: 80
 
By tanipat, Senior Member on 26th November 2015, 04:15 AM
Post Reply Email Thread
7th January 2016, 06:57 AM |#31  
NLBeev's Avatar
Senior Member
Flag Scheveningen
Thanks Meter: 1,900
 
More
Quote:
Originally Posted by DefectiveRobot

...Wifi still does not turn on.....I'll re-root it tomorrow

Have seen the same WiFi issue as yours with a Samsung S3.
Cause was the interfering and strong wifi-signal from an accespoint of the neighbours.
7th January 2016, 09:11 AM |#32  
Senior Member
Thanks Meter: 1,194
 
More
Quote:
Originally Posted by DefectiveRobot

Thanks - The text files at that location definitely seem to be where it pulls its display info from when I run:

Code:
#ip link show wlan0
My actual mac address appears correctly there, as well as in binary file: /persist/wifi/.macaddr

I am leaning away from this issue being a corrupted /persist and more towards it being a driver issue. I was able to get wifi to turn back on by adding the line "ap_scan=1" to the /data/misc/wifi/wpa_supplicant.conf file, as suggested by this thread, but it did not survive a reboot. Like the experience of @jpsflores, the line was automatically removed from the wpa_supplicant.conf, and now I can't get wifi back with or without any of these lines in the wpa_supplicant.conf file:
Code:
ap_scan=1
ctrl_interface=wlan0
disable_scan_offload=0
So, I am quite frustrated. The few times wifi appeared, it seemed to be a fluke, and lasted only about an hour or until a reboot. Now I am not sure what to do.

---------- Post added at 05:03 PM ---------- Previous post was at 04:53 PM ----------



Thank you. However, this wifi problem started after the phone took an OTA to 6.0.0 Marshmallow. It is currently running the stock MRA58R build.

I am considering flashing the 6.0.1 MMB29S factory image, hoping the wifi driver might get replaced. Does anyone know if the radio changes from 6.0.0 to 6.0.1?

AFAIK the wifi driver is in the kernel, not in the radio.
The Following User Says Thank You to Droidphilev For This Useful Post: [ View ] Gift Droidphilev Ad-Free
7th January 2016, 03:29 PM |#33  
DefectiveRobot's Avatar
Member
Thanks Meter: 6
 
More
Quote:
Originally Posted by NLBeev

Have seen the same WiFi issue as yours with a Samsung S3.
Cause was the interfering and strong wifi-signal from an accespoint of the neighbours.

A strong wifi signal masked your mac address and prevented the wifi from even turning on? Wouldn't you at least have to be able to turn on the wifi first before being affected by such a rogue signal? Also, after seeing the behavior in more than one location (at home and at work) I could say that in my case at least, it is not environmental.

However, thanks for highlighting that the problem is not unique to the Nexus 6. In my searching, I found tons of Nexus 5 users and some Samsung users complaining of the exact same symptoms.

Strangely, unlike most others, I can toggle bluetooth on and off all day long, but I can't toggle wifi to the on state.
7th January 2016, 05:32 PM |#34  
DefectiveRobot's Avatar
Member
Thanks Meter: 6
 
More
Quote:
Originally Posted by Droidphilev

AFAIK the wifi driver is in the kernel, not in the radio.

Yes - and either way, replacing both had no effect. Flashed the stock image of MMB29S, and still no wifi.

Re-rooting was easy without a build.img using SuperSU 2.6.6, and as expected, the /data/misc/wifi/wpa_supplicant.conf reverts to the template from /system/etc/wifi/wpa_supplicant.conf, and looks like this now, with the default "ap_scan=1":
Code:
update_config=1
eapol_version=1
ap_scan=1
fast_reauth=1
pmf=1
But I am curious.... how does a wpa_supplicant.conf file go from looking like the above, to looking like this, which is how mine was right after the problems started?
Code:
disable_scan_offload=1
driver_param=use_p2p_group_interface=1p2p_device=1
update_config=1
device_name=shamu
manufacturer=motorola
model_name=Nexus 6
model_number=Nexus 6
serial_number=**********
device_type=10-0050F204-5
config_methods=physical_display virtual_push_button
p2p_no_go_freq=5170-5740
pmf=1
external_sim=1
wowlan_triggers=any
p2p_search_delay=0

network={
	ssid="**"
	psk="************"
	key_mgmt=WPA-PSK
	priority=1
}

network={
	ssid="******"
	psk="********"
	key_mgmt=WPA-PSK
	priority=2
}
I mean, what process goes in and changes this file over the life of the phone?
7th January 2016, 06:01 PM |#35  
NLBeev's Avatar
Senior Member
Flag Scheveningen
Thanks Meter: 1,900
 
More
Quote:
Originally Posted by DefectiveRobot

.... after seeing the behavior in more than one location (at home and at work) I could say that in my case at least, it is not environmental...

Then there are only setting options left to try out.
1. WiFi interval (root)
Add/set in the file build.prop --> WiFi_supplicant_scan_interval; value of your choice (mine 200 for battery life). App: build.prop editor.
2. WiFi settings - Advanced: during sleep - never; frequency - 2,4 Ghz (manual)
8th January 2016, 08:46 PM |#36  
DefectiveRobot's Avatar
Member
Thanks Meter: 6
 
More
Quote:
Originally Posted by DefectiveRobot

...what process goes in and changes this file over the life of the phone?

Apparently, it is the wpa_supplicant binary that updates its own config, as long as "update_config=1" is present. I found a line-by-line explanation of the wpa_supplicant.conf file that sheds some light on the various directives used. Obviously, the network keys get added, but also the model name, serial number, and device type get added to the conf file for handshaking with an accesspoint. So, I imagine the other directives get added over time to optimize the connection, or assert preferences. Is that correct? That said, it looks like the wpa_supplicant's only role is to assist in scanning, selecting, and handshaking the credentials with available connections. My current, stock, and rather sparse wpa_supplicant.conf file says nothing to suggest it is the problem.

But there is a lower level service that handles the wifi on/off state, and which likely communicates the current mac and ip to the system for display (where the 02:00:00:00:00:00 is coming from). Either:
  1. the wifi service can't start the supplicant, or
  2. it can't read the info it needs to start properly, or
  3. the physical chip is damaged and isn't responding to the driver.

So, I've tried "svc wifi disable" and "svc wifi enable" with no change in behavior. Taking a deeper peek, I ran "dumpsys wifi" right after attempting to toggle wifi on, and this is what it returns:
Code:
Wi-Fi is unknown state
Stay-awake conditions: 0
mMulticastEnabled 0
mMulticastDisabled 0
mInIdleMode false
mScanPending false
WifiController:
 total records=60
 rec[0]: time=01-03 02:36:52.576 processed=DefaultState org=ApStaDisabledState dest=<null> what=155652(0x26004)
 rec[1]: time=01-03 02:36:52.602 processed=DefaultState org=ApStaDisabledState dest=<null> what=155652(0x26004)
 rec[2]: time=01-03 02:37:11.709 processed=DefaultState org=ApStaDisabledState dest=<null> what=155650(0x26002)
 rec[3]: time=01-03 02:37:11.846 processed=DefaultState org=ApStaDisabledState dest=<null> what=155651(0x26003)
 rec[4]: time=01-03 02:37:39.759 processed=DefaultState org=ApStaDisabledState dest=<null> what=155652(0x26004)
 rec[5]: time=01-03 02:37:40.120 processed=DefaultState org=ApStaDisabledState dest=<null> what=155652(0x26004)
 rec[6]: time=01-03 02:38:39.759 processed=DefaultState org=ApStaDisabledState dest=<null> what=155652(0x26004)
 rec[7]: time=01-03 02:38:40.288 processed=DefaultState org=ApStaDisabledState dest=<null> what=155652(0x26004)
 rec[8]: time=01-03 02:39:40.444 processed=DefaultState org=ApStaDisabledState dest=<null> what=155652(0x26004)
 rec[9]: time=01-03 02:40:40.610 processed=DefaultState org=ApStaDisabledState dest=<null> what=155652(0x26004)
 rec[10]: time=01-03 02:41:39.754 processed=DefaultState org=ApStaDisabledState dest=<null> what=155652(0x26004)
 rec[11]: time=01-03 02:41:40.770 processed=DefaultState org=ApStaDisabledState dest=<null> what=155652(0x26004)
 rec[12]: time=01-03 02:43:39.755 processed=DefaultState org=ApStaDisabledState dest=<null> what=155652(0x26004)
 rec[13]: time=01-03 02:43:41.091 processed=DefaultState org=ApStaDisabledState dest=<null> what=155652(0x26004)
 rec[14]: time=01-03 02:44:41.250 processed=DefaultState org=ApStaDisabledState dest=<null> what=155652(0x26004)
 rec[15]: time=01-03 02:45:39.757 processed=DefaultState org=ApStaDisabledState dest=<null> what=155652(0x26004)
 rec[16]: time=01-03 02:45:41.410 processed=DefaultState org=ApStaDisabledState dest=<null> what=155652(0x26004)
 rec[17]: time=01-03 02:46:39.757 processed=DefaultState org=ApStaDisabledState dest=<null> what=155652(0x26004)
 rec[18]: time=01-03 02:46:41.572 processed=DefaultState org=ApStaDisabledState dest=<null> what=155652(0x26004)
 rec[19]: time=01-03 02:47:10.792 processed=ApStaDisabledState org=ApStaDisabledState dest=DeviceActiveState what=155656(0x26008)
 rec[20]: time=01-03 02:47:39.757 processed=DefaultState org=DeviceActiveState dest=<null> what=155652(0x26004)
 rec[21]: time=01-03 02:47:41.713 processed=DefaultState org=DeviceActiveState dest=<null> what=155652(0x26004)
 rec[22]: time=01-03 02:48:00.882 processed=DefaultState org=DeviceActiveState dest=<null> what=155650(0x26002)
 rec[23]: time=01-03 02:48:07.420 processed=DeviceActiveState org=DeviceActiveState dest=<null> what=155660(0x2600c)
 rec[24]: time=01-03 02:48:13.841 processed=DefaultState org=DeviceActiveState dest=<null> what=155652(0x26004)
 rec[25]: time=01-03 02:48:13.949 processed=DefaultState org=DeviceActiveState dest=<null> what=155652(0x26004)
 rec[26]: time=01-03 02:48:41.889 processed=DefaultState org=DeviceActiveState dest=<null> what=155652(0x26004)
 rec[27]: time=01-03 02:48:47.829 processed=DefaultState org=DeviceActiveState dest=<null> what=155652(0x26004)
 rec[28]: time=01-03 02:48:47.918 processed=DefaultState org=DeviceActiveState dest=<null> what=155652(0x26004)
 rec[29]: time=01-03 02:48:51.782 processed=DefaultState org=DeviceActiveState dest=<null> what=155652(0x26004)
 rec[30]: time=01-03 02:48:52.560 processed=DefaultState org=DeviceActiveState dest=<null> what=155652(0x26004)
 rec[31]: time=01-03 02:48:52.634 processed=DefaultState org=DeviceActiveState dest=<null> what=155652(0x26004)
 rec[32]: time=01-03 02:48:52.886 processed=DefaultState org=DeviceActiveState dest=<null> what=155652(0x26004)
 rec[33]: time=01-03 02:48:53.019 processed=DefaultState org=DeviceActiveState dest=<null> what=155652(0x26004)
 rec[34]: time=01-03 02:49:38.361 processed=DefaultState org=DeviceActiveState dest=<null> what=155651(0x26003)
 rec[35]: time=01-03 02:49:42.047 processed=DefaultState org=DeviceActiveState dest=<null> what=155652(0x26004)
 rec[36]: time=01-03 02:49:53.028 processed=DefaultState org=DeviceActiveState dest=<null> what=155652(0x26004)
 rec[37]: time=01-03 02:50:42.213 processed=DefaultState org=DeviceActiveState dest=<null> what=155652(0x26004)
 rec[38]: time=01-03 02:50:53.032 processed=DefaultState org=DeviceActiveState dest=<null> what=155652(0x26004)
 rec[39]: time=01-03 02:51:42.369 processed=DefaultState org=DeviceActiveState dest=<null> what=155652(0x26004)
 rec[40]: time=01-03 02:52:42.531 processed=DefaultState org=DeviceActiveState dest=<null> what=155652(0x26004)
 rec[41]: time=01-03 02:52:53.033 processed=DefaultState org=DeviceActiveState dest=<null> what=155652(0x26004)
 rec[42]: time=01-03 02:53:42.693 processed=DefaultState org=DeviceActiveState dest=<null> what=155652(0x26004)
 rec[43]: time=01-03 02:54:42.854 processed=DefaultState org=DeviceActiveState dest=<null> what=155652(0x26004)
 rec[44]: time=01-03 02:54:53.032 processed=DefaultState org=DeviceActiveState dest=<null> what=155652(0x26004)
 rec[45]: time=01-03 02:55:43.018 processed=DefaultState org=DeviceActiveState dest=<null> what=155652(0x26004)
 rec[46]: time=01-03 02:55:53.032 processed=DefaultState org=DeviceActiveState dest=<null> what=155652(0x26004)
 rec[47]: time=01-03 02:56:43.168 processed=DefaultState org=DeviceActiveState dest=<null> what=155652(0x26004)
 rec[48]: time=01-03 02:56:53.032 processed=DefaultState org=DeviceActiveState dest=<null> what=155652(0x26004)
 rec[49]: time=01-03 02:57:43.335 processed=DefaultState org=DeviceActiveState dest=<null> what=155652(0x26004)
 rec[50]: time=01-03 02:58:43.485 processed=DefaultState org=DeviceActiveState dest=<null> what=155652(0x26004)
 rec[51]: time=01-03 02:58:53.028 processed=DefaultState org=DeviceActiveState dest=<null> what=155652(0x26004)
 rec[52]: time=01-03 02:59:43.648 processed=DefaultState org=DeviceActiveState dest=<null> what=155652(0x26004)
 rec[53]: time=01-03 02:59:53.031 processed=DefaultState org=DeviceActiveState dest=<null> what=155652(0x26004)
 rec[54]: time=01-03 02:59:57.086 processed=DefaultState org=DeviceActiveState dest=<null> what=155650(0x26002)
 rec[55]: time=01-03 03:00:02.338 processed=DeviceActiveState org=DeviceActiveState dest=<null> what=155660(0x2600c)
 rec[56]: time=01-03 03:00:08.742 processed=StaEnabledState org=DeviceActiveState dest=<null> what=155657(0x26009)
 rec[57]: time=01-03 03:00:08.747 processed=DefaultState org=DeviceActiveState dest=<null> what=155654(0x26006)
 rec[58]: time=01-03 03:00:08.915 processed=DefaultState org=DeviceActiveState dest=<null> what=155654(0x26006)
 rec[59]: time=01-03 03:00:10.007 processed=StaEnabledState org=DeviceActiveState dest=<null> what=155656(0x26008)
curState=DeviceActiveState
mScreenOff false
mDeviceIdle false
mPluggedType 2
mIdleMillis 900000
mSleepPolicy 2
mPersistWifiState 1
mAirplaneModeOn false
mNotificationEnabled true
mNotificationRepeatTime 0
mNotificationShown false
mNumScansSinceNetworkStateChange 0
mEnableTrafficStatsPoll false
mTrafficStatsPollToken 0
mTxPkts 0
mRxPkts 0
mDataActivity 0
Latest scan results:

Locks acquired: 0 full, 0 full high perf, 1 scan
Locks released: 0 full, 0 full high perf, 1 scan

Locks held:
Multicast Locks held:
WifiWatchdogStateMachine:
 total records=0
curState=NotConnectedState
mWifiInfo: [null]
mLinkProperties: [null]
mCurrentSignalLevel: [0]
mPoorNetworkDetectionEnabled: [false]

WifiStateMachine:
 total records=46
 rec[0]: time=01-03 02:36:49.467 processed=DefaultState org=InitialState dest=<null> what=131154(0x20052) CMD_ENABLE_RSSI_POLL  rt=14980/14980 1 0
 rec[1]: time=01-03 02:36:49.468 processed=DefaultState org=InitialState dest=<null> what=69632(0x11000) AsyncChannel.CMD_CHANNEL_HALF_CONNECTED  rt=14981/14981 0 0
 rec[2]: time=01-03 02:36:49.544 processed=DefaultState org=InitialState dest=<null> what=131084(0x2000c) (-5)CMD_STOP_SUPPLICANT  rt=15057/15057 0 0
 rec[3]: time=01-03 02:36:54.149 processed=DefaultState org=InitialState dest=<null> what=131133(0x2003d) CMD_GET_SUPPORTED_FEATURES uid=10014  rt=19662/19662 0 0
 rec[4]: time=01-03 02:37:01.125 processed=DefaultState org=InitialState dest=<null> what=131206(0x20086) CMD_BOOT_COMPLETED  rt=26638/26638 0 0
 rec[5]: time=01-03 02:37:11.705 processed=DefaultState org=InitialState dest=<null> what=131167(0x2005f) !CMD_SCREEN_STATE_CHANGED  rt=37219/37219 1 0
 rec[6]: time=01-03 02:37:11.706 processed=DefaultState org=InitialState dest=<null> what=131154(0x20052) !CMD_ENABLE_RSSI_POLL  rt=37219/37219 1 0
 rec[7]: time=01-03 02:37:11.707 processed=DefaultState org=InitialState dest=<null> what=131158(0x20056) !CMD_SET_SUSPEND_OPT_ENABLED  rt=37220/37220 0 0
 rec[8]: time=01-03 02:37:11.708 processed=DefaultState org=InitialState dest=<null> what=131129(0x20039) !(-5)CMD_CLEAR_BLACKLIST  rt=37221/37221 0 0
 rec[9]: time=01-03 02:37:11.798 processed=DefaultState org=InitialState dest=<null> what=131167(0x2005f) CMD_SCREEN_STATE_CHANGED  rt=37311/37311 0 0
 rec[10]: time=01-03 02:37:11.799 processed=DefaultState org=InitialState dest=<null> what=131154(0x20052) CMD_ENABLE_RSSI_POLL  rt=37312/37312 0 0
 rec[11]: time=01-03 02:37:11.801 processed=DefaultState org=InitialState dest=<null> what=131158(0x20056) CMD_SET_SUSPEND_OPT_ENABLED  rt=37314/37314 1 0
 rec[12]: time=01-03 02:47:16.417 processed=InitialState org=InitialState dest=SupplicantStartingState what=131083(0x2000b) CMD_START_SUPPLICANT  rt=641929/641930 0 0
 rec[13]: time=01-03 02:47:16.418 processed=SupplicantStartingState org=SupplicantStartingState dest=<null> what=131144(0x20048) (-4)CMD_SET_OPERATIONAL_MODE  rt=641931/641931 1 0
 rec[14]: time=01-03 02:47:16.420 processed=SupplicantStartingState org=SupplicantStartingState dest=<null> what=131085(0x2000d) (-4)CMD_START_DRIVER  rt=641933/641933 0 0
 rec[15]: time=01-03 02:47:16.422 processed=DefaultState org=SupplicantStartingState dest=<null> what=131149(0x2004d) CMD_SET_HIGH_PERF_MODE  rt=641935/641935 0 0
 rec[16]: time=01-03 02:47:16.424 processed=SupplicantStartingState org=SupplicantStartingState dest=InitialState what=147458(0x24002) SUP_DISCONNECTION_EVENT  rt=641937/641937 0 0
 rec[17]: time=01-03 02:47:16.628 processed=DefaultState org=InitialState dest=<null> what=131144(0x20048) (-5)CMD_SET_OPERATIONAL_MODE  rt=642141/642141 1 0
 rec[18]: time=01-03 02:47:16.630 processed=DefaultState org=InitialState dest=<null> what=131085(0x2000d) (-5)CMD_START_DRIVER  rt=642143/642143 0 0
 rec[19]: time=01-03 02:47:37.048 processed=InitialState org=InitialState dest=SupplicantStartingState what=131083(0x2000b) CMD_START_SUPPLICANT  rt=662561/662561 0 0
 rec[20]: time=01-03 02:47:37.050 processed=SupplicantStartingState org=SupplicantStartingState dest=InitialState what=147458(0x24002) SUP_DISCONNECTION_EVENT  rt=662563/662563 0 0
 rec[21]: time=01-03 02:47:57.668 processed=InitialState org=InitialState dest=SupplicantStartingState what=131083(0x2000b) CMD_START_SUPPLICANT  rt=683181/683181 0 0
 rec[22]: time=01-03 02:47:57.670 processed=SupplicantStartingState org=SupplicantStartingState dest=InitialState what=147458(0x24002) SUP_DISCONNECTION_EVENT  rt=683183/683183 0 0
 rec[23]: time=01-03 02:48:00.725 processed=DefaultState org=InitialState dest=<null> what=131167(0x2005f) !CMD_SCREEN_STATE_CHANGED  rt=686238/686238 1 0
 rec[24]: time=01-03 02:48:00.725 processed=DefaultState org=InitialState dest=<null> what=131154(0x20052) !CMD_ENABLE_RSSI_POLL  rt=686238/686238 1 0
 rec[25]: time=01-03 02:48:00.726 processed=DefaultState org=InitialState dest=<null> what=131158(0x20056) !CMD_SET_SUSPEND_OPT_ENABLED  rt=686239/686239 0 0
 rec[26]: time=01-03 02:48:00.726 processed=DefaultState org=InitialState dest=<null> what=131129(0x20039) !(-5)CMD_CLEAR_BLACKLIST  rt=686239/686239 0 0
 rec[27]: time=01-03 02:48:18.241 processed=InitialState org=InitialState dest=SupplicantStartingState what=131083(0x2000b) !CMD_START_SUPPLICANT  rt=703754/703754 0 0
 rec[28]: time=01-03 02:48:18.244 processed=DefaultState org=SupplicantStartingState dest=<null> what=131214(0x2008e) !(-5)CMD_RELOAD_TLS_AND_RECONNECT  rt=703757/703757 0 0
 rec[29]: time=01-03 02:48:18.246 processed=DefaultState org=SupplicantStartingState dest=<null> what=131135(0x2003f) !CMD_GET_LINK_LAYER_STATS uid=1000  rt=703759/703759 0 0
 rec[30]: time=01-03 02:48:18.249 processed=SupplicantStartingState org=SupplicantStartingState dest=InitialState what=147458(0x24002) !SUP_DISCONNECTION_EVENT  rt=703762/703762 0 0
 rec[31]: time=01-03 02:48:18.454 processed=DefaultState org=InitialState dest=<null> what=131135(0x2003f) !CMD_GET_LINK_LAYER_STATS uid=1000  rt=703967/703967 0 0
 rec[32]: time=01-03 02:48:28.753 processed=InitialState org=InitialState dest=SupplicantStartingState what=131083(0x2000b) !CMD_START_SUPPLICANT  rt=714266/714266 0 0
 rec[33]: time=01-03 02:48:28.755 processed=SupplicantStartingState org=SupplicantStartingState dest=InitialState what=147458(0x24002) !SUP_DISCONNECTION_EVENT  rt=714268/714268 0 0
 rec[34]: time=01-03 02:48:39.231 processed=InitialState org=InitialState dest=SupplicantStartingState what=131083(0x2000b) !CMD_START_SUPPLICANT  rt=724744/724744 0 0
 rec[35]: time=01-03 02:48:39.232 processed=SupplicantStartingState org=SupplicantStartingState dest=InitialState what=147458(0x24002) !SUP_DISCONNECTION_EVENT  rt=724745/724745 0 0
 rec[36]: time=01-03 02:48:47.917 processed=DefaultState org=InitialState dest=<null> what=131135(0x2003f) !CMD_GET_LINK_LAYER_STATS uid=1000  rt=733430/733430 0 0
 rec[37]: time=01-03 02:48:53.014 processed=DefaultState org=InitialState dest=<null> what=131135(0x2003f) !CMD_GET_LINK_LAYER_STATS uid=1000  rt=738527/738527 0 0
 rec[38]: time=01-03 02:49:38.238 processed=DefaultState org=InitialState dest=<null> what=131167(0x2005f) CMD_SCREEN_STATE_CHANGED  rt=783751/783751 0 0
 rec[39]: time=01-03 02:49:38.240 processed=DefaultState org=InitialState dest=<null> what=131154(0x20052) CMD_ENABLE_RSSI_POLL  rt=783753/783753 0 0
 rec[40]: time=01-03 02:49:38.242 processed=DefaultState org=InitialState dest=<null> what=131158(0x20056) CMD_SET_SUSPEND_OPT_ENABLED  rt=783755/783755 1 0
 rec[41]: time=01-03 02:59:56.994 processed=DefaultState org=InitialState dest=<null> what=131167(0x2005f) !CMD_SCREEN_STATE_CHANGED  rt=1402507/1402507 1 0
 rec[42]: time=01-03 02:59:56.994 processed=DefaultState org=InitialState dest=<null> what=131154(0x20052) !CMD_ENABLE_RSSI_POLL  rt=1402507/1402507 1 0
 rec[43]: time=01-03 02:59:56.995 processed=DefaultState org=InitialState dest=<null> what=131158(0x20056) !CMD_SET_SUSPEND_OPT_ENABLED  rt=1402508/1402508 0 0
 rec[44]: time=01-03 02:59:56.995 processed=DefaultState org=InitialState dest=<null> what=131129(0x20039) !(-5)CMD_CLEAR_BLACKLIST  rt=1402508/1402508 0 0
 rec[45]: time=01-03 03:00:10.010 processed=DefaultState org=InitialState dest=<null> what=131131(0x2003b) !CMD_GET_CONFIGURED_NETWORKS uid=10029  rt=1415523/1415523 10029 0 num=0
curState=InitialState
SupplicantStateTracker:
 total records=0
curState=UninitializedState
mAuthenticationFailuresCount 0
mAuthFailureInSupplicantBroadcast false
mNetworksDisabledDuringConnect false

mLinkProperties {LinkAddresses: []  Routes: [] DnsAddresses: [] Domains: null MTU: 0}
mWifiInfo SSID: <unknown ssid>, BSSID: <none>, MAC: 02:00:00:00:00:00, Supplicant state: UNINITIALIZED, RSSI: -127, Link speed: -1Mbps, Frequency: -1MHz, Net ID: -1, Metered hint: false, score: 0
mDhcpResults null
mNetworkInfo [type: WIFI[], state: UNKNOWN/IDLE, reason: (unspecified), extra: (none), roaming: false, failover: false, isAvailable: false]
mLastSignalLevel -1
mLastBssid null
mLastNetworkId -1
mOperationalMode 1
mUserWantsSuspendOpt true
mSuspendOptNeedsDisabled 4
Supplicant status null
mLegacyPnoEnabled false
mDriverSetCountryCode null
mConnectedModeGScanOffloadStarted false
mGScanPeriodMilli 0
mConnectionRequests 1
mUntrustedReqCount 0

Dump of WifiConfigStore
mLastPriority -1
Configured networks

WifiConfigStore - Log Begin ----
01-03 02:37:11.705 - wlan0: 0:IFNAME=wlan0 SET pno 0 -> false
01-03 02:37:11.798 - wlan0: 1:IFNAME=wlan0 SET pno 0 -> false
01-03 02:47:10.906 - startHal stack:  - startHal - processMessage - processMsg - handleMessage - dispatchMessage - loop
01-03 02:47:11.404 - p2p0: connectToSupplicant
01-03 02:47:12.409 - p2p0: connectToSupplicant
01-03 02:47:13.411 - p2p0: connectToSupplicant
01-03 02:47:14.412 - p2p0: connectToSupplicant
01-03 02:47:15.414 - p2p0: connectToSupplicant
01-03 02:47:16.415 - p2p0: connectToSupplicant
01-03 02:47:21.450 - startHal stack:  - startHal - processMessage - processMsg - handleMessage - dispatchMessage - loop
01-03 02:47:22.017 - p2p0: connectToSupplicant
01-03 02:47:33.035 - p2p0: connectToSupplicant
01-03 02:47:34.038 - p2p0: connectToSupplicant
01-03 02:47:35.041 - p2p0: connectToSupplicant
01-03 02:47:36.044 - p2p0: connectToSupplicant
01-03 02:47:37.046 - p2p0: connectToSupplicant
01-03 02:47:42.075 - startHal stack:  - startHal - processMessage - processMsg - handleMessage - dispatchMessage - loop
01-03 02:47:42.635 - p2p0: connectToSupplicant
01-03 02:47:53.660 - p2p0: connectToSupplicant
01-03 02:47:54.662 - p2p0: connectToSupplicant
01-03 02:47:55.663 - p2p0: connectToSupplicant
01-03 02:47:56.664 - p2p0: connectToSupplicant
01-03 02:47:57.666 - p2p0: connectToSupplicant
01-03 02:48:00.724 - wlan0: 5:IFNAME=wlan0 SET pno 0 -> false
01-03 02:48:02.680 - startHal stack:  - startHal - processMessage - processMsg - handleMessage - dispatchMessage - loop
01-03 02:48:03.226 - p2p0: connectToSupplicant
01-03 02:48:14.237 - p2p0: connectToSupplicant
01-03 02:48:15.238 - p2p0: connectToSupplicant
01-03 02:48:16.238 - p2p0: connectToSupplicant
01-03 02:48:17.239 - p2p0: connectToSupplicant
01-03 02:48:18.240 - p2p0: connectToSupplicant
01-03 02:48:23.278 - startHal stack:  - startHal - processMessage - processMsg - handleMessage - dispatchMessage - loop
01-03 02:48:23.745 - p2p0: connectToSupplicant
01-03 02:48:24.746 - p2p0: connectToSupplicant
01-03 02:48:25.748 - p2p0: connectToSupplicant
01-03 02:48:26.749 - p2p0: connectToSupplicant
01-03 02:48:27.751 - p2p0: connectToSupplicant
01-03 02:48:28.752 - p2p0: connectToSupplicant
01-03 02:48:33.769 - startHal stack:  - startHal - processMessage - processMsg - handleMessage - dispatchMessage - loop
01-03 02:48:34.223 - p2p0: connectToSupplicant
01-03 02:48:35.225 - p2p0: connectToSupplicant
01-03 02:48:36.227 - p2p0: connectToSupplicant
01-03 02:48:37.229 - p2p0: connectToSupplicant
01-03 02:48:38.230 - p2p0: connectToSupplicant
01-03 02:48:39.231 - p2p0: connectToSupplicant
01-03 02:49:38.235 - wlan0: 6:IFNAME=wlan0 SET pno 0 -> false
01-03 02:59:56.992 - wlan0: 8:IFNAME=wlan0 SET pno 0 -> false
WifiConfigStore - Log End ----

*** firmware logging disabled, no debug data ****
set config_wifi_enable_wifi_firmware_debugging to enable
In there, I see repeated attempts that the wifi service makes to start the supplicant and the driver. These are followed right away with disconnection events from the supplicant - that is to say - the supplicant never starts. And I can't be sure about the driver either. This seems to be confirmed by this line near the end, where we can see the false null mac that the service reports to the system, and the Supplicant state of "UNINITIALIZED".
Code:
mWifiInfo SSID: <unknown ssid>, BSSID: <none>, MAC: 02:00:00:00:00:00, Supplicant state: UNINITIALIZED, RSSI: -127, Link speed: -1Mbps, Frequency: -1MHz, Net ID: -1, Metered hint: false, score: 0
So, I ask - what does the supplicant (and/or wifi driver) need to start? Could it be having trouble reading from /persist to get the mac address?

I checked for errors in the persist partition, running this command while in recovery (where /persist was not mounted), and it came up clean:
Code:
# e2fsck /dev/block/mmcblk0p26

e2fsck 1.42.9 (28-Dec-2013)
/dev/block/mmcblk0p26: clean, 62/320 files, 1110/1280 blocks
So, what about permissions? Here is the structure of my /persist folder and its subfolders. Does anyone see anything amiss?
Code:
[email protected]:/ # ls -ld persist
drwxrwx--x system   system            2015-12-06 20:58 persist

[email protected]:/ # ls -la /persist
drwxr-xr-x 9001     9001              1969-12-31 19:00 batt_health
drwxr-xr-x 9004     bluetooth          1969-12-31 19:00 bt
drwxr-sr-x 9004     camera            1969-12-31 19:00 camera
drwx------ system   system            2014-11-16 07:29 data
drwxr-xr-x 9004     9004              2014-10-20 20:20 factory
drwx------ root     root              1969-12-31 19:00 lost+found
drwxrwx--- radio    radio             2015-05-19 18:04 mdm
-r-------- root     root            0 1969-12-31 19:00 pds_formatted_v12
drwxr-xr-x system   radio             2014-10-20 20:19 public
drwxrws--- 9007     9007              2014-11-16 07:29 security
drwxrwxr-x nobody   nobody            2014-10-20 20:19 sensors
drwxrws--- 9004     9009              1969-12-31 19:00 whisper
drwxrwxr-x wifi     system            2015-12-06 20:59 wifi
-rw------- wifi     system         13 1969-12-31 19:00 wlan_mac_serial.bin
drwxrwxr-x 9003     9003              1969-12-31 19:00 wmdrm

[email protected]:/ # ls -la /persist/wifi
-rwxrwxr-x wifi     system          6 2015-12-06 20:59 .macaddr

[email protected]:/ # ls -la /persist/bt
[email protected]:/ #
Could someone with a working Nexus 6 running 6.0.0 or 6.0.1 run the same commands and post the results? Obviously, do not post the contents of the files. I just want to see the file/folder permissions. The following four commands should cover it:
Code:
ls -ld persist
ls -la /persist
ls -la /persist/wifi
ls -la /persist/bt
Thanks in advance.
9th January 2016, 06:29 AM |#37  
Senior Member
Thanks Meter: 1,194
 
More
Quote:
Originally Posted by DefectiveRobot

[/CODE]Could someone with a working Nexus 6 running 6.0.0 or 6.0.1 run the same commands and post the results? Obviously, do not post the contents of the files. I just want to see the file/folder permissions. The following four commands should cover it:

Code:
ls -ld persist
ls -la /persist
ls -la /persist/wifi
ls -la /persist/bt
Thanks in advance.

Looks different
Attached Thumbnails
Click image for larger version

Name:	Screenshot_20160109-072738.jpg
Views:	1174
Size:	247.2 KB
ID:	3603885  
The Following User Says Thank You to Droidphilev For This Useful Post: [ View ] Gift Droidphilev Ad-Free
11th January 2016, 11:43 PM |#38  
DefectiveRobot's Avatar
Member
Thanks Meter: 6
 
More
Quote:
Originally Posted by Droidphilev

Looks different

I can't thank you enough for posting those permissions. The differences were minor, and all were related to me trying to fix it in the first place. I removed the extra permissions from wlan_mac_serial.bin, and the wifi folder, but could not change the owner and group to 9004. In this context, that UID doesn't exist. (I am able to chown 9004 while in recovery, however I can not mount the persist folder there to edit it) But, since both your bt and wifi folders were empty anyway, I said, "ef it" and just deleted the wifi folder entirely. While in recovery I deleted cache and dalvik, and rebooted.

So, the wifi is currently working, and if it stays that way for more than a few days, I am selling this sucker as is. I already have an unopened N6 being delivered to replace it.

Interestingly, this is the third time that wifi has re-appeared after trying various things. For all three of these times the phone had been left on, untouched, in airplane mode for more than 48 hours. The first time it disappeared a week after taking the OTA to 6.0.0. I tried many things to fix it, rooting it in the process, and ultimately frustrated, left it alone for a week, turned it on without the sim card, and there it was working again. The second time it disappeared was after unrooting using the "Full Unroot" option in SuperSU. After rebooting, wifi was gone. Many more failed attempts to restore wifi later, it sat in airplane mode for another day or two until I added "apscan=1" to the wpa_supplicant.conf file. On reboot, wifi was back! 20 minutes later, it went away without reason! Today, after tweaking the permissions in the /persist folder, I rebooted, took it out of airplane mode, and there it was again. Coincidence? Or is it only working after COMPLETELY cycling power to the wifi chip?

I am both grateful (for your help), and skeptical (that it will last).
12th January 2016, 06:06 AM |#39  
Senior Member
Thanks Meter: 1,194
 
More
Quote:
Originally Posted by DefectiveRobot

I can't thank you enough for posting those permissions. The differences were minor, and all were related to me trying to fix it in the first place. I removed the extra permissions from wlan_mac_serial.bin, and the wifi folder, but could not change the owner and group to 9004. In this context, that UID doesn't exist. (I am able to chown 9004 while in recovery, however I can not mount the persist folder there to edit it) But, since both your bt and wifi folders were empty anyway, I said, "ef it" and just deleted the wifi folder entirely. While in recovery I deleted cache and dalvik, and rebooted.

So, the wifi is currently working, and if it stays that way for more than a few days, I am selling this sucker as is. I already have an unopened N6 being delivered to replace it.

Interestingly, this is the third time that wifi has re-appeared after trying various things. For all three of these times the phone had been left on, untouched, in airplane mode for more than 48 hours. The first time it disappeared a week after taking the OTA to 6.0.0. I tried many things to fix it, rooting it in the process, and ultimately frustrated, left it alone for a week, turned it on without the sim card, and there it was working again. The second time it disappeared was after unrooting using the "Full Unroot" option in SuperSU. After rebooting, wifi was gone. Many more failed attempts to restore wifi later, it sat in airplane mode for another day or two until I added "apscan=1" to the wpa_supplicant.conf file. On reboot, wifi was back! 20 minutes later, it went away without reason! Today, after tweaking the permissions in the /persist folder, I rebooted, took it out of airplane mode, and there it was again. Coincidence? Or is it only working after COMPLETELY cycling power to the wifi chip?

I am both grateful (for your help), and skeptical (that it will last).

Well, np. Let me tell you a story of some problem i had a while ago. I use a Samsung tablet. When the first custom roms came i was very excited. A friend of mine made a CM12.1 rom for this device. I use a Logitech case with BT keyboard. I flashed CM, set everything up and everything worked fine untill i rebooted. The pair with the keyboard was gone and BT mac of the tablet was changed. After searching for days i had the idea to compare the /EFS partition (which holds IMEI, WIFI MAC, BT MAC ETC on a Samsung) with the tablet of my kid (same model, a month younger). I turned out that the rom changed not only permissions but also user/group of the file that holds the BT MAC. I don't know much about permissions, user and groups but i do know they are most important. I hope changing the permission like you did now fixed your problem.

(If the rom couldn't read the MAC from this file it "fantasized" a mac on booting. Sorry, english is not my native language so i don't know the correct word)
18th January 2016, 04:44 PM |#40  
DefectiveRobot's Avatar
Member
Thanks Meter: 6
 
More
Quote:
Originally Posted by Droidphilev

... the rom changed not only permissions but also user/group of the file that holds the BT MAC. [...] I hope changing the permission like you did now fixed your problem.

It's interesting, because even in your persist folder, the /persist/bt and /persist/wifi folders are empty, and the file permissions I changed only made it more restrictive, not less. I really can't say why it started working.

So, wifi has been working just fine since my last post. For a full week, I carried it with me, poked at it, turned wifi on and off (and back on again), connected to many different access points, signed into my google account, used every app in the stock image (including google apps for those thinking its related to google connectivity services) and browsed the newsstand for days without a hiccup. However, I kept it powered on the whole time. I allowed it to sleep, of course, and even drained the battery slowly down to 25%, and then charged it back to 100%. Nothing in the hardware prevented it from functioning perfectly.

What it can't do, it seems, is continue working after a reboot. I'd like to sell this thing, which means I've got to wipe it, which means I eventually would have had to reboot it. Which I did. Just now. And no... wifi did not come back.

Time to test a theory: I'll leave it on in airplane mode for 48 hours without changing anything else at all. I'll report back then...
21st January 2016, 05:58 PM |#41  
DefectiveRobot's Avatar
Member
Thanks Meter: 6
 
More
Quote:
Originally Posted by DefectiveRobot

Time to test a theory: I'll leave it on in airplane mode for 48 hours without changing anything else at all.

After 73 hours, left on, I turned off airplane mode, and no dice. Still not working.

meh.
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes