"We offer new support options and therefor the forums are now in read-only mode! Please check out our Support Center for more information." - Vuforia Engine Team

Vuforia slow intialization

We were using Vuforia 7.0.50 on our Android app for target recognition. On Google Pixel devices, initialization was just a couple of seconds. But on Samsung Galaxy S8 and Note 8, initialization was talking about 4-5 seconds.

We tried upgrading to Vuforia 7.2.0, but initialization was much worse on all devices. It is taking about 8 seconds to show up the camera stream on Note 8 and like 4 seconds on Google Pixel.

This is a major concern for us since Samsung devices compose a big part of the market and of our users devices. Is anyone else experiencing this?

Hello,

It is unclear to me why you'd see such differences in the initialization time on either release.

magglemitch

Sun, 08/05/2018 - 01:19

This is also happening for me on Android. Noticed it using Unity 2018.2 and Vuforia 7.2.2. On Android, it takes at least 4-5 seconds to start up the app. Previous versions of Unity/Vuforia would only take a second or so to load.

 

I wonder if the slow load time has something to do with the new auto load and activate databases in 7.1.  If you were manually loading and activating databases prior to 7.1+ , and your database had a decent number of trackables, you'd see a difference in load time after upgrading.

daverinnadesan18

Thu, 08/09/2018 - 13:28

Vuforia v7.2.24

Unity 2018.2.0f2

Hi I am experiencing the same problem after upgrading to v7.2.24 with my Samsung S9+. Initialization time used to be 0.5 seconds and is now 4-5 seconds on every application start (not just the first one).

Hello,

[quote=daverinnadesan18]

This means that it is not to do with the "Vuforia Engine Initialization" mentioned.

[/quote]

Apologies, but I'm not following your logic. How did you come to this conclusion? Which other version of Vuforia are you comparing this to?

daverinnadesan18

Sat, 08/18/2018 - 17:56

In reply to by medabit

Hi medabit.

I tried what you suggested and it worked. Why is it fetching the device profile on every application start? Why not fetch it only on first run?

How do I disable this feature and what would be the implications?

Thanks for your help

Daverin 

Hello @daverinnadesan18,

[quote=daverinnadesan18]

Why is it fetching the device profile on every application start? Why not fetch it only on first run?

[/quote]