#Rotategate: Many Samsung Galaxy S6 Edge users are having auto-rotate issues

Is your Samsung Galaxy S6 Edge suddenly stuck in one screen orientation? You’re not alone — Samsung Galaxy S6 Edge accelerometers everywhere seem to be getting their gears jammed.

A fairly sizable collective of individuals have reported that their Samsung Galaxy S6 Edge units periodically refuse to respond when trying to switch from portrait to landscape and vice versa. These people aren’t idiots, so most of them have already thought to check the auto-rotate option in settings. That makes it a legit problem that’s worth looking into.

There doesn’t appear to be any rhyme or reason to any of this just yet. We’ve heard reports for models from Verizon, Sprint and AT&T. It’s also worth noting that there have been no such reports for the regular version of the Samsung Galaxy S6, just the S6 Edge.

A couple of theories are already in play, including the obvious thought that this is simply a software glitch that can be ironed out with a quick patch. That would be great as it would mean the issue can be eradicated without much of an issue.

But a few users are suggesting that this issue only occurs after they’ve used a fast charger to charge their devices. Pretty big problem, if true: all Samsung Galaxy S6 and S6 Edge units ship with a fast charger as standard. The fast charger causes the device to heat the battery up a pretty good bit, so the heat could be causing some sort of failure in the accelerometer chip.

A hardware flaw would be much trickier for Samsung to deal with, and there’s no telling what would have to be done in order to get early adopters situated short of a mass recall.

That said, it’s important to note that official details are scarce right now. Until Samsung has a chance to investigate the cause of these claims we won’t know for sure how severe or widespread an issue this is. We’ll have to drop a line into the Korean company to see if they can shed some light, but in the meantime be sure to see your carrier or retailer about a replacement to see if you can luck into a unit that dodges these issues.

[via AndroidForums.com, thanks to everyone who sent this in!]