Re: LG-VX3200 comments

Great comments - here are just some quick replies - I will chew on the
others for awhile.

1. Below where I said "The LG files are 128x128 16BPP-R5G6B5 format." what
I meant to say is "The LG files are 128x128 BIT 16BPP-R5G6B5 format.". I
think you interpreted what I said is that the wallpaper on the LG-VX3200
is some sort of BMP file. The format actually is:

  2 bytes - width
  2 bytes - height
  width x height 16bit R5G6R5 image data

Lean and mean. The final image file, e.g. wallpaper.bit, is therefore
128*128*2 + 4 bytes or 32772 bytes for a 128x128 image. As an aside the
image in a BIT file is also flipped about the x-axis compared to a BMP
file.

I will attempt to make the LGBIT related defs in fileinfo.py and
conversions.py more general purpose.

2. Auto-detect is not working. The problem appears to be related to
exactly what you describe below, i.e. the port I am using (COM3) has
class='serial' and not 'modem' therefore is it not used in the phone
detection process.

This is from my log:

12:49:15.920 coms:
[{'available': True,
   'driverdate': (2001, 7, 1),
   'description': 'Communications Port (COM1)',
   'driverprovider': 'Microsoft',
   'driverversion': '5.1.2600.0',
   'hardwareinstance': 'ROOT\\*PNP0501\\PNPBIOS_12',
   'driverdescription': 'Communications Port',
   'active': True,
   'class': 'serial',
   'name': 'COM1'},
 {'available': False,
   'driverdate': (1999, 11, 14),
   'description': 'Communications Port (COM2)',
   'driverprovider': 'Microsoft',
   'driverversion': '5.0.2183.1',
   'hardwareinstance': 'ROOT\\*PNP0501\\PNPBIOS_16',
   'driverdescription': 'Communications Port',
   'active': False,
   'class': 'serial',
   'name': 'COM2'},
 {'available': True,
   'driverdate': (2002, 4, 9),
   'description': 'Prolific USB-to-Serial Comm Port (COM3)',
   'driverprovider': 'Prolific',
   'driverversion': '1.5.0.0',
   'hardwareinstance': 'USB\\VID_067B&PID_2303\\4&1217B47&0&1',
   'driverdescription': 'Prolific USB-to-Serial Comm Port',
   'active': True,
   'class': 'serial',
   'name': 'COM3'}]
12:49:15.936 Available ports: ['COM1', 'COM3']
12:49:15.950 Available modem ports: []


>> Unfortunately LG did a real hack job here. They have an images related
>> index file in the phone but it is completely unused.
>
> They seem to drag code from phone to phone, each of which is worked on
> by different developers who for some reason are never allowed to talk to
> each other.
>
>> Finally, the
>> wallpaper image format is proprietary to LG which requires further
>> finessing in BitPim.
>
>
> I believe that format is also used on the other phones as well.
> When you select an image as your wallpaper then the .bit file
> is created from the selected file contents.
>
>> I have added support in conversions.py for converting between this LG
>> proprietary format and BMP files. (Side note - I only support 128x128
>> 24BPP BMP files. The LG files are 128x128 16BPP-R5G6B5 format.)
>
> That BMP format is probably what the vx4500 uses then.  We have
> been trying quite hard to figure it out.  It would be really useful if
> you could write code that takes any sized 24 bit BMP and converts to the
> same sized 16 bit BMP.
>
>> it. I have enabled reading in BitPim but currently writing is not
>> suppported. This will be my next major step in development.
>
> On all the other LG phones you can take a filesystem backup of the pim
> directory, and then go ahead and do your development.  When
> you want things back to how they were, restore the pim directory
> and reboot the phone.
>
>> I have not spent one second looking at this. I hope to get to it soon
>> and I hope that it will just work!  ;-)
>
> The VX4400 calendar code and hence all the models that inherit from it
> do not work correctly at the moment.
>
>> I have put the necessary info in com_lgvx3200.py in support of
>> autodetect.
>
> From the help you say only USB to serial can be used.  In that case the
> auto-detect is fine.  It is the phones with direct USB and
> the composite interface that need some work first.
>
>> I have provided the necessary BitPim Help files to support the
>> capabilities I am providing. The new help files will obvisouly need
>> valid Index numbers inserted.
>
> The index numbers are actually generated by a script as the
> phonesupporttable.
>
>> Let me know what I am missing for this Rev 0 release.
>
> Nothing!  Very complete and well done.
>
> Roger
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by Yahoo.
> Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
> Search APIs Find out how you can build Yahoo! directly into your own
> Applications - visit
> http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005
> _______________________________________________
> BitPim-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/bitpim-devel


-- 
Bruce Schurmann
BitPim LG-VX3200 dev




-------------------------------------------------------
This SF.Net email is sponsored by Yahoo.
Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
Search APIs Find out how you can build Yahoo! directly into your own
Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005