New backlight levels in 2.26.8

[Dimitrios Kanellopoulos]

Isn’t there standby light ?

[inkognito]

@Dimitrios-Kanellopoulos Yes, there is. But that does not solve my “problem”: I do not need (or even want) any backlight most of the time and when I need it, I want it to be low enough… Also upon any button press, backlight would go from Standby level to newly increased “Low” (that is not really low anymore for me)…

The only solution for me with 2.26.8 is probably to use DND (which also decreases backlight), but then I lose alerts and notifications…

I have a crazy (or even utopistic) idea: the level of “Low” backlight has to be defined by one simple variable in the code, no? Cannot somebody compile lets say “2.26.8.1859-F” firmware with that variable set to 10% instead of the current increased value?

[Dimitrios Kanellopoulos]

@inkognito I wish I could

[Łukasz Szmigiel]

Let’s have a custom FW generator where users can set their own values into variables

[inkognito]

@Łukasz-Szmigiel That sounds way too anarchistic For starters, let’s introduce the very novel backlight implementation where user can choose any backlight intensity in, let’s say, 5% steps… Improved readability and satisfaction guaranteed… Oh wait, we already had this…

[Dimitrios Kanellopoulos]

@inkognito I hear your concerns. Please do also raise this with support.

[Łukasz Szmigiel]

@inkognito yeah finding a good balance between too much and too little is hard.

But you have my vote for more detailed settings in regards to backlight and haptics. Ideally split into in and out of workout.

[inkognito]

@Dimitrios-Kanellopoulos I don’t know if I really want to contact support with this or anything else ever again… I thought we have this forum for such things…

I contacted support like 10 times in the past 5 years… Literally every case went like this:

1. I clearly described my issue/suggestion, stated important details and/or all the things I tried to solve the problem (soft reset etc.).
2. Support paid attention only to every third word and started with obivous things I already knew (like “try the soft reset” even when I specifically stated that I did that and it did not help).
3. Then I tried again and again, trying to persuade them that I know what I’m talking about… Support still reacted like I was a noob…
4. In the end, they replied that they’re pushing the issue further… After that nothing ever happened…

Honestly, this was extremely demotivating every time…

[Łukasz Szmigiel]

@inkognito been there, done that.

[Brad_Olwin]

@inkognito How do you know nothing happened. I agree you were not contacted but you should not assume nothing happened.

[inkognito]

@Brad_Olwin Let’s say “nothing effectively happened”. Unfortunately, the effect or result is what matters the most for user.

E.g. here are some bugs I discussed with support during last years

1. S9/S9B: Scroll down to “Training” (that round progress circle with weekly goal) and swipe to the side until you reach that little chart with duration of activities in this and last 3 weeks. First you see values for all activities titled “All activities” (e.g. for me it shows 8:31h 3 weeks average and a chart). If you tap the screen, it shows charts and values for selected individual activities (for me the first is waking with 2:33h 3 weeks average, title is “Walking”). And now, from any of those individual activities, swipe back to “Training plan” and forward. Now it shows chart and values related to the individual activity (2:33h in my case), but the title is “All activities” (instead of “Walking” in my case). Reported years ago… Still there…

2. When I had my Spartan Trainer, I bought a “Wahoo RPM Speed” bike pod. Every time I used it and paused my activity, it added some random distance… There was clearly some bug… I reported this multiple times to support, provided logs and links to activities and occasionally checked whether the bug was solved… After 3 firmware updates I simply stopped checking since nothing happened… Meanwhile I read about other people having the same problem and fighting with support that does not seem to acknowledge the issue…

3. Remember call notifications that were never deleted from S9? Right now I see zombie notification from phone call I missed 35 hours ago…

4. Remember crashes at the beginning of activities several months ago? It took a long time until support even acknowledged the problem. People were already discussing it here, on facebook and reddit for a long time, many stated that they reported it to support… And support always acted like they hear about it for the first time…

I know that things are not easy for support and that there are things of various priorities. But I feel that I wasted hours contacting support for no effect…

Why should I do it now when the probability of a change is negligible (especially for 5 years old model)?

I know that these “complains” are not constructive at all… Problem is that every time I tried to constructively discuss with support, I did not see any results or outcome apart from feeling that they don’t trust me…

[olivier.cornelissen]

@inkognito
If you set brightness to low and activate energy saving settings, it seems to be the same brightness as before. Wouldn’t that solve your issue?
M

[inkognito]

@olivier-cornelissen Start an activity and see for yourself Backlight will increase immediately once you choose any sport…

[A Former User]

@inkognito said in New backlight levels in 2.26.8:

@Dimitrios-Kanellopoulos I don’t know if I really want to contact support with this or anything else ever again… I thought we have this forum for such things…

I contacted support like 10 times in the past 5 years… Literally every case went like this:

1. I clearly described my issue/suggestion, stated important details and/or all the things I tried to solve the problem (soft reset etc.).
2. Support paid attention only to every third word and started with obivous things I already knew (like “try the soft reset” even when I specifically stated that I did that and it did not help).
3. Then I tried again and again, trying to persuade them that I know what I’m talking about… Support still reacted like I was a noob…
4. In the end, they replied that they’re pushing the issue further… After that nothing ever happened…

Honestly, this was extremely demotivating every time…

I may be mistaken, but the “weight” of a claim (or various ) via a support line vs a forum may be different. With support lines I believe there will be a better quantification of how many people had the issue.
With Garmin is similar, we report the bugs on forum, but once you contact support and open a ticket I have the feeling that it creates much more awareness and things go solved faster.

But I understand your frustration. Fortunately the times I contacted support were not for big issues, but yes the answers were a bit on the basic side (reset). But in suunto’s (or other brand) defense, this approach maybe solve 80% of the issues.

[inkognito]

@André-Faria Yeah, I get that.

And I fully agree that my overall feeling about support is probably massively influenced by the fact, that I always try everything possible first and contacting support is just the last instance when nothing really worked…

And I also know that for the majority of everyday problems (like where many solutions can even be found in the manual that nobody reads anymore ) support might do a perfect and effective job.

[Tomas5]

@inkognito something similar happend with S5 two years ago. With new rise to wake feature, toggle backlight was removed. Prior that update, during night with DND enabled, backlight was very dim and it was perfect. After update it changed to full backlight after every button press. And only possibility to force dim backlight at night is enable powersaving but at costs of loosing hr tracking.

[Sanandres]

@inkognito The new “low” mode in “raise to wake” does not solve your problem?

[inkognito]

@Sanandres No, it doesn’t. I don’t want any backlight most of the time, so there’s no reason to drain battery with raise to wake.

And when I need to interact with my watch, I want backlight to be low. Upon any button press, backlight would still increase from “Raise to Wake” level to newly increased “Low” that is not low for me anymore.

[MaTroskinas9]

@inkognito so you accepted this " backlight improvements" as it is or downgraded to 2.23.20 ?

[inkognito]

@MaTroskinas9 Since the days are long now where I live, it is not a big deal now… I only went for two hikes very late at night and decided to use Do not disturb mode to decrease backlight (I did not expect any notifications around midnight anyway ). But this improved “low” backlight will become really annoying for me starting from autumn… If nothing happens by then, I will probably really downgrade…

Furthermore, my S9 now crashes from time to time and trying to find some pattern there is great fun