14 DAY TRIAL // Even if we’re a day away from the official release date of the Samsung Galaxy S6 and Galaxy S6 Edge, some carriers have already started shipping out the new flagships to eager customers.
This means there are a lot of people out there who are already rocking a new Galaxy S6 or Galaxy S6 Edge on a daily basis. Actually, we told you a few days ago that a select number of users had already taken to the forums to complain about their T-Mobile units, which apparently shipped out with chipped displays and even dead pixels.
We also told you that AT&T supposedly sent out a memo informing employees that the boxes of some Galaxy S6 and Galaxy S6 Edge units had some sort of problem that caused the phones to power on while in transit.
This means that when a phone reaches its destination, it might be completely out of battery. So AT&T is recommending users to try and charge their phones before turning them on.
Samsung Galaxy S6's flash remains on
Another day, another Galaxy S6 issue comes to light. According to a thread on the xda-developers forum, some users are experiencing a problem with the Galaxy S6’s camera flash. Apparently, the camera flash remains dimly lit even when it’s not being used.
What’s more, it seems that the flash remains lit while the device is tuned off as well. One user who has noticed the problem on his device, claims that he performed a reboot of the handset and then turned it off, but the camera flash continued to give off a faint light.
It would have been interesting to see whether pulling out the battery would have resulted in the same effect, but that’s obviously something that can’t be done with the Galaxy S6.
Other users, however, claim they are not experiencing the issue on their models, so luckily, it seems we’re not dealing with a widespread problem after all.
We’re also told on the aforementioned thread that Samsung has been made aware of the problem and has already developed a fix which will be made available in a future software update. This is good news, especially since it appears the problem is not related to hardware.
Unfortunately, we have no word so far on when the update will make its way into the wild.
