On Tuesday, April 17, 2012 10:57:11 AM UTC-4, Glenn Kasten wrote: > > One solution I've seen for this kind of problem is to have a separate > 'factory' filesystem > which is mounted read/write during factory provisioning, but then is > mounted read-only > during normal operation. This is also a good place to store > information such as camera calibration data. >
That sounds like a good idea at least for information that is specific to a given serial number. For branding though, I think most vendors are creating a unique build of Android for each version. That may be important if you need to share keys for system apps with a brand partner, have different upgrade schedules, etc. In general terms, things in the actual root filesystem are hardest to change since this tends to be a special archive which must be regenerated and concatenated onto the kernel image. In contrast, /data, /system, or any custom partitions can probably be changed by the run-time upgrade mechanism (at least by the original author who holds the keys needed to sign the update file). So it's probably better to keep often customized system parameters on /system or a custom partition as Glenn mentions. Several directories that are actually on /system get symlinked to the top level at runtime anyway. -- unsubscribe: [email protected] website: http://groups.google.com/group/android-porting
