@Blackbomber said: @kugiigi Would an older UT version be possible? Like @kugiigi said it could be. But then you would have deprecated OS with most apps deprecated and non fonctionnal, both from install and openstore.

@gpatel-fr said: I don't know what this could mean for Volla phones. Neither do I -- I just created a support ticket with them that includes all the troubleshooting info I have. We'll see...

@nbdynl definaly not very good noticed I coude not fullscreen but I was able to play vidios from trending page which worked well apart from being able to fullscreen Mby with a wireless keyboard an mouse But very unpratical to use wireless keyboard on a phone

@nomadster Atleast it is good to know the porter is pretty active, and i have seen some news on possible solutions for the current issues they are facing with the root sizing issues... so fingers crossed that they can fix it, once they are able to ... there is some promising updates on the horizon If you find difficulties installing and configurating the "hacks" or "tuning" mentioned by @keneda, dont hesitate to ask! oh and welcome!

The behaviour of the Quintus seems related to this Gitlab issue: Bluetooth sometimes in a state where not all paired devices are listed and can be connected

@Privacy-freedom not that i know of but i have been doing a lot of things on my daily driver including installing/compiling stuff (natively) so its possible i changed some setting somewhere a year ago that fixed it for me, altough its possible the problem is your install.

@dl8aax This should be possible through python with fpdf and use this python inside your qml app.

@ubuntushop said: Why not just fix the problem.? You mean instantly ? How could that happens ? This sure will be fixed, but be patient, this is not a trivial task to maintain and fix such an OS with so few Devs involved...

For info, just installed it on OP3... Made sure the device was on Oxygen OS 9.0.6. unlocked the bootloader Booted to fastboot - then booted TWRP 3.7.0_9 Formatted DATA Wiped Cache, Dalvik/Cache, Storage and System Rebooted to Bootloader (fastboot mode) Used Installer 0.11.2 to test and started the install - device got picked up, no need to select Left "wipe data" unticked Followed instructions and UT installed as expected (Xenial).

@Linus67 Thanks very much. Will try it out…

@gpatel-fr That´s perfect! Thank you very much for solving this stubborn problem. Now I can put the Pixel 3a into ‘Nokia 3210 mode’ with a single click. Calls and text messages work, and the battery lasts at least three days in this mode. #!/bin/bash # ==================================================================== # NOKIA 3210 MODUS: CPU throttling + All offline services (Pixel 3a) # ==================================================================== if [ "$EUID" -ne 0 ]; then echo "ERROR: Please run the script using: sudo $0" exit 1 fi echo "Enable Nokia 3210 mode..." # 1. Force CPU cores into power-saving mode for governor in /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor; do if [ -f "$governor" ]; then echo "powersave" > "$governor" fi done echo "[✓] CPU throttling enabled." # 2. Turn off Wi-Fi nmcli radio wifi off echo "[✓] Wi-Fi disabled." # 3. Turn off location tracking (GPS) sudo dbus-send --system --type=method_call --print-reply --dest=com.lomiri.location.Service /com/lomiri/location/Service org.freedesktop.DBus.Properties.Set string:com.lomiri.location.Service string:IsOnline variant:boolean:false echo "[✓] Location tracking disabled." # 4. Turn off Bluetooth rfkill block bluetooth echo "[✓] Bluetooth disabled." # 5. Turn off mobile data sudo -u phablet DBUS_SESSION_BUS_ADDRESS="unix:path=/run/user/32011/bus" dbus-send --session --type=method_call --print-reply --dest=com.lomiri.connectivity1 /com/lomiri/connectivity1/Private org.freedesktop.DBus.Properties.Set string:com.lomiri.connectivity1.Private string:MobileDataEnabled variant:boolean:false echo "[✓] Mobile data disabled." # 6. Greenline-Service stop at user level XDG_RUNTIME_DIR=/run/user/32011 sudo -u phablet systemctl --user stop greenline.service 2>/dev/null echo "[✓] greenline.service stopped." echo "------------------------------------------------" echo "Success! CPU, wireless modules and GPS are in sleep mode." sleep 3

@linl OK, it seems there are problems, meaning restrictions from maybe your country (or maybe USA, or both, I don't know where the download servers are hosted), that can prevent installer to download properly. Another topic is already opened about this problem. https://forums.ubports.com/topic/12174/mirrors-for-users-in-russia/21?page=2 I'll merge yours with it. Please be patient, the issue is already known, but UBPorts team don't have much ressources (in any kind) to react like gafams can (but may not), and this may need a new version of installer, servers, mirrors, or whatever. Feel free to read thread and continue here, and maybe go to the russian telegram UBPorts help channel mentioned in previous post.

@Vlad-Nirky No, the quota limit is the number of unlocking request per day that Xiaomi approves. I read somewhere that it was set to 2000 requests per day. It seems that millions of people are waiting till midnight in Beijing, because the limit is reached instantaneously. However, according to what is written in the Xiaomi community app this procedure, and hence the limit, is for devices running HyperOS. In my case I am running MIUI12. EDIT: I read contradictory info about the number of devices one can unlock, but this is the first and only one I want to unlock.

@nbdynl said: @trunghieu1710, out of curiousity, why would you want to have any os installed without a functioning screen? Where I live, they use a number of Samsung devices, including the Samsung S7. They use them in large quantities, around several hundred thousand, to run fake advertisements and obtain promotional codes.These phones have been modified to receive power directly and remove the screen, controlling everything entirely via ADB. I can buy them very cheaply and I want to take advantage of that.

@systemmaniac2010 said: I have reached out to the telegram group and a member going by the username Pavel Glad you found support.

@kugiigi clickable works fine on UT now. Install clickable snap and docker snap connect some.slots and you're off to the races.

@Moem thank you so much, it is very new, I created it, I wish you best of luck as well

I only had this issue start when moving from stable 1.2 to 1.3

@gpatel-fr Oh, wow, I would have never thought of checking after a restart... Let me just link that here: https://forums.ubports.com/topic/12289/changing-message-sound-requires-restart

@MrT10001 Getting stock Android 11 onto the Lenovo Tab was a real challenge yesterday. Problems: SPflashtool failed due to chip permissions. Attempts using MTK bypass tools also failed How it filaly worked (after ~3 houres) Download Lenovo Software Fix Tool (thanks for the tip) Create a Lenovo account (using a disposable email address) Start the recovery workaround (but you can only flash up to Android 10 !!!!) OK, perform a recovery with Android 10 The recovery tool downloads the ROM (A 11) to your PC Before starting the recovery, you must replace the downloaded Android 10 files with the Android 11 files witch you downloaded from the UBports link bevor. Then start the recovery process and the Lenovo Software Fix Tool will flash the tablet with Android 11, which you’ve placed in its nest, just like a cuckoo’s egg. Translated with DeepL.com (free version)