It is not fixed, although they have acknowledged the issue, but it seems like they might not be now. I will believe it when I see it. IMHO, the nav, as is currently, creates a dangerous situation. If I am moving and inputting a destination, I have to do it before I stop, because if I stop and the safety lock disengages, the input is lost. If I am using voice input at a stop and start driving, the input is lost because of the safety lock engaging. If I am entering voice at a stop, there is no reason that input should be interrupted when I start driving as voice input is allowed when driving. If I was programming this, it is pretty much a state based transition problem. It would be so easy to map it out with a grid and do it right. Oh well. I don't use the nav that much.
I just downloaded 10.851. I may have big news. I believe the hands free safety lock feature has been fixed. I ran a test. While stopped i pushed the on screen microphone button and spoke "drive to an address". As I was prompted for the a dress I started driving and was not kicked out due to the safety lock. I did witness the "safety lock enabled" on screen, but I was never kicked out to the map screen. It may be fixed.
I just downloaded 10.851. I may have big news. I believe the hands free safety lock feature has been fixed. I ran a test... It may be fixed.
With these fixes should I consider adding the NAV to my screen? I've been thinking of going with an aftermarket HU after all the NAV complaints on here, but if they are addressing the concerns this would be the easiest option I would think.
Did this update the other night, but was having delays because my hard drive was too full for the download (temp files). Anyway, got me thinking, what would have happened if I'd had an emergency and had to go somewhere while the update was still going on, meaning I would have driven the car without the memory card in the dash. I assume the Nav wouldn't work, but would that be it?