Age | Commit message (Collapse) | Author |
|
PiperOrigin-RevId: 408462735
Change-Id: Ia54550179ad88a213890529afa62d04e62346fd2
Bug: 203687523, 203700812, 203707755, 204487577
|
|
paused.
Bug: 202322468, 197674787, 202427652
PiperOrigin-RevId: 402636807
Change-Id: I05e66762e9f9ed95be5e5d2dbf15aa5a5cbf4b6f
|
|
Bug: 197674556
PiperOrigin-RevId: 401365789
Change-Id: I9a569ece4fc902ed4aca014c137bead4fba6dd39
|
|
Fix: 197153503
Test: Manual
Change-Id: Iff8b96fd308f9602b875b5bba828bfeaec0e2261
|
|
Messages content lost after tap Mute, and messages no longer displayed in Notification center
Update conversation "mute" behavior
RCS message content with text+image disappears
All Messages Database read in First Received Message - If MSG DB has unread Messages
Add "tap to read aloud" to Car Messenger
Old messages read out along with the new message
Bug: 182834412, 197153672, 197532449, 199747755, 200687249, 200689447
PiperOrigin-RevId: 400019901
Change-Id: I2a893b45ee45208fe8bb9469ae0a72016da1ed68
|
|
PiperOrigin-RevId: 395801506
Change-Id: I32f699c09a359ff10dcc705564c2108e279062a1
Bug: 197576507
|
|
Bug: 188396041
Test: Manual
Change-Id: Ia3afbbf6cfa652e5a153cb3453fc4e78bf5bafd6
|
|
PiperOrigin-RevId: 382848835
Change-Id: Ib62228110fdd634c6ddf2f9660f525c33013ae66
Bug: 185279757
|
|
API is ready.
PiperOrigin-RevId: 382634124
Bug: 161144808
Change-Id: Ib95c7e1fe3f081da8940ffa79300c4b4ae5b769c
|
|
PiperOrigin-RevId: 382626868
Change-Id: I6be0527e4edc8cc6226b70a08e9282a9323edc16
Bug: 192598216
|
|
PiperOrigin-RevId: 382178480
Bug: 192390813
Change-Id: I73a9374f60e4b2b9d271de4c94592a3e14cafa9e
|
|
PiperOrigin-RevId: 381956735
Bug: 184573289
Change-Id: Ie42f649ace8bc73fead097a96e8bad8ac44e9733
|
|
Targeting S+ (version 31 and above) requires that one of
FLAG_IMMUTABLE or FLAG_MUTABLE be specified when creating a
PendingIntent. So this CL uses FLAG_IMMUTABLE to create
the PendingIntent because the flag is recommended in most cases.
Bug: 192103710
Test: manual
Change-Id: I2ab79dc4a0e6279676135a34ee8230190cbdd27e
|
|
Bug: 190713258
PiperOrigin-RevId: 378985586
Change-Id: Ic1e146f8628f0cd320b6436221fc88b4d4cee376
|
|
PiperOrigin-RevId: 377626398
Bug: 189198971
Change-Id: Iadf7a2517e5e6b3436814336ae9eaebed6bf9434
|
|
Bug: 184649681
PiperOrigin-RevId: 374699655
Change-Id: I277ad38b5c84adcb2758cc8bf4f6e329e8c06ddf
|
|
Bug: 183655801
Change-Id: Ie6cd71b6604b4f78e80e1288998765426169ca3f
Test: manually
|
|
Bug: 183210926
Test: Resolves NullPointerException
PiperOrigin-RevId: 363998728
Change-Id: I57eb9d3eae420b2fba906470315f2cfbf8f6832e
|
|
Bug: 172853812
PiperOrigin-RevId: 363771443
Change-Id: I31713f2520c40971bdd0766d17cd2bcfcc9d06d2
|
|
This reverts commit c3c585e07c255d3af5779b5daff7161d9cf1f6fc.
Reason for revert: Need to fix authoring
Change-Id: I513c3785dd0d3719fe1836167a92e2121b2c166b
|
|
Bug: 172853812
PiperOrigin-RevId: 363677727
Change-Id: Ic41588f8331e5908a865e66c51e7a83c6a9173fd
|
|
Generated titles should not be reused after changing the locale.
Because:
1 - Change of locale means none of the separators used are valid
anymore. For example a string like "name, name2, name3" cannot be used
in a language that does not use "," as a separator.
2 - All the text direction markers should be reassessed when the locale
changes. Please note that TextDirectionHeuristics.LOCALE translates
to either RLM or LRM based on the current locale. The generated string
should not be used in another locale with a different text direction.
Bug: 159221409
Bug: 161947401
Test: Manual
Change-Id: I725f23a306ff97889d08879c44a38c94f128d326
|
|
Fix: 161853183
Test: manually tested, see comments in the bug.
Change-Id: I336a32ee70ab16afd762fa1e51b61aa260d5249b
|
|
Bug: 159221409
Test: manual, unit tested API
Change-Id: I0b170d4ca5aa9f25c46c77493ade4098ed394e21
|
|
Fix: 145803615, 144314202
Test: verified app w/ changes has no regressions, performs TTR correctly,
group conversations work as expected.
Change-Id: If719cf10b239ccdf8be9fb4f60081252e27fe978
|
|
Bug: 145803615
Test: verified Messenger app built successfully, locally used this class
and verified Group message notifications appeared correctly, replies
to a conversation updated the conversation's notification, Tap to Read
worked as expected, and the title showed up correctly.
Change-Id: I626fe741dda3578befc99ee8be358bc6eee3d90e
|
|
Part of the refactor effort to share logic with 3P messaging.
Bug: 145803615
Test: built Messenger app with no errors.
Change-Id: Ibc630153e45c129e61d7742065e49e9a8015f1d3
|
|
Bug: 152233109
Test: built app successfully, verified notifications suppressed correctly,
verified no service connection leaks when user switched.
Change-Id: I3e9bc924de7a3b74486ef551bcef2f3fc7059bef
|
|
Change-Id: I28488b8e95040e50657a43fe5ca148524a877051
|
|
NotificationInfos hold reference to MessageKeys, which then map to
Messages. Since we were clearing the Messages map before Notification
Infos Map, and before clearNotifications(), NPEs were being thrown
when clearNotifications() was making an API call to a null Message
object.
Fix: 151448117
Test: verified on hawk by disconnecting a device, checking for NPE
Change-Id: Ifad7145dbae5774f9339ce74612d0a49a8b20ddb
|
|
If a projection app, like AAP or Carplay is in the active foreground, we
should just post message notifications that originated from the phone
(and hence will already be shown in the projection app) silently in the
notification center without posting a HUN.
Bug: 138747359
Test: verified on IHU by having AAP + non-AAP phone connected via BT:
Ensure SMS notifications appear when AAP isn't active,
Ensure SMS notifications for non-AAP device appear when AAP is active,
Ensure SMS notifications for AAP device don't appear when AAP is active.
Ensure SMS notifications still show up in the notification center
Change-Id: I10ee77012a48fe451e0e88e82557f092beb3bcdf
|
|
qt-qpr1-dev
|
|
If a projection app, like AAP or Carplay is in the active foreground, we
should just post message notifications that originated from the phone
(and hence will already be shown in the projection app) silently in the
notification center without posting a HUN.
Bug: 138747359
Test: manual
Change-Id: I89dcbe55e6f115b4b5afd8c7dff3119777cbc98c
Fix: verified on IHU by having AAP + non-AAP phone connected via BT:
Ensure SMS notifications appear when AAP isn't active,
Ensure SMS notifications for non-AAP device appear when AAP is active,
Ensure SMS notifications for AAP device don't appear when AAP is active.
Ensure SMS notifications still show up in the notification center
|
|
Change-Id: I5590f81df7ddda2b884d9d26e5f9563c94cd354c
|
|
|
|
Change-Id: Ic78e23f28f92eaa9e7f7b854d751fe4ec86e7ad6
|
|
This CL drops messages that have multiple recipients. This is a
risk mitigation change in case Bluetooth MMS/RCS support is added
later on this branch. If the Bluetooth change is added, 1-1 RCS
and non-Group MMS messages will still be supported by Messenger.
Bug: 145803615
Test: to test on hawk, verify no breakages.
Change-Id: Ie3e0dc99ffac33b355c5ffdca8bf091b56da2f73
|
|
Java initializes booleans to false. shouldInclude should initially be true
for all messages.
Fix: 149993183
Test: verified Tap to Read flow works on Hawk
Change-Id: I6f05f7ee544f2cc022bf08d2b6b66e33daf22181
|
|
b078b94a57
Change-Id: I7a20099b97530897c056b004367043b9af268818
|
|
When a user dismisses a message notification, OR when a message
notification is successfully read aloud, the messages in that notification
should not appear when/if that notification gets updated with newer
messages.
This change combines the two states (dismiss and read) since they both
have the same logical consequence.
Change-Id: I1518a86606f4035e6f721844e4705442482a3307
Fix: 146362547
Test: manual
|
|
fd9e8e0361 am: e1358b52a2 am: 6deca8922c
Change-Id: I830a75f3d762ade6b518b6c44ecafc8e5f344637
|
|
This will ensure the icons are synchronized between Dialer : Messenger, and
that OEMs can set their icons to be rectangular by setting
contact_avatar_corner_radius_percent to 0.
Bug: 145832093
Test: manual
Change-Id: I4fe686dc450d545e9f36877f3eb3fd090541a874
|
|
am: a5dcdcacb9 am: 1c9caeab89 am: daccdb46f0 am: 4b4a259736
am: e5e202786f
Change-Id: I15ced67c7fba21fa4405d20213f6c7cb00e761af
|
|
|
|
c952b06498 am: f05024ea55
am: 446044e136
Change-Id: I57bb4a3d152f31096f0a7872f65749b5403a6a8a
|
|
This CL fixes a couple of bugs:
1. When Messenger gets onDestroy we should call closeProfileProxy as that
is what is causing ServiceConnection leaks
2. onServiceDisconnected is called when the connection is lost, not necessarily
when the connection is closed so instead of calling BMC.close in this situation,
we should only set BMC to null and not make any BMC API calls until
onServiceConnected
3. Because of 2, trying to reconnect by calling getProfileProxy won't speed
up getting the BMC, so we should stop doing that.
4. Sal mentioned most BT lifecycle logic relies on closeProfileProxy, not
BMC.close, so I stopped calling that API
5. For readability's sake, I renamed the cleanup() methods to specifically
onDestroy so readers can understand when this method is invoked.
Change-Id: I7727df11664a67b809a2361289afbc4623877631
Fix: 142077620
Test: manual, force onDestroy
|
|
Contact URIs need to be non-null for BluetoothMapClient to understand
which sender on the phone to send a message to. Therefore, if a URI is null,
we should disable replying/sending a message.
Change-Id: I8d8bf9d8ad335711de32efbe6f1e3664901844d6
Fix: 144842584
Test: verified for iOS 12, iOS 13+, Android
|
|
am: f312e689fc
am: 74f2b36cd8
Change-Id: I30890a0e4070376f81bb4aa16e9aa0041ac9ae32
|
|
Fix: 144778351
Test: mma
Change-Id: I10e97bd4c4ad237f8e224f2ba74c900db7241832
|
|
478b1acf29 am: 0199ff9e28 am: f33fd37e63
am: 1485f78347
Change-Id: I278b77d53896b86c1f06d22a5296cb976d0b1fca
|