I have a handsfree Bluetooth kit in my car so that I can safely place calls while driving. This worked flawlessly with my previous Windows Mobile phones (Tilt/Tilt II). With the phone tucked in my pocket and the mobile OS ?locked? I could press the voice activation button on the dashboard and easily call someone. Not so with my shiny new AT&T Samsung Galaxy S II. Now I have to dig the phone out and unlock the device before I can use my handsfree system? are we back in the smartphone dark ages?? I might as well take up texting and driving while I?m at it and forget the handsfree unit altogether.
Apparently Google in their infinite wisdom has decided already paired Bluetooth devices pose a security risk. As such, when Android is ?locked? it disables any control from Bluetooth. I suppose if you work for the government or some place that you need Pentagon like security this makes sense. For the 95% of us that don?t need these draconian measures this is just plain stupid and potentially unsafe.
I?ve heard a few Android phones have a ?bluetooth bypass? option but apparently it?s rare (mine doesn?t have it) and I?ve read it doesn?t always work. I also can?t just disable locking since I connect to my work?s Exchange email which requires the device to have a PIN. And I shouldn?t have to throw away ALL security just to drive safely anyway.
I?d love to stick with Android and support a developer friendly platform but I?m not going to sacrifice usability and safety to do so. This issue is a deal breaker for me ? I?d be using an iPhone right now if I knew of this problem a few months ago. If it?s not solved I?ll be an iPhone user in about 8 months. This would be a shame since I don?t like Apple as a company, it?s too bad they seem to be the only ones who really get how people use technology.
If you know of a *real* solution to this problem I?d love to hear it. So far everything I?ve found out there goes unanswered (except for flames and other unconstructive replies) or states unrealistic answers (turn off security, stop making phone calls while driving, blah blah blah).
Apparently Google in their infinite wisdom has decided already paired Bluetooth devices pose a security risk. As such, when Android is ?locked? it disables any control from Bluetooth. I suppose if you work for the government or some place that you need Pentagon like security this makes sense. For the 95% of us that don?t need these draconian measures this is just plain stupid and potentially unsafe.
I?ve heard a few Android phones have a ?bluetooth bypass? option but apparently it?s rare (mine doesn?t have it) and I?ve read it doesn?t always work. I also can?t just disable locking since I connect to my work?s Exchange email which requires the device to have a PIN. And I shouldn?t have to throw away ALL security just to drive safely anyway.
I?d love to stick with Android and support a developer friendly platform but I?m not going to sacrifice usability and safety to do so. This issue is a deal breaker for me ? I?d be using an iPhone right now if I knew of this problem a few months ago. If it?s not solved I?ll be an iPhone user in about 8 months. This would be a shame since I don?t like Apple as a company, it?s too bad they seem to be the only ones who really get how people use technology.
If you know of a *real* solution to this problem I?d love to hear it. So far everything I?ve found out there goes unanswered (except for flames and other unconstructive replies) or states unrealistic answers (turn off security, stop making phone calls while driving, blah blah blah).