- 18 Mar, 2015 1 commit
-
-
Dan Stoza authored
Enables -Weverything and -Werror, with just a few exceptions for warnings we can't (or shouldn't need to) work around. Cherry pick of I034abec27bf4020d84af60d7acc1939c59986dd6 plus a couple of minor changes to CpuConsumer.cpp to make it work with a prior change: Uncomment CC_LOGV on line 46 Change C-style cast to static_cast on line 71 Change-Id: Iaec610477ea0122317b0578fb74caf2383d4cf08
-
- 15 Mar, 2015 1 commit
-
-
Jesse Hall authored
-
- 10 Mar, 2015 1 commit
-
-
Andreas Gampe authored
* commit '5a25a63d': Installd: Pass debuggable flag
-
- 09 Mar, 2015 5 commits
-
-
Andreas Gampe authored
-
Andreas Gampe authored
Pass the debuggable flag from the package manager to dex2oat. Change-Id: Id17ec72babe2ee88713a0d274eff86508de30666
-
Dan Stoza authored
-
Dan Stoza authored
Fixes a null pointer exception in getActiveConfig Bug: 19416124 Change-Id: I45a01f67affb63a348866ce42a6013c5eb71fe8f
-
- 05 Mar, 2015 3 commits
-
-
Nick Kralevich authored
* commit '5fec7915': service_manager: reorder permission checks for find
-
Nick Kralevich authored
-
Nick Kralevich authored
Reorder the find permission checks. This avoids generating misleading SELinux denials when a service doesn't exist, or when a service is prohibited to isolated apps. The original reason for structuring the code this way is explained in https://android-review.googlesource.com/#/c/100530/4/cmds/servicemanager/service_manager.c@172 The concern at the time was to avoid leaking a situation where a caller could probe for the existance of a service. This turns out to be unnecessary. The same return value is used for both a permission denied and a service not found. The only side effect is the generation of an SELinux audit log, which likely won't be accessible to the calling application. Change-Id: I9760e1821ed16102fa5f9bec07f8c34944565be9
-
- 26 Feb, 2015 7 commits
-
-
Christopher Ferris authored
* commit '9d68ed0e': Add timeout for dump_file.
-
Christopher Ferris authored
-
Mark Salyzyn authored
* commit 'bb67beca': dumpstate: add pstore read
-
Mark Salyzyn authored
-
Mark Salyzyn authored
Call logcat -L to pull any LAST Android logs. If the kernel is not configured for PSTORE and PSTORE_PMSG, the hopes are the empty content will pressure vendors to slice up and configure support. Change-Id: I5fddfa1e0f59f24fccc30b257ba68af8a8cf8640
-
Christopher Ferris authored
It turns out dump_file is used on a number of /proc and system files. In one case, the read of a file stalled and caused a bugreport to hang forever. It's still possible if there is a kernel bug that this could stall forever, but less likely. Also, change the return type of nanotime to uint64_t. Testing: - Created a named fifo and verified that dump_file fails with a timeout. - Created a large /data/anr/traces.txt to verify that large files still dump properly and that the additional NONBLOCK parameter doesn't cause a problem. - Created a dummy /data/tombstones/tombstone_00 to verify that the dump of these files still works. - Compared a dump using the old dumpstate to the new dumpstate to verify nothing obviously different. Bug: 19117030 Change-Id: I0d3dd27583c853cdaccd2fd278748cb5f9ccd4fb
-
Greg Hackmann authored
* commit '56f8c6c4': Error compiling waitforvsync.cpp
-
- 25 Feb, 2015 3 commits
-
-
Greg Hackmann authored
-
Dan Albert authored
* commit '79749845': Fix pointer-to-int and int-to-pointer warnings.
-
Dan Albert authored
-
- 23 Feb, 2015 4 commits
-
-
Dan Albert authored
Change-Id: If534cbcf2c3e644270572cbf829ba9b5acab29e6
-
Mark Salyzyn authored
* commit 'd80268ba': vsync.cpp test is throwing error whe compiled
-
Mark Salyzyn authored
-
Nanik Tolaram authored
frameworks/native/services/surfaceflinger/tests/vsync/vsync.cpp:55:44: error: 'ALOOPER_EVENT_INPUT' was not declared in this scope loop->addFd(myDisplayEvent.getFd(), 0, ALOOPER_EVENT_INPUT, receiver, ^ frameworks/native/services/surfaceflinger/tests/vsync/vsync.cpp:64:18: error: 'ALOOPER_POLL_WAKE' was not declared in this scope case ALOOPER_POLL_WAKE: ^ frameworks/native/services/surfaceflinger/tests/vsync/vsync.cpp:67:18: error: 'ALOOPER_POLL_CALLBACK' was not declared in this scope case ALOOPER_POLL_CALLBACK: ^ frameworks/native/services/surfaceflinger/tests/vsync/vsync.cpp:70:18: error: 'ALOOPER_POLL_TIMEOUT' was not declared in this scope case ALOOPER_POLL_TIMEOUT: ^ frameworks/native/services/surfaceflinger/tests/vsync/vsync.cpp:73:18: error: 'ALOOPER_POLL_ERROR' was not declared in this scope case ALOOPER_POLL_ERROR: ^ it is missing one header file Change-Id: Ie2fb02523a866b13a99edf837f072d101cacb466 Signed-off-by:
Nanik Tolaram <nanikjava@gmail.com>
-
- 20 Feb, 2015 3 commits
-
-
Elliott Hughes authored
* commit 'f3f22e55': Add missing <unistd.h> include for close.
-
Elliott Hughes authored
-
Elliott Hughes authored
Change-Id: Iebce6d74eecb8c275e800b7f47f74bbd4374860d
-
- 19 Feb, 2015 1 commit
-
-
Bill Yi authored
-
- 18 Feb, 2015 1 commit
-
-
Jesse Hall authored
-
- 17 Feb, 2015 1 commit
-
-
Elliott Hughes authored
-
- 16 Feb, 2015 1 commit
-
-
Elliott Hughes authored
Change-Id: I5c9bb4aa74d8a36d44e086bbcb5d60876727ce4c
-
- 13 Feb, 2015 1 commit
-
-
Nanik Tolaram authored
The waitforvsync.cpp throws error when compiling. Following is the error log target thumb C++: test-waitforvsync <= frameworks/native/services/surfaceflinger/tests/waitforvsync/waitforvsync.cpp frameworks/native/services/surfaceflinger/tests/waitforvsync/waitforvsync.cpp: In function 'int main(int, char**)': frameworks/native/services/surfaceflinger/tests/waitforvsync/waitforvsync.cpp:43:17: error: 'close' was not declared in this scope close(fd); ^ .... .... make: *** [out/target/product/grouper/obj/EXECUTABLES/test-waitforvsync_intermediates/waitforvsync.o] Error 1 the file is missing #include <unistd.h> Change-Id: I57728dbde65641cd3138625f9a590f9db8648158 Signed-off-by:
Nanik Tolaram <nanikjava@gmail.com>
-
- 12 Feb, 2015 1 commit
-
-
Alistair Strachan authored
Some time before kitkat, a workaround was put in place to keep tuna working with obsolete PowerVR GPU drivers. The tuna product was dropped in AOSP for kitkat, but the workaround remained. There are still a number of devices shipping with OMAP4 processors, and this workaround continues to be applied on those products even when it is not required. The effect is that virtual display CTS will fail on those devices.
-
- 11 Feb, 2015 4 commits
-
-
Nick Vaccaro authored
* commit 'b9bb1f13': Add support for SENSOR_TYPE_WRIST_TILT_GESTURE
-
Lajos Molnar authored
* commit '9b6be8e1': Revert "omx: add Intel's SemiPlanar OMX color format that is used on some devices"
-
Nick Vaccaro authored
-
Lajos Molnar authored
This reverts commit 61b17d64f90b85fd367ea1c7609cac69485957d4. Bug: 19317169 Change-Id: Ib1fcc26c46a52c848ffa8238ddbf6abfe57cfa5d
-
- 10 Feb, 2015 2 commits
-
-
Christopher Ferris authored
* commit '8511b3ae': Remove -z option.
-
Christopher Ferris authored
-