@Manichee, you are correct about the "pop" noise.
The issue wass that in vehicles with factory remote start systems. When the vehicle was remote started, Uconnect is not powered up yet. This is because if the vehicle is within the BT range (about 30 - 35 feet) and you tried to use your phone or had an incoming call, you wouldn't be able to talk to the other person because Uconnect would be active and your call would be active in the vehicle.
Ok, so now that we understand the "why it's noot powered up" question, lets explain the real issue:
When you get into the vehicle after remote starting it, turn the ignition on, Uconnect now will power up and you will hear a "pop" thru the car speakkers. The reason fpor the "pop" is because the radio would be in an AUX mode with no audio input signal until Uconnect powered up, read the USB or iPod to make sure that there hasn't been any changes made (after the key is turned off, uconnect doesn't know if the device has been removed or not) and that all data is still correct, then start to play. So while there would be a short period of reading, Uconnect powers up and then the "pop".
There were a lot of people thinking something was wrong and would go tto the dealer for repairs. This caused a stir in warranty so Chrysler decided to not have resume play but to go back to the last media used prior to using an iPod or USB. Then manually start the device play.
Hope this helps.
If you are listening to a CD it should start playing the cd upon starting the car again. If you are using the ipod/mp3 interface it will not play from it because when the car is turned on it takes time for it to recognize the ipod/mp3 and the radio defaults to fm. Same thing happens when using BT. I remember reading a thread somewhere that there was some issues with early systems and there was a loud noise if the car was on the ipod input when the car was started.