Re: [Opensync-users] Trying to synchronize text messages (sms) to/from Nokia N80

[Brian J. <br...@do...>]

Daniel,

Thanks for getting back to me. I have not had a chance to try out the
patch, but I will when I get home (I'm at work).

Regarding the "PC Suite 2" profile. Nokia by default on their Series 60
version 3 phones (Nokia E/N-Series) have a default "PC Suite" sync profile
in Connectivity -> Sync. Unfortunately, this profile only allows you to
use SyncML over Bluetooth/USB to sync the contacts, notes and calendar
(todo in S60v3 is part of the calendar). If the user wants to synchronize
additional items -- the only other items are browser favorites -- which I
need to talk to you about when you get some free time, and text messages
"sms", then the user has to create another sync profile. In the profile
settings, there is an option to pick an identifier. This is how SyncML
determines which profile to use. I simply called it PC Suite 2.

- Brian

On Wed, January 2, 2008 5:28 am, Daniel Gollub wrote:
> On Wednesday 02 January 2008 08:10:55 Brian Johnson wrote:
>
>> With that said, when using the
>> syncml-obex-client command line program, I get the following output (I
>> assume this is good):
>>
>> $ syncml-obex-client -u 0 --identifier "PC Suite 2" --wbxml --sync
>> "text/x-vMessage" Messages
>> connection with device succeeded Received an Alert for the DS Server at
>> Messages: Type: 201, Last , Next
>> 20080102T065600Z
>> Just received a new session with ID 1
>> Received the DevInf
>> Session 1 reported final. flushing
>>
>
> Interesting. You changed the profile on your mobile to "PC Suite 2"
> right? Didn't know that there is a relation.. i wonder how determine the
> available profiles...
>
> Could you try --slow-sync instead of --sync as well .. this should get
> all message (not only the latest one). Just to proof that it's working...
>
>> I did notice that the phone responds when using the "text/x-vMessage"
>> mime type on syncml-obex-client, and I do not know if objtype = data,
>> objformat = plain corresponds to text/plain, but I somehow need to get
>> msynctool to use text/x-vMessage.
>
> Correct, currently there handling of this mimetype is missing. Actually
> we should provide another field (e.g. <mimetype>) and drop the <objtype>
> field. <objtype> isn't needed since the <objformat> is mapped to one
> objtype already (redundancy).
>
>
> Anyway, i just did an untested hack to just hardcode text/x-vMessage for
> <objformat> plain, for testing purposes.
>
>
> best regards, Daniel
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/___________________
> ____________________________
> Opensync-users mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/opensync-users
>
>