Usually it is not necessary to use a high amp charger as the charging circuit in the watch will never allow high currents anyway. If the battery is in deep discharge then a state of the art charging circuit will trickle charge it until it can come back to a normal charge. This is why it can take a long time on the charger until he device comes back to life. Thus the recommendation for deep discharged devices is: leave it on the charger for a longer time. I would only call it defective if it does not come back after a day or so. This does not solve the initial high discharge though…

Thanks @Nigel-Taylor-0. I’ll set the middle button to bring up the alarm app and try that tomorrow. Thanks!!

@saq10is - remove your profile form the GFit app, as you don’t get any benefit from using it (unless there is a specific reason you want it…) Since Sept 20 update to GFit where they changed how the sync works - data is often delayed and or never populates the GFit app, plus with recent API changes some data like HR will not now sync. GFit also now seems to recalculate steps and calories. So unless you have some specific need of GFit that the suunto app doesn’t already cover, would suggest removing profile to solve any GFit issues by not using it. PS - daily details missing on Suunto app - assume that you could see those details on your watches today widget i.e. it is actually recording steps?

@egika very good point - should have added that. And completely agree with you that certain activities shouldn’t generate steps. @Marco-G --> I think you will find that what Egika has said is correct, and that is the way it should be. You might find that any indoor activity doesn’t include steps, as would only be able to count them via movement sensors, which is unlikely to be accurate, however if outdoors, then yes activities like that may count steps. But yes agree water sports, cycling i.e. activities where you aren’t actually making steps shouldn’t count towards steps. ps - Garmin does the same - missed my step target on days I went cycling and swiming as neither days kms counted towards steps (and correctly so).

@jamie-bg i did see that post from Google (although after my other posts on here). I’m inclined to believe a bit of both of them, but also think that they are both covering their own backsides. Yes, it is likely that the 3100, 4100, and 4100+ can run WearOS 3. But will they run it well? If a watch runs it badly then it will damage the reputation of the OS and the hardware. In fact, WearOS 3 could be dead on arrival if too many devices run it badly. Obviously Google wants as many devices as possible to run it, but they want, no, they NEED it to run perfectly. This is likely their last chance to take on the Apple Watch and if all of the initial reviews are that it runs like a dog then it’s game over. Consumers won’t take into consideration that the hardware is old, they will see the headlines that WearOS 3 is slow and that will be it. Qualcomm however, don’t care two hoots about WearOS (i think that have become obvious over the years). All they care about it selling chips, saving reputation, and saying they are market leaders. So if their older chips are no longer supported then it hurts them as a company. Qualcomm would put WearOS 3 on every chip they ever made if they thought it would benefit them, but sod the customer, as long as it makes them money. Google want (and again, NEED) WearOS to run perfectly, so they should be pushing for it on only the absolute best hardware. As good as the 3100 is and as good a job Suunto have done with it (which they really have!), it is old, slow and power hungry. There is no point having the amazing Suunto App if the OS underneath it is running slow due to the hardware. IF (and it’s a big if) the 3100 can run WearOS 3 well then I would expect Suunto to support the S7 for quite a while yet. However, if it runs with even the slightest lag then Suunto need to keep the S7 on WearOS 2 and get a new model out ASAP. As I mentioned before, the average consumer already considers the TWP3 better than the S7 purely based on it having the 4100 (despite there being no notable improvement in having that chip). The S7 is already over 18 months old, so is long in the tooth in the tech world. I personally think a 2 year cycle for something like this is perfect, as it allows each iteration to have noticeable improvements and ensures support from manufacturer. However if Suunto are too late to the WearOS 3 party then they could lose out on sales. A newer S7 (whatever it may be called) with Samsung silicone, better battery life, reduced bezel, lighter, slimmer, etc with still the Suunto smarts inside (and with continued updates) could be the WearOS device to beat and with proper advertising (and a sensible price unlike the S7 at launch!) could take a serious chunk of the market. Just my thoughts for this wet and soggy British morning

@дима-мельниченко you shouldn’t to wait, the routes transferred over straight away for me. As in, i click save on desktop, unlock phone and opwn Suunto App and the routes are there. It’s genuinely amazing how fast it is. I love plotaroute! Simply love it! But getting routes across to Sunnto is a bit of a faff - download the gpx file to my desktop, upload to Google Drive, open Suunto App on phone, upload gpx file in from Google Drive. It’s a first world problem, but it’s more of a faff than the Komoot auto sync. However, The ease of the Komoot auto sync is undone somewhat by the sheer insane amount of waypoints it plots! I get having a waypoint where there is a change in direction, but when I run past a turning I do not need a waypoint telling me to “Continue Straight” as I will do that until told otherwise. So the time I save by using the auto sync is completely undone by having to remove roughly 80% of the auto generated waypoints. Again, this is all first world problems and either of these options are still better (for me) than creating a route within the Suunto App on the phone.

@isazi ticwatch pro 2020 has that feature (but It is still to far away from our watch )

@giulio i just got THE update

@amasidlover said in Fear and loathing in Amsterdam: or Garmin will add a WearOS co-process to a Fenix… As one friend of mine used to say, it it were that simple, it would be sitting on a shelf at Walmart for $3. Fenix is incompatible with WearOS from the ground up. Basically, Garmin would have to abandon what they currently have and spend upward of a year or two catching up to where Suunto is here and now. Worse still, having all these bells and whistles, aka features, means a bulk of them will have to be ported too. Otherwise, it ain’t be Garmin. Look at the flak Suunto is getting for leaving features out of Suunto 7. Imagine tenfold of it for Garmin. Worse still, they can’t just abandon ConnectIQ and will have to continue to bleed cash on it because it already made its way into Forerunner and other series. For now Fenix and other high-end watches underwrite further development. It will become a much tougher proposition once left to mostly Forerunner line.

GPS and OHR worked really well : https://beta.quantified-self.io/user/88tGXoxa0YOtAw07abZo8jK8mN93/event/3cPQA91MbTn2CvY9nukbwvqsE5BRQodXKmw79U2Pe41tGmy

@NickK it was already available yesterday but there is no way to order it, although it is stated as in stock. Really strange. Anyhow, the watch should arrive on Monday, I still have to try and evaluate it. Still a question mark around the size. Never had such a big watch. I have a suunto elementum ventus already but it is smaller. When I decide to keep it, I will look again at the spare charger. Thanks