From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Samsung Z500 + bluez rfcomm problem, potential bug?
Date: Sat, 10 Sep 2005 15:42:22 +0200 [thread overview]
Message-ID: <1126359742.31313.7.camel@blade> (raw)
In-Reply-To: <4322E012.1070701@telia.com>
Hi Mikael,
> Can anyone from the developer team look at
> http://sourceforge.net/mailarchive/forum.php?thread_id=8154927&forum_id=1883
> ?
>
> I am suspecting it is a potential bug in either the phone or the
> software. Yet I am not qualified enough in the area to judge which. I
> did try out Seba T.'s suggestion yet the reply was placed as a new
> thread (for some reason) at
> http://sourceforge.net/mailarchive/forum.php?thread_id=8159796&forum_id=1883.
it is a good idea to check with sdptool to which RFCOMM channel the DUN
profile is attached. However you can also send me the phone and I try to
fix it or at least create a workaround.
Regards
Marcel
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2005-09-10 13:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-10 13:30 [Bluez-devel] Samsung Z500 + bluez rfcomm problem, potential bug? Mikael Hakali
2005-09-10 13:42 ` Marcel Holtmann [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1126359742.31313.7.camel@blade \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox