Menu
▾
▴
bitpim-devel
|
From: Stephen W. <sa...@us...> - 2004-01-09 02:12:18
|
I have gotten some feedback on the Sanyo phone support from sprintusers and howardforums readers who have tried BitPim 0.7test1. 1. Several windows users got stuck initially because BitPim didn't auto detect their phone and they didn't know what to do. I can add some notes to the help, but is there anything else that can be done help users here? (On my XP system, the port browser shows COM1 and COM2, but my phone is know to windows as a modem on COM4.) 2. A MacOS user was successfull using BitPim with an 8100. 3. While it is explained in the help that media are not supported for the Sanyo phones, that is not clear from the application itself. A user tried to download wallpaper and ringtones from his 4900 and got a python error. Is there a way I can pop up an error, or can the wallpaper/ringer items in the get and send be disabled when they are not supported. 4. A user reported success with the phonebook for the SCP-7200. The 7200 is a newer Sprint Readylink (push to talk) phone. He also reported that he got an error when trying to download the calendar. Unfortunately, I have not be able to get a more descriptive error report than that yet. But this gives hope to my suspicion that it will be easy for BitPim to support at least the phonebook for most of Sanyo's phones. I have tried to encourage people to report the experience on bitpim-user, but I think without too much success. Steve |
|
From: Roger B. <ro...@ro...> - 2004-01-09 06:08:39
|
> 1. Several windows users got stuck initially because BitPim didn't auto
> detect their phone and they didn't know what to do. I can add some
> notes to the help, but is there anything else that can be done help
> users here? (On my XP system, the port browser shows COM1 and COM2, but
> my phone is know to windows as a modem on COM4.)
Currently on Windows it only lists serial ports, not modems. I did
experiment with a one line change and the modems are detected as
well. However the modem is the wrong thing to pick for the LG phones.
The correct fix will be:
- In the listing of ports, add in a 'class' that shows if the
port is a com port or a modem
- In the code that selects the device, it should pay attention
to the class
> 3. While it is explained in the help that media are not supported for
> the Sanyo phones, that is not clear from the application itself. A user
> tried to download wallpaper and ringtones from his 4900 and got a python
> error. Is there a way I can pop up an error, or can the
> wallpaper/ringer items in the get and send be disabled when they are not
> supported.
My intention was to have the wallpaper/ringtone panes removed if the
currently selected phone didn't support it. It is actually going to
be considerably easier to just disable them, and the relevant portion
of the get/send dialogs. (I currently detest the get/send dialog
so if you want to make something better, please volunteer or make
a suggested screenshot). The per phone profile will then contain
information about what features the phone/bitpim supports.
> I have not be able to get a more descriptive error report
> than that yet.
I have had a few of those :-) I did update the help for support
and now just point people at that.
http://bitpim.sourceforge.net/testhelp/support.htm
> I have tried to encourage people to report the experience on
> bitpim-user, but I think without too much success.
Yup, I have the same problem. I get very impressed by the non-LG
people who mail me at the SourceForge address as well as the
address from the vx4400 FAQ on my website.
These things just take time, and will correct themselves with
enough gentle persuasion. I always make sure I deal with stuff
on the bitpim groups first, and give more detailed and helpful
answers there. Often I refuse to answer stuff in personal email
unless they post to the lists. (If I am going to use my time
to answer stuff, it is way more beneficial for all involved
that everyone sees the answers, and can comment on the original
question and issues).
I will make an effort to fix both 1 & 3 before the next test
release (I would like to do them every two weeks or so).
However I may be out of action for up to a week. I am having
some "oral surgery" (it sounds really wierd to me) to correct
some British dentistry.
Roger
|
|
From: Roger B. <ro...@ro...> - 2004-01-11 10:07:50
|
> 1. Several windows users got stuck initially because BitPim didn't auto > detect their phone and they didn't know what to do. I can add some > notes to the help, but is there anything else that can be done help > users here? (On my XP system, the port browser shows COM1 and COM2, but > my phone is know to windows as a modem on COM4.) I have now implemented the fix for this. ports now have a "class" field which is "serial" or "modem". (The LG phones are on serial, the Sanyo on modem). The usb information is now in the profile for each phone class. I put the sanyo entry into com_sanyo, so you will need to update that if it differs by model. Steven, can you please update the comscanmac function in comscan.py to note if the device is a serial or modem. I think the Mac uses /dev/cu.usbserial and /dev/cu.usbmodem respectively. res["class"] should be set the the right value in the loop. Roger |
|
From: Stephen W. <sa...@us...> - 2004-01-12 02:58:53
|
On Sun, 2004-01-11 at 05:07, Roger Binns wrote: > The usb information is now in the profile for each phone class. I put > the sanyo entry into com_sanyo, so you will need to update that if > it differs by model. Will the usbids in com_sanyo.py prevent a phone with different ID's from working? If so, I should move the usbids to the 4900 specific code and leave it blank for phones that I don't know the id's for. Could one of the SCP-8100 owners get the USB id's for that phone. Also, if there is anyone with a different Sanyo phone (5300 or the new readylink or video phones), could you also post your USB ids along with your phone model. Steve |
|
From: Roger B. <ro...@ro...> - 2004-01-12 06:31:28
|
> Will the usbids in com_sanyo.py prevent a phone with different ID's from > working? They won't be selected as part of auto guessing and they won't have a (*) next to them in the com port browser. > If so, I should move the usbids to the 4900 specific code and > leave it blank for phones that I don't know the id's for. Yup. The LG uses the same vid/pid for the 4400 and 6000. I haven't heard from anyone with other models. If any of the phones use usb to serial cables, you will need their vid/pid in there as well. Roger |
|
From: Steven P. <n9...@n9...> - 2004-01-12 03:38:50
|
On Jan 11, 2004, at 4:07 AM, Roger Binns wrote:
> Steven, can you please update the comscanmac function in comscan.py
> to note if the device is a serial or modem. I think the Mac uses
> /dev/cu.usbserial and /dev/cu.usbmodem respectively. res["class"]
> should be set the the right value in the loop.
I'm not sure if it is that simple... Maybe it is for the
drivers/cables commonly used for cell phones, but, for example, the
very popular USB<-->Serial adapters made by KeySpan show up like this:
- /dev/tty.KeyUSA28X<geo>1 -- or -- /dev/cu.KeyUSA28X<geo>1
- /dev/tty.KeyUSA28X<geo>2 -- or -- /dev/cu.KeyUSA28X<geo>2
where <geo> is the 2 or more digit geographical name. (e.g. "913"
means USB bus #9, host hub port #1 and external hub port #3)
I did find a reference to the Prolific chipset and the driver they
have for MacOS X does, as far as I can tell, use usbserial.
Since this is so arbitrary, depending on the vendor's driver and
choice of text string they use when constructing the name, I'd hesitate
to code to it, it's not quite a standard. However, if there is a choice
that must be made to make things work properly I guess we can just punt
and hope for the best.
-. ----. -.-- - -.--
Steve Palm - n9...@n9...
-. ----. -.-- - -.--
|
|
From: Roger B. <ro...@ro...> - 2004-01-12 07:13:01
|
> Since this is so arbitrary, depending on the vendor's driver and > choice of text string they use when constructing the name, I'd hesitate > to code to it, it's not quite a standard. However, if there is a choice > that must be made to make things work properly I guess we can just punt > and hope for the best. Generally mark everything as serial unless you know it is a modem. The Sanyo phones are only modem. The LG should present a modem and a serial interface, and they should be marked as such (so the autodetect code picks/excludes the right thing). Roger |
|
From: Steven P. <n9...@n9...> - 2004-01-12 16:32:51
|
On Jan 12, 2004, at 1:13 AM, Roger Binns wrote: > Generally mark everything as serial unless you know it is a modem. > > The Sanyo phones are only modem. The LG should present a modem and a > serial interface, and they should be marked as such (so the autodetect > code picks/excludes the right thing). Maybe we're not on the same page here.... When I'm just scanning a list of devices that exist in the /dev filesystem, how am I to know what is or is not a modem or serial interface? That was my question. I can't be assured that the chosen string by the vendor will be representative of the actual use of the device. The LG phone on my creates a /dev/cu.usbmodemXXX and a /dev/tty.usbmodemXXX entry. There is no "serial" interface created as such. Now, in the case of the KeySpan adapter (which you may have connected and have found some way to plug your phone in to this using some serial adapter cable combination), I have no idea what it is. At any rate, what logic are you using on Linux and/or Windows to know this information? Are you just guessing as well, or does the system present more concrete information to you? How would the system tell me that it *is* a modem so I would know it's not serial? Sorry for the ignorance here, but I'm missing something. -. ----. -.-- - -.-- Steve Palm - n9...@n9... -. ----. -.-- - -.-- |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X