maemo.org - Talk - [ANNOUNCE]Alarm UI replacement

maemo.org - Talk (https://talk.maemo.org/index.php)

- Maemo 5 / Fremantle (https://talk.maemo.org/forumdisplay.php?f=40)

- - [ANNOUNCE]Alarm UI replacement (https://talk.maemo.org/showthread.php?t=87823)

Re: [ANNOUNCE]Alarm UI replacement

do you know if this *.deb fix alarm bug on n9? on n9 sometimes telophone don't turn on when alarm must be start, and all alarm are erased

Re: [ANNOUNCE]Alarm UI replacement

Quote:

Originally Posted by rotoflex (Post 1293261)

Produces this:...

Sorry about that, link fixed

Quote:

I am personally hoping to see the Snooze button increased in size relative to the Stop button, maybe 66% to 33%.

Well, lets first fix the functionality ;)

Re: [ANNOUNCE]Alarm UI replacement

Quote:

Originally Posted by rotoflex (Post 1293261)

Produces this:

Originally Posted by freemangordon View Post

source code here:
https://git.gitorious.org/community-...emui-alarm.git

Produces this:
Not Found

The requested URL /community-ssu/osso-systemui-alarm.git was not found on this server.
Apache Server at git.gitorious.org Port 80

Freemangordon is pointing to the git link. If you want to look at it via your browser, remove the ".git"

Re: [ANNOUNCE]Alarm UI replacement

Quote:

Originally Posted by reinob (Post 1293265)

I still haven't tested the new libalarm, but will install it in one of the dev N900s.

As a bug report, this is as bad as it gets, but it's only happened once (I'm talking stock PR1.3, no CSSU, no nothing):

One day I was in the lift (aka "elevator"), looking at my display, when suddenly an alarm popped-up (on the display, still no sound, usually takes a second or two to start ringing). Given that I was actively looking at the display, when I saw the alarm pop-up I instantly tapped on "close". The alarm UI closed, but then the ring started sounding, with no UI to turn it off. Given the "urgency" of the situation (other people were looking at me as if I was just trying to bother them :), I resorted to turning off the N900 by holding the power button for a few seconds.

Obviously there's a race condition somewhere, but I didn't bother investigating further (alarms usually *wake* me up, so I'm never so quick so as to reproduce the bug).

Perhaps you can have a look? (I will myself take a look at the code, but don't expect that I will find the bug, assuming it's in osso-systemui-alarm.c.

Thanks in advance!

Hmm, I wonder how is that possible, given that alarm UI is single-threaded. Would you try to re-produce the same with replacement?

Re: [ANNOUNCE]Alarm UI replacement

Quote:

Originally Posted by freemangordon (Post 1293277)

Hmm, I wonder how is that possible, given that alarm UI is single-threaded. Would you try to re-produce the same with replacement?

Yup. Just have to find one of those precious time-windows where I have some time to spare and happen to have a spare-N900 with me :)

Re: [ANNOUNCE]Alarm UI replacement

Heh, this sounded a bit like what i observed multiple times: the UI didn't respond to stopping the alarm, (it seemed frozen), and it kept sounding...

Re: [ANNOUNCE]Alarm UI replacement

Quote:

Originally Posted by don_falcone (Post 1293281)

Heh, this sounded a bit like what i observed multiple times: the UI didn't respond to stopping the alarm, (it seemed frozen), and it kept sounding...

But I think that's a different (much more common?) issue. I also have the feeling that many times when the alarm rings and you're too quick (but not as quick as in my bug report above) the UI needs some time to recognize the tap.

I suspect it's something with the proximity sensor (like with the call-ui), where the screen is too quick to display something, but the touch screen is still waking up (or deciding whether to wake up, who knows).

Maybe when the alarm-ui works OK fmg can jump to the call-ui! :)

Re: [ANNOUNCE]Alarm UI replacement

Hi,

Quote:

Originally Posted by reinob (Post 1293265)

Given that I was actively looking at the display, when I saw the alarm pop-up I instantly tapped on "close". The alarm UI closed, but then the ring started sounding, with no UI to turn it off. Given the "urgency" of the situation (other people were looking at me as if I was just trying to bother them :), I resorted to turning off the N900 by holding the power button for a few seconds

I once had the very same behaviour with the old alarmui.

Quote:

Originally Posted by freemangordon (Post 1293258)

Yeah, auto-snooze shows the alarm time, not the current time. I think it is better that way(stock behaves like that), though current time must be shown somewhere too.

Why is it better that way? This tricked me multiple times when I was too sleepy to realize, that the shown time was wrong. An alarm clock should always show the current time. Thats what they do ;)

Re: [ANNOUNCE]Alarm UI replacement

Checked new Alarm Ui so far no problem. snooze works fine and repeat itself without any problem. but after 1 reboot my N900 started to hang but 2nd reboot solved it.

Re: [ANNOUNCE]Alarm UI replacement

Quote:

Originally Posted by Flyser (Post 1293293)

Hi,

Why is it better that way? This tricked me multiple times when I was too sleepy to realize, that the shown time was wrong. An alarm clock should always show the current time. Thats what they do ;)

You got me wrong, what I am saying is that BOTH (current and alarm) times should be shown.