I titled the thread like that because I think it may come useful to other people in future.
The device I ask info for is Huawei Ideos Mobile Phone.
It has Android 2.2 and ARM11 chip, but just to be sure…
ARM11 is too weak and not supported (at least at the time)
Or otherwise this one: Buy Mobile Phones online | Vodafone UK
Well, I thought ARM11 was a LATER (and better) incarnation respect to ARM6!!!
OK here is the Wiki page about ARM processors: ARM architecture family - Wikipedia
But I really think a Unity Wiki page should be set up with the compatible devices, not only to allow a new developer to aim his buy, but also to show off to clients of his applications!
What about this one? http://pdadb.net/index.php?m=specs&id=2274&c=lg_gt540_swift_lg_optimus
Its commonly rather easy to keep in mind: ARMV7 based cpu are fine , anything below (iphone 2G /3G level and weaker to much weaker like ARM11) isn’t.
alternatively look up for the graphics chip. if it is not opengl es 2.0 capable chances are good that the same way of saving money by using 3-4 year old hardware happened for the cpu.
If the device new without contract is less than $400-$500 chances are low to zero that it is supported
So Unity games won’t run on iPhone 3G either??? 
I have a game running smoothly on my 3G and it’s made with Unity
Unity iOS games work on iPhone 3G etc
I only mentioned the iPhone as a “technology level comparision” cause the unsupported androids we talk about here are at best as performant as the iphone 3G, commonly weaker though
What mobile would you suggest as the less expensive yet working with Unity?
Define “less expensive” 
Most android phones with reasonable hardware / supported hardware fall into a range of $100-$150 between $500 and $700 without contract (commonly easy to get as mentioned due to OpenGL ES 2.0 or cpu speeds of 800mhz+)
I personally have the HTC Desire as it is fast (not the fastest, that would be Galaxy S, but Samsung is fucking up the OS as well as the android 2.2 deploy). its can compete with iOS 4 on the hw specs and is actually ahead
Lots of Android phones have better specs than the iPhone 4 like the Droid 2, Droid X, Droid Incredible, a few HTC phones, the Galaxy S, etc.
On the ANDROID page of Wikipedia I read that it works on ARM, MIPS, Power Architecture.
These are 3 types of chip architecture if I don’t mistake.
Will Unity work on all of these?
Also, here is the page of PDADB.NET where you can make a selection: http://pdadb.net/index.php?m=pdachooser
There are A LOT of different chips being implanted into mobiles.
How is it possible to find where Unity is working?
Because first you must go and know which processors are ARM architecture or… is Unity working also on different architecture?
Then you must know if the device has OpenGL 2… right?
This is a damn huge work, a page with compatible devices should be held somewhere by the Unity Team or the users, I don’t know.
But I think it’s really a must do.
Hi,
I have a question about a tablet that I found. It is an android 2.2 Freescale IMX515 Cortex A8 1GHz with 512 MB of RAM.
The reseller says that is good also for gaming, so my question is:
Can I use it with unity?
If it is this one it looks like it runs OpenGL 2.0 so it should be ok but better wait for some answer 
up! please
No. As explained here, Unity Android (currently) requires an ARMv7-A processor to run (that is the Cortex-A ARM family).
That would be like mentioning every PC manufacturer (or even every PC model) under the Desktop requirements; there are just too many to mention. Instead we list the required hardware (and operating system). Obviously we could list the most popular devices but that wouldn’t help you in this case.
If it has decent OpenGLES capabilities (ie at least 1.1, and it should); then yes, Unity should work on that device. We currently don’t have such a device in our Android testing ‘zoo’, so I can’t vouch for how well it will run Unity content.
What about screen resolution?
We have found this, which runs with a screen 400x240, can Unity run on this resolution?
Unity is resolution agnostic; and so should your code be (if you don’t want to target each resolution explicitly). We use whatever resolution the GL setup gives us (by using the that can fudged a bit, but it still uses whatever the GL say is the ‘native’ resolution).