Ask / Submit

Revision history [back]

click to hide/show revision 1
initial version

posted 2017-11-06 02:06:56 +0200

BUG: Default Ambiences should not set system tones

I know that this has been discussed before, but I cannot find it in search and for a feature that was so pushed as something unique to Sailfish OS it is really mystifying that this long standing issue has still not been rectified when there is such a simple fix, since it renders the feature next to useless by default (and still of limited use even with this fixed, but it would be a huge start).

The problem is that all the default ambiences (except the silent profile) set all the tones back to default, so if you are using custom ringtones you cannot use any of the system ambiences (except silent).

The workaround is simple enough - just remove all the actions in each of the system ambiences. The problem with this workaround is that it gets wiped out whenever the ambiences package is updated, so this isn't something we can actually rely on in practice.

The fix is just as simple: Ship the ambiences without any actions that set tones. This would take someone at Jolla literally two minutes to fix... So, fix it?

Yes, there's a more advanced fix - have ambiences restore the previously set tones when they are unset (assuming the user hasn't since manually changed the tones and prior to applying the new ambience's tones), but this is useless if all the default ambiences still reset all the tones anyway, so just start with this simple fix and then we can talk about other ways to make this feature more useful.

BUG: Default Ambiences should not set system tones

EDIT: I am NOT looking for advice or workarounds. I know we can use custom ambiences, but that isn't the issue here. This issue is about the DEFAULT ambiences, and this can only be resolved by Jolla updating the Ambience package shipped with Sailfish OS. Any other advice to avoid the problem is not helpful, because the problem still exists. The ONLY other discussion that should even be happening here is other ways in which the Ambience mechanics can be improved, but even that is only tangentially related to this report and should really be in a different thread.

I know that this has been discussed before, but I cannot find it in search and for a feature that was so pushed as something unique to Sailfish OS it is really mystifying that this long standing issue has still not been rectified when there is such a simple fix, since it renders the feature next to useless by default (and still of limited use even with this fixed, but it would be a huge start).

The problem is that all the default ambiences (except the silent profile) set all the tones back to default, so if you are using custom ringtones you cannot use any of the system ambiences (except silent).

The workaround is simple enough - just remove all the actions in each of the system ambiences. The problem with this workaround is that it gets wiped out whenever the ambiences package is updated, so this isn't something we can actually rely on in practice.

The fix is just as simple: Ship the ambiences without any actions that set tones. This would take someone at Jolla literally two minutes to fix... So, fix it?

Yes, there's a more advanced fix - have ambiences restore the previously set tones when they are unset (assuming the user hasn't since manually changed the tones and prior to applying the new ambience's tones), but this is useless if all the default ambiences still reset all the tones anyway, so just start with this simple fix and then we can talk about other ways to make this feature more useful.

BUG: Default Ambiences should not set system tones

EDIT: I am NOT looking for advice or workarounds. I know we can use custom ambiences, but that isn't the issue here. This issue is about the DEFAULT ambiences, and this can only be resolved by Jolla updating the Ambience package shipped with Sailfish OS. Any other advice to avoid the problem is not helpful, because the problem still exists. The ONLY other discussion that should even be happening here is other ways in which the Ambience mechanics can be improved, but even that is only tangentially related to this report and should really be in a different thread.

I know that this has been discussed before, but I cannot find it in search and for a feature that was so pushed as something unique to Sailfish OS it is really mystifying that this long standing issue has still not been rectified when there is such a simple fix, since it renders the feature next to useless by default (and still of limited use even with this fixed, but it would be a huge start).

The problem is that all the default ambiences (except the silent profile) set all the tones back to default, so if you are using custom ringtones you cannot use any of the system ambiences (except silent).

The workaround is simple enough - just remove all the actions in each of the system ambiences. The problem with this workaround is that it gets wiped out whenever the ambiences package is updated, so this isn't something we can actually rely on in practice.

The fix is just as simple: Ship the ambiences without any actions that set tones. This would take someone at Jolla literally two minutes to fix... So, fix it?

Yes, there's a more advanced fix - have ambiences restore the previously set tones when they are unset (assuming the user hasn't since manually changed the tones and prior to applying the new ambience's tones), but this is useless if all the default ambiences still reset all the tones anyway, so just start with this simple fix and then we can talk about other ways to make this feature more useful.

BUG: Default Ambiences should not set system tones

EDIT: Patch is included in below answer for Jolla to apply

EDIT: I am NOT looking for advice or workarounds. I know we can use custom ambiences, but that isn't the issue here. This issue is about the DEFAULT ambiences, and this can only be resolved by Jolla updating the Ambience package shipped with Sailfish OS. Any other advice to avoid the problem is not helpful, because the problem still exists. The ONLY other discussion that should even be happening here is other ways in which the Ambience mechanics can be improved, but even that is only tangentially related to this report and should really be in a different thread.

I know that this has been discussed before, but I cannot find it in search and for a feature that was so pushed as something unique to Sailfish OS it is really mystifying that this long standing issue has still not been rectified when there is such a simple fix, since it renders the feature next to useless by default (and still of limited use even with this fixed, but it would be a huge start).

The problem is that all the default ambiences (except the silent profile) set all the tones back to default, so if you are using custom ringtones you cannot use any of the system ambiences (except silent).

The workaround is simple enough - just remove all the actions in each of the system ambiences. The problem with this workaround is that it gets wiped out whenever the ambiences package is updated, so this isn't something we can actually rely on in practice.

The fix is just as simple: Ship the ambiences without any actions that set tones. This would take someone at Jolla literally two minutes to fix... So, fix it?

Yes, there's a more advanced fix - have ambiences restore the previously set tones when they are unset (assuming the user hasn't since manually changed the tones and prior to applying the new ambience's tones), but this is useless if all the default ambiences still reset all the tones anyway, so just start with this simple fix and then we can talk about other ways to make this feature more useful.

BUG: Default Ambiences should not set system tonestones [PATCH]

EDIT: Patch is included in below answer for Jolla to apply

EDIT: I am NOT looking for advice or workarounds. I know we can use custom ambiences, but that isn't the issue here. This issue is about the DEFAULT ambiences, and this can only be resolved by Jolla updating the Ambience package shipped with Sailfish OS. Any other advice to avoid the problem is not helpful, because the problem still exists. The ONLY other discussion that should even be happening here is other ways in which the Ambience mechanics can be improved, but even that is only tangentially related to this report and should really be in a different thread.

I know that this has been discussed before, but I cannot find it in search and for a feature that was so pushed as something unique to Sailfish OS it is really mystifying that this long standing issue has still not been rectified when there is such a simple fix, since it renders the feature next to useless by default (and still of limited use even with this fixed, but it would be a huge start).

The problem is that all the default ambiences (except the silent profile) set all the tones back to default, so if you are using custom ringtones you cannot use any of the system ambiences (except silent).

The workaround is simple enough - just remove all the actions in each of the system ambiences. The problem with this workaround is that it gets wiped out whenever the ambiences package is updated, so this isn't something we can actually rely on in practice.

The fix is just as simple: Ship the ambiences without any actions that set tones. This would take someone at Jolla literally two minutes to fix... So, fix it?

Yes, there's a more advanced fix - have ambiences restore the previously set tones when they are unset (assuming the user hasn't since manually changed the tones and prior to applying the new ambience's tones), but this is useless if all the default ambiences still reset all the tones anyway, so just start with this simple fix and then we can talk about other ways to make this feature more useful.

BUG: Default Ambiences should not set system tones [PATCH]

EDIT: Patch is included in below answer for Jolla to apply

EDIT: I am NOT looking for advice or workarounds. I know we can use custom ambiences, but that isn't the issue here. This issue is about the DEFAULT ambiences, and this can only be resolved by Jolla updating the Ambience package shipped with Sailfish OS. Any other advice to avoid the problem is not helpful, because the problem still exists. The ONLY other discussion that should even be happening here is other ways in which the Ambience mechanics can be improved, but even that is only tangentially related to this report and should really be in a different thread.

I know that this has been discussed before, but I cannot find it in search and for a feature that was so pushed as something unique to Sailfish OS it is really mystifying that this long standing issue has still not been rectified when there is such a simple fix, since it renders the feature next to useless by default (and still of limited use even with this fixed, but it would be a huge start).

The problem is that all the default ambiences (except the silent profile) set all the tones back to default, so if you are using custom ringtones you cannot use any of the system ambiences (except silent).

The workaround is simple enough - just remove all the actions in each of the system ambiences. The problem with this workaround is that it gets wiped out whenever the ambiences package is updated, so this isn't something we can actually rely on in practice.

The fix is just as simple: Ship the ambiences without any actions that set tones. This would take someone at Jolla literally two minutes to fix... So, fix it?

Yes, there's a more advanced fix - have ambiences restore the previously set tones when they are unset (assuming the user hasn't since manually changed the tones and prior to applying the new ambience's tones), but this is useless if all the default ambiences still reset all the tones anyway, so just start with this simple fix and then we can talk about other ways to make this feature more useful.

Edit: This advanced fix is described in more detail in this bug report:
https://together.jolla.com/question/173201/bug-ambiences-should-restore-previous-sound-volume-when-unset/

BUG: Default Ambiences should not set system tones [PATCH]

EDIT: Patch is included in below answer for Jolla to apply

EDIT: I am NOT looking for advice or workarounds. I know we can use custom ambiences, but that isn't the issue here. This issue is about the DEFAULT ambiences, and this can only be resolved by Jolla updating the Ambience package shipped with Sailfish OS. Any other advice to avoid the problem is not helpful, because the problem still exists. The ONLY other discussion that should even be happening here is other ways in which the Ambience mechanics can be improved, but even that is only tangentially related to this report and should really be in a different thread.

I know that this has been discussed before, but I cannot find it in search and for a feature that was so pushed as something unique to Sailfish OS it is really mystifying that this long standing issue has still not been rectified when there is such a simple fix, since it renders the feature next to useless by default (and still of limited use even with this fixed, but it would be a huge start).

The problem is that all the default ambiences (except the silent profile) set all the tones back to default, so if you are using custom ringtones you cannot use any of the system ambiences (except silent).

The workaround is simple enough - just remove all the actions in each of the system ambiences. The problem with this workaround is that it gets wiped out whenever the ambiences package is updated, so this isn't something we can actually rely on in practice.

The fix is just as simple: Ship the ambiences without any actions that set tones. This would take someone at Jolla literally two minutes to fix... So, fix it?

Yes, there's a more advanced fix - have ambiences restore the previously set tones when they are unset (assuming the user hasn't since manually changed the tones and prior to applying the new ambience's tones), but this is useless if all the default ambiences still reset all the tones anyway, so just start with this simple fix and then we can talk about other ways to make this feature more useful.

useful. Edit: This advanced fix is described in more detail in this bug report:
https://together.jolla.com/question/173201/bug-ambiences-should-restore-previous-sound-volume-when-unset/