Well, I'm glad you have a fix, but it sure sounds painful. Wish someone had been able to find a simpler way. Hopefully this thread at least helps others with similar issues.

@Talkless OK so I've changed to download updates no only on WiFI, but always. After that I've got list of chanels, and got the update. I guess there's a bug with "WiFi" "detection" in Volla Phone X?

@Enrico13011978 me too you have to downgrade

Hi @Andrej1299 Telegram will ask on the new device to register with your phone number. Then it will send a code that you'll have to enter. So as Bolly said, it's best to set your new phone first. What I do is set everything using WIFI, install the app and configure everything. Create a backup or transfer data to your new device (if they both run Focal) Then when everything is working on the new device, I switch SIM on a weekend, so I have time to mess things around if the mobile network does not work out of the box. Test everything out and you should be golden.

Hi @gemini What @Keneda tried to explain is that if you are looking to test this kind of things on a FP5 then you'll probably be disappointed. The FP5 port is very fresh and needs testing for the basics first and then more advanced features. If it applies to another device then fair enough but you original post was misleading. So check out @ikoz 's answer.

I finally managed to make a video call with Ubuntu Touch ! :face_with_tongue: With the excellent app Webber (here), i created very easyly a webapp that's run Wire (here), a Skype alternative. It's work very well ! Enjoy !

@arubislander I don't see how. There is a lot of mixing up of how Lenovo names it's device and you shouldn't go on just M10 2nd gen or M10 3rd gen, but on the actual model number which starts with TB - for tablet or YT for Yoga Tablet. As we are well aware of the two installer supported devices are the 3Gb/32Gb Tab-X605F or Tab-X605L. The Android firmware should be interchangeable between the two, however I wouldn't recommend losing your SIM slot (for mobile data) by flashing the F version of the firmware. Likewise as I have found out it is quite easy to soft brick the device without using Lenovo's recovery tool. Likewise the other M10 tablet on the installer is the TB-X306F 4Gb/64Gb version. The LTE version is the TB-X306X. These are also 2nd Gen tablets. Again the firmware should technically be interchangeable, but I again would avoid if I can for obvious reasons. Both of these tablets are 2nd gen. Annoyingly so is the TB-X606F and the TB-606X..... Would I swap the devices Android round between the three. No. The TB-306 and TB-606 are Mediatek and the TB-605 are Qualcomm. The screen sizes are different which gives a different resolution. Of course Lenovo made life difficult by stopping official Android versions as well, which we know the correct Android version is required for UT to install correctly. The 306 and 606 have basically the same battery which differs from the 605's battery and from experience lets say swapping the battery from a OP3 and OP3T or OP6 and OP6T resulted in a kernel panic. And, just to throw a spanner into the works the 605 tablets are a pig to boot from cold or a reboot (so I guess there is a hardware issue that Lenovo patched so Android would flawlessly boot, most likely related to the battery offline charging, but that is a guess) whereas the 306 has always booted with no issue. I digress as there is no version called X306L, that would be the X306X. See upgrade matrix

@MrT10001 yes Well I installed the app then let it install the kernel mods and then rebooted. Everything seems fine but as if the gui or some download process doesnt work. Not the installation itself.

Update: verified the camera works fine on waydroid so probably some specific config related to libertine

@Fish That's great, I'm so glad i could help!

@padraic Definitely not my work. Anyway, you can check GitLab to see who worked on this: https://gitlab.com/debclick/uFirefox

@hejaali You don't need to. Boot into the bootloader (fastboot mode), i.e power off the decvice, wait a few seconds and then press and hold volume down and press the power button, release power button when device starts. Start up the UT installer, plug the phone into the PC and manually select the device from the drop down menu box.

Hi, As suggested by @Fuseteam, I disabled data connection and I did a new test (still without BatterySaver app): Wi-Fi on, data off : 38 hours of battery lifetime Same as Wi-Fi on and data on. It seems that the data connection is not used while Wi-Fi is on.

@MrT10001 That driver did not work, however, after looking through drivers I was able to select from the list, the "Remote NDIS Compatible Device" worked.

Also note that nowadays ext4 filesystem natively supports per-directory encryption which may allow a more efficient and better integrated way to encrypt /home. replying to myself: this is called filesystem-based encryption. Here is the relevant documentation for the part living inside the Linux kernel. Appears that Android nowadays also uses this for providing user-data encryption (albeit with a different user-space tooling). As this allows very fine-grained encryption of specific directories only, it may be easier to integrate with LightDM, i.e. maybe not requiring a full restart of LightDM after unlocking just some of the more privacy-relevant directories. Both recent LUKS versions and fscrypt userspace can process the disk encryption password via Argon 2. If you choose sufficiently CPU-intensive parameters for Argon 2 (e.g. multi-second execution time, 4 CPU threads, 512 MB of RAM), then even a password with 40 bits of entropy will be very costly to break using a GPU based brute-force atttack. If one believes the (pretty outdated) claims on the argon2-gpu gitlab page, then the Argon2 settings that I use with LUKS on my Volla22: PBKDF: argon2id Time cost: 12 Memory: 500000 Threads: 4 only allow for roughly 8 password attempts per seconds when brute-forcing on a NVIDIA Tesla K20X. That's only 2^28 password attempts per year and GPU!? Note that Argon2 support in LUKS is not available on the older 16.04 version of UBports, you need 20.04 (focal).

You can install what you want on any UT device if you make its file system read/write. But if you do that, which is not a supported way using UT, you'll be then the only one to deal with any issue, including breaking the system, you could encounter. AND you'll no longer should make OTA updates as it will overwrite some or all of the customisations you made, with a result depending on which parts where modded (from system bug to device not booting anymore). If you really want to mess with your UT, search the forum how you can make the system read/write. There is also a telegram group for people like you that are not feared "breaking" UT.