Instrumentation of Batphone to assist field diagnosis

[gardners]

We need to be able to easily allow a user to collect information such as:

• the output of batmand -cd1
• the output of logcat (possibly filtered for batphone related tags?)
• output of tcpdump (including packet bodies?)

and anything else we might need to gather so that we can figure out what is going on with problems that people report. It would be nice to have a way to automatically upload this data as well, or encrypt it and offer it via Rhizome so that it can be easily collected to a central point during a test.

Mantis severity: major
Mantis priority: high
Mantis project: Core Project
Can reproduce: N/A

[gardners]

Originally reported as mantis:0000140 at Wed Nov 16 14:40:59 2011.

[quixotique]

Issue migrated from Mantis to GitHub with Mantis status assigned and resolution open at Fri Oct 19 18:43:39 2012 using sp-mantis2github version 1.1

[lakeman]

Note, batman is no longer supported.

[quixotique]

Much of the back-end functionality required to resolve this issue is addressed in servalproject/serval-dna#36. The extra work required for Batphone will be:

• Write a Serval logging interface and re-factor all existing logging statements to use it.
• Implement the new Serval logging interface, encapsulating the Android Log “tag” strings and logging some messages via servald instead of directly through Android.
• Implement a way to inject the logcat buffer and other environmental information into a diagnostic bundle sent by servald.
• Replace the existing crufty log view activity with a new activity that provides filtered views of the Serval logs.
• Implement a new activity for setting all the debug flags by symbolic name. This will require a new servald command for listing all the available flags. This activity could eventually expand to allow direct Here Be Dragons” viewing and editing of the entire servald configuration.

[quixotique]

Originally reported as mantis:0000051

[quixotique]

As per mantis:0000144 Need an activity display that asks a user for permission to upload diagnostic information to ServalHQ:

If chipset detection fails, or if we need to upload diagnostic information for some other reason, we should ask the user for permission first. This should be a full-screen, i.e, activity, that displays the diagnostic data in a text area and asks if we can up load it. Two buttons "submit data" and "do not submit", each of which close the activity, with the former first uploading the data to serval HQ. Should probably show the URL the data is to be sent to, possibly with some futher explanation/privacy policy stuff.

[quixotique]

Originally reported as mantis:0000144 at 2011-11-22.