Pixel Fold - Outer Screen Stopped Working

de0u

Glo This is not hardware issue.

If the issue is present on GrapheneOS but not on Google's stock OS, it is not a hardware issue. If a factory reset of GrapheneOS makes the issue go away for a long time, it's probably not a hardware issue.

If the issue is present on GrapheneOS and on Google's stock OS, it most likely is a hardware issue -- as reported by users of Google's stock OS, e.g.:

Glo

de0u
Thank you for your help and for raising this issue.

de0u https://support.google.com/pixelphone/thread/255727280/outer-screen-not-working

I wanna say that "Outer screen not working" is incorrect, because the screen is working, but not correctly. You can switch to the Rear Camera Selfies and start the screen. Or use the Fold Switcher app and switch the screen manually.

de0u

de0u https://www.reddit.com/r/PixelFold/comments/1bg97iw/outer_screen_touch_not_working/

This is not the same thing. A similar error occurs due to a pop socket with a magnet and a circle under the same phone case. The magnet affects the open/close sensor.

Our problem is FoldableSeviceStateProvider and

de0u Please note that multiple users in that GitHub thread determined that their issue was a hardware failure.

You are right. But different issues are described under one thread

de0u

Glo Please note that multiple users in that GitHub thread determined that their issue was a hardware failure.

de0u

Glo Different issues are described under one thread.

Maybe I missed it, but I didn't see a report (there or here) of a device that exhibited the issue on GrapheneOS but worked fine when flashed back to Google's stock OS. If there is such a case, it might be productive for the GrapheneOS developers to look into it, though probably not very productive if they can't reproduce it. However, if there is not such a case then the issue likely is a hardware problem. Even if it is a firmware glitch that affects a very small number of devices, it's genuinely not likely that the GrapheneOS developers would fix it before Google does, especially if they don't have a device exhibiting the issue.

In terms of moving forward with your device, I can understand that you may be reluctant to factory-reset it or to flash it back to Google's OS. But I am confident that without those steps the likelihood that the issue with your device will be resolved by the GrapheneOS developers is near zero. And if the issue persists after those steps it is extremely unlikely that it will be resolved by the GrapheneOS developers.

Please note that I do not speak for the GrapheneOS project.

sketchy9

I had the exact same problem. Everything was working well until the other day when I rebooted the phone (for an unrelated reason) and the front screen no longer worked. The boot splash screen would show and then it was black. I tried using the rear camera as a selfie camera and that would also work, showing that it was not a hardware issue. I ended up reflashing GrapheneOS onto the phone and everything worked again as usual (I did not flash to the stock Google Pixel OS first. I simply reflashed GrapheneOS onto the pre-existing GrapheneOS).

I say everything worked "as usual" because since about September my front-facing camera doesn't work at all. I also believe this is a software issue because neither the outer front-facing camera nor the inner front-facing camera are recognized. I have a hard time believing I would have simultaneous failure of two different cameras, but perhaps there is some common pathway that failed that affects them both.

In short, GrapheneOS has some rough edges when it comes to the OG Fold. I'm on build 2025112100.

pixel_user

I have the same outer screen issue on Pixel Pro Fold 9 after an update a month ago. Furthermore, since the same patch I have two extra bugs which I have described here: https://discuss.grapheneos.org/d/31694-screen-doesnt-respond-when-folded-and-no-option-to-reconnect-to-mobile-network/2

BurgherCain

b3nji Having the exact issue, after my phone rebooted itself (which it's never done before) on Friday the 13th. Just one minute perfectly fine then next no outer screen. The FoldSwitcher @Glo cited does work. I am hard pressed to believe this is because of a ribbon cable as the phone works normally until Android OS is running.

ifman13

I have been using a Pixel Fold with GrapheneOS for 16 months and have never had any problems with any screen.
Reading your comments, it's scary to think that this problem could arise. I hope a solution is found soon.

shirubax

I am having the same issue.

Opening took a bit longer for the internal screen to display the last few days.
There is a question mark next to the battery
The external screen does display when I close the phone, but touch doesn't work.
Rebooting, including completely powering down does not fix the issue.
The "selfie" camera behind the front screen does work.
This also started happening after an update - but searching online, this is a common issue with the stock OS too, also often occurring after an update.
I think perhaps a new version of Android started using some signals that are not getting through correctly.
Either way, since it happens with stock OS, I don't think it's a Graphene OS issue - though perhaps Graphene OS could offer a work-around (though I think that is probably a bit out of scope).

Aeleon

shirubax No, it's a hardware failure. Very common with pixel 9 fold, exactly as you describe.

shirubax

By the way, this was covered under Google's extended support program as it's a known design defect for this phone.

de0u

shirubax Thanks for reporting back! This information may well be useful to others.

« Previous Page