Active Topics
-
The N900 is now 15 years old! (8)
to Nokia N900 by whayong - 6 hrs, 13 mins ago -
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (4)
to SailfishOS by Maemish - 5 days, 2 hrs ago - more...
| The Following 2 Users Say Thank You to Spenc3 For This Useful Post: | ||
|
2010-06-03
, 22:41
|
|
Posts: 52 |
Thanked: 44 times |
Joined on Dec 2008
@ Mississauga, ON
|
#522
|
Originally Posted by 白い熊
Bug tracked for the alarm sync issue... i was able to recreate it.. have to look at it why it didn't take...
There's a catch.
On the N900 it seems flipclock only syncs the alarms, every second try. I.e. set an alarm, go back to the main screen... If you see the system message "Alarms synced..." it'll sound.
If now you go reset the alarm to some other time, and go back to the main screen, it doesn't sync the alarm, i.e. no info message. Fliplock still shows 8 hours till the alarm, or what have you, but it ain't gonna sound.
If you just go in to set the alarm again, don't change anything and go back to the main screen, it'll show the message "Alarms synced" and it'll sound then at the alotted time.
This is the biggest catch... serious, I also learnt the hard way...
__________________
Your friendly neighbourhood geek -- Spenc3
Your friendly neighbourhood geek -- Spenc3
| The Following User Says Thank You to Spenc3 For This Useful Post: | ||
|
|
2010-06-04
, 03:32
|
|
Posts: 451 |
Thanked: 334 times |
Joined on Sep 2009
|
#523
|
Originally Posted by Spenc3
I'm curious what you discover, as to what's causing it...
Bug tracked for the alarm sync issue... i was able to recreate it.. have to look at it why it didn't take...
|
|
2010-06-04
, 04:31
|
|
Posts: 52 |
Thanked: 44 times |
Joined on Dec 2008
@ Mississauga, ON
|
#524
|
Originally Posted by 白い熊
i was just able to recreate it.. haven't dive into it yet to find out what's wrong...
I'm curious what you discover, as to what's causing it...
Let you know once i dive into it.
__________________
Your friendly neighbourhood geek -- Spenc3
Your friendly neighbourhood geek -- Spenc3
| The Following User Says Thank You to Spenc3 For This Useful Post: | ||
|
|
2010-06-04
, 17:54
|
|
Posts: 39 |
Thanked: 0 times |
Joined on Oct 2007
|
#525
|
Originally Posted by Spenc3
I had sound with my alarm again this morning. It was a different song than yesterday, so it looks like 0.97-7 is behaving for me now, but there are still five days' worth of alarms that haven't been verified yet.
There's another hidden file in the phone under /home/user/.flipClockPrefs.xml
If another alarm didn't sound, can yo send me the file then?? you can attach it in the garage page
This weekend I'll make a list of a few songs that FlipClock refuses to play - full pathnames and ID3 tags.
Will FlipClock freak out if I copy the Prefs file to save it while I do some experiments and restore it afterwards?
|
|
2010-06-06
, 01:34
|
|
Posts: 39 |
Thanked: 0 times |
Joined on Oct 2007
|
#526
|
What's a good command line tool to read the ID3 tag on either an N800 or a Mac?
|
|
2010-06-06
, 01:36
|
|
Posts: 39 |
Thanked: 0 times |
Joined on Oct 2007
|
#527
|
Path of a file that won't play as an alarm:
<sound>/media/mmc1/Audio/David Lindley & El Rayo-X/Win This Record!/01. Something's Got A Hold On Me.mp3</sound>
<sound>/media/mmc1/Audio/David Lindley & El Rayo-X/Win This Record!/01. Something's Got A Hold On Me.mp3</sound>
|
|
2010-07-11
, 13:46
|
|
Posts: 1 |
Thanked: 4 times |
Joined on Jul 2010
|
#528
|
Hi! I quite like flipclock, but had the same random alarm issues as some N900 users reported before.
Well, I took a look at the code and I think I know what the problem is. The alarmdv2 interface expects the recurrence in secs, not minutes. However, the internal recurrence of flipclock is in minutes, which as far as I understand is necessary for the older alarmd interface. Therefore, on the N900, there is an alarm every 10080s ~ 3h instead of every week. If you specify an alarm e.g. at 8:00, there will be another one at 10:48, 15:36 and so on. And since alarmd automatically pushes alarms in the past to the next valid time, that looks pretty random at the end :-).
My solution was simply to put a factor of 60 in line 508 of the SVN alarmDv2Func.c, where the recurrence is copied (note that the field is called recur_secs...). Like this, only the newer alarmd is fixed, and so far I get the alarms at the time I expect them :-).
Thanks for the nice program!
Well, I took a look at the code and I think I know what the problem is. The alarmdv2 interface expects the recurrence in secs, not minutes. However, the internal recurrence of flipclock is in minutes, which as far as I understand is necessary for the older alarmd interface. Therefore, on the N900, there is an alarm every 10080s ~ 3h instead of every week. If you specify an alarm e.g. at 8:00, there will be another one at 10:48, 15:36 and so on. And since alarmd automatically pushes alarms in the past to the next valid time, that looks pretty random at the end :-).
My solution was simply to put a factor of 60 in line 508 of the SVN alarmDv2Func.c, where the recurrence is copied (note that the field is called recur_secs...). Like this, only the newer alarmd is fixed, and so far I get the alarms at the time I expect them :-).
Thanks for the nice program!
| The Following 4 Users Say Thank You to awa For This Useful Post: | ||
|
|
2010-07-11
, 16:35
|
|
Posts: 52 |
Thanked: 44 times |
Joined on Dec 2008
@ Mississauga, ON
|
#529
|
Originally Posted by awa
Thanks for the the code change in the SVN and have JoLouis update the deb (nudge nudge)...
Hi! I quite like flipclock, but had the same random alarm issues as some N900 users reported before.
Well, I took a look at the code and I think I know what the problem is. The alarmdv2 interface expects the recurrence in secs, not minutes. However, the internal recurrence of flipclock is in minutes, which as far as I understand is necessary for the older alarmd interface. Therefore, on the N900, there is an alarm every 10080s ~ 3h instead of every week. If you specify an alarm e.g. at 8:00, there will be another one at 10:48, 15:36 and so on. And since alarmd automatically pushes alarms in the past to the next valid time, that looks pretty random at the end :-).
My solution was simply to put a factor of 60 in line 508 of the SVN alarmDv2Func.c, where the recurrence is copied (note that the field is called recur_secs...). Like this, only the newer alarmd is fixed, and so far I get the alarms at the time I expect them :-).
Thanks for the nice program!
__________________
Your friendly neighbourhood geek -- Spenc3
Your friendly neighbourhood geek -- Spenc3
 |
|
2010-07-11
, 17:14
|
|
Posts: 120 |
Thanked: 14 times |
Joined on Jun 2010
@ Queens, NY
|
#530
|
Once it's updated I will redownload and install.
__________________
Device: Nokia N900
Theme: MaemoItalia Graffiti Theme
---
Who but me?!
--HeavyC.
Device: Nokia N900
Theme: MaemoItalia Graffiti Theme
---
Who but me?!
--HeavyC.
If another alarm didn't sound, can yo send me the file then?? you can attach it in the garage page
Your friendly neighbourhood geek -- Spenc3