Orientation sensor "fix" for 2.2 and the landscape blues!

mcl1981

Well-Known Member
I'm sure everyone has noticed that with 2.2, the orientation control blows. In previous versions, the orientation sensor was active anytime the display was on and it was quick. But now it is only active when an app using it is active. If you're on the home screen, the orientation sensor is not active. So, if you have the phone in landscape and back out to home, the orientation remains in landscape regardless of how you hold the phone after closing the app. If you hold the phone upright and open an app, it will open the app in landscape mode even though you're holding it vertical. It takes up to several seconds for the orientation sensor to come back on, recognize you're vertical, and rotate itself. This is annoying at best and can cause some serious lagging if the app is trying to do other things at the same time.

So what we need is a way to make the orientation sensor be active all the time again. No such option. So we'll trick it! Solution? TASKER!

Create a new profile in tasker, I called mine "Orientation Un-F&ck". Set the context for State > Orientation > Standing Up. It doesn't really matter what orientation you pick, we're just making it check the orientation. For tasks, it doesn't actually have to do anything so I made the task be Tasker > Stop. So it literally just does nothing.

So now tasker is always monitoring the display orientation. The phone doesn't give a crap why or what it does. It just knows something cares about orientation so the orientation sensor is active and doing its thing.

Result, when you back out of an app in landscape, and open an app in while vertical, it immediately switches to vertical. No delay.

I do not know what effect this will have on the battery. Probably nothing since no matter what you do, the orientation sensor is off when the display is off. Most people don't sit there staring at their home screen for hours so I anticipate no adverse effects on battery draw.
 

Drew5150

Android Expert
My phone doesn't experience this issue you are talking about. I've never even heard of this issue before.

You must be using an evo shift? This is the evo 4g forum.
 

mcl1981

Well-Known Member
Thread starter
No. I've had an Evo since the day it was released and I've read many other people bitching about this.
 
This problem is bugging the heck out of me!!!! I want to get your solution but what is "Tasker"? Is that the task manager or is it an app? Whatever it is, I want it!!!!!!!!!!!!
 

frenchy714

Android Expert
This problem is bugging the heck out of me!!!! I want to get your solution but what is "Tasker"? Is that the task manager or is it an app? Whatever it is, I want it!!!!!!!!!!!!

Like already mentioned, you can find Tasker in the Market or at Appbrain. If you google Tasker and go to their site, I believe they allow you to download a trial version so you can use it for free for 7 days.
 
Ok I found tasker and I've made a few profiles now. I can't get the orientation profile to work.

Can anyone walk me through with baby steps on how to make this profile work?

Right now I have the context as orientation is faceup, orientation is standing up, and time is 00:00 to 12:59. The task is Display Rotation On. I had it with just the context of orientation is faceup and the task as tasker stop like the original poster said but it didn't seem to work.

Also, if this is a working profile, should it show up as an active profile?
 

geek0125

Lurker
Try this oddity I discovered - When you go to calibrate the Display:

Settings >> Display >> G-Sensor Calibration

Do not hold the phone standing on an end - place it on a level table top ON IT'S BACK! then hit calibrate. Ok after it's done

The orientation sensing will now work the way it's supposed to.
 

mcl1981

Well-Known Member
Thread starter
Try this oddity I discovered - When you go to calibrate the Display:

Settings >> Display >> G-Sensor Calibration

Do not hold the phone standing on an end - place it on a level table top ON IT'S BACK! then hit calibrate. Ok after it's done

The orientation sensing will now work the way it's supposed to.

That will do nothing to fix the orientation issue we're talking about.
 
Top