Hi - first post. Just bought my Playbook (32g) and absolutely delighted with it. I have both an Ipad and Android Tablet but this is the one for me.

...anyways, have encountered a tricky app problem. I downloaded Pool Break (the free one) but whilst playing it the screen froze. It gave me the option to wait or close but neither responded. After closing it via the swipe and small 'x' I relaunched - but it was back to the same place with no response.

I then uninstalled the app and reinstalled - back to exactly the same place (??).
I then left it uninstalled (fed up trying) and some time later installed the google launcher app. However, when I tried to run than it rather remarkably defaulted to my frozen Pool Break screen - so no response. to cut a longer story shorter - despite various installing and uninstalling, I cannot get either app to work. Its not obvious (to me anyway) what the link is between the two.

Any ideas appreciated?

Try rebooting the PlayBook. Under Tablet OS 2.0 all android apps run under a single window. With OS 2.1 that is changed, but it sounds like Pool Break has choked and frozen the emulator. A reboot should get you out of that.

Thanks hrbuckley - your suggestion worked. It happened again though - do you think I have an underlying problem or is this a common occurance? Just mindful that the shop I bought the playbook from is relocating in a week or so to the other side of the City and so if I needed to go back I'd prefer to do it this week.

cheers

Android applications freezing was quite common when support first came out, but is less so now. I have a free pool app on my PlayBook (can't recall the name at the moment and my PB is at home) but it hasn't ever frozen on me with OS 2.0 but did once under the beta 2.1 which I'm running now.

You need to do what you think is best, but be aware that emulating another OS is always going to be a less reliable way to run applications than porting them. Tablet OS 2.1 should be out fairly soon. Most of the changes are to address Android issues.

Thanks, I'll maybe just leave it and see if it persists or is resolved by the next update.

Cheers