@giukas I don't know :(. All I did was that I used some clean alcohol to wipe the SIM card and regarding the slot I've just looked inside if there is something visible that would cause the issue and haven't seen anything. So I just blowed some air there ... and it still wasn't ok since the contact was lost later again so what resolved the issue for me was to push the card into the slot thoroughly ... maybe I haven't had it fully inserted before ... there could have been some dust there that have prevented me to place the card correctly.

Not sure ... but be careful and try not to destroy the slot it if isn't yet :). Good luck.

PS. It could also be a SIM card issue. You may want to try another one to see if it works or try this one in a different phone.

@giukas I've recently replaced battery on mine so I had to unscrew the back cover and prior taking that off remove the sim card from the slot. I am not sure what I did wrong but I had to re-insert the card to that slot a few more times in the next few days until I am finally not experiencing more such issues.

Fortunately in my case removing the sim card, cleaning the slot as well as the card and reinserting it fixed the issue (after a few retries).

This doesn't seem like system related issue though (especially since it does work for me). You can try installing Android on your device and see if it works there, but I suspect it to be a hardware issue. If that's the case that you may want to try cleaning the slot again and if nothing helps either ask some cellphone service to repair it or purchase a new device.

TBH I am often experiencing weird OSK behaviour with Telegram Plus (TELEports). From time to time I start typing a sentence and when I am on it, having its part written already, the keyboard just hides and I can only summon it again by either waiting a bit for it to appear again (if this works it can take quite a while, even like 30 to 60 seconds) or I can close the Telegram app and restart it again to finally be able to type - for a while :).

And now I've just found out I already reported this thing I am explaining above: https://github.com/ubports/ubuntu-touch/issues/695 so in case you are experiencing that too (no matter the app) please add your comment to that report so that it can be confirmed :).

@stefano Probably the best to add the repo to your system and use it from there. Did you try that?

echo "deb http://repo.ubports.com/ bionic main" | sudo tee /etc/apt/sources.list.d/ubports.list
wget http://repo.ubports.com/keyring.gpg -O - | sudo apt-key add -

and then

apt update
apt install ubuntu-device-flash

@guru Yeah, the behaviour is different but you can still close the opened tab by clicking the cross that shows up in the app's header.

@dobey Sorry, I was pointing this specifically at Flo who probably knows what I am talking about from the Telegram dev group.

Anyway, for certain I should have made this more clear. I meant the following two issues we've bumped into:

1. "limitedBandwith" property seems to be static, not changing based on the connection type.
2. On start, "online" property is always set to false and only changes if connection actually changes. Afterwards this seem pretty much reliable but you can't get correct connection state info until you start the app and then change networks.

I am not sure how "limitedBandwith" behaved when Canonical was still developing Ubuntu Touch as I was never using this but I am pretty sure I had issues with the "online" property even at that time. Sadly I can't remember if it was this issue or something else.

Hi,
you can always Google man pages for specific things when on the go, even narrow it down by distro and its version when searching.

But it doesn't make much sense to have them installed on phones. It would just occupy precious space while being very rarely useful - especially when there are other sources available.

Hello,
I am aware that Flo is trying to get in touch with NetworkManager guys to make networking on our Ubuntu devices way better. He also mentioned it on the last call. There is also this related bug report available: https://github.com/ubports/ubuntu-touch/issues/885

My question is however as follows as I was not able to understand this at all so far:
At least Ubuntu 18.04+ has NetworkManager that supports captive portal detection and ignores interfaces with no data flow. So in case you were passing by a WiFi with captive portal or in case the signal was too bad it would simply ignore that interface and could still use mobile data.

Why is it not possible to backport a newer version of NetworkManager and see what happens?

Related to that Connectivity api: https://docs.ubuntu.com/phone/en/apps/api-qml-development/Ubuntu.Connectivity.NetworkingStatus is also in need of a redesign/rewrite as it is not fully working so when attending to NetworkManager it would be great to bind this to the possibilities of the latest network manager.

Thank you very much for shedding some more light on this topic and as always I really appreciate all the work you guys are doing!

@doniks Yeah, LTE and everything else did work for me back when I was using http://system-image.tasemnice.eu/ubuntu-touch (currently dead) repository - which was based on the original Canonical images.

The last time I had my "deb" in my hands (before I gave it away) I was trying to install Ubports on it after that original repo died and I can see that I was not able to make bluetooth and camera to work but I was hacking things on top of what was available so I guess that was the issue: https://forums.ubports.com/topic/44/installing-ubuntu-on-nexus-7-2013-deb-lte

But ... even with these workarounds LTE did work for me ... it was just a matter of having a correct "boot.img" flashed AFAIK.

Btw, it seems pretty much everything worked for you at some point as well, including Bluetooth:
https://forums.ubports.com/topic/44/installing-ubuntu-on-nexus-7-2013-deb-lte/23

Hm, "It now shows the version as Ubuntu 16.04 (2019-01-12)" that doesn't seem like a stable release to me. But it is probably because a switch from devel to stable didn't succeed.

I've bumped into this odd behaviour every time I've tried to use the system settings channel switcher - the behaviour of the system settings app is a bit odd after you trigger a release change, you can no longer see the list of channels when it is processing the change, it takes a while (depending on your Internet connection speed) and not always displays progress on the update page.

So, what I would suggest you to do until you see "OTA-7" on the about page is to reboot the device so that all possible pending operations are killed, then go to the channel switcher and switch from "devel" to "stable" (which is what you want) and then try to watch the updates screen of the setting app. Once the desired stable Ubuntu release is downloaded (it is about 500MB+ large IIRC) hit the install button.

In case there is nothing visible on the update screen of the settings app, try to exit and renter the updates screen of the setting app a few times (give it time, maybe 10 minutes) and if nothing shows up you may want to restart the device and try again the whole process from switching from devel to stable on the versions screen.

IMPORTANT: Only do the above if you still see the "2019-01-12" version format instead of "OTA-7" on the device screen, otherwise you are on stable and can ignore it all...

Good luck