The device page requires community help

[Kaizen]

Currently, there are +20 devices with seriously incomplete information. Many of these are devices which will get a major update soon. If we don't get our information straight, newcomers might make a very bad choice of device. Bad for them but also bad for us.See you getting sleep now.

Our plan is to arrange the information, so that old ports that haven't been updated are not promoted in any way. Please help us to fill the empty pages with relevant info ASAP.

Core: Google Nexus 4, Bq Aquaris E5, Meizu Pro 5, F(x)tec Pro1, Nexus 7 2013 WiFi, Google Nexus 7 2013 LTE

Community: Sony Xperia X Compact (F5321), Sony Xperia X Performance (F8131 & F8132), Sony Xperia XZ (F8331 & F8332), Xiaomi Redmi 5 Plus, Yu Yureka Black, Samsung Galaxy Note 4 (910F, 910P, 910T), Xiaomi Redmi 4X, Xiaomi Redmi 3X, 3S and 3SP, Xiaomi Redmi 4A, Sony Xperia Z1 (C610X), Zuk z2 Plus

Other: Pinebook, Desktop PC and Raspberry Pi

Simply click on "Community" -> "Improve this page" and follow the instructions. Good luck!

Take good examples & awe-inspiring for following good use of guidlines

• Samsung Galaxy S7 Award winner for technical writing & Porting resposbilty
• Xiaomi Redmi Note 7 Pro Vast info covered

Thanks ...

• To Moem for updating BQ E4.5
• Nikfrager for updating BQ E5

[nero355]

Perhaps you could let us know which devices will be EOL when it comes to future OTA Support after the Ubuntu 20.04 LTS base has been released and all devcies that don't support SystemD are dropped ?!

[Kaizen]

@nero355 I'm sorry, but I don't know.
All I can suggest at this point is to arrange the information so core team would be able to balance their decision.

[Nikfrager]

@kaizen I would like to provide the informations for the bq E5 by copy and paste from the bq E4.5. I can edit the md in GitLab and I can copy the information from the bq E4.5 but I cannot paste it into the md of the bq E5. Any hints?

[Capsia]

@nikfrager Hello! Gitlab doesn't allow the paste operation for some reason, if you'd like, you can use the "ctrl+v" keyboard shortcut instead. Thanks

[Capsia]

@nero355 Since 20.04 based Ubuntu Touch will be booting using SystemD I think devices that can't be pached to support it will be dropped at some time. Nothing official yet though.

[nero355]

@capsia
I know, but a list of those would be nice to have so people don't waste effort on those phones!

Perhaps two categories :

• Currently Supported Devices
• Legacy Devices

The sooner we know, the better!

And PLEASE PLEASE PLEASE : Sort them by Brand and their Model Name !!!
The current list is a mess...

[Moem]

@nero355 said in The device page requires community help:

And PLEASE PLEASE PLEASE : Sort them by Brand and their Model Name !!!

No, please don't. Sorting by matureness is a lot more useful to me.

[Capsia]

@Moem @nero355 said in The device page requires community help:

And PLEASE PLEASE PLEASE : Sort them by Brand and their Model Name !!!

We'll have sorting options soon, so you can choose to list them alphabetically or using maturity, but to have this and the filters as well we need the data about these ports

@nero355 said in The device page requires community help:

The sooner we know, the better!

True. I can say that Halium 9 devices will stay, but that's mostly up to the porter. If they wish to add all the necessary changes needed to make the device work, it will work, otherwise not.

[Nikfrager]

@capsia Thank you for the hint. Now I have completed the edition of the data/devices/vegetahd.md but I cannot commit the changes because of the message: "! Someone edited the file the same time you did. Please check out the file and make sure your changes will not unintentionally remove theirs." I cannot find this file. How to proceed now?

[Capsia]

@nikfrager I'm not sure if you already did, but you should make a fork before you commit the file. Then you can make the commit and file the merge request.

[Lakotaubp]

@nero355 Sorry but agree strongly with @Moem. It is of more use for people to know what devices are the most usabe as a daly driver quickly and as mentioned in the new blog https://ubports.com/blog/ubports-news-1/post/the-devices-page-recent-updates-future-development-3794 we are looking at possible groupings based around a Stable, RC and Dev rating similar to the OTA system.

[Nikfrager]

@capsia I did not find how to fork. I made a merge request instead with "replace vegetahd" and the content of the new edited file.

[Capsia]

@nikfrager Good! I'm merging it. Thank you

[Nikfrager]

@capsia Thank you!

[Moem]

It's lovely to see the legacy BQ devices get some love!

[nero355]

@lakotaubp said in The device page requires community help:

@nero355 Sorry but agree strongly with @Moem. It is of more use for people to know what devices are the most usabe as a daly driver quickly and as mentioned in the new blog https://ubports.com/blog/ubports-news-1/post/the-devices-page-recent-updates-future-development-3794 we are looking at possible groupings based around a Stable, RC and Dev rating similar to the OTA system.

I agree that it should not disappear but be one of the options because of the following :

• A user finds out about Ubuntu Touch
• Goes to the https://devices.ubports.com/ page
• Wants to check if any of the phones he/she owns are on the list quickly!

At this point you want to check something like that as easy as possible like for example the LineageOS website offers : https://download.lineageos.org/
Or the /e/ website : https://doc.e.foundation/devices

Not by scrolling endlessly...

[Moem]

@nero355 said in The device page requires community help:

A user finds out about Ubuntu Touch
Goes to the https://devices.ubports.com/ page
Wants to check if any of the phones he/she owns are on the list quickly!

And so she types 'onep' or 'xper' or another suitable combination of letters... and the right options pop up (or there is a notice that this phone is not yet supported). It can't get quicker than that. I would not want to scroll down to Oneplus or Sony...

Anyway, new options are coming, and you may even like them.

[nero355]

@moem said in The device page requires community help:

And so she types 'onep' or 'xper' or another suitable combination of letters... and the right options pop up (or there is a notice that this phone is not yet supported). It can't get quicker than that.

The visibility of that option is very poor in either Dark Mode Firefox of Day Mode Pale Moon

Also sometimes Search functions don't find what I am looking for while the thing I am looking for is actually there so I have stopped trusting them a very long time ago!

I would not want to scroll down to Oneplus or Sony...

Another option : https://wiki.merproject.org/wiki/Adaptations/libhybris

• Easy to go through.
• Very specific overview of the stuff that works and doesn't

Anyway, new options are coming, and you may even like them.

Can't wait!