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?

                          • SSmog

                            • Post #22

                            Well, I restored the pixel to the factory OS and the problem remains. This is definitely NOT a graphene OS problem.

                              • SSmog

                                • Post #23

                                pratyush What pixel do you have? Android 14 or 15?

                                    manage to reproduce it on pixel 8 with MTE, this is bluetooth issue on system layer stock pixel is affected as well.

                                    Smog

                                      Smog Can you please let the Cheogram / jmp.chat people know that so they don't tell people it's a GrapheneOS issue? The app likely has a problem with the current February release of Android 15 QPR1 and perhaps also earlier, maybe since Android 15 QPR1 was released in December. It's important for developers to have a Pixel so they can test the latest Android releases. Android 15 is not the latest Android release and most non-Pixel devices don't ship the monthly and quarterly updates.