I flashed Crimson like this
./scripts/librem5-flash-image --stable --variant plain --dist crimson
and the script said that the image installed was
Build "stable" 'Last stable librem5r4 build' from Tue Jan 14 18:35:42 2025
SMS works.
For phonecalls there is no audio (I can make a call but I cannot hear the other person’s voice and they cannot hear me).
Ideas on how to fix that?
Other who have tested, does phonecall audio work for you in Crimson?
Not working. Mic/sources not seen by system.
OK that explains why the other side cannot hear me, but I also hear no sound in a phonecall. I can get sound in other ways, like the test function in sound settings (the “front left” and “front right” sounds there work) and playing sound in web the browser works. Even if the mic does not work, it should be possible to hear the incoming audio in a phonecall?
There are some changes you may just did not see yet. For example Squeekboard supports more characters and smileys and some previously not supported apps and Shift Modifier. Some of my recent work for custom layouts do not work correctly on Squeekboard below version 1.43.
Also Phosh supports new stuff like custom quick settings, quick settings drop down menus, different users on one system, lots of improvements to phosh-osk-stub and so on. Not everything is visible on the UI or on the first view.
Crimson have the backports too
See also:
I have that same issue. Just installed crimson and can’t get Wifi, lucky or not…
As you can see from the table, at the moment it depends on which card you have.
Anyone who can’t get WiFi able to test a USB ethernet dongle? (so that there is at least some way of being on the network)
I created an issue for this: Redpine card is not supported in current Crimson image (#5) · Issues · PureOS / Core Packages / base-files · GitLab
Crimson devs also requested to get feedback of non-working issues to PureOS-project - Purism Mailing Lists - drop them a line and/or link to ticket, just in case.
I can verify that usb-dongle/hub did give net connection (as per convergence testing), although I did also have a working wifi.
So the alsa path is the defective one? What do those {} mean? Is that just a programmers way of leaving comments on the programming without it interfering by being read by the computer as code?
man bash
search for Brace Expansion
Hey, I am thinking to flash PureOS Crimson. Some things are broken, the LUKS disk encryption is a big one for me. Will this problems get fixed with updates, or will I have to re-flash a “final release image”?
The Crimson is purely for testing at this point. It is not suggested to “upgrade” to it. More updates and images are expected to come in the coming months. Expect to need to re-flash a new image if you use a testing image (the plan seems to be that there will be an upgrade path from byz, eventually). For more info, see " PureOS Crimson Development Reports" from Purism news page - monthly update expected in a week or so.
I understand. Thank you sir.
Almost certainly. It is difficult to change an unencrypted disk to an encrypted disk in situ.
Even apart from the disk encryption (current) restriction, there is some likelihood that you might have to reflash in order to get to the final (official) release of crimson - given the unpredictable and potentially buggy state of the many devices that have been testing interim releases of crimson.
the official crimson probably will be out very close to the end of the support of Debian 11 day which in Aug 31 2026. I don’t think it is even in the beta release now. Feels like byzantium will have another year without any updates.ha