It does not matter. For me personally I flashed the 20240519 App .img file first just to see if the CAN file was really needed in order for functionality. So after flashing the .img file I saw the new swipe down buttons but was not able to use the right side set of buttons (ex: door function, fold/unfold mirror, passenger seat and battery preconditioning buttons). However the left side set of buttons (ex: bluetooth and AA/Carplay pulldown menu buttons) work since that replaced the previous set of buttons on the main screen. So after I flashed the CAN v2.8 file then sure enough the right side set of buttons door function, fold/unfold mirror and battery preconditioning buttons worked.
It is the faster red model 3 boot screen. I don't know what the old Hansshow boot screen was. Was it the old white tesla that was a lot longer which said "Go Electric" since I didn't get mine from Hansshow and the boot screen was way too long like maybe 7-10 seconds. Personally I prefer a fast boot screen so the red model 3 works fine for me. I always thought people absolutely detested the Hansshow logo boot up screen because it seemed so douchey splattering their logo on there. Does you have video of the Hansshow boot up screen so I know what that looks like?
I have been using the display for about 2 weeks now and yes I agree with you that the front camera not going away until 20 mph is ridiculous. Honestly it either shouldn't pop up when switching to "D" at all or it should just be capped off at 5 mph max and then turn off. But I prefer not having it there because having all the unnecessary transitions between camera and stock UI/AA/Carplay is just not necessary.
Glad you agree with me because I just couldn't believe it when they programmed it this way.
I agree the manual front camera activation duration can be reduced slightly so it doesn't conflict with a single press function of the right scroll wheel. Personally I don't think a "parking mode" can be implemented with the read only data capabilities from the CAN bus. I also agree that the cleanest way to deal with the issue is just remove the functionality completely. Just thinking of it from a code perspective, all they have to do is just remove the lines of code where it tells the display to not activate the front camera when set to "D". I don't think it really should be an option in general so that they don't have to muck with the "Front camera" toggle to add an if/else case. I can't think of most people that would want that feature anyways.
Yeah I agree I'm not sure if it's possible for it read through CAN bus if tesla is in parking mode. But I know it's not just based on speed for the tesla since it reads for parking spaces for it's own tesla vision to activate. Or was this only a FSD feature...not sure.
@Huy La Ba
i had try ota can, it auto updated, and can is back to the 2.6....
The icons don't work with CAN v2.6. Why did you revert back? I posted the link many times already here.
The yellow symbol is the tire pressure symbol. When you first enter your vehicle and in Park status for some reason the tire pressure measurement is inaccurate and assumes the tire pressure is always at 92 PSI which is why the yellow tire pressure symbol warning shows up since that it is way above the limits of the tire.
@flai54
The CAN update is agnostic of Android version or Linux version. All the CAN does is update how the signals between the car and the display work so that shouldn't differ between Android and Linux versions. The App update (IVT244.img) file is what is different between the Linux and Android versions and from my understanding the only difference between the Android and Linux version is that the Android version has the Tbox icon and the Linux version does not.
i had updated the can_app.bin from this link.
teslamotorsclub.com
