我刚刚在我的LogCat中注意到我得到了一致的错误(大约每一秒),并想知道是否有人可以解决这个问题? Droid X2 w /最新更新。
10-21 14:52:49.590: ERROR/TundConnector(1482): Communications error
10-21 14:52:49.590: ERROR/TundConnector(1482): java.io.IOException: No such file or directory
10-21 14:52:49.590: ERROR/TundConnector(1482): at android.net.LocalSocketImpl.connectLocal(Native Method)
10-21 14:52:49.590: ERROR/TundConnector(1482): at android.net.LocalSocketImpl.connect(LocalSocketImpl.java:238)
10-21 14:52:49.590: ERROR/TundConnector(1482): at android.net.LocalSocket.connect(LocalSocket.java:98)
10-21 14:52:49.590: ERROR/TundConnector(1482): at com.android.server.NativeDaemonConnector.listenToSocket(NativeDaemonConnector.java:99)
10-21 14:52:49.590: ERROR/TundConnector(1482): at com.android.server.NativeDaemonConnector.run(NativeDaemonConnector.java:83)
10-21 14:52:49.590: ERROR/TundConnector(1482): at java.lang.Thread.run(Thread.java:1019)
10-21 14:52:49.590: ERROR/TundConnector(1482): Error in NativeDaemonConnector
10-21 14:52:49.590: ERROR/TundConnector(1482): java.io.IOException: No such file or directory
10-21 14:52:49.590: ERROR/TundConnector(1482): at android.net.LocalSocketImpl.connectLocal(Native Method)
10-21 14:52:49.590: ERROR/TundConnector(1482): at android.net.LocalSocketImpl.connect(LocalSocketImpl.java:238)
10-21 14:52:49.590: ERROR/TundConnector(1482): at android.net.LocalSocket.connect(LocalSocket.java:98)
10-21 14:52:49.590: ERROR/TundConnector(1482): at com.android.server.NativeDaemonConnector.listenToSocket(NativeDaemonConnector.java:99)
10-21 14:52:49.590: ERROR/TundConnector(1482): at com.android.server.NativeDaemonConnector.run(NativeDaemonConnector.java:83)
10-21 14:52:49.590: ERROR/TundConnector(1482): at java.lang.Thread.run(Thread.java:1019)
我也经常看到这个:
10-21 14:55:27.856: ERROR/NetlinkEvent(1351): NetlinkEvent::FindParam(): Parameter 'UDEV_LOG' not found
答案 0 :(得分:1)
我没有找到任何真正的解决方案,甚至导致这一点。但我找到了一种方法使logcat可以用于这些错误,在Logcat中使用以下正则表达式:
tag:[^((TundConnector)|(NetlinkEvent))]
这将为日志中的所有内容提供 NOT 标记为 TundConnector 或 NetlinkEvent
答案 1 :(得分:1)
尝试重新启动eclipse,遇到同样的问题,重新启动eclipse后,问题就解决了。