Re: A few questions...

> The amount of functionality doesn't matter.  What is there should be 
> reasonably safe
> in that it doesn't destroy user's data.  (ie it is better to get one thing 
> working well rather than lots of things working badly)
>

Ok, I'm almost to that point.  The last thing I was missing in the phone 
book protocol was the speed dial, and I just got that worked out.  Now I 
just need to do some more defensive testing.

> Then post your changes to this group.  Make sure to include text for the 
> versionhistory
> file which sets expectations appropriately.

From what I've seen in the past you want me to post the two files 
(com_lgpm325.py and p_lgpm325.p) with copyright info included, help files 
(such as lgpm325notes.hpd and lgpm325cables.hpd since cables were a major 
pain for me), and the CVS diff for the guiwidgets class.  Missing anything?

> The "brew protocol" does files in the embedded filesystem only.  The LG 
> phonebook
> protocol is at a higher level and operates on phonebook records.

Oops. Forgot that the mode transitioned to phonebook mode and was out of 
brew mode.  Let me read some more and see if I can find out more about how 
to do protocol analysis at a lower level than I've been doing so far.

> I always avoid modifying the files directly instead of using the sync 
> protocol.
> That means that you don't get caught out by other data dependencies - for 
> example
> the call history may link into the phonebook and if you directly update 
> the
> phonebook file, you could make the phone crash due to broken linkage.
> One possibility is to update everything you can using the phonebook 
> protocol and
> then patching the file to update the wallpaper info.  That is far less 
> risky.


Yeah, that's kind of what I was thinking.  In this case it appears I have to 
hack at the main contact file which has 90% of the information.  Kind of "in 
for a penny, in for a pound" kind of problem - the contact format could 
easily be changed by a firmware update to add one byte here or there, so any 
updating I do could be deadly to a new firmware.  However, by using the 
phone book protocol for 90% of the data I could at least allow the user to 
disable the "extra" capabilities and still keep basic phone book management. 
I'll keep looking for extended protocol values.  There are a couple of other 
links I'm missing - the voicedial setting is lost when I replace a phone 
book entry in addition to the wall paper setting.

Thanks for your comments.

- Ed 



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click