About Store Forum Documentation Contact
Donations:
345$/mo



Post Reply 
Crash on Samsung Galaxy SIII
Author Message
yvanvds Offline
Silver Supporter

Post: #1
Crash on Samsung Galaxy SIII
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?
(This post was last modified: 07-28-2013 06:33 PM by yvanvds.)
07-28-2013 06:02 PM
Find all posts by this user Quote this message in a reply
SamerK Offline
Member

Post: #2
RE: Crash on Samsung Galaxy SIII
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.
07-29-2013 01:59 PM
Find all posts by this user Quote this message in a reply
aceio76 Offline
Silver Supporter

Post: #3
RE: Crash on Samsung Galaxy SIII
That sounds exactly like what was happening. Your issue might be the same.
07-29-2013 03:58 PM
Visit this user's website Find all posts by this user Quote this message in a reply
Esenthel Offline
Administrator

Post: #4
RE: Crash on Samsung Galaxy SIII
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.
08-06-2013 10:10 AM
Find all posts by this user Quote this message in a reply
SamerK Offline
Member

Post: #5
RE: Crash on Samsung Galaxy SIII
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.


Attached File(s)
.txt  Android Device Log.txt (Size: 63.12 KB / Downloads: 11)
.txt  Esenthel Error.txt (Size: 2.23 KB / Downloads: 19)
08-06-2013 02:18 PM
Find all posts by this user Quote this message in a reply
Esenthel Offline
Administrator

Post: #6
RE: Crash on Samsung Galaxy SIII
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.
08-20-2013 04:19 AM
Find all posts by this user Quote this message in a reply
SamerK Offline
Member

Post: #7
RE: Crash on Samsung Galaxy SIII
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


Attached File(s)
.txt  Android Device Log.txt (Size: 61.16 KB / Downloads: 3)
.txt  Esenthel Error.txt (Size: 11.13 KB / Downloads: 10)
08-20-2013 03:46 PM
Find all posts by this user Quote this message in a reply
Esenthel Offline
Administrator

Post: #8
RE: Crash on Samsung Galaxy SIII
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.
08-23-2013 06:19 AM
Find all posts by this user Quote this message in a reply
Pherael Offline
Silver Supporter

Post: #9
RE: Crash on Samsung Galaxy SIII
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).
(This post was last modified: 08-23-2013 12:25 PM by Pherael.)
08-23-2013 12:23 PM
Find all posts by this user Quote this message in a reply
SamerK Offline
Member

Post: #10
RE: Crash on Samsung Galaxy SIII
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.


Attached File(s)
.txt  1st Android Device Log.txt (Size: 76.17 KB / Downloads: 2)
.txt  2nd Android Device Log.txt (Size: 63.66 KB / Downloads: 3)
.txt  Esenthel Error.txt (Size: 6.68 KB / Downloads: 3)
(This post was last modified: 08-23-2013 09:13 PM by SamerK.)
08-23-2013 09:12 PM
Find all posts by this user Quote this message in a reply
Pherael Offline
Silver Supporter

Post: #11
RE: Crash on Samsung Galaxy SIII
SamerK, I also have 4.1.2 version. So the issue must be somewhere else.
08-24-2013 09:24 AM
Find all posts by this user Quote this message in a reply
SamerK Offline
Member

Post: #12
RE: Crash on Samsung Galaxy SIII
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..
08-24-2013 01:32 PM
Find all posts by this user Quote this message in a reply
Esenthel Offline
Administrator

Post: #13
RE: Crash on Samsung Galaxy SIII
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.


Attached File(s) Image(s)
   
08-26-2013 10:49 AM
Find all posts by this user Quote this message in a reply
SamerK Offline
Member

Post: #14
RE: Crash on Samsung Galaxy SIII
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


Attached File(s) Image(s)
   

.doc  SIII device info copy.doc (Size: 29 KB / Downloads: 6)
(This post was last modified: 08-26-2013 03:26 PM by SamerK.)
08-26-2013 02:08 PM
Find all posts by this user Quote this message in a reply
Esenthel Offline
Administrator

Post: #15
RE: Crash on Samsung Galaxy SIII
@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 smile

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
08-28-2013 09:53 AM
Find all posts by this user Quote this message in a reply
Post Reply