@ChromiumOS-Guy said:

@nbdynl before i continue, append this to camera / location and if possible networking as well.

we want a one time approval option, as well as foreground only. only system apps (like Phone app) should be eligable for background access for services microphone/camera by default, devision as follows:
only phone (the app) has background access to microphone by default
camera should not be accessible on background by default. (any app)
location should not be accessible on background by default (any app)
networking should not be accessible on background by default ,push notifications goes through a push server so not affected if im wrong this can be ammended (any non system app)

It would be nice to have an explicit permission for apps that need to run in the background all the time, even if it's something that makes it require review. There are a number of apps that only work properly when unsuspended, or by using an unconfined background daemon. Would be good to converge on a single permission for them.

I've taken the liberty of packaging Lagrange for Ubuntu Touch. Lagrange uses its own completely custom C-based UI stack built on top of SDL/OpenGL, which means that while it runs fine, the keyboard does not work out of the box on Ubuntu Touch. The UT package has a patch that 1) enables the keyboard and 2) packages it as a .click.

There are still some issues with the keyboard and integration with the system. Namely:

1. Clipboard does not work.
2. Keyboard still has some weird behavior on textboxes that aren't the URL bar. You cannot edit text in the middle of them, for example.
3. No integration with content hub.
4. No integration with URL dispatcher (i.e. cannot open gemini links in Lagrange).

I think most of these should be solvable. I will continue working on it and see what comes out.

You can find Lagrange here: https://next.open-store.io/app/fi.skyjake.lagrange/

@lduboeuf said in Call for testing: calendar-app:

@projectmoon said in Call for testing: calendar-app:

@lduboeuf So unfortunately, calendar sync is still broken. The calendar that was syncing (connection to Nextcloud via generic caldav instead of built-in Nextcloud integration) is no longer syncing. Only thing I see in Evolution logs is something about i_cal_time_compare < 0 failed.

I turned the Nextcloud integration itself back on for Calendar, and that synced fine... But I don't know if it will sync more later.

Sorry, i don't understand, you mean it works or not ? Please also precise on which OS version are you .
The sync can be sometimes unstable ( and it always has been). It is sometimes needed to recreate all accounts ( remove them all, reboot, recreate them)

Stable 1.2, and the accounts were previously already cleared and removed from Evolution. Re-re-(re?)-creating the accounts shouldn't be necessary, I would hope.

What I mean is that the Generic CalDAV Account seemed to stop syncing. But when I re-enabled the Nextcloud Account, that synced fine. I have two Online Accounts set up on the phone. Both point to my Nextcloud instance. Just one is the "proper" Nextcloud Online Account and the other is Generic CalDAV.

@PhAndersson said in Hardware recommendation for Noble:

@projectmoon said in Hardware recommendation for Noble:

Volla Quintus has served me well so far. It's also one of the only devices that is officially commercially supported for UT. Volla has someone working on UT for their devices.

Many thanks -- I'll give it a look. I guess flashing my first 2 phones with fastboot and adb earned me a few nerd points, but I won't complain either if the next one comes pre-installed

From a hardware standpoint, it's one of the few phones that functions without issue (beyond the software limitations of UT itself--QT 5.15 etc). All hardware except the in-screen fingerprint reader and FM radio are functioning. Both would be nice-to-have, especially the fingerprint reader, but are not deal-breakers. Camera quality is not SUPER amazing, but it is serviceable.

@lduboeuf So unfortunately, calendar sync is still broken. The calendar that was syncing (connection to Nextcloud via generic caldav instead of built-in Nextcloud integration) is no longer syncing. Only thing I see in Evolution logs is something about i_cal_time_compare < 0 failed.

I turned the Nextcloud integration itself back on for Calendar, and that synced fine... But I don't know if it will sync more later.

@pparent said in Organic Maps on Ubuntu Touch:

I have succeeded to start the app without Xwayland thank's tu qtubuntu-qt .
The "Terms and conditions" Window displays well and works well, but then the main window appears for 2 sec and crashes with:

Feb 24 13:43:05 ubuntu-phablet aa-exec[31163]: Aborted
Feb 24 13:43:05 ubuntu-phablet aa-exec[31165]: CHECK(!m_acquiredFrame->isBound())
Feb 24 13:43:05 ubuntu-phablet aa-exec[31165]: qt_common/qtoglcontext.cpp:108
Feb 24 13:43:05 ubuntu-phablet aa-exec[31165]: (1) ASSERT FAILED

I think I will leave it here for now. I think for this app to be usable it would require:

• To wait for Qt6 and possibly Mir2.x to be properly integrated in the system
• That Organic Maps get a Qt app more adapted to mobile display.

How did you get it to run without XWayland?

Volla Quintus has served me well so far. It's also one of the only devices that is officially commercially supported for UT. Volla has someone working on UT for their devices.

I may have discovered an issue with Postal/Lomiri Push Service/Lomiri URL Dispatcher. I'm not sure which component is affected, but basically, Indra notifications stopped working after I upgraded to the RC a few days ago. I finally just sat down to figure this out, and I was able to get notifications to show up again if I remove the actions array from the notification JSON. Put the actions back, no notifications appear. Importantly, the notifications do fire, they just don't show up in the top bar.

This code worked before i upgraded to the RC: https://git.agnos.is/projectmoon/indra/src/branch/master/indra/src/notify.rs#L72

Now it only works if i remove the "actions": [ ... ] field.

Edit: It seems to happen on the stable version of 24.04-1.2 as well.

@mark1250 filesystem as a whole is read only. It is possible to mount as rw. That will allow you to edit the file. Don't know if it will allow encryption though.

@lduboeuf said in Call for testing: calendar-app:

@projectmoon said in Call for testing: calendar-app:

@lduboeuf I installed it on a Volla Quintus on the current stable 24.04. Things seem to work. I notice that all my broken accounts/calendars are now sectioned as "Local Calendars," which I cannot delete.

Unfortunately, the broken online calendars for those who have already switched to 24.04 before the next release won't be automatically fixed.

A work around is to remove configs file:
rm -rf .config/evolution/sources then restart the phone

OK, then. New bug :). I deleted it and tried to re-add my calendars. The Google account went through the add flow but then said there's already an email address associated with that Google account. Then it did not add the calendar.

@gpatel-fr said in Thinnking of getting myself into Fairphone 5...:

@Boldos

If GPS is something like a deal breaker for you, some Volla phones are said to have working AGPS , something that is lacking at the moment for the FP5 so GPS is a bit of a hit and miss.

The other problems you are talking about are not specific to the FP5 (some rather uncommon media types have trouble with the main media app yes but can be read if necessary with third party software, VoLTE call following is also hit and miss, focus is not very reliable for low distance (<50cm) photos but this can be worked around by switching to video mode and back, and I have no problem with my Wifi hotspot but I'm not using a variety of Wifi nodes)

I can confirm that the Volla Quintus has functioning AGPS. GPS lock takes a few seconds at most, usually.

@lduboeuf I installed it on a Volla Quintus on the current stable 24.04. Things seem to work. I notice that all my broken accounts/calendars are now sectioned as "Local Calendars," which I cannot delete.

@mihael I have this problem as well, and it's because the X11 server doesn't really know what the keyboard height is. The responsive patch for Whatsapp Web/Signal/etc is basically shrinking the window size inside the X server to the standard keyboard height when the keyboard is out. But it would need a configurable option to change that value in the app itself, I think. Unless there is some magic (and preferably confined) way to yoink the keyboard height from the keyboard?

Personally, I think the keyboard height in UT is way too low. But, an adjustable height keyboard Should Just Work once Mir 2.x comes out... right?

Indra 1.2.1 is now available with a laundry list of improvements and fixes. Find it at https://next.open-store.io/app/indra.projectmoon/ or https://git.agnos.is/projectmoon/indra/releases/tag/v1.2.1.

• Feature: Make links clickable in messages.
• Feature: Add the ability to search and filter nodes on the map.
• Feature: De-duplicate messages that are likely rebroadcasts.
• Feature: Show hops away/signal strength on messages.
• Feature: Add/remove favorite nodes.
• Improvement: New message footer layout.
• Improvement: Better node list appearance in dark mode.
• Improvement: Tweaks to the choice of black or white text for messages in dark mode. More readable.
• Improvement: Add node ID to the node info page.
• Improvement: Show node distance on the map, and sort by distance.
• Improvement: New map icon.
• Improvement: Pull to refresh the node list.
• Improvement: Proper status indicators for sending messages.
• Improvement: Show channel/conversation status indicators on main view.
• Improvement: Add a setting to toggle forced Bluetooth reset.
• Improvement: Add a setting to control how long it takes before a node is considered offline.
• Improvement: Add a setting to control the message de-duplication window.
• Improvement: Translation updates.
• Fix: Apply the default channel name to the public channel no matter its index.
• Fix: Fix a UI lockup when reconnecting to the radio.
• Fix: No more UI flickering when disconnecting from the radio.
• Fix: More efficient refreshing of the node list.

@pparent out of curiosity, have you considered attempting to bundle the Qt6 web engine statically? Similar to whatever is going on with Morph Qt6 version.

@mihael so is mine.

@pparent said in Whatslectron: Whatsapp Web with Electron.:

@projectmoon

This is kind of strange that the icon is named Signal, I don't have the same thing.

Maybe localization oversight?

Seems like it works. But for some reason, the icon is named Signal (this is a problem with Min Browser too).

@Averiz very nice to see alternative keyboards. Is there a way to adjust the height of the keyboard?

@pparent said in French ID app interoperability.:

@domubpkm

Well I'm not sure but given what I have published above, It could mean that it can only work by design on an un-compromised google certified devices ( I've read that there exists so-called technologies as "Android hardware-backed keystore" and "Trusted Execution Environment" , could the app possibly rely on that? ). So maybe it's not working with microG because they don't want it to, because they want the app to run only on a so-called "safe envieronement" provided by google.

This kind of stuff is happening more and more. Even apps like the ChatGPT app for Android require "Play Integrity." It's an API that needs to be made illegal, and a lot of national apps are relying on it too. For example, the Icelandic app Auðkenni used to work without it, but now your device has to be "secure" in order to use the app. Thankfully, in that case, there is an alternative method of authentication using SIM Toolkit.

MicroG is able to execute SafetyNet/Play Integrity, but the device has to have the bootloader locked and a bunch of other stuff. And depending on level of attestation required by the app, it may or may not actually run.