Official feedback from Octopus re: Electroverse compatibility with GrapheneOS

edwin-jones

Hey folks, I was trying to sign up for Octopus Energy's electroverse EV charging app in the UK and noticed it wasn't supported, even though the main octopus app is. I emailed their team and got confirmation GrapheneOS isn't support BUT they intend to support it soon. I think it's great news it's on their roadmap and hopefully this post helps anybody else trying to understand why the app won't work for them.

Hey Edwin,

Thanks a lot for reaching out to us to discuss this!

You're absolutely correct; at this time, devices running GrapheneOS are not supported by our app - not very helpful! However, we've certainly taken note of the demand for this, and it's now on our list of priorities for future development. While I don't have a specific timeline to share just yet, please be assured that we do plan to offer support for GrapheneOS in the future.

Hope this helps, let me know if you've got any other questions.

t_r_davies

Note that I was able to install Electroverse a couple of months ago from APKMirror without any problems at all.

Adoo

t_r_davies Which APKMirror did you install the app from? I would like to use the app for my holiday as it lists almost all charging stations and is easy to filter.

Adoo

That's good news, I also installed Octopus Energy's electroverse EV and it keeps crashing. Hopefully GrapheneOS will be supported soon.

wizoatk

FWIW Version 2025.25.0 is the latest on Play Store. I installed it, created an account, and played around with the map a little. No immediate issues seen.

Adoo

wizoatk Now I was hoping that the error has been fixed and have also installed version 2025.25.0. But unfortunately it also crashes after a few minutes, sometimes the error occurs faster. I have attached the report.

`type: crash
userType: full.secondary
package: energy.octopus.electricjuice.android:953, targetSdk 35
osVersion: google/akita/akita:15/BP1A.250505.005.B1/2025050700:user/release-keys
uid: 1410278 (u:r:untrusted_app:s0:c22,c257,c526,c768)
cmdline: energy.octopus.electricjuice.android
processUptime: 1458s

signal: 11 (SIGSEGV), code 9 (SEGV_MTESERR), faultAddr d9eb734d1110
threadName: MapboxRenderThr
MTE: enabled

backtrace:
    /data/app/~~ZGzOixEVArWLZT8wLrpLhA==/energy.octopus.electricjuice.android-ZqVj3r2J4XR4lUi_1lP2nw==/split_config.arm64_v8a.apk!libmapbox-maps.so (pc 76b3f0)
    /data/app/~~ZGzOixEVArWLZT8wLrpLhA==/energy.octopus.electricjuice.android-ZqVj3r2J4XR4lUi_1lP2nw==/split_config.arm64_v8a.apk!libmapbox-maps.so (pc 5944e0)
    /data/app/~~ZGzOixEVArWLZT8wLrpLhA==/energy.octopus.electricjuice.android-ZqVj3r2J4XR4lUi_1lP2nw==/split_config.arm64_v8a.apk!libmapbox-maps.so (pc 5f756c)
    /data/app/~~ZGzOixEVArWLZT8wLrpLhA==/energy.octopus.electricjuice.android-ZqVj3r2J4XR4lUi_1lP2nw==/split_config.arm64_v8a.apk!libmapbox-maps.so (pc 5f63a8)
    /data/app/~~ZGzOixEVArWLZT8wLrpLhA==/energy.octopus.electricjuice.android-ZqVj3r2J4XR4lUi_1lP2nw==/split_config.arm64_v8a.apk!libmapbox-maps.so (pc 5f48b8)
    /data/app/~~ZGzOixEVArWLZT8wLrpLhA==/energy.octopus.electricjuice.android-ZqVj3r2J4XR4lUi_1lP2nw==/split_config.arm64_v8a.apk!libmapbox-maps.so (pc 637864)
    /data/app/~~ZGzOixEVArWLZT8wLrpLhA==/energy.octopus.electricjuice.android-ZqVj3r2J4XR4lUi_1lP2nw==/split_config.arm64_v8a.apk!libmapbox-maps.so (pc 5c35c0)
    /data/app/~~ZGzOixEVArWLZT8wLrpLhA==/energy.octopus.electricjuice.android-ZqVj3r2J4XR4lUi_1lP2nw==/split_config.arm64_v8a.apk!libmapbox-maps.so (pc 5c3ba4)
    /data/app/~~ZGzOixEVArWLZT8wLrpLhA==/energy.octopus.electricjuice.android-ZqVj3r2J4XR4lUi_1lP2nw==/split_config.arm64_v8a.apk!libmapbox-maps.so (pc 64a4b0)
    /data/app/~~ZGzOixEVArWLZT8wLrpLhA==/energy.octopus.electricjuice.android-ZqVj3r2J4XR4lUi_1lP2nw==/split_config.arm64_v8a.apk!libmapbox-maps.so (pc 64826c)
    /data/app/~~ZGzOixEVArWLZT8wLrpLhA==/energy.octopus.electricjuice.android-ZqVj3r2J4XR4lUi_1lP2nw==/split_config.arm64_v8a.apk!libmapbox-maps.so (pc 4aadac)
    /data/app/~~ZGzOixEVArWLZT8wLrpLhA==/energy.octopus.electricjuice.android-ZqVj3r2J4XR4lUi_1lP2nw==/split_config.arm64_v8a.apk!libmapbox-maps.so (pc 4a2c70)
    /data/app/~~ZGzOixEVArWLZT8wLrpLhA==/energy.octopus.electricjuice.android-ZqVj3r2J4XR4lUi_1lP2nw==/split_config.arm64_v8a.apk!libmapbox-maps.so (pc 936c24)
    /system/framework/arm64/boot.oat (art_jni_trampoline+112, pc 2cd120)
    /data/app/~~ZGzOixEVArWLZT8wLrpLhA==/energy.octopus.electricjuice.android-ZqVj3r2J4XR4lUi_1lP2nw==/oat/arm64/base.odex (com.mapbox.maps.renderer.MapboxRenderThread.draw+564, pc 3590684)
    /data/app/~~ZGzOixEVArWLZT8wLrpLhA==/energy.octopus.electricjuice.android-ZqVj3r2J4XR4lUi_1lP2nw==/oat/arm64/base.odex (com.mapbox.maps.renderer.MapboxRenderThread.doFrame+336, pc 35945d0)
    /system/framework/arm64/boot-framework.oat (android.view.Choreographer.doCallbacks+884, pc 606eb4)
    /system/framework/arm64/boot-framework.oat (android.view.Choreographer.doFrame+2256, pc 607a00)
    /system/framework/arm64/boot-framework.oat (android.view.Choreographer$FrameDisplayEventReceiver.run+72, pc 605868)
    /system/framework/arm64/boot-framework.oat (android.os.Handler.dispatchMessage+68, pc 4b83f4)
    /system/framework/arm64/boot-framework.oat (android.os.Looper.loopOnce+976, pc 4ed1c0)
    /system/framework/arm64/boot-framework.oat (android.os.Looper.loop+244, pc 4ecd74)
    /system/framework/arm64/boot-framework.oat (android.os.HandlerThread.run+544, pc 4e05d0)
    /apex/com.android.art/lib64/libart.so (art_quick_invoke_stub+612, pc 37db94)
    /apex/com.android.art/lib64/libart.so (art::ArtMethod::Invoke(art::Thread*, unsigned int*, unsigned int, art::JValue*, char const*)+140, pc 3a61ac)
    /apex/com.android.art/lib64/libart.so (art::Thread::CreateCallback(void*)+1008, pc 54bcb0)
    /apex/com.android.art/lib64/libart.so (art::Thread::CreateCallbackWithUffdGc(void*)+12, pc 54b8ac)
    /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*)+180, pc 7b134)
    /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+68, pc 6bc64)`

wizoatk

Adoo

I can reproduce a similar MTE error.

matchboxbananasynergy

Adoo If that's the issue, enabling exploit protection app compatibility mode for the app in app info should get it running.

wizoatk

matchboxbananasynergy

Believe I've tried that before, but I'll repeat again.

Enabled "Exploit protection compatability mode". It still crashes with "Memory tagging detected an error in Electroverse".

Memory tagging is still "Enabled This app has opted-in to memory tagging". And apparently cannot be disable as both options for "Default (Disabled)" and "Disabled" are greyed out in the settings.

Uninstalled Electroverse, reinstalled, enabled compatability mode. Started app and can still force MTE crash with a bit of fiddling between Maps and Profile/Settings in the app.

Anything else I can try or do?

matchboxbananasynergy

Ah, I see. The app themselves have marked it as compatible with MTE. We make it so MTE is always enabled in that case. They either need to stop opting into MTE or fix their memory corruption bug.

wizoatk

Thanks for the confirmation. That's pretty much where my head was at too.

dee_

I don't think they're going to fix it... I traced it back to an exception inside a third party library supplied by MapBox... when I spoke to Electroverse support all I got was "we see you're running GrapheneOS and we do not support that, I hope you have another device that you can use" (not entirely helpful when the car had little battery left and I couldn't launch the app to start a charge).

I too would like the option to disable MTE explicitly so that I can get the app to run, as not charging the car is a big motivation to move back to Google Android, and I just do not want to do that and would prefer to stay on Graphene as this is the only roadblock that I've run into.

dee_

btw, I can get it to run with Exploit Compatibility Mode set to Enabled... but that only defers the crash rather than guarantees it won't crash AFAICT. sometimes it's enough to get a charge started, sometimes it's not... I don't know exactly how to trigger the MTE crash except to have narrowed it down to the MapBox library.

matchboxbananasynergy

We do allow users to enable/disable MTE for apps, but not when the app itself has opted into it. This is their issue, they have an MTE issue but are opting into it. It's not specific to GrapheneOS, it would crash on another OS with MTE too.

edwin-jones

Looks like my feedback to octopus helped, I can now install and run the app from Google Play on my 8a. Thanks for the updates!