I did everything verbatim on this sample (How do I discover a Chromecast device using Android?).
The chromecast icon turns to white on indicating there are devices available.
When I pressed it, the application unfortunately stops.
What can be going wrong? The only step so far I want to achieve is list all available devices.
Cheers!
Related
I am looking for a simple app (preferably for iPhone, but if not then for Android), which pops up a message when it receives a signal from a beacon.
The beacon is a Sensoro 4AA, we only purchased it for demonstration purposes.
The idea is: once we turn the smartphone's bluetooth on, the beacon is detected and the message just pops up.
Is there such an app (as simple as can be), where I can just insert the beacon's details (uuid, addtess, or whatever is needed) and maybe some text or link, in order to achieve that?
Thanks
You can use Beacon Simulator for Creating, broadcasting and Scanning Beacons as per your needs and testing.
For Android: https://play.google.com/store/apps/details?id=net.alea.beaconsimulator
For iOS: https://itunes.apple.com/us/app/noteacons-beacon-simulator/id1136196655?mt=8 or https://itunes.apple.com/us/app/dropbeacon-a-beacon-simulator-for-development-purposes/id866760594?mt=8
I hope this helps!!!
I got new Bluetooth speakers and inherently they seem to have a delay of about 0.5 to 1s when watching streams or videos online. I already mailed to the manufacturer and I was told that this has to do with how they make use of the Bluetooth protocol (pair of speakers in master-slave mode for stero sound) and how the respective video player is doing encoding/decoding. iTunes for instance seems to be just fine while vlc and all streams in browsers have this delay.
So I was wondering whether there is a way to manually delay audio either just in the browser (chrome) or even system-wide on MacOSX?! It would be great if the possible solution was transient since I do not want the delay when I am not using these speakers.
Additionally it would be just perfect if somebody even knew how to this on iOS although I don't think that it is possible there, that's why I did not include iOS in the title.
I have a status page (a la Google Analytics) that I want to stream to my screen via ChromeCast. The problem I'm running into is that after 10 or 15 minutes, my ChromeCast cuts off the connection and goes back to the ChromeCast screen rather than continue casting from my status board. I already tried having the page refresh automatically, but apparently that's not good enough.
Ideally I just want to do this via a Chrome tab without having to create an entire application, but I'm willing to do so if necessary. I don't see anything in the docs to suggest that this is possible, though.
Ideas?
Is the screen you are casting a static one in which no UI change happens or there are elements that change on the UI?
I'm not sure what the cause is; but I think casting a tab here might be overkill, and not using it might fix your issue.
Casting a tab basically encodes what's visible into a video stream and streams it over your network to the Chromecast. This uses significant resources encoding the video on your PC, network transfer of a video stream, decoding on the Chromecast.
If the app is already web-based, it would be much better to get the Chromecast to just render it natively (this avoids encoding anything to a video stream, and removes the need for your PC to be on completely).
I'm still waiting for my Chromecast to be whitelisted so I can't test it; but I suspect it would be trivial to be able to get the Chromecast to display a "status page" natively with just a little HTML and JS on your PC to "launch" it, and a tiny wrapper for the receiver.
I got the email back from Google and they said they have, but having trouble getting it to show up under devices using some of the example code they provide, but now wondering if maybe I gave them the wrong serial or something and it really hasn't been white-listed.
You can always email them with the developer ID (Should be in the email), app ID, and your serial # to have them check. One thing I learned, though (when experiencing the same thing), was that I forgot to configure my chromecast with the "send this serial # to Google when communicating about updates" flag. If that isn't checked, then your Chromecast can't be notified that it is allowed to communicate with your app id. Also note that the Chromecast Android app had a bug (don't know if today's update fixed it) where setting that flag wouldn't stick, so I had to do it through the desktop app and then reboot the Chromecast and wait a few hours for the next time it pinged Google.
Make sure you have the "Send this Chromecast's serial number when checking for updates" setting enabled using one of the ChromeCast setup apps for your OS or Android. And reboot your ChromeCast device after enabling that setting.
You should be able to open Chrome and enter http://[ip.to.chrome.cast]:9222 in the browser address field. If your cromecast device is whitelisted the page will open.
I'm looking to target a website specifically for an iPad but we don't have any Macs in house for testing. What's the most accurate way to test the site on a PC? I image I could use the Safari browser and shrink the window down to approximate the iPad screen size but I wonder if there's a better method out there.
If you target a website specifically for a particular device, buy that particular device. This doesn't only apply to iPad.
Two caveats I noticed a lot of websites have for a touch-oriented device like an iPad, iPhone:
The mouse-hover event isn't generated. So, the HTML/CSS/Javascript menu structure which works without clicking on a WebKit browser (like Safari) on a mouse-oriented device might stop working completely.
The scrolling event (coming from a flick of a finger) is not passed to elements inside a page; instead it just scrolls the entire page. A subelement shown with a scroll bar on a non-touch-oriented device might be shown without the scroll bar at all. So, sometimes you lose the ability to scroll inside a subelement.
There might be other caveats. It's really difficult to imagine all the way a device might behave differently from a mouse-oriented device; so, buy an iPad.
By the way, it's of no use to buy a Mac in this situation: Safari on a Mac still behaves (as far as the mouse/touch events are concerned) rather differently from Safari on an iPad/iPhone. An iPad can be paired with a Windows PC.
See this Apple document for a few advices for preparing a web page for the iPad.
I'd just use Safari, as the mobile version uses the same rendering engine (though possibly modified to fit the iPads resources).
It should display the same, if not close.
You can try to use online imitation services.
For example http://app.crossbrowsertesting.com/, or https://saucelabs.com/. They provide lots of imitations environments, for different devices and OS. You can test the site, that is already in the web, or your local files.
I myself am working currently with app.crossbrowsertesting.com for the first time. It really shows the problem, that the client encountered on his iPad. Also have good notices about these services from experienced developer, a friend of mine.