I recently started working on a daydream project and for the most part everything is working great, but we've noticed that iteration speed is much worse than it is with a stock android project. Most notably, after launching to device I'd expect a subsequent launch with no changes to be quick (and in a stock android project, it is - just a few seconds).
But configured for daydream each launch takes about 3 minutes regardless of whether or not we've changed anything.
Notably, it seems to be configuring and compiling the apk twice? From watching the build process it seems like this is definitely the lion's share of the time. Is there something in the googlevr plugin that would cause this to happen?
I've attached a sample output log from a launch attempt. This is a subsequent run with no changes made to the project since the previous launch, and you can see it's taking just shy of 200 seconds to completely deploy to device. Even if it's just some hints for where to start looking to improve the situation, I'd greatly appreciate any advice!
But configured for daydream each launch takes about 3 minutes regardless of whether or not we've changed anything.
Notably, it seems to be configuring and compiling the apk twice? From watching the build process it seems like this is definitely the lion's share of the time. Is there something in the googlevr plugin that would cause this to happen?
I've attached a sample output log from a launch attempt. This is a subsequent run with no changes made to the project since the previous launch, and you can see it's taking just shy of 200 seconds to completely deploy to device. Even if it's just some hints for where to start looking to improve the situation, I'd greatly appreciate any advice!
Comment