Knightshade
Well-Known Member
Like did he give you his personal paypal to send it to, or did he send an actual official Tesla estimate for the bill? (if the later I'd love to see it)
-
Want to remove ads? Register an account and login to see fewer ads, and become a Supporting Member to remove almost all ads.
Just got 2019.24.4
- Thread starter mwenn1
- Start date
Like did he give you his personal paypal to send it to, or did he send an actual official Tesla estimate for the bill? (if the later I'd love to see it)
alseTrick
Active Member
Was your issue the same in that a map update was stuck and needed to be repaired or were you just asking to have a newer firmware version pushed to your car?
pdx_m3s
Active Member
Well someone at Tesla must have been watching this thread. My navigation data updated as soon as I got home and connected to WiFi.
In all seriousness, though, they’re probably just slowly rolling it out. Patience.
BulletToothWoo
Member
Well, I just went out on a relatively empty I-25 in Denver to test out the new map data. I drive 10 miles to work each day on the south end of the city. I-25 north to Colorado Blvd. Since I got my car in May, the interchange there has counted too few lanes and NoA always puts me in the wrong lane for my exit. I was hoping this update would correct the number of lanes there. Nope. It switched lanes to the 2nd from the right lane less than a mile before the exit, looked for the exit markings, didn’t see them, and blew on by.
Unfortunately, the phantom braking was terrible and after I turned around at the next exit, got back on the freeway and headed home, it was herky jerky, then slowed down on the freeway to 40 mph to attempt to exit at my return exchange. It does not slow like this at the other exchange if I cancel the lane change it wants to do before exiting. Seems unique to this exit (with limited additional testing, admittedly).
I know it is in beta, but there is still a long way to go. I hope V10 improves on this behavior. NoA is essentially useless to me for my daily commute (on both ends) since I got the car. I guess I’ll continue to be patient.
In the meantime, is there someone I should notify of the map discrepancy?
Unfortunately, the phantom braking was terrible and after I turned around at the next exit, got back on the freeway and headed home, it was herky jerky, then slowed down on the freeway to 40 mph to attempt to exit at my return exchange. It does not slow like this at the other exchange if I cancel the lane change it wants to do before exiting. Seems unique to this exit (with limited additional testing, admittedly).
I know it is in beta, but there is still a long way to go. I hope V10 improves on this behavior. NoA is essentially useless to me for my daily commute (on both ends) since I got the car. I guess I’ll continue to be patient.
In the meantime, is there someone I should notify of the map discrepancy?
I posted the following in another forum tonight. Hope it helps.
********
So, this is very interesting.
A few months ago, I noticed that both Apple Maps and the Tesla navigation system both routed me in a very strange way near my house, as if the principal neighborhood road right by my house was closed or otherwise impassable. Google Maps has never made such errors in the five years I have lived here.
When I looked at the info page on Apple Maps, it indicated that the map data was coming from TomTom. So, I created a TomTom account on their map editor website, where, sure enough, my local street was marked as blocked. I submitted a correction and then went about my business.
Fast forward four or five months, to today. Maps version 2019.20 was pushed to my car this morning. On my commute home this evening, the car routed me via my local street that even yesterday it refused to use. Eureka!
It would therefore appear that, in my neck of the woods, at least, Tesla's system is getting at least some map data from TomTom, despite the screen's saying that it comes from Google. So, if you have map errors on your car, you might try reporting them here!
Map Share™ Reporter
alseTrick
Active Member
Firmware update when ~96% of owners (per TeslaFi's website) had a newer version of software than I did.
My thinking is, I prefer HW 3 so that IFF more FSD functions are released I’ll get them without the wait for a computer swap. I paid for FSD, it would be nice if the hardware is ready for it so it’s a matter of a software OTA update.
One percent of the TeslaFI fleet is on 15.104 or 15.105 - over 80% are 24.4.
My Raven X with H265 videos is on 24.4.
It's possible that's an aberration - it was delivered on a 2019.15 build in early June and the second day I rebooted it for a glitch and it said firmware update required and twenty minutes later had downloaded the then current version (2019.20.x, I think,) and offered to update.
Since then I've had several updates, about one every ten days.
You seem to be the exception as there is no Model 3 with HW3 having the 24.4 firmware reported in TeslaFi database.
TeslaFI doesn't reliably identify HW3 vs HW2.5 at the moment.
BulletToothWoo
Member
Mrcarcrazy
In need of a shrinking gun to zap a plaid with.
This is what I finally received after submitting a service request for software update. I went back and forth and zero F’s to give. I’m connected to WiFi and plugged in from 5pm-7am...nothing. Appreciate the map update but I hadn’t had any problems during my routes. Build date of 23 June 2019, should be HW3 but haven’t confirmed via file format, I will today.
Why have a software update request in the service section if you’re not going to do anything? I did tell them that my blinkers have stopped making noise a couple times and that was of concern to them but nothing back yet.
Because if you are having a problem getting an update or have one stuck you may need to have them do something. But in your case they are saying that at this time there is not a newer firmware version assigned to your car, so there is nothing for them to do.
Similar threads
