I’ve just compiled the latest build from Git in order to try it out on our new Samsung Galaxy S3 (Android 4.1.1) at work.
So, after struggling with setting up the ant build script on my Mountain Lion (just a tad… no worries), I’ve finally managed to compile the juce_jni module and to deploy the JuceDemo on the phone successfully.
To be honest, I didn’t expect that to be that easy.
In fact, I had a very bad experience last year when I tried building that up from scratch… until I finally reached the point of starting to tear my hair out (which turned out to be damn painful indeed cuz, judging by your avatar, it seems to be as long as your Jules ).
Anyway, so no big issues encountered along the road on that side…
But god! It turns out to be slow as hell so far.
The default demo (without any advanced animation enabled) hardly reaches the 10 FPS, and it drops to ca. 3 FPS if I enable all the fancy animations in the bottom-right corner.
I first compiled it with the SDK r10 so I thought this could have explained such bad performance, so thereby I’ve updated the project to build for the SDK r16 (Android 4.1.2)… and no big changes here the performance are still unbelievably slow.
Am I the only one experiencing that?
I thought the Samsung Galaxy S3 was supposed to be renowned for being a quite powerful smartphone, if not the best actually.
PS: Originally, I wanted to upload the tiny video that I’ve made earlier but it seems the 17 MB are perhaps a bit too much for the forum. Too bad.