Has anyone filed a bug report yet? Or corona is already on this bug?
Hi guys,
We’re going to begin testing our in-house devices with this issue starting today, and determine if there’s a pattern of behavior. I’ll keep you posted on what I learn this week.
Regards,
Brent
Hi Brent, did you find anything?
Hi all,
I checked into this again, and the engineers are still aware of the issue (we’re not dismissing it). However, it remains somewhat isolated and quite difficult to pin down, since it seems to occur on a limited number of devices, only in landscape mode. What would help at this time is if you can contribute a list of devices that it does not work on… that is, you have personally tested it with a recent build of Corona (or you know somebody who has, and can vouch for it). Then we can compare with our in-house devices and see if there’s any pattern.
So, a list of these things would be helpful:
-
Test with the Corona-built sample app: CoronaSDK > SampleCode > Hardware > SystemEvents
-
Then include a report with:
a. Device/Model, and also “variety” if there are a few similar in the model line
b. Android OS version
c. Corona build used
I know some of you have tested various devices already, and thank you for that… but for the sake of consistency, following the above guidelines would be helpful.
Thanks,
Brent
@Brent install the sample app in any of these devices.It’s so easy to check this but you make it sound so hard!Am i missing something?File a report or never happened logic?
I really don’t care anymore , just asking.
“”“Premium Galaxy (WVGA) - [Galaxy Ace 2 , Galaxy Ace 3 , Galaxy Beam (8520) , Galaxy Beam (8530) , Galaxy Core , Galaxy Express , Galaxy Grand , Galaxy M style , Galaxy R , Galaxy Reverb , Galaxy Rugby LTE , Galaxy S , Galaxy S Advance , Galaxy S DUOS , Galaxy S II , Galaxy S II LTE , Galaxy S II Plus , Galaxy S III Mini , Galaxy S Super Clear LCD , Galaxy Victory , Galaxy W , Galaxy Win , Galaxy Xcover 2 , Galaxy 大噐Ⅱ_CN , Giorgio Armani Galaxy S , Samsung W899 , 心系天下_CN]”""
You’ve confirmed that the issue exists on all of these devices? Our research seems to indicate the issue only occurs on a few devices. This is what I’m trying to figure out. There are hundreds (perhaps thousands) of Android devices out there, and we haven’t been able to reproduce the issue consistently on our in-house test devices (clearly we do not have all of devices you list).
Brent
There are at least 2638 android devices.I don’t have all these devices but I have checked some like galaxy s1,2,3 mini and the problem is there.I have checked some other too and the sound issue is not there.So I guess this list is correct.This is a minor bug but on the other hand Samsung rejects every corona app.There is one perfect solution.Wait until Samsung stops checking on these devices.Just joking 
Everyone,
After some extensive testing via 4 people on our end and on several devices, we finally found 1 device that was able to reproduce this issue. It was a “Nook Color”. We finally have something to work with.
We were *not* able to reproduce this issue on the following devices:
- Nexus One running Android 2.3.6
- Nexus 3 running Android 4.0.2
- Nexus 4 running Android 4.2.2
- Nexus 7 running Android 4.2.2
- Nexus 10 running Android 4.2.2
- Galaxy Nexus running Android 4.0.3
- Galaxy SII running Android 2.3.4
- Galaxy SIII running Android 4.1.2
- Galaxy S4 running Android 4.2.2
- Galaxy Tab (Did not get the rest of the info from the volunteer.)
- HTC One running Android 4.1.2
- EVO 4G running Android 2.2
- Nook Tablet running Android 2.3
- Nook HD running Android 4.0
- Kindle Fire (1st Generation) running Android 2.3
- Kindle Fire HD 7" running Android 4.0
- Kindle Fire HD 8.9" running Android 4.0
So, the above list should give you some confidence on how rare this issue really is. Although the fact that it happens on the Samsung app reviewers’ devices ups the priority. This is the first I’ve heard that come up.
Josh, Brent,
My app was rejected for the same issue.
In order to reproduce it you need to have a high-end *Samsung* device. Older Samsung devices do not have the problem.
The key thing here is that it’s not just a “pair of devices” that exhibit this behaviour, it’s (presumably) *all* of Samsung’s latest devices. As a consequence Samsung rejects our app submissions, so an entire (Corona-supported) marketplace is unavailable to us.
Using build 971 is not an option.
Please update this topic with your latest advice.
Thanks,
Per
@perflubron what do you mean high-end? If galaxy s3 is high-end then I have to say that I don’t have any problems.
The failure report from Samsung does not list exact devices. But they are referred to in the report as “high-end” or “premium”. These three failed:
Galaxy Camera Wi-Fi (HD)
High-end Galaxy Wi-Fi (HVGA)
Premium Galaxy Wi-Fi (WVGA)
Note: This does not mean that *only* those devices would fail, Samsung appear to terminate the certification process after a certain number of errors.
I’ve asked a friend to test a Galaxy S4.
S4 works as intended.
So I take back my statement that it probably affects *all* high-end devices.
My error report from Samsung included a video of a device that looked like a camera, Galaxy Camera Wi-Fi. I’m speculating that perhaps it affects certaian Samsung devices whose default orientation is landscape rather than portrait (c.f. Josh’s comment 08 May 2013 - 08:24 PM). But then again Odijack had the same problem with some other devices, which sounded like phones (10 May 2013 - 08:18 AM).
Brent made a comment earlier (10 May 2013 - 05:40 PM) that “The only thing I know that changed very slightly between the two public builds (related to your issue, I mean) was a minor adjustment of how the system events are handled”. When was that change made?
@perflubron Build 971 is not an option for you but I think it’s the last working build… I’m really interested too.Lets see what coronalabs has to say.
Has anyone filed a bug report yet? Or corona is already on this bug?
Hi guys,
We’re going to begin testing our in-house devices with this issue starting today, and determine if there’s a pattern of behavior. I’ll keep you posted on what I learn this week.
Regards,
Brent
Hi folks, any progress on resolving this?
Not yet. We have other commitments that must be met first. But this issue is on our to-do list.
Hi Brent, did you find anything?
Hi all,
I checked into this again, and the engineers are still aware of the issue (we’re not dismissing it). However, it remains somewhat isolated and quite difficult to pin down, since it seems to occur on a limited number of devices, only in landscape mode. What would help at this time is if you can contribute a list of devices that it does not work on… that is, you have personally tested it with a recent build of Corona (or you know somebody who has, and can vouch for it). Then we can compare with our in-house devices and see if there’s any pattern.
So, a list of these things would be helpful:
-
Test with the Corona-built sample app: CoronaSDK > SampleCode > Hardware > SystemEvents
-
Then include a report with:
a. Device/Model, and also “variety” if there are a few similar in the model line
b. Android OS version
c. Corona build used
I know some of you have tested various devices already, and thank you for that… but for the sake of consistency, following the above guidelines would be helpful.
Thanks,
Brent
@Brent install the sample app in any of these devices.It’s so easy to check this but you make it sound so hard!Am i missing something?File a report or never happened logic?
I really don’t care anymore , just asking.
“”“Premium Galaxy (WVGA) - [Galaxy Ace 2 , Galaxy Ace 3 , Galaxy Beam (8520) , Galaxy Beam (8530) , Galaxy Core , Galaxy Express , Galaxy Grand , Galaxy M style , Galaxy R , Galaxy Reverb , Galaxy Rugby LTE , Galaxy S , Galaxy S Advance , Galaxy S DUOS , Galaxy S II , Galaxy S II LTE , Galaxy S II Plus , Galaxy S III Mini , Galaxy S Super Clear LCD , Galaxy Victory , Galaxy W , Galaxy Win , Galaxy Xcover 2 , Galaxy 大噐Ⅱ_CN , Giorgio Armani Galaxy S , Samsung W899 , 心系天下_CN]”""