Reports of this problem have been around for at least a couple months and it is still not fixed? From the log I can see that it appears to be a binding error and that was what was reported with the Gingerbread emulators.
On Feb 26, 1:16 pm, mp6800 <mport...@gmail.com> wrote: > Yeah the problem still seems to exist. Thankfully it's only in the emulator > though, at least for 2.3.3 (I'm testing on a Nexus One and it works > properly). Can anybody vouch for 3.0? -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
