@AdFundum did you find a command that works from the terminal/adb shell? If so, does that command work if you make your app unconfined?

Its possible that UT does not have an app armor policy that fits your use case, and that's the cause of your problem. From the list of policy groups I cannot see anything that would allow a confined app to change the background image.

https://docs.ubports.com/no/latest/appdev/platform/apparmor.html

@mihael noted!

Btw there's a new release: https://github.com/brennoflavio/greenline/releases

If you didn't disconnected your Whatsapp account in the last update, please take time to do it. Takes a few minutes and will improve your experience with the app.

Changes:

• Now links inside text are clickable and will open the browser
• Mentions are also treated as links, clicking on them open the messages
• Text between stars are rendered as bold message, like in Whatsapp
• Now sending a message while offline does not crash the app anymore
• Daemon should be way faster to reconnect when going back from offline to online or switching networks
• Fix bug when clearing data app not deleting all files

@Zer0 Nice iniciative, to me there is some nice ideas in your effort, will try in a spare phone in the near future. Its always good to have options, design choices should evolve and enable users to use their device as they wish.

I would suggest having your work as an unconfined click app, so you can reach more users. There are other launchers and apps that modify Lomiri so should be doable.

Thanks for your work

@gpatel-fr I'm talking about the title, that an app has no API to set an action when clicking on the notification bubble.

I think your example shows that, as it is not using the official lomiri api for this. So it doesn't work with an http post to the push server for example.

There's a new release for this app. This release contains a big standardization / internal refactor. I highly recommend that you:

• Logout from the app in your main Whatsapp device
• In Greenline settings, reset the app
• Install the update
• Then login again

If you don't disconnect, there's a high chance that the app will crash in some places. As we approach to a beta release, I added more safeguards to catch bugs and make the app more robust, fixing some bugs on the way. Hopefully this will be the last time this will be needed, as from now on I'll adopt a data migration system for changes.

https://github.com/brennoflavio/greenline/releases

Changes:

• Allow sending documents
• Add option to catch and report crashes
• Add option to pause daemon when closing the app
• Render Whatsapp text messages with buttons
• Fix images rotating in chat page
• Restore old behavior for unread count bubble in app drawer
• Handle Group Information and other whatsmeow events
• Remove daemon configuration database, centralize all configuration in python
• Harden media download, prevent crashes when downloading unavailable media
• Reorganize code into modules, better separation of concerns
• Add tests for daemon <> python communication and python <> qml communication
• Document and test all python interfaces, with real, sanitized Whatsmeow data
• App now validates at build and at runtime all data structures, logs errors, and ensures consistency between app parts

Its definitely a Lomiri UI inconsistency, not an app issue. From apps perspective, there's no way to tweak this behavior. And there's no difference between an app using dbus or the http apis to send notifications, they end up flowing over the same path in your device.

@ChromiumOS-Guy please keep the discussion on feedback and suggestions, avoiding giving orders or similar statements.

The way you put it is a bit rude for my taste. It does not sound intentional, but with a bit of out of context to me. Its not that the app is being developed without a data model in mind, more like new requirements (replies, edits, new message types, etc.) requires rethink on how things are done, which is pretty common on any medium o higher complexity project.

@Vlad-Nirky Its not an impression, the app is inefficient in its current state, optimizations are needed. The perception will vary depending on the amount of whatsapp data you receive. Its a combination of having the backend written in python (which means that on receiving new events, a python process is created to process it on the fly) and the qml frontend re-rendering on each event that emits a qml update. So for example receiving a new chat means re-rendering the whole chat list.

Not too worried about it yet, but something for me to look in the future. I'm not 100% decided on how this app will manage its data so not gonna waste time optimizing something that might change. Probably will get back to this once the app support all possible Whatsapp events / message types, which will give clarity on how to model everything.

Thanks you all, keep feedback coming, it helps a lot. No problem to report usability / polish issues aswell.

@nbdynl yeah broke that a while ago, still not 100% correct as muted chats still counts but at least consistent now.

There's a new release for this app. I recommend disconnecting an connecting Whatsapp after installing this update using the settings since there was some rework on how messages are represented, which can lead to old glitched messages. Since its an alpha, I'm not guaranteeing consistency on each update:

https://github.com/brennoflavio/greenline/releases

• Better offline mode: now if the app has no connection, messages are queued to be sent once connection is back
• Optimizations for rooms that had a lot of replied messages, should load faster now
• Now the pending / sent / delivered / read icons matches closely with whatsapp
• Better handling when whatsapp servers are unavailable, avoiding app crashes
• Better media previews: now you can zoom in / out images, its easier to pause / reproduce videos, and better look and feel
• Fixed a bug where if the person used whatsapp on two devices (like web and app), its chat appeared duplicated and in groups the profile picture did not appear when the message was sent from the second device
• Prevent app crash when trying to download media while offline

@developerbayman your point just suggests that we need better confinement, not to remove it. For example, the alarm app could have apis to run confined

Just pushed a new release for this app:

• Better image and video controls. Pinch to zoom, double tap, and other gestures. (thanks @kugiigi , heavily inspired in your commit for the gallery app)
• Upgrade some libraries
• Don't crash the person list page if a person does not have a thumbnail
• Support servers with subpaths (like https://example.com/immich)
• Give a better error to the user if app cannot connect to Immich on login

@ChromiumOS-Guy contributions are welcome! But support for all message types is planned before going beta

@pparent No plans for a confined version, mainly due to the burden of mantaining two versions of the same app. The best move here is to work with UT devs for proper support of backgroud services for click packages, so this app can run confined as is.

Support for pausing the daemon when app closes is planned tho, which achieves the same result I think.

@Linus67 The chat list is the source of truth for contact information, there's no separate list of contacts in this app. This makes the code easier to undersand and with fewer moving parts, but the tradeoff is that to render the person name in the group it needs to exist as a individual in the list, so removing chats is not possible.

This is unlikely to change, would add a complexity I don't want to manage. However I do plan to add basic filtering in the list, similar to how Teleports works, which should mitigate this.

Thanks for the feedback you all, any issues please report.

We have a new release: https://github.com/brennoflavio/greenline/releases

• Experimental support to record voice messages. Give it a try and report if it works for you
• Support for messages with images and buttons
• New icon and splash screen
• Support for deleted messages, both seeing deleted messages and deleting your own messages

@ChromiumOS-Guy what do you mean by seeing the message after time runs out?

@mihael the app has a built in logic to recover the daemon in case of a crash, which seems to be working here

Nice script to stop the daemon, I added to the todo list to include before release

A few bugs here and there, but a nice daily driver