pkodali
Member
Had a ranger come over today and he said that he didn't have the V9 update anymore, updated us to 36 instead
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.
Interestingly, they were able to get the brake fix out to everyone in one weekend so why can't we get a 500mb update to everyone.
not really.IIRC, there is no single universal image--there are SW builds specific to each hardware combination
not really.
There are 3 individual hw configs:
1. All MCU1 cars
2. All MCU2 cars
3. Model 3s
firmware image is 100% identical within those categories. So they really have 3 big hw combinations. Then there's the whole ap1 vs ap2 vs ap2.5 - those images are separate and are pulled in separately. Model 3 only has a specialized hw2.5 so it's a monolithic config anyway. Mcu1 and MCU2 cars share same ape2 and ape2.5 images based on what's installed in the car.
I understood well what you said. None of that maters though, every firmware for the categories outlined includes EVERYTHING possible hw-wise (except the ap2.0/ap2.5 firmware image), so if you have a hw2.x car on mcu1, your car includes AP1 firmwares and other stuff that your car cannot have but other MCU1-based car might have, you have every modelX bit even when your car is a model S and so on.When I said HW, I meant more than the compute HW, I meant the actual vehicle hardware--drive units, different revs of the BMS, etc.
You can get into any MCU1 car, get firmware dump and install it into any other MCU1 car even of a completely different config and it will work.
Yes, you can make it work. you will need to update the config in the replacement mcu to match the config of your actual car, of course (this includes vin). Root is pretty important here to first read the old config from old mcu and then to get it into another mcu, but I heard of a pretty interesting way to achieve it without root (that was part-closed in a recent firmware update).Not to go too far OT here, but this statement got me thinking. Does this mean I can take an MCU1 from a salvage model X and install it on my MCU1 model s and expect it to work? Because I have heard that it doesn’t actually function (due to hw-config and VIN mismatches...).
Hopefully there's some good info in here for those who didn't get the update yet...Please has any one with AP1 received V9 update? I know it may not have all the specials that come's with EAP model S,X and 3. After all the statement on Tesla site says All! Model S, X and 3 on the road will get some improvement with V9 ipdate, so has any one updated AP1 Tesla's to V9?
You can't. Get in line with the others already complaining about it.How do I change the position of the rear looking camera to the top half of the screen? By habit I always keep that view on to monitor what's going on behind me and in blind spots. Being stuck at the bottom half of the screen isn't ideal for me.
Oh
The thread is so long that I must have missed the complaints/feedbacks.
How about removing some screws then rotate the screen? Haha.You can't. Get in line with the others already complaining about it.