Related
As announced, JB 4.2 will support miracast which allows display mirroring through wifi-direct. I don´t understand whether this feature require certain hardware, and my question is wheter this will work on my 16 GB Nexus 7 when it is updated to 4.2? Anyone know?
Tegra 3 supports it and it uses wifi direct so I'm confident it will be supported.
Sent from my XT910 using Tapatalk 2
I hope that's true. All the hardware indicates it is able to support it, but not necessarily that it will actually be made available. The Nexus 10 doesn't have the option for Miracast, despite having WiFi direct/Android 4.2.
I don't get what all the worry about will it support it. The only hardware thing necessary is does the device have hardware encoding, and this does. Yes the N7 has wifi direct but ANY device could be upgraded to support wifi direct. It's not like wifi direct is some additional hardware on a wifi chip. Any wifi could technically support wifi direct.
So I would be really surprised if this doesn't support miracast. From what I've read the hardware encoder has a big influence on latency (as does the cpu). So one question that I would like answered is, how low is the latency? Movies/browsing etc doesn't really matter, but for gaming.
Has any article mentioned how low the latency is with miracast? This will vary from device to device of course, but even knowing for one device might give a ballpark of what to expect with the n7
I can't believe miracast is not supported by the N10! Mind boggling...
Sent from my SAMSUNG-SGH-I727 using xda premium
yes I just read that. Does it not have hardware encoding? The nexus 4 definitely has miracast enabled but not the nexus 10?!
Where is written that N10 doesn't support Miracast? I watched android developers hangout on YouTube a few days ago and if I remember correctly then they told both N4 and N10 support it. When someone asked about N7 they first told no, but then said they don't know for sure. Unfortunately YouTube is down, so I can't double check that at the moment.
Here:
Miracast is the Wi-Fi Alliance's standard for wireless streaming of video, and its addition to Jelly Bean made us very excited -- Android finally has a response to AirPlay. Imagine our disappointment, then, upon learning that Miracast isn't supported in the Nexus 10, at least not yet. It is there in the Nexus 4, a perplexing state of affairs that Google wasn't able to give us much clarity on, but it does appear that this is not a hardware limitation, since all the communication takes place over WiFi. If Miracast isn't going to be software-enabled in every Android 4.2 device then we're struggling to see how it's actually part of the OS, and we're definitely feeling let down about its potential to improve the platform as a whole.
Click to expand...
Click to collapse
'
'http://www.engadget.com/2012/11/02/nexus-10-review/
It's not like the nexus 10 ships with 4.1.2. It comes with 4.2 but yet miracast is disabled?! But he's wrong about pointing out wifi as the potential hardware limitation. Everything has wifi (and could potentially support wifi direct as that is done in software) the hardware barrier is hardware encoding. Does anyone know the details of the chipset the nexus 10 has?
Interesting... Cnet review says it is supported, but they didn't have a dongle to test it.
I believe even the Verge/Google video said it is supported, but again, I can't check that either at the moment. Why is YouTube down when you need it the most?
Does anyone know if Miracast supports audio only? I know that it supports audio and video, but what happens if I want to connect it to my AV receiver and use it for audio only?
Edit: YouTube works again. http://www.youtube.com/watch?v=Z92fwFQntG8 at 56:30 they say that both devices have HDMI and Miracast.
I think the software in review devices wasn't final. Some N10 review devices didn't have user accounts either, but the final software clearly will have that, so I believe its the same case with Miracast.
Does anyone know if Miracast supports audio only? I know that it supports audio and video, but what happens if I want to connect it to my AV receiver and use it for audio only?
Turn off your display and you have audio only
Sent from my SAMSUNG-SGH-I727 using xda premium
WalkSoftly said:
Does anyone know if Miracast supports audio only? I know that it supports audio and video, but what happens if I want to connect it to my AV receiver and use it for audio only?
Turn off your display and you have audio only
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
That's what I want to do, but is it possible? Does the Netgear ptv3000 work if it's not connected to TV?
It is possible that it doesn't allow connections from android device if its not connected to TV. For example Nexus Q doesn't allow streaming YouTube to it if its not connected to TV.
I'm thinking it should bypass through the a/v receiver but I am simply speculating... it's going to be one of those things we will have to test with or a/v systems
Sent from my SAMSUNG-SGH-I727 using xda premium
I would buy and test it but I can't I can't find this product in any shop in Europe. And US shops that have it in stock don't ship to Europe.
I'm in the u.s. and I will buy it once the 4.2 update and miracast are official for the N7. Then, I will report back with my findings on how the netgear miracast box interacts with my a/v receiver.
I'm so pumped for this feature!
Sent from my Nexus 7 using xda premium
I never thought about audio only. One thing I hope is possible is to turn off the n7's screen but still stream. It's one thing if you are interacting with it, but say you are streaming a movie, why have the n7's screen on for 2 hrs? Or even a game where you are using a gamepad and you aren't touching the device at all.
I've wondered if that functionality is in the spec, but I doubt. The other thing I wonder about is how low the latency is for gaming.
I found a US store that has it in stock and ships internationally. Only bad news is that shipping costs more then the device :| I'm not sure I want to pay that much for it.
About games, I have no idea if the screen can be off when streaming, but I hope so. One interesting thing that was discussed in Google developers hangout was a api that let's app developers use the two screens (tablet and connected display) as separate displays. For example the game runs on TV while your android device has buttons or whatever else on display.
Saw this on Reddit:
http://www.reddit.com/r/Android/comments/1iwnvb/miracast_working_on_nexus_7_devices_link_to_dev/
http://www.youtube.com/watch?v=WMlTxTyoaOs
I was only mildly interested until I saw the note that he got it working both for receiving and sending.
If we can integrate this into our OUYAs (and it should be easier to do since Nexus 7 is somewhat similar hardware), then we won't need another box to receive Miracast streams!
I will try and port it, but not sure when I'll get around to it. Posting it here in case some dev wants to take a crack at it sooner!
Also if anyone can verify that this will/will not work, please do! Getting the OUYA to receive screen-mirroring of some sort has been on my wishlist since I first ordered it.
EDIT: Knew there had to be a catch I wasn't thinking of... The Miracast stuff linked is working with Android 4.2, whereas OUYA is 4.1, so that would probably be the main hurdle -either getting OUYA up to 4.2 or backporting Miracast+patches to 4.1. Not sure how difficult either would be.
EDIT2: OUYA's weak wifi would probably also be a problem, would probably work better to rework the streaming to work as long as you're on the same router.
~Troop
What about the Chromecast device? I'm really not understanding the goal here.
Basically sending video from a device, to the Ouya, to pass through to the TV?
Sent from Nexus 7 FHD from XDA Premium HD
Yes it's all about mirroring the screen output of your phone via ouya to the TV. What's the point? Mostly displaying content without having to transfer it to the ouya.
Oh and chromecast doesn't support miracast.
Gesendet von meinem HTC One X+ mit Tapatalk 4 Beta
nchantmnt said:
Yes it's all about mirroring the screen output of your phone via ouya to the TV. What's the point? Mostly displaying content without having to transfer it to the ouya.
Oh and chromecast doesn't support miracast.
Gesendet von meinem HTC One X+ mit Tapatalk 4 Beta
Click to expand...
Click to collapse
Chromecast is kinda a letdown imo without full on mirroring.
its all about knocking off the apple tv up in this thread.
player911 said:
What about the Chromecast device? I'm really not understanding the goal here.
Basically sending video from a device, to the Ouya, to pass through to the TV?
Click to expand...
Click to collapse
Yeah, I posted all this before I heard about Chromecast.... believe me, I jumped on that boat quickly!
I already got my Netflix promo code and my chromecast should arrive by Wednesday and I have great hopes for it, but yeah, it won't do full-on mirroring. True mirroring isn't really needed in most use cases though, but it is handy in a few.
~Troop
Trooper_Max said:
Yeah, I posted all this before I heard about Chromecast.... believe me, I jumped on that boat quickly!
I already got my Netflix promo code and my chromecast should arrive by Wednesday and I have great hopes for it, but yeah, it won't do full-on mirroring. True mirroring isn't really needed in most use cases though, but it is handy in a few.
~Troop
Click to expand...
Click to collapse
If Chromecast could do full on mirroring we woudn´t even need a Ouya anymore.
At first this didn't make sense to me, ouya as a miracast receiver to stream from your nexus 7 while the ouya is already hooked up to the tv via hdmi?! But when I think about it, this could make the ouya perform double-duty as a small miracast dongle/receiver. I was looking to buy a miracast receiver but if the ouya could do this, then I would probably buy this as my miracast receiver to boot. I guess if you had a video or somethng on your nexus 7 and didn't want to bother sending the file over to your ouya, you could just miracast it.
Personally, I think if the hardware is capable of it, why not? meaning why isn't miracast enabled in all devices by now? Last year they were saying the n7 (and the n10) couldn't do miracast, well this guy proved it can, and the n10 officially has support as of 4.3.
But here's the bad news: I was reading that guys blog who made miracast work for the n7 and the sink mode (acting as a receiver) has been stripped out of android 4.3. Why google did that I don't know.
I commented on it here:
http://forum.xda-developers.com/showpost.php?p=44124359&postcount=7
His site mentioning it is here:
https://github.com/kensuke/How-to-Miracast-on-AOSP/wiki/Android-4.3
I'm still surprised so much time has past and none of the rom devs were trying to implement miracast in their roms for the n7.
I hope the source from 4.2.2 (last source with sink code) can be brought forward to 4.3, but that probably makes this all the harder. But I'd be interested to hear why google removed that functionality.
it's also a neat feature to be able to miracast device to device, for say showing someone how to do something, share a video etc. I guess google never advertised the n4 as capable of being a receiver?
You need to research miracast more. it's a failure, there is a delay which makes trying to play a game useless. unless your playing checkers or watching a movie. Miracast is useless , it's why devs don't bother with it. Chromecast uses a google tv port to do the heavy lifting. get a Bluetooth mouse and keyboard and a Bluetooth controller. link them to your nexus 7 (2013) with hdmi out and you have a ouya on steroids.
kpa2727 said:
You need to research miracast more. it's a failure, there is a delay which makes trying to play a game useless. unless your playing checkers or watching a movie. Miracast is useless , it's why devs don't bother with it. Chromecast uses a google tv port to do the heavy lifting. get a Bluetooth mouse and keyboard and a Bluetooth controller. link them to your nexus 7 (2013) with hdmi out and you have a ouya on steroids.
Click to expand...
Click to collapse
Hmm, well this video with the work being done for nexus 7 looks pretty smooth. Yes, a little latency, but for a 3d game that's working pretty good. Especially on a n7 which supposedly couldn't do it.
I read one comment on it being a failure but I couldn't find any comments on any dev here attempting to implement it in their rom. Maybe there are some things to work out, but it's still getting a big push. LG has announced about 70 tv sets with built-in miracast and mircosoft has it in windows 8.1. So I wouldn't give up on it yet.
http://www.youtube.com/watch?v=20s567tzTdM&feature=player_detailpage&t=316
If I can get the performance as in the video above, I'll be a happy camper.
Did anyone watch the google event just now? What do you think about their new "Q"?
My thouhts;
The positive - great seamless connectivity between all platforms and the price ($35!)
The negative - I kinda like the way to have something "beautiful" (like the Nexus Q was) on top of my receiver in the living room. This whole thing with a hidden tiny HDMI-dongle is just not my cup of tea. I'm also a bit concerned about the sound quality through that tiny thing when streaming Google Music for example. One thing I liked about the Nexus Q was that it really had *great* output audio quality through the HDMI to my receiver.
Another thing I did not like at all is that they still keep bashing us that don't use google play to see our movies. I have most of my movies on my computer in MKV and I want to be able to stream them! This is again where airplay from apple is ahead of google...
What do you guys think?
Btw, is there ANY chance what-so-ever that the new stream button in youtube/google music will have compability with the Nexus Q?
I bought one just because of the price and portability !
I REALLY REALLY REALLY hope the new buttons work with the Q though. I liked having it as a jukebox on my mantle.
the lights are beautiful!
Volatyle said:
My thouhts;
The positive - great seamless connectivity between all platforms and the price ($35!)
The negative - I kinda like the way to have something "beautiful" (like the Nexus Q was) on top of my receiver in the living room. This whole thing with a hidden tiny HDMI-dongle is just not my cup of tea. I'm also a bit concerned about the sound quality through that tiny thing when streaming Google Music for example. One thing I liked about the Nexus Q was that it really had *great* output audio quality through the HDMI to my receiver.
Another thing I did not like at all is that they still keep bashing us that don't use google play to see our movies. I have most of my movies on my computer in MKV and I want to be able to stream them! This is again where airplay from apple is ahead of google...
What do you guys think?
Btw, is there ANY chance what-so-ever that the new stream button in youtube/google music will have compability with the Nexus Q?
Click to expand...
Click to collapse
one can hope. or just keep using the old apps.
Nexus Q
Wish it had an option like the banana jacks for speakers like the nexus Q does.
Since they released a chrome cast SDK maybe someone at XDA will be able to implement support for chromecast in the nexus Q?
Sent from my Nexus 10 using Tapatalk HD
Volatyle said:
Since they released a chrome cast SDK maybe someone at XDA will be able to implement support for chromecast in the nexus Q?
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
I am hoping for the same thing.....if there are even Devs left....
Or, since we have the parts we need (HAL drivers etc) to make a chromecast rom?
I hope that the chromecast can get ported over i would hate to just toss my balls away they are very cool looking.
Sent from my Nexus 4 using xda app-developers app
Okay, so now google says they're adding chromecast compability with Google TV - which RUNS ANDROID. Just like the Nexus Q does.
Even more hope!!!
Vol
when I get home I'll try the app to see if it'll "map" to the Q. Yesterday it was trying to connect to the bluetooth stereo in my car.
Plan B is putting an amp in where I have my Q now and working via the audio out from the TV
rmm989 said:
when I get home I'll try the app to see if it'll "map" to the Q. Yesterday it was trying to connect to the bluetooth stereo in my car.
Plan B is putting an amp in where I have my Q now and working via the audio out from the TV
Click to expand...
Click to collapse
I am using the Sonos AMP where my Q was so I still can connect HTMI on my TV to my speakers. Now adding the Chromecast to the TV I should now have a Q replacement.
My thoughts on the Chromecast compared to the Q:
I just got my 2 chromecasts in today and I wanted to share my experience.
It can do all the basic functionality the Q could and more, but there are a few things the Q did better regarding play music.
With the Q one could start music from one device, then pick up another and "now playing" would be synced. This isn't the case with chromecast. Same thing goes the the queue, It isn't synced either, which is odd because I thought I read that others could join in and add to the queue. I always loved this feature with the Q because I could start music in one room with my phone and later control it with my tablet in another room. Plus, my wife would always like to put her songs in on the playlist as well. I also had issues with connecting a second device and the music would just stop. Perhaps future updates with fix some of these bugs.
If you have any other questions, I'll be glad to answer them!
El Daddy said:
My thoughts on the Chromecast compared to the Q:
I just got my 2 chromecasts in today and I wanted to share my experience.
It can do all the basic functionality the Q could and more, but there are a few things the Q did better regarding play music.
With the Q one could start music from one device, then pick up another and "now playing" would be synced. This isn't the case with chromecast. Same thing goes the the queue, It isn't synced either, which is odd because I thought I read that others could join in and add to the queue. I always loved this feature with the Q because I could start music in one room with my phone and later control it with my tablet in another room. Plus, my wife would always like to put her songs in on the playlist as well. I also had issues with connecting a second device and the music would just stop. Perhaps future updates with fix some of these bugs.
If you have any other questions, I'll be glad to answer them!
Click to expand...
Click to collapse
Thanks for the feedback. Now we're just waiting for the Q to get chromecast ability
Sent from my Nexus 10 using Tapatalk HD
Hey Guys,
Saw over at this thread http://forum.xda-developers.com/hardware-hacking/chromecast/apk-adt-1-cast-receiver-leanback-t2814210 That to the Google Cast Receiver apk has been ripped from the ADT-1. Wont be long until someone works how to port this to the OUYA
Rob,
Hum
I've been using CheapCast with varying levels of success.
I personally can't wait to see if devs can rip apart the new Nexus Player "Android TV" OS.
If it's portable, that'll be sweet.
I keep going on and off with this thing on ROM'ing it but one thing has sort of made me decide to jump yes if there is an android 10 ROM out there. I love using ps4 remote play in my house. Right now I use my pixel 2 but Id love to use a larger screen. With my pixel c dead I have either this or my nexus 9 (which prob couldnt handle remote play anyway) to try and run a rom to see if I can connect the dual shock to the tablet as well. Remote play will work on anything above 5 but in order to use your dual shock instead of touch controls (yuck) you need android 10.
Is there a 10 based ROM or is this tablet just too old to have it?
Anyone know if it would work? (what Im looking to do)
Thanks
I don't think so, we only have an unofficial, and apparently on development halt LOS 16. It would be nice if we had a recent official build, then it could be picked up automatically by the microG fork.
Meanwhile the little brother Galaxy Note 3 has been on proper LOS 16 development, and there is an unofficial LOS 17, and two other roms (crDroid and Havoc OS) based on that.
The Note 10.1 is a really good device, the last one with stylus, before the stylus was reintroduced. And it's still kicking!