Which Android device and OS version are you seeing the 30-second camera init times for? Are you seeing this behavior with any of the sample apps?
 

We are experiencing a similar issue.

Currently, our app’s loading time on iOS (iPad Air) is 6 sec but on new Android (Galaxy Tab S) it is 40 sec, which is unacceptably long. After doing some research we’ve discovered that the initial file system read operation done by Vuforia becomes extremely slow. Each such read operation takes ~15 seconds (!). Is it possible that Vuforia’s post-build process is causing that, e.g. due to the repacking of the APK?

We’re testing this using all of the latest versions:

·         Unity3d 4.5.4

·         Vuforia 3.09

.         Android 4.4.2

Thanks, 

amit7200 wrote:

We are experiencing a similar issue.

Currently, our app’s loading time on iOS (iPad Air) is 6 sec but on new Android (Galaxy Tab S) it is 40 sec, which is unacceptably long. After doing some research we’ve discovered that the initial file system read operation done by Vuforia becomes extremely slow. Each such read operation takes ~15 seconds (!).

Really interested to know how you tested this.
I seem to have encountered the same problem, with loading times exceeding 30 seconds and up to 80-90 seconds on a Samsung 3 and HTC One M7 Android device.
I am also using Unity3d 4.5.4 and Vuforia 3.09.

At first I though that this problem was due to the number of markers I have in the scene.
During testing I kept all the markers enabled, but had 2 versions of the app. The difference between these 2 version was the size of the Resources folder (No difference in code or loading assets from the resource folder).
The bigger\more items in the resources folder I had, the longer it took for the scene to load/initialize.

As this behaviour only occures in the scene which is included Vuforia components such as the AR camera/Image targets, I suspect that this problem has something to do with Vuforia (It might be testing something in the resource folder?)

I still need to test to see if there any differences in the loading time realted the size of the Resource folder in IOS.

Any further insights into this problem would be appreciated.

Are you able to provide some metrics on the data you are reading in? How many Device DBs in the scene? How many targets in each DB and size of each DB?
 

 How many Device DBs in the scene? 2 but i only load one for each build.

 How many targets in each DB and size of each DB? 48 and 56.

For these 2 Device DBs, are you re-loading them across multiple scenes in Unity or just once and persisting them? When do you notice increases in time over multiple attempts? Is it during scene changes or closing/restarting the app? It looks like across the various posts, that there's 3 different Android devices reported as having slow load times. Are there any Android devices that you've found that are loading DBs at faster speeds comparable to the iPad Air?

are you re-loading them across multiple scenes in Unity or just once and persisting them? no only once.

When do you notice increases in time over multiple attempts? all the attemps take the same time.

Is it during scene changes or closing/restarting the app? when i open the app.

Are there any Android devices that you've found that are loading DBs at faster speeds comparable to the iPad Air? no.

If you split your Device DB into two or three separate databases, does it improve the load times? Also, are all the targets in the DB assigned to ImageTargets in the scene? In other words, do you have any targets in your DB that you are not using in your scene?
 

If you split your Device DB into two or three separate databases, does it improve the load times? no it makes the load time much longer.

are all the targets in the DB assigned to ImageTargets in the scene? yes.

Are you able to reproduce the long load times by importing your data sets into the ImageTarget sample app? If you are able to isolate the long load time and provide us steps to reproduce that would be helpful. The Samsung Galaxy Tab S looks like it has a Quadcore processor. I haven't been able to reproduce the long load times when running using the ImageTarget sample app and a large data set on a dual-core 1.5GHz Android device.

Can you confirm the model number of the Samsung Galaxy Tab S and which processor?

http://en.wikipedia.org/wiki/Samsung_Galaxy_Tab_series#Samsung_Galaxy_Tab_S

Also, are you loading the data sets from an SD card or from the app resource folder?