Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.mobile.android > #122850

Re: Google improves Google Messages

From "Carlos E. R." <robin_listas@es.invalid>
Newsgroups comp.mobile.android
Subject Re: Google improves Google Messages
Date 2023-12-08 18:07 +0100
Message-ID <kth0qjFikeqU1@mid.individual.net> (permalink)
References (7 earlier) <ukt4ac.mro.1@ID-201911.user.individual.net> <ktgie7FcvgcU1@mid.individual.net> <ukvbaf.8a4.1@ID-201911.user.individual.net> <ktgnqdFcvgfU2@mid.individual.net> <ukvhed.mr0.1@ID-201911.user.individual.net>

Show all headers | View raw


On 2023-12-08 16:49, Frank Slootweg wrote:
> Carlos E. R. <robin_listas@es.invalid> wrote:
>> On 2023-12-08 15:04, Frank Slootweg wrote:
>>> Carlos E. R. <robin_listas@es.invalid> wrote:
>>>> On 2023-12-07 18:53, Frank Slootweg wrote:
>>> [...]
>>>>>      Perhaps other Samsung users (AJL?) can post which Messages app their
>>>>> phone has (Samsung's or Google's).
>>>>>
>>>>>      If Google's Messages app: If they installed that themselves or it came
>>>>> with the phone or a phone-software update.
>>>>>
>>>>>      If Samsung's Messages app: If that can do RCS or/and has settings for
>>>>> RCS.
>>>>>
>>>>>      As to my Samsung Messages app: I can't prove that it can't do RCS, but
>>>>> it does not have any RCS related setting, while I understand the Google
>>>>> Messages app has a switch to turn RCS on/off.
>>>>
>>>> You can open a conversation, and tap in the compose box. A little icon
>>>> or label should tell you if it will use SMS or RCS (and maybe MMS). If
>>>> you try several conversations (private people, not organizations) and
>>>> none says RCS, there are chances your app doesn't support RCS.
>>>>
>>>> My guess is, it does RCS.
>>>
>>>     In the compose box of my Samsung Messages app, there is no such icon,
>>> label or anything.
>>>
>>>     The only things are recipient box (with a '+' to select recipients),
>>> message box (with a '+' to select immediate or scheduled sending) and
>>> the arrow-in-green-circle to send the message.
>>>
>>>     So I can not select RCS and have no idea if the recipient can handle
>>> RCS or not.
>>
>> Well, your phone is three years old, I think you said, and Samsung
>> switched to the google app 2 years ago.
> 
>    Phil said "a couple of years", not two, and without a reference, so
> for the time being we have to take his word for it, together with the
> vague period.

A couple of years is two years :-)

https://en.wiktionary.org/wiki/couple

Noun

couple (plural couples)

1 Two of the same kind connected or considered together.

     A couple of police officers appeared at the door.

2 Two partners in a romantic or sexual relationship.
3 (informal) A small number.
4 One of the pairs of plates of two metals which compose a voltaic 
battery, called a voltaic couple or galvanic couple.
5 (physics) A turning effect created by forces that produce a non-zero 
external torque.
6 (architecture) A couple-close.
7 That which joins or links two things together; a bond or tie; a coupler.


>    Anyway, as I said, my phone is fully updated with Samsung 'Software
> update's (now Android 13) and 'Google Play system update's, but the
> Messages app is *still* Samsung's not Google's. So there for no *forced*
> update/switch from Samsung Messages to Google Messages. AJL reported the
> same for his Samsung Galaxy S10+ phone.

I never mentioned a forced update, not to a different app.

I talked about google updating its own app, and having a default of 
"enabled".

>>>     So things are not as ideal as we would like. OTOH, a sender with RCS
>>> capability can always *try* if the recipient can handle RCS.
>>
>> The google messages tool tells instantly, before typing, if it is RCS.
> 
>    But what if the recipients phone is RCS-*capable*, but the recipient
> has not *enabled* RCS? Does the sender then get any kind of yes/no (RCS)
> indication, *before* sending the message,

We get "SMS".



-- 
Cheers,
        Carlos E.R.

Back to comp.mobile.android | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

Re: Google improves Google Messages "Carlos E. R." <robin_listas@es.invalid> - 2023-12-08 14:01 +0100
  Re: Google improves Google Messages Frank Slootweg <this@ddress.is.invalid> - 2023-12-08 14:04 +0000
    Re: Google improves Google Messages "Carlos E. R." <robin_listas@es.invalid> - 2023-12-08 15:33 +0100
      Re: Google improves Google Messages Frank Slootweg <this@ddress.is.invalid> - 2023-12-08 15:49 +0000
        Re: Google improves Google Messages "Carlos E. R." <robin_listas@es.invalid> - 2023-12-08 18:07 +0100
          Re: Google improves Google Messages AJL <noemail@none.com> - 2023-12-08 10:28 -0700
          Re: Google improves Google Messages Frank Slootweg <this@ddress.is.invalid> - 2023-12-08 18:01 +0000
            Re: Google improves Google Messages "Carlos E. R." <robin_listas@es.invalid> - 2023-12-08 19:16 +0100
            Re: Google improves Google Messages Phil <philusenet1458@gmx.com> - 2023-12-09 13:58 +0000
              Re: Google improves Google Messages "Carlos E. R." <robin_listas@es.invalid> - 2023-12-09 17:03 +0100

csiph-web