WirelessAndroidAutoDongle
WirelessAndroidAutoDongle copied to clipboard
nisargjhaveri
2018 Jeep JLU Sahara
I was setting up Pi Zero 2 W and ran into a constant reboot issues. Bluetooth visible Connect phone to Bluetooth Popup message "Unable to connect to <Bluetooth Device Address>", this happens due to PI Zero reboots
Q. Any settings to make the logs persistent? It is not easy to retrieve logs due to constant reboot
If you have reboots than I think it may be some kind of power issue. The logs can be easily extracted but only when the Pi is not rebooting. I am personally also using Pi Zero 2 W.
My other car is 2023 Kia Car running 0.5.0 with Pixel 7Pro. I tried setting up another phone Samsung S22 Ultra which failed and during next drive it gets in constant reboot cycle.
I will try with secondary power.
If you have reboots than I think it may be some kind of power issue. The logs can be easily extracted but only when the Pi is not rebooting. I am personally also using Pi Zero 2 W.
I tested with secondary power with a brand new image on sdcard but same reboot loop.
Hmm.... this still seems for me like a power/hardware problem... maybe as the last resort try to connect some small HDMI display to the HDMI port to visually see what is going on...
Here are 3 reboots. First reboot (Reboot-1) is different. Brand new image on sdcard.
HW: Raspberyy PiZero 2W (Tried two different hardware) Version 0.50 Vehicle: 2018 Jeep JLU Wrangler Sahara Unlimited
Please tell me one thing, @sharmay. I read this issue again and you tell us:
I tried setting up another phone Samsung S22 Ultra which failed and during next drive it gets in constant reboot cycle.
By reboot cycle I understand that your raspberry pi reboots, meaning rebooting - starting again like with power-cycle. But maybe it is about restarting android auto on your phone? not a raspberry pi? Are we thinking about same "reboot"? :)
Regarding your screen: yes two are very similar - it is just showing a properly booted raspberry, while one of them seems like catched earlier in the boot process - when everything doesn't start yet. Does it stopped there? Do you have "Welcome to Buildroot" message and more "OK" of service starting?
Please tell me one thing, @sharmay. I read this issue again and you tell us:
I tried setting up another phone Samsung S22 Ultra which failed and during next drive it gets in constant reboot cycle.
Above was 2023 Kia Carnival.
By reboot cycle I understand that your raspberry pi reboots, meaning rebooting - starting again like with power-cycle. But maybe it is about restarting android auto on your phone? not a raspberry pi? Are we thinking about same "reboot"? :)
PI Zero 2W reboots, On PI I see the green power LED goes off, monitor turns blank. I recorded a video, where PI rebooted 3 times.
Regarding your screen: yes two are very similar - it is just showing a properly booted raspberry, while one of them seems like catched earlier in the boot process - when everything doesn't start yet. Does it stopped there? Do you have "Welcome to Buildroot" message and more "OK" of service starting?
I connected HDMI monitor, setup phone to record video, connect PI to Jeep and start engine. PI starts booting and get to the status shown in 1st image and PI power LED goes off, PI starts booting again and get to the status shown in 2nd image and PI power LED goes off, PI starts booting again and get to the status shown in 2nd image and PI power LED goes off. At this point I turn off engine and stopped video recording.
I connected HDMI monitor, setup phone to record video, connect PI to Jeep and start engine. PI starts booting and get to the status shown in 1st image and PI power LED goes off, PI starts booting again and get to the status shown in 2nd image and PI power LED goes off, PI starts booting again and get to the status shown in 2nd image and PI power LED goes off. At this point I turn off engine and stopped video recording.
OK, everything's clear... it's a hardware issue... check your power, maybe you can power it from external source using split usb cable...?
I was able to setup logs to write to /persist/log/ using these steps:
- mount sdcard
- cd rootfs/var/
- sudo ln -s ../persist/log log
- cd ../..
- sudo vi rootfs/etc/init.d/S00persist
- add mkdir -p /persist/log in "start)" section
messages.txt line 269 is where I believe PI rebooted.
OK, everything's clear... it's a hardware issue... check your power, maybe you can power it from external source using split usb cable...?
Split cable or add an another cable to "power only micro usb port"?
OK... your logs is not telling us anything new. It is only confirming that you have a hardware issue. It is not normal that raspberry is restarting. And there may be multiple reasons for this: weak power from USB port, overheating, SD card problems, etc...
Split cable or add an another cable to "power only micro usb port"?
This kind of thing for example:
I mean the cable for which you split data and power. And you can get the power from cigarette 12V charger and only data to the headunit.
Do you have problems only when connected to the car? What if you connect it via charger but eg in your home... is it working reliable, not rebooting?
I will order this cable, mean while:
I powered it using either of micro usb when connected to a powerbank, no crash.
I powered it using the right side micro usb and connected to a Jeep, no crash but as soon as I also connect the left side micro usb to Jeep, crash starts.
I powered it using the right side micro usb connected to a powerbank, no crash but as soon as I connect the left micro usb to Jeep, crash starts.
Q. Since PI has 2 micro USB Power and Data, can't I use both? Rigt side to power and left side for data?
Hmmm... it makes sense, and in this case probably you don't need this cable :) The cable was mentioned in regards connecting Pi5 where it is unable to grab power the other way...
I heard about one case though when someone broke their USB port in HU when "playing" with this USB and power things. But it was probably using USB hub, right, @Ioniq3 ?
Unfortunately, Pi still crashed when I connected both power (power only cable) and data usb ports.
Hmmm... it makes sense, and in this case probably you don't need this cable :) The cable was mentioned in regards connecting Pi5 where it is unable to grab power the other way...
I heard about one case though when someone broke their USB port in HU when "playing" with this USB and power things. But it was probably using USB hub, right, @Ioniq3 ?
Raspberry pi 0w, 2w and 3a doesn't need to power by power only microusb, all these board consume less than 500mA of 5V and can be power only by the data+power usb connected to the car.
With hubs, and if you want to power it you have to be carefull, the best is to isolate +5V line from car to the hub.
I have a 2020 Pacifica with Uconnect 4 exhibiting the same symptoms. The head unit displayed "Device not supported" at which point the pi promptly reboots which as the OP pointed out makes grabbing logs difficult. After getting the reboot loop I tried it in my 2022 Tacoma and managed to get a wireless android auto session going (Huzzah!).
- ✅ Hardwired android auto connection with USB A to USB C cable works for Pacifica as well as Tacoma
- ✅ Wireless android auto works for tacoma
- ❌ Wireless android auto dongle shows device not supported when plugged into Pacifica and reboots the dongle as soon as that message appears
I have also tried switching the connection mode to 2 which prevents the reboot doom loop but the phone never finds an android auto connection.
I don't have an external monitor at the moment to capture logging output. Will see if the above mentioned log persist works for me. At least it works in the tacoma so that the pi zero wasn't a complete bust of a purchase.
Great project!
I'm guessing Uconnect 4 does something odd with the bluetooth or usb handshake. My main motivation for trying this project was that if wired android auto connection ever gets disrupted (checking a notification on phone causing cable to come loose momentarily) there's about a 1 in 3 chance that the head unit will display that "device not supported" message if you try to replug the phone in basically disabling android auto for the rest of the journey (sometimes turning car off for 30 seconds works to fix this... other times no such luck)
Here are the logs I grabbed from when trying connection mode 2 ( no reboot loop, but no successful launch of wireless android auto)
# cat /var/log/
dbus/ dnsmasq.leases hostapd messages
# cat /var/log/messages
Jan 1 00:00:03 buildroot syslog.info syslogd started: BusyBox v1.36.1
Jan 1 00:00:03 buildroot user.info console: Starting syslogd: OK
Jan 1 00:00:03 buildroot kern.notice kernel: klogd started: BusyBox v1.36.1 (2025-03-09 08:49:34 UTC)
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.000000] Booting Linux on physical CPU 0x0
Jan 1 00:00:03 buildroot kern.notice kernel: [ 0.000000] Linux version 6.1.61-v7 (runner@fv-az1922-927) (arm-buildroot-linux-gnueabihf-gcc.br_real (Buildroot -g7a59c3a4) 12.3.0, GNU ld (GNU Binutils) 2.40) #1 SMP Sun Mar 9 09:21:32 UTC 2025
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.000000] CPU: ARMv7 Processor [410fd034] revision 4 (ARMv7), cr=10c5383d
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.000000] CPU: div instructions available: patching division code
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.000000] OF: fdt: Machine model: Raspberry Pi Zero 2 W Rev 1.0
Jan 1 00:00:03 buildroot kern.notice kernel: [ 0.000000] random: crng init done
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.000000] Memory policy: Data cache writealloc
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.000000] Reserved memory: created CMA memory pool at 0x15800000, size 64 MiB
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.000000] OF: reserved mem: initialized node linux,cma, compatible id shared-dma-pool
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.000000] Zone ranges:
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.000000] DMA [mem 0x0000000000000000-0x0000000019bfffff]
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.000000] Normal empty
Jan 1 00:00:03 buildroot user.info console: Starting klogd: OK
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.000000] Movable zone start for each node
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.000000] Early memory node ranges
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.000000] node 0: [mem 0x0000000000000000-0x0000000019bfffff]
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.000000] Initmem setup node 0 [mem 0x0000000000000000-0x0000000019bfffff]
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.000000] percpu: Embedded 12 pages/cpu s18004 r8192 d22956 u49152
Jan 1 00:00:03 buildroot kern.debug kernel: [ 0.000000] pcpu-alloc: s18004 r8192 d22956 u49152 alloc=12*4096
Jan 1 00:00:03 buildroot kern.debug kernel: [ 0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 104545
Jan 1 00:00:03 buildroot kern.notice kernel: [ 0.000000] Kernel command line: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_headphones=0 bcm2708_fb.fbwidth=720 bcm2708_fb.fbheight=480 bcm2708_fb.fbswap=1 smsc95xx.macaddr=B8:27:EB:34:FF:24 vc_mem.mem_base=0x1ec0000
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes, linear)
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes, linear)
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.000000] mem auto-init: stack:all(zero), heap alloc:off, heap free:off
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.000000] Memory: 337224K/421888K available (9216K kernel code, 718K rwdata, 2316K rodata, 1024K init, 520K bss, 19128K reserved, 65536K cma-reserved)
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.000000] rcu: Hierarchical RCU implementation.
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.000000] Tracing variant of Tasks RCU enabled.
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 10 jiffies.
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.000000] rcu: srcu_init: Setting srcu_struct sizes based on contention.
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.000000] arch_timer: cp15 timer(s) running at 19.20MHz (phys).
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x46d987e47, max_idle_ns: 440795202767 ns
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.000001] sched_clock: 56 bits at 19MHz, resolution 52ns, wraps every 4398046511078ns
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.000019] Switching to timer-based delay loop, resolution 52ns
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.000350] Console: colour dummy device 80x30
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.000862] printk: console [tty1] enabled
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.000914] Calibrating delay loop (skipped), value calculated using timer frequency.. 38.40 BogoMIPS (lpj=192000)
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.000955] CPU: Testing write buffer coherency: ok
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.001013] pid_max: default: 32768 minimum: 301
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.001139] LSM: Security Framework initializing
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.001262] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes, linear)
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.001300] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes, linear)
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.002333] cgroup: Disabling memory control group subsystem
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.002853] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.003620] cblist_init_generic: Setting adjustable number of callback queues.
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.003651] cblist_init_generic: Setting shift to 2 and lim to 1.
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.003786] Setting up static identity map for 0x100000 - 0x10003c
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.003919] rcu: Hierarchical SRCU implementation.
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.003941] rcu: Max phase no-delay instances is 1000.
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.004574] smp: Bringing up secondary CPUs ...
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.005369] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.006171] CPU2: thread -1, cpu 2, socket 0, mpidr 80000002
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.006900] CPU3: thread -1, cpu 3, socket 0, mpidr 80000003
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.006988] smp: Brought up 1 node, 4 CPUs
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.007061] SMP: Total of 4 processors activated (153.60 BogoMIPS).
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.007086] CPU: All CPU(s) started in HYP mode.
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.007103] CPU: Virtualization extensions available.
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.007716] devtmpfs: initialized
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.020024] VFP support v0.3: implementor 41 architecture 3 part 40 variant 3 rev 4
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.020244] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.020294] futex hash table entries: 1024 (order: 4, 65536 bytes, linear)
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.022896] pinctrl core: initialized pinctrl subsystem
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.023884] NET: Registered PF_NETLINK/PF_ROUTE protocol family
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.026148] DMA: preallocated 1024 KiB pool for atomic coherent allocations
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.030703] audit: initializing netlink subsys (disabled)
Jan 1 00:00:03 buildroot kern.notice kernel: [ 0.030947] audit: type=2000 audit(0.030:1): state=initialized audit_enabled=0 res=1
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.031446] thermal_sys: Registered thermal governor 'step_wise'
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.031717] hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers.
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.031766] hw-breakpoint: maximum watchpoint size is 8 bytes.
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.031980] Serial: AMBA PL011 UART driver
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.037492] bcm2835-mbox 3f00b880.mailbox: mailbox enabled
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.050014] raspberrypi-firmware soc:firmware: Attached to firmware from 2023-10-17T15:42:39, variant start
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.060029] raspberrypi-firmware soc:firmware: Firmware hash is 30f0c5e4d076da3ab4f341d88e7d505760b93ad7
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.098381] kprobes: kprobe jump-optimization is enabled. All kprobes are optimized if possible.
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.100182] bcm2835-dma 3f007000.dma: DMA legacy API manager, dmachans=0x1
Jan 1 00:00:03 buildroot kern.notice kernel: [ 0.101668] SCSI subsystem initialized
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.101872] usbcore: registered new interface driver usbfs
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.101939] usbcore: registered new interface driver hub
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.101998] usbcore: registered new device driver usb
Jan 1 00:00:03 buildroot kern.warn kernel: [ 0.102187] usb_phy_generic phy: supply vcc not found, using dummy regulator
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.102516] pps_core: LinuxPPS API ver. 1 registered
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.102539] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <[email protected]>
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.102584] PTP clock support registered
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.103870] clocksource: Switched to clocksource arch_sys_counter
Jan 1 00:00:03 buildroot kern.notice kernel: [ 0.104158] VFS: Disk quotas dquot_6.6.0
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.104230] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Jan 1 00:00:03 buildroot kern.notice kernel: [ 0.104382] FS-Cache: Loaded
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.104608] CacheFiles: Loaded
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.113042] NET: Registered PF_INET protocol family
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.113269] IP idents hash table entries: 8192 (order: 4, 65536 bytes, linear)
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.115145] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 4096 bytes, linear)
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.115203] Table-perturb hash table entries: 65536 (order: 6, 262144 bytes, linear)
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.115242] TCP established hash table entries: 4096 (order: 2, 16384 bytes, linear)
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.115327] TCP bind hash table entries: 4096 (order: 4, 65536 bytes, linear)
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.115512] TCP: Hash tables configured (established 4096 bind 4096)
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.115635] UDP hash table entries: 256 (order: 1, 8192 bytes, linear)
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.115686] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes, linear)
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.115889] NET: Registered PF_UNIX/PF_LOCAL protocol family
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.116364] RPC: Registered named UNIX socket transport module.
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.116390] RPC: Registered udp transport module.
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.116409] RPC: Registered tcp transport module.
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.116427] RPC: Registered tcp NFSv4.1 backchannel transport module.
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.117470] hw perfevents: enabled with armv7_cortex_a7 PMU driver, 7 counters available
Jan 1 00:00:03 buildroot kern.notice kernel: [ 0.118568] Initialise system trusted keyrings
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.118749] workingset: timestamp_bits=14 max_order=17 bucket_order=3
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.124923] zbud: loaded
Jan 1 00:00:03 buildroot kern.notice kernel: [ 0.126824] NFS: Registering the id_resolver key type
Jan 1 00:00:03 buildroot kern.notice kernel: [ 0.126869] Key type id_resolver registered
Jan 1 00:00:03 buildroot kern.notice kernel: [ 0.126890] Key type id_legacy registered
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.126999] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.127025] nfs4flexfilelayout_init: NFSv4 Flexfile Layout Driver Registering...
Jan 1 00:00:03 buildroot kern.notice kernel: [ 0.128085] Key type asymmetric registered
Jan 1 00:00:03 buildroot kern.notice kernel: [ 0.128110] Asymmetric key parser 'x509' registered
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.128252] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 247)
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.128284] io scheduler mq-deadline registered
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.128305] io scheduler kyber registered
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.131060] bcm2708_fb soc:fb: FB found 1 display(s)
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.142734] Console: switching to colour frame buffer device 90x30
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.149347] bcm2708_fb soc:fb: Registered framebuffer for display 0, size 720x480
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.155051] bcm2835-rng 3f104000.rng: hwrng registered
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.157550] vc-mem: phys_addr:0x00000000 mem_base=0x1ec00000 mem_size:0x20000000(512 MiB)
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.171738] brd: module loaded
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.178840] loop: module loaded
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.181688] Loading iSCSI transport class v2.0-870.
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.185280] usbcore: registered new interface driver lan78xx
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.187650] usbcore: registered new interface driver smsc95xx
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.189892] dwc_otg: version 3.00a 10-AUG-2012 (platform bus)
Jan 1 00:00:03 buildroot kern.debug kernel: [ 0.192218] dwc_otg: FIQ enabled
Jan 1 00:00:03 buildroot kern.debug kernel: [ 0.192226] dwc_otg: NAK holdoff enabled
Jan 1 00:00:03 buildroot kern.debug kernel: [ 0.192232] dwc_otg: FIQ split-transaction FSM enabled
Jan 1 00:00:03 buildroot kern.debug kernel: [ 0.192244] Module dwc_common_port init
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.192447] usbcore: registered new interface driver usb-storage
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.194879] mousedev: PS/2 mouse device common for all mice
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.198378] sdhci: Secure Digital Host Controller Interface driver
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.200697] sdhci: Copyright(c) Pierre Ossman
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.203125] sdhci-pltfm: SDHCI platform and OF driver helper
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.206065] ledtrig-cpu: registered to indicate activity on CPUs
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.208549] hid: raw HID events driver (C) Jiri Kosina
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.210882] usbcore: registered new interface driver usbhid
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.213142] usbhid: USB HID core driver
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.215449] bcm2835_vchiq 3f00b840.mailbox: there is not valid maps for state default
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.221230] Initializing XFRM netlink socket
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.223547] NET: Registered PF_PACKET protocol family
Jan 1 00:00:03 buildroot kern.notice kernel: [ 0.225967] Key type dns_resolver registered
Jan 1 00:00:03 buildroot kern.notice kernel: [ 0.228407] Registering SWP/SWPB emulation handler
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.230850] registered taskstats version 1
Jan 1 00:00:03 buildroot kern.notice kernel: [ 0.233080] Loading compiled-in X.509 certificates
Jan 1 00:00:03 buildroot kern.notice kernel: [ 0.235847] Key type .fscrypt registered
Jan 1 00:00:03 buildroot kern.notice kernel: [ 0.237946] Key type fscrypt-provisioning registered
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.244630] uart-pl011 3f201000.serial: cts_event_workaround enabled
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.246883] 3f201000.serial: ttyAMA1 at MMIO 0x3f201000 (irq = 114, base_baud = 0) is a PL011 rev2
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.251437] serial serial0: tty port ttyAMA1 registered
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.254978] bcm2835-wdt bcm2835-wdt: Broadcom BCM2835 watchdog timer
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.257572] bcm2835-power bcm2835-power: Broadcom BCM2835 power domains driver
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.261043] mmc-bcm2835 3f300000.mmcnr: mmc_debug:0 mmc_debug2:0
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.263427] mmc-bcm2835 3f300000.mmcnr: DMA channel allocated
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.293885] sdhost: log_buf @ 8fda17ee (d5910000)
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.343926] mmc0: sdhost-bcm2835 loaded - DMA enabled (>1)
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.346528] of_cfs_init
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.348950] of_cfs_init: OK
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.352169] Waiting for root device /dev/mmcblk0p2...
Jan 1 00:00:03 buildroot kern.warn kernel: [ 0.380385] mmc0: host does not support reading read-only switch, assuming write-enable
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.385633] mmc0: new high speed SDXC card at address 0001
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.388688] mmcblk0: mmc0:0001 62.5 GiB
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.392823] mmcblk0: p1 p2 p3
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.395627] mmcblk0: mmc0:0001 62.5 GiB
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.428731] mmc1: new high speed SDIO card at address 0001
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.448558] EXT4-fs (mmcblk0p2): orphan cleanup on readonly fs
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.450917] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Quota mode: none.
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.455515] VFS: Mounted root (ext4 filesystem) readonly on device 179:2.
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.458602] devtmpfs: mounted
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.462805] Freeing unused kernel image (initmem) memory: 1024K
Jan 1 00:00:03 buildroot kern.info kernel: [ 0.484291] Run /sbin/init as init process
Jan 1 00:00:03 buildroot kern.debug kernel: [ 0.486648] with arguments:
Jan 1 00:00:03 buildroot kern.debug kernel: [ 0.486654] /sbin/init
Jan 1 00:00:03 buildroot kern.debug kernel: [ 0.486660] with environment:
Jan 1 00:00:03 buildroot kern.debug kernel: [ 0.486665] HOME=/
Jan 1 00:00:03 buildroot kern.debug kernel: [ 0.486671] TERM=linux
Jan 1 00:00:03 buildroot kern.info kernel: [ 1.792994] EXT4-fs (mmcblk0p3): recovery complete
Jan 1 00:00:03 buildroot kern.info kernel: [ 1.797380] EXT4-fs (mmcblk0p3): mounted filesystem with ordered data mode. Quota mode: none.
Jan 1 00:00:03 buildroot kern.notice kernel: [ 2.148830] cfg80211: Loading compiled-in X.509 certificates for regulatory database
Jan 1 00:00:03 buildroot kern.notice kernel: [ 2.207338] cfg80211: Loaded X.509 cert '[email protected]: 577e021cb980e0e820821ba7b54b4961b8b4fadf'
Jan 1 00:00:03 buildroot kern.notice kernel: [ 2.214655] cfg80211: Loaded X.509 cert '[email protected]: 3abbc6ec146e09d1b6016ab9d6cf71dd233f0328'
Jan 1 00:00:03 buildroot kern.notice kernel: [ 2.222166] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
Jan 1 00:00:03 buildroot kern.debug kernel: [ 2.340954] brcmfmac: F1 signature read @0x18000000=0x1541a9a6
Jan 1 00:00:03 buildroot kern.info kernel: [ 2.345747] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1
Jan 1 00:00:03 buildroot kern.info kernel: [ 2.351655] usbcore: registered new interface driver brcmfmac
Jan 1 00:00:03 buildroot kern.info kernel: [ 2.554737] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM43430/1 wl0: Jun 14 2023 07:27:45 version 7.45.96.s1 (gf031a129) FWID 01-70bd2af7 es7
Jan 1 00:00:03 buildroot kern.info kernel: [ 2.601108] Bluetooth: Core ver 2.22
Jan 1 00:00:03 buildroot kern.info kernel: [ 2.604114] NET: Registered PF_BLUETOOTH protocol family
Jan 1 00:00:03 buildroot kern.info kernel: [ 2.606946] Bluetooth: HCI device and connection manager initialized
Jan 1 00:00:03 buildroot kern.info kernel: [ 2.609808] Bluetooth: HCI socket layer initialized
Jan 1 00:00:03 buildroot kern.info kernel: [ 2.612565] Bluetooth: L2CAP socket layer initialized
Jan 1 00:00:03 buildroot kern.info kernel: [ 2.615288] Bluetooth: SCO socket layer initialized
Jan 1 00:00:03 buildroot kern.info kernel: [ 2.637242] Bluetooth: HCI UART driver ver 2.3
Jan 1 00:00:03 buildroot kern.info kernel: [ 2.639908] Bluetooth: HCI UART protocol H4 registered
Jan 1 00:00:03 buildroot kern.info kernel: [ 2.642540] Bluetooth: HCI UART protocol Three-wire (H5) registered
Jan 1 00:00:03 buildroot kern.info kernel: [ 2.645300] Bluetooth: HCI UART protocol Broadcom registered
Jan 1 00:00:03 buildroot kern.warn kernel: [ 2.645486] hci_uart_bcm serial0-0: supply vbat not found, using dummy regulator
Jan 1 00:00:03 buildroot kern.warn kernel: [ 2.650440] hci_uart_bcm serial0-0: supply vddio not found, using dummy regulator
Jan 1 00:00:03 buildroot kern.info kernel: [ 2.773209] uart-pl011 3f201000.serial: no DMA platform data
Jan 1 00:00:03 buildroot kern.info kernel: [ 3.024650] Bluetooth: hci0: BCM: chip id 94
Jan 1 00:00:03 buildroot kern.info kernel: [ 3.027581] Bluetooth: hci0: BCM: features 0x2e
Jan 1 00:00:03 buildroot kern.info kernel: [ 3.031212] Bluetooth: hci0: BCM43430A1
Jan 1 00:00:03 buildroot kern.info kernel: [ 3.033533] Bluetooth: hci0: BCM43430A1 (001.002.009) build 0000
Jan 1 00:00:03 buildroot kern.info kernel: [ 3.040450] Bluetooth: hci0: BCM43430A1 'brcm/BCM43430A1.raspberrypi,model-zero-2-w.hcd' Patch
Jan 1 00:00:03 buildroot kern.warn kernel: [ 3.489654] dwc2 3f980000.usb: supply vusb_d not found, using dummy regulator
Jan 1 00:00:03 buildroot kern.warn kernel: [ 3.492061] dwc2 3f980000.usb: supply vusb_a not found, using dummy regulator
Jan 1 00:00:03 buildroot kern.info kernel: [ 3.595292] dwc2 3f980000.usb: EPs: 8, dedicated fifos, 4080 entries in SPRAM
Jan 1 00:00:03 buildroot kern.info kernel: [ 3.685156] Bluetooth: hci0: BCM: features 0x2e
Jan 1 00:00:03 buildroot kern.info kernel: [ 3.689306] Bluetooth: hci0: BCM43436 37.4MHz Class 1.5 RaspBerry Pi Zero2 [Version: 1017.1042]
Jan 1 00:00:03 buildroot kern.info kernel: [ 3.689331] Bluetooth: hci0: BCM43430A1 (001.002.009) build 1042
Jan 1 00:00:03 buildroot kern.info kernel: [ 3.689921] Bluetooth: hci0: BCM: Using default device address (43:43:a1:12:1f:ac)
Jan 1 00:00:03 buildroot user.info console: Running sysctl: OK
Jan 1 00:00:03 buildroot daemon.notice haveged: haveged starting up
Jan 1 00:00:03 buildroot user.warn console: haveged: command socket is listening at fd 3
Jan 1 00:00:03 buildroot user.info console: Starting haveged: OK
Jan 1 00:00:03 buildroot daemon.info rngd: Initializing available sources
Jan 1 00:00:03 buildroot daemon.info rngd: [hwrng ]: Initialized
Jan 1 00:00:03 buildroot daemon.info rngd: [jitter]: JITTER timeout set to 5 sec
Jan 1 00:00:03 buildroot user.info console: Starting rngd: OK
Jan 1 00:00:03 buildroot user.info console: Starting system message bus: done
Jan 1 00:00:03 buildroot user.info console: Generate hostapd configuration at /var/run/hostapd.conf
Jan 1 00:00:03 buildroot user.info console: Starting bluetoothd: OK
Jan 1 00:00:04 buildroot daemon.info bluetoothd[170]: Bluetooth daemon 5.68
Jan 1 00:00:04 buildroot daemon.info bluetoothd[170]: Starting SDP server
Jan 1 00:00:04 buildroot daemon.warn bluetoothd[170]: src/plugin.c:plugin_init() System does not support csip plugin
Jan 1 00:00:04 buildroot daemon.warn bluetoothd[170]: src/plugin.c:plugin_init() System does not support bass plugin
Jan 1 00:00:04 buildroot daemon.warn bluetoothd[170]: profiles/network/bnep.c:bnep_init() kernel lacks bnep-protocol support
Jan 1 00:00:04 buildroot daemon.warn bluetoothd[170]: src/plugin.c:plugin_init() System does not support network plugin
Jan 1 00:00:04 buildroot daemon.info bluetoothd[170]: Bluetooth management interface 1.22 initialized
Jan 1 00:00:04 buildroot kern.info kernel: [ 4.139984] Bluetooth: MGMT ver 1.22
Jan 1 00:00:04 buildroot kern.info kernel: [ 4.168771] NET: Registered PF_ALG protocol family
Jan 1 00:00:04 buildroot kern.info kernel: [ 4.210534] cryptd: max_cpu_qlen set to 1000
Jan 1 00:00:04 buildroot user.info console: Starting network: OK
Jan 1 00:00:04 buildroot user.info console: No persistent location to store SSH host keys. New keys will be
Jan 1 00:00:04 buildroot user.info console: generated at each boot. Are you sure this is what you want to do?
Jan 1 00:00:04 buildroot kern.info kernel: [ 4.603087] NET: Registered PF_INET6 protocol family
Jan 1 00:00:04 buildroot authpriv.info dropbear[230]: Running in background
Jan 1 00:00:04 buildroot kern.info kernel: [ 4.662276] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Jan 1 00:00:04 buildroot kern.info kernel: [ 4.664709] Segment Routing with IPv6
Jan 1 00:00:04 buildroot kern.info kernel: [ 4.668688] In-situ OAM (IOAM) with IPv6
Jan 1 00:00:04 buildroot user.info console: Starting dropbear sshd: OK
Jan 1 00:00:04 buildroot daemon.info dnsmasq[235]: started, version 2.89 cachesize 150
Jan 1 00:00:04 buildroot daemon.info dnsmasq[235]: compile time options: IPv6 GNU-getopt DBus no-UBus no-i18n no-IDN DHCP DHCPv6 no-Lua TFTP no-conntrack ipset no-nftset auth no-cryptohash no-DNSSEC loop-detect inotify dumpfile
Jan 1 00:00:04 buildroot daemon.info dnsmasq-dhcp[235]: DHCP, IP range 10.0.0.2 -- 10.0.0.20, lease time 12h
Jan 1 00:00:04 buildroot daemon.info dnsmasq[235]: read /etc/hosts - 2 names
Jan 1 00:00:04 buildroot user.info console: Starting dnsmasq: OK
Jan 1 00:00:04 buildroot user.info console: Starting bt-agent: OK
Jan 1 00:00:04 buildroot kern.info kernel: [ 4.880970] file system registered
Jan 1 00:00:04 buildroot user.info console: Setting up usb_gadgets: OK
Jan 1 00:00:04 buildroot kern.info kernel: [ 4.955732] read descriptors
Jan 1 00:00:04 buildroot kern.info kernel: [ 4.957653] read strings
Jan 1 00:00:05 buildroot daemon.info rngd: [jitter]: Initializing AES buffer
Jan 1 00:00:05 buildroot user.info console: Starting umtprd: OK
Jan 1 00:00:05 buildroot user.info console: Starting aawgd: OK
Jan 1 00:00:05 buildroot daemon.info : starting pid 272, tty '/dev/tty1': '/sbin/getty -L tty1 0 vt100 '
Jan 1 00:00:06 buildroot user.info aawgd[271]: AA Wireless Dongle
Jan 1 00:00:06 buildroot user.info aawgd[271]: Starting uevent monitoring
Jan 1 00:00:06 buildroot user.info aawgd[271]: Uevent monitoring started
Jan 1 00:00:06 buildroot user.info aawgd[271]: Initializing USB ManagerJan 1 00:00:06 buildroot user.info aawgd[271]: USB Manager: Disabled all USB gadgets
Jan 1 00:00:06 buildroot user.info aawgd[271]: USB Manager: Found UDC 3f980000.usb
Jan 1 00:00:06 buildroot user.info aawgd[271]: Using bluetooth adapter at path: /org/bluez/hci0
Jan 1 00:00:06 buildroot user.info aawgd[271]: Bluetooth adapter alias: WirelessAADongle-34ff24
Jan 1 00:00:06 buildroot user.info aawgd[271]: Bluetooth AA Wireless profile active
Jan 1 00:00:06 buildroot kern.info kernel: [ 6.264023] Bluetooth: RFCOMM TTY layer initialized
Jan 1 00:00:06 buildroot kern.info kernel: [ 6.265916] Bluetooth: RFCOMM socket layer initialized
Jan 1 00:00:06 buildroot kern.info kernel: [ 6.267741] Bluetooth: RFCOMM ver 1.11
Jan 1 00:00:06 buildroot user.info aawgd[271]: HSP Handset profile active
Jan 1 00:00:06 buildroot user.info aawgd[271]: Connection Strategy: 2
Jan 1 00:00:06 buildroot user.info aawgd[271]: Waiting for the accessory to connect first
Jan 1 00:00:06 buildroot kern.info kernel: [ 6.279832] dwc2 3f980000.usb: bound driver configfs-gadget.default
Jan 1 00:00:06 buildroot user.info aawgd[271]: USB Manager: Enabled default gadget
Jan 1 00:00:06 buildroot kern.info kernel: [ 6.879636] dwc2 3f980000.usb: new device is high-speed
Jan 1 00:00:06 buildroot kern.info kernel: [ 6.997681] android_work: sent uevent USB_STATE=CONNECTED
Jan 1 00:00:06 buildroot kern.info kernel: [ 6.999591] dwc2 3f980000.usb: new address 4
Jan 1 00:00:07 buildroot kern.info kernel: [ 7.022542] android_work: sent uevent USB_STATE=CONFIGURED
Jan 1 00:00:09 buildroot daemon.info rngd: [jitter]: Unable to obtain AES key, disabling JITTER source
Jan 1 00:00:09 buildroot daemon.err rngd: [jitter]: Initialization Failed
Jan 1 00:00:19 buildroot daemon.info hostapd: wlan0: STA 62:54:80:e8:02:99 IEEE 802.11: associated
Jan 1 00:00:21 buildroot daemon.info hostapd: wlan0: STA 62:54:80:e8:02:99 IEEE 802.11: disassociated
Jan 1 00:00:21 buildroot daemon.info hostapd: wlan0: STA 62:54:80:e8:02:99 IEEE 802.11: disassociated
Jan 1 00:00:21 buildroot daemon.info hostapd: wlan0: STA 62:54:80:e8:02:99 IEEE 802.11: associated
Jan 1 00:00:25 buildroot daemon.info hostapd: wlan0: STA 62:54:80:e8:02:99 IEEE 802.11: disassociated
Jan 1 00:00:34 buildroot daemon.info hostapd: wlan0: STA 62:54:80:e8:02:99 IEEE 802.11: associated
Jan 1 00:00:35 buildroot daemon.info hostapd: wlan0: STA 62:54:80:e8:02:99 WPA: pairwise key handshake completed (RSN)
Jan 1 00:00:38 buildroot daemon.info dnsmasq-dhcp[235]: DHCPDISCOVER(wlan0) 62:54:80:e8:02:99
Jan 1 00:00:38 buildroot daemon.info dnsmasq-dhcp[235]: DHCPOFFER(wlan0) 10.0.0.2 62:54:80:e8:02:99
Jan 1 00:00:38 buildroot daemon.info dnsmasq-dhcp[235]: DHCPDISCOVER(wlan0) 62:54:80:e8:02:99
Jan 1 00:00:38 buildroot daemon.info dnsmasq-dhcp[235]: DHCPOFFER(wlan0) 10.0.0.2 62:54:80:e8:02:99
Jan 1 00:00:38 buildroot daemon.info dnsmasq-dhcp[235]: DHCPDISCOVER(wlan0) 62:54:80:e8:02:99
Jan 1 00:00:38 buildroot daemon.info dnsmasq-dhcp[235]: DHCPOFFER(wlan0) 10.0.0.2 62:54:80:e8:02:99
Jan 1 00:00:38 buildroot daemon.info dnsmasq-dhcp[235]: DHCPREQUEST(wlan0) 10.0.0.2 62:54:80:e8:02:99
Jan 1 00:00:38 buildroot daemon.info dnsmasq-dhcp[235]: DHCPACK(wlan0) 10.0.0.2 62:54:80:e8:02:99 Pixel-6
Jan 1 00:02:31 buildroot authpriv.info dropbear[278]: Child connection from 10.0.0.2:34084
Jan 1 00:02:31 buildroot authpriv.info dropbear[278]: Generated hostkey /etc/dropbear/dropbear_ed25519_host_key, fingerprint is SHA256:IxGGHFMMGYU9cNXyyRd5a3gsGRTL5t53G1b4DtFIhc0
Jan 1 00:02:32 buildroot authpriv.info dropbear[279]: Child connection from 10.0.0.2:34088
Jan 1 00:02:33 buildroot authpriv.notice dropbear[279]: Password auth succeeded for 'root' from 10.0.0.2:34088
Jan 1 00:02:36 buildroot authpriv.info dropbear[278]: Exit before auth from <10.0.0.2:34084>: Exited normally
#
I have also tried switching the connection mode to 2 which prevents the reboot doom loop but the phone never finds an android auto connection.
Maybe you can try disable legacy mode from aa-proxy-rs. It is doing less USB switching. Maybe it's worth trying as I suspect that probably it is something wrong with power during these resets...
Tried the version you linked to but no joy. Is there a config fill I should have modified to disable legacy mode? I didn't'see it so assumed that was an image with legacy mode already disabled. The version you linked to also did NOT work in the tacoma.
Is there a config fill I should have modified to disable legacy mode?
Yes there is. You can adjust the config manually or via webinterface: https://github.com/aa-proxy/aa-proxy-rs?tab=readme-ov-file#embedded-web-interface
didn't'see it so assumed that was an image with legacy mode already disabled
No, it is a general build. All options are set to its defaults.
Logs can be obtained also via web and I'll be glad to see those to tell you more about your problems... ps. you can also join our discord (link on main project page) to more easily talk and and support...
I'm having trouble connecting to the WiFi to make the changes - whats the wifi password?
I'm having trouble connecting to the WiFi to make the changes - whats the wifi password?
Depend what image you flashed (aa-proxy-rs?) and if you enabled WiFi password in aawgd.conf