Android ADB device offline - unable to connect to: by: Erik. Email This BlogThis! Share to Twitter Share to Facebook Share to Pinterest. Label: Android Debug Bridge (adb), Android Developer Tips, Android Developer Tools. No comments: Post a Comment. More Google Charts examples on Android WebView; Display Google Charts.
I am trying to utilize chrome for remote debugging of an android web application. I am unable to get any open tabs from the device to show under chrome://inspect list for remote debugging.I have done the following:. Made sure my device driver is installed appropriately. Turned on developer mode and usb debugging on my device via the developer menu. Checked and made sure that my device is listed in adb list via issuing 'adb devices' from the command line.My device is displayed under the device list via (chrome://inspect) just cant seem to get any open tabs listed any help would be much appreciated.
ThanksDevice:Samsung Galaxy Tablet 10.1Android 4.2.2.
EDIT by admin December 2014: The following from is very helpful for developers in China: 致中国同胞:如果你按照要求操作最后却得到一个空窗口,翻墙后再试试。不用谢。. Remote debugging with Chrome downloads files from. Test your connection: Try to open. If it doesn't work, thats why you're getting an empty window. In this case maybe you need a VPN.This is really a problem for people in China because the appspot.com domain is blocked. So sad.(original issue follows)When clicking 'inspect' next to the url of the page open on the Nexus 7 an empty window shows up and nothing happens.ADBPlugin (0.9.6) in Chrome (Version 28.0.1500.89 beta) running on Fedora 18. This seems to have nothing to do with being in China (or any specific network for that matter).
I'm in the US - this is just a bizarre bug with Chrome that sometimes (and it's hard to reliably reproduce) results in a second, empty inspector window opening when you open inspector.To quote my earlier message which has more detail:I have this issue. If I open inspector, a blank inspector opens with the following in the titlebar: chrome-devtools://devtools/bundled/inspector.html?isSharedWorker=true&remoteBase=Sierra 10.12.3, Chrome 57.0.2987.98 (64-bit)The last time this was happening to me, I tried disabling all extensions and it did not resolve the issue.