All I keep hearing about this wrt JellyBean 4.2 and phones is that it's "not quite there yet". Why does this open standard seem so closed walled? I can understand that they would want to do closed trial runs with certain devs and manufacturers first, but at this point there is no SDK or API or even example code to look at for how to implement the wireless display tech, just Wifi Direct demos and libraries that have to do with file transfer and such. If there was more to work with the guys at xda or other developers would have had this running months ago. Things like the Android Transporter have been hacked together but that is fairly unusable in its current state for phones. I've also yet to hear anything about application development in the x86 PC world. Miracast dongles and Wifi Direct TVs have been around for awhile now, the lack of software support is extremely disappointing.
I wouldn't be surprised if it has to do with the overhead from doing real-time H.264 compression. A low power ARM just isnt going to cut it, you will need a dedicated IP block to do the H.264 encoding.
Hopefully we'll see more NFC interactivity between operating systems next year. I'd like to see NFC on Android, Windows Phone, Windows 8, and other embedded systems all place nice with each other.
I'm looking forward to see more miracast dongles offer at the beginning of 2013. I am so ready to buy one to mirror my Nexus 7's screen onto my HDTV. Just release them already for <$100 :)
Honestly, the idea that you don't have *some* smarter device on the other end is disturbing. Just make Google TV sync up with whatever Android device is connected (and in the process, force Google TV and phones to stay up to date to support that connectivity. TWO BIRDS DOWN!). And make a PS3 app, and maybe even an XBox 360 app. There, half of America supports your wireless display system.
But it truly is a technology that is a solution in search of a problem. Perhaps Broadcom adding this to a combo chip will help smartphone developers to add without incurring significant cost increases.
I think the main issue is that everything NFC does can also be done with other technologies like Bluetooth. It has no killer feature where they can proclaim "no one else does this but us"
We’ve updated our terms. By continuing to use the site and/or by logging into your account, you agree to the Site’s updated Terms of Use and Privacy Policy.
8 Comments
Back to Article
SilentSin - Thursday, December 13, 2012 - link
All I keep hearing about this wrt JellyBean 4.2 and phones is that it's "not quite there yet". Why does this open standard seem so closed walled? I can understand that they would want to do closed trial runs with certain devs and manufacturers first, but at this point there is no SDK or API or even example code to look at for how to implement the wireless display tech, just Wifi Direct demos and libraries that have to do with file transfer and such. If there was more to work with the guys at xda or other developers would have had this running months ago. Things like the Android Transporter have been hacked together but that is fairly unusable in its current state for phones. I've also yet to hear anything about application development in the x86 PC world. Miracast dongles and Wifi Direct TVs have been around for awhile now, the lack of software support is extremely disappointing.extide - Thursday, December 13, 2012 - link
I wouldn't be surprised if it has to do with the overhead from doing real-time H.264 compression. A low power ARM just isnt going to cut it, you will need a dedicated IP block to do the H.264 encoding.jeffkibuule - Thursday, December 13, 2012 - link
Hopefully we'll see more NFC interactivity between operating systems next year. I'd like to see NFC on Android, Windows Phone, Windows 8, and other embedded systems all place nice with each other.amdwilliam1985 - Friday, December 14, 2012 - link
I'm looking forward to see more miracast dongles offer at the beginning of 2013. I am so ready to buy one to mirror my Nexus 7's screen onto my HDTV. Just release them already for <$100 :)overzealot - Sunday, December 16, 2012 - link
You used the acronym NFC nearly 20 times, but didn't give the expansion of it.Had to Google to find out what the hell this article was about.
:(
lmcd - Monday, December 17, 2012 - link
I guess since it's been in a lot of cell-phone articles over the last year, but then again it usually isn't explained there either.lmcd - Monday, December 17, 2012 - link
Honestly, the idea that you don't have *some* smarter device on the other end is disturbing. Just make Google TV sync up with whatever Android device is connected (and in the process, force Google TV and phones to stay up to date to support that connectivity. TWO BIRDS DOWN!). And make a PS3 app, and maybe even an XBox 360 app. There, half of America supports your wireless display system.hmurchison - Monday, December 31, 2012 - link
But it truly is a technology that is a solution in search of a problem. Perhaps Broadcom adding this to a combo chip will help smartphone developers to add without incurring significant cost increases.I think the main issue is that everything NFC does can also be done with other technologies like Bluetooth. It has no killer feature where they can proclaim "no one else does this but us"
Fix that issue and you may have a chance.