Thursday, July 28, 2011

Embedded XSD

Looks like it IS possible to embed XSD data inside the XML, meaning we don't need to make an XSD file for each kis/gps xml file we generate.

Expect the new kisxml format to be based on this example:
https://www.kismetwireless.net/code/svn/trunk/xml/contained.xml

which valides with xmlstarlet and seems to output a sane collection of xpaths when dom-parsed:

k:run
k:run/xs:schema
k:run/xs:schema/xs:import
k:run/xs:schema/xs:import
k:run/xs:schema/xs:import
k:run/xs:schema/xs:import
k:run/xs:schema/xs:import
k:run/xs:schema/xs:element
k:run/version
k:run/startTime
k:run/endTime
k:run/captureSource
....
k:run/device/deviceMac
k:run/device/name
k:run/device/firstSeen
k:run/device/lastSeen
k:run/device/frequencySeen
k:run/device/frequencySeen/frequency
k:run/device/packetLink
k:run/device/packetData
k:run/device/packetFiltered
k:run/device/packetError
k:run/device/dataBytes
k:run/device/type
k:run/device/ssid
k:run/device/ssid/firstSeen
k:run/device/ssid/lastSeen
k:run/device/ssid/type
k:run/device/ssid/essid

The extended device elements are cleanly integrated into the DOM.

This file also presents no problems to the Python XML parser ETree, so I think it's going to be fairly reasonable to implement tools using it.

If you handle XML from Kismet, let me know / stop by IRC.

Tuesday, July 26, 2011

Fixing the Droid 3 reboot

Just a followup to the previous post asking for a contact at Moto, and to keep the info out there for anyone with a Droid 3 suffering frequent reboots.

If your new Droid 3 reboots constantly when you're on the edge of cell coverage areas, when turning it on or off, placing it in your pocket, or when using wifi, this seems to be the solution.

The bug appears to be directly tied to the restoration of saved wifi configurations from your google profile.

Go into the wifi configuration screen, go to "manage networks", and remove ALL networks from the list.

You can re-add networks, but you must do it from the droid3 wifi config.  The problem doesn't seem to be the networks, it seems to be the way they're restored.

As from the previous post, the google bug for this is at:
http://code.google.com/p/android/issues/detail?id=18460

which includes stack traces for anyone at Moto who is able to debug the root cause of this and initiate a fix.  It would probably be a reasonable thing to star the bug to raise it's priority, although it seems to be a motorola bug, not a google android one.

Wednesday, July 13, 2011

Looking for a contact in the motorola android division

I've been debugging a nasty reboot/crash bug on the Droid 3 and have logs including the fault address (consistent) and stack traces leading up to it (system_server has a poo, followed by everything else in the android environment).

If anyone works at (or has a contact at) the motorola android division, please, let me know.

Tuesday, July 5, 2011

XSD is a cruel joke

In an attempt to both support phy-neutral plugins dynamically adding logging attributes to the XML and supporting proper validation, the only reasonable path is XSD schemas with namespaces.  For something so extensively documented, it's very difficult to properly comprehend.

Amazingly, it looks like it IS possible to define relatively dynamic schemas, extend existing common elements, and still validate.