Problems on New Google TV 3.2 Release

Showing 1-12 of 12 messages
Problems on New Google TV 3.2 Release Dan Syrstad 2/7/12 7:31 AM
Hi,

We're starting to get reports from Sony TV users that our game -
Syrious Scramble - isn't working correctly. These users have received
the 3.2 upgrade. It looks as though certain characters are being
dropped from the font rendering - with two different fonts. One font
is a custom TTF built into the game, the other is the standard sans
serif font (DroidSans). The "Pause" screen is missing the "P". It's
rendered in DroidSans with standard text in a standard TextView. In
the game view, the letter "D" is missing from the tile using our
custom font.

We don't have a Sony TV to test on, but a user was kind enough to send
in screen shots:

https://docs.google.com/open?id=0B3CFPp3_TiVWY2EzYTYxNGItZWU1Yi00MmVmLTkzYjItNmNmMzllN2YwN2Qw

https://docs.google.com/open?id=0B3CFPp3_TiVWNTJiMjM3OTYtZWU1Yi00MDMwLThhOGYtOWQxMjcxZTZlMjcy

It is possible that if font metric calculations have changed in 3.2,
it could mess up the positioning of the letter on the tile. But the
Pause screen baffles me. The "ause" is even centered as if the "P"
isn't there.

Would it be possible to have someone at Google test Syrious Scramble
Free on a Sony TV upgraded to 3.2. We don't have access to one.

-Dan
Re: Problems on New Google TV 3.2 Release Yossie 2/7/12 7:05 PM
I noticed this too. It seems certain uppercase letters as well as
symbols (e.g. "@") don't render if the font size is too large. Not
sure what's up, but I just lowered the font size to fix it..

On Feb 7, 10:31 am, Dan Syrstad <dsyrs...@gmail.com> wrote:
> Hi,
>
> We're starting to get reports from Sony TV users that our game -
> Syrious Scramble - isn't working correctly. These users have received
> the 3.2 upgrade. It looks as though certain characters are being
> dropped from the font rendering - with two different fonts. One font
> is a custom TTF built into the game, the other is the standard sans
> serif font (DroidSans). The "Pause" screen is missing the "P". It's
> rendered in DroidSans with standard text in a standard TextView. In
> the game view, the letter "D" is missing from the tile using our
> custom font.
>
> We don't have a Sony TV to test on, but a user was kind enough to send
> in screen shots:
>
> https://docs.google.com/open?id=0B3CFPp3_TiVWY2EzYTYxNGItZWU1Yi00MmVm...
>
> https://docs.google.com/open?id=0B3CFPp3_TiVWNTJiMjM3OTYtZWU1Yi00MDMw...
Re: Problems on New Google TV 3.2 Release Dan Syrstad 2/8/12 7:32 AM
I got some more feedback yesterday and it looks like the problem is
happening at 1080p and not 720p.

With @Yossie's response above, this appears to be a Google TV 3.2
regression issue.
-Dan
Re: Problems on New Google TV 3.2 Release Dan Syrstad 2/8/12 10:27 AM
Another update: Another user reports that if they don't adjust for
overscan at 1080p (i.e., the picture goes beyond the TV bounds),
everything works fine. Once they adjust for overscan, the problem
starts to appear.
-Dan
Re: Problems on New Google TV 3.2 Release Les Vogel 2/8/12 10:31 AM
We reported your fist report and all subsequent comments to engineering - we haven't heard back yet.

Les
--
Developer Programs Engineer - GoogleTV


Please send questions to the list and only use my email address for things that require privacy such as source code or APK's.   We also answer questions on StackOverflow.com  #Google-TV

Re: Problems on New Google TV 3.2 Release Les Vogel 2/9/12 7:21 AM
It's looking like it's related to android:hardwareAccelerated="true" - If you could confirm and if you could try your apps w/o that and let us know it would be appreciated.  

Dan - I know you have a M4 - I updated the software on it recently - it should reproduce there.  You might also see something in the log file - if you'd pass that along it would be appreciated.

Les
Re: Problems on New Google TV 3.2 Release Dan Syrstad 2/9/12 4:57 PM
Les - I reproduced the problem on the M4. I've also confirmed that
turning off android:hardwareAccelerated fixes the problem. However,
this causes the animations to be as slow as 3.1. With it on, the
animations are nice and smooth on 3.2. Turning this setting off also
affects animation speed on tablets. I currently have a single apk that
targets all devices.  It'd be really nice to have this enabled for all
devices and not have to maintain separate apks.
-Dan

On Feb 9, 9:21 am, Les Vogel <l...@google.com> wrote:
> It's looking like it's related to android:hardwareAccelerated=**"true" - If
> you could confirm and if you could try your apps w/o that and let us know
> it would be appreciated.
>
> Dan - I know you have a M4 - I updated the software on it recently - it
> should reproduce there.  You might also see something in the log file - if
> you'd pass that along it would be appreciated.
>
> Les
>
>
>
>
>
>
>
>
>
> On Wed, Feb 8, 2012 at 10:31 AM, Les Vogel <l...@google.com> wrote:
> > We reported your fist report and all subsequent comments to engineering -
> > we haven't heard back yet.
>
> > Les
>
> > Les Vogel <https://plus.google.com/u/1/107226127526541403399>
> > Developer Programs Engineer - GoogleTV
> > lesv@ <l...@google.com>*G**oogl**e*.com <http://code.google.com/>
>
> > Getting Started on Google TV <http://developers.google.com/tv>  Sample
> > Code <http://code.google.com/p/googletv-android-samples/>  LeftNavBar<http://code.google.com/p/googletv-android-samples/source/browse/>
> >   Google TV Video Player <http://code.google.com/p/googletv-video-player/>
> >   Android <http://d.android.com>
>
> > Please send questions to the list<https://groups.google.com/forum/#!forum/googletv-android>and only use my email address for things that require privacy such as
> > source code or APK's.   We also answer questions on StackOverflow.com
> >  #Google-TV
>
> --
> Les Vogel <https://plus.google.com/u/1/107226127526541403399>
> Developer Programs Engineer - GoogleTV
> lesv@ <l...@google.com>*G**oogl**e*.com <http://code.google.com/>
>
> Getting Started on Google TV <http://developers.google.com/tv>  Sample
> Code<http://code.google.com/p/googletv-android-samples/>
>   LeftNavBar<http://code.google.com/p/googletv-android-samples/source/browse/>
>   Google TV Video Player <http://code.google.com/p/googletv-video-player/>
> Android <http://d.android.com>
>
> Please send questions to the
> list<https://groups.google.com/forum/#!forum/googletv-android>and only
Re: Problems on New Google TV 3.2 Release Les Vogel 2/9/12 5:34 PM
Dan,

  Believe me, I understand.  There are bugs in HW Acceleration.  That's why on the release notes we told folks to test their apps again, as it manifests in some apps.

  I'm not going to try and do work arounds, but since you use an all caps font, you might consider pre-rendering each letter and just use a bitmap.  If it works, you fix your problem and can keep HW Accel.

Les --
Developer Programs Engineer - GoogleTV


Please send questions to the list and only use my email address for things that require privacy such as source code or APK's.   We also answer questions on StackOverflow.com  #Google-TV

Re: Problems on New Google TV 3.2 Release Dan Syrstad 2/10/12 7:43 AM
Thanks Les. Unfortunately, as I originally reported, the problem is
more than the tiles. It's also in a TextView. Since I don't know what
the font size cutoff is, I don't think can pre-render every TextView.
The quickest short-term workaround for us is to turn off
hardwareAcceleration, which is unfortunate.

Is Engineering planning on addressing this issue in a upcoming build?

-Dan

On Feb 9, 7:34 pm, Les Vogel <l...@google.com> wrote:
> Dan,
>
>   Believe me, I understand.  There are bugs in HW Acceleration.  That's why
> on the release notes we told folks to test their apps again, as it
> manifests in some apps.
>
>   I'm not going to try and do work arounds, but since you use an all caps
> font, you might consider pre-rendering each letter and just use a bitmap.
>  If it works, you fix your problem and can keep HW Accel.
>
> Les
>
>
>
>
>
>
>
>
>
Re: Problems on New Google TV 3.2 Release Les Vogel 2/10/12 9:09 AM
Short answer - NO - not in the near term.

Long answer - It's likely to be fixed in the longer term.--
Developer Programs Engineer - GoogleTV


Please send questions to the list and only use my email address for things that require privacy such as source code or APK's.   We also answer questions on StackOverflow.com  #Google-TV

Re: Problems on New Google TV 3.2 Release Paul (Google) 2/10/12 10:26 AM
Hi Dan,

You can have hardware acceleration on at the application level, and turn it off programmatically using:

myView.setLayerType(View.LAYER_TYPE_SOFTWARE, null);

If you want to turn hw acceleration off for a view for Google TV only, leaving it on for other devices, you can query for the com.google.android.feature at runtime.

if (getPackageManager().hasSystemFeature("com.google.android.tv")) {
    // disable features that are not supported on Google TV.
}

There are a few other options for controlling hardware acceleration at:


I hope this helps!

Paul S.
--
Developer Advocate
Google Inc.

Re: Problems on New Google TV 3.2 Release Dan Syrstad 2/10/12 10:43 AM
Hi Paul,

Yep - I was reading about the same thing today and this is the tactic
I'm going to run with.

-Dan

On Feb 10, 12:26 pm, "Paul (Google)" <n...@google.com> wrote:
> Hi Dan,
>
> You can have hardware acceleration on at the application level, and turn it
> off programmatically using:
>
> myView.setLayerType(View.LAYER_TYPE_SOFTWARE, null);
>
> If you want to turn hw acceleration off for a view for Google TV only,
> leaving it on for other devices, you can query for the
> com.google.android.feature at runtime.
>
> if (getPackageManager().hasSystemFeature("com.google.android.tv")) {
>     // disable features that are not supported on Google TV.
>
> }
>
> There are a few other options for controlling hardware acceleration at:
>
> http://developer.android.com/guide/topics/graphics/hardware-accel.html
>
> I hope this helps!
>
> Paul S.
>
>
>
>
>
>
>
>
>
> On Fri, Feb 10, 2012 at 9:09 AM, Les Vogel <l...@google.com> wrote:
> > Short answer - NO - not in the near term.
>
> > Long answer - It's likely to be fixed in the longer term.
>