blocks|key|3035219|text|使用createRfcommSocketToServiceRecord而不是createRfcommSocket|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3035220|createRfcommSocketToServiceRecord使用您传递的UUID，并使用SDP来决定用于连接的无线信道。它还检查服务器是否使用相同的UUID侦听远程端点。以这种方式，这是获得连接的最可靠的方式:它总是使用正确的通道，如果打开连接成功，您知道在另一端的东西可以理解您的协议。|3035221|相反，createRfcommSocket只是连接到你告诉它的频道。无法知道远程端点上是否存在任何内容:您只知道设备在那里。另外，你选择广播频道可能是完全不恰当的。这就是为什么这个函数没有在API中发布，而另一个函数是首选的。|3035222|createRfcommSocket最初看起来可能更可靠，但这是因为它没有检查另一个端点是否存在侦听器:它忽略了某些错误情况。这也许可以用于实验，但对于生产系统来说是没用的，因为用户通常会忘记在另一个端点上启动服务器，而您的应用程序会以令人困惑的方式失败。|3035223|当然，由于createRfcommSocket没有在API中发布，所以你不能保证它在将来的安卓版本中会继续工作。|3035224|entityMap^0|2|X|12|I|0|0|X|0|3|I|0|0|I|0|5|I|0^^$0|@$1|2|3|4|5|6|7|P|8|@$9|Q|A|R|B|C]|$9|S|A|T|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|U|8|@$9|V|A|W|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|X|8|@$9|Y|A|Z|B|C]]|D|@]|E|$]]|$1|J|3|K|5|6|7|10|8|@$9|11|A|12|B|C]]|D|@]|E|$]]|$1|L|3|M|5|6|7|13|8|@$9|14|A|15|B|C]]|D|@]|E|$]]|$1|N|3|-4|5|6|7|16|8|@]|D|@]|E|$]]]|O|$]]

Use <code>createRfcommSocketToServiceRecord</code> instead of <code>createRfcommSocket</code>

<code>createRfcommSocketToServiceRecord</code> takes the UUID you pass and uses SDP to decide what radio channel to use for the connection. It also checks to make sure that a server is listening on the remote endpoint, with the same UUID. In this way, it's the most reliable way to get a connection: it'll always use the correct channel, and if opening the connection succeeds, you know something at the other end can understand your protocol.

In contrast, <code>createRfcommSocket</code> just connects to the channel you tell it. There's no way to know whether anything is listening on the remote endpoint: you only know the device is there. Also, your choice of radio channel may be completely inappropriate. That's why this function is not published in the API, and the other function is preferred.

<code>createRfcommSocket</code> may appear at first to be more reliable, but it's because it's not checking for the presence of a listener at the other endpoint: it's ignoring some error cases. This might be alright for experimenting, but it's no use for a production system, because often the user will forget to start the server on the other endpoint, and your app will fail in confusing ways.

Of course, as <code>createRfcommSocket</code> isn't published in the API, you've no guarantee it will continue to work at all in future releases of Android.

blocks|key|2538669|text|我在Lollipop上也有类似的问题(在以前的版本中使用)，并将"createRfcommSocket“替换为"createInsecureRfcommSocket”，解决了这个问题。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2538670|如果您选择官方API，您可以尝试createInsecureRfcommSocketToServiceRecord，因为createRfcommSocketToServiceRecord也不适合我。|2538671|entityMap^0|X|I|1K|Q|0|G|15|1O|X|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]|$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|O|8|@$9|P|A|Q|B|C]|$9|R|A|S|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|T|8|@]|D|@]|E|$]]]|I|$]]

I had a similar problem on Lollipop only (was working on previous versions) and replacing "<code>createRfcommSocket</code>" by "<code>createInsecureRfcommSocket</code>" fixed the problem.

if you choose the official API you could try <code>createInsecureRfcommSocketToServiceRecord</code> as <code>createRfcommSocketToServiceRecord</code> 
 was not working for me either.

blocks|key|2538681|text|我和Lollipop也有类似的问题(在本例中为5.0.2)。我在运行Kitkat的时候没有发现任何问题。我一直在使用createInsecureRfcommSocketToServiceRecord。我尝试了一些建议的使用反射的方法，但它似乎没有帮助(我认为这个解决方案与旧版本的Android有关)。不过，要明确的是，当我连接到多个SPP设备(条形码读取器和I/O板上带有巡回网络的蓝牙收音机)时，我所看到的通常会发生。我很难找到解决方案，并且认为可能没有解决方案，因为如果您连接到两个具有相同UUID的设备(在本例中是通用的SPP+)，则可能会在Lollipop中出现问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2538682|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I am having a similar issue with Lollipop (in this case 5.0.2). I don't see any issues when running Kitkat. I have been using createInsecureRfcommSocketToServiceRecord. I tried some of the suggested methods for using reflection but it didn't seem to help (I think that solution was related to older versions of Android). To be clear though, what I'm seeing typically happens when I connect to multiple SPP devices (barcode reader and I/O board with a roving networks bluetooth radio on it). I'm struggling to find a solution and think there might be none as maybe there is an issue in Lollipop if you connect to two devices with the same UUID (in this case the generic SPP one).

blocks|key|2538700|text|在6.0.1中，我一直面临着同样的问题，我在不同的线程/论坛/博客上读到了这个问题，我知道这是因为一个缺失的退路。您可以通过捕获异常并创建所需的回退来处理它。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2538701|更确切地说，BluetoothManager返回一个默认值-1，这是不可接受的状态，因此出现了错误。这将引发一个异常，该异常可以通过替换-1的错误来创建一个回退以解决问题。|2538702|以下是帮助我的链接：|2538703|https://github.com/don/BluetoothSerial/issues/89|offset|length|2538704|参考资料：IOException:+read+failed,+socket+might+closed+-+Bluetooth+on+Android+4.3|2538705|entityMap|0|LINK|mutability|MUTABLE|url|1|https://stackoverflow.com/questions/18657427/ioexception-read-failed-socket-might-closed-bluetooth-on-android-4-3?rq=1^0|0|0|0|0|1C|0|0|5|20|1|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|V|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|W|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|X|8|@]|9|@$H|Y|I|Z|1|10]]|A|$]]|$1|J|3|K|5|6|7|11|8|@]|9|@$H|12|I|13|1|14]]|A|$]]|$1|L|3|-4|5|6|7|15|8|@]|9|@]|A|$]]]|M|$N|$5|O|P|Q|A|$R|G]]|S|$5|O|P|Q|A|$R|T]]]]

I've been facing the same issue on 6.0.1, after reading about it at various threads/forums/blogs I understood that it is because of a missing fallback. And you can take care of it by catching the exception and creating the required fallback.

To be more specific, the BluetoothManager returns a default value of -1, which is not a acceptable state and hence, the error. This will raise an exception, which can be handled to create a fallback to solve the issue by replacing the error of -1.

Here is the link which helped me:

<a href="https://github.com/don/BluetoothSerial/issues/89" rel="nofollow noreferrer">https://github.com/don/BluetoothSerial/issues/89</a>

Reference:
<a href="https://stackoverflow.com/questions/18657427/ioexception-read-failed-socket-might-closed-bluetooth-on-android-4-3?rq=1">IOException: read failed, socket might closed - Bluetooth on Android 4.3</a>

I am making Bluetooth socket connection to Bluetooth device and want to read bytes from the device.

I have established connection correctly :

<pre><code> try {
 Method m = mmDevice.getClass().getMethod("createRfcommSocket", new Class[] { int.class });
 temp = (BluetoothSocket) m.invoke(mmDevice, 1);
 } catch (Exception e) {
 }
</code></pre>

I am reading bytes correctly from Bluetooth device.

I am getting the exception : 

<blockquote>
 java.io.IOException: read failed, socket might closed or timeout, read
 ret: -1
</blockquote>

Due to this, the connection is broken and the communication is also over between my device and Bluetooth device.

This problem is coming on Android 5.0.1 Lollipop especially

Can anyone have workaround ?

java.io.IOException: read failed, socket might closed or timeout, read ret: -1 on Android 5.0.1 Lollipop version

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我将蓝牙套接字连接到蓝牙设备，并希望从该设备读取字节。我正确地建立了联系： try {         Method m = mmDevice.getClass().getMethod("createRfcommSocket", new Class[] { int.class });          temp = (...

问java.io.IOException:读取失败，套接字可能关闭或超时，在Android5.0.1Lolliop版本上读取ret：-1
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问java.io.IOException:读取失败，套接字可能关闭或超时，在Android5.0.1Lolliop版本上读取ret：-1EN