[BitPim-devel] 0.7.35 Feedback

[John O'Shaughnessy]

I downloaded the recent build and tested with Mac OS X 10.4.2 on my
PowerMac G4 against my LG VX6100.

- The new Call History feature works fine
- The new SMS feature brings down the data, but it is sorted and
displayed oddly. I have 13 messages in my Inbox, and they aren't
displayed in the order they were received. How should they be
displayed? Also, the From: field shows '6245' for all the messages.
That seems odd.


Rebooting the phone didn't fix things, nor did restarting BitPim. I
resorted to removing my ,bitpim-files directory, and my Preferences
file, and then it worked again, until I next tried to detect the phone.


- In the Phonebook, if you select an entry, and edit that entry's
wallpaper, the list of image names correctly matches the images from
the phone. If you change a wallpaper, and then replace the phonebook
on the phone, that wallpaper entry is not updated. This is the same
behavior I experienced before that I was unable to fix. Also, and
perhaps there needs to be some logic change here, but you can select
the names of the built-in images as wallpaper, but since they aren't
loaded to BitPim from the phone, you get a picture of a yellow crown
on a green background if you select any of these wallpaper as
background images.

- What is the expected results of Edit -->Detect phone? It seems to
work, and I can name the phone, but if I run through the process,
nothing else will function. I get the following error:
" LG-VX6100 on /dev/cu.usbmodem18131: The phone is not responding
while transitioning mode from none to brew."

Details from the log are below:



23:01:33.832 coms:[{'available': True, 'class': 'modem', 'name': '/
dev/cu.modem', 'description': 'Modem (/dev/cu.modem)'}, {'available':
True, 'class': 'modem', 'name': '/dev/cu.usbmodem18131',
'description': 'Modem (/dev/cu.usbmodem18131)'}]
23:01:33.832 Available ports: ['/dev/cu.modem', '/dev/cu.usbmodem18131']
23:01:33.833 Available modem ports: ['/dev/cu.modem', '/dev/
cu.usbmodem18131']
23:01:37.817 Gathering data on port: /dev/cu.modem
23:01:37.818 /dev/cu.modem: Opening port /dev/cu.modem, 115200 baud,
timeout 1.000000, hardwareflow 0, softwareflow 0
23:01:37.818 Gathering data on port: /dev/cu.usbmodem18131
23:01:37.819 /dev/cu.usbmodem18131: Opening port /dev/
cu.usbmodem18131, 115200 baud, timeout 1.000000, hardwareflow 0,
softwareflow 0
23:01:37.820 /dev/cu.modem: Open of comm port suceeded
23:01:37.821 /dev/cu.usbmodem18131: Open of comm port suceeded
23:01:37.828 Done on port: /dev/cu.usbmodem18131
23:01:37.828 Done on port: /dev/cu.modem
23:01:37.830 Checking for model: LG-TM520
23:01:37.855 Checking for model: LG-VX10
23:01:37.855 Checking for model: LG-VX3200
23:01:37.883 Likely ports:[]
23:01:37.883 Checking for model: LG-VX4400
23:01:37.884 Likely ports:[]
23:01:37.888 Checking for model: LG-VX4500
23:01:37.888 Likely ports:[]
23:01:37.889 Checking for model: LG-VX4600 (Telus Mobility)
23:01:37.896 Likely ports:[]
23:01:37.898 Checking for model: LG-VX4650 (Verizon Wireless)
23:01:37.932 Likely ports:[]
23:01:37.933 Checking for model: LG-VX6000
23:01:37.943 Likely ports:[]
23:01:37.944 Checking for model: LG-VX6100
23:01:37.944 Likely ports:[]
23:01:56.277 /dev/cu.usbmodem18131: Opening port /dev/
cu.usbmodem18131, 115200 baud, timeout 3.000000, hardwareflow 0,
softwareflow 0
23:01:56.278 /dev/cu.usbmodem18131: Open of comm port suceeded
23:01:56.278 LG-VX6100: Attempting to contact phone
23:01:56.278 LG-VX6100: Retrieving fundamental phone information
23:01:56.278 LG-VX6100: Phone serial number
23:01:56.279 LG-VX6100: Getting file contents 'nvm/$SYS.ESN'
23:01:59.049 /dev/cu.usbmodem18131: Timed out waiting for 7e,
requested bytes 1 - 0 bytes read
23:01:59.051 /dev/cu.usbmodem18131: Changed port speed to 38400
23:02:02.553 /dev/cu.usbmodem18131: Timed out waiting for 7e,
requested bytes 1 - 0 bytes read
23:02:02.561 /dev/cu.usbmodem18131: Changed port speed to 115200
23:02:06.057 /dev/cu.usbmodem18131: Timed out waiting for 7e,
requested bytes 1 - 0 bytes read
23:02:06.073 Error: Device needs attention - LG-VX6100 on /dev/
cu.usbmodem18131
LG-VX6100 on /dev/cu.usbmodem18131: The phone is not responding while
transitioning mode from none to brew.

See the help for troubleshooting tips

[Simon C]

- The new SMS feature brings down the data, but it is sorted and displayed
oddly. I have 13 messages in my Inbox, and they aren't displayed in the
order they were received. How should they be displayed? Also, the From:
field shows '6245' for all the messages. That seems odd.

Rebooting the phone didn't fix things, nor did restarting BitPim. I
resorted to removing my ,bitpim-files directory, and my Preferences file,
and then it worked again, until I next tried to detect the phone.

So are you saying that removing the bitpim-files corrected the from field
problem? Was the from field displayed for outbox messages?
I agree the order of the messages is odd, on windows they are not sorted at
all either, sorting by date would make sense as an improvement to SMS.

- In the Phonebook, if you select an entry, and edit that entry's wallpaper,
the list of image names correctly matches the images from the phone.

Is this better than before?

If you change a wallpaper, and then replace the phonebook on the phone, that
wallpaper entry is not updated. This is the same behavior I experienced
before that I was unable to fix.

I noticed this during testing and Joe commented that this was a problem with
the 4650 as well, it appears to be a firmware issue not a bitpim problem.


Also, and perhaps there needs to be some logic change here, but you can
select the names of the built-in images as wallpaper, but since they aren't
loaded to BitPim from the phone, you get a picture of a yellow crown on a
green background if you select any of these wallpaper as background images.
Maybe an "unable to display image" image?

[John O'Shaughnessy]

Post by John O'Shaughnessy
- The new SMS feature brings down the data, but it is sorted and
displayed oddly. I have 13 messages in my Inbox, and they aren't
displayed in the order they were received. How should they be
displayed? Also, the From: field shows '6245' for all the
messages. That seems odd.
Rebooting the phone didn't fix things, nor did restarting BitPim.
I resorted to removing my ,bitpim-files directory, and my
Preferences file, and then it worked again, until I next tried to
detect the phone.

Sorry - cut and paste problem when creating this feedback. The
rebooting and clean up comments above were related to using the
Detect Phone option.

Post by John O'Shaughnessy
So are you saying that removing the bitpim-files corrected the from
field problem? Was the from field displayed for outbox messages?
I agree the order of the messages is odd, on windows they are not
sorted at all either, sorting by date would make sense as an
improvement to SMS.

I didn't have any saved or outbox messages. I'll create some and try
again.

Post by John O'Shaughnessy
- In the Phonebook, if you select an entry, and edit that entry's
wallpaper, the list of image names correctly matches the images
from the phone.
Is this better than before?

I'll load up an old version and compare. I forget if this behavior
was the same or not.

Post by John O'Shaughnessy
If you change a wallpaper, and then replace the phonebook on the
phone, that wallpaper entry is not updated. This is the same
behavior I experienced before that I was unable to fix.
I noticed this during testing and Joe commented that this was a
problem with the 4650 as well, it appears to be a firmware issue
not a bitpim problem.

Interesting!

Post by John O'Shaughnessy
Also, and perhaps there needs to be some logic change here, but
you can select the names of the built-in images as wallpaper, but
since they aren't loaded to BitPim from the phone, you get a
picture of a yellow crown on a green background if you select any
of these wallpaper as background images.
Maybe an "unable to display image" image?

I think that a message like that would be less confusing for the user
than the current crown image.

Thanks,

John

[Joe Pham]

Post by John O'Shaughnessy
The new SMS feature brings down the data, but it is sorted and
displayed oddly.

The messages are being sorted in the order they're retrieved from the phone, perhaps they should be sorted based on the order they're received by the phone.

Post by John O'Shaughnessy
Also, the From: field shows '6245' for all the messages.

That seems to indicate messages being sent from a Verizon server, such as vtext or vzwpix.

Post by John O'Shaughnessy
Rebooting the phone didn't fix things, nor did restarting BitPim.

What broke?

Post by John O'Shaughnessy
but since they aren't loaded to BitPim from the phone, you get a
picture of a yellow crown on a green background

That's the default pix for those images that either have no pix or pix that BitPim does not understand. I'm open to any suggestions for improvment.

Post by John O'Shaughnessy
What is the expected results of Edit -->Detect phone?

It's supposed to detect, and set the correct phone model & com port for your phone.

Thanks for the feedback.

-Joe Pham



______________________________________________________________________
NetZero Is Giving Away $3,000 A Day!
Sign up for NetZero HiSpeed 3G with Instant On!
Visit http://www.netzero.com/3Gsweeps TODAY for your chance to win!

[Simon C]

On Aug 30, 2005, at 11:47 PM, Simon C wrote:


- The new SMS feature brings down the data, but it is sorted and
displayed oddly. I have 13 messages in my Inbox, and they aren't displayed
in the order they were received. How should they be displayed? Also, the
From: field shows '6245' for all the messages. That seems odd.

Rebooting the phone didn't fix things, nor did restarting BitPim. I
resorted to removing my ,bitpim-files directory, and my Preferences file,
and then it worked again, until I next tried to detect the phone.


Sorry - cut and paste problem when creating this feedback. The rebooting
and clean up comments above were related to using the Detect Phone option.
John,

How about changing the phone setting manually after the autodetect has
messed it up, go back to entering the model and port number by hand. You
might want to change it to something else and then back to the correct
value. I'm trying to figure out if the reason deleting the bitpim files
fixes the porblem is because it "cleans-up" some bad settings.