Garmin 20 Character Product Serial Number
1) Navigate to the Garmin folder on the unit (your exact drive letter will vary), and within it you'll find the 'startup.txt' file. Simply double click it – it'll open in. Another racer had found my 510, called Garmin to give them the serial number and was put in touch with me. I received it a few days later and sent.
Model: Fenix 5 Sapphire Serial Number: 53A008. FW: 4.02 beta GPS Issues: NO BT Issues: NO (Sometimes my Bluetooth on the phone switchs completely off. Haven´t had this ever before. Seems that the Fenix 5 goes in a sleep mode and switchs the bluetooth on the phone off.
Don´t have any other idea. Oneplus one with AOSiP Android 7.1.1) ANT+: Don't know (heart rate strap works fine) Phone: Oneplus one with AOSiP Android 7.1.1 Region: Europe My main issue (without any Garmin-help so far): the calculation of total ascent and descent is wrong (but the Fenix records a pretty very good altitude profile.because basecamps shows pretty good dates for ascent/descent). Model: Fenix 5 Sapphire Serial Number: 53A0014.
FW: 4.10 (9adafd9) GPS Issues: NO BT Issues: NO ANT+: I use the Garmin footpod during running, always connecting fast and logging data Phone: Motorola X Force Android 6.0 Region: Europe wearing it 24/7 since mid-march. Great device. Dbz Torrent All Episodes. I run +/- 60k per week. Done a full marathon with it, casual bike rides and hiking. Bath, shower, hot, all not a single flaw.
Automatic timezones work very fast I noticed during my travels. Distance My Demons Rar Files. Two weeks ago I had a unexpected reboot during navigation back to a waypoint in a 15k run I was recording, total surprised that the device just went on recording after the reboot, no loss of data My black case is a little bit scuffed but it also gives the device some character. Visit to the 508 meters tall Taipei 101. So, recieved my replacement watch 2 days ago. I RMA-ed my F5 (number 3 in table) due to very short (3-5 meters) range and frequent BT drops (connection with the phone).
As I expected, I only wasted my time (and time of those garmin folks who had to process the RMA), as the 'new' watch has exact same issues. I'm now wondering, how can we get any official statement from Garmin, explaining the laughable range of BT in F5? Why would you even need 'find my phone' or any 'smart' notifications if the connection drops once you're five steps away? Loads of my friends decided not to buy F5 after seeing me constantly toggling BT in my phone. Updates for the table: 'New' watch: Model: F5 slate Region: EU Serial Number: 5360479XX FW: 4.10 GPS Issues: none ANT/ANT+ Issues: never tested BT Issues: drops, range 5m WiFi Issues: N/A Phone: Sony Xperia Z1 Compact Update for RMA-ed number 3 in table: Model: F5 slate Region: EU GPS Issues: none ANT/ANT+ Issues: never tested BT Issues: drops, range 5m.
Ok, so I thought I'd contribute to this table as I've finally been able to test ANT+, and it's been a bit disappointing Model: F5 Sapphire Region: EU Serial Number: 53A0153. FW: 4.10 GPS Issues: none ANT/ANT+ Issues: Drops my speed cadence sensor and super short range on HR compared to my old F3. No issues with power so far. BT Issues: none (only tested with phone, no sensors) WiFi Issues: SOO SLOW!!! Practically useless!
Phone: iPhone 5S My biggest annoyance is that my Edge 520 is so quick to sync my workouts that I've usually not even been able to dismount my bike before it's done. My F5 Sapphire needs at least 10 minutes to sync the very same workout. Also, the OHR is complete garbage for cycling and cold weather running on the F5.
In my case the OHR fails below +10C while running. Anyone picking up a trend yet? Yeah, looks tricky - certainly more Android devices than iPhones. But, we also need to define 'issue'. Speaking for BT, there are 2 for me (and guess for others) 1. Too short range (3-5 meters, straight line, open space, no walls), which makes any 'smart' features unusable 2. BT connection drops within short distance to the phone (less than 1 meter) It looks like in my case, those connection drops (issue 2 above) were 'almost' resolved by re-flashing my Sony Xperia Z1 Compact completely to default (deleting all settings, internal storage wipe etc.).
It now happens maybe once per day. So, it was either Android, or GCM in my case. The range issue still stands - but I fear that for majority of F5 users the BT range is not a problem as they only use BT to synchronise and not for notifications etc.