bitpim-devel Mailing List for BitPim (Page 14)

Brought to you by: djpham, sawecw, sburke1

bitpim-devel — For bitpim developers

You can subscribe to this list here.

2003	Jan	Feb	Mar (53)	Apr (48)	May (14)	Jun (3)	Jul (21)	Aug (11)	Sep (77)	Oct (67)	Nov (28)	Dec (163)
2004	Jan (112)	Feb (143)	Mar (114)	Apr (138)	May (173)	Jun (119)	Jul (119)	Aug (117)	Sep (187)	Oct (170)	Nov (254)	Dec (193)
2005	Jan (336)	Feb (284)	Mar (189)	Apr (100)	May (89)	Jun (52)	Jul (85)	Aug (138)	Sep (181)	Oct (137)	Nov (104)	Dec (98)
2006	Jan (76)	Feb (106)	Mar (224)	Apr (270)	May (103)	Jun (144)	Jul (77)	Aug (38)	Sep (37)	Oct (20)	Nov (14)	Dec (73)
2007	Jan (130)	Feb (68)	Mar (78)	Apr (60)	May (45)	Jun (63)	Jul (84)	Aug (45)	Sep (40)	Oct (12)	Nov (71)	Dec (56)
2008	Jan (44)	Feb (20)	Mar (25)	Apr (17)	May (33)	Jun (60)	Jul (97)	Aug (38)	Sep (10)	Oct (20)	Nov (13)	Dec (19)
2009	Jan (7)	Feb (5)	Mar (23)	Apr (10)	May (6)	Jun (5)	Jul (17)	Aug (7)	Sep (14)	Oct (27)	Nov (13)	Dec (12)
2010	Jan (37)	Feb (9)	Mar (13)	Apr (12)	May (8)	Jun (3)	Jul (1)	Aug (9)	Sep (3)	Oct (1)	Nov (1)	Dec (4)
2011	Jan (1)	Feb	Mar (1)	Apr (4)	May	Jun (2)	Jul (8)	Aug	Sep	Oct	Nov	Dec
2012	Jan (2)	Feb	Mar	Apr	May (5)	Jun	Jul	Aug	Sep (5)	Oct	Nov (3)	Dec
2015	Jan	Feb	Mar	Apr	May	Jun	Jul	Aug	Sep	Oct	Nov (2)	Dec
2017	Jan	Feb	Mar	Apr	May	Jun	Jul	Aug	Sep (1)	Oct	Nov	Dec
2021	Jan	Feb	Mar	Apr	May	Jun	Jul	Aug (2)	Sep (2)	Oct	Nov	Dec

Flat | Threaded

<< < 1 .. 12 13 14 15 16 .. 265 > >> (Page 14 of 265)

Re: [BitPim-devel] LG LX260 (Sprint Rumor) database format.

From: Stephen W. <bi...@gm...> - 2008-07-31 02:27:52

The format of the contentInfo file might be similar to what is used on
the LG PM225 or PM325, both Sprint phones.  You might look at the code
and protocol definitions for these phones.

How do you connect your phone?  With a data cable?  Bluetooth?  What
drivers do you use?  I ask because while there are 3 Rumors in my
house, I can't borrow them very often, so don't want to waste time
trying to figure out how to connect.

Stephen

On Wed, Jul 30, 2008 at 5:39 PM, Jack Miller <ja...@co...> wrote:
> Hi all.
>
> This isn't strictly Bitpim related (yet), but I'm attempting to reverse
> engineer the format of the Sprint Rumor's contentInfo/executionInfo
> databases. It's going very well for the most part and I have 90% of the file
> figured out, but one thing I can't figure out is their string storage
> techniques.
>...

[BitPim-devel] LG LX260 (Sprint Rumor) database format.

From: Jack M. <ja...@co...> - 2008-07-30 21:39:50

Hi all.

This isn't strictly Bitpim related (yet), but I'm attempting to reverse
engineer the format of the Sprint Rumor's contentInfo/executionInfo
databases. It's going very well for the most part and I have 90% of the file
figured out, but one thing I can't figure out is their string storage
techniques.

Perhaps someone in bitpim development will recognize the format, or have some
insight?

First there's a type code
0x00 0x04

Then a field num (incremented for each variable in the record)
0x36

The a field length
0x10

A marker of some sort
0x00 0xFF 0x00

The string, in ASCII (null terminated)
Applications

After the null terminator, though there's what is apparently garbage. The
string length includes the marker, terminator and the garbage, so it can be
used to jump over accurately. Sometimes it's got some random bytes in it.
Sometimes it's all zeroes. Sometimes there is no garbage.

It's not a hash of any sort, because it's changes between two identical
strings ("Applications" appears alot), and even the number of bytes of
garbage changes between identical strings.

It also can't be some sort of padding, as far as I can tell, it adds all
sorts of number of bytes, and the strings don't start or end on any special
address.

Also, the string 0x98 0xFE 0xCD 0xAB shows up a lot in the garbage as well, 
but not always and not always at the beginning or the end when it does.

Anyone seen anything like this before? I've been manipulating the files with
a Python script, and two files one before I added a ringer via the internet
and one after and the *only* difference between the file I generate and the
reference file is the lengths of the strings/record/file and the lack of
garbage. Yet the reference file works and mine doesn't, so their must be
something to it...

Thanks for your help.

--Jack

[BitPim-devel] fails to connect except when manually set phone after restart of phone

From: R S P. <RSP...@in...> - 2008-07-30 19:00:36

I thought I'd pass along this annoying bug.

Bitpim (all recent versions) fails to connect to my VX-6100, ** unless I 
restart phone connected to running BitPIM via usb cable.  (I thought I 
recalled this working without restart on some older ver of BitPim?  < 1.0.2. 
or <1.0 ??)

a second issue:  detects only generic "Other CDMA phone" when 
restart phone and autoscan  -- lsusb data below may help

Thanks for your work on BitPim!

some info:
I use a generic USB cable 

phone:
k7:~ # lsusb
...
Bus 004 Device 003: ID 1004:6000 LG Electronics, Inc. VX4400/VX6000 Cellphone

logs :
-------------------------------------------------------
Start BitPim, connect phone, and auto scan:
   same result if connect phone first ...

14:15:36.744 USB Comm Watch started
14:15:59.702 coms:[{'available': True, 'description': 'USB modem 
(/dev/ttyACM0)', 'driver': 'ttyACM', 'device': (166, 
0), 'class': 'modem', 'name': '/dev/ttyACM0'}, {'available': 
False, 'usb-vendor': 'Hewlett-Packard', 'protocol': 'Printer / Printer / 
Bidirectional', 'name': 'usb::006::002::0', 'VID': '0x03F0', 'PID': '0xB602', 'usb-vendor#': 
1008, 'usb-serialnumber': 'CN3BO320H9N8', 'usb-interface#': 
0, 'usb-productstring': 'photosmart 7900 series', 'active': True, 'libusb': 
True, 'usb-product#': 46594, 'usb-vendorstring': 'hp', 'description': 'USB 
Device - Vendor Hewlett-Packard, Product #B602, (Interface #00)'}, 
{'available': True, 'usb-vendor': 'Hewlett-Packard', 'protocol': 'Vendor 
Specific Class / Vendor Specific Subclass / Vendor Specific 
Protocol', 'name': 'usb::006::002::1', 'VID': '0x03F0', 'PID': '0xB602', 'usb-vendor#': 
1008, 'usb-serialnumber': 'CN3BO320H9N8', 'usb-interface#': 
1, 'usb-productstring': 'photosmart 7900 series', 'active': True, 'libusb': 
True, 'usb-product#': 46594, 'usb-vendorstring': 'hp', 'description': 'USB 
Device - Vendor Hewlett-Packard, Product #B602, (Interface #01)'}, 
{'available': False, 'usb-vendor': 'Hewlett-Packard', 'protocol': 'Mass 
Storage / SCSI / Bulk 
(Zip)', 'name': 'usb::006::002::2', 'VID': '0x03F0', 'PID': '0xB602', 'usb-vendor#': 
1008, 'usb-serialnumber': 'CN3BO320H9N8', 'usb-interface#': 
2, 'usb-productstring': 'photosmart 7900 series', 'active': True, 'libusb': 
True, 'usb-product#': 46594, 'usb-vendorstring': 'hp', 'description': 'USB 
Device - Vendor Hewlett-Packard, Product #B602, (Interface #02)'}, 
{'available': False, 'driver-required': True, 'protocol': 'Data / 
Generic', 'name': 'usb::004::004::1', 'VID': '0x1004', 'usb-vendor': 'LG 
Electroncs', 'description': 'USB Device - Vendor LG Electroncs, Product VX 
Series Phone (Direct USB connection), (Interface Modem 
Interface)', 'PID': '0x6000', 'usb-vendor#': 4100, 'usb-interface#': 
1, 'usb-productstring': 'Qualcomm CDMA Technologies MSM', 'usb-product': 'VX 
Series Phone (Direct USB connection)', 'active': True, 'libusb': 
True, 'usb-product#': 24576, 'usb-interface': 'Modem Interface'}, 
{'available': True, 'usb-vendor': 'LG Electroncs', 'protocol': 'Vendor 
Specific Class / Vendor Specific 
Subclass', 'name': 'usb::004::004::2', 'VID': '0x1004', 'description': 'USB 
Device - Vendor LG Electroncs, Product VX Series Phone (Direct USB 
connection), (Interface Diagnostics 
Interface)', 'PID': '0x6000', 'usb-vendor#': 4100, 'usb-interface#': 
2, 'usb-productstring': 'Qualcomm CDMA Technologies MSM', 'usb-product': 'VX 
Series Phone (Direct USB connection)', 'active': True, 'libusb': 
True, 'usb-product#': 24576, 'usb-interface': 'Diagnostics Interface'}]
14:15:59.796 Available ports: 
['/dev/ttyACM0', 'usb::006::002::1', 'usb::004::004::2']
14:15:59.797 Available modem ports: ['/dev/ttyACM0']
14:15:59.929 Gathering data on port: /dev/ttyACM0
14:15:59.929 /dev/ttyACM0: Opening port /dev/ttyACM0, 115200 baud, timeout 
1.000000, hardwareflow 0, softwareflow 0
14:15:59.929 /dev/ttyACM0: Open of comm port suceeded
14:15:59.933 Done on port: /dev/ttyACM0
14:15:59.934 Checking for model: E815
14:16:00.151 Likely ports:[]
14:16:00.152 Detect Phone result: {'/dev/ttyACM0': {'mode_modem': 
True, 'mode_brew': False, 'firmwareresponse': 
None, 'esn': '1F866AEF', 'model': 'VX6100 108', 'firmware_version': 'S/W VER: 
DP3.3 PATCH  T61VZV02 ', 'manufacturer': 'LG Electronics Inc.'}}
14:16:00.152 Checking for model: E815m
14:16:00.152 Likely ports:[]
14:16:00.152 Detect Phone result: {'/dev/ttyACM0': {'mode_modem': 
True, 'mode_brew': False, 'firmwareresponse': 
None, 'esn': '1F866AEF', 'model': 'VX6100 108', 'firmware_version': 'S/W VER: 
DP3.3 PATCH  T61VZV02 ', 'manufacturer': 'LG Electronics Inc.'}}
14:16:00.152 Checking for model: K1m
14:16:00.153 Likely ports:[]
14:16:00.153 Detect Phone result: {'/dev/ttyACM0': {'mode_modem': 
True, 'mode_brew': False, 'firmwareresponse': 
None, 'esn': '1F866AEF', 'model': 'VX6100 108', 'firmware_version': 'S/W VER: 
DP3.3 PATCH  T61VZV02 ', 'manufacturer': 'LG Electronics Inc.'}}
14:16:00.153 Checking for model: LG-AX8600
14:16:00.153 Likely ports:['usb::004::004::2']
14:16:00.220 usb::004::004::2: Opening port usb::004::004::2, 115200 baud, 
timeout 1.000000, hardwareflow 0, softwareflow 0
14:16:00.221 usb::004::004::2: Open of comm port suceeded
14:16:00.221 LG-AX8600: Attempting to contact phone
14:16:02.240 usb::004::004::2: Timed out - flushing and trying again
14:16:04.291 usb::004::004::2: Timed out waiting for 7e, requested 
bytes -99999  - 0 bytes read
14:16:04.292 usb::004::004::2: Port speed 38400 not supported
14:16:04.292 usb::004::004::2: Port speed 115200 not supported
14:16:04.292 Detect Phone result: {'/dev/ttyACM0': {'mode_modem': 
True, 'mode_brew': False, 'firmwareresponse': 
None, 'esn': '1F866AEF', 'model': 'VX6100 108', 'firmware_version': 'S/W VER: 
DP3.3 PATCH  T61VZV02 ', 'manufacturer': 'LG Electronics 
Inc.'}, 'usb::004::004::2': {'mode_modem': None, 'mode_brew': 
False, 'firmwareresponse': None, 'esn': None, 'model': 
None, 'firmware_version': None, 'manufacturer': None}}
14:16:04.293 Checking for model: LG-C2000
14:16:04.375 Likely ports:[]
14:16:04.375 Detect Phone result: {'/dev/ttyACM0': {'mode_modem': 
True, 'mode_brew': False, 'firmwareresponse': 
None, 'esn': '1F866AEF', 'model': 'VX6100 108', 'firmware_version': 'S/W VER: 
DP3.3 PATCH  T61VZV02 ', 'manufacturer': 'LG Electronics 
Inc.'}, 'usb::004::004::2': {'mode_modem': None, 'mode_brew': 
False, 'firmwareresponse': None, 'esn': None, 'model': 
None, 'firmware_version': None, 'manufacturer': None}}
14:16:04.375 Checking for model: LG-G4015
14:16:04.375 Likely ports:[]
14:16:04.376 Detect Phone result: {'/dev/ttyACM0': {'mode_modem': 
True, 'mode_brew': False, 'firmwareresponse': 
None, 'esn': '1F866AEF', 'model': 'VX6100 108', 'firmware_version': 'S/W VER: 
DP3.3 PATCH  T61VZV02 ', 'manufacturer': 'LG Electronics 
Inc.'}, 'usb::004::004::2': {'mode_modem': None, 'mode_brew': 
False, 'firmwareresponse': None, 'esn': None, 'model': 
None, 'firmware_version': None, 'manufacturer': None}}
14:16:04.376 Checking for model: LG-LG6190
14:16:04.438 Likely ports:['usb::004::004::2']
14:16:04.438 Detect Phone result: {'/dev/ttyACM0': {'mode_modem': 
True, 'mode_brew': False, 'firmwareresponse': 
None, 'esn': '1F866AEF', 'model': 'VX6100 108', 'firmware_version': 'S/W VER: 
DP3.3 PATCH  T61VZV02 ', 'manufacturer': 'LG Electronics 
Inc.'}, 'usb::004::004::2': {'mode_modem': None, 'mode_brew': 
False, 'firmwareresponse': None, 'esn': None, 'model': 
None, 'firmware_version': None, 'manufacturer': None}}
14:16:04.438 Checking for model: LG-LG6200
14:16:04.504 Likely ports:['usb::004::004::2']
14:16:04.555 Detect Phone result: {'/dev/ttyACM0': {'mode_modem': 
True, 'mode_brew': False, 'firmwareresponse': 
None, 'esn': '1F866AEF', 'model': 'VX6100 108', 'firmware_version': 'S/W VER: 
DP3.3 PATCH  T61VZV02 ', 'manufacturer': 'LG Electronics 
Inc.'}, 'usb::004::004::2': {'mode_modem': None, 'mode_brew': 
False, 'firmwareresponse': None, 'esn': None, 'model': 
None, 'firmware_version': None, 'manufacturer': None}}
14:16:04.555 Checking for model: LG-LG8100
14:16:04.599 Likely ports:['usb::004::004::2']
14:16:04.599 Detect Phone result: {'/dev/ttyACM0': {'mode_modem': 
True, 'mode_brew': False, 'firmwareresponse': 
None, 'esn': '1F866AEF', 'model': 'VX6100 108', 'firmware_version': 'S/W VER: 
DP3.3 PATCH  T61VZV02 ', 'manufacturer': 'LG Electronics 
Inc.'}, 'usb::004::004::2': {'mode_modem': None, 'mode_brew': 
False, 'firmwareresponse': None, 'esn': None, 'model': 
None, 'firmware_version': None, 'manufacturer': None}}
14:16:04.599 Checking for model: LG-LX5450
14:16:04.647 Likely ports:['usb::004::004::2']
14:16:04.647 Detect Phone result: {'/dev/ttyACM0': {'mode_modem': 
True, 'mode_brew': False, 'firmwareresponse': 
None, 'esn': '1F866AEF', 'model': 'VX6100 108', 'firmware_version': 'S/W VER: 
DP3.3 PATCH  T61VZV02 ', 'manufacturer': 'LG Electronics 
Inc.'}, 'usb::004::004::2': {'mode_modem': None, 'mode_brew': 
False, 'firmwareresponse': None, 'esn': None, 'model': 
None, 'firmware_version': None, 'manufacturer': None}}
14:16:04.647 Checking for model: LG-LX5550
14:16:04.905 Likely ports:[]
14:16:04.905 Detect Phone result: {'/dev/ttyACM0': {'mode_modem': 
True, 'mode_brew': False, 'firmwareresponse': 
None, 'esn': '1F866AEF', 'model': 'VX6100 108', 'firmware_version': 'S/W VER: 
DP3.3 PATCH  T61VZV02 ', 'manufacturer': 'LG Electronics 
Inc.'}, 'usb::004::004::2': {'mode_modem': None, 'mode_brew': 
False, 'firmwareresponse': None, 'esn': None, 'model': 
None, 'firmware_version': None, 'manufacturer': None}}
14:16:04.905 Checking for model: LG-PM225
14:16:04.906 Likely ports:['usb::004::004::2']
14:16:04.906 Detect Phone result: {'/dev/ttyACM0': {'mode_modem': 
True, 'mode_brew': False, 'firmwareresponse': 
None, 'esn': '1F866AEF', 'model': 'VX6100 108', 'firmware_version': 'S/W VER: 
DP3.3 PATCH  T61VZV02 ', 'manufacturer': 'LG Electronics 
Inc.'}, 'usb::004::004::2': {'mode_modem': None, 'mode_brew': 
False, 'firmwareresponse': None, 'esn': None, 'model': 
None, 'firmware_version': None, 'manufacturer': None}}
14:16:04.906 Checking for model: LG-PM325
14:16:04.906 Likely ports:['usb::004::004::2']
14:16:04.907 Detect Phone result: {'/dev/ttyACM0': {'mode_modem': 
True, 'mode_brew': False, 'firmwareresponse': 
None, 'esn': '1F866AEF', 'model': 'VX6100 108', 'firmware_version': 'S/W VER: 
DP3.3 PATCH  T61VZV02 ', 'manufacturer': 'LG Electronics 
Inc.'}, 'usb::004::004::2': {'mode_modem': None, 'mode_brew': 
False, 'firmwareresponse': None, 'esn': None, 'model': 
None, 'firmware_version': None, 'manufacturer': None}}
14:16:04.907 Checking for model: LG-TM520
14:16:04.907 Checking for model: LG-UX5000
14:16:04.907 Likely ports:['usb::004::004::2']
14:16:04.907 Detect Phone result: {'/dev/ttyACM0': {'mode_modem': 
True, 'mode_brew': False, 'firmwareresponse': 
None, 'esn': '1F866AEF', 'model': 'VX6100 108', 'firmware_version': 'S/W VER: 
DP3.3 PATCH  T61VZV02 ', 'manufacturer': 'LG Electronics 
Inc.'}, 'usb::004::004::2': {'mode_modem': None, 'mode_brew': 
False, 'firmwareresponse': None, 'esn': None, 'model': 
None, 'firmware_version': None, 'manufacturer': None}}
14:16:04.907 Checking for model: LG-VI125
14:16:05.289 Likely ports:['usb::004::004::2']
14:16:05.289 Detect Phone result: {'/dev/ttyACM0': {'mode_modem': 
True, 'mode_brew': False, 'firmwareresponse': 
None, 'esn': '1F866AEF', 'model': 'VX6100 108', 'firmware_version': 'S/W VER: 
DP3.3 PATCH  T61VZV02 ', 'manufacturer': 'LG Electronics 
Inc.'}, 'usb::004::004::2': {'mode_modem': None, 'mode_brew': 
False, 'firmwareresponse': None, 'esn': None, 'model': 
None, 'firmware_version': None, 'manufacturer': None}}
14:16:05.289 Checking for model: LG-VI5225
14:16:05.356 Likely ports:['usb::004::004::2']
14:16:05.356 Detect Phone result: {'/dev/ttyACM0': {'mode_modem': 
True, 'mode_brew': False, 'firmwareresponse': 
None, 'esn': '1F866AEF', 'model': 'VX6100 108', 'firmware_version': 'S/W VER: 
DP3.3 PATCH  T61VZV02 ', 'manufacturer': 'LG Electronics 
Inc.'}, 'usb::004::004::2': {'mode_modem': None, 'mode_brew': 
False, 'firmwareresponse': None, 'esn': None, 'model': 
None, 'firmware_version': None, 'manufacturer': None}}
14:16:05.356 Checking for model: LG-VX10
14:16:05.356 Checking for model: LG-VX10000
14:16:05.357 Likely ports:['usb::004::004::2']
14:16:05.357 Detect Phone result: {'/dev/ttyACM0': {'mode_modem': 
True, 'mode_brew': False, 'firmwareresponse': 
None, 'esn': '1F866AEF', 'model': 'VX6100 108', 'firmware_version': 'S/W VER: 
DP3.3 PATCH  T61VZV02 ', 'manufacturer': 'LG Electronics 
Inc.'}, 'usb::004::004::2': {'mode_modem': None, 'mode_brew': 
False, 'firmwareresponse': None, 'esn': None, 'model': 
None, 'firmware_version': None, 'manufacturer': None}}
14:16:05.357 Checking for model: LG-VX3200
14:16:05.430 Likely ports:[]
14:16:05.431 Detect Phone result: {'/dev/ttyACM0': {'mode_modem': 
True, 'mode_brew': False, 'firmwareresponse': 
None, 'esn': '1F866AEF', 'model': 'VX6100 108', 'firmware_version': 'S/W VER: 
DP3.3 PATCH  T61VZV02 ', 'manufacturer': 'LG Electronics 
Inc.'}, 'usb::004::004::2': {'mode_modem': None, 'mode_brew': 
False, 'firmwareresponse': None, 'esn': None, 'model': 
None, 'firmware_version': None, 'manufacturer': None}}
14:16:05.431 Checking for model: LG-VX4400
14:16:05.431 Likely ports:['usb::004::004::2']
14:16:05.431 Detect Phone result: {'/dev/ttyACM0': {'mode_modem': 
True, 'mode_brew': False, 'firmwareresponse': 
None, 'esn': '1F866AEF', 'model': 'VX6100 108', 'firmware_version': 'S/W VER: 
DP3.3 PATCH  T61VZV02 ', 'manufacturer': 'LG Electronics 
Inc.'}, 'usb::004::004::2': {'mode_modem': None, 'mode_brew': 
False, 'firmwareresponse': None, 'esn': None, 'model': 
None, 'firmware_version': None, 'manufacturer': None}}
14:16:05.431 Checking for model: LG-VX4500
14:16:05.524 Likely ports:[]
14:16:05.524 Detect Phone result: {'/dev/ttyACM0': {'mode_modem': 
True, 'mode_brew': False, 'firmwareresponse': 
None, 'esn': '1F866AEF', 'model': 'VX6100 108', 'firmware_version': 'S/W VER: 
DP3.3 PATCH  T61VZV02 ', 'manufacturer': 'LG Electronics 
Inc.'}, 'usb::004::004::2': {'mode_modem': None, 'mode_brew': 
False, 'firmwareresponse': None, 'esn': None, 'model': 
None, 'firmware_version': None, 'manufacturer': None}}
14:16:05.525 Checking for model: LG-VX4600
14:16:05.525 Likely ports:['usb::004::004::2']
14:16:05.525 Detect Phone result: {'/dev/ttyACM0': {'mode_modem': 
True, 'mode_brew': False, 'firmwareresponse': 
None, 'esn': '1F866AEF', 'model': 'VX6100 108', 'firmware_version': 'S/W VER: 
DP3.3 PATCH  T61VZV02 ', 'manufacturer': 'LG Electronics 
Inc.'}, 'usb::004::004::2': {'mode_modem': None, 'mode_brew': 
False, 'firmwareresponse': None, 'esn': None, 'model': 
None, 'firmware_version': None, 'manufacturer': None}}
14:16:05.525 Checking for model: LG-VX4650
14:16:05.600 Likely ports:['usb::004::004::2']
14:16:05.600 Detect Phone result: {'/dev/ttyACM0': {'mode_modem': 
True, 'mode_brew': False, 'firmwareresponse': 
None, 'esn': '1F866AEF', 'model': 'VX6100 108', 'firmware_version': 'S/W VER: 
DP3.3 PATCH  T61VZV02 ', 'manufacturer': 'LG Electronics 
Inc.'}, 'usb::004::004::2': {'mode_modem': None, 'mode_brew': 
False, 'firmwareresponse': None, 'esn': None, 'model': 
None, 'firmware_version': None, 'manufacturer': None}}
14:16:05.600 Checking for model: LG-VX5200
14:16:05.600 Likely ports:['usb::004::004::2']
14:16:05.601 Detect Phone result: {'/dev/ttyACM0': {'mode_modem': 
True, 'mode_brew': False, 'firmwareresponse': 
None, 'esn': '1F866AEF', 'model': 'VX6100 108', 'firmware_version': 'S/W VER: 
DP3.3 PATCH  T61VZV02 ', 'manufacturer': 'LG Electronics 
Inc.'}, 'usb::004::004::2': {'mode_modem': None, 'mode_brew': 
False, 'firmwareresponse': None, 'esn': None, 'model': 
None, 'firmware_version': None, 'manufacturer': None}}
14:16:05.601 Checking for model: LG-VX5300
14:16:05.665 Likely ports:['usb::004::004::2']
14:16:05.665 Detect Phone result: {'/dev/ttyACM0': {'mode_modem': 
True, 'mode_brew': False, 'firmwareresponse': 
None, 'esn': '1F866AEF', 'model': 'VX6100 108', 'firmware_version': 'S/W VER: 
DP3.3 PATCH  T61VZV02 ', 'manufacturer': 'LG Electronics 
Inc.'}, 'usb::004::004::2': {'mode_modem': None, 'mode_brew': 
False, 'firmwareresponse': None, 'esn': None, 'model': 
None, 'firmware_version': None, 'manufacturer': None}}
14:16:05.665 Checking for model: LG-VX5400
14:16:05.665 Likely ports:['usb::004::004::2']
14:16:05.666 Detect Phone result: {'/dev/ttyACM0': {'mode_modem': 
True, 'mode_brew': False, 'firmwareresponse': 
None, 'esn': '1F866AEF', 'model': 'VX6100 108', 'firmware_version': 'S/W VER: 
DP3.3 PATCH  T61VZV02 ', 'manufacturer': 'LG Electronics 
Inc.'}, 'usb::004::004::2': {'mode_modem': None, 'mode_brew': 
False, 'firmwareresponse': None, 'esn': None, 'model': 
None, 'firmware_version': None, 'manufacturer': None}}
14:16:05.666 Checking for model: LG-VX6000
14:16:05.737 Likely ports:['usb::004::004::2']
14:16:05.737 Detect Phone result: {'/dev/ttyACM0': {'mode_modem': 
True, 'mode_brew': False, 'firmwareresponse': 
None, 'esn': '1F866AEF', 'model': 'VX6100 108', 'firmware_version': 'S/W VER: 
DP3.3 PATCH  T61VZV02 ', 'manufacturer': 'LG Electronics 
Inc.'}, 'usb::004::004::2': {'mode_modem': None, 'mode_brew': 
False, 'firmwareresponse': None, 'esn': None, 'model': 
None, 'firmware_version': None, 'manufacturer': None}}
14:16:05.738 Checking for model: LG-VX6100
14:16:05.738 Likely ports:['usb::004::004::2']
14:16:05.738 Detect Phone result: {'/dev/ttyACM0': {'mode_modem': 
True, 'mode_brew': False, 'firmwareresponse': 
None, 'esn': '1F866AEF', 'model': 'VX6100 108', 'firmware_version': 'S/W VER: 
DP3.3 PATCH  T61VZV02 ', 'manufacturer': 'LG Electronics 
Inc.'}, 'usb::004::004::2': {'mode_modem': None, 'mode_brew': 
False, 'firmwareresponse': None, 'esn': None, 'model': 
None, 'firmware_version': None, 'manufacturer': None}}
14:16:05.738 Checking for model: LG-VX7000
14:16:05.738 Likely ports:['usb::004::004::2']
14:16:05.739 Detect Phone result: {'/dev/ttyACM0': {'mode_modem': 
True, 'mode_brew': False, 'firmwareresponse': 
None, 'esn': '1F866AEF', 'model': 'VX6100 108', 'firmware_version': 'S/W VER: 
DP3.3 PATCH  T61VZV02 ', 'manufacturer': 'LG Electronics 
Inc.'}, 'usb::004::004::2': {'mode_modem': None, 'mode_brew': 
False, 'firmwareresponse': None, 'esn': None, 'model': 
None, 'firmware_version': None, 'manufacturer': None}}
14:16:05.739 Checking for model: LG-VX8000
14:16:05.739 Likely ports:['usb::004::004::2']
14:16:05.739 Detect Phone result: {'/dev/ttyACM0': {'mode_modem': 
True, 'mode_brew': False, 'firmwareresponse': 
None, 'esn': '1F866AEF', 'model': 'VX6100 108', 'firmware_version': 'S/W VER: 
DP3.3 PATCH  T61VZV02 ', 'manufacturer': 'LG Electronics 
Inc.'}, 'usb::004::004::2': {'mode_modem': None, 'mode_brew': 
False, 'firmwareresponse': None, 'esn': None, 'model': 
None, 'firmware_version': None, 'manufacturer': None}}
14:16:05.739 Checking for model: LG-VX8100
14:16:05.740 Likely ports:['usb::004::004::2']
14:16:05.740 Detect Phone result: {'/dev/ttyACM0': {'mode_modem': 
True, 'mode_brew': False, 'firmwareresponse': 
None, 'esn': '1F866AEF', 'model': 'VX6100 108', 'firmware_version': 'S/W VER: 
DP3.3 PATCH  T61VZV02 ', 'manufacturer': 'LG Electronics 
Inc.'}, 'usb::004::004::2': {'mode_modem': None, 'mode_brew': 
False, 'firmwareresponse': None, 'esn': None, 'model': 
None, 'firmware_version': None, 'manufacturer': None}}
14:16:05.740 Checking for model: LG-VX8300
14:16:05.740 Likely ports:['usb::004::004::2']
14:16:05.740 Detect Phone result: {'/dev/ttyACM0': {'mode_modem': 
True, 'mode_brew': False, 'firmwareresponse': 
None, 'esn': '1F866AEF', 'model': 'VX6100 108', 'firmware_version': 'S/W VER: 
DP3.3 PATCH  T61VZV02 ', 'manufacturer': 'LG Electronics 
Inc.'}, 'usb::004::004::2': {'mode_modem': None, 'mode_brew': 
False, 'firmwareresponse': None, 'esn': None, 'model': 
None, 'firmware_version': None, 'manufacturer': None}}
14:16:05.741 Checking for model: LG-VX8350
14:16:05.741 Likely ports:['usb::004::004::2']
14:16:05.741 Detect Phone result: {'/dev/ttyACM0': {'mode_modem': 
True, 'mode_brew': False, 'firmwareresponse': 
None, 'esn': '1F866AEF', 'model': 'VX6100 108', 'firmware_version': 'S/W VER: 
DP3.3 PATCH  T61VZV02 ', 'manufacturer': 'LG Electronics 
Inc.'}, 'usb::004::004::2': {'mode_modem': None, 'mode_brew': 
False, 'firmwareresponse': None, 'esn': None, 'model': 
None, 'firmware_version': None, 'manufacturer': None}}
14:16:05.741 Checking for model: LG-VX8500
14:16:05.741 Likely ports:['usb::004::004::2']
14:16:05.742 Detect Phone result: {'/dev/ttyACM0': {'mode_modem': 
True, 'mode_brew': False, 'firmwareresponse': 
None, 'esn': '1F866AEF', 'model': 'VX6100 108', 'firmware_version': 'S/W VER: 
DP3.3 PATCH  T61VZV02 ', 'manufacturer': 'LG Electronics 
Inc.'}, 'usb::004::004::2': {'mode_modem': None, 'mode_brew': 
False, 'firmwareresponse': None, 'esn': None, 'model': 
None, 'firmware_version': None, 'manufacturer': None}}
14:16:05.742 Checking for model: LG-VX8550
14:16:05.742 Likely ports:['usb::004::004::2']
14:16:05.742 Detect Phone result: {'/dev/ttyACM0': {'mode_modem': 
True, 'mode_brew': False, 'firmwareresponse': 
None, 'esn': '1F866AEF', 'model': 'VX6100 108', 'firmware_version': 'S/W VER: 
DP3.3 PATCH  T61VZV02 ', 'manufacturer': 'LG Electronics 
Inc.'}, 'usb::004::004::2': {'mode_modem': None, 'mode_brew': 
False, 'firmwareresponse': None, 'esn': None, 'model': 
None, 'firmware_version': None, 'manufacturer': None}}
14:16:05.742 Checking for model: LG-VX8600
14:16:05.903 Likely ports:['usb::004::004::2']
14:16:05.903 Detect Phone result: {'/dev/ttyACM0': {'mode_modem': 
True, 'mode_brew': False, 'firmwareresponse': 
None, 'esn': '1F866AEF', 'model': 'VX6100 108', 'firmware_version': 'S/W VER: 
DP3.3 PATCH  T61VZV02 ', 'manufacturer': 'LG Electronics 
Inc.'}, 'usb::004::004::2': {'mode_modem': None, 'mode_brew': 
False, 'firmwareresponse': None, 'esn': None, 'model': 
None, 'firmware_version': None, 'manufacturer': None}}
14:16:05.903 Checking for model: LG-VX8700
14:16:05.903 Likely ports:['usb::004::004::2']
14:16:05.904 Detect Phone result: {'/dev/ttyACM0': {'mode_modem': 
True, 'mode_brew': False, 'firmwareresponse': 
None, 'esn': '1F866AEF', 'model': 'VX6100 108', 'firmware_version': 'S/W VER: 
DP3.3 PATCH  T61VZV02 ', 'manufacturer': 'LG Electronics 
Inc.'}, 'usb::004::004::2': {'mode_modem': None, 'mode_brew': 
False, 'firmwareresponse': None, 'esn': None, 'model': 
None, 'firmware_version': None, 'manufacturer': None}}
14:16:05.904 Checking for model: LG-VX8800
14:16:05.904 Likely ports:['usb::004::004::2']
14:16:05.904 Detect Phone result: {'/dev/ttyACM0': {'mode_modem': 
True, 'mode_brew': False, 'firmwareresponse': 
None, 'esn': '1F866AEF', 'model': 'VX6100 108', 'firmware_version': 'S/W VER: 
DP3.3 PATCH  T61VZV02 ', 'manufacturer': 'LG Electronics 
Inc.'}, 'usb::004::004::2': {'mode_modem': None, 'mode_brew': 
False, 'firmwareresponse': None, 'esn': None, 'model': 
None, 'firmware_version': None, 'manufacturer': None}}
14:16:05.904 Checking for model: LG-VX9400
14:16:05.905 Likely ports:['usb::004::004::2']
14:16:05.905 Detect Phone result: {'/dev/ttyACM0': {'mode_modem': 
True, 'mode_brew': False, 'firmwareresponse': 
None, 'esn': '1F866AEF', 'model': 'VX6100 108', 'firmware_version': 'S/W VER: 
DP3.3 PATCH  T61VZV02 ', 'manufacturer': 'LG Electronics 
Inc.'}, 'usb::004::004::2': {'mode_modem': None, 'mode_brew': 
False, 'firmwareresponse': None, 'esn': None, 'model': 
None, 'firmware_version': None, 'manufacturer': None}}
14:16:05.905 Checking for model: LG-VX9800
14:16:05.905 Likely ports:['usb::004::004::2']
14:16:05.905 Detect Phone result: {'/dev/ttyACM0': {'mode_modem': 
True, 'mode_brew': False, 'firmwareresponse': 
None, 'esn': '1F866AEF', 'model': 'VX6100 108', 'firmware_version': 'S/W VER: 
DP3.3 PATCH  T61VZV02 ', 'manufacturer': 'LG Electronics 
Inc.'}, 'usb::004::004::2': {'mode_modem': None, 'mode_brew': 
False, 'firmwareresponse': None, 'esn': None, 'model': 
None, 'firmware_version': None, 'manufacturer': None}}
14:16:05.906 Checking for model: LG-VX9900
14:16:05.906 Likely ports:['usb::004::004::2']
14:16:05.906 Detect Phone result: {'/dev/ttyACM0': {'mode_modem': 
True, 'mode_brew': False, 'firmwareresponse': 
None, 'esn': '1F866AEF', 'model': 'VX6100 108', 'firmware_version': 'S/W VER: 
DP3.3 PATCH  T61VZV02 ', 'manufacturer': 'LG Electronics 
Inc.'}, 'usb::004::004::2': {'mode_modem': None, 'mode_brew': 
False, 'firmwareresponse': None, 'esn': None, 'model': 
None, 'firmware_version': None, 'manufacturer': None}}
14:16:05.906 Checking for model: MM-5600
14:16:06.076 Checking for model: MM-7400
14:16:06.136 Checking for model: MM-7500
14:16:06.206 Likely ports:[]
14:16:06.249 Detect Phone result: {'/dev/ttyACM0': {'mode_modem': 
True, 'mode_brew': False, 'firmwareresponse': 
None, 'esn': '1F866AEF', 'model': 'VX6100 108', 'firmware_version': 'S/W VER: 
DP3.3 PATCH  T61VZV02 ', 'manufacturer': 'LG Electronics 
Inc.'}, 'usb::004::004::2': {'mode_modem': None, 'mode_brew': 
False, 'firmwareresponse': None, 'esn': None, 'model': 
None, 'firmware_version': None, 'manufacturer': None}}
14:16:06.250 Checking for model: MM-8300
14:16:06.250 Checking for model: Other CDMA phone
14:16:06.250 Checking for model: PM-8200
14:16:06.250 Checking for model: RL-4920
14:16:06.250 Checking for model: RL-4930
14:16:06.251 Checking for model: SCH-A310
14:16:06.320 Likely ports:[]
14:16:06.320 Detect Phone result: {'/dev/ttyACM0': {'mode_modem': 
True, 'mode_brew': False, 'firmwareresponse': 
None, 'esn': '1F866AEF', 'model': 'VX6100 108', 'firmware_version': 'S/W VER: 
DP3.3 PATCH  T61VZV02 ', 'manufacturer': 'LG Electronics 
Inc.'}, 'usb::004::004::2': {'mode_modem': None, 'mode_brew': 
False, 'firmwareresponse': None, 'esn': None, 'model': 
None, 'firmware_version': None, 'manufacturer': None}}
14:16:06.320 Checking for model: SCH-A650
14:16:06.321 Likely ports:[]
14:16:06.321 Detect Phone result: {'/dev/ttyACM0': {'mode_modem': 
True, 'mode_brew': False, 'firmwareresponse': 
None, 'esn': '1F866AEF', 'model': 'VX6100 108', 'firmware_version': 'S/W VER: 
DP3.3 PATCH  T61VZV02 ', 'manufacturer': 'LG Electronics 
Inc.'}, 'usb::004::004::2': {'mode_modem': None, 'mode_brew': 
False, 'firmwareresponse': None, 'esn': None, 'model': 
None, 'firmware_version': None, 'manufacturer': None}}
14:16:06.321 Checking for model: SCH-A670
14:16:06.321 Likely ports:[]
14:16:06.321 Detect Phone result: {'/dev/ttyACM0': {'mode_modem': 
True, 'mode_brew': False, 'firmwareresponse': 
None, 'esn': '1F866AEF', 'model': 'VX6100 108', 'firmware_version': 'S/W VER: 
DP3.3 PATCH  T61VZV02 ', 'manufacturer': 'LG Electronics 
Inc.'}, 'usb::004::004::2': {'mode_modem': None, 'mode_brew': 
False, 'firmwareresponse': None, 'esn': None, 'model': 
None, 'firmware_version': None, 'manufacturer': None}}
14:16:06.321 Checking for model: SCH-A870
14:16:06.463 Likely ports:[]
14:16:06.507 Detect Phone result: {'/dev/ttyACM0': {'mode_modem': 
True, 'mode_brew': False, 'firmwareresponse': 
None, 'esn': '1F866AEF', 'model': 'VX6100 108', 'firmware_version': 'S/W VER: 
DP3.3 PATCH  T61VZV02 ', 'manufacturer': 'LG Electronics 
Inc.'}, 'usb::004::004::2': {'mode_modem': None, 'mode_brew': 
False, 'firmwareresponse': None, 'esn': None, 'model': 
None, 'firmware_version': None, 'manufacturer': None}}
14:16:06.507 Checking for model: SCH-A930
14:16:06.507 Likely ports:[]
14:16:06.507 Detect Phone result: {'/dev/ttyACM0': {'mode_modem': 
True, 'mode_brew': False, 'firmwareresponse': 
None, 'esn': '1F866AEF', 'model': 'VX6100 108', 'firmware_version': 'S/W VER: 
DP3.3 PATCH  T61VZV02 ', 'manufacturer': 'LG Electronics 
Inc.'}, 'usb::004::004::2': {'mode_modem': None, 'mode_brew': 
False, 'firmwareresponse': None, 'esn': None, 'model': 
None, 'firmware_version': None, 'manufacturer': None}}
14:16:06.508 Checking for model: SCH-A950
14:16:06.508 Likely ports:[]
14:16:06.568 Detect Phone result: {'/dev/ttyACM0': {'mode_modem': 
True, 'mode_brew': False, 'firmwareresponse': 
None, 'esn': '1F866AEF', 'model': 'VX6100 108', 'firmware_version': 'S/W VER: 
DP3.3 PATCH  T61VZV02 ', 'manufacturer': 'LG Electronics 
Inc.'}, 'usb::004::004::2': {'mode_modem': None, 'mode_brew': 
False, 'firmwareresponse': None, 'esn': None, 'model': 
None, 'firmware_version': None, 'manufacturer': None}}
14:16:06.568 Checking for model: SCH-U470
14:16:06.639 Likely ports:[]
14:16:06.640 Detect Phone result: {'/dev/ttyACM0': {'mode_modem': 
True, 'mode_brew': False, 'firmwareresponse': 
None, 'esn': '1F866AEF', 'model': 'VX6100 108', 'firmware_version': 'S/W VER: 
DP3.3 PATCH  T61VZV02 ', 'manufacturer': 'LG Electronics 
Inc.'}, 'usb::004::004::2': {'mode_modem': None, 'mode_brew': 
False, 'firmwareresponse': None, 'esn': None, 'model': 
None, 'firmware_version': None, 'manufacturer': None}}
14:16:06.640 Checking for model: SCH-U740
14:16:06.640 Likely ports:[]
14:16:06.640 Detect Phone result: {'/dev/ttyACM0': {'mode_modem': 
True, 'mode_brew': False, 'firmwareresponse': 
None, 'esn': '1F866AEF', 'model': 'VX6100 108', 'firmware_version': 'S/W VER: 
DP3.3 PATCH  T61VZV02 ', 'manufacturer': 'LG Electronics 
Inc.'}, 'usb::004::004::2': {'mode_modem': None, 'mode_brew': 
False, 'firmwareresponse': None, 'esn': None, 'model': 
None, 'firmware_version': None, 'manufacturer': None}}
14:16:06.640 Checking for model: SCP-200
14:16:06.640 Checking for model: SCP-2400
14:16:06.641 Likely ports:[]
14:16:06.641 Detect Phone result: {'/dev/ttyACM0': {'mode_modem': 
True, 'mode_brew': False, 'firmwareresponse': 
None, 'esn': '1F866AEF', 'model': 'VX6100 108', 'firmware_version': 'S/W VER: 
DP3.3 PATCH  T61VZV02 ', 'manufacturer': 'LG Electronics 
Inc.'}, 'usb::004::004::2': {'mode_modem': None, 'mode_brew': 
False, 'firmwareresponse': None, 'esn': None, 'model': 
None, 'firmware_version': None, 'manufacturer': None}}
14:16:06.641 Checking for model: SCP-3100
14:16:06.641 Likely ports:[]
14:16:06.641 Detect Phone result: {'/dev/ttyACM0': {'mode_modem': 
True, 'mode_brew': False, 'firmwareresponse': 
None, 'esn': '1F866AEF', 'model': 'VX6100 108', 'firmware_version': 'S/W VER: 
DP3.3 PATCH  T61VZV02 ', 'manufacturer': 'LG Electronics 
Inc.'}, 'usb::004::004::2': {'mode_modem': None, 'mode_brew': 
False, 'firmwareresponse': None, 'esn': None, 'model': 
None, 'firmware_version': None, 'manufacturer': None}}
14:16:06.642 Checking for model: SCP-3200
14:16:06.746 Likely ports:[]
14:16:06.747 Detect Phone result: {'/dev/ttyACM0': {'mode_modem': 
True, 'mode_brew': False, 'firmwareresponse': 
None, 'esn': '1F866AEF', 'model': 'VX6100 108', 'firmware_version': 'S/W VER: 
DP3.3 PATCH  T61VZV02 ', 'manufacturer': 'LG Electronics 
Inc.'}, 'usb::004::004::2': {'mode_modem': None, 'mode_brew': 
False, 'firmwareresponse': None, 'esn': None, 'model': 
None, 'firmware_version': None, 'manufacturer': None}}
14:16:06.747 Checking for model: SCP-4900
14:16:06.747 Checking for model: SCP-5300
14:16:06.747 Checking for model: SCP-5400
14:16:06.824 Checking for model: SCP-5500
14:16:06.825 Checking for model: SCP-6600 (Katana)
14:16:06.868 Likely ports:[]
14:16:06.869 Detect Phone result: {'/dev/ttyACM0': {'mode_modem': 
True, 'mode_brew': False, 'firmwareresponse': 
None, 'esn': '1F866AEF', 'model': 'VX6100 108', 'firmware_version': 'S/W VER: 
DP3.3 PATCH  T61VZV02 ', 'manufacturer': 'LG Electronics 
Inc.'}, 'usb::004::004::2': {'mode_modem': None, 'mode_brew': 
False, 'firmwareresponse': None, 'esn': None, 'model': 
None, 'firmware_version': None, 'manufacturer': None}}
14:16:06.869 Checking for model: SCP-6650 (Katana-II)
14:16:06.933 Likely ports:[]
14:16:06.933 Detect Phone result: {'/dev/ttyACM0': {'mode_modem': 
True, 'mode_brew': False, 'firmwareresponse': 
None, 'esn': '1F866AEF', 'model': 'VX6100 108', 'firmware_version': 'S/W VER: 
DP3.3 PATCH  T61VZV02 ', 'manufacturer': 'LG Electronics 
Inc.'}, 'usb::004::004::2': {'mode_modem': None, 'mode_brew': 
False, 'firmwareresponse': None, 'esn': None, 'model': 
None, 'firmware_version': None, 'manufacturer': None}}
14:16:06.934 Checking for model: SCP-7050
14:16:06.934 Likely ports:[]
14:16:06.934 Detect Phone result: {'/dev/ttyACM0': {'mode_modem': 
True, 'mode_brew': False, 'firmwareresponse': 
None, 'esn': '1F866AEF', 'model': 'VX6100 108', 'firmware_version': 'S/W VER: 
DP3.3 PATCH  T61VZV02 ', 'manufacturer': 'LG Electronics 
Inc.'}, 'usb::004::004::2': {'mode_modem': None, 'mode_brew': 
False, 'firmwareresponse': None, 'esn': None, 'model': 
None, 'firmware_version': None, 'manufacturer': None}}
14:16:06.934 Checking for model: SCP-7200
14:16:06.934 Checking for model: SCP-7300
14:16:06.935 Checking for model: SCP-8100
14:16:07.030 Checking for model: SCP-8100 (Bell)
14:16:07.031 Checking for model: SK6100
14:16:07.031 Checking for model: SPH-A460
14:16:07.099 Checking for model: SPH-A620 (VGA1000)
14:16:07.100 Checking for model: SPH-A660 (VI660)
14:16:07.100 Checking for model: SPH-A680
14:16:07.100 Checking for model: SPH-A740
14:16:07.100 Checking for model: SPH-A840
14:16:07.100 Checking for model: SPH-A840 (Telus)
14:16:07.163 Checking for model: SPH-A900
14:16:07.163 Checking for model: SPH-M300MEDIA
14:16:07.225 Likely ports:[]
14:16:07.226 Detect Phone result: {'/dev/ttyACM0': {'mode_modem': 
True, 'mode_brew': False, 'firmwareresponse': 
None, 'esn': '1F866AEF', 'model': 'VX6100 108', 'firmware_version': 'S/W VER: 
DP3.3 PATCH  T61VZV02 ', 'manufacturer': 'LG Electronics 
Inc.'}, 'usb::004::004::2': {'mode_modem': None, 'mode_brew': 
False, 'firmwareresponse': None, 'esn': None, 'model': 
None, 'firmware_version': None, 'manufacturer': None}}
14:16:07.226 Checking for model: SPH-M300PIM
14:16:07.226 Checking for model: SPH-N200
14:16:07.226 Checking for model: SPH-N400
14:16:07.677 Checking for model: V325
14:16:07.722 Likely ports:[]
14:16:07.723 Detect Phone result: {'/dev/ttyACM0': {'mode_modem': 
True, 'mode_brew': False, 'firmwareresponse': 
None, 'esn': '1F866AEF', 'model': 'VX6100 108', 'firmware_version': 'S/W VER: 
DP3.3 PATCH  T61VZV02 ', 'manufacturer': 'LG Electronics 
Inc.'}, 'usb::004::004::2': {'mode_modem': None, 'mode_brew': 
False, 'firmwareresponse': None, 'esn': None, 'model': 
None, 'firmware_version': None, 'manufacturer': None}}
14:16:07.723 Checking for model: V325M
14:16:07.723 Likely ports:[]
14:16:07.723 Detect Phone result: {'/dev/ttyACM0': {'mode_modem': 
True, 'mode_brew': False, 'firmwareresponse': 
None, 'esn': '1F866AEF', 'model': 'VX6100 108', 'firmware_version': 'S/W VER: 
DP3.3 PATCH  T61VZV02 ', 'manufacturer': 'LG Electronics 
Inc.'}, 'usb::004::004::2': {'mode_modem': None, 'mode_brew': 
False, 'firmwareresponse': None, 'esn': None, 'model': 
None, 'firmware_version': None, 'manufacturer': None}}
14:16:07.723 Checking for model: V3c
14:16:07.724 Likely ports:[]
14:16:07.724 Detect Phone result: {'/dev/ttyACM0': {'mode_modem': 
True, 'mode_brew': False, 'firmwareresponse': 
None, 'esn': '1F866AEF', 'model': 'VX6100 108', 'firmware_version': 'S/W VER: 
DP3.3 PATCH  T61VZV02 ', 'manufacturer': 'LG Electronics 
Inc.'}, 'usb::004::004::2': {'mode_modem': None, 'mode_brew': 
False, 'firmwareresponse': None, 'esn': None, 'model': 
None, 'firmware_version': None, 'manufacturer': None}}
14:16:07.724 Checking for model: V3cm
14:16:07.724 Likely ports:[]
14:16:07.724 Detect Phone result: {'/dev/ttyACM0': {'mode_modem': 
True, 'mode_brew': False, 'firmwareresponse': 
None, 'esn': '1F866AEF', 'model': 'VX6100 108', 'firmware_version': 'S/W VER: 
DP3.3 PATCH  T61VZV02 ', 'manufacturer': 'LG Electronics 
Inc.'}, 'usb::004::004::2': {'mode_modem': None, 'mode_brew': 
False, 'firmwareresponse': None, 'esn': None, 'model': 
None, 'firmware_version': None, 'manufacturer': None}}
14:16:07.725 Checking for model: V3m
14:16:07.725 Likely ports:[]
14:16:07.725 Detect Phone result: {'/dev/ttyACM0': {'mode_modem': 
True, 'mode_brew': False, 'firmwareresponse': 
None, 'esn': '1F866AEF', 'model': 'VX6100 108', 'firmware_version': 'S/W VER: 
DP3.3 PATCH  T61VZV02 ', 'manufacturer': 'LG Electronics 
Inc.'}, 'usb::004::004::2': {'mode_modem': None, 'mode_brew': 
False, 'firmwareresponse': None, 'esn': None, 'model': 
None, 'firmware_version': None, 'manufacturer': None}}
14:16:07.725 Checking for model: V3mM
14:16:07.725 Likely ports:[]
14:16:07.726 Detect Phone result: {'/dev/ttyACM0': {'mode_modem': 
True, 'mode_brew': False, 'firmwareresponse': 
None, 'esn': '1F866AEF', 'model': 'VX6100 108', 'firmware_version': 'S/W VER: 
DP3.3 PATCH  T61VZV02 ', 'manufacturer': 'LG Electronics 
Inc.'}, 'usb::004::004::2': {'mode_modem': None, 'mode_brew': 
False, 'firmwareresponse': None, 'esn': None, 'model': 
None, 'firmware_version': None, 'manufacturer': None}}
14:16:07.726 Checking for model: V710
14:16:07.726 Likely ports:[]
14:16:07.726 Detect Phone result: {'/dev/ttyACM0': {'mode_modem': 
True, 'mode_brew': False, 'firmwareresponse': 
None, 'esn': '1F866AEF', 'model': 'VX6100 108', 'firmware_version': 'S/W VER: 
DP3.3 PATCH  T61VZV02 ', 'manufacturer': 'LG Electronics 
Inc.'}, 'usb::004::004::2': {'mode_modem': None, 'mode_brew': 
False, 'firmwareresponse': None, 'esn': None, 'model': 
None, 'firmware_version': None, 'manufacturer': None}}
14:16:07.726 Checking for model: V710m
14:16:07.726 Likely ports:[]
14:16:07.727 Detect Phone result: {'/dev/ttyACM0': {'mode_modem': 
True, 'mode_brew': False, 'firmwareresponse': 
None, 'esn': '1F866AEF', 'model': 'VX6100 108', 'firmware_version': 'S/W VER: 
DP3.3 PATCH  T61VZV02 ', 'manufacturer': 'LG Electronics 
Inc.'}, 'usb::004::004::2': {'mode_modem': None, 'mode_brew': 
False, 'firmwareresponse': None, 'esn': None, 'model': 
None, 'firmware_version': None, 'manufacturer': None}}
14:16:07.727 Checking for model: VI-2300
14:16:07.727 Checking for model: VM4050
14:16:07.825 Likely ports:[]
14:16:07.825 Detect Phone result: {'/dev/ttyACM0': {'mode_modem': 
True, 'mode_brew': False, 'firmwareresponse': 
None, 'esn': '1F866AEF', 'model': 'VX6100 108', 'firmware_version': 'S/W VER: 
DP3.3 PATCH  T61VZV02 ', 'manufacturer': 'LG Electronics 
Inc.'}, 'usb::004::004::2': {'mode_modem': None, 'mode_brew': 
False, 'firmwareresponse': None, 'esn': None, 'model': 
None, 'firmware_version': None, 'manufacturer': None}}





---------------------------
Start BitPim and connect phone and select manually:

13:52:03.300 usb::004::002::2: Opening port usb::004::002::2, 115200 baud, 
timeout 3.000000, hardwareflow 0, softwareflow 0
13:52:03.301 usb::004::002::2: Open of comm port suceeded
13:52:03.301 LG-VX6100: Attempting to contact phone
13:52:03.301 LG-VX6100: Getting Phone Info
13:52:03.301 LG-VX6100: Getting file contents 'brew/version.txt'
13:52:09.296 usb::004::002::2: Timed out - flushing and trying again
13:52:15.310 usb::004::002::2: Timed out waiting for 7e, requested 
bytes -99999  - 0 bytes read
13:52:21.332 usb::004::002::2: Timed out - flushing and trying again
13:52:30.348 usb::004::002::2: Timed out waiting for 7e, requested 
bytes -99999  - 0 bytes read
13:52:30.348 usb::004::002::2: Port speed 38400 not supported
13:52:30.349 usb::004::002::2: Port speed 115200 not supported
13:52:33.476 usb::004::002::2: Write Exception: could not set config 1: Device 
or resource busy
13:52:33.476 LG-VX6100: No response to AT+GMM
13:52:33.477 usb::004::002::2: Write Exception: could not set config 1: Device 
or resource busy
-----------------------------
************
Start BitPim, connect phone, *THEN start phone* and select manually:

13:56:58.711 usb::004::003::2: Opening port usb::004::003::2, 115200 baud, 
timeout 3.000000, hardwareflow 0, softwareflow 0
13:56:58.712 usb::004::003::2: Open of comm port suceeded
13:56:58.712 LG-VX6100: Attempting to contact phone
13:56:58.712 LG-VX6100: Getting Phone Info
13:56:58.712 LG-VX6100: Getting file contents 'brew/version.txt'
13:56:58.822 LG-VX6100: Now in brew mode
13:56:58.855 LG-VX6100: Getting file contents 'nvm/$SYS.ESN'
13:56:58.943 LG-VX6100: Getting file contents 'nvm/nvm/nvm_0000'

************ It works!!!

-----------------------------
Start BitPim, connect phone, *THEN start phone* and autoscan
** detects generic phone?? if use auto-detect **
this is probably another issue, the lsusb data may help.
log
...
14:21:14.756 Likely ports:[]
14:21:14.756 Detect Phone result: {'/dev/ttyACM0': {'mode_modem': 
True, 'mode_brew': False, 'firmwareresponse': 
None, 'esn': '1F866AEF', 'model': 'VX6100 108', 'firmware_version': 'S/W VER: 
DP3.3 PATCH  T61VZV02 ', 'manufacturer': 'LG Electronics 
Inc.'}, 'usb::004::005::2': {'mode_modem': None, 'esn_file': 
None, 'lgpbinfo': None, 'mode_brew': True, 'firmwareresponse': None, 'esn': 
None, 'model': None, 'brew_version.txt': None, 'firmware_version': 
None, 'manufacturer': None}}
14:21:14.756 Found phone:Other CDMA phone port:'usb::004::005::2'

-------------
-------------------------------------------------------

Re: [BitPim-devel] Thank you

From: Don L. <dl...@la...> - 2008-07-30 13:44:24

I use Bitpim all the time, and want to thank all the developers working on this project.

I truly appreciate the amount of time and quality of the work you are all doing, as well as, your dedication to the project.

Thanks,
Don L. Lewis

Re: [BitPim-devel] Bug report - SMS Sent Items and Sanyo MM-7500

From: -= D. =- <del...@ya...> - 2008-07-29 20:31:59

Thanks again for your quick response on this issue Stephen.  Do you by any chance know when your fix will be implemented in the next 'test' version?  When I read through the list of changes on the latest test release (1.0.6.20080726), I did not see the fix mentioned.  I tried it just in case, but the issue is still there. 

I'm looking forward to testing out the patch to see if the issue has been taken care of once and for all.

-----------------------------------------------------------
Date: Sat, 26 Jul 2008 23:24:40 -0400
From: "Stephen Wood" 
Subject: Re: [BitPim-devel] Re-send: Re: Bug report - SMS Sent Items
    and    Sanyo MM-7500
To: bit...@li...
Message-ID:
    <2d1...@ma...>
Content-Type: text/plain; charset=ISO-8859-1

I have put in a patch to fix this, making the padding before the date
larger. The patch only applied to the SCP-7500.  If anyone has seen
this problem on other Sanyo phones, let me know.

Stephen

On Fri, Jul 25, 2008 at 5:47 PM, -= Delphicoder =-
<del...@ya...> wrote:
> I appreciate the quick response Stephen.  I have attached a text file
> containing the send and receive of the same message.  I believe the problem
> lies in offset "00000110", as you will notice that the data is offset by 1
> to the right on the second set of data.
>

Re: [BitPim-devel] BitPim port connection failure on test release

From: Sean B. <sea...@gm...> - 2008-07-29 14:37:48

Nathan, Don,  There may be an issue with the USB module build script. I'll
check to see if the module is being built as a universal binary.   If it
isn't, I'll release builds for both platforms until we can get
it straightened out.

Best,

Sean


On Tue, Jul 29, 2008 at 10:00 AM, Nathan Hjelm <hj...@ma...> wrote:

> Does the phone show up as available when manually selecting a port? If
> it is under "Ports not unavailable" do you get an error when trying to
> access the phone after selecting the port?
>
> The port you are looking for is named "USB Device - Vendor LG
> Electronics, Product VX Series Phone (Direct USB connection),
> (Interface Diagnostics Interface)"
>
> -Nathan
>
> On Jul 29, 2008, at 7:32 AM, Don Lewis wrote:
>
> >
> > The new test build errors on connection.
> >
> > "Failed to auto-detect the port to use.  I couldn't
> > detect any candidate ports to use."
> >
> > Mac Powerbook G4 OSX 10.5.4 (non Intel)
> >
> > LG VX 5300
> >
> > Works properly on Bitpim 1.0.5 release
> >
> > Don L.
> >
> > -------------------------------------------------------------------------
> > This SF.Net email is sponsored by the Moblin Your Move Developer's
> > challenge
> > Build the coolest Linux based applications with Moblin SDK & win
> > great prizes
> > Grand prize is a trip for two to an Open Source event anywhere in
> > the world
> > http://moblin-contest.org/redirect.php?banner_id=100&url=/
> > _______________________________________________
> > BitPim-devel mailing list
> > Bit...@li...
> > https://lists.sourceforge.net/lists/listinfo/bitpim-devel
>
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's
> challenge
> Build the coolest Linux based applications with Moblin SDK & win great
> prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> BitPim-devel mailing list
> Bit...@li...
> https://lists.sourceforge.net/lists/listinfo/bitpim-devel
>



-- 
Sean Burke
Imaging Analysis Specialist
Albert Einstein College of Medicine
Yeshiva University
Bronx, NY 10461

Re: [BitPim-devel] BitPim port connection failure on test release

From: Nathan H. <hj...@ma...> - 2008-07-29 14:05:00

Does the phone show up as available when manually selecting a port? If  
it is under "Ports not unavailable" do you get an error when trying to  
access the phone after selecting the port?

The port you are looking for is named "USB Device - Vendor LG  
Electronics, Product VX Series Phone (Direct USB connection),  
(Interface Diagnostics Interface)"

-Nathan

On Jul 29, 2008, at 7:32 AM, Don Lewis wrote:

>
> The new test build errors on connection.
>
> "Failed to auto-detect the port to use.  I couldn't
> detect any candidate ports to use."
>
> Mac Powerbook G4 OSX 10.5.4 (non Intel)
>
> LG VX 5300
>
> Works properly on Bitpim 1.0.5 release
>
> Don L.
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's  
> challenge
> Build the coolest Linux based applications with Moblin SDK & win  
> great prizes
> Grand prize is a trip for two to an Open Source event anywhere in  
> the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> BitPim-devel mailing list
> Bit...@li...
> https://lists.sourceforge.net/lists/listinfo/bitpim-devel

Re: [BitPim-devel] BitPim port connection failure on test release

From: Don L. <dl...@la...> - 2008-07-29 14:00:30

USB LG cable I tried both USB Ports on the Mac.  Both failed with the same error.
 
Don L.
 

-----Original Message-----
From: bit...@li... [mailto:bit...@li...]On Behalf Of Sean Burke
Sent: Tuesday, July 29, 2008 7:55 AM
To: bit...@li...
Subject: Re: [BitPim-devel] BitPim port connection failure on test release


Don, 
  Are you using the USB or Bluetooth connection?

Sean



On Tue, Jul 29, 2008 at 9:32 AM, Don Lewis < dl...@la...> wrote:



The new test build errors on connection.

"Failed to auto-detect the port to use.  I couldn't
detect any candidate ports to use."

Mac Powerbook G4 OSX 10.5.4 (non Intel)

LG VX 5300

Works properly on Bitpim 1.0.5 release

Don L.

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100 <http://moblin-contest.org/redirect.php?banner_id=100&url=/> &url=/
_______________________________________________
BitPim-devel mailing list
Bit...@li...
https://lists.sourceforge.net/lists/listinfo/bitpim-devel





-- 
Sean Burke
Imaging Analysis Specialist
Albert Einstein College of Medicine
Yeshiva University
Bronx, NY 10461

Re: [BitPim-devel] BitPim port connection failure on test release

From: Sean B. <sea...@gm...> - 2008-07-29 13:54:30

Don,  Are you using the USB or Bluetooth connection?

Sean



On Tue, Jul 29, 2008 at 9:32 AM, Don Lewis <dl...@la...> wrote:

>
> The new test build errors on connection.
>
> "Failed to auto-detect the port to use.  I couldn't
> detect any candidate ports to use."
>
> Mac Powerbook G4 OSX 10.5.4 (non Intel)
>
> LG VX 5300
>
> Works properly on Bitpim 1.0.5 release
>
> Don L.
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's
> challenge
> Build the coolest Linux based applications with Moblin SDK & win great
> prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> BitPim-devel mailing list
> Bit...@li...
> https://lists.sourceforge.net/lists/listinfo/bitpim-devel
>



-- 
Sean Burke
Imaging Analysis Specialist
Albert Einstein College of Medicine
Yeshiva University
Bronx, NY 10461

[BitPim-devel] BitPim port connection failure on test release

From: Don L. <dl...@la...> - 2008-07-29 13:32:06

The new test build errors on connection.

"Failed to auto-detect the port to use.  I couldn't  
detect any candidate ports to use."

Mac Powerbook G4 OSX 10.5.4 (non Intel)

LG VX 5300

Works properly on Bitpim 1.0.5 release

Don L.

Re: [BitPim-devel] BitPim Test Release 1.0.6.20080724 available

From: Joe P. <dj...@ne...> - 2008-07-29 01:19:37

>Forgot to mention to run protogen.py. Can you fix that and build a 
>new test version?

Once upon a time, those files were generated at build time, apparently it no longer does that.  I'll fix the build script.  A new test release is now available.

-Joe Pham



____________________________________________________________
Orlando Vacations - Click Here!
http://thirdpartyoffers.netzero.net/TGL2231/fc/Ioyw6ijmf39myT0a0MRq65TBxvorPqTEMo93K6QcPtMWf1hxvLDDlK/

[BitPim-devel] BitPim Test Release 1.0.6.20080724 available

From: Joe P. <dj...@ne...> - 2008-07-29 00:59:30

Grab it from:

<http://sourceforge.net/project/showfiles.php?group_id=75211&package_id=76673&release_id=615895>

Changes in this release:

***** Changes in 1.0.6 *****
    * Bug fix: LG VX-8800/10000 Note Pad.
    * Improvement: LG AX-8600 Call History and Note Pad (patch submitted by
      David Ritter).
    * Bug fix: LG VX-8500/8800/10000: better BREW file access (i.e. fewer "file
      block" errors).
    * Bug fix: LG VX-9900: access to the mmc1 dir via Command Line Interface
      (CLI).
    * Bug fix: Motorola: BitPim failed to read phonebook from some Motorola
      models.
    * Improvement: Call History: Navigate to other subtrees.
    * Bug fix: SCP-6650: Fix Katana-II phone/port detection
    * Add "extrazero" fields to listfile and listdirectory responses so that
      filesystem view will work for Samsung SPHA-900. May break filesystem view
      for other phones.
    * New phone support: Sanyo SCP-8400
    * New phone support: LG VX-9100 (enV2) (Initial)
    * Bug fix: Can't view Data Recording files on non-Intel Mac.
    * Bug fix: Correctly process BREW special files.
    * New phone support: LG VX-8560 (Initial)
    * New Phone support: LG VX-9700 (Initial)
    * New Phone support: LG VX-8610 (Initial)
    * Bug fix: LG VX-9900 SMS support.

This release also fixed a build issue in the 1.0.6.20080724 that broke support for the LG Dare & Chocolate 3.

-Joe Pham

____________________________________________________________
Click for  FHA loan, $0 lender fees, low rates & approvals nationwide
http://thirdpartyoffers.netzero.net/TGL2231/fc/Ioyw6ijldpyS5ci3V7UA5rwXyvXyVZa4rudX1n5u9So5rkuBdYSVr2/

[BitPim-devel] U8120 - U8330

From: Manolo S. <man...@gm...> - 2008-07-27 09:20:40

Hi to all.

I'm trying to manage my LG U8330 (download files from
phone to my ASUS F3Ja laptop, for example). I've been trying some other
programs
with no success. Now I just installed BitPim but still no luck. First
of all Ubuntu 8.04 detects it as u8120 and not as u8330 (may be because I
installed
another firmware version on my LG?!?)

lsusb
Bus 005 Device 001: ID 0000:0000
Bus 004 Device 001: ID 0000:0000
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 004: ID 046d:c019 Logitech, Inc.
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 002: ID 1004:1fae LG Electronics, Inc. U8120 3G Cellphone
Bus 001 Device 001: ID 0000:0000

but it shows at least that Ubuntu recognized an LG mobile phone connected to
a usb port.

"BitPim 1.0.5 - official" doesn't seem to have neither u8120 nor u8330
models in it's "supported phones" list anyway.
Any suggestion on how to manage my LG?

A log it's reported in the link below:
http://pastebin.com/fbac6657

Re: [BitPim-devel] Re-send: Re: Bug report - SMS Sent Items and Sanyo MM-7500

From: Stephen W. <bi...@gm...> - 2008-07-27 03:24:33

I have put in a patch to fix this, making the padding before the date
larger. The patch only applied to the SCP-7500.  If anyone has seen
this problem on other Sanyo phones, let me know.

Stephen

On Fri, Jul 25, 2008 at 5:47 PM, -= Delphicoder =-
<del...@ya...> wrote:
> I appreciate the quick response Stephen.  I have attached a text file
> containing the send and receive of the same message.  I believe the problem
> lies in offset "00000110", as you will notice that the data is offset by 1
> to the right on the second set of data.
>

[BitPim-devel] Re-send: Re: Bug report - SMS Sent Items and Sanyo MM-7500

From: -= D. =- <del...@ya...> - 2008-07-25 21:47:16

ÿþ1

Re: [BitPim-devel] Bug report - SMS Sent Items and Sanyo MM-7500

From: -= D. =- <del...@ya...> - 2008-07-25 18:38:15

ÿþ1

Re: [BitPim-devel] BitPim Test Release 1.0.6.20080724 available

From: Nathan H. <hj...@ma...> - 2008-07-25 16:57:59

Joe, when I sent those patched I didn't include any changes to the p_*.py files to make them easier to read. As a result none of the VX-8700/VX-8550/etc work with the test build. Forgot to mention to run protogen.py. Can you fix that and build a new test version?

-Nathan

On Thursday, July 24, 2008, at 08:16PM, "Joe Pham" <dj...@ne...> wrote:
>Grab it from:
>
><http://sourceforge.net/project/showfiles.php?group_id=75211&package_id=76673&release_id=615536>
>
>Changes in this release:
>
>***** Changes in 1.0.6 *****
>    * Bug fix: LG VX-8800/10000 Note Pad.
>    * Improvement: LG AX-8600 Call History and Note Pad (patch submitted by
>      David Ritter).
>    * Bug fix: LG VX-8500/8800/10000: better BREW file access (i.e. fewer "file
>      block" errors).
>    * Bug fix: LG VX-9900: access to the mmc1 dir via Command Line Interface
>      (CLI).
>    * Bug fix: Motorola: BitPim failed to read phonebook from some Motorola
>      models.
>    * Improvement: Call History: Navigate to other subtrees.
>    * Bug fix: SCP-6650: Fix Katana-II phone/port detection
>    * Add "extrazero" fields to listfile and listdirectory responses so that
>      filesystem view will work for Samsung SPHA-900. May break filesystem view
>      for other phones.
>    * New phone support: Sanyo SCP-8400
>    * New phone support: LG VX-9100 (enV2) (Initial)
>    * Bug fix: Can't view Data Recording files on non-Intel Mac.
>    * Bug fix: Correctly process BREW special files.
>    * New phone support: LG VX-8560 (Initial)
>    * New Phone support: LG VX-9700 (Initial)
>    * New Phone support: LG VX-8610 (Initial)
>    * Bug fix: LG VX-9900 SMS support.
>
>
>-Joe Pham
>
>____________________________________________________________
>Click here to find Medical Transcription Training programs.
>http://thirdpartyoffers.netzero.net/TGL2231/fc/Ioyw6ijmaKOcsSstd3WH1MjhkGCuw251khKsLoVXgrzVGne34F4oKo/
>
>-------------------------------------------------------------------------
>This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
>Build the coolest Linux based applications with Moblin SDK & win great prizes
>Grand prize is a trip for two to an Open Source event anywhere in the world
>http://moblin-contest.org/redirect.php?banner_id=100&url=/
>_______________________________________________
>BitPim-devel mailing list
>Bit...@li...
>https://lists.sourceforge.net/lists/listinfo/bitpim-devel
>
>

[BitPim-devel] BitPim Test Release 1.0.6.20080724 available

From: Joe P. <dj...@ne...> - 2008-07-25 02:15:52

Grab it from:

<http://sourceforge.net/project/showfiles.php?group_id=75211&package_id=76673&release_id=615536>

Changes in this release:

***** Changes in 1.0.6 *****
    * Bug fix: LG VX-8800/10000 Note Pad.
    * Improvement: LG AX-8600 Call History and Note Pad (patch submitted by
      David Ritter).
    * Bug fix: LG VX-8500/8800/10000: better BREW file access (i.e. fewer "file
      block" errors).
    * Bug fix: LG VX-9900: access to the mmc1 dir via Command Line Interface
      (CLI).
    * Bug fix: Motorola: BitPim failed to read phonebook from some Motorola
      models.
    * Improvement: Call History: Navigate to other subtrees.
    * Bug fix: SCP-6650: Fix Katana-II phone/port detection
    * Add "extrazero" fields to listfile and listdirectory responses so that
      filesystem view will work for Samsung SPHA-900. May break filesystem view
      for other phones.
    * New phone support: Sanyo SCP-8400
    * New phone support: LG VX-9100 (enV2) (Initial)
    * Bug fix: Can't view Data Recording files on non-Intel Mac.
    * Bug fix: Correctly process BREW special files.
    * New phone support: LG VX-8560 (Initial)
    * New Phone support: LG VX-9700 (Initial)
    * New Phone support: LG VX-8610 (Initial)
    * Bug fix: LG VX-9900 SMS support.


-Joe Pham

____________________________________________________________
Click here to find Medical Transcription Training programs.
http://thirdpartyoffers.netzero.net/TGL2231/fc/Ioyw6ijmaKOcsSstd3WH1MjhkGCuw251khKsLoVXgrzVGne34F4oKo/

Re: [BitPim-devel] Bug report - SMS Sent Items and Sanyo MM-7500

From: Stephen W. <bi...@gm...> - 2008-07-24 03:15:21

Delphicoder:

Could you send me (privately is fine), a bigger extract from the
protocol log, either the whole thing, or enough to include several
Sent and Received text messages.

Thanks, Stephen

On Tue, Jul 22, 2008 at 4:08 PM, -= Delphicoder =-
<del...@ya...> wrote:
> Devs:
>
> Versions used during testing:  1.0.5 Stable and 1.0.6.2008.07.07
>
> I recently activated a Sanyo MM-7500 after testing the functionalities with
> BitPim.   The tests seemed to work as expected (ie. Phonebook transfer and
> SMS).  The only thing that I noticed is a problem is the way BitPim is
> reading messages from the SMS 'Sent' folder.  The message is properly
> formatted, but the DATE/TIME are off.  They're 'right shifted' to be exact.
>
> Currently, the data posted below should read:
>
> ** Note ** - Phone number changed to zeros in example and data log provided
> below
>
> Callback #: (000) 000-0000
> Date: 2008-07-21 16:27
>
> Instead, it reads:
>
> Callback #: <Blank>  <---  Nothing displayed
> Date: 2000-08-07 21:16:27   <-- Notice the right shifting of the data
>
> In the list of messages, the phone number is displayed correctly, but is
> preceded by a square (ie. more than likely the 0A, or carriage return found
> in the data location immediately before the phone number)
>
> I would greatly appreciate your assistance on this.  I look forward to
> testing out the bug fix.
>
> Thanks goes to Joe Pham, the rest of the developing crew and those that have
> contributed patches and bug reports in the past to keep this project going.
> Good work!!!
>
>
> Actual data below:
>
> "00000000 fa 00 02 e1 0c 00 11 01 00 00 00 81 18 3c 00 02
> .............<..
> 00000010 01 00 3b 54 68 69 73 20 20 69 73 20 61 20 74 65     ..;This  is a
> te
> 00000020 73 74 20 6d 65 73 73 61 67 65 20 66 72 6f 6d 20     st message from
> 00000030 74 68 65 20 72 65 63 65 6e 74 6c 79 20 61 63 74     the recently
> act
> 00000040 69 76 61 74 65 64 20 70 68 6f 6e 65 2e 20 00 00     ivated phone.
> ..
> 00000050 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> ................
> 00000060 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> ................
> 00000070 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> ................
> 00000080 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> ................
> 00000090 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> ................
> 000000a0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> ................
> 000000b0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> ................
> 000000c0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> ................
> 000000d0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> ................
> 000000e0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> ................
> 000000f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> ................
> 00000100 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> ................
> 00000110 00 00 00 08 07 15 10 1b 31 0a 30 30 30 30 30 30
> ........1.000000
> 00000120 30 30 30 30 00 00 00 00 00 00 00 00 00 00 00 00
> 0000............
> 00000130 00 00 00 00 00 00 00 00 00 00 00 00 0a 30 30 30
> .............000
> 00000140 30 30 30 30 30 30 30 00 00 00 00 00 00 00 00 00
> 0000000.........
> 00000150 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> ................
> 00000160 00 00 00 64 00 00 00 01 00 00 00 00 00 00 00 00
> ...d............
> 00000170 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> ................
>
>
>
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great
> prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> BitPim-devel mailing list
> Bit...@li...
> https://lists.sourceforge.net/lists/listinfo/bitpim-devel
>
>

Re: [BitPim-devel] LG Dare (VX-9700) Support

From: Nathan H. <hj...@ma...> - 2008-07-23 04:13:44

Dare support is already complete. Check the latest svn code for Dare support.

-Nathan Hjelm
 
On Tuesday, July 22, 2008, at 09:53PM, "Andrew Rosca" <an...@ro...> wrote:
>Hello,
> 
>I would like to help with VX9700 development. I just bought one and I am a
>developer myself. I am not sure if work isn't already in progress though so
>I'm looking for some feedback from you guys.
> 
>BitPim supports VX9700 partially with the VX9100 profile. I guess the only
>additional development necessary is proper device detection (it is currently
>detected as Other CDMA, which annoying because you have to set the phone
>type manually every time you use BitPim) and support for Media, Ringtones,
>etc.
> 
>If you are already working on VX9700 please get back to me so I don't do
>duplicate work, or if you would like help. If not, please let me know who I
>can coordinate with to get started on it.
> 
>Thanks!
>

[BitPim-devel] Source Download Problem

From: <ben...@mt...> - 2008-07-23 04:07:01

Hi, just starting to work with this. Hope to be able to contribute.
Haven't worked in python yet, but anyway, that's not the issue.

I am not familiar with Subversion or how to use it, but when I tried
clicking the HTML version link it does not load.  Is there another way to
get the source. I am on vista (laptop) but I will be putting back together
a Fedora machine and have access to linux based labs if that is
recommended.

Thanks,
Ben

Re: [BitPim-devel] LG VX-9100 Support

From: Nathan H. <hj...@ma...> - 2008-07-22 21:17:24

Attachments: chocolate_dare.patch

>>backup_perms.diff         - set permissions of files in a backup  
>
>What issue does this patch fix and on what platform?

On OSX (and any other UNIX platform) when a backup zip is expanded all files have no access permissions (---------) which forces the user to chmod the files before they can be read or modified. The patch sets the file permissions to rw------- so the file owner will have read and write permissions. As I said in an earlier email it might be a good idea to set the file permissions based off what they are on the phone so that Bitpim can eventually preserve permissions on a backup.

>All other patches have been committed.  Please verify them before we build the next test release.  For now, I'd prefer to keep the VX9100 code intact so I can continue working on them w/o affecting other models.

Attached is a diff adding call history support to the Dare and bypassing the VX-9100's prototypes on the VX-8560 and VX-9700 for everything but SMS. The VX-9100 phonenumber prototype doesn't define the malformed() method at the moment. Everything else looks good and I will verify then when I get home.

-Nathan

[BitPim-devel] Bug report - SMS Sent Items and Sanyo MM-7500

From: -= D. =- <del...@ya...> - 2008-07-22 20:08:32

Devs:

Versions used during testing:  1.0.5 Stable and 1.0.6.2008.07.07

I recently activated a Sanyo MM-7500 after testing the functionalities with BitPim.   The tests seemed to work as expected (ie. Phonebook transfer and SMS).  The only thing that I noticed is a problem is the way BitPim is reading messages from the SMS 'Sent' folder.  The message is properly formatted, but the DATE/TIME are off.  They're 'right shifted' to be exact.

Currently, the data posted below should read:

** Note ** - Phone number changed to zeros in example and data log provided below

Callback #: (000) 000-0000
Date: 2008-07-21 16:27

Instead, it reads:

Callback #: <Blank>  <---  Nothing displayed

Date: 2000-08-07 21:16:27   <-- Notice the right shifting of the data 

In the list of messages, the phone number is displayed correctly, but is preceded by a square (ie. more than likely the 0A, or carriage return found in the data location immediately before the phone number)

I would greatly appreciate your assistance on this.  I look forward to testing out the bug fix.

Thanks goes to Joe Pham, the rest of the developing crew and those that have contributed patches and bug reports in the past to keep this project going.  Good work!!!


Actual data below:

"00000000 fa 00 02 e1 0c 00 11 01 00 00 00 81 18 3c 00 02     .............<..
00000010 01 00 3b 54 68 69 73 20 20 69 73 20 61 20 74 65     ..;This  is a te
00000020 73 74 20 6d 65 73 73 61 67 65 20 66 72 6f 6d 20     st message from 
00000030 74 68 65 20 72 65 63 65 6e 74 6c 79 20 61 63 74     the recently act
00000040 69 76 61 74 65 64 20 70 68 6f 6e 65 2e 20 00 00     ivated phone. ..
00000050 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00     ................
00000060 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00     ................
00000070 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00     ................
00000080 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00     ................
00000090 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00     ................
000000a0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00     ................
000000b0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00     ................
000000c0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00     ................
000000d0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00     ................
000000e0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00     ................
000000f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00     ................
00000100 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00     ................
00000110 00 00 00 08 07 15 10 1b 31 0a 30 30 30 30 30 30     ........1.000000
00000120 30 30 30 30 00 00 00 00 00 00 00 00 00 00 00 00     0000............
00000130 00 00 00 00 00 00 00 00 00 00 00 00 0a 30 30 30     .............000
00000140 30 30 30 30 30 30 30 00 00 00 00 00 00 00 00 00     0000000.........
00000150 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00     ................
00000160 00 00 00 64 00 00 00 01 00 00 00 00 00 00 00 00     ...d............
00000170 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00     ................

Re: [BitPim-devel] LG VX-9100 Support

From: Joe P. <dj...@ne...> - 2008-07-22 19:57:59

>backup_perms.diff         - set permissions of files in a backup  

What issue does this patch fix and on what platform?

All other patches have been committed.  Please verify them before we build the next test release.  For now, I'd prefer to keep the VX9100 code intact so I can continue working on them w/o affecting other models.

-Joe Pham



____________________________________________________________
Click here to find affordable degree programs. 
http://thirdpartyoffers.netzero.net/TGL2231/fc/Ioyw6ijlTK4wb9jp8Jhh2ghotqf3ZuLGZlUvhvPkOnDD2mgOXy4Uh2/

[BitPim-devel] LG Dare (VX-9700) Support

From: Andrew R. <an...@ro...> - 2008-07-22 17:41:03

Hello,
 
I would like to help with VX9700 development. I just bought one and I am a
developer myself. I am not sure if work isn't already in progress though so
I'm looking for some feedback from you guys.
 
BitPim supports VX9700 partially with the VX9100 profile. I guess the only
additional development necessary is proper device detection (it is currently
detected as Other CDMA, which annoying because you have to set the phone
type manually every time you use BitPim) and support for Media, Ringtones,
etc.
 
If you are already working on VX9700 please get back to me so I don't do
duplicate work, or if you would like help. If not, please let me know who I
can coordinate with to get started on it.
 
Thanks!

107 messages has been excluded from this view by a project administrator.

Flat | Threaded

<< < 1 .. 12 13 14 15 16 .. 265 > >> (Page 14 of 265)