Yeah I agree. You don't fully grasp yet how QML works. We all had that time when we are starting especially when coming from non-declarative language You should really try reading a bit even just the basics of it. One key thing is that Javascript is used for logic within QML, ideally only for front end logic but you could also do everything with just QML and JS. For your example, you can simply add an inline conditional statement for the icon.name property. Or for more advanced use especially if you intend to add more changes, you can use States. Here's a sample one for the inline: icon.name: switch.checked ? "tick" : "close"

@Schlicki2808 futify is using this api, but seems to use deprecated api calls instead of creating another alternative client, i belive that more efficient would be to put already done frontend + backend stack into click package, In this way is already futify working, there is backend in golang that reads spotify stream and "forward it" on localhost:8765/song?id stream that is feeded to phone (which is probably the issue why futify does not show album/title/author in media navigator) this is backend side https://github.com/Spotifyd/spotifyd this is one of the clients https://github.com/xou816/spot

@CiberSheep Thank you for sharing this code with me. I've noticed that the problem seems to exist for this app too, as the developer uses a timer to start playback with a delay. I applied this in my code and it seems to work. I'll now be able to add a few features to it. Thanks again. Here's a code snippet if it helps anyone in the future. Timer interval (1500ms) to be adapted. Timer { id: playStarter interval: 1500 onTriggered: { musicPlayer.play() } } MediaPlayer { id: musicPlayer } function pause() { musicPlayer.pause(); } function play() { if (musicPlayer.source) { musicPlayer.pause(); playStarter.restart(); } }

@uxes Your idea is pretty amazing and would love to see it as an application soon. Thumbs Up...

@lduboeuf it is true... it persists but: for the josele's Focal app it still uses old framework "framework": "ubuntu-sdk-16.04.5", "policy_version": 16.04 Ah, after reboot my webapp also works, not the qml though

@lduboeuf why did you posted in the General forum and not App dev one ? sorry

@lduboeuf thanks

@lduboeuf thanks for explain $ /home/phablet/.config/systemd/user/batterysaver.service -bash: /home/phablet/.config/systemd/user/batterysaver.service: Permission denied ~$ systemctl status --user batterysaver ● batterysaver.service - Battery saver Loaded: loaded (/home/phablet/.config/systemd/user/batterysaver.service; enabled; vendor preset: enabled) Active: active (running) since Mon 2024-10-28 10:18:03 CET; 16min ago Main PID: 9322 (batterysaver) CGroup: /user.slice/user-32011.slice/user@32011.service/batterysaver.service └─9322 /home/phablet/.local/share/batterysaver.lduboeuf/batterysaver /ril_1 gsm lte false true true Oct 28 10:21:56 ubuntu-phablet batterysaver[9322]: lockStateChanged(): screenIsLocked false Oct 28 10:21:56 ubuntu-phablet batterysaver[9322]: lockStateChanged(): switching to pref tech Oct 28 10:21:56 ubuntu-phablet batterysaver[9322]: lockStateChanged(): NOW SWITCHING TO "lte" Oct 28 10:22:58 ubuntu-phablet batterysaver[9322]: lockStateChanged(): screenIsLocked true Oct 28 10:22:58 ubuntu-phablet batterysaver[9322]: lockStateChanged(): NOW SWITCHING TO "gsm" Oct 28 10:24:41 ubuntu-phablet batterysaver[9322]: lockStateChanged(): screenIsLocked false Oct 28 10:24:41 ubuntu-phablet batterysaver[9322]: lockStateChanged(): switching to pref tech Oct 28 10:24:41 ubuntu-phablet batterysaver[9322]: lockStateChanged(): NOW SWITCHING TO "lte" Oct 28 10:25:58 ubuntu-phablet batterysaver[9322]: lockStateChanged(): screenIsLocked true Oct 28 10:25:58 ubuntu-phablet batterysaver[9322]: lockStateChanged(): NOW SWITCHING TO "gsm"

omg i see why axolotl isnt getting any development love ........its a giant mess .....this may take a extremely long time .....30 years of writing software i have come to the conclusion the K.I.S.S method is really king ....axolotl does not and i repeat does not follow K.I.S.S (keep it simple silly) ....i can build it kinda so we shall see

@arubislander oh wow ....i must have lost my mind then lol .....maybe i used a vm once and totally forgot or something

@gonbuntu well that's good news in its self : issue will be handled

@naofeifei Hello and Welcome. As you have noticed, Ubuntu Touch (UT) is set up in a different way than Ubuntu on the desktop. UT has a read-only filesystem, similar to SteamOS, Fedora Silver Blue or Ubuntu Core. Because of this apt is not supported. Updates are provided via the system settings. Additional applications are installed via the Open Store. Apps for UT are bundled as click packages, or clicks for short. The regular way of developing apps for UT is on a(n Ubuntu) Linux desktop with the Clickable tool. But if for whatever reason you want to develop on your UT device, you will need set up your development environment in a container of some sort. You can try doing this in a Libertine container. There have been sucesses going this route in the past. If your device supports it, you could also enable snap support with the Snapz0r app. Then you could install the LXD snap and set up your development environment in a LXD vm or container.

@moredevelopers Hi. Here we discourage our forum users to install random clicks on their devices You say this is a big project. Is there then any reason you need external testers? Is it a lack of devices, or?

@developerbayman We are happy for your love. But I fear it might not be mutual for long if you flood the forum with your idea of what would take UT to the next level, if it means making it more like Rhino or Droidian. People can only take so much of, what becomes to them, badgering. Listen, I appreciate your enthusiasm, I truly do. But as a project we have been through this back and forth ad nauseam, if not with you, with others. And really, we have no desire of being another Droidian. If what you say is true, that opening up and becoming more "linuxy" would bring in a flood of new applications (and I would like to add the qualifier) that work as well on a small screen as on larger screens, do we already see this effect with e.g. Droidian? And even if there were an influx of apps on those platforms, such applications could theoretically be repackaged as clicks and made available for UT too. Someone just needs to want it badly enough to make it happen. Futhermore, clicks are not the issue that is 'holding the OS back', old libraries are. Many of the latest linux mobile apps require newer libraries than are available on 20.04. Updating UT to 24.04, a work that is already in progress, is a huge undertaking, and that isn't necessarily because of the peculiarities of UT that seem to trip you up the most. It is very much the Linux and Open Source way to repackage Open Source apps to 'exotic' formats, see snaps, and Nix packages. NixOS's packaging choice is not stopping it from being the current darling of the Linux hipster community. Finally I would like you to consider if it is not possible that the reason this Community is much more pleasant, in your estimation, than others for similar projects, might just be due to the way UT is set up. This OS targets a different type of user than does Droidian for instance, that makes the make up of the community different. If we became another Droidian in the software area, chances are huge, we would also become another Droidian community-wise. Then you would have also lost the one-thing you appreciate most about this project.