Is there any way of inspecting element on a Samsung tablet using the default Internet Application? I have some bugs that need sorting that only appear in the native Samsung / Android 'Internet' application.
Samsung Internet can be debugged remotely using Chrome on the desktop. Any pages you have open in Samsung Internet should be listed for inspection under chrome://inspect:
As Ada shared here, you can also enable port forwarding and connect to a server running on your desktop machine. You will need the Chrome app running on your desktop. If your localhost URL does not resolve, visit chrome://inspect and ensure port forwarding is enabled. You may also need to open the Chrome app on your mobile device.
Update: There is a page in the Dev Hub docs about remote debugging here.
Related
I installed WebStorm on my PC and started NodeJS server. I am able to access it from Chrome and Firefox browsers using localhost but not with my PC's IP address.
I followed instructions given here. I verified whether extension is enabled or not in Chrome as well checked the port no in WebStorm's Build, Execution, Deployment -> Debugger. My PC's firewall has been turned off. Still I am unable to access it using IP address.
Can anyone guide me how to go about this?
I am running WebStorm in my PC and trying to access it from the same machine through above browsers.
Using WebStorm 2016.3.3 version.
Here are my findings when connecting to WebStorm's internal web server via Chrome using the following:
WebStorm 2018.1 Build #WS-181.4203.535
Windows 7 6.1, 64 Bit Pro
Chrome Version 65.0.3325.162 (Official Build) (64-bit)
Chrome connected to localhost:63342 but returned connection refused when attempting to connect to WebStorm at <ip address of machine>:63342, even with Windows Firewall disabled.
I first configured WebStorm to listen at port 63343 instead of 63342 and still had the same result. Unexpectedly, with this setting WebStorm answered at both localhost:63342 and localhost:63343, even after restarting WebStorm.
I then noticed that with either of these ports, WebStorm's Can accept external connections checkbox was grayed out and unchecked. Changing WebStorm's port to 1338 alone still resulted in Connection refused at http://<ip address of machine>:1338. Turning off Windows firewall did not affect this.
Since WebStorm's Can accept external connections checkbox became usable after I changed its port to 1338, I now checked the box. Chrome was now able to reach WebStorm at http://<ip address of machine>:1338.
So it seems that it is not the port itself that makes a difference, but WebStorm's Can accept external connections checkbox. Note that checking this box may be a security risk if you are using a shared network since WebStorm will now serve pages to other stations as well as your own.
Got answer for this in this post I changed the default port no to something else and now i am able to access the page from the browser using ip address.
i want to test my site on feature phone like nokia asha phones , user agent does not give exact behavior . for smartphone i can connect my android device to chrome browser using USB debug mode and can inspect element , how to do this thing for feature phone
You can't. The DevTools remote debugging uses a very specific protocol to talk to the remote device over. If that device doesn't expose the protocol, you can't see into it with DevTools directly.
I am trying to setup remote desktop access to a chrome box. Plan is to be able to access the chrome box from any where by just entering a pin and I don't want user using the chrome box to generate a key for me and send it over to me.
I thought chrome remote desktop app would help me achieve this, but Enable remote connections option is not available on chrome Remote desktop app on Chrome OS. This option is available if the app is installed on windows and I was able to remote in. Is there any option to achieve the same in Chrome OS?
Star this issue: https://code.google.com/p/chromium/issues/detail?id=471639 to show your support for adding this feature.
I want to debug a custom Chromecast receiver application on a Nexus Player. I've added the serial number / CSSN to my application whitelist. When I do the same for the Chromecast dongle, I'm able to attach the chrome debugger through ipaddress:9222. However, when trying the same using the IP:9222 port of the Nexus Player, I am unable to connect.
You need to use chrome://inspect. Quoting the documentation:
On your development machine, open a Chrome browser window and navigate to chrome://inspect .
Note: This is different than debugging for a Chromecast device, where
you navigate to your receiver's IP address on port 9222.
Click the inspect link to bring the receiver into the debugger.
I'd like to examine the possibility of writing an unofficial Windows 8 (WinRT/Metro) sender API for Chromecast. The goal would be to allow Windows 8 Store apps roughly the same functionality of iOS / Android apps through the official sender API available for those platforms.
I've noticed that, although the inner workings of the API haven't really been exposed yet, some of the source code for the Chromecast device is available, and there's an unofficial emulator for the device out on Github (https://github.com/dz0ny/leapcast).
Is this possible, given how Chromecast devices seem to take commands directly from Google?
ChromeCast is using a proprietary protocol called RAMP (Remote Application Media Protocol) to do media control. Once you have setup your ChromeCast device for development, the device will open a port for remote Chrome debugging. Open Chrome at your ChromeCast device IP address port 9222: http://192.168.0.x:9222/
You should see a page with a link to the receiver page of the currently running ChromeCast app. Click the link and then use Chrome developer tools on that page. Take a look at the network and console tabs to see the RAMP commands.
I have open sourced an Android app that shows you how to discover ChromeCast devices and setup the Websocket connection to handle the RAMP commands: https://github.com/entertailion/DIAL