Open GoogleCodeExporter opened 8 years ago
Original comment by rdamazio@gmail.com
on 1 Oct 2010 at 6:34
There is really nothing I can do about it, the OS is reporting the android app
is closing the connection abruptly. I would suggest calling
socket.shutdownOutput() after flush() and before close() in
IpNotificationMethod to see if it helps.
Original comment by lehph...@gmail.com
on 1 Oct 2010 at 6:52
Thanks for the quick reponse. Suggestion is way over my head, not a coder and
have no idea how to execute that idea, but thanks anyway!. Will uninstall and
try again at some later date.
Original comment by rmillet...@gmail.com
on 1 Oct 2010 at 7:28
Sorry, my suggestion is for rdamazio actually. You'll see this happen sometimes
only, I got it only once.
Original comment by lehph...@gmail.com
on 1 Oct 2010 at 7:41
I get the following using 0.5.1 on Win7 which I guess is the same issue, pings
work but messages produce this error :
2010-10-08 21:42:36,143 INFO [NotificationManagerImpl] - Notification received:
notificationId=38288218171819376, type=Battery
2010-10-08 21:42:37,138 DEBUG [bluetooth] - connection accepted
2010-10-08 21:42:37,138 DEBUG [bluetooth] - socket[1788] getpeeraddress
2010-10-08 21:42:37,138 DEBUG [bluetooth] - connection open, open now 1
2010-10-08 21:42:37,139 DEBUG [bluetooth] - socket[1788] recv
(byte[],int,int=4096)
2010-10-08 21:42:37,182 DEBUG [bluetooth] - Connection closed
2010-10-08 21:42:37,182 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-10-08 21:42:37,183 DEBUG [bluetooth] - closing RFCOMM Connection 1788
2010-10-08 21:42:37,183 DEBUG [bluetooth] - connection closed, open now 0
2010-10-08 21:42:37,183 DEBUG [bluetooth] - socket[1788] close
Original comment by SmnTh...@gmail.com
on 9 Oct 2010 at 8:32
@SmnThorn This message has been posted in issue 217. In short, some
notifications are not sent properly over bluetoot. Issue 3 is about bluetooth
errors you might want to star that one to get updates about it.
Original comment by lehph...@gmail.com
on 9 Oct 2010 at 2:24
Hello
please send me source code or give source code link .please
Original comment by ghorivip...@gmail.com
on 19 Aug 2014 at 4:13
Original issue reported on code.google.com by
rmillet...@gmail.com
on 1 Oct 2010 at 6:24