Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Causes ADB Crash #26

Closed
GoogleCodeExporter opened this issue Nov 13, 2015 · 2 comments
Closed

Causes ADB Crash #26

GoogleCodeExporter opened this issue Nov 13, 2015 · 2 comments
Labels
auto-migrated Priority-Medium Type-Defect

Comments

@GoogleCodeExporter
Copy link 

What steps will reproduce the problem?
1. Trying to manipulate phone interface through computer. (Immediate)
2. Manipulating phone interface while viewing through computer. (Delayed)
3. Viewing static phone interface. (Longer delay)

What is the expected output? What do you see instead?
When performing any of the above actions, Windows alerts that ADB has failed.

What version of the product are you using? On what operating system?
Current version as of post on Windows XP Pro.

Please provide any additional information below.

Original issue reported on code.google.com by aasloan...@gmail.com on 4 Jan 2010 at 11:39
@GoogleCodeExporter
Copy link
Author 

May be an ADB issue. Will see if it's still crashing with ADB from SDK 2.0

Original comment by thiel.al...@gmail.com on 26 Jan 2010 at 5:16

  • Changed state: WontFix

@GoogleCodeExporter
Copy link
Author 

Are there any workarounds?

Original comment by Chet.Bri...@gmail.com on 1 Feb 2010 at 4:37

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
auto-migrated Priority-Medium Type-Defect
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@GoogleCodeExporter