Maximum file size ?

Hello,

Thank you for answering.
If you mean the manual by "document" there was nothing in it about maximum
file size, neither could I find something about it in the device settings
I'm trying to retrieve it now via the Capability Object's Memory Record
FileSize property, but I have troubles retrieving the Capability object (I'm
using Windows Sockets/C++). If anyone has an example of this it would be
most welcome, along with other ideas.

Michiel.


"haru" <haru_c@digitalme.com> wrote in message
news:639f05e3.0403010052.25dd792@posting.google.co m...
> Hi, Michiel.
>
> It is NOT a restriction of Bluetooth/OBEX.
>
> I can't fully understand the problem, but it seems be a BUG, or an
> error. Did you read the document for your phone? Are there any
> restrictions or any settable parameters of an Bluetooth/OBEX
> environment written in the document?
>
> /haru
>
> "Michiel" <michielGEEN@RECLAMEpayvision.com> wrote in message
news:<403f139d$0$570$e4fe514c@news.xs4all.nl>...
> > Hello,
> >
> > I made a program that uses Bluetooth/OBEX to send files to a phone.
> > However, for the the i-mate Smartphone2 (aka Orange SPV e200, QTek 8080,
HTC
> > Voyager, O2 Xphone) with Windows Mobile 2003 i can't seem to send files
> > larger than ~540KB ? (536 yes, 569 no).
> > Which of either the phone, Bluetooth, the Bluetooth device or the OS
could
> > be causing this restriction ?
> >
> > Thanks for any clues.

Hi, Michiel.

I understand that the manual says nothing about this problem.
Again, if you send a file which is lager than 540Kb to a phone, what
kind of error will happen? How does the phone behave?
For example, an OBEX error is returned, or the connection is released,
or no response, etc. Please tell us more detail.


In another article, you said you can't retrieve the OBEX Capability
Object(it is also written in the following). The OBEX Capability
Object is the object that has the MIME type of "x-obex/capability",
you mean? If so, I think it is not used for Bletooth OBEX, differently
from IrOBEX.

It is unnecessary to have the OBEX Capability Object for Bluetooth
OBEX services(OPP, FTP, Sync), because they have the Service Record to
expose its own capabilities instead of the OBEX Capability Object. If
you want to get the OBEX capability of a peer device, you are supposed
to retrieve the Service Record using SDP(Service Discovery Protocol)
and analyze it.

/haru


"Michiel" <michielGEEN@RECLAMEpayvision.com> wrote in message news:<40434c17$0$569$e4fe514c@news.xs4all.nl>...
> Hello,
>
> Thank you for answering.
> If you mean the manual by "document" there was nothing in it about maximum
> file size, neither could I find something about it in the device settings
> I'm trying to retrieve it now via the Capability Object's Memory Record
> FileSize property, but I have troubles retrieving the Capability object (I'm
> using Windows Sockets/C++). If anyone has an example of this it would be
> most welcome, along with other ideas.
>
> Michiel.

---<CUT>---

I'm sorry, Michiel

I have posted the reply for your article, but I forgot one thing to be
written.
If you get the Service Record instead of the Capability Object, the
memory size information is not included in the Service Record of
course.
(For this reason, your problem can't be resolved easily. Please tell
us more information about your situation.)

/haru

"Michiel" <michielGEEN@RECLAMEpayvision.com> wrote in message news:<40434c17$0$569$e4fe514c@news.xs4all.nl>...
> Hello,
>
> Thank you for answering.
> If you mean the manual by "document" there was nothing in it about maximum
> file size, neither could I find something about it in the device settings
> I'm trying to retrieve it now via the Capability Object's Memory Record
> FileSize property, but I have troubles retrieving the Capability object (I'm
> using Windows Sockets/C++). If anyone has an example of this it would be
> most welcome, along with other ideas.
>
> Michiel.

---<CUT>---

Hi Haru, thanks for replying.

"haru" <haru_c@digitalme.com> wrote in message
news:639f05e3.0403011819.6e0118f8@posting.google.c om...
> Hi, Michiel.
>
> I understand that the manual says nothing about this problem.
> Again, if you send a file which is lager than 540Kb to a phone, what
> kind of error will happen? How does the phone behave?
> For example, an OBEX error is returned, or the connection is released,
> or no response, etc. Please tell us more detail.
>

The phone behaviour is normal, i.e. it asks "do you want to save file
xxx.xxx" after the download has completed. I say "yes" just like in any
other case, but the file just isn't on the phone after that.


>
> In another article, you said you can't retrieve the OBEX Capability
> Object(it is also written in the following). The OBEX Capability
> Object is the object that has the MIME type of "x-obex/capability",
> you mean? If so, I think it is not used for Bletooth OBEX, differently
> from IrOBEX.

Aha, my program actually has interfaces for both Infrared as well as
Bluetooth, perhaps I'll put it in the Infrared section then. Do you know any
newsgroup specifically dedicated to OBEX btw ?

>
> It is unnecessary to have the OBEX Capability Object for Bluetooth
> OBEX services(OPP, FTP, Sync), because they have the Service Record to
> expose its own capabilities instead of the OBEX Capability Object. If
> you want to get the OBEX capability of a peer device, you are supposed
> to retrieve the Service Record using SDP(Service Discovery Protocol)
> and analyze it.
>
> /haru

Yes, I'm already retrieving the COD from the devices (if that's what you
mean - a.o. GET_COD_SERVICE), but this is too limited and also incomplete.
E.g. I've dissected the COD's (Classes of Device) for both the Nokia 6310i
(non-smart)
and 7650 (smart), but there doesn't seem to be any relevant difference
between them. (I want to know which file types I can send to a phone as
well, and the 6310i only accepts vcf files) I was hoping the Smart Phone bit
of the Minor Device
Class mask would be enabled for the 7650, but unfortunately both phones
return Cellular as Minor Device Class.

Hi, Michiel.

I'm sorry to delay the reply due to my business journey.

> The phone behaviour is normal, i.e. it asks "do you want to save file
> xxx.xxx" after the download has completed. I say "yes" just like in any
> other case, but the file just isn't on the phone after that.

Well,...
Your phone has two areas when it receives a OBEX put data. One is for
receiving a data "temporarily", another is for storing a data
"permanently".

The temporary area is so-called "inbox" in the OBEX world, as you
know. The Put operation, from your program on a PC to your phone,
probably has finished normally. However, Moving that data, from the
temporary area("inbox") to the permanent area (both are in your
phone), is failed probably after you say "yes" for asking "do you want
to save file xxx.xxx". This means, the memory inside your phone may be
insufficient to store that data. If you try it after you delete some
unnecessary data from (your phone book? of) your phone, I suppose it
might work well enough. Otherwise, your phone has only approximately
540KB memory (for a phonebook?) by nature.


> Aha, my program actually has interfaces for both Infrared as well as
> Bluetooth, perhaps I'll put it in the Infrared section then. Do you know any
> newsgroup specifically dedicated to OBEX btw ?

I'm sorry, I don't know such a newsgroup.


> Yes, I'm already retrieving the COD from the devices (if that's what you
> mean - a.o. GET_COD_SERVICE), but this is too limited and also incomplete.
> E.g. I've dissected the COD's (Classes of Device) for both the Nokia 6310i
> (non-smart)
> and 7650 (smart), but there doesn't seem to be any relevant difference
> between them. (I want to know which file types I can send to a phone as
> well, and the 6310i only accepts vcf files) I was hoping the Smart Phone bit
> of the Minor Device
> Class mask would be enabled for the 7650, but unfortunately both phones
> return Cellular as Minor Device Class.

What I want to say is NOT the "CoD", but the "Service Record" (I'm
sorry that my explanation may be not enough to convey my intention to
you, because I'm not good at English).

The "Service Record" is the database of each profile, for example,
section 6.1 "SD SERVICE RECORDS" in Object Push Profile of the
Bluetooth. It can be retrieve using the Service Discovery
Protocol(SDP). It has various properties such a "Supported Formats
List" which is suppored format by that device(eg. vCard, vCal, vNote,
vMessage). It is also incomplete to realize your intention, but it is
any use.

/haru