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?
Unity uses the very latest SDK to take advantage of the features present there (like installing to sdcard etc). This means that the development computer needs to have SDK 2.2 installed, but this does not mean that the app won’t work on devices with earlier versions. The new features of Froyo will simply be ignored when run on such a device.
I would say its only possible to be using newer features if you inject your own java code using plugins (or access java from a native plugin). And then you would need to put a custom AndroidManifest.xml in the Plugins folder with the correct settings.
Basically; with “normal” use of Unity you won’t run into this problem.
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?
Not a whole lot except the adding of Device Filter and support for License Verification Library. Please have a look at the release notes for a complete list of changes affecting Android.
The RC1 one has been tested, and should build a simple scene without hiccups…
That sounds like more than one bug if thats the case… What kind of device are you using?
You can have a look under Player Settings; those are the only setting relevant for Android.
What does the logcat tell you?
If you build&run the exact same project in beta7 does it work? If so, please submit a bug report and attach the project.
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:
I’m simply doing something wrong.
something has changed, potentially in 3.7, that is setting some default setting I need to disable.
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.
A8 is an ARMv7A class CPU, so no worries. (ARM architecture family - Wikipedia) But we’ve had isolated crash reports with apps running on Galaxy S (Vibrant) and we’re looking into that. Hopefully we will be able to resolve it quickly…