Active Topics
-
[ANNOUNCE] MeeShop - new app store (8)
to Applications by Maemish - 5 hrs, 8 mins ago -
HTTP-401 Sfos-Builder when using /etc/ssu credentials (0)
to SailfishOS by insanelysexy - 9 hrs, 38 mins ago -
Longtime users: What device(s) are you using today? (54)
to General by ryu1 - 2 days, 15 hrs ago -
Registering (1)
to General by Halftux - 5 days, 7 hrs ago -
Applications Wishlist (55)
to Maemo 7 / Leste by sixwheeledbeast - 6 days, 10 hrs ago - more...
|
2010-11-08
, 19:48
|
|
Posts: 35 |
Thanked: 13 times |
Joined on Feb 2010
|
#12
|
I'm afraid I found a workaround. I've rarely been this horrified by the behavior of a piece of software, and I wish I could say this was the first time for Maemo.
First, to see what I'm talking about, go into the calendar app, and try to set an alarm on something. Note the list of options that comes up. Note that it is *impossible* to set, say, a 10 minute alarm (let alone an 11 minute alarm). Which is a travesty, if you ask me.
The basic problem is that Maemo's MfE is now *enforcing those options*, even on alarms that come from somewhere else.
The "workaround": [edit: keep reading, there's a better one]
1. Set the alarm for something that isn't alarming to one of the acceptable values (to save you trouble: 0 min, 5 min, 15 min, 30 min, 1 h, 3 h, 1 d; that's *IT*)
2. Go into the MfE settings. Disable sync for everything but calendar, or this will take *forever*.
3. Go into the MfE settings. At the bottom, force a *full* resynchronization. On my phone, with nothing but calendar, synchronizing back to "all entries", this takes 20+ minutes.
It gets better, though: you have to do this *every time* you change an alarm anywhere but the phone. Even if you set an alarm to one of the allowed values, a full resync is required to pick up the change. If you set it to any other value, it just doesn't work at all.
But it gets better: it's bi-directional. Setting the alarm time on the phone and doing a regular sync does nothing to the remote calendar. Doing a full resync makes it respect your "if conflict" setting; in my case, that's the remote server, so it just tosses all the changes on the phone.
[edit: BETTER WORKAROUND]
Oh, wait! I just found another way that works with a normal sync!
If you change *something else* about the event, like the time, *and* change the time to one of the supported times, a regular sync picks it up. In both directions!
(When I change the time on my phone, the Google time ends up 1 hour early, but I assume that's a totally unrelated bug
-Robin
First, to see what I'm talking about, go into the calendar app, and try to set an alarm on something. Note the list of options that comes up. Note that it is *impossible* to set, say, a 10 minute alarm (let alone an 11 minute alarm). Which is a travesty, if you ask me.
The basic problem is that Maemo's MfE is now *enforcing those options*, even on alarms that come from somewhere else.
The "workaround": [edit: keep reading, there's a better one]
1. Set the alarm for something that isn't alarming to one of the acceptable values (to save you trouble: 0 min, 5 min, 15 min, 30 min, 1 h, 3 h, 1 d; that's *IT*)
2. Go into the MfE settings. Disable sync for everything but calendar, or this will take *forever*.
3. Go into the MfE settings. At the bottom, force a *full* resynchronization. On my phone, with nothing but calendar, synchronizing back to "all entries", this takes 20+ minutes.
It gets better, though: you have to do this *every time* you change an alarm anywhere but the phone. Even if you set an alarm to one of the allowed values, a full resync is required to pick up the change. If you set it to any other value, it just doesn't work at all.
But it gets better: it's bi-directional. Setting the alarm time on the phone and doing a regular sync does nothing to the remote calendar. Doing a full resync makes it respect your "if conflict" setting; in my case, that's the remote server, so it just tosses all the changes on the phone.
[edit: BETTER WORKAROUND]
Oh, wait! I just found another way that works with a normal sync!
If you change *something else* about the event, like the time, *and* change the time to one of the supported times, a regular sync picks it up. In both directions!
(When I change the time on my phone, the Google time ends up 1 hour early, but I assume that's a totally unrelated bug
-Robin
| The Following User Says Thank You to rlpowell For This Useful Post: | ||
|
|
2010-11-08
, 20:50
|
|
Posts: 35 |
Thanked: 13 times |
Joined on Feb 2010
|
#13
|
I have created https://bugs.maemo.org/show_bug.cgi?id=11556
Please add comments there if you are having this issue.
-Robin
Please add comments there if you are having this issue.
-Robin
| The Following User Says Thank You to rlpowell For This Useful Post: | ||
Last edited by marioaguado; 2010-11-04 at 21:35.