Unity Android OS version support?

I realize this is probably written somewhere but I couldn't for the life of me find it...

Anyone know what versions of the android OS will actually play a unity android build?

I'm going to assume 2.1 and 2.2 but anything lower?

thanks in advance

 

Ok sounds good, thanks for the quick response

 

So there are no plans for Unity Android to support Gingerbread?

 

Ah ok, that's a relief. Thanks for the clarification.

 

our programmer was saying that he was getting errors at one point that suggested that unity was building for 2.2. Is there a setting somewhere that needs to be changed in order to build for 2.1 or 2.0?

 

Alright so then it's simply up to us to make sure we don't use features that are not supported in our lowest target OS?

 

Did something change with the newest release? because I can't even get a simple scene to install correctly on my device anymore. It either tells me that it,s installed, brings up the splash screen and crashes, or simply won't install.

are there perhaps settings somewhere I need to adjust?

 

I'll have a look at the release notes to see if I notice anything. I believe the beta 7 builds are not working but a few I made from beta 5/6 are.

I'm thinking, because I trust the unity people would test this kind of simple function, and because no one else seems to be having any issues, it has to be one of 3 things:

1. I'm simply doing something wrong.

2. something has changed, potentially in 3.7, that is setting some default setting I need to disable.

3. my device is a little bit of a special case and isn't playing nicely (iRobot, 2.1 Eclair)

I'm going to spend some time trying to be absolutely sure I'm not doing anything wrong, and If I don't find a solution in the next day or so I'll send a bug report.

thanks for the help!

 

ahhh, that would explain it #3 it is, with maybe just a bit of #1 .

Thanks a bunch for the help it's really appreciated. Hopefully this won't be an issue for us.

 

... I wonder why the early ones work?

 

I'm just wondering - as a galaxy s owner.... will unity android compile ok for the ARM Cortex A8 1GHz?

 

Where might i be able to get my hands on these?

 

I'm happy to test apps on the galaxy s for you.

Just shout in my direction

Tony

 

The galaxy s is at the time the only device that has a reasonable GPU for its screen resolution, it uses the successor of what apple has been using the past 18 months, the SGX540 (over the SGX535 used by apple)

For the android side thats actually pretty uncommon at least up to now cause most use some other gpus as those qualcom brings with their cpus directly etc.

that being said, that shouldn't make a difference unless the ogl es driver is fu** up

 

Hmm is the java interfacing/plugin stuff is documented anywhere?? Sounds really interesting...!

Thanks!

 

The answer to my own question lies here:

http://forum.unity3d.com/viewtopic.php?t=64443

 

Ok so, it's 2 weeks later I have a new 2.1 device with an ARM 11 processor and I still can't get unity to build an app that will successfully install. I'm almost certain that it's because unity is using the updated 2.2 sdk to compile but I can't find a way in either the sdk manager or in unity to force it to only use 2.1.

Any advice would be greatly appreciated.

 

Ok... so no to ARM 9 or ARM 11 but yes to ARM 6 or ARM 7 (but only those two) and all of the Cortex versions? Or only a few of those as well?

Thanks for the info... Hopefully I'll get my head wrapped around this stuff soon.

 

ohhh... wait, I had a look at that wiki link. I think I get it. I was looking at a different diagram that was confusing me a little.

correct me if I'm wrong.

unity supports: ARMv7-A, ARMv7-R, ARMv7-ME, ARMv7-M, ARMv6-M,
which includes: Cortex-A8, Cortex-A9, Cortex-A9 MPCore, Cortex-R4(F), Cortex-M4, Cortex-M3, Cortex-M0, Cortex-M1.

right? so those are the only ones?...

 

Also, if I may ask, why exactly does unity only support the above processors? is there something special about them that unity requires? or is it more to do with performance quality?

 

Unity requires Cortex family processors for the best experience. Weaker processors lack fast FPU that is required (mostly for sounds) for the best performance. And also video accelerators in ARMv6-only CPUs are commongly too slow.

 

The problem that I'm having is that the application fails to install and if by chance it does, it simply brings up a black screen, waits a second and then bounces back to the device home screen.

This to me feels less like a simple quality issue and more like it's simply not working. If I was using an old joke of a processor I wouldn't be surprised except from what I can tell the ARM 11 processors aren't that far off of the unity supported ones.

does unity have a built in mechanism for preventing an application from installing / running if it detects that the processor isn't supported?

 

Ok I see,

I'm not overly concerned about the market because we aren't developing for the market. we're developing for a specific hardware only and it's looking like the client wants to use an ARM 11 processor. Is there any way at all i could get unity to ignore the device filter so we can at least see what it looks like / show the client something? I tried using the universal / emulator setting but this doesn't work either.

p.s I really appreciate all of the help on this one

 

CPU specs:

Processor : ARMv6-compatible processor rev 6 (v6l)
BogoMIPS : 499.71
Features : swp half thumb fastmult vfp edsp java
CPU architecture: 7
CPU revision : 6
Hardware : Telechips TCC89/91/92XX Demo Board

and I'll send logcat info as soon as I get it working...

 

ok so we got it working... this is the error I get when It has installed and I try to run it. The app starts, I get a black screen and then it crashes and jumps to the device home screen:

D/Zygote ( 2819): Process 6717 terminated by signal (4)
I/ActivityManager( 2835): Process com.BlackCherry.BabyToy (pid 6717) has died.
I/UsageStats( 2835): Unexpected resume of com.fede.launcher while already resume
d in com.BlackCherry.BabyToy
W/InputManagerService( 2835): Window already focused, ignoring focus gain of: co
m.android.internal.view.IInputMethodClient$Stub$Proxy@44f65358

I'd be lying if I knew said I what it meant.

I'm going to keep playing with this and hopefully get a few different scenarios going. I'll post up anything that might be different/helpful.

 

I've attached 2 logs. One is the error I get when it fails to install and one is the error I get when it fails to run. It seems to be an issue with the apk not being compiled the way the device wants it to be...

 

Right, so up until now I wasn't using the build and run option to test the app, I was building an apk then transferring the file to the device and installing it there through the device options. Sometimes when I tried to install the app, the device would report that it had installed and others it would report that the app had not installed. If it did happen to report a successful install it would fail to run when I attempted to open/launch it.

That's what I thought, however I can't even get the application to install (using the method i described above) when I use the 'Universal/Experimental' setting.

BUT It will install and run when we use the method you outlined (not sure exactly what the difference is but, oh well). This answers a lot of questions and will give us a nice solid starting point. I realize that our problems before were more than likely related to the processor but I've included the logcat for kicks.

Thank you so much! I can't tell you how much I appreciate all of your patience with me and this issue.