Should have been more clear. I was referring to Auto High Beams. Head lights do turn on/off from day to night. But the auto dimming of brights when there is oncoming traffic is gone. The feature in the settings menu is there, but I never get the ‘(A)’ icon in the driver display, and it doesn’t auto dim for oncoming traffic anymore.
-
Want to remove ads? Register an account and login to see fewer ads, and become a Supporting Member to remove almost all ads.
Should have been more clear. I was referring to Auto High Beams. Head lights do turn on/off from day to night. But the auto dimming of brights when there is oncoming traffic is gone. The feature in the settings menu is there, but I never get the ‘(A)’ icon in the driver display, and it doesn’t auto dim for oncoming traffic anymore.
Pagemakers
Active Member
Just installed 2019.16.2 on a UK HW2 S.
It gives navigation on Autopilot for the first time.
Initial short drive seems OK on autopilot with no disconnects round tight-ish bends.
The one thing I have noticed is it no longer displays dual carriageways as 2 lanes so it is not possible to change lanes with the autopilot engaged. Is this a function of Navigation on Autopilot? If I turned that feature off would it once again see the road as 2 laned?
It gives navigation on Autopilot for the first time.
Initial short drive seems OK on autopilot with no disconnects round tight-ish bends.
The one thing I have noticed is it no longer displays dual carriageways as 2 lanes so it is not possible to change lanes with the autopilot engaged. Is this a function of Navigation on Autopilot? If I turned that feature off would it once again see the road as 2 laned?
Appears that Lane Departure Avoidance is not included for S/X in release 2019.16.2, only for the model 3. My MS has AP2.5, so that is not the issue.
Given the conflicting reports on this, and also conflicting reports on the availability of various features from people with the same hardware and same software version, I wonder if Tesla is conducting A/B tests of some sort. They roll out firmware capable of a feature, but disable that feature through configuration on certain cars, either randomly or by geographic area? This would be strange though... when would they choose to enable it in the cars where it is disabled? In a future software update that doesn't actually update the software, but just the configuration?
My 2015 Model S 85D updated to 2016.16.1.1 last week right as I was leaving for some work out of state. I got back and haven't driven the car yet but hopped in to see the updates. I noticed on the Software section of the UI, it says "Software Downloading" (or something along those lines) with a progress bar that appears to be sitting at ~1%. It's been like that for hours and hasn't moved (car is connected to wifi). I tried rebooting everything but it appears to be stuck there. I'm assuming it's trying to download 2016.16.2 but any ideas as to why it appears to be stuck? Double checked my firewall to make sure it's not blocking anything. It hasn't been an issue in the past so I don't think that's it anyways.
ahkahn
Active Member
I just updated this morning, looking forward to trying it out.
I got Sentry mode on my 2017 AP2 car with 2019.12. With 2019.16 should I now be seeing video files recorded on the USB? Or do I have the wrong hw for that and video is only saved to the "Tesla Cloud"?
I saw some reports of corrupt video files being created on AP2 cars but to be honest I have lost track of which sw features goes with which hardware.
I got Sentry mode on my 2017 AP2 car with 2019.12. With 2019.16 should I now be seeing video files recorded on the USB? Or do I have the wrong hw for that and video is only saved to the "Tesla Cloud"?
I saw some reports of corrupt video files being created on AP2 cars but to be honest I have lost track of which sw features goes with which hardware.
My car has the same problem and it did not resolve with the 2016.16.2 update. Any solutions on your end yet? I got an email from customer service yesterday stating it’s a camera calibration issue that needs a service center visit.
Make sure you have your high beams turned on manually as well. The "automatic high beams" are actually automatic dimming of the high beams. When you toggle the high beams on via the left stalk (lights on or off) you should see the A icon. With X or S this means leaving the stalk in the forward position to keep the high beams on. A slightly rough turn signal activation can turn high beams off. For the 3 the stalk returns to the center. Less likely to screw it up with a turn, but the software might forget the state after an update and reset.
Understand - my experience has been that with new firmware it seems the car needs to be taught again - like a recalibration on AP and then it is better than before. Just got 16.2 and noticed some negative differences on a daily traveled portion of roadway today. No evidence just a theory based on my experience. Maybe a new NN?
Shock-On-T
⚡️⚡️⚡️⚡️⚡️
I had the exact same issue, was resolved by replacing the radar, triple front cameras and side cameras. It happened after updating to 2019.12.1 and Ive seen others report the same thing. Not sure if the software and hardware have some incompatibility or maybe the new software is more sensitive to the inputs, but it does seem related and it was fixed after those items were replaced and re-calibrated by Testa.
Made a post about it here: What could be wrong? Both Autopilot and Cruise not working at high speed
I lost the "Lane Departure Warning", and it must have happened after 2019.16.1.1 or 2019.16.2.
The browser, however, is usable again.
On Edit: Till today, my rated miles was unchanged and at %90 Soc was still showing 238 after over 4 years of ownership and 43K miles, when others expectedly report the RM losses of few percentages. Today after charging to %90, I noticed for the first time the charging completed at 232 miles, a loss of about %2.5 since I took delivery of the car. My car's RM is recalculated after 2019.16.2.
The browser, however, is usable again.
On Edit: Till today, my rated miles was unchanged and at %90 Soc was still showing 238 after over 4 years of ownership and 43K miles, when others expectedly report the RM losses of few percentages. Today after charging to %90, I noticed for the first time the charging completed at 232 miles, a loss of about %2.5 since I took delivery of the car. My car's RM is recalculated after 2019.16.2.
Last edited:
Automatically arming the sentry mode is cool. I guess that it's some kind of a deterrent, especially once more crooks see themselves on YouTube videos from Tesla's with AP3 hw. I have dashcam anyway.
I didn't notice any difference in AP performance. Browser works again too.
I pity the person at Tesla in charge of change control and their sw/hw matrix. This is why most car manufacturers don't do OTA updates.
ahkahn
Active Member
Browser on MCU1 is actually usable again on 2019.16.2. Not the greatest, but I was able to surf around reasonably well. Great firmware cleanup, Tesla!
Yeah it is a double edged sword, OTA is great for rolling out new features but also gives the programmers an easy out if they get it wrong. Their system isn't working very well though, it needs a shake up and refocus rather than stacking more wood on the very delicate pile with each release.
I'm guessing there is no old school programmers working there from back in the days when games were burnt to ROM's (arcade machines) or recorded to floppies/cassettes and mass produced, you had to be very thorough or it cost money to fix.
I see the same insanity with modern games consoles, Gb's of updates needed everytime you play a game.
Similar threads
