BTW Mark, since you are with Qualcomm, you should be able to find out more about the QualcommCameraHardware messages that we see in G1 crash logs? It is only most recently that I learnt that camera preview on the T-Mobile G1 uses some YUV 411 encoding instead of the emulators single supported format which is a YUV 422 variant. These kinds of "surprises" are killing for our camera based apps, and as a result also killing for our developer reputation with end users (they blame us for broken apps). My own camera app runs fine on the emulator but breaks and shows scrambled previews on the G1, at least in part due to this new find about the undocumented use of an 411 encoding that I still need to account for by writing a dedicated preview decoder. Who is sitting on this kind of vital developer information? Is it Google, T-Mobile or Qualcomm?
More about reporting about the ongoing struggle with the G1 QualcommCameraHardware at http://code.google.com/p/android/issues/detail?id=1129 and at http://groups.google.com/group/android-developers/browse_thread/thread/6e070855723aede0/ Any help is appreciated! Peter On Nov 5, 2:26 am, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > I was wondering if anyone has any information on when we could expect > improved camera support for the Android emulator, ie being able to > capture pictures and video input on the emulator. I know this is a > critical issue for many of us. Thanks in advance. > > Mark --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
