bitpim-devel — For bitpim developers

Re: [Bitpim-devel] 0.7-test11 now available

[Roger B. <ro...@ro...>]

Stephen Wood wrote:
> It worked OK on XP Home for a couple of Sanyo phones.

Except for all the egrigious spelling errors in the help you
just fixed :-)  

All my pre-release tests were fine and there is nothing new
that should tickle any problems.  test10 on Windows actually
had the Outlook 2000 type library included which worried
me a bit.

Roger

Re: [Bitpim-devel] 0.7-test11 now available

[Stephen W. <sa...@us...>]

It worked OK on XP Home for a couple of Sanyo phones.

Re: [Bitpim-devel] bitpim with non-supported phones

[Roger B. <ro...@ro...>]

> It would appear to me that the data from the newer Kyocera phones is 
> stored a bit differently from the other phones that are
> supported by bitpim, but I am not that familiar with the code, so I could 
> easily be wrong.  I wonder if anyone more familiar with
> the file system code could easily make a modification to support these phones?  

For some reason the 'unknown2' field is one byte longer.  Or the name
has one more prefix byte depending on how you view it.

I am working on some code that should work for all phones.  Please can you
post what protocol you get for listing files in the root directory.

> p_brew.listfileresponse
>   responseheader header: <p_brew.responseheader>
>     UINTlsb commandmode: 89 0x59
>     UINTlsb command: 11 0xb
>     UINTlsb errorcode: 0 0x0
>   UINTlsb entrynumber: 2 0x0
>   UNKNOWN unknown1: '\x01\xff\x00\x01'
>   UINTlsb date: -1356481536 0xaf25bc00
>   UINTlsb size: 2808621 0x2adb2d
>   UNKNOWN unknown2: '\x00\x00,\x00\x00'
>   STRING filename: '\x19user/mypictures'

Did you type that all in by hand?

Roger

[Bitpim-devel] 0.7-test11 now available

[Roger B. <ro...@ro...>]

http://sf.net/project/showfiles.php?group_id=75211&package_id=76673&release_id=240693

Please post if you see any problems.  The main announcement will go out
tomorrow.

So far the only issue I know about is that the VX4500 cable page was
not updated (I forgot :-)  It is updated on the web site.

Roger

[Bitpim-devel] bitpim with non-supported phones

[DanW <da...@ho...>]

I finally had a chance to view the data from my phone in the protocol =
analyzer.

bitpim 7 betas seem to accurately read the folder names, but not the =
file names.


Here is the partial information from the Protocol Log screen:

11:41:46.479 Other CDMA Phone: Listing dir 'user/mypictures'

11:41:46.709 Other CDMA Phone: brew response Data - 51 bytes
<#! p_brew.listfileresponse !#>
00000000 59 0b 00 01 00 00 00 01 ff 00 01 00 56 23 af 2d     =
Y...........V#.-
00000010 35 17 00 00 00 18 00 00 10 19 75 73 65 72 2f 6d     =
5.........user/m
00000020 79 70 69 63 74 75 72 65 73 2f 42 6d 70 30 31 2e     =
ypictures/Bmp01.
00000030 70 6e 67                                            png

11:41:46.719 Other CDMA Phone: brew request Data - 23 bytes
<#! p_brew.listfilerequest !#>
00000000 59 0b 02 00 00 00 10 75 73 65 72 2f 6d 79 70 69     =
Y......user/mypi
00000010 63 74 75 72 65 73 00                                ctures.

11:41:46.759 Other CDMA Phone: brew response Data - 51 bytes
<#! p_brew.listfileresponse !#>
00000000 59 0b 00 02 00 00 00 01 ff 00 01 00 bc 25 af 2d     =
Y............%.-
00000010 db 2a 00 00 00 2c 00 00 10 19 75 73 65 72 2f 6d     =
*...,....user/m
00000020 79 70 69 63 74 75 72 65 73 2f 42 6d 70 30 33 2e     =
ypictures/Bmp03.
00000030 70 6e 67                                            png

11:41:46.759 Other CDMA Phone: brew request Data - 23 bytes
<#! p_brew.listfilerequest !#>
00000000 59 0b 03 00 00 00 10 75 73 65 72 2f 6d 79 70 69     =
Y......user/mypi
00000010 63 74 75 72 65 73 00                                ctures.

11:41:46.789 Other CDMA Phone: brew response Data - 51 bytes
<#! p_brew.listfileresponse !#>
00000000 59 0b 00 03 00 00 00 01 ff 00 01 00 f6 2b af 2d     =
Y............+.-
00000010 d9 3d 00 00 00 40 00 00 10 19 75 73 65 72 2f 6d     =
=3D...@....user/m
00000020 79 70 69 63 74 75 72 65 73 2f 42 6d 70 30 32 2e     =
ypictures/Bmp02.
00000030 70 6e 67                                            png



Here is some sample data from the Protocol Analyzer:

p_brew.listfileresponse
  responseheader header: <p_brew.responseheader>
    UINTlsb commandmode: 89 0x59
    UINTlsb command: 11 0xb
    UINTlsb errorcode: 0 0x0
  UINTlsb entrynumber: 2 0x0
  UNKNOWN unknown1: '\x01\xff\x00\x01'
  UINTlsb date: -1356481536 0xaf25bc00
  UINTlsb size: 2808621 0x2adb2d
  UNKNOWN unknown2: '\x00\x00,\x00\x00'
  STRING filename: '\x19user/mypictures'

00000000  59 0B 00 02 00 00 00 01  FF 00 01 00 BC 25 AF 2D  =
Y............%.-
00000010  DB 2A 00 00 00 2C 00 00  10 19 75 73 65 72 2F 6D  =
*...,....user/m
00000020  79 70 69 63 74 75 72 65  73 2F 42 6D 70 30 33 2E  =
ypictures/Bmp03.
00000030  70 6E 67                                          png

It would appear to me that the data from the newer Kyocera phones is =
stored a bit differently from the other phones that are supported by =
bitpim, but I am not that familiar with the code, so I could easily be =
wrong.  I wonder if anyone more familiar with the file system code could =
easily make a modification to support these phones?

Dan

[Bitpim-devel] Code ready for build

[Roger B. <ro...@ro...>]

Everything is ready on my end.

Roger

Re: [Bitpim-devel] Samsung VGA-1000 phonebook notes

[Stephen W. <sa...@us...>]

This post is just to note for the record a couple of more URL's with
information about talking to Samsung phones.

http://webpages.charter.net/hideo_a310/downs/TechNotes/a310_atcommands.txt

has a list of for the SCH-A310, found by trial and error (similar to the
SCH-8500 list in my previous post).

http://webpages.charter.net/hideo_a310/a310_tech.htm

has a bit more information about the A310.  (The cable I have for the
VGA-1000 actually is labeled A310.)


http://www.howardforums.com/archive/topic/83000-1.html

is a thread about the S105, some other Samsung phone (not CDMA).  There
is more information there about possible AT commands.

				Stephen

Re: [Bitpim-devel] Samsung VGA-1000 phonebook notes

[Roger B. <ro...@ro...>]

Stephen Wood wrote:
> It looks like it has a fairly full file system.  The wallpapers and
> ringers are in the filesystem, so media up/downloads won't be as much a
> pain as the Sanyo's.

It is usually the index files which are the pain.

> One of the AT commands is "AT#PCBIT?" which looks like it returns a
> bunch of useful information like number of entries in phonebook, field
> lengths etc.  This phone returns:

You should look at the GSM specs since the Samsung stuff seems to mostly
be the same.  You can download them from 
http://webapp.etsi.org/key/key.asp?GSMSpecPart1=27&GSMSpecPart2=007

(The required registration process is horrible.  I have the 1MB PDF
downloaded and will email you a copy.  If anyone else wants it, please
email me, or go through the registration crap yourselves.)

I think Motorola phones use a substantially similar protocol.

> #PCBIT: 1008,1,0,5,5,300,300,6,1,12,32,20,32,3,"URL",32,"Birthday",10,"Avatar",2

Well, since you got the new phone, you get to update the commport
code :-)  In particular it will need the following methods I think.

sendatcommand

  This would need to send an AT style command, and then peek at the
  first line returned and if it is an echo back of the command then
  throw the line away.  It could also throw an exception if the
  next line is ERROR and do nothing if it is OK (or return nothing,
  "OK" or "ERROR")

readline
  
  Read the next line of data

readlines

  (Dunno if this is needed)  Read all the lines up until the 
  next OK (or ERROR)

peekline

  Read the next line of data, but preserve it so that it can be 
  returned in the next call to readline

Once you have all that figured out and working, let me know and I
will put it into the BitFling code.

I think we will also need two new types for the protocol description
stuff.  One would be an integer specified in string form, and one
would be a string in CSV quoted form.  It would probably also make
sense to have a new list type as well that seperates entries with
commas.  I would suggest writing a description file, and then I'll
be happy to write the types for it.

It would be good if you can do some investigation of what happens to
string values that have double quotes, carriage returns, commas, backslashes
and other characters in them.  It would also be useful to know how
rigid the whitespace requirements are - for example is leading and
trailing whitespace of the string.

Roger

[Bitpim-devel] Samsung VGA-1000 phonebook notes

[Stephen W. <sa...@us...>]

I have a SCH-620/VGA-1000 now.

It looks like it has a fairly full file system.  The wallpapers and
ringers are in the filesystem, so media up/downloads won't be as much a
pain as the Sanyo's.

I did try writing the schedule file, but as Ben has observed, it is not
easily writable.  I also tried offlining the phone fist, but this didn't
help.

The phonebook uses straightforward AT commands rather than the HDLC used
by Brew mode or phonebook protocols for other phones.

One of the AT commands is "AT#PCBIT?" which looks like it returns a
bunch of useful information like number of entries in phonebook, field
lengths etc.  This phone returns:

#PCBIT: 1008,1,0,5,5,300,300,6,1,12,32,20,32,3,"URL",32,"Birthday",10,"Avatar",2

This might mean that a fairly generic driver that works for multiple
Samsung phones could be developed.

Other commands are AT#PBOKR and AT#PBOKW to read and write phonebook
entries.  AT#PMODE=1 puts the phone into a mode so that it will read and
write the phonebook.

These commands are close to what works with the SCH-8500, a Samsung
Sprint phone of a few years ago.  There is a perl script, sambru, that
talks to the SCH-6100 and SCH-8500.  The author learned the command set
by sending half a million AT commands to his phone.

sambru can be found at http://sandeen.net/sambru/.  There also seem to
be commands for manipulating the calendar.  (AT#PISHR and AT#PISHW).  A
terminal program like hyperterminal or kermit should be sufficient to do
some exploration of this phone.

				Stephen

Re: [Bitpim-devel] Sanyo 4920

[Stephen W. <sa...@us...>]

> 
> Hi,
> 
> Anyone tested this phone? Is it compatible to any of the other phones (like 5500 maybe)?
> 
> Thanks,
> Ron
> 

Try reading the phone book of the 4920, trying setting BitPim both to
the SCP-4900 and the SCP-5500 and let us know what happens.  I wouldn't
try writing to the phone just yet.

				Stephen

Re: [Bitpim-devel] Samsung VGA-1000 schedule file

[Roger B. <ro...@ro...>]

Ben Curtis wrote:
> What I have is basically 47 numbers (b3, e9, af, etc) for each entry and
> determined what each does/means.  

Post here what seems most natural to you and I will translate it.

> Where do I even go to find out about
> synchronization protocols?  

Look to see if any products support the calendar, and then record them
doing so.  DataPilot doesn't.  I can't tell about SnapSync and I
have trouble even figuring out what Smith Micro's product supports.

> I get a really long debug message, the same message that you get if you
> try to do anything in bitpim other than view the filesystem (I.E. Get
> Data).  

That isn't a debug message, it is an error exception and the details
in it actually matter!

Roger

Re: [Bitpim-devel] Samsung VGA-1000 schedule file

[Ben C. <bi...@no...>]

> > I've learned that each entry in the calendar has 47 hex numbers associated
> > with it, and what 45 or 46 of those 47 stand for.  I've even figured out
> > where the time stamps are stored so I can create a calendar entry
> > programmatically already. 
> 
> Post a description to the group.  Look in the source for packetdescription.txt
> which is the format it is described in.  The various p_*.p files are
> good examples to crib from.
> 
> Also please check to see if there is an explicit synchronization protocol
> for the calendar.  It is always better to use the official protocol 
> rather than just changing files behind the scenes.
> 

Unfortunately those files are way over my head, which is why I was
wondering if it would be useful for anyone who knew what they were doing.  
What I have is basically 47 numbers (b3, e9, af, etc) for each entry and
determined what each does/means.  Where do I even go to find out about
synchronization protocols?  (I'm fairly new to any type of mobile device
development, can you tell? :)  )

> > However, bitpim doesn't appear to have the
> > ability to overwrite files on my phone.  
> 
> What happens when you try?  If you get file locked exceptions then that
> is the phone not wanting those to be overwritten.
> 

I get a really long debug message, the same message that you get if you
try to do anything in bitpim other than view the filesystem (I.E. Get
Data).  I can paste it (and what I found out about the schedule file) if
anyone will use it.  Though if someone who actually has a clue is getting
one soon, I'm sure he'll hit the error rather quickly.


Thanks,
Ben

[Bitpim-devel] Sanyo 4920

[Ron S. (Cellebrite) <ro...@ce...>]

Hi,

Anyone tested this phone? Is it compatible to any of the other phones (like 5500 maybe)?

Thanks,
Ron

[Bitpim-devel] Re: [bitpim-cvs-checkins] bitpim/help phones-developer.htd,1.3,1.4

[Roger B. <ro...@ro...>]

Stephen A. Wood wrote:
> -<td>Sanyo
> -<td>SCP-4900
> -<td>

Does that mean you have got rid of your 4900?

Roger

[Bitpim-devel] Oh, Canada :-)

[Roger B. <ro...@ro...>]

RPI Wireless are looking to acquire a Canadian LG VX4600.  They wish
to develop a cable for it, and then send it to me so that it can be
fully supported by BitPim.  (Dale, this is your lucky day :-)

If you are in Canada and can get hold of one of these phones, please
let me know via email.  RPI will compensate you fully.

If there are other Canadian phones that are popular and you feel
are under-served by cables and BitPim let us know and we may be able 
to make similar arrangements.

Roger

Re: [Bitpim-devel] Samsung VGA-1000 schedule file

[Roger B. <ro...@ro...>]

Ben Curtis wrote:
> I've learned that each entry in the calendar has 47 hex numbers associated
> with it, and what 45 or 46 of those 47 stand for.  I've even figured out
> where the time stamps are stored so I can create a calendar entry
> programmatically already. 

Post a description to the group.  Look in the source for packetdescription.txt
which is the format it is described in.  The various p_*.p files are
good examples to crib from.

Also please check to see if there is an explicit synchronization protocol
for the calendar.  It is always better to use the official protocol 
rather than just changing files behind the scenes.

> However, bitpim doesn't appear to have the
> ability to overwrite files on my phone.  

What happens when you try?  If you get file locked exceptions then that
is the phone not wanting those to be overwritten.

I have some vague information on there being file attributes and the ability
to change them.  However I won't be looking at it for a while.

> Is anyone currently working on this functionality?

I believe there is a phone in the mail heading towards Stephen courtesy
of RPI Wireless.

> P.S. I sent an email like this one to the list before I was a member, so
> no need to pass that through if your an admin.  Thanks!

I reject all those emails.  (If I let them on, then the next one will need
to be explicitly allowed etc.  Far too much work!)

Roger

[Bitpim-devel] Samsung VGA-1000 schedule file

[Ben C. <bi...@no...>]

I'm sure this applies to many other Samsung phones, since they all appear
to be using the same basic calendar.  I've been examining the schedule
file in the nvm/nvm folder of my phone, and have created a specification
for the file.

I've learned that each entry in the calendar has 47 hex numbers associated
with it, and what 45 or 46 of those 47 stand for.  I've even figured out
where the time stamps are stored so I can create a calendar entry
programmatically already.  However, bitpim doesn't appear to have the
ability to overwrite files on my phone.  Is anyone currently working on
this functionality?


Thanks,
Ben

P.S. I sent an email like this one to the list before I was a member, so 
no need to pass that through if your an admin.  Thanks!

Re: [Bitpim-devel] Re: [bitpim-cvs-checkins] bitpimguiwidgets.py,1.182,1.183

[Roger B. <ro...@ro...>]

Stephen Wood wrote:
> I wonder if the BitFling client should be unavailable for binary
> builds.  Developers will generally be running from the CVS source.  But
> I guess I can think of uses for BitFling other than developing, such as
> friends or co-workers sharing phonebooks.

Yes, I was hoping that people would think of new ways of using BitFling.
It will certainly help when the code and UI are more complete.

> I figured something had to be done!  And it gave me an excuse to explore
> other parts of the code.

There is one part that is a blocker for 0.7 and needs to be completed.
It is the code that deals with "importing" phonebook entries.  The
import process happens when you do a CSV/Outlook import, but also
when a phonebook is read from a phone.  

Two pieces of code run.  The first tries to match imported entries up 
against existing ones, in order to decide if the imported entry is a 
new entry or a variation of an existing entry.  (Ideally it should
also detect existing entries that should be deleted).  I did write
the code for this stuff, but it hasn't been thoroughly tested.

The second piece of code merges two entries, and is incomplete.
It has to deal with things like data being mangled where it came
from (eg a phone with limited space for names, punctuation removed
from phone numbers).  This code really needs to be completed.

Here is what I sent someone else about it:

Look at phonebook.ImportDialog.MergeEntries()

It is trying to merge two entries.  One is what BitPim has
already stored, and the other is from an import source
such as Outlook, a CSV file or a phone.

It needs to go through each type of data and do the right
thing.  That means deciding if the imported data is an
update or augmentation and applying it if so.  Things
are made somewhat more complicated as the import source
may be "crippled" like most phones.  For example phones
limit the length of names to 16 or 22 characters, and
limit what characters are allowed in phone numbers
(eg no parentheses, dashes, spaces etc).  So, just because
an imported value is different than the existing value,
doesn't necessarily mean it is an updated value - it could
be a truncation or simplification of the existing value
and the existing value should be preserved.

You can see that I have already written the code to deal
with merging of phone numbers.  Note how it reduces the
imported and existing number to digits only before
comparing, and figures out when to replace the existing
value and when to add to the existing list.

That sort of thing has to be done for all the different
types of information and added to the loop in MergeEntries.
You can work on one data type at a time in small discrete
pieces so it doesn't interfere in your studies.  It is
also part art, part science and just good old fashioned
heuristics.

I would also welcome any test cases you write.  I would
expect there to be two csv files.  The first one is imported
overwriting everything, and then the second one has to be
merged into the first.


Roger

Re: [Bitpim-devel] Re: [bitpim-cvs-checkins] bitpim guiwidgets.py,1.182,1.183

[Stephen W. <sa...@ge...>]

I figured something had to be done!  And it gave me an excuse to explore
other parts of the code.

I wonder if the BitFling client should be unavailable for binary
builds.  Developers will generally be running from the CVS source.  But
I guess I can think of uses for BitFling other than developing, such as
friends or co-workers sharing phonebooks.

				Stephen

On Tue, 2004-05-18 at 21:24, Roger Binns wrote:
> Stephen A. Wood wrote:
> > Disable BitFling "Enable" checkbox until the Settings dialog as run.
> 
> I was going to do it a different way, but your way looks simpler :-)
> 
> Roger

[Bitpim-devel] Re: [bitpim-cvs-checkins] bitpim guiwidgets.py,1.182,1.183

[Roger B. <ro...@ro...>]

Stephen A. Wood wrote:
> Disable BitFling "Enable" checkbox until the Settings dialog as run.

I was going to do it a different way, but your way looks simpler :-)

Roger

Re: [Bitpim-devel] LG 4600 support

[Roger B. <ro...@ro...>]

Dale wrote:
> Roger that fix works, I was finally able to import the contact from the
> phone. Should I be able to send back to the phone or is there something that
> still needs to be done?

You won't be able to send back until more code is written.  I'll try to do
it over the next few days.

Roger

RE: [Bitpim-devel] LG 4600 support

[Dale <dri...@te...>]

Roger that fix works, I was finally able to import the contact from the
phone. Should I be able to send back to the phone or is there something that
still needs to be done?

Dale 

-----Original Message-----
From: bit...@li...
[mailto:bit...@li...] On Behalf Of Roger Binns
Sent: Monday, May 17, 2004 11:24 PM
To: bit...@li...
Subject: Re: [Bitpim-devel] LG 4600 support

Dale wrote:
> Hey Roger, here is the lastest error I am getting
> 
> AttributeError: 'pbentry' object has no attribute 'msgringtone'
> 
> Can I just comment this out from the code or is that a standard 
> attribute that the phone should have and I just need to update the length?

I have committed a fix.  It is because the generic LG code expects every
entry to have a msgringtone and your phone doesn't.

BTW who is your carrier?  I will change the UI in BitPim so it lists the
phone as being with that carrier as I believe the Verizon (or other carrier)
4600 will be different.

Roger


-------------------------------------------------------
This SF.Net email is sponsored by: SourceForge.net Broadband Sign-up now for
SourceForge Broadband and get the fastest
6.0/768 connection for only $19.95/mo for the first 3 months!
http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click
_______________________________________________
Bitpim-devel mailing list
Bit...@li...
https://lists.sourceforge.net/lists/listinfo/bitpim-devel

RE: [Bitpim-devel] LG 4600 support

[Dale <dri...@te...>]

The carrier is Telus Mobility. I will try the fix.

Dale 

-----Original Message-----
From: bit...@li...
[mailto:bit...@li...] On Behalf Of Roger Binns
Sent: Monday, May 17, 2004 11:24 PM
To: bit...@li...
Subject: Re: [Bitpim-devel] LG 4600 support

Dale wrote:
> Hey Roger, here is the lastest error I am getting
> 
> AttributeError: 'pbentry' object has no attribute 'msgringtone'
> 
> Can I just comment this out from the code or is that a standard 
> attribute that the phone should have and I just need to update the length?

I have committed a fix.  It is because the generic LG code expects every
entry to have a msgringtone and your phone doesn't.

BTW who is your carrier?  I will change the UI in BitPim so it lists the
phone as being with that carrier as I believe the Verizon (or other carrier)
4600 will be different.

Roger


-------------------------------------------------------
This SF.Net email is sponsored by: SourceForge.net Broadband Sign-up now for
SourceForge Broadband and get the fastest
6.0/768 connection for only $19.95/mo for the first 3 months!
http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click
_______________________________________________
Bitpim-devel mailing list
Bit...@li...
https://lists.sourceforge.net/lists/listinfo/bitpim-devel

Re: [Bitpim-devel] LG 4600 support

[Roger B. <ro...@ro...>]

Dale wrote:
> Hey Roger, here is the lastest error I am getting
> 
> AttributeError: 'pbentry' object has no attribute 'msgringtone'
> 
> Can I just comment this out from the code or is that a standard attribute
> that the phone should have and I just need to update the length?

I have committed a fix.  It is because the generic LG code expects every
entry to have a msgringtone and your phone doesn't.

BTW who is your carrier?  I will change the UI in BitPim so it
lists the phone as being with that carrier as I believe the
Verizon (or other carrier) 4600 will be different.

Roger

[Bitpim-devel] Doc updates

[Roger B. <ro...@ro...>]

The support page now also points to the group archives on Gmane as 
SourceForge has issues keeping theirs up to date.

I would appreciate reports for any of the doc that is out of date
or misleading.  The exception are the "reference pages" which
detail each tab and the dialog boxes.  They will be updated
closer to release.

Stephen,

Please ensure the doc is up to date for Sanyo stuff, in particular which
features are supported (it seemed that the versionhistory and the phone
pages contradicted each other :-).

I also added a phones-developer.htd listing what phones the developers
have (personally owned or loaned).  Please add yours and the ones from
RPI in there.

Roger