frameworks_base.git - frameworks

	Commit message (Collapse)	Author	Age	Files	Lines
*	Share Wear bugreport right after it is taken	Yeabkal Wubshit	2021-11-24	1	-4/+8
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	In rvc-wear-dev, bugreports were not shared to phone until user tapped on the bugreport-complete notification. Now, we are sending bugreports to phones immediately after bugreport is taken. We still retain the bugreport-complete notification. The bugreport-complete notification will have an action button that leads the user to a bugreport-warning screen as long as the user has not opted out from seeing the warning. If the user chooses not to see that message again (which they can do in the warning screen), there will not be any action button on the bugreport-complete notification, and the user can just swipe to delete it. Refer to the look of the notification when no warning message is to be displayed (https://screenshot.googleplex.com/JStqotLwCaTXeL9) and when a warning message is to be displayed (https://screenshot.googleplex.com/AdGKWFqbky8Ad8s) Note: this change does NOT affect the functionality of the BugreportProgressService for any other device except Wear devices. Bug: 163083307 Test: the described feature tested with salmon running rvc-wear-dev Change-Id: If6890ef8cada60e454c9232d402bbdb8a1b0315e
*	Don't allow non-system window overlays for bug report warnings.	Varun Shah	2021-05-12	1	-0/+5
\| \| \| \| \| \|	Bug: 175614079 Test: test PoC app Change-Id: Ie4543c95a6b2d7de47360737b82a6dadde704053
*	Only require that system UIDs tag their sockets.	Jeff Sharkey	2017-06-27	1	-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
*	Always use chooser for Share Bug Report intent.	Felipe Leme	2016-07-28	1	-1/+2
\| \| \| \| \| \| \| \| \|	When using startActivity(intent), the platform allows the user to pick the same activity for the intent, which can be a problem for sharing bug reports when the device has personal and work profiles. Change-Id: I1fd66905feb5d894307bbe5656c2aec705a59ab7 Fixes: 22115530
*	Don't opt-out of warning dialog by default on user builds.	Felipe Leme	2016-04-25	1	-1/+10
\| \| \| \| \|	BUG: 28341946 Change-Id: I9ce6bf52a02a14055d4ded41aac50c79abdb4ee9
*	Revert warning logic so it has a "don't show again" message.	Felipe Leme	2016-04-13	1	-2/+2
\| \| \| \| \| \|	BUG: 28140003 Change-Id: I93e7b1494a0f4c5ca080fbe9dd94dc2168092ffa
*	Handle finished bugreports, share from private.	Jeff Sharkey	2013-03-13	1	-0/+77
	Show notification when a bugreport is finished, letting the user launch a SEND_MULTIPLE intent to share them. Add dialog that warns user about contents before sharing. Since bugreports are now stored in private app data of the Shell app, use FileProvider to build Uris that we can grant others access to. Define BUGREPORT_FINISHED as being a protected broadcast. Delete older bugreports automatically to reclaim disk space. Migrate any Intent extras to ClipData when building PendingIntents. Add --receiver-permission support to am shell command. Bug: 7005318 Change-Id: If6c607dbcf137362d5887eac482ff7391563890f