eop:automotive:entertainment_or_info_systems
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| eop:automotive:entertainment_or_info_systems [2023/12/24 22:06] – [Doom (on custom Android)] io55admin | eop:automotive:entertainment_or_info_systems [2023/12/24 22:12] (current) – [Ubuntu chroot] io55admin | ||
|---|---|---|---|
| Line 89: | Line 89: | ||
| >The hack involves a whole lot of delicate steps | >The hack involves a whole lot of delicate steps | ||
| - | Some of these Pioneer units are able to accept custom ROMs with more proper functions of an Android | + | While the writers |
| https:// | https:// | ||
| Line 103: | Line 103: | ||
| >4GB of (DDR4 I think) RAM, and a 64GB eMMC for storage | >4GB of (DDR4 I think) RAM, and a 64GB eMMC for storage | ||
| - | While requiring some disabling of certain Intel safeguards relating to the vehicle, it is possible to run a fully featured Ubuntu instance on the little console within a Tesla Model 3, plus potentially the Model S and Xs. The Model 3’s Intel MCU is known to be a lot more locked down, so this being done is somewhat of an achievement compared to other Tesla systems. | + | While this hack does require the disabling of certain Intel safeguards relating to the vehicle, it is possible to run a fully featured Ubuntu instance on the little console within a Tesla Model 3. This could potentially |
| https:// | https:// | ||
eop/automotive/entertainment_or_info_systems.1703473619.txt.gz · Last modified: by io55admin
