Modernisation - Hardware support

[matt2005]

Hi,

I've been working on a modernised version of Crankshaft.

I've been working on a CI/CD to build and publish and general code tidyup.

Below is what I've done and my thinking behind it.

1. Bookworm and then Trixie update - This while being successful in running it was very buggy with all the supplemental scripts
2. Yocto build. This was somewhat successful but took ages to build and didn't work in GitHub actions without using a self hosted runner which was costly.
3. Repackage into Deb for bookworm/Trixie. - Successful, but still had buggy scripts that barely worked.
4. re-write scripts - this was aborted due to a lot of legacy processes that just don't work in newer debian.
5. Full ground up re-write in Qt6 utilising a separate backend core and ui. This will reduce the scripts to hopefully zero.

Point 5 is the part I'm working on now and its going well however I'm concentrating on getting a MVP out.
As this is going to be a MVP I have concentrated on a few core features.

Core Features implemented in MVP.

• Separate Core and UI
• Built via CI
• Creates artifacts for AMD64, ARMHF and ARM64.
• Raspberry PI images for Trixie for ARMHF and ARM64.
• AndroidAuto Support for both wired and wireless.

I really want to remove the older Pi2 from supported hardware, but add the RPI 4, RPI5,RPI zero 2.

[matt2005]

Based on the poll above pi2 is going to be removed from support