lichess.org
Donate

Mobile App Alpha

Preferences: Sound when time gets critical

Not every single move!

Again, the old app is perfect: sound just once, when time gets critical the first time. Don't repeat the sound every next move, it's useless and stressful.

> Preferences: Sound when time gets critical Not every single move! Again, the old app is perfect: sound just once, when time gets critical the first time. Don't repeat the sound every next move, it's useless and stressful.

Guys, is the sound bug fixed yet? When playing with sound on, the animation is buggy and is very distracting/tilting.

Guys, is the sound bug fixed yet? When playing with sound on, the animation is buggy and is very distracting/tilting.

@MarkIorio said in #151:

Preferences: Sound when time gets critical
Not every single move!

No change in the last beta. Please, guys, the critical time notification is NASTY! What's the point to harass the player each and every single move? It's scary! Why didn't you just copy the old app behaviour? Make a sound just once, that's all we need.

@MarkIorio said in #151: >> Preferences: Sound when time gets critical > Not every single move! No change in the last beta. Please, guys, the critical time notification is NASTY! What's the point to harass the player each and every single move? It's scary! Why didn't you just copy the old app behaviour? Make a sound just once, that's all we need.

@MarkIorio said in #153:

No change in the last beta. Please, guys, the critical time notification is NASTY! What's the point to harass the player each and every single move? It's scary! Why didn't you just copy the old app behaviour? Make a sound just once, that's all we need.

It wasn't intentional and the bug has been fixed now

@MarkIorio said in #153: > No change in the last beta. Please, guys, the critical time notification is NASTY! What's the point to harass the player each and every single move? It's scary! Why didn't you just copy the old app behaviour? Make a sound just once, that's all we need. It wasn't intentional and the bug has been fixed now

@T-Rex96 said in #154:

the bug has been fixed now

I saw, thanx. Now it's usable, but if you want to do the right thing all the way down you should copy bit by bit the clock look in the old app, in every phase of the counting.

We had multiple colours:

  • Background colours
  • Digit colours

Changing for active and inactive clocks, and in 3 phases of the game:

  • normal counting
  • time critical
  • last ten seconds

That was perfect, while the new app doesn't catch the eye on the clock, when it's your turn, when time is critical and what's more important in the last ten seconds. It's now easy to be surprised by the time expired, unfortunately, while that couldn't happen with the old app. This is because now clocks are smaller, digits are too thin and they are black on white instead of white on a dark colour background.

Just copy and paste all values for clocks dimensions and colours from the old app to the new one and you are done.

@T-Rex96 said in #154: >the bug has been fixed now I saw, thanx. Now it's usable, but if you want to do the right thing all the way down you should copy bit by bit the clock look in the old app, in every phase of the counting. We had multiple colours: - Background colours - Digit colours Changing for active and inactive clocks, and in 3 phases of the game: - normal counting - time critical - last ten seconds That was perfect, while the new app doesn't catch the eye on the clock, when it's your turn, when time is critical and what's more important in the last ten seconds. It's now easy to be surprised by the time expired, unfortunately, while that couldn't happen with the old app. This is because now clocks are smaller, digits are too thin and they are black on white instead of white on a dark colour background. Just copy and paste all values for clocks dimensions and colours from the old app to the new one and you are done.

Nasty bug: during the "waiting for opponent" phase the auto screen off timeout is still effective, the screen goes blank and you get no sound or warning when an opponent is found. The game is aborted and you get a warning for that.

Expected behaviour: while waiting for opponent we should be able to switch to another app, or let the screen go off while the search remains active in the background. When an opponent is found the app should either swap itself to the foreground or pop up a notification, and make a sound in any case.

Nasty bug: during the "waiting for opponent" phase the auto screen off timeout is still effective, the screen goes blank and you get no sound or warning when an opponent is found. The game is aborted and you get a warning for that. Expected behaviour: while waiting for opponent we should be able to switch to another app, or let the screen go off while the search remains active in the background. When an opponent is found the app should either swap itself to the foreground or pop up a notification, and make a sound in any case.

@MarkIorio said in #156:

Nasty bug: during the "waiting for opponent" phase the auto screen off timeout is still effective, the screen goes blank and you get no sound or warning when an opponent is found. The game is aborted and you get a warning for that.

Expected behaviour: while waiting for opponent we should be able to switch to another app, or let the screen go off while the search remains active in the background. When an opponent is found the app should either swap itself to the foreground or pop up a notification, and make a sound in any case.

Please, fix that. I've already been banned once because of it. You should primarily fix bugs and problems that prevent the beta version to be used safely.

By the way, Lichess ban is riddiculously short for aborters. If it's the same for rage quitters I understand why they keep coming.

@MarkIorio said in #156: > Nasty bug: during the "waiting for opponent" phase the auto screen off timeout is still effective, the screen goes blank and you get no sound or warning when an opponent is found. The game is aborted and you get a warning for that. > > Expected behaviour: while waiting for opponent we should be able to switch to another app, or let the screen go off while the search remains active in the background. When an opponent is found the app should either swap itself to the foreground or pop up a notification, and make a sound in any case. Please, fix that. I've already been banned once because of it. You should primarily fix bugs and problems that prevent the beta version to be used safely. By the way, Lichess ban is riddiculously short for aborters. If it's the same for rage quitters I understand why they keep coming.

@MarkIorio said in #153:

@MarkIorio сказал в #151:

Предпочтения: Звук, когда время становится критическим
Не каждое движение!

Никаких изменений по сравнению с последней бета-версией. Пожалуйста, ребята, уведомление о критическом времени ПРОТИВНОЕ! Какой смысл изводить игрока на каждом шагу? Это страшно! Почему вы просто не скопировали поведение старого приложения? Издайте звук всего один раз, вот и все, что нам нужно.
@MarkIorio said in #153:
Preferences: Sound when time gets critical
Not every single move!

No change in the last beta. Please, guys, the critical time notification is NASTY! What's the point to harass the player each and every single move? It's scary! Why didn't you just copy the old app behaviour? Make a sound just once, that's all we need.

support

@MarkIorio said in #153: > @MarkIorio сказал в #151: > > Предпочтения: Звук, когда время становится критическим > Не каждое движение! > > Никаких изменений по сравнению с последней бета-версией. Пожалуйста, ребята, уведомление о критическом времени ПРОТИВНОЕ! Какой смысл изводить игрока на каждом шагу? Это страшно! Почему вы просто не скопировали поведение старого приложения? Издайте звук всего один раз, вот и все, что нам нужно. @MarkIorio said in #153: > Preferences: Sound when time gets critical > Not every single move! > > No change in the last beta. Please, guys, the critical time notification is NASTY! What's the point to harass the player each and every single move? It's scary! Why didn't you just copy the old app behaviour? Make a sound just once, that's all we need. support

@VovaDrago said in #158:

No change in the last beta. Please, guys, the critical time notification is NASTY! What's the point to harass the player each and every single move? It's scary! Why didn't you just copy the old app behaviour? Make a sound just once, that's all we need.

support

Well, that is fixed now. What version are you running?

@VovaDrago said in #158: >>No change in the last beta. Please, guys, the critical time notification is NASTY! What's the point to harass the player each and every single move? It's scary! Why didn't you just copy the old app behaviour? Make a sound just once, that's all we need. >support Well, that is fixed now. What version are you running?

@MarkIorio said in #157:

Nasty bug: during the "waiting for opponent" phase the auto screen off timeout is still effective, the screen goes blank and you get no sound or warning when an opponent is found. The game is aborted and you get a warning for that.

Expected behaviour: while waiting for opponent we should be able to switch to another app, or let the screen go off while the search remains active in the background. When an opponent is found the app should either swap itself to the foreground or pop up a notification, and make a sound in any case.

Please, fix that. I've already been banned once because of it. You should primarily fix bugs and problems that prevent the beta version to be used safely.

Still no fix in the last beta. Sorry, guys, I'm not using it anymore until this is gone. I don't want to step into another ban for aborting games, and I refuse to manually disable my screen off timeout every single time I want to use the app and reenable it when I'm done.

This problem has been neglected by the new app's programmers since the very beginning, when the app didn't make a sound at a game start, not even with the screen well lit. Please, understand that the opponent search can be long, and you cannot expect a player to be staring at a screen locked on the "searching for opponent" window for minutes without being able to do anything else at all. It's crazy!

@MarkIorio said in #157: > > Nasty bug: during the "waiting for opponent" phase the auto screen off timeout is still effective, the screen goes blank and you get no sound or warning when an opponent is found. The game is aborted and you get a warning for that. > > > > Expected behaviour: while waiting for opponent we should be able to switch to another app, or let the screen go off while the search remains active in the background. When an opponent is found the app should either swap itself to the foreground or pop up a notification, and make a sound in any case. > > Please, fix that. I've already been banned once because of it. You should primarily fix bugs and problems that prevent the beta version to be used safely. Still no fix in the last beta. Sorry, guys, I'm not using it anymore until this is gone. I don't want to step into another ban for aborting games, and I refuse to manually disable my screen off timeout every single time I want to use the app and reenable it when I'm done. This problem has been neglected by the new app's programmers since the very beginning, when the app didn't make a sound at a game start, not even with the screen well lit. Please, understand that the opponent search can be long, and you cannot expect a player to be staring at a screen locked on the "searching for opponent" window for minutes without being able to do anything else at all. It's crazy!

Join the Lichess Beta Testers team, to post in this forum