Discussion:
[BitPim-devel] LG G4015 Testers?
Joe Pham
2005-10-20 04:54:12 UTC
Permalink
Anyone who has a G4015 and can run BitPim off source, and willing to help? I need to verify the data format for the SMS messages & Call History data, and since my loaner has no services, I have no real data to verify.

TIA,

-Joe Pham


______________________________________________________________________
Revolutionize the way you surf the Web!
Try NetZero HiSpeed 3G.
Visit http://www.netzero.com to sign up today!
littletux
2005-11-16 10:56:31 UTC
Permalink
Post by Joe Pham
Anyone who has a G4015 and can run BitPim off source, and willing to help? I need to verify the data format for the SMS messages & Call History data, and since my loaner has no services, I have no real data to verify.
Hi, i have no G4015 but a T5100 (a LG GSM phone too, seen as "G7200"
using serial cable).
Much of the code for the G4015 also works for this phone (I could import
phonebook, wallpaper index, ringtone index, calendar, memos, with very
little modifications:).

So, about the SMS, i've noticed an issue importing messages containing
carriage returns ('\x0a'): the massage isn't imported fully, and then
the next message import fails (doesn't find the '+CMGL: ' string but the
rest of the previous message). I didn't try to fix this yet.

To fix the display of Inbox, I had to change in sms_tab.py, l 48:
- int(v[9:11]), int(v[11:13]), int(v[13:])))
+ int(v[9:11]), int(v[11:13]), int(v[13:15])))

I did test Call History briefly, I think the commands are wrong for my
phone : they result in AT Errors.

Joined are other patches for the T5100. Don't know if it can help with
the G4015.
"com_" and "p_" patches apply to a copy of respective file for the
G4015.

BTW, can support for the T5100 be added in bitpim ?
Anyway, thanks for the great software;)

Best regards,

Guillaume B.

PS:
USB should be disabled for T5100 as these kinds of syncs don't work with
this cable (only photos, videos and mp3 with usb, see t5100-utils for
now to do this).
littletux
2005-11-18 10:59:58 UTC
Permalink
Hello !
Post by littletux
So, about the SMS, i've noticed an issue importing messages containing
carriage returns ('\x0a'): the massage isn't imported fully, and then
the next message import fails (doesn't find the '+CMGL: ' string but
the rest of the previous message). I didn't try to fix this yet.
So I answer myself about this : it seems simpler to handle SMS using
"Base64" encoding instead of "IRA". The Base64 encoded newlines just
don't result in split strings. WDYT ?

I may send an other patch for this soon...

Regards,

Guillaume B.

Loading...