summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorShareef Ali <shareefalis@cyanogenmod.org>2013-05-28 22:44:31 -0500
committerGerrit Code Review <gerrit@cyanogenmod.org>2013-07-03 12:50:00 -0700
commitd0884b9808c44d6ea8c72c9e8f9e75e01eb303df (patch)
treeafae4554c47c6ee3523c9480838caac2d5cd6064
parent73b34f60bc9ad058bbeddef79142bb32280786c3 (diff)
downloadbuild-d0884b9808c44d6ea8c72c9e8f9e75e01eb303df.zip
build-d0884b9808c44d6ea8c72c9e8f9e75e01eb303df.tar.gz
build-d0884b9808c44d6ea8c72c9e8f9e75e01eb303df.tar.bz2
build: get rid of the sparse expand stuff
* i don't see a reason why we are doing this because we never deal with flashing system img rawly * This will put useless write on ssd.. * we don't have space on ssd Change-Id: Icd53d161b8515f5eca238b98ad68515d69caa34f
-rwxr-xr-xtools/releasetools/build_image.py2
1 files changed, 1 insertions, 1 deletions
diff --git a/tools/releasetools/build_image.py b/tools/releasetools/build_image.py
index 94a9fda..358d718 100755
--- a/tools/releasetools/build_image.py
+++ b/tools/releasetools/build_image.py
@@ -56,7 +56,7 @@ def BuildImage(in_dir, prop_dict, out_file):
build_command = ["mkuserimg.sh"]
if "extfs_sparse_flag" in prop_dict:
build_command.append(prop_dict["extfs_sparse_flag"])
- run_fsck = True
+ #run_fsck = True
build_command.extend([in_dir, out_file, fs_type,
prop_dict["mount_point"]])
if "partition_size" in prop_dict: