Notices

Arrgh.. it's to complicated, I rather quit before I ruin my device ;-)

Thanks a lot rmoravcik!

Could you please add also a binary for a i486 target?

It would help. So can some not so advanced user test it on the SDK before they try it on their real devices without the needed knowledge how to compile it temself.

Edit:
@mumac: Perhaps if you have the knowledge in some month you can move your SMS then from your old device to your N900.

A GUI would help a lot of us noobs for this.
Do we add to the garage?

@Helmuth:

Yeah, you are right. I am just too scared to play with the x terminal, not that I will damage my device...

I haven't tried to use the tool yet, but from a look over the source one suggestion for an improvement is, when getting the contact (remote_ebook_uid ) from the number on the sms you could possibly change the lookup from a full compare of the sms number and contact number to a lookup comparing the last 7 digits of both numbers.

e.g., change line 240 on smsimporter.c from

if (!strcmp (number, remote_uid)) {

to

if (g_str_has_suffix (number, group_uid))

This should allow you to match the contact even if the sms number is in full international format and the contact isn't saved that way.

First of all, thank you for the app!

Sadly, though, it doesn't work for me. I copied the inbox and sent folders to my N900 via Bluetooth, but I get a segfault using v0.2.

One thing that strikes me about the code is that the char array text only holds 161 bytes including the final NULL-byte. I'd be fine with that, but some of my old SMS on my N70 are way longer than that (read: 752 Bytes + \0). The N70 supports up to 30 SMS "in one".

Unfortunately, I have no clue how to compile stuff for the N900 to add debug code to go about and find the problem causing the segfault.

/edit: Just did some debugging on my x86 box: If you malloc 2 bytes for delimiter before memcpy'ing it from the buf pointer it doesn't segfault there anymore. I can't say if that's also the deal on the N900.

Just a random side note: smsimporter can't parse the line if the delimiter also exists in the SMS's text - could you somehow work around that? What about quotation marks in the text's content? Keep up the good work

Thank you rmoravcik for the application.

Unfortunately, it didn't work for me. It gives me always the message "Segmentation fault".

Can someone show an example of a sms in csv format that works with the smsimporter?

Thanks.

Could the segmentation fault be because there arer semicolons " ; " in the actual body of some of the text messages?

There's a fatal problem in the code. No memory is allocated to delimiter, which causes the segmentation faults. (But it does indeed at least try to detect the delimiter despite earlier comments, perhaps it was added to version 0.2?) By happy coincidence it sometimes works, though . The fix is simple, though, I put the patch here: http://modeemi.fi/~flux/software/mae...iter-fix.patch
. A compiled binary (only the binary!) is at http://modeemi.fi/~flux/software/maemo/smsimporter (..until I remove it).

Thanks for this very useful piece of software!

I tried with one single sms without special chars and the problem continues.

In attachment i put the test file i tried to import.

Thanks