goodev / android-xbmcremote

Automatically exported from code.google.com/p/android-xbmcremote
1 stars 0 forks source link

TV Mode Locked to Portrait #544

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Orient phone/tablet in landscape mode
2. Click into TV Shows 
3. XBMC, now in the TV list mode will re-orient into portrait mode, and stay 
locked there
4. Additionally, if you click into a TV show, (now in the season select screen) 
XBMC will stay locked in portrait mode.
5. Once select a season and get into the episode select screen, XBMC will 
respect the orientation of you device and switch back to lndscape mode.

What is the expected output? What do you see instead?
Expected behavior is XBMC-remote respecting the orientation of the device. 
Movies performs as expeted, TV Shows does not, and Music is at this time, 
untested.

Additionally the About screen, if you click the XBMC logo on the main screen, 
will not respect device orientation either. It will always lock into portrait 
mode.

What version of XBMC Remote are you using?
Phone: v0.8.6-beta1 Rev 768
Tablet: v0.8.6-beta1 Rev 768

Which Android device are you using (and which ROM, if custom)?
SGH-i897 Captivate Cyanogen7
GT-P7510 Galaxy Tab 10.1 Stock 3.1

Which XBMC revision are you running and on which platform?
10.1 Git: 3939099

Please provide any additional information below.

Original issue reported on code.google.com by nolan.re...@gmail.com on 23 Jul 2011 at 7:24

GoogleCodeExporter commented 9 years ago
You're talking about the banner that get screwed up when download in landscape 
mode, right?

Original comment by phree...@gmail.com on 13 Aug 2011 at 8:07

GoogleCodeExporter commented 9 years ago

Original comment by phree...@gmail.com on 13 Aug 2011 at 8:09

GoogleCodeExporter commented 9 years ago
No, the whole screen layout changes from landscape to portrait.

Original comment by nolan.re...@gmail.com on 13 Aug 2011 at 8:19

GoogleCodeExporter commented 9 years ago
I believe this was fixed in 0.8.7 or 0.8.8

Original comment by nat...@gmail.com on 18 Feb 2012 at 11:23