So Why is there a x86 option now for Android with Unity 3.5... doesn't work!

Hopefully I'm doing something wrong, because as it currently stands this is a half baked implementation that shouldn't of been included

I have Pro and Android Pro I also have a Logitech revue (Google TV Intel atom) that has never worked with unity because unity only supports arm7 and above (yes a few others) When I learned of this I was getting a mono not found exception thrown on the revue After updating to unity 3.5 and it FORCING ME (not cool) to update my android sdk to include 4.0 I noticed that the device filter now has x86 as an option. So I pulled the revue out of the closet and gave it another go. (I have searched and unity doesn't seem to mention this anywhere) but figured it may just work... So gave it a shot... and mono not found exception.... low and behold I switched it back to arm7 filter and tried to push it to the revue again and it gave me a warning that I haven't seen before that said this device does not support arm7 apk. It didn't give me the warning with the x86, so I'm guessing this is just a half ass attempt of making it work with these types of processors.

*also to note a company this size should really learn to make an installer. I had Unity beta 3.5 installed and Unity 3.4 on my computer and just 3.4 on a different computer, the new 3.5 overwrote my beta version and left it in the beta folder! and on the other computer didn't even ask if I want it to be a separate install or to just overwrite the previous version and just deleted ALL dlls within that folder. And since unity can't make a proper location for windows dlls to reside it deleted all my custom dlls out of that folder too. And then this crap about having to have android 4.0 on my computer before I can use unity as I was before hand is just not acceptable... There are some instances where 4.0 is purposely left off a computer until we develop for the specified platform!