I am developing a game on Galaxy S. Now a days, I am prototyping the game. It runs well on HTC nexus.
But the prototype goes down very frequently on Galaxy S. Will you support the Galaxy S ?
We’ve been having similar troubles with the Galaxy S. I can usually load our menu level, but once we try to load into a game level it will just exit out.
The Unity folks are aware of some serious problems on Samsung Galaxy devices and they are working on a fix for it.
Yes, we have two developers working almost exclusively on the Samsung Galaxy S crashes. Please stay in touch, we’ll release a build with a fix over the Android beta lists when we have it. We’ll also announce the fix on this forum.
Anyone eager to participate in Android beta, please mail me at oleg@unity3d.com
Only Android license owners are allowed at this point.
While I don’t have the device nearby to check it out myself, but if
there are some curious minds eager to try the new official Samsung 2.2
firmware out:
http://briefmobile.com/galaxy-s-updated-to-android-2-2
Android 2.2 JIT compiler
Adobe Flash Player 10.1 compatibility
New Android Market with auto-updating
Speed improvements
Please share your experience 
The new firmware should fix the crashes
so far I managed to test the official 2.2 firmware:
Freekick madness - does not crash
Zombie Defence - does not crash
castle warriors - does not crash
Thanks, but will Unity ever work with 2.1 on Galaxy S or will we have to require 2.2?
Hi does this crash impact all versions of Galaxy S phones or does it impact only certain carriers? I noticed many people are updating Captivate to Android 2.2 with root. Just thinking of picking up more Android phones to do testing with.
Does it mean that phones prior to 2.2 may not have multi touch? I understand that some models don’t support mult touch period.
Sorry I very new to Android and I’m a Unity iOS Pro, and Android Pro user. Thanks.
Yes, this crash impacts all versions of Galaxy S phones. If the 2.2 update proves to be a solid fix, then you might want to consider requiring 2.2 or higher when you publish your app to the market. There are a LOT of these devices out there, and they will all give you angry 1-star reviews when your game crashes on them because they haven’t updated to 2.2.
We can only hope Samsung starts doing OTA updates soon, instead of relying on Kies…
fully agree here … finally got my Samsung ADB driver NOT to fail on install after trying for a whole good day. Kies - the most horribly bloated and badly programmed Software i ever came across - still does’nt find my Galaxy → MTP driver constantly keeps failing …
This is one of the rare cases i really can say that Apple does a good job in that regard …
By the way - reason the ADB Drivers failed on install, was something in my Windows media player 11 install. I do not use this thing but had it installed. After i re-installed WMP11 , the ADB driver finally started to work…
Updating to 2.2 via Kies for us U.S. users supposedly hoses up your phone (such as removing Android Market, among other problems), but I haven’t tried it myself out of fear. Has anyone in the US tried it yet?
Does that mean that Unity is officially not working on this problem anymore and just relying on 2.2 as the fix for this issue?
its a problem with Samsung fucking up the memory - paging handling on Android among other things. Samsung themself rely on 2.2 to fix it, they didn’t dedicate any time to fix it on 2.1 at all actually.
As Mantas replied over the beta list:
So if this is simply a problem with Samsung 2.1, are other games and applications not created with unity crashing as well? I don’t personally have this phone (so if someone could chime in with personal experience feel free) but a friend of mine does and the only app she has problems with is our unity built app.
Android users are pretty used to the unpredictable app experience by now but generally blame the apps. It’s for this reason I am holding off the android port till last, hopefully in about a year most people will be 2.2 and it will finally be a device that works better. Google’s fault 
Yes, afaik both Skype and Mozilla suffers from this problem as well (on GalaxyS/Vibrant running 2.1).
I have a Galaxy S phone (Vibrant) running 2.1 and I don’t have any crashing issues with non-Unity games for the most part. Of course there’s the odd crash here and there but games like Angry Birds, Fruit Ninja and Dungeon Hunter all work extremely solidly. So while something is obviously jacked in Samsung’s 2.1 kernel it’s not something that applies universally to all Android games.
The good news is that 2.2 should be getting rolled out soon.
Lets hope they can resolve the stuff soon. Galaxy Tab is on 2.2 already so it shouldn’t be that hard as it is just a 7" Galaxy S (given we talk about the real galaxy s here, not the US spinoffs which have custom roms and will just wait another 2 months thanks to it)
Its sad that something that technically could have crushed anything got crushed by major issues that are kind of laughable as they were not android issues but custom kernel fuckups from Samsung (missuse of flash as “paging ram” → speedfix and the still not working acceptable gps incapabilities)