Incoming call not displaying

jemmy7776

Sometimes incoming call does not display on screen and even if I try to go to phone app the call screen do not display anywhere, only phone vibrates. Any quick fix for that?

DevilsDueRebellion

Sounds similar to an issue that I am having on the 6. If it slightly helps you I find I do not need to completely reboot, just relog back into the ended session.
Its possible your issue may be resolved with a factory reset. I read recently someone else with a 7 was fine after. The 6 for me did not resolve with a reset however.

jemmy7776 I could only test once a day but i finally found a workaround.

Go to settings/ system / gestures. Then turn off the option that says Prevent Ringing on all profiles. This seems to have resolved it even when a factory reset would not.

ReadOnlyUser

I experienced same with Pixel 7 running 2022101800 release. Signal was also affected at the same time by not showing notification/calls. Just the sound was triggered. So maybe it's not only about calls but about notification in general. Reboot solved these issues for now.

DevilsDueRebellion

Sorry all, it seems although I only tested that change, the real reason it worked that day is because the profile was continually being active. It seems tied to some kind of keep alive on the profile. I'll make sure to repeat test if I see something work next time.

DevilsDueRebellion

Fixed with completely full reflash. To avoid confusion in my case a factory reset did not work. A reflash of just Grapheneos did not work. It required me to first flash back to stock android and then flash to Grapheneos again completely.

The take away from this is to double check you have disabled OEM unlock after finishing installation. Especially if you obtained your phone from a third party that automatically installs Grapheneos.

I have two phones, one I setup myself which ran fine and the other custom setup and they did not disable OEM unlock. I assumed it was or that I checked it previously. Double check this option whatever your case.

GlytchMeister

DevilsDueRebellion

I was under the impression that GOS strongly advises against buying phones from 3rd parties that install GOS themselves due to not only erroneous installation issues like this, but also due to major privacy and security concerns because that 3rd party can modify whatever they want about their "version" of GOS. IIRC, this sort of thing has been used as honey traps by law enforcement - they made a bogus company that sold "private" and "secure" phones that were actually extensively backdoored to allow law enforcement snooping.

DevilsDueRebellion

A bug when using lockdown mode. Not fixed.

Elvira

This just happened to me as well (I'm using the new 2023100800 release on a Pixal 6a phone).

Resetting my device to factory settings didn't help and apparently a completely full reflash doesn't work either (according to DevilsDueRebellion). Hope this will be fixed soon :(

RautaKanke

Have a similar issue with a 6a and a 6 Pro. 20231105 on both. No sound, no vibration and no lit-up display. Call can only be seen in the drop-down menu on the main screen.

This happens most of the time, but sometimes it rings as it should...

Will check if turning off Prevent Ringing helps.

RautaKanke

RautaKanke No help from turning off Prevent Ringing.

RautaKanke

RautaKanke The phone rings OK (display also being turned on) on incoming calls in Owner Mode on the 6a. Prevent Ringing worked on the 6 Pro. This is bad voodoo. Does anyone have a clue?

rkeenan

Hello, I'm having the same problem described in this thread. I'm using the Pixel 6a. I've tried resetting the carrier settings and rebooting the device. Resetting the entire device does not seem to work. Is this problem resolved?

AlanRyan

rkeenan

I have the same issue, but only if I install another Dialer app and disable the stock one, which sucks because the stock GrapheneOS dialer is ugly and it means you have to have 2 dialers in your launcher.

CuriousGeorge

rkeenan AlanRyan

Any luck on solving this? Unfortunately happening to me for both the native app and installed apps. Interestingly, the phone calls do show up in another profile, so I'm wondering if there's a setting I've messed up in the main profile...

AlanRyan

CuriousGeorge

Nope. The stock dialer works fine to me, but nothing else.

rkeenan

CuriousGeorge

No I haven't resolved this issue. I've wiped the phone, reinstalled GOS, restored the service provider settings, nothing works. Takes me 3-5 minutes to receive a text and I rarely get the notification that I'm receiving a call. The phone is almost useless at this point. Honestly at this point, I'm ready to wipe the phone and use stock Google android.

I opened a github ticket with the developer, but he claims that this is not a GOS issue...

CuriousGeorge

AlanRyan

Urgh, I wish the stock dialer worked... I guess I should reflash then. Just a pain and a worry if I haven't backed up everything properly.

I can answer calls using my bluetooth headphone touch gestures at least in the meantime.

de0u

GlytchMeister I was under the impression that GOS strongly advises against buying phones from 3rd parties that install GOS themselves due to not only erroneous installation issues like this, but also due to major privacy and security concerns because that 3rd party can modify whatever they want about their "version" of GOS.

Is it possible to cite a source?

Detecting a tweaked version of GrapheneOS is as easy as rebooting once. If the boot hash matches, and no "corrupt OS" alert is displayed, either it's a legitimate GrapheneOS image or a very-well-resourced attacker has compromised Google's verified boot, or perhaps has a secret fab spitting out fake Google SoCs. Somebody that powerful could probably get your data via cheaper means.

GlytchMeister

Could've sworn I saw something to that effect on the GOS website, but I can't find it now. So I guess take what I say with many, many grains of salt.

de0u

rkeenan Takes me 3-5 minutes to receive a text and I rarely get the notification that I'm receiving a call.

Just FYI, this is not at all typical for GrapheneOS users, especially not with a blank phone right after a factory reset (i.e., using the stock dialer).

What happens if the SIM card from the GrapheneOS device is used in a different phone? What happens if a different SIM card is used in the GrapheneOS device? Which carrier is being used?

other8026

rkeenan but he claims that this is not a GOS issue...

It does sound like an AOSP issue. As far as I know, GrapheneOS hasn't changed any of the related code, so the only remaining source of the bug would be upstream AOSP.

rkeenan the developer

Just want to point out that there are multiple full time developers.

Only a small number of people report having this issue. This just leads me (personally, not speaking for any developers or the project here) to believe that it's some issue with the setup.