Commit Graph
7512 Commits
Author SHA1 Message Date
Ethan Yonker 9eb1cd4752 Fix USB Mass Storage on some devices
On some devices we need to set the sys.storage.ums_enabled
property before we write to the lun file. Also sleep for a bit
after setting the propery before writing to the lun file.

Change-Id: I77ac853fde14ffc3adf20571c132f91ed85196df
2014-11-04 15:40:05 +01:00
bigbiff c40c1c52d6 This patchset causes issues with backups.
Revert "update exfat from current head"

This reverts commit 2e33c5ee0b.

Change-Id: I00d19d98f721bb50aa937ca15b11fe3491132fcd
2014-11-04 15:37:42 +01:00
that 39b7c16d28 add "done" after "Updating partition details..."
This addresses a usability problem. Some users are confused when they
switch to the console and see this message, thinking they have to wait.

Examples:
http://forum.xda-developers.com/showthread.php?t=2498492
http://androidforums.com/verizon-galaxy-s3-all-things-root/718376-twrp-recovery-update-question.html

Change-Id: Ib44773998c2ef1b8b821f3b8876218e11a7de357
2014-11-04 15:35:16 +01:00
that 7c0deaafd6 gitignore: ignore tags file
Change-Id: I78f7e51bdb0f7fd8800de4dd2d2880f0161d7b6a
2014-11-04 15:34:19 +01:00
that d43bf2dc77 fix some compiler warnings
Change-Id: I23c490e6228b0fcf656c76ac314c69508ba2329d
2014-11-04 15:33:04 +01:00
that 78d0c5fc25 partitionmanager: remove unused By_Block and By_Name methods
Change-Id: Ia6eefd23f6671428221e35642f01534bc9fff6ad
2014-11-04 15:29:06 +01:00
The Android Automerger ac1e11ff83 merge in lmp-mr1-release history after reset to 2020564f21 2014-11-04 06:09:44 -08:00
Matt Mower 031163b2c6 Remove dependence on build hax in makefiles
Update makefiles to no longer rely on INTERNAL_RECOVERY_FILES. Define
LOCAL_ADDITIONAL_DEPENDENCIES instead.

Set LOCAL_LDFLAGS to properly link recovery executable.

Change-Id: I4542104c69399b5a19674b9772ab89c3709efa72
2014-11-03 13:36:03 -06:00
The Android Automerger 2dc16b1937 merge in lmp-mr1-release history after reset to 2020564f21 2014-11-03 06:09:03 -08:00
The Android Automerger 43aa6a1a1c merge in lmp-mr1-release history after reset to 2020564f21 2014-11-02 06:08:56 -08:00
The Android Automerger fc357be4f3 merge in lmp-mr1-release history after reset to 2020564f21 2014-11-01 06:09:04 -07:00
Michael Runge 9537d92ff5 am 8bebe58e: am 2020564f: am be81e51c: Use more aggressive sync writing to applypatch.
* commit '8bebe58e540b34078aecd155e7b58a7a02985483':
  Use more aggressive sync writing to applypatch.
2014-10-31 00:26:30 +00:00
Michael Runge 60a473d298 am c2e7d903: am e908a454: am 042c3cd0: Force sync files written by minzip.
* commit 'c2e7d903adca4195588be085011c2a6a9c80426a':
  Force sync files written by minzip.
2014-10-31 00:26:30 +00:00
Michael Runge 8bebe58e54 am 2020564f: am be81e51c: Use more aggressive sync writing to applypatch.
* commit '2020564f21bb0216965f0f5c43c5c1c995785bab':
  Use more aggressive sync writing to applypatch.
2014-10-31 00:13:22 +00:00
Michael Runge c2e7d903ad am e908a454: am 042c3cd0: Force sync files written by minzip.
* commit 'e908a45420fc4194c6007193d21d5b690e04583f':
  Force sync files written by minzip.
2014-10-31 00:13:21 +00:00
The Android Automerger f54d64fc8e merge in lmp-mr1-release history after reset to 2020564f21 2014-10-30 06:08:59 -07:00
Michael Runge cddb68b5ea Use more aggressive sync writing to applypatch.
We have seen cases where the boot partition is patched, but upon
recovery the partition appears to be corrupted.  Open up all
patched files/partitions with O_SYNC, and do not ignore the
errors from fsync/close operations.

Bug: 18170529
Change-Id: I392ad0a321d937c4ad02eaeea9170be384a4744b
2014-10-29 13:29:40 -07:00
Michael Runge a6c142f2a5 Force sync files written by minzip.
Some files appear to be missing their sync to disk.

Bug: 18145574
Change-Id: Ic858624a4dd65bbfc54d30f3a13c607078270345
2014-10-29 13:29:40 -07:00
Michael Runge 2020564f21 am be81e51c: Use more aggressive sync writing to applypatch.
* commit 'be81e51c171a0cf9b9b5045ee949282b7f36d779':
  Use more aggressive sync writing to applypatch.
2014-10-29 20:23:58 +00:00
Michael Runge be81e51c17 Use more aggressive sync writing to applypatch.
We have seen cases where the boot partition is patched, but upon
recovery the partition appears to be corrupted.  Open up all
patched files/partitions with O_SYNC, and do not ignore the
errors from fsync/close operations.

Bug: 18170529
Change-Id: I392ad0a321d937c4ad02eaeea9170be384a4744b
2014-10-29 13:00:21 -07:00
Michael Runge e908a45420 am 042c3cd0: Force sync files written by minzip.
* commit '042c3cd04ec3ef416019fa382cd5b1a942bd79e1':
  Force sync files written by minzip.
2014-10-29 18:51:51 +00:00
The Android Automerger b0ac0814b9 merge in lmp-mr1-release history after reset to fe8563f4f2 2014-10-29 06:08:52 -07:00
Michael Runge 042c3cd04e Force sync files written by minzip.
Some files appear to be missing their sync to disk.

Bug: 18145574
Change-Id: Ic858624a4dd65bbfc54d30f3a13c607078270345
2014-10-28 19:49:57 -07:00
The Android Automerger fa0ceba80c merge in lmp-mr1-release history after reset to fe8563f4f2 2014-10-28 06:10:10 -07:00
Badhri Jagan Sridharan b5b43043fa adbd: Support for new f_fs descriptor format
The patch "[RFC] usb: gadget: f_fs: Add flags
to  descriptors block" marks the current
usb_functionfs_descs_head format deprecated
and introduces support for sending SuperSpeed
descriptors.

This CL makes adbd to send Descriptors in the
new format. Adbd would fall back to the old
format, if kernel is not able to recognize
the new format. This is done to prevent
adbd from breaking in the older versions
of the kernel.

Bug: 17394972
Change-Id: I1acf684ef8a4dcc612ac20b5abe1e27b43901031
Signed-off-by: Badhri Jagan Sridharan <badhri@google.com>
2014-10-28 02:00:32 +00:00
The Android Automerger 835499a41d merge in lmp-mr1-release history after reset to fe8563f4f2 2014-10-27 06:08:45 -07:00
The Android Automerger 28754d4f42 merge in lmp-mr1-release history after reset to fe8563f4f2 2014-10-26 06:08:42 -07:00
The Android Automerger 512eddf4ae merge in lmp-mr1-release history after reset to fe8563f4f2 2014-10-25 06:09:00 -07:00
Michael Runge f997340fe8 am 8a9ee089: am fe8563f4: am 5ddf4293: Log mount/unmount errors to UI
* commit '8a9ee089d380bcbd2f4447770b944a552001fd28':
  Log mount/unmount errors to UI
2014-10-25 02:37:16 +00:00
Michael Runge 8a9ee089d3 am fe8563f4: am 5ddf4293: Log mount/unmount errors to UI
* commit 'fe8563f4f2a6efe1eb00bb41a5037c88917becfc':
  Log mount/unmount errors to UI
2014-10-24 23:39:40 +00:00
Michael Runge fe8563f4f2 am 5ddf4293: Log mount/unmount errors to UI
* commit '5ddf4293df45a051c7900eeb62fb5ec4950b6cb6':
  Log mount/unmount errors to UI
2014-10-24 23:17:43 +00:00
Michael Runge f15e31edf9 Log mount/unmount errors to UI
Bug: 18092022
Change-Id: I6c42038ebeb1cfc1e7ca0d3e12310fdce1b990b0
2014-10-24 16:05:13 -07:00
Nick Kralevich 6a821fe5f0 unconditionally apply SELinux labels to symlinks
At the end of the OTA script, we walk through /system, updating
all the permissions on the filesystem, including the UID, GID,
standard UNIX permissions, capabilities, and SELinux labels.

In the case of a symbolic link, however, we want to skip most of
those operations. The UID, GID, UNIX permissions, and capabilities
don't meaningfully apply to symbolic links.

However, that's not true with SELinux labels. The SELinux label on
a symbolic link is important. We need to make sure the label on the
symbolic link is always updated, even if none of the other attributes
are updated.

This change unconditionally updates the SELinux label on the symbolic
link itself. lsetfilecon() is used, so that the link itself is updated,
not what it's pointing to.

In addition, drop the ENOTSUP special case. SELinux has been a
requirement since Android 4.4. Running without filesystem extended
attributes is no longer supported, and we shouldn't even try to handle
non-SELinux updates anymore. (Note: this could be problematic if
these scripts are ever used to produce OTA images for 4.2 devices)

Bug: 18079773
Change-Id: I87f99a1c88fe02bb2914f1884cac23ce1b385f91
2014-10-24 16:05:13 -07:00
Michael Runge 5ddf4293df Log mount/unmount errors to UI
Bug: 18092022
Change-Id: I6c42038ebeb1cfc1e7ca0d3e12310fdce1b990b0
2014-10-24 14:14:41 -07:00
Nick Kralevich cb83d7a420 am 944fc5e6: am 915d661c: am 68802416: unconditionally apply SELinux labels to symlinks
* commit '944fc5e616b6f70da3447fc6987fb2f92dfdc01f':
  unconditionally apply SELinux labels to symlinks
2014-10-24 17:57:23 +00:00
Nick Kralevich 944fc5e616 am 915d661c: am 68802416: unconditionally apply SELinux labels to symlinks
* commit '915d661ccc64f25a533919054f487a8e5943574d':
  unconditionally apply SELinux labels to symlinks
2014-10-24 17:52:40 +00:00
Nick Kralevich 915d661ccc am 68802416: unconditionally apply SELinux labels to symlinks
* commit '688024169df70336cc128ea8cc929174c53a501e':
  unconditionally apply SELinux labels to symlinks
2014-10-24 17:43:15 +00:00
Nick Kralevich 688024169d unconditionally apply SELinux labels to symlinks
At the end of the OTA script, we walk through /system, updating
all the permissions on the filesystem, including the UID, GID,
standard UNIX permissions, capabilities, and SELinux labels.

In the case of a symbolic link, however, we want to skip most of
those operations. The UID, GID, UNIX permissions, and capabilities
don't meaningfully apply to symbolic links.

However, that's not true with SELinux labels. The SELinux label on
a symbolic link is important. We need to make sure the label on the
symbolic link is always updated, even if none of the other attributes
are updated.

This change unconditionally updates the SELinux label on the symbolic
link itself. lsetfilecon() is used, so that the link itself is updated,
not what it's pointing to.

In addition, drop the ENOTSUP special case. SELinux has been a
requirement since Android 4.4. Running without filesystem extended
attributes is no longer supported, and we shouldn't even try to handle
non-SELinux updates anymore. (Note: this could be problematic if
these scripts are ever used to produce OTA images for 4.2 devices)

Bug: 18079773
Change-Id: I87f99a1c88fe02bb2914f1884cac23ce1b385f91
2014-10-23 20:46:33 -07:00
Michael Runge bd6138cffe Allow passing of mount args to mountFn
Bug: 18079773
Bug: 18092222

Change-Id: Ifc3f3e123de729dfbb2f49414b3207afa96268d5
2014-10-23 17:35:13 -07:00
Michael Runge 7548025bdd Log to UI any metadata setting errors
Bug: 18079773
Change-Id: Ic6fddbcbcb6ddb9e1cbd1698df98387c0033ae15
2014-10-23 17:35:13 -07:00
Nick Kralevich b8344b6f59 Make /cache/recovery/last_log available in recovery
Create a new recovery UI option to allow the user to view
/cache/recovery/last_log for their device. This gives enhanced
debugging information which may be necessary when a failed
OTA occurs.

Bug: 18094012
Change-Id: Ic3228de96e9bfc2a0141c7aab4ce392a38140cf3
2014-10-23 17:35:13 -07:00
Michael Runge 257a0e9ef8 am 45322f93: am da500cec: am 168f7778: Allow passing of mount args to mountFn
* commit '45322f939a5bf66d378aab57e1fee1aa29ff9469':
  Allow passing of mount args to mountFn
2014-10-23 22:23:02 +00:00
Brian Carlstrom 661478eef6 am d1e909e7: am 4da9cdea: am 473967d8: Merge "Log to UI any metadata setting errors" into lmp-dev
* commit 'd1e909e77d6c20aa88630a86d7a93de54d5cf2af':
  Log to UI any metadata setting errors
2014-10-23 22:22:59 +00:00
Michael Runge 45322f939a am da500cec: am 168f7778: Allow passing of mount args to mountFn
* commit 'da500cecf5b004498c0dd17bc27a30eb4b0b9a2d':
  Allow passing of mount args to mountFn
2014-10-23 22:15:29 +00:00
Brian Carlstrom d1e909e77d am 4da9cdea: am 473967d8: Merge "Log to UI any metadata setting errors" into lmp-dev
* commit '4da9cdeab97297e69075dd9b6cad9921cfae30b9':
  Log to UI any metadata setting errors
2014-10-23 22:15:28 +00:00
Michael Runge da500cecf5 am 168f7778: Allow passing of mount args to mountFn
* commit '168f77787700f0e9f66675beef33c593a777e64e':
  Allow passing of mount args to mountFn
2014-10-23 21:56:52 +00:00
Brian Carlstrom 4da9cdeab9 am 473967d8: Merge "Log to UI any metadata setting errors" into lmp-dev
* commit '473967d87ff9fc7a541c16ebdc56364c285d2862':
  Log to UI any metadata setting errors
2014-10-23 21:56:52 +00:00
Nick Kralevich efcdf752b1 am 3e62e9d9: am d0602fbb: am 9b2db80d: Merge "Make /cache/recovery/last_log available in recovery" into lmp-dev
* commit '3e62e9d93e97e39c260b62ac230002ae21ed4d96':
  Make /cache/recovery/last_log available in recovery
2014-10-23 20:44:56 +00:00
Michael Runge e2aa0b8ad6 am c224ac28: am 3b5c6dca: am 2f0ef730: Treat already-renamed files as having no problems.
* commit 'c224ac28adf1248dcd5716a0c6ed77825418fe0d':
  Treat already-renamed files as having no problems.
2014-10-23 20:44:55 +00:00
Nick Kralevich 3e62e9d93e am d0602fbb: am 9b2db80d: Merge "Make /cache/recovery/last_log available in recovery" into lmp-dev
* commit 'd0602fbb88c095520d0fc88e821eb5557298e32b':
  Make /cache/recovery/last_log available in recovery
2014-10-23 20:41:00 +00:00