Quote:
Originally Posted by bigsmokefarmer
We need to pester Samsung about this so they prioritise it to get fixed. I have contacted them and got the below response:
"Please be advised that our engineers are currently investigating the issue you have described. If they find it to be a genuine fault then a firmware update to fix the issue will be rolled out as soon as possible. Due to the nature of our investigations we are unable to advise on a timescale for any possible update. "
Register the issue at this link and hopefully they will actually get this sorted
https://contactus.samsung.com/customer/contactus/formmail/mail/MailQuestionProduct.jsp?SITE_ID=31 |
We really need to demand a fix from Samsung! If even Jelly Bean have this issue it's worse than I thought..
I went down to Samsung Care Singapore today to show them my problem.
They have no idea of this bug and immediately suggested that I do a Factory Reset.
I refused and demand that they escalate this issue to their HQ.
Really hope they do something about it and not put up a show that they care and then KIV the complain somewhere.