When tests run for the first time, the list of activities that can
handle ACTION_SEND_MULTIPLE might not be scrollable, which was cause the
scrollForward() method to fail.
BUG: 27431998
Change-Id: I5992bc9fec6291c74c4af7887ee66eb4f96e87c0
am: 06e650c
* commit '06e650cd97df645bd0bef9342b432ca885679b13':
Revert warning logic so it has a "don't show again" message.
Change-Id: I64e0cf42ebedd931a22c6eda3ce60cb1907ec767
am: 7fd1cbd
* commit '7fd1cbd49d0ace00c65229f65252136902aedaf3':
Revert warning logic so it has a "don't show again" message.
Change-Id: Ie2ca3b9be95991b8d0087bd83c49ed85df33b0c9
When a bugreport is finished with a pending notification, it already
display a subtext explaining the situation - not only the extra title is
redundant, but it's too large.
BUG: 27583025
Change-Id: I8d8171faf7b8b86b34f6d860555839918be10550
The code that asserts the right progress is displayed was based on the
percentage text displayed in the system notification, but such text is
gone.
Since UIObject doesn't easily expose the underlying ProgressBar, such
checks were temporarily disabled.
BUG: 28114251
Change-Id: Idb64fe97cf84f5f73e08e293b8fd0384bc8b70d6
am: dfbd58a
* commit 'dfbd58aa7ebeaff7f8a18cfd236ec04cfef97396':
Fixed the contentinfo api usage in the bugreport
Change-Id: Idbbe3484a2e257a8d8b3c84896db49775903ea43
am: cbc68e5
* commit 'cbc68e59119e31ccd405c482afe19572c520cec3':
Fixed the contentinfo api usage in the bugreport
Change-Id: I9fb1d5202c919d1bb7f4cde7884d2c9c98ac14ad
Removed the percentage shown in the header and
migrated the name to the subtext as contentinfo
was deprecated.
Change-Id: Ifd79a67cad8958049bd29b8eb4c9bcbb4822688b
- Better dump of received intents by displayed the relevant extras.
- Gracefully handles the case where the bugreport file URI is invalid
during development.
BUG: 27996121
Change-Id: I97a48d1e9641142a43c66c1dded2f7f322dc66aa
On M, internal storage such as bugreport files were only shown when user
selected the "Show internal storage", but such UI has changed on N.
BUG: 27862860
Change-Id: I1edf086a9f9345303595ee952e4646764709d36d
When Shell receives a BUGREPORT_STARTED intent for a process it's
already monitoring, it should completely ignore it, but current it's
taking an extra screenshot.
BUG: 27804637
Change-Id: I733cacfee5e9c82646a3295b50c3856b6e0352c3
When dumpstate starts, it estimates its maximum duration and sends it
through an extra on BUGREPORT_STARTED; as it progress, it sets a system
property with its current progress and if the progress value overflows
the estimated max, it increases the max as well.
Shell uses the max/progress to display the progress % in the
system notification, and need to handle the scenario where the max
changes. The initial implementation would recalculate the progress, with
makes it swing back and forth as dumpstate increases the max.
This CL changes the Shell logic so the progress never go back, just
forward. The drawback of this approach is that if dumpstate
underestimate the maximum, the progress might get stuck in a high
value (99%) early on, but such issue will be addressed in the long
term by tuning the estimated max value.
BUG: 26354314
Change-Id: I3a5416acaffaaa43fd28d2f1f8ec8ea12aa0d91e
Mostly consists of removing the word "encryption" from most APIs,
since we can't actually make promises about the data being encrypted.
Bug: 27531029
Change-Id: Iace9d7c4e64716abf86ed11847c40f3947e1d625
