<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.16.1">
</HEAD>
<BODY>
I am using my Neo (latest Qtopia image) since about 10 days as my primary business phone. I am a quality engineer of automobile industry and the main problems I have before deeper testing, is that the Neo will not establish a bluetooth connection with the handsfree system of common automobile bluetooth units (OEM). Further more I haven't found a seperate charger for the Neo. I charge it at home with my Linux-machine and during work the battery get's flat after about 4 hours using it. My windows-business-machine won't load the battery, which means I have to wait until the next day. Is there somebody out there, who can give me an advice which wall-plug-charger I have to buy and secondly which car-charger I have to buy?<BR>
<BR>
Kind Regards<BR>
<BR>
Ralf<BR>
<BR>
Am Mittwoch, den 20.02.2008, 19:48 +0100 schrieb Tilman Baumann:
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000">Joe Pfeiffer wrote:</FONT>
<FONT COLOR="#000000">> Tilman Baumann writes:</FONT>
<FONT COLOR="#000000">>> Hm. I never tried Windows. But this does not make much sense to me.</FONT>
<FONT COLOR="#000000">>> The Os just has to select a device configuration to allow it to draw </FONT>
<FONT COLOR="#000000">>> power. This does not mean it has to have a driver for it.</FONT>
<FONT COLOR="#000000">>> I'm pretty much sure my linux server which i sometimes use for charging </FONT>
<FONT COLOR="#000000">>> does not have any driver whatsoever for this device. But it charges nicely.</FONT>
<FONT COLOR="#000000">>></FONT>
<FONT COLOR="#000000">>> Strange. But however, it is windows...</FONT>
<FONT COLOR="#000000">> </FONT>
<FONT COLOR="#000000">> I don't know anything about Windows, but -- the problem with not</FONT>
<FONT COLOR="#000000">> charging on dumb cords is that the NEO is polite about needing to</FONT>
<FONT COLOR="#000000">> handshake, and being able to request 500mA, before it will draw</FONT>
<FONT COLOR="#000000">> 500mA. If the device on the other end doesn't even do that, the NEO</FONT>
<FONT COLOR="#000000">> will only draw 100mA which isn't enough (the fast_cccv parameter</FONT>
<FONT COLOR="#000000">> somebody else mentioned will, apparently, force it to draw lots of</FONT>
<FONT COLOR="#000000">> power anyway).</FONT>
<FONT COLOR="#000000">I know. But selecting a device configuration (allowing the device to go </FONT>
<FONT COLOR="#000000">into a status that consumes more than 10mA) has nothing to do with </FONT>
<FONT COLOR="#000000">drivers or anything like that.</FONT>
<FONT COLOR="#000000">At least not necessarily.</FONT>
<FONT COLOR="#000000">Any USB device just offers the host one or many possible device </FONT>
<FONT COLOR="#000000">configurations (descriptors) with they respective power consumtion </FONT>
<FONT COLOR="#000000">profiles when it is plugged in.</FONT>
<FONT COLOR="#000000">The next step for the host (operating system) is to select one of these </FONT>
<FONT COLOR="#000000">configurations to allow the device to go in this mode.</FONT>
<FONT COLOR="#000000">The os does not need to now what a device does, in order to allow it to </FONT>
<FONT COLOR="#000000">do anything.</FONT>
<FONT COLOR="#000000">I'm really surprised and not entirely convinced that windows does not </FONT>
<FONT COLOR="#000000">select a profile on any unknown device.</FONT>
<FONT COLOR="#000000">A mobile phone would be not the only situation where this behaviour </FONT>
<FONT COLOR="#000000">seems like a bad idea.</FONT>
<FONT COLOR="#000000">Regards</FONT>
<FONT COLOR="#000000"> Tilman</FONT>
</PRE>
</BLOCKQUOTE>
</BODY>
</HTML>