Database Develop

NC for HTPC remote - thoughts?

Going to be setting up a HTPC pretty soon and was looking for remote control options. Considering I just want it to mainly be a HTPC remote, it would just need Wifi, a big screen, and Android, the NC does seem a strong contender at first glance.
XBMC with it's Android wifi-based remote app seems like a very nice solution, as well as some others, (as long as the apps work fine on the larger screen).
Anyone have any thoughts or experience with this, or alternate suggestions?

The Nook is a fantastic media remote. I've not tried the XBMC apps specifically yet, though they should work fine.
I've built a home theater & home automation setup around a Windows program called Girder, from Promixis. Girder offers a full web server with javascript hooks so you can create html pages and use any browser to control things.
I started with this, using Nokia 800 tablets as the controller. It worked great, but I wanted more responsiveness and features than browsers would easily let me achieve. Thankfully Girder has a nice web service interface, against which I've been writing a native Android app that acts sort of like a Philips Pronto universal remote, except with all the Android goodies like voice recognition, gestures, etc.
Regardless of the implementation details, the Nook is a solid media remote control when paired with a decent back-end. The battery life is fine if you don't mind keeping a plug nearby (I get just under a week with moderate remote usage and occasional browsing), the form-factor isn't too big, and the bundled capabilities of an armchair browsing/<insert Android app here> device are hard to beat.
My only wants that the Nook doesn't have would be a few more physical buttons (I already map the volume buttons to TV volume controls but would like channel and FF/Rewind/Play or D-Pad controls), vibrate feedback for button presses, and a less finicky plug, ideally a drop-and-charge dock of some kind.
HTH!

I'm an avid XBMC fan. Been running it for a good while now. I ordered a NookColor for the same reason you did OP. The XBMC app is great on my Android phone, and I've been talking with the dev who works on it, trying to come up with some improvements for when it's run on tablets. I'd definitely recommend using it if you've got XBMC running off a machine at your place.

Thanks for the responses. Think I'll end up getting one later on, once I get the rest of the setup going (who knows, they might be back in stock by then ).
I've had XBMC running on my home server as a test for a little while, with the app on my HD2 running Android. App hasn't been 100% stable, force closing here & there, but hard to tell if it's the app, or just some of the quirks found in running Android on HD2. I did notice battery life suffered quite a bit, but that was with heavy remote testing today. I'll have to see how that goes with more testing.
The Girder stuff looked interesting, except for it's price tag. I'm on a bit of a budget & still have to get HTPC specific hardware, and slightly redo the backend. XBMC on Ubuntu is free and quite acceptable, so that's what I'll stick with for now. I did like that the stock phone volume controls worked through XBMC to control it's playback volume.

I use my Nook for a remote on my Ubuntu HTPC box.. Using Boxee instead of XBMC though. The Boxee app works great.

I tried both the apps for xbmc in the market - they both work well.
My problem is I have freeze-ups with xbmx on win 64 computer; don't know if it is related to nook as controller yet.

XBMC is the way to go, no doubt.
The app works fine now, but since the screen is so much larger, there is room for scaling improvements throughout the app. Nothing is a deal breaker, though.
I love that you can send links to stream to XBMC

Another XMBC user here using the Nook as a remote. Also on my Ubuntu box I'm running Subsonic (/w the Android app) - makes a much better streaming music server.

The boxee app is what I use on my HTPC. Then I use the Cloud Boxee remote app on my nook. It works great!
Sent from my PC36100 using XDA App

I have tried a few of the remote apps on the Market and I havent found anything yet that really fits.

Can anyone point to a tutorial on how to set up the XBMC/NC remote to work with a Win7 HTPC?
Still very new to the rooted NC world.
Many thanks!
sorry, found it shortly after I'd posted this

I installed both "the official" xbmc remote, and the other one that is rated well, but neither one is working. The official one asks that I set up Hosts in Settings, but the settings page it offers is blank. So there is no way to do what it is asking
The other one, keeps telling me to make sure XBMC is allowing control via HTTP in Network settings (which it is) My Nook is connected to my wlan, so it should be connecting

Unified Remote Control offers the most remotes I have seen in 1 program.
Really simple and handy.

RASTAVIPER said:
Unified Remote Control offers the most remotes I have seen in 1 program.
Really simple and handy.
Click to expand...
Click to collapse
Do you know if it successfully works in XBMC?

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

miracast and xbmc

was thinking about this possibly being a sweet setup hopefully miracast will be implemented into the device or possible being implemented into xbmc having that along the airplay option on xbmc enabled would make this a pretty sweet device
i purchased(preordered one) but I was hoping it would be more so like a media center device kinda like google tv but no hdmi out so no google tv overlay. But if I could use this to do miracast with my 4.2 sgs3 and whenever friends come over can use xbmc to allow them to do airplay that would be really cool
reason i bring up miracast support is because supposedly is supported in tegra 3
i've been trying to figure/find out how you go about setting up a miracast server but the documentation doesn't seem to exist not saying that i have the ability to implement but i wouldn't mind taking a look into it
thoughts?

This is more of a question for xbmc team. I suggest you provide that feedback on their forum. There was a talk of xbmc supporting miracast but no eta.
Sent from my GT-I9305 using xda premium

As long as it supports PLEX, I am sold!

Keland44 said:
was thinking about this possibly being a sweet setup hopefully miracast will be implemented into the device or possible being implemented into xbmc having that along the airplay option on xbmc enabled would make this a pretty sweet device
i purchased(preordered one) but I was hoping it would be more so like a media center device kinda like google tv but no hdmi out so no google tv overlay. But if I could use this to do miracast with my 4.2 sgs3 and whenever friends come over can use xbmc to allow them to do airplay that would be really cool
reason i bring up miracast support is because supposedly is supported in tegra 3
i've been trying to figure/find out how you go about setting up a miracast server but the documentation doesn't seem to exist not saying that i have the ability to implement but i wouldn't mind taking a look into it
thoughts?
Click to expand...
Click to collapse
I've heard the documentation costs around $200 and that might not even be all of it. Or I might be pulling that number out of air, don't remember where I saw that, but did find this:
http://forum.xbmc.org/showthread.php?tid=147320
I am more interested in seeing the Android Transporter Player ported to Ouya, except that they haven't released their source code on the sending side yet...
https://github.com/esrlabs/AndroidTransporterPlayer
https://www.youtube.com/watch?v=lyoZoNA8U24
~Troop

I'm not from familiar with Miracast. All I know is what the Wiki page said. It really reads like DNLA. And from my experience, this has been something that can be app dependent. Since I have no experience with Miracast, I don't know if it's full mirroring or just certain apps.
That said, Miracast may just be work versus just installing individual apps. Unless there is something in the application code for specific devices, if you side load an APK, it should run on the Ouya. Doesn't mean it will run well or look correct. Thus, you may be able to just side load XBMC. I know I'll try it with Plex, Netflix, Hulu, various sports--MLB, NHL, NBA, etc--and so on.
I couldn't figure out what the end result you were suggesting about friends coming over and their mobile devices.

lovekeiiy said:
I'm not from familiar with Miracast. All I know is what the Wiki page said. It really reads like DNLA. And from my experience, this has been something that can be app dependent. Since I have no experience with Miracast, I don't know if it's full mirroring or just certain apps.
That said, Miracast may just be work versus just installing individual apps. Unless there is something in the application code for specific devices, if you side load an APK, it should run on the Ouya. Doesn't mean it will run well or look correct. Thus, you may be able to just side load XBMC. I know I'll try it with Plex, Netflix, Hulu, various sports--MLB, NHL, NBA, etc--and so on.
I couldn't figure out what the end result you were suggesting about friends coming over and their mobile devices.
Click to expand...
Click to collapse
I believe Miracast is primarily for screencasting - ie it just mirrors what is on the device's screen onto the TV or whatever is receiving. And I believe the previous poster was saying that it would be nice if it is easy to screencast from your phone to the TV and allow visiting friends to be able to easily screencast their content as well - so if one person has a video they want to show everyone, it's not a hassle to pull it up on the big screen. I think this is what a lot of us want.
~Troop

Trooper_Max said:
I believe Miracast is primarily for screencasting - ie it just mirrors what is on the device's screen onto the TV or whatever is receiving. And I believe the previous poster was saying that it would be nice if it is easy to screencast from your phone to the TV and allow visiting friends to be able to easily screencast their content as well - so if one person has a video they want to show everyone, it's not a hassle to pull it up on the big screen. I think this is what a lot of us want.
~Troop
Click to expand...
Click to collapse
yea this is exactly what i'm lookin for been keeping an eye on it have google alerts set up for pretty much anytime miracast is being searched on the net to possibly find any tidbit of info that might be helpful with this. thanks Troop

video streaming
Hi all. Bit late to the party but my ouya comes tomorrow
Assuming no problems on sideloading why not just use
twonky. Been using for ages bouncing files between my
nas drive, xperia s, xoom2 and Xbox. Even adhoc with
android.......jus puttin it out there..... It's spot on even with
playlists and web streams.

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.

[Release] OpenAuto - open source AndroidAuto(tm) headunit emulator

Hello,
I would like to announce my newest project called OpenAuto.
Donate​
What is OpenAuto?
OpenAuto is an open source AndroidAuto(tm) headunit emulator application based on aasdk library and Qt libraries. Main goal is to run AndroidAuto(tm) on the RaspberryPI 3 board computer smoothly.
Demo video: https://www.youtube.com/watch?v=k9tKRqIkQs8
Status
Project is currently under beta testing.
Links and open source code
https://github.com/f1xpl/openauto
Features
480p, 720p and 1080p with 30 or 60 FPS
RaspberryPI 3 hardware acceleration support to decode video stream (video stream up to [email protected])
Audio playback from all audio channels (Media, System and Speech)
Audio input for voice commands
Touchscreen and buttons input
Bluetooth
Automatic launch after device hotplug
User-friendly settings
Supported platforms
Linux
RaspberryPI 3
Windows
Before you start using OpenAuto please read Readme and wiki page. Also check OpenAuto Pro.

Whoa, nice work. Would this also have a audio EQ/Crossover interface for the Pi?

Can you post a Windows binary build please? Thanks

Daved+ said:
Can you post a Windows binary build please? Thanks
Click to expand...
Click to collapse
Is this at least possible OP? Noobs here, Thanks in advance.

Will this work as standalone or does it need the app?
"Do not use while driving" Well where is the fun in that?

look like someone may able create Open AA instead and resolve blocking issue by google..i guess

Time to give my ride a sweet upgrade

Will raspberry survive high or low temperatures?

I'm trying to compile it, but I got a bit rusty in building under linux.
Code:
[ 6%] Building CXX object CMakeFiles/autoapp.dir/src/autoapp/Main.cpp.o
In file included repos/android-auto/openauto/src/autoapp/Main.cpp:19:0:
repos/android-auto/openauto/include/f1x/openauto/autoapp/USB/USBMain.hpp:22:40: fatal error: f1x/aasdk/USB/USBWrapper.hpp: No such file or directory
#include <f1x/aasdk/USB/USBWrapper.hpp>
Did I forget something when configuring with cmake?

f1x said:
Hello,
I would like to announce my newest project called OpenAuto.
Donate​
What is OpenAuto?
OpenAuto is an open source AndroidAuto(tm) headunit emulator application based on aasdk library and Qt libraries. Main goal is to run AndroidAuto(tm) on the RaspberryPI 3 board computer smoothly.
Demo video: https://www.youtube.com/watch?v=k9tKRqIkQs8
Status
Project is currently under beta testing.
Links and open source code
https://github.com/f1xpl/openauto
Features
480p, 720p and 1080p with 30 or 60 FPS
RaspberryPI 3 hardware acceleration support to decode video stream (video stream up to [email protected])
Audio playback from all audio channels (Media, System and Speech)
Audio input for voice commands
Touchscreen and buttons input
Bluetooth
Automatic launch after device hotplug
User-friendly settings
Supported platforms
Linux
RaspberryPI 3
Windows
Before you start using OpenAuto please read Readme and wiki page.
Click to expand...
Click to collapse
Hi! First of all, thank you for bring us this post! Amazing I've the same question as another guy here, Could you post the Windows binaries or link to the step by step to get it running under windows?
Thanks a lot in advance!

Seriously impressive, great work.
Works perfectly on my Pixel 2/PI3.

Do you think it would be possible to get Android Auto Wireless functionality at a later point? Or does this require some specific wireless/bluetooth protocol that Google hasn't released just yet?

bluethoot
What can you do with the bluethoot feature ?

xbenjiiman said:
Seriously impressive, great work.
Works perfectly on my Pixel 2/PI3.
Click to expand...
Click to collapse
Thanks for your feedback. Great to see it working .
Zaf9670 said:
Do you think it would be possible to get Android Auto Wireless functionality at a later point? Or does this require some specific wireless/bluetooth protocol that Google hasn't released just yet?
Click to expand...
Click to collapse
I think it will be possible but needs some time and effort to implement it. OpenAuto is a hobbyist project and I cannot promise the exact deadline but this feature is on the TODO list.
brett1996 said:
What can you do with the bluethoot feature ?
Click to expand...
Click to collapse
What do you mean?

f1x said:
I think it will be possible but needs some time and effort to implement it. OpenAuto is a hobbyist project and I cannot promise the exact deadline but this feature is on the TODO list.
Click to expand...
Click to collapse
I wasn't sure how much of Android Auto is "open" to use. I haven't invested too much time looking into these forks like Auto and Wear but I know they're not quite as public as standard Android. At least that is the take I have gotten over the past few years.
Hopefully it's something that won't require some sort of specific hardware. Best of luck! I hope to test this out on my Pi 3 in a few weeks myself. I'll be sure to keep tabs on the project!
I promise I'm not one of those XDA ETA/update zombies.

Woohoo!! Thank you for this effort!
I'm curious which hardware, aside from the Pi, has been used successfully so far? Is that the Raspberry Pi Foundation touch display? Any HATs?
Thanks again!
-Chad

MasterCLC said:
Woohoo!! Thank you for this effort!
I'm curious which hardware, aside from the Pi, has been used successfully so far? Is that the Raspberry Pi Foundation touch display? Any HATs?
Thanks again!
-Chad
Click to expand...
Click to collapse
Only Raspberry PI 3 has been tested so far in case of embedded platforms. Code itself is portable for any Linux-based or Windows platforms. If hardware acceleration of video decoding is supported by underlying backend used in Qt multimedia library (GStreamer for Linux and DirectShow for Windows) then OpenAuto will run smoothly without additional effort. If hardware acceleration is not supported by underlying backends then it must be implemented in OpenAuto (like in case of Raspberry PI 3).

I apologize, I meant in addition to the Pi, not alternative platforms. Things like which screen is it that you've used, any HATs on your Pi, etc. ?
Thank you!

MasterCLC said:
I apologize, I meant in addition to the Pi, not alternative platforms. Things like which screen is it that you've used, any HATs on your Pi, etc. ?
Thank you!
Click to expand...
Click to collapse
Screen is the official one from PI Foundation (7''). Basically any screen should be suitable to run OpenAuto (as long as it is supported by the OS that hosts OpenAuto). The same for other hardware.

Dude! You're my hero, I've been playing around with so many ways to get this working, yours seems to be the perfect solution, I'll take it for a test drive tomorrow