We shipped Ticket to Ride with JOGL 2.0.2-rc-20130619 which was the latest version available at that time. We tried to refresh the project and track the JOGL release version 2.0.2 (mainly to fix an issue on desktop with NVidia cards where there was no compatibility profile available). Doing so broke the android version of the application with the following problem: there is absolutely no GLProfile available (and certainly no ES2 profile available). I'm attaching the full logcat run with jogl.debug=all available if that helps. I didn't try to run a newer JOGL version yet. It's possible that the issue comes from the fact we require a GL2ES2 profile, and not a pure GLES2 profile. I'll update the bug report with more detail as it comes.
Created attachment 512 [details] Jogl 2.0.2 no GLES2 profile available
Just tested 2.1.0-rc-20131006 and there's the exact same issue.
> Doing so broke the android version of the application What I can see is: +++ 10-09 17:50:53.711: W/System.err(14608): Platform: ANDROID / Linux 3.1.10-g1e8b3d8 (os), armv7l (arch), EABI_GNU_ARMEL, 4 cores 10-09 17:50:53.711: W/System.err(14608): Platform: Android Version: REL, 4.3 [4.3], SDK: 18, JELLY_BEAN_MR2 10-09 17:50:53.711: W/System.err(14608): MachineDescription: runtimeValidated true, littleEndian true, 32Bit true, primitive size / alignment: 10-09 17:50:53.711: W/System.err(14608): int8 1 / 1, int16 2 / 2 10-09 17:50:53.711: W/System.err(14608): int 4 / 4, long 4 / 4 10-09 17:50:53.711: W/System.err(14608): int32 4 / 4, int64 8 / 8 10-09 17:50:53.711: W/System.err(14608): float 4 / 4, double 8 / 8, ldouble 8 / 8 10-09 17:50:53.711: W/System.err(14608): pointer 4 / 4, page 4096 10-09 17:50:53.711: W/System.err(14608): Platform: Java Version: 0, VM: Dalvik, Runtime: Android Runtime 10-09 17:50:53.711: W/System.err(14608): Platform: Java Vendor: The Android Project, http://www.android.com/, JavaSE: true, Java6: true, AWT enabled: false +++ Can you be more specific about the android device which is broken ?
I just tested on: * nexus 4 * nexus 7 * kindle fire hd 7" and none of those work. I'm going to try on some other devices and report. The attached logcat is from the nexus 7.
So to add versions: * nexus 7 is running Android 4.3 * nexus 4 same version * kindle fire hd is running Android 4.0.4 * Xperia ZL running Andoird 4.1.2 * Samsung Tab 2 10.1 is running 4.0.4 All those devices runs perfectly with jogl 2.0.2-rc-20130619 which we shipped with originally. All those devices fail with jogl 2.0.2 and 2.1.0-rc-20131006, with the exact same log.
Created attachment 517 [details] kindle-fire-hd_7.jogl-test.log
(In reply to comment #6) > Created attachment 517 [details] > kindle-fire-hd_7.jogl-test.log Linux 3.0.8-02795 .. armv7l ARMEL Android 4.0.3 SDK15
(In reply to comment #7) > (In reply to comment #6) > > Created attachment 517 [details] > > kindle-fire-hd_7.jogl-test.log > > Linux 3.0.8-02795 .. armv7l ARMEL > Android 4.0.3 SDK15 .. working. Trying to update the kindle's firmware to 4.0.4 to match your version.
Created attachment 518 [details] nexus10.Android4_2_2.jogl-test.log
Created attachment 519 [details] nexus10.Android4_2_2.jogl-version.log
nexus10.Android4_2_2: works ..
Our proguard config was working fine with jogl 2.0.2-rc but not with versions afterward. Preventing proguard to shrink some jogl classes made it work on our devices. Closing this ticket as invalid (sorry for the noise...)