Trying to revive 'ubtd' (Bluetooth file transfer)
-
@PhAndersson said in Trying to revive 'ubtd' (Bluetooth file transfer):
it says the official Android or iOS app is required to do this, which I don't have access to
I have heard Telegram works on Waydroid, fwiw.
-
@arubislander said in Trying to revive 'ubtd' (Bluetooth file transfer):
@PhAndersson said in Trying to revive 'ubtd' (Bluetooth file transfer):
it says the official Android or iOS app is required to do this, which I don't have access to
I have heard Telegram works on Waydroid, fwiw.
Thanks for the tip -- I'll give it a look.
-
@PhAndersson said in Trying to revive 'ubtd' (Bluetooth file transfer):
if the obexd issue can be solved at platform level, the app could be ported to 24.04 with minimum effort.
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. -
@PhAndersson there's active OpenStore matrix room.
-
@gpatel-fr said in Trying to revive 'ubtd' (Bluetooth file transfer):
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...
-
@PhAndersson said in Trying to revive 'ubtd' (Bluetooth file transfer):
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.
-
@paulcarroty said in Trying to revive 'ubtd' (Bluetooth file transfer):
@PhAndersson there's active OpenStore matrix room.
Many thanks -- I just joined it.
-
Status update:
'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
.clickpackages:- 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.
-
Final status update: the app has passed the code review and v0.1.1 is now available on the OpenStore.
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
-
P PhAndersson has marked this topic as solved
-
@PhAndersson Not tested yet. But thank you for your work and perseverance.
-
@PhAndersson Should the app be shown in UT TT apps ? I don't see anything on my Volla 22. What should be the names of the cache config data directories ?
-
@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). -
-
Sure, Tweak Tool, of course -- sorry.
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.
-
I need to amend the statement above. After further tests, the code that has been used to generate the packages is the correct one, so all the latest functionalities are present, and both sending and receiving files should work.
The only problem is that the wrong version string has been used when building.
-
@PhAndersson Can connect with bluetooth a Volla with Volla OS to a Volla 22 with UT noble. Try to send a little video from Volla to Volla 22 following the procedure. But doesn't work currently. File not sent / received.
-
@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.
-
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 $HOMEafter adding the overlay, you have to restart the obex service using systemctl --user restart obex
-
@PhAndersson @gpatel-fr So the fix is in 1.3 daily. Wait 1.3 candidate to test. Thanks.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login