For people running Noble (24.04) on their devices, is your device listed on devices.ubuntu-touch.io with Noble support?

paulcarroty

@sm-xcx yeah, 24.04 works well, so remove "abandoned" label for now. Heard that VoLTE works too, Hotspot was fixed long time ago.

Moem

@paulcarroty said:

Heard that VoLTE works too

I found that hard to believe but here is a report: https://forums.ubports.com/topic/11941/call-for-testing-ubuntu-touch-24.04-1.2/31?_=1773354021518

sm-xcx

@paulcarroty sure, will do.

messayisto

@sm-xcx volta quintus works with noble toi, see my entry in the device section of the -forum:
https://forums.ubports.com/topic/11616/installation-experience-ut-on-vollaos-15/8

sm-xcx

@messayisto thank you so much!!

oldbutndy

@sm-xcx - Since you are working on the whole group, could you add WiFi Calling to every device page ?
It is NOT working, for most UT phones, as far as I know, but I am newbie, so I don't truly know.
The point is, if someone new to UT wants to convert their phone to UT, or buy a new phone for UT use, and they REQUIRE WiFi calling, then it would be really nice to have the fact it does NOT work show up on easy to find page.

Also, I believe Nord N10 5G VoLTE calling IS working (at least on 24.04-1.n Daily, in USA, on T-Mobile & maybe others), but I can't use it (require WiFi calling), so please get confirmation from others.

Suggestion: Maybe add some type of region groups listing for countries that require VoLTE, and others transitioning to require it, and another group for countries still functional on 2G or 3G for long term ?
I realize with so many countries in the world and changing all the time, this might be a crazy suggestion. But it would help for people now using 2G / 3G , but in a country changing soon to VoLTE. They might want to buy a phone that already supports it.

Also, any country that REQUIRES VoLTE.

If you created a code for the above groups, that code could be on each device page, next to VoLTE section, and people could see quickly if VoLTE worked in their region, on a specific phone, or not.

One last suggestion: Somewhere on every device page, there should be a list of supported cellular bands.
When people search online for phones that run UT, some phones show up listed as running well, but that is only for certain countries, because the phone lack cellular bands required in other countries.

Mario.CH

Hi @oldbutndy,

I'm sorry to have to say this, but your expectations are pretty high, considering that UT OS isn't sold but is based on donations.
Anyone who uses free software should really be more modest, especially since so many people aren't willing to make a donation because the software usually doesn't yet meet all their hoped-for requirements.
That's my view, regardless of whether your concerns are justified or not.

Greetings
Mario

Translated with DeepL.com (free version)

Moem

@oldbutndy said:

Since you are working on the whole group, could you add WiFi Calling to every device page ?

That's a change to the structure of the page itself. @sm-xcx is working on the contents of the page, which is a different thing. I'm not saying that your idea is bad, it's simply outside the scope of what they are doing.

sm-xcx

@oldbutndy As @moem said I am only working within the given guidelines and scopes of the syntaxes used by the website. I'm merely updating the pre existing information so that it's more accurate. I cannot add entries myself that's a feature request for the website itself. I do like the ideas tho and I do think the execution of them is quite easy but also tedious. It's something I'll look into once I'm done doing things that need fixing first. We can't keep adding more stuff when the current stuff still needs fixing

Mario.CH

Hi everyone,

Sorry to all the readers of my off-the-cuff post above—it turned out a bit harsh again.

All the information on the device page should be as accurate as possible, meaning it should have been tested.
Therefore, it’s better to have outdated but correct information than information that’s up to date but based on a single tester’s experience.

I feel the need to highlight the amount of work involved in creating something that’s “nice to have.”

First, there’s the OS: It’s maintained by the core developers. They have to ensure it runs on the current Android Hallium versions of the various ported devices.
The developers (all 5 or 9 of them—well, I don’t know exactly how many we have) must have a device running an Android version that we support.

The device ports: These are maintained by the porters and must be adapted; for example, to support the G4 wireless system or VoLTE.
Every porter is required to have such a device, and they probably only have one or two SIM cards to test.

Mobile carriers offer a network that, while standardized, is still not uniform. So, roughly speaking: 193 countries times at least 3 carriers equals 579 networks. Well, many of them are probably similar, so the number is too high, but clarifying this is still very time-consuming, isn’t it?

Please correct me if I’m wrong; this isn’t based on in-depth research. I’m just concerned about the amount of work involved.

Greetings
Mario

Translated with DeepL.com (free version)

oldbutndy

@Moem said:

@oldbutndy said:

Since you are working on the whole group, could you add WiFi Calling to every device page ?

That's a change to the structure of the page itself. @sm-xcx is working on the contents of the page, which is a different thing. I'm not saying that your idea is bad, it's simply outside the scope of what they are doing.

Ahh.
Previously, someone was recently able to clarify functionality of VoLTE for devices, by adding info to pages.
I thought that adding the functionality of WiFi calling next to that might be possible.

When I first was learning about this, it was not clear that just because VoLTE calling worked, did NOT mean WiFi calling would work.
Since I spent huge time, and $100 on a PHONE, to make primarily VOICE calls, and also send TXT messages, and rarely search online, or maybe take a picture, it turns out, at this point in time, to be a failed effort.
I already owned a better phone - P 4XL, running LineageOS 23 & capable of WiFi calls.
I thought I would buy a phone specifically to run UT, and replace the 4XL, and possibly add occasional Desktop Convergence (4XL can't do that).
It might be possible to do this in the future, but from what I can tell, not today, and maybe not for 6 more months (if then). [actually, I could spend $300 on a cell boost amplifier. NOT cost effective !]
My suggestions were made to help others NOT waste time and money, if their need was to have a phone to make voice calls today, especially where cellular was not working well.

oldbutndy

@Mario.CH said:

I feel the need to highlight the amount of work involved in creating something that’s “nice to have.”

Hi Mario,
I understand (from an AI search) that porting a device can often take 300 hours of time, working part time, over a period of many months. And developers work for free.

My point here is the latter half of your sentence quoted above.

Trying not to be harsh here either, but ...
We are all talking about cellular phones here.
The thing that differentiates a pocket computer from a cellular phone is the ability to make VOICE calls.
IF the device CANNOT make voice calls then it should be called 'Pocket Computer', and not cellular phone.
Since other phones I have (iPhone and Pixels) CAN make voice calls using VoLTE, and when cell service is weak, Voice calls over WiFi, it would seem to be a CORE functionality, NOT a 'nice to have'.
If a device can't do something that is core functionality, it seems that should be very clearly stated.