Right now autoport is limited to only using a pre-existing pre-expanded image from the Android Dumps project.
This has its limitations. First is that we are tied to the devices for which ROMs have been dumped, which is also limited to OEM releases. Second is that it relies on their service being stable, and working. This is not a given.
By parsing images ourselves, we can produce skeletons for devices which have not been made available to the Android Dumps project.
We also can parse non-OEM images.
Since we can parse images from multiple sources, we should require the use of a --rom-type argument where the user gives the origin, e.g. oem, lineageos.
Right now
autoportis limited to only using a pre-existing pre-expanded image from the Android Dumps project.This has its limitations. First is that we are tied to the devices for which ROMs have been dumped, which is also limited to OEM releases. Second is that it relies on their service being stable, and working. This is not a given.
By parsing images ourselves, we can produce skeletons for devices which have not been made available to the Android Dumps project.
We also can parse non-OEM images.
Since we can parse images from multiple sources, we should require the use of a
--rom-typeargument where the user gives the origin, e.g.oem, lineageos.