This new firmware just got released.
Gonna post some pics of it later.
Still 8.1
Gonna post some pics of it later.
Still 8.1
-
Want to remove ads? Register an account and login to see fewer ads, and become a Supporting Member to remove almost all ads.
SeBsZ
Former Vendor
All firmwares since late 2017 have it. So it isn't a special developer build, they just use this branch name for whatever reason.
Nice car! Red is a great look on P and the plus suspension is fun.
The "whatever reason" most probably means using Gitflow workflow (or some derivative of it) for branch handling/naming: Gitflow Workflow | Atlassian Git Tutorial
SeBsZ
Former Vendor
Right. So they should be releasing master branch releases to us. Not ones from the dev branch, as that branch normally contains a high amount of bugs.
@SeBsZ The "tag" depends on whether they rebuild on merge (both approaches are used). They probably don't - just have a rule that all "other" changes from master (usually hotfixes) need to be merged down to develop before merging to master. That means the code can't change on merge up to release/master and you don't need to rebuild (and retest) again (the binary had been already tested in develop). The disadvantage is that the tag "develop" stays somewhere.
On the other side, we rebuild on every push/merge. The disadvantage of that approach is that if there are changes in master since last release (real merge of changes needs to happen), you release "untested" code (combination of the changes may mess up something). Or something in the build chain may have changed. Or...
Anyway, no one probably cares
On the other side, we rebuild on every push/merge. The disadvantage of that approach is that if there are changes in master since last release (real merge of changes needs to happen), you release "untested" code (combination of the changes may mess up something). Or something in the build chain may have changed. Or...
Anyway, no one probably cares
Wish they give us more info on what's new because that pin feature is not a 930 Mb patch, lol. Major parts of the code are redone.
Does size of the update actually have anything to do with the extent of what changes?
That's the full size, not a patch size. Acutally all firmwares between 2018.32.2 and 2018.36 are nearly the same size (< 1MB difference)
2018.28.5 is 2 megs less compared to 32.2, that's when they added PIN to Drive.
Since then all releases contain bugfixes only (and new bugs, probably
)The largest firmware release ever is 2018.18.2, being 2 megs heavier then the second largest 2018.36
These sizes are all for Tegra only (so without APE firmware and different for MCU2 or M3)
They are trying to keep the size low because the partition sizes they use on the Tegra MCUs is 1 gig for firmware. So I imagine they will have to solve this problem in the future when they can't fit into just 1 gig anymore (v9.0, maybe?). They could get like 1 gigabyte off the partition that stores user data and settings as that one is unreasonably large, but they would have to do it during the update.
If you ask me, resizing partitions over the air just sounds scary
Last edited:
arcus
Active Member
I have seen news reports that an update disabled autopilot. Has anyone experienced this?
SeBsZ
Former Vendor
Anything new? That's a new one 2018.36.1 904a9a4 , with 9 installations on Teslafi so far.
I also got my hands on .36.1
Model 3 release notes: This release contains minor improvements and bug fixes.
Model S/X release notes: PIN to Drive...
By the way, PIN to Drive doesn't seem to be available in the Middle East
mrbulk
Member
Twice in a row my uploads failed, first for 34 and now 36! First time it's ever happened...
Similar threads
