Related
Hi all,
We all know that rSAP is not supported by Android
Those with carkits (VW, Audi, etc) with this profile cannot use their Android phone. A massive disappointment.
What will it take to get someone write some code to get this bluetooth profile to work on - for starters - the basic Froyo code for Nexus?
I'd be happy to kick off a project with a $150 donation or an HTC Hero (such as for testing).
Assuming we can get more people together who are interested in this (I am positive!), the big question remains - who would be able to write the required code?
MC
+1
We need rSAP
Sent from my Nexus One using Tapatalk
In Android issue 4402 (not permitted to post outside links, just go to the google code page and search for 4402) about the rSap profile some people are reporting that the Samsung Galaxy S (I9000) does have the rSap profile and does successfully connect to VW/Audi premium carkits.
In the Galaxy S forums are some roms (including a MCR rom for the Galaxy S) ... so there might be some possibility to port some code from the Galaxy S to the Nexus One
TFox said:
In Android issue 4402 (not permitted to post outside links, just go to the google code page and search for 4402) about the rSap profile some people are reporting that the Samsung Galaxy S (I9000) does have the rSap profile and does successfully connect to VW/Audi premium carkits.
In the Galaxy S forums are some roms (including a MCR rom for the Galaxy S) ... so there might be some possibility to port some code from the Galaxy S to the Nexus One
Click to expand...
Click to collapse
Thanks, I found it and repeated my post there as well.
I really hope that someone can come up with something. Surely, as you say it works on the Galaxy S, one must be able to get this to work on the Nexus One, or any other Android phone for that matter.
Hoping to see some more replies here! Or maybe a recommendation of a programmer who might be able to do this.
Cheers, MC
Hi, I have the RSAP working on an Samsung galaxy i9000 wich my Audi built in car phone. The only hing bugging is the sync of phonebok. It synces alright, but with phone conacts only. It took me a while to realize that phone conacts and my primarily used exchange contact list are two different things in this setting. First I had believed it synces only sim contacts. While this is not the problem, I have not found a way yet to "replicate" the synced exchange contacts or map them to the phone phonebok from business contacts, wich would make them visible to the carphone via rSAP.
maybe someone here knows a solution or an app that would solve this? The rSAP itself works, as Samsung has implemented it into the Galaxy i9000.
Sent from my GT-I9000 using XDA App
I will exceed the OP's donation and donate $151 who ever manages to crack the rSAP on Android. Samsing just made the sourcecode (search: Samsung releases Captivate source code) so there seems to also be a ZIP file for the GT-I9000 (European Samsung Galaxy S).
I am stuck with TouchHD for my VW PremiumGSM, and would love to get an Android.
Cheers and keep it up devs!!
+1!
plz, an app for rsap on n1!
Android on GSM... maybe, but limited; CDMA not likely
According to a post 4402, "rSAP allows different devices to connect to your mobile's SIM Card to read your contacts etc. The car than uses its own antenna and gsm Module to call. The mobile phone goes in a stand by mode which needs very low energy."
If this is true, then your rSAP-bluetooth connection is actually hijacking your sim card ID and using it to place calls and receive calls through the car's integrated GSM radio, and not actually synching as it seems. In this case (in the US), there is no Verizon or Sprint fix because neither network uses SIM card (chip based ID profiles) technology, and furthermore, both their networks are CDMA and therefore incompatible with Bentley, VW and Audi GSM modules. If the connection could be bridged, the car's GSM radio would be seeking access to a network the CDMA user is not subscribed to.
So the definitive end is that as long as you have a VAG auto, you better have an rSAP GSM phone to use with it.
Ironically, Apple iPhones are GSM and they have had a longstanding good relationship with VAG, so I am surprised to find them boxed out of compatibility with Audi and VW especially. I am not certain, but it could have something to do with Apple's unique provisioning architecture is as much as they do not have a readily accessible SIM card (or battery), and in doing so, they are not respecting the need for SIM portability.
When I worked at a multi-carrier mobile phone reseller years ago, I briefly had a SIM-card based phone that I could then take the SIM card from and insert it into any GSM phone (from the same carrier) and use that phone to place and receive calls. This same migration can be effected in CDMA technology, but only through over-the-air provisioning, and that process is not as immediate as the rSAP SIM takeover process seems to be.
I'll keep looking into this matter, but perhaps the upgrade we should be barking for is to have VAG integrate support for the same bluetooth profile (HFP) that BMW does. BMWs from 2007 on with bluetooth will connect to my Droid X all day. rSAP just overtakes your SIM id and uses it to place and receive calls on the car's GSM radio. Of course it also can access a portion of your Address Book, but after that, you are stuck with the features offered in your car's radio and no longer have full utility of your Droid phone features and apps, etc. As a result, Google Voice search will be a non-starter for Android rSAP unless the car's GSM radio is actually running Android OS as well. And how likely is that...
maybe this could help?
http://allforfreelancers.com/getafr...Android-iPhone-J2ME-Nokia-Symbian-726296.html
Rsap works..but no Bluetooth audio
Hi,
I got my I9000 working on my Premium Bluetooth in my VW Passat. However I cannot figure out how to get the Bluetooth Audio (in the Media Secion of the car display) working. I have enabled it in settings in the car. AUX works, SD-card works.. but bluetooth audio I just cannot figure out.
Does any1 know?
I have a NTG1 Comand in my Mercedes, and the rSAP conection works like charme, with the SGS(2.2.1 jpy).
Only thing that not works is the PBAP so only my sim card contacs r listed!
Mike
tommylad said:
Hi,
I got my I9000 working on my Premium Bluetooth in my VW Passat. However I cannot figure out how to get the Bluetooth Audio (in the Media Secion of the car display) working. I have enabled it in settings in the car. AUX works, SD-card works.. but bluetooth audio I just cannot figure out.
Does any1 know?
Click to expand...
Click to collapse
Hi, Bluetooth Audio works exactly as it works with bluetooth headset: you need to launch a music player on the phone and then the audio will be transfered to your car's speakers. I just got my new VW Touran and SGS works almost fine with it (having troubles with the contacts with emails, which are not synced to the car). I think I'm going to get an SDHC card for my music (Media-IN works great with a usb drive).
Cheers
I had a couple of questions about using Spirit FM Radio app on CM 7.2. And I would like to know in detail about it.
Firstly, When I ran the Spirit app on CM 7.2 i noticed that it doesn't switch on the Bluetooth. Does that mean that it uses the internal Broad com FM chip instead of Bluetooth to receive FM transmissions just like in the LG stock FM radio app?
Will the Spirit FM app still run properly if I UN-install the CM 7.2 Stock FM app? Or does it need the CM 7.2 Stock FM app to run properly?
In the setting of the app, within audio, I saw various options like cyanogen Mod, LG, lge-msm7x27,etc. Even tough i didn't see any difference in quality while going through different options. Which would be the ideal option for us and What do these options do?
CM9 hasn't got a radio am I right? (Btw I'm new to the forum I couldn't find a topic to write this I'm sorry
What phone are you using?
When Bluetooth is enabled FM is enabled too because they locate at the same chip. It's the easiest way to enable FM and so is CM radio doing. Spirit FM (and stock LG) does it little bit harder by only enabling FM thus saving some starting time and battery (battery part is not a 100% fact though, only my own speculation).
You can remove CM radio, it is not needed.
Recommended method by author in Spirit is CyanogenMod. I don't know exactly what are the differences between different methods but stick with CyanogenMod.
Spirit FM does use Bluetooth, only the icons aren't changed that's all.
Sent from my LG-P500 using xda premium
4silvertooth said:
Spirit FM does use Bluetooth, only the icons aren't changed that's all.
Sent from my LG-P500 using xda premium
Click to expand...
Click to collapse
I might be wrong but if Bluetooth is turned on i see no indication, not only in status bar, settings, no device discovers it (visible), i think i need an app to check the components...
Will check back whit the answer
Edit: It dose use bluetooth
moby_test said:
I might be wrong but if Bluetooth is turned on i see no indication, not only in status bar, settings, no device discovers it (visible), i think i need an app to check the components...
Will check back whit the answer
Edit: It dose use bluetooth
Click to expand...
Click to collapse
How did u finally come to that conclusion that it does use Bluetooth? And if it does... Does that mean that there is no big difference in the way Spirit, Cyanogen mod and LG FM radio app works?
I have my own thread for questions, 1st link in my sig: http://forum.xda-developers.com/showthread.php?p=13379669
And I respond to emails and PMs, but sometimes respond on my thread for all to benefit. Or just let me know a thread's been opened...
See below for answers:
sweettaniyaa said:
Firstly, When I ran the Spirit app on CM 7.2 i noticed that it doesn't switch on the Bluetooth. Does that mean that it uses the internal Broad com FM chip instead of Bluetooth to receive FM transmissions just like in the LG stock FM radio app?
Will the Spirit FM app still run properly if I UN-install the CM 7.2 Stock FM app? Or does it need the CM 7.2 Stock FM app to run properly?
In the setting of the app, within audio, I saw various options like cyanogen Mod, LG, lge-msm7x27,etc. Even tough i didn't see any difference in quality while going through different options. Which would be the ideal option for us and What do these options do?
Click to expand...
Click to collapse
Copied on my thread, because I did a lot of thinking and typing...
Yes you can remove the CM FM app.
On CM7, the default CyanogenMod audio method is generally best. It's the same method the CM7 FM app uses, so it's the most likely to work well, especially when dealing with things like phone calls coming in when FM is on.
If a CM ROM for any phone has a CM FM app, this method should work, but unfortunately that's not yet the case with CM9 ROMs. so low level methods are needed for now on CM9, and there are often issues, and many CM9 ROMs just don't support FM audio routing yet, or I haven't figured them out.
Re: Bluetooth: my app has many ways to access FM chips.
- The first method I supported was via Bluetooth (the HCI API), like the CM FM app. Like it, my app can run commands using the command line hcitool utility, and this is nice because my app can run without root/SU. But it's not too efficient, especially when using RDS where lots of data gets transferred.
- For better efficiency, with root, my app supports direct access to the HCI sockets, through a daemon, because apps don't have the privilege otherwise.
- But because many people were running stock or stock derived ROMs using the Broadcom proprietary BT stack, and I could find no way to send HCI commands with it, I created a "UART mode" that communicates directly with the Bluetooth/FM UART. The wireless part of Bluetooth is not switched on, which saves power. But this mode requires root (unless /dev/ttyHS0 or whatever is accessible from an app), and only works if BT is off.
- A new access method is available now on stock and stock derived ROMs that run the proprietary Broadcom BT stack and that supports the stock LG FM app. This can work on stock, unrooted devices. In this mode the characteristics of the stock FM stack are unavoidable, both positive and negative.
The Broadcom proprietary BT stack has a special mode where Bluetooth is considered off, but FM is on. This enables the Bluetooth HCI "UART" to provide a path to control the FM part of the chip.
- There are different device driver access methods used for dedicated FM chips not contained in a BT/FM combo chip, but those don't apply to the P500.
OK for SGA?
Can I use this FM radio app for my Samsung Galaxy Ace? I have Ice Cream Sunday ROM installed.
donzzy said:
Can I use this FM radio app for my Samsung Galaxy Ace? I have Ice Cream Sunday ROM installed.
Click to expand...
Click to collapse
Off-topic, and you should ask on my thread anyway, or check post 2 of my thread. Please don't respond here.
Canned response now:
The Simpsons taught me that among Hemingway's words of wisdom was:
“The shortest answer is doing the thing.”
IE, why don't you just try it ? It's free and only takes a minute or two I think.
There's even an intro that can be read and will give some useful information on configuration.
Then if you have trouble, you can come back, report it, and hope for an answer.
mikereidis said:
Copied on my thread, because I did a lot of thinking and typing...
Yes you can remove the CM FM app.
On CM7, the default CyanogenMod audio method is generally best. It's the same method the CM7 FM app uses, so it's the most likely to work well, especially when dealing with things like phone calls coming in when FM is on.
If a CM ROM for any phone has a CM FM app, this method should work, but unfortunately that's not yet the case with CM9 ROMs. so low level methods are needed for now on CM9, and there are often issues, and many CM9 ROMs just don't support FM audio routing yet, or I haven't figured them out.
Re: Bluetooth: my app has many ways to access FM chips.
- The first method I supported was via Bluetooth (the HCI API), like the CM FM app. Like it, my app can run commands using the command line hcitool utility, and this is nice because my app can run without root/SU. But it's not too efficient, especially when using RDS where lots of data gets transferred.
- For better efficiency, with root, my app supports direct access to the HCI sockets, through a daemon, because apps don't have the privilege otherwise.
- But because many people were running stock or stock derived ROMs using the Broadcom proprietary BT stack, and I could find no way to send HCI commands with it, I created a "UART mode" that communicates directly with the Bluetooth/FM UART. The wireless part of Bluetooth is not switched on, which saves power. But this mode requires root (unless /dev/ttyHS0 or whatever is accessible from an app), and only works if BT is off.
- A new access method is available now on stock and stock derived ROMs that run the proprietary Broadcom BT stack and that supports the stock LG FM app. This can work on stock, unrooted devices. In this mode the characteristics of the stock FM stack are unavoidable, both positive and negative.
The Broadcom proprietary BT stack has a special mode where Bluetooth is considered off, but FM is on. This enables the Bluetooth HCI "UART" to provide a path to control the FM part of the chip.
- There are different device driver access methods used for dedicated FM chips not contained in a BT/FM combo chip, but those don't apply to the P500.
Click to expand...
Click to collapse
Thank you for clearing it to me. But I don't know... something weird happened to me. I was using Spirit FM radio app whole day yesterday but the Blue-tooth icon never showed up. But today when tried the app again It has been showing the Blue-tooth icon. I don't get it. What changed? I tried re-booting and everything. Still the same.
Does Android 4.1 allow a device to serve as a Hands-Free Profile (HFP) device? Similar to the way many newer cars come with integrated Bluetooth/HFP, I would like to use my tablet (Nexus 7) as a front-end for my phone. When an incoming call comes in, the phone should relay the call over Bluetooth to the tablet; it should also allow the tablet to make outgoing calls via Bluetooth over the phone's network.
Please note that I am not interested in solutions such as GrooveIP, Talkatone, and SIPDroid. I am specifically looking for Bluetooth HFP.
I've done quite a bit of searching but have not seen an app that does this. I wouldn't mind looking into developing such a product - but I first wanted to know if the HSP 1.6 host API was available in Android 4.1. I've seen resources stating it was available in ICS 4.0, but I believe this is to allow Android devices to connect to third-party HSP devices - I'm looking to do the opposite (i.e. have the Android device serve as the HSP host).
i am also curious about this.
fxftwo said:
i am also curious about this.
Click to expand...
Click to collapse
Me too
For those of us that plans to install a Android tablet in the car for music etc. this would be tha last part to make it a complete in-car device.
I am another curious one about this. The only devices I know of for sure that can do this are the 3.6 and 4.2 samsung galaxy players. Unfortunately, I have the 4.0 galaxy player, that doesn't support it. The galaxy players run gb, not jb, btw.
Sent using Tapatalk
Did anybody found a solution, and trying to add this feature to my android app.
anonim1 said:
Does Android 4.1 allow a device to serve as a Hands-Free Profile (HFP) device? Similar to the way many newer cars come with integrated Bluetooth/HFP, I would like to use my tablet (Nexus 7) as a front-end for my phone. When an incoming call comes in, the phone should relay the call over Bluetooth to the tablet; it should also allow the tablet to make outgoing calls via Bluetooth over the phone's network.
Please note that I am not interested in solutions such as GrooveIP, Talkatone, and SIPDroid. I am specifically looking for Bluetooth HFP.
I've done quite a bit of searching but have not seen an app that does this. I wouldn't mind looking into developing such a product - but I first wanted to know if the HSP 1.6 host API was available in Android 4.1. I've seen resources stating it was available in ICS 4.0, but I believe this is to allow Android devices to connect to third-party HSP devices - I'm looking to do the opposite (i.e. have the Android device serve as the HSP host).
Click to expand...
Click to collapse
From what I can gather:
* Bluetooth defines HFP to have two roles: the Audio Gateway (AG) role and the Hands-Free (HF) role.
* Android doesn't natively support the HF role.
I too am interested in exactly what you are describing -- would like to use a tablet as the infotainment hub of a vehicle. I would happy to be a part of or organize a bounty to support development of such a capability in CM10.
-jd
Someone custom-implemented the needed Bluetooth role
Looks like some Android device has custom implementations of both A2DP sink role and hands free unit role. I can't post links yet. Google this:
AllGo Systems Demonstrates Android Based Automotive Infotainment Solutions with Fast Boot-up as a Critical Feature at SAE Convergence 2012 - Detroit, Michigan, USA
n230384 said:
Looks like some Android device has custom implementations of both A2DP sink role and hands free unit role. I can't post links yet. Google this:
AllGo Systems Demonstrates Android Based Automotive Infotainment Solutions with Fast Boot-up as a Critical Feature at SAE Convergence 2012 - Detroit, Michigan, USA
Click to expand...
Click to collapse
any leads if this is available on android yet? (Hands free profile)
There's some development about this but I'm not sure it's possible yet.
have a look at the links here: https://stackoverflow.com/questions...a-receiver-for-a2dp-profile/28892944#28892944
I want, too
to use android device as hands free
Hello all,
I'm after a little bit of guidance on how I might add Bluetooth support to an Android powered Car stereo. It is a "Road Veles" single DIN WinCE and Android device with a 7" flip out screen. The reason I bought this stereo is to run an app by the name of MSDroid. This app was to connect to my vehicle's engine management system via Bluetooth.
Can't post links yet, easy search on Google for Road Veles, look for hit on Chinavasion
The specs say it has Bluetooth, but having tested the device out on the work bench what the specs don't say is that the bluetooth is only accessible for handsfree from WinCE, there is no bluetooth for Android. WiFi via USB dongle works great. I have purchased but not yet received a combined WiFi and Bluetooth dongle. I would very much like to have this combined dongle work with the device. The Bluetooth control is not visible under WiFi control inside settings like it is in my Android phone.
Can anybody point me in the direction of where to start with this? Can I root the device and mod to add bluetooth? Is there another ROM I could run? I have done a lot of searching but can't see much at all out in internet land on this stereo!
Any help greatly appreciated! Thanks in advance,
Arran
Hi, I'm not sure how these sort of things usually work, what sort of dollar value would usually be associated with making a some tweaks to an Android build? ...
Hi again, still looking into this. Any ideas how to tweak the Android 4.0.4 OS to make bluetooth appear inside the settings menu?
Hello,
I have rooted my infotainment system in my Honda Civic according to this forum post successfully.
I installed the Torque Pro app which connects to the a Bluetooth ODB-II reader. I verified that it was working using my OnePlus 2 phone and that there were no issues pairing. However, the car infotainment system seems to only display Phones when scanning for devices. It does not detect the reader or my laptop when in discoverable mode.
I took a peak inside the /etc/bluetooth/main.conf file and it seems that it contains entries to whitelist only certain kinds of devices. However, following the comments replacing the values 0xFFFFFF does nothing. I don't think the file is even being read because if I change the device name "HandsFreeLink" to something else, it doesn't actually change.
My suspicion has something to do with the Android version that it is running and the bluetooth stack. It is running Android 4.2.2, and since Jelly Bean, the Bluez stack was replaced with Bluedroid. However, I can't tell what Bluetooth stack is actually running because of some contradictory things:
- /etc/bluetooth/main.conf is there (though it seems to be ignored)
- /data/misc/bluetooth is empty
- /data/misc/bluetoothd has a folder with the device MAC address. Looking into the files, they have lists of already paired devices, etc. (isn't this Bluez that creates these?)
- /data/misc/bluedroid does not exist
I also tried using a separate app to do the pairing, perhaps the UI was hiding other devices. Nope, only phones are being shown.
Where else should I look for Bluetooth configuration? Is there anything I can do, or is this likely something deeply ingrained whenever Honda rewrote part of the bluetooth stack for their car...
Thanks,
cdahmedeh
I'm looking for the same thing but my data/misc/Bluetooth is not empty, I have two HCI folders. I'm trying to get any command that use bluetooth like hciconfig but I cannot get it
Have you guys found a way to pair other bluetooth devices? Its really seems that only phones are visible. Please share if you guys found a solution. Thanks!
I may have found a fix. Not sure how helpful this is but there is a customizable ECU for honda vehicles called Hondata. Normally it just allows you to flash you car ECU to gain more HP but since honda started using android on their headunits, it opened up doors for your car to display ECU info and communicate easier with other bluetooth devices. In this video tutorial, it showed how to root the headunit, install custom apps, and also find other bluetooth devices. They show you for their own purposes of connecting their device but im sure it will allow any bluetooth device.
https://www.youtube.com/watch?v=XGdF1jm987o