Is there any way to build a pure JS/HTML5 Chromecast Sender implementation that runs in Chrome or Firefox on Android.
The Chromecast Chrome extension doesn't run on Android Chrome, so the only solution I can think of is to launch the Receiver via the desktop Chrome extension, then use WebRTC and webkitRTCPeerConnection to send messages between the Chromecast Receiver and a different Android Sender.
Both Android Chrome & Firefox support the data channels so at least once launched that might be a viable way to control the receiver. I wonder if anyone has any better ideas, or a way to get the Chromecast Chrome extension onto Android?
(Btw. I am aware that DIAL SDP uses UDP != WebRTC RTCDataChannels)
No, currently there is no such solution on an Android device in pure JS/HTML5 in Android Chrome (nor Firefox for that matter).
Related
I know you can work with beacons with a iOS app or Android app.
But you can work with a web app to?
(A website recognize a beacon and do something)
Unfortunately, the general answer is no. You need native components to detect Bluetooth beacons on both Android and iOS. The web browsers on both operating systems have no hooks to detect beacons via JavaScript or HTML.
Chrome OS does have Bluetooth bindings in its Chrome browser, which may allow you to build a web app on Chrome OS that does this. But this would really be a Chrome App not a general purpose web app.
The Chrome browser for iOS and Android also detects Eddystone-URL beacons, but it will not pass the detection info to a web app. Detections are sent to the user as a notification and tapping on that notification simply brings up a configured URL in the Chrome web browser. This does not allow any dynamic web app behavior based on beacon detections.
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 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.
When a PC connects to an Android device via USB, the device's information can be found on chrome://inspect. How can I get this information in a Chrome extension？
That information isn't available in the Chrome Apps/Extensions API. You should file a feature request at crbug.com explaining your use case.
If you write a Chrome App, you'll have access to the chrome.usb API, where you can connect to specific devices. See Spark's ADB functionality for an example: https://github.com/dart-lang/spark.
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