bluez-alsa VS rpi-eeprom

One thing I found from a quick search is that you no longer need to use hciattach if you're using a recent enough firmware. See here.

Maybe your Rant might have made sense a decade ago not anymore, you're just forgetting you you choice one can still survive with Alsa+Jack (even the firefox supports alsa when you complied with flags) if you question about bluez has pulse dependency bluez-alsa has been running flawlessly for me years now.

The current headset status in Linux for traditional bluetooth looks like this: The better quality mSBC (16kHz mono) codec for HFP is available with. pipewire/pipewire-pulse 0.3.20: https://gitlab.freedesktop.org/pipewire/pipewire/-/blob/master/NEWS Work is in progress for pulseaudio: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/254 bluez-alsa seems to have something as well, I am not sure about the completeness. https://github.com/Arkq/bluez-alsa

I don't have Pi 5 to check this, but from what I've read, it does not support PPS. And such support is required; otherwise, even with a source that supports PPS, the connection will behave in a non-PPS fashion.

Apparently, cable quality is also demonstrating itself to be a significant factor in the Pi 5 power supply environment.

Regarding both these points:

https://github.com/raspberrypi/rpi-eeprom/issues/497

I should note, I updated the eeprom, USB hub, and network firmware using the images provided from the following repository: https://github.com/raspberrypi/rpi-eeprom. So it certainly isn't a corrupted eeprom chip, and if it was I wouldn't be able to boot the old installation I pulled from my backup drive.

Its a known issue with the current Pi 4 boot firmware. The net install option is trying to look for a keyboard and gets confused with some HIDs.

I was working on a final project for my class and needed an adc. So I ordered an ADS1115 and I had to solder the pins onto it. I've never soldered before, but I tried my best. Didn't look amazing, but didn't look like any pins were getting shorted so I plugged it in to the Pi. I then noticed that my ssh disconnected and couldn't reconnect. Tried plugging in the HDMI and there was no video output. I tried flashing a new OS onto it, didn't work. Tried EEPROM recovery from here and it didn't work. So I think I killed the Pi. It doesn't feel like it's getting warmed up or anything.

See https://github.com/raspberrypi/rpi-eeprom/blob/master/firmware/release-notes.md

I try to reset the pi as factory settings (following this github advice). I use pi-imager to set my SD card to lead the pi using USB boot priority and plug a USB key with raspbian OS (no desktop) and now getting green screen when booting. Think that the pi is dead.

I think it was this one:

https://github.com/raspberrypi/rpi-eeprom/blob/master/firmwa...

I had the same problem as you, updated my eeprom and the problem was fixed

Firmware: https://github.com/raspberrypi/rpi-eeprom/releases/tag/v2020.09.03-138a1