You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What steps will reproduce the problem?
1. Save a log or email it to yourself
2. Open the saved/emailed log file and (quickly!) compare it to the one that
appears on the screen
3. Notice that every other line on the screen appears to be missing from the
saved/emailed file.
What is the expected output? What do you see instead?
For example, I was trying to track down an issue with my bluetooth adapter.
The log message on the screen contained the following information, which is
what I expected to see in the file that was emailed to me:
I/BluetoothAudioGateway.cpp( 170): Accepting HF connection.
I/BluetoothAudioGateway.cpp( 170): Successful accept() on AG socket 29: new
socket 36, address XX:XX:XX:XX:XX:XX, RFCOMM channel 10
I/BT Audio Gateway( 170): connect notification!
I/BT Audio Gateway( 170): Incoming connection from handsfree XX:XX:XX:XX:XX:XX
on channel 10
I/BT HSHPF( 170): Incoming rfcomm (handsfree) connection from
XX:XX:XX:XX:XX:XXon channel 10
I/BT HSHFP( 170): Rejecting incoming connection because priority = 0
I/BT HSHFP( 170): initializeNativeDataNative: ALREADY CONNECTED!
But when I emailed it to myself, the same section only contained the following
lines:
I/BluetoothAudioGateway.cpp( 170): Successful accept() on AG socket 29: new
socket 36, address XX:XX:XX:XX:XX:XX, RFCOMM channel 10
I/BT Audio Gateway( 170): Incoming connection from handsfree XX:XX:XX:XX:XX:XX
on channel 10
I/BT HSHFP( 170): Rejecting incoming connection because priority = 0
What version of the product are you using? On what operating system?
Logger version 1.2
on
Nexus One
Android version 2.2
Build number FRF91
Original issue reported on code.google.com by jasonvin...@gmail.com on 10 Aug 2010 at 8:03
The text was updated successfully, but these errors were encountered:
Original issue reported on code.google.com by
jasonvin...@gmail.com
on 10 Aug 2010 at 8:03The text was updated successfully, but these errors were encountered: