Resuming Playback with 2014 CX-5 GT Tech Stereo and other issues

See what I mean?

Not at all.

As a side note, do your research on the outback. my previous car was a subaru (wrx) and I was leaning toward the outback/forester as well. There have been a number of mechanical problems with the outbacks, which are far more impactful than the function of the radio. (more so the forester I think than the outback but do check it.)

Thanks for the advice. But, the only issues I am aware of are the 2.5/CVT issues, which aren't important to me because I would buy the 3.6/5AT, and the "wandering" which was addressed with the 2013 suspension changes.
 
Atitus, the thing is, almost none of these issues would show up in a normal test drive. As I have NEVER seen a car with iPod functionality that didn't resume correctly, why on earth would I, during a test drive, have turned off the ignition, waited two minutes, and started it back up.

I'm not sure why you keep repeating this point. I'm not challenging that, and I'm not suggesting that you should have tested this. I agree that it should not behave this way, and no one expects that it should.

Same with bringing an iPod to begin with. This is 2013. I doubt you can even FIND a car without iPod integration at this point. So it goes to expect 'reasonable' functionality with it. I have never seen a car that takes 25 MINUTES to scan an iPod on boot up. So WHY would I assume I needed to bring an iPod to test this Mazda.

This is where you and I disagree. The functionality varies substantially between manufacturers, both by design and by error. If IPOD integration is important to you, then just flat out assuming that its going to work the way you think it should work is being naive, and you take a big (and expensive) risk by not actually testing the features that are important to you.

See the thing is, no matter how much Mazda claims it's working as designed, they're full of sh*t. They KNOW they screwed it up, it's flawed, broken, etc. And so far they have refused to fix it. So please, do us all a favor, and stop saying this is OUR fault for not doing a 45 minute iPod examination when taking a test drive.

No doubt in the case of Mazda these problems are errors. I am not disputing that. I am only trying to educate people as consumers on how to protect yourselves. The manufacturer (Mazda or any other in similar situation) will claim that its working as intended so that the problems cannot be claimed as warranty issues. Is it "right" ? No, not in many people's eyes. But is it going to happen? YES. As a consumer you still should protect yourself as much as possible. If you expect the manufacturer to look out for YOUR best interests and not their own, then you are living in a fantasy world and we'll just have to agree to disagree going forward.
 
This is where you and I disagree. The functionality varies substantially between manufacturers, both by design and by error. If IPOD integration is important to you, then just flat out assuming that its going to work the way you think it should work is being naive, and you take a big (and expensive) risk by not actually testing the features that are important to you.
Since there has never been another case that I've heard of where an iPod connection does not work as one would expect it to, I think it is reasonable to expect this one to also work. Especially when the official specs state that it is compatible with the exact iPod version I am using. While I do agree that a buyer should do a thorough test drive, I disagree that this is an issue that any reasonable inspection would have turned up. By your thinking, I should never take for granted that any system is working without a thorough test. For example, rear defrost is very important in my region. Should I wait for an icy day to test the car out before committing to buy? AWD is very important to me, so should I assume it is not working and wait for winter before I buy a car? Of course not. At some point you have to have faith in the manufacturer of the vehicle to be testing these things BEFORE they release them to the public. In this case, where there is no reason for a buyer to anticipate and test for every scenario where the iPod connection might not work properly, I firmly believe that Mazda failed, not the consumer.
 
Trey, yes you make very good point, and I agree that its not always going to be practical to test every component. I still think its in the best interest of the consumer to test what is practical. If you have an ipod that you plan to use on a daily basis, you should bring it and try it out, versus not bringing it at all. The case of the large ipod that takes 25 mins to scan the files, which I think everyone can agree is the "most broken" of all the issues, would have been easily caught on the first attempt to use it.
 
The case of the large ipod that takes 25 mins to scan the files, which I think everyone can agree is the "most broken" of all the issues, would have been easily caught on the first attempt to use it.
Actually, I tend to disagree with this. If the iPod took 25 minutes to scan the files when it was first attached (and ONLY when first attached), there'd be no problem with that delay whatsoever for most people.

The problem is that 25 minute scan happens each and every single time I start the car, and the head unit can't even play music until the scan is done - making the iPod completely useless for anything but the longest drives.

Adding to that 25 minute delay, we also have a device that doesn't remember what song it was playing, what playlist it was playing from, or anything else - and Mazda is on the fringe of falsely advertising support for a device.
 
Actually, I tend to disagree with this. If the iPod took 25 minutes to scan the files when it was first attached (and ONLY when first attached), there'd be no problem with that delay whatsoever for most people.

The problem is that 25 minute scan happens each and every single time I start the car, and the head unit can't even play music until the scan is done - making the iPod completely useless for anything but the longest drives.

Adding to that 25 minute delay, we also have a device that doesn't remember what song it was playing, what playlist it was playing from, or anything else - and Mazda is on the fringe of falsely advertising support for a device.

I think you are stretching here, just to force a disagreement. If you took the car on a test drive, lets say it went 15 mins or so, and the ipod still hadn't loaded, wouldn't you be all over the dealer about it? I'd bet they'd offer to let you try it in another vehicle just in case there was a problem with that first one -- and then you'd get the same behavior again. You'd sit there for a while and it would just keep waiting. I bet most people wouldn't wait 25 mins to see if it happened to come on. You might not get to the actual conclusion of what was happening, but you'd certainly figure out that it had a problem playing your ipod. This would be the all important "red flag" you needed to factor in when trying to decide if you want to buy. That is the point I am trying to make.. and I don't think its mutually exclusive with (most) other people's view points. It still really sucks, and Mazda still needs to stop deflecting the issue and try to come up with a solution.
 
I think you are stretching here, just to force a disagreement.
Oh? I don't think so - I think I'm pointing out the actual problem isn't just the delay, its the delay that happens every time the car is started.
If you took the car on a test drive, lets say it went 15 mins or so, and the ipod still hadn't loaded, wouldn't you be all over the dealer about it? I'd bet they'd offer to let you try it in another vehicle just in case there was a problem with that first one -- and then you'd get the same behavior again.
I think this is the flaw in your logic and assumptions. I'd find it annoying, but not completely unusual, for the car to spend 15 minutes to load the data. In fact, I had this very experience on one of my test drives. In my case, I made sure that the music eventually started playing before I "ended" my test drive. (When this did happen, I even commented to the salesman that it would be nice if Mazda allowed playing while it scanned the same way that Ford does.) I also verified that I was able to select a playlist and turn on shuffle.

It never occurred to me that this long delay would occur EACH AND EVERY time I started the car. THAT is the big problem, and I really doubt people test drive a car with an iPod attached, and as part of the test drive, they stop the car, turn off the ignition, wait 15 minutes, and then restart the car (all while leaving an iPod attached.)

This is just one of those things that are perfectly reasonable to assume works. Similar to it being reasonable to expect ABS to not lock up the brakes without getting on the highway and slamming on the brakes to test.

Some other things I didn't test during my test drive (and I doubt many people did):

If the AWD kicks in when the front wheels slip.

If the traction control works.

If the spare tire actually fits properly on the wheel hub.

If the jack used to put on a spare tire actually works (or that it lifts the car.)

If the highbeam lights work

That the airbags would deploy if I hit something head on.

That the side airbags would deploy if I let something hit me from the side.

...and so on. I think (hope) you get the point. It's perfectly reasonable to assume that some things will work as advertised without actually testing them. Mazda claims compatibility with my iPod... just as they claim that there's a clock on the console stack. I'd feel the same way if I had to reset the clock on the console each time I started the car.
 
Atitus, you continue to completely miss the point, or you're just trying to be a jerk and piss people off. Name one... ONE car that exhibits this behavior with the iPod. You can't. I've driven dozens of cars with iPod connections, and not ONE behaves this way. So no, it never occurred to me that it was something I needed to 'test'. Like brakes, steering, etc, in this day and age, there is 'reasonable expectation' that when a manufacturer claims iPod Compatibility, they also are responsible for 'usable' Ipod connectivity. It just should go without saying.

According to your logic, I'm the one responsible for having discovered every possible flaw that Mazda built into the car?
 
We have gone beyond circular and redundant here, but still, I LOL'ed :)

Some other things I didn't test...
If the spare tire actually fits properly on the wheel hub.
That the airbags would deploy if I hit something head on.
 
Atitus, you continue to completely miss the point, or you're just trying to be a jerk and piss people off.

Neither of these things is true.

While I can't name another car with exactly these ipod problems, there are similar 'infotainment' ones. You insist on grouping all classifications of problems together as if they carry the same weight. Like AWD, spare tires, etc. They are not, and should not, be treated the same. There is the expectation that critical vehicle parts must work. The manufacturer would not knowingly release the car with a problem like that, they get discovered after the fact. Things like the radio are completely different and should be treated as such. Would the manufacturer release the car with known issues in the infotainment system but they just ran out of time to fix it? Sure, they would. And they DID. Will they ever fix it? Probably. Issue a recall? Doubtful.

Please understand that I am **NOT** trying to tell you that you should not complain, or you should not press Mazda to get it fixed. I am **NOT** saying that you do not have the right to be frustrated or angry. By the reactions, its clear that some people are interpreting me this way. This is simply not the case. What bothers me is the fact that some people DO ACT like a radio problem is the same level of severity as the AWD or braking system. That is not realistic. And expecting the manufacturer to respond with the same level of severity is equally unrealistic.

According to your logic, I'm the one responsible for having discovered every possible flaw that Mazda built into the car?

No, I never said that. Either you are misinterpreting me or you are twisting my words the way you want, in an attempt to discredit my statement.
 
I just tested with my iPhone 5 on iOS 6.1.4
Yes it defaults to the first song every time it starts up. Not as bad as I have access to all the playlists, so i just press the diplay for the song I want to hear. It took no more than a minute for the iPod to load after car starts up. I tired 2 times just to make sure. I have 500 songs on my iPhone, not an enormous amount.
Although operation isn't perfect, it doesn't bother me enough to complain about it daily on here. Most of the time I use Bluetooth streamimg(yeas quality isn't as good) as I drive my wife's CX-5 on short trips on the weekends. One time when we took a road trip, the playlist didn't load, but I think that was the cheap replica lightening cable I bought.
 
You know, I just had a nice long reply to atitus including quotes where he contradicts himself, and then completely ignores entire paragraphs demonstrating why he might be incorrect. And then I realized, it's a waste of time.

So, I'll keep it simple: It's broken. The level of severity and the particular thing most bothers a person is up to the individual person. I find the broken iPod interface more of a problem than someone else might. The majority of people (and the courts in the US legal system) might agree that Mazda's claims imply a certain level of expected functionality that the system doesn't give. It's also fairly obvious that there are some things that just can't feasibly be tested on a single (or even multiple) test drives (such as the fact that the iPod has to re-scan every time the car is turned off and turned back on.)

Personally, I expect that Mazda will eventually correct the issues. In the meantime, is there really any problem with leaving us to complain in this thread peacefully?
 
Would the manufacturer release the car with known issues in the infotainment system but they just ran out of time to fix it? Sure, they would. And they DID.
What deadline did they have to meet? The 2014 was released in what, February, March of 2013? Seems to me that they had nearly 6 months to fix the issues to be on track (no pun intended) with the rest of the industry. If there was such a big rush to get the 2.5 out to quiet media rumblings about lackadaisical power, they should have just plunked the new engine in and left the 2013 infotainment system in rather than risk a whole new negative media storm around their new flagship.

And yes, several dealers told me the CX-5 is their new flagship, destined to outshine the 6.
 
And then I realized, it's a waste of time.
So, I'll keep it simple: It's broken.
is there really any problem with leaving us to complain in this thread peacefully?

I have reached the same conclusions. Complain away. Sue Mazda if it makes you feel better. If you are successful at getting them to issue a recall on the radio, all the more power to you.
 
I sent another email to mazda usa using your email with some personal suggestions. Hope we can hound Mazda USA long enough so they start to hound the real engineers back in JAPAN.

OK, this is really bugging me and I'm getting ready to go on a 14 hour driving trip and don't want to flip through where I left off every time I stop for gas or a health break. I realize this will not be fixed in-time, but regardless, it NEEDS to be fixed.

Here's what I sent Mazda, I paraphrased it from information at the top of this Topic, please feel free to copy it or re-write, but make sure you notify Mazda this is not acceptable.
 
TreyP,
How much did your new head unit cost you and where did you look? Im considering this as well.
 
TreyP,
How much did your new head unit cost you and where did you look? Im considering this as well.
I got it from Crutchfield, it is a Kenwood DDX-370 and it cost around $375 including the Mazda wiring adapter, the steering wheel controls interface, the antenna adapter, and the mounting kit.

I'm still working on getting the original back up camera hooked up because I discovered that the camera requires 6v, so I've ordered a voltage converter and am just waiting for that to arrive so I can complete the experiment. Otherwise I am beyond thrilled with the new head unit.
 
Last edited:
I got it from Crutchfield, it is a Kenwood DDX-370 and it cost around $375 including the Mazda wiring adapter, the steering wheel controls interface, the antenna adapter, and the mounting kit.

I'm still working on getting the original back up camera hooked up because I discovered that the camera requires 6v, so I've ordered a voltage converter and am just waiting for that to arrive so I can complete the experiment. Otherwise I am beyond thrilled with the new head unit.
But no Bluetooth or HD radio, correct?
 
TreyP thats nice man, i have the tech package tho and not sure if I would want to rid myself of that tom tom guidance (which sucks) and the backup cameras huge screen. Ill take a look at that stereo tho, its always been a personal dream of mine to have a nice headunit with organic light show that beats to the music and properly plays my usb devices.
 

New Threads and Articles

Back