Age | Commit message (Collapse) | Author |
|
Handles to show the unlock screen if the device is screen locked.
Please refer to bug for demo videos
Bug: 285328495
Test: Verified manually that on stk app notification click,
it is asking to unlock the device.
Change-Id: I63be4b7e35080f9a8eea6e9f35143bd78b82c4a2
|
|
Bug: 273282505
Test: presubmit
Change-Id: I0cfe7f5920ad7f2733ceba4d156283f827a967bb
|
|
verified manually" am: 3a1517a7a2 am: df31a2ff3b am: 0a254ebb74
Original change: https://android-review.googlesource.com/c/platform/packages/apps/Stk/+/2382003
Change-Id: I3064c0688d03cac8dfb1cd00691e2683f17f70cd
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
Bug: 261140349
Test: verified manually
Change-Id: I6b186648e4b8b2d6e07fe5623f7dffc3a01596a1
|
|
am: cc1964ec37 am: f02c947dae am: 55e9e3bf2c
Original change: https://android-review.googlesource.com/c/platform/packages/apps/Stk/+/2261947
Change-Id: I6aad23ac765a2c72b0c8015f69155be4768e7f0f
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
am: cc1964ec37
Original change: https://android-review.googlesource.com/c/platform/packages/apps/Stk/+/2261947
Change-Id: Ie70b0afeb5a926a2ea5d9042bcc7252229bd3324
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
|
|
Bug: 244483864
Test: verified manually
Change-Id: I43ad6f72d8592c973f1d72328baea175100c6201
|
|
8ef971d282 am: ede8ff39ac
Original change: https://android-review.googlesource.com/c/platform/packages/apps/Stk/+/2256452
Change-Id: Id6213074ad62e7f9064c9e9d57a14529b95de8c6
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
Original change: https://android-review.googlesource.com/c/platform/packages/apps/Stk/+/2256452
Change-Id: I229bb529c6915d1b77efe9da4d172772b1312083
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
This commit is part of a large scale change to fix errorprone
errors that have been downgraded to warnings in the android
source tree, so that they can be promoted to errors again.
The full list of changes include the following, but not all
will be present in any one individual commit:
BadAnnotationImplementation
BadShiftAmount
BanJNDI
BoxedPrimitiveEquality
ComparableType
ComplexBooleanConstant
CollectionToArraySafeParameter
ConditionalExpressionNumericPromotion
DangerousLiteralNull
DoubleBraceInitialization
DurationFrom
DurationTemporalUnit
EmptyTopLevelDeclaration
EqualsNull
EqualsReference
FormatString
FromTemporalAccessor
GetClassOnAnnotation
GetClassOnClass
HashtableContains
IdentityBinaryExpression
IdentityHashMapBoxing
InstantTemporalUnit
InvalidTimeZoneID
InvalidZoneId
IsInstanceIncompatibleType
JUnitParameterMethodNotFound
LockOnBoxedPrimitive
MathRoundIntLong
MislabeledAndroidString
MisusedDayOfYear
MissingSuperCall
MisusedWeekYear
ModifyingCollectionWithItself
NoCanIgnoreReturnValueOnClasses
NonRuntimeAnnotation
NullableOnContainingClass
NullTernary
OverridesJavaxInjectableMethod
ParcelableCreator
PeriodFrom
PreconditionsInvalidPlaceholder
ProtoBuilderReturnValueIgnored
ProtoFieldNullComparison
RandomModInteger
RectIntersectReturnValueIgnored
ReturnValueIgnored
SelfAssignment
SelfComparison
SelfEquals
SizeGreaterThanOrEqualsZero
StringBuilderInitWithChar
TreeToString
TryFailThrowable
UnnecessaryCheckNotNull
UnusedCollectionModifiedInPlace
XorPower
See https://errorprone.info/bugpatterns for more
information on the checks.
Bug: 253827323
Test: m RUN_ERROR_PRONE=true javac-check
Change-Id: I07df460b89c2f6c261626f9482a8c3a807d74167
|
|
Original change: https://googleplex-android-review.googlesource.com/c/platform/packages/apps/Stk/+/20011152
Change-Id: I84751f85d22e87bb541f9eb3587e0651686226d5
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
Bug: 227203202
Test: Manual Verification done
Change-Id: Ie2cc6d9fd45980515cc481ecca415577389ea8f8
(cherry picked from commit b169eb572e57f8a24a51ba8bf14c61eeec2cb646)
|
|
foreground" am: ad17dd1382 am: 050ddad38e am: 4a675e79ae am: 32cd589ba9 am: 809450af0d
Original change: https://android-review.googlesource.com/c/platform/packages/apps/Stk/+/1944564
Change-Id: I1c7219552e3e23f680029c54ef90e9deda6eaac0
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
|
|
Bug: 227203202
Test: Manual Verification done
Change-Id: Ie2cc6d9fd45980515cc481ecca415577389ea8f8
|
|
Bug: 231930192
Test: Manual Verification done
Change-Id: Ie90512001b49062daeceac6e2f2b3c80614716b1
|
|
Original change: https://android-review.googlesource.com/c/platform/packages/apps/Stk/+/2099921
Change-Id: Iaeda7df9e3800ec70b02805dc139139f7a6099e8
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
Avoid calling getSimpleName() on a class type determined at runtime.
This prevents issues with more aggressive R8 optimizations.
Note: Should the Stk app ever switch to using obfuscation, it's probably
better to switch to fixed strings for logging tags.
Bug: 215530220
Test: m + presubmit
Change-Id: I1012148cebf8fe5034bb0283c39853e6322233b1
|
|
Avoid calling getSimpleName() on a class type determined at runtime.
This prevents issues with more aggressive R8 optimizations.
Note: Should the Stk app ever switch to using obfuscation, it's probably
better to switch to fixed strings for logging tags.
Bug: 215530220
Test: m + presubmit
Change-Id: I1012148cebf8fe5034bb0283c39853e6322233b1
|
|
There is an usecase that the software keyboard remains in the screen
even after closing StkInputActivity. This change is an approach to fix
the issue on SIM Toolkit app side.
Bug: 224586736
Test: Manually confirmed that the software keyboard disappears
Change-Id: I217737858d0d02688dd7e114459e496aa904fbac
|
|
Bug: 205056467
Merged-In: I9936a3eac58497f7e54184499d9bc04d40696e03
Change-Id: Iafb589f302cf44bca6946f20093fbd6a5888524c
|
|
ACTION_CLOSE_SYSTEM_DIALOG always requires a receiver exported flag. It seems as if receiver in ToneDialog has one caller in the same class, so we are going to mark it as NOT_EXPORTED.
Change-Id: I4f6a138fad39dda7b091b5cd71dd6d4906211f61
Test: no-op
Bug: 161145287
|
|
am: ea4c284bed
Original change: https://android-review.googlesource.com/c/platform/packages/apps/Stk/+/1450515
Change-Id: If191d9a8d138a7a28c59eba9ac0d4386ee82f9bb
|
|
|
|
Original change: https://googleplex-android-review.googlesource.com/c/platform/packages/apps/Stk/+/15662609
Change-Id: Ia453ea188f2e06ebcb35577a8bdd4f91b35f250f
|
|
Test: manually verified
Bug: 194545490
Change-Id: Ia9cf7c3500e9ad939d4bfc225b60c9052ee2024e
Merged-In: Ifcada6c2cfeb8805dd422d0c44b98618de6c1bb8
|
|
Original change: https://googleplex-android-review.googlesource.com/c/platform/packages/apps/Stk/+/15664508
Change-Id: I944d4461b7f8e56ae94dac6d58e4ea165a16e8a1
|
|
Test: manually verified
Bug: 194545490
Change-Id: Ifcada6c2cfeb8805dd422d0c44b98618de6c1bb8
|
|
|
|
Test: none" am: 76da9cc0a5 am: 28ced5f1d7
Original change: https://android-review.googlesource.com/c/platform/packages/apps/Stk/+/1790992
Change-Id: I9f1e14d9cfa0e4ab7d94f4b40de59d0eb5fbbcb8
|
|
Bug: 194545490
Test: none
Change-Id: Id74724b13ac69d21fe753dd0a82683c0039addcb
|
|
am: 0f79cda521
Original change: https://android-review.googlesource.com/c/platform/packages/apps/Stk/+/1318779
Change-Id: Idee9e2352a37e30369b884768fba1848786b7830
|
|
SIM Toolkit has a logic to remove itself from the launcher screen once
it becomes unnecessary, but the condition is wrong. It is removed when
all the SIM cards go into ABSENT state in the current implementation,
but it must be executed when the number of active main menu becomes 0.
Bug: 159662728
Test: Manually confirmed all the possible SIM removal scenarios.
Change-Id: I8091bf6ea82df873335cce3477a6c759735ed79b
|
|
There are several places we can find similar logics to show or hide SIM
Toolkit application on the launcher screen. Some are a kind of code
clone and another one is a bit different logic. That is not good for
future code maintenance.
Bug: 159662728
Test: Manually confirmed all the possible SIM removal scenarios.
Change-Id: Iaea976aa772b2d07a162619ba089839bb465e83a
|
|
22d92add67 am: 5e023c00b1 am: 6473b856ba
Original change: https://android-review.googlesource.com/c/platform/packages/apps/Stk/+/743041
Change-Id: I3a7454055bfdea6cd53d0e4c92278354379c15d5
|
|
The list of the menu items provided by SET UP MENU command shall be a
part of the menu system of the terminal and the alpha identifier shall
be used for the title of the menu in accordance with the clause 6.4.8
SET UP MENU in ETSI 102.223. The terminal shall be able to display the
alpha identifier as the lable of the launcher activity of SIM Toolkit.
Bug: 113638339
Test: Confirmed the label of SIM Toolkit can be controlled as expected.
Change-Id: I215de452f14aaa04b7389197aac03c1d50257ae0
|
|
NotificationBuilder.setContentTitle() is called with the application
name in some scenarios, but it is unnecessary in many cases because the
header area also shows the application name. Content title should be
specified only when it is helpful to differentiate multiple SIM cards.
Bug: 170175877
Test: Manually tested various SSIM/MSIM scenarios
Change-Id: I118a7b0998ddd74184a1def30d6b483aa6854e01
|
|
Bug: 179047632
Test: build
Change-Id: Ief2c93d2f59f1b0e442694f24871116f515f6260
(cherry picked from commit e030178897b44aebb610cc3157c2b5cd2fb81ea3)
|
|
Rename to HomeVisibilityListener
Bug: 170226810
Test: atest ActivityManagerTest
Change-Id: I37eef12435af3411f2d6d78980000b92ae6d27e8
|
|
Revert "Expose the HomeVisibilityListener API"
Revert "Add CTS for HomeVisibilityListener"
Revert submission 12775890-home-vis-listener
Reason for revert: broke build, b/170776449
Reverted Changes:
I8e6de3267:Add CTS for HomeVisibilityListener
I33d943603:Follow rename of HomeVisibilityObserver
I5d99f2bad:Expose the HomeVisibilityListener API
Change-Id: I1c4507ade4c84d114a199079cee40b3568d8710d
|
|
Rename to HomeVisibilityListener
Bug: 170226810
Test: atest ActivityManagerTest
Change-Id: I33d943603735e9a334c9b8f68439ac190b5e2ba8
|
|
Original change: https://googleplex-android-review.googlesource.com/c/platform/packages/apps/Stk/+/12424843
Change-Id: Ie22718250c752e7f87ac5beedb1d600fbbb6e0ce
|
|
Bug: 161207764
Test: manual
Change-Id: I6fc37039c2153211c5bc669aca4a2e642dfd935a
|
|
Original change: https://googleplex-android-review.googlesource.com/c/platform/packages/apps/Stk/+/12363181
Change-Id: I03e6021808fa1245a45a874890214e0eef75b6ac
|
|
This aligns the behavior of lockscreen notifications with that of idle
screen notifications (see line 2153: for notifications posted when
screen is idle, we either set the notification title to the menu title
(if we are currently handling an STK menu) or we set it to "".)
Note that the app name will still be visible on the notifcation.
Bug: 162908615
Test: manual
Change-Id: I1944307dbddb8744123d34954ed5dcf0b5eddc6e
|
|
For interactive STK dialogs which listen for user presses of the HOME
key, we will treat RECENTAPPS presses as equivalent. The reason for this
is because with new gesture-based navigation it's hard for the user to
trigger a HOME press, and the same user intention often triggers a
RECENTAPPS press.
Bug: 161207764
Test: manual
Change-Id: Ib64068f191e62b7103472d39525305be3dab59c8
Merged-In: Ib64068f191e62b7103472d39525305be3dab59c8
|
|
369b84b595
Original change: https://android-review.googlesource.com/c/platform/packages/apps/Stk/+/1389216
Change-Id: I167b47c0fc642799fd4b32088e7b7b863859ec82
|
|
For interactive STK dialogs which listen for user presses of the HOME
key, we will treat RECENTAPPS presses as equivalent. The reason for this
is because with new gesture-based navigation it's hard for the user to
trigger a HOME press, and the same user intention often triggers a
RECENTAPPS press.
Bug: 161207764
Test: manual
Change-Id: Ib64068f191e62b7103472d39525305be3dab59c8
Merged-In: Ib64068f191e62b7103472d39525305be3dab59c8
|
|
a0bbc5e35a
Change-Id: I1b08668e06dd1ae4d2400fc6c6f5da429045de2d
|