Hi guys,
I have really annoying problem which I firstly noticed on Molly, so I switch to Signal since I was thinking it's Molly issue but it is not. Any time I pick up Molly/Signal call while screen is locked, the screen will not turn black when I place phone on my ear and since I have thin case, my ear get in touch with display and slide down quick settings menu or anything else. It's really annoying for me. I tried turn on/off sensors for booth apps, it does not help. Is there any chance how I can get this fixed? I don't have problem with any other apps at all, turning screen to black even with locked screen works.

And also wanted to ask, is there way to setup the phone that it will require unlock before picking up any call? I was trying to find it but I did not.

Many thanks guys upfront for all responds and help. Cheers

    Have you allowed sensors for molly ?

      harvema
      Hi,
      I have difficulty recreating your problems, because…

      1. when I receive an incoming call with the screen locked, I first have to unlock it with a fingerprint scan, otherwise I can't answer the call with Molly at all
      2. to reproduce your problem, I first had to switch off the screen lock in Molly under Settings/Privacy, as this also prevents me from answering calls directly.

      That's why I don't understand your question:

      harvema And also wanted to ask, is there way to setup the phone that it will require unlock before picking up any call? I was trying to find it but I did not.

      However, after answering the call with Molly I have no problem with not turning screen black.
      When the phone is at my ear or I cover the optical sensor with my fingers, the screen goes black immediately.

            Eagle_Owl Hi, thanks for reply. I tried to setup screen lock for Molly and also then for Signal, it does not help. Every time when someone is calling me an phone is locked, the proximity sensor is not working and not turning screen black. It's very funny that on all other aplications like Threema or Whats App it works normally. I am really kinda lost with this lol

              NetRunner88 Hi, sure, I allowed sensors for Molly, I even tried locking the app with fingerprint and unlocking it before every call, sadly this unlock only Molly, the phone remain locked and seems proximity sensor is not working when phone is locked. I am kinda lost, have no idea how to fix this. My friend have same problem - booth on Molly and Signal. All other apps works normally and make screen black when proximity sensor is covered even when call is picked up on locked phone.

              • TGOS replied to this.

                  • TGOS

                    • Post #7
                    • Edited

                    harvema
                    Do you checked your notification settings,?
                    I would try to activate "full screen notification" if not done yet.
                    Othervise you could deinstall and reinstall Molly and hope its solved.

                      I observed the same problem with Molly FOSS v7.26.1, but when answering a call while using the phone (not locked). Screen wont turn off when I put the phone to my ears. I answered a call while using the phone by pressing the green button that shows up in the little notification.

                      Sensors permission is granted as well as full screen notifications are allowed.

                      Not sure what @Eagle_Owl does differently if they can get the screen to turn off during the call with the proximity sensor. Maybe a different Molly version or Molly FOSS or non-FOSS?

                        Snibby
                        Good question. ;-)
                        When I tried to reproduce the problem and it did not occur, I had Molly-FOSS v7.26.1-1 installed.
                        Permissions:
                        – Notifications
                        – Microphone
                        – Network
                        It was under GOS release 2024123000.

                        Now I have tried it again, in the meantime I am using pre-release v7.28.4-1-FOSS & GOS 2025010700.
                        First, I had the same problem. The screen no longer switched off when I hold the Pixel phone to my ear or cover the sensor area with my hand.
                        – Then I made a reboot and tried it again – now it works again as expected!
                        I have nothing changed, only a reboot was the remedy on my phone.
                        Same permissions, no permission for “Phone”, “Sensors” or “Devices nearby” necessary or useful.

                            Eagle_Owl Thanks! That's strange. Not sure if this is an issue specifically on GrapheneOS or with Molly or upstream Signal.

                            That you don't need sensors permission might imply that the proximity sensor is not covered by that permission and is always available for apps.

                              Eagle_Owl this sounds like a Signal/Molly issue. I think some other messaging app (was it WhatsApp?) had similar issues some time ago (maybe even on iOS, I don't exactly remember). So it's certainly in the realm of possibility that it has nothing to do with Graphene at all, but rather a sensor being "stuck" or "held hostage" by another process. I'd file a bug report on Github (if there isn't one already) and see where it goes.

                                2 months later

                                This issue is still present for me with Molly-FOSS v7.33.2-1-FOSS and GOS 2025030300.

                                When my phone is locked and I receive a call via Molly, I can answer the call without having to unlock the phone, but the screen does not go black when I put it near my ear. This results in my ear accidentally pressing buttons, like swiping down the notification bar.

                                It might take some extra setup, but a person could try mollysocket

                                I don't run Molly or Signal myself, but I use Element with ntfy and notifications are sent via UnifiedPush.

                                It works well.

                                Disregard the last post. That likely won't help with the sensor issue.