Bug 5589 - Cannot deploy to HTC Flyer (2.3)
Summary: Cannot deploy to HTC Flyer (2.3)
Status: CLOSED NOT_REPRODUCIBLE
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Android Add-in ()
Version: unspecified
Hardware: PC Mac OS
: Normal normal
Target Milestone: ---
Assignee: Greg Munn
URL:
Depends on:
Blocks:
 
Reported: 2012-06-08 17:48 UTC by PJ
Modified: 2016-08-03 15:37 UTC (History)
5 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
CLOSED NOT_REPRODUCIBLE

Description PJ 2012-06-08 17:48:34 UTC
Deploying to the HTC Flyer with Gingerbread installed results in MD freezing.

Deploy to device output:

Detecting shared runtime location

Detecting package list location

Getting package list from device

Getting available internal storage space on the device

Installing 'AnotherTime.AnotherTime-Signed'
Package is already up to date

(no other output)



Logcat: https://gist.github.com/2898244



This issue does not occur on the HTC Flyer with HoneyComb installed.


Seen on 
MD 3.0.3.1
MFA 4.2.3
Mono 2.10.9_11
Comment 1 Greg Munn 2015-04-02 12:52:23 UTC
@pj, is this still an issue? seems like it might not be anymore given the age of the bug
Comment 2 PJ 2015-04-02 14:21:12 UTC
No, this should be cleaned up. I'll close. Thanks Greg!