What steps will reproduce the problem? 1. Open up life counter 2. Turn the phone... sideways. Shake it a bit, for good measure. If it's still being a bit recalcitrant, yell at it that you're going to ditch it for a phone on another carrier. Maybe an iPhone.

What is the expected output? What do you see instead? The +/- buttons should rotate, the number should rotate, and the result list should have its internal table of results change directions.

What version of the product are you using? On what operating system? 1.0

Please provide any additional information below. Many people using their phones as life counters during magic games use their phones with a kickstand (it's super handy!), which are always in landscape mode. Rotation makes it usable with a kickstand.

This should apply to more than the life counter. At least the card search and result list also. Maybe even the cardview, although that could get a little ugly. The good thing is that its easy to fix, as seen here: http://stackoverflow.com/questions/4858026/android-alternate-layout-xml-for-landscape-mode Just remember to change the Activity's rotation lock in the manifest.

Also, the MainActivity should not be rotatable. There is a bug where if it rotates during a threaded operation (update) it could force close. It's easier to lock rotation than to debug the actual issue.

Yep, the reason why I made it a separate bug from the other rotation bug is that while the other ones should simply rotate the viewport, the life counter absolutely needs to have a different layout in landscape mode (because you can't just have one on top of the other in landscape mode; instead, they need to be side-by-side).

r70 - rotated with a new layout. Mike, make sure this is up to spec and if it is, close out this ticket

Tweaked from Adam's version to make buttons bigger and farther from reset button as well as shrinking history while expanding life readout. I also made all of the textviews singleLine so they don't introduce line breaks when the text gets too long 1000+ life etc. Ultimately I think we may have to subclass TextView and make one that automatically scales the text. That would suck, but I've looked for an alternative for my programs in the past and have found none. Whew.