There is no solution. Decision are made. Buy a new iphones and get over it. [import]uid: 86417 topic_id: 8991 reply_id: 70032[/import]
(Personal view below)
I understand you guys might find it fustrating not to be able to develop for arm6 devices but there is good reason for this.
-
Arm6 surely doesn’t have long left, it will probably always hold a place in the cheap bargain smartphones but it doesn’t have a future in high performance smartphones.
-
Android devices on a whole… A lot depend on firmware these days (along with specs) I recently picked up a archos 101 android tablet, 1ghz single core armv7 processor and it’s performance was woeful. Angry birds was jerkier than on a samsung galaxy mini. So the point being, there are a lot of deciding factors on good performance on android devices, firmware being one, processor being the other.
Things are advancing but it’s always going to be harder to get your game to support android devices as opposed to ios devices. Thats the beauty of ios, you have x number of generations, the specs (processor, memory) is the same on each device (respective of generation) so there are less variables to contend with.
With android it becomes harder, what could run fine on a iphone 3g, might lag on a samsung galaxy S. [import]uid: 84637 topic_id: 8991 reply_id: 70039[/import]
Still now , I never found any solution for my demo project
When I compile with build process . I got extension file .
When I try to install on Motorola mile stone ARM 7 Processes .
I got 2 Kind of error
-
When install process . it stopped trigger error for Network info
-
ALLOW to control vibrator
I tested with 2 Night build version (Recent (For ARM 7) and 317 )of corona
Any one help to solve my problem !!!
[import]uid: 104397 topic_id: 8991 reply_id: 70047[/import]
I have now the same problem, in this moment my company are testing new tool CORONA SDK #fail bye, bye CORONA is not a good choice!! a lose a lot of potential customers… [import]uid: 7372 topic_id: 8991 reply_id: 93933[/import]
@Martin: This is called feedback - you get over it. It’s not our phones that are the problem it’s the majority of the userbase out there on ARMv6. All of our Android test phones work yet our customers are reporting problems on their phones.
@Danny: Thanks for posting the personal view good to see staff interacting on the board - ARMv6 devices are still being churned onto the market because they’re cheap to produce. The tech still has some legs left before it’s discarded.
Isn’t it possible for us to choose which architecture we want to target with the build? If we have non-intensive apps with no FPS dependencies and can put up with the touch bug we choose ARMv6. If you have a snazzy game with FPS requirements select ARMv7 for the build.
Right now we’re looking at rolling out a network services app for a mobile operator. No snazzy FPS requirements yet we’re stuck with a really old build of Corona for Android while iPhone gets all of the bells and whistles. The majority of their subscribers use cheaper newly released ARMv6 Android handsets which continue to sell so we can’t turn around and claim that ARMv7 is the minimum standard.
As far as the customer is concerned we wouldn’t have Android support if we can only build for ARMv7 yet subscribers can still go out and buy a brand new ARMV6 *Android* handset. [import]uid: 11393 topic_id: 8991 reply_id: 103437[/import]