A word about android, dynamic and stuff - Revision history

Luka177 at 21:02, 23 September 2023

2023-09-23T21:02:43Z

← Older revision		Revision as of 23:02, 23 September 2023
Line 20:		Line 20:
	The ABM team decided to create a separate super partition for each android based os installed, a big suprise they are named: super1, super2, ..., superX		The ABM team decided to create a separate super partition for each android based os installed, a big suprise they are named: super1, super2, ..., superX

	As partitions are located on sd card and android wants to mount them from /dev/block/by-name, we should somehow get them there with minimum to no binary patching. Apparently its easy as adding path to sd device, like ```soc/8804000.sdhci``` to ```androidboot.boot_device``` but you should leave old one as first and separate wit {{,}}		As partitions are located on sd card and android wants to mount them from /dev/block/by-name, we should somehow get them there with minimum to no binary patching. Apparently its easy as adding path to sd device, like ```soc/8804000.sdhci``` to ```androidboot.boot_device``` but you should leave old one as first and separate wit ,

Luka177 at 21:01, 23 September 2023

2023-09-23T21:01:47Z

← Older revision		Revision as of 23:01, 23 September 2023
Line 20:		Line 20:
	The ABM team decided to create a separate super partition for each android based os installed, a big suprise they are named: super1, super2, ..., superX		The ABM team decided to create a separate super partition for each android based os installed, a big suprise they are named: super1, super2, ..., superX

	As partitions are located on sd card and android wants to mount them from /dev/block/by-name, we should somehow get them there with minimum to no binary patching. Apparently its easy as adding path to sd device, like ```soc/8804000.sdhci``` to ```androidboot.boot_device``` but you should leave old one as first and separate wit ~~```~~,~~```~~		As partitions are located on sd card and android wants to mount them from /dev/block/by-name, we should somehow get them there with minimum to no binary patching. Apparently its easy as adding path to sd device, like ```soc/8804000.sdhci``` to ```androidboot.boot_device``` but you should leave old one as first and separate wit {{,}}

Luka177 at 21:00, 23 September 2023

2023-09-23T21:00:02Z

← Older revision		Revision as of 23:00, 23 September 2023
Line 20:		Line 20:
	The ABM team decided to create a separate super partition for each android based os installed, a big suprise they are named: super1, super2, ..., superX		The ABM team decided to create a separate super partition for each android based os installed, a big suprise they are named: super1, super2, ..., superX

	As partitions are located on sd card and android wants to mount them from /dev/block/by-name, we should somehow get them there with minimum to no binary patching. Apparently its easy as adding path to sd device, like soc/8804000.sdhci to androidboot.boot_device but you should leave old one as first and separate wit ,		As partitions are located on sd card and android wants to mount them from /dev/block/by-name, we should somehow get them there with minimum to no binary patching. Apparently its easy as adding path to sd device, like ```soc/8804000.sdhci``` to ```androidboot.boot_device``` but you should leave old one as first and separate wit ```,```

Luka177: Created page with "This page contains a bit of info about android dualboot handling for platform and app developers. Usually not too relevant for porters. All info here is up to date as of September 2023. Take all info found here with grain of salt. == Handling super == Obviously a first question when it comes to dualbooting on modern android phones, is what to do with so called super partition, that in fact should contain such parturition as: * system * vendor Likely to contain: * pr..."

2023-09-23T20:59:29Z

Created page with "This page contains a bit of info about android dualboot handling for platform and app developers. Usually not too relevant for porters. All info here is up to date as of September 2023. Take all info found here with grain of salt. == Handling super == Obviously a first question when it comes to dualbooting on modern android phones, is what to do with so called super partition, that in fact should contain such parturition as: * system * vendor Likely to contain: * pr..."

New page

This page contains a bit of info about android dualboot handling for platform and app developers. Usually not too relevant for porters. All info here is up to date as of September 2023. Take all info found here with grain of salt.

== Handling super ==
Obviously a first question when it comes to dualbooting on modern android phones, is what to do with so called super partition, that in fact should contain such parturition as:

* system
* vendor

Likely to contain:

* product
* system_ext

Can contain:

* odm

Those partition might or might not be in 2 sets A and B. Right some devices are very modern but still A only.

The ABM team decided to create a separate super partition for each android based os installed, a big suprise they are named: super1, super2, ..., superX

As partitions are located on sd card and android wants to mount them from /dev/block/by-name, we should somehow get them there with minimum to no binary patching. Apparently its easy as adding path to sd device, like soc/8804000.sdhci to androidboot.boot_device but you should leave old one as first and separate wit ,