When you click on links to various merchants on this site and make a purchase, this can result in this site earning a commission. Affiliate programs and affiliations include, but are not limited to, the eBay Partner Network.
Just to be clear, you tried a USB stick (no phone) with an uncompressed format?
Yes and No.
I have used .flac music files and the noise is still there but to make the problem apparent I use test tones. and I have used text tones in USB, phone or bluetooth with same result, they are compressed.
That same text tone has been burned into an MP3 cd as well as music track that the noise is very apparent and the noise is gone because audio is being played directly from the ACM.
So in short the problem is not the files you use to play music its the APIM working its magic produce the weird noise.
Did you ever get the MEM_ERR03 before the success? Would you atribute your success to a brand new USB flash drive? If so, what exactly did you get?
I don't know if the success was due to using the 32GB USB flash drive or not. I just know that the first time I tried the install I used a 16GB and did not format it to exFAT and did not allow the install to keep running once it said it was complete like instructed on the Ford Owner's website. The 2nd time I bought the most inexpensive Sandisk 32GB USB drive I could find at Walmart and formatted it to exfat put the download on the USB and followed the instructions meticulously from the Ford Owner's website and it worked perfectly and is still working. Good luck.
So in short the problem is not the files you use to play music its the APIM working its magic produce the weird noise.
Yes that seems to be the case but I was only trying to rule out if it's the APIM working its magic on any file, compressed or not, or on compressed audio. It's probably any file as you mentioned. Not sure there will be much you can do about it as it's probably the codec's handling of the audio. Some info and things to try after looking at the fcc disclosure, that may or may not help you. There appear to be some sound settings that could be related if they are trying to provide virtual effects. Not sure if these are enabled in as built or elsewhere. I am not familiar with them but if you have any of those options enables they could be messing with the sound.
Audio CODEC – CS4234 has 4 Channels of Differential audio data input (4 ADC Channels) and 5 channels of Differential Analog Audio Output (DACs). The Sync module is currently using 2 analog channel inputs for microphone digitalization and 3 DAC channels for a stereo and mono signal output. All data communicated over the I2S buses is at a 48KHz.
Yes that seems to be the case but I was only trying to rule out if it's the APIM working its magic on any file, compressed or not, or on compressed audio. It's probably any file as you mentioned. Not sure there will be much you can do about it as it's probably the codec's handling of the audio. Some info and things to try after looking at the fcc disclosure, that may or may not help you. There appear to be some sound settings that could be related if they are trying to provide virtual effects. Not sure if these are enabled in as built or elsewhere. I am not familiar with them but if you have any of those options enables they could be messing with the sound.
Audio CODEC – CS4234 has 4 Channels of Differential audio data input (4 ADC Channels) and 5 channels of Differential Analog Audio Output (DACs). The Sync module is currently using 2 analog channel inputs for microphone digitalization and 3 DAC channels for a stereo and mono signal output. All data communicated over the I2S buses is at a 48KHz.
Thanks for the great info!
I did try the different occupancy settings and its the same... do you know if the MY18 Apims are any different?
I did try the different occupancy settings and its the same... do you know if the MY18 Apims are any different?
JC
As far as I can tell, no. But, it looks like there's a MY18.5 that will likely have a different software structure (meaning the updates won't be designed for the previous generations), and possibly a 10" screen. There may be other differences as well. Hopefully we'll learn more at CES.
Little late to this thread and read through splitting the autoinstall.lst file by removing Item 4/Open 4. In my search for resolving MEM_ERR03, I came across this thread (http://www.thedieselstop.com/forums/...-2-2-a-624377/) that looks to have instructions for the second half of the install... although it's about 2.2, the gist of it is to install the Item4/Open 4 that was removed from the first part of the install. Maybe I missed it in this thread but I didn't see anything about installing the rest of 2.3, meaning Item 4/Open 4.
For the experts on this thread, any thoughts on whether the instructions I found from the other thread would work for the rest of the 2.3 install?
Little late to this thread and read through splitting the autoinstall.lst file by removing Item 4/Open 4. In my search for resolving MEM_ERR03, I came across this thread (http://www.thedieselstop.com/forums/...-2-2-a-624377/) that looks to have instructions for the second half of the install... although it's about 2.2, the gist of it is to install the Item4/Open 4 that was removed from the first part of the install. Maybe I missed it in this thread but I didn't see anything about installing the rest of 2.3, meaning Item 4/Open 4.
For the experts on this thread, any thoughts on whether the instructions I found from the other thread would work for the rest of the 2.3 install?
For 2.3 I would not do it the way they did it. 14G381 is the most important package, it's the sync software. For 2.3 Ford also has patches that need to be installed along with 381 that depend on your system. What seems to be the block for MEM_ERR3 is Voice and/or Gracenotes. Voice is 391, and GN is 423. I would remove those from the first pass. Then if it installs without a problem and your system is updated, make two more installs, one each for 391/423 to update voice and GN.
For 2.3 I would not do it the way they did it. 14G381 is the most important package, it's the sync software. For 2.3 Ford also has patches that need to be installed along with 381 that depend on your system. What seems to be the block for MEM_ERR3 is Voice and/or Gracenotes. Voice is 391, and GN is 423. I would remove those from the first pass. Then if it installs without a problem and your system is updated, make two more installs, one each for 391/423 to update voice and GN.
So if I understand what you are advising correctly, I would do the following:
Partial success! Did the upload in 2 parts... removed 14G391 from the first pass and updated successfully to 2.3. Tried 14G391 on second pass and got the MEM_ERR03 error... What's interesting is that GN serial number showed up after the first pass.
