Re: [QtMoko] intermittent USB networking + non-working WLAN = must use wired LAN = USB port hardware problem

2010-03-04 Thread Brolin Empey
Radek Polak wrote: On Monday 01 March 2010 04:16:22 Brolin Empey wrote: Does anyone use USB networking with their FreeRunner with Windows Vista or Windows 7? I had it working with XP. That does not matter to me because I do not use Windows XP any more. But now i switched all my machines

Re: [QtMoko] intermittent USB networking + non-working WLAN = must use wired LAN = USB port hardware problem

2010-03-01 Thread Radek Polak
On Monday 01 March 2010 04:16:22 Brolin Empey wrote: Does anyone use USB networking with their FreeRunner with Windows Vista or Windows 7? I had it working with XP. But now i switched all my machines (even at work) to linux. I think i left preinstalled win 7 on my notebook so i can try at

Re: [QtMoko] intermittent USB networking + non-working WLAN = must use wired LAN = USB port hardware problem

2010-03-01 Thread Dave
Hi Using qtmoko V16, I have found that suspending using the power button or waking by plugging in the charger guarantee that bluetooth is killed. If I allow the phone to suspend through timeout settings or wake the phone before attaching to a charge/usb source then bluetooth remains good for

Re: [QtMoko] intermittent USB networking + non-working WLAN = must use wired LAN = USB port hardware problem

2010-03-01 Thread Paul Fertser
Dave dave...@gmail.com writes: Using qtmoko V16, I have found that suspending using the power button or waking by plugging in the charger guarantee that bluetooth is killed. And what do you mean by killed? Does BT adapter disappear from lsusb list? Or does bluetoothd get confused by something?

[QtMoko] intermittent USB networking + non-working WLAN = must use wired LAN = USB port hardware problem

2010-02-28 Thread Brolin Empey
Hello FreeRunners, I am still using QtMoko v14 in onboard NAND on my US GTA02A6. I know v16 is old by now, but I am not upgrading because it is a huge hassle. I already upgraded from v11 to v14 months ago; I do not want to repeat that hassle. I will have even more to do after upgrading from