I got it working on a Xiaomi with faking to Pixel 6, but never on my 6a with GOS. :(
KernelSU doesn't work anymore, so no chance to test or does anyone have tips on booting a rooted boot.img?
I know, root is bad but...
Dexcom G7 connection error
4 months later
Has anyone got the G7 app working? I really don't want to have to buy a stand alone monitor 😮💨
I am getting a "Connection Error" when opening the app.
No VPN or DNS filters on.
a month later
Well, I can confirm the Dexcom G7 app isn't working on my new install of Grapheme OS on my Pixel 9 Pro XL, but was with the stock Android 15 install.
PjMuffin Me too.
How can I Post or share the app log for dexcom g7 ?
disqus_a4OlbSVOoE
Can you send logs to me on matrix or via email @carlosanso:grapheneos.org
Carlos-Anso Done. Let me know if you don't see it for any reason. Subject is: Fw: Dexcom G7 Case #250107-013582
Carlos-Anso It's basically lots of this sort of stuff.
--------- beginning of events
01-08 02:32:05.214 21859 21859 I auditd : avc=type=1400 audit(0.0:9878): avc: denied { read } for comm="app_process64" name="u:object_r:userdebug_or_eng_prop:s0" dev="tmpfs" ino=385 scontext=u:r:untrusted_app:s0:c168,c256,c512,c768 tcontext=u:object_r:userdebug_or_eng_prop:s0 tclass=file permissive=0 app=com.dexcom.g7
01-08 02:32:05.226 21859 21859 I auditd : avc=type=1400 audit(0.0:9879): avc: denied { read } for comm="app_process64" name="u:object_r:userdebug_or_eng_prop:s0" dev="tmpfs" ino=385 scontext=u:r:untrusted_app:s0:c168,c256,c512,c768 tcontext=u:object_r:userdebug_or_eng_prop:s0 tclass=file permissive=0 app=com.dexcom.g7
01-08 02:32:05.226 21859 21859 I auditd : avc=type=1400 audit(0.0:9880): avc: denied { read } for comm="app_process64" name="u:object_r:userdebug_or_eng_prop:s0" dev="tmpfs" ino=385 scontext=u:r:untrusted_app:s0:c168,c256,c512,c768 tcontext=u:object_r:userdebug_or_eng_prop:s0 tclass=file permissive=0 app=com.dexcom.g7
01-08 02:32:05.226 21859 21859 I auditd : avc=type=1400 audit(0.0:9881): avc: denied { read } for comm="app_process64" name="u:object_r:userdebug_or_eng_prop:s0" dev="tmpfs" ino=385 scontext=u:r:untrusted_app:s0:c168,c256,c512,c768 tcontext=u:object_r:userdebug_or_eng_prop:s0 tclass=file permissive=0 app=com.dexcom.g7
01-08 02:32:05.226 21859 21859 I auditd : avc=type=1400 audit(0.0:9882): avc: denied { read } for comm="com.dexcom.g7" name="u:object_r:userdebug_or_eng_prop:s0" dev="tmpfs" ino=385 scontext=u:r:untrusted_app:s0:c168,c256,c512,c768 tcontext=u:object_r:userdebug_or_eng_prop:s0 tclass=file permissive=0 app=com.dexcom.g7
disqus_a4OlbSVOoE apologise I don't mean to intruder on the this thread, however, have you turned on Exploit protection compatibility mode (can be found via settings>apps>app name>exploit protection).
It may also be with changing your network settings to google servers (via networks setting scroll to the bottom three options and select google on each).
Again I apologise if I've overstepped any boundaries
Wadder No worries, but I tried all that. It looks like it's calling some processes that it doesn't have access to due to app sandboxing. Just my guess though.
- Edited
Can see the app has a lot of one star reviews on Play Store people are having all kinds of issues
PjMuffin I am getting a "Connection Error" when opening the app.
Not hugely surprising but theres no sign of any kind of connectivity issues in the logs disqus sent us. They didnt say but thought they may be seeing the same error message. From the logs can see the app is blocking you from running with it and we havent been able to work out why.
We are a relatively small team, always have lots to do, and haven't got the capacity to spend time trying to work out exactly whats happening or implement work around for each individual app purposely blocking users and/or being buggy.
This app apparently implement a whitelist of devices. It may be GrapheneOS is somehow falling foul of however they determine that.
Could be various other things they are looking for. May be a combination of a few factors will push it over a threshold.
In the reddit post linked above theres mention of Private DNS, proxy and VPNs being a cause of blocking. Apps can detect a VPN running in a different profile - user, work or Private space
Noticed a negative Play Store review mentioned having to keep enabling location to keep it working. May be worth you trawling through more reviews looking for reports of people hitting the same issue that you are and figuring out a workaround.
Other things that have been reported to us as blocking other, mainly banking, apps
Dev options enabled
Having a private space
App installed in secondary user
Not having Play Services installed
App not installed from Play Store
Using a less common keyboard app for example something other than Google Keyboard, Samsung Keyboard or swiftboard
Heres some relevant things that one anti-fraud / device trust library looks for as risk factors. Should suggest some other things that may be worth trying if they feel relevant.
no_sim
abnormal_time
screen_sharing
short_uptime
risk_rom - any or risky alternative OS?
gps_fake
sys_multiple_running -more than one profile running?
vpn_detected
adb_link
proxy_detected
Finally it could be they are now using Play Integrity to do the device check. Feels like in this case its more likely something else, but it could be.
Do let us know if you get it working
Carlos-Anso I tried everything, no VPN, no private DNS, tried all the stuff but no joy. I'm using a compatible device that has no problems on the stock android 15. I had to revert back to the stock android 15 and there's really no compatible other app. I'm looking into something called xDrip on GitHub, but that may cause other issues as this is a medical app for a proprietary medical device (CGM). It just really pisses me off that a publicly traded company could be this incompetent with their software development.
https://github.com/NightscoutFoundation/xDrip/discussions/3850
@Mocadon
Mocadon
18 hours ago
Okay, here's what I'm going to do over the next month.
First, I'll get a prescription for the Dexcom G7 receiver and have it delivered.
Second, I'll make a final irreversible move to GrapheneOS.
Third, I'll install and test xDrip+ on GrapheneOS and I'll report my results here. I expect it'll run with sandboxed Google Play services for real time notifications (the main reason apps seem to require it).
Last, I'll verify the G7 sensor can be concurrently paired with the G7 Receiver and my phone running GrapheneOS and xDrip+.
The big missing link is being able to upload directly to Clarity. I'd think that code from byod would be available even if it just became a standalone method.
- Edited
disqus_a4OlbSVOoE it'll run with sandboxed Google Play services for real time notifications
As far as notifications go, Play Services only helps for notifications which are triggered from an internet service , mainly this is messenger apps. Play Services is set to always run and keeps a constant connection to Googles servers. Google push a notification down this connection which, generally, wakes the app and then the app connects to its own server to download the message.
With something like a blood sugar monitor the app has to be awake to do the monitoring, and any notifications will almost certainly not involve any internet connection or Google and just be fired directly on device by the app.
Theres some chance the app may need Play Services for some other reason.
Carlos-Anso I'll keep you updated as I get the receiver and move permanently to GrapheneOS. Diabetics like me who want a secure phone need an alternative to Dexcom's G7 app. The xDrip+ app seems to be the only existing alternative. 👍
6 days later
- Edited
@disqus_a4OlbSVOoE I have the same issue. Tried everything with g7 on graphene os. I used xdrip+ but the problem is it doesn't get the trend arrow like the pump or G7 app. This severely affected my blood sugar management so I am back on G6 sensor. There is a way to upload to clarity in xdrip+ app.
I don't know why Dexcom g6 app works but not this new g7 app. It's a shame and I may have to leave graphene os in the future for my health.
8 days later
pink-donut I've gone back to GrapheneOS and I'm using the G7 Receiver for now. It's actually pretty handy and much smaller than my phone. Uploads to Clarity are simple and fast, but do require a computer to connect to. Next I'll install and test xDrip.
Carlos-Anso Okay, I'm permanently on GrapheneOS. I have the Dexcom receiver that allows me to avoid needing a smartphone. So, I've installed xDrip+ and that's running well without any special settings on GrapheneOS, it paired successfully with the Dexcom G7 transmitter which is concurrently paired with the standalone receiver. Thus, I guess the advice for us diabetics running GrapheneOS is to ditch the Dexcom G7 app and go with xDrip+. The one thing some won't like is that xDrip+ doesn't offer any upload to the Dexcom Clarity app, which does run on GrapheneOS, so if they need that then they'll still need to get the standalone receiver and upload manually via their computer and a USB connection to the Dexcom G7 receiver daily. 👍
disqus_a4OlbSVOoE Thanks for the report! Even if the answer isn't ideal, it's good for people to know some usable situation without each person needing to personally experiment.
Just FYI, I have a Pixel 6a and Pixel 8a running the latest stable xDrip with 2 G7s (and 2 tSlim X2s) and everything works out of the box, without issue. So far, I'd say the bluetooth connection is more stable on Graphene as well, as compared to stock Android.
You might need to monkey with your settings, because I do get a trend arrow on both my and my son's instances. Let me know if you want screenshots or settings and I'd be happy to help.
Can't speak to the Clarity upload as we don't use it - our endos both like the Tandem Source reports better.
Best of luck, regardless!