Hi @Brent Yes,there are no problems in build 971.I have no problem using it except the message that appears the first time you run the game on the device.I thought it was in splash screen category.Can I remove it somehow? Well, this minor adjustment created all the problems.If you test on galaxy s i9000 or mini 2 you will see how bad it is!
Hmm… what message appears? Can you describe it, or even show a screenshot?
Sorry for the delay
Corona SDK Trial
This message only appears in the trial version
Ok - Learn More (buttons)
If i can remove this message then i have no problem using the previous build 
Hi @Odijack,
This message actually appears ON the device, when you build and deploy? As in, it appears to your end users who will download the game from Google Play? If so, I’ll investigate…
I build for iphone or android ,then install it in my devices and appears on the device like popup only the first time you start the game.
Im pretty sure it will appear to my end users too.
If we can remove it everything will be fine!!I will use 971 for android and latest build for iphone!
Hi @Odijack,
OK, I checked into this, and with 971 the pop-up will appear for non-subscribers. It should not appear for non-subscribers using 1076.
So basically, it appears that you have 3 choices, if you wish to remain a Starter user:
-
Release with 1076 and “accept” that the issue will occur on a few Android devices like the “mini 2” if, and only if, the user force-exits the app with the power button (not the “home” button). In the plus column, assume the game will run just fine on most Android devices and all iOS devices.
-
Use the “media” library. When I said that your sound setup is “simple”, I meant (from your earlier post) that you’re merely playing basic audio tracks and sound effects. Most likely you don’t need to “seek”, “rewind”, or use other OpenAL features. I might be mistaken about what you’re doing with the audio, but the media library does handle essential audio needs just fine: playing, stopping, pausing, adjusting volume, etc.
-
Wait for the next public release in which this issue might be fixed (Android is often a moving target in this regard because of the countless devices, models, core processors, and OS versions in the market).
It’s not only the sound problem.Power button makes the game unplayable because mess with timers too.There are more problems because of suspend changes.You shouldnt act like i imagine the problems.Someday i will make a post.So no2 is not a solution.No1 is not a solution either.I have no idea how many devices have the same problem.As for no3 no comments. Our only real solution is to pay for pro and use 971 build. We regret using corona but we must find a solution and release the game. Brent and Joshua ty for your time.
@Odijack,
I don’t act like you’re imagining the problem, but I think you overestimate the number of devices that it potentially occurs on. If this was a widespread issue on Android, we would have received several reports from several users and fixed it in 1076… but that did not happen. So, I maintain this is an isolated case.
That being said, I don’t treat it as “unimportant” just because it’s isolated. We want to support as many Android devices as possible, but there are thousands of them. If you submit a proper bug report, we can investigate this further and try to fix it in a daily build upcoming, but since you’re a Starter user, you would not be able to use that build. Suggestion #3 should warrant some consideration for you, however, as the next public build is not that far away. If you submit a proper bug report, then we can investigate this sooner than later and hopefully get it fixed… but if you must release the game next week, then this isn’t an option.
I dont want to make another topic , so i will post here.
I thought a few solutions but didn’t work except one!
I abandoned landscape and used only portrait in build.settings.Then i rotated the display groups 90 degrees and repositioned a few images-buttons.This way i use portrait but player must hold horizontal the device like landscape
Everything works great now!
I wonder if there is any problem with this method…
Hi @Odijack,
I’m glad that you got this working, even though it’s a “workaround” solution. Would you be willing to compile an official bug report using your previous test case, so we can investigate and fix this issue in the next public build? I’d like to see it fixed, and a test case is the best way to prioritize that it happens.
In any case, your method should be fine except if you use any “native” objects like the soft keyboard, native text input fields/boxes, or banner ads. These things are dependent on the orientation of the device, so if you use them, they’ll probably be rotated 90 degrees.
Anyway, let me know about the bug report, and I’ll instruct you on what’s required to submit it (and where to send it).
Thanks,
Brent
Hi, I have encountered the same problem. Detected by samsung app store reviewers.
I have tested on my low end android Sony Ericsson phone but cannot reproduce the same problem.
Device that has this problem is Galaxy S Wifi 3.6
you can view the videos and the bug report here
report: https://docs.google.com/document/d/1MN7zISNrw5pkKPuJyzuOXhEPwYcD57FG13WUbmoTpDU/edit?usp=sharing
video link: https://docs.google.com/file/d/0B3yx-Bx5swYkVlYxUFRfdGRoNkk/edit?usp=sharing
My solution for now is to remove all HVGA phones (low end 320x480 phones) from supported devices list.
for the build setting I am using landscape too
default = “landscapeRight”,
supported =
{
“landscapeLeft”, “landscapeRight”
}
I am using corona build version 1041
Well , im not the only one developing in landscape and using audio at the same time.We are 2!!! Maybe trying the latest public build??
Hi, I have encountered the same problem. Detected by samsung app store reviewers.
I have tested on my low end android Sony Ericsson phone but cannot reproduce the same problem.
Device that has this problem is Galaxy S Wifi 3.6
you can view the videos and the bug report here
report: https://docs.google.com/document/d/1MN7zISNrw5pkKPuJyzuOXhEPwYcD57FG13WUbmoTpDU/edit?usp=sharing
video link: https://docs.google.com/file/d/0B3yx-Bx5swYkVlYxUFRfdGRoNkk/edit?usp=sharing
My solution for now is to remove all HVGA phones (low end 320x480 phones) from supported devices list.
for the build setting I am using landscape too
default = “landscapeRight”,
supported =
{
“landscapeLeft”, “landscapeRight”
}
I am using corona build version 1041
Well , im not the only one developing in landscape and using audio at the same time.We are 2!!! Maybe trying the latest public build??
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.