chfour Not sure I understand. Maybe what I wrote wasn't very clear. It sounds like what you were experiencing is a known issue. It hasn't been fixed in any releases yet, but I believe the fix will be in the next release.

So, in other words, the developers know about it (assuming it's the same issue).

And, yes, other people have fixed it by resetting their bluetooth settings, so I think it should work fine for you now.

    Skylight7009

    I have the same question. Being a privacy minded OS enabling 'block connections without VPN' is essential for added privacy.

    Right now, the VM is broken unless you disable that setting. Which basically makes this feature less useful. It may also be worth adding in the UI/UX to warn users to disable that as I only learned by reading earlier responses here to disable it.

        I'm not quite sure if it happens since this release or the previous one, but bypass (or at least the shield icon showing up) doesn't work @100% anymore.

        Still works @80%.

        Tried with two different chargers, one of them being the official model. Left it plugged @100 for extensive period of time. Will try again overnight.

        Ps: on a pixel 8 pro.

          Skylight7009 It will definitely be fixed in the future but we don't know if the fix will be in our next release.

          grapheneosuser294783 It's an experimental feature only available via developer options. No further warning is needed. Developer options are already warned against on a production device by us.

                GrapheneOS

                Thanks for your answer.
                I got so used seeing that shield running @80 limit I assumed it was there @100 aswell. Does it mean plugged @100 results in trickle charging ?

                    Canardo_Sanchez

                    Does it mean plugged @100 results in trickle charging ?

                    We don't know, we haven't specifically tested it. It doesn't display the shield UI without the limit toggle enabled outside of the special case deployed for the Pixel Tablet stand earlier where it stops at 90% which is a bit odd now. It interacts a bit strangely with the charge limit toggle such as it not being able to recalibrate until it's charged normally without the stand so it will start going to the 90% limit with the stand until it's charged another way.

                      I got a graphical glitch. When I ended an ongoing phonecall (by tapping the red phone button for ending the call), the active phone window closed correctly (like any other app), by doing the animation where it is descending/reducing down to the home screen icon. But after that the contact list was full screen, and i could switch between open apps (like the multitask switching, long swipe up from bottom), and the open apps were all in full screen. Normally the multitask switching reduces the viewport to half the size, but not now. Have anyone experienced this before?

                      To calrify, i could swipe anywhere on the screen to swipe between apps, and the switched apps was filling the entire screen. And stopping on one app didn't actually open the app, I could swipe indefinitely.

                      Pixel 7 Pro
                      2025030900
                      Normal call via mobile network

                      Anyone figured out how to SSH into the terminal from another machine? I have tried setting up SSH but I am getting an error:

                      ssh: connect to host 192.168.1.181 port 2222: Connection refused

                      (I changed from port 22 and allowed it when I got the notification prompt)

                      I am probably failing in a very basic way.

                        Will we one day be able to use our Pixels and GoS to run full OSes in a virtual environment?

                          0xsigsev The terminal can ping other devices on the network, and login via SSH even. However when trying to ping from that other device I get a time out. For example, my other device is 192.168.1.50 I can SSH from the terminal. The terminal is 192.168.0.2 which I cannot ping.

                              grapheneosuser294783 is that even an actual IP acquired by DHCP on your router? I guess not, since the subnet is different, so I would assume this is an internal, self assigned IP inside the VM. SSH or anything with ICMP will not work obviously, since the router doesn't know where it is.

                                grapheneosuser294783 That's the point, you'd need to bind that IP to be able to ssh to it. Assuming inbound connections are at all allowed. Check the iptables/nftables rules to figure out what's going on

                                    locked That's already what this feature provides. The next release of GrapheneOS likely coming later today includes GUI, speaker and microphone support.

                                        Has anyone else lost RCS chat ability in Google Messages recently?

                                        0xsigsev They are all empty. I've tried adding some rules (but I'm pretty clueless at IPtables so GPT tried to help).

                                        I tried making a new network in /etc/systemd/network but that did not work either.

                                        I'm curious if anyone else has actually managed to SSH into the terminal and how they did it. Trying to change DHCP obviously disconnected the terminal window and reset the networking back to defaults. I'm guessing it's probably not possible at this stage?