Hi,
while configuring my Nexus 4 I noticed the "Wireless Display" possibility and did a little research.
Are there already receivers to buy?
BTW: Does the nexus Q support this and can act as a receiver? I want to buy one anyways when it becomes available.
Gesendet von meinem Nexus 4
Hello, as far as I know there are currently no receivers that can connect to the Nexus 4.
A lot of these devices that are out there (such as ones that support Intel's WiDi) can have their firmware upgraded and may eventually support the Nexus 4. After an update, my Nexus 4 is able to recognize my D-Link Mainstage but not connect to it. Intel WiDi 3.5 is supposed to be compatible with Miracast. Oh well, maybe I have to wait for 3.6
This was announced almost a year ago and has become such a clusterf**k, I'll be surprised if we ever see it (much like the Nexus Q, Nexus 7 dock, and Nexus 4 wireless charger, well... you get the idea). Thankfully, I don't have a need for it at this point. If I did, I'd have gone to an Apple device. Theirs has been working for years.
Related
In articles released today, Nvidia said the Tegra 3 chipset will support miracast (an open streaming tech similar to DLNA) for mirroing/streaming to other devices/ monitors. Will the Nexus support this and would this be their workaround for forgoing the MHL/HDMI? Or would it only be on future models? -Ara
Sent from my SAMSUNG-SGH-I927 using xda app-developers app
AraDreamer said:
In articles released today, Nvidia said the Tegra 3 chipset will support miracast (an open streaming tech similar to DLNA) for mirroing/streaming to other devices/ monitors. Will the Nexus support this and would this be their workaround for forgoing the MHL/HDMI? Or would it only be on future models? -Ara
Sent from my SAMSUNG-SGH-I927 using xda app-developers app
Click to expand...
Click to collapse
I'm very curious about this too.
I've looked into this briefly and from what I gather, any device that supports WIFI direct should be able to do this. I think I read somewhere that the N7 has wifi direct. Miracast is only a standard. There are other non-standard devices out there that can also do the same thing, but requires changes to the core android files.
Search for xbounds on youtube and the internet. You will see some demos of it. it requires an hdmi dongle that has wifi on it that communicates with your device.
In any event, if the N7 doesn't support miracast, it will support xbounds via a custom ROM (if and when somebody decides to build a custom ROM with xbounds integrated). Then all that is required is the xbounds dongle. Unfortunately, there is not much information on xbounds and when it will be released.
What would I need to purchase to get this working?
Hopefully, we don't need to buy stuff, we just need to update our devices when miracast comes down. There's a list of compatible devices on the Wi-Fi Alliance website. -Ara
EDIT: here's a link to the tegra explanation of miracast, taken from an article on the issue. Yeah, a dangle may be involved depending on the setup. http://www.nvidia.com/content/PDF/tegra_white_papers/tegra-miracast-whitepaper-final.pdf
Sent from my Nexus 7 using xda app-developers app
I've not found any hardware that you could plug into say an HTML Monitor that will work with this yet. I do think it will be coming available soon though.
hope so
I reckon it will work with a Nexus 7. Hopefully the dongle isn't too expensive and my Nexus 7 will be my new PSone.
Shouldn't need a dongle. Maybe a Raspberry Pi but everyone should have one of those anyway Search "Android Transporter" for more info.
Sent from my Nexus 7 using Tapatalk 2
Nexus Q might get Miracast support
Nexus 7 and most Tegra 3 (also Galaxy S3) phones/tablets can get a fw upgrade to enable miracast (most that support WIFI Direct probably can have Miracast enabled).
Now that google is having another round of tinkering on the Nexus Q before release we might end up with Miracast support in it as well.
Personaly I think Miracast will be added out of the box and maybee even Google TV.
I only hope that it won't be possible to disable mirroring from inside an app using the API, if so I'm sure some streaming services will disable mirroring of the screen while using there apps lika HBO Go have done to Airplay
mfucci said:
Shouldn't need a dongle. Maybe a Raspberry Pi but everyone should have one of those anyway Search "Android Transporter" for more info.
Click to expand...
Click to collapse
Using a Raspberry Pi would be like a dongle... I'd like to get my hands on one to play, currently, there is a 12 week delivery time on those as well and you most likely would want it in some sort of case for it as well.
While most likely a solution, not a real clean one for mass marketing. That will come though.
TwistedRat said:
Now that google is having another round of tinkering on the Nexus Q before release we might end up with Miracast support in it as well.
Click to expand...
Click to collapse
Hopefully it does include support, but that is still a bit pricey and also not very portable.
Think of something you put in your briefcase, take out for a meeting, plug into the HDMI port of whatever display is in the room and play. So it needs to be portable, reasonably priced and easy to use out of the box without a lot of fiddling with it.
widi and Miracast adapters
I am thinking that these will do what we need on the display side. Now to enable it on the Nexus 7.
Netgear announces Push2TV WiDi adapter and three new NeoTV units
engadget. com/2012/09/20/netgear-push2tv-neotv/#continued
krelvinaz said:
Using a Raspberry Pi would be like a dongle... I'd like to get my hands on one to play, currently, there is a 12 week delivery time on those as well and you most likely would want it in some sort of case for it as well.
While most likely a solution, not a real clean one for mass marketing. That will come though.
Hopefully it does include support, but that is still a bit pricey and also not very portable.
Think of something you put in your briefcase, take out for a meeting, plug into the HDMI port of whatever display is in the room and play. So it needs to be portable, reasonably priced and easy to use out of the box without a lot of fiddling with it.
Click to expand...
Click to collapse
Has anyone heard any updated news on miracast? I tried Google but all I found was old news. I'm really tired of waiting.
Does the device with android 4.2 need to have a special chip set to do the new wireless HDMI out? Also what is this adapter that I need? I can't find very much information on this, seems like I'm the only one excited about this...
Sent from my Galaxy Nexus
I would hold off on buying an adapter.It seems only the nexus 4 gets miracast from the 4.2 update.Maybe one day we will see it on the N7 but for now nobody has shown it working on anything.
James-NC said:
I would hold off on buying an adapter.It seems only the nexus 4 gets miracast from the 4.2 update.Maybe one day we will see it on the N7 but for now nobody has shown it working on anything.
Click to expand...
Click to collapse
Actually its been done using a Raspberry Pi
Hey guys,
has anybody experience with Miracast on the Nexus 10 or Android 4.2? I'm going to get an Adapter for my TV and I'm not sure how that works... haven't found any Miracast-related options in the settings app, and I don't know how the whole stuff with wifi is working (is the bandwidth of wifi high enough for that high resolution? How will the Nexus scale its 2650px down to the 1920 of my TV? ...).
Thanks
Currently nexus 10 is not miracast capable. Many people think it will be later, but since there might be bus bandwith issues i dont think it will.
Sent from my Nexus 10 using xda app-developers app
Check this thread out if you want to learn more: http://forum.xda-developers.com/showthread.php?t=1989513
Practical testing: Miracast with Nexus 10
There was quite of bit of discussion/speculation back on Nov-Dec on whether, how, and when Nexus 10 would support Miracast. I recently did some testing to support an app I'm developing, and wanted to: give an update on practical test results, and see if anyone has any further information (since none is forthcoming from google so far).
I tested Miracast links using Netgear's PTV3000 (Push2TV):
Samsung S3 - WORKS, after an upgrade to their latest PTV3000 firmware (v.2.2.9)
Google Nexus 10 - Does not work.
Google Galaxy Nexus - Does not work.
This is consistent with a recent posting on AndroidCentral ("Netgear PTV3000 gets a firmware update, now officially supports host of Android devices"). I'm interested in running on as many devices as possible, including the Nexus tablets and phones, but still can't find any information on plans and timing for Nexus 10, for example.
Anyone?
OK so I have been thinking about this for a while. I know the Samsung galaxy s3 and note 2 allow Bluetooth syncing. Can we try a build.prop rename for device name to spoof a galaxy s3 and see if the 4.0 can get any action? Anyone able to help me with this.
I have been in contact with Fitbit and they say the Bluetooth stack for hardware is different on each hardware. But I'm still wanting to get this working. Anyone able to assist? Fitbit one and nexus 4
Sent from my Nexus 4 using Tapatalk 2
iamdarren said:
OK so I have been thinking about this for a while. I know the Samsung galaxy s3 and note 2 allow Bluetooth syncing. Can we try a build.prop rename for device name to spoof a galaxy s3 and see if the 4.0 can get any action? Anyone able to help me with this.
I have been in contact with Fitbit and they say the Bluetooth stack for hardware is different on each hardware. But I'm still wanting to get this working. Anyone able to assist? Fitbit one and nexus 4
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
No.
Galaxy s4 is looking pretty good to me now. :-s
Sent from my Nexus 4 using Tapatalk 2
I have a Fitbit One and a Galaxy Nexus at the moment. I see the latest version will sync via Bluetooth with Samsung S3 and Note 2, but the comments on Google Play mention that it works with the Nexus 4 also. Can anyone confirm or deny this?
Sent from my Nexus 7 using Tapatalk HD
nigelw said:
I have a Fitbit One and a Galaxy Nexus at the moment. I see the latest version will sync via Bluetooth with Samsung S3 and Note 2, but the comments on Google Play mention that it works with the Nexus 4 also. Can anyone confirm or deny this?
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
I just bought a Fitbit One. I do not even see the One on my LG Nexus 4 V4.2.2 using the standard bluetooth control panel. Maybe there's a radio diag util that'll let me see it. Android Fitbit V1.6.1 software does not offer the option to sync on my LG Nexus 4. The LG Nexus 4 DOES have Bluetooth v4.0 hardware doesn't it?
I have an SMK Link V4 LE USB Bluetooth dongle on my netbook that, after downloading the god awful 400 megabyte driver from their website, does show the Fitbit One bluetooth but the Netbook refuses to attach to the Fitbit One. The Win 7 bluetooth control panel times out. It says I never entered the number (presumably on the FitBit One). I never saw any prompt to enter the four digit code on the PC or the Fitbit One.
Fitbit.com/store shows a $14.95 wireless dongle so I can sync at work & home but I'm hesitant to buy it given support for more Android phones are "coming soon". I wish they'd communicate their plans, schedules & devices better.
John
---------- Post added at 01:47 PM ---------- Previous post was at 01:14 PM ----------
jzoch said:
I just bought a Fitbit One. I do not even see the One on my LG Nexus 4 V4.2.2 using the standard bluetooth control panel. Maybe there's a radio diag util that'll let me see it. Android Fitbit V1.6.1 software does not offer the option to sync on my LG Nexus 4. The LG Nexus 4 DOES have Bluetooth v4.0 hardware doesn't it?
I have an SMK Link V4 LE USB Bluetooth dongle on my netbook that, after downloading the god awful 400 megabyte driver from their website, does show the Fitbit One bluetooth but the Netbook refuses to attach to the Fitbit One. The Win 7 bluetooth control panel times out. It says I never entered the number (presumably on the FitBit One). I never saw any prompt to enter the four digit code on the PC or the Fitbit One.
Fitbit.com/store shows a $14.95 wireless dongle so I can sync at work & home but I'm hesitant to buy it given support for more Android phones are "coming soon". I wish they'd communicate their plans, schedules & devices better.
John
Click to expand...
Click to collapse
I just stumbled upon this:
URL deleted because I'm a noob.
Finally! Wireless Sync (beta) on Android!
2013 February 12
by lking
We’re excited to announce that wireless syncing with Android has arrived! Our free Fitbit App for Android now syncs your Fitbit One and Zip stats directly to the Samsung Galaxy SIII and Note II. With our app, you can sync your stats wirelessly (beta) and see how you are tracking against your daily goals, with friends, and against historic averages. You can download the app from Google Play today!
Android dashboard
Android dashboard
We know how important it is for our customers to get real-time access to their stats. Those who’ve been able to take advantage of wireless background syncing already have been telling us how they’ve worked to get their extra steps in after receiving notifications that they’re close to their goal, or how they find motivation from the instant feedback right on their Dashboard. We are very excited to bring this feature to our Android users!
We began working on the wireless sync for Android and iOS at around the same time. It took us much longer to get this working on Android phones than it did with iOS, and we appreciate our Android users’ patience in the meantime. We know many of you may be curious about the development of this feature, and we’d like to share some insight into some of the challenges we’ve encountered and what they’ve taught us in the process.
Currently, the Android OS does not provide apps with access to the Bluetooth 4.0 chips in newer phones. To work around this, some phones instead have custom software that provides access to Bluetooth 4.0. Since this software is different for each phone, our team has worked on developing a solution for each phone independently.
Fitbit is among the first to try and use the Bluetooth 4.0 in Android phones, and part of being the first means we got to help find and document any problems with the software. We also spent quite a bit of time piecing together how the software works, since it previously hadn’t been well-documented. For many of the problems we encountered, we were able to create our own work-arounds. For others, we coordinated with phone manufacturers and carriers to get more permanent fixes in place.
For phones we have yet to introduce syncing capabilities with, we’re working with phone manufacturers to see which phones will allow our app to work with their Bluetooth 4.0 capabilities. This process involves us individually checking each model of phone. There may be better support for third-party apps to access Bluetooth in the future, and once this is available we will be able to easily support all phones with this update.
We’ve been working hard to improve the wireless sync experience, but the feature is still in beta. Syncing your stats will typically take about 30 seconds. In some cases, especially where there are issues with network connection, it may take longer. We’re working hard to provide the best user experience possible, so improved syncing speed is just one thing you can look forward to seeing in future updates of our Android app.
Fitbit is dedicated to making connected devices that fit seamlessly into your everyday life, and we fully believe that incorporating Android phones in all of our future efforts is a huge part of that. We truly appreciate our Android users’ patience as we continue to work on supporting additional mobile devices. We’re closely collaborating with phone carriers and handset manufacturers to try to support more phones. There’s a number of phones we’re actively working on, but we don’t yet have an ETA on when we might be able to release updates to include them. For now, you can see a list of all of the supported devices here. If your device is not on that list, we encourage you to contact your phone carrier to ask that they work to build out further Bluetooth support. Your feedback could help us speed this process along!
Happy syncing and logging — wherever you go!
–The Fitbit team
Seems the problem is Google have not fully implemented Bluetooth 4.0 support, but Samsung for all their faults, have. Maybe we will get lucky with the next release of Android, Google IO is 2 weeks away.
Was really thinking about a Fitbit Flex but good thing I looked up wireless syncing.
bleuiko said:
Was really thinking about a Fitbit Flex but good thing I looked up wireless syncing.
Click to expand...
Click to collapse
All Fitbit devices have wireless sync via the included bluetooth dongle. Real time active-sync via a Bluetooth 4.0 connection to your smartphone is what you are referring to..
G1ForFun said:
All Fitbit devices have wireless sync via the included bluetooth dongle. Real time active-sync via a Bluetooth 4.0 connection to your smartphone is what you are referring to..
Click to expand...
Click to collapse
Yup. As this is a Nexus 4 forum, I figured the distinction was obvious. Thanks for making it clear. Fingers cross for some BT4 announcement at IO.
So I have been reading reviews for the flex and one of them mentioned NFC syncing to mobile devices although the fitbit website doesn't seem to spec this feature..... Was this just a deranged reviewer??
edit: Another review explains the following
"Even if your phone isn't one of the currently compatible models (the Galaxy S III, S4 and Note II), the inclusion of NFC lets you quickly launch the app with a tap, though there will be no ability to sync."
Ruprect said:
So I have been reading reviews for the flex and one of them mentioned NFC syncing to mobile devices although the fitbit website doesn't seem to spec this feature..... Was this just a deranged reviewer??
edit: Another review explains the following
"Even if your phone isn't one of the currently compatible models (the Galaxy S III, S4 and Note II), the inclusion of NFC lets you quickly launch the app with a tap, though there will be no ability to sync."
Click to expand...
Click to collapse
No, that's true. It just opens up the app but doesn't sync. I hate going back to TW. Mann.
ok im going to put this out there, but why do you need to sync your fitbit with your phone at all, i use my fitbit all day long and as long as i walk within 20 feet of my pc at home with the fitbit usb adapter and software on it my fitbit syncs so does my wifes, when she gets home from work walks in front door boom sync'd i have never had to open the app to sync my fitbit manually and never seen the need to sync to app being their are indicators on all fitbits saying where you stand on activity.
You only need mobile sync if you're away from your home pc for more than 5 days.
Sent from my Nexus 7 using Tapatalk HD
nigelw said:
You only need mobile sync if you're away from your home pc for more than 5 days.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
oh ok ty that would be why i never thought i needed it even when i got on vacation i bring my netbook which is where it syncs.
I only have a Nexus 7 and a desktop PC, so a mobile sync will be useful when I'm away on holiday.
Sent from my Nexus 7 using Tapatalk HD
m3f2u said:
No, that's true. It just opens up the app but doesn't sync. I hate going back to TW. Mann.
Click to expand...
Click to collapse
I got no reaction after tap the flex by my nexus 4. Yes, the NFC is on
billsky83 said:
I got no reaction after tap the flex by my nexus 4. Yes, the NFC is on
Click to expand...
Click to collapse
its quirky, sometimes i have to make my phone have sex with my fitbit to get it launch the app thats all the nfc feature does. its 90% of the time faster to just open the app with my finger then nfc, but its not nearly as cool as fitbit/phone sex
I have a Fitbit Flex and have looked into this. Apparently mobile syncing requires BLE (Bluetooth Low Energy) which our phones don't have. However, they are capable of it and BLE is one of the rumored additions for Android 4.3.
Personally I hate having to take my dongle back and forth between home and work so I'm looking forward to being able to sync on my phone.
bringing this thread back up. I know that we have BLE now in 4.3 but fitbit has not updated the app yet. Anyway we can spoof the app in Build.prop maybe to make it work?
Pretty sure that the app needs to be coded for the nexus 4 BLE driver first...
Hello all, my first post here.
Recently jumped into the Nexus 7 game with both feet and bought first a 2012 Nexus 7 then almost immediately a 2013 Nexus 7. After playing with both a bit I opted to buy yet another Nexus 7 but my purchase of choice the 3rd time around was another 2012 Nexus 7.
While on paper the specs for the 2013 Nexus 7 are sweet and it is no doubt a fantastic tablet my needs seem to be more suited to the 2012 based on the following conditions, (which I'm aware could change with hacks and kernel updates).
First of all I have USBROM installed on both my 2012 Nexus 7's. It allows me to connect a DAC to my Nexus and also an OTG Y cable which I can simultaneously charge. I have found with the latest CyanogenMod 10.2 nightlies for the 2013 Nexus 7 I can also connect a DAC but I cannot charge at the same time.
I use Logitech Media Server to stream music to my Nexus 7 and having a wonderful touch screen that won't go off during use is fantastic. It replaced a Raspberry Pi running Squeezeplug. More user friendly for the family but of course more expensive.
Another reason I'm a fan of the 2012 is because I can connect a USB 3G dongle to it using PPPWidget. I have an unlocked Huawei E303 and travel extensively. Being able to hook a dongle up to my Nexus will be invaluable when I'm working on some foreign runway with no wifi and not data roaming on my cell phone.
Nexus 7 flo seems to have kernel module loading disabled.
Anyway in my opinion the newer Nexus 7 is somewhat crippled compared to its older brother. That being said I use my 2013 Nexus 7 religiously and constantly as the others seem to have taken up duties as stereo sources at work and at home. However when I travel I leave the new Nexus 7 at home.
Anyway, just an observation and an introduction. As I said I'm aware one good kernel makes the older Nexus 7 almost obsolete but I'm living in the here and now.
John Hagensieker
MCAS Iwakuni Japan
hagensieker said:
Hello all, my first post here.
Recently jumped into the Nexus 7 game with both feet and bought first a 2012 Nexus 7 then almost immediately a 2013 Nexus 7. After playing with both a bit I opted to buy yet another Nexus 7 but my purchase of choice the 3rd time around was another 2012 Nexus 7.
While on paper the specs for the 2013 Nexus 7 are sweet and it is no doubt a fantastic tablet my needs seem to be more suited to the 2012 based on the following conditions, (which I'm aware could change with hacks and kernel updates).
First of all I have USBROM installed on both my 2012 Nexus 7's. It allows me to connect a DAC to my Nexus and also an OTG Y cable which I can simultaneously charge. I have found with the latest CyanogenMod 10.2 nightlies for the 2013 Nexus 7 I can also connect a DAC but I cannot charge at the same time.
I use Logitech Media Server to stream music to my Nexus 7 and having a wonderful touch screen that won't go off during use is fantastic. It replaced a Raspberry Pi running Squeezeplug. More user friendly for the family but of course more expensive.
Another reason I'm a fan of the 2012 is because I can connect a USB 3G dongle to it using PPPWidget. I have an unlocked Huawei E303 and travel extensively. Being able to hook a dongle up to my Nexus will be invaluable when I'm working on some foreign runway with no wifi and not data roaming on my cell phone.
Nexus 7 flo seems to have kernel module loading disabled.
Anyway in my opinion the newer Nexus 7 is somewhat crippled compared to its older brother. That being said I use my 2013 Nexus 7 religiously and constantly as the others seem to have taken up duties as stereo sources at work and at home. However when I travel I leave the new Nexus 7 at home.
Anyway, just an observation and an introduction. As I said I'm aware one good kernel makes the older Nexus 7 almost obsolete but I'm living in the here and now.
John Hagensieker
MCAS Iwakuni Japan
Click to expand...
Click to collapse
There are custom kernels that have module loading enabled on the 2013 nexus.
Sent from my Nexus 7 using XDA Premium 4 mobile app
blackhand1001 said:
There are custom kernels that have module loading enabled on the 2013 nexus.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Could you point me to one please. I have searched and been unable to find. I have tried ElementalX, franco, Bulletproof, among others.
Thanks,
John
hagensieker said:
Could you point me to one please. I have searched and been unable to find. I have tried ElementalX, franco, Bulletproof, among others.
Thanks,
John
Click to expand...
Click to collapse
Try CM Mod
wait why u bought 3 nexus 7 tablets?