http://talkingandroid.com/2009/11/04/droiddrop-remote-logging-for-android/ Android Development and talk Mon, 08 Mar 2010 18:26:58 +0000 http://wordpress.com/ hourly 1 http://talkingandroid.com/2009/11/04/droiddrop-remote-logging-for-android/#comment-63 Droid Drop – Remote Logging Thu, 04 Mar 2010 23:17:53 +0000 http://talkingandroid.com/?p=126#comment-63 [...] “FC, fuck you!” without those nice people trying to get in touch with you? No more! Droid Drop to the rescue! I didn’t try it out yet but it seems like a pretty useful extension for all of [...] [...] “FC, fuck you!” without those nice people trying to get in touch with you? No more! Droid Drop to the rescue! I didn’t try it out yet but it seems like a pretty useful extension for all of [...]

]]> http://talkingandroid.com/2009/11/04/droiddrop-remote-logging-for-android/#comment-38 Dave @ Datalogging Wed, 18 Nov 2009 05:27:58 +0000 http://talkingandroid.com/?p=126#comment-38 This reminds me of a GPS application for Droid where you can log everywhere you go by just using two buttons and then be able to take that off and use it with Google maps. This reminds me of a GPS application for Droid where you can log everywhere you go by just using two buttons and then be able to take that off and use it with Google maps.

]]> http://talkingandroid.com/2009/11/04/droiddrop-remote-logging-for-android/#comment-36 Diagnosing Sporadic Errors | AndroidGuys Mon, 16 Nov 2009 21:15:53 +0000 http://talkingandroid.com/?p=126#comment-36 [...] First, gather concrete data. Relying simply on Market comments and the like is not going to get you far. Instead, you need to get at the Java stack trace of the crashes in the field. Fortunately, there are multiple tools to help collect that data, from Flurry to DroidDrop. [...] [...] First, gather concrete data. Relying simply on Market comments and the like is not going to get you far. Instead, you need to get at the Java stack trace of the crashes in the field. Fortunately, there are multiple tools to help collect that data, from Flurry to DroidDrop. [...]

]]> http://talkingandroid.com/2009/11/04/droiddrop-remote-logging-for-android/#comment-35 Diagnosing Sporadic Errors « Android Junkies Mon, 16 Nov 2009 20:41:33 +0000 http://talkingandroid.com/?p=126#comment-35 [...] First, gather concrete data. Relying simply on Market comments and the like is not going to get you far. Instead, you need to get at the Java stack trace of the crashes in the field. Fortunately, there are multiple tools to help collect that data, from Flurry to DroidDrop. [...] [...] First, gather concrete data. Relying simply on Market comments and the like is not going to get you far. Instead, you need to get at the Java stack trace of the crashes in the field. Fortunately, there are multiple tools to help collect that data, from Flurry to DroidDrop. [...]

]]> http://talkingandroid.com/2009/11/04/droiddrop-remote-logging-for-android/#comment-34 Diagnosing Sporadic Errors | The Androider Mon, 16 Nov 2009 18:05:07 +0000 http://talkingandroid.com/?p=126#comment-34 [...] First, gather concrete data. Relying simply on Market comments and the like is not going to get you far. Instead, you need to get at the Java stack trace of the crashes in the field. Fortunately, there are multiple tools to help collect that data, from Flurry to DroidDrop. [...] [...] First, gather concrete data. Relying simply on Market comments and the like is not going to get you far. Instead, you need to get at the Java stack trace of the crashes in the field. Fortunately, there are multiple tools to help collect that data, from Flurry to DroidDrop. [...]

]]> http://talkingandroid.com/2009/11/04/droiddrop-remote-logging-for-android/#comment-33 Android Overview - Diagnosing Sporadic Errors Mon, 16 Nov 2009 14:50:53 +0000 http://talkingandroid.com/?p=126#comment-33 [...] First, gather concrete data. Relying simply on Market comments and the like is not going to get you far. Instead, you need to get at the Java stack trace of the crashes in the field. Fortunately, there are multiple tools to help collect that data, from Flurry to DroidDrop. [...] [...] First, gather concrete data. Relying simply on Market comments and the like is not going to get you far. Instead, you need to get at the Java stack trace of the crashes in the field. Fortunately, there are multiple tools to help collect that data, from Flurry to DroidDrop. [...]

]]>