Device is getting reboot if WiFi is on

[prashantsinhpvips]

Facing reboot issue when WiFi is on with arpi-10 branch. Attaching two boots logcat logs for the reference both of the time it is rebooting at the same spot.

Note: Both files contain logs from boot to reboot.

First Boot: reboot_logcat.txt Second Boot: reboot_logcat_1.txt

[prashantsinhpvips]

@peyo-hd Is this issue known? with android-10.0.0_r39 it was working smooth.

[peyo-hd]

I could not find clue on the attached log. Maybe analyze more by yourself. Or you can compare with arpi-11 status.

[prashantsinhpvips]

Thank you @peyo-hd for the valuable suggestion I have started to build arpi-11, will compare status with it. Attaching the full logs with arpi-10 branch if it can help. dmesg.log logcat.txt

[KonstaT]

This looks like the same issue that's been reported on my LineageOS builds (https://github.com/lineage-rpi/android_kernel_brcm_rpi/issues/6) and it's probably been present in all builds after switching to 4.19 kernel and newer (Pi 3 & Pi 4 on Android Pie & Android 10). I still have no clue why this is only reproducible on some devices/circumstances because I've never come across this myself.

[prashantsinhpvips]

@KonstaT I have tried the same images with multiple RPI4 (4GB and 8GB RAM) both are crashing. Are there any chances that build/build-machine have some issues? This the link of images I have used, if you want to reproduce it to your end - link

[KonstaT]

I've never been able to reproduce the issue on any of my devices or builds. No, it's not about the build setup because the images I've released work fine for me but some small percentage of users have reported this issue using the very same images.

More likely something to do with your network environment. Wifi region, router settings, what other wifi devices are present (crash has something to do with p2p?), etc.

[prashantsinhpvips]

The device is rebooting even if I just turn on it. (Not saved any password, not connected to router)

[KonstaT]

Yeah, that's also what I've been told. Maybe radio environment would better describe what I meant i.e. all wifi device/networks that are visible to your device. But there should be some common factor why this only happens on certain circumstances.

[andersling]

Yeah, that's also what I've been told. Maybe radio environment would better describe what I meant i.e. all wifi device/networks that are visible to your device. But there should be some common factor why this only happens on certain circumstances.

Hi, MR.KonstaT, thanks for your amazing work of lineage-rpi ! Do you have plan when to update it the android 11? If you can publish all the source code (especially the HOWTO build instructions),That is too much great!!!

and btw, The wifi problem maybe is the drivers's problem. My device works very nice on this room~

thanks KonstaT!

@KonstaT

[KonstaT]

@andersling Sorry, but android-rpi issue tracker is certainly not the right place to discuss my plans on lineage-rpi.

Yes, it's most definitely a driver issue. Works great on what ROM? This issue is about it not working on android-rpi which seems to be exactly the same issue as reported on my LineageOS builds.

[andersling]

@KonstaT Thanks for your reply! I means that this andorid-rpi 11 room and the android-rpi 10( maybe this android 10 room's wifi driver was fixed by @peyo-hd and now boots up ok with wifi ON ,on my raspberry PI4B 2G/4G/8G recently). AS for this andorid-rpi 11 room , It runs almost pefectly on my raspberry PI4B 2G/4G/8G ,with WIFI and bluetooth ON at boot! And the bluetooth auto connect to the Bluetooth Device(such as bluetooth audio speaker)that It connected the last time . I hope this information may be referenced by you to solve lineage-rpi's wifi problem. I Like your room so much, IT'S REALLY NICE !
Have a good day, MR. @KonstaT:-)

[KonstaT]

@andersling Are you sure that you can reproduce this with any build anymore? You also said it's fixed with latest kernel from lineage-rpi (https://github.com/lineage-rpi/android_kernel_brcm_rpi/issues/5#issuecomment-686466563). I highly doubt that because people have still reported it with the very same kernel.

There hasn't been any recent changes to arpi-10 branch. This issue report is about latest arpi-10 branch having this issue (while android-10.0.0_r39 maybe didn't).

@peyo-hd Any idea about this issue?

Instead of force pushing kernel branches would it be possible to keep the old source in a separate branch? It's now impossible to say e.g. what kernel source was used when manifest was at android-10.0.0_r39. This would greatly help bisecting the source code in situations like this if an issue is reproducible in one branch or an update has caused a regression. I have also enabled LOCALVERSION_AUTO on my kernels so anyone can easily see where the git HEAD was when the kernel was built.

[peyo-hd]

Hi Konsta,

Kernel git in android-rpi is just for holding a few patches upon latest rpi & aosp kernel source. Your suggestion is reasonable for storing history of release. But I will keep it minimal in android-rpi.

[andersling]

@KonstaT Hi,MR.KonstaT, This morning I try to rebuild the android-rpi 10 with andorid 10 R41, it's very confusing that It can not boot up by default config ! It keeping rebooting after the rainbow screen! and I try the Omini Room from https://github.com/maxwen/android_device_brcm_rpi4 It compile it from source, And it boot upnormally and can connect to WIFI . It's image is arm64 bit ,so is this android-rpi 11 by MR. peyo-hd. Is this the key reason for the 32 bit wifi failed? @KonstaT @peyo-hd

BTW, I will try to reproduce the log for you .

Thanks  MR.Konsta and MR. peyo-hd !

[KonstaT]

@andersling No, nothing to do with architecture.

[NumberOneGit]

The common aspect of most of these errors is the presence of an ANQP / Hotspot 2.0 network in local results. This was noted by KonstaT in a LineageOS issue thread on the same topic. I'm just updating this thread with the same info in case developers may have any possible workaround. I've tried multiple versions of the RPi4 and CM4 with WiFi and had the same result. I've tried in two different locations in NYC where these types of networks are prevalent and get an immediate reboot with Android-rpi and LineageOS and an incredibly unstable OmniRom which occasionally allows me to click a few menus before also rebooting. All work fine over Ethernet with WiFi disabled. Is there a way to disable network scan but retain access to our own WiFi network using a wpa_supplicant.conf? The scan itself seems to be the point at which this bug occurs.

[matthuo333]

In the network detection link in the initialization process, can I add a manual method of adding Ethernet IP?

[kaushal98]

We have a private fork of the arpi-11 branch and seeing this issue. We don't know the exact cause, but we also had a hotspot AP and as soon as the device rebooted it would crash within 20-30 seconds and sometimes it would keep on rebooting for 20-30 times in a row. As a temporary workaround we ended up re-flashing the SD card with new image, and not touch the Wifi settings at all and only connect using ethernet.

If it helps someone debug, this is what the log looked like when ethernet was connected and we tried to enable wifi from settings and crash/reboot.

05-19 02:23:50.735   387   406 I DropBoxManagerService: add tag=system_app_strictmode isTagEnabled=true flags=0x2
05-19 02:23:51.952   387   960 E TaskPersister: File error accessing recents directory (directory doesn't exist?).
05-19 02:23:56.149   166   166 I Binder:166_2: type=1400 audit(0.0:96): avc: denied { call } for scontext=u:r:carwatchdogd:s0 tcontext=u:r:hal_vehicle_default:s0 tclass=binder permissive=1
05-19 02:23:58.983   387  1878 I WifiService: setWifiEnabled package=com.android.car.settings uid=1001000 enable=true
05-19 02:23:58.987   387   464 D WifiActiveModeWarden: Starting ClientModeManager
05-19 02:23:59.000   387   464 D WifiController: DisabledState.exit()
05-19 02:23:59.000   387   464 D WifiController: EnabledState.enter()
05-19 02:23:59.001   387   464 D WifiClientModeManager: entering IdleState
05-19 02:23:51.952   387   960 I chatty  : uid=1000(system) LazyTaskWriterT identical 1 line
05-19 02:23:51.954   387   960 E TaskPersister: File error accessing recents directory (directory doesn't exist?).
05-19 02:23:59.003   238   238 I android.hardware.wifi@1.0-service: Wifi HAL started
05-19 02:23:59.004   387   464 I WifiVendorHal: Vendor Hal started successfully
05-19 02:23:59.019   238   238 E WifiHAL : wifi_pre_initialize
05-19 02:23:59.019   238   238 E WifiHAL : --- HAL version: Android-10-FRC2-SDK_29 59.0 (r854927) 2019-12-06 23:33:52 +0530 (Fri, 06 Dec 2019) ---
05-19 02:23:59.019   238   238 I WifiHAL : Creating socket
05-19 02:23:59.023   238   238 I WifiHAL : Initialized Wifi HAL Successfully; vendor cmd = 103
05-19 02:23:59.023   238   238 I WifiHAL : found interface wlan0
05-19 02:23:59.023   238   238 E WifiHAL : Calling preInit
05-19 02:23:59.023   238   238 E WifiHAL : Hal preInit
05-19 02:23:59.024   238   238 E WifiHAL : Failed to register set Hal preInit; result = -95
05-19 02:23:59.024   238   238 E WifiHAL : wifi_hal_preInit failed
05-19 02:23:59.067   387   404 I EthernetTracker: interfaceLinkStateChanged, iface: wlan0, up: false
01-01 00:02:24.036     0     0 E brcmfmac: brcmf_cfg80211_set_power_mgmt: power save enabled
05-19 02:23:59.071   238   238 E WifiHAL : wifi_initialize
05-19 02:23:59.071   238   238 I WifiHAL : found interface wlan0
05-19 02:23:59.071   238   238 E WifiHAL : Calling Hal_init
05-19 02:23:59.071   238   238 E WifiHAL : Start Set Hal
05-19 02:23:59.072   238   238 E WifiHAL : Failed to register set hal start response; result = -95
05-19 02:23:59.072   238   238 E WifiHAL : wifi_start_hal failed
05-19 02:23:59.073   238   238 I android.hardware.wifi@1.0-service: Adding interface handle for wlan0
05-19 02:23:59.073   238   238 W android.hardware.wifi@1.0-service: No active wlan interfaces in use! Using default
05-19 02:23:59.074   238   238 E android.hardware.wifi@1.0-service: Failed to register radio mode change callback
05-19 02:23:59.074   238   238 W android.hardware.wifi@1.0-service: No active wlan interfaces in use! Using default
05-19 02:23:59.075   238   238 E WifiHAL : Failed to register debug response; result = -95
05-19 02:23:59.075   238   238 E android.hardware.wifi@1.0-service: Failed to get driver version: UNKNOWN ERROR
05-19 02:23:59.075   238   238 I android.hardware.wifi@1.0-service: Configured chip in mode 0
05-19 02:23:59.075   238   238 W android.hardware.wifi@1.0-service: No active wlan interfaces in use! Using default
05-19 02:23:59.080   387   464 D HalDevMgr: updateRttController: no one is interested in RTT controllers
05-19 02:23:59.082   238   238 I android.hardware.wifi@1.0-service: Adding interface handle for wlan0
05-19 02:23:59.083   238   238 E android.hardware.wifi@1.0-service: Failed to set DFS flag; DFS channels may be unavailable.
05-19 02:23:59.106   387   464 D WifiNl80211Manager: Setting up interface for client mode
05-19 02:23:59.118   279   279 I wificond: create scanner for interface with index: 8
05-19 02:23:59.118   279   279 I wificond: subscribe scan result for interface with index: 8
05-19 02:23:59.123   387   464 I WifiNative: Interface state changed on Iface:{Name=wlan0,Id=0,Type=STA_SCAN}, isUp=true
05-19 02:23:59.124   387   464 I WifiNative: Successfully setup Iface:{Name=wlan0,Id=0,Type=STA_SCAN}
05-19 02:23:59.124   387   464 E SupplicantStaIfaceHal: checkHalVersionByInterfaceName: called but mServiceManager is null
05-19 02:23:59.124   387   464 E SupplicantStaIfaceHal: checkHalVersionByInterfaceName: called but mServiceManager is null
05-19 02:23:59.124   387   464 E SupplicantStaIfaceHal: Method getKeyMgmtCapabilities is not supported in existing HAL
05-19 02:23:59.131   387   464 E WifiVendorHal: getSupportedFeatureSet(l.1263) failed {.code = ERROR_UNKNOWN, .description = unknown error}
05-19 02:23:59.133   387   464 E WifiVendorHal: getSupportedFeatureSet(l.1276) failed {.code = ERROR_UNKNOWN, .description = unknown error}
05-19 02:23:59.140   387   464 E SupplicantStaIfaceHal: checkHalVersionByInterfaceName: called but mServiceManager is null
05-19 02:23:59.140   387   464 I SupplicantStaIfaceHal: Method getWpaDriverFeatureSet is not supported in existing HAL
05-19 02:23:59.140   387   464 D WifiClientModeManager: entering StartedState
05-19 02:23:59.141   387   464 D WifiClientModeManager: entering ScanOnlyModeState
05-19 02:23:59.146   387   464 D WifiScanRequestProxy: Sending scan available broadcast: true
05-19 02:23:59.148   387   468 I WifiScanningService: Received a request to enable scanning, UID = 1000
05-19 02:23:59.149   387   464 I WifiScanRequestProxy: Scanning is enabled
05-19 02:23:59.149   387   464 I WifiScanRequestProxy: Scanning for hidden networks is disabled
05-19 02:23:59.151   387   464 D WakeupController: start()
05-19 02:23:59.151   387   468 E WifiVendorHal: getBgScanCapabilities(l.674) failed {.code = ERROR_UNKNOWN, .description = unknown error}
05-19 02:23:59.152   387   464 I WakeupController: Ignore wakeup start since there are no good networks.
05-19 02:23:59.158   387   464 I android_os_HwBinder: HwBinder: Starting thread pool for getting: android.hidl.manager@1.0::IServiceManager/default
05-19 02:23:59.163   387   464 I SupplicantStaIfaceHal: Starting supplicant using HIDL
05-19 02:23:59.165   175   175 I hwservicemanager: Since android.hardware.wifi.supplicant@1.0::ISupplicant/default is not registered, trying to start it as a lazy HAL.
05-19 02:23:59.167   387   464 D SupplicantStaIfaceHal: Successfully triggered start of supplicant using HIDL
05-19 02:23:59.170   387   468 I WifiScanningService: Created a new impl for wlan0
05-19 02:23:59.172   387   468 I WifiScanningService: wifi driver loaded with scan capabilities: max buckets=16
01-01 00:02:24.145     0     0 I init    : starting service 'wpa_supplicant'...
01-01 00:02:24.151     0     0 I init    : Created socket '/dev/socket/wpa_wlan0', mode 660, user 1010, group 1010
01-01 00:02:24.167     0     0 I init    : Control message: Processed ctl.interface_start for 'android.hardware.wifi.supplicant@1.0::ISupplicant/default' from pid: 175 (/system/bin/hwservicemanager)
01-01 00:02:24.401     0     0 I capability: warning: `wpa_supplicant' uses 32-bit capabilities (legacy support in use)
05-19 02:23:59.465  2331  2331 I wpa_supplicant: Processing hidl events on FD 3
05-19 02:23:59.469  2331  2331 I HidlServiceManagement: Registered android.hardware.wifi.supplicant@1.3::ISupplicant/default
05-19 02:23:59.470  2331  2331 I wpa_supplicant: Successfully initialized wpa_supplicant
05-19 02:23:59.491  2331  2331 I wpa_supplicant: rfkill: Cannot open RFKILL control device
05-19 02:23:59.493   387   404 I EthernetTracker: interfaceLinkStateChanged, iface: wlan0, up: false
05-19 02:23:59.564   387   423 I android_os_HwBinder: HwBinder: Starting thread pool for getting: android.hardware.wifi.supplicant@1.0::ISupplicant/default
05-19 02:23:59.567   387   423 I SupplicantStaIfaceHal: Completed initialization of ISupplicant.
05-19 02:23:59.568   387   464 E SupplicantStaIfaceHal: Can't call setupIface, ISupplicantStaIface is null
05-19 02:23:59.573   387   464 I android_os_HwBinder: HwBinder: Starting thread pool for getting: android.hardware.wifi.supplicant@1.0::ISupplicant/default
05-19 02:23:59.611   387   464 D SupplicantStaIfaceHal: Newer HAL is found, skip V1_2 remaining init flow.
05-19 02:23:59.611   387   464 D SupplicantStaIfaceHal: Newer HAL is found, skip V1_1 remaining init flow.
05-19 02:23:59.611   387   464 D SupplicantStaIfaceHal: Newer HAL is found, skip V1_0 remaining init flow.
05-19 02:23:59.617   387   464 E WifiVendorHal: getSupportedFeatureSet(l.1263) failed {.code = ERROR_UNKNOWN, .description = unknown error}
05-19 02:23:59.618   387   464 E WifiVendorHal: getSupportedFeatureSet(l.1276) failed {.code = ERROR_UNKNOWN, .description = unknown error}
05-19 02:23:59.630   387   464 I WifiNative: Successfully switched to connectivity mode on iface=Iface:{Name=wlan0,Id=0,Type=STA_CONNECTIVITY}
05-19 02:23:59.631   387   464 D WakeupController: stop()
05-19 02:23:59.631   387   464 E WifiScanner: listener cannot be found
05-19 02:23:59.632   387   464 D WifiClientModeManager: entering ConnectModeState
05-19 02:23:59.639   387   464 D WifiScanRequestProxy: Sending scan available broadcast: true
05-19 02:23:59.639   387   468 I WifiScanningService: Received a request to enable scanning, UID = 1000
05-19 02:23:59.639   387   468 I WifiScanningService: scanner impls already exists
05-19 02:23:59.640   387   468 E WifiScanningService: wifi driver loaded received while already loaded
05-19 02:23:59.641   387   464 I WifiScanRequestProxy: Scanning is enabled
05-19 02:23:59.641   387   464 I WifiScanRequestProxy: Scanning for hidden networks is enabled
05-19 02:23:59.643   387   464 D WifiClientModeImpl: entering ConnectModeState: ifaceName = wlan0
05-19 02:23:59.645   387   464 D WifiClientModeImpl: setupClientMode() ifacename = wlan0
05-19 02:23:59.645   387   401 I WifiService: startScan uid=1001000
05-19 02:23:59.668   387   464 D WifiCountryCode: Reading country code from telephony
05-19 02:23:59.672   387   464 D WifiCountryCode: Set telephony country code to: 
05-19 02:23:59.672   387   464 D WifiCountryCode: updateCountryCode to null
05-19 02:23:59.673   238   238 D WifiHAL : Start get packet fate command
05-19 02:23:59.673   238   238 D WifiHAL : createRequest Monitor packet fate request
05-19 02:23:59.674   238   238 E WifiHAL : Failed to register get pkt fate response; result = -95
05-19 02:23:59.675   387   464 E WifiVendorHal: startPktFateMonitoring(l.1821) failed {.code = ERROR_UNKNOWN, .description = unknown error}
05-19 02:23:59.675   387   464 W WifiDiags: Failed to start packet fate monitoring
05-19 02:23:59.676   238   238 E WifiHAL : Failed to register debug response; result = -95
05-19 02:23:59.676   238   238 E android.hardware.wifi@1.0-service: Failed to get driver version: UNKNOWN ERROR
05-19 02:23:59.678   387   464 E WifiVendorHal: requestChipDebugInfo(l.1636) failed {.code = ERROR_UNKNOWN, .description = unknown error}
05-19 02:23:59.678   387   464 I WifiVendorHal: Driver: null Firmware: null
05-19 02:23:59.679   238   238 E WifiHAL : Failed to register debug response; result = -95
05-19 02:23:59.680   387   464 E WifiVendorHal: requestChipDebugInfo(l.1636) failed {.code = ERROR_UNKNOWN, .description = unknown error}
05-19 02:23:59.680   387   464 I WifiVendorHal: Driver: null Firmware: null
05-19 02:23:59.681   575   575 W View    : requestLayout() improperly called by com.android.keyguard.AlphaOptimizedLinearLayout{960f630 V.E...... ......ID 0,0-30,28 #7f0a05b9 app:id/wifi_group} during layout: running second layout pass
05-19 02:23:59.682   238   238 E WifiHAL : Failed to register debug response; result = -95
05-19 02:23:59.684   387   464 E WifiVendorHal: getRingBufferStatus(l.1713) failed {.code = ERROR_UNKNOWN, .description = unknown error}
05-19 02:23:59.684   387   464 W WifiDiags: no ring buffers found
05-19 02:23:59.684   387   464 D WifiDiags: startLogging() iface list is {wlan0} after adding wlan0
05-19 02:23:59.688  2331  2331 E wpa_supplicant: wpa_driver_nl80211_driver_cmd: failed to issue private command: BTCOEXSCAN-STOP
05-19 02:23:59.689   387   464 E SupplicantStaIfaceHal: ISupplicantStaIface.setBtCoexistenceScanModeEnabled failed: {.code = FAILURE_UNKNOWN, .debugMessage = }
05-19 02:23:59.689  2331  2331 E wpa_supplicant: wpa_driver_nl80211_driver_cmd: failed to issue private command: RXFILTER-STOP
05-19 02:23:59.690   387   464 E SupplicantStaIfaceHal: ISupplicantStaIface.stopRxFilter failed: {.code = FAILURE_UNKNOWN, .debugMessage = }
05-19 02:23:59.690  2331  2331 E wpa_supplicant: wpa_driver_nl80211_driver_cmd: failed to issue private command: RXFILTER-STOP
05-19 02:23:59.691   387   464 E SupplicantStaIfaceHal: ISupplicantStaIface.stopRxFilter failed: {.code = FAILURE_UNKNOWN, .debugMessage = }
05-19 02:23:59.692  2331  2331 E wpa_supplicant: wpa_driver_nl80211_driver_cmd: failed to issue private command: SETSUSPENDMODE 0
05-19 02:23:59.693   387   464 E SupplicantStaIfaceHal: ISupplicantStaIface.setSuspendModeEnabled failed: {.code = FAILURE_UNKNOWN, .debugMessage = }
05-19 02:23:59.696   387   464 D WakeupController: reset()
05-19 02:23:59.699   387   464 I WifiClientModeImpl: disconnectedstate enter
05-19 02:23:59.721   198   198 I Binder:198_2: type=1400 audit(0.0:99): avc: denied { read } for name="wakeup0" dev="sysfs" ino=14714 scontext=u:r:system_suspend:s0 tcontext=u:object_r:sysfs:s0 tclass=dir permissive=1
05-19 02:24:02.199   387   404 I EthernetTracker: interfaceLinkStateChanged, iface: wlan0, up: false
05-19 02:24:02.201   387  1878 D WifiNl80211Manager: Scan result ready event
05-19 02:24:02.202   387  1878 D WifiNative: Scan result ready event
05-19 02:24:02.446  2331  2331 I wpa_supplicant: wlan0: GAS-QUERY-START addr=1e:bd:ad:15:a4:c2 dialog_token=14 freq=2412
05-19 02:24:02.447   387   464 D HS20    : ANQP initiated on 1e:bd:ad:15:a4:c2
05-19 02:24:02.447   387   464 D PasspointManager: ANQP entry not found for: 1e:bd:ad:15:a4:c2:<T wifi zone_secure>
01-01 00:02:27.424     0     0 F         : Unable to handle kernel access to user memory outside uaccess routines at virtual address 0000000000001218
01-01 00:02:27.435     0     0 F         : Mem abort info:
01-01 00:02:27.439     0     0 F         : ESR = 0x96000005
01-01 00:02:27.442     0     0 F         : EC = 0x25: DABT (current EL), IL = 32 bits
01-01 00:02:27.447     0     0 F         : SET = 0, FnV = 0
01-01 00:02:27.451     0     0 F         : EA = 0, S1PTW = 0
01-01 00:02:27.454     0     0 F         : Data abort info:
01-01 00:02:27.457     0     0 F         : ISV = 0, ISS = 0x00000005
01-01 00:02:27.461     0     0 F         : CM = 0, WnR = 0
01-01 00:02:27.464     0     0 F user pgtable: 4k pages, 39-bit VAs, pgdp=000000014937c000
01-01 00:02:27.470     0     0 F         : [0000000000001218] pgd=0000000000000000, p4d=0000000000000000, pud=0000000000000000

[greenozon]

Could anyonehint me how to collect required logs? I've just hit this very strange and annoying issue on my Android phone ... it never happened before, but right now it is reproducible 100% of the time, must be some fix/update from Lineage update servers...?