CMMotionManager in iOS 10 b5 ignores CMAttitudeReferenceFrameXTrueNorthZVertical

Originator:andreas.schacherbauer
Number:rdar://27787269 Date Originated:August 10, 2016
Status:Open Resolved:
Product:iOS Product Version:10 b2-b5
Classification: Reproducible:always
 
When using the CMMotionManager method -startDeviceMotionUpdatesUsingReferenceFrame:toQueue:withHandler: and passing CMAttitudeReferenceFrameXMagneticNorthZVertical as reference frame, the data seems not to be aligned correctly anymore. Using the same method in iOS 9 or older, the motion data was correctly aligned to magnetic north.


Steps to Reproduce:
Call the method -startDeviceMotionUpdatesUsingReferenceFrame:toQueue:withHandler: on a iOS device running iOS 10 b2-b5

Expected Results:
The motion data is aligned to magnetic north like in previous versions of iOS

Actual Results:
The motion data is not aligned to magnetic north anymore.

Version:
10.0 b2-b5

Notes: 
Also rotating the device seems to mess up CMMotionManager internally. The motion data seems to be lagging several frames behind the rotation.

Comments

Related: http://www.openradar.me/28007399

By gheric.speiginer at Sept. 15, 2016, 7 p.m. (reply...)

Seeing the same problem here, with CMAttitudeReferenceFrameXTrueNorthZVertical. Motion data is lagging and jittery. Running on iOS 10.0

By gheric.speiginer at Sept. 15, 2016, 6:45 p.m. (reply...)

Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!