murse
Member
2018.34.b4c2b9a installed and IC reboots have stopped
Reboots are still happening. Not quite as often but still daily.
You can install our site as a web app on your iOS device by utilizing the Add to Home Screen feature in Safari. Please see this thread for more details on this.
Note: This feature may not be available in some browsers.
2018.34.b4c2b9a installed and IC reboots have stopped
It appears to be completely random. Very few releases go "wide" where they're pushed to the whole fleet while other releases are only ever pushed to a minority of cars for reasons we can only speculate. Perhaps they just want the feedback (not from the people, the cars) of a certain number of cars only, or they're pushed for specific submodels when there are issues with them. Either way, there is no transparency from Tesla as to how or why they choose which cars to send it to, and it's normal to get releases only about every 4-6 weeks, and not all the ones in-between. If you have a specific issue you can ask your SC to push a newer version, and they can't specify a version but just ask for the latest to be pushed, but otherwise they will refuse to do it. There was a promise made for a feature to "look for updates" but that is one of those promises that falls into the who-knows-when-if-ever category.Hello fellow MS owners, so I have a question about these Tesla updates. I have a 2015 MS 85 currently on version 2018-32.2 (3817FDD) and something I don't understand is how exactly these updates get pushes to us. Everyone is talking about receiving this new pin to drive update but I'm sitting over here like, "WDF is my car waiting for? I guess my question is, are the updates based on where you live like state by state or is it the newer vehicles first then eventually the older cars? Also what exactly would you define a classic owner to be, someone with a 2013 and older? Can someone please help a fellow owner out. TBW I do live in California not that this matters since I seem to get updates way after the fact.
I installed this update yesterday.
Everything seems to be working OK, but AP2 seems to have regressed slightly in each of the last 2 updates.
I'm having more often / more dramatic phantom braking incidents, less recognition of braking cars in front of me when travelling at high speeds, and it is discontenting more often on curves, especially in HOV lanes where is still tries to hug the left shoulder / median....also still have issues with certain areas where the TACC / AP2 speed drops when passing an off-ramp, as well as not recovering the original set speed after dropping the speed for lower speed corners. Still a bit frustrating having the same issues in AP2 as ?I had 6-8 months ago - very little progress with AP2, IMO...
I did not. I will do that when I leave work. Is the scroll wheels reboot good enough or should I do a full Power Off for few minutes?have you rebooted since the install? Consensus from posts here say to reboot after you do an update to shake out the squirrels.
I did not. I will do that when I leave work. Is the scroll wheels reboot good enough or should I do a full Power Off for few minutes?
Perhaps the later one was so buggy it was pulled and they're deploying the earlier one instead?I got an update last night. But it was to 34.1. So... head scratcher on why its not the latest.... *shrug.
sounds like a good guess to me.Perhaps the later one was so buggy it was pulled and they're deploying the earlier one instead?