I confirm this issue is present on other devices which are running 3.013 firmware. See this post for more information: