Notices

LABAUDIO: You are a mess: that was the worste bugs report ever!!

Anyway Jolouis have an N800: The N800 does NOT have the sweetness of the color LEDs (just a sad lonely white very nice shade of royal blue led) so he cant test anything LED related.
Im really surprised he put so much time just for a feature he can't even enjoy!
Ill try to fix all the small issue I leaved there because Im a lazy a**.

Meanwhile Im working on some graphic fixing (differentiate the buttons from the labels, strip a bit some heavy lines and reordering a bit the alarm interface (this is the time for suggestions because I still have to touch the code to remaps the things a bit.

The N800 has a sad lonely little blue LED, actually. A very nice shade of royal blue.

sorry iam just a french noob lol

but all issue i wrote uphere is real lol

I had a problem with the alarm too, this morning. It didn't ring, as I set it yesterday.
When I reprogrammed the alarm it worked fine.
Looks to me, like the alarm wasn't sent to alarmd.
When I change the time for an already activated alarm, do I have to switch it off and on again, so it get's changed in alarmd?

Alarms don't work (sound) for me either. I have a N810.

Interesting problem with the alarms stuff that you guys are reporting. You shouldn't have to turn it on/off to resave the alarm, it will get updated any time you make any change and then leave the alarm screen (or choose another day). Did you see the gray "wait..." screen showing up after making your alarm changes and moving screens (that's when it does the alarmD stuff)?
Also it seems to be more of a strange sound playback issue/dbus issue with N810s based on what you guys have said here... i.e. LABAUDIO said that when he sets and alarm and closes the app, at the time of the alarm the app does automatically open again, but it doesn't "trigger" the alarm (alarm should light up display and start playing sounds/show snooze bar, etc). This means that AlarmD is actually working (alarmD is what causes the app to "automatically open"), but when the app opens it's not receiving the signal to actually go into alarm.
Can everyone who's having the no alarm problem please confirm this behaviour... that is, set an alarm and close the app, then let me know if 1) the app opens at automatically at the right time 2) the "snooze" bar shows up on the screen to indicate clock is in alarm and 3) does the sound play or not?
That way I can try to narrow down the cause of the problem and fix it.

Ciro's right, my N800 only has the one poor lonely blue LED, which has a completely different control interface, so no pretty flashing lights or anything for me to test with... all I did was take Ciro's existing LED code and trigger it from the setMood function. LABAUDIO, when you say Uhh, is the LED supposed to stay on when the clock is exited?? That doesn't make sense to me... but I'm not an N810 LED guy, just poor old N800... in my mind, LED should go back to doing whatever it normally does if you're not in the clock app anymore, right?...anyone?...
As for the keyboard turning off the LED, don't know, my bet is that it's probably something to do with the native behaviour of the OS LED controls... i.e. if the LED was blinking for a notification/etc, does opening the keyboard stop it? I don't think there's much control over that... could be wrong, but never saw any other info about it anywhere; any thoughts guys?

Ciro, nice work on the updated graphics, one thing tho... and I ran into this when doing the alarms update the first time... I think we need a bit more order/organization. I.e. everything related to each alarm should be beside the digits, anything related to the clock settings itself could be below/on another part of the screen/another screen/whatever. I'm not a designer by any means, and your stuff is amazing, but I do think the organizing would help to make a bit more sense, as some things change per alarm, and some things are "clock global":
Per alarm settings: - Alarm On/Off
- Alarm time
- Alarm Sound
- Alarm Am/PM
- Loop/Once button

Global clock settings - 12/24 hour mode
- Mood
- About button

I like the strawberry on the bottom of the 0 by the way

i confirm again...

when alarm is set it up ( i see the gray "wait...")
i close application...

after that, application open at the rigth time...

but no snoozing message...and no ring or mp3 playing...

I'm mildly embarrassed to say I've never used the alarm function of this app before, I'm on spring break :/

Just tested it. First problem, I still get the wallpaper error message on program start. I then set an alarm and exited the program. The program reactivated, presented the wallpaper message, flashed a few pretty lights, showed the snooze button, but didn't make any sounds. The program then promptly (under 2 seconds) closed itself.

I tested it again after uninstalling it and then reinstalling the 0.1.7 deb (are there any config files I should delete as well?) and observed the same behavior. If flipclock is left open, the program still exits when the alarm is supposed to sound.

So... good thing I was still using my cell phone for an alarm clock before break I'd be happy to do any other testing necessary, do you need any console output?

After last timezonefix upgrade the alarm seem worked fine for me (but I often reset my tablet so I guess is not a realible test for a more normal manydays uptime use: I would just want a way to know which alarm is set and when should ring without have to launch the clock: Ill see what can be possible to do with the status bar (like the nokia one) or maybe beg Kirill to modify the 'advanced power' app and integrate something there
A very nice shade of royal blue!
Mainly my fault: I didn't put too much efforts on the led parts and the integration is poor (I was just happy to see something blinky) the application hardly control the status of the leds: I usually leaved the red led partially dimmed (just to notify that the app is running and to find the tablet in the dark): it should be set to 0 quitting the clock. If something go wrong or maybe jolouis decided an alternative way to close the apps could happen that some led to stay on: since I have the os led notify that is not a big deal for me because at the 1st event the leds are reset to their normal behaviours... Ill disable the OS control and do a serious check about that. Dont worry too much about Jolouis: Ill can take a look to calm the psychedelic mob.

yes this is the actual direction: I suppose is more sensfull switching the loop with the 12/24 buttons on the blueberry screenshot but beside that I cant think too a lot more other options (but often the obvious is beside me).
Im not a designer either (everytime I think at a designer I have this vision of a ponytailed douchebag selling bs in front of a jumboscreen)
well, it really look like a slotmachine... maybe could be a spinoff
application: Ncasino...
Edit: I just read the recent comments: seem the alarm things must have the priority over all the design and leds rambles!

Heh, well, I think that having an alarm clock that sounds an alarm is more immediately important than UI/LED changes, however I'm still very interested in seeing what changes to the UI will be made. Once I use the app more I'm sure I'll have some suggestions