|
|
|
|
|
|
by Unklejoe
3542 days ago
|
|
|
What gets me is the fact that they did the recall and produced a new version of the phone which was supposed to fix the issue, yet now there are reports of the replacement units doing the same thing. Seems like they either jumped to conclusions and mis-identified the problem, or they attempted to fix the problem with a band-aid solution with the hopes of reducing the probability of failure just enough to make the issue "go away". On a more personal note: I hope this gives other Android phone manufacturers a chance to gain some market share. Primarily, I want HTC to do well. They seem to be one of the most friendly when it comes to unlocking the bootloader (you can do it via their website). I really wanted to get the Galaxy S7, but after finding out that the versions with the SnapDragon SoC will have locked bootloaders, I decided not to. In my experience, Samsung's version of Android has never been that great. Without the ability to flash custom ROMs and remove some of that useless crap, I just couldn't bring myself to make the purchase. |
|
|
It'd be smart to give the tolerances some extra headroom on the second go-around, but I would guess that in order to get additional certainty on their sample, they would need to run their testing program for longer while the inventory is piling up. And I have to imagine with a production the scale of the Galaxy there are immense pressures to get that inventory moving.
But it sounds like they gambled and lost.