[prev in list] [next in list] [prev in thread] [next in thread]
List: bitpim-devel
Subject: Re: [BitPim-devel] Questions regarding support for LG VX-5400
From: MBR <mbr () arlsoft ! com>
Date: 2009-01-31 19:09:50
Message-ID: 4984A1FE.2050207 () arlsoft ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Thanks a lot for your quick response.
I just found the page at http://www.bitpim.org/help/versionhistory.htm,
which shows the following:
LG VX-5400
Ver. 1.0.3 New phone support
Ver. 1.0.4 Bug fix: display wrong caller ID number.
LG VX-8610
Ver. 1.0.6 New Phone support
Your email was explicit that I should use "the most recent test build of
Bitpim," which would be Release 1.0.7.20081215, but the change list for
that release at
http://sourceforge.net/project/shownotes.php?group_id=75211&release_id=648738
<http://sourceforge.net/project/shownotes.php?group_id=75211&release_id=648738>,
doesn't mention any changes that would affect either the LG VX-5400 or
the LG VX-8610.
Are there changes relevant to the 8610 or the 5400 that aren't listed at
http://sourceforge.net/project/shownotes.php?group_id=75211&release_id=648738
<http://sourceforge.net/project/shownotes.php?group_id=75211&release_id=648738>?
If not, wouldn't I be better off using the stable version (1.0.6) rather
than the test version (1.0.7.20081215)?
Mark <http://www.bitpim.org/#download>
Sean Patrick Burke wrote:
> The 8610 and 5400 are both supported by the most recent test build of
> Bitpim. If the phones support a bluetooth connection, then you
> should probably be able to connect to them.
>
> Hope this helps,
>
> Sean
> --
> Sean Patrick Burke
> Full time law student, part time developer
> http://www.bitpim.org
>
>
>
>
> On Jan 30, 2009, at 2:49 PM, MBR wrote:
>
>> I just looked for the LG VX-5400 in the navigation tree at
>> http://www.bitpim.org/help, and couldn't find it listed. But a
>> series of emails in this group from 11/18/2007 (Subject: Newly
>> released VX5400 appears to be similar to Bitpim's LG-VX8550) through
>> 1/7/2008 (Subject: VX5400 /pim/pbnumber.dat caller-id lookup problem)
>> seem to indicate that work was being done on this model, and that it
>> was similar to the VX-8550. http://www.bitpim.org/help warns:
>>
>> *My phone is not in the list*
>>
>> You should select your exact phone in the list, ...
>>
>> Picking "similar" phones means you are experimenting and
>> could end up with problems such as your phone locking up with
>> a worst case of it becoming completely inoperable.
>>
>> So I don't want to try a similar but not identical model number. And
>> I don't know what to infer from the fact that neither the LG VX-5400
>> nor the LG VX-8550 is listed at http://www.bitpim.org/help.
>>
>> It could mean that the development discussed in the aforementioned
>> series of emails was abandoned because someone decided the phone
>> simply couldn't be properly supported. Or it could mean that those
>> models are supported but nobody ever got around to writing the
>> documentation.
>>
>> Does anyone know whether I can safely use BitPim with an LG VX-5400?
>> If so, does it know the phone by that name, by the name VX-8550, or what?
>>
>> Mark Rosenthal
>> mbr@arlsoft.com <mailto:mbr@arlsoft.com>
>>
>>
>> -------- Original Message --------
>> Subject: Re: [BitPim-devel] VX5400 /pim/pbnumber.dat caller-id
>> lookup problem
>> Date: Tue, 8 Jan 2008 00:04:52 GMT
>> From: Joe Pham <djpham@netzero.com>
>> Reply-To: bitpim-devel@lists.sourceforge.net
>> To: bitpim-devel@lists.sourceforge.net
>>
>>
>>
>> >caller-id lookup on the VX5400 with Bitpim version 1.04 official is
>> >now working correctly.
>>
>> Thanks for the testing and the feedback.
>>
>> -Joe Pham
>>
>>
>> ------------------------------------------------------------------------------
>> This SF.net email is sponsored by:
>> SourcForge Community
>> SourceForge wants to tell your story.
>> http://p.sf.net/sfu/sf-spreadtheword_______________________________________________
>> BitPim-devel mailing list
>> BitPim-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/bitpim-devel
>
> ------------------------------------------------------------------------
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by:
> SourcForge Community
> SourceForge wants to tell your story.
> http://p.sf.net/sfu/sf-spreadtheword
> ------------------------------------------------------------------------
>
> _______________________________________________
> BitPim-devel mailing list
> BitPim-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitpim-devel
>
[Attachment #5 (text/html)]
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
<font face="Times New Roman, Times, serif">Thanks a lot for your quick
response.<br>
<br>
</font>I just found the page at <a
href="http://www.bitpim.org/help/versionhistory.htm">http://www.bitpim.org/help/versionhistory.htm</a><font
face="Times New Roman, Times, serif">, which shows the following:<br>
</font>
<blockquote><font face="Times New Roman, Times, serif">LG VX-5400</font><br>
<blockquote><font face="Times New Roman, Times, serif">Ver. 1.0.3 \
</font><font face="Times New Roman, Times, serif">New phone support</font><br>
<font face="Times New Roman, Times, serif">Ver. 1.0.4 Bug fix:
display wrong caller ID number.</font><br>
</blockquote>
<font face="Times New Roman, Times, serif">LG VX-8610</font><br>
<blockquote><font face="Times New Roman, Times, serif">Ver. 1.0.6
New Phone support</font><br>
</blockquote>
</blockquote>
<font face="Times New Roman, Times, serif">Your email was explicit that
I should use </font><font face="Times New Roman, Times, serif">"</font>the
most recent test build of Bitpim," which would be Release
1.0.7.20081215, but the change list for that release at <a
href="http://sourceforge.net/project/shownotes.php?group_id=75211&release_id=6487 \
38">http://sourceforge.net/project/shownotes.php?group_id=75211&release_id=648738</a>,
doesn't mention any changes that would affect either the LG VX-5400 or
the LG VX-8610.<br>
<br>
<font face="Times New Roman, Times, serif">Are there changes relevant
to the 8610 or the 5400 that aren't listed </font>at <a
href="http://sourceforge.net/project/shownotes.php?group_id=75211&release_id=6487 \
38">http://sourceforge.net/project/shownotes.php?group_id=75211&release_id=648738</a>?
<br>
<br>
If not, wouldn't I be better off using <font
face="Times New Roman, Times, serif">the stable version (1.0.6) rather
than </font><font face="Times New Roman, Times, serif">the test version</font>
(<font face="Times New Roman, Times, serif">1.0.7.20081215)?<br>
</font>
<blockquote><font face="Times New Roman, Times, serif">Mark</font><font
face="Times New Roman, Times, serif"><a
href="http://www.bitpim.org/#download"></a></font><br>
</blockquote>
Sean Patrick Burke wrote:
<blockquote cite="mid:B53AC772-AB6F-4FD8-B7B1-0EC8FE5E65E5@gmail.com"
type="cite">The 8610 and 5400 are both supported by the most recent
test build of Bitpim. If the phones support a bluetooth connection,
then you should probably be able to connect to them.
<div><br>
</div>
<div>Hope this helps,</div>
<div><br>
</div>
<div>Sean</div>
<div apple-content-edited="true"> <span class="Apple-style-span"
style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; \
font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; \
letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; \
text-transform: none; white-space: normal; widows: 2; word-spacing: 0px;"> <div \
style=""><span class="Apple-style-span" style="border-collapse: separate; color: \
rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; \
font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: \
normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; \
widows: 2; word-spacing: 0px;"> <div style="">
<div>--</div>
<div>Sean Patrick Burke</div>
<div>Full time law student, part time developer</div>
<div><a moz-do-not-send="true" \
href="http://www.bitpim.org">http://www.bitpim.org</a></div> <div><br>
</div>
</div>
</span><br class="Apple-interchange-newline">
</div>
</span><br class="Apple-interchange-newline">
</div>
<br>
<div>
<div>On Jan 30, 2009, at 2:49 PM, MBR wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">
<div bgcolor="#ffffff" text="#000000"> I just looked for the LG
VX-5400 in the navigation tree at <a moz-do-not-send="true"
href="http://www.bitpim.org/help">http://www.bitpim.org/help</a>, and
couldn't find it listed. But a series of emails in this group from
11/18/2007 (Subject: Newly released VX5400 appears to be similar to
Bitpim's LG-VX8550) through 1/7/2008 (Subject: VX5400 /pim/pbnumber.dat
caller-id lookup problem) seem to indicate that work was being done on
this model, and that it was similar to the VX-8550. <a
moz-do-not-send="true" \
href="http://www.bitpim.org/help">http://www.bitpim.org/help</a> warns:<br>
<blockquote>
<blockquote><b>My phone is not in the list</b><br>
<br>
You should select your exact phone in the list, ...<br>
<br>
Picking "similar" phones means you are experimenting and could end up
with problems such as your phone locking up with a worst case of it
becoming completely inoperable.<br>
</blockquote>
</blockquote>
So I don't want to try a similar but not identical model number. And I
don't know what to infer from the fact that neither the LG VX-5400 nor
the LG VX-8550 is listed at <a moz-do-not-send="true"
href="http://www.bitpim.org/help">http://www.bitpim.org/help</a>.<br>
<br>
It could mean that the development discussed in the aforementioned
series of emails was abandoned because someone decided the phone simply
couldn't be properly supported. Or it could mean that those models are
supported but nobody ever got around to writing the documentation.<br>
<br>
Does anyone know whether I can safely use BitPim with an LG VX-5400?
If so, does it know the phone by that name, by the name VX-8550, or
what?<br>
<blockquote>Mark Rosenthal<br>
<a moz-do-not-send="true" href="mailto:mbr@arlsoft.com">mbr@arlsoft.com</a><br>
</blockquote>
<br>
-------- Original Message --------
<table class="moz-email-headers-table" border="0" cellpadding="0"
cellspacing="0">
<tbody>
<tr>
<th align="right" nowrap="nowrap" valign="baseline">Subject: </th>
<td>Re: [BitPim-devel] VX5400 /pim/pbnumber.dat caller-id
lookup problem</td>
</tr>
<tr>
<th align="right" nowrap="nowrap" valign="baseline">Date: </th>
<td>Tue, 8 Jan 2008 00:04:52 GMT</td>
</tr>
<tr>
<th align="right" nowrap="nowrap" valign="baseline">From: </th>
<td>Joe Pham <a moz-do-not-send="true"
class="moz-txt-link-rfc2396E" \
href="mailto:djpham@netzero.com"><djpham@netzero.com></a></td> </tr>
<tr>
<th align="right" nowrap="nowrap" valign="baseline">Reply-To:
</th>
<td><a moz-do-not-send="true" class="moz-txt-link-abbreviated"
href="mailto:bitpim-devel@lists.sourceforge.net">bitpim-devel@lists.sourceforge.net</a></td>
</tr>
<tr>
<th align="right" nowrap="nowrap" valign="baseline">To: </th>
<td><a moz-do-not-send="true" class="moz-txt-link-abbreviated"
href="mailto:bitpim-devel@lists.sourceforge.net">bitpim-devel@lists.sourceforge.net</a></td>
</tr>
</tbody>
</table>
<br>
<br>
<pre>>caller-id lookup on the VX5400 with Bitpim version 1.04 official is
>now working correctly.
Thanks for the testing and the feedback.
-Joe Pham
</pre>
</div>
------------------------------------------------------------------------------<br>
This SF.net email is sponsored by:<br>
SourcForge Community<br>
SourceForge wants to tell your story.<br>
<a moz-do-not-send="true"
href="http://p.sf.net/sfu/sf-spreadtheword___________________________________________ \
____">http://p.sf.net/sfu/sf-spreadtheword_______________________________________________</a><br>
BitPim-devel mailing list<br>
<a class="moz-txt-link-abbreviated" \
href="mailto:BitPim-devel@lists.sourceforge.net">BitPim-devel@lists.sourceforge.net</a><br>
<a class="moz-txt-link-freetext" \
href="https://lists.sourceforge.net/lists/listinfo/bitpim-devel">https://lists.sourceforge.net/lists/listinfo/bitpim-devel</a><br>
</blockquote>
</div>
<br>
<pre wrap="">
<hr size="4" width="90%">
------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
<a class="moz-txt-link-freetext" \
href="http://p.sf.net/sfu/sf-spreadtheword">http://p.sf.net/sfu/sf-spreadtheword</a></pre>
<pre wrap="">
<hr size="4" width="90%">
_______________________________________________
BitPim-devel mailing list
<a class="moz-txt-link-abbreviated" \
href="mailto:BitPim-devel@lists.sourceforge.net">BitPim-devel@lists.sourceforge.net</a>
<a class="moz-txt-link-freetext" \
href="https://lists.sourceforge.net/lists/listinfo/bitpim-devel">https://lists.sourceforge.net/lists/listinfo/bitpim-devel</a>
</pre>
</blockquote>
</body>
</html>
------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
BitPim-devel mailing list
BitPim-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitpim-devel
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic