Gas Is Expensive

Does this release work with any existing mods, such as IDT, etc.? I'd like to get some shortcuts back in action on the map screen. Thanks in advance for your attention and response.

Does IDT work with this? I miss the shortcuts.

Woot woot!

Does IDT work with this? I miss the shortcuts.

Gas Is Ex: I'm saying yes, you can control the volume with the sound settings but when sourcing from USB or SD (and only from those) you can expect nav guidance to be as loud as the source and also controllable from the knob. Or maybe I'm saying you should RTFM...

Whoah there. No need to get so excited. I still think you're missing the point of this thread and the issue at hand. The voice guidance is much louder than the SD source, not "as loud as." Also, why are you continuously mentioning that you can control the guidance voice volume level from the knob ? How is this any different when the source is Sirius or CD, etc.? Of COURSE the knob will control the volume. That's it's job in EVERY source. But it DOES NOT control the guidance voice independently, which is what you're making it sound like. What are you trying to say?

With 3.0 when using SD or USB as a source the nav guidance will be at the same volume level as the source and can be controlled by the knob. This is clearly stated in the manual. Not saying it's a smart way to do things, just saying there's a reason for it...

Absurd! What you just said doesn't even make sense. Maybe I'm missing something, but what are you talking about? I control the volume of voice guidance through the navi system menu, not the knob. The knob controls the overall volume of ALL audio. So what are you trying to say?

They basically broke SD playback with 3.0.

 

I just ended up getting an Ipod, which loads really fast and sounds much better.

No, they FIXED SD playback with 3.0. You missed the point of this thread. I'm complaining about the voice guidance volume, not the SD. There's nothing wrong with SD playback now. It actually plays through entire songs without jumping to the next track 5-7 seconds before the end.

So nobody knows what i need to do here?

For whatever stupid reason, when I'm listening to music on an SD card, Samantha's voice is obnoxiously and dangerously loud. I have to go into settings and lower/raise either the voice volume or the master navi volume every time I switch back and forth between Sirius and SD. It's driving me nuts. What's the reason for this nonsense? I have invested a lot of time and money into installing a very high end audio system, and her voice blaring like that (all clipped out and distorted as hell) is threatening to damage my speakers. Is there a file I need to edit in order to fix this? If so, can someone please point me in the right direction?

Thanks in advance.

Yeah, I'm really disappointed with the Sirius integration. Naming the presets isn't much of a concern for me, but I do agree that more screen space should be used to display information. Is there anything that can be done about this, or is this an area of the unit that can't be customized? One thing I really miss about my old stand-alone Sirius unit is the ability to see a readout of what's playing on other stations without having to tune into them. Boo! Can anyone shed some light on all of this? Thanks.

Why isn't this one of the top concerns? I know it has been discussed before, but it's just f'ing ridiculous! Why does the piece of crap skip to the next track before finishing the previous track? Why aren't more people complaining about it? Why hasn't anyone resolved it? Why wasn't this one of the main issues addressed in the 2.0 update? What's wrong here? Is there a solution? Does Pioneer give a shit? Do I need to use a batch-converting program to just add an additional 6 seconds of fucking silence to the end of every one of the files I put on my SD and USB drives? Good lord!

My F700bt didn't automatically adjust the time for DST. Also, when I attempt to manually correct this, it simply reverts back after a minute or two. Customer service/tech support basically hung up on me and refused to help. Any input would be appreciated. Thanks.

Ha. Yeah, I figured he was just talking out of his ass. I've played with all of the units and noticed very few differences between them.

Other than the obvious DVD playback and voltage of the preouts, what are the hardware differences between the 700, 900 and 90? Thanks.

Sorry, .db editing noob here...

How do I save/export my .db file in SQLite so that I can upload the modified file to my unit?

Also a huge THANK YOU for figuring this out.

I've scoped my F900

 

Using a 1KHz 0db test tone, flat EQ, SLA on 0 and no bass boost, the unit doesn't clip at volume 62. BUT as soon as you add any boost to the EQ (or change bass boost or SLA settings), it does start to clip. Personally I would use 60 as max volume, to give yourself a little bit of leeway.

 

When I measured it, volume 62 gave the full 2v output, and 58 gave around 1v, which is normal line level IIRC - volume 46 will be very low in comparison. I suspect the 3sixty will cope with input voltages from about 1-5v, which covers almost all head units out there. I'm planning to connect my F900 to the aux input of another head unit/processor, which accepts normal line level signal only (i.e. 2v is too high) - volume 58 worked very well when I tested it all

Yeah, the 3Sixty actually accepts input voltages from 1-20v. You indicated that the head unit puts out 1v at 58. That makes perfect sense to me, because the 3Sixty requires at least 1v to get its clip indicators to begin flashing, and I had to turn the unit all the way up to 58 in order to get it to do so.

I tested it out tonight, and it looks like we've got a jump that's 2-3 seconds too early. So I need to find a batch-converter application that will allow me to add 2.5 seconds of silence to each of the mp3s on my SD card.

Anyone know of one?

What do you mean don't finish reading? As in going from one track to the next? Or when you shut down, and then start up again?

The player jumps to the next track and starts playing it before it finishes playing the previous track. I believe it makes the jump about 6 seconds too early, but I haven't checked for sure. This is unacceptable to me, and the fact that this issue wasn't addressed in v2.0 really says a LOT about the clowns over at Pioneer. Especially because they claim "more reliable playback" from SD/USB sources. I wonder if there's a way that we can fix this ourselves...

Is there any software out there that will allow me to add 6 seconds of silence to the end of many mp3 files at once?

Thanks for the responses guys. I actually ended up settling on 60 as my max volume setting before reading this (I leave the volume on the unit set to 60 and use the 3Sixty's volume knob as my master volume control). I had suspected that the unit wasn't clipping at the full 62, and I don't use any of the HU's EQ functions anyway, as all of those duties are handled by my external processor.

I would, however, like to retune my setup using the unit's full 2 volt output at 62. The only concern I have is that you say the unit will begin to clip using the SLA feature. For whatever reason, the clowns over at Pioneer didn't bother to fix the fact that CD playback is significantly louder than all other sources when they released v2.0.

Have you tested for the clipping point of the SD reader? I'm wondering if it's safe to bump up the SLA to +4 (which is STILL not level-matched with the CD player) on just the SD and Sirius sources. I guess I can always try that Radio Shack test. Perhaps I will.

Thanks again guys.

Ok so here we go, just updated the bluetooth on the f900. My HU see's the phone, connects fine with it, and transfers the contacts, however it did not read Home, Work, Mobile, ECT. so i'll have to update those manually again...Which SUCKS!!!!

 

 

But that made me think, where is the difference here, 2 t-Mobile dash's, two of the same decks, let's compare Software versions for everything.

 

HU - Version: 2.000000

Bluetooth - Version: HW100-SW330 RC3

 

T-mobile Dash Windows 6 - CE OS 5.2.1236 Build 17741.0.2.1

The only difference between our two setups is my OS version. My Dash is running Windows Mobile 6.1 - CE OS 5.2.19700 (Build 19700.1.1.0)

HOWEVER, after installing Bluetooth firmware v2.9, attempting to connect using it, failing to establish any kind of connection whatsoever, then reinstalling v3.3, then changing my Dash's device name, then hard resetting my unit, then attempting to beam contacts one by one to the unit, then rebooting my Dash, then kicking my tires, then trying to transfer my phonebook again 7 more times, I FINALLY was able to get my contacts onto the unit!

However, about 15 of the 280 numbers (4 of which are important and frequent dials) didn't transfer over. At least now I can live with this, but there really should be a way to enter contacts manually on the unit itself. Bah!

Anyone else have a solution for this? I don't get it at all.

Does anyone have the firmware that came preinstalled on my unit? I just bought one with the blue dot, so it had v1.0017 on it. That Bluetooth firmware it came with worked perfectly with my phone, and now it's trashed. Any help would be much appreciated. Thanks.

If your phone worked before, then download and install the "Alternate" bluetooth update. That should work.

No dice. Doesn't work. In fact, with BT v2.9 the unit can't even "see" my phone. At least v3.3 will let me connect, but I have to operate everything via the phone, not the unit. This is garbage. Has anyone else called to file a ticket about this issue? I tried calling again and this time got a different rep. This rep happened to have a nasty attitude and was incredibly rude and condescending. He also refused to email me the firmware I had before I updated the unit.

What the F is wrong with these clowns? That seems like a pretty simple and OBVIOUS fix to me. Maybe I'm wrong. Maybe it's really f'ing hard to program the unit to play a song all the way through...

I have the F700BT running to my 3Sixty processor which then splits the signal up to my amps. I'm trying to set the levels properly, but I don't have an o-scope to see for certain at what volume level the head unit begins to clip. Max volume is 62.

Normally, in a situation like this, I would just set the HU's volume to 3/4 max (~ 46) and do the rest by ear, but at 3/4 volume I can't get the 3Sixty's clip indicator to blink red (the ideal level for the 3Sixty is where the red clip indicator is on the brink of solid red (blinking).

Has anyone properly tested this HU for clipping? Is max volume safe?

Thanks.

I just called customer service at 800-421-1404 and they put a ticket in to their "engineers" and said they'd call me back within 5-7 business days, hopefully with a work around or resolution.

They also asked that I have anyone else I know with similar problems call up and make a report as well. So please call them and file a report so we can get this issue addressed asap. Thanks.

Man, these guys at Pioneer really like to rush things out without testing them first, eh? Why don't they have a program where they release the update to a large group of consumers to TEST before they approve a final release? This is ridiculous. So now what? I have to wait around for the next update, if there ever IS one, in order to get my unit to function the way it did when I bought it?