Wondering how the work done elsewhere could be useful to avoid dropping M10 FHD from being supported

Moem · 29 Sept 2021, 18:29

@rondarius said in Wondering how the work done elsewhere could be useful to avoid dropping M10 FHD from being supported:

I think that @Flohack mentoined something about it in a Q&A a while back

I found this:

UBP 5.1 is a slightly different case as it came after Canonical but it still lacks a lot of what we need. Where possible we can take devices forward to the Halium based 7.1 [thinking Nexus 5 and Oneplus One here] but if that turns out not to be possible those will also have to be dropped. If there are people in the community who want to keep the old stuff and are able to maintain it, they are welcome to do that but the core team does not have enough resources to do that.

Source

(In the meantime, I may already have found a very affordable Oneplus 3...)

A Former User · 29 Sept 2021, 19:46

@moem

There are already 7.1 halium ports of Nexus 5 and OnePlus One.

Nexus 5 7.1 here: https://forums.ubports.com/topic/3614/lge-nexus-5-hammerhead

OPO 7.1 here: https://forums.ubports.com/topic/6012/halium-7-1-test-channel/60

Please note that these are 'in-development' test channels. Use at your own risk

Moem · 29 Sept 2021, 19:50

@loops said in Wondering how the work done elsewhere could be useful to avoid dropping M10 FHD from being supported:

There are already 7.1 halium ports of Nexus 5 and OnePlus One.

How could I forget? I tested that one! D'oh.

But does that mean that these devices will remain supported once we reach the Ubuntu 20.04 base?

nero355 · 29 Sept 2021, 20:11

Then I guess the BQ phones from that era will also be dropped as supported devices ?

I hope I can get Ubuntu Touch running on the Xiaomi 9T I have bought a while ago and someone made a start with porting Ubuntu Touch to it!

I need my non-Android fix...

Lakotaubp · 30 Sept 2021, 05:36

@nero355 THat issue got mentioned on Q&A 108 https://ubports.com/blog/ubports-news-1/post/ubuntu-touch-q-a-108-3778

Lakotaubp · 30 Sept 2021, 05:58

@moem OT for here but if you can stretch to a OP5. Personnally just found it better.

dobey · 1 Oct 2021, 16:10

@rondarius said in Wondering how the work done elsewhere could be useful to avoid dropping M10 FHD from being supported:

Probably will the drop of the 32 bit version of Ubuntu have some impact too. It will probably means that there will be no armhf version of UT.

No. Ubuntu and Debian still build 32-bit packages for both armhf and i386. The only thing Ubuntu dropped was 32-bit ISO builds, so they don't produce images any more. And I think they don't build 32-bit snaps maybe. Anything packaged as debs though should still be in the Ubuntu archives in even the latest Ubuntu releases.

So that doesn't affect how we build things.

Mez · 30 Sept 2021, 16:20

@rondarius Thanks for your reply.
I assumed the problem was the work to bring it to a more recent version of Halium (through Android). I thought that maybe if that work is already mostly done and the subsequent effort to bring it to the common mutualized Halium base is lighter than expected, it would make things easier and maybe even manageable for an extra couple years of support.
But from your answer, it seems it's not the only block of work to undertake to keep on supporting it, and kernel updates are another big chunk that amounts to too much.

It would be sad, I kind of thought it was a 1st class citizen (in the device support) and would be supported a bit longer due to historical nostalgia (one of the few official UT devices) but of course I understand priorities are elsewhere than a 5 years old device.
I was just throwing something out there to see if this could help in reducing the work to make it happen. If not, I'll stay on Android 6.2 until the end of (its) time, I can live with that.

Rondarius · 1 Oct 2021, 16:10

@dobey

CiberSheep · 3 Oct 2021, 08:29

This made me wonder if that work could actually help save the Aquaris M10 from being scrapped when 20.04 is up and running. You never know.
Is this useless or is this something to work on?

I followed you train of thought and put together a list of possible trees that might come handy for you to port to Halium image.

https://forums.ubports.com/topic/6790/device-tree-list

If I understood correctly:
cm/lineage 16.0 is Halium 9.0 (preferred?)
cm/lineage 14.1 is Halium 7.1 (good)
cm/lineage 12.1 is Halium 5.1 (current?)

I put there also vegetalte (Vegeta 5G) that someone started porting long time ago