Database Develop

Controlling Android on a Raspberry Pi

I realize this is a dumb question but I haven't been able to find the answer. If I install Android on a Raspberry Pi attached to my TV, how do I control it? Is there a way to use a regular remote control?

There is always the wireless Keyboard and Mouse option.
I believe you can also use multi-touch touchpads such as Wacom Bamboo.

LiFE1688 said:
There is always the wireless Keyboard and Mouse option.
I believe you can also use multi-touch touchpads such as Wacom Bamboo.
Click to expand...
Click to collapse
Thanks for the reply.I was hoping to use a media center remote or something similar, but I assume none of the drivers will work.

If you want to control your RPi using a remote I wouldn't install Android (The current builds aren't that stable and are buggy at best). I would recommend taking a look at Raspbmc, it's Xbmc for the RPi and should be compatible with a variety of media remote controls.
Sent from my SCH-I535 using xda premium

You can Use a Normal Mouse (And Keyboard)

Xbmc isn't really what I'm looking for. If a keyboard and mouse work, maybe someone will figure out how to use a remote.

When android is more polished I think you will have options
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

lithium630 said:
Xbmc isn't really what I'm looking for. If a keyboard and mouse work, maybe someone will figure out how to use a remote.
Click to expand...
Click to collapse
What are you looking for then? Since you want to drive it using an IR remote (I'm guessing), that typically indicates some sort of media center.

METDeath said:
What are you looking for then? Since you want to drive it using an IR remote (I'm guessing), that typically indicates some sort of media center.
Click to expand...
Click to collapse
I run Windows Media Center on all my tv's with the Ceton Companion app to control it. Currently the app does not support streaming live tv but it is supposed to be in the works. When it finally supports streaming to android, I could build a small raspberry pi box and use it as an extender when I'm out of town. If nothing else I would finally have an excuse to buy one.

lithium630 said:
I run Windows Media Center on all my tv's with the Ceton Companion app to control it. Currently the app does not support streaming live tv but it is supposed to be in the works. When it finally supports streaming to android, I could build a small raspberry pi box and use it as an extender when I'm out of town. If nothing else I would finally have an excuse to buy one.
Click to expand...
Click to collapse
this is something like what I want, too. I would ultimately like to have an HTPC running android that supports video streaming, local media playback, live tv and streaming of everything above to all my connected devices.....like xbmc, but also with an option to use it as an android device when necessary. I don't want to have to use a mouse and keyboard for it either since my tv is too far away from the couch for that to be a reasonable option.....but mouse and kb support are still necessary for some things. IMHO, the best possible option would be a logitech remote that also has an on-screen pointer and motion controls like a wii remote has.
......come to think of it, an app supporting a wii remote to control android functions wouldn't exactly be a bad solution!!

you can use raspbmc instead of android if you are willing to use it as media center. it also has broader possibilities for choosing a remote.
http://www.raspbmc.com/wiki/user/configuring-remotes/
but i prefer this one most
https://play.google.com/store/apps/details?id=org.xbmc.android.remote
enjoy !

I use a regular remote from my tv when i use raspmbc since it supports cec. The xbmc remote most people use through their Android device is specific for xbmc, so it wouldnt do much good with anything else. Droidmote isnt the prettiest but its functions well. Theres a lot of apps for remotes, that even take advantage of voice and nfc. So when Android is running stable enough, you will be able to take your pic. If your not interested in embedded hardware or other similar usages for the pi, you could always get a g box midnight or minix neo g4 or 5. There all dual core and come rooted with firmware updates that will give you JB and xbmc. There is a quad core one that is out or coming out and will come with JB and full hardware acceleration.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2

In raspbmc u can use u tv pilot to control xbmc.

Nizda1 said:
IDroidmote isnt the prettiest but its functions well.
Click to expand...
Click to collapse
You can also use Tablet Remote
https://play.google.com/store/apps/details?id=com.tournesol.tabletremote
or LANmote
https://play.google.com/store/search?q=lanmote

Yatse is a damn good remote for xbmc, it syncs your library list to your device, so you can scroll on device, links to imdb for movies,you can change audio tracks,dl subtitles, and all sorts of cool stuff. And it's free
Sent from my DROID3 using xda premium

You can already stream to your ras pi from windows or wherever, I like prefer my tablet or phone. Download the app bubbleupnp from the playstore and it will populate a library of videos, music whatever you have on the device by selecting it as the local renderer and it will see the raspi then press play. Also some android apps like youtube for ex.you can just share it to the app and it will play on your tv connected to the pi. If I want a remote I use the official xmbc remote or if im using a win box to get the media ill use unified remote app. Which then gets cool cause you can use voice and all kinds of stuff.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2

Whats your BIG Chromecast idea? More potential than a "traditional" A/V streamer?

Whats your BIG Chromecast idea? More potential than a "traditional" A/V streamer?
So I've seen many people, developers and users alike, swarming the ideas of the expected basic usages of this wonderful device.
Examples: Out-of-Box expected usage (streaming from qualified providers), mirrored A/V from PC/Phone/Tablet, other connectivity proof of concepts (IE: emulators), ect…
So my question is: What's your big idea to extend the usage of this device beyond "traditional" implementation?
I’ll start by sharing mine (actually 2 product idea’s, that could become 1 at some point in time).
1. All-in-one media station. Taking the concept of a HTPC/XBMC build, and extending it to have the Chromcast as the “presenter”, and the PC/Phone/Tablet as the “remote”. The software package would include a “media server” run on a compatible PC on the same network, accompanied by the “remote” app on the Phone/Tablet (web-based control for PC remote).
I intend to also include the ability to queue/control presentation files such as PPT, PDF, ect… I’d like to have the package useful to both home and business clients/users.
One of my favorite parts of this idea resides in the remote app. Upon selection of the media you intend to cast, use a 2-finger up gesture to begin casting (makes me think of the scene in IronMan2 when he takes over the monitors in the courtroom by using a similar gesture on his “phone”, lol) It’s the little things that get me excited haha.
2. A home automation/security media point. On demand or automated view of automation/security enabled objects in your environment. Example: You have a security system with camera’s in your home, specifically, one is mounted at your front door. Someone appears at your door (motion-trigger), and/or rings the doorbell (another available trigger). HDMI-CEC enabled TV’s would switch the input to the Chromcast and display the camera at your front door.
My brain begins to hurt as all the possibilities for automation and security integration pile up. But hopefully, you get the point.
I’d love to hear from some of the other inventive people on this forum, and interested in the Chromcast. Again, what’s your idea?

Android stick with a BT android remote with cheapcast

Low power consumption httpd, ircd, VPN, or ssh.
Sent from my One true love.

The one thing I'd love to see the chromecast do is be able to connect directly to my phone and use it's 4g for streaming. I would figure something like this should be possible since it's basically what it does during initial setup.
Due to the layout of where I work (big concrete building), I get great signal with my phone in the window, but no signal anywhere else. i'd love to be able to plug the chromecast into the tv during breaks and stream from the phone.

evelbug said:
The one thing I'd love to see the chromecast do is be able to connect directly to my phone and use it's 4g for streaming. I would figure something like this should be possible since it's basically what it does during initial setup.
Due to the layout of where I work (big concrete building), I get great signal with my phone in the window, but no signal anywhere else. i'd love to be able to plug the chromecast into the tv during breaks and stream from the phone.
Click to expand...
Click to collapse
No during initial setup the chromecast generates its own wifi hostpost. Ofcourse this hotspot has no internet access and so would be useless for anything but setting up.
But why not make a hotspot with your phone? That would do the same thing.

I just want miracast support

Chromecast ideas
Chromecast supports multiple connections so could do things like a card game where player cards need to be private. The screen shows the playing field and each player sees just their cards on phone/tablet/computer. Is a simple example but there may be other uses to have multiple game play or interaction to same screen.
Chromecast and DIAL protocol are free to license so could be put into any consumer electronics device - SmartTV, refrigerators, home thermostat, etc.

xenokc said:
Chromecast supports multiple connections so could do things like a card game where player cards need to be private. The screen shows the playing field and each player sees just their cards on phone/tablet/computer. Is a simple example but there may be other uses to have multiple game play or interaction to same screen.
.
Click to expand...
Click to collapse
That is quite an awesome idea! Granted, I see it as a similar setup that the WiiU has tried to do with some of their games. And MS also with the "second screen" for xbox and such.
But why shouln't google get in on this tech as well? I'm very interested to start investigating this idea myself. Mind if I borrow your idea xenokc? lol

Unholyfire said:
That is quite an awesome idea! Granted, I see it as a similar setup that the WiiU has tried to do with some of their games. And MS also with the "second screen" for xbox and such.
But why shouln't google get in on this tech as well? I'm very interested to start investigating this idea myself. Mind if I borrow your idea xenokc? lol
Click to expand...
Click to collapse
Go for it!

Unholyfire said:
So I've seen many people, developers and users alike, swarming the ideas of the expected basic usages of this wonderful device.
Examples: Out-of-Box expected usage (streaming from qualified providers), mirrored A/V from PC/Phone/Tablet, other connectivity proof of concepts (IE: emulators), ect…
So my question is: What's your big idea to extend the usage of this device beyond "traditional" implementation?
I’ll start by sharing mine (actually 2 product idea’s, that could become 1 at some point in time).
1. All-in-one media station. Taking the concept of a HTPC/XBMC build, and extending it to have the Chromcast as the “presenter”, and the PC/Phone/Tablet as the “remote”. The software package would include a “media server” run on a compatible PC on the same network, accompanied by the “remote” app on the Phone/Tablet (web-based control for PC remote).
I intend to also include the ability to queue/control presentation files such as PPT, PDF, ect… I’d like to have the package useful to both home and business clients/users.
One of my favorite parts of this idea resides in the remote app. Upon selection of the media you intend to cast, use a 2-finger up gesture to begin casting (makes me think of the scene in IronMan2 when he takes over the monitors in the courtroom by using a similar gesture on his “phone”, lol) It’s the little things that get me excited haha.
2. A home automation/security media point. On demand or automated view of automation/security enabled objects in your environment. Example: You have a security system with camera’s in your home, specifically, one is mounted at your front door. Someone appears at your door (motion-trigger), and/or rings the doorbell (another available trigger). HDMI-CEC enabled TV’s would switch the input to the Chromcast and display the camera at your front door.
My brain begins to hurt as all the possibilities for automation and security integration pile up. But hopefully, you get the point.
I’d love to hear from some of the other inventive people on this forum, and interested in the Chromcast. Again, what’s your idea?
Click to expand...
Click to collapse
#1 will be done when Plex enables Chromecast functionality.

Chromecast & Ultramon for dual monitor?

Will it be possible at some point to use Chromecast as a gateway to use the TV as second independent monitor, rather than a mirror of the laptop/desktop with a browser extension, maybe in conjunction with Ultramon?
I have Ultramon installed in my laptop. When I turn my iPad into a second monitor using an app like AirDisply, Ultramon immediately picks it up as the second monitor and provides all the functionality for a second monitor - position, resolution, task bar, etc.
Can I achieve something similar with Chromecast + Ultramon, if not now in the future?

New Daddy said:
Will it be possible at some point to use Chromecast as a gateway to use the TV as second independent monitor, rather than a mirror of the laptop/desktop with a browser extension, maybe in conjunction with Ultramon?
I have Ultramon installed in my laptop. When I turn my iPad into a second monitor using an app like AirDisply, Ultramon immediately picks it up as the second monitor and provides all the functionality for a second monitor - position, resolution, task bar, etc.
Can I achieve something similar with Chromecast + Ultramon, if not now in the future?
Click to expand...
Click to collapse
No the CCast wouldn't do that since it would be a waste since the CCast connects to the same network the Android device does so why send it to CCast when you could send it to the Device directly.
CCast does however act as a second monitor for Android and other devices...

New Daddy said:
Will it be possible at some point to use Chromecast as a gateway to use the TV as second independent monitor, rather than a mirror of the laptop/desktop with a browser extension, maybe in conjunction with Ultramon?
I have Ultramon installed in my laptop. When I turn my iPad into a second monitor using an app like AirDisply, Ultramon immediately picks it up as the second monitor and provides all the functionality for a second monitor - position, resolution, task bar, etc.
Can I achieve something similar with Chromecast + Ultramon, if not now in the future?
Click to expand...
Click to collapse
Future, maybe, but the 1-2 second lag from having to compress the video (and Chromecast having to decompress it at the other end) would be annoying at best.

bhiga said:
Future, maybe, but the 1-2 second lag from having to compress the video (and Chromecast having to decompress it at the other end) would be annoying at best.
Click to expand...
Click to collapse
Oh... I never noticed any annoying lag when I use iPad with AirDisplay. I guess iPad has lot more processing power than Chromecast.

AirPlay is designed for screen mirroring and hence low latency. The current methods of Chromecast desktop mirroring essentially make the desktop a video stream first.
Likely this will change once they're screen mirroring is implemented by devices.
Sent from a device with no keyboard. Please forgive typos, they may not be my own.

bhiga said:
AirPlay is designed for screen mirroring and hence low latency. The current methods of Chromecast desktop mirroring essentially make the desktop a video stream first.
Likely this will change once they're screen mirroring is implemented by devices.
Sent from a device with no keyboard. Please forgive typos, they may not be my own.
Click to expand...
Click to collapse
I'm telling you. With AirPlay, there is more than mirroring. You can use the iPad as a second monitor. It works perfectly with Ultramon.

New Daddy said:
I'm telling you. With AirPlay, there is more than mirroring. You can use the iPad as a second monitor. It works perfectly with Ultramon.
Click to expand...
Click to collapse
Yes, and screen mirroring/output isn't the core intent of Chromecast, and I'm not sure screen mirroring will ever make it to iOS for Chromecast.
Long story short, we all can want Chromecast to be more than it is and it's growing steadily, but there will be limits based on its core design.

Thinking about it more... I think Google could (and probably is) making the screen mirroring similar to how RemoteX works in Windows - instead of sending a picture of a red box, send a command to draw a red box - much less data and identical result as long as both source and Chromecast share the same drawing language and techniques. Definitely possible for Android-Chromecast, not sure if/how it could be implemented outside of code that Google owns though, including Windows as a source.
Apple has a definite advantage there as they can make sure iOS, AppleTV and MacOS all share a common drawing implementation.
Sent from a device with no keyboard. Please forgive typos, they may not be my own.

Problem is, can't use computer when full screen for other tasks
You cannot use the computer screen for anything else when using Chromecast. thios would be a win win

Android chrome to chromecast

Hey im new to this chromecast. I can see my chrome browser on the pc but not on android, how can I do that? Sijce here are very experienced users oj chromecast can someone describe the full working potentials this device has?
Sent from my GT-N8013 using xda app-developers app

You cant do squat with Chrome on Android yet for some odd reason.

Tab casting from Chrome uses the host CPU to re-encode the video and stream it to the Chromecast on-the-fly. Tablet and phone CPUs don't have enough processing power. That's why there's no Chromecast extension for Chrome on your portable device.

Well that sucks bc there is possibilities with this chromecast. I downloaded the allcast and obviously updated my google services. I cast a picture and it doesnt show normal, shows rotated to the left. Can you cast from the gallery vids and photos?
Sent from my GT-N8013 using xda app-developers app

The man problem is the fact that Android Chrome does not support Chrome Apps and Extensions.
Something I'm told Google is working on...

Asphyx said:
The man problem is the fact that Android Chrome does not support Chrome Apps and Extensions.
Something I'm told Google is working on...
Click to expand...
Click to collapse
Yea they better be working on it, this has been out couple months now they need to update more
Sent from my GT-N8013 using xda app-developers app

Google is working on a way to mirror your android screen to the chromecast and we know this because on kitkat roms theres an option to cast screen but isn't quite working yet. Its only been coded in but thats it.
Sent from my SPH-L710 using Tapatalk

tooblackforjack said:
Google is working on a way to mirror your android screen to the chromecast and we know this because on kitkat roms theres an option to cast screen but isn't quite working yet. Its only been coded in but thats it.
Click to expand...
Click to collapse
KitKat roms have Miracast, a different protocol.
Supported by HTC and Samsung since 2012 with their private dongles.
Not new, sorry.

EarlyMon said:
KitKat roms have Miracast, a different protocol.
Supported by HTC and Samsung since 2012 with their private dongles.
Not new, sorry.
Click to expand...
Click to collapse
Yeah ik, i was just informing in case he didn't know sorry.
Sent from my SPH-L710 using Tapatalk

EarlyMon said:
KitKat roms have Miracast, a different protocol.
Click to expand...
Click to collapse
Yes, but Google has renamed it to Cast Screen. Clearly, they will be adding support for casting to Chromecasts directly inside of Android. Otherwise, renaming it to match the Chromecast nomenclature makes no sense.

bozzykid said:
Yes, but Google has renamed it to Cast Screen. Clearly, they will be adding support for casting to Chromecasts directly inside of Android. Otherwise, renaming it to match the Chromecast nomenclature makes no sense.
Click to expand...
Click to collapse
Because MiraCAST isn't confusing enough?
I'm aware that a number of blogs not familiar with Miracast are spreading that rumor. I think it's wishful thinking but we'll see, won't we?
http://www.howtogeek.com/177145/wir...ed-airplay-miracast-widi-chromecast-and-dlna/
http://readwrite.com/2013/11/07/android-kitkat-developers-users
A side note, Android 4.4 KitKat devices can now be certified by the Wi-Fi alliance as being Miracast compatible. That is a big step for Android in being able to stream content from a device to a television by supporting more streaming standards. Now only if the Chromecast supported Miracast.
Click to expand...
Click to collapse
http://www.androidpolice.com/tags/miracast/
So, you believe that WiFi Direct is coming to the existing Chromecast?
Or that in addition to Miracast, they'll be providing a second protocol for phones, with a server (like Koush did)? And people will be able to figure out the two casting options on their devices?
I think that it's far more likely that rather than put both protocols on a phone or into the existing Chromecast, it's more likely that DIAL support plus Miracast *might* appear in a Chromecast 2.
Miracast dongles already exist, it's February and the SDK libraries still aren't out, and in July, Chromecast will be a year old.
Apple TV costs $100 with this feature, a Belkin Miracast dongle is $80, an HTC Media Link HD is $100, the Samsung Allshare Cast Hub was a hundred, is $65 on Amazon now.
It's possible that Google is going to pump this in to the existing Chromecast for the faithful for free, but I'm just not feeling it.
Either way, so far KitKat includes Miracast, not DIAL.

EarlyMon said:
Or that in addition to Miracast, they'll be providing a second protocol for phones, with a server (like Koush did)? And people will be able to figure out the two casting options on their devices?
I think that it's far more likely that rather than put both protocols on a phone or into the existing Chromecast, it's more likely that DIAL support plus Miracast *might* appear in a Chromecast 2.
...
It's possible that Google is going to pump this in to the existing Chromecast for the faithful for free, but I'm just not feeling it.
Either way, so far KitKat includes Miracast, not DIAL.
Click to expand...
Click to collapse
First part:
Since it's (Android) device mirroring functions appear to be in the SDK, but are limited only to OEM developers, my best-guess is that what we'll see is any Chromecast device mirroring will have to be "cooked" into a ROM rather than a loose bit (makes sense - that's how Samsung's AllShare Cast works too).
Hopefully the UX engineers win and make it so the Screen Mirroring option at least combines Google Cast and Miracast device options together, rather than having separate options for Screen Mirroring (Miracast) and Screen Mirroring (Google Cast).
Second part:
Yeah, not going to hold my breath. As I keep saying, screen mirroring is not the core competency of Chromecast.

bhiga said:
First part:
Since it's (Android) device mirroring functions appear to be in the SDK, but are limited only to OEM developers, my best-guess is that what we'll see is any Chromecast device mirroring will have to be "cooked" into a ROM rather than a loose bit (makes sense - that's how Samsung's AllShare Cast works too).
Hopefully the UX engineers win and make it so the Screen Mirroring option at least combines Google Cast and Miracast device options together, rather than having separate options for Screen Mirroring (Miracast) and Screen Mirroring (Google Cast).
Click to expand...
Click to collapse
Both together sounds like a bit much, but it's possible.
Samsung is likely going their own way.
http://www.slashgear.com/samsung-an...ultiscreen-and-overlay-capabilities-28303309/
Second part:
Yeah, not going to hold my breath. As I keep saying, screen mirroring is not the core competency of Chromecast.
Click to expand...
Click to collapse
Agree.

If you ask me any attempt to make CCast work like a Miracast would be a big waste, Even a downgrade!
No need for Direct Connection for Mirroring as Mirror over IP is far more flexible and less problematical. Not to mention requires no special software support like Miracast does. If they really wanted Miracast type direct mirroring all it would take is some additions to the rom cause hardware wise, the CCast has everything it needs
It may not be part of why the CCast was developed but I don't see Google being as smart as they are leaving that market open to Miracast dongles when they know full well the only thing inhibiting CCast from doing it (and better) is their lack of developing an App that does it for Mobile...
As for the Casting support in the SDK for OEM use I suspect that is more generic in nature and just an exposure of the display system to support Miracast, Perhaps CCast Mirroring and any other 2nd screen tech that comes down the pipe.
I think mirroring feature is a bit overrated myself, it's good for an audience but not for an operator's use.
It's easier to do than what CCast is trying to do because there is no need for a control protocol...Just a simple transcoder for Video and Audio the rest is all done on the Master Display device.
As for that Samsung option I don't expect it to take off due to proprietary concerns. It's meant for Samsung SmartTVs and I bet LG and Sony won't support it. Samsung would be better off building that capability directly into the TV itself.
DIAL is still in its infancy and I expect the protocol to expand as support and adoption of it grows...
Whatever lessons they learned from Chromecast I expect to be addressed whenever they get around to making the second gen CCast.
Wired Networking or at minimum 5Ghz Wireless support is to be expected as would a more robust Video playback Compatibility.
It's not likely that any app that adds CCast support is going to remove it in the future which means as the Apps list grows so too does the chance we have of seeing this supported without the need for a dongle at all.
TV over the Web will work the way it was supposed to and remove the biggest hurdle to achieving full IPTV to date...
The Navigation and Channel Guide no one could figure out how to do....
And who knew the Web Browser was the answer all along.

Samsung is still the largest supplier of flat screen TVs in North America, is it not?
Besides, they've never been shy about adding interfaces to support the future. I have a Samsung TV with a specialized iPod interface as proof. (And I believe that the article did say clearly that Samsung was going to build the new casting into their TVs.)
And none of the TV makers think twice about adding fragmenting features, and Samsung certainly doesn't for their mobile devices.
As for the claim that it's just about making a mobile app and declaring victory for screen casting, you might want to review the API changes that have been evolving for months.
Doing that without library support and not differentiating DRM vs non-DRM cast calls may seem simple to you but it doesn't to me.
Last published, Netflix and YouTube accounted for over 50% of North American broadband traffic.
Screen casting may be an emerging market, or it could just be a flash in the pan.

EarlyMon said:
Samsung is still the largest supplier of flat screen TVs in North America, is it not?
Besides, they've never been shy about adding interfaces to support the future. I have a Samsung TV with a specialized iPod interface as proof. (And I believe that the article did say clearly that Samsung was going to build the new casting into their TVs.)
And none of the TV makers think twice about adding fragmenting features, and Samsung certainly doesn't for their mobile devices.
As for the claim that it's just about making a mobile app and declaring victory for screen casting, you might want to review the API changes that have been evolving for months.
Doing that without library support and not differentiating DRM vs non-DRM cast calls may seem simple to you but it doesn't to me.
Last published, Netflix and YouTube accounted for over 50% of North American broadband traffic.
Screen casting may be an emerging market, or it could just be a flash in the pan.
Click to expand...
Click to collapse
Well I guess Samsung is the largest supplier of Flat Screens in NA just like Apple is the biggest supplier of Smart Phones in NA...
Until you realize combine all the NOT Samsung Models into an US vs THEM and they are not the Majority by any means...Same with Apple vs Android as opposed to Apple vs Samsung itself.
As for the DRM you forget that DIAL doesn't care and leaves using or not using up to the content provider. It's there if you want it and if not you only have to support the DIscover and Launch capabilities.
Is Sony (who owns a majority of content compared to Samsung) going to cut out DIAL for Samsung's proprietary system?
Doubtful!
And since the CCast and DIAL supports ANY TV with HDMI input it has a far better chance of being adopted as a standard than Samsung's device is.

IMO most of the current desire for screencasting is really a "backup plan" for content that is currently not supported via DIAL. "___ isn't supported so I want to mirror my screen/tab."
So the mainstream correct solution would be to get the desired content providers on-board with Google Cast.
That would leave non-"canned" content for screen mirroring (games in a second screen model, general browsing, presentations, Skype, etc).
I'd love to see a native Skype for Chromecast using the microphone and controls on my tablet/phone with video on the TV but keeping it in sync might be nontrivial engineering on the Skype end.

Asphyx said:
As for the DRM you forget that DIAL doesn't care and leaves using or not using up to the content provider. It's there if you want it and if not you only have to support the DIscover and Launch capabilities.
Click to expand...
Click to collapse
I can only invite you, again, to look at the actual casting API rather than rely on assumptions.
It's NOT the same as that last July and it absolutely, positively does recognize casting DRM content.
Start here -
https://groups.google.com/a/chromium.org/forum/m/#!topic/apps-dev/emlKA4C-c90
And then Google for what's happened since, along with Koush's commentaries.
Is Sony (who owns a majority of content compared to Samsung) going to cut out DIAL for Samsung's proprietary system?
Doubtful!
And since the CCast and DIAL supports ANY TV with HDMI input it has a far better chance of being adopted as a standard than Samsung's device is.
Click to expand...
Click to collapse
Did you even read the article to discover that Samsung is using a superset of DIAL and support by Sony, LG, and Panasonic TV sets is expected?
---------- Post added at 04:14 PM ---------- Previous post was at 04:07 PM ----------
bhiga said:
IMO most of the current desire for screencasting is really a "backup plan" for content that is currently not supported via DIAL. "___ isn't supported so I want to mirror my screen/tab."
So the mainstream correct solution would be to get the desired content providers on-board with Google Cast.
That would leave non-"canned" content for screen mirroring (games in a second screen model, general browsing, presentations, Skype, etc).
Click to expand...
Click to collapse
Have you checked out what Vbukit is planning on supporting with Chromecast?
Pretty interesting, I think.
Not sure about getting Skype sorted out.
It seems like every time Skype updates, it's a step backwards, but that's just my off-topic opinion.

EarlyMon said:
Have you checked out what Vbukit is planning on supporting with Chromecast?
Pretty interesting, I think.
Not sure about getting Skype sorted out.
It seems like every time Skype updates, it's a step backwards, but that's just my off-topic opinion.
Click to expand...
Click to collapse
Yes, Vbukit is a little rough around the edges, but I can definitely see it being useful for presenters and educators especially.
Agree with you on Skype...
Back on-topic, there isn't a lot of technical copyright/DRM concern regarding casting anything you see on the screen - after all, if you can see it on the screen, you've seen it already. It's just that the legal types are not technical, highly likely to make crazy conclusions and assumptions, and get paid no matter what they do - so it's in their best interest to make issue of little things. I've personally seen warnings from the copyright hunters complete with ISP traces down to the router endpoint too, so they are watching and waiting to pounce.
I still hope an optimized device mirroring comes as something deeper within the Android OS itself.
Something akin to RemoteX in the Windows space, which is a "remote render" or offload of the graphic drawing functions. Anything that's not reliant upon a local bitmap could be rendered on Chromecast, rather than sent as large/inefficient bitmap data or CPU-intensive compressed data. That would make some "twitchy" games playable, especially if Chromecast has enough memory/storage to cache bitmaps that it does end up needing. Full-screen video, of course, doesn't benefit, nor does typical FPS games since the entirety of the screen is being updated with bitmaps.
For fun, I played a video on my phone and watched it on my computer (no audio) via TeamViewer. It took me back to the early 90's.
We've waited for apps and other optimized content this long, let's see what Google delivers.

Content providers have been successfully inhibiting HDMI and MHL output from their apps running on Android devices.
I believe that the casting API changes may have them in mind, but that's pure conjecture on my part.
I think it's ridiculous but so long as people check the boxes and agree to the terms of service, they're free to enforce it.

Is there a working way to mimic the chromecast's cec switch-input behavior?

Hi everyone, first time poster so I'm sorry if this isn't the right forum to post in, but I felt like it was the closest I could think of.
I'm trying to find a way to mimic how the chromecast causes a tv to switch to the input of the chromecast dongle. I have an Android Box that came rooted and has HDMI-CEC capability. What I'm looking to do is somehow use Tasker to trigger the CEC-switch activity/intent/whatever to have my tv (turn on) and switch to the HDMI source of the Android Box (the box will be left on 24/7 and tasker will continually run as background service on the box). Basically, I'm trying to imitate the chromecast's cast action to bring me to my Android Box's input and ultimately it's home screen.
That's where I'm stuck at the moment. Things I've thought might work:
1. Wake-On-Lan (Doesn't seem to wake the box, even when I've checked to make sure the power button made the box sleep and not perform a full shutdown) Tried-Unsuccessful
2. AutoCast to have the box cast to itself, but it doesn't have chromecast/miracast/etc built-in as far as I can tell according to the specs and see anything about cast ability while browsing through its menus.
3. Using Android's HDMI-CEC library in a Java Action in Tasker to imitate the CEC switch sources intent/activity. However, I just recently learned that Google decided to lockdown their API for HDMI-CEC interactivity, so that scrubs that idea.
4. The best bet, and what gave me the idea to post here, is this App Cast Receiver that was created by another user on these forums that seems to accomplish something close to what I'm trying to do in allowing an android device to imitate a chromecast device. If I were able to use this couldn't I then use the AutoCast app I mentioned above to have the Android Box cast to itself, then stop the AutoCast app a few seconds later (after giving the box's CEC capability enough time to make the tv switch sources)? But, unfortunately it appears the app has since been deserted and won't work with the newer chromecast sdk. Maybe someone has an alternative app?
Since this is my first Android Box I'm not quite sure how Tasker actions function when ran from the box. Example: Would a Wake Screen Action trigger a switch of HDMI inputs?
So, after exhausting all my ideas after coming up with nothing in my searches I figured I'd ask the community here since this seems to be a pretty dev/mod-heavy community (and I love it). I'm not sure if this would be better suited for the Tasker or AMLogic Android Box forums on here. If so, I'll happily move the post if a mod cannot do so for me.
TL;DR: Looking for some way, be it app or otherwise, to imitate chromecast behavior (utilizing CEC) in order to make tv switch source to a running Android Box's homescreen.

Hey! tell me more about 3, I was looking to have a Raspberry Pi act as a go-between to simulate CEC with a non-CEC TV by receiving my remotes IR codes and sending either CEC codes to the ChromeCast or using the CC API to pause/stop play - but only reverse engineered versions are available on Pi.
The Pi has built-in CEC support so you can use `apt-get install cec-tools` and then play with the `cec-client` to do some interesting stuff. The ChromeCast in my case has an invalid address so I don't seem to be able to activate pause play. (I see a logical address of 4 but also an address of `f.f.f.f`, ie invalid).
Anyways, it may be worth playing with a Pi and seeing if HDMI-CEC will do what you want, and then seeing if you can get a CEC library for android and just recreate the Pi work. Less hoops to jump around.
I don't know enough about the Android side. The CC API has an Android implementation so I would think you'd be able to do everything you want, iff it does the switching. I've done very little development on Android (a meteor app and an Android native camera library work), unfortunately. (If the Pine64 supports CEC I may end up going down this route).
I've posted more about my interest here: on reddit /r/Chromecast/comments/5znpuk/i_want_to_use_a_raspberry_pi_to_control_the/

jlongman said:
Hey! tell me more about 3, I was looking to have a Raspberry Pi act as a go-between to simulate CEC with a non-CEC TV by receiving my remotes IR codes and sending either CEC codes to the ChromeCast or using the CC API to pause/stop play - but only reverse engineered versions are available on Pi.
The Pi has built-in CEC support so you can use `apt-get install cec-tools` and then play with the `cec-client` to do some interesting stuff. The ChromeCast in my case has an invalid address so I don't seem to be able to activate pause play. (I see a logical address of 4 but also an address of `f.f.f.f`, ie invalid).
Anyways, it may be worth playing with a Pi and seeing if HDMI-CEC will do what you want, and then seeing if you can get a CEC library for android and just recreate the Pi work. Less hoops to jump around.
I don't know enough about the Android side. The CC API has an Android implementation so I would think you'd be able to do everything you want, iff it does the switching. I've done very little development on Android (a meteor app and an Android native camera library work), unfortunately. (If the Pine64 supports CEC I may end up going down this route).
I've posted more about my interest here: on reddit /r/Chromecast/comments/5znpuk/i_want_to_use_a_raspberry_pi_to_control_the/
Click to expand...
Click to collapse
Here's the link to Android's documentation for the HDMI-CEC Control Service. But, like I said it's been locked down and only allows system-level access now.
I don't have any Pi at my disposal (plus my Android Box also has built-in CEC-capability/functionality) and since my situation doesn't actually involve chromecast I never thought to look at their api/sdk. But, I was able to finally solve my problem with a painfully simple, yet not that intuitive or logical method. The way my box's os/firmware appears to work is by firing the cec signal to switch inputs only on its boot_complete and wake_from_standby procedures. My solution just simulates pressing the Standby button twice in a row via Shell command (with Root option checked) from within Tasker. Logically, I thought after the first press the box wouldn't respond to the second press due to already being in standby mode (because of the first button press). But, it turns out both simulated presses occur (maybe keyevents are queue?), allowing me to put the box in standby momentarily and immediately bring it out of standby, which triggers the wake_from_standby procedure and in turn causes the input to switch (or my tv to turn on then input to switch).

My thought with the Pi and CC API was that you would use the PI to monitor the HDMI-CEC bus as the output is controlled by the CC - assuming it switches the input to itself but my TV doesn't support HDMI so maybe that's a bad assumption - and then use that knowledge to replay using the Android HDMI-CEC API. And not understanding what you meant by the API being locked down. That kind of sucks - I was hoping Android would be another bridge platform if the Pi failed me.
Well congrats on a working solution. Cheers!