Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 7 Jul 2010 12:32:43 -0700
From:      Maksim Yevmenkin <maksim.yevmenkin@gmail.com>
To:        Alexandre Sunny Kovalenko <gaijin.k@ovi.com>
Cc:        freebsd-bluetooth@freebsd.org, Oliver Fromme <olli@lurza.secnetix.de>
Subject:   Re: Samsung SPF-800P supported by FreeBSD?
Message-ID:  <AANLkTikpqxltZZTng6O5j-V8Rpft9JsVvHSMzGl1hKxp@mail.gmail.com>
In-Reply-To: <1278529366.54763.15.camel@RabbitsDen>
References:  <201007071730.o67HUqO2044187@lurza.secnetix.de> <1278529366.54763.15.camel@RabbitsDen>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jul 7, 2010 at 12:02 PM, Alexandre "Sunny" Kovalenko
<gaijin.k@ovi.com> wrote:
> On Wed, 2010-07-07 at 19:30 +0200, Oliver Fromme wrote:
>> Maksim Yevmenkin wrote:
>>  > yes, sorry. i meant obexapp :) obexapp is known to work with various
>>  > mobile phones (and other devices) that implement opp (obex push
>>  > profile) and oftp (obex file transfer profile). it is likely that you,
>>  > or someone you know, own such a mobile phone, and, you can always try
>>  > obexapp against it to see what it does and how it works.
>>
>> Well, even if it works with a mobile phone, that doesn't
>> guarantee that it would work with such a photo frame.
>>
>> In fact, the bluetooth function of that photo frame is
>> intended so you can upload pictures from a mobile phone
>> to the frame (not from a PC, AFAIK).  Can FreeBSD with
>> obexapp act like a mobile phone?
> If it helps you any... I have yet to see a difference between obexapp
> implementation of the Bluetooth PUSH and that of the handheld device. I
> have pushed pictures *from* my FreeBSD laptop *to* MacOS 10.4, Windows
> XP, Motorola V3xx, Nokia N75, Samsung Impression (or something similarly
> sounding -- no longer around to check), Nokia N810 and HTC Aria. This is
> not intended to give you any guarantees, merely some degree of
> assurance.

thanks :)

> One thing, which Maksim is much better positioned to comment on, is
> pairing. One would hope that frame being input-less device would just
> have a hardcoded PIN, but I would hunt downloadable manual for the thing
> and read up on the pairing process. Compatibility with Mac OS is good,
> multi-step Windows wizard, unless it boils down to "enter 0000 when
> prompted to do so", is, probably bad.

according to the manual the fixed pin is 0000 :) it appears that
pairing must be initiated from photo frame side. so, yes, will also
need to enable hcsecd(8) and adjust /etc/bluetooth/hcsecd.conf(5) to
include entry for the photo frame bdaddr with 0000 pin code. it should
be fine, imo.

thanks,
max



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTikpqxltZZTng6O5j-V8Rpft9JsVvHSMzGl1hKxp>