One last note, I pulled the failing BrickBreaker sample from supportforums.blackberry.com/t5/Web-and-WebWorks-Development/TEXT-object-cause-black-screen-after-OS-2-1-0-1032/td-p/1938303 and packaged/deployed to my PlayBook (188.8.131.528) and definitely saw some issues (and some potential issues):
* As I was playing, the rendered area kept growing larger. Not sure if that was intentional.
* After playing for ~20 seconds, the screen went black.
The timing of the screen going black appears related to the growing play area. I did not come across any large volume increase though (it was always around 50% volume.)
That being said, I clicked through / failed a few times without any issues beyond the growing play area / eventual black screen.
Are these the issues in question?
By my test months ago,
the text with webgl-on is sufficient to make screen black.
It's great to hear that they'll be ok now.
The story about growing paly area is here:
When I was making Brick Breaker for testing if playbook's performance is good enough for ACT,
I tried many ways to figure out why it always turned into black screen,
then I found that when I choose "Letterbox Integer Scale" mode, it showed with smaller size and worked.
(WebGL is On)
Therefore, I made the growing-area to make sure if it's screen size problem.
The result is, if the screen size just fit Playbooks's screen size, it crashed to black screen.
At first, I thought it's screen size issue,
after more tests, I found if I turned WebGL off, the growing area wouldn't crash anything.
Moreover, if I removed text object, it worked with WebGL too.
For study reason, I'd show you this:
Monday Morning Escape
It's my first playbook game after BrickBreaker testing.
Actually speaking, I want this game published at first, but it turned into black screen too.
I removed all text objects to fix the black screen issue,
but it wouldn't be a game without hints and story-telling.
After BrickBreaker testing, I simply turn WebGL Off in Monday Morning Escape project,
then it amazingly worked.
That's why I think it's not screen area issue and surely is WebGL problem.
I don't know if something fixed or not in these months.