From: Ben C. <bi...@no...> - 2004-05-21 13:20:23
|
> > 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 |