throbber
Case 2:17-cv-00514-JRG Document 131-2 Filed 01/29/19 Page 1 of 3 PageID #: 9356
`Case 2:17-cv-00514-JRG Document 131-2 Filed 01/29/19 Page 1 of 3 PageID #: 9356
`
`IN THE UNITED STATES DISTRICT COURT
`
`FOR THE EASTERN DISTRICT OF TEXAS
`
`MARSHALL DIVISION
`
`AGIS SOFTWARE DEVELOPMENT LLC,
`
`Plaintiff,
`
`V-
`HTC CORPORATION,
`
`Case No. 2: 17-cv-00514-JRG
`(Lead case)
`
`Defendant
`
`JURY TRIAL DEMANDED
`
`AGIS SOFTWARE DEVELOPMENT LLC,
`
`Plaintiff»
`
`Case NO. 2: 17-cv-00515-JRG
`
`V
`
`(Member Case)
`
`LG ELECTRONICS INC”
`
`JURY TRIAL DEMANDED
`
`Defendant.
`
`DECLARATION OF WILLIAM LUH IN SUPPORT OF
`
`LG ELECTRONICS INC.’S MOTION FOR SUMMARY JUDGMENT
`
`I, William Luh, state and declare as follows:
`
`1.
`
`I am the Technical Lead Manager and Software Engineer for the Find My Device
`
`application on Android. I work out of Google LLC’s (“Google”) Mountain View, California
`
`

`

`Case 2:17-cv-00514-JRG Document 131-2 Filed 01/29/19 Page 2 of 3 PageID #: 9357
`Case 2:17-cv-00514-JRG Document 131-2 Filed 01/29/19 Page 2 of 3 PageID #: 9357
`
`office.
`
`I submit this declaration based upon my best and current knowledge of Find My Device,
`
`which I understand was previously branded as Android Device Manager. If called as a witness, I
`
`could and would testify competently to the information contained herein.
`
`2.
`
`Google, not any Android partner, is solely responsible for developing, designing,
`
`maintaining, modifying, making available and/or distributing the Find My Device system. Find
`
`My Device can be used to locate, ring, secure or lock, and/or wipe another device linked to a
`
`Google account. The functionality provided by Find My Device has always been categorized
`
`into different parts: (1) the receiver-side; (2) the client-side; and (3) the backend.
`
`3.
`
`The receiver-side of Find My Device on an Android device is what receives and
`
`implements remote instructions. More specifically, the receiver-side on a device is used to report
`
`the device location to Google servers and to implement received instructions (as sent from the
`
`client-side of the Find My Device) to secure or lock the device, to ring the device, or to wipe
`
`itself. This receiver-side is part of GmsCore, which is also known as Google Play Services,
`
`meaning every device that has GmsCore will also include only this receiver-side functionality.
`
`Moreover, the receiver-side of Find My Device does not include functionality to generate or
`
`transmit remote instructions to secure or lock, ring, or wipe a device.
`
`4.
`
`The client-side of Find My Device is the application and interface that a Google
`
`user interacts with to view an account-linked device’s location and to select and create a remote
`
`instruction to be transmitted to that device — e.g., to lock or secure the device, to ring the device,
`
`or to erase the device. The GmsCore package does not include this client-side application and
`
`interface. The client-side Find My Device application is available for download by users of
`
`Android phones via the Google Play Store, which is provided, managed, and controlled by
`
`

`

`Case 2:17-cv-00514-JRG Document 131-2 Filed 01/29/19 Page 3 of 3 PageID #: 9358
`Case 2:17-cv-00514-JRG Document 131-2 Filed 01/29/19 Page 3 of 3 PageID #: 9358
`
`Geogle. Software updates to the client-side Find My Device application are also provided via
`
`the Google Fla}.r Store.
`
`5.
`
`This client—side fitnetionaiity can also be assessed through an}.r generic web
`
`browser at the fellowing URL: https:ffwuav.geoglc.corufanflroidffind. Geogle provides and
`
`manages this webpage on their owl: servers, and, through that webpage, a user can also select
`
`and create the same remote instruction -- securedoek, ring1 or wipe — to be transmitted to a
`
`recipient device. To the extent accessed through a generic web browser on a mobile device, the
`J
`
`Google webpage functionality"ts never installed an that deviee.
`
`6.
`
`The backendts the bridge between the eltaot—stdeWM avaiiable fer
`
`
`
`the receiver-side defiee
`
`'_ ,aretaanaged,
`
`

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