Ticket #120 (assigned defect)
bluetooth OBEX
| Reported by: | laforge@… | Owned by: | openmoko-devel |
|---|---|---|---|
| Priority: | high | Milestone: | |
| Component: | bluez | Version: | current svn head |
| Severity: | normal | Keywords: | |
| Cc: | buglog@… | Blocked By: | |
| Blocking: | Estimated Completion (week): | ||
| HasPatchForReview: | no | PatchReviewResult: | |
| Reproducible: |
Description
work out what we want to do here, which libraries to use, how to integrate with
contacts and other apps.
Change History
comment:2 Changed 5 years ago by willie_chen@…
- Owner changed from marcel@… to michael@…
- Status changed from assigned to new
Hi Machiael,
Help us follow this issue.
comment:4 Changed 5 years ago by Woody14619
FYI, the ObexFTP and ObexPush? (libobex based) from the angstrom archive worked with 2007.2, but no longer work with 2008.8. They both attempt to connect, seem to partially hook, and then get an error code of -94. (Which I can find little documentation on. I'm guessing this is a bluez version mismatch issue?) Implementing obexftp and receiving obexpush is pretty simple after pulling those packages and altering /etc/init.d/bluetooth to startup/shutdown the daemons involved.
Note: See
TracTickets for help on using
tickets.
There are a lot of possibilities to implement this for the clients. The basic
idea would be to have an OpenOBEX GLib binding. This is work in progress and at
this time far from being mainline ready. An alternative would be to use the
gwobex library from the Maemo project.
The other option is to have a server process that allows to push and receive
files via a simple D-Bus interface. An attempt to get this done is currently
work in progress via bluetoothd-service-transfer.