Closed/NoBug: Touchscreen is disabled until Bluetooth enables

[no-tec]

I'm in the same boat as skame, as I always cold boot when my car starts. It takes about twice as long for everything to start working since the bluetooth takes so long to connect. [Phone takes longer than the keyboard does]

[knightmare]

I "HAD" this problem a while back. Search for it, I'll also see if I can find it. Its got nothing to do with your touchscreen. I bet if you used a mouse on the screen and clicked something, CF would not respond. It's because the BT is trying to initialize, and until it does, CF will not do anything else.

I fixed it, don't recall how, let me try to find the thread.



HERE IT IS! ...


RC3 Bugs.


Basically, check your settings folders for bluetooth, contacts, cf, yada yada yada. Delete all that old crap, it prob got corrupt, and thigns will run much smoother if you start over.

I think that my contacts were screwed up, and that was causing bs to lag when coming out of hibernation.

Good luck.

[salvi]

Can you provide the path for such folder?

Remind u that this is an issue with the touch screen being disabled.

[Scott]

Originally Posted by skeme

I also have this problem on start up from fresh.

Until the bluetooth is sync as headset profile (all icons appear) the touch screen wont move

this is normal. cf will be unresponsive during the connection to the phone, because bluesoleil seems to hog all resources during the connection. It should not last more than 3-6 seconds though... How long does it take for you?

[Scott]

Originally Posted by no-tec

I'm in the same boat as skame, as I always cold boot when my car starts. It takes about twice as long for everything to start working since the bluetooth takes so long to connect. [Phone takes longer than the keyboard does]

longer than the keyboard does? i would think it would. Not sure what you mean though. How long doe bluetooth take to connect? (from the time the headset icon starts blinking, to the time it makes connection and headset/battery/signal icon is shown...)

[salvi]

This happens even if CF is not running. The touchscreen will not respond.

[Scott]

Originally Posted by salvi

This happens even if CF is not running. The touchscreen will not respond.

not in his case. he mentioned the phone connecting.

in your case -
how long is the delay before ts starts responding?. and what happened with first 2 suggestions? - 1. uninstall/resinstall touchscreen driver, and 2. increase resume delays .. ? Also a 3rd suggestion, uninstall Bluesoleil from Programs List, and re-install bluesoleil (just exit cf setup after bs install finishes)...

[salvi]

I would say this takes a good 10+ seconds or more.

I will give the first two suggestions a try during lunch

The uninstall/reinstall would have to wait till I get home from work.

[Scott]

sounds good, i will watch for your post

[no-tec]

Originally Posted by Scott

longer than the keyboard does? i would think it would. Not sure what you mean though. How long doe bluetooth take to connect? (from the time the headset icon starts blinking, to the time it makes connection and headset/battery/signal icon is shown...)

yeah the bt keyboard seems to connect right with startup of xp but i guess a phone is a little more complex so it should take longer. id say once cf is loaded [its normal boot time] 30 seconds later everything becomes responsive again. ive disabled the phone for now bc i dont have a headset to use with it so its not a big deal. let me reinstall the latest release and see if that fixes the issue [along with the other issues im having]