Also, GLDiag is meant to test and output all the settings that a device returns. Check the logcat for what the device is returning. Even if the application ends up crashing, some settings may actually work, it's just that the application ends up selecting one mode in the end, which may not work.
andreia On Tue, May 1, 2012 at 4:31 PM, Andreia Gaita <[email protected]> wrote: > Hi, > > This is a problem that occurs in some devices because the device is > returning invalid graphics settings when initialized. I thought it was > only Samsung doing this, looks like it's not. Some devices don't fail > every time, giving them some lower settings sometimes work. Check the > TexturedCube sample in the monodroid-samples for alternate ways to > initialize the GraphicsMode object with different settings. This has > been fixed and the fix will be on the next release. > > andreia > > On Tue, May 1, 2012 at 4:41 AM, vchelaru <[email protected]> wrote: >> I was able to reproduce this same problem with 4.0.6 on a Motorola Droid (1). >> Maybe I missed it but this thread doesn't seem to conclude whether this is a >> bug with MFA or if there's something that we can do to correct this problem. >> >> -- >> View this message in context: >> http://mono-for-android.1047100.n5.nabble.com/GLDiag-not-working-in-4-0-6-on-Samsung-Galaxy-S-tp5644655p5677392.html >> Sent from the Mono for Android mailing list archive at Nabble.com. >> _______________________________________________ >> Monodroid mailing list >> [email protected] >> >> UNSUBSCRIBE INFORMATION: >> http://lists.ximian.com/mailman/listinfo/monodroid _______________________________________________ Monodroid mailing list [email protected] UNSUBSCRIBE INFORMATION: http://lists.ximian.com/mailman/listinfo/monodroid
