Hardware design fault in all galaxy aces
- Thread starter fishhf
- Start date
Well its not so big but its kinda annyoing sometimes + if we can get something out of Samsung Company pocket its good
class action
Scratching around 10 minutes with my left hand so nothing came near the right side of the screen.
wtf ...
[edit] you cannot fake it , except with image editor, cause the boxes on the right side get green if you touch there..
Sent from my GT-S5830 using xda premium
Last edited:
That means, only S5830's digitizer is defective. Other variants are fine.
Sent from my GT-S5830 using Tapatalk
Better ask this question to samsung representatives. Flash stock ROM via ODIN and show this digitizer defect to service centre representatives and enjoy a new phone, maybe Ace plus or Ace 2
Sent from my GT-S5830 using Tapatalk
i think its not hardware issue
but maybe someone who have similar digitizer(without bugs) can attach to galaxy ace and check, is its hardware or its firmware bug
but maybe someone who have similar digitizer(without bugs) can attach to galaxy ace and check, is its hardware or its firmware bug
If it would have been a firmware bug, samsung would have fixed it long back. Since, no one noticed this hardware bug, samsung kept quite about it too. Why would a super successful cellphone manufacturer destroy its name in market by pointing out its own mistake? And fixing the digitizer in soo many ace's would cost them a lot too.
Sent from my GT-S5830 using Tapatalk
Similar threads
- Poll
Top Liked Posts
-
There are no posts matching your filters.
-
6I started a thread about the digitizer problem in Janauary about things suddenly scrolls rapidly, especially when browsing webpages.
Then on the Jan 15th, I took it to warranty, but without being able to demonstrate the problem clearly, all they done was reflashing the firmware.
I've already tried to fix the bug in the driver, but it is damn hard to filter the "noisy" touches without side effects. (like ignoring movements that are too quick, then i can't type in swype quickly)
I should have known *#0*# earlier, as I'm now able to reproduce the problem right in front of them.
On March 15, I took it to them again. Today, got my phone back with replaced touch screen. Then, tested it in front of their CS and reproduced the bug as shown in the attachment again.
I suggest anyone who owns an ace, please go into *#0*# to test your phone. Keep circling around the lower-left box for at least 10 minutes. Reply to this thread if you're able or not able to reproduce this. I may print this thread to Samsung on my next visit to them.
I've also uploaded a video to youtube to show this. (it's around 1:51 for the bug to appear)
We need to get Samsung to fix this!!2
I tried to find their emails on the web without success.
It would be nice if we can list their emails here(as much as possible, especially mobile division managers in different regions), then I'll initiate an email to all of them, and CC it to all of us.
With the CC'd email, we can all reply it with our own situation, and everyone gets a copy. When it didn't work out, we can just simply forward the whole email thread to our local consumer council/courts.1
Hmm...
Then try firekernel 23/6 version on official cm OC version(non oc version has the problem, wierd) The OC version on official cm will solve all the problems(based on my comparison with zImage and firekernel)
But there is a small battery drain issue in that kernel after reaching 20% otherwise it is great.
