Hi. I use rSAP (remote sim access protocol I think) connecting to my Audi. Does anyone know if the s6 supports this please?
Thanks.
Sent from my Passport using Tapatalk
uktivo said:
Hi. I use rSAP (remote sim access protocol I think) connecting to my Audi. Does anyone know if the s6 supports this please?
Thanks.
Sent from my Passport using Tapatalk
Click to expand...
Click to collapse
yes, i can confirm this is working with my s6 and my audi a4 with the mmi 3g+ as expected. also heard, that it works on the s6 edge, too.
I can also confirm the rSAP works quite fine with the S6 Edge. Phone, SMS, 3G on a Volkswagen.
So far, I'm only stuck with trying to setup bluetooth DUN back to the phone ! Otherwise, I loose the internet access on the phone.
If someone has a clue, it is more than welcome.
kreilinger said:
yes, i can confirm this is working with my s6 and my audi a4 with the mmi 3g+ as expected. also heard, that it works on the s6 edge, too.
Click to expand...
Click to collapse
What did you do to setup your S6 phone? I have the S6 edge and Audi RS5 and can connect to the car system but not able to use my cell SIM for the car network. Thanks
gee92 said:
What did you do to setup your S6 phone? I have the S6 edge and Audi RS5 and can connect to the car system but not able to use my cell SIM for the car network. Thanks
Click to expand...
Click to collapse
did you order your car with the audi connect option? if not, your navigation system does not have the ability to establish a connection by itself. you can easily determine this by looking at the front of the unit. if there is a sim-slot between the two sd-slots, it should work as expected. otherwise (only two sd-slots) your mmi cannot establish a connection by itself. (missing gsm-device)
kreilinger said:
did you order your car with the audi connect option? if not, your navigation system does not have the ability to establish a connection by itself. you can easily determine this by looking at the front of the unit. if there is a sim-slot between the two sd-slots, it should work as expected. otherwise (only two sd-slots) your mmi cannot establish a connection by itself. (missing gsm-device)
Click to expand...
Click to collapse
Yes, my car have Audi connect with the T-Mobile sim in it but the service is bad in my area only 2g half of the time.
i sometimes have the problem that the mmi sticks to its internal data connection even when my phone is connected in rsap mode. usually ejecting the sim from the mmi and reconnecting the phone fixes this
kreilinger said:
i sometimes have the problem that the mmi sticks to its internal data connection even when my phone is connected in rsap mode. usually ejecting the sim from the mmi and reconnecting the phone fixes this
Click to expand...
Click to collapse
I tired removing the T-Mobile SIM and still not able to get my S^ to work with my Audi and can someone send me the instruction if you where able to connect your cell. Thanks!
Sorry to revive this old topic. I have galaxy s6 and for some reason it will not share the data connection through Bluetooth with my audi car. Are there steps to take to activate rsap?
thx
@shadow except allowing rsap from the S6 in the Audi Bluetooth device. I'm not aware of something else. This is my setup in my VW
Envoyé de mon SM-G925F en utilisant Tapatalk
Bluetooth Remote SIM Access Profile on audi a8 d3 2003
Sent from my SM-G925F using Tapatalk
Related
Sometimes I want my Galaxy S2 to connect to my carkit (Nokia 616) using the normal HFP (not using rsap), so my phone doesn't loose its internet connection and I can use Google Maps etc.
However, since the Nokia 616 has no way of disabling rsap, I have to disable rsap on the phone. Does anybody know of a way to disable rsap on the Galaxy S2 so it connects using HFP with my carkit?
Any luck with finding a solution?
I have been trying to find a work around to this since June, can't believe there is no option to disable remote sim mode in either device... We must be the only people in the world struggling with this because there is nothing out there... emailed Samsung got no reply, called Nokia and spoke to the most unhelpful support person i have ever dealt with...
I did read in the Nokia 616 Manual however that in order for remote sim mode to work you need to have an external antenna connected... so i am going to try and disconnect the external antenna in the hope that the 616 recognises that its not connected and disables remote sim mode... its a long shot but im at breaking point...
I'm struggling to believe there is no command line method to disable or remove rsap on a rooted galaxy s, if I could get a lead at least i would look into it myself.
Found a way
See my post below
http://forum.xda-developers.com/showpost.php?p=17416532&postcount=3
I want to use the built-in wifi hotspot in my SGS3.
My laptop is an old Acer Travelmate 4100, which supports only 802.11b/g. It is abe, though, to connect to my wireless 802.11n router without problems (I suppose there must be backwards compatiblity).
But I can't connect to my SGS3 in tethering mode. It detects the hotspot but it timesout connecting.
I have also tested USB and BT tether and it works OK, so at least I have this little "workaround".
I set the hotspot as open just to make things easier.
Anyone has tried the built-in wireless tether in the SGS3?
Anyone has tried another wireless tether app?
I have tried Wireless Tether for root users and it doesn't work.
By the way, my phone is rooted.
Thanks.
mine works fine but im not rooted
Not sure if it applies to you but I would try again with a password for the hotspot. Some roms don't seem to want to let a connection happen without it.
krabman said:
Not sure if it applies to you but I would try again with a password for the hotspot. Some roms don't seem to want to let a connection happen without it.
Click to expand...
Click to collapse
I have already tried with a password
Enviado desde mi GT-I9300 usando Tapatalk 2
I know it seems crazy but if you have vista or 7 try a password with at least 8 letters and one number or symbol. Also change the hotspot name to something else and try both wpa and wpa2. If that doesn't get it then its likely not one of the usual password snafus keeping it from connecting.
krabman said:
I know it seems crazy but if you have vista or 7 try a password with at least 8 letters and one number or symbol. Also change the hotspot name to something else and try both wpa and wpa2. If that doesn't get it then its likely not one of the usual password snafus keeping it from connecting.
Click to expand...
Click to collapse
Just tried, no luck
faulty device ?
pinmemo said:
faulty device ?
Click to expand...
Click to collapse
I hope this is not the case.
I've found a workaround, though. I can use a USB cable or Bluetooth. Both of them work OK.
Maybe it's wifi standard related, as my laptop only supports 802.11b/g connections, and I don't know if my phone is capable of running only in b/g standard.
Also, the phone wifi connection works flawlessly with my home cablemodem.
I'm thinking about flashing a different firmware so I can test if it software or hardware related. Does Omega 3.0 firmware support wifi tethering?
Wait!. I'm going to test if my wife's SGS2 can connect to my SGS3's wifi hotspot!.
Oh, yeah!. It works!. So it's not hardware related, but software. My laptop also can connect to my wife's SGS2 wifi hotspot (as used to do, by the way).
Weird....
Galaxy S3 tethering doesn't work
I have exactly the same issue for tethering on Samsung's GS3. Bluetooth, USB tethering works fine.
Wifi tethering:
WPA2 - doesn't work, no clients can connect (password >8 alphanum chars)
WPA - doesn't work, no clients can connect (password >8 alphanum chars)
Open - works for connecting a single Win7 x64 client only.
iPhone, iTab, Nokia E72, Blackberry cannot connect to either of those above although it sees the AP.
The same SIM card (converted back to normal size SIM) works fine with tethering on Samsung Galaxy S1/S2. This is a pure GS3 issue.
I purchased the phone from FNAC in Madrid (no contract) and has current configuration:
Android version: 4.0.4
Baseband model: I9300XXLE8
Kernel version: 3.0.15-554452-user
Build number: IMM76D.I9300XXALE8
No ideas on what else can be tried... looks to be hardware/software bug...
Paktas said:
I have exactly the same issue for tethering on Samsung's GS3. Bluetooth, USB tethering works fine.
Wifi tethering:
WPA2 - doesn't work, no clients can connect (password >8 alphanum chars)
WPA - doesn't work, no clients can connect (password >8 alphanum chars)
Open - works for connecting a single Win7 x64 client only.
iPhone, iTab, Nokia E72, Blackberry cannot connect to either of those above although it sees the AP.
The same SIM card (converted back to normal size SIM) works fine with tethering on Samsung Galaxy S1/S2. This is a pure GS3 issue.
I purchased the phone from FNAC in Madrid (no contract) and has current configuration:
Android version: 4.0.4
Baseband model: I9300XXLE8
Kernel version: 3.0.15-554452-user
Build number: IMM76D.I9300XXALE8
No ideas on what else can be tried... looks to be hardware/software bug...
Click to expand...
Click to collapse
Well, in my case it works when connecting from another phone (my wife's SGS2). So it looks like it's software or configuration related...
Enviado desde mi GT-I9300 usando Tapatalk 2
wifi tethering
doesnt´t work for me either (stock, unrooted).
wifi teth does NOT work for me with my mac, pc, and some other mobiles that i tried. (All Encryptions )
neither does bluetooth tethering with my mac (usb as well but i guess that story is apples fault).
usb works on my pc (win7 x64) .
Anyone else can confirm this problem?
Beside this the Button Layout in the wifi-tethering config screen is quite weired. So i really think something really buggy in there.
thanks
quok
No problems here. Wifi hotspot set up on S3, set to WPA2, password over 8 characters with a mix of letters and numbers, TouchPad is happily connected to it. I'm on stock XXALF2.
Sent from my CM9 TouchPad
Hi,
USB & Wifi tethering doesn't work for me with rom omega 5.2 (or official XXALE8 and XXALF2) but on Cynaogenmod 9 (21/06) it's working fine...
Having connection problems as well. Seems to be a Samsung problem because when I loaded the app FoxFi I had no problem using WiFi tethering. Hopefully they fix this soon.
FoxFi app worked for me on stock.
Sent from my SAMSUNG-SGH-I747 using XDA
Ok I'm having the same problem.
I found this link
http://www.bytewiki.com/how-to-fix-wifi-connection-problem-in-samsung-galaxy-s3/
Basically:
1. Go to dialer, type *#0011#
2. Hit the MENU button and select Wifi
3. At the bottom of the screen is the button for Wifi Power Save Mode. Turn it off.
4. Back out of the menu.
5. Try tethering.
While it seems to have improved the reliability of the connection, the connection seems extremely slow and laggy compared to the connection I had with my Sensation.
Feedback from anyone?
Conundrum68 said:
Ok I'm having the same problem.
I found this link
http://www.bytewiki.com/how-to-fix-wifi-connection-problem-in-samsung-galaxy-s3/
Basically:
1. Go to dialer, type *#0011#
2. Hit the MENU button and select Wifi
3. At the bottom of the screen is the button for Wifi Power Save Mode. Turn it off.
4. Back out of the menu.
5. Try tethering.
While it seems to have improved the reliability of the connection, the connection seems extremely slow and laggy compared to the connection I had with my Sensation.
Feedback from anyone?
Click to expand...
Click to collapse
It didn't work, but I have found the culprit: the kernel. I was using a custom kernel (siyah). I have gone back to the stock kernel and now it works ok. I hope this is fixed in next releases of the kernel. I have also tested with other custom kernels and it happens the same.
Enviado desde mi GT-I9300 usando Tapatalk 2
I'm on ALE8 with Siyah-Kernel and it works without issues, not even dropping data connection once over several hours as was the regular issue with my S1.
At the moment i believe you must have root to wifi tether via foxfi, FoxFi devs seem to be aware of the issue based on their notes on their bin link, stating "*Support for the new Galaxy S3 and the new ICS update for Epic Touch are being worked on. Should be compatible soon in a future update."
Same issue on stock rom and kernel for me. Other Android devices connect fine as does a newer Samsung laptop. But an older laptop with Intel B/G adapter running Win7-home prem 32 bit will not connect. Whether open, wpa2, b only, g only, .... My HTC Evo 4G has no problem connecting to any device.
(posted this in the wrong forum earlier)
Is there a way to disable the remote sim protocol on the S3? My carkit (RNS510 premium from Volkswagen) connects via this protocol but it's not the preferred method. There is a workarround, i can manually disconnect and then connect to the carkit via the phone (i think it connects via a2dp or something), but it's bit of a hassle. If I could just disable rsap my carkit will automaticlly connect via the other protocol (like it connects with an iphone)
If your phone is rooted you can rename /system/lib/bluez-plugin/sap.so. This should remove the SAP profile from your phone. Perhaps you have to repeat the pairing.
forza11 said:
(posted this in the wrong forum earlier)
Is there a way to disable the remote sim protocol on the S3? My carkit (RNS510 premium from Volkswagen) connects via this protocol but it's not the preferred method. There is a workarround, i can manually disconnect and then connect to the carkit via the phone (i think it connects via a2dp or something), but it's bit of a hassle. If I could just disable rsap my carkit will automaticlly connect via the other protocol (like it connects with an iphone)
Click to expand...
Click to collapse
I am so happy that rSAP is available now - before I had to root and install 3rd party software. But usually you can decide while pairing which mode you like - at least my Audi asks which connection mode I would like. Maybe you have to unpair first on both devices and the pair again.
Out of interest: Why is rSAP not your preferred method? The phone itself uses less energy, reception is better due to the build in antenna and also the phonebook features are available in the car.
The only reason for me would be the lack of data connection on the phone which is only true if your car does not provide the Wifi Hotsport function - with this my S3 is connecting to the Internet and also the car has access for online traffic info, Google Earth, etc...
bbathome said:
I am so happy that rSAP is available now - before I had to root and install 3rd party software. But usually you can decide while pairing which mode you like - at least my Audi asks which connection mode I would like. Maybe you have to unpair first on both devices and the pair again.
Out of interest: Why is rSAP not your preferred method? The phone itself uses less energy, reception is better due to the build in antenna and also the phonebook features are available in the car.
The only reason for me would be the lack of data connection on the phone which is only true if your car does not provide the Wifi Hotsport function - with this my S3 is connecting to the Internet and also the car has access for online traffic info, Google Earth, etc...
Click to expand...
Click to collapse
Grrr, why it does not want to work with MMI on A7? and he wants have disconnected, doh
I made the update, but nothing. It fails after the request of 6 digit PIN (indeed, I had 16 digits on my old BB Storm). Also with that 3rd party app, it doesn't work... what car do you have and what did you exactly to make it works?
Thanks.
Oooh...which firmware version did rsap support come in?
Sent from my GT-I9300 using xda premium
XXB LG8 for sure.
Will you try?
Sent from my GT-I9300 using xda app-developers app
Galaxy SIII x RSAP Vollks
forza11 said:
(posted this in the wrong forum earlier)
Is there a way to disable the remote sim protocol on the S3? My carkit (RNS510 premium from Volkswagen) connects via this protocol but it's not the preferred method. There is a workarround, i can manually disconnect and then connect to the carkit via the phone (i think it connects via a2dp or something), but it's bit of a hassle. If I could just disable rsap my carkit will automaticlly connect via the other protocol (like it connects with an iphone)
Click to expand...
Click to collapse
Hi there!
My name is Andre and I installed a Volkswagen Bluetooth kit with the remote SIM feature.
As I paired my Galaxy SIII with the kit, my phone asked me a couple of things that I auto answered yes...
The first one was about giving permission to access my SIM.
After that my phone always entered in remote SIM mode with the kit.
Today I remade the pairing and when my phone asked to enable access to the kit for my SIM... I answered NO (and checked the box "do not ask me this again").
Now me, my phone and my car seem to be understanding each other.
Hope that this was of any help,
Andre
So I got a Gear S, paired it with my Galaxy S4 and S-Voice seemed to work well at home, but I found that it didn't work when I was outside. Nothing about S-Voice worked when I was out (except the wake up command "Hi Gear"). Doing a bit of testing I found that it worked when my phone was on Wi-Fi but it didn't work when my phone was switched to data. Oddly enough, S-Voice works from my phone regardless of the Internet connection it has, so this seems to be an issue with the Gear S. The error message I am getting on my Gear S is "Could not find network connection." Any ideas? Tips? Advice? (besides avoiding Samsung's crap, because that's all I've been hearing until now...)
On your gear is your mobile clicked on?
GeeZnU said:
On your gear is your mobile clicked on?
Click to expand...
Click to collapse
If you mean connected, then yes, they are connected. If I go to "Phone" on my gear and look for a contact and dial it, it finds the contact and dials using my phone. I control the music, etc, from my Gear without issues.
The only exception appears to be S-Voice on my Gear when the phone is using the data connection. This particular case is the only one not working.
fardelian said:
If you mean connected, then yes, they are connected. If I go to "Phone" on my gear and look for a contact and dial it, it finds the contact and dials using my phone. I control the music, etc, from my Gear without issues.
The only exception appears to be S-Voice on my Gear when the phone is using the data connection. This particular case is the only one not working.
Click to expand...
Click to collapse
Hmm, I'd say try resetting the gear
GeeZnU said:
Hmm, I'd say try resetting the gear
Click to expand...
Click to collapse
Same thing. I just reset the Gear to factory settings, re-connected it to my phone and when I disable the Wi-Fi on my phone, S-Voice on my Gear doesn't work (it still work on my phone). The error message it says is exactly this: "I can't find a network connection / Please connect and try again."
I also did a software update (it did update the firmware) but the problem persists.
I bet Samsung didn't even test this case. It seems like they just rushed everything to get the Gear S on the market and didn't give testers enough time to do proper testing and they didn't listen to any UX feedback.
Fixed!
I figured it out. ROOT REQUIRED.
For some reason the firmware was blocking my phone from sharing its data Internet connection. After a lot of digging I found that it has something to do with carriers, so at first I contacted tech support and they told me that "Portable Wi-Fi hotspot is definitely supported" and it's not blocked by them, which meant they weren't blocking Bluetooth tethering. To me it's still not clear whether or not the carrier can/could fix the issue, but I was sure it was a software issue so I kept searching for Wi-Fi hotspot apps and read as much as I could about them to avoid purchasing a bunch of useless apps. One of these apps got my attention as I read its description, before I even looked for more details:
This app will bypass all the apn restrictions for mobile tethering, recently included in Android releases.
Click to expand...
Click to collapse
Here is how I got S-Voice to work on my Gear S:
Root the phone
Install the Free Tethering Unlocker *ROOT* app from play.google.com/store/apps/details?id=net.kernelxp.freetether
Install BusyBox (required by the unlocker app) from play.google.com/store/apps/details?id=stericson.busybox
Open the Free Tether Unlocker app and press the "Unlock my Tethering!" button
For some reason the Wi-Fi hotspot doesn't work at all any more (I can't see my phone as a hotspot, but I could see it and connect to it before, except I didn't get any Internet access on my laptop) but Bluetooth tethering works so now I can access the Internet with my laptop and I can use S-Voice on my Gear S. I'm still not sure why tethering didn't work by default because I got the phone without a contract and I didn't see any signs that it wouldn't work - it simply didn't without a warning.
I'm sorry for text links, the forum prevents me from posting externallinks.
I passed by Galaxy S6 Edge to Galaxy S6 Edge+ and I do not work more calls and notifications remotely with Gear S .
Before when I walk away from the range of the bluetooth with the Galaxy S6 Edge could perfectly to have call forwarding and notifications, now with Galaxy S6 Edge+ I get the message that you can not make the call diversion etc etc. connect to Bluetooth.
You have done the same experience?
You know the reasons and solutions?
Thanks for the reply
( * Please forgive Google Translate for the bad translation)
Same with me. Moved from the note 4 to S6 Edge+ and once disconnected from blue tooth it fails to connect remotely...
I was having this issue at first but I got it to work, and now it's fine everytime.
Make sure the watch is on, and connected via Bluetooth. Then in the Gear S app, select "remote connect" so that it turns the option on. Then go to "auto call forwarding" and turn that on.
Then walk away until the Bluetooth disconnects. It will appear that remote connection is not working. Then walk back to your phone until Bluetooth reconnects. Then turn off remote connect (without turning off auto-call forward). Then turn remote connect back on. Then go to auto call forward and turn it on again. Viola, works.
ingenious247 said:
I was having this issue at first but I got it to work, and now it's fine everytime.
Make sure the watch is on, and connected via Bluetooth. Then in the Gear S app, select "remote connect" so that it turns the option on. Then go to "auto call forwarding" and turn that on.
Then walk away until the Bluetooth disconnects. It will appear that remote connection is not working. Then walk back to your phone until Bluetooth reconnects. Then turn off remote connect (without turning off auto-call forward). Then turn remote connect back on. Then go to auto call forward and turn it on again. Viola, works.
Click to expand...
Click to collapse
I'm sorry but no, your method does not work!
I tried several times to do what you advice, but the remote connection is not activated from my Gear S and my S6 Edge +
ddborello said:
I'm sorry but no, your method does not work!
I tried several times to do what you advice, but the remote connection is not activated from my Gear S and my S6 Edge +
Click to expand...
Click to collapse
Worked for me. Bummer, sorry!
Still works perfect. Gear S + Galaxy Edge+ (T-Mobile)
Perfect! "Magically" now it works perfectly diverting calls and notifications remotely.
Try it yourself, probably there has been some change in the server Samsung with admission at the service of the Galaxy S6 Edge +
Can people confirm that it is working now?
LuisLJ said:
Can people confirm that it is working now?
Click to expand...
Click to collapse
no working for me , I reset the Gear S , Reset my Note 5 , nothing work Gear App don't connect by Bluetooth , said not find Gear , I uninstall Gear App , reinstalled not work
Well I've been using remote connection for the past week and it works flawlessly on the S6 Edge+
Sent from my iPad using Tapatalk
Remote connection and call forwarding confirmed working on Sprint Note 5 paired with AT&T Gear S. No issues so far. Their was a small update to Gear Manager a couple days ago too.
Can't connect gear s to my s6 edge
i can't connect my gear s to s6 edge. my phone firmware is : lollipop 5.1.1
and my phone have an updated version of gear manager (version 2.2.15092142)
error while i'm trying to connect " check if your phone is compatible and if the samsung gear app need to be updated, then try again"
anyone please help me out
thanks
Bunk, this works 100% for me since day 1. No issues whatsoever with both on stock