I’ve never used it myself, but @mquadrat posting something about this a while ago. Maybe you should get in touch with him about it and get some advice
I know the thread @mquadrat, I was hoping somebody could provide some instructions on the forum. I know it would certainly cut down on support requests / bug reports if people start using these libraries instead of the stock Android browser in their Android builds.
Yeah I was also hoping for some advice. Seems like we have to figure it out on our own Not sure when I find a few hours to test it out. I’m very busy at the moment.
Well, I haven’t tackled it yet, but when I get around to deploying on Android I certainly intend to use Crosswalk myself if Ionic hasn’t yet rolled it (or ChromeView) into the cli.
I may play around with that sooner than I planned if others are interested. I think it’s going to be crucial for supporting Android. The stock web view on pre 4.4 devices is a donkey.
It’s pretty painless to migrate the code from ‘assets’ over to the CrossWalk preferred location if you use the CrossWalk ./bin/create command to use as a template. The biggest pain point was adapting to the workflow it forces on you - specifically using the ./bin/build and ./bin/run in the dev cycle (instead of cordova/ionic prepare/build/run) and switching from the ‘cordova’ binary to ‘plugman’ to manage plugins. Coincidentally CrossWalk solved a myriad of problems with elements that are generated dynamically that are missing (or rather disabled/invisible) on the device but appearing in a emulator or hosted environment.
Could you provide a tutorial or blog post explaining each step ? It would help a lot of people.
Thanks for the links !
Unfortunatly, I have a BUILD failed error with the Hello world app
I’ve posted on the intel forum : https://forums.html5dev-software.intel.com/viewtopic.php?f=34&t=5884
I resolved my issue by using the last beta version. Everything is so fluid now !
Did you switch from the Canary branch to the Beta branch? What version of were you having issues with?
If you want to build project again using “ionic build android” you can follow these steps:
- Migrate project to CrossWalk as given on their website. Follow eclipse steps instead of replacing cordova library. (keep cordova library file on platform\android as it is, don’t replace)
- I noticed that it changes project.properties file (when you import project in eclipse and change the dependencies)
I kept both project.properties file. (prior to project import in eclipse - projectC.properties, after import - projectT.properties)
I created android.sh file with following lines:
#!/bin/bash mv platforms/android/project.properties platforms/android/projectT.properties mv platforms/android/projectC.properties platforms/android/project.properties ionic build android -d mv platforms/android/project.properties platforms/android/projectC.properties mv platforms/android/projectT.properties platforms/android/project.properties
now you can build project using this android.sh file and compile project in eclipse.
I can confirm Crosswalk improves the scrolling and transition animations. Tested on Galaxy S4 4.4.2.
In Eclipse you import the crosswalk framework folder as a project. I used the Cordova Android (ARM) stable version.
Then Eclipse in project properties of the app, remove CordovaLib from Libraries and add Cordova and xwalk_core_library. Don’t forget to add Wifi and Network state permissions to Android manifest file.
It would be great if ionic CLI would support this.
I also used Crosswalk on a Galaxy S3, and solved many problems like phonecalls and various performance enhancements, specially on video. All the app feels much more responsive, and more native.
My way is probably the simplest: install all comand-line apps necessary (only needed to install python in my case, already had Ant and Java).
Then download a crosswalk-cordova zip (I used an 8 beta version, had zero problems).
Create a new app using the new template project. Then replace the
<new app>/www content with your current Ionic
<app>/www contents, and execute
I also can’t wait for Ionic to use it on the CLI.
If anyone is still facing issue in packing Ionic app with Crosswalk, check my response on below thread.
I use IntelXDK to package Ionic app with crosswalk and its simple few clicks, no command line required. I hope below link will help many, let me know if you face any issues in following the instructions.
I also packaged my ionic project with Intel XDK and crosswalk, however I didn’t see any animation performance improvement.
What improved my animation perf a little bit was using bindonce fix. It worked fine for a small list which used to suck with default ng-repeat. But when I use a slide animation for a view with resolve, it lags as usual.
I believe Android animation performance should be Ionic Team’s number 1 priority at this point.
I agree. Android needs focus. The performance is crap. I have the very latest Samsung Alpha and it lags horribly. While on iOS it feels like an app.
Please work on the Android native feel!
I also agree, though i did check ionic in intel xdk, and the performance was better, especially in lists, some of the transitions behave a bit different than in chromium build… built it is better. though, i also think the performance in android needs a bit of tweaking, I am sure the ionic team are working on it. maybe do native scrolling inside the app to feel more snappy or such.
if ionic can pull the android performance standard with their framework, i am almost sure it will be the standard…