maemo.org - Talk

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)

freemangordon 2012-11-11 21:27

[ANNOUNCE]Alarm UI replacement
 
Well, after almost 3 years living with unreliable alarms on my n900, finally there is a light at the end of the tunnel. Could be a train, who knows :p

package is in CSSU-devel repo, you can install it with apt or by downloading the .deb from here:
http://maemo.merlin1991.at/cssu/comm...ystemui-alarm/

Don't forget to reboot after installing it :)

Have in mind this is beta quality, so it might have some bugs.

source code here:
https://gitorious.org/community-ssu/osso-systemui-alarm

look at the commits to see what has changed compared to stock, but in short:

Simultaneous alarms should work with no problems, auto/snooze no longer leads to missed alarm events. Fixed a nasty memory leak.

I head that for inclusion in CSSU, but need some testing by those who had the problems stated on 720p thread to confirm there are no more missed alarm events. In other words - I need a couple of guinea pigs :D

ZogG 2012-11-11 21:40

Re: [ANNOUNCE]Alarm UI replacement
 
some screenshots would be nice :P
Thanks btw for that you keep working on maemo even in such hard times

ade 2012-11-11 21:41

Re: [ANNOUNCE]Alarm UI replacement
 
Please do not confuse this with the clock itself, it is more related to the alarm popup that you get.
Thanks for taking care of this part.

freemangordon 2012-11-11 21:54

Re: [ANNOUNCE]Alarm UI replacement
 
Quote:

Originally Posted by ade (Post 1293131)
Please do not confuse this with the clock itself, it is more related to the alarm popup that you get.

Exactly.
BTW I fixed some bugs since you installed it, you may want to download and install the .deb again

ZogG: This looks exactly like stock alarm event/calendar event popup, no changes on that part.

mr_pingu 2012-11-12 07:48

Re: [ANNOUNCE]Alarm UI replacement
 
First of all, I was waked up on 8:10. Thanks :) Of course I had also backup but I was wide awake, thanks to these alarms, before the backup-alarm ringed.

My first reaction was pressing snooze of the 8:10 alarm and so I did. Then waited about half a minute and left the phone ringing to the alarm of 8:12. I stopped 8:12, immediately after I stopped 8.12. 8:11 popped up and started ringing again.

So I stopped 8:11 too.

8:10 was supposed to snooze at 8:15, so it did. Nothing strange, all good. This time instead of snooze, I did nothing, after the hardcoded 60 seconds it turned off. At 8:20 it started to ring again, however, the time that was displayed on the alarm was 8:15, but it was 8:20 in real-time.

Also small-feature request: Prohibit blanking of the screen while an alarm is actively ringing. It does turn the screen on/unlocks but it uses the default time-out value. If one wants to stop/snooze, after 30 seconds (my timeout-value), one needs to reach for the unlockkey first. When I am sleepy, that's too hard for me. :p
It vaguely remember the default plugin already did it, but I can be wrong as I didn't use the alarm for a long time after it failed one day :D

panjgoori 2012-11-12 07:54

Re: [ANNOUNCE]Alarm UI replacement
 
im ready for testing after creating backup.

freemangordon 2012-11-12 08:46

Re: [ANNOUNCE]Alarm UI replacement
 
Quote:

Originally Posted by mr_pingu (Post 1293239)
I stopped 8:12, immediately after I stopped 8.12. 8:11 popped up and started ringing again.
So I stopped 8:11 too.

Thats expected, so far so good.

Quote:

8:10 was supposed to snooze at 8:15, so it did. Nothing strange, all good. This time instead of snooze, I did nothing, after the hardcoded 60 seconds it turned off. At 8:20 it started to ring again, however, the time that was displayed on the alarm was 8:15, but it was 8:20 in real-time.
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.

Quote:

Also small-feature request: Prohibit blanking of the screen while an alarm is actively ringing. It does turn the screen on/unlocks but it uses the default time-out value. If one wants to stop/snooze, after 30 seconds (my timeout-value), one needs to reach for the unlockkey first. When I am sleepy, that's too hard for me. :p
It vaguely remember the default plugin already did it, but I can be wrong as I didn't use the alarm for a long time after it failed one day :D
you can always turn it face-down to snooze ;). Though blanking the display might be a bug, I'll check that.

Thanks a lot for the testing.

In the meanwhile a newer version .deb is on the same place, it fixes the last (I hope) bug.

rotoflex 2012-11-12 08:51

Re: [ANNOUNCE]Alarm UI replacement
 
Quote:

Originally Posted by freemangordon (Post 1293124)

Produces this:

Quote:

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
Downloading & opening the .deb with application manager, on CSSU-testing, produces the error bar:
Quote:

Unable to update 'osso-systemui-alarm'.
Incompatible application package.
I am personally hoping to see the Snooze button increased in size relative to the Stop button, maybe 66% to 33%.

reinob 2012-11-12 09:02

Re: [ANNOUNCE]Alarm UI replacement
 
Quote:

Originally Posted by freemangordon (Post 1293124)
is the .deb for replacement of the stock Alarm UI. Don't forget to reboot after installing it :)

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!

mr_pingu 2012-11-12 09:03

Re: [ANNOUNCE]Alarm UI replacement
 
aaargh, silly me, forced myself to reflash, doh :( Need to get my N900 up and running again, will test the new .deb ASAP ;)



@rotoflex: Use dpkg -i from terminal.
cd to download folder, dpkg -i packagename (needs superuser or root privileges)

dann9 2012-11-12 09:05

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

freemangordon 2012-11-12 09:13

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 ;)

ade 2012-11-12 09:13

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"

freemangordon 2012-11-12 09:20

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?

reinob 2012-11-12 09:25

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 :)

don_falcone 2012-11-12 09:41

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...

reinob 2012-11-12 09:53

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! :)

Flyser 2012-11-12 10:16

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 ;)

panjgoori 2012-11-12 10:19

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.

freemangordon 2012-11-12 11:33

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.

reinob 2012-11-12 14:22

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?

I just installed the replacement on my spare N900 and everything looks OK. I set-up two alarms. The first one I snoozed (and it came up again correctly after 10min). For the second one I tried to quickly close it when starting, but the sound/vibration was already there (I think even before the GUI appeared.. :)

So for my purposes I will add my "bug" to the collection of, let's say, oddities, that the N900/Maemo has, for which we all love it so much :)

freemangordon 2012-11-12 15:18

Re: [ANNOUNCE]Alarm UI replacement
 
Package moved to CSSU-devel, major refactoring has been done since the last update, I hope I didn't break something.

Anyway, please install the version in CSSU-devel and report.

Thanks.

don_falcone 2012-11-13 07:23

Re: [ANNOUNCE]Alarm UI replacement
 
At least it woke me up at 6 today. :)

peterleinchen 2012-11-13 08:18

Re: [ANNOUNCE]Alarm UI replacement
 
Yes, me too. BUT also the standard alarm UI woke me up (more than less) reliable the last days.
Again: the last time I suffered from not alarming, my hildon-home was "hanging".
Not to be pessimistic, but I fear, that all "is working" notes here are nice, but we need to wait for the bad "not alarming" message :(. Or wait a few days/weeks more :)

freemangordon 2012-11-13 08:38

Re: [ANNOUNCE]Alarm UI replacement
 
Quote:

Originally Posted by peterleinchen (Post 1293681)
Yes, me too. BUT also the standard alarm UI woke me up (more than less) reliable the last days.
Again: the last time I suffered from not alarming, my hildon-home was "hanging".
Not to be pessimistic, but I fear, that all "is working" notes here are nice, but we need to wait for the bad "not alarming" message :(. Or wait a few days/weeks more :)

Your "h-h hang" is a bit different to the main reason I started RE of alarmUI - everything is responsible and works, but alarms just don't ring.

Otherwise I agree that alarmUI should be tested thoroughly, I don't want someone to be fired because he/she overslept :)

sifo 2012-11-13 11:48

Re: [ANNOUNCE]Alarm UI replacement
 
Updated yesterday, and everything is completely fine :)
thank you FMG.

./sifo

don_falcone 2012-11-13 12:57

Re: [ANNOUNCE]Alarm UI replacement
 
Question: does anyone else observe that after a reboot, the trigger time of the next alarm in queue is not displayed anymore in status area? (Disclaimer: i use this)

peterleinchen 2012-11-13 13:21

Re: [ANNOUNCE]Alarm UI replacement
 
Quote:

Originally Posted by freemangordon (Post 1293688)
Your "h-h hang" is a bit different to the main reason I started RE of alarmUI - everything is responsible and works, but alarms just don't ring.

IIRC also in my case everything was working fine, except the ringing.
But if not, then I was asleep and cannot remember ;)
No serious, this h-h-hanging is just like you do not notice until you missed a (not notified) SMS or a (not shown) notification for a missed call or you want to run/update a widget on desktop.
Everything else runs fine, switching desktops works, standard contacts and bookmarks on desktop work.
So I thought this would/could be the same cause?
(as the alarm UI is not able to popup, so no ringing)


Quote:

Originally Posted by freemangordon (Post 1293688)
Otherwise I agree that alarmUI should be tested thoroughly, I don't want someone to be fired because he/she overslept :)

Yeah, thanks :D

peterleinchen 2012-11-14 08:18

Re: [ANNOUNCE]Alarm UI replacement
 
OK, here I am (the guy with bad news :() .

This morning my alarm UI did not ring.
I had a (forgotten) alarm at 0600 coming from calendar. This one rang and woke me up, so I pushed the stop button. Then I had two alarms from clock (0715 and 0730). As I was already awake I checked my N900 from time to time and yes the 0715 alarm popped onto the screen, but it did NOT ring. So I pushed Snooze. Then the 0730 popped up and did not ring either. I pushed Stop. Abit later the 0715 popped up agaian (no ringing), and again snoozed it. Then I checked hildon-home and it was "frozen". No widgtes updated, no email notification working. So I killed hildon-home. A bit later the snoozed 0715 alarm came up again and guess what? It rang!
So my assumption that hildon-home is somehow in the game is correct. @freemangordon, please tell me if I can provide you some logs or other info ...

And maybe I did not install it correctly: I just extracted the deb and put the library in their directory. I did not reboot (nor killed hildon-home), so maybe the old library was still loaded?

reinob 2012-11-14 08:37

Re: [ANNOUNCE]Alarm UI replacement
 
@perleinchen,

Quote:

Don't forget to reboot after installing it
But anyway, that's a typical recommendation which may or may not be necessary (perhaps freemangordon can explain that one).

In any case, your hildon-home-freezing problem sounds quite bad (are you the only one here suffering from it, or do the others suffer in silence? :)

I have never, or extremely rarely, had any problems with hildon-desktop or hildon-home. My uptime usually reaches 30+ days before I power off for one reason or another.

I don't know how "open" or how "hackable" hildon-home is but it may be about time to start debugging that mess.

Can you install syslog and check the next time it happens in case there's some indication in the log of what the problem might be?

freemangordon 2012-11-14 10:20

Re: [ANNOUNCE]Alarm UI replacement
 
Rebooting the device after the installation is not just a recomendation, it is a must. systemui process keeps its plugins loaded and the only way I know to correctly restart it is a reboot.

dzano 2012-11-14 12:00

Re: [ANNOUNCE]Alarm UI replacement
 
Quote:

Originally Posted by peterleinchen (Post 1294059)
OK, here I am (the guy with bad news :() .

This morning my alarm UI did not ring.
I had a (forgotten) alarm at 0600 coming from calendar. This one rang and woke me up, so I pushed the stop button....

I can say for sure that Desktop Command Execution Widget makes hildon-home "frozen"...no alarms, no calls, no sms. I had this problem almost every day until I uninstalled it.

don_falcone 2012-11-14 12:31

Re: [ANNOUNCE]Alarm UI replacement
 
Hmm interesting. Because i use two instances (% free root fs, battery level), and after some time (multiple days) i can't start anything from the desktop, or edit it/configure widgets. Only the status area is responsive. But i can't say if this happens _reliably_, as sometimes i restart the device more often.

reinob 2012-11-14 12:45

Re: [ANNOUNCE]Alarm UI replacement
 
Quote:

Originally Posted by dzano (Post 1294149)
I can say for sure that Desktop Command Execution Widget makes hildon-home "frozen"...no alarms, no calls, no sms. I had this problem almost every day until I uninstalled it.

I use DCEW on my spare-spare-N900 (where I have removed a big part of Maemo). Unfortunately that particular N900 is not usually left turned on for more than a few minutes/hours.

I'll try to keep an eye on it though.

dzano 2012-11-14 14:02

Re: [ANNOUNCE]Alarm UI replacement
 
Quote:

Originally Posted by don_falcone (Post 1294157)
Hmm interesting. Because i use two instances (% free root fs, battery level), and after some time (multiple days) i can't start anything from the desktop, or edit it/configure widgets. Only the status area is responsive. But i can't say if this happens _reliably_, as sometimes i restart the device more often.

Same thing was happening to me. Now I'm using Queen BeeCon Widget and since I installed it, I've never had that problem again.

don_falcone 2012-11-14 14:28

Re: [ANNOUNCE]Alarm UI replacement
 
Ok. The question is whether QBW can do weather too...

peterleinchen 2012-11-14 23:06

Re: [ANNOUNCE]Alarm UI replacement
 
Quote:

Originally Posted by reinob (Post 1294070)
@peterleinchen,

Quote:

Originally Posted by freemangordon (Post 1293124)
Don't forget to reboot after installing it :)

Doh!

In any case, your hildon-home-freezing problem sounds quite bad (are you the only one here suffering from it, or do the others suffer in silence? :)
There are lots of others ...

I have never, or extremely rarely, had any problems with hildon-desktop or hildon-home. My uptime usually reaches 30+ days before I power off for one reason or another.
Lucky guy ;)
I have another problem with hildon-desktop eating CPU, but another story...


Can you install syslog and check the next time it happens in case there's some indication in the log of what the problem might be?
Already have sysklogd, but disbaled it few weeks ago. Will reenable and see if I may provoke this once again.


Quote:

Originally Posted by freemangordon (Post 1294109)
Rebooting the device after the installation is not just a recomendation, it is a must. systemui process keeps its plugins loaded and the only way I know to correctly restart it is a reboot.

Had something like this in mind (after almost written my post).
OK, will keep this version and reboot and try again. Sorry.

And yes, it may be DCEW.
I had a fresh install (after deleting the config from /home/user/.desktop_cmd_exec) and this problem did not or very very rarely happen. But I am still not sure!
Nor can I detect in any automated way, that this happened ...

sixwheeledbeast 2012-11-14 23:15

Re: [ANNOUNCE]Alarm UI replacement
 
Quote:

Originally Posted by reinob (Post 1294070)
In any case, your hildon-home-freezing problem sounds quite bad (are you the only one here suffering from it, or do the others suffer in silence? :)

Silence???

woody14619 2012-11-14 23:24

Re: [ANNOUNCE]Alarm UI replacement
 
Quote:

Originally Posted by don_falcone (Post 1294201)
Ok. The question is whether QBW can do weather too...

Yes, kind of? It depends what you mean with it? :)

peterleinchen 2012-11-15 12:40

Re: [ANNOUNCE]Alarm UI replacement
 
Quote:

Originally Posted by sixwheeledbeast (Post 1294363)

Or did you mean silentio ?


All times are GMT. The time now is 08:01.

vBulletin® Version 3.8.8