Is the link search feature available in version 3.0?

That's not true... If you hold down the Up/Down button on your steering wheel for approximately a 1/2 second or so (rather than just clicking it) it will seek for the next station.

That assumes that you have a wheel that can be held, rather than just rotated, and in any case, we weant it to move through presets, not just tune to whatever's next.

The Pioneer EU website for the F910BT states "Hands Free Dialling" for the bluetooth phone. Has Voice Control been enabled in 3.0 for the F900BT ?

Iaf, can you tell us if the gps arrow in the north facing up mode is near the bottom of the screen? I'm hoping its not just plopped in the middle of the screen. Thanks!!

The Pioneer EU website for the F910BT states "Hands Free Dialling" for the bluetooth phone. Has Voice Control been enabled in 3.0 for the F900BT ?

On my computer it says "handsfree calling" not "dialing", anyway: No Voice control! It was propably to expensive to teach the system all the different European Languages. Given the fact, that that they have difficulties with the voice guidance in Europe (at least in Germany) that's propably a feature rather than something you want to be added

rgds

Jörg

Hello

Why you already have the new version if it is not already available?

 

 

Why ? Cause i wanted it!

lol, maybe u wanted to know HOW i got the new version already... Well.. a friend of mine know somebody who knows somebody...

Lol. So, if you know a friend who knows another friend who knows a ... and I know you yourself, we are all friends !!!!!!

Any possibility?

In 2.0, the only steering wheel input that the unit would recognize for controlling tuning would nudge the tuner up, not seek, nor next preset. So if you're rocking to 101.1 (Preset 1) and push the steering wheel button, you'd go to 101.3

 

That's not true... If you hold down the Up/Down button on your steering wheel for approximately a 1/2 second or so (rather than just clicking it) it will seek for the next station.

Let me clarify:

The PAI remote adapter can be programed for seek up/down or preset up/down. The AVIC-F series do not respond to preset up/down when the remote adapter is programmed to output these signals to the head unit. The only input that unit recognizes for controlling tuning is the seek up/down. Seek is not the behavior for a single press, and to seek, requires that the steering wheel controls will output a continuous signal for the head unit to seek.

Regardless, the preset up/down is definitely the preferred behavior of the majority.

iaf_22, thank you so much for the video and your info!

 

Can you confirm to us that you can still do the soft-mod for the handbrake? i.e. you can still insert the vehicle speed in the .ini file?

 

Thank you!

 

Not sure what you mean... Are you talking about watching video while the parking brake is off ?? The shop who installed me the Avic did this bypass for me... and this is still working.

But maybe that's not what u meant... ??

Allright iaf_22 here's the nutshell: there are two types of bypasses, a hardwired and a software. The software is primary source of concern because of the questions with testmode's functionality. Hardwire fools the unit into thinking the parking brake is pulled. However, when you start moving, the gyros/GPS senses your moving and once you make it over 10mph, you get another safety warning that once again disables input to the unit (inputting addresses, watching video, etc).

However, this software warning can also be disabled (via testmode) by changing the parking_break_speed value in the DATA.zip file (/project_config/pioneer.ini) does in fact bypass the video/gps restriction . Looks like this:

[pioneer]

parking_break_speed=16.0

hide_logos=1

Change the 16 to 256 (I think) and you have bypassed it.

The question is, is it still accessible and is it still in an easy to find spot - not to mention, IF you can find it - DOES IT STILL WORK...

iaf_22, thank you so much for the video and your info!

 

Can you confirm to us that you can still do the soft-mod for the handbrake? i.e. you can still insert the vehicle speed in the .ini file?

 

Thank you!

 

Not sure what you mean... Are you talking about watching video while the parking brake is off ?? The shop who installed me the Avic did this bypass for me... and this is still working.

But maybe that's not what u meant... ??

 

Allright iaf_22 here's the nutshell: there are two types of bypasses, a hardwired and a software. The software is primary source of concern because of the questions with testmode's functionality. Hardwire fools the unit into thinking the parking brake is pulled. However, when you start moving, the gyros/GPS senses your moving and once you make it over 10mph, you get another safety warning that once again disables input to the unit (inputting addresses, watching video, etc).

 

However, this software warning can also be disabled (via testmode) by changing the parking_break_speed value in the DATA.zip file (/project_config/pioneer.ini) does in fact bypass the video/gps restriction . Looks like this:

[pioneer]

parking_break_speed=16.0

hide_logos=1

 

Change the 16 to 256 (I think) and you have bypassed it.

 

The question is, is it still accessible and is it still in an easy to find spot - not to mention, IF you can find it - DOES IT STILL WORK...

?

The complete hardware bypass involves both grounding the parking brake wire and moving and grounding the mute wire. When this is done, there is nothing else to bypass. The software bypass simply substitutes moving the mute wire with changing the speed setting in the INI file. The end result is identical.

Is the link search feature available in version 3.0?

+1 on this.

Iaf?

The complete hardware bypass involves both grounding the parking brake wire and moving and grounding the mute wire. When this is done, there is nothing else to bypass. The software bypass simply substitutes moving the mute wire with changing the speed setting in the INI file. The end result is identical.

When I had hard wire bypass only, I would get a parking brake warning when I went over 10mph (I think that is the correct override speed), this continued until I did the software bypass.

Either way, the question remains: can you still software bypass using testmode in 3.0

wait so is scrolling through the songs on the SD card much faster now? can't for sure tell on the video

The complete hardware bypass involves both grounding the parking brake wire and moving and grounding the mute wire. When this is done, there is nothing else to bypass. The software bypass simply substitutes moving the mute wire with changing the speed setting in the INI file. The end result is identical.

When I had hard wire bypass only, I would get a parking brake warning when I went over 10mph (I think that is the correct override speed), this continued until I did the software bypass.

 

Either way, the question remains: can you still software bypass using testmode in 3.0

The only way that is possible is you screwing up the process. Moving and grounding the mute wire would have eliminated that problem.

The complete hardware bypass involves both grounding the parking brake wire and moving and grounding the mute wire. When this is done, there is nothing else to bypass. The software bypass simply substitutes moving the mute wire with changing the speed setting in the INI file. The end result is identical.

When I had hard wire bypass only, I would get a parking brake warning when I went over 10mph (I think that is the correct override speed), this continued until I did the software bypass.

 

Either way, the question remains: can you still software bypass using testmode in 3.0

The only way that is possible is you screwing up the process. Moving and grounding the mute wire would have eliminated that problem.

True. I have had the hardware bypass from day one of my install and have always had full functionality of my unit.

Your hardware bypass must have been faulty.

Question still remains as to testmode working (apparently yes) and what modes can be done. Hopefully more will become clear soon.

iaf_22: any answer to this question?

well ckelly sounds like your hardware bypass didnt work right. The whole point of the hardware bypass was so you dont get that warning over 10mph.

It should and does work on the 2 versions and sounds like IAF's version too.

Sounds like it.

Seriously, there are too many people with video lag issues for this thread to just DIE like this.

So what do we know so far: This is a EU-only update, and the version number is 3.002, which is technically prior to 3.0101, which is the latest.

Can we assume that 3.0101 includes the 3.002 stuff?

If so, can anyone with 3.0101 confirm that the video lag is gone?

I'm particularly interested because I'm running DiVX files off my USB drive.

Please share if you have info.

Thanks.

iaf_22, thank you so much for the video and your info!

 

Can you confirm to us that you can still do the soft-mod for the handbrake? i.e. you can still insert the vehicle speed in the .ini file?

 

Thank you!

 

Not sure what you mean... Are you talking about watching video while the parking brake is off ?? The shop who installed me the Avic did this bypass for me... and this is still working.

But maybe that's not what u meant... ??

 

Allright iaf_22 here's the nutshell: there are two types of bypasses, a hardwired and a software. The software is primary source of concern because of the questions with testmode's functionality. Hardwire fools the unit into thinking the parking brake is pulled. However, when you start moving, the gyros/GPS senses your moving and once you make it over 10mph, you get another safety warning that once again disables input to the unit (inputting addresses, watching video, etc).

 

However, this software warning can also be disabled (via testmode) by changing the parking_break_speed value in the DATA.zip file (/project_config/pioneer.ini) does in fact bypass the video/gps restriction . Looks like this:

[pioneer]

parking_break_speed=16.0

hide_logos=1

 

Change the 16 to 256 (I think) and you have bypassed it.

 

The question is, is it still accessible and is it still in an easy to find spot - not to mention, IF you can find it - DOES IT STILL WORK...

Well, my initial installation was made by professional, and of course i never had this park brake limitation. So i guess they 've done it the hardwired mode ( ?? ).

Going to 3.002 didn't change a thing on this matter.

I have a F900 with the x-series 3.01 firmware (all except the igo directory). Noticed video lag significantly decreased. Even button response when video is running is better (not perfect, but much better). Playing videos off SD with following specs:

Package- .AVI

Video code-mpeg4

Video size-720 x 576

Video Framerate-25 fps

Audio Codec-aac or MP3

Audio Bitrate-128

Sample Rate-11025