That's also a fine question for device manufacturers and Google.
The manufacturer of one of the phones I have made the effort to publish
their drivers, including the one for ADB, on Microsoft's Windows Update.
Plugging the phone automatically found and installed those.
Another manufacturer (or two) makes the drivers available only as parts
of their bloated "phone management" software packages that want to take
over my life (or at least my computer).
Yet another does not have the "tablet management" bloatware, but there
seem to be no drivers on their site.
Personally, I often resort to .inf file hacking.
I suppose this _could_ be a part of the device certification process -
the manufacturer would be required to provide a public page to download
the drivers, or better yet, to do the Windows Update Center thing, but
the only thing we have right now is this:
http://developer.android.com/sdk/oem-usb.html
So I agree with Mark, going the WiFi route with the browser is probably
your best option.
You could set up a special WiFi-based environment just for this, with
its own DNS / web server, so the devices would connect to SSID
"installtheprogram" and go to "http://installtheprogram"; or something
along those lines for convenience.
-- Kostya
03.10.2011 21:38, Mark Murphy пишет:
> By the way, SIDE-QUESTION: WHY DOES LINUX REQUIRE NO DRIVER FOR ADB --
> YET WINDOWS REQUIRES SPECIFIC PER MANUFACTURER?)
That's a fine question for Microsoft. I doubt they are monitoring this list.:-)
--
Kostya Vasilyev
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
