
28 Apr
2015
28 Apr
'15
11:33 a.m.
Hi Hans,
So it seems that I'm not the only one seeing this, and I've been wrongly blaming it on the A33, instead it seems to be a kernel bug, triggered on my A33 due to the display resolution it has.
For details see:
That's good news; far less scary than a HW issue.
Would you mind replying on that thread to give it a bit more visibility?
Thanks, Mark.