@AppLee said in Flight Mode does not work reliably on my Google Pixel 3a XL:

my provider sends an SMS on missed calls without voicemai.

Yes, mine does too - and I sometimes receive the SMS notification when I'm in flight mode lol.

Occasionally when flight mode is enabled, I can still receive a phone call. However, after a few seconds, the call is cut off, and I have to disable flight mode to call back.

I also receive text messages sometimes in flight mode.

Just wondering if anyone else has had this issue. If not, it's ok. My UT installation is very old. I even upgraded from Xenial back in the day instead of doing a clean install. It's always worked just fine, except for this one weird bug. If it's just my device/installation, I can do a fresh install.

I would like to contribute to the documentation and have a few questions.

• There are a number of open issues in the Github repo for the documentation. If there are no objections, I would suggest beginning with these: evaluating them to see if they are still relevant, closing the ones that are not immediately, and making updates / creating new content for the ones that still are. Who would be the right person to coordinate with, i.e. who is in charge of the documentation?
• The move from UT 16.04 to 20.04 may have rendered some sections of the existing documentation outdated. Will UT 16.04 continue to exist alongside UT 20.04? If so, might it be a good idea to preserve the existing documentation as it is, create a copy, and update the copy / create new content to reflect the current functionality of UT 20.04?

@Moem said in How to sign up to telegram on ut?:

Wow, that's suboptimal. It used to be, you only needed a phone that could receive an SMS to verify your phone number. I guess those days are over.

I tried that several times at first, but it never worked. I also contacted support, but they never responded. On the bright side, the process isn't too bad:

1. Insert your SIM card into any Android or iOS phone that has the Telegram app installed
2. If someone else is already logged in on the phone, log them out
3. Create and verify your account on the phone
4. While still logged in on the phone, initiate login process on any Telegram desktop app
5. Use logged in account on phone to verify login attempt from desktop app (QR code, verification code via Telegram message)
6. Log out on the phone, remove your SIM card, put other person's SIM card back in, etc.
7. Done. As long as you always have at least one active, valid session on any device, you can use it to verify other devices and never need the phone again.

This is correct. The Telegram servers see Teleports as a desktop app, not a mobile app. Telegram does not allow you to create an account using only a desktop app.

To create a Telegram account, you must first install the app on either iOS or Android and create your account there. I used my wife's old iPhone for this purpose.

@kristatos said in Few thoughts regarding coming back after several years:

I don't understand why people want to change from iOS/Android to UT but on the other hand still want to use all their services. In my opinion one effort of UT is, that you don't have to use accounts and services from these big companies and still have a functional and free phone in your hand.

I agree. Big Tech surveils you 24/7, exploits your most private data, and tries to control what information you have access to. I am so not down for that. If the only choice was Apple or Android, I would not have a smart phone.

I like UT for two reasons: It's not Google and it's not Apple. Oh, and it works. That makes three reasons.

@Darkice I had similar problems when I updated to 20.04 via OTA. The good news is, I didn't have to completely reinstall UT to solve them. The bad news is, I did have to do a reset, which (as far as I can tell) deletes all apps, settings and personal data.

But maybe someone else knows of a smarter way to do it with less data loss.

Just one more question: The README.md also says "Please make sure that you're in the right place".

That page, which was also part of the wiki, was a list of bug trackers for different purposes. Here is a snapshot of the page:

https://web.archive.org/web/20170622144801/https://wiki.ubports.com/wiki/UBports-Bug-Trackers

I didn't find anything similar in the current documentation, but I think such a list is quite useful. If it does not yet exist, then since the logical place to (re)create it would be the documentation site, and since it would take a while to create it and get it merged, I would suggest creating a short, temporary list directly in the README.md file. If you have time, please have a look at my proposed changes here: https://github.com/RayCulp/ubports.com/tree/master

If it seems like I'm a little unsure of myself, that's because I am. Up till now I've only ever used Github to host my own private repos. I've never actually created a single pull request.

@arubislander said in Github repo for main website source?:

The readme is in a GitHub repo, so you don't need special access. Fork the repo to your own account, make the necessary changes in your fork. And then propose the changes back as a PR (Github) or MR (Gitlab) to the main repo.

Very true, didn't think of that.

@arubislander said in Github repo for main website source?:

Lastly, bug someone

Yeah... I'm not so sure about that part.

@prophanetes said in Github repo for main website source?:

My suspicion is that wiki.ubports is dead, and is replaced by docs.ubports.com, though there is still the occasional dead link.
https://docs.ubports.com/en/latest/contribute/bugreporting.html is not quite a perfect replacement, but contains some guidelines about halfway down the page.

Ok, is there a way we could determine that for sure? Then I could go ahead and edit the readme.md file and have it point to https://docs.ubports.com/en/latest/contribute/bugreporting.html. Who would I need to talk to for access/permission.

I was just browsing the documentation and I found some info on repo2.ubports.com, so I decided to check it out. If you just copy/paste the name of the server (without "https://") you get an unencrypted connection. SSL is enabled, and navigating to https://repo2.ubports.com/ gives you an encrypted connection. I think a permanent redirect http > https might be good.

@lduboeuf Thanks for that info.

@all Just wondering, the README.md says I should check https://wiki.ubports.com/wiki/Writing-a-Good-Bug-Report for hints on how to write a good bug report, but that site is currently down. Does anyone know if this is temporary?

@arubislander So, here's a user story (I'm role-playing here, not asking for myself): As a user, I'd like to buy a device that has the highest likelihood of receiving updates for at least the next five years. Is there a recommendation?

@arubislander said in Devices discontinued?:

less intractable

Ok, makes sense.

Is the website source hosted in a Github repo someplace (like the source of the documentation site https://docs.ubports.com)? I was looking through the issues at https://github.com/ubports/docs.ubports.com/issues, and I see somebody opened an issue for a problem with the form at https://ubports.com/join-us. I'm not 100% sure, but I don't think that's the right place for that issue.

@arubislander said in Devices discontinued?:

For some devices a port is commissioned and/or sponsored by the vendors. This is the case with the Volla phones and the Fairphone 4.
For other devices it is much more the case of, someone with that device and the know-how wanting to see UT on running on it.

Ok, but then it seems counterintuitive that the Google Pixel 3a is at 100% completion while none of the Volla phones are 100%. Why is this? I mean, they're close, but still.

@BarryT said in How to access data on phone with broken screen?:

The cost of a replacement screen is much higher than a replacement phone (second hand) so I have not considered it.

If you're able to rescue your data successfully and are not planning to replace the screen, please contact me via pm before you throw it away. I might be interested in it.

@Moem said in Devices discontinued?:

If anyone abandons the Nexus 5, or any other device, that's the port maintainer, not the UBports devs

I'm wondering, is there one device at any given time that is always guaranteed to be compatible with UT? Something like a reference device. Or is UT developed completely separate from any particular device, and then ported independently by individual port maintainers?

Here's a frightening thought: Are there any situations where fiddling around with unsupported stuff might brick the phone so badly that you can't even re-install from scratch? oO