Closed GoogleCodeExporter closed 8 years ago
Using Android 2.2 on Samsung Galaxy S - Desktop version 0.5.1 - the PC gives
the following relevant portion from the log:
2010-11-09 11:13:01,421 DEBUG [bluetooth] - connection open, open now 1
2010-11-09 11:13:01,421 DEBUG [bluetooth] - rf(8) read(byte[4096])
2010-11-09 11:13:01,421 DEBUG [bluetooth] - read[] waits for data
2010-11-09 11:13:01,453 DEBUG [bluetooth] - read waits returns WAIT_OBJECT_0
2010-11-09 11:13:01,453 DEBUG [bluetooth] - read waits returns WAIT_OBJECT_0
2010-11-09 11:13:01,453 DEBUG [bluetooth] - rf(8) read([]) received 0
2010-11-09 11:13:01,453 DEBUG [bluetooth] - rf(8) read([]) not connected
2010-11-09 11:13:01,453 DEBUG [bluetooth] - read([]) no data
2010-11-09 11:13:01,453 DEBUG [bluetooth] - read([]) return EOF
2010-11-09 11:13:01,453 ERROR [BluetoothNotificationReceiver] - Error handling
bluetooth notification
com.notifier.desktop.exception.ParseException:
com.google.protobuf.InvalidProtocolBufferException: While parsing a protocol
message, the input ended unexpectedly in the middle of a field. This could
mean either than the input has been truncated or that an embedded message
misreported its own length.
at com.notifier.desktop.parsing.MultiNotificationParser.parse(MultiNotificationParser.java:53)
at com.notifier.desktop.parsing.MultiNotificationParser.parse(MultiNotificationParser.java:27)
at com.notifier.desktop.notification.bluetooth.BluetoothNotificationReceiver$1.run(BluetoothNotificationReceiver.java:87)
at java.lang.Thread.run(Unknown Source)
Caused by: com.google.protobuf.InvalidProtocolBufferException: While parsing a
protocol message, the input ended unexpectedly in the middle of a field. This
could mean either than the input has been truncated or that an embedded message
misreported its own length.
at com.google.protobuf.InvalidProtocolBufferException.truncatedMessage(InvalidProtocolBufferException.java:49)
at com.google.protobuf.CodedInputStream.refillBuffer(CodedInputStream.java:691)
at com.google.protobuf.CodedInputStream.readRawByte(CodedInputStream.java:714)
at com.google.protobuf.CodedInputStream.readRawVarint32(CodedInputStream.java:318)
at com.notifier.desktop.parsing.MultiNotificationParser.parse(MultiNotificationParser.java:42)
... 3 more
2010-11-09 11:13:01,453 DEBUG [bluetooth] - closing RFCOMM Connection 8
2010-11-09 11:13:01,453 DEBUG [bluetooth] - connection closed, open now 0
2010-11-09 11:13:01,453 DEBUG [bluetooth] - rf(8) CloseServerConnection
2010-11-09 11:13:01,453 DEBUG [bluetooth] - rf(8) closing RfCommPort,
Connected[FALSE]
2010-11-09 11:13:01,515 DEBUG [bluetooth] - rf(8) closed RfCommPort
Original comment by jman1...@gmail.com
on 9 Nov 2010 at 7:15
PC is using WIDCOMM Bluetooth software 5.5.0.3208
Original comment by jman1...@gmail.com
on 9 Nov 2010 at 7:16
You are not the first one to report this, it seems Samsung Galaxy S phones
don't send bluetooth messages correctly. Updated wiki page.
Original comment by lehph...@gmail.com
on 9 Nov 2010 at 7:41
Issue 289 has been merged into this issue.
Original comment by lehph...@gmail.com
on 15 Nov 2010 at 1:32
Problem occurred in 2.2, I was using SGS with AND on anrdoid 2.1 and it was
working correctly
Original comment by jaroslaw...@gmail.com
on 20 Jan 2011 at 2:49
Original issue reported on code.google.com by
jman1...@gmail.com
on 9 Nov 2010 at 7:13