@Silverforce, @Mayfly, I still failed to reproduce it with some experiments.

@Silverforce, I agree with your analysis for the blurry image caused by scaling. If I could reproduce it, I think I can fix in XDK/Crosswalk, at least to provide a option for developer to decide if auto-scaling is needed.

Would you please paste a piece of code to show how do you use the image in HTML file? for example, if viewport meta tag is used, and the css applied to image, so that I can reproduce it easily and correctly.

@hmin Honestly no idea about the code, because thats just exported from C2. If you load up C2, make a blank layout 720p, add in a 256 x 256 sprite of your choice.. then export it and go through the compile process in XDK or CocoonJS, you get the same result, more blurry after XDK compiled.

I've attached some links to a much simpler reproduction. I have also put links to the XDK apk and CJS apk.If you open and run either the C2 or CJS versions, the loading layout comes first, very quickly loads and takes you to the title screen.

If you try the XDK version then it gets stuck at the loading screen. You can get past this by pressing your phone home button to minimoise out. Then select the app icon again to load it back up. It will get past the stuck stage but will not trigger the 'physics gravity = 0' command.

I have left some extra lines in my titlescreen sheet for PeerJS pluggin and CLAY.ioThey are not needed for the title screen but they are needed in my app. I need to clear all PeerJS connections at the title screen and also I force close the clay.io login screen as for some reason XDK exports make it appear even when it is not called?

I am expecting crosswalk 6 this week, but the blacklist option will take a few more weeks because we are redoing the build system and it will come as part of some other changes. This is my best guess about timing--not a promise.

shinkan wrote:@IntelTyler @IntelRobert

When we can expect a change to stable 5.34.104.5 and beta 6.35.131.4 ? New Beta offers an option to ignore GPU blacklist and I'm curious how it works.

The behavior of displaying splashscreen during orientation change is bad. Will fix it ASAP, and will let you know when it's fixed. You can also track the issue via jira: And also for your 1st question:I have tested locally with below cases:1. Use default splashscreen for both orientation2. Upload only one customized splashscreen.3. Upload two customized splashscreenAll of above cases can not reproduce the black white screen issue, Would you please share me your image of splashscreen? (You can upload to the jira or here)Thanks again.

1. To reproduce the black and white screen, change the orientation of your phone while the splashscreen is showing. For example, hold your phone in portrait mode, once the splashscreen is showing, turn your phone sideways to landscape mode. It should than reproduce the black and white screen.

2. Also for this, I have uploaded two splashscreen for both portrait and landscape. I wanted it to show the same image, so I used the same image for portrait, but just adjusted the resolution to be portrait. But something happens, when I do the 1 problem. When I turn the phone from portrait to landscape or vice versa, instead of the splashscreen staying the same because the two images in both modes are the same, it actually stretched the original image to fit the new orientation. That means a portrait image being stretched to fit a landscape resolution.

Hi @Mayfly, I have checked your XDKOffline.apk And inspected the app, found the error message from console: "Uncaught TypeError: Cannot read property 'closeModal' of undefined "

I have a short investigation about this error, and found it should be c2runtime error: There is no 'UI' item under 'Clay' for crosswalk, and will cause the javascript error. I have just commented out below codes in c2runtime.js 13846: if( ID ) Clay['UI']['closeModal']( 'clay-' + ID + '-wrapper' ); else 13849: Clay['UI']['closeModal']();

Hi @guangzhenMany thanks for taking the time to look into this. I will update my apk this afternoon and retest. If there are any files missing then they are not being generated by either C2 or XDK build as everything should be made automatically?

@ashley is there a chance that some clay.io files are not being exported properly for XDK? I remember there was something similar with clay and CJS were you had to implement some files into the exported zip file before cloud compiling it.THanks

@guangzhen, That's weird. I don't think it has to do with my image specifically, because even if I use the default splashscreen image, it also happens. So far, I've tested on a HTC One and Sony Z1 and they both have the same issues. I also notice earlier that there are other members beside me who are facing this same problem. For your information, it was built using the stable built. I will try it with the beta build and report if the issue still persist.

@rekjlI get the same issues with al my XDK builds. Put the phone in portrait and open the app. Turn to landscape and you get a half black and white screen for a moment while it loads. I have also noticed that sometimes a splashscreen will display if you have loaded in images, even if you choose not to have one displayed. Happens on stable and beta builds for me everytime.