First build on Android, way too SLUGGISH... works well on iOS.

Hi,

My app works well on iOS, tested on iPod Touch and iPhone 3GS. Then I built it for Android and tested on an Acer Iconia A100 tab (Android v3.2.1). It is way too sluggish.

I’m using storyboard API, and the screen transitions (slideLeft and slideRight) are very slow. I have a spinning wheel in one scene which the user can drag and spin. That too is very slow.

I read through the forums and saw Carlos’s post that ARMV6 is not supported. So I checked the CPU of the tablet, it is Nvidia Tegra 2 T20. That’s an ARMV7 CPU.

I have a feeling that I’m missing something very obvious here. Please help…

Corona build 799.

Regards,
Kapil
[import]uid: 135671 topic_id: 26758 reply_id: 326758[/import]

iOS with Corona is super fast for some reason. When you port it over to Android it’s slow. I have never understood this but I’ve always just assumed it’s a bad port or their Android builds don’t take advantage of all hardware components. I would love to know why Android Corona builds are slower than iOS builds.

Regards,
Jordan Schuetz
Ninja Pig Studios [import]uid: 29181 topic_id: 26758 reply_id: 108552[/import]

I second that. I tested my interactive book app on Acer A500 tablet with 1 GB DDR2 RAM and the CPU is Dual-core 1 GHz Cortex-A9 and it’s a little slow in respond even I already reduced image/audio file sizes so much. I think Corona SDK for Android isn’t optimized enough. I hope they’re working on it to improve this issue really soon. [import]uid: 146445 topic_id: 26758 reply_id: 108567[/import]

I tested my app, exact same APK, on a Samsung Note and it works perfectly. So I wonder is it the Acer tablet’s hardware that’s causing the sluggishness or the Android 3.2.1?

The Acer tablet A100 also uses the Nvidia Tegra 2 T20 CPU which is a Dual core 1GHz Cortex-A9.

@willandgolf - you said “it’s a little slow in respond” - I am seeing super slow sluggishness. My app on my Acer tablet is absolutely unusable, but on Samsung Note it is very smooth. So the question I want to ask you is have you used the Storyboard API and its slideLeft/slideRight transitions? Your input here will really help me. Thanks!

Regards,
Kapil [import]uid: 135671 topic_id: 26758 reply_id: 108626[/import]

There have been issues with Corona apps running on Tegra 2 based devices in the past and I know that even Android itself has issues on that hardware. My wife has a Droid X2 (which uses Tegra 2) and it’s sluggish in regular use let alone running apps. I would suggest trying build 819 or newer since they fixed a regression bug that slowed image loading on Android by 2x (it might not fix the problem but it certainly wouldn’t hurt). Android performance with Corona is definately not as fast as iOS but it shouldn’t be as bad as you describe on most devices. On my Galaxy S phone which has a much slower processor than Tegra 2 everything runs smooth unless I get a little crazy with physics. [import]uid: 27965 topic_id: 26758 reply_id: 108671[/import]

@calebr2048 - Yes you are right. I tried with build 821 and it is MUCH better now. Actually it is not sluggish now at all, although still not as smooth as iOS. But this acceptable.

Now the only problem is, with 821 or 819, my iOS build doesn’t work on iPhone 3GS. That’s a different issue, which I think is a bug. It works on iPod Touch but crashes on launch on iPhone 3GS, at a simple group:insert() function call.

So I will watch out for next few daily builds if a fix for that bug comes along.

Cheers!
Kapil
[import]uid: 135671 topic_id: 26758 reply_id: 108683[/import]

@kapil.pendse I am using Director Class with Kwik to build my book app so I have not touched any codes. The transitions and the interactions are not sluggish, but it takes some secs to respond to the touch (like tabbing the buttons), then fire the transitions. So far, the app runs smoothly on my A500, except that it slow in respond on touch.

I asked Alex, the Kwik creator. He suggested that the newest SDK build might help. the performance also differs from device to device.

I haven’t tried the Storyboard API yet. I have heard that it still has bugs so I wait.

Hope this help

Will and Golf [import]uid: 146445 topic_id: 26758 reply_id: 108722[/import]