I recently signed up with jmp.chat and installed the Cheogram app. However, I am facing the same problem that it seems many others have faced. When using the stock dialer or any other dialer, the sound button flickers, and audio output seems to switch rapidly between Bluetooth, speaker, and handset, and I'm unable to actually communicate. Most of the time when the sound button flickers, I am unable to select what device I'd actually like to talk through. On rare occasions, when it flickers I can actually select it, but that's rare. Sometimes the sound button flickers for a moment and then seems to find the Bluetooth connection. And then I'm able to talk normally. But that only happens about 25% of the time. There seems to be no rhyme or reason to it. I can have difficulty with the sound button flickering on one call and hang up and and make another call directly after, and that second call, will be connected normally with the sound button connecting to Bluetooth correctly. You can imagine how frustrating this can be.

I'm using a Pixel 9 Pro Fold with Graphine OS. I have tried the stock dialer, fossify dialer, and Google dialer all have the exact same results. I have given the Cheogram app and the dialer app, all the permissions that they require, and I've also enabled the exploit compatibility mode with Cheogram. None of it seems to make any difference.

In researching this problem, I discovered that others have had this problem, and JMP. net/Cheogram fixed this with an update to Cheogram 2.15. I am using Cheogram 2.17.24 So perhaps there's been some regression. Apparently, I'm not alone as other users after 2.15 have also had the same problem.

When talking to the JMP.chat people, they seem to believe that the problem is a Graphine OS problem. I don't have any audio problems with any audio devices using any other app, whether it be music or Signal or any other app, just the Cheogram app. In fact, I would say my Graphine OS experience has been awesome. I can't think of a single problem except for Cheogram. But in spite of my positive experience, I want to be fair. Could this indeed be a bug somewhere in graphene? The JMP.chat people say that they only see this problem with graphene OS. Up to this point, they've really not had much to offer to solve the problem.

So without a clear solution in mind, I'm here to ask if this could indeed be a Graphine problem? I know that others have faced this problem. If you faced this problem, were you able to overcome it? What did you wind up doing to fix the problem? I am desperate to get this to work.

I'm running out of time to dedicate to fixing this. If you couldn't fix the problem, what did you wind up doing for voice over IP?

    Smog
    Have you tried using Conversations, the app Cheogram is based upon, instead. I wonder if that has the same issue.

    For a quick work around could alternatively use a wired usb headset.

    • Smog replied to this.

        Smog When talking to the JMP.chat people, they seem to believe that the problem is a Graphine OS problem. [...] Could this indeed be a bug somewhere in graphene?

        Sure, why not? But it's hard to say.

        Most AOSP derivatives (e.g., Lineage) are often very far behind AOSP, while GrapheneOS tracks AOSP very promptly. So if in February of 2025 almost all Cheogram users using Google's OS and Samsung's OS and LineageOS are happy, but there is a problem on GrapheneOS, maybe that means there is a bug in GrapheneOS, or maybe there is a bug in Cheogram that is exposed by the newest AOSP code that almost nobody is running except for GrapheneOS users.

        Every time a new Android release rolls out, some developers need to update their apps. Users of Google's OS may update to the new Android over a period of months (and some never will). LineageOS may not update for weeks or months. But a very large fraction of GrapheneOS users will update on the same day. So this forum will fill up with "Why did the new GrapheneOS release break my ThunderTwitch app? It works fine on my friend's phone with the latest BargleOS!!". And app developers may see a sudden wave of complaints "from GrapheneOS users". But really what's happening is complaints from Android 15 users, almost all of whom are running A15 because they are running GrapheneOS.

        Anyway, the way to decide whether a bug is in Cheogram or in GrapheneOS is for somebody to find the bug. Then it will likely be clear where it is.

        Aside from finding the bug, probably the best thing would be trying Cheogram on vanilla AOSP (which is run by almost nobody). If AOSP and Cheogram disagree, maybe the issue is AOSP, maybe it's Cheogram, but it almost certainty won't be GrapheneOS.

            Where did you download the Cheogram app from? Just for reference, I installed the F-droid version via Obtanium and it's labeled version 2.17.2-4+free. I've never had any issues with Cheogram and I've been using it about a year now. I'm using the stock dialer on Pixel 8 and don't have Google Play services installed. Did you enable jmp.chat in Calling Accounts on the stock Dialer settings?

              Smog Turn on system crash reporting in Settings > Security & privacy > More privacy & security at the bottom. It's possible your Bluetooth accessory is uncovering a memory corruption bug detected by GrapheneOS.###

                  @Smog I am unable to reproduce this issue.
                  Cheogram version 2.17.2-4+free version code 4205704.

                  can you please provide some info on how to reproduce this issue?

                    pratyush
                    I wish I knew how to reproduce it. That might give me some clues to help me solve the problem. I just signed up with jmp.net and then I installed Cheogram and began having the problem from day one.

                      Carlos-Anso
                      I like this idea a lot. I won't have time to try it out until Monday, but that will be the first thing I do. Thanks for this. This seems to be a really constructive idea.

                        I see from the discussion there are users with earlier versions of pixels that are using JMP.net/Cheogram without any trouble. I have an old lineage phone that I could try, but if there are users who are successfully using JMP.net/Cheogram with older devices, I don't know that it would help determine anything.

                        I wonder if there are users of the Google Pixel 9 series who are using JMP.net/Cheogram successfully?

                        I hate this feeling like I'm the only one with this problem.

                        • de0u replied to this.

                          GrapheneOS
                          I did try this. And then I went and tried a phone call while using Bluetooth. It failed as it usually does. I got no notifications of anything. But I can only assume that that means perhaps that the graphing team would get a notification? But it didn't ask to send anything so I don't know if it recognized a problem. Thanks for the suggestion.

                            • SSmog

                              • Post #13
                              • Edited

                              Carlos-Anso
                              Thank you for the input and thank you for this suggestion. I did try conversations, but it seems to lack dialer integration, which is really where the problem was with Cheogram. Otherwise it seemed to function just like cheogram did.

                              I do appreciate your suggestion about the wired headset. I did think about that, but using the dialer with Bluetooth is pretty important. Whether it be driving or working out on the gym and a call comes in, the ability to answer that is pretty necessary. Thank you.

                                Smog I hate this feeling like I'm the only one with this problem.

                                I wonder if clearing Phone's cache would make a difference?

                                I don't know what might be lost by clearing Phone's storage too... maybe the call log?

                                  In an attempt to figure out where the problem is, I installed JMP.chat/Cheogram on an older phone, a Pixel 5a with Graphine OS (Android 14 build number 20250221000). It worked beautifully in my limited testing. So it looks like the problem may be a pixel 9 series or an Android 15 problem.

                                  Is there anyone running JMP.chat/Cheogram on a Pixel 9, Android 15? (With or without GrapheneOS)

                                  Has the issue been reproduced on the stock OS on a Pixel 9?

                                  • Smog replied to this.

                                    I was thinking about this. I might give it a try. I'll need to backup my stuff first so it might take me a day or two to get everything backed up.

                                    Is there a guide to restore to stock? I use Linux if it needs a PC.

                                    When I try stock are there any logs I can extract that would be helpful? I also thought of factory resetting Graphine to try it without any possible conflicts therthere as well.

                                      spring-onion
                                      Thanks. That looks like I can flash using a graphine phone instead of a PC like I did to install GrapheneOS in the first place. Am I understanding that correctly?

                                          Smog

                                          Any phone running Android 12 or higher, not only GrapheneOS.

                                            • SSmog

                                              • Post #21

                                              GrapheneOS
                                              Are there any logs I can create that would help diagnose the problem? Where should I submit those to?