GrapheneOS version 2025073000 released

HecticHector

Pixel 8 Pro 🤌 No issues

cdflasdkesalkjfkdfkjsdajfd

Just updated (P7Pro) and rebooted.
It's normal that device showing the boot animation for 1:30-2 mins?
Finally boot sequence has ended, but never ocurrered this.

supersonic

cdflasdkesalkjfkdfkjsdajfd I had this experience as well, maybe about 3 minutes.

MartiMarto

Hello! Just installed it on my Pixel 6 Pro. I had the same weird behavior of the boot animation stuck for about 3 minutes (instead of the usual 10 seconds).

But the real problem is it doesn't charge anymore. It could just be a coincidence, but it was charging alright before the update and as soon as it was rebooted, charging stopped working. As soon as app optimization is finished, I'm going to shut it down, boot it back up, try to charge it and look at logs. I'll keep you updated. Please let me know if you know for sure that it isn't linked to the upgrade and I should just create a dedicated post on the forum.

other8026

MartiMarto Please let me know if you know for sure that it isn't linked to the upgrade and I should just create a dedicated post on the forum.

It doesn't sound related. We'd be getting a lot of reports if it was.

I'd try turning the phone completely off, leave it for several minutes, then power it on, and check again to see if it still won't charge.

GrapheneOS

MartiMarto

Hello! Just installed it on my Pixel 6 Pro. I had the same weird behavior of the boot animation stuck for about 3 minutes (instead of the usual 10 seconds).

That's expected unless you were already on 2025072700 or later which haven't gone to the Stable channel until 2025073000. It's covered in the 2025072700 release notes:

temporarily disable asynchronous pre-reboot OS update app optimization (dexopt) added in Android 16 to avoid the Finalizing step completing before apps are recompiled which can then result in it causing a very long initial boot of the new OS version if the user reboots before the background app optimization completes (this will not apply to updating to this release but rather only updating to future releases from this one and onwards)

Byku

GrapheneOS After the update (stable channel) apps can no longer use wireless debugging. It's like it is not detected at all. Pairing again won't work either. The usual schtick of rebooting or clearing app cache also doesn't work. It worked ok just before the update. I can still manually connect to wireless debugging via termux-adb command so it is there, just not accessible to apps for some reason.

Byku

Byku To clarify, the problem is with detecting the wireless debugging service once it's been paired. It is still possible to connect by manually typing the IP and to pair apps.

GrapheneOS

Byku Byku We didn't receive any reports of issues during the lengthy Alpha and Beta testing for the recent changes. Are you using a VPN with VPN lockdown enabled? Did you try in a profile without it?

nashgraph

Yeah it took a long time. I was a bit worried at some point.

Byku

GrapheneOS
I got same results with lockdown mode disabled.
When I disabled VPN completely I've managed to get one app to detect wireless debugging (Shizuku). The other app I've tried is Automate and it still failed to detect wireless ADB service throwing JavaScript internal error. So you're right that this behavior seems to be related to VPN. Maybe the new leak protections are interfering with discovering wireless debugging? I should mention that before the update all the apps could detect wireless debugging even when VPN with lockdown mode was running.

GrapheneOS

Byku Try connecting to it from another profile without a VPN.

AccJustForThat

Mh wtf, Update basically soft-bricked my device.

Phone got low on Power over night and the insane 3min+ bootloop drains faster than it charges ....

Slowly i start hating GrapheneOS for it's horrible Updates, no progression, User Apps sucks ass and Stuff Like 'Nightlight and extra Dimm' still has the Display issue after turning off. :/

I don't like these kind of instability and uncertainty .

other8026

AccJustForThat Update basically soft-bricked my device.

That's not what happened.

AccJustForThat Phone got low on Power over night and the insane 3min+ bootloop drains faster than it charges ....

When you see the notice that you're loading another OS, push the lock button to pause the boot process. Let the device charge for a while so it has enough battery.

AccJustForThat horrible Updates

The issue you're describing isn't about updates. It's that your device didn't have a full enough battery to do the update.

AccJustForThat no progression

Yes there is? Have you checked the release notes? There are improvements in every release.

AccJustForThat User Apps sucks ass

You can install other apps. The developers are working on improving them, but it takes time.

AccJustForThat Stuff Like 'Nightlight and extra Dimm' still has the Display issue after turning off. :/

These are known upstream bugs. Fixing them can take a lot of time and effort and maintaining those fixes would be even more effort. The bugs are easily worked around, but it's true they can be annoying for some people. I've found that toggling night light on and off can fix some of them.

AccJustForThat I don't like these kind of instability and uncertainty .

Updates that get to the stable channel are just that: stable. You're complaining here about something that is out of GrapheneOS's control, namely your device's battery charge level.

Quantum

AccJustForThat People have already answered you a month ago. Why are you still stuck on that?

For the bootloop just search the forum

other8026

I've had to remove a number of posts here.

I can understand that sometimes people run into issues and then they may be unhappy and want to complain about their experience. Keep in mind that some people spend a lot of money on their devices, and when unexpected things happen it can be pretty upsetting.

Please take the time to be understanding of people in these situations. If things get out of hand, a moderator may have to step in. Please flag offending posts in those situations. People can also feel free to ping @mods in the chat rooms if a situation needs more immediate attention.

Quantum

other8026 I get that soft bricking part. It's just that people already spent a bunch of time(mod included) a month ago explaining this to him(the other problems). That's why I replied in that manner.

other8026

Quantum It's just that people already spent a bunch of time(mod included) a month ago explaining this to him(the other problems).

Yeah, I checked post history after my first reply and saw that.

Quantum That's why I replied in that manner.

I can understand being frustrated, but considering the problem they experienced it makes sense that they were upset. I didn't like the tone either, but I hope that if the problem is addressed then we can all move on without further trouble.

Quantum

other8026 I'll leave it at that then

semi

I am still having the issue of the background being dimmed when switching from one profile to another, even though "Modes" is off. I need to turn Modes on and off again to make the background normal brightness. Issue began in version 2025070800. Pixel 6a.

Byku

GrapheneOS maybe I'm dumb, but how do I do that? I thought debugging only works on owner profile. I created a brand new profile without a VPN. I can't access developer options on that profile to pair an app via wireless debugging. The closest thing was copying Shizuku app from owner profile. However Shizuku only shows that it is running when started in owner profile. The only option in the new profile is to stop it. When I stop it there are no options to pair or start Shizuku from the new profile. I can't test Automate because I'd need a way to pair it first.

In owner profile I can get Shizuku to detect wireless debugging by turning always-on VPN off.

« Previous Page Next Page »