Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Error parsing BT HCI trace created with btsnooz.py

Hi All,

I've just used these instructions and python script btsnooz.py from there to extract BT HCI log (trace) from the bug report zip produced by my Samsung SM-A320FL smartphone running Android 8 Oreo: https://source.android.com/devices/bluetooth/verifying_debugging#debugging-with-bug-reports

Unfortunately Wireshark only displays the first 5 packets and returns the following error: "The capture file appears to be damaged or corrupt. (btsnoop: File has 117440512-byte packet, bigger than maximum of 262144)".

Although I should probably asking Android Engineering that instead, just wondering if I'm doing something obvious wrong by chance? Here's the trace in question: https://drive.google.com/file/d/1TpNnQ7Z39KHwtUgbYPPwRa6zu8JK05su/view?usp=sharing

Wireshark build is current stable 3.4.2 (v3.4.2-0-ga889cf1b1bf9).

Many thanks in anticipation!

Error parsing BT HCI trace created with btsnooz.py

Hi All,

I've just used these instructions and python script btsnooz.py from there to extract BT HCI log (trace) from the bug report zip produced by my Samsung SM-A320FL smartphone running Android 8 Oreo: https://source.android.com/devices/bluetooth/verifying_debugging#debugging-with-bug-reports

Unfortunately Wireshark only displays the first 5 packets and returns the following error: "The capture file appears to be damaged or corrupt. (btsnoop: File has 117440512-byte packet, bigger than maximum of 262144)". I understand that this trace is of some type (extension) ".cfa" but others can still open theirs with Wireshark. I gave mine extension .pcap as .cfa doesn't seem to be associated with anything.

Although I should probably asking Android Engineering that instead, just wondering if I'm doing something obvious wrong by chance? Here's the trace in question: https://drive.google.com/file/d/1TpNnQ7Z39KHwtUgbYPPwRa6zu8JK05su/view?usp=sharing

Wireshark build is current stable 3.4.2 (v3.4.2-0-ga889cf1b1bf9).

Many thanks in anticipation!

Error parsing BT HCI trace created with btsnooz.py

Hi All,

I've just used these instructions and python script btsnooz.py from there to extract BT HCI log (trace) from the bug report zip produced by my Samsung SM-A320FL smartphone running Android 8 Oreo: https://source.android.com/devices/bluetooth/verifying_debugging#debugging-with-bug-reports

Unfortunately Wireshark only displays the first 5 packets and returns the following error: "The capture file appears to be damaged or corrupt. (btsnoop: File has 117440512-byte packet, bigger than maximum of 262144)". I understand that this trace is of some type (extension) ".cfa" but others can still open theirs with Wireshark. Wireshark and I can open theirs too. I gave mine extension .pcap as .cfa doesn't seem to be associated with anything.

Although I should probably asking Android Engineering that instead, just wondering if I'm doing something obvious wrong by chance? Here's the trace in question: https://drive.google.com/file/d/1TpNnQ7Z39KHwtUgbYPPwRa6zu8JK05su/view?usp=sharing

Wireshark build is current stable 3.4.2 (v3.4.2-0-ga889cf1b1bf9).

Many thanks in anticipation!

Error parsing BT HCI trace created with btsnooz.py

Hi All,

I've just used these instructions and python script btsnooz.py from there to extract BT HCI log (trace) from the bug report zip produced by my Samsung SM-A320FL smartphone running Android 8 Oreo: https://source.android.com/devices/bluetooth/verifying_debugging#debugging-with-bug-reports

Unfortunately Wireshark only displays the first 5 packets and returns the following error: "The capture file appears to be damaged or corrupt. (btsnoop: File has 117440512-byte packet, bigger than maximum of 262144)". I understand that this trace is of some type (extension) ".cfa" but others can still open theirs with Wireshark and I can open theirs too. Assuming extension as such doesn't matter I gave mine extension .pcap as .cfa doesn't seem to be associated with anything.

Although I should probably asking Android Engineering that instead, just wondering if I'm doing something obvious wrong by chance? Here's the trace in question: https://drive.google.com/file/d/1TpNnQ7Z39KHwtUgbYPPwRa6zu8JK05su/view?usp=sharing

Wireshark build is current stable 3.4.2 (v3.4.2-0-ga889cf1b1bf9).

Many thanks in anticipation!

Error parsing BT HCI trace created with btsnooz.py

Hi All,

I've just used these instructions and python script btsnooz.py from there to extract BT HCI log (trace) from the bug report zip produced by my Samsung SM-A320FL smartphone running Android 8 Oreo: https://source.android.com/devices/bluetooth/verifying_debugging#debugging-with-bug-reports

Unfortunately Wireshark only displays the first 5 packets and returns the following error: "The capture file appears to be damaged or corrupt. (btsnoop: File has 117440512-byte packet, bigger than maximum of 262144)". I understand that this trace is of some type (extension) ".cfa" but others can still open theirs with Wireshark and I can open theirs too. Assuming extension as such doesn't matter I gave mine extension .pcap as .cfa doesn't seem to be associated with anything.

Although I should probably be asking Android Engineering that instead, just wondering if I'm doing something obvious wrong by chance? Here's the trace in question: https://drive.google.com/file/d/1TpNnQ7Z39KHwtUgbYPPwRa6zu8JK05su/view?usp=sharing

Wireshark build is current stable 3.4.2 (v3.4.2-0-ga889cf1b1bf9).

Many thanks in anticipation!