Which tablets are supported?
Android 3.1 or above is required. For a list of tablets which are known to work, see below.
There are known USB issues between various tablets / phones and some Garmin models. See here for more.
There are known USB issues between various tablets / phones and some Garmin models. See here for more.
Which Forerunner / Edge models are supported?
- Forerunner models connected through a USB cable (301, 205, 305, 110, 210). Most likely the 10 as well.
- ANT+ Forerunner models: 405, 405CX, 410. You need to set up thing properly: see here for details.
- ANT-FS Forerunner models: 310XT, 610, 910XT, 60, 70. You need to set up thing properly: see here for details.
- Edge 205, 305, 500, 605, 705 and 800.
- Some eTrex, GpsMap and Oregon models are also supported: see here for details.
- Other devices are reported to be working: Astro 200 and Montana.
- The Garmin Fenix is reported to be working, with the right options: see here for details.
Known working Tablets / Devices
Here is a list of tested device / tablet combinations. In some cases (mostly for the Samsung), the Android ROM version can be important. The Garmin Firmware version is reported for completeness, but it's usually irrelevant - if you have a different firmware version, it's very likely that it will work anyway.
Most likely, many other tablets will work just as well. Give it a try, and if you run into troubles, get in touch.
Most likely, many other tablets will work just as well. Give it a try, and if you run into troubles, get in touch.
|
Garmin device
Forerunner 310xt Firmware Version 4.50
Forerunner 310xt Firmware Version 3.70 Forerunner 610 Firmware Version 2.80 Forerunner 910xt Firmware Version 2.70 Forerunner 910xt Firmware Version 2.60 Forerunner 910xt Firmware Version 2.40 Garmin Edge 800 Firmware Version 2.20 Forerunner 110 Firmware Version 2.20 Forerunner 110 Firmware Version 2.50 |
Android tablet
Samsung Galaxy Tab 2 10.1 GT-P5110, Android 4.1.1,
ROM version JRO03C/P5110XXCLK7 Samsung Espresso10wifi, Android 4.1.2, ROM version aokp_p5110 (AOKP) Asus Transformer TF700T, Android 4.1.1 Samsung Galaxy Tab GT-P7510, Android 4.0.4, ROM version IMM76D/UELPL Asus Transformer Prime TF201, Android 4.1.1 AsusTransformer TF700T, Android 4.1.1 Samsung Galaxy Tab 2 10.1 GT-P5110, Android 4.1.2 ROM version JZO54K cyanogenmod Samsung Galaxy Tab 2 10.1 GT-P5113, Android 4.1.1, ROM version JRO03C.P5113UECLK7 Samsung Galaxy Note 10.1 GT-N8010 Android 4.1.1, ROM version JRO03C.N8010XXBLK9 Samsung Galaxy Note 10.1 GT-N8000 Android 4.1.1, ROM version JRO03C/N8000XXBLK4 Asus Transformer TF101, Android 4.0.3 Asus Transformer Prime TF201, Android 4.1.1 AsusTransformer TF700T, Android 4.1.1 Samsung Galaxy Note 10.1 GT-N8000 Android 4.0.4 ROM version IMM76D.N8000XWALI5 Acer Iconia A500, Android 3.2.1 Samsung Galaxy Note 10.1 GT-N8000 Android 4.1.1, ROM version JRO03C.N8000DXBLL3 Samsung Galaxy Note 10.1 GT-N8013, Android 4.1.2, ROM version JZO54K/N8013UEUCMC2 Asus Transformer TF101 , Android 4.0.3 Samsung Galaxy Tab 10.1 , Android 3.2 Asus Transformer TF101 , Android 4.0.3 Samsung Galaxy Note 10.1 GT-N8010 Android 4.1.2, ROM version JZO54K.N8010XXUCMA8 Acer Iconia Tab A200, Android 4.0.3 |
Notes
Requires powered USB hub Requires powered USB hub |
More known working combinations
|
Acer Iconia A500, Android 3.2.1
Garmin Forerunner 301 (Firmware Version 3.20) Asus Transformer TF101 , Android 4.0.3 Garmin Forerunner 301 (Firmware Version 3.20) Asus Transformer Prime, Android 4.0.3 Garmin Forerunner 305 (Firmware Version 2.90) Acer Iconia A500, Android 3.2.1 Garmin Forerunner 305 (Firmware Version 2.90) Acer Iconia Tab A200, Android 4.0.3 Garmin Forerunner 305 (Firmware Version 2.90) Asus Transformer TF101 , Android 4.0.3 Garmin Forerunner 305 (Firmware Version 2.90) Asus Transformer TF201 , Android 4.0.3 Garmin Forerunner 305 (Firmware Version 2.90) Medion Lifetab P9516 (Lenovo K1), Android 3.2.1 Garmin Forerunner 305 (Firmware Version 2.80) Motorola Xoom Wi-Fi, Android 3.2 Garmin Forerunner 305 (Firmware Version 2.90) Toshiba Thrive AT100, Android 3.2.1 Garmin Forerunner 305 (Firmware Version 2.90) Google / Samsung Nexus 10, Android 4.2 Garmin Forerunner 305 (Firmware Version 2.90) Acer Iconia A501, Android 3.2 Garmin Forerunner 305 (Firmware Version 2.90) Toshiba Thrive, Android 3.1 Garmin Forerunner 205 (Firmware Version 2.60) Asus Transformer Infinity TF700, Android 4.03 Garmin Forerunner 205 (Firmware Version 2.60) Asus Transformer TF300T, Android 4.1.1 Garmin Forerunner 305 (Firmware Version 2.90) Samsung Galaxy Tab 10.1 , Android 4.0.4 Custom ROM Garmin Forerunner 305 (Firmware Version 2.90) Acer Iconia A501, Android 4.0.3 Garmin Forerunner 210 (Firmware Version 2.50) Asus Transformer TF101 , Android 4.0.3 Garmin Forerunner 210 (Firmware Version 2.50) Asus Transformer TF101 , Android 4.0.3 Garmin Edge 205 (Firmware Version 3.20) Acer Iconia A500, Android 3.2.1 Garmin Edge 305 (Firmware Version 3.20) |
Acer Iconia A500, Android 3.2.1
Garmin Edge 500 (Firmware Version 2.80) Asus Transformer TF101 , Android 4.0.3 Garmin Edge 500 (Firmware Version 2.80) Archos 101 G9, Android 4.0.3 Garmin Edge 500 (Firmware Version 2.80) Lenovo IdeaTab S2109, Android 4.0.4 Garmin Edge 705 (Firmware Version 3.30) Acer Iconia A511,Android 4.0.3 Garmin Edge 705 (Firmware Version 3.30) Samsung Galaxy Tab 7.7 (GT-P6800, ROM HTJ85B/XXLA4), Android 3.2 Garmin eTrex 30 (Firmware Version 2.80) Samsung Galaxy Tab 7.7 (GT-P6800, ROM HTJ85B/XXLA4), Android 3.2 Garmin eTrex Legend HCx (Firmware Version 3.20) Samsung Galaxy Tab 2 10.1 (GT-P5110, ROM P5110XWALD2), Android 4.0.3 Garmin Oregon 550t (Firmware Version 5.80) Acer Iconia A200, Android 4.03 Garmin GPSMap60CSX (Firmware Version 4.20) Medion Lifetab P9516 (Lenovo K1), Android 4.0.3 Garmin Astro 220 (Firmware Version 3.70) Medion Lifetab P9516 (Lenovo K1), Android 4.0.3 Garmin GPSMap60CSX (Firmware Version 4.00) Medion Lifetab P9516 (Lenovo K1), Android 4.0.3 Garmin Montana 600 (Firmware Version 4.20) Acer Iconia A500, Android 3.2.1 Garmin Forerunner 405 (Firmware Version 2.80) Asus Transformer TF300T , Android 4.1.1 Garmin Forerunner 410 (Firmware Version 2.30) Toshiba AT100, Android 3.2.1 Garmin Forerunner 405CX (Firmware Version 2.40) Asus Transformer TF700T , Android 4.1.1 Garmin Forerunner 405 (Firmware Version 2.80) Acer Iconia A510, Android 4.0.3 Garmin Forerunner 410 (Firmware Version 2.30) Asus Transformer TF101 , Android 4.0.3 Garmin Forerunner 410 (Firmware Version 2.30) Motorola Xoom , Android 4.1.1 Garmin Forerunner 405CX (Firmware Version 2.30) Asus Transformer TF700T , Android 4.1.1 Garmin Etrex Vista C (Firmware Version 2.70) |
It doesn't work on my tablet / forerunner / edge, can you help me?
Sure! Enable the Detailed diagnostics under My options, and send me a copy of the transfer log. Please provide some details about your tablet (model, Android version) and about your Garmin device (model, perhaps the firmware version too).
How do I send a log?
Select "my options" (Sportablet) or "options" (Uploader). Scroll down to Diagnostics, check the Enable device diagnostics box. Go back and try to upload. At the end (whether it succeeds, fails, or if you stop with cancel), you can click the red email log button. Your email app will pop up with the log as a message body. Make sure that your email app is not truncating the log, as it's pretty useless otherwise. Add anything relevant, like your Garmin model etc. Send the email (the address is already there). I'll get in touch.
Can I export my activities to SD card?
YES :-), this is supported in version 1.9 and above. See this blog post for details.
Can I post my activity to Garmin Connect from my tablet?
Yes, see this blog post for details.
Can I share on Facebook?
Yes, see this blog post for details.
Can I track shoes mileage etc?
Yes, see this blog post for details.
How can I speed up the upload?
Android is not terribly fast at reading data from the USB port, and some devices (like the Forerunner 305) always send all the internal data. You can speed up the upload process by periodically removing old data from your device.
Why am I getting a "no GPS track" message ?
The Forerunner has limited internal memory. If you never delete activities, it will eventually run out of space and recycle some memory, by erasing the GPS track of the oldest. Some track data (distance, duration, etc) remain available, and are shown in the activity list. You'll get a "track ok" notice in the activity list when the GPS track is ok, and a "no track" notice when it's not.
Why are distance, duration and / or average speed / pace different between the activity list (or some other software) and the detailed statistics?
The Forerunner keeps an approximate count for total distance, duration, average pace, speed, etc. The real data is stored in the GPS track.
This approximate summary is shown in the Sportablet activity list, and it's also what many other programs show (e.g. the Garmin Training Center). However, once you select an activity, we go through the actual samples, and the result can be different.
Some software choose to always show the approximate counter, but that's not only inaccurate, it's also misleading. For instance, in this screenshot of the Training Center we have a run that is reported for 23:22:52, but the chart shows an actual duration of 23:10.
Once you open an activity, Sportablet recalculates duration, distance, and all the average / min / max statistics for maximum accuracy and consistency.
This approximate summary is shown in the Sportablet activity list, and it's also what many other programs show (e.g. the Garmin Training Center). However, once you select an activity, we go through the actual samples, and the result can be different.
Some software choose to always show the approximate counter, but that's not only inaccurate, it's also misleading. For instance, in this screenshot of the Training Center we have a run that is reported for 23:22:52, but the chart shows an actual duration of 23:10.
Once you open an activity, Sportablet recalculates duration, distance, and all the average / min / max statistics for maximum accuracy and consistency.
I get an error message on my Forerunner 301
(Thanks to Andreas Fuchs for reporting the problem and the solution :-)
Sportablet may fail to get new tracks and display "exception while processing message" in the transfer log panel. The problem is due to some "incomplete" tracks on the Forerunner, which cannot be deleted by standard means. The solution is to perform a factory reset for the Forunner: with the unit off, press and hold the MODE and ENTER buttons simultanously and press and release the POWER button. The screen should turn light gray. Continue holding the MODE and ENTER button until the startup screen appears. Please note that all data and settings on the Forerunner will be erased. Also, before creating a new track make shure you have a GPS fix, so time and date are properly set on the Forerunner.
Sportablet may fail to get new tracks and display "exception while processing message" in the transfer log panel. The problem is due to some "incomplete" tracks on the Forerunner, which cannot be deleted by standard means. The solution is to perform a factory reset for the Forunner: with the unit off, press and hold the MODE and ENTER buttons simultanously and press and release the POWER button. The screen should turn light gray. Continue holding the MODE and ENTER button until the startup screen appears. Please note that all data and settings on the Forerunner will be erased. Also, before creating a new track make shure you have a GPS fix, so time and date are properly set on the Forerunner.
What about an iPad version?
Sorry, it's not in my immediate plans.
