@StephPTi Now you can see in Greenline: Meta stores all your actions on WhatsApp. If you like a comment in a group, that contact is stored in the database linked to your phone number. You can view all these records now in Greenline. You now have a complete list of the phone numbers (contacts) to which you have ever reacted or commented. This is part of the metadata that WhatsApp stores permanently on its servers: when you interacted with whom. This means that most of what you delete in WhatsApp is simply hidden. In a future version of Greenline, it may be possible to hide this ‘metadata’.

@Privacy-freedom You need to gain a bit more experience to create a .conf file properly and ensure it works as intended. Don’t forget to make copies of your working settings. AI can also be helpful.

@arubislander Thank you for the advice, it's truly appreciated.

@danfro I hadn't even paid attention to the broken sorting mode ! Perhaps this is an opportunity to implement different sorting modes internal to tedit or for tedit to conform to the sorting mode defined for Files?

@Vlad-Nirky @gpatel-fr @sander Thank you for testing & glad it works for you as well ;-). I've made a note of the radio-browser API, and I'll check.

@sysadmin Same question (more or less) Is there a way to install UT by downloading the necessary files beforehand? There are an increasing number of people living in countries (such as Russia) that block our servers and are unable to complete the installation.

On the subject of battery consumption. It is very difficult to compare battery consumption when devices are being used simultaneously. I only test and compare battery consumption under identical conditions without active use (for example, at night) 7 hours in aeroplane mode 7 hours with only calls and texts active 7 hours with selected background services also active. (Selected apps, such as Dekko, or those with connections to NextCloud) Using this test method, I have not observed any increased battery consumption with RC 1.3.

@computersalat said: so sad to have a technically fine Device (my OP2) but you can't use it because of outdated OS. That is indeed sad, but let's be fair... the world is full of such devices. This is not at all a specific Ubuntu Touch problem. On Android, this device was outdated a long time ago.

Ah, no. I don't think it's possible to pass an url + the appid link. The idea is to open the app...

@tidip said: Still interesting to know that these 2 are not affecting us too much. This is not what I wrote. You could replace 'are' by 'may'. It depends on the specific device. I provided the means of testing these exploits to allow people to test themselves.

@domubpkm To stop the script: sudo pkill backup-ip.sh It's true that I've not taken into account the case where LTE is activated, but mobile data is disabled.

@shcarl276 said: It's not the matter of the devs not being ABLE to do something. Sorry, but I disagree. This is not on the dev's plate.

Updated the original post with new links, as I have added a tutorial, per Vladimir's great suggestion. [image: 1779060430118-tutorial.png]

@Moem Yes, I thought so too, and it matches the description in the wiki. https://wiki.ubuntuusers.de/Ubuntu_Touch/UT_Tweak_Tool/ In my tests, however, the opposite was true. There might be another reason for this. I’ll repeat the test with different scenarios and log the power consumption in sleep mode. -10 hours of standby (all apps with background suspension) -10 hours of standby (all apps without background suspension) In any case, battery consumption in standby mode (accessible only via phone calls and text messages + alarm clock function) can be reduced to a minimum. It feels like a Nokia 3210 with up to 260 hours of battery life, with the difference that modern smartphone features are available at all times.

@Peyo il est possible qu'il s'agisse d'un problème de focus. Avec mon Fairphone 5 j'ai eu longtemps des soucis sur les photos à faible distance (à peu près moins de 50cm) qui étaient toutes floues, j'ai utilisé le truc de basculer en mode caméra puis revenir en mode photo, mais une manoeuvre plus simple est de tapoter un peu l'écran ce qui indique au logiciel d'esssayer d'améliorer le focus. L'appareil photo sous Waydroid n'a pas ce souci sur le même matériel, le focus est correct immédiatement à toute distance.

@developerbayman said: simple question really ...do we really need app confinement?? Yes @developerbayman said: ...but like everyone including myself is making unconfined apps because xyz does not work Only a few developers are unconfining their apps because they don't want to follow the OS way of doing things. Last time I got a «ContentHub?, No!».

@lduboeuf aaaah, true. I thought Notes was unconfined... (I thought all core apps would be), but it seems not to (apparmor) It also needs to specify an account-qml-plugin that I think is how the app (Notes in this case) authorize the provider: https://gitlab.com/ubports/development/apps/lomiri-notes-app/-/blob/main/manifest.json.in?ref_type=heads#L15 the qml file is: https://gitlab.com/ubports/development/apps/lomiri-notes-app/-/blob/main/src/account-plugin/qml/evernote/Main.qml.in?ref_type=heads PS: I'm still confused with the different hooks and different apparmors...

"Places" case solved. What I obeserved in short: At startup, "Places" is created and provides shortcuts to standard folders (immutable): Home, Documents, Downloads, Music, Pictures, Video, Network and Root folder. These folders can't be deleted from there (no trash can symbol). This list is expandable with any folder. These are removable, too (trash can symbol on swipe right). "Music" folder was deleted (accidently, I didn't realize at first). "Places" tried to provide a link to this non-existent folder which ended up with a ".". "Music" folder was recreated and appeared at the bottom of the "Places" list while "." still existed. After a reboot, "Places" got organized again (or rebuild by scratch). "Music" folder could be referenced again and "Places" was rebuilt as intensioned and looks normal again. No "." for a folder that could not be found. Sorry for causing this confusion and any inconvenience. It happens, when you're chronically overworked.

@hlbkv said: @gpatel-fr The installer doesn't seem to detect the device this happens to me when trying to reinstall my Fairphone 5 that works correctly both before reinstalling and after, so it's more a shortcoming of the installer than a blocker. @hlbkv said: states one should have Android 11 installed here it's more mixed unfortunately. If you had already installed 24.04-1.2 and it worked correctly (as far as the device page for this device states it) I think that you can proceed nonetheless since all that the previous Android version is leave the correct device drivers in the Android partitions, so if it worked before it should work after. A caveat is that a hardware problem could have developed on your device in this case there is not much that software can do. After all, so far you are the only person having such trouble with updating to 1.3 from 1.2. If not, it would be wise to give more details on the previous situation before going further.

antidorsessions did you have install android 13