Revision history [back]

I am using OpenCV for Android. Library version is 2.4.10. I want to use the findChessboardCorners() method in CameraCalibration.

Upon running, the code does nothing and I see a error message in logcat:

E/OpenCV_for_Tegra(xxxx): Canot create OpenGL context

I searched around and found there is a bug already open for the issue: http://code.opencv.org/issues/3372

However according to the link, the bug should have been fixed for my library version. I wondered if it's a different issue? Maybe just not enough memories?

I am using OpenCV for Android. Library version is 2.4.10. I want to use the findChessboardCorners() method in CameraCalibration.

Upon running, the code does nothing and I see a error message in logcat:

E/OpenCV_for_Tegra(xxxx): Canot create OpenGL context

I searched around and found there is a bug already open for the issue: http://code.opencv.org/issues/3372

However according to the link, the bug should have been fixed for my library version. I wondered if it's a different issue? Maybe just not enough memories?

I am using OpenCV for Android. Library version is 2.4.10. I want to use the findChessboardCorners() method in CameraCalibration.

Upon running, the code does nothing and I see a error message in logcat:

W/Adreno-EGL﹕ : EGL_BAD_CONFIG

E/OpenCV_for_Tegra(xxxx): Canot create OpenGL context

I searched around and found there is a bug already open for the issue: http://code.opencv.org/issues/3372

However according to the link, the bug should have been fixed for my library version. I wondered if it's a different issue? Maybe just not enough memories?

I am using OpenCV for Android. Library version is 2.4.10. I want to use the findChessboardCorners() method in CameraCalibration.Utils.bitmapToMat() method.

Upon running, the code does nothing and I see a error message in logcat:

W/Adreno-EGL﹕ : EGL_BAD_CONFIG

E/OpenCV_for_Tegra(xxxx): Canot create OpenGL context

I searched around and found there is a bug already open for the issue: http://code.opencv.org/issues/3372

However according to the link, the bug should have been fixed for my library version. I wondered if it's a different issue? Maybe just not enough memories?