Started work to restructure how I handle not driving events.  I'm moving most of the code out of the GetCurrentLocation class and making that just a location listener.  I pass it a MessageHandler reference so that when it gets a decent fix for location it can send a message back to the ActivityRecognitionIntentService.  I may move this even further back into the ActivityRecognitionService.
Moved most of the database and path recording code up to the ActivityRecognition service.  Something broke and I'm stupid apparently.
Updated database version
Re-wrote how services ar handled.  The first ActivityRecognition service starts the others and then waits for messages from them.  All the business logic has been moved into this class.
Modified how the program works so that it can have persistence variables.  The new TripVars class creates a Serializable construct that I can stash variables in.  The ActivityRecognitionService now doesn't do much other than register an Intent(ActvityRecognitionIntentService) with the system to get updates about what you're doing.  All the business logic to track what you're doing and record it is now in that class.  This is the last commit before I rip out a huge amount of old cruft so that I can clean all of this up.
I ripped out a ton of code that was no longer needed or being used.  This is much cleaner and easier to understand now.  Probably broke a lot of stuff so now I get to work on fixing it.
Fixed all of the problems so that when you click on the Notification that's generated when entering or leaving a fence it correctly displays the information about your trip.  This definitely needs some refinement to display more information as well as giving the user some options about what to do with the data.  I also modified the SQLite tables to better reflect what I care about.  It now save all trip segments regardless of whether or not they were business related so I can use them for distance lookups.  Not only does it save them but there is now a boolean trigger that lets the program know whether or not they are business related.

I created a new table that holds information about Trip groupings.  This table tracks when new trips are started as well as when they're over.  It has two columns, one as a unique identifier for each trip group and another detailing when it's closed.  The one that details when it is closed is accessed by a foreign key in the TripTable so that when you close a group it automatically closes all related path segments.

There is a new class that handles creating Trip Rows.  It automatically handles whether or not your trip is closed as well as handling inserting new data.
Merge branch 'master' into Major_Refactor

This code is much much cleaner, going to make it the new master branch.