[soren203]

Hey everyone after I upgraded to os 2 I have noticed that sometimes when Im in an app or using the browser the playbook just wont respond to my touch. Right now I cant get the top homescreen banner to respond when I touch it. Has anyone else had this problem?

[Spencerdl]

No, not at all. I was just thinking the other day about how much more responsive the entire PlayBook is since the OS2.0 update. I've had my PlayBook since May and it's more responsive then its ever been, maybe because everything appears to be quicker.

[kbz1960]

I'm sure you know if you are touching the bezel too far in from the edge that touching is effected.

[jamesharmeling]

I have found that I sometimes have to click links twice. Clicking once will highlight the link, but goes nowhere until I hit it again.

[Scotter75]

I think you are too fast with the tap.

[robsteve]

Try cleaning the screen when you have a problem with responsiveness. I find screen protectors can affect responsiveness too; even more when dirty.

[currentodysseys]

Hi, as kbz said, maybe the way you hold the playbook if accidentally have prolonged hold on to the bezel could cause that.

Personally i find the screen more responsive after os2

The double tap i think you can fix by actually triple-taping works for me. Hope that helps.

[I am JT]

No problem with mine.

[Vector-SS]

I have found that I sometimes have to click links twice. Clicking once will highlight the link, but goes nowhere until I hit it again.

I've had this issue since OS1 and it's frustrating to no avail.

However, I noticed the screen to be more responsive with OS2 and sort of more "precise" to the touch such as clicking page numbers on forums is now somehow easier.

[hpulley]

Yes, twice with OS 2.0 the browser stopped responding to top bezel swipes. Yesterday most recently. Other apps are fine at the same time so it is just the browser for me, not the OS as a whole or a strange bezel hardware issue, just the browser. Killing the browser and restarting it fixes the problem. Annoying bug for sure.

When it isn't doing this, going poof or hanging the 2.0 browser is really good...