I'm looking for an chromeOS API to get all the network interfaces, I saw this one but I'm not able to invoke it because it doesn't exists for me.
Is there any other way to get the android arc_x network interface from chromeOS?
Thanks
Related
I am using the webusb API in Google Chrome to try to connect a device to the browser. It worked with webserial API, but I am having trouble getting it to work with webusb API.
I am using HTTPS (Github pages)
I enabled #new-usb-backend for my browser
I can open the device and select configuration, but device.claimInterface(0) is not working (and I can confirm that 0 is an interface number).
None of the two interfaces this device has seems to be claimed
The error I get looking at chrome://device-log is
Failed to claim interface: Access denied (insufficient permissions)
I'm not sure where to go from here. I would appreciate some help.
Thank you.
device.claimInterface(1) worked. I heard somewhere mac automatically claims interfaces. Perhaps the first interface was claimed, although the api indicated otherwise. Anyhow, something about the second interface worked that didn't work in the first.
That error message indicates that there is either an existing driver that has claimed the interface or (Windows only) the WinUSB driver hasn't attached to the interface in order to enable applications like your browser to claim it. On Windows you can use the Zadig tool to force Windows to change the drivers being used for a USB device.
If the device can be opened using the Web Serial API then that indicates that the operating system has already loaded a serial driver for the device and so it has claimed at least some of the device's interfaces.
Why, if the Web Serial API works to connect to your device, are you trying to connect to it with the WebUSB API instead? Are you now on a different operating system which doesn't provide a USB serial driver compatible with the device?
I'm trying to determine if I can access any browser api for chrome OS that will allow me to identify the device that its running on when the application has been force-installed in kiosk mode as a PWA.
We're running into exactly the same issue right now. The correct path seems to be to create a PWA and to connect it to a (pre-installed) extension that has access to the enterprise.deviceAttributes:
See https://developers.chrome.com/apps/migration:
"If there is a capability that your Chrome App has that the regular web platform can't provide, it might be available as an extension API. In this case, you use a progressive web app together with an externally connectable extension your web app can send messages to."
enterprise.deviceAttributes are only accessible if the calling App/Site is pre-installed to the device and not loaded dynamically, so it cannot run in the PWA by design.
But with this tutorial, it seems possible:
https://developer.chrome.com/extensions/messaging#external-webpage
We're looking into that right now and will post our progess here.
I sort of make shift followed this guide on how to setup remote debugging. Since I am using Adobe Animate to compile my app I assume it has done the majority of the build steps already as I get a similar screen described.
I don't understand though. Here I have port forwarding up on my router so that it goes to my PC. I have TCP port 7935 up and open. Windows firewall on or off doesn't seem to make difference. Windows firewall even prompted me to allow or deny fdb after I ran it. I can't get my phone to connect via remote debugging. I want to be able to send this to my client who is having issue with the app so I can see what's going on under the hood instead of relying on a giant sum of try/catch statements and screenshots. Any help?
I tried a dummy domain and it seems to know that it can't connect to it. When I try mine or my IPv4 it doesn't let me connect. It just freezes up the app.
I don't know whether it works or not in Animate CC, but it works via Flash Builder. I'm using Android real device and I have Android SDK tools installed on my PC
Yes, I have followed that tuts from official Adobe docs, but that doesn't work
First: Simply connect your device to your PC
Actually , you can debug your app remotely as long as your device has been connected with your PC. This step, doesn't necessarily requires FDB.
In my case , all I need was things like
adb connect 192.168.xx.xx:port
this will connect your Android device with your PC on your default network .
Second, set debug setting over network
You've done it in Animate CC, with addition you might want to check "install application on the connected device'
Third, just debug as usual
You can get all those debugging stuff including traces
Is it possible to use PeerFinder for initiating connection between applications in different PCs inside intranet?
I tried ProximityCS (Windows 8.1) sample and PeerFinder.SupportedDiscoveryTypes returns None for me. (Tested with Windows 8.1 Preview)
I have only found samples to connect using NFC or WifiDirect.
Is there any samples of using Infrastructure (TCP/IP) way of connecting?
Is it possible do this manually using Broadcast messages from Windows Store app?
Windows store apps support multicast; from this you can build your discoverability solution. There's a short video how-to about this on the Channel 9 site at http://channel9.msdn.com/posts/Multicast-LAN-Discovery
To send a multicast message in Windows Runtime, just send it to a multicast address. To receive, you just call JoinMulticastGroup and you can start to receive. To increase your code robustness, re-join when you learn about new networks; this will join the multicast group on newly available adapters.
Peerfinder is part of the Windows.Networking.Proxmity namespace which, as you have mentioned, supports only NFC and WifiDirect for communication and data transfer between two applications in different PCs.
Have you tried using StreamSocket so as to emulate a client-server like communication between two applications?
I am trying to create a windows phone 8 application but the emulator does not show me the map. all I get is this.
as you can see no land mass is show and no roads are shown. I have panned around and come across nothing and the emulator location is set to an area where land should show.
If I run it on my device it works fine and the map loads.
Could this be due to a port blocking issue or something silly like that.
Cheers
Mark
The approved answer might not be 100% correct. Check out the following blog post, and you will notice, that your emulator probably doesn't have an access to the internet.
http://michalstawarz.pl/2013/01/26/windows-phone-8-emulator-maps-display/
Windows Phone emulator supports Bing Map for sure.
It seems the Problem may be due to
Network Connectivity Issues with Host PC
Proxy Issues
Other Issues
Workaround for the above Issues.
If you see blank blue map screen as in http://michalstawarz.pl/2013/01/26/windows-phone-8-emulator-maps-display/ as Michael referred.
Then its good to go. Problem is Internet connectivity / proxy not configured.
If its is Network Connectivity, then troubleshoot your system network adapter. Problem may be due to limited network connectivity / PC not connected to internet.
If it is proxy then,
Get IP Address of "Internal Ethernet Port Windows Phone Emulator
Internal Switch" using IPCONFIG in CMD prompt
Then Enter it under Exception List in IE's LAN Settings >> Advanced >> Exception
Other Issues may be due to Not Configured / improper IP configuration when adapter's IP setting changed manually.
If it is the case -- then Remove all virtual adapters using Virtual Switch Manager Menu in Hyper-V Manager and RUN Emulator with ADMIN Privileges.
Maps are not supported on the Windows Phone 8 emulator.
Maps are now supported, and the original question is no longer valid.
If the answers from Micheal and Prakash doesn't solve your problem.Then try this-
Open regedit in the C:\Windows folder.
In Registry Editor open
for 64 bit Windows-
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\InternetExplorer\MAIN
\FeatureControl\FEATURE_BROWSER_EMULATION and then create XDETools.exe with hex value 2328.
for 64 bit Windows-
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\InternetExplorer\MAIN
\FeatureControl\FEATURE_BROWSER_EMULATION and then create XDETools.exe with hex value 2328.
Source-http://igrali.com/2012/07/30/windows-phone-location-tool-in-emulator-down-no-problem/