Related
Many of the people who had been wondering why Google chose to go with the OMAP 4460 as the processor for the Galaxy Nexus have gotten yet another answer to that question. The Omap4 series of processors are compatible with wifi display. as of right now, besides the Omap4 family the Snapdragon S4 is the only mentioned to be getting wifi display. It looks as if the Tegra 3 isn't going to support it at all according to http://www.androidauthority.com/wifi-display-to-make-your-life-easier-in-2012-47153/ . At this time it looks as though the OMAP4 is going to be the only current gen chip that will support wifi display, and of course with us having a nexus device we will most likely be seeing that update before anybody.
http://androidandme.com/2012/01/new...ay-likely-powered-by-texas-instruments-omap4/
Thanks for sharing this. I hope this actually happens soon!
chino0131 said:
Thanks for sharing this. I hope this actually happens soon!
Click to expand...
Click to collapse
No problem. According to the androidandme article we're looking at a summer release. I am looking forward to this coming to our phones as I think it would be very useful for me. Often times I'll either connect a laptop to the TV or my cell phone and stream kid's shows from a particular site for my son. It would be very nice if I could do that without having to connect my phone directly to the television like I've been doing. I could sit across the room on my computer while he watches his show and still have my phone right next to me. That would be nice.
Is this WiDi?
ushim6 said:
Is this WiDi?
Click to expand...
Click to collapse
From what I understand (and I could be wrong, so anyone correct me if I am) widi is an intel thing and it's for displaying your pc wirelessly to a television. Wifi display involves a "wifi direct" connection between two devices and is actually an emerging standard that the wifi alliance is backing. All in all I don't think it is the same thing was WiDi.
But we need tv that support this wifi display?
I don't have such tv.
Sent from my Galaxy Nexus using xda premium
gogol said:
But we need tv that support this wifi display?
I don't have such tv.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
That or just an adapter. Also, from my understanding it works with computers too, and any other wifi display capable device (not sure what other devices that would be).
mysterioustko said:
That or just an adapter. Also, from my understanding it works with computers too, and any other wifi display capable device (not sure what other devices that would be).
Click to expand...
Click to collapse
Maybe it will work better than WiFi Direct? Has anybody managed to figure this crap out?
Maybe hardware supports it, but I think we will need software to handle this. I'm not sure that there is a permission for app to handle access to wifi radio (and any other hardware needed for this), so it will have to be implemented in the OS...
This technology is much lower latency than Intel WiDi, and it's also not proprietary. WiDi is good only for video, whereas WiFi Display is quick enough to support real-time gaming. And as an open standard that's cheap to implement, you can expect it to kill WiDi in short order.
k_myk said:
Maybe it will work better than WiFi Direct? Has anybody managed to figure this crap out?
Maybe hardware supports it, but I think we will need software to handle this. I'm not sure that there is a permission for app to handle access to wifi radio (and any other hardware needed for this), so it will have to be implemented in the OS...
Click to expand...
Click to collapse
Connecting two wifi direct devices isn't too difficult. For example, connecting a galaxy s2 to a Galaxy Nexus works fairly easily. That being said, you are right that wifi display will have to be implemented on the OS level. From what I understand they expect an update to come from Google some time this summer that will implement the feature. We've got something to look forward to this summer lol.
Could the WiFi display work two ways, buy a small 10.1" WiFi display with touch screen, connect to the Galaxy Nexus - instant Nexus Tablet!
StuMcBill said:
Could the WiFi display work two ways, buy a small 10.1" WiFi display with touch screen, connect to the Galaxy Nexus - instant Nexus Tablet!
Click to expand...
Click to collapse
I was wondering the exact same thing! That would be great if that turns out to be possible. There seems to be several different possible applications for this. I'm excited to see what the community comes up with for this.
Something off the top of my head is: Having software installed on the computer to remotely control the phone. Create a nfc tag that starts up wifi display to your tv and launches the computer remote controls. When you place the phone on the tag you will instantly be able to control the phone via the computer and have it displayed on the television. That's just an idea that came to my mind.
This is why i got a nexus
Is there any word on when we might be receiving this?
What I want to know is when we will see the technology on the TV side. Google updating doesn't do much good until we have devices to pair with.
On another note, I'd have trouble justifying purchase of a toggle or $4000 flagship Sony TV exclusively for this functionality. I wonder if we will see this technology utilized in entry-level smart tvs or rokus, google tvs, and xboxes. This feature will really become useful when it is available on most any wifi-connected display around you.
kensingtn5 said:
What I want to know is when we will see the technology on the TV side. Google updating doesn't do much good until we have devices to pair with.
Click to expand...
Click to collapse
I'm just hoping for an adapter box that outputs HDMI.
Looks like the Galaxy SIII is going to beat us to it.
Can't wait to see the first demos of it. Perhaps it's like with iphone.
manore said:
Can't wait to see the first demos of it. Perhaps it's like with iphone.
Click to expand...
Click to collapse
The demos from Texas Instruments I saw looked more appealing than the iPhone's method to me. The latency is also suppose to be much lower. I'm excited, that was the one feature of the iOS ecosystem I was very jealous of.
This is somewhat OT, but Samsung is also releasing a set of cameras with built-in WiFi direct capability. Your phone basically becomes a remote control/viewfinder for the camera and you can control most of its functions. I love where this technology is going.
Never thought i would see Android like this haha
http://www.astina.dk/multimedie/autoradio-2din-android-wince-695-touch-med-alt-p-116659.html
Google translate (for the lazys): http://translate.google.com/transla...android-wince-695-touch-med-alt-p-116659.html
I looked into getting something like this but have you seen the price?
Nearly £700 i will wait til its half that
Sent from my cm_tenderloin using xda premium
tenchar
I have a unit very similar to this, but no android on it, mine is an older model, would I be able to instal Android On it.
Sent from my HTC One X using xda app-developers app
There is a guy that deals in an Android unit for Rover 75 and MG ZT with all the Chinese variants.
I however as mentioned plumped for the cheaper WinCE unit.
Sent from my HTC One X using xda premium
Just shove a Nexus 7 in the gap, 3.5ml to phono to your amp, 12v micro USB car adaptor, problem solved xD
Great now a non stable car stereo that crashed every 2 minutes... just what i need on a long drive.
crsnwby said:
Great now a non stable car stereo that crashed every 2 minutes... just what i need on a long drive.
Click to expand...
Click to collapse
Go buy a iphone if you're too rookie for Android.
Sent from my HTC One X using xda app-developers app
WebghostDK said:
Never thought i would see Android like this haha
http://www.astina.dk/multimedie/autoradio-2din-android-wince-695-touch-med-alt-p-116659.html
Google translate (for the lazys): http://translate.google.com/transla...android-wince-695-touch-med-alt-p-116659.html
Click to expand...
Click to collapse
Gasps I cant wait to S-off my radio and load a faux kernel.
Sent from my HTC One X using xda premium
Hmmm, why does it have sense in one of the pics?
Edit: oops, just zoomed in, not sense at all.
http://forum.xda-developers.com/showthread.php?t=1819175
This is a real android car radio and a hell of a lot cheaper
stezo2k said:
http://forum.xda-developers.com/showthread.php?t=1819175
This is a real android car radio and a hell of a lot cheaper
Click to expand...
Click to collapse
Yup cheaper, but you got a problem there. No remote for the buttons on the steering wheel. When used to those, its hard to get rid of
And the sound output is much worse compared.
Sent from my HTC One X using xda app-developers app
Android 2.2 6,5" CAR Device
There is an Android 2.2 800Mhz 256MB 8GB 6,2" TFT CAR DVD on sale (800 USD to door in Russia) that I have bought recently and after some software installations it does deliver what I have wanted to have in the car.
Nevertheless there are a few major complaints to its performance: http://www.youtube.com/watch?v=cx53a6N7_ws
As well there are several other minor things that would be great to change if possible.
If there is someone interested and able to cook a custom ROM for this device - I can send this device for free as a gift and for experiments. We really want a good ROM for this CA-Fi Car Stereo and the guy's in China don't seem caring enough.
I will check this thread once in a while and provide contact details for anyone interested in developing this device. It is very close to being a great thing for a CAR!
I have updated my email in the XDA profile so you can as well use this option to contact me.
PS
I Have a ROM update file (192MB) that came from the device vendor (dealer). I can send it out for revision.
The way to install this rom on the car stereo is to extract files to the root of a microSD card, insert it, switch off the device, then, while holding the screen tapped, power on – the device starts an install mode. When finished it asks for screen calibration and restarts with a new rom as after a hard reset (erases everything).
And there is the Parrot as well.
i've gone down the route of car pc etc, it was running win 7.
to be honest, they're wayyy to much fuss and aggro.
the sound quality sucked, the screen was **** (it was cheap - £250 "cheap") and broke shortly after a year of having it.
a decent head unit, with either apt x bluetooth dongle plugged in, or just the 3.5mm with hox is much much better. sound quality is way better, and i don't have to put up with some slow 800mhz cpu when all i want is to be driving whilst listening to music
just a fyi for those considering, its a huge cost, for not actually that much benefit (unless you live in your car)
CA-Fi Android Car Radio
I understand you if you only need to have music playing while driving, as well as some people who still prefer using monochrome cell phones. This is a matter of needs.
Regarding the sound quality of this particular CA-Fi device its surprisingly fine. I use its 4x45W out lines conneted directly to car OEM speakers (its a Chrysler PT) and the subwoofer RCA out channel connected via a 1KW Kenwood amplifier to a large Polk Audio woofer. With the available in this device GEQ and Bass/Treble settings the unit provides perfectly sharp and clear sound in the high+mid ranges for the OEM speakers that in company with the powerful sub make a really impressive rich and clear sound scene with no distortion at any volume.
This sound setup is very easy and efficient. Honestly, to my hearing it is not lacking comparing to my previous JVC Mosfet 192/24 DAC car stereo that was routed through amplifiers for all channels to Focal speakers instead of the OEM... That was too much trouble for the gained advantage. Again, depending on the needs. Trully - the sound of this Android Radio is fine, a sound of a branded Hi-Fi car stereo.
And if you had a Win7 Car PC setup that is quite complicated to arrange you should agree that this easy one-box Android PC solution is a great idea. It provides the music and all the tablet PC advantages. It's really nice after switching on the ignition to hear from your car that you have a new e-mail arrived, and enjoy other goodies like that.
---------- Post added at 08:42 PM ---------- Previous post was at 08:23 PM ----------
leppie said:
And there is the Parrot as well.
Click to expand...
Click to collapse
yes, I considered the Parrot, but found it limited for modifications and with a too small screen. There is as well a Clarion at present under development, but it does not appeal to me neither. It is a concept from the Clarion Malaysia division and most likely will be limited for modifications; if it will ever be released at all:
http://www.youtube.com/watch?v=xNQC56S5NFI
http://www.youtube.com/watch?v=N1TFiy2Dsdg
I really have spent some plenty of time on the web before selecting this CA-Fi device and I couldnt find anything better. To be honest I even went trough a mistake and loss of money by ordering an Android/WinCE dual OS device first (by the way its refferted to above in this thread). Result - I installed it into my dad's car (its better than his OEM 2003 Mercedes device anyway). But that one is wierd. My advice: be aware not to get one of those by mistake. For example, mine had GPS only in WinCE and 3G only in Android - so I couldnt have the Navigation system working along with traffic updates.... this spoiled everything for me.
PS
Important to know that CA-Fi offer a few dozens of versions of the same model with different front panels to match many of original car dashboards without the need of modifying the panels - the device fits in as a replacement for the OEM unit! As well for those who think that there are many different Android car stereos to choose from - this may be the same model with different front facing.
Like theese are the same device:
I have a JVC head unit in my car paired up to my Galaxy S III, and no matter what I do (tried a different SIII, resets, different music apps, etc.) the Bluetooth drops when I go to skip tracks from the radio (AVRCP). I have been forced to go to the CM10 ROM to get a reliable connection (although I'm stuck on a build from about a month ago, as some Bluetooth bugs have introduced there as well). Anyway, I'm eyeing up the Note II, but I'm wondering if anyone can confirm/deny if the Note II (stock ROM) has a different Bluetooth driver than the SIII. I hate to say it, but I actually really like Samsung's new interface, but the Bluetooth issue I'm having is a deal breaker. The other question is if anyone knows if the 4.1 update coming out for the SIII will have the same BT driver as 4.0.
Thanks!
had you ever flashed the KT747 kernel on the stock ROM of your s3? it changes the WiFi and Bluetooth drivers.
OR, if you haven't, maybe give it a try since it changes the WiFi and Bluetooth drivers.
Russ77 said:
had you ever flashed the KT747 kernel on the stock ROM of your s3? it changes the WiFi and Bluetooth drivers.
OR, if you haven't, maybe give it a try since it changes the WiFi and Bluetooth drivers.
Click to expand...
Click to collapse
I have not tried that. I would prefer to keep it stock, but that's something to try.
I thought I was the only one with this issue. I can relate as well . I too have a JVC unit and also experience the same bug on JB TW Rom. It tends to disconnect after I skip a few tracks and reconnects again . It does F*** up the mood when jamming to your music. At the moment im trying a different kernel to see if it does the same. But like you said CM10 doesn't disconnect.
Sent from my SGH-T999 using xda premium
J-ROCK said:
I thought I was the only one with this issue. I can relate as well . I too have a JVC unit and also experience the same bug on JB TW Rom. It tends to disconnect after I skip a few tracks and reconnects again . It does F*** up the mood when jamming to your music. At the moment im trying a different kernel to see if it does the same. But like you said CM10 doesn't disconnect.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
I emailed JVC on it, and they gave me the whole "did you try a reset" business... Infuriating. At this point I just want a stock ROM that works. My S & S II worked perfect on the same head unit...
How can you tell if the stock S III and Note II use the same BT driver? Oh, and let me know what your experience is with the new kernel.
It's a few more days until Jelly Bean is released. There are changes to the Bluetooth stack in Jelly Bean. I'd wait and give that a try before getting a new phone.
I had the same problem on my JVC receiver. Had the issue with Task's ROM too. Would happen when you skip through the songs fast. I switched to an Alpine deck and it still has slight issues but not as much. I also have an issue of it disconnecting and reconnecting right after I make a call. Hopefully Monday will bring a fix for us Canadians.
Sent from my SGH-I747M using xda app-developers app
Bluetooth has been messed up on the S3 from day one. I think it's an ICS issue because my gf's OneX has the same issues. I have a Mercedes B200 and I can't get sound through the car's speakers at all. Tried a bunch of different ROMs and kernels, including some JB (4.1) builds, all to no avail. I'm at this point waiting for 4.2.
I dont see any problems with my SG3 connecting my hyundai sonata car(2013 model) and honda CRV via bluetooth. No problems playing songs, phone calls and Google navigation.
Same phone didn't work with kia soronto SUV.
I feel the car bluetooth software has issues, not the phone software.
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
nani4215 said:
I dont see any problems with my SG3 connecting my hyundai sonata car(2013 model) and honda CRV via bluetooth. No problems playing songs, phone calls and Google navigation.
Same phone didn't work with kia soronto SUV.
I feel the car bluetooth software has issues, not the phone software.
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
Click to expand...
Click to collapse
It could be, but I've used a Captivate, Infuse, & S2 on the same radios (two different JVC decks), and they've all worked perfect. Those all had stock ROMs (to start). I flashed CM9 and then CM10 on the Captivate & SII, and they still worked perfect. The only phone (stock/not stock ROM) that has ever had problems for me is the S3. My gut tells me it's a problem with the Bluetooth stack on the stock ROM, seeing as BT on CM9/CM10 works perfect on the S3 (other than the bass-less sound bug on the "stable" release and after - nice "stable" release).
Somebody on XDA should start hacking the software on these touchscreen head-units (they are update-able :good, then I'll be impressed.
Note 2 BT
Anyway, has anyone tried a Note 2 on one of the radios you had problems with? If not, I might try a re-post over in the Note 2 forum...
rytymu said:
Anyway, has anyone tried a Note 2 on one of the radios you had problems with? If not, I might try a re-post over in the Note 2 forum...
Click to expand...
Click to collapse
Well I bought a Note 2, SAME DAMN PROBLEM! I'm 95% sure I'm returning it, the only other option is to buy a different head unit. Anyone else have a GS3 and an aftermarket radio that DOESN'T drop the bluetooth connection when skipping tracks?
rytymu said:
Well I bought a Note 2, SAME DAMN PROBLEM! I'm 95% sure I'm returning it, the only other option is to buy a different head unit. Anyone else have a GS3 and an aftermarket radio that DOESN'T drop the bluetooth connection when skipping tracks?
Click to expand...
Click to collapse
i have a kenwood ddx 418 and ive got no issues with bluetooth, best bet would be to go to a bestbuy and try out the display units there imho
Bluetooth audio for music and calls works fine with my Ford Edge...however there is no track information (avrcp) sent to the headunit which is annoying. No change with the Jellybean update either.
mixxy said:
i have a kenwood ddx 418 and ive got no issues with bluetooth, best bet would be to go to a bestbuy and try out the display units there imho
Click to expand...
Click to collapse
funkydude101 said:
Bluetooth audio for music and calls works fine with my Ford Edge...however there is no track information (avrcp) sent to the headunit which is annoying. No change with the Jellybean update either.
Click to expand...
Click to collapse
But are both of you running bone-stock ROMs? If so, I may have to start looking at radios again.
Returned it. I guess that's a $35 experiment (thank you AT&T for the restocking fee). Either the Sammy BT stack is too advanced for my basic A2DP radio (as in ALL BT radios), or the Sammy BT stack is just horribly developed (which I've come to believe is true). Now I just have to wait for an apt-x head unit to come out, then I can try this experiment again...
I remember reading sometime back that Galaxy Nexus has hardware capable of supporting both Bluetooth 4.0 stacks, but that BLE (Low Energy profile) was not enabled via driver/SDK. I wonder if there was any progress in this direction or at least clear indication from Google on the support. There is a binder full of BLE devices getting on the market in Q1 that jump on support from iPhone 5 and some of them are extremely attracting but I would hate to get rid of my Nexus if I could.
Is there a ROM that can provide compatibility?
Ive been trying to post everywhere and anywhere about this topic but noone seems to care. More and more devices are being launched use BLE and developers wont make an android app because android doesn't support BLE at the moment. I dont know why more websites are making this an issue yet..phones are being launched saying they are 4.0 capable..which is correct but we cant use that technology. Its sad because i want the new FITBIT flex band but they are only making the app available to sync with the S3 and note 2 because samsung is helping then with the Bluetooth drivers for the app.
In addition to your post, a ton of devices are coming with AVRCP 1.3+ on stock devices. However only a select few ROMs have it enabled at all.
Sent from my Galaxy Nexus using xda premium
newtonfb said:
Ive been trying to post everywhere and anywhere about this topic but noone seems to care. More and more devices are being launched use BLE and developers wont make an android app because android doesn't support BLE at the moment. I dont know why more websites are making this an issue yet..phones are being launched saying they are 4.0 capable..which is correct but we cant use that technology. Its sad because i want the new FITBIT flex band but they are only making the app available to sync with the S3 and note 2 because samsung is helping then with the Bluetooth drivers for the app.
Click to expand...
Click to collapse
Thanks, I am personally waiting for these devices (StickNFind, BluTracker) to hit the market in March and April respectively and I more and more inclining to get an iPhone because of the better support there. For Newtonfb, did you look at BodyMedia FIT LINK Armband? This is what I use and it has all the same features plus more of Fitbit and is fully supported on GNEX via regular Bluetooth.
I'll look into that. Thanks.
Sent from my Galaxy Nexus using xda app-developers app
Hello guys...
I want to buy this phone but I have some questions before buying it!
So...I want to use this phone with my Passat CC Bluetooth CarKit.
The CarKit supports only rSAP protocol connection.
Does this phone support this type of connection?
I`m asking this because now I own a Xperia Z1 Compact and unfortunately this phone doesn`t have support for rSAP Bluetooth connection.
Thank you!
aresbv2000 said:
Hello guys...
Does this phone support this type of connection?
Click to expand...
Click to collapse
Regarding to your question I think just making a test with a phone friend can be sure of that.
After a brief search I found this information:
This profile allows devices such as car phones with built-in GSM transceivers to connect to a SIM card in a Bluetooth enabled phone, thus the car phone itself doesn't require a separate SIM card. This profile is sometimes referred to as rSAP (remote-SIM-Access-Profile), though that name does not appear in the profile specification published by the Bluetooth SIG. Information on phones that support SAP can be found below:
Samsung:GT-B7610, GT-B7620, GT-B7350 (OMNIA 735), SGH-i900 ...
And ...
GT-I9000 Galaxy S
GT-I9001 Galaxy S plus
GT-S5570 Galaxy mini(POP)
GT-I9100 Galaxy S II (only to Android 2.3.x, with newest update from 4.04 again possible)
GT-I9300 Galaxy S III
GT-I9305 Galaxy S III LTE
GT-I9505 Galaxy S IV
GT-I8150 Galaxy W
GT-N7000 Galaxy Note
GT-N7100 Galaxy Note II
GT-P1000 Galaxy Tab
GT-I9105P Samsung Galaxy S2 plus
Click to expand...
Click to collapse
So, if you want to be 100% SURE about compatibility, only with test YOU CAN.
LE: Maybe you can ask someone in our dedicated forum vwForum.ro :good:
Thank you so much for your reply. Unfortunately I don`t have any friend or something like that that owns a S4 Mini for direct testing with my car integrated bluetooth. A good idea is to ask on the vw forum what phones do other users connect to their cars. Thank you again! Have a nice day!
In case anybody else digs this thread up (as I did on a Google search), there are a variety of phones that will work IF they are rooted: see Android-RSAP.com, where there is a small-scale (single dev) effort to get phones working.
He's had a reasonable level of success with some phones.
In terms of phones that are supported officially (out the box), this list is kept up to date by Audi, so is reasonably reflective of the other VAG cars (e.g. VW): HERE, make sure you tick "Carphone", otherwise it'll give you all the phones that support handsfree
The general summary is that almost ALL Samsung (Android) and Nokia (Symbian ONLY!) phones should work, there are a smattering of other HTC / Blackberry phones that will also work, but it's pretty limited - I've tested Galaxy S2's, S3's, S4's and S5's.... all worked witdout any fiddling, out the box, first time... likewise with my OLD "Nokia X3-2 Touch"... significantly less luck with the Blackberries, including a 9360Curve and a 9900Bold, that were on the supported list at the time: they would connect once, but needed the entire Bluetooth profile removed and re-added for each time I tuned the ignition off and back on.
I've also have an extensive "fiddle" with a (rooted) HTC One X+ and Nexus 4 and never had a usable connection.