Unfortunately, there has yet to be a resolution to this.
I tried to get this resolved by contacting Google, but they basically said 'no, we won't fix it because it's really old'. I tried to point out that this was a unique case, and that the fix was elementary, but in the end it felt like I was trying to reason with the Daleks. Eventually they locked the bug, took up their plungers, and went home.
Another avenue of appeal is to the crosswalk project itself. I suspect they may be a little more open to reason, but I haven't had time to write up a bug yet and submit it to them.
Intel is being strange about this, in that they acted like they wanted to get this resolved, made a blog post about it...and then just dropped the ball. I'm glad they are being active in the forum, and a recent alpha of the latest crosswalk build looks to be a big improvement, but part of providing a reliable method of deployment is supporting the only freakin' version of the exporter that works well on less-than-bleeding-edge devices.
tl;dr: Why the hell does it come down to users to resolve an issue like this? And what happens when a more significant bug crops up...?
/rant
P.S.
No hard feelings at Scirra, I get that Ashley is crazy overloaded, and this really isn't their responsibility in the first place.