Re: Bug report - SMS Sent Items and Sanyo MM-7500

-= Delphicoder =- <[email protected]>
Newsgroups gmane.comp.mobile.bitpim.devel
Message-ID <[email protected]>
I appreciate the quick response Stephen.  I have attached a text file containing the send and receive of the same message.  I believe the problem lies in offset "00000110", as you will notice that the data is offset by 1 to the right on the second set of data.

Open the file in Wordpad so it can keep the proper formatting.

>From what I could gather, the first set of data is from the Inbox folder and the second from the Outbox/Sent Items.

Thanks again!


--- On Wed, 7/23/08, Stephen Wood <[email protected]> wrote:
From: Stephen Wood <[email protected]>
Subject: Re: [BitPim-devel] Bug report - SMS Sent Items and Sanyo MM-7500
To: [email protected], [email protected]
Date: Wednesday, July 23, 2008, 11:15 PM

Delphicoder:

Could you send me (privately is fine), a bigger extract from the
protocol log, either the whole thing, or enough to include several
Sent and Received text messages.

Thanks, Stephen

On Tue, Jul 22, 2008 at 4:08 PM, -= Delphicoder =-
<[email protected]> wrote:
> Devs:
>
> Versions used during testing:  1.0.5 Stable and 1.0.6.2008.07.07
>
> I recently activated a Sanyo MM-7500 after testing the functionalities
with
> BitPim.   The tests seemed to work as expected (ie. Phonebook transfer and
> SMS).  The only thing that I noticed is a problem is the way BitPim is
> reading messages from the SMS 'Sent' folder.  The message is
properly
> formatted, but the DATE/TIME are off.  They're 'right shifted'
to be exact.
>
> Currently, the data posted below should read:
>
> ** Note ** - Phone number changed to zeros in example and data log
provided
> below
>
> Callback #: (000) 000-0000
> Date: 2008-07-21 16:27
>
> Instead, it reads:
>
> Callback #: <Blank>  <---  Nothing displayed
> Date: 2000-08-07 21:16:27   <-- Notice the right shifting of the data
>
> In the list of messages, the phone number is displayed correctly, but is
> preceded by a square (ie. more than likely the 0A, or carriage return
found
> in the data location immediately before the phone number)
>
> I would greatly appreciate your assistance on this.  I look forward to
> testing out the bug fix.
>
> Thanks goes to Joe Pham, the rest of the developing crew and those that
have
> contributed patches and bug reports in the past to keep this project
going.
> Good work!!!
>
>
> Actual data below:
>
> "00000000 fa 00 02 e1 0c 00 11 01 00 00 00 81 18 3c 00 02
> .............<..
> 00000010 01 00 3b 54 68 69 73 20 20 69 73 20 61 20 74 65     ..;This  is a
> te
> 00000020 73 74 20 6d 65 73 73 61 67 65 20 66 72 6f 6d 20     st message
from
> 00000030 74 68 65 20 72 65 63 65 6e 74 6c 79 20 61 63 74     the recently
> act
> 00000040 69 76 61 74 65 64 20 70 68 6f 6e 65 2e 20 00 00     ivated phone.
> ..
> 00000050 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> ................
> 00000060 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> ................
> 00000070 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> ................
> 00000080 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> ................
> 00000090 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> ................
> 000000a0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> ................
> 000000b0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> ................
> 000000c0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> ................
> 000000d0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> ................
> 000000e0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> ................
> 000000f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> ................
> 00000100 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> ................
> 00000110 00 00 00 08 07 15 10 1b 31 0a 30 30 30 30 30 30
> ........1.000000
> 00000120 30 30 30 30 00 00 00 00 00 00 00 00 00 00 00 00
> 0000............
> 00000130 00 00 00 00 00 00 00 00 00 00 00 00 0a 30 30 30
> .............000
> 00000140 30 30 30 30 30 30 30 00 00 00 00 00 00 00 00 00
> 0000000.........
> 00000150 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> ................
> 00000160 00 00 00 64 00 00 00 01 00 00 00 00 00 00 00 00
> ...d............
> 00000170 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> ................
>
>
>
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
> Build the coolest Linux based applications with Moblin SDK & win great
> prizes
> Grand prize is a trip for two to an Open Source event anywhere in the
world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> BitPim-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/bitpim-devel
>
>

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/

_______________________________________________
BitPim-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bitpim-devel
txt-msg.txt (text/plain, 8.2 KB) - not displayed
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.