Joshua Quick,
We have gotten feedback from the users and error reports. The error were reported with build 937 and 902. We do not have the phones to test with, but hoped you had access to some. [import]uid: 88922 topic_id: 26169 reply_id: 129563[/import]
dirtyBit,
Most of the devices that you have listed (the SGH and LG models) are using the “PowerVR SGX 540” GPU, which is the same GPU that the Kindle Fire and Nook Color is using. That GPU has been known to cause the error that you’ve reported. We’ve fixed that issue since release build #894, which was months ago.
Are you sure those errors are not coming from older builds?
We don’t have any of the devices that you’ve mentioned to test with. Do you? Are you able to reproduce this issue yourself?
[import]uid: 32256 topic_id: 26169 reply_id: 129551[/import]
Joshua Quick,
We have gotten feedback from the users and error reports. The error were reported with build 937 and 902. We do not have the phones to test with, but hoped you had access to some. [import]uid: 88922 topic_id: 26169 reply_id: 129563[/import]
Have you guys got a look at this yet? [import]uid: 88922 topic_id: 26169 reply_id: 131090[/import]
Have you guys got a look at this yet? [import]uid: 88922 topic_id: 26169 reply_id: 131090[/import]
No, because we can’t reproduce this issue on our end.
Can you reproduce this issue on your devices? [import]uid: 32256 topic_id: 26169 reply_id: 131125[/import]
No, because we can’t reproduce this issue on our end.
Can you reproduce this issue on your devices? [import]uid: 32256 topic_id: 26169 reply_id: 131125[/import]
We still haven’t got the devices, but get tons of error messages about it from Google as we can’t filter out the OTHER devices. We hope that you will look into this as this probably is a problem for lots of your paying users. [import]uid: 88922 topic_id: 26169 reply_id: 131749[/import]
dirtyBit,
So far, you’re the only person reporting this issue. I’m starting to wonder if your app is being built with an older version of Corona and you don’t even know it. I’m not trying to be difficult, but this is an issue that I know we’ve solved and we’re not receiving tech-support issues about this anymore. Unless of course you’ve found an edge case, in which case please prove me wrong.
So, that said, would you mind posting your “build.settings” file contents here please?
If it contains a [lua]customBuildID[/lua], then it is using an older version of Corona and needs to be removed.
I also recommend that you add the following line to your app to prove that your app is built with the newest Corona version…
[lua]print("*** Corona Build #" … tostring(system.getInfo(“build”)))[/lua]
Run the above on your Android device and have a look at the log. You can view the log via the Android SDK “adb logcat” or “ddms” tools.
[import]uid: 32256 topic_id: 26169 reply_id: 131790[/import]
We still haven’t got the devices, but get tons of error messages about it from Google as we can’t filter out the OTHER devices. We hope that you will look into this as this probably is a problem for lots of your paying users. [import]uid: 88922 topic_id: 26169 reply_id: 131749[/import]
dirtyBit,
So far, you’re the only person reporting this issue. I’m starting to wonder if your app is being built with an older version of Corona and you don’t even know it. I’m not trying to be difficult, but this is an issue that I know we’ve solved and we’re not receiving tech-support issues about this anymore. Unless of course you’ve found an edge case, in which case please prove me wrong.
So, that said, would you mind posting your “build.settings” file contents here please?
If it contains a [lua]customBuildID[/lua], then it is using an older version of Corona and needs to be removed.
I also recommend that you add the following line to your app to prove that your app is built with the newest Corona version…
[lua]print("*** Corona Build #" … tostring(system.getInfo(“build”)))[/lua]
Run the above on your Android device and have a look at the log. You can view the log via the Android SDK “adb logcat” or “ddms” tools.
[import]uid: 32256 topic_id: 26169 reply_id: 131790[/import]
Hi,
I can see that it could look that way, if this is something you already have fixed. If there is anything more we can send just name it. Hope this helps some.
build.settings
settings =
{
android =
{
versionCode = "11",
usesPermissions = {"com.android.vending.BILLING",},
},
iphone =
{
plist =
{
UIAppFonts =
{
"BradyBunchRemastered.ttf"
},
UIApplicationExitsOnSuspend = false
},
},
orientation =
{
default = "landscapeRight",
supported =
{
"landscapeLeft", "landscapeRight"
},
},
} From the android app when using your newest build:
11-22 14:59:42.248: I/Corona(2369): *** Corona Build #2012.971
Our latest live version is with 2012.947, and it still have that problem. When we update our corona software, do we have to uninstall the old one, or can we just install the new one over it?
We also have some problems with the sound on your newest version. It has like a 0.5-1 sec delay before it is played. Tested on Nexus S android 4.1.2 and Galaxy S android 2.3.7
We appreciate your help. [import]uid: 88922 topic_id: 26169 reply_id: 132076[/import]
Hi,
I can see that it could look that way, if this is something you already have fixed. If there is anything more we can send just name it. Hope this helps some.
build.settings
settings =
{
android =
{
versionCode = "11",
usesPermissions = {"com.android.vending.BILLING",},
},
iphone =
{
plist =
{
UIAppFonts =
{
"BradyBunchRemastered.ttf"
},
UIApplicationExitsOnSuspend = false
},
},
orientation =
{
default = "landscapeRight",
supported =
{
"landscapeLeft", "landscapeRight"
},
},
} From the android app when using your newest build:
11-22 14:59:42.248: I/Corona(2369): *** Corona Build #2012.971
Our latest live version is with 2012.947, and it still have that problem. When we update our corona software, do we have to uninstall the old one, or can we just install the new one over it?
We also have some problems with the sound on your newest version. It has like a 0.5-1 sec delay before it is played. Tested on Nexus S android 4.1.2 and Galaxy S android 2.3.7
We appreciate your help. [import]uid: 88922 topic_id: 26169 reply_id: 132076[/import]
Just released a new patch using build 2012.971. We still gets reports of the same error. [import]uid: 88922 topic_id: 26169 reply_id: 132412[/import]
Just released a new patch using build 2012.971. We still gets reports of the same error. [import]uid: 88922 topic_id: 26169 reply_id: 132413[/import]
Just released a new patch using build 2012.971. We still gets reports of the same error. [import]uid: 88922 topic_id: 26169 reply_id: 132412[/import]
Just released a new patch using build 2012.971. We still gets reports of the same error. [import]uid: 88922 topic_id: 26169 reply_id: 132413[/import]
I’ve created a own thread for this problem: http://developer.coronalabs.com/forum/2012/10/29/force-close-startup-android [import]uid: 88922 topic_id: 26169 reply_id: 133192[/import]
I’ve created a own thread for this problem: http://developer.coronalabs.com/forum/2012/10/29/force-close-startup-android [import]uid: 88922 topic_id: 26169 reply_id: 133192[/import]