Quila

1 hour ago, joshtrel99@yahoo.com said:

 

Also looking for sensor disconnect location. Any progress?

 

 

Mine literally tried to kill me like a trash compactor.

 

 

 Tapped on the back?! I was literally fighting to have it stop crushing me. 

 

 

Can anyone point me to the location of the sensor plug in? I would like to disable this foot thing....

I actually was hit by the liftgate again last night and was a lot more than a tap this time.

The hands-free liftgate actuation module is behind center the section of the rear bumper cover.  That's the piece that is closest to the tailpipes and hitch receiver.  There are 18 plastic tabs that hold that cover in place and then you should be able to see the module on the passenger side of the car (North American) with three connectors plugged into it.  There's a connector for each of the upper and lower sensors and a power connector.  The connector on the left side is the upper sensor, the middle connector is the power connector and the right connector is the lower sensor.  I don't know if disconnecting these will cause any other issues, but I may give it a shot myself when I have some time.

On 1/18/2019 at 4:08 AM, wildbillpookers said:

I was told that what you have is what you have.

There is no update for navigation on the 2016 Edge?

I have, sync 3 software 3.0

Gracenote, 1.1.1.1139(NA-0010)

Navigation Maps, 1 14

 

This is suppose to be totally up to date!

There was an update for the 2016 Edge at one point.  I bought it for my Edge.  The maps are now 1 16.  I bought the update through a Ford dealer in BC.  They didn't think there was an update, but I kept asking and eventually they found it.  The update came on a USB drive and the serial number of your Sync system had to be encoded into a file on the USB.  The update took about 20 minutes.  I don't think it's available online.

I've got a 2016 Edge with Sync 3 and Nav. I can take a look at 720-05-01 later today and let you know what I see tonight.

However, from looking at the mod sheet, it looks like the 2 in D028 means no climate control without nav. D038 would mean no climate control with nav. The default value for nav is D8B8 and the default value for no nav is D8A8. Those codes are hexadecimal values and if you break them down to binary, it appears that there is one bit that is the toggle for the nav menu. I'm looking specifically at the third digit in D028/D038/D8A8/D8B8 and the fourth binary digit of that third hexadecimal digit. (I'll try to keep the computer gibberish to a minimum).

In binary 2 is 0010, 3 is 0011, A is 1010 and B is 1011. Think of those binary digits as toggle switches. That fourth binary digit is the one that appears to be the nav menu toggle. It's 1 (or on) for each code for nav and 0 (or off) for each code for no nav. The first binary digit appears to be the toggle for climate control. I don't have climate control on my right screen, so I would guess that my code is D038 right now or maybe D838. I'm not sure what the second hexadecimal digit does.

If you're seeing D028 right now, I'd change that to D038 to enable the nav menu on the right screen. Changing it to another value means that you would be changing other bits (or toggle switches) and we don't necessarily know what they do.

Edit: I just downloaded my as-built data from the Ford/Motorcraft site and it shows 720-05-01 on my vehicle as D838.

I updated to v3.0 in March 2018, and after seeing your post I logged on and it indicated that my Sync isn't up to date, so I went through the whole update and uploaded the xml log file, and it still says that my Sync isn't up to date.

I updated my Sync on Saturday and uploading the XML file didn't seem to register with the Ford Owner site. It would say it accepted the upload but then say that I still needed to confirm the install by uploading the XML file. I just logged into the Ford Owner site now and it says I'm up to date. Whatever the problem was, I think it was on the Ford web site and it's since been fixed.

I just got a 2017 Ford Edge Titanium. I can't get my Google Pixel 2 nor my wife's Samsung Galaxy S6 to connect via Android Auto. Both will connect via Bluetooth. No probs there.

 

I've gone into the Settings and "enabled" Android Auto. On my Pixel 2, I get a message that it's not responding. On my wife's S6, I get a message that it requires too much power. So I went onto the Ford owner site and saw a link for compatible phones. There are 7 phones that are listed as compatible. SEVEN. Really. Please tell me that there are more than 7 phones that work with SYNC3 and Android Auto.

 

Any help?

My phone isn't on the list of compatible phones but it still works with AA. I think the compatible phone list is just a list of phones that Ford has actually tested. It doesn't mean that phones not on the list won't work.

Try a different cable as omar302 suggested. There are a lot of cheap USB cables out there that can cause all kinds of problems.

I read that 18025 was for non navigation vehicles and that 17276 was for vehicles with navigation. I don't know but possibly some one has more information.

I have navigation and my SYNC build number is 18025. I seem to recall reading somewhere that you need to downgrade to 2.2 before it will upgrade to the official 3.0 from the unofficial version. I never installed the unofficial version, so I can't offer any real advice based on experience.

For those that have updated to version 3.0 do you see any difference in performance from v2.3. My edge recently did an auto update from 2.2 to 2.3 and since then I experience screen lockups that last 20-30 seconds at random when switching between functions. Didn't have that before 2.3. Does 3.0 solve this? Are there any issues with V3.0? I have downloaded it onto a flash drive but have yet to install it.

I didn't notice any lockups in 2.3 although I didn't change the screens all that often. I've been changing the screens quite a bit in 3.0 looking for any new features and getting Applink to work with my Android phone and didn't notice any lockups at all.

I contacted the "Naviextras" support and they sent me back that Ford Sync3 Navigation map upgrades are thru this site https://why-update-ford.azurewebsites.net/

When I go on that site it shows OFFICIAL FORD SYNC® 3 NAVIGATION MAP UPDATE WEBSITE, BUT THAT SITE DOESN'T ALLOW ME TO DOWNLOAD THE MAP LOADER?

Based on the address for that site, that is most likely a development site and most likely not meant or ready for public use. The support group for Naviextras probably shouldn't be giving that address out since development sites usually have a lot of broken links.

 

For the 2.3 update I left my engine running - this requirement is crazy, and I'll give it a try with just the ignition on.

I think the reason they say to leave the engine running is that the accessory power will not stay on for 30 minutes without the engine running. If Sync3 shuts down during an update, that could result in a botched update. You can still drive while the update is in progress, it just needs to be in park to start the update. Once the update is started, you can drive the vehicle. Ideally, start the update just before a 30+ minute drive.

You should be able to adjust this in the settings menu on the left side. Go into Settings, Vehicle, Remote Start. There are settings there for climate control, seats and steering wheel.

It sucks that maps don't get updated, but I just chalk it up to a learning experience. I have no intention of buying built in navigation again unless there is some kind of written guarantee that maps will be updated. Of course, when they realize people don't want to pay for outdated navigation any more, they'll probably start charging for Android Auto and Carplay. BMW is already charging for Carplay and wants to start charging an annual subscription fee for it.

https://www.theverge.com/2018/1/16/16897326/bmw-apple-carplay-subscription-google-alexa-detroit-auto-show-2018

So, I have to make a correction. Waze app itself has not been updated for CarPlay compatibility yet. This will be coming in March.

 

Sorry for an inconvenience!

 

Your SYNC version will need to be 3.0 or higher. The latest version (as of now) is v2.3 over WiFi. So it seems as though FORD and Waze both needs to issue updates, which are expected within two months.

I think this is old news, or maybe I'm missing something. Waze has been working with Sync3 and Android Auto since Sync3 version 2.2. Actually, I think there was an update to the Waze app before it worked with Sync3 2.2, but it definitely worked before 2.3 came out. You need to have Waze installed on your phone and the phone has to be connected to Sync3 with a USB cable. Then on the navigation button you can select either Google Maps or Waze.

335 hp, 380 lb-ft of torque, 8 speed automatic transmission. I don't think I'm in the market for a new Edge quite yet, but it looks interesting.

http://www.roadandtrack.com/car-shows/detroit-auto-show/a14783801/2019-ford-edge-st-specs-info-pictures/

This doesn't happen for me. I use Waze through Android Auto and just select Waze from the map icon. I have to admit that I would use it a lot more often if it would stay running until I got to my destination, but it doesn't turn the radio on. I think Android Auto is still pretty buggy.

I've been driving in mountains through some pretty extreme winter conditions for a little over 30 years and have never put chains or cables on my tires. Good winter tires and careful driving is all you really need. Avoid any sudden maneuvers and go easy on the gas and brakes. AWD or 4x4 is nice to have, but don't assume it makes you invincible. I always see lots of SUVs off the road.

162 N-M is basically 120 lb-ft. I wonder if they used the metric rating but English units.

The owner's manual says "162 lb. ft (220 Nm)", so I don't think they mixed the units up.

I did a bit of Googling on this last night and it looks like 150 lb. ft and higher is not all that uncommon these days, especially for wheels with larger lug nuts.

162 lb ft seems high, but that's what Ford has printed in the Edge owner's manuals since at least 2016. I originally thought it was a misprint, but it's still in the 2018 Ford Edge manual. Every other vehicle I have owned has always been 100 lb ft. I'd kind of like to know why they went so high as well.

My battery was dead after being parked for 23 days last June. That was with the alarm system installed. I didn't park it that long before I had the alarm installed, so I'm not actually sure how much of an impact the alarm had, but I'm sure it shortened the life a bit. Actually, I'm not even sure at what point during those 23 days that the battery died.

This was a problem with my last vehicle too, so I've got one of those Li-Ion jump starters that fits nicely in the center console. That's so much easier than looking for someone to give you a boost.

Those aren't alarm lights, they're just lights to tell you that the doors are locked. If you want an alarm light, you need to add the optional perimeter security system (FT4Z-19A361-A) with the also optional LED indicator (DM5Z-19D596-A).

I added that to my Edge specifically for the flashing alarm light. I don't care so much about the alarm, but was hoping the light would at least be a bit of a deterrent to someone who might try breaking a window. However the light only blinks about once every 10 seconds and it's only on for about a quarter of a second at a time. You have to know where the light is and wait for it to see if the alarm is armed. I doubt it actually would work as a deterrent.

Are you parking somewhere where the SiruisXM signal might be weak? I don't use SiriusXM, but I use Spotify over Bluetooth a lot. Most of the time, Sync 3 connects to my phone and starts playing music from Spotify when I start the car. Sometimes it takes a bit too long for the connection to happen and it defaults to the radio instead, usually whatever the radio was last tuned to. The same thing might be happening with SiruisXM if it's not locking onto the signal quick enough. Just a semi-educated guess.

I didn't have any luck finding anything decent in the local shops, so I bought mine online at www.wheelwiz.ca and paid about the same price ($2020 CAD all in). Shipping was free, tires were mounted and balanced with TPMS sensors. I put them on myself and used a Bartec Tech 200 tool to clone the original TPMS sensors onto the new wheels. I'm on the west coast and the wheels were delivered just under a week after I ordered them (shipped from Montreal). I have to admit I was a bit hesitant ordering from a relatively new company online, but I was impressed with their service and knowledge.

Wheels are 18" Fast Switch titanium finish and tires are Michelin Lattitude X-Ice2. I had Michelins on my previous vehicle and they work very well for the terrain I drive in. Fast Wheels list these wheels as "approved for winter use" which I think just means that there are no surfaces that might corrode with exposure to salt.

Whats worse is if you use the apple carplay feature you have to have it plugged in to the usb port and during the day that's fine but at night you have that distracting little light when that little door is open. there is a few things ford didn't think through

I usually just put the phone in the cubby and close the door.

I did the update from a 2 GB stick. It took about 20 minutes on my drive home today. No map updates. Hopefully Android Auto will crash a little less often.

I didn't have to change any settings after the update.

It may store temporary data on the drive also but 32 does seem like overkill.

That's definitely possible. I've actually got a 2 GB stick here. I'm curious enough to try to do the new update using that stick now. I know for sure that the last update worked with an 8 GB stick.

I checked via wi-fi last night using my phone as a hotspot and it didn't see an update. I'll try tonight or I may try a USB stick. Do I really need a 32 GB stick to do this?

2 GB is probably enough. The files that are copied to the USB stick use about 1.7 GB of space and the upgrade only needs a very small amount of free space to write a small log file. I used an 8 GB stick last time and have copied the new files to the same stick. I'll update on my way home tonight.

I'm not sure why they say you need 32 GB.