S2U2 Landscape

[touch_rules]

Originally Posted by stevedensmore

I've heard s2u2 eats the battery. I am thinking this could be true because my mogul had it since day one and the battery life on that thing was horrendous.

I am using 2.04 and out of no where without any changes my landscape mode seems to be working fine. I was messed up but the last couple of days it started working. Weird.

On another note, this thing is eating up my battery. Anyone know what could be causing this in S2U2? My battery life was awesome before I installed this. Now I have to charge it a couple of times a day to get through the day.

Thanks.

[GoodThings2Life]

Originally Posted by touch_rules

On another note, this thing is eating up my battery. Anyone know what could be causing this in S2U2? My battery life was awesome before I installed this. Now I have to charge it a couple of times a day to get through the day.

This is purely based on how you've configured it. Try the attached "safe" configuration that I use and see if your results don't improve. This already has the RawBuffer and KeyBoard hook settings enabled, and uses battery-friendly defaults.

You can change some of the appearance settings (like number/appointment settings, but don't change any of the Power, Phone, or Advanced settings.

Post back here if you have any trouble with this file.

[xconwayx]

Originally Posted by touch_rules

I am using 2.04 and out of no where without any changes my landscape mode seems to be working fine. I was messed up but the last couple of days it started working. Weird.

On another note, this thing is eating up my battery. Anyone know what could be causing this in S2U2? My battery life was awesome before I installed this. Now I have to charge it a couple of times a day to get through the day.

Thanks.

Mine is the exact same way.

[WarChild]

does anyone have a good cab so I don't have to look for it?

[DZF]

hopefully the landscape is fixed so my .gif works properly. still a great program! someone keep us informed when the new S2U2 comes out

[LilRico]

A_C is still examining the logs I sent him along with the registry settings I have. This should all be fixed for 2.05.

[bast525]

Hmmm I am still concerned about the overall issue... something strange is going on with the TP2 display drivers. Nothing horrible or deal breaking, but still something that is worth investigating IMO. It's not just S2U2........

[GoodThings2Life]

Originally Posted by bast525

Hmmm I am still concerned about the overall issue... something strange is going on with the TP2 display drivers. Nothing horrible or deal breaking, but still something that is worth investigating IMO. It's not just S2U2........

I keep seeing you and some others say so, but I've yet to see any issues aside from specific app compatibility issues, and this is true whether you're using the stock driver (htc_d3dm.dll) or the enhanced driver (ati_d3dm.dll).

For example, I was having issues (terrible Landscape lag) with performance when I was using the "battery indicator" gauge (the one that puts the red-to-green bar across the very top of the screen). As soon as I disabled that, the issues immediately went away.

Bottom line, it's the same thing true as on the desktop. Not every app can be 100% compatible with every device and every situation possible. So, check your programs one at a time, and the ones that cause issues, replace them with either new versions or new programs.

[LilRico]

Originally Posted by GoodThings2Life

I keep seeing you and some others say so, but I've yet to see any issues aside from specific app compatibility issues, and this is true whether you're using the stock driver (htc_d3dm.dll) or the enhanced driver (ati_d3dm.dll).

For example, I was having issues (terrible Landscape lag) with performance when I was using the "battery indicator" gauge (the one that puts the red-to-green bar across the very top of the screen). As soon as I disabled that, the issues immediately went away.

Bottom line, it's the same thing true as on the desktop. Not every app can be 100% compatible with every device and every situation possible. So, check your programs one at a time, and the ones that cause issues, replace them with either new versions or new programs.

I totally understand that, but this is happening to all 3 TP's I have access to. T-Mobile, Verizon and Sprints. All on a stock ROM with nothing loaded. When I mean nothing, I mean, not even contacts or any kind of sync. I also tried the enhanced drivers, but that still doesn't get rid of the problem and this is an issue that's been going on for quite some time. A_C is looking at the logs and is doing his best to determine what exactly is going on... Though its taking him some time to figure it out, I'm sure he will.

[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...