I found that giving messages, and carrier location permission fixed the RCS problem for me Pixel 9
OfflinePuffin
- Joined Apr 16, 2024
Androids go Beep boop... The RCS guy on the forum
A bug in Google Message maybe cause if you right carefully the two megathread there is for RCS there is no mention of messing with Google messages permissions
I just had RCS stop working recently. I tried going through the initial setup steps again, but it didn't work. I then tried to uninstall Google Messages and unregistered my number here:
https://messages.google.com/disable-chat
Then I rebooted my phone and reinstalled Google Messages on cellular data (not WiFi, if that makes a difference). I already had given Google Play Services permission to read my device identifier and have Carrier Services installed. Within a few minutes of opening the app, Google Messages registered itself for RCS! I am not signed into any Google account on my device or in Google Messages.
- In Mascot
Like Clippy, but a graphene molecule instead of a paperclip.
DirtyDan mine is still working from a few months ago
OfflinePuffin It's not particularly user facing but is a prerequisite to start making it into a better app.
Linuxx If I completely disable USB function and use wireless charging, would that make the phone the safest it can be?"
I don't know how wireless charging works, but I believe it includes negotiation for various rates. If so, in theory, that communication channel might have an exploitable implementation on the device.
Novastatic Have you tried temporarily installing the official Google app and giving it the same permissions? There was some speculation on this thread that the app included some config stuff and needs to be installed beforehand. You may have to repeat all the steps you mentioned. But first, try the following things:
Have you assigned the necessary permissions to play services and Google messages? Minimum should be network, SMS, notifications, and phone (I think) - contacts or contacts scope for ease of use. If you do install the Google app afterwards, apply the same permissions.
When you changed the device identifiers permission using adb/app opps, did you make sure to do it for both Google Messages AND Play services? (I think this is probably what caused it).
Another shot in the dark: In the Google messages app, go to settings -> Advanced -> change it from unknown to to your number.
Also, restarting your phone is also a way to see if the changes worked.
Also, should RCS start working, you should be able to uninstall the Google app and app opps (if you used them) with RCS still working.
Twice now after GrapheneOS updates, I lost the ability to send Google messages thru my laptop unless my phone was unlocked & had Google Messages open. Definitely an irritation..
I thought GOS updates were rolling back functionality, but after resolving the issue just now, I now believe that after GrapheneOS finishes 'optimizing apps' post-update, the phone just needs an additional reboot for Google Messages to work as expected.
Sharing this in case it saves someone from similar frustration.
- Edited
Been waiting for this update for a while. Already using fingerprint unlock plus pin, and loving it.
- Edited
Our 2-factor fingerprint unlock feature is now fully implemented and will be available in the upcoming GrapheneOS release. This adds the option to set a PIN for using fingerprint unlock. You can use a strong diceware passphrase as the primary unlock method with fingerprint+PIN secondary unlock.
The usual restrictions on fingerprint unlock still apply. It's a secondary unlock mechanism only usable for 48 hours after the last primary unlock. The limit on failed fingerprint unlock attempts in GrapheneOS is 5 as opposed to allowing 4 batches of 5 attempts (20 total) with 30s delays in between.
The devices we support have a high quality secure element heavily throttling unlock attempts which is why a random 6 digit PIN provides secure encryption, unlike most Android devices. It's nicer to have a strong passphrase not depending on an attacker never being able to exploit the secure element.
Our new 2-factor fingerprint unlock feature means you can get this benefit of a strong passphrase while still having the convenience of a PIN. Since our PIN scrambling feature works with the 2nd factor PIN, you get the combined anti-shoulder-surfing benefits of a scrambled PIN and a fingerprint.
If you want to avoid entering your passphrase in public, you just need to make sure to refresh the 48 hour timer after last using it to unlock to keep fingerprint unlock available. We plan to add configuration for how many failed fingerprint unlock attempts are allowed to help with this use case.
We came up with the concept for this 2-factor fingerprint unlock feature in 2015 and filed it in the public issue tracker in 2016. This was extremely difficult to implement correctly and we needed to fix multiple upstream Android bugs. The lockscreen will be more robust even if you don't use this.
This is now one of the flagship features of GrapheneOS alongside hardened_malloc, hardware memory tagging, hardware-level disabling of the USB-C port, Storage Scopes, Contact Scopes, sandboxed Google Play compatibility layer, etc. It will be harder to port to new versions than our existing features.
Our duress PIN/password feature is fully compatible with our 2-factor fingerprint unlock and will near instantly wipe the device as usual if you enter the duress PIN instead of the correct 2nd factor PIN for fingerprint unlock. See https://grapheneos.org/features#duress for more details on that feature.
This post is also available on social media platforms:
https://grapheneos.social/@GrapheneOS/113738455998741928
https://bsky.app/profile/grapheneos.org/post/3lehzq3i3d22z
https://x.com/GrapheneOS/status/1873496781373497667- Edited
I don't have it installed, and no desire to reinstall it.
It's available for android and iOS, and needs both Android and iOS users to have it installed in Japan because RCS hasn't been activated by the carriers (for IOS) here in Japan outside of this app.
It won't send to people on google messages, either.- Edited
henryfbp "The Google API is insecure"
No, Googles attestation being insecure is not why GOS cannot pass said attestation, its because its not authenticated to do so.
GOS cannot pass Play Integrity API as GOS isn't authenticated to do so by Google. They would need to whitelist GOS or make an API that doesn't require approval from Google.
Its fully Googles choice and there is a good chance they will never allow GOS to pass the Play Integrity API
OfflinePuffin Yep! It's clunky, and only (as far as I can tell) available on Japanese app stores...
- Edited
CrabPerson Define 'deannonymize',
Are you talking about someone who is able to be queried in exact location based on IMEI via LE? Then assuming they have the IMEI it would be easy to triangulate based on cell signal.
Are you talking about Joe Normal Guy trying to find personal data? Then its fully dependent on what you share online and where. Not much about that will be effected by being logged into Google or using a SIM card without a name to it.
Are you talking about Google trying to query a user? Then its going to be based on what applications you run by Google and what information might be taken from that.
Cybersec and Opsec are not black and white 'you are protected now'/'you aren't protected now' things, nor is GOS a magic wizard that makes your phone instantly unhackable and all personal data ever online about you is gone. Its deciding who you want access to what and how to enforce that. What risks are you willing to take? Who do you trust? What do you need in your life and what information are you willing to give away for it?
OfflinePuffin We do have that app in Japan, but each person needs to have it installed, and even then it's not the most reliable.
If this helps anyone, I got RCS to work by turning off WiFi and using only cell data (I use T-Mobile btw), then make sure you turn off your vpn on your phone if you are using one. Then you can go to Message Settings > RCS Chats, and you'll see that it's connecting.
Other than that, I installed Play Services., Play Store, and Carrier Services with access to Network, SMS, and Phone enabled. I assume you don't need some of these permissions enabled but this worked for me.
- In Pixel laptop
Everything would depend on the price, but it would be interesting to have a GrapheneOS laptop.
I did, yes. Although some of the Play Services permissions were already in place so I could get google wallet to work (for Ticketmaster events, not payments)
