Volkswagen Amarok RNS 315 Bluetooth stuck on “Start Phone…” after restart

User question

Hello everyone, and a big thank you for your help.
I have a small problem with my RNS 315 car radio with integrated Bluetooth module in my 2010 Amarok (3C0035279, version 0010).
For some time now, the Bluetooth connects normally when I first start the vehicle, but when I stop the vehicle and restart it, the Bluetooth no longer connects, and I constantly get the "Start Phone..." message without it connecting.
I've tried everything: resetting the unit, removing the battery, and updating from version 0010 to 0011. Despite all these steps, there's still no result. The problem persists.

Artificial Intelligence Response

Direct answer to the question

Your symptom is very unlikely to be a phone-pairing problem or a simple firmware problem. Because the Bluetooth works after a cold start but hangs on “Start Phone…” after a short stop/restart, the most probable fault is:

• the internal Bluetooth section of the RNS 315 is not being reset correctly during a warm restart, or
• the Bluetooth module/power supply inside the RNS 315 is failing, often due to ageing capacitors, a regulator issue, thermal solder-joint failure, or a voltage dip during engine cranking.

Since you already tried reset, battery disconnection, and SW 0010 → 0011, I would next test for warm-start brownout and internal Bluetooth module lock-up before replacing parts.

Your unit number 3C0 035 279 is one of the RNS 315 versions known to support integrated Bluetooth, so the issue is not that the unit lacks Bluetooth hardware. Some RNS 315 units have integrated Bluetooth and some do not; compatibility lists identify 3C0 035 279 as Bluetooth-capable, and the coding is normally handled in 37-Navigation, Byte 3, Bit 5 for the telephone transceiver setting. (vag-coding.net)

---

Detailed problem analysis

The important clue is the difference between:

Situation	Result	Meaning
First start after vehicle has been off for a while	Bluetooth connects normally	Full cold boot/reset works
Stop vehicle, restart shortly after	“Start Phone…” forever	Warm restart / soft wake-up fails
Battery disconnected / unit reset / SW updated	No permanent improvement	Not a simple configuration fault

The RNS 315 does not behave like a modern smartphone that fully reboots every time. In the vehicle it has several power states:

1. Deep sleep / cold boot
   After the car is locked and the CAN bus goes to sleep, the radio/navigation unit and internal Bluetooth electronics are effectively forced through a cleaner reset sequence.

2. Standby / warm wake-up
   If you stop and restart the Amarok before the infotainment system has gone fully to sleep, the main processor wakes up from a semi-retained state. The internal Bluetooth module must then be reinitialized by software or reset circuitry.

3. Cranking event
   During engine start, the 12 V rail can dip sharply. If the radio’s internal Bluetooth power rail drops just enough to disturb the Bluetooth processor but not enough to reset the whole RNS unit cleanly, the Bluetooth section can hang. The main RNS processor then waits for a response and stays at “Start Phone…”.

This is why the fault appears after a short stop/restart but not after the car has been left long enough for a true sleep cycle.

Volkswagen documentation also confirms that RNS 315 systems exist with integrated Bluetooth functionality, including HFP, A2DP, phone data transfer, voice operation, and multifunction steering-wheel integration. (static.oemdtc.com) In other words, the Bluetooth part is not just a passive antenna; it is an electronic subsystem that can fail or lock up independently of the navigation/radio functions.

---

What the SW 0010 → 0011 update tells us

The fact that you updated from 0010 to 0011 and the fault stayed is significant.

There was a Volkswagen software update reference for RNS 315 software level 0011, but the listed concern was a system reset issue in specific regions, not specifically a warm-restart Bluetooth hang on 3C0 035 279. (static.nhtsa.gov) Therefore, updating to 0011 was a reasonable step, but it does not rule out hardware failure in the Bluetooth section.

So at this point I would stop treating this as a normal firmware issue and start diagnosing it as:

• internal Bluetooth module lock-up,
• low-voltage/brownout problem,
• defective RNS 315 internal power regulation,
• cracked solder joint / thermal failure,
• or less likely, incorrect coding after previous retrofit or module changes.

---

Practical diagnostic procedure

1. Test whether engine cranking causes the fault

Do this exactly:

1. Start the vehicle from cold.
2. Let the Bluetooth connect.
3. Switch ignition off.
4. Wait only 10–30 seconds.
5. Switch ignition back on to accessory/ignition without cranking the engine.
6. Check whether Bluetooth reconnects.

Then repeat the test but actually crank/start the engine.

Interpretation:

Result	Likely cause
Bluetooth works if you do not crank, but fails after engine start	Voltage dip / brownout during cranking
Bluetooth fails even without cranking	Internal RNS warm-start/reset problem
Bluetooth works only after waiting 15–30 minutes	CAN sleep/hard reset dependency
Bluetooth works after manually rebooting the RNS	Internal software/reset sequencing fault

If cranking causes the problem, measure the voltage at the battery and ideally at the radio supply during engine start. A weak battery can still start the engine but drop low enough to upset infotainment electronics.

Check:

• battery condition under load,
• battery terminals,
• chassis ground,
• engine ground strap,
• radio supply fuse contacts,
• voltage at permanent supply Terminal 30,
• voltage at switched supply/CAN wake line if applicable.

A minimum cranking voltage around or below 9–10 V can be enough to disturb older infotainment electronics even if the engine starts.

---

2. Try forced reboot when the fault is present

When the screen is stuck on “Start Phone…”:

1. Keep the engine running.
2. Press and hold the RNS 315 power/volume knob for approximately 10–20 seconds.
3. Wait for the unit to reboot.
4. Check whether Bluetooth starts normally.

Interpretation:

Result	Meaning
Bluetooth works after forced reboot	The Bluetooth hardware can work, but warm wake/reset is failing
Bluetooth still hangs	Internal Bluetooth module is probably failing
Bluetooth works sometimes depending on temperature	Possible solder joint or component ageing

---

3. Wait for complete vehicle sleep

After the fault appears:

1. Turn the vehicle off.
2. Remove key.
3. Lock the vehicle.
4. Wait at least 20–30 minutes.
5. Restart and test Bluetooth.

If it works only after this long wait, that strongly supports a soft-wake / warm-restart lock-up rather than phone incompatibility.

---

4. Scan with VCDS, ODIS, OBDeleven, or equivalent

Scan at least:

• 37 - Navigation
• 56 - Radio, if separate/available
• 19 - CAN Gateway
• 77 - Telephone, if an external telephone module exists

Look for faults such as:

• Telephone transceiver malfunction,
• internal control module fault,
• low voltage,
• communication fault,
• microphone open circuit,
• incorrect coding,
• CAN gateway installation-list conflict.

If the vehicle has both an internal RNS 315 Bluetooth function and an external telephone module coded at the same time, the system can behave unpredictably. Ross-Tech forum discussions also note that RNS 315 units can have built-in Bluetooth and that, where an external Bluetooth module is used, the internal Bluetooth may need to be coded out. (forums.ross-tech.com)

---

Coding checks

Because your Bluetooth works on first start, coding is probably not the main fault. Still, verify it.

For internal Bluetooth on RNS 315:

• Go to 37 - Navigation
• Coding / Long Coding Helper
• Check the telephone transceiver setting around Byte 3
• Make sure the internal telephone/Bluetooth configuration matches the vehicle hardware

A commonly documented activation path for RNS 315 Bluetooth uses 37 - Navigation → Coding 07 → Long Coding Helper → Byte 3, with the telephone transceiver bit adjusted accordingly. (vag-coding.net)

Also check whether a separate 77 - Telephone module is installed. If the car has an external Bluetooth module under the seat or behind trim, the gateway installation list and RNS coding must be consistent.

---

Most likely root causes, ranked

1. Internal Bluetooth module lock-up during warm restart — most likely

The unit boots, radio works, navigation works, but phone stays at “Start Phone…”. This suggests the main RNS processor is alive but waiting for the Bluetooth subsystem.

Possible internal causes:

• Bluetooth processor frozen,
• reset line not pulsing correctly,
• local 3.3 V / 1.8 V regulator issue,
• degraded capacitors,
• marginal oscillator startup,
• UART/CAN communication between main board and Bluetooth module failing.

2. Voltage dip during restart

A 2010 vehicle may have enough battery capacity to crank but still produce severe voltage transients. Older infotainment units are sensitive to this, especially if their internal filtering capacitors have aged.

Check this before replacing the radio.

3. Thermal solder-joint problem

If the unit works cold and fails warm, suspect thermal issues:

• cracked solder joints,
• BGA fatigue on the Bluetooth chipset,
• connector fatigue between daughterboard and main board,
• failing regulator that becomes unstable when warm.

This is especially plausible if the problem appears after driving for a while and restarting shortly afterward.

4. Firmware/configuration mismatch — less likely now

You already updated to 0011. Since the symptom remains, firmware alone is not the leading suspect. However, coding should still be verified with VCDS/ODIS.

5. Smartphone compatibility — unlikely

If the RNS hangs at “Start Phone…” even when your phone Bluetooth is switched off or all paired phones are deleted, the fault is inside the RNS 315, not the phone.

---

Repair options

Option A — Check vehicle electrical health first

Before opening or replacing the RNS 315:

• load-test the battery,
• check alternator charging voltage,
• inspect battery terminals,
• inspect engine/body ground straps,
• check fuses and radio supply contacts,
• measure voltage during cranking.

This is low-cost and should always be done first.

---

Option B — Repair the RNS 315 internally

If the electrical system is healthy, the RNS 315 likely needs bench repair.

A competent electronics repairer should check:

• internal 5 V / 3.3 V / 1.8 V rails,
• ripple on Bluetooth supply rails,
• reset signal to Bluetooth IC/module,
• regulator stability during simulated crank voltage,
• electrolytic/tantalum/SMD capacitor ESR,
• cracked solder joints around the Bluetooth module.

Possible repairs:

• replace aged low-ESR capacitors,
• replace local voltage regulator,
• rework cracked solder joints,
• replace or reball Bluetooth IC/module if available.

I would not recommend a casual “heat gun reflow.” It may temporarily improve a cracked joint but can damage the board. Proper hot-air rework with temperature control, flux, preheating, and inspection is required.

---

Option C — Replace the RNS 315

This is often the most practical solution.

If replacing, make sure:

• the replacement RNS 315 has integrated Bluetooth if you want to keep the same configuration,
• you get the anti-theft PIN/security code,
• the part number and region are compatible,
• navigation maps/radio region are correct,
• microphone wiring is compatible,
• coding is copied from the old unit before removal.

Do a full autoscan before replacement so you can restore coding.

---

Option D — Use an external OEM Bluetooth module

Another robust workaround is to stop using the failing internal Bluetooth and fit an external VW Bluetooth module, for example a 9W7/7P6-family module, if compatible with your Amarok wiring and cluster/radio configuration.

General concept:

1. Install external Bluetooth module.
2. Add correct microphone/audio/CAN/power harness.
3. Register module in CAN Gateway if required.
4. Code RNS 315 to use external telephone module or disable internal Bluetooth.
5. Verify steering-wheel and MFD phone functions.

Volkswagen technical information also states that some RNS 315 Bluetooth diagnosis is similar to the 9W7 system, which supports the idea that the external Bluetooth architecture can be integrated with these vehicles when correctly coded. (static.nhtsa.gov)

This option is useful if the RNS 315 radio/navigation functions are otherwise good and only the internal Bluetooth is unreliable.

---

Practical recommendation for your case

I would proceed in this order:

1. Perform the no-crank restart test.

   • If Bluetooth only fails when the starter is used, investigate battery/grounds and voltage drop.

2. When stuck on “Start Phone…”, force reboot the RNS.

   • If it recovers, the internal Bluetooth is probably not being reset correctly during warm wake.

3. Scan with VCDS/ODIS/OBDeleven.

   • Save all DTCs and coding before changing anything.

4. Delete all paired phones and test with phone Bluetooth off.

   • If it still hangs, the phone is not the cause.

5. If the fault remains, choose between internal repair and replacement.

   • For long-term reliability, replacement or professional repair is better than repeated resets.

---

Possible temporary workaround

If you need a short-term workaround:

• wait until the car has gone fully to sleep before restarting,
• or hold the RNS power button to force reboot when “Start Phone…” appears,
• or disable Bluetooth temporarily if the hang affects other radio functions.

But these are workarounds, not repairs.

---

Brief summary

Your RNS 315 is most likely suffering from an internal Bluetooth module warm-restart failure, not a normal pairing or firmware issue. The update to 0011 was reasonable but does not directly prove the Bluetooth hardware is healthy. Test for cranking voltage drop, force-reboot behavior, CAN sleep behavior, and scan the unit with VCDS/ODIS. If the vehicle electrical system is healthy, the durable fix is usually professional repair of the RNS 315 Bluetooth/power section, replacement of the unit, or conversion to an external OEM Bluetooth module with correct coding.

Disclaimer: The responses provided by artificial intelligence (language model) may be inaccurate and misleading. Elektroda is not responsible for the accuracy, reliability, or completeness of the presented information. All responses should be verified by the user.