Artem Kholodnyi
Artem Kholodnyi
1/ Documentation claims onSaveInstanceState will occur (if ever) before onStop, not onDestroy. I think you are right. http://developer.android.com/reference/android/app/Activity.html#onSaveInstanceState%28android.os.Bundle%29 2/ Not only onRestoreInstanceState as you mention but onSaveInstanceState are both conditional;...
Thanks for reporting! I think I'll get my hands on that very device on Monday and check if the same bug appears.
It occurs when texture can't be generated because of a trashed OpenGL context. One way it can happen when `mTilesFrameLayout.startAnimation()` is called after `mTilesFrameLayout.onPause()`. Do you work on your own...
@bradmartin the only was I can reproduce it if I comment out `mTilesFrameLayout.onResume();` call in demo app and then go from and back to activity. That would cause GL thread...
@bradmartin the only way I can reproduce it if I comment out `mTilesFrameLayout.onResume();` call in demo app and then go from and back to activity. That would cause GL thread...
@bradmartin Yes, any view can be in the layout. If there are several views - just wrap it in any `ViewGroup`. Exception at line 53 is thrown if `glGenTextures` failed...
cc @warko-san @PenzK @severianremi
It looks like it. libjpeg-turbo version need to be upgraded.
Same error here. @kiwiandroiddev do you have things like Dagger or ButterKnife which use annotations?
I don't see how sequential download does hurt. What really hurts - upload speed & share ratio limits - yet you can set them freely in settings and ignore everyone....