For people running Noble (24.04) on their devices, is your device listed on devices.ubuntu-touch.io with Noble support?
-
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
MarioTranslated with DeepL.com (free version)
-
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. -
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. -
Hi @oldbutndy,
Sorry, the comment “nice to have” refers exclusively to the amount of information on the device page.
Of course, I too want phone calls to work first and foremost—which, by the way, worked flawlessly for a long time on 3G technology.My point was that users should also take the initiative to look for information themselves. This would help UBports and the community.
But here in the forum, the performance of our very small organization—including the community—is constantly being compared to that of big companies like Google, Apple, Samsung, Xiaomi, etc.
I also think that anyone who wants to break free from the tech giants and big data
shouldn’t rush headlong into the arms of AI.
But, I’m probably too old to understand that.
Greetings
Mario -
I also think that anyone who wants to break free from the tech giants and big data
shouldn’t rush headlong into the arms of AI.I am old enough to have watched 2001: Space Odyssey, Colossus: the Forbin Project, and all the Terminator movies. [those AI's were lethal but not stupid, like half the Google initial search results lately].
I would prefer NOT to use AI ...
But, when you are new to a thing (porting of UT specifically to phones, in this case), you search via any & all means necessary to gain knowledge as quickly as possible.
If that information is not so easy to find on the primary website for UT, you search wherever you can find, and try to get multiple sources.
So, when you search for phones that might run UT, and make voice calls, in a specific country, just where are you supposed to look ?
[for starters, in USA, the pixel 3A does NOT do VoLTE, the Volla or other one (can't remember) is missing bands required in USA (again NOT work), and the Nord N10 and N100 which DO work - ALL NOT clearly shown on the device page.]
and how many hours is a person supposed to spend ?
I REALLY appreciate the efforts of @sm-xcx ! (but I already spent the time and money, so that effort helps others, not me directly. Indirectly, it helps others find phone that could work, which grows this whole group, which helps all of us). -
@oldbutndy said:
I would prefer NOT to use AI ...Then don't. I never use it. I survive somehow. It's been only a very short time that these options have existed at all. Have we already forgotten how to do without them?
AI can't help with Ubuntu Touch because there is not enough information on the web for it to work with. It was made to give answers, whether or not the information exists. So it starts to make stuff up. That's not information, it just sounds like it.
and how many hours is a person supposed to spend ?
Spend fewer hours, ask more questions.
We're happy to help, give us the chance to! You're part of a community, there is no need to stumble around in the dark, come sit around the fire with us and we'll swap tales and information. -
-
Hi @oldbutndy,
Welcome to the Ubports forum—it always takes a bit of conversation to get to know each other. Unfortunately, it’s still harder to do that through text alone.
As Moem already wrote
You're part of a community, there is no need to stumble around in the dark, come sit around the fire with us and we'll swap tales and information.
Now I’m ready to sit around the campfire too, but it’s a shame it’s just text—we’re missing body language, like a smile.
So, when you search for phones that might run UT, and make voice calls, in a specific country, just where are you supposed to look ?
In our forum, under the “Devices” category, there are quite a few posts from the community.
Unfortunately, the search function isn't great—to be honest, it's pretty bad. I think a dedicated internal AI would probably be useful here.
Greetings
Mario -
In an effort to streamline information across all the sources I am working on updating device listings on the official ubuntu touch website first.
- xcx
I understand that you are specifically trying to update info for specific devices.
Are you also able to add a bullet point to the main page https://devices.ubuntu-touch.io/ ?
I ask because I read a new forum post today where the person was unable to unlock bootloader on device.
I search the main page I linked and the one for the device (Poco) the poster mentioned.
Nowhere did I see 'Bootloader', or 'unlock'.It seems to me that a Bullet Point line should be added to the 'Before Installation' section, right after 'Ensure your device is fully functional beforehand', that says something like 'PLEASE learn (ASK on forum) all you can about bootloader unlocking for your specific/desired device, before procuring device or attempting UT installation'.
I think this might help new people have a better experience with UT.
-
@Mario.CH said:
Unfortunately, the search function isn't great—to be honest, it's pretty bad. I think a dedicated internal AI would probably be useful here.
Greetings, MarioHi Mario,
a few months ago, as total newbie, I did not even know some of the questions I needed to search for or ask in forum.
So, I just read a variety of forum threads for days.
Some of what I learned was recent info, NOT yet shown on devices pages, and important enough that it should have been.
That is why I think the effort that @sm-xcx is attempting is so critically important.
Not so much for us already using UT on a device, but the entire rest of the world who might WANT to try UT.
The device page is the GATEWAY to the whole thing.
It is the ENABLER of UT growth (besides having at least 1 ported, functional device, obviously...)
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login