Yeah, I just got done reading it and was going to come back and say “never mind”. Now I just have to get a hold of a 2.2 or better device. Not sure how i’m going to do that 
Thanks [import]uid: 19383 topic_id: 4508 reply_id: 28557[/import]
I’m developing with the Target OS Compatibility set as 2.2.
I can assume that despite this, your proposal is more than just a target OS compatibility – it’s fully embracing 2.2 as the base, which in turn will allow Corona Apps to be much more optimized.
If I’m on base, then I would like to honestly say that it wasn’t clear to me from your post.
I took away that apps developed with compatibility for 1.6 and other lower versions had poor performance, and kept the assumption that 2.2 should run fine. [import]uid: 19875 topic_id: 4508 reply_id: 28572[/import]
I did the same and had the same experience.
If I might say – the advantage of allowing registered users to download daily builds is nice – but at this point in Corona’s development – people who have not purchased Corona are people who have not committed to Corona.
I am looking into a few other options, simply because I have a task that I need to accomplish and based from what I can see with the Corona SDK demo – my app is not working out on Android.
With daily builds that are still under the same limitations, this would increase my loyalty to Corona and my desire to purchase the SDK upon completing my app.
I don’t think that daily builds is an incentive to register. I think wanting to publish your app is [import]uid: 19875 topic_id: 4508 reply_id: 28573[/import]
I agree with what you’re saying - I think the problem from their aspect is it would cause a support nightmare. All the n00bs would download the last daily, and if there were a bug it would fill the bug base and more likely forums.
Then you’d get all those people complaining that there’s no documentation for the feature that was added last night 
There should probably be more regular release builds instead I think. To me it looks like most dailies have less bugs than the last release. [import]uid: 8872 topic_id: 4508 reply_id: 28606[/import]
touch and holding screen still is a big problem with CORONA Android.
We still facing this error with lastest daily build and Android 2.2 device.
Should we create some kind of device black list for faster testing purpose? [import]uid: 9190 topic_id: 4508 reply_id: 29547[/import]
having tha same problem here, with a pinball-like game.
When you touch and hold in place the string, (but i think more when you go offscreen with your finger), the movement of the ball is slow and jerky, like a major lag.
What i have seen too is that the simulator on Mac is fluid, but the one on windows is lagging. An OpenGl issue? [import]uid: 44010 topic_id: 4508 reply_id: 29578[/import]
yo do not have the updated ARM7 build. We have not released it yet. So you are still having issues. We fixed a bunch of this stuff. But the ARM7 2.2 is *not* on the daily build.
http://developer.anscamobile.com/forum/2011/03/01/android-update-please-…
C [import]uid: 24 topic_id: 4508 reply_id: 29614[/import]
I’m having the same issue in iPod 3 with iOS 4.3.
I’m drawing an line based on the touch points and there is a delay starting to get the touched point.
I’m will prepare a sample code to post here.
[import]uid: 6732 topic_id: 4508 reply_id: 32674[/import]