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


Groups > comp.mobile.android > #149489 > unrolled thread

For those using Google messages with RCS with iPhone owners...

Started byMarion <marion@facts.com>
First post2025-07-02 04:15 +0000
Last post2025-07-07 15:27 +0100
Articles 20 on this page of 28 — 9 participants

Back to article view | Back to comp.mobile.android


Contents

  For those using Google messages with RCS with iPhone owners... Marion <marion@facts.com> - 2025-07-02 04:15 +0000
    Re: For those using Google messages with RCS with iPhone owners... Andy Burns <usenet@andyburns.uk> - 2025-07-02 08:02 +0100
      Re: For those using Google messages with RCS with iPhone owners... "Carlos E.R." <robin_listas@es.invalid> - 2025-07-02 12:45 +0200
        Re: For those using Google messages with RCS with iPhone owners... Marion <marion@facts.com> - 2025-07-02 17:41 +0000
        Re: For those using Google messages with RCS with iPhone owners... Stan Brown <someone@example.com> - 2025-07-05 08:59 -0700
          Re: For those using Google messages with RCS with iPhone owners... "Carlos E.R." <robin_listas@es.invalid> - 2025-07-05 20:04 +0200
      Re: For those using Google messages with RCS with iPhone owners... "s|b" <me@privacy.invalid> - 2025-07-02 16:11 +0200
        Re: For those using Google messages with RCS with iPhone owners... Yusuf Khan <yusuf.khan.nospam@ptcl.net.pk> - 2025-07-02 22:43 +0500
          Re: For those using Google messages with RCS with iPhone owners... "Carlos E.R." <robin_listas@es.invalid> - 2025-07-02 20:16 +0200
            Re: For those using Google messages with RCS with iPhone owners... Yusuf Khan <yusuf.khan.nospam@ptcl.net.pk> - 2025-07-03 00:04 +0500
              Re: For those using Google messages with RCS with iPhone owners... "Carlos E.R." <robin_listas@es.invalid> - 2025-07-02 22:57 +0200
                Re: For those using Google messages with RCS with iPhone owners... "Carlos E.R." <robin_listas@es.invalid> - 2025-07-03 00:18 +0200
              Re: For those using Google messages with RCS with iPhone owners... Arno Welzel <usenet@arnowelzel.de> - 2025-07-03 17:36 +0200
          Re: For those using Google messages with RCS with iPhone owners... Andy Burns <usenet@andyburns.uk> - 2025-07-03 00:17 +0100
          Re: For those using Google messages with RCS with iPhone owners... Arno Welzel <usenet@arnowelzel.de> - 2025-07-03 17:33 +0200
      Re: For those using Google messages with RCS with iPhone owners... Arno Welzel <usenet@arnowelzel.de> - 2025-07-03 17:29 +0200
        Re: For those using Google messages with RCS with iPhone owners... Arno Welzel <usenet@arnowelzel.de> - 2025-07-03 17:30 +0200
          Re: For those using Google messages with RCS with iPhone owners... "Carlos E.R." <robin_listas@es.invalid> - 2025-07-03 20:08 +0200
            Re: For those using Google messages with RCS with iPhone owners... Frank Slootweg <this@ddress.is.invalid> - 2025-07-03 19:42 +0000
              Re: For those using Google messages with RCS with iPhone owners... micky <NONONOmisc07@fmguy.com> - 2025-07-03 21:23 -0400
              Re: For those using Google messages with RCS with iPhone owners... Arno Welzel <usenet@arnowelzel.de> - 2025-07-06 12:58 +0200
          Re: For those using Google messages with RCS with iPhone owners... "s|b" <me@privacy.invalid> - 2025-07-04 16:12 +0200
            Re: For those using Google messages with RCS with iPhone owners... Arno Welzel <usenet@arnowelzel.de> - 2025-07-06 12:59 +0200
              Re: For those using Google messages with RCS with iPhone owners... Marion <marion@facts.com> - 2025-07-06 13:52 +0000
              Re: For those using Google messages with RCS with iPhone owners... "s|b" <me@privacy.invalid> - 2025-07-06 19:46 +0200
                Re: For those using Google messages with RCS with iPhone owners... Arno Welzel <usenet@arnowelzel.de> - 2025-07-07 13:28 +0200
                  Re: For those using Google messages with RCS with iPhone owners... Marion <marion@facts.com> - 2025-07-07 14:18 +0000
                    Re: For those using Google messages with RCS with iPhone owners... Andy Burns <usenet@andyburns.uk> - 2025-07-07 15:27 +0100

Page 1 of 2  [1] 2  Next page →


#149489 — For those using Google messages with RCS with iPhone owners...

FromMarion <marion@facts.com>
Date2025-07-02 04:15 +0000
SubjectFor those using Google messages with RCS with iPhone owners...
Message-ID<1042bom$28bd$1@nnrp.usenet.blueworldhosting.com>
Is this of any interest to you?
https://www.androidauthority.com/google-messages-edit-messages-sent-to-iphones-3573055/

Google is finally starting to roll out the ability for Android users to
edit RCS messages sent to iPhones, a feature previously unavailable
cross-platform.

Made possible by the new Universal Profile 3.0 specification, users can
long-press a sent message to edit and resend it within a 15-minute window.

The feature is in limited testing and isn't perfect yet, as edited texts
currently appear as a new message on iPhones and iPhones can't edit
messages sent to Android devices.

[toc] | [next] | [standalone]


#149495

FromAndy Burns <usenet@andyburns.uk>
Date2025-07-02 08:02 +0100
Message-ID<mck3rmFd2etU2@mid.individual.net>
In reply to#149489
Marion wrote:

> https://www.androidauthority.com/google-messages-edit-messages-sent-to-iphones-3573055/
> 
> Google is finally starting to roll out the ability for Android users to
> edit RCS messages sent to iPhones, a feature previously unavailable
> cross-platform.
Editing or rescinding *anything* after pressing send is a do-not-want 
feature in any messaging/email app ...

[toc] | [prev] | [next] | [standalone]


#149509

From"Carlos E.R." <robin_listas@es.invalid>
Date2025-07-02 12:45 +0200
Message-ID<28ffjlxhuu.ln2@Telcontar.valinor>
In reply to#149495
On 2025-07-02 09:02, Andy Burns wrote:
> Marion wrote:
> 
>> https://www.androidauthority.com/google-messages-edit-messages-sent- 
>> to-iphones-3573055/
>>
>> Google is finally starting to roll out the ability for Android users to
>> edit RCS messages sent to iPhones, a feature previously unavailable
>> cross-platform.
> Editing or rescinding *anything* after pressing send is a do-not-want 
> feature in any messaging/email app ...
> 

Arguably it is better to edit a typo than sending another post with the 
correction. But the app should warn the recipient that the post has been 
edited, and maybe mark the edit.

-- 
Cheers, Carlos.

[toc] | [prev] | [next] | [standalone]


#149529

FromMarion <marion@facts.com>
Date2025-07-02 17:41 +0000
Message-ID<1043r0h$2st2$1@nnrp.usenet.blueworldhosting.com>
In reply to#149509
On Wed, 2 Jul 2025 12:45:54 +0200, Carlos E.R. wrote :


>>> https://www.androidauthority.com/google-messages-edit-messages-sent- 
>>> to-iphones-3573055/
>>>
>>> Google is finally starting to roll out the ability for Android users to
>>> edit RCS messages sent to iPhones, a feature previously unavailable
>>> cross-platform.
>> Editing or rescinding *anything* after pressing send is a do-not-want 
>> feature in any messaging/email app ...
>> 
> 
> Arguably it is better to edit a typo than sending another post with the 
> correction. But the app should warn the recipient that the post has been 
> edited, and maybe mark the edit.

I will agree with anyone who makes a logical argument, where I'm agreeing
with both s|b and Carlos in this case, where I think it's a useful feature.

You're the one SENDING the text.
Why can't YOU edit it (for a short while).

We've had this in Google Mail for many years now, haven't we?
It's useful. Very useful.

Of course, if the other person already RECEIVED (and read) the message, and
perhaps even started RESPONDING to that message, then we may have an issue.

But I'd rather fix a typo any day of the weak...
... week...

:)

[toc] | [prev] | [next] | [standalone]


#149626

FromStan Brown <someone@example.com>
Date2025-07-05 08:59 -0700
Message-ID<MPG.42d2ebcaac83307b990418@news.individual.net>
In reply to#149509
On Wed, 2 Jul 2025 12:45:54 +0200, Carlos E.R. wrote:
> Arguably it is better to edit a typo than sending another post with the 
> correction. But the app should warn the recipient that the post has been 
> edited, and maybe mark the edit.
> 

The published article mentions that the "editing" is done by sending 
a new message, containing the entire original as corrected, with an 
asterisk at the top that (my words) the recipient is supposed to 
_guess_ means "here's version 2 of my message".

-- 
After using my real address in 37 years of Usenet articles,
I am now reluctantly posting a fake address because of the
large number of sites scraping Usenet articles without
permission and putting them on their own pretend forum sites.

[toc] | [prev] | [next] | [standalone]


#149631

From"Carlos E.R." <robin_listas@es.invalid>
Date2025-07-05 20:04 +0200
Message-ID<826ojlxe7s.ln2@Telcontar.valinor>
In reply to#149626
On 2025-07-05 17:59, Stan Brown wrote:
> On Wed, 2 Jul 2025 12:45:54 +0200, Carlos E.R. wrote:
>> Arguably it is better to edit a typo than sending another post with the
>> correction. But the app should warn the recipient that the post has been
>> edited, and maybe mark the edit.
>>
> 
> The published article mentions that the "editing" is done by sending
> a new message, containing the entire original as corrected, with an
> asterisk at the top that (my words) the recipient is supposed to
> _guess_ means "here's version 2 of my message".

Ok, I suppose that otherwise they would have to create a language for 
sending edits. Sending the message again is easier. The client software 
just has to recognize it as an edit and only display the latest version.

A rogue client software could send an edit an hour or a day later.

The client software might show the user both versions with a tap.

-- 
Cheers, Carlos.

[toc] | [prev] | [next] | [standalone]


#149515

From"s|b" <me@privacy.invalid>
Date2025-07-02 16:11 +0200
Message-ID<mckt0qFh743U2@mid.individual.net>
In reply to#149495
On Wed, 2 Jul 2025 08:02:08 +0100, Andy Burns wrote:

> Editing or rescinding *anything* after pressing send is a do-not-want 
> feature in any messaging/email app ...

Signal has this feature. It was quite useful when I mistakenly sent a
message to the wrong person and to correct typos.

-- 
s|b

[toc] | [prev] | [next] | [standalone]


#149530

FromYusuf Khan <yusuf.khan.nospam@ptcl.net.pk>
Date2025-07-02 22:43 +0500
Message-ID<1043r36$19egn$1@news.mixmin.net>
In reply to#149515
On Wed, 02 Jul 2025 16:11:38 +0200, s|b wrote:

>> Editing or rescinding *anything* after pressing send is a do-not-want 
>> feature in any messaging/email app ...
> 
> Signal has this feature. It was quite useful when I mistakenly sent a
> message to the wrong person and to correct typos.

My E-mail has it too I think.

[toc] | [prev] | [next] | [standalone]


#149534

From"Carlos E.R." <robin_listas@es.invalid>
Date2025-07-02 20:16 +0200
Message-ID<hk9gjlxfaq.ln2@Telcontar.valinor>
In reply to#149530
On 2025-07-02 19:43, Yusuf Khan wrote:
> On Wed, 02 Jul 2025 16:11:38 +0200, s|b wrote:
> 
>>> Editing or rescinding *anything* after pressing send is a do-not-want
>>> feature in any messaging/email app ...
>>
>> Signal has this feature. It was quite useful when I mistakenly sent a
>> message to the wrong person and to correct typos.
> 
> My E-mail has it too I think.

The only way to do this in email is to not send the email when the user 
clicks send, but wait. Once an email is actually sent, the recipient has 
a copy that can not be altered by the sender.

You might have an edit mail feature if both parties are using the same 
mail platform with complying (specific) client software.

-- 
Cheers, Carlos.

[toc] | [prev] | [next] | [standalone]


#149537

FromYusuf Khan <yusuf.khan.nospam@ptcl.net.pk>
Date2025-07-03 00:04 +0500
Message-ID<1043vsj$19lag$1@news.mixmin.net>
In reply to#149534
On Wed, 2 Jul 2025 20:16:17 +0200, Carlos E.R. wrote:

> On 2025-07-02 19:43, Yusuf Khan wrote:
>> On Wed, 02 Jul 2025 16:11:38 +0200, s|b wrote:
>> 
>>>> Editing or rescinding *anything* after pressing send is a do-not-want
>>>> feature in any messaging/email app ...
>>>
>>> Signal has this feature. It was quite useful when I mistakenly sent a
>>> message to the wrong person and to correct typos.
>> 
>> My E-mail has it too I think.
> 
> The only way to do this in email is to not send the email when the user 
> clicks send, but wait. Once an email is actually sent, the recipient has 
> a copy that can not be altered by the sender.
> 
> You might have an edit mail feature if both parties are using the same 
> mail platform with complying (specific) client software.

https://news.itsfoss.com/protonmail-undo-send/

[toc] | [prev] | [next] | [standalone]


#149540

From"Carlos E.R." <robin_listas@es.invalid>
Date2025-07-02 22:57 +0200
Message-ID<32jgjlx445.ln2@Telcontar.valinor>
In reply to#149537
On 2025-07-02 21:04, Yusuf Khan wrote:
> On Wed, 2 Jul 2025 20:16:17 +0200, Carlos E.R. wrote:
> 
>> On 2025-07-02 19:43, Yusuf Khan wrote:
>>> On Wed, 02 Jul 2025 16:11:38 +0200, s|b wrote:
>>>
>>>>> Editing or rescinding *anything* after pressing send is a do-not-want
>>>>> feature in any messaging/email app ...
>>>>
>>>> Signal has this feature. It was quite useful when I mistakenly sent a
>>>> message to the wrong person and to correct typos.
>>>
>>> My E-mail has it too I think.
>>
>> The only way to do this in email is to not send the email when the user
>> clicks send, but wait. Once an email is actually sent, the recipient has
>> a copy that can not be altered by the sender.
>>
>> You might have an edit mail feature if both parties are using the same
>> mail platform with complying (specific) client software.
> 
> https://news.itsfoss.com/protonmail-undo-send/

It does what I said: they delay the actual sending for 10 seconds, so 
during that time you can abort the operation. Once actually sent, you 
can not do anything to it.

-- 
Cheers, Carlos.

[toc] | [prev] | [next] | [standalone]


#149543

From"Carlos E.R." <robin_listas@es.invalid>
Date2025-07-03 00:18 +0200
Message-ID<jqngjlxtvq.ln2@Telcontar.valinor>
In reply to#149540
On 2025-07-02 23:17, Stefan Ram wrote:
> "Carlos E.R." <robin_listas@es.invalid> wrote or quoted:
>> It does what I said: they delay the actual sending for 10 seconds, so
>> during that time you can abort the operation. Once actually sent, you
>> can not do anything to it.
> 
>    I used to have this account where, before I sent out a transfer,
>    I would double-check every single detail. I'd go over each digit,
>    line it up with the original, once from the start and once from the
>    end, then break it down into groups of three, then four. After
>    minutes of sweating it out, I'd finally hit "Submit Transfer!". -
>    Then this popped up: "You have entered the following information.
>    Please verify that all details are correct before proceeding.".
>    (Since I couldn't be sure the info on the screen actually matched
>    what I'd just checked, I'd have to start all over from scratch . . .)
> 
> 

I know that feeling.

-- 
Cheers, Carlos.

[toc] | [prev] | [next] | [standalone]


#149572

FromArno Welzel <usenet@arnowelzel.de>
Date2025-07-03 17:36 +0200
Message-ID<mcnmavFnbiU7@mid.individual.net>
In reply to#149537
Yusuf Khan, 2025-07-02 21:04:

> On Wed, 2 Jul 2025 20:16:17 +0200, Carlos E.R. wrote:
> 
>> On 2025-07-02 19:43, Yusuf Khan wrote:
>>> On Wed, 02 Jul 2025 16:11:38 +0200, s|b wrote:
>>>
>>>>> Editing or rescinding *anything* after pressing send is a do-not-want
>>>>> feature in any messaging/email app ...
>>>>
>>>> Signal has this feature. It was quite useful when I mistakenly sent a
>>>> message to the wrong person and to correct typos.
>>>
>>> My E-mail has it too I think.
>>
>> The only way to do this in email is to not send the email when the user 
>> clicks send, but wait. Once an email is actually sent, the recipient has 
>> a copy that can not be altered by the sender.
>>
>> You might have an edit mail feature if both parties are using the same 
>> mail platform with complying (specific) client software.
> 
> https://news.itsfoss.com/protonmail-undo-send/

This is not "undo" - it only allows to stop the transmission if you
accidentally hit the "send" button, quote:

"You don’t need to explicitly change settings to enable this feature.
Undo Send is automatically enabled for all ProtonMail users with a
default timer delay of 10 seconds.

When you hit the send button, you’ll see an “undo” button and if you hit
it, the email will not be sent and the composer window will reopen. You
can make the changes and send the edited mail again."

But if you finally sent the e-mail, it's done. You can not "undo" that.


-- 
Arno Welzel
https://arnowelzel.de

[toc] | [prev] | [next] | [standalone]


#149544

FromAndy Burns <usenet@andyburns.uk>
Date2025-07-03 00:17 +0100
Message-ID<mclt0mFm865U1@mid.individual.net>
In reply to#149530
Yusuf Khan wrote:

> s|b wrote:
> 
>> Signal has this feature. It was quite useful when I mistakenly sent a
>> message to the wrong person and to correct typos.
> 
> My E-mail has it too I think.

Microsoft thinks that their email has it (it does if both the sender and 
receiver use microsoft) but if the receiver uses a real email system 
then how is the unwanted message getting recalled?

[toc] | [prev] | [next] | [standalone]


#149571

FromArno Welzel <usenet@arnowelzel.de>
Date2025-07-03 17:33 +0200
Message-ID<mcnm68FnbiU6@mid.individual.net>
In reply to#149530
Yusuf Khan, 2025-07-02 19:43:

> On Wed, 02 Jul 2025 16:11:38 +0200, s|b wrote:
> 
>>> Editing or rescinding *anything* after pressing send is a do-not-want 
>>> feature in any messaging/email app ...
>>
>> Signal has this feature. It was quite useful when I mistakenly sent a
>> message to the wrong person and to correct typos.
> 
> My E-mail has it too I think.

E-mail itself - no.

An e-mail which was sent *and* fetched from the mailbox by the recipient
can not be changed. This is not implemented in SMTP. But some
proprietary solutions like Microsoft Outlook support revoking sent
messages when you use their proprietary infrastructure - but the both
the sender and recipient have to be in the same infrastructure then.

-- 
Arno Welzel
https://arnowelzel.de

[toc] | [prev] | [next] | [standalone]


#149569

FromArno Welzel <usenet@arnowelzel.de>
Date2025-07-03 17:29 +0200
Message-ID<mcnlv5FnbiU4@mid.individual.net>
In reply to#149495
Andy Burns, 2025-07-02 09:02:

> Marion wrote:
> 
>> https://www.androidauthority.com/google-messages-edit-messages-sent-to-iphones-3573055/
>>
>> Google is finally starting to roll out the ability for Android users to
>> edit RCS messages sent to iPhones, a feature previously unavailable
>> cross-platform.
> Editing or rescinding *anything* after pressing send is a do-not-want 
> feature in any messaging/email app ...

So upditing a tipo is not wanted?


-- 
Arno Welzel
https://arnowelzel.de

[toc] | [prev] | [next] | [standalone]


#149570

FromArno Welzel <usenet@arnowelzel.de>
Date2025-07-03 17:30 +0200
Message-ID<mcnm0kFnbiU5@mid.individual.net>
In reply to#149569
Arno Welzel, 2025-07-03 17:29:

> Andy Burns, 2025-07-02 09:02:
> 
>> Marion wrote:
>>
>>> https://www.androidauthority.com/google-messages-edit-messages-sent-to-iphones-3573055/
>>>
>>> Google is finally starting to roll out the ability for Android users to
>>> edit RCS messages sent to iPhones, a feature previously unavailable
>>> cross-platform.
>> Editing or rescinding *anything* after pressing send is a do-not-want 
>> feature in any messaging/email app ...
> 
> So upditing a tipo is not wanted?

So updating a typo is not wanted? Instead it is better to re-send the
same message again?


-- 
Arno Welzel
https://arnowelzel.de

[toc] | [prev] | [next] | [standalone]


#149577

From"Carlos E.R." <robin_listas@es.invalid>
Date2025-07-03 20:08 +0200
Message-ID<bitijlx3h.ln2@Telcontar.valinor>
In reply to#149570
On 2025-07-03 17:30, Arno Welzel wrote:
> Arno Welzel, 2025-07-03 17:29:
> 
>> Andy Burns, 2025-07-02 09:02:
>>
>>> Marion wrote:
>>>
>>>> https://www.androidauthority.com/google-messages-edit-messages-sent-to-iphones-3573055/
>>>>
>>>> Google is finally starting to roll out the ability for Android users to
>>>> edit RCS messages sent to iPhones, a feature previously unavailable
>>>> cross-platform.
>>> Editing or rescinding *anything* after pressing send is a do-not-want
>>> feature in any messaging/email app ...
>>
>> So upditing a tipo is not wanted?
> 
> So updating a typo is not wanted? Instead it is better to re-send the
> same message again?

X'-D

upditing actually exists, I googled :-D

-- 
Cheers, Carlos.

[toc] | [prev] | [next] | [standalone]


#149584

FromFrank Slootweg <this@ddress.is.invalid>
Date2025-07-03 19:42 +0000
Message-ID<1046tge.7gk.1@ID-201911.user.individual.net>
In reply to#149577
Carlos E.R. <robin_listas@es.invalid> wrote:
> On 2025-07-03 17:30, Arno Welzel wrote:
> > Arno Welzel, 2025-07-03 17:29:
> > 
> >> Andy Burns, 2025-07-02 09:02:
> >>
> >>> Marion wrote:
> >>>
> >>>> https://www.androidauthority.com/google-messages-edit-messages-sent-to-iphones-3573055/
> >>>>
> >>>> Google is finally starting to roll out the ability for Android users to
> >>>> edit RCS messages sent to iPhones, a feature previously unavailable
> >>>> cross-platform.
> >>> Editing or rescinding *anything* after pressing send is a do-not-want
> >>> feature in any messaging/email app ...
> >>
> >> So upditing a tipo is not wanted?
> > 
> > So updating a typo is not wanted? Instead it is better to re-send the
> > same message again?
> 
> X'-D
> 
> upditing actually exists, I googled :-D

  Even better: Googling 'upditing' gives results without an AI summary.
Way to make AI shut up! :-)

  Also: Google Translate (English to Dutch) gives the same result for
'updating' and 'upditing' (no, it doesn't say "Did you nean: updating").

  So 'upditing' it is!

[toc] | [prev] | [next] | [standalone]


#149596

Frommicky <NONONOmisc07@fmguy.com>
Date2025-07-03 21:23 -0400
Message-ID<07be6kp70se0andlle87j795jj0f90db71@4ax.com>
In reply to#149584
In comp.mobile.android, on 3 Jul 2025 19:42:44 GMT, Frank Slootweg
<this@ddress.is.invalid> wrote:

>Carlos E.R. <robin_listas@es.invalid> wrote:
>> On 2025-07-03 17:30, Arno Welzel wrote:
>> > Arno Welzel, 2025-07-03 17:29:
>> > 
>> >> Andy Burns, 2025-07-02 09:02:
>> >>
>> >>> Marion wrote:
>> >>>
>> >>>> https://www.androidauthority.com/google-messages-edit-messages-sent-to-iphones-3573055/
>> >>>>
>> >>>> Google is finally starting to roll out the ability for Android users to
>> >>>> edit RCS messages sent to iPhones, a feature previously unavailable
>> >>>> cross-platform.
>> >>> Editing or rescinding *anything* after pressing send is a do-not-want
>> >>> feature in any messaging/email app ...
>> >>
>> >> So upditing a tipo is not wanted?
>> > 
>> > So updating a typo is not wanted? Instead it is better to re-send the
>> > same message again?
>> 
>> X'-D
>> 
>> upditing actually exists, I googled :-D
>
>  Even better: Googling 'upditing' gives results without an AI summary.
>Way to make AI shut up! :-)
>
>  Also: Google Translate (English to Dutch) gives the same result for
>'updating' and 'upditing' (no, it doesn't say "Did you nean: updating").
>
>  So 'upditing' it is!

I thought upditing was diting a girl who made more money than I did. 

[toc] | [prev] | [next] | [standalone]


Page 1 of 2  [1] 2  Next page →

Back to top | Article view | comp.mobile.android


csiph-web