Comments for Mihai Mobile

Comment on How to work around Android’s 24 MB memory limit by Dario Marcato

Dario Marcato — Fri, 11 Nov 2011 12:16:37 +0000

Hi! I’m trying to create a cache structure for images in native code but I’m having some trouble to find a way to allocate memory directly from c and use it for a Bitmap java object (your first method).
Can you share some snippets of code to help me doing that?
Thank you very much for your nice work!

Comment on Synergetic Stupidity in Java by Designing Scalable Code Generators for very large Java Projects « XTEXTerience

Fri, 04 Nov 2011 16:01:24 +0000

[...] Berlin, Heidelberg, 2005. Preda, Mihai: Synergetic Stupidity in Java. Mihai Mobile Blog. 2009. http://blog.javia.org/synergetic-stupidity-in-java/ MoreLike this:LikeBe the first to like this [...]

Comment on Nexus One display and subpixel pattern by Cómo calcular los píxels por pulgada de una pantalla | Smartblog

Cómo calcular los píxels por pulgada de una pantalla | Smartblog — Mon, 24 Oct 2011 17:37:17 +0000

[...] los blogs Expiance y Mihai Mobile muestran muy bien la diferencia entre los subpíxeles con la disposición tradicional RGB y la [...]

Comment on Nexus One display and subpixel pattern by Cómo calcular los píxels por pulgada de una pantalla | Smartblog

Cómo calcular los píxels por pulgada de una pantalla | Smartblog — Mon, 24 Oct 2011 17:37:17 +0000

[...] los blogs Expiance y Mihai Mobile muestran muy bien la diferencia entre los subpíxeles con la disposición tradicional RGB y la [...]

Comment on RenderFX: color vs. power by the closest thing to Flux (F.lux) on the Android phone I can find | ryan merritt

Tue, 18 Oct 2011 04:23:46 +0000

[...] can read about Render FX here, here, here, watch a video [...]

Comment on Android package name by Max

Max — Fri, 30 Sep 2011 12:43:10 +0000

Thanks, clear and very useful.

Comment on How to work around Android’s 24 MB memory limit by Mihai Preda

Mihai Preda — Thu, 25 Aug 2011 06:16:18 +0000

Java objects created through jni (e.g. newByteArray) are just normal java objects, thus count towards the java memory limit. You have to use malloc/free (or new/delete), which do not create java objects, to work around.

Comment on How to work around Android’s 24 MB memory limit by Peter

Peter — Wed, 24 Aug 2011 21:58:10 +0000

wow, great post.

will calling newByteArray in jni count towards the 24mb limit ? Or do I have to use malloc ?

If you have any code that can be shown ( both the opengl and jni stuff ), it would be very helpful

thanks,
Peter

Comment on How to work around Android’s 24 MB memory limit by Where there's a will, be fast » SDL for Android in 10 drunken steps

Where there's a will, be fast » SDL for Android in 10 drunken steps — Fri, 29 Jul 2011 15:50:32 +0000

[...] only real advantage of C++ for Android, aside from the lack of arbitrary memory limitations, is freedom, since JNI calls will likely slow small Apps down more the native code speeds them up. [...]

Comment on How to work around Android’s 24 MB memory limit by Shravan

Shravan — Mon, 18 Jul 2011 04:49:38 +0000

Thanks for your article Mihai.

“android.os.Debug.getNativeHeapAllocatedSize()” – statement helped us monitor memory leaks in our application and explore the fixes!