History log of /frameworks/base/core/java/com/android/server/BootReceiver.java
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
dcd3644f224da72ec95c590394ed656915bba481 13-May-2016 Tianjie Xu <xunchang@google.com> Report OTA time statistics

Read time and I/O for OTA update from last_install, and report the
statistics using MetricsLogger.histogram.

Bug: 28658632
Change-Id: I7fd06a82cbabd346d6d44f81ebad08f6baf4b8d0
/frameworks/base/core/java/com/android/server/BootReceiver.java
20be5d62471d520eed3a52d90c11944464a71c07 26-Feb-2016 Paul Lawrence <paullawrence@google.com> Add API to IMountService to get encryption state

Bug: 18002358
Change-Id: If7d9c9a5ed38ac37849fcf638ec10c76d2f419a1
/frameworks/base/core/java/com/android/server/BootReceiver.java
8b231a96a147d0b897a68cc9b1d0feaca515b000 13-Feb-2016 Tao Bao <tbao@google.com> BootReceiver: Stop using SharedPreferences.

BootReceiver was using SharedPreferences to record the timestamp that a
log file was lastly added to the dropbox. It no longer works after the
cleanup of the ContextImpl, because Context storage APIs are designed
for app data storage (as opposed to the system server). This CL switches
to writing its own xml file instead (/data/system/log-files.xml).

Bug: 26966507
Change-Id: Ife6b7544a7636b37dd239f059d1ca8c9c28f81a3
/frameworks/base/core/java/com/android/server/BootReceiver.java
b49dd577f421adbc4e2c7aa7aa88174905b76242 08-Apr-2015 Mark Salyzyn <salyzyn@google.com> BootReceiver: scrub APANIC

Bug: 19525200
Change-Id: I940e25a6dd20d53d44ad8848f490ac18c5e971e9
/frameworks/base/core/java/com/android/server/BootReceiver.java
e37030505ee3d461508611e1a291aff7b9e82a43 09-Dec-2014 Patrick Tjin <pattjin@google.com> Add recovery kmsg to dropbox

Bug: 18642766

Change-Id: I10e4532904a3a8cac43bec7630b9a7a90c2424ba
Signed-off-by: Patrick Tjin <pattjin@google.com>
/frameworks/base/core/java/com/android/server/BootReceiver.java
dea847c2ace8894a595cf9bd87764ce2ca9698ab 01-Oct-2014 Patrick Tjin <pattjin@google.com> Skip over directories when iterating tombstones

Bug: 17380601
Change-Id: Idb6e559a89c7438751bd7a52375b9789454e0334
/frameworks/base/core/java/com/android/server/BootReceiver.java
91317107a39a4f2a9347105b96aafcb98fe21fee 11-Sep-2014 Paul Lawrence <paullawrence@google.com> Create correct files in dropbox on encrypted boot

On the minimal framework start, don't mark ro.runtime.firstboot, allowing
the real framework to properly create the dropbox files in the real /data

Bug: 17450632
Change-Id: Ic53b3471b44e69f3eea7e3f3de18e789f51192bc
/frameworks/base/core/java/com/android/server/BootReceiver.java
29564cd24589867f653cd22cabbaac6493cfc530 07-Aug-2014 Narayan Kamath <narayan@google.com> Remove system_server classes from the boot image.

We set the system_server classpath in the environment
(like we do with BOOTCLASSPATH). After the zygote forks
the system_server, we dexopt the classpath (if needed)
and then launch the system server with the correct
PathClassLoader. This needed several small / medium
refactorings :

- The logic for connecting to installd is now in a separate
class and belongs in the system_server.
- SystemService / SystemServiceManager have now moved to
classes.jar. They are only used from there, and since they
use Class.forName, we want them to be loaded by the
system_server classloader, and not the bootclassloader.
- BootReceiver now moves to frameworks.jar, because it is
used by ActivityThread and friends.

bug: 16555230

Change-Id: Ic84f0b2baf611eeedff6d123cb7191bb0259e600
/frameworks/base/core/java/com/android/server/BootReceiver.java