Crosswalk Intel XDK experiences

Discussion and feedback on Construct 2

Post » Thu Jun 05, 2014 1:54 am

Hi, I read through all your posts, here I'd like to give some clarifications and background about gpu blacklist issue.

* Why not ignore gpu blacklist in Crosswalk now?

The gpu blacklist was originally ignored by default in Crosswalk. However, about several months, some C2 users reported WebGL running with Crosswalk gets crash on their device due to the buggy gfx driver. Such a crash seems not so good, and Crosswalk is not ignore the blacklist, instead it lets web developer decide if it is on or off via command line options.

EDIT: Chromium introduces the mechanism of gpu blacklist for those devices which don't have a good enough passrate in WebGL conformance test. This mean those devices may trigger some bug or limited feature support in the gfx driver in some condition although most of time they work well.

* How to append the command line option to ignore gpu blacklist?

I am sorry to confuse you with a different context. The approach I mentioned above is in the context of using make_apk.py directly instead of Intel XDK build. With XDK build, there is no way for web developer to add an individual file in assets folder. XDK is working on adding such an option to ignore gpu blacklist for web developer.

* What is the relationship between XDK build and open source Crosswalk?

Crosswalk is a HTML5 app runtime to run web app. It supports the HTML5 standard API and features without phonegap APIs and plugins support. XDK build uses a Crosswalk variant as the backend engine. This Crosswalk variant integrates phonegap APIs and plugins based on the open source Crosswalk project. For simplicity, we call both of them as Crosswalk.

So if you web app depends on phonegap API or plugin, you can't build a workable web app by use of make_apk.py. The make_apk.py is only useful for 'pure' HTML5 app.

[BTW: since I have no enough reputations to paste URL and pm some of you. Sorry for no reply if you PMed me:)]
Last edited by hmin on Fri Jun 06, 2014 1:31 am, edited 5 times in total.
B
4
S
1
Posts: 35
Reputation: 416

Post » Thu Jun 05, 2014 2:03 am

ALI3D69 wrote:@kbm
its really funny! i have all your problem.
I don't know how to what hmins says
and i have Galaxy S2. i cant run webgl with crosswalk. and i have problem with cjs.

when i export with cjs, my game dose not work in my phone. but in note 10.1 2012 edition it works fine. is it because its ram?
and why crosswalk get lower ram? is it slower than cjs?
if i enable webgl, is it possible that my game dosent run in my phone because of more ram needing?
and is it harm for phone? why they make this blacklist?


The crosswalk and cjs (canvas+) have different implementations for webgl support. I don't think the failure running your game app on Note 10.1 was caused by memory consumption, maybe a buggy gfx driver to support some feature required by webgl. You can capture some logs by adb logcat to see if there is some suspicious error message.
B
4
S
1
Posts: 35
Reputation: 416

Post » Thu Jun 05, 2014 7:59 am

hmin wrote:Hi, I read through all your posts, here I'd like to give some clarifications and background about gpu blacklist issue.

* Why not ignore gpu blacklist in Crosswalk now?

The gpu blacklist was originally ignored by default in Crosswalk. However, about several months, some C2 users reported WebGL running with Crosswalk gets crash on their device due to the buggy gfx driver. Such a crash seems not so good, and Crosswalk is not ignore the blacklist, instead it lets web developer decide if it is on or off via command line options.

* How to append the command line option to ignore gpu blacklist?

I am sorry to confuse you with a different context. The approach I mentioned above is in the context of using make_apk.py directly instead of Intel XDK build. With XDK build, there is no way for web developer to add an individual file in assets folder. XDK is working on adding such an option to ignore gpu blacklist for web developer.

* What is the relationship between XDK build and open source Crosswalk?

Crosswalk is a HTML5 app runtime to run web app. It supports the HTML5 standard API and features without phonegap APIs and plugins support. XDK build uses a Crosswalk variant as the backend engine. This Crosswalk variant integrates phonegap APIs and plugins based on the open source Crosswalk project. For simplicity, we call both of them as Crosswalk.

So if you web app depends on phonegap API or plugin, you can't build a workable web app by use of make_apk.py. The make_apk.py is only useful for 'pure' HTML5 app.

[BTW: since I have no enough reputations to paste URL and pm some of you. Sorry for no reply if you PMed me:)]


Thanks a lot for your quick response! :) Really awesome to speak directly to a Crosswalk-Dev.

Anyways, does that mean that I basically can't use Crosswalk without Intel XDK because it doesn't fully support Construct 2 [with plugins and all]?

On another note, you say that the next XDK release might give us an option to turn off the blacklist, but you also said that doing so may lead to crashes or even brick the phone. Maybe I'm naive but wouldn't a better solution be to manually remove specific phones from the blacklist, such as the mentioned Galaxy S3 and S4? Turning off the whole blacklist seems very brute-force.
B
5
S
2
Posts: 29
Reputation: 483

Post » Fri Jun 06, 2014 1:27 am

kbm wrote:Anyways, does that mean that I basically can't use Crosswalk without Intel XDK because it doesn't fully support Construct 2 [with plugins and all]?


No. Intel XDK can help build your app for PhoneGap API support, and you can also use Crosswalk directly by use of make_apk.py packaging tools if PhoneGap API is NOT used. Generally, Crosswalk also fully support Contruct2 library and its plugins (both of them are pure JS libraries).

kbm wrote:On another note, you say that the next XDK release might give us an option to turn off the blacklist, but you also said that doing so may lead to crashes or even brick the phone. Maybe I'm naive but wouldn't a better solution be to manually remove specific phones from the blacklist, such as the mentioned Galaxy S3 and S4? Turning off the whole blacklist seems very brute-force.


Don't over-worry about that. The potential crashes caused by a buggy gfx driver is somewhat a kind of software level error. You should test your app carefully on a backlisted device to make sure it won't trigger such an error.

See my above update:
EDIT: Chromium introduces the mechanism of gpu blacklist for those devices which don't have a good enough passrate in WebGL conformance test. This mean those devices may trigger some bug or limited feature support in the gfx driver in some condition although most of time they work well.
B
4
S
1
Posts: 35
Reputation: 416

Post » Fri Jun 06, 2014 11:14 am

Thanks for clearing that up for me, @hmin ! :) Unfortunately I get the "AttributeError: 'module' object has no attribute 'maxint' " error and make_apk.py doesnt work. I have no idea what the problem is, my setup/paths seem to be alright and I followed the instructions in the documentation step by step.

Anyways, thanks again and I'm looking forward to future updates!
B
5
S
2
Posts: 29
Reputation: 483

Post » Sat Jun 07, 2014 3:57 pm

@hmin

I can not re produce the issue, but when I do I will screenshot it! Thank you.


Another question, is when could we see push notifications by using Crosswalk? That show up on the users toolbar
B
18
S
6
Posts: 348
Reputation: 2,633

Post » Mon Jun 09, 2014 1:52 am

GameThirsty wrote:@hmin
Another question, is when could we see push notifications by using Crosswalk? That show up on the users toolbar


Do you have a try to a 3rd party phonegap plugin for push notification? see github.com/phonegap-build/PushPlugin
B
4
S
1
Posts: 35
Reputation: 416

Post » Mon Jun 09, 2014 1:56 am

kbm wrote:Thanks for clearing that up for me, @hmin ! :) Unfortunately I get the "AttributeError: 'module' object has no attribute 'maxint' " error and make_apk.py doesnt work. I have no idea what the problem is, my setup/paths seem to be alright and I followed the instructions in the documentation step by step.

Anyways, thanks again and I'm looking forward to future updates!


Could you please paste the whole error message to here, including the callstack printed by python? Thanks.
B
4
S
1
Posts: 35
Reputation: 416

Post » Mon Jun 09, 2014 9:51 am

Exit problem is again here in latest XDK :(
B
25
S
4
G
2
Posts: 318
Reputation: 2,501

Post » Mon Jun 09, 2014 1:09 pm

Hello hmin,

I am using the latest XDK compiler BETA Crosswalk 6.35.131.6 on Cordova 3.4.0 and the latest Construct 2. When running the APK on an Alcatel Fierce One phone I get a crash. The crash happens when the game tries to play any sound effect. Streaming music works fine on this phone but as soon as any sound effect plays the game crashes and exits immediately. If I do not play sound effects the games runs fine. The exact same build runs perfectly fine on a Samsung Galaxy 4 and plays sound effects fine.

I do not have an extensive Android handset collection on hand but this crash worries me as to how many other phones this will be a problem with. Do you guys run unit tests on many handsets with XDK/Crosswalk?
B
5
S
1
Posts: 24
Reputation: 423

PreviousNext

Return to Construct 2 General

Who is online

Users browsing this forum: No registered users and 2 guests