Force close on Defy

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Open the app.
2. The force-close window appears, while on the background
the app's GUI shows up, but the sphere doesn't.

What version of the product are you using? On what operating system?
Motorola Defy, stock Eclair (2.1)

Original issue reported on code.google.com by runnerbl...@gmail.com on 24 Dec 2011 at 8:27

[GoogleCodeExporter]

I've looked at the req. for this app. Moto Defy is running android 2.1, with 
OpenGL ES 1.1, so the tehnical specs match. Merry Christmas, I hope to see your 
app being able to run on Defy too, as a 3D modeling/sculpting app is what I've 
wanted for myself since I have Android

Original comment by runnerbl...@gmail.com on 25 Dec 2011 at 12:26

[GoogleCodeExporter]

Based on your description and the error reports i got from the market, it looks 
like a memory issue, ie one of the main trouble i had while developing 
truesculpt. Let me explain : even if an Android device has 512Mo of RAM, for 
one strange reason Android will only let you use 16Mo or 24Mo for each 
individual application (depending on your device/manufacturer).

The problem is that sculpture is a pretty memory hungry activity and it is 
difficult to optimize for both speed and memory efficiency. The app is 
frequently reaching limits and i have to dynamically strip history to remain 
inside the 24Mo allowed RAM.

If my guess is right, the harcoded device dependent application memory limit of 
the Defy must be smaller (16Mo) than the one of the Samsung Galaxy S (24Mo) 
which is the only one i tested before releasing (and where it works correctly).

To test my hypothesis and try to solve your problem, i will send you by mail a 
modified truesculpt version with a much smaller initial mesh (less subdivided). 
The sculpture will be more coarse and ugly (5000 triangles instead of the 20000 
initial default) but it should work , otherwise i'll have to find another idea 
;-)

The pb is that i can only do this when i'm back from my christmas holidays and 
can reach my good old home dev computer, this means not before the 3rd of 
January. Sorry you'll have to wait a little.

The only true workaround seems to develop in native C++ using the NDK instead 
of using Java, so i can allocate more memory, but i won't do this since this 
means starting from scratch and using a more difficult language/toolchain.

Happy holidays, regards,
Fabrice

Original comment by fabrice....@gmail.com on 28 Dec 2011 at 6:55

[GoogleCodeExporter]

Thank you for the fast response. I no longer need help as I changed the phone 
with a lg optimus hub, which gives truesculpt enough memory to run :) However, 
it would be wonderful if I could also test it on Defy.

Also, even if NDK is much harder to use than SDK, consider the speed and the 
features you could add to your already marvelous app.

Happy holidays,
Thank you for this really awesome code,
Alex

PS: is there any way you could also make a subdivision modeler? :D Android 
really lacks 3D modelers, we're really lucky with your sculpt app.

Original comment by runnerbl...@gmail.com on 31 Dec 2011 at 12:37

[GoogleCodeExporter]

I'm happy you got a brand new phone and could enjoy truesculpt in good 
conditions. It's always nice and encouraging when people likes what your doing.

As I got no real workaround for the defy and I can't test easily (no device), I 
will temporarily exclude this device from the market for this app. This will 
prevent other persons from being disapointed. Meanwhile, I'll try improve my 
OutOfMemory exceptions handling (both for RAM and GPU memory).

About the NDK, I didn't used it because my day job consists in working with C++ 
(in a very different application domain), I know it very well but I wanted to 
train to a more fun and recent langage/framework like java and the android SDK. 
I know this is probably a bad technological choice for this kind of demanding 
application but I wouldn't have started this project otherwise.

I already tried to integrate dynamic subdivision to the project but I 
discovered the memory issues at this moment and this prevented me to go further 
and integrate this into the release. Maybe I'll find a way to do this more 
efficiently and have some time to code it. The purpose of the project is not to 
mimic a real complete 3D modeler (where desktop version are way more precise 
and efficient), but rather to try to feel the fun part of sculpting on a 
portable device.

This project is very young and uncomplete (published 1 month ago), but as it is 
opensource, if you want to try to modify or add features, I would happily 
integrate your changes to the source code and publish them (after a carefull 
review ;)). Any help is welcome !(see here 
https://code.google.com/p/truesculpt/wiki/HelpNeeded). 

And thank you for updating your (previously bad) comment on the market, I 
appreciate it! 

Regards,
Fabrice

Original comment by fabrice....@gmail.com on 1 Jan 2012 at 1:14

• Changed state: Started

[GoogleCodeExporter]

I am not good at programming, just an intermediate highschool C++ programmer. 
Instead, I'll try making some tutorials, and post some things.

I'll send you everything on email/the gallery :D

Original comment by runnerbl...@gmail.com on 13 Jan 2012 at 9:29

[GoogleCodeExporter]

Hello I am Spanish sculptor and would be interested in participating in the 
project developing sample models

Original comment by antoniod...@hotmail.com on 23 Feb 2012 at 10:03

Attachments:

• Mesh.obj