phone detect change

"Simon C" <[email protected]>
Newsgroups gmane.comp.mobile.bitpim.devel
Message-ID <001801c5d457$a7d0cf10$6400a8c0@HOME>
The lg vx5200 responds on the modem port with all of it's data including
esn, model and manufacturer. See EOM for trace.

This causes the phone detect code to think it is on the modem port instead
of the serial port.

 

The dict (phone_detect.__data) after calling the phonedetect() on the vx5200
looks like:

{'COM3': {'mode_modem': True, 'mode_brew': False, 'firmwareresponse': None,
'esn': '1XXXXXXX, 'model': 'VX5200 111', 'firmware_version': 'S/W VER:
DS3.1.90     T5EVZV03 ', 'manufacturer': 'LG Electronics Inc.'}, 'COM4':
{'mode_modem': None, 'esn_file': '\xff\ <SNIP> \x00', 'mode_brew': True,
'firmwareresponse': None, 'esn': '1XXXXXXX', 'model': 'VX5200',
'brew_version.txt': 'VX5200, VRZ, 24, 2.1.3.11, 13, 771418, 14, 771458,
20050526', 'firmware_version': None, 'manufacturer': 'LG Electronics Inc'}}

 

The __check_profile function returns COM3, but this incorrect, it should be
COM4. comdiagnose.islikelyport returns COM4 in this instance. I'd like to
change the __check_profile function to take the likelyports list and only
return ports that are in this list. I'd also like to add a little more
logging for the phone detect.

 

I'll check this in tomorrow if it is OK with everyone.

 

Simon

 

 

 

 

 

 

 

 

Modem port trace from vx5200

 

17:31:47.694 Available ports: ['COM1', 'COM2', 'COM3', 'COM4']

17:31:47.703 Available modem ports: ['COM3']

17:31:47.874 Gathering data on port: COM3

17:31:47.884 COM3: Opening port COM3, 115200 baud, timeout 1.000000,
hardwareflow 0, softwareflow 0

17:31:47.884 COM3: Open of comm port suceeded

17:31:47.884 COM3: Writing Data - 8 bytes

00000000 41 54 45 30 56 31 0d 0a                             ATE0V1..

 

17:31:47.884 COM3: Reading remaining data Data - 4 bytes

00000000 4f 4b 0d 0a                                         OK..

 

17:31:47.884 COM3: Writing Data - 8 bytes

00000000 41 54 2b 47 4d 49 0d 0a                             AT+GMI..

 

17:31:47.884 COM3: Reading remaining data Data - 33 bytes

00000000 2b 47 4d 49 3a 20 4c 47 20 45 6c 65 63 74 72 6f     +GMI: LG
Electro

00000010 6e 69 63 73 20 49 6e 63 2e 0d 0a 0d 0a 4f 4b 0d     nics
Inc.....OK.

00000020 0a                                                  .

 

17:31:47.884 COM3: Writing Data - 8 bytes

00000000 41 54 2b 47 4d 4d 0d 0a                             AT+GMM..

 

17:31:47.894 COM3: Reading remaining data Data - 24 bytes

00000000 2b 47 4d 4d 3a 20 56 58 35 32 30 30 20 31 31 31     +GMM: VX5200
111

00000010 0d 0a 0d 0a 4f 4b 0d 0a                             ....OK..

 

17:31:47.894 COM3: Writing Data - 8 bytes

00000000 41 54 2b 47 4d 52 0d 0a                             AT+GMR..

 

17:31:47.894 COM3: Reading remaining data Data - 45 bytes

00000000 2b 47 4d 52 3a 20 53 2f 57 20 56 45 52 3a 20 44     +GMR: S/W VER:
D

00000010 53 33 2e 31 2e 39 30 20 20 20 20 20 54 35 45 56     S3.1.90
T5EV

00000020 5a 56 30 33 20 0d 0a 0d 0a 4f 4b 0d 0a              ZV03 ....OK..

 

17:31:47.914 COM3: Writing Data - 8 bytes

00000000 41 54 2b 47 53 4e 0d 0a                             AT+GSN..

 

17:31:47.914 COM3: Reading remaining data Data - 22 bytes

00000000 2b 47 53 4e 3a 20 31 44 43 44 35 31 46 34 0d 0a     +GSN: 1XXXXXX..
(deliberately changed)

00000010 0d 0a 4f 4b 0d 0a                                   ..OK..
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.