Hello Mk1 community, first post of I'm sure many, just got my Mk1 and will be diving with it weekly and will try to help developers with any feedback I can provide, so entering tank pressure when on PSI it will take you 45 minutes rolling thru to get to 3700 , this is at least on android version ciq.forums.garmin.com/.../1359237.jpg
I have sent several emails to garmin hoping to fix this issue but to no avail. You'd think it would be a simple fix to the app to be able to input numbers manually. Only way I have found is to get onto the computer and input the pressures there.
That whole Edit Gas Details is screwed: * You can't put decimal places in for tank size: my tanks are 10.5L, 12.2L and 15L - That makes a difference when calculating SAC. * It doesn't give you decimal places for average depth - That makes a difference when calculating SAC * It doesn't automatically calculate the SAC * Entering the SAC manually is a joke because again it doesn't allow decimal places. My SAC with a 12.2L tank is between 0.9 and 1.5 bar/min so no decimal places makes it meaningless.
The same issues happens with the dive number. It takes forever to scroll.
I assume the Garmin Connect Mobile interface is written by a different team but I suspect they have never even learnt to dive let alone have been on a dive.
Connect is a universal interface for all Garmin outdoor and sport products. So while it can track your steps, weight, HR, Cycling, Hiking, Running, Climbing, Swimming, Diving, etc activities, it really does not do a great job on any of them. For the Cycling world, and I think running, they can automatically sync with Strava which does a great job on these activities. I suspect their plan is to do the same with Dive Activities, but given how slow they are on fixing issues with the Descent I would not recommend you hold your breath on this.
Only we aren't talking about missing features here. These are "features" that Garmin have provided that don't actually work. It would be better to not have SAC at all that have a a field that is useless.
Hello Odie, Mark, Tony,Atj, I just wanted to kind of check with everyone but at least for me when I purchased the Mk1 i was well aware (been reading this forum and others) that the watch is at infancy state of development and I was and still am ok working thru its i am sure years to come worth of updates, it has tons of potential, i was part of android first launch, i activated the very first android model which was a Tmobile G1 on the morning of its launch and can tell you has come a long way :) we all have purchased dive computers and know they are not cheap this one has a lot more to offer at this state than others that's why i made the choice to purchase. I am static with the watch and look forward to see it evolve, lets all try to be constructive and help its development Atj has some great feedback, very very cool
I expected some issues, but also expected Garmin would address these in a timely manner. Which frankly is not happening. And some of the issues are just so stupid it makes me wonder if they actually tested the Descent in dive mode. In particular adding the end of dive timeout to the dive time, or the compass only pointing to True North (which has been fixed). I also purchased a Shearwater Perdix when it first came out, granted this was based on the Petrel 2, but there were only minor bugs which were fixed almost immediately. Garmin has only fixed two minor bugs, and cannot communicate a plan for what issues they will address, when they might be addressed, in fact they pretty much ignore all input from their user community.
I think the Descent has great potential, but Garmin needs to get their stuff together on the software side. For the record I was very positive about this early on, but Garmin has managed to make me a bit more negative with their lack of responsiveness and piss poor support.
I am struggling to understand those 2 issues matter in bigger scheme of things.
Dive delay- how does it affect anything physiologically? Might be annoying to get your surface location incorrectly, but I suspect it is a design compromise as one can't get GPS signal reliably while bobbing in the water.
True North - Modern instruments point to TN, such as in aircrafts and consistency is required. Regardless, where you dive (Monterrey) magnetic declination is 10m over 100m swim in a straight line. Now which use case you can't address with TN compass?
Currently, Garmin is the only smart watch with dive capabilities. Comparing it to another dive computer in terms of complexity is not an apple to apple comparison,
I am struggling to understand those 2 issues matter in bigger scheme of things.
Dive delay- how does it affect anything physiologically? Might be annoying to get your surface location incorrectly, but I suspect it is a design compromise as one can't get GPS signal reliably while bobbing in the water.
True North - Modern instruments point to TN, such as in aircrafts and consistency is required. Regardless, where you dive (Monterrey) magnetic declination is 10m over 100m swim in a straight line. Now which use case you can't address with TN compass?
Currently, Garmin is the only smart watch with dive capabilities. Comparing it to another dive computer in terms of complexity is not an apple to apple comparison,
If you taught students, you’d understand. Very few affordable dive computers are on the market that have an integrated digital compass on board that may have the ability of choosing between TN and MG (most that I know of don’t), so students and/or regular divers use a standard compass (wrist or integrated in their console) that points too...wait for it...Magnetic North! The cost of an UW compass is $40-60 bucks, much more affordable for divers.
The EOD delay should be corrected and not have that delayed time be added onto the dive time. In a previous post of yours, you claimed to have 1000’s of dives under your belt. Assuming that is correct, how many “hours” would you have that would be “false”...yes quite a bit. So yes, that does need to be fixed.
