googlearchive/adbplugin

Google Chrome Extension with ADB Daemon

adbplugin's Issues

Change popup font from serif to sans-serif

I know this is a totally unglamorous issue from a technical perspective, but the default serif font in the popup looks completely out of place to me. For better or worse it's the first thing I noticed.

I propose we change the font to the system default sans-serif at least to more closely resemble a menu in both the Windows and Mac GUIs.

Extension updated and moved - testing welcome!

Hi all

Just a note to anyone watching this repo.. It has now moved to https://github.com/GoogleChrome/ADBPlugin

It also now works on Win, Mac and Linux (ia32/x8_64)! See install instructions for details.

Please note that it does not auto-update. I'm going to work on adding it to the Chrome Web Store for easier installation and updating.

Enjoy

The webpage to be inspected was not shown in Developer Tools

"chome_stable+ADBcmd" for remote debugging works fine.
I have tried "chrome_beta+ADBPlugin" both on windows7 and ubuntu. After clicking the inspect link, the window of Developer Tools will be popped out, but the content of "Elements" will always be like following content no matter what page is shown on my Android device.
//
//
//<_html>
//<_head></_head>"
// <_body>
// <_object type="application/x-adbplugin" id="adb-plugin">
// <_script type="text/javascript" src="background.js"></script>
// </_body>
//</_html>

Did I use it in a wrong way?

New Chrome Extension Policy will Kill ADB Pluggin for Win8

As you may know. (Or not).. Google has made the decision to change the policy on installing Extensions in Chrome so you have to have an app in the webstore and install from there..
I don't want to go into why.
But just want to flag up the side effect of this is on Win8 where the Extension HAS to be loaded outside of the webstore. (Which obviously you do know since its on the main page).

Can someone who works at Google go over to the peeps who are doing this change and give them a quick Prod.. Remind them that this will effect their OWN extensions in a bad way.

Linux version

Here is a linux version: https://github.com/Sfate/ADBPlugin-linux-x32 if someone need it =)

Can't install extension on Chrome 30/Win 8

Hi,

I can't even click on the download Icon. It says something like: "This application is not supported on this computer. The installation was deactivated."

Why should my PC not be supported.

Running
Chrome 30
Win 8 64-Bit

Edit Sorry my bad just saw the the solution on the main page.
Would be great to add this in the app discripton.

Clicking "view devices" takes me to chrome://inspect/

Hello, after your presentation at i/o last week I wanted to try this out. I've tested in latest Chrome and Canary both and after I click the icon to start ADB then click again to view devices I don't actually get devices, instead it takes me to chrome://inspect/ and from there I'm not sure how to proceed.

I'd love to use this and am happy to help troubleshoot if I can. I'm on Mac OS 10.7 and adb and ddms both work as I'd expect them to when you used from the command line.

Can I downgrade?

The native Chrome debugger doesn't detect any of my devices. The ADB plugin used to worked just fine. I've spent my morning reinstalling USB drivers for my S4, Google Nexus and Nexus 7, rebooting everything and I just get "No devices detected."

I've tried it with 33.0.1750.117 m and 35.0.1858.0 canary on the desktop and 32.0.1700.99 on my devices. I'd rather not use the legacy way and install the sdk. I'd really just like to enable the ADB plugin and go about my work.

Not supported on this computer. Windows 8

Hi,

When going to the Chrome store, I see the message: "This application is not supported on this computer. Installation has been disabled." And indeed, installation is not possible.

I'm running Chrome Canary 30.0.1552.0 on a Windows 8.1 machine.

Any ideas?

Thanks!

Debian 7 x86_64 / Chrome 29.0.1547.41 beta / ADBPlugin 0.9.7 - Not working

Per the instructions I have installed the plugin using Chrome beta from the official Linux repos.

Per the readme, I have enabled multiarch (sudo dpkg --add-architecture i386) and installed ia32-libs and libncurses5:i386. I can run adb from /Chrome/chromepackage/linux just fine, it sees my device.

I can manually start up adb from the command line and navigate to chrome://inspect to fire up inspection. However the plugin will simply not work.

Please let me know how I can help debug this issue, I know you're a busy guy (I've seen several of your presentations).

Not working on Windows 7

After installation from webstore and plugin the device, Chrome crashes.
I restartet the browser and installed ADB again (it was removed from extensions).
Reinstallation went well, but then I recognized a hight CPU usage (about 50%). ADB was also not working, just the active state of the icon was shown.
Deactivation the plugin in extension manager was not possible without killing the process via taskmanager before.

OS: Windows 7
Device: Nexus 4
Browser: Chrome canary version 30.0.1553.3

to exec "xcodebuild ARCHS=i386 ONLY_ACTIVE_ARCH=NO -configuration Release -project build/FireBreath.xcodeproj" Error on the imac

=== BUILD NATIVE TARGET ADBPlugin OF PROJECT FireBreath WITH CONFIGURATION Release ===
Check dependencies

PhaseScriptExecution "CMake PostBuild Rules" build/projects/ADBPlugin/FireBreath.build/Release/ADBPlugin.build/Script-D133E8809F0F4511A3DB9C19.sh
cd /Users/ethan/Downloads/firebreath
/bin/sh -c /Users/ethan/Downloads/firebreath/build/projects/ADBPlugin/FireBreath.build/Release/ADBPlugin.build/Script-D133E8809F0F4511A3DB9C19.sh
/bin/cp -r /Users/ethan/Downloads/firebreath/projects/ADBPlugin/Chrome/chromepackage/* /Users/ethan/Downloads/firebreath/build/projects/ADBPlugin/gen/npADBPlugin-crx
/bin/cp -r /Users/ethan/Downloads/firebreath/build/projects/ADBPlugin/Release/npADBPlugin.plugin /Users/ethan/Downloads/firebreath/build/projects/ADBPlugin/gen/npADBPlugin-crx
/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --pack-extension="/Users/ethan/Downloads/firebreath/build/projects/ADBPlugin/gen/npADBPlugin-crx" --pack-extension-key="/Users/ethan/Downloads/firebreath/projects/ADBPlugin/sign/dummy_key.pem" --no-message-box
无法加载插件的路径“/Users/ethan/Downloads/firebreath/build/projects/ADBPlugin/gen/npADBPlugin-crx/npADBPlugin.dll”。
make: *** [ADBPlugin_buildpart_1] Error 21
Command /bin/sh failed with exit code 2

** BUILD FAILED **

The following build commands failed:
PhaseScriptExecution "CMake PostBuild Rules" build/projects/ADBPlugin/FireBreath.build/Release/ADBPlugin.build/Script-D133E8809F0F4511A3DB9C19.sh
(1 failure)

View Devices opens inspect tab

The adb plugin starts up just fine and even showed a little "1" when I started an emulator.

But the "View Devices" entry just opens the "inspect" tab. Shouldn't there be a list of attached devices or sth?

OS: Windows 7
Chrome: stable, 27

Plugin crashes Chrome version 30

Installed the plugin last week on an earlier version of chrome and it worked fine. However after chrome updated this week the plugin now crashes chrome when used, including when you try to disable it or remove it.

Chrome Version 30.0.1599.69 m
Windows 7 Professional, Service Pack 1

Black page

But I've version 32 of Chrome in both in my mobile and computer as well. But still i'm facing this problem.

Issues remote debugging with Chrome on Windows 7

Filed upstream here: https://code.google.com/p/chromium/issues/detail?id=361856

Inspect opens an empty window

EDIT by admin December 2014: The following information from @gockxml is very helpful for developers in China:

致**同胞：如果你按照要求操作最后却得到一个空窗口，翻墙后再试试。不用谢。

1. Remote debugging with Chrome downloads files from https://chrome-devtools-frontend.appspot.com.
2. Test your connection: Try to open https://chrome-devtools-frontend.appspot.com
3. If it doesn't work, thats why you're getting an empty window.
   1. In this case maybe you need a VPN.

This is really a problem for people in China because the appspot.com domain is blocked by GFW. 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.

ADB Extension does not install!

No matter how many times I re-attempt, re-start, etc, the extension for ADB will not install. It keeps giving me "An error has occurred" pop up. I am on Windows 7 using Chrome 22. Any help appreciated!

Clicking the gray icon does not bring up does not bring up start options

I have ran adb devices and it list my connected device. I can debug in eclipse and debug is enabled in Chrome on the device. When I click on the gray adroid icon nothing happens. The start and stop options do not list as in the instructions. I am running windows 7. with the latest chrome I am sure as it auto updates... Any help getting adb started would be great...

Linux build instructions

Linux build instructions would be much appreciated.
Any hints? I'm guessing I need cmake... 😉

Windows support

• investigate https://github.com/koush/UniversalAdbDriver for an easy way of windows driver support.

Is it possible to make this work with Amazon's Kindle devices?

Just came across Amazon's docs for developing/debugging web apps, and was wondering if anyone knew if it would be possible to use this extension to debug a web app on a Kindle?

Here are the docs.

Extension is blocked if installed using Developer Mode

After installing the extension using the Windows 8 instructions from the README.md file and rebooting my computer, my extension got blocked because "it may be installed without my knowledge". I've tried to install it again, same happens.

can't find devices

can't find devices
on page chrome://inspect/
chrome 28.0.1500.95+macox 10.8
thanks

"Start ADB" does not work, gives ncurses error

If I click on "Start ADB" it gives me the error:

 /home/blarsen/.config/google-chrome-beta/Default/Extensions/dpngiggdglpdnjdoaefidgiigpemgage/0.9.7_0/linux/adb: error while loading shared libraries: libncurses.so.5: cannot open shared object file: No such file or directory

libncurses5-5.9+20130608-1ubuntu1 is installed on my machine.

I have to start adb manually at the command line by typing adb devices. When I do that the icon turns green and everything works fine.

uname -a: Linux ball 3.11.0-12-generic #19-Ubuntu SMP Wed Oct 9 16:20:46 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

Google Chrome 31.0.1650.48 (Official Build 233213) beta

ADB 0.9.7

Crashes in Windows 8.1

Visiting the chrome://inspect page's Device tab crashes the browser

Using Windows 8.1 x64, Chrome 30
Tried on 2 devices HP Touchpad (ICS), Archos Platinum 50 (JB)

The plugin doesn't start. Linux.

I just installed the ADBPlugin (0.9.6) in Chrome (Version 28.0.1500.89 beta) ran on Fedora 18. Nothing happens when I click "Start ADB" in the ADB dropdown menu in chrome. The log shows the following:

/home/samuel/.config/google-chrome/Default/Extensions/dpngiggdglpdnjdoaefidgiigpemgage/0.9.6_0/linux/adb: error while loading shared libraries: libncurses.so.5: cannot open shared object file: No such file or directory

Inspect Page Not Showing Pages from Attached Device

Hi,

I just installed the plugin. Everything worked fine except that inspect window from "View Device" is not listing pages from the attached device although the android icon in the top right corner was showing '1'.

Here is the environment that I am working in:

Development Machine:
-Ubuntu 11.10
-ADB Version 1.0.31
-ADBPlugin 0.9.6
-Chrome Version 27.0.1453.110

Phone:
-HTC One X
-Andriod Chrome Version 28.0.1500.64
-USB Debugging On
-Chrome USB Web debugging enabled

Everything worked fine after following the procedure described under "Remote debugging with Chrome Stable".

Thanks for great tool!

Connect AVD Emulator Instance

Is it possible to connect an avd emulator instance, too?
Or is there any other tool to debug applications in emulator?
Thx.

Why is port forwarding limited to 1024-10000 range?

Port forwarding is a great feature but is limited by a seemingly arbitrary range restriction in Chrome:

function validatePort(input) {
  var match = input.value.match(/^(\d+)$/);
  if (!match)
    return false;
  var port = parseInt(match[1]);
  if (port < 1024 || 10000 < port) // ←←←←←←←←←←
    return false;
  ...
  return true;
}

Is there a reason for that? Can this be changed to allow all ports, or at least, ports above 10000?

Inspect opens and closes instantly.

If I knew how to generate log I would. Not chinese btw.

Devices list is empty, though the Android icon shows otherwise

As title states; my device list is showing up empty, yet the Android icon beside the address bar shows a little number 1 when I connect my device.

System settings:

Mac OSX (10.7.5)
Google Chrome (31.0.1650.48) - Also using official Glow theme.

Nexus 4 (16 gb) Running Android 4.3
Google Chrome for Android (30.0.1599.92)

Both Chrome for Android, and the device itself have USB Debugging Enabled & permission granted

No longer works with my VZ LG Spectrum 2

Hooked up as ethernet with a usb, debugging enabled. Says debugging connected. Inspection targets does not show it. Tried multiple modes. My Nexus 7 works just fine. Help.