Related
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?
Tried to pair my Focus with some other bluetooth devices and failed. Did anyone managed to do this?
The scenario is always the same. I'm finding the other BT device on my Focus, the other device can detect my phone either, but when I try to pair them no chance. Always getting message "unsupported". (of course pins are matching). Tried to do it with my laptop, with my other Blackberry phone, even with my friend's android unit. What the... ?
edit: ok Found some info that WP7 wont support file transfer via BT. You may close this thread.
Not quite close it, it's useful info for others (it's also on Focus Wiki I believe).
BT is supported only for headsets and other WP7 devices but WP7 doesn't have a file stack so no transfers, so just handsfree/listening.
I recently bought Android HU for my mercedes E 2005 form Isudar China.
Android 8.0 Octa core 4gb Ram and 32GB rom with DSP.
After finishing installing it. I tried to turn on the WiFi but there was no way to turn it at all (it stay in off side). I also notice that the MAC address for the WiFi is 02:00:00:00:00:00 , which I think it is wrong. In the other hand the Bluetooth is working but i couldn’t use it for Internet (it work only for calling and music play) and I can’t send or receive any file using Bluetooth. I bought TB-link WiFi dongle but didn’t work I also tried to use 3G dongle, it also didn’t work. When I connected other device to USB (DAB) it works. I asked the seller what to do?! He didn’t give me answer. I need professional help. I don’t know if the problem is hardware or software. Because the device is totally new, and from beginning doesn’t work.. Every help is appreciated.
No one has or had the same problem?
Joying JY-VOS01N4GS w/ an SC-9853i 1.8GHz Octa-core, installed in a 1991 Toyota MR2 with a Honda K24A2 turbo engine swapped into it, controlled by an ECU called a Hondata KPro V4.
https://rover.ebay.com/rover/0/0/0?mpre=https://www.ebay.com/ulk/itm/143309152617
I can install and run Hondata or RealDash apps on the stereo without issue, but I can't get it to connect to the ECU itself so I'm looking for suggestions. I've got a $20 no name tablet or a 7+ yrs old Samsung Note 3....all connect to the KPro without issue. Hondata, RealDash and Torque apps all connect without issue on the tablet or phone. New $350+ stereo...keeps giving me failed to connect error.
I'm open to rooting if needed, installing a different Bluetooth app, I have the pin to access developer options, etc....I just need it to connect and work.
m5james said:
Joying JY-VOS01N4GS w/ an SC-9853i 1.8GHz Octa-core, installed in a 1991 Toyota MR2 with a Honda K24A2 turbo engine swapped into it, controlled by an ECU called a Hondata KPro V4.
https://rover.ebay.com/rover/0/0/0?mpre=https://www.ebay.com/ulk/itm/143309152617
I can install and run Hondata or RealDash apps on the stereo without issue, but I can't get it to connect to the ECU itself so I'm looking for suggestions. I've got a $20 no name tablet or a 7+ yrs old Samsung Note 3....all connect to the KPro without issue. Hondata, RealDash and Torque apps all connect without issue on the tablet or phone. New $350+ stereo...keeps giving me failed to connect error.
I'm open to rooting if needed, installing a different Bluetooth app, I have the pin to access developer options, etc....I just need it to connect and work.
Click to expand...
Click to collapse
It will not pair. Joying (actually FYT/SYU) crippled the bluetooth on their units. You can only pair with phones and a few OBD and TPMS BT devices.
For the rest: nothing.
And that is done onto the lowest compiled level including the MCU. Other drivers/apps/kernels/whatever will not work.
I've been writing Joying and they offered to sell me their OBDII dongle at a discount. I explained to them shortly before writing this post that the car doesn't have an OBDII port since it's a 91, lightly explained the engine sway, but I haven't heard anything yet. Why would they go through all that effort...just to force us to buy their $15 OBDII dongle?
What about universal Bluetooth dongle plugged into one of the USB cords? Or maybe even USB to USB? The ECU has a USB port that I use when I connect to my laptop to run KPro Manager (a Windows PC based program) and the RealDash app on Android does give me the option of Bluetooth, USB or serial input. I'm currently monitoring from this tablet which is completely illegible while driving, needs to be manually powered on/off and then reconnected to Bluetooth...not being able to see the gauges on a much larger screen and automatically reconnect when I start the car crushes EVERY reason why I bought this stereo. There's gotta be a way.
Wrote a long reply, stupid token expired...I'm gonna try this.
https://www.hondata.com/forum/viewtopic.php?t=18829
Bluetooth dongle didn't work, but I can't confirm if it's a dongle issue since I can connect to it but then the Hondata app says "Ignition not on" when it is. Nevertheless today I played around with the GF's cwr who has a Joying JY-HOS02P4 screen in hers, it's only 3 months old, and it'll connect to my Hondata just fine! Would it be as simple as taking the Bluetooth APK from her car and installing it on mine?
Bump for help...there's gotta be a way :/
Bumping again, hoping maybe someone can help.
Following - need this for ECUTEK bluetooth adapter in my GTR, otherwise the screen is worthless...
m5james said:
Bumping again, hoping maybe someone can help.
Click to expand...
Click to collapse
Like mentioned a couple of posts above. Joying crippled Bluetooth and there is simply no "normal" bluetooth stack.
You cannot alter the current BT app as it won't be signed correctly anymore and it will not even be visible anymore.
You cannot add another BT app as that will not have the correct signing either.
Your question is not new. This BT "not being able to pair" is already an issue since 2016. You would be the first to find a solution.
The only thing you can try is what I described in this post, based on info from ojuniour.
Having said that: you should also search the rest of the forum and not only stick to your own question. Otherwise you might already have tried what I described. It might work, it might not.
Surfer, thank you so much for the reply. I've read in depth and was fearful of that, but will try what is in the thread you linked. If you'd be so kind, couple questions that you may have answers to:
- I have a sofia 9853 with android 8.1 (upgrading to 9.0), does that make things better worse or same for the bluetooth situation?
- I've seen some talk on much older threads of using Comfast® CF-WU725B as an external/usb bluetooth solution? Did this (or an alternative dongle) ever or does it still work?
- I've also seen talk of used xposed modules to add bluetooth devices to the whitelist - is there any truth to this?
Surfer, thanks in advance, this is for a tesla screen in a GTR. By removing the stock screen we lose a ton of critical info that can only be gotten back through ecutek, which currently only has a bluetooth solution for android.
M5James - sorry for hijacking your thread, but hopefully this helps you as well
xadamadax said:
Surfer, thank you so much for the reply. I've read in depth and was fearful of that, but will try what is in the thread you linked. If you'd be so kind, couple questions that you may have answers to:
- I have a sofia 9853 with android 8.1 (upgrading to 9.0), does that make things better worse or same for the bluetooth situation?
- I've seen some talk on much older threads of using Comfast® CF-WU725B as an external/usb bluetooth solution? Did this (or an alternative dongle) ever or does it still work?
- I've also seen talk of used xposed modules to add bluetooth devices to the whitelist - is there any truth to this?
Click to expand...
Click to collapse
1. There is no Sofia 9853. There is a Intel Sofia AND an Intel SC9853i. Those are 2 different CPUs needing different ROMs.
2. No idea. Like mentioned: an external BT dongle has not worked till now, but I have never heard of that Confast one.
3. Xposed is not supported on the 9853i. Not on Android 8.1 and neither on 9.0
@surfer63, thank you again, your thread here (https://forum.xda-developers.com/an...qa-tips-info-roll-joying-fyt-sc9853i-t3979377) helped me tremendously
@m5james, on a whim i plugged in ecutek to usb via the usb mini port, and shockingly there is support for it. Maybe try the same with Hondata if there is an sort of interface on it.
surfer63 said:
Like mentioned a couple of posts above. Joying crippled Bluetooth and there is simply no "normal" bluetooth stack.
You cannot alter the current BT app as it won't be signed correctly anymore and it will not even be visible anymore.
You cannot add another BT app as that will not have the correct signing either.
Your question is not new. This BT "not being able to pair" is already an issue since 2016. You would be the first to find a solution.
The only thing you can try is what I described in this post, based on info from ojuniour.
Having said that: you should also search the rest of the forum and not only stick to your own question. Otherwise you might already have tried what I described. It might work, it might not.
Click to expand...
Click to collapse
Fair enough...honestly like 10 +/-yrs ago I was WAY more into custom ROMs, baking, etc etc but nowadays I feel like it's over my head again. The only reason why I asked about using other BT versions from other Joying devices is because the GF's similarily aged stereo was able to connect, but I understand the signing thing since our two stereos don't share the same OS and CPU.
xadamadax said:
M5James - sorry for hijacking your thread, but hopefully this helps you as well
Click to expand...
Click to collapse
You're fine, the more exposure the merrier...I'm not as good at this stuff as I used to be so I'm just hoping someone smarter than me can help
xadamadax said:
@surfer63, thank you again, your thread here (https://forum.xda-developers.com/an...qa-tips-info-roll-joying-fyt-sc9853i-t3979377) helped me tremendously
@m5james, on a whim i plugged in ecutek to usb via the usb mini port, and shockingly there is support for it. Maybe try the same with Hondata if there is an sort of interface on it.
Click to expand...
Click to collapse
Do you have a pic of how you physically hooked it up? I haven't touched much on this subject since my original post and honestly don't recall the connections at the moment but I do recall mine having a square port (I don't know it's official name) that allows me to connect via USB to a laptop. I think I even tried connecting directly to the stereo that way but no luck.
Hondata runs on the screen easily in both portrait and landscape mode but I prefer RealDash, which at doesn't like portrait mode...I'm hoping it's something I can adjust to fit myself since RealDash allows for customisable gauges.
@m5james that is a micro usb port you have, try connecting it to a usb port on the head unit (same way you would a laptop) and open your hondata app - with any luck you'll be in business. If one port doesn't work, try the other - good luck
If you guys want to use the bluetooth pairing with basically about anything then buy the "Stop" brand. Unit actually confess with 2 BT models. One for music and phone call, the other one is located in the android bluetooth setting that would enable you to pair with anything.
ojuniour said:
If you guys want to use the bluetooth pairing with basically about anything then buy the "Stop" brand. Unit actually confess with 2 BT models. One for music and phone call, the other one is located in the android bluetooth setting that would enable you to pair with anything.
Click to expand...
Click to collapse
I looked on eBay for "stop android DIN" and nothing comes up.
m5james said:
I looked on eBay for "stop android DIN" and nothing comes up.
Click to expand...
Click to collapse
lol my bad I mean Atoto.. Damn auto correction.
here is an example of one connecting to ecuTek obd bluetooth:
https://www.ft86club.com/forums/showthread.php?t=141515
xadamadax said:
@m5james that is a micro usb port you have, try connecting it to a usb port on the head unit (same way you would a laptop) and open your hondata app - with any luck you'll be in business. If one port doesn't work, try the other - good luck
Click to expand...
Click to collapse
Wait wait wait. Wait a minute.... Are you saying you are able to get the ecuTek OBD bluetooth to work in wired mode[ to the head unit] without connecting to it wirelessly through bluetooth?
And you are using the ecuTek App?
I cant find much info on this device so I figured I would ask here. I picked up one of those Carplay AI Box dongles for the car and am having an issue keeping a bluetooth connection. Im trying to connect to and ODB MX+ which is attached to my car, via bluetooth and an app like DashCommand. Only issue is everytime I restart the car I have to go into the pairing menu of DashCommand for it to reactiveate bluetooth on the Ai Box. For whatever reason it seems bluetooth just isnt staying on. Even when the app is running and its connected the bluetooth indicator on the MI Box is off.
psychoholica said:
I cant find much info on this device so I figured I would ask here. I picked up one of those Carplay AI Box dongles for the car and am having an issue keeping a bluetooth connection. Im trying to connect to and ODB MX+ which is attached to my car, via bluetooth and an app like DashCommand. Only issue is everytime I restart the car I have to go into the pairing menu of DashCommand for it to reactiveate bluetooth on the Ai Box. For whatever reason it seems bluetooth just isnt staying on. Even when the app is running and its connected the bluetooth indicator on the MI Box is off.
Click to expand...
Click to collapse
What device. You haven't listed what the device is details, what you've done to resolve it or what the reseller suggests.
You brought a cheap Chinese origin device and then expect support - do you realise xda isn't the seller or the support forum. What I mean by that is you have to put the effort in to get help
Wake up on the wrong side of bed today or whats your deal?
I came here asking for help which I've done multiple times over the years, never once getting such a crap response. Yes, I bought a cheap Chinese android device, have you never purchased anything from China? I bought it because from the limited info on the internet it seemed to be the fastest one out there with the Snapdragon 665 cpu. If there was a better one made my Samsung or whoever I would have bought that but they dont exist so excuse me for buying somethign from China.
Any why on earth would I assume XDA is the reseller? There are literally hundreds of thousands of threads on this site of people asking for help with something they didnt buy from XDA so no idea why the hostility.
Thanks for your worthless reply, why did you even bother?
You could try one of the 'Bluetooth auto connect' apps on the Play Store.
But what I would do is use Tasker. Setup a profile with tasks that: turns on Bluetooth, then connects to your ODB device. And set the profile to activate when the display is 'on'.
You lucked out with yours as my CarPlay AI box doesn't even allow more than one device to be paired...so I've been unable to even pair my ODB reader.