garyd9

She will say something like "There is a six minute slowdown in 8 miles. This is still the quickest way to your destination. You should arrive at 6:42".

Odd.  For me, she keeps threatening that I won't get any ice cream.

Is it possible to re-create a "warp" compatible image once any firmware changes are made?  This would give people the best of both worlds (customizable and quicker boot times.)

Also, what version of android are the NEX units running?  I'm wondering if xposed framework could be made to work with it...  That should allow some quick changes (like bypassing the boot up "warning" screen) fairly easily.  

Some ideas of what to do...

* (As mentioned,) bypass the bootup warning screen

* some digging into whatever launcher code they are using -- or just replacing the launcher (else adding anything would be pointless)

* If the device/kernel can handle multiple BT connections at once, perhaps OBDII software (such as torque) on the HU would be nice.

* getting some form of adb working would be extremely helpful.  Otherwise, testing stuff will be a PITA.  (However, I doubt the USB ports on the HU will work in that mode.)

* if getting adb working isn't an option, perhaps a version of the firmware could be put together that would work on a tablet (nexus 7?) to use for testing/debugging.  

...  just some random thoughts.

Take care

Gary

 

Anyone had any success resolving these issues or have Pioneer's just always been this bad at route guidance options?... I was shocked that my route wasn't shown first, but even more floored when it wasn't eve one of the multiple options under alternate routes...

It's "iGo" (the nav software) and it sucks.  Like I said with my "first impressions", the nav software is similar to the very early generations of garmin/tomtom units with all the associated issues.  If it weren't for android auto (and google maps), I'd have returned the unit quickly based on the bad nav software.  As it is, however, it's okay as a backup for google maps.

I wonder if something like the 'xposed' framework would be a better way to go about changing things on the HU's.  (Search on XDA)

I think I understand some of the confusion.  herbert68, you aren't using an android phone, are you?  On Android, pandora only works over BT.  Over iThings, it works differently...

You left out a CRITICAL piece of information...

I think Kenwood advertises something similar for one or two of their units, but my experience with Kenwood's consumer car radio folks leads me to believe that they are even worse than Pioneer.  (Completely unresponsive, and generally give off the attitude of "you already paid for it, so screw you.")

(It's kind of ironic, as Kenwood's amateur radio people are the exact opposite.)

I guess it'd be impossible to help you without knowing what about "avicsync" you want?  The live updates on maps/traffic are easily provided by Android Auto.  You could also get an appradio compatible phone and use waze (or one of the various other mapping packages that are appradio compatible.)

Manjo, first - please keep it to a single thread.  I've been trying to help you, but you keep taking the one issue jumping between threads. 

Second, the "Android Auto cannot connect right now. When it is safe to do so, please check your Android phone." issue has nothing whatsoever to do with parking brakes, bypasses, etc.

Android Auto doesn't seem to use the head unit's parking brake detection whatsoever.  I have the brake bypassed in my unit (8100), and the head unit plays DVD's without the brake, etc.  However, android auto's maps hides the "search" box while I'm moving and shows it when I'm stopped (which indicates that it uses it's own movement detection.)

So, to what is apparently your real issue:  The "cannot connect right now" message:

This might seem obvious, but the obvious should be checked anyway:  

Is the Android Auto app installed on your Nexus5?  Are the apps all up to date?  In particular, google play services, google play music, google maps, etc?  Are you sure that you're plugging into USB2 on the head unit (and not USB1?)

Usually, when I get that message (and I do on occasion) there's some prompt on my phone that I have to acknowledge before android audo can fully start.  Often times, it's some silly thing like Play Music asking me if I want to subscribe.  So, did you stop your car and check your phone?

When android auto is running and the phone is attached, you should see notification icons for "car mode" and "android auto."  When you unlock the phone, you should see the android auto splash screen (which is different than when you run the android auto app on your phone manually.)

Oh, it might not matter, but turn on "usb debugging" in the developer options.  It seems to help some people.  

Finally, please describe, in detail, the steps to repeat the issue. Please don't make assumptions about what might be obvious and what might not be.  For example, you might start with:

I start my car, and after pressing OK on the warning screen on the head unit, I plug Nexus 2 phone (running android 5.21)  into the USB3 port on the back of the radio.  I then press the HOME button on the radio, and see "android auto" in the upper left corner of the radio.  I press that, and I get a message stating, "blah, blah, blah."  If I look at my phone, the screen is off.  I turn on the screen and I see "blah, blah, blah."  When I unlock the phone, I see "blah, blah, blah."

...

Gary

It's not typical, but there's no way to know what be "normal" in your particular car.  The radio begins booting immediately when it has power on the yellow and red wires (12v battery and 12v ACC) and a valid ground on the black wire.

I'd bring it back to Best Buy and ask them to wire the harness properly.

"android auto cannot connect..." has nothing whatsoever to do with your parking brake.  It's more related to the android auto app on the phone not being ready or waiting for the answer to some prompt.

In fact, as far as I've been able to determine, android auto uses it's own sensors to determine if you're stopped or not (and ignores parking brakes and/or brake bypasses.)  

I'll reply to myself.. I like talking to myself anyway...

Apparently, there's some incompatiblity between that sony camcorder and the HDMI port on the HU.  When I plugged in a RaspberryPi, the HDMI source worked perfectly.  

(Now that leads to all kinds of fun ideas...)

I pulled my 8100 this evening and plugged a HDMI extension in, and plugged a camcorder to the extension.  However, I couldn't seem to select the HDMI a/v source from the 8100.  From the "home" screen, it was grayed out, and it didn't show up at all in the drop down lists from the various A/V modes.

I then plugged the HDMI cable directly from the camcorder into the back of the radio (taking the extension out of the equation) - same result (can't select HDMI.)

I then plugged the HDMI cable from the camcorder to my television - that worked fine (so I know the cable and camcorder are working.)

I'm at a loss as to why I can't select the HDMI source from the HU.  There doesn't seem to be any type of setting for enabling or disabling it.  

Any suggestions?

Thanks

Gary

Your ipod is a 5th or previous generation.   The 6th (classic) and 7th (classic 160GB) generations resume fine.

The RGB connector is also used with Pioneer's CD-IU201S - it has a 30pin ipod/iphone connector on one end and both a USB and that RGB connector on the other end.    It's how the "video" connection is made with the ipod touch 4th gen, and a person should be able to watch videos stored on their ipod touch via that connection. 

I'm just wondering that can be mirrored to the rear.  (When using the AUX connector with an older ipod, it CAN be mirrored.)

Gary

What about the "RGB" connector that's used with some of the 30-pin iProducts?  (iphone 4, ipod touch 4th gen, etc)

Did your installer do something for steering wheel remote control?  It sounds like remote signals are being sent to the head unit each time the car starts (or perhaps stops.)

Regardless, get whoever installed the unit to fix it.

Just measure with a ruler. Cut it a bit small so it doesn't overlap the rounded corners.

I honestly don't remember the exact dimensions I used. I did a rough cut and trimmed as needed using a paper cutter (for perfectly straight cuts.)

If you're not in the US all you have to do is ground your parking brake wire.

(I'm sorry.. I REALLY can't resist...)

So if I take a quick run down to Mexico, I don't have to do anything special to bypass?  Will that "stick" when I drive north of the border again?  

 Can you describe how you did it? We should have the same menu options..

From the "home" screen, select the icon for "A/V", which should give you a grid full of various A/V sources.  Select "Camera View".

Or... from a A/V screen (ipod playing, FM radio playing, etc), select the circle with a arrow icon in it and it should give you a list of possible A/V sources.  I think the proper selection is CameraView.

(On the 8100 I can also press/hold one of the panel buttons - I forget which one.)

(page 13 of the 4100nex manual)

Additional Info:  On the 8100, when I view the rear camera (but am NOT in reverse), there are two icons on the top of the screen.  On the left is an icon that looks like a stopwatch.  That icon will cause the screen to jump back to whatever was showing before for several seconds, and then come back to the rear view camera.  (Useful to see the name of the currently playing track?)  On the right side is an "X" icon that just closes the rear view camera display.

Whoa Relax..

Sorry - my reaction is in large part due to naviextra's response directly to me (see post 3 in this thread.)  I do software development for a living and few things in life piss me off more than when my so-called peers blow off defects.

When it's broken, stop making BS excuses and just fix it.

i think you are throwing this a bit out of proportion, i have had many GPS units threw the years ranging from garmin portable units to several Pioneer avic units. Every single one of them miss pronounced street names on a regular basis. hell when garmin first put out a GPS it would take me off the highway then turn around just to get right back on the same highway i was just on.

I don't mind a mispronounced street name.  Actually, I'm used to that.  (garmin, tomtom, etc)  What bothers me is that instead of "Take exit five to eye sixty-eight east bound", I instead get "Take exit five dot to eye sixty-eight exabytes."  Since when would "EB" ever stand for "exabytes" in navigation?  

Instead of "Turn left on to Pea A 12" or "Turn left on Pennsylvania 12", I get "Turn left on Pa 12".  (I wonder if in Massachusetts the state roads all refer to someone's mother.)

This isn't mispronouncing local roads.  It's taking "E.B.", which in navigation TTS should always mean "EAST BOUND", and assuming an abbreviation for a unit of information (which makes ZERO sense for navigation TTS.)

It's also taking a STATE abbreviation (which is "PA", not "Pa") and instead of reading an abbreviation, reading a word.

If it assumes that "EB" means "exabytes" and not "eastbound", doesn't that mean it's going "mispronounce" 1/4th of every interstate in the country?  Yet, you suggest that I'm throwing it a bit out of proportion?

If it calls every state road in Pennsylvania a short version of "father", and every road in Massachusetts as a short version of mother, I wonder if it does the same thing for AL, DE, ID, LA, (and so on.)  If so, am I still throwing things a bit out of proportion?

Again, because it irritates me that someone would suggest I'm "throwing this a bit out of proportion."  This isn't a "local road being mispronounced" issue.  This is a case of a nationally used abbreviation for "east bound" being read as the word for "1,000,000,000,000,000,000 bytes"  In the case of I-68, it's being read as "Eye 68,000,000,000,000,000,000 bytes"

Do you have any idea how many roads in the United States (English-US TTS) have travel East/West?  Each one of them has a west bound direction and an east bound direction.  Is it still some minor issue to you?  Am I still "throwing this a bit out of proportion"?

As reported to pioneer:

You are correct.  I've experienced this with both of my 5th gen iPod's (one 60, one 80) and the 8100NEX.  

Being that the pioneer unit doesn't support playlists on USB or SD storage devices, the only alternative for you might be to play your music from your iPhone via car play.  My solution (which you've stated you don't like) was to purchase a used 7th gen iPod classic.  (My fallback to that would have been to get a refurbished ipod touch 64GB 4th gen.)

Does the PAC adapter have a wire marked "VSS"?  If so, that's what you want.

It's funny that I read this just now.  I just cut down and stuck on an anti-glare screen protector this evening.  I used one that was originally designed for a 2012 nexus 7, and cut it down to size.  As with anything that will reduce glare, it will also reduce some of the screen sharpness, but also help with fingerprints.

Here's a link to what I ordered from amazon:

http://www.amazon.com/gp/product/B008OHRJ32

Considering the price ($7 for 3), it's well worth it even if you throw two of them away.