From owner-freebsd-bluetooth@FreeBSD.ORG Wed Jul 7 19:32:50 2010 Return-Path: Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 883BC106566B for ; Wed, 7 Jul 2010 19:32:50 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 3DADE8FC08 for ; Wed, 7 Jul 2010 19:32:46 +0000 (UTC) Received: by vws6 with SMTP id 6so45207vws.13 for ; Wed, 07 Jul 2010 12:32:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=OqgZCOHcvalJeorxmlMhMrOS4KkWQlymJAQSvXIiCzM=; b=HnU5OPs1buzIDOQJaI4EWVl79JmWoxIo8zbd/TwuDxmFbWp8/lpAGYw+LaxphGO/Fs 2APVjckVzYPOtzpSP+A28nU0o2mzmpNf4tRTOJ/DCf8/U7BovCTLs8QOrvo0H0h9s0ax jFVmRxO5zE6dngwJ8D1FzMX2GOrhcrlm/Jqr4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=BpTTzMUfdL/RPVuyonWSwWIgtLX7f1MIPwalP42P+hXr2fvY4HANcBJ09LJ7/bpdTQ VOqgDwxZ7BeLhQfIyokEdmi2LhwZESbchEtFEHjxEGJSS1/BZKamgBkz9DlttyvzF3+N CjuXZ8p/RDqlUZBSwLACiENP0CkkRqjffWqPI= MIME-Version: 1.0 Received: by 10.220.127.95 with SMTP id f31mr3659550vcs.67.1278531163651; Wed, 07 Jul 2010 12:32:43 -0700 (PDT) Received: by 10.220.199.13 with HTTP; Wed, 7 Jul 2010 12:32:43 -0700 (PDT) In-Reply-To: <1278529366.54763.15.camel@RabbitsDen> References: <201007071730.o67HUqO2044187@lurza.secnetix.de> <1278529366.54763.15.camel@RabbitsDen> Date: Wed, 7 Jul 2010 12:32:43 -0700 Message-ID: From: Maksim Yevmenkin To: Alexandre Sunny Kovalenko Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-bluetooth@freebsd.org, Oliver Fromme Subject: Re: Samsung SPF-800P supported by FreeBSD? X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Jul 2010 19:32:50 -0000 On Wed, Jul 7, 2010 at 12:02 PM, Alexandre "Sunny" Kovalenko 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