Issues with Droid

Solar2D Daily Builds and Public Releases
#1

It seems there’s some serious issues with Droid 2 and droid X phones.

This post highlights one issue:

http://developer.anscamobile.com/forum/2010/10/22/bad-performance-motorola-milestone

Building for 1.6 seems to work fine for every other phone I have tried, but on the milestone, droid 2 or droid X there are very frame rates and lots of lag.

Worse, building for 2.2 causes force closes when tapping the screen too much.

I’ve had to highlight droid phones are not supported in my app for now.

There’s no workaround to supporting droid at this time :confused:

The problem is there on all corona builds I can find - including 301.

Help! [import]uid: 8872 topic_id: 6864 reply_id: 306864[/import]

#2

We can add Nexus S to the list of phones with a problem :open_mouth:

Its definatly the touch event fix you guys did in the daIlys:

302 (or any daily):
1.6 build - slow and choppy
2.0.1 build - misses some touch events, and a little slow
2.2 - works but FC on too many taps

268 (stable)
1.6 build - slow and choppy (?? why?!)
2.2 build - works fine

The problem is the 268 build doesnt have the new setidletimer working.

This is a critical issue for me now, as its not just motorola phones that have this issue. I expect there’s even more phones that have this issue. People will assume my game is poorly coded at this rate.

HELP!

Would it be possible to have a daily with the touch fix removed or toggleable? in code or lua config? [import]uid: 8872 topic_id: 6864 reply_id: 24053[/import]

#3

Add no loading icon on webpopups and webpopup input boxes not bringing up the keyboard when you touch them. :frowning: [import]uid: 7143 topic_id: 6864 reply_id: 25751[/import]

#4

Hi, Ansca mobile said on there blog that they will select the easy way for them: abandon Android OS version 1.6 :smiley:

@AnscaMobile: we need all Android OS’s version will be supported and we also need Android 3.0 as soon as possible. Do not make them as slow as Game Center support.

BTW, both of 02 errors (I reported) DO NOT have any fix at all, they still remain in current version of CORONA SDK
(1)randomize losing texture in Milestone (any Android Version) and
(2)performance issues in some case with AOS 1.6 build.

However, CORONA SDK is really amazing, big thanks to Ansca Mobile.
[import]uid: 9190 topic_id: 6864 reply_id: 26040[/import]

#5

An update to the Corona SDK Android update. http://bit.ly/ffl5qP Feel the need for speed? [import]uid: 24 topic_id: 6864 reply_id: 26206[/import]