Return-Path: Subject: RE: [Bluez-devel] bluetooth socket + rfcomm tty From: Marcel Holtmann To: BlueZ Mailing List In-Reply-To: References: Content-Type: text/plain Message-Id: <1106760899.28444.42.camel@pegasus> Mime-Version: 1.0 Sender: bluez-devel-admin@lists.sourceforge.net Errors-To: bluez-devel-admin@lists.sourceforge.net Reply-To: bluez-devel@lists.sourceforge.net List-Unsubscribe: , List-Id: BlueZ development List-Post: List-Help: List-Subscribe: , List-Archive: Date: Wed, 26 Jan 2005 18:34:59 +0100 Hi Victor, > Now I close the socket after converting to TTY. After this I open > "/dev/rfcomm0" with O_RDWR | O_NOCTTY and write ATD12345\n\r command to > it, then read the response (receive echo), and sleep, meanwhile phone > starts to dial the number, but then stops for no reason. If I do the > same with original (non-converted) socket (skipping converting to TTY), > everything is OK. if the socket way works, why don't you use it? > I've taken a look at hcidump output and it looks rather strange if I > compare it for both cases. In the case of file handle to converted TTY > all the data looks fragmented between ACL packets (like ATD1234 is not > sent in one packet, like in the case of non-converted socket, but piece > by piece in a number of packets) + there is a lot of activity from the > phone during the sleep phase when I do not do anything with the file > handle. What kind of phone is this? Regards Marcel ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ Bluez-devel mailing list Bluez-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bluez-devel