| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Change-Id: I57645a59c1d37c5f2fdcee13a920f6be0a9276db
|
|
|
|
| |
Change-Id: Ia0f3867d40d7f317e9fbe2fd55f0a3d26ce3d44f
|
|
|
|
| |
Change-Id: I16c3223a7d5d3fc3ccf680d92c417f1d7e04676a
|
|
|
|
| |
Change-Id: Idc7f7294f4c2511ace43a291cd2360f22b3dba13
|
|
|
|
| |
Change-Id: I3cd230d0c91b9e2efb56c56634f54edd7581323d
|
|
|
|
| |
Change-Id: I6c8922d41dc8063725378a6224907bde13050bea
|
|
|
|
| |
Change-Id: I9f221a937bc7d2956b041297107098f025fe46c2
|
|
|
|
|
|
|
|
|
| |
We no longer need this custom setting.
With the new wizard manager-based setup wizard, the original
issue addressed by the setting is no longer present.
Change-Id: I1ba64ba7da6034023db260c7519d00aa64182261
|
|
|
|
| |
Change-Id: I766f80d6413754f14a073921a3367993b5eea911
|
|
|
|
| |
Change-Id: I7223d0f21ae33b421d572f264c68044117cd7217
|
|
|
|
| |
Change-Id: Ib7074e9f90bed16e6fa1cce3992a6146f77e3b84
|
|
|
|
| |
Change-Id: I9046e0fde6c4fa2476f788d92356e059f8a5148d
|
|
|
|
|
| |
Change-Id: I8249347939d948c229346aff19c6e816aaf00a60
Ticket: -
|
|
|
|
|
| |
Change-Id: I7065c2947db93d889cbc8a95ae7ff3f4d715f537
Ticket: -
|
|
|
|
|
|
| |
packages/apps/InCallUI/res/values-zh-rTW/qtistrings.xml:35: error: Error parsing XML: not well-formed (invalid token)
Change-Id: I04969357aa563e8b0d66fe830ed082db94c70372
|
|
|
|
|
| |
Change-Id: Ia21963ddc29dfe6e1f845ac935bc49b52d8f84b2
Ticket: -
|
|
|
|
|
| |
Change-Id: I6489cef03c0f3ae6544aa5ba39c09bcbbd1169a1
Ticket: -
|
|
|
|
|
| |
Change-Id: I6f2faa1bcb22e5fe2887f38854e022f1c471dc9d
Ticket: -
|
|
|
|
|
| |
Change-Id: Idef3bd77e1f662179b92627c9b567b8c0bbef8d5
Ticket: -
|
|
|
|
|
| |
Change-Id: I847520f1c1c8bb41e78fcd25172be5ebe44e1f36
Ticket: -
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The original patch causes a mismatch between the call action text
and the call action buttons. Although the call action buttons were
swapped for RTL targets, the call action text were not.
As a result, to answer a call, the user has to swipe left to a
button that is green, but whose text is "לא לענות" (Do not answer).
The same goes for the other call action buttons.
This reverts commit 5227cbd5278bf614197b6b0cf85517f82ad0eab8.
Change-Id: I6c677008f4ed246019ae5972b3355d4402d09679
|
|
|
|
|
| |
Change-Id: I7ddb6c7efba94a333e3d76ce31f9f55d6501c70e
Ticket: -
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
On smaller devices this moves the glowpad too far
down, resulting in the bottom of the block target
to be cut off by any softkeys. Instead, glowpad
should figure out its placement according to gravity.
Glowpad don't need no marginBottom telling it
how to live its life.
Ticket: CYNGNOS-3119
Change-Id: Ic5584a47f7d94c7c3291a8e963413c7e9e4062c4
|
|
|
|
|
| |
Change-Id: I263d9e256cf1c3793c213872b37931f53f889731
Ticket: -
|
|
|
|
|
| |
Change-Id: Ica047bc376cd979c6c6b93609e9c65f748cc06bd
Ticket: -
|
|
|
|
|
| |
Change-Id: I1bfb033bc80af5e5ac43d063e13b568c6f69ad0a
Ticket: -
|
|
|
|
|
|
|
|
|
|
|
| |
On smaller screens with custom themes and software nav the
bottom target (Block) can be cut off by the navigation.
This sets our gravity to properly scale for a completely
centered ring.
Change-Id: I02f8bdc86ec4ae7ab95fe7b04a313b112cad2610
Ticket: CYNGNOS-3119
|
|
|
|
|
| |
Change-Id: Ibcbd00503dd1f2f8741c3ca13b3e897cf12a8b1b
Ticket: -
|
|
|
|
|
| |
Change-Id: I9f33aec516eaa7fab6848300f6bfcd87f4f2b67b
Ticket: -
|
|
|
|
|
| |
Change-Id: I102ad9be83a347f4c24b2c0b8bf317fcf26e92a4
Ticket: -
|
|
|
|
|
|
|
|
| |
When a dialog gets cancelled on the incall screen we need to reset
the glowpad otherwise the ui gets into a strange state.
Change-Id: I1bd73152e2e38bb64d35fa2dd42933fe08a077a8
Ticket: CYNGNOS-3111
|
|
|
|
|
|
| |
Ticket: CYNGNOS-3096
Change-Id: I67648c1651f59b0a9774c77ce6d6d25bc76da5f0
|
|
|
|
| |
Change-Id: I7480a2af3cdb48009f7aafc34fb08fa38e9cab9b
|
|
|
|
|
|
|
|
|
|
|
|
| |
Consider case where VT call UI is in fullscreen mode and the
UI orientation is changed. When InCall activity is re created
due to rotation, the fullscreen flag is still true, but actual
UI will be created in normal mode. Due to wrong fullscreen flag
value, auto enter fullscreen thread is not scheduled.
To fix this clear fullscreen flag in InCallActivity.onCreate().
Change-Id: I18ec2b4442eae3b9ec01aeacc2b38f91f08f21c9
CRs-Fixed: 979860
|
|
|
|
|
|
|
|
|
|
|
| |
If ContactsProvider is unable to get geocoder location for call
number, the 'null' will be used to populate DB.
When InCallUI cannot get its geocodder loaction, it should ignore
displaying geocoder location info.
Change-Id: Ibdfcf607ba3044de39a886c171f144f804410b36
CRs-Fixed: 942213
|
|
|
|
|
|
|
|
|
| |
When anwser a incoming call, GlowPadView alwasy shows the button
in LTR view. While the RTL locale needs the mirror UI of LTR.
Switch the left target and right target while in RTL view.
Change-Id: I693932ab1cba35910dbea418adb50e0a32a7364d
|
|
|
|
|
|
|
|
| |
When user answers the call from status bar do not display the incall
screen until ACTIVE state is received.
Change-Id: I3d9667bccdf1bac3ab817a0282a8140c6dea785b
CRs-Fixed: 936970
|
|
|
|
| |
Change-Id: I1bdbe15b039ce45cd718570befb6789e4fc797c3
|
|
|
|
| |
Change-Id: Ia1cf45d78649ba21992d446ca72e5fa3d88d0e3f
|
|
|
|
| |
Change-Id: I41950b19683d99462d3fb0a733f461e70791557a
|
|
|
|
|
|
|
|
| |
commit 919274abeb189a33e35533825aa0071b1c7e2bc1
introduce a problem that reject call with message
does not dismiss the call ui. Fixes it.
Change-Id: I136358b2855ce31c183b37ee1690f47a8d38eaeb
|
|
|
|
|
|
|
|
|
|
|
| |
The right icon within the notification at times had the wrong visibility
state. This led to the contact attribution badge not showing up at times.
This could be the result of a series of notification state updates due to
the state change callbacks via ContactInfoCache. Resorting to explicitly
updating the view's visibility.
Change-Id: I447a1a4dc08ee8b6bba5569c7a1bb91d7677bd15
Issue-Id: OPO-766
|
|
|
|
|
|
|
|
|
| |
This call was causing a lot of log spam on devices without Core, and
may have been contributing a slow down in showing the Call UI.
NOTES-150
Change-Id: Ica37627f22673d5f521e2be164ed05e709bf216f
|
|
|
|
| |
Change-Id: I3be835ba09d60ae151cff28995ed86360d324913
|
|
|
|
| |
Change-Id: I98a3536fc75e589386cdd0f54c6aca13bd428848
|
|
|
|
|
|
|
|
|
|
|
| |
At least rejectCallWithMessage seems to get called with
phoneId being -1, resulting in an OOB
Fix that case on other places as well
Reference:
BugDump 20160527-0602 L#163
Change-Id: I65ae5bc439ef9a4d4f435369e1c41abe110e02b6
|
|
|
|
| |
Change-Id: I1ba8fba8c707837559c03a1346c43979fadeea5a
|
|
|
|
| |
Change-Id: I9b773ccb4fac5e1ff312e94767a23d9bb832e2da
|
|
|
|
| |
Change-Id: Idf6ccd70c78f94fc25148052965a8957b5e8cb6b
|
|
|
|
|
|
|
|
| |
That ring doesn't really look material-ly. Go back to just showing the
colored icon in normal state and white icon on colored circle in
activated state.
Change-Id: I147e22e590a34c966aee9567f9ff549f6f957107
|