+++ This bug was initially created as a clone of Bug #1085230 +++ +++ This bug was initially created as a clone of Bug #1073399 +++ > Since OTA will uncompress update package in /system partition, it should need enough space to let update successfully. > > From vendor base image, it only has 102.9MB from their released user build. > We should have a better solution to avoid OTA fail again in the future. > > Attachment shows different timing free space in /system. The potential problem is if update to v2.2, free space in /system only left over 760.0K while uncompressing update package. We have been hitting this too much. There are ways to increase the size of the partition, as documented on bug 1085230 comment 12 and bug 1085230 comment 13. But there are risks, it's not trivial to patch, and it needs manual flashing. In the mean time of providing an update from vendor, we should at least improve the error detection path and make sure we get proper feedback to the user.

FW the needinfo to TAM.

> (In reply to Alexandre LISSY :gerard-majax from comment #0) > In the mean time of providing an update from vendor, we should at least > improve the error detection path and make sure we get proper feedback to the > user. Hi Alex: Would you help me understand more about the "error detection path" that you suggested to improve? Is that a request to T2M as they provide FOTA update of based image?

(In reply to Wesly Huang from comment #2) > > (In reply to Alexandre LISSY :gerard-majax from comment #0) > > In the mean time of providing an update from vendor, we should at least > > improve the error detection path and make sure we get proper feedback to the > > user. > > Hi Alex: > > Would you help me understand more about the "error detection path" that you > suggested to improve? Is that a request to T2M as they provide FOTA update > of based image? It's unrelated to FOTA, but to OTA that fails to apply because of out of space.