From: A F <eat...@ho...> - 2004-02-15 20:24:52
|
Hi Roger, I've gathered some of the information you requested for the LG 4600. 1) USB vendor/product id... I have no idea how to find this. I found the getphoneinfo function in com_lg.py and I added a call to it in com_lgvx4400.__init__. However, it seems to fetch standard strings (eg. Manufacturer="LG Electronics Ltd.", Model="LG-4600"). Are there other commands I can send to the phone to fetch the USB Vendor/Prod ID, or should I be looking somewhere in the file system for this info? 2) Names and locations of index files. So the main "index" for both ringers and wallpapers is a file called \$USER_DIRS. It's has a very simple record structure which is [length of record (including this field)][Directory name (which is 0 terminated)]. These point to directories in \usr\Ringtone and \usr\Wallpaper. Each subdirectory in those dirs contains 2 files: .desc(a fixed length file which contains mime type info and file size) and a file named body (no extension) which is the actual media file. The name of the subdirectory becomes the name of the Ringtone/Wallpaper as seen when using the phone. As I mentioned before, I've already added several tones and images to the phone, and this file did NOT have to be modified. I simply created a new subdir under \usr\Wallpaper (or Ringtone) and gave it an appropriate name. In that directory I dumped in the .desc file (modified to reflect the mime type and file size) and the body file. The $USER_DIRS files seems to update itself when you power cycle the phone. 3) Length of index record... see above 4 + 5) Neither the phone nor calendar seems to work. I have to do some more playing to check out where it is failing, but I suspect the phone is different than the vx4500 in how it handles the PIM info. A cursory look at the file system shows a \pim directory which contains pbentry.dat (which contains the entries, obviously. These appear to be fixed length records which include the name, and various offsets into the other files), pbnumber.dat, pbgroup, and record_id. I'll investigate further when I get the chance. Anthony ----- Original Message ----- From: "Roger Binns" <ro...@ro...> To: <bit...@li...> Sent: Thursday, February 12, 2004 12:14 AM Subject: Re: [Bitpim-devel] Debugging using the python GUIs > > I'm looking to add support for the LG 4600. > > Looking on phonescoop it seems that the phone is almost identical > to the 4400. If you are committing to support this phone, I will > add in the code necessary to get it going initially. Let me know > when you have some time (it will take a few iterations to get everything > going). > > The information needed is: > > - USB vendor/product id (almost certainly 0x1004/0x6000) > - Names and locations of index files for wallpapers and ringtones > (See line 45 in com_lgvx6000.py for that phone and line 42 in > com_lgvx4400.py) > - Figure out the length of an index record > - Verify the calendar works > - The phonebook should work as well > > > how can I start executing module bp.py and set a breakpoint in another > > file (for example, p_lg.py) and have it hit the > > breakpoint? > > That file in particular is dynamically loaded which may make it quite > hard. See the Debugging and Tweaking section on > http://bitpim.sourceforge.net/developer.html > > > I'd like to do this all in one of the GUIs (Idle or winPython) if > > possible (I get enough of command line debugging > > at work... I've had enough cdb and cordbg to last a lifetime!) > > Another debugger I have heard of is Hap at http://hapdebugger.sf.net/ > > However the command line pdb (especially as I point out in the debug > and tweak bit) works wonderfully. Its is very closely modelled on > the GNU Debugger (gdb) which is actually a very usable command line > debugger. > > Roger > > > ------------------------------------------------------- > SF.Net is sponsored by: Speed Start Your Linux Apps Now. > Build and deploy apps & Web services for Linux with > a free DVD software kit from IBM. Click Now! > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click > _______________________________________________ > Bitpim-devel mailing list > Bit...@li... > https://lists.sourceforge.net/lists/listinfo/bitpim-devel > |