Crimson backports unofficial

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.

4 Likes

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.

2 Likes

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 ?

1 Like

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.

2 Likes

Gnome 50 is here!

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

3 Likes

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?

1 Like

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.

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

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?

1 Like

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

1 Like

yes

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

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

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

1 Like