Infeasible
Status Update
Comments
dn...@google.com <dn...@google.com>
dn...@google.com <dn...@google.com> #2
Hi,
Thanks for reporting this issue. Can you provide the below requested information to better understand the issue:
Android bug report
After reproducing the issue, press the volume up, volume down, and power button simultaneously. This will capture a bug report on your device in the “bug reports” directory. Attach the bug report file to this issue.
Alternate method:
After reproducing the issue, navigate to developer settings, ensure ‘USB debugging’ is enabled, then enable ‘Bug report shortcut’. To take bug report, hold the power button and select the ‘Take bug report’ option.
NOTE:
Please check the issue on Nexus/Pixel devices on latest android Oreo build and let us know the result. If issue reproduces, please share bugreport for the same.
Thanks for reporting this issue. Can you provide the below requested information to better understand the issue:
Android bug report
After reproducing the issue, press the volume up, volume down, and power button simultaneously. This will capture a bug report on your device in the “bug reports” directory. Attach the bug report file to this issue.
Alternate method:
After reproducing the issue, navigate to developer settings, ensure ‘USB debugging’ is enabled, then enable ‘Bug report shortcut’. To take bug report, hold the power button and select the ‘Take bug report’ option.
NOTE:
Please check the issue on Nexus/Pixel devices on latest android Oreo build and let us know the result. If issue reproduces, please share bugreport for the same.
ma...@gmail.com <ma...@gmail.com> #3
Hi, hopefully this has what you need. I'm sure you can tell from the log but to clarify: I enabled logging, switched on Bluetooth, the phone connected to the car as regular hands free, I selected rsap Bluetooth in the car, it tried 3 times to connect and then failed.
Thanks.
Thanks.
dn...@google.com <dn...@google.com> #4
We have passed this to the development team and will update this issue with more information as it becomes available.
ma...@gmail.com <ma...@gmail.com> #5
I have today upgraded to android 8.1 beta and the issue is resolved.
Thanks
Thanks
fe...@gmail.com <fe...@gmail.com> #6
i have the same problem with HUAWEI MATE 10 PRO with Oreo
jo...@gmail.com <jo...@gmail.com> #7
I have the same Problem on Nokia 6
at...@gmail.com <at...@gmail.com> #8
I have the same problem on my Samsung S8+ with Oreo (and my Audi Q5 Car). Rsap profil BT is never activited.
fr...@gmail.com <fr...@gmail.com> #9
I have the same problem with Skoda Yeti (2014), but with PIXEL 2 (Android 8.1.0)
fr...@gmail.com <fr...@gmail.com> #10
And, unfortunately, the same problem with Samsung tablet TabS2, Android 7, NO SIM card, no connection with my Skoda Yeti (2014). Samsung Galaxy S 5 phone (Android 7) works perfectly.
st...@gmail.com <st...@gmail.com> #11
I have the same Problem on Nokia 5. #9 has the same problem with android 8.1? I thought that the update to 8.1 would fix the rsap problem.
ma...@gmail.com <ma...@gmail.com> #12
Also got the same problem with Nokia 6 and 2016 Audi A4. The phone appears disconnected and the phone directory is emptied.
ph...@googlemail.com <ph...@googlemail.com> #13
I updated my Nokia 5 to 8.1 and the problem is not resolved.
st...@gmail.com <st...@gmail.com> #14
I also updated my Nokia 5 to 8.1 and the problem is still the same !
se...@gmail.com <se...@gmail.com> #15
Same on Nokia 6 TA-1033 with 8.1.0 vs. VW. Phone is not compatible ....
jo...@gmail.com <jo...@gmail.com> #16
Same issue on Nokia 6 TA-1021 with 8.1.0 in my VW Passat. 'Phone not compatible' but it was working when I had the phone with android 7.
in...@83555.at <in...@83555.at> #17
Nokia 5 Oreo 8.1 TA-1053 Build 00WW_5_580 problem NOT solved, still no rSAP connection possible, BT rSAP profile missing
in...@83555.at <in...@83555.at> #18
Build info: TA-1053_00WW-user 8.1.0 OPR1.170623.026 00WW_5_580 release-keys
Serial number: D1AGAD1772807001
Serial number: D1AGAD1772807001
fr...@gmail.com <fr...@gmail.com> #19
I vor the same Problem. Updated my Nokia 5 to Android 8.1 and it is Not compatible to my Car. In Android 7 it worked fine. Please solve this!
sa...@gmail.com <sa...@gmail.com> #20
Same problem here with Nokia 6 TA-1033 with android 8.1 having the latest security update installed.
ne...@gmail.com <ne...@gmail.com> #21
Same problem here with Nokia 6.1 TA-1043 with android 8.1 having the latest security update installed.
ec...@gmail.com <ec...@gmail.com> #22
rsap does not work with Nokia 5 and latest security update as of today
mm...@gmail.com <mm...@gmail.com> #23
Hi,
Issue is still visible with Oreo 8.1.0 with June security update.
This functionality used to work with Android Nougat 7.1.1 (and if I remember correctly 7.1.2).
With upgrade to 8.0 followed by 8.1 this feature stopped working.
Could somebody at least say if this is planned to be resolved in the future?
Or should we throw those phones into garbage as due to SW changes they are not usable anymore?
Issue is still visible with Oreo 8.1.0 with June security update.
This functionality used to work with Android Nougat 7.1.1 (and if I remember correctly 7.1.2).
With upgrade to 8.0 followed by 8.1 this feature stopped working.
Could somebody at least say if this is planned to be resolved in the future?
Or should we throw those phones into garbage as due to SW changes they are not usable anymore?
al...@gmail.com <al...@gmail.com> #24
I have the same problem, the RSAP support was removed...
I use Android 7.0 with Sansung J7
Please solve this...
I use Android 7.0 with Sansung J7
Please solve this...
a....@gmail.com <a....@gmail.com> #25
Same problem on galaxy s7 after upgrade to android 8.0.0. It was working fine before the update.
ma...@gmail.com <ma...@gmail.com> #26
The same issue - Nokia 6 upgraded to android 8.0 - could anybody give an information if it is planned to be corrected? Thanks.
ka...@gmail.com <ka...@gmail.com> #27
no rSAP with Nokia 5 DualSim and Android 8.1
in...@bluemagicwaves.info <in...@bluemagicwaves.info> #28
Please fix rSAP in new android version . Especially in combination with dual sim phones .
eh...@gmail.com <eh...@gmail.com> #29
Hi, same Problem with Gigaset GS185, is there a timeline when this will be solved?
a....@gmail.com <a....@gmail.com> #30
Updated oreo on samsung s7 today and problem is still there. Rsap connection drops shortly after successfully connecting to car.
a....@gmail.com <a....@gmail.com> #31
One more firmware update for the Samsung S7 today and rsap still dropping connections. Come on Google, put this back working already!
[Deleted User] <[Deleted User]> #32
Nokia 7 Plus with 8.1 the same Problem, no rSAP on my VW
lu...@gmail.com <lu...@gmail.com> #33
Connection with rSAP BT profile does not work since upgrade to Oreo 8.1.0. Phone Nokia 7 plus. Bluetooth device: RNS310 - handsfree infotainment in VW Golf VI.
a....@gmail.com <a....@gmail.com> #34
Another update for samsung galaxy s7 yesterday and no fix. This needs to be fixed in 8.0 Google, because it was working perfectly in android 7 until you broke it in devices like the s7, which are not going to receive an update to 8.1.
ni...@gmail.com <ni...@gmail.com> #35
Same Problem here. RSAP worked on Android 7 on VW Golf Mk6 but stopped working on Oreo.
is...@google.com <is...@google.com>
vi...@google.com <vi...@google.com>
a....@gmail.com <a....@gmail.com> #36
Another update for the S7 today and still no fix in oreo 8.0. How many more months until you fix what you broke, google?
vi...@google.com <vi...@google.com> #37
Thanks for the feedback. Due to other priority features, we're not currently able support your request. Please feel free to re-open the issue in the future if desired.
a....@gmail.com <a....@gmail.com> #38
Not a priority? That's not nice google. The bluetooth connection was working fine before the 8.0 update so the least you can do is fix it.
m....@gmail.com <m....@gmail.com> #39
What is the crap? This is a bug and a big one and it needs to be fixed.
a....@gmail.com <a....@gmail.com> #40
Not only a bug, it's a.bug that Google introduced in an update, this breaking a feature that we need. It must be fixed.
mm...@gmail.com <mm...@gmail.com> #41
Can you tell us what this bug is about? Is there any workaround for that? Could 3rd party SW fix that somehow with an app? Is it in protocol somehow? in BT stack? or what is the problem here?
a....@gmail.com <a....@gmail.com> #42
Perhaps Samsung can fix it. In the past when there was no support for rsap in Android, Samsung added rsap to its phones, at.least the s3 and the note 4 which I used in my car everyday. Never buy google devices as google screws them and takes no responsibility.
Description
If I select rsap profile in the car it connects on the phone as it used to but then disconnects a second later. This repeats 3 or 4 times untill the car gives up. When connecting I get the message on the phone stating that the car is accessing the SIM and tap here to disconnect. It then switches to 'waiting for client to disconnect' like something has requested disconnection but I have not asked it to.
I have a galaxy s8 still running android 7 and rsap works fine. I have factory reset my Nokia and reset the Bluetooth in the car but still not working.