From: Jason Jordan Date: Fri, 14 Jul 2006 04:27:40 -0400 (EDT) Hi Gavin, Over a year ago I more or less did the same thing you did, which was to analyze the Navini packets as best as I could. After putting in many hours over several days, I had most of the statistics figured out. My data looked very similar to Matt's data as seen on your webpage. However, some things (such as overall S/N ratio, distance to BTS, etc.) still escaped me. Then I had the idea of trying to decompile the jar files in the Navini distribution. I wasn't optimistic it would work, but within minutes, I was staring at the algorithms used to calculate all statistics. Victory! This should give you (and others) a huge jump on an open source tool. I have some custom monitoring software, but it is strictly home-brew and nowhere near release quality. Anyway, here's how I did it: 1. Install Navini Diagnostics somewhere, say /usr/local/navdiag 2. Install Jad: http://www.kpdus.com/jad.html 3. Create a directory to hold the source files: % mkdir /path/to/navdiag_source % cd /path/to/navdiag_source 4. Unzip the class files from the following jar files: % unzip -d ctl /usr/local/navdiag/data/lib/ctl.jar % unzip -d navDiag /usr/local/navdiag/data/lib/navDiag.jar 5. Decompile the class files: % mkdir decompiled % find ctl -name '*.class' | xargs jad -r -d "decompiled/ctl" % find navDiag -name '*.class' | xargs jad -r -d "decompiled/navDiag" That's it. Now go digging around the decompiled subdirectory for the goods! It's been a long time since I've looked at these files, but let me know if you have any questions, and I'll do my best to answer them. :-) Have fun, Jason