| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
| |
Change-Id: I5e819911b32a57e018ecf7d1614120964e88031d
Signed-off-by: mydongistiny <jaysonedson@gmail.com>
|
| |
|
|
|
|
|
|
|
|
|
|
| |
We recently created a new GID that can be granted to critical system
processes, so that the system is usable enough for the user to free
up disk space used by abusive apps.
128MB ought to be enough for anybody.
Test: builds, boots
Bug: 62024591
Change-Id: I412ed9b0a885668ebe4c6c677a3bd0cd7f44080b
|
| |
|
|
|
|
|
|
|
| |
Explicit kernel panic since device is not reliable usable after this
hits.
Bug: 62257194
Test: check mount after boot
Change-Id: Ic9ffda18d819e92008f3666a4eff328c35e476ca
|
| |
|
|
|
|
|
|
|
|
|
|
| |
-Switch to LZ4 for better overall performance
-Set max_comp_streams to num of cores since upstream also moves this to
percpu.
-Set page-cluster to 0 as the incremental cost of reading 1 page at a
time is negligible for zram
Bug: 38249616
Test: boot and run zram-perf showing better performance
Change-Id: I924a2f6523735196cac15e6c7b5a1ed4cfd9e3c3
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit d037710937d1c15c2d5c70f06f752799e77eaf60.
The following CL on AOSP can fix the recovery failure.
So revert this revert.
https://android-review.googlesource.com/#/c/357170/
Bug: 35811655
Bug: 36502022
Change-Id: I2b56c5709885a0cce1db18801c9adc3db1c9ebe6
Test: normal boot sailfish, go to Settings > System & tap on
"Factory Data reset"
Test: recovery boot sailfish
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit 03f297713036576a60f7a3cbc96e3f7b8bc0f677.
recovery fails to find /misc while it tries to load from /fstab.sailfish.
Bug: 35811655
Bug: 36502022
Test: boot into recovery on sailfish. No "failed to find /misc partition"
message.
Change-Id: I6552411e601372ce3cfb11f6c9dff9fcf6ead384
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
fstab.${ro.hardware} contains SoC-specific settings and should be moved
to vendor partition. Note that this commit depends on the following
changes:
https://android-review.googlesource.com/#/q/topic:fstab_relocation
Bug: 35811655
Test: boot sailfish, checks fstab is moved to /vendor/etc/fstab.sailfish
Test: boot sailfish, checks that 'adb disable-verity' and
'adb enable-verity' can work by checking property:
- partition.system.verified
- partition.vendor.veerified
Test: boot marlin, do the same tests as above
Change-Id: I801502f96515f0fd74026c4cabf59ef680e49779
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
/vendor is mounted using fstab entry provided through the device tree
now.
Bug: 27805372
Bug: 35811655
Test: Boot sailfish, checks /vendor is early mounted
Test: Boot sailfish, checks that 'adb disable-verity' and
'adb enable-verity' can work
Change-Id: Icf0cb18e2f0ac3895f2b26f238510c052be2810e
Signed-off-by: Sandeep Patil <sspatil@google.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
In order to early mount partitions, verity params must contain the
real device nodes and also this makes it consistent with how we expect
fstab entries to be for mounting partitions (i.e. partition specific
'by-name' entries).
b/27805372
Test: Boot sailfish
Change-Id: I55b1f9649fd023ce7ed995dfca11efcb5dfe316b
Signed-off-by: Sandeep Patil <sspatil@google.com>
|
| |
|
|
|
|
|
|
| |
This reverts commit fc4391e357a622d243fee0122c6d7b194c0c3ad0.
Bug: 35324014
Test: Booted, checked that metadata absent in mount.
Change-Id: I323047e4ff75e830ea39a984fa6e4c3d612a924d
|
| |
|
|
|
|
|
|
|
| |
This will cause fs_mgr to use tune2fs to enable the quota feature on
these devices.
Test: builds, boots, quota enabled
Bug: 27948817
Change-Id: Ica947cc0e5a6395dd0266c34295098d21b1c68ec
|
| |
|
|
|
|
| |
Test: booted phone and ensured partition was present.
Bug: 28693324
Change-Id: Id84582b9de9d31f751d5a0cdb67d0312607da265
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
When atime tracking is enabled on a filesystem, simple read-only
operations result in touching the atime value, resulting in writes.
This is bad for both performance and flash lifetime.
Many historical Android devices have shipped with 'noatime' enabled,
so we're just bringing marlin/sailfish in alignment with them.
Test: booted, benchmarked before/after
Bug: 32144070
Change-Id: I333e67ed63d1804acb2a1bfaf981fa1224f0f079
|
| |
|
|
|
|
|
| |
Start bootanim before mounting data partition
Bug: 30118894
Change-Id: Id8390ad330fde00e5ebdf4ae39c3550f10a7bb9b
|
| |
|
|
|
|
|
|
| |
Remove discard for ro mounts
Delete unused revovery.fstab
Bug: 30807864
Change-Id: If212f5f7de181cab308c4206de523f1dc8b46907
|
| |
|
|
|
| |
Bug: 30807864
Change-Id: If212f5f7de181cab308c4206de523f1dc8b46907
|
| |
|
|
|
| |
Bug: 30678773
Change-Id: Ie3b82a812ab59a9aa66e4edf0b6cd8f218b4428c
|
| |
|
|
|
|
|
|
|
| |
Disable dm-verity for the vendor partition in AOSP builds. This
allows the device to boot even though verity metadata is signed
with a different key.
Bug: 30074027
Change-Id: I79f1de03367d1bc465891d88cd1568b603ad3994
|
| |
|
|
|
| |
Bug: 29335716
Change-Id: I743e1638aa59151a4ee1901dee40943b905d81d1
|
| |
|
|
|
|
|
| |
Flip kernel domain back into enforcing mode.
Bug: 29160970
Change-Id: Iebe2da5f9ba6bc8a528171e43067011a38236145
|
| |
|
|
|
|
|
| |
Bug: 28845874
This reverts commit f9a4bb811361abd852ca18e2b8d0934dd0dee3fe.
Change-Id: I02111f8539bf8183fffa9a86450a68d47d8e1a0c
|
| |
|
|
|
|
| |
Bug: 29108510
Change-Id: Ic137bca20bf4c2e391d67dd6bcb54c551388bad5
Signed-off-by: evan_wong <evan_wong@htc.com>
|
| |
|
|
|
| |
Bug: 28054350
Change-Id: I7fb89a77389043235f5352a0a54644acde263304
|
| |
|
|
|
|
|
|
|
| |
Bug: 29043680
Bug: 28845874
This reverts commit 166f762e5aaeb02efda1ed6cd5e061ed0b2c82ff.
Change-Id: Id65f820980f2085f0218e4a96e58c6872038468d
|
| |
|
|
|
|
|
|
|
|
| |
/dev/dm-0 is the rootdev irrespective of which slot
is booted. Also, remove slotselect as the rootdev
always remains the same.
Bug: 28845874
Change-Id: I1078d61683b7bb4d71657518d0e0b2cf0724fdf9
|
| |
|
|
|
|
|
|
| |
Add the path for mount OTG storage
Bug: 28731261
Change-Id: I630801e64ff8b0edb864fddeb2fe2ccac0a1f98a
|
| |
|
|
|
|
|
| |
Note that this sets encryption type to software.
Bug: 28616054
Change-Id: I62f87d7992c5dcf42d8c09d0e1c9b161d5e3ec8a
|
| |
|
|
|
|
|
|
| |
If the userdata partition is empty.
It also can boot successful and accelerate production.
Change-Id: I84e55684d4b936d5a69f97d7b0171db5e3ae890c
|
| |
|
|
|
|
|
|
| |
Disable FBE until I/O errors blocking app installs can be fixed.
This reverts commit c833990750ffd33de501773f2fd810df4a733e0c.
Bug: 28638491
|
| |
|
|
|
| |
Bug: 27745979
Change-Id: I442541ded125e491277e0d27ca7ea474e80d7bb2
|
| |
|
|
| |
Change-Id: I60c5762b002eeb63bf568cd331c51a3ed7744ba8
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The boot_control HAL is implemented by bootctrl.msm8996 which requires
the librecovery_updater_msm to be installed as well. This patch enables
and installs the bootctl module, the HAL and sets the permissions
required by the "boot_control_hal" attribute.
To isolate the permission to read/write A/B partition and manipulation
required by the HAL, this patch labels all the _a and _b partitions
present in the disk. The whole-disk block device is used by the HAL edit
the attributes in the GPT and is also labeled.
Bug: 27347498
Test: Manual test procedure, see description.
1. `make`
2. fastboot to the device the built partitions.
3. `make dist` and generated an OTA package from the target_files.zip.
4. Deployed the update to update_engine and works all the way to the
point it needs to mark the new slot as ready which fails due to bugs
on the HAL.
Change-Id: I39683fcb7247c7eab8ce49cba25d38bec54d6c60
|
| |
|
|
|
|
|
|
|
|
|
| |
Make symbolic link from
/dev/block/platform/soc/${ro.boot.bootdevice} to
/dev/block/bootdevice.
Rename all /dev/block/platform/soc/624000.ufshc to
/dev/block/bootdevice as well.
Change-Id: I7b7f4c728656103445e7fb68ccca92402fa36ff5
|
| |
|
|
|
|
|
|
| |
To be compatible, always mount system_a & system before formal
solution of A/B boot is ready.
Change-Id: Ie51ea137eb34e0caf1e7e4a3f2db5124ee13cd5d
Signed-off-by: Woody Lin <woody_lin@htc.com>
|
|
|
Change-Id: I07d39fc5087be3beeb3f12cfc8c0053ed9b0d6ec
Signed-off-by: Ed Tam <etam@google.com>
|