On Oct 3, 1:38 pm, Mark Murphy <mmur...@commonsware.com> wrote: > On Mon, Oct 3, 2011 at 1:29 PM, dmacke <dma...@retaildoneright.com> wrote: > > We have a project for a Client to push an APK from a Windows platform. > > Basically we have an APYK we need to get pushed to a phone quickly and > > completely stupid proof. > > APYK?
Ok I admit it -- I am sloppy typist. You get what I mean -- you didnt have to call me out. Geez. This critique is coming from book author!? you guys are like chronic violators of errors in typing and abuse of the english language. > > > PRE-QUESTION - is there a way to launch a file saved on SD card > > WITHOUT a file browser? > > Well, *something* on the phone will have to kick off the APK install > process. That doesn't have to be a "file browser". However, there is > no end-user application that will do this as part of ordinary Android > builds, and there's no guarantee there will be one on any given > device. > > > But this only works when the USB drivers are configured on Windows -- > > now this leads to USB driver hell. > > Which is why you really want to use b) IMHO. Yes, getting WiFi hooked > up may be annoying, but they need that anyway in many cases, and it's > probably no more difficult than getting adb drivers to work. Also, if > they have a data plan, and the APK is available on the Internet, you > don't even need to fuss with the WiFi. The URL can be handled via a > URL shortener (e.g., goo.gl, or roll your own for mobile-friendly > URLs). Totally agree. We loved the wifi idea. We have short URL - easy to remember and totally small footprint to download. The Client dont like it. They dont have wifi and we dont have control of their environment. we are trying to market package that runs on Windows platform and interfaces with Android phone. But as you say the pain of Windows USB drivers may make someone think that maybe wifi aint so bad. One day hopefully will be there. I agree with you -- but I am assigned to get some sort of generic USB process working. > > 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. > :-) > > > Could a generic Windows USB driver be created for most every Android > > phone that would allow ADB functions? > > Possibly, but that has nothing really to do with this list, which is > for writing apps with the SDK. Perhaps try the [adt-dev] Google Group, > where there are discussions of the developer tools, including adb. D'oh!. will re-post there. Thank you. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
