• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

The device is not recognized

  • Thread starter Thread starter hexabin05
  • Start date Start date
H

hexabin05

Guest
Hi, I've been trying to run an app for like a week, I can't figure out what's wrong. I enabled developer mode on the smartphone and USB debugging too. I just want to run a hello world. I tried the "troubleshoot device connections" and "restart ADB server", it says "unable to locate ADB" every time. I tried with 2 smartphones !

And Android Studio doesn't want to download the emulator from SDK Manager, it says "Installation did not complete successfully. See the IDE log for details.". I can't even find this log file ! The AVD cannot be started without the emulator.

What should I do to solve either ADB or AVD issue ? I've tried everything.
 
If using Win10, Go into uefi and disable the driver signature verification check before installing said driver, or it will never actually install..
 
Thanks for your answer. I'm on Windows 8.1, I tried "adb devices" on the command line but it said something like "list of attached devices:" and nothing more.
I can access to personal files on the smartphone, does it mean the driver is good ? Anyway I can't find any driver for wiko, there are only crappy pages that lead to ads.
Other than that, when I try to download something from android.bat, it says "permission denied", maybe it's from windows defender but I don't know how to fix that safely...

I think I will reinstall android studio or install it on another PC, there is definitely something messed up, absolutely nothing works.
 
hexabin05 said:
I can access to personal files on the smartphone, does it mean the driver is good ? Anyway I can't find any driver for wiko, there are only crappy pages that lead to ads.
Click to expand...

There's typically a different driver which should be used for fastboot/adb mode versus file transfer mode. Check in Device Management to see if you see anything like "Android ADB Device" showing up.

As for finding the right driver, that's unfortunately often the case with lesser-known phone brands, and it can make development work a bit of a challenge. You might try the so-called Universal ADB Driver which attempts to handle most cases:
https://adb.clockworkmod.com/
 
Thanks codesplice, I installed the universal ADB Driver and the phone is recognized now ! It was unauthorized then but I did "adb kill-server" and "adb start-server" on command line, it still didn't work but then I just unplugged the phone and plugged it again, and it was recognized by android studio.

The only problem is that the application doesn't run, I don't know why, the build is okay, the device is set to authorized when I check it on the command line with "adb devices". Everything is fine but nothing happens on the phone.

Edit:forget it ! I just didn't notice that the app was actually launched on the phone, I didn't pay attention because there is no notification or anything when it runs. It works fine now.
Thanks to everyone !
 
Last edited:
You must log in or register to reply here.
Back
Top Bottom