To be clear, if you're having this same issue the problem is probably an out-of-date SDK. As of 4.2.2 there is a security feature that requires you to confirm the RSA fingerprint of the connecting device. Open the SDK manager and update the tools! Then reboot.
The thing that fixed it for me was to upgrade the SDK platform-tools to r16.0.1. For me, this version was not displayed in my SDK Manager, so I pulled it down from -tools_r16.0.1-windows.zip directly.
I hit the same issue on a Nexus 7 running 4.2.2 OTA update. I'm almost certain I had an ADB connection over USB and Wi-Fi after the update until it just stopped working. To fix, I updated my SDK using:
For anyone wondering about 4.2.2, there is a security question that appears on the phone requesting RSA verification with the PC. Be sure your tools are updated AND you allow the PC access by verifying the security question on the devices in question. This fixed it for me.
If your device normally connects over USB, but suddenly stops working, especially after the USB cable has been disconnected and reconnected, try the following non-invasive steps before doing some of the more drastic things mentioned in the other answers:
If your device is listed with 'offline' next to it, try restarting the device. The ADB daemon on the device will occasionally get hung. I've noticed this more when I've disconnected the cable while LogCat is running and after switching back from connecting via Wi-Fi or Ethernet.
Another problem I was having was that I was trying to connect ADB over Wi-Fi, which is my only option because the USB ports on my Mac are really finnicky. Unfortunately, ADB over Wi-Fi doesn't show the security question in 4.2.2, so you need to find a USB cable that'll work and connect over USB at least once to accept the security question, but after you do that once, you can connect over Wi-Fi.
Then in the developer options, get into the "Wireless ADB" feature, if you're not already there yet. Go to "Pair using PIN" or similar. There, a IP and port will pop up in a dialog, together with a pin. Connect to the phone using:
To verify that it worked, run 'adb version' before and after the commands and make sure it is the latest. The reason for the adb kill-server command is that it it most likely running, and it can't be updated while it is running, so you have to kill it first.
Finally I ended up with just doing the ADB stuff over the LAN. The setting was right next to the USB Debug setting and in ADB it can be activated with "adb connect [IPADDRESS]:[PORT]". The port was 5555 on my phone.
One more possibility for people with flaky ADB connections, and if they're on a Mac and have Android File Transfer installed: I found that file transfer was interfering with my ADB connection, causing it to stop working intermittently.
I have a dodgy USB connection so I tried to get wifi connectivity going. Tried basically everything here, but one thing I did not try until last, and suddenly it worked! So, if you end up stuck, try these steps:
Sweet! I don't know exactly if forcing it to restart USB mode then TCP/IP in sequence helped, or just the last three commands, but clearly it started working. I also found there's a Developer Option to Enable Debugging on Wifi, and you select your hotspot. That may also prevent it working, so check that as well.
If you've previously authorized the RSA fingerprint of your PC and tried adb kill-server etc. with no luck, your problem might just be that you're trying to connect to it while it's locked. Try pressing the screen-on button and entering your pattern - this fixed it for me.
The reason for a device to be reported as offline is that adb can not connect to it. Adb executable from the development environment creates a connection (socket) with the device under control. The device has a service (daemon) that listens for this communication. The daemon is called adbd (as in adbdaemon).When one enables adb on a device in fact one starts this daemon, so comms can be established with the device.
When the device is reported by adb as offline is because the daemon is not running anymore or is in a state that will not accept connections. Most often than not this happens if the network goes down on an active (network) connection.
I am trying to connect my Galaxy S5 to my computer running Ubuntu 14.04 so I can do some android development. I have recently downloaded and installed Android Studio and the SDK and my device is detected when it's connected via USB but the device either appears as 'unauthorized' or 'offline'. I know I should be expecting the RSA key prompt but this never appears.
ADB saves a key file in one of multiple places on a Windows computer, the first is in the location where adb.exe is (C:\android), the second is in the user's >profile (C:\Users*username*.android), the third place is in the Windows system files (C:\Windows\System32\config\systemprofile.android), the file is >simply named "adbkey" with no extension. If there is no key file when ADB runs, it will generate one automatically.
Mine was located in my user folder (C:\Users*username*.android). All I had to do was delete the adbkey file (there was also a file named "adbkey.pub" which >I deleted as well), restart the adb server in command prompt (adb start-server) and plug my phone in. I instantly received the RSA Fingerprint Key window on my >G3 allowing connection between the two devices. Then typing "adb devices" returned my phone's serial number followed by "device" showing it was available. >I went back to the C:\Users*username*.android\ folder and sure enought there were new "adbkey" and "adbkey.pub" files.
in my case, on my Windows 7 i have one more adb on "C:\Windows\adb.exe" and its an old version, so my adb command always run from that file. I fixed the problem by running adb form my sdk directory "SDK_DIR/platform-tools/adb.exe"
In my case (same problem - that Nexus 5 is connected but with "offline" status) the problem was solved by "Invalidate caches and Restart" in Android Studio.Suppose that problem was in adb and restarting Android Studio causes to adb restart.
When a phone is powered off, the network and GPS radios are deactivated, making it difficult to track the device's real-time location. However, specialized Pixel hardware enables Pixel 8 and 8 Pro users to locate their devices via Find My Device, even when they're powered off or the battery has died. Other devices doesn't support this for now.
Besides, Find My (for iOS), Find My Mobile (for Samsung), network providers can help you find the last location before the phone is switched off. GPS tracking apps such as AirDroid Family Locator, allows you to check whether the pairing phone has a low-power. You can remind them to charge their phone before it switches off due to low power.
"Find My Mobile" is a service designed for Samsung device users that allows them to locate, lock, or erase their devices remotely in case they are lost or stolen. There are two requirements to use this way:
Find My is available for Apple devices (iPad, iPod, Mac, iPhone) users. When they connect their devices with their Apple ID and turn on Location service and "Find My iPhone" they can find the iPhone's last location.
The Google Timeline is an overview of all location data collected from the device. This data can be used to find a lost phone that is turned off. The Google Maps timeline only works if location history and reporting are enabled. Otherwise, you can use the Find My services.
AirDroid Family Locator is an app that aids in keeping kids safe. If you have installed the app and paired it with the lost phone, you can track its real-time location and will get alerts if the phone is low-power. So you can take action before it's powered off.
Network providers can access the IMEI and can only triangulate a phone's most recent location. But they may require legal authorization or a court order to share this information for tracking purposes. In this case, the only option for the end user is to contact the relevant wireless carrier service provider. Speak with their representative, discuss the issue and see if they can help.
Setting up parental controls lets you have peace of mind over your child's online content, interactions, and communication. It also helps build healthy online habits that will set them up with the online skills and mindfulness they and you need.
I know this question has been asked a million times (I've googled it), but I still can't find where my offline files are stored on my phone. I've looked in SD card>Android>data>com.dropbox.android>files, but it's empty. However, in the Dropbox app, I've marked a file as "Available offline", it shows the little green icon on the right indicating that it's been downloaded, and I can open it. So where is it?
The reason I ask is that I want to be able to play MP3 files in a music player (either Google Play Music or VLC), I don't want to have to open each MP3 individually in Dropbox to play it. But I have to tell VLC where the folder is that contains the MP3 files. Seems very simple, but I haven't been able to figure it out. Am I the only one having this problem? It doesn't seem like such a strange thing to request.
Could you try exporting the MP3 file from the Offline Files or Home view now and let me know if this persists? You should be able to see "export" option for MP3 files as well after pressing the ellipsis button (...) so if this is still not happening please send me a screenshot so I can have a visual of this as well.
Did this post help you? If so, give it a Like below to let us know.
Need help with something else? Ask me a question!
Find Tips & Tricks Discover more ways to use Dropbox here!
Interested in Community Groups? Click here to join