Thank you for visiting the BlackBerry Support Community Forums.
BlackBerry will be closing the BlackBerry Support Community Forums Device Forums on April 1st (Developers, see below)
BlackBerry remains committed to providing excellent customer support to our customers. We are delighted to direct you to the CrackBerry Forums, a well-established and thorough support channel, for continued BlackBerry support. Please visit http://forums.crackberry.com or http://crackberry.com/ask. You can also continue to visit BlackBerry Support or the BlackBerry Knowledge Base for official support options available for your BlackBerry Smartphone.
"When we launched CrackBerry.com 10 years ago, we set out to make it a fun and useful destination where BlackBerry Smartphone owners could share their excitement and learn to unleash the full potential of their BlackBerry. A decade later, the CrackBerry community is as active and passionate as ever and I know our knowledgeable members and volunteers will be excited to welcome and assist more BlackBerry owners with their questions."
- Kevin Michaluk, Founder, CrackBerry.com
Developers, for more information about the BlackBerry Developer Community please review Join the Conversation on the BlackBerry Developer Community Forums found on Inside BlackBerry.
02-08-2011 11:53 AM
Anyone else have issues going from your app to the browser and then coming back?
I'm basically doing Twitter OAuth through the browser and when I come back from the browser the debugger looses it's connection and the screen looks all screwed up.
02-08-2011 11:59 AM - edited 02-08-2011 11:59 AM
No such problem here. I just tested my app navigating from a link in some htmlText with navigateToURL(), and it opened the browser, gave me a nice 404 error (the page doesn't exist, so that's correct), and then I can left-bezel-swipe to get back to my app and everything looks fine. Debugger connection persisted as well.
02-08-2011 12:02 PM
Can you clarify (screenshot?) what "screen looks all screwed up" means?
Even in the old simulator (and I believe the one before that) I would often get the Navigator screen messing up, with the wallpaper lost, colours screwed up, and sometimes odd panels of gray stretching from top to bottom and covering the right half of the screen (underneath the transparent stuff). I still get this sort of thing with the new one. Generally bottom-swiping once or twice and/or opening an app then exiting again has always restored it.
Or did you mean your app itself is all messed up?
02-08-2011 01:00 PM
Here's a screenshot of what it looks like.
I think just in general the display is messing up.
I noticed too after closing the app the top bar wasn't looking right either:
02-08-2011 01:25 PM
I've never seen a dialog messed up like that, but then I rarely see that dialog, and don't use the others.
The second screenshot I definitely recognize. That's very much like what I've seen frequently with each of the simulators. Usually an extra bottom-swipe and/or open/close an app will recover most of it, for a while.
02-08-2011 01:31 PM
I think a service is crashing on the OS. Not knowing exactly what applications are running, but since your app looks fine and the dialog system system (which is a service) does not complete its rendering, plus the rendering the toolbar stops, then what ever the reading service to the OS is, has failed. It would be nice that if a critical service on the OS crashes, that a monitoring service would restart it. Any QNX experts would know if such a service exists.
02-08-2011 01:31 PM
Set in the app.xml. I commented it out and it seems to fix any issues I have with rendering.
I wonder if it's the same thing with the actual device.
02-08-2011 01:39 PM
I've never had an <renderMode> setting in my app.xml, so I don't think that's really it.
I think it's just that with intermittent problems, it always seems like the last thing you did had some effect on it, when in fact it's random chance. Give it some time and I think it will mess up again.
02-08-2011 01:44 PM
Rendermode is a setting you can turn on for Android and iOs devices.
It essentially renders everything that has cacheAsBitmap turned on the GPU.
I was testing on a Galaxy Tab (same res at Playbook) so I turned it on. Not sure if the Playbook will support it.