I have a Pixel 7a running GrapheneOS. I have a MySudo VOIP account running separate phone numbers and emails for different profiles. messages and emails are coming through with no issue but phone calls never come through, they just go to voicemail. I'm having a similar issue with Zalo. I get the voicemail notification, just not the call. I am however able to make outgoing calls with no issue, so the line is up, its just an issue with the call notifications. I checked with the MySudo Support page (https://support.mysudo.com/hc/en-us/articles/360020182333-I-m-unable-to-make-or-receive-a-voice-call) and followed the trouble shooting instructions. I verified that Receive call notifications is turned on in the MySudo settings. I checked that my device's Do not disturb feature was not enabled. I verified that my device's date and time are set to automatic, I verified that my device is giving notification permissions to the app. I checked that the individual MySudo profiles are set to receive call notifications. I don't know what else to check. Does anybody have any suggestions? or is there a line I can call to troubleshoot? Can I pay someone to do some technical support?

a month later

I'm experiencing the exact same issue and MySudo support has been less than helpful, I've reinstalled google services, and MySudo multiple times, done everything their support said to do and followed the advice in a few threads here with no luck.

Sorry you are having issues with Mysudo on Graphene, but honestly I ran into them too. I ended up porting my VOIP numbers out of MySudo to Cheogram + JMP.chat. It always rings, does not require any Google services to be installed, and even integrates with the stock dialer. Plus I can use my VOIP numbers on my laptop too. Maybe worth considering if you can't find a solution.

    Just like @calpurtmun mentions I, too, ran into many issues with the MySudo app and service on GOS. Contacting MySudo support was a waste of time, as they just brushed it off. So, I also switched to Cheogram (the XMPP/Jabber client) + JMP.chat (the XMPP gateway/VoIP provider) + a hosted Snikket instance (XMPP server). If you're unfamiliar with Jabber, it can be quite confusing at first, but it becomes much clearer as you utilize it.

    FWIW, there's some steps I shared with the community here, that may help you resolve your MySudo issues.

    Also I forgot to mention @Rhusta:

    Also, take a look at this MySudo support post. MySudo staff states that incoming call notifications/rings will not work on a GrapheneOS device without Sandboxed Google Play services. So, @Rhusta you can choose to install Google Play services (perhaps even on a secondary user profile for added privacy), and see if your issue persists. FWIW, I tried this and it didn't work for me, but YMMV.

      lordiont I do have play services installed and receive every notification accept for calls. I get a missed call notification lol. As for jabber, do I need to use snikket or could I just make a jmp account and use cheogram for calls? I also did follow your steps trying to fix it with no luck.

          Rasta9 Yeah, so given that you have Sandboxed Google Play services installed and it's still not working, you should forget about MySudo, IMHO.

          Well, when you create and account with JMP (which you can do entirely from the Cheogram app), you have to select a server, so that it all works as it should.

          I you plan on using JMP, I suggest you take a look at JMP's Frequently Asked Questions, page. It explains most of what you need to know. Regarding the Jabber/XMPP servers, read question number 16, and visit this link, which explains the Snikket thing further. What you're looking for is Snikket Hosting, i.e., a hosted instance, not to self-host, as that is more complex.

          Lastly, I suggest you take a look at JMP's support methods here. Their web chat is especially helpful and the staff is very responsive.

          P.S.: this Reddit thread may answer some other questions for you.

              lordiont

              One thing I’ve been concerned about with all the recent sim swap type attacks, do the jabber ids offer 2fa to prevent someone from stealing your number?

                  applesbana From my understanding, no. That is, Snikket which is my XMPP/Jabber provider that provisions my account and my Jabber IDs, doesn't support 2FA. I really wish they did.

                  However, given that phone numbers provisioned by JMP are not true cellular numbers, but rather are VoIP numbers, the odds of a successful SIM swap attack are much lower. Typically, attackers will target victims whose phone number (obtained via phishing or social engineering) is provisioned by a carrier like Verizon or T-Mobile. Because pretexting a low-paid CS rep from a legacy phone company is a lot easier that trying to SIM swap a VoIP number.

                  That said, I'm sure nothing is impossible. And I really do wish Snikket and other XMPP providers allowed for MFA and a toggle to lock any port-out attempts, like Google Voice does.

                    2 months later

                    [deleted]
                    Once you are on a plan (say 3 numbers)
                    You can create 3 "sudos" - effectively 3 identities with a handle, email and a phone number of no extra cost. It is included in your monthly payment.

                    If you wish to change a number on a specific sudo, then you must pay ~$1 (not entirely sure). For each number/ time you want to change.

                    Note I believe you are restricted to 3 or less numbers. If you want a 4th you have to get the 9 number plan. You cannot add a number for $1 after you have reached your plans cap.

                    Hope this helps.

                      [deleted] for JMP.chat yes you pay for each number. I only have three so it's not very much. The JMP.chat website has more info about how it works.

                        9 months later

                        Try going into Apps - Google Play Services, and changing notification permissions inside Google Play Services to ON, and then turn off all the options except Allow full-screen notifications and allow notification dot.