@gpatel-fr said:

@domubpkm

Well, if my calculation is correct that means about 2Mbits/s, it seems quite decent for Bluetooth.

Agreed.

@domubpkm said:

@phandersson I transferred a RAR file from UT smartphone to another with Volla OS, because no function to decompress RAR on UT. Did not work directly, extension not recognized. On the other hand, workaround by transforming the RAR extension into mp4: ok, worked. Then I put the RAR extension back in, and unzipped it without any problem. Just tested this.

Thanks for the feedback.

Make Ratatoskr recognize various extensions?

Well spotted -- the main app will accept incoming files of any type, but the SharePlugin only registers itself as handler for a limited number of file types. For no particular reason, as far as I know.

I've created the following issue to track this: https://github.com/petroniusniger/ratatoskr/issues/34

Well, if my calculation is correct that means about 2Mbits/s, it seems quite decent for Bluetooth.

@domubpkm said:

@phandersson ok. I switched to dev channel and i tried to send a (big) file from my Volla 22 with UT to a Volla with volla OS with your last update : it works now. .

Excellent news -- thanks for the feedback.

But i found the transfer speed was very slow. Could it be improve or not ?

Could you be a bit more specific, please? From what I read online, typical Bluetooth transfer speeds are between 1 and 3 Mbps.

When I tested the app prior to releasing v0.1.1, I measured 1.3 Mbps when pushing a large file from my (Linux) laptop to the phone (Pixel 3a).

Do you get a comparable bandwidth, or something much lower? (to measure it, I simply time the transfer and divide it by the file size).

yes that's it.
@domubpkm
you can add the fix even on stable with a systemd overlay file.

phablet@ubuntu-phablet:~$ systemctl --user cat obex
# /usr/lib/systemd/user/obex.service
[Unit]
Description=Bluetooth OBEX service

[Service]
Type=dbus
BusName=org.bluez.obex
ExecStart=/usr/libexec/bluetooth/obexd

[Install]
Alias=dbus-org.bluez.obex.service

# /usr/lib/systemd/user/obex.service.d/ubuntu-touch-session.conf
[Service]
ExecStart=
ExecStart=/usr/lib/bluetooth/obexd -P ftp,irmc,mas,pcsuite -r $HOME

# /home/phablet/.config/systemd/user/obex.service.d/xxoverride.conf
[Service]
ExecStart=
ExecStart=/usr/libexec/bluetooth/obexd -P ftp,irmc,mas,pcsuite -r $HOME

after adding the overlay, you have to restart the obex service using systemctl --user restart obex

@domubpkm said:

@PhAndersson Can connect with bluetooth a Volla with Volla OS to a Volla 22 with UT noble.

There is currently a bug in Noble (up to 24.04-1.2) that prevents the OBEX daemon from starting.

The fix exists and is already merged. Here is the related MR: https://gitlab.com/ubports/development/core/ubuntu-touch-session/-/merge_requests/81. It is supposed to be part of the upcoming 24.04-1.3.

Based on earlier tests by @gpatel-fr, once this fix is available, 'ratatoskr' should work on Noble as well.

The only problem is that the wrong version string has been used when building.

I just checked on my phone and it shows there, yes. Just look under the name 'Ratatoskr' (that's the actual name I gave the app -- "Bluetooth file transfer" is only a description).

It's the first UT app I built, so I'm not familiar yet with all the intricacies of the dev. workflow.

In any case, it seems there was a mixup, as the packages that were pushed on the server are v0.1.0, not v0.1.1. The "file sending" functionality may not be functional in that version (the receiving one should be).

I'll try to get this fixed tomorrow.

@domubpkm said:

@PhAndersson Should the app be shown in UT TT apps ? I don't see anything on my Volla 22.

I'm sorry, I guess I'm a bit slow tonight, but I'm not clear on what 'TT' means in this context. Can you clarify?

What should be the names of the cache config data directories ?

The app cache is in ~/.cache/ratatoskr.petroniusniger/. This is where incoming files are kept -- but there is no config data there (the app doesn't store any configuration data at this stage).

You will find it under the name "Ratatoskr (Bluetooth file transfer)", in the "Utilities" category.

If you install it, may I suggest that you check the README here: https://github.com/petroniusniger/ratatoskr/tree/main for a brief description of how to use it most effectively?

Also, should you discover any bug, please report them here: https://github.com/petroniusniger/ratatoskr/issues

'ratatoskr' source code has just been reviewed by @bhdouglass (OpenStore team), and two issues have been identified that should be resolved before allowing publication of the .click packages:

• https://github.com/petroniusniger/ratatoskr/issues/12 (new one)
• https://github.com/petroniusniger/ratatoskr/issues/6 (known issue)

I'll work on resolving those 2 issues and release a v0.1.1 of the code before re-submitting it for publication.

@PhAndersson there's active OpenStore matrix room.

Many thanks -- I just joined it.

waiting for 24.04-2/stable,

or 24.04-1.3, whatever comes first. I'd bet on 24.04-1.3 but who knows?

as a status update, my available bandwidth has been dedicated to try to find a solution for the dbus rights problem (I have again flipflopped in my opinion about this matter, I have seen in the app code where it was supposed to prompt the user and instead it is always answering 'yes').
However Apparmor is not the easiest thing in the world to configure, so far I had no success.

about the confined apps being forbidden, there are in fact quite a few unconfined apps in the store, most of the ones I know of are managed by 'core' developers, but not all - as far as I know PureMaps is not maintained by a core Ubuntu touch developer; so it's mostly a matter of trust.

as they say in open source, 'unfortunately' the MR was backported to the 24.04-1.x too late to be included in the 24.04-1.2 version . That means that your app will not work at all in this version unless some system fiddling is done by the user.

So this means waiting for 24.04-2/stable, I guess...