Re: Voyager/Venus calendar patch
Nathan Hjelm <[email protected]>
| Newsgroups | gmane.comp.mobile.bitpim.devel |
|---|---|
| Message-ID | <[email protected]> |
On Thursday, November 29, 2007, at 08:40PM, "Joe Pham" <[email protected]> wrote: >>- Write correct firmware version/ESN in the serial number field of >>calendar entries. > >Did you determine the essential values of this field (ie, can some of them be 0x00 or 0xff or don't care. Also, I noticed the VX8550 has '0x000000ca-..' while the VX8800 has '0x000000cc-..', not sure if it makes any differences or not. The values in the serial number don't seem to make a difference. The only reason to set the serial number is to be consistent with the phone's software. >You may also need to deconflict between the 'ringpath' and 'serial_number' field. I didn't realize there was a ringtone path. If it isn't fixed once the new calendar patch is ready I will fix that as well. >>- Write correct firmware version/ESN in the serial number field of >>calendar entries. > >It appears that the VX8800 needs to have the full 300 entries. Can the empty entries have any values (don't care garbage), or need they have all 0xff? In any case, I'd suggest creating the empty entries/buffers in the protocol file instead. I don't think it matters what values schedule.dat is padded with as long as the file is exactly 41402 (works with both all 0's and with all 255's) bytes long (any shorter and the calendar doesn't show up correctly on the phone). I am not sure how to best pad the file using the protocol file. Is there a class for handling padding or should I write one? -Nathan ------------------------------------------------------------------------- SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4