Occasionally (more often when the app is run from Eclipse it seems) the resolution of the camera is not set, defaulting to Rather Large. This causes performance problems currently, and a fix should be looked into.
Possible causes:
The LoaderCallbackInterface.SUCCESS case in the onManagerConnected() callback isn't being taken, so the call to setMaxFrameSize() isn't being called. Unlikely, since the touch listener is being attached as far as I can tell.
(more likely) There is some kind of race condition on setting up the camera/activity/app that makes the call to setMaxFrameSize() occasionally not matter. Some reordering or synchronization would fix this.
Occasionally (more often when the app is run from Eclipse it seems) the resolution of the camera is not set, defaulting to Rather Large. This causes performance problems currently, and a fix should be looked into.
Possible causes:
LoaderCallbackInterface.SUCCESScase in theonManagerConnected()callback isn't being taken, so the call tosetMaxFrameSize()isn't being called. Unlikely, since the touch listener is being attached as far as I can tell.setMaxFrameSize()occasionally not matter. Some reordering or synchronization would fix this.