maemo.org - Talk - iSync and Mac support with maemo 5

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

- Maemo 5 / Fremantle (https://talk.maemo.org/forumdisplay.php?f=40)

- - iSync and Mac support with maemo 5 (https://talk.maemo.org/showthread.php?t=31345)

Re: iSync and Mac support with maemo 5

Btw, the ;PT3M seems to be the "snooze" time, which in this case would be 3 minutes.

I am really puzzled why nothing else than ISync is stumbling over this bogosity. Maybe other vcal-parsers are simply ignoring those bogus lines.

Re: iSync and Mac support with maemo 5

Quote:

Originally Posted by 3quid (Post 474769)

Hi Guys,

I have also written a plugin to do this (before realising there was one in progress here!)

I have everything working as far as I can see minus two things. Events with alarms. If they are created in iCal the event is transferred to the N900 just fine but minus their alarms. If they are created (with alarms) on the N900 they do not transfer to iCal at all.

I see you are having trouble transferring events made on the N900 to the mac. My plugin does that correctly (apart from the alarm issue). Do the events transferred by your plugin (from iCal to N900) have alarms set? If so do they still have alarms once in the N900?

You can grab my plugin in here if anyone wants it :)

Anyone who does try mine out. Let me know how you get on.

Cheers :)

After struggling with the instructions here, the only way I could get my Mac to recognize the plug in was if it was in ~/Library/PhonePlugIns v. /Library/PhonePlugIns. In other words, in my user folder. You have to create the PhonePlugIns folder if it doesn't already exist.

Now to see if it works...fingers crossed.

Re: iSync and Mac support with maemo 5

Quote:

Originally Posted by 3quid (Post 474769)

Anyone who does try mine out. Let me know how you get on.

Cheers :)

Thanks !
It works great for me.
But... the birthday field is erased when transfered to the N900 (and then erased in the contacts on my Mac).

Re: iSync and Mac support with maemo 5

One last plan of attack :-
1) Create alarmed event on Mac
2) Sync
3) Modify on N900 keeping alarm details
4) Sync, and monitor bluetooth packets and detailed iSync log
I want to see if the AALARM details are formatted any differently in this scenario.

Re: iSync and Mac support with maemo 5

Quote:

Originally Posted by scudderfish (Post 482209)

I just tried that sequence.

Having changed the name of the event in the version sync'd to my N900 it then failed to parse when I tried to resync. In the console log it shows it has removed the Z from the original sync and added the "; PT7M ;" to the end.

Re: iSync and Mac support with maemo 5

So after many hours (w/3quid's plug-in), I'm finally all in sync, at least for my contacts. I haven't had time to evaluate the calendar part yet. In due time.

I have 2400 contacts in my phone and syncing didn't love that so much so I created a dummy group in my address book and added 300 or so contacts at a time, syncing after each. Hope this helps someone else.

Re: iSync and Mac support with maemo 5

Quote:

Originally Posted by 3quid (Post 482346)

(sending this from my N900 whilst I wait for my train home :) ) Does it also put in the dodgy CRLF ?

Re: iSync and Mac support with maemo 5

Quote:

Originally Posted by scudderfish (Post 482374)

(sending this from my N900 whilst I wait for my train home :) ) Does it also put in the dodgy CRLF ?

Yes, unfortunately it does. The format of the failing event looks exactly like one originally created on the N900.

There MUST be a way of stopping it doing this!

Re: iSync and Mac support with maemo 5

it's like we need some sort of filter program that sits between the bt interface and the n900 syncml stack

Re: iSync and Mac support with maemo 5

Quote:

Originally Posted by scudderfish (Post 482436)

it's like we need some sort of filter program that sits between the bt interface and the n900 syncml stack

Yup exactly. It's a pretty simple change that's required. Will persevere with it but I am running out of ideas. If we could find out what file/app that creates that code it would be pretty handy.