![]() |
[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 |
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 |
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. |
Re: [ANNOUNCE]Alarm UI replacement
Quote:
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. |
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 |
Re: [ANNOUNCE]Alarm UI replacement
im ready for testing after creating backup.
|
Re: [ANNOUNCE]Alarm UI replacement
Quote:
Quote:
Quote:
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. |
Re: [ANNOUNCE]Alarm UI replacement
Quote:
Quote:
Quote:
|
Re: [ANNOUNCE]Alarm UI replacement
Quote:
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! |
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) |
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:
Quote:
|
Re: [ANNOUNCE]Alarm UI replacement
Quote:
|
Re: [ANNOUNCE]Alarm UI replacement
Quote:
|
Re: [ANNOUNCE]Alarm UI replacement
Quote:
|
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:
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:
Quote:
|
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:
|
Re: [ANNOUNCE]Alarm UI replacement
Quote:
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 :) |
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. |
Re: [ANNOUNCE]Alarm UI replacement
At least it woke me up at 6 today. :)
|
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 :) |
Re: [ANNOUNCE]Alarm UI replacement
Quote:
Otherwise I agree that alarmUI should be tested thoroughly, I don't want someone to be fired because he/she overslept :) |
Re: [ANNOUNCE]Alarm UI replacement
Updated yesterday, and everything is completely fine :)
thank you FMG. ./sifo |
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)
|
Re: [ANNOUNCE]Alarm UI replacement
Quote:
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:
|
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? |
Re: [ANNOUNCE]Alarm UI replacement
@perleinchen,
Quote:
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? |
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.
|
Re: [ANNOUNCE]Alarm UI replacement
Quote:
|
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.
|
Re: [ANNOUNCE]Alarm UI replacement
Quote:
I'll try to keep an eye on it though. |
Re: [ANNOUNCE]Alarm UI replacement
Quote:
|
Re: [ANNOUNCE]Alarm UI replacement
Ok. The question is whether QBW can do weather too...
|
Re: [ANNOUNCE]Alarm UI replacement
Quote:
Quote:
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 ... |
Re: [ANNOUNCE]Alarm UI replacement
Quote:
|
Re: [ANNOUNCE]Alarm UI replacement
Quote:
|
Re: [ANNOUNCE]Alarm UI replacement
Quote:
|
All times are GMT. The time now is 08:01. |
vBulletin® Version 3.8.8