Crimson backports unofficial

Hardware Librem 5
144

Purism has informally indicated that the time interval between crimson and dawn will be less than the time interval between byzantium and crimson was, and you can see from the commit stream that @‌dos is already working on dawn but he has stated clearly that it is not ready for experimental download and install.

So don’t be too pessimistic but in any case I guess it depends on what you mean by “soon” - and I would in no way encourage Purism to make any more precise public statements about the timing for dawn.

145

Well, you can install and run it, you just won’t get any help nor compassion when things inevitably break :wink: There’s little value in reporting bugs and regressions at this point either.

146

Since crimson’s gnome calls USSD support was very unreliable compared to that of FuriOS forky, I wanted to try updating just gnome calls.

I installed individual debs by manually resolving dependencies, but gnome apps won’t start, firefox and thunderbird worked.

Then I did a dist-upgrade but keyboard won’t launch. I had to run

update-alternatives –config Phosh-OSKand select phosh-osk-stevia (I had to use jumpdrive and chroot). So you might want to add this to readme.

Also millipixels from backports don’t recognize qr codes, so I had to downgrade and hold it to the crimson version. Did you miss any patches or updates ?

147

The latest one also works not so good, Cyrillic symbols show up as “?”. It would be difficult to upgrade just gnome calls because they depends on whole gnome infrastructure like gnome-shell, gnome-control-center, etc.

Yes, I’ve disabled qr-codes to speed-up the app. gnome-decoder works fine with backports, please try it.

p.s. please do not try to upgrade your phone right now, there are some broken deps in the repo that I’m trying to fix to reach Gnome 50 environment.

148

Gnome 50 is here!

p.s. epiphany-browser is working a little bit again

149

Phosh 0.56 is here!

Note: at some point I’ve lost the vibration feedback on my phone… Does anybody know how to debug this issue?

150

Maybe search this forum for feedbackd but, beyond that, no.

Do you get haptic feedback on initial power on? i.e. way before any part of the UI is running / probably before any part of Linux is even running?

The point of that question is to distinguish between a hypothetical hardware failure of the haptic unit and just some breakage within the UI.

151

Yes, so I assume that hardware is working well but events from, e.g.m phone calls or button pressing are mist somewhere.

152

OK, given that you may be running an unusual operating system, what about downloading standard crimson, flashing it to a spare µSD card, and temporarily booting your phone from µSD card. Does standard crimson provide correct haptic feedback?

153

Is your user in the feedbackd group? I needed to do this manually at one point.

154

yes

$ groups
purism dialout sudo audio video systemd-journal render netdev feedbackd geoclue

155

Yes! For the first sight it works. At least for calls, keyboard, closing apps…

156

OK, now the hard part … working out what is causing the difference. It could be software version. It could be settings.

157

The apps are very very slow since last update - most likely due to missing hardware acceleration and newer gtk4 (needs gles 3.0). It also power off more often.

I can still use USSD pay, though needs a lot of patience. Since it does not work well on crimson I can’t go back either :frowning:

Hoping dawn comes sooner or newer mesa lands in crimson.

Update: Setting MESA_GLES_VERSION_OVERRIDE = 3.2 seems to help.

Now I’m wondering how to set it system wide, may be /etc/profile ?

158

Could you specify which exactly app you tested?

There are quite a lot glitches to set MESA_GLES_VERSION_OVERRIDE in system wide.. Waiting the newer mesa appears in debian repo.

159

Both GTK4 and Mesa need further work than what’s already upstream to work well, so you can’t expect them to work well in any backports right now.

160

I can get calls, chatty and millipixels to load faster, firefox gives a black screen, can’t see any text, gnome web still works, so can live with it.

I copied .desktop files from /usr/share/applications to .local/share/applications and added env MESA_GLES_VERSION_OVERRIDE=3.0 (not sure if 3.2 or 3.0 better) before the command on Exec= line.

I tried the same in /usr/share/wayland-sessions but it sees not working - millipixels loading screen keeps spinning even after millipixels itself is started. Is phosh ported to gtk4 yet?

161

I’ve just landed Mesa 26.3.0-rc1 to the backports!

Let’s see the profit:

purism@pureos:~$ DISPLAY=:0 glxinfo -B
name of display: :0
display: :0  screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
    Vendor: Mesa (0xffffffff)
    Device: Vivante GC7000 rev 6214 (0xffffffff)
    Version: 26.3.0
    Accelerated: yes
    Video memory: 0MB
    Unified memory: yes
    Preferred profile: compat (0x2)
    Max core profile version: 0.0
    Max compat profile version: 2.1
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 3.0
OpenGL vendor string: Mesa
OpenGL renderer string: Vivante GC7000 rev 6214
OpenGL version string: 2.1 Mesa 26.3.0~rc1-1
OpenGL shading language version string: 1.20

OpenGL ES profile version string: OpenGL ES 3.0 Mesa 26.3.0~rc1-1
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00
162

Yay! galilliey is back.

Looks like keyboard osk has issues mesa upstream. Looks like bug show up on a initramfs update, not installing mesa at first time.

163

My L5 still alive :joy:

Thanks for this link! I’ve just thought to upgrade my kernel but will do it more careful now. I used 6.18 for a week and do not observed troubles with mesa 26.2.0. Hope current update will be successful… :folded_hands: