Software release 2.30.26

duffman19

Is it worth pointing out small UI bugs in this topic? Should there be a separate topic for these? I know we’ve got one going for the black grid problem, but I’ve found a handful of much less serious inconsistencies and am wondering whether it’s worth posting them. If so, here are a couple more:

On iOS, Calendar notifications are labelled as missed calls with the “red phone with X” icon. Not sure if this is also true on Android.
The Control Panel no longer shows phone connection status. IIRC, on the previous SW, the Bluetooth symbol was present when connected.

(From Above)

When in the Widgets menu, swiping right returns to watch face, but the watch face comes in from the right. It should come in from the left to follow the swipe direction.
Long press of bottom button defaults to the Alarm Clock in Control Panel, rather than to the top of the menu.
Scrolling issue: When viewing activity stats (after ending), and in the Sleep, Sunset/Sunrise, and Training widgets, pressing the down button jumps down about half way through the menu, skipping over the top few listings. Doesn’t appear to happen when using the touchscreen.

I’ll stop posting these here if it isn’t helpful. I know there are other more pressing issues for some.

Ketoohs

Another possible bug.

I did a structured workout using TP. The main part was 5x1000m. At the fourth interval I could not hold the pace at around halfway 540m so I pushed the lap button. Jogged the rest of the interval 460m and the rest period notification came normally and the fifth interval, rest and cooldown.

But when I checked the app that 460m is designated as 1000m and the summary of manual laps is greater then the whole workout.

gone troppo

Loving the new resource’s algorithm for the first time ever I actually get results near 100% when I wake up instead of 60-70% and the graph during the day is much more believable well done suunto

GiPFELKiND

@gone-troppo hey why is the ressources now higher? check your watch… before the update your ressources was 50% after softreset or charging your watch on cable. now it is 70% starting after charge on cable or do a softreset only numbers are changed…

Frederick Rochette

Hi All,
I confirme that there no sync between the watch and SA for CTL / ATL / TSB / TSS… also the TSS is always superior on the watch.
I have to soft reset the watch each time for having the same for both. This is not acceptable.
And when I do soft reset the ressources are restarted at 70%… why?
And several times by day I have to recalibrate the compas…
Hope that will be fixed very soon.

GiPFELKiND

@Frederick-Rochette said in Software release 2.30.26:

And several times by day I have to recalibrate the compas…
Hope that will be fixed very soon.

This is since the vertical goes on the market this year in May … Since theere no positive news about that. All write here they will be chanced, but nothing happened…
and i am totally with you the missing Actualisation from TSB, CTL is very frustrating… cause this week we had the BIG UPDATE from the vertical… seems nothing is working…

@GiPFELKiND that’s actually a valid point. After the upgrade it was 70% instantly and since then I have not managed to go to 0%. So when I gain resources during my sleep they are every morning close to 100%. That’s just my observation.

GiPFELKiND

@tomasbartko said in Software release 2.30.26:

@GiPFELKiND that’s actually a valid point. After the upgrade it was 70% instantly and since then I have not managed to go to 0%. So when I gain resources during my sleep they are every morning close to 100%. That’s just my observation.

yes and that is supposed to be a new Suunto internal special algorithm? I dare to doubt that… that is predictable and so reproducible… just like the lack of the correct TSB and CTL data. It’s nice that others notice what has been created here again.

jjpaz

@Frederick-Rochette Sync is working without reboot but one day later. If you verify your watch data it corresponds to yesterday data on SuuntoApp.
So tomorrow you’ll have today’s data on the watch.
Very visual feature but unusable.

The curious thing is that no tester has detected it in weeks of testing and it was reported in the Race when it was launched.

Michaël POINTEAU

@Dimitrios-Kanellopoulos
Have I dreamed? I thought that when going to the watch activity logs, we were able to see lap table?
And no longer with the update I made today…

No really sure about that.

Stoke80

Since the update I dont get the messages when I reach my daily goals for steps and calories.

Additionally I didn‘t get the weekly summary tonight, which normally is shown at 9pm on Sunday.

And also, the function „delete all messages“ does only delete the messages on the watch, but not on the mobile.
Not sure if this is a bug or „works as designed“ ?

Jonathan C

@Michaël-POINTEAU they are now organized behind the overview screen instead of separate pages. So you will have to go to the section with “automatic laps” or “manual laps” and click the middle button to get to the tables.

gone troppo

@GiPFELKiND

I don’t understand this incoherent mumble. I’m saying the resources now reflect how I feel. They have also fixed calories burned during the exercise now much more realistic

BastMaSVSRS9PP

@gone-troppo I have same experience as you. Ressources appear to reflect much better how I feel with regard to my energy levels. This also includes how the resources look like after a bad vs good night of sleep. I agree it’s well done.

Michaël POINTEAU

@Stoke80 post update I got the weekly report.

Maryn

TSB, CTL, TSS, and other metrics in watch are one day delayed comparing to the app.

Current activity isn’t visibile in TSS chart in watch.

Suunto App beta iOS.

wmichi

Suunto has done a great job in bringing some (or maybe all?) bugs from the Race to the Vertical. And some of them are so obvious, you just cannot oversee them. The problem with TSB, CTL,… was the first thing I noticed and all I needed to “test” this, was looking at the app and the watch.

I think all of this is known to Suunto and the people testing these devices. If not, there would be something seriously wrong (I don’t think it is). Suunto simply ignored those bugs and released the update (to fix more serious bugs I guess). If known bugs are released as part of a firmware update, it would be nice if Suunto would add a “known issues” section to release notes, at least here in the forum. I think this transparency would be appreciated by users. If you release beta software, at least respect your users.

Please don’t understand this is as ranting. I have the impression, that Suunto now really started to bring their products forward with a lot of new features. For me it’s clear, that this also means more bugs. I am just asking for more transparency.

nseslija

@Jonathan-C thanks, I haven’t noticed that…

pilleus

@wmichi said in Software release 2.30.26:

If you release beta software, at least respect your users.

It would be a step into the right direction to introduce an official beta software program, so that the experiences of the users who are willing to participate could be collected and bugs could be removed. I would appreciate providing weekly snapshots of the beta firmware and would be interested to test those snapshots on my watch.

But in the current situation, I’m no longer willing to accept the bugs and to wait an indefinite period of time for improvement. That’s why I’m now sticking with my SSU, which was just as flawed when it was introduced and only became a usable watch after several updates.

Both Verticals (I wanted to choose one of the two, Solar or not) are being returned to the dealer today and I will stay tuned and follow the experiences of the users and I’m waiting now to maybe decide on one of the new watches in the future.

And last but not least, I notice an increasing rejection of justified criticism here in the forum, which I absolutely don’t like.

Maryn

@pilleus I also have an EPIX and I can say that the beta program has done a lot of good for garmin. The garmin devices at least those in the fenix/epix line really work stably and don’t have such obvious bugs.