From: Roger B. <ro...@ro...> - 2004-05-01 08:09:17
|
I have committed code that works for me when testing on the VX6000 (the phone just ignores it - I am using the directory structure). When reading from the phone, BitPim automatically adds an extension to the directory name to name the resulting file. When writing back again, the extension is stripped to come up with the directory name and the mime-type deduced from the extension. This basically means you can just use ordinary files with BitPim and the right thing happens. You need to do the following: - Test and verify things work for you. I tested adding, replacing and reading - Get a full complete listing of what the phone expects for mime-types. Some of these are not standard. This is what I use so far: __mimetoextensionmapping={ 'image/jpg': '.jpg', 'image/bmp': '.bmp', 'image/png': '.png', 'image/gif': '.gif', 'image/bci': '.bci', 'audio/mp3': '.mp3', 'audio/mid': '.mid', 'audio/qcp': '.qcp' } - Is there a maximum number of wallpapers or ringtones that can be made? [The code currently sets a limit of 30 which is the same as other LG phones, but they have a fixed sized index file] - In conjunction with the next bit, work out what number is added to a wallpaper or ringtone index to store it in the phonebook. For example, the builtin image 'Butterfly' will be stored as zero. If you have added a wallpaper with index value of 3, what is it stored as in the phonebook. On other LG phones, they add 50, so it would be stored as 53. - Start working on the phonebook. Add an entry where you fill out each field to the maximum possible length. Read the phonebook with protocol logging turned on. Find that entry in the protocol log, highlight the whole packet and press Ctrl-Alt-P. Check the decoding of the fields. The description is in pbentry in p_lgvx4600.p. That is what will need to be changed to get things right. When you get to this stage tell me and I will give more detailed instructions. Roger |