blocks|key|687776|text|我有一个Logitech+Revue，它肯定不是一个快速的设备；我希望开发人员在瞄准它时注意性能。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|687777|根据此论坛链接的说法，这些是Revue的规范：|offset|length|687778|英特尔Atom+CE4150+1.2+GHz处理器，带有400+MHz图形处理器|unordered-list-item|687779|GA/T1482-1996+GA+2主板|687780|三星K9F8G08U0M+1+GB+NAND+(单级单元)数据表反射镜|687781|Hynix+H27UBG8T2ATR+4+GB+NAND闪存(多级单元)数据表|687782|TI公司的硅图像Sil9135+HDMI1.3接收机芯片信息数据表|687783|南亚NT5CB128M8CN-CG+1+GB+DDR3+SDRAM+(1GB+X8)数据表|687784|Realtek半导体RTL8201N+10/100+m+PHYceiver数据表|687785|PIC24FJ64GA004-I/PT+16位微控制器数据表|687786|PhisonS2251-50+USB到Flash控制器(根据生产情况，最终用户无法使用数据表)|687787|用于CPU数据表的IDT+时钟|687788|三星K9F8G08U0M+1+GB+NAND用于存储引导加载程序、内核、引导闪存图形、Linux等。Hynix+H27UBG8T2ATR|687789|4+GB+NAND闪存(长期存储)|687790|​
用于持久存储，设备是/dev/sda+-可以用外部USB驱动器覆盖
|687791|PIC24FJ64GA004-I/PT+16位微控制器|687792|用于处理遥控器/红外燃烧器的红外输入/输出以及可能与无线键盘的接口
系统重新启动/关闭
|687793|可能是HDMI+CEC|687794|硅像Sil9135+HDMI1.3接收机|687795|用于处理与HDMI端口之间的视频以及HDMI和SPDIF上的音频，即使Revue不支持DTS+(更新可能启用此功能)
|687796|用于CPU的IDT+ICS9LPRS525AGLF时钟|687797|为Intel+Atom+CPU提供时钟。
|entityMap|0|LINK|mutability|MUTABLE|url|http://www.googletvforum.org/forum/google-tv-hardware-discussion/891-logitech-revue-hardware.html^0|0|2|5|0|0|0|0|0|0|0|0|0|0|0|2|2|2|1|1|1|1|1|1|1^^$0|@$1|2|3|4|5|6|7|1R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1S|8|@]|9|@$D|1T|E|1U|1|1V]]|A|$]]|$1|F|3|G|5|H|7|1W|8|@]|9|@]|A|$]]|$1|I|3|J|5|H|7|1X|8|@]|9|@]|A|$]]|$1|K|3|L|5|H|7|1Y|8|@]|9|@]|A|$]]|$1|M|3|N|5|H|7|1Z|8|@]|9|@]|A|$]]|$1|O|3|P|5|H|7|20|8|@]|9|@]|A|$]]|$1|Q|3|R|5|H|7|21|8|@]|9|@]|A|$]]|$1|S|3|T|5|H|7|22|8|@]|9|@]|A|$]]|$1|U|3|V|5|H|7|23|8|@]|9|@]|A|$]]|$1|W|3|X|5|H|7|24|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|H|7|25|8|@]|9|@]|A|$]]|$1|10|3|11|5|H|7|26|8|@]|9|@]|A|$]]|$1|12|3|13|5|H|7|27|8|@]|9|@]|A|$]]|$1|14|3|15|5|6|7|28|8|@]|9|@]|A|$]]|$1|16|3|17|5|H|7|29|8|@]|9|@]|A|$]]|$1|18|3|19|5|6|7|2A|8|@]|9|@]|A|$]]|$1|1A|3|1B|5|H|7|2B|8|@]|9|@]|A|$]]|$1|1C|3|1D|5|H|7|2C|8|@]|9|@]|A|$]]|$1|1E|3|1F|5|6|7|2D|8|@]|9|@]|A|$]]|$1|1G|3|1H|5|H|7|2E|8|@]|9|@]|A|$]]|$1|1I|3|1J|5|6|7|2F|8|@]|9|@]|A|$]]]|1K|$1L|$5|1M|1N|1O|A|$1P|1Q]]]]

I have a Logitech Revue and it is certainly not a speedy device; I would hope that developers pay attention to performance when targeting it. 

According to <a href="http://www.googletvforum.org/forum/google-tv-hardware-discussion/891-logitech-revue-hardware.html">this forum link</a>, these are the specs for the Revue:

<ul>
<li>Intel Atom CE4150 1.2 GHz processor, with a 400 MHz GPU</li>
<li>Gigabyte GA-SBKAN2 motherboard</li>
<li>Samsung K9F8G08U0M 1 GB NAND Flash (Single Level Cell) Datasheet Mirror</li>
<li>Hynix H27UBG8T2ATR 4 GB NAND Flash (Multiple Level Cell) Datasheet</li>
<li>Silicon Image Sil9135 HDMI 1.3 Receiver Chip Information Datasheet from TI</li>
<li>Nanya NT5CB128M8CN-CG 1 GB DDR3 SDRAM (1 Gb X 8) Datasheet</li>
<li>Realtek Semiconductor RTL8201N 10/100M PHYceiver Datasheet</li>
<li>Microchip PIC24FJ64GA004-I/PT 16-bit microcontroller Datasheet</li>
<li>Phison S2251-50 USB to Flash Controller (Datasheet not available to end users according to manufacture)</li>
<li>IDT ICS9LPRS525AGLF Clock for CPU Datasheet
<ul>
<li>Samsung K9F8G08U0M 1 GB NAND Flash
Used for storage of bootloader, kernel, boot flash graphics, Linux OS etc..
Hynix H27UBG8T2ATR </li>
<li>4 GB NAND Flash (Long Term Storage)</li>
</ul></li>
</ul>

Used for persistent storage, device is /dev/sda - possible to override with an external USB drive

<ul>
<li>Microchip PIC24FJ64GA004-I/PT 16-bit microcontroller</li>
</ul>

Used to handle IR input/output for remotes/IR blasters and possible interface with wireless keyboard

System reboot/powerdown

<ul>
<li>Possibly HDMI CEC</li>
<li>Silicon Image Sil9135 HDMI 1.3 Receiver</li>
</ul>

Used to process video to and from HDMI ports as well as audio over HDMI and SPDIF
Supports DTS even though the Revue does not (An update can probably enable this feature)

<ul>
<li>IDT ICS9LPRS525AGLF Clock for CPU</li>
</ul>

Provides a clock for the Intel Atom CPU

blocks|key|207633|text|你注意到的是已经存在了一段时间的事情。某个地方的人决定称它为"10英尺用户界面“，而XBMC正是这样做的。一般来说，是的，用户体验在共享设备上有很大的不同，你不能也不会接触，而个人设备你会接触相当多。在手持设备上，用户界面往往是“通过外观玻璃”类型的东西。你可以直接与之互动和操作的东西。在一个10英尺的用户界面上，事情往往更大，更简单，更友好，间接地操纵像一个经典的0-9遥控器一样摇摇欲坠。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|207634|entityMap|0|LINK|mutability|MUTABLE|url|http://en.wikipedia.org/wiki/10-foot_user_interface^0|V|8|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

What you are noticing is something that has been around for a while. Somebody somewhere decided to call it the "<a href="http://en.wikipedia.org/wiki/10-foot_user_interface" rel="nofollow">10 Foot UI</a>" when XBMC was the way to do all this. Generally speaking, yes, the user experience is much different on a shared device that you cannot or would not be touching, versus a personal device you would be touching quite a bit. On a handheld device, user interefaces tend to be "through the looking glass" types of things. Things that you can interact with and manipulate directly. On a 10-foot ui, things tend to be bigger, simpler, and friendlier to indirectly manipulate with something as wonky as a classic 0-9 remote.

blocks|key|207690|text|考虑到Android最初是为内存有限的移动设备设计的，谷歌电视的应用程序设计有什么不同吗？|type|blockquote|depth|inlineStyleRanges|entityRanges|data|207691|从根本上说不是。这些设备可以以其形式存在，因为它们使用的是移动操作系统，因此可以在较便宜的硬件上运行。CPU可能围绕当前中级手机的性能；据我所知，GPU的性能要低得多(特别是考虑到它正在驱动的屏幕分辨率)，而目前它在手机上是典型的。|unstyled|207692|此外，已经宣布的下一代谷歌电视设备都是基于ARM的，因此期望它们的性能更接近。|207693|手机和平板电脑没有交换空间的奢侈，因此内存有很大的限制。谷歌电视也是这样吗？|207694|是的，这就是Android设计的运作方式。我不知道目前的GoogleTV设备中有多少内存，但我怀疑这比你在目前的安卓平板电脑(1GB)上看到的还要多。与往常一样，您可以使用ActivityManager.getMemoryClass()和ActivityManager.getLargeMemoryClass()来查找正在运行的设备的内存状况。|offset|length|207695|Dalvik+VM是针对手机/平板电脑的最小内存占用而优化的。Google+TV是由完全相同的VM驱动的吗?这是专门为Google设计的一个稍微不同的版本(但所考虑的设计目标是相同的)，还是完全不同的VM+(考虑到不同的设计目标)？|207696|它是完全相同的VM，只运行在x86上。|207697|当比较手机/平板电脑和谷歌电视时，硬件上的实际差别是什么？这些差异有意义吗？|207698|有一些显而易见的事情：|207699|输入主要是通过DPAD交互，所以您希望实现您的应用程序，以便与DPAD的交互工作良好。Android一直支持与DPAD的完全交互，所以这并不是什么新的东西，只是当前面向移动的开发人员经常忽略的应用程序设计的一部分。(然而，正确地支持DPAD不仅仅是为了GTV，当用户与键盘交互时，它对于像华硕变压器这样的东西也很重要。)|unordered-list-item|207700|没有像加速度计之类的传感器。您可以使用平台app+(如PackageManager.hasSystemFeature()+)来确定硬件特性是否存在，或者在清单中声明对该功能的要求，这样应用程序就无法在这些设备上使用。|207701|这些设备不能旋转，所以您需要在景观屏幕上工作。|207702|当然，您将要运行的屏幕比典型的手机屏幕要大，但是由于Android支持平板电脑，您可以使用许多工具(例如片段)来调整以利用屏幕的优势。特别是现在您可以假设这些设备正在运行3.x或更高版本，平台中引入的所有平板电脑基础设施都是可用的。|207703|还有一篇关于GoogleTV在模式上的UI设计的冗长文档，其中有很多关于如何在电视上思考UI的好材料。关于GoogleTV的UI设计有很多细节；我建议您注意总体要点(+UI可用的空间并不比手机多，不要围绕鼠标之类的交互来设计UI，等等)，然后决定在电视上展示手机/平板用户界面的意义是什么，而不是做一些更定制的事情来遵循GoogleTV指导方针。只要您遵循与DPAD导航等良好工作的UI基础，我认为您将是好的。|207704|entityMap|0|LINK|mutability|MUTABLE|url|http://developer.android.com/reference/android/app/ActivityManager.html#getMemoryClass%2528%2529|1|http://developer.android.com/reference/android/app/ActivityManager.html#getLargeMemoryClass%2528%2529|2|http://developer.android.com/reference/android/content/pm/PackageManager.html#hasSystemFeature%2528java.lang.String%2529|3|https://developers.google.com/tv/android/docs/gtv_android_patterns^0|0|0|0|0|2E|W|0|3B|11|1|0|0|0|0|0|0|R|X|2|0|0|0|F|2|3|0^^$0|@$1|2|3|4|5|6|7|1J|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|1K|8|@]|9|@]|A|$]]|$1|E|3|F|5|D|7|1L|8|@]|9|@]|A|$]]|$1|G|3|H|5|6|7|1M|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|1N|8|@]|9|@$K|1O|L|1P|1|1Q]|$K|1R|L|1S|1|1T]]|A|$]]|$1|M|3|N|5|6|7|1U|8|@]|9|@]|A|$]]|$1|O|3|P|5|D|7|1V|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|1W|8|@]|9|@]|A|$]]|$1|S|3|T|5|D|7|1X|8|@]|9|@]|A|$]]|$1|U|3|V|5|W|7|1Y|8|@]|9|@]|A|$]]|$1|X|3|Y|5|W|7|1Z|8|@]|9|@$K|20|L|21|1|22]]|A|$]]|$1|Z|3|10|5|W|7|23|8|@]|9|@]|A|$]]|$1|11|3|12|5|D|7|24|8|@]|9|@]|A|$]]|$1|13|3|14|5|D|7|25|8|@]|9|@$K|26|L|27|1|28]]|A|$]]|$1|15|3|-4|5|D|7|29|8|@]|9|@]|A|$]]]|16|$17|$5|18|19|1A|A|$1B|1C]]|1D|$5|18|19|1A|A|$1B|1E]]|1F|$5|18|19|1A|A|$1B|1G]]|1H|$5|18|19|1A|A|$1B|1I]]]]

<blockquote>
 Considering that Android was originally designed for mobile devices
 with limited memory, is designing an application for a Google TV any
 different?
</blockquote>

Fundamentally, no. These devices can exist in their form because they are using a mobile OS and so can run on less expensive hardware. The CPU may be around the performance of current mid-level phones; as far as I can tell the GPU is much lower performance (especially given the screen resolution it is driving) then currently typical on phones.

Also, the next generation Google TV devices that have been announced are ARM-based, so expect them to be much more similar in performance.

<blockquote>
 Phones and tablets don't have the luxury of swap space and therefore
 there are hard limits on memory... is this also the case with a Google
 TV?
</blockquote>

Yes, this is how Android is designed to operate. I don't know off-hand how much RAM is in the current GoogleTV devices, but I doubt it is more than what you are seeing on current Android tablets (1 GB). As always you can use <a href="http://developer.android.com/reference/android/app/ActivityManager.html#getMemoryClass%28%29" rel="nofollow noreferrer">ActivityManager.getMemoryClass()</a> and <a href="http://developer.android.com/reference/android/app/ActivityManager.html#getLargeMemoryClass%28%29" rel="nofollow noreferrer">ActivityManager.getLargeMemoryClass()</a> to find out the memory situation of the device you are running on.

<blockquote>
 The Dalvik VM is optimized for minimal memory footprint on
 handsets/tablets... is Google TV powered by the exact same VM, a
 slightly different version designed specifically for the Google TV
 (but with the same design goals in mind), or a completely different VM
 (with different design goals in mind)?
</blockquote>

It's the exact same VM, just running on x86.

<blockquote>
 What are the actual differences in hardware when comparing a
 handset/tablet and a Google TV? Are these differences significant?
</blockquote>

There are a number of obvious things:

<ul>
<li>Input is primarily through DPAD interaction, so you want to implement your app so that interaction with the DPAD works well. Android has always supported fairly complete interaction with the DPAD, so this is not really anything new, just a part of application design that current mobile-oriented developers often let slide. (However it is good to support the DPAD correctly for more than just GTV, it is also important for things like the Asus Transformer when the user is interacting with a keyboard.)</li>
<li>There are no sensors like an accelerometer, etc. You can use the platform APIs like <a href="http://developer.android.com/reference/android/content/pm/PackageManager.html#hasSystemFeature%28java.lang.String%29" rel="nofollow noreferrer">PackageManager.hasSystemFeature()</a> to find out whether a hardware feature exists, or declare the requirement for the feature in your manifest so the app is not available on such devices.</li>
<li>These devices can't rotate, so you will need to work in a landscape screen.</li>
</ul>

Of course the screen you will be running on is larger than a typical phone screen, but with Android's support for tablets you have a lot of tools (such as fragments) available to adjust to take advantage of the screen. Especially now that you can assume that these devices are running 3.x or later, all of the infrastructure introduced in the platform for tablets is available.

There is also a lengthy document on UI design for GoogleTV at <a href="https://developers.google.com/tv/android/docs/gtv_android_patterns" rel="nofollow noreferrer">https://developers.google.com/tv/android/docs/gtv_android_patterns</a> that has a lot of good material on how to think about your UI on a TV. There are many specifics on the UI design of GoogleTV; I would suggest you pay a lot of attention to the overall points (the space available for UI is not that much more than a phone, don't design your UI around mouse-like interaction, etc) and then decide what makes sense for you how much you are just going to present your phone/tablet UI on the TV vs. doing something more customized to follow the GoogleTV guidelines. As long as you follow the basics with a UI that works well with DPAD navigation and such, I think you will be good.

First of all, I am not asking "is it OK if I totally forget about efficiency when writing an application for a Google TV". I would never do that! :)

But I'm still curious: what are the differences between developing something for a Google TV and a mobile device such as a tablet/handset? I have found a lot of information online about the differences in user interface design (i.e. TV is meant to be more social, no screen orientations, no touchscreen, etc.) but none of the documentation describes the hardware-specific differences between the two devices. To be more specific,

<ol>
<li>Considering that Android was originally designed for mobile devices with limited memory, is designing an application for a Google TV any different?</li>
<li>Phones and tablets don't have the luxury of swap space and therefore there are hard limits on memory... is this also the case with a Google TV?</li>
<li>The Dalvik VM is optimized for minimal memory footprint on handsets/tablets... is Google TV powered by the exact same VM, a slightly different version designed specifically for the Google TV (but with the same design goals in mind), or a completely different VM (with different design goals in mind)?</li>
<li>What are the actual differences in hardware when comparing a handset/tablet and a Google TV? Are these differences significant?</li>
<li>Does Ice Cream Sandwich and Jelly Bean improve performance in any way (i.e. does it make use of these new hardware capabilities?)</li>
</ol>

Google TV - is designing for efficiency as important as it is with handsets/tablets?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

首先，我并不是在问“如果我在为谷歌电视编写一个应用程序的时候完全忘记了效率，那好吗？”我绝不会这样做！)但我还是很好奇:为谷歌电视和平板电脑/手机等移动设备开发东西有什么区别？我在网上发现了很多关于用户界面设计差异的信息(也就是说，电视应该更加社会化，没有屏幕定位，没有触摸屏等等)。但是这些文档都没有描述这两种设备之间...

问谷歌电视--设计效率和手机/平板电脑一样重要吗？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问谷歌电视--设计效率和手机/平板电脑一样重要吗？EN