[bast525]

While it is true that only certain apps are causing the issue, I dont think you understand fully exactly how the problem is affecting system performance.

This isnt just S2U2 not displaying correctly. Putting S2U2 in Raw Buffer mode, or opening Coreplayer, will have an immediate impact on overall rendering performance in landscape, EVEN AFTER YOU COMPLETELY CLOSE OUT OF S2U2 OR COREPLAYER.

Do this... Completely disable S2U2/iLock. Then start your camera (this "resets" the driver for some reason). Immediately close the camera. Slide the keyboard out to force landscape, and then load Opera and go to whatever webpage. Do a lot of scrolling around and note how smooth it is. Then close it and switch back to portrait.

Now start iLock, and if you dont have it this way already, switch it to run in rawbuffer mode. Then STOP THE RUNNING ILOCK AGAIN (note, if iit was already in rawbuffer, you merely need to launch ilock and then immediately stop it). Now open Opera again in landscape view. Scroll around a large page and tell me you dont notice a distinct drop in smoothness of the animation, and you should now notice screen tearing that was not there before.

Other apps show this even worse... The Resco photo viewer beta is one of them. The free SK Tools Lite application has a "Draw Bitmaps" benchmark test that VERY clearly shows this... run it in landscape after opening and closing the camera... you'll get a score of about 200 and it will be smooth. Run it after opening and closing ilock (set to rawbuffer mode) or Coreplayer, and you'll get a score of about 130, and it will look choppy as hell. Just like it ALWAYS did on the TP1 in landscape.

The reason I keep saying it is a driver issue is because the effects persist even when the apps that cause it are disabled. And really, whatever it is, it is very minor. Still.. I hope this is something fixable once we start getting custom ROMs...