I don't currently have Gyrator2 installed because I did a hard reset, and I'm slowly adding programs back as I assess their battery impact, but when I had Gyrator2 I had it working pretty smoothly for how I wanted, I just had to take a few seconds to add an exception every tiime I had a program rotating that I didn't want to rotate. Let me see if I can recall exactly how I set it up.
First off I think I deleted all the events that came preloaded on it, except for the event that rotates EVERYTHING. This is obviously annoying if it rotates things you don't want rotated, so then I just added exceptions.
To add an exception, I would have to create a new event, and then in the section that dealt with what application it would affect I would either select it from the list (if it already existed there), or I would "learn program" or whatever it was called. At first this was really confusing, but once I figured out how to do it, it was actually pretty easy.
This is coming from memory, so forgive me if I get the exact wording wrong, but it went like this:
1) click the entry field for entering the name
2) click "Learn Program Name" (or something like that)
3) open the program that I want to create the rule for
4) remove the stylus and put it back into the slot (this is the signal for gyrator2 to take the program name of the active program)
At this point I think it would auto-navigate back to Gyrator2, and the program's name would be entered.
5) where you select what events happen and when, only select rotate, and only select "portrait" orientation. this basically tells Gyrator 2 to only rotate the program to portrait mode, effectively not letting it rotate at all (you could also have it always be in landscape mode, if that's what you prefer).
6) select "OK" or "apply" or whatever it is, and go back to the menu that shows all the events
7) right click the event you just made and select "orientation" event, so that it knows what type of event it is
right click this event and promote it above the event that rotates EVERYTHING (this is important, as the way Gyrator2 determines which event to do for any given program is that it starts at the top of the list and works its way down, and stops once it reaches an applicable event. Basically you want the "rotate all" event to be on the bottom)
An alternative method would be to delete all the events, but then add back in events for programs that you want rotated, make sure they are set as "orientation" events, make sure that "rotate" is checked, and that all the screen orientations are selected. If the first set of rules I laid out could be described as "rotate everything EXCEPT these programs" then this way of setting rules could be described as "only rotate these programs".
IMPORTANT NOTE: For some reason phone calls are handled by 2 different applications. There is the "Incoming Call" application, and the "Phone call" application (there might even be a third for ending a call...I forget). Anyway, you have to make sure that BOTH of these applications are set as exceptions if you don't want the screen to rotate for incoming calls or for when you are on a call. Both of these applications are in the default list, though I think one of them is named differently than what it shows up when you select it (ie it is called "Incoming Call" in the program list, but once selected the event is called "Phone - Incoming", or something like that. Just look around). ALSO NOTE: If you use a non-stock dialer/phone app, then you might need to add it to the exceptions list manually.
Anyway, personally I liked the program, but it is one of my leading candidates for battery drain testing, and if I determine it uses an excessive amount of battery, then I probably won't add it back in. In the 2 weeks since hard resetting, I haven't really missed having it, so it won't be a huge deal.