Ok so I tried updating the Bluetooth with the 4100 update with the 4000 firmware. It worked. My device reads 3.41 for its Bluetooth now. Picture proof in a moment. Gotta upload to imgur.
Edit. Here you go. Proof I have a 4000 and that I am using the 4100 Bluetooth firmware. http://imgur.com/5AmdK2O
http://imgur.com/zNNnUdYCurrently reinstalling the hacked 1.03 update for the 4100. Let's see if it works better with the upgraded Bluetooth.
So progress!
The Bluetooth firmware update worked. It also did not revert after the full software update. The radio booted faster this time than when I didn't update Bluetooth prior and the unit isn't glitching anymore. However we still don't have audio in CarPlay or Bluetooth. Don't know why but it has something to do with that new Bluetooth audio setting.
I tried doing a full system reset post update and that didn't force the Bluetooth setting to kick over either. Not sure why but it still won't let you click Bluetooth audio on.
But hey! Good news guys. You can now successfully update your Bluetooth to 3.41.10 on your radio.
So if you have the 1.03 upgrade that has been converted to load on a 4000, go to the bluetooth update page BEFORE updating to 1.03 and the radio will update from 3.21.10 to 3.41.10.
Did you try to revert back to 1.08 and keep the 3.41 bluetooth folder and see if bluetooth worked?
Did you try to revert back to 1.08 and keep the 3.41 bluetooth folder and see if bluetooth worked?
Here's the steps I've done so far. I reverted back to 1.08, then using the 1.03 firmware while in 1.08 I updated the bluetooth. So while the radio is in the 1.08 firmware it successfully updated to 3.41.10. I tested bluetooth audio and calling, and everything is working great.
I then updated to 1.03 again. The 3.41.10 bluetooth firmware stayed put. The radio actually ran much more reliably. The first time carplay was utterly unusable and glitchy and half the buttons on the radio weren't cooperating. This time though the radio responded fine and carplay moved fine. The only problem was the same problem. The bluetooth audio would not switch from off to on.
So I tried something crazy. I thought "hey what if the recovery is on the device side? So when you install an update it installs a recovery update as well so if your flash drive dies the radio fixes itself." So I tried the crazy plan. I turned off my radio during the downgrade from 1.08 to 1.03.
Yep I went full nuts. I now know how the restore process works. It works from the SD card, not from the Radio. It used the 1.08 update file to do a restore install. Interestingly it did NOT revert me back to the 3.21.10 bluetooth firmware.
So there you have it. My current findings.
Oh and the turning off the radio to force a restore plan did Not break my radio so I will be trying the same thing with the 1.03 firmware to see if it will work right that way.
hmmm
somewhat how I expected it to work with the "recovery" file in the firmware but interesting still.
I wonder if doing the full 1.03 upgrade and then reverting the bluetooth back to 1.08 (just bluetooth) does anything? If not than it may be something higher level than the bluetooth...
damn me for buying a 5000 nex
damn me for buying a 5000 nex
Ya "dam" you for buying a less than 1 year old product.....
Wonder how it worked out for Danny...
Radio is working fine with the upgraded bluetooth firmware. All functions are great in 1.08. Haven't tried to restore to 1.03 instead of upgrade yet. Haven't had time.
Thanks guys for testing.
So from the testing preform by all of you we can safely conclude that the problem is not with the Bluetooth firmware but with something in combination with the audio settings
Quick question
if I upgrade to the 1.03 that I downloaded from Pioneer's website what do you think will happened to my radio? will be become a brick?
I've read somewhere that there are a few extras with the 4100, not only android auto. what if something within those extra is not playing nice with the 4000 hardware? and that can cause the problem.
Thanks guys for testing.
So from the testing preform by all of you we can safely conclude that the problem is not with the Bluetooth firmware but with something in combination with the audio settings
Quick question
if I upgrade to the 1.03 that I downloaded from Pioneer's website what do you think will happened to my radio? will be become a brick?
I've read somewhere that there are a few extras with the 4100, not only android auto. what if something within those extra is not playing nice with the 4000 hardware? and that can cause the problem.
The only update was the screen i believe.
Obviously our first gen next has all the hardware to run everything correctly. We use bluetooth on the old firmware, so no reason why it cant work with new. Also ANdroid auto runs just fine, there is no lag and usb connection is good. So there is no excuse.
The only update was the screen i believe.
Obviously our first gen next has all the hardware to run everything correctly. We use bluetooth on the old firmware, so no reason why it cant work with new. Also ANdroid auto runs just fine, there is no lag and usb connection is good. So there is no excuse.
If you upgrade the bluetooth ahead of time and change the file names on all the files from 150 to 140 it will give you many new features, but your bluetooth will be for nothing and your carplay won't play music.
So I tried doing a restore install to 1.03. Did nothing differently. The bluetooth audio is still stuck at off no matter what I try. I have also noticed that when I first turn on carplay my illumination turns off until I try to play music at which point I hear a beep and no sound comes. I'm going to revert back to 1.08. Unless someone with actual programming experience looks over the difference between the two open source releases of the firmwares and figures out what exactly is wrong I think this is a dead end.
Haven't seen this mentioned yet.
On my 7000, installing 1.03 changes the navigation firmware from 9.18.13411863 to 9.18.23.497282 and this was the result.
That sucks. Go back to the 1.08 firmware and see if your nag comes back.
That sucks. Go back to the 1.08 firmware and see if your nag comes back.
Sorry, I should have stated the navigation does come back when I reinstall 1.08.
So we can conclude that either hardware changes have been made between the x000 and x100 units, or Pioneer is deliberately messing this up for those of us who are trying to upgrade. Why else would these weird and random problems crop up if the hardware is identical?
well at the very least we are able to upgrade our bluetooth firmware safely with this. I wouldn't suggest 1.03 unless someone with actual programming skills has a go at fine tuning it first.
Hi guys,
I made the upgrade on my F960DAB (european version of the NEX 6000) and had the same results (No Bluetooth).
In adition my HDMI input wouldn't show up any more either. Installed the NEX 8000 firmware, in hopes that this would activate the HDMI, but still no luck.
As far as I can tell the firmware kit is the same for all NEX devices, and once installed based on the model number it changes the available options on the unit.
I was scared for a moment that I have permanently lost HDMI input even after reverting to 1.08, since it wouldn't show up, but after a factory reset everything was back to normal.
Just throwing this out there. Has anyone gone through the settings after the upgrade to see if there is a bluetooth on and off. Since the Bluetooth is toggled to off.
Also, another thought, could there be something in the code that sees that the unit is a prior generation and it turns off the bluetooth?
Just some thoughts.
Just throwing this out there. Has anyone gone through the settings after the upgrade to see if there is a bluetooth on and off. Since the Bluetooth is toggled to off.
Also, another thought, could there be something in the code that sees that the unit is a prior generation and it turns off the bluetooth?
Just some thoughts.
I was thinking about the same thing as far as a model or serial number goes. Their might be within the programing. As per DP3343, we need someone with programing skills to look through both file and see the difference as far as compatibility
there has to be something with the device # of the unit, when I updated my 8000 with 8100 software, the device number actually changed, I think I`m just going to off my 8000nex and buy the 4100, I like the google maps better anyways then pioneers. 