All geek questions in one place

Calling Google Play services GoogleApiClient.connect () from Activity onStart () causes OpenGL to crash (NvRmChannelSubmit errors, etc.)

I upgraded our application to Google Play Services rev 17, this required a change in our 3D application activity from Activity to FragmentActivity. We also call GoogleApiClient.connect () much earlier than before, because Google recommends calling GoogleApiClient.connect () from the onStart () action.

This caused a serious regression: now the new program is reset about 30% of the time on the Nexus 7 at startup. NvRmChannelSubmit crash logs: NvError_IoctlFailed, followed by endless other NvRmChannelSubmit errors, which, in my opinion, simply indicate the broken state of the opengl driver.

This is a completely new error, nothing has changed in our application except:

  • activity changed from Activity to android.support.v4.app.FragmentActivity
  • The GPS init interface now starts earlier because we call connect () from onStart ()
  • updated to GPS rev 17 (which had a lot of changes, but hopefully nothing affected opengl!)

One theory I have is that the GPS connection interface and / or the basic change to FragmentActivity affects the window when the application starts and interferes with the initialization of the opengl driver. But I have no evidence, so I don’t know how to fix it.

Has anyone else seen problems with opengl drivers related to GPS UI thread or FragmentActivity?

+4
1

​​.

, opengl GoogleApiClient.connect() onStart(), opengl : connect() , OpenGL, ​​.

:

  • Google connect() Activity onStart(), opengl. opengl Nexus 7, 4.3, connect() GPS, .
  • connect() , , Activity onStop() GoogleApiClient.disconnect(), , , () (). GPS, , Google , , .

opengl. , GPS , onStart ( ). , GPS , FragmentActivity opengl.

+4

Source: https://habr.com/ru/post/1546369/

More articles:


All Articles