Hi folks, not sure if this a ‘known’ issue, I saw some older posts related to this, but figured I would mention I’m seeing this broken in rc2 on android.
Essentially, If I create a packed blender file, and convert it to .j30, when I attempt to load the j30 on android it fails with out of memory.
I/dalvikvm(13312): “GLThread 2610” prio=5 tid=11 RUNNABLE
I/dalvikvm(13312): | group=“main” sCount=0 dsCount=0 obj=0x412af470 self=0x5c8f6a70
I/dalvikvm(13312): | sysTid=13334 nice=0 sched=0/0 cgrp=apps handle=1457649272
I/dalvikvm(13312): | schedstat=( 14954983000 2379301000 12755 ) utm=1422 stm=73 core=0
I/dalvikvm(13312): at java.io.ByteArrayOutputStream.expand(ByteArrayOutputStream.java:~91)
I/dalvikvm(13312): at java.io.ByteArrayOutputStream.write(ByteArrayOutputStream.java:201)
I/dalvikvm(13312): at com.jme3.export.binary.BinaryImporter.load(BinaryImporter.java:235)
I/dalvikvm(13312): at com.jme3.export.binary.BinaryImporter.load(BinaryImporter.java:126)
I/dalvikvm(13312): at com.jme3.export.binary.BinaryImporter.load(BinaryImporter.java:110)
I/dalvikvm(13312): at com.jme3.asset.DesktopAssetManager.loadAsset(DesktopAssetManager.java:283)
I/dalvikvm(13312): at com.jme3.asset.DesktopAssetManager.loadModel(DesktopAssetManager.java:369)
I/dalvikvm(13312): at com.jme3.asset.DesktopAssetManager.loadModel(DesktopAssetManager.java:373)
On the desktop the j30 loads just fine.
anyways for now I’m just unpacking blender file,and its working fine on android 
so not much of blocker.
Cheers
Dano
What do you mean by “packed”, you mean the textures are included in the file? Yeah, thats suboptimal, you should avoid that.
Probably related to this:
http://code.google.com/p/jmonkeyengine/issues/detail?id=477
I don’t recommend using packed textures at all. Not with Android or Desktop.
Fair enough, I only packed the textures into the blender file, as was moved the project to different folder, so the image references were wrong. (so unpacking it appears after appears to have solved the issues (except the textures are now under /assets/models/textures/ vs assets/textures).
not sure if that’s really an issue or not, everything appears to load up properly regardless.