imaffett

but let's make it clear: Crosswalk team can't fix Chromium bugs. Yes?

They have access to the source, commit bug fixes, and features to Chromium. So overall, yes of course they can fix bugs.

I wanted to thank everyone for their feedback. I can tell you the Crosswalk team is very aware of the issues with performance. They are actively looking into it now. This is not an "easy" fix as you can guess, but I hope you have patience as the issues are being worked out. The goal is to make Crosswalk work amazing on Android for gaming!

Samsung Galaxy Tab 3 SM-T110 - Android 4.4.2

• cw07 | 25-36 fps | canvas 2d | laggy but playable
• cw10 | 28-38 fps | canvas 2d | laggy but playable
• cw11 | 19-36 fps | canvas 2d | too laggy
• cw12 | 15-25 fps | canvas 2d | too laggy

GIGABYTE GSmart Guru G1 - Android 4.2.1

• cw07 | 33-36 fps | canvas 2d | fps looks ok, but barely playable
• cw10 | 29-30 fps | canvas 2d | steady but low fps, barely playable
• cw11 | 29-30 fps | canvas 2d | steady but low fps, barely playable
• cw12 | 20-22 fps | canvas 2d | unplayable

Samsung i9300 Galaxy S III - Android 4.3

• cw07 | 49-57 fps | canvas 2d | only little lags, good
• cw10 | 59-60 fps | webGL | smooth, very good
• cw11 | 59-60 fps | webGL | smooth, very good
• cw12 | 59-60 fps | webGL | smooth, very good

From my tests it looks like lower cw versions behave better in canvas 2d mode. GSmart G1 is the most powerful from all 3 devices, but I think it's blacklisted by Google and forced to use canvas 2d and there cw7 somehow performs little bit better than newer versions (not much tbh, but it was noticable).

On Samsung i9300, that's where webGL kicks in and the new cw versions shine.

My result is:

Low end or blacklisted device with canvas 2d = cw7 >= cw10 > cw11 & cw12

Device which uses webGL = use newest crosswalk version

Any chance I can get a link to your app or APK?

imaffett

Hello, for me CW7 is still better than 11,12.

Another words, the higher version cw = the less fps <img src="{SMILIES_PATH}/icon_e_surprised.gif" alt=":o" title="Surprised"> <img src="{SMILIES_PATH}/icon_e_smile.gif" alt=":)" title="Smile">

game url: http://happysubmarine.indieboygames.com

apk cw7: http://goo.gl/jEIKlw

cw12 = 20 fps

cw11 = 34 fps

cw7 = 41fps

Which device/OS are you testing on?

Ashely - I have rebuilt the APK's that should ignore GPU blacklisting - https://crosswalk-project.org/documenta ... t/faq.html

You can find all the APK's in dropbox below (CW10-12)

https://www.dropbox.com/sh/as7923g3zaib ... OANVa?dl=0

Iolva

The problem now isn't to loose the Webstorage data, but loosing the ability to play in the first place!

The performance is very poor, forget about the powerful devices that can run anything, at lease 50% of players will give the game one star on Google Play because of the poor performances that makes the game unplayable.

Even with crosswalk 7 i get about 10 reviews everyday mentioned the "poor performance"!, imagine what can happen if i use crosswalk 10 or 11 or 12 !!! players will kill me.

Somebody give me a fixed Crosswalk 7 without OpenSSL issue, PLEASE.

I don't need anything else in my sad life on this planet.

I do not believe the CW team will upgrade CW7 at all. Your best bet is going to be grabbing the source, patching it and building from the command line.

Hi

I would like to point out three things:

1. Is the WebStorage going to work if we update our APKs from CW10 to CW12?

The upgrade from CW7 to CW10 erased all the WebStorage

2. I have tested my app with the "CW11Shell" and "CW12Shell" and I have to say the performance is way better than CW10 (CW11 is fast, but CW12 is even a little bit faster)!

The game feels totally different, I'm hoping to see CW12 as stable version

3. Is somewhere a changelog of these CW11 and CW12?

I'm sure the improvements we are seeing here does not come from magic!

I would like to read the changelogs

Thanks for all the effort!

Hi —

#1 this was fixed. CW10 upgrade should NOT remove local storage. If this is still happening in our build system, let me know.

#2 - thanks. I'll try to make a push if this is the case

#3 - You can find all information about Crosswalk at http://crosswalk-project.org

Ok - the CW7 shell app can be found at https://www.dropbox.com/s/xt5h50lghjs79 ... d.apk?dl=0

The CW10 shell app can be found at https://www.dropbox.com/s/vvr5whoupdwr9 ... d.apk?dl=0

Thanks for the responses everyone! I will get a CW7 shell and a CW 10 shell up in the next two hours.

I have created two debuggable APK's for users to test their apps on. One for Crosswalk 11 and one for Crosswalk 12. Please note, Cordova Plugins are not available, this is simply to test performance of your app. Both the apps allow you to enter a URL to redirect to. To test your apps, you must be running your C2 exported code on a webserver. You can host it anywhere, but your Android device must be able to access it for this to work.

You can use Chrome to test FPS. There is an ADB plugin for Chrome at https://chrome.google.com/webstore/deta ... e?hl=en-US . You must have drivers installed for your device. Once it is configured, you can inspect the target, then go to "Rendering" -> "Show FPS Meter" to get accurate FPS measuring.

https://www.dropbox.com/s/28q3chyl3sv5m ... d.apk?dl=0 - CW11 shell

https://www.dropbox.com/s/yyqhqo504gp6o ... d.apk?dl=0 - CW12 shell

If you have questions about web servers, firewalls, etc, search google <img src="{SMILIES_PATH}/icon_e_wink.gif" alt=";)" title="Wink">

Hi TiAm,

Thanks for the kind words! Building from the command line is a little tricky right now, but what is your time frame for release?. I'm pushing to get CW11 and 12 available soon (since 11 is stable and 12 is beta).

GPU Rasterization *is* supported on 10, and I can tell this via CSS demo's. But I'm not sure why Chrome wasn't reporting it. I updated the Crosswalk bug this morning with the APK's and findings. I hope to hear something from them soon.

thanks,

Ian

Eisenhans - Absolutely! I only used that one since Ashley gave it to us. It does the FPS client side, but I was using Chrome Developer Tools and saw a big difference between CW11 and CW12. An odd note is GPU Rasterization did not appear to be on in CW11, but I did see it was enabled in CW12.

If someone provides a capx of a better project, I will get it tested right away.