Hi,
When building FxOS, how/where's the logic that dispatches the resulting files
into the various boot.img, recovery.img, system.img, ... files. Can it be
overridden?
I'm asking this because I'm currently trying to "port" FxOS for my Alcatel
OneTouch 6015X "Fire E" phone. Within the OEM ROM, FxOS files that normally
reside in system partition are splitted between system and custpack partitions,
with symlinks from system to custpack partition when files are physically
stored in custpack (e.g. system/webapps -> custpack/webapps). I would like to
customize the default content of system.img produced by local build to mimic
this behaviour.
Maybe people behind Hamachi device can help? Indeed, it's also an Alcatel
OneTouch phone, so the partition scheme may also involve custpack partition.
Or maybe people behind Flame device also have an idea: Flame and Fire E are
very close, with T2M (who designed Flame) and TCT (who designed Fire E) both
being hold by TCL. So I wasn't that surprised to find in gpt_main0.bin of
Flame's v18D image the exact same partition layout (including custpack
partition) than in my Fire E:
modem
sbl1
sdi
DDR
aboot
rpm
boot
tz
pad
modemst1
modemst2
system
persist
cache
recovery
misc
fsg
fsc
ssd
splash
traceability
tuningpara
secro
fota
abootbk
rpmbk
tzbk
custpack
userdata
usbmsc
Out of curiosity, this reminds me bug 1085230 - [Flame] OTA needs enough
/system space to update [2]. Since Flame also has custpack partition, I was
wondering if using it (and making symlinks from system to custpack like in Fire
E) would have been a viable alternative to increasing the size of system
partition?
Thanks,
Émeric
[1] https://bugzilla.mozilla.org/show_bug.cgi?id=1085230
_______________________________________________
dev-fxos mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-fxos
