GrapheneOS version 2025092700 released

Boss777

Hello here! Sorry to bother you again with my 7 Pro updates troubles ;). Now it's all bad. After update and reboot and app optimisation finished I left the phone on the wireless charger. I forgot that it will not wirelessly charge after the update, so it got fully discharged. I plugged in the cable and left it for the night. Now I cannot turn it on. The screen is black, but the phone is probably alive. Long press on the power button produces one haptic feedback. Plugging the charger makes usual sound. But nothing else. It is not connected to wifi, connecting USB to a computer doesn't show any USB device.
Is there any way to "reset it" not in a sense of re-flashing, but fully power off without screen controls?

yore

Boss777 It's best to leave it plugged in for a couple of hours and then try using it. If for some reason the OS is booted but there's no input, you can hold the power button for 30 seconds to do a hard shutdown

W1zardK1ng

Boss777 connect the charger, press power button while phone is starting to pause the boot process. Leave the phone like that for sometimes. Resume the boot by pressing the power button again. Phone should start like normal.

Boss777

yore This was the state after spending a night on the wire charger. The hard shutdown keys are Power+Volume UP, so I did and it has rebooted in the working state.

lcalamar

GrapheneOS Would that mean a new release for that? (I've repeated all the steps several times - an still can't get RCS to work).

I wonder if using Google FI as a carrier is causing issues? (maybe that's the subset?0

GrapheneOS

skorge

lcalamar I dont think the carrier is the issue, I'm on Mint and having the same issues after following all the steps. Multiple people on Mint, Verizon and AT&T have said it doesn't connect to RCS for them either

lcalamar

GrapheneOS When I go into the phone app permissions I don't see anything specific for play services?

Here is what I've checked:

Play services, app permissions - phone is allowed
Google Messages, app permissions - phone is allowed
Google FI, app permissions - phone is allowed
Phone, app permissions

Am I ok on Permissions?

lcalamar

skorge Ah- I see. I guess it is good to know 'it isn't me!"

Saint

I'm on Verizon. RCS setup still says "Connecting". If I touch the little ⓘ symbol, it says, "RCS is provided by your mobile carrier under their terms of service". Despite it still saying "Connecting", it seems to be working. I'm not positive though. When it worked in the past it said something else. I just can't remember what it was.

GrapheneOS

Carrier Services does not appear to be required by Google Messages for RCS and we recommend uninstalling it. We've determined that there's likely another sandboxed Google Play workaround require which will potentially require a toggle for granting special access to use RCS.

GrapheneOS

It also doesn't appear to matter how Google Messages is installed, although we recommend using the sandboxed Play Store to make sure it gets installed properly.

ntop

Logs as below

type: logcat
buffers: main,system,crash,events,kernel
level: verbose
filterRegex: Barclay

--------- beginning of main
09-30 03:04:23.165 10123  3055  3055 D AlphabeticalAppsList: addAppsWithSections: adding sectionName: B with appInfoTitle: Barclaycard
09-30 03:04:23.166 10123  3055  3055 D AlphabeticalAppsList: addAppsWithSections: adding sectionName: B with appInfoTitle: Barclaycard
09-30 03:57:07.571 10123  3055  3055 D AlphabeticalAppsList: addAppsWithSections: adding sectionName: B with appInfoTitle: Barclaycard
09-30 03:57:07.572 10123  3055  3055 D AlphabeticalAppsList: addAppsWithSections: adding sectionName: B with appInfoTitle: Barclaycard
09-30 03:57:10.895 10123  3055  3055 D AlphabeticalAppsList: addAppsWithSections: adding sectionName: B with appInfoTitle: Barclaycard
09-30 03:57:10.896 10123  3055  3055 D AlphabeticalAppsList: addAppsWithSections: adding sectionName: B with appInfoTitle: Barclaycard
09-30 03:58:59.207 10045 14651 14651 D LogcatActivity: command: logcat --buffer=main,system,crash,events,kernel -d --dividers --format=UTC,printable,uid,descriptive --regex=Barclay *:V

Anyone can assist would be greatly appreciate

Barclay's are not helpful at all.

Volen

ntop

Having the same issue with the Barclaycard app.

It might make sense to reinstall the previous version to narrow down - it might be due to recent app update.

ETA

skorge

Make sure google account is connected to phone number and phone number verification is enabled.
Give google place services phone permission as mentioned with the GOS update.
Download google msgs and connect to rcs.

This worked for me

EDIT: I should add that it took 5 min to connect and verify my number

mousetrapreplica

ETA

ETA have you verified that you're sending RCS messages to other phones? Many users have received the RCS "verified" indicator but still had Messages only send SMS.

Shrunk836

It says RCS connected after giving play services the sms permissions... But how can I check of it actually works? Sending myself a sms didn't activate a RCS chat.

ETA

mousetrapreplica Good question. I have not sent a rcs msg yet. I am not too sure if anyone else in my contacts uses it. I'll have to test it out over the weekend

underhand

mousetrapreplica

I just wanted to add to this. I already had RCS working prior to Google recently breaking it. Even when it broke, my RCS status has always shown "connected," but all RCS attempts fail back to SMS. Even now after the recent update, I can turn RCS off and back on again and it still shows as connected, but always fails back to SMS. So it's not just an issue for those who aren't able to connect, it's also an issue for at least some who show as already connected. Happy to provide any additional detail necessary.

HecticHector

Phone calls are not being received 80% of the time. To receive calls I have to toggle off then on the sim.

GrapheneOS

HecticHector That's likely an issue with your carrier. You should start by resetting cellular settings via Settings > System > Reset.

Boss777

The strange power consumption after each upgrade continues. Now I was able to confirm that wireless charger actually charges the phone, but it just discharges faster ... It was oscillating between 40 and 43% of charge. Battery status menu showing 99% consumed by system applications with <1% by all others.
Is it a kind of special battery calibration mode?? It seems that after 2 full charges : 1st up to 100% regardless of my battery limit setting and 2nd to 83% it kind of calms down. Will see during today. But this "feature" should be documented at least... Getting out and seeing battery level melting as a spring snow is kind of stressful.

GrapheneOS

Boss777 There's no such thing. This is caused by your apps or network, unless you're talking about the post-boot optimizing apps needing a lot of CPU until it's done, but it saves CPU later since it's already compiled.

Boss777

GrapheneOS Optimizing apps process is visible with notification and that also says when it's complete. It takes some time but what I am talking about lasts for couple of days. Like full charge, discharge, another full charge. I don't believe an app can ever detect the update and have a special behaviour about it. The network is always the same my home wifi and it's the 3rd or 4th update like this. Before, during first months of my GrapheneOS use, there was nothing like this.
It was not an intermittent glitch. The phone spent the whole day and night on the wireless charger in the same place as usual, on the same usual wifi network and was charging and discharging at the same time as I described. I have to put it on a wired charger, charge completely, and now it charges as usual on the wireless and the battery lasts for almost 2 days, while during the events I have described it got to 20% in half a day.

« Previous Page Next Page »