Re: [BitPim-user] 1.0.7.20090805-Test vs LG enV3: Send PhoneBook to Phone corrupts Contacts

[Lowell <sha...@am...>]

Before you did all this, did you use backup assistant to backup your
contacts?  I was having some issues with BA on a new phone where the contact
list did not download properly.  The tech told me to use Bluetooth and try
and send across a contact person that way.  It worked.  So we knew the phone
would accept a new contact.  He then told me to log into BA as a 'new-user'
and download the contact list that way.  Voila!  The phone now had all the
correct contacts.  I use bitpim also with my enV3 but just for ringtones and
music.   I export the contact list to a zip file just in case I need it at a
future date.  I also use BA (free from VZN for those who have online
accounts) exclusively.  Good luck.  

-----Original Message-----
From: Shal Farley [mailto:sh...@ve...] 
Sent: Tuesday, September 29, 2009 5:04 AM
To: bit...@li...
Subject: [BitPim-user] 1.0.7.20090805-Test vs LG enV3: Send PhoneBook to
Phone corrupts Contacts

Ok,

Having retrieved the contacts (PhoneBook) from the phone successfully, I
exported it to a .csv file. This contained only the handful of contacts I'd
entered manually so far. I then opened the .csv in Excel and manually merged
in the contacts I'd transcribed out of my old phone. 

I also trimmed off the four extra digits BitPim prepended to the phone
numbers. This fact now seems relevant.

I then imported this new, larger, .csv into BitPim, and synced it back to
the phone (this is, as it happens, exactly the operation for which I
obtained BitPim). The sync appears to have gone normally, including the
reboot of the phone at the end. See attached log file.

That's where the good news ends. Any attempt to examine any contact in my
phone causes the phone to reboot on the spot. Oops. I did find a clue by
trying to call my wife: the number presented on the "Calling..." screen
consisted of only the last six digits of her phone number. Oh...  Ten minus
four is six.

So it seems that those "extra" four digits are actually needed. Since I
removed them, the phone took the first four digits (area code plus one more)
of the phone number and used them for whatever purpose. And that probably
explains the reboot: indexed off the end of some table no doubt.

Ok, so I tediously put the extra four digits back into the spreadsheet. Then
imported it to BitPim, and synced with the phone once more.

Partial joy. Now the contact list entries have all 10 digits, and can be
used to dial and text message. But attempting to open the contact entry
(say, to edit it, or to select a particular phone number to dial) causes the
phone to reboot.

So, something is still corrupt. I read the contact list from the phone
again, and saved to another .csv file. That file is identical to the file I
loaded into BitPim. So whatever went wrong, it is invariant in what can be
seen through BitPim's import/export.

Any clues what I should try next? I can't leave the phone in this condition
for long, I'll have to find some way to clear out the corruption, even if it
means deleting the contacts and reentering them one by one through the
phone's keyboard.

-- Shal

1.0.7.20090805-Test
WinXP MCE 2002, Limited User
LGUSBModemDriver_WHQL_Eng_Ver_4.8.1
Verizon LG-VX9200 (enV3)
Straight USB A to microB cable