Skip to content

Bolero bluetooth problem !

Featured Replies

A2DP is not supported by any skoda kit.

How did you pair your phone, if the phone option is not in the menu.

I have a 60 plate octy elegance with bluetooth and A2DP works fine with my iphone4

also i get texts show up in the maxidot ( which can be read out by the bluetooth, very amusing ) havn't tried doing a reply yet

Edited by boilerman

I have a 60 plate octy elegance with bluetooth and A2DP works fine with my iphone4

also i get texts show up in the maxidot ( which can be read out by the bluetooth, very amusing ) havn't tried doing a reply yet

Boilerman,

Can you offer wisdom on getting the iphone to stream music via bluetooth? I can get it to stream like it was a receiver, but I can't get it to allow me to start/stop, choose tracks, or go into the menu like I can with the Media player when it's connected via cable.

Also, did you do anything to get SMS to show up via bluetooth?

Otherwise the iphone/Bolero integration is truly superb in my Octavia.

mmmm so what do u think

is it worth it to change to GSMIII for the sake of sms reading while driving ? or shall one settle with factory fit GSM II ?? :wonder:

No. GSM III is only good on paper. To start rSAP is a sim access mode - it doesn't connect to phone to retrieve anything - it takes over functions of the phone, with phone being left out in flight mode and out of the loop after pairing. So yes - if you do long journeys - reception is better (due to aerial on the roof) and you can read texts, but all the texts you receive during that time and history of all the phone calls received during your journey stay in the car system - since phone is in flight mode. Once you switch off the engine and remove your phone, the handset knows nothing of what happened after pairing - no SMS messages on card, no phone calls in calls history. This also goes for history the other way - for example if you store your sms as conversation threads, the car system is not aware of any previous messages from the phone and phone, after you leave the car is not aware of any messages retrieved by car.

Also pairing and unpairing requires change to state of the phone, so you can not walk to the car and switch over to bluetooth, drive while talking then stop, and switch audio back to handset - rsap doesnt work that way - there is a minute or two when the phone shuts down and car takes over, during which time neither is connected to network at all.

If your sat nav or your work relies on data from the phone - be it satnav to phone tethering for live/traffic services or your phone syncing with mail server etc - none of that is available with rsap - the phone is dead and deep asleep, the car kit doesn't support data tethering.

Another inconvenience is upgradability - US market doesn't understand rsap or, to ever bigger degree, need to pay Nokia for license - so most of the new phones - Androids, iPhones, linux based platforms etc - don't support it. So you are left with Nokia, older Sony Ericssons, some Samsungs and Windows phones to use in your car for years to come.

Edited by v0n

No. GSM III is only good on paper. To start rSAP is a sim access mode - it doesn't connect to phone to retrieve anything - it takes over functions of the phone, with phone being left out in flight mode and out of the loop after pairing. So yes - if you do long journeys - reception is better (due to aerial on the roof) and you can read texts, but all the texts you receive during that time and history of all the phone calls received during your journey stay in the car system - since phone is in flight mode. Once you switch off the engine and remove your phone, the handset knows nothing of what happened after pairing - no SMS messages on card, no phone calls in calls history. This also goes for history the other way - for example if you store your sms as conversation threads, the car system is not aware of any previous messages from the phone and phone, after you leave the car is not aware of any messages retrieved by car.

Also pairing and unpairing requires change to state of the phone, so you can not walk to the car and switch over to bluetooth, drive while talking then stop, and switch audio back to handset - rsap doesnt work that way - there is a minute or two when the phone shuts down and car takes over, during which time neither is connected to network at all.

If your sat nav or your work relies on data from the phone - be it satnav to phone tethering for live/traffic services or your phone syncing with mail server etc - none of that is available with rsap - the phone is dead and deep asleep, the car kit doesn't support data tethering.

Another inconvenience is upgradability - US market doesn't understand rsap or, to ever bigger degree, need to pay Nokia for license - so most of the new phones - Androids, iPhones, linux based platforms etc - don't support it. So you are left with Nokia, older Sony Ericssons, some Samsungs and Windows phones to use in your car for years to come.

With my Superb 2 (RSAP) text messages and call history syncs back to the phone, so the call history and texts received whilst on the move are also stored on the phone.

Latest android version now supports RSAP, as does WM6.5 and WM7. This leaves the Iphone as virtually the only current model phone not supporting RSAP.

You can configure a data access point in the phone menu, although I have had little succuess in getting it to work.

The latest version of the RSAP kit (60 plate cars) fitted to the Superb and Octavia now support A2DP

With my Superb 2 (RSAP) text messages and call history syncs back to the phone, so the call history and texts received whilst on the move are also stored on the phone.

No such thing happens in my Octy FL and SE phone. The new 9WZ bluetooth units are rumoured to support that, but I'm not sure whether that means the regular profile introduced in 9W7 as used by most for iphone is broken again or not. Information flying around internet about 035 730 units is just too messy and scarce.

Latest android version now supports RSAP, as does WM6.5 and WM7. This leaves the Iphone as virtually the only current model phone not supporting RSAP.

Latest android on which phone? Maybe something manufacturer specific as Froyo (2.2) doesn't have RSAP support. Considering bluetooth on android doesn't even do proper file exchanges and device browsing, RSAP wasn't even in plans for Froyo. Hey - last time I checked (June) - even new Nokia phones based on linux - meego and maemo platforms like the N900 didn't support RSAP anymore.

The latest version of the RSAP kit (60 plate cars) fitted to the Superb and Octavia now support A2DP

Technically, 035 729C and 035 729D units supported A2DP as well.

Edited by v0n

Create an account or sign in to comment

Recently Browsing 0

  • No registered users viewing this page.

Important Information

Welcome to BRISKODA. Please note the following important links Terms of Use. We have a comprehensive Privacy Policy. We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.

Account

Navigation

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.