Martin,
Please find my replies to your previous mail.
But some bluetooth C API don't work as expected.
[Martin] Can you tell me the detail? Thanks!
[corentin] OPP CAPI.
Let me detail the current status of NTB integration :
[Martin]: The bugs owner is Coretine, and I find Coretine is working
on the two bugs, right? If you need any help, please let us know.
*- dedicated user :*
https://bugs.tizen.org/jira/browse/TC-1981
<TC-1981https://bugs.tizen.org/jira/browse/TC-1981> : user privileges
record file is not created
https://bugs.tizen.org/jira/browse/TC-1972 : dedicated 'bluetooth' user
*[Martin] I have add comments to your patches to fix the bugs, I hope
that can help you. **J*
[corentin] Yes I took those bugs. I'm just waiting for knowing how we
will handle obex dbus activation before finalizing.
This requires to fix obex implementation in NTB.
**
--> there are some difficulties to activate dbus obex service on dbus
session when it go through systemd dbus service activation.
If obex is only run as 'bluetooth' user, we could activate it on dbus
system and apply security with security-manager.
Then security-manager could set some relevant permissions/rights and
move transferred data to the right user directory...
We need to know how obex will be launched.
[Martin] Let’s talk in the Conference meeting. I’d like to know more
detail. I believe we can find right solution. J
[corentin] It is clear now, I will detail a way to handle multi-user
obex part in the wiki and let you know.
*- NFC :*
https://bugs.tizen.org/jira/browse/TC-1970 : Add OOB feature in NTB
https://bugs.tizen.org/jira/browse/TC-1971 : OOB pairing mechanism is
broken on NFC manager daemon
[Martin] we can fix it next week
[corentin] OK great.
*- OPP : *
https://bugs.tizen.org/jira/browse/TC-2088 : user can not send file
using OPP client C API
https://bugs.tizen.org/jira/browse/TC-2090 : unable to receive file
with OPP server C API
[Martin] That feature should be ready long long time ago. Maybe there
has some bug there.
Besides, have you set obex simple agent so user can confirm to acquire
the file when remote send the file?
But even not do that it should not segment fault. The issues should be
fixed before next Monday.
[corentin] Yes feature is present but doesn't work on Tizen.
The main problem I see is that NTB is not tested on Tizen Common before
deliveries.
To verify that, just take a look on the NTB dbus service which makes
activate it by 'app' user. This user doesn't exist on Tizen common.
Thanks to Zheng Wu, I was able to receive a file without NTB and using
simple obex agent from Bluez upstream sources.
But it is not a solution in Tizen.
--> OPP server/client CAPI are not working now. Zheng Wu told me that
it will be fixed in few days.
[corentin] The day is tomorrow for having an OPP implementation which
runs as 'bluetooth' user (as NTB daemon).
*Other questions :*
- How obex agent is supposed to be handled ? Does it need to be
register in popup app as it is done for pairing popups ?
If yes, a new Jira bug can be filed.
[Martin] If I did not remember wrong, we need to have a popup UI and
let user to confirm to accept the file transferred from remote device.
[corentin] Yes, indeed. I wanted to get a reply about implementation.
With current design pairing popups are managed by bt_agent_xxx CAPI.
As OPP implementation is currently evoluting to work on Tizen and match
multi-user compliancy. I would like to know how obex agent is supposed
to be registered in popup app ?
- If obex is only run on 'bluetooth' user for all other users, can
obex service run on dbus system instead of session ?
[Martin] in my knowledge, obex should run as DBus session. Only root
user run as system Dbus. I can’t find any issue here. Let’s talk in
next Conference meeting.
[corentin] There are maybe too much modifications to run obex on system
dbus... It was just an idea as we want to run it only on a single
'bluetooth' user who is a system user. But I will configure 'bluetooth'
user or NTB to enable obex dbus session activation over systemd.
Until now, I was mainly focused on Web Bluetooth API which doesn't
offer all of these bluetooth profiles.
So I haven't tested yet other bt profiles CAPI (hid, avrcp, a2dp,...).
[Martin] I was complaining that there are some web API issue, that is
what you are working on? Can you tell us detail about that?
[corentin] I know there are some Bluetooth Web API issues but there are
minor compared to the NTB integration issues which have a much higher
priority.
Best regards,
Corentin
_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev
