I had the DevTerm and an A04 and that thing ran hot too.
I found an answer to the input/rotation problem using wayland and VNC. Took a lot of digging, and sifting through plenty of unhelpful suggestions. It’s apparently not a bug in wayfire/wayland, but a poorly documented decision with broken defaults (and no indication it’s a problem, except for lots of people posting on the internet with the issue) that has been that way for a while and will probably never be fixed. Good times.
Anyhow, the answer was here:
referring to the documentation at:
The takeaway is that the config file needs to be updated to add a specific section and entry.
For the Devterm (and presumably uConsole), the config file is at:
~/.config/wayfire.ini
And the new lines to include are (specifically for our devices):
[input-device:wlr_virtual_pointer_v1]
output = DSI-1
I don’t think it matters where you put them. I put those lines after the last [input-device …] section in my file.
The section name identifies that we’re talking about the virtual pointer which will get used in VNC (and probably other remote utilities?) And the output entry links it to our physical display, so it does the proper rotation translation based on the settings of the display. Without this config entry, it apparently takes bogus defaults and completely ignores the rotation.
This might be a good thing to add to the image at some point, @Rex. It would only affect people using VNC (and probably other stuff that uses the virtual pointer), but it’s such an obscure fix that it would save time and frustration, even if it’s only for a few folks. 
Bonus info:
Along the way, it educated me in wayland stuff a bit, since I was unfamiliar with it. There’s a utility called wlr-randr which is the wayland equivalent of xrandr. Just running it with no params will show the name of your display and various properties.
But you can also change the resolution, orientation, and scale with it. It won’t hurt your physical display to change these values, but it will affect how the screen is shown and can be cut off, etc. When remoting in with VNC, you can use it to get a larger display than the usual 1280x480.
This gives extra height and sets it to a more standard display mode (on the device itself, the top half of the screen won’t show).
wlr-randr --output DSI-1 --custom-mode 720x1280
or go full HD with
wlr-randr --output DSI-1 --custom-mode 1080x1920
I didn’t find --scale to be very useful, but it applies the scale to both width and height equally. If you want to zoom in you can go with something like
wlr-randr --output DSI-1 --custom-mode 1080x1920 --scale 1.5
or zoom out with something like
wlr-randr --output DSI-1 --custom-mode 1080x1920 --scale .75
In any case, putting those missing lines in the config file did the trick, and would probably be helpful for others.
6 Likes
I’ll add that and it will be in the next build.
2 Likes
I’ve installed ClockworkPi-CM4-Bookworm-Lite-6.6.41.img.xz and noticed two issues with it on my uconsole:
- wifi become ~5x less sensitive (like it is using another antenna connector?)
- upower shows 4x more power consumption (3.5W against 0.7W on stock Raspbian) — it could be a upower issue of course.
Has anyone try powertop to tune power consumption?
What discharging rate should I expect to be normal?
UPDATE: yeah… It looks like upower on the stock Raspbian shows some irrelevant data. It shows “energy-full” as 8 Wh, but it should be more like 25 Wh.
How do you have the external antenna connected? The stock distro only utilizes the PCB antenna on the CM4. This Bookworm image enables the u.fl port on the CM4 for the external antenna and if you have the stock antenna stuck to the metal case you’ll have interference problems.
1 Like
I have found that ibus does not want to work rationally on Wayfire. You will need to boot into X11 to get Chinese to work.
Hi, how to map ABXY keys for the proper usage e.g. in TIC-80 games?
UPDATE: found this method - trying it now
UPDATE2: it works with TIC80
If this was already mentioned on this thread, I apologize for the repeat. I noticed a lot of whine noise on the latest CM4 Bookworm image for Devterm with full battery and charger still connected and I vaguely remembered a fix for the stock image years ago…
It was this from @yatli:
There’s a bunch of other stuff in the same repo that might be useful, but I suspect most of the other issues are taken care of by the image itself (like the printer, fan, seems to work already, etc.) Also, I think most of the other things are for A04 and A06, but the battery/charging whine fix seems to work on CM4 as well, unless I’m imagining things. 
Anyhow, it’s a quick and easy build, and install, and it’s just another service to start up to run behind the scenes and tone down the whine. Not sure if it should be included in the Bookworm build, but thought it might be useful to share here in case anyone else was frustrated with the noise.
(Based on other posts to the forum, the whine noise isn’t an indication that’s something is wrong and going to break. But even if it’s not causing damage that doesn’t make it any less annoying.)
Wow! Okay… That’s something new. Thank you.
That was one part of the problem. I was using the PCB antenna and the external antenna was stuck to the metal case.
Now I enabled ant2 on both configurations. External antenna is connected to the u.fl port on the CM4.
The SIGNAL displayed by nmcli dev wifi list shows something like 15 dB lower values in Bookworm for the same hardware configuration. I had to connect a better external antenna to have something to measure at all. But it could be just a measurement issue. Download speed values are mostly equal.
That could also have something to do with the binary blobs for the Wi-Fi that ship with the old image and kernel, compared to the newer blobs that got pulled down when I built the new bookworm kernel and image.
What would take to port this to the CM4S? PotatoMania’s Arch Image work great, but I’m trying to get a debian distribution. I was hopping that this image would work since it can use the external Wifi, but it works the same as the official one: without wireless and sound.
I’m willing to work to get it done, and I did some (naive) things such as trying to port Arch’s wireless drivers and overlays, but I’m inexperienced with doing this kind of stuff, so if I someone can point me towards the right direction it would be great.
you can add the overlays from the arch kernel to the one from my github and recompile the kernel. then set the necessary overlays.
1 Like
I finally built my uConsole and confirmed that this was needed on it as well as the DevTerm. Without the wayfire.ini change, the mouse directions were rotated, but with the change it works as it should.
1 Like
thanks…I’ll look into that, wish you a good day, sir!
My bookworm image did some updates yesterday, and now it does not connect to any wifi.
It gives me this prompt for a passwerd, and even when I enter the correct password, it keeps brining this prompt.
Update, this doesn’t happen on other systems, that have’t been updated.
1 Like
My daily driver image is fully updated and I just updated a fresh flashed sd and i’m not having any issues. Did you install any extra WiFi stuff?
I had macchanger installed. I removed it just now, and It seems to have fixed the problem.
At least I was able to connect.
Would be a shame to lose the ability to randomize mac addresses. Macchanger still works on images that weren’t updated.
All the updates come from Raspberry Pi except the kernel and software just for the uConsole.
If Raspberry Pi changes how something works it will get updated in this image. That includes if they break a workflow.
1 Like
I get that. I will be testing another solution later.
Thanks for your increadible work on the images! They are fantastic!
1 Like
Thank you, I appreciate it!