Hi everyone,
I've got multiple devices that I do testing on for various android programs (.apks).
Right now I'm using adb. It's pretty fast but requires I do the installs one by one.
I know there is a way to specify a device using "adb devices" but I'm looking for a way to automate going through the device ids.
Anyone have any tips/info on how you could setup your computer so that you plug in all the devices, run one command/script and have android apps be installed across all devices?
Thanks!
Related
Hello. I've been long lurking about xda, and now for the first time would love some specific help.
I've been working on debugging some Android applications of mine and I need to test with multiple different devices, I just ran into one issue using the AVDs. I can't seem to change the name of the device that appears to the apps and play store for example. This is a very crucial part of my debugging, and since I don't have multiple real devices, I would love to be able to test different ones on the emulator.
For example: My actual device appears to apps/play as "HTC HTC Vision" (HTC Desire-Z)
The emulator appears to apps/play as "Verizon Phone".
I would like to be able to change the emulator to appear as "Galaxy SII" for example... Well.. It actually doesn't matter what the string is, just that it's different from the ones I already have tested.
Thanks : )
Hullo.
Looking for a little advice from folks about sideloading apks to multiple android devices at once (like, 8 or 9 of em). Searched around the forums a bit and couldn't find anything directly relating to this issue, so I figured I'd ask. I dunno if this belongs more in App development, but its an Android specific issue so...
At present I'm using Test Flight App (I'd post the URL but I'm too much of a noob here) to manage builds and releases. Its really great for getting beta builds out to the studio team, and to various beta testers and potential partners.
However there are a few issues with it, which are particularly problematic for quick iterations etc.
1) Actually downloading the apks is a manual process per device. So if you've a small QA team (or are working solo) it takes alot of time to get the newest build onto everything.
2) Each build has to be uploaded via the Test Flight website, then distributed to users on a build by build basis. This is a difficult to automate process, so makes having any kind of continuous integration system for nightlies etc. difficult at best.
I've been looking into possibly doing something like installing a Dropbox on each device and automating CI builds to a dedicated folder, which is shared via Dropbox to everything, but its a bit of work up front to get it working and I may still have to actually manually install the things each time.
Any of you guys had any experience attempting to do something like this?
Figured I might as well come back and answer my own question incase anyone else was wondering.
Ended up using a USB hub to connect multiple devices then running a script that used ADB to get all attached devices, then passed that list one by one into the adb install function.
Still not ideal, as it requires a wired connection for each phone, but works for now.
Dansixminute said:
Figured I might as well come back and answer my own question incase anyone else was wondering.
Ended up using a USB hub to connect multiple devices then running a script that used ADB to get all attached devices, then passed that list one by one into the adb install function.
Still not ideal, as it requires a wired connection for each phone, but works for now.
Click to expand...
Click to collapse
How about Wireless ADB?
Check ADB Wireless on Play Store. (Unfortunately all phones must be rooted, because it requires ADB port to be set to 5555)
https://play.google.com/store/apps/details?id=com.wave18.adbwireless
I think you are using batch file to get ADB script for all devices.
Press Thanks if helped.
Hi Devs!
I imagine this should be already discussed and explained somewhere, but I just can't find it as the word "android driver" is ambiguos and directs me to different topics.
Here we go with the question: nowadays many Android devices come with otgusb, so you can connect usb sticks, and all sorts of compatible devices. But: how to make a device compatible?
Since Android is linux, I assume loading a driver cannot be loaded just by installing an app, so do you need to call google and say "hey I got this new device, can you load the driver in your next kernel?" (sarcasm!!) or ...well...in short:
what the heck should one do if he wants to make a device compatible with android phones/tablets, even assuming he is able to write the driver by himself?
the question may be applicable to a variety of devices... a new remote one bought, a new BT wristband one wants to launch into the market, a usb sensor of some kind, etc etc etc.
thank you!
Ok, so I see there's apparently something called USB Host API, I read a little bit how it works, but I still have questions:
1. Does this mean basically that Android phone/tablet will provide RAW access via the USB Host API to any usb data stream received, and all I need is to write an app to decode that data?
2. If so, what makes a device compatible/incompatible?
3. If all of the above assumptions are wrong, please help
4. this still doesn't answer the bluetooth part, sorry for being so slow
Now with the advent of USB type C and the ability to Daisy chain 2 phones together to charge one from the other, I'm wondering if we could run terminal commands on one phone and send them to the other.
For example, instead of relying on a pc to send ADB and Fastboot commands to a phone, could we (at least at some point) connect 2 phones and send ADB/Fastboot from one phone to the other?
This would simplify rooting and could possibly even open up the possibility of having programs like NRT running on the Android platform.
Just my 2c
Sent from my Nexus 6P using XDA Free mobile app
There are some threads here that may in part bring up an issue with running emulators on Windows 10. I can only describe my difficulties and for whatever reason I like to use BlueStacks. Before I get into that one there is another that I have difficulties using like Droid4X which unlike Bluestacks, Droid4X has been able to try starting up, but then my PC crashes. I havent tried to fix using Droid4, mostly centered on how to get BlueStacks running.
BlueStacks, when I would try to start it would result in a pop up that mentions I can't use it because of Windows 10 Creation aspect runs something called Hyper-V and this is what prevents me. There were a few walk-arounds and Hyper v could be disabled, however, now in order to disable it requires going into the BIOS. This seems like a big hassle if you want to just bounce in for a minute to test an app. If you run it all day it wont matter.
As of yet I cannot find an emulator I can use on Windows 10 without having to go that far to do so. Seems to me that MSN is targeting anything Android in my PC. There are reasons I wonder, why on Earth would the August 14th update be removing the ADB USB Interface, device not recognized took me a while to correct among a few other issues I was calling MSN Tech support very angry with them.
I dont care if MSN doesnt like the fact they have been locked out of my PC, there will be no more updating anything, I told them. I am stuck with this Hyper-V getting in the way of running an emulator on Win 10.
My question is there anyone aware of an Android Emulator that can be used on MSN OS that Im unaware of, and free?