Samsung Galaxy S II

[Wampus]

Things go from bad to worse. Now my apps are not working on the Asus Transformer ;( I have absolutely no idea whats wrong ;(

All your apps? The free version of Glowing Sky I tried was working fine on the S II.

Is there something I can do for you with debugging on my S II? I could sign and fax you a non-disclosure agreement or whatever, then you could send me the code and I could try and track down what was causing the problem.

[Minion]

Its a strange one for sure. Ive had Andy from Ovine looking over my code and trying all sorts with it, ripping it apart to its bare bones etc and every time it fails to work at different points within the code (1 pass will get to the splash screen, so we add code to show which part of the splash screen routine its in, and then run again and it flies past that and fails in another part of the code - no matter where we put the trap routines, it either gets past them with no problems, or doesnt even get that far in the code). The really annoying thing is that I have a build thats *almost* finished and that works fine.

[Wampus]

That is weird. Any idea what the general error is? An infinite loop? Illegal access? etc.

[Minion]

Nope, nothing. We tried removing all the polyvector routines and just using the bog standard sprite routines, but that didnt work.  We tried removing huge chuncks of code (splash screens, intros, high score tables etc) too see if that would make a difference, but still nothing ;( I have a version of my game that does actually write to a file after every line of code (using CODELINE and CODEFILE), sadly Andy was unable to get to the package to extract the file once it had run, but it would have shown the exact line it was failing on and maybe shed some light as to what was going on.

[Moebius]

[Apologies in advance for the bump....]
Testing on a GS2 my game also hangs - seemingly randomly but at specific commands (specific ENDPOLYs and STRECHSPRITEs).  It only crashes whilst drawing to a virtual screen, and I haven't been able to find a logical explanation why.....
After a seemingly random number of loops, the first 'render' command after the USESCREEN seems to cause the program to hang.  The app doesn't crash, and when the back button is pressed the app exits and logs normally, but before then it seems stuck executing the command...
If it feels like it, the app sometimes waits until a later STRETCHSPRITE call before it crashes - always crashing at one of these two places...
I can't seem to replicate it in a simpler example, even with a massive loop of POLYVECTORs and STRETCHSPRITEs.     Any ideas as to why?   Could there be a hardware issue?  Is it possible for the drawing commands to get stuck like this?

[Kitty Hello]

Can you get a stack trace?

[Moebius]

Still working on that (i.e. googling to fill in my lack of knowledge) but I do notice that one of these messages shows up in the log every few seconds after the app hangs:

Code (glbasic) Select Expand

01-14 13:12:52.345 21165 21165 D dalvikvm: GC_EXPLICIT freed 70K, 53% free 2538K/5379K, external 0K/0K, paused 90ms
01-14 13:12:57.365  5431  5431 D dalvikvm: GC_EXPLICIT freed 42K, 53% free 2912K/6087K, external 0K/0K, paused 102ms
01-14 13:13:05.130  2965  2965 D dalvikvm: GC_EXPLICIT freed 55K, 47% free 3745K/7047K, external 0K/0K, paused 58ms
seems to go on indefinitely, a new logged message like this every few seconds, and not one of these shows up while the program is running normally.....

[Moebius]

It seemed that I'd have to root my phone in order to kill the app in order to get a stack trace....  long story short I ended up installing MIUI (android v2.3.7) and it doesn't crash anymore   

[Kitty Hello]

I ended up installing MIUI (android v2.3.7) and it doesn't crash anymore   

So, it's a software bug? What a shit.