Hello Sailors. Alarm Clock play sound clip max for 1 minute. I need 2 minutes. How to change this value?
2 Likes
If you find out, let me know… But I guess there isn’t an option for it (yet)
Did you try to set an alarm with 2 minutes playtime?
Explain please where’s this option. I have almost 2 minute sound clip and always it’s cut after 60 seconds.
Honestly alarm should be ringing until i turn it off. Turning off by itself is so stupid and made me oversleep to work multiple times
7 Likes
I can’t find the app’s source code. However, it must be very easy, couple of hours at most, maybe even less than an hour for an experienced coder, to redo the app and make the alarm sound until it is turned off.
If nobody is going to do it before I have time, I might have a go at it.
If so, I’ll link to the source code and rpms as a post in this thread.
1 Like
No need to redo. Just adjust the parameters a bit. Adding that the file is played until end. Maybe add an UI option for a time and how often to repeat.
1 Like
We don’t have source code, at least I can’t find it.
Yes, I get it. But it’s such a small piece of software, maybe we can get @rainemak to add it to the Open sourcing proceeding and then change it.
As a workaround, setting the snooze time to 65 s wouldn’t do it?
Definitely worth to raise topic in community meeting if Jolla could find time to open source it after the Jolla phone launch. Would be amazing to have it ij native alarm as a option
Has anyone tried searching where the actual audio file is stored and making it longer?
The problem is not the length of the audio file but the Clock app cutting off at 1 minute.
1 Like
@Schlens A workaround could be setting an alarm one minute later and, if needed, a third one or more. This wouldn’t result in a continuous sound, but in several ones shortly following the first one …
1 Like
AI give this
dconf write /org/nemomobile/timed/alarm_timeout 120
What do You think? It’s safe and correct?
Should be safe, but may be @nephros can add it AS a patch for patchmanager…
It doesn’t turn off, it just snoozes for five minutes and starts again. To be honest, I like that I know six minutes have passed when the alarm sounds for the second time, and twelve minutes have passed when it sounds for the third time. I don’t need to look at the clock to know how lazy I’m being, and the alarm noise is annoying enough to wake me but not annoying enough to intrude on letting me snooze for a bit longer.
The one thing that does catch me out is sometimes I will get up and be in the middle of something and have forgotten I did not explicitly cancel the alarm, so it will start sounding again in my pocket. But I can’t have it both ways and this is a functionality that I like more than I dislike.
and what is that if not turning off? And it wont repeatedly snooze forever either.
Just to be different, I like that the alarm stops after a minute. If I can hear it and not get to it, I am often thankful it stops. So of course this should be an option to stop or run infinitely.
Why me? Anyone can (learn to) do that!
And I’m also in the camp that the current default functionality is fine. I even find it superior to many other clock variants.
If you want different behavior, maybe instead of a clock event create a Calendar reminder, and assign a longer tone to those notifications?
2 Likes