Well I wonder if they adress the issue on 6.2 live letter or gonna be pretending that problem doesn't exist.