I've just published version 0.1.6, that corrects the app that was broken by a change upstream in Whatsapp web; Here is the changelog of the version: Adapt to a change upstream that broke the app Improve ContentHub to Import/Export files Fix broken app on 24.04-1.x daily I've only tested the main features, I've not had the time to do a comprehensive testing before releasing the new version, but as it was broken it's always better to have something that works. If you find any new bug, or thing that does not work anymore with this new version or since change in Whatsapp web, please do not hesitate to report.

i actually had to slow the execution environment to to the hybris translation actually slowing down execution i have zero clue how this is going to play with game/emulator performance its like it was overloading lomri

@danfro said: The power button itself works. It brings up the power menu, but pressing the buttons failed. I have that now and then... But no idea what may be causing it.

@PhAndersson @gpatel-fr So the fix is in 1.3 daily. Wait 1.3 candidate to test. Thanks.

im thinking about bolting on a python ide as well so its built in ...kinda a one stop shop manage/develop/deploy

This will not be possible as a confined app. You will need a background service that listen to incoming sms and forward it. I'm not sure if such app can be allowed in the openstore, but here is a few things to know. First create your background service, it could be in standard python if you are familiar with. Ofono is the service that emit notifications when new incoming sms, it uses dbus. api can be found here: https://github.com/rilmodem/ofono/blob/master/doc/messagemanager-api.txt (old repository but sending and receiving sms still like that ) AI can help you with a minimal script. then when your service seems to work, you have to create all the plumbery to install/remove/run it, you can find an example with battery-saver app: https://gitlab.com/lduboeuf/battery-saver/

@pparent I've been experimenting for some time and, honestly saying I already don't remember which one, but there was some part of functionality which crashes with Wayland, and works well with XWayland.

@projectmoon funnely enough we had the same idea hours apart, i stopped development on my end (no need to have two apps for the same thing). thanks this is huge because now i can have push notifications for my university mail (dekko can't login to my university mail I have it forwarded to my protonmail).

No problem for devices with MTK Power Bypass. @arubislander said: Unless you don't mind your battery degrading, because the device would be constantly plugged in to the charger, you would have to device a routine for charging and discharging the device.

@gpatel-fr I can't see the difficulty. Instructions for clickable installation are the same for 8.7 version: https://clickable-ut.dev/en/latest/install.html (just use pipx command instead of pip3, as proposed also in the book)

Just as @applee, I suspect that this thread possibly discusses several different bugs. Notably, I believe the problem described in reply #3, and maybe by @kristatos are the same as the one I described in this other topic. The issue in that other topic is related to how UBports interfaces with the android gps drivers and it affects all apps using gps on all ported android phones released since around 2020, but possibly with app-dependent symptoms : freezing, crashing, or just going on with a frozen location. The good news is that the other topic's bug has a working fix which should hopefully land in an upcoming OTA.

The Indicator Upower now supports battery charging limit on MTK and other devices - don't forget to reinstall indicator if this feature didn't work in older releases.

@CiberSheep said: I can't remember, but it is still possible to define new kinds of accounts to be included in the Accounts in the system (adding to nextCloud, etc)? It should yes, i think UBsync do that, but seems confined: https://open-store.io/app/ubsync