I am connecting to the Revue Google TV device via adb connect IPAddress of GTV which is connecting fine and showing up in ddms.
When I go to take a screenshot of one of our GTV app's we get "Screen not available" in the Device Screen Capture window and in the console it prints: 05:51:15 D/ddms: image params: bpp=32, size=7471104, width=1824, height=1024 05:51:40 D/ddms: read: timeout 05:51:40 W/ddms: Unable to get frame buffer: timeout
Connecting an N1 and attempting to take a screenshot of that device works fine.
Running latest Revue update to GTV 2.0 and have tried both r12 and r16 adb tools on multiple Windows 7 machines with the same results. N1 screenshot completes and on Revue screenshot shows error.
I have also tried a factory reset (Settings, privacy, reset) - which did fix Chrome not showing up after the update, but screenshots still not working.
Please help, we need screenshots to post to market.
On Mon, Dec 12, 2011 at 4:57 PM, Dustin Brand <dustinbr...@gmail.com> wrote: > Hello Google TV team,
> I am connecting to the Revue Google TV device via adb connect IPAddress of > GTV which is connecting fine and showing up in ddms.
> When I go to take a screenshot of one of our GTV app's we get "Screen not > available" in the Device Screen Capture window and in the console it prints: > 05:51:15 D/ddms: image params: bpp=32, size=7471104, width=1824, > height=1024 > 05:51:40 D/ddms: read: timeout > 05:51:40 W/ddms: Unable to get frame buffer: timeout
> Connecting an N1 and attempting to take a screenshot of that device works > fine.
> Running latest Revue update to GTV 2.0 and have tried both r12 and r16 adb > tools on multiple Windows 7 machines with the same results. N1 screenshot > completes and on Revue screenshot shows error.
> I have also tried a factory reset (Settings, privacy, reset) - which did > fix Chrome not showing up after the update, but screenshots still not > working.
> Please help, we need screenshots to post to market.
Please send questions to the list<https://groups.google.com/forum/#!forum/googletv-android>and only use my email address for things that require privacy such as source code or APK's. We also answer questions on StackOverflow.com #Google-TV
Thanks for the quick reply. Same error with or without Live TV in PIP.
Also, as I said earlier, ADB is working as I can connect to, launch/publish apps, and see Logcat output from the GTV device, so it's not that. adb devices also lists the GTV unit.
If I connect my N1 via USB, it works as well, so it's not the ddms version or the tools version. Screenshots on the same ddms window work for the N1 or an emulator.
I am also getting these messages from the GTV device: 07:08:26 E/EventLogParser: unknown tag number: 1290501 07:08:26 E/EventLogParser: unknown tag number: 1290704 07:08:26 E/EventLogParser: unknown tag number: 1290703
Hope that helps clarify - if you engineers need any more info, please let me know. I'd really like to get this resolved soon as it's preventing us from deploying an app.
On Mon, Dec 12, 2011 at 6:10 PM, Dustin Brand <dustinbr...@gmail.com> wrote: > Hi Les,
> Thanks for the quick reply. Same error with or without Live TV in PIP.
> Also, as I said earlier, ADB is working as I can connect to, > launch/publish apps, and see Logcat output from the GTV device, so it's not > that. adb devices also lists the GTV unit.
> If I connect my N1 via USB, it works as well, so it's not the ddms version > or the tools version. Screenshots on the same ddms window work for the N1 > or an emulator.
> I am also getting these messages from the GTV device: > 07:08:26 E/EventLogParser: unknown tag number: 1290501 > 07:08:26 E/EventLogParser: unknown tag number: 1290704 > 07:08:26 E/EventLogParser: unknown tag number: 1290703
> Hope that helps clarify - if you engineers need any more info, please let > me know. I'd really like to get this resolved soon as it's preventing us > from deploying an app.
Please send questions to the list<https://groups.google.com/forum/#!forum/googletv-android>and only use my email address for things that require privacy such as source code or APK's. We also answer questions on StackOverflow.com #Google-TV
If anyone runs into this issue on 3.1 and this build, the solution is to reboot with your Resolution set to 720p vs 1080p.
There is a bug in the 1080p ddms screenshot function due to the buffer size. You cannot take a screenshot using ddms @ 1080p but you will be able to @ 720p.
I was just about to pull my hair out trying to figure out why I could
see actions in the log but still not capture the screen. Thanks so
much for the 720p fix!
On Dec 14, 1:21 am, Dustin Brand <dustinbr...@gmail.com> wrote:
> If anyone runs into this issue on 3.1 and this build, the solution is to
> reboot with your Resolution set to 720p vs 1080p.
> There is a bug in the 1080p ddms screenshot function due to the buffer
> size. You cannot take a screenshot using ddms @ 1080p but you will be able
> to @ 720p.