Hi.

I've started beta testing my new app. One of my testers has a Samsung Galaxy SIII phone and my app instantly closed down on it.

After that I have compiled the very first tutorial and sent it to him, and it has the same problem.

We also ran the free Multiplayer Racing game from the app store and that one does work just fine. So most likely it is a recent change in the engine that causes the crash?

Regards,

yvan

---

An update:

It seems that the same tutorial compiled with 1.0 does work! Perhaps that makes things easier?

last Month I published to my SIII and it was successfully running, but it is crashing now !! it immediately shuts when I try to run it. I'm not sure if this issue related to the latest android firmware I received 4.1.2 or because some recent EE2 updates.

Hi, do you see any call stack when the crash occurs? Can you paste it here?
Something should be visible in the Android Device Log.

Hi,

I just recompiled Touch screen tutorial to my SIII, check attachments for Android device log,and Esenthel Error.txt generated on my device.

Thanks.

Hi,
I've checked "Esenthel Error", but it lists only Warnings and no Errors, Can you make sure that it's the complete file that you're attaching?
Thanks!

I see that the text file ends with:
"WARNING: 0:43: Creating Macro Object
WARNING: 0:43: Deleting Macro Object
WARNING: 0:43: Creating Macro Objec"
last line does not have 't' character, I'll do some checks in the engine, if it limits the shader output log to some number of characters.

Hi,

please find attached error logs after rebuilding "Touch Screen" Tutorial..

if you still unable to find the required data let me then know if there is any additional settings required to generate a proper error log in my phone.

Thanks

Hi,
It seems that EE buffer for holding the error information is big enough, current release should be able to handle 10*1024 characters, while your error has only around 1024 characters ("Esenthel Error.txt" from your first post after converting to ANSI), so I'm wondering if the internal android shader compiler has some limitation for returning the message in full.
Also I don't see any issues in the "Android Device Log.txt", but I know that it generates plenty of messages all the time, and it's possible that EE message will get lost quickly in it, can you try exporting "Android Device Log" as soon as the app exits, to make sure that the messages won't disappear?
Thanks.

Don't know if it will help, but I also have Samsung Galaxy SIII, and everything working fine on it.

Some time ago I had similar problem with my game (three weeks ago), but now, the issue don't occur. I think the problem's gone with some of last android update (for me, at least).

Esenthel, check attached, I made two logs, I tried to export them as quickly as possible.


Pherael , which Android update version you got? I have 4.1.2.


many thanks.

SamerK, I also have 4.1.2 version. So the issue must be somewhere else.

Thanks Pherael, thats really interesting and confusing because as I mentioned earlier EE apps used to run without issues before receiving the the 4.1.2 update !! I don't really know what has changed..

Thanks, now I see the error in the Android DevLog as well, but unfortunately it's clipped as well, it looks like the message gets clipped internally in Android.

BTW. just providing Android OS version is not enough, device makers very often release updates/patches to their devices with the same Android OS version number.

Here is my attached screenshot from "Settings/../About" page.
Galaxy Note 2 - Everything works fine, you can see the model number, kernel version, and build number. (everything works also on my Transformer Prime TF201, and HTC Evo 3D).

What are your Galaxy S3 build model versions? Could you attach screenshots as well? and also which GPU do you have? I'm not sure but I think that there are different versions of Galaxy S3 with different GPU's.

I really think the problem is that you've got some update to the phone that has bad OpenGL shader code compilation.

Hi, I attached a screenshot from phone about, also full device info details generated by "System info Droid" (nice free app) .. I hope this helps.

note, I never had any issues before running any kind of app on this phone.

Thanks,

_____
Updated screenshot

@Pherael could you attach a similar screenshot as well? I'm curious about your system version, if it's different than of SamerK's since you're getting different results.

Quote:note, I never had any issues before running any kind of app on this phone.

yes, system glsl shader compiler can fail only on certain codes

In the meantime I'll try and check
"WARNING: 0:43: Creating Macro Object
WARNING: 0:43: Deleting Macro Object
WARNING: 0:43: Creating Macro Objec"
to what macro this message relate to

@Esenthel Sure.