throbber
Case 6:21-cv-00569-ADA Document 153-5 Filed 01/12/23 Page 1 of 2
`Case 6:21-cv-00569-ADA Document 153-5 Filed 01/12/23 Page 1 of 2
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`EXHIBIT 9
`EXHIBIT 9
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`

`

`Case 6:21-cv-00569-ADA Document 153-5 Filed 01/12/23 Page 2 of 2
`
`FXPAL Blog » Blog Archive » Lean back with YouTube and Android
`10/18/21, 5:54 PM
`The Wayback Machine - https://web.archive.org/web/20111106221315/http://palblog.fxpal.com/?p=4953
`
`FXPAL Blog
`
`On technology and beyond!
`
`« Kno news is good news
`MyUnity, explained »
`Lean back with YouTube and Android
`
`Thursday, November 11th, 2010 by Surendar Chandra
`
`Google just released a YouTube remote control app that allows one to seamlessly continue watching a YouTube
`video from the Android phone to the YouTube Leanback system (and back). Leanback provides a relaxing way to access
`YouTube contents on a large screen such as on a Google TV or on a desktop screen. Leanback continually picks videos from your feed,
`including your video subscriptions, video rentals and related videos. The system is designed for minimal user interaction.
`
`The new remote control app behaves like a YouTube player until it detects that the user had also logged into the
`same YouTube account from a Leanback player (browser or Google TV). At this point, it transfers video
`playback to the Leanback system and starts behaving like a Leanback remote control. The remote allows one to
`perform the usual Leanback functions: pause and continue video playback, fast forward and rewind, as well as
`skip to the next or previous video from the feed. When the user logs out of the Leanback system, video playback
`is transferred back to the remote. Overall, the system behaves as expected. The controls were far more
`responsive than the YouTube video playback system itself.
`
`More interestingly, the system lets you search for new videos on the Android remote and schedule them for
`playback on the Leanback system. Under certain circumstances, this juke box functionality is far more useful
`than the iPhone remote app style of immediate control of video playback on iTunes/Apple TV. Perhaps one can
`even use the remote app during a Leanback based video demonstration: presenters can dynamically choose and
`schedule the next demo video based on the audience reaction.
`
`The system even works when the user logs into multiple Leanback browsers; remote control operations are
`seamlessly sent to all the browsers. However, there is apparently no feedback on the playback location from the
`browser back to the remote. So, any video browser that lags in playback will continue to respond to remote
`control commands, albeit at different points of the video. The ability to control multiple browsers is useful in the
`video demonstration scenario. For example, a presenter might see videos on a laptop, while also showing them
`on a nearby Google TV.
`
`In a Google TV scenario, one missing feature is a social video selection feature similar to iTunes DJ with the
`iTunes Remote app. In the iTunes scenario, any local user (within the same link local multicast domain – Apple
`uses Zeroconf for location) using an iPhone/iPod/iPad can request a song/video for playback while the iTunes is
`playing in the DJ mode. The system sorts the playback order based on the number of votes. However, we suspect
`that the wide area nature of the Leanback system prevents Google from naturally selecting “local” users who
`could be allowed to control the feed.
`
`https://web.archive.org/web/20111106221315/https:/palblog.fxpal.com/?p=4953
`
`1/1
`
`GOOG-PA-00000031
`
`

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket