`
`Case 2:17-cv-00513-JRG Document 74-8 Filed 01/05/18 Page 1 of 2 PagelD #: 1708
`
`IN THE UNITED STATES DISTRICT COURT
`
`FOR THE EASTERN DISTRICT OF TEXAS
`
`MARSHALL DIVISION
`
`AGES SOFTWARE DEVELOPMENT, LLC
`
`Plalntlffs
`
`IL
`
`CIVIL ACTION NO. 2:17—cV—Sl3-JRG
`
`HUAWEI DEVICE USA INC, HUAWEI
`DEVICE co, LTD. AND HUAWEI DEVICE
`
`(DONGGUAN) CO., LTD.
`
`Defendants.
`
`
`JURY TRIAL DEMANDED
`
`DECLARATION OF ANDREW OPLINGER REGARDING DEFENDANTS’ MOTION
`
`TO TRANSFER VENUE TO THE NORTHERN DISTRICT OF CALIFORNIA
`
`1, Andrew Oplinger, state and declare as follows:
`
`1.
`
`Until December 2017, I was a Technical Lead Manager for Google Product
`
`Infrastructure and work out of Google LLC’s (“Google”) Mountain View, California office.
`
`I
`
`submit this declaration based upon my personal knowledge, and, if called as a witness, I could
`
`and would testify competently to the information contained herein.
`
`2.
`
`I am aware that Google maintains relatively small offices in Austin, in the
`
`Western District of Texas, and Dallas, in the Northern District of Texas. However, based on my
`
`investigation, I am aware of no relevant witnesses in Google’s Austin office or Dallas office
`
`related to the design, development, operation, or management of the Google Maps for Mobile
`
`application (“GMM”) or Google’s Location Sharing functionality on GMM.
`
`3.
`
`Additionally, the source code used to compile the GMM application, including the
`
`Location Sharing feature is not publicly available, is highly confidential, and maintained internally
`
`
`
`
`
`Case 2:17-cv-00513-JRG Document 74-8 Filed 01/05/18 Page 2 of 2 PageID #: 1709
`
`Case 2:17-cv-00513-JRG Document 74-8 Filed 01/05/18 Page 2 of 2 PageID #: 1709
`
`by the Google engineers responsible for GMM or Location Sharing, including the Google
`
`personnel I previously identified in my first declaration.
`
`I declare under penalty of perjury that the foregoing is true and correct. Executed in
`
`Mountain View, California on January 3, 2018
`
`
`
`
`
`
Accessing this document will incur an additional charge of $.
After purchase, you can access this document again without charge.
Accept $ Charge
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.
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.
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
