maemo.org - Talk - Flip clock pre pre pre pre release

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

- Applications (https://talk.maemo.org/forumdisplay.php?f=41)

- - Flip clock pre pre pre pre release (https://talk.maemo.org/showthread.php?t=25582)

Re: Flip clock pre pre pre pre release

Is there a way to get the screen to dim but not blank the screen? I like the thought of the screen dimming to save power, but it'd be nice if I could see what time it is without having to tap the screen, if I wake up in the middle of the night.

Also, when this is running, my blue led blinks about once every few seconds even if I set the color mood to red.

Re: Flip clock pre pre pre pre release

Quote:

Originally Posted by wax4213 (Post 274570)

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.

wax4213, okay good feedback; can you try running it from a console and see if there's any wierd output/etc? i.e. run flipclock from console, set an alarm for 2 minutes in the future, leave the clock app open and wait for the alarm to go off... hopefully it will try for 2 seconds then crash as you've reported, and with luck maybe the console will throw an error message.
I'm betting that all of these problems of no alarm have something to do with my rather crude gstreamer module that I built to play the mp3s failing for some reason, so anyone else with no audio output, let me know if you get anything odd from the console.
Sorry I'm not going to mess around any more with the LED thing until we can get the more important stuff (like alarm playback) solved...

As for background, wax4213, can you open up the /home/user/.osso/hildon-desktop/home-background.conf file and tell me what the BackgroundImage field is set to?

Thanks for all the feedback so far guys, hopefully we can get the rest of these bugs worked out quickly!

Re: Flip clock pre pre pre pre release

For me music mp3 wake up me gently and work perfectly but only when the application still open.

When application be closed after set up alarm, the application open up again at the rigth times but no ring or mp3 play

Re: Flip clock pre pre pre pre release

Ok, here's the output from my console:

Code:

~ $ flipclock

/usr/lib/python2.5/site-packages/flipclock/flipclock.py:4: RuntimeWarning: import cdrom: No module named cdrom

  import pygame

/usr/lib/python2.5/site-packages/flipclock/flipclock.py:4: RuntimeWarning: import joystick: No module named joystick

  import pygame

24

sent

on_battery

python[11459]: GLIB DEBUG ConIc - con_ic_connection_send_event(0x34a810, (null), (null), 1)

pre comparing and updating alarms

comparing and updating alarms

pre comparing and updating alarms

Done alarm update

Received alarm trigger

found matching alarm, running

trying to load file/usr/share/flipclock/ringer.mp3

set vol to 0

process 11459: arguments to dbus_connection_send() were incorrect, assertion "connection != NULL" failed in file dbus-connection.c line 3003.

This is normally a bug in some application using the D-Bus library.  D-Bus not built with -rdynamic so unable to print a backtrace

Aborted

And the BackgroundImage field isn't set to anything. I presume this is because I don't have a background image set for my desktop? I just set the color to black.

Re: Flip clock pre pre pre pre release

Thanks wax4213, that helps tremendously!! Two things:
1) lol no background image, of course! That would do it... as Ciro said before, sometimes we miss the most obvious things that are right infront of us. Okay, try updating the ci_init.py file, line's 264 - 280ish should now read:

Code:

userbg = ""

try:              

  config=ConfigParser.ConfigParser()

  config.read (userpath+"/.osso/hildon-desktop/home-background.conf")

  userbg = config.get("Hildon Home", "BackgroundImage")

  userbg = userbg.replace("file://", "")

  #replace spaces

  userbg = userbg.replace("%20", " ")

  us_bground=pygame.image.load(userbg).convert()   #Background user

except:

  if (len(userbg) > 0):

        if tablet==1:

                osso_c = osso.Context("osso_test_note", "0.0.1", False)

                note = osso.SystemNote(osso_c)

                result = note.system_note_dialog("Can't read the user wallpaper", type='notice') 

                print result



  #Use default background

  us_bground=pygame.image.load(path+"sosbg.png").convert()

That adds the check to see if the background is set to nothing, and it loads the default background if so (I'll add a bit of code to draw your default background colour, but for now should at least keep that annoying popup away!)

2) Aha! So it's a dbus crashing thing, that makes sense and lines up with the problems others have been having... Can you try a few little things for me?
A) Open ci_deviceMonitor.py, goto line 31, and change:

Code:

name = dbus.service.BusName(BME_REQ_IFC, bus=self.bus)

to read

Code:

self.name = dbus.service.BusName(BME_REQ_IFC, bus=self.bus)

Save it, try again and see if the problem still exists or not.

B) If problem still exists, please try opening up ci_dbus.py, line 73 reads:

Code:

self.HelloSignal("Ok");

Try just adding the # to comment it out like this:

Code:

#self.HelloSignal("Ok");

And again give it a shot, see if the problem is still there, and please let me know so that if one of the above does fix the problem I can roll it into an update!

LABAUDIO, one quick thought I just had... when you set an alarm, exit the app, and open it up again manually (i.e. before the alarm is triggered), if you go to the alarms page, does the alarm actually still show up there?? Did you remember to erase the old config file manually before installing the latest build (I mentioned before that the config file from Ciro's clock didn't work with the latest builds so you had to manually remove it).... the more I think about it, the more this sounds like exactly the cause of your problem...

Thanks!

Re: Flip clock pre pre pre pre release

Quote:

Originally Posted by jolouis (Post 274773)

LABAUDIO, one quick thought I just had... when you set an alarm, exit the app, and open it up again manually (i.e. before the alarm is triggered), if you go to the alarms page, does the alarm actually still show up there??

YES all is show up (for 7 day after 3 reboot) all be saved!

Quote:

Originally Posted by jolouis (Post 274773)

Did you remember to erase the old config file manually before installing the latest build (I mentioned before that the config file from Ciro's clock didn't work with the latest builds so you had to manually remove it)....

i never see this old config for erasing manually before
where it is?

but anyway is not problem whit ''save'' but ''trigger'' the alarm when the application is close it.

Like i said...all work exept when the application is closed.

Let me know if you find a solution

and the
the more I think about it, the more this sounds like exactly the cause of your problem...

Thanks!

Re: Flip clock pre pre pre pre release

LABAUDIO: try setting an alarm for a few minutes in the future, then quit the application. Open up an x-term, and type "flipclock" so that the app opens up again. Wait a few minutes until the alarm time has passed (I assume nothing will happen based on what you've described before), and then post up the console output so I can see if the alarm is actually being triggered at all, or if you're having a problem similiar to wax4213.

Thanks!

Re: Flip clock pre pre pre pre release

here this is output when the application still open...all work on this way

Code:

/usr/lib/python2.5/site-packages/flipclock/flipclock.py:4: RuntimeWarning: import cdrom: No module named cdrom

  import pygame

/usr/lib/python2.5/site-packages/flipclock/flipclock.py:4: RuntimeWarning: import joystick: No module named joystick

  import pygame

sent

on_battery

python-launcher-daemon[1566]: GLIB DEBUG ConIc - con_ic_connection_send_event(0x33b410, a3033f6a-9dd9-4f81-96fb-2ab7a436d815, WLAN_INFRA, 0)

Received alarm trigger

found matching alarm, running

trying to load filefile:///media/mmc1/mp3/J'ai pas de face.mp3

set vol to 0

done running alarm

1236897180

<enum GST_STATE_PLAYING of type GstState>

Playing

alarm stopped

{'sound': "file:///media/mmc1/mp3/J'ai pas de face.mp3", 'snoozeTime': 10, 'alarm_index': 4, 'recurrence_count': -1, 'ampm': 0, 'alarm_cookie': 1236897180, 'title': 'Flipclock Alarm 5', 'enabled': 1, 'loopSound': 0, 'alarm_time': 1236897180, 'recurrence': 10080, 'alarm_day': 4, 'alarm_hhmm': '1833', 'alertMode': 1}

done stopping alarm

snoozed

<enum GST_STATE_NULL of type GstState>

None

done main loop

Re: Flip clock pre pre pre pre release

here i test some others way and here i found something weird...

-i set an alarm for the next 10 minutes at 17:00
-the gray box wait appear and disappear...
-i close the application...
-i reboot my n8x0...

=at 16:59 the application open 1 minute before the alarm setting time...
=at 17:00 the alarm ring perfectly at the rigth times

woot

but if i dont reboot after alarm is set at 17:00 :

-i close after setting...
-i waiting...
-at 17:00 the application open at the rigth times of the alarm's be set
-at 17:02 the alarm finaly ring (2 minutes lately)

so in fact...when we rebooting after set alarm = All work perfectly all the way

but when i dont rebooting the device...the alarm is 2 minutes late (when the application be close after setting alarm)

But when you dont close the application after setting alarm...all work perfectly
i follow developements here tonite

Re: Flip clock pre pre pre pre release

LABAUDIO, Wow, that is strange... It sounds a lot like there's something consuming CPU or the clock application is getting caught up when it first relaunches and not actually processing the trigger until it finishes doing whatever it is that it's doing... I assume you don't have any other apps or anything running during testing that might be holding it up?
It seems very strange that everything works if you restart the tablet, but not if you leave it running... that could also be something related to alarmD, but on the other hand it really doesn't make sense since the application does indeed get launched. Can you try going into ci_dbus.py, line #50 there's this:

Code:

                #Alarm was triggered!

                print "Received alarm trigger"

And try adding:

Code:

                osso_c = osso.Context("osso_test_note", "0.0.1", False)

                note = osso.SystemNote(osso_c)

                result = note.system_note_dialog("Running alarm", type='notice')

That should make a popup show when an alarm is actually triggered. Do your same test (the way that didn't work properly), and see if the popup message shows up or not.
Can anyone else reproduce this problem? Thus far I've been unable to on any of the 3 N800's I've got here...

Thanks!