Device reboots when wifi is enabled about android_kernel_brcm_rpi HOT 59 CLOSED

Looks promising so far! Just flashed the image (20211216) and seems to be holding. I tried earlier with (19.0.20211125), but that had also reboot issues.

Kept it on Wifi scanning for about 5 minutes so far and no reboots.

from android_kernel_brcm_rpi.

Would this only solve it for the RPI 4 and not for the 3 like I have?

I have retired my Pi 3 from development so I won't be providing any builds with this fix.

from android_kernel_brcm_rpi.

Thanks for the log. This seems like the issue discussed before (http://disq.us/p/2ax3vmu). I still have no idea why this only happens on some devices.

You can disable wifi by adding dtoverlay=disable-wifi to /boot/config.txt.

from android_kernel_brcm_rpi.

KernelDBG_Msg_DisableWIFI_Room20200813ByKonstaT.txt
Thanks for you reply, and just now I try to disabled wifi follow your tips, and IT CAN BOOT UP NOW! That is really exciting!!! Thanks ,sir!
Hope in the new version that you can fixed the wifi isue, big thanks!

from android_kernel_brcm_rpi.

and by the way, can i enable the ethernet interface so that i can use it to connect to the internet.. Thanks!

from android_kernel_brcm_rpi.

anther information report to you: when the room boot up successfully, i try to turn the wifi on in the setting ui, after a few seconds, the on went back to off automatic, and the USB debug message show no new messages! and after that ,the system is still runing normall ,NO Reboots!
hope this can be referred by you, thanks!

from android_kernel_brcm_rpi.

I can't reproduce this issue myself which makes testing possible fixes really difficult.

Ethernet is automatically enabled when you plug in a cable. There's no settings options for it but you'll see an icon on the status bar when you're connected using ethernet.

from android_kernel_brcm_rpi.

Hello,

Firstly, like many others, I'd like to offer my sincere thanks for your work. It is really fantastic. I am having the same rebooting loop issue, and I did see that you've not been able to reproduce it, but I am hoping by giving some more symptoms / data points, it might be useful.

I have a Pi 4 with 8GB RAM (first one). I initially experienced the exact symptoms described above (would get just past the LineageOS splash screen then reboot). I followed the directions, and this is where it gets a little interesting. I changed the config.txt file to shut the Wi-Fi off. It booted, but only got to the screen "Enter Name of Wi-Fi network" - I couldn't get past that. I tried this with both the standard LineageOS and AndroidTV builds with the same result.

Then, I reflashed the card with both builds, but did not change the config.txt file , I plugged the Ethernet cable in. It worked. Once plugged in, I tried to join a Wi-Fi network - it reboots. If I turn off Wi-Fi and stay on Ethernet, it works fine.

Ultimately, I'd like to use Wi-Fi, and I am sure that will happen. Until then, I sincerely hope this provides a little more data. I can also add I have tried two different micro SD cards - same result. I have also installed Raspberry Pi OS as a test and it works fine on all fronts.

Thanks again for your time and work.

from android_kernel_brcm_rpi.

Hello,

Firstly, like many others, I'd like to offer my sincere thanks for your work. It is really fantastic. I am having the same rebooting loop issue, and I did see that you've not been able to reproduce it, but I am hoping by giving some more symptoms / data points, it might be useful.

I have a Pi 4 with 8GB RAM (first one). I initially experienced the exact symptoms described above (would get just past the LineageOS splash screen then reboot). I followed the directions, and this is where it gets a little interesting. I changed the config.txt file to shut the Wi-Fi off. It booted, but only got to the screen "Enter Name of Wi-Fi network" - I couldn't get past that. I tried this with both the standard LineageOS and AndroidTV builds with the same result.

Then, I reflashed the card with both builds, but did not change the config.txt file , I plugged the Ethernet cable in. It worked. Once plugged in, I tried to join a Wi-Fi network - it reboots. If I turn off Wi-Fi and stay on Ethernet, it works fine.

Ultimately, I'd like to use Wi-Fi, and I am sure that will happen. Until then, I sincerely hope this provides a little more data. I can also add I have tried two different micro SD cards - same result. I have also installed Raspberry Pi OS as a test and it works fine on all fronts.

Thanks again for your time and work.

Hi, The main issue is the wifi-driver not works! There is no solution yet, what we have to is waiting MR.Kansta release some fix.
and by the way ,you can use the Android-RPI 11 (64bit), On all my 2G/4G/8G raspberryPI4 boards, it works well including wifi and bluetooth. https://github.com/android-rpi/device_arpi_rpi4

Have a good day!

from android_kernel_brcm_rpi.

Hi,sir! When I use you 20200813 rom for pi4,it keep rebooting and rebooting, i catch the debug messages from USB ,please take a look at it,thanks!

It seems that the wlan supplant has something wrong,would you build a room without the wifi enabled by default? Then I cam debug it and report the result to you,thanks!

Hello, How did you catch this debug on USB. I am having the same issue with Konstakang's buid. I want to catch the log whether what is going wrong. I do not know how to get the log. Please help.

from android_kernel_brcm_rpi.

Thanks for the log. This seems like the issue discussed before (http://disq.us/p/2ax3vmu). I still have no idea why this only happens on some devices.

You can disable wifi by adding dtoverlay=disable-wifi to /boot/config.txt.

I disabled the wifi, It successfully boot up but it now stuck on Select your Wifi Network. It is not allowing me to skip the wifi connection screen. I have inserted the LAN cable, still it is not connecting to internet, I mean still it is not allowing me to bypass the wifi connection screen

from android_kernel_brcm_rpi.

Thanks for the log. This seems like the issue discussed before (http://disq.us/p/2ax3vmu). I still have no idea why this only happens on some devices.
You can disable wifi by adding dtoverlay=disable-wifi to /boot/config.txt.

I disabled the wifi, It successfully boot up but it now stuck on Select your Wifi Network. It is not allowing me to skip the wifi connection screen. I have inserted the LAN cable, still it is not connecting to internet, I mean still it is not allowing me to bypass the wifi connection screen

Are you sure you disabled WIFI ? As for me ,the LAN will auto connect by DHCP .

from android_kernel_brcm_rpi.

Hi,sir! When I use you 20200813 rom for pi4,it keep rebooting and rebooting, i catch the debug messages from USB ,please take a look at it,thanks!

It seems that the wlan supplant has something wrong,would you build a room without the wifi enabled by default? Then I cam debug it and report the result to you,thanks!

Hello, How did you catch this debug on USB. I am having the same issue with Konstakang's buid. I want to catch the log whether what is going wrong. I do not know how to get the log. Please help.

Hi, you can search youtube or google by "Debug kernel Message in RaspberryPI" , you will find a lot useful instruction to do it.
First of all ,you have to prepare a USB To TTL adapter .maybe it cast 3-5 dollars in amazon.
Have a nice day!

and btw, you can try android-rpi 11 64bit room, it is all works with wifi and bluetooth.

from android_kernel_brcm_rpi.

As I suspected elsewhere wifi network surroundings seem to have an effect on this (http://disq.us/p/2cj20pe). It would be interesting to know which device nearby you need to turn on/off to be able to reproduce this.

Also could someone run 'iogcat' and post the output as well? I've only seen the kernel log so far.

from android_kernel_brcm_rpi.

As I suspected elsewhere wifi network surroundings seem to have an effect on this (http://disq.us/p/2cj20pe). It would be interesting to know which device nearby you need to turn on/off to be able to reproduce this.

Also could someone run 'iogcat' and post the output as well? I've only seen the kernel log so far.

Hi,MR. KonstaT! Do you mean that the Device Driver decode the WIFI Beacon packets,some ap's beacons are no so good ,such as 802.11ac or 802.11ax ,or the vendor Information Elements( IEs) ..etc, which cause the driver decode error?
I am familar with the WIFI standard such as 802.11n, ac ,ax. how can i do something for you? capture the beacon frames with wireshark format or elsething?
Have a nice day,sir!

from android_kernel_brcm_rpi.

As I suspected elsewhere wifi network surroundings seem to have an effect on this (http://disq.us/p/2cj20pe). It would be interesting to know which device nearby you need to turn on/off to be able to reproduce this.
Also could someone run 'iogcat' and post the output as well? I've only seen the kernel log so far.

Hi,MR. KonstaT! Do you mean that the Device Driver decode the WIFI Beacon packets,some ap's beacons are no so good ,such as 802.11ac or 802.11ax ,or the vendor Information Elements( IEs) ..etc, which cause the driver decode error?
I am familar with the WIFI standard such as 802.11n, ac ,ax. how can i do something for you? capture the beacon frames with wireshark format or elsething?
Have a nice day,sir!

No, I'm not interested about packet captures. If you could run 'logcat' using serial console adapter that might bring some new information.

From practical point of view I'd more interested to know what kind of device I'd need to bring to my network surroundings so I could reproduce this issue myself. Can you turn off some surrounding devices? Does this only happen after turning some device on? E.g. wireless CarlinKit adapter seems to be one this can be reproduced with (https://www.raspberrypi.org/forums/viewtopic.php?f=73&t=281187&sid=06c476372818de3df141ee7dbf7c6238&start=150#p1749890) but I'm not going to spend ~100€ on something I have no other use for.

from android_kernel_brcm_rpi.

I have tried it by switching off different bandwidth wifi and i found that with 5ghz bandwidth it get in rebooting loop with other wifi it work fine.

from android_kernel_brcm_rpi.

@govindmaheshwari2
What makes you think this is somehow related to 5GHz? Did you switch off some bandwidths from your router or something else?

5GHz networks are not normally visible on my device for some reason when my wifi region is set to FI. If I set wifi region to US (iw reg set US) I can connect to my 5GHz AP fine. No reboots.

from android_kernel_brcm_rpi.

Hi Mr. Konsta,

Your build is working great! Thanks A Lot.

I have experienced with wifi issue like the others, it could be not enough power on rpi4, so it reboot.
I did booting LOS 17.1 with 5 volt and 1 amp power supply, but when I turn on the wifi , it reboot.
So I tried with greater power supply 5 volt and 2.4 amp and no problem, run perfectly.
Actually recommended from the official rpi4 is 5 v and 3 Amp.
so I think that the wifi device consume much power and can cause the rpi4 processors under voltage or power that make it reboot.
I have experienced this under power symtoms since rpi1 and other mobile device. I hope this can help.

Happy LineAgeOS!!!

from android_kernel_brcm_rpi.

Please test the latest LineageOS 17.1 builds on the Pi 4 and report if there's any change. I patched the kernel around where this is crashing.

from android_kernel_brcm_rpi.

No change still the same issue. Rebooting again again

from android_kernel_brcm_rpi.

@govindmaheshwari Which build did you use?

from android_kernel_brcm_rpi.

The one you release yesterday for android tv lineage-17.1-20201119

from android_kernel_brcm_rpi.

Ok, thanks for the report.

I guess I still need to find some way to reproduce this myself. And I'm also yet to even see a logcat of this on LineageOS.

from android_kernel_brcm_rpi.

I can share my screen and device so that you can see and reproduce these issue like teamviewer or any other required software. So that you can make it correct and you don't have to buy expensive things

from android_kernel_brcm_rpi.

@govindmaheshwari2 No, that doesn't work in any way for something like this.

from android_kernel_brcm_rpi.

@KonstaT @govindmaheshwari2 I also have the same problem, when I use the raspberry with wifi it goes into a reboot loop, even with a very powerful powersupply, the issue happens with 2.4 and 5 ghz wifi.
I will get a Serial Adapter and run more tests on this
BTW it is a great work, Thank you!!!!!

from android_kernel_brcm_rpi.

@KonstaT your new build lineage-18.1-20210104-UNOFFICIAL-KonstaKANG-rpi4 is working great. there is no issue of wifi or any other thing i can find right now. Can you please provide TV version of lineage 18.1. GAPPS is not an issue there are lots of 3rd party store can be used. Thank you for building a great and smooth working android 11 rom.

from android_kernel_brcm_rpi.

@govindmaheshwari2 Thanks for the report. There's no plans for Android TV 11 releases in any near future (it does not offer anything you don't already have with current Android TV builds). You can install a different launcher if you want to have a more TV friendly UI.

Difference between LineageOS 17.1 and 18.1 kernels is just one configuration option so it looks like the root of this issue was not in the kernel after all. Like I suspected this is fixed somewhere else in Android 11 most likely wpa_supplicant. I would still like to have this fixed for older Android versions of course.

from android_kernel_brcm_rpi.

There's also a report that this issue is not resolved with LineageOS 18.

It seems that this is somehow related to Hotspot 2.0/802.11u/Access Network Query Protocol (ANQP) networks being present in the network environment.

And finally a logcat:

2021-01-24 17:39:39.259 513-513/? D/wpa_supplicant: nl80211: Drv Event 34 (NL80211_CMD_NEW_SCAN_RESULTS) received for wlan0
2021-01-24 17:39:39.259 513-513/? D/wpa_supplicant: wlan0: nl80211: New scan results available
2021-01-24 17:39:39.259 513-513/? D/wpa_supplicant: nl80211: Scan probed for SSID ''
2021-01-24 17:39:39.259 513-513/? D/wpa_supplicant: nl80211: Scan included frequencies: 2412 2417 2422 2427 2432 2437 2442 2447 2452 2457 2462 2467 2472 5180 5200 5220 5240 5260 5280 5300 5320 5500 5520 5540 5560 5580 5600 5620 5640 5660 5680 5700
2021-01-24 17:39:39.259 513-513/? D/wpa_supplicant: wlan0: Event SCAN_RESULTS (3) received
2021-01-24 17:39:39.259 513-513/? D/wpa_supplicant: nl80211: Received scan results (6 BSSes)
2021-01-24 17:39:39.259 384-765/system_process D/WifiNl80211Manager: Scan result ready event
2021-01-24 17:39:39.260 513-513/? D/wpa_supplicant: wlan0: BSS: Start scan result update 1
2021-01-24 17:39:39.260 513-513/? D/wpa_supplicant: wlan0: BSS: Add new id 0 BSSID a0:39:ee:8a:b0:16 SSID 'LinkSys' freq 2437
2021-01-24 17:39:39.260 384-765/system_process D/WifiNative: Scan result ready event
2021-01-24 17:39:39.260 513-513/? D/wpa_supplicant: wlan0: BSS: Add new id 1 BSSID a2:39:ee:8a:b0:17 SSID 'LinkGuest' freq 2437
2021-01-24 17:39:39.260 513-513/? D/wpa_supplicant: wlan0: BSS: Add new id 2 BSSID e0:ce:c3:c7:ee:15 SSID 'AKADO-0040' freq 2462
2021-01-24 17:39:39.260 513-513/? D/wpa_supplicant: wlan0: BSS: Add new id 3 BSSID ec:41:18:f5:f3:d9 SSID 'MIEPL REKTOR' freq 2417
2021-01-24 17:39:39.260 384-401/system_process I/EthernetTracker: interfaceLinkStateChanged, iface: wlan0, up: false
2021-01-24 17:39:39.260 513-513/? D/wpa_supplicant: wlan0: BSS: Add new id 4 BSSID e1:8c:2a:99:b5:92 SSID 'Hotspot 2.0' freq 2442 HESSID 2c:c5:d3:11:50:90
2021-01-24 17:39:39.260 513-513/? D/wpa_supplicant: wlan0: BSS: Add new id 5 BSSID a0:8e:78:01:c0:1e SSID 'AKADO-C018' freq 2412
2021-01-24 17:39:39.260 513-513/? D/wpa_supplicant: BSS: last_scan_res_used=6/32
2021-01-24 17:39:39.260 513-513/? D/wpa_supplicant: wlan0: New scan results available (own=0 ext=1)
2021-01-24 17:39:39.260 513-513/? D/wpa_supplicant: wlan0: Do not use results from externally requested scan operation for network selection
2021-01-24 17:39:39.261 513-513/? D/wpa_supplicant: RTM_NEWLINK: ifi_index=8 ifname=wlan0 wext ifi_family=0 ifi_flags=0x1003 ([UP])
2021-01-24 17:39:39.263 384-467/system_process D/WifiNl80211Manager: get 6 scan results from wificond
2021-01-24 17:39:39.277 384-467/system_process D/WifiNative: get 6 scan results from wificond
2021-01-24 17:39:39.278 384-467/system_process D/WifiAsyncChannel.WifiScanningService: sendMessage sendMessage message=159764
2021-01-24 17:39:39.283 384-467/system_process I/chatty: uid=1000(system) WifiScanningSer identical 22 lines
2021-01-24 17:39:39.283 384-467/system_process D/WifiAsyncChannel.WifiScanningService: sendMessage sendMessage message=159764
2021-01-24 17:39:39.284 384-467/system_process D/WifiAsyncChannel.WifiScanningService: sendMessage sendMessage message=159749
2021-01-24 17:39:39.285 384-467/system_process D/WifiAsyncChannel.WifiScanningService: sendMessage sendMessage message=159767
2021-01-24 17:39:39.286 384-467/system_process D/WifiAsyncChannel.WifiScanningService: sendMessage sendMessage message=159749
2021-01-24 17:39:39.286 384-467/system_process D/WifiAsyncChannel.WifiScanningService: sendMessage sendMessage message=159767
2021-01-24 17:39:39.287 384-467/system_process D/WifiAsyncChannel.WifiScanningService: sendMessage sendMessage message=159749
2021-01-24 17:39:39.287 384-464/system_process D/WifiScanRequestProxy: Scan results received
2021-01-24 17:39:39.287 384-464/system_process D/WifiScanRequestProxy: Received 6 scan results
2021-01-24 17:39:39.287 384-467/system_process D/WifiAsyncChannel.WifiScanningService: sendMessage sendMessage message=159749
2021-01-24 17:39:39.288 384-505/system_process D/WifiHealthMonitor:  2G scanResult count: 6, Above2g scanResult count: 0
2021-01-24 17:39:39.291 384-1401/system_process I/WifiService: getScanResults uid=1000
2021-01-24 17:39:39.295 384-1401/system_process I/WifiService: getWifiEnabledState uid=1000
2021-01-24 17:39:39.295 384-1401/system_process I/WifiService: getScanResults uid=1000
2021-01-24 17:39:39.298 384-1401/system_process I/WifiService: getSupportedFeatures uid=1000
2021-01-24 17:39:39.298 384-1401/system_process D/WifiAsyncChannel.WifiService: sendMessageSynchronously sendMessageSynchronously.send message=131133
2021-01-24 17:39:39.298 384-464/system_process D/WifiClientModeImpl:  DefaultState screen=on uid=1000 0 0
2021-01-24 17:39:39.299 384-1401/system_process D/WifiAsyncChannel.WifiService: sendMessageSynchronously sendMessageSynchronously.recv message=131133 sendingUid=1000
2021-01-24 17:39:39.308 384-1401/system_process I/WifiService: getSupportedFeatures uid=1000
2021-01-24 17:39:39.308 384-1401/system_process D/WifiAsyncChannel.WifiService: sendMessageSynchronously sendMessageSynchronously.send message=131133
2021-01-24 17:39:39.308 384-464/system_process D/WifiClientModeImpl:  DefaultState screen=on uid=1000 0 0
2021-01-24 17:39:39.308 384-1401/system_process D/WifiAsyncChannel.WifiService: sendMessageSynchronously sendMessageSynchronously.recv message=131133 sendingUid=1000
2021-01-24 17:39:39.313 384-1401/system_process I/WifiService: getSupportedFeatures uid=1000
2021-01-24 17:39:39.313 384-1401/system_process D/WifiAsyncChannel.WifiService: sendMessageSynchronously sendMessageSynchronously.send message=131133
2021-01-24 17:39:39.314 384-464/system_process D/WifiClientModeImpl:  DefaultState screen=on uid=1000 0 0
2021-01-24 17:39:39.314 384-1401/system_process D/WifiAsyncChannel.WifiService: sendMessageSynchronously sendMessageSynchronously.recv message=131133 sendingUid=1000
2021-01-24 17:39:39.328 384-1401/system_process I/WifiService: getSupportedFeatures uid=1000
2021-01-24 17:39:39.328 384-1401/system_process D/WifiAsyncChannel.WifiService: sendMessageSynchronously sendMessageSynchronously.send message=131133
2021-01-24 17:39:39.329 384-464/system_process D/WifiClientModeImpl:  DefaultState screen=on uid=1000 0 0
2021-01-24 17:39:39.329 384-1401/system_process D/WifiAsyncChannel.WifiService: sendMessageSynchronously sendMessageSynchronously.recv message=131133 sendingUid=1000
2021-01-24 17:39:39.336 384-1401/system_process I/WifiService: getSupportedFeatures uid=1000
2021-01-24 17:39:39.337 384-1401/system_process D/WifiAsyncChannel.WifiService: sendMessageSynchronously sendMessageSynchronously.send message=131133
2021-01-24 17:39:39.337 384-464/system_process D/WifiClientModeImpl:  DefaultState screen=on uid=1000 0 0
2021-01-24 17:39:39.338 384-1401/system_process D/WifiAsyncChannel.WifiService: sendMessageSynchronously sendMessageSynchronously.recv message=131133 sendingUid=1000
2021-01-24 17:39:39.344 384-1401/system_process I/WifiService: getSupportedFeatures uid=1000
2021-01-24 17:39:39.344 384-1401/system_process D/WifiAsyncChannel.WifiService: sendMessageSynchronously sendMessageSynchronously.send message=131133
2021-01-24 17:39:39.344 384-464/system_process D/WifiClientModeImpl:  DefaultState screen=on uid=1000 0 0
2021-01-24 17:39:39.345 384-1401/system_process D/WifiAsyncChannel.WifiService: sendMessageSynchronously sendMessageSynchronously.recv message=131133 sendingUid=1000
2021-01-24 17:39:39.354 384-1401/system_process I/WifiService: getWifiConfigsForMatchedNetworkSuggestions uid=1000
2021-01-24 17:39:39.365 384-1401/system_process I/WifiService: getMatchingPasspointConfigurations uid=1000
2021-01-24 17:39:39.367 513-513/? D/wpa_supplicant: wlan0: ANQP: Query Request to e1:8c:2a:99:b5:92 for 5 id(s)
2021-01-24 17:39:39.368 513-513/? D/wpa_supplicant: GAS: Use own MAC address as the transmitter address (no driver rand capa
2021-01-24 17:39:39.368 513-513/? I/wpa_supplicant: wlan0: GAS-QUERY-START addr=e1:8c:2a:99:b5:92 dialog_token=229 freq=2442
2021-01-24 17:39:39.368 513-513/? D/wpa_supplicant: wlan0: Add radio work 'gas-query'@0xb2680a90
2021-01-24 17:39:39.368 513-513/? D/wpa_supplicant: wlan0: First radio work item in the queue - schedule start immediately
2021-01-24 17:39:39.368 513-513/? D/wpa_supplicant: wlan0: ANQP: Query started with dialog token 229
2021-01-24 17:39:39.368 513-513/? D/wpa_supplicant: wlan0: Starting radio work 'gas-query'@0xb2680a90 after 0.000292 second wait
2021-01-24 17:39:39.368 513-513/? D/wpa_supplicant: GAS: Send action frame to e1:8c:2a:99:b5:92 len=37 freq=2442 prot=0 using src addr ac:a2:52:f4:a5:e3
2021-01-24 17:39:39.368 513-513/? D/wpa_supplicant: Off-channel: Send action frame: freq=2442 dst=e1:8c:2a:99:b5:92 src=ac:a2:52:f4:a5:e3 bssid=e1:8c:2a:99:b5:92 len=37
2021-01-24 17:39:39.368 513-513/? D/wpa_supplicant: Off-channel: Stored pending action frame (dst=e1:8c:2a:99:b5:92 pending_action_tx=0xb26c2b30)
2021-01-24 17:39:39.368 513-513/? D/wpa_supplicant: nl80211: Send Action frame (ifindex=8, freq=2442 MHz wait=1000 ms no_cck=0 offchanok=1)
2021-01-24 17:39:39.369 384-464/system_process D/SupplicantStaIfaceHal: ISupplicantStaIface.initiateAnqpQuery succeeded
2021-01-24 17:39:39.369 384-464/system_process D/HS20: ANQP initiated on e1:8c:2a:99:b5:92
2021-01-24 17:39:39.370 384-464/system_process D/PasspointManager: ANQP entry not found for: e1:8c:2a:99:b5:92:<Hotspot 2.0>
2021-01-24 17:39:39.374 384-1401/system_process I/WifiService: getMatchingOsuProviders uid=1000
2021-01-24 17:39:39.375 384-1401/system_process I/WifiService: getMatchingPasspointConfigsForOsuProviders uid=1000
2021-01-24 17:39:39.378 384-1401/system_process I/WifiService: getWifiEnabledState uid=1000
reboot

from android_kernel_brcm_rpi.

Konsta Hi.
I've just noticed a very confusing thing. I changed my box from standard one (https://ae01.alicdn.com/kf/H7b384e742d274837b315fce47bb389134.jpg_q50.jpg) to passive one (https://http2.mlstatic.com/D_NQ_NP_830683-MLM31962423570_082019-O.webp) and it stopped rebooting. I keep on looking afer its behavior... 24hrs of stable work so far.

from android_kernel_brcm_rpi.

@Rpi4Alex No, unlikely that case has anything to do with this. This issue is to do with specific type of wifi network being in your surroundings. In your case it was the BSSID e1:8c:2a:99:b5:92 SSID 'Hotspot 2.0' network which is most likely now just turned off.

from android_kernel_brcm_rpi.

Konsta, Hi.
Thanks once again for your quick feedbacks. It is per se worth a lot.
No,... You are right . The new case doesn't resolve the issue. It still reboots. Herewith i attach the latest log but it seems to me that it doesn'r show anything since the device was connected via wifi. There are 4 full zip reports in a raw ( https://yadi.sk/d/2_vxccbc6M9W_w ).
I will try to connect it via usb (waiting for the device) later on.

from android_kernel_brcm_rpi.

BSSID e1:8c:2a:99:b5:92 SSID 'Hotspot 2.0' is there on fullLogBeforeReboot4.txt at least. Is that your or some neighbors network? Try switching it off if you can.

from android_kernel_brcm_rpi.

I dont even see this network in the list of availabele wifi networks.
Is there a way to block the specified network (or number of networks) from detection (exclude it from the availability list) and stick to one predefined by user?

from android_kernel_brcm_rpi.

@Rpi4Alex No, I'm not aware of any way you could that. This issue needs some proper way to resolve it anyway.

Lets keep the discussion on this issue.

from android_kernel_brcm_rpi.

Concur, having this issue as well at a complex with lots of wifi signals.

from android_kernel_brcm_rpi.

And I thought I was the only one in the boat - I even bought a new RP4 with more memory just to isolate it's not a faulty RP4. I tried 2 different RP4s (2gb and 8gb) model and 3 different SD cards and all have the same reboot problem.

Wifi disabled - all looks good.

Here's a logcat right before it rebooted, hopefully it helps?

03-01 21:03:32.135   702  1803 W TileUtils: Found com.android.settings.Settings$DataUsageSummaryActivity for intent Intent { act=com.android.settings.action.SETTINGS pkg=com.android.settings } missing metadata com.android.settings.category
03-01 21:03:32.150   386   893 I WifiService: startScan uid=1000
03-01 21:03:32.162   702   702 W ConnectivityManager.CallbackHandler: callback not found for CALLBACK_AVAILABLE message
03-01 21:03:32.168   386   902 D PackageManager: Instant App installer not found with android.intent.action.INSTALL_INSTANT_APP_PACKAGE
03-01 21:03:32.169   386   902 D PackageManager: Clear ephemeral installer activity
03-01 21:03:32.176   702  1803 D SettingsActivity: Enabled state changed for some tiles, reloading all categories {com.android.settings/com.android.settings.Settings$PowerUsageSummaryActivity},
03-01 21:03:32.181   702  1667 W TileUtils: Found com.android.settings.Settings$DataUsageSummaryActivity for intent Intent { act=com.android.settings.action.SETTINGS pkg=com.android.settings } missing metadata com.android.settings.category
03-01 21:03:32.596   386   496 D ConnectivityService: releasing NetworkRequest [ TRACK_DEFAULT id=18, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 1000] ] (release request)
03-01 21:03:32.600   562   562 V KeyguardUpdateMonitor: onSubscriptionInfoChanged()
03-01 21:03:33.161   386   413 E system_server: No package ID 7f found for ID 0x7f080249.
03-01 21:03:33.161   386   413 E system_server: No package ID 7f found for ID 0x7f121205.
03-01 21:03:33.161   386   413 E system_server: No package ID 7f found for ID 0x7f080248.
03-01 21:03:33.161   386   413 E system_server: No package ID 7f found for ID 0x7f120517.
03-01 21:03:33.162   386   413 E system_server: No package ID 7f found for ID 0x7f080247.
03-01 21:03:33.162   386   413 E system_server: No package ID 7f found for ID 0x7f120b34.
03-01 21:03:33.168   386   482 I InputReader: Reconfiguring input devices.  changes=0x00000010
03-01 21:03:33.172   702  1667 W TileUtils: Found com.android.settings.Settings$DataUsageSummaryActivity for intent Intent { act=com.android.settings.action.SETTINGS pkg=com.android.settings } missing metadata com.android.settings.category
03-01 21:03:33.176   386   386 I Telecom : DefaultDialerCache: Refreshing default dialer for user 0: now null: DDC.oR@AA8
03-01 21:03:33.178   386   413 W Searchables: No global search activity found
03-01 21:03:33.180   386   413 W VoiceInteractionManagerService: no available voice interaction services found for user 0
03-01 21:03:34.174   386   893 D WificondControl: Scan result ready event
03-01 21:03:34.179   386   495 D WificondScannerImpl: Filtering out 2 scan results.
03-01 21:03:34.180   386   405 I EthernetTracker: interfaceLinkStateChanged, iface: wlan0, up: true
03-01 21:03:34.181   202   202 I netd    : interfaceGetCfg("wlan0") <0.79ms>
03-01 21:03:34.187   636   636 I wpa_supplicant: wlan0: GAS-QUERY-START addr=ee:22:80:12:75:fd dialog_token=0 freq=5240
03-01 21:03:34.187   386   493 D HS20    : ANQP initiated on ee:22:80:12:75:fd
03-01 21:03:34.188   386   493 D PasspointManager: ANQP entry not found for: ee:22:80:12:75:fd:<AlticeWiFi>
03-01 21:03:34.212   702   702 D WifiSettings: onAccessPointsChanged (WifiTracker) callback initiated

from android_kernel_brcm_rpi.

I did some more additional digging to see what this Wifi actually is, and it seems to be a public hotspot from a Cable Company in the area.

Is it maybe related to that?

from android_kernel_brcm_rpi.

@msugirin Yes, as commented before this seems to be related to Hotspot 2.0/802.11u/Access Network Query Protocol (ANQP) networks being present in the network environment. BSSID ee:22:80:12:75:fd SSID 'AlticeWiFi' in your case.

Which LineageOS version is this BTW? There's been some mixed reports about this being fixed in LineageOS 18.

from android_kernel_brcm_rpi.

This is on the January release of 17.1 (lineage-17.1-20210122). I tried the same on the 18.1 (lineage-18.1-20210214) release and ran into the same issue during the setup screen.

I can retry it on 18.1 and also check the logcats - will post later

from android_kernel_brcm_rpi.

Same issue on latest 18.1 build:

03-02 08:34:10.929   391  1760 D WifiNl80211Manager: Scan result ready event
03-02 08:34:10.929   391  1760 D WifiNative: Scan result ready event
03-02 08:34:10.957   391   471 D PasspointManager: ANQP entry not found for: ee:22:80:12:75:fd:<AlticeWiFi>
03-02 08:34:10.962   520   520 I wpa_supplicant: wlan0: GAS-QUERY-START addr=ee:22:80:12:75:fd dialog_token=165 freq=5240
03-02 08:34:10.963   391   471 D HS20    : ANQP initiated on ee:22:80:12:75:fd
03-02 08:34:10.963   391   471 D PasspointManager: ANQP entry not found for: ee:22:80:12:75:fd:<AlticeWiFi>
03-02 08:34:11.014   391   471 D ANQPRequestManager: Not allowed to send ANQP request to ee:22:80:12:75:fd for another 9 seconds
03-02 08:34:11.015   391   471 D PasspointManager: ANQP entry not found for: ee:22:80:12:75:fd:<AlticeWiFi>
12-31 13:14:05.477     0     0 F         : 8<--- cut here ---
12-31 13:14:05.480     0     0 F         : Unable to handle kernel NULL pointer dereference at virtual address 00000000
03-02 08:34:11.029   391   442 I system_server: oneway function results will be dropped but finished with status OK and parcel size 4

from android_kernel_brcm_rpi.

Same issue here. It looks like RPi and Android won't be an option for a lot of us in densely populated areas until this is resolved. I have the same issue wherever I try to boot up in NYC.

from android_kernel_brcm_rpi.

Is there any conclusion on this question?

from android_kernel_brcm_rpi.

How to set to skip Ethernet detection? Because I am in China, I need a VPN, but there is no place to set the gateway address during the detection. After entering the system, I need to manually set the network

from android_kernel_brcm_rpi.

is it fixed yet? i am using raspi 3b+ with 5v 3amp power supply and it only works when i disable wifi with the config.txt file .

from android_kernel_brcm_rpi.

This issue should be now resolved in one way with the latest LineageOS 19 build (https://konstakang.com/devices/rpi4/LineageOS19/). Please test and confirm that this is the case.

I'll also include similar fix to LineageOS 18 builds if/when there's another release.

from android_kernel_brcm_rpi.

Ran it all day, used different apps, downloaded/uninstalled apps. Not a single reboot :) so happy!

Now I can finally re-start my car-droid project :) thanks a bunch for all the hard work!!

from android_kernel_brcm_rpi.

This issue should be now resolved in one way with the latest LineageOS 19 build (https://konstakang.com/devices/rpi4/LineageOS19/). Please test and confirm that this is the case.

I'll also include similar fix to LineageOS 18 builds if/when there's another release.

Hi KonstaT,

Thanks for this amazing build. Would this only solve it for the RPI 4 and not for the 3 like I have?

Thanks in advance!

from android_kernel_brcm_rpi.

I get that! Thanks for getting back so quickly.

from android_kernel_brcm_rpi.

This issue should be now resolved with the latest LineageOS 18 builds as well. Please test and confirm that this is the case.

from android_kernel_brcm_rpi.

This has been reported to no longer be an issue with all the builds that are still maintained so closing this.

from android_kernel_brcm_rpi.

I have also tried installing lineage (android 11) and (android 12) I have the same problem that the raspberry pi 4(8gb ram) is rebooting again and again

from android_kernel_brcm_rpi.

I have also tried installing lineage (android 11) and (android 12) I have the same problem that the raspberry pi 4(8gb ram) is rebooting again and again

Most likely it's not this issue if you're using the latest builds (as this was already fixed).

Please attach appropriate logs (logcat, dmesg) to your issue report because it's impossible to say anything otherwise.

General advice is to use proper sdcard (at least class 10) and power source (3A in case of Pi 4).

from android_kernel_brcm_rpi.

I am using 4amp power supply and class 10 sd card the problem is that i have installed android 11 on raspberry pi 4 when the os stats after 5 minutes it starts rebooting and after 5 minutes again it again starts rebooting and it goes on i then tried installing android 12 but same thing happens with it

from android_kernel_brcm_rpi.

in the above discussion you told to diable wifi but dont know from where to diable it

from android_kernel_brcm_rpi.

@AkshitSingh28

It is not this issue so why would disabling wifi do any good? (For how to do this see my first reply in this discussion.)

Please get appropriate log and open a new issue as this is off topic for this discussion.

There's no point in making blind guesses but the next one is that you've overclocked your CPU too high/haven't taken care of proper cooling.

from android_kernel_brcm_rpi.

i have upgraded my power supply from 4amp to 5amp and now it is running very smooth thanks for android 12 build

from android_kernel_brcm_rpi.

Cheap USB power cable could introduce too much voltage drop, which may cause issues as well.

from android_kernel_brcm_rpi.