Hi, I am currently upgrading the old base to cupcake base. I meet 2 issues with video playback and surface flinger.
1. In my old code base, the YUV data is put onto overlay directly after a few seconds operations with postBuffer through base layer. This is mainly because android did not have framework for overlay previously. This worked fine until I move the same code onto cupcake recently. Right now I find even if I don't go through postBuffer any more, as long as the buffer list is not unregistered from the surface handler, surface flinger seems to keep pushing the last 1 or 2 frames onto base layer by itself. This costs a lot of CPU cycles when I actually only need overlay. My question: is this a new feature introduced into surface flinger? If so, is it reasonable for me to unregister this buffer list to save performance? And is there an interface in application level to control the behavior of surface flinger like disabling pushing the last frames? 2. Even if I unregister the buffer list of surface handler, there are still 2%-3% CPU Mhz (600MHz in total) consumed by "system_server". I did not observe this issue in older code base. It seems a bit weird as I dont know where it comes from. I'd appreciate if any hints are provided! Thanks, Andy --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "android-framework" 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-framework?hl=en -~----------~----~----~----~------~----~------~--~---
