IssueTracker

The iPhone Simulator has a nice UI for this.  You hold down a key combo and you see
two finger spots on the emulator screen, mirrored around the center of the screen.
Drag away from the center to pinch open; drag toward the center to pinch closed.

That is nice, but that only handles the case of "pinch".  It would be a good start,
and would handle probably the majority of common use cases, but there are certainly
very many ways I can move two fingers at once that don't even resemble a pinch.  :)

It is impossible to test multitouch gestures without having a multitouch capable
device... please add at least comment#1 suggestion !

This would be really handy.  I would also like to mention that many people with TUIO devices would love to use them to test.

Pinch is by far the most common multi-touch gesture IMHO. Also, the iPhone simulator also simulates two-fingered scrolling (dragging across the screen with two fingers). I can't think of any other two-fingered gesture that would make sense in a UI :)

Currently the Android version of our app is on hold because it uses multi-touch and we don't have an actual device to test it on.

Rotation is another useful gesture.

Whatever the "common gestures" are, it would be nice to be able to hold down certain keys on the keyboard to perform these gestures in the emulator. E.g. Ctrl for pinch, Alt for Rotate, etc.

In addition, I would like to be able to move additional pointers freely. It could work by holding down number keys, for instance. Holding/pressing "1" would freeze all current pointers and let you control the first pointer with the mouse (up/down/move). Holding/pressing "2" would freeze all current pointers and let you control the second pointer (up/down/move). Etc. This would be useful for apps that use actual multitouch and not just gestures.

Ahhh, come on, guys!  We need the right tools to help Google make its projected $10 billion/year on Android.  Can't you get an intern to do this?  Or a new college hire?

I want to second request the MPX support. Also supporting an standard protocol such as TUIO (tuio.org) will be very handy. That would make porting multi-touch apps to android a breeze.

With TUIO support, we could use the TUIO Simulator for testing Multi-Touch. I used that tool to develop a tabletop Application.

But a solution which is integrated into the android simulator would be much more handy.

MPX input on the emulator is very much needed!  So hopefully this will be added soon!  Without multi-touch apps, Android will never surpass the iPhone.

When we talk about MPX, we're not just talking about two fingers... I hope Android allows mapping of, say, four fingers simultaneously.

To #11, that would be a nice idea, but you have to keep in mind there are very different screen sizes and formats and doing letterboxing to, say, map a 16:9 real screen to a 4:3 or 1:1 screen might not be ideal.

Still, it's a nice idea to work around this while the emulator doesn't have direct support, IMHO.

[Comment deleted]

This feature is especially important since multitouch has been enabled since 2.0.

Even considering how bad Eclipse is, the emulator is the worst part of the SDK. It's slow. Try the iOS Simulator is relatively fast and doesn't take a minute to launch.

To be fair, the Android emulator is a legitimate phone emulator.  Almost _anything_ you can do with a real phone can be successfully tested in the emulator (save for multitouch, obviously, but that's an interface issue, not a software issue).  It really is emulating the ARM processor, which is what makes it slow.  The iPhone simulator does not actually emulate anything.  The "simulator" label is very appropriate, because it only simulates enough of iOS to run a version of your application (not necessarily the final compiled version that will run on the phone), so you can't really say for sure that "works in the simulator, works on the phone" like you can with Android's emulator.  Closer to it's original release, there were even a couple guys who hooked up GPS and an accelerometer to the emulator and used their laptop to test the app they'd developed before we had any physical phones, which is something the iPhone simulator couldn't even dream of.

Not to downplay the need for multitouch, but need to give props to the emulator folks where props are due, because they've done some seriously cool work.

Any official word from Google on this?  Apart from making the SDK faster, this is second on my wish list.  It's more than I nice-to-have.  You can't seriously test anything multitouch-related without an actual device, which is a pretty big drawback.

Also, to clarify another comment above: you can do more than multitouch scale (pinch-to-zoom) in the iOS simulator.  You can also rotate elements.  It's not as natural as it would be on an actual device, but it's passable.  Right now it's completely impossible in the Android emulator, save for actually simulating the events in JavaScript.

Google doesn't comment on (or read) bug reports in this issue tracker.

This issue is in the status "New", which means that no Googler has reviewed the issue. Unfortunately, it's not alone; 80% of the top 100 Defects are "New."

http://code.google.com/p/android/issues/list?q=Type%3ADefect&sort=-stars

And it's even worse when you look at the top 100 enhancements, all of which have more stars than this issue.

http://code.google.com/p/android/issues/list?q=Type%3AEnhancement&sort=-stars

Well, in r17 they've finally added "Multi-Touch" support, as detailed here: http://tools.android.com/tips/hardware-emulation#TOC-Multi-Touch

However, to use this multitouch support requires a phone tethered running their multi-touch simulation software, so it's still limited to folks owning a real phone, in which case you might as well test directly on the phone.

Hi there,

the online documentation is not up to date

see
http://code.google.com/p/android/issues/detail?id=34868

use the instruction you find in the SdkController application itself.

I'd like to see this feature implemented not so much because I don't have a device, but because sometimes I would like to:

1) Test multi-touch with different Android versions,
2) Develop on a remote desktop (hence no possibility to attach a physical device).

[Comment deleted]

[Comment deleted]

[Comment deleted]

What the Hey,  Is this going to be fixed anytime soon?

Implemented by CL 185430

Specifically, a pinch/rotate gesture was added in Emulator release 25.0.4 preview 5 - hold Alt to bring up the interface.

Reference issue 36949180 to track the addition of a "two-finger swipe gesture".
Reference issue 36949180 to track the addition of an interface for general multitouch input.

Yes, this is a separate bug. I'll file it separately internally. If you file a separate bug externally, I'll hook the two
of them together. Thanks

I've filed it as issue 36915848. Thanks.

Plz fix this bug.  We need to be able to dl .gpx files.  The nice weather is here!

Use c:geo on android. It downloads the cache information and logs back to the website.

This is still a problem on 2.2, at least in the "leaked" Nexus One build.

@LynJar:
If you want to run afoul of Geocaching.com's terms of service, then sure... go that route.  Not wanting to do that is a big reason that everyone is so interested in getting this bug (not enhancement) fixed.

Anxiously waiting for a solution

The bug is still not fixed in 2.2.1 . Though *sometimes* the file DOES download, most of the time I will get two request for the data which interfere and corrupt the download or lead to premature cancellation of the download.

If a form POST in the browser results in the download manager trying a GET to the same URI but without the form parameters, you'd be hard pressed to explain to me how that's not a bug.  At a minimum, reporting to the user that the download failed is a bug, instead of blocking the download manager from ever starting and telling the user it's a platform deficiency.  For the record, my interest in this isn't for geocaching, for me it's a crippling issue for a mobile corporate site currently in development, and will likely cause us to abandon support for Android devices if there's no fix in sight.

Still no fix after two years? This is an extremely crippling bug and should be high priority. This breaks every website that serves unique content based on POST data.

just discovered this issue with the GPX files ... shocking that this has not been fixed after 27 months.

Agreed, this is getting ridiculous

[Comment deleted]

this impacts ePUBs that are dynamically generated by post variables whose content EXCEEDS get usability.

I'm trying to write an app for a travel site that generates itineraries based on data posted from travel agencies, returning the itinerary as an XML document.  Opera works, downloading the document and firing up my app to read it, but I'm loathe to make Opera a requirement for the app. The stock browser should work properly.

We are caching files on the server for the sole purpose of supporting downloads from the android browser. I would have liked to just drop support for this browser, but users don't really understand enough about how browsers work to know that the problem is with the android browser and would probably just think our web app is broken.

Someone should really fix this. This a BUG, not an enhancement.

I have the exact same problem

My ERP .NET web app uses a form post to download an attachment from within a .NET DDL control.  On all platforms, the file downloads just fine, except on the Android.

I just spent 4 days LAN tracing, tearing my .NET web app down to bare minimums and spot debugging my Javascript to find out what *I* must be doing to cause this problem.  A LAN trace showed that my POST request for the download triggered an http response for the download, yet after a few packets, my Droid sent a FIN and RST and the download was cancelled.  Then a new GET request was issued with the same URI followed.  It turns out that the partially downloaded file is populated with the HTML as a result of the 2nd GET!  Weird!

I'm not angry, I just wanted to relay my experience and show that this bug is causing pain.  Also,  it is unfortunately forcing my hand when an employee is going to get a new smart phone and they ask "Droid or IPhone?".  Using the Droid platform, no-one can download attachments using my ERP web app.

Please address this problem as soon as possible.

This problem is such a big show stopper that it makes a related article in my blog having as many views as all other articles together!

For the time being the only reliable way to make downloads work from scripts that need to receive parameters, is to NOT transfer the parameters by POST, but by GET or by RESTful URLs (encoding all needed data for the HTTP request within the URL itself).

See http://digiblog.de/2011/04/19/android-and-the-download-file-headers/ for more details.

Cheers, Jörg.

When can this be fixed?  With 100 million Android phones out there, it would mean that millions of users daily are inconvenienced when they click a link to download a text file.

Thanks.

@kingkong:

Simple download links will usually work. The problem affects downloads that are initiated by a POST, e.g. a form that is sent using a POST request and in turn returns a downloadable file.

But you are right. It is unbelievable that this issue is still not fixed (and also that it is classified as an "enhancement" instead of as a "bug" - which is simply outrageous).

But then again: Until today not a single iPhone in the world is capable of adding a contact to its internal database, if the user clicks a link to a VCF file. They have to receive the VCF by email to process it correctly.

A world of ugly imperfections...

Just curious if this issue has fallen off the face of the earth? Basically, I have a web application that allows the client download zip files which of course works in every browser but the stock android browser! While the solution seems to be either use a different browser or upgrade the device to ICS, this is not acceptable for our clients. Any help would be appreciated!

Come on Google. 3 years, and we still can't download a file initiated by a POST?

Surely something that works in every other browser is a BUG, not an enhancement.

[Comment deleted]

Any hopes for this issue to be fixed?? I am experiencing this issue both in my HTC Desire HD and Galaxy Tablet 10.1

My company has developed a webapplication for work orders where one of the features is the ability to access all kinds of documentation about the job at hand from the smartphone. Up til now we have thought that this problem was due to some bug in the third party components we use for development and have gladly endorsed Android phones to around 2000 users (and counting). Since installing another browser for this functionality seems absolutely ludicrous (not to mention an inconvenience to our users and possibly a bigger workload for our support department) i regret we won't have any option but to recommend some other system until this get fixed. This is not just a problem for geocaching hobbyists. It's hurting our business and, ultimately, yours.

Regards

Sören Alexandersson
Svensk Dataförvaltning AB

Apple can't be better than Android. Download runs under Apple and even Microsoft but not Android... Please fix this!!!

Very big problem................

I'm developing an app that is running into this problem. It is NOT an enhancement.
This is a bug and should be fixed.

When I use Stock browser and Chrome(on JB and ICS), I download an index.php file.
The file itself is still the PDF file it is supposed to download, BUT it is not creating the proper name or extention.

Dolphin is now working properly. It looks like they have their own download manager that pops up, and then verifies the filename and location.

This is a BUG, not an enhancement.

Please fix this Andriod. We just re-verified this problem today.

It is a serious problem that.

[Comment deleted]

Hello,
seconding this also.
I encountered this issue about 1 year ago. Decided to wait see if it got solved. no luck. I'm back today looking on the web for a solution, still there's none provided. I guess Android's shares (and holders) don't suffer from this bug and sales are still fine. We may be waiting in vain.

[Comment deleted]

So, based on the status, this will nto be fixed?
Why? :|
What the hack are we supposed to do?
Change our implementations and our security policies (that work everywhere else but Android) just because Google doesn't want this fixed?

I don't know the reason for the Obsolete status of this issue. Why??

Download runs under Apple and even Microsoft but not Android... Please fix this!!!

I cant open my phone
Somting wrong
Com.android.systemui = stop