SGS3 problems? Anyone else?

[Azid Zeyre]

Hey, I've been trying to test out some of my Awe6 games on some colleague's S3's, and for some reason, when they try getting past the intro screen, the app bugs out and they return to their app drawer...
Anyone else having this issue?

Regards,

Azid

[Azid Zeyre]

So anyone else having problems with the S3?
Also, if anyone hasn't seen it yet, there's this place called manymo
https://www.manymo.com/
where you can upload apks and test via a cloud emulator for Android. Really neat. 

Rob, any idea what it miiight be? I'm thinking of importing to eclipse and trying to debug with adb....

[Rob Fell]

Maybe try this latest patch:

http://code.google.com/p/awe6/source/detail?r=548#

 

I found that having fully bubbling messages on init and dispose was resource intensive if there are 100s of entities.

That hit shows up most on a scene change, so it may be related?

[Azid Zeyre]

Hey, would it be possible to wrap that in a zip for me? I've not subversion set up, it'd be really neat if you could put it in a zip? Just a request, or I can go set up subversion on my dev machine!

Hope this works... On the S3's, the app gets to the intro screen, but when I try to click to go to the game, it doesn't work. This has been so for all of the little Awe6 games I've made, I don't think they're too super resource-intensive...

--
You received this message because you are subscribed to a topic in the Google Groups "awe6" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/awe6/3L4yjtqI3v8/unsubscribe?hl=en-GB.
To unsubscribe from this group and all of its topics, send an email to awe6+uns...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Rob Fell]

An easy way to grab a few files without an svn client is to follow the revision link, then view each file following the links, then right click and save-as for each file via the "View raw file" link:

 

So for revision 548 it would be these 2 urls:

 

http://awe6.googlecode.com/svn-history/r548/trunk/app/src/awe6/core/Entity.hx

http://awe6.googlecode.com/svn-history/r548/trunk/app/src/awe6/core/Process.hx

 

Then copy them over the respective files in your haxelib awe6 installation.

[Azid Zeyre]

Did so, but then when I tried to run, I got errors

C:\Motion-Twin\haxe\lib\awe6/1,3,522/awe6/core/Entity.hx:49: lines 49-348 : Field view has different property access than in awe6.interfaces.IViewable ((get_view,null) should be (_get_view,null))

C:\Motion-Twin\haxe\lib\awe6/1,3,522/awe6/core/Entity.hx:49: lines 49-348 : Field isActive has different property access than in awe6.interfaces.IPauseable ((default,set_isActive) should be (default,_set_isActive))

C:\Motion-Twin\haxe\lib\awe6/1,3,522/awe6/core/Process.hx:42: lines 42-206 : Field isActive has different property access than in awe6.interfaces.IPauseable ((default,set_isActive) should be (default,_set_isActive))

Build halted with errors (haxelib.exe).

Urk, I think I'm prettty behind with the patches, maybe a previous patch added something else... I'll see about svn now. WOld rather not go back and copy/paste everything from prior patches.

Hmmm.. I hope this issue gets fixed. S3s and related Samsung phones are pretty popular, wouldn't want an app to halt on those.

[Rob Fell]

Yes, my mistake, these latest files are totally incompatible because of the Haxe3 migration changes.

Instead, see the revision diffs, and copy and paste only those methods over the older files' corresponding methods.  Then it should be fine.

[Azid Zeyre]

Hey, so I finally managed to borrow a teammate's Galaxy S4 to test our game on. I've had scaling issues, but I'm trying to address those elsewhere in a different post.

An odd thing happens; the game apk does open, and I can see the intro screen. However, tapping the screen to go to the next screen doesn't work. In fact, if I just wait a few seconds on the intro screen, the app closes on its own. I tried the debug version, and nothing happens. It's like the scene initialises, and then freezes up before anything starts.

By this I mean that things are indeed drawn on screen, and the little debug ticker that openFL adds to the corner does show up, but it does not function, and after a few seconds, crashes.

I don't see any log output to the log in the flahsdevelop output window, even in debug mode. Heck, I even tried importing the Android project into Eclipse to make the apk manually and install, and it still didn't work, nor give me anything useful to try and figure out what the problem is.

Apparently I can run projects written in just OpenFL without awe6, so I think the problem is somewehre in Awe6 rather than with OpenFL.

:\ Any thoughts/ideas? This project runs just fine on my own Android phone, an LG Thrill. It runs as I described above on a teammates Galaxy S3 and another teammate's Galaxy S4.

On Tuesday, April 30, 2013 8:32:42 AM UTC-7, Azid Zeyre wrote:

[Azid Zeyre]

Okay, so I ran a b lank OpenFL proejct, and that ran/stayed open alright on the phone.

I ran my game coded in Awe6, and the graphics assets load but freezes up and crashes.

Then I ran the blank Awe6 OpenFL template, and the same thing happened :\

This is all on a Galaxy S4...

On my own phone, all three of these work.

Would really like to get this figured out...

Kindest Regards,

Azid Zeyre

[Rob Fell]

I am speculating (I don't have access to a G4) ... perhaps it is a similar issue to the iOS config.xml bundle issue?  Some options to try are here:

 

https://groups.google.com/d/msg/awe6/sPP9FFZUul4/OrDs1rc4000J

 

Easiest one to try first is to inline the config.xml, or replicate the HelloWorld example.

 

http://code.google.com/p/awe6/wiki/ExampleHelloWorld

 

If no success, then try stripping down to nothing (i.e. no assets, no fonts), and then add back the assets to see which one is causing the problem on this device.

[Azid Zeyre]

Great,thanks! I'll try!

--

You received this message because you are subscribed to a topic in the Google Groups "awe6" group.

To unsubscribe from this topic, visit https://groups.google.com/d/topic/awe6/3L4yjtqI3v8/unsubscribe.

[Liam Routt]

Was there a result to this?

I've just tried to export my prototype to Android and I'm finding the same thing - runs on the intro page for 8 seconds, then crashes out (or something).

Everything works fine on neko, iOS, flash, windows.

I don't own an Android device, but I've been getting a friend to try builds for me.

Any further insights here?

Take care,

Liam Routt

[Rob Fell]

No results that I know of.  Makes me question what's happening at the 8 second mark?

 

Is the Intro scene updating prior to that, or just frozen (in which case the 8 second is a non-responsiveness timeout)?

 

Or if the Intro scene is updating perhaps the 8 second mark represents a timeout to something else that has failed - e.g. a SharedObject save, an asset load, or another bad request (e.g. audio format), garbage collection or memory consumption - I am speculating.

 

If possible try slimming it down to a minimal, e.g. removing the SceneTransition, Overlay, Session save.  Thanks.

[Azid Zeyre]

Yeah, I wasn't able to find much after this issue.. :\ I ended up looking info HaxeFlixel, and that seemed to work okay, though I'm still figuring out scaling issues for mobile.

[Liam Routt]

Well, my app had no sound at all, so that should be one thing off the list.

I've created the simple HelloWorld referred to above, and I'll get that tested, then go from there (and report back).

Take care,

Liam

[Liam Routt]

OK. The simple Hello World seems to have run without any problem at all.

I'm slowly adding bits back in. I will report back at the point where a problem appears.

Take care,

Liam

[Liam Routt]

OK. I've gotten somewhere, the following version fails.

Interestingly, my tester was able to get a screenshot for the first few seconds (perhaps 4?) then it locked up, and finally crashed as before, after about 8 seconds.

The screenshot shows that the text is as I expect it on the screen, so everything has worked to this point.

Given the comments earlier about the possibility that the config file might be the problem I am reverting to loading the config from the string, and I'll test that. If that version works fine, then it would appear the config file is a problem. The other possibility is something with the AssetManager, which is exactly as in the template created for FlashDevelop, and loads the font for us.

I will confirm one way or the other, I hope.

package ;

import awe6.extras.gui.Text;

import awe6.Types;

import awe6.core.TextStyle;

import flash.Lib;

import test.my.hello.AssetManager;

import haxe.Resource;

class Main 

{       

        static function main() 

        {

                //var l_config = '<?xml version="1.0" encoding="utf-8"?><data><message>Hello World! from text</message></data>';

                //new Factory( Lib.current, false, l_config ); 

                new Factory( Lib.current, false, Resource.getString( "config" ) ); 

        }       

}

class Factory extends AFactory

{

private var _assetManager:AssetManager;

override private function _configurer( p_isPreconfig:Bool = false ):Void 

{

if ( p_isPreconfig ) 

{

id = "Hello";

version = "1.0.3";

author = "me";

isDecached = true;

width = Lib.current.stage.stageWidth;  // 768;

height = Lib.current.stage.stageHeight;  // 1024;

bgColor = 0xffFFFFFF;  // 0xFF999999;

targetFramerate = 20;

isFixedUpdates = false;

}

}

override public function createScene( p_type:EScene ):IScene 

{

var l_scene = new Scene( _kernel, p_type );

var l_fontName:String = _assetManager.font.fontName;

var l_textStyle:TextStyle = new TextStyle(l_fontName, 30);

var l_text:Text;

l_scene.addEntity( l_text = new Text( _kernel, width, height, _kernel.getConfig( "message" ) + " version " + version, l_textStyle ), true );

l_text.setPosition(40, 60);

return l_scene;

}

override public function createAssetManager():IAssetManagerProcess 

{

if ( _assetManager == null ) 

{

_assetManager = new AssetManager( _kernel );

}

return _assetManager;

}

}

Take care,

Liam

[Liam Routt]

OK, I can confirm that loading the config from the file, rather than a string, is the change which makes this simple example fail. This was mentioned earlier as a possible area of concern.

If there are further tests I can run, in order to help fix this issue with Android, I'd be happy to assist in any way possible.

I will now go back to the app I was working on and put my config into a string and see if it will run with just that adjustment.

Take care,

Liam

[Liam Routt]

This is probably not the right place for it, but in order to get my config file to parse, I had to modify core/drivers/AFactory.hx, lines 156-163 to:

if ( i.firstChild() == null )

{

config.set( l_name, "");

}

else

{

var l_nodeType = i.firstChild().nodeType;

if ( (l_nodeType != Xml.Element) && (l_nodeType != Xml.Document) )

{

config.set( l_name, i.firstChild() == null ? "" : i.firstChild().nodeValue );

//trace( l_name + " = " + config.get( l_name ) );

for ( j in i.attributes() )

{

var l_aName:String = l_name + "." + j;

config.set( l_aName, i.get( j ) );

//trace( l_aName + " = " + config.get( l_aName ) );

}

}

}

Otherwise when I removed the extra newlines from the config file to make it a string, the code was falling over after parsing the asset packages element, as it tried to find the content of the assets element itself, which in the file version at least contains a newline, but in the one-line string version does not. There is probably a more elegant rephrasing than my quick fix. I'm just eager to get a version of my app to my Android tester to see whether it now works.

Take care,

Liam

[Azid Zeyre]

Odd... GOod to hear your code's working for now! :D Let's hope this gets fixed!

[Rob Fell]

Thanks for this.

 

As you mention this fix is issue specific because if patched back in the library it would cause other issues (because attributes for null value elements won't parse).

So I've not many any updates to SVN yet.

 

I've reviewed the surrounding code to see how a newline may cause issues, and haven't spotted anything yet.  Baffled!?

[Azid Zeyre]

Many baffles!

[Liam Routt]

What of the base issue of the problem of the config file under Android? Is there an easy solution to that?

I guess ideally one would want to solve them both, so that an inline string would be parseable and a string able to be used as well.

Just to confirm, my full app works fine on Android when I load the config from a string; this was the only showstopper as far as I can tell.

I'm looking at expressing my config as a multiline string for the time-being.

Take care,

Liam

[Liam Routt]

Wow, I haven't been well, but the code I suggested was simply not right, basically leaving out all of the attributes in the config file. How did I manage that?

Here's the corrected version:

if ( i.firstChild() == null )

{

config.set( l_name, "");

}

else

{

var l_nodeType = i.firstChild().nodeType;

if ( (l_nodeType != Xml.Element) && (l_nodeType != Xml.Document) )

{

config.set( l_name, i.firstChild() == null ? "" : i.firstChild().nodeValue );

}

else

{

config.set( l_name, "");

}

}

//trace( l_name + " = " + config.get( l_name ) );

for ( j in i.attributes() )

{

var l_aName:String = l_name + "." + j;

config.set( l_aName, i.get( j ) );

//trace( l_aName + " = " + config.get( l_aName ) );

}

Apologies for the mistake!

Take care,

Liam

[Rob Fell]

Thanks Liam, patch added to svn revision 612:

http://code.google.com/p/awe6/source/detail?r=612