We’re having issues with lag on the android device after upgrading from Corona SDK 2011.703 to CoronaSDK 2012.926. We’ve also tried running on CoronaSDK-2012.894.dmg
We fixed all of the runtime errors and the app works great in the simulator. However, after building it to the Galaxy Nexus, the app is notably slower to the point where the game is unplayable. There are no errors in the terminal.
Thanks, [import]uid: 120903 topic_id: 31622 reply_id: 331622[/import]
bump [import]uid: 120903 topic_id: 31622 reply_id: 127669[/import]
bump [import]uid: 120903 topic_id: 31622 reply_id: 127669[/import]
any help? [import]uid: 120903 topic_id: 31622 reply_id: 128974[/import]
any help? [import]uid: 120903 topic_id: 31622 reply_id: 128989[/import]
any help? [import]uid: 120903 topic_id: 31622 reply_id: 128974[/import]
any help? [import]uid: 120903 topic_id: 31622 reply_id: 128989[/import]
bump? any help?
When we did adb logcat, we noticed that the game stops every couple milliseconds to do the garbage collection. Why does this happen on the newer build and not on 704?
This is driving us crazy. If anyone can shed some light on this issue, that would be great. Otherwise, we would have to release the game without Android, which means we are not benefitting from Corona’s cross platform build.
Any insight would be appreciated.
Thanks. [import]uid: 120903 topic_id: 31622 reply_id: 131512[/import]
Why not get .971, it’s the release candidate for the next stable build. It has many android fixes and enhancements in particular with audio. [import]uid: 19626 topic_id: 31622 reply_id: 131514[/import]
What version of Android is your Galaxy Nexus running? If it’s 4.0 (ICS), then I’ve seen in other forums that it can be quite slow. You should be able to upgrade the Nexus to 4.1 or 4.2 (Jelly bean) which seems to have sped thing up.
I only have a 2.3 (Gingerbread) device for my testing, and I don’t see any problems with performance running on a Galaxy S Wifi. I should be receiving my Google Nexus 7 this week which has 4.1 installed and if I have performance problems I’ll update this thread. [import]uid: 70847 topic_id: 31622 reply_id: 131535[/import]
bump? any help?
When we did adb logcat, we noticed that the game stops every couple milliseconds to do the garbage collection. Why does this happen on the newer build and not on 704?
This is driving us crazy. If anyone can shed some light on this issue, that would be great. Otherwise, we would have to release the game without Android, which means we are not benefitting from Corona’s cross platform build.
Any insight would be appreciated.
Thanks. [import]uid: 120903 topic_id: 31622 reply_id: 131512[/import]
Why not get .971, it’s the release candidate for the next stable build. It has many android fixes and enhancements in particular with audio. [import]uid: 19626 topic_id: 31622 reply_id: 131514[/import]
What version of Android is your Galaxy Nexus running? If it’s 4.0 (ICS), then I’ve seen in other forums that it can be quite slow. You should be able to upgrade the Nexus to 4.1 or 4.2 (Jelly bean) which seems to have sped thing up.
I only have a 2.3 (Gingerbread) device for my testing, and I don’t see any problems with performance running on a Galaxy S Wifi. I should be receiving my Google Nexus 7 this week which has 4.1 installed and if I have performance problems I’ll update this thread. [import]uid: 70847 topic_id: 31622 reply_id: 131535[/import]
I tried with v971. Some other bugs that we encountered are fixed but the game is still laggy on Android.
We’re using Galaxy Nexus with 4.1 (Jelly Bean).
Just FYI, we get the following log messages when we do ‘adb logcat’:
D/dalvikvm( 1526): GC_FOR_ALLOC freed 374K, 62% free 11529K/29767K, paused 18ms, total 18ms
D/dalvikvm( 1526): GC_CONCURRENT freed 395K, 62% free 11606K/29767K, paused 13ms+3ms, total 31ms
D/dalvikvm( 1526): GC_CONCURRENT freed <1K, 60% free 12024K/29767K, paused 13ms+3ms, total 32ms
D/dalvikvm( 1526): WAIT_FOR_CONCURRENT_GC blocked 12ms
D/dalvikvm( 1526): GC_CONCURRENT freed 513K, 60% free 11994K/29767K, paused 13ms+2ms, total 28ms
D/dalvikvm( 1526): WAIT_FOR_CONCURRENT_GC blocked 13ms
D/dalvikvm( 1526): GC_CONCURRENT freed 483K, 60% free 11984K/29767K, paused 12ms+3ms, total 26ms
D/dalvikvm( 1526): GC_CONCURRENT freed 851K, 62% free 11591K/29767K, paused 12ms+2ms, total 28ms
D/dalvikvm( 1526): GC_CONCURRENT freed 462K, 62% free 11532K/29767K, paused 2ms+4ms, total 21ms
D/dalvikvm( 1526): WAIT_FOR_CONCURRENT_GC blocked 14ms
D/dalvikvm( 1526): GC_CONCURRENT freed 398K, 62% free 11606K/29767K, paused 2ms+14ms, total 33ms
D/dalvikvm( 1526): GC_CONCURRENT freed <1K, 60% free 12024K/29767K, paused 2ms+4ms, total 22ms
D/dalvikvm( 1526): WAIT_FOR_CONCURRENT_GC blocked 18ms
D/dalvikvm( 1526): GC_CONCURRENT freed 513K, 60% free 11994K/29767K, paused 2ms+7ms, total 25ms
D/dalvikvm( 1526): WAIT_FOR_CONCURRENT_GC blocked 20ms
D/dalvikvm( 1526): GC_CONCURRENT freed 483K, 60% free 11984K/29767K, paused 12ms+13ms, total 42ms
D/dalvikvm( 1526): GC_CONCURRENT freed 851K, 62% free 11602K/29767K, paused 12ms+2ms, total 27ms
D/dalvikvm( 1526): GC_FOR_ALLOC freed 399K, 62% free 11529K/29767K, paused 18ms, total 19ms
D/dalvikvm( 1526): GC_CONCURRENT freed 395K, 62% free 11606K/29767K, paused 13ms+3ms, total 50ms
We get this every few milliseconds so it’s lagging quite a lot. Anyone else has some tips?
Cheers. [import]uid: 120903 topic_id: 31622 reply_id: 131625[/import]
I tried with v971. Some other bugs that we encountered are fixed but the game is still laggy on Android.
We’re using Galaxy Nexus with 4.1 (Jelly Bean).
Just FYI, we get the following log messages when we do ‘adb logcat’:
D/dalvikvm( 1526): GC_FOR_ALLOC freed 374K, 62% free 11529K/29767K, paused 18ms, total 18ms
D/dalvikvm( 1526): GC_CONCURRENT freed 395K, 62% free 11606K/29767K, paused 13ms+3ms, total 31ms
D/dalvikvm( 1526): GC_CONCURRENT freed <1K, 60% free 12024K/29767K, paused 13ms+3ms, total 32ms
D/dalvikvm( 1526): WAIT_FOR_CONCURRENT_GC blocked 12ms
D/dalvikvm( 1526): GC_CONCURRENT freed 513K, 60% free 11994K/29767K, paused 13ms+2ms, total 28ms
D/dalvikvm( 1526): WAIT_FOR_CONCURRENT_GC blocked 13ms
D/dalvikvm( 1526): GC_CONCURRENT freed 483K, 60% free 11984K/29767K, paused 12ms+3ms, total 26ms
D/dalvikvm( 1526): GC_CONCURRENT freed 851K, 62% free 11591K/29767K, paused 12ms+2ms, total 28ms
D/dalvikvm( 1526): GC_CONCURRENT freed 462K, 62% free 11532K/29767K, paused 2ms+4ms, total 21ms
D/dalvikvm( 1526): WAIT_FOR_CONCURRENT_GC blocked 14ms
D/dalvikvm( 1526): GC_CONCURRENT freed 398K, 62% free 11606K/29767K, paused 2ms+14ms, total 33ms
D/dalvikvm( 1526): GC_CONCURRENT freed <1K, 60% free 12024K/29767K, paused 2ms+4ms, total 22ms
D/dalvikvm( 1526): WAIT_FOR_CONCURRENT_GC blocked 18ms
D/dalvikvm( 1526): GC_CONCURRENT freed 513K, 60% free 11994K/29767K, paused 2ms+7ms, total 25ms
D/dalvikvm( 1526): WAIT_FOR_CONCURRENT_GC blocked 20ms
D/dalvikvm( 1526): GC_CONCURRENT freed 483K, 60% free 11984K/29767K, paused 12ms+13ms, total 42ms
D/dalvikvm( 1526): GC_CONCURRENT freed 851K, 62% free 11602K/29767K, paused 12ms+2ms, total 27ms
D/dalvikvm( 1526): GC_FOR_ALLOC freed 399K, 62% free 11529K/29767K, paused 18ms, total 19ms
D/dalvikvm( 1526): GC_CONCURRENT freed 395K, 62% free 11606K/29767K, paused 13ms+3ms, total 50ms
We get this every few milliseconds so it’s lagging quite a lot. Anyone else has some tips?
Cheers. [import]uid: 120903 topic_id: 31622 reply_id: 131625[/import]