summaryrefslogtreecommitdiff
path: root/packages/Shell/src
Commit message (Collapse)AuthorAgeFilesLines
...
* | | Merge "Add a null home activity to Shell.apk" am: fd2ba540df am: 24f93a2b48 ↵Automerger Merge Worker2020-02-071-0/+43
|\ \ \ | |/ / |/| / | |/ | | | | am: 26f49e7b75 Change-Id: I77be28465d8fe8439877859e3e630103efe69c4f
| * Add a null home activity to Shell.apkIsaac Chen2020-02-071-0/+43
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In configurations where AOSP Settings.apk is not included, there might not be any home activity. E.g. CSI doesn't have Settings.apk. This CL adds a null home activity to Shell.apk, which is in CSI, so the framework can be in a sane state. Without such null home activity in CSI, package manager fails to install any APKs. Bug: 148044842 Test: $ lunch csi_arm64-userdebug; m -j # Flash CSI to a Pixel (with AVB disabled) and reboot $ m DeviceHealthChecks $ adb install $OUT/testcases/DeviceHealthTests/arm64/DeviceHealthTests.apk Performing Streamed Install Success Change-Id: I87999e30298bbe42af64f28e88fc6dc5975f1ca3
* | Remove legacy-flow no-op variables: max, realMax and realProgressAbhijeet Kaur2020-01-261-52/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Legacy onProgress aidl listener callback function used to take 2 params: progress and max. So, the client had to calculate the percentage progress. This legacy onProgress method is removed. Now dumpstate sends the actual progress in percentage without requiring the client to calculate it. Bug: 123617758 Test: Takes interactive bugreport as expected. And shows progress notification as expected. Change-Id: Ic5a355cc886e51b964f73c227f5f657173e99420
* | Merge "Move heap dump sharing to SHELL." am: c29b5cba29 am: 2cdf2d5ad7Kweku Adams2019-10-304-1/+432
|\| | | | | | | | | | | am: 215d92f880 Change-Id: Ic092f2d5c0c0a1497c19e73417c68b8e8616cc63
| * Move heap dump sharing to SHELL.Kweku Adams2019-10-294-1/+432
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The system shouldn't be granting read URI permissions as itself. This means that heap dumps aren't successfully shared. Moving the heap dump sharing mechanism to SHELL, which already has the permission to dump heaps so that dumps can be shared properly. The ActivityManagerService changes are submitted separately. Bug: 126885951 Bug: 135150619 Test: collect a heap dump and confirm it's successfully shared with an app Test: do manual test on a secondary user & confirm it's not available to other user Change-Id: I6fad69280b5124c8ec2d3b4bef0f7dddb6a9422c
* | Remove unused broadcasts/functions/variables from ShellAbhijeet Kaur2019-10-223-585/+73
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Bugreport is now triggered using API and not via broadcasts from dumpstate. As migration to API flow is stable, we can remove methods and broadcasts that were used in non-API bugreport flow. Now, callbacks are used for communication between dumpsate and Shell instead of broadcasts. * Remove BugreportReceiver.java as it used to handle BUGREPORT_STARTED and BUGREPORT_FINISHED intents which are not required by Shell anymore to track bugreports. * Remove RemoteBugreportReceiver.java as it used to handle REMOTE_BUGREPORT_FINISHED intent which is not required by Shell anymore. * Remove methods that were being used when processing these broadcasts. * Remove pid as that is not used anymore. * Since Shell owns the file now, don't need mTempName, mSavedName, onFocusListener and disable file name after the bugreport is finished. File name can be sanitized and updated even after bugreport finished. Bug: 136066578 Test: Build and flash. Interactive/Full bugreports from Settings/Power button. Test: Rename workflow for interactive bugreports works as expected. Test: * Build and flash * Install TestDPC * Make it device owner * Take a remote bugreport. Works as expected Change-Id: I5e0f829631cb63074c41c914236e78abe95ba162
* | Read screenshot file from screenshotFiles arrayAbhijeet Kaur2019-10-101-4/+4
| | | | | | | | | | | | | | | | | | | | | | Regression from merge issue that was created when merging ag/9489200 and ag/9502526. Previously, before saving the screenshot file in the array, it had to be created each time it was required. Bug: 123617758 Test: manual Change-Id: I2dc2924aa20609d2445af00025580b2752935903
* | Add synchronized locks to bugreport callback methodsAbhijeet Kaur2019-10-071-67/+88
| | | | | | | | | | | | | | | | | | | | | | | | BugreportCallbackImpl class methods modify (read/write) the private variable mInfo. Add synchronized locks for consistency. Make other methods static to be thread-safe, and operate only on its arguments. Bug: 123617758 Test: Build and flash. Takes bugreport as expected Change-Id: I237fd940f5ccd4833d053558cf1b014883d59791
* | Fix bugreport rename in API workflowAbhijeet Kaur2019-10-071-72/+142
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In the current implementation of API flow of bugreport, renaming bugreports works fine but it changes the entire name. In legacy flow, the user is only able to rename the suffix of the file. The prefix of the name (bugreport-deviceName-buildID) remains unchanged. Also, wifi and telephony bugreports have the type of the bugreport specified explicitly in the name. Fix Shell's rename implementation to follow legacy logic. Also stop setting name property in the API flow since it's a functional no-op anyway, and we want all communications to dumpstate be through the API when possible. No need to call trackInfoWithId() for remote bugreports as Shell does not process any notification related to it. Bug: 123617758 Test: * Take interactive bugreport, rename and save. (work as expected) Test: Corner case: * Take interactive bugreport, rename and save. * Click on the progress notification again and keep the edit box open. * Wait for bugreport to finish, filename edit box would be disabled and autofilled with last saved rename. You will still be able to edit title and summary. (works as expected) Change-Id: I0016ef4fc1e80fb792712c45439e2b0d348f5249
* | Merge "Handle legacy broadcasts from dumpstate logic in onFinished() callback"Abhijeet Kaur2019-09-261-8/+132
|\ \
| * | Handle legacy broadcasts from dumpstate logic in onFinished() callbackAbhijeet Kaur2019-09-241-8/+132
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In legacy bugreport workflow dumpstate used to send BUGREPORT_STARTED, BUGREPORT_FINISHED and REMOTE_BUGREPORT_FINISHED broadcasts. BUGREPORT_FINISHED and REMOTE_BUGREPORT_FINISHED broadcasts contain information about the bugreport file, this information is not with dumpstate in the API WORKFLOW, and is passed to it by the API caller. Hence these broadcasts need to be sent by the caller of the bugreport API to share the bugreport file information in the onfinished() callback function. Send REMOTE_BUGREPORT_DISPATCH broadcast for DevicePolicyManager to handle. Add minimal information in these broadcasts. Not adding all fields that dumpstate used to send, as most of those were used by Shell. Only sending necessary fileds used by receivers of these broadcasts. Handle clean up of old bugreports in onFinished() callback function Bug: 137825297 Test: * Interactive/Full bugreports successfully created * Share notification appears as expected * Able to attach these to gmail Test: * Trigger remote bugreport by hardcoding the value of remote bugreport when calling the API * Remote bugreport is created successfully * No share notification (same behavior as before) * Same logs in logcat as triggering remote bugreport using old flow: * adb shell setprop dumpstate.options bugreportremote * adb shell setprop ctl.start bugreport Test: * TestDpc (go/testdpc): * Install TestDPC * Set it as Device Owner * Open TestDPC to trigger a remote bugreport ("Request bugreport") * Shows user consent for bugreport collection (indicating that the API workflow is triggered. * Once the collection is complete and you tap "Share" in the notification. * TestDPC shows another notification showing the received bugreport file path and hash. * Verify using adb shell to check if the bugreport file is present in the above specified file path Change-Id: I07c0c64b74a723683601e53e3c68a374ca54f3cb
* | | Merge "Bugreport progress notification should use the bug icon." am: ↵Dan Sandler2019-09-181-3/+1
|\ \ \ | |/ / |/| / | |/ | | | | | | | | cb783ea2ee am: 704b11756a am: 777b2325be am: 362e959c7d Change-Id: I161186cbfef27ace50349d60b1726ef3ba6d1932
| * Bugreport progress notification should use the bug icon.Dan Sandler2019-09-121-3/+1
| | | | | | | | | | | | | | | | | | (Don't worry, stat_sys_adb isn't going away, but it will only be used by the ADB notification now.) Bug: 138661761 Test: initiate bugreport from globalactions Change-Id: I238659d50f70bfbc047133d89afb76f78ec841f9
| * Merge "Remove obsolete methods from DumpstateListener implementations"Nandana Dutt2019-08-071-44/+7
| |\ | | | | | | | | | | | | | | | am: cbdb10f982 Change-Id: Ia746b0cdadd0c4d652c373763f7a12266b080e3b
| | * Remove obsolete methods from DumpstateListener implementationsNandana Dutt2019-08-061-44/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Note that with the new Bugreporting API, SystemServer is the only expected DumpstateListener implementation. Once we fully migrate Shell app, we can remove the implementation in BugreportService as well. BUG: 128980174 Test: bugreport from power menu, observe progress bar Change-Id: I40d654a70bd9ceb3a29f8a0113b85616100f4ee9 Merged-In: I40d654a70bd9ceb3a29f8a0113b85616100f4ee9
| | * Add Looper.prepare() to doInBackground()Abhijeet Kaur2019-03-231-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Fix runtime error that was being thrown as Looper.prepare() was not called in the async function doInBackground. Bug: 124612105 Test: Was not able to reproduce the bug (that is make code execution flow through the catch block). * Reproduced by throwing IOException in the try block so that code flows to the catch block. * Build and flash. * Take interactive bugreport and change title and name of the bugreport from the progress bar. Merged-In: I6a5ea594d95462e1c66bd28eb81dd5f4daa6f35e Change-Id: I6a5ea594d95462e1c66bd28eb81dd5f4daa6f35e (cherry picked from commit b7a6549654374800d3954b4e765c86b5a888258b)
* | | Set up to migrate requestBugreport flavors to use bugreport APIAbhijeet Kaur2019-08-191-7/+29
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Add initial set up code to migrate requestBugreport, requestBugreportWithDescription, requestWifiBugreport and requestTelephonyBugreport to use the new Bugreport API. Prepare the intent (to trigger API workflow) but do not send. Not sending the intent keeps the workflow same as before. This set up helps to move away from directly setting system properties (dumpstate.options.title and dumpstate.options.description). Bug: 139415553 Test: build and flash. Taking a bugreport works as usual Change-Id: I0b57643ff8f4eadb281e1d7788171ef751a01b79
* | | Merge "Remove obsolete methods from DumpstateListener implementations"Nandana Dutt2019-08-061-45/+7
|\ \ \
| * | | Remove obsolete methods from DumpstateListener implementationsNandana Dutt2019-08-011-45/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Note that with the new Bugreporting API, SystemServer is the only expected DumpstateListener implementation. Once we fully migrate Shell app, we can remove the implementation in BugreportService as well. BUG: 128980174 Test: bugreport from power menu, observe progress bar Change-Id: I40d654a70bd9ceb3a29f8a0113b85616100f4ee9
* | | | Merge "Add logic to handle screenshot file creation failure"TreeHugger Robot2019-08-051-12/+2
|\ \ \ \ | |/ / / |/| | |
| * | | Add logic to handle screenshot file creation failureAbhijeet Kaur2019-08-051-12/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Delete the bugreport file to free the space before returning. Delete unnecessary if blocks as the File constructor would never return null Bug:123617758 Test: Force code to execute the if (screenshotFd == null) block. Bugreport file gets deleted successfully Change-Id: Ib88278a8a56799ef562b8b06e5e530a8e31e85d5
* | | | Merge "Leave error handling the same as old workflow using dumpstate"TreeHugger Robot2019-08-011-2/+4
|\ \ \ \ | |/ / / |/| | |
| * | | Leave error handling the same as old workflow using dumpstateAbhijeet Kaur2019-07-311-2/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Removing the TODO as won't be working on improving error handling as part of this bug. Created another bug (b/138576498) to work on better error handling. Bug: 123617758 Bug: 127431371 Test: builds (only removing comment) Change-Id: I8a7fea416e9871909cfb3cc801232bff6056536e
* | | | Merge "Make shell bugreport file names consistent with dumpstate"Abhijeet Kaur2019-07-291-3/+8
|\ \ \ \
| * | | | Make shell bugreport file names consistent with dumpstateAbhijeet Kaur2019-07-291-3/+8
| |/ / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Since bugreport API workflow will be replacing old workflow of directly starting dumpstate, we aim that the resulting file names be the same as the users are used to the old file names (that dumpstate used to decide). Bug:126862297 Test: * Build and flash to the device * Turn on Settings feature flag to use the bugreport API * Take interactive and full bugreports * Output file names same as before Change-Id: I24d800e26a8cc4f739038ac0f27da13bd83f7f47
* / / / Set id for bugreports after dumpstate increments it.Abhijeet Kaur2019-07-251-14/+35
|/ / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | dumpstate increments system property PROPERTY_LAST_ID when a bugreport is triggered. In the old workflow for bugreports, dumpstate used to get triggered before Shell, and dumpstate would send the 'id' to Shell. Hence Shell always assumed that it has a known value for 'id', that is why 'id' is declared as a final variable which could be assigned value in the constructor. In new workflow using API, the 'id' is incremented after dumpstate gets triggered. Hence making the following changes: * Changing 'id' variable to be not final * Reading 'id' after dumpstate has incremented the system property Bug: 123617758 Test: Build and flash to device. Turn on the feature flaggenerate bugreports Check the progress and Finish notifications. Change-Id: I44762190391c128cba135bf0ef795a1ae872dbb7
* | | Merge "Progress notification for interactive bugreports"TreeHugger Robot2019-07-221-3/+1
|\ \ \
| * | | Progress notification for interactive bugreportsAbhijeet Kaur2019-06-041-3/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Send instant progress notification for interactive bugreports (when using bugreport API), starting notification when progress = 0 Bug: 123617758 Test: * Build and flash to the device * Turn on use bugreport API feature flag from Settings * Take interactive bugreport Expectation: Progress notification is shown instantly Change-Id: Icd834c05324108430ee6cb9c3d8539f91059e563
* | | | Add logic to create screenshot fileAbhijeet Kaur2019-07-181-15/+17
|/ / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Creating screenshot file for all types of bugreport * The logic to populate the screenshot file is in dumpstate (few bugreport types that do not need screenshots will leave the file untouched/empty) * Delete the empty screenshot file and set the file to null so that empty file does not get shared * This TODO was previously left as binder did not allow to send null screenshotfd, which was recently fixed. While fixing and testing the optional screenshot fd CL with these changes, left the value "null" by default. Fixed now. * Not adding any logic here on the basis of the type of bugreport as all that is already in dumpstate * Making the names of bugreport (.zip file) and bugreport screenshot (.png file) consistent. In the old flow also both have the same names. Bug: 123617758 Test: * Build and flash to the device * Turn on use bugreport API feature flag from Settings * Take interactive bugreport Expectation: On clicking the notification to "Share the bugreport" only 1 file (the bugreport zip file) gets shared. Also, there is no screenshot file in /bugreports/ in the device * Take full bugreport Expectation: On clicking the notification to "Share the bugreport" 2 files (bugreport zip and screenshot png file) get shared. Also we can see the screenshot file in /bugreports/ in the device Change-Id: I39cb6913033b6e3c61bd0c6655a76524c12d2428
* | | Merge "Add dark theme for Shell app." into qt-dev am: 190e99cf3a am: 1cceacc469Abhijeet Kaur2019-05-291-2/+5
|\| | | | | | | | | | | | | | | | | am: 2c90394b5d Change-Id: I8c913dfa6823f9c9cfee1a68a3f61000e5594b57
| * | Add dark theme for Shell app.Abhijeet Kaur2019-05-241-2/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Bugreport info dialog is used in the BugreportProgressService; services are not themeable from the manifest file. Added themed context wrapper in the service file. Text view underlines are no longer black, and are white in color. Bug: 128364209 Test: build and flash to device, manually verified the color of the dialog Change-Id: Ia42c1c7c2b6f2e30d91a5522f1d6b3507b032cdb
* | | Migrate Shell app to use the new bugreport API.Abhijeet Kaur2019-05-282-97/+329
|/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Add new calls to bugreport API, all the while keeping the previous code and logic untouched. Added feature flag in Settings which if untouched, runs the old dumpstate workflow by default. To test the new workflow turn on the feature flag from UI or `adb shell setprop settings_call_bugreport_api true`. Add permission TRIGGER_SHELL_BUGREPORT so that not all can send broadcasts to trigger bugreports. Create new receiver BugreportRequestedReceiver for the new broadcast intent that the shell app will use. Whitelist Shell app to use the bugreport API. Bug: 123617758 Test: manually built and flash to device. Turn on the feature flag, generate bugreports and check the onProgress and onFinish notifications. Test: Turn off the feature flag test old workflow. Change-Id: I1c7c258a48815a0386d7d4771301cd76f9cae3d0
* / Add Looper.prepare() to doInBackground()Abhijeet Kaur2019-03-221-0/+1
|/ | | | | | | | | | | | | | | | | Fix runtime error that was being thrown as Looper.prepare() was not called in the async function doInBackground. Bug: 124612105 Test: Was not able to reproduce the bug (that is make code execution flow through the catch block). * Reproduced by throwing IOException in the try block so that code flows to the catch block. * Build and flash. * Take interactive bugreport and change title and name of the bugreport from the progress bar. Change-Id: I6a5ea594d95462e1c66bd28eb81dd5f4daa6f35e
* Improvements to Bugreporting API.Nandana Dutt2019-01-231-2/+1
| | | | | | | | | | | | * Add cancelBugreport method. * Remove unused arguments to onFinished listener call. * Publish the system service now that sepolicy for it is submitted. * Use the new bugreportd service. Test: boots BUG:111441001 Change-Id: I12d72e0e1f4ca72d285fd02a3fc1a44f5c179885
* BugreportAPI : Connect listener to binder callbacksNandana Dutt2019-01-151-2/+1
| | | | | | | BUG: 111441001 Test: builds Test: interactive bugreport still works Change-Id: Ie3f2328f558bb2de1dec2908c6ab13f5a17df115
* Add the new dumpstate listener methods to implementationsNandana Dutt2019-01-141-23/+52
| | | | | | | | | | | Add dummy implementations for status, error and finished callbacks. Next step: wire these up end-to-end; change Shell's listener to be BugreportManager.BugreportListener, and make it communicate with the native service explicitly through the new system api. BUG: 111441001 Test: Verified progress in interactive bugreport still works Change-Id: Iad0bb7b23b04f6bc7e3b31e5071df42409c78684
* Merge "Disable the buginfo dialog on AndroidTV"Nandana Dutt2018-10-031-2/+8
|\
| * Disable the buginfo dialog on AndroidTVKristian Monsen2018-10-021-2/+8
| | | | | | | | | | | | | | | | | | Bug: 113033835 Test: Tested manually on Atom Change-Id: If65997e28db7c0100018145f9313549494e41a2a Merged-In: If65997e28db7c0100018145f9313549494e41a2a (cherry picked from commit cb68d29f03f14b188ccc02b877161173b631685d) (cherry picked from commit 01badb78744bc48e35215556a49ac97a17cbce3a)
* | Merge "Warn about sensitive bugreport contents."Nandana Dutt2018-10-031-0/+13
|\ \
| * | Warn about sensitive bugreport contents.Jeff Sharkey2018-10-021-0/+13
| |/ | | | | | | | | | | | | | | | | | | | | We show this message when clicking a notification, but we also want to alert users when they're picking files to attach/share. Bug: 114711671 Test: manual Change-Id: I23e249c93d6fa9cf960ef2a61d3fe769eb56ddf5 Merged-In: I23e249c93d6fa9cf960ef2a61d3fe769eb56ddf5 (cherry picked from commit 59137825eb11e6ca4c53e43a9973983ebdd09b33)
* / Synchronize access to sNotificationBundle.Felipe Leme2018-10-021-4/+8
|/ | | | | | | | | | | | | Otherwise Shell can crash due to ConcurrentModificationException Test: atest BugreportReceiverTest Test: manual verification Fixes:116280360 Change-Id: I138acd43b313d2a7a9d945fb44a9d63e1ad798eb Merged-In: I138acd43b313d2a7a9d945fb44a9d63e1ad798eb (cherry picked from commit ee72fa19a97f2b0677a130204e3527bc3233e4d9)
* Migrated various apps under frameworks/base/packages/Shell to androidxKOUSHIK PANUGANTI2018-08-281-1/+1
| | | | | | | | | | Bug: 76692459 Test: make Shell Change-Id: If11159cac1bd5aa61c46a346647b97a661abbf11 Merged-In: If11159cac1bd5aa61c46a346647b97a661abbf11 (cherry picked from commit e92135a6e9e3bae6236063d35670f3f7f2f51be4) (cherry picked from commit 474df059db94fac9a279e5f90ab0c046de4a3e08) (cherry picked from commit e0efaddbebaf9cdabe4253d7f3cfdf87dc9a7446)
* Bugreport SAF provider isn't "advanced."Jeff Sharkey2018-02-221-1/+1
| | | | | | | | | | | UX churn over the years has turned FLAG_ADVANCED into "show internal storage" which means it's super confusing. When the Bugreport SAF provider is enabled, just show it. Test: sure Bug: 32540478 Change-Id: Id11278c27da8f5f1d1346b208d85b5db59a9e174
* Allow custom keyguard "prompt reason"Lucas Dupin2018-01-111-1/+1
| | | | | | | | | | | | | | Adds the possibility of presenting a custom message on the keyboard if you're trying to dismiss the keyguard. This is particularly useful when you're showing the bouncer because custom authentication (SmarLock) failed. Test: launch FLAG_SHOW_WHEN_LOCKED activity and call KeyguardManager#requestDismissKeyguard Fixes: 63940122 Change-Id: I0d88c0e59521887efa56d74874062b2b14970e4e
* Apply IDumpstateListener changesVishnu Nair2018-01-051-1/+10
| | | | | | Bug: 70154685 Test: Take bugreport on phone and verify debug output Change-Id: Icc5b532689c050837f6b4bde93f4655abec4aa0a
* Update screenshot requests to render proper crop and rotation.chaviw2017-11-301-76/+6
| | | | | | | | | | | | The previous screenshot requests in SystemUI would generate a bitmap and then adjust crop and rotation afterwards. Bitmaps from screenshots are now hw Bitmaps so they can't be updated in software. Instead request the proper crop and rotation from the native code to generate a Bitmap with the correct configurations. Change-Id: I4591c468b055c784460e5ddf2f9163ffa943c2ee Fixes: 69898957 Test: Manual screenshots work and bugreport screenshots work in landscape.
* Don't tag bugreport notifications as System.Felipe Leme2017-07-141-1/+0
| | | | | | | | | | Otherwise, they'll skip DND settings. Test: mmm -j32 frameworks/base/packages/Shell && adb install -r -g ${OUT}/data/app/ShellTests/ShellTests.apk && adb shell am instrument -e class com.android.shell.BugreportReceiverTest$1 -w com.android.shell.tests/android.support.test.runner.AndroidJUnitRunner Bug: 63509844 Change-Id: I7d802b4c8d115c989979a9edaff2f83fc19a4eae
* Only require that system UIDs tag their sockets.Jeff Sharkey2017-06-271-1/+1
| | | | | | | | | | | | | Apps with a normal UID are typically isolated enough to not require socket tagging; we're mostly interested in tracking down internal UIDs that have lots of code sharing the same UID. Also fix up everyone doing manual string checks of Build.TYPE, since we now have first-class fields for those. Bug: 38126076 Test: builds, boots Change-Id: I3a40348196bd8459289f2b9355d9783a07f1e7dd
* Merge "Enable wide color gamut rendering"TreeHugger Robot2017-06-021-1/+1
|\
| * Enable wide color gamut renderingRomain Guy2017-06-021-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When wide color gamut rendering is requested, hwui will now use an rgba16f scRGB-nl surface for rendering. This change also fixes the way screenshots are handled in the platform to behave properly with wide gamut rendering. This change does not affect hardware layers. They also need to use rgba16f scRGB-nl; this will be addressed in another CL. Bug: 29940137 Test: CtsUiRenderingTestCases, CtsGraphicsTestCases Change-Id: I68fd96c451652136c566ec48fb0e97c2a7a257c5
generated by cgit v1.2.3 (git 2.25.1) at 2026-01-10 18:31:59 +0000