I would like to detect if Android TV is being video casting (connected from phone (sender) ).
Android TV has the system app (Chromecast build-in) pre-installed. I would like to know if there is events that a phone is connected or just disconnected for video casting.
Or do I need to develop custom Chromecast receiver app just in order to catch those events?
Found this https://stackoverflow.com/a/58655387/1099884, but it is not what I needed. I would like the opposite usage. (My device is receiver while the others are sender)
Related
Do I need to develop Android TV Receiver App to cast from existing sender app to "Chromecast with google tv" device?
I thought just web receiver app would be okay for casting without registered android TV app just like Chromecast.
You do not need to developer an Android TV receiver app to cast to the Chromecast with Google TV. A standard web receiver will work on this device the same as a typical device running the Android TV OS. The main reason to use the Cast Connect library to build an Android TV receiver app is if you already have an Android TV app and want to give a more robust casting experience (e.g., allowing users to control playback with their remote control or providing a UX that's easier with native Android code).
I am using eddystone beacons to transmit my business url. How can I make the url notification received to alert thru sound on the users device? Any idea?
Understand that Eddystone-URL beacon advertisements don't automatically do anything on a user's phone unless they have an app installed to detect them.
Chrome for iOS and Android (installed on many newer Android devices, but very few iOS devices) will automatically detect Eddystone-URL advertisements and display a notification from Chrome if the user has opted-in. However, no sound is played. Bottom line: on a phone without a custom app, detecting an Eddystone-URL will not cause a sound to play.
If you build a custom app and get it installed on users' devices, you can certainly make it play a sound on Android devices when the beacon is detected. On iOS devices, you could also display a local notification on the device that will play a sound, but only if the user has the volume turned up on the device, does not have do not disturb on, and has opted-in to receiving notifications from the app.
In Android Wear it shows the notification and we can reply back through wearable device. But how to start any app from the Wearable device like voice input("Ok Google") or tap on the icon. Action should start from the wearable device not from mobile.
For Example to start my mobile's camera through Android Wear Device i will give voice input as "start Camera" and camera should start.
With the current preview-version of the SDK, this is not possible yet.
But looking at http://developer.android.com/wear/design/user-interface.html tells you, that this will possible using the "Cue Cards".
You can do this now! :)
With the release of the Wear SDK (API Level 20, Android 4.4W), you can now develop Wear applications with very much the same stack as standard Android apps (i.e. Activities, Services, Layouts, Views, &c).
There is also an API for communication, which for example Google Play Music uses to control media playback from the watch.Therefore, you could develop an application, installed both in the Wear device and in the handheld, to launch the phone's camera when started (by sending the command from the Wear activity).
We're building a LIVE Smooth Streaming WP7 App.It works perfectly on the emulator, but not on device (shows up blank).
We are also trying smf player for streaming on WP7 but every time we are getting a blank screen on player. Its only work on Emulator.
Though there is no error being thrown.
How i can apply live streaming on my windows phone not on emulator.
looking for your responce
Does your streaming source contain multi-resolution tracks?
This kind of problem may appear when testing on a WP8 Emulator and then deploying the app to a WP7 device. Specially if the WP7 device is a first-generation device, like HTC HD7.
Basically this happens because the WP8 emulator and Wp8 devices do support multi-resolution, but old devices do not support multi-resolution tracks. You can read more here: http://blog.supaywasi.com/2013/01/smooth-streaming-multi-resolution-support-for-windows-phone/
So, basically you have to handle the ManifestReady event on your WP7 app and RestrictTracks to only tracks of the same resolution.
For WP8 devices you will not need to this.
I am using a mediaelement and when the headset is unplugged I get a mediafailed event with NullReferenceException. Since the media element stream is not working anymore, I want to be able to distinguish this case and to handle it properly.
It is in the windows phone 7 design that when you unplug a headset or your headphones that the music player or other apps using the mediaelement should pause.
You can have a look at the CurrentStateChanged event to see if the state of the MediaElement is changed.
docs:
http://msdn.microsoft.com/en-us/library/system.windows.controls.mediaelement.currentstatechanged%28VS.95%29.aspx