EDIT : so I've tried, and as both Yalp and Aurora crash at startup (for another similar app needed in another area in my country [it is not a joke]), and as the APK file for the app is no longer findable, I can't try to use it. So that's the end of it, I'll say I can't download it and it won't' be a lie. I'll mark this thread as solved, even though it is not in the way it should have been in the beginning.

Which device do you have? If it's Nexus 5, you shouldn't install the patched kernel anymore as it's already installed by default. You just need to install anbox via apt.

Developer follow up: https://github.com/ubports/telepathy-ofono/pull/17

@lduboeuf . Thank you very much for your hint.

pm sent.

I think that phone numbers are the only sensitive data yes. Not sure the logs are still useful.

Regarding Firefox - we would need Mozilla to build a mobile version for UT, or to have someone code a fork for one - otherwise you can already install desktop Firefox on UT devices via a Libertine container - some info on that here - https://forums.ubports.com/topic/3774/where-is-firefox/15?_=1603043940011 - but the performance and interface on it will be slower and more clunky relative to the native Morph browser. Regarding "built in mail app" - there is already a very good UT native email client being maintained available for install in the Open Store - https://open-store.io/app/dekko2.dekkoproject Dekko2 is coded and maintained by a team that is separate from the UT core developers - so it is not by default included in the OS. Also - many people do not use email clients these days, or prefer to use web based clients - so the app is not included with the UT OS image by default, in order to keep the image smaller, and with less things that might not get used by all users. Best regards, Steve Berson

@mawil1013 sounds like a hardware problem to me.

@rocket2nfinity said in Recover files while stuck in bootloop?: @Vistaus If you can boot TWRP, you can back it up to an SD or pull it that way. But, only if there isn't anything wrong with memory/emmc. That turned out to be the solution! Thank you so, so much!

@Tellina UT: 2020-10-14/2, channel: dev Hello, to whom it may concern. UT on VollaPhone has been improved a lot. :beaming_face_with_smiling_eyes: Following issues are fixed now: Carrier registration failing during booting device. Carrier registration not reestablished after loosing the network connection, e.g. in tunnel, basement etc. . Carrier registration failing abroad without reboot. Data connection abroad is still not possible, but under investigation. List of open issues can be found here: https://github.com/HelloVolla/ubuntu-touch-beta-tests/issues Due to this I will change the title. Have a nice day. Cheers, T.

I've investigated it last night. The chat in question contained some longish posts (forwarded mails) and rendering this made TELEports block for around 20 seconds. I deleted them and all was fine. I now resent 100 lines of /etc/services file and it blocks again. The older unsupported telegram app has no problem and no delay showing the 100 lines. There must be a problem or bug in TELEports or in the infrastructure to render text to the GUI. matthias

@peey Yes it's safer to try it out an tinker if you have and old phone. See if you like it, if you have everything you really need before taking the leap. I didn't take the cautious path, I jumped right to it, but I knew that I needed very few to be happy. I realized I missed an app for my domoticz server so I created the app. Now I'm good, videochat would be icing on the cake...

Can you provide insight on the connection parameters, its probably Enterprise WPA2 and needs a specific setup. Unfortunately Ubuntu Touch cannot detect which login parameters are needed. Probably try Authentication PEAP, inner auth MSCHAPv2, leave all other fields default except username and password.

@PhoenixLandPirat Thanks, i wasn't quite sure

@velo27 BT calling on Meizu Pro 5 never worked correctly. Not even back on Canonical 15.04 Vivid build. There were numerous bugs reported regarding this, but no one seems to be able fix it until now. I heard that on Oneplus One is BT calling working correctly at the moment, don't know about other devices. Would be great, if people share their experiences with BT calling. Fingers crossed for someone to be able to fix this issue on UT.

@James-T Hmm... thats quite interessting: I ve got the same two issues on my Nexus 4 for months (running OTA-12). Gonna download an painting-app - we will see...

@potet Thank you. I realise all that but I could not get it to work. Eventually I found the problem to be that I was swiping up from the bottom edge of the visible display, when what I needed to do was swipe up from the bottom of the glass which is over half an inch further down. All's well that ends well.

@poVoq Possible, use copy paste feature to overcome this bug

Upgrade the installer and install the phone again, there was a problem with the installer.