Yes, but it is only applied to the CM5 device tree. CM4/CM3 use the BCM2835 audio driver and that doesn’t support what I did on CM5.
Another small update: the axp20x_battery
driver now reports energy_now
based on what the PMIC reports, not just the design capacity.
You can now also customize your battery’s capacity with
dtoverlay=clockworkpi-custom-battery,charge_full_design_uah=<full charge in uAh>,energy_full_design_uwh=<full charge in uWh>
after the dtoverlay=clockworkpi-uconsole-*
line.
For example I added an extra 2040mAh battery to my uConsole with 2 existing 3500mAh batteries, I would write:
dtoverlay=clockworkpi-custom-battery,charge_full_design_uah=9040000,energy_full_design_uwh=32544000
energy_full_design_uwh
assumes a 3.6V typical voltage.
Both of these changes will be PR’d back to Rex’s kernel soon.
The 6.12.30 kernel is out, which brings back the charging light. An update would be appreciated.
It was updated yesterday to 6.12.32. Didn’t pay attention to charging light though, but if it’s back without special config / userspace components then it should be back.
Just a heads up. Building from source with @Rex’s latest branch merge breaks keyboard and trackball input.
Did it? I was about to compile and test it to upload the new package. I should get on that ASAP see what’s wrong.
You are correct, not sure what happened but looking now.
Not sure, the only changes from the RPi kernel was the same changes that’s been there I reverted the merge from RPi earlier today for now till I look into it.
Rebuilt just now and it still didn’t work, but I’m not sure if it’s my fault because I forgot my sd card reader at home and can’t see what happened. When I get home I’ll try again and let you know how it goes. Thanks for looking into it so quickly though.
I looked it’s nothing on my end is wrong but they did make several changes to dwc2
here’s just 2 of the many.
I suspect one of the changes broke USB for us. I’ll go over them later and see what needs reverted and do a PR to get it fixed.
I just seen there are 2 new commits for dwc2, I just merged them. Going to compile and test to see if RPi fixed it already.
Can confirm! Working great.
I found another problem with 6.12.33 USB storage is not working for me.
RPi fixed the issue, it’s not merged yet mainline yet but I’ve fixed the issue in my fork. Build away!
Thanks as always! Seems to be working.
By the way, the recent Arch Linux update has the linux-firmware
package split by vendor, and Arch Linux ARM is also affected by the change. Updating the package now pulls in a motherload of firmware bloat. Can somebody update the kernel package to accept only the minimum firmware?
I’ve been daily driving this image since a bit after it was posted and now I’ve (re-)made an account to post here. Thank you very much for this. Today I’ve upgraded to kernel version 6.12 and through some trial and error once again have a working system.
I have a novice question: How do I configure this kernel for Waydroid? I’ve been feeling my way towards a working setup but this feels relevant given the audience and if you could give me any tips you would help me out a lot.
Glad you asked.
It used to be that older versions of linux
required you to install an additional binder_linux-dkms
package. But the standard wiki suggests that the binder
kernel module necessary for Android to work is now included as standard, so feel free to get Waydroid in one of the following ways:
- Create and install your own package using AUR here. You may install the
yay
helper first if prolonged exposure to the terminal scares you. - Add the
archlinuxcn
repository to your/etc/pacman.conf
file, and install the keyring usingpacman -Sy archlinuxcn-keyring
. Afterwards, install the app itself usingpacman -Syu waydroid
.
I happen to have Waydroid installed on my install, and what few apps I ran it with worked. Mostly.
Were you not able to build the standard aur waydroid package? I didn’t have any problem using stock everything, but I admittedly didn’t play with it long before uninstalling it.