Intel® XDK FAQs - Crosswalk

Q1: How do I play audio with different playback rates?

Here is a code snippet that allows you to specify playback rate:

var myAudio = new Audio('/path/to/audio.mp3');
myAudio.play();
myAudio.playbackRate = 1.5;

Q2: Why are Intel XDKs Android build files so large?

If your app has been built with Crosswalk, it will be a minimum of 15-18MB in size because it includes a complete web browser to use instead of the built-in webview on the device. Despite the size, this is the preferred solution for Android, because the built-in webviews on the majority of Android devices are inconsistent.

When using the "Legacy" build option, changing the code base from "gold" to "lean" will reduce the size of your APK, but the "lean” option also excludes the Cordova 2.9 library components (among other elements). Investing time and effort in the legacy build system is not recommended as it has been deprecated and will be obsolete sometime during 2015. The legacy build system also cannot take advantage of the numerous Cordova plugins that are available for use with the Cordova and Crosswalk build systems.

Q3: Why does my Android Crosswalk build fail with the com.google.playservices plugin? [Plugin]

The Intel XDK Crosswalk build system does not support the library project format that was introduced in the com.google.playservices@21.0.0 plugin. Use "com.google.playservices@19.0.0" instead.

Q4: Why is the size of my installed app much larger than the apk for a Crosswalk application?

This is because the apk is a compressed image, so when installed it occupies more space due to being decompressed. Also, when your Crosswalk app starts running on your device it will create some data files for caching purposes which will increase the installed size of the application.

Q5: Why does my app fail to run on some devices?

There are some Android devices in which the GPU hardware/software subsystem does not work properly. This is typically due to poor design or improper validation by the manufacturer of that Android device. Your problem Android device probably falls under this category.

Note that each iteration of the Crosswalk system is based on more recent versions of the Chromium project. Each new version of the Chromium project has become more "agressive" with regard to its use of the GPU subsystem on Android devices. Our experience has been that the Crosswalk 7 build is the least aggressive regarding the use of the GPU subsystem and generally runs on the widest array of Android devices. If you desire maximum compatibility, you should use the Crosswalk 7 build option.

Q6: How to I stop the "pull to refresh" from resetting and restarting my Crosswalk app?

See the code posted in this forum thread for a solution: https://software.intel.com/en-us/forums/topic/557191#comment-1827376.

Back to FAQs Main