On Tue, Oct 30, 2007 at 09:10:12PM +0900, Michal Čihař wrote: > Dne Tue, 30 Oct 2007 12:25:19 +0100 > Florian Lohoff <[EMAIL PROTECTED]> napsal(a): > > > Wammu should really have a phone database and possibly detect the > > possible connection methods e.g. serial, irda, bluetooth on first > > startup and then let the user select the phone (or autodetect) and the > > connection method. Wammu should then select the correct protocol by > > itself. > > This is basically what guided configuration does, have you tried that? > It should be probably a bit more advertised ... any idea?
Hmm - Okay - had a quick look - very confusing.
The automatic then worked although the search output in the text
windows is more than confusing - I just want to know what was found,
and it didnt find the bluetooth device in the first run ...
Using the guided -
Bluetooth -> Nokia and then i get the question
"AT based"
"Nokia FBUS"
"OBEX based"
What Aunt Tilly does not have a clue about. I would expect some
kind of Microsoft Vendor Driver selector where ony selects the Vendor
and then the Type.
When selecting "Siemens" "S25" i get asked "Serial or IRDA" because
it does not have bluetooth.
When selecting "Nokia" "6230(i)" i get Bluetooth, Serial or IRDA
to select. I dont care about the protocol the mobile supports
on the different communication channels - I know the phone - its in my
hand and most likely i have an idea about which communication channel
to use but not the protocol the device supports.
BTW: For example on the "Connection test" screen one cant click
next until the test finished. Why not make the next button
grey thats its clearly not allowed to press yet.
Flo
--
Florian Lohoff [EMAIL PROTECTED] +49-171-2280134
Those who would give up a little freedom to get a little
security shall soon have neither - Benjamin Franklin
signature.asc
Description: Digital signature
