That's what we are doing using a kalman filter in our application but the speed information is really important for a good precision. We have noticed that the speed is 0 when the course accuracy is 180 degree.

The only problem in my case is that our speedAccuracy does not contains a negative number, but the actual speed property is equal to zero (while the device is still moving). Is there any other issues related to this one known ?