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.
According to my local service center, they said yes the car needs to be on Wi-Fi preferentially.Does the car have to be on WIFI to get the update?
Yes, it is as I got my car (X) yesterday delivered with 2017.50_ and it was fixed last night with 2017.50.1 -- created this thread on 50.1 -- 2017.50.1 ceae3b8 is out per TeslaFISoftware version 2017.50.1 ceae3b8 was just detected on a Tesla Model S P100D with Autopilot 2 hardware. The highest previous version was 2017.50 2275226. You were alerted per your settings on TeslaFi.com.
I believe this is the fix for the fix
After 400km drive today
I notice the autopark is greatly improved
It detects the parking spot much better than .48
However, when I tried the autopark today, the car scratch the curb, good thing is little damage on the bottom of the bumper.
I have AP2.5 and EAP didn't break for me, instead, the breaking is one bit smoother than .48
I don't think autopark detects parking spots. It just puts itself between existing vehicles. That's why you can't use autopark unless there are vehicles present.
It didn't fully download until I was pulling into my subdivision. 5 hours later. So, that's why wifi is that much better - it's just a lot quicker than the allegedly throttled LTE.
No way! the full package is 820 or so megs. They do a binary diff so typical download is in tens of megabytes at most.the car had already downloaded 3/4 of the package, around 700 megs or so
No way! the full package is 820 or so megs. They do a binary diff so typical download is in tens of megabytes at most.
if you have ap2, that adds about 310M for the ap firmware download.
The longest part of the firmware download process is to apply the binary diff and write out full 800+ megs onto the emmc and then replicate that same write onto IC computer and then read it back to calculate integrity of the whole thing - needless to say neither of those depend on your download speed.
Well, without knowing the exact wording what is it you saw it's a bit hard to comment on it.Then perhaps it was 70mb out of 90mb, rather than 700mb out of 900mb. I was looking over the tech's shoulder at his screen. I can tell you 100% though the download speed was crap, both on wifi (which I was on for over 45 minutes, watching it download via his laptop) and on LTE, which 2 hours after I left the SC had still not completed when I called Support while Supercharging.
I DO have AP2, btw.
EDIT: On second thought, I know it had to be more than that, because the tech commented how big the package was... and it took forever.
Well, without knowing the exact wording what is it you saw it's a bit hard to comment on it.
It is possible mothership would opt to do a full download instead of a diff, but it is usually only when what you are running is different from what you are getting which does not appear to be the case with you.
Same version to same version is only ~13k, I don't know how far back you were behind on the update of course, but unless something drastically changed in 17.50 it still should not be all that big of a diff.
2017-12-15T10:43:06.257268-08:00 cid : cid-updater:23312: HTTP Client sid 95 using session->xfer_filename = /var/spool/cid-updater/handshake-response.part-89
...
2017-12-15T10:51:02.780041-08:00 cid : cid-updater: 9226: handshake command=patch http://...
...
2017-12-15T11:19:03.347204-08:00 cid QtCarServer[1671]: [SoftwareUpdateAvailableNotification] INFO Alert UPDATE_AVAILABLE triggered with value true - sending
Perhaps your are on to something. I had problems with my new X but went from .44 (Thu test drive) to .50_ (Sat pickup) where I had no AP. Then to a successful AP usable .50.1 (Sat night).Updated overnight from 2017.44 to 2017.50 2275226 without any issues. My MX 100D is only 1 month old, no clue whether that is of any influence to the upgrade process (other hardware?).
Well, I had 17.48->17.48 "upgrade" - download size: 13K (no ape firmware download because I already had it).
From the moment it was pushed to "your firmware update is ready to install" it took about 40 minutes.
Code:2017-12-15T10:43:06.257268-08:00 cid : cid-updater:23312: HTTP Client sid 95 using session->xfer_filename = /var/spool/cid-updater/handshake-response.part-89 ... 2017-12-15T10:51:02.780041-08:00 cid : cid-updater: 9226: handshake command=patch http://... ... 2017-12-15T11:19:03.347204-08:00 cid QtCarServer[1671]: [SoftwareUpdateAvailableNotification] INFO Alert UPDATE_AVAILABLE triggered with value true - sending
I wonder if there is a way I could get a copy of my logs just to see what took it so long?!? You ever heard of that happening??
Tesla has a process in place to fetch car logs from your car (don't even need to be local - they can do it OTA). Whenever you can convince them or a ranger to then give you a copy - I don't know.I wonder if there is a way I could get a copy of my logs just to see what took it so long?!? You ever heard of that happening??