Status Update
No update yet.
Comments
jo...@gmail.com
Information redacted by Android Beta Feedback.
ba...@google.com
ba...@google.com
Thank you for reporting this issue. For us to further investigate this issue, please provide the following additional information:
Please upgrade to the latest release from the link
cf...@gmail.com
cf...@gmail.com
Thank you for reporting this issue. We have shared this with our product and engineering team and will update this issue with more information as it becomes available.
jo...@ynstein.net
Thanks for reporting this issue.
-
We are handling "No more paying via Wallet because the system is not up to date" wallet issue here.
-
Please file a separate ticket for "Upgrade was never offered to install android 16" with details.
je...@gmail.com
After upgrading to stable the issue persists.
pa...@gmail.com
em...@gmail.com
bv...@gmail.com
ma...@gmail.com
Me: *sigh*
If it works in India now and it worked everywhere in January, it should be widely released, or least put into a current beta. I'm a big proponent of Android but I really can't defend this. Let's go!
al...@gmail.com
cb...@gmail.com
What
Feature request
Iv never been able to get this working
Where
Build and device data
- Build Number: google/husky_beta/husky:15/AP41.240823.009/12329489:user/release-keys
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)
- SoC Revision: Zuma B1
Debugging information
Google Play services
com.google.android.gms
Version 243934036 (24.39.34 (260408-683343373))
System App (Updated)
Android System WebView
com.google.android.webview
Version 666808133 (129.0.6668.81)
System App (Updated)
Network operator: TELUS
SIM operator: TELUS
Filed by Android Beta Feedback. Version (Updated): 2.45-betterbug.external_20240829_RC01 (DOGFOOD)
To learn more about our feedback process, please visit
zl...@gmail.com
rz...@gmail.com
me...@gmail.com
da...@gmail.com
he...@outlook.com
It is honestly embarassing that Google has been publically screaming for Apple to support RCS years. And then, finally, when iOS does support RCS, Apple chose to support the RCS standard better than Google: Enabling RCS out-of-the-box on iOS without any user input needed, vowing to implement E2EE natively through the RCS standardization body instead of creating its own proprietary encryption layer on top of standard RCS like Google did, supporting high-res images without insane compression as default option, dual sim support, and much, much more. I am embarrassed to have witnessed this.
I need dual-sim RCS, and have been missing out for many years now, because I (for some reason) opt to use Android over iOS.
se...@gmail.com
After having RCS Dual SIM once in the past on Samsung - changing to iPhone 15 plus - having RCS on physical and eSIM with just on turning on one switch
Changing to Pixel 9 Pro XL ( the mother of all RCS, i thought ) only one card for RCS available....
Seriously Google - you need to hurry up. If WhatsApp will drop Usernames before you can use a public number and private number with rcs in one device....
It will be the next Message App with no future by Google....
al...@gmail.com
Now the ball is with Google's hands to make RCS working as expected.
NB - Make your support available for people from Asia, not just western countries. When I say support, not robots, real people.
6o...@gmail.com
What
Feature request
!
Where
Build and device data
- Build Number: google/akita_beta/akita:15/AP41.240925.009/12534705:user/release-keys
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)
Debugging information
Google Play services
com.google.android.gms
Version 244232035 (24.42.32 (260400-688217902))
System App (Updated)
Android System WebView
com.google.android.webview
Version 666810233 (129.0.6668.102)
System App (Updated)
Network operator: Not available
SIM operator: T-Mobile
Filed by Android Beta Feedback. Version (Updated): 2.45-betterbug.external_20240829_RC01 (DOGFOOD)
To learn more about our feedback process, please visit
an...@gmail.com
I have dual SIM RCS now, just did a factory reset today on my Pixel 8 Pro to quit the Android 15 QPR beta and go back to stable.
I'm using the beta branch of Messages, version is messages.android_20241018_01_RC00.phone.openbeta_dynamic com.google.android.apps.messaging
ne...@gmail.com
What
Feature request
Please we need that feature to come again 🙏
Where
Build and device data
- Build Number: google/bluejay_beta/bluejay:15/AP41.240925.009/12534705:user/release-keys
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)
Debugging information
Google Play services
com.google.android.gms
Version 244233035 (24.42.33 (260400-689790151))
System App (Updated)
Android System WebView
com.google.android.webview
Version 666810033 (129.0.6668.100)
System App (Updated)
Network operator: Vodacom
SIM operator: Vodacom
Network operator: TIGO
SIM operator: TIGO
Filed by Android Beta Feedback. Version (Updated): 2.45-betterbug.external_20240829_RC01 (DOGFOOD)
To learn more about our feedback process, please visit
yo...@gmail.com
replaying to
he...@outlook.com
I got dual sim RCS on my Pixel 8 Pro in Denmark on the Google Messages Beta!
According to Google's help page, it is not enough to opt-in to Google Messages Beta. Opting into the beta of Carrier Services (companion app) is also necessary:
Less than 24 hours after opting in to both betas and waiting for the latest beta updates (for both apps) to reach my phone, I got dual sim RCS :D
yo...@gmail.com
hallelujah! all right, angry mob. that's the ticket! opt-in to messages and carrier services betas, then some time later, dual-sim RCS will be made available. it's finally happening!
wi...@gmail.com
What
Feature request
Mi dispositivo dejo de reconocer mis sim y esim al momento de reiniciar mi dispositivo, es la primera vez que me pasa eso, estoy en la versión beta
Where
Build and device data
- Build Number: google/husky_beta/husky:15/AP41.240925.009/12534705:user/release-keys
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)
- SoC Revision: Zuma B1
Debugging information
Servicios de Google Play
com.google.android.gms
Version 244337036 (24.43.37 (260408-693941914))
System App (Updated)
Android System WebView
com.google.android.webview
Version 672308633 (130.0.6723.86)
System App (Updated)
Network operator: Not available
SIM operator: Altice
Filed by Android Beta Feedback. Version (Updated): 2.45-betterbug.external_20240829_RC01 (DOGFOOD)
To learn more about our feedback process, please visit
wi...@gmail.com
Information redacted by Android Beta Feedback.
br...@gmail.com
It seems the Google server is only switching these flags on if a certain combination of conditions are met (country, phone model, carrier), and the best we can do is to wait and hope.
... or root your phone and use ADB Shell / SQLite Editor to manually enable these settings
br...@gmail.com
fa...@gmail.com
night. Only two of my RCS messages have locks on them and all my other
Android users do not. When I went to log into my Samsung account on my
computer it is stating that the only available area codes are india,
Republic of korea, and China. I don't know if this is due to the fact that
I have switched he seems multiple times and then I started out with a
physical Sim. But still soon does not seem to work I have a Galaxy s23
On Sun, Dec 8, 2024, 7:56 PM <buganizer-system@google.com> wrote:
fa...@gmail.com
wo...@gmail.com
al...@gmail.com
ar...@gmail.com
What
More information
I have a similar issue as well. On my end I'm having trouble verifying even one.
Where
Build and device data
- Build Number: google/tokay_beta/tokay:15/BP11.241121.010/12780007:user/release-keys
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)
Debugging information
Google Play services
com.google.android.gms
Version 244961035 (24.49.61 (260400-705672791))
System App (Updated)
Android System WebView
com.google.android.webview
Version 683405642 (132.0.6834.56)
System App (Updated)
Network operator: Mobitel
SIM operator: Sri Lanka Telecom Mobitel
Network operator: Dialog
SIM operator: Dialog
Filed by Android Beta Feedback. Version (Updated): 2.46-betterbug.external_20241023_RC01 (DOGFOOD)
To learn more about our feedback process, please visit
ar...@gmail.com
Information redacted by Android Beta Feedback.
cw...@gmail.com
rj...@gmail.com
What
More information
This bugs coming out from someone who has duel esim card to my actual sim card. But I don't know who that person is.
Where
Build and device data
- Build Number: google/bluejay_beta/bluejay:15/BP11.241121.010/12780007:user/release-keys
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)
Debugging information
Google Play services
com.google.android.gms
Version 244738035 (24.47.38 (260400-705893532))
System App (Updated)
Android System WebView
com.google.android.webview
Version 677820033 (131.0.6778.200)
System App (Updated)
Network operator: Home
SIM operator: TFW
Filed by Android Beta Feedback. Version (Updated): 2.46-betterbug.external_20241023_RC01 (DOGFOOD)
To learn more about our feedback process, please visit
rj...@gmail.com
Information redacted by Android Beta Feedback.
Description
What
User experience
What type of Android issue is this?
Messaging
What steps would let us observe this issue?
What did you expect to happen?
That both numbers would work with RCS
What actually happened?
One is RCS while the other is always SMS/MMS
What was the effect of this issue on your device usage, such as lost time or work?
High
Additional comments
Now that iphone FINALLY has RCS support Android MUST step up quickly and fix this. I have my work number and personal number on one device (Pixel 9 pro) and I want to be able to send high resolution pictures and videos to using both numbers to everyone. I currently have to email or put my sim into a non android phone.
Please fix asap...
THANK YOU!
When
Time and frequency
When did this happen?
Sep 28, 2024 4:20 PM GMT-04:00
How often has this happened?
Every time
Where
Component
Suggested component: <not visible> (1630575)
Build and device data
- Build Number: google/caiman_beta/caiman:15/AP41.240823.009/12329489:user/release-keys
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)
Debugging information
Google Play services
com.google.android.gms
Version 243734030 (24.37.34 (190408-679256246))
System App (Updated)
Android System WebView
com.google.android.webview
Version 661314633 (128.0.6613.146)
System App (Updated)
Network operator: FirstNet
SIM operator: FirstNet
Network operator: US Mobile
SIM operator: Verizon
Filed by Android Beta Feedback. Version (Updated): 2.45-betterbug.external_20240829_RC01 (DOGFOOD)https://developer.android.com/preview/feedback#feedback-app .
To learn more about our feedback process, please visit