However, i tried to load the model you provided with 1.5 on the actual phone and 2.1 and 2.2 in the emulator (Both with default setting, i.e. no heap adjustments made). All loaded fine, so i can't reproduce this problem. If native memory size (and not java heap size) is the actual problem (and it looks like it), it may help to do a <yourObject>.forceGeometryIndicies(true);...but that will make the compilation process much slower in return. It will use less native memory though.