mhejl

Can anyone confirm if the many nagging bugs in 3.x have been fixed? Like: random boot to black/nav screen, HD tuner preset info, skipping multiple channels, going to map at end of call, 3-d limited zoom and street names, ... I'm not paying that much for just maps - I wish they'd just release a firmware update to fix the existing bugs!

Another Droid issue I've had. Pull the battery from the phone and restart.

I've had problems with my Droid/F90, too. One issue I found was using 86,,, as a contact for voice dial (the "," are pauses). I'd get an error screen saying "no number". Deleted the contact and it sync'd. The Droid has other means of dialing voice mail. No problems with this on my old Razr. Other times, I'd just get a failure message. Restarting my F90 and/or deleting the Droid and re-pairing usually works. Now, on my 2nd droid (the first returned for the #@&^ echo problem) I get all sorts of goofy contacts in my F90. Lots of , contacts with the box being first,last name holde

Me too - Input device number is not correct. I'm so fed up with this damn thing (Pioneer, in particular!) it may be time for an Office Space printer episode. And it isn't O (oh) vs 0 (zero) because it is a hex number.

Another known bug. Happens with my P10 HD radio, too. Mine has even gotten stuck in an infinite loop requiring a reboot.

I've noted before that I've had my P10 connected to two other HUs (FH-P8000BT, DEH-P7000BT) besides the F90 and it worked perfectly - including preset info and song info. The issues aren't in the tuner - it is in the F-series.

Allow me to continue the digression... This capability is not possible with existing "3G" cellular technology and will require "4G" infrastructure including WiMAX and/or LTE. The former requires entirely new infrastructure and is based on IEEE 802.16 standards and is currently ahead of LTE in standards, development, and deployment. Simplisticaly, LTE is a "retrofit" of existing infrastructure (i.e. more cost effective) but still requires a substantial investment for CDMA/GSM carriers. Consequently, wide-spread deployment won't likely be for years...

You only need to mod if you want the option displayed when vehicle type = car. Otherwise, just set it to pedestrian and the AlignToRoad is displayed (and off by default). See comments in the "iGO sys.txt" thread: you need to mod both common/ui/setting.ui and sys.txt.

This annoying behavior isn't just the F series - it is a Pioneer thing. I have three recent Pioneer HUs (with USB) and all do the same stupid thing.

Even with the edit above, the (new) radio button is disabled if vehicle type is "Car" (F90BT). This is disabled in common/ui/setting.ui and then defaulted to off in other cases. Comment out the following (note the comma in the first edit): : [...] ;-----my init ui_SettingRoute.y 0 runif nVehicle 0 'nVehicleTmp.set "Car", btn_vehicle_value.set "Car"' else_runif nVehicle 5 'nVehicleTmp.set "Pedestrian", btn_vehicle_value.set "Pedestrian" ;, btnSR_AlignToRoad.DISABLE' runif nVehicle 5 'rdkeepposon.enable, rdkeepposoff.enable' else_runif nVehicle 6 '

Why would the new HD tuner version "fix" anything? The "old" one works perfectly with two other Pioneer HUs I have - just not with the F-series. This would imply the issues are with the F-series, not the tuner. FYI - we know about the presets jumping multiple channels, right? My F90 got stuck in a loop - beeping and changing presets until I rebooted it. Grrrr...

Subarus also require an antenna adapter - at least the '05 Legacy I just did an install in. Are you sure the antenna (not just the power motor) is even connected? You certainly do not use butt connectors, solder, etc. on the coax antenna feed.

Here's mine (I suggested the o-ring):

Got mine - the o-ring one - Looks GREAT! Perfect choice for the o-ring location, too (offset toward the front). Before I mount it, though, I'm going to mount it on my (wood) lathe and do a high polish job. Then again, maybe not - gotta stare it for a while... I didn't realize this was an "overlay" and fit *around* the existing knob. Now I understand the #40/41 drill bit (non-) issue. For those of you concerned about the price increase, it is still worth it. Thanks, Thomas!

Thomas: Did you investigate the possibility of using #40 or #41 drill bits I emailed you about? Any more news on the tight fit? BTW, I say THANKS, too! Just ignore that cretin.