I tried many ADB Driver Softwares of Xaiomi redmi note but i am unable to use USB-debugging mode while running a real app from android studio
No need to install external ADB Driver for Redmi,Redmi already Provide with device. The device may not be visible for debugging if it is in MTP mode. Redmi 3S work in charging Mode in win 8.
This can be change
1. Go Setting
2. Additional Setting
3. Developers Option
4. Select USB Configuration
5. Select Charging Only
If you're having problem on Windows, perform the following
On your Windows desktop, Go to your Control Panel then Device Manager.
You should see Android Phone under Other Devices with a Yellow ! mark on it.
Right click on it and choose "Update Driver Software"
Choose "Browse my computer", then "Let me pick from a list."
If you see categories, select "Android Device", then select "MOT Composite ADB Interface".
The driver will install and you can now run the update with ADB.
Let me know if you have issues.
Related
I am using Android Studio version
Android Studio 3.4.1
Build #AI-183.6156.11.34.5522156, built on May 1, 2019
JRE: 1.8.0_152-release-1343-b01 x86_64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
macOS 10.14.5
with multiple Android devices including Pixel XL with Android Q (QPP4.190502.019)
All my test devices have started repeatedly displaying the
"Allow USB debugging?" PopUp
And losing ADB connectivity
What recent update has caused this behavior?
UPDATE
I reboot my laptop daily, as do my colleagues.
I and my colleagues have not updated USB drivers.
Ive tried multiple USB leads, as have my colleagues.
I've tried multiple Android devices and versions from 21 to Q
Devices include Pixel, Pixel 2, Pixel 3 & Pixel C, and Samsung S9, as have my colleagues.
I have revoked USB privileges and re granted on all devices, as have my colleagues.
The issue still persists
try to check the changelog for android studio update or have you try to enable the usb debugging in your device.
Haven't you installed/reinstalled Android USB drivers recently, if so try to reboot your system
It can also be caused by your broken USB cable, try to replace it with another one and check
I think you haven't checked never ask again option, that is why it's asking continuously.
So you can try to check that box if you haven't done that.
For others who might run into this problem, this started happening to me after I updated the OS version of my device. Restarting the device solved the issue.
On a Macbook Pro with Yosemite -
After getting through the difficulties of getting Android SDK installed, I plug in the device, but it doesn't show. The command adb devices yields "List of devices attached" with nothing following. It's there on the USB, the About This Mac System Report shows it present on the USB.
This question looks similar to Issue setting up the development environment for ProjectTango developemnt Device but is not the same because I'm not using Eclipse.
Please ensure that USB debugging is enabled in order to enter ADB, go to Settings > About tablet > Build number and then press Build number seven times. Then press back and go to Developer options > USB debugging.
Make sure you're using the latest Google USB driver. I was having this problem (but on Win 8) and updating the driver fixed it, I'm now getting the device in adb devices and can push content to it.
I am trying to debug my android application in sony xperia J but the
adb devices
returns no devices
I have enabled USB debugging, Mass storage and installed sony pc companion.
I also allowed to install external applications.
I tried with enabling USB teathering.
Is there any additional setting I am missing?
I guess I have installed drivers for it but I am not very sure.
Can somebody help me on this it is really irritating.
You have to be sure about drivers installed or not.
in my job I see many devices that are not recognised by adb at first.
I have noticed that this is happening due to an auto-mount of the sdcard on the computer.
make sure there are no mounted drives on your computer and that should fix this
You can use PC companion software connect Phone to PC for debugging
Link: http://www.sonymobile.com/in/tools/pc-companion/
and also try it
Settings > Xperia > USB Connectivity > USB Connection Mode and select MASS Storage, not MTP
If your USC pc connection is to Media device try changing it to Camera (PTP) or Vice Versa.
First you have to configure your phone not to install PC companion when connecting to PC by deselecting it from the phone menu. Also enable USB debugging and Mass storage, then connect the phone to the PC. Delete all devices that look like your phone in the Device Manager by uninstallling them. Then right-click and scan for hardware changes. Go to Android, right-click and Update driver. Browse folder until sdk/extras/google/usbdriver. Then Let me pick... Select Android phone, then have disk browse until sdk/extras/usbdriver. Select android_winusb.inf. Open, then select Android Composite ADB Interface. Next install. Wait until it is done and reopen Eclipse. You will find your phone there under devices.
I am running W8.1 x64 Pro and all above solutions had failed because Windows would not recognize a driver inside of sdk/extras/google/usbdriver even with a manual install.
Anyhow, my solution was to use Sony's PC companion tool, which was able to automatically download the drivers for my PC.
Official doc: http://dl-developer.sonymobile.com/documentation/other/Get_drivers_through_PC_Companion.txt
Now the abd interface is installed, and the phone is detected in adb devices.
I am trying to get Eclipse and DDMS to see my Google Glass device. I have followed the instructions found here:
https://developers.google.com/glass/develop/gdk/quick-start
However the DDMS device list is still empty no matter what I do. I have tried multiple USB ports and different cables. The Device Manager can see the Glass device but the DDMS doesn't. The DDMS can see emulators however.
After doing a little digging it seems that you need to make sure that a driver is installed for actual devices vs emulators. However I can't find any instructions on how to do that with Google Glass. I tried installed the generic Google USB driver however that wouldn't install for the Glass device. I am running all of this on Windows 8.1, though I can't seem to find anything where that would make a difference. I am wondering if anyone else has had this problem or can offer any advise.
First - Disable driver signature enforcement for Windows 8. Google for a buffet of how-to tutorials/instructions, if you don't already know.
Second - Update android_winusb.inf file #
Example: C:\Development\adt-bundle-windows-x86_64-20131030\sdk\extras\google\usb_driver
[Google.NTamd64]
;GoogleGlass
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_4E11&REV_0216
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E11&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_9001&REV_0216
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_9001&MI_01
[Google.NTx86]
;GoogleGlass
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_4E11&REV_0216
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E11&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_9001&REV_0216
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_9001&MI_01
Once inf file is edited, go into your Windows Device Manager, right click on the Glass Device, select Update Driver Software. When prompted, choose "Select From Computer" and enter your android_winusb.inf parent folder location.
NOTE: During Driver Update you may receive an unsigned driver warning; you must proceed with the unsigned driver to succeed.
Open eclipse. If you don't see the Glass device in DDMS perspective right off, run your application/sample as an Android Application and the device should be available as an selectable option during an Android Device Chooser dialog (Provided Glass is running with debug on and plugged into the machine).
matthew06854's solution works well! Thanks. Just one thing, after connecting glass to the computer, one needs to confirm on the glass to allow this connection (trusted computer, or something like it).
It is necessary to check that VID and PID matches what you see in Control Panel/System/Device Manager/Portable Devices/Glass 1/Properties/Details/Hardware Ids. I only got USB\VID_18D1&PID_9001&REV_0216 and USB\VID_18D1&PID_9001, so I changed the file \adt-bundle-windows-x86_64-20131030\sdk\extras\google\usb_driver to reflect this:
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_9001&REV_0216
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_9001&MI_01
Since I had already installed first version og the driver I had to remove driver before I could install with new settings. Now it works for me also :)
Easy way
Download these custmized drivers from
http://www.androidfilehost.com/?fid=22979706399752791
Then go to device manager look for glass-right click-update divers-custom brows location and provide the path of above folder
This link really helped me
http://appliedanalog.com/agw/?p=17
There's a missing step here ,that I figured out.
In my case, my andriod_winusb.inf already had some values under the ;Google Glass line.
That made the Google Glass device appear in the device manager, but as an "Android ADB Interface" instead of an "Android Composite ADB Interface".
Any changes to the andriod_winusb.inf didn't make any difference.
What worked for me was to click on the Andid ADB Interface in the Device Manager. Click uninstall, and (very important) check the check box that says : "Delete the driver software for this device".
Then I modified the andriod_winusb.inf file, and clicked on Glass 1 in the Device manager, and updated the driver.
I'm guessing that once Windows knows about a driver, it caches it somewhere, so uninstalling it and reinstalling ,without "deleting the driver software" just brings the cached driver back, and completely disregards the changes in the original driver folder.
I have a Brew MP which I want to upload my app to. But I understand, it must first be "developer activated" before it will accept my apps. In the Qualcomm tools, I use the Target Manager, but I find no way to activate the phone.
I have a Brewmp.com account, and I read the instructions, but they are not clear to me.
The Target Manager says "Connected Status: Currently not connected", if that means anything. The phone is connected enough for the tool to display it in the list of the physical devices though.
The handset is a Dopod F3188 running Brew MP 1.0.2.481.
I installed the generic gateway USB driver found in the Brew Tools. However, if I enable a developer mode which is more than USB gateway (+ COM) in the phone, the phone is not recognized by Windows and I can not find any drivers for the phone.
The problem disappeared once I started using a real Windows XP machine instead of a virtual machine. (VirtualBox in this case.)