Re: Re: PM-8200 Todo Support Added

Stephen Wood <[email protected]>
Newsgroups gmane.comp.mobile.bitpim.devel
Message-ID <[email protected]>
On 12/14/05, Jordan Foley <[email protected]> wrote:
>
> You can just transfer the copyright over since you did most of the work
> haha, I just troubleshooted the code, being in the credits is enough for
> me. :)


OK.  I'll make sure you are on the credits page.

The problem with the sms function is that for some reason it will only
> grab the messages out of my inbox so I hardcoded the folder to Inbox. On
> my phone I have the folders Inbox, Sent, Outbox, Drafts. The Outbox isnt
> used and the Drafts would be the same as Saved in BitPim. I ran your
> foldernamerequest and it did not return anything useful, but I will look
> at it again. Just wondering what does the packettype mean? I noticed
> that in the packet it returns one of the values is 0B instead of 0C. Did
> you just find all of this by guessing or was it an educated guess.


It was a long time ago that I investigated all this, and only with the
4900.  These SMS packet definitions were found by trial and error.  I tried
all possible combinations of packettype (actually just 0x0 to 0x0f) and
command (0x0 to 0xff) and looked for interesting stuff coming back.  I have
only repeated this in limited ways for phones newer than the 4900.  I have a
couple of donated 8200's, so if you would like I could try to do a command
scan in the next few days and send you the results.  My experience is that
it is safe to send random packets to sanyo phones, as long as you don't put
the phone into update mode (with the beginupdaterequest packet).  But it is
probably better to do such a scan with a discarded phone if possible.

Also do the newer sanyos support memos because I can not find this
> function on my phone. All I have is voice memos.

I don't recall that the older Sanyo phones had memos either.

Now retrieving voice memo's might be another interesting project!

Stephen
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.