Has anyone tested if the OnePlus 5 ist rSAP compatible?
This feature is needet to connect the smartphone with your car entertainment like at audi, vw, mercedes or bmw.
I hope there is one of you who tested this already.
Unless the car only supports rSAP I wouldn't even bother with it. HandsFreeProfile has countless advantages.
Just out of curiosity: why do you need rSAP?
PS: I am testing the telephony side of the next gen Mercedes entertainment system.
I need rSAP to connect my online services from my audi to the web. I don't have an additional sim card, which could be used to connect everything to the web. I would also like to use the wifi functionality for me and my passengers.
Sure my car also does support the regular hands free protocoll, but thats without sharing the internet service of my device.
Do you have the ability to test the rSAP functionality? Du wärst mir echt eine grosse Hilfe, bevor ich das Geld für das Hands ausgebe und dann merke, dass es wohl doch nicht klappt
Sadly I don't have a 1+5 yet, so I cannot test rSAP on this particular model. I'm still waiting to a few things to clear up (not necessarily related to 1+5) before buying it.
On the case that the 1+5 doesn't support rSAP, you could try asking your operator for a second SIM for the same account (technically possible) and use an older phone that supports rSAP only in the car. Or check a few tutorials around the web on how to activate it on any phone.
Not sure if it is enabled or not but you can do that yourself.
http://www.android-rsap.com/41-support/128-enable-qualcomm-sim-access.html
Hi, I have an Audi with a similar setup to the OP, although I don't know comparative ages and MMI versions etc, but in short it didn't work. So first off searching for the OP5 it finds the device no problem and offers up three connection options, "Car Phone", "Handsfree" and "Media" (not exact names, but the first is rSAP, effectively). So this suggests it should support rSAP (although not sure if the Head Unit always offers that as an option or not), however when I try and connect to the "Car Phone" profile it attempts to connect but in the end fails to do so. There are no particular error messages (none on the phone) and handsfree and music audio seem to be supported just fine.
So fingers crossed an upcoming firmware update might fix this issue but will have to wait and see.
Just a quick update and it looks like there is currently no support for rSAP on the OP5, which I guess isn't a surprise. I've asked for it to be fed back to the dev team - whether that will make any difference whatsoever only time will tell. Perhaps the more people that request it the better, if you need it.
I haven't tried the method(s) mention by @Kahun as it looks like you need root and not sure I want to do that as, a) I presume Android Pay will stop working and b) not sure if this completely invalidates the warranty (e.g. qfuse as Samsung had) or whether reflashing to stock is fine. Also not sure if I'd have to re-root and re-enable after every firmware update, so would hold off until there are fewer releases.
Hope that helps.
Anyone got RSAP to work?
Related
Sadly enough I have noticed that the xperia X1 does not like my premium volkswagen carkit. As used in passat or audi or skoda superb, bmw, Mercedes, etc.
I have an RNS-510, but have also tried it with a RNS-310. Both having the premium carkit in it. Also called carkit III.
It uses rSAP to enable transfer of contacts and phone settings control.
I have tested with a nokia N95 and it works perfectly fine with that after you enable the remote sim access profile. Also known as SAP.
Sadly enough, the X1 refuses to connect. The carkit just says the phone is not compatible.
Anybody have any clue what to do?
Maybe a custom ROM which does have this functionality? Or a tool that can be added?
u r talking about remote sim access right?
my rom (cmex absolute touch) got an option to enable it under bluetooth setting (connections)
Yes or You use this little cab! Works perfectly with VW Golf VI PRemium Handsfreekit. I used the smaller file, but if it dont works try the bigger one!
In the bluetoothsettings you should find the sap profile after the installation, and in the programs a small utility to activate it. the Xperia himself has no SAP Profile!
wow!
I definately came to the right place! I will try this out tommorow first thing and let you know if it works!
Thnx's again. Also considering your rom now achmed20, because I believe this is quite basic functionality which should have been there in the first place!
As I said, I'll let you know if this worked!
not working yet
Well, that helped, a bit.
I get to the connection screen, have to enter the 16 digit pincode and after that the car just says connecting, and stays doing this for a minute or two and then just says failed or not compatible.
So I'm a lot further, but it isn't working yet! I'm thinking because of all the things I have tried, I might have broken it somewhere, but unsure how or what.
Thinking of maybe flashing it with a different (custom) rom, to see if that might fix the problem.
Anyone have any other advice?
no experience with the kind of trouble your having but if you want to try off on a fresh start, i would do a hard reset, then install the cab fix that was recommended.
still not working
I just installed the cmEX absolute TOUCH rom and did a hard reset after that.
Enabled rsap on the last tab of bluetooth and the car says its connecting and just does that for a long time (after entering pin code). Sadly enough, it just times out.
Anybody have any clue what could be the problem? I have the feeling we are allmost there, but there is just a little thing causing it to time out.
rsap even says it's connected to my skoda and everything.
From what I can gather, the cmEX absolute TOUCH rom is based on a touch HD.
more testing!
Okay, from what I have been able to gather, the following is going on.
The carkit is trying to log on in a frequency that it cannot handle.
I have been able to connect the carkit, download the address book and make calls with my Xperia now. No problems what so ever....except one. I was using a SIM from a collega whom has a different network!
I use t-mobile and my collegea has kpn/telfort. Doing more research, I have learned that kpn/telfort and vodaphone use the 1800 band frequency. And that t-mobile uses the 900 frequency.
I am not entirely certain at this point that this truly is the real problem, but, my phone works, my carkit and car works, so all the software bits are in sync, but only using a different sim. Rebooting the phone, changing nothing but the sim, makes it completely broken again!!
I'm using a RNS-510 with the Skoda/VW premium carkit. If anyone is able to shed some light on this and what possible fixes could be, I'd really like to hear!
I have been looking (and mailed) if a fiscon unit could potentionaly fix this problem. They also have units which intergrate with the system.
But I'd rather find a software solution, obviously. Sadly enough, manny cases can be found where people have problems, often, with no solution. This problems is *NOT* specefic to the Xperia, I do realize that now, since the new ROM, rSAP is working just fine.
more complex then ever....
Okay, things just more complex then ever before.
My x1 using a HTC touch HD rom base and rSAP from HTC (default in rom).
KPN sim = works and can call
Vodaphone sim = logs in but carkit crashes on trying to connect to cell towers. But car connection functions.
T-mobile sim = connection to carkit never gets finished.
I'm totally lost. Using a friends N95, all the sims work flawlessly.... which makes me even more clueless, because the carkit reads the sim data and then connects using it's own radio to the cell network.
Please, advice? How can this be fixed? Is there a different version of the HTC rSAP software available maybe?
The plot thickens again.
Using my sim card in my X1, not working. Original ROM, Original ROM + rSAP extensions, cooked rom from touch HD with native rSAP. Just non-functional.
Using the exact same phone, without the t-mobile sim but with the KPN sim, works perfectly, no problems what so ever.
Using an older Nokia E50, both sims work flawlessly, also my t-mobile sim.
This leads me to one conclusion and that is that the HTC rSAP implementation is seriously bugged.
Anyone have any idea on how to proceed? Somewhere I have read that the HTC's wouldn't handle 3G or UMTS sims and only use older ones. But, using the KPN sim I connect to 3G and it works. Also the nokia E50 of N95 can use any network and it just plain works. There for that statement is wrong in my opinion and it is caused by buggy software of HTC.
Anyone have a good idea on how to proceed? Lots of people having this problem and buying nokia's, but for no real reason other then buggy software it seems.
I really like my X1, and payed a lot of money for it, so I really need this to start working.... Please assist and help, also people with a diamond or other HTC, using the same software.
sadly enough, no progress
Did some tests again today, but sadly enough, no progress yet.
I'm going to try and get a hold of a Touch Diamond and a Touch HD and see how those preform with my sim. If my suspiciouns are correct, they will also fail, making this a combination of bad software with bugs with certain sim's.
That is the conclusion I am faced with right now... sadly enough, no idea how this can be remedied.
Are there developers whom might be able to write a reliable rsap implementation or will HTC ever come with a working version?
What do you guys think?
Sonyericsson will not provide SAP for the Xperia. Thats the point....
Been in contact with support
I have been in contact with Sony-Ericsson support and they tell me they cannot make the X1 compatible, because it is not just software.
Off course, to me this sound like total bull****, seeying I have allready had an raap connection with the X1. But this was either using HTC software add-on's or using a rom that was based on the htc touch HD.
Sadly enough, I cannot work without this functionality... and thus will be forced to sell my phone and buy... a nokia.... not bad, since I have had nokia's all my life. But I really really do not eNjoy beying forced to do so.
But everybody has known that the xperia has no SAP Profile... in every test, in every Datasheet you can see it! Why you buyed an xperia?
Wrong order
I orderd the x1 around the same time I orderd my new car (Skoda Superb II 2.0 TDI Ambition Business line ).
The car came with a carkit that can only do rSAP, but it is very very nicely intergrated with a external antenna, full adress book acces, etc. etc.
To my amazement, there was no rSAP on the phone, while all current high end models do carry support for it. Thus thought that a simple program or rom fix would provide it.... sadly enough, while some stuff works, it is very very flaky.
So it's a combination issue, off course I realize that. But I'd rather replace my phone and sell the x1, then having to change the carkit piece in my car (it is far more expensive). And still, I just cannot believe that such a basic function, is not in there.
Especially because it is made by HTC, which do carry this functionality!
So the problem was created by having both products in the same time frame. And my reluctance to believe such a high end phone would not carry this protocol.
From closer reading though. It seems that the x1 (with a custom rom) is not at fault here. If my speculations are right, any htc device with rsap from factory even has a big change that it is not going to function. Also reflected by my tests.
Using a HTC touch HD based rom on the X1, rsap is added and functions brilliantly using a KPN sim. Vodaphone works sometimes and crashes the carkit now and then and using a t-mobile sim, it does not work, at all. Since I have a t-mobile business account... it doesn't work at all for me.
I have not been able to get a hold of a Touch HD or Touch Pro to test if these problems also form on that phone, but will do so when I get the change.
So for now, even the HTC software seems to be bugged and thus I have formed my conclusion that my best option is to go back to nokia (which I have used for about 10 years now). The x1 is great, but not beying able to call in the car.... that just isn't going to work for me.
The new N97 looks pretty decent....
I have a jetta 06 tdi with mfd2(dvd version rev c) and skoda (kufatec) bluetooth modul installed by myself. I can do a Synchronisation of the Phonebook with Names and Numbers , dialed and missed calls , incomming calls with Names and i have a option to accept or decline a Call from the fis display , using my Multifunction Steering Wheel. Everything working perfect with my Xperia x1i.
Hmm
Most likely that module is a fiscon module or an older part of skoda. Am I correct?
The fiscon does not use rsap and older premium carkits from VW also did not. But their newest carkits included in the passat CC and skoda superb II are rsap only.
Quindor said:
Most likely that module is a fiscon module or an older part of skoda. Am I correct?
The fiscon does not use rsap and older premium carkits from VW also did not. But their newest carkits included in the passat CC and skoda superb II are rsap only.
Click to expand...
Click to collapse
Im not sure we can post a direct link here to another website , but there is what im using in my Jetta : http://www.kufatec.de/shop/product_....html/XTCsid/9f268df051bdc7806c7825cc426d606c
Old Version
Ah, yes. That is an orginal skoda part, but it is the older version from the Superb I and not the Superb II. That uses the other profiles and not rSAP.
touch HD behaves just the same
Hi everybody.
I had the chance to test both X1 (rSAP from cabs in post #3, thanks by the way) and HD (native rSAP implementation) on a VW touareg premium car kit and I must say they suffer from the same problems: most of the time the connection is established, but immediately drops and enters an endless loop of connection/disconnection, where everything can happen: car kit crashes, phone crashes, vodafone goes bankrupt, etc.
What hurts the most, though, is that very rarely and randomly, the connection with X1 is firmly established and everything, for unknown reasons, starts to work fine. This drives me crazy, for it would be a lot easier to cope if the feature wasn't available full stop.
Nonetheless, this makes me think a solution must exist somewhere, but I'm too much of a noob to find it...
Hope this helps, byebye.
Hey guys,
I'm trying to connect my HD Mini with my Audi's rSAP adaptor (which is located in the center arm rest, so it's not the Audi in-built MMI-phone module). As far as I know the rSAP adaptor is identical to the adaptors available for VW and Skoda cars(?).
My Mini ist Vodafone branded, the ROM-Version is 1.11.162.1 (87652) GER, Manila-Version is2.5.20131825.1.
All of the first attempts to connect by SAP failed. After entering the 16-digit pin the HD Mini shows a message that the "Sim-Access-Adapter" wants to use a SAP connection. After accepting this screen the Mini shows the SIM Access profile on the bluetooth configuration screen for less than a second and then the HD Mini falls back to a hands-free connection.
After playing around with settings, resetting both devices I gave up and started a support call at Audi and HTC. When Audi tried at least to provide some helpful information, HTC provided less than nothing, their DACH support totally refused to provide anything! :sad: My previous HTC devices all connected fine to the rSAP-adaptor (though they weren't listed to be compatible with the adaptor). My Rose worked fine for months and also my S710 (by using the additional rSap sw-tool) are still able to establish a SAP connection while the HD Mini can't.
Then occurred the strange thing: My Audi MMI display showed the network strength symbol which is only shown if the Audi phone module have booked into my provider's net correctly.
I looked at the rSAP module: Same thing. It actually has booked into the net, which means the adaptor was able to read the SIM-card information. Next look to the HD Mini's display: It was booked into the net too but showed the "Sim-Access-Adapter" connected with Hands-free mode.
Since I'm using a Vodafone twin-card contract (second card is currently unused) having 2 devices booked into the provider's net can be explained but of course this state was extremly unstable:
My car's adaptor catched an incoming call and when I spoke and heard the voice in my car's speakers the HD Mini stroke back, catched the connection including the ongoing-call and I needed to continue on the HD Mini, while the MMI car's display showed no connection anymore.
Just a few seconds later I must recognize that the battle wasn't over: The car adaptor catched the call, (right now without SAP-mode but Hands-free mode) and I heard my colleague on the speaker again...for 10 seconds and this toggled again and again...
Since my older HTC gadgets worked fine and also the HD Mini is showing the adaptor's attempt for a SAP mode connection but then falls back to Hands-free-mode, I think that there must be some changes on the phone, bluetooth stack implementation, perhaps something with WM 6.5, it simply looks like a timing issue?
So right now I'm hoping that anyone can provide something useful. Perhaps an expert can point me to the right direction?
My last try would be to clear my second SIM-card on the weekend so that there are no contacts - perhaps this can make the difference... :-\
Any help is greatly appreciated of course!
Thanks and cheers, Alf.
Btw: Great board with tons of helpful information!
Quick Update:
I completed a hard reset to Audi MMI, Audi rSAP-adaptor, HTC HD Mini and removed all contacts and SMS saved on my second SIM-card but unfortunately no change in the behaviour of the HD Mini.
But then surprisingly another HTC support guy dropped me a line today so it seems that my support call at HTC is currently still in progress although the first HTC support contact refused any help...so let's see and wait...
Cheers, Alf.
Hallo!
Did you get any useful information from HTC support?
I'm using a HTC HD mini in a new VW Sharan with Premium FSE (so via rSAP). In general it works, but ...
a) often the connection process fails and I have to klick on "connect" manually.
b) sometimes I only get a standard FSE connection (not premium) and when I leave my car for some minutes and come back, it works again with "premium"
c) sometimes my HD mini does not reactivate the phone module after I left my car.
Michael
Although they tried to help and provided a tracking tool which logged status information about the bluetooth communication stack I never received additional help after providing my bluetooth log.
I ended in using the HDMini with the Audi built-In Bluetooth module of the MMI instead of the rSap adapter. :-(
That way the internal antenna of the car is not in use but at least the MMI is displaying the phone contacts...
Cheers, Alf.
I'm starting a new thread on this because I think it is important and to gather together findings on this.
From early reports it seems that rSAP is not working for some people after upgrading to Froyo.
rSAP is not part of any Android build but is built in to the Galaxy S by Samsung, which is why it is the only Android phone to support this.
Samsung seem to say it is still there but all the reports I have read suggest otherwise, although one member has posted on this forum saying it works for him. This leaves us with four possibilities:
Some Bluetooth settings have changed which disable rSAP (I can find none.)
Some network settings have changed which disable rSAP. As rSAP is a GSM only protocol, which is why it doesn't work on 3, this is a possibility. I see the network setting is now for Auto GSM/WCDMA mode, which did cause problems on a previous Nokia with rSAP. Possibly changing to GSM only could resolve this.
Various builds of Froyo do not include rSAP. It is possible, for example, that the 3 build does not and the upcoming O2 build may include it.
Samsung really have made a rick and left it out of the build.
Currently my Mercedes-Benz is in for a respray and I have no way of testing any of this.
I'd be interested in hearing others experiences. This is a serious issue for me as I purchased the Galaxy S precisely because it did support rSAP. If it is now removed then the reason I bought the phone is gone and Samsung owe me a refund under the sale of goods act.
Just had a reply from Samsung support who say that if rSAP isn't working it is a software issue and to take the phone to a Samsung service centre. Given that the rSAP profile is a Samsung thing and not an Android thing perhaps this means some Froyo installations fail to initialize the rSAP profile.
So, for the avoidance of doubt, has anyone actually confirmed they've got rSAP working when running Froyo?
Someone has... reply #7
http://forum.xda-developers.com/showthread.php?t=824950
I can confirm that RSAP is working on my german I-9000. I am currently running Tayutamas Froyo (1.03) and using my phone with a VW PSFE. The issue that contacts are only imported from the sim card still remains.
So far all the reports of rSAP continuing to work after Froyo seem to be VW users. Mercedes-Benz, Audi and possibly Porsche seem to be the users reporting issues.
Just installed the VW 3C8035730A module to replace the rSap only 5N0035730C.
I have a HTC Touch HD that works as a rSap and a Iphone 4 that works as HF now. Android should should work i guess too.
You can read my post here: http://briskoda.net/forums/topic/182537-installed-rns510-module-3c8035730a-rsap-bluetooth/
Can anyone tell me if there is a technical reason Bluetooth SAP/rSAP cannot be delivered on the Windows Phone 7 platform, or are the just being lazy about delivering it??
So... no reply cause nobody knows or no reply cause I'm being a n00b and this is answered elsewhere? Or something worse?
http://lmgtfy.com/?q=rsap+windows+phone+7
Just follow the first link "Frage zu SAP..." (german)
So far only these BT profiles are implemented:
PBAP — Phone Book Access Profile
A2DP — Advanced Audio Distribution Profile
HSP — Headset Profile
HFP — Hands-Free Profile
AVRCP — A/V Remote Control Profile
Anything else would be speculation, because Mango BT updates known so far:
http://wmpoweruser.com/windows-phone-mango-bluetooth-stack-updated-but-not-much/
esackbauer said:
http://lmgtfy.com/?q=rsap+windows+phone+7
Just follow the first link "Frage zu SAP..." (german)
So far only these BT profiles are implemented:
PBAP — Phone Book Access Profile
A2DP — Advanced Audio Distribution Profile
HSP — Headset Profile
HFP — Hands-Free Profile
AVRCP — A/V Remote Control Profile
Anything else would be speculation, because Mango BT updates known so far:
http://wmpoweruser.com/windows-phone-mango-bluetooth-stack-updated-but-not-much/
Click to expand...
Click to collapse
Thanks - just saw that qualified listing and was a little disappointed. I checked the one for Apple iOS (listed as software version 4.1 and 4.2) and it also doesn't mention SAP or rSAP, but I know it does support those profiles, so I'm wondering whether I am just reading it wrong.
The differences are that iOS has:
RFCOMM
Bluetooth Network Encapsulation Protocol
Personal Area Networking Profile
HID
Interop Test Spec
Which one of these is linked to SAP/rSAP?
How do you "know" that iPhone supports rSAP? It does not, not even 4.3:
http://iamtim.de/2011/05/das-iphone-und-das-sim-access-profil-sap-oder-rsap/
None of these profiles you listed is rSAP (or SAP, SIM), as written here:
http://en.wikipedia.org/wiki/Bluetooth_profile#SIM_Access_Profile_.28SAP.2C_SIM.2C_rSAP.29
esackbauer said:
How do you "know" that iPhone supports rSAP? It does not, not even 4.3:
http://iamtim.de/2011/05/das-iphone-und-das-sim-access-profil-sap-oder-rsap/
None of these profiles you listed is rSAP (or SAP, SIM), as written here:
http://en.wikipedia.org/wiki/Bluetooth_profile#SIM_Access_Profile_.28SAP.2C_SIM.2C_rSAP.29
Click to expand...
Click to collapse
Well I suppose to be clear I don't "know", I just "think". The reason I "think" is because it communicates with my car, that says it "requires" SIM Access Profile, whereas my phone REFUSES to communicate with my car.
Additional detail: the car actually supports 2 bluetooth "modes": Headphone mode and SIM Access mode. If I have the car initiate the bluetooth connection it will use the remote SIM mode, and if the phone initiates the connection it will use the "headphones" mode.
A Nokia N97 works in both directions. As does the iPhone 3 and 4. My Samsung Omnia 7 won't do either.
Maybe Mango will be a solution, because it updates the Headset and Hands-free profiles.
"New is Hand-Free Profile 1.5, which should mean better support for Bluetooth car kits. "
Also there comes PBA (Phonebook Access profile), which is basically the same as SAP, but it uses the radio of the phone, instead the radio inbuilt to the car kit.
PBA and your interpretation of it being very similar to SAP sounds quite interesting yet it will most likely not be recognized by SAP-only car-kits like the older VW premium handsfree-boxes. I for instance refrain from switching to any other OS than windows Mobile simply because i need my phone working with the car kit and i am not going to buy a new car because my phone doesnt support the current.
Well, anyhow. I was going to say, that if the PBA doesn't support some kinda fake-SAp mode (pretend to be sap or so) it will most likely not help anyone with sap-only car kits. not matter how much it is similar to sap.
sorry to say this.
Sneakyghost said:
I for instance refrain from switching to any other OS than windows Mobile simply because i need my phone working with the car kit and i am not going to buy a new car because my phone doesnt support the current.
Click to expand...
Click to collapse
While i have both versions of Windows OS and yes the 6.x suported rSAP, the new WP7 does not. If you want a new phone that supports rSAP then Android fills the bill. Microsoft really dropped the ball by not supporting rSAP. Like you, have a VW-based phone system and without rSAP support the current handsfree phone protocols in WP7 is basically worthless.
[Update]
Just updated my phone to Mango, and annoyingly neither the headphone mode or reomte SIM modes work. This is a deal-breaker for me.
While I was quite enjoying the phone I am now going to switch to a Galaxy SII which works reliably in both directions, and connects properly to my WiFi as well. A real shame, but I can't imagine another WP update will be coming too soon and I don't have any patience left.
esackbauer said:
Maybe Mango will be a solution, because it updates the Headset and Hands-free profiles.
"New is Hand-Free Profile 1.5, which should mean better support for Bluetooth car kits. "
Also there comes PBA (Phonebook Access profile), which is basically the same as SAP, but it uses the radio of the phone, instead the radio inbuilt to the car kit.
Click to expand...
Click to collapse
Since update my Omnia 7 to Mango, I get a lot of "BT connection error" on my display car.
all working here.
car radio is a Kenwood.
Finally now the phone transmits the name of the song playing to the headunit! like windows mobile.
Voice comands thru the Headunit work amazing too.The other day i received an sms while driving, voice comand told me that there was a new sms from Ken,then it ask me if i wanted it read out loud! I said yes and it did, at the end it ask me if i want it to reply to.
Also this is the only phone that actually auto connects to the car stereo,all my android devices need to be reconnected manually.
Funny thing all of this was set up by just pairing the device with the headunit.
Well my "head unit" is integrated into the dash - it's a Porsche touch screen system called PCM (which I think, lamely, stands for Porsche Control Module). I have anecdotal evidence that other WP7 models will connect which makes me think it may actually be the Samsung Omnia 7 itself and not WP7 per se.
What sux is that my Samsung Galaxy S2 works perfectly and my wife's iPhone4 works perfectly. So it isn't the car.
...I really haven't got the patience to wait for the Win8 update and keep using headphones for the next year!
some news here?
Hi,
i own a D802 und used the Stock Rom for a while, switched to CM und now i am on ParanoidAndroid 4.0.
In every Rom i had i had the exact same issue: When i am pressing the call button on my Headset (original or extra one, doesn´t matter) or Hands-free kit (Parrot MKI9000) for a while to start speech recognize i just get an black/gray screen and in the middle there stands "Initialize" and a Voice tells my "please wait". Ok i thought, than wait. I even waited, not only once, like 30 Mins but nothing happens. I tried wiping cache and so on for google search, but without success - in fact, i thought so, because it happened on differend roms.
I downloaded the offline language(s) for recognizing and speaking, same problem.
Do you have any idea how i can solve this or what is causing the problem?
Thanks
Regards,
Erik
I never was able to make my Motorola Bluetooth to work. On Droid DNA or on G2. You may try to install apk from your Bluetooth manufacturer if they have one. As for mine, i don't like what they offer. To use Google Now, you should stark it manualy only as far as i know.
Melodycd said:
I never was able to make my Motorola Bluetooth to work. On Droid DNA or on G2. You may try to install apk from your Bluetooth manufacturer if they have one. As for mine, i don't like what they offer. To use Google Now, you should stark it manualy only as far as i know.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=46832417
Look at post #10 & #30