#ANDROID HTML INSPECTOR HOW TO#
#ANDROID HTML INSPECTOR INSTALL#
#ANDROID HTML INSPECTOR FOR ANDROID#
#ANDROID HTML INSPECTOR DOWNLOAD#

If you still have a problem upon retrying the Terminal command, you might have kill the process directly. There is a very small chance that, if it didn’t work, the bridge isn’t running, but its process still is.

Go back to the Terminal, check it, and try again. If you instead get a message saying that the server sent no data, or similar, you might have typed in the Terminal command incorrectly. You’ll see a list of inspectable tabs (note that if you open a new tab on the device, you’ll need to refresh the Inspectable Tabs page): To begin debugging, go to localhost:9222 in your desktop browser. Your device and desktop browser should now be connected and able to send information to each other across the debugging bridge. You’ll then need to restart the Terminal, or open a new tab. To start the debugging bridge, Type in the following terminal command:Įxport PATH=/Users/your-username/path-to-adk-folder/adt/sdk/platform-tools/:$PATH

#ANDROID HTML INSPECTOR FOR ANDROID#

Inside there you should see an executable called adb, which is an acronym for Android Debugging Bridge. Once there, navigate to sdk > platform-tools. In your computer’s terminal, navigate to the directory into which you extracted the Android SDK. Start Opera for Android, and enable debugging by entering opera:debug in your address bar and checking the “enable” checkbox in the resulting page, as seen below. You should see a message on the phone along the lines of “USB debugging connected” to indicate that things are proceeding successfully. If it was already connected, try disconnecting and reconnecting it, just to make sure the computer recognises the phone properly. When doing mobile debugging on Android it is also useful to check the “stay awake” option that you’ll find in the same place as the “USB debugging” option, so the device stays on while plugged into USB, but this isn’t mandatory.īefore moving on, connect your phone to your computer via the USB cable. This is a security mechanism accept the dialog. On Android 4.2.2 and higher, you’ll see a dialog asking whether to accept an RSA key. Returning to the previous screen shows previously-hidden developer options. On Android 4.2 and newer, go to Settings > About phone and tap Build number seven times to get a message that says “congratulations! you are now a developer”.On Android 4.0 and newer, it’s in Settings > Developer options.On Android 2.3, the option is under Settings > Applications > Development.Check the “USB debugging” checkbox in Developer Options. Next, you need to enable USB debugging on your device. Note that you can’t remotely debug Opera Mini from desktop, as the rendering is done on our Mini servers and only displayed on the device. Preparing your deviceĮnsure that you have a USB cable available to connect your Android device to your computer (the USB power cable should be fine) and Opera for Android installed on it (see the Opera for Android user guide for installation help, if needed.) Keep the phone disconnected from your computer just for now. Use Opera 15+, Google Chrome, Chromium, or the Yandex browser. You’ll need a Chromium-based desktop browser.

#ANDROID HTML INSPECTOR INSTALL#

Windows users may need to install Device drivers. If you choose something else, use that in the example steps below.

#ANDROID HTML INSPECTOR DOWNLOAD#

The first thing you’ll need is the Android SDK - download it and then put the kettle on it’s a 400MB file.Įxtract the files to a memorable location, such as /Users/ your-user-name/adt or c:android/adt. You’ll be remotely debugging your phone from your desktop, so let’s get the desktop ready.

#ANDROID HTML INSPECTOR HOW TO#

Here’s how to connect Opera for Android to Chromium-based desktop browsers for remote debugging. Now that Opera for Android is out, you’ll sometimes need to debug it, as there are differences in Standards support between Opera and Chrome for Android and Chrome on Android 4+ (, etc,). This article is outdated, please refer to: Introduction

Android html inspector